Hardware Requirements: Difference between revisions

    From Consumerium development wiki R&D Wiki
    m (+ BaracodaPencil)
    (+ This article is from 2004-2005 and describes hardware from that perspective + Category:Technology)
     
    (17 intermediate revisions by 3 users not shown)
    Line 1: Line 1:
    ''See also [[e-waste]], [[protocol requirements]], [[software requirements]] and (especially) [[performance requirements]].''
    This article is from [[2004]]-[[2005]] and describes hardware from that perspective
    ==Hardware requirements of the Consumerium project==
    ==Hardware requirements of the Consumerium project==


    Hardware requirements are divided into four parts:
    Hardware requirements arise from several functions in the network.  Read [[Consumerium Service access]] for the full range of access requirements.


    #Requirements of consumer's terminal
    #Requirements of [[consumer terminal]], typically a [[worn device]]
    #Store's infrastructure's requirements
    #[[Friendly retail]] infrastructure's requirements, e.g. [[retail shelf]], [[checkout counter]]
    #Requirements of the Consumerium-information system
    #[[Computer hardware]] requirements of the [[Consumerium server]] software.
    #Miscellaneous notes on Hardware
    #low-volume product ad product
    #additional hardware that could be integrated
     
    We'll describe each case in detail.  ''Note [[Consumerium maintenance]] must deal with keeping all this junk running, so the less of it there is, the better!''


    We'll describe each case in detail.
    ----
    ----
    ===1. Consumer's terminal===
    ==Consumer's terminal device(s) ==


    Consumer's terminal is usually a mobile telephone because that apparatus can often be found in the consumers pocket or hand bag. A PDA can also be used as a terminal if it is equipped with suitable networking ability. We presume that markets will direct development into such a state that in approximatelly the year 2005 there will be on the mass market a mobile phone that offers the following features:
    Consumer's terminal is usually a [[worn device]] carried in the consumers pocket or hand bag. It might be a [[PDA]] with suitable [[wireless network]]ing ability but is more likely a [[cell phone]] with a [[headset]] attached. All serious cell phones have a [[headset jack]].  This should be the minimum required hardware.  There is also potential to use a [[walkman]] style [[FM radio]] receiver to deliver the [[Consumerium buying signal]] in some cases.  This is optimal as no [[ewaste]] is created by "requiring" advanced devices.


    *The mobile phone has a short-range wireless network technology built-in. Our presumption is that this technology is [[w:Bluetooth|Bluetooth]](tm). We've just received confirmation that Bluetooth v1.1 has finally the possibility to network devices, without revealing the device's identity ([[BD_ADDR]] in the case of Bluetooth)�to other parties. This [[anonymity]] is an unconditional requirement for a networking technology suitable for Consumerium because if the user's identity or his/her terminal's identity were to be exposed to the merchant, it would be possible to gather data about the consumer's behaviour and tastes without his/her permission and knowledge, and to utilize this data in target marketing or pricing.�
    However, we might assume that these existing delivery devices will not satisfy all [[Consumerium Service access]] requirements, e.g. for mobile [[purchasing agent]]s applying [[institutional buying criteria]].  It might further be assumed that markets will direct development into such a state that in approximately the year 2005 there will be on the mass market a mobile phone that offers the following features:


    *The mobile phone has an programming enviroment that is open to developers, so that Consumerium's [[Consumer Agent]] or one component of it can be installed on the phone. The [[w:J2ME]]-enviroment seem very suitable at the first glance and it seems that Java is gaining a broad support among phone manufacturers.
    *The [[headset]] (of course)


    The two features described above are the only features that are ''necessary'' for the consumer's terminal. In the following I describe a few additional hardware features, which would enhance the usability of the system.
    *Short-range wireless network technology built-in. Our presumption is that this technology is [[w:Bluetooth|Bluetooth]](tm).  Bluetooth v1.1 can network devices without revealing the device's identity ([[BD_ADDR]] in the case of Bluetooth)�to other parties. This [[anonymity]] is an unconditional requirement for a networking technology suitable for Consumerium because if the user's identity or his/her terminal's identity were to be exposed to the merchant, it would be possible to gather data about the consumer's behaviour and tastes without his/her permission and knowledge, and to utilize this data in target marketing or pricing.� This would help [[retail management]] and [[brand management]], but at too high a price for the [[consumer privacy]] in our view.  There is usually some [[privacy risk]] with new networking technology.


    *The phone could have a built-in digital camera. I've just tried out the new Nokia 7650 (tm) model, which is Nokia's first phone with a fitted camera. The focusing and resolution properties of 7650 were maybe just a little bit too poor that one could use the pictures to OCR the numerical representation of EAN-codes. But it came very close, so hopes are high that OCRing the code will be possible in the near future.
    *A programming environment that is open to developers, so that Consumerium's [[Consumer Agent]] or one component of it can be installed on the phone to fully participate in a [[healthy buying infrastructure]] and possibly later a more general [[healthy signal infrastructure]]. The [[w:J2ME]] platform based on [[Java]] seems at first glance to have all the right features on paper, but [[Python]] is also now gaining a broad support among phone manufacturers. It is reported by [[Nokia]] that 11 lines of Python can replace 1000 lines of [[C++]]. ''Perhaps however this is very good Python and very bad C++?''


    *The phone could have a bar-code or a general purpose scanner. This would be a perfect hardware feature for Consumerium usability. It would boost the speed and precision of using Consumerium, but unfortunatelly it doesn't seem one of the likeliest gadgets to be integrated into a mobile phone. I've been in contact with Nokia about this feature and I got information that Nokia and other phone-manufacturers have researched the feasibility of integrating a bar-code scanner. At the moment I don't have knowledge of anything concretic happening in this area,  but hey, who knows?
    The features described above are the only features that would enhance the [[consumer terminal]]. To enhance the usability of the system, consider:


    *The First Ever [[Bluetooth]] [[Barcode]] [[Scanner]], The [[BaracodaPencil]], has been introduced by [http://www.baracoda.com Baracoda Wireless Technologies]], which will play a major role in the ease-of-use of Consumerium. We are expecting pricing information soon
    *A [[built-in digital camera]], e.g. as on the Nokia 7650 and 3650 models, with VGA resolution cameras.  The focusing and resolution properties of the phones were maybe just a little bit too poor that one could use the pictures to [[barcode scan]] the numerical representation of EAN-codes ([[barcode]]s). But it came very close, so hopes are high that OCRing the code will be possible in the near future.  [[OCR]] could alternatively be done from [[retail shelf]] tags, which usually contain the product name in a fairly big font with uniform typeface. Also using image recognition of the packaging graphics, e.g. for [[brand logo]]s and [[standard label]]s may be possible.
    ::Update: There is now available an additional lense package (CC-49) for Nokia 3650 that snaps in place of the rear cover offering lenses for focusing to 10 and 5 centimeter distances in addition to the standard 30cm to infinity focusing, which would be just the thing. Unfortunately the Nokia models don't enable TCP/IP traffic over Bluetooth - it is quite common to find such limits built into phones as part of a [[planned obsolescence]] strategy.  One of the more important [[Consumerium]] goals is to avoid such junk to cut [[e-waste]].


    *There are reports saying that [[w:RFID]] (Radio Frequency IDentification) might be surpassing bar codes even in retail stores as a means of product identification. In such a case an integrated [[w:tranceiver]] would be optimal.
    *The device could have within it a [[general purpose scanner]]. This could be used to read the bar-code or the numeric representation directly.  The usefulness of having a small (4-5mm width) general purpose scanner embedded in your phone is apparrent:
    **Scanning business cards or [[frequent buyer card]]s
    **Scanning the telephone book
    **Making a quick note of a newspaper article or just-off-the-press quaterly report
    **Storing open hours, addresses, contact info from adverts
    **With advanced enough reading techonology the scanner could be adapted to read straight off a CRT or TFT display
     
    *The device could have a dedicated [[barcode scanner]] - ideal for [[Consumerium usability at point of sale]].  It would boost speed and precision of using Consumerium and possibly other [[healthy signal infrastructure]] services.
     
    However this doesn't seem one of the likeliest gadgets to be integrated into a mobile phone, unless [[Consumerium Service access]] on the move becomes itself a major selling feature.  So, it's more likely to be an adjunct device such as:
     
    *The [[Bluetooth]] [[barcode]] [[scanner]]s with [[CCD]] and [[Laser]] reading which are available from the folks that brought out the First Ever [[Bluetooth]] [[Barcode]] [[Scanner]], The [[Baracoda Pencil]], by [http://www.baracoda.com Baracoda Wireless Technologies], which will play a major role in the ease-of-use of Consumerium.
     
    In addition it is possible that the [[barcode]] could be succeeded by other technology at the [[retail shelf]] at some point:
     
    *Adaptation of [[Near Field Communication]] Technology is of very high interest in making [[product identification]] a snap by embedding NFC-devices into the shelf.
     
    *There are reports saying that [[RFID]] (Radio Frequency IDentification) might be surpassing bar codes even in retail stores as a means of product identification. In such a case an integrated [[w:transceiver]] would be optimal.
    ----
    ----
    ===2. Store's infrastructure's requirements===


    The store must provide the following hardware in order to start providing the Consumerium-service to their clients
    ==[[Friendly retail]] store's infrastructure's requirements==
     
    A store that wishes to support [[Consumerium Services]] directly, e.g. seeking a strategic advantage like the [[Big Carrot]] or equivalents in other cities, must provide some hardware in order to start providing the Consumerium-service to their clients.  This might include a very low overhead [[in-store radio]] system to carry what amount to positive [[advertising]] for desirable [[green light]] products.  Or, it might be a higher tech solution:


    *Wireless network (Bluetooth), so that consumers can connect to the system with their terminals.
    *Wireless network (Bluetooth), so that consumers can connect to the system with their terminals.
    Line 36: Line 61:
    *Internet access, so that information can be fetched from outside of the  store's own datasystem and to deliever the consumer's feedback to the producers.
    *Internet access, so that information can be fetched from outside of the  store's own datasystem and to deliever the consumer's feedback to the producers.


    *Servers that contain the data about products sold in the store. To save costs it makes sense that retail chains place the data about products that are sold in all stores on it's central servers and then cache the data onto the store servers whenever it's requested.
    *[[Consumerium server]] software that contain the data about products sold in the store. To save costs it makes sense that retail chains place the data about products that are sold in all stores on it's central servers and then cache the data onto the store servers whenever it's requested.
     
    *One possibility for providing the needed core-servers for the system, is to require in the software-license that the retail chains that wish to provide Consumerium-service to their clients must provide a certain amount of host and network capacity (to store, process and transfer information that is not in the store's servers) This capacity could be bound to eg. the amount of floor space, parking lots or customers in the store, or some other scheme specified in the [[Consumerium License]].  Optional hardware for the stores might include:


    *One possibility for providing the needed core-servers for the system, is to require in the software-licence that the retail chains that wish to provide Consumerium-service to their clients must provide a certain amount of server and network capasity (to store, process and transfer information that is not in the store's servers) This capasity could be bound to eg. the amount of floor space, parking lots or customers in the store.
    *Mounted [[Bluetooth|Bluetooth keyboards]] so that consumers can better send [[feedback]] and otherwise interact with the system.
    ----
    ----
    ===3. Requirements of the Consumerium-information system===
    ==Requirements of the Consumerium-information system==
    *Servers that contain the data inserted into the system and references to documents (external docoments) outside of databases, scattered around the Internet and of course network connections for the servers.
    *Servers that contain the data inserted into the system and references to documents (external docoments) outside of databases, scattered around the Internet and of course network connections for the servers.


    *Software for the servers will be assembled from other [[Interesting projects|open source projects]]. What doesn't exist already will be coded by the project-team.
    *Software to integrate with the servers will be assembled from other [[Interesting projects|open source projects]]. What doesn't exist already will be coded by the project-team.
     
    At this early stage it is unclear how we will arrange the needed hosts, network connections and software.  This costs money, so sources of financing are needed, see [[healthy signal infrastructure]] for how that might be managed, especially the [[self-funding]] requirement.
     
    If hosts are [http://www.opennic.unrated.net/personal.html personal computers running OpenNIC] then they will be cheap, interchangeable, and be able to read data sources banned by [[The Empire]].  If the Empire tears one up, the data can move to another one.  This is probably part of [[Distributed Consumerium]], a later phase of the project.
     
    ----
    == low-volume-product [[Advertisement Video|video advertisement]] production==
     
    *A DV camera
    *A computer with video editing software or professional DV edit station
    *Video Encoder for the formats supported by consumers terminal


    At this early stage it is unclear how we will arrange the needed servers. Network connections and servers cost money, so sources of financing are needed, but describing this is not the goal of this document.  If these are [http://www.opennic.unrated.net/personal.html personal computers running OpenNIC] then they will be cheap, interchangeable, and be able to read data sources banned by [[The Empire]].  If the Empire tears one up, the data can move to another one.
    ----
    ----
    ===4. Miscellaneous notes on Hardware===
    == Other Hardware that could be integrated ==


    * [http://www.skannerz.com Skannerz] Have you perhaps seen adverts for this toy called "Skannerz". The basic idea is to scan [[barcode]]s from [[product]]s that translate to some kind of monsters and then you connect your toys to each other and fight with the monsters ... or something. It'd be interesting to know what these gadgets cost. Sold in Walmart, K-mart and some other stores.
    * [http://www.skannerz.com Skannerz] Have you perhaps seen adverts for this toy called "Skannerz". The basic idea is to scan [[barcode]]s from [[product]]s that translate to some kind of monsters and then you connect your toys to each other and fight with the monsters ... or something. It'd be interesting to know what these gadgets cost. Sold in Walmart, K-mart and some other stores.
    Line 54: Line 91:


    :I wonder how much it would cost to put a small scanner on a cell phone. It'd be really useful for inputting phone numbers, addresses straight from the phone book or some newspaper. Or making notes from just released [[quaterly report]]s. Or reading some [[GTIN]] code :)
    :I wonder how much it would cost to put a small scanner on a cell phone. It'd be really useful for inputting phone numbers, addresses straight from the phone book or some newspaper. Or making notes from just released [[quaterly report]]s. Or reading some [[GTIN]] code :)
    [[Category:Technology]]
    [[Category:Hardware]]

    Latest revision as of 19:23, 12 April 2021

    See also e-waste, protocol requirements, software requirements and (especially) performance requirements.

    This article is from 2004-2005 and describes hardware from that perspective

    Hardware requirements of the Consumerium project[edit | edit source]

    Hardware requirements arise from several functions in the network. Read Consumerium Service access for the full range of access requirements.

    1. Requirements of consumer terminal, typically a worn device
    2. Friendly retail infrastructure's requirements, e.g. retail shelf, checkout counter
    3. Computer hardware requirements of the Consumerium server software.
    4. low-volume product ad product
    5. additional hardware that could be integrated

    We'll describe each case in detail. Note Consumerium maintenance must deal with keeping all this junk running, so the less of it there is, the better!


    Consumer's terminal device(s)[edit | edit source]

    Consumer's terminal is usually a worn device carried in the consumers pocket or hand bag. It might be a PDA with suitable wireless networking ability but is more likely a cell phone with a headset attached. All serious cell phones have a headset jack. This should be the minimum required hardware. There is also potential to use a walkman style FM radio receiver to deliver the Consumerium buying signal in some cases. This is optimal as no ewaste is created by "requiring" advanced devices.

    However, we might assume that these existing delivery devices will not satisfy all Consumerium Service access requirements, e.g. for mobile purchasing agents applying institutional buying criteria. It might further be assumed that markets will direct development into such a state that in approximately the year 2005 there will be on the mass market a mobile phone that offers the following features:

    • Short-range wireless network technology built-in. Our presumption is that this technology is Bluetooth(tm). Bluetooth v1.1 can network devices without revealing the device's identity (BD_ADDR in the case of Bluetooth)�to other parties. This anonymity is an unconditional requirement for a networking technology suitable for Consumerium because if the user's identity or his/her terminal's identity were to be exposed to the merchant, it would be possible to gather data about the consumer's behaviour and tastes without his/her permission and knowledge, and to utilize this data in target marketing or pricing.� This would help retail management and brand management, but at too high a price for the consumer privacy in our view. There is usually some privacy risk with new networking technology.
    • A programming environment that is open to developers, so that Consumerium's Consumer Agent or one component of it can be installed on the phone to fully participate in a healthy buying infrastructure and possibly later a more general healthy signal infrastructure. The w:J2ME platform based on Java seems at first glance to have all the right features on paper, but Python is also now gaining a broad support among phone manufacturers. It is reported by Nokia that 11 lines of Python can replace 1000 lines of C++. Perhaps however this is very good Python and very bad C++?

    The features described above are the only features that would enhance the consumer terminal. To enhance the usability of the system, consider:

    • A built-in digital camera, e.g. as on the Nokia 7650 and 3650 models, with VGA resolution cameras. The focusing and resolution properties of the phones were maybe just a little bit too poor that one could use the pictures to barcode scan the numerical representation of EAN-codes (barcodes). But it came very close, so hopes are high that OCRing the code will be possible in the near future. OCR could alternatively be done from retail shelf tags, which usually contain the product name in a fairly big font with uniform typeface. Also using image recognition of the packaging graphics, e.g. for brand logos and standard labels may be possible.
    Update: There is now available an additional lense package (CC-49) for Nokia 3650 that snaps in place of the rear cover offering lenses for focusing to 10 and 5 centimeter distances in addition to the standard 30cm to infinity focusing, which would be just the thing. Unfortunately the Nokia models don't enable TCP/IP traffic over Bluetooth - it is quite common to find such limits built into phones as part of a planned obsolescence strategy. One of the more important Consumerium goals is to avoid such junk to cut e-waste.
    • The device could have within it a general purpose scanner. This could be used to read the bar-code or the numeric representation directly. The usefulness of having a small (4-5mm width) general purpose scanner embedded in your phone is apparrent:
      • Scanning business cards or frequent buyer cards
      • Scanning the telephone book
      • Making a quick note of a newspaper article or just-off-the-press quaterly report
      • Storing open hours, addresses, contact info from adverts
      • With advanced enough reading techonology the scanner could be adapted to read straight off a CRT or TFT display

    However this doesn't seem one of the likeliest gadgets to be integrated into a mobile phone, unless Consumerium Service access on the move becomes itself a major selling feature. So, it's more likely to be an adjunct device such as:

    In addition it is possible that the barcode could be succeeded by other technology at the retail shelf at some point:

    • There are reports saying that RFID (Radio Frequency IDentification) might be surpassing bar codes even in retail stores as a means of product identification. In such a case an integrated w:transceiver would be optimal.

    Friendly retail store's infrastructure's requirements[edit | edit source]

    A store that wishes to support Consumerium Services directly, e.g. seeking a strategic advantage like the Big Carrot or equivalents in other cities, must provide some hardware in order to start providing the Consumerium-service to their clients. This might include a very low overhead in-store radio system to carry what amount to positive advertising for desirable green light products. Or, it might be a higher tech solution:

    • Wireless network (Bluetooth), so that consumers can connect to the system with their terminals.
    • Internet access, so that information can be fetched from outside of the store's own datasystem and to deliever the consumer's feedback to the producers.
    • Consumerium server software that contain the data about products sold in the store. To save costs it makes sense that retail chains place the data about products that are sold in all stores on it's central servers and then cache the data onto the store servers whenever it's requested.
    • One possibility for providing the needed core-servers for the system, is to require in the software-license that the retail chains that wish to provide Consumerium-service to their clients must provide a certain amount of host and network capacity (to store, process and transfer information that is not in the store's servers) This capacity could be bound to eg. the amount of floor space, parking lots or customers in the store, or some other scheme specified in the Consumerium License. Optional hardware for the stores might include:

    Requirements of the Consumerium-information system[edit | edit source]

    • Servers that contain the data inserted into the system and references to documents (external docoments) outside of databases, scattered around the Internet and of course network connections for the servers.
    • Software to integrate with the servers will be assembled from other open source projects. What doesn't exist already will be coded by the project-team.

    At this early stage it is unclear how we will arrange the needed hosts, network connections and software. This costs money, so sources of financing are needed, see healthy signal infrastructure for how that might be managed, especially the self-funding requirement.

    If hosts are personal computers running OpenNIC then they will be cheap, interchangeable, and be able to read data sources banned by The Empire. If the Empire tears one up, the data can move to another one. This is probably part of Distributed Consumerium, a later phase of the project.


    low-volume-product video advertisement production[edit | edit source]

    • A DV camera
    • A computer with video editing software or professional DV edit station
    • Video Encoder for the formats supported by consumers terminal

    Other Hardware that could be integrated[edit | edit source]

    • Skannerz Have you perhaps seen adverts for this toy called "Skannerz". The basic idea is to scan barcodes from products that translate to some kind of monsters and then you connect your toys to each other and fight with the monsters ... or something. It'd be interesting to know what these gadgets cost. Sold in Walmart, K-mart and some other stores.
    • Search for "Translator Pen" on Google turned up the following http://www.tvdate.com/translator/qt/ for about 168$/piece. I've seen these advertised on TV-shopping channel quite sometime ago but somehow failed to mention these. Contains Scanner, OCR, Display, Memory, Processor, Data and Some UI and of these the only thing not in Mobile Phones at the moment is the Scanner.
    I wonder how much it would cost to put a small scanner on a cell phone. It'd be really useful for inputting phone numbers, addresses straight from the phone book or some newspaper. Or making notes from just released quaterly reports. Or reading some GTIN code :)