System and method of data communication

• US 10,708,124 B1
• Filed: 12/31/2018
• Issued: 07/07/2020
• Est. Priority Date: 12/31/2018
• Status: Active Grant

• Current Assignee: Meta Platforms, Inc. (f/k/a Facebook, Inc.)
• Original Assignee: Meta Platforms, Inc. (f/k/a Facebook, Inc.)
• Inventors: Padmanabhan, Amar, Ramakrishnan, Praveen Kumar, Hasan, Shaddi Husein, Tomar, Anoop Singh, Makeev, Evgeniy, Ramadan, Omar, Ouyang, Jiannan, Tian, Xiaochen, Romano, Thomas, Xia, Ting, Rallapalli, Jagannath, Li, Kuan-Yu, Sanadhya, Shruti
• Primary Examiner(s): Eskandarnia, Arvin
• Application Number:
  US16/237,328
• Publication Number:
  US 20200213187A1
• Time in Patent Office: 554 Days
• CPC Class Codes: H04L 12/4633 Interconnection of networks using encapsulation techniques, e.g. tunneling
• CPC Class Codes: H04L 41/08 Configuration management of networks or network elements address allocation H04L61/50
• CPC Class Codes: H04L 41/0806 for initial configuration or provisioning, e.g. plug-and-play
• CPC Class Codes: H04L 41/0816 the condition being an adaptation, e.g. in response to network events
• CPC Class Codes: H04L 41/0886 Fully automatic configuration
• CPC Class Codes: H04L 41/0895 Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
• CPC Class Codes: H04L 41/0896 Bandwidth or capacity management, i.e. automatically increasing or decreasing capacities flow or congestion control using dynamic resource allocation, e.g. in-call renegotiation, H04L47/76
• CPC Class Codes: H04L 41/40 using virtualisation of network functions or resources, e.g. SDN or NFV entities
• CPC Class Codes: H04L 41/5054 Automatic deployment of services triggered by the service manager, e.g. service implementation by automatic configuration of network components
• CPC Class Codes: H04L 43/0805 by checking availability
• CPC Class Codes: H04L 43/20 the monitoring system or the monitored elements being virtualised, abstracted or software-defined entities, e.g. SDN or NFV
• CPC Class Codes: H04L 67/1097 for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]

Abstract

Particular embodiments may communicate to a core network by a user device via an access point. The user device may be authenticated by the core network which comprises one or more network functionality components, and each of the one or more network functionality components may be decomposed into multiple service types. The core network may receive a user task associating with service instances. Each of the service instances may belong to one of the multiple decomposed service types and be configured by a service chaining orchestration entity. The service instances may be deployed to one or more of server machines of the core network with respect to the configurations of the service instances, by a service chaining orchestration entity. The capacity of the core network may be scaled up or down by network dimensioning.

Claims

1. A system comprising:

one or more server machines of a core network, wherein the core network is communicated with a user device via an access point;

one or more network functionality components, wherein each of the one or more network functionality components is decomposed into multiple service types, and each of the multiple service types resides in a respective server machine;

a plurality of service instances associating with a user task, wherein the user task is received by one of the plurality of service instances, and each of the plurality of service instances belongs to one of the decomposed multiple service types; and

a service chaining orchestration entity configuring deployment of the plurality of service instances, wherein the plurality of service instances is deployed to the one or more server machines with respect to the configurations of the plurality of service instances, and the capacity of the core network is scaled up or down by network dimensioning.

2. The system of claim 1 further comprising one or more pipelines including the plurality of service instances in a sequence, wherein the sequence is determined by configurations of the plurality of service instances.

3. The system of claim 2 wherein the one or more server machines being deployed are determined by hashing one or more fields of an encapsulation header of an encapsulation protocol.

4. The system of claim 2 wherein the one or more pipelines comprises message pipeline.

5. The system of claim 1 wherein the decomposition of the functionality components is a service-oriented decomposition.

6. The system of claim 1 wherein the deployment of the plurality of service instances is based on resource requirements of the plurality of service instances and the availability of the server machines, wherein the server machines are in a computation center including a centralized computation center or a virtual computation center.

7. The system of claim 1 wherein the service chaining orchestration entity is further configured to update one or more of the multiple service types or to add one or more new service types.

8. The system of claim 1 wherein the service chaining orchestration entity is further configured to update the configurations of the plurality of service instances.

9. The system of claim 1 wherein the network dimensioning includes dynamically adjusting the number of the plurality of service instances or consolidating the servicer machines being deployed with respect to a network load.

10. The system of claim 1 wherein the one or more functionality components include at least a Mobility Management Entity (MME), a Service Gateway (SGW), or a Packet Gateway (PGW).

11. A method comprising:

communicating, by a user device, to a core network via an access point, wherein the core network comprises one or more network functionality components, and each of the one or more network functionality components is decomposed into multiple service types;

receiving, by the core network, a user task associating with a plurality of service instances, wherein each of the plurality of service instances belongs to one of the multiple decomposed service types;

configuring, by the core network, the plurality of service instances; and

deploying, by the core network, the plurality of service instances to one or more server machines of the core network with respect to the configurations of the plurality of service instances, and the capacity of the core network is scaled up or down by network dimensioning.

12. The method of claim 11 further comprising

forming one or more pipelines, wherein the one or more pipelines comprise the plurality of service instances, wherein a sequence of the plurality of service instances in a pipeline is determined with respect to configurations of the plurality of service instances.

13. The method of claim 12 further comprising hashing one or more fields of an encapsulation header of an encapsulation protocol for determining which one or more server machines are deployed.

14. The method of claim 12 further comprising forming at least a message pipeline.

15. The method of claim 11 wherein the decomposing each of the one or more functionality components is service-oriented decomposing.

16. The method of claim 11 wherein the deploying of the plurality of service instances is based on resource requirements of the plurality of service instances and the availability of the server machines, wherein the server machines are in a computation center including a centralized computation center or a virtual computation center.

17. The method of claim 11 further comprising updating one or more of the multiple service types or adding one or more new service types.

18. The method of claim 11 further comprising reconfiguring the plurality of service instances.

19. The method of claim 11 wherein the network dimensioning includes dynamically adjusting the number of the plurality of service instances or consolidating the servicer machines being deployed with respect to a network load.

20. The method of claim 11 wherein the decomposing each of the one or more functionality components include decomposing functionality components of at least a Mobility Management Entity (MME), a Service Gateway (SGW), or a Packet Gateway (PGW).