Abstract:
A method and apparatus for intersystem mobility security context handling between different radio access networks which can include a receiver configured to receive a tracking area update message from a user terminal. The message can include a first key identifier configured to identify a mapped security context and a second key identifier configured to identify a cached security context. A verifier can be configured to verify the tracking area update message with a key identified by the first or second key identifier.

Description:
BACKGROUND OF THE INVENTION  
       [0001]    1. Field of the Invention 
         [0002]    The invention generally relates to mobile communication networks. Particularly, the invention relates to intersystem mobility security context handling between different radio access networks. 
         [0003]    2. Description of the Related Art 
         [0004]    There exist a variety of different data communication systems or networks. Each network has its own characteristics and specifications. When there exists several different networks, there is always a problem of how to interconnect these networks, i.e. how to execute a switchover or handover of a connection from one network to another. 
         [0005]    GSM EDGE Radio Access Network (GERAN) is the radio part of GSM/EDGE together with the network that joins the base stations The network represents the core of a GSM network, through which phone calls and packet data are routed from and to the PSTN and Internet to and from subscriber handsets. 
         [0006]    UMTS Terrestrial Radio Access Network (UTRAN) is a collective term for the Node B&#39;s and Radio Network Controllers which make up the UMTS radio access network. The UTRANs is able to carry many traffic types from real-time Circuit Switched to IP based Packet Switched. The UTRAN contains base stations, which are called Node Bs, and Radio Network Controllers (RNC). The RNC provides control functionalities for one or more Node Bs. 
         [0007]    Evolved UTRAN (E-UTRAN) is an evolution of the 3G UMTS radio access network towards a high-data-rate, low-latency and packet-optimized radio-access network. 
         [0008]    In E-UTRAN user equipment (UE) can have both a mapped and cached security context during mobility from GERAN/UTRAN to E-UTRAN. In the mapped security context EPS (Evolved Packet System) keys and other security parameters are converted from received context from UTRAN/GERAN. In the cached security context EPS keys and other security parameters are cached in the EPS and re-used when UE moves to the EPS system, e.g. from UTRAN/GERAN or WiMAX/WLAN/DSL. 
         [0009]    One of the problems in idle mode mobility or handover to/from E-UTRAN is that how does both user equipment and E-UTRAN negotiate key usage in the different cases when the user equipment has or does not have the cached security context or when E-UTRAN has or does not have the cached security context. 
       SUMMARY OF THE INVENTION  
       [0010]    According to a first aspect of the invention there is provided a method comprising: receiving a tracking area update message from a user terminal, the message comprising a first key identifier identifying a mapped security context and a second key identifier identifying a cached security context; and verifying the tracking area update message with a key identified by the first or second key identifier. 
         [0011]    In one embodiment of the invention, the tracking area update message comprises an indication identifying the key used to protect the tracking area update message and the tracking area update message is verified with the identified key. 
         [0012]    In one embodiment of the invention, in the verification step, verifying the tracking area update message with a key identified by the first key identifier; and activating the cached security context with a security mode command procedure. 
         [0013]    According to a second aspect of the invention there is provided a method comprising: sending to a user terminal a message comprising a first key identifier identifying a mapped security context and a second key identifier identifying a cached security context; and sending to an evolved UMTS terrestrial radio access network the mapped security context and the cached security context. 
         [0014]    According to a third aspect of the invention there is provided a method comprising: receiving a mapped security context and a cached security context from an evolved packet core entity; receiving a handover complete message from a user terminal, the message comprising a first key identifier identifying the mapped security context and a second key identifier identifying the cached security context and the message being protected by the security context identified by the first key identifier or the second key identifier; and verifying the handover complete message based on the key identified by the first or second key identifier. 
         [0015]    In one embodiment of the invention, the handover complete message further comprises an indication identifying the key used to protect the handover complete message, wherein the message is verified with the identified key. 
         [0016]    According to a fourth aspect of the invention there is provided a method comprising: including a first key identifier identifying a mapped security context and a second key identifier identifying a cached security context in a tracking area update message; protecting the tracking area update message by using a key associated with the first key identifier or the second key identifier; and sending the tracking area update message to an evolved packet core entity. 
         [0017]    In one embodiment of the invention, the method further comprises: including an indication identifying the key used to protect the tracking area update message in the tracking area update message. 
         [0018]    In one embodiment of the invention, the method further comprises: activating the cached security context with a security mode command procedure. 
         [0019]    According to a fifth aspect of the invention there is provided a method comprising: receiving a handover command message comprising a first key identifier identifying a mapped security context and a second key identifier identifying a cached security context; selecting a key identifier of a key in response to receiving the handover command message; including the selected key identifier in a handover complete message; protecting the handover complete message with the selected key; and sending the handover complete message to an evolved UMTS terrestrial radio access network. 
         [0020]    In one embodiment of the invention, when selecting the key identifier, selecting the key identifier identifying the mapped security context; and including in the handover command message also the second key identifier. 
         [0021]    In one embodiment of the invention, the handover complete message further comprises an indication identifying the key used to protect the handover complete message. 
         [0022]    In one embodiment of the invention, when selecting the key identifier, selecting the key identifier identifying the cached security context. 
         [0023]    According to a sixth aspect of the invention there is provided an apparatus comprising: a receiver configured to receive a tracking area update message from a user terminal, the message comprising a first key identifier identifying a mapped security context and a second key identifier identifying a cached security context; and a verifier configured to verify the tracking area update message with a key identified by the first or second key identifier. 
         [0024]    In one embodiment of the invention, the tracking area update message comprises an indication identifying the key used to protect the tracking area update message and the tracking area update message is verified with the identified key. 
         [0025]    In one embodiment of the invention, the verifier is configured to verify the tracking area update message with a key identified by the first key identifier; and an activator configured to activate the cached security context with a security mode command procedure. 
         [0026]    According to a seventh aspect of the invention there is provided an apparatus comprising: a first transmitter configured to send to a user terminal a handover message comprising a first key identifier identifying a mapped security context and a second key identifier identifying cached security context; and a second transmitter configred to send to an evolved UMTS terrestrial radio access network the mapped security context and the cached security context. 
         [0027]    According to a eight aspect of the invention there is provided apparatus comprising: a first receiver configured to receive a mapped security context and a cached security context from an evolved packet core entity; a second receiver configured to receive a handover complete message from a user terminal, the message comprising a first key identifier identifying the mapped security context and a second key identifier identifying the cached security context and the message being protected by the security context identified by the first key identifier or the second key identifier; and a verifier configured to verify the handover complete message based on the key identified by the first or second key identifier. 
         [0028]    In one embodiment of the invention, the handover complete message further comprises an indication identifying the key used to protect the handover complete message, wherein the message is verified with the identified key. 
         [0029]    According to a ninth aspect of the invention there is provided an apparatus comprising: a setting unit configured to include a first key identifier identifying a mapped security context and a second key identifier identifying a cached security context in a tracking area update message; a protector configured to protect the tracking area update message by using a key associated with the first key identifier or the second key identifier; and a transmitter configured to send the tracking area update message to an evolved packet core entity. 
         [0030]    In one embodiment of the invention, the setting unit is configured to include an indication identifying the key used to protect the tracking area update message in the tracking area update message. 
         [0031]    According to a tenth aspect of the invention there is provided an apparatus comprising: a receiver configured to receive a handover command message comprising a first key identifier identifying a mapped security context and a second key identifier identifying cached security context; a selection unit configured to select a key identifier of a key in response to receiving the handover command message; a setting unit configured to include the selected key identifier in a handover complete message; a protecting unit configured to protect the handover complete message with the selected key; and a transmitter configured to send the handover complete message to an evolved UMTS terrestrial radio access network. 
         [0032]    In one embodiment of the invention, the selection unit is configured to select the key identifier identifying the mapped security context and to include in the handover command message also the second key identifier. 
         [0033]    In one embodiment of the invention, the setting unit is configured to include in the handover complete message an indication identifying the key used to protect the handover complete message. 
         [0034]    In one embodiment of the invention, the selection unit is configured to select the key identifier identifying the cached security context. 
     
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS  
         [0035]    The accompanying drawings, which are included to provide a further understanding of the invention and constitute a part of this specification, illustrate embodiments of the invention and together with the description help to explain the principles of the invention. In the drawings: 
           [0036]      FIG. 1   a  is a sequence diagram illustrating one embodiment of the invention, 
           [0037]      FIG. 1   b  is a sequence diagram illustrating another embodiment of the invention, 
           [0038]      FIG. 2   a  is a sequence diagram illustrating another embodiment of the invention, and 
           [0039]      FIG. 2   b  is a sequence diagram illustrating another embodiment of the invention. 
       
    
    
     DETAILED DESCRIPTION OF THE EMBODIMENTS  
       [0040]    Reference will now be made in detail to the embodiments of the invention, examples of which are illustrated in the accompanying drawings. 
         [0041]      FIG. 1   a  discloses an embodiment of the invention in which user equipment (UE)  10  moves from UTRAN to E-UTRAN. E-UTRAN comprises one or more evolved node B&#39;s (eNB)  12  which are connected to a mobility management entity  14 . E-UTRAN and the mobility management entity are specified in more detail e.g. in specification 3GPP TS 36.300 V8.3.0 (2007-12). UTRAN and SGSN are discussed in more detail e.g. in specification 3GPP TS 25.401 V8.0.0 (2007-12). 
         [0042]    The user equipment  10  includes a key identifier (K ASME  Key Set Identifier, KSI ASME , in E-UTRAN) identifying a cached security context in a tracking area update (TAU) message ( 104 ). The user equipment  10  uses cached security context for deriving Non Access Stratum (NAS) keys and for integrity protecting a Tracking Area Update (TAU) request message during idle mode mobility from UTRAN to E-UTRAN. In one embodiment, the user equipment may have the cached security context available for a predetermined time period, and is thus able to directly use it instead of the mapped security context. 
         [0043]    In this embodiment, the mobility management entity  14  has also in its possession the cached security context. The included K ASME  in the TAU message identifies for the mobility management entity  14  which key to use for verifying the TAU message. Thus the mobility management node  14  able to verify ( 106 ) the message with the correct key. 
         [0044]    If, for some reason, the mobility management entity  14  did not have the cached context available any more, an Authentication and Key Agreement (AKA) procedure may be run to establish a new security context. 
         [0045]      FIG. 1   b  discloses an embodiment of the invention in which user equipment (UE)  10  moves from UTRAN to E-UTRAN. E-UTRAN comprises one or more evolved node B&#39;s (eNB)  12  which are connected to a mobility management entity  14 . E-UTRAN and the mobility management entity are specified in more detail e.g. in specification 3GPP TS 36.300 V8.3.0 (2007-12). UTRAN and SGSN are specified in more detail e.g. in specification 3GPP TS 25.401 V8.0.0 (2007-12). 
         [0046]    The user equipment has in its possession two security contexts (mapped and cached). In this embodiment, the user equipment  10  includes two key identifiers (KSI and KSI ASME ) in a tracking area update (TAU) message. KSI identifies the mapped security context and KSI ASME  identifies the cached security context. The user equipment then uses the mapped security context for deriving Non Access Stratum (NAS) keys and for integrity protecting a Tracking Area Update (TAU) request message during idle mode mobility from UTRAN to E-UTRAN. 
         [0047]    In one embodiment, the tracking area update message comprises TMSI (Temporary Mobile Subscriber Identity), RAI (Routing Area Identity) and KSI (Key Set Identifier) of the mapped security context. Since in this embodiment, the user equipment  10  has also a cached security context in its possession, the tracking area update message comprises also a GUTI/S-TMSI/M-TMSI (GUTI, Globally Unique Temporary Identity), TAI (Tracking Area Identity) and KSI ASME  of the cached security context. 
         [0048]    The user equipment  10  sends ( 114 ) the tracking area update message to the eNB  12 , which forwards it further to the mobility management entity  14 . The mobility management entity  14  selects a correct key based on the key identifier (KSI) and verifies ( 116 ) message. Although the user equipment protected the TAU message by using the mapped security context, the identifier (KSI ASME ) identifying the cached security context is still comprised in the TAU message. This indicates to the mobility management entity  14  that the user equipment has also the cached security context available and that it is able to use also that. The mobility management entity  14  may activate ( 118 ) the cached security context with Security Mode Command (SMC) procedure if needed. 
         [0049]    In one embodiment, the tracking area update message comprises an indication identifying the key used to protect the tracking area update message. Based on the indication, the mobility management entity  14  is able to use the correct key to verify the message. 
         [0050]      FIG. 2   a  discloses an embodiment of the invention in which user equipment (UE)  20  moves from UTRAN or GERAN to E-UTRAN in an active mode (handover). E-UTRAN comprises one or more evolved node B&#39;s (eNB)  26  which are connected to a mobility management entity  28 . E-UTRAN and the mobility management entity are discussed in more detail e.g. in specification 3GPP TS 36.300 V8.3.0 (2007-12). UTRAN and SGSN are discussed in more detail e.g. in specification 3GPP TS 25.401 V8.0.0 (2007-12). GERAN and SGSN are discussed in more detail e.g. in specification 3GPP TS 43.051 V7.0.0 (2007-12). 
         [0051]    The SGSN transfers UE&#39;s (GERAN/UTRAN and possibly also EPC/E-UTRAN) security capabilities to the mobility management entity  28  in a relocation request message ( 200 ). The mobility management entity  28  then selects the NAS security algorithms and includes the allowed UP/RRC algorithms as well as the RRC and UP keys, both mapped and cached security context based in the relocation request message ( 202 ) to the target eNB  26 . The eNB  26  selects the RRC and UP algorithms and indicates them in the relocation request acknowledgement message ( 204 ) to the mobility management entity  28 . The mobility management entity  28  includes the selected NAS, UP, and RRC algorithms in a relocation response message ( 206 ) along with a KSI/CKSN and KSI ASME  to an SGSN  24 . KSI/CKSN identifies a key for mapped security context and KSI ASME  identifies a key for cached security context. KSI is used in UTRAN and CKSN is used in GERAN network. 
         [0052]    Since the handover is an intersystem handover, a transparent container included in the relocation response message sent by the mobility management entity  28  includes also other radio resource configuration data so that the user equipment  20  is able to select correct parameters (e.g. link level identity, correct frequencies, etc.) and to be able to find the correct eNB. 
         [0053]    The SGSN  24  includes the parameters in a relocation command message ( 208 ) and a radio network controller (RNC)  22  in UTRAN indicates them to the user equipment  20  in a handover from UTRAN command ( 210 ). 
         [0054]    In response to the handover command message ( 210 ), the user equipment selects ( 212 ) a key to be used for protecting a handover complete message to be sent to the eNB. The user equipment  20  includes ( 214 ) a key identifier (KSI/CKSN or KSI ASME ) of the selected key in the handover complete message ( 218 ). In addition to the key identifier, the handover complete message may include an indication whether the key identifier identifies the mapped or cached security context. The indication is e.g. a 1-bit value for which the meanings of ‘0’ and ‘1’ have been previously determined. The key identifier identifies to the eNB whether the user equipment used the mapped security context or the cached security context to protect the handover complete message. Based on the key identifier the eNB uses the correct security context to verify ( 220 ) the handover complete message. 
         [0055]    In another embodiment, the user equipment may include in the handover complete message key identifiers identifying both the mapped and cached security context. At the same time the user equipment may also indicate to the eNB which one of the keys (KSI/CKSN or K ASME ) was used to protect the handover complete message. If mapped security context was used, the evolved packet system may activate cached security context with a Security Mode Command (SMC) procedure and avoid running Authentication and Key Agreement (AKA). 
         [0056]      FIG. 2   b  discloses an embodiment of the invention in which user equipment (UE)  20  moves from UTRAN or GERAN to E-UTRAN. E-UTRAN comprises one or more evolved node B&#39;s (eNB)  26  which are connected to a mobility management entity  28 . E-UTRAN and the mobility management entity are discussed in more detail e.g. in specification 3GPP TS 36.300 V8.3.0 (2007-12). GERAN and SGSN are discussed in more detail e.g. in specification 3GPP TS 43.051 V7.0.0 (2007-12). UTRAN and SGSN are discussed in more detail e.g. in specification 3GPP TS 25.401 V8.0.0 (2007-12). 
         [0057]      FIG. 2   b  discloses another embodiment of the invention in which user equipment (UE)  20  moves from GERAN/UTRAN to E-UTRAN in an active mode (handover). E-UTRAN comprises one or more evolved node B&#39;s (eNB)  26  which are connected to a mobility management entity  28 . E-UTRAN and the mobility management entity are discussed in more detail e.g. in specification 3GPP TS 36.300 V8.3.0 (2007-12). GERAN and SGSN are discussed in more detail e.g. in specification 3GPP TS 43.051 V7.0.0 (2007-12). UTRAN and SGSN are discussed in more detail e.g. in specification 3GPP TS 25.401 V8.0.0 (2007-12). 
         [0058]    The SGSN transfers UE&#39;s (GERAN/UTRAN and possibly also EPC/E-UTRAN) security capabilities to the mobility management entity  28  in a relocation request message ( 230 ). The mobility management entity  28  then selects the NAS security algorithms and includes the allowed UP/RRC algorithms as well as the RRC and UP keys, mapped or cached security context based in the relocation request message ( 232 ) to the target eNB  26 . The eNB  26  selects the RRC and UP algorithms and indicates them in the relocation request acknowledgement message ( 234 ) to the mobility management entity  28 . The mobility management entity  28  includes the selected NAS, UP, and RRC algorithms in a relocation response message ( 236 ) along with a KSI/CKSN or KSI ASME  to an SGSN  24 . KSI/CKSN identifies a key for mapped security context and KSI ASME  identifies a key for cached security context. KSI is used in UTRAN and CKSN is used in GERAN network. The SGSN  24  includes them in the relocation command ( 238 ) and a radio network controller (RNC)  22  indicates them to the user equipment  20  in a handover from UTRAN command ( 240 ). 
         [0059]    Since the handover is an intersystem handover, a transparent container included in the relocation response message sent by the mobility management entity  28  includes also other radio resource configuration data so that the user equipment  20  is able to select correct parameters (e.g. link level identity, correct frequencies, etc.) and to be able to find the correct eNB. 
         [0060]    In another embodiment, although the mobility management entity  28  might include in the relocation response message ( 236 ) only the cached security context to the user equipment  20 , the mobility management entity  28  may send both the mapped and cached security context to the eNB  26 . This may be useful in a case in which the user equipment  20  does not have the cached security context at all (although the mobility management entity  28  indicated only the cached security context to the user equipment  28 ). The user equipment would  28  then be forced to use the mapped security context, and the eNB  26  would also have it. 
         [0061]    In response to the handover command message, the user equipment selects ( 242 ) a key to be used for protecting a handover complete message to be sent to the eNB. As disclosed above, in one embodiment the mobility management entity  28  may send a key identifier that identifies only the cached security context. For some reason (expired cached security context timer etc.) the user equipment may not have any more the cached security context. Therefore, the only option is to choose the mapped security context. In another embodiment, the user equipment has the cached security context available and chooses to use that. 
         [0062]    In a further embodiment the handover command message ( 240 ) included only a key identifier identifying the mapped security context. The user equipment  20  has two options. The first option is to choose the mapped security context as instructed by the mobility management entity  28 . The second option is to choose the cached security context if it is abailable at the user equipment although the mobility management entity  28  instructed to use the mapped security context. 
         [0063]    The user equipment  20  includes ( 244 ) a key identifier (KSI, CKSN or K ASME ) of the selected key in a handover complete message ( 248 ). In one embodiment, when the user equipment  20  chooses the mapped security (KSI in UTRAN or CKSN in GERAN), the user equipment may also include a key identifier of the cached security context in the handover complete message. Then the evolved packet system can activate cached security context with a Security Mode Command (SMC) procedure and avoid running Authentication and Key Agreement (AKA). The user equipment  20 , however, protects the handover complete message by using the mapped security (KSI/CKSN). 
         [0064]    In one embodiment, in addition to the key identifier, the handover complete message may include an indication whether the key identifier identifies the mapped or cached security context. The indication is e.g. a 1-bit value for which the meanings of ‘0’ and ‘1’ have been previously determined. 
         [0065]    The key identifier and the indication identify to the eNB whether the user equipment used the mapped security context or the cached security context to protect the handover complete message. Based on the key identifier the eNB uses the correct security context to verify ( 250 ) the handover complete message. 
         [0066]    The exemplary embodiments can include, for example, any suitable mobile devices, mobile phones, smart phones, personal digital assistants, laptop computers, servers, and mobile communication devices, audio/video players capable of performing the processes of the exemplary embodiments. Furthermore, the exemplary embodiments can include, for example, wireless networks, mobile communication networks and various network elements of the corresponding network. The devices and subsystems of the exemplary embodiments can communicate with each other using any suitable protocol and can be implemented using one or more programmed computer systems or devices. 
         [0067]    It is to be understood that the exemplary embodiments are for exemplary purposes, as many variations of the specific hardware used to implement the exemplary embodiments are possible, as will be appreciated by those skilled in the hardware and/or software art(s). For example, the functionality of one or more of the components of the exemplary embodiments can be implemented via one or more hardware and/or software devices. Furthermore, the claimed methods may be implemented as a computer program. The units and other elements of the apparatuses may be implemented with any appropriate means including various hardware and/or software solutions. 
         [0068]    The exemplary embodiments can store information relating to various processes described herein. This information can be stored in one or more memories, such as a hard disk, optical disk, magneto-optical disk, RAM, and the like. One or more databases can store the information used to implement the exemplary embodiments of the present inventions. The databases can be organized using data structures (e.g., records, tables, arrays, fields, graphs, trees, lists, and the like) included in one or more memories or storage devices listed herein. The processes described with respect to the exemplary embodiments can include appropriate data structures for storing data collected and/or generated by the processes of the devices and subsystems of the exemplary embodiments in one or more databases. 
         [0069]    All or a portion of the exemplary embodiments can be conveniently implemented using one or more general purpose processors, microprocessors, digital signal processors, micro-controllers, and the like, programmed according to the teachings of the exemplary embodiments of the present inventions, as will be appreciated by those skilled in the computer and/or software art(s). Appropriate software can be readily prepared by programmers of ordinary skill based on the teachings of the exemplary embodiments, as will be appreciated by those skilled in the software art. In addition, the exemplary embodiments can be implemented by the preparation of application-specific integrated circuits or by interconnecting an appropriate network of conventional component circuits, as will be appreciated by those skilled in the electrical art(s). Thus, the exemplary embodiments are not limited to any specific combination of hardware and/or software. 
         [0070]    Stored on any one or on a combination of computer readable media, the exemplary embodiments of the present inventions can include software for controlling the components of the exemplary embodiments, for driving the components of the exemplary embodiments, for enabling the components of the exemplary embodiments to interact with a human user, and the like. Such software can include, but is not limited to, device drivers, firmware, operating systems, development tools, applications software, and the like. Such computer readable media further can include the computer program product of an embodiment of the present inventions for performing all or a portion (if processing is distributed) of the processing performed in implementing the inventions. Computer code devices of the exemplary embodiments of the present inventions can include any suitable interpretable or executable code mechanism, including but not limited to scripts, interpretable programs, dynamic link libraries (DLLs), Java classes and applets, complete executable programs, Common Object Request Broker Architecture (CORBA) objects, and the like. Moreover, parts of the processing of the exemplary embodiments of the present inventions can be distributed for better performance, reliability, cost, and the like. 
         [0071]    As stated above, the components of the exemplary embodiments can include computer readable medium or memories for holding instructions programmed according to the teachings of the present inventions and for holding data structures, tables, records, and/or other data described herein. Computer readable medium can include any suitable medium that participates in providing instructions to a processor for execution. Such a medium can take many forms, including but not limited to, non-volatile media, volatile media, transmission media, and the like. Non-volatile media can include, for example, optical or magnetic disks, magneto-optical disks, and the like. Volatile media can include dynamic memories, and the like. Transmission media can include coaxial cables, copper wire, fiber optics, and the like. Transmission media also can take the form of acoustic, optical, electromagnetic waves, and the like, such as those generated during radio frequency (RF) communications, infrared (IR) data communications, and the like. Common forms of computer-readable media can include, for example, a floppy disk, a flexible disk, hard disk, magnetic tape, any other suitable magnetic medium, a CD-ROM, CDR, CD-RW, DVD, DVD-ROM, DVD±RW, DVD±R, any other suitable optical medium, punch cards, paper tape, optical mark sheets, any other suitable physical medium with patterns of holes or other optically recognizable indicia, a RAM, a PROM, an EPROM, a FLASH-EPROM, any other suitable memory chip or cartridge, a carrier wave or any other suitable medium from which a computer can read. 
         [0072]    While the present inventions have been described in connection with a number of exemplary embodiments, and implementations, the present inventions are not so limited, but rather cover various modifications, and equivalent arrangements, which fall within the purview of prospective claims.