Combined service description information processing method and device, electronic equipment and medium

Abstract

The invention discloses a combined service description information processing method and device, electronic equipment and a medium, and belongs to the technical field of communication. The method comprises the steps of obtaining network element change data reported by a network element; based on a pre-constructed target model file, obtaining combined service description information corresponding to the target management object class MOC, the combined service description information being used for representing associated information of the target MOC; and changing the combined service field data corresponding to the target MOC according to the network element change data and the combined service description information to obtain the latest combined service field data, so that a database which performs synchronous updating based on the latest combined service field data queries the combined service field data corresponding to the target MOC in real time. According to the invention, the real-time performance of querying the MO data can be improved.

Description

Technical Field

[0001] This application relates to the field of communication technologies, and in particular, to a method, apparatus, electronic device, and medium for processing combined service description information. Background Art

[0002] The network management part MOC (Managed Object Class) often needs to add new fields to describe the combined service information of the MO (Managed Object). These fields need to be real-time when used by users. Therefore, when performing addition, deletion, or modification operations on associated MO data, recalculation is required, and high timeliness is required without affecting the operation of MO data.

[0003] However, currently, the existing technologies for adding such combined service description information fields are divided into two types:

[0004] (1) Non-modeling, that is, no configuration fields are added to the network element model, and the combined service information fields are generated in real time when the user queries data.

[0005] (2) Modeling, that is, configuration fields are added to the network element model for the user to configure by themselves.

[0006] However, both of these processing methods have certain drawbacks. For the non-modeling method, since the combined service information fields are calculated in real time when the user queries data, this will result in low real-time performance of the user's query of MO data and affect the user experience. For the modeling method, since the existing network element modeling method is a flat modeling method, the modeling of each MOC is independent of each other, and the combined service description field information depends on the data information of multiple associated MOCs. Therefore, when the user modifies the associated MO data, the user also needs to perform manual associated calculation and modification on the affected description fields. The scenarios involved are numerous and the complexity is high, which will also result in low real-time performance of the user's query of MO data. Summary of the Invention

[0007] The main purpose of this application is to provide a method, apparatus, electronic device, and medium for processing combined service description information, aiming to solve the technical problem of low real-time performance of currently querying MO data.

[0008] To achieve the above object, this application provides a method for processing combined service description information, including:

[0009] Obtain the network element change data reported by the network element;

[0010] Based on a pre-constructed target model file, obtain the combined service description information corresponding to the target Managed Object Class (MOC), where the combined service description information is used to represent the associated information of the target MOC;

[0011] Based on the network element change data and the combined service description information, change the combined service field data corresponding to the target MOC to obtain the latest combined service field data, so that the database that is synchronously updated based on the latest combined service field data can query the combined service field data corresponding to the target MOC in real time.

[0012] In addition, to achieve the above object, the present application further provides a processing device for combined service description information, including:

[0013] An acquisition module, configured to acquire network element change data reported by a network element; based on a pre-constructed target model file, acquire combined service description information corresponding to a target management object class (MOC), where the combined service description information is used to characterize the association information of the target MOC;

[0014] A processing module, configured to change the combined service field data corresponding to the target MOC according to the network element change data and the combined service description information to obtain the latest combined service field data, so that the database that is synchronously updated based on the latest combined service field data can query the combined service field data corresponding to the target MOC in real time.

[0015] In addition, to achieve the above object, the present application further provides an electronic device, where the electronic device includes a processor and a memory, the memory stores a program or instruction that can run on the processor, and when the program or instruction is executed by the processor, it implements the processing method of combined service description information as described in any one of the above.

[0016] In addition, to achieve the above object, the present application further provides a computer-readable storage medium, where a program or instruction is stored on the computer-readable storage medium, and when the program or instruction is executed by a processor, it implements the processing method of combined service description information as described in any one of the above.

[0017] The embodiments of the present application provide a method, apparatus, electronic device, and medium for processing combined service description information. The technical solution of the embodiments of the present application is to obtain the network element change data reported by the network element, and based on the pre-constructed target model file, obtain the combined service description information corresponding to the target management object class (MOC). This combined service description information is used to represent the association information of the target MOC, so that the embodiments of the present application adopt a model-driven method to configure field association information, avoiding the inconvenience of the existing user operation to configure data, thus facilitating the user to dynamically configure the combined service description fields, with high scalability. Compared with the prior art of adding such combined service description information fields in a non-modeling way, the present embodiment improves the real-time performance of querying MO data. The present embodiment also performs change processing on the combined service field data corresponding to the target MOC according to the network element change data and the combined service description information to obtain the latest combined service field data, so that the database synchronized and updated based on the latest combined service field data can query the combined service field data corresponding to the target MOC in real time, thereby enabling the embodiments of the present application to implement a method of hierarchical control for warehousing based on a microservices architecture, improving the real-time performance of user operation of MO data. The target model file is constructed based on the association information corresponding to the target MOC. Compared with the prior art of adding such combined service description information fields in a modeling way, the embodiments of the present application can perform pre-cascading changes on the affected description fields through the pre-constructed target model file, where the cascading relationship of the combined description fields or attributes between each MOC has been predefined by the target model file, rather than the modeling relationships between each MOC being independent of each other, thus ensuring high timeliness when performing addition, deletion, or modification operations on the associated MO data, and further solving the technical problem of low real-time performance of currently querying MO data.

[0018] It is worth mentioning that since new fields need to be added in some MOCs to describe the combined service information of the MO, and these fields need to be real-time when the user uses them, recalculation is required when performing addition, deletion, or modification operations on the associated MO data, and high timeliness is required without affecting the operation of the MO data. In order to solve the problem of quickly and real-time viewing the key service information of the MO without affecting the user's operation of the MO, the embodiments of the present application obtain the combined service description information corresponding to the target MOC through the step of based on the pre-constructed target model file, model the combined service description fields outside the network element model modeling, and define all the association information of the combined service description fields in the model. The present embodiment adopts a model-driven method to configure field association information, solves the problem of flat modeling of the network element model, and at the same time this modeling method is also convenient for users to modify dynamically, with strong scalability. Brief Description of the Drawings

[0019] To more clearly illustrate the technical solutions in the embodiments of the present application or the prior art, the following will briefly introduce the drawings required for the description of the embodiments or the prior art. Obviously, the drawings in the following description are only some embodiments of the present application. For those of ordinary skill in the art, without creative efforts, other drawings can be obtained based on the structures shown in these drawings.

[0020] Figure 1 Fig. 4 shows a flowchart of a method for processing combined service description information provided by an exemplary embodiment of the present application;

[0021] Figure 2 Fig. 8 shows a product structure diagram provided by an exemplary embodiment of the present application;

[0022] Figure 3 Fig. 12 shows a flowchart of a method for parsing and obtaining model information provided by an exemplary embodiment of the present application;

[0023] Figure 4 Fig. 16 shows a flowchart of processing when the network element change type is network element data change provided by an exemplary embodiment of the present application;

[0024] Figure 5 Fig. 20 shows a flowchart of processing when the network element change type is network element first access or network element upgrade provided by an exemplary embodiment of the present application;

[0025] Figure 6 Fig. 24 shows a schematic diagram of functional modules of an embodiment of a processing device for combined service description information of the present application;

[0026] Figure 7 Fig. 28 shows a structural block diagram of an electronic device provided by an exemplary embodiment of the present application. Detailed Embodiments

[0027] Here, the exemplary embodiments will be described in detail, and the examples are shown in the drawings. When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. On the contrary, they are merely examples of devices and methods consistent with some aspects of the present application as detailed in the appended claims.

[0028] Currently, there are two ways for the prior art to add such combined service description information fields:

[0029] (1) Without modeling, that is, not adding configuration fields to the network element model, and generating combined service information fields in real time when the user queries data.

[0030] (2) Modeling, that is, adding configuration fields to the network element model for the user to configure by themselves.

[0031] However, both of these two processing methods have certain drawbacks. For the non-modeling method, since the combined service information fields will be calculated in real time when the user queries data, this will result in low real-time performance of the user's query of MO data, affecting the user experience. For the modeling method, since the existing network element modeling method is a flat modeling method and the modeling of each MOC is independent, and the combined service description field information depends on the data information of multiple associated MOCs, when the user modifies the associated MO data, the user also has to manually perform associated calculation and modification on the affected description fields. With many involved scenarios and high complexity, it will also lead to low real-time performance of the user's query of MO data.

[0032] Based on this, the technical solutions provided in the embodiments of the present application will be described below with reference to the accompanying drawings.

[0033] Figure 1 The flowchart of the method for processing combined service description information provided by an exemplary embodiment of the present application is shown. As Figure 1 shown, the method for processing combined service description information mainly includes the following steps.

[0034] Step S100, obtain the network element change data reported by the network element.

[0035] In this embodiment, the change types of the network element change data generally include three cases: the first access of the network element, the upgrade of the network element, and the change of the network element data.

[0036] As known to those skilled in the art, the first access of the network element means that a new network element is newly added to the network topology of the network element management system (i.e., the network management system). The upgrade of the network element means that the original network element in the network topology of the network element management system is upgraded to a new network element. The change of the network element data means that the data information mounted by the original network element in the network topology of the network element management system changes. It is easy to understand that both the first access of the network element and the upgrade of the network element cause changes in the network topology relationship of the network element management system (i.e., the network topology connecting each network element in the network element management system). The change of the network element data does not cause a change in the network topology relationship of the network element management system, but only performs a change process on the data information mounted by the network element in the network element management system.

[0037] Exemplarily, after obtaining the network element change data reported by the network element, it includes:

[0038] Step A10, synchronously update the obtained network element change data to the database.

[0039] In this embodiment, the obtained network element change data is synchronously updated to the database, so as to facilitate the data query device to query data information in real time from the synchronously updated database, thereby improving the real-time performance of querying MO data. Among them, the data information includes the combined service field data corresponding to the target MOC.

[0040] After step S100, step S200 is executed to obtain the combined service description information corresponding to the target management object class MOC based on the pre-constructed target model file. The combined service description information is used to represent the association information of the target MOC.

[0041] Among them, the target MOC refers to the MOC whose combined service field data needs to be changed.

[0042] In this embodiment, the target model file is constructed based on the association information corresponding to each MOC. Among them, the association information (specifically, it can be called the type of association information, and it can also be called the scenario type of association information) includes at least one of the following: association constant string, association with its own attributes, association with parent class attributes, association with subclass attributes, association with the MOC attributes pointed to by the ref attribute field of itself, association with its own enumerated value attributes, and association with the combined service description fields of other MOCs. The content of the model file supports configuring multiple types of association information, that is, the combined service description information can describe multiple types of association information, including: its own service combination, reference to the service combination of the parent MOC, reference to the service combination of the subclass MOC, reference to the service combination of the ref type MOC, and the combination superposition of multiple types among them.

[0043] Specifically, the specific introduction of these seven scenario types mainly included in the association information is as follows:

[0044] (1) Association constant string scenario

[0045] This scenario is for the case where the combined service description field of the MOC is a constant string. For this scenario, the modeling method is: define the MOC field, the combined service description field, and the object information field of the associated MOC. For the object information field of the associated MOC, the type field in the field needs to be defined as "constant", and the reference string field needs to be defined as a constant string.

[0046] (2) Association with its own attributes scenario

[0047] This scenario is for the case where the combined service description field of MOC associates with its own attributes, that is, the value of the combined service description field depends on (the "dependency" can also be called "association") the attribute value of its own MOC. For this scenario, the modeling method is as follows: Define the MOC field, the combined service description field, and the object information field that associates with the MOC. For the object information field that associates with the MOC, the type field in the field needs to be defined as "self", and the attribute field needs to be defined as a certain attribute of its own MOC.

[0048] (3) Scenario of associating with the attributes of the parent class (the parent node level is not limited)

[0049] This scenario is for the case where the combined service description field of MOC associates with the attributes of the parent class (the parent node level is not limited), that is, the value of the combined service description field depends on the attribute value of the parent class MOC. For this scenario, the modeling method is as follows: Define the MOC field, the combined service description field, and the object information field that associates with the MOC. For the object information field that associates with the MOC, the type field in the field needs to be defined as "parent", the MOC field needs to be defined as the parent class MOC path, and the attribute field needs to be defined as a certain attribute of the parent class MOC.

[0050] (4) Scenario of associating with the attributes of the subclass (the child node level is not limited)

[0051] This scenario is for the case where the combined service description field of MOC associates with the attributes of the subclass (the child node level is not limited), that is, the value of the combined service description field depends on the attribute value of the subclass MOC. For this scenario, the modeling method is as follows: Define the MOC field, the combined service description field, and the object information field that associates with the MOC. For the object information field that associates with the MOC, the type field in the field needs to be defined as "child", the MOC field needs to be defined as the subclass MOC path, and the attribute field needs to be defined as a certain attribute of the subclass MOC.

[0052] (5) Scenario of associating with the MOC attributes pointed to by the self-ref attribute field

[0053] This scenario is for the case where the combined service description field of MOC associates with the attributes of the MOC pointed to by its own ref attribute, that is, the value of the combined service description field depends on the attribute value of the MOC corresponding to the ref attribute. For this scenario, the modeling method is as follows: Define the MOC field, the combined service description field, and the object information field that associates with the MOC. For the object information field that associates with the MOC, the type field in the field needs to be defined as "ref", the ref attribute field needs to be defined as a certain ref attribute of its own MOC, the MOC field needs to be defined as the reference MOC path, and the attribute field needs to be defined as a certain attribute of the reference MOC.

[0054] (6) Internationalization scenario of associating with the self-enumeration value attribute

[0055] This scenario is for the case where the combined service description field of MOC is associated with its own MOC enumeration value attribute, that is, the value of the combined service description field depends on the internationalized value of its own MOC enumeration value attribute. For this scenario, the modeling method is as follows: Define the MOC field, the combined service description field, and the object information field associated with MOC. For the object information field associated with MOC, the type field in the field needs to be defined as "self", the attribute field needs to be defined as a certain enumeration value attribute of its own MOC, and the internationalized label field needs to be defined as "true".

[0056] (7) Scenario of combined service description field associated with other MOCs

[0057] This scenario is for the case where the combined service description field of MOC is associated with the combined service description field of other MOCs, that is, the value of the combined service description field depends on the value of the combined service description field of other MOCs. The combined service description field of other MOCs will also be defined in the model. This scenario is also called the cascade scenario, that is, the combined service description fields between MOCs are associated with each other. For example, the combined service description field of MOC1 depends on the combined service description field of MOC2, and the combined service description field of MOC2 depends on the attribute of MOC3.

[0058] It should be noted that these seven scenarios of association information can be defined in a superimposed manner in the model, that is, the combined service description field of a MOC can be defined to be associated with one or more scenarios. The modeling method is as follows: Define the MOC field, the combined service description field, and the object information field associated with MOC. The defined object information field associated with MOC is an array object, and each element object is defined to be associated with one scenario.

[0059] It is worth mentioning that the method for configuring field association information in the embodiments of the present application adopts a model-driven manner. Outside the network element model, a combined service description field is modeled to establish a set of service description files for MOs (i.e., target model files). The association information of the combined service description field is defined in the files. Users can dynamically configure this file, so that when adding, deleting, or modifying operations are performed on the associated MO data in the embodiments of the present application, recalculation is required, and efficient calculation can be performed in a model-driven manner, with high timeliness.

[0060] Exemplarily, based on the pre-constructed target model file, the steps for obtaining the combined service description information corresponding to the target management object class MOC include:

[0061] Step B10: Parse the pre-constructed target model file to obtain the combined service description information corresponding to the target management object class MOC.

[0062] In this embodiment, the target model file pre-constructed can be parsed through a model management tool to obtain the combined service description information corresponding to the target management object class MOC. Specifically, the target model file pre-constructed can be parsed through the model management tool, and the parsed information (this parsed information is the combined service description information corresponding to the target MOC) is cached. Meanwhile, the dynamic changes of the target model file are monitored through a monitoring mechanism to update the cache. Then, the data processor of the network management system obtains the cached parsed information to obtain the combined service description information corresponding to the target MOC.

[0063] After step S200, step S300 is executed. According to the network element change data and the combined service description information, the combined service field data corresponding to the target MOC is changed to obtain the latest combined service field data, so that the database that is synchronously updated based on the latest combined service field data can query the combined service field data corresponding to the target MOC in real time.

[0064] In this embodiment, according to the network element change data and the combined service description information, changing the combined service field data corresponding to the target MOC to obtain the latest combined service field data may specifically be: determining the original combined service field data corresponding to the target MOC before the change according to the combined service description information, determining the service field data to be changed that needs to be changed in the original combined service field data according to the network element change data, and changing the service field data to be changed to obtain the latest combined service field data.

[0065] After obtaining the latest combined service field data, the latest combined service field data can be synchronously updated to the database, so as to facilitate subsequent real-time querying of the combined service field data corresponding to the target MOC according to the synchronously updated database, thereby improving the real-time performance of querying MO data.

[0066] In a possible implementation manner, the step of the database that is synchronously updated based on the latest combined service field data querying the combined service field data corresponding to the target MOC in real time includes:

[0067] Step C10, determining the database to which the latest combined service field data is synchronously updated as a real-time update database, and real-time querying data information from the real-time update database through a data query device, where the data information includes the combined service field data corresponding to the target MOC.

[0068] In this embodiment, after the data information is queried through the data query device, the data information can be output and displayed through the display interface of the network management system.

[0069] The embodiments of the present application provide a method, an apparatus, an electronic device, and a medium for processing combined service description information. The technical solution of the embodiments of the present application is to obtain the network element change data reported by a network element, and based on a pre-constructed target model file, obtain the combined service description information corresponding to a target management object class (MOC). This combined service description information is used to represent the association information of the target MOC, so that the embodiments of the present application adopt a model-driven method to configure field association information, avoiding the inconvenience of the existing user operation for configuring data, thus facilitating the user to dynamically configure combined service description fields, with high scalability. Compared with the method of adding such combined service description information fields without modeling in the prior art, the present embodiment improves the real-time performance of querying MO data. The present embodiment also performs change processing on the combined service field data corresponding to the target MOC according to the network element change data and the combined service description information to obtain the latest combined service field data, so that the database synchronized and updated based on the latest combined service field data can query the combined service field data corresponding to the target MOC in real time, thereby enabling the embodiments of the present application to implement a method of hierarchical control for warehousing based on a microservices architecture, improving the real-time performance of user operation of MO data. The target model file is constructed based on the association information corresponding to the target MOC. Compared with the method of modeling to add such combined service description information fields in the prior art, the embodiments of the present application can perform pre-cascade changes on the affected description fields through the pre-constructed target model file, where the cascade relationship of the combined description fields or attributes between each MOC has been predefined by the target model file, rather than the modeling relationships between each MOC being independent of each other, thereby ensuring high timeliness when performing addition, deletion, or modification operations on associated MO data, and further solving the technical problem of low real-time performance of querying MO data currently.

[0070] It is worth mentioning that since new fields need to be added in some MOCs to describe the combined service information of MOs, and these fields need to be real-time when used by users, recalculation is required during addition, deletion, or modification operations on associated MO data, and high timeliness is required without affecting the operation of MO data. In order to solve the problem of quickly and real-time viewing the key service information of MOs without affecting user operation of MOs, the embodiments of the present application, through the step of obtaining the combined service description information corresponding to the target MOC based on a pre-constructed target model file, perform modeling on the combined service description fields outside the network element model, and define all the association information of the combined service description fields in the model. The present embodiment adopts a model-driven method to configure field association information, solves the problem of flat modeling of the network element model, and at the same time this modeling method is also convenient for users to modify dynamically, with strong scalability.

[0071] In a possible implementation, after step B10 of parsing a pre-constructed target model file to obtain combined service description information corresponding to a target management object class MOC, the following steps are included:

[0072] Step D10, dynamically monitor the target model file.

[0073] Step D20, after monitoring that the target model file has changed, re-parse the target model file to obtain the latest combined service description information.

[0074] Step D30, execute the step of changing the combined service field data corresponding to the target MOC according to the network element change data and the combined service description information.

[0075] In the embodiment of the present application, by dynamically monitoring the target model file, after monitoring that the target model file has changed, re-parse the target model file to obtain the latest combined service description information, and then execute the step of changing the combined service field data corresponding to the target MOC according to the network element change data and the combined service description information, so that if the user needs to add combined service description field definitions of other MOCs or modify the combined service description field definitions of existing MOCs in the target model file in the later stage, the user can directly modify the target model file, and then re-import the modified target model file into the model management tool. The model management tool will re-parse the target model file through the monitoring mechanism, and then update the original cache information. The data processor will also monitor the import of the model file. After monitoring, it will calculate the combined service description field values of the MOC according to the updated cache information in the model management, obtain the latest combined service description information, and then execute the step of changing the combined service field data corresponding to the target MOC according to the network element change data and the combined service description information, so as to ensure that after the user modifies the target model file, the combined service description field values of the existing network element MOCs can always be kept correct.

[0076] Further, after step D20 of re-parsing the target model file to obtain the latest combined service description information, the following steps are included:

[0077] Step E10, update the combined service field data of the target MOC according to the latest combined service description information, and synchronously update the updated combined service description fields to the database.

[0078] In this embodiment, according to the latest combined service description information, the combined service description fields of the target MOC are updated, and the updated combined service description fields are synchronously updated to the database, so as to facilitate the data query device to query data information in real time from the synchronously updated database, thereby improving the real-time performance of querying MO data.

[0079] In a possible implementation manner, the step of changing the combined service field data corresponding to the target MOC according to the network element change data and the combined service description information to obtain the latest combined service field data includes:

[0080] Step F10, determining the change requirements corresponding to the combined service field data according to the network element change data and the combined service description information.

[0081] Step F20, assembling the network element change data of the combined service field data based on the content of the change requirements to obtain change information.

[0082] Step F30, changing the combined service field data corresponding to the target MOC according to the change information and the combined service description information to obtain the latest combined service field data.

[0083] In this embodiment, specifically, it is possible to determine whether there are change requirements for the combined service field data according to the network element change data and the combined service description information. After determining that there are change requirements, the network element change data that generates change requirements for the combined service field data is assembled to obtain change information (that is, based on the content of the change requirements, the network element change data of the combined service field data is assembled to obtain change information), and then according to the change information and the combined service description information, the combined service field data corresponding to the target MOC is changed to obtain the latest combined service field data.

[0084] In this embodiment, according to the network element change data and the combined service description information, the change requirements corresponding to the combined service field data are determined. Based on the content of the change requirements, the network element change data of the combined service field data is assembled to obtain change information. Then, according to the change information and the combined service description information, the combined service field data corresponding to the target MOC is changed to obtain the latest combined service field data, thereby realizing the processing of the change information. By calculating the value of the combined service description field and updating it into the database, the value of the combined service description field is changed in real time accordingly, enabling users to view the latest value of the service description field in real time and improving the timeliness of querying MO data.

[0085] In a possible implementation manner, the step of changing the combined service field data corresponding to the target MOC according to the change information and the combined service description information to obtain the latest combined service field data includes:

[0086] Step G10: Determine the combined service description field of the target MOC with requirement changes according to the change information, and use the combined service description field of the target MOC with requirement changes as the target service field data.

[0087] Step G20: Change the target service field data, and update the changed target service field data to the database.

[0088] Step G30: Use the changed target service field data as the changed service field data, and determine the target service description field cascaded by the changed service field data according to the combined service description information, where the target service description field is the combined service description field of other target MOCs.

[0089] Step G40: According to the hierarchical dependency relationship corresponding to the cascaded target service description field, hierarchically update the changed target service description field to the database in sequence for each round of change.

[0090] In this embodiment, by determining the combined service description field of the target MOC with requirement changes according to the change information, using the combined service description field of the target MOC with requirement changes as the target service field data, changing the target service field data, updating the changed target service field data to the database, using the changed target service field data as the changed service field data, then determining the target service description field cascaded by the changed service field data according to the combined service description information, where the target service description field is the combined service description field of other target MOCs, and hierarchically updating the changed target service description field to the database in sequence according to the hierarchical dependency relationship corresponding to the cascaded target service description field, the embodiment of the present application improves the calculation efficiency by adopting a method of hierarchical control for warehousing based on a microservice architecture. By performing hierarchical processing on the data, the MO data fields are preferentially processed to ensure that the operations of the MO data fields are not affected. By performing hierarchical calculation processing on the combined service description fields, this embodiment can effectively solve the problem of low real-time performance of user querying MO data.

[0091] To help understand the technical concept of the embodiment of the present application, a specific Example 1 is listed. Figure 2 The product structure diagram provided by an exemplary embodiment of the present application is shown. The following is a detailed introduction in combination with Figure 2 :

[0092] The components described in the embodiments of this application are divided into two modules. One is the network management system, and the other is the network element system. The components are introduced as follows:

[0093] Model file (i.e., the target model file): Model the combined service description fields, supporting dynamic configuration. The content of the model file supports configuring multiple association types, that is, the combined service description fields can describe multiple association information, including: its own service combination, referencing the parent MOC service combination, referencing the child MOC service combination, referencing the ref type MOC service combination, and the superposition of various type combinations, etc.

[0094] Model management (i.e., the above-mentioned model management tool): Parse the network element model and the combined service description field model (the combined service description field model is the target model file), cache the model information after parsing (here the model information is the combined service description information of MOC), and update the cache information by listening to the changes of the model file through the listening mechanism.

[0095] Data processor: mainly processes the messages on the network element side (i.e., network element change data), and at the same time, with the help of the model information cached by the model management, calculates the values of the combined service description fields (i.e., the values of the above-mentioned target service description fields) level by level, and then stores them in the database corresponding to the levels. The data processor includes: a network element data processing module, a change message processing module, and a combined service data processing module. The network element data processing module processes and stores the network element reported data (i.e., network element change data) of the existing network element system. The change message processing module assembles and sends the change messages that affect the combined service field data (i.e., the above-mentioned change information). The combined service data processing module processes the change messages, calculates the values of the combined service description fields (i.e., the values of the above-mentioned target service description fields), and updates and stores them. The data processor realizes the hierarchical processing method through the change message processing module and the combined service data processing module, and calculates the values of the combined service description fields of the cascading dependent MOC in turn and cyclically.

[0096] Data query tool: mainly provides the data query function, and queries data information from the database.

[0097] Network element: the service processor on the network element side (or can also be called the service processor of the network element system), mainly processes network element services and reports network element side data information to the network management system.

[0098] User interface: the interaction interface between the user and the network management system. This user interface provides the display information of MO data and combined service description field data.

[0099] It should be noted that the many details described in the first specific embodiment only help to understand the technical concept of the present application and do not constitute a limitation to the present application. Based on this technical concept of the present application, more forms of simple transformation should be within the protection scope of the present application.

[0100] In an implementable manner, the step of hierarchically updating the target service description fields changed in each round to the database according to the hierarchical dependency relationship corresponding to the cascaded target service description fields includes:

[0101] Step H10, determine whether there is a directly associated target service description field for the changed service field data according to the hierarchical dependency relationship corresponding to the cascaded target service description fields.

[0102] Step H20, in the case where there is a directly associated target service description field, perform the current round of change on the directly associated target service description field according to the combined service description information, and update the target service description field after the current round of change to the database.

[0103] Step H30, use the target service description field after the current round of change as the new changed service field data, and return to execute the step of determining whether there is a directly associated target service description field for the changed service field data according to the hierarchical dependency relationship corresponding to the cascaded target service description fields until there is no directly associated target service description field for the changed service field data.

[0104] In the embodiment of the present application, by determining whether there is a directly associated target service description field for the changed service field data according to the hierarchical dependency relationship corresponding to the cascaded target service description fields, in the case where there is a directly associated target service description field, performing the current round of change on the directly associated target service description field according to the combined service description information, updating the target service description field after the current round of change to the database, and then using the target service description field after the current round of change as the new changed service field data, and returning to execute the step of determining whether there is a directly associated target service description field for the changed service field data according to the hierarchical dependency relationship corresponding to the cascaded target service description fields until there is no directly associated target service description field for the changed service field data, it is possible to calculate the combined service description fields in a hierarchical control warehousing manner, which can not only ensure the timeliness of the fields, but also ensure high timeliness when performing addition, deletion, or modification operations on the associated MO data.

[0105] To help understand the technical concept of the embodiment of the present application, a second specific embodiment is listed, and the specific implementation steps include:

[0106] Step 1: Parse the model file

[0107] The model management parses the model file (i.e., the target model file) of the combined service description field, caches the parsed information, and listens for dynamic changes in the model file through a listening mechanism to update the cache accordingly.

[0108] Step 2: Report data information

[0109] The network element system (specifically, the service processor of the network element system) reports data to the data processor.

[0110] Step 3: Obtain combined service description field information

[0111] The data processor obtains the combined service description field model information (i.e., the combined service description information of the MOC) from the model management.

[0112] Step 4: Hierarchically calculate combined service description field data

[0113] The data processor mainly processes and stores the data reported by the network element and the values of the combined service description fields into the database. The data processor includes three functional modules: the network element data processing module, the change message processing module, and the combined service data processing module. The network element data processing module processes and stores the changed data reported by the network element (i.e., the network element change data) into the database. The change message processing module determines whether the changed data stored in the database will directly affect the combined service description fields of the MOC (i.e., determines whether there is a directly associated target service description field for the changed service field data) based on the combined service description field model information (i.e., the combined service description information of the MOC obtained based on the pre-constructed target model file), assembles the changed data that affects the values of the combined service description fields (i.e., assembles the network element change data of the combined service field data based on the content of the change requirements of the combined service field data to obtain the change information), and sends the change message (i.e., the change information). The combined service data processing module processes the received change message, calculates the values of the combined service description fields and updates and stores them into the database, and then the change message processing module processes based on the changed combined service description field data stored in the database (i.e., the above-mentioned changed service field data), and calculates and cascades the values of the combined service description fields of the MOC in a loop in turn.

[0114] Step 5: Display combined service description field data

[0115] The user can obtain the MO data and the corresponding combined service description field data through the data query tool in the user interface.

[0116] Figure 3 The flowchart of parsing and obtaining model information provided by an exemplary embodiment of the present application is shown as Figure 3As shown, the operation steps of Step 1 include:

[0117] Among them, the overall process of model file parsing is as follows: (1) Import the model file (i.e., the target model file) modeled based on the association information of the target MOC. (2) Parse and process the model file to obtain model information (i.e., the combined service description information of the MOC). (3) Cache the model information.

[0118] Specifically, first, it is necessary to register the model file listening mechanism, then import the model file, parse the model file, and cache the parsed model information. After the model file is dynamically modified, the model file can be re-parsed through the listening mechanism, and the cache information (i.e., update the cached model information) can be updated.

[0119] In this embodiment, the overall modeling idea of the model file: Model the combined service description fields (the combined service description fields are the combined service description information) of the involved MOCs outside the network element model. The modeled field information includes: MOC fields, combined service description fields, and object information fields associated with the MOC. Among them, the object information fields associated with the MOC include type fields, MOC fields, attribute fields, ref attribute fields, reference string fields, and internationalization label fields. The meanings of each modeled field: The MOC field represents the defined MOC path. The combined service description field represents the format of the defined combined service description field. The object information field associated with the MOC represents the MOC information associated with the defined combined service description field.

[0120] The modeling scenarios mainly include the following seven scenarios:

[0121] (1) Association with constant string scenario

[0122] This scenario is for the case where the combined service description field of the MOC is a constant string. For this scenario, the modeling method is: Define MOC fields, combined service description fields, and object information fields associated with the MOC. For the object information fields associated with the MOC, the type field in the field needs to be defined as "constant" and the reference string field needs to be defined as a constant string.

[0123] (2) Association with its own attribute scenario

[0124] This scenario is for the case where the combined service description field of MOC associates with its own attributes, that is, the value of the combined service description field depends on the attribute value of its own MOC. For this scenario, the modeling method is as follows: Define the MOC field, the combined service description field, and the object information field associated with the MOC. For the object information field associated with the MOC, the type field in the field needs to be defined as "self", and the attribute field needs to be defined as a certain attribute of its own MOC.

[0125] (3) Scenario of associating with the attributes of the parent class (regardless of the parent node level)

[0126] This scenario is for the case where the combined service description field of MOC associates with the attributes of the parent class (regardless of the parent node level), that is, the value of the combined service description field depends on the attribute value of the parent class MOC. For this scenario, the modeling method is as follows: Define the MOC field, the combined service description field, and the object information field associated with the MOC. For the object information field associated with the MOC, the type field in the field needs to be defined as "parent", the MOC field needs to be defined as the parent class MOC path, and the attribute field needs to be defined as a certain attribute of the parent class MOC.

[0127] (4) Scenario of associating with the attributes of the subclass (regardless of the child node level)

[0128] This scenario is for the case where the combined service description field of MOC associates with the attributes of the subclass (regardless of the child node level), that is, the value of the combined service description field depends on the attribute value of the subclass MOC. For this scenario, the modeling method is as follows: Define the MOC field, the combined service description field, and the object information field associated with the MOC. For the object information field associated with the MOC, the type field in the field needs to be defined as "child", the MOC field needs to be defined as the subclass MOC path, and the attribute field needs to be defined as a certain attribute of the subclass MOC.

[0129] (5) Scenario of associating with the MOC attributes pointed to by the self ref attribute field

[0130] This scenario is for the case where the combined service description field of MOC associates with the attributes of the MOC pointed to by its own ref attribute, that is, the value of the combined service description field depends on the attribute value of the MOC corresponding to the ref attribute. For this scenario, the modeling method is as follows: Define the MOC field, the combined service description field, and the object information field associated with the MOC. For the object information field associated with the MOC, the type field in the field needs to be defined as "ref", the ref attribute field needs to be defined as a certain ref attribute of its own MOC, the MOC field needs to be defined as the reference MOC path, and the attribute field needs to be defined as a certain attribute of the reference MOC.

[0131] (6) Internationalization scenario of associating with the self-enumeration value attributes

[0132] This scenario is for the case where the combined service description field of MOC associates with its own MOC enumeration value attribute, that is, the value of the combined service description field depends on the internationalized value of its own MOC enumeration value attribute. For this scenario, the modeling method is as follows: Define the MOC field, the combined service description field, and the object information field associated with the MOC. For the object information field associated with the MOC, the type field in the field needs to be defined as "self", the attribute field needs to be defined as a certain enumeration value attribute of its own MOC, and the internationalized label field needs to be defined as "true".

[0133] (7) Scenario of combined service description field associated with other MOCs

[0134] This scenario is for the case where the combined service description field of MOC associates with the combined service description field of other MOCs, that is, the value of the combined service description field depends on the value of the combined service description field of other MOCs. The combined service description field of other MOCs will also be defined in the model. This scenario is also called the cascading scenario, that is, the combined service description fields between MOCs are associated with each other. For example, the combined service description field of MOC1 depends on the combined service description field of MOC2, and the combined service description field of MOC2 depends on the attribute of MOC3.

[0135] It should be noted that these seven association scenarios can be defined in a superimposed manner in the model, that is, the combined service description field of a MOC can be defined to associate with one or more scenarios. The modeling method is as follows: Define the MOC field, the combined service description field, and the object information field associated with the MOC. The defined object information field associated with the MOC is an array object, and each element object is defined to associate with one scenario.

[0136] This modeling method of the combined service description field can not only expand the description scope of the combined service description field, but also facilitate users to perform dynamic configuration.

[0137] In this embodiment, the implementation of dynamic configuration is achieved by means of the function of parsing the model file. The overall process of dynamic configuration is as follows: The user imports the model file (i.e., the target model file) that defines the combined service description fields into the network management system (i.e., the network management system). The model management parses the model file and caches the parsed model information. The data processor module listens for the import of the model file. After detecting the import of the model file, the data processor module obtains the model cache information from the model management to calculate the combined service description field values of the existing network elements MOC in the network management. The content in the following specific embodiments describes in detail the processing flow when the network element data changes, the network element is first accessed, or the network element is upgraded, which will not be elaborated here. If the user needs to add new definitions of the combined service description fields of other MOCs or modify the existing definitions of the combined service description fields of MOCs in the model file in the later stage, the user can directly modify the model file and then re-import the modified model file into the model management. The model management will re-parse the model file through the listening mechanism and then update the original cache information. The data processor module also listens for the import of the model file. After detecting it, it will calculate the combined service description field values of MOCs according to the updated cache information in the model management, so as to ensure that the combined service description field values of the existing network elements MOC are always correct after the user modifies the model file.

[0138] It should be noted that the many details described in this specific embodiment 2 only help to understand the technical concept of this application and do not constitute a limitation to this application. Based on this technical concept of this application, more forms of simple transformations should be within the protection scope of this application.

[0139] In a possible implementation manner, before the step of changing the target service field data, it further includes:

[0140] Step I10, when the network element change type corresponding to the network element change data is network element data change, trigger the execution of: the step of changing the target service field data.

[0141] As is known to those skilled in the art, when the network element change type corresponding to the network element change data is network element data change, it indicates that the network topology relationship of the network element management system has not changed. That is, it often means that the amount of network element change data is small, resulting in fewer times of hierarchical update and storage. It will not reduce the efficiency due to the relatively large number of storage operations during the hierarchical storage process and affect the real-time performance of users querying MO data. At this time, directly adopting the method of hierarchical control and storage based on the microservice architecture to improve the computing efficiency. By classifying the data, first processing the MO data fields to ensure that the operations on the MO data fields are not affected, and then performing hierarchical calculation and processing on the combined service description fields. The change data calculated in each round can be updated and stored first to improve the timeliness of database update, so that users can query MO data in the database in real time, thereby effectively solving the problem of low real-time performance of users querying MO data.

[0142] To further assist in understanding the technical concept of the embodiments of the present application, specific embodiment three is listed to introduce steps 2, 3, and 4 in the above specific embodiment two in detail, including:

[0143] First, the network element reporting data information is divided into three cases: the network element is newly connected, the network element is upgraded, and the network element data changes. The processing methods for network element data changes are different from those for the network element being newly connected and the network element being upgraded, and need to be described separately.

[0144] Before elaborating on the processing methods respectively, the concepts of the direct impact (i.e., the above-mentioned direct association) and the indirect impact (i.e., the indirect association) of the combined service description fields are elaborated first. In this embodiment, the cascade scenario is used to illustrate the concepts of the direct impact and the indirect impact. Among them, the seventh scenario of the combined service description field associated with other MOCs is a simple cascade scenario. For example, define a two-layer cascade dependency. The combined service description field of MOC1 depends on the combined service description field of MOC2, and the combined service description field of MOC2 depends on the attributes of MOC3. When the corresponding attribute value of MOC3 changes, it will directly affect (also known as direct association) the value of the combined service description field of MOC2, and at the same time will indirectly affect (also known as indirect association) the value of the combined service description field of MOC1. When the value of the combined service description field of MOC2 changes, it will directly affect the value of the combined service description field of MOC1. Therefore, the idea of hierarchical cyclic calculation mentioned in the embodiment of this application is: when the corresponding attribute value of MOC3 changes, first update and store it in the database, and then judge according to the model information that it will directly affect the value of the combined service description field of MOC2. Therefore, it is necessary to calculate the value of the combined service description field of MOC2 and update the value of the combined service description field of MOC2 into the database. Then, judge according to the model information that the value of the combined service description field of MOC2 will directly affect the value of the combined service description field of MOC1. Therefore, it is necessary to calculate the value of the combined service description field of MOC1. Through two rounds of calculation, all the values of the combined service description fields in the cascade scenario are updated. The calculation method for each round is calculated according to the defined model information.

[0145] The calculation idea for the multi-layer cascade dependency scenario with more than two layers is the same as above. For example, define a four-layer cascade dependency scenario: the combined service description field of MOC1 depends on the combined service description field of MOC2, the combined service description field of MOC2 depends on the combined service description field of MOC3, the combined service description field of MOC3 depends on the combined service description field of MOC4, and the combined service description field of MOC4 depends on its own attribute value. When the corresponding attribute value of MOC4 changes, first calculate the value of the combined service description field that directly affects MOC4. Then, since the value of the combined service description field of MOC4 directly affects the combined service description field of MOC3, the value of the combined service description field of MOC3 is calculated in the second round. Then, since the value of the combined service description field of MOC3 directly affects the combined service description field of MOC2, the value of the combined service description field of MOC2 is calculated in the third round. Then, since the value of the combined service description field of MOC2 directly affects the combined service description field of MOC1, the value of the combined service description field of MOC1 is calculated in the fourth round. Since the value of the combined service description field of MOC1 will not directly affect the combined service description fields of other MOCs, the cyclic calculation ends.

[0146] This embodiment introduces the concepts of direct impact (i.e., direct association) and indirect impact (i.e., indirect association) and a method of cyclically calculating the combined service description field. Next, this embodiment first describes a method for processing network data changes:

[0147] Please refer to Figure 4 , Figure 4 A processing flow chart is shown when the network element change type provided by an exemplary embodiment of the present application is a network element data change.

[0148] Specifically, when the network element data is changed, the network element reports the data to the data processor. The network element data processing module in the data processor first updates the changed network element data (i.e., network element change data) to the database (specifically, the target service field data is changed, and the changed target service field data is first updated to the database). Then, the change message processing module queries the combined service description field model information through the model management (i.e., based on the pre-built target model file, obtains the combined service description information), and determines whether the stored change data will directly affect the combined service description field of itself or other related MOCs according to the model information (i.e., according to the hierarchical dependency relationship corresponding to the cascaded target service description field in the model information, determine whether the changed service field data has a directly related target service description field). If not, the processing flow is terminated, otherwise, the change data affecting the combined service description field data is assembled and sent. The combined service data processing module processes the received change message: first, the dependent data required by the affected MOC in the model information is queried through the data query device, and then the combined service description field information value of the affected MOC is calculated based on the change data and the queried dependent data, and finally the calculated data is stored in the database. After the combined business data processing module completes processing, it then loops back to the message processing module. The message processing module determines whether the changed combined business description field data will directly affect the combined business description fields of other related MOCs. If so, it is necessary to recalculate and update the combined business description fields of other related MOCs, and repeat the calculation in a loop until the data will not directly affect the combined business description fields of other MOCs (that is, the above-mentioned "until the changed business field data does not have a directly related target business description field").

[0149] It should be noted that the many details described in the third specific embodiment are only helpful for understanding the technical concept of the present application and do not constitute a limitation of the present application. More simple transformations based on the technical concept of the present application should all be within the scope of protection of the present application.

[0150] In another possible implementation manner, before the step of changing the target business field data, the step further includes:

[0151] Step J10: When the network element change type corresponding to the network element change data is the first access of the network element or the upgrade of the network element, perform a full MOC change on the target service field data, and update all the target service field data after the full MOC change to the database. Herein, the full MOC change refers to changing all the combined service description fields of the target MOCs in the target model file.

[0152] As known to those skilled in the art, when the network element change type corresponding to the network element change data is the first access of the network element or the upgrade of the network element, it indicates that the network topology relationship of the network element management system has changed. That is, it often means that the data volume of the network element change data is large, resulting in a large number of hierarchical update and storage operations. Too many storage operations will reduce the efficiency and affect the real-time performance of users querying MO data.

[0153] Based on this, in this embodiment, when the network element change type corresponding to the network element change data is the first access of the network element or the upgrade of the network element, first perform a full MOC change on the target service field data, and update all the target service field data after the full MOC change to the database, and then execute the step of changing the target service field data. Herein, the full MOC change refers to changing all the combined service description fields of the target MOCs in the target model file, thereby avoiding the situation of low efficiency caused by too many repeated database import operations during hierarchical update and storage due to excessive data volume. In this embodiment, after sequentially changing all the combined service description fields of the target MOCs in the target model file, all are imported into the database together, which further ensures high timeliness when performing addition, deletion, or modification operations on associated MO data and improves the real-time performance of querying MO data.

[0154] In addition, it should be noted that after updating all the target service field data after the full MOC change to the database, if the stored combined service description field data directly affects the values of the combined service description fields of other associated MOCs, continue to process according to the above-mentioned network element data change processing flow, that is, continue to adopt the hierarchical control storage method, and the change data calculated in each round can be updated and stored first to improve the timeliness of update and storage, so that users can query MO data in the database in real time.

[0155] To further assist in understanding the technical concept of the embodiments of the present application, specific Example 4 is listed. Please refer to Figure 5 , Figure 5 FIG. shows a processing flow chart when the network element change type provided by an exemplary embodiment of the present application is the first access of the network element or the upgrade of the network element, which specifically includes:

[0156] When a network element is first accessed or upgraded, the network element system reports data to the data processor. The network element data processing module in the data processor first stores all the network element data in the database, and then the change message processing module sends a special message. When the combined service data processing module receives the special message, it first queries the combined service description field model information through model management, and then queries all the dependent data required for the MOCs defined in the model information through the data query (i.e., the above-mentioned "determine the target service description field for cascading the changed service field data according to the combined service description information"). Finally, it calculates the combined service description field values of all the MOCs defined in the model based on the dependent data, and stores the calculated combined service description field values in the database (i.e., the above-mentioned "in the case where the network element change type corresponding to the network element changed data is the first access of the network element or the upgrade of the network element, perform the change of the full MOC on the target service field data, and update all the target service field data after the change of the full MOC to the database"). Then the change message processing module will judge the combined service description field data stored in the database to determine whether the data will directly affect the combined service description field values of other associated MOCs. If there is an impact, it will continue to be processed according to the above-mentioned network element data change processing process.

[0157] In addition, step 5 in the above-mentioned specific embodiment 2 may specifically include:

[0158] The user views the MO data information and the corresponding combined service description field information on the user interface, and can also perform addition, deletion, and modification operations on the MO data on the user interface. After the operations are executed, the combined service description field values also change accordingly, enabling the user to view the latest values of the service description fields in real time.

[0159] It should be noted that the many details described in this specific embodiment 4 only help to understand the technical concept of the present application and do not constitute a limitation to the present application. Based on this technical concept of the present application, more forms of simple transformations should be within the protection scope of the present application.

[0160] In addition, the embodiment of the present application also proposes a processing device for combined service description information. Refer to Figure 6 , Figure 6 which shows a schematic diagram of the functional modules of an embodiment of the processing device for combined service description information of the present application.

[0161] In this embodiment, the processing device for combined service description information includes:

[0162] An acquisition module 10, configured to acquire the network element change data reported by the network element; and based on a pre-constructed target model file, acquire the combined service description information corresponding to the target management object class MOC, where the combined service description information is used to represent the association information of the target MOC.

[0163] The processing module 20 is configured to change the combined service field data corresponding to the target MOC according to the network element change data and the combined service description information, so as to obtain the latest combined service field data, so that the database synchronously updated based on the latest combined service field data can query the combined service field data corresponding to the target MOC in real time.

[0164] In some embodiments, the processing module 20 is further configured to:

[0165] Determine the change requirements corresponding to the combined service field data according to the network element change data and the combined service description information;

[0166] Assemble the network element change data of the combined service field data based on the content of the change requirements to obtain change information;

[0167] Change the combined service field data corresponding to the target MOC according to the change information and the combined service description information to obtain the latest combined service field data.

[0168] In some embodiments, the processing module 20 is further configured to:

[0169] Determine the combined service description fields of the target MOC with changed requirements according to the change information, and use the combined service description fields of the target MOC with changed requirements as the target service field data;

[0170] Change the target service field data and update the changed target service field data to the database;

[0171] Use the changed target service field data as the changed service field data, and determine the target service description fields cascaded by the changed service field data according to the combined service description information, where the target service description fields are the combined service description fields of other target MOCs;

[0172] Update the target service description fields changed in each round to the database level by level according to the hierarchical dependency relationship corresponding to the cascaded target service description fields.

[0173] In some embodiments, the processing module 20 is further configured to:

[0174] Determine whether there are directly associated target service description fields for the changed service field data according to the hierarchical dependency relationship corresponding to the cascaded target service description fields;

[0175] In the case where there are target service description fields with direct associations, according to the combined service description information, perform changes to the directly associated target service description fields in the current round, and update the target service description fields after the changes in the current round to the database;

[0176] Use the target service description fields after the changes in the current round as new changed service field data, and return to execute the step of determining whether there are directly associated target service description fields for the changed service field data according to the hierarchical dependency relationship corresponding to the cascaded target service description fields, until there are no directly associated target service description fields for the changed service field data.

[0177] In some embodiments, the processing module 20 is further configured to:

[0178] In the case where the network element change type corresponding to the network element change data is network element first access or network element upgrade, perform changes to all target MOCs for the target service field data, and update all the target service field data after the changes to all target MOCs to the database, where the change to all target MOCs refers to changing all combined service description fields of the target MOCs in the target model file.

[0179] In some embodiments, the obtaining module 10 is further configured to:

[0180] Synchronously update the obtained network element change data to the database.

[0181] In some embodiments, the obtaining module 10 is further configured to:

[0182] Parse the pre-constructed target model file to obtain combined service description information corresponding to the target management object class MOC.

[0183] In some embodiments, the obtaining module 10 is further configured to:

[0184] Dynamically monitor the target model file;

[0185] After monitoring that the target model file has changed, re-parse the target model file to obtain the latest combined service description information;

[0186] Execute the step of changing the combined service field data corresponding to the target MOC according to the network element change data and the combined service description information.

[0187] In some embodiments, the obtaining module 10 is further configured to:

[0188] Update the combined service field data of the target MOC according to the latest combined service description information, and synchronously update the updated combined service description field to the database.

[0189] In some embodiments, the association information includes:

[0190] At least one of an association constant string, an associated self-attribute, an associated parent-class attribute, an associated subclass attribute, an MOC attribute pointed to by an associated self-ref attribute field, an associated self-enumeration value attribute, and a combined service description field of an associated other MOC.

[0191] The processing device for combined service description information provided in this embodiment and the processing method for combined service description information provided in the above embodiment belong to the same inventive concept. Technical details not described in detail in this embodiment can be referred to the embodiments of the processing method for combined service description information above, and this embodiment has the same beneficial effects as the embodiments of the processing method for combined service description information, which will not be elaborated here.

[0192] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separated, that is, they may be located in one place or distributed to multiple network units. Some or all of the modules can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0193] Figure 7 The block diagram of the electronic device 1800 shown in an exemplary embodiment of the present application is shown. As Figure 7 shown, the electronic device can be implemented as the cloud terminal management platform or the cloud server with cloud terminals in the above solution of the present application, such as a network management platform (or called a network management system), or more specifically, the central processing unit of the gateway platform. This embodiment does not make specific limitations in this regard. The electronic device 1800 includes a central processing unit (CPU) 1801, a system memory 1804 including a random access memory (RAM) 1802 and a read-only memory (ROM) 1803, and a system bus 1805 connecting the system memory 1804 and the central processing unit 1801. The electronic device 1800 also includes a storage device 1806 for storing an operating system 1809, a client 1810, and other program modules 1811.

[0194] Without loss of generality, the computer-readable medium may include a computer storage medium and a communication medium. The computer storage medium includes volatile and non-volatile, removable and non-removable media implemented by any method or technology for storing information such as computer-readable instructions, data structures, program modules, or other data. The computer storage medium includes RAM, ROM, erasable programmable read-only memory (EPROM), electrically-erasable programmable read-only memory (EEPROM), flash memory or other solid-state storage technologies, CD-ROM, digital versatile disc (DVD) or other optical storage, magnetic tape cartridges, tapes, disk storage or other magnetic storage devices. Of course, those skilled in the art will appreciate that the computer storage medium is not limited to the above several types. The above system memory 1804 and storage device 1806 may be collectively referred to as memory.

[0195] According to various embodiments of the present disclosure, the electronic device 1800 may also operate by connecting to a remote computer on a network such as the Internet. That is, the electronic device 1800 may be connected to the network 1808 through the network interface unit 1807 connected to the system bus 1805, or in other words, the network interface unit 1807 may also be used to connect to other types of networks or remote computer systems (not shown).

[0196] The memory further includes at least one instruction, at least one program, a code set or an instruction set, and the at least one instruction, at least one program, code set or instruction set is stored in the memory. The central processing unit 1801 implements all or part of the steps in the processing method of the combined service description information shown in the above various embodiments by executing the at least one instruction, at least one program, code set or instruction set.

[0197] In an exemplary embodiment, a computer-readable storage medium is further provided. At least one computer program is stored in the computer-readable storage medium, and the computer program is loaded and executed by a processor to implement all or part of the steps in the above-mentioned processing method of combined service description information, or to implement all or part of the steps in the above-mentioned processing method of combined service description information. For example, the computer-readable storage medium may be a Read-Only Memory (ROM), a Random Access Memory (RAM), a Compact Disc Read-Only Memory (CD-ROM), magnetic tape, floppy disk, and optical data storage device, etc.

[0198] In an exemplary embodiment, a computer program product is further provided. The computer program product includes at least one computer program, and the computer program is loaded and executed by a processor to implement all or part of the steps in the processing method of combined service description information shown in any of the above embodiments, or all or part of the steps in the processing method of combined service description information.

[0199] After considering the specification and practicing the invention disclosed herein, those skilled in the art will readily conceive of other embodiments of the present application. The present application is intended to cover any variations, uses, or adaptations of the present application, which follow the general principles of the present application and include well-known knowledge or conventional technical means in the technical field not disclosed in the present application. The specification and embodiments are only regarded as exemplary, and the true scope and spirit of the present application are pointed out by the claims.

[0200] It should be understood that the present application is not limited to the exact structures described above and shown in the drawings, and various modifications and changes can be made without departing from its scope. The scope of the present application is only limited by the appended claims.

Claims

1. A method for processing combined service description information, characterized in that, it includes: Obtain the network element change data reported by the network element; Based on the pre-constructed target model file, obtain the combined service description information corresponding to the target management object class (MOC), and the combined service description information is used to represent the association information of the target MOC; According to the network element change data and the combined service description information, change the combined service field data corresponding to the target MOC to obtain the latest combined service field data, so that the database that performs synchronous update based on the latest combined service field data can query the combined service field data corresponding to the target MOC in real time.

2. The method for processing combined service description information according to claim 1, characterized in that, the step of changing the combined service field data corresponding to the target MOC according to the network element change data and the combined service description information to obtain the latest combined service field data includes: Determine the change requirements corresponding to the combined service field data according to the network element change data and the combined service description information; Based on the content of the change requirements, assemble the network element change data of the combined service field data to obtain change information; According to the change information and the combined service description information, change the combined service field data corresponding to the target MOC to obtain the latest combined service field data.

3. The method for processing combined service description information according to claim 2, characterized in that, the step of changing the combined service field data corresponding to the target MOC according to the change information and the combined service description information to obtain the latest combined service field data includes: According to the change information, determine the combined service description fields of the target MOC whose requirements need to be changed, and use the combined service description fields of the target MOC whose requirements need to be changed as the target service field data; Change the target service field data and update the changed target service field data to the database; Use the changed target service field data as the changed service field data, and according to the combined service description information, determine the target service description fields cascaded by the changed service field data, where the target service description fields are the combined service description fields of other target MOCs; According to the hierarchical dependency relationship corresponding to the cascaded target service description fields, hierarchically update the changed target service description fields in each round to the database in sequence.

4. The method for processing combined service description information according to claim 3, characterized in that, the step of hierarchically updating the changed target service description fields in each round to the database according to the hierarchical dependency relationship corresponding to the cascaded target service description fields includes: According to the hierarchical dependency relationship corresponding to the cascaded target service description fields, determine whether there are directly associated target service description fields for the changed service field data; In the case where there is a directly associated target service description field, according to the combined service description information, perform the current round of change on the directly associated target service description field, and update the target service description field after the current round of change to the database; Use the target service description field after the current round of change as the new changed service field data, and return to execute the step of determining whether there is a directly associated target service description field for the changed service field data according to the hierarchical dependency relationship corresponding to the cascaded target service description field, until there is no directly associated target service description field for the changed service field data.

5. The method for processing combined service description information according to claim 3, characterized in that, before the step of changing the target service field data, further includes: In the case where the network element change type corresponding to the network element change data is network element first access or network element upgrade, perform a full MOC change on the target service field data, and update all the target service field data after the full MOC change to the database, where the full MOC change refers to changing all the combined service description fields of the target MOC in the target model file.

6. The method for processing combined service description information according to claim 1, characterized in that, after obtaining the network element change data reported by the network element includes: Synchronously update the obtained network element change data to the database.

7. The method for processing combined service description information according to claim 1, characterized in that, The step of obtaining the combined service description information corresponding to the target management object class MOC based on the pre-constructed target model file includes: Parse the pre-constructed target model file to obtain the combined service description information corresponding to the target management object class MOC.

8. The method for processing combined service description information according to claim 7, characterized in that, after the step of parsing the pre-constructed target model file to obtain the combined service description information corresponding to the target management object class MOC, includes: Dynamically monitor the target model file; After detecting that the target model file has changed, re-parse the target model file to obtain the latest combined service description information; Execute the step of changing the combined service field data corresponding to the target MOC according to the network element change data and the combined service description information.

9. The method for processing combined service description information according to claim 8, characterized in that, after the step of re-parsing the target model file to obtain the latest combined service description information, includes: According to the latest combined service description information, perform an update process on the combined service field data of the target MOC, and synchronously update the combined service description field after the update process to the database.

10. The method for processing combined service description information according to any one of claims 1 to 9, characterized in that, The associated information includes: At least one of the combined service description fields including associating a constant string, associating its own attributes, associating the attributes of the parent class, associating the attributes of the subclass, associating the MOC attributes pointed to by the ref attribute field of itself, associating the enumerated value attributes of itself, and associating other MOCs.

11. A processing device for combined service description information, Characterized in that, It includes: An acquisition module, configured to acquire the network element change data reported by the network element; Based on the pre-constructed target model file, obtain the combined service description information corresponding to the target management object class (MOC), and the combined service description information is used to represent the association information of the target MOC; A processing module, configured to change the combined service field data corresponding to the target MOC according to the network element change data and the combined service description information, so as to obtain the latest combined service field data, so that the database that performs synchronous update based on the latest combined service field data can query the combined service field data corresponding to the target MOC in real time.

12. An electronic device, Characterized in that, The electronic device includes a processor and a memory, and the memory stores a program or instruction that can run on the processor. When the program or instruction is executed by the processor, the processing method of the combined service description information according to any one of claims 1 to 10 is implemented.

13. A computer-readable storage medium, Characterized in that, The computer-readable storage medium stores a program or instruction, and when the program or instruction is executed by a processor, the processing method of the combined service description information according to any one of claims 1 to 10 is implemented.

Images