# US 2022/0021538 A1 · Blockchain token-based cloud orchestration architecture for discrete virtual network instances

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

- Number: US 2022/0021538 A1
- Document ID: US20220021538A1
- Status: Published application
- Kind: A1
- Application number: 17/458,842
- Filed: 2021-08-27
- Published: 2022-01-20
- Earliest claimed: 2017-09-13
- Assignees: Vijay Madisetti
- Inventors: Vijay Madisetti; Arshdeep Bahga
- Web page: https://patentgrep.com/patent/US20220021538A1

## CPC

- H04L 9/3239: {involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD}
- H04L 9/0866: {involving user or device identifiers, e.g. serial number, physical or biometrical information, DNA, hand-signature or measurable physical characteristics}
- H04L 9/3213: {using tickets or tokens, e.g. Kerberos (network architectures or network communication protocols for entities authentication using tickets in a packet data network H04L63/0807)}
- H04L 9/50: {using hash chains, e.g. blockchains or hash trees}
- H04L 41/044: comprising hierarchical management structures
- H04L 41/0895: Configuration of virtualised networks or elements, e.g. virtualised network function or OpenFlow elements
- 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 63/105: {Multiple levels of security}
- H04L 67/104: Peer-to-peer [P2P] networks
- H04W 12/086: using security domains
- H04L 2209/56: Financial cryptography, e.g. electronic payment or e-cash
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- H04W: WIRELESS COMMUNICATION NETWORKS (broadcast communication H04H; communication systems using wireless links for non-selective communication, e.g. wireless extensions H04M1/72)

## Abstract

A blockchain-enabled service-based cloud native function (CNF) application architecture including a physical cloud infrastructure that includes computing resources, an application service mesh network including CNF that communicate with each other, and a blockchain-supported network slice orchestration of one or more network slices managed by a slice coin orchestrator, each network slice being an instantiated logical network, is defined by a smart contract deployed on a blockchain network. The slice coin orchestrator transacts smart contracts transferring tokens that are configured to be exchangeable for instantiation of a network slice, defined as slice coins, with each slice coin of the plurality of slice coins being configured to regulate at least one of access to and use by the one or more network slices to at least one of the computing resources and the CNF applications of the application service mesh network.

## Claims

### Claim 1

A blockchain-enabled service-based cloud native function (CNF) application architecture comprising:
physical cloud infrastructure comprising computing resources, the computing resources comprising:
a processor;
memory positioned in communication with the processor; and
a network communication device positioned in communication with the processor;
an application service mesh network comprising a plurality of CNF applications configured to communicate with each other, each application of the plurality of applications being executable on the physical infrastructure;
a blockchain-supported network slice orchestration of one or more network slices managed by a slice coin orchestrator, each network slice being an instantiated logical network, is defined by a smart contract deployed on a blockchain network, and comprises:
a set of network slice functions performed by CNF applications of the application service mesh network; and
resources from the computing resources operable to execute the set of network slice functions; and
wherein the slice coin orchestrator is operable to transact smart contracts transferring tokens that are configured to be exchangeable for instantiation of a network slice, defined as a plurality of slice coins, on the blockchain network, each slice coin of the plurality of slice coins being configured to regulate at least one of access to and use by the one or more network slices to at least one of the computing resources and the CNF applications of the application service mesh network.

### Claim 2 (depends on 1)

The architecture of claim 1 wherein the network slice is configured across computing resources and services controlled by multiple distinct network operators.

### Claim 3 (depends on 1)

The architecture of claim 1 wherein the plurality of slice coins is configured to regulate access to enforce at least one of security constraints, service constraints, and computing resources.

### Claim 4 (depends on 3)

The architecture of claim 3 wherein:
a first slice coin of the plurality of slice coins is configured to regulate access to enforce a security constraint;
a second slice coin of the plurality of slice coins is configured to regulate access to enforce a service constraint; and
a third slice coin of the plurality of slice coins is configured to regulate access to computing resources.

### Claim 5 (depends on 1)

The architecture of claim 1 wherein usage of each slice coin is tracked by a network slice identifier.

### Claim 6 (depends on 5)

The architecture of claim 5 wherein usage of each slice coin is further tracked by an identifier for a network operator.

### Claim 7 (depends on 1)

The architecture of claim 1 wherein at least one function performed by a CNF application is shared between two of the network slices.

### Claim 8 (depends on 1)

The architecture of claim 1 wherein the network slice is a Kubernetes-based microservices application.

### Claim 9 (depends on 1)

The architecture of claim 1 wherein:
a network slice of the plurality of network slices comprises at least one of a priority, a security level, a security indication, and a duration, defining a network slice requirement; and
wherein the slice coin orchestrator is configured to determine at least one of a quantity and a type of slice coins necessary to instantiate each network slice responsive to the network slice requirement.

### Claim 10 (depends on 1)

The architecture of claim 1 wherein:
the physical cloud infrastructure comprises a plurality of computing devices, each computing device comprising a processor, a memory, and a network communication device, defining computing resources for each computing device of the physical cloud infrastructure; and
the slice coin orchestrator is configured to provision computing resources for each network slice from the plurality of computing devices.

### Claim 11

A method of instantiating a blockchain-enabled service-based cloud native function (CNF) application architecture comprising an application service mesh network comprising a plurality of CNF applications configured to communicate with each other via a blockchain-supported network slice orchestrator, comprising:
receiving a request from a user to instantiate a network slice, defining a network slice request, the network slice request comprising:
a set of network slice functions performed by CNF applications of the application service mesh network; and
computing resources operable to execute the set of network slice functions;
determining at least one of a required quantity of slice coins and slice coin type requirement responsive to the network slice request, defining a slice coin price;
transmitting an indication of the slice coin price to the user;
transacting a smart contract transferring from the user to the network slice orchestrator at least one of a number of slice coins equal to the required quantity of slice coins and slice coins matching the slice coin type requirement on a blockchain network whereupon the slice coins are deployed;
instantiating a network slice responsive to the network slice request, the network slice comprising the set of network slice functions and computing resources provisioned from a cloud infrastructure; and
recording the instantiation to a smart contract deployed on the blockchain.

### Claim 12 (depends on 11)

The method of claim 11 wherein the slice coins are configured to regulate access by the one or more network slices to at least one of the computing resources and the CNF applications of the application service mesh network.

### Claim 13 (depends on 11)

The method of claim 11 wherein the slice coins are configured to regulate access to enforce at least one of security constraints, service constraints, and computing resources.

### Claim 14 (depends on 13)

The method of claim 13 wherein:
a first slice coin of the plurality of slice coins is configured to regulate access to enforce a security constraint;
a second slice coin of the plurality of slice coins is configured to regulate access to enforce a service constraint; and
a third slice coin of the plurality of slice coins is configured to regulate access to computing resources.

### Claim 15 (depends on 11)

The method of claim 11 further comprising tracking the usage of each slice coin by a network slice identifier.

### Claim 16 (depends on 15)

The method of claim 15 further comprising tracking the usage of each slice coin by an identifier for a network operator.

### Claim 17 (depends on 11)

The method of claim 11 wherein at least one function performed by a CNF application is shared between two of the network slices.

### Claim 18 (depends on 11)

The method of claim 11 wherein the network slice is instantiated on a Kubernetes cluster.

### Claim 19 (depends on 11)

The method of claim 11 wherein:
the network slice request further comprises at least one of a priority, a security level, a security indication, and a duration, defining a network slice requirement; and
the slice coins price is determined responsive to the network slice requirement.

### Claim 20

A blockchain-enabled service-based cloud native function (CNF) application architecture comprising:
physical cloud infrastructure comprising a plurality of computing devices, each computing device comprising computing resources, the computing resources comprising:
a processor;
memory positioned in communication with the processor; and
a network communication device positioned in communication with the processor;
an application service mesh network comprising a plurality of CNF applications configured to communicate with each other, each application of the plurality of applications being executable on the physical infrastructure;
a blockchain-supported network slice orchestration of one or more network slices managed by a slice coin orchestrator, each network slice being an instantiated logical network, is defined by a smart contract deployed on a blockchain network, and comprises:
a set of network slice functions performed by CNF applications of the application service mesh network;
resources from the computing resources operable to execute the set of network slice functions; and
a network slice requirement comprising at least one of a priority a security level, a security indication, and a duration;
wherein the slice coin orchestrator is configured to determine at least one of a quantity and a type of slice coins necessary to instantiate each network slice responsive to the network slice requirement;
wherein the slice coin orchestrator is operable to transact smart contracts transferring tokens that are configured to be exchangeable for instantiation of a network slice, defined as a plurality of slice coins, on the blockchain network, each slice coin of the plurality of slice coins being configured to regulate access by the one or more network slices to at least one of the computing resources and the CNF applications of the application service mesh network; and
wherein the slice coin orchestrator is configured to provision computing resources for each network slice from the physical cloud infrastructure.
