IP Library Granted Patent US 11,588,680
Granted Patent B2
US 11,588,680 · App. 17/177,084 · Granted Feb 21, 2023

System and method of data communication

Inventors: Amar Padmanabhan (Menlo Park, CA); Praveen Kumar Ramakrishnan (San Carlos, CA); Shaddi Husein Hasan (Blacksburg, VA); Anoop Singh Tomar (Santa Clara, CA); Evgeniy Makeev (Belmont, CA); Omar Ramadan (Berkeley, CA); Jiannan Ouyang (Palo Alto, CA); Xiaochen Tian (San Mateo, CA); Thomas Romano (San Francisco, CA); Ting Xia (Vancouver, CA); Jagannath Rallapalli (San Jose, CA); Kuan-Yu Li (Mountain View, CA); Shruti Sanadhya (Sunnyvale, CA)
Assignee: Meta Platforms, Inc.
H04L41/08H04L12/4633H04L67/1097
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,588,680
App. No.
17/177,084
Granted
Feb 21, 2023
Kind
B2
Abstract

Particular embodiments may receive a request to perform a task 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 identify service instances for deployment based on the task. Each of the service instances may belong to one of the multiple decomposed service types. The service instances may be deployed to one or more server machines to accomplish the task by the core network based on resource requirements of the service instances and current resource availability of the one or more server machines.

Claims (39)

1. A method comprising:

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

identifying, by the core network, a plurality of service instances for deployment to accomplish the task, wherein each of the plurality of service instances belongs to one of the multiple decomposed service types; and

deploying, by the core network, the plurality of service instances to one or more server machines of the core network according to a schedule based on resource requirements of the service instances and current resource availability of the one or more server machines.

2. The method of claim 1 , further comprising:

forming one or more pipelines, wherein the one or more pipelines comprise the sequence of the plurality of service instances.

3. The method of claim 2 , further comprising:

hashing one or more fields of an encapsulation header of an encapsulation protocol for determining which of the one or more server machines are deployed.

4. The method of claim 2 , further comprising forming a message pipeline.

5. The method of claim 1 , wherein the one or more network functionality components are decomposed into multiple service types by a service-oriented decomposing.

6. The method of claim 1 , further comprising:

scheduling, by the core network, the plurality of service instances for deployment to accomplish the task.

7. The method of claim 6 , further comprising rescheduling the plurality of service instances.

8. The method of claim 1 , further comprising:

updating one or more of the multiple decomposed service types or adding one or more new service types.

9. The method of claim 1 , further comprising:

scaling a capacity of the core network by network dimensioning, wherein the network dimensioning includes dynamically adjusting a number of the plurality of service instances or consolidating the servicer machines being deployed with respect to a network load.

10. The method of claim 1 , 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).

11. One or more computer-readable non-transitory storage media embodying software that is operable when executed to:

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

identify, by the core network, a plurality of service instances for deployment to accomplish the task, wherein each of the plurality of service instances belongs to one of the multiple decomposed service types; and

deploy, by the core network, the plurality of service instances to one or more server machines of the core network according to a schedule based on resource requirements of the service instances and current resource availability of the one or more server machines.

12. The media of claim 11 , wherein the software is further operable when executed to:

form one or more pipelines, wherein the one or more pipelines comprise the sequence of the plurality of service instances.

13. The media of claim 12 , wherein the software is further operable when executed to:

hash one or more fields of an encapsulation header of an encapsulation protocol for determining which of the one or more server machines are deployed.

14. The media of claim 12 , wherein the software is further operable when executed to form a message pipeline.

15. The media of claim 11 , wherein the one or more network functionality components are decomposed into multiple service types by a service-oriented decomposing.

16. The media of claim 11 , wherein the software is further operable when executed to:

schedule, by the core network, the plurality of service instances for deployment to accomplish the task.

17. The media of claim 16 , wherein the software is further operable when executed to reschedule the plurality of service instances.

18. The media of claim 11 , wherein the software is further operable when executed to:

update one or more of the multiple decomposed service types or adding one or more new service types.

19. The media of claim 11 , wherein the software is further operable when executed to:

scale a capacity of the core network by network dimensioning, wherein the network dimensioning includes dynamically adjusting a number of the plurality of service instances or consolidating the servicer machines being deployed with respect to a network load.

20. A system comprising: one or more processors; and a memory coupled to the processors comprising instructions executable by the processors, the processors being operable when executing the instructions to:

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

identify, by the core network, a plurality of service instances for deployment to accomplish the task, wherein each of the plurality of service instances belongs to one of the multiple decomposed service types; and

deploy, by the core network, the plurality of service instances to one or more server machines of the core network according to a schedule based on resource requirements of the service instances and current resource availability of the one or more server machines.

Assignments (1)
CHANGE OF NAME Recorded Dec 20, 2021
From: FACEBOOK, INC.
To: META PLATFORMS, INC.
Reel/Frame 058553/0802 →
Continuity (3)
Continuation 16865196 · May 1, 2020
Continuation 16237328 · Dec 31, 2018
Related Publication 20210168026A1 · Jun 3, 2021