EP1337980A1 - Carte a puce avec descripteur d'application - Google Patents
Carte a puce avec descripteur d'applicationInfo
- Publication number
- EP1337980A1 EP1337980A1 EP01983669A EP01983669A EP1337980A1 EP 1337980 A1 EP1337980 A1 EP 1337980A1 EP 01983669 A EP01983669 A EP 01983669A EP 01983669 A EP01983669 A EP 01983669A EP 1337980 A1 EP1337980 A1 EP 1337980A1
- Authority
- EP
- European Patent Office
- Prior art keywords
- application
- elements
- state
- electronic object
- portable electronic
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Withdrawn
Links
Classifications
-
- G—PHYSICS
- G07—CHECKING-DEVICES
- G07F—COIN-FREED OR LIKE APPARATUS
- G07F7/00—Mechanisms actuated by objects other than coins to free or to actuate vending, hiring, coin or paper currency dispensing or refunding apparatus
- G07F7/08—Mechanisms actuated by objects other than coins to free or to actuate vending, hiring, coin or paper currency dispensing or refunding apparatus by coded identity card or credit card or other personal identification means
- G07F7/10—Mechanisms actuated by objects other than coins to free or to actuate vending, hiring, coin or paper currency dispensing or refunding apparatus by coded identity card or credit card or other personal identification means together with a coded signal, e.g. in the form of personal identification information, like personal identification number [PIN] or biometric data
- G07F7/1008—Active credit-cards provided with means to personalise their use, e.g. with PIN-introduction/comparison system
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
- G06Q20/34—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using cards, e.g. integrated circuit [IC] cards or magnetic cards
- G06Q20/341—Active cards, i.e. cards including their own processing means, e.g. including an IC or chip
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
- G06Q20/34—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using cards, e.g. integrated circuit [IC] cards or magnetic cards
- G06Q20/355—Personalisation of cards for use
- G06Q20/3552—Downloading or loading of personalisation data
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
- G06Q20/34—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using cards, e.g. integrated circuit [IC] cards or magnetic cards
- G06Q20/357—Cards having a plurality of specified features
- G06Q20/3576—Multiple memory zones on card
Definitions
- the present invention relates to applications described in a portable electronic object, such as a smart card, also known as a microcontroller card or integrated circuit card, and deployed through an application execution means notably comprising a terminal reception of the smart card, in a wide and heterogeneous context.
- a portable electronic object such as a smart card, also known as a microcontroller card or integrated circuit card
- an application execution means notably comprising a terminal reception of the smart card, in a wide and heterogeneous context.
- an application is composed of software components dispersed in one. telecommunications network and must be able to be executed from heterogeneous terminals having hardware and software characteristics
- Heterogeneous terminals differ, for example, in their operating systems and their coding characteristics.
- the terminal To correctly run the applications, the terminal must have service data relating to
- a given application presents a complex graphical interface based on windows in a personal computer, and simple text menus in a mobile radiotelephone, or establishes an audio or video communication according to the speed offered by the network.
- an API application in a smart card CP1, or any other portable electronic object having a relatively small memory capacity, by a descriptor DAP1 of a first API application identifying elements essentials of the application, such as the software components of the application and the connections between these components two by two.
- an application comprises at least three components II, Al and SI and at least two connections CIA1 and CAS1 interconnecting in pairs the components II and Al and the components Al and SI.
- the first component II is a user interface containing the entry point of the application, which needs a consultation service, for example a banking consultation service offered by the second component A1, so to recover information taken from a personal bank account of the user who owns the card managed by the third component SI constituted by a server of a bank with which one or more user accounts have been opened.
- the user interface component II is located in the reception terminal TE, while the other two components A1 and SI are located in different sites. Only the first two components II and Al are configurable.
- the application can be executed, adapting to the execution context essentially constituted by the terminal.
- An application component is a software processing unit encapsulating functionalities, small enough to be able to create and maintain it, and large enough to be able to install and support it.
- the functional properties of a component are the processing possibilities offered by the component and are programmed and invariant whatever the context.
- the component also has non-functional properties which represent system aspects linked to the implementation of the component, such as transaction, security, persistence, fault tolerance, and which are variable depending on the context and the application. The separation between invariable functional properties and variable non-functional properties makes it possible to execute the component in a different way on an execution platform.
- the component is also provided with communication interfaces so that it can cooperate with other components and thus present its behavior to these other components.
- a software component can be installed on any site of an RT telecommunications network.
- a connection defines the relationships between the communication interfaces of two components.
- Application connection parameters are also adapted to the context of the execution platform.
- the application descriptor DAP1 does not contain the element itself, the software component or the connection, but a descriptor DU, DCIA1, DA1, DCAS1, DSI of the element II, CIA1, Al, CAS1, SI containing properties and parameters of the element defining it and allowing it to be found among a multitude of elements.
- the properties of the descriptor of an element are fixed once and for all by the supplier of the application which specializes the element, component or connection, in order to satisfy the needs of the application and the user according to the characteristics of subscription. They indicate the characteristics of the platform on which the element can be executed, as well as the system requirements necessary for execution.
- a property is the type or address of an element which is associated with each element and used for searching for the code or the implementation of the element, or is intimately linked to the application or to a type of application, such as the "account number" property associated with a component, consultation agent or bank account server 1 .
- These properties are, according to the prior art, frozen when subscribing to the service corresponding to the application by the user of the smart card, and are only accessible in read-only mode.
- Other properties, called parameters are preferably personalized by the user and can be modified at any time.
- a parameter has the value of the display currency of an amount, or a range of colors for displaying pages on a screen, or the value of the bit rate or of a transmission characteristic in a connection.
- Each descriptor of an application is represented in the form of an object graph in object-oriented language, for example JAVA language (trademark).
- the descriptors of the applications in a multi-application smart card are combined in an applet which acts as a descriptor server creating the tree of objects representing the components and the connections of the descriptors.
- application descriptors are written in XML (Extensible Markup Language) language.
- the descriptor server constituting the applet is associated with a client, called a PII deployment driver (in English bootstrap) which constitutes within the smart card.
- CP1 an application to configure the selected application according to its descriptor.
- the pilot manages the deployment of elements of the selected application, after the introduction of the CP1 card in the TE reception terminal. By grouping the descriptor server and the deployment pilot in the card, the confidentiality of the descriptors is ensured so that the reading of the descriptors by the " deployment pilot constituting a known client does not require authentication.
- the pilot Deployment authenticates each client who interrogates it before making available all of the methods of the applet.
- the PI deployment pilot informs the descriptor server which then considers all the requests addressed to it as relating to the DAP1 descriptor of the selected application.
- the PI driver thus processes one or more application deployments according to the DAP1 descriptor of the selected application API and the execution context of the application. consisting essentially of the TE terminal.
- an application element, component or connection is configured according to the context of the application, that is to say the hardware and software properties of the platform where the application will be executed, and parameters chosen by the user and customizing the application.
- the properties of the execution context provided by the terminal are for example the type of reception terminal used TE, the name of the terminal, a certificate or key identifying the terminal, the location of the terminal in the telecommunications network and a date of manufacture of the terminal. All this information is gathered in the descriptor of the application element so that the PI deployment pilot filters the information contained in the descriptor of the element according to the context of the application and the personalization parameters of the user. .
- the deployment pilot PI located in the smart card CP transmits deployment commands to a deployment portal PO which is an application element implemented in the reception terminal TE.
- the main role of the portal is to receive deployment commands and re-issue them to the deployment platform in order to install the selected application.
- the deployment portal mainly has a function of informing the smart card about the environment in which the installation and execution of the selected application must be done, and a function of communication with the card in order to receive various commands for deploying the selected application.
- the deployment of an application is synchronous, that is to say the commands developed by the deployment pilot PI are transmitted sequentially to the terminal TE, one after the other, respectively for the installation of the elements of the application , then for the configuration of the elements of the application. After these installations and configuration of elements, the application is launched by an execution command (RUN) which contains the name of the component of the selected application determining the entry point of the application, generally the component of user interface.
- RUN execution command
- the deployment is carried out by the deployment pilot from the descriptor DAP1 of the selected application API so that a dialogue is established between the deployment pilot PII in the smart card CP1 and the deployment portal PO in the terminal.
- the portal can contain an element search engine, or be linked to one or more MR element search engines, as shown in FIG. 2.
- Each MR search engine constitutes a directory of application elements to reference and search for application elements in libraries of BI application elements across the RT telecommunications network.
- Each element in a library is memorized with its descriptor and managed by the designer of the element.
- the set of components and connections constituting an application defines a profile of the application. So two different users can have different application profiles because of the parameters of the user-defined applications with different values, such as bank account numbers. Conversely, a single user can configure an application according to several different profiles.
- the profiles of an application are thus defined either by the user, or automatically according to the context of use of the application, which can depend in particular on the reception terminal and in particular on the operating system implemented in it. .
- certain values of the parameters of a component depend in particular on the type, name and location of the terminal.
- the descriptor of the application AP2 also shown in FIG. 2 includes descriptors DI2, DA2, DS2, DCIA2 and DCAS2 of a user interface 12, of a bank consultation agent A2, of a bank server S2 and CIA2 and CAS2 connections between components 12 and A2, and A2 and S2.
- the user cannot carry out operations dependent on these two bank accounts.
- the agents A1 and A2 are transfer agents, a transfer from the bank account managed by the first server SI to the bank account managed by the second server S2 is impossible by either of the agents A1 and A2.
- the deployment of an API application is total.
- ' all API, Al and SI components of the application must be found by the search engine MR regardless of the execution context , in particular the TE terminal, to execute the application.
- the components of the API application including the server SI, must be installed while the last information consulted is stored in the card CP1 and their reading does not require the intervention of the server component SI.
- the API bank consultation application is deployed on a secure terminal, although the secure nature of the terminal is not necessary for such an application.
- the invention therefore aims to remedy the aforementioned drawbacks.
- the description of the applications with elements distributed according to the prior art so as to offer more applications global for the user and can be deployed only partially under the user's control or depending on the context surrounding the application's execution platform.
- a portable electronic object of the microcontroller card type comprising a means for describing an application composed of several remote elements distributed with descriptors of the elements, and a means for deploying the application outside the electronic object.
- the means for describing combines several states of the application which are selectively deployed outside the electronic object under the control of the means for deploying, and which each comprise at minus an element of the application.
- Said at least one element can for example be a user interface, or an agent qualifying at least one process and operating alone, or even a server operating alone.
- an application state includes two, or some or all of the elements of the application.
- the means for describing the application can then comprise the descriptor of a user interface, and / or the descriptor of at least one element qualifying at least one process, and / or the descriptor of at least one data server. .
- One of the states of the application can comprise the parameters of at least one element included in this state.
- states differ for example by parameters of a common element.
- the invention also relates to a method for configuring and deploying an application composed of several remote elements distributed from a portable electronic object in accordance with the invention, containing descriptors of the elements, through a data processing means connected to means for implanting the elements to execute the configured and deployed application.
- the method is characterized in that after a transmission of characteristics of the execution context of the application from the processing means to the portable electronic object, it comprises a selection of one of the states of the application which each include at least one element of the application.
- an element for example an agent qualifying a process
- the method comprises, with the transmission of characteristics of the execution context of the application, the transmission of a key associated with an element of the application, and the deployment of a selected state of the application comprising the element only in response to a prior detection of the predetermined key by the portable electronic object.
- several keys can be associated respectively with elements of the application, the selection of a state from among states of the application comprising at least connections with the elements associated with the transmitted keys.
- the method preferably comprises a selection of one of several deployments of the selected state of the application, so as to adapt the deployment in the context of the application and if possible increase the speed of execution.
- the deployment is essentially asynchronous, or else essentially
- One of the asynchronous or synchronous deployments can include the installation of at least one element
- FIG. 1 already commented on, shows the modularity of two applications in three components for example;
- - Figure 2 already discussed, is a schematic block diagram of the means used in a telecommunications network for the deployment of applications of distributed remote elements, according to the prior art;
- FIG. 3 is a graph of the states of a global application according to the invention.
- FIG. 4 is similar to Figure 2, but with a smart card according to the invention
- - - Figure 5 is a graph of the main states of a banking application according to the invention
- FIGS. 5A and 5B are state graphs only between two components of the application of Figure 5, respectively, - - Figure 6 is a state graph for a variant banking application;
- - Figures 7 and 8 are graphs of two applications according to the invention respectively with a single agent and a single server; and - Figure 9 is an application configuration and deployment algorithm according to the invention.
- an application AP is composed of several distributed remote elements which are a user interface IU, agents AGI to AGM and data servers SEl to SEN, at least one of the integers M and N being greater than 1.
- FIG. 3 also represents other elements of the application AP constituting connections CIAG1 to CIAGM respectively between the interface UI and the agents AGI to AGM and connections CAS11-CAS1N to CASM1-CASMN respectively between each of the agents AGI to AGM and SEl servers at SEN.
- One or more such applications are described in the form of descriptors in a smart card CP, or any other portable electronic object, as shown in FIG. 4. According to this figure, the
- • 5 smart card includes at least the DAP descriptor of the AP application including the IUD descriptors, DAG1 to DAGM and DSE1 to DSEN of the components and the descriptors of the application connections.
- the descriptors of the connections in FIG. 4 are not marked for clarity.
- the user interface IU is located in the reception terminal TE of the smart card CP, the reception terminal TE being connected to a network of
- the user interface essentially constitutes the human interface. machine which is configured by the user, in particular at level 0 of. , screen page design and listening to. voice messages.
- the user interface IU thus visually and / or vocally presents data transmitted by at least one of the agents AGI to AGM included in the selected state of the application, as will be seen below.
- commands to be processed by an agent of the selected state are entered by the interface UI to trigger operations on data in one or more of the servers SEl to SEN included in 0 the selected state of the application. .
- the user may be able to select states of the AP application and data relating thereto. These states and these data are contained in the descriptor DIU and saved in the non-volatile memory EEPROM of the chip card CP between two application sessions, that is to say between two selections of application states.
- the user interface IU is thus a session type component which is created at the start of the session and totally or partially destroyed at the end of the session.
- the user interface IU constitutes the entry point of the AP application for the user, and therefore intervenes each time the user wishes to have one of the states of the AP application executed directly.
- An AGm agent qualifies at least one predetermined process for processing data transmitted by the user interface IU when it is linked to the AGm agent, and / or for processing transmitted data by at least one of the servers SEl to SEN when the latter is connected to the agent AGm for the selected state of the application.
- the agent AGm can be configured by the user from the interface UI and / or according to the characteristics of the context of the application essentially depending on the characteristics of the reception terminal TE of the smart card CP.
- the descriptor DAGm of the agent AGm thus has several parameters, the values programmed in particular by the user are saved in the non-volatile memory of the smart card.
- the agent AGm is therefore of the process type, which implies that it can be maintained during a partial termination of the selected state of the application.
- this offline state is executed so that the agent AGm processes data from one or more SEl to SEN servers included in the selected application state, without any intervention of the user interface UI which is kept offline.
- a data server SEn is an entity containing data which can be consulted or processed by one of the agents AGI to AGM so as to retransmit the data without or with modification to the user interface IU and / or to the server SEn and / or at least one other server.
- the state of the server SEn is independent of the user, that is to say cannot be modified by the user interface IU, and is managed by the designer of the server SEn, just as an agent AGm is managed by the designer of the AGm agent, from an appropriate terminal through the RT network.
- the server SEn can optionally process several requests from agents relating to several applications and therefore to several users respectively.
- a state of the application AP which is not very wide comprises at least one or two different components, either the user interface IU and / or the agent AGm connected by the corresponding connection CIAGm, or an agent AGm and / or one servers SEl to SEN connected by the corresponding connection CASml to CASmN, with 1 ⁇ m ⁇ M.
- the most extensive "global" state of the application is the arrangement of the interface UI, of all the agents AGI to AGM and of all the servers SEl to SEN with all the connections shown in FIG. 3.
- intermediate states include one or more agents AGI to AGM which can each be linked to the user interface IU and / or to one or more respective servers SEl to SEN.
- agents AGI to AGM can each be linked to the user interface IU and / or to one or more respective servers SEl to SEN.
- an APB application relates to an inter-bank and inter-account service.
- the APB application generally includes as elements, a user interface IU, two agents AGC and AGV dedicated to banking consultation and to bank transfer, and N data servers SBl to SBN containing the data of the various accounts that the user opened in N banks.
- the banking consultation agent AGC is connected to the user interface and to one or more of the servers of SBl bank at SBN.
- the user can then select his accounts from a list presented by the interface UI in order to connect the accounts which are opened in the various banks corresponding to the servers SBl to SBN in relation with the agent AGC.
- the bank transfer agent AGV is intermediate between the user interface IU and one or more of the servers of SBl bank at SBN.
- the AGV agent can be configured by the user to make an automatic transfer for example between two accounts managed by the same server SBn, or between two accounts managed respectively by different servers SBn and SBp, with p ⁇ n and 1 ⁇ p ⁇ N.
- the descriptions of the states of the interface UI and of the agents AGC and AGV are saved in the non-volatile memory of the card.
- smart CP thus it stores the list of identifiers of the user's bank accounts and at least their last known balances, and the recently configured functional states of the agents AGC and AGV.
- Figures 5A and 5B show minimum states T3 and T4 of the application. APB banking service.
- the state T3 relates to the connection between. 1 UI user interface and 1 AGC banking consultation agent. This state is selected by the user when the latter wishes to consult again the last 'data it has stored in the smart card CP at, recent consultations SBI servers SBN.
- the T3 state can be imposed by the execution context of the application.
- a predetermined key KAGC is associated with the descriptor DAGC of the agent AGC contained in the descriptor DAP of the application AP included in the chip card CP. If no key or a key of zero value is transmitted with the characteristics of the application context by the portal PO from the terminal TE to the deployment pilot PI in the smart card CP prior to the selection of one .
- the driver - PI not recognizing the KAGC key does not install and therefore prohibits any connection from the AGC agent to the SBl servers at SBN. Consequently, the driver PI only authorizes the connection of the agent AGC with the user interface IU according to the application state T3 shown in FIG. 5A.
- the TE terminal transmits the KAGC key to the PI deployment pilot, the latter authorizes the agent AGC to be connected to at least one of the servers SB1 to SBN.
- the KAGC key thus makes it possible to validate secure connections in predetermined states of the application. More generally, concomitantly with the transmission of characteristics of the execution context of the application from the terminal TE to the pilot PI, the transmission of a predetermined key KAGC, KAGV associated with a given element, such as one of. AGC and AGV agents qualifying at least one process, capable of being connected to two other elements of the application, such as two of the servers SBn to SBp or one of these servers and the user interface IU, by the TE reception terminal is mandatory so that the PI driver on the CP card does not authorize the deployment of a selected state of
- the state T4 of the APB application shown in FIG. 5B. connects the bank transfer agent AGV and two SBn and SBp bank servers.
- This state is an offline state for which the user interface IU is not connected to the AGV agent, that is to say for which the user terminal TE has no access to servers. through the AGV agent.
- the state T4 has been programmed by the user during a previous state connecting the user interface IU to the servers SBn and SBp by the intermediary of the bank transfer agent AGV so as to configure automatic transfers to the less between one of the accounts managed by the SBn server and one of the accounts managed by the SBp server. For example, if one of the accounts managed by the SBn server is a checking account and if one of the accounts managed by the SBp server is a savings account, the user can program one of the following two sets of operations:
- Each of the two preceding automatic transfers is programmed by the user in the AGV agent so that it can be executed offline, as shown in FIG. 5B, in a periodic manner, for example after each day, as soon as the balance Cn of the checking account has become greater than. SUP threshold or has become below the INF threshold.
- a transfer operation by means of one bank transfer AGV can only be carried out on an execution platform, in this case • the reception terminal TE,. who has provided a KAGV security key which is only known to the user and recognized by the PI driver in the chip card CP so as to install the AGV agent connections with servers according to the descriptor thereof contained in the DAP descriptor of the AP application.
- the user can also choose parameter values of the IU interface and of the agents AGC and AGV-. For example, the user selects one of several display languages in the user interface IU and one of several currencies in the AGC agent or the AGV agent.
- the APC application is a variant of a banking service application.
- the agent and server pairs AGCl-SCl, AGCm-SCm and AGCM-SCM relate to viewing and managing a checking account, a savings account and a securities account .
- the AGCM agent can also be connected to a market data server SCB. All AGCl agents at AGCM. are connected to the user interface UI.
- an AGVC transfer agent is intermediary between the user interface IU and the account consultation agents AGCl at AGCM in order to carry out automatic transfers from one to the other of the accounts whose the data is included in the SCI servers at SCM.
- the descriptor describing the APC application in the CP card only includes the descriptors of the following elements: the user interface UI, • several elements AGCl to AGCM each qualifying at least one process, and several data servers SCI to SCM can be connected respectively to the qualifying elements.
- an application APJ comprises a global state which brings together a single agent AGJ with the user interface IU and N data server SJ1 to SJN.
- the application APJ is for example relating to a game common to N players Jl to JN, including the player, for example Jl, possessor of the chip card CP and deploying the game application APJ on the terminal TE.
- the agent AGJ is a game concentrator-broadcaster while the server components SJ1 to SJN are installed respectively in players' terminals J1 to JN.
- the descriptor describing the APJ application in the CP card includes the descriptors of the following elements: the user interface IU, the element APJ qualifying at least one process, and several data servers SJ1 to SJN which can be selectively connected to the qualifying element.
- a third realization of. application 'according to the invention shown in Figure 8 relates to an APE application whose overall state includes M agents AGEl to AGEM which can each be connected to one user interface IU and to a common data server SE.
- the server SE is an electronic mail server receiving electronic messages from various correspondents of the user possessing the smart card CP.
- the agents AGEl at AGEM filter the messages each according to predetermined conditions. For example, the agent AGEl retransmits to the user interface UI only all the messages coming from private senders whose addresses are listed in a first directory so as to store only these private messages in the card smart CP; the AGEm agent filters messages from only professional senders listed in a second directory and only signals the reception of a professional message at the user interface UI and retransmits each professional message to a destination server located on the site user professional; the AGEM agent contains the first and second directories of the agents AGEl and AGEm in order to filter only the messages coming from senders not listed in these two directories and to signal to the user interface IU that such a message has been recorded and that an acknowledgment, pending message processing has been returned to the sender of the message.
- the descriptor describing the APE application in the CP card only includes the descriptors of the following elements: the user interface IU, several elements AGEl to AGEM each qualifying at least one process, and a single data server SE can be selectively connected to "qualifying elements.
- the configuration and deployment of a selected state selected application AP in a smart card multi-application CP comprises the steps, following El to E13.
- the user inserts the smart card CP into the reader slot of the reception terminal TE in step E1, the reception terminal being for example a mobile radiotelephone terminal, a personal electronic assistant or a personal computer.
- the reception terminal being for example a mobile radiotelephone terminal, a personal electronic assistant or a personal computer.
- the smart card After the introduction of the smart card, it authenticates the user by means of a confidential code or a biometric fingerprint entered by the terminal TE, in step E2.
- characteristics of the execution context are transmitted by the terminal TE to the deployment pilot PI in the smart card CP, in step E3.
- the context of the hardware environment external to the smart card is defined by characteristics of the execution platform which are transmitted by the terminal TE to the smart card CP in step E3.
- the characteristics of the execution context provided by the terminal are for example the type of reception terminal used TE, the name of the terminal, a certificate or key identifying the terminal, the location of the terminal in the telecommunications network and a date of manufacture of the terminal. These characteristics allow the PI deployment pilot to limit the amount of data that he transmits to the PO deployment portal and thus minimize the duration of the deployment.
- the characteristics of the execution context may include at least one security key, such as the keys KAGC and KAGV (FIGS. 5A, 5B), composed by the user in the terminal TE and capable of being assigned to the access of connections with elements, such as AGC and AGV agents, of the selected application AP below.
- KAGC and KAGV KAGC and KAGV
- step E4 the user selects one of the applications AP whose descriptors DAP are stored in the smart card CP.
- the pilot PI retransmits the list of states T of the selected application AP authorized by the card CP according to the context.
- step E5 one of the authorized states of the selected application AP is selected by the user from the list of authorized states displayed by the terminal TE.
- the selected state T includes at least connections with the elements associated with the transmitted keys.
- step E6 the terminal TE according to the context and preferably according to the wishes of the user sets the descriptor DT, that is to say sets some or all of the descriptors of the components and connections of the state selected T from the selected application AP.
- the configuration by the user is classic using tree menus asking for parameter values.
- the method offers several deployment choices in steps E7, E8, E9 and E10 according to a complete realization of the invention, although in a variant, the method can only comprise one or some of the steps E7 to E10.
- steps E7, E8 and E9 one of the values of a property or one of several properties in the descriptor of at least one element EL of the selected state of the selected application AP is selected by the user possessing the chip card CP, or by the chip card CP as a function of characteristics of the context of execution of the application transmitted by the terminal TE.
- step E7 the user decides that the selected application is at least partially degraded. Otherwise, the process goes to step E8.
- a degradation consists in step E71 in selecting at least one EL of the elements of the selected state T of the selected application AP that can be degraded.
- the degradation of an EL element, component or connection consists of a loss of quality or performance of the expected result produced by the component or connection. This degradation is introduced during the installation of the element during the next deployment step proper Eli or E12.
- the degradation of a calculator-type component concerns, as a parameter, the number of. decimal points of the decimal result of a predetermined calculation. If the user has configured in step E6 that the result of the calculation would contain P digits after the decimal point, he can accept in step E71 that the result and therefore the calculation " be performed only with Q digits after the decimal point, with ' Q ⁇ P.
- the search engine MR searches for all the calculation components that can calculate with decimal numbers including Q to P digits after the decimal point, and the PI driver does not maintain l installation only of the component found having decimal numbers to be calculated having the largest number of digits after the decimal point.
- Step E8 relates to the selection of a weighting on the value of at least one property in at least one EL of the elements of the selected state T of the selected application AP. If the user does not want any weighting, the method proceeds to the next step E9.
- the user selects one of the weightings associated with at least one. EL of the elements, components and connections, of the selected state of the application selected in step E81.
- the purpose of the weighting is to assist the PI deployment pilot in his reaction to errors and to allow the smart card to be intrinsically scalable over time.
- one or more properties in one or more descriptors of the EL element are assigned weight so that the user configures the deployment prior to the execution of the actual deployment of the application state comprising at least the affected elements of a selected weight.
- the weights assigned to the different values of the properties of certain elements of the state of the application allow the PI deployment pilot to choose a configuration of the state of the application according to a degree of satisfaction of the user.
- PP and PQ denote low and high weights assigned to calculations performed with decimal numbers having P digits and Q encrypted after the decimal point, with P> Q. If the user is looking for rapid deployment, he selects a high weight such as PQ. On the contrary if the user is looking for a more computational result precise and therefore a slower deployment, it selects a low weight, such as PP.
- a weight can be assigned as a function of the more or less long duration of the execution of a component or of the duration of a connection between two components.
- the weight of a weighted property of an element is corrected as a function of predetermined quality criteria on at least the deployment of a previous state of the selected application containing said element.
- the weight of a weighted property is revalued according to the weighted average of quality measurements carried out during the previous deployment or during a predetermined number of previous deployments. The weighting is thus conditioned by the history of previous deployments.
- step E9 the user decides to select a configuration of at least one property of one of the elements of the selected state T of the selected application AP. Otherwise, the method goes to step E10.
- a component of the selected application state has configurations that differ in a few different properties.
- the component can be a means of calculation in decimal numbers having P and Q digits after the decimal point in two configurations, or else a graphical interface presenting color combinations according to two configurations.
- configurations of at least one selected component or connection of the selected application state, and more generally of. several selected elements of the application state having configurations are selected.
- the installation of the first configuration found among the selected configurations of each of the elements sought by the search engine MR is then maintained by the deployment pilot PI which ignores the other configurations by a special destruction command (Abort) of these additional configurations .
- Abort special destruction command
- the deployment pilot selects one of these configurations a posteriori, for example by retaining only the first which has been received, or by retaining the one which satisfies a predetermined quality criterion, and destroys the other installed configurations.
- the deployment pilot PI When several configurations of an EL element are selected in step E91, the deployment pilot PI successively transmits several installation commands containing respectively the descriptors of these different configurations of the element, during the deployment below.
- step E10 the synchronous or asynchronous character of the deployment is selected. If synchronous deployment is chosen, this is developed in step E1.
- the synchronous deployment of the selected state T of the selected application AP mainly consists of the transmission of sequential commands, one after the other, by the pilot PI to the portal PO to first install all the components of the state d selected application T which are dependent on installations of other elements of the application state T, to configure the components installed respectively in response to acknowledgments from the installations of the components transmitted by the PO portal and according to parameters contained in the descriptors of the components, then to install all the connections of the selected application state T each dependent on two respective installed components respectively in response to acknowledgments of the settings' of the two respective components and as a function of the connection descriptors, and of the settings of all the connections respectively in response to acknowledgments from the connection installations and as a function of parameters contained in the connection descriptors.
- Asynchronous deployment essentially consists of the transmission of commands in parallel by the PI pilot to the PO portal to install and configure the various elements of the selected state T of the selected application AP.
- the . Asynchronous deployment naturally begins with the installation of elements, such as the components of the application state T, the installation of which is independent of other installations and depends on the descriptors of the components.
- the pilot approves substantially in parallel, independently of any scheduling of the elements, parameter settings of the components respectively in response to acknowledgments of installation of; components and according to parameters contained in the component descriptors, installations of the connections of the selected application state T each dependent on at least one installation of two respective components respectively in response each to the acknowledgment of configuration of the two respective components and according to the descriptors connections, and settings of the connections respectively in response to acknowledgments of installation of the connections and according to parameters contained in the descriptors of the connections.
- the descriptors of the elements of the state of application selected T in the commands include characteristics in particular of property which were selected in the preceding steps E7 to E91. These characteristics concerning the degradation, the weighting and of the configurations of element as well as the synchronous or asynchronous character of the deployment can be selected entirely by the user or selected by the deployment pilot PI possibly with the help of information provided by the user. the user and / or by the reception terminal TE as a function of characteristics of the context transmitted by the terminal TE in step E3, or can be selected in part by the user and in part by the terminal TE.
- the IP default driver selects the synchronous character for one user or the terminal TE does not intervene, in 'forcing the deployment that it is synchronous.
- This default choice of synchronous deployment makes it possible to deploy the selected application state on all the terminals, including those which do not have the means to trigger several commands during the processing of the current command.
- step E11 or E12 After deployment in step E11 or E12, the selected application state deployed T is executed in step E13 from the terminal TE.
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Microelectronics & Electronic Packaging (AREA)
- Computer Networks & Wireless Communication (AREA)
- Accounting & Taxation (AREA)
- Strategic Management (AREA)
- General Business, Economics & Management (AREA)
- Theoretical Computer Science (AREA)
- Stored Programmes (AREA)
Abstract
Description
Claims
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
FR0014364 | 2000-11-06 | ||
FR0014364A FR2816429B1 (fr) | 2000-11-06 | 2000-11-06 | Carte a puce avec descripteur d'application |
PCT/FR2001/003390 WO2002037435A1 (fr) | 2000-11-06 | 2001-10-31 | Carte a puce avec descripteur d'application |
Publications (1)
Publication Number | Publication Date |
---|---|
EP1337980A1 true EP1337980A1 (fr) | 2003-08-27 |
Family
ID=8856223
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP01983669A Withdrawn EP1337980A1 (fr) | 2000-11-06 | 2001-10-31 | Carte a puce avec descripteur d'application |
Country Status (4)
Country | Link |
---|---|
EP (1) | EP1337980A1 (fr) |
AU (1) | AU2002215096A1 (fr) |
FR (1) | FR2816429B1 (fr) |
WO (1) | WO2002037435A1 (fr) |
Families Citing this family (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN100343803C (zh) | 2004-07-26 | 2007-10-17 | 国际商业机器公司 | 将个性化计算环境从源平台移植到目标平台的方法和*** |
Family Cites Families (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
ATE197743T1 (de) * | 1995-08-04 | 2000-12-15 | Belle Gate Invest B V | Datenaustauschlsysteme mit tragbaren datenverarbeitungseinheiten |
EP0949595A3 (fr) * | 1998-03-30 | 2001-09-26 | Citicorp Development Center, Inc. | Méthode et système pour la gestion des applications pour une carte à puce multifonctionnelle |
-
2000
- 2000-11-06 FR FR0014364A patent/FR2816429B1/fr not_active Expired - Fee Related
-
2001
- 2001-10-31 EP EP01983669A patent/EP1337980A1/fr not_active Withdrawn
- 2001-10-31 WO PCT/FR2001/003390 patent/WO2002037435A1/fr active Application Filing
- 2001-10-31 AU AU2002215096A patent/AU2002215096A1/en not_active Abandoned
Non-Patent Citations (1)
Title |
---|
See references of WO0237435A1 * |
Also Published As
Publication number | Publication date |
---|---|
WO2002037435A1 (fr) | 2002-05-10 |
FR2816429B1 (fr) | 2003-04-11 |
AU2002215096A1 (en) | 2002-05-15 |
FR2816429A1 (fr) | 2002-05-10 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP1044436B1 (fr) | Procede de communication entre une station d'utilisateur et un reseau, notamment du type internet, et architecture de mise en oeuvre | |
EP1395962B1 (fr) | Deploiement d'application depuis une carte a puce | |
CA2309293A1 (fr) | Procede, carte a puce et terminaux pour effectuer des transactions a travers un reseau de telecommunication | |
EP1360665A1 (fr) | Procede et systeme de telepaiement | |
WO2000049584A1 (fr) | Systeme embarque possedant des moyens d'interface de reseau, et procede d'activation d'applications localisees dans ce systeme embarque | |
FR2817055A1 (fr) | Execution d'une application dans un objet electronique portable a faible capacite de memoire | |
WO2001065480A1 (fr) | Procede de commande d'une carte a puce | |
EP1337980A1 (fr) | Carte a puce avec descripteur d'application | |
WO2007144509A2 (fr) | Dispositif de memorisation amovible et appareil electronique aptes a l ' autre et procede de sauvegarde de donnees d ' environnement | |
EP1772000A2 (fr) | Terminal et procede de communication | |
EP1337979B1 (fr) | Deploiement d'application depuis une carte a puce | |
WO2007080328A2 (fr) | Procédé de génération d'un profil pour la personnalisation d'une entité électronique et système associé | |
FR2854261A1 (fr) | Procede d'execution d'une application logicielle par l'intermediaire d'un programme d'amorce logicielle et architecture informatique pour la mise en oeuvre du procede | |
WO2004056071A1 (fr) | Procede de communication entre serveurs avec conversion de format des donnees et dispositif pour sa mise en oeuvre | |
WO2002008897A1 (fr) | Protocole d'echange de messages entre applications implantees sur un systeme embarque, et systeme embarque correspondant | |
EP1065866A1 (fr) | Méthode et dispositif de contrôle d'accès à des services disponibles depuis un terminal de télécommunications | |
EP1086561B1 (fr) | Interfonctionnement entre des equipements par page d'accueil hypertexte | |
WO2011131852A1 (fr) | Système informatique de partage et procédé correspondant | |
EP0991032A1 (fr) | Procédé d'utilisation d'une carte en mode prépayé | |
WO2003073273A1 (fr) | Procede et dispositif de gestion decentralisee et personnalisee de services | |
WO2002039369A1 (fr) | Protocole de communication entre une carte a puce de type pro-active et son terminal d'accueil | |
WO2003069475A2 (fr) | Programme complementaire api pour traitement de transaction dans un reseau modulaire | |
WO2002058019A1 (fr) | Procede pour la creation de fichiers de donnees, prives securises et carte a puce comportant un fichier prive securise | |
WO2021123603A1 (fr) | Procede de gestion d'une pluralite de listes d'items | |
EP1233383A1 (fr) | Procédé et dispositif de gestion d'applications de cartes à puce |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
PUAI | Public reference made under article 153(3) epc to a published international application that has entered the european phase |
Free format text: ORIGINAL CODE: 0009012 |
|
17P | Request for examination filed |
Effective date: 20030606 |
|
AK | Designated contracting states |
Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LI LU MC NL PT SE TR |
|
AX | Request for extension of the european patent |
Extension state: AL LT LV MK RO SI |
|
RIN1 | Information on inventor provided before grant (corrected) |
Inventor name: PELLEGRINI, MARIE-CLAUDE Inventor name: POTONNIEE, OLIVIER |
|
RIN1 | Information on inventor provided before grant (corrected) |
Inventor name: PELLEGRINI, MARIE-CLAUDE Inventor name: POTONNIEE, OLIVIER |
|
RAP1 | Party data changed (applicant data changed or rights of an application transferred) |
Owner name: GEMALTO SA |
|
17Q | First examination report despatched |
Effective date: 20091015 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN |
|
18D | Application deemed to be withdrawn |
Effective date: 20111210 |