An operation and maintenance operation method, system and network device

Abstract

The application discloses an operation and maintenance operation method and system and network equipment. The method is as follows: a first network equipment acquires a first message, the first message indicates a first operation and maintenance operation, the first operation and maintenance operation comprises a second operation and maintenance operation which needs to be executed by a second network equipment, the first network equipment sends a second message to the second network equipment, the second message indicates that the second network equipment executes the second operation and maintenance operation, the second operation and maintenance operation is obtained according to the first operation and maintenance operation and an operation and maintenance template, the operation and maintenance template comprises an operation and maintenance operation identifier and a conversion model, the operation and maintenance operation identifier indicates the first operation and maintenance operation, and the conversion model indicates a conversion relationship between the first operation and maintenance operation and the second operation and maintenance operation, so that different methods do not need to be designed for each operation and maintenance scene, and the conversion between the first operation and maintenance operation and the second operation and maintenance operation can be realized through the conversion model for any scene, thereby providing a general operation and maintenance operation method in a network.

Description

Technical Field

[0001] This application relates to the field of network operation and maintenance, and in particular to an operation and maintenance method, system and network equipment. Background Technology

[0002] Operators can automate network operation and maintenance (O&M) management through an Operation Support System (OSS). However, network O&M management can involve various scenarios. This is because the same network management function can be implemented using various technologies. For example, network connectivity testing can be performed using Ethernet Operation Administration and Maintenance (OAM) commands such as loopback (LB), link trace (LT), and connectivity check (CC). Furthermore, the command lines or interfaces for the same O&M operation differ across network devices in different domains; for instance, network connectivity testing commands differ between the access domain and the transport domain.

[0003] For example, network devices in different network domains or from different vendors may have different input, output, and coordination parameters for the same operational operation command line or interface. If a network includes network devices of multiple network domain types, it will require customizing various operational operation interfaces on the network operation and maintenance system or OSS system. This makes the implementation of operational operations complex and results in low performance. Therefore, a universal operational operation method is urgently needed. Summary of the Invention

[0004] This application provides an operation and maintenance method, system, and network device to improve the operational performance of operation and maintenance.

[0005] Firstly, this application provides an operation and maintenance method. This method can be executed by the network device provided in this application (the network device provided in the third aspect), and the method includes:

[0006] A first network device receives a first message, which indicates a first maintenance operation, including a second maintenance operation that needs to be performed by a second network device. The first network device sends a second message to the second network device, which indicates that the second network device should perform the second maintenance operation. The second maintenance operation is obtained based on the first maintenance operation and a maintenance template. The maintenance template includes a maintenance operation identifier and a conversion model. The maintenance operation identifier indicates the first maintenance operation, and the conversion model indicates the conversion relationship between the first maintenance operation and the second maintenance operation.

[0007] In the above approach, through the operation template, regardless of the scenario, the conversion between the first operation and maintenance operation and the second operation and maintenance operation is realized according to the conversion model and operation and maintenance operation identifier defined in the operation template. Thus, for any operation and maintenance scenario, the conversion between the first operation and maintenance operation and the second operation and maintenance operation can be realized through the conversion model, so that the first network device can send a second message to the second network device to instruct the second network device to perform the second operation and maintenance operation, thereby providing a general operation and maintenance operation method in the network.

[0008] In one possible design, the conversion model includes a parameter model that indicates the conversion relationship between the first input parameter of the first operation and maintenance operation and the second input parameter of the second operation and maintenance operation.

[0009] In the above approach, since the conversion model includes a parameter model, the conversion between the first and second input parameters can be achieved through the parameter model. This allows for pre-conversion when input parameters are required for the second maintenance operation, resulting in higher efficiency of the maintenance operation method.

[0010] In one possible design, the parameter model also indicates the conversion relationship between the first input parameters of the first operation and maintenance operation and the second message.

[0011] In the above approach, through the parameter model, once the first network device obtains the first input parameters, it can send a second message to the second network and device, thereby instructing the second network device and making the operation and maintenance method more applicable.

[0012] In one possible design, the parameter model also indicates the conversion relationship between the first output parameter of the first operation and maintenance operation and the second output parameter of the second operation and maintenance operation.

[0013] In the above approach, since the conversion model includes a parameter model, the conversion between the first output parameter of the first operation and maintenance operation and the second output parameter of the second operation and maintenance operation can be achieved through the parameter model, thereby further improving the efficiency of the operation and maintenance operation method.

[0014] In one possible design, after the first network device sends the second message to the second network device, the process further includes: the first network device obtaining a response message for the second message, the response message including a second output parameter; and the first network device obtaining the first output parameter based on the parameter model and the second output parameter.

[0015] In the above manner, after the first network device obtains the response message of the second message, it obtains the first output parameter according to the parameter model and the second output parameter. Thus, the first output parameter of the first operation and maintenance operation and the second output parameter of the second operation and maintenance operation can be converted through the parameter model. Therefore, after the second operation and maintenance operation is completed, it can be directly converted into the first output parameter of the first operation and maintenance operation, which further improves the efficiency of the operation and maintenance operation method.

[0016] In one possible design, the operation and maintenance template includes operation and maintenance operation modes.

[0017] In the above approach, by introducing operation and maintenance modes into the operation and maintenance template, the operation and maintenance operations are further defined in the template, thereby increasing the accuracy of the operation and maintenance operations.

[0018] In one possible design, the operation and maintenance mode includes synchronous mode or asynchronous mode.

[0019] In the above approach, since the operation and maintenance mode includes synchronous or asynchronous mode, the synchronous or asynchronous mode can be selected according to the characteristics of the operation and maintenance, thereby improving the flexibility of the operation and maintenance.

[0020] In one possible design, after the first network device obtains the first message and before the first network device sends the second message to the second network device, the method further includes: the first network device determining, based on the operation and maintenance strategy, the operation and maintenance operations that the second network device can perform, including the second operation and maintenance operation.

[0021] In the above manner, the first network device determines the second network device's executable operation and maintenance operation based on the operation and maintenance operation strategy, including the second operation and maintenance operation. After determination, it sends a second message to the second network device. In this way, the application scope of the operation and maintenance operation method is controlled by the application-level operation and maintenance operation strategy, thereby improving the flexibility of the operation and maintenance operation method.

[0022] In one possible design, the first network device is a top-level controller, and the second network device is a domain controller or a device within the domain under the first network device.

[0023] When the operation and maintenance method provided in this application is applied to the above scenario, since the operation and maintenance operations of the top-level controller can affect the domain controllers and devices in multiple domains globally, the efficiency of operation and maintenance operations of a wide range of network devices can be enhanced.

[0024] In one possible design, the second message is used to call the first application programming interface (API) of the second network device, and the first API is used by the second network device to perform the second operation and maintenance operation.

[0025] In the above manner, the first API can be called directly through the second message, enabling the second network device to perform the second operation and maintenance operation, thereby improving the efficiency of the operation and maintenance operation.

[0026] Secondly, this application provides an operation and maintenance method. This method can be executed by the network device provided in this application (the network device provided in the fourth aspect), and the method includes:

[0027] The second network device receives a second message from the first network device. The second message instructs the second network device to perform a second maintenance operation. The second maintenance operation is obtained based on a first maintenance operation and a maintenance template. The first maintenance operation is the maintenance operation indicated by the first message received by the first network device. The first maintenance operation includes the second maintenance operation that the second network device needs to perform. The maintenance template includes a maintenance operation identifier and a conversion model. The maintenance operation identifier indicates the first maintenance operation, and the conversion model indicates the conversion relationship between the first maintenance operation and the second maintenance operation.

[0028] The second network device performs the second operation and maintenance operation.

[0029] Optionally, the conversion model includes a parameter model, which indicates the conversion relationship between the first output parameter of the first operation and maintenance operation and the second output parameter of the second operation and maintenance operation. After the second network device executes the second operation and maintenance operation, it further includes:

[0030] The second network device obtains a response message for the second message. The response message includes a second output parameter, which is used by the first network device to obtain a first output parameter based on the parameter model and the second output parameter.

[0031] Thirdly, this application provides a network device, which includes:

[0032] Acquisition module. Used to acquire a first message, the first message indicating a first maintenance operation, the first maintenance operation including a second maintenance operation that needs to be performed by a second network device;

[0033] The sending module is used to send a second message to the second network device. The second message instructs the second network device to perform a second operation and maintenance operation. The second operation and maintenance operation is obtained based on the first operation and maintenance operation and the operation and maintenance template. The operation and maintenance template includes an operation and maintenance operation identifier and a conversion model. The operation and maintenance operation identifier indicates the first operation and maintenance operation, and the conversion model indicates the conversion relationship between the first operation and maintenance operation and the second operation and maintenance operation.

[0034] Optionally, the conversion model includes a parameter model, which indicates the conversion relationship between the first input parameter of the first operation and maintenance operation and the second input parameter of the second operation and maintenance operation.

[0035] Optionally, the parameter model also indicates the conversion relationship between the first input parameters of the first operation and maintenance operation and the second message.

[0036] Optionally, the parameter model also indicates the conversion relationship between the first output parameter of the first operation and maintenance operation and the second output parameter of the second operation and maintenance operation.

[0037] Optionally, after the first network device sends the second message to the second network device, the method further includes: the first network device obtaining a response message for the second message, the response message including a second output parameter; and the first network device obtaining the first output parameter based on the parameter model and the second output parameter.

[0038] Optionally, the operation and maintenance template includes operation and maintenance operation modes.

[0039] Optionally, the operation and maintenance mode includes synchronous mode or asynchronous mode.

[0040] Optionally, the sending module is further configured to: determine, based on the operation and maintenance strategy, that the operation and maintenance operations that the second network device can perform include a second operation and maintenance operation.

[0041] Optionally, the first network device is a top-level controller, and the second network device is a domain controller or a device within the domain under the first network device.

[0042] Optionally, the second message is used to call the first application programming interface (API) of the second network device, and the first API is used by the second network device to perform the second operation and maintenance operation.

[0043] Fourthly, this application provides a network device, which includes:

[0044] The acquisition module is used to acquire a second message from a first network device. The second message instructs the second network device to perform a second operation and maintenance operation. The second operation and maintenance operation is obtained by the first network device based on a first operation and maintenance operation and a maintenance template. The first operation and maintenance operation is the operation and maintenance operation indicated by the first message acquired by the first network device. The first operation and maintenance operation includes a second operation and maintenance operation that needs to be performed by the second network device. The maintenance template includes an operation and maintenance operation identifier and a conversion model. The operation and maintenance operation identifier indicates the first operation and maintenance operation, and the conversion model indicates the conversion relationship between the first operation and maintenance operation and the second operation and maintenance operation.

[0045] The processing module is used to execute the second operation and maintenance operation.

[0046] Optionally, the conversion model includes a parameter model, which indicates the conversion relationship between the first output parameter of the first operation and maintenance operation and the second output parameter of the second operation and maintenance operation. The processing module is further configured to: send a response message of the second message to the first network device, the response message including the second output parameter, which is used by the first network device to obtain the first output parameter according to the parameter model and the second output parameter.

[0047] Fifthly, this application provides an operation and maintenance operating system, which includes:

[0048] The first network device is configured to acquire a first message, the first message indicating a first maintenance operation, the first maintenance operation including a second maintenance operation that needs to be performed by the second network device;

[0049] The first network device is further configured to send a second message to the second network device, the second message instructing the second network device to perform a second operation and maintenance operation, the second operation and maintenance operation being obtained based on the first operation and maintenance operation and maintenance and an operation and maintenance template, the operation and maintenance template including an operation and maintenance operation identifier and a conversion model, the operation and maintenance operation identifier indicating the first operation and maintenance operation, and the conversion model indicating the conversion relationship between the first operation and maintenance operation and the second operation and maintenance operation;

[0050] The second network device is used to obtain a second message from the first network device and to perform the second operation and maintenance operation.

[0051] A sixth aspect provides an electronic device for use as a first network device, the electronic device comprising: a memory including instructions; and a processor, which, when executing the instructions, causes the electronic device to perform the method as described in any of the first aspects above.

[0052] A seventh aspect provides an electronic device for use as a second network device, the electronic device comprising: a memory including instructions; and a processor, which, when executing the instructions, causes the electronic device to perform the method as described in any of the second aspects above.

[0053] Eighthly, a computer-readable storage medium is provided, wherein computer instructions are stored thereon, which, when executed by a processor, cause the processor to perform the method as described in any one of the first or second aspects above.

[0054] Ninth aspect, a computer program product is provided, comprising computer instructions that, when executed, implement the method as described in any one of the first or second aspects above.

[0055] For the beneficial effects of aspects two through nine above, please refer to the beneficial effects of aspect one, which will not be repeated here. Attached Figure Description

[0056] Figure 1 A schematic diagram of a system architecture applicable to operation and maintenance is provided for an embodiment of this application;

[0057] Figure 2 A schematic diagram illustrating a specific architecture applicable to an operation and maintenance scenario in a PING operation between a PON domain and an OTN domain, as provided in an embodiment of this application.

[0058] Figure 3 A schematic diagram of the software architecture of a top-level controller provided in an embodiment of this application;

[0059] Figure 4 A schematic diagram illustrating the implementation process of an operation and maintenance method provided in this application embodiment;

[0060] Figure 5 This application provides a schematic flowchart of the steps of an operation and maintenance method.

[0061] Figure 6 This application provides a schematic diagram illustrating the specific steps of an operation and maintenance method.

[0062] Figure 7 This application provides a schematic diagram of the structure of a network device according to an embodiment of the present application.

[0063] Figure 8 This application provides a schematic diagram of the structure of a network device according to an embodiment of the present application.

[0064] Figure 9 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0065] The technical solutions in the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings.

[0066] The terminology used in the following embodiments is for the purpose of describing specific embodiments only and is not intended to be limiting of this application. As used in the specification and appended claims of this application, the singular expressions “a,” “an,” “the,” “the,” “the,” and “this” are intended to also include expressions such as “one or more,” unless the context clearly indicates otherwise. It should also be understood that in the embodiments of this application, “one or more” means one or more (including two); “and / or” describes the relationship between related objects, indicating that three relationships may exist; for example, A and / or B can represent: A alone, A and B simultaneously, or B alone, where A and B can be singular or plural. The character “ / ” generally indicates that the preceding and following related objects are in an “or” relationship.

[0067] References to "one embodiment" or "some embodiments" as described in this specification mean that one or more embodiments of this application include a specific feature, structure, or characteristic described in connection with that embodiment. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in still other embodiments," etc., appearing in different parts of this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized.

[0068] In this application's embodiments, the term "multiple" refers to two or more. Therefore, in this application's embodiments, "multiple" can also be understood as "at least two." "At least one" can be understood as one or more, such as one, two, or more. For example, "including at least one" means including one, two, or more, and is not limited to which ones are included. For example, "including at least one of A, B, and C" could mean A, B, C; A and B; A and C; B and C; or A and B and C. Similarly, the understanding of descriptions such as "at least one" is similar. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone; A and B existing simultaneously; or B existing alone. Additionally, the character " / ", unless otherwise specified, generally indicates that the preceding and following related objects have an "or" relationship.

[0069] Unless otherwise stated, the ordinal numbers such as "first" and "second" mentioned in the embodiments of this application are used to distinguish multiple objects, and are not used to limit the order, sequence, priority or importance of multiple objects.

[0070] For ease of understanding, the terms involved in the embodiments of this application are explained, and the explanation of these terms is also part of the inventive content of the embodiments of this application.

[0071] Application scenarios

[0072] like Figure 1 The diagram shown is a schematic of the system architecture to which an operation and maintenance method provided in this application can be applied.

[0073] The system architecture may include: an operation support system (OSS), a first network device, and a second network device. Figure 1 The first network device is illustrated using a top-level controller (TC) as an example, and the second network device is illustrated using a domain controller (DC) or an in-domain device (DD). This architecture allows for the selection of devices based on specific scenarios. For example, the architecture can consist of only a TC, DC, and DD; it can also include OSS, TC, DC, and DD; or it can include OSS runtime devices (TC being a component of OSS), DC, and DD. In the above description, "domain" refers to a network area divided according to a certain standard, such as a network area uniformly using a certain technology. In this case, network devices within this network area can achieve efficient interoperability due to the absence of technical barriers.

[0074] In this architecture, the functions of each device can be as follows: OSS is used to deploy network services. For example, OSS can send an OSS operation request to the top-level controller to issue a service deployment request. Network services include network operation and maintenance services, such as connectivity detection services, used to detect connectivity between network devices. The top-level controller obtains the service request to be deployed by acquiring a first message. The first message can come from the service deployment configuration entered by the user in the top-level controller interface. The first message can also come from a service request sent by a third-party system, such as an OSS operation request sent by OSS. The first message can be in the form of a message, such as a northbound interface message sent by OSS. The first message indicates the first operation and maintenance operation; for example, OSS needs the top-level controller to perform a path connectivity detection operation and maintenance operation. In order to perform the above path connectivity detection operation and maintenance operation, the top-level controller needs to issue multiple operation and maintenance operations to multiple domain controllers and / or multiple network devices within the domain under the top-level controller. The above path connectivity detection operation and maintenance operation can only be realized after the above multiple operation and maintenance operations are executed. Therefore, the first operation and maintenance operation includes the operation and maintenance operations that the above domain controllers or devices within the domain need to perform. The first message can be obtained from the OSS operation request sent by the OSS running device, or from the input information of the top-level controller locally. If the operation and maintenance commands or interfaces of the aforementioned domain controllers or devices within the domain are different, the top-level controller needs to deploy operation and maintenance operations to the aforementioned domain controllers or devices within the domain according to the operation and maintenance command or interface. In this embodiment, the top-level controller converts the first operation and maintenance operation into a second message according to the conversion relationship in the operation and maintenance template. The second message can be in message form, and can be called a southbound operation command or a southbound interface message. When the first message includes a first input parameter, the first input parameter is converted into a second input parameter of the operation command for the specified domain. The second message includes the second input parameter. The top-level controller is also used to send the second message to the domain controller or devices within the domain. The second message is used to call the domain controller of the specified domain to call the application programming interface (API) to execute the operation and maintenance operation corresponding to the API. The second message can also be used to issue operation and maintenance operation configurations to the domain controller or devices within the domain based on network operation and maintenance protocols, including Netconf, SNMP, etc., or proprietary protocols, which are not limited here. The domain controller of the designated domain is used to receive the second message and execute the maintenance operations indicated by the second message. The domain controller of the designated domain is also used to send the second message to devices within the designated domain, which then implement service functions based on the second message. In some embodiments, after executing the maintenance operations indicated by the second message, the controller of the designated domain sends a response message to the top-level controller. The top-level controller receives the response message and determines the status of the maintenance operations based on the information carried in the corresponding message.When the response message includes a second output parameter, after the top-level controller receives the response message, the top-level controller converts the second output parameter into the first output parameter according to the operation and maintenance template.

[0075] It should be noted that the functions of each device in the above architecture are only examples. The specific functions of each device can be flexibly adjusted according to the actual application scenario. For example, when processing the first message, it may not involve the first output parameter and the second output parameter. That is, after the device in the domain executes the operation command according to the second input parameter, it does not need to obtain the second output parameter, and the response message does not need to include the second output parameter.

[0076] This architecture enables various operational and maintenance (O&M) operations. Since any O&M operation may involve multiple different scenarios and therefore different messages, this embodiment pre-arranges corresponding O&M templates for any O&M operation and defines the necessary conversion relationships for various scenarios. For example, the O&M template includes the conversion relationship between the first input parameter and the second input parameter, as well as the conversion relationship between the first output parameter and the second output parameter. In this way, regardless of the scenario, the top-level controller and the domain controller can receive the first message through a unified interface and process it step-by-step according to the O&M template and the first message. It should be noted that after the top-level controller converts the first message into a second message, the second message can be directly executed when it reaches devices within the domain, enabling O&M operations to be performed on devices within the domain. In cross-domain scenarios, the conversion by the top-level controller can overcome the technical barriers between different technical domains.

[0077] Furthermore, for the second maintenance operation to be performed, the relevant second network devices can pre-load the second maintenance operation. This allows the second network device (such as a device within the domain) to recognize the pre-loaded operation upon receiving it and then execute it. The services implemented by this architecture can be intra-domain or cross-domain. For intra-domain services, the intra-domain device executing the service function involves only devices within one network area; for cross-domain services, the intra-domain device executing the service function needs to involve devices within multiple network areas. For example, for... Figure 2The illustrated architecture, when performing connectivity testing within a local area network (LAN), requires mounting a second connectivity testing operation within that LAN to ensure its legitimacy. When the OSS (Optical Service Provider) sends a connectivity testing OSS operation request to the top-level controller, the top-level controller executes the OSS operation request, converting the first connectivity testing input parameter in the request into a second connectivity testing input parameter. This second input parameter is then distributed by the domain controller to the devices within the LAN's domain. The second input parameter is contained in the second connectivity testing message, allowing the devices within the LAN to successfully execute the connectivity testing operation command based on the second input parameter. For cross-domain services, such as the packet internet groper (PING) operation between a passive optical network (PON) and an optical transport network (OTN), link tracing can be used. To implement link tracing (LT) technology, it is necessary to mount the respective second maintenance operations (LT operation commands) in both the PON and OTN domains. This ensures that the execution of the second maintenance operations in both the PON and OTN domains is legitimate. When the OSS needs to perform link tracing between the PON and OTN domains, it issues the second maintenance operation (which may include the corresponding second input parameters of LT) to the relevant devices in the PON and OTN domains. The devices in the PON and OTN domains then execute the corresponding link tracing operation commands to achieve the link tracing function between the PON and OTN domains.

[0078] More specifically, Figure 1 or Figure 2 The software architecture diagram inside the mid-to-high-level controller is as follows: Figure 3 As shown, the top-level controller may include the following software modules:

[0079] (1) The business logic processing system includes the following components:

[0080] The business designer binds operation and maintenance templates and business models, and generates operation application policies. These policies control network operation and maintenance operations under different circumstances. The business model encapsulates network operation and maintenance functions, enabling general network operation and maintenance functionalities. The business model can group different application scenarios of a single operation and maintenance operation together.

[0081] The northbound application programming interface (API) is used to receive the first message, such as an OSS operation request, and trigger the operation executor to generate the first maintenance operation according to the operation application policy.

[0082] The business graphical user interface (GUI) is used to receive the first message, such as a user operation request, and trigger the operation executor to generate the first operation and maintenance operation according to the operation application policy.

[0083] Logic processor: Used to perform business logic processing according to the set business logic.

[0084] (2) The operation designer is used to generate operation and maintenance templates according to operation requirements and manage operation and maintenance templates through the operation and maintenance template library.

[0085] (3) Operation and maintenance template library, which is used to maintain operation and maintenance templates. Maintenance includes storing, modifying, querying and adding operation and maintenance templates.

[0086] (4) The operation executor is used to generate the second message according to the operation and maintenance template, and display the input interface and output interface, as well as receive requests and display processing results. It is also used to parse the input parameters of the first message according to the definition of the parameter model in the operation and maintenance template, and pass them to the southbound adapter module to distribute them to each domain controller. It is also used to parse and display the return of each domain controller according to the definition of the output parameter model in the operation and maintenance template.

[0087] (5) Southbound adapter module, used for communication protocol conversion with each domain controller.

[0088] It should be noted that, Figure 3 The software architecture of the top-level controller shown is only an example. The software modules can be flexibly organized and the functions of each software module can be designed. No limitations are imposed here.

[0089] The following is combined with Figure 4 This document describes in detail the implementation process of an operation and maintenance method provided in an embodiment of this application. For example... Figure 4 As shown, the specific steps of this implementation process are as follows:

[0090] Step 401: Arrange the operation and maintenance templates for operation and maintenance.

[0091] Step 402: Bind the operation and maintenance template to the business object and set the operation application policy.

[0092] Step 403: Perform maintenance operations.

[0093] In step 401, for example, the operation and maintenance operation is a PING operation from the PON device to the OTN device, which can be implemented through LT technology.

[0094] The operation and maintenance template includes: operation and maintenance operation identifier, operation application policy, and basic operation information.

[0095] The operation and maintenance (O&M) identifier is used to indicate O&M operations and also identifies an O&M template. The O&M operation identifier includes, but is not limited to, the O&M operation name and the O&M operation sequence number.

[0096] Operation application policies refer to the applicable scenarios for operations. These policies can include operation and maintenance (O&M) operation modes, which refer to the execution flow patterns of O&M operations. These include synchronous, asynchronous, and reporting modes. In synchronous mode, the network device performing the O&M operation must wait for the response message (response message) of the operation message (second message) until it receives the response message before it can perform other O&M operations. In asynchronous mode, the network device performing the O&M operation can wait for the response message of the operation message while asynchronously performing other O&M operations. In reporting mode, the network device performing the operation directly executes the O&M operation message without forwarding it or waiting for a response message. Operation application policies can also include business objects, which specify the devices for which the O&M template is effective. Furthermore, operation application policies can include information such as device type and O&M operation version, indicating the applicable scenarios for the operation.

[0097] The basic operation information refers to the basic model of the operation, which may include the operation name and the conversion model. The conversion model indicates the conversion relationship between the first and second operation and maintenance operations. The conversion model may include a parameter model, which may include an input parameter model and an output parameter model. The input parameter model includes a southbound model and a northbound model defining the input parameters of the operation. The northbound model of the input parameters is the message body model of the input parameters. The southbound model of the input parameters indicates the conversion relationship between the first input parameter of the first operation and maintenance operation and the second message, such as a model of input parameters to a specified message body of an external system. For example, in the top-level controller, the first input parameter received by the top-level controller can be converted into a second input parameter that satisfies the domain controller based on a mapping file, which is the output message of the top-level controller. The format of the output message satisfies the specified format required by the domain controller's input message (i.e., the format of the second input parameter). Correspondingly, the output parameter model is similar to the input parameter model. The output parameter model can refer to the description of the input parameter model. The output parameter model indicates the conversion relationship between the first output parameter of the first operation and maintenance operation and the second output parameter of the second operation and maintenance operation, which will not be elaborated further here. It should be noted that the input parameter model or output parameter model is not necessarily required. An operation and maintenance template may only have an input parameter model but no output parameter model, and some operation and maintenance templates may only have an output parameter model but no input parameter model, or both, or neither. This is not a limitation; the specific design depends on the characteristics of the operation and maintenance. Both the input and output parameter models can flexibly select specific data definition formats, such as JSONSchema, or mapping files, which can map input operation messages to second input parameters in a format specified by the domain controller. Mapping files can be implemented using FreeMarker extended syntax. The operation and maintenance templates can be designed through an online system, stored in an operation and maintenance template library, validated, and then published.

[0098] Specifically, taking the PING operation from a PON device to an OTN device as an example, both the PON and OTN devices need to define two separate operation and maintenance templates. Different operation and maintenance strategies are used to control the application of different templates across different technical fields. Taking the PON device side as an example, the operation name is PING, and both OSS and the GUI perceive the PING operation of the general interface. The operation and maintenance template can be defined using a JSON file, and its structure can be as follows:

[0099] Template identifier (id), operation application strategy (commandRestraint), and basic operation information (commandBasciInfo); the basic operation information includes: operation name (operationName), input parameter model (commandConfigure), and output parameter model (commandStatus).

[0100] The following is an example of an operations and maintenance template:

[0101]

[0102]

[0103] It should be noted that in the structure of the above template examples, some variables may have multiple layers. The content within "{}" and "[]" after a variable represents the specific definition of a variable. Variables can also be nested within each other. That is, variables described by "{}" and "[]" can contain variables described by "{}" and "[]", such as "rootRestraints" and "applyObjects" within "commandRestraints". Furthermore, the scope of the value of each variable defined within "{}" and "[]" is only within that "{}" and "[]". For example, the scope of "value" in "commandConfigure" is only within "commandConfigure", and the scope of "value" in "commandStatus" is only within "commandStatus". All Chinese characters in the above template examples are code comments.

[0104] As can be seen from the above operation and maintenance template example, id is the template identifier of the operation and maintenance template. In the example, the value of id is "NCEFANEthernetOamLTCommandTemplate ID"; description is the description of the operation and maintenance template, used to describe the business functions implemented by the operation and maintenance template; operStatus is the deployment status of the operation and maintenance template, which can be deployed or uneployed; commandRestraint is the operation application policy, where rootRestraints defines the application scenarios in which the operation and maintenance operation can be applied. "scenario":"OTN_P2MP" indicates that the operation and maintenance template is applied to the OTN domain and the point-to-multiple-point (P2MP) technology, and "subScenario":"TP" indicates Termination The `Point` directive describes whether this operation is port-level. `vendors` specifies the manufacturers, device types, and versions for which the operation can run. `processMode` specifies the operation mode; in the example, "syncMode" indicates synchronous mode. `applyObjects` specifies the application objects for the operation; `objectType` specifies the object type. `COMPOSED-AC` indicates a combined service access point, representing an end-to-end service access point. `validScopes` specifies detailed operation application constraints; `validScopes` is a list of name-value pairs, where "name" is the parameter name, "workingLayer" indicates the working layer (the layer at which this operation takes effect), and "value" is the parameter value. `LR_Ethernet` indicates that Ethernet services are allowed to start. If the access point's operating mode is not Ethernet, this command is not allowed to be initiated; commandBasicinfo contains basic operation information, and operationName is a generic operation name. For example, the manufacturer's connectivity detection operation is an Ethernet OAM LT operation, but externally it can be uniformly encapsulated as PING (transmission, access, and data communication connection) through the operation name (operationName), in which case operationName can be "PING"; commandConfigure is the input parameter model. The "name" in commandConfigure points to the name of a specific input parameter model, which is implemented through the input parameter definition component and component mapping file. The "value" in commandConfigure is the unique identifier ID corresponding to the input parameter template. Specifically, an example of defining the component structure can be as follows:

[0105] Defining a component structure can include two parts: a component template and a component mapping file. The component template describes the input parameters and constraints using JsonSchema.

[0106] The specific example of the component template is as follows:

[0107]

[0108] Component mapping file: This translates the first message (northbound interface message) into the second message (southbound interface message) input to the domain controller. An example snippet is shown below:

[0109]

[0110]

[0111] The input parameter model is defined using `commandConfigure`, and the output parameter model is defined using `commandStatus`. The northbound interface component name points to a northbound interface component and mapping file defined by a JSONSchema. This JSONSchema defines the input parameters required for the PING operation, such as the source maintenance entity group end point (MEP) identifier and Time To Live (TTL) values. The "name" and "value" in the output parameter model (`commandStatus`) are similar to those in `commandConfigure`, and can be found in the description of the input parameter model.

[0112] By orchestrating operation and maintenance (O&M) templates, any O&M operation can be abstracted into an extensible, general O&M template. Real-time orchestration of O&M templates significantly reduces the development workload for O&M operations. This is because O&M templates abstract the scenarios for each situation. The templates automatically generate interfaces, input parameters, output parameters, and different operation modes for different scenarios, eliminating the need for repetitive orchestration for each scenario, thus reducing workload. Operation modes can be abstracted into synchronous and asynchronous interfaces for general operations. Application logic obtains the process mode from the O&M template, calls the unified synchronous or asynchronous interface, and uses the mapping file of the bound business object to convert the first input parameter into the second input parameter and the second output parameter into the first output parameter. By associating the O&M template with the operation application strategy, a business-level abstract interface is provided to OSS.

[0113] In step 402, the service object may include the access points (e.g., two access points) that implement the service connection and the network path between the access points. If the operation and maintenance template is directly bound to the service object, then since the operation and maintenance of a service requires the cooperation of all access points, the operation and maintenance will be decomposed into operation commands on each access point, and each access point needs to execute the operation and maintenance. For example, each access point may specifically be a designated PON device in the PON domain and a designated OTN device in the OTN domain. The operation and maintenance is a node activation operation, which involves registering a node in a designated network area. In this example, this means the designated PON device and the designated OTN device. When the node activation operation is executed, the corresponding node activation commands need to be executed synchronously on the designated PON device and the designated OTN device respectively.

[0114] The business object can also be just an access point, in which case the operation and maintenance operation can be initiated from only one access point without needing to be executed synchronously. For example, if the operation and maintenance template is bound to a specified PON device and a specified OTN device, and the operation and maintenance operation is a latency detection operation, then the latency detection command (southbound operation command) can be initiated from the specified PON device, and the specified PON device can wait for the specified OTN device to respond; alternatively, the latency detection command (southbound operation command) can be initiated from the specified OTN device, and the specified OTN device can wait for the specified PON device to respond.

[0115] It should be noted that the specific execution of the above-mentioned maintenance operations in different situations is constrained by the maintenance operation strategy. Before the top-level controller converts the first message into the second message, it is also necessary to determine whether the OTN and PON devices have enabled the corresponding maintenance operations through the maintenance operation strategy. The maintenance operation strategy of the maintenance template also includes service objects, which can specify whether one end or multiple ends are affected. The maintenance operation strategy can also specify the type of device affected, the effective version of the operation command, etc., which can be flexibly designed according to the specific maintenance operation. Among them, for services that are divided into source and destination segments, one-end effect can be applied to both the source and destination ends, and multi-end effect can be applied to both ends.

[0116] In the example of a PON device pinging an OTN device, the operation and maintenance strategy can be defined using a JSON file. Specifically, the operation and maintenance strategy can be as follows:

[0117] Among them, CommandTemplate is the operation and maintenance template identifier, used to bind the operation and maintenance template name; CommandOperateName is the name of the operation command displayed corresponding to the operation and maintenance operation; GUIHookPoint is the interface hook node, used to specify the business object to which the operation and maintenance operation is attached; ValidObjectCfg is the operation activation policy, specifying the source end to be effective; BindingBusinessObjects is the application object, used to control which business objects the operation and maintenance template is effective on, and fdName is specifically the name of the bound business object.

[0118] The following is an example of an operation and maintenance strategy, which may include the following fields:

[0119]

[0120] The following describes in detail the process of step 403 when the first network device is used as the top-level controller and the second network device is used as the domain controller, respectively, in a scenario where the top-level controller controls any specified domain to perform operation and maintenance operations. The specific steps of step 403 can be found in [reference needed]. Figure 5 This is a flowchart illustrating the specific procedures for performing maintenance operations.

[0121] Step 501: The top-level controller receives the first message.

[0122] Specifically, the first operation and maintenance operation can be a single-domain operation or a cross-domain operation. The first message indicates the first operation and maintenance operation. The first operation and maintenance operation includes a second operation and maintenance operation that needs to be performed by the second network device. The second operation and maintenance operation is obtained based on the first operation and maintenance operation and maintenance template. The second network device can be instructed by the second message to perform the second operation and maintenance operation. The operation and maintenance template includes an operation and maintenance operation identifier and a conversion model. The operation and maintenance operation identifier indicates the first operation and maintenance operation, and the conversion model indicates the conversion relationship between the first operation and maintenance operation and the second operation and maintenance operation.

[0123] It should be noted that the first message may include the first input parameter. If the operation and maintenance template corresponding to the operation and maintenance operation includes an input parameter model, then the first input parameter needs to be obtained according to the specifications in the input parameter model. When obtaining the first input parameter, in step 501, the client's operation interface can be generated according to the input parameter model in the operation and maintenance template of the operation and maintenance operation. Based on the input information of the client's operation interface, the first input parameter of the operation and maintenance operation is determined, which can be as follows: Figure 6 As shown, based on the JsonSchema definition of the input parameters, a Json operation interface is generated, and the input information of the Json operation interface is obtained. Alternatively, the top-level controller can also extract the first input parameters of the operation and maintenance operation from the OSS operation request sent by the OSS device based on the input parameter model; step 501 can be achieved through... Figure 3 The operation executor implementation in the [system / process].

[0124] Step 502: The top-level controller determines whether the maintenance operations that the domain controller can perform include the second maintenance operation based on the maintenance operation policy.

[0125] If yes, proceed to step 503; otherwise, terminate the process directly.

[0126] Step 503: The top-level controller generates a second message based on the first message and determines the operation mode in the operation and maintenance template.

[0127] For example, if the first message is an OSS operation request, it can be directly converted into a JSON message based on the input parameter model. The JSON message can be as follows:

[0128] CommonCommand

[0129] operationName: ping

[0130] commandConfigure attach node

[0131] |--name:PONEthernetOamLTCfg

[0132] |--value: "{{\"remoteMepId\":2,\"ttl\":62}}"

[0133] Where commandConfigure is the input parameter model, PONEthernetOamLTCfg represents it, remoteMepId represents the ID of the remote MEP point, and TTL represents the time to live, which is 62 milliseconds (ms).

[0134] Specifically, when the pending operation request includes a first input parameter, the top-level controller can convert the first input parameter into a second input parameter based on the mapping file of the input parameter model in the operation and maintenance template, and generate a southbound interface message based on the second input parameter. The format of the second input parameter in the southbound interface message is the specified format required by the domain controller for input parameters; step 502 can be achieved through... Figure 3 The operation executor implementation in the [system / process].

[0135] If the operation mode is synchronous, proceed to step 504; if the operation mode is asynchronous, proceed to step 505; step 503 can be performed via... Figure 3 The logic processor implementation in [the system / processor].

[0136] Step 504: The top-level controller sends the southbound interface message to the designated domain controller and waits for the response message from the southbound interface message.

[0137] If a response message is obtained, proceed to step 507.

[0138] Step 505: The top-level controller sends the southbound interface message to the designated domain controller and obtains the task identifier.

[0139] This task identifier is used to mark the task of the domain controller processing southbound interface messages.

[0140] Step 506: The top-level controller waits for the response message from the southbound interface based on the task identifier.

[0141] If a response message is received, proceed to step 507. It should be noted that while step 506 is being executed, the top-level controller can also perform other operations in parallel.

[0142] Step 507: The top-level controller performs further processing based on the response message.

[0143] If the operation and maintenance template includes an output parameter model, then the devices within the domain will obtain the second output parameter. If the operation and maintenance template includes an input parameter model, the devices within the domain can obtain the second output parameter based on the second input parameter. In this case, the response message will include the second output parameter. Then, based on the mapping file of the output parameter model, the top-level controller can convert the second output parameter output by the domain controller into the first output parameter for northbound communication. The format of the first output parameter conforms to the specified format required by OSS, so that the first output parameter can be returned to the OSS or the client's operation interface.

[0144] The following describes the process with a more concrete example. For instance, an operation might be a PON device pinging an OTN device. This ping operation can be implemented using the LT command. The PING operation template includes an input parameter model and an output parameter model. Specific steps can be described as follows: Figure 6 As shown, the details are as follows:

[0145] Step 601: The top-level controller obtains the northbound interface message of the PING operation.

[0146] For example, the top-level controller can generate a client JSON view interface based on the JSON schema definition of the input parameter model of the PING operation. The input information from the client's operation interface is directly converted into a northbound interface message in JSON format, and the northbound interface message includes the first input parameter.

[0147] Step 602: The top-level controller converts the northbound interface message into a southbound interface message.

[0148] For example, the top-level controller converts the first input parameter into a second input parameter through the mapping file of the input parameter model. The second input parameter is in the format required by the domain where the PON device is located, and the second input parameter is included in the southbound interface message.

[0149] Step 603: The top-level controller determines that the operation mode defined in the operation and maintenance template of the PING operation is the synchronous mode.

[0150] It should be noted that if the operation mode defined for the PING operation is synchronous, then step 604 will be executed. If the defined operation mode is not synchronous, there may be other branches.

[0151] Step 604: The top-level controller sends the converted southbound interface message to the domain controller where the PON device is located through the southbound adapter module, and waits to receive the response message.

[0152] Step 605: The domain controller sends the southbound interface message to the PON device.

[0153] It should be noted that in this example, it was pre-determined that the PING operation was an operation and maintenance operation on the PON device, so step 605 was executed. However, in some other cases, the domain controller may also determine that the operation and maintenance operation corresponding to the southbound interface message is an operation and maintenance operation on the domain controller, so the southbound interface message is executed directly to realize the operation and maintenance operation on the domain controller.

[0154] Step 606: The PON device executes the southbound interface message and obtains the second output parameter based on the second input parameter.

[0155] The second output parameter is included in the response message.

[0156] Step 607: The PON device sends a response message to the domain controller.

[0157] Step 608: The domain controller sends a response message to the top-level controller.

[0158] Step 609: The top-level controller converts the second output parameter into the first output parameter according to the mapping file of the output parameter model of the PING operation.

[0159] After step 609, the top-level controller can convert the first output parameter into OSS or output it in the client's operation interface.

[0160] The above method only requires updating the operation and maintenance template to achieve online expansion of operation and maintenance functions, without reloading the program package, thus achieving version-free release. This method implements a technology for building an ecosystem. OSS and clients do not need to understand complex processing logic; they only need to arrange the operation and maintenance template according to this core framework to obtain various operation and maintenance functions for cross-domain businesses. This solves the problem of end-to-end operation and maintenance functions across technology domains, quickly adapts to the special requirements of different technology domains, and addresses the current shortcomings in cross-technology domain end-to-end operation and maintenance.

[0161] like Figure 7 As shown, this application provides a network device, which includes:

[0162] Acquisition module 701. Used to acquire a first message, the first message indicating a first maintenance operation, the first maintenance operation including a second maintenance operation that needs to be performed by a second network device;

[0163] The sending module 702 is used to send a second message to the second network device. The second message instructs the second network device to perform a second operation and maintenance operation. The second operation and maintenance operation is obtained based on the first operation and maintenance operation and the operation and maintenance template. The operation and maintenance template includes an operation and maintenance operation identifier and a conversion model. The operation and maintenance operation identifier indicates the first operation and maintenance operation, and the conversion model indicates the conversion relationship between the first operation and maintenance operation and the second operation and maintenance operation.

[0164] Optionally, the conversion model includes a parameter model, which indicates the conversion relationship between the first input parameter of the first operation and maintenance operation and the second input parameter of the second operation and maintenance operation.

[0165] Optionally, the parameter model also indicates the conversion relationship between the first input parameters of the first operation and maintenance operation and the second message.

[0166] Optionally, the parameter model also indicates the conversion relationship between the first output parameter of the first operation and maintenance operation and the second output parameter of the second operation and maintenance operation.

[0167] Optionally, after the first network device sends the second message to the second network device, the method further includes: the first network device obtaining a response message for the second message, the response message including a second output parameter; and the first network device obtaining the first output parameter based on the parameter model and the second output parameter.

[0168] Optionally, the operation and maintenance template includes operation and maintenance operation modes.

[0169] Optionally, the operation and maintenance mode includes synchronous mode or asynchronous mode.

[0170] Optionally, the sending module 702 is further configured to: determine, according to the operation and maintenance strategy, that the operation and maintenance operations that the second network device can perform include the second operation and maintenance operation.

[0171] Optionally, the first network device is a top-level controller, and the second network device is a domain controller or a device within the domain under the first network device.

[0172] Optionally, the second message is used to call the first application programming interface (API) of the second network device, and the first API is used by the second network device to perform the second operation and maintenance operation.

[0173] like Figure 8 As shown, this application provides a network device, which includes:

[0174] The acquisition module 801 is used to acquire a second message from a first network device. The second message instructs the second network device to perform a second operation and maintenance operation. The second operation and maintenance operation is obtained by the first network device based on a first operation and maintenance operation and a maintenance template. The first operation and maintenance operation is the operation and maintenance operation indicated by the first message acquired by the first network device. The first operation and maintenance operation includes a second operation and maintenance operation that needs to be performed by the second network device. The maintenance template includes an operation and maintenance operation identifier and a conversion model. The operation and maintenance operation identifier indicates the first operation and maintenance operation, and the conversion model indicates the conversion relationship between the first operation and maintenance operation and the second operation and maintenance operation.

[0175] The processing module 802 is used to execute the second operation and maintenance operation.

[0176] Optionally, the conversion model includes a parameter model, which indicates the conversion relationship between the first output parameter of the first operation and maintenance operation and the second output parameter of the second operation and maintenance operation. The processing module 802 is further configured to: send a response message of the second message to the first network device, the response message including the second output parameter, the second output parameter being used by the first network device to obtain the first output parameter according to the parameter model and the second output parameter.

[0177] This application also provides an electronic device that can have the following features: Figure 9 The structure shown indicates that the electronic device can be a computer device or a chip or chip system that can support the computer device in implementing the operation and maintenance methods provided in the embodiments of this application. The electronic device can be used as a first network device or as a second network device.

[0178] like Figure 9The illustrated electronic device may include at least one processor 901, which is coupled to a memory to read and execute instructions in the memory to implement the steps of the operation and maintenance method provided in this embodiment. Optionally, the electronic device may also include a communication interface 902 for supporting the electronic device in receiving or sending signaling or data. The communication interface 902 in the electronic device can be used to interact with other electronic devices. The processor 901 can be used to implement the steps of the operation and maintenance method provided in this embodiment. Optionally, the electronic device may also include a memory 903 storing computer instructions. The memory 903 may be coupled to the processor 901 and / or the communication interface 902 to support the processor 901 in calling the computer instructions in the memory 903 to implement the steps of the operation and maintenance method provided in this embodiment. In addition, the memory 903 may also be used to store data involved in the method embodiments of this application, such as data and instructions necessary to support the interaction of the communication interface 902, and / or configuration information necessary for the electronic device to execute the method described in this embodiment.

[0179] This application also provides a computer-readable storage medium storing computer instructions. When these computer instructions are invoked and executed by a computer, the computer can perform the methods involved in any possible design of the above-described method embodiments. In this application, the computer-readable storage medium is not limited; for example, it can be RAM (random-access memory), ROM (read-only memory), etc.

[0180] This application also provides a chip that may include a processor and an interface circuit for performing the methods involved in any of the above-described method embodiments and any possible implementations of the method embodiments, wherein "coupling" refers to two components being directly or indirectly combined with each other, and such combination may be fixed or movable.

[0181] This application also provides a computer program product, including computer instructions, which, when executed, can implement the methods involved in any possible design of the above method embodiments.

[0182] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented in software, implementation can be entirely or partially in the form of computer instructions. When the computer instructions are loaded and executed on a computer, the processes or functions described in the embodiments of the present invention are generated entirely or partially. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, optical fiber) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid-state disk (SSD)).

[0183] The steps of the methods or algorithms described in the embodiments of this application can be directly embedded in hardware, software units executed by a processor, or a combination of both. The software units can be stored in RAM, flash memory, ROM, EPROM, EEPROM, registers, hard disks, removable disks, CD-ROMs, or any other form of storage medium in the art. Exemplarily, the storage medium can be connected to the processor so that the processor can read information from and write information to the storage medium. Optionally, the storage medium can also be integrated into the processor. The processor and storage medium can be housed in an ASIC, which can be housed in a terminal device. Optionally, the processor and storage medium can also be housed in different components within the terminal device.

[0184] These computer instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0185] Although the invention has been described in conjunction with specific features and embodiments, it is obvious that various modifications and combinations can be made therein without departing from the scope of the invention. Accordingly, this specification and drawings are merely exemplary descriptions of the invention as defined by the appended claims, and are considered to cover any and all modifications, variations, combinations, or equivalents within the scope of the invention. Clearly, those skilled in the art can make various alterations and modifications to the invention without departing from its spirit and scope. Thus, if such modifications and modifications of the invention fall within the scope of the claims and their equivalents, the invention is also intended to include such modifications and modifications.

Claims

1. A method for operation and maintenance, characterized in that, include: A first network device receives a first message, the first message indicating a first operation and maintenance operation, the first operation and maintenance operation including a second operation and maintenance operation that needs to be performed by a second network device; the first network device is a top-level controller, and the second network device is a domain controller or a device within the domain under the first network device. The first network device sends a second message to the second network device, the second message instructing the second network device to perform a second operation and maintenance operation. The second operation and maintenance operation is obtained based on the first operation and maintenance operation and maintenance and an operation and maintenance template. The operation and maintenance template includes an operation and maintenance operation identifier and a conversion model. The operation and maintenance operation identifier indicates the first operation and maintenance operation, and the conversion model indicates the conversion relationship between the first operation and maintenance operation and the second operation and maintenance operation. The second message is used to call the first application programming interface (API) of the second network device. The first API is used by the second network device to perform the second operation and maintenance operation.

2. The method as described in claim 1, characterized in that, The conversion model includes a parameter model, which indicates the conversion relationship between the first input parameter of the first operation and maintenance operation and the second input parameter of the second operation and maintenance operation.

3. The method as described in claim 2, characterized in that, The parameter model also indicates the conversion relationship between the first input parameter of the first operation and maintenance operation and the second message.

4. The method according to any one of claims 2 to 3, characterized in that, The parameter model also indicates the conversion relationship between the first output parameter of the first operation and maintenance operation and the second output parameter of the second operation and maintenance operation.

5. The method as described in claim 4, characterized in that, After the first network device sends the second message to the second network device, it also includes: The first network device obtains a response message to the second message, the response message including the second output parameter; The first network device obtains the first output parameter based on the parameter model and the second output parameter.

6. The method according to any one of claims 1 to 5, characterized in that, The operation and maintenance template includes operation and maintenance modes.

7. The method as described in claim 6, characterized in that, The operation and maintenance modes include synchronous mode or asynchronous mode.

8. The method according to any one of claims 1 to 7, characterized in that, After the first network device receives the first message, and before the first network device sends the second message to the second network device, the process further includes: The first network device determines the second network device's executable operation and maintenance operation based on the operation and maintenance operation strategy, including the second operation and maintenance operation.

9. A method for operation and maintenance, characterized in that, include: The second network device receives a second message from the first network device. This second message instructs the second network device to perform a second maintenance operation. This second maintenance operation is obtained by the first network device based on a first maintenance operation and a maintenance template. The first maintenance operation is the operation indicated by the first message received by the first network device. This first maintenance operation includes a second maintenance operation that the second network device needs to perform. The maintenance template includes a maintenance operation identifier and a conversion model. The maintenance operation identifier indicates the first maintenance operation, and the conversion model indicates the conversion relationship between the first and second maintenance operations. The first network device is a top-level controller, and the second network device is a domain controller or a device within a domain under the first network device. The second message is used to call the second network device's first application programming interface (API), which is used by the second network device to perform the second maintenance operation. The second network device calls the first API of the second network device to perform the second operation and maintenance operation.

10. The method as described in claim 9, characterized in that, The conversion model includes a parameter model, which indicates the conversion relationship between the first output parameter of the first operation and maintenance operation and the second output parameter of the second operation and maintenance operation. After the second network device executes the second operation and maintenance operation, it further includes: The second network device sends a response message to the first network device for the second message. The response message includes the second output parameter, which is used by the first network device to obtain the first output parameter based on the parameter model and the second output parameter.

11. A first network device, characterized in that, include: The acquisition module is used to acquire a first message, which indicates a first operation and maintenance operation, including a second operation and maintenance operation that needs to be performed by a second network device; the first network device is a top-level controller, and the second network device is a domain controller or a device within the domain under the first network device; The sending module is used to send a second message to the second network device. The second message instructs the second network device to perform a second operation and maintenance operation. The second operation and maintenance operation is obtained based on the first operation and maintenance operation and a maintenance template. The maintenance template includes an operation and maintenance operation identifier and a conversion model. The operation and maintenance operation identifier indicates the first operation and maintenance operation, and the conversion model indicates the conversion relationship between the first operation and maintenance operation and the second operation and maintenance operation. The second message is used to call the first application programming interface (API) of the second network device. The first API is used by the second network device to perform the second operation and maintenance operation.

12. A second network device, characterized in that, include: The acquisition module is used to acquire a second message from a first network device. The second message instructs the second network device to perform a second maintenance operation. The second maintenance operation is obtained by the first network device based on a first maintenance operation and a maintenance template. The first maintenance operation is the maintenance operation indicated by the first message acquired by the first network device. The first maintenance operation includes a second maintenance operation that the second network device needs to perform. The maintenance template includes a maintenance operation identifier and a conversion model. The maintenance operation identifier indicates the first maintenance operation, and the conversion model indicates the conversion relationship between the first maintenance operation and the second maintenance operation. The first network device is a top-level controller, and the second network device is a domain controller or a device within a domain under the first network device. The second message is used to call a first application programming interface (API) of the second network device. The first API is used by the second network device to perform the second maintenance operation. The processing module is used to call the first API of the second network device to execute the second operation and maintenance operation.

13. An operation and maintenance operating system, characterized in that, include: First network device and second network device; The first network device is configured to acquire a first message, the first message indicating a first operation and maintenance operation, the first operation and maintenance operation including a second operation and maintenance operation that needs to be performed by the second network device; the first network device is a top-level controller, and the second network device is a domain controller or a device within a domain under the first network device; The first network device is further configured to send a second message to the second network device, the second message instructing the second network device to perform a second operation and maintenance operation, the second operation and maintenance operation being obtained based on the first operation and maintenance operation and maintenance and an operation and maintenance template, the operation and maintenance template including an operation and maintenance operation identifier and a conversion model, the operation and maintenance operation identifier indicating the first operation and maintenance operation, and the conversion model indicating the conversion relationship between the first operation and maintenance operation and the second operation and maintenance operation; the second message is configured to call a first application programming interface (API) of the second network device, the first API being used by the second network device to perform the second operation and maintenance operation; The second network device is used to obtain a second message from the first network device and to call the first API of the second network device to perform the second operation and maintenance operation.

14. An electronic device used as a first network device, characterized in that, The electronic device includes: Memory, including instructions; A processor, when executing the instructions, causes the electronic device to perform the method of any one of claims 1-8.

15. An electronic device used as a second network device, characterized in that, The electronic device includes: Memory, including instructions; A processor, when executing the instructions, causes the electronic device to implement the method of claim 9 or 10.

16. A computer-readable storage medium, characterized in that, It stores computer instructions that, when executed by a processor, implement the method as described in any one of claims 1-10.

17. A computer program product, characterized in that, Includes computer instructions that, when executed, implement the method as described in any one of claims 1-10.

Images