# US 11,310,733 B1 · On-demand application-driven network slicing

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

- Number: US 11,310,733 B1
- Document ID: US11310733B1
- Status: Granted
- Kind: B1
- Application number: 17/118,568
- Filed: 2020-12-10
- Granted: 2022-04-19
- Earliest claimed: 2020-12-10
- Assignees: Amazon Technologies, Inc.
- Applicants: Amazon Technologies, Inc.
- Inventors: Diwakar Gupta; Kiran Kumar Edara; Igor A. Kostic; Kaixiang Hu; Shane Ashley Hall; Ishwardutt Parulkar
- Web page: https://patentgrep.com/patent/US11310733B1

## CPC

- H04W 4/021: Services related to particular areas, e.g. point of interest [POI] services, venue services or geofences
- H04W 48/18: Selecting a network or a communication service
- H04L 41/0806: for initial configuration or provisioning, e.g. plug-and-play
- H04L 41/5054: Automatic deployment of services triggered by the service manager, e.g. service implementation by automatic configuration of network components
- H04L 43/0852: Delays
- H04L 45/64: using an overlay routing layer
- H04L 47/781: {Centralised allocation of resources}
- H04W 4/50: Service provisioning or reconfiguring
- H04W 4/60: Subscription-based services using application servers or record carriers, e.g. SIM application toolkits
- H04W 24/02: Arrangements for optimising operational condition
- H04W 28/0268: {using specific QoS parameters for wireless networks, e.g. QoS class identifier [QCI] or guaranteed bit rate [GBR] (negotiating SLA or negotiating QoS H04W28/24)}
- H04W 28/0967: {Quality of Service [QoS] parameters}
- H04W 28/16: Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
- H04L 41/0895: Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
- H04L 41/0897: by horizontal or vertical scaling of resources, or by migrating entities, e.g. virtual resources or entities
- H04L 41/14: Network analysis or design
- 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
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Disclosed are various embodiments for on-demand application-driven network slicing. In one embodiment, it is determined that an application executed in a particular computing device has a quality-of-service requirement. The particular computing device is connected to a communications network. A request is sent that causes a network slice allocation service to reserve a network slice having the quality-of-service requirement in the communications network. Data to or from the application is transmitted using the network slice.

## Claims

### Claim 1

A system, comprising:
a radio-based network including a radio access network and associated core network, wherein an application utilizes a network slice of the radio-based network to send and/or receive network traffic;
a network slice allocation service configured to dynamically modify the network slice in response to application programming interface (API) requests from the application; and
at least one computing device implementing the application, wherein the application is configured to at least:
determine that the network slice does not meet a quality-of-service requirement including at least one of: a minimum bandwidth requirement or a minimum latency requirement;
send a first API request that causes the network slice allocation service to reserve additional capacity for the network slice for the application in the radio-based network, the network slice providing the quality-of-service requirement;
use the network slice to send and/or receive the network traffic;
determine that the network slice exceeds the quality-of-service requirement; and
send a second API request to the network slice allocation service to release at least a portion of capacity reserved for the network slice.

### Claim 2 (depends on 1)

The system of claim 1, wherein the application is further configured to at least:
obtain a token identifying the network slice from the network slice allocation service; and
wherein one or more data packets sent using the network slice identify the network slice with the token.

### Claim 3 (depends on 1)

The system of claim 1, wherein the application is further configured to send or receive subsequent data using a default network connection instead of the network slice after sending the second API request.

### Claim 4

A computer-implemented method, comprising:
determining, by an application implemented via at least one computing device, that the application has a quality-of-service requirement, the particular computing device being connected to a communications network;
sending, by the application, a request that causes a network slice allocation service to reserve a network slice having the quality-of-service requirement in the communications network; and
transmitting data to or from the application using the network slice.

### Claim 5 (depends on 4)

The computer-implemented method of claim 4,
further comprising transmitting other data to or from another application executed in the at least one computing device without using the network slice.

### Claim 6 (depends on 4)

The computer-implemented method of claim 4, further comprising:
determining a duration for the network slice based at least in part on a length of time that the application has the quality-of-service requirement; and
wherein the request specifies the duration.

### Claim 7 (depends on 6)

The computer-implemented method of claim 6, wherein the duration corresponds to a session of the application.

### Claim 8 (depends on 4)

The computer-implemented method of claim 4, further comprising:
determining that the application no longer has the quality-of-service requirement; and
sending, by the application, a subsequent request to the network slice allocation service to release the network slice.

### Claim 9 (depends on 4)

The computer-implemented method of claim 4, further comprising:
determining that the application has an increased quality-of-service requirement; and
sending, by the application, a subsequent request that causes the network slice allocation service to modify the network slice to have the increased quality-of-service requirement.

### Claim 10 (depends on 4)

The computer-implemented method of claim 4, further comprising:
determining that the application has a decreased quality-of-service requirement; and
sending, by the application, a subsequent request that causes the network slice allocation service to modify the network slice to have the decreased quality-of-service requirement.

### Claim 11 (depends on 4)

The computer-implemented method of claim 4, further comprising:
determining that another application executed in the at least one computing device has another quality-of-service requirement; and
sending, by the other application, a subsequent request that causes the network slice allocation service to reserve a different network slice for the application, the different network slice being associated with a lesser quality-of-service requirement than a default network slice for the particular computing device.

### Claim 12 (depends on 4)

The computer-implemented method of claim 4, wherein the network slice is associated with a lesser latency than a default network slice.

### Claim 13 (depends on 4)

The computer-implemented method of claim 4, wherein the quality-of-service requirement includes a minimum latency requirement for the application.

### Claim 14 (depends on 4)

The computer-implemented method of claim 4, wherein the quality-of-service requirement includes a minimum bandwidth requirement for the application.

### Claim 15 (depends on 4)

The computer-implemented method of claim 4, wherein sending the request that causes the network slice allocation service to reserve the network slice further comprises sending the request from the application to the network slice allocation service via an application programming interface.

### Claim 16 (depends on 4)

The computer-implemented method of claim 4, further comprising:
receiving, by the application, a user specification of a parameter via a user interface; and
determining, by the application, the quality-of-service requirement based at least in part on the parameter.

### Claim 17

A non-transitory computer-readable medium embodying an application executable in a computing device, wherein when executed the application causes the computing device to at least:
determine that a network slice in a radio-based network does not meet a quality-of-service requirement for an application;
send a request that causes a network slice allocation service to reserve the network slice for the application in the radio-based network, the network slice providing the quality-of-service requirement; and
send or receive data using the network slice.

### Claim 18 (depends on 17)

The non-transitory computer-readable medium of claim 17, wherein when executed the application further causes the computing device to at least:
send a subsequent request to the network slice allocation service to release the network slice.

### Claim 19 (depends on 17)

The non-transitory computer-readable medium of claim 17, wherein when executed the application further causes the computing device to at least determine a duration for the network slice, the duration being a time duration or a data quantity, and the request specifies the duration.

### Claim 20 (depends on 17)

The non-transitory computer-readable medium of claim 17, wherein when executed the application further causes the computing device to determine a maximum latency for the network slice, and the request specifies the maximum latency.