CN105379354A

CN105379354A - Method for MME reselection and MME

Info

Publication number: CN105379354A
Application number: CN201480029829.2A
Authority: CN
Inventors: 时晓岩; 张万强
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2014-06-17
Filing date: 2014-06-17
Publication date: 2016-03-02
Anticipated expiration: 2034-06-17
Also published as: US20190159089A1; KR101886748B1; US20180249392A1; KR20170016977A; CN111510968B; CN111510968A; EP3678414A1; US10212632B2; JP6386102B2; CN105379354B; EP3145244B1; EP3145244A4; KR102024332B1; EP3145244A1; KR20180089571A; JP2017522796A; US10004016B2; EP3678414B1; US10412647B2; US20170099623A1

Abstract

Provided are a method for MME (Mobility Management Entity) reselection and an MME. The method enables UE (User Equipment) to timely use a proper MME to perform an access request procedure. The method comprises: receiving an access request message sent by user equipment UE, the access request message carrying the identification information of the UE (801); determining, according to the identification information of the UE, the type of an MME to which the UE needs to be accessed (802); reselecting a second MME according to the type of the MME to which the UE needs to be accessed (803); and forwarding the access request message to the second MME to enable the second MME to perform the access request procedure of the UE (804). The method for MME reselection is applicable to the field of communication technology.

Description

Method for MME reselection and MME

The method and MME of a kind of MME gravity treatments

Technical field

The present invention relates to the method and MME of communication technical field, more particularly to a kind of MME gravity treatments.

Background technology

For signing the legitimate user equipment (User Equipment, abbreviation UE) into fidonetFido with operator, UE needs to complete the flow that registration is attached to network on carrier network in each start；Or UE leaves the network coverage and exceeded after preset time, it is necessary to complete the flow that registration is attached to network on carrier network again completely；Or UE needs when entering another region from a region of carrier network to carry out the flow of routing region updating, the business that such UE can just have been opened by Internet normal use.

At present, by being all not quite similar in the UE of the net business opened and Freight Basis, operator is wished mobility management entity (Mobility Management Entity, abbreviation MME) carry out classification setting, the UE of different business access request has been opened in different MME processing, it so will logically open user's separate management of different business, it is possible to increase the efficiency of management of common carrier.For example, to the user equipment of all signing M2M business, being managed using one group of proprietary MME；And the user equipment of all unsigned M2M business is managed using another set MME.

But in Long Term Evolution（Long Term Evolution, abbreviation LTE) in network, when UE performs the flow of attachment or routing region updating, enode eNodeB only relies on topology network and selects MME for UE.So eNodeB is possible to choose the MME of mistake for UE.Therefore, it is divided into multiclass in MME, in the case of providing service to the UE for opening different service types, how to select MME is urgent problem to be solved.

The content of the invention

Embodiments of the invention provide the method and MME of a kind of MME gravity treatments so that UE timely can perform access request flow using correct MME.

To reach above-mentioned purpose, embodiments of the invention are adopted the following technical scheme that：

There is provided a kind of first mobility management entity MME, the first MME for first aspect Including：

Receiving unit, the access request message for receiving user equipment (UE) transmission, the access request message carries the identification information of the UE；

Determining unit, for the identification information according to the UE, determines that the UE needs the MME type of access；

Gravity treatment unit, the MME types that UE needs to access, the MME of gravity treatment 1 the 2nd are stated for shelter;

Transmitting element, for the access request message to be forwarded into the 2nd MME, to cause the 2nd MME to perform the access request flow of the UE.

With reference in a first aspect, in the first possible embodiment,

The receiving unit, is additionally operable to receive the interaction message of the UE and the 2nd MME in the access request flow is performed；

The transmitting element, is additionally operable to forward the interaction message of the UE and the 2nd MME in the access request flow is performed.

With reference to the first possible embodiment of first aspect or first aspect, in second of possible embodiment, the determining unit specifically for：

According to the identification information of the UE and pre-configured configured information, determine that the UE needs the MME type of access, wherein, the pre-configured configured information includes the correspondence relationship information of UE identification information and the MME of UE needs access type.

With reference to the first possible embodiment of first aspect or first aspect, in the third possible embodiment, the determining unit specifically for：

According to the identification information of the UE, the type information for the MME for including the UE needs access in the subscription data of the UE, the subscription data is obtained from subscribed services device HSS；

According to the subscription data, determine that the UE needs the MME type of access.With reference to the first possible embodiment of first aspect or first aspect, in the 4th kind of possible embodiment, the determining unit specifically for： Shelter states UE identification information, and the mobile management contextual information of the UE is obtained from the UE former MME accessed, and the mobile management contextual information includes the MME of UE needs access type information；

According to the mobile management contextual information, determine that the UE needs the MME type of access.

According to the 4th of first aspect the kind of possible embodiment, in the 5th kind of possible embodiment, the transmitting element specifically for, the mobile management contextual information of the access request message and the UE is forwarded to the 2nd MME, to cause the 2nd MME to perform the access request flow of the UE according to the access request message and the UE mobile management contextual information.

Second aspect includes there is provided a kind of second mobility management entity MME, the 2nd MME：

Receiving unit, the mark of the UE is included for receiving in the access request message that the user equipment (UE) of the first MME forwardings is sent, the access request message；

Processing unit, the access request flow for performing the UE according to the access request message.

With reference to second aspect, in the first possible embodiment, the 2nd MME also includes：

Transmitting element, for the processing unit according to the access request message perform described in

In UE access request flow, by the first MME to the UE send interaction disappear receiving unit described in it specifically for, in the access request flow that the processing unit performs the UE according to the access request message, the interaction message that the UE is sent is received by the first MME.

With reference to the first possible embodiment of second aspect or second aspect, in second of possible embodiment,

The receiving unit, is additionally operable to receive the UE of the first MME forwardings shifting Dynamic managing context information；

The processing unit is specifically for performing the access request flow of the UE according to the access request message and the UE mobile management contextual information.

With reference to the first possible embodiment of second aspect or second aspect, in the third possible embodiment,

The transmitting element, is additionally operable to, according to the UE marks carried in the access request message, mobile management context request message be sent to UE former MME；

The receiving unit, is additionally operable to receive the mobile management context response information that the former MME of the UE is sent, wherein the mobile management context response information carries the mobile management contextual information of the UE；

The third aspect includes there is provided a kind of first mobility management entity MME, the first MME：

Receiver, the access request message for receiving user equipment (UE) transmission, the access request message carries the identification information of the UE；

Processor, for the identification information according to the UE, determines that the UE needs the MME type of access；And the blunt MME types for needing to access according to the UE of, the MME of gravity treatment 1 the 2nd;

Transmitter, for the access request message to be forwarded into the 2nd MME, to cause the 2nd MME to perform the access request flow of the UE.

With reference to the third aspect, in the first possible embodiment,

The receiver, is additionally operable to receive the interaction message of the UE and the 2nd MME in the access request flow is performed；

The transmitter, is additionally operable to forward the interaction message of the UE and the 2nd MME in the access request flow is performed.

It is possible at second with reference to the first possible embodiment of the third aspect or the third aspect In embodiment, the processor specifically for：

With reference to the first possible embodiment of the third aspect or the third aspect, in the third possible embodiment, the processor specifically for：

According to the subscription data, determine that the UE needs the MME type of access.With reference to the first possible embodiment of the third aspect or the third aspect, in the 4th kind of possible embodiment, the processor specifically for：

Shelter states UE identification information, and the mobile management contextual information of the UE is obtained from the UE former MME accessed, and the mobile management contextual information includes the MME of UE needs access type information；

According to the 4th of the third aspect the kind of possible embodiment, in the 5th kind of possible embodiment, the transmitter specifically for, the mobile management contextual information of the access request message and the UE is forwarded to the 2nd MME, to cause the 2nd MME to perform the access request flow of the UE according to the access request message and the UE mobile management contextual information.

Fourth aspect includes there is provided a kind of second mobility management entity MME, the 2nd MME：

Receiver, the mark of the UE is included for receiving in the access request message that the user equipment (UE) of the first MME forwardings is sent, the access request message；

Processor, the access request stream for performing the UE according to the access request message Journey.

With reference to fourth aspect, in the first possible embodiment, the 2nd MME also includes：

Transmitter, in the access request flow that the processor performs the UE according to the access request message, interaction message to be sent to the UE by the first MME；The receiver is specifically in the access request flow that the processor performs the UE according to the access request message, the interaction message that the UE is sent is received by the first MME.

With reference to the first possible embodiment of fourth aspect or fourth aspect, in second of possible embodiment,

The receiver, is additionally operable to receive the UE of the first MME forwardings mobile management contextual information；

The processor is specifically for performing the access request flow of the UE according to the access request message and the UE mobile management contextual information.

With reference to the first possible embodiment of fourth aspect or fourth aspect, in the third possible embodiment,

The transmitter, is additionally operable to, according to the UE marks carried in the access request message, mobile management context request message be sent to UE former MME；

The receiver, is additionally operable to receive the mobile management context response information that the former MME of the UE is sent, wherein the mobile management context response information carries the mobile management contextual information of the UE；

5th aspect is there is provided a kind of method of mobility management entity MME gravity treatments, and this method includes：

The access request message that user equipment (UE) is sent is received, the access request message carries the identification information of the UE； According to the identification information of the UE, determine that the UE needs the MME type of access；

The MME types for needing to access according to the UE, the MME of gravity treatment 1 the 2nd;The access request message is forwarded to the 2nd MME, to cause the 2nd MME to perform the access request flow of the UE.

With reference to the 5th aspect, in the first possible embodiment, the access request message is being forwarded to the 2nd MME, after the access request flow to cause the 2nd MME execution UE, this method also includes：

Receive the interaction message of the UE and the 2nd MME in the access request flow is performed；

Forward the interaction message of the UE and the 2nd MME in the access request flow is performed.

With reference to the 5th aspect or the first possible embodiment of the 5th aspect, in second of possible embodiment, shelter states UE identification information, determines that the UE needs the MME accessed type to specifically include：

With reference to the 5th aspect or the first possible embodiment of the 5th aspect, in the third possible embodiment, shelter states UE identification information, determines that the UE needs the MME type of access, specifically includes：

According to the subscription data, determine that the UE needs the MME type of access.With reference to the 5th aspect or the first possible embodiment of the 5th aspect, in the 4th kind of possible embodiment, shelter states UE identification information, determines that the UE needs the MME accessed Type, specifically include：

According to the 4th kind of possible embodiment of the 5th aspect, in the 5th kind of possible embodiment, it is forwarded to by the access request message after the 2nd MME, this method also includes：The mobile management contextual information of the UE is forwarded to the 2nd MME.

6th aspect is there is provided a kind of method of mobility management entity MME gravity treatments, and this method includes：

Receive the mark for including the UE in the access request message that the user equipment (UE) of the first MME forwardings is sent, the access request message；

The access request flow of the UE is performed according to the access request message.

With reference to the 6th aspect, in the first possible embodiment, in the access request flow that the UE is performed according to the access request message, specifically include：

Interaction message is sent to the UE by the first MME, and the interaction message that the UE is sent is received by the first MME.

With reference to the 6th aspect or the first possible embodiment of the 6th aspect, in second of possible embodiment, before the access request flow of the UE is performed according to the access request message, this method also includes：

Receive the UE of the first MME forwardings mobile management contextual information；The access request flow of the UE is performed according to the access request message, is specifically included：

The access request flow of the UE is performed according to the access request message and the UE mobile management contextual information.

It is possible at the third with reference to the 6th aspect or the first possible embodiment of the 6th aspect In embodiment, after the access request message that the user equipment (UE) for receiving the first MME forwardings is sent, this method also includes：

According to the UE marks carried in the access request message, mobile management context request message is sent to UE former MME；

Receive the mobile management context response information that the former MME of the UE is sent, wherein described mobile management context response information carries the mobile management context letter of the UE according to access request message execution UE access request flow, specifically includes：

The method and MME of MME gravity treatments provided in an embodiment of the present invention, based on technical scheme described above, because the first MME can reselect the MME that the UE needs to access for UE, that is the 2nd MME, and UE access request message is forwarded to the 2nd MME, and the 2nd MME can according to the first MME forward UE access request message perform UE access request flow so that UE can timely using correct MME perform access request flow.

Brief description of the drawings

In order to illustrate more clearly about the embodiment of the present invention or technical scheme of the prior art, the required accompanying drawing used in embodiment or description of the prior art will be briefly described below, apparently, drawings in the following description are only some embodiments of the present invention, for those of ordinary skill in the art, on the premise of not paying creative work, other accompanying drawings can also be obtained according to these accompanying drawings.

Fig. 1 is LTE evolved packet system EPS wireless network architecture figures；

Fig. 2 is a kind of interaction schematic diagram of LTE attachment flow；

Fig. 3 is a kind of interaction schematic diagram of LTE routing region updating flow；

Fig. 4 is a kind of first MME composition structural representation provided in an embodiment of the present invention；Fig. 5 is a kind of 2nd MME composition structural representation provided in an embodiment of the present invention； Fig. 5 a are another 2nd MME provided in an embodiment of the present invention composition structural representation；

Fig. 6 is a kind of first MME composition structural representation provided in an embodiment of the present invention；Fig. 7 is a kind of 2nd MME composition structural representation provided in an embodiment of the present invention；Fig. 7 a are another 2nd MME provided in an embodiment of the present invention composition structural representation；

Fig. 8 is that a kind of method flow schematic diagram Fig. 9 of MME gravity treatments provided in an embodiment of the present invention is the interaction schematic diagram one that a kind of method flow schematic diagram Figure 10 of MME gravity treatments provided in an embodiment of the present invention is a kind of method execution attachment flow of MME gravity treatments provided in an embodiment of the present invention；

Fig. 11 performs the interaction schematic diagram two of attachment flow for a kind of method of MME gravity treatments provided in an embodiment of the present invention；

Figure 12 performs the interaction schematic diagram one of routing region updating flow for a kind of method of MME gravity treatments provided in an embodiment of the present invention；

Figure 13 performs the interaction schematic diagram two of routing region updating flow for a kind of method of MME gravity treatments provided in an embodiment of the present invention.

Embodiment

Below in conjunction with the accompanying drawing in the embodiment of the present invention, the technical scheme in the embodiment of the present invention is clearly and completely described, it is clear that described embodiment is only a part of embodiment of the invention, rather than whole embodiments.Based on the embodiment in the present invention, the every other embodiment that those of ordinary skill in the art are obtained under the premise of creative work is not made belongs to the scope of protection of the invention.

In addition, succinct for the description of following each embodiments, several related definitions given below are specific as follows：

First MME:According to topology network it is the selected MME of UE for eNodeB. 2nd MME:For identification informations of the first MME according to the UE, it is determined that the UE need the MME accessed, wherein the UE needs the MME accessed to be referred to as the 2nd MME.

Former MME:The MME of UE attachment flows is performed before the request of this routing region updating is initiated for UE or the MME of previous routing region updating flow is performed.

If specifically, before the request of this routing region updating is initiated, the last access request that UE is initiated and completed is attach request, then original MME refers to the MME for performing UE attachment flows herein;If before the request of this routing region updating is initiated, the last access request that UE is initiated and completed is asked for routing region updating, then original MME refers to the MME for performing a upper routing region updating flow herein.

It should be noted that above-mentioned each definition is applied to following each embodiments, it is described collectively, is repeated no more below herein.

LTE is referred to as 3.9G by popular, and the data download capabilities with 100Mbps are considered the mainstream technology from 3 G to 4G evolution.Evolved packet core（Evolved Packet Core, abbreviation EPC) it is the scheme that a set of help operator provides the advanced good business of mobile broadband month by using LTE technologies.Core net evolution tendency is EPC in LTE, EPC and the Universal Terrestrial wireless access network of evolution (Evolved Universal Terrestrial Radio Access Network, abbreviation EUTRAN) are combined and are referred to as evolved packet system（Evolved Packet System, abbreviation EPS).

Wherein, EPS wireless network architectures are as shown in figure 1, include：UE, EUTRAN MME, gateway（Serving Gateway, abbreviation S-GW), grouped data network gateway（Packet Data Network Gateway, abbreviation P-GW), HSS, general packet radio service technological service supporting node（Serving General Packet Radio Service Support Node, abbreviation SGSN), Policy and Charging Rules Function（Policy and Charging Rules Function, abbreviation PCRF), and operator can provide the network entity such as server of IP services.

Specifically, main network entity function is as follows： EUTRAN:The network being made up of multiple eNodeB, realizes radio physical layer function, scheduling of resource and RRM, wireless access control and mobile management function to ps domain.

Wherein, eNodeB is connected by interface in the user plane S1-U with S-GW, for transmitting user data；It is connected by chain of command interface S 1-MME with MME, using functions such as S1-AP protocol realizations RAB controls.

MME:It is responsible for all control plane functions of user conversation management, including NAS signaling and security setting, the management of tracking area list, P-GW and S-GW selection etc..

S-GW:It is responsible for UE data transfer, forwarding and route handoff etc., and local mobile anchor point when switching as UE between eNodeB（For each UE, each moment only has a S-GW and serviced for it).

P-GW:The anchor point connected as PDN, is responsible for distribution UE IP address, UE data message filtering, speed control, generation charge information etc..

Specifically, UE is by attachment flow or routing region updating flow, accesses EPS networks and create packet data network（Packet Data Gateway, abbreviation PDN) connection, in the process, P-GW is that user equipment distributes IP address, and UE connects the data transfer realized with external network by the IP address.

First, for the ease of the understanding of the present invention, UE attachment flow in the prior art and routing region updating flow are first briefly described below.

Specifically, the implementation process of UE attachment flow is as shown in Fig. 2 specific as follows：

201st, UE sends Attach Request message to eNodeB.

Wherein, the information such as IMSI, UE core network ability, the discontinuous reception parameters that UE is specified, Encryption Options transmission mark, type of attachment, NAS sequence numbers, NAS- medium access control are included in the Attach Request message.

202nd, the UE Attach Request messages sent are transmitted to the first MME by eNodeB.

Wherein, it further comprises customer position information in the Attach Request message.

203a, the first MME and HSS complete the authentication to UE.

203b, the first MME complete the Non-Access Stratum with UE（Non-Access-Stratum, Abbreviation NAS) message security setting.

Specifically, the first MME completes the security setting with UE NAS message, such as integrity protection, cipher mode and key information.

204th, the first MME and HSS complete interacting for location update request message and position updating request confirmation message.

Specifically, first MME sends location update request message to HSS, MME positional information where HSS updates stored UE, home position updates request confirmation message to the first MME after the completion of renewal, while returning to UE signing information to the first MME.

205 the oneth MME, which are sent, creates conversation request message to S-GW.

Specifically, the first MME is that UE selects S-GW and P-GW according to UE signing information, and send the S-GW for creating conversation request message to selection.

Wherein, the IMSI for including UE in conversation request message that creates is, it is necessary to the P-GW of access address, access technology type, customer position information, EPS carrying marks etc..

206th, S-GW is connected and is sent establishment conversation request message to P-GW.

Specifically, S-GW creates default bearer contextual information, and according to the P-GW accessed the need for including in the conversation request message address, connect and send establishment conversation request message to P-GW.

Wherein, the default bearer contextual information includes for the Tunnel End Point Identifier (Tunnel End Point Identifier, abbreviation TEID) in default bearer distributing user face etc..

Wherein, it is described to create the user plane address for including IMSI, S-GW in conversation message, S-GW user planes TEID, access technology type, customer position information, EPS carrying marks etc..

207 P-GW, which are returned, creates conversational response message to S-GW.

Specifically, P-GW creates default bearer contextual information, the charging identifier of default bearer is generated, and returns to establishment conversational response message to S-GW.

Wherein, the default bearer contextual information includes for default bearer distributing user face TEID etc.. Wherein, it is described to create the information such as the address for including P-GW user planes in conversational response message, TEID, EPS carrying mark of P-GW user planes, the IP address for distributing to UE；Since this step, P-GW starts to forward initial downlink data；And Slow deposits the downlink data received from P-GW since S-GW this step.

208th, S-GW, which is returned, creates conversational response message to the first MME.

Wherein, include the IP address for distributing to UE, the address of S-GW user plane, S-GW user plane TEID, EPS bearer quality of service (Quality of Service, abbreviation QoS), EPS carrying marks etc. in the establishment conversational response message.

209th, the first MME sends initial context and sets up request message to eNodeB.

Wherein, the initialization context, which is set up in request message, includes the address that EPS carries QoS, EPS carrying marks, and S-GW user plane, the information such as S-GW user plane TEID；The initialization context sets up in request message the content that further comprises the attachment received message that the first MME is sent to UE by eNodeB, including distributes to UE IP address, and EPS carrying marks, EPS carries the information such as QoS.

210th, eNodeB sends radio resource control and connects reconfiguration message to UE.

Wherein, the content that the first MME is sent to UE attachment received message by eNodeB is further comprises in the radio resource control connection reconfiguration message, including distributes to UE IP address, EPS carrying marks, EPS carries the information such as QoS.

211st, UE sends radio resource control connection and reconfigures completion message to eNodeB.

212nd, eNodeB sends initialization context and sets up response message to the first MME.

Wherein, the initialization context sets up in response message the TEID for including that eNodeB is user plane distribution, address of eNodeB user plane etc..

213rd, UE sends directly transmission message to eNodeB.

Wherein, the content that UE is sent to the first MME attachment completion message by eNodeB is included in the direct transmission message.

214th, eNodeB forwardings attachment completion message is to the first MME.

215th, the first MME sends bearer update request message to S-GW. Set up specifically, the first MME receives initialization context after response message and attachment completion message, the first MME sends bearer update request message to S-GW.

Wherein, the address of TEID, eNodeB that eNodeB distributes for user plane user plane is included in the bearer update request message.

216th, S-GW sends bearer update response message to the first MME, and starts to send the downlink data message that Slow is deposited since step 207 to eNodeB.

The implementation process of UE routing region updating flow is as shown in figure 3, specific as follows：

301st, UE sends routing region updating request message to eNodeB.

Wherein, include UE global unique temporary identity (Globally Unique Temporary Identity in the routing region updating request message, abbreviation GUTI), the mark is distributed by former MME, and the GUTI includes the unique MME marks in the whole world（English:Globally Unique MME Identifier, abbreviation GUMMEI), GUMMEI distributes to UE's by the MME for performing UE attachment flows or the MME for performing a upper routing region updating flow.

302nd, eNodeB forwards routing region updating request message to the first MME.

Specifically, eNodeB is that UE selects a MME, i.e. the first MME according to topology network, and UE routing region updating is forwarded to ask to the first MME.

303rd, the first MME sends mobile management context request message to former MME.

Specifically, former MME addresses of the first MME according to where the GUMMEI information included in GUTI knows UE mobile management contexts, mobile management context request message is sent to former MME.

Wherein, UE GUTI is included in the mobile management context request message.

304th, original MME returns to mobile management context response information to the first MME.

Specifically, the blunt GUTI according to the UE of original MME ability determines UE mobile management context, UE mobile management context is returned into the first MME in mobile management context response information.

305a, the first MME and HSS complete the authentication to UE.

305b, the first MME complete the security setting with UE NAS message. Specifically, the first MME completes the security setting with UE NAS message, such as integrity protection, cipher mode and key information.

It should be noted that the step is to be based on 304.

If including former MME and UE safe context in the mobile management context for returning to the first MME in 304 by former MME, without this step, the first MME need not carry out the security setting of NAS message with UE.

If being returned to by former MME in 304 does not include original MME and UE safe context in the first MME mobile management context, need to carry out the security setting of NAS message by the first MME and UE in this step.

306th, the first MME sends context acknowledgement message to former MME.

Wherein, include S-GW change instructions in the context message, specify whether S-GW in the routing region updating flow is changed, in order to which whether former MME decision-makings delete the former S-GW of storage user's context, its Central Plains S-GW is the S-GW that former MME is selected to UE.

307th, the first MME initiates bearer update request message to S-GW.

Specifically, the first MME initiates bearer update request message to S-GW, and the positional information of current UE is provided etc..

308th, S-GW sends bearer update request message to P-GW.

309th, P-GW returns to bearer update response message to S-GW.

310th, S-GW sends bearer update response message to the first MME.

311st, the first MME sends location update request message to HSS.

Specifically, the first MME sends location update request message to HSS, HSS updates stored UE positional information, and the updating location information that wherein HSS is serviced UE by former MME is the positional information that UE is serviced by the first MME.

312nd, HSS and original MME complete interacting for position deletion request message and position removal request confirmation message.

Removed specifically, HSS sends position deletion request message to former MME, former MME User's mobile management context, home position deletes confirmation message to HSS.

313rd, HSS home positions update request confirmation message to the first MME.

Specifically, HSS update UE where the first MME positional information after, home position update request confirmation message give the first MME, while send user contracting data to the first MME.

314th, the first MME sends routing region updating and accepts message to eNodeB.

Wherein, it is the GUTI that UE is redistributed that the first MME is included in the routing region updating received message.

315th, eNodeB forwards routing region updating to accept message to UE.

During the implementing of above-mentioned flow, when performing the flow of attachment flow or routing region updating due to UE, eNodeB only relies on the MME that topology network selects MME, such eNodeB to be possible to choose mistake for UE for UE.

In view of this, the embodiments of the invention provide the first MME of one kind, as shown in figure 4, the MME includes：Receiving unit 401, determining unit 402, gravity treatment unit 403, transmitting element 404.

The receiving unit 401, the access request message for receiving user equipment (UE) transmission, the access request message carries the identification information of the UE.

The determining unit 402, for the identification information according to the UE, determines that the UE needs the MME type of access.

The gravity treatment unit 403, the MME types that UE needs to access, the MME of gravity treatment 1 the 2nd are stated for shelter.

The transmitting element 404, for the access request message to be forwarded into the 2nd MME, to cause the 2nd MME to perform the access request flow of the UE.

Optionally, the receiving unit 401, is additionally operable to receive the interaction message of the UE and the 2nd MME in the access request flow is performed；

Optionally, the transmitting element 402, is additionally operable to forward the interaction message of the UE and the 2nd MME in the access request flow is performed. Wherein, the determining unit 402 specifically for：

Optionally, the determining unit 402 obtains the type information for the MME for including the UE needs access in the subscription data of the UE, the subscription data also particularly useful for the identification information according to the UE from subscribed services device HSS；According to the subscription data, determine that the UE needs the MME type of access.

Optionally, the determining unit 402 is also particularly useful for the identification information according to the UE, the mobile management contextual information of the UE is obtained from the UE former MME accessed, the mobile management contextual information includes the MME of UE needs access type information；According to the mobile management contextual information, determine that the UE needs the MME type of access.

Optionally, the transmitting element 404 specifically for, the mobile management contextual information of the access request message and the UE is forwarded to the 2nd MME, to cause the 2nd MME to perform the access request flow of the UE according to the access request message and the UE mobile management contextual information.

The embodiments of the invention provide the first MME of one kind, based on technical scheme described above, because the first MME can reselect the MME that the UE needs to access for UE, that is the 2nd MME, and UE access request message is forwarded to the 2nd MME so that UE timely can perform access request flow using correct MME.

The MME of one kind the first provided based on above-described embodiment, the embodiment of the present invention additionally provides the 2nd MME of one kind, as shown in figure 5, the MME includes：Receiving unit 501 and processing unit 502.

The receiving unit 501, the mark of the UE is included for receiving in the access request message that the user equipment (UE) of the first MME forwardings is sent, the access request message；The processing unit 502, the access request flow for performing the UE according to the access request message； Optionally, as shown in Figure 5 a, the 2nd MME also includes：

Transmitting element 503, in the access request flow that the processing unit 502 performs the UE according to the access request message, interaction message to be sent to the UE by the first MME；

The receiving unit 501 is specifically in the access request flow that the processing unit 502 performs the UE according to the access request message, the interaction message that the UE is sent is received by the first MME.

Optionally, the receiving unit 501, is additionally operable to receive the UE of the first MME forwardings mobile management contextual information；

The processing unit 502 is specifically for performing the access request flow of the UE according to the access request message and the UE mobile management contextual information.

Optionally, the transmitting element 503, is additionally operable to, according to the UE marks carried in the access request message, mobile management context request message be sent to UE former MME；The receiving unit 501, is additionally operable to receive the mobile management context response information that the former MME of the UE is sent, wherein the mobile management context response information carries the mobile management contextual information of the UE；

The embodiments of the invention provide the 2nd MME of one kind, based on technical scheme described above, because the 2nd MME can perform UE access request flow according to the first MME UE forwarded access request message so that UE timely can perform access request flow using correct MME.

The MME of one kind the first provided based on above-described embodiment, the embodiment of the present invention additionally provides the first MME of one kind, as shown in fig. 6, the first MME includes：Receiver 601, processor 602, transmitter 603, the communication bus 605 of memory 604 and first, for realizing the connection communication between these devices.

Wherein, processor 602 is probably a central processing unit（Central Processing Unit, abbreviation CPU), or specific integrated circuit（ Application Specific Integrated Circuit, abbreviation ASIC), or it is arranged to implement one or more integrated circuits of the embodiment of the present invention.

Processor 602 is used to performing the executable program code that is stored in memory 604, and such as computer program runs program corresponding with executable code.

Memory 604 is used to store executable program code, and the program code includes computer-managed instruction.Memory 604 may include high-speed RAM memory, it is also possible to also including nonvolatile memory（Non- volatile memory), for example, at least one magnetic disk storage.

First communication bus 605 can be industry standard architecture（Industry Standard Architecture, abbreviation ISA) bus, sunset fore-telling portion apparatus interconnection（Peripheral Component, abbreviation PCI) bus or extended industry-standard architecture（Extended Industry Standard Architecture, abbreviation EISA) bus etc..The bus 605 can be divided into address bus, data/address bus, controlling bus etc..For ease of representing, only represented in Fig. 6 with a thick line, it is not intended that only one bus or a type of bus.

Specifically, the receiver 601, the access request message for receiving user equipment (UE) transmission, the access request message carries the identification information of the UE；

The processor 602, for the identification information according to the UE, determines that the UE needs the MME type of access；And the MME types for needing to access according to the UE, the MME of gravity treatment 1 the 2nd;

The transmitter 603, for the access request message to be forwarded into the 2nd MME, to cause the 2nd MME to perform the access request flow of the UE.

Optionally, the receiver 601, is additionally operable to receive the interaction message of the UE and the 2nd MME in the access request flow is performed；

The transmitter 603, is additionally operable to forward the interaction message of the UE and the 2nd MME in the access request flow is performed.

Wherein, the processor 602 is specifically for according to the identification information of the UE and pre-configured configured information, determining that the UE needs the MME type of access, wherein, the pre-configured configured information includes UE identification information and the MME of UE needs access class The correspondence relationship information of type.

Optionally, the processor 602, UE identification information is stated also particularly useful for shelter, and the type information for the MME for including the UE needs access in the subscription data of the UE, the subscription data is obtained from subscribed services device HSS；According to the subscription data, determine that the UE needs the MME type of access.

Optionally, the processor 602, UE identification information is stated also particularly useful for shelter, the mobile management contextual information of the UE is obtained from the UE former MME accessed, the mobile management contextual information includes the MME of UE needs access type information；According to the mobile management contextual information, determine that the UE needs the MME type of access.

Optionally, the transmitter 603 specifically for, the mobile management contextual information of the access request message and the UE is forwarded to the 2nd MME, to cause the 2nd MME to perform the access request flow of the UE according to the access request message and the UE mobile management contextual information.

The MME of one kind the 2nd provided based on above-described embodiment, the embodiment of the present invention additionally provides the 2nd MME of one kind, as shown in fig. 7, the 2nd MME includes：Receiver 701, processor 702, the communication bus 704 of memory 703 and first, for realizing the connection communication between these devices.

Wherein, processor 702 is probably a central processing unit（Central Processing Unit, abbreviation CPU), or specific integrated circuit（Application Specific Integrated Circuit, abbreviation ASIC), or it is arranged to implement one or more integrated circuits of the embodiment of the present invention.

Processor 702 is used to performing the executable program code that is stored in memory 703, and such as computer program runs program corresponding with executable code. Memory 703 is used to store executable program code, and the program code includes computer-managed instruction.Memory 703 may include high-speed RAM memory, it is also possible to also including nonvolatile memory（Non- volatile memory), for example, at least one magnetic disk storage.

First communication bus 704 can be industry standard architecture（Industry Standard Architecture, abbreviation ISA) bus, sunset fore-telling portion apparatus interconnection（Peripheral Component, abbreviation PCI) bus or extended industry-standard architecture（Extended Industry Standard Architecture, abbreviation EISA) bus etc..The bus 704 can be divided into address bus, data/address bus, controlling bus etc..For ease of representing, only represented in Fig. 7 with a thick line, it is not intended that only one bus or a type of bus.

Specifically, the receiver 701, the mark of the UE is included for receiving in the access request message that the user equipment (UE) of the first MME forwardings is sent, the access request message；

The processor 702, the access request flow for performing the UE according to the access request message；

Optionally, as shown in Figure 7a, the 2nd MME also includes：

Transmitter 705, in the access request flow that the processor 702 performs the UE according to the access request message, interaction message to be sent to the UE by the first MME；

The receiver 701 is specifically in the access request flow that the processor 702 performs the UE according to the access request message, the interaction message that the UE is sent is received by the first MME.

Optionally, the receiver 701, is additionally operable to receive the UE of the first MME forwardings mobile management contextual information；

The processor 702 is specifically for performing the access request flow of the UE according to the access request message and the UE mobile management contextual information.

Optionally, the transmitter 705, is additionally operable to, according to the UE marks carried in the access request message, mobile management context request message be sent to UE former MME； The receiver 701, is additionally operable to receive the mobile management context response information that the former MME of the UE is sent, wherein the mobile management context response information carries the mobile management contextual information of the UE；

The MME of one kind the first provided based on above-described embodiment, the embodiments of the invention provide a kind of method of MME gravity treatments, this method executive agent is the first MME, as shown in figure 8, this method includes：

801st, the access request message that UE is sent is received, the access request message carries the identification information of the UE.

Wherein, UE is according to eNodeB system broadcast message, select suitable cell resident and initiate access request flow to eNodeB, select a MME to be the good business of the UE according to topology network by eNodeB, and UE access request message is transmitted into MME processing.Wherein, it is the first MME by the eNodeB MME selected according to topology network.

Wherein, access request message can be attach request or routing region updating request.

Wherein, if access request type of message is Attach Request message, the identification information of the UE is the international mobile subscriber identity of the UE（International Mobile Subscriber Idenity, abbreviation IMSI).

Wherein, also include in the Attach Request message：Discontinuous reception parameters that UE core networks ability, UE are specified, Encryption Options transmission mark, type of attachment, NAS sequence numbers, NAS- medium access control etc..

If access request message is routing region updating request message, the identification information of the UE is the IMSI of the UE;Or the identification information of the UE can also be and once perform the MME of UE attachment flows or a preceding Route Area before thus secondary routing region updating is asked MME in area update flow distributes to UE global unique temporary identity（Globally Unique Temporary Identity, abbreviation GUTI).

Wherein, the information such as type of attachment are also included in the routing region updating request message.

802nd, shelter states UE identification information, determines that the UE needs the MME type of access.

Optionally, first MME can be according to the identification information and pre-configured configured information of the UE, determine that the UE needs the MME type of access, wherein, the pre-configured configured information includes the correspondence relationship information of UE identification information and the MME of UE needs access type；

Wherein, the pre-configured configured information is stored in MME, includes UE identity（Identity, abbreviation ID) information and UE need the correspondence relationship information of MME types that accesses.

Specifically, the identification information for the UE that the pre-configured configured information includes is specially the id information of the UE.

Further, the first MME can search in pre-configured configured information corresponding UE ID and need the MME type information accessed according to the IMSI of the UE, determine that the UE needs the MME type accessed.

Optionally, the first MME can state UE identification information with shelter, and the type information for the MME for including the UE needs access in the subscription data of the UE, the subscription data is obtained from the signing good business device HS S of the moon.

Wherein, the subscription data is stored in HS S, includes the correspondence relationship information of the MME types of the ID and UE needs access of the UE.

Specifically, the identification information for the UE that the subscription data of the UE includes is specially the id information of the UE.

Further, the first MME can be asked according to the IMSI of the UE and obtain corresponding UE ID in the subscription data and need the MME type informations that access to HSS, determine that the UE needs the MME type accessed. Optionally, if what UE was initiated is routing region updating request, first MME can state UE identification information with shelter, the mobile management context of the UE is obtained from the UE former MME accessed, the mobile management context includes the MME of UE needs access type information.

Wherein, the mobile management context is stored in former MME, is included the MME in MME or a preceding routing region updating flow that UE attachment flows are once performed before thus secondary routing region updating request and is distributed to the discontinuous reception parameters, packet data network type, security/encryption information that the instruction of MME types, TAI, UE core network ability of the effective last visits of UE, UE that UE GUTI, UE needs access specify（For example：The encrypting and decrypting mode interacted between UE）, type of attachment, NAS sequence numbers, NAS- medium access control etc..

Specifically, the identification information for the UE that the mobile management context includes is specially the GUTI of the UE.

Further, first MME is according to UE GUTI, know the former MME of storage UE mobile management contexts mark, and ask former MME forwardings UE mobile management contextual information, the MME types that the UE needs that first MME includes according to mobile management contextual information are accessed are indicated, determine that the UE needs the MME type of access.

It should be noted that, generally, operator is number section or set meal type by UE to distinguish UE type of service, therefore the type of the MME can occupy UE number section to be classified, it can also be classified according to UE set meal type, or divided according to the actual demand of operator, the present invention does not do specific restriction to the type for how dividing MME.

803rd, the MME types accessed, the MME of gravity treatment 1 the 2nd are needed according to the UE.

If specifically, the UE needs the MME types accessed not to be consistent with the first MME type, the first MME can need the MME types accessed, the MME of gravity treatment 1 the 2nd according to UE;And occupy in pre-configured network all MME type information or The address of the 2nd MME types is obtained from dns server, is established a connection by the MME of address the first and the 2nd MME, realizes the MME of UE gravity treatment.

If it should be noted that there is multiple MME to use under the MME types of required access, selecting a nearest MME to set up according to topology network and connecting.

804th, the access request message is forwarded to the 2nd MME, to cause the 2nd MME to perform the access request flow of the UE.

Specifically, the access request message for the UE having been received by is transmitted to the 2nd MME by the first MME, to allow the 2nd MME to perform the access request flow of the UE.

It should be noted that, it will be understood by those skilled in the art that, if the UE needs the MME types accessed to be consistent with the first MME type, gravity treatment MME is not needed then, UE access request flow is directly performed by the first MME and is completed, such case is not in scope described in the invention.

The embodiments of the invention provide a kind of method of MME gravity treatments, based on technical scheme described above, because the first MME can reselect the MME that the UE needs to access for UE, that is the 2nd MME, and UE access request message is forwarded to the 2nd MME so that UE timely can perform access request flow using correct MME.Simultaneously because the first MME can choose the MME matched with UE types of service for UE, it is linked into equal to by the UE for having opened different business under the MME of its type of service of correspondence, UE classification is managed by operator by MME, so as to improve the efficiency of management of operator.Further, access request flow is performed because MME of the prior art is only capable of the just blunt access request message according to the eNodeB UE forwarded, and the first MME in this programme may also help in UE selections UE and need the MME of access and forward UE access request, thus realizations of this programme only needs to carry out existing MME software upgrading can to help UE gravity treatments reaching MME and forward purpose of the access request to the MME for needing access, and MME quantity is relatively fewer, so the influence caused to carrier network is also smaller.

The MME of one kind the 2nd provided based on above-described embodiment, the embodiments of the invention provide the method for another MME gravity treatments, this method executive agent is the 2nd MME, wherein the 2nd MME is first The MME types that MME needs to access according to UE, are the MME of the UE gravity treatments, as shown in Fig. 9, this method includes：

901st, the mark for including the UE in the access request message that the user equipment (UE) of the first MME forwardings is sent, the access request message is received.

Wherein, the first MME is that eNodeB is the MME that UE is selected according to topology network.Specifically, the 2nd MME receives the access request message that the UE of the first MME forwardings is sent.

Wherein, the detailed description of access request message refers to 801 description, the present embodiment

902nd, the access request flow of the UE is performed according to the access request message.Optionally, in the access request flow of the UE is performed according to the access request message, 2nd Μ Μ Ε can be by the first Μ Μ Ε to UE transmission interaction messages, and pass through the interaction message that the first Μ Μ Ε receive the UE transmissions.

It should be noted that, it will be understood by those skilled in the art that, 2nd Μ Μ Ε, can be by the first Μ Μ Ε to UE transmission interaction messages when performing the access request flow of the UE, and pass through the interaction message that the first Μ Μ Ε receive the UE transmissions；Interaction message directly can also be sent to the UE by eNodeB as shown in prior art Fig. 2 and Fig. 3, and the interaction message that the UE is sent is received by eNodeB, as shown in step 205-216 and 306-3 15；And other any other equipments from interaction message to UE or mode that the 2nd MME can be helped to forward, the present invention does not do specific restriction to this, for convenience of the description of this invention and introduction, following examples are illustrated exemplified by only sending interaction message, and the interaction message sent by the first MME receptions UE to the UE by the first MME with the 2nd MME.

The embodiments of the invention provide a kind of method of MME gravity treatments, based on technical scheme described above, because the 2nd MME can perform UE access request flow according to the first MME UE forwarded access request message so that UE timely can perform access request flow using correct MME.Simultaneously because MME of the prior art is only capable of performing access request flow according to the eNodeB UE forwarded access request message, and the 2nd MME in this programme can also be according to the first MME The access request message of forwarding performs UE access request flow, thus the realization of this programme only needs to carry out existing MME software upgrading to reach that MME can perform the purpose of UE access request flow according to the access request message of the first MME forwardings, and because MME quantity is relatively fewer, so the influence caused to carrier network is also smaller.

Hereinafter, so that UE performs attachment flow as an example, the method for describing a kind of MME gravity treatments that the present invention is provided in detail implements process as shown in Figure 10.

It should be noted that, the interaction for the attachment flow that the present embodiment is enumerated is identical with a part of step of existing attachment flow, wherein identical step is just no longer --- narration, only highlight a kind of interaction of MME gravity treatments provided in an embodiment of the present invention.

1001st, UE sends Attach Request message to eNodeB.

1002nd, the UE Attach Request messages sent are transmitted to the first MME by eNodeB.

1003a, the first MME and HSS complete the authentication to UE.

1003b, the first MME complete the security setting with UE NAS message.

1004th, the first MME completes location update request message with HSS and confirms interacting for position updating request confirmation message.

100 A, the MME types for needing to access according to the UE, UE MME described in gravity treatment.Specifically, identification informations of the first MME according to the UE, determines that the UE needs the mobility management entity MME type of access, gravity treatment MME, i.e. the 2nd MME, and connection is set up therewith, detailed process refer to described in 802,803.

If it should be noted that affiliated UE does not need gravity treatment MME, directly by first

MME performs and completed the follow-up attachment flows of UE, it is not necessary to perform attachment flow by the 2nd MME, such case is not in scope described in the invention.

100B, the first MME forwarding contexts give the 2nd MME.

Wherein, the context includes the Attach Request message of UE transmissions.

1005th, the 2nd MME, which is sent, creates conversation request message to S-GW.

1006th, S-GW is connected and is sent establishment conversation request message to P-GW.

1007th, P-GW, which is returned, creates conversational response message to S-GW. 1008th, S-GW, which is returned, creates conversational response message to the 2nd MME.

100C, the 2nd MME and HSS complete interacting for location update request message and position updating request confirmation message.

Specifically, the 2nd MME sends location update request message to HSS, MME positional information where HSS updates stored UE, the updating location information that wherein HSS is serviced UE by the first MME is the positional information that UE is serviced by the 2nd MME.After MME positional information where HSS updates UE, the 2nd MME position updating request confirmation messages are returned to.

100D, HSS and the first MME complete interacting for position deletion request message and position removal request confirmation message.

Specifically, HSS launch positions deletion request message gives the first MME, the first MME to delete the mobile context set up between the UE of storage positional information, i.e. the first MME and UE, HSS positions removal request confirmation message is returned to after deletion.

100E, the 2nd MME send context to the first MME.

Wherein, attachment received message is included in the context and initial context sets up request message.

1009th, the first MME sends initial context and sets up request message to eNodeB.

1010th, eNodeB sends radio resource control and connects reconfiguration message to UE.

101 1, UE sends radio resource control connection and reconfigures completion message to sNodsB.

1012nd, eNodeB sends initialization context and sets up response message to the first MME.100F, the first MME forwarding contexts give the 2nd MME.

Wherein, initial context is included in the context and sets up response, the initialization context sets up in response message the TEID for including that eNodeB is user plane distribution, address of eNodeB user plane etc..

1013rd, UE sends directly transmission message to eNodeB.

1014th, eNodeB forwardings attachment completion message is to the first MME.

100G, the first MME forwarding contexts give the 2nd MME. Wherein, attachment completion message is included in the context.

1015th, the 2nd MME sends bearer update request message to S-GW.

1016th, S-GW sends bearer update response message to the 2nd MME, and starts to send the downlink data message that Slow is deposited since 1007 to eNodeB.

Based on embodiment described above, because the first MME can reselect the MME that the UE needs to access for UE, that is the 2nd MME, and UE access request message is forwarded to the 2nd MME, and the 2nd MME can according to the first MME forward UE access request message perform UE access request flow so that UE can timely using correct MME perform access request flow.

Hereinafter, so that UE performs attachment flow as an example, the method for describing a kind of MME gravity treatments that the present invention is provided in detail implements process as shown in figure 11.

It should be noted that, the interaction for the attachment flow that the present embodiment is enumerated is identical with a kind of a part of step of the attachment flow for MME gravity treatments that a upper embodiment is provided, wherein identical step is just no longer --- narration, only highlight ciphering process when MME is interacted with UE.

It should be further stated that, it is all in Figure 11 that represent the step of be decorated with dotted line frame is the step of possible occurring.

1 101, UE sends Attach Request message to eNodeB.

1 102, the UE Attach Request messages sent are transmitted to the first MME by eNodeB.

1 103a, the first MME and HSS complete the authentication to UE.

1 103b, the first MME complete the security setting with UE NAS message.

1 104, the first MME and HSS complete interacting for location update request message and position updating request confirmation message.

1 10A, the MME types for needing to access according to the UE, UE MME described in gravity treatment.1 10B, the first MME forwarding contexts give the 2nd MME.

Wherein, the context includes the Attach Request message of UE transmissions.

Optionally, the safe context that the first MME and UE is set up can also be included in the context（That is the cipher mode appointed between MME and UE, key information etc.）. 1105th, the 2nd MME, which is sent, creates conversation request message to S-GW.

1106th, S-GW is connected and is sent establishment conversation request message to P-GW.

1107th, P-GW, which is returned, creates conversational response message to S-GW.

1108th, S-GW, which is returned, creates conversational response message to the 2nd MME.

110C, the 2nd MME and HSS complete interacting for location update request message and position updating request confirmation message.

110D, HSS and the first MME complete interacting for position deletion request message and position removal request confirmation message.

110al, the 2nd MME complete the encryption to context.

Wherein, the context is that the 2nd MME will be sent to the first MME context, includes attachment received message and initial context is set up request and disappeared,.

Specifically, the step is to be based on 110B.

If context described in 110B includes the safe context that the first MME and UE is set up, the cipher mode in the safe context set up with UE that this step is forwarded by the 2nd MME according to the first MME in 110B is needed, this context is encrypted.

If context described in 110B does not include the safe context that the first MME and UE is set up, without this step, the 2nd MME need not perform cryptographic operation.

110E, the 2nd MME send context to the first MME.

Wherein, the context includes attachment received message and initial context is set up and asks encryption of 110a2, the first the MME completion to context that disappear.

Wherein, the context is the context that the first MME is sended over, and includes attachment received message and initial context sets up request message.

Specifically, the step is to be based on 110B.

If context described in 110B includes the safe context that the first MME and UE is set up, without this step, the first MME need not perform cryptographic operation.

If context described in 110B is not included above and below the safety that the first MME and UE is set up Text, then because the first MME will not be transmitted to the 2nd MME with the safe context that UE is set up, so the 2nd MME can not know encryption when being interacted with UE and manner of decryption, it is necessary to be completed by the first MME to the encryption from the 2nd MME contexts sended over.

1 109, the first MME sends initial context and sets up request message to eNodeB.

1 110, eNodeB sends radio resource control and connects reconfiguration message to UE.

1111, UE sends radio resource control connection and reconfigures completion message to sNodsB.

11 12, eNodeB sends initialization context and sets up response message to the first MME.

1 10b2, the first MME complete to set up initialization context the decryption of response message.Wherein, the initialization context sets up what response message sended over for eNodeB.Specifically, the step is to be based on 1 10B.

If context described in 1 10B includes the safe context that the first MME and UE is set up, without this step, the first MME need not perform decryption oprerations.

If context described in 1 10B does not include the safe context that the first MME and UE is set up, then because the first MME will not be transmitted to the 2nd MME with the safe context that UE is set up, so the 2nd MME can not know encryption when being interacted with UE and manner of decryption, it is necessary to be completed to set up the initialization context that will be sent to the 2nd MME the decryption of response message by the first MME.

1 10F, the first MME forwarding contexts give the 2nd MME.

Wherein, the context include initialization context set up response message.

1 10b l, the 2nd MME complete the decryption to context.

Wherein, the context is the context that the first MME is transmitted across, and includes initialization context and sets up response message.

Specifically, the step is to be based on 1 10B.

If context described in 1 10B includes the safe context that the first MME and UE is set up, the manner of decryption in the safe context set up with UE that this step is forwarded by the 2nd MME according to the first MME in 1 10B is then needed, will be forwarded over to the first MME by the 2nd MME The initialization context come is set up response message and is decrypted.

If context described in 110B does not include the safe context that the first MME and UE is set up, without this step, the 2nd MME need not perform decryption oprerations.

1113rd, UE sends directly transmission message to eNodeB.

1114th, eNodeB forwardings attachment completion message is to the first MME.

110c2, the first MME complete the decryption to adhering to completion message.

Wherein, the attachment completion message is what eNodeB was sended over.

Specifically, the step is to be based on 110B.

If context described in 110B includes the safe context that the first MME and UE is set up, without this step, the first MME need not perform decryption oprerations.

If context described in 110B does not include the safe context that the first MME and UE is set up, then because the first MME will not be transmitted to the 2nd MME with the safe context that UE is set up, so the 2nd MME can not know encryption when being interacted with UE and manner of decryption, it is necessary to be completed by the first MME to the decryption for the attachment completion message that will be sent to the 2nd MME.

110G, the first MME forwarding contexts give the 2nd MME.

Wherein, the context includes attachment completion message.

110cl, the 2nd MME complete the decryption to context.

Wherein, the context is the context that the first MME is transmitted across, and includes attachment completion message.

Specifically, the step is to be based on 110B.

If context described in 110B includes the safe context that the first MME and UE is set up, the manner of decryption in the safe context set up with UE that this step is forwarded by the 2nd MME according to the first MME in 110B is then needed, the first MME attachment completion messages forwarded will be decrypted by the 2nd MME.

1115th, the 2nd MME sends bearer update request message to S-GW. 11 16, S-GW sends bearer update response message to the 2nd MME, and starts to send the downlink data message that Slow is deposited since 1 107 to eNodeB.

Hereinafter, so that UE performs routing region updating flow as an example, the method for describing a kind of MME gravity treatments that the present invention is provided in detail implements process as shown in figure 12.

It should be noted that, the interaction for the routing region updating flow that the present embodiment is enumerated is identical with a part of step of existing route area update flow, wherein identical step is just no longer --- narration, only highlight a kind of interaction of MME gravity treatments provided in an embodiment of the present invention.

It should be further stated that, it is all in Figure 12 that represent the step of be decorated with dotted line frame is the step of possible occurring.

1201st, UE sends routing region updating request message to eNodeB.

1202nd, eNodeB forwards routing region updating request message to the first MME.

1203rd, the first MME sends mobile management context request message to former MME.

1204th, original MME returns to mobile management context response information to MME.

1205a, the first MME and HSS complete the authentication to UE.

1205b, the first MME complete the security setting with UE NAS message.

It should be noted that the step is to be based on 1204.

If including former MME and UE safe context in the mobile management context for returning to the first MME in 1204 by former MME, without this step, the first MME need not carry out the security setting with UE NAS message.

If being returned to by former MME in 1204 does not include original MME and UE safe context in the first MME mobile management context, need to carry out the security setting of NAS message by the first MME and UE in this step. 120A, the just blunt MME types for needing to access according to the UE, UE MME described in gravity treatment.

Specifically, identification informations of the first MME according to the UE, determines that the UE needs the mobility management entity MME type of access, gravity treatment MME, i.e. the 2nd MME, and connection is set up therewith, detailed process refer to described in 802,803.

If it should be noted that affiliated UE does not need gravity treatment MME, directly being performed by the first MME and being completed the follow-up routing region updating flows of UE, it is not necessary to performed by the 2nd MME, such case is not in scope described in the invention.

120B, the first MME forwarding contexts give the 2nd MME.

Wherein, the context includes the mobile management context for the UE that the routing region updating request message of UE transmissions, the first MME are obtained.

Optionally, the safe context that the first MME and UE is set up can also be included in the context（That is the cipher mode appointed between the first MME and UE, key information etc.）.

1207th, the 2nd MME initiates bearer update request message to S-GW.

1208th, S-GW sends bearer update request message to P-GW.

1209th, P-GW returns to bearer update response message to S-GW.

1210th, S-GW sends bearer update response message to the 2nd MME.

121 1, the 2nd MME launch positions update request message to HSS.

1212nd, HSS and original MME complete interacting for position deletion request message and position removal request confirmation message.

1213rd, HSS home positions update request confirmation message to the 2nd MME.

120C 1, the 2nd MME complete the encryption to routing region updating received message.

Wherein, it is the GUTI that UE is distributed that the routing region updating received message, which includes the 2nd MME,.

Specifically, the step is to be based on 120B.

If context described in 120B includes the safe context that the first MME and UE is set up, need to be built with UE according to what the first MME in 120B was forwarded by the 2nd MME in this step Cipher mode in vertical safe context, routing region updating received message is encrypted.If context described in 120B does not include the safe context that the first MME and UE is set up, without this step, the 2nd MME need not perform cryptographic operation.

120D, the 2nd MME send context to the first MME.

Wherein, the context includes routing region updating received message, S-GW change instructions.1206th, the first MME sends context acknowledgement message to former MME.

Wherein described context acknowledgement message includes S-GW change instructions.

It should be noted that, because the selection of S-GW in routing region updating flow is performed by the 2nd MME, thus the first MME can only be after the 2nd MME returns to S-GW change instruction message, and could send context confirms to former MME, so being placed on this execution by 1206.

120C2, the first MME complete the encryption to routing region updating received message.

Included by the context that wherein, the routing region updating received message sends over for the 2nd MME.

Specifically, the step is to be based on 120B.

If context described in 120B includes the safe context that the first MME and UE is set up, without this step, the first MME need not perform cryptographic operation.

If context described in 120B does not include the safe context that the first MME and UE is set up, then because the first MME will not be transmitted to the 2nd MME with the safe context that UE is set up, so the 2nd MME can not know encryption when being interacted with UE and manner of decryption, it is necessary to be completed by the first MME to the encryption from the 2nd MME routing region updating received messages sended over.

1214th, the first MME sends routing region updating and accepts message to eNodeB.

Wherein, it is the GUTI that UE is distributed that the 2nd MME is included in the routing region updating received message.

1215th, eNodeB forwards routing region updating to accept message to UE.

Based on embodiment described above, because the first MME can reselect MME, i.e. the 2nd MME that the UE needs to access for UE, and UE access request message is forwarded to second MME, and the 2nd MME can perform UE access request flow according to the first MME UE forwarded access request message so that UE timely can perform access request flow using correct MME.

Hereinafter, so that UE performs routing region updating flow as an example, the method for describing a kind of MME gravity treatments that the present invention is provided in detail implements process as shown in figure 13.

It should be noted that the interaction for the routing region updating flow that the present embodiment is enumerated is identical with a kind of a part of step of the routing region updating flow for MME gravity treatments that a upper embodiment is provided, wherein identical step is just no longer --- narration.Difference is the channel of the mobile management context for the UE that the 2nd MME is obtained, the mobile management context for the UE that the 2nd MME is obtained is to be transmitted to the 2nd MME after being obtained from the first MME to former MME in a upper embodiment, the present embodiment is directly to former MME acquisition requests, so the present embodiment only highlights this process from the 2nd MME.

1301st, UE sends routing region updating request message to eNodeB.

1302nd, eNodeB forwards routing region updating request message to the first MME.

1303rd, the first MME sends mobile management context request message to former MME.

1304th, original MME returns to mobile management context response information to the first MME.

130A, the just blunt MME types for needing to access according to the UE, UE MME described in gravity treatment.

MME performs and completed the follow-up routing region updating flows of UE, it is not necessary to pass through second

MME is performed, and such case is not in scope described in the invention.

130B, the first MME forwarding contexts give the 2nd MME.

Wherein, the context includes the routing region updating request message of UE transmissions.130C, the 2nd MME send mobile management context request message to former MME.Specifically, the 2nd MME knows UE according to the GUMMEI information included in GUTI Former MME addresses where mobile management context, mobile management context request message is sent to former MME.

Wherein, UE GUTI is included in the mobile management context request message.130D, original MME return to mobile management context response information to the 2nd MME.Specifically, original MME occupies the mobile management context that GUTI determines UE, UE mobile management contexts are returned into the 2nd MME in mobile management context response information.

1305a, the 2nd MME and HSS complete the authentication to UE.

1305b, the 2nd MME complete the security setting with UE NAS message.

Specifically, the 2nd MME completes the security setting with UE NAS message, such as integrity protection, cipher mode and key information.

It should be noted that the step is to be based on 130D.

If including former MME and UE safe context in the mobile management context for returning to the 2nd MME in 130D by former MME, without this step, the 2nd MME need not carry out the security setting with UE NAS message.

If being returned to by former MME in 130D does not include original MME and UE safe context in the 2nd MME mobile management context, need to carry out the security setting of NAS message by the 2nd MME and UE in this step.

1306th, the 2nd MME sends context acknowledgement message to former MME.

Wherein, S-GW change instructions are included in the context acknowledgement message.

1307th, the 2nd MME initiates bearer update request message to S-GW.

1308th, S-GW sends bearer update request message to P-GW.

1309th, P-GW returns to bearer update response message to S-GW.

13 10, S-GW sends bearer update response message to the 2nd MME.

13 11, the 2nd MME launch positions update request message to HSS.

13 12, HSS and original MME complete interacting for position deletion request message and position removal request confirmation message.

13 13, HSS home positions update request confirmation message to the 2nd MME. 130E, the 2nd MME send context to the first MME.

Wherein, it is the GUTI that UE is distributed that the context, which includes including the 2nd MME in routing region updating received message, routing region updating received message,.

1314th, MME sends routing region updating and accepts message to eNodeB.

1315th, eNodeB forwards routing region updating to accept message to UE.

In several embodiments provided herein, it should be understood that disclosed MME and method, it can realize by another way.For example, MME embodiments described above are only schematical, for example, the division of the unit, it is only a kind of division of logic function, there can be other dividing mode when actually realizing, such as multiple units or component can combine or be desirably integrated into another system, or some features can be ignored, or do not perform.Another, it, by some interfaces, the INDIRECT COUPLING or communication connection of device or unit, can be electrical or other forms that shown or discussed coupling or direct-coupling or communication connection each other, which can be,.

The unit illustrated as separating component can be or may not be physically separate, the part shown as unit can be or may not be physical location, a place can be located at, or can also be distributed on multiple NEs.Some or all of unit therein is selected to realize the purpose of this embodiment scheme the need for reality can be occupied.

In addition, each functional unit in each of the invention embodiment can be integrated in a processing unit or the independent physics of unit includes, can also two or more units it is integrated in a unit.Above-mentioned integrated unit can both be realized in the form of hardware, It can also be realized in the form of hardware adds SFU software functional unit.

The above-mentioned integrated unit realized in the form of SFU software functional unit, can be stored in a computer read/write memory medium.Above-mentioned SFU software functional unit is stored in a storage medium, including some instructions are to cause a computer equipment（Can be personal computer, server, or network equipment etc.）Perform the part steps of each embodiment methods described of the invention.And foregoing storage medium includes：U disks, mobile hard disk, read-only storage（Read-Only Memory, abbreviation ROM), random access memory (Random Access Memory, abbreviation RAM), magnetic disc or CD etc. are various can be with the medium of store program codes.

Finally it should be noted that：The above embodiments are merely illustrative of the technical solutions of the present invention, rather than its limitations；Although the present invention is described in detail with reference to the foregoing embodiments, it will be understood by those within the art that：It can still modify to the technical scheme described in foregoing embodiments, or carry out equivalent substitution to which part technical characteristic；And these modifications or replacement, the essence of appropriate technical solution is departed from the spirit and scope of various embodiments of the present invention technical scheme.

It is described above; only embodiment of the invention, but protection scope of the present invention is not limited thereto, any one skilled in the art the invention discloses technical scope in; change or replacement can be readily occurred in, should be all included within the scope of the present invention.Therefore, protection scope of the present invention should be based on the protection scope of the described claims.

Claims

Claims

1st, a kind of first mobility management entity MME, it is characterised in that the first MME includes：

Receiving unit, the access request message for receiving user equipment (UE) transmission, the access request message carries the identification information of the UE；

Determining unit, for the identification information according to the UE, determines that the UE needs the MME type of access；

Gravity treatment unit, the MME types that UE needs to access, the MME of gravity treatment 1 the 2nd are stated for shelter;

Transmitting element, for the access request message to be forwarded into the 2nd MME, to cause the 2nd MME to perform the access request flow of the UE.

2nd, the first MME according to claim 1, it is characterised in that

The receiving unit, is additionally operable to receive the interaction message of the UE and the 2nd MME in the access request flow is performed；

The transmitting element, is additionally operable to forward the interaction message of the UE and the 2nd MME in the access request flow is performed.

3rd, the first MME according to claim 1 or 2, it is characterised in that the determining unit specifically for：

According to the identification information of the UE and pre-configured configured information, determine that the UE needs the MME type of access, wherein, the pre-configured configured information includes the correspondence relationship information of UE identification information and the MME of UE needs access type.

4th, the first MME according to claim 1 or 2, it is characterised in that the determining unit specifically for：

According to the identification information of the UE, the type information for the MME for including the UE needs access in the subscription data of the UE, the subscription data is obtained from subscribed services device HSS；

According to the subscription data, determine that the UE needs the MME type of access. 5th, the first MME according to claim 1 or 2, it is characterised in that the determining unit specifically for：

Shelter states UE identification information, and the mobile management contextual information of the UE is obtained from the UE former MME accessed, and the mobile management contextual information includes the MME of UE needs access type information；

According to the mobile management contextual information, determine that the UE needs the MME type of access.

6th, the first MME according to claim 5, it is characterised in that

The transmitting element specifically for, the mobile management contextual information of the access request message and the UE is forwarded to the 2nd MME, to cause the 2nd MME to perform the access request flow of the UE according to the access request message and the UE mobile management contextual information.

7th, a kind of second mobility management entity MME, it is characterised in that the 2nd MME includes：

Receiving unit, the mark of the UE is included for receiving in the access request message that the user equipment (UE) of the first MME forwardings is sent, the access request message；

Processing unit, the access request flow for performing the UE according to the access request message.

8th, the 2nd MME according to claim 7, it is characterised in that the 2nd MME also includes：

Transmitting element is used for, in the access request flow that the processing unit performs the UE according to the access request message, and interaction message is sent to the UE by the first MME；The receiving unit is specifically in the access request flow that the processing unit performs the UE according to the access request message, the interaction message that the UE is sent is received by the first MME.

9th, the 2nd MME according to claim 7 or 8, it is characterised in that the receiving unit, is additionally operable to receive the UE of the first MME forwardings shifting Dynamic managing context information；

The processing unit is specifically for performing the access request flow of the UE according to the access request message and the UE mobile management contextual information.

10th, the 2nd MME according to claim 7 or 8, it is characterised in that the transmitting element, is additionally operable to, according to the UE marks carried in the access request message, mobile management context request message be sent to UE former MME；

The receiving unit, is additionally operable to receive the mobile management context response information that the former MME of the UE is sent, wherein the mobile management context response information carries the mobile management contextual information of the UE；

The processing unit is specifically for performing the access request flow of the UE according to the access request message and the UE mobile management contextual information.

11st, a kind of first mobility management entity MME, it is characterised in that the first MME includes：

Receiver, the access request message for receiving user equipment (UE) transmission, the access request message carries the identification information of the UE；

Processor, for the identification information according to the UE, determines that the UE needs the MME type of access；And the blunt MME types for needing to access according to the UE of, the MME of gravity treatment 1 the 2nd;

Transmitter, for the access request message to be forwarded into the 2nd MME, to cause the 2nd MME to perform the access request flow of the UE.

12nd, the first MME according to claim 11, it is characterised in that

The receiver, is additionally operable to receive the interaction message of the UE and the 2nd MME in the access request flow is performed；

The transmitter, is additionally operable to forward the interaction message of the UE and the 2nd MME in the access request flow is performed.

13rd, the first MME according to claim 11 or 12, it is characterised in that the processor specifically for： According to the identification information of the UE and pre-configured configured information, determine that the UE needs the MME type of access, wherein, the pre-configured configured information includes the correspondence relationship information of UE identification information and the MME of UE needs access type.

14th, the first MME according to claim 11 or 12, it is characterised in that the processor specifically for：

According to the identification information of the UE, the type information for the MME for including the UE needs access in the subscription data of the UE, the subscription data is obtained from subscribed services device HSS；

According to the subscription data, determine that the UE needs the MME type of access.

15th, the first MME according to claim 11 or 12, it is characterised in that the processor specifically for：

Shelter states UE identification information, and the mobile management contextual information of the UE is obtained from the UE former MME accessed, and the mobile management contextual information includes the MME of UE needs access type information；

According to the mobile management contextual information, determine that the UE needs the MME type of access.

16th, the first MME according to claim 15, it is characterised in that

The transmitter specifically for, the mobile management contextual information of the access request message and the UE is forwarded to the 2nd MME, to cause the 2nd MME to perform the access request flow of the UE according to the access request message and the UE mobile management contextual information.

17th, a kind of second mobility management entity MME, it is characterised in that the 2nd MME includes：

Receiver, the mark of the UE is included for receiving in the access request message that the user equipment (UE) of the first MME forwardings is sent, the access request message；

Processor, the access request flow for performing the UE according to the access request message. 18th, the 2nd MME according to claim 17, it is characterised in that the 2nd MME also includes：

Transmitter, in the access request flow that the processor performs the UE according to the access request message, interaction message to be sent to the UE by the first MME；The receiver is specifically in the access request flow that the processor performs the UE according to the access request message, the interaction message that the UE is sent is received by the first MME.

19th, the 2nd MME according to claim 17 or 18, it is characterised in that the receiver, is additionally operable to receive the UE of the first MME forwardings mobile management contextual information；

The processor is specifically for performing the access request flow of the UE according to the access request message and the UE mobile management contextual information.

20th, the 2nd MME according to claim 17 or 18, it is characterised in that the transmitter, is additionally operable to, according to the UE marks carried in the access request message, mobile management context request message be sent to UE former MME；

The receiver, is additionally operable to receive the mobile management context response information that the former MME of the UE is sent, wherein the mobile management context response information carries the mobile management contextual information of the UE；

The processor is specifically for performing the access request flow of the UE according to the access request message and the UE mobile management contextual information.

21st, a kind of method of mobility management entity MME gravity treatments, it is characterised in that this method includes：

The access request message that user equipment (UE) is sent is received, the access request message carries the identification information of the UE；

According to the identification information of the UE, determine that the UE needs the MME type of access；

The MME types for needing to access according to the UE, the MME of gravity treatment 1 the 2nd; The access request message is forwarded to the 2nd MME, to cause the 2nd MME to perform the access request flow of the UE.

22nd, after the method according to claim 21, it is characterised in that the access request message is being forwarded into the 2nd MME, the access request flow to cause the 2nd MME execution UE, this method also includes：

Receive the interaction message of the UE and the 2nd MME in the access request flow is performed；

Forward the interaction message of the UE and the 2nd MME in the access request flow is performed.

23rd, the method according to claim 21 or 22, it is characterised in that according to the identification information of the UE, determines that the UE needs the MME type of access, specifically includes：According to the identification information of the UE and pre-configured configured information, determine that the UE needs the MME type of access, wherein, the pre-configured configured information includes the correspondence relationship information of UE identification information and the MME of UE needs access type.

24th, the method according to claim 21 or 22, it is characterised in that according to the identification information of the UE, determines that the UE needs the MME type of access, specifically includes：According to the identification information of the UE, the type information for the MME for including the UE needs access in the subscription data of the UE, the subscription data is obtained from subscribed services device HSS；

According to the subscription data, determine that the UE needs the MME type of access.

25th, the method according to claim 21 or 22, it is characterised in that according to the identification information of the UE, determines that the UE needs the MME type of access, specifically includes：Shelter states UE identification information, and the mobile management contextual information of the UE is obtained from the UE former MME accessed, and the mobile management contextual information includes the MME of UE needs access type information；

According to the mobile management contextual information, determine that the UE needs the MME type of access. 26th, the method according to claim 25, it is characterised in that be forwarded to by the access request message after the 2nd MME, this method also includes：

The mobile management contextual information of the UE is forwarded to the 2nd MME.

27th, a kind of method of mobility management entity MME gravity treatments, it is characterised in that this method includes：

Receive the mark for including the UE in the access request message that the user equipment (UE) of the first MME forwardings is sent, the access request message；

The access request flow of the UE is performed according to the access request message.

28th, the method according to claim 27, it is characterised in that the access request flow of the UE is performed according to the access request message, is specifically included：

Interaction message is sent to the UE by the first MME, and the interaction message that the UE is sent is received by the first MME.

29th, the method according to claim 27 or 28, it is characterised in that before the access request flow of the UE is performed according to the access request message, this method also includes：Receive the UE of the first MME forwardings mobile management contextual information；The access request flow of the U E is performed according to the access request message, is specifically included：The access request flow of the UE is performed according to the access request message and the UE mobile management contextual information.

30th, the method according to claim 27 or 28, it is characterised in that after the access request message that the user equipment (UE) for receiving the first MME forwardings is sent, this method also includes：

According to the UE marks carried in the access request message, mobile management context request message is sent to UE former MME；

Receive the mobile management context response information that the former MME of the UE is sent, wherein described mobile management context response information carries the mobile management context letter of the UE according to access request message execution U E access request flow, specifically includes： Institute E access request flow is performed according to the access request message and the UE mobile management contextual information.