Data exchange system comprising portable data processing units

• US 7,185,110 B2
• Filed: 04/16/2002
• Issued: 02/27/2007
• Est. Priority Date: 08/04/1995
• Status: Expired due to Fees

• Current Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Original Assignee: Sun Microsystems Incorporated (Oracle Corporation)
• Inventors: De Jong, Eduard Karel
• Primary Examiner(s): Lim; Krisna
• Assistant Examiner(s): STRANGE, AARON N
• Application Number:
  US10/122,480
• Publication Number:
  US 20020111987A1
• Time in Patent Office: 1,778 Days
• Field of Search: 718/1, 718/100, 719313-316
• US Class Current: 709/245
• CPC Class Codes: G06F 11/328 Computer systems status display G06F11/327 takes precedence
• CPC Class Codes: G06K 19/07 with integrated circuit chips
• CPC Class Codes: G06Q 20/341 Active cards, i.e. cards including their own processing means, e.g. including an IC or chip
• CPC Class Codes: G06Q 20/3576 Multiple memory zones on card
• CPC Class Codes: G07F 7/1008 Active credit-cards provided with means to personalise their use, e.g. with PIN-introduction/comparison system
• CPC Class Codes: H04L 41/50 Network service management, e.g. ensuring proper service fulfilment according to agreements
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services

Abstract

Data exchange system includes at least one portable data processing unit with data communication processing and memory units, the latter including an executive program and one or more application descriptors, each application description including at least one interaction context comprising commands, data elements, data references, procedures, access conditions, and external references; the structure of the data elements and the data references as well as other references is chosen in such a way that a very efficient use of the restricted memory space of e.g. smart cards is obtained.

Claims

1. A data exchange system comprising at least one portable data processing unit (5) comprising data communication means (14), processing means (15) and memory means (16), the memory means (16) comprising an executive program (17) and at least one interaction context (19(1) . . . 19(m)) containing the following coherent data structure:

a. a set of basic communication primitives (A(1) . . . ) which are accepted whenever the data processing unit (5) communicates with a similar unit (4), said primitives at least including a primitive used to selectively enter one of the said interaction contexts (19(1) . . . );

b. a set of procedural descriptions (C(1) . . . ) defining the actions to be performed in response to each of the accepted communication primitives (A(1) . . . ), at least comprising a first procedural description to be performed upon activating the interaction context, and a last procedural description to be performed immediately before deactivating the context;

c. a, possibly empty, set of data elements (H(1) . . . ) either permanently stored or computed, which are available for use when procedures as defined in the procedural descriptions (C(1) . . . ) are performed;

d. a, possibly empty, set of references to data elements, which references are associated to the procedural descriptions (C(1) . . . ), said data elements are also accessible to possibly further interaction contexts and are available for use when procedures as defined in the procedural descriptions (C(1) . . . ) are performed;

e. a, possibly empty, data list comprising a list of references (B(1) . . . ) to data elements which are available for explicit reference as part of a communication primitive (A(1) . . . ) to be used by the procedural description (C(1) . . . ) associated with the communication primitive;

f. a set of access conditions associated to the data elements which are referenced in association to the procedural descriptions (C(1) . . . );

g. a set of access conditions associated to the list of data references (B(1) . . . ) in the data list.

2. The data exchange system according to claim 1 characterized in that the memory means (16) further comprises at least two interaction contexts (19(1) . . . 19(m)), at least one application description (18(1) . . . ) and a memory element (20) storing a reference to the interaction context currently being in force, each application description comprising:

a. a data list comprising references (E(1) . . . ) to data elements, which references may be accessible to two or more interaction contexts (19(1) . . . ) and may be extended by additional data elements;

b. a further set of access conditions associated to said references (E(1) . . . ) or to said additional data elements and defining restrictions of use.

3. The data exchange system according to claim 2 characterized in that each application description (18(1) . . . ) also comprises a procedure library comprising units of executable code (F(1) . . . ) which can be used by procedural descriptions (C(1) . . . ) of each interaction context associated to each of said application descriptions (18(1) . . . ).

4. The data exchange system according to claims 2 or 3 characterized in that the memory means comprises at least two application descriptions (18(1) . . . ) and units of executable code (G(1) . . . ) which can be used by procedural descriptions (C(1) . . . ) of each interaction context (19(1) . . . ) within each application description (18(1) . . . ) or by each unit of executable code (F(1) . . . ) of each procedure library within each application description (18(1) . . . ).

5. The data exchange system according to claim 3 characterized in that the units of executable code in the procedure library are enhanced by including a specification of the use of their operational parameters into classes relating to attributes pertaining to data elements which can be passed as actual value in a computation, which computation only proceeds if the data attributes and parameter classes match.

6. The data exchange system according to claim 2 characterized in that the executive program (17) comprises a reference to a default interaction context which is used to initialize the memory element (20) storing a reference to the interaction context currently being in force, in order to carry out a final action after a detection of an internal inconsistency in a recovery to a normal state of operation or whenever the executive program (17) is active and no explicit interaction context has been specified by a communication primitive received from an opposite data processing unit (4).

7. The data exchange system according to claim 2 characterized in that the memory means (16) comprises an interaction context dedicated to comprise Personal Identification Numbers and that the executive program (17) is arranged to verify Personal Identification Numbers supplied by a user of the data exchange system.

8. The data exchange system according to any of the claims 2, 3, or 5–

7 characterized in that each application description (18(1) . . . ) comprises a list of numeric values which is constructed to provide identifiers for all interaction contexts (19(1) . . . ) and comprises at least a first numeric value indicating an application type, a second numeric value indicating a unique identification of the entity providing the application, a third numeric value indicating the nature of the application description (18(1) . . . ) and further numbers each uniquely referring to one interaction context (19(1) . . . ) associated with the application description.

9. The data exchange system according to any of claims 2, 3, or 5–

7 characterized in that the data communication means (14) is arranged to structure data exchange in blocks of data comprising at least two parts, a first part being data qualified as operational in that it is used to influence the nature of the operations performed by a command as indicated by a communication primitive or data resulting from operations carried out, a second part being qualified as security in that it is used to determine the appropriateness of performing an operation or of the acceptability of data within the operational part, to be used in the operation or to prove completion of the operation or correctness of the resulting data.

10. The data exchange system according to claim 9 characterized in that the executive program (17) is arranged to perform, upon accepting a communication primitive to perform operations specified in the current interaction context (19(1) . . . ), each operation as part of a predetermined and fixed sequence of actions each of which is specified separately as part of a procedural description associated to the accepted communication primitive, which actions comprise at least the following actions:

a. authorization of the use of the communication primitive;

b. decryption of operational data or any part of it;

c. performing a command with any input data;

d. encryption of any operational data resulting from any operation performed;

e. computation of a proof of completion of any performed action or of correctness of the resulting data to be used in security computations.

11. The data exchange system according to any of claims 2, 3, or 5–

7 characterized in that the data processing unit (5) generates a random transaction number upon initializing data transfer, which serves as basis for cryptographic computations.

12. The data exchange system according to any of the claims 2, 3, or 5–

7 characterized in that one communication .primitive is assigned a specified value which will always be interpreted as a request to enter a new interaction context (19(1) . . . ).

13. The data exchange system according to any of claims 2, 3, or 5–

7 characterized in that it comprises a further data processing unit (4) comprising the same elements as the data processing unit (4) which might optionally contain in its memory an application programmers interface (10) which consists of program code designed to allow additional computer programs to be implemented to give users control over the sequence of exchanged communication primitives or to influence the data transferred in them or to learn or further process the data received in the exchange.

14. The data exchange system according to claim 13 characterized in that the primitive used to enter a specified interaction context (19(1) . . . ) comprises numeric values to be used in security calculations in subsequent communications, a first random value generated by one of the processing units and a second value serving to identify said one processing unit.

15. The data exchange system according to claim 13 characterized in that each communication primitive is composed of two or more numeric values, a first value being used to refer to a procedural description of an action associated to the communication primitive, a second value being composed of a fixed number of binary values each of which is interpreted by the executive program (12, 17) as a reference to a single data element.

16. The data exchange system according to claim 13 characterized in that each communication primitive is composed of two or more numeric values, a first value being used to refer to a procedural description of an action associated to the communication primitive, a second value being used to determine which of the data elements available for external reference in an active interaction context (19(1) . . . ) will be used while performing responding actions in such a way that any date element is selected if it contains a value that matches said second value.

17. The data exchange system according to claim 13 characterized in that each communication primitive is composed of two or more numeric values, a first value being used to refer to a procedural description of an action associated to the communication primitive, a second value being composed of a number of binary values which are assigned specific meanings by the executive program (12, 17) to be used in interpreting data formats in the communication primitive and in performing responding actions.