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

Abstract

The present disclosure provides a network operation management system, method and device, electronic equipment and storage medium, and relates to the technical field of network. A method is executed by a service receiver, comprising: obtaining a service request message, determining the level of the service request message; determining a first orchestrator according to the level of the service request message; and sending the service request message to the first orchestrator. Another method is executed by the first orchestrator, comprising: receiving the service request message sent by the service receiver; converting the service request message into corresponding orchestration instructions; sending the orchestration instructions to a controller; the controller is used for receiving the orchestration instructions, converting the orchestration instructions 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 the central orchestrator. When a large number of users propose service request messages, the processing pressure of the central orchestrator can be reduced. And the response speed of the service request message can be accelerated, and the efficiency of network operation management can be improved.

Description

Technical Field

[0001] This disclosure relates to the field of network technology, and in particular to a network operation management system, method, apparatus, electronic device, and storage medium. Background Technology

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

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

[0004] Therefore, the methods provided by these technologies may place a significant processing burden on the central orchestrator when a large number of user service request messages are received. Furthermore, the latency caused by detours can lead to untimely responses to service request messages, resulting in inefficient network operation and management.

[0005] It should be noted that the information disclosed in the background section above is only used to enhance the understanding of the background of this disclosure, and therefore may include information that does not constitute prior art known to those skilled in the art. Summary of the Invention

[0006] This disclosure provides a network operation management system, method, apparatus, electronic device, and storage medium, which at least to some extent overcomes the problems in related technologies that may bring huge processing pressure to the central orchestrator and that business request messages may not be responded to in a timely manner, resulting in low efficiency in network operation management.

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

[0008] According to one aspect of the present disclosure, a network operation management system is provided, including: a service receiver, 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.

[0009] This service receiver is used to obtain service request messages and determine the level of the service request message;

[0010] The service receiver is also used to determine the 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, wherein the first orchestrator is a central orchestrator or a domain orchestrator.

[0011] The first orchestrator is used to convert the service request message into a corresponding orchestration instruction and send the orchestration instruction to the controller.

[0012] 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.

[0013] In some embodiments of this disclosure, when the first arranger is a central arranger, the first arranger is used to send the arrangement instruction to the domain arranger corresponding to the first arranger.

[0014] The domain orchestrator corresponding to the first orchestrator is used to send the orchestration instruction to the controller.

[0015] In some embodiments of this disclosure, the first orchestrator is further configured to generate a service data block, which stores 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 who sent the service request message.

[0016] The first orchestrator is also used to send the service data block to each of the second orchestrators and controllers among the multiple system orchestrators other than the first orchestrator;

[0017] The second orchestrator is used to store the received service data blocks;

[0018] The controller is also used to store the received service data blocks.

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

[0020] The second orchestrator is used to verify the business data block according to the consensus mechanism of the distributed ledger. When the business data block is verified, it is stored in the user's business data chain.

[0021] The controller is used to verify the business data block according to the consensus mechanism of the distributed ledger. When the business data block is verified, it is stored in the user's business data chain.

[0022] In some embodiments of this disclosure, the service receiver includes a service classification table, which describes the type of at least one service request message and the classification level corresponding to the type of at least one service request message.

[0023] This service receiver is used to determine the level of the service request message using the service classification table.

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

[0025] The first orchestrator is used to convert the business request message into corresponding orchestration instructions using the smart contract template.

[0026] According to another aspect of this disclosure, a network operation management method is provided, executed by a service receiver connected to multiple system orchestrators, comprising:

[0027] Obtain the business request message and determine its priority level;

[0028] Based on the level of the service request message, the first orchestrator is determined from multiple system orchestrators;

[0029] Send the service request message to the first orchestrator;

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

[0031] According to another aspect of this disclosure, a network operation management method is provided, executed by a first orchestrator, which is a central orchestrator or a domain orchestrator, and connected to a service receiver; the service receiver is used to acquire a service request message, determine the 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 includes:

[0032] Receive service request messages sent by the service receiver;

[0033] The service request message is converted into a corresponding orchestration instruction and sent to the controller. The controller receives the orchestration instruction, converts it into service configuration information, and sends the service configuration information to the network device.

[0034] According to another aspect of this disclosure, a network operation management apparatus is provided, applied to a service receiver, the service receiver being connected to multiple system orchestrators, comprising:

[0035] The level determination module is used to obtain business request messages and determine the level of the business request message;

[0036] The first orchestrator determination module is used to determine the first orchestrator from multiple system orchestrators based on the level of the service request message.

[0037] The service request message sending module is used to send 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.

[0038] According to another aspect of this disclosure, a network operation management apparatus is provided, applied to a first orchestrator, which is a central orchestrator or a domain orchestrator, and connected to a service receiver; the service receiver is used to acquire a service request message, determine the 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 apparatus includes:

[0039] The business request message receiving module is used to receive business request messages sent by the business receiver.

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

[0041] According to another aspect of this 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 network operation management method described above by executing the executable instructions.

[0042] According to another aspect of this disclosure, a computer-readable storage medium is provided having a computer program stored thereon that, when executed by a processor, implements the network operation management method described above.

[0043] According to another aspect of this 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 operation management method provided in various alternative embodiments of this disclosure.

[0044] The technical solution provided in this disclosure allows for the determination of the service request message's level by a service receiver, and the selection of a first orchestrator based on that level. Furthermore, this disclosure enables both the central orchestrator and the domain orchestrator to receive service request messages and convert them into corresponding orchestration instructions. Therefore, this disclosure eliminates the need for all service request messages to pass through the central orchestrator. When a large number of users submit service request messages, it reduces the processing load on the central orchestrator. Moreover, this disclosure can accelerate the response speed of service request messages and improve the efficiency of network operation and management.

[0045] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this disclosure. Attached Figure Description

[0046] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this disclosure and, together with the description, serve to explain the principles of this disclosure. It is obvious that the drawings described below are merely some embodiments of this disclosure, and those skilled in the art can obtain other drawings based on these drawings without any inventive effort.

[0047] Figure 1 This diagram illustrates an operation management system architecture in an operator network according to an embodiment of the present disclosure.

[0048] Figure 2 A schematic diagram of the system architecture of a network operation management system according to an embodiment of this disclosure is shown;

[0049] Figure 3 This diagram illustrates a flowchart of a network operation management method according to an embodiment of the present disclosure;

[0050] Figure 4 This diagram illustrates a network operation management process according to an embodiment of the present disclosure.

[0051] Figure 5 This diagram illustrates a system orchestrator according to an embodiment of the present disclosure;

[0052] Figure 6 A schematic diagram of a user terminal according to an embodiment of this disclosure is shown;

[0053] Figure 7 This diagram illustrates a network operation management device according to an embodiment of the present disclosure;

[0054] Figure 8 This diagram illustrates another network operation management device in an embodiment of the present disclosure;

[0055] Figure 9 A structural block diagram of an electronic device according to an embodiment of the present disclosure is shown. Detailed Implementation

[0056] Exemplary embodiments will now be described more fully with reference to the accompanying drawings. However, these exemplary embodiments can be implemented in many forms and should not be construed as limited to the examples set forth herein; rather, they are provided so that this disclosure will be more comprehensive and complete, and will fully convey the concept of the exemplary 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.

[0057] Furthermore, the accompanying drawings are merely illustrative of this disclosure and are not necessarily drawn to scale. The same reference numerals in the drawings denote the same or similar parts, and therefore repeated descriptions of them will be omitted. Some block diagrams shown in the drawings are functional entities and do not necessarily correspond to physically or logically independent entities. These functional entities may be implemented in software, in one or more hardware modules or integrated circuits, or in different network and / or processor devices and / or microcontroller devices.

[0058] To facilitate understanding, the architecture of the operation and management system in a carrier network will be explained first. For example... Figure 1 As shown, the operation and management system architecture in an operator's network may include a portal, a central orchestrator, a domain orchestrator, a controller, and network devices.

[0059] The portal is responsible for receiving user service request messages and sending them to the central orchestrator. The central orchestrator can then convert the service request message into orchestration instructions and send these instructions to a domain orchestrator corresponding to the central processing unit. For example... Figure 1 As shown, the central orchestrator corresponds to domain orchestrators A, B, and C. Therefore, the central orchestrator can send orchestration commands to any one of these domain orchestrators. Taking the central orchestrator sending orchestration commands to domain orchestrator A as an example, domain orchestrator A can then forward the received orchestration commands to its managed controller A. Controller A converts the orchestration commands into configuration commands and sends them to the corresponding AS (Autonomous System) 1. Finally, the corresponding AS 1 can send the configuration information to the network device (i.e.,...). Figure 1 (The user site shown).

[0060] Depend on Figure 1As shown in the illustrated operation and management system architecture, every service request message sent by a user must be routed through the central orchestrator for processing before being distributed level by level to the corresponding controller. When a large number of users send service request messages on the network, it can place a significant processing load on the central orchestrator, and the latency caused by this routing can prevent some simpler user service requests from being responded to in a timely manner. Therefore, it is necessary to... Figure 1 The system architecture shown has been adjusted.

[0061] Figure 2 A schematic diagram of an exemplary system architecture that can be applied to the network operation management system of the embodiments of this disclosure is shown.

[0062] like Figure 2 As shown, the system architecture 100 may include a service receiver 101, multiple system orchestrators 102, a controller 103, and a network device 104. Among them, the multiple system orchestrators 102 include at least one of a central orchestrator and a domain orchestrator.

[0063] The service acceptor 101 can be used to acquire service request messages and determine the level of the service request message. The service acceptor 101 can also be used to determine a first orchestrator from multiple system orchestrators 102 based on 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 can be used to convert the service request message into a corresponding orchestration instruction and send the orchestration instruction to the controller 103. The controller 103 can be used to receive the orchestration instruction, convert the orchestration instruction into service configuration information, and send the service configuration information to the network device 104.

[0064] This disclosure does not limit the type of the service acceptor 101; the service acceptor 101 can be any electronic device with computing capabilities. The type of the service acceptor 101 can be determined according to the application scenario.

[0065] This disclosure does not limit the type of network device 104. Optionally, the network device 104 can be a CPE (Customer Premise Equipment) or a gateway.

[0066] For example, a communication link can be provided between the service receiver 101 and any system orchestrator 102 via a network. Furthermore, a communication link can also be provided between any system orchestrator 102 and the network device 104 via a network. This network can be a wired network or a wireless network.

[0067] Optionally, the aforementioned wireless or wired networks use standard communication technologies and / or protocols. The network is typically the Internet, but can also be any network, including but not limited to Local Area Networks (LANs), Metropolitan Area Networks (MANs), Wide Area Networks (WANs), mobile, wired or wireless networks, private networks, or any combination of virtual private networks. In some embodiments, technologies and / or formats including Hyper Text Markup Language (HTML), Extensible Markup Language (XML), etc., are used to represent data exchanged over the network. Furthermore, conventional encryption technologies such as Secure Socket Layer (SSL), Transport Layer Security (TLS), Virtual Private Networks (VPNs), and Internet Protocol Security (IPsec) can be used to encrypt all or some links. In other embodiments, customized and / or dedicated data communication technologies can be used to replace or supplement the aforementioned data communication technologies.

[0068] In some exemplary embodiments, the service acceptor 101 may be located inside the user terminal, or the service acceptor 101 may also be a network device capable of establishing a connection with the user terminal. Therefore, when a user submits a service request message, the service acceptor 101 can acquire the service request message.

[0069] This disclosure does not limit the user terminal described above. The user terminal can be various electronic devices, including but not limited to smartphones, tablets, laptops, desktop computers, wearable devices, augmented reality devices, virtual reality devices, etc.

[0070] In some embodiments, the service receiver 101 may include a service classification table, which describes the type of at least one service request message and the classification level corresponding to that type of service request message. Therefore, the service receiver 101 can be used to determine the classification level of the service request message using the service classification table.

[0071] This disclosure does not limit the type of service request messages. For example, service request messages with the same service characteristics can be classified as the same type. These service characteristics include, for example, issues related to construction, changes to network infrastructure, or changes to a single network performance parameter.

[0072] In an exemplary embodiment, the service request message concerning construction issues could be, for example, the activation of a new leased line. The service request message concerning changes to network infrastructure could be, for example, a change in QoS (Quality of Service). The service request message concerning changes to a single network performance parameter could be, for example, a bandwidth adjustment.

[0073] For example, the service hierarchy table included in the service acceptor 101 may be as shown in Table 1.

[0074] Table 1

[0075] Level 1 Construction issues Level 2 Involves changes to network infrastructure Level 3 Involving a single network performance parameter

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

[0077] This disclosure does not limit the method for determining the first orchestrator from multiple system orchestrators 102 based on the level of the service request message. Exemplarily, this 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, taking 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. Then, the service request message can be sent to the first orchestrator.

[0079] Therefore, the method provided in this disclosure defines a service classification table, thereby enabling the classification of service request messages by level. Furthermore, this disclosure allows lower-level service request messages to be sent directly to the domain orchestrator instead of bypassing the central orchestrator, improving the response speed of lower-level service request messages, reducing latency, and enhancing the efficiency of network operation and management.

[0080] In some embodiments, when the first orchestrator is a domain orchestrator, it can convert service request messages into corresponding orchestration instructions and send the orchestration instructions to the corresponding controller 103. When the first orchestrator is a central orchestrator, it can first send the orchestration instructions to the domain orchestrator corresponding to it. Then, the domain orchestrator corresponding to the first orchestrator sends the orchestration instructions to the controller 103.

[0081] This disclosure does not limit the method by which the first orchestrator converts a business request message into a corresponding orchestration instruction. In some embodiments, the first orchestrator may include a smart contract template. In this case, the first orchestrator is used to convert the business request message into a corresponding orchestration instruction using the smart contract template.

[0082] This disclosure does not limit the form of the smart contract template; the form can be determined based on experience or application scenarios. For example, any type of business 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 the business request message. Furthermore, this disclosure does not limit the form of the orchestration instructions.

[0083] In some embodiments, the first orchestrator can also generate a service data block, which stores 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 who sent the service request message. Then, the first orchestrator can send the service data block to each of the second orchestrators (excluding itself) and the controller 103 in the plurality of system orchestrators 102. The second orchestrator can be used to store the received service data block. Furthermore, the controller 103 can also be used to store the received service data block.

[0084] For example, when the service request message is sent for the first time, the first orchestrator can generate a new service data block based on the service request message. When the service request message is not sent for the first time, the first orchestrator can 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 can be a QoS change request. Since QoS can change multiple times, when a user first sends a QoS change request message, the first orchestrator can generate a new service data block to store the relevant data for that QoS change. Subsequently, when the user sends another QoS change request message, the first orchestrator can update the data in the previously generated service data block based on the new request message to store the latest data related to the QoS change.

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

[0087] This disclosure does 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 who sent the service request message. For example, both the service identifier corresponding to the service request message and the user identifier corresponding to the user who sent the service request message can be included in the service request message. The first orchestrator can obtain the service identifier corresponding to the service request message and the user identifier corresponding to the user who sent the service request message through the service request message. Alternatively, both the service identifier corresponding to the service request message and the user identifier corresponding to the user who sent the service request message can be generated by the first orchestrator.

[0088] In some exemplary embodiments, this disclosure does not limit the order in which the first orchestrator converts the service request message into the corresponding orchestration instruction and generates the service data block. For example, the first orchestrator may first convert the service request message into the corresponding orchestration instruction and then generate the service data block. Alternatively, the first orchestrator may first generate the service data block and then convert the service request message into the corresponding orchestration instruction. Or, the first orchestrator may perform both operations—generating the service data block and converting the service request message into the corresponding orchestration instruction—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 of the second orchestrators, the second orchestrator can verify the service data block according to the consensus mechanism of the distributed ledger. The second orchestrator is used to store the service data block into the user service data chain when the verification is successful. Similarly, the controller 103 can also be used to verify the service data block according to the consensus mechanism of the distributed ledger, and store the service data block into the user service data chain when the verification is successful.

[0090] For example, both the second orchestrator and the controller 103 can store the service data block in the user service data chain in a Merkle tree structure.

[0091] For example, when the business data block fails the verification of the second orchestrator, the second orchestrator can discard the business data block and no longer perform subsequent operations.

[0092] This disclosure does not limit the consensus mechanism of the distributed ledger. For example, the consensus mechanism of the distributed ledger can be 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 change occurs in the underlying data of the Merkle tree structure, the corresponding parent node of that underlying data will also change accordingly, and so on, the change can propagate layer by layer along the path to the root node.

[0095] Therefore, by storing business data blocks using a Merkle tree structure, malicious tampering of the data in any business data block recorded in any system orchestrator 102 can be avoided.

[0096] For example, for a user business data chain with N nodes, once it is found that the value of a certain node (e.g., the root node) in its corresponding Merkle tree structure has changed, the business data block whose data has been tampered with can be quickly located by traversing down along that node in at most O(lgN) time.

[0097] Those skilled in the art will know that Figure 2 The number of service receivers 101, multiple system orchestrators 102, controllers 103, and network devices 104 in this embodiment is merely illustrative. Any number of service receivers 101, multiple system orchestrators 102, controllers 103, and network devices 104 can be included as needed. This disclosure does not limit the scope of the embodiments.

[0098] The following detailed description of this exemplary implementation method is provided in conjunction with the accompanying drawings and embodiments.

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

[0100] Figure 3 This invention discloses a flowchart of a network operation management method according to an embodiment of the present invention, as shown below. Figure 3 As shown, the network operation management method provided in this embodiment includes the following steps S302 to S312.

[0101] S302, the service receiver obtains the service request message and determines the level of the service request message.

[0102] S304, the service receiver determines the first orchestrator from multiple system orchestrators based on the level of the service request message.

[0103] S306, the service receiver sends the service request message to the first orchestrator.

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

[0105] S310, the first orchestrator sends the orchestration 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 methods of S302 to S312 here can be found in the above embodiments, and will not be repeated here.

[0108] The method provided in this disclosure can determine the level of a service request message through a service receiver and determine a first orchestrator based on that level. Furthermore, this disclosure allows both the central orchestrator and the domain orchestrator to receive service request messages and convert them into corresponding orchestration instructions. Therefore, this disclosure eliminates the need for all service request messages to pass through the central orchestrator. When a large number of users submit service request messages, it can reduce the processing pressure on the central orchestrator. Moreover, this disclosure can accelerate 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 operation and management process can be as follows: Figure 4 As shown. In Figure 4In this context, the user terminal may include a client corresponding to the user site. Users can send service request message A and service request message B to the service receiver through the user terminal. For example, service request message A can be used to request the opening of a new leased line from AS1 to AS3. Service request message B can be used to request an increase in the bandwidth of the user site.

[0110] This service receiver can receive service request message A and service request message B. Furthermore, the service receiver can determine the level 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, and 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 receiver can send service request message A to the central orchestrator and service request message B to the domain orchestrator C.

[0111] The central orchestrator can receive a service request message A and, based on a smart contract template, convert the service request message A into a corresponding orchestration instruction A. Then, it sends the orchestration instruction A to the domain orchestrator corresponding to the central orchestrator.

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

[0113] Additionally, the domain orchestrator C can receive service request messages B and, based on the smart contract template, convert B into corresponding orchestration instructions B. It then sends these instructions B to the controller C. The controller C can convert the orchestration instructions B into corresponding configuration information B and send it to the user site via AS3 and the service receiver.

[0114] In some exemplary embodiments, Figure 5A schematic diagram of a possible system orchestrator is shown. It should be noted that this system orchestrator can be a central orchestrator or a domain orchestrator. Figure 5 As shown, the system orchestrator adds a user business data chain library to the existing functional modules. For example, this user business data chain library can be used to store various user business data chains.

[0115] Furthermore, this disclosure does not limit the first original functional module of the system orchestrator. For example, the first original functional module of the system orchestrator can be used to convert service request messages into corresponding orchestration instructions.

[0116] In some exemplary embodiments, Figure 6 A schematic diagram of a possible user terminal is shown. For example... Figure 6 As shown, this user terminal adds a service acceptor to the existing second functional module. This service acceptor may include a service hierarchy table.

[0117] For example, the service receiver can be used to obtain a service request message and determine the level of the service request message according to the service classification table. Additionally, the service processor can also 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.

[0118] Based on the same inventive concept, this disclosure also provides a network operation management device, as described in the following embodiments. Since the principle by which this device solves the problem is similar to that of the above-described method embodiments, the implementation of this device embodiment can refer to the implementation of the above-described method embodiments, and repeated details will not be elaborated further.

[0119] Figure 7 This diagram illustrates a network operation management device according to an embodiment of the present disclosure. The device is applied to a service receiver, which is connected to multiple system orchestrators, such as... Figure 7 As shown, the device includes:

[0120] The grade determination module 701 is used to obtain the service request message and determine the grade of the service request message;

[0121] The first orchestrator determination module 702 is used to determine the first orchestrator from multiple system orchestrators based on 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. 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] Figure 8 This diagram illustrates another network operation management device according to an embodiment of the present disclosure. This 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 receiver. The service receiver is used to acquire service request messages, determine the level of the service request message, and, based on the level of the service request message, determine a first orchestrator from multiple system orchestrators and send the service request message to the first orchestrator. Figure 8 As shown, the device includes:

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

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

[0126] The apparatus provided in this disclosure can determine the level of a service request message through a service receiver and determine a first orchestrator based on that level. Furthermore, this disclosure allows both the central orchestrator and the domain orchestrator to receive service request messages and convert them into corresponding orchestration instructions. Therefore, this disclosure eliminates the need for all service request messages to pass through the central orchestrator. When a large number of users submit service request messages, it can reduce the processing pressure on the central orchestrator. Moreover, this disclosure can accelerate the response speed of service request messages and improve the efficiency of network operation and management.

[0127] Those skilled in the art will understand that various aspects of this disclosure can be implemented as a system, method, or program product. Therefore, various aspects of this disclosure can be specifically implemented in the following forms: a completely hardware implementation, a completely software implementation (including firmware, microcode, etc.), or a combination of hardware and software aspects, collectively referred to herein as a "circuit," "module," or "system."

[0128] The following reference Figure 9 To describe an electronic device 900 according to such an embodiment of the present disclosure. Figure 9The electronic device 900 shown is merely an example and should not impose any limitation on the functionality and scope of use of the embodiments disclosed herein.

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

[0130] The storage unit stores program code that can be executed by the processing unit 910, causing the processing unit 910 to perform the steps described in the "Detailed Description" section of this specification according to various exemplary embodiments of this disclosure.

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

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

[0133] Bus 930 can represent one or more of several types of bus structures, including a memory cell bus or memory cell controller, a peripheral bus, a graphics acceleration port, a processing unit, or a local bus using any of the various bus structures.

[0134] Electronic device 900 can also communicate with one or more external devices 940 (e.g., keyboard, pointing device, Bluetooth device, etc.), and with one or more devices that enable a user to interact with electronic device 900, and / or with any device that enables electronic device 900 to communicate with one or more other computing devices (e.g., router, modem, etc.). This communication can be performed via input / output (I / O) interface 950. Furthermore, electronic device 900 can also communicate with one or more networks (e.g., local area network (LAN), wide area network (WAN), and / or public networks, such as the Internet) via network adapter 960. As shown, network adapter 960 communicates with other modules of electronic device 900 via bus 930. It should be understood that, although not shown in the figures, other hardware and / or software modules can be used in conjunction with 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] From the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein can be implemented by software or by combining software with necessary hardware. Therefore, the technical solutions according to the embodiments of this disclosure can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (such as a CD-ROM, USB flash drive, external hard drive, etc.) or on a network, including several instructions to cause a computing device (such as a personal computer, server, terminal device, or network device, etc.) to execute the methods according to the embodiments of this disclosure.

[0136] In exemplary embodiments of this disclosure, a computer-readable storage medium is also provided, which may be a readable signal medium or a readable storage medium. A program product capable of implementing the methods described above is stored thereon. In some possible implementations, various aspects of this disclosure may also be implemented as a program product including program code, which, when run on a terminal device, causes the terminal device to perform the steps of the various exemplary embodiments of this disclosure described in the "Detailed Description" section of this specification.

[0137] More specific examples of computer-readable storage media in this disclosure may include, but are not limited to: electrical connections having one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0138] In this disclosure, a computer-readable storage medium may include a data signal propagated in baseband or as part of a carrier wave, carrying 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, capable of transmitting, propagating, or transmitting a program for use by or in connection with an instruction execution system, apparatus, or device.

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

[0140] In practical implementation, program code for performing the operations of this disclosure can be written in any combination of one or more programming languages, including object-oriented programming languages ​​such as Java and C++, and conventional procedural programming languages ​​such as C or similar languages. The program code can execute 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 cases involving remote computing devices, the remote computing device can 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 it can be connected to an external computing device (e.g., via the Internet using an Internet service provider).

[0141] It should be noted that although several modules or units for the device used to perform actions have been mentioned in the detailed description above, this division is not mandatory. In fact, according to embodiments of this disclosure, the features and functions of two or more modules or units described above can be embodied in one module or unit. Conversely, the features and functions of one module or unit described above can be further divided and embodied by multiple modules or units.

[0142] Furthermore, although the steps of the method in this disclosure are described in a specific order in the accompanying drawings, this does not require or imply that the steps must be performed in that specific order, or that all the steps shown must be performed to achieve the desired result. Additional or alternative steps may be omitted, multiple steps may be combined into one step, and / or a step may be broken down into multiple steps.

[0143] From the above description of the embodiments, those skilled in the art will readily understand that the exemplary embodiments described herein can be implemented by software or by combining software with necessary hardware. Therefore, the technical solutions according to the embodiments of this disclosure can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (such as a CD-ROM, USB flash drive, external hard drive, etc.) or on a network, including several instructions to cause a computing device (such as a personal computer, server, mobile terminal, or network device, etc.) to execute the methods according to the embodiments of this disclosure.

[0144] Other embodiments of this disclosure will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope of this disclosure is indicated by the appended claims.

Claims

1. A network operation and management system, characterized in that, The system includes: a service receiver, multiple system orchestrators, a controller, and network devices, wherein the multiple system orchestrators include at least one of a central orchestrator and a domain orchestrator. The service receiver is used to acquire service request messages and determine the level of the service request messages; The service acceptor is further configured to 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, wherein the first orchestrator is a central orchestrator or a domain 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 configured to receive the orchestration instructions, convert the orchestration instructions into service configuration information, and send the service configuration information to the network device.

2. The network operation management system according to claim 1, characterized in that, When the first arranger is a central arranger, the first arranger is used to send the arrangement instructions to the domain arranger corresponding to the first arranger; The domain orchestrator corresponding to the first orchestrator is used to send the orchestration instructions to the controller.

3. The network operation management system according to claim 1 or 2, characterized in that, The first orchestrator is further configured to generate a service data block, wherein the service data block is 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 who sent the service request message; The first orchestrator is also configured to send the service data block to each of the second orchestrators and controllers among the multiple system orchestrators other than the first orchestrator; The second orchestrator 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, characterized in that, Each system orchestrator and controller includes a user business data chain; The second orchestrator is used to verify the business data block according to the consensus mechanism of the distributed ledger, and when the business data block is verified, it stores 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 is verified, it stores the business data block in the user business data chain.

5. The network operation management system according to claim 1 or 2, characterized in that, The service receiver includes a service hierarchy table, which describes at least one type of service request message and the level corresponding to that type of service request message. The service receiver is used to determine the level of the service request message through the service classification table.

6. The network operation management system according to claim 1 or 2, characterized in that, The first orchestrator includes a smart contract template; The first orchestrator is used to convert the business request message into corresponding orchestration instructions through the smart contract template.

7. A network operation and management method, characterized in that, The method, executed by a service acceptor connected to multiple system orchestrators, includes: Obtain the business request message and determine the level of the business request message; Based on the level of the service request message, a first orchestrator is determined from multiple system orchestrators, wherein the first orchestrator is a central orchestrator or a domain orchestrator. Send 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 and management method, characterized in that, The process is executed by a first orchestrator, which is either a central orchestrator or a domain orchestrator, and is connected to a service receiver. The service receiver is used to obtain a service request message, determine the 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 method includes: Receive the service request message sent by the service receiver; The service request message is converted into a corresponding orchestration instruction, which is then sent to the controller. The controller receives the orchestration instruction, converts it into service configuration information, and sends the service configuration information to the network device.

9. A network operation management device, characterized in that, Applied to a service acceptor, the service acceptor is connected to multiple system orchestrators, including: The level determination module is used to obtain the business request message and determine the level of the business request message; The first orchestrator determination module is used to determine a first orchestrator from multiple system orchestrators based on the level of the service request message, wherein the first orchestrator is a central orchestrator or a domain orchestrator. 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 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.

10. A network operation management device, characterized in that, The first orchestrator is applied to a first orchestrator, which is either a central orchestrator or a domain orchestrator, and is connected to a service receiver. The service receiver is used to obtain a service request message, determine the 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 device includes: The service request message receiving module is used to receive service request messages sent by the service acceptor; An orchestration instruction sending module is used to convert the service request message into a corresponding orchestration instruction, send the orchestration instruction to the controller, and 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, characterized in that, include: processor; as well as Memory for storing the 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, characterized in that, When the computer program is executed by the processor, it implements the network operation management method according to any one of claims 7 to 8.

Images