Encryption in a wireless telecommunications
14 claims: 6 independent, 8 dependent
- 1A method of transmitting encrypted user data (40) to a mobile terminal (28) in a wireless telecommunications network (14), the method comprising sending to the mobile terminal a data packet (32,48), the data packet comprising both an identifier (38,50) of encryption information to be used in recovering encrypted user data, and user data (40,52) encrypted using said encryption information, wherein in response to receipt of the data packet the mobile terminal initialises (70) its security context using the identified encryption information, and the network comprises a UMTS or LTE network.
- 10A UMTS or LTE wireless telecommunications base station (20,64) configured to transmit encrypted user data in a data packet (32,48), the data packet comprising both an identifier (38,50) of new encryption information, said new encryption information being adapted to be used in a receiver to recover encrypted user data, and user data (40,52) encrypted using said new encryption information.
- 12A wireless telecommunications terminal (28) comprising a receiver and a processor, the receiver being configured to receive a data packet (32,48), the data packet comprising both an identifier (38,50) of encryption information to be used in recovering encrypted user data, and user data (40,52) encrypted using said encryption information, wherein in response to receipt of the data packet the mobile terminal (28) initialises its security context using the identified encryption information, and the processor is configured to use said encryption information to recover the user data encrypted using said encryption information, the mobile terminal being configured to store said encryption information for subsequent use, and the terminal is a UMTS or LTE wireless telecommunications terminal
- 14A method of a mobile terminal (28) in a wireless telecommunications network receiving encrypted user data, the method comprising:the mobile terminal receiving a first data packet, the first data packet comprising user data encrypted using first encryption information;recovering the user data in the mobile terminal using first encryption information stored in the mobile terminal;the mobile terminal receiving a next data packet (32,48), the data packet comprising both an identifier (38,50) of updated encryption information to be used in recovering encrypted user data, and user data (40,52) encrypted using said updated encryption information, wherein in response to receipt of said next data packet the mobile terminal initialises its security context using the identified updated encryption information;the mobile terminal using said encryption information to recover the user data encrypted using said updated encryption information and storing said updated encryption information for subsequent use in decrypting subsequent packets.
Independent claims6
49 paragraphs, as filed
<u>Field of the Invention</u>
0001The present invention relates to telecommunications, in particular to wireless telecommunications.
<u>Description of the Related Art</u>
0002In known Universal Mobile Telecommunications System (UMTS) systems, some messages are encrypted. Encryption is initiated by a security mode command being sent from the core network via the UMTS terrestrial radio access network (UTRAN) to be received by the mobile terminal. This is followed by a security mode response being sent from the mobile terminal and received by the core network.
0003For example, as shown in <figref idref="f0001">Figure 1</figref>, upon receiving a session, or bearer, establishment request 1, the core network(CN) 2 sends a security mode command 4 to the UTRAN 6. This causes the UTRAN 6 to forward the security mode command 4 to the mobile terminal (User Equipment, UE 8). The mobile terminal 8 reacts by initialising its encryption algorithms using specific parameter values, sometimes referred to as a security context, and then acknowledges by sending a security mode response 10 to the UTRAN 6 which passes the response 10 on to the core network 2. Thereafter an encrypted Non Access Stratum (NAS) message, such as a session establishment response 12 is sent from the core network 2 to the mobile terminal 8 via the UTRAN 6.
0004In this known approach, the security mode messages are unencrypted since they provide the encryption information needed to encrypt the messages that follow.
0005Third Generation Partnership Project Technical Specification 3GPP TS 25.331 provides some background on UMTS networks.
0006Another area of background is Long Term Evolution, LTE, networks. From UMTS networks, so-called Long Term Evolution, LTE, networks are now being developed. For background on Long Term Evolution networks, the reader is referred to Third Generation Partnership Project Technical Specification 3GPP TS23.882.
0007It is known from United States Patent Publication <patcit id="pcit0001" dnum="US2004024012A"><text>US-A-2004/024012</text></patcit> to provide a method of transmitting encrypted user data to a mobile terminal in a wireless telecommunications network, the method comprising sending to the mobile terminal a data packet, the data packet comprising both an identifier of encryption information to be used in recovering encrypted user data, and user data encrypted using said encryption information.
<u>Summary of the Invention</u>
0008The reader is referred to the appended independent claims. Some preferred features are laid out in the dependent claims.
0009The inventors realised that in the known approach security mode command and response signalling causes delay in session establishment procedures. For example, when the mobile terminal moves to the coverage area of another base station, there can be a change in the encryption key used. This requires security mode command and response signalling so as to inform the mobile terminal of the new key before data encrypted using the new key is sent. This additional signalling can give rise to additional delay. Such a delay may be irksome to the subscriber, and can cause problems with applications that are call setup delay sensitive, such as Push-to-talk.
0010In some embodiments of the invention such delays may be reduced.
<u>Brief Description of the Drawings</u>
0011Embodiments of the present invention will now be described by way of example and with reference to the drawings, in which: <ul id="ul0001" list-style="none" compact="compact"><li><figref idref="f0001">Figure 1</figref> is a diagram illustrating the known approach to instigating encryption as part of session establishment (PRIOR ART),</li><li><figref idref="f0002">Figure 2</figref> is a diagram illustrating a Long Term Evolution, LTE, network according to a first embodiment of the present invention,</li><li><figref idref="f0003">Figure 3</figref> is a diagram illustrating an approach to instigating encryption as part of session establishment in the network shown in <figref idref="f0002">Figure 2</figref>,</li><li><figref idref="f0003">Figure 4</figref> is a diagram illustrating the structure of a NAS message sent in session establishment,</li><li><figref idref="f0004">Figure 5</figref> is a diagram illustrating how NAS signalling messages are encrypted,</li><li><figref idref="f0004">Figure 6</figref> is a diagram illustrating handover between core network CN nodes in the LTE network,</li><li><figref idref="f0005">Figure 7</figref> is a diagram illustrating instigating encryption as part of Radio resource control, RRC, connection establishment in the LTE network,</li><li><figref idref="f0005">Figure 8</figref> is a diagram illustrating a Universal Mobile Telecommunications System (UMTS) network according to a second embodiment of the present invention, and</li><li><figref idref="f0006">Figure 9</figref> is a diagram illustrating an approach to instigating encryption as part of session establishment in the network shown in <figref idref="f0005">Figure 8</figref>.</li></ul>
<u>Detailed Description</u>
0012An example LTE network will first be described, followed by explanations of how encryption is initiated in session establishment using a combined message. This is followed by an explanation of how encryption is handled upon handover of a mobile terminal from connection with one core network node to another.
0013An alternative combined message is then described.
0014An alternative network is then described, that being a UMTS network, followed by an explanation of how encryption is initiated in that network.
Long Term Evolution Network
0015The LTE network 14, which is based on a Universal Mobile Telecommunications System (UMTS) network, is basically as shown in <figref idref="f0002">Figure 2</figref>. The core network includes Mobile Management Entities (MME). Each MME 16 includes a NAS message encryption stage 26. In <figref idref="f0002">Figure 2</figref>, only one Mobile Management Entity (MME) 16 of the core network 18 and one base station 20 of the LTE network 14 are shown for simplicity. The LTE network includes multiple base stations. In the Figure, the base station is also designated "eNode B" in accordance with LTE terminology. A cell, also referred to as a sector, is the radio-coverage area served by a corresponding antenna of a base station. Each base station 20 typically has three cells 22, each covered by one of three directional antennas 24 angled at 120 degrees to each other in azimuth.
0016In use, a mobile user terminal 28 (often referred to as User Equipment (UE) in LTE/UMTS terminology) communicates with a mobile management entity 16 via at least one cell 22 of at least one base station 20. In that way, the mobile user terminal communicates with the UTRAN network 2.
Instigating encryption in session establishment
0017The inventors realised that it is possible to combine the Security mode command and Non Access Stratum (NAS) message (such as a session establishment response) into a single combined message. The first part of the message is the security mode command and this part is unencrypted. The second part of the message is a NAS message and this part is encrypted.
0018As shown in <figref idref="f0003">Figure 3</figref>, upon receiving a session establishment request 30, the mobile management entity 16 sends the combined message 32 consisting of the unencrypted security mode command and encrypted NAS signalling message to the base station 20. This causes the base station 20 to forward the combined message 32 to the mobile terminal (User Equipment, UE 28). The mobile terminal 28 effects initialisation of its security context and then acknowledges by sending a security mode response 34 to the base station 20 from where the response 34 is forwarded on to the mobile management entity 16. Thereafter an encrypted Non Access Stratum (NAS) message, such as a session establishment response 36 is sent from the MME 16 to the mobile terminal 28 via the base station 20.
0019The combined message 32 referred to above is as shown in <figref idref="f0003">Figure 4</figref>, and consists of an unencrypted security command 38 and an encrypted NAS message 40. The security command 38 consists of information elements defining security context information such as an identifier of the encryption key to be used, and for example, an identifier of start time for the encryption. The NAS message 40 consists of information elements constituting a Session Establishment response.
Production of the combined message
0020In the LTE network 14 encryption of NAS messages is performed by encryption stages 26 in the respective nodes of the core network 18. Encryption of NAS messages is independent of, encryption of user data.
0021As shown in <figref idref="f0004">Figure 5</figref>, the NAS message for encryption together with information to effect the encryption such as encryption keys are input to the encryption stage 26 from which the encrypted NAS message 40 is provided The encrypted NAS message 40 is concatenated with unencrypted header information 38. This is possible because the MME 16 generally allows encryption of at least part of an NAS message before concatenation with another unencrypted message portion.
Handling encryption upon handover
0022Handover is the process of transferring the mobile terminal 28 from connection with one base station 20 and hence core network node 18 to another base station (not shown) and hence another core network node (not shown). Handover is sometimes known as handoff.
0023An example of handover procedure is shown in <figref idref="f0004">Figure 6</figref>. Initially the connection is to the base station 20 and involves using a first encryption key. The core network node 18 sends a handover command 42 via the base station 20 to the mobile terminal 28, after which handover 44 of the call connection to a further base station 20' and hence core network node 20' is effected. A "handover complete" message 46 is then sent from the mobile terminal 28 to the new base station 18' and hence core network node 18'. Thereafter the core network node sends a combined message 48, consisting of an unencrypted security mode command 50 including encryption key identifiers as previously discussed, followed by an encrypted portion 52 of user data such as NAS signalling messages. So, for example, when the core network node doing encryption changes, the first combined message 50 from the new core network node 18' indicates in the security mode command the new security parameter values to be used, and includes in encrypted form, new NAS signalling messages.
0024In an otherwise similar embodiment, if encryption and encryption configuration is instead done in the user plane, the combined packet in the user plane consists of the unencrypted security mode command concatenated with user data.
0025Of course, in some embodiments, switching to a new encryption key, by sending a combined message consisting of an unencrypted security mode command including encryption key identifiers followed by an encrypted portion of user data encrypted using that encryption key, can be done at other times than handover between cells. For example, in another embodiment, the old cell and new cell can be the same cell.
0026In this example, initially the cell communicates with the mobile terminal using the old encryption parameters. Part-way through the session the cell sends a packet containing the new encryption parameters and additional user data. The mobile terminal receives the new encryption parameters. The mobile terminal uses the new encryption parameters to decrypt the encrypted part of the packet. The mobile terminal also stores the new encryption parameters for subsequent use in decryption of subsequent packets that are encrypted using the new encryption parameters.
Radio Resource Control
0027As shown in <figref idref="f0005">Figure 7</figref>, a combined message can similarly be sent consisting of an unencrypted security mode command and an encrypted user data portion, where the user data portion consists of a Radio Resource Control (RRC) message. As shown in <figref idref="f0005">Figure 7</figref>, a RRC Connection Request 54 is sent to a base station 20" and the combined message 56, which more specifically comprises the unencrypted Security Mode command followed by the encrypted (with the new key) RRC Connection Response, is sent by the base station to the mobile terminal 28' in reply. A security mode response is then sent from the user terminal 28'.
Another example system: UMTS
0028The network is a Universal Mobile Telecommunications System (UMTS) terrestrial access network (UTRAN), which is a type of wideband code division multiple access (CDMA) network for mobile telecommunications. The UTRAN network is basically as shown in <figref idref="f0005">Figure 8</figref>. Only one radio network controller and two base stations of the UTRAN network 62 are shown for simplicity. As shown in this Figure, the UTRAN network 62 includes base stations 64. In the Figure, each of the base stations 64 is also designated "Node B" in accordance with UMTS terminology. A cell, also referred to as a sector, is the radio-coverage area served by a corresponding antenna of a base station. Each base station typically has three cells 66, each covered by one of three directional antennas 67 angled at 120 degrees to each other in azimuth. Each radio network controller (RNC) 68 typically controls several base stations 64 and hence a number of cells 66. A base station 64 is connected to its controlling radio network controller (RNC) 68 via a respective interface 69 known as an IuB interface. In use, a mobile user terminal 70 (often referred to as User Equipment (UE) in UMTS terminology) communicates with a serving radio network controller (RCN) 68 via at least one cell 66 of at least one base station 64. In that way, the mobile user terminal communicates with the UTRAN network 62.
0029The RNC is connected to a Serving Gateway Support Node, SGSN, 72 of the core network 74. The SGSN 72 includes a NAS message encryption stage 76 as described in more detail below.
Instigating encryption in session establishment: UMTS Example
0030The inventors realised that it is possible to combine the Security mode command and Non Access. Stratum (NAS) message (such as a session establishment response) into a single combined message. The first part of the message is the security mode command and this part is unencrypted. The second part of the message is a NAS message and this part is encrypted.
0031As shown in <figref idref="f0006">Figure 9</figref>, upon receiving a session establishment request 78, the SGSN 72 sends the combined message 80 consisting of the unencrypted security mode command and encrypted NAS signalling message to the RNC 68 and hence base station 64. This causes the base station 64 to forward the combined message 80 to the mobile terminal (User Equipment, UE 70).
0032The combined message 80 consists of an unencrypted security command and an encrypted NAS message. The security commend consists of information elements defining security context information such as an identifier of the encryption key to be used, and for example, an identifier of start time for the encryption. The encrypted NAS message portion of message 80 consists of information elements constituting a Session Establishment response.
0033The mobile terminal 70 effects initialisation of its security context and then acknowledges by sending a security mode response 82 to the base station 64 and hence RNC 68 from where the response 82 is forwarded on to the SGSN 72.
General
0034The present invention may be embodied in other specific forms without departing from its essential characteristics. The described embodiments are to be considered in all respects only as illustrative and not restrictive. The scope of the invention is, therefore, indicated by the appended claims rather than by the foregoing description. All changes that come within the meaning and range of equivalence of the claims are to be embraced within their scope.
Some Abbreviations
0035<ul id="ul0002" list-style="none" compact="compact"><li>CN: Core Network</li><li>UMTS: Universal Mobile Telecommunications System</li><li>UE: User equipment</li><li>NAS: Non Access Stratum (also known as the Core network protocol)</li><li>MME: Mobility Management Entity</li><li>LTE: Long Term Evolution, a term used in 3GPP for system that is being standardised after UMTS</li><li>IE: Information Element</li><li>RRC: Radio Resource Control (The Radio part of the control protocol otherwise called Access Stratum part of the control protocol).</li><li>SGSN: Signalling Gateway Support Node.</li></ul>
6 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| US2004240412A1 | Cites | United States of America | – |
| "3rd Generation Partnership Project; Technical Specification Group Radio Access Network; Evolved Universal Terrestrial Radio Access (E-UTRA) and Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Radio interface protocol aspects (Release 7) V7.1.0" 3RD GENERATION PARTNERSHIP PROJECT (3GPP); TECHNICAL REPORT (TR), XX, XX, vol. TR 25.813 V7.1.0, September 2006 (2006-09), pages 1-41, XP003012351 | Non-patent | – | – |
| "Universal Mobile Telecommunications System (UMTS); Radio Resource Control (RRC); Protocol specification (3GPP TS 25.331 version 7.2.0 Release 7); ETSI TS 125 331", IEEE, LIS, SOPHIA ANTIPOLIS CEDEX, FRANCE, vol. 3-R2, no. V7.2.0, 1 September 2006 (2006-09-01), XP014035587, ISSN: 0000-0001 | Non-patent | – | – |
| "Universal Mobile Telecommunications System (UMTS); Radio Resource Control (RRC); Protocol specification (3GPP TS 25.331 version 7.2.0 Release 7); ETSI TS 125 331", IEEE, LIS, SOPHIA ANTIPOLIS CEDEX, FRANCE, vol. 3-R2, no. V7.2.0, 1 September 2006 (2006-09-01), XP014035587, ISSN: 0000-0001 | Non-patent | – | Examiner |
34 members in 14 offices
Priority claims3
| Document | Office | Kind | Date |
|---|---|---|---|
| 0619499 | United Kingdom | – | |
| 0619499 | United Kingdom | A | |
| 2007006995 | European Patent Office (EPO) | W |
Members34
| Document | Office | Kind | |
|---|---|---|---|
| GB0619499D0 | United Kingdom | D0 | |
| AU2007304555A1 | Australia | A1 | |
| WO2008040412A1 | World Intellectual Property Organization (WIPO) | A1 | |
| TW200830817A | Taiwan Province of China | A | |
| MX2009003314A | Mexico | A | |
| EP2070290A1 | European Patent Office (EPO) | A1 | |
| KR20090063274A | Republic of Korea | A | |
| CN101518032A | China | A | |
| IL197829A0 | Israel | A0 | |
| JP2010506469A | Japan | A | |
| US2010067697A1 | United States of America | A1 | |
| RU2009116675A | Russian Federation | A | |
| AU2007304555B2 | Australia | B2 | |
| KR101078615B1 | Republic of Korea | B1 | |
| RU2458476C2 | Russian Federation | C2 | |
| JP2013081252A | Japan | A | |
| US8494163B2 | United States of America | B2 | |
| US2013216042A1 | United States of America | A1 | |
| CN103327483A | China | A | |
| BRPI0717324A2 | Brazil | A2 | |
| TWI442743B | Taiwan Province of China | B | |
| IL197829A | Israel | A | |
| CN101518032B | China | B | |
| CN104394527A | China | A | |
| US9107066B2 | United States of America | B2 | |
| US2015237501A1 | United States of America | A1 | |
| JP2016021746A | Japan | A | |
| EP2070290B1This record | European Patent Office (EPO) | B1 | |
| ES2581354T3 | Spain | T3 | |
| JP6016643B2 | Japan | B2 | |
| US9503901B2 | United States of America | B2 | |
| CN103327483B | China | B | |
| CN104394527B | China | B | |
| BRPI0717324B1 | Brazil | B1 |
81 legal events, as 10 offices reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | Office | |
|---|---|---|---|
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Opt-out of the competence of the unified patent court (upc) registeredP01 | P01 | EP | |
| Amendments to the register in respect of changes of name or changes affecting rights (sect. 32/1977)REGISTERED BETWEEN 20200402 AND 20200408732E | 732E | GB | |
| Change of applicant/patenteeR081 | R081 | DE | |
| Change of representativeR082 | R082 | DE | |
| Change of representativeR082 | R082 | DE | |
| Fee paymentPLFP | PLFP | FR | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Fee paymentPLFP | PLFP | FR | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Patent lapsedLapsedMM4A | MM4A | IE | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Patent ceasedCeasedPL | PL | CH | |
| No opposition filedOpposition26N | 26N | EP | |
| No opposition filed within time limitOppositionORIGINAL CODE: 0009261PLBE | PLBE | EP | |
| Information on the status of an ep patent application or granted ep patentGrantedSTATUS: NO OPPOSITION FILED WITHIN TIME LIMITSTAA | STAA | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| No opposition filed against granted patent, or epo opposition proceedings concluded without decisionGrantedR097 | R097 | DE | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Patent invalid in the netherlands as no translation has been filedMP | MP | NL | |
| Deletion acc. to par. 5 (withdrawal of the translation of the ep patent)MK05 | MK05 | AT | |
| Definitive protectionFG2A | FG2A | ES | |
| Fee paymentPLFP | PLFP | FR | |
| Invalidated european patentMG4D | MG4D | LT | |
| Dpma publication of mentioned ep patent grantGrantedR096 | R096 | DE | |
| European patents granted designating irelandGrantedFG4D | FG4D | IE | |
| European patent takes effect as a national patent in ch/liEP | EP | CH | |
| Reference to at number (ep patent validated in austria)REF | REF | AT | |
| Designated contracting statesAK | AK | EP | |
| European patent grantedGrantedFG4D | FG4D | GB | |
| (expected) grantORIGINAL CODE: 0009210GRAA | GRAA | EP | |
| Grant fee paidORIGINAL CODE: EPIDOSNIGR3GRAS | GRAS | EP | |
| Intention to grant announcedINTG | INTG | EP | |
| Despatch of communication of intention to grant a patentORIGINAL CODE: EPIDOSNIGR1GRAP | GRAP | EP | |
| Intention to grant announcedINTG | INTG | EP | |
| Despatch of communication of intention to grant a patentORIGINAL CODE: EPIDOSNIGR1GRAP | GRAP | EP | |
| Intention to grant announcedINTG | INTG | EP | |
| Information provided on ipc code assigned before grantRIC1 | RIC1 | EP | |
| Information provided on ipc code assigned before grantRIC1 | RIC1 | EP | |
| Information provided on ipc code assigned before grantRIC1 | RIC1 | EP | |
| Despatch of communication of intention to grant a patentORIGINAL CODE: EPIDOSNIGR1GRAP | GRAP | EP | |
| Amendment of ipc main classPREVIOUS MAIN CLASS: H04L0029060000R079 | R079 | DE | |
| Party data changed (applicant data changed or rights of an application transferred)RAP1 | RAP1 | EP | |
| Information provided on other rights and legal means of execution (deleted)D11X | D11X | EP | |
| Information provided on other rights and legal means of executionAT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LI LT LU LV MC MT NL PL PT RO SE SI SK TR111Z | 111Z | EP | |
| Party data changed (applicant data changed or rights of an application transferred)RAP1 | RAP1 | EP | |
| Request for extension of the european patent (deleted)DAX | DAX | EP | |
| First examination report despatched17Q | 17Q | EP | |
| Party data changed (applicant data changed or rights of an application transferred)RAP3 | RAP3 | EP | |
| Request for examination filed17P | 17P | EP | |
| Designated contracting statesAK | AK | EP | |
| Request for extension of the european patentAX | AX | EP | |
| Public reference made under article 153(3) epc to a published international application that has entered the european phaseORIGINAL CODE: 0009012PUAI | PUAI | EP |
Numbers
- Publication
- 2070290
- Application
- 78015468
Titles3
- German
- Verschlüsselung bei einer drahtlosen Telekommunikation
- English
- Encryption in a wireless telecommunications
- French
- Cryptage dans une télécommunication sans fil
Classification
- CPC, 9
- H04L63/0428
- H04W12/02
- H04W12/08
- H04L63/068
- H04W12/04
- H04W12/033
- H04L9/065
- H04L63/0407
- H04L63/0442
- IPC, 3
- H04W12 02
- H04W12 04
- H04L29 06
Designated states32
- Contracting states, 32
- Austria
- Belgium
- Bulgaria
- Switzerland
- Cyprus
- Czechia
- Germany
- Denmark
- Estonia
- Spain
- Finland
- France
- United Kingdom
- Greece
- Hungary
- Ireland
- Iceland
- Italy
- Liechtenstein
- Lithuania
- Luxembourg
- Latvia
- Monaco
- Malta
and 8 moreShow fewer
- Netherlands (Kingdom of the)
- Poland
- Portugal
- Romania
- Sweden
- Slovenia
- Slovakia
- Türkiye
