EP1637003B1 - Databases synchronization - Google Patents
Databases synchronization Download PDFInfo
- Publication number
- EP1637003B1 EP1637003B1 EP04736849A EP04736849A EP1637003B1 EP 1637003 B1 EP1637003 B1 EP 1637003B1 EP 04736849 A EP04736849 A EP 04736849A EP 04736849 A EP04736849 A EP 04736849A EP 1637003 B1 EP1637003 B1 EP 1637003B1
- Authority
- EP
- European Patent Office
- Prior art keywords
- application
- database
- synchronization
- command
- mobile apparatus
- 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.)
- Not-in-force
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
- G06F16/275—Synchronous replication
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
Definitions
- the invention deals with synchronization of databases.
- Data synchronization is the act of establishing equivalence between two data collections, where each data element in one item maps to a data item in the other, and each item and its respective mapping having a content which is equivalent.
- the existing technology allows Terminal Equipments to exchange and to synchronize data with an external device.
- the way that a synchronization process is requested depends on the protocol used, which is based on the capabilities of the terminal equipment.
- US 6, 505,215 discloses a method for synchronizing databases, a first database being stored in a first data processing system, a second database being stored in a second data processing system, said method comprising:
- the first data processing system is a small microprocessor based computer system such as a cellular phone or a handheld personal information manager.
- This invention particularly applies to security tokens such as smart cards, potentially equipped with a subscription related application provided by a service provider or network operator.
- This application can be indifferently a SIM (Subscriber Identity Module), a USIM (Universal Subscriber Identity Module), a RUIM (Removable User Identity Module) or any emergent smart card application managed/controlled by an entity such as an operator.
- SIM Subscriber Identity Module
- USIM Universal Subscriber Identity Module
- RUIM Removable User Identity Module
- the main objective of the invention is to apply the technology known by the above mentioned prior document to the control of the synchronisation processes of a mobile equipement using a security token thereby rendering the process easier and more reliable, in particular in the field of security.
- the invention has therefore as an object a method according to claim 1.
- the command will operate as an interface between the application and the synchronisation capabilities of the User Equipment.
- the card is owned and controlled by the operator. Moreover, the card applications can interact with the terminal, the user, and the network by means of existing "Card Application Toolkit" commands. In this way, according to the invention, the synchronization process is initiated by the card and not the mobile phone. This new command is added within the Card Application Toolkit that can be launched either locally by the user or a special application, or either remotely by the operator via the existing OTA (Over The Air) process. So, the invention can be applied to allow a user or a card application to command the execution of a data synchronization process between a UE (User Equipment) and an external entity.
- a User Equipment is a device allowing a user access to network services.
- the User Equipment is at least composed of a terminal equipment (e.g. a mobile equipment) and a smart card.
- this new command will send to the mobile the information needed to perform the synchronization: source device, destination device, used synchronization protocol, used transport layer, type of synchronization and database to synchronize.
- Figure 1 is a block diagram view of the architecture of a computer system on which the solution can be applied. On this figure appear some arrows illustrating different steps of the invention.
- a Mobile Network Operator implements a device management system consisting in the following components (see figure 1 ):
- the SIM application is able to ask the mobile equipment to start a synchronization process of his Local Device Management Database with the MNO's Device Management Database.
- This controlled synchronization may permit the MNO to offer different services to their subscribers and to perform various management functions. For example, knowing what is the version of an application currently installed in the mobile device, MNO is able to propose an available upgrade.
- the source database may be any database that can be accessed by the mobile equipment including databases (files, applications,...) of the SIM.
- This database can be indifferently located in the card CAR or in the mobile equipment MOB.
- the application in the card could use the card application toolkit functionalities to interact with other entities (e.g. the user).
- the user may be prompted before the synchronization command is sent, or it could be informed after the successful synchronization had taken place.
Abstract
Description
- The invention deals with synchronization of databases. Data synchronization is the act of establishing equivalence between two data collections, where each data element in one item maps to a data item in the other, and each item and its respective mapping having a content which is equivalent.
- The existing technology allows Terminal Equipments to exchange and to synchronize data with an external device. The way that a synchronization process is requested depends on the protocol used, which is based on the capabilities of the terminal equipment.
-
US 6, 505,215 discloses a method for synchronizing databases, a first database being stored in a first data processing system, a second database being stored in a second data processing system,
said method comprising: - a. A loading step in which an application is loaded into said first data processing system;
- b. An execution step in which the application executes a command;
- c. A requesting step in which said command requests the first data processing system to process a synchronization step, said command providing the first data processing system with the information about the synchronization parameters to be used for synchronizing the content of the first and the second databases.
- In this prior reference, the first data processing system is a small microprocessor based computer system such as a cellular phone or a handheld personal information manager.
- This invention particularly applies to security tokens such as smart cards, potentially equipped with a subscription related application provided by a service provider or network operator. This application can be indifferently a SIM (Subscriber Identity Module), a USIM (Universal Subscriber Identity Module), a RUIM (Removable User Identity Module) or any emergent smart card application managed/controlled by an entity such as an operator.
- If an operator wants to create his own data synchronisation applications (e.g. to provide management procedures linked to synchronisation process), some important facts shall be considered:
- "The operator does not own the terminal equipment, it is owned by the user (see the reference cited above).
- -Most terminal manufactures do not provide standardized capabilities to implement customizable applications in their terminals.
- -Applications present in the terminals are not controlled by the operator (see also the above cited reference).
- -There is a standardized way to update/download applications in the card. Other prior art is disclosed in : Smart Cards; Card Application Toolkit (CAT) (Release 6)", ETSI TS 102 223 V6.0.0, February 2003, pages 1 to 16.
- The main objective of the invention is to apply the technology known by the above mentioned prior document to the control of the synchronisation processes of a mobile equipement using a security token thereby rendering the process easier and more reliable, in particular in the field of security.
- The invention has therefore as an object a method according to claim 1.
- In this way, the command will operate as an interface between the application and the synchronisation capabilities of the User Equipment.
- The card is owned and controlled by the operator. Moreover, the card applications can interact with the terminal, the user, and the network by means of existing "Card Application Toolkit" commands. In this way, according to the invention, the synchronization process is initiated by the card and not the mobile phone. This new command is added within the Card Application Toolkit that can be launched either locally by the user or a special application, or either remotely by the operator via the existing OTA (Over The Air) process. So, the invention can be applied to allow a user or a card application to command the execution of a data synchronization process between a UE (User Equipment) and an external entity. A User Equipment is a device allowing a user access to network services. The User Equipment is at least composed of a terminal equipment (e.g. a mobile equipment) and a smart card.
- In our example, this new command will send to the mobile the information needed to perform the synchronization: source device, destination device, used synchronization protocol, used transport layer, type of synchronization and database to synchronize.
- It will be easier to understand the invention on reading the description below, given as an example and referring to the attached drawings.
-
Figure 1 is a block diagram view of the architecture of a computer system on which the solution can be applied. On this figure appear some arrows illustrating different steps of the invention. - A Mobile Network Operator (MNO) implements a device management system consisting in the following components (see
figure 1 ): - A database DB1 in the mobile (MOB) containing a list of basic parameters (i.e. IMEI, used language, sounds, etc...) and a list of applications and games that are installed in the device together with their operating parameters (version, size,...). This database is called Local Device Management Database. In another example, this database should have been stored in the SIM card itself.
- A copy of this database DB2 in a MNO's server. Let us call this database MNO's Device Management Database.
- A device management application in the SIM. This application is controlled and managed by the MNO. The application is in charge of analysing different parameters (e.g. time that the equipment has been connected) and can dialog with the MNO through a secured channel.
- Thanks to the command in the card Application Toolkit, following the MNO's synchronization policy, the SIM application is able to ask the mobile equipment to start a synchronization process of his Local Device Management Database with the MNO's Device Management Database.
- This synchronization can be summarized as follows: (see
fig.1 ) - A. The MNO installs a device management application in the subscriber's SIM. The MNO may update this application or modify any parameters used since this is completely controlled by him through a secured communication channel.
- B. The card CAR is informed of different events that may occur in the mobile equipment or in the network. The device management application may be informed of there events. This may include data regarding terminal capabilities.
- C. Following the MNO's policy contained in the device management application and considering the events and/or messages received, the device management application may conclude that a synchronization of the Mobile Local Database with the MNO's Device Management Database is needed.
- D. The device management application uses a new command in the card application toolkit: "Request Synchronization". This command informs the mobile that a new synchronization is requested. In a preferred embodiment, the device management application gives to the mobile synchronization agent the following information:
- synchronization protocol: Synchronization protocol that should be used. (e.g. SYNCML)
- session/transport layer: Transport or session layer that should be used (e.g. WSP)
- type of synchronization:Type of synchronization that should be used (e.g. refresh from the client)
- Source database: Unique Identifier of the local database in the client. Containing:
- i. device: identifier of the device containing the source database (e.g. IMEI of the mobile equipment)
- ii. database : identifier of the database (e.g. an URL of the Local Device Management Database)
- Target database: Unique identifier of the database in the server to be synchronized. Containing:
- i. device: identifier of the device containing the target database (e.g. URL of the MNO's server)
- ii. database : identifier of the database (e.g. an URL of the MNO's Device Management Database)
- Notification: Whether the Application shall be notified of the final result of the synchronization. (e.g. No notification requested)
- E. The Mobile equipment receives all the parameters. The mobile is now able to initiate a synchronization process using the information given in the "Request synchronization" command. Synchronization is performed between the Local Device Management Database in the mobile and the MNO's Device Management Database in the MNO's server. Advantageously, a program is able to receive all the parameters and to activate the synchronization process.
- F. The card device management application may be informed of the synchronization results if this was requested in the previous "Request synchronization" command.
- This controlled synchronization may permit the MNO to offer different services to their subscribers and to perform various management functions. For example, knowing what is the version of an application currently installed in the mobile device, MNO is able to propose an available upgrade.
- To be noted is that the source database may be any database that can be accessed by the mobile equipment including databases (files, applications,...) of the SIM. This database can be indifferently located in the card CAR or in the mobile equipment MOB.
- To be also noticed is that the application in the card could use the card application toolkit functionalities to interact with other entities (e.g. the user). In this case, for instance, the user may be prompted before the synchronization command is sent, or it could be informed after the successful synchronization had taken place.
Claims (9)
- A method for synchronizing databases (DB1, DB2), a first database (DB1) being stored in a mobile apparatus (MOB) or in a security token (CAR), controlled by an operator (OP), coupled to the mobile apparatus, a second database (DB2) being stored in a data processing system (MNO),
said method comprising:a. loading an application (APP) into the security token (CAR), the application being able to request the mobile apparatus to start a synchronisation process of the first database with the second database according to a synchronisation policy,b. executing the application (APP) ;c. receiving, by the application (APP), of messages or events that occur in the mobile apparatus (MOB) or in a network,d. in response to the messages or events received and following the synchronisation policy, concluding or not, by the application (APP), that a synchronisation of the first and second databases is needed, ande. if a synchronisation is needed, transmitting, by the application (APP), a command to the mobile apparatus (MOB) that informs the mobile apparatus that a new synchronisation is requested, said command providing the mobile apparatus (MOB) with information about synchronization parameters to be used for synchronizing the content of the first (DB1) and the second (DB2) databases,f. initiating, by the mobile apparatus (MOB), the synchronisation process of the first and second databases in response to the reception of the command. - The method according to claim 1, characterized in that the information includes the identifier of the database (DB2) to be synchronized.
- The method according to claim 1, characterized in that the information includes the synchronization protocol to be used between the mobile apparatus and the data processing system.
- The method according to claim 1, characterized in that the information includes the identifier of the first database (DB1).
- The method according to claim 1, characterized in that the security token is a smart card.
- The method according to claim 1, characterized in that the application is informed of the synchronization result between the 1st and 2nd databases.
- The method according to claim 1 or 6, characterized in that the application is informed of the synchronization result if this was requested in the command.
- The method according to claim 1, wherein the command is a card application toolkit command.
- The method according to claim 1, wherein the mobile apparatus (MOB) executes a program able to receive all the synchronisation parameters and to start the synchronisation process.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP04736849A EP1637003B1 (en) | 2003-06-20 | 2004-06-15 | Databases synchronization |
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP03291520A EP1489862A1 (en) | 2003-06-20 | 2003-06-20 | Database synchronization |
EP04736849A EP1637003B1 (en) | 2003-06-20 | 2004-06-15 | Databases synchronization |
PCT/IB2004/001984 WO2004114152A2 (en) | 2003-06-20 | 2004-06-15 | Databases synchronization |
Publications (2)
Publication Number | Publication Date |
---|---|
EP1637003A2 EP1637003A2 (en) | 2006-03-22 |
EP1637003B1 true EP1637003B1 (en) | 2010-01-27 |
Family
ID=33396048
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP03291520A Withdrawn EP1489862A1 (en) | 2003-06-20 | 2003-06-20 | Database synchronization |
EP04736849A Not-in-force EP1637003B1 (en) | 2003-06-20 | 2004-06-15 | Databases synchronization |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
EP03291520A Withdrawn EP1489862A1 (en) | 2003-06-20 | 2003-06-20 | Database synchronization |
Country Status (10)
Country | Link |
---|---|
US (1) | US20070174348A1 (en) |
EP (2) | EP1489862A1 (en) |
JP (1) | JP4592694B2 (en) |
KR (1) | KR101040022B1 (en) |
CN (1) | CN100524298C (en) |
AT (1) | ATE456918T1 (en) |
BR (1) | BRPI0411443A (en) |
DE (1) | DE602004025345D1 (en) |
ES (1) | ES2342171T3 (en) |
WO (1) | WO2004114152A2 (en) |
Families Citing this family (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7143117B2 (en) | 2003-09-25 | 2006-11-28 | International Business Machines Corporation | Method, system, and program for data synchronization by determining whether a first identifier for a portion of data at a first source and a second identifier for a portion of corresponding data at a second source match |
DE602006012746D1 (en) * | 2005-01-14 | 2010-04-22 | Asml Netherlands Bv | Lithographic apparatus and manufacturing method |
KR100748697B1 (en) | 2006-03-17 | 2007-08-13 | 삼성전자주식회사 | Method and system for distributed database multiple connection with application |
US7827138B2 (en) * | 2006-10-02 | 2010-11-02 | Salesforce.Com, Inc. | Method and system for synchronizing a server and an on-demand database service |
CN101296507B (en) * | 2007-04-29 | 2012-06-27 | 华为技术有限公司 | Method and system and server for implementing list information synchronization |
CN101227671B (en) * | 2007-12-28 | 2010-08-18 | 北京握奇数据系统有限公司 | Method for interactive managing data base with mobile terminal and smart card thereof |
KR101139610B1 (en) | 2010-07-29 | 2012-04-27 | 한국수력원자력 주식회사 | System and method for synchronized interfaces between engineering analysis programs using databased shared memory |
US11044244B2 (en) | 2018-09-18 | 2021-06-22 | Allstate Insurance Company | Authenticating devices via one or more pseudorandom sequences and one or more tokens |
KR102321294B1 (en) | 2020-10-20 | 2021-11-02 | 이동호 | Carbonization prevention folding ami with replaceable grill |
Family Cites Families (21)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP3319341B2 (en) * | 1997-06-20 | 2002-08-26 | 日本電気株式会社 | Data sharing system |
US6205448B1 (en) * | 1998-01-30 | 2001-03-20 | 3Com Corporation | Method and apparatus of synchronizing two computer systems supporting multiple synchronization techniques |
CA2276840A1 (en) * | 1999-07-05 | 2001-01-05 | Telefonaktiebolaget Lm Ericsson | Method and apparatus for synchronizing a database in portable communication devices |
US6779002B1 (en) * | 2000-06-13 | 2004-08-17 | Sprint Communications Company L.P. | Computer software framework and method for synchronizing data across multiple databases |
FR2810482B1 (en) * | 2000-06-15 | 2003-05-16 | Sagem | METHOD FOR MANAGING A COMMUNICATION MODULE AND DEVICE COMPRISING SUCH A MODULE |
US6813498B1 (en) * | 2000-10-27 | 2004-11-02 | Lucent Technologies Inc. | Apparatus, method and system for detection and recovery of missing wireless devices in communication systems |
US20020055939A1 (en) * | 2000-11-06 | 2002-05-09 | Joseph Nardone | System for a configurable open database connectivity conduit |
US20020069192A1 (en) * | 2000-12-04 | 2002-06-06 | Aegerter William Charles | Modular distributed mobile data applications |
US6824064B2 (en) * | 2000-12-06 | 2004-11-30 | Mobile-Mind, Inc. | Concurrent communication with multiple applications on a smart card |
AU2002237758A1 (en) * | 2001-01-03 | 2002-07-16 | Synchrologic, Inc. | A system and method for data synchronization between remote devices |
US7418254B2 (en) * | 2001-02-20 | 2008-08-26 | Microsoft Corporation | Mobile communication device dynamic service application and dynamic service application scripting |
JP4225729B2 (en) * | 2001-03-06 | 2009-02-18 | シャープ株式会社 | Information management device |
US7266840B2 (en) * | 2001-07-12 | 2007-09-04 | Vignette Corporation | Method and system for secure, authorized e-mail based transactions |
JP2003157190A (en) * | 2001-09-05 | 2003-05-30 | Matsushita Electric Ind Co Ltd | Synchronizing message processing method |
JP2003134257A (en) * | 2001-10-23 | 2003-05-09 | Casio Comput Co Ltd | Information terminal and information terminal setting program |
JP4142866B2 (en) * | 2001-11-07 | 2008-09-03 | カシオソフト株式会社 | Database synchronization apparatus and program |
CA2467404A1 (en) * | 2001-11-15 | 2003-05-30 | Visto Corporation | System and methods for asychronous synchronization |
US6676022B1 (en) * | 2002-10-04 | 2004-01-13 | Mobile-Mind, Inc. | Smart card system with command queuing |
US6925156B2 (en) * | 2002-12-20 | 2005-08-02 | International Business Machines Corporation | Pre-connection telephony data synchronization |
US20050021388A1 (en) * | 2003-05-30 | 2005-01-27 | Hatcher Christopher L. | Survey management system and method of using the same |
US7584201B2 (en) * | 2005-08-10 | 2009-09-01 | Qwest Communications International, Inc | Management of mobile-device data |
-
2003
- 2003-06-20 EP EP03291520A patent/EP1489862A1/en not_active Withdrawn
-
2004
- 2004-06-15 CN CNB2004800172835A patent/CN100524298C/en not_active Expired - Fee Related
- 2004-06-15 EP EP04736849A patent/EP1637003B1/en not_active Not-in-force
- 2004-06-15 JP JP2006516553A patent/JP4592694B2/en not_active Expired - Fee Related
- 2004-06-15 US US10/561,012 patent/US20070174348A1/en not_active Abandoned
- 2004-06-15 WO PCT/IB2004/001984 patent/WO2004114152A2/en active Application Filing
- 2004-06-15 BR BRPI0411443-4A patent/BRPI0411443A/en not_active Application Discontinuation
- 2004-06-15 AT AT04736849T patent/ATE456918T1/en not_active IP Right Cessation
- 2004-06-15 DE DE602004025345T patent/DE602004025345D1/en active Active
- 2004-06-15 ES ES04736849T patent/ES2342171T3/en active Active
- 2004-06-15 KR KR1020057024343A patent/KR101040022B1/en not_active IP Right Cessation
Also Published As
Publication number | Publication date |
---|---|
US20070174348A1 (en) | 2007-07-26 |
EP1637003A2 (en) | 2006-03-22 |
EP1489862A1 (en) | 2004-12-22 |
ES2342171T3 (en) | 2010-07-02 |
JP4592694B2 (en) | 2010-12-01 |
WO2004114152A3 (en) | 2005-02-17 |
KR101040022B1 (en) | 2011-06-08 |
BRPI0411443A (en) | 2006-07-18 |
CN100524298C (en) | 2009-08-05 |
JP2007520779A (en) | 2007-07-26 |
ATE456918T1 (en) | 2010-02-15 |
CN1810057A (en) | 2006-07-26 |
DE602004025345D1 (en) | 2010-03-18 |
KR20060073893A (en) | 2006-06-29 |
WO2004114152A2 (en) | 2004-12-29 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11039301B2 (en) | Apparatuses, methods and systems for implementing a system-on-chip with integrated reprogrammable cellular network connectivity | |
EP1825702B1 (en) | Backup system and method in a mobile telecommunication network | |
DE60218124T2 (en) | Apparatus and method for restricting access to and storage of content | |
EP3446502B1 (en) | Method, servers and system for downloading an updated profile | |
EP3337219B1 (en) | Carrier configuration processing method, device and system, and computer storage medium | |
US20100281139A1 (en) | Mobile terminal and associated storage devices having web servers, and method for controlling the same | |
RU2004119554A (en) | SYSTEM AND METHOD OF IDENTIFICATION AND ACCESS TO NETWORK SERVICES | |
EP1733580A1 (en) | Updating of the preferred roaming list (prl) in a sim (subscriber identity module) / ruim (removable user identity module) card. | |
CN102088691A (en) | User authentication and identification system and method for mobile internet application of mobile phone | |
US10901716B2 (en) | Implicit file creation in APDU scripts | |
US11051160B2 (en) | Apparatuses, methods and systems for implementing a system-on-chip with integrated reprogrammable cellular network connectivity | |
US20230319577A1 (en) | Postponed esim delivery to secondary mobile wireless device for cellular wireless service subscription | |
EP3257281A1 (en) | Communication with plurality of cellular networks using cellular modem and virtual subscriber identity modules stored in software-based embedded universal integrated circuit card (euicc) | |
EP3729845B1 (en) | Adaptive esim delivery | |
EP1637003B1 (en) | Databases synchronization | |
KR20050096930A (en) | Communication between a smart card and a server | |
US20040040022A1 (en) | Method and apparatus for just-in-time provisioning application-related information at a communication device | |
US11930558B2 (en) | Method for providing subscription profiles, subscriber identity module and subscription server | |
CN109639629B (en) | Data access processing method and device, computer equipment and storage medium | |
CN113825121B (en) | Delaying delivery of esims to secondary mobile wireless devices subscribed to cellular wireless services | |
RU2292668C1 (en) | Method for controlling additional services in mobile communication networks | |
CN116112925A (en) | Subscription updating method, device, network element and medium | |
CN102737111A (en) | Software component information acquiring method of software component management object and service system | |
WO2008044959A1 (en) | Method for managing additional services in mobile telecommunications networks | |
WO2002075580A1 (en) | Mass subscriber handling |
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: 20051209 |
|
AK | Designated contracting states |
Kind code of ref document: A2 Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LI LU MC NL PL PT RO SE SI SK TR |
|
DAX | Request for extension of the european patent (deleted) | ||
17Q | First examination report despatched |
Effective date: 20080620 |
|
RAP1 | Party data changed (applicant data changed or rights of an application transferred) |
Owner name: GEMALTO SA |
|
RIC1 | Information provided on ipc code assigned before grant |
Ipc: H04W 56/00 20090101AFI20090626BHEP Ipc: G06F 17/30 20060101ALI20090626BHEP |
|
GRAP | Despatch of communication of intention to grant a patent |
Free format text: ORIGINAL CODE: EPIDOSNIGR1 |
|
GRAS | Grant fee paid |
Free format text: ORIGINAL CODE: EPIDOSNIGR3 |
|
GRAA | (expected) grant |
Free format text: ORIGINAL CODE: 0009210 |
|
AK | Designated contracting states |
Kind code of ref document: B1 Designated state(s): AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IT LI LU MC NL PL PT RO SE SI SK TR |
|
REG | Reference to a national code |
Ref country code: GB Ref legal event code: FG4D |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: EP |
|
REG | Reference to a national code |
Ref country code: IE Ref legal event code: FG4D |
|
REF | Corresponds to: |
Ref document number: 602004025345 Country of ref document: DE Date of ref document: 20100318 Kind code of ref document: P |
|
REG | Reference to a national code |
Ref country code: NL Ref legal event code: VDEP Effective date: 20100127 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: AT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20100127 |
|
REG | Reference to a national code |
Ref country code: ES Ref legal event code: FG2A Ref document number: 2342171 Country of ref document: ES Kind code of ref document: T3 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: NL Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20100127 Ref country code: PT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20100527 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: FI Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20100127 Ref country code: PL Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20100127 Ref country code: SI Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20100127 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: RO Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20100127 Ref country code: CY Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20100127 Ref country code: GR Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20100428 Ref country code: EE Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20100127 Ref country code: SE Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20100127 Ref country code: BE Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20100127 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: SK Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20100127 Ref country code: CZ Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20100127 Ref country code: BG Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20100427 |
|
PLBE | No opposition filed within time limit |
Free format text: ORIGINAL CODE: 0009261 |
|
STAA | Information on the status of an ep patent application or granted ep patent |
Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT |
|
26N | No opposition filed |
Effective date: 20101028 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: DK Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20100127 Ref country code: MC Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20100630 |
|
REG | Reference to a national code |
Ref country code: CH Ref legal event code: PL |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: IT Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20100127 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: LI Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20100630 Ref country code: IE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20100615 Ref country code: CH Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20100630 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: HU Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20100728 Ref country code: LU Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20100615 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: TR Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT Effective date: 20100127 |
|
REG | Reference to a national code |
Ref country code: FR Ref legal event code: PLFP Year of fee payment: 13 |
|
REG | Reference to a national code |
Ref country code: FR Ref legal event code: PLFP Year of fee payment: 14 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: DE Payment date: 20170522 Year of fee payment: 14 Ref country code: GB Payment date: 20170526 Year of fee payment: 14 Ref country code: FR Payment date: 20170523 Year of fee payment: 14 |
|
PGFP | Annual fee paid to national office [announced via postgrant information from national office to epo] |
Ref country code: ES Payment date: 20170703 Year of fee payment: 14 |
|
REG | Reference to a national code |
Ref country code: DE Ref legal event code: R119 Ref document number: 602004025345 Country of ref document: DE |
|
GBPC | Gb: european patent ceased through non-payment of renewal fee |
Effective date: 20180615 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: DE Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20190101 Ref country code: FR Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20180630 Ref country code: GB Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20180615 |
|
REG | Reference to a national code |
Ref country code: ES Ref legal event code: FD2A Effective date: 20190916 |
|
PG25 | Lapsed in a contracting state [announced via postgrant information from national office to epo] |
Ref country code: ES Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES Effective date: 20180616 |