Card reading device for service access

A read device (1) for reading an interface card (16). The card (16) is configured for insertion into the read device (1). The card (16) comprises indicia formed thereon and a memory having data stored therein for communicating with an external device (601, 700). The read device (1) comprises a substantially transparent touch sensitive membrane (8) arranged to overlay the interface card (16) upon receipt of the card (16) in the read device (1). The read device (1) also comprises a central processing unit (45) for sending a service identifier, a distinguishing identifier and a specific portion of the data to the external device (601, 700). The specific data is related to a user selected indicia (14). A service identified by the service identifier upon receipt of the data is provided via the external device (601, 700).

TECHNICAL FIELD OF THE INVENTION

The present invention relates to a control template or smart card for use with a remote reader device and, in particular, to a card interface system for providing a service. The invention also relates to a computer program product including a computer readable medium having recorded thereon a computer program for a card interface system.

BACKGROUND ART

Control pads of various types are known and used across a relatively wide variety of fields. Typically, such pads include one or more keys, buttons or pressure responsive areas which, upon application of suitable pressure by a user, generate a signal which is supplied to associated control circuitry.

Unfortunately, prior art control pads are somewhat limited, in that they only allow for a single arrangement of keys, buttons or pressure sensitive areas. Standard layouts rarely exist in a given field, and so a user is frequently compelled to learn a new layout with each control pad they use. For example, many automatic teller machines (“ATMs”) and electronic funds transfer at point of sale (“EFTPOS”) devices use different layouts, notwithstanding their relatively similar data entry requirements. This can be potentially confusing for a user who must determine, for each control pad, the location of buttons required to be depressed. The problem is exacerbated by the fact that such control pads frequently offer more options than the user is interested in, or even able to use.

Overlay templates for computer keyboards and the like are known. However, these are relatively inflexible in terms of design and require a user to correctly configure a system, with which the keyboard is associated, each time the overlay is to be used.

One known arrangement involves a smart card reading device intended for the remote control of equipment. Such, for example, allows a television manufacturer, to manufacture a card and supply same together with a remote control housing and a television receiver. A customer is then able to utilize the housing in conjunction with the card as a remote control device for the television receiver. In this manner, the television manufacturer or the radio manufacturer need not manufacture a specific remote control device for their product, but can utilize the remote control housing in conjunction with their specific card.

However, the above-described concept suffers from the disadvantage that control data stored upon the card and being associated with the apparatus to be controlled, comes from the manufacturer of the application and is thus limited in its application.

SUMMARY OF THE INVENTION

According to a first aspect of the present invention there is provided a read device for reading an interface card, said card being configured for insertion into said read device, wherein said card comprises indicia formed thereon and a memory having data stored therein for communicating with an external device, said read device comprising:

a substantially transparent touch sensitive membrane arranged to overlay said interface card upon receipt of said card in said read device,

a central processing unit for sending a service identifier, a distinguishing identifier and a specific portion of said data to said external device, said specific data being related to a user selected indicia, wherein a service identified by the service identifier upon receipt of said data is provided via said external device.

According to another aspect of the present invention there is provided a program configured for execution in a read device, said read device comprising a substantially transparent touch sensitive membrane arranged to overlay a removable interface card received therein, said card comprising a substrate and indicia formed on said substrate, said program comprising:

code for reading a service identifier, distinguishing identifier and a specific portion of data stored within a memory of said card, said specific data being related to a user selected indicia; and

code for a sending said identifiers and said specific data to an external device, whereby a service is provided by said external device, said service being identified by the service identifier.

According to still another aspect of the present invention there is provided a method of processing data on a read device, said read device comprising a substantially transparent touch sensitive membrane arranged to overlay a removable interface card, said card comprising a substrate with indicia formed thereon, said method comprising the steps of:

reading a service identifier, distinguishing identifier and a specific portion of data stored within a memory of said card, said specific data being related to a user selected indicia; and

sending said identifiers and said specific data to an external device, whereby a service is provided via said external device, said service being identified by the service identifier.

According to still another aspect of the present invention there is provided a read device for reading an interface card, said card comprising indicia formed thereon and a memory having data stored therein and being configured for insertion into said read device, said read device comprising:

substantially transparent touch sensitive means arranged to overlay said interface card upon receipt of said card in said read device,

read means for reading a service identifier, distinguishing identifier and a specific portion of data stored in the card, said specific data being related to user selected indicia; and

send means for sending said identifiers and said data to an external device, wherein a service is provided via said external device, said service being identified by the service identifier.

According to still another aspect of the present invention there is provided a card interface system comprising an interface card and a read device, said card being configured for insertion into said read device, and said card comprising at least a substrate with indicia formed thereon, said read device comprising a substantially transparent touch sensitive membrane arranged to overlay said card, said system comprising:

a memory being associated with said card and for storing a service identifier, distinguishing identifier and data related to a user selected indicia; and

a central processing unit integrally formed within said read device for sending said identifiers and said data to an external device in order that a user of said card receives a service via said external device, said service being identified by the service identifier.

According to still another aspect of the present invention there is provided an electronic card reader for reading an electronic card, said electronic card having at least one indicia formed thereon and an electronic memory having data stored therein for controlling data controlled equipment, said electronic reader comprising:

a touch sensitive substantially transparent membrane having an upper surface configured to be depressible by a user of said reader;

a receptacle shaped to receive said electronic card, wherein said electronic card received therein and said indicia can be viewed through said touch sensitive membrane; and

an electronic circuit coupled to said membrane to read a specific portion of said data from said memory according to depression of said membrane associated with a specific one of said indicia, and for sending said specific data together with a service identifier and a distinguishing identifier to said data controlled equipment, wherein a function is provided via said data controlled equipment depending upon said specific data, said function being associated with said service identifier.

According to still another aspect of the present invention there is provided a read device for an interface card, said card comprising a substrate having at least one indicia formed thereon, said read device comprising:

a receptacle shaped to receive said interface card;

a substantially transparent touch sensitive membrane arranged to overlay said interface card upon receipt of said interface card in said receptacle such that said indicia can be viewed through said touch sensitive membrane; and

an electronic circuit for coupling to a memory component of said interface card and for reading data related to one of said indicia selected by a user of said read device via said membrane, wherein said electronic circuit is configured to send said data together with a service identifier and a distinguishing identifier to an external device, wherein a service associated with said service identifier is provided via said external device upon receipt of said read data.

According to still another aspect of the present invention there is provided a program executable in an electronic card reader for reading an electronic card having data configured for controlling data controlled equipment, said electronic card having at least one indicia formed thereon and an electronic memory having said data stored therein, said reader having a touch sensitive substantially transparent membrane configured to be depressible by a user of said reader, wherein said electronic card and said indicia can be viewed through said touch sensitive membrane upon insertion of said card into said reader, said program comprising:

code for detecting a selection of one of said indicia upon depression of said touch sensitive membrane;

code for reading selected data from said memory according to said depression of said membrane associated with one indicia, said selected data comprising at least a service identifier, a distinguishing identifier and specific data associated with said one indicia;

code for sending said selected data to said data controlled equipment, wherein a function being provided via said data controlled equipment upon receipt of said selected data, said function being associated with said service identifier.

According to still another aspect of the present invention there is provided a read device having a substantially transparent touch sensitive membrane arranged to overlay a detachable interface card which comprises a substrate and indicia formed on said substrate, said device comprising:

a central processing unit for determining a validity of said card upon insertion of said card into said read device, and for sending a service identifier and data stored in the card to an external device, said data being related to a user pressed indicia, in order that a card user receives a service identified via said external device according to said pressed indicia.

According to still another aspect of the present invention there is provided a read device having a substantially transparent touch sensitive membrane arranged to overlay a detachable interface card which comprises a substrate and indicia formed on said substrate, said device comprising:

a central processing unit for determining a validity of said card upon insertion of said card into said read device, and for sending a service identifier and user press coordinates to an external device upon selection of at least one of said indicia utilizing said touch sensitive membrane, in order that a card user receives a service identified according to the service identifier.

According to still another aspect of the present invention there is provided a read device having a substantially transparent touch sensitive membrane arranged to overlay a detachable interface card, said card comprising a substrate and indicia formed thereon, said device comprising:

a central processing unit configured for distinguishing an identifier stored in said card and for sending a service identifier and user press coordinates to an external device, said coordinates representing a press position on said touch sensitive membrane to select at least one of said indicia, wherein said service identifier is based on a result of said distinction, and wherein a card user receives a service identified by said service identifier via said external device.

According to still another aspect of the present invention there is provided a read device having a substantially transparent touch sensitive membrane arranged to overlay a detachable interface card, said card comprising a substrate and indicia formed on said substrate, said device comprising:

a central processing unit configured for detecting a user press on said touch sensitive membrane and for sending touch coordinates corresponding to said user press to an external device, wherein said touch coordinates are used as cursor information.

According to still another aspect of the present invention there is provided a read device having a substantially transparent touch sensitive membrane arranged to overlay a detachable interface card inserted into said read device, said device comprising:

a central processing unit for reading information that affects functions that said card performs in said read device, and for performing the functions based on said information.

According to still another aspect of the present invention there is provided a read device having a substantially transparent touch sensitive membrane arranged to overlay a detachable interface card inserted into said device, said device comprising:

a central processing unit configured for generating a session identifier identifying a current session of a card insertion, said session identifier being a number incremented each time a card is inserted into said read device, said central processing unit being further configured for sending said session identifier to an external device in order to determine the validity of said inserted card.

According to still another aspect of the present invention there is provided a service providing apparatus for providing a service to a card user utilizing a card read device having a substantially transparent touch sensitive membrane arranged to overlay a detachable interface card inserted into said apparatus, said card comprising a substrate having indicia formed thereon, said apparatus comprising:

a central processing unit adapted for receiving, from said read device, a service identifier and user press coordinates corresponding to a press position on said membrane, and for matching said coordinates with data associated with at least one of said indicia in order to read at least a portion of said data corresponding to said coordinates from said service providing apparatus, said central processing unit being further adapted to provide said user with a service identified by said service identifier, said service being associated with said at least one indicia.

According to still another aspect of the present invention there is provided a service providing apparatus for providing a service to a card user utilizing a card read device having a substantially transparent touch sensitive membrane arranged to overlay a detachable interface card inserted into said apparatus, said card comprising a substrate with indicia formed thereon, said apparatus comprising:

a central processing unit adapted for matching user press coordinates corresponding to a press position on said membrane with data associated with at least one of said indicia in order to read at least a portion of said data corresponding to said coordinates from said service providing apparatus upon said apparatus receiving a service identifier and said coordinates from said read device, said central processing unit being further adapted to provide said user with a service identified by said service identifier, said service being associated with said at least one indicia.

According to still another aspect of the present invention there is provided a service providing apparatus for providing a service to a card user utilizing a card read device having a substantially transparent touch sensitive membrane arranged to overlay a detachable interface card inserted into said apparatus, said card comprising a substrate having indicia formed thereon, said apparatus comprising:

a central processing unit adapted for receiving, from said read device, user press coordinates corresponding to a press position on said membrane, and for matching said coordinates with data associated with at least one of said indicia in order to read at least a portion of said data corresponding to said coordinates from said service providing apparatus, said central processing unit being further adapted to provide said user with a service associated with said at least one indicia.

According to still another aspect of the present invention there is provided a service providing apparatus for providing a service to a card user utilizing a card read device having a substantially transparent touch sensitive membrane arranged to overlay a detachable interface card inserted into said apparatus, said card comprising a substrate having indicia formed thereon, said apparatus comprising:

a central processing unit adapted for matching user press coordinates with data corresponding to a press position on said membrane with data associated with at least one of said indicia in order to read at least a portion of said data corresponding to said coordinates from said service providing apparatus upon said apparatus receiving said coordinates from said read device, said central processing unit being further adapted to provide said user with a service associated with said at least one indicia.

Other aspects of the invention are also disclosed.

DETAILED DESCRIPTION INCLUDING BEST MODE

The arrangement disclosed herein has been developed primarily for use with remote control systems, automatic tellers, video game controllers, and network access and will be described hereinafter with reference to these and other applications. However, it will be appreciated that the invention is not limited to these fields of use.

For ease of explanation the following description has been divided into Sections 1.0 to 12.0, each section having associated subsections.

1.0 Card Interface System Overview

Referring toFIG. 1, there is provided a remote reader1, having a housing2which defines a card receptacle4and a viewing area6. Data reading means are provided in the form of exposed electrical contacts7and associated control circuitry (not shown). The remote reader1also includes sensor means in the form of a substantially transparent pressure sensitive membrane forming a touch panel8covering the viewing area6. The remote reader1disclosed herein has been described as having a substantially transparent pressure sensitive membrane forming the touch panel. However, it will be appreciated by one skilled in the art that alternative technology can be used as a substantially transparent touch panel. For example, the touch panel can be resistive or temperature sensitive. The remote reader1is configured for use with a user interface (UI) card, which, in the arrangement shown inFIGS. 1 to 3, takes the form of an electronic smart card10. The smart card10includes a laminar substrate12with various control indicia14in the form of a four way directional controller20, a “jump button”22, a “kick button”24, a “start button” and an “end button” printed on an upper face16thereof. Other non-control indicia, such as promotional or instructional material, can be printed alongside the control indicia. For example, advertising material26can be printed on the front face of the smart card10or on a reverse face27of the card10, as seen inFIG. 2.

As seen inFIG. 3, the smart card10includes storage means in the form of an on-board memory chip19for data associated with the control indicia. The smart card10also includes electrical data contacts18connected to the on-board memory chip19corresponding with the exposed contacts7on the remote reader1.

As again seen inFIG. 3, the upper face16may be formed by an adhesive label60upon which are printed control indicia64, in this case corresponding to the “End Button” and the “Right-arrow button” of the directional controller20. The label60is affixed to the laminar substrate12. In accordance with this arrangement, a home user can print a suitable label for use with a particular smart card10by using a printer, such as a color BUBBLE JET™ printer manufactured by Canon, Inc. Alternatively, the control indicia14can be printed directly onto the laminar substrate or separate adhesive labels can be used for each of the control indicia.

In use, the smart card10is inserted into the card receptacle4, such that the pressure sensitive touch panel8covers the upper face16of the smart card10. In this position, the control indicia are visible within the viewing area6through the transparent pressure sensitive touch panel8.

The exposed contacts7and associated circuitry of the reader1are configured to read the stored data associated with the control indicia14from the memory chip19, either automatically upon insertion of the smart card10into the control template receptacle4, or selectively in response to a signal from the remote reader1. This signal can, for example, be transmitted to the smart card10via the exposed contacts7and data contacts18.

Once the data associated with the control indicia24has been read, a user can press areas of the pressure sensitive touch panel8on or over the underlying control indicia14. By sensing the pressure on the pressure sensitive touch panel8and referring to the stored data, the remote reader1can deduce which of the control indicia14the user has selected. For example, if the user places pressure on the pressure sensitive touch panel8adjacent the “kick button”24, the remote reader1is configured to assess the position at which the pressure was applied, refer to the stored data, and determine that the “kick” button24was selected. This information can then be used to control an external device, for example, an associated video game console (of conventional construction and not shown).

It will be appreciated from above that the control indicia14are not, in fact buttons. Rather, the control indicia14are user selectable features which by virtue of their corresponding association with the mapping data and the function of the touch panel8, operate to emulate buttons traditionally associated with remote control devices.

In one arrangement, the remote reader1includes a transmitter (of conventional type and not shown), such as an infra-red (IR) transmitter or radio frequency (RF) transmitter, for transmitting information in relation to indicia selected by the user. In the arrangement shown inFIG. 1, the remote reader1incorporates an IR transmitter having the remote reader1has an IR transmitter having an IR light emitting diode (LED)25. Upon selection of one of the control indicia20,22,24,64, the remote reader1causes information related to the selection to be transmitted to a remote console (not shown inFIG. 1) where a corresponding IR receiver can detect and decode the information for use in controlling some function, such as a game being played by a user of the reader1.

Any suitable transmission method can be used to communicate information from the remote reader1to the remote console, including direct hard-wiring. Moreover, the remote console itself can incorporate a transmitter, and the remote reader1, a receiver, for communication in an opposite direction to that already described. The communication from the remote console to the remote reader1can include, for example, handshaking data, setup information, or any other form of information desired to be transferred from the remote console to the remote reader1.

Turning toFIG. 4, there is shown an alternative arrangement of the card shown inFIGS. 1 and 2, taking the form of a control card30. The control card30still includes a laminar substrate12bearing control indicia. However, in this arrangement the storage means takes the form of a magnetic strip29formed along an edge28of the reverse face27of the control card30. The stored data associated with the control indicia may be stored on the magnetic strip29in a conventional manner. A corresponding reader (not shown) for this arrangement includes a magnetic read head positioned at or adjacent an entrance to the corresponding control template receptacle. As the control card30is slid into the card receptacle, the stored data is automatically read from the magnetic strip29by the magnetic read head. The reader may then be operated in a manner corresponding to the arrangement ofFIG. 1.

FIG. 5shows another arrangement of a card in the form of a control card34, in which the storage means takes the form of machine readable indicia. In the arrangement shown inFIG. 5, the machine readable indicia takes the form of a barcode36formed along an edge38of the reverse face27of the card34. The stored data is suitably encoded, and then printed in the position shown. A corresponding controller (not shown) for the arrangement shown inFIG. 5includes an optical read head positioned at or adjacent an entrance to the associated control template receptacle. As the card34is slid into the control receptacle, the stored data is automatically read from the barcode36by the optical read head. Alternatively, the barcode can be scanned using a barcode reader associated with the reader immediately prior to inserting the card34, or scanned by an internal barcode reader scanner once the card34has completely been inserted. The card34may then be operated in a manner again corresponding to the arrangement ofFIG. 1. It will be appreciated that the position, orientation and encoding of the barcode can be altered to suit a particular application. Moreover, any other form of machine readable indicia can be used, including embossed machine-readable figures, printed alpha-numeric characters, punched or otherwise formed cut outs, optical or magneto optical indicia, two dimensional bar codes. Further, the storage means can be situated on the same side of the card10as the control indicia.

FIG. 6(a) shows a hardware architecture of a card interface system600A according to a first arrangement. In accordance with the system600A, the remote reader1is hard wired to a personal computer system100via a communications cable3. Alternatively, instead of being hardwired, a radio frequency or IR transceiver106can be used to communicate with the remote reader1. The personal computer system100includes a screen101and a computer module102. The computer system100will be explained in more detail below with reference toFIG. 7. A keyboard104and mouse203are also provided.

The preferred smart card10is programmable and can be created or customized by a third party, which in this case can be a party other than the manufacturer of the card and/or card reader. Alternatively, a barcode can be printed onto the card10at the same time as the control indicia. The third party can be the ultimate user of the smart card10itself, or may be an intermediary between the manufacturer and user. In accordance with the arrangement ofFIG. 6(a), the smart card10can be programmed and customized for one touch operation to communicate with the computer100and obtain a service over a network220, such as the Internet. The computer100operates to interpret signals sent via the communications cable3from the remote reader1, according to a specific protocol, which will be described in detail below. The computer100performs the selected function according to touched control indicia (e.g. jump button22), and can be configured to communicate data over the network220. In this manner the computer100can permit access to applications and/or data stored on remote servers150,152and appropriate reproduction on the display device101.

FIG. 6(b) shows a hardware architecture of a card interface system600B according to a second arrangement. In accordance with the system600B, the remote reader1can be programmed for obtaining a service locally at a set top box601, that couples to an output interface, in this example an audio-visual output device116such as a digital television set. The set-top box601operates to interpret signals112received from the remote reader1, which may be electrical, radio frequency, or infra-red (IR), and according to a specific protocol which will be described in detail below. The set top box601can be configured to perform the selected function according to touched control indicia and permit appropriate reproduction on the output device116. Alternatively, the set top box601can be configured to convert the signals112to a form suitable for communication and cause appropriate transmission to the computer100. The computer100can then perform the selected function according to the control indicia, and provide data to the set-top box601to permit appropriate reproduction on the output device116. The set top box601will be explained in more detail below with reference toFIG. 43.

In a still further application of the system600B, the smart card10can be programmed for obtaining a service both remotely and locally. For instance, the smart card10can be programmed to retrieve an application and/or data stored on remote servers150,152, via the network220, and to load the application or data on to the set top box601. The latter card can be alternatively programmed to obtain a service from the loaded application on the set top box601.

Unless referred to specifically, the systems600A and600B will be hereinafter referred to as the system600.

FIG. 7shows the general-purpose computer system100of the system600, which can be used to run the card interface system and to run software applications for programming the smart card10. The computer system102includes a computer module102, input devices such as a keyboard104and mouse203, output devices including the printer (not shown) and the display device101. A Modulator-Demodulator (Modem) transceiver device216is used by the computer module102for communicating to and from the communications network220, for example connectable via a telephone line221or other functional medium. The modem216can be used to obtain access to the Internet, and other network systems, such as a Local Area Network (LAN) or a Wide Area Network (WAN).

The computer module102typically includes at least one central processing unit (CPU)205, a memory unit206, for example formed from semiconductor random access memory (RAM) and read only memory (ROM), input/output (I/O) interfaces including a video interface207, and an I/O interface213for the keyboard104and mouse203, a write device215, and an interface208for the modem216. A storage device209is provided and typically includes a hard disk drive210and a floppy disk drive211. A magnetic tape drive (not illustrated) is also able to be used. A CD-ROM drive212is typically provided as a non-volatile source of data. The components205to213of the computer module201, typically communicate via an interconnected bus204and in a manner which results in a conventional mode of operation of the computer system102known to those in the relevant art. Examples of computers on which the arrangement described herein can be practiced include IBM-computers and compatibles, Sun Sparcstations or alike computer system evolved therefrom.

Typically, the software programs of the system600are resident on the hard disk drive210and are read and controlled in their execution by the CPU205. Intermediate storage of the software application programs and any data fetched from the network220may be accomplished using the semiconductor memory206, possibly in concert with the hard disk drive210. In some instances, the application programs can be supplied to the user encoded on a CD-ROM or floppy disk and read via the corresponding drive212or211, or alternatively may be read by the user from the network220via the modem device216. Still further, the software can also be loaded into the computer system102from other computer readable medium including magnetic tape, ROM or integrated circuits, a magneto-optical disk, a radio or infra-red transmission channel between the computer module210and another device, a computer readable card such as a smart card, a computer PCMCIA card, and the Internet and Intranets including email transmissions and information recorded on websites and the like. The foregoing is merely exemplary of relevant computer readable media. Other computer readable media are able to be practiced without departing from the scope and spirit of the invention.

The smart card10can be programmed by means of a write device215coupled to the I/O interface213of the computer module102. The write device215can have the capability of writing data to the memory on the smart card10. Preferably, the write device215also has the capability of printing graphics on the top surface of the smart card10. The write device215can also have a function reading data from the memory on the smart card10. Initially, the user inserts the smart card10into the write device215. The user then enters the required data via the keyboard104of the general purpose computer102and a software application writes this data to the smart card memory via the write device215. If the stored data is encoded for optical decoding such as using a barcode, the write device can print the encoded data onto the smart card10.

FIG. 43shows the set top box601of the system600, which can be used to interpret signals112received from the remote reader1. The set top box601in some implementations essentially is a scaled version of the computer module102. The set top box601typically includes at least one CPU unit4305, a memory unit4306, for example formed from semiconductor random access memory (RAM) and read only memory (ROM), and input/output (I/O) interfaces including at least an I/O interface4313for the digital television116, an I/O interface4315having an IR transceiver4308for receiving and transmitting the signals112, and an interface4317for coupling to the network220. The components4305,4306,4313,4315and4317of the set top box601, typically communicate via an interconnected bus4304and in a manner which results in a conventional mode of operation. Intermediate storage of any data received from the remote reader1or network220may be accomplished using the semiconductor memory4306. In accordance with a further arrangement, the set top box can include a storage device (not shown) similar to the storage device209.

The card interface system600will now be explained in more detail in the following paragraphs.

2.0 Card Interface System Software Architecture

2.1 Software Architecture Layout

A software architecture200for the hardware architectures depicted by the system600, is generally illustrated inFIG. 8. The architecture200can be divided into several distinct process components and one class of process. The distinct processes include an I/O interface300, which may be colloquially called an “I/O daemon”300, an event manager301, a display manager306, an (application) launcher303and a directory service311. The class of process is formed by one or more applications304. In one arrangement, there exists one I/O daemon300, one event manager301, one display manager306and one launcher303for every smart card remote connection, usually formed by the set-top box601, and one master launcher (not shown) for each computer100(e.g. the servers150,152) that is running the launchers303, and at least one directory service311for all systems. The directory service311, is queried by the launcher303to translate service data into a Resource Locator (e.g. a URL) that indicates a name or location of a service or the location or name of an application304to be used for the service.

In this form, the architecture200can be physically separated into six distinct parts101,307,309,312,313and601as shown by the dashed lines inFIG. 8, each of which can be run on physically separate computing devices. Communication between each of the parts of the system600is performed using Transport Control Protocol/Internet Protocol (TCP/IP) streams. Alternatively, each of the parts101,307,309,312,313and601can be run on the same machine.

In the arrangement of the system600A ofFIG. 6(a), all of the process components300,301,303,304and306can run on the computer100. The event manager301, the launcher303and the display manager306are preferably all integrated into one executable program which is stored in the hard disk209of the computer100and can be read and controlled in its execution by the CPU205. The directory service311runs on the same computer100or on a different computer (e.g. server150) connected to the computer100via the network220.

In the arrangement of the system600B ofFIG. 6(b), all of components300to304and306can run from the set-top-box601. In this instance, the components300to304and306can be stored in the memory4306of the set top box601and can be read and controlled in their execution by the CPU4305. The directory service311can run on the computer100and can be stored in the memory206of the computer100and be read and controlled in its execution by the CPU205. Alternatively, the directory service311can be run on the set top box601or its function performed by the launcher303.

In a still further arrangement, if the set-top-box601is not powerful enough to run the system600locally, the I/O daemon300can run on the set-top-box601and the remainder of the architecture200(i.e. process components301,303,304,306and311) can run remotely on the other servers (150,152) which can be accessed via the network220. In this instance, the I/O daemon300can be stored in the memory4306of the set top box601and can be read and controlled in its execution by the CPU4305. Again, the functional parts of such a system can be divided as shown inFIG. 8.

The I/O daemon300is a process component that converts datagrams received from the remote reader1into a TCP/IP stream that can be sent to the event manager301and, when using a two-way protocol, vice versa. Any suitable data format can used by the remote reader1. The I/O daemon300is preferably independent of any changes to the remote reader1data format, and can work with multiple arrangements of the remote reader1. In one implementation of the system600, the I/O daemon300is integrated into the event manager301.

In the system600A, the I/O daemon300is started when a user starts the smart card system600by powering up the computer100and the event manager301has been started. In a further arrangement of the system600, the I/O daemon300is started when a user starts the system600by turning on the set-top box601.

The I/O daemon300will be explained in more detail below with reference to section 9.0.

2.1.2 Event Manager

The event manager301forms a central part of the architecture200in that all communications are routed through the event manager301. The event manager301is configured to gather all events that are generated by the remote reader1and relayed by the I/O daemon300. These events are then redistributed to the various process components300to304and306and running applications. The event manager301is also configured to check that an event has a valid header, correct data length, but is typically not configured to check that an event is in the correct format. An “event” in this regard represents a single data transaction from the I/O daemon300or the launcher303or applications304.

Any changes in protocol between different systems can be dealt with by the event manager301. Where possible, events can be rewritten to conform with the data format understood by any presently running application304. If such is not possible, then the event manager301reports an error to the originating application304. When different data formats are being used, for example with a system running multiple smart cards, the event manager301preferably ensures that the smallest disruption possible occurs.

The event manager301does not have any presence on the display screen or other output device116. However, the event manager301can be configured to instruct the display manager306which application is presently required (i.e. the “front” application) and should currently be displayed on the display101. The event manager301infers this information from messages passed to the applications304from the launcher303as will be explained in more detail below with reference to section 10.0.

The event manager301can be configured to always listen for incoming I/O daemon connections or alternatively, can start the system600. The method used is dependent on the overall arrangement of the system600. Depending on the configuration of the system600, the event manager301can start the system600or the set top box601can use the incoming connection of the I/O daemon300to start the system600. The event manager301will be described in more detail below with reference to section 7.0.

In one arrangement, where a thin client computer is being utilized and multiple launchers303are running with each launcher303being responsible for one set top box, a master launcher (not shown) which communicates directly with the event manager301can be used. The master launcher is used to start the launcher303corresponding to each of the event managers301if more than one event manager is running on the system600. Initially, when the I/O daemon300connects to the event manager301, the event manager301requests that the master launcher start a first process for the event manager301. The first process is generally a launcher303for any smart card application304. The master launcher can also be configured to shut down the launcher303of an application304when the event manager301so requests, and for informing the event manager301that the launcher330has exited.

There is preferably one master launcher running for each physically separate server (e.g.150,152) that is running an associated smart card application304. This one master launcher handles the requests for all event managers that request launchers on a particular server. When being executed on a computer100, as seen inFIG. 7, the master launcher commences operation either before or no later than the system600. In this instance, the master launcher is started first.

The master launcher can be integrated into the event manager301, for example, when an associated launcher is running on the same computer as the event manager301.

In the arrangements of the systems600A and600B, the first process started by the insertion of a smart card10into the remote reader1is the launcher303. In specific systems, specified applications may be commenced. For example, an automatic teller machine can start a banking application. Another example includes the use of restricted launchers that only start a specified sub-set of applications. The launcher303is an application that starts other applications for a specific event manager301. The launcher303starts and ends applications and can also start and end sessions. The launcher303also informs the event manager301when applications are starting and ending, and tells the applications304when they are receiving or losing focus, or when they need to exit. In this regard, where a number of applications304are operating simultaneously, the application304that is currently on-screen is the application having focus, also known as the “front application”. When another application is about to take precedence, the launcher303tells the front application that it is losing focus, thereby enabling the current application to complete its immediate tasks. The launcher303also tells the new application304that it is gaining focus, and that the new application304shall soon be changing state. The launcher303can also configured to force an application to exit.

The launcher303receives certain events such as “no-card”, “low battery” and “bad card” events generated by the remote reader1. The launcher303also receives events that are intended for applications that are not currently the front application, and the launcher303operates to correctly interpret these events.

In one arrangement of the system600, the launcher303is started when a request is generated by the event manager301to start the launcher303. The launcher303can also be told to exit and forced to exit by the event manager301.

The launcher303is preferably the only process component that needs to communicate with the directory service311. When the launcher303is required to start a new application304, the launcher303queries the directory service311with service data, and the directory service311returns a location of the application304and service data associated with the new application304. The service data is sent to the new application304as initialization data in an event, referred to herein as the EM_GAINING_FOCUS event. The application location specifies the location of the application304to be run, and may be local, for implementations with a local computer, or networked. If the application location is empty, then the launcher303has to decide which application to start based on the service data.

The launcher303is also configured to start any applications, for example a browser controller, that are typically always be running while the system600is operating. Such applications are referred to as persistent applications. The launcher303can also start applications either in response to a first user selection on a corresponding smart card10, or at the request of another one of the applications304.

The launcher303can be integrated into the event manager301in some arrangements of the system600and will be explained in more detail below with reference to section 10.0.

2.1.5 Display Manager

The display manager306selects which smart card application304is currently able to display output on the display screen101. The display manager306is told which application304can be displayed by an EM_GAINING_FOCUS event originating from the launcher303. This event can be sent to the display manager306directly, or the event manager301can send copies of the event to the display manager306and the intended recipient.

Generally, the only application304that is attempting to display output is the front application. The display manager306can provide consistent output during the transfer between applications having control of the display. The display manager306may need to use extrapolated data during change-oversee of applications as the front application.

In some arrangements of the architecture200, the display manager306may not be needed or the role of the display manager306may be assumed by the other parts (e.g.301or303) of the architecture200.

2.1.6 Directory Service

The directory service311is configured to translate a service identifier that is stored on smart cards10into a resource locator (e.g. a URL) that indicates the location of the service or the location of an application associated with the service. The directory service311is also configured to translate optional service data. The directory service311allows the launcher303associated with a particular card10to decide what to do with a resource locator, for example, download and run the associated application304or load the resource locator into a browser application. The translation by the directory service can be performed using a distributed lookup system.

The applications304associated with a particular smart card10can be started by the launcher303associated with that smart card10as a response to a first button press on a corresponding card. Each application304can be a member of one or more service groups. An application304can be specified to not be part of any service group in which case the application will never be run with other applications. An application can become part of a service group once the application is running and can remove itself from a service group when the application is the currently front application.

Some applications can be started when the system600is started and these applications (e.g. a browser control application or a media playing application) can be always running. These persistent applications can be system specific or more generally applicable.

FIG. 9is a schematic block diagram representation of a card interface system including the process components301to306described above. In the arrangement ofFIG. 9, the remote reader1is communicating with a computer900via an IR link in conjunction with an I/O daemon300for controlling the IR link. Further, the computer900is configured for communicating to and from a communications network, in this case represented by the Internet400, to a Web server410. In this instance, some of the applications304accessible utilizing the smart card10and remote reader1can be Web pages406associated with different smart cards10. The Web libraries407contain functions (e.g. JavaScript functions) and classes (e.g. Java classes) that can be included with Web pages for use with the smart card10. The Web pages406can be accessed with a running application called the Web browser403.

In the arrangement ofFIG. 9, the event manager301is configured to receive an event from the remote reader1. The event is then sent to the launcher303, which can be configured to send a message to the browser controller402controlling the Web browser403. The process for starting an application or browser session will be explained in more detail below. The launcher303can also be configured to download applications408as well running applications from a file server411which is also connected to the computer900via the Internet400.

The remote reader1is preferably a hand-held, battery-powered unit that interfaces with a smart card10to provide a customizable user interface. As described above, the remote reader1is intended for use with a digital television, a set top box, computer, or cable television equipment to provide a simple, intuitive interface to on-line consumer services in the home environment.

FIGS. 43 and 44show a reader4401similar to the reader1described above. The reader4401is configured for the reading of the card10according to one arrangement. The reader4401is formed of a housing4402incorporating a card receptacle4404and a viewing area4406. The receptacle4404includes an access opening4410through which a smart card10, seen inFIG. 1, is insertable.

An upper boundary of the viewing area4406is defined by sensor means in the form of a substantially transparent pressure sensitive membrane4408similar to the membrane8described above. Arranged beneath the membrane4408is a data reading means provided in the form of an arrangement of exposed electrical contacts4407configured to contact complementary contacts of the smart card10.

The card10is inserted into the reader4401via the access opening4410as shown inFIG. 45. The configuration of the reader4401allows a user to hold the controller101in one hand and easily insert the smart card10into the controller4401with their other hand. When the smart card10is fully inserted into the controller4401, the pressure sensitive membrane4408fully covers the upper face16of the smart card10. The viewing area4406preferably has substantially the same dimensions as the upper face16of the card10such that the upper face16is, for all intents and purposes, fully visible within the viewing area4406through the transparent pressure sensitive membrane4408.

FIG. 46shows a user operating the reader4401after a card has been fully inserted.

Referring toFIGS. 47(a) to47(c), the housing4402is formed of a substantially two part outer shell defined by a top section4827that surrounds the membrane4408and a base section4805which extends from a connection4829with the top section4827to a location4811below and proximate the transverse centre of the membrane4408. The base section4805incorporates a facing end4815formed from infrared (IR) transparent material thereby permitting IR communications being emitted by the reader4401.

The location4811defines a point of connection between the base section4805a card support surface4807which extends through a plane in which the contacts4407lie to an interior join4835that sandwiches the membrane4408between the surface4807and the top section4827. From this arrangement it will be appreciated that the access opening4410is defined by the space between the location4811and a periphery4836of the housing4402, seen inFIG. 47(a).

The contacts4407extend from a connector block4837mounted upon a printed circuit board (PCB)4801positioned between the base section4805and support surface4807by way of the two mountings4817and4819. Arranged on an opposite side of the PCB4801to the connector block4837is electronic circuitry (not shown), electrically connected to the connectors4407and the touch sensitive membrane4408and configured for reading data from the card10according to depression of the membrane4408. Mounted from the PCB4801is an infrared light emitting diode (LED)4800positioned adjacent the end4815which acts as an IR window for communications with a device (e.g. the set top box601) to be controlled.

FIG. 47(b) shows a similar view toFIG. 47(a), with the smart card10partially inserted through the access opening4410into the receptacle4404. As can be seen inFIG. 47B, the support surface4807has an integrally formed curve contour4840that leads downward from the plane of the contacts4407towards the join4811. This configuration allows the controller4401to receive the smart card10such that the smart card10may be initially angled to the plane of the receptacle4404, as seen inFIG. 47(b). The curve contour4840configuration of the support surface4807guides the smart card10into a fully inserted position under the force of a user's hand. Specifically, as the card10is further inserted, the curvature of the support surfaces guides the card10into the plane of the contacts4407and receptacle4404.

FIG. 47(c) shows a similar view toFIG. 47(a), with the smart card10fully inserted into the receptacle4404. In this position, the card10lies in the plane of the receptacle4404and the contacts4407which touch an associated one of the data contacts4408of the smart card10, and the smart card10is covered by the pressure sensitive membrane4408. Further, the contacts4407are preferably spring contacts, the force of which against the card10, provides for the card10to be held within the receptacle by a neat interference fit.

In the following description references to the reader1can be construed as references to a reader implemented as the reader ofFIG. 1or the reader4401ofFIG. 43.

FIG. 10is a schematic block diagram showing the internal configuration of the remote reader1in more detail. The remote reader1includes a microcontroller44for controlling the remote reader1, co-ordinating communications between the remote reader1and a set top box601, for example, and for storing mapping information. The microcontroller44includes random access memory (RAM)47and flash (ROM) memory46. The microcontroller44also includes a central processing unit (CPU)45. The microcontroller44is connected to a clock source48and a clock controller43for coordinating the timing of events within the microcontroller44. The CPU45is supplied with electrical 5 volts by a battery53, the operation of the former being controlled by a power controller50. The microcontroller44is also connected to a beeper51for giving audible feedback about card entry status and for “button” presses.

Infra-red (IR) communications are preferably implemented using two circuits connected to the microcontroller44, an IR transmitter (transmitter)49for IR transmission and an IR receiver (receiver)40for IR reception.

The pressure sensitive touch panel8of the remote reader1communicates with the microcontroller44via a touch panel interface41. A smart card interface42connects to the electrical contacts7.

An in-system programming interface52is also connected to the microcontroller44, to enable programming of the microcontroller44by way of the microcontroller FLASH memory46with firmware. The firmware will be explained in further detail later in this document with reference to section 6.0.

The internal configuration of the remote reader1will now be described in further detail.

3.1 Low Power Mode Lifetime

The power controller50is operable to provide two power modes, one being a low-power mode “sleep” mode, and another being an active mode. The low power mode lifetime is the lifetime of the battery53expressed in years. When the remote reader1is not functioning and is in the low power mode, the lifetime can be between greater than 2 years.

If the reader1is sleep mode and a user presses the touch panel8then the remote reader1comes out of sleep mode, and the CPU45calculates the touch co-ordinates and sends a serial message by infra-red transmission. The battery53should remain serviceable for the current supply requirements of more than 100,000 button presses.

3.2 Service Life

The service life is defined as the period of time that the remote reader1can be expected to remain serviceable, not including battery replacement. The service life is related to the Mean Time Between Failures (MTBF) figure and is usually derived statistically using accelerated life testing. The service life of the remote reader1can thus be greater than 5 years.

The microcontroller44of the remote reader1has an 8 bit central CPU with 4096 bytes of FLASH memory and 128 bytes of random access memory. The device also operates on a supply voltage from 3 to 5 Volts and has flexible on-board timers, interrupt sources, 8 bit analog to digital converters (ADC), clock watchdog and low voltage reset circuits. The device also has high current output pins and can be programmed in circuit with only a few external connections.

3.4 Clock Source

The main clock source48for the remote reader1is preferably a 3 pin 4.91 MHz ceramic resonator with integral balance capacitors. The frequency tolerance is 0.3%. While such tolerance is not as good as a crystal, such is however adequate for serial communications and is much smaller and cheaper than a crystal.

The beeper51is included with the remote reader1to give audible feedback about card entry status and for button presses. The beeper51is preferably a piezo-ceramic disk type.

As described above, infra-red (IR) communications are preferably implemented using two circuits, an IR transmitter49for IR transmission and an IR receiver40for IR reception. The two circuits40and49are preferably combined on a printed circuit board (e.g. the PCB4801ofFIG. 47) within the remote reader1. The printed circuit board can be connected to the microcontroller44by a 4 way flat printed cable. Large bulk decoupling capacitors (not shown) are required on the infra-red board to provide surge currents, which are required when transmitting.

IR transmission is preferably by means of an infra-red Light Emitting Diode (LED) (e.g. the LED4800ofFIG. 47(a)) forming part of the IR transmitter49.

The IR receiver40is preferably integrated with an infra-red filter, a PIN diode, an amplifier and discriminator circuitry into a single device. Received serial information passes directly from this device to an input port of the microcontroller44. This port can be programmed to generate an interrupt on receiving data allowing speedy storage and processing of incoming signals.

The remote reader1can preferably support smart cards10as defined by International Standards Organization (ISO) standards 7816-3 and ISO 7810. Three and five volt CPU cards (i.e. cards with an embedded microprocessor) with T=0 and T=1 protocols can also be supported as are 3 and 5V memory cards.

The electrical contacts7used to make contact between the card10and the microcontroller44are preferably implemented as a surface mount connector with 8 sliding contacts and a “card in” switch. In accordance with the ISO requirements the following signals must be provided:Pin 1—VCC—Supply voltage;Pin 2—RST—Reset signal. Binary output to card;Pin 3—CLK—Clock signal, Binary output to card;Pin 4—RFU—Reserved, leave unconnected;Pin 5—GND—Ground;Pin 6—VPP—Programming voltage, not required, link to GND, VCC or open;Pin 7—I/O—Data I/O, bi-directional signal; andPin 8—RFU—Reserved, leave unconnected.

The RST and I/O pins are preferably connected directly to the microcontroller44. All pins except the power supplies are equipped with series termination and transient voltage suppressor diodes to prevent electrostatic discharge problems.

3.9 CPU Card Power Supply

As described above, the microcontroller44requires a 3–5 Volt power supply for operation. The 5 Volt supply can be generated from a 3V Lithium coin cell operating as the battery53by means of the power controller50in the form of a regulated 5V charge-pump DC—DC converter chip.

3.10 Touch Sensitive Interface

As described above, the pressure sensitive touch panel8of the remote reader1communicates with the microcontroller44via a touch panel interface41. The touch panel interface41provides an analog signal according to the position of the touch on the touch panel8. This analog signal is then communicated to the microcontroller44.

The calculation of touch co-ordinates requires bottom and left touch panel8contacts (not shown) to be connected to the inputs of an analog to digital converter on the microcontroller44.

A touch on the touch panel8can preferably be used to wake up the remote reader1from sleep mode. A resistive connection from the left screen contact to a sleep WAKE UP port as illustrated provides this feature. Note that during in-system programming, up to 8 volts may be applied to a pin on the microcontroller44referred to as the Interrupt Request Pin (IRQ) so a clamping diode needs to be fitted to this pin to prevent device damage. In this instance, it is the internal pull up on the IRQ pin that actually provides the bias required to detect touch panel8presses.

As described above, the remote reader1uses a battery53. A 3 Volt lithium coin cell can be used as the battery53to power all the circuitry of the remote reader1.

3.12 In System Programming

The microcontroller supports in-system programming (ISP) options. The in-system programming interface52is used in the remote reader1to perform programming of the microcontroller44such as programming of the microcontroller FLASH ROM memory46with firmware.

3.13 Printed Circuit Boards and Interconnection

The remote reader1can include two printed circuit boards (PCB), instead of the one PCB4801of the reader4401, as follows:(i) an infra-red (IR) PCB which holds the infra-red diode, drive FET and receiver; and(ii) a main PCB (e.g. the PCB4801ofFIG. 47(a)) which holds all the other components40to53mentioned above.

Both of the PCB boards described above are preferably double sided using standard grade FR4, 1.6 mm PCB material. The main PCB preferably utilizes surface mount components since the thickness of the finished PCB is critical and preferably components are restricted to a height of approximately 3 mm max.

The IR PCB can use through hole parts but again there are preferably stringent component height restrictions imposed. The interconnection of the two PCBs is via a custom designed 4-way flat printed cable (FCA). This cable interfaces to the two PCBs via a surface mount FCA connector. Another FCA is used to interface to the touch panel8.

3.14 Low Power Mode

When the remote reader1has not been used for a short period of time, pre-programmed firmware preferably puts the unit into low-power mode to conserve battery life. In low-power mode, the supply voltage is switched off to all current consuming components, the ports of the microcontroller44are set into a safe sleep state and the clock48is stopped. In this state the current consumption of the remote reader1is less than 5 μA. A P-channel FET can be used to control the supply of power to the current consuming components.

There are three preferred methods to wake the remote reader1up from low power mode as follows:touch the touch panel8;insert a card into the card receptacle4; andremove and re-insert the battery53.

The card insert wake up enables the remote reader1to always beep when a card is inserted, regardless of whether the unit is in low power mode or not. The ‘touch’ and ‘card insert’ wake ups are handled by the IRQ pin of the microcontroller44. It is important that the IRQ pin is set to “edge trigger” so that only a new touch or card insert wakes the microcontroller44up. If IRQ sensitivity is set to “level” trigger then inadvertently leaving the touch panel8pressed, for example when the remote reader1is packed in luggage, would prevent the remote reader1from entering low power mode.

3.15 Interrupts and Resets

The microcontroller44firmware for the remote reader1uses two external and one internal interrupt sources. External interrupts come from the IRQ pin for low power mode wake up. The internal interrupt is triggered by a timer overflow and is used to time various external interfaces. These interrupts are serviced by pre-programmed firmware procedures.

There are four possible reset sources for the microcontroller as follows:low supply voltage reset at 2.4 Volts;illegal firmware op-code reset;Computer Operating Properly (COP) reset if firmware gets stuck in a loop; andISP reset forced onto a RESET pin when in-system programming (ISP) starts.
4.0 Card Data Format

The format of data for the card10described above will be described in the following paragraphs. For memory cards such as the control card30as described in relation toFIG. 4, data conforming to the format to be described can be copied directly onto the card. For the CPU card arrangement described above, data conforming to the format to be described can be loaded as a file into the file system of the CPU of the card.

The card10described above preferably stores a data structure that describes various card properties and any user-interface indicia printed on the card. The cards10can also include global properties that specify attributes such as information about the card, vendor and one or more services. User-interface objects, if present, specify data to associate with areas of the surface of the card10.

The user-interface objects, in the arrangements described herein, represent mapping data, which relate predetermined areas, or iconic representations directly imprinted, on a surface of the card10to commands or addresses (e.g.: Uniform Resource Locators (URLs)). The mapping data includes the coordinates which typically define the size and location of User Interface Elements (UI) elements (e.g.: predetermined areas) on the card10. In this connection, the term UI element typically refers to the indicia on the card10, whilst the term UI interface object refers to the data relating to a particular indicia. However, these terms are used interchangeably throughout the following description.

The User-interface objects are preferably stored directly on the card10. Alternatively, the User-Interface objects can be stored not on the card10itself, but in the system600. For instance, the card10can store, via the on-card memory, barcode or magnetic strip, a unique identifier, which is unique to cards10having a substantially similar UI elements and layout. The unique identifier together with the coordinates determined from the touch panel8, as a result of a press, can be transmitted by the reader1to the computer100or set top box601of the system600. The system600having the user-interface objects stored on the computer100, set top box601or a server150, over a network220, can perform the mapping from the determined coordinates to the corresponding command, address or data relevant to the service associated with the card10and the press for a desired function represented by the UI element on the card10. Thus, in this instance, data related to the user selected indicia are the coordinates determined by the reader1as a result of a press by the user on a portion of the touch panel8which overlays the desired indicia.

In accordance with the card arrangements described above, data stored by the card10includes a card header followed by zero or more objects described in the following sections.

4.1 Card Header

FIG. 11shows the data structure of a card header1100as stored in the smart card10. The header1100includes a number of rows1101, each of which represents four bytes of data. The data is in big-endian format. The complete header is 20 bytes long and includes the following fields (described inFIG. 12):(i) magic number field: includes a constant that specifies a card as being a valid memory card; for example, the magic number field can be used to check or verify that a propriety card belonging to a particular manufacture is being used;(ii) versions field: includes each version increment that specifies a change in the card layout that can not be read by a reader that is compatible with lower versions of the layout;(iii) reserved field: this field is reserved for future use;(iv) flags field: includes flags for a card (seeFIG. 13);(v) distinguishing identifier field: includes two fields—a service and a service specific field; the service field identifies the service of the card and the service specific field optionally contains a service-specific value;(vi) a number of objects field: includes a number value representing how many objects follow the header; this field can be set to zero; and(vii) a checksum field: includes a card checksum of all data on the card excluding the checksum itself.

The distinguishing identifier includes a service identifier that distinguishes one service from another or one vendor from another. That is, the service is identified by an application that provides the service to a card user. In the arrangements described herein, the distinguishing identifier also includes a service-specific identifier that can be optionally used by the vendor of a service to provide predetermined functions of a particular service. The use of this service-identifier is substantially dependent upon the application run on the system600. For example, the service identifier together with the service-specific identifier can be used as a unique identifier of a card10; to gain or deny access to a specific feature of a particular service; to reproduce a specific-service identifier value in a log file to confirm or verify that a particular card10having that value was used to access a service; and to provide a unique identifier that can be matched with a corresponding value in a database to retrieve information about the user of the service (e.g.: name, address, credit card number etc).

Other examples of uses of the service-specific identifier can include providing information about a mechanism or mode of distribution of the cards10(e.g. by mail, bus terminal kiosks, handed out on a train etc). The service-specific identifier, for instance, can identify what data should be loaded into the system600when a service is accessed.

The foregoing is not intended to be an exhaustive list of possible applications of the service-specific identifier but a small sample of possible applications and there are many other applications of the service-specific identifier.

4.1.1 Card Flags

The flags field of the header ofFIG. 11includes three flags as follows:(i) Don't beep;(ii) No move events; and(iii) No event co-ordinates.

FIG. 13shows a description of each of the above flags. The above flags effect the functions that a smart card10can perform in a remote reader1, as is defined by the description of each flag. An example, of a User Interface (UI) element as referred to inFIG. 13is a “button” on the card10. UI Elements will be explained in further detail later in this document.

Immediately following the card header1100ofFIG. 11can be zero or more object structures defining the objects of a particular card10and forming part of the card data. Each object structure has an object header. The object header includes four fields as follows:(i) a type field;(ii) an object flags field;(iii) a length field; and(iv) a data field.

The structure of the data field depends on the object type as will be described below.

FIG. 14shows a description of each of the fields of the object header in accordance with the card arrangements described herein. The flags object field of the object header ofFIG. 14, includes an inactive flag.FIG. 15shows a description of the inactive flag in accordance with the card arrangements described herein.

There are five object types provided in accordance with the described card arrangements, as follows:(i) User Interface (UI) objects (i.e. data defining a button on the card10);(ii) Card Data;(iii) Fixed Length Data;(iv) Reader Insert;(v) No operation; and(vi) No operation (single byte).

FIG. 16shows a description of each of the above object types (i) to (vi).

4.2.1 User Interface (UI) Object

Each UI object defines a rectangular area on the card10and some quantity of associated data that is transmitted when the user touches an area of the panel8over the corresponding rectangular area of the card10. The origin for the co-ordinate mapping system is the top left of the smart card10as if the card10was an ISO standard memory smart card held in a portrait view with the chip contacts18facing away from the viewer and towards the bottom of the card. For any reader that does not use this card orientation, the values of the corner points must be adjusted by the reader so as to report a correct “button” press.

The UI (element) object structure has six fields in accordance with the card arrangements described, as follows:(i) a flags field;(ii) an X1field;(iii) an Y1field;(iv) an X2field;(v) a Y2field; and(vi) a data field which typically includes data associated with the UI element; for example, a URL, a command, a character or name.

FIG. 17shows a description of each of the above fields for the UI object structure of the described card arrangements. A press on the pressure sensitive touch panel8is defined to be inside a particular UI object if:(i) an X value corresponding to the press location is greater than or equal to the X1value of the associated UI object and is strictly less than the X2value for that particular UI object; and(ii) a Y value corresponding to the press location is greater than or equal to the Y1value of the particular UI element and strictly less than the Y2value.

Overlapping UI elements is allowed. If a press is within the bounds of more than one UI element then an object subsequently sent in response to the press is determined by a Z order. The order of the UI elements on the card defines the Z ordering for all of the UI elements on that particular card. The top UI element is the first UI element for a particular card. The bottom UI element is the last UI element for that particular card. Such an arrangement allows for non-rectangular areas to be defined. For example, to define an “L” shaped UI element, a first UI object would be defined with zero bytes in the data field, and a second UI object would be defined to the left and below the first UI object but overlapping the UI object.

The location of a press is to be reported in “fingels”, which represent finger elements (analogous to “pixels” which represent picture elements). The height of a fingel is defined to be 1/256th of the length of an ISO memory smart card and the width is defined to be 1/128th of the width of an ISO memory smart card. The behaviour associated with each element may be modified with one or more flags.

Each UI element has four flags associated with it as follows:(i) Invert Beep Enable;(ii) Auto repeats;(iii) Do Not Send Data on Press; and(iv) Do Not Send Data on Release.

FIG. 18shows a description for each of the UI element flags.

4.2.2 Card Data

The card data object is used to store data specific to a particular card. The data layout for this object is undefined.

4.2.3 Fixed Length Data

The fixed length data object is used to define a fixed length block on the card that can be written to by the computer100.

4.2.4 Reader Insert

The reader insert object can be used to store instructions for the remote reader1when a particular card is inserted. The reader insert object can be used, for example, to instruct the reader1to use a specific configuration of IR commands to allow communication with a specific set top box or TV.

4.2.5 No Operation

The No Operation object is used to fill in unused sections between other objects on a particular card. Any data stored in the no operation object is ignored by the remote reader1. Any unused space at the end of the card10does not need to be filled with a no operation object.

The No Operation (One Byte) object is used to fill gaps between objects that are too small for a full object header. These objects are only one byte long in total.

5.0 Reader Protocol

The remote reader1uses a datagram protocol that supports both uni-directional and bi-directional communication between the remote reader1and the set top box601or computer100, for example. The format used for messages from the remote reader1as a result of user interactions with the remote reader1are of a different format than those that are sent to the remote reader1.

5.1 Message Types

There are at least seven message event types that can be sent by the remote reader1. These event types are as follows:INSERT: When a card10is inserted into the remote reader1, and the card10is validated, an INSERT event is generated by the remote reader1and an associated message is transmitted. This message announces the card10to a receiver (e.g. the set top box601). The INSERT message preferably includes the particular distinguishing identifier and allows applications to be started or fetched immediately upon the card10insertion rather than waiting until the first interaction takes place.REMOVE: When a card10is removed from the remote reader1, a corresponding REMOVE event is generated and a REMOVE message is sent to the particular receiver associated with the remote reader1. Like the INSERT message, the associated distinguishing identifier is transmitted along with the message. As the distinguishing identifier cannot be read from the now removed card10, the identifier is stored in the memory47of the remote reader1. Storing the distinguishing identifier in the memory47is a useful optimization as the distinguishing identifier is required for all other messages and reading the identifier from the card10each time the identifier is required can be too slow. INSERT and REMOVE messages are not relied upon by the system600to control processing. The system600is configured to infer missing messages if a message is received and is not immediately expected. For example, if an application sees two INSERT messages in a row, then the application can assume that it has missed the REMOVE message associated with the card of the first INSERT message as it is not possible to have two cards inserted at one time in the arrangements described herein. The application can then take whatever action is required prior to processing the second INSERT message.Another example of where a missing message can occur is where a hand-held, infra-red connected reader1, as compared with a wired reader, is being used. Often a user does not point the reader1directly at a receiver when inserting or removing cards. This problem can be corrected by the system600inferring the INSERT or REMOVE operations based on differing distinguishing identifiers in consecutive PRESS and RELEASE pairs.BAD CARD: If an invalid card is inserted, then the remote reader1is preferably configured to generate a BAD CARD event and to send a BAD CARD message. Such a message allows an associated receiver to take some action to alert the user to the invalid card.PRESS: When a touch is detected by the remote reader1and the position of the touch maps to a user-interface object, a PRESS event is generated and a PRESS message is sent to an associated receiver. The PRESS message contains details of the associated card, the position of the press and the data associated with the user-interface element at that particular position. If there is no user interface element defined for that position (e.g. if there are no user interface elements defined on the card10at all) a PRESS message is sent containing details of the associated card and the position of the press. If there is no card present in the remote reader1when a PRESS event is generated then a PRESS message is sent containing the special “NO_CARD” identifier (i.e. eight bytes of zero—0×00) and the position of the press.RELEASE: A RELEASE event complements the PRESS event and a RELEASE message can be sent in order to inform the application program of the system600that a PRESS has been lifted. Every PRESS event preferably has a corresponding RELEASE event. Readers can allow multiple presses to be registered or provide other events that may occur between PRESS and RELEASE messages.MOVE: If, after processing a PRESS event, the touch position changes by a certain amount then the finger (or whatever is being used to touch the card) is assumed to be moving. MOVE EVENTS are generated and MOVE messages are sent until the touch is lifted. MOVE events auto-repeat by re-sending the last MOVE messages when the touch position remains stationary. Auto-repeat finishes when the touch is lifted and a corresponding RELEASE message is sent. Unlike PRESS and RELEASE events there is no user-interface object involved with MOVE events.LOW BATT: A LOW BATT event is generated and a LOW BATT message is sent when the battery53in the remote reader1is getting low. This message is sent after user interactions to increase the chance that the message will be received by the rest of the system600. The sending of the LOW BATT message does not prevent the remote reader1from entering a low power state.
5.2 Data Formats

The preferred data format for the system600is a fixed size header followed by a variable length data field which can be zero bytes or more in length, followed by an eight bit check-sum and complement.

5.2.1 Message Header

The message header is preferably of a fixed length and is prepended to all messages sent from the remote reader1. The message header is preferably as small as possible due to any bandwidth restrictions that may be imposed.FIG. 19shows the format of the message header that is sent from a remote reader1.

Service and service-specific identifiers can be assigned, by a smart card identification authority, to a vendor when the vendor registers a particular service. The service and service-specific identifier are the same for every message from a given card. A service specific identifier is preferably set by a vendor for use with their application.

FIG. 20shows a table listing the message event types that have been described above.

5.2.2 Simple Messages

A number of message types are considered simple in that they consist solely of the message header described above followed by the message checksum byte and its complement. For example, a BADCARD message is a simple message.

FIG. 21shows the format of a simple message in accordance with the arrangements described herein.

5.2.3 MOVE Messages

MOVE messages are formed of the message header described above followed by two fields defining the co-ordinates of the touch position on the touch panel8of the remote reader1.FIG. 22shows the format of a MOVE message in accordance with the arrangements described herein.

5.2.4 PRESS and RELEASE Messages

FIG. 23shows the format of PRESS and RELEASE messages. PRESS and RELEASE messages, like MOVE messages contain the message header and touch co-ordinates. In addition, PRESS and RELEASE messages send data associated with the user-interface element if the touch position matches a user-interface element defined on the card. This data is of variable length, the actual size being defined by a corresponding card10. If the touched position does not match a user-interface element defined on the card (including if no user-interface elements are defined on the card), zero bytes of data associated with user interface elements are sent. If there is no card10in the reader1then the service identifiers are all set to zero (i.e. 0x00) and zero bytes of data associated with the user-interface elements are sent. The data associated with the UI element normally corresponds to the data associated with the user interface element defined on the card but may be modified or generated by processing on the card10or reader1.

FIG. 24is a data flow diagram showing the flow of the above described messages within the system600. As seen inFIG. 24, the card header and object header are read by the CPU45of the remote reader1which sends a corresponding INSERT, REMOVE, PRESS, RELEASE, MOVE, BADCARD or LOW BAT message to the event manager301via the I/O daemon300. As will be described in more detail below, the event manager301has twenty-one core messages, which are sent to and received from the ML302, launcher303and applications304.

The microcontroller44has non-volatile memory46embedded within which can be programmed with the firmware to be described in detail below. The firmware working in concert with the microcontroller44and peripheral hardware (e.g. the computer100) can thus dictate the functional requirements of the remote reader1.

6.2 Code Type

In an attempt to minimize the cost of the remote reader1to a user, memory on the remote reader1is preferably minimized. As a result the application program written for the remote reader1(i.e. the firmware) must be as compact and fast as is possible.

6.3 Resource Constraints

The microcontroller44has the following characteristics:

The flash memory46is configured with 4096 bytes of FLASH ROM and can be utilized for firmware storage. The FLASH ROM is re-programmable but in the case of mass production a MASK ROM part can be utilized.

6.3.2 Random Access Memory (RAM)

The RAM47is configured as 128 bytes of RAM for use by the firmware.

The remote reader1uses two of the numerous interrupt sources supported by the microcontroller44. These interrupts can be described as follows:

6.4.1 Received Data Interrupt

An infra-red (IR) serial data receiver generally generates a falling edge when incoming data is received. This data has to be sampled and buffered as quickly as possible. One port of the microcontroller44doubles as an input timing capture pin which can initiate an interrupt on the falling edge.

The microcontroller44has a free-running 16 bit timer, which can be programmed to generate an interrupt when it overflows. In conjunction with the 4.91 MHz clock source and pre-scale factor of 64, this equates to an interrupt every 3.41 seconds. An interrupt service routine increments a counter which triggers the suspension to low power mode preferably after about one minute of inactivity.

The microcontroller44supports five reset sources and the remote reader1is preferably configured to use all of reset sources. These reset sources can be described as follows:

6.5.1 Power on Reset (POR)

The POR reset is initiated when a new battery is fitted to the remote reader1. The microcontroller44includes a circuit that detects the power on condition and generates a reset.

The LVI reset is initiated when a circuit (not shown) within the microcontroller44detects that the supply voltage has fallen below 2.4 Volts. When this kind of reset occurs a flag is set in a Reset Status Register (RSR) and an initialization routine can deduce that the battery53is becoming depleted. For example, when infra-red data is being transmitted, the infra-red LED consumes high current as it is being pulsed. If the battery53is depleted, the supply voltage can dip under the 2.4 Volt threshold during transmission causing an LVI reset. After reset, the battery53voltage recovers and the LVI reset does not occur until the next high current drain. As such, the remote reader1is given a chance to flag the failing of the battery53to an associated set-top box or remote equipment so that the user can be prompted to replace the battery53.

6.5.3 Computer Operating Properly (COP) Reset

The COP reset is configured to reset the microcontroller44if the microcontroller44gets stuck doing a particular operation for an inordinate amount of time. The COP circuit takes the form of a counter that generates a reset if the counter is allowed to over-flow. The COP register must be written at predetermined time intervals to avoid a COP reset.

An Illegal Address/Opcode Reset is generated by the microcontroller44if it encounters either an address out of a predetermined range or an opcode that does not conform to predefined conditions. This reset cannot be turned off but should only be in evidence during code debugging.

6.5.5 Hardware Reset

A hardware reset is generated by driving a ‘Reset’ pin on the microcontroller44low during normal operation. Additionally, if the microcontroller44is in low power mode, a falling edge on the Interrupt Request (IRQ) pin also generates a hardware reset. This reset is the mechanism used to wake the microcontroller44out of low power mode in the firmware. The IRQ pin is preferable for this function since it can be configured to be edge sensitive only, not level sensitive as the reset pin is.

6.6 Memory Card/CPU Card Interface

The firmware preferably supports only memory card peripherals using an Integrated Circuit Protocol (e.g. the I2C protocol). Alternatively, the firmware can support CPU card formats.

6.7 Power Consumption

The firmware plays a critical role in conserving the life of the battery53. All operations performed by the microcontroller44are optimized so as to be performed as quickly as possible while wasting as little power as possible. As soon as the remote reader1has been inactive for a time (e.g. 1 minute) the microcontroller44suspends to low power mode to conserve battery life still further. Low power mode consumes about 1000 times less current than normal operating mode so efficient suspension to this mode is very desirable. The firmware controls the state of the microcontroller44ports during low power mode. It is very important that the low power state be carefully tested, one bit of one port incorrectly set during low power mode can easily halve the battery life.

6.8 Device Programming

The microcontroller44is able to be programmed using an In-System program (ISP) function supported by an embedded monitor within the microcontroller44. Monitor code is typically factory set by a manufacturer and cannot be altered.

Programming of the microcontroller44for specific hardware can be performed using an In-Circuit Simulator (ICS) kit and a monitor-mode download cable. This cable uses the VCC, GND, RST, IRQ and PTB0 pins on the microcontroller44. Source code to be programmed can be delivered from a Windows™ 95 development environment via a computer serial port to the ICS hardware and from there via the download cable to the microcontroller44pins. This programming method is ideal for firmware development and testing, but may be altered for mass production.

A monitor-mode programming model is preferred in the microcontroller and an embedded programming jig for production can be used. Test points for programming signals can be provided to allow for production ISP. If the firmware is mask programmed into the microcontroller44then device programming will not be required.

6.9 Firmware Programming Sequence

The programming of the firmware will be described with reference to the reader1being operative coupled to a local computer100.

6.9.1 The Main Loop

FIG. 25is a flow diagram showing the read process2500performed by the remote reader1in accordance with the arrangements described herein. The process2500is preferably implemented as software being resident on the reader1, and being read and controlled in its execution by the CPU45. The process ofFIG. 25is configured in a “paced loop” manner. That is, the process is paced by a routine, which generates a 10 ms delay. This delay gives adequate service to the necessary routines while providing good latency for the handling of interrupts.

The process2500begins after a reset event, as described above, has been generated. At the first step2600, an initialization routine is performed by the CPU45. The initialization routine is performed in order to initialize configuration registers and will be explained below with reference to flow diagram2600. At the next step2501, the computer operating properly (COP) register is cleared indicating that the firmware is not stuck in any recurring loops. The process2500continues at the next step2700where a check card process is performed, by the CPU45, to check for any changes in the presence and validity of a particular smart card10. The check card process2700will be explained in more detail below with reference toFIG. 27. At the next step2800, a scan touch panel process is performed by the CPU45to check for any touches on the touch panel8by the user. At the next step2900, a wait 10 ms process is performed by the CPU45, and the process2500then returns to step2501.

6.9.1 The Initialization Process

After a reset from any one of the five sources described above all configuration registers require correct initialization. If an LVI reset was received then a “possibly depleted battery” flag is set.FIG. 26is a2600showing a process2600for initializing the systems600A and600B in accordance with the arrangements described. The process2600is preferably implemented as software being resident on the reader1, and being read and controlled in its execution by the CPU45. The process2600begins at step2601where all registers are initialized to a predetermined default state. At the next step2602, a check is performed by the CPU45to determine if the reset was an LVI reset. If the reset was not an LVI reset at step2602, then the process2600concludes. Otherwise the process2600proceeds to step2603where the possibly depleted battery flag is set and then the process2600concludes.

6.9.2 The Check Card Process

FIG. 27is a flow diagram showing the process2700for checking the card10. As described above, the process2700checks for changes in the presence and validity of a smart card10in the remote reader1and responds accordingly. The process2700is preferably implemented as software being resident on the reader1, and being read and controlled in its execution by the CPU45. The process2700begins at step701where if a smart card10is inserted in the remote reader1, then the process2700proceeds to step702. At step702, if the card10is a new card (i.e., the previous state such that there was no card in the reader1), then the process2700proceeds to step703. Otherwise, the process of2700concludes. At step703, the “magic number” and “checksum” are read from the card header stored in the memory19of the card10and are checked for correctness. If the “magic number” and “checksum” are correct, then the process2700proceeds to step704. At step704, the distinguishing identifier is read from the card header and the “No MOVE events” and “No Event Co-ordinates” flags are set. The process2700continues at the next step705, where an INSERT message is sent to computer100, and the INSERT message is processed by the CPU205. At the next step706, a “BEEP” is sounded and the process2700concludes.

If the “magic number” and “checksum” are not correct (i.e.: card is not valid) at step703, then the process2700proceeds to step710where the don't beep, no move events and event co-ordinate flags are set. At the next step711, a BAD CARD message is sent to the computer100, and the BAD CARD message is processed by the CPU205. At the next step712, a “BOOP” is sounded and the process2700concludes.

If a smart card10is not inserted in the remote reader1at step701, then the process2700proceeds to step707. At step707, if this is the first operation of the reader1after the reset then the process2700concludes. Otherwise, the process2700proceeds to step708where the “Don't beep”, “No MOVE Events” and “No Event Co-ordinates” flags are set and the distinguishing identifier is set to “NO_CARD”. At the next step709, a REMOVE message is sent to the computer100, and the REMOVE message is processed by the CPU205. The process2700concludes after step709.

6.9.3 The Scan Touch Panel Routine

FIG. 28is a flow diagram showing the process2800for scanning the touch panel8of the reader1. As described above, the scan touch panel process2800checks for touch panel touches that equate with card button presses and responds accordingly. The process2800is preferably implemented as software being resident on the reader1and being read and controlled in its execution by the CPU45. The process2800begins at step801where if the panel8is being touched, then the process2800proceeds to step802. Otherwise, the process2800proceeds to step812, where if the panel8has been touched previously then the process2800proceeds to step813. Otherwise, the process2800concludes.

At step813, the “don't beep”, “no move events” and “event co-ordinate” flags are set. At the next step814, the message type is set to RELEASE and the process2800proceeds to step805. The process2800continues at the next step802, where if this is the first time that the touch has been detected by the CPU45since there was no touch, then the process2800proceeds to step803.

At step803, the CPU45determines if a bad card has been inserted by checking the result of step703. In the case that a bad card has been inserted into the reader1, the process2800proceeds to step815. Then at step815, a BAD CARD message is sent to the computer100, the BAD CARD message is stored in memory206, and the process2800concludes. If the CPU45determines that the card10was valid, at step803, by checking the result of step703or that no card was inserted into the reader1by the checking of step701, then the process2800proceeds to step804. At step804, the type of message is set to PRESS in a message header as seen inFIG. 19.

The process2800continues at the next step805, where the CPU45determines the touch coordinates (i.e. X, Y coordinates of user press location) via the touch panel interface41. At the next step807, the offset and scale coordinates are determined. The offset and scale coordinates, map the coordinate space of the touch panel8to the coordinate space of the card10.

The process2800continues at the next step807, where if the CPU45determines that the set message was a MOVE and/or no card was inserted, by checking step701, then the process2800proceeds directly to step809. Otherwise, the process2800proceeds to step808and the memory19of the card10is searched in order to match the touch coordinates determined at step805with the X,Y value of each UI object (see inFIG. 17). Data associated with the matched UI object is read from the card10by the CPU45. At the next step809, the message is sent along with any data to the associated computer100, and the CPU205in the computer100processes the message. The process2800continues at the next step811, where a BEEP sound is sounded and the process2800concludes.

If the CPU45determines that this is not the first time that the touch has been noticed since there was no touch, at step802, then the process2800proceeds to step816. At step816, if the touch detected at step801was a move, then the process2800proceeds to step817. Otherwise, the process2800concludes. At step817, the message type is set to MOVE and the process2800proceeds to step805. For example, a MOVE message as defined byFIGS. 19 and 22is sent along with the X, Y coordinates of a touch position, a PRESS and RELEASE message as defined byFIGS. 19 and 23is sent along with X, Y coordinates of touch position and data associated with the UI object (e.g. one of the indicia14). If the CPU45determines that the message was MOVE, at step807, then the CPU45sends MOVE message to the computer100at the next step809. Then the CPU205processes the X, Y coordinates as cursor information and moves a cursor that is displayed on the Video Display101.

Further, if NO Event Coordinates (seeFIG. 13) have been set in the card10, the reader1can send the data associated with the UI object to the event manager301in the computer100or STB601without sending X, Y coordinates of the touch position.

Still further, if the application304has a UI Object structure (seeFIG. 17) and can perform a matching function as executed at step808of the process2800, then the reader1may send X, Y coordinates corresponding to a touch position to the application304.The can then CPU205execute the same matching function to read data associated with the UI object from the event manager301and provides a service (e.g. game) to a card user as identified by a service identifier corresponding to the data. For example, at step4205of the process4200, as seen inFIG. 41, the CPU205reads any data in the data field of the message and then processes the data in accordance with the process2800described above, at the next steps ofFIG. 41. If there is no data in the data field, the CPU205reads X,Y coordinates from the message and executes the matching function for the coordinates to determine data associated with user pressed indicia. Alternatively, the event manager301, using the UI object structure available to the event manager301can perform such a matching function.

Accordingly, if a card user can use the reader1, without inserting the card10, as a mouse by moving his or her finger on the touch panel8. In this manner, the user can select a STB service on a STB menu displayed on a TV116display. Also, if the card user uses the reader1with a card10inserted and selects some indicia14, the user can receive a service (e.g. game) from computer100or STB601. For example, if the user selects START indicia, a desired game is executed in the computer100or STB601and an object in the game kicks a ball according to a selection of KICK indicia24.

Further, by pre-defining per-card flag values in the card10, various types of cards (e.g. card10) can be provided to a user. For example, if a flag, “NO Move Events”, has been pre-set in the card10, a mouse function is not given to reader1and the reader1can not perform as a mouse based on the flag setting. On the other hand, if the flag, “NO Move Events” has not been pre-set in card10, such a mouse function is given to reader1and the reader1can perform as a mouse based on the flag.

As seen inFIG. 13, although the default is that the reader1provides audio feedback, acts as a mouse and sends coordinates for press, release and move events, the default may alternatively be that the reader1does not provide audio feedback, act as a mouse and send coordinates for them. Per-Code Flag Values defines that some function (Beep Function, Mouse Function and Matching Function).

Therefore, if the beep function is given to the reader1by the per-card flag values, the reader1sounds a “beep” and the CPU45can execute the processes2700and2800as seenFIGS. 27 and 28. Further, if the Mouse Function is given to reader1by the per-card flag values, the reader1can act as a mouse and the CPU45can execute the processes2700and2800as seen inFIGS. 27 and 28. Still further, if the Matching Function is given to the reader1by the per-card flag values, the reader1can send coordinates corresponding to a press, release and move event executing the processed2700and2800and can further perform the matching function (i.e., step808) in event manager301. For example, the card10may be a card having only a mouse function and/or a basic function (e.g., sending to the EM301data associated with indicia selected by a user). By combining each of the per-card flag values randomly, various types of cards can be provided to a user.

By sending at least a service identifier in the distinguishing identifier to the event manager301, a service can be provided to a card user, since the service identifier is an indispensable identifier for the system600. A service specific identifier can be preferably set by a vendor for use with an application associated with the vendor. Therefore, if the vendor defines a unique service specific identifier for each card, the card would be unique. If the service specific identifier is being used to provide information about the means by which cards were distributed (e.g. by mail, hand out on train, etc.), the service specific identifier can be added to a file which gives a record of which cards have been used to access the service for later use in determining how effective different distribution means have been.

6.9.4 The Wait 10 ms Process

FIG. 29is a flow diagram2900showing a wait 10 ms process2900. The wait 10 ms process2900loops so as to consume CPU cycles until 10 ms has elapsed. The process2900is preferably implemented as software being resident on the reader1and being read and controlled in its execution by the CPU45. The process2900begins at step901where a predefined process counter is cleared. At the next step902, the counter is incremented. At the next step903, if 10 ms has not elapsed, then the process2900returns to step902. Otherwise the process2900concludes.

7.0 Event Manager

The event manager301is one of the most important of the process components of the software architecture200. The event manager301enforces the rules of the architecture200and ensures consistent behavior between the other process components.

7.1 Role in the System

Most communications pass through the event manager301and the event manager301is the only part of the architecture200that all process components except the directory service311components need to be able to directly communicate with. The event manager301acts as the enforcer of the rules of the architecture200, and the event manager301does not necessarily have to be configured as one distinct software program. The event manager301can also be formed of trusted relays or other separate process components that perform part of the event manager role. This can be done for efficiency or security reasons for example.

The event manager301may incorporate various other parts of the software architecture200such as the I/O daemon300and the launcher303. The event manager310may even incorporate an application such as a browser controller.

The event manager301can communicate with every process component of the system600except the directory service311either directly or through a trusted relay. These components include the I/O daemon300, launcher303and any of the applications304. The event manager301can use any suitable communications method to communicate with the other process components. The preferred communication method is Transmission Control Protocol/Internet Protocol (TCP/IP) due to it's nearly universal implementation but other OS specific methods, such as Unix™ sockets, etc can also be used. When the process components are integrated together the method used to communicate could be internal data passing between separate threads.

The event manager301is preferably configured to be immune to interference from other process components. This includes other processes being able to kill the event manager301or being able to starve the event manager301of CPU time or network bandwidth. This is to ensure that the event manager301can remain in ultimate control of the system600.

7.2 Internal Requirements

The event manager301must do non-blocking I/O to all the other process components300,303,304and306of the architecture200by methods such as polling (NB: polling is not recommended due to the CPU load), interrupt driven I/O, having a separate thread reading and writing from each component or any other suitable method that achieves the same goal. This is to ensure that one component is not starved out by another component, which also generally reduces user wait time.

The event manager301must also check all incoming data for validity and repair the data if possible before output. This includes data from trusted components. The event manager301should also be fail safe. If the event manager301receives unexpected data from one of the components300,303,304, or306, then the event manager301should deal with the data and not exit unless it is absolutely unavoidable.

The event manager301can be required to be running for a considerable length of time and it is configured so as to ensure that performance does not degrade over time. The event manager301is preferably configured to assume that the transmission mechanism is reliable for communication with any component that is using a predetermined em-protocol but must assume that the transmission mechanism used to communicate with the remote reader1, via the I/O daemon300, is unreliable and parts of the incoming data may be incorrect or missing.

The event manager301is a direct participant in some of the operations of the system600but also transparently takes part in many of the other operations of the architecture200. The event manager301is transparent in that it uses data packets as they pass through it without modifying them. The procedures will be explained in more detail below particularly with reference to section 8.0.

FIG. 30is a flow diagram showing an overview process3010performed by the system600in accordance with the arrangements described. The process3010is executed by the CPU205depending on the configuration of the system600. The process3010begins at step3000where a system initialization routine is performed, which includes starting the event manager301. At step3000the I/O daemon is typically also started with the event manager301.

At the next step3700the event manager301starts the launcher303. At the next step3300, the event manager301passes a message to the launcher303, which enables the launcher303to determine which application304to execute, and the launcher303then starts the corresponding application304. At the next step3400, once the currently running application304is no longer needed, for instance, when a new card10is inserted into the reader1, the launcher303provides an exit message to the running application to end the execution of the running application. All applications are terminated when the system600is powered down (or switched off).

FIG. 31is a flow diagram showing a process3000performed by the event manager301. The process3000can be executed by the CPU205for computer implementations. Alternatively, the process3000can be executed by the CPU4305in set top box implementations. The process3000begins at step3101, where the launcher303is started. At the next step3103, the event manager301receives an event. If the event received at step3103is not from the remote reader1at the next step3105, then the process3000proceeds to step3107where the component identifier is checked and corrected if necessary. At the next step3109, if the new application sending an event is allowed to send the event, then the process3000proceeds to step3111. At step3111, the event is sent to a destination process component and the process3000returns to step3103. If the sending application is not allowed to send the event at step3109, then the process3000proceeds to step3113, where the event is dropped and the process3000returns to step3103.

If the event is not from the remote reader1at step3105, then the process3000proceeds to step3115. If the event is a BADCARD, LOWBAT, INSERT or REMOVE event at step3115then the process3000proceeds to step3117. Otherwise the process3000proceeds to step3119. At step3117, the event is passed to the launcher303and the process3000returns to step3103. If the distinguishing identifier is the NO_CARD identifier at step3119, then the process3000proceeds to step3117. Otherwise the process3000proceeds to step3121, where if the service identifier is not the same as that which has been used to determine the front application, then the process3000proceeds to step3117. Otherwise, the process3000proceeds to step3123, where the event is sent to the front application and the process3000returns to step3103.

7.4 Focus Change

The event manager301can safely ignore any EM_LOSING_FOCUS events that are not for the currently front application. The event manager301needs to watch for EM_GAINING_FOCUS messages for which applications becoming the front application as well as the service identifiers that are associated with that application. The event manager301can safely ignore multiple EM_GAINING_FOCUS events that are to the same application with the same service identifier as well as any EM_LOSING_FOCUS events to applications that are not the currently front application. Messages that are ignored are passed on as normal.

7.5 Reader Messages

The event manager301is also responsible for distributing the messages to the correct component. The event manager301is configured to follow the certain predetermined protocol rules, which will be described in detail below.

7.6 Restrictions on Sending Messages

A further role of the event manager301is to enforce predetermined restrictions on the transmitting of messages.

8.0 Event Manager Protocol

The event manager protocol (EM-protocol) is the protocol used to communicate between all components of the architecture200except for the directory service311. Generally all messages are configured to go through the event manager301before being passed onto an intended recipient. The EM-protocol is a datagram based protocol that is implemented on top of a reliable communications protocol, for example, Transport Control Protocol/Internet Protocol (TCP/IP). The event manager301is configured to assume that all data being sent will arrive unchanged and in the correct order. The event manager301does not assume that there is a reliable method of synchronization between the process components of the architecture200.

All multi-byte values are sent in Internet byte order (i.e. big-endian). The exception to this is the ‘distinguishing identifier’ values representing services, which are sent as blocks of several single bytes and are always treated as such (i.e. the distinguishing identifier values are never stored as a number due to byte ordering issues).

8.1 Communication Methods

The event manager protocol is preferably configured to assume a TCP/IP like method of communication between the components of the architecture200and the system600hardware components. Alternatively, any known method of communication that ensures reliable transport can be used. For example, an operating specific method such as ‘Unix sockets’ can be used. The data can be passed between the process components301,303,304and306directly via internal data structures in a multi-threaded application, for example.

In the case of architectures where an alternative method of communication between the components is being used, the problem of byte-ordering must be taken into account. If it is possible that applications can run on a machine that has different byte orderings or is required to communicate with components that expect the data in network byte order, which all components assume by default, then all affected communications can be done in network byte order.

8.2 Data Format

8.2.1 Basic Data Types

Some abbreviations that are used in the following paragraphs to refer to data types are as follows:

Every addressable process component in the architecture200is assigned a 32 bit unsigned value referred to as an ‘xid’ (or component identifier). This number is unique within the boundaries of each individual system600instance. Some xids of the process components are always the same. These are:

The xid value is divided up into a one byte type field and a three byte identifier. The different types are shown in Table 1 below.

TABLE 1ValueTypeInternal xid'sThese xid values are not routableand can be used internally by allcomponents. They are dropped ifseen by the EMCore System xid'sThese identify the core systemcomponents of a UICard system.These components include the EM,Launcher and Master Launcher.Standard UICard ApplicationThese identify standard applicationsthat are started and ended by theLauncher as needed.Special UICard applicationThese identify special applicationsthat aren't controlled by thestandard rules for starting andending applications. They areapplications that are writtento provide the UICard system withfunctionality that canbe controlled by other applicationssuch as a video on demand playeror a browser controller.ReadersReaders are assigned xids by the EM.These xids are unique to eachreader that is used to accessthe system for the durationof the EM. If the event managerand therefore the system isrestarted then the reader xidswill change.
8.3 Message Types

There are twenty-two core messages in the EM-protocol, which in the arrangements described herein have the following labels:EM_NEW_LAUNCHEREM_KILL_LAUNCHEREM_APP_REGISTEREM_EXIT_NOWEM_CLOSEEM_APP_STARTINGEM_APP_DYINGEM_GAINING_FOCUSEM_LOSING_FOCUSEM_LIST_MESSAGESEM_LIST_APPSEM_SEND_MESSAGEEM_POST_MESSAGEEM_GET_MESSAGEEM_DELETE_MESSAGEEM_READER_INSERTEM_READER_REMOVEEM_READER_BADCARDEM_READER_MOVEEM_READER_PRESSEM_READER_RELEASEEM_READER_LOW_BATT

These messages will be explained in more detail in the following paragraphs.

8.3.1 Message Header

The messages sent within the system600have a header portion preferably including the following information:version: This represents the version number of the protocol being used by the component. Version should always be set to EM_PROTOCOL_VERSION which is defined in library headers to be the version used by the library.type: This represents the type of message that this header proceeds and is set to one of the message types listed above and described below. The length of the messages is assigned the label dataLength.reserved: This represents that the value in these two bytes is reserved and should be set to zero.timestamp: This represents the timestamp of a data packet.to_xid: This represents the destination xid of the particular packet. This is the final destination of the packet and should only be set to the event manager if that is the intended final recipient.from_xid: This represents the source xid of the packet.dataLength:This represents the length of the data that follows the header. This value can be zero. Different types of messages impose different requirements on the data following the message header. Components should not assume the length of a message from the type. The number of bytes in the dataLength field is always read even if this is different to the correct size of the message to insure that the stream can only be corrupted by an incorrect dataLength.
8.3.2 EM_NEW_LAUNCHER

The EM_NEW_LAUNCHER message is sent when the event manager301requires a new launcher303. This message is only sent between the event manager301and a master launcher if the arrangement includes such a master launcher. The packet containing this message also contains information that a new launcher needs to connect to the event manager301. The EM_NEW_LAUNCHER message preferably includes the following information:port: This represents the port number that the event manager301is listening for new connection on.host: This represents the host name of the machine running the event manager301.
8.3.3 EM_KILL_LAUNCHER

The EM_KILL_LAUNCHER message is sent when the event manager301wants the master launcher (if the arrangement includes a master launcher) to kill the current launcher303. The EM_KILL_LAUNCHER message has no data associated with it.

The EM_APP_REGISTER message is sent, when an application is starting up, to the launcher303and informs the rest of the components of the architecture200that it is now ready to receive messages. Any messages that an application304sends before it has registered will be discarded by the event manager301.

The EM_APP_REGISTER message preferably includes the following information:xid: This represents the component identifier that was assigned to the application by the associated launcher303.

The remainder of the information sent can not be represented by the structure as the remaining fields are of variable length. The data following the xid is a series of null terminated strings with a maximum length of 256 characters not including the terminating null, consisting of the lower and upper case characters a–z, the numbers 0–9 and the characters (.,-_). If the strings are longer than 256 characters the strings will be truncated at 256 characters.Application Name: This represents a name that is used to identify the present application to other applications.Service Group: This represents one or more names of service groups that the application wishes to be a part of.

An application that is persistent, such as a browser controller, only needs to register once. It does not need to register everytime it gets an EM_GAINING_FOCUS event.

The EM_EXIT_NOW message is sent by the launcher303to an application when the application is about to be forced to exit. The EM_EXIT_NOW message has no data associated with it.

The EM_CLOSE message is sent to persistent applications to indicate that the current session is closed and to return the application to its startup state. Once this message is received by an application the application is required to treat the next EM_GAINING_FOCUS event as the start of a new session rather than as a change in input/output focus. The EM_CLOSE message has no associated data.

The EM_APP_STARTING message is sent by the launcher303to the event manager301when an application is about to start. The EM_APP_STARTING message preferably includes the following information:xid: This represents the component identifier of the application that is about to start.
8.3.8 EM_APP_DYING

The EM_APP_DYING message is sent by the launcher303to the event manager301when an application has exited. The EM_APP_DYING message is sent only after the launcher303is certain that the application has finished. The EM_APP_DYING message preferably includes the following information:xid: This represents the component identifier of the application that has exited.
8.3.9 EM_GAINING_FOCUS

The EM_GAINING_FOCUS message is sent to an application by the launcher303when the application304is about to start receiving input from the remote reader1. The EM_GAINING_FOCUS message preferably includes the following information:id: This represents the distinguishing identifier of the remote reader1messages that will be sent to an application.Data: This represents extra data that is to be sent to the application when it is about to receive focus. The extra is specific to each service and it is up to the application to interpret the data. The extra data is not checked for byte ordering issues and this should be dealt with by the application. Any multi-byte data is sent by applications in network byte order and is assumed to be in this order by the receiving application. An example of this data when the receiving application is a browser controller is a URL which the browser controller is a URL which the browser controller is being instructed to load.
8.3.10 EM_LOSING_FOCUS

The EM_LOSING_FOCUS message is sent when an application304is about to lose input/output focus from the remote reader1and the display101. The EM_LOSING_FOCUS message has no extra data.

The EM_LIST_APPS message is sent when an application wishes to know what other applications are also running at a point in time. The EM_LIST_APPS message is returned to the application with the data field containing the application list. This message does not need to be addressed to any of the process components301to306. The event manager301ensures that the EM_LIST_APPS message is sent to the correct component, which is usually the launcher303, regardless of the to_xid field of the header. It is the role of the receiving component to decide which applications to list.

The EM_LIST_APPS message has two formats. The first is the format used when the EM_LIST_APPS is sent as a request and the second is the format when it is sent as a reply. The request has no extra data associated with it.

The EM_LIST_APPS message preferably includes the following information:app_xid: This represents the xid of the application being described.app_desc: This represents the name string given to the launcher303when the application first registers.
8.3.12 EM_SEND_MESSAGE

The EM_SEND_MESSAGE message can be sent between any two concurrently running applications in the system600. There is no structure imposed on this message by the architecture200but communicating applications need to agree on a common data structure.

The EM_LIST_MESSAGES message is used to get a list of all messages currently on a message board used in accordance with the arrangements described. The message board will be described in more detail below with reference to section 8.4.7. 1. The EM_LIST_MESSAGES message should be sent to the launcher303. The EM_LIST_MESSAGES message has a request and reply format. The request format has no data associated with it. The reply preferably includes the following information:message_count: This represents the number of messages currently on the message board and can be equal to zero.messages: This represents a variable number (i.e. equal to message_count) of variable sized structures that have the following structure:

Each message preferably includes the following information:message_id: This represents the message identifier of this message.poster_id: This represent the xid (component identifier) of the component that posted this message.mime_type: This represents the Multipurpose Internet Mail Extension-type (MIME-type) of the data associated with this message and is a null terminated string which can be of zero length in which case the terminating zero is still present.message_desc: This represents the description of this message that was assigned when the message was posted by the posting application and is a null terminated string that is at most 255 characters long not including the terminating zero. The length of this string can be zero in which case the terminating zero is still present.
8.3.14 EM_POST_MESSAGE

The EM_POST_MESSAGE message is used to post some data to the message board of the architecture200. These messages last until there is a service group change and can be accessed by any application that is running. The EM_POST_MESSAGE messages can also be deleted by any currently running application and are not assumed to be totally reliable. Once the message has been posted it is returned to the application that posted it to inform said application of the message identifier of the message. These messages are sent to the launcher303by the application. The message from the application (i.e. the application that posted the message) includes the following information:message_desc: This represents a description of the message and is a null terminated string that can be at most 255 characters long not including the terminating zero. The description can be zero bytes in length but must still have a terminating zero.mime_type: This represents the MIME type of the message data that is being posted. The MIME type is not required but there must still be a terminating zero.message_data: This represents the data to be posted to the message board.

The message returned to the application preferably includes the following information:message_id: This represents the message identifier by which this message can be retrieved or deleted.
8.3.15 EM_GET_MESSAGE

The EM_GET_MESSAGE message is used to retrieve a message from the message board. The EM_GET_MESSAGE message is sent containing the message identifier of the message that the component wishes to retrieve and it is returned to the component either containing the message or an error that there is no message with that identifier. These messages are sent to the launcher303by an application.

The information included when requesting the message is as follows:message_id: This represents the message identifier of the message the application wishes to retrieve.flags: This is a flags word. All unused bits should be set to zero. The flag shown in Table 2 is defined:

TABLE 2FlagDescriptionValueEM_GM_DELETEDelete the message from0 × 01the message board afterit has been sent
The reply has the following information:error: If an error occurred then this will be set to one of the values in Table 3 below.

The EM_DELETE_MESSAGE message is used to delete messages from the message board. It is not an error to delete a message that does not exist. These messages are sent to the launcher303by the front application. The EM_DELETE_MESSAGE preferably includes the following information:message_id: This represents the message identifier of the message that is to be deleted.
8.3.17 User Interface (UI) Card Reader Messages

The UICard reader messages are generated by the remote reader1and are encapsulated by the event manager301so that they conform to the event manager protocol. There are three types of messages that are generated by the remote reader1. These messages are “simple” messages, “move” messages and “press/release” messages. Move messages are simple messages with co-ordinates added, and press/release messages are simple messages with data and coordinates added.

8.3.17.1 Simple Messages

The following messages are simple messages:EM_READER_INSERTEM_READER_REMOVEEM_READER_BADCARDEM_READER_LOW_BATT

These simple messages preferably include the following information:id: This represents the distinguishing identifier that was sent by the remote reader1and the value of id has no meaning for BADCARD messages.
8.3.17.2 Move Messages

The EM_READER_MOVE messages preferably includes the following information:id: This represents the distinguishing identifier that was sent by the remote reader1, and is set to all zeros for no card messages.X: This represents the x value.Y: This represents the y value.
8.3.17.3 Press/Release Messages

EM_READER_PRESS and EM_READER_RELEASE messages preferably includes the following information:id: This represents the distinguishing identifier that was sent by the remote reader1.x: This represents the x value.y: This represents the y value.data: This represents any data that was associated with the press or release (associated with the UI-element data).
8.4 Procedures

The following paragraphs describe the main procedures that each process component follows in accordance with the described arrangements.

8.4.1 Starting a New Application

FIG. 32is a flow diagram showing detail of the process3300for starting a new application used whenever the launcher303starts a new application. The process3300can be executed by the CPU205for computer implementations. Alternatively, the process3300can be executed by the CPU4305in set top box implementations. The process3300begins at the first step3301where the launcher303performs a mapping to translate the service identifier into a URL if necessary. At the next step3303, the launcher303fetches and starts the application informing it of an event manager host-name and port number. The process3300continues at the next step3305, where the launcher303sends the event manager301an EM_APP_STARTING message informing the event manager301of the xid of the starting application. At the next step3307, the new application connects to the event manager301and sends the launcher303an EM_APP_REGISTER message. Further, there is normally a focus change to the new application.

8.4.2 Ending an Application

FIG. 33is a flow diagram showing a process3400for ending an application. The process3400can be executed by the CPU205for computer implementations. Alternatively, the process3400can be executed by the CPU4305in set top box implementations. The process3400is used whenever the launcher303terminates a running application. The process3400begins at step3401, where the launcher303sends the running application an EM_EXIT_NOW message. The launcher303sets a time out at this point to give the application a chance to exit cleanly. At the next step3403, the running application cleans up and exits. Alternatively, the application ignores the EM_EXIT_NOW message and the launcher303times out and forces the application to quit. At the next step3405, the launcher303sends the event manager301an EM_APP_DYING to tell it that the application has exited and it should discard any waiting data and close the connection to the application if the connection is still open, and the process3400concludes.

8.4.3 Closing a Persistent Application's Session

FIG. 34is a flow diagram showing a process3500for closing the current session of a persistent application. The process3500can be executed by the CPU205for computer implementations. Alternatively, the process3500can be executed by the CPU4305in set top box implementations. The process3500is analogous to the application ending but the application does not actually close. The process3500begins at step3501, where the launcher303sends the persistent application an EM_CLOSE message. At the next step3503, the persistent application resets to its initial state, and the process3500concludes. This may involve closing connections to outside servers, loading a default web page etc. The next EM_GAINING_FOCUS event that the persistent application receives is assumed to be the start of a new session.

8.4.4 Focus Change

FIG. 35is a flow diagram showing a process3600for performing a focus change. The process3600can be executed by the CPU205for computer implementations. Alternatively, the process3600can be executed by the CPU4305in set top box implementations. The process3600is used to tell an application that it is about to gain/lose input/output focus, which is not a signal for the application to exit. At the first step3601, the launcher303makes the decision to change the application that currently has input/output focus and sends the application that is to receive input focus an EM_GAINING_FOCUS event typically based on a card change. The sending of this event is used by the event manager301to decide which application should receive input/output focus based on predetermined conditions. At the next step3603, the launcher303sends the previous front application an EM_LOSING_FOCUS event, and the process3600concludes. This message is less critical and is not sent when the currently front application remains the same, but still needs the EM_GAINING_FOCUS (i.e. in the case of a browser controller where the EM_GAINING_FOCUS events are used to tell the browser controller402the base URL).

8.4.5 Message Passing

There are two distinct types of message passing between applications supported by the architecture200. The message board that is as persistent as the current service group and a direct message method where two components communicate with each other directly.

8.4.5.1 Message Board

One component of the architecture200typically the launcher303, maintains a message board and the event manager301knows which component does this. The message board is formed of a list of messages that are assigned a 32 bit unsigned number as an identifier by the process component managing the message board. The messages are formed of a text description, an optional MIME type for the message data and the message itself. An application can request a list of all messages currently on the message board by sending an EM_LIST_MESSAGES message. This will return with the text descriptions of all messages currently on the message board with their associated message identifiers. The application can then request a specific message by sending a EM_GET_MESSAGE with the message identifier of the message that it requires.

A message can be deleted between getting a listing of the message board and actually requesting a message and such will be indicated by an error field of the EM_GET_MESSAGE message.

8.4.5.2 Direct Communication

Two applications can send each other arbitrary data directly by using direct communication. This is performed by one application sending the other application the data by using an EM_SEND_MESSAGE message. The two applications need to agree on a data format for these messages and byte ordering issues need to be taken into account. To get the component identifier of the other application, an application can request to be sent a list of all running applications by sending an EM_LIST_APPS message which returns a list of all publicly visible applications that are currently running.

8.5 Reader Messages

This section outlines the rules used by the event manager301to route the EM_READER_* messages. The following messages are always sent to the launcher303regardless of which application currently has focus.EM_READER_INSERTEM_READER_REMOVEEM_READER_BADCARDEM_READER_LOW-BATT

The following messages are sent to the currently front application if the messages are from cards (e.g. the card10) that have the same service identifier as the currently front application. A service-specific identifier is not taken into account in this comparison. If the service identifier is different to the currently front application or the distinguishing identifier is the NO_CARD present value (i.e. all zeroes) then the message is sent to the launcher303.EM_READER_PRESSEM_READER_RELEASEEM_READER_MOVE
8.6 Restrictions on Sending Messages

To improve the security and stability of the system600there are preferably restrictions placed on the sending of messages. Any messages that breach these rules will be discarded by the event manager301.

8.6.1 Restrictions for All Components

No component except the remote reader1will be allowed to send EM_READER_* messages.

8.6.2 Restrictions on the Event Manager

The event manager301is the enforcer of the rules and as such can send any messages necessary. The event manager301is configured to generate EM_KILL_LAUNCHER and EM_NEW_LAUNCHER messages but it can copy messages and send the copies to process components that are not the target component. The event manager301also handles all transmissions between components.

8.6.3 Restrictions on the Launcher

The launcher303sends messages to all components301to306of the architecture200. The messages that the launcher303can not send are as follows:EM_KILL_LAUNCHEREM_NEW_LAUNCHER
8.6.4 Restrictions on Applications

Applications only send the following messages to other applications (which includes the launcher303):EM_APP_REGISTEREM_SEND_MESSAGEEM_LIST_APPSEM_POST_MESSAGEEM_GET_MESSAGEEM_DELETE_MESSAGEEM_LIST_MESSAGES
8.7 Component Procedure Lists

This section lists the functions which each major component of system600is involved in.

8.7.1 Event Manager

The event manager301is a direct participant in the following procedures:System InitializationSystem StartupStarting a new ApplicationEnding an ApplicationFocus ChangeMessage PassingReader Messages
8.7.2 Launcher

The Launcher303is a participant in the following procedures:System InitializationSystem StartupStarting a new ApplicationEnding an ApplicationFocus ChangeMessage Passing (in some instances)Reader Messages (in some instances)
8.7.3 Applications

The Applications304are participants in the following procedures:Starting a new ApplicationEnding an ApplicationClosing a session if the application is persistent.Focus ChangeMessage PassingReader Messages (in some instances)
9.0 I/O Daemon

The I/O daemon300is responsible for transporting the data being sent from the remote reader1to the event manager301, and vice versa for a two-way protocol. In this connection, the I/O daemon300is configured to be able to read from the hardware of the system600either directly or through operating system drivers that interface with the remote reader1, for example, an IR link or standard serial hardware connection. The I/O daemon300is also required to listen on a TCP/IP port to wait for the event manager301to connect, at which point the I/O daemon300sends data from the remote reader1to the event manager301encapsulated in a TCP/IP stream.

The I/O daemon300does not communicate with the rest of the system600except to send the remote reader1data to the event manager301.

While the functionality of the I/O daemon300must be present in the system600, the I/O daemon300does not have to be a separate component. For example, the I/O daemon300can be integrated into the event manager301if the event manager301is running on the same machine as the hardware used to interface with the remote reader1.

The I/O daemon300is configured to run on minimum hardware for the instance where the rest of the system600is running remotely.

9.1.1 General Requirements

The platform upon which the I/O daemon300is implemented must be able to receive signals from (and optionally transmit signals to) a remote reader1. The platform also preferably has a TCP/IP stack or other reliable communications method implemented on it to communicate with the other parts of the system (i.e. the event manager (EM)301). The I/O daemon300can be required to do multiplexed I/O, and the I/O system of the architecture200is preferably configured to support such a function. The architecture200is preferably configured to assign a port that the I/O daemon300will be listening on, for example, as a command line argument.

9.1.2 Internal Requirements

The I/O daemon300is not required to understand the protocol used by the remote reader1. The I/O daemon300is only required to forward all data that it receives to any listening event manager301. The I/O daemon300is not required to correct any errors of transmission from the remote reader1unless it is supported by the transport protocol of the communications link (i.e. through error correcting codes or similar). If the transport protocol being used supports error detection but not correction then any data that does not pass the error check can be passed onto the event manager301.

9.1.3 External Interface Requirements

The I/O daemon300is preferably able to accept one or more TCP/IP connections. The data stream that is sent to the event manager301is the content of the data sent by the remote reader1. All header and footer information that is transmitted as part of the communications protocol used is preferably stripped off and the byte ordering is big endian. If the communication method of the architecture200ever becomes unusable (e.g. due to an error arising) then the I/O daemon300closes all connections as soon as error condition arises.

9.2 External Interface

The external interface (not shown) of the I/O daemon300is intentionally simplistic to allow it to be run on minimum hardware. The I/O daemon300is preferably configured in the following manner.

The I/O daemon300listens on a TCP/IP port that is specified to it in some manner, for example, by command line arguments. The exact method of informing the I/O daemon300of the TCP/IP port is implementation specific. The communications hardware used to communicate with the remote reader1is initialized if required and the method to read data that is sent from the remote reader1is configured to be ready to receive data. While the I/O daemon300is waiting for a connection, the I/O daemon300consumes the data that is being sent by the remote reader1so that when a connection is made only new data is being sent. This new data is not required to start on a message boundary.

9.2.2 Connection from an Event Manager

If a connection arrives on the TCP/IP port then the I/O daemon300is configured to accept the connection and begin transmitting any data received from the remote reader1down the connection. If the I/O daemon300is already connected to an event manager301then the I/O daemon300has two options. Firstly, the I/O daemon can accept the connection and send all data down all currently connected event managers. This option is provided for system debugging purposes. The second method is to reject the second connection and continue to send the data to the already connected em. Any encryption of the stream can be handled externally by some other method, such as port tunneling.

9.2.3 Connection from an Event Manager Closing

If at any time the connection to the event manager301is closed, then the I/O daemon300is configured to discard any data from the remote reader1that is waiting to be sent to that event manager301. If this is the only event manager connected then the I/O daemon300is configured to return to an initial startup state whereby the I/O daemon300consumes data being sent by the remote reader1and waits for a connection.

9.2.4 Unrecoverable Error is Encountered

If the I/O daemon300detects an error that cannot be dealt with and will cause the I/O daemon300to exit then the I/O daemon300is configured to close all connections to any event managers to inform the event managers that the I/O daemon300has detected an error. Examples of these errors include if the hardware that is being used to communicate with the remote reader1becomes unavailable or if the I/O daemon300receives a signal that would cause it to exit. The I/O daemon300is configured to close all connections as soon as an error is experienced.

The launcher303is the process component that enforces site specific rules such as allowed applications and basic application configuration rules. The launcher303allows the other component processes300,301,304,305and306of the system architecture200to be used in a wide range of applications from a general home set top box601to a very specific application (e.g. an automatic teller machine (ATM)). The launcher303can be specifically written for each network or installation.

The launcher303is configured with special privileges. For example, the launcher303can be configured to be the first component to connect to the event manager301as the system600starts up. Further, the launcher303receives all “LOW_BATT”, “BADCARD”, “INSERT”, and “REMOVE” messages sent by the remote reader1and also receives all “PRESS”, “RELEASE” and “MOVE” messages that originate from a card other than the smart card10that the front application is associated with at any one point in time. The launcher303also receives PRESS, RELEASE and MOVE messages with a special “NO_CARD” distinguishing identifier. The launcher303also has control over which application is the front application via the EM_GAINING_FOCUS and EM_LOSING_FOCUS events.

The launcher303is configured to decide when applications need to be started and made to exit. The launcher303is also configured to start and stop applications although this is not always the case. This role can be undertaken by another application at the instruction of the launcher303for instance in the case where the applications304are run on separate machines to the rest of the components of the architecture200.

The events that are sent to the launcher303instead of being sent to the currently front application allow the launcher303to make decisions on which application(s) are to be running at the any moment in time and being configured to force applications to exit means that the launcher303can enforce which applications are to be currently running. The launcher303is also required to inform the event manager301when it is starting and stopping applications.

FIG. 36is a flow diagram showing an overview of the process3700performed by the launcher303in accordance with the arrangements described herein. The process3700can be executed by the CPU205for computer implementations. Alternatively, the process3700can be executed by the CPU4305in set top box implementations or by the CPU of a remote server. The process3700begins at the first step3701, where the launcher303connects to the event manager301, and then continues to a next step3702where persistent applications are started. At the next step3703, the launcher303waits for an event and when an event is received the launcher303proceeds to step3705. If the event is the NO_CARD identifier at step3705, then the process3700proceeds to step3707. Otherwise the process3700proceeds to step3709. At step3707, the launcher303performs a predetermined system specific function (e.g. displays a message on the display101) in response to the NO_CARD identifier and the process returns to step3703.

If the event is a PRESS, RELEASE, REMOVE or MOVE event at step3709, then the process3700proceeds to step3800. Otherwise the process3700proceeds to step3713. At step3800, the launcher303changes the application and the process3700returns to step3703. The process3800of changing an application performed by the launcher303will be described below with reference to the flow diagram ofFIG. 37

If the event is a BADCARD or LOW_BATT event at step3713, then the process3800proceeds to step3715. Otherwise the process3800proceeds to step3717. At step3715, the launcher303gives the user some feedback (e.g. displaying a “Low Battery” message on the display101) and the process3800returns to step3703.

If the event is an APP_REGISTER event at step3717, then the process proceeds to step3719. Otherwise the process3800proceeds to step3725. At step3900, the application is registered (i.e. the application informs the other components301,302and306that it is now ready to receive messages, as described above with reference to section 8.3.4) and the process3800returns to step3703. A process3900of registering an application in accordance with step3900, will be described in more detail below with reference to the flow diagram ofFIG. 38. At step3725, the event is discarded and the process3700returns to step3703.

FIG. 37is a flow diagram showing the process3800for changing an application, which is performed by the launcher303. The process3800can be executed by the CPU205for computer implementations. Alternatively, the process3800can be executed by the CPU4305in set top box implementations or by the CPU of a remote server. The process3800begins at step3817, where if a REMOVE message has been received by the launcher303then the process3800proceeds directly to step3813. Otherwise, the process3800proceeds to step3801. At step3801, if the service represented by the event is registered, then the process3800proceeds directly to step3819. Otherwise, the process3800proceeds to step3803, where a service identifier lookup is performed to determine the name of the new application and any initial data associated with the new application. At the next step3805, if the application is new the process3800proceeds to step3819. Otherwise, the process3800proceeds to step3809, where the application is retrieved from the applications304. At the next step3811, the new application is started as the front application, and at step3812the event manager301is notified of the component identifier of the front application.

At step3819, if an INSERT message has been received by the launcher303then the process3800concludes. Otherwise, the process3800proceeds to step3807, where the new application is sent a GAINING_FOCUS event indicating that the new application will soon be changing state. At the next step3813, if there is no previously front application, then the process3800concludes. Otherwise, a LOSING_FOCUS event is sent to the previous front application enabling the previous front application to complete immediate tasks, and the process3800concludes.

FIG. 38is a flow diagram showing the process3900of registering a new application, which is performed by the launcher303. The process3900can be executed by the CPU205for computer implementations. Alternatively, the process3900can be executed by the CPU4305in set top box implementations or by the CPU of a remote server. The process3900begins at step3901, where a new service group list, including the new application is generated. At the next step3903, a GAINING_FOCUS event is sent to the new application. At the next step3905, if any applications are not part of the new service group and are not persistent, then the process3900proceeds to step3907. Otherwise the process3900concludes. At step3907, any applications which are not part of the service group are sent an EXIT_NOW event, and the process3900proceeds to a next step3908where the event manager301is notified that the applications have terminated. The process3900then concludes.

FIG. 39is a flow diagram showing the process4000performed by an application when receiving events from the launcher303. The process4000can be executed by the CPU205for computer implementations. Alternatively, the process4000can be executed by the CPU4305in set top box implementations or by the CPU of a remote server (e.g. the servers150,152. The process4000begins at step4001, where the launcher303connects to the event manager301and then proceeds to step4002. At step4002, the application is registered by sending an APP_REGISTER message to the launcher303. At the next step4003, the application waits for events and when an event is received the process proceeds to step4005. If the event is a GAINING_FOCUS event at step4005, then the process proceeds to step4007. Otherwise the process4000proceeds to step4009. At step4007, the application is initialized if necessary, optionally using the distinguishing identifier and the process4000returns to step4003.

If the event is a PRESS, RELEASE or MOVE event at step4009, then the process4000proceeds to step4011. Otherwise the process4000proceeds to step4013. At step4011, an application specific action is performed in response to the event. The application specific action is performed using data from the event (i.e. data associated with an indicia on the card10, (e.g. URL, character or video name)), the X/Y position or distinguishing identifier or any combination of these.

The application specific action is typically associated with indicia on the card10. For example, an indicia can be associated with a particular URL and when the indicia is pressed the URL may be accessed. Therefore, the computer100or STB601, for example, can download desired programs from a Web Page that was designated by the URL and a card user can receive the service (i.e. program download) from the system600. Further, an indicia can be associated with a particular memory address and when the indicia is pressed the address can be accessed. Therefore, for example, the computer100or STB601can download desired image data from memory or from a file server on a network, which was designated by the memory address and a card10user can receive the service (e.g. image data download) from the system600. After step4011, the process4000returns to step3703.

If the event is a LOSING_FOCUS event at step4013, then the process4000proceeds to step4015. Otherwise the process4000proceeds to step4017. At step4015, the application reverts to an inactive state and the process4000returns to step4003. The application may also see the data field of the GAINING_FOCUS event for initialization. This may include a URL to load, a filename to load etc.

If the event is an EXIT_NOW event at step4017, then the process4000concludes. Otherwise the process4000proceeds to step4019, where the event is ignored and the process returns to step4003.

FIG. 40is a flow diagram showing the process4100performed by the browser controller403application when receiving events from the launcher303. The process4100can be executed by the CPU205for computer implementations. Alternatively, the process4100can be executed by the CPU4305in set top box implementations or by the CPU of a remote server. The process4100begins at step4101, where the browser application sends an APP_REGISTER message to the launcher303. At the next step4103, the browser application waits for events and when an event is received the process4100proceeds to step4105. If the event is a GAINING_FOCUS event at step4105, then the process4100proceeds to step4107. Otherwise the process4100proceeds to step4109. At step4107, the application is initialized if necessary. For example, the application reads the data field of the GAINING_FOCUS message and, if the data field represents a URL, the application loads that URL. The process4100continues at the next step4121, where the distinguishing identifier is determined from the event. At the next step4123, where a Javascript call back function (preferably known as the Notify_Card_ID) is called in the current top-level document with the distinguishing identifier as the argument, and then the process4100returns to step4103. Initialization is performed on the browser controller403, by loading an initial URL into the browser application402and storing the base of the URL.

If the event is a PRESS, RELEASE or MOVE event at step4109, then the process4100proceeds to step4100. Otherwise the process proceeds to step4113. At step4200, a browser application specific action is performed in response to the event. The browser application specific action will be described in more detail below with reference to the flow diagram ofFIG. 41. After step4200, the process4200returns to step4103.

If the event is a LOSING_FOCUS event at step4113, then the process4100proceeds to step4115. Otherwise the process4200proceeds to step4117. At step4115, the browser application reverts to an inactive state and the process returns to step4103.

If the event is an EXIT_NOW event at step4117, then the process4100concludes. Otherwise the process4100proceeds to step4119. At step4119, the event is ignored and the process4100returns to step4103.

FIG. 41is a flow diagram4200showing a browser application process (i.e. step4111) in accordance with the arrangements described herein. The process4200can be executed by the CPU205for computer implementations. Alternatively, the process4200can be executed by the CPU4305in set top box implementations or by the CPU of a remote server. The process4200begins at step4201, where if the event is a PRESS event then the process4200proceeds to step4225. Otherwise the process4200proceeds to step4203, where the event is ignored and the process4200concludes. At step4225, the distinguishing identifier is determined from the event. At the next step4227, if the current page has been notified about the current distinguishing identifier then the process4200proceeds to step4205. Otherwise, the process4200proceeds to step4229, where the JavaScript call back function known as the Notify_Card_ID is called in the current top-level document with the distinguishing identifier as the argument, and then the process4200proceeds to step4205.

At step4205, data is retrieved from the event. At the next step4207, if the data is a single character then the process4200proceeds to step4209. Otherwise the process4200proceeds to step4211. At step4209, the character is sent to the browser application402, and the process4200concludes. This may be used to provide the same effect as a user pressing a key on a keyboard or a button on a conventional remote control. The current page may provide an action which is performed on receipt of a given keypress using existing methods such as those provided by Hyper Text Mark-up Language (HTML).

If the data starts with “js:” at step4211, then the process4200proceeds to step4213. Otherwise the process4200proceeds to step4215. At step4213, a JavaScript function in the current top-level document is called and the process4200concludes. The specified data may optionally include an argument for the JavaScript function. For example, the data “js:hello” would indicate that the browser controller is to call the JavaScript function “hello”, and the data “js:hello” would indicate that the browser controller is to call the JavaScript function “hello” with the argument “world”.

If the data starts with “cmd:” at step4215, then the process4200proceeds to step4217. Otherwise the process4200proceeds to step4219. At step4217, a specified browser function is called and the process4200concludes. For example, the data “print” would result in the browser controller instructing the data “back” would result in the browser controller instructing the browser to return to the previously displayed page.

If the data is an absolute URL at step4219, then the process4200proceeds to step4221. Otherwise the process4200proceeds to step4223. At step4221, the data is loaded into the browser application402as a URL and the process4200concludes.

At step4223, the data is loaded into the browser application402as a URL after the base URL has been appended, and the process4200concludes.

The description with reference toFIG. 40provides an example of an application in the form of a browser controller application. A variation on this example is a program controller, which provides control of a software program. The software program can include any program, which is normally controlled with one or more keypress events (e.g., like a keyboard keypress event or the equivalent on a game controller). The program controller is used to provide card-based control of an existing software program such as an interactive game. The program controller process behaves substantially as described with reference toFIG. 40with the following exceptions:

If the event at step4105is a GAINING_FOCUS event, then the process4100proceeds to a step of getting a Resource Locator, for the software program to be controlled, from the GAINING_FOCUS message. The process4100then proceeds to a step of getting and starting the software program specified by the resource locator. The process4100then proceeds to step4103. Further, at step4109, instead of testing for a PRESS, RELEASE or MOVE event, this particular variation in the process4100would substantially check for a PRESS event. If the event is a PRESS event, the process4100proceeds to the steps of getting the data from the event, taking the first character from that data, and effecting a keypress of that character resulting in the same effect as if a user had typed that character on a keyboard.

10.1 Special Routing Rules for the Launcher

The launcher303has a special set of routing rules and the launcher303always receives the following events:EM_REMOTE_INSERTEM_REMOTE_REMOVEEM_REMOTE_BADCARD

The launcher also receives EM_REMOTE_PRESS, EM_REMOTE_RELEASE and EM_REMOTE_MOVE messages if a service identifier does not match a currently front application or if the distinguishing identifier represents the NO_CARD present identifier (i.e. all zeroes). For the purposes of determining whether or not messages match, the service-specific identifier is ignored.

The launcher303can be configured to explicitly make itself the front application by sending itself an EM_GAINING_FOCUS event. In this instance, all messages will be sent to the launcher303regardless of the service identifier of the message. The launcher303is not required by the protocol to respond to any of these messages.

This section outlines several examples of launcher configuration.

A generic launcher can be used in an open Set-Top-Box or computer environment with broad-band Internet connectivity. In accordance with such a configuration, the launcher303assumes that there are applications that can be downloaded to a local machine or designated remote machine and run. A generic launcher can also be configured to accommodate the use of applications that use the browser402via the browser controller403.

The generic launcher can be configured to download applications as well as always running applications. The computer100running the system600preferably has a reasonably fast Internet connection available. In this instance, some of the applications304can be web pages with JavaScript that is handled by a persistent application called the browser controller402, as described above. Further some of the applications304can be designed to work together. The generic launcher preferably also assumes that the communications link used by the remote reader1is unreliable (i.e. an IR link) so messages can be lost.

10.2.2 Rules for the Generic Launcher

The following rules are the rules that are preferably used by the launcher303to define the system600.EM_REMOTE_PRESS and EM_REMOTE_RELEASE events that have the no card present identifier (i.e. all zeroes) are used as a cue that the user wishes to exit from the front application. This could result in the system600either generating a “Please insert a card” message on the display101or returning to an earlier application depending on the configuration of the system600.EM_REMOTE_BADCARD events cause the launcher303to provide the users with feedback indicating that the card is faulty.EM_REMOTE_INSERT, EM_REMOTE_REMOVE are not relied upon to provide the bounds of the session due to the unreliable communications method from the remote reader1to the event manager301.If the Launcher receives an EM_REMOTE_PRESS, EM_REMOTE_RELEASE or an EM_REMOTE_MOVE message the launcher does a service mapping and if the service identifier points at a downloadable application then that application is downloaded and run. The mapping is done by querying the Directory Server305with the service information from cards. The values returned from the Directory Server305are an application location and associated service data. The application location specifies the location of the application or a value the launcher recognises as a local application. The service data is the initialization data that is sent to the application in the EM_GAINING_FOCUS message. If the application location is empty the launcher303is configured to decide which application to use based upon the service data which will be a URL.When a new application registers with an EM_APP_REGISTER message the specified service groups are compared with the currently running set of applications and if there is no overlap then all other currently running applications are told to exit. The new application is made the currently front application (using an EM_GAINING_FOCUS event) and the previously front application is sent an EM_LOSING_FOCUS event. If this occurs and the service identifier points at a web page then the focus is changed, using an EM_GAINING_FOCUS message, to the browser controller403with the location of the web page in the data field. The data field is returned in the query that told the launcher303that the service identifier pointed at a web page. An EM_LOSING_FOCUS event is also required to be sent to the currently front application in this situation. All other applications are told to exit.
10.3 An Example Single Use System

The system600can be configured for use with a single specialized application. In this instance, the launcher303can be used where it is advantageous to have a physical token (e.g. a bank card) where part or all of the user interface can be printed onto the token. The example given here is in an automatic teller machine.

Such a system can be configured to be able to use a single or at least very limited number of cards. In this system no other applications are started regardless of the card that is entered. The launcher303takes the role of a single application as well as that of a system controller. No modifications are made to the event manager301.

A single use system can be used in an automatic teller machine for example. A bank can produce personalized bankcards with commonly used options on the cards that are used as the sole or supplementary interface for an automatic teller machine. In this instance, the automatic teller machine preferably contains an event manager such as the event manager301and other core process components of the system600. The communications link between the remote reader1and the event manager301must also be reliable in accordance with such system.

The following rules can be used by a launcher to define a single use system:Any events that do not come from cards associated with a participating bank could cause the launcher to display an incompatible card screen on the terminal.EM_REMOTE_BADCARD events are ignored.EM_REMOTE_INSERT events are used to start the transaction.EM_REMOTE_REMOVE events are used to end the transaction.EM_REMOTE_PRESS, EM_REMOTE_RELEASE and EM_REMOTE_MOVE events are treated as a user interaction. These are preferably handled directly by a launcher as that is the one application that is running.Service mappings to an external Directory Server are never done. If the card is not one that a particular ATM knows about then the card should be rejected.
11.0 General

Typically, the applications304are resident on the hard disk drive210and read and controlled in their execution by the CPU205. Intermediate storage of the programs and any data fetched from the network220can be accomplished using the semiconductor memory206, possibly in concert with the hard disk drive210. In some instances, the applications304can be supplied to the user encoded on a CD-ROM or floppy disk and read via the corresponding drive212or211, or alternatively may be read by the user from the network220via the modem device216. Still further, the software can also be loaded into the computer system102from other compute readable medium including magnetic tape, a ROM or integrated circuit, a magneto-optical disk, a radio or infra-red transmission channel between the computer module210and another device, a computer readable card such as a smart card, a computer PCMCIA card, and the Internet and Intranets including email transmissions and information recorded on websites and the like. The foregoing is merely exemplary of relevant computer readable media. Other computer readable media can be practiced without departing from the scope and spirit of the invention.

Alternatively, the process components301to306described above can be implemented in dedicated hardware as one or more integrated circuits performing the described functions or sub-functions. Such dedicated hardware is able to include graphic CPUs, digital signal CPUs, or one or more micro-CPUs and associated memories. Examples of such dedicated hardware include the set top box601for a television.

12.0 Other Variations

12.1 A Session Identifier

In the arrangements described above, the distinguishing identifier is included in every INSERT, REMOVE, PRESS, RELEASE and MOVE message sent from the reader1to the computer100or set-top box601. In a variation of the above-described arrangements, the distinguishing identifier is only sent in connection with an INSERT message. Upon insertion of a new card10, the reader1generates a session identifier. The session identifier identifies a current session of a card insertion. The session identifier, for example, can be a pseudo-random number (which can be represented with 2 bytes of data). Alternatively, the session identifier can be a number that is incremented each time a card is inserted (and reset to zero when a predetermined value is reached). In accordance such an arrangement, the reader1sends an INSERT message to the computer100or the set-top box601, which includes a distinguishing identifier as described above and a session identifier. All subsequent PRESS, RELEASE and MOVE messages need not include the distinguishing identifier but include the session identifier and UI object data or press coordinates previously described.

When using a session identifier, the system is as described with reference to the system600, except that the event manager301, when it receives an INSERT message from a reader1, stores the session identifier as the current session identifier and a distinguishing identifier as the current distinguishing identifier. When the event manager301receives a PRESS, RELEASE or MOVE message, the event manager301checks that the session identifier is equal to the current session identifier. If so, the event manager301sets a distinguishing identifier used in all messages to the current distinguishing identifier. Otherwise, if the session identifier is not equal to the current session identifier, the event manager301informs the user, via the display manager306and the display device101that a message has been received without a corresponding INSERT message. The user is then requested to remove and reinsert the card10.

12.2 Other Characteristics of a Press

The above described arrangements refer to the sending of information relating to the pressing, moving and releasing of an object (typically a finger or stylus) on the touch panel8of the reader1. However, the reader1can send additional information pertaining to an interaction touch panel8to the computer100or set-top box601for use by the system600. For example, the additional information can represent a length of time or an amount of pressure exerted upon the touch panel8as a result of a press. This additional information can be incorporated in the PRESS messages sent from the reader1to the system600and with the EM_READER_PRESS messages sent within the system600. This information is passed to an application304corresponding to the card inserted in the reader1. An application can make use of the additional information to provide, for example, an added effect on a particular action. For instance, the application can use pressure information, when associated with a press on indicia (e.g. indicia14) indicating an increase in (audio) volume, to determine an amount of increase in volume. That is, the harder the press on the indicia the higher the rate of increase in the volume and the softer the press on the selected indicia the lower the rate of increase.

Another example of the use of additional information in relation to a length of time (or duration) of an interaction with a touch panel8is described below. If a press of very short duration can to be considered as a “tap”. On the other hand, a very long duration can be considered as a persistent “holding down” of a keypress. In this instance, additional information can add an extra dimension to a mode of interacting with an instant software application. For instance, a “tap” on the touch panel8can be an instruction to the software application to select an item displayed at a current (on-screen) cursor position.

12.3 No Coordinates

In yet another variation of the above described arrangements, a PRESS and RELEASE message would not include coordinate data of a user's interaction with the touch panel8. In this instance, coordinate data can only be sent from the reader1to the system600in conjunction with a MOVE message. The advantage of this arrangement is a size reduction of messages sent by a reader1to the system600, where an applications304does not require coordinate information for mapping from coordinates to UI element data.

The above-described arrangements can be used with a one-way or a two-way protocol for communication between a reader1and a computer100or set-top box601. The description of the reader1hardware with reference toFIG. 10, and the I/O Daemon described with reference toFIG. 8andFIG. 9include a sending of information from a reader1to the computer100or set-top box601and vice versa. The sending of information back to a reader1from a computer100or set top box601can be used to change the stored data on a card10. For example, this may include changing UI object data stored on the memory chip of a smart card10. A two-way protocol can also be used to enable hand-shaking in the protocol. For example, a two-way protocol between a reader1and a set-top box601or computer100can be used so that the system600can acknowledge the receipt of an INSERT message sent when a card is inserted in the reader1. An arrangement which supports a two-way protocol should also provide an additional message in the event manager protocol, in order to allow an application to send a request to modify a portion of the stored data on a card10to the I/O Daemon300via the event manager301. The I/O daemon300can then send a message to the reader to bring about a requested action.

For instance, an arrangement of the system600having a two-way protocol can provide a security mechanism to ensure that applications could not modify cards without the permission of a user or without a system-defined privilege. In one example of such an arrangement, the event manager301presents a displayed message to a user asking if it is OK for the application to modify a currently inserted card. The user can assent to the proposal by pressing a first region of the touch panel8and dissent from the proposal by pressing a second region of the touch panel8. If the user assents to the modification of the card10the event manager301can allow the request from the application304to be passed onto the I/O daemon300and then on to the reader1. On the other hand, if the user dissents from the modification, the event manager301drops the message and the information is not sent to the reader1.

The foregoing describes only some arrangements and variations on those arrangements of the present invention, and modifications and/or changes can be made thereto without departing from the scope and spirit of the invention, the embodiments being illustrative and not restrictive.

In the context of this specification, the word “comprising” means “including principally but not necessarily solely” or “having” or “including” and not “consisting only of”. Variations of the word comprising, such as “comprise” and “comprises” have corresponding meanings.