GB2376673A

GB2376673A - Packaging for programmable electronic devices

Info

Publication number: GB2376673A
Application number: GB0114449A
Authority: GB
Inventors: Steven Evans
Original assignee: Roke Manor Research Ltd
Current assignee: Roke Manor Research Ltd
Priority date: 2001-06-14
Filing date: 2001-06-14
Publication date: 2002-12-24
Anticipated expiration: 2021-06-14
Also published as: GB2376673B; WO2002103700A1; GB0114449D0

Abstract

A business method for producing electronic devices involves manufacturing the devices 100 and packaging them whilst software 110 is still being developed, then the software is loaded onto the devices at the latest time before shipment. To do this, the packaging 120 for the device is constructed so that it contains an interface 150 which connects to the programming port of the device which may be a mobile telephone. Typically this interface may be made from wires or printed conductive ink, alternately it may use an induction coil, electric or magnetic fields, or optical means. A programming device 130 adapted to be used with the system is also envisaged, as is large packaging crate for holding groups of the individual packages which further contains an interface between the box and the individual packages, such that the programmer may send information to the crate which relays it to the packages.

Description

IMPROVEMENTS IN PACKAGING The present invention relates to improved packaging, more specifically to improved packages for electronic equipment.

Typical electronic devices, or devices containing electronic sub-systems include both hardware and software elements. All of these devices are encompassed by the term"electronic devices"as used in this application. Many modern electronic devices are very dependent upon their software components to determine their functionality.

Consumer electronic devices, in particular, are very sensitive to time-tomarket. That is, the manufacturer who can introduce a product first is likely to gain a greater market share than another manufacturer entering the market later with a competing, possibly superior, product.

There is therefore great pressure on manufacturers of electronic devices to develop product quickly, and to bring the product to market in the shortest time possible.

Fig. 1 shows a typical development cycle of an electronic product. Stages 10 and 20 respectively represent the existing hardware and software from one or more previous products or designs. If the development in question is beginning truly from scratch, this stage may be empty. Such a scenario is rare, however, as almost all new products are a development of an existing or previous product.

Once a new product development begins, hardware design (step 11) and software design (step 21) may begin approximately simultaneously, in an attempt to reach market as soon as possible. Hardware design (stage 11) is followed by hardware test (stage 12). There may be one or more further iterations of hardware design, depending on the outcome of the hardware test. Meanwhile, software design 21 continues until, when hardware testing is complete, the software is loaded into the hardware at the integration step 30.

Integration 30 provides the first opportunity for the hardware and software elements of the product to be tested simultaneously. As a result of this test, some 'bugs'may be detected, that is, faults in the software. In addition, faults may be identified with the hardware which may be corrected by suitable amendments to the software. In either case, a process of software patching or'bug-fix'22 will take

place, in that an amended version of the software is prepared to correct any defects identified at the integration stage 30.

Once hardware testing is complete, and any software patch required to correct defects is complete, the amended version of the software is loaded into the tested hardware at the manufacturing stage 40, where mass production of the final product takes place. The products are packaged, and distributed in stage 50. The products are then sold, stage 60, via wholesale, retail or trade outlets.

Difficulties arise with this method of product development, and some of those difficulties are now described.

Time can be added to the development programme to allow for sufficient bug-fixing (software patching) prior to mass manufacture. This delays the product's entry to market and can be a serious problem for establishing the product in the market place. Delay in product launch usually directly results in loss of market share.

Alternatively, the product may be manufactured 50 without a full bug-fix, with revised products, which have a complete bug-fix, being marketed later. This causes difficulty in that the first product to market 60 may not be fully functional, but it is this early product which will determine whether the manufacturer gains a share of the market. A non-fully functional version of a certain product may well be less favoured than a fully functional version of a competing product of inferior design. The non-fully functional version may offer reduced features, and it may be necessary to recall some product, if a serious defect is discovered, destroying the reputation of the product and tarnishing the reputation of the manufacturer in the relevant market. The release of a fully functional version of the superior design at a later date may well be too late to gain market share, as the product's reputation will be determined by the first version of the product to reach the market.

While some products have successfully employed after sales software or firmware updates, this is usually only successful for large and/or specialist equipment, as the consumer must ensure that updates are received and used appropriately. This may involve returning the product to the manufacturer, or obtaining updated software over the internet, for example. Such upgrading methods are unsuitable for mass produced articles such as mobile telephones, since the

individual user may not bother to obtain the upgrades, or may not be prepared to return their product to the manufacturer if they do not perceive any problem with the product in its original state. The product will, however, remain less functional than the designer intended, and the consumer's opinion of the product will correspondingly be reduced.

Upgrading software/hardware after manufacture but before reaching the consumer is rendered economically impossible, not least because of the packaging required, particularly for mass-market consumer applications. Supposing a revised version of operating software has been developed for a particular mobile telephone.

Although the manufacturer may have large quantities in a warehouse awaiting distribution, it would be uneconomic to unpackage each device, connect it to a programming tool and reprogramme the software. Therefore, even though improved software may be available, it may be quite some time before the improved software reaches the consumer, as all of the stocks of the previous version need to be sold first. This means that sub-optimal product is being sold, which is bad for the image of the product and for the market share of the product and of the manufacturer.

There are therefore conflicting requirements of ensuring that a new product reaches the market as quickly as possible, yet allowing software upgrades to be made as extensively as possible before the product reaches the consumer.

The present invention accordingly provides methods and apparatus as defined in the appended claims.

The present invention accordingly provides a package for a programmable device, comprising means for accessing a programming port of such device from the exterior of the package. The package may further comprise means for supplying power to such device from the exterior of the package.

The package may comprise a connector for connecting such device with the means for accessing and/or the means for supplying power.

At least one path may be provided, each path terminating at one end at an interface for receiving software and/or a power supply from an external source, and terminating at the other end at a location suitable for connection to such programming port of such device. Each path may be an electrically conductive

path. The conductive path (s) may comprise wires. Alternatively, the conductive path (s) may comprise patterns of conductive ink printed on the material of the package.

The interface may comprise electrically conductive pads exposed to the exterior of the package, each pad being respectively connected to at least one of the conductive paths. Alternatively, the interface may comprise an induction coil, connected to transfer data from an external source to such device. Alternatively, the interface may comprise a microphone or other sonic receptor arranged to receive audio or sonic signals representing software to be transferred to such device, said interface being connected to transfer data from an external source to such device.

Alternatively, the interface may comprise an optical receptor arranged to receive optical signals representing software to be transferred to such device, said interface being connected to transfer data from an external source to such device.

Alternatively, the interface may comprise a receptor arranged to receive signals in the form of electric or magnetic field strengths, said signals representing software to be transferred to such device, said interface being connected to transfer data from an external source to such device.

In any such package, a smartcard may be is included in communication with such device and with the exterior of the package. The smartcard is preferably in communication with the exterior of the package through the interface. The smartcard may include a storage area for the temporary storage of revised software during transfer between an external source and such device. The smartcard may include a download control device, to control the transfer of revised software between an external source and such device. The smartcard may comprise one or more of security means and verification means for ensuring the authenticity and integrity of the software to be supplied to such device.

The present invention also provides a storage means for storing a plurality of packages as described, wherein the storage means comprises a corresponding plurality of respective interfaces for transferring software to each of the packages, and at least one interface for receiving software from a programming device.

The present invention also provides a programming device for use with a package or a storage means as described, said programming device comprising an

interface for producing signals representing software to be transferred to such device, in a format suitable for reception by the interface of the package.

The present invention also provides a method of product development and distribution, comprising the steps of: (a) designing a hardware portion of the product; (b) designing a software portion of a product; (c) testing the hardware portion; (d) integrating the software portion into the hardware portion; (e) manufacturing the product; and (f) packaging the product, in which step (d) is performed after all of the other steps have been completed.

The method may further comprise the step of : (g) distributing the packaged product. Preferably, step (d) is performed after step (g).

Steps (b) and (d) may each be performed in at least two stages, comprising

the sub-steps of : (i) prior to step (f), - (bl) designing a first version of the software ; - (dl) integrating the first version of the software into the product; and (ii) after step (f),

- (b2) designing a second version of the software ; - (d2) integrating the second version of the software into the product.

Step (b2) may be performed contemporaneously with step (e).

The foregoing, and further, aims, characteristics and advantages of the present invention will be apparent with reference to the following description of certain embodiments thereof, described by way of example only, in conjunction with the appended drawings, wherein: Fig. 1 shows a conventional product development cycle; Fig. 2 shows an improved product development cycle according to as aspect of the present invention;

Fig. 3 shows a programming system according to an embodiment of the present invention, including a package according to an embodiment of the present invention; and Fig. 4 shows a programming system according to an embodiment of the present invention, including a package according to another embodiment of the present invention.

According to an aspect of the present invention, software modifications may be made to the product after packaging and even after distribution. This allows development cycles to be shortened without reducing the features available from the product, without reducing quality and without increasing the overall time to market.

According to an aspect of the present invention, products may be programmed through their packaging, to receive amended or replacement software. Products may even be packaged without software, and appropriate software could be loaded just before sale, possibly even at the point of sale. This would allow many different versions of a software to be made available, for different markets or different service levels within a market, without the manufacturer or distributor needing to maintain stocks of every possible variant of the product.

The invention allows software updates, that is, improvements which are not necessarily needed to overcome defects, but rather provide an enhanced product, without removing the product from its packaging, allowing updates to be made after manufacture, after packaging or even after distribution.

According to a further aspect of the present invention, specialised storage means such as crates are provided. Numerous packaged products are stored within the storage means, and the storage means comprises means for allowing a software of each product to be loaded or modified without the need for the product to be removed from the storage means.

Fig. 3 shows an arrangement according to an embodiment of the present invention. A product 100 containing software 110 is held within a package 120. As discussed above, the invention allows software 110 to be modified without interfering with the packaging. A programming device 130, external to packaging 120, contains a software patch or replacement software, 140. According to an aspect of the present invention, the software 140 may be transferred along a path

150 from the programming device 130 to the product 100. Examples of path 150 will be discussed below. An identical, or possibly different, reprogramming operation may then be applied to second or further packaged product (s) 220.

Path 150 flows from the programming means 130 through the packaging 120 to the product 100. For example, conductive wires may be connected to an access port of the product, to conductive pads on the outside of the package. By bringing probes or similar into contact with the conductive pads, path 150 may be completed. A connector may be provided to link the product with the wires, and such connector may need to be removed by the consumer when unpacking the product. Preferably, the connector is integrated into the packaging such that the connector is automatically removed from contact with the product as the product is unpacked, without the consumer having to perform a specific operation to remove the connector. Some or all of the wires associated with the packaging may be replaced by a conductive ink printed on the packaging. In these embodiments, power may be supplied to the product by simply applying appropriate voltages to selected conductive pads.

In an alternate embodiment, an induction coil is provided within the packaging and comprises at least one of a wire coil, and a pattern printed in conductive ink on the packaging. A complementary induction coil may then be provided in association with the programming means 130, so that electrical induction may be used to supply power to the product and also to supply the amended software.

The effect of each of these embodiments is to allow a programming port on the product to be made available externally, together with providing a power supply to the product to enable it to store the new software as required.

Fig. 4 illustrates an enhanced embodiment of the invention, in which a smart card 200 is provided within the packaging, located in path 150 between the product 100 and the programming device 130. Smart card 200 may be connected to the product 100 by any suitable connection 230, such as a ribbon cable, other forms of wires, or printed conductive ink. The product may be connected to such connection 230 by a connector as discussed above or any other suitable means. The smart card 200 may be connectable to the programming device 130 by conductive wires or ink

connected to conductive pads on the outside of the package, or an induction coil may be provided within the packaging and comprises at least one of a wire coil, and a pattern printed in conductive ink on the packaging. A complementary induction coil may then be provided in association with the programming means 130, so that electrical induction may be used to supply power and also the amended software to the smart card 200 and thence to the product 100.

Although the term"smart card"itself has a fairly specific definition-that is, of an integrated circuit packaged into a thin, card-like package usually many times larger than the integrated circuit, the term as used herein should not be limited to such products. Rather, the term as used herein encompasses any suitably protected and connected circuitry able to perform the functions described herein.

The smart card 200 itself may include a storage area 240 for the temporary storage of the revised software 140 during transfer between programming device 130 and product 100. A download control device 250 may be provided within the smartcard, to control the software download operation. The introduction of a smart card to control the software transfer allows advanced features to be added, such as security, buffering and verification. These functions would all help to ensure a controlled and flexible programming process, and ensure that only authorised software is applied to the product. In the absence of security features, a third party software producer could apply unauthorised software to the product, potentially compromising final product quality.

As briefly discussed above, storage means such as crates may be provided which comprise means for allowing a software of each product to be loaded or modified without the need for the product to be removed from the storage means.

For example, a crate may be provided with a network of conductive paths, arranged to connect to the respective conductive pads of each package, and with a port for connection to the programming device to allow a single programming device to rapidly programme many products. By analogy, the storage means, such as a crate, may be provided with induction coils at relevant locations for transferring

the required amended software to each package by induction. Similar arrangements can easily be designed for other types of data communication to the packaged products, for example by electric or magnetic fields or by optical means such as fibre optics.

Programming of the products may be done simultaneously, with the programming device transferring a new version of the software only once, and with all products simultaneously receiving a the same version of software. This allows rapid programming of a large number of products. Alternatively, the programming device may access individual products, or a subset of the products, by a polling mechanism, and transfer a revised software specifically to an individual product or subset of products. This process may need to be repeated until all products have received a revised software. With this version of the system, individual products may be customised by the application of a selected version of the software, perhaps at the request of the consumer or retailer, just before the products leave a distribution warehouse.

Fig. 2 illustrates an improved product development cycle according to an aspect of the present invention. While all stages up to and including integration 30 are unchanged, the present invention allows software patching or'bug fix'right up to the end of the distribution stage 50, as amendments to the software can be made while the packaged product is awaiting shipment to a retailer ; possibly, the revised software could be supplied to the retailer for application to his stock of product.

This enables at least one of the following beneficial effects. Firstly, product may be marketed very soon after'bug-fix'is complete, reducing the product's time-tomarket. Secondly, more time can be spent on revising software without impacting the time-to-market, meaning that a more thorough review of the software may be performed, perhaps avoiding the need to release a second version of the software after first marketing the product. This will also allow increased quality of the product reaching the consumer. Thirdly, the longer time available for software development may allow additional features to be added before first marketing of the product, allowing an improved product to be made available to consumers.

Alternatively, or in addition, the present invention allows the distribution stage 40 to commence earlier than would otherwise be possible. It accordingly

becomes possible to use slower, less costly distribution routes without adversely affecting the time-to-market, provided that the distribution route chosen allows software programming at the distribution stage.

While the present invention has been described with reference to a limited number of particular embodiments, it will be apparent to one skilled in the art that numerous modifications amendments and variations may be made without departing from the scope of the present invention as defined in the appended claims.

For example, one or more of many means of communicating software through the packaging may be used, such as magnetic or electric fields, optical signalling such as fibre optic communication, radio or microvave communication to an appropriate receiver in the package, or even audio/sonic transmissions to be received by a microphone or other sound sensor located on or in the packaging.

Claims

CLAIMS : 1. A package for a programmable device, comprising means for accessing a programming port of such device from the exterior of the package.
2. A package according to claim 1 further comprising means for supplying power to such device from the exterior of the package.
3. A package according to claim 1 of claim 2, comprising a connector for connecting such device with the means for accessing and/or the means for supplying power.
4. A package according to any preceding claim in which at least one path is provided, each path terminating at one end at an interface for receiving software and/or a power supply from an external source, and terminating at the other end at a location suitable for connection to such programming port of such device.
5. A package according to claim 4 wherein each path is an electrically conductive path.
6. A package according to claim 5 wherein the conductive path (s) comprise wires.
7. A package according to claim 5 wherein the conductive path (s) comprise patterns of conductive ink printed on the material of the package.
8. A package according to any of claims 5-7 wherein the interface comprises electrically conductive pads exposed to the exterior of the package, each pad being respectively connected to at least one of the conductive paths.
9. A package according to any of claims 5-7 wherein the interface comprises an induction coil, connected to transfer data from an external source to such device.

<Desc/Clms Page number 12>
10. A package according to any of claims 5-7 wherein the interface comprises a microphone or other sonic receptor arranged to receive audio or sonic signals representing software to be transferred to such device, said interface being connected to transfer data from an external source to such device.
11. A package according to any of claims 5-7 wherein the interface comprises an

optical receptor arranged to receive optical signals representing software to be 0 transferred to such device, said interface being connected to transfer data from an external source to such device.
12. A package according to any of claims 5-7 wherein the interface comprises a receptor arranged to receive signals in the form of electric or magnetic field strengths, said signals representing software to be transferred to such device, said interface being connected to transfer data from an external source to such device.
13. A package according to any preceding claim, wherein a smartcard is included in communication with such device and with the exterior of the package.
14. A package according to claim 4 and claim 13 wherein the smartcard is in communication with the exterior of the package through the interface.
15. A package according to claim 13 or claim 14 wherein the smartcard includes a storage area for the temporary storage of revised software during transfer between an external source and such device.
16. A package according to any of claims 13-15 wherein the smartcard includes a download control device, to control the transfer of revised software between an external source and such device.
17. A package according to any of claims 13-16 wherein the smartcard comprises one or more of security means and verification means for ensuring the authenticity and integrity of the software to be supplied to such device.

<Desc/Clms Page number 13>
18. A storage means for storing a plurality of packages as recited in any preceding claim, wherein the storage means comprises a corresponding plurality of respective interfaces for transferring software to each of the packages, and at least one interface for receiving software from a programming device.
19. A programming device for use with a package or a storage means according to z : l any preceding claim, said programming device comprising an interface for z : l producing signals representing software to be transferred to such device, in a format suitable for reception by the interface of the package.
20. A method of product development and distribution, comprising the steps of : (a) designing a hardware portion of the product ; (b) designing a software portion of a product; (c) testing the hardware portion; (d) integrating the software portion into the hardware portion; (e) manufacturing the product; and (f) packaging the product, characterised in that step (d) is performed after all of the other steps have been completed.
21. A method according to claim 20 further comprising the step of: (g) distributing the packaged product.
22. A method according to claim 21 wherein step (d) is performed after step (g).
23. A method according to any of claims 20-22 wherein steps (b) and (d) are each performed in at least two stages, comprising the sub-steps of: (i) prior to step (f), - (bl) designing a first version of the software; - (dl) integrating the first version of the software into the product; and (ii) after step (f),

<Desc/Clms Page number 14>

- (b2) designing a second version of the software; - (d2) integrating the second version of the software into the product.
24. A method substantially as described herein and/or as illustrated in Fig. 2 of the accompanying drawings.

24. A method according to claim 23 wherein step (b2) is performed contemporaneously with step (e).

25. A package substantially as described herein and/or as illustrated in Figs 3-4 of IZ > the accompanying drawings.

26. A storage means substantially as described herein.

27. A method substantially as described herein and/or as illustrated in Fig. 2 of the accompanying drawings.

<Desc/Clms Page number 15>

Amendments to the claims have been filed as follows CLAIMS :

1. Packaging for a programmable device, comprising at least one path terminating at one end at an interface for receiving software and/or a power supply from an external source, and terminating at the other end at a location suitable for connection to a programming port of such device.

2. Packaging according to claim 1, comprising a connector for connecting such device with the path.

3. Packaging according to any preceding claim wherein each path is an electrically conductive path.

4. Packaging according to claim 3 wherein the conductive path (s) comprise wires.

5. Packaging according to claim 3 wherein the conductive path (s) comprise patterns of conductive ink printed on the material of the packaging.

6. Packaging according to any of claims 3-5 wherein the interface comprises electrically conductive pads exposed to the exterior of the package, each pad being respectively connected to at least one of the conductive paths.

7. Packaging according to any of claims 3-5 wherein the interface comprises an induction coil, connected to transfer data from the external source to such device.

8. Packaging according to any of claims 3-5 wherein the interface comprises a microphone or other sonic receptor arranged to receive audio or sonic signals representing software to be transferred to such device, said interface being connected to transfer data from the external source to such device.

<Desc/Clms Page number 16>

9. Packaging according to any of claims 3-5 wherein the interface comprises an optical receptor arranged to receive optical signals representing software to be transferred to such device, said interface being connected to transfer data from the external source to such device.

10. Packaging according to any of claims 3-5 wherein the interface comprises a receptor arranged to receive signals in the form of electric or magnetic field strengths, said signals representing software to be transferred to such device, said interface being connected to transfer data from the external source to such device.

11. Packaging according to any preceding claim, wherein a smartcard is included in communication with such device and with the exterior of the packaging.

12. Packaging according to claim 11 wherein the smartcard is in communication with the exterior of the package through the interface.

13. Packaging according to claim 11 or claim 12 wherein the smartcard includes a storage area for the temporary storage of revised software during transfer between an external source and such device.

14. Packaging according to any of claims 11-13 wherein the smartcard includes a download control device, to control the transfer of revised software between an external source and such device.

15. Packaging according to any of claims 11-13 wherein the smartcard comprises one or more of security means and verification means for ensuring the authenticity and integrity of the software to be supplied to such device.

16. A storage means for storing a plurality of programmable devices, each in packaging as recited in any preceding claim, wherein the storage means comprises a corresponding plurality of respective interfaces for transferring software to each of

<Desc/Clms Page number 17>

the programmable devices, and at least one interface for receiving software from a an external device.

17. An external device for use with packaging or a storage means according to any preceding claim, said external device comprising an interface for producing signals representing software to be transferred to such programmable device, in a format suitable for reception by the interface of the packaging.

18. A method of producing a packaged progammable device having hardware and software portions, comprising the steps of: (a) integrating the software portion into the hardware portion ; (b) manufacturing the device ; and (c) packaging the device, characterised in that: - step (c) comprises packaging the device in packaging according to any of claims 1-15 ; and in that - step (a) is performed after all of the other steps have been completed.

19. A method according to claim 18 further comprising the step of: (d) distributing the packaged product.

20. A method according to claim 19 wherein step (a) is performed after step (d).

21. A method according to any of claims 18-20 wherein step (a) is performed in at least two stages, comprising the sub-steps of: (i) prior to step (c), - (al) integrating a first version of the software into the product ; and (ii) after step (c), - (a2) integrating a second version of the software into the product.

22. Packaging substantially as described herein and/or as illustrated in Figs 3-4 of the accompanying drawings.

<Desc/Clms Page number 18>

23. A storage means substantially as described herein.