Patent Description:
A Universal Mobile Telecommunication System (UMTS) is a <NUM> wireless communication network standard defined by the Third Generation Partnership Project (3GPP). A UMTS network consists of a Core Network (CN) and an Access Network (AN). The CN consists of a Circuit Switched (CS) domain and a Packet Switched (PS) domain. The CS domain provides CS-based services such as voice services. The PS domain provides PS-based services such as Internet access. A terminal used by a mobile subscriber is a User Equipment (UE).

<FIG> shows a structure of a UMTS network in a prior art. The CN consists of a PS domain and a CS domain. The PS domain in the CN consists of a Serving GPRS Support Node (SGSN), a Gateway GPRS Support Node (GGSN), and a Home Location Register (HLR). The CS domain on the CN consists of a Mobile Switching Center (MSC), a Visitor Location Register (VLR), and a Gateway Mobile Switching Center (GMSC). The AN consists of a Radio Network Controller (RNC) and a NodeB. Each RNC is connected to several NodeBs. Each SGSN is connected to several RNCs. An Iu interface is a key interface between the AN and the CN. Management and control of radio resources are isolated on the AN by the Iu interface, and thus the CN focuses solely on the service provision.

On a traditional network such as an R99 system, one RNC is connected to only one CN node. For example, one RNC is connected to only one SGSN. Thus, problems such as single point failure exist. If an SGSN is down, a UE in the service area of the SGSN cannot access the network, and thus cannot perform communications. To rectify the foregoing defect, a concept of flex is introduced. <FIG> shows a configuration of a pool area in a prior art. When a many-to-many relationship between AN devices and CN devices exists on an Iu interface, the Iu interface is called Iu-flex. In <FIG>, an RNC is connected to multiple SGSNs, and an SGSN is connected to multiple RNCs. These SGSNs form a pool. In a pool, multiple CN nodes such as SGSNs are connected to all Radio Access Network (RAN) nodes (such as RNCs) in the pool, which is different from a traditional mode where one AN node is connected to only one CN node. When a UE enters a pool initially, an RAN node can select one CN node according to load sharing principles. Thus, when the UE moves or accesses the network in the pool, the UE is always anchored at the selected CN node. Therefore, single point failure and frequent relocation of CN nodes can be prevented because the UE does not need to change the CN node in the pool.

In a prior art, a network allocates a Temporary Mobile Station Identity (TMSI, which is allocated by an MSC in a CS domain) or a P-TMSI (which is allocated by an SGSN in a PS domain) to a UE after the UE is attached to the network.

<FIG> shows a network with TMSI/P-TMSI design in a prior art. The network includes four pools that have overlapped parts. Each pool includes five CN devices, which are differentiated with different Network Resource Identifiers (NRIs). A Non Access Stratum (NAS) Node Selection Function (NNSF) and the TMSI uniqueness of a UE in a paging area are not affected, and therefore, duplicate NRIs can be used in non-adjacent pools. Assume that each CN device can attach a maximum of <NUM>,<NUM>,<NUM> subscribers, while the overlapped pool areas have <NUM>,<NUM>,<NUM> subscribers, and other areas have few subscribers.

On the preceding network, <NUM> CN devices are sufficient to attach <NUM>,<NUM>,<NUM> subscribers. An NRI may be set to <NUM> bits (<NUM> = <NUM>, which can be used to identify <NUM> CN devices). The independently allocated ID of each device is <NUM> bits (<NUM> = <NUM>, which can be used to identify <NUM>,<NUM>,<NUM> subscribers), two bits are used to differentiate a PS domain from a CS domain, and the remaining four (<NUM> - <NUM> - <NUM> - <NUM> = <NUM>) bits are used for restart.

<FIG> shows a structure of the flex on an SAE network in a prior art. The flex is designed on the SAE network. In a pool, multiple CN nodes such as Mobility Management Entities (MMEs) are connected to all RAN nodes such as eNodeBs (ENBs), which is similar to the method of a prior art. When a UE enters the pool initially, an RAN node can select one CN node according to load sharing principles. Thus, when the UE moves or accesses the network in this pool, the UE is always anchored at the selected CN node. On the SAE network, pools may also be overlapped. In addition, the SAE network specifies that an MME pool or an S-GW pool includes a complete Tracking Area (TA, which is similar to a Location Area (LA) or a Routing Area (RA) on a UMTS network).

Assume that a UE is allocated one TA once. When the UE enters MME pool <NUM> (hereinafter referred to as MP1) for the first time, for example, when the UE enters ENB1, the UE selects one MME from MP1. When the UE moves from ENB1 to ENB2 and then to ENB3, the UE does not need to change the MME. When the UE moves to ENB4 that is not connected to the source MME and belongs to only MP2, the UE needs to reselect an MME in MP2. In <FIG>, ENB2 and ENB3 belong to two MME pools; that is, ENB2 and ENB3 are connected to all MMEs in the two MME pools. Therefore, ENB2 and ENB3 are overlapped parts of MP1 and MP2. The advantage of overlapping is as follows: because ENB3 is connected to MP2, when the UE returns from ENB4 to ENB3, the UE does not need to reselect an MME until the UE returns to ENB1, thus preventing ping-pong MME relocation. If ENB3 is not connected to MP2, the UE moves between ENB3 and ENB4, and as a result, ping-pong MME relocation occurs.

With respect to the TA concept, it should be noted that on an SAE network, multiple TAs can be allocated to a UE, which is different from the practice in a UMTS network where only one LA or RA can be allocated to a UE. In <FIG>, if a UE is registered in a pool, and if the TA list includes TA1 and TA2, the UE does not need to initiate an update when moving between ENB1 and ENB2. That is, the UE does not need to initiate an update when moving in the allocated TA list.

Currently, a TMSI problem about the SAE is as follows: the SAE needs to support multiple Radio Access Technologies (RATs), and therefore, several types of terminals access the network; to keep the system capacity, an SAE-TMSI (namely, SAE TMSI) may need to be extended to support more subscribers, to expand the capacity, and to simplify the network.

When implementing the invention, the inventor finds at least the following problem in the prior art: when a UE moves from an SAE network to an old network, the old network cannot identify the SAE-TMSI, and therefore, the newly selected SGSN cannot find the old MME on the SAE network; as a result, the new SGSN cannot obtain the context of the UE.

<CIT> relates to that an SAE-TMSI includes at least: a pool-ID, an MME-ID and a UE temporary identifier, and the SAE-TMSI is used to temporarily identify the UE in the SAE network.

<NPL>, discloses an updated definition and state transient of LTE-MM states.

Method and apparatuses are provided for accessing an old network through a temporary ID of an evolved network to rectify a technical defect in the prior art that a newly selected SGSN cannot obtain the context of a UE because the new SGSN cannot find the old MME on an SAE network. The present invention is defined by the method of independent claim <NUM> and <NUM>, and by the apparatus of independent claim <NUM> and <NUM>.

Embodiments of the invention are hereinafter described in detail with reference to the accompanying drawings.

A TMSI/P-TMSI is introduced to prevent a permanent ID, namely, an International Mobile Subscriber Identity (IMSI), from being exposed on an air interface and thus being tracked, so as to protect subscriber privacy. The TMSI is unique in an LA or RA of a UE (LA in a CS domain and RA in a PS domain; one LA may include several RAs). Thus, when the UE accesses a network, the TMSI/P-TMSI is taken as the user ID. In addition, the TMSI/P-TMSI has the following function: when the UE accesses a new CN node and the flex concept is not introduced, the new CN node searches old nodes for the context of the UE through a Location Area Identity (LAI) or Routing Area Identity (RAI). A many-to-many relationship between AN devices and CN devices exists on the flex, and therefore, it is insufficient to search old nodes according to the LAI or RAI. Old nodes must be determined according to the LAI/RAI and the TMSI/P-TMSI.

The TMSI/P-TMSI has another function, that is, an RAN can find a node where the UE is registered according to the TMSI or P-TMSI information in the case of the flex. The specific method is as follows: the configurable bits <NUM>-<NUM> available in the TMSI or P-TMSI are used to identify a Network Resource Identifier (NRI) which is used to differentiate different CN nodes in a pool. Thus, when the UE accesses the pool for the first time, an RAN node selects a proper CN node for the UE according to the NNSF and load sharing principles. When the UE moves in the pool, the UE does not change the selected node. The principle is as follows: the CN node allocates one TMSI or P-TMSI to the UE and the TMSI or P-TMSI carries an NRI that represents the CN node. When the UE accesses the pool, an Initial Direct Transfer message sent by the UE carries the TMSI or P-TMSI. According to the NRI in the TMSI or P-TMSI, the RAN node finds and selects the CN node where the UE is originally registered. Thus, when the UE moves in the pool, the UE does not change the CN node. When the UE moves out of the pool, the RAN node reselects a new CN node because it cannot find the corresponding NRI. Subsequently, when the UE moves in the new pool, the UE still does not change the new CN node.

A TMSI or P-TMSI in the prior art consists of <NUM> bits, namely, several bits used to differentiate a PS domain from a CS domain (two bits generally), configurable bits <NUM>-<NUM> used to identify an NRI (Bit <NUM> indicates no flex), several bits used as a restart ID, and several other bits. These bits may be allocated according to the network deployment situation. <FIG> shows a structure of the TMSI or P-TMSI in a prior art. Two bits are used to differentiate the TMSI from the P-TMSI. A <NUM>-bit restart ID is used to prevent that the allocated TMSI is reallocated because of node restart; the <NUM>-bit restart ID may be associated with the time to prevent duplicate TMSIs from being allocated. Seven bits are used to identify an NRI. The remaining <NUM> bits may be used as an ID allocated to the UE by each CN device.

<FIG> is a flowchart of accessing a <NUM>/<NUM> network in a prior art. In the flowchart, an RNC selects a new SGSN for a UE, and the new SGSN requests the context of the UE from the old SGSN according to the RAI+P-TMSI. The process is as follows: The UE initiates an RAU process and sends an RRC message (Initial Direct Transfer message) to the RNC. The message includes an RAU Request carrying the old RAI and old P-TMSI, where the RAU Request is located in the Non Access Stratum (NAS) information element (IE) of the RRC message. The RNC can see only the RRC message but does not parse the NAS message. According to the NRI information in the P-TMSI field carried on an Intra Domain NAS Node Selector Network Element (NE) of the RRC message, the RNC selects the corresponding SGSN, establishes a connection with the SGSN, and forwards the NAS message to the SGSN. If the RNC does not find the corresponding SGSN, it selects a new SGSN (in this process, the RNC selects a new SGSN).

According to the RAI and P-TMSI information carried in the received RAU Request, the new SGSN queries the address of the old SGSN in its configuration or domain name server (DNS). Then, the new SGSN sends a SGSN Context Request carrying the old RAI and old P-TMSI to the old SGSN to request the context of the UE. According to the old RAI and old P-TMSI information, the old SGSN finds the corresponding UE and returns the context of the UE to the new SGSN. After executing other processes such as updating a location to a Home Subscriber Server (HSS), the new SGSN allocates a new RAI and P-TMSI to the UE.

When the UE moves from an SAE network to an old network, the old network cannot identify the SAE-TMSI, and therefore, the newly selected SGSN cannot find the old MME on the SAE network. As a result, the context of the UE cannot be obtained. In embodiments of the invention, when the UE moves from an evolved network such as an SAE network to an old network such as a <NUM>/<NUM> network, the UE notifies the MME information of the MME where the UE is registered on the evolved network to the old network by sending an access message such as RAU or Attach to the old network. The MME information can uniquely identify the MME accessed by the UE in the evolved network. Thus, after the old network selects a new SGSN for the UE, the new SGSN determines and finds the MME according to the MME information in the access message, and then sends a Context Request or Identification Request to the MME to obtain the context (in the RAU process) or IMSI information (in the Attach process) of the UE. If a combined MME/SGSN exists, when the UE is registered with the combined node, and the UE moves from an SAE system to a <NUM>/<NUM> pool or from a <NUM>/<NUM> pool to an SAE system, it is better to select the old combined node if possible to prevent context transfer. Embodiments of the invention can also implement the function.

According to different cases of MME information, embodiments of the invention provide different methods for adding the MME information to an access message. For example, if one MME corresponds to one MME-id on an evolved network, the MME-id can uniquely identify the MME; therefore, only the MME-id needs to be added to the P-TMSI or RAI information in the access message. If a pool exists on the evolved network, an MME has a unique MME-id in the pool; therefore, the Pool-id+MME-id should be used to determine the MME. If Pool-ids on different Public Land Mobile Networks (PLMNs) are duplicate, the PLMN-id+Pool-id+MME-id can uniquely determine the MME. In addition, the TAI+Pool-id+MME-id or PLMN-id+TAI+Pool-id+MME-id may also uniquely determine the MME. The pool is an area where a UE moves and the serving MME does not need to be changed. The following describes the preceding cases provided in embodiments of the invention in detail.

In embodiments of the invention, it is assumed that the UE accesses an old network (such as a <NUM>/<NUM> network) through a temporary user ID (SAE-TMSI) of an evolved network. In a preferred solution, embodiments of the invention provide a structure of the SAE-TMSI, which includes the Pool-id, MME-id, UE temporary id, optional restart ID, and optional other IDs (the PLMN-id may be or may not be taken as one part of the SAE-TMSI). That is, the SAE-TMSI contains at least the Pool-id, MME-id, and UE-id. The Pool-id indicates the ID of a pool or area where the MME is located. The MME-id indicates the ID of an MME in the pool. The UE-id indicates an ID that uniquely identifies a UE in an MME. That is, the MME-id of the entire network is indicated by the Pool-id+MME-id.

The Pool-id may be unique or duplicate on the entire PLMN. The IDs of non-adjacent pools may be the same. Thus, if Pool-ids are duplicate, the SAE-TMSI and TAI information should be used together to identify an MME. The MME-id is a unique ID in the pool. The UE temporary id is an ID that may be allocated to the UE by each MME. A restart-id may also be added to the SAE-TMSI. The function of the restart-id is similar to the restart-id in a P-TMSI in a prior art; that is, the function is to prevent the same SAE-TMSIs from being allocated in the same MME. In addition, an ID used to differentiate a UMTS/SAE network or other IDs used to differentiate networks can be added to the SAE-TMSI.

The foregoing SAE-TMSI structure is a preferred solution provided in embodiments of the invention, where an RNC and an SGSN on a prior network do not need to be changed. However, the major concern of embodiments of the invention is that an old network can uniquely determine and find an MME that is accessed by the UE on an evolved network, and thus obtain the context of the UE after the UE accesses the old network through the SAE-TMSI. When the following requirements are met, any change of the SAE-TMSI structure should be covered in the scope of protection of the invention. Embodiments of the invention raise the following requirements for the SAE-TMSI:.

Obviously, the IDs that meet the preceding requirements for the SAE-TMSI are still in the SAE-TMSI range although their names are different.

<FIG> is a flowchart of a method for accessing an old network through a temporary ID of an evolved network according to the claimed invention.

The flowchart includes the following steps:.

Mode <NUM>: On the evolved network, the MME has a unique MME-id, based on which the old network can determine and find the MME that is accessed by the UE in the evolved network. In an embodiment of the invention, the UE adds the MME-id to the RAI information and/or P-TMSI information carried in the access message. Preferably, the UE adds the MME-id to the P-TMSI information. The UE may also add the MME-id to the P-TMSI Signature of the access message.

On the evolved network, an MME and an SGSN may be combined generally. In this case, the old network may reselect another SGSN rather than the combined MME/SGSN for the UE when the UE moves from the evolved network to the old network (<NUM>/<NUM> network) in the same pool as the evolved network, and accesses the old network. This causes unnecessary node reselection and context transfer. Therefore, the NRI and the MME-id of the combined MME/SGSN must be the same. In addition, when the UE moves from the evolved network to the old network, the NRI information in the P-TMSI information carried in the access message is set as the MME-id. Thus, when the old network selects an SGSN for the UE, it selects the old combined MME/SGSN, thus avoiding node reselection. <FIG> shows how to select a combined MME/SGSN in an embodiment of the invention. Assume that <NUM> and <NUM> indicate a combined MME/SGSN whose NRI or MME-id is equal to <NUM> and <NUM> respectively, and that <NUM>, <NUM>, and <NUM> indicate a pure MME or SGSN whose NRI or MME-id is equal to <NUM>, <NUM>, and <NUM> respectively. When the UE is registered with node <NUM> (a combined MME/SGSN) in pool <NUM>, the UE is still in pool <NUM> when it moves from the SAE network to the <NUM>/<NUM> network. When the UE initiates access in the <NUM>/<NUM> network, it uses an access message of the <NUM>/<NUM> network and places the MME-id part of the SAE-TMSI to the NRI part of the P-TMSI. Thus, upon reception of the message, a BSC or an RNC forwards the message to node <NUM> to establish a connection with node <NUM> through the information of NRI=<NUM>, and therefore, the combined SGSN/MME (<NUM>) can still be selected, and the node does not change. When moving to a <NUM>/<NUM> network in pool <NUM>, the UE initiates an RAU process. A BSC or an RNC receives an Initial Direct Transfer message. According to the information of NRI=<NUM>, the BSC or RNC cannot find the corresponding node, and therefore, it initiates node selection and selects a new SGSN with NRI=<NUM>. After receiving the RAU Request, the SGSN queries information in the configuration or DNS according to the RAI and P-TMSI information. If the DNS is upgraded or the configuration is changed, the corresponding old MME address may be found according to the MME-id (or Pool-id+MME-id or PLMN-id+Pool-id+MME-id). The new SGSN sends a Context Request carrying RAI and P-TMSI information to the MME. According to the implicit SAE-TMSI information in the RAI and P-TMSI, the old MME finds the corresponding UE and returns the context of the UE to the new SGSN.

According to the foregoing descriptions, placing the MME-id part of the SAE-TMSI to the NRI part of the P-TMSI is a preferred solution of the embodiment of the invention. Thus, unnecessary node reselection can be avoided efficiently.

In addition, if the UE moves from the <NUM>/<NUM> network (old network) to the SAE network (evolved network), the UE accesses the SAE network through the P-TMSI. An ENB (RAN node of the evolved network) selects the MME with MME-id=NRI preferentially. For example, if the UE moves from the SAE network to the <NUM>/<NUM> network, and the UE has been registered with the combined node <NUM> in pool <NUM>, the accessed <NUM>/<NUM> network still belongs to pool <NUM>. Then, the ENB still selects the old combined MME/SGSN (<NUM>). If the ENB cannot find the corresponding MME, it triggers a new MME selection process and selects a new MME for the UE.

Mode <NUM>: On the evolved network, the MME-id is unique in the same pool, but duplicate IDs may exist on the entire evolved network. The Pool-id is unique on the entire evolved network (PLMN). Therefore, the Pool-id+MME-id can uniquely identify the MME accessed by the UE in the evolved network. In a preferred embodiment of the invention, the SAE-TMSI contains the unique Pool-id on the PLMN, unique MME-id in a pool, and unique UE-id (and other possible fields) in an MME. That is, the MME can be identified by the unique Pool-id on the PLMN and the unique MME-id in the pool. The UE adds the Pool-id and the MME-id to the RAI and/or P-TMSI information carried in the access message; that is, the Pool-id and the MME-id are mapped to the RAI and/or P-TMSI field. Preferably, in an embodiment of the invention, the Pool-id and the MME-id are added to the RAI information and the P-TMSI information. <FIG> shows how to add the Pool-id and the MME-id to RAI information and P-TMSI information in an embodiment of the invention. The NRI information of the P-TMSI information in the access message is set as the MME-id, and the Pool-id is added to other information except the NRI (such as the other part of the P-TMSI or the LAC and/or RAC part of the RAI, or other part of the RAI except the Mobile Country Code (MCC) and the Mobile Network Code (MNC) and other part of the P-TMSI except the NRI); other information includes P-TMSI information, RAI information, or P-TMSI Signature. The RAI or P-TMSI information may also carry other IEs of the SAE-TMSI. For example, in <FIG>, the Pool-id is added to the RAI. The Pool-id may also occupy the P-TMSI or a part of RAI and a part of P-TMSI. To avoid unnecessary node reselection when a combined MME/SGSN exists, in another preferred embodiment of the invention, the MME-id part of the SAE-TMSI is placed to the NRI part of the P-TMSI (the NRI and the MME-id of the combined MME/SGSN must be the same). If the SAE-TMSI is longer than the P-TMSI (for example, the length is <NUM> bits or <NUM> bits), the other part needs to occupy certain bits of the RAI and/or certain bits of the P-TMSI Signature. In a preferred embodiment of the invention, only certain bits of the RAI are occupied to prevent the SGSN and the RNC from being changed.

The Pool-id and other part of the SAE-TMSI may be placed to the P-TMSI information except the NRI. If the SAE-TMSI is longer than the P-TMSI, the LAC and/or RAC part of the RAI can also be occupied. Thus, the length of the SAE-TMSI can be extended to a maximum of <NUM> bits. Therefore, the mode does not limit the number of MMEs on the PLMN. That is, the number of MMEs depends on the Pool-id+MME-id. The maximum number of MMEs in a pool is <NUM> (<NUM><NUM> because the maximum MME-id is the length of the NRI, namely, <NUM> bits). If no interaction with the <NUM>/<NUM> network is required, the number of MMEs in a pool is not limited by the length of the NRI.

Similarly, if the UE moves from the <NUM>/<NUM> network to the SAE network, the UE accesses the SAE network through the P-TMSI. In this case, the RAN node such as the ENB of the evolved network tries to select the MME with MME-id=NRI. For example, if the UE moves from the SAE network to the <NUM>/<NUM> network, and the UE has been registered with the combined node <NUM> in pool <NUM>, the accessed <NUM>/<NUM> network still belongs to pool <NUM>. Then, the ENB still selects the old combined MME/SGSN (<NUM>). If the ENB cannot find the corresponding MME, it triggers a new MME selection process and selects a new MME for the UE.

Therefore, an embodiment of the invention provides an optimized mode: in the case of a pure SAE network, it is required that Pool-ids should not be duplicate on the PLMN and that MME-ids should not be duplicate in a pool; in the case of a hybrid network of an SAE network and a <NUM>/<NUM> network, the NRI of the SGSN of the combined MME/SGSN must be equal to the MME-id of the MME of the combined MME/SGSN, and the MME-id of a pure MME should not be the same as the NRI of a pure SGSN in adjacent pools.

It should be noted that after the UE accesses the <NUM>/<NUM> network through the SAE-TMSI and selects a new SGSN, the SGSN needs to search the DNS or configuration for the old node according to the P-TMSI and the RAI (SAE-TMSI information actually from the SGSN point of view). If the DNS or configuration is upgraded, the old MME address can be uniquely determined and found according to the PLMN-id (MCC+MNC in the RAI) in the SAE-TMSI information, Pool-id, and MME-id. The SGSN sends a Context Request or Identification Request message carrying the P-TMSI and the old RAI (including the SAE-TMSI actually from the SGSN point of view). After receiving the message, the MME finds the UE according to the SAE-TMSI and returns the context of the UE.

Mode <NUM>: In this mode, the PLMN-id belongs to a part of the SAE-TMSI. On the evolved network, the MME-id is unique in a pool, but duplicate IDs may exist on the entire evolved network. A Pool-id is not unique on different PLMNs. Therefore, the PLMN-id (MCC+MNC) should be used with the Pool-id+MME-id to identify the MME accessed by the UE in the evolved network. That is, the MME is uniquely identified by the PLMN-id+Pool-id+MME-id. As shown in <FIG>, the NRI information of the P-TMSI information in the access message is set as the MME-id. The RAI, P-TMSI, and P-TMSI Signature can carry the PLMN-id and the Pool-id. For example, the PLMN-id is added to the RAI information, and the Pool-id is added to the other part of the P-TMSI information except the NRI; the PLMN-id and the Pool-id can be added to the RAI information or P-TMSI Signature information. In an embodiment of the invention, a preferred mode is to set the NRI information as the MME-id. The RAI, P-TMSI Signature, and P-TMSI can separately carry or together carry the PLMN-id and the Pool-id.

To avoid unnecessary node reselection when a combined MME/SGSN exists, another preferred embodiment of the invention places the MME-id part of the SAE-TMSI to the NRI part of the P-TMSI (the NRI and the MME-id of the combined MME/SGSN must be the same).

Mode <NUM>: When the Pool-id and the MME-id are not unique on the PLMN, for example, Pool-ids on the PLMN may be duplicate (Pool-ids of adjacent pools should be different), the old MME may be determined by combining the Pool-id and the MME-id with the TAI; that is, the MME is uniquely identified by the TAI+Pool-id+MME-id. <FIG> shows how to add a TAI, a Pool-id, and an MME-id to RAU information and P-TMSI information in an embodiment of the invention. The UE needs to provide the TAI information to the old network. Because the SAE-TMSI may be extended, the SAE-TMSI+TAI needs to occupy the position of the old RAI+P-TMSI. If the TAC occupies <NUM> bits, four bits may be provided for the SAE-TMSI. Thus, the SAE-TMSI has <NUM> bits. (The P-TMSI field is <NUM> bits in length, and the LAC+RAC is <NUM> bits in length. ) If the UE accesses a <NUM>/<NUM> network through the SAE-TMSI, the MME selects a proper SGSN at the NRI position, and the SGSN searches the updated DNS or configuration for the old MME and finds the old MME through the TAI+Pool-id+MME-id. The Pool-id may be combined with the MME-id into one MME-id. In an embodiment of the invention, the NRI information in the P-TMSI information of the access message is set as the MME-id, and the TAI and the Pool-id are added to the RAI information. To avoid unnecessary node reselection when a combined MME/SGSN exists, another preferred embodiment of the invention places the MME-id part of the SAE-TMSI to the NRI part of the P-TMSI (the NRI and the MME-id of the combined MME/SGSN must be the same).

Step S703: The old network selects the corresponding SGSN for the UE according to the access message. According to the NRI of the P-TMSI information carried in the received access message, the old network selects the corresponding SGSN. If no corresponding SGSN exists, the old network selects a new SGSN. If the UE accesses the new SGSN, the UE sends the RAI IE and P-TMSI information carried in the NAS message to the new SGSN.

Step S704: If the selected SGSN is a new node, the selected SGSN determines an MME according to the MME information carried in the access message and requests the UE information from the MME. Specifically, the configuration information or DNS of the SGSN is upgraded, and the SGSN searches the configuration information or DNS for the MME according to the MME information. For example, the corresponding address of the old MME can be found through the MME-id (or Pool-id+MME-id or PLMN-id+Pool-id+MME-id), and the new SGSN sends a Context Request carrying the RAI and P-TMSI information to the MME; the old MME finds the corresponding UE according to the implicit SAE-TMSI information in the RAI and P-TMSI and returns the context of the UE to the new SGSN.

According to the foregoing embodiments, an embodiment of the invention provides mode <NUM> of carrying SAE-TMSI information: The mode for a UE to access an old network such as a <NUM>/<NUM> network in the prior art is as follows: P-TMSI information is placed in a received RRC message (Initial Direct Transfer message), and an RAN node such as an RNC or a BSC finds the corresponding SGSN according to the NRI information in the P-TMSI information; in addition, the NAS message in the RRC message carries P-TMSI information, that is, two P-TMSIs; the P-TMSI (and the old RAI, as well as the possible P-TMSI Signature) in the NAS message is transferred to an SGSN, and the RAN node such as the RNC or BSC does not parse the P-TMSI information in the NAS message. Therefore, the method of this mode is as follows: only the P-TMSI in the RRC message is changed; the NRI information is set as the MME-id; and the information of the P-TMSI in the RRC message except the NRI information may not be processed, for example, may be set to zero. With regard to the P-TMSI, RAI, and P-TMSI Signature in the NAS message, it is required to place the MME information to the P-TMSI and/or the RAI only, and thus the old MME address can be found in the DNS or SGSN configuration. The MME-id does not need to be placed in the NRI information of the P-TMSI information in the NAS message. <FIG> is an embodiment of the invention. When a UE accesses an old <NUM>/<NUM> network through the SAE-TMSI, the NRI information of the P-TMSI information in an RRC message is set to MME information, such as the MME-id. In the NAS message, it is required that the old MME should be found according to the old RAI and the P-TMSI only. For example, the Pool-id and the MME-id are set in the old RAI, the UE-id and other bytes are placed in the P-TMSI, but the MME-id does not need to be placed in the NRI information of the P-TMSI information in the NAS message. Other implementation modes may also be adopted. For example, the global MME-id is placed to the old RAI, or the TAI is placed to the P-TMSI, or a duplicate MME-id is placed to the old RAI, and even the P-TMSI Signature can be used (for example, the global MME-id is placed to the old RAI and the P-TMSI, and the UE-id is placed to the P-TMSI Signature). Thus, the length of the SAE-TMSI can be further extended. The MME information such as the Pool-id, MME-id, and TAI are placed to the old RAI and/or P-TMSI, thus reducing the configurations of DNSs or SGSNs.

According to the DNS or configuration, the old MME/SGSN can be found. It is possible that the found old MME/SGSN is not the actual old MME/SGSN of the UE. For example, if the UE accesses an SGSN that is not configured with the flex, of another PLMN, and the SGSN searches for the address of the default MME/SGSN according to only the RAI information, the new SGSN sends a Context Request or Identity Request message carrying RAI and P-TMSI information to the MME/SGSN. After receiving the message, the default MME/SGSN finds the actual MME/SGSN according to the RAI and P-TMSI information, and then forwards the message to the actual MME/SGSN.

If the UE accesses the SAE network again through the allocated SAE-TMSI, an ENB can select the old MME according to the MME-id or Pool-id of the SAE-TMSI and the MME-id. If there is no corresponding MME, the ENB selects a new MME. The new MME finds the old MME according to the Pool-id and the MME-id in the SAE-TMSI. The old MME finds the UE according to the SAE-TMSI and returns the context of the UE to the new MME.

According to the foregoing embodiments, an embodiment of the invention further provides mode <NUM> of carrying SAE-TMSI information: In the foregoing modes, the PLMN-id, TAI, and Pool-id (or MME-id) may be added to the access message by occupying the P-TMSI Signature. In this mode, the method for occupying the P-TMSI Signature is mainly described, but it does not means that this mode can be implemented by occupying the P-TMSI Signature only. The embodiment can be used with other information, such as RAI information and/or P-TMSI information.

The P-TMSI Signature is used to ensure the security. When a UE accesses a <NUM>/<NUM> network, the UE can carry the old RAI, P-TMSI, and P-TMSI Signature to the access network. If an SGSN changes, the new SGSN uses the old RAI and the P-TMSI to query the address of the old SGSN. Then, the new SGSN sends an Identification Request and a Context Request that may carry the optional parameter P-TMSI Signature besides the old RAI and P-TMSI, to the old SGSN. Therefore, when the UE accesses the old network through the SAE-TMSI, the SAE-TMSI may occupy the P-TMSI Signature only if the new SGSN finds the address of the old MME according to the old RAI and the P-TMSI. <FIG> shows how to occupy the P-TMSI Signature in an embodiment of the invention. Assume that the SAE-TMSI in the embodiment consists of at least the Pool-id (the Pool-id is unique on the entire PLMN), MME-id, and UE-id. The Pool-id and the MME-id must be placed to the old RAI and/or P-TMSI information. The MME-id still needs to be placed in the NRI (in mode <NUM>, the MME-id of the P-TMSI information in the NAS message does not need to be placed in the NRI information). Other fields occupy not only the old RAI and P-TMSI information but also certain bits of the P-TMSI Signature. For example, the P-TMSI Signature has <NUM> bits, where ten bits are used for SAE security, and the remaining part may occupy certain bits (information necessary for querying the address of the old MME, such as the Pool-id and the MME-id cannot be placed in these bits) such as six bits according to the configuration length of the SAE-TMSI. Thus, after the UE accesses a new SGSN, the new SGSN queries the address of the old MME according to the old RAI and the P-TMSI. The new SGSN can find the address of the old MME according to the PLMN-id+Pool-id+MME-id if the configuration of the DNS or SGSN is upgraded. The new SGSN sends a Context Request carrying the old RAI, P-TMSI, P-TMSI Signature to the address of the old MME. The MME finds the corresponding UE through the SAE-TMSI formed by these parameters, and returns the context of the UE.

The Pool-id may not be unique or is even not required, and the corresponding MME is determined by a combination of the TAI information and the MME-id. For example, the UE accesses a <NUM>/<NUM> network through the SAE-TMSI and the old TAI. The SAE-TMSI includes an MME-id (The MME-id may be unique on the entire PLMN or unique in a pool. In the embodiment, assume that the MME-id is unique in a pool). The UE places the TAI information to the old RAI information and places the MME-id to the NRI information. The remaining information occupies the position of other remaining information of the old RAI and the P-TMSI, and even occupies the P-TMSI Signature that does not participate in query of the old MME. If the old MME can be queried according to the old RAI and the P-TMSI (the TAI and the MME-id actually), the other part of the SAE-TMSI that does not participate in query of the old MME may occupy the P-TMSI Signature. The new SGSN sends a request to the found MME address. The MME finds the UE according to a regrouped SAE-TMSI according to the parameters that are sent and returns a response.

The length of the SAE-TMSI may reach <NUM> bits by occupying the P-TMSI Signature. (Note that the information such as the MME-id, Pool-id, and TAI information used to query the MME cannot be placed to the P-TMSI Signature.

In the foregoing embodiments, when a UE moves from an evolved network to an old network, MME information for uniquely identifying an MME is added to an access message sent to the old network; therefore, the old network can determine and find the MME that is accessed by the UE in the evolved network without changing an RNC and an SGSN on the old network. Especially, when a combined MME/SGSN exists, unnecessary mode reselection can be avoided efficiently by setting the MME-id of the MME in the combined node to be the same as the NRI of the SGSN. (A configuration method can also be used, and therefore, the MME-id may be different from the NRI.

<FIG> shows a structure of a UE <NUM> in an embodiment of the invention. The UE <NUM> includes an access message sending module <NUM> and an MME information adding module <NUM>. The access message sending module <NUM> is adapted to send an access message to an old network when the UE <NUM> moves from an evolved network to the old network. The MME information adding module <NUM> is adapted to add MME information for uniquely identifying an MME accessed by the UE <NUM> on the evolved network to the access message sent by the access message sending module <NUM>.

The MME information adding module <NUM> includes a P-TMSI information adding submodule <NUM>, which is adapted to add the MME-id in an SAE-TMSI to the P-TMSI information of the access message.

The MME information adding module <NUM> includes an RAI information adding submodule <NUM>, which is adapted to add the Pool-id, and PLMN-id or TAI or PLMN in the SAE-TMSI to the RAI information of the access message.

The MME information adding module <NUM> further includes an NRI setting submodule <NUM>, which is adapted to set the NRI information in the P-TMSI information of the access message as the MME-id, thus avoiding unnecessary node reselection when a combined MME/SGSN exists.

The UE <NUM> further includes a P-TMSI Signature adding module <NUM>, which is adapted to add other information in the SAE-TMSI except the MME information to the P-TMSI Signature.

In addition, corresponding to the methods provided in the foregoing embodiments, the following case exists: The SAE-TMSI of a UE consists of an MCC, an MNC, a Pool-id, an MME-id, and an M-TMSI (remaining SAE-TMSI bits). A global MME ID is composed of the MCC+MNC+Pool-id+MME-id. The SAE-TMSI can uniquely identify a UE globally.

In a UMTS PS domain or GPRS system, the temporary ID of a UE is a P-TMSI. The P-TMSI uniquely identifies a UE in an RA. The P-TMSI and the RAI can uniquely identify a UE globally.

In addition, the following scenario may exist when a <NUM>/<NUM> network and an SAE network are deployed: a standalone SGSN and a standalone MME exist, and a combined MME/SGSN also exists. When a UE accesses a standalone SGSN, a P-TMSI and an RAI are allocated to the UE, and a P-TMSI Signature may also be allocated to the UE. The following RAI and P-TMSI combination includes the P-TMSI Signature. When the UE accesses a standalone MME, an SAE-TMSI is allocated to the UE. When the UE accesses a combined MME/SGSN, the combined node may allocate an SAE-TMSI or an RAI/P-TMSI combination to the UE. The SAE-TMSI and the RAI/P-TMSI can be mutually mapped; for example, the MCC+MNC+Pool-id+MME-id in the SAE-TMSI and the RAI can be mutually mapped, and the M-TMSI in the SAE-TMSI and the P-TMSI can be mutually mapped, or any other mapping method may be used (Certain bits are mapped to the P-TMSI Signature). If the UE accesses a <NUM>/<NUM> network, the RAI and the P-TMSI are allocated to the UE. If the UE accesses an LTE network, a combined node allocates an SAE-TMSI to the UE. Thus, when the UE accesses an SAE network, the UE uses the SAE-TMSI (if available) for access. An ENB finds the old MME through the MME-id information in an RRC message or selects a new MME (if the MME corresponding to the MME-id does not exist). If a new MME is accessed, the new MME may find the old MME and the UE context according to the SAE-TMSI, thus obtaining the context of the UE. If the UE has only the RAI/P-TMSI and accesses the SAE network, the RAI/P-TMSI is mapped to an SAE-TMSI for access. That is, when the UE accesses the SAE network, the network considers that the ID carried by the UE is the SAE-TMSI, which is the same as the SAE-TMSI that is actually carried by the UE. Specifically, the UE carries the mapped SAE-TMSI in an RRC Connection Complete message; the ENB finds the old MME (such as a combined node) according to the mapped MME-id or selects a new MME; the new MME finds the old SGSN and the UE context according to the mapped SAE-TMSI, thus obtaining the context of the UE. When the UE accesses the <NUM>/<NUM> network, the UE uses a P-TMSI and an RAI (if available ) for access. An RNC finds the old SGSN according to the NRI in the P-TMSI information of an RRC message or selects a new SGSN (if the SGSN corresponding to the NRI does not exist). If the UE has only an SAE-TMSI and accesses the <NUM>/<NUM> network, the UE accesses the network by mapping the SAE-TMSI to the RAI/P-TMSI. The foregoing mapping method may be used to access the old SGSN (a combined node) or a new SGSN. The new SGSN finds the old MME and the UE according to the mapped RAI/P-TMSI to obtain the context of the UE.

In the foregoing method, the combined node may allocate two IDs (the SAE-TMSI and the RAI/P-TMSI combination) to the UE only when the Idle mode Signaling Reduction (ISR) feature is enabled. Thus, the UE can know whether the ISR feature is enabled according to one or two IDs received rather than extra signaling or an extra parameter.

Furthermore, there is another solution: when the UE accesses a standalone SGSN, a P-TMSI and an RAI are allocated; when the UE accesses a standalone MME, an SAE-TMSI is allocated; when the UE accesses a combined MME/SGSN, the combined node allocates an SAE-TMSI and an RAI/P-TMSI combination, which cannot be mutually mapped, to the UE. The problem is as follows: when a UE supports only one RAT, for example, the UE belongs to the old network and supports only the <NUM>/<NUM> access technology, and when the ID of an RAT that is not supported is allocated to the UE, the UE cannot use or even cannot save the ID. Therefore, when the UE accesses a network, it needs to carry the RAT capability supported by the UE. A combined node obtains the RAT capability supported by the UE; for example, it may obtain the RAT capability from the UE or the context of the UE to determine how to allocate an ID. For example, the combined node allocates an RAI/P-TMSI combination to a UE that supports only the <NUM>/<NUM> access technology, allocates an SAE-TMSI to a UE that supports only the LTE access technology, and allocates an SAE-TMSI and an RAI/P-TMSI combination to a UE that supports the <NUM>/<NUM> access technology and the LTE access technology.

According to the foregoing descriptions, when the UE accesses an MME through the SAE-TMSI, the objective of the invention may be achieved through at least the following steps: setting the NRI of the P-TMSI information in the RRC message as the MME-id; and setting the MME address information to the old RAI and/or P-TMSI of the NAS message so that other information may occupy the old RAI, and/or P-TMSI, and/or P-TMSI Signature of the NAS message. It should be noted that the settings may not be sequential settings or unique settings. For example, certain bits of the Pool-id can be set to the old RAI and certain bits of the Pool-id can be set to the P-TMSI. In addition, the MME-id may be set both in the old RAI and in the NRI, and the information in the two positions can be the same or duplicate.

In the foregoing embodiments of the invention, when the MME information for uniquely identifying an MME is added to the access message sent to the old network, the old network can determine and find the MME that is accessed by the UE in the evolved network without changing the RNC and the SGSN on the old network. Each network node that communicates with the UE, such as an MME and an SGSN, may be described as the network.

An embodiment of the invention also proposes a method for providing a Temporary Logical Link Identity (TLLI) when a UE accesses a <NUM> network: The network receives an access message sent by the UE. The access message contains two TLLIs, namely, the first TLLI and the second TLLI. When the first TLLI information carries the TMSI information (if the RAT adopted for the last access is <NUM>/<NUM>, the TLLI is formed by removing the first two bits of the P-TMSI; if the RAT adopted for the last access is SAE, the TLLI is formed by removing the first two bits of the M-TMSI) of the RAT of the network that is accessed by the UE at the last time, the RAT is called the first RAT. When the second TLLI information carries the TMSI information (if the RAT adopted by the current access is <NUM>/<NUM>, the TLLI is formed by removing the first two bits of the P-TMSI; if the RAT adopted by the current access is SAE, the TLLI is formed by removing the first two bits of the M-TMSI) of the RAT of the network that is accessed by the UE currently, the RAT is called the second RAT. If the two RATs are the same, the UE may carry only the information of one TLLI. If the RAT adopted for the last access is SAE, the old RAI in an NAS message sent by the UE also needs to be mapped by other information of the SAE-TMSI except the M-TMSI. In addition, the NAS message sent by the UE further carries the old RAI of the RAT or the remaining information of the SAE-TMSI except the M-TMSI. When the two RATs are the same, the NAS message sent by the UE may not carry the old RAI of the RAT or the remaining information of the SAE-TMSI except the M-TMSI.

For example, when the UE moves from an MME of an evolved network to a <NUM> network, the first TLLI is formed by removing the first two bits of an M-TMSI and is placed at the normal TLLI position, and the second TLLI is formed by removing the first two bits of a P-TMSI on the <NUM> network and is placed at a new position (The usage is different from the usage in Release <NUM>). Other information of the SAE-TMSI except the M-TMSI carried in the NAS message sent by the UE is mapped to the normal old RAI position and the old RAI information of the <NUM> network carried in the NAS message is placed at a new position.

When the UE moves from a <NUM> network to another <NUM> network, or when the latest context of the UE is on the <NUM> network, the first TLLI is formed by removing the first two bits of a P-TMSI and is placed at the normal TLLI position, and the second TLLI is formed by removing the first two bits of the P-TMSI and is placed at a new position (The usage is different from the usage in Release <NUM>). The UE may also carry only one TLLI.

If an RAN node is connected to a <NUM> CN of a later version (such as Release <NUM>), the RAN node may use the second TLLI to select a CN node. If only one TLLI is available, the RAN node selects a CN node according to the TLLI. If an RAN node is connected to a <NUM> CN of an earlier version (such as Release <NUM> or earlier versions), the RAN node selects a CN node according to the first TLLI.

When a UE accesses an SGSN of a network earlier than 3GPP R8 (Pre-R8), the UE needs to carry the ID allocated for the RAT adopted for the last access, in the TLLI. For example, the ID allocated for the RAT of a <NUM>/<NUM> network that is last accessed by the UE is a P-TMSI. When the UE accesses an SGSN of Pre-R8, the UE removes the first two bits of a P-TMSI and places the P-TMSI to the TLLI. According to the received TLLI, the SGSN generate a P-TMSI of the NAS. For example, the SGSN adds two bits whose values are <NUM> before the TLLI.

If the last accessed MME of the UE is on an evolved network, the UE needs to remove the first two bits of the M-TMSI in the SAE-TMSI that is allocated to the UE by the MME and places the M-TMSI to the TLLI, and places other bits in the SAE-TMSI to the old RAI.

When the UE accesses a <NUM> network, the UE provides the information of two TLLIs if the UE has two TMSIs. The first TLLI carries the latest TMSI information of the UE, such as the TMSI information used when the UE accesses the network at the last time. The second TLLI carries the TMSI information that supports the same RAT when the UE accesses the network currently. If the UE finds that the two TMSIs are the same, the UE provides the information of only one TMSI. When an RAN node is connected to a new system, such as an SGSN of 3GPP R8, the access node selects a CN node according to only the second TLLI carrying the TMSI information that supports the same RAT when the UE accesses the network currently. If only one TLLI is available, the access node selects a CN node according to the TLLI. If the RAN node is connected to an old system, such as an SGSN of Pre-R8, the RAN node selects a CN node according to the first TLLI. With the embodiment, the RAN node can select a proper CN node according to the feature of the connected CN node. Thus, the old CN node can obtain the latest context information without being upgraded.

In an embodiment of the invention, a method is provided for accessing an old network through temporary ID of an evolved network. The method includes:.

In an example, after selecting, by the old network, a corresponding Serving GPRS Support Node, SGSN, the method further includes: determining, by the SGSN, the MME according to the MME information added to the access message if the SGSN is not a node registered by the UE; and requesting the UE information from the MME.

In another example, the MME information includes an MME-id in an SAE-TMSI, accordingly, adding, by the UE, MME information to an access message sent to an old network includes: adding the MME-id to the P-TMSI information of the access message and/or the RAI information of the access message.

In another example, adding the MME-id to the P-TMSI information of the access message includes: setting the NRI information in the P-TMSI information carried in the access message as the MME-id.

In another example, the MME information includes a Pool-id and the MME-id in an SAE-TMSI, accordingly, adding, by a UE, MME information for uniquely identifying an Mobility Management Entity to an access message sent to an old network includes: adding the MME-id and the Pool-id to the P-TMSI information of the access message and/or the RAI information of the access message.

In another example, adding the MME-id and the Pool-id to the P-TMSI information in the access message and/or the RAI information in the access message includes: setting the NRI information of the P-TMSI information in the access message as the MME-id; and adding the Pool-id to the RAI information and/or the P-TMSI information.

In another example, the MME information includes a PLMN-id and the Pool-id and MME-id in an SAE-TMSI, and accordingly, the adding, by a UE, MME information for uniquely identifying an Mobility Management Entity, MME, accessed by the UE on an evolved network, to an access message sent to an old network includes: adding the PLMN-id, Pool-id and MME-id to the P-TMSI information and/or RAI information.

In another example, the adding the PLMN-id, Pool-id and MME-id to the P-TMSI information and/or RAI information includes: setting the NRI information of the P-TMSI information as MME-id; and adding the PLMN-id to the RAI information; adding the Pool-id to the RAI information and/or P-TMSI information.

In another example, the method further includes: setting the NRI information of a combined MME/SGSN the same as the MME-id; and selecting, by the old network, the combined MME/SGSN for the UE when the UE enters the old network from the evolved network within the same pool as the old network.

In another example, the method further includes: selecting, by the evolved network, for the UE, the MME preferrentially of which the MME-id is the NRI value of the P-TMSI.

In another example, wherein the method further includes: adding the information of the SAE-TMSI other than MME information of the SAE-TMSI to the signature of the P-TMSI.

In another example, the determining, by the SGSN, the MME according to the MME information includes: upgrading configuration information or DNS of the SGSN; and finding, by the SGSN, the MME in the configuration information or DNS according to the MME information.

In another example, the access message includes Radio Resource Control message, RRC message, and the MME information includes MME-id; accordingly, the adding, by a User Equipment, UE, Mobility Management Entity, MME information for uniquely identifying an Mobility Management Entity, MME, accessed by the UE on an evolved network, to an access message sent to an old network includes: adding the MME-id to the NRI information in the P-TMSI information carried in the RRC message.

In another example, the method includes: adding the MME information to the P-TMSI and/or RAI of NAS information in the RRC message and mapping the information of SAE-TMSI other than MME information into the P-TMSI, RAI or P-TMSI Signature of the NAS information.

In another embodiment of the invention, a UE is provide for accessing old network through temporary ID of evolved network. The UE includes an access message sending module and an MME information adding module;.

In an example, the MME information adding module includes a P-TMSI information adding submodule, adapted to add the MME-id in an SAE-TMSI to the P-TMSI information of the access message.

In another example, the MME information adding module includes an RAI information adding submodule, adapted to add Pool-id, PLMN-id or TAI in the SAE-TMSI to the RAI information adding submodule.

In another example, the MME information adding module further includes an NRI setting submodule, adapted to set the NRI information in the P-TMSI information of the access message as the MME-id.

In another example, the UE further includes a P-TMSI signature adding module, adapted to add other information in the SAE-TMSI except the MME information to the P-TMSI Signature.

In another embodiment of the invention, a RAN is provided. The RAN is adapted to select an MME preferentially of which the MME-id is corresponding to NRI.

In another embodiment of the invention, a method is provided for enabling a UE to access an old network, wherein the method includes: receiving, by the old network, an access message sent by a UE that accesses the old network though a temporary ID of an evolved network, where the access message includes Mobility Management Entity information, MME information, for uniquely identifying an MME accessed by the UE in the evolved network; and selecting, by the old network, a corresponding SGSN for the UE according to the access message.

In another example, the MME information includes a Pool-id and MME-id of PLMN-id and S-TMSI, and the PLMN-id, the Pool-id, and the MME-id are contained in P-TMSI information and/or RAI information.

Through the foregoing descriptions, it is understandable to those skilled in the art that the embodiments of the invention may be implemented through software and a necessary general hardware platform or through hardware only. However, in most cases, software and a general hardware platform are preferred. Based on such understandings, the technical solution of the invention or contributions to the prior art can be embodied by software products. The software products are stored in a storage medium and incorporate several instructions to instruct a computer device, for example, a personal computer, a server, or a network device, to execute the method provided by each embodiment of the invention.

Claim 1:
A method for accessing a <NUM>/<NUM> network, the method comprising:
obtaining (s702), by a User Equipment, UE, mobility management entity, MME, information for uniquely identifying an MME initially
accessed by the UE in an evolved network, from
a system architecture evolution- temporary mobile station identity, SAE-TMSI, wherein the SAE-TMSI is allocated by the MME and the MME information comprises a Public Land Mobile Network-Identity, PLMN-id, a pool-id, and an MME-id;
sending (s703), by the UE, when the UE moves from the evolved network to the <NUM>/<NUM> network, an access message to a Serving general packet radio service, GPRS, Support Node, SGSN, in the <NUM>/<NUM> network, wherein the access message comprises the MME information of the SAE-TMSI, and wherein the access message enables the <NUM>/<NUM> network to select the SGSN for the UE, and, if the SGSN is a new node for the UE, the MME information enables the SGSN to determine the MME and request UE information from the MME.