Hardware Requirements: Difference between revisions

''See also [[e-waste]], [[protocol requirements]] and [[software requirements]].''

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

#Requirements of [[consumer terminal]], typically a [[worn device]]

#[[Friendly retail]] infrastructure's requirements, e.g. [[retail shelf]], [[checkout counter]]

#[[Computer hardware]] requirements of the [[Consumerium server]] software.

#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!''

==Consumer's terminal device(s) ==

 

 

*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.

*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 ([[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]].

*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

*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:

*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==

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:

*[[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:

*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.

 

 

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==

== Other Hardware that could be integrated ==