CN102821440B - The method and apparatus accessing, obtaining customer equipment context and customer equipment identification - Google Patents

Abstract

The embodiment of the present invention provides a kind of access, the method and apparatus obtaining customer equipment context and customer equipment identification.A kind of method of access, the method includes: when user equipment (UE) accesses System Architecture Evolution network SAE, and the Mobility Management Entity group mark MMEGI that evolution base station eNodeB judges in the unique Mobility Management Entity mark GUMMEI or described GUMMEI in the described UE whole world carried is SAE distribution or maps.And the method and apparatus accessing, obtaining customer equipment context and customer equipment identification, the temporary mark carried during by UE is accessed network side is distinguished as the still mapping of network side distribution, thus adopting different cut-in methods for different temporary marks, it is achieved the flexible Application to temporary mark.

Description

The method and apparatus accessing, obtaining customer equipment context and customer equipment identification

Technical field

The present invention relates to communication technical field, particularly relate to access, the method and apparatus obtaining customer equipment context and customer equipment identification.

Background technology

In existing communication network, there is the traditional second filial generation (2G, SecondGeneration) communication network, the third generation (3G, 3rdGeneration) communication network, and merged Long Term Evolution (LTE, LongTermEvolution)/system architecture evolution (SAE, the SystemArchitectureEvolution) network of more advanced technology.Communication network is generally by wireless access network (RAN, and core net (CN RadioAccessNetwork), CoreNetwork) composition, different communication networks can adopt different wireless access technology (RAT, RadioAccessTechnology) CN is entered, namely different communication networks has different RAN, such as the RAN of 3G communication network is called universal land radio access web (UTRAN, UniversalTerrestrialRadioAccessNetwork), the RAN of SAE communication network is called E-UTRAN etc..

RAN is made up of RAN node, for instance radio network controller (RNC, RadioNetworkController) in UTRAN and base station (NodeB)；CN is then made up of CN node, for instance the SGSN (Serving GPRS Support Node, ServingGPRSSupportNode) in UTRAN, or the Mobility Management Entity (MME, MobilityManagementEntity) etc. in E-UTRAN.Wherein, the function of MME is to preserve the MM Context (Context) of subscriber equipment (UE, UserEquipment), is called for short the context of UE, as UE identifies, and mobility management states, positional information etc..

In prior art, a RAN node can be routed to multiple CN node, and namely RAN node can be that the UE being initially accessed selects to be routed on different CN nodes.These CN nodes composition territory, one pond (Pool), CN node in Pool in 2G/3G system, such as SGSN network resource identifier (NRI, NetworkResourceIdentifier) identifying, the CN node in the Pool in SAE system is then identify with unique Mobility Management Entity mark (GUMMEI) in the whole world.

When UE is linked into communication network, communication network can distribute to mono-temporary mark of UE, such as 2G/3G system meeting allocation packets interim subscriber identity (P-TMSI, PacketTemporaryMobileSubscriberIdentity)/TMSI is to UE, SAE system then can distribute whole world unique temporary identity (GUTI, GlobalUniqueTemporaryIdentity) to UE, wherein, GUTI includes GUMMEI.Owing to UE can move in different communication networks, so, be switched to new communications network at UE from former communication network, or from former CN node be switched to new CN node time, the temporary mark requiring over NRI/GUMMEI and UE searches former CN node to obtain the context of UE, in order to can quickly switch.If the switching between different communication network, the RAT adopted due to them is different, so when UE accesses new communications network from former communication network, also need to map the mark of the RAT of former communication network, namely the mark of the RAT being identified to new communications network of old RAT accesses, so, it is only possible to the CN node found in former communication network, is only possible to the context obtaining UE.

In the process realizing the present invention, inventor have found that prior art at least there is problems in that

Owing to the mark of the RAT after mapping is different with the mark of real RAT, the mark possibility of the RAT after therefore mapping cannot corresponding CN node, it is possible to appear in situation about selecting in new communications network less than new CN node.

Additionally, owing to having different communication networks, if so the mark that new CN node not can recognise that current RAT is identifying or the mark of the RAT after mapping of real RAT, just do not know that the RAT adopting which kind of form obtains UE context to former CN node, cause that possibly cannot obtain UE context.

Summary of the invention

The purpose of the embodiment of the present invention is in that to provide the method and apparatus accessing, obtaining customer equipment context and customer equipment identification, it is achieved the flexible utilization to temporary mark.

The embodiment of the present invention provides a kind of method of access, and the method includes:

When UE accesses SAE, network side node, such as evolution base station (eNodeB) or preset Centroid judge that Mobility Management Entity group mark (MMEGI, MobilityManagementEntityGroupIdentity) in the described UE GUMMEI carried or described GUMMEI is SAE distribution or maps；

If described GUMMEI or MMEGI is SAE distribution, described eNodeB is according to described GUMMEI, or encode (MMEC according to described MMEGI and Mobility Management Entity, MobilityManagementEntityCode), or the mark (below referred to as PLMN-id) of the public land mobile network (PLMN, PublicLandMobileNetwork) according to described selection and MMEGI and MMEC select Mobility Management Entity MME；

If described GUMMEI or MMEGI maps, described eNodeB is according to the Mobile Country Code MCC (MCC in described GUMMEI, MobileCountryCode), Mobile Network Code (MNC, MobileNetworkCode) and MMEC select MME, or select MME according to the MMEC in described GUMMEI, or select MME according to the MMEC in PLMN-id and the GUMMEI selected.

The embodiment of the present invention also provides for a kind of method of access, and the method includes:

When UE accesses SAE, MME judges that the described UE GUTI carried is SAE distribution or maps；

If described GUTI is SAE distribution, described MME takes the context of UE with described GUTI to old Mobility Management Entity (oldMME)；

If described GUTI maps, described MME is reduced into old Routing Area Identifier (oldRAI described GUTI, and packet TMSI P-TMSI oldRoutingAreaIdentification), or, it is reduced into oldRAI and logical links temporary mark (TLLI, and take the context of UE according to the mark after described reduction to old service universal grouping wireless business supporting node (oldSGSN) TemporaryLogicalLinkIdentity),.

The embodiment of the present invention also provides for a kind of method of access, and the method includes:

UE access SAE time, the GUTI that described UE carries is mapped to oldRAI and P-TMSI by MME, or, TLLI and packet TMSI signature P-TMSISignature) form；

OldRAI and P-TMSI after described MME mapping, or, TLLI and P-TMSISignature takes the context of UE to oldMME or oldSGSN；

Described oldMME by described oldRAI and P-TMSI, or, oldRAI and TLLI and P-TMSISignature is reduced into GUTI, and the GUTI obtained according to reduction returns the context of UE to described MME.

The embodiment of the present invention also provides for a kind of method of access, and the method includes:

When user equipment (UE) accesses System Architecture Evolution network SAE,

If described old node is MME, described MME takes the context of UE with described GUTI to old Mobility Management Entity oldMME；

If described old node is Gn/GpSGSN, then described MME is reduced into described GUTI old Routing Area Identifier oldRAI and packet TMSI P-TMSI, or is reduced into logical links temporary mark TLLI；And take the context of UE to oldSGSN by the mark after described reduction；If described old node is S4SGSN, then described MME takes the context of UE with described GUTI to oldSGSN；Described oldSGSN is reduced into oldRAI and P-TMSI described GUTI, or is reduced into oldRAI/TLLI mark, and returns to described MME after found the context of UE by described mark.

The embodiment of the present invention also provides for a kind of method of access, and the method includes:

When UE accesses 2G/3G network, SGSN according to described UE oldRAI and the P-TMSI carried, or, TLLI, search corresponding old physical address, obtain the context of UE to old entity；

If described old entity is oldMME, described oldMME reduces described oldRAI and P-TMSI, or, described TLLI and the P-TMSISignature that reduces is GUTI, returns the context of the UE found to described SGSN.

The embodiment of the present invention also provides for a kind of method of access, and the method includes:

When UE accesses 2G/3G network, SGSN according to described UE oldRAI and the P-TMSI carried, or, be 2G/3G distribution according to described UE TLLI and the P-TMSISignature carried or map, searching corresponding old entity is oldSGSN or oldMME；

If oldRAI and the P-TMSI that described UE carries, or, TLLI and P-TMSISignature maps, described old entity is oldMME, described SGSN is according to described oldRAI and P-TMSI, or, TLLI/P-TMSISignature reduces GUTI, and obtains the context of UE to described oldMME with GUTI；Described oldMME will find UE context according to GUTI and return to SGSN；

If oldRAI and the P-TMSI that UE carries, or, TLLI and P-TMSISignature is 2G/3G distribution, and described old entity is oldSGSN, described SGSN with described oldRAI and P-TMSI, or, TLLI takes the context of UE to described oldSGSN.

The embodiment of the present invention also provides for a kind of method obtaining user equipment (UE) context, and the method includes:

As the temporary mark (TIN that next update uses, TemporaryIdentityusedinNextupdate) temporary mark indicated is consistent with additional (Additional) temporary mark, and user equipment (UE) only carries the temporary mark of TIN instruction and accesses;

Access node finds UE context by the UE TIN the carried temporary mark indicated.

The embodiment of the present invention also provides for a kind of method obtaining user equipment (UE) context, and the method includes:

Tracing section updating (TAU in handoff procedure, or Routing Area Update (RAU TrackingAreaUpdate), RoutingAreaUpdate), UE has only to carry the TMSI of this RAT system or do not carry any TMSI, UE find UE context by the connection that target side establishes.

The embodiment of the present invention also provides for a kind of method obtaining UE mark, and the method includes:

Initiate in attachment (Attach) process at UE,

If there is the temporary mark of RAT in UE, then carry described temporary mark, access entity and search corresponding node by described temporary mark, obtain IMSI International Mobile Subscriber Identity (IMSI, InternationalMobileSubscriberIdentity) and the security parameter of UE；

If UE is absent from accessing the temporary mark of RAT, but there is the temporary mark of another RAT, then carry the temporary mark of another RAT described, access entity and search corresponding node, the IMSI of acquisition UE and security parameter by the temporary mark of another RAT described.

The embodiment of the present invention also provides for a kind of network side apparatus, including such as lower module,

Identity property acquisition module, for obtaining the attribute of the temporary mark of the UE of present access network side, the attribute of the temporary mark of described UE is, described UE mark is network side distribution or maps；

Internet resources node distribution module, is that UE distributes Internet resources node according to the attribute of the temporary mark of described UE.

When user equipment (UE) accesses System Architecture Evolution network SAE, UE is being sent to the radio resource control (RRC of evolution base station eNodeB, RadioResourceControl) connection establishment request message carry the Temporary Mobile Subscriber Identity (S-TMSI of SAE network, it is made up of MMEC and M-TMSI, if the mark that UE carries 2G/3G accesses SAE/LTE system, then actual the mapping by NRI and RAC and part P-TMSI of S-TMSI forms), the RRC connection setup complete message be sent to eNodeB does not carry the unique Mobility Management Entity mark GUMMEI in the whole world；

ENodeB selects corresponding Mobility Management Entity MME according to the S-TMSI received, and without corresponding MME, then eNodeB selects a new MME.

The temporary mark carried when the embodiment of the present invention is by accessing network side to UE is distinguished as the still mapping of network side distribution, thus adopting different cut-in methods for different temporary marks, it is achieved the flexible Application to temporary mark.

Accompanying drawing explanation

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

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

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

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

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

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

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

Network scenarios schematic diagram in Fig. 8 embodiment of the present invention one；

Fig. 9 is method flow diagram during UE use TAregisteredcase access SAE/LTE network in the embodiment of the present invention two；

Figure 10 is method flow diagram during UE use TAnotregisteredcase access SAE/LTE network in the embodiment of the present invention two.

Detailed description of the invention

Below in conjunction with accompanying drawing the detailed description of the invention of the embodiment of the present invention done and further elaborate.

Embodiment one, the method present embodiments providing demarcation of location district code (LAC, LocationAreaCode) and MMEGI, for instance the numerical value arranging the bit position corresponding from MMEGI, the bit position in LAC is different, it is possible to distinguish LAC and MMEGI.Concrete method to set up, for instance, the bit that a bit is 1, LAC of MMEGI is 0, and this bit is called the flag bit distinguishing MMEGI and LAC, naturally it is also possible to use other bit as diacritics position.So when UE is by oldRAI and the P-TMSI in 3G network, or the TLLI in oldRAI and 2G communication network, when the GUTI after mapping accesses eNodeB, eNodeB passes through this differentiation, understands UE and uses real GUTI to access.Such as, it is the SAE GUTI distributed that eNodeB obtains, or uses the GUTI after mapping, as it has been described above, the GUTI after oldRAI and P-TMSI (or oldRAI and TLLI) mapping accesses.When the GUTI after UE carries mapping accesses, eNodeB selects the NRI MME corresponding for MMEC mapped, this MME can not be the UE MME originally registered, or, use MME corresponding for this NRI MMEC mapped, and this MME is that idle state signaling reduces (ISR, IdlemodeSignalingReduction) node of allowing or unification node or during for the node of configuration, then select this node.

Refer to Fig. 1, UE is accessing in SAE process at radio resource control (RRC, RadioResourceControl) part carries GUMMEI information, namely GUMMEI information is carried in the UE RRC part being sent in tracing section updating request (TAURequest) message of eNodeB, eNodeB checks that GUMMEI is the GUMMEI after mapping, or the GUMME of SAE distribution, if the GUMME of SAE distribution, then eNodeB is according to all information in GUMMEI, MCC+MNC+MMEGI+MMEC, or MMEGI+MMEC determines MME, or, eNodeB carries out the reselection procedure of MME owing to can not find corresponding GUMMEI, if there is the MME corresponding with MCC+MNC+MMEGI+MMEC or MMEGI+MMEC, then select this MME, the GUMMEI that GUMMEI and the UE of this MME carries is consistent or MMEGI+MMEC is corresponding unanimously.If there is no corresponding with MCC+MNC+MMEGI+MMEC or MMEGI+MMEC MME then eNodeB reselects MME.If GUMMEI is the GUMMEI mapped, then eNodeB according to the MCC+MNC+MMEC in GUMMEI or only determines MME according to MMEC, it is specially, if there is MME, MCC, MNC, MMEC (being mapped by NRI) that the MCC of this MME, MNC, MMEC and UE carry is consistent or configures optional, for instance: eNodeB configuring MME C or NRI certain MME corresponding, then select this MME, otherwise, one MME of reselection procedure.

Or, if UE is in accessing SAE process, according to the UE mark that will carry, as by TIN (TemporaryIdentityusedinNextupdate, next update needs the temporary mark used) identify the mark that will carry, if TIN=" P-TMSI ", representing to access next time needs to carry the mark after P-TMSI/oldRAI maps, if TIN=" GUTI ", represent that next time accesses the mark carrying SAE, if TIN=" RAT-relatedTMSI ", represent and access that RAT next time just with the TMSI of that RAT distribution.If during TIN=" P-TMSI " of therefore UE, UE can access network at the GUMMEI after RRC part does not carry mapping, but carry S-TMSI in RRC part and (be made up of MMEC and M-TMSI, actual mapping by NRI and RAC and part P-TMSI forms) access network, such eNodeB will not obtain MMEGI, eNodeB can select MME according to MMEC therein (being mapped by NRI).Certainly, if there is MOCN, eNodeB digs up the roots and selects MME according to the MMEC in S-TMSI, also can select MME according to PLMN-id (SelectedPLMN-id) information selected, namely eNodeB selects Mobility Management Entity MME according to PLMN-id and MMEGI and the MMEC selected, if the PLMN-id of the selection that the MCC, MNC and the UE that are specially in the GUMMEI of MME carry is identical, the MMEC that MMEC and UE carries simultaneously is identical, then described network side node selects this MME.Additionally, UE also needs to the GUTI after Non-Access Stratum (NAS, NonAccessStratum) part carries mapping, such MME could obtain context to oldSGSN.Or, eNodeB configures LAC list, when eNodeB finds that MMEGI belongs to this one of LAC list or this LAC list, then select the MME of correspondence, such as when eNodeB finds that the UE GUMMEI carried is consistent with the mark being arranged in certain corresponding for eNodeB MME, then select the MME of correspondence, otherwise, without corresponding MME, carry out new MME and select；Wherein, the actual mapping by PLMN-id+LAC+NRI of the GUMMEI mark of this MME forms.Such as, the Pool of Pool and the 2G/3G of SAE is overlapping, there is MME/SGSN and unify node in this Pool, RAI1 is there is under this Pool of 2G/3G, RAI2, RAI3, three Route Area (RA, RoutingArea), when UE and accesses from 2G/3G Network Mobility to SAE network, UE uses the oldRAI/P-TMSI GUTI mapped to access, the eNodeB information according to configuration, find that UE uses the GUTI mapped, and the RA before mapping belongs to RAI1, RAI2, RAI3 one of them, then eNodeB selects corresponding MME according to MCC+MNC+MMEC (being mapped by NRI) or MMEC, need not MCC, MNC, MMEGI, MMEC unanimously just selects MME.Without meeting the corresponding MME that above-mentioned situation describes, for instance be not belonging to one of RAI of configuration, then reselect a MME.

Wherein, eNodeB configures LAC list and can adopt following methods.

MME passes through S1 configuration response (S1SETUPRESPONSE) message or MME config update (CONFIGURATIONUPDATE) message, the LAC of configuration is mapped to GUMMEI and is sent to eNodeB, eNodeB notes down this S1SETUPRESPONSE message or MMECONFIGURATIONUPDATE message, preserve to configuration information, namely in LAC list.Below citing is illustrated.

Such as, in Fig. 8, Pool1 includes SGSNPool and MMEPool, SGSN1, SGSN2, MME1, MME2 etc. are the node in Pool1, Pool1 there is also MME/SGSN and unify node SGSN3/MME3, LAC1 in Fig. 8, LAC2, LAC3 and LAC4 etc. are then the Location Area Code in 2G/3G network respectively, and TA1, TA2, TA3 and TA4 etc. are then the tracking area of SAE network respectively；Wherein, from SAE system perspective, the GUMMEI of unification node SGSN3/MME3 is PLMN-id (PLMNIdentity, PLMN identifies, wherein, PLMN-id is MCC+MNC)+MMEGI (i.e. the id of MMEPool)+MMEC (i.e. the id of MME3 in MMEPool), in order to allow the SGSN being registered to this unification node, namely the UE on SGSN3 also can select that this unification node when entering SAE region from 2G/3G region, all LAC in this SGSN3Pool can be also configured in eNodeB by MME3, forming LAC list, method is as follows:

For each LAC in Pool1, MME3 forms a GUMMEI respectively, this GUMMEI corresponds to PLMN-id+LAC+NRI, and (namely unification node is configured to SGSN, i.e. NRI on SGSN3, the MMEC that general and this unification node is configured on MME is equal), therefore, MME3 can form several GUMMEI.GUMMEI after real GUMMEI (mark in SAE) and mapping (is had several by this MME3, the corresponding GUMMEI of each LAC in Pool1) list be sent to eNodeB by S1SETUPRESPONSE message or MMECONFIGURATIONUPDATE message, eNodeB preserves this GUMMEI list (or perhaps LAC list, because each LAC suffers from the GUMMEI of correspondence), thus working as the UE being registered to SGSN3 LAC from Pool1, such as LAC1 or LAC2 etc. enter into E-UTRAN region, when accessing eNodeB, it is designated GUMMEI (being mapped by PLMN-id+LAC1+NRI) due to what UE access was carried, therefore this eNodeB can pass through query configuration, namely by the list of the GUMMEI after the real GUMMEI preserved before inquiring about and mapping, learn this GUMMEI correspondence MME3, then this MME3 node is directly selected.

Configuration as above method has the disadvantage that, due to unification node and ISR demand, may there is substantial amounts of mapping GUMMEI in one MME, because each LAC in Pool can be correspondingly formed a MMEGI by MME, even MME can be also that each LAC in adjacent S GSNPool is also respectively configured a MMEGI to meet the demand of ISR, therefore, in S1SETUPRESPONSE message or MMECONFIGURATIONUPDATE message, it may be necessary to carry substantial amounts of GUMMEI.

Current S1SETUPRESPONSE message and MMECONFIGURATIONUPDATE message carry GUMMEI list by following method, referring to table one, wherein, for convenience, eliminate other cells in table.

Table one:

IE/Group Name (information element name)	......
		Served GUMMEIs (service GUMMEI list)	......
> GUMMEI (GUMMEI value)	......

As shown in Table 1, S1SETUPRESPONSE message or complete GUMMEI list can be carried in MMECONFIGURATIONUPDATE message, i.e. service GUMMEI list.It addition, as SGSNPool increase/deletion/amendment LAC, all of GUMMEI list can be resend to each eNodeB by MME by MMECONFIGURATIONUPDATE message.Owing to GUMMEI list is relatively big, and eNodeB quantity is more, so more information will necessarily be caused to transmit in a network, increases the signaling traffic in network, has namely increased the weight of the expense of network.Such as, if a Pool exists 10 MME, 200 eNodeB, so, when relevant LAC change, then needing each MME to send MMECONFIGURATIONUPDATE message to each eNodeB, this also implies that and transmits having 2000 CONFIGURATIONUPDATE message on S1 interface, further, each message comprises all of GUMMEI list (renewal and do not update be required for send).In order to avoid this situation, the embodiment of the present invention can also adopt following collocation method.

(1) in order to reduce the size of the configuration message such as S1SETUPRESPONSE message or MMECONFIGURATIONUPDATE message, make in the configuration message such as S1SETUPRESPONSE message or MMECONFIGURATIONUPDATE message without carrying substantial amounts of GUMMEI list, GUMMEI can be decomposed, then the list each ingredient of GUMMEI formed respectively is transmitted, namely the configuration message about LAC list that MME sends is to eNodeB, described about the configuration message of LAC list is carried PLMN-id list, MMEGI list and MMEC list, specific as follows:

Due to for each LAC in Pool, MME can form a corresponding GUMMEI, so, eNodeB configures LAC list and actually can also regard as, eNodeB configures GUMMEI list, owing to GUMMEI is made up of PLMN-id+MMEGI+MMEC, if so GUMMEI is formed by 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 is also identical, therefore, there is a large amount of identical content in GUMMEIlist.Thus, as shown in Table 2, GUMMEI list can be changed into the form of PLMN-id (i.e. PLMNIdentity in table)/PLMN-idlist+MMEGIlist+MMEC/MMEClist, wherein, PLMN-idlist refers to PLMN-id list, MMEGIlist refers to MMEG list, and MMEClist refers to MMEC list；

Table two:

Under normal circumstances, the value of PLMN-id and the MMEC in GUMMEI list is identical, only the value of MMEGI is different, the form that therefore GUMMEI list makes into PLMN-id+MMEGIlist+MMEC is transmitted saving the transmission of PLMN-id and the MMEC of a large amount of repetition, certainly when supporting many PLMN, PLMN-id can also be readily modified as PLMN-idlist, and in like manner, MMEC can also change MMEClist mode into.When, after the list after eNodeB receives this change, preserving and be combined into GUMMEI list according to information such as PLMN-id, MMEGIlist and the MMEC in table voluntarily, thus completing the configuration to LAC list.

Such as, PLMN-id is currently 3 byte, MMEGI be 2 byte, MMEC is 1 byte.If a MMEPool supports that 3 PLMN, MMEPool need a configuration 100 MMEGI and MMEC, wherein, 100 MMEGI include the MMEGI after 1 real MMEGI and 99 LAC maps).If that by original collocation method, the size of GUMMEIlist is: 3*100* (3+2+1)=1800byte.And by this method, present GUMMEIlist is made up of PLMN-idlist and MMEGIlist and MMEClist, and what take is sized to: 3*3 (PLMN-list)+100*2 (MMEGIlist)+1*1 (MMEClist)=210byte.It can be seen that existing GUMMEIlist takes up room and greatly reduces.

(2) in order to solve when LAC or GUMMEI change, the problem that MME needs to send all GUMMEI lists to eNodeB and causes too much information to transmit in a network, the embodiment of the present invention proposes, when LAC or GUMMEI changes, MME sends instruction message to eNodeB, described instruction message instruction eNodeB interpolation/amendment/delete the GUMMEI in LAC list, in the MME MMECONFIGURATIONUPDATE message sent to eNodeB, such as carry an instruction, instruction shows the change conditions of LAC or GUMMEI, namely it is add one or several GUMMEI or have modified GUMMEI or delete GUMMEI etc..Amended MMECONFIGURATIONUPDATE message may refer to table three；

Table three:

It is of course also possible to directly indicate interpolation in the message or delete or amendment GUMMEI, it is also sent to eNodeB without allowing the MME GUMMEI other not changed, for instance can be such that

When MME needs to add a GUMMEI, then can send MMECONFIGURATIONUPDATE (newGUMMEI, behavior='add') message is to eNodeB, wherein, " newGUMMEI " represents the mark (ID of the GUMMEI needing interpolation, Identity), " behavior='add' " then indicates that needs add GUMMEI in original LAC list, " behavior " is a kind of information element (IE, InformationElement), its value shows concrete action, so, when eNodeB receives this MMECONFIGURATIONUPDATE (newGUMMEI, behavior='add') after message, in original LAC list, just add a GUMMEI；

When MME to delete a GUMMEI, then can send MMECONFIGURATIONUPDATE (GUMMEI, behavior='delete') message is to eNodeB, wherein, " GUMMEI " represents the ID of the GUMMEI deleted in original LAC list, " behavior='delete ' " represents to be needed to delete GUMMEI, after eNodeB receives this message, deletes corresponding GUMMEI according to this message in original LAC list；

When MME to revise a GUMMEI, then can send MMECONFIGURATIONUPDATE (newGUMMEI, GUMMEI, behavior='modify') message is to eNodeB, wherein, " behavior='modify' " represents to be needed to revise the GUMMEI in original LAC list, " GUMMEI " represents the ID of the GUMMEI needing amendment, " newGUMMEI " then indicates that the ID of GUMMEI needing to make into, and namely the ID of GUMMEI that " GUMMEI " is corresponding in original LAC list to change " newGUMMEI " into.

Certainly, " behavior " such IE can not also be carried, such as can pass through " updatedGUMMEI " and " newGUMMEI " and show action, namely " GUMMEI is updated " and " new GUMMEI ", wherein, " updatedGUMMEI " represents that to update original GUMMEI, newGUMMEI represents the GUMMEI needing interpolation new；So, if updatedGUMMEI void value or be not carried, and newGUMMEI=5, then it represents that will add an id is the GUMMEI of 5；If updatedGUMMEI=5, and newGUMMEI void value or be not carried, represent and will delete that GUMMEI that id is 5；If updatedGUMMEI=5, and newGUMMEI=10, represent that to revise GUMMEI that GUMMEI equal to 5 changes 10 into.

(3) certain, in order to reduce when LAC or GUMMEI change further, MME is sent to the quantity of the message of eNodeB, reduces the signaling traffic between MME and eNodeB, it is also possible to take another kind of method, as follows:

All of configuration information is all concentrated on a preset Centroid, this Centroid can be preset eNodeB, can also be preset MME etc., this Centroid has all MME configuration informations, if the configuration information of certain MME changes, then sent configuration message by this Centroid to all of eNodeB, such as send S1SETUPRESPONSE message or MMECONFIGURATIONUPDATE message.Therefore, when this Centroid needs to send configuration information to eNodeB, the configuration information of all MME will be sent.GUMMEIlist in such as S1SETUPRESPONSE message or MMECONFIGURATIONUPDATE message is not the GUMMEIlist of a MME, but the GUMMElist of all MME, certainly, in order to realize the method, needing S1SETUPREPONSE message is modified, amended S1SETUPREPONSE message is as shown in Table 4；

Table four:

" GUMMEI " in table is GUMMEI real for each MME, the GUMMEI that each MME only one of which is real, the GUMMEI after mapping it is left out at this, MME uses this real GUMMEI as unique mark, the information of all of MME is concentrated in together, form MMElist, each MME in this MMElist has some specific configuration information, the name of such as MME, ability, also has GUMMEIlist of mapping etc., wherein, GUMMEIlist is probably (PLMN-id+MMEGI+MMEC) list, it is also likely to be PLMN-idlist+MMEGIlist+MMEClist, it is likely to the GUMMEIlist being absent from this mapping.

In a word, it is exactly configured message by this Centroid by one to provide the configuration information of all MME in this MMEPool to the eNodeB in Pool, so, when LAC or GUMMEI change, just have only to this Centroid and send a MMECONFIGURATIONUPDATE message to each eNodeB, send to each eNodeB without each MME, thus decreasing the quantity of the message transmitted in network.Such as there are 10 MME in MMEPool, 200 eNodeB, when LAC change, just have only to this Centroid and send out the total configuration message about configuration change to 200 eNodeB, message number only has 200, certainly, before this, MME is likely to also need to send the configuration message of self to this Centroid.

(1) (2) (3) three kinds of methods can be independently from above, can also in conjunction with use, certainly, can more optimize in conjunction with use, as (1) method and (2) method combine, so, when there being 10 LAC to be added, MME just only need to update the information of these 10 LAC, then the MMEGI+MMEC after PLMN-idlist+10 LAC maps is sent to eNodeB, when not supporting the core net node of multiple operator, the size of this message being sent to eNodeB just only has 3+20+1=24byte.Otherwise, if only using (1) method, although reduce the size of of message, but the quantity of message is again without change, namely needs for sending all GUMMEI information (including not updating) to eNodeB；If only using (2) method, although the quantity of message reduces to some extent, but the size of message is still 6*10=60byte, it is clear that the above-mentioned size by the message after (1) method and the combination of (2) method of ratio, namely " 24byte " is many greatly.Certainly (3) method can also combine with (1) method or (2) method, even all combines, does not repeat them here.

It should be noted that, the present embodiment is that eNodeB illustrates for network side node, described network side node can also be described Centroid, that is, in the present embodiment, the operation performed by eNodeB can also be completed by this Centroid, such as this Centroid can also as the node selecting CN node, namely, this Centroid is connected with each eNodeB, when UE accesses eNodeB, eNodeB does not select CN node, but sends the message to this Centroid, CN node is selected, for instance MME by this Centroid.So, just have only to the configuration information of MME is configured to this Centroid, without being sent to eNodeB, that is, each MME is when S1 sets up or configuration information changes, namely during LAC or GUMMEI change, it is only necessary to carry out information alternately with this Centroid.Such as there are 10 MME in MMEPool, 200 eNodeB, when LAC changes, 10 MME have only to send the configuration message about configuration change to this Centroid, message number only has 10, without the configuration message sent to 200 eNodeB about configuration change, greatly reduce the quantity that in network, information transmits.

The beneficial effect of embodiment one: mark when embodiment one is by accessing for UE makes a distinction, obtain the information of UE mark, confirm that this information is that the information of network allocation or network are to the information after the information MAP of this UE, and according to above-mentioned differentiation, suitable network node is selected, it is to avoid UE cannot be linked into corresponding CN node owing to changing RAT for UE.

Embodiment two, method described by embodiment one is all when UE carries 2G/3G mark access SAE/LTE network, tracking area (the TA of registration it is not at according to the UE community being currently stationed, TrackingArea) situation in carries out accessing, in the method described by embodiment one, if the community that UE is currently stationed is in the TA of registration, then complete the NAS part in (RRCConnectionSetupComplete) message in RRC connection establishment, the NAS part (the NAS part all claiming RRC connection setup complete message below is NAS message) of such as TAURequest message can not carry UE mark (UE-id), such as the information such as GUTI or P-TMSI or IMSI, namely whether UE can determine whether carry UE mark in NAS message according to the TA being currently accessed in the TA list (TAlist) of self.

That is, if NAS message is carried UE mark, general then think the UE community being currently stationed be not at registration TA in, and actually, if carrying UE mark in NAS message, so can also access according to the situation that the UE community being currently stationed is in the TA of registration, the such as NAS message when the mark that UE carries 2G/3G network accesses SAE/LTE network can only be attachment request (AttachRequest) message or tracing section updating request (TAURequest) message, so, as long as the two message always carries UE mark, even if the MME then selected does not have UE context, the MME of this selection can also pass through UE mark and find old node to obtain UE context, or obtain UE context to HSS.For this, present embodiments provide another kind of cut-in method.

For convenience, below the community that UE is currently stationed is not at registration TA in this situation call TAnotregisteredcase, otherwise, if the community that UE is currently stationed is in the TA of registration, be then called TAregisteredcase.It should be noted that, in order to describe the technical scheme that the present embodiment provides better, hereinafter TAregisteredcase and TAnotregisteredcase technology being briefly described, TARegisteredcase and TAnotregisteredcase is the technology during UE mark access SAE carrying SAE distribution.

When UE enter a SAEPool and use SAE distribute temporary mark initiate access time, UE judges whether the community being currently accessed belongs to the registration area of UE, namely UE detects whether the community self being currently stationed is in the TA of registration, if, then the UE of idle (idle) pattern accesses in RRC connection establishment request (RRCConnectionRequest) message that SAE/LTE network is initiated and carries S-TMSI, owing to UE does not necessarily move out original Pool region in this case, therefore, eNodeB can be simply selected to original MME (in MOCN situation by the MMEC in S-TMSI, also to combine according to the PLMN-id information of the UE selection carried and select MME), after receiving the eNodeB RRC connection establishment message carrying S-TMSI returned, in order to reduce the size of message, save the bandwidth taken, it is sent in the NAS message in the RRC connection setup complete message of eNodeB at UE subsequently and can not carry UE mark, RRC part in RRC connection setup complete message does not carry GUMMEI yet, after eNodeB have selected MME, eNodeB sends initial UE message to the MME chosen, then MME obtains the context of UE according to S-TMSI, wherein, initial UE message includes the information such as the NAS message in S-TMSI and the RRC connection setup complete message in the UE RRC connection establishment initiated request；If not, namely UE detect the community self being currently stationed be not at registration TA in time, then the UE of idle idle pattern accesses in the RRC connection establishment request message that SAE/LTE network is initiated and carries a random number (RandomID), then the eNodeB RRC connection establishment message carrying random number returned is received, it is likely to does not move out original Pool region owing to UE in this case is likely to move out original Pool region, so needing to carry the mark of UE in UE NAS message in the RRC connection setup complete message being sent to eNodeB afterwards, RRC in RRC connection setup complete message part carries GUMMEI simultaneously, such eNodeB just can search the MME of correspondence (in MOCN situation by GUMMEI, MMEGroupID and the MMEC that eNodeB is in PLMN-id and the GUMMEI according to the UE selection carried selects MME's), if there is corresponding MME (MME originally), then it is simply selected to original MME, if there is no corresponding MME, then illustrate that UE has changed Pool, so eNodeB selects a new MME, then initial UE message is retransmited to the MME chosen, the MME chosen by this obtains the context of UE, wherein, initial UE message includes the information such as NAS message.Can referring to Fig. 9 and Figure 10, Fig. 9 is that UE uses TAregisteredcase to access the method flow diagram of SAE/LTE network, and Figure 10 is that UE uses TAnotregisteredcase to access the method flow diagram of SAE/LTE network.

The cut-in method that the present embodiment provides is: when UE carries the mark access SAE system of 2G/3G, UE is first by mark form that the identity map of 2G/3G is SAE, then according to TAregisteredcase accesses, namely UE carries the S-TMSI of mapping in RRC connection establishment request (RRCConnectionRequest) message initiated, and the RRC part in RRC connection setup complete message subsequently does not carry GUMMEI.And in the NAS message in RRC connection setup complete message, can always carry UE mark, at this moment eNodeB can not carry S-TMSI in the initial UE message (Article 1 InitialUEMessage) sent to MME.Can also be, UE judges whether the community being currently accessed is in the TA of registration, if it is, always do not carry UE mark in the NAS message in RRC connection setup complete message, if it is not, then carry UE mark in NAS message in RRC connection setup complete message.

Certainly, before UE accesses System Architecture Evolution network SAE, it is that SAE distributes or the carrying out mapped judges that UE can also dock the UE mark of fashionable use, if described UE mark is to map, just perform the action described in above method, namely perform UE and ask message is carried the S-TMSI of mapping in the RRC connection establishment being sent to eNodeB, the RRC connection setup complete message be sent to eNodeB does not carry the step of GUMMEI；Otherwise, if described UE mark is SAE distribution, then judge whether the UE region accessed belongs to the registration area of UE, if the region that UE accesses belongs to the registration area of UE, then perform TAregisteredcase to access, if the region that UE accesses is not belonging to the registration area of UE, then performs TAnotregisteredcase and access, can referring to the associated description of TAregisteredcase and TAnotregisteredcase in the present embodiment, no longer burdensome at this.

It should be noted that, what need to distinguish the request of RRC connection establishment message carries due to eNodeB is S-TMSI or random number, it is thus desirable to definition one mark is in S-TMSI and random number, such as by this mark called after DistinguishingMark, define it and be sized to 8bit, if the number on 8bit is 1 entirely, it is determined that what RRC connection establishment request message was carried is random number, if the number on 8bit is not all 1, it is determined that RRC connection establishment request message is carried is S-TMSI.This DistinguishingMark is positioned at the MMEC part of S-TMSI and the front 8bit of random number.

Due to UE carry the mark of mapping access SAE time, the MMEC part in S-TMSI is to be mapped by NRI, and NRI is probably complete 1, and such eNodeB can think that what receive is random number by mistake, accordingly, it would be desirable to defining NRI can not be complete 1.

Certainly, whether the community being currently accessed can also be belonged to the registration area of UE by UE judges, or need not be that SAE distributes or the carrying out mapped judges to self-contained UE mark, but always use TARegisteredCase, namely ask message always carries S-TMSI in the RRC connection establishment being sent to eNodeB, then no matter under what circumstances, NAS message in RRC connection setup complete message always carries UE mark, and ask the S-TMSI carried in message to be used only to select MME for eNodeB in RRC connection establishment, without on S1 interface subsequently by S-TMSI band, namely eNodeB does not carry S-TMSI information in the MME initial UE message sent, such that it is able to reduce the uninterrupted of message, save the bandwidth taken, but, the deficiency of the method is in that, when UE changes Pool, if new Pool there is also the MMEC of identical numbering, then eNodeB directly selects this to have the MME corresponding to the MMEC of identical numbering in new Pool, without selecting a new MME by principles such as load balancing (LoadBalancing).Or, TAnotregisteredcase can also be always used to access SAE/LTE network, namely UE asks always to carry random number in message in the RRC connection establishment being sent to eNodeB, RRC part at RRC connection setup complete message subsequently carries GUMMEI, the NAS message of RRC connection setup complete message is carried UE mark, but so the process of UE initiation service request (ServiceRequest) will not be too fast, because service request information generally understands limited length, in order to initiate as soon as possible to access.

Need to illustrating it is be simply more than MME with RAN node for eNodeB, CN node be that example illustrates, this RAN node can also be have the miscellaneous equipment of similar functions with eNodeB, and CN node can also be have to have the miscellaneous equipment of similar functions with MME.

The beneficial effect of embodiment two: embodiment two asks to carry S-TMSI in message by the UE RRC connection establishment initiated, then passing through S-TMSI is that UE selects suitable CN node, avoid UE and cannot be linked into the situation of corresponding CN node owing to changing RAT, meanwhile, the present embodiment by not carrying the methods such as GUMMEI in RRC connection setup complete message, reduce the uninterrupted of message, save the bandwidth taken.

Embodiment three, the present embodiment is by arranging differentiation LAC and MMEGI, for instance the numerical value arranging the bit position corresponding from MMEGI, the bit position in LAC is different, it is possible to distinguish LAC and MMEGI.The present embodiment proposes to access MME as UE by GUTI, and concrete access way can include attachment attach or TAU.If there is UE context (UEContext) in MME, then MME finds UE by GUTI, otherwise, MME finds oldMME by the GUMMEI in GUTI, such as can pass through domain name analysis system (DNS, DomainNameSystem) oldMME is searched, and send context request (ContextRequest) to oldMME, this context request comprises GUTI or sends identification request (IdentificationRequest), this identification request comprises GUTI, oldMME finds UEContext by GUTI, the IMSI information etc. of return UEContext or UE gives MME.And the GUTI after UE is mapped by oldRAI/P-TMSI or TLLI accesses MME, MME or DNS and needs the differentiation according to the GUTI that GUTI such as SAE is UE distribution and the GUTI of mapping that network is UE distribution.As known, GUTI is the GUTI mapped, then reduction GUTI is the TLLI/oldRAI (if oldSGSN is 2GSGSN) of oldRAI/P-TMSI or 2G network.OldSGSN is found by oldRAI or by oldRAI and NRI, ContextRequest is sent to oldSGSN, this ContextRequest comprises oldRAI, P-TMSI or TLLI, or send checking request (IdentificationRequest), this IdentificationRequest comprises oldRAI, P-TMSI or TLLI.OldSGSN passes through oldRAI and P-TMSI, or oldGGSN finds UEcontext by TLLI, returns the IMSI information of UEContext or UE to MME.

Refer to Fig. 2, UE sends tracing section updating request, namely TAURequest message is to MME, this TAURequest message comprises GUTI, MME checks that GUTI is real GUTI, namely SAE network side distributes to the real GUTI of UE, or the GUTI after mapping, if real GUTI, then MME sends ContextRequest to oldMME, this ContextRequest carries (GUTI, completeTAURequestmessage) come to obtain context to oldMME, oldMME searches UEContext by GUTI, completeTAURequestmessage is the UE TAURequest message sent, if this message has integrity protection, then carry this message to oldMME, checked for integrity protection is carried out in order to oldMME, if be proved to be successful, then return UE context to newMME.If MME checks that GUTI is the GUTI after mapping, then MME sends ContextRequest (oldRAI, P-TMSIorTLLI), oldSGSN to oldSGSN and searches UEContext according to oldRAI and P-TMSI or TLLI.

Wherein, about safety integrity protection problem, when UE accesses SAE system by the GUTI after mapping, it is possible to adopt following several ways:

1., owing to oldSGSN does not have the integrity protection parameter of SAE, therefore MME can be that after mapping, GUTI does not send TAURequest message to oldSGSN according to GUTI.

Or

No matter whether GUTI is the mark after mapping to 2.MME, all the time old node is given, as oldSGSN sends the checking of TAURequest message calls, but this message is not verified by oldSGSN, return the information not being proved to be successful or not having checking to MME, MME is made to perform coupling of safety-relevant processes, if MME does not have UE context, that such as subsidiary whole world unique temporary identity (AdditionalGUTI) indicates is other MME, coupling of safety-relevant processes can be performed by other MME, or MME finds the UE context self preserved according to AdditionalGUTI, UE is carried out safety verification, or, MME initiates safety certification process to UE.

Or

3.UE carries AdditionalGUTI and just indicates UE to have UE context at the MME accessed, UE is carried out safety verification by the MME then accessed, if by safety verification, then in oldSGSN ContextRequest or IdentificationRequest sent, carry the UE information having verified that.

Or

If 4. AdditionalGUTI indicates other MME, then new MME obtains safe context to the AdditionalGUTI MME indicated, and UE is verified by new MME according to the safety information obtained；Or the MME that attachment request (AttachRequest) message or TAURequest message issue AdditionalGUTI instruction is verified by newMME.

Or

5., if UE carries the GUTI after mapping when accessing, the message such as TAURequest message or AttachRequest message are not carried out integrity protection by UE.

Or

6., if UE carries the GUTI after mapping when accessing, UE carries the SGSN P-TMSISignature field allocated it, and issues network, after MME receives, P-TMSISignature field is issued oldSGSN and carries out the checking of UE.If namely UE carries oldRAI/P-TMSI or the TLLI GUTI mapped and accesses SAE, then UE carries P-TMSISignature cell, and MME also carries P-TMSISignature cell to the oldSGSN ContextRequest message sent, and UE is verified by request oldSGSN.

Above safety problem is equally applicable to the GUTI after following UE carries mapping and accesses in the embodiment of SAE system or UE carries the oldRAI/P-TMSI (or TLLI) after mapping/P-TMSISignature and accesses in the embodiment of 2G/3G (MME and SGSN needs reversing of position).

Embodiment four, is different in that with embodiment three, GUTI is directly mapped by MME.GUTI is mapped or is reduced to oldRAI/P-TMSI (or TLLI)/P-TMSISignature or oldRAI/P-TMSI by the present embodiment MME, or P-TMSI therein can also be the form of TLLI, by the form of oldRAI/P-TMSI (or TLLI)/P-TMSISignature to old entity, such as oldMME or oldSGSN obtains context, if during oldMME, oldRAI/P-TMSI is mapped or is reduced to GUTI and obtains UEContext by oldMME；If oldSGSN, oldSGSN are directly according to oldRAI/P-TMSI (or TLLI), P-TMSISignature finds UEContext, can referring to Fig. 3.

Embodiment five, is different in that with embodiment three, in the present embodiment, it is judged that is after the GUTI mapped, is S4SGSN or Gn/GpSGSN according to corresponding oldSGSN, carries out different operations.It is that MME/S4-SGSN or Gn/GpSGSN carries out different operating that the present embodiment understands old node by access node.As the GUTI after UE is mapped by oldRAI/P-TMSI accesses MME, concrete access way can be Attach (attachment) or TAU mode.If MME knows that oldSGSN is the SGSN supporting S4, such as according to inquiry DNS, or it is that the interface based on GTP-v2 knows that oldSGSN is the SGSN supporting S4 according to its interface, so MME sends ContextRequest to oldSGSN, this ContextRequestGUTI comprises GUTI, or send IdentificationRequest, this IdentificationRequest comprises GUTI, by the oldSGSN differentiation according to GUTI, reduction GUTI is oldRAI, P-TMSI, or it is reduced to oldRAI, P-TMSITLLI, by oldRAI and P-TMSI, or oldRAI and/or TLLI finds UEcontext, return UEContext or IMSI etc. gives MME；If MME knows that oldSGSN is the SGSN supporting Gn/Gp, such as according to inquiry DNS, or it is that the interface based on GTP-v1 or v0 knows that oldSGSN is the SGSN supporting Gn/Gp according to its interface, such as the SGSNPre-R8SGSN before 3GPPR8 version definition, so MME reduction oldRAI/P-TMSI (or TLLI), SGSNContextRequest (oldRAI is sent to oldSGSN, P-TMSI or TLLI) or IdentificationRequest (oldRAI, P-TMSI or TLLI), oldSGSN finds UEcontext by oldRAI and P-TMSI (or TLLI), return to MME.

Refer to Fig. 4, if UE is when SAEAttach, temporary mark (the TIN that the next update of UE uses, TemporaryIdentityusedinNextupdate) P-TMSI or TLLI or UE last time it are set at the 2G/3G attachment removal Detach temporary mark used, UE needs to use oldRAI/P-TMSI, and wherein P-TMSI can also access SAE for the GUTI after TLLI mapping；MME receives the GUTI of this mapping, oldRAI/P-TMSI (or TLLI) can be directly reduced to or see that oldSGSN is S4SGSN or Gn/GpSGSN, if oldSGSN is S4SGSN, UE can pass through IdentificationRequest (GUTI, completeAttachRequestmessage) obtaining IMSI and context etc. to S4SGSN, GUTI is reduced to oldRAI/P-TMSI (or TLLI) and finds UE context and return IMSI etc. by S4SGSN.If oldSGSN is Gn/GpSGSN, MME uses the oldRAI/P-TMSI (or TLLI) after reduction to obtain information to oldSGSN, by identification request IdentificationRequest, this identification request is carried oldRAI/P-TMSI (or TLLI).Certainly, if there being the temporary mark accessing RAT distribution to exist, UE is used as accessing the temporary mark of RAT distribution when Attach, instruction regardless of TIN, the temporary mark of another RAT is then used without the temporary mark accessing RAT, if or the temporary mark of each RAT all without, then use IMSI access.If GUTI is real GUTI; so IdentificationRequest message is carried possibly from the UE complete AttachRequest message brought up; integrity protection checking is carried out for oldMME; if MME finds that GUTI is the GUTI mapped; so MME need not carry this AttachRequest message in the IdentificationRequest message issuing SGSN, and needs UE is carried out safety verification.

About safety-related problem; if AdditionalGUTI or AdditionalRAI/P-TMSI that UE carries indicates UE to there is context in this locality; then UE carries out the security process such as integrity protection checking in this locality; so; access entity; such as MME or SGSN; avoid the need for the old entity to TIN instruction; such as oldMME or oldSGSN; requirement carries out integrity protection checking etc.; if UE has been carried out integrity protection checking in this locality, then access entity carries UE in ContextRequest and has verified that information, and UE just need not be verified by old entity.UE accesses entity in this locality else if does not have UE context; when old entity and the access entity of TIN instruction are same RAT; so access entity and may require that UE is carried out integrity protection checking by old entity, for instance accessing entity and the message that UE sends is sent to old entity, old entity is verified.Otherwise access entity and can not require that UE is carried out security process by old entity, such as access entity and the message that UE sends is not sent to old entity, or, access entity inquiry old entity and UE is carried out security process, if but old entity cannot verify (as usual entity is not same RAT with access entity), then old entity return checking does not pass through or is not fully complete the information such as checking, it is desirable to accesses entity and voluntarily UE is verified.In addition, if that the TIN instruction of UE is " P-TMSI " or " TLLI ", then UE needs to carry P-TMSISignature when Attach or TAU/RAU accesses, in order to carry out the safety verification of UE, namely access entity to bring old entity UE is verified, that the TIN instruction of UE is " GUTI " else if, then UE needs to carry P-TMSISignature when accessing 2G/3G, because GUTI needs partial information and is mapped to P-TMSISignature.

Embodiment six, is different in that with embodiment three, and in embodiment three, that UE is accessed by GUTI is MME, and in the present embodiment, that UE carries that oldRAI/P-TMSI/P-TMSISignature accesses is SGSN, and wherein P-TMSI may also be TLLI.OldMME or oldSGSN is found according to real oldRAI/P-TMSI (or TLLI)/P-TMSISignature is different from the different 1bit such as MMEGI and LAC of the mark after mapping when UE carries oldRAI/P-TMSI (or TLLI)/P-TMSISignature access SGSN, SGSN or DNS.SGSN can obtain context by oldRAI/P-TMSI/P-TMSISignature form to old entity all the time, if old entity is MME, SGSN sends SGSNContextRequest to oldMME, this ContextRequest comprises oldRAI, P-TMSI/TLLI, P-TMSISignature, oldMME recovers GUTI, find UEContext, return UEContext, return EPSContext or 2G/3GContext according to interface or ContextRequest content.

Refer to Fig. 5, UE asks message by sending RAU, namely oldRAI is passed through, P-TMSI/TLLI, P-TMSISignature accesses SGSN, if UE uses the GUTI oldRAI mapped, P-TMSI/TLLI, P-TMSISignature accesses, so SGSN finds oldMME address, ContextRequest is sent to oldMME, this ContextRequest carries (oldRAI, P-TMSI/TLLI, P-TMSISignature) message, oldMME is according to oldRAI, P-TMSI/TLLI, P-TMSISignature reduces GUTI, find UE context and return UEContext.Additionally, due to oldMME does not have P-TMSISignature information, therefore, it is verified UE adopting following methods:

1.OldMME carries UE safety in the ContextResponse returned and does not verify information, for instance carry ' the Cause value of P-TMSISignaturemismatch' so that SGSN verifies UE again.

2. or, if SGSN does not have UE context and SGSN to understand the oldRAI of TIN instruction, P-TMSI/TLLI, old node corresponding for P-TMSISignature is oldMME, then UE is always verified by SGSN, and carry " MSValidated " information to the oldMME ContextRequest sent, represent that UE has passed through checking.If SGSN has UE context, wherein, UEContext can be found by AdditionalRAI/P-TMSI, then SGSN verifies UE in advance, if be proved to be successful, then carrying " MSValidated " information to the oldMME ContextRequest sent, representing that UE has passed through checking.

Embodiment seven, is different in that with embodiment six, in embodiment six, oldMME oldRAI/P-TMSI/P-TMSISignature is reduced into GUTI, and wherein P-TMSI can be TLLI.In the present embodiment, when old entity is oldMME, SGSN oldRAI/P-TMSI (or TLLI)/P-TMSISignature is reduced into GUTI.Referring to Fig. 6, SGSN understanding old entity is MME or SGSN, if old entity is MME, then S4SGSN recovers GUTI, sends ContextRequest (GUTI), oldMME to oldMME and finds UEContext according to GUTI, returns UEContext.

Safety problem is with embodiment three to six, if there is UE context SGSN this locality, verifies P-TMSISignature, without UE context and find old entity correspondence MME, then SGSN always initiates security process and SGSN reduction GUTI to UE, asks UE context to oldMME.

It is the mark after original temporary mark or mapping that access node oneself can distinguish temporary mark, it is also possible to by DNS, DNS feed back after analyzing whether this temporary mark of access node is the mark after mapping.If the old node address of access node and DNS translation is wrong, then, after the old node after translation receives ContextRequest, continues to search for real old node, relay the message to real old node.

In addition, in prior art, UE is likely to also to carry AdditionalTMSI (subsidiary temporary mark), namely UE carries AdditionalGUTI when accessing SAE, AdditionaloldRAI/P-TMSI is carried when accessing 2G/3G, wherein P-TMSI may also be TLLI, the effect of this AdditionalTMSI is used to find the UEContext that may be present accessed in RAT entity as far as possible, and use the TIN temporary mark indicated to obtain context etc., so can directly merge the context of acquisition to the UEContext in this RAT entity, otherwise access RAT and need according to the IMSI information in the context obtained inquires about whether this RAT entity exists UEContext again, then remerge and cause complexity.Can carry in this AdditionalTMSI situation actually below, to save interface-free resources: TAU or RAU in periodic location update (PeriodicTAU or PeriodicRAU) or handoff procedure；Or the temporary mark of TIN instruction is consistent with Additional temporary mark, i.e. the temporary mark accessing RAT exactly of TIN instruction；Or UE exist in Attach process access RAT temporary mark time.

Adopt above example of the present invention, specify that the process to temporary mark of each node.It is achieved that

GUTI after real GUTI and mapping distinguishes to some extent；OldRAI/P-TMSI (or TLLI) after real oldRAI/P-TMSI (or TLLI) and mapping also distinguishes to some extent.As arranged a bit position in LAC and MMEGI, LAC is always 0, MMEGI and is always 1.

Know that UE uses oldRAI/P-TMSI to access when UE uses the oldRAI/P-TMSI GUTI mapped to access SAE, eNodeB by differentiation, then select MME corresponding for NRI as far as possible；Or eNodeB is by finding whether this LAC has configuration, decides whether select NRI correspondence MME or reselect MME.

GUTI after UE is mapped by oldRAI/P-TMSI accesses MME, it is the GUTI mapped that MME understands this GUTI, reduction oldRAI/P-TMSI/TLLI, oldSGSN is found by oldRAI and NRI, sending ContextRequest to oldSGSN, this ContextRequest carries (oldRAI, P-TMSI/TLLI), oldSGSN finds UEcontext by oldRAI and P-TMSI/TLLI, returns to MME.

Or, GUTI after UE is mapped by oldRAI/P-TMSI accesses MME, MME, and to understand this GUTI be that to inquire about oldSGSN be S4SGSN or Gn/GpSGSN to GUTI, the MME mapped.If oldSGSN is S4SGSN, so MME sends ContextRequest (GUTI) to oldSGSN, namely this ContextRequest carries GUTI, or send IdentificationRequest, oldSGSN reduction GUTI is oldRAI, P-TMSI/TLLI, finds UEcontext by oldRAI and P-TMSI/TLLI, returns to MME；If oldSGSN is Gn/GpSGSN, so MME reduction oldRAI/P-TMSI/TLLI, ContextRequest is sent to oldSGSN, this ContextRequest carries (oldRAI, P-TMSI/TLLI), oldSGSN finds UEcontext by oldRAI and P-TMSI/TLLI, returns to MME.

AdditionalTMSI can not need when the temporary mark of TAU/RAU, PeriodicTAU/RAU, TIN instruction switched in HO is consistent with Additional temporary mark or when UE there is the temporary mark of access RAT in Attach process.

When MME and the SGSN of Combined node belongs to different PLMN, or when MME and the SGSN of different PLMN sets up ISR, UE can pass through to carry two PLMN-id or configuration, allows RAN node choose the CN node of correspondence.

Being which RAT distribution by distinguishing the UE mark carried, RAN node or access node can do process suitable accordingly, it is prevented that select error node or send inconsistent parameter to corresponding node.

The embodiment of the present invention additionally provides a kind of method distributing Internet resources node for user equipment (UE), and the method includes:

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

Network side is that UE distributes Internet resources node according to the attribute mapping of this temporary mark.

Specifically, network side obtains the attribute mapping of the entrained temporary mark of user equipment (UE) is that network side judges that ID is after network side distribution or mapping.

Detailed implementation describes as follows:

When the network side that user equipment (UE) accesses is System Architecture Evolution network SAE, this network side obtains the attribute mapping of the entrained identity of user equipment (UE) specifically: the Mobility Management Entity group mark MMEGI that the evolution base station eNodeB of this SAE network judges in the unique Mobility Management Entity mark GUMMEI/ or described GUMMEI in the whole world that described UE carries is SAE distribution or mapping；

If described GUMMEI/ or MMEGI is SAE distribution, then network side is that UE distributes Internet resources node specifically according to the attribute mapping of described mark: eNodeB encodes MMEC according to GUMMEI or MMEGI and Mobility Management Entity and selects Mobility Management Entity MME；

If described GUMMEI or MMEGI maps, then network side is that UE distribution Internet resources node specifically eNodeB selects MME according to the Mobile Country Code MCC MCC in described GUMMEI, Mobile Network Code MNC and MMEC according to the attribute mapping of mark；Or eNodeB selects MME according to the MMEC in GUMMEI.

Or realize also by following manner:

When user equipment (UE) access network side be System Architecture Evolution network SAE time, network side obtain user equipment (UE) entrained identity attribute mapping specifically: the Mobility Management Entity MME of SAE network judge the described UE global unique temporary identity GUTI carried be SAE distribution or mapping；

If GUTI is SAE distribution, then network side is also include before UE distributes Internet resources node according to the attribute mapping of described mark, and MME GUTI takes the context of UE to old Mobility Management Entity oldMME；

If GUTI maps, then network side is also include before UE distributes Internet resources node according to the attribute mapping of mark, and MME is reduced into old Routing Area Identifier oldRAI/ packet TMSI P-TMSI described GUTI or is reduced into oldRAI/ logical links temporary mark TLLI；And take the context of UE to old service universal grouping wireless business supporting node oldSGSN with oldRAI/P-TMSI or oldRAI/TLLI.

The statement of correspondence embodiment of the method above, the embodiment of the present invention additionally provides a kind of user equipment (UE), and this UE includes, and when UE uses the GUTI after mapping to access SAE system, then access message is not done integrity protection.

Refer to Fig. 7, network side apparatus, including identity property acquisition module 701, use the temporary mark after mapping or real temporary mark, the mark of real temporary mark and network side distribution for distinguishing UE；This network side node can be wireless access network node.

Internet resources node distribution module 702, the attribute according to the temporary mark of above-mentioned UE, namely UE is identifying or the mark after mapping of network side distribution, distributes Internet resources node for UE.These Internet resources node bag MME or SGSN or CN node.

Through the above description of the embodiments, those skilled in the art is it can be understood that can add the mode of required hardware platform by software to the present invention and realize, naturally it is also possible to implement all through hardware.Based on such understanding, what background technology was contributed by technical scheme can embody with the form of software product in whole or in part, this computer software product can be stored in storage medium, such as ROM/RAM, magnetic disc, CD etc., including some instructions with so that a computer equipment (can be personal computer, server, or the network equipment etc.) perform the method described in some part of each embodiment of the present invention or embodiment.

The above is only the specific embodiment of the present invention; it should be pointed out that, for those skilled in the art, under the premise without departing from the principles of the invention; can also making some improvements and modifications, these improvements and modifications also should be regarded as protection scope of the present invention.

Claims (6)

1. the method accessed, it is characterised in that the method includes:

When user equipment (UE) accesses 2G/3G network, service universal grouping wireless business supporting node SGSN is according to the described UE old Routing Area Identifier oldRAI carried and packet TMSI P-TMSI/ logical links temporary mark TLLI, search corresponding old physical address, obtain the context of UE to old entity；

Described SGSN receives the context of the described UE that described old entity returns, wherein, described old entity is old Mobility Management Entity oldMME, the context of described UE is the described oldMME described oldRAI of reduction, P-TMSI/TLLI, it is whole world unique temporary identity GUTI with packet TMSI signature P-TMSIsignature, finds according to described GUTI.

2. the device for accessing, it is characterised in that including:

When user equipment (UE) accesses 2G/3G network, for the old Routing Area Identifier oldRAI carried according to described UE and packet TMSI P-TMSI/ logical links temporary mark TLLI, search corresponding old physical address, obtain the module of the context of UE to old entity；

For receiving the module of the context of the described UE that described old entity returns, wherein, described old entity is old Mobility Management Entity oldMME, the context of described UE is the described oldMME described oldRAI of reduction, P-TMSI/TLLI, it is whole world unique temporary identity GUTI with packet TMSI signature P-TMSIsignature, finds according to described GUTI.

3. the method accessed, it is characterised in that including:

Mobility Management Entity MME receives the service universal grouping wireless business supporting node SGSN context request sent, described context request carries old Routing Area Identifier oldRAI, packet TMSI P-TMSI/ logical links temporary mark TLLI, and packet TMSI signature P-TMSISignature；

Described MME, according to described oldRAI, P-TMSI/TLLI, and P-TMSISignature reduction whole world unique temporary identity GUTI, finds UE context according to described GUTI and returns described user equipment (UE) context to described SGSN.

4. the device for accessing, it is characterised in that including:

For making Mobility Management Entity MME receive the service universal grouping wireless business supporting node SGSN context request sent, described context request carries old Routing Area Identifier oldRAI, packet TMSI P-TMSI/ logical links temporary mark TLLI, and the module of packet TMSI signature P-TMSISignature；With

For making described MME according to described oldRAI, P-TMSI/TLLI, and P-TMSISignature reduction whole world unique temporary identity GUTI, find UE context according to described GUTI and return the module of described UE context to described SGSN.

5. the method accessed, it is characterised in that including:

When user equipment (UE) accesses 2G/3G network, service universal grouping wireless business supporting node SGSN is according to the described UE old Routing Area Identifier oldRAI carried and packet TMSI P-TMSI/ logical links temporary mark TLLI, search corresponding old physical address, context request is sent to old entity, described context request carries old Routing Area Identifier oldRAI, packet TMSI P-TMSI or logical links temporary mark TLLI, and packet TMSI signature P-TMSISignature；

Described old entity is Mobility Management Entity MME, described MME receives described context request the described oldRAI that reduces, P-TMSI/TLLI and packet TMSI signature P-TMSIsignature is whole world unique temporary identity GUTI, finds the context of described UE according to described GUTI and returns to described SGSN；

Described SGSN receives the context of the described UE that described old entity returns.

6. the system for accessing, it is characterised in that include service universal grouping wireless business supporting node SGSN and Mobility Management Entity MME, wherein,

When service universal grouping wireless business supporting node SGSN accesses 2G/3G network for user equipment (UE), according to the described UE old Routing Area Identifier oldRAI carried and packet TMSI P-TMSI/ logical links temporary mark TLLI, search corresponding old physical address, context request is sent to old entity, described context request carries old Routing Area Identifier oldRAI, packet TMSI P-TMSI/ logical links temporary mark TLLI, and packet TMSI signature P-TMSISignature；

Described old entity is Mobility Management Entity MME, described MME is used for receiving described context request the described oldRAI that reduces, P-TMSI/TLLI and packet TMSI signature P-TMSIsignature is whole world unique temporary identity GUTI, finds the context of described UE according to described GUTI and returns to described SGSN；

Described SGSN is additionally operable to receive the context of the described MME described UE returned.