SYSTEMS, METHODS AND MEDIA FOR MOBILE MANAGEMENT ENTITY (MME) SELECTION BY EVOLVED NODE B (eNodeB)

• US 20140169269A1
• Filed: 12/19/2012
• Published: 06/19/2014
• Est. Priority Date: 12/19/2012
• Status: Active Grant

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Salot, Nirav, Dodd-Noble, Aeneas, Guntupalli, Ravi
• Granted Patent: US 9,055,520 B2
• Time in Patent Office: Days
• US Class Current: 370/328
• CPC Class Codes: H04L 47/12 Avoiding congestion; Recovering from congestion
• CPC Class Codes: H04L 47/2408 for supporting different services, e.g. a differentiated services [DiffServ] type of service
• CPC Class Codes: H04W 48/20 Selecting an access point
• CPC Class Codes: H04W 76/10 Connection setup
• CPC Class Codes: H04W 76/12 Setup of transport tunnels
• CPC Class Codes: H04W 76/27 Transitions between radio resource control [RRC] states
• CPC Class Codes: H04W 76/50 for emergency connections
• CPC Class Codes: H04W 8/065 involving selection of the user mobility server
• CPC Class Codes: H04W 92/045 between access point and backbone network device
• CPC Class Codes: H04W 92/14 between access point controllers and backbone network device

Abstract

A method for mobile management entity (MME) selection includes receiving at a base transceiver station (BTS) a message from each of multiple MMEs including information for advertising functionalities of each of the MMEs. The functionalities include at least one type of communications session supported by each of the MMEs. The method also includes receiving at the BTS a message from a user equipment (UE) to request for a communications session. The request message includes session type information indicating a type of session requested by the UE. At least one of the MMEs is capable of serving the requested type of session. The method further includes generating a list of candidate MMEs capable of serving the requested type of communications session from the MMEs by matching the session type information with the capability information, and selecting a serving MME from the list based on the information relating to the advertised functionalities.

Claims

1. A method comprising:

receiving at a base transceiver station (BTS) a message from each of a plurality of mobile management entities (MMEs), wherein each of the messages includes capability information for advertising functionalities that each of the plurality of MMEs is capable of providing and wherein the advertised functionalities include at least one type of communications session that is supported by each of the plurality of MMEs;

receiving at the BTS a message from a user equipment (UE) to request for a communications session, wherein the request message includes session type information indicating a type of communications session requested by the UE for services and wherein at least one of the plurality of the MMEs is capable of serving the requested type of communications session;

generating at the BTS a list of candidate mobility management entities (MMEs) that are capable of serving the requested type of communications session for the services from the plurality of MMEs by matching the session type information with the information regarding the advertised functionalities; and

selecting at the BTS a serving mobility management entity (MME) from the list of candidate MMEs based at least in part on the information relating to the advertised functionalities.

2. The method of claim 1, further comprising establishing the requested type of communications session between the UE and the selected serving MME, wherein the selection includes selecting based on a combination of the information relating to the advertised functionalities and on at least one factor that is independent of the advertised functionalities of the candidate MMEs.

3. The method of claim 2, wherein the at least one factor that is independent of the advertised functionalities of the candidate MMEs includes a load factor.

4. The method of claim 1, wherein the message from each of the plurality of MMEs includes a message supported by S1 Application Part (S1AP) interface and the capability information includes an S1AP Information Element (IE).

5. The method of claim 4, wherein the S1AP IE includes an MME Supporting Features information element (IE).

6. The method of claim 5, wherein the MME Supporting Features IE includes a bitmap having an array of bits, wherein each bit in the bit array corresponds to a different type of communications session that can be supported by an MME.

7. The method of claim 4, wherein the message supported by S1AP interface includes one of:

an S1 Setup Response message or an MME Configuration Update message.

8. The method of claim 1, wherein the session type information includes an element of Establishment Cause included in an RRC Connection Request.

9. The method of claim 8, further comprising deriving at the BTS the requested type of communications session from the element of Establishment Cause.

10. The method of claim 1, wherein the at least one type of communications session that is supported by each of the plurality of MMEs and the type of communications session requested by the UE include an emergency session, a relatively high priority access session, and a relatively low priority delay tolerant access session.

11. A network device comprising:

a memory capable of storing data; and

a processor configured for using the data such that the network device can;

receive a message from each of a plurality of mobile management entities (MMEs), wherein each of the messages includes capability information for advertising functionalities that each of the plurality of MMEs is capable of providing and wherein the advertised functionalities include at least one type of communications session that is supported by each of the plurality of MMEs;

receive a message from a user equipment (UE) for a communications session, wherein the request message includes session type information indicating a type of communications session requested by the UE for services and wherein at least one of the plurality of the MMEs is capable of serving the requested type of communications session;

generate a list of candidate mobility management entities (MMEs) that are capable of serving the requested type of communications session for the services from the plurality of MMEs by matching the session type information with the information regarding the advertised functionalities; and

select a serving mobility management entity (MME) from the list of candidate MMEs based at least in part on the information relating to the advertised functionalities.

12. The network device of claim 11, wherein the selection includes selecting based on a combination of the information relating to the advertised functionalities and on at least one factor that is independent of the advertised functionalities of the candidate MMEs.

13. The network device of claim 12, wherein the at least one factor that is independent of the advertised functionalities of the candidate MMEs includes a load factor.

14. The network device of claim 11, wherein the network device includes a base transceiver station (BTS).

15. The network device of claim 11, wherein the network device includes an Evolved Node B (eNodeB).

16. The network device of claim 11, wherein the processor is further configured for using the data such that the network device can establish the requested type of communications session between the UE and the selected serving MME and wherein the message from each of the plurality of MMEs includes a message supported by S1 Application Part (S1AP) interface and the capability information includes an S1AP Information Element (IE).

17. The network device of claim 16, wherein the S1AP IE includes an MME Supporting Features information element (IE).

18. The network device of claim 17, wherein the MME Supporting Features IE includes a bitmap having an array of bits, wherein each bit in the bit array corresponds to a different type of communications session that can be supported by an MME.

19. The network device of claim 11, wherein the session type information includes an element of Establishment Cause included in an RRC Connection Request.

20. A computer program product residing on a non-transitory computer-readable medium, the computer program product comprising computer executable code which, when executed by one or more processors, causes the one or more processors to perform a method comprising:

receiving at a base transceiver station (BTS) a message from each of a plurality of mobile management entities (MMEs), wherein each of the messages includes capability information for advertising functionalities that each of the plurality of MMEs is capable of providing and wherein the advertised functionalities include at least one type of communications session that is supported by each of the plurality of MMEs;

receiving at the BTS a message from a user equipment (UE) to request for a communications session, wherein the request message includes session type information indicating a type of communications session requested by the UE for services and wherein at least one of the plurality of the MMEs is capable of serving the requested type of communications session;

generating at the BTS a list of candidate mobility management entities (MMEs) that are capable of serving the requested type of communications session for the services from the plurality of MMEs by matching the session type information with the information regarding the advertised functionalities; and

selecting at the BTS a serving mobility management entity (MME) from the list of candidate MMEs based at least in part on the information relating to the advertised functionalities.