Network arrangement management method and system

Abstract

The invention provides a network arrangement management method and system, and relates to the technical field of communication. Resource nodes in the network are divided into at least one distributed management domain provided with a resource management module and a strategy generation module, the at least one distributed management domain comprises a centralized management domain, and an intention perception module is further arranged in the centralized management domain. The intention perception module translates a user demand into a network arrangement management demand; a strategy generation module in the centralized management domain determines a target distributed management domain according to the network arrangement management requirement and the distributed resource knowledge map summary, and sends the network arrangement management requirement to the strategy generation module of the target distributed management domain; and a strategy generation module generates a scheduling strategy corresponding to the user demand according to the network orchestration management demand and the distributed resource knowledge map, and notifies a corresponding MANO / VIM to complete the orchestration management of the network so as to realize the orchestration management of the large-scale network.

Description

Technical Field

[0001] This application relates to the field of communication technologies, and in particular, to a method and system for network orchestration and management. Background Art

[0002] The orchestration and management of a network can be regarded as a problem of mapping multiple virtualized network functions (VNFs) to appropriate physical resources and forming a service chain as needed. However, the integrated space-air-ground network for the 6th generation mobile networks (6G) is a super-large-scale three-dimensional network that integrates space, air, and ground infrastructure. Its network scale and resource diversity have increased unprecedentedly, and it has the characteristics of network heterogeneity, highly dynamic spatial nodes, and time-varying topological structure. Currently, the orchestration and management methods for terrestrial networks are no longer applicable.

[0003] Therefore, there is an urgent need to provide an orchestration and management solution for the integrated space-air-ground network. Summary of the Invention

[0004] Embodiments of this application provide a method and system for network orchestration and management to achieve the orchestration and management of large-scale networks.

[0005] In a first aspect, embodiments of this application provide a network orchestration and management system. Resource nodes in the network are divided into at least one distributed management domain. A resource management module and a policy generation module are set in the distributed management domain. One of the at least one distributed management domains is a centralized management domain, and an intent awareness module is also set in the centralized management domain;

[0006] The resource management module in the distributed management domain is used to generate a distributed resource knowledge map corresponding to the distributed management domain. The distributed resource knowledge map includes the attributes of resource nodes and the connection relationships between resource nodes. The resource management module in the centralized management domain is used to converge and process the obtained distributed resource knowledge maps to generate a global resource knowledge map and a summary of the distributed resource knowledge maps. The intent awareness module is used to receive user requirements and translate the user requirements into network orchestration and management requirements. The policy generation module in the centralized management domain is used to determine a target distributed management domain according to the network orchestration and management requirements and the summary of the distributed resource knowledge maps, and send the network orchestration and management requirements to the policy generation module of the target distributed management domain. The policy generation module of the target distributed management domain is used to generate a scheduling policy corresponding to the user requirements according to the network orchestration and management requirements and the distributed resource knowledge map. The scheduling policy includes the mapping relationship between virtual network functions and resource nodes, and virtual connection relationships; and notify the corresponding MANO / VIM to complete the orchestration and management of the network.

[0007] In a possible implementation, the policy generation module in the centralized management domain is further configured to: when the target distributed management domain cannot be determined based on the network orchestration management requirements and the summary of the distributed resource knowledge map, generate a scheduling policy according to the network orchestration management requirements and the global resource knowledge map, and notify the corresponding MANO / VIM to complete the network orchestration management.

[0008] In a possible implementation, at least one distributed management domain is divided according to at least one of the following: the scale of resource nodes, the type of resource nodes, the connection relationship of resource nodes, the service area of resource nodes, and the movement trajectory of resource nodes.

[0009] In a possible implementation, the attributes of resource nodes include node information, resource information, and the corresponding MANO / VIM identifier, where the node information includes at least one of node name, node service area, node type, node status, and remaining service time of the node; the resource information includes at least one of resource type, resource form, resource status, and service status; and / or, the connection relationship between resource nodes includes at least one of connection status, maximum path bandwidth, available path bandwidth, and path delay.

[0010] In a possible implementation, it further includes at least one of the following: the attributes of resource nodes are directly reported by the resource nodes; the attributes of resource nodes are reported by the MANO / VIM agent; the node service area and the remaining service time of the node are obtained according to ephemeris information and / or network operation and maintenance information; the ephemeris information, network operation and maintenance information, and the connection relationship between resource nodes are obtained from the operation control center or a third-party network element.

[0011] In a possible implementation, the centralized management domain is determined according to the multi-dimensional capabilities of the management domain, and the multi-dimensional capabilities include at least one of the storage capacity of the management domain, the computing capacity of the management domain, the security of the management domain, and the operability and maintainability of the management domain.

[0012] In a possible implementation, for any distributed management domain, the resource management module set therein is deployed on the target resource nodes included in the distributed management domain, and the target resource nodes are determined according to at least one factor such as the available memory, available hard disk, processor computing power, and the connection relationship between the resource nodes corresponding to the resource nodes.

[0013] In a possible implementation, the resource management module in the centralized management domain actively obtains the distributed resource knowledge map from the resource management module in the distributed management domain, or the resource management module in the distributed management domain actively reports the distributed resource knowledge map to the resource management module in the centralized management domain.

[0014] In a second aspect, an embodiment of the present application provides a method for network orchestration and management. Resource nodes in the network are divided into at least one distributed management domain. A resource management module and a policy generation module are provided in the distributed management domain. One of the at least one distributed management domains is a centralized management domain, and an intent awareness module is also provided in the centralized management domain. Among them, the resource management module in the distributed management domain is used to generate a distributed resource knowledge map corresponding to the distributed management domain. The distributed resource knowledge map includes the attributes of resource nodes and the connection relationships between resource nodes; the resource management module in the centralized management domain is used to converge and process the obtained distributed resource knowledge maps to generate a global resource knowledge map and a summary of the distributed resource knowledge maps.

[0015] The method for network orchestration and management includes: The intent awareness module receives user requirements and translates the user requirements into network orchestration and management requirements; the policy generation module in the centralized management domain determines a target distributed management domain according to the network orchestration and management requirements and the summary of the distributed resource knowledge maps, and sends the network orchestration and management requirements to the policy generation module of the target distributed management domain; the policy generation module of the target distributed management domain generates a scheduling policy corresponding to the user requirements according to the network orchestration and management requirements and the distributed resource knowledge map. The scheduling policy includes the mapping relationship between virtual network functions and resource nodes, and virtual connection relationships; notify the corresponding Network Function Virtualization Management and Orchestration (MANO) / Virtual Infrastructure Manager (VIM) to complete the network orchestration and management.

[0016] In a possible implementation, the method for network orchestration and management further includes: when the policy generation module in the centralized management domain cannot determine the target distributed management domain according to the network orchestration and management requirements and the summary of the distributed resource knowledge maps, generate a scheduling policy according to the network orchestration and management requirements and the global resource knowledge map, and notify the corresponding MANO / VIM to complete the network orchestration and management.

[0017] In a third aspect, an embodiment of the present application provides a computer-readable storage medium. Computer-executable instructions are stored in the computer-readable storage medium. When the computer-executable instructions are executed, the method for network orchestration and management provided in the second aspect is implemented.

[0018] In a fourth aspect, an embodiment of the present application provides a program product. The program product includes computer-executable instructions. When the computer-executable instructions are executed, the method for network orchestration and management provided in the second aspect is implemented.

[0019] The network orchestration management method and system provided by this application divide the resource nodes in the network into at least one distributed management domain equipped with a resource management module and a policy generation module. One of the at least one distributed management domains is a centralized management domain, and an intent awareness module is also set in the centralized management domain. Among them, the resource management module in the distributed management domain is used to generate a distributed resource knowledge map corresponding to the distributed management domain, which includes the attributes of resource nodes and the connection relationships between resource nodes. The resource management module in the centralized management domain is used to converge and process the obtained distributed resource knowledge maps to generate a global resource knowledge map and a summary of the distributed resource knowledge map; the intent awareness module is used to receive user requirements and translate the user requirements into network orchestration management requirements; the policy generation module in the centralized management domain is used to determine the target distributed management domain according to the network orchestration management requirements and the summary of the distributed resource knowledge map, and send the network orchestration management requirements to the policy generation module of the target distributed management domain; the policy generation module of the target distributed management domain is used to generate a scheduling policy corresponding to the user requirements, which includes the mapping relationship between virtual network functions and resource nodes and virtual connection relationships, according to the network orchestration management requirements and the distributed resource knowledge map, and notify the corresponding MANO / VIM to complete the network orchestration management. This application realizes the orchestration management of large-scale networks based on the real-time perceived distributed resource knowledge map, which can not only reduce the computational complexity of network orchestration management, but also improve the accuracy of the mapping between virtual network functions and physical resources. Description of the Drawings

[0020] The drawings here are incorporated into the specification and form a part of this specification, showing embodiments consistent with this application, and are used together with the specification to explain the principles of this application.

[0021] Figure 1 It is an architecture diagram of Management and Orchestration (MANO) for network function virtualization;

[0022] Figure 2 It is an architecture diagram of the network orchestration management system provided by an embodiment of this application;

[0023] Figure 3 It is an architecture diagram of a distributed and centralized hybrid orchestration management system provided by an embodiment of this application;

[0024] Figure 4 It is a flowchart of global resource knowledge map generation provided by an embodiment of this application;

[0025] Figure 5 It is a schematic diagram of the division of the sparse satellite constellation distributed management domain provided by an embodiment of this application;

[0026] Figure 6Schematic diagram of a resource node dynamically joining a distributed management domain provided by an embodiment of the present application;

[0027] Figure 7 Flowchart of a resource node dynamically joining / leaving a distributed management domain provided by an embodiment of the present application;

[0028] Figure 8 Flowchart of a resource node reporting the attributes of the resource node provided by an embodiment of the present application;

[0029] Figure 9 Flowchart of the attributes of a resource node being reported by a MANO / VIM agent provided by an embodiment of the present application;

[0030] Figure 10 Flowchart of a network orchestration management method provided by an embodiment of the present application;

[0031] Figure 11 Flowchart of distributed network orchestration management provided by an embodiment of the present application;

[0032] Figure 12 Flowchart of centralized network orchestration management provided by an embodiment of the present application.

[0033] Through the above-mentioned drawings, specific embodiments of the present application have been shown, and there will be more detailed descriptions hereinafter. These drawings and textual descriptions are not intended to limit the scope of the concept of the present application in any way, but to illustrate the concept of the present application to those skilled in the art by referring to specific embodiments. Detailed Description of the Embodiment

[0034] Here, exemplary embodiments will be described in detail, and examples are shown in the drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. On the contrary, they are merely examples of devices and methods consistent with some aspects of the present application as detailed in the appended claims.

[0035] In the related art, Network Function Virtualization Management and Orchestration (NFV Management and Orchestration, abbreviated as MANO) is an architecture framework for managing and coordinating Virtualized Network Functions (VNFs), and the Network Function Virtualization Orchestrator (NFVO) is a functional module of MANO. The following will be combined with Figure 1 to describe the architecture of MANO in detail.

[0036] Figure 1 This is an architecture diagram of the network function virtualization management and orchestration (MANO) provided by an embodiment of the present application. As Figure 1 shown, the MANO standard defined by the European Telecommunications Standards Institute (ETSI) includes a Network Function Virtualized Orchestrator (NFVO), VNF Managers (VNFM), and Virtualised Infrastructure Managers (VIM). Among them, the NFVO is used for service orchestration and resource orchestration, and realizes the lifecycle management of network services (NS) through the management and orchestration of NFV infrastructure resources. The VNFM is used to manage the lifecycle of VNFs. One or more VNFs are connected through a virtual network to provide network services. The VIM is used to control and manage the NFV infrastructure, including computing, storage, and network resources.

[0037] Specifically, the NFVO manages and orchestrates network services based on the infrastructure resource usage situation collected by the VIM, and realizes the lifecycle management of VNFs.

[0038] Based on the problems existing in the related technologies, the present application adopts a distributed and centralized hybrid orchestration management architecture. Based on the real-time perception of the distributed resource knowledge map, it can reduce the computational complexity of network orchestration management in large-scale networks such as space-air-ground integrated networks, and improve the accuracy of virtual network function and physical resource mapping.

[0039] The following provides a detailed description of the network orchestration management method and system provided by the embodiments of the present application.

[0040] Figure 2 This is an architecture diagram of the network orchestration management system provided by an embodiment of the present application. As Figure 2 shown, the network orchestration management system 20 includes a distributed management domain 21 and a centralized management domain 22. Among them, a resource management module 210, a policy generation module 211, a regional infrastructure, and a regional MANO / VIM are provided in the distributed management domain 21, and a resource management module 220, a policy generation module 221, an intent perception module 222, a regional infrastructure, and a regional MANO / VIM are provided in the centralized management domain 22.

[0041] Specifically, the resource management module 210 in the distributed management domain 21 is used to generate a distributed resource knowledge map corresponding to the distributed management domain 21. The distributed resource knowledge map includes the attributes of resource nodes and the connection relationships between resource nodes. The resource management module 220 in the centralized management domain 22 is used to converge and process the obtained distributed resource knowledge maps to generate a global resource knowledge map and a summary of the distributed resource knowledge maps. The intent perception module 222 is used to receive user requirements and translate the user requirements into network orchestration management requirements. The policy generation module 221 in the centralized management domain 22 is used to determine the target distributed management domain according to the network orchestration management requirements and the summary of the distributed resource knowledge maps, and send the network orchestration management requirements to the policy generation module 211 of the target distributed management domain. The policy generation module 211 of the target distributed management domain is used to generate a scheduling policy corresponding to the user requirements according to the network orchestration management requirements and the distributed resource knowledge map. The scheduling policy includes the mapping relationship between virtual network functions and resource nodes, and virtual connection relationships, and notifies the corresponding MANO / VIM to complete the network orchestration management.

[0042] Optionally, the network orchestration management system provided in the embodiments of the present application can be applied to an air-space-ground integrated network to implement the orchestration management of the air-space-ground integrated network.

[0043] Figure 3 This is an architecture diagram of a distributed and centralized hybrid orchestration management system provided in the embodiments of the present application. As Figure 3 shown, the distributed and centralized hybrid orchestration management system includes a distributed management domain A, a distributed management domain B, and a distributed management domain C, and the distributed management domain C is a centralized management domain. Among them, the corresponding resource nodes in the distributed management domain A and the distributed management domain B can be the management domains corresponding to the resource nodes of the satellite network, and the distributed management domain C can be the management domain corresponding to the resource nodes of the ground network. Specifically, the functional modules provided in the distributed management domain or the centralized management domain, and the functions of each functional module are similar to those described above, and will not be elaborated here.

[0044] It can be understood that when there are both management domains corresponding to the resource nodes of the satellite network and management domains corresponding to the resource nodes of the ground network at the same time, since the resource nodes of the ground network are relatively stable and have strong storage capacity, computing capacity, security, operability, and maintainability, the management domain corresponding to the resource nodes of the ground network can be determined as the centralized management domain.

[0045] Optionally, the policy generation module 221 can also be used to: when the target distributed management domain cannot be determined according to the network orchestration management requirements and the summary of the distributed resource knowledge maps, generate a scheduling policy according to the network orchestration management requirements and the global resource knowledge map, and notify the corresponding MANO / VIM to complete the network orchestration management.

[0046] Optionally, the resource management module 220 in the centralized management domain 22 actively obtains the distributed resource knowledge map from the resource management module 210 in the distributed management domain 21, or the resource management module 210 in the distributed management domain actively reports the distributed resource knowledge map to the resource management module 220 in the centralized management domain 22.

[0047] Figure 4 This is a flowchart for generating the global resource knowledge map provided by the embodiments of the present application. As Figure 4 shown, the generation of the global resource knowledge map specifically includes the following steps:

[0048] Reporting of the distributed resource knowledge map; generating a summary of the distributed resource knowledge map and updating the global resource knowledge map.

[0049] Among them, the reporting of the distributed resource knowledge map can be actively obtained by the resource management module in the centralized management domain, or actively reported by the resource management module in the distributed management domain. Specifically, the dashed box 41 indicates that the resource management module in the centralized management domain actively obtains from the resource management module in the distributed management domain, and the dashed box 42 indicates that the resource management module in the distributed management domain actively reports to the resource management module.

[0050] Exemplarily, the reporting of the distributed resource knowledge map can be periodic reporting.

[0051] The network orchestration management system provided by the embodiments of the present application realizes the orchestration management of large-scale networks based on the real-time perceived distributed resource knowledge map, which can not only reduce the computational complexity of network orchestration management, but also improve the accuracy of virtual network function and physical resource mapping.

[0052] Optionally, at least one distributed management domain is divided according to at least one of the following: resource node scale, resource node type, resource node connection relationship, resource node service area, and resource node movement trajectory. Exemplarily, the resource node type can be a ground node, a satellite node, etc.

[0053] Optionally, for any distributed management domain, the resource management module set therein is deployed on the target resource node included in the distributed management domain, and the target resource node is determined according to at least one factor among the available memory, available hard disk, processor computing power, and connection relationship between the resource node and other resource nodes corresponding to the resource node.

[0054] For a sparse satellite constellation with a limited number of satellites, where the number of satellite nodes with computing capabilities available for network orchestration is even more limited, it may be considered to partition the resource nodes within the entire constellation into a distributed management domain. By comprehensively evaluating multiple factors such as the available memory, available hard disk, processor computing power of the resource nodes, and the single-hop or multi-hop connection relationships between the resource nodes and other resource nodes, the target resource node is determined. Figure 5 This is a schematic diagram of the distributed management domain partitioning for the sparse satellite constellation provided in the embodiments of this application. As Figure 5 shown, this high-orbit sparse satellite constellation includes four satellite nodes, namely A, B, C, and D, and there are inter-satellite links connecting each pair of satellite nodes; among them, satellites A, B, and C have computing capabilities, and satellite nodes A, B, and C are partitioned into the same distributed management domain. Among them, the resource information corresponding to the satellite nodes can be expressed as [Central Processing Unit (CPU) main frequency, available memory, available hard disk], and this resource information is used to determine the target resource node for setting the resource management module in this distributed management domain. Specifically, as Figure 5 shown, when the CPU main frequency weight is high, the resource management module is selected to be set on satellite node C; when the available memory weight is high, the resource management module is selected to be set on satellite node B.

[0055] In another possible implementation, for a large satellite constellation with a large number of resource nodes distributed on different orbital planes, the distributed management domain can be partitioned by orbital plane. The resource nodes on the same orbital plane are partitioned into the same distributed management domain, and for the resource nodes on the same orbital plane, their movement trajectories and connection relationships are relatively stable. By comprehensively evaluating multiple factors such as the available memory, available hard disk, processor computing power of the resource nodes, and the single-hop or multi-hop connection relationships between the resource nodes and other resource nodes, the target resource node is determined, and the resource management module in the corresponding distributed management domain is set on this target node. Specifically, the setting method of the resource management module is similar to the above and will not be elaborated here; the distributed management domain can also be partitioned according to the resource node type, resource node service area, and resource node movement trajectory, etc.

[0056] Exemplarily, one geostationary orbit (GEO) satellite node and several low earth orbit (LEO) satellite nodes are divided into a distributed management domain. When determining the target resource nodes, i.e., satellite nodes, in this distributed management domain, since GEO is stationary relative to the earth and usually the computing power of GEO satellite nodes is higher than that of LEO, a resource management module is deployed on the GEO satellite node. LEO satellite nodes whose service areas overlap with the service area of this GEO satellite node can dynamically join this distributed management domain. Figure 6 It is a schematic diagram of the dynamic joining of resource nodes into a distributed management domain provided by an embodiment of this application. As Figure 6 shown, the service area TA1 + TA2 of the high-orbit satellite GA is a distributed management domain, and the service area TA3 of the high-orbit satellite GB is another distributed management domain. Low-orbit satellite nodes whose current service areas on the LEO orbital planes L1 and L2 overlap with TA1 and / or TA2 dynamically join this distributed management domain. As Figure 6 shown, the satellite nodes A1, B1, and C1 on the orbital plane L1 and the satellite nodes A2, B2, and C2 on the orbital plane L2 can dynamically join this distributed management domain. When the low-orbit satellite moves and its service area no longer overlaps with TA1 or TA2, the low-orbit satellite node leaves this distributed management domain.

[0057] Next, in combination with Figure 7 the implementation method of the dynamic joining / leaving of resource nodes in a distributed management domain will be described in detail.

[0058] Figure 7 It is a flowchart of the dynamic joining / leaving of resource nodes in a distributed management domain provided by an embodiment of this application. As Figure 7 shown, the dynamic joining / leaving of resource nodes in a distributed management domain may specifically include the following steps:

[0059] 1. After the distributed management domains A and B are divided, and resource management modules A and B are respectively set in the distributed management domains A and B. Among them, the service area of the distributed management domain A is TA1 to TA3, and the service area of the distributed management domain B is TA4 to TA6.

[0060] 2. The resource management modules A and B respectively obtain ephemeris information, network operation and maintenance information, and inter-satellite link connection relationships from the ground operation and control center or a third-party network element. Specifically, the connection relationship includes connection status, path maximum bandwidth, path available bandwidth, path delay, etc.

[0061] 3. The ground operation and control center or a third-party network element configures the mapping relationship between the service area TA and the resource management module identifier for the resource node according to the ephemeris information and / or network operation and maintenance information. All mapping relationships can be configured. Exemplarily, service area TAs 1 to 3 correspond to resource management module A, and service area TAs 4 to 6 correspond to resource management module B; or only the mapping relationship between the current service area TA and the resource management module identifier can be configured. When the TA changes, step 5 is executed, that is, the ground operation and control center or a third-party network element updates the mapping relationship between the service area TA and the resource management module identifier for the resource node according to the ephemeris information and / or network operation and maintenance information.

[0062] 4. Exemplarily, when the resource node is about to move out of service area TA3 and enter TA4, the time t before the resource node enters service area TA4 can be determined according to the running speed of the satellite. Step 5 is executed, that is, the ground operation and control center or a third-party network element updates the mapping relationship between the TA and the resource management module identifier for the resource node according to the ephemeris information and / or network operation and maintenance information, or step 6 is executed, that is, the resource node notifies resource management module A that the node status is unavailable, or the resource node deregisters from resource management module A. Exemplarily, the time t can be 2 minutes.

[0063] 5. The ground operation and control center or a third-party network element updates the mapping relationship between the TA and the resource management module identifier for the resource node according to the ephemeris information and / or network operation and maintenance information.

[0064] 6. The resource node notifies resource management module A that the node status is unavailable, or the resource node deregisters from resource management module A.

[0065] 7. The resource node registers with resource management module B and joins the distributed resource knowledge map B generated by resource management module B.

[0066] Optionally, the attributes of the resource node include node information, resource information, and the corresponding MANO / VIM identifier. Among them, the node information includes at least one of the node name, node service area, node type, node status, and node remaining service time; the resource information includes at least one of the resource type, resource form, resource status, and resource service status;

[0067] And / or, the connection relationship between resource nodes includes at least one of the connection status, path maximum bandwidth, path available bandwidth, and path delay.

[0068] In a possible implementation manner, the attributes of the resource node are directly reported by the resource node or reported by the MANO / VIM proxy; the node service area and the node remaining service time are obtained according to the ephemeris information and / or network operation and maintenance information; the ephemeris information, network operation and maintenance information, and the connection relationship between resource nodes are obtained from the operation and control center or a third-party network element.

[0069] Specifically, when the resource node is a satellite node, the node service area and the remaining service time of the node can be obtained according to ephemeris information.

[0070] The following combines Figure 8 to elaborate in detail on the implementation method in which the attributes of the resource node are directly reported by the resource node.

[0071] Figure 8 is the flowchart for the resource node to report the attributes of the resource node provided by the embodiment of the present application. As Figure 8 shown, the resource node reporting the attributes of the resource node specifically includes the following steps:

[0072] 1. The distributed management domain division is completed, and the resource management module in the distributed management domain has been deployed.

[0073] 2. The resource management module in the distributed management domain obtains ephemeris information, network operation and maintenance information, and inter-satellite link connection relationships from the ground operation and control center or a third-party network element. The connection relationship includes connection status, path maximum bandwidth, path available bandwidth, path delay, etc.

[0074] 3. Configure a resource management module identifier for the satellite node (i.e., the resource node) with computing capabilities and available for network orchestration. The resource node sends a registration request to the resource management module, and the request message carries node information and the MANO or VIM identifier to which the resource node belongs. Exemplarily, the node information includes node name (such as satellite identifier), node service area, node type, and node status. The node service area can be a geographical area represented by longitude and latitude, or a tracking area TA.

[0075] 4. The resource management module returns a registration response to the resource node and assigns a resource node identifier to the resource node. Exemplarily, the resource node identifier assigned to the resource node can be automatically generated by the resource management module.

[0076] 5. The resource management module generates the resource node information and the connection relationships between resource nodes in the distributed resource knowledge map. Among them, the remaining service duration of the resource node and the connection relationships between resource nodes can be derived according to the ephemeris information and / or network operation and maintenance information obtained in step 2.

[0077] Optionally, the reporting of resource node attribute information can be periodic perception or event-triggered perception.

[0078] Specifically, steps 6-7 are the periodic perception process

[0079] 6. The resource management module sends a perception task to the resource node, including a perception period and a perception template.

[0080] 7. Resource nodes report node information and resource information periodically. Among them, only the changed parts of the node information can be reported. For example, due to the movement of LEO satellites, the service area of the node changes; due to planned operation and maintenance factors, the resource node is temporarily unavailable. Resource information includes resource type, resource form, resource status, resource service status, etc.

[0081] Steps 8 - 9 are the event-triggered perception process

[0082] 8. The resource management module sends an event perception trigger to the resource node.

[0083] 9. The resource node monitors whether it meets the event reporting conditions. When the reporting conditions are met, it reports the node information and resource information to the resource management module.

[0084] 10. The resource management module obtains ephemeris information, network operation and maintenance information, and inter-satellite link connection relationships from the ground operation and control center or a third-party network element. Specifically, this acquisition step can be triggered by Step 7 or Step 9, or can be acquired periodically.

[0085] 11. The resource management module updates the resource node information and the connection relationships between resource nodes in the distributed resource knowledge map according to the information reported in Step 7 or Step 9, and the information obtained in Step 10.

[0086] The following combines Figure 9 to elaborate in detail on the implementation method of reporting the attributes of resource nodes by the MANO / VIM agent.

[0087] Figure 9 This is the flowchart of reporting the attributes of resource nodes by the MANO / VIM agent provided in the embodiments of this application. As Figure 9 shown, the specific steps of reporting the attributes of resource nodes by the MANO / VIM agent include the following:

[0088] 1. MANO / VIM has formed a stable management relationship with the resource nodes. VIM can be a container management tool such as Kubernetes, or a virtual machine management tool such as Openstack. MANO / VIM manages the node information and resource information of each resource node. Among them, the node information includes node name, node service area, node type, and node status; the resource information includes resource type, resource form, resource status, resource service status, etc.

[0089] 2. The distributed management domain division is completed, and the resource management module in the distributed management domain has been deployed.

[0090] 3. The resource management module in the distributed management domain obtains ephemeris information, network operation and maintenance information, and inter-satellite link connection relationships from the ground operation and control center or a third-party network element. The connection relationships include connection status, maximum path bandwidth, available path bandwidth, path delay, etc.

[0091] 4. Configure the resource management module identifier for MANO / VIM. MANO / VIM sends a registration request to the resource management module. The request message carries the MANO / VIM identifier and a list of resource nodes, and reports the node information of each resource node.

[0092] 5. The resource management module returns a registration response and assigns resource node identifiers to all resource nodes in the resource node list. Exemplarily, the resource node identifiers assigned to the resource nodes can be automatically generated by the resource management module.

[0093] 6. The resource management module generates resource node information, the correspondence between nodes and MANO / VIM, and the connection relationships between resource nodes in the distributed resource knowledge map. Among them, the remaining service duration of the resource nodes and the connection relationships between resource nodes can be derived based on the ephemeris information and / or network operation and maintenance information obtained in step 2.

[0094] Optionally, the reporting of resource node attribute information can be periodic perception or event-triggered perception.

[0095] Specifically, steps 7-8 are the periodic perception process

[0096] 7. The resource management module issues a perception task to MANO / VIM, including the resource node identifier to be perceived, the perception period, and the perception template.

[0097] 8. MANO / VIM reports node information and resource information periodically. Among them, only the changed part of the node information can be reported.

[0098] Steps 9-10 are the event-triggered perception process

[0099] 9. The resource management module issues an event perception trigger and the resource node identifier to be perceived to MANO / VIM.

[0100] 10. MANO / VIM monitors whether the resource node meets the event reporting conditions. When the reporting conditions are met, it reports the node information and resource information to the resource management module.

[0101] 11. The resource management module obtains ephemeris information, network operation and maintenance information, and inter-satellite link connection relationships from the ground operation and control center or a third-party network element. Specifically, this obtaining step can be triggered by step 7 or step 9, or can be obtained periodically.

[0102] 12. The resource management center updates the resource node information and the connection relationships between resource nodes in the knowledge map according to the information reported in step 7 or step 9 and the information obtained in step 10.

[0103] Optionally, the centralized management domain is determined according to the multi-dimensional capabilities of the management domain, and the multi-dimensional capabilities include at least one of the management domain storage capability, the management domain computing capability, the management domain security, and the management domain operability and maintainability.

[0104] Exemplarily, the centralized management domain can be determined according to the weights of the management domain storage capability, the management domain computing capability, the management domain security, and the management domain operability and maintainability. Specifically, when the weight of the management domain storage capability is high, the distributed management domain with the highest management domain storage capability is selected as the centralized management domain; when the weight of the management domain computing capability is high, the distributed management domain with the highest management domain computing capability is selected as the centralized management domain, etc.

[0105] Based on the above network orchestration management system, the network orchestration management method provided in the embodiments of the present application will be described in detail below in conjunction with Figure 10 This application embodiment provides a flowchart of a network orchestration management method. As

[0106] Figure 10 As shown, the network orchestration management method includes the following steps: Figure 10 As shown, the network orchestration management method includes the following steps:

[0107] S111. The intent perception module receives the user requirements and translates the user requirements into network orchestration management requirements.

[0108] S112. The policy generation module in the centralized management domain determines the target distributed management domain according to the network orchestration management requirements and the distributed resource knowledge map summary, and sends the network orchestration management requirements to the policy generation module of the target distributed management domain.

[0109] Optionally, the distributed resource knowledge map summary is obtained by the resource management module in the centralized management domain through aggregation processing of the obtained distributed resource knowledge maps. Exemplarily, it can be obtained by de-duplicating and fusing at least one distributed resource knowledge map.

[0110] S113. The policy generation module of the target distributed management domain generates a scheduling policy corresponding to the user requirements according to the network orchestration management requirements and the distributed resource knowledge map. The scheduling policy includes the mapping relationship between virtual network functions and resource nodes, and the virtual connection relationship; and notifies the corresponding network function virtualization management and orchestration MANO / virtual infrastructure manager VIM to complete the network orchestration management.

[0111] It should be noted that the network orchestration and management method provided in the embodiments of the present application can be applied to the space-air-ground integrated network to achieve the orchestration and management of the space-air-ground integrated network.

[0112] In the embodiments of the present application, based on the real-time perception-based distributed resource knowledge map, the orchestration and management of large-scale networks are realized, which can not only reduce the computational complexity of network orchestration and management, but also improve the accuracy of virtual network function and physical resource mapping.

[0113] Optionally, when the policy generation module in the centralized management domain cannot determine the target distributed management domain according to the network orchestration and management requirements and the summary of the distributed resource knowledge map, it generates a scheduling policy according to the network orchestration and management requirements and the global resource knowledge map, and notifies the corresponding MANO / VIM to complete the network orchestration and management.

[0114] The following details the distributed network orchestration and centralized network orchestration provided in the embodiments of the present application.

[0115] Figure 11 This is a flowchart of the distributed network orchestration and management provided in the embodiments of the present application. As Figure 11 shown, the distributed network orchestration specifically includes the following steps:

[0116] 1. The intent perception module receives the user's requirements, that is, the user's deployment intent.

[0117] 2. The intent perception module translates the user's deployment intent into network deployment requirements based on historical experience or artificial intelligence (AI) analysis.

[0118] 3. The intent perception module sends the network instance deployment requirements to the policy generation module in the centralized management domain. The requirements include the description of the network service (NSD), and the network service description includes the description of the virtualized network element (VNFD). The VNFD includes the network requirements and resource requirements of the VNF instance.

[0119] 4. The policy generation module in the centralized management domain obtains the summary of the distributed resource knowledge map from the resource management module in the centralized management domain.

[0120] 5. The policy generation module in the centralized management domain determines the target distributed management domain according to the network deployment requirements. Exemplarily, the target distributed management domain can be determined according to the resource information of the resource node. Specifically, for example, if VNF_A (running an edge business server) requires GPU computing power, and VNF_B and VNF_C (core network elements) can use general CPU computing power, according to the summary of the distributed resource knowledge map, it is determined that VNF_A is deployed in the target distributed management domain A, and VNF_B and VNF_C are deployed in the target distributed management domain B.

[0121] 6a - 6b. The policy generation modules in the centralized management domain respectively request the policy generation modules A and B in the distributed management domain to instantiate network services. Among them, network service A includes VNF_A, and network service B includes VNF_B and VNF_C.

[0122] 7. After the policy generation module in the centralized management domain receives the responses indicating the successful instantiation of all distributed network services, it returns a network deployment success response to the intent awareness module.

[0123] Figure 12 This is the flowchart of the centralized network orchestration and management provided by the embodiments of this application. As Figure 12 shown, the centralized network orchestration and management specifically includes the following steps:

[0124] 1. The intent awareness module receives the user requirements, that is, the user deployment intent.

[0125] 2. The intent awareness module translates the user deployment intent into network deployment requirements based on historical experience or artificial intelligence (AI) analysis.

[0126] 3. The intent awareness module sends the network deployment requirements to the policy generation module in the centralized management domain. The requirements include the description of the network service (NSD), and the network service description includes the description of the virtualized network element (VNFD). The VNFD includes the network requirements and resource requirements of the VNF instance.

[0127] 4. The policy generation module in the centralized management domain obtains the global resource knowledge map from the resource management module in the centralized management domain.

[0128] 5. The policy generation module in the centralized management domain determines the target resource nodes and their corresponding MANO / VIM according to the network deployment requirements.

[0129] 6a - 6b. The policy generation modules in the centralized management domain respectively request MANO / VIM_A and MANO / VIM_B to instantiate network services.

[0130] 7. After the policy generation module in the centralized management domain receives the responses indicating the successful instantiation of all MANO / VIM services, it returns a network deployment success response to the centralized intent awareness module.

[0131] It should be noted that the centralized network orchestration process is applicable to scenarios where the scale of network resources is controllable. For example, the space-air-ground integrated network is divided into one management domain.

[0132] The embodiments of the present application further provide a computer-readable storage medium, in which computer-executable instructions are stored. When the computer-executable instructions are executed, they are used to implement the method steps in the above method embodiments. The specific implementation manners and technical effects are similar and will not be elaborated here.

[0133] The embodiments of the present application further provide a program product, which includes computer-executable instructions. When the computer-executable instructions are executed, they are used to implement the method steps in the above method embodiments. The specific implementation manners and technical effects are similar and will not be elaborated here.

[0134] Those skilled in the art will readily conceive of other embodiments of the invention after considering the specification and practicing the invention disclosed herein. The present application is intended to cover any variations, uses, or adaptations of the present application, which follow the general principles of the present application and include known common general knowledge or conventional technical means in the technical field not disclosed in the present application. The specification and embodiments are only regarded as exemplary, and the true scope and spirit of the present application are pointed out by the following claims.

[0135] It should be understood that the present application is not limited to the exact structures described above and shown in the drawings, and various modifications and changes can be made without departing from its scope. The scope of the present application is only limited by the appended claims.

[0136] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, displayed data, etc.) involved in the present application are all information and data authorized by the user or fully authorized by all parties. The collection, use, and processing of the relevant data need to comply with the relevant laws, regulations, and standards of the relevant countries and regions, and corresponding operation entrances are provided for the user to choose to authorize or reject.

Claims

1. An orchestration management system for a network, characterized in that, resource nodes in the network are divided into at least one distributed management domain, a resource management module and a policy generation module are arranged in the distributed management domain, one of the at least one distributed management domain is a centralized management domain, and an intent awareness module is also arranged in the centralized management domain; the resource management module in the distributed management domain is used to generate a distributed resource knowledge map corresponding to the distributed management domain, and the distributed resource knowledge map includes the attributes of resource nodes and the connection relationships between resource nodes; the resource management module in the centralized management domain is used to converge and process the obtained distributed resource knowledge maps to generate a global resource knowledge map and a summary of the distributed resource knowledge maps; the intent awareness module is used to receive user requirements and translate the user requirements into network orchestration management requirements; the policy generation module in the centralized management domain is used to determine a target distributed management domain according to the network orchestration management requirements and the summary of the distributed resource knowledge maps, and send the network orchestration management requirements to the policy generation module of the target distributed management domain; the policy generation module of the target distributed management domain is used to generate a scheduling policy corresponding to the user requirements according to the network orchestration management requirements and the distributed resource knowledge map, and the scheduling policy includes the mapping relationship between virtual network functions and resource nodes and virtual connection relationships; notify the corresponding Network Function Virtualization Management and Orchestration (MANO) / Virtual Infrastructure Manager (VIM) to complete the orchestration management of the network.

2. The network orchestration management system according to claim 1, characterized in that, the policy generation module in the centralized management domain is further used for: when the target distributed management domain cannot be determined according to the network orchestration management requirements and the summary of the distributed resource knowledge maps, generating a scheduling policy according to the network orchestration management requirements and the global resource knowledge map, and notifying the corresponding MANO / VIM to complete the orchestration management of the network.

3. The network orchestration management system according to claim 1 or 2, characterized in that, the at least one distributed management domain is divided according to at least one of the following: resource node scale, resource node type, resource node connection relationship, resource node service area, and resource node movement trajectory.

4. The network orchestration management system according to claim 1 or 2, characterized in that, the attributes of the resource nodes include node information, resource information, and corresponding MANO / VIM identifiers, wherein the node information includes at least one of node name, node service area, node type, node status, and remaining node service time; the resource information includes at least one of resource type, resource form, resource status, and resource service status; and / or, the connection relationship between resource nodes includes at least one of connection status, maximum path bandwidth, available path bandwidth, and path delay.

5. The network orchestration management system according to claim 4, characterized in that, further includes at least one of the following: The attributes of the resource node are directly reported by the resource node; The attributes of the resource node are reported by the MANO / VIM agent; The node service area and the remaining service time of the node are obtained according to ephemeris information and / or network operation and maintenance information; The ephemeris information, the network operation and maintenance information, and the connection relationship between the resource nodes are obtained from the operation control center or a third-party network element.

6. The network orchestration and management system according to claim 1 or 2, characterized in that, The centralized management domain is determined according to the multi-dimensional capabilities of the management domain, and the multi-dimensional capabilities include at least one of the management domain storage capacity, the management domain computing capacity, the management domain security, and the management domain operability and maintainability.

7. The network orchestration and management system according to claim 1 or 2, characterized in that, For any one of the distributed management domains, the resource management module set therein is deployed on the target resource node included in the distributed management domain, and the target resource node is determined according to at least one factor among the available memory, the available hard disk, the processor computing power, and the connection relationship between the resource node and other resource nodes corresponding to the resource node.

8. The network orchestration and management system according to claim 1 or 2, characterized in that, The resource management module in the centralized management domain actively obtains the distributed resource knowledge map from the resource management module in the distributed management domain, or the resource management module in the distributed management domain actively reports the distributed resource knowledge map to the resource management module in the centralized management domain.

9. A network orchestration and management method, characterized in that, The resource nodes in the network are divided into at least one distributed management domain, a resource management module and a policy generation module are set in the distributed management domain, one of the at least one distributed management domains is a centralized management domain, and an intention perception module is also set in the centralized management domain. Among them, the resource management module in the distributed management domain is used to generate a distributed resource knowledge map corresponding to the distributed management domain, and the distributed resource knowledge map includes the attributes of the resource node and the connection relationship between the resource nodes; the resource management module in the centralized management domain is used to converge and process the obtained distributed resource knowledge map to generate a global resource knowledge map and a summary of the distributed resource knowledge map; The network orchestration and management method includes: The intention perception module receives the user requirements and translates the user requirements into network orchestration and management requirements; The policy generation module in the centralized management domain determines the target distributed management domain according to the network orchestration and management requirements and the summary of the distributed resource knowledge map, and sends the network orchestration and management requirements to the policy generation module of the target distributed management domain; The policy generation module of the target distributed management domain generates a scheduling policy corresponding to the user requirements according to the network orchestration management requirements and the distributed resource knowledge map. The scheduling policy includes the mapping relationship between virtual network functions and resource nodes, as well as virtual connection relationships; and notifies the corresponding Network Function Virtualization Management and Orchestration (MANO) / Virtual Infrastructure Manager (VIM) to complete the network orchestration management.

10. The network orchestration management method according to claim 9, wherein, it further includes: When the policy generation module in the centralized management domain cannot determine the target distributed management domain according to the network orchestration management requirements and the summary of the distributed resource knowledge map, it generates a scheduling policy according to the network orchestration management requirements and the global resource knowledge map, and notifies the corresponding MANO / VIM to complete the network orchestration management.

Images