Time management at communication level for a smart card-type entity

Abstract

An entity of the smart card (CP) type, having an application layer (AP) linked to a communication protocol layer (PR), comprises a time manager (GD) containing a timer (CD) interfacing with the protocol layer (PR) for substantially periodically constructing waiting time extension (WTX) requests transmitted to a terminal (TE) through the protocol layer as long as data are in the process of being processed in the application layer. The application layer is thus freed from any time constraint.

Description

[0001] The present invention relates to time constraints in communication protocols of the application layer used in entities of the smart card type, also referred to as an integrated circuit card or microprocessor card. It relates particularly to communication protocols where time measurement constraints are severe, for example for communication protocols dedicated to cards with or without contacts, and difficult to take into account, for example for open operating systems.

[0002] The majority of smart cards, such as a credit card or a SIM (Subscriber Identity Module) telephone subscriber card, exchange, with terminals, such as readers or mobile radiotelephone stations, to which the cards are electrically connected during operation, data according to dedicated communication protocols according to ISO standard 7816-3.

[0003] According to this standard, during a process of exchanging data blocks (I-blocks) according to the T=1 asynchronous block transmission protocol at application layer level, the time between the leading edge of the last character of a first block received by the card and the leading edge of the first character of a second data block transmitted by the card may not exceed a predetermined maximum time BWT (Block Waiting Time). If, during the sequence of operations of the application process, the application layer of the card knows that the processing of the first block will exceed the predetermined maximum time and it must therefore put the terminal into a “wait state”, the application layer transmits a specific protocol request referred to as “Waiting Time eXtension” WTX before expiry of the maximum time BWT. The information field of the WTX request contains an integer multiple of the maximum time BWT, defining a time allocated to the application layer of the card which starts after the reception of an acknowledgement transmitted by the terminal in response to the request.

[0004] If, following a first block, the card does not send another block normally before expiry of the time BWT, or on request, before expiry of the allocated time, the terminal interprets this absence of a block as a time-out and for example sends the first block again.

[0005] However, at application level, the smart card software programs are first designed independently of any notion of time relating to information exchanges.

[0006] On the one hand, the application is not intended to count the time since the performance time-wise is dependent on the operating system, particularly on the characteristics of the microprocessor, the system routines, etc. This problem is very difficult to solve in open operating systems such as JavaCard, where the application, such as an applet, is assumed to be an independent platform.

[0007] On the other hand, it is not desirable that the lower level sub-programs (kernel) are responsible for issuing these requests since they are completely disconnected from the time aspects.

[0008] Thus, certain communication protocols are very restrictive in terms of time management, since the time values are directly linked to the efficiency of the protocol, for example dedicated contactless card protocols.

[0009] Two types of management of waiting time extension WTX requests are known according to the prior art for solving this problem.

[0010] In a first type, as shown in FIG. 1, the waiting time extension WTX requests supplied by the protocol layer PR1 underlying the application layer AP1 in the card are managed by the application layer AP1 itself. This software architecture is not portable, that is to say the times are dependent on the sub-programs K1 (kernel), it has an empirical time counting, is not applicable when the application calls a service having a long processing process, for example a complex cryptography algorithm, does not take into account specific parameters such as the durations of waiting times, and is very restrictive for the application during short waiting times, for example those relating to dedicated contactless protocols.

[0011] According to a second type, the waiting time extension WTX requests are supplied by the protocol layer PR2 to the sub-programs (kernel) K2 which manage them, as shown in FIG. 2. This second known software architecture is advantageous in that the application is relieved of the management of the WTX requests which is a requirement in open operating systems since the functions of the application are independent of the functions of applications with at least one external entity. Furthermore, the software architecture facilitates the implementation of a long process by inserting a number of calls with WTX requests during the process.

[0012] However, this second software architecture is neither rigorous nor exhaustive owing to the difficulties to be considered each call sequence by sub-programs, does not taken into account specific protocol parameters, such as waiting times, and may have repercussions on each sub-program.

[0013] The invention aims to improve time management in the software architecture at application level according to the first type in a smart card, by freeing the application layer from this time constraint.

[0014] To that end, an entity of the smart card type, having an application layer linked to a communication protocol layer, is characterised in that it comprises a time manager interfacing with the protocol layer for substantially periodically constructing, at the expiry of a waiting time, a waiting time extension request transmitted to a terminal through the protocol layer as long as data are in the process of being processed in the application layer.

[0015] The time manager comprises in practice a time counting means which is activated after reception of a command with or without data transmitted by the terminal or after a response with data transmitted by the entity, which is de-activated pending a command with data by the application layer or substantially at the time of transmission of a response with or without data to the terminal, and which is de-activated and then re-activated substantially at the expiry of each waiting time causing transmission of the extension request to the terminal. The time counting means is for example integrated in the microprocessor of a smart card which is thus distinct from the protocol layer and from the set of sub-programs.

[0016] The software architecture at application level according to the invention ensures that the time counting is not performed as a base task in the application layer and does not interact with times laid down by the central unit (CPU) of the entity, such as a microprocessor The application layer does not consider the processing time of a data block and depends on the protocol layer for managing this time with the terminal, by putting the terminal into a wait state. A program is thus developed in the application layer without worrying about the processing time relating to this program.

[0017] The invention also relates to a method of managing time at the level of the application layer linked to a communication protocol layer in an entity of the smart card type, characterised in that it comprises the following steps:

[0018] providing a time manager interfacing with the protocol layer linked to the application layer,

[0019] activating the time manager, by means of the protocol layer, in response to a command with or without data transmitted by a terminal or after a response with data transmitted by the entity to the terminal, so as to substantially periodically construct waiting time extension requests transmitted by the protocol layer to the terminal, and

[0020] deactivating the time manager when the protocol layer is waiting for a command with data or substantially when the protocol layer transmits a response with or without data.

[0021] Preferably, the activation step comprises the following periodic steps:

[0022] counting down a waiting time with the time counting means included in the activated manager,

[0023] deactivating the counting means and constructing, by means of the manager, a waiting time extension request substantially at the expiry of a waiting time, and

[0024] transmitting the extension request by means of the protocol layer to the terminal, and activating the counting means.

[0025] Other characteristics and advantages of the present invention will emerge more clearly from a reading of the following description of a number of preferred embodiments of the invention with reference to the corresponding accompanying drawings in which:

[0026] FIG. 1 depicts schematically the software modular architecture at application layer level in a smart card according to a first type of the prior art already commented upon;

[0027] FIG. 2 depicts schematically the software modular architecture at application layer level in a smart card according to a second type of the prior art already commented upon;

[0028] FIG. 3 depicts schematically the software modular architecture at application layer level in a smart card according to the invention; and

[0029] FIG. 4 is an algorithm for managing time between the protocol layer and a time manager in the software architecture according to the invention.

[0030] FIG. 3 shows, in a smart card CP, the software architecture of an operating system according to the first type shown in FIG. 1, at the level of the application layer AP linked to an underlying communication protocol layer PR and to lower level subprograms and programming tools (kernel) K. The smart card is connected to a terminal TE such as a card reader or a mobile radiotelephone terminal by a simplex link LI with or without electrical contacts.

[0031] According to the invention, a time manager GD is interfaced directly to the protocol layer PR so as to control therein waiting time extension WTX requests. The time manager uses a dedicated time counting resource, for example a timer CD clocked by clock pulses and implemented hardware-wise in or in connection with the smart card microprocessor. The communication protocol layer manages exchanges of commands and responses with the protocol layer of another entity, such as the terminal TE. The communication protocol is for example the “T=1” simplex asynchronous block communication protocol according to ISO standard 7816-3.

[0032] The software architecture according to the invention necessitates a specific software design in order to synchronize the requests with the protocol command primitives transmitted automatically and thus avoid protocol conflicts. This is because, at the time of initiation of a data processing process, on the one hand the application layer AP does not manage the processing time between the reception of data and the transmission of new data and relies permanently on primitives of the underlying protocol layer PR. On the other hand, the protocol layer PR, itself supervising, according to the invention, the data processing times in the application layer which is unaware of these times, must control the construction and transmission of WTX requests without disrupting the communication protocol.

[0033] The interfacing between the time manager GD and the protocol layer PR entails certain modifications in the protocol layer, compared with the prior art.

[0034] The protocol layer PR supplies, to the time manager GD, protocol parameters relating notably to the waiting times, like the maximum time BWT between a command with or without a data field (byte sequence) received in the card, as a protocol data unit, and a response with or without a data field to be transmitted by the card. The timer CD included in the manager GD is initialized with these parameters supplied by the protocol layer PR.

[0035] Dependent upon the sequence of operations of the communication protocol, the protocol layer PR controls the activation of the timer CD and therefore the construction of WTX requests by the time manager GD which avoids protocol conflicts. Thus, a counting down, or a counting up, of a predetermined number of clock pulses in the timer CD causes the production of a WTX request by calling a communication service concerned in the protocol layer PR without the latter knowing precisely the processing time required by the application layer.

[0036] With reference to an example time management method illustrated in FIG. 4, this is presented for four main types of protocol data unit APDU processed and constructed by the application layer AP, namely commands without data COM and commands with data CDO transmitted by the terminal TE to the card CP through the link LI, and responses without data RES and responses with data RDO transmitted by the card CP to the terminal TE through the link LI. Thus, the method of managing time at the level of the application layer AP comprises four steps Al to A4 relating to these four types of protocol unit COM, CDO, RES and RDO; each of the four protocol units initiates interactions between the protocol layer PR and the time manager GD, after an initialization. During the initialization, the aforementioned protocol parameters relating notably to the wait data and defined in the protocol layer PR are transmitted to the manager GD for setting the timer CD accordingly.

[0037] The cyclic sequence of steps A1 to A4 in the application layer AP ensures that there is no conflict between protocol units notably to be transmitted and received.

[0038] Furthermore, the application layer AP has functionalities totally independent of the cycle of steps in the time manager described later.

[0039] When a command without data COM is to be received in the application layer (step A1), the protocol layer PR supervises and manages reception of the command at a step P1.

[0040] If a COM command is detected, the protocol layer PR invokes a procedure for activating the time manager GD at a step G1. In the time manager, the activation step G1 initializes the timer CD at a step G2, for example by setting the count CI thereof equal to a number [BWT] representing the maximum time BWT between a received protocol unit, such as the COM command, and a protocol unit transmitted by the smart card CP.

[0041] Then, a counting down of clock pulses is initiated at a step G3. Cyclically at an intermediate step G4 in response to each clock pulse, the manager GD compares the count CI of the counter CD with a parameter dT, such that dT<<[BWT], defining a time, small compared with the maximum time BWT, for transmitting a WTX request. Thus, as long as the count CI is greater than dT at the step G4, counting down of the clock pulses is continued. As will be seen subsequently with regard to the steps A3 and A4, the counting down is continued as long as the application layer AP has not produced a RES or RDO response to the COM command.

[0042] If the count CI reaches dT at the step G4, the counter CD is deactivated at the step G5. The manager GD then constructs, at the following step G6, a waiting time extension WTX request applied to the protocol layer PR, and, at a step G7, again activates the counter CD whose count is reset to CI=[BWT] at the step G2 which continues with cycles of steps G3 and G4. After having constructed and transmitted the WTX request to the terminal TE at a step P2, the protocol layer PR signals this to the application layer AP which will maintain the WTX request generation cycle G2 to G7 as long as a response is not to be transmitted.

[0043] When a command with data CDO is to be received in the application layer (step A2), the protocol layer PR invokes a procedure for deactivating the manager GD at a step G8 in order that the manager GD stops and thus prevents any counting down in the counter CD at a step G9, the counter CD possibly being in the process of counting down following a response with transmitted data RDO. The protocol layer PR also supervises and manages the reception of a CDO command at the step P3.

[0044] If a CDO command is detected at the step P3, the protocol layer PR invokes a procedure for activating the time manager GD at a step identical to the step G1 which initializes the timer CD at the step G2 and initiates the steps already described G2 to G7 in the manager GD, with possibly the transmission of a constructed WTX request at the step P2, as long as a RES or RDO response is not produced which would suspend the counting down in the counter CD.

[0045] When a response without data RES is to be transmitted by the application layer (step A3), the protocol layer PR invokes a procedure for deactivating the manager GD at the step G8 which stops the counter at the step G9, since the counter CD was started upon reception of a COM or CDO command and maintained in the cyclic counting down state as long as the application layer has not completed the processing generated by this last command. Substantially simultaneously, the protocol layer PR transmits the RES response by encapsulating it at a step P4.

[0046] Similarly, when a response with data RDO is to be transmitted by the application layer (step A4), the protocol layer PR invokes substantially simultaneously the procedure for deactivating the manager GD at the steps G8 and G9 and transmits the RDO response encapsulated by the protocol layer PR at a step P5.

[0047] However, the step P5 is followed by the step G1 during which the protocol layer PR invokes a procedure for activating the time manager GD according to the steps G2 to G7. This is because the response with data RDO is not necessarily the end of processing in the application layer which may still require time extension by transmitting one or more WTX requests in order to continue said processing, waiting for data transmitted by the terminal by at least one command with data CDO, as long as a “definitive” RES response is not transmitted.

Claims

1. An entity of the smart card (CP) type, having an application layer (AP) linked to a communication protocol layer (PR), characterised in that it comprises a time manager (GD) interfacing with the protocol layer (PR) for substantially periodically constructing, at the expiry of a waiting time (BWT), a waiting time extension (WTX) request transmitted to a terminal (TE) through the protocol layer as long as data are in the process of being processed in the application layer.

2. An entity according to claim 1, in which the time manager (GD) comprises a time counting means (CD) which is activated (G1) after reception of a command with or without data (COM, CDO) transmitted by the terminal (TE) or after a response with data (RDO) transmitted by the entity, which is de-activated (G8) pending a command with data (CDO) by the application layer (AP) or substantially at the time of transmission of a response with or without data (RES, RDO) to the terminal, and which is de-activated and then re-activated (G5-G7) substantially at the expiry of each waiting time (BWT) causing transmission of the extension (WTX) request to the terminal (TE).

3. A method of managing time at the level of an application layer (AP) linked to a communication protocol layer (PR) in an entity of the smart card (CP) type according to claim 1 or 2, characterised in that it comprises the following steps: providing a time manager (GD) interfacing with the protocol layer (PR) linked to the application layer, activating (G1) the manager (GD), by means of the protocol layer, in response (P1, P3) to a command with or without data transmitted by a terminal (TE) or after a response with data transmitted (P5) by the entity to the terminal, so as to substantially periodically construct waiting time extension (WTX) requests transmitted by the protocol layer (PR) to the terminal (TE), and deactivating (G8) the manager (GD) when the protocol layer is waiting for (P3) a command with data or substantially when the protocol layer transmits (P4, P5) a response with or without data.

4. A method according to claim 3, in accordance with which the activation step comprises the following periodic steps: counting down (G3, G4) a waiting time (BWT) with the time counting means (CD) included in the activated manager (GD), deactivating (G5) the counting means and constructing (G6), by means of the manager, a waiting time extension (WTX) request substantially at the expiry of a waiting time (BWT), and transmitting (P2) the extension (WTX) request by means of the protocol layer to the terminal (TE), and activating (G7) the counting means.