Systems and methods for designing network slices using extensible components
A system may include one or more devices that with processors. The processors are configured to: receive instructions to assemble a slice service design for a network using slice design components; store the slice service design; and receive a request to deploy a slice service specified by the slice service design. The processors may be configured to: deploy the slice service in subnets of the network; or deploy services defined by portions of the slice service design in some of the subnets of the network.
1. A system comprising one or more devices that include:
one or more processors, and
a memory to store instructions executable by the processors, wherein the processors are configured to:
receive, from a user, design inputs for a network service deployment unit (NDU), a network service component, which defines a network slice, and a location component, wherein the location component specifies a particular network cloud in which the network slice is instantiated; and
instantiate the network slice in the particular network cloud in accordance with the location Component.
2. The system of claim 1 , wherein when the processors instantiate the network slice, the processors are configured to:
retrieve a document, from a database, that corresponds to the network service, wherein the document is written in a Topology and Orchestration Specification for Cloud Applications (TOSCA) language.
3. The system of claim 1 , wherein the network service component includes descriptions of a network function comprising one of:
a Unified Data Management (UDM);
a Policy Control Function (PCF);
a Network Slice Selection Function (NFF);
an Authentication Server Function (AUSF);
a Network Repository Function (NRF);
a Network Exposure Function (NEF); or
a Charging Function (CHF).
4. The system of claim 1 , wherein when the processors instantiate the network slice, the processors are configured to:
apply configuration parameters specified by configuration components included in the network service component.
5. The system of claim 1 , the processors are further configured to:
receive inputs for designing an end-to-end network slice service, wherein the inputs include metadata for the network slice, and wherein the metadata includes:
a virtual local area network (VLAN) identifier (ID) that corresponds to the network slice.
6. The system of claim 5 , wherein the processors are further configured to:
create an end-to-end component that encapsulates the design of the end-to-end network slice service, and wherein the end-to-end component includes:
a set of NDUs, of which only one NDU, among the NDUs, is instantiated when a condition associated with the set is satisfied.
7. The system of claim 5 , wherein the end-to-end component includes a slice assurance service (SAS) component that defines a service for monitoring a Quality of Service (QoS) of a service rendered by the network slice.
8. The system of claim 7 , wherein the SAS component includes the location component.
9. A method comprising:
receiving, from a user, design inputs for a network service deployment unit (NDU), a network service component which defines a network slice, and a location component, wherein the location component specifies a particular network cloud in which the network slice is instantiated;
and instantiating the network slice in the particular network cloud in accordance with the location component.
10. The method of claim 9 , wherein instantiating the network slice includes:
retrieve a document, from a database, that corresponds to the network service, wherein the document is written in a Topology and Orchestration Specification for Cloud Applications (TOSCA) language.
11. The method of claim 9 , wherein the network service component includes descriptions of a network function comprising one of:
a Unified Data Management (UDM);
a Policy Control Function (PCF);
a Network Slice Selection Function (NFF);
an Authentication Server Function (AUSF);
a Network Repository Function (NRF);
a Network Exposure Function (NEF); or
a Charging Function (CHF).
12. The method of claim 9 , wherein instantiating the network slice includes:
apply configuration parameters specified by configuration components included in the network service component.
13. The method of claim 9 , further comprising:
receiving inputs for designing an end-to-end network slice service, wherein the inputs include metadata for the network slice, and wherein the metadata includes:
a virtual local area network (VLAN) identifier (ID) that corresponds to the network slice.
14. The method of claim 13 , further comprising:
creating an end-to-end component that encapsulates the design of the end-to-end network slice service, and wherein the end-to-end component includes:
a set of NDUs, of which only one NDU, among the NDUs, is instantiated when a condition associated with the set is satisfied.
15. The method of claim 13 , wherein the end-to-end component includes a slice assurance service (SAS) component that defines a service for monitoring a Quality of Service (QoS) of a service rendered by the network slice.
16. The method of claim 15 , wherein the SAS component includes the location component.
17. A non-transitory computer-readable medium comprising processor-executable instructions, which when executed by processors, cause the processors to:
receive, from a user, design inputs for a network service deployment unit (NDU), a network service component which defines a network slice, and a location component, wherein the location component specifies a particular network cloud in which the network slice is instantiated; and
instantiate the network slice in the particular network cloud in accordance with the location component.
18. The non-transitory computer-readable medium of claim 17 , wherein when the processors instantiate the network slice, the instructions cause the processors to:
retrieve a document, from a database, that corresponds to the network service, wherein the document is written in a Topology and Orchestration Specification for Cloud Applications (TOSCA) language.
19. The non-transitory computer-readable medium of claim 17 , wherein the network service component includes descriptions of a network function comprising one of:
a Unified Data Management (UDM);
a Policy Control Function (PCF);
a Network Slice Selection Function (NFF);
an Authentication Server Function (AUSF);
a Network Repository Function (NRF);
a Network Exposure Function (NEF); or
a Charging Function (CHF).
20. The non-transitory computer-readable medium of claim 17 , wherein when the processors instantiate the network slice, the instructions cause the processors to:
apply configuration parameters specified by configuration components included in the network service component.