# US 11,909,584 B2 · System and method of data communication

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 11,909,584 B2
- Document ID: US11909584B2
- Status: Granted
- Kind: B2
- Application number: 18/171,193
- Filed: 2023-02-17
- Published: 2023-06-22
- Granted: 2024-02-20
- Earliest claimed: 2018-12-31
- Assignees: Meta Platforms, Inc.
- Applicants: Meta Platforms, Inc.
- Inventors: Amar Padmanabhan; Praveen Kumar Ramakrishnan; Shaddi Husein Hasan; Anoop Singh Tomar; Evgeniy Makeev; Omar Ramadan; Jiannan Ouyang; Xiaochen Tian; Thomas Romano; Ting Xia; Jagannath Rallapalli; Kuan-Yu Li; Shruti Sanadhya
- Web page: https://patentgrep.com/patent/US11909584B2

## CPC

- H04L 41/0895: Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
- H04L 12/4633: {Interconnection of networks using encapsulation techniques, e.g. tunneling}
- H04L 41/0806: for initial configuration or provisioning, e.g. plug-and-play
- 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)
- H04L 41/40: using virtualisation of network functions or resources, e.g. SDN or NFV entities
- H04L 43/0805: by checking availability
- H04L 43/20: the monitoring system or the monitored elements being virtualised, abstracted or software-defined entities, e.g. SDN or NFV
- 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]
- H04L 41/0816: the condition being an adaptation, e.g. in response to network events
- H04L 41/0886: {Fully automatic configuration}
- H04L 41/5054: Automatic deployment of services triggered by the service manager, e.g. service implementation by automatic configuration of network components
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Particular embodiments may detect, by a core network, a change in network traffic types from a first network traffic type to a second network traffic type. The core network includes one or more network functionality components. Each of the one or more network functionality components is decomposed into multiple service types. The core network may determine several service instances for deployment in response to the change in the network traffic types. Each of the service instances may belong to one of the multiple decomposed service types. The core network may deploy several service instances to one or more server machines of the core network according to a decomposed service type of a respective service instance.

## Claims

### Claim 1

A method comprising:
detecting, by a core network, a change in network traffic types from a first network traffic type to a second network traffic type, 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;
determining, by the core network, a plurality of service instances for deployment in response to the change in the network traffic types, 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 decomposed service type of a respective service instance of the plurality of service instances.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
forming one or more pipelines, wherein the one or more pipelines comprise a sequence of the plurality of service instances.

### Claim 3 (depends on 2)

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.

### Claim 4 (depends on 2)

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

### Claim 5 (depends on 1)

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

### Claim 6 (depends on 1)

The method of claim 1, further comprising:
scheduling, by the core network, the plurality of service instances for deployment to accomplish a task.

### Claim 7 (depends on 6)

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

### Claim 8 (depends on 1)

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.

### Claim 9 (depends on 1)

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.

### Claim 10 (depends on 1)

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).

### Claim 11

One or more computer-readable non-transitory storage media embodying software that is operable when executed to:
detect, by a core network, a change in network traffic types from a first network traffic type to a second network traffic type, 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;
determine, by the core network, a plurality of service instances for deployment in response to the change in the network traffic types, 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 decomposed service type of a respective service instance of the plurality of service instances.

### Claim 12 (depends on 11)

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 a sequence of the plurality of service instances.

### Claim 13 (depends on 12)

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.

### Claim 14 (depends on 12)

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

### Claim 15 (depends on 11)

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

### Claim 16 (depends on 11)

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 a task.

### Claim 17 (depends on 16)

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

### Claim 18 (depends on 11)

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 add one or more new service types.

### Claim 19 (depends on 11)

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.

### Claim 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:
detect, by a core network, a change in network traffic types from a first network traffic type to a second network traffic type, 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;
determine, by the core network, a plurality of service instances for deployment in response to the change in the network traffic types, 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 decomposed service type of a respective service instance of the plurality of service instances.