Operation and maintenance object description method based on object-oriented technology

Abstract

The invention discloses an operation and maintenance object description method based on an object-oriented technology. The method comprises the following steps: carrying out operation and maintenance object modeling according to characteristics of cloud network operation and maintenance so as to describe an operation and maintenance object; defining attributes of the operation and maintenance object to describe parameters of the operation and maintenance object; defining an index of the operation and maintenance object to describe a running state of the operation and maintenance object; defining an operation and maintenance object method to describe an operation service opened by the operation and maintenance object, wherein the operation and maintenance object method is an operation supported by the operation and maintenance object; analyzing the relationship among the operation and maintenance objects and associating the inheritance relationship of the operation and maintenance objects; the inheritance relation of one operation and maintenance object to the attribute, the index and the method of the other operation and maintenance object is constructed according to the relation between the operation and maintenance objects; and applying the operation and maintenance object to the production scene, and using the attribute, the index and the method of the operation and maintenance object in the production scene. According to the invention, cloud network objects are uniformly managed, actual daily production requirements are quickly responded, and the cloud network objects are quickly incorporated into operation and maintenance scenes.

Description

Technical Field

[0001] The present invention relates to the field of telecommunication cloud network production operation and maintenance, and in particular to an operation and maintenance object description method based on object-oriented technology. Background Art

[0002] Cloud network objects such as professional network elements, various alarms, work orders, and services are the core of cloud network operation and maintenance. Various production and operation scenarios are developed around cloud network objects. The duplication of capabilities or the inconsistent performance of the same capability in different scenarios will cause ambiguity in actual operation and maintenance.

[0003] Although the current existing technology has master data management for data, which realizes the unified management, distribution and auditing of master data, it only targets the data of cloud network objects and does not target the relationships between cloud network objects and the operations supported by cloud network objects. Summary of the Invention

[0004] The purpose of the present invention is to provide an operation and maintenance object description method based on object-oriented technology, so as to avoid the problem that when cloud network objects are used in existing production scenarios, they are constructed independently and the capabilities of cloud network objects at different levels are not shared.

[0005] The technical solution adopted in the present invention is: An operation and maintenance object description method based on object-oriented technology includes the following steps: Step 1: Model the operation and maintenance objects based on the characteristics of cloud network operation and maintenance to describe the operation and maintenance objects; Step 2: Analyze the relationships between the various operation and maintenance objects and associate the inheritance relationships between the various operation and maintenance objects. That is, based on the relationships between the operation and maintenance objects, construct the inheritance relationships of one operation and maintenance object to the attributes, indicators, and methods of another operation and maintenance object. Step 3: Apply the operation and maintenance object to the production scenario and use the attributes, indicators, and methods of the operation and maintenance object in the production scenario.

[0006] Furthermore, the operation and maintenance object modeling in step 1 includes defining the attributes of the operation and maintenance object to describe the parameters of the operation and maintenance object; defining the indicators of the operation and maintenance object to describe the operating status of the operation and maintenance object; and defining the operation and maintenance object methods to describe the operation services open to the operation and maintenance object. The operation and maintenance object methods are the operations supported by the operation and maintenance object.

[0007] Furthermore, the attributes of the operation and maintenance object in step 1 include the attribute name (PropName), the attribute code (PropCode), the attribute data type (DataType), the attribute label (Category), and the attribute data example (DataExample).

[0008] Specifically, the data type includes the data source type (SrcType), [script content | service name]) Furthermore, the indicators of the operation and maintenance object in step 1 include the indicator name (PropName), the indicator code (PropCode), the indicator data type (DataType), and the indicator data example (DataExample).

[0009] Furthermore, the operation and maintenance object methods include the operation name (OperName), operation identifier / code (OperCode), operation type (OperType), whether to initialize execution (IsInit), whether to feedback results (IsReturnResult), whether to push to the operation list display (IsDisplay), number of retries (RetryTimes), timeout (seconds) (Overtimes), request headers (Headers), input parameters (InParams), output parameters and echo (OutParams).

[0010] Furthermore, the object inherited in step 2 is called the base class, and the class that inherits properties, indicators, and methods is called the subclass; inheritance is divided into single inheritance and multiple inheritance. In single inheritance, the subclass inherits all properties, indicators, and methods of the parent class, and the subclass extends the properties, indicators, and methods of the subclass itself; in multiple inheritance, the subclass inherits the properties, indicators, and methods of multiple base classes. There is one main class among the multiple base classes. When the properties, indicators, and methods of other base classes conflict with the main class, the properties, indicators, and methods of the main class take precedence.

[0011] Specifically, the object being inherited is called a base class, parent class, or superclass, and the class that inherits properties, indicators, and methods is called a derived class or subclass. The main purpose of inheritance is to improve the reusability and maintainability of operation and maintenance objects.

[0012] In single inheritance, a subclass inherits all properties, indicators, and methods (supported operations) of its parent class. It can also set whether methods are initialized, whether results are returned, whether they are pushed to the operation list for display, and the method's input and output parameters. Subclasses extend their own properties, indicators, and methods (supported operations). Multiple inheritance follows the same inheritance pattern as single inheritance; with multiple base classes, the first-listed base class becomes the primary class. If there are conflicts in properties, indicators, or methods between base classes, the primary class's definition takes precedence.

[0013] Furthermore, production scenarios include topology presentation, fault and work order handling, risk operations, and human-computer interaction.

[0014] Furthermore, step 3 specifically includes the following steps: Step 3-1: Define the production operation and maintenance scenario based on the production scenario and define the application conditions that meet the production scenario; Step 3-2: Analyze and determine the cloud network operation and maintenance objects involved in the application scenario; Step 3-3: Obtain the operation and maintenance objects required by the application scenario and perform initialization operations, that is, the operations performed by the system background after matching the application scenario; Step 3-4: Push the operation and maintenance object methods, that is, the operations supported by the operation and maintenance object, to the user.

[0015] This invention adopts the above technical solution, employing object-oriented technology to abstract cloud network objects. It abstracts various cloud network operation and maintenance objects (e.g., network elements, boards, ports, relays, services, alarms, and work orders) into classes. Based on the inheritance characteristics of these classes, different subclasses are generated. For example, subclasses of network elements can include wireless network elements and transmission network elements. Wireless network elements can be further divided into wireless 4G network elements and wireless 5G network elements, which can then be further divided into various wireless 4G network elements. Each object abstractly defines attributes, indicators, and methods (supported operations) based on production requirements. This method provides unified management of cloud network objects, forming a "master resource" library of cloud network objects that can quickly respond to actual daily production requirements and be quickly incorporated into operation and maintenance scenarios.

[0016] This invention is suitable for operators to standardize the operation and maintenance management of cloud network objects. Its open capabilities can support scenarios such as network acceptance, fault handling, daily inspections, and risk operations. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] The present invention will be further described in detail below with reference to the accompanying drawings and specific embodiments; Figure 1 This is a schematic diagram of the principle architecture of an operation and maintenance object description method based on object-oriented technology of the present invention; Figure 2 This is a schematic diagram of the single inheritance relationship of the present invention; Figure 3 This is a multiple inheritance diagram of the inheritance relationship of the present invention; Figure 4 This is a flowchart of applying the operation and maintenance object of the present invention to a production scenario. DETAILED DESCRIPTION

[0018] In order to make the purpose, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application.

[0019] like Figures 1 to 4 As shown in FIG1 , the present invention discloses an operation and maintenance object description method based on object-oriented technology, which includes the following steps: Step 1: Model the operation and maintenance objects based on the characteristics of cloud network operation and maintenance to describe the operation and maintenance objects; Step 2: Analyze the relationships between the various operation and maintenance objects and associate the inheritance relationships between the various operation and maintenance objects. That is, based on the relationships between the operation and maintenance objects, construct the inheritance relationships of one operation and maintenance object to the attributes, indicators, and methods of another operation and maintenance object. Step 3: Apply the operation and maintenance object to the production scenario and use the attributes, indicators, and methods of the operation and maintenance object in the production scenario.

[0020] Furthermore, the operation and maintenance object modeling in step 1 includes defining the attributes of the operation and maintenance object to describe the parameters of the operation and maintenance object; defining the indicators of the operation and maintenance object to describe the operating status of the operation and maintenance object; and defining the operation and maintenance object methods to describe the operation services open to the operation and maintenance object. The operation and maintenance object methods are the operations supported by the operation and maintenance object.

[0021] Furthermore, the attributes of the operation and maintenance object in step 1 include the attribute name (PropName), the attribute code (PropCode), the attribute data type (DataType), the attribute label (Category), and the attribute data example (DataExample).

[0022] Specifically, the data type includes the data source type (SrcType), [script content | service name]) Furthermore, the indicators of the operation and maintenance object in step 1 include the indicator name (PropName), the indicator code (PropCode), the indicator data type (DataType), and the indicator data example (DataExample).

[0023] Furthermore, the operation and maintenance object methods include the operation name (OperName), operation identifier / code (OperCode), operation type (OperType), whether to initialize execution (IsInit), whether to feedback results (IsReturnResult), whether to push to the operation list display (IsDisplay), number of retries (RetryTimes), timeout (seconds) (Overtimes), request headers (Headers), input parameters (InParams), output parameters and echo (OutParams).

[0024] Furthermore, the object inherited in step 2 is called the base class, and the class that inherits properties, indicators, and methods is called the subclass; inheritance is divided into single inheritance and multiple inheritance. In single inheritance, the subclass inherits all properties, indicators, and methods of the parent class, and the subclass extends the properties, indicators, and methods of the subclass itself; in multiple inheritance, the subclass inherits the properties, indicators, and methods of multiple base classes. There is one main class among the multiple base classes. When the properties, indicators, and methods of other base classes conflict with the main class, the properties, indicators, and methods of the main class take precedence.

[0025] Specifically, the object being inherited is called a base class, parent class, or superclass, and the class that inherits properties, indicators, and methods is called a derived class or subclass. The main purpose of inheritance is to improve the reusability and maintainability of operation and maintenance objects.

[0026] In single inheritance, a subclass inherits all properties, indicators, and methods (supported operations) of its parent class. It can also set whether methods are initialized, whether results are returned, whether they are pushed to the operation list for display, and the method's input and output parameters. Subclasses extend their own properties, indicators, and methods (supported operations). Multiple inheritance follows the same inheritance pattern as single inheritance; with multiple base classes, the first-listed base class becomes the primary class. If there are conflicts in properties, indicators, or methods between base classes, the primary class's definition takes precedence.

[0027] Furthermore, production scenarios include topology presentation, fault and work order handling, risk operations, and human-computer interaction.

[0028] Furthermore, step 3 specifically includes the following steps: Step 3-1: Define the production operation and maintenance scenario based on the production scenario and define the application conditions that meet the production scenario; Step 3-2: Analyze and determine the cloud network operation and maintenance objects involved in the application scenario; Step 3-3: Obtain the operation and maintenance objects required by the application scenario and perform initialization operations, that is, the operations performed by the system background after matching the application scenario; Step 3-4: Push the operation and maintenance object methods, that is, the operations supported by the operation and maintenance object, to the user.

[0029] This invention adopts the above technical solution, employing object-oriented technology to abstract cloud network objects. It abstracts various cloud network operation and maintenance objects (e.g., network elements, boards, ports, relays, services, alarms, and work orders) into classes. Based on the inheritance characteristics of these classes, different subclasses are generated. For example, subclasses of network elements can include wireless network elements and transmission network elements. Wireless network elements can be further divided into wireless 4G network elements and wireless 5G network elements, which can then be further divided into various wireless 4G network elements. Each object abstractly defines attributes, indicators, and methods (supported operations) based on production requirements. This method provides unified management of cloud network objects, forming a "master resource" library of cloud network objects that can quickly respond to actual daily production requirements and be quickly incorporated into operation and maintenance scenarios.

[0030] This invention is suitable for operators to standardize the operation and maintenance management of cloud network objects. Its open capabilities can support scenarios such as network acceptance, fault handling, daily inspections, and risk operations.

[0031] Obviously, the described embodiments are part of the embodiments of the present application, rather than all of the embodiments. In the absence of conflict, the embodiments in the present application and the features in the embodiments can be combined with each other. The components of the embodiments of the present application generally described and shown in the drawings here can be arranged and designed in various different configurations. Therefore, the detailed description of the embodiments of the present application is not intended to limit the scope of the application for protection, but merely represents the selected embodiments of the present application. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without making creative work are within the scope of protection of this application.

Claims

1. A method for describing operation and maintenance objects based on object-oriented technology, characterized by: It includes the following steps: Step 1: Model the operation and maintenance objects based on the characteristics of cloud network operation and maintenance to describe the operation and maintenance objects; define the attributes of the operation and maintenance objects to describe the parameters of the operation and maintenance objects; define the indicators of the operation and maintenance objects to describe the operating status of the operation and maintenance objects; define the operation and maintenance object methods to describe the operation services exposed by the operation and maintenance objects. The operation and maintenance object methods are the operations supported by the operation and maintenance objects. Step 2: Analyze the relationships between the various operation and maintenance objects and associate the inheritance relationships between the various operation and maintenance objects. That is, based on the relationships between the operation and maintenance objects, construct the inheritance relationships of one operation and maintenance object to the attributes, indicators, and methods of another operation and maintenance object. Step 3: Apply the operation and maintenance object to the production scenario and use the attributes, indicators, and methods of the operation and maintenance object in the production scenario.

2. The method for describing operation and maintenance objects based on object-oriented technology according to claim 1, characterized in that: The attributes of the operation and maintenance object in step 1 include attribute name, attribute code, attribute data type, attribute label, and attribute data sample.

3. The method for describing operation and maintenance objects based on object-oriented technology according to claim 2, characterized in that: The data type includes the data source type.

4. The method for describing operation and maintenance objects based on object-oriented technology according to claim 1, characterized in that: The indicators of the operation and maintenance object in step 1 include the indicator name, indicator code, indicator data type, and indicator data sample.

5. The method for describing operation and maintenance objects based on object-oriented technology according to claim 1, characterized in that: The operation and maintenance object methods include the operation name, operation identifier, operation type, whether to initialize the execution, whether to feedback the results, whether to push to the operation list for display, number of retries, timeout period, request header, input parameters, output parameters and echo.

6. The method for describing operation and maintenance objects based on object-oriented technology according to claim 1, characterized in that: The object inherited in step 2 is called the base class, and the class that inherits properties, indicators, and methods is called the subclass; inheritance is divided into single inheritance and multiple inheritance. In single inheritance, the subclass inherits all properties, indicators, and methods of the parent class, and the subclass extends its own properties, indicators, and methods; in multiple inheritance, the subclass inherits the properties, indicators, and methods of multiple base classes. There is one main class among multiple base classes. When the properties, indicators, and methods of other base classes conflict with the main class, the properties, indicators, and methods of the main class take precedence.

7. The method for describing operation and maintenance objects based on object-oriented technology according to claim 1, characterized in that: Production scenarios include topology presentation, fault and work order handling, risk operations, and human-computer interaction.

8. The method for describing operation and maintenance objects based on object-oriented technology according to claim 1, characterized in that: Step 3 specifically includes the following steps: Step 3-1: Define the production operation and maintenance scenario based on the production scenario and define the application conditions that meet the production scenario; Step 3-2: Analyze and determine the cloud network operation and maintenance objects involved in the application scenario; Step 3-3: Obtain the operation and maintenance objects required by the application scenario and perform initialization operations, that is, the operations performed by the system background after matching the application scenario; Step 3-4: Push the operation and maintenance object methods, that is, the operations supported by the operation and maintenance object, to the user.

Images