[go: up one dir, main page]

EP2611221B1 - Gestion des informations de licence pour un terminal de communication - Google Patents

Gestion des informations de licence pour un terminal de communication Download PDF

Info

Publication number
EP2611221B1
EP2611221B1 EP12187587.6A EP12187587A EP2611221B1 EP 2611221 B1 EP2611221 B1 EP 2611221B1 EP 12187587 A EP12187587 A EP 12187587A EP 2611221 B1 EP2611221 B1 EP 2611221B1
Authority
EP
European Patent Office
Prior art keywords
terminal
license
message
application
security module
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.)
Active
Application number
EP12187587.6A
Other languages
German (de)
English (en)
Other versions
EP2611221A1 (fr
Inventor
Ulrich Seifert
Thorsten Nozulak
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Vodafone Holding GmbH
Original Assignee
Vodafone Holding GmbH
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Vodafone Holding GmbH filed Critical Vodafone Holding GmbH
Publication of EP2611221A1 publication Critical patent/EP2611221A1/fr
Application granted granted Critical
Publication of EP2611221B1 publication Critical patent/EP2611221B1/fr
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/20—Services signaling; Auxiliary data signalling, i.e. transmitting data via a non-traffic channel
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/10—Protecting distributed programs or content, e.g. vending or licensing of copyrighted material ; Digital rights management [DRM]
    • G06F21/12—Protecting executable software
    • G06F21/121—Restricting unauthorised execution of programs
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/03—Protecting confidentiality, e.g. by encryption
    • H04W12/033—Protecting confidentiality, e.g. by encryption of the user plane, e.g. user's traffic
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/04—Key management, e.g. using generic bootstrapping architecture [GBA]
    • H04W12/041—Key generation or derivation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/04—Key management, e.g. using generic bootstrapping architecture [GBA]
    • H04W12/043—Key management, e.g. using generic bootstrapping architecture [GBA] using a trusted network node as an anchor
    • H04W12/0433—Key management protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/08—Access security
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/10—Integrity
    • H04W12/102—Route integrity, e.g. using trusted paths
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/30—Security of mobile devices; Security of mobile applications
    • H04W12/35—Protecting application or service provisioning, e.g. securing SIM application provisioning
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
    • H04W12/40—Security arrangements using identity modules
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
    • H04W4/60—Subscription-based services using application servers or record carriers, e.g. SIM application toolkits

Definitions

  • the invention relates to licenses for executing applications and / or content for a communication terminal.
  • the invention relates to a method and a system for controlling the release of the use of at least one application and / or content in a communication terminal, wherein the usage is released when the presence of a valid license information in a security module of the communication terminal is detected.
  • the communication terminal may in particular be a mobile terminal
  • the unauthorized use of electronic content, such as multimedia files, and applications in mobile devices can be prevented by means of licenses. Due to a license acquired by the user, authorized users are provided with license information stored in the users' mobile terminals. Access to the contents or applications is only permitted if valid license information is present in the terminal.
  • the license information can be stored in a chip card, in particular a SIM (Subscriber Identity Module) card, which is used for the identification and / or authentication of a subscriber in a mobile radio network. This is for example in the GB 2 387 505 A described.
  • the licensor often does not want to grant permission to use the content or applications for an unlimited period of time, for example, because license fees must be paid at regular intervals.
  • the validity of license information may be limited in time, as in the aforementioned document GB 2 387 505 A is proposed.
  • such a time limit has the disadvantage that a new license information must be sent to the user and deposited in his mobile device, if the user wants to continue using content or an application after the expiration of validity and is entitled to use.
  • license information can not be deleted independently of a validity period, if this is desired, for example, due to a termination of the user regardless of the term.
  • US 2007/0198834 A1 discloses a method for authentication of applications, wherein the authentication is performed by means of a cryptogram transmitted by a control server, the cryptogram being based on data transmitted by a terminal.
  • a security module locally connected to the terminal determines a first control value based on the cryptogram and a second control value based on licensing data stored in the security module.
  • US 2007/0130079 A1 discloses a system and method for controlling software applications and associated licenses.
  • the object is achieved by a method according to claim 1, by a computer program according to claim 9, by a communication terminal according to Claim 10 and by a system according to claim 12.
  • Embodiments of the method, the computer program and the communication terminal are specified in the dependent claims.
  • a method for controlling the release of the use of content and / or an application wherein the use is released when the presence of a valid license information in a security module of a communication terminal is detected.
  • the method is characterized in that a valid license information stored in the security module is deleted from the security module on the basis of the receipt of a deletion message or marked as invalid in the security module.
  • the invention proposes a communication terminal for enabling the use of content and / or an application, wherein the communication terminal comprises a security module and the use is releasable, if the presence of a valid license information in the security module is detected.
  • the security module is configured such that a valid license information stored in the security module is deleted from the security module or marked as invalid in the security module due to the receipt of a deletion message in the communication terminal.
  • the invention also provides a computer program comprising software code sections with instructions on the basis of which the method and / or an embodiment of the method is executed when the program is executed by a processor.
  • An advantage of the invention is that a license information already issued to a user and deposited in a security module is discarded as needed due to the receipt of a message. This can happen, for example, if the validity of a license - for example due to a deadline - terminated without the user renewing the license. If the license is extended, however, the license information can be retained. In addition, it is possible to instruct the security module at any time to discard license information at any time.
  • the security module is in a communication terminal, which may be configured in particular as a mobile terminal, which is connectable to a mobile network include.
  • the computer program and the terminal the license information is deleted or marked invalid as a result of receiving the control message.
  • a further embodiment of the method, the computer program, the terminal and the system makes it possible to access the license information remotely in the Security module to deposit.
  • the license information is sent together with an installation message to the communication terminal and stored in the security module due to the receipt of the installation message.
  • the deletion or the marking as invalid, but also the deposit of the license information in the terminal can be made based on a message sent to the terminal.
  • the computer program and the terminal provide that the deletion message and / or the installation message comprise at least one authentication feature and wherein the license information is discarded due to a successful examination of the authentication feature or the license information is stored in the security module due to a successful check of the authentication feature.
  • the authentication feature can be generated with a cryptographic key of a trusted license server. Furthermore, it can be provided that the authentication feature is generated with a key that is uniquely assigned to the security module. In one embodiment, the authentication feature is an encryption of at least part of the deletion message or of the installation message.
  • the computer program and the terminal is a so-called over-the-air (OTA) message sent using the OTA mechanism, which allows secure remote access to security modules .
  • OTA over-the-air
  • the deletion message and / or the installation message can be sent to the terminal via a mobile radio network to which the communication terminal is connected.
  • the license authorizing the user of the terminal to use the content and / or the application by means of the terminal can be managed in a license server.
  • the deletion message is sent to the terminal when a license server determines that a license of the user of the terminal to use the content and / or the application is completed. The determination can be made in the license server, for example, due to the expiration of a validity period of the license, wherein the transmission of the deletion message is preferably omitted if the license is extended before the expiry of the validity period.
  • the contents and / or the application can be used in the communication terminal in which the license information can be stored. Likewise it can be provided that the contents and / or the application is used in a further device that is connected to the communication terminal. This makes it possible to use the communication terminal for the activation of applications on another device.
  • the further device which may be, for example, a PC (personal computer), may communicate with the communication terminal via a wired or a wireless connection.
  • the security module is an identification module connected to the terminal for identification and / or authentication in the mobile radio network, which is contained in particular in a chip card connected to the terminal.
  • the identification module can be designed, for example, as a SIM card or as a chip card with a USIM (Universal Subscriber Identity Module).
  • protected applications 102i a, b, c
  • three protected applications 102i are shown. However, fewer or more protected applications 102i may be executed in the terminal 101.
  • the applications 102i each comprise a software code which is stored in a memory unit of the terminal 101 and executed in a processor unit, which may be, for example, the main processor unit of the terminal 101 comprising one or more processors.
  • the applications can access further units of the terminal 101 which are needed to provide the functionality.
  • the applications have access to a user interface of the terminal 101 in order to be able to interact with the user of the terminal 101.
  • the user interface may include output means such as a display unit and / or a speaker unit and input means such as a keyboard and / or a touch screen and a microphone.
  • the protected function is preferably the main function provided by the application 102i. In addition to the main functions, additional functions can be provided by an application 102i which can also be executed without license information 105i present in the terminal 101. An example of this is a function for installing and / or ordering license information 105i.
  • the license information 105i can be transmitted to the terminal 101 via a mobile radio network 301. It can be output via the mobile radio network 301 or in some other way, in particular by the operator of the mobile radio network 301, who can also make the protected applications 102i available. In this case, the applications 102i can provide, for example, additional functions for the use of the terminal 101 in a mobile radio network 301.
  • An example of this is an application 102i for encryption and decryption of messages and / or voice communication, which is sent via the mobile network 301 or takes place. In principle, however, any protected applications can be provided.
  • license information 105i does not have to be output by the operator of the mobile radio network 301, but can be issued by be provided to any providers over the cellular network 301 or otherwise.
  • the installation of the protected applications 102i can be carried out in any manner known to those skilled in the art as well as in conventional unprotected applications which are executable without the presence of license information 105i in the terminal 101 and installed in the terminal 101 in addition to the protected applications can.
  • the protected applications can already be installed in the terminal 101 during the production or initial configuration.
  • a later installation can be done.
  • the software code to be installed can be transmitted to a protected application 102i via the mobile radio network 301 or in some other way to the terminal 101.
  • the installation of the license information 105i belonging to an application 102i takes place in a separate process, which is carried out in addition to the installation of the application 102i. This process can in particular also be initiated after installation of the application 102i using the installed application 102i.
  • the terminal 101 is in the in the FIG. 1 illustrated embodiment as a mobile communication terminal 101, such as a mobile phone, a smartphone, a tablet or notebook computer or the like, running, which can connect via an access network wirelessly with a mobile network to use provided by the mobile network mobile services.
  • Examples of services that can be provided over the mobile network and for the use of which the terminal 101 can be used are services for voice or video calls, data services for the access to data networks, such as the Internet, and news services, such as SMS ( Short Message Service), MMS (Multimedia Messaging Service) or e-mail.
  • the terminal 101 comprises a radio module 103, with which the terminal 101 can be connected to a mobile radio network via the corresponding radio access network.
  • the radio module 103 has this over the required radio technology, for example an antenna with associated peripheral components, and via a control device for controlling the radio module 103 and for carrying out the data processing necessary for the data exchange with the mobile radio network or the radio access network.
  • the terminal 101 For access to a mobile network, the terminal 101 further comprises an identification module 104, which provides data and processes needed for the access of the terminal 101 to a mobile network.
  • an identification module 104 data and processes for subscriber identification and authentication in the mobile network are used.
  • the subscriber identification and authentication is usually performed when logging into a mobile network and includes the identification of the identification module 104 based on an identifier, which are sent from the identification module 104 to the mobile network, and the authentication of the identification module 104 based on information contained in the identification module 104 can be calculated using predetermined algorithms and information.
  • the identification module 104 has a special security architecture which prevents unauthorized access to data and processes, in particular to the aforementioned data and processes used for accessing the mobile radio network.
  • the identification module 104 is a secured chip that is contained in a smart card that can be detachably plugged into a card reader of the terminal 101.
  • the identification module 104 may be a SIM or USIM card used for access to a mobile network 301 known as GSM (Global System for Mobile Communications), UMTS (Universal Mobile Telecommunications System). - or LTE (Long Term Evolution) network is executed.
  • GSM Global System for Mobile Communications
  • UMTS Universal Mobile Telecommunications System
  • LTE Long Term Evolution
  • the identification module 104 may also be a chip that is firmly integrated with the terminal 101.
  • the chip can in particular also be configured as a SIM or USIM chip.
  • a secure software module which is executed on a processor of the terminal 101, which is also used for other tasks and which may be, for example, the main processor of the terminal 101.
  • the identification module 104 is registered in a mobile radio network 301, which is also referred to as the home network of the identification module 104 or of the user of the terminal 101 and which is described in US Pat FIG. 2 is shown.
  • the home network 301 can be the mobile radio network with whose operator the user has concluded a mobile telephone contract.
  • the identification module 104 is output by the operator of the home network 301 or on his behalf to the user and preconfigured beforehand in a secure process. This comprises a personalization in which data predetermined by the operator of the home network 301 for the identification and authentication of the identification module 104, processes predetermined by the operator, such as encryption algorithms used in the authentication, and further data specified by the operator are installed in the identification module 104.
  • the identification module 104 serves as a security module for the secure storage of the license information 105i available in the terminal 101, which are required for executing the protected applications 102i.
  • the identification module 104 has a control unit 106. This is preferably designed as a software unit installed and executed in the identification module 104.
  • the license information 105i are embodied as codes which are checked in the associated applications 102i in order to enable the applications 102i or their protected functions.
  • control unit 106 may also perform the test for application 102i and report the result of the test to application 102i.
  • the license information may also be configured merely as flags or the like, which may be read out by the control unit 106 in order to report their presence to the protected applications 102i.
  • a protected application 102i can send a corresponding request to the control unit 106.
  • information can be used that can be stored in the application 102.
  • the control unit 106 checks whether a license information is stored in the identification module 104 for the requesting protected application 102i. If this is not the case, the control unit 106 sends an error message to the requesting application 102i. Preferably, this will not be executed after receiving the error message or does not release access to the protected functions.
  • control unit 106 determines that the requesting application 102i has license information, it transmits it to the application 102i in one embodiment, which is a code, so that it can check the license information.
  • the license information can also be checked in the control unit 106. The check can be carried out, for example, based on a comparison of the existing license information 105i with reference information stored in the application. In order to enable a check in the control unit 106, the reference information can be previously transmitted from the application to the control unit 106.
  • the application 102i is then executed or releases access to the protected functionalities. The execution or release takes place when the validity of the existing license information 105i has been found. Otherwise, the application 102i is not executed or the release of the protected functionalities is omitted.
  • the control unit 106 merely notifies its presence to the requesting application 102i, which then proceeds in exactly the same way as described above for the case of a successful check of the license information 105i.
  • a further device 201 may be provided instead of the terminal 101 in further embodiments, which is connected to the communication terminal 101, as it is exemplary of the application 102a in the FIG. 3 is illustrated.
  • the device 201 may be, for example, a PC or other device for executing applications 102i.
  • Via a communication link 202 the device 201 is connected to the terminal 101.
  • the communication link 202 is preferably temporary and may be configured as a wired or wireless communication link.
  • a wireless communication connection which generally allows a simpler connection of the devices than a wired communication connection, can be designed as a radio connection, for example as a Bluetooth, NFC (Near Field Communication) or ZigBee connection.
  • a program of the further device 201 embodied as a middleware can allow the application 102a access to the communication connection 202 or to an interface of the further device 201 via which the communication connection 202 is established.
  • the application 102a communicates in one embodiment via the Communication connection 202 with the control device 106 of the identification module 104.
  • the application 102 a sends a corresponding request to the control device 106 via the communication connection 202, which is answered by the control device 106.
  • the response of the controller 106 is sent back to the application 106 via the communication link 202.
  • the request and the response are basically configured in the same way as described above in connection with applications 102i executed in the communication terminal 101.
  • the processing of the request of the application in the control device 106 also takes place in the manner already described above.
  • the communication terminal 101 or the contained identification module 104 can also be used for the activation of a protected application 102a in further devices 201.
  • the user of the applications 102a ensures that the communication connection between the further device 201 and the communication terminal 101 is established.
  • temporary communication link 201 can be made to various other devices 201 that are operated at different locations.
  • the identification module 104 can be used to unlock applications 102a that are executed in different further devices 201.
  • FIG. 2 schematically illustrates a system in which the license information 105i can be deposited via the mobile network 301 in the identification module 104 and other identification modules 104 and deposited in the identification module (104) license information 105i can be deleted or marked as invalid, so they do not Release of a protected application 102i or protected functions of such can be used.
  • the deposit and the deletion can be found in the FIG. 2 illustrated System controlled by a license server 302. It is understood that this can be done in the same way for a plurality of terminals 101 or identification modules 104 and is not limited to the illustrated identification module 104, which in the FIG. 2 is shown as an example.
  • the license server 302 is operated by the organization issuing the license information. This may be the same organization that also provides the applications 102i. However, the operator of the license server 302 can also offer the functionalities of the license server 302 to one or more organizations providing the applications 102i, which thus can use the license server 302 for depositing and / or deleting license information 105i. In one embodiment, the license server 302 is operated by the operator of the mobile radio network 301 in order to deposit license information 105i for applications 102i in identification modules or to delete stored license information 105i or to mark it as invalid.
  • the license server 302 may have a license database 307 for managing the license information output to the users of terminals 101 in which the identification modules 104 in which license information 105i is stored are registered in association with the license information 105i.
  • the installation of the license information may be controlled by the license server 302, as described in more detail below, wherein the license is registered in the license database 307 due to the output by the license server 302.
  • license information 105i may also be stored in an identification module 104 in other ways.
  • the license can already be stored in the production or personalization of the identification module 104 or in a configuration that takes place after the output of the identification module 104.
  • the output of the license information becomes 105i and the user who is authorized to use an application on the basis of the license, or the associated identification module 104 reported to the license server 302 and also registered in the license database 307.
  • the installation of a license information 105i for an application installed in the terminal 101 or in the further device 201 can take place on the basis of the acquisition of a license by the user of the terminal 101.
  • the license can be acquired simultaneously with the application 102i if it is installed in the terminal 101 or in the further device 201, or separately, for example, after installation by means of a corresponding function of the application 102i.
  • the acquisition of the license may be made in a suitable manner via the license server 302 or via a device coupled to the license server 302 and connected to the payment of a license fee which the user pays for the use of the application.
  • the license may for example be acquired together with the user's subscription in his home network 301, the license information in particular in this case being able to be stored in the identification module 104 during personalization.
  • the license of the user for the use of a protected application 102i is limited in time and expires after a predetermined validity period, which is stored in the license database 307.
  • the license may preferably be extended by the user, whereby renewal may entail the payment of further license fees.
  • a corresponding function can be provided by the protected application 102i, by means of which the extension can be handled by means of a communication with the license server 302 or a device coupled to the license server 302, which reports the extension of the license to the license server 302 , Likewise, the extension can also independently of the application via the license server 302 or provided for this purpose coupled with the license server 302 device be handled.
  • the new validity period of the license is deposited in the license database 307 of the license server 302, replacing the original validity period.
  • the relevant validity periods for the registered licenses stored in the license database 307 are monitored by the license server 302. If the license server 302 determines that the license for a license to use a protected application 102i expires, the license server 302 causes the deletion message to be transmitted to the identification module 104 in which the license information 105i associated with the license is stored so that the license information 105i be discarded. As a result, the user can no longer use the protected applications after expiration of the validity period. If, however, the user extends the license before the expiry of the validity period and a new validity period is deposited in the license database 307 before expiry of the valid period, the deletion message can be omitted, so that the license information 105i stored in the identification module 104 can still be used.
  • licenses for protected applications 102i are linked to other conditions in addition or as an alternative to the temporal binding to validity periods. For example, it may be necessary for the user of the terminal 101 in the home network 301 to have a subscription of a certain type in order to be entitled to use a protected application 102i. As long as the condition is met, the license to use the protected application 102i is valid. On the other hand, if the condition is no longer met, for example because of a change in the user's subscription, the user's license will become invalid.
  • the license server 302 sends a deletion message to the user's identification module 104 in which the license information 105i associated with the license is stored so that the license information 105i is discarded.
  • the termination of validity the license due to the termination of the validity condition may be detected in the license server 302 or in another device connected to the license server 302 instructing the license server 302 to transmit the deletion message when it determines the cessation of validity.
  • the device may, for example, be provided for the administration of subscriptions in the mobile radio network 301 and determine the termination of the validity if the subscription is changed or deleted for a user.
  • a mechanism for remote access implemented in the identification modules 104 is preferably used. Such a mechanism enables wireless access to the identification modules 104 registered in the mobile radio network 301 after the output in order to make adjustments. For example, data and processes or programs in the identification module 104 can be changed, supplemented or deleted remotely. By means of the remote access mechanism, such adjustments can be made without having to adapt or reissue the identification modules 104 in a service station of the mobile operator or another provider.
  • the remote access mechanism is an OTA mechanism in which an OTA server 303 can send messages to registered identification modules 104, the data for installation in the identification modules 104, and / or commands for modifying data or executing processes and programs may be included in the identification modules 104.
  • the OTA server 303 may be arranged in the mobile radio network 301 and be operated, for example, by the associated mobile radio provider, wherein in the OTA server 303 all identification modules 104 may be registered, to which the However, the OTA server 303 can also be operated outside the mobile radio network 301 by a trustworthy organization and / or with any predetermined selection of registered identification modules 104.
  • the messages sent by the OTA server 303 to an identification module 104 are encrypted with a cryptographic key to protect them from unauthorized manipulations in the transport path and to prevent unauthorized third parties from issuing valid OTA messages can send to an identification module 104.
  • received OTA messages are decrypted with a corresponding cryptographic key. The decryption also checks the authenticity of the message since the message can only be successfully decrypted if it has been encrypted with the correct key stored only in the OTA server 303.
  • the keys used for encryption in the OTA server 303 and the keys used for decryption in the identification modules 104 may each form a symmetric key pair. However, the use of asymmetric key pairs may also be provided.
  • the OTA key used in an identification module 104 may be deposited in the production or personalization of the identification module 104 therein.
  • the identifier under which the cryptographic keys assigned to the identification modules 104 are respectively stored in the database 304 of the OTA server 303 can be one configured as MSISDN (Mobile Subscriber Integrated Services Digital Network Number) Identification module 104 associated call number, which can also be used to address the OTA messages to the identification module 104.
  • MSISDN Mobile Subscriber Integrated Services Digital Network Number
  • the identifiers may also include other identification codes associated with the identification modules 104. If the MSISDNs assigned to the identification modules are not contained in the identifiers used, these are preferably additionally stored in the database 304 of the OTA server 303 in order to be used by the OTA server 303 for addressing OTA messages to the identification modules 104 , Alternatively, the telephone numbers may be passed to the OTA server 303 when instructed to send an OTA message to an identification module 104.
  • the OTA messages are transmitted via a data transmission service provided in the mobile network 301.
  • a short message service can be used, which in one embodiment is the SMS (short message service) known per se.
  • SMS short message service
  • short messages are sent from a short message service center (SMSC) 305 of the mobile network 301 to terminals 101 connected to the mobile network 301.
  • SMS short message service center
  • the OTA server 303 has an SMS interface 306 via which it is connected to the SMSC 305.
  • the OTA server 303 via the SMS interface 306, transfers the content of the OTA message encrypted with the OTA key of the identification module 104 together with the MSISDN assigned to the identification module 104 to the SMSC 305.
  • the SMSC 305 then sends an SMS message configured as an OTA message using the identification module 108 associated phone number to the terminal 101 to which the identification module is connected. This basically happens in the same way as the transmission of other SMS messages to the Terminal 101.
  • the OTA message is preferably transparently, ie invisible to the user of the terminal 101, forwarded to the identification module 108 and initially decrypted in the identification module 104 and thereby, as explained above, also by means of a contained special identifier in the terminal 101 the OTA key of the identification module 104 is authenticated. After successful decryption the message is evaluated and contained control commands are executed.
  • an interface 308 is provided between the OTA server 303 and the license server 302, via which the license server 302 can communicate with the OTA server 303 and utilize functionalities of the OTA server 303.
  • the interface 308 may be used by the license server 302 to install license information 105i in identification modules 104.
  • To install (ie deposit) a license information 105i for a protected application 102i an installation message designed as an OTA message is sent to the identification module 104.
  • the license server 302 transfers via the interface 308 to the OTA server 303 a corresponding instruction for generating an OTA message with a control command for depositing a license information 105i for the application 102i to the OTA server.
  • the control command may be passed from the license server 302 for insertion into the installation message.
  • the protected application 102i is specified in the OTA message by a designation passed from the license server 302 to the OTA server 303. If the license information includes a code, then this is also passed from the license server 302 to the OTA server 303.
  • the license server 302 transmits the instruction for generating the installation message to the OTA server 303 together with an indication of the identification module 104 to which the message is to be transmitted. For this purpose, the license server 302, the identifier is registered to the OTA server 303.
  • the OTA server 303 After the OTA server 303 has received the instruction together with the aforementioned information, the OTA server generates an OTA message which contains the control command for depositing a license information and possibly the code contained in the license information. In addition, the OTA server 303 preferably takes over the name of the protected application 102i received from the license server 302 in the OTA message.
  • the OTA message is encrypted with the OTA key associated with the identification module 104 specified by the license server 302 and by the OTA server 303 based on the ID of the identification module 104 provided by the license server 302 in the database 304 of the OTA server 303 is determined.
  • the OTA message After being generated, the OTA message is sent to the identification module 104 or the terminal 101 in which the identification module 104 is contained. For this purpose, the OTA server 303 transmits the message together with the identification number assigned to the identification module 104 to the SMSC 305, which sends the message using the number.
  • the identification module 104 identifies by an identifier that this is an OTA message and decrypts the message using the OTA key present in the identification module 104. If the installation message has been successfully decrypted, it is evaluated in the identification module 104. Here, the identification module 104 recognizes the contained control command for depositing the license information 105i and executes it. In this case, the license information 105i for the protected application specified in the installation message is stored in the identification module 104 in such a way that it can be supplied to it by the control unit 106 upon request by the application. If the license information 105i contains a flag, it is set accordingly. If a code is included, it will be stored accordingly in the identification module 104 so that it will be deleted from the Control unit 106 can be passed to the secure application for testing, if it makes a corresponding request to the control unit 106.
  • the deposit of the license information 105i may optionally be confirmed to the license server 302 by an acknowledgment message automatically generated in the identification module 104.
  • the message can also be transmitted via the SMSC to the license server 302 by means of the SMS.
  • another message service can be used to transmit the confirmation message.
  • the confirmation message may be encrypted using the OTA key of the identification module 104.
  • the message is first communicated to the OTA server 303, which decrypts it with the OTA key associated with the identification module 104, and forwards the decrypted content to the license server 302.
  • a license information 105i can be stored in an identification module 104. Further possibilities for depositing license information 105i in the identification module 104 have already been described above and include a deposit in the personalization of the identification module 104 or in the configuration of an identification module 104 in a service station.
  • a license information 105i After a license information 105i has been deposited in an identification module 104, it can, as already described, be deleted or marked as invalid by means of a deletion message.
  • the transmission of a deletion message is preferably also initiated by the license server 302. This can happen, for example, when the license server 302 detects or notifies the license server 302 that the validity of a user's license to use a protected application is finished.
  • the license server 302 passes to the OTA server 303 via the interface 308 an instruction to generate a deletion message.
  • a corresponding deletion command which is included in the deletion message, may be transferred with the instruction from the license server 302 or already stored in the OTA server 303.
  • the license server 302 specifies the protected application 102i to which the license to be discarded relates.
  • the designation of the application 102i can be transferred, under which the associated license information is stored in the identification module 104 or enables the determination of the application or the license information in the identification module 104.
  • the identification module 104 is specified in which the license information to be discarded is stored.
  • the identifier can be transferred under which the identification module 104 is registered in the OTA server and which, as described above, can be the call number of the identification module 104.
  • the OTA server 303 After the OTA server 303 has received an instruction to generate a deletion message together with the aforementioned information about the interface from the license server 302, the OTA server 303 generates an OTA message containing the deletion command and the name of the protected application 102i, to which the license information to be discarded relates.
  • the OTA message is encrypted with the OTA key of the identification module 104 to be addressed. This key is determined on the basis of the specification of the identification module 104 received in the database 304 of the OTA server 303 from the license server 302.
  • the encrypted deletion message is passed from the OTA server 303 along with the call number to the SMSC 305, which is used to address the deletion message. From the SMSC 305, the cancellation message is then sent over the mobile network 301 using the received number transmitted to the identification module 104 and the terminal 101, in which the identification module 104 is inserted.
  • the deletion message is then transmitted by means of the message service used for the transmission, in particular the SMS, to the terminal 101 in the manner known per se to the person skilled in the art and received by means of the radio module 103 of the terminal 101.
  • the deletion message is then transferred to the identification module 104 of the terminal 101 and recognized in the identification module 104 as an OTA message. Due to this, the message is decrypted with the OTA key stored in the identification module 104.
  • the identification module 104 evaluates the content of the message, thereby recognizing the deletion command that is subsequently executed. For this purpose, the license information 105i to be discarded is determined on the basis of the description of the protected application 102i contained in the message.
  • the license information 105i is determined, which is stored in the identification module 104 for the application 102i specified in the deletion message. This license information 105i is then deleted in one embodiment. If the license information 105i is a set flag, it is removed. If the license information includes a code stored in the identification module 104, it is deleted. In another embodiment, the code remains stored in the identification module 104, but is marked as invalid. This allows, for example, the subsequent determination that a valid license information for the relevant protected application was stored in the identification module 104.
  • the deletion of the license information 105i or the tag as invalid may be confirmed to the license server 302 by an acknowledgment message automatically generated in the identification module 104.
  • the message can also be transmitted via the SMSC to the license server 302 by means of the SMS.
  • another message service can be used to transmit the confirmation message.
  • the A confirmation message can be encrypted by means of the OTA key of the identification module 104. In this case, the message is first communicated to the OTA server 303, which decrypts it with the OTA key associated with the identification module 104, and forwards the decrypted content to the license server 302.
  • the confirmation message can also be encrypted in another way or encryption can be dispensed with.
  • the protected application or its protected functions can no longer be executed in the terminal 101 or in the further device 201 in the future. If the application 102i sends a corresponding request to the control unit 106 to check for the presence of a license information 105i, it sends back an error message to the application 102i. As described above, then the protected application 102i is not executed or the access to the protected functions of the application 102i is not released.
  • a valid license information 105i can again be stored in the identification module 104 for the same application 102i, if so desired.
  • a corresponding installation message can be sent to the identification module 104. This can be done, for example, if the user again acquires a license for the use of the protected application 102i.
  • Another embodiment differs from the embodiments described above in that a deletion message is not sent to an identification module 104 because the license for the use of a protected application 102i is terminated, but because a license information 105i is to be deleted for other reasons.
  • An example for this purpose an exchange of the license information 105i stored in the identification module 104 with a first code by a new license information 105i with a second code. Such an exchange may be provided to increase security against unauthorized use of applications 102i.
  • an erase message initiated by the license server 302 may first be sent to the identification module 104, which results in discarding the license information 105i stored in the identification module 104 with the first code.
  • an installation message initiated by the license server 302 for installing a license information 105i with the second code may be sent to the identification module 104.
  • the installation message may be sent, for example, after the identification module 104 has confirmed the discarding of the old license information.
  • license information for the use of protected applications 102i can be stored in an identification module 104 and stored license information can be deleted. Further embodiments differ from this in that the license information for the use of protected content, in particular of multimedia contents, such as video and / or audio content stored in the terminal 101 or the further device 201, may be provided.
  • an application for the reproduction of the contents communicates with the control unit 106 of the identification module 104 and, when accessing protected contents, checks whether the necessary license information is available for the contents. This may be done in the same way as checking for the presence of license information by a protected application 102i.
  • the license information for the use of protected content in the terminal 101 or in the further device 201 can be stored in the same way in the identification module 104, in particular by means of an installation message, and discarded due to the receipt of a deletion message.
  • the messages are structured in the same way as the installation and installation described above Deletion message, but instead of a protected application 102i, the protected contents, in particular the relevant multimedia files, are specified in the messages.
  • the license information 105i need not be stored in an identification module 104, but may also be stored in another security module in the terminal, in particular in a security module, which is specially provided for the storage of license information. Such may be designed as a separate chip or as a software module, which is executed on a processor of the terminal.
  • security modules can be used in particular in terminals that do not have an identification module of the aforementioned type.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Software Systems (AREA)
  • Theoretical Computer Science (AREA)
  • Technology Law (AREA)
  • Computer Hardware Design (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Multimedia (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Telephone Function (AREA)

Claims (12)

  1. Procédé de commande de l'autorisation d'utilisation de contenus et/ou d'une application (102i), l'utilisation étant autorisée quand la présence d'une information de licence (105i) valide est constatée dans un module de sécurité (104) d'un terminal de communication (101), caractérisé en ce qu'une information de licence (105i) valide enregistrée dans le module de sécurité (104) est supprimée du module de sécurité (104) ou marquée comme non valide dans le module de sécurité (104) en raison de la réception d'un message de suppression,
    le message de suppression étant envoyé au terminal (101) quand un serveur de licences (302) constate qu'une licence de l'utilisateur du terminal (101) pour l'utilisation des contenus et/ou de l'application (102i) a expiré
    les contenus et/ou l'application (102i) étant utilisés dans le terminal de communication (101) ou dans un autre appareil (201) pouvant être relié au terminal de communication (101).
  2. Procédé selon la revendication 1, dans lequel le message de suppression comprend au moins une caractéristique d'authentification et dans lequel l'information de licence (105i) est rejetée en raison d'une vérification réussie de l'information d'authentification.
  3. Procédé selon l'une des revendications précédentes, dans lequel l'information de licence (105i) est envoyée au terminal de communication conjointement avec un message d'installation et est enregistrée dans le module de sécurité (104) en raison de la réception du message d'installation.
  4. Procédé selon la revendication 3, dans lequel le message d'installation comprend au moins une caractéristique d'authentification et dans lequel l'information de licence (105i) est enregistrée dans le module de sécurité (104) en raison d'une vérification réussie de la caractéristique d'authentification.
  5. Procédé selon la revendication 2 ou 4, dans lequel l'information d'authentification est générée avec une clé cryptographique d'un serveur fiable.
  6. Procédé selon l'une des revendications 2, 4 et 5, dans lequel l'information d'authentification est générée avec une clé associée au module de sécurité (104).
  7. Procédé selon l'une des revendications précédentes, dans lequel le message de suppression et/ou le message d'installation est un message Over The Air.
  8. Procédé selon l'une des revendications précédentes, dans lequel le module de sécurité (104) est un module d'identification relié au terminal (101) pour l'identification et/ou l'authentification dans le réseau de téléphonie mobile, qui est en particulier compris dans une carte à puce reliée au terminal (101).
  9. Programme informatique comprenant des parties de code logiciel avec des instructions pour l'exécution d'un procédé selon l'une des revendications précédentes, quand le programme est exécuté par un processeur.
  10. Terminal de communication (101) pour l'autorisation d'utilisation de contenus et/ou d'une application (102i), le terminal (101) comprenant un module de sécurité (104) et l'utilisation pouvant être autorisée quand la présence d'une information de licence (105i) valide est constatée dans le module de sécurité (104), caractérisé en ce que le module de sécurité (104) est conçu de telle manière qu'une information de licence (105i) valide enregistrée dans le module de sécurité (104) est supprimée du module de sécurité (104) ou marquée comme non valide dans le module de sécurité (104) en raison de la réception d'un message de suppression
    le message de suppression étant envoyé au terminal (101) quand un serveur de licences (302) constate qu'une licence de l'utilisateur du terminal (101) pour l'utilisation des contenus et/ou de l'application (102i) a expiré
    les contenus et/ou l'application (102i) étant utilisés dans le terminal de communication (101) ou dans un autre appareil (201) pouvant être relié au terminal de communication (101).
  11. Terminal de communication (101) selon la revendication 10, dans lequel le terminal de communication (101) est conçu pour reproduire les contenus et/ou exécuter l'application (102i).
  12. Système comprenant un terminal de communication (101) selon la revendication 10 et un autre appareil (201), dans lequel l'autre appareil (201) est conçu pour reproduire les contenus et/ou exécuter l'application (102i).
EP12187587.6A 2011-10-21 2012-10-08 Gestion des informations de licence pour un terminal de communication Active EP2611221B1 (fr)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
DE102011085050A DE102011085050A1 (de) 2011-10-21 2011-10-21 Verwaltung von Lizenzinformationen für ein Kommunikationsendgerät

Publications (2)

Publication Number Publication Date
EP2611221A1 EP2611221A1 (fr) 2013-07-03
EP2611221B1 true EP2611221B1 (fr) 2019-12-11

Family

ID=47257435

Family Applications (1)

Application Number Title Priority Date Filing Date
EP12187587.6A Active EP2611221B1 (fr) 2011-10-21 2012-10-08 Gestion des informations de licence pour un terminal de communication

Country Status (2)

Country Link
EP (1) EP2611221B1 (fr)
DE (1) DE102011085050A1 (fr)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113196262B (zh) * 2018-12-22 2025-09-26 华为技术有限公司 一种真伪查询方法及其终端设备

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2387505B (en) 2002-04-12 2005-11-23 Vodafone Plc Communication systems
US20040205151A1 (en) * 2002-12-19 2004-10-14 Sprigg Stephen A. Triggering event processing
EP1536606A1 (fr) * 2003-11-27 2005-06-01 Nagracard S.A. Méthode d'authentification d'applications
US7814023B1 (en) * 2005-09-08 2010-10-12 Avaya Inc. Secure download manager
US20070130079A1 (en) * 2005-11-23 2007-06-07 Microsoft Corporation Enforcing subscription validity
US20070180231A1 (en) * 2006-01-31 2007-08-02 Widevine Technologies, Inc. Preventing entitlement management message (EMM) filter attacks
WO2008048433A1 (fr) * 2006-10-06 2008-04-24 Best Buy Enterprise Services, Inc. Lecteur multimédia avec avertissement d'expiration de licence
US20110196793A1 (en) * 2010-02-05 2011-08-11 General Instrument Corporation Generic feature licensing framework

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
None *

Also Published As

Publication number Publication date
DE102011085050A1 (de) 2013-04-25
EP2611221A1 (fr) 2013-07-03

Similar Documents

Publication Publication Date Title
EP2777309B1 (fr) Procédé et système permettant la validation d'un dispositif technique
EP3939344B1 (fr) Procédé de mise à disposition de profils de souscription, module d'identité de participant et serveur de souscription
EP2898714B1 (fr) Module d'identite pour l'authentification d'un utilisateur dans un reseau de communication
EP2528362B1 (fr) Changement de données de souscription dans un module d'identification
EP2910039B1 (fr) Procédé pour introduire des données d'identité d'abonné dans un module d'identités d'abonné
WO2012130460A1 (fr) Procédé d'actualisation d'un support de données
EP2779722B1 (fr) Procédé de personnalisation d'un module de sécurité d'un terminal de télécommunication
EP2692157A2 (fr) Actualisation d'une application de support de données
EP2528363B1 (fr) Changement de souscription dans un module d'identification
DE102011075257B4 (de) Beantwortung von Anfragen mittels des Kommunikationsendgeräts eines Nutzers
WO2005024543A2 (fr) Procede et dispositif pour etablir des liaisons entre des terminaux de communication et des reseaux de donnees et/ou de communication presentant des trajets de transmission sans fil, reseaux locaux sans fil et/ou reseaux telephoniques mobiles par exemple, ainsi que programme informatique correspondant
EP2697989B1 (fr) Procédé et système pour la transmission de données à un module d'identification d'un téléphone mobile
EP2677791B1 (fr) Procédé et dispositif de détermination d'une demande de contrôle à un module d'identification
EP2611221B1 (fr) Gestion des informations de licence pour un terminal de communication
DE102013001733A1 (de) Verfahren zum Zugriff auf einen Dienst eines Servers über eine Applikation eines Endgeräts
EP2434719B1 (fr) Procédé et serveur destinés à la préparation de données utilisateur
EP2613491B1 (fr) Exécution d'opérations cryptographiques avec les données d'un poste terminal d'utilisateur
EP2116075B1 (fr) Module de sécurité
EP2933769B1 (fr) Procédé de transaction
DE10308932B4 (de) Verfahren zum Signalisieren von Steueranweisungen an ein Telekommunikationsgerät
WO2006079579A1 (fr) Systeme et procede pour delivrer une licence de fonctionnalites dans des terminaux de communications
EP4138435A1 (fr) Procédé d'octroi d'un droit d'accès à une unité de commande dans un système de commande de bâtiment
DE102007058213A1 (de) Verfahren und System zur geschützten Übertragung von Mediendaten in einem Netzwerk

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

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

AX Request for extension of the european patent

Extension state: BA ME

RIN1 Information on inventor provided before grant (corrected)

Inventor name: NOZULAK, THORSTEN

Inventor name: SEIFERT, ULRICH

17P Request for examination filed

Effective date: 20131223

RBV Designated contracting states (corrected)

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: EXAMINATION IS IN PROGRESS

17Q First examination report despatched

Effective date: 20170914

REG Reference to a national code

Ref country code: DE

Ref legal event code: R079

Ref document number: 502012015598

Country of ref document: DE

Free format text: PREVIOUS MAIN CLASS: H04W0004000000

Ipc: H04W0004200000

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: GRANT OF PATENT IS INTENDED

RIC1 Information provided on ipc code assigned before grant

Ipc: H04W 4/20 20180101AFI20190521BHEP

Ipc: H04W 4/60 20180101ALI20190521BHEP

Ipc: G06F 21/12 20130101ALI20190521BHEP

Ipc: H04W 12/08 20090101ALI20190521BHEP

INTG Intention to grant announced

Effective date: 20190606

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE PATENT HAS BEEN GRANTED

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): AL AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HR HU IE IS IT LI LT LU LV MC MK MT NL NO PL PT RO RS SE SI SK SM TR

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

Free format text: NOT ENGLISH

REG Reference to a national code

Ref country code: CH

Ref legal event code: EP

REG Reference to a national code

Ref country code: AT

Ref legal event code: REF

Ref document number: 1213399

Country of ref document: AT

Kind code of ref document: T

Effective date: 20191215

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 502012015598

Country of ref document: DE

REG Reference to a national code

Ref country code: IE

Ref legal event code: FG4D

Free format text: LANGUAGE OF EP DOCUMENT: GERMAN

REG Reference to a national code

Ref country code: NL

Ref legal event code: MP

Effective date: 20191211

REG Reference to a national code

Ref country code: LT

Ref legal event code: MG4D

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

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: 20200311

Ref country code: NO

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: 20200311

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: 20200312

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: 20191211

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: 20191211

Ref country code: LV

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: 20191211

Ref country code: LT

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: 20191211

Ref country code: ES

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: 20191211

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: HR

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: 20191211

Ref country code: RS

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: 20191211

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: AL

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: 20191211

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: 20191211

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: 20191211

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: 20191211

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: 20191211

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: 20200506

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IS

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: 20200411

Ref country code: SM

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: 20191211

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: 20191211

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 502012015598

Country of ref document: DE

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

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: 20191211

26N No opposition filed

Effective date: 20200914

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

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: 20191211

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: 20191211

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: 20191211

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: MC

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: 20191211

Ref country code: LU

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20201008

REG Reference to a national code

Ref country code: BE

Ref legal event code: MM

Effective date: 20201031

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: CH

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20201031

Ref country code: BE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20201031

Ref country code: LI

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20201031

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: IE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20201008

REG Reference to a national code

Ref country code: AT

Ref legal event code: MM01

Ref document number: 1213399

Country of ref document: AT

Kind code of ref document: T

Effective date: 20201008

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 NON-PAYMENT OF DUE FEES

Effective date: 20201008

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: 20191211

Ref country code: MT

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: 20191211

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: 20191211

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: MK

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: 20191211

P01 Opt-out of the competence of the unified patent court (upc) registered

Effective date: 20230519

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: DE

Payment date: 20251021

Year of fee payment: 14

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: GB

Payment date: 20251022

Year of fee payment: 14

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: FR

Payment date: 20251030

Year of fee payment: 14