Dark fiber dense wavelength division multiplexing service path design for microservices for 5g or other next generation network

Abstract

A dark fiber dense wavelength division multiplexing service path design microservice (ddSPDmS) can provide a scalable self-contained meta-data driven approach for a flexible implementation of a dark fiber dense wavelength division multiplexing (DWDM) service path design solution. The service plan design solution can be used as a standalone solution or integrated with a network management application. In order to manage a large volume of circuit designs, multiple microservices can accept application program interface (API) requests in a cloud environment. Permission can then be given to any application to use the API to make a call to the design and inventory. Additionally, metadata templates can be designed to support a node, a link, and/or a topology for the microservices.

What is claimed is: 
     
         1 . A method, comprising:
 applying, by a system comprising a processor, a network topology template to macro orchestration flow data associated with a network service, wherein the network topology template is representative of a network topology applicable to the network service, and wherein the network topology template comprises device data, representative of respective node devices associated with the network topology, and link data, representative of connection endpoints associated with the respective node devices; and   generating, by the system in response to the applying, micro orchestration flow data representative of a service path, for a microservice to be associated with the network service, within the network topology.   
     
     
         2 . The method of  claim 1 , further comprising:
 receiving, by the system, a request for the micro orchestration flow data, wherein the applying is in response to the receiving of the request.   
     
     
         3 . The method of  claim 1 , further comprising:
 sending, by the system, the micro orchestration flow data to the network service; and   receiving, by the system in response to the sending of the micro orchestration flow data, a request to instantiate the microservice.   
     
     
         4 . The method of  claim 3 , further comprising:
 instantiating, by the system in response to the receiving of the request, the microservice.   
     
     
         5 . The method of  claim 1 , wherein the network topology template further comprises rules data representative of a rule that defines connectivity between the respective node devices. 
     
     
         6 . The method of  claim 1 , wherein the connection endpoints associated with the respective node devices are optical connection endpoints. 
     
     
         7 . The method of  claim 1 , further comprising:
 retrieving, by the system, the device data from a data store.   
     
     
         8 . The method of  claim 1 , further comprising:
 storing, by the system in response to the generating of the micro orchestration flow data, service path data, representative of the service path, to a data store.   
     
     
         9 . The method of  claim 8 , wherein the service path is a first service path, wherein the service path data is first service path data, wherein the network service is a first network service, wherein the generating of the micro orchestration flow data is based on second service path data stored in the data store, and wherein the second service path data is representative of a second service path associated with a second network service. 
     
     
         10 . A system, comprising:
 a processor; and   a memory that stores executable instructions that, when executed by the processor, facilitate performance of operations, comprising:
 applying topology template data to a macro orchestration flow associated with a network service, wherein the topology template data is representative of a network topology applicable to the network service, and wherein the topology template data comprises device template data, representative of respective node devices within the network topology, and link template data, representative of connection endpoints between the respective node devices; and 
 generating, in response to the applying, a micro orchestration flow representative of a service path, for a microservice to be associated with the network service, within the network topology. 
   
     
     
         11 . The system of  claim 10 , wherein the operations further comprise:
 receiving a request for the micro orchestration flow, wherein the applying is in response to the receiving of the request.   
     
     
         12 . The system of  claim 10 , wherein the operations further comprise:
 conveying the micro orchestration flow to the network service;   in response to the conveying, receiving a request to instantiate the microservice; and   in response to the receiving of the request, instantiating the microservice.   
     
     
         13 . The system of  claim 10 , wherein the topology template data further comprises rules template data representative of a rule that defines connectivity between the respective node devices. 
     
     
         14 . The system of  claim 10 , wherein the operations further comprise:
 in response to the generating of the micro orchestration flow, storing service path data, representative of the service path, to a database.   
     
     
         15 . The system of  claim 14 , wherein the service path is a first service path, wherein the service path data is first service path data, wherein the network service is a first network service, and wherein the generating of the micro orchestration flow is based on second service path data stored in the database, the second service path data being representative of a second service path associated with a second network service. 
     
     
         16 . A non-transitory machine-readable medium, comprising executable instructions that, when executed by a processor, facilitate performance of operations, comprising:
 applying topology template data, representative of a topology of a communication network, to first orchestration flow data associated with a network service, the topology template data comprising device data, representative of network devices associated with the communication network, and link data, representative of connection endpoints associated with the network devices; and   generating, in response to the applying, second orchestration flow data, the second orchestration flow data being representative of a service path, within the topology of the communication network, wherein the second orchestration flow data is applicable to a microservice to be associated with the network service.   
     
     
         17 . The non-transitory machine-readable medium of  claim 16 , wherein the operations further comprise:
 receiving a request for the first orchestration flow data via the network service, wherein the applying is in response to the receiving of the request.   
     
     
         18 . The non-transitory machine-readable medium of  claim 16 , wherein the operations further comprise:
 communicating the second orchestration flow data to the network service;   in response to the communicating of the second orchestration flow data, receiving a request to instantiate the microservice via the network service; and   in response to the receiving of the request, instantiating the microservice.   
     
     
         19 . The non-transitory machine-readable medium of  claim 16 , wherein the topology template data further comprises rules data representative of a rule that defines connectivity between the network devices. 
     
     
         20 . The non-transitory machine-readable medium of  claim 16 , wherein the service path is a first service path, wherein the network service is a first network service, and wherein the generating of the second orchestration flow data is based on stored service path data, the stored service path data being representative of a second service path associated with a second network service.