VIRTUAL MOBILE MANAGEMENT ENTITY MANAGEMENT

• US 20180206108A1
• Filed: 12/23/2015
• Published: 07/19/2018
• Est. Priority Date: 07/27/2015
• Status: Active Grant

• Current Assignee: Apple Inc.
• Original Assignee: Intel IP Corporation (Intel Corporation)
• Inventors: Chou, Joey
• Granted Patent: US 10,595,190 B2
• Time in Patent Office: Days
• CPC Class Codes: H04W 28/088 among core entities
• CPC Class Codes: H04W 8/12 between location registers or mobility servers

Abstract

The present disclosure provides systems for instantiating and terminating a MME VNF. The MME VNF is instantiated and/or terminated using an EM, a NM, a VNFM, a VIM, a NFVO and/or a catalog. Instantiating an MME VNF includes on-boarding the VNF package, creating a managed element, executing the enabled VNF package, instantiating the MME VNF instance, creating the MME function and modifying the MME pool to add the MME VNF instance. Terminating the MME VNF includes decommissioning the MME VNF services, modifying the MME pool to remove the MME VNF from the MME pool, and terminating the MME VNF instance.

Claims

1. An element manager, comprising:

electronic memory;

one or more processors configured to access the electronic memory to;

receive, from a network manager (NM), a request to create a management object instance;

receive, from a virtual network function manager (VNFM), a notification of a successful instantiation of a virtual mobile management entity (VMME);

create the management object instance in response to receiving the request and the notification;

add the management object instance to a mobile management entity (MME) pool to manage a plurality of user equipment (UE) in a mobile communication system; and

notify the NM of the creation of the management object instance.

2. The element manager of claim 1, wherein the managed object instance is a Managed Element Object.

3. The element manager of claim 1, wherein the management object instance is created with at least a user defined state attribute, a vendor name attribute, a version attribute, a managed element type attribute, and a virtual network function (VNF) image identification (ID) attribute.

4. The element manager of claim 1, further configured to modify attributes of the managed object instance in response to receiving a request to modify the attributes.

5. The element manager of claim 4, wherein at least the user defined state attribute is modified to an enabled value in response to a request from the NM.

6. The element manager of claim 1, further configured to create a mobile management entity MME function object that inherits from the managed object instance.

7. The element manager of claim 1, further configured to add the management object instance to the MME pool by setting an mMEPoolMemberList attribute of the MME pool object equal to a domain name (DN) of the MMEFunction object.

8. The element manager of claim 7, further configured to set the MMEPool attribute of the MMEFunction object equal to the DN of the MMEPool object.

9. A computer-readable storage medium having stored thereon instructions that, when implemented by a computing device, cause the computing device to perform operations for a virtual mobile management entity virtual network function (MME VNF) instantiation, the operations comprising:

on-boarding a virtual network function (VNF) package in response to a request for mobile management entity (MME) resources;

creating a management object instance in response to the on-boarding of the VNF package;

enabling the VNF package based on the on-boarding of the VNF package in response to the creation of the management object instance; and

instantiating a MME VNF based on the enablement of the VNF package in response to the enablement of the VNF package.

10. The computer-readable medium of claim 9, wherein on-boarding the VNF package further comprises:

submitting the VNF package to a network function virtualization orchestrator (NFVO) to be included in a catalog; and

receiving an acknowledgement from the NFVO of a completion of the on-boarding of the VNF package.

11. The computer-readable medium of claim 9, wherein enabling the VNF package marks the VNF package as enabled at the catalog.

12. The computer-readable medium of claim 11, wherein enabling the VNF package further comprises:

sending a request to the NFVO to enable the VNF package; and

receiving an acknowledgement from the NFVO of an enablement of the VNF package.

13. The computer-readable medium of claim 9, wherein instantiating the MME VNF further comprises:

sending a request to the NFVO to instantiate the MME VNF; and

receiving an acknowledgement from the NFVO of an instantiation of the MME VNF.

14. The computer-readable medium of claim 9, wherein creating the management object instance further comprises sending, to an element manager (EM), a plurality of configuration management (CM) commands.

15. The computer-readable medium of claim 14, wherein the CM commands include:

a command to create the management object instance; and

a command to modify the attributes of the created management object instance.

16. A system comprising:

an element manager (EM) comprising one or more processors and configured to;

decommission virtual mobile management entity (VMME) services provided by a VMME;

remove the VMME from a mobile management entity (MME) pool;

a virtual network function manager (VNFM) comprising one or more processors configured to;

terminate the VMME; and

release the virtualized resources.

17. The system of claim 16, wherein the EM is further configured to request a move of a user equipment (UE) from the VMME to a different MME.

18. The system of claim 16, wherein the EM is further configured to remove the VMME from the MME pool by deleting a DN of the VMME from the mMEPoolMemberList attribute of the MME pool.

19. The system of claim 16, wherein the EM is further configured to delete the MMEFunction associated with the VMME.

20. The system of claim 16, further comprising the NM comprising one or more processors and configured to:

request a decommission of the VMME services;

request a removal of the VMME from the MME pool; and

request a termination of the VMME.

21. A network function virtualization orchestrator (NFVO), comprising:

electronic memory;

one or more processors configured to access the electronic memory to;

receive, from a network manager (NM), a request to on-board a virtual network function (VNF) package in response to a request for mobile management entity (MME) resources;

on-board the VNF package;

receive, from the NM, a request to enable the VNF package;

enable the VNF package;

receive, from the NM, a request to instantiate the VNF package; and

instantiate the VNF package.

22. The NFVO of claim 21, wherein the NFVO instantiates the VNF package by requesting that a virtual infrastructure manager (VIM) start network and virtual resources.

23. A method comprising:

receiving, from a virtual network function manager (VNFM), a notification of a successful instantiation of a virtual mobile management entity (VMME);

creating the management object instance in response to receiving the request and the notification;

adding the management object instance to a mobile management entity (MME) pool to manage a plurality of user equipment (UE) in a mobile communication system; and

notifying the NM of the creation of the management object instance.