CN116056120A - Operation and maintenance operation method, system and network equipment - Google Patents

Operation and maintenance operation method, system and network equipment Download PDF

Info

Publication number
CN116056120A
CN116056120A CN202111261486.0A CN202111261486A CN116056120A CN 116056120 A CN116056120 A CN 116056120A CN 202111261486 A CN202111261486 A CN 202111261486A CN 116056120 A CN116056120 A CN 116056120A
Authority
CN
China
Prior art keywords
network device
message
maintenance
indicates
model
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202111261486.0A
Other languages
Chinese (zh)
Inventor
张丽雅
杜佐钱
宋玮
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Huawei Technologies Co Ltd
Original Assignee
Huawei Technologies Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co Ltd filed Critical Huawei Technologies Co Ltd
Priority to CN202111261486.0A priority Critical patent/CN116056120A/en
Priority to PCT/CN2022/123609 priority patent/WO2023071717A1/en
Publication of CN116056120A publication Critical patent/CN116056120A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04JMULTIPLEX COMMUNICATION
    • H04J3/00Time-division multiplex systems
    • H04J3/16Time-division multiplex systems in which the time allocation to individual channels within a transmission cycle is variable, e.g. to accommodate varying complexity of signals, to vary number of channels transmitted
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04JMULTIPLEX COMMUNICATION
    • H04J3/00Time-division multiplex systems
    • H04J3/16Time-division multiplex systems in which the time allocation to individual channels within a transmission cycle is variable, e.g. to accommodate varying complexity of signals, to vary number of channels transmitted
    • H04J3/1605Fixed allocated frame structures
    • H04J3/1652Optical Transport Network [OTN]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/14Network analysis or design
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04LTRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/14Network analysis or design
    • H04L41/145Network analysis or design involving simulating, designing, planning or modelling of a network
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W24/00Supervisory, monitoring or testing arrangements
    • H04W24/04Arrangements for maintaining operational condition
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04WWIRELESS COMMUNICATION NETWORKS
    • H04W24/00Supervisory, monitoring or testing arrangements
    • H04W24/06Testing, supervising or monitoring using simulated traffic

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

The invention discloses an operation and maintenance method, an operation and maintenance system and network equipment. The method comprises the following steps: the first network equipment acquires a first message, the first message indicates a first operation, the first operation comprises a second operation which needs to be executed by the second network equipment, the first network equipment sends the second message to the second network equipment, the second message indicates the second network equipment to execute the second operation, the second operation is obtained according to the first operation and an operation template, the operation template comprises an operation identifier and a conversion model, the operation identifier indicates the first operation, the conversion model indicates the conversion relation between the first operation and the second operation, and therefore, no different methods are needed to be designed for each operation scene, and conversion between the first operation and the second operation can be achieved through the conversion model for any scene, so that a general operation method in a network is provided.

Description

Operation and maintenance operation method, system and network equipment
Technical Field
The present disclosure relates to the field of network operation and maintenance, and in particular, to an operation and maintenance method, system and network device.
Background
The operator may automatically conduct network operations and maintenance management through the operation support system (operation support system, OSS). However, network operation management may present a variety of scenarios. This is because the operation and maintenance of the same network management function can be implemented by various technologies, such as a network connectivity test operation, a Loop Back (LB) command, a Link Trace (LT) command, and a connectivity monitoring (connectivity check, CC) command, which are implemented by an ethernet (OAM) operation management maintenance (operation administration and maintenance, OAM), and the same operation and maintenance operation may be implemented by different technologies, where there is a difference between a corresponding command line or a docking interface on a network device in different domains, such as a network connectivity test command of an access domain and a network connectivity test command of a transport domain.
For example, network devices in different network domains or from different vendors may have different input parameters, output parameters, and collaboration parameters for a command line or interface of the same operation and maintenance operation. If a network includes multiple network domain types of network devices, this results in the need to customize the interfaces of multiple operation and maintenance operations on the network operation system or OSS system. This results in a more complex implementation of the operation and maintenance operations, which operate in a lower manner. Therefore, a general operation method is needed.
Disclosure of Invention
The application provides an operation and maintenance operation method, an operation and maintenance system and network equipment, which are used for improving the operation performance of operation and maintenance operation.
In a first aspect, the present application provides a method of operation and maintenance. The method may be performed by a network device provided by the present application (network device provided by the third aspect), the method comprising:
the method comprises the steps that first network equipment obtains a first message, wherein the first message indicates a first operation and maintenance operation, and the first operation and maintenance operation comprises a second operation and maintenance operation which needs to be executed by second network equipment; the first network device sends a second message to the second network device, the second message indicates the second network device to execute the second operation, the second operation is obtained according to the first operation and an operation template, the operation template comprises an operation identifier and a conversion model, the operation identifier indicates the first operation, and the conversion model indicates a conversion relation between the first operation and the second operation.
In the above manner, the conversion between the first operation and the second operation is realized according to the conversion model and the operation identifier defined in the operation template through the operation template, so that the conversion between the first operation and the second operation can be realized through the conversion model no matter which operation scene is, the first network device can send a second message to the second network device, and the second network device is instructed to execute the second operation through the second message, thereby providing a general operation method in the network.
In one possible design, the transformation model includes a parametric model that indicates a transformation relationship of a first input parameter of the first operation and a second input parameter of the second operation.
In the above manner, the conversion model includes the parameter model, so that the conversion of the first input parameter and the second input parameter can be realized through the parameter model, and the pre-conversion can be realized when the input parameter is required for the second operation and maintenance operation, so that the efficiency of the operation and maintenance operation method is higher.
In one possible design, the parametric model further indicates a conversion relationship of the second message and a first input parameter of the first operation and maintenance operation.
In the above manner, through the parameter model, after the first network device obtains the first input parameter, the second message can be sent to the second network and the device, so that the second network device is indicated, and the applicability of the operation and maintenance method is higher.
In one possible design, the parametric model further indicates a conversion relationship of a first output parameter of the first operation and a second output parameter of the second operation.
In the above manner, the conversion model includes a parameter model, so that the conversion between the first output parameter of the first operation and the second output parameter of the second operation can be realized through the parameter model, and the efficiency of the operation method is further higher.
In one possible design, after the first network device sends the second message to the second network device, the method further includes: the first network device obtains a response message of the second message, wherein the response message comprises a second output parameter; and the first network equipment obtains the first output parameter according to the parameter model and the second output parameter.
In the above manner, after the first network device obtains the response message of the second message, the first output parameter is obtained according to the parameter model and the second output parameter, so that the conversion between the first output parameter of the first operation and the second output parameter of the second operation can be realized through the parameter model, and therefore, after the second operation is completed, the first output parameter of the first operation can be directly converted, and further, the efficiency of the operation method is higher.
In one possible design, the operation and maintenance template includes an operation and maintenance operation mode.
Under the mode, the operation mode is introduced into the operation and maintenance template, so that the operation and maintenance operation is further limited in the operation and maintenance template, and the accuracy of the operation and maintenance operation is improved.
In one possible design, the operation mode includes a synchronous mode or an asynchronous mode.
In the above manner, the operation mode includes a synchronous mode or an asynchronous mode, so that the synchronous mode or the asynchronous mode can be selected according to the characteristics of operation and maintenance, and flexibility of operation and maintenance is improved.
In one possible design, after the first network device obtains the first message, before the first network device sends the second message to the second network device, the method further includes: the first network device determines that the operation and maintenance operations executable by the second network device include a second operation and maintenance operation according to an operation and maintenance operation policy.
In the above manner, the first network device determines that the operation executable by the second network device includes the second operation according to the operation policy, and sends the second message to the second network device after the determination, so that the application range of the operation method is controlled by performing advanced judgment on the operation policy at the application level, thereby improving the flexibility of the operation method.
In one possible design, the first network device is a top level controller, and the second network device is a domain controller or an intra-domain device under the first network device.
When the operation and maintenance method provided by the application is applied to the scene, the operation and maintenance operation efficiency of the large-scale network equipment can be enhanced because the operation and maintenance operation of the top-level controller can influence the domain controllers and the intra-domain equipment of the global multiple domains.
In one possible design, the second message is used to call a first application programming interface API of the second network device, where the first API is used for the second network device to perform the second operation and maintenance operation.
In the above manner, the first API may be directly called by the second message, so that the second network device executes the second operation and maintenance operation, thereby improving efficiency of the operation and maintenance operation.
In a second aspect, the present application provides a method of operation and maintenance. The method may be performed by a network device provided by the present application (network device provided by the fourth aspect), the method comprising:
a second network device obtains a second message from a first network device, the second message indicates the second network device to execute a second operation, the second operation is obtained according to a first operation and an operation template, the first operation is an operation indicated by the first message obtained by the first network device, the first operation includes a second operation which needs to be executed by the second network device, the operation template includes an operation identifier and a conversion model, the operation identifier indicates the first operation, and the conversion model indicates a conversion relation between the first operation and the second operation;
The second network device performs the second operation.
Optionally, the conversion model includes a parameter model, the parameter model indicating a conversion relationship between a first output parameter of the first operation and a second output parameter of the second operation, and after the second network device performs the second operation, the method further includes:
the second network device obtains a response message of the second message, wherein the response message comprises a second output parameter, and the second output parameter is used for the first network device to obtain a first output parameter according to the parameter model and the second output parameter.
In a third aspect, the present application provides a network device comprising:
and an acquisition module. Obtaining a first message, wherein the first message indicates a first operation and the first operation comprises a second operation which needs to be executed by second network equipment;
the sending module is configured to send a second message to the second network device, where the second message indicates the second network device to perform the second operation, where the second operation is obtained according to the first operation and an operation template, and the operation template includes an operation identifier and a conversion model, where the operation identifier indicates the first operation, and the conversion model indicates a conversion relationship between the first operation and the second operation.
Optionally, the transformation model includes a parametric model indicating a transformation relationship of a first input parameter of the first operation and a second input parameter of the second operation.
Optionally, the parameter model further indicates a conversion relationship of the second message and a first input parameter of the first operation and maintenance operation.
Optionally, the parameter model further indicates a conversion relationship between a first output parameter of the first operation and a second output parameter of the second operation.
Optionally, after the first network device sends the second message to the second network device, the method further includes: the first network device obtains a response message of the second message, wherein the response message comprises a second output parameter; and the first network equipment obtains the first output parameter according to the parameter model and the second output parameter.
Optionally, the operation and maintenance template comprises an operation and maintenance operation mode.
Optionally, the operation mode includes a synchronous mode or an asynchronous mode.
Optionally, the sending module is further configured to: and determining that the operation and maintenance operation executable by the second network equipment comprises a second operation and maintenance operation according to the operation and maintenance operation strategy.
Optionally, the first network device is a top-level controller, and the second network device is a domain controller or an intra-domain device under the first network device.
Optionally, the second message is used to call a first application programming interface API of the second network device, where the first API is used for the second network device to execute the second operation and maintenance operation.
In a fourth aspect, the present application provides a network device comprising:
an obtaining module, configured to obtain a second message from a first network device, where the second message indicates that the second network device performs a second operation, where the second operation is obtained by the first network device according to a first operation and an operation template, where the first operation is an operation indicated by the first message obtained by the first network device, the first operation includes a second operation that needs to be performed by the second network device, and the operation template includes an operation identifier and a conversion model, where the operation identifier indicates the first operation, and the conversion model indicates a conversion relationship between the first operation and the second operation;
And the processing module is used for executing the second operation and maintenance operation.
Optionally, the conversion model includes a parameter model, the parameter model indicating a conversion relationship between a first output parameter of the first operation and a second output parameter of the second operation, and the processing module is further configured to: and sending a response message of the second message to the first network device, wherein the response message comprises the second output parameter, and the second output parameter is used for the first network device to obtain a first output parameter according to the parameter model and the second output parameter.
In a fifth aspect, the present application provides an operation and maintenance operating system, the operation and maintenance operating system comprising:
the first network device is configured to obtain a first message, where the first message indicates a first operation, and the first operation includes a second operation that needs to be performed by the second network device;
the first network device is further configured to send a second message to the second network device, where the second message indicates the second network device to perform the second operation, where the second operation is obtained according to the first operation and an operation template, where the operation template includes an operation identifier and a conversion model, where the operation identifier indicates the first operation, and the conversion model indicates a conversion relationship between the first operation and the second operation;
The second network device is configured to obtain a second message from the first network device, and perform the second operation and maintenance operation.
In a sixth aspect, there is provided an electronic device for use as a first network device, the electronic device comprising: a memory comprising instructions; a processor which, when executing the instructions, causes the electronic device to implement the method as described in any one of the first aspects above.
In a seventh aspect, there is provided an electronic device for use as a second network device, the electronic device comprising: a memory comprising instructions; a processor which, when executing the instructions, causes the electronic device to implement the method as described in any one of the second aspects above.
In an eighth aspect, there is provided a computer readable storage medium having stored thereon computer instructions which, when executed by a processor, cause the processor to implement the method according to any of the first or second aspects above.
A ninth aspect provides a computer program product comprising computer instructions which, when executed, implement the method of any one of the first or second aspects above.
The advantages of the second aspect to the ninth aspect are described above with reference to the advantages of the first aspect, and the description is not repeated.
Drawings
FIG. 1 is a schematic diagram of a system architecture to which operation and maintenance operations according to an embodiment of the present application are applicable;
fig. 2 is a schematic diagram of a specific architecture, in which operation and maintenance operations are applicable in a PING operation scenario between a PON domain and an OTN domain, provided in an embodiment of the present application;
fig. 3 is a schematic software architecture diagram of a top-level controller according to an embodiment of the present application;
fig. 4 is a schematic implementation process diagram of an operation and maintenance method according to an embodiment of the present application;
fig. 5 is a schematic step flow diagram of an operation and maintenance method according to an embodiment of the present application;
fig. 6 is a flowchart illustrating specific steps of an operation and maintenance method according to an embodiment of the present application;
fig. 7 is a schematic structural diagram of a network device according to an embodiment of the present application;
fig. 8 is a schematic structural diagram of a network device according to an embodiment of the present application;
fig. 9 is a schematic structural diagram of an electronic device according to an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application.
The terminology used in the following embodiments is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. As used in the specification and the appended claims, the singular forms "a," "an," "the," and "the" are intended to include, for example, "one or more" such forms of expression, unless the context clearly indicates to the contrary. It should also be understood that in embodiments of the present application, "one or more" refers to one or more than two (including two); "and/or", describes an association relationship of the association object, indicating that three relationships may exist; for example, a and/or B may represent: a alone, a and B together, and B alone, wherein A, B may be singular or plural. The character "/" generally indicates that the context-dependent object is an "or" relationship.
Reference in the specification to "one embodiment" or "some embodiments" or the like means that a particular feature, structure, or characteristic described in connection with the embodiment is included in one or more embodiments of the application. Thus, appearances of the phrases "in one embodiment," "in some embodiments," "in other embodiments," and the like in the specification are not necessarily all referring to the same embodiment, but mean "one or more but not all embodiments" unless expressly specified otherwise. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless expressly specified otherwise.
The term "plurality" in the embodiments of the present application means two or more, and for this reason, "plurality" may be also understood as "at least two" in the embodiments of the present application. "at least one" may be understood as one or more, for example as one, two or more. For example, including at least one means including one, two or more, and not limiting what is included. For example, at least one of A, B and C is included, then A, B, C, A and B, A and C, B and C, or A and B and C may be included. Likewise, the understanding of the description of "at least one" and the like is similar. "and/or", describes an association relationship of an association object, and indicates that there may be three relationships, for example, a and/or B, and may indicate: a exists alone, A and B exist together, and B exists alone. The character "/", unless otherwise specified, generally indicates that the associated object is an "or" relationship.
Unless stated to the contrary, the embodiments of the present application refer to ordinal terms such as "first," "second," etc., for distinguishing between multiple objects and not for defining a sequence, timing, priority, or importance of the multiple objects.
For ease of understanding, the terms involved in the embodiments of the present application are explained as part of the summary of the embodiments of the present application.
Application scenario
Fig. 1 is a schematic diagram of a system architecture to which an operation and maintenance method according to an embodiment of the present application is applicable.
The system architecture may include: an operations support system (operation support system, OSS), a first network device, a second network device. The first network device in fig. 1 is exemplified by a top-level controller (TC), and the second network device is exemplified by a Domain Controller (DC) or an in-Domain Device (DD). The architecture may select devices in the architecture according to a specific scenario, e.g., the devices in the architecture may have only TC, DC, and DD, may include OSS, TC, DC and DD, and may include OSS running devices (TC is a component of OSS), DC, and DD. The "domain" in the above description refers to a network area divided according to a certain standard, such as a network area uniformly applying a certain technology, so that the network devices in the network area can implement efficient interworking between the network devices due to no technology barrier.
Wherein, the functions of each device in the architecture can be: OSS is used to deploy network traffic. For example, the OSS may issue a service deployment request to the top level controller by sending an OSS operation request to the top level controller. Network services include network operations services, such as connectivity detection services, for detecting connectivity between network devices. The top-level controller obtains the service request to be deployed by obtaining the first message. The first message may be from a service deployment configuration entered by the user at the top level controller interface. The first message may also be from a service request sent by a third party system, such as an OSS operation request sent by an OSS. The first message may be in the form of a message, such as a northbound interface message sent by the OSS. The first message indicates a first operation, e.g., an operation in which the OSS requires the top level controller to perform a path connectivity check. In order for the top-level controller to perform the operation and maintenance operation of the path connectivity detection, it is necessary to issue a plurality of operation and maintenance operations to a plurality of domain controllers and/or a plurality of intra-domain network devices under the top-level controller. The operation and maintenance operations of the path connectivity detection can be implemented after the operation and maintenance operations are executed. The first operation includes the operation that the domain controller or the device within the domain needs to perform. The first message obtaining manner may be obtained according to an OSS operation request sent by the OSS operation device, or may be obtained according to local input information of the top controller. If the operation commands or interfaces of the domain controllers or the devices in the domain are different, the top-level controller needs to deploy operation and maintenance operations to the domain controllers or the devices in the domain according to the operation commands or interfaces. In this embodiment, the top-level controller converts the first operation to the second message according to the conversion relationship between the first operation and the operation template. The second message may be in the form of a message, which may be referred to as a southbound operation command, southbound interface message. When the first message includes the first input parameter, the first input parameter is converted into a second input parameter of the operation command of the specified domain. The second message includes a second input parameter. The top level controller is also configured to send a second message to the domain controller or the in-domain device. The second message is used for calling the domain controller of the designated domain to call an application programming interface (application programming interface, API) to execute the operation and maintenance operation corresponding to the API. The second message may also be used to issue an operation configuration to the domain controller or the in-domain device based on a network operation protocol, including, but not limited to, netconf, SNMP, etc., or a proprietary protocol. The domain controller of the designated domain is configured to receive the second message and perform the operation and maintenance operation indicated by the second message. The domain controller of the specified domain is further configured to send a second message to the in-domain device of the specified domain, and the in-domain device implements the service function according to the second message. In some embodiments, after the controller of the designated domain performs the operation and maintenance operation indicated by the second message, a response message of the second message is sent to the top-level controller. The top controller obtains the response message and determines the execution condition of the operation and maintenance operation according to the information carried by the corresponding message. When the response message comprises the second output parameter, after the top controller receives the response message, the top controller converts the second output parameter into the first output parameter according to the operation and maintenance template.
It should be noted that the functions of each device in the above architecture are merely taken as examples, and the functions of each device may be flexibly adjusted according to an actual application scenario, for example, when the first message is processed, the first output parameter and the second output parameter may not be involved, that is, after the intra-domain device executes the operation command according to the second input parameter, the second output parameter does not need to be obtained, and the second output parameter does not need to be included in the response message.
Various operation and maintenance operations can be realized in the architecture, and as various different scenes can occur in any operation and maintenance operation, the messages are different, and in the embodiment of the application, the operation and maintenance templates corresponding to any operation and maintenance operation are pre-arranged, and the conversion relations required under various scenes are defined, for example, the operation and maintenance templates comprise the conversion relations between the first input parameters and the second input parameters and the conversion relations between the first output parameters and the second output parameters. In this way, the top-level controller and the domain controller can receive the first message through the unified interface in any scene, and perform corresponding processing step by step according to the operation and maintenance template and the first message. It should be noted that after the top layer controller converts the first message into the second message, the second message can be directly executed when reaching the device in the domain, so that the device in the domain can implement operation and maintenance operation, and when the cross-domain scene is involved, the technical barriers between different technical domains can be broken through the conversion of the top layer controller.
In addition, for the second operation to be executed, the related second network device may mount the second operation in advance, so that after the second network device (such as the in-domain device) receives the corresponding second operation, it can determine that the second operation is the second operation that is mounted in advance, and then the second operation can be executed. The service realized by the architecture can be a service in a domain or a service in a cross-domain. For intra-domain services, the intra-domain device performing the service function involves only intra-domain devices of one network area; for cross-domain traffic, an in-domain device performing traffic functions needs to involve in-domain devices within multiple network areas. For example, for the architecture shown in fig. 2, connectivity detection is performed in a local area network, then a second operation of connectivity detection needs to be installed in the local area network, so that the second operation of connectivity detection is performed in the local area network, when OSS outputs an OSS operation request of connectivity detection to a top-level controller, the top-level controller converts a first input parameter of connectivity detection in the OSS operation request into a second input parameter of connectivity detection by executing the OSS operation request, and then issues the second input parameter of connectivity detection to a device in a domain of the local area network through the domain controller, where the second input parameter is included in a second message of connectivity detection, and then the device in the domain of the local area network can successfully execute an operation command of connectivity detection according to the second input parameter; for cross-domain services, such as an internet packet explorer (packet internet groper, PING) operation between a passive optical network (passive optical network, PON) and an optical transport network (optical transport network, OTN), may be implemented by a Link Trace (LT) technology, then respective second operation and maintenance operations (LT operation commands) need to be installed in the PON domain and the OTN domain, so that the execution of the second operation and maintenance operations in the PON domain and the OTN domain is legal, and when OSS needs to perform link trace between the PON domain and the OTN domain, the second operation and maintenance operations (which may include corresponding second input parameters of LT) are issued to related devices in the PON domain and the OTN domain, and the link trace function between the PON domain and the OTN domain can be implemented by executing corresponding link trace operation commands by devices in the PON domain and the OTN domain.
More specifically, as shown in fig. 3, a schematic diagram of a software architecture inside the top-level controller in fig. 1 or fig. 2, the inside of the top-level controller may specifically include the following software modules:
(1) A business logic processing system comprising the following components:
and the service designer is used for binding the operation and maintenance template and the service model and generating an operation application strategy, wherein the operation application strategy is used for controlling network operation and maintenance operations under different situations. The service model is a model of the packaged network operation and maintenance function and is used for realizing the general network operation and maintenance function, and the service model can merge different application scenes of one operation and maintenance operation together.
A northbound application program interface (application programming interface, API) for receiving a first message, such as an OSS operation request, and triggering the operation executor to generate a first operation and maintenance operation according to an operation application policy.
A business graphical user interface (graphical user interface, GUI) for receiving a first message, such as a user operation request, and triggering an operation executor to perform generating a first operation and maintenance operation according to an operation application policy.
Logic processor: and the service logic processing is used for carrying out service logic processing according to the set service logic.
(2) The operation designer is used for generating an operation and maintenance template according to operation requirements and managing the operation and maintenance template through an operation and maintenance template library.
(3) The operation and maintenance template library is used for maintaining operation and maintenance templates, wherein the maintenance comprises the steps of storing, modifying, inquiring, adding the operation and maintenance templates newly and the like.
(4) The operation executor is used for generating a second message according to the operation and maintenance template, displaying an input interface and an output interface, receiving a request, displaying a processing result, analyzing input parameters of the first message according to the definition of a parameter model in the operation and maintenance template, transmitting the input parameters to a south-oriented adaptation (adapter) module, distributing the parameters to each domain controller, and analyzing and displaying each domain controller to return according to the definition of a parameter model in the operation and maintenance template.
(5) And the south adapting module is used for converting communication protocols with each domain controller.
It should be noted that the software architecture of the top-level controller shown in fig. 3 is merely an example, and each software module may be flexibly organized and the functions of each software module may be designed, which is not limited herein.
An implementation process schematic diagram of an operation and maintenance method provided in the embodiment of the present application is described in detail below with reference to fig. 4. As shown in fig. 4, the implementation process specifically includes the following steps:
step 401: and compiling an operation and maintenance template for operation and maintenance.
Step 402: and binding the operation and maintenance template of the operation and maintenance operation to the business object, and setting an operation application strategy.
Step 403: and executing operation and maintenance operation.
In step 401, for example, the operation and maintenance operation is a PING operation from PON device to OTN device, and the PING operation may be implemented by LT technology.
The operation and maintenance template comprises: operation identification, operation application strategy and operation basic information.
Wherein the operation identifier is used for indicating the operation and also identifying an operation template. The operation identifier includes, but is not limited to, an operation name, an operation sequence number, and the like.
The operation application policy refers to a situation that the operation is applicable, and the operation application policy may include an operation and maintenance operation mode, where the operation and maintenance operation mode refers to an execution flow mode of the operation and maintenance operation, including a synchronous mode, an asynchronous mode and a reporting mode, where in the synchronous mode, a network device executing the operation and maintenance operation needs to wait for a response message (response message) of an operation message (second message) until receiving the response message, and then may execute other operation and maintenance operations; in the asynchronous mode, the network device executing the operation and maintenance operation can asynchronously execute other operation and maintenance operations while waiting for a response message of the operation message; in the reporting mode, the network device executing the operation directly executes the operation and maintenance operation message, and does not need to forward the operation and maintenance operation message and wait for a response message. The operation application policy may further include a service object, in which a device in which the operation and maintenance template takes effect is specified; the operation application policy may also include information of operation adaptation situations such as device type, version of operation and maintenance operation, etc.
The operation basic information refers to a basic model of an operation and can comprise an operation name and a conversion model, wherein the conversion model is used for indicating the conversion relation between the first operation and the second operation; the transformation model may include a parametric model, which may include an in-parameter model and an out-parameter model. The input model includes a southbound model and a northbound model that define input parameters of an operation, the northbound model of the input parameters is a message body model of the input parameters, the southbound model of the input parameters is used for indicating a conversion relationship between a first input parameter of the first operation and the second message, such as a model of a designated message body from the input parameters to an external system, for example, in a top-level controller, the conversion of the first input parameter received by the top-level controller into a second input parameter meeting a domain controller can be realized based on a mapping file, that is, an output message of the top-level controller, and a format of the output message meets a designated format (that is, a format of the second input parameter) required by the input message of the domain controller; accordingly, the parameter outputting model is similar to the parameter inputting model, and the parameter outputting model can refer to the description of the parameter inputting model, and is used for indicating the conversion relationship between the first output parameter of the first operation and the second output parameter of the second operation, which is not described herein. It should be noted that the parameter entering model or the parameter exiting model does not have to include, the operation and maintenance templates of the operation and maintenance operations may only include the parameter entering model but not the parameter exiting model, and the operation and maintenance templates of some operation and maintenance operations may only include the parameter exiting model but not the parameter entering model, or neither of them, which are not limited herein, and specifically need to be designed according to the operation characteristics of the operation and maintenance operations. The input parameter model and the output parameter model can flexibly select specific data definition formats, such as JsonSchema definition formats, and further, such as a mapping file, the input operation message can be mapped into a second input parameter of a domain controller appointed format, and the mapping file can be realized by adopting FreeMarker expansion grammar. The design of the operation and maintenance template can be completed through an online system and stored in an operation and maintenance template library, the effectiveness of the operation and maintenance template is checked, and the operation and maintenance template is distributed.
Specifically, for example, the PING operation from PON device to OTN device, the PON device and the OTN device side need to define two operation and maintenance templates respectively, and control different operation and maintenance templates applied in different technical fields through different operation and application policies. Taking PON equipment side as an example, the operation name is PING, and OSS and GUI sense PING operation of a general interface. The operation and maintenance template can be defined by Json file, and the structure of the operation and maintenance template can be as follows:
template identification (id), operation application policy (commandrespaint), operation basic information (commanddbascinifo); wherein the operation basic information includes: an operation name (operationName), a parameter entry model (commandonfigure), and a parameter exit model (commandStatus).
Examples of the operation and maintenance templates are as follows:
Figure BDA0003325904070000091
/>
Figure BDA0003325904070000101
it should be noted that, in the structure of the template sample, some variables may include multiple layers, the content in "{ }" and \or "[ ]" after the variables represents a specific definition of a variable, and the variables may be further nested therein, that is, the variables described by "{ }" and \or "[ ]" may be further included therein, for example, the variables described by "{ }" and \or "[ ]" include "rootsolutions" and "applyObjects" in the command response, and each of "{ }" and \or "[ ]" defines the variables whose scope of value is only in the "{ }" and \or "[ ], for example," value "in" command configuration "and the scope of value" in "command configuration" are only in "command configuration" and "in" command status ", and the scope of value" in "command status" is only in "command status", and the code of the template is the code of the template sample.
As can be seen from the operation and maintenance template sample, wherein id is the template identifier of the operation and maintenance template, and in the sample, the value of id is NCEFANEthernetOamLTCommandTemplate ID; the description is the description of the operation and maintenance template and is used for explaining the service functions realized by the operation and maintenance template; operastatus is the release state of the operation and maintenance template, and can be released (released) or unpublished (unpublished); the commandresumpt is an operation application policy, in which "scenario" defines an application scenario in which an operation and maintenance operation is applicable, where "otn_p2mp" indicates that the operation and maintenance template is applied to an OTN domain, and a point-to-multipoint master station (point 2multiple point,P2MP) technology, "subscreenio" indicates Termination Point, describes that this operation is for a port level, venders is vendor, device type and version information in which the operation and maintenance operation is operable, processMode is an operation mode, in which "syncMode" indicates a synchronization mode, applyObjects is an application object of the operation and "objectType" is an object type, and "posid-AC" indicates an access point of a combined service, and "idscenes" indicates a detailed operation constraint, and "name" in a list of values is a parameter name "worklayer" indicates that a work layer is operable, and "value" in a list of values "vals" value "indicates that" value of a service layer "is valid" is started up in an Ethernet "value" indicates that "value of a service is allowed to take effect. If the working mode of the access point is not Ethernet, the command is not allowed to be started; command BICInfo is operation basic information, operation name is a common operation name, for example, factory connectivity detection operation is Ethernet OAM LT operation, but the operation name (operation name) can be uniformly packaged into PING (transmission, access and data communication pull-through) for the outside, and the operation name can be 'PING'; the command is a parameter entering model, the name in the command points to the name of a specific parameter entering model, the parameter entering model is realized through a parameter entering definition component and a component mapping file, and the value in the command is a unique identification ID corresponding to the parameter entering template. Specifically, examples of defining the component structure may be as follows:
Defining the component structure may include two parts, a component template and a component mapping file, where the component template describes the input and constraints of parameters through JsonSchema.
Component templates are specified for example as follows:
Figure BDA0003325904070000111
component mapping files: the first message (north interface message) is translated into the second message (south interface message) of the input domain controller, and the sample fragments are as follows:
Figure BDA0003325904070000112
/>
Figure BDA0003325904070000121
the input model is defined by command configuration, the output model is defined by command status, and the output model points to a northbound interface component and a mapping file defined by JsonSchema through a northbound interface component name. The json schema defines the input parameters necessary for PING operation, such as source maintenance endpoint (maintenance entity group end point, MEP) identity, time To Live (TTL) etc.; the "name", "value" and command in the parameter model (command status) are similar, and reference is made to the description of the parameter model.
By means of the operation and maintenance template arrangement, any operation and maintenance operation can be abstracted into an extensible general operation and maintenance template, and development workload of the operation and maintenance operation can be greatly reduced by arranging the operation and maintenance templates in real time. This is because, by abstracting the situation in each scene through the operation and maintenance template, the interface, the input parameter, the output parameter and the different operation modes in different scenes are automatically generated in the operation and maintenance template, and the repeated arrangement in each scene is not needed, so that the workload is reduced. The operation mode can be abstracted into a synchronous interface of general operation and an asynchronous interface of operation, the application logic obtains the flow mode from the operation and maintenance template, calls a unified synchronous interface or an asynchronous interface, converts a first input parameter into a second input parameter by using a mapping file of a bound business object in the unified interface, and converts the second output parameter into the first output parameter, and the service level abstract interface is provided for the OSS through the association of the operation and maintenance template and an operation application strategy.
In step 402, a traffic object may include each access point (e.g., two access points) implementing a traffic connection and a network path between the access points. If the operation template of the operation and maintenance operation is directly bound to the service object, because the operation and maintenance operation of a service is realized by matching all access points, the operation and maintenance operation is decomposed into operation commands on all the access points, and the operation and maintenance operation is required to be executed on all the access points. For example, each access point is specifically a designated PON device in a PON domain and a designated OTN device in an OTN domain, the operation and maintenance operation is a node activation operation, and the node activation operation is to register a node in a designated network area, in this example, the designated PON device and the designated OTN device, and when the node activation operation is performed, it is necessary to synchronously perform respective corresponding node activation commands on the designated PON device and the designated OTN device, respectively.
The service object may be an access point only, and then the operation and maintenance operation may be initiated by only one access point, without synchronous execution. For example, the operation and maintenance template is bound to the designated PON device and the designated OTN device, and the operation and maintenance operation is a delay detection operation, so that the designated PON device side may wait for the designated OTN device to respond by initiating a delay detection command (southbound operation command) from the designated PON device, and the designated OTN device side may wait for the designated PON device to respond by initiating a delay detection command (southbound operation command) from the designated OTN device.
It should be noted that how the above operation is executed in different situations is limited by the operation policy. Before the top-level controller converts the first message into the second message, judging whether the OTN equipment and the PON equipment are opened with corresponding operation or not through an operation and maintenance operation strategy, wherein the operation and maintenance operation strategy of the operation and maintenance template further comprises a service object, one end of the service object can be appointed to take effect and multiple ends of the service object can take effect, the effective equipment type, the effective version of an operation command and the like can be appointed in the operation and maintenance operation strategy, and the operation and maintenance module can be flexibly designed according to specific operation and maintenance operations; for the service of dividing the source end and the destination end, one section of validation can be the source end validation and the destination end validation, and multiple ends of validation can be the two ends validation.
In an example of a PON device to OTN device PING operation, the operation and maintenance operation policy may be defined by a Json file, and specifically, the operation and maintenance operation policy may be as follows:
the CommandTomplite is an operation and maintenance template identifier and is used for binding the name of the operation and maintenance template; command operatedName is the name of the operation command correspondingly displayed by the operation and maintenance operation; the GUIHookPoint is an interface hanging node and is used for indicating a business object on which operation and maintenance operations are mounted; validObjectCfg is an operation validation policy, and the source is specified to be validated; bindingBusinesObjects are application objects for controlling on which business objects the operation and maintenance template takes effect, and fdNAe is specifically the name of the business object to be bound.
Examples of the operation and maintenance operation policy include the following fields:
Figure BDA0003325904070000131
in the following, taking the first network device as the top layer controller and taking the second network device as the domain controller as an example, the detailed description of the flow of step 403 when the top layer controller controls any designated domain to execute the operation scene is given, and the specific steps of step 403 may refer to fig. 5, which is a specific flowchart for executing the operation.
Step 501: the top level controller obtains a first message.
Specifically, the first operation may be an operation in a single domain or an operation in a cross domain, the first message indicates the first operation, the first operation includes a second operation that needs to be performed by a second network device, the second operation is obtained according to the first operation and an operation template, the second operation performed by the second network device may be indicated by the second message, the operation template includes an operation identifier and a conversion model, the operation identifier indicates the first operation, and the conversion model indicates a conversion relationship between the first operation and the second operation.
It should be noted that, the first message may include a first input parameter, and if the operation and maintenance template corresponding to the operation and maintenance operation includes the parameter entering model, the first input parameter needs to be obtained according to the specification in the parameter entering model. When the first input parameter is obtained, in step 501, a parameter entering model may be used in an operation and maintenance template of an operation and maintenance operation, an operation interface of a client may be generated, according to input information of the operation interface of the client, the first input parameter of the operation and maintenance operation may be determined, as shown in fig. 6, according to a Json schema definition of the parameter entering, a Json operation interface may be generated, and input information of the Json operation interface may be obtained, or, according to the parameter entering model, the top-level controller may also extract the first input parameter of the operation and maintenance operation from an OSS operation request sent by an OSS device; step 501 may be implemented by the operation executor of fig. 3.
Step 502: the top level controller determines whether the operation and maintenance operations executable by the domain controller include a second operation and maintenance operation according to the operation and maintenance operation policy.
If yes, go to step 503, otherwise, directly end the flow.
Step 503: the top level controller generates a second message from the first message and determines an operational mode in the operation and maintenance template.
For example, the first message is an OSS operation request, and is directly converted into a Json message according to the parameter entry model, where the Json message may specifically be as follows:
CommonCommand
operationName:ping
command configuration hanging node
|--name:PONEthernetOamLTCfg
|--value:“{{\“remoteMepId\”:2,\”ttl\”:62}}”
Wherein command is a parameter entering model, ponnetoamtcfg represents, remoteMepId represents the ID of the far-end MEP point, and TTL represents that the survival time is 62 milliseconds (ms).
Specifically, when the operation request to be processed includes a first input parameter, the top-level controller may convert the first input parameter into a second input parameter according to a mapping file of the parameter entering model in the operation and maintenance template, and generate a southbound interface packet according to the second input parameter, where a format of the second input parameter in the southbound interface packet is a specified format of the input parameter required by the domain controller; step 502 may be implemented by the operation executor of fig. 3.
If the operation mode is the synchronous mode, executing step 504; if the operation mode is asynchronous, executing step 505; step 503 may be implemented by the logic processor in fig. 3.
Step 504: and the top layer controller sends the southbound interface message to the designated domain controller and waits for a response message of the southbound interface message.
If a response message is obtained, step 507 is executed.
Step 505: and the top layer controller sends the southbound interface message to the designated domain controller and acquires the task identifier.
The task identifier is used for marking the task of the domain controller for processing the southbound interface message.
Step 506: and the top-layer controller waits for a response message of the southbound interface message according to the task identifier.
If a response message is obtained, step 507 is executed. It should be noted that, when step 506 is performed, the top-level controller may also perform other operations in parallel.
Step 507: and the top controller further processes according to the response message.
If the operation and maintenance template of the operation and maintenance operation comprises the parameter outputting model, the in-domain device can obtain the second output parameter, when the operation and maintenance template of the operation and maintenance operation comprises the parameter outputting model, the in-domain device can obtain the second output parameter according to the second input parameter, in this case, the response message can comprise the second output parameter, and then the top-level controller can convert the second output parameter output by the domain controller into the first output parameter in the north direction according to the mapping file of the parameter outputting model, and the format of the first output parameter accords with the appointed format required by the OSS, so that the first output parameter can be returned to the OSS or the operation interface of the client for outputting.
In the following, a more specific example will be described, for example, the operation and maintenance operation is a PING operation from PON device to OTN device in PON device, and the PING operation may be implemented by an LT command, and an operation and maintenance template of the PING operation includes an in-parameter model and an out-parameter model. The specific steps can be as shown in fig. 6, and specifically are as follows:
step 601: and the top-level controller acquires a north interface message of the PING operation.
For example, the top-level controller may generate a Json view interface of the client according to the Json schema definition of the parameter entry model of the PING operation, directly convert the input information of the operation interface of the client into a northbound interface message in Json format, where the northbound interface message includes the first input parameter.
Step 602: the top layer controller converts the north interface message into the south interface message.
For example, the top-level controller converts the first input parameters into second input parameters through the mapping file of the parameter entry model, where the second input parameters are in a format of input parameters required by the domain where the PON device is located, and the second input parameters are included in the southbound interface packet.
Step 603: the top level controller determines the operation mode defined in the operation and maintenance template of the PING operation as a synchronous mode.
It should be noted that, if it is determined that the operation mode defined by the PING operation is the synchronous mode, step 604 is performed, and if the defined operation mode is not the synchronous mode, other branches are possible.
Step 604: and the top layer controller transmits the converted southbound interface message to a domain controller where the PON equipment is located through the southbound adapter module, and waits for obtaining a response message.
Step 605: the domain controller issues a southbound interface message to the PON device.
It should be noted that, in this example, the PING operation is determined in advance to be the operation on the PON device, so step 605 is performed, however, in some other cases, the domain controller may also determine that the operation corresponding to the southbound interface packet is the operation on the domain controller, and then directly execute the southbound interface packet to implement the operation on the domain controller.
Step 606: and the PON equipment executes the southbound interface message and obtains a second output parameter according to the second input parameter.
Wherein the second output parameter is included in the response message.
Step 607: the PON device transmits a response message to the domain controller.
Step 608: the domain controller sends a response message to the top-level controller.
Step 609: and the top-level controller converts the second output parameters into the first output parameters according to the mapping file of the parameter-outputting model of the PING operation.
After step 609, the top level controller may convert the first output parameter to an OSS or an operator interface output at the client.
The method can realize the online expansion function of operation and maintenance operation only by updating the operation and maintenance template without reloading the program package, thereby realizing release-free release. The method realizes an ecological construction technology, the OSS and the client do not need to understand complex processing logic, and various operation and maintenance functions of the cross-domain service can be obtained only by compiling the operation and maintenance template according to the kernel framework, so that the end-to-end operation and maintenance functions of the cross-domain technology are solved, the special requirements of different domains are quickly adapted, and the end-to-end operation and maintenance short board of the current cross-domain technology is solved.
As shown in fig. 7, the present application provides a network device, including:
the module 701 is acquired. Obtaining a first message, wherein the first message indicates a first operation and the first operation comprises a second operation which needs to be executed by second network equipment;
a sending module 702, configured to send a second message to the second network device, where the second message indicates that the second network device performs the second operation, where the second operation is obtained according to the first operation and an operation template, and the operation template includes an operation identifier and a conversion model, where the operation identifier indicates the first operation, and the conversion model indicates a conversion relationship between the first operation and the second operation.
Optionally, the transformation model includes a parametric model indicating a transformation relationship of a first input parameter of the first operation and a second input parameter of the second operation.
Optionally, the parameter model further indicates a conversion relationship of the second message and a first input parameter of the first operation and maintenance operation.
Optionally, the parameter model further indicates a conversion relationship between a first output parameter of the first operation and a second output parameter of the second operation.
Optionally, after the first network device sends the second message to the second network device, the method further includes: the first network device obtains a response message of the second message, wherein the response message comprises a second output parameter; and the first network equipment obtains the first output parameter according to the parameter model and the second output parameter.
Optionally, the operation and maintenance template comprises an operation and maintenance operation mode.
Optionally, the operation mode includes a synchronous mode or an asynchronous mode.
Optionally, the sending module 702 is further configured to: and determining that the operation and maintenance operation executable by the second network equipment comprises a second operation and maintenance operation according to the operation and maintenance operation strategy.
Optionally, the first network device is a top-level controller, and the second network device is a domain controller or an intra-domain device under the first network device.
Optionally, the second message is used to call a first application programming interface API of the second network device, where the first API is used for the second network device to execute the second operation and maintenance operation.
As shown in fig. 8, the present application provides a network device, including:
an obtaining module 801, configured to obtain a second message from a first network device, where the second message indicates that the second network device performs a second operation, where the second operation is obtained by the first network device according to a first operation and an operation template, where the first operation is an operation indicated by the first message obtained by the first network device, where the first operation includes a second operation that needs to be performed by the second network device, where the operation template includes an operation identifier and a conversion model, where the operation identifier indicates the first operation, and where the conversion model indicates a conversion relationship between the first operation and the second operation;
A processing module 802, configured to perform the second operation and maintenance operation.
Optionally, the conversion model includes a parameter model, the parameter model indicating a conversion relationship between a first output parameter of the first operation and a second output parameter of the second operation, and the processing module 802 is further configured to: and sending a response message of the second message to the first network device, wherein the response message comprises the second output parameter, and the second output parameter is used for the first network device to obtain a first output parameter according to the parameter model and the second output parameter.
The embodiment of the application also provides an electronic device, which may have a structure as shown in fig. 9, and may be a computer device, or may be a chip or a chip system capable of supporting the computer device to implement the operation and maintenance operation method provided in the embodiment of the application, where the electronic device may be used as a first network device or a second network device.
The electronic device as shown in fig. 9 may comprise at least one processor 901, the at least one processor 901 being configured to couple to a memory, read and execute instructions in the memory to implement the steps of the operation and maintenance method provided in the embodiments of the present application. Optionally, the electronic device may further include a communication interface 902 for supporting the electronic device for signaling or data reception or transmission. A communication interface 902 in the electronic device may be used to enable interaction with other electronic devices. The processor 901 may be configured to implement the electronic device to perform the steps in the operation and maintenance method provided in the embodiments of the present application. Optionally, the electronic device may further include a memory 903, in which computer instructions are stored, where the memory 903 may be coupled to the processor 901 and/or the communication interface 902, for enabling the processor 901 to call the computer instructions in the memory 903 to implement the steps in the operation and maintenance method provided in the embodiments of the present application; in addition, the memory 903 may be used to store data related to the method embodiments of the present application, for example, to store data, instructions necessary to support the interaction performed by the communication interface 902, and/or to store configuration information necessary for the electronic device to perform the methods described in the embodiments of the present application.
Embodiments of the present application also provide a computer readable storage medium, where computer instructions are stored, where the computer instructions, when executed by a computer, may cause the computer to perform the method involved in any one of the possible designs of the method embodiments and the method embodiments described above. In the embodiment of the present application, the computer readable storage medium is not limited, and may be, for example, RAM (random-access memory), ROM (read-only memory), or the like.
The present application also provides a chip that may include a processor and interface circuitry for performing the methods referred to in any one of the possible implementations of the method embodiments described above, wherein "coupled" means that the two components are directly or indirectly joined to each other, which may be fixed or movable.
The present application also provides a computer program product comprising computer instructions which, when executed, can implement the method involved in any one of the possible designs of the above-described method embodiments.
In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of computer instructions. When the computer instructions are loaded and executed on a computer, the processes or functions described in accordance with embodiments of the present invention are produced in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from one website, computer, server, or data center to another website, computer, server, or data center by a wired (e.g., coaxial cable, optical fiber), or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains an integration of one or more available media. The usable medium may be a magnetic medium (e.g., a floppy Disk, a hard Disk, a magnetic tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a Solid State Disk (SSD)), or the like.
The steps of a method or algorithm described in the embodiments of the present application may be embodied directly in hardware, in a software element executed by a processor, or in a combination of the two. The software elements may be stored in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. In an example, a storage medium may be coupled to the processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC, which may reside in a terminal device. In the alternative, the processor and the storage medium may reside in different components in a terminal device.
These computer instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
Although the invention has been described in connection with specific features and embodiments thereof, it will be apparent that various modifications and combinations thereof can be made without departing from the scope of the invention. Accordingly, the specification and drawings are merely exemplary illustrations of the present invention as defined in the appended claims and are considered to cover any and all modifications, variations, combinations, or equivalents that fall within the scope of the invention. It will be apparent to those skilled in the art that various modifications and variations can be made to the present invention without departing from the spirit or scope of the invention. Thus, it is intended that the present invention also include such modifications and alterations insofar as they come within the scope of the appended claims or the equivalents thereof.

Claims (19)

1. A method of operation and maintenance comprising:
the method comprises the steps that first network equipment obtains a first message, wherein the first message indicates a first operation and maintenance operation, and the first operation and maintenance operation comprises a second operation and maintenance operation which needs to be executed by second network equipment;
the first network device sends a second message to the second network device, the second message indicates the second network device to execute the second operation, the second operation is obtained according to the first operation and an operation template, the operation template comprises an operation identifier and a conversion model, the operation identifier indicates the first operation, and the conversion model indicates a conversion relation between the first operation and the second operation.
2. The method of claim 1, wherein the transformation model comprises a parametric model indicating a transformation relationship of a first input parameter of the first operation and a second input parameter of the second operation.
3. The method of claim 1 or 2, wherein the parametric model further indicates a conversion relationship of the first input parameter of the first operation and the second message.
4. A method according to any one of claims 2 to 3, wherein the parametric model further indicates a conversion relationship of a first output parameter of the first operation and a second output parameter of the second operation.
5. The method of claim 4, wherein after the first network device sends the second message to the second network device, further comprising:
the first network device obtains a response message of the second message, wherein the response message comprises the second output parameter;
and the first network equipment obtains the first output parameter according to the parameter model and the second output parameter.
6. The method of any of claims 1 to 5, wherein the operation and maintenance template comprises an operation and maintenance operation mode.
7. The method of claim 6, wherein the operational mode of operation comprises a synchronous mode or an asynchronous mode.
8. The method of any of claims 1-7, wherein after the first network device obtains the first message, before the first network device sends the second message to the second network device, further comprising:
the first network device determines that the operation and maintenance operations executable by the second network device include a second operation and maintenance operation according to an operation and maintenance operation policy.
9. The method of any of claims 1 to 8, wherein the first network device is a top level controller and the second network device is a domain controller or an intra-domain device under the first network device.
10. The method of any of claims 1 to 9, wherein the second message is to call a first application programming interface, API, of the second network device, the first API to be used by the second network device to perform the second operation and maintenance operation.
11. A method of operation and maintenance comprising:
a second network device obtains a second message from a first network device, the second message indicates the second network device to execute a second operation, the second operation is obtained by the first network device according to a first operation and an operation template, the first operation is an operation indicated by the first message obtained by the first network device, the first operation includes a second operation which needs to be executed by the second network device, the operation template includes an operation identifier and a conversion model, the operation identifier indicates the first operation, and the conversion model indicates a conversion relation between the first operation and the second operation;
The second network device performs the second operation.
12. The method of claim 11, wherein the transformation model comprises a parametric model indicating a transformation relationship of a first output parameter of the first operation and a second output parameter of the second operation, the second network device further comprising, after performing the second operation:
the second network device sends a response message of the second message to the first network device, wherein the response message comprises the second output parameter, and the second output parameter is used for the first network device to obtain a first output parameter according to the parameter model and the second output parameter.
13. A network device, comprising:
an acquisition module, configured to acquire a first message, where the first message indicates a first operation, and the first operation includes a second operation that needs to be performed by a second network device;
the sending module is configured to send a second message to the second network device, where the second message indicates the second network device to perform the second operation, where the second operation is obtained according to the first operation and an operation template, and the operation template includes an operation identifier and a conversion model, where the operation identifier indicates the first operation, and the conversion model indicates a conversion relationship between the first operation and the second operation.
14. A network device, comprising:
an obtaining module, configured to obtain a second message from a first network device, where the second message indicates that the second network device performs a second operation, where the second operation is obtained by the first network device according to a first operation and an operation template, where the first operation is an operation indicated by the first message obtained by the first network device, the first operation includes a second operation that needs to be performed by the second network device, and the operation template includes an operation identifier and a conversion model, where the operation identifier indicates the first operation, and the conversion model indicates a conversion relationship between the first operation and the second operation;
and the processing module is used for executing the second operation and maintenance operation.
15. An operation and maintenance operating system, comprising: a first network device and a second network device;
the first network device is configured to obtain a first message, where the first message indicates a first operation, and the first operation includes a second operation that needs to be performed by the second network device;
The first network device is further configured to send a second message to the second network device, where the second message indicates the second network device to perform the second operation, where the second operation is obtained according to the first operation and an operation template, where the operation template includes an operation identifier and a conversion model, where the operation identifier indicates the first operation, and the conversion model indicates a conversion relationship between the first operation and the second operation;
the second network device is configured to obtain a second message from the first network device, and perform the second operation and maintenance operation.
16. An electronic device for use as a first network device, the electronic device comprising:
a memory comprising instructions;
a processor, which when executing the instructions, causes the electronic device to implement the method of any one of claims 1-10.
17. An electronic device for use as a second network device, the electronic device comprising:
a memory comprising instructions;
a processor, which when executing the instructions, causes the electronic device to implement the method of claim 11 or 12.
18. A computer readable storage medium having stored thereon computer instructions which, when executed by a processor, implement the method of any of claims 1-12.
19. A computer program product comprising computer instructions which, when executed, implement the method of any of claims 1-12.
CN202111261486.0A 2021-10-28 2021-10-28 Operation and maintenance operation method, system and network equipment Pending CN116056120A (en)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN202111261486.0A CN116056120A (en) 2021-10-28 2021-10-28 Operation and maintenance operation method, system and network equipment
PCT/CN2022/123609 WO2023071717A1 (en) 2021-10-28 2022-09-30 Operation and maintenance operation method and system, and network device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202111261486.0A CN116056120A (en) 2021-10-28 2021-10-28 Operation and maintenance operation method, system and network equipment

Publications (1)

Publication Number Publication Date
CN116056120A true CN116056120A (en) 2023-05-02

Family

ID=86116911

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202111261486.0A Pending CN116056120A (en) 2021-10-28 2021-10-28 Operation and maintenance operation method, system and network equipment

Country Status (2)

Country Link
CN (1) CN116056120A (en)
WO (1) WO2023071717A1 (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN116384715B (en) * 2023-06-06 2023-08-11 深圳墨影科技有限公司 Robot operation and maintenance management method of digital robot industrial chain

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101483836A (en) * 2009-01-15 2009-07-15 中兴通讯股份有限公司 Novel maintenance system and method
CN111193602B (en) * 2018-11-15 2023-04-07 顺丰科技有限公司 Automatic operation and maintenance management system and method
CN111061555A (en) * 2019-12-22 2020-04-24 济南浪潮数据技术有限公司 Operation and maintenance method based on infrastructure and related device
CN111158743B (en) * 2019-12-29 2022-04-22 北京浪潮数据技术有限公司 Big data operation and maintenance management platform
CN113515603A (en) * 2021-04-27 2021-10-19 深圳力维智联技术有限公司 Method, system and equipment for processing operation and maintenance monitoring data of machine room

Also Published As

Publication number Publication date
WO2023071717A1 (en) 2023-05-04

Similar Documents

Publication Publication Date Title
WO2018006789A1 (en) Parameter checking method and apparatus, and network management server and computer storage medium
EP3143511B1 (en) Method and apparatus for affinity-based network configuration
EP3355517B1 (en) Service and resource orchestration system, method and device
CN111490893B (en) Method, device and system for establishing network forwarding model
EP3706382A1 (en) Method and device for implementing remote procedure call
US20210119880A1 (en) Generating and implementing a platform-neutral cloud-native application model
CN111683066B (en) Heterogeneous system integration method, heterogeneous system integration device, computer equipment and storage medium
US20140351801A1 (en) Formal verification apparatus and method for software-defined networking
CN113709810B (en) Method, equipment and medium for configuring network service quality
CN111159019B (en) Application program testing method, testing control terminal and testing terminal
CN111225070B (en) Flow control method, device and system and SDN controller
CN113612654A (en) Vehicle-mounted gateway function testing method based on database
CN113806037A (en) Service calling method and device, storage medium and electronic equipment
CN113810206A (en) Network automation arrangement management method, entity, controller and electronic equipment
CN116056120A (en) Operation and maintenance operation method, system and network equipment
CN105515890A (en) OpenFlow protocol consistency testing method and equipment
CN110187986B (en) Command management method, system, device and computer readable storage medium
CN113360386B (en) Method and device for testing driving of switching chip, electronic equipment and storage medium
Zaballa et al. Automation of modular and programmable control and data plane SDN networks
CN115314565B (en) Protocol configuration method, protocol conversion method and building control system
CN113342456A (en) Connection method, device, equipment and storage medium
CN108616453B (en) Method, device and system for network equipment
CN116455869A (en) Method and system for efficiently configuring public network domain name based on Kubernetes
US10200445B2 (en) Method for analyzing performance of network application program in software defined networking environment, apparatus therefor, and computer program therefor
WO2023044673A1 (en) Method and apparatus for deploying industrial edge application, and computer-readable storage medium

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination