CN102761855B - Access, obtain customer equipment context and the method and apparatus of customer equipment identification - Google Patents
Access, obtain customer equipment context and the method and apparatus of customer equipment identification Download PDFInfo
- Publication number
- CN102761855B CN102761855B CN201110241665.8A CN201110241665A CN102761855B CN 102761855 B CN102761855 B CN 102761855B CN 201110241665 A CN201110241665 A CN 201110241665A CN 102761855 B CN102761855 B CN 102761855B
- Authority
- CN
- China
- Prior art keywords
- old
- mme
- tmsi
- context
- guti
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 104
- 238000013507 mapping Methods 0.000 claims abstract description 58
- CSRZQMIRAZTJOY-UHFFFAOYSA-N trimethylsilyl iodide Substances C[Si](C)(C)I CSRZQMIRAZTJOY-UHFFFAOYSA-N 0.000 claims description 206
- 230000009467 reduction Effects 0.000 claims description 14
- 230000008569 process Effects 0.000 claims description 13
- 238000012795 verification Methods 0.000 claims description 10
- 239000000203 mixture Substances 0.000 claims description 5
- 238000004321 preservation Methods 0.000 claims description 2
- 238000004891 communication Methods 0.000 description 23
- ATJFFYVFTNAWJD-UHFFFAOYSA-N Tin Chemical compound [Sn] ATJFFYVFTNAWJD-UHFFFAOYSA-N 0.000 description 19
- 230000004044 response Effects 0.000 description 12
- 230000008859 change Effects 0.000 description 7
- 230000004069 differentiation Effects 0.000 description 7
- 238000005516 engineering process Methods 0.000 description 7
- 238000010586 diagram Methods 0.000 description 5
- 230000000737 periodic effect Effects 0.000 description 4
- 230000011664 signaling Effects 0.000 description 4
- 101000946191 Galerina sp Laccase-1 Proteins 0.000 description 3
- 230000009471 action Effects 0.000 description 3
- 210000004027 cell Anatomy 0.000 description 3
- 230000006870 function Effects 0.000 description 3
- 101100218337 Gibberella zeae (strain ATCC MYA-4620 / CBS 123657 / FGSC 9075 / NRRL 31084 / PH-1) aurL2 gene Proteins 0.000 description 2
- 101001088739 Homo sapiens Probable inactive ribonuclease-like protein 12 Proteins 0.000 description 2
- 101001099922 Homo sapiens Retinoic acid-induced protein 1 Proteins 0.000 description 2
- 101001100103 Homo sapiens Retinoic acid-induced protein 2 Proteins 0.000 description 2
- 101001100101 Homo sapiens Retinoic acid-induced protein 3 Proteins 0.000 description 2
- 101150017281 LAC2 gene Proteins 0.000 description 2
- 102100033988 Probable inactive ribonuclease-like protein 12 Human genes 0.000 description 2
- 102100038452 Retinoic acid-induced protein 2 Human genes 0.000 description 2
- 102100038453 Retinoic acid-induced protein 3 Human genes 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 2
- 230000008878 coupling Effects 0.000 description 2
- 238000010168 coupling process Methods 0.000 description 2
- 238000005859 coupling reaction Methods 0.000 description 2
- 238000012217 deletion Methods 0.000 description 2
- 230000037430 deletion Effects 0.000 description 2
- 230000006872 improvement Effects 0.000 description 2
- 230000007774 longterm Effects 0.000 description 2
- 238000013519 translation Methods 0.000 description 2
- 101100074137 Arabidopsis thaliana IRX12 gene Proteins 0.000 description 1
- 241001316028 Euphaedusa tau Species 0.000 description 1
- 101150081322 LAC3 gene Proteins 0.000 description 1
- 101150022713 LAC4 gene Proteins 0.000 description 1
- 101150114331 MME1 gene Proteins 0.000 description 1
- 101100020526 Pycnoporus cinnabarinus LCC3-1 gene Proteins 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 210000002230 centromere Anatomy 0.000 description 1
- 238000005034 decoration Methods 0.000 description 1
- 230000007423 decrease Effects 0.000 description 1
- 230000007812 deficiency Effects 0.000 description 1
- 235000013399 edible fruits Nutrition 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 239000004615 ingredient Substances 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000000149 penetrating effect Effects 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
- 239000011800 void material Substances 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/0005—Control or signalling for completing the hand-off
- H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
- H04W36/0022—Control or signalling for completing the hand-off for data sessions of end-to-end connection for transferring data sessions between adjacent core network technologies
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W36/00—Hand-off or reselection arrangements
- H04W36/0005—Control or signalling for completing the hand-off
- H04W36/0011—Control or signalling for completing the hand-off for data sessions of end-to-end connection
- H04W36/0033—Control or signalling for completing the hand-off for data sessions of end-to-end connection with transfer of context information
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
- H04W60/04—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration using triggered events
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W8/00—Network data management
- H04W8/02—Processing of mobility data, e.g. registration information at HLR [Home Location Register] or VLR [Visitor Location Register]; Transfer of mobility data, e.g. between HLR, VLR or external networks
- H04W8/08—Mobility data transfer
- H04W8/10—Mobility data transfer between location register and external networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
- H04W88/005—Data network PoA devices
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Databases & Information Systems (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
The embodiment of the present invention provides a kind of access, obtains customer equipment context and the method and apparatus of customer equipment identification.A kind of method of access, the method includes: during user equipment (UE) access system architecture evolution network SAE, and evolution base station eNodeB judges that the Mobility Management Entity group mark MMEGI in the whole world unique Mobility Management Entity mark GUMMEI or described GUMMEI that described UE carries is SAE distribution or maps.And access, obtain customer equipment context and the method and apparatus of customer equipment identification, the still mapping of network side distribution it is distinguished as by the temporary mark carried during to UE access network side, thus use different cut-in methods for different temporary marks, it is achieved the flexible Application to temporary mark.
Description
Technical field
The present invention relates to communication technical field, particularly relate to access, obtain customer equipment context and user
The method and apparatus of device identification.
Background technology
In existing communication network, there is traditional second filial generation (2G, Second Generation) and lead to
Communication network, the third generation (3G, 3rd Generation) communication network, and merged more advanced technology
Long Term Evolution (LTE, Long Term Evolution)/system architecture evolution (SAE, System
Architecture Evolution) network.Communication network is typically by wireless access network (RAN, Radio Access
Network) forming with core net (CN, Core Network), different communication networks can use difference
Wireless access technology (RAT, Radio Access Technology) enter CN, the most different communication
Network has the RAN of different RAN, such as 3G communication network and is referred to as universal land radio access web
(UTRAN, Universal Terrestrial Radio Access Network), the RAN of SAE communication network
It is referred to as E-UTRAN etc..
RAN is made up of RAN node, such as radio network controller (RNC, the Radio in UTRAN
Network Controller) and base station (NodeB);CN is then made up of CN node, such as UTRAN
In SGSN (Serving GPRS Support Node, Serving GPRS Support Node), or
Mobility Management Entity (MME, Mobility Management Entity) etc. in E-UTRAN.Its
In, the function of MME is that the mobile management of preservation subscriber equipment (UE, User Equipment) is upper and lower
Literary composition (Context), is called for short the context of UE, as UE identifies, and mobility management states, positional information
Deng.
In prior art, a RAN node can be routed to multiple CN node, i.e. RAN node can
Think that the UE being initially accessed selects to be routed on different CN nodes.One pond of these CN nodes composition
Territory (Pool), the CN node in the Pool in 2G/3G system, as SGSN with network resource identifier (NRI,
Network Resource Identifier) identify, the CN node in the Pool in SAE system is then to use
Unique Mobility Management Entity mark (GUMMEI) in the whole world identifies.
When UE is linked into communication network, communication network can distribute to mono-temporary mark of UE, such as
2G/3G system can allocation packets interim subscriber identity (P-TMSI, Packet Temporary Mobile
Subscriber Identity)/TMSI to UE, SAE system then can distribute the whole world unique temporary identity
(GUTI, Global Unique Temporary Identity) gives UE, and wherein, GUTI includes
GUMMEI.Owing to UE can move in different communication networks, so, at UE from former communication network
It is switched to new communications network, or when former CN node is switched to new CN node, needs to pass through NRI/
The temporary mark of GUMMEI and UE is searched former CN node and is obtained the context of UE, in order to permissible
It is switched fast.If the switching between different communication network, the RAT used due to them is different, institute
With when UE accesses new communications network from former communication network, in addition it is also necessary to map the RAT's of former communication network
Mark, the mark of the RAT being identified to new communications network of the oldest RAT accesses, and so, is only possible to look for
CN node in former communication network, is only possible to obtain the context of UE.
During realizing the present invention, inventor finds 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, after therefore mapping
The mark of RAT may corresponding CN node, it is possible to appear in new communications network selects less than
The situation of new CN node.
Further, since have different communication networks, if so new CN node can not identify current
The mark of RAT is identifying or if the mark of the RAT after mapping, just not knowing of real RAT
The RAT using which kind of form obtains UE context to former CN node, causes possibly to obtain UE
Context.
Summary of the invention
The purpose of the embodiment of the present invention is to provide access, obtain customer equipment context and subscriber equipment mark
The method and apparatus known, 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 centromere
Point judges the Mobility Management Entity group mark in GUMMEI or the described GUMMEI that described UE carries
Know (MMEGI, Mobility Management Entity Group Identity) be SAE distribution or
Map;
If described GUMMEI or MMEGI is SAE distribution, described eNodeB is according to described
GUMMEI, or encode (MMEC, Mobility according to described MMEGI and Mobility Management Entity
Management Entity Code), or according to the public land mobile network of described selection (PLMN,
Public Land Mobile Network) mark (below be referred to as PLMN-id) and MMEGI with
MMEC selects Mobility Management Entity MME;
If described GUMMEI or MMEGI is to map, described eNodeB is according to described
Mobile Country Code MCC (MCC, Mobile Country Code) in GUMMEI, Mobile Network Code (MNC,
Mobile Network Code) and MMEC selection MME, or according in described GUMMEI
MMEC selects MME, or selects according to the MMEC in PLMN-id and GUMMEI selected
MME。
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 GUTI that described UE carries is SAE distribution or reflects
Penetrate;
If described GUTI be SAE distribution, described MME with described GUTI to old mobility pipe
Reason entity (old MME) takes the context of UE;
If described GUTI is to map, described MME is reduced into old Routing Area Identifier described GUTI
(old RAI, old Routing Area Identification) and packet TMSI P-TMSI,
Or, it is reduced into old RAI and logical links temporary mark (TLLI, Temporary Logical Link
Identity), and according to the mark after described reduction to old service universal grouping wireless business supporting node (old
SGSN) context of UE is taken.
The embodiment of the present invention also provides for a kind of method of access, and the method includes:
When UE accesses SAE, the GUTI that described UE carries is mapped to old RAI and P-TMSI by MME,
Or, TLLI and the form of packet TMSI signature (P-TMSI Signature);
Old RAI and P-TMSI after described MME mapping, or, TLLI and P-TMSI Signature
The context of UE is taken to old MME or old SGSN;
Described old MME by described old RAI and P-TMSI, or, old RAI and TLLI and P-TMSI
Signature is reduced into GUTI, and the GUTI obtained according to reduction returns the upper of UE to described MME
Hereafter.
The embodiment of the present invention also provides for a kind of method of access, and the method includes:
During user equipment (UE) access system architecture evolution network SAE,
If described old node is MME, described MME with described GUTI to old Mobility Management Entity
Old MME takes the context of UE;
If described old node is Gn/Gp SGSN, the most described MME is reduced into old road described GUTI
Identified old RAI and packet TMSI P-TMSI by district, or be reduced into logical links and face
Time mark TLLI;And take the context of UE to old SGSN by the mark after described reduction;
If described old node is S4SGSN, the most described MME takes UE with described GUTI to old SGSN
Context;Described old SGSN is reduced into old RAI and P-TMSI, or reduction described GUTI
Become old RAI/TLLI mark, and return 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, old RAI and P-TMSI that SGSN carries according to described UE,
Or, TLLI, searches corresponding old physical address, obtains the context of UE to old entity;
If described old entity is old MME, described old MME reduces described old RAI and P-TMSI,
Or, described TLLI and the P-TMSI Signature that reduces is GUTI, finds to described SGSN return
The context of UE.
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, old RAI and P-TMSI that SGSN carries according to described UE,
Or, TLLI and the P-TMSI Signature carried according to described UE is 2G/3G distribution or maps
, searching corresponding old entity is old SGSN or old is MME;
If old RAI and P-TMSI that described UE carries, or, TLLI and P-TMSI Signature
Be map, described old entity is old MME, described SGSN according to described old RAI and P-TMSI,
Or, TLLI/P-TMSI Signature reduces GUTI, and obtains UE with GUTI to described old MME
Context;Described old MME will find UE context according to GUTI and return to SGSN;
If old RAI and P-TMSI that UE carries, or, TLLI and P-TMSI Signature is 2G/3G
Distribution, described old entity is old SGSN, described SGSN with described old RAI and P-TMSI, or,
TLLI takes the context of UE to described old SGSN.
The embodiment of the present invention also provides for a kind of method obtaining user equipment (UE) context, and the method includes:
When the temporary mark (TIN, Temporary Identity used in Next update) that next update uses
The temporary mark of instruction is consistent with additional (Additional) temporary mark, and user equipment (UE) only carries TIN
The temporary mark of instruction accesses;
Access node finds UE context by the temporary mark of the TIN instruction that UE carries.
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, Tracking Area Update) in handoff procedure or Routing Area Update
(RAU, Routing Area Update), UE has only to carry the TMSI of this RAT system or do not take
Carrying any TMSI, UE finds 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:
During UE initiates attachment (Attach),
If UE exists the temporary mark of RAT, then carry described temporary mark, access entity and pass through institute
State temporary mark and search corresponding node, obtain IMSI International Mobile Subscriber Identity (IMSI, the International of UE
Mobile Subscriber Identity) and security parameter;
If there is not the temporary mark accessing RAT in UE, but there is the temporary mark of another RAT, then
Carry the temporary mark of another RAT described, access entity and searched by the temporary mark of another RAT described
Corresponding node, obtains IMSI and the security parameter of UE.
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 network according to the attribute of the temporary mark of described UE
Resource node.
During user equipment (UE) access system architecture evolution network SAE, UE is being sent to evolution base station
Radio resource control (RRC, Radio Resource Control) the connection establishment request of eNodeB
(S-TMSI, by MMEC and M-TMSI to carry the Temporary Mobile Subscriber Identity of SAE network in message
Composition, if the mark that UE carries 2G/3G accesses SAE/LTE system, then S-TMSI is actual by NRI
Map with RAC and part P-TMSI and form), complete in the RRC connection establishment being sent to eNodeB
Message is not carried the whole world unique Mobility Management Entity mark GUMMEI;
ENodeB selects corresponding Mobility Management Entity MME according to the S-TMSI received, without
Corresponding MME, then eNodeB selects a new MME.
The embodiment of the present invention is distinguished as network side by the temporary mark carried during to UE access network side and divides
That join or mapping, thus use different cut-in methods for different temporary marks, it is achieved to temporarily
The flexible Application of 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 that in the embodiment of the present invention two, UE uses TA registered case to access SAE/LTE network
Time method flow diagram;
Figure 10 is that in the embodiment of the present invention two, UE uses TA not registered case to access SAE/LTE
Method flow diagram during network.
Detailed description of the invention
Below in conjunction with the accompanying drawings the detailed description of the invention of the embodiment of the present invention is further elaborated.
Embodiment one, present embodiments provides demarcation of location district code (LAC, Location Area Code)
With the method for MMEGI, such as, the bit position corresponding with MMEGI, the bit position in LAC is set
Numerical value is different, can distinguish LAC and MMEGI.Concrete method to set up, such as, the of MMEGI
One bit is 1, and a bit of LAC is 0, and this bit is referred to as the flag bit distinguishing MMEGI and LAC,
Other bit can certainly be used as diacritics position.So old RAI in UE is by 3G network
With the TLLI in P-TMSI, or old RAI and 2G communication network, the GUTI after mapping access eNodeB
Time, eNodeB passes through this differentiation, understands UE and uses real GUTI to access.Such as, eNodeB obtains
Take be SAE distribution GUTI, or use map after GUTI, as it has been described above, old RAI and
GUTI after P-TMSI (or old RAI and TLLI) maps accesses.GUTI after UE carries mapping
In the case of access, eNodeB selects the MME corresponding for MMEC that NRI maps, and this MME is permissible
It not the MME that originally registered of UE, or, the MME corresponding for MMEC using this NRI to map,
And this MME is that idle state signaling reduces (ISR, Idle mode Signaling Reduction) permission
Node or unification node or for configuration node time, then select this node.
Refer to Fig. 1, UE during accessing SAE at radio resource control (RRC, Radio
Resource Control) partly carry GUMMEI information, the tracking of eNodeB i.e. it is sent at UE
RRC part in district more newly requested (TAU Request) message carries GUMMEI information, eNodeB
Check that GUMMEI is the GUMMEI after mapping, or the GUMME of SAE distribution, if SAE
The GUMME of distribution, then eNodeB is according to all information in GUMMEI,
MCC+MNC+MMEGI+MMEC, or MMEGI+MMEC determines MME, or, eNodeB
Carry out the reselection procedure of MME owing to can not find corresponding GUMMEI, if there is with
The MME that MCC+MNC+MMEGI+MMEC or MMEGI+MMEC is corresponding, then selecting should
The GUMMEI that GUMMEI with UE of MME, this MME carries is consistent or MMEGI+MMEC
Corresponding consistent.If there is no with MCC+MNC+MMEGI+MMEC or MMEGI+MMEC pair
The MME answered then eNodeB reselects MME.If GUMMEI is the GUMMEI mapped,
Then eNodeB according to the MCC+MNC+MMEC in GUMMEI or only comes really according to MMEC
Determine MME, specifically, if there is MCC, MNC, MMEC and UE of MME, this MME
MCC, MNC, the MMEC (being mapped by NRI) carried is consistent or configures optional, such as: eNodeB
Configuring MME C or NRI certain MME corresponding, then select this MME, otherwise, one MME of reselection procedure.
Or, if UE is during accessing SAE, the mark will carried according to UE, as passed through TIN
(Temporary Identity used in Next update, next update needs the temporary mark used) comes
The mark that identification will be carried, if TIN=" P-TMSI ", represents that accessing needs next time carries
Mark after P-TMSI/old RAI mapping, if TIN=" GUTI ", represents that next time is accessed and carries SAE
Mark, if TIN=" RAT-related TMSI ", represent that accessing that RAT next time just uses that RAT
The TMSI of distribution.If during TIN=" P-TMSI " of therefore UE, UE can not take in RRC part
GUMMEI access network after band mapping, but carry S-TMSI (by MMEC in RRC part
Forming with M-TMSI, actual mapping by NRI and RAC and part P-TMSI forms) access network,
So eNodeB will not obtain MMEGI, eNodeB can be according to MMEC therein (being mapped by NRI)
Select MME.Certainly, dig up the roots according to the MMEC in S-TMSI if there is MOCN, eNodeB
Select MME, also can select MME according to PLMN-id (Selected PLMN-id) information selected,
I.e. eNodeB selects Mobility Management Entity according to PLMN-id and MMEGI selected and MMEC
MME, if the selection that MCC, MNC of being specially in the GUMMEI of MME carry with UE
PLMN-id identical, the MMEC that MMEC with UE carries simultaneously is identical, the most described network side save
This MME of point selection.Additionally, UE also needs at Non-Access Stratum (NAS, Non Access Stratum)
Part carries the GUTI, such MME after mapping could obtain context to old SGSN.Or,
ENodeB configures LAC list, when eNodeB finds that MMEGI belongs to this LAC list or this LAC
One of list, then select the MME of correspondence, such as, find, as eNodeB, the GUMMEI that UE carries
Time consistent with the mark being arranged in certain corresponding for eNodeB MME, then select correspondence MME, otherwise,
Without corresponding MME, carry out new MME and select;Wherein, the GUMMEI mark of this MME
Know actual mapping by PLMN-id+LAC+NRI to form.Such as, the Pool of Pool Yu 2G/3G of SAE
Overlap, there is MME/SGSN and unify node, under this Pool of 2G/3G, there is RAI1 in this Pool,
RAI2, RAI3, three Route Area (RA, Routing Area), when UE from 2G/3G Network Mobility to
SAE network also accesses, UE use old RAI/P-TMSI map GUTI access, eNodeB according to
Configuration information, find UE use map GUTI, and map before RA belong to RAI1, RAI2,
RAI3 one of them, then eNodeB is according to MCC+MNC+MMEC (being mapped by NRI) or MMEC
Select corresponding MME, it is not necessary to MCC, MNC, MMEGI, MMEC unanimously just select
MME.Without meeting the corresponding MME that above-mentioned situation describes, such as, it is not belonging to the RAI of configuration
One of, then reselect a MME.
Wherein, eNodeB configuration LAC list can use following methods.
MME is configured more by S1 configuration response (S1 SETUP RESPONSE) message or MME
Newly (CONFIGURATION UPDATE) message, is mapped to GUMMEI by the LAC of configuration and sends out
Give eNodeB, eNodeB and note down this S1SETUP RESPONSE message or MME
CONFIGURATION UPDATE message, preserves to configuration information, i.e. in LAC list.Under
Citing is illustrated by face.
Such as in Fig. 8, Pool1 include SGSN Pool and MME Pool, SGSN1, SGSN2,
MME1, MME2 etc. are the node in Pool1, there is also MME/SGSN unification joint in Pool1
Point SGSN3/MME3, LAC1, LAC2, LAC3 and the LAC4 etc. in Fig. 8 are 2G/3G the most respectively
Location Area Code in network, TA1, TA2, TA3 and TA4 etc. are the tracking area of SAE network the most respectively;
Wherein, from the point of view of SAE system perspective, the GUMMEI of unification node SGSN3/MME3 is PLMN-id
(PLMN Identity, PLMN identify, and wherein, PLMN-id is MCC+MNC)+MMEGI
(i.e. the id of MME Pool)+MMEC (i.e. the id of MME3 in MME Pool), in order to allow registration
UE on the SGSN of this unification node, i.e. SGSN3 from 2G/3G region enter SAE region time also
Can choose this unification node, all LAC in this SGSN3Pool can be also configured to by MME3
In eNodeB, forming LAC list, method is as follows:
A GUMMEI, this GUMMEI is formed respectively for each LAC, MME3 in Pool1
Correspond to PLMN-id+LAC+NRI (i.e. unification node be 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 be formed
Several GUMMEI.This MME3 is by after real GUMMEI (mark in SAE) and mapping
The list of GUMMEI (having several, the corresponding GUMMEI of each LAC in Pool1)
Sent out by S1SETUP RESPONSE message or MME CONFIGURATION UPDATE message
Give eNodeB, eNodeB to preserve this GUMMEI list (or perhaps LAC list, because often
Individual LAC suffers from the GUMMEI of correspondence), thus when being registered to the UE of SGSN3 from Pool1
LAC, such as LAC1 or LAC2 etc. enter into E-UTRAN region, when accessing eNodeB, due to
What UE access was carried is designated GUMMEI (being mapped by PLMN-id+LAC1+NRI), therefore should
ENodeB can pass through query configuration, i.e. by the real GUMMEI preserved before inquiry and mapping
After the list of GUMMEI, learn this GUMMEI correspondence MME3, then directly select this MME3
Node.
Configuration as above method has the disadvantage that, due to unification node and ISR demand, a MME
Substantial amounts of mapping GUMMEI may be there is, because MME can be right to each LAC in Pool
Should ground formed a MMEGI, even MME can be also each LAC in adjacent S GSN Pool also
It is respectively configured a MMEGI to meet the demand of ISR, therefore, at S1SETUP RESPONSE
In message or MME CONFIGURATION UPDATE message, it may be necessary to carry substantial amounts of
GUMMEI。
S1 SETUP RESPONSE message and MME CONFIGURATION UPDATE disappear at present
Breath carries GUMMEI list by following method, sees table one, wherein, for convenience,
Table eliminates other cells.
Table one:
IE/Group Name (information element name) | ...... |
Served GUMMEIs (service GUMMEI list) | ...... |
> GUMMEI (GUMMEI value) | ...... |
As shown in Table 1, S1SETUP RESPONSE message or MME CONFIGURATION
UPDATE message can carry complete GUMMEI list, i.e. service GUMMEI list.It addition,
As SGSN Pool increase/deletion/amendment LAC, MME can pass through MME
All of GUMMEI list is resend to each by CONFIGURATION UPDATE message
eNodeB.Owing to GUMMEI list is relatively big, and eNodeB quantity is more, so will necessarily cause
More information transmits in a network, increases the signaling traffic in network, has i.e. increased the weight of the expense of network.
Such as, if a Pool exists 10 MME, 200 eNodeB, then, when relevant
When LAC changes, then each MME is needed to send MME to each eNodeB
CONFIGURATION UPDATE message, this also implies that and will have 2000
CONFIGURATION UPDATE message transmits on S1 interface, and, each message is wrapped
Containing 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 use following collocation method.
(1) in order to reduce S1SETUP RESPONSE message or MME CONFIGURATION
The size of the configuration message such as UPDATE message so that S1SETUP RESPONSE message or MME
Without carrying substantial amounts of GUMMEI row in the configuration message such as CONFIGURATION UPDATE message
Table, can decompose GUMMEI, and then each ingredient to GUMMEI is formed respectively
List is transmitted, i.e. 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 row
Table, specific as follows:
Owing to a corresponding GUMMEI, institute all can be formed for each LAC, MME in Pool
With, eNodeB configuration LAC list actually can also be regarded as, configures GUMMEI on eNodeB
List, owing to GUMMEI is made up of PLMN-id+MMEGI+MMEC, if so GUMMEI
Be to be formed by mapping method, then the actual value of GUMMEI is PLMN-id+LAC+NRI.Typically
From the point of view of the value of MMEC and NRI be identical, and the value of PLMN-id is also identical, therefore, GUMMEI
List exists a large amount of identical content.Thus, as shown in Table 2, GUMMEI list can be changed into
PLMN-id (i.e. PLMN Identity in table)/PLMN-id list+MMEGI list+
The form of MMEC/MMEC list, wherein, PLMN-id list refers to PLMN-id list, MMEGI
List refers to MMEG list, and MMEC list refers to MMEC list;
Table two:
Under normal circumstances, the value of PLMN-id and MMEC in GUMMEI list is identical, only
The value having MMEGI is different, therefore makes GUMMEI list into PLMN-id+MMEGI list
The form of+MMEC is transmitted saving the transmission of PLMN-id and MMEC of a large amount of repetition,
Certainly, in the case of supporting many PLMN, PLMN-id can also be readily modified as PLMN-id list, in like manner,
MMEC can also change MMEC list mode into.After list after eNodeB receives this change, protect
Deposit and be combined into according to information such as PLMN-id, MMEGI list and MMEC in table voluntarily
GUMMEI list, thus completes the configuration to LAC list.
Such as, PLMN-id be currently 3 byte, MMEGI be 2 byte, MMEC be 1
byte.If a MME Pool supports that 3 PLMN, MME Pool need to configure 100 MMEGI
With a MMEC, wherein, 100 MMEGI include 1 real MMEGI and 99 LAC
MMEGI after mapping).If that by original collocation method, the size of GUMMEI list is:
3*100* (3+2+1)=1800byte.And by this method, present GUMMEI list is by PLMN-id
List and MMEGI list and MMEC list composition, the size taken is: 3*3 (PLMN-list)+100*
2 (MMEGI list)+1*1 (MMEC list)=210byte.It can be seen that existing GUMMEI list
Take up room and greatly reduce.
(2) in order to solve when LAC or GUMMEI changes, MME needs to send out to eNodeB
The problem sending all GUMMEI lists and cause too much information to transmit in a network, the embodiment of the present invention
Proposing, when LAC or GUMMEI changes, MME sends instruction message, described finger to eNodeB
Show the GUMMEI in message instruction eNodeB interpolation/amendment/deletion LAC list, such as at MME
An instruction is carried in the MME CONFIGURATION UPDATE message that eNodeB sends,
In instruction, show the change conditions of LAC or GUMMEI, be i.e. to add one or several GUMMEI
Still have modified GUMMEI and still delete GUMMEI etc..Amended MME
CONFIGURATION UPDATE message may refer to table three;
Table three:
It is of course also possible to indicate interpolation the most in the message or delete or amendment GUMMEI, and not
Need the GUMMEI allowing MME other not changed to be also sent to eNodeB, such as, can be such that
When MME needs to add a GUMMEI, then can send MME
CONFIGURATION UPDATE (new GUMMEI, behavior=' add ') message to eNodeB,
Wherein, " new GUMMEI " represents the mark (ID, Identity) of the GUMMEI needing interpolation,
" behavior=' add ' " is then to represent that needs add GUMMEI in original LAC list,
" behavior " is a kind of information element (IE, Information Element), and its value shows concrete
Action, so, when eNodeB receives this MME CONFIGURATION UPDATE (new
GUMMEI, behavior=' add ') after message, in original LAC list, just add a GUMMEI;
When MME to delete a GUMMEI, then can send MME CONFIGURATION
Message is to eNodeB for UPDATE (GUMMEI, behavior=' delete '), wherein, and " GUMMEI "
The ID of the GUMMEI in original LAC list is deleted in expression, and " behavior=' delete ' " represents to be needed
GUMMEI to be deleted, after eNodeB receives this message, arranges at original LAC according to this message
Table is deleted corresponding GUMMEI;
When MME to revise a GUMMEI, then can send MME CONFIGURATION
UPDATE (new GUMMEI, GUMMEI, behavior=' modify ') message to eNodeB, its
In, " behavior=' modify ' " represents to be needed to revise the GUMMEI in original LAC list,
" GUMMEI " represents the ID of the GUMMEI needing amendment, and " new GUMMEI " is then to represent to need
The ID of GUMMEI to be made into, i.e. " GUMMEI " are corresponding in original LAC list
The ID of GUMMEI to change " new GUMMEI " into.
It is of course also possible to do not carry " behavior " such IE, such as, can pass through " updated
GUMMEI " and " new GUMMEI " shows action, i.e. " updates GUMMEI " and " new
GUMMEI ", wherein, " updated GUMMEI " represents to update original GUMMEI, new
GUMMEI represents to be needed to add new GUMMEI;So, if updated GUMMEI does not has
Value or be not carried, and new GUMMEI=5, then it represents that will add an id is the GUMMEI of 5;
If updated is GUMMEI=5, and new GUMMEI void value or be not carried, represent and will delete
Except that GUMMEI that id is 5;If updated is GUMMEI=5, and new GUMMEI=10,
Expression GUMMEI to be revised that GUMMEI equal to 5 changes 10 into.
(3) certain, in order to reduce when LAC or GUMMEI changes further, MME sends out
Give the quantity of the message of eNodeB, reduce the signaling traffic between MME and eNodeB, it is also possible to
Take another kind of method, as follows:
All being concentrated on by all of configuration information on a preset Centroid, this Centroid can be
Preset eNodeB, it is also possible to be preset MME etc., this Centroid has all MME and joins
Confidence ceases, if the configuration information of certain MME changes, then by this Centroid to all of eNodeB
Send configuration message, such as send S1 SETUP RESPONSE message or MME
CONFIGURATION UPDATE message.Therefore, need to send to eNodeB when this Centroid
During configuration information, the configuration information of all MME will be sent.Such as S1 SETUP RESPONSE disappears
GUMMEI list in breath or MME CONFIGURATION UPDATE message is not one
The GUMMEI list of MME, but the GUMME list of all MME, certainly, in order to realize this
Method, needs to modify S1SETUP REPONSE message, amended S1 SETUP
REPONSE message is as shown in Table 4;
Table four:
" GUMMEI " in table is GUMMEI real for each MME, and each MME only has one
Individual real GUMMEI, does not consider that at this GUMMEI, MME after mapping use this real
The information of all of MME, as unique mark, is concentrated in together by GUMMEI, forms MME list,
Each MME in this MME list has the name of some specific configuration information, such as MME,
Ability, also has GUMMEI list of mapping etc., and wherein, GUMMEI list is probably (PLMN-id
+ MMEGI+MMEC) list, it is also possible to PLMN-id list+MMEGI list+MMEC list,
It is likely to not exist the GUMMEI list of this mapping.
In a word, it is simply that being configured message eNodeB offer in Pool by this Centroid by one should
The configuration information of all MME in MME Pool, so, when LAC or GUMMEI changes,
Just have only to this Centroid and send a MME CONFIGURATION to each eNodeB
UPDATE message, it is not necessary to each MME sends to each eNodeB, thus decreases in network
The quantity of the message transmitted.There are 10 MME, 200 eNodeB in such as MME Pool, works as LAC
When changing, just have only to this Centroid and send out total occurring about configuration to 200 eNodeB
The configuration message of variation, message number only has 200, and certainly, before this, MME may also need to
The configuration message of self is sent to this Centroid.
(1) (2) (3) three kinds of methods can be independently operated, and can also be used in combination above, certainly, and knot
Close use can more optimize, as (1) method and (2) method combine, then, when there being 10 LAC
When being added, MME the most only need to update the information of these 10 LAC, then sends PLMN-id list+10
MMEGI+MMEC after individual LAC mapping is to eNodeB, in the core not supporting multiple operator
In the case of net node, this is sent to the size the most only 3+20+1=24byte of message of eNodeB.No
Then, if only use (1) method, although reduce the size of of message, but the quantity of message again without
Change, i.e. need for sending all GUMMEI information (including not updating) to eNodeB;As
Fruit only uses (2) method, although the quantity of message has reduced, 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, i.e.
" 24byte " is many greatly.Certainly (3) method can also combine, very with (1) method or (2) method
To all combining, do not repeat them here.
It should be noted that, the present embodiment is to illustrate as a example by eNodeB by network side node, described
Network side node can also be described Centroid, say, that in the present embodiment performed by eNodeB
Operation can also be completed by this Centroid, and such as this Centroid can also be as selecting CN node
Node, i.e. this Centroid is connected with each eNodeB, when UE accesses eNodeB, eNodeB
Do not select CN node, but send the message to this Centroid, this Centroid select CN to save
Point, such as MME.So, just have only to the configuration information of MME is configured to this Centroid,
Without being sent to eNodeB, say, that each MME sets up or configuration information change at S1
Time, when i.e. LAC or GUMMEI changes, it is only necessary to carrying out information with this Centroid is alternately
Can.There are 10 MME, 200 eNodeB in such as MME Pool, when LAC changes,
10 MME have only to send the configuration message changed about configuration, message count to this Centroid
Amount only 10, without sending the configuration message changed about configuration to 200 eNodeB,
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, and obtains
Take the information of UE mark, confirm that this information is the information of network allocation or the information of this UE is reflected by network
Information after penetrating, and according to above-mentioned differentiation, select suitable network node for UE, it is to avoid UE due to
Change RAT and corresponding CN node cannot be linked into.
Embodiment two, the method described by embodiment one is all to access when UE carries 2G/3G mark
During SAE/LTE network, the community being currently stationed according to UE is not at tracking area (TA, the Tracking of registration
Area) situation in carries out accessing, in the method described by embodiment one, if UE is currently stationed
Community be in the TA of registration, then complete (RRC Connection Setup in RRC connection establishment
Complete) the NAS part in message, the NAS part of such as TAU Request message is (the most equal
The NAS part of RRC connection setup complete message is called NAS message) UE mark can not be carried
, (UE-id) can be according to being currently accessed such as the information such as GUTI or P-TMSI or IMSI, i.e. UE
Whether TA determines whether carry UE mark in NAS message in the TA list (TA list) of self
Know.
If it is to say, NAS message is carried UE mark, the most then thinking that UE is currently stationed little
District be not at registration TA in, and if it practice, carry in NAS message UE mark, then
Can also access according to the situation that the community that UE is currently stationed is in the TA of registration, such as when
It can only be attachment request that UE carries NAS message when accessing SAE/LTE network that identifies of 2G/3G network
(Attach Request) message or tracing section updating request (TAU Request) message, then, as long as
The two message always carries UE mark, even if the MME then selected does not has UE context, and this selection
MME can also by UE mark find old node obtain UE context, or to HSS obtain
UE context.To this end, present embodiments provide another kind of cut-in method.
For convenience, below the community that UE is currently stationed is not at this feelings in the TA of registration
Condition is referred to as TA not registered case, otherwise, if the community that UE is currently stationed is in the TA of registration,
Then it is referred to as TA registered case.It should be noted that, in order to preferably describe the skill that the present embodiment is provided
Art scheme, below will be situated between to TA registered case and TA not registered case technology simply
Continue, TA Registered case and TAnot registered case be UE carry SAE distribution mark connect
Enter technology during SAE.
When UE enter a SAE Pool and use SAE distribute temporary mark initiate access time, UE
Judge whether the community that is currently accessed belongs to the registration area of UE, i.e. UE detects self be currently stationed little
Whether district is in the TA of registration, the most then the UE of idle (idle) pattern accesses SAE/LTE net
RRC connection establishment request (RRC Connection Request) message that network is initiated carries S-TMSI,
Owing to UE does not the most move out original Pool region in this case, therefore, eNodeB is permissible
It is simply selected to original MME by the MMEC in S-TMSI (in the case of MOCN, also want
The PLMN-id information of the selection carried according to UE combines and selects MME), receiving eNodeB
After the RRC connection establishment message carrying S-TMSI returned, in order to reduce the size of message, save
The bandwidth taken, the NAS in UE subsequently is sent to the RRC connection setup complete message of eNodeB
Can not carry UE mark in message, the RRC part in RRC connection setup complete message is the most not
Carrying GUMMEI, after eNodeB have selected MME, eNodeB sends initial UE message to choosing
The MME selected, then MME obtains the context of UE, wherein, initial UE according to S-TMSI
Message includes that S-TMSI and the RRC connection establishment in the RRC connection establishment request that UE initiates completes
The information such as the NAS message in message;If it is not, i.e. UE detects the community self being currently stationed is not at note
Time in the TA of volume, then the RRC connection that the UE access SAE/LTE network of idle idle pattern is initiated is built
Vertical request message is carried a random number (Random ID), then receives carrying of eNodeB return
There is the RRC connection establishment message of random number, owing to UE may move out original Pool in this case
Region is likely to not move out original Pool region, so UE is being sent to eNodeB's afterwards
Need to carry the mark of UE in NAS message in RRC connection setup complete message, simultaneously at RRC
RRC part in connection setup complete message is carried GUMMEI, such eNodeB and just can be passed through
GUMMEI searches corresponding MME, and (in the case of MOCN, eNodeB is to carry according to UE
Selection PLMN-id and GUMMEI in MME Group ID and MMEC select MME
), if there is corresponding MME (MME originally), then it is simply selected to original MME,
If there is no corresponding MME, then explanation UE has changed Pool, then eNodeB selects one
Individual new MME, then retransmits initial UE message to the MME, this MME chosen chosen
Obtaining the context of UE, wherein, initial UE message includes the information such as NAS message.Can be found in Fig. 9
With Figure 10, Fig. 9 are that UE uses TA registered case to access the method flow diagram of SAE/LTE network,
Figure 10 is that UE uses TA not registered case 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 the mark form that the identity map of 2G/3G is SAE, then according to TA registered case
Access, i.e. UE disappears in RRC connection establishment request (RRC Connection Request) initiated
Breath carries the S-TMSI of mapping, and the RRC part in RRC connection setup complete message subsequently
Do not carry GUMMEI.And can always take in the NAS message in RRC connection setup complete message
Band UE identifies, and at this moment eNodeB can be in initial UE message (Article 1 Initial sent to MME
UE Message) in do not carry S-TMSI.Can also be that UE judges whether the community being currently accessed is located
In the TA of registration, if it is, total in the NAS message in RRC connection setup complete message
It is not carry UE mark, if it is not, then take in the NAS message in RRC connection setup complete message
Band UE identifies.
Certainly, before UE access system architecture evolution network SAE, UE can also dock fashionable use
UE mark is that SAE distributes or the carrying out mapped judges, if described UE mark is to map,
Performing the action described in above method, i.e. performing UE please in the RRC connection establishment being sent to eNodeB
Seek the S-TMSI carrying mapping in message, in the RRC connection setup complete message being sent to eNodeB
Do not carry the step of GUMMEI;Otherwise, if described UE mark is SAE distribution, then judge
Whether the region that UE accesses belongs to the registration area of UE, if the region that UE accesses belongs to the registration of UE
Region, then perform TA registered case and access, if the region that UE accesses is not belonging to the Acceditation Area of UE
Territory, then perform TA not registered case and access, can be found in TA registered case in the present embodiment
With the associated description of TA not registered case, the most burdensome at this.
It should be noted that, due to eNodeB need distinguish RRC connection establishment request message carry be
S-TMSI or random number, it is therefore desirable to define one and identify in S-TMSI and random number, such as will
This mark named Distinguishing Mark, defining its size is 8bit, if the number on 8bit is all 1,
Then determine the request of RRC connection establishment message carries is random number, if the number on 8bit is not all 1, then
That determine the request of RRC connection establishment message carries is S-TMSI.This Distinguishing Mark is positioned at
The MMEC part of S-TMSI and the front 8bit of random number.
When carrying the mark access SAE of mapping due to UE, the MMEC part in S-TMSI is by NRI
Mapping, and NRI is probably complete 1, and what such eNodeB can be mistakenly considered to receive is random number,
Accordingly, it would be desirable to definition NRI can not be complete 1.
Certainly, UE can also need not whether belong to the community being currently accessed the registration area of UE and carries out
Judge, or need not be that SAE distributes or the carrying out mapped judges to self-contained UE mark,
But always use TA Registered Case, i.e. ask in the RRC connection establishment being sent to eNodeB
Message is always carried S-TMSI, the most under what circumstances, completes to disappear in RRC connection establishment
NAS message in breath is always carried UE and is identified, and carry in RRC connection establishment request message
S-TMSI be used only to for eNodeB select MME, without on S1 interface subsequently by S-TMSI
On band, i.e. eNodeB does not carry S-TMSI information in the initial UE message that MME sends, thus
The uninterrupted of message can be reduced, save the bandwidth taken, but, the deficiency of the method is, when
When UE changes Pool, if new Pool there is also the MMEC of identical numbering, then eNodeB is direct
This is selected to have the MME corresponding to the MMEC of identical numbering in new Pool, without by negative
Carry the principles such as equilibrium (Load Balancing) and select a new MME.Or, it is also possible to always make
Access SAE/LTE network, i.e. UE with TA not registered case and be sent to the RRC of eNodeB
Connection establishment request message always carries random number, at RRC connection setup complete message subsequently
RRC part carries GUMMEI, carries UE in the NAS message of RRC connection setup complete message
Mark, but the process that so UE initiates service request (Service Request) will not be too fast, because clothes
Business request message typically understands limited length, in order to initiate as soon as possible to access.
Need to illustrate it is to be more than with RAN node as eNodeB, CN node is to carry out as a example by MME
Illustrating, this RAN node can also be for having the miscellaneous equipment of similar functions, CN node with eNodeB
The miscellaneous equipment of similar functions can also be had with MME for having.
The beneficial effect of embodiment two: the RRC connection establishment request message that embodiment two is initiated by UE
In carry S-TMSI, be then that UE selects suitable CN node by S-TMSI, it is to avoid UE
Cannot be linked into the situation of corresponding CN node owing to changing RAT, meanwhile, the present embodiment passes through
Not carrying the methods such as GUMMEI in RRC connection setup complete message, the flow reducing message is big
Little, save the bandwidth taken.
Embodiment three, the present embodiment by arranging differentiation LAC and MMEGI, such as, is arranged in LAC
The numerical value of the bit position that bit position is corresponding from MMEGI is different, can distinguish LAC and MMEGI.This
Embodiment propose when UE by GUTI access MME, concrete access way can include adhere to attach or
TAU.If MME exists UE context (UE Context), then MME is found by GUTI
UE, otherwise, MME finds old MME by the GUMMEI in GUTI, such as, can pass through domain name
Resolution system (DNS, Domain Name System) searches old MME, and sends to old MME
Context request (Context Request), comprises GUTI or sends identification request in this context request
(Identification Request), this identification request is comprised GUTI, old MME and is found by GUTI
UE Context, returns the IMSI information etc. of UE Context or UE to MME.And when UE passes through
GUTI access MME, MME or DNS after old RAI/P-TMSI or TLLI maps need basis
Network be the GUTI such as SAE of UE distribution be the GUTI of GUTI and the mapping of UE distribution
Differentiation.As know GUTI be map GUTI, then reduction GUTI be old RAI/P-TMSI or
The TLLI/old RAI (if old SGSN is 2G SGSN) of 2G network.By old RAI or logical
Cross old RAI and NRI and find old SGSN, send Context Request to old SGSN, should
Context Request comprises old RAI, P-TMSI or TLLI, or sends checking request (Identification
Request), this Identification Request comprises old RAI, P-TMSI or TLLI.old SGSN
By old RAI and P-TMSI, or old GGSN finds UE context by TLLI, returns
The IMSI information of UE Context or UE is to MME.
Refer to Fig. 2, UE send tracing section updating request, i.e. TAU Request message to MME,
This TAU Request message comprises GUTI, MME and checks that GUTI is real GUTI, i.e. SAE net
The GUTI after the real GUTI of UE, or mapping is distributed in network side, if real GUTI, then
MME to old MME send Context Request, this Context Request carry (GUTI,
Complete TAU Request message) to obtain context to old MME, old MME passes through
It is the TAU that UE sends that GUTI searches UE Context, complete TAU Request message
Request message, if this message has integrity protection, then carries this message to old MME, in order to old
MME carrys out checked for integrity protection, if be proved to be successful, then returns UE context to new MME.
If MME checks that GUTI is the GUTI after mapping, then MME sends Context to old SGSN
Request (old RAI, P-TMSI or TLLI), old SGSN is according to old RAI and P-TMSI or TLLI
Search UE Context.
Wherein, about safety integrity protection problem, when UE accesses SAE by the GUTI after mapping
During system, following several ways can be used:
1. not having the integrity protection parameter of SAE due to old SGSN, therefore MME can be according to GUTI
It is that after mapping, GUTI does not send TAU Request message to old SGSN.
Or
No matter whether GUTI is the mark after mapping to 2.MME, gives old node all the time, such as old SGSN
Send the checking of TAU Request message calls, but this message is not verified by old SGSN, return
It is not proved to be successful or there is no the information of checking to MME so that MME performs coupling of safety-relevant processes, as
MME does not really have UE context, such as subsidiary whole world unique temporary identity (Additional GUTI)
Instruction be other MME, can by other MME perform coupling of safety-relevant processes, or MME according to
Additional GUTI finds the UE context self preserved, and UE carries out safety verification, or,
MME initiates safety certification process to UE.
Or
3.UE carries Additional GUTI and just indicates UE to have UE context at the MME accessed,
The MME then accessed carries out safety verification to UE, if by safety verification, then sent out to old SGSN
The Context Request sent or Identification Request carries the information that UE has verified that.
Or
4., if Additional GUTI indicates other MME, the newest MME is to Additional
GUTI instruction MME obtain safe context, new MME according to obtain safety information to UE
Verify;Or new MME is by attachment request (Attach Request) message or TAU Request
Message is issued the MME of Additional GUTI instruction and is verified.
Or
5. GUTI after if UE carries mapping accesses, UE not to TAU Request message or
The message such as Attach Request message carry out integrity protection.
Or
6., the GUTI after if UE carries mapping accesses, UE carries what SGSN allocated it
P-TMSI Signature field, issues network, after MME receives, by P-TMSI Signature field
Issue old SGSN and carry out the checking of UE.Reflect if i.e. UE carries old RAI/P-TMSI or TLLI
The GUTI penetrated accesses SAE, then UE carries P-TMSI Signature cell, and MME is to old
The Context Request message that SGSN sends also carries P-TMSI Signature cell, asks old
UE is verified by SGSN.
Above safety problem is equally applicable to the GUTI after following UE carries mapping and accesses SAE
In the embodiment of system or UE carries old RAI/P-TMSI (or TLLI)/P-TMSI after mapping
In the embodiment of Signature access 2G/3G (MME and SGSN needs reversing of position).
Embodiment four, is with the difference of embodiment three, GUTI is directly mapped by MME.
GUTI is mapped or is reduced to old RAI/P-TMSI (or TLLI)/P-TMSI by the present embodiment MME
Signature or old RAI/P-TMSI, or P-TMSI therein can also be the form of TLLI, logical
Cross the form of old RAI/P-TMSI (or TLLI)/P-TMSI Signature to old entity, such as old
MME or old SGSN obtains context, if during old MME, old MME is by old
RAI/P-TMSI maps or is reduced to GUTI and obtains UE Context;If old is SGSN, old SGSN
Directly according to old RAI/P-TMSI (or TLLI), P-TMSI Signature finds UE Context, can
See Fig. 3.
Embodiment five, is with the difference of embodiment three, in the present embodiment, it is judged that be the GUTI mapped
Afterwards, it is S4SGSN or Gn/Gp SGSN according to corresponding old SGSN, carries out different operations.
It is that MME/S4-SGSN or Gn/Gp SGSN comes that the present embodiment understands old node by access node
Carry out different operating.As the GUTI after UE is mapped by old RAI/P-TMSI accesses MME, tool
Body access way can be Attach (attachment) or TAU mode.If MME knows old SGSN
It is the SGSN supporting S4, such as according to inquiry DNS, or is based on GTP-v2 according to its interface
Interface knows that old SGSN is the SGSN supporting S4, then MME sends Context to old SGSN
Request, this Context Request GUTI comprise GUTI, or send Identification Request,
This Identification Request comprises GUTI, by old SGSN according to the differentiation of GUTI, reduces GUTI
For old RAI, P-TMSI, or be reduced to old RAI, P-TMSI TLLI, by old RAI and
P-TMSI, or old RAI and/or TLLI find UE context, returns UE Context or IMSI
Deng to MME;If MME knows that old SGSN is the SGSN supporting Gn/Gp, such as according to looking into
Ask DNS, or be that interface based on GTP-v1 or v0 knows that old SGSN is to prop up according to its interface
Hold the SGSN of Gn/Gp, such as the SGSNPre-R8SGSN before 3GPP R8 version definition, then
MME reduction old RAI/P-TMSI (or TLLI), sends SGSN Context Request to old SGSN
(old RAI, P-TMSI or TLLI) or Identification Request (old RAI, P-TMSI or TLLI),
Old SGSN finds UE context by old RAI and P-TMSI (or TLLI), returns to MME.
Refer to Fig. 4, if UE is when SAE Attach, the temporary mark that the next update of UE uses
(TIN, Temporary Identity used in Next update) is set to P-TMSI or TLLI or UE
The temporary mark that last time uses at 2G/3G attachment removal Detach, UE needs to use old RAI/P-TMSI,
GUTI after wherein P-TMSI can also map for TLLI accesses SAE;MME receives this mapping
GUTI, can be directly reduced to old RAI/P-TMSI (or TLLI) or see that old SGSN is S4
SGSN or Gn/Gp SGSN, if old SGSN is S4SGSN, UE can pass through
Identification Request (GUTI, complete Attach Request message) is to S4SGSN
Obtaining IMSI and context etc., GUTI is reduced to old RAI/P-TMSI (or TLLI) by S4SGSN
Find UE context and return IMSI etc..Use if old SGSN is Gn/Gp SGSN, MME
Old RAI/P-TMSI (or TLLI) after reduction obtains information to old SGSN, passes through identification request
Identification Request, carries old RAI/P-TMSI (or TLLI) in this identification request.Certainly,
If with the presence of accessing the temporary mark that RAT distributes, UE is used as when Attach accessing RAT
The temporary mark of distribution, regardless of the instruction of TIN, then uses without the temporary mark accessing RAT
The temporary mark of another RAT, if or the temporary mark of each RAT all do not have, then use IMSI to connect
Enter.If GUTI is real GUTI, then Identification Request message may be carried
The complete Attach Request message brought up from UE, carries out integrity protection for old MME and tests
Card, if MME finds that GUTI is the GUTI mapped, then MME need not carry this Attach
Request message is in the Identification Request message issuing SGSN, and needs to enter UE
Row safety verification.
About safety-related problem, if Additional GUTI or Additional that UE carries
There is context in this locality in RAI/P-TMSI instruction UE, then UE carries out integrity protection checking in this locality
Deng security process, so, access entity, such as MME or SGSN, avoid the need for TIN instruction
Old entity, such as old MME or old SGSN, it is desirable to carry out integrity protection checking etc., and if
UE has been carried out integrity protection checking in this locality, then access entity and carry in Context Request
UE has verified that UE just need not be verified by information, old entity.UE accesses real in this locality else if
Body does not has UE context, when old entity and the access entity of TIN instruction are same RAT, then access
Entity may require that old entity carries out integrity protection checking to UE, such as, access what UE was sent by entity
Message is sent to old entity, and old entity is verified.Otherwise access entity and can not require that old entity is to UE
Carry out security process, such as, access entity and the message that UE sends is not sent to old entity, or, access
The old entity of entity inquiry carries out security process to UE, if but old entity cannot verify (as usual entity with connect
Entering entity is not same RAT), the oldest entity returns checking not to be passed through or is not fully complete the information such as checking, it is desirable to
Access entity voluntarily UE to be verified.If additionally, that the TIN instruction of UE is " P-TMSI "
Or " TLLI ", then UE needs when Attach or TAU/RAU accesses to carry P-TMSI Signature,
In order to carry out the safety verification of UE, i.e. access entity and bring old entity and UE is verified, else if
The TIN instruction of UE is " GUTI ", then UE needs to carry P-TMSI when accessing 2G/3G
Signature, because GUTI needs partial information and is mapped to P-TMSI Signature.
Embodiment six, is with the difference of embodiment three, in embodiment three, UE is connect by GUTI
That enter is MME, and in the present embodiment, UE carries old RAI/P-TMSI/P-TMSI Signature and connects
That enter is SGSN, and wherein P-TMSI may also be TLLI.When UE carry old RAI/P-TMSI (or
TLLI)/P-TMSI Signature accesses SGSN, SGSN or DNS according to real old RAI/P-TMSI
(or TLLI)/P-TMSI Signature is different such as MMEGI and LAC from the mark after mapping
1bit difference find old MME or old SGSN.SGSN can pass through old all the time
RAI/P-TMSI/P-TMSI Signature form obtains context to old entity, if old entity is
MME, SGSN send SGSN Context Request, this Context Request bag to old MME
Recover GUTI containing old RAI, P-TMSI/TLLI, P-TMSI Signature, old MME, find UE
Context, returns UE Context, returns EPS Context according to interface or Context Request content
Or 2G/3G Context.
Refer to Fig. 5, UE and ask message by sending RAU, i.e. by old RAI, P-TMSI/TLLI,
P-TMSI Signature accesses SGSN, if UE uses the old RAI that GUTI maps,
P-TMSI/TLLI, P-TMSI Signature accesses, then SGSN finds old MME address, to
Old MME send Context Request, this Context Request carry (old RAI,
P-TMSI/TLLI, P-TMSI Signature) message, old MME according to old RAI, P-TMSI/TLLI,
P-TMSI Signature reduces GUTI, finds UE context and returns UE Context.Additionally, by
There is no P-TMSI Signature information in old MME, therefore, UE is carried out checking can use with
Lower method:
1.Old MME carries UE safety in the Context Response returned and does not verifies information, example
As carried ' the Cause value of P-TMSI Signature mismatch ' so that SGSN verifies UE again.
2. or, if SGSN does not has UE context and SGSN to understand the old RAI of TIN instruction,
Old node corresponding for P-TMSI/TLLI, P-TMSI Signature is old MME, then SGSN is always
UE is verified, and the Context Request sent to old MME carries " MS Validated "
Information, represents that UE is by checking.If SGSN has UE context, wherein, Additional can be passed through
RAI/P-TMSI finds UE Context, then SGSN verifies UE in advance, if be proved to be successful, then to
The Context Request that old MME sends carries " MS Validated " information, represents that UE passes through
Checking.
Embodiment seven, is with the difference of embodiment six, in embodiment six, by old MME by old
RAI/P-TMSI/P-TMSI Signature is reduced into GUTI, and wherein P-TMSI can be TLLI.?
In the present embodiment, when old entity is old MME, by SGSN by old RAI/P-TMSI (or TLLI)
/ P-TMSI Signature is reduced into GUTI.Refer to Fig. 6, SGSN understand old entity be MME also
Being SGSN, if old entity is MME, then S4SGSN recovers GUTI, sends out to old MME
Sending Context Request (GUTI), old MME finds UE Context according to GUTI, returns UE
Context。
Safety problem is with embodiment three to six, if there is UE context SGSN this locality, verifies P-TMSI
Signature, without UE context and find old entity correspondence MME, then SGSN always to
UE initiates security process, and SGSN reduction GUTI, asks UE context to old MME.
Access node can be the mark after original temporary mark or mapping with oneself differentiation temporary mark, also
DNS can be passed through, DNS after analyzing, feed back 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 the old node after translation receives
After Context Request, continue to search for real old node, relay the message to real old node.
Additionally, in prior art, UE also may can carry Additional TMSI (subsidiary temporary mark),
I.e. UE carries Additional GUTI when accessing SAE, carry Additional old when accessing 2G/3G
RAI/P-TMSI, wherein P-TMSI may also be TLLI, and the effect of this Additional TMSI is used to the greatest extent
Amount finds the UE Context that may be present accessed in RAT entity, and uses what TIN indicate to mark temporarily
Know and obtain context etc., so can directly merge the context of acquisition to the UE in this RAT entity
Context, otherwise accessing RAT needs to inquire about the most originally according to the IMSI information in the context obtained again
There is UE Context in RAT entity, then remerges and cause complexity.This Additional TMSI is actual
Can carry, to save interface-free resources: periodic location update (Periodic in the case of the most below
TAU or Periodic RAU) or handoff procedure in TAU or RAU;Or the interim mark of TIN instruction
Know consistent with Additional temporary mark, i.e. the temporary mark accessing RAT exactly of TIN instruction;Or
When there is the temporary mark accessing RAT during Attach in UE.
Use 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 has distinguished;Real old RAI/P-TMSI (or TLLI)
Distinguish with the old RAI/P-TMSI (or TLLI) after mapping.In LAC Yu MMEGI
Arranging a bit position, LAC is always 0, and MMEGI is always 1.
The GUTI access SAE, eNodeB that use old RAI/P-TMSI to map as UE are known by differentiation
Road UE uses old RAI/P-TMSI to access, then select MME corresponding for NRI as far as possible;Or eNodeB
By finding whether this LAC has configuration, decide whether select NRI correspondence MME or reselect
MME。
GUTI after UE is mapped by old RAI/P-TMSI accesses MME, MME understanding should
GUTI is the GUTI mapped, reduction old RAI/P-TMSI/TLLI, is found by old RAI and NRI
Old SGSN, to old SGSN send Context Request, this Context Request carry (old RAI,
P-TMSI/TLLI), old SGSN finds UE context by old RAI and P-TMSI/TLLI, returns
Back to MME.
Or, the GUTI after UE is mapped by old RAI/P-TMSI accesses MME, MME
Solving the GUTI, MME that this GUTI is mapping and inquiring about old SGSN is S4SGSN or Gn/Gp
SGSN.If old SGSN is S4SGSN, then MME sends Context to old SGSN
Request (GUTI), i.e. this Context Request carry GUTI, or send Identification
Request, old SGSN reduction GUTI is old RAI, P-TMSI/TLLI, by old RAI and
P-TMSI/TLLI finds UE context, returns to MME;If old SGSN is Gn/Gp SGSN,
So MME reduces old RAI/P-TMSI/TLLI, sends Context Request to old SGSN,
This Context Request carries (old RAI, P-TMSI/TLLI), old SGSN by old RAI and
P-TMSI/TLLI finds UE context, returns to MME.
Additional TMSI TAU/RAU, Periodic TAU/RAU, TIN in switching HO refers to
When the temporary mark shown is consistent with Additional temporary mark or UE exists access during Attach
Can need not during the temporary mark of RAT.
When MME and SGSN of Combined node belongs to different PLMN, or different PLMN
When MME and SGSN sets up ISR, UE can allow RAN by carrying two PLMN-id or configuration
Node chooses the CN node of correspondence.
The mark carried by distinguishing UE is which RAT distributes, and RAN node or access node can
Make corresponding suitably process, prevent from selecting error node or sending inconsistent parameter to corresponding node.
The embodiment of the present invention additionally provides a kind of method for user equipment (UE) distribution Internet resources node, should
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, the attribute mapping of the entrained temporary mark that network side obtains user equipment (UE) is network
After side judges that ID is network side distribution or mapping.
Detailed implementation is described as follows:
When the network side that user equipment (UE) accesses is System Architecture Evolution network SAE, this network side obtains
Take the attribute mapping of entrained identity of user equipment (UE) specifically: the evolution of this SAE network
Base station eNodeB judge the whole world unique Mobility Management Entity mark GUMMEI/ that described UE carries or
Mobility Management Entity group mark MMEGI in described GUMMEI is SAE distribution or maps
's;
If described GUMMEI/ or MMEGI is SAE distribution, then network side is according to described mark
Attribute mapping be UE distribution Internet resources node specifically: eNodeB according to GUMMEI or
MMEGI and Mobility Management Entity coding MMEC selects Mobility Management Entity MME;
If described GUMMEI or MMEGI is to map, then network side is according to the attribute mapping of mark
For UE distribution Internet resources node specifically eNodeB according to the Mobile Country Code MCC in described GUMMEI
MCC, Mobile Network Code MNC and MMEC select MME;Or eNodeB is according to GUMMEI
In MMEC select MME.
Or also can be accomplished in that
When the network side that user equipment (UE) accesses is System Architecture Evolution network SAE, network side obtains
The attribute mapping of the entrained identity of user equipment (UE) is specifically: the mobility pipe of SAE network
Reason entity MME judges that global unique temporary identity GUTI that described UE carries is that SAE distribution is gone back
It is to map;
If GUTI is SAE distribution, then network side is that UE divides according to the attribute mapping of described mark
Also including before distribution network resource node, MME GUTI takes to old Mobility Management Entity old MME
The context of UE;
If GUTI is to map, then network side is that UE distributes Internet resources according to the attribute mapping of mark
Also including before node, MME is reduced into the interim shifting of old Routing Area Identifier old RAI/ packet described GUTI
Move ID P-TMSI or be reduced into old RAI/ logical links temporary mark TLLI;And use old
RAI/P-TMSI or old RAI/TLLI is to old service universal grouping wireless business supporting node old
SGSN takes the context of UE.
The statement of corresponding embodiment of the method above, the embodiment of the present invention additionally provides a kind of user equipment (UE),
This UE includes, when UE uses the GUTI after mapping to access SAE system, does not does access message
Integrity protection.
Refer to Fig. 7, network side apparatus, including identity property acquisition module 701, be used for distinguishing UE and make
With the temporary mark after mapping or real temporary mark, the i.e. network side of real temporary mark distributes
Mark;This network side node can be wireless access network node.
Internet resources node distribution module 702, according to the attribute of the temporary mark of above-mentioned UE, i.e. UE be
Mark after the mark of network side distribution or mapping, 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 arrive this
Bright can add the mode of required hardware platform by software and realize, naturally it is also possible to all be come by hardware
Implement.Based on such understanding, technical scheme background technology is contributed whole or
Part can embody with the form of software product, and this computer software product can be stored in storage and be situated between
In matter, such as ROM/RAM, magnetic disc, CD etc., instruct with so that a computer sets including some
Standby (can be personal computer, server, or the network equipment etc.) performs each embodiment of the present invention
Or the method described in some part of embodiment.
The above is only the detailed description of the invention of the present invention, it is noted that general for the art
For logical technical staff, under the premise without departing from the principles of the invention, it is also possible to make some improvement and profit
Decorations, these improvements and modifications also should be regarded as protection scope of the present invention.
Claims (14)
1. the method accessed, it is characterised in that the method includes:
When user equipment (UE) access system architecture evolution SAE network, Mobility Management Entity MME
Judge that global unique temporary identity GUTI that described UE carries is described SAE network allocation or reflects
Penetrate;
If described GUTI is described SAE network allocation, described MME with described GUTI to old
Mobility Management Entity old MME obtains the context of described UE;
If described GUTI is to map, described MME is reduced into old Routing Area Identifier described GUTI
Old RAI and packet TMSI P-TMSI, and according to described old RAI and P-TMSI to
Old service universal grouping wireless business supporting node old SGSN obtains the context of described UE, or,
Described MME is reduced into old RAI and logical links temporary mark TLLI described GUTI, and according to
Described old RAI and TLLI obtains institute to old service universal grouping wireless business supporting node old SGSN
State the context of UE.
Cut-in method the most according to claim 1, it is characterised in that described MME judges described
The GUTI that UE carries be described SAE network allocation or map include:
Described MME checks that in described GUTI, the flag bit of Mobility Management Entity group mark MMEGI is
The mark of MMEGI or the mark of Location Area Code LAC;
If the mark of MMEGI, then judge that GUTI is described SAE network allocation;
If the mark of LAC, then judge that GUTI is to map.
Cut-in method the most according to claim 1, it is characterised in that described MME is according to described
Old RAI and P-TMSI, or, described MME according to described old RAI and TLLI to old SGSN
The context obtaining described UE includes:
Described MME sends context request Context Request to described old SGSN, described
Context Request carry described UE access described SAE network time request message and described old
RAI and P-TMSI, or old RAI and TLLI;It is right that described old SGSN returns to described MME
The integrity protection authentication failed of described request message or do not have the message of checking;Described MME is according to subsidiary
The information of whole world unique temporary identity Additional GUTI, the described UE context preserved by self
Described UE is verified, or to the context having described UE of Additional GUTI instruction
MME sends described request message or this MME of safety verification message calls carries out integrity to described UE
Protection checking;Or described MME initiates security process to described UE, authenticates described UE;
Or,
According to described old RAI and P-TMSI or the instruction of old RAI and TLLI, described MME to
Described old SGSN sends Context Request, described Context Request and does not carry described UE and connect
Enter request message during described SAE network;Described MME is according to the information of Additional GUTI, logical
Cross the described UE context self preserved described UE is verified, or to Additional GUTI
The MME of the context having described UE of instruction sends described request message or safety verification message calls should
MME carries out integrity protection checking to described UE;Or described MME initiates safety to described UE
Process, authenticates described UE;
Or,
According to described old RAI and P-TMSI, or the instruction of old RAI and TLLI, described MME
Sending Context Request to described old SGSN, described Context Request checking safe to carry is led to
Cross information, and do not carry request message when described UE accesses SAE;Described MME is according to Additional
The information of GUTI, is verified described UE by the UE context of self preservation, or to
The MME of the context having described UE of Additional GUTI instruction sends described request message or safety
Checking this MME of message calls carries out integrity protection checking to described UE;Or described MME is to institute
State UE and initiate security process, described UE is authenticated.
Cut-in method the most according to claim 1, it is characterised in that described MME is to described old
SGSN obtains the context of described UE and includes:
If there being the context of described UE on described MME, described UE is accessed described by described MME
Request information authentication integrity protection during SAE network;
If the verification passes, described MME sends Context Request to described old SGSN, described
Context Request carries and is verified message.
Cut-in method the most according to claim 1, it is characterised in that described MME is according to described
The context that old RAI and P-TMSI or old RAI and TLLI obtains UE to old SGSN includes:
According to the instruction of Additional GUTI, described MME sends out to the MME of the context having UE
Send request message during UE described SAE network of access;
The MME of the described context having UE returns the integrity to described request message to described MME
The result of protection;
If the verification passes, described MME sends Context Request to described old SGSN, described
Context Request carries described old RAI/P-TMSI, or, carry described old RAI and TLLI
Be verified information;
According to described old RAI and P-TMSI, or, according to described old RAI and TLLI, described old
SGSN finds the context of UE;
According to the described information that is verified, UE is not verified by described old SGSN, and to described
MME returns the context of UE.
Cut-in method the most according to claim 1, it is characterised in that described MME is according to described
Old RAI and P-TMSI, or, described MME according to described old RAI and TLLI to old SGSN
The context obtaining described UE includes:
According to the instruction of Additional GUTI, described MME is to the MME of the context having described UE
Obtain safe context;
Described MME according to described safe context to described UE access described SAE network time request
Information authentication integrity protection;
If the verification passes, described MME sends Context Request to described old SGSN, described
Context Request carries described old RAI and P-TMSI, or, carry described old RAI and TLLI
Be verified information;
According to described old RAI and P-TMSI, or, described old RAI and TLLI, described old SGSN
Find the context of UE;
According to the described information that is verified, UE is not verified by described old SGSN, and to described
MME returns the context of UE.
Cut-in method the most according to claim 1, it is characterised in that if described UE carries old
RAI and P-TMSI, or, the GUTI that TLLI maps accesses described SAE network, and the most described UE is not
Tracing section updating request TAU Request message or attachment request Attach Request message are carried out completely
Property protection.
Cut-in method the most according to claim 1, it is characterised in that if described UE carries old
RAI and P-TMSI accesses described SAE network, or carries the GUTI described SAE of access that TLLI maps
Network, the most described UE carries packet TMSI signature P-TMSI Signature cell, and
And the Context Request message that described MME sends to old SGSN also carries P-TMSI Signature
Cell, UE is verified by request old SGSN.
9. the method accessed, it is characterised in that the method includes:
During user equipment (UE) access system architecture evolution SAE network, Mobility Management Entity MME will
Global unique temporary identity GUTI that described UE carries is mapped to old Routing Area Identifier old RAI and packet
Temporary Mobile Subscriber Identity P-TMSI, or, logical links temporary mark TLLI and packet are interim mobile
The form of ID signature P-TMSI Signature;
Old RAI and P-TMSI after described MME mapping, or, TLLI and P-TMSI Signature
To old Mobility Management Entity old MME or old service universal grouping wireless business supporting node old
SGSN obtains the context of UE;
Described old MME by described old RAI and P-TMSI, or, old RAI and TLLI and P-TMSI
Signature is reduced into GUTI, and the GUTI obtained according to reduction returns the upper of UE to described MME
Hereafter;Or,
Described old SGSN according to described old RAI and P-TMSI, or, old RAI and TLLI,
P-TMSI Signature obtains the context of UE, returns the context of UE to described MME.
10. the method accessed, it is characterised in that the method includes:
When user equipment (UE) access system architecture evolution SAE network,
If old node is Mobility Management Entity MME, described MME whole world unique temporary identity
GUTI obtains the context of described UE to old Mobility Management Entity old MME;
If described old node is Gn/Gp SGSN, the most described MME is reduced into old road described GUTI
Identified old RAI and packet TMSI P-TMSI by district, or be reduced into logical links and face
Time mark TLLI;And obtain the context of UE to old SGSN by the mark after described reduction;
If described old node is S4SGSN, the most described MME obtains to old SGSN with described GUTI
Take the context of UE;Described old SGSN is reduced into old RAI and P-TMSI described GUTI, or
Person is reduced into old RAI/TLLI mark, and is found by the mark after described reduction that described UE's is upper and lower
Described MME is returned to after literary composition.
11. 1 kinds of methods accessed, it is characterised in that the method includes:
When user equipment (UE) accesses 2G/3G network, service universal grouping wireless business supporting node
Old Routing Area Identifier old RAI that SGSN carries according to described UE and packet TMSI
P-TMSI, or, the logical links temporary mark TLLI carried according to described UE and the interim mobile use of packet
Family identification signature P-TMSI Signature is described 2G/3G network allocation or maps, and it is right to search
The old entity answered is old service universal grouping wireless business supporting node old SGSN or old mobile management
Entity old MME;
If old RAI and P-TMSI that described UE carries, or, TLLI and P-TMSI Signature
Be map, described old entity is old MME, described SGSN according to described old RAI and P-TMSI,
Or, TLLI/P-TMSI Signature reduces GUTI, and obtains UE with GUTI to described old MME
Context;Described old MME will find UE context according to GUTI and return to SGSN;
If old RAI and P-TMSI that UE carries, or, TLLI and P-TMSI Signature is institute
Stating 2G/3G network allocation, described old entity is old SGSN, and described SGSN is with described old RAI
And P-TMSI, or, TLLI obtains the context of UE to described old SGSN.
12. 1 kinds of mobile management entities, it is characterised in that described mobile management entity includes:
When user equipment (UE) access system architecture evolution SAE network, it is judged that it is complete that described UE carries
Ball unique temporary identity GUTI is SAE distribution or the module mapped;
If described GUTI is described SAE network allocation, with described GUTI to old mobile management
Entity old MME obtains the module of the context of UE;
If described GUTI be map, described GUTI be reduced into old Routing Area Identifier old RAI and
Packet TMSI P-TMSI, and lead to old service according to described old RAI and P-TMSI
The context of UE is obtained with grouping wireless business supporting node old SGSN, or, described GUTI
It is reduced into old RA and logical links temporary mark TLLI, and according to described old RA and TLLI to old
Service universal grouping wireless business supporting node old SGSN obtains the module of the context of described UE.
13. mobile management entities according to claim 12, it is characterised in that described in described judgement
Global unique temporary identity GUTI that UE carries is described SAE network allocation or the module mapped,
Specifically for
Check that in described GUTI, the flag bit of Mobility Management Entity group mark MMEGI is MMEGI
Mark or the mark of Location Area Code LAC;
If the mark of MMEGI, then judge that GUTI is SAE distribution;
If the mark of LAC, then judge that GUTI is to map.
14. mobile management entities according to claim 12, it is characterised in that described mobile management
Entity also includes:
If described UE carries old RAI and P-TMSI and accesses SAE, or carries the GUTI that TLLI maps
Access SAE, the most described UE and carry packet TMSI signature P-TMSI Signature cell,
And the Context Request message that MME sends to old SGSN also carries P-TMSI Signature
Cell, the unit that UE is verified by request old SGSN.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN201110241665.8A CN102761855B (en) | 2008-06-18 | 2009-01-05 | Access, obtain customer equipment context and the method and apparatus of customer equipment identification |
Applications Claiming Priority (8)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN200810039358X | 2008-06-18 | ||
CN200810039358 | 2008-06-18 | ||
CN200810039358.X | 2008-06-18 | ||
CN200810175964 | 2008-11-03 | ||
CN2008101759644 | 2008-11-03 | ||
CN200810175964.4 | 2008-11-03 | ||
CN201110241665.8A CN102761855B (en) | 2008-06-18 | 2009-01-05 | Access, obtain customer equipment context and the method and apparatus of customer equipment identification |
CN2009100035419A CN101610504B (en) | 2008-06-18 | 2009-01-05 | Method and device for accessing and obtaining user equipment context and user equipment identification |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN2009100035419A Division CN101610504B (en) | 2008-06-18 | 2009-01-05 | Method and device for accessing and obtaining user equipment context and user equipment identification |
Publications (2)
Publication Number | Publication Date |
---|---|
CN102761855A CN102761855A (en) | 2012-10-31 |
CN102761855B true CN102761855B (en) | 2016-08-10 |
Family
ID=43477772
Family Applications (4)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN2011102433456A Pending CN102307339A (en) | 2008-06-18 | 2009-01-05 | Access method and device, and method and device for acquiring user equipment context and user equipment identity |
CN201210283093.4A Active CN102821440B (en) | 2008-06-18 | 2009-01-05 | The method and apparatus accessing, obtaining customer equipment context and customer equipment identification |
CN201110241665.8A Active CN102761855B (en) | 2008-06-18 | 2009-01-05 | Access, obtain customer equipment context and the method and apparatus of customer equipment identification |
CN2012102831227A Pending CN102821381A (en) | 2008-06-18 | 2009-01-05 | Method and device for accessing and acquiring contexts and identifiers of user equipment |
Family Applications Before (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN2011102433456A Pending CN102307339A (en) | 2008-06-18 | 2009-01-05 | Access method and device, and method and device for acquiring user equipment context and user equipment identity |
CN201210283093.4A Active CN102821440B (en) | 2008-06-18 | 2009-01-05 | The method and apparatus accessing, obtaining customer equipment context and customer equipment identification |
Family Applications After (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN2012102831227A Pending CN102821381A (en) | 2008-06-18 | 2009-01-05 | Method and device for accessing and acquiring contexts and identifiers of user equipment |
Country Status (1)
Country | Link |
---|---|
CN (4) | CN102307339A (en) |
Families Citing this family (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
EP3266233B1 (en) | 2015-03-02 | 2020-05-06 | Samsung Electronics Co., Ltd. | Method and apparatus for providing service in wireless communication system |
WO2017052342A1 (en) | 2015-09-24 | 2017-03-30 | 삼성전자 주식회사 | Method for supporting lawful interception of remote prose ue in network |
SG11201811110VA (en) | 2016-07-01 | 2019-01-30 | Ericsson Telefon Ab L M | Systems and methods for user equipment (ue) registration |
WO2019041347A1 (en) * | 2017-09-04 | 2019-03-07 | Oppo广东移动通信有限公司 | Method and device for wireless communications |
CN112512035B (en) * | 2018-06-26 | 2022-04-29 | 华为技术有限公司 | Access method, device and system |
US11140655B2 (en) * | 2018-10-17 | 2021-10-05 | Mediatek Singapore Pte. Ltd. | GUTI allocation after establishment of mobile-terminated connection in mobile communications |
Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101098561A (en) * | 2006-06-14 | 2008-01-02 | 日本电气株式会社 | Communication system, operation control method and location management server |
Family Cites Families (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN100420333C (en) * | 2005-02-02 | 2008-09-17 | 华为技术有限公司 | Method for repositioning between support nodes in service general group wireless business |
CN100550804C (en) * | 2006-01-25 | 2009-10-14 | 华为技术有限公司 | A kind of network attached method and network attachment system |
CN101035308A (en) * | 2006-03-09 | 2007-09-12 | 华为技术有限公司 | Radio communication system and mobility management method |
CN101039510A (en) * | 2006-03-17 | 2007-09-19 | 华为技术有限公司 | Method for realizing equivalent routing area in wireless evolution network |
CN101043705A (en) * | 2006-03-21 | 2007-09-26 | 华为技术有限公司 | Method and system for limiting signaling of mobile management in wireless evolvement network |
US20070254667A1 (en) * | 2006-04-28 | 2007-11-01 | Joanna Jokinen | Inter-MME handover in evolved communication systems |
US20070280177A1 (en) * | 2006-05-31 | 2007-12-06 | Nokia Corporation | Managing user profile information in a mobile telecommunications network |
CN101128030B (en) * | 2006-08-16 | 2010-04-14 | 华为技术有限公司 | Context negotiation method |
CN100563390C (en) * | 2006-08-16 | 2009-11-25 | 华为技术有限公司 | Obtain the method for access system context |
-
2009
- 2009-01-05 CN CN2011102433456A patent/CN102307339A/en active Pending
- 2009-01-05 CN CN201210283093.4A patent/CN102821440B/en active Active
- 2009-01-05 CN CN201110241665.8A patent/CN102761855B/en active Active
- 2009-01-05 CN CN2012102831227A patent/CN102821381A/en active Pending
Patent Citations (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101098561A (en) * | 2006-06-14 | 2008-01-02 | 日本电气株式会社 | Communication system, operation control method and location management server |
Also Published As
Publication number | Publication date |
---|---|
CN102761855A (en) | 2012-10-31 |
CN102821440B (en) | 2016-06-29 |
CN102821381A (en) | 2012-12-12 |
CN102821440A (en) | 2012-12-12 |
CN102307339A (en) | 2012-01-04 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN102821382B (en) | A kind of device for accessing | |
JP6983913B2 (en) | SMF insert method and AMF entity | |
CN101511079B (en) | Method and device for accessing original network through evolution network temporary mark | |
CN102761855B (en) | Access, obtain customer equipment context and the method and apparatus of customer equipment identification | |
CN102355743B (en) | Management method and management device for UE (User Equipment) context information | |
CN106211311A (en) | A kind of user equipment registration is to the method and apparatus of network | |
CN103369500B (en) | Transmission method and device of CSG subscription information | |
CN102448185B (en) | Remote access method and equipment | |
CN104918246A (en) | Authentication method and system, ProSe (Proximity-based Service) functional entities and UE (User Equipment) |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
C06 | Publication | ||
PB01 | Publication | ||
C10 | Entry into substantive examination | ||
SE01 | Entry into force of request for substantive examination | ||
C14 | Grant of patent or utility model | ||
GR01 | Patent grant |