Network operation management system, method and apparatus, and related device

By introducing business acceptors and multiple system orchestrators into the network operation management system, and using business grading tables and smart contract templates to optimize message processing, the problems of central orchestration pressure and response delay are solved, and the efficiency of network operation management is improved .

WO2024230034A1PCT designated stage expired Publication Date: 2024-11-14CHINA TELECOM CORP LTD
View PDF 7 Cites 0 Cited by

Patent Information

Application Number
PCT/CN2023/118316
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-05-05
Filing Date
2023-09-12
Publication Date
2024-11-14

AI Technical Summary

Technical Problem

When a large number of users submit business request messages, the central orchestrator bears huge processing pressure, resulting in increased response delay of service request messages and inefficient efficiency.

Method used

Introduce service handlers and multiple system orchestrators, including central orchestrator and domain orchestrator, determine the request message level through the service hierarchy table, and directly send request messages with lower levels to the domain orchestrator to reduce dependence on the central orchestrator. , and optimize message processing through smart contract templates and distributed ledger consensus mechanism.

Benefits of technology

Effectively reduce the processing pressure of the central orchestrator, improve the response speed of service request messages, improve the efficiency of network operation management, and reduce delays.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2023118316_14112024_PF_FP_ABST
    Figure CN2023118316_14112024_PF_FP_ABST
Patent Text Reader

Abstract

Provided in the present disclosure are a network operation management system, method and apparatus, and a related device, relating to the technical field of networks. A method is executed by a service acceptor, comprising: acquiring a service request message, and determining a level of the service request message; according to the level of the service request message, determining a first orchestrator; and sending the service request message to the first orchestrator. Another method is executed by the first orchestrator, comprising: receiving a service request message sent by the service acceptor; converting the service request message into a corresponding orchestration instruction, and sending the orchestration instruction to a controller, the controller being configured to receive the orchestration instruction; converting the orchestration instruction into service configuration information; and sending the service configuration information to a network device. Therefore, the present disclosure does not require all service request messages to pass through a central orchestrator. When a large number of users propose service request messages, the processing pressure of the central orchestrator can be reduced, and the speed of responding to the service request messages can be accelerated, thus improving the efficiency of network operation management.
Need to check novelty before this filing date? Find Prior Art

Description

Network operation management system, method, device and related equipment

[0001] This disclosure is based on the Chinese patent application with application number 202310499161.9, application date May 5, 2023, and invention name “Network Operation Management System, Method, Device, Electronic Equipment and Storage Medium”, and claims the priority of the Chinese patent application. The entire content of the Chinese patent application is hereby introduced into this disclosure as a reference. Technical Field

[0002] The present disclosure relates to the field of network technology, and in particular to a network operation management system, method, apparatus, and related equipment. Background Art

[0003] With the continuous development of network technology, the number of users in the network is also growing. Any service request message sent by a user needs to be sent to the corresponding network device through the network operation and management system.

[0004] In related technologies, after a user sends a service request message, the service request message needs to pass through the central orchestrator, domain orchestrator, and controller in the network operation and management system in sequence, and then be sent to the corresponding network device by the controller.

[0005] Therefore, the methods provided by related technologies can place enormous processing pressure on the central orchestrator when a large number of users submit service request messages. Furthermore, the delays caused by detours can prevent service request messages from being responded to in a timely manner, leading to inefficient network operations and management.

[0006] It should be noted that the information disclosed in the above background technology section is only used to enhance the understanding of the background of the present disclosure, and therefore may include information that does not constitute prior art known to ordinary technicians in the field.

[0007] Summary of the Invention

[0008] The present disclosure provides a network operation management system, method, apparatus, and related equipment, which, at least to a certain extent, overcome the problems in related technologies, such as the huge processing pressure on the central orchestrator, the inability to respond to business request messages in a timely manner, and the low efficiency of network operation management.

[0009] Other features and advantages of the present disclosure will become apparent from the following detailed description, or may be learned in part by practice of the present disclosure.

[0010] According to one aspect of an embodiment of the present disclosure, a network operation and management system is provided, comprising: a service acceptor, a plurality of system orchestrators, a controller, and a network device, wherein the plurality of system orchestrators include at least one of a central orchestrator and a domain orchestrator;

[0011] The service acceptor is used to obtain the service request message and determine the level of the service request message;

[0012] The service acceptor is further configured to determine a first orchestrator from a plurality of system orchestrators according to a level of the service request message, and send the service request message to the first orchestrator, wherein the first orchestrator is a central orchestrator or a domain orchestrator;

[0013] The first orchestrator is configured to convert the service request message into a corresponding orchestration instruction and send the orchestration instruction to the controller;

[0014] The controller is configured to receive the orchestration instruction, convert the orchestration instruction into service configuration information, and send the service configuration information to the network device.

[0015] In some embodiments of the present disclosure, when the first orchestrator is a central orchestrator, the first orchestrator is configured to send the orchestration instruction to a domain orchestrator corresponding to the first orchestrator;

[0016] The domain orchestrator corresponding to the first orchestrator is configured to send the orchestration instruction to the controller.

[0017] In some embodiments of the present disclosure, the first orchestrator is further configured to generate a service data block, the service data block being configured to store the service configuration in the service request message, the service identifier corresponding to the service request message, and the user identifier corresponding to the user sending the service request message;

[0018] The first orchestrator is further configured to send the service data block to each second orchestrator other than the first orchestrator in the plurality of system orchestrators and the controller;

[0019] The second orchestrator is configured to store the received service data blocks;

[0020] The controller is further configured to store the received service data blocks.

[0021] In some embodiments of the present disclosure, each system orchestrator and controller includes a user service data link;

[0022] The second orchestrator is configured to verify the business data block according to the consensus mechanism of the distributed ledger, and when the business data block passes the verification, store the business data block in the user business data chain;

[0023] The controller is used to verify the business data block according to the consensus mechanism of the distributed ledger, and when the business data block passes the verification, store the business data block in the user business data chain.

[0024] In some embodiments of the present disclosure, the service acceptor includes a service rating table, which is used to describe at least one type of service request message and a level corresponding to the type of at least one service request message;

[0025] The service acceptor is used to determine the level of the service request message through the service level table.

[0026] In some embodiments of the present disclosure, the first orchestrator includes a smart contract template;

[0027] The first orchestrator is configured to convert the service request message into a corresponding orchestration instruction by using the smart contract template.

[0028] According to another aspect of the present disclosure, a network operation management method is provided, which is executed by a service acceptor, wherein the service acceptor is connected to a plurality of system orchestrators, respectively, and includes:

[0029] Obtaining a service request message and determining the level of the service request message;

[0030] determining a first orchestrator from a plurality of system orchestrators according to a level of the service request message;

[0031] Sending the service request message to the first orchestrator;

[0032] The first orchestrator is used to convert the service request message into a corresponding orchestration instruction, and send the orchestration instruction to the controller. The controller is used to receive the orchestration instruction, convert the orchestration instruction into service configuration information, and send the service configuration information to the network device.

[0033] According to another aspect of the present disclosure, a network operations management method is provided, which is performed by a first orchestrator, the first orchestrator being a central orchestrator or a domain orchestrator, and connected to a service acceptor. The service acceptor is configured to obtain a service request message, determine a level of the service request message, determine a first orchestrator from a plurality of system orchestrators based on the level of the service request message, and send the service request message to the first orchestrator. The method comprises:

[0034] Receive the service request message sent by the service acceptor;

[0035] The service request message is converted into a corresponding orchestration instruction, and the orchestration instruction is sent to a controller. The controller is used to receive the orchestration instruction, convert the orchestration instruction into service configuration information, and send the service configuration information to the network device.

[0036] According to another aspect of the present disclosure, a network operation management device is provided, which is applied to a service acceptor, wherein the service acceptor is connected to multiple system orchestrators respectively, including:

[0037] A level determination module, configured to obtain a service request message and determine the level of the service request message;

[0038] a first orchestrator determining module, configured to determine a first orchestrator from a plurality of system orchestrators according to a level of the service request message;

[0039] The service request message sending module is used to send the service request message to the first orchestrator, wherein the first orchestrator is used to convert the service request message into a corresponding orchestration instruction and send the orchestration instruction to the controller. The controller is used to receive the orchestration instruction, convert the orchestration instruction into service configuration information, and send the service configuration information to the network device.

[0040] According to another aspect of the present disclosure, a network operations management apparatus is provided, which is applied to a first orchestrator, the first orchestrator being a central orchestrator or a domain orchestrator, and connected to a service acceptor. The service acceptor is configured to obtain a service request message, determine a level of the service request message, determine a first orchestrator from multiple system orchestrators based on the level of the service request message, and send the service request message to the first orchestrator. The apparatus includes:

[0041] A service request message receiving module, configured to receive a service request message sent by the service acceptor;

[0042] The orchestration instruction sending module is used to convert the service request message into a corresponding orchestration instruction and send the orchestration instruction to the controller. The controller is used to receive the orchestration instruction, convert the orchestration instruction into service configuration information, and send the service configuration information to the network device.

[0043] According to another aspect of the present disclosure, an electronic device is provided, comprising: a processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to perform the above-mentioned network operation management method by executing the executable instructions.

[0044] According to another aspect of the present disclosure, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the network operation management method described above is implemented.

[0045] According to another aspect of the present disclosure, a computer program product or computer program is provided, comprising computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the computer device to perform the network operations management method provided in any of the optional embodiments of the present disclosure.

[0046] It is to be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0047] The accompanying drawings are incorporated into and constitute a part of the specification, illustrate embodiments consistent with the present disclosure, and together with the specification, are used to explain the principles of the present disclosure. Obviously, the drawings described below are only some embodiments of the present disclosure, and those skilled in the art can derive other drawings based on these drawings without inventive effort.

[0048] FIG1 is a schematic diagram showing an operation management system architecture in an operator network according to an embodiment of the present disclosure;

[0049] FIG2 is a schematic diagram showing a system architecture of a network operation management system according to an embodiment of the present disclosure;

[0050] FIG3 shows a flow chart of a network operation management method according to an embodiment of the present disclosure;

[0051] FIG4 shows a schematic diagram of a process of network operation management according to an embodiment of the present disclosure;

[0052] FIG5 shows a schematic diagram of a system orchestrator according to an embodiment of the present disclosure;

[0053] FIG6 shows a schematic diagram of a user terminal according to an embodiment of the present disclosure;

[0054] FIG7 shows a schematic diagram of a network operation management device according to an embodiment of the present disclosure;

[0055] FIG8 shows a schematic diagram of another network operation management device according to an embodiment of the present disclosure;

[0056] FIG9 shows a structural block diagram of an electronic device according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0057] Example embodiments will now be described more fully with reference to the accompanying drawings. However, example embodiments can be embodied in many forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete and will fully convey the concepts of the example embodiments to those skilled in the art. The described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[0058] In addition, the accompanying drawings are merely schematic illustrations of the present disclosure and are not necessarily drawn to scale. Identical reference numerals in the figures denote identical or similar parts, and thus repetitive descriptions thereof will be omitted. Some of the block diagrams shown in the accompanying drawings are functional entities that do not necessarily correspond to physically or logically separate entities. These functional entities may be implemented in software, in one or more hardware modules or integrated circuits, or in different networks and / or processor devices and / or microcontroller devices.

[0059] To facilitate understanding, the following first explains the architecture of the operations management system in a carrier network. As shown in Figure 1, the architecture of the operations management system in a carrier network can include a portal, a central orchestrator, a domain orchestrator, a controller, and network devices.

[0060] Among them, the portal is responsible for receiving the user's business request message and sending the business request message to the central orchestrator. The central orchestrator can convert the business request message into an orchestration instruction and send the orchestration instruction to a domain orchestrator corresponding to the central processor. As shown in Figure 1, the domain orchestrators corresponding to the central orchestrator include domain orchestrator A, domain orchestrator B, and domain orchestrator C. Therefore, the central orchestrator can send orchestration instructions to any domain orchestrator among domain orchestrator A, domain orchestrator B, and domain orchestrator C. Taking the central orchestrator sending the orchestration instruction to domain orchestrator A as an example, the domain orchestrator A can send the received orchestration instruction to the controller A it manages, and the controller A converts the orchestration instruction into a configuration command and sends it to the corresponding AS (Autonomous System) 1. Finally, the corresponding AS 1 can send the configuration information to the network device (i.e., the user site shown in Figure 1).

[0061] As shown in the operations management system architecture shown in Figure 1, any service request message sent by a user must be processed by the central orchestrator before being sent down to the corresponding controller level by level. When a large number of users in the network send service request messages, this can place enormous processing pressure on the central orchestrator. Furthermore, the delays caused by this detour can prevent some simpler user service requests from being responded to in a timely manner. Therefore, adjustments to the system architecture shown in Figure 1 are necessary.

[0062] FIG2 shows a schematic diagram of an exemplary system architecture of a network operation and management system that can be applied to an embodiment of the present disclosure.

[0063] As shown in Figure 2, system architecture 100 may include a service acceptor 101, multiple system orchestrators 102, a controller 103, and a network device 104. The multiple system orchestrators 102 include at least one of a central orchestrator and a domain orchestrator.

[0064] The service acceptor 101 can be configured to obtain a service request message and determine the level of the service request message. The service acceptor 101 can also be configured to determine a first orchestrator from among multiple system orchestrators 102 based on the level of the service request message and send the service request message to the first orchestrator, where the first orchestrator can be a central orchestrator or a domain orchestrator. The first orchestrator can convert the service request message into a corresponding orchestration instruction and send the orchestration instruction to the controller 103. The controller 103 can receive the orchestration instruction, convert the orchestration instruction into service configuration information, and send the service configuration information to the network device 104.

[0065] The embodiment of the present disclosure does not limit the type of the service acceptor 101. The service acceptor 101 can be any electronic device with computing and processing capabilities. The type of the service acceptor 101 can be determined according to the application scenario.

[0066] The embodiment of the present disclosure does not limit the type of the network device 104. Optionally, the network device 104 may be a CPE (Customer Premise Equipment) or a gateway.

[0067] For example, a network can be used as a medium for communication links between service acceptor 101 and any system orchestrator 102. Furthermore, a network can also be used as a medium for communication links between any system orchestrator 102 and network device 104. The network can be either a wired network or a wireless network.

[0068] Optionally, the above-mentioned wireless network or wired network uses standard communication technologies and / or protocols. The network is typically the Internet, but can also be any network, including but not limited to a local area network (LAN), a metropolitan area network (MAN), a wide area network (WAN), a mobile, wired or wireless network, a private network or any combination of a virtual private network). In some embodiments, technologies and / or formats including Hypertext Markup Language (HTML), Extensible Markup Language (XML), etc. are used to represent data exchanged over the network. In addition, conventional encryption technologies such as Secure Socket Layer (SSL), Transport Layer Security (TLS), Virtual Private Network (VPN), Internet Protocol Security (IPsec), etc. can be used to encrypt all or some links. In other embodiments, customized and / or dedicated data communication technologies can also be used to replace or supplement the above-mentioned data communication technologies.

[0069] In some exemplary embodiments, the service acceptor 101 may be located inside a user terminal, or the service acceptor 101 may also be a network device that can establish a connection with the user terminal. Therefore, when a user submits a service request message, the service acceptor 101 may obtain the service request message.

[0070] The embodiments of the present disclosure do not limit the above-mentioned user terminal. The user terminal can be various electronic devices, including but not limited to smart phones, tablet computers, laptop computers, desktop computers, wearable devices, augmented reality devices, virtual reality devices, etc.

[0071] In some embodiments, the service acceptor 101 may include a service rating table that describes at least one type of service request message and the level corresponding to the at least one type of service request message. Therefore, the service acceptor 101 may determine the level of the service request message using the service rating table.

[0072] The embodiments of the present disclosure do not limit the types of service request messages. For example, service request messages with the same service characteristics may be determined to be of the same type. The service characteristics may include, for example, those involving construction issues, changes to network infrastructure, or changes to a single network performance parameter.

[0073] In an exemplary embodiment, the service request message related to a construction issue may be, for example, the activation of a new dedicated line. The service request message related to a network infrastructure change may be, for example, a QoS (Quality of Service) change. The service request message related to a change in a single network performance parameter may be, for example, a bandwidth adjustment.

[0074] Illustratively, the service classification table included in the service acceptor 101 may be as shown in Table 1.

[0075] Table 1

[0076] As shown in Table 1, service request messages involving construction issues may be rated as level 1. Service request messages involving network infrastructure changes may be rated as level 2. Service request messages involving a single network performance parameter may be rated as level 3.

[0077] The present embodiment does not limit the method for determining the first orchestrator from multiple system orchestrators 102 based on the level of the service request message. For example, the method for determining the first orchestrator from multiple system orchestrators 102 based on the level of the service request message can be limited based on experience or application scenarios.

[0078] In one possible implementation, using the service level table shown in Table 1 as an example, when the service request message is level 1 or 2, the first orchestrator can be designated as the central orchestrator. When the service request message is level 3, the first orchestrator can be designated as the domain orchestrator. The service request message can then be sent to the first orchestrator.

[0079] Therefore, the method provided by the embodiments of the present disclosure defines a service classification table, thereby enabling the classification of service request messages. Furthermore, by eliminating the need for lower-level service request messages to bypass the central orchestrator, the present disclosure can directly send them to the domain orchestrator, thereby improving the response speed of lower-level service request messages, reducing latency, and enhancing the efficiency of network operations management.

[0080] In some embodiments, when the first orchestrator is a domain orchestrator, the first orchestrator may convert the service request message into a corresponding orchestration instruction and send the orchestration instruction to the corresponding controller 103. When the first orchestrator is a central orchestrator, the first orchestrator may first send the orchestration instruction to the domain orchestrator corresponding to the first orchestrator. The domain orchestrator corresponding to the first orchestrator then sends the orchestration instruction to the controller 103.

[0081] The disclosed embodiments do not limit the method by which the first orchestrator converts the service request message into the corresponding orchestration instructions. In some embodiments, the first orchestrator may include a smart contract template. In this case, the first orchestrator is configured to convert the service request message into the corresponding orchestration instructions using the smart contract template.

[0082] The disclosed embodiments do not limit the form of the smart contract template; the form of the smart contract template can be determined based on experience or application scenarios. For example, any type of service request message can correspond to a smart contract template, and the first orchestrator can select the corresponding smart contract template based on the type of service request message. Furthermore, the disclosed embodiments do not limit the form of the orchestration instruction.

[0083] In some embodiments, the first orchestrator may also generate a service data block, which is used to store the service configuration in the service request message, the service identifier corresponding to the service request message, and the user identifier corresponding to the user sending the service request message. The first orchestrator may then send the service data block to each second orchestrator other than the first orchestrator in the plurality of system orchestrators 102 and to controller 103. The second orchestrator may store the received service data block. Furthermore, controller 103 may also store the received service data block.

[0084] For example, when the service request message is sent for the first time, the first orchestrator may generate a new service data block based on the service request message. If the service request message is not sent for the first time, the first orchestrator may update the data in the previously generated service data block based on the service request message sent this time.

[0085] In one possible implementation, the service request message may be a QoS change request. Since QoS can change multiple times, when a user first sends a service request message requesting a QoS change, the first orchestrator may generate a new service data block to store data related to the QoS change. Subsequently, when the user sends another service request message requesting a QoS change, the first orchestrator may update the data in the previously generated service data block based on the newly sent service request message to store the latest data related to the QoS change.

[0086] In an exemplary embodiment, the first orchestrator may store the service identifier corresponding to the service request message and the user identifier corresponding to the user sending the service request message by encapsulating the corresponding <user identifier, service identifier> tuple in a service data block.

[0087] The disclosed embodiments do not limit the method by which the first orchestrator obtains the service identifier corresponding to the service request message and the user identifier corresponding to the user sending the service request message. For example, the service identifier corresponding to the service request message and the user identifier corresponding to the user sending the service request message may both be included in the service request message. The first orchestrator may obtain the service identifier corresponding to the service request message and the user identifier corresponding to the user sending the service request message through the service request message. Alternatively, the service identifier corresponding to the service request message and the user identifier corresponding to the user sending the service request message may both be generated by the first orchestrator.

[0088] In some exemplary embodiments, the disclosed embodiments do not limit the order in which the first orchestrator converts the service request message into the corresponding orchestration instructions and generates the service data blocks. For example, the first orchestrator may first convert the service request message into the corresponding orchestration instructions and then generate the service data blocks. Alternatively, the first orchestrator may first generate the service data blocks and then convert the service request message into the corresponding orchestration instructions. Alternatively, the first orchestrator may perform both the generation of the service data blocks and the conversion of the service request message into the corresponding orchestration instructions in parallel.

[0089] In some embodiments, each system orchestrator 102 and controller 103 may include a user service data chain. After the first orchestrator sends the service data block to each second orchestrator, the second orchestrator may verify the service data block based on the distributed ledger's consensus mechanism. The second orchestrator is configured to store the service data block in the user service data chain if the service data block passes verification. Furthermore, the controller 103 may also be configured to verify the service data block based on the distributed ledger's consensus mechanism and, if the service data block passes verification, store the service data block in the user service data chain.

[0090] Exemplarily, the second orchestrator and the controller 103 may both store the service data block in the user service data chain in a Merkle Tree structure.

[0091] Illustratively, when the service data block fails to pass the verification of the second orchestrator, the second orchestrator may discard the service data block and no longer perform subsequent operations.

[0092] The embodiments of the present disclosure do not limit the consensus mechanism of the distributed ledger. Exemplarily, the consensus mechanism of the distributed ledger may be, for example, POW (Proof Of Work), BFT (Byzantine Fault Tolerance), a hybrid consensus mechanism, etc.

[0093] It should be noted that the data stored in the user service data chain corresponding to each system orchestrator 102 is consistent. Each system orchestrator 102 can be regarded as a node in the user service data chain.

[0094] For example, since the Merkle tree structure can record hash values ​​layer by layer, when any changes occur to the underlying data in the Merkle tree structure, the parent node corresponding to the underlying data will also change accordingly. Similarly, the change can be propagated layer by layer along the path to the root node.

[0095] Therefore, by storing the business data blocks in a Merkle tree structure, it is possible to prevent the data in the business data blocks recorded in any system orchestrator 102 from being maliciously tampered with.

[0096] For example, for a user business data chain with N nodes, once the value of a node (such as the root node) in its corresponding Merkle tree structure is found to have changed, by traversing downward along the node, the business data block where the data has been tampered with can be quickly located in a maximum of O(lgN) time.

[0097] Those skilled in the art will appreciate that the number of service acceptors 101, multiple system orchestrators 102, controllers 103, and network devices 104 in FIG2 is merely illustrative, and any number of service acceptors 101, multiple system orchestrators 102, controllers 103, and network devices 104 may be provided as needed. This is not limited in the presently disclosed embodiments.

[0098] This exemplary implementation is described in detail below with reference to the accompanying drawings and examples.

[0099] First, an embodiment of the present disclosure provides a network operation management method, which can be interactively executed by a service acceptor and a first orchestrator.

[0100] FIG3 shows a flow chart of a network operation management method in an embodiment of the present disclosure. As shown in FIG3 , the network operation management method provided in the embodiment of the present disclosure includes the following steps S302 to S312 .

[0101] S302: The service acceptor obtains a service request message and determines the level of the service request message.

[0102] S304: The service acceptor determines a first orchestrator from a plurality of system orchestrators according to the level of the service request message.

[0103] S306: The service acceptor sends the service request message to the first orchestrator.

[0104] S308: The first orchestrator receives the service request message sent by the service acceptor, and converts the service request message into a corresponding orchestration instruction.

[0105] S310: The first scheduler sends the schedule instruction to the controller.

[0106] S312: The controller receives the orchestration instruction, converts the orchestration instruction into service configuration information, and sends the service configuration information to the network device.

[0107] It should be noted that the implementation of S302 to S312 here can refer to the above embodiments and will not be repeated here.

[0108] The method provided by the embodiment of the present disclosure can determine the level of the service request message through the service acceptor and determine the first orchestrator based on the level. In addition, the embodiment of the present disclosure can enable both the central orchestrator and the domain orchestrator to receive service request messages and convert them into corresponding orchestration instructions. Therefore, the present disclosure does not require all service request messages to pass through the central orchestrator. When a large number of users submit service request messages, the processing pressure on the central orchestrator can be reduced. In addition, the embodiment of the present disclosure can speed up the response speed of service request messages and improve the efficiency of network operation and management.

[0109] In some embodiments, a schematic diagram of a network operations management process can be shown in Figure 4. In Figure 4, the user terminal can include a client corresponding to the user site. The user can use the user terminal to send a service request message A and a service request message B to the service acceptor. For example, service request message A can be used to request the establishment of a new dedicated line from AS1 to AS3. Service request message B can be used to request an increase in bandwidth for the user site.

[0110] The service acceptor can receive service request message A and service request message B. Furthermore, the service acceptor can determine the levels of service request message A and service request message B, respectively, using a service level table. For example, service request message A can be level 1, while service request message B can be level 3. Assume that the first orchestrator corresponding to a level 1 service request message is the central orchestrator. And the first orchestrator corresponding to a level 3 service request message is the domain orchestrator. Therefore, the service acceptor can send service request message A to the central orchestrator and send service request message B to domain orchestrator C.

[0111] The central orchestrator can receive the service request message A and convert the service request message A into the corresponding orchestration instruction A according to the smart contract template. The orchestration instruction A is then sent to the domain orchestrator corresponding to the central orchestrator.

[0112] It should be noted that since the service request message A is used to request the opening of a new dedicated line from AS1 to AS3. Therefore, the domain orchestrators corresponding to the central orchestrator may include domain orchestrator A, domain orchestrator B, and domain orchestrator C. Therefore, domain orchestrator A, domain orchestrator B, and domain orchestrator C can all receive the orchestration instruction A sent by the central orchestrator, and send the orchestration instruction A to the corresponding controllers respectively. Afterwards, controller A can convert the orchestration instruction A into configuration information A, and send the configuration instruction to AS1 respectively. Controller B can convert the orchestration instruction A into configuration information A, and send the configuration instruction to AS2 respectively. Controller C can convert the orchestration instruction A into configuration information A, and send the configuration instruction to AS3 respectively. Afterwards, the configuration information obtained in AS1, AS2, and AS3 can be sent to the network device (i.e., the user site shown in Figure 4) through the service acceptor.

[0113] In addition, domain orchestrator C can receive service request message B and convert it into corresponding orchestration instruction B based on the smart contract template. It then sends orchestration instruction B to controller C. Controller C can convert orchestration instruction B into corresponding configuration information B and send it to the user site via AS3 and the service acceptor.

[0114] In some exemplary embodiments, FIG5 shows a schematic diagram of a possible system orchestrator. It should be noted that the system orchestrator can be a central orchestrator or a domain orchestrator. As shown in FIG5 , the system orchestrator adds a user service data link library based on the first original functional module. Exemplarily, the user service data link library can be used to store various user service data links.

[0115] In addition, the embodiment of the present disclosure does not limit the first original functional module of the system orchestrator. Exemplarily, the first original functional module of the system orchestrator can be used to convert the service request message into a corresponding orchestration instruction.

[0116] In some exemplary embodiments, a schematic diagram of a possible user terminal is shown in Figure 6. As shown in Figure 6, the user terminal has a new service acceptor based on the second original functional module. The service acceptor may include a service classification table.

[0117] Exemplarily, the service acceptor may be configured to obtain a service request message and determine a level of the service request message based on the service classification table. Furthermore, the service processor may also determine a first orchestrator from among multiple system orchestrators based on the level of the service request message and send the service request message to the first orchestrator.

[0118] Based on the same inventive concept, the present disclosure also provides a network operation management device, as described in the following embodiment. Since the principle of solving the problem in the device embodiment is similar to that in the above method embodiment, the implementation of the device embodiment can refer to the implementation of the above method embodiment, and the repeated parts will not be repeated.

[0119] FIG7 shows a schematic diagram of a network operation management device according to an embodiment of the present disclosure. The device is applied to a service acceptor, and the service acceptor is connected to multiple system orchestrators. As shown in FIG7 , the device includes:

[0120] A level determination module 701 is configured to obtain a service request message and determine the level of the service request message;

[0121] A first orchestrator determining module 702 is configured to determine a first orchestrator from a plurality of system orchestrators according to the level of the service request message;

[0122] The service request message sending module 703 is used to send the service request message to the first orchestrator, wherein the first orchestrator is used to convert the service request message into a corresponding orchestration instruction and send the orchestration instruction to the controller. The controller is used to receive the orchestration instruction, convert the orchestration instruction into service configuration information, and send the service configuration information to the network device.

[0123] FIG8 shows a schematic diagram of another network operation management device according to an embodiment of the present disclosure. The device is applied to a first orchestrator, which can be a central orchestrator or a domain orchestrator. The first orchestrator can be connected to a service acceptor. The service acceptor is used to obtain a service request message, determine the level of the service request message, determine the first orchestrator from multiple system orchestrators based on the level of the service request message, and send the service request message to the first orchestrator. As shown in FIG8, the device includes:

[0124] The service request message receiving module 801 is used to receive the service request message sent by the service acceptor;

[0125] The orchestration instruction sending module 802 is used to convert the service request message into a corresponding orchestration instruction and send the orchestration instruction to the controller. The controller is used to receive the orchestration instruction, convert the orchestration instruction into service configuration information, and send the service configuration information to the network device.

[0126] The device provided by the embodiment of the present disclosure can determine the level of the service request message through the service acceptor and determine the first orchestrator based on the level. In addition, the embodiment of the present disclosure can enable both the central orchestrator and the domain orchestrator to receive service request messages and convert them into corresponding orchestration instructions. Therefore, the present disclosure does not require all service request messages to pass through the central orchestrator. When a large number of users submit service request messages, the processing pressure on the central orchestrator can be reduced. In addition, the embodiment of the present disclosure can speed up the response speed of service request messages and improve the efficiency of network operation and management.

[0127] Those skilled in the art will appreciate that various aspects of the present disclosure may be implemented as systems, methods, or program products. Therefore, various aspects of the present disclosure may be implemented in the following forms: a complete hardware implementation, a complete software implementation (including firmware, microcode, etc.), or a combination of hardware and software implementations, which may be collectively referred to herein as "circuits," "modules," or "systems."

[0128] The electronic device 900 according to this embodiment of the present disclosure is described below with reference to Figure 9. The electronic device 900 shown in Figure 9 is merely an example and should not limit the functions and scope of use of the embodiments of the present disclosure.

[0129] As shown in Figure 9, electronic device 900 is implemented as a general-purpose computing device. Components of electronic device 900 may include, but are not limited to, the aforementioned at least one processing unit 910, the aforementioned at least one storage unit 920, and a bus 930 connecting various system components (including storage unit 920 and processing unit 910).

[0130] The storage unit stores program code, which can be executed by the processing unit 910, so that the processing unit 910 performs the steps according to various exemplary embodiments of the present disclosure described in the above "Specific Implementation" section of this specification.

[0131] The storage unit 920 may include a readable medium in the form of a volatile storage unit, such as a random access memory unit (RAM) 9201 and / or a cache memory unit 9202 , and may further include a read-only memory unit (ROM) 9203 .

[0132] The storage unit 920 may also include a program / utility 9204 having a set (at least one) of program modules 9205, such program modules 9205 including but not limited to: an operating system, one or more application programs, other program modules, and program data, each of which or some combination may include an implementation of a network environment.

[0133] Bus 930 may represent one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, a processing unit, or a local bus using any of a variety of bus architectures.

[0134] The electronic device 900 can also communicate with one or more external devices 940 (e.g., a keyboard, a pointing device, a Bluetooth device, etc.), one or more devices that enable a user to interact with the electronic device 900, and / or any device that enables the electronic device 900 to communicate with one or more other computing devices (e.g., a router, a modem, etc.). Such communication can occur via an input / output (I / O) interface 950. Furthermore, the electronic device 900 can communicate with one or more networks (e.g., a local area network (LAN), a wide area network (WAN), and / or a public network such as the Internet) via a network adapter 960. As shown, the network adapter 960 communicates with other modules of the electronic device 900 via a bus 930. It should be understood that, although not shown in the figure, other hardware and / or software modules can be used in conjunction with the electronic device 900, including but not limited to microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems.

[0135] Through the description of the above embodiments, it is easy for those skilled in the art to understand that the example embodiments described herein can be implemented by software or by combining software with necessary hardware. Therefore, the technical solution according to the embodiments of the present disclosure can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a USB flash drive, a mobile hard disk, etc.) or on a network, and includes several instructions to enable a computing device (which can be a personal computer, a server, a terminal device, or a network device, etc.) to execute the method according to the embodiments of the present disclosure.

[0136] In particular, according to an embodiment of the present disclosure, the process described above with reference to the flowchart may be implemented as a computer program product, which includes: a computer program, which implements the above-mentioned network operation management method when executed by a processor.

[0137] In an exemplary embodiment of the present disclosure, a computer-readable storage medium is also provided. The computer-readable storage medium may be a readable signal medium or a readable storage medium. A program product capable of implementing the above-mentioned method of the present disclosure is stored thereon. In some possible implementations, various aspects of the present disclosure may also be implemented in the form of a program product, which includes program code. When the program product is run on a terminal device, the program code is used to cause the terminal device to execute the steps according to the various exemplary embodiments of the present disclosure described in the "Detailed Implementation Methods" section above of this specification.

[0138] More specific examples of computer-readable storage media in the present disclosure may include, but are not limited to, an electrical connection having one or more conductors, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), optical fibers, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0139] In the present disclosure, a computer-readable storage medium may include a data signal propagated in baseband or as part of a carrier wave, which carries readable program code. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. A readable signal medium may also be any readable medium other than a readable storage medium that can transmit, propagate, or transfer a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0140] Alternatively, the program code contained on the computer-readable storage medium may be transmitted using any appropriate medium, including but not limited to wireless, wired, optical cable, RF, etc., or any suitable combination thereof.

[0141] In a specific implementation, the program code for performing the operations of the present disclosure may be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Java, C++, and the like, as well as conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user's computing device, partially on the user's device, as a standalone software package, partially on the user's computing device and partially on a remote computing device, or entirely on a remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the user's computing device via any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computing device (e.g., via the Internet using an Internet service provider).

[0142] It should be noted that although several modules or units of the device for action execution are mentioned in the detailed description above, this division is not mandatory. In fact, according to the embodiments of the present disclosure, the features and functions of two or more modules or units described above can be concretized in one module or unit. Conversely, the features and functions of one module or unit described above can be further divided into multiple modules or units to be concretized.

[0143] Furthermore, although the steps of the method of the present disclosure are described in a particular order in the accompanying drawings, this does not require or imply that the steps must be performed in this particular order, or that all steps shown must be performed to achieve the desired results. Additionally or alternatively, some steps may be omitted, multiple steps may be combined into one step, and / or one step may be decomposed into multiple steps.

[0144] From the description of the above embodiments, it will be readily apparent to those skilled in the art that the exemplary embodiments described herein may be implemented via software or via a combination of software and necessary hardware. Therefore, the technical solutions according to the embodiments of the present disclosure may be embodied in the form of a software product, which may be stored on a non-volatile storage medium (such as a CD-ROM, USB flash drive, or mobile hard drive) or on a network and include instructions for causing a computing device (such as a personal computer, server, mobile terminal, or network device) to execute the methods according to the embodiments of the present disclosure.

[0145] Other embodiments of the present disclosure will readily occur to those skilled in the art after considering the specification and practicing the invention disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of the present disclosure that follow the general principles of the present disclosure and include common knowledge or customary techniques in the art not disclosed herein. The description and examples are to be considered as exemplary only, with the true scope of the present disclosure being indicated by the appended claims.

Claims

1. A network operation management system, wherein: The system includes: a business acceptor, multiple system orchestrators, a controller, and a network device, wherein the multiple system orchestrators include at least one of a central orchestrator and a domain orchestrator; The service acceptor is used to obtain the service request message and determine the level of the service request message; The service acceptor is further configured to determine a first orchestrator from a plurality of system orchestrators according to the level of the service request message, and send the service request message to the first orchestrator, wherein the first orchestrator is a central orchestrator or a domain orchestrator; The first orchestrator is configured to convert the service request message into a corresponding orchestration instruction and send the orchestration instruction to the controller; The controller is used to receive the orchestration instruction, convert the orchestration instruction into service configuration information, and send the service configuration information to the network device.

2. The network operation management system according to claim 1, wherein: When the first orchestrator is a central orchestrator, the first orchestrator is configured to send the orchestration instruction to a domain orchestrator corresponding to the first orchestrator; The domain orchestrator corresponding to the first orchestrator is configured to send the orchestration instruction to the controller.

3. The network operation management system according to claim 1 or 2, wherein: The first scheduler is further used to generate a service data block, wherein the service data block is used to store the service configuration in the service request message, the service identifier corresponding to the service request message, and the user identifier corresponding to the user sending the service request message; The first orchestrator is further configured to send the service data block to each second orchestrator and a controller in a plurality of system orchestrators except the first orchestrator; The second arranger is used to store the received service data blocks; The controller is also used to store the received service data blocks.

4. The network operation management system according to claim 3, wherein: Each system orchestrator and controller includes a user service data link; The second orchestrator is configured to verify the business data block according to a consensus mechanism of the distributed ledger, and when the business data block passes the verification, store the business data block in the user business data chain; The controller is used to verify the business data block according to the consensus mechanism of the distributed ledger, and when the business data block passes the verification, store the business data block in the user business data chain.

5. The network operation management system according to claim 1 or 2, wherein: The service acceptor includes a service classification table, wherein the service classification table is used to describe at least one type of service request message and a level corresponding to the type of at least one service request message; The service acceptor is used to determine the grade of the service request message through the service grade table.

6. The network operation management system according to claim 1 or 2, wherein: The first orchestrator includes a smart contract template; The first orchestrator is configured to convert the service request message into a corresponding orchestration instruction through the smart contract template.

7. A network operation management method, wherein: The method is performed by a service acceptor, wherein the service acceptor is connected to a plurality of system orchestrators respectively, and comprises: Obtaining a service request message, and determining a level of the service request message; Determining a first orchestrator from a plurality of system orchestrators according to the level of the service request message; Sending the service request message to the first orchestrator; The first orchestrator is used to convert the service request message into a corresponding orchestration instruction, and send the orchestration instruction to the controller; the controller is used to receive the orchestration instruction, convert the orchestration instruction into service configuration information, and send the service configuration information to the network device.

8. A network operation management method, wherein: The method is performed by a first orchestrator, the first orchestrator being a central orchestrator or a domain orchestrator, and the first orchestrator being connected to a service acceptor; the service acceptor is used to obtain a service request message, determine a level of the service request message, determine a first orchestrator from a plurality of system orchestrators according to the level of the service request message, and send the service request message to the first orchestrator; The method comprises: Receiving a service request message sent by the service acceptor; The service request message is converted into a corresponding orchestration instruction, and the orchestration instruction is sent to a controller, wherein the controller is used to receive the orchestration instruction, convert the orchestration instruction into service configuration information, and send the service configuration information to a network device.

9. A network operation management device, wherein: Applied to a business acceptor, the business acceptor is connected to a plurality of system orchestrators respectively, including: A level determination module, used to obtain a service request message and determine the level of the service request message; A first orchestrator determining module, configured to determine a first orchestrator from a plurality of system orchestrators according to the level of the service request message; A service request message sending module is used to send the service request message to the first orchestrator, wherein the first orchestrator is used to convert the service request message into a corresponding orchestration instruction, and send the orchestration instruction to a controller, and the controller is used to receive the orchestration instruction and convert the orchestration instruction into service configuration information, and send the service configuration information to the network device.

10. A network operation management device, wherein: The method is applied to a first orchestrator, the first orchestrator is a central orchestrator or a domain orchestrator, and the first orchestrator is connected to a service acceptor; the service acceptor is used to obtain a service request message, determine the level of the service request message, determine a first orchestrator from multiple system orchestrators according to the level of the service request message, and send the service request message to the first orchestrator; The device comprises: A service request message receiving module, used to receive the service request message sent by the service acceptor; The orchestration instruction sending module is used to convert the service request message into a corresponding orchestration instruction, and send the orchestration instruction to the controller. The controller is used to receive the orchestration instruction, convert the orchestration instruction into service configuration information, and send the service configuration information to the network device.

11. An electronic device, wherein: include: processor; as well as A memory, configured to store executable instructions of the processor; The processor is configured to execute the network operation management method according to any one of claims 7 to 8 by executing the executable instructions.

12. A computer-readable storage medium having a computer program stored thereon, wherein: When the computer program is executed by a processor, the network operation management method according to any one of claims 7 to 8 is implemented.

13. A computer program product comprising a computer program, wherein: When the computer program is executed by a processor, the bandwidth resource allocation method according to any one of claims 7 to 8 is implemented.

Citation Information

Patent Citations

  • Service orchestrator-based metropolitan area network service processing method

    CN109120459A

  • End-to-end service quality guarantee system

    CN110278118A

  • Network end-to-end service arrangement system and method

    CN110401572A

  • Service orchestration method, device and system and storage medium

    CN114090244A

  • Network operation management system, method and device, electronic equipment and storage medium

    CN116489227A