CN102821381A

CN102821381A - Method and device for accessing and acquiring contexts and identifiers of user equipment

Info

Publication number: CN102821381A
Application number: CN2012102831227A
Authority: CN
Inventors: 郭小龙
Original assignee: Shanghai Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd; Shanghai Huawei Technologies Co Ltd
Priority date: 2008-06-18
Filing date: 2009-01-05
Publication date: 2012-12-12
Also published as: CN102821440B; CN102307339A; CN102761855B; CN102821440A; CN102761855A

Abstract

The embodiment of the invention provides a method and a device for accessing and acquiring contexts and identifiers of user equipment. The method comprises the following steps: when the user equipment UE is accessed into a system architecture evolution network SAE, an evolution base station eNodeB judges whether global mobile management entity identifiers GUMMEI carried by the UE or mobile management entity group identifiers MMEGI in the GUMMEI are distributed or mapped by the SAE. The method and the device provided by the invention have the advantages that the temporary identifiers carried when the UE is accessed into the network side are distinguished to be distributed or mapped by the network side, so that different access methods are adopted for different temporary identifiers, and flexible application to the temporary identifiers is realized.

Description

Insert, obtain the method and apparatus of customer equipment context and customer equipment identification

Technical field

The present invention relates to communication technical field, relate in particular to access, obtain the method and apparatus of customer equipment context and customer equipment identification.

Background technology

In existing communication network; There is traditional second generation (2G, Second Generation) communication network, the third generation (3G; 3rd Generation) communication network; And Long Term Evolution (LTE, Long Term Evolution)/system architecture evolution (SAE, the System Architecture Evolution) network that has merged more advanced technologies.Communication network is generally by wireless access network (RAN; Radio Access Network) and core net (CN; Core Network) form, different communication networks can adopt different wireless access technology (RAT, Radio Access Technology) to get into CN; Be that different communication networks has different RAN; For example the RAN of 3G communication network is called universal land radio access web (UTRAN, Universal Terrestrial Radio Access Network), and the RAN of SAE communication network is called E-UTRAN or the like.

RAN is made up of the RAN node, for example the radio network controller among the UTRAN (RNC, Radio Network Controller) and base station (NodeB); CN then is made up of the CN node, for example the SGSN among the UTRAN (Serving GPRS Support Node, Serving GPRS Support Node), perhaps Mobility Management Entity among the E-UTRAN (MME, Mobility Management Entity) etc.Wherein, the function of MME is to preserve the MM Context (Context) of subscriber equipment (UE, User Equipment), is called for short the context of UE, like UE sign, mobility management states, positional information etc.

In the prior art, a RAN node can be routed to a plurality of CN nodes, and promptly the RAN node can be selected to be routed on the different CN nodes for the initial UE that inserts.These CN nodes are formed territory, a pond (Pool); CN node in the Pool in the 2G/3G system; Like SGSN with network resource identifier (NRI; Network Resource Identifier) identify, the CN node in the Pool in the SAE system then is to identify with global unique Mobility Management Entity sign (GUMMEI).

When UE is linked into communication network; Communication network can be distributed to temporary mark of UE, and for example the 2G/3G system can give UE by allocation packets casual user sign (P-TMSI, Packet Temporary MobileSubscriber Identity)/TMSI; The SAE system then can distribute global unique temporary identity (GUTI; Global Unique Temporary Identity) gives UE, wherein, comprise GUMMEI among the GUTI.Because UE can move in different communication networks; So; Switch to new communications network at UE from former communication network; Or when former CN node switches to new CN node, need search the context that former CN node obtains UE through the temporary mark of NRI/GUMMEI and UE, so that can switch fast.If the switching between different communication network; Because the RAT that their adopt is different, so when UE during, the sign that also need shine upon the RAT of former communication network from former communication network access new communications network; The sign that is the RAT that is identified to new communications network of old RAT inserts; Like this, just possibly find the CN node in the former communication network, just possibly obtain the context of UE.

In realizing process of the present invention, the inventor finds that there is following problem at least in prior art:

Because the sign of the RAT after the mapping is different with the sign of real RAT, therefore the sign of the RAT after the mapping maybe corresponding CN node, promptly may appear to select in the new communications network less than the new situation of CN node.

In addition; Owing to have different communication networks; So if new CN node can not be discerned sign that the sign of current RAT is real RAT or the sign of the RAT after the mapping; Just do not know to adopt the RAT of which kind of form to obtain the UE context, cause and possibly can't obtain the UE context to former CN node.

Summary of the invention

The purpose of the embodiment of the invention is the method and apparatus that access is provided, obtains customer equipment context and customer equipment identification, realizes applying in a flexible way to temporary mark.

The embodiment of the invention provides a kind of method of access, and this method comprises:

When UE inserts SAE; Network side node; For example evolution base station (eNodeB) or the Centroid that presets judge that GUMMEI or the Mobility Management Entity group id among the said GUMMEI (MMEGI, Mobility Management Entity Group Identity) that said UE carries are that SAE distributes or mapping;

If being SAE, said GUMMEI or MMEGI distribute; Said eNodeB is according to said GUMMEI; Perhaps according to said MMEGI and Mobility Management Entity coding (MMEC; Mobility Management Entity Code), perhaps select Mobility Management Entity MME according to the sign (the following PLMN-id that all is called) of the public land mobile network (PLMN, Public Land Mobile Network) of said selection and MMEGI and MMEC;

If said GUMMEI or MMEGI shine upon; Said eNodeB is according to the Mobile Country Code MCC (MCC among the said GUMMEI; Mobile Country Code), Mobile Network Code (MNC; Mobile Network Code) and MMEC select MME, perhaps select MME, perhaps according to PLMN-id that selects and the selection of the MMEC among GUMMEI MME according to the MMEC among the said GUMMEI.

The embodiment of the invention also provides a kind of method of access, and this method comprises:

When UE inserted SAE, MME judged that the GUTI that said UE carries is that SAE distributes or mapping;

Distribute if said GUTI is SAE, said MME gets the context of UE to old Mobility Management Entity (old MME) with said GUTI;

If said GUTI shines upon; Said MME is reduced into old Routing Area Identifier (old RAI to said GUTI; Old Routing Area Identification) and packet TMSI P-TMSI, perhaps, be reduced into old RAI and logical links temporary mark (TLLI; Temporary Logical Link Identity), get the context of UE and according to the sign after the said reduction to old service universal grouping wireless business supporting node (old SGSN).

When UE inserted SAE, the GUTI that MME carries said UE was mapped to old RAI and P-TMSI, perhaps, and the form of TLLI and packet TMSI signature (P-TMSI Signature);

Said MME is with old RAI and P-TMSI after shining upon, or TLLI and P-TMSI Signature get the context of UE to old MME or old SGSN;

Said old MME is with said old RAI and P-TMSI, and perhaps, old RAI and TLLI and P-TMSI Signature are reduced into GUTI, and returns the context of UE to said MME according to the GUTI that reduction obtains.

During user equipment (UE) connecting system architecture evolution network SAE,

If said old node is MME, said MME gets the context of UE to old Mobility Management Entity old MME with said GUTI;

If said old node is Gn/Gp SGSN, then said MME is reduced into old Routing Area Identifier old RAI and packet TMSI P-TMSI to said GUTI, perhaps is reduced into logical links temporary mark TLLI; And get the context of UE to old SGSN with the sign after the said reduction; If said old node is S4 SGSN, then said MME gets the context of UE to old SGSN with said GUTI; Said old SGSN is reduced into old RAI and P-TMSI to said GUTI, perhaps is reduced into old RAI/TLLI sign, and returns to said MME find the context of UE through said sign after.

When UE inserts the 2G/3G network, old RAI and P-TMSI that SGSN carries according to said UE, perhaps, TLLI searches corresponding old physical address, obtains the context of UE to old entity;

If said old entity is old MME, said old MME reduces said old RAI and P-TMSI, or reducing said TLLI and P-TMSI Signature is GUTI, returns the context of the UE that finds to said SGSN.

When UE inserted the 2G/3G network, old RAI and P-TMSI that SGSN carries according to said UE, or the TLLI that carries according to said UE is that 2G/3G distributes or mapping with P-TMSI Signature, the old entity of searching correspondence were old SGSN or old is MME;

If old RAI and P-TMSI that said UE carries; Or TLLI and P-TMSI Signature shine upon, and said old entity is old MME; Said SGSN is according to said old RAI and P-TMSI; Or TLLI/P-TMSI Signature reduces GUTI, and obtains the context of UE to said old MME with GUTI; Said old MME will find the UE context and return to SGSN according to GUTI;

If old RAI and P-TMSI that UE carries, or TLLI and P-TMSI Signature are that 2G/3G distributes, said old entity is old SGSN, said SGSN is with said old RAI and P-TMSI, or TLLI gets the context of UE to said old SGSN.

The embodiment of the invention also provides a kind of contextual method of user equipment (UE) of obtaining, and this method comprises:

The temporary mark that upgrades temporary mark (TIN, the Temporary Identity used in Next update) indication of using when next time is consistent with additional (Additional) temporary mark, and the temporary mark that user equipment (UE) only carries the TIN indication inserts;

Access node finds the UE context through the temporary mark of the TIN indication that UE carries.

Tracing section updating (TAU in handoff procedure; Tracking Area Update) or Routing Area Update (RAU; Routing Area Update), UE only need carry the TMSI of this RAT system or not carry any TMSI, and UE sets up good connection through target side and finds the UE context.

The embodiment of the invention also provides a kind of method of the UE of obtaining sign, and this method comprises:

Initiate to adhere in (Attach) process at UE,

If there is the temporary mark of RAT in UE; Then carry said temporary mark; Insert entity and search corresponding node, obtain IMSI International Mobile Subscriber Identity (IMSI, International Mobile Subscriber Identity) and the security parameter of UE through said temporary mark;

If there is not the temporary mark that inserts RAT in UE, but there is the temporary mark of another RAT, then carries the temporary mark of said another RAT, insert entity and search corresponding node, obtain IMSI and the security parameter of UE through the temporary mark of said another RAT.

The embodiment of the invention also provides a kind of network side apparatus, comprises like lower module,

The identity property acquisition module is used to obtain the attribute of temporary mark of the UE of current access network side, and the attribute of the temporary mark of said UE is that said UE sign is that network side distributes or mapping;

Internet resources node distribution module is a UE allocation of network resources node according to the attribute of the temporary mark of said UE.

During user equipment (UE) connecting system architecture evolution network SAE; UE is sending to the radio resource control (RRC of evolution base station eNodeB; Radio Resource Control) Temporary Mobile Subscriber Identity (S-TMSI that carries the SAE network in the request message is set up in connection; Form by MMEC and M-TMSI; If UE carries the sign of 2G/3G and inserts the SAE/LTE system, then S-TMSI reality is shone upon with part P-TMSI with RAC by NRI and is formed), in sending to the RRC connection setup complete message of eNodeB, do not carry global unique Mobility Management Entity and identify GUMMEI; ENodeB selects corresponding movable management entity MME according to the S-TMSI that receives, if there is not corresponding MME, then eNodeB selects a new MME.

The still mapping that the temporary mark difference that the embodiment of the invention is carried through to UE access network side the time distributes for network side, thus different cut-in methods adopted to different temporary marks, and realization is to the flexible Application of temporary mark.

Description of drawings

Fig. 1 is the schematic flow sheet of cut-in method in the embodiment of the invention one;

Fig. 2 is the schematic flow sheet of cut-in method in the embodiment of the invention three;

Fig. 3 is the schematic flow sheet of cut-in method in the embodiment of the invention four;

Fig. 4 is the schematic flow sheet of cut-in method in the embodiment of the invention five;

Fig. 5 is the schematic flow sheet of cut-in method in the embodiment of the invention six;

Fig. 6 is the schematic flow sheet of cut-in method in the embodiment of the invention seven;

Fig. 7 is the structural representation of network side apparatus in the embodiment of the invention;

Network scenarios sketch map in Fig. 8 embodiment of the invention one;

Fig. 9 is the method flow diagram when UE uses TA registered case to insert the SAE/LTE network in the embodiment of the invention two;

Figure 10 is the method flow diagram when UE uses TA not registered case to insert the SAE/LTE network in the embodiment of the invention two.

Embodiment

Below in conjunction with accompanying drawing the embodiment of the embodiment of the invention is done further elaboration in detail.

Embodiment one, and present embodiment provides the method for demarcation of location district sign indicating number (LAC, Location Area Code) and MMEGI, and the numerical value that bit position corresponding among bit position and the MMEGI among the LAC for example is set is different, can distinguish LAC and MMEGI.Concrete method to set up, for example, the bit of MMEGI is 1, and the bit of LAC is 0, and this bit is called the flag bit of distinguishing MMEGI and LAC, can certainly use other bit as the diacritics position.Work as UE like this through old RAI and P-TMSI in the 3G network, or the TLLI in old RAI and the 2G communication network, when the GUTI after the mapping inserted eNodeB, eNodeB distinguished through this, and understanding UE uses real GUTI to insert.For example, it is the GUTI that SAE distributes that eNodeB obtains, and also is to use the GUTI after the mapping, as stated, and the GUTI access after old RAI and P-TMSI (or old RAI and TLLI) mapping.Under the situation that GUTI after UE carries mapping inserts; ENodeB selects the corresponding MME of MMEC of NRI mapping, and this MME can not be the MME of the original registration of UE, perhaps; Use the corresponding MME of MMEC of this NRI mapping; And this MME is that idle state signaling reduces node that (ISR, Idle mode Signaling Reduction) allow or unification node or during for the node of configuration, then selects this node.

See also Fig. 1, UE carries GUMMEI information in radio resource control (RRC, Radio Resource Control) part in inserting the SAE process; The RRC that promptly sends in tracing section updating request (TAU Request) message of eNodeB at UE partly carries GUMMEI information, and eNodeB inspection GUMMEI is the GUMMEI after the mapping, still the GUMME of SAE distribution; If the GUMME that SAE distributes, then eNodeB is according to all information among the GUMMEI, MCC+MNC+MMEGI+MMEC; Or MMEGI+MMEC confirms MME; Perhaps, eNodeB carries out the reselection procedure of MME owing to can not find corresponding GUMMEI, if the existence MME corresponding with MCC+MNC+MMEGI+MMEC or MMEGI+MMEC; Then select this MME, the GUMMEI that the GUMMEI of this MME and UE carry is consistent or MMEGI+MMEC is corresponding consistent.If do not have the MME corresponding then eNodeB reselects MME with MCC+MNC+MMEGI+MMEC or MMEGI+MMEC.If GUMMEI is the GUMMEI of mapping, then eNodeB perhaps only confirms MME according to MMEC according to the MCC+MNC+MMEC among the GUMMEI, is specially; If there is MME; MCC, MNC, the MMEC (by the NRI mapping) that the MCC of this MME, MNC, MMEC and UE carry consistent or dispose optional, for example: eNodeB configuring MME C or certain MME of NRI correspondence, then select this MME; Otherwise, MME of reselection procedure.

Perhaps, if UE is in inserting the SAE process, the sign that will carry according to UE; As passing through TIN (Temporary Identity used in Next update; The temporary mark that next update need use) discerns the sign that to carry, if TIN=" P-TMSI " representes the sign after next access need be carried P-TMSI/old RAI mapping; If TIN=" GUTI "; Expression inserts the sign of carrying SAE next time, if TIN=" RAT-related TMSI ", the TMSI that next that RAT of access of expression just distributes with that RAT.Therefore if during the TIN=" P-TMSI " of UE; UE can be at the GUMMEI access network after the RRC part is not carried mapping; (form but partly carry S-TMSI by MMEC and M-TMSI at RRC; It is actual that mapping forms with part P-TMSI with RAC by NRI) access network, eNodeB can not obtain MMEGI like this, and eNodeB meeting basis MMEC (being shone upon by NRI) wherein select MME.Certainly; If there is MOCN, eNodeB removes according to the MMEC among the S-TMSI and selects MME, also can select MME according to PLMN-id (Selected PLMN-id) information of selecting; Be that eNodeB is according to the PLMN-id that selects and MMEGI and MMEC selection Mobility Management Entity MME; If the MCC, the MNC that are specially among the GUMMEI of MME are identical with the PLMN-id of the selection that UE carries, MMEC is identical with the MMEC that UE carries simultaneously, then said this MME of network side node selection.In addition, UE also need be at the GUTI after Non-Access Stratum (NAS, Non Access Stratum) part is carried mapping, and MME could obtain context to old SGSN like this.Perhaps, eNodeB configuration LAC tabulation belongs to one of this LAC tabulation or this LAC tabulation when eNodeB finds MMEGI; Then select corresponding MME; When the sign of certain MME that the GUMMEI that for example carries as eNodeB discovery UE is corresponding with being configured in eNodeB is consistent, then select corresponding MME, otherwise; If there is not corresponding MME, carries out new MME and select; Wherein, the GUMMEI of this MME sign is actual is made up of the PLMN-id+LAC+NRI mapping.For example, the Pool of SAE and the Pool of 2G/3G are overlapping, and there is MME/SGSN unification node in this Pool; There is RAI1 under this Pool of 2G/3G, RAI2, RAI3; Three route districts (RA, Routing Area) are when UE also inserts from the 2G/3G network mobile to the SAE network; UE uses the GUTI of old RAI/P-TMSI mapping to insert, and eNodeB finds that according to information configured UE uses the GUTI of mapping; And the RA before the mapping belong to RAI1, RAI2, RAI3 one of them, then eNodeB selects corresponding MME get final product according to MCC+MNC+MMEC (by the NRI mapping) or MMEC, needn't MCC, MNC, MMEGI, MMEC all unanimity just select MME.If do not meet the MME of the correspondence of above-mentioned situation description, for example do not belong to one of RAI of configuration, then reselect a MME.

Wherein, eNodeB configuration LAC tabulation can be adopted following method.

MME is through S1 configuration response (S1 SETUP RESPONSE) message or MME config update (CONFIGURATION UPDATE) message; The LAC that disposes is mapped to GUMMEI sends to eNodeB; ENodeB this S1 SETUP RESPONSE message of record or MMECONFIGURATION UPDATE message; Be saved in the configuration information, i.e. in the LAC tabulation.To describe for example below.

For example among Fig. 8; Pool1 comprises SGSN Pool and MME Pool; SGSN1, SGSN2, MME1, MME2 etc. are the node among the Pool1; Also have MME/SGSN unification node SGSN3/MME3 among the Pool1, the LAC1 among Fig. 8, LAC2, LAC3 and LAC4 etc. then are respectively the Location Area Codes in the 2G/3G network, and TA1, TA2, TA3 and TA4 etc. then are respectively the tracking areas of SAE network; Wherein, from the SAE system perspective, the GUMMEI of unification node SGSN3/MME3 is PLMN-id (PLMN Identity; The PLMN sign; Wherein, PLMN-id is MCC+MNC)+MMEGI (being the id of MME Pool)+MMEC (being the id of MME3 among the MME Pool), in order to let the SGSN that is registered to this unification node; Be that UE on the SGSN3 also can choose this unification node when getting into the SAE zone from 2G/3G zone; MME3 can also be configured to all LAC in this SGSN3 Pool among the eNodeB, forms the LAC tabulation, and method is following:

To each LAC among the Pool1; MME3 forms a GUMMEI respectively; This GUMMEI corresponds to PLMN-id+LAC+NRI (promptly unify node configuration to SGSN, promptly the NRI on the SGSN3 is general equal to the MMEC on the MME with this unification node configuration); Therefore, MME3 can form several GUMMEI.This MME3 (has several with the GUMMEI after real GUMMEI (SAE in sign) and the mapping; The corresponding GUMMEI of each LAC among the Pool1) tabulation sends to eNodeB through S1 SETUP RESPONSE message or MME CONFIGURATION UPDATE message, this GUMMEI tabulation of eNodeB preservation (or perhaps the LAC tabulation, because each LAC has corresponding GUMMEI); Thereby as the LAC of UE from Pool1 that is registered to SGSN3; For example LAC1 or LAC2 etc. enter into the E-UTRAN zone, when inserting eNodeB since UE insert carry be designated GUMMEI (by the PLMN-id+LAC1+NRI mapping); Therefore this eNodeB can pass through query configuration; Promptly, learn the corresponding MME3 of this GUMMEI, directly select this MME3 node then through the tabulation of the GUMMEI after the real GUMMEI that preserves before the inquiry and the mapping.

The shortcoming that above collocation method exists is; Because unification node and ISR demand, may there be a large amount of mapping G UMMEI in a MME, because MME can form a MMEGI accordingly to each LAC in the Pool; Even MME also can also dispose a MMEGI respectively to satisfy the demand of ISR for each LAC in the adjacent S GSN Pool; Therefore, in S1 SETUP RESPONSE message or MME CONFIGURATION UPDATE message, possibly carry a large amount of GUMMEI.

S1 SETUP RESPONSE message and MME CONFIGURATION UPDATE message are carried the GUMMEI tabulation through following method at present, referring to table one, wherein, for convenience, have omitted other cells in the table.

Table one:

IE/Group Name (information element title)	......
		Served GUMMEIs (service GUMMEI tabulation)	......
GUMMEI (GUMMEI value)	......

Shown in table one, can carry complete GUMMEI tabulation in S1 SETUP RESPONSE message or the MME CONFIGURATION UPDATE message, promptly serve the GUMMEI tabulation.In addition, when SGSN Pool increase/deletion/modification LAC, MME can resend all GUMMEI tabulations to each eNodeB through MME CONFIGURATION UPDATE message.Because the GUMMEI tabulation is bigger, and eNodeB quantity is more, transmits in network so will inevitably cause more information, increase the signaling traffic in the network, promptly increased the weight of the expense of network.For example, if having 10 MME, 200 eNodeB among a Pool; So; When relevant LAC change, then need each MME to send MMECONFIGURATION UPDATE message to each eNodeB, this also just means and transmits on the S1 interface having 2000 CONFIGURATION UPDATE message; And, all comprise all GUMMEI tabulation (sending of renewal) in each message with all needing of not upgrading.For fear of this situation, the embodiment of the invention can also adopt following collocation method.

(1) in order to reduce the size of configuration messages such as S1SETUP RESPONSE message or MME CONFIGURATION UPDATE message; Make and need not to carry a large amount of GUMMEI tabulations in the configuration messages such as S1 SETUP RESPONSE message or MME CONFIGURATION UPDATE message; Can GUMMEI be decomposed; The tabulation that then each part of GUMMEI is formed is respectively sent; Be that the configuration messages about the LAC tabulation that MME sends is given eNodeB, carry PLMN-id tabulation, MMEGI tabulation and MMEC tabulation in the said configuration messages about the LAC tabulation, specific as follows:

Because to each LAC among the Pool; MME can form a corresponding GUMMEI, so eNodeB configuration LAC tabulation in fact also can be regarded as; Configuration GUMMEI tabulation on eNodeB; Because GUMMEI is made up of PLMN-id+MMEGI+MMEC, so if GUMMEI forms through mapping method, then the actual value of GUMMEI is PLMN-id+LAC+NRI.The value of MMEC and NRI is identical in general, and the value of PLMN-id also is identical, therefore, has a large amount of identical contents among the GUMMEIlist.Thus; Shown in table two; Can the GUMMEI tabulation be changed into the form of PLMN-id (i.e. PLMN Identity in the table)/PLMN-id list+MMEGI list+MMEC/MMEC list, wherein, PLMN-id list refers to the PLMN-id tabulation; MMEGI list refers to the MMEG tabulation, and MMEC list refers to the MMEC tabulation;

Table two:

Generally; PLMN-id in the GUMMEI tabulation is identical with the value of MMEC, and the value of having only MMEGI is different, therefore the tabulate form that makes PLMN-id+MMEGI list+MMEC into of GUMMEI is sent the PLMN-id that can save a large amount of repetitions and the transmission of MMEC; Certainly under the situation of supporting many PLMN; PLMN-id can also change PLMN-id list into, and in like manner, MMEC also can change MMEC list mode into.After the tabulation after eNodeB receives this change, preserve also and tabulate according to the synthetic GUMMEI of the information sets such as PLMN-id, MMEGI list and MMEC in the table voluntarily, accomplish configuration thus the LAC tabulation.

For example, PLMN-id is 3 byte at present, and MMEGI is 2 byte, and MMEC is 1 byte.If a MME Pool supports 3 PLMN, MME Pool need dispose 100 MMEGI and a MMEC, wherein, comprises the MMEGI after 1 real MMEGI and 99 LAC shine upon among 100 MMEGI).If by original collocation method, the size of GUMMEI list is: 3*100* (3+2+1)=1800byte so.And use this method, and present GUMMEI list is made up of PLMN-id list and MMEGI list and MMEC list, and the size that takies is: 3*3 (PLMN-list)+100*2 (MMEGI list)+1*1 (MMEC list)=210byte.Can find out that existing GUMMEI list takes up room and significantly reduces.

(2) in order to solve when LAC or the GUMMEI change; MME need send all GUMMEI tabulations and cause the problem that too much information transmits in network to eNodeB; The embodiment of the invention proposes, and when LAC or GUMMEI change, MME sends Indication message to eNodeB; GUMMEI in said Indication message indication eNodeB interpolation/modification/deletion LAC tabulation; For example in the MME CONFIGURATION UPDATE message that eNodeB sends, carrying an indication at MME, in indication, show the change conditions of LAC or GUMMEI, promptly is to add one or several GUMMEI or revised GUMMEI or deleted GUMMEI or the like.Amended MME CONFIGURATION UPDATE message can be referring to table three;

Table three:

Certainly, also can directly in message, indicate and add or deletion or modification GUMMEI, and need not let MME not have the GUMMEI that changes also to send to eNodeB other, for example can be following:

When MME need add a GUMMEI, then can send MME CONFIGURATION UPDATE (new GUMMEI, behavior='add') message is given eNodeB; Wherein, and the sign of the GUMMEI that " new GUMMEI " expression need be added (ID, Identity); " behavior='add' " then is that expression need be added GUMMEI in original LAC tabulation, and " behavior " is a kind of information element (IE, Information Element); Its value shows concrete action, like this, and when eNodeB receives this MME CONFIGURATION UPDATE (new GUMMEI; Behavior='add') after the message, just in original LAC tabulation, add a GUMMEI;

When MME will delete a GUMMEI; Then can send MME CONFIGURATION UPDATE (GUMMEI, behavior='delete') message is given eNodeB, wherein; " GUMMEI " indicates to delete the ID of the GUMMEI in original LAC tabulation; " behavior='delete ' " expression needs deletion GUMMEI, after eNodeB receives this message, according to this message corresponding GUMMEI of deletion in original LAC tabulation;

When MME will revise a GUMMEI; Then can send MME CONFIGURATION UPDATE (new GUMMEI; GUMMEI, behavior='modify') message is given eNodeB, wherein; " behavior='modify' " expression needs to revise the GUMMEI in original LAC tabulation; The ID of the GUMMEI that " GUMMEI " expression need to be revised, " new GUMMEI " then are the ID of the expression GUMMEI that need make into, and promptly " GUMMEI " ID of pairing GUMMEI in original LAC tabulates will change " new GUMMEI " into.

Certainly; Can not carry " behavior " such IE yet; For example can show action, promptly " upgrade GUMMEI " and " new GUMMEI ", wherein through " updated GUMMEI " and " new GUMMEI "; " updated GUMMEI " indicates to upgrade original GUMMEI, and new GUMMEI representes that needs add new GUMMEI; Like this, if updated GUMMEI void value or do not carried, and new GUMMEI=5 then indicates to add an id and is 5 GUMMEI; If updated is GUMMEI=5, and new GUMMEI void value or do not carried, it is that GUMMEI of 5 that expression will be deleted id; If updated is GUMMEI=5, and new GUMMEI=10, indicates to revise GUMMEI and equal that GUMMEI of 5 and change 10 into.

(3) certain, in order further to reduce when LAC or the GUMMEI change, MME sends to the quantity of the message of eNodeB, and the signaling traffic between minimizing MME and the eNodeB can also be taked another kind of method, as follows:

All configuration informations are all concentrated on the Centroid that presets; This Centroid can be the eNodeB that presets; Also can be MME that presets or the like, this Centroid has all MME configuration informations, if the configuration information of certain MME changes; Then send configuration messages to all eNodeB, such as sending S1 SETUP RESPONSE message or MME CONFIGURATION UPDATE message by this Centroid.Therefore, when this Centroid need be when eNodeB sends configuration information, with the configuration information that sends all MME.GUMMEI list such as in S1 SETUP RESPONSE message or the MME CONFIGURATION UPDATE message is not the GUMMEI list of a MME; But the GUMME list of all MME; Certainly; In order to realize this method, need make amendment to S1 SETUP REPONSE message, amended S1 SETUP REPONSE message is shown in table four;

Table four:

" GUMMEI " in the table is the real GUMMEI of each MME, and each MME has only a real GUMMEI, the GUMMEI after this does not consider to shine upon; MME uses this real GUMMEI as unique identification, and the information of all MME is concentrated in together, and forms MME list; Each MME among this MME list has some specific configuration information, such as the name of MME, ability; Also have GUMMEI list of mapping or the like, wherein, GUMMEI list possibly be (PLMN-id+MMEGI+MMEC) list; Also possibly be PLMN-id list+MMEGI list+MMEC list, also possibly not have the GUMMEI list of this mapping.

In a word; The configuration information of all MME among this MME Pool is provided through the eNodeB of configuration messages in Pool by this Centroid exactly; Like this, when LAC or GUMMEI change, just only need this Centroid to send a MME CONFIGURATION UPDATE message and get final product to each eNodeB; Need not each MME to each eNodeB transmission, thereby reduced the quantity of the message that transmits in the network.For example there are 10 MME in MME Pool; 200 eNodeB when the LAC change, just only need this Centroid to send out a total configuration messages about the configuration change to 200 eNodeB; Message number has only 200; Certainly, before this, MME possibly also need send the configuration messages of self to this Centroid.

More than (3) the three kinds of methods in (1) (2) can independently use, also can be used in combination, certainly; Be used in combination and optimize more, combine like (1) method and (2) method, so; When 10 LAC were added, MME just only needed to upgrade the information of these 10 LAC, sent PLMN-id list+10 the MMEGI+MMEC after the LAC mapping then and gave eNodeB; Under the situation of the core net node of not supporting a plurality of operators, this size that sends to the message of eNodeB just has only 3+20+1=24byte.Otherwise if only use (1) method, though the size of message has reduced, the quantity of message does not still change, and promptly still need send all GUMMEI information (comprise and not upgrading) and give eNodeB; If only use (2) method, though the quantity of message reduces to some extent, the size of message still is 6*10=60byte, and obviously than above-mentioned size with the message after (1) method and the combination of (2) method, promptly " 24byte " is many greatly.Certainly (3) method also can combine with (1) method or (2) method, even all combines, and repeats no more at this.

What need explanation is, present embodiment is that eNodeB is that example describes with network side node, and said network side node also can be said Centroid; That is to say that the performed operation of eNodeB also can be accomplished by this Centroid in the present embodiment, for example this Centroid also can be used as the node of selecting the CN node; That is, this Centroid links to each other with each eNodeB, when UE inserts eNodeB; ENodeB does not select the CN node; But send to this Centroid to message, select CN node, for example MME by this Centroid.Like this, just only need the configuration information of MME be configured to this Centroid and get final product, and need not send to eNodeB; That is to say; Each MME is when S1 foundation or configuration information change, i.e. during LAC or GUMMEI change, a needs and this Centroid carry out information interaction and get final product.For example there are 10 MME in MME Pool; 200 eNodeB; When LAC changed, 10 MME only need send the configuration messages about the configuration change to this Centroid, and message number has only 10; And need not send configuration messages to 200 eNodeB about the configuration change, significantly reduced the quantity that information transmits in the network.

The sign of the beneficial effect of embodiment one: embodiment one when inserting for UE distinguished; Obtain the information of UE sign; Confirm that this information is information or the network of the network allocation information after to the information mapping of this UE; And,, avoided UE owing to change RAT and can't be linked into corresponding CN node for UE selects the suitable network node according to above-mentioned differentiation.

Embodiment two; Embodiment one described method all is when UE carries 2G/3G sign access SAE/LTE network; Be not in the tracking area (TA of registration according to the current sub-district of being stationed of UE; Tracking Area) situation in inserts, in embodiment one described method, if the current sub-district of being stationed of UE is among the TA of registration; Then connect and set up the NAS part of accomplishing in (RRC Connection SetupComplete) message at RRC; For example the NAS of TAU Request message part (the following NAS of RRC connection setup complete message that all claims partly is NAS message) can not carried UE sign (UE-id), and like information such as GUTI or P-TMSI or IMSI, promptly whether UE can decide in NAS message, whether to carry the UE sign according to the TA of current access in the TA tabulation (TA list) of self.

That is to say; If carry the UE sign in the NAS message, general then think that the current sub-district of being stationed of UE is not among the TA of registration, and in fact; If in NAS message, carry the UE sign; So also can insert according to the situation that the current sub-district of being stationed of UE is among the TA of registration, the NAS message when inserting the SAE/LTE network such as the sign of carrying the 2G/3G network as UE can only be attach request (Attach Request) message or tracing section updating request (TAU Request) message, so; As long as these two message are always carried the UE sign; Even the MME that then selects does not have the UE context, the MME of this selection also can find old node to obtain the UE context through the UE sign, perhaps obtains the UE context to HSS.For this reason, present embodiment provides another kind of cut-in method.

For convenience, will not be in the current sub-district of being stationed of UE below that this situation calls TA not registered case among the TA of registration, otherwise, if the current sub-district of being stationed of UE is among the TA of registration, then be called TA registered case.What need explanation is; The technical scheme that is provided in order to describe present embodiment better; Below will do to introduce simply to TA registered case and TA not registered case technology, TA Registered case and TA not registered case be the technology of UE when carrying the sign access SAE that SAE distributes.

When UE got into a SAE Pool and use the temporary mark initiation access of SAE distribution, UE judged whether the sub-district of current access belongs to the registration area of UE, i.e. whether the current sub-district of being stationed of UE detection self is among the TA of registration; If; The UE of then idle (idle) pattern inserts RRC that the SAE/LTE network initiates and connects to set up in request (RRC Connection Request) message and carry S-TMSI, because UE does not necessarily move out original Pool zone in this case, therefore; ENodeB can directly choose original MME (under the MOCN situation through the MMEC among the S-TMSI; The PLMN-id information of the selection that also will carry according to UE combines to select MME), receive the RRC that carries S-TMSI that eNodeB returns connect set up message after, in order to reduce the size of message; The bandwidth that saving takies; Send at UE subsequently and can not carry the UE sign in the NAS message in the RRC connection setup complete message of eNodeB, the RRC part in the RRC connection setup complete message is not carried GUMMEI yet, after eNodeB has selected MME; ENodeB sends initial UE message and gives the MME that chooses; MME obtains the context of UE according to S-TMSI then, and wherein, initial UE message comprises that RRC that UE initiates connects S-TMSI and the information such as NAS message in the RRC connection setup complete message in the request of foundation; If not; Be UE when detecting among the TA that self current sub-district of being stationed is not in registration, the UE of then idle idle pattern inserts RRC that the SAE/LTE network initiates and connects to set up and carry a random number (Random ID) in the request message, receives the RRC that carries random number that eNodeB returns then and connects and set up message; Because UE possibly move out original Pool zone and also possibly not move out original Pool zone in this case; So the sign that need carry UE in the NAS message of UE in sending to the RRC connection setup complete message of eNodeB afterwards, the RRC in the RRC connection setup complete message partly carries GUMMEI simultaneously, and eNodeB just can search corresponding MME (under the MOCN situation through GUMMEI like this; ENodeB is that the PLMN-id of the selection of carrying according to UE and MME Group ID and the MMEC among the GUMMEI select MME's); If there is corresponding MME (MME originally), then directly choose original MME, if there is not corresponding MME; Explain that then UE has changed Pool; ENodeB selects a new MME so, and then sends initial UE message and give the MME that chooses, and is obtained the context of UE by this MME that chooses; Wherein, initial UE message comprises information such as NAS message.Can be referring to Fig. 9 and Figure 10, Fig. 9 inserts the method flow diagram of SAE/LTE network for UE uses TA registered case, and Figure 10 inserts the method flow diagram of SAE/LTE network for UE uses TA not registered case.

The cut-in method that present embodiment provides is: the sign of carrying 2G/3G as UE inserts the SAE system; UE at first is mapped as the sign of 2G/3G the sign format of SAE; Insert according to TA registered case then; Be that UE connects the S-TMSI that carries mapping in foundation request (RRC Connection Request) message at the RRC that initiates, and the part of the RRC in RRC connection setup complete message is not subsequently carried GUMMEI.And can always carry the UE sign in the NAS message in the RRC connection setup complete message, at this moment eNodeB can not carry S-TMSI in the initial UE message (article one Initial UE Message) of sending to MME.Also can be; UE judges whether the sub-district of current access is among the TA of registration, if then always do not carry the UE sign in the NAS message in the RRC connection setup complete message; If, then do not carry the UE sign in the NAS message in the RRC connection setup complete message.

Certainly; Before UE connecting system architecture evolution network SAE; The UE sign that UE also can dock fashionable use is that SAE distributes or the judging of mapping, if said UE sign is shone upon, just carries out the described action of above method; Promptly carry out UE and set up the S-TMSI that carries mapping in the request message, the step of in sending to the RRC connection setup complete message of eNodeB, not carrying GUMMEI in the RRC connection that sends to eNodeB; Otherwise, if being SAE, said UE sign distributes, judge then whether the zone of UE access belongs to the registration area of UE; If the zone that UE inserts belongs to the registration area of UE; Then carry out TA registered case and insert,, then carry out TA not registered case and insert if the zone that UE inserts does not belong to the registration area of UE; Can be referring to the associated description of TA registered case in the present embodiment and TA not registered case, no longer burdensome at this.

What need explanation is, to connect what set up that request message carries be S-TMSI or random number because eNodeB need distinguish RRC, therefore needs one of definition to be identified in S-TMSI and the random number; Such as identifying called after Distinguishing Mark; Define its size for 8bit,, confirm that then it is random number that RRC connects what set up that request message carries if the number on the 8bit is 1 entirely; If the number on the 8bit is not 1 entirely, confirm that then it is S-TMSI that RRC connects what set up that request message carries.This Distinguishing Mark is positioned at the MMEC part of S-TMSI and the preceding 8bit of random number.

Because UE carries the sign of mapping when inserting SAE, the MMEC among the S-TMSI partly is by the NRI mapping, and NRI possibly be complete 1, and eNodeB can think that what receive is random number by mistake like this, and therefore, need define NRI can not be complete 1.

Certainly, the registration area whether UE also can not need belong to UE to the sub-district of current access is judged, need is not judging of that SAE distributes or mapping to self-contained UE sign perhaps; But always be to use TA Registered Case, promptly connect to set up and always carry S-TMSI in the request message, then no matter under which kind of situation at the RRC that sends to eNodeB; NAS message in the RRC connection setup complete message is always carried the UE sign; And connect at RRC and to set up the S-TMSI that carries in the request message and just be used for supplying eNodeB to select MME, and needn't on S1 interface subsequently, S-TMSI be with, promptly eNodeB does not carry S-TMSI information in the initial UE message that MME sends; Thereby can reduce the flow size of message; The bandwidth that saving takies, still, the deficiency of this method is; When UE changes Pool; If also there is the MMEC of identical numbering in new Pool, then eNodeB directly selects this to have the pairing MME of MMEC of identical numbering in new Pool, does not select a new MME and can not pass through load balancing principles such as (Load Balancing).Perhaps; Also can always be to use TA not registered case to insert the SAE/LTE network; To be UE at the RRC that sends to eNodeB connect to set up always carries random number in the request message; RRC at subsequently RRC connection setup complete message partly carries GUMMEI, in the NAS of RRC connection setup complete message message, carries the UE sign, but like this UE initiate the process of services request (Service Request) can be too not fast; Because service request information is generally understood limited length, insert so that initiate as soon as possible.

Needing explanation be, is eNodeB with the RAN node just more than, and the CN node is that MME is that example describes, and this RAN node can also be the miscellaneous equipment that has similar functions with eNodeB, and the CN node also can be for having the miscellaneous equipment that has similar functions with MME.

The RRC connection that the beneficial effect of embodiment two: embodiment two initiates through UE is set up and is carried S-TMSI in the request message; Be that UE selects appropriate C N node through S-TMSI then; Avoided UE owing to change RAT and can't be linked into the situation of corresponding CN node, meanwhile, present embodiment is not through carrying method such as GUMMEI in the RRC connection setup complete message; Reduce the flow size of message, saved the bandwidth that takies.

Embodiment three, and present embodiment is distinguished LAC and MMEGI through being provided with, and the numerical value that bit position corresponding among bit position and the MMEGI among the LAC for example is set is different, can distinguish LAC and MMEGI.Present embodiment proposes to insert MME as UE through GUTI, and concrete access way can comprise adheres to attach or TAU.If there is UE context (UE Context) in MME, then MME finds UE through GUTI, otherwise; MME finds old MME through the GUMMEI among the GUTI; For example can pass through domain name analysis system (DNS, Domain Name System) and search old MME, and send context request (Context Request) to old MME; Comprise GUTI in this context request or send identification request (Identification Request); This identification request comprises GUTI, and old MME finds UE Context through GUTI, and the IMSI information etc. of UE Context or UE of returning is given MME.And the GUTI after UE is through old RAI/P-TMSI or TLLI mapping inserts MME, and MME or DNS need be the GUTI of UE distribution according to network---for example SAE is the GUTI that UE distributes---and the differentiation of the GUTI of mapping.As know that GUTI is the GUTI of mapping, the GUTI that then reduces is the TLLI/old RAI (if old SGSN is 2G SGSN) of old RAI/P-TMSI or 2G network.Perhaps find old SGSN through old RAI through old RAI and NRI; Send Context Request to old SGSN; This Context Request comprises old RAI, P-TMSI or TLLI, or send checking request (Identification Request); This Identification Request comprises old RAI, P-TMSI or TLLI.Old SGSN is through old RAI and P-TMSI, and perhaps old GGSN finds UE context through TLLI, and the IMSI information of UE Context or UE of returning is given MME.

See also Fig. 2, UE sends the tracing section updating request, and promptly TAU Request message is to MME; This TAU Request message comprises GUTI, and MME inspection GUTI is real GUTI, and promptly the SAE network side is distributed to the real GUTI of UE; Still the GUTI after shining upon, if real GUTI, then MME sends Context Request to old MME; This Context Request carries (GUTI, complete TAU Request message) and comes to obtain context to old MME, and old MME searches UE Context through GUTI; Complete TAU Request message is the TAU Request message that UE sends, if this message has integrity protection, then carries this message and gives old MME; Come the checked for integrity protection in order to old MME,, then return the UE context and give new MME if verify successfully.If MME inspection GUTI is the GUTI after the mapping, then MME sends Context Request (old RAI, P-TMSI or TLLI) to old SGSN, and old SGSN searches UE Context according to old RAI and P-TMSI or TLLI.

Wherein, about safety integrity protection problem, when the GUTI after UE is through mapping inserts the SAE system, several kinds of modes below can adopting:

1. the integrity protection parameter that does not have SAE owing to old SGSN, so MME can be that mapping back GUTI does not send TAU Request message to old SGSN according to GUTI.

Perhaps

2.MME no matter whether GUTI is the sign after the mapping, give the old node all the time, send TAU Request message like old SGSN and require checking; But old SGSN does not verify this message, returns the information of not verifying successfully or not having to verify and gives MME, makes MME carry out coupling of safety-relevant processes; If there is not the UE context among the MME, that for example subsidiary global unique temporary identity (Additional GUTI) is indicated is other MME, can carry out coupling of safety-relevant processes by other MME; Perhaps MME finds the UE context of self preserving according to Additional GUTI; UE is carried out safety verification, and perhaps, MME initiates safety certification process to UE.

Perhaps

Just in time indicate UE the UE context to be arranged 3.UE carry Additional GUTI at the MME that inserts; The MME that then inserts carries out safety verification to UE; If through safety verification, then in Context Request that old SGSN sends or Identification Request, carry the information that UE has verified.

Perhaps

4. if Additional GUTI is indicated to other MME, then new MME obtains safe context to the MME of Additional GUTI indication, and new MME verifies UE according to the security information of obtaining; Perhaps new MME MME that attach request (Attach Request) message or TAU Request message are issued Additional GUTI indication verifies.

Perhaps

5. if when UE carried GUTI after the mapping and inserts, UE did not carry out integrity protection to message such as TAU Request message or Attach Request message.

Perhaps

6. if when UE carried GUTI after the mapping and inserts, UE carried the P-TMSI Signature field that SGSN distributes to its, issues network, after MME receives, P-TMSI Signature field is issued the checking that old SGSN carries out UE.If promptly UE carries the GUTI access SAE of old RAI/P-TMSI or TLLI mapping; Then UE carries P-TMSI Signature cell; And MME also carries P-TMSI Signature cell to the Context Request message that old SGSN sends, and request old SGSN verifies UE.

Above safety problem can be applied to following UE equally and carry GUTI after the mapping and insert in the SAE system implementation example or UE carries among the embodiment that old RAI/P-TMSI (or TLLI)/P-TMSISignature after the mapping inserts 2G/3G (MME and SGSN need reversing of position).

Embodiment four, are that with the difference of embodiment three MME directly shines upon GUTI.Present embodiment MME is with the GUTI mapping or be reduced to old RAI/P-TMSI (or TLLI)/P-TMSISignature or old RAI/P-TMSI; Perhaps wherein P-TMSI also can be the form of TLLI; Form through old RAI/P-TMSI (or TLLI)/P-TMSI Signature is to the old entity; For example oldMME or old SGSN obtain context, if during old MME, old MME is with the oldRAI/P-TMSI mapping or be reduced to GUTI and obtain UE Context; If old is SGSN, directly according to old RAI/P-TMSI (or TLLI), P-TMSI Signature finds UE Context to old SGSN, can be referring to Fig. 3.

Embodiment five, are with the difference of embodiment three, and in the present embodiment, judgement is after the GUTI of mapping, are S4 SGSN or Gn/Gp is SGSN according to the old SGSN of correspondence, carry out different operation.It is that MME/S4-SGSN or Gn/Gp SGSN carry out different operating that present embodiment is understood the old node through access node.GUTI as after UE is through old RAI/P-TMSI mapping inserts MME, and concrete access way can be Attach (adhering to) or TAU mode.If it is the SGSN that supports S4 that MME is known old SGSN,, be to know that based on the interface of GTP-v2 old SGSN is the SGSN that supports S4 perhaps according to its interface for example according to inquiry DNS; MME sends Context Request to old SGSN so, and this Context Request GUTI comprises GUTI, or sends Identification Request; This Identification Request comprises GUTI, and by the differentiation of old SGSN according to GUTI, reduction GUTI is old RAI; P-TMSI; Perhaps be reduced to old RAI, P-TMSI TLLI is through old RAI and P-TMSI; Perhaps old RAI and/or TLLI find UE context, return UE Context or IMSI etc. and give MME; If it is the SGSN that supports Gn/Gp that MME is known old SGSN;, be to know that based on the interface of GTP-v1 or v0 old SGSN is the SGSN that supports Gn/Gp perhaps, for example like the SGSNPre-R8 SGSN before the 3GPP R8 version definition according to its interface according to inquiry DNS; MME reduction old RAI/P-TMSI (or TLLI) so; Send SGSN Context Request (old RAI, P-TMSI or TLLI) or Identification Request (old RAI, P-TMSI or TLLI) to old SGSN; Old SGSN finds UE context through old RAI and P-TMSI (or TLLI), returns to MME.

See also Fig. 4; If UE is when SAE Attach; Temporary mark (the TIN that the next update of UE uses; Temporary Identity used in Next update) be set to the temporary mark that uses at 2G/3G attachment removal Detach P-TMSI or TLLI or UE last time, UE need use old RAI/P-TMSI, and wherein P-TMSI also can be that GUTI after the TLLI mapping inserts SAE; MME receives the GUTI of this mapping; Can directly be reduced into old RAI/P-TMSI (or TLLI) or see that old SGSN is S4SGSN or Gn/Gp is SGSN; If old SGSN is S4 SGSN; UE can pass through Identification Request (GUTI, complete Attach Request message) and obtain IMSI and context etc. to S4 SGSN, and S4 SGSN is reduced to old RAI/P-TMSI (or TLLI) with GUTI and finds the UE context and return IMSI etc.If old SGSN is Gn/Gp SGSN, MME uses the old RAI/P-TMSI (or TLLI) after the reduction to obtain information to old SGSN, through identification request Identification Request, carries old RAI/P-TMSI (or TLLI) in this identification request.Certainly; Insert the temporary mark existence that RAT distributes if having; No matter UE also can use when Attach and insert the temporary mark that RAT distributes, and the indication of TIN, if do not insert the temporary mark of RAT then use the temporary mark of another RAT; If perhaps the temporary mark of each RAT does not all have, then use IMSI to insert.If GUTI is real GUTI; Carry the complete Attach Request message of bringing up from UE so in the Identification Request message possibly; Be used for old MME and carry out the integrity protection checking; If it is the GUTI of mapping that MME finds GUTI, MME need not carry this Attach Request message in issuing the Identification Request message of SGSN so, and need carry out safety verification to UE.

About safety-related problem, if there are context in Additional GUTI that UE carries or Additional RAI/P-TMSI indication UE in this locality, then UE carries out security process such as integrity protection checking in this locality; Like this, insert entity, for example MME or SGSN; Just need be to the old entity of TIN indication; For example old MME or old SGSN require to carry out integrity protection checking etc., and if UE carried out the integrity protection checking in this locality; Then insert entity and in Context Request, carry UE authorization information, old entity just needn't be verified UE.UE inserts entity in this locality does not else if having the UE context; The old entity of indicating as TIN is same RAT with inserting entity; Insert entity so and can require old entity that UE is carried out the integrity protection checking, for example insert entity the message that UE sends is sent to old entity, old entity is verified.Otherwise insert entity and can not require that old entity carries out security process to UE; For example insert entity and the message that UE sends is not sent to old entity; Perhaps, insert entity and require old entity that UE is carried out security process, if but old entity can't be verified (as usual entity is not same RAT with the access entity); Then old entity return checking not through or accomplish information such as checking, require the access entity voluntarily UE to be verified.In addition; If that the TIN of UE indication is " P-TMSI " or " TLLI ", then UE need carry P-TMSI Signature when Attach or TAU/RAU access, in order to carry out the safety verification of UE; Promptly inserting entity brings old entity UE is verified; That the TIN of UE indication is " GUTI " else if, and then UE need carry P-TMSISignature when inserting 2G/3G, is mapped to P-TMSI Signature because GUTI needs partial information.

Embodiment six, are with the difference of embodiment three, and among the embodiment three, that UE inserts through GUTI is MME, and in the present embodiment, that UE carries that old RAI/P-TMSI/P-TMSI Signature inserts is SGSN, wherein also TLLI of P-TMSI.Insert SGSN when UE carries old RAI/P-TMSI (or TLLI)/P-TMSI Signature, SGSN or DNS according to real old RAI/P-TMSI (or TLLI)/P-TMSI Signature with shine upon after different---1bit like MMEGI and LAC is different---of sign find old MME or old SGSN.SGSN can obtain context through old RAI/P-TMSI/P-TMSI Signature form to the old entity all the time, if the old entity is MME, SGSN sends SGSN Context Request to old MME; This Context Request comprises old RAI, P-TMSI/TLLI, P-TMSI Signature; Old MME recovers GUTI; Find UEContext, return UE Context, return EPS Context or 2G/3G Context according to interface or Context Request content.

See also Fig. 5, UE promptly passes through old RAI, P-TMSI/TLLI through sending the RAU request message; P-TMSI Signature inserts SGSN, if that the UE use is the old RAI of GUTI mapping, and P-TMSI/TLLI, P-TMSI Signature inserts; SGSN finds old MME address so, sends Context Request to old MME, and this Context Request carries (old RAI; P-TMSI/TLLI, P-TMSI Signature) message, old MME is according to old RAI; P-TMSI/TLLI, P-TMSI Signature reduce GUTI, find the UE context and return UE Context.In addition, because old MME do not have P-TMSI Signature information, therefore, UE verified can adopt following method:

1.Old MME carries not authorization information of UE safety in the Context Response that returns, for example carry ' the Cause value of P-TMSI Signature mismatch', make SGSN verify UE again.

2. perhaps; If SGSN does not have UE context and SGSN to understand the old RAI of TIN indication; P-TMSI/TLLI, the old node that P-TMSI Signature is corresponding is old MME, then SGSN always verifies UE; And the Context Request that sends to old MME carries " MS Validated " information, and expression UE is through checking.If SGSN has the UE context, wherein, can find UE Context through Additional RAI/P-TMSI; Then SGSN verifies UE in advance; If verify successfully, the Context Request that then sends to old MME carries " MS Validated " information, and expression UE is through checking.

Embodiment seven, are that with the difference of embodiment six among the embodiment six, by old MME oldRAI/P-TMSI/P-TMSI Signature is reduced into GUTI, wherein P-TMSI can be TLLI.In the present embodiment, when old entity is old MME, old RAI/P-TMSI (or TLLI)/P-TMSI Signature is reduced into GUTI by SGSN.See also Fig. 6, it is MME or SGSN that SGSN understands the old entity, if the old entity is MME, then S4SGSN recovers GUTI, sends Context Request (GUTI) to old MME, and old MME finds UE Context according to GUTI, returns UEContext.

Safety problem is with embodiment three to six, if there is the UE context SGSN this locality, and checking P-TMSISignature; If do not have the UE context and find the corresponding MME of old entity; Then SGSN always initiates security process to UE, and SGSN reduction GUTI, to old MME request UE context.

It is the sign after original temporary mark or the mapping that access node can oneself be distinguished temporary mark, also can pass through DNS, and whether this temporary mark of feedback access node is the sign after the mapping after being analyzed by DNS.If the old node address of access node and DNS translation is wrong, after then the old node after the translation is received Context Request, continue to search real old node, give real old node with message relay.

In addition; In the prior art; UE possibly also can carry Additional TMSI (subsidiary temporary mark), carries Additional GUTI when promptly UE inserts SAE, carries Additional old RAI/P-TMSI when inserting 2G/3G; Also TLLI of P-TMSI wherein; The effect of this Additional TMSI is to be used for finding the UE Context that possibly exist that inserts in the RAT entity as far as possible, and uses the temporary mark of TIN indication to obtain context etc., can directly merge the context that obtains like this to arrive the UE Context in this RAT entity; Need to inquire about again according to the IMSI information in the context that obtains whether there is UE Context in this RAT entity otherwise insert RAT, and then merging causes complexity.This Additional TMSI can carry under the situation in fact below, to save interface-free resources: TAU or RAU in periodic location update (Periodic TAU or Periodic RAU) or the handoff procedure; Or the temporary mark of TIN indication is consistent with the Additional temporary mark, and what promptly TIN indicated is exactly the temporary mark that inserts RAT; Or UE is when existing the temporary mark that inserts RAT in the Attach process.

Adopt the above embodiment of the present invention, the clear and definite processing of each node to temporary mark.Can realize:

GUTI after real GUTI and the mapping distinguishes to some extent; Old RAI/P-TMSI (or TLLI) after real old RAI/P-TMSI (or TLLI) and the mapping also distinguishes to some extent.As a bit position is set among LAC and the MMEGI, LAC is always 0, and MMEGI is always 1.

Insert SAE when UE uses the GUTI of old RAI/P-TMSI mapping, eNodeB knows that through differentiation UE uses old RAI/P-TMSI to insert, and then selects the corresponding MME of NRI as far as possible; Perhaps eNodeB is through finding whether this LAC has configuration, and whether decision is selected the corresponding MME of NRI or reselected MME.

GUTI after UE is through old RAI/P-TMSI mapping inserts MME, and MME understands the GUTI that this GUTI is mapping, reduction old RAI/P-TMSI/TLLI; Find old SGSN through old RAI and NRI; Send Context Request to old SGSN, this Context Request carry (old RAI, P-TMSI/TLLI); Old SGSN finds UE context through old RAI and P-TMSI/TLLI, returns to MME.

Perhaps, the GUTI after UE is through old RAI/P-TMSI mapping inserts MME, and MME understands the GUTI that this GUTI is mapping, and MME inquiry old SGSN is S4SGSN or Gn/GpSGSN.If old SGSN is S4 SGSN; MME sends Context Request (GUTI) to old SGSN so, and promptly this Context Request carries GUTI, perhaps sends Identification Request; Old SGSN reduction GUTI is old RAI; P-TMSI/TLLI finds UE context through old RAI and P-TMSI/TLLI, returns to MME; If old SGSN is Gn/Gp SGSN; MME reduction old RAI/P-TMSI/TLLI so; Send Context Request to old SGSN, this Context Request carry (old RAI, P-TMSI/TLLI); Old SGSN finds UE context through old RAI and P-TMSI/TLLI, returns to MME.

When the temporary mark of the TAU/RAU of Additional TMSI in switching HO, Periodic TAU/RAU, TIN indication is consistent with the Additional temporary mark or UE can not need when in the Attach process, having the temporary mark that inserts RAT.

When the MME of Combined node belongs to different PLMN with SGSN, or the MME of different PLMN and SGSN be when setting up ISR, and UE can let the RAN node choose corresponding CN node through carrying two PLMN-id or configuration.

The sign of carrying through differentiation UE is that which RAT distributes, and RAN node or access node can be done corresponding suitable processing, prevents to select wrong node or sends inconsistent parameter to corresponding node.

The embodiment of the invention also provides a kind of method of user equipment (UE) allocation of network resources node that is, this method comprises:

Network side obtains the mapping attribute of the entrained temporary mark of user equipment (UE),

Network side is a UE allocation of network resources node according to the mapping attribute of this temporary mark.

Particularly, network side to obtain the mapping attribute of the entrained temporary mark of user equipment (UE) be that network side distributes for network side judges sign or mapping after.

Implementation is described below in detail:

When the network side that inserts when user equipment (UE) is System Architecture Evolution network SAE, this network side obtain user equipment (UE) entrained identify label the mapping attribute specifically: the evolution base station eNodeB of this SAE network judges that global unique Mobility Management Entity sign GUMMEI/ or the Mobility Management Entity group id MMEGI among the said GUMMEI that said UE carries are that SAE distributes or mapping;

Distribute if said GUMMEI/ or MMEGI are SAE, then network side according to the mapping attribute of said sign be UE allocation of network resources node specifically: eNodeB is according to GUMMEI or MMEGI and Mobility Management Entity coding MMEC selection Mobility Management Entity MME;

If said GUMMEI or MMEGI shine upon, then network side is that UE allocation of network resources node specifically is that eNodeB selects MME according to the Mobile Country Code MCC MCC among the said GUMMEI, Mobile Network Code MNC and MMEC according to the mapping attribute of sign; Perhaps eNodeB selects MME according to the MMEC among the GUMMEI.

Perhaps also can realize through following mode:

When the network side that inserts when user equipment (UE) is System Architecture Evolution network SAE, network side obtain user equipment (UE) entrained identify label the mapping attribute specifically: the Mobility Management Entity MME of SAE network judges that the global unique temporary identity GUTI that said UE carries is that SAE distributes or mapping;

Distribute if GUTI is SAE, then network side is to comprise that also MME gets the context of UE to old Mobility Management Entity old MME with GUTI before the UE allocation of network resources node according to the mapping attribute of said sign;

If GUTI shines upon; Then network side is also to comprise before the UE allocation of network resources node according to the mapping attribute of sign, and MME is reduced into old Routing Area Identifier old RAI/ packet TMSI P-TMSI to said GUTI and perhaps is reduced into old RAI/ logical links temporary mark TLLI; And get the context of UE to old service universal grouping wireless business supporting node old SGSN with oldRAI/P-TMSI or old RAI/TLLI.

The statement of corresponding preamble method embodiment, the embodiment of the invention also provides a kind of user equipment (UE), and this UE comprises that the GUTI after UE uses mapping inserts the SAE system, does not then do integrity protection to inserting message.

See also Fig. 7, network side apparatus comprises identity property acquisition module 701, and the temporary mark that is used to distinguish after the UE use is shone upon still is real temporary mark, and real temporary mark is the sign that network side distributes; This network side node can be a wireless access network node.

Internet resources node distribution module 702, according to the attribute of the temporary mark of above-mentioned UE, promptly UE is network side sign of distributing or the sign after the mapping, is UE allocation of network resources node.This Internet resources node bag MME or SGSN or CN node.

Through the description of above execution mode, those skilled in the art can be well understood to the present invention and can realize by the mode that software adds essential hardware platform, can certainly all implement through hardware.Based on such understanding; All or part of can the coming out that technical scheme of the present invention contributes to background technology with the embodied of software product; This computer software product can be stored in the storage medium, like ROM/RAM, magnetic disc, CD etc., comprises that some instructions are with so that a computer equipment (can be a personal computer; Server, the perhaps network equipment etc.) carry out the described method of some part of each embodiment of the present invention or embodiment.

The above only is an embodiment of the present invention; Should be pointed out that for those skilled in the art, under the prerequisite that does not break away from the principle of the invention; Can also make some improvement and retouching, these improvement and retouching also should be regarded as protection scope of the present invention.

Claims

1. the method for an access is characterized in that, this method comprises:

During user equipment (UE) connecting system architecture evolution network SAE, network side node judges that global unique Mobility Management Entity sign GUMMEI or the Mobility Management Entity group id MMEGI among the said GUMMEI that said UE carries are that SAE distributes or mapping;

If being SAE, said GUMMEI or MMEGI distribute; Said network side node is according to said GUMMEI; Perhaps, perhaps identify PLMN-id and MMEGI and MMEC and select Mobility Management Entity MME according to the public land mobile network of selecting according to said MMEGI and Mobility Management Entity coding MMEC;

If said GUMMEI or MMEGI shine upon; Said network side node is selected MME according to the Mobile Country Code MCC MCC among the said GUMMEI, Mobile Network Code MNC and MMEC; Perhaps select MME, perhaps select MME according to PLMN-id that selects and the MMEC among the GUMMEI according to the MMEC among the said GUMMEI.

2. cut-in method according to claim 1 is characterized in that, said network side node judges that GUMMEI or MMEGI are that SAE distributes or the comprising of mapping:

Said network side node checks that the flag bit of MMEGI among the said GUMMEI is the sign of MMEGI or the sign of Location Area Code LAC;

If the sign of MMEGI judges that then GUMMEI is that SAE distributes;

If the sign of LAC judges that then GUMMEI shines upon.

3. cut-in method according to claim 1 is characterized in that, said network side node selects MME to comprise according to MMEGI among said GUMMEI or the said GUMMEI and MMEC:

If the GUMMEI of MME is identical with the GUMMEI that said UE carries, perhaps, if the MMEGI among the GUMMEI of MME and MMEC are identical respectively with MMEC with MMEGI among the GUMMEI that said UE carries, then said network side node is selected this MME; Perhaps,

Said network side node is searched the LAC tabulation; MMEGI in the GUMMEI that said UE carries belongs to one of said LAC tabulation, and then said network side node selects corresponding MME of the MMEC among the GUMMEI that said UE carries or said network side node to select MCC and the MME of MNC and MMEC correspondence among the GUMMEI that said UE carries.

4. cut-in method according to claim 1 is characterized in that, said network side node selects MME to comprise according to the MCC among the said GUMMEI, MNC and MMEC:

If the MCC among the GUMMEI of MME, MNC and MMEC are identical respectively with MCC, MNC and MMEC among the GUMMEI that said UE carries, then said network side node is selected this MME; Perhaps

If the MCC among the GUMMEI of MME, MNC are identical with the PLMN-id of the selection that UE carries, MMEC is identical with the MMEC that UE carries simultaneously, then said this MME of network side node selection.

5. cut-in method according to claim 1 is characterized in that, said network side node selects MME to comprise according to the MMEC among the said GUMMEI:

If the MMEC among the GUMMEI of MME is identical with MMEC among the GUMMEI that said UE carries, then said network side node is selected this MME; Perhaps,

Said network side node is searched LAC tabulation, and the MMEGI in the GUMMEI that said UE carries belongs to one of said LAC tabulation, and then said network side node is selected the corresponding MME of MMEC among the GUMMEI that said UE carries.

6. according to claim 3 or 5 described cut-in methods, it is characterized in that said eNodeB also comprises before searching the LAC tabulation:

Network side node configuration LAC tabulation.

7. cut-in method according to claim 6 is characterized in that, said network side node configuration LAC tabulation is specially:

Network side node receives the configuration messages about the LAC tabulation that MME sends, and carries the GUMMEI tabulation in the said configuration messages about the LAC tabulation, perhaps, carries PLMN-id tabulation, MMEGI tabulation and MMEC tabulation in the said configuration messages about the LAC tabulation;

Network side node is preserved said configuration messages about the LAC tabulation.

8. according to claim 6 or 7 described cut-in methods, it is characterized in that, also comprise:

When the LAC change, network side node receives the Indication message that MME sends, the GUMMEI in the Indication message indication network side gusset interpolation/modification that said MME sends/deletion LAC tabulation;

GUMMEI in the Indication message interpolation/modification that network side node sends according to said MME/deletion LAC tabulation.

9. according to each described cut-in method of claim 1 to 8, it is characterized in that said network side node comprises eNodeB or the Centroid that presets.

10. cut-in method according to claim 9 is characterized in that, also comprises:

If said network side node is eNodeB, so, when the LAC change, eNodeB receives the Indication message of the Centroid transmission of presetting, the GUMMEI in Indication message indication eNodeB interpolation/modification/deletion LAC tabulation that said Centroid sends;

GUMMEI in the Indication message interpolation/modification that eNodeB sends according to the said Centroid that presets/deletion LAC tabulation.

11. the method for an access is characterized in that, this method comprises:

During user equipment (UE) connecting system architecture evolution network SAE, Mobility Management Entity MME judges that the global unique temporary identity GUTI that said UE carries is that SAE distributes or mapping;

Distribute if said GUTI is SAE, said MME gets the context of UE to old Mobility Management Entity old MME with said GUTI;

If said GUTI shines upon; Said MME is reduced into old Routing Area Identifier old RAI and packet TMSI P-TMSI to said GUTI; Perhaps; Be reduced into old RA and logical links temporary mark TLLI, and get the context of UE to old service universal grouping wireless business supporting node oldSGSN according to the sign after the reduction.

12. cut-in method according to claim 11 is characterized in that, said MME judges that GUTI that said UE carries is that SAE distributes or the comprising of mapping:

Said MME checks that the flag bit of Mobility Management Entity group id MMEGI among the said GUTI is the sign of MMEGI or the sign of Location Area Code LAC;

If the sign of MMEGI judges that then GUTI is that SAE distributes;

If the sign of LAC judges that then GUTI shines upon.

13. cut-in method according to claim 11 is characterized in that, said old RAI of said usefulness and P-TMSI, and perhaps, old RAI and TLLI comprise to the context that old SGSN gets UE:

Said MME sends context request Context Request to said old SGSN, request message and said old RAI and P-TMSI, perhaps old RAI and TLLI when said Context Request carries said UE and inserts SAE; Said old SGSN returns the integrity protection authentication failed of described request message or does not have the message of checking to said MME; Said MME is according to the information of subsidiary global unique temporary identity Additional GUTI; UE context through self preserving verifies that to UE perhaps contextual MME transmission described request message that UE is arranged or the safety verification message to Additional GUTI indication requires this MME that UE is carried out the integrity protection checking; Perhaps said MME initiates security process to UE, and UE is carried out authentication;

Perhaps,

According to the indication of said old RAI and P-TMSI or old RAI and TLLI, said MME sends Context Request to said old SGSN, the request message when said Context Request does not carry said UE and inserts SAE; Said MME is according to the information of Additional GUTI; UE context through self preserving verifies that to UE perhaps contextual MME transmission described request message that UE is arranged or the safety verification message to Additional GUTI indication requires this MME that UE is carried out the integrity protection checking; Perhaps said MME initiates security process to UE, and UE is carried out authentication;

Perhaps,

According to said old RAI and P-TMSI; The perhaps indication of old RAI and TLLI; Said MME sends Context Request to said old SGSN, and said Context Request checking safe to carry is through information, and the request message when not carrying said UE and inserting SAE; Said MME is according to the information of Additional GUTI; UE context through self preserving verifies that to UE perhaps contextual MME transmission described request message that UE is arranged or the safety verification message to Additional GUTI indication requires this MME that UE is carried out the integrity protection checking; Perhaps said MME initiates security process to UE, and UE is carried out authentication.

14. cut-in method according to claim 11 is characterized in that, said MME comprises to the context that old SGSN gets UE:

If the context of UE is arranged on the said MME, the request message checking integrity protection when said MME inserts SAE to UE;

If checking is passed through, said MME sends Context Request to said old SGSN, and said Context Request carries checking and passes through message.

15. cut-in method according to claim 11 is characterized in that, said old RAI of said usefulness and P-TMSI or old RAI and TLLI comprise to the context that old SGSN gets UE:

According to the indication of Additional GUTI, the request message of said MME when the contextual MME that UE is arranged sends UE access SAE;

The contextual MME of the said UE of having returns the checking result to the integrity protection of described request message to said MME;

If checking is passed through, said MME sends Context Request to said old SGSN, and said Context Request carries said old RAI/P-TMSI or old RAI and TLLI and checking and passes through information;

According to said old RAI and P-TMSI, perhaps, find the context of UE according to said old RAI and the said old SGSN of TLLI;

Through information, said old SGSN does not verify UE, and returns the context of UE to said MME according to said checking.

16. cut-in method according to claim 11 is characterized in that, said old RAI of said usefulness and P-TMSI, and perhaps, old RAI and TLLI comprise to the context that old SGSN gets UE:

According to the indication of said Additional GUTI, said MME obtains safe context to the contextual MME that UE is arranged;

Request message checking integrity protection when said MME inserts SAE according to said safe context to UE;

If checking is passed through, said MME sends Context Request to said old SGSN, and said Context Request carries said old RAI and P-TMSI, perhaps, carries said old RAI and TLLI and checking and passes through information;

According to said old RAI and P-TMSI, perhaps, old RAI and TLLI, said old SGSN finds the context of UE;

17. cut-in method according to claim 11; It is characterized in that, if UE carries old RAI and P-TMSI, or; The GUTI of TLLI mapping inserts SAE, and then UE does not carry out integrity protection to tracing section updating request TAU Request message or attach request Attach Request message.

18. cut-in method according to claim 11; It is characterized in that; If UE carries old RAI and P-TMSI, or carry the GUTI access SAE of TLLI mapping, then UE carries packet TMSI signature P-TMSI Signature cell; And MME also carries P-TMSI Signature cell to the Context Request message that old SGSN sends, and request old SGSN verifies UE.

19. the method for an access is characterized in that, this method comprises:

During user equipment (UE) connecting system architecture evolution network SAE; The global unique temporary identity GUTI that Mobility Management Entity MME carries said UE is mapped to old Routing Area Identifier old RAI and packet TMSI P-TMSI; Perhaps, the form of logical links temporary mark TLLI and packet TMSI signature P-TMSI Signature;

Said MME is with old RAI and P-TMSI after shining upon, or TLLI and P-TMSI Signature get the context of UE to old Mobility Management Entity old MME or old service universal grouping wireless business supporting node old SGSN;

20. the method for an access is characterized in that, this method comprises:

If said old node is Gn/Gp SGSN, then said MME is reduced into old Routing Area Identifier old RAI and packet TMSI P-TMSI to said GUTI, perhaps is reduced into logical links temporary mark TLLI; And get the context of UE to old SGSN with the sign after the said reduction;

If said old node is S4SGSN, then said MME gets the context of UE to old SGSN with said GUTI; Said old SGSN is reduced into old RAI and P-TMSI to said GUTI, perhaps is reduced into old RAI/TLLI sign, and returns to said MME find the context of UE through said sign after.

21. the method for an access is characterized in that, this method comprises:

When user equipment (UE) inserts the 2G/3G network; Old Routing Area Identifier old RAI and packet TMSI P-TMSI that service universal grouping wireless business supporting node SGSN carries according to said UE; Perhaps; Logical links temporary mark TLLI searches corresponding old physical address, obtains the context of UE to old entity;

If said old entity is old MME; Said old MME reduces said old RAI and P-TMSI; Or said TLLI and the packet TMSI signature P-TMSI Signature that reduces is global unique temporary identity GUTI, returns the context of the UE that finds to said SGSN.

22. the method for an access is characterized in that, this method comprises:

When user equipment (UE) inserts the 2G/3G network; Old Routing Area Identifier old RAI and packet TMSI P-TMSI that service universal grouping wireless business supporting node SGSN carries according to said UE; Or; The logical links temporary mark TLLI and the packet TMSI signature P-TMSI Signature that carry according to said UE are that 2G/3G distributes or mapping, and searching corresponding old entity is old service universal grouping wireless business supporting node old SGSN or old Mobility Management Entity old MME;

23. one kind is obtained the contextual method of user equipment (UE), it is characterized in that this method comprises:

The temporary mark that upgrades the temporary mark TIN indication of using when next time is consistent with additional Additional temporary mark, and the temporary mark that user equipment (UE) only carries the TIN indication inserts;

24. one kind is obtained the contextual method of user equipment (UE), it is characterized in that this method comprises:

Tracing section updating TAU or routing area updating RAU in handoff procedure, UE only need carry the Temporary Mobile Subscriber Identity TMSI of this wireless access technology RAT system or not carry any TMSI, and UE sets up good connection through target side and finds the UE context.

25. a method of obtaining the user equipment (UE) sign is characterized in that this method comprises:

Initiate to adhere in the Attach process at user equipment (UE),

If there is the temporary mark that inserts wireless access technology RAT in UE, then carry said temporary mark, insert entity and search corresponding node through said temporary mark, obtain IMSI International Mobile Subscriber Identity IMSI and the security parameter of UE;

26. a network side apparatus is characterized in that, comprises like lower module,

27. the method for an access is characterized in that, comprising:

During user equipment (UE) connecting system architecture evolution network SAE; UE sets up the Temporary Mobile Subscriber Identity S-TMSI that carries the SAE network in the request message in the radio resource control RRC connection that sends to evolution base station eNodeB, in sending to the RRC connection setup complete message of eNodeB, does not carry global unique Mobility Management Entity sign GUMMEI;

ENodeB selects corresponding movable management entity MME according to the S-TMSI that receives, if there is not corresponding MME, then eNodeB selects a new MME.

28. the method for access according to claim 27 is characterized in that, also comprises:

Non access stratum NAS message in the RRC connection setup complete message of the said eNodeB of sending to is carried the UE sign.

29. the method for access according to claim 28 is characterized in that, also comprises:

ENodeB does not carry S-TMSI information in the initial UE message that the MME that selects sends.

30. the method for access according to claim 27 is characterized in that, also comprises:

UE judges whether the sub-district of current access is among the tracking area TA of registration, if the NAS message that then sends in the RRC connection setup complete message of eNodeB is not carried the UE sign.

31. the method according to each described access in the claim 27 to 30 is characterized in that, also comprises:

Before UE inserted SAE, UE judged that the UE sign of using when inserting is that SAE distributes or mapping;

If said UE sign shine upon, the S-TMSI that carries mapping in the request message is set up in the RRC connection that then sends to eNodeB, then sends in the RRC connection setup complete message of eNodeB and does not carry GUMMEI.