Joint orchestration for private mobile network
Some embodiments provide a method for implementing a software-defined private mobile network (SD-PMN) for an entity. At a physical location of the entity, the method deploys a first set of control plane components for the SD-PMN, the first set of control plane components including a security gateway, a user-plane function (UPF), an AMF (access and mobility management function), and an SMF (session management function). At an SD-WAN (software-defined wide area network) PoP (point of presence) belonging to a provider of the SD-PMN, the method deploys a second set of control plane components for the SD-PMN that includes a subscriber database that stores data associated with users of the SD-PMN. The method uses an SD-WAN edge router located at the physical location of the entity and a SD-WAN gateway located at the SD-WAN PoP to establish a connection from the physical location of the entity to the SD-WAN PoP.
1. A method for providing joint orchestration across a system comprising an SD-PMN (software-defined private mobile network) and SD-WAN (software-defined wide area network) for an edge application, the method comprising:
at a PMN orchestrator:
receiving a first intent-based API (application programming interface) specifying a set of parameters for the edge application to be deployed for the SD-PMN, the set of parameters comprising a plurality of desired networking requirements for the edge application;
from the plurality of networking requirements specified by the first intent-based API, generating (i) a second intent-based API to provide to a management system for a RAN (radio access network), the second API comprising a first set of networking parameters for the RAN management system to configure the SD-PMN to provide desired PMN network requirements for the edge application, and (ii) a third intent-based API to provide to a management system of the SD-WAN, the third API comprising a second set of networking parameters for the SD-WAN management system to use to configure the SD-WAN to provide desired WAN network requirements for the edge application; and
sending (i) the second intent-based API to the RAN management system to configure the SD-PMN to provide the desired PMN network requirements for the edge application, and (ii) the third intent-based API to the SD-WAN management system to configure the SD-WAN to provide the desired WAN network requirements for the edge application.
2. The method of claim 1 , wherein the first intent-based API comprises a user-defined first intent-based API and receiving the first intent-based API comprises receiving the user-defined first intent-based API from a user that manages the joint orchestration for the system.
3. The method of claim 1 , wherein:
the set of parameters specified by the first intent-based API further comprises a plurality of desired resource requirements; and
generating the second and third intent-based APIs further comprises generating, from the plurality of desired resource requirements, a fourth intent-based API to provide to a management system for an edge compute stack that connects the SD-PMN to the SD-WAN, the fourth API comprising a set of resource parameters for the edge compute stack management system to configure the edge compute stack to provide a set of resource requirements for the edge application.
4. The method of claim 3 , wherein the set of resource parameters of the third intent-based API comprises parameters for defining (i) a set of resources to be allocated for the edge application according to the set of resource requirements, and (ii) a container image URL for the edge application.
5. The method of claim 1 , wherein the first set of networking parameters of the second intent-based API comprises parameters for (i) defining a subscriber group for devices requiring connectivity to the edge application and (ii) defining QoS requirements for the edge application.
6. The method of claim 5 , wherein the QoS requirements comprise QoS requirements to be applied to traffic associated with devices belonging to the subscriber group.
7. The method of claim 1 , wherein the second set of networking parameters of the third intent-based API comprises parameters for (i) identifying application traffic associated with the edge application, and (ii) adding one or more business policies regarding a priority level for application traffic associated with the edge application.
8. The method of claim 7 , wherein the priority level is defined based on QoS requirements defined as part of the plurality of desired networking requirements of the first intent-based API.
9. The method of claim 1 , wherein:
the plurality of networking requirements comprises a set of security requirements for the edge application; and
generating the second and third intent-based APIs further comprises generating a fourth intent-based API to provide to a management system for a set of SASE (secure access service edge) services that is used by the SD-PMN, the fourth API comprising a third set of networking parameters for the SASE services management system to configure the SASE services to provide the set of security requirements for the edge application.
10. The method of claim 9 , wherein the third set of networking parameters of the third intent-based API comprises parameters for defining (i) security services for a service chain based on the set of security requirements, and (ii) a set of new security policies based on the set of security requirements, wherein at least one new security policy in the set of new security policies comprises a URL filtering security policy for application traffic associated with the edge application.
11. A non-transitory machine readable medium storing a program for execution by a set of processing units, the program for providing joint orchestration across a system comprising an SD-PMN (software-defined private mobile network) and SD-WAN (software-defined wide area network) for an edge application, the program comprising sets of instructions for:
at a PMN orchestrator:
receiving a first intent-based API (application programming interface) specifying a set of parameters for the edge application to be deployed for the SD-PMN, the set of parameters comprising a plurality of desired requirements for the edge application;
from the plurality of networking requirements specified by the first intent-based API, generating (i) a second intent-based API to provide to a management system for a RAN (radio access network), the second API comprising a first set of networking parameters for the RAN management system to configure the SD-PMN to provide desired PMN network requirements for the edge application, and (ii) a third intent-based API to provide to a management system of the SD-WAN, the third API comprising a second set of networking parameters for the SD-WAN management system to use to configure the SD-WAN to provide desired WAN networking requirements for the edge application; and
sending (i) the second intent-based API to the RAN management system to configure the SD-PMN to provide the desired PMN network requirements for the edge application, and (ii) the third intent-based API to the SD-WAN management system to configure the SD-WAN to provide the desired WAN network requirements for the edge application.
12. The non-transitory machine readable medium of claim 11 , wherein the first intent-based API comprises a user-defined first intent-based API and receiving the first intent-based API comprises receiving the user-defined first intent-based API from a user that manages the joint orchestration for the system.
13. The non-transitory machine readable medium of claim 11 , wherein:
the set of parameters specified by the first intent-based API further comprises a plurality of desired resource requirements; and
the set of instructions for generating the second and third intent-based APIs further comprises a set of instructions for generating, from the plurality of desired resource requirements, a fourth intent-based API to provide to a management system for an edge compute stack that connects the SD-PMN to the SD-WAN, the fourth API comprising a set of resource parameters for the edge compute stack management system to configure the edge compute stack to provide a set of resource requirements for the edge application.
14. The non-transitory machine readable medium of claim 13 , wherein the set of resource parameters of the third intent-based API comprises parameters for defining (i) a set of resources to be allocated for the edge application according to the set of resource requirements, and (ii) a container image URL for the edge application.
15. The non-transitory machine readable medium of claim 11 , wherein the first set of networking parameters of the second intent-based API comprises parameters for (i) defining a subscriber group for devices requiring connectivity to the edge application and (ii) defining QoS requirements for the edge application.
16. The non-transitory machine readable medium of claim 15 , wherein the QoS requirements comprise QoS requirements to be applied to traffic associated with devices belonging to the subscriber group.
17. The non-transitory machine readable medium of claim 11 , wherein the second set of networking parameters of the third intent-based API comprises parameters for (i) identifying application traffic associated with the edge application, and (ii) adding one or more business policies regarding a priority level for application traffic associated with the edge application.
18. The non-transitory machine readable medium of claim 17 , wherein the priority level is defined based on QoS requirements defined as part of the plurality of desired networking requirements of the first intent-based API.
19. The non-transitory machine readable medium of claim 11 , wherein:
the plurality of networking requirements comprises a set of security requirements for the edge application; and
the set of instructions for generating the second and third intent-based APIs further comprises a set of instructions for generating a fourth intent-based API to provide to a management system for a set of SASE (secure access service edge) services that is used by the SD-PMN, the fourth API comprising a third set of networking parameters for the SASE services management system to configure the SASE services to provide the set of security requirements for the edge application.
20. The non-transitory machine readable medium of claim 19 , wherein the third set of networking parameters of the third intent-based API comprises parameters for defining (i) security services for a service chain based on the set of security requirements, and (ii) a set of new security policies based on the set of security requirements, wherein at least one new security policy in the set of new security policies comprises a URL filtering security policy for application traffic associated with the edge application.