Data processing method and device, electronic equipment and nonvolatile storage medium

Abstract

The invention discloses a data processing method and device, electronic equipment and a nonvolatile storage medium. The method comprises the steps that a resource change message pushed by a network element management system is acquired, and the resource change message is used for representing the change condition of a target resource in an optical communication network; a service category corresponding to the target resource is determined, and under the condition that the service category belongs to a target push range, resource data of a first format contained in the resource change message is converted into resource data of a target format, the target push range is used for representing a service category range of resources needing to be managed by the resource management system, and the resource data of the target format is sent to the resource management system. The first format is a data format supported by a network element management system, and the target format is a data format supported by a resource management system; and pushing the resource data in the target format to a resource management system. According to the method and the device, the technical problems of data updating lagging, low manual input efficiency and error proneness of a resource management system in related technologies are solved.

Description

Technical Field

[0001] This application relates to the field of transmission network management technology, and more specifically, to a data processing method, apparatus, electronic device, and non-volatile storage medium. Background Technology

[0002] With the rapid development of information technology, optical communication networks, as the cornerstone of information transmission, are becoming increasingly larger and more complex. Currently, the management and maintenance of optical networks mainly rely on the cooperation of the manufacturer's Element Management System (EMS) and the operator's Operational Transmission Management System (OTMS). However, the operator's resource management system, as a comprehensive resource management platform covering multiple disciplines such as transmission, IP, and optical cables, relies on manual operation for the input and management of resource data, resulting in significant inefficiencies and technical limitations.

[0003] There is currently no effective solution to the above problems. Summary of the Invention

[0004] This application provides a data processing method, apparatus, electronic device, and non-volatile storage medium to at least solve the technical problems of lagging data updates, low efficiency of manual data entry, and susceptibility to errors in resource management systems in related technologies.

[0005] According to one aspect of the embodiments of this application, a data processing method is provided, comprising: acquiring a resource change message pushed by a network element management system, wherein the resource change message is used to characterize the change of a target resource in an optical communication network; determining the service category corresponding to the target resource, and, if the service category falls within the target push range, converting resource data in a first format contained in the resource change message into resource data in a target format, wherein the target push range characterizes the service category range of resources that need to be managed by the resource management system, the first format is a data format supported by the network element management system, and the target format is a data format supported by the resource management system; and pushing the resource data in the target format to the resource management system.

[0006] Optionally, converting the resource data in the first format contained in the resource change message into resource data in the target format includes: determining the target vendor corresponding to the network element management system; obtaining the mapping rules between the first format corresponding to the target vendor and the target format supported by the resource management system, wherein the mapping rules are used to characterize the correspondence between fields in resource data of different formats; and mapping the fields in the resource data of the first format to the corresponding fields in the resource data of the target format according to the mapping rules, thereby obtaining the resource data in the target format.

[0007] Optionally, according to the mapping rules, mapping the fields in the resource data of the first format to the corresponding fields in the target format to obtain the resource data in the target format includes: determining the correspondence between the resource name field in the first format and the resource name field in the target format according to the mapping rules, and converting the resource name field in the resource data of the first format to the corresponding resource name field in the target format according to the correspondence; determining the attribute parameter field corresponding to the resource name field in the first format, and converting the attribute parameter field in the first format to the attribute parameter field in the target format according to the parameter conversion rules in the mapping rules, wherein the parameter conversion rules are used to characterize the conversion logic relationship between the attribute parameter field in the first format and the attribute parameter field required by the target format.

[0008] Optionally, the target resource includes: channel resources, wherein the resource name field of the channel resource in the first format includes at least one of the following: optical multiplexer segment, optical channel, ODUk, and the correspondence includes at least one of the following: the optical multiplexer segment field in the first format corresponds to the transmission system multiplexer segment field in the target format; the optical channel field in the first format corresponds to the optical layer channel field in the target format; the ODUk field in the first format corresponds to the synchronous digital hierarchy system field and / or the optical transport network pre-connection channel field in the target format; the attribute parameter field corresponding to the optical channel field in the first format includes at least one of the following: center frequency field, and the parameter conversion rule corresponding to the center frequency field includes: the conversion correspondence between the center frequency in the first format and the channel number in the target format.

[0009] Optionally, the target resource further includes: circuit resources, wherein the resource name field of the circuit resource in the first format includes at least one of the following: ODUk, VCx, and the correspondence includes at least one of the following: the ODUk field in the first format corresponds to the EoO service circuit field or Client service circuit field in the target format, and the VCx field in the first format corresponds to the Ethernet service circuit field and / or Synchronous Digital Architecture service circuit field in the target format; the attribute parameter field corresponding to the resource name field of the circuit resource includes at least one of the following: a routing type field, and the parameter conversion rule includes: the correspondence between the routing type in the first format and the routing type in the target format.

[0010] Optionally, before pushing the resource data in the target format to the resource management system, the method further includes: performing data integrity verification on the resource data in the target format, wherein the data integrity verification includes at least one of the following: verifying whether the data in the resource data conforms to the hierarchical structure required by the resource management system, verifying whether the resource data contains all the required fields; and, if the data integrity verification fails, performing data repair on the resource data, wherein the data repair is used to repair the data defects in the resource data that caused the data integrity verification to fail.

[0011] Optionally, the target resources also include: physical resources, wherein the physical resources include at least one of the following: network element, chassis, slot, board, port, and the hierarchical structure corresponding to the physical resources includes at least one of the following: at least one chassis exists under a network element, at least one slot exists under a chassis, at least one board occupies at least one slot, and at least one port is contained on a board.

[0012] According to another aspect of the embodiments of this application, a data processing apparatus is also provided, comprising: a resource change sensing module, configured to acquire resource change messages pushed by a network element management system, wherein the resource change messages are used to characterize the changes in target resources in an optical communication network; a resource data conversion module, configured to determine the service category corresponding to the target resource, and, if the service category falls within the target push range, convert resource data in a first format contained in the resource change message into resource data in a target format, wherein the target push range characterizes the range of service categories of resources that need to be managed by the resource management system, the first format is a data format supported by the network element management system, and the target format is a data format supported by the resource management system; and a resource data push module, configured to push the resource data in the target format to the resource management system.

[0013] According to another aspect of the embodiments of this application, an electronic device is also provided, including: a memory and a processor, the processor being configured to run a program stored in the memory, wherein the program executes a data processing method during runtime.

[0014] According to another aspect of the embodiments of this application, a non-volatile storage medium is also provided, the non-volatile storage medium including a stored computer program, wherein the device where the non-volatile storage medium is located executes a data processing method by running the computer program.

[0015] According to another aspect of the embodiments of this application, a computer program product is also provided, including a computer program that, when executed by a processor, implements the steps of a data processing method.

[0016] In this embodiment, a method is adopted to obtain resource change messages pushed by the network element management system, wherein the resource change messages are used to characterize the changes in target resources in the optical communication network; determine the service category corresponding to the target resource, and if the service category falls within the target push range, convert the resource data in the first format contained in the resource change message into resource data in the target format, wherein the target push range is used to characterize the service category range of resources that need to be managed by the resource management system, the first format is a data format supported by the network element management system, and the target format is a data format supported by the resource management system; and push the resource data in the target format to the resource management system. By sensing network resource changes in real time and automatically converting and pushing them to the resource management system, the real-time performance, accuracy, and consistency of resource data are improved, thereby solving the technical problems of lagging data updates in the resource management system, low efficiency of manual input, and susceptibility to errors in related technologies. Attached Figure Description

[0017] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings:

[0018] Figure 1 This is a hardware structure block diagram of a computer terminal (or electronic device) for implementing a data processing method according to an embodiment of this application;

[0019] Figure 2 This is a schematic diagram of a data processing method flow according to an embodiment of this application;

[0020] Figure 3 This is a schematic diagram of a method for automatically pushing resource data according to an embodiment of this application;

[0021] Figure 4 This is a schematic diagram illustrating a scenario of real-time perception of newly added physical resources according to an embodiment of this application;

[0022] Figure 5 This is a schematic diagram of the structure of a data processing device provided according to an embodiment of this application. Detailed Implementation

[0023] To enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present application, and not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative effort should fall within the scope of protection of the present application.

[0024] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0025] To facilitate a better understanding of the embodiments of this application by those skilled in the art, some technical terms or nouns involved in the embodiments of this application are explained as follows:

[0026] OTMS (Operational Transmission Management System): refers to the operator's all-optical network controller system;

[0027] Resource Sharing System: Refers to the operator's resource management system;

[0028] EMS (Element Management System): The manufacturer's network management system is a key management component in the transmission network, responsible for configuring, monitoring, maintaining, and managing the faults of one or more network elements (NEs).

[0029] OTS (Optical Transmission Section): The most basic physical transmission segment in an optical transmission network refers to the pure optical fiber transmission segment between two optical amplifiers (such as EDFA) or optical repeaters. It is the lowest physical bearer in a DWDM system and is responsible for the power transmission and physical layer management of optical signals.

[0030] OMS (Optical Multiplex Section): is a logical segment in an optical transmission network. It refers to the collection of optical channels carrying multiple wavelength signals between two optical multiplexing devices (such as OTU, OLA, or OXC). It is a key component of DWDM (Dense Wavelength Division Multiplexing) systems and is responsible for multiplexing multiple optical signals into a single optical fiber for transmission.

[0031] OCH (Optical Channel): is an end-to-end logical channel in an optical transport network, representing a complete transmission path from the source to the destination for a specific wavelength (λ). It is a key layer in the OTN (Optical Transport Network) architecture, responsible for providing transparent optical layer bearer services for client signals (such as SDH and Ethernet).

[0032] ODUk (Optical Channel Data Unit-k): is a data encapsulation structure in the OTN (Optical Transport Network) architecture, used to provide standardized digital encapsulation, performance monitoring, and fault management functions in the Optical Channel Layer (OCH). Here, k represents different rate levels (such as ODU1, ODU2, ODU3, ODU4, ODUC2, ODUC4, ODUflex, etc.).

[0033] VCx (Virtual Container-x): This is the basic transmission unit in SDH (Synchronous Digital Hierarchy), used to carry tributary signals of different rates (such as E1, E3, E4, etc.). Here, x represents the virtual container level (such as VC-12, VC-3, VC-4), corresponding to different transmission capacities. VCx provides flexible mapping, multiplexing, and cross-connection functions in SDH networks.

[0034] EoO (Ethernet over OTN): This technology processes Ethernet signals, encapsulates and maps them, and then transmits them through the WDM channel to the OTN system.

[0035] EoSoO (Ethernet over SDH over OTN): is a multi-layer transmission technology that carries Ethernet services through a two-layer network architecture of SDH and OTN. It retains the traditional SDH management functions while using OTN to improve transmission capacity and reliability.

[0036] In related technologies, resource management systems, as comprehensive resource management platforms covering multiple disciplines such as transmission, IP, and optical cables, still rely mainly on manual methods for resource entry. This requires manual maintenance of physical resources such as network elements, chassis, and boards in the all-optical network, as well as channel and circuit resources. This not only involves a huge workload but also suffers from the problem of delayed resource updates, resulting in the system data being out of sync with the actual network status. This delay will further affect the accuracy of cutover impact analysis and may even lead to the risk of misjudgment.

[0037] To address the aforementioned issues, this application provides a solution that includes an automatic resource data push mechanism to improve the efficiency of resource system data entry and enable real-time perception and synchronization of resource changes, thereby enhancing the real-time performance, accuracy, and consistency of resource data. The following provides a detailed explanation.

[0038] According to an embodiment of this application, a method embodiment for data processing is provided. It should be noted that the steps shown in the flowchart in the accompanying drawings can be executed in a computer system such as a set of computer-executable instructions. Furthermore, although a logical order is shown in the flowchart, in some cases, the steps shown or described may be executed in a different order than that shown here.

[0039] The methods and embodiments provided in this application can be executed on mobile terminals, computer terminals, or similar computing devices. Figure 1 A hardware structure block diagram of a computer terminal (or electronic device) for implementing a data processing method is shown. Figure 1 As shown, the computer terminal 10 (or electronic device) may include one or more processors 102 (shown as 102a, 102b, ..., 102n in the figure) 102 (processor 102 may include, but is not limited to, a microprocessor MCU or a programmable logic device FPGA, etc.), a memory 104 for storing data, and a transmission device 106 for communication functions. In addition, it may also include: a display, an input / output interface (I / O interface), a universal serial bus (USB) port (which may be included as one of the ports of a BUS bus), a network interface, a power supply, and / or a camera. Those skilled in the art will understand that... Figure 1 The structure shown is for illustrative purposes only and does not limit the structure of the aforementioned electronic device. For example, computer terminal 10 may also include... Figure 1 The more or fewer components shown, or having the same Figure 1 The different configurations shown.

[0040] It should be noted that the aforementioned one or more processors 102 and / or other data processing circuits are generally referred to herein as "data processing circuits". These data processing circuits may be embodied, in whole or in part, in software, hardware, firmware, or any other combination thereof. Furthermore, the data processing circuits may be a single, independent processing module, or may be integrated, in whole or in part, into any other element within the computer terminal 10 (or electronic device). As involved in the embodiments of this application, the data processing circuits serve as a processor control mechanism (e.g., selection of a variable resistor termination path connected to an interface).

[0041] The memory 104 can be used to store software programs and modules of application software, such as program instructions / data storage devices corresponding to the data processing method in this embodiment. The processor 102 executes various functional applications and data processing by running the software programs and modules stored in the memory 104, thereby implementing the aforementioned data processing method. The memory 104 may include high-speed random access memory, and may also include non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 104 may further include memory remotely located relative to the processor 102, and these remote memories can be connected to the computer terminal 10 via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

[0042] The transmission device 106 is used to receive or send data via a network. Specific examples of the network described above may include a wireless network provided by the communication provider of the computer terminal 10. In one example, the transmission device 106 includes a Network Interface Controller (NIC), which can connect to other network devices via a base station to communicate with the Internet. In another example, the transmission device 106 may be a Radio Frequency (RF) module, used for wireless communication with the Internet.

[0043] The display may be, for example, a touchscreen liquid crystal display (LCD) that allows the user to interact with the user interface of the computer terminal 10 (or electronic device).

[0044] Under the above operating environment, this application provides a data processing method. Figure 2 This is a schematic diagram of a data processing method flow provided according to an embodiment of this application, such as... Figure 2 As shown, the method includes the following steps:

[0045] Step S202: Obtain resource change messages pushed by the network element management system, wherein the resource change messages are used to characterize the changes in target resources in the optical communication network;

[0046] Step S204: Determine the business category corresponding to the target resource, and if the business category is within the target push range, convert the resource data in the first format contained in the resource change message into resource data in the target format. The target push range is used to characterize the business category range of the resources that need to be managed by the resource management system. The first format is the data format supported by the network element management system, and the target format is the data format supported by the resource management system.

[0047] Step S206: Push the resource data in the target format to the resource management system.

[0048] By taking the above steps, and by sensing changes in network resources in real time and automatically converting and pushing them to the resource management system, the real-time performance, accuracy, and consistency of resource data are improved. This solves the technical problems of lagging data updates in resource management systems, low efficiency of manual data entry, and susceptibility to errors.

[0049] The data processing method in steps S202 to S206 of the embodiments of this application will be further described below.

[0050] Figure 3 This is a schematic diagram of a method for automatically pushing resource data according to an embodiment of this application, such as... Figure 3 As shown, this embodiment of the application utilizes resource change messages pushed by the Element Management System (EMS) to capture status changes of target resources in the optical communication network. These changes may include the addition, modification, or deletion of resources. Subsequently, by intelligently identifying the service category corresponding to the target resource, it ensures that only resource data within the target push scope is converted and synchronized, avoiding unnecessary data processing and optimizing the resource management process. Next, standardized field mapping rules and multi-level data verification algorithms are used to convert the original first-format data into target-format data, ensuring the accuracy and integrity of the data. Finally, the converted resource data is pushed to the resource management system in real time through an automated interface, achieving second-level synchronization of optical network resource data, greatly improving the data freshness and operational efficiency of the resource management system. A detailed description follows.

[0051] First, the system detects changes in EMS resource data (additions, modifications, deletions, etc.) in the current network in real time. When a change in a target resource is detected in the optical communication network, the network element management system (EMS) will push the resource data change information to the optical transmission operation support platform (OTMS) through a resource change message. The OTMS can detect the data changes of each EMS in the current network in real time.

[0052] Since not all resources need to be pushed to the resource management system for management, and OTMS centrally manages all network management data from various vendors' network element management systems, selective pushing is required in accordance with production. This involves determining the service category corresponding to the target resource and whether that service category falls within the target pushing scope. Specifically, in this embodiment, during the engineering construction phase, the management objects to be pushed to the resource system can be clearly defined, and the target pushing scope can be delineated. During the implementation phase, OTMS senses data changes and classifies them according to engineering construction requirements. If the real-time sensed data (target resource) falls within the engineering construction pushing scope (target pushing scope), the next step is performed; otherwise, no further processing is performed. That is, when the service category falls within the target pushing scope, the resource data in the first format contained in the resource change message is converted into resource data in the target format. The specific steps are as follows.

[0053] In some embodiments of this application, converting resource data in a first format contained in a resource change message into resource data in a target format includes the following steps: determining the target vendor corresponding to the network element management system; obtaining the mapping rules between the first format corresponding to the target vendor and the target format supported by the resource management system, wherein the mapping rules are used to characterize the correspondence between fields in resource data of different formats; and mapping the fields in the resource data of the first format to the corresponding fields in the resource data of the target format according to the mapping rules, thereby obtaining the resource data in the target format.

[0054] Specifically, when the network element management system reports resource change messages, the system first identifies and determines the target vendor corresponding to the message source. Then, according to predefined mapping rules, it obtains the conversion correspondence between the first format resource data of the target vendor and the target format resource data supported by the resource management system. The mapping rules describe in detail the correspondence of fields in different formats of resource data, including but not limited to physical resources such as network elements, chassis, boards, and ports, as well as channel resources and service circuit resources such as OCH optical layer channels, OTN pre-connection channels, and SDH systems. Based on these rules, the fields in the original data (i.e., the first format resource data) reported by EMS to OTMS can be converted into the corresponding fields in the target format resource data, thereby realizing the automatic conversion of the resource data model.

[0055] The specific steps for mapping fields in the resource data of the first format to the corresponding fields in the resource data of the target format according to the mapping rules are as follows.

[0056] In some embodiments of this application, mapping fields in resource data of the first format to corresponding fields in the target format according to mapping rules to obtain resource data of the target format includes: determining the correspondence between resource name fields in the first format and resource name fields in the target format according to mapping rules, and converting resource name fields in resource data of the first format to corresponding resource name fields in the target format according to the correspondence; determining attribute parameter fields corresponding to resource name fields in the first format, and converting attribute parameter fields in the first format to attribute parameter fields in the target format according to parameter conversion rules in the mapping rules, wherein the parameter conversion rules are used to characterize the conversion logic relationship between attribute parameter fields in the first format and attribute parameter fields required by the target format.

[0057] Specifically, the correspondence between the resource name field in the EMS model and the resource name field in the resource management system model can be determined first. The resource name field in the EMS data can be converted into the format required by the resource management system through field mapping. Then, the attribute parameter fields corresponding to the resource name field in the EMS model can be analyzed. According to the preset parameter conversion rules, these attribute parameter fields can be converted into a format that conforms to the resource system model standard. The parameter conversion rules describe in detail the conversion logic between EMS attribute parameters and resource system attribute parameters.

[0058] Through the above conversion process, resource data changes can be automatically identified and processed, ensuring accurate conversion and synchronization of data between the resource system model and the EMS model. This enables real-time updates of resource data, improves network operation and maintenance efficiency, reduces data entry errors, and provides solid technical support for real-time monitoring and management of the resource system.

[0059] Afterwards, before pushing the converted resource data in the target format to the resource management system, you can also perform data integrity verification. The specific steps are as follows.

[0060] In some embodiments of this application, before pushing the resource data in the target format to the resource management system, the method further includes the following steps: performing data integrity verification on the resource data in the target format, wherein the data integrity verification includes at least one of the following: verifying whether the data in the resource data conforms to the hierarchical structure required by the resource management system, and verifying whether the resource data contains all the required fields; if the data integrity verification fails, performing data repair on the resource data, wherein the data repair is used to repair the data defects in the resource data that caused the data integrity verification to fail.

[0061] Specifically, the data integrity verification process covers verifying whether the hierarchical structure of the resource data meets the requirements of the resource management system, and whether all necessary fields are complete and present. If the data integrity verification fails, i.e., if the data is found to have non-standard hierarchical structure or missing fields, the data repair mechanism will be automatically triggered to repair the data defects in order to meet the acceptance standards of the resource management system. The introduction of this mechanism effectively avoids push failures caused by data quality issues, ensures accurate synchronization of resource data, and improves the efficiency and success rate of automated push.

[0062] Finally, after the integrity verification is passed, the resource data in the target format can be pushed to the resource management system through a standardized interface to achieve automated data entry, reduce the risk of data asynchrony caused by manual maintenance, effectively support network maintenance work, such as circuit activation and cutover impact analysis, ensure that the data of the resource system is synchronized with the network status, and improve the efficiency and accuracy of operation and maintenance.

[0063] In this embodiment, the target resources in the all-optical network can be divided into three categories: physical resources (network elements, chassis, channels, boards, ports, etc.), channel resources (transmission systems, OCH channels, OTN pre-connection channels, SDH systems), and circuit resources. First, physical resources must be available. Once physical resources are available, channel resources are created on top of them. Finally, circuit resources are created based on the channel resources. Circuits are the top layer of the hierarchical model and are not further subdivided; they are directly customer-facing. The following examples illustrate the automatic push process for the above resource data with specific resource categories.

[0064] like Figure 4 The diagram shows a process for adding and real-time sensing physical resources, as detailed below.

[0065] First, real-time monitoring of changes in physical resource data within the existing network is crucial. Changes in physical resources are reported to the OTMS system via messages from the EMS, which can be analyzed by examining messages reported by the EMS to the OTMS system (such as addition and deletion messages for circuit boards). Then, the OTMS system categorizes and organizes physical resources according to network elements, chassis, channels, circuit boards, and ports, simultaneously determining whether the current physical resource falls under the resource sharing and management scope (i.e., whether it belongs to the target push range). If not, no processing is performed; otherwise, further processing is initiated. The raw data reported by the EMS to the OTMS is converted to a standardized format according to the resource management system model standard, transforming the vendor's original network management data (OTMS storage) model into standardized data conforming to the resource system model (i.e., resource data in the target format). Before pushing, data integrity needs to be verified, primarily checking whether the data hierarchy is standardized and whether there is any missing data. The hierarchical structure corresponding to physical resources is mainly as follows.

[0066] In some embodiments of this application, the target resource further includes: physical resources, wherein the physical resources include at least one of the following: network element, chassis, slot, board, port, and the hierarchical structure corresponding to the physical resources includes at least one of the following: at least one chassis exists under a network element, at least one slot exists under a chassis, at least one board occupies at least one slot, and at least one port is included on a board.

[0067] If validation fails, the data needs to be processed through data governance, repaired, and then the model transformation repeated. If validation passes, proceed to the next step. The validated data is then pushed to the resource management system via a standardized interface to complete automated data entry.

[0068] The above process involves scenarios such as adding, modifying, and deleting physical resources. For example, if there was originally a 2-port card and today a 4-port card is added, after EMS reports the change, the push service detects that the card has been changed to a resource under the resource sharing management system and pushes the card's data to the resource sharing system (resource management system) as an update. Another example is if a new card is added to this network element; the push service will push the new card to the resource sharing system for addition processing. If a card is deleted, the deletion will be pushed.

[0069] Regarding channel resources, the automatic conversion mechanism for channel resources in this embodiment is as follows.

[0070] In some embodiments of this application, the target resource includes: channel resources, wherein the resource name field of the channel resource in the first format includes at least one of the following: optical multiplexer segment, optical channel, ODUk, and the correspondence includes at least one of the following: the optical multiplexer segment field in the first format corresponds to the transmission system multiplexer segment field in the target format, the optical channel field in the first format corresponds to the optical layer channel field in the target format, the ODUk field in the first format corresponds to the synchronous digital hierarchy system field and / or the optical transport network pre-connection channel field in the target format; the attribute parameter field corresponding to the optical channel field in the first format includes at least one of the following: center frequency field, and the parameter conversion rule corresponding to the center frequency field includes: the conversion correspondence between the center frequency in the first format and the channel number in the target format.

[0071] Specifically, channel resources mainly include transmission system multiplex section channel resources, OCH channel resources (optical layer channel field), SDH system resources (synchronous digital hierarchy system field), and OTN pre-connection channel resources (optical transport network pre-connection channel field), corresponding to OMS (optical multiplex section), OCH (optical channel), and ODUK resources on the network element management system; as shown in the table below.

[0072]

[0073] Channel resources are layered. First, after the physical resources are available, a new topology connection (equivalent to a physical optical fiber) is established between network elements. Then, an OTS is established on the topology connection. Multiple OTS segments form an OMS. The OMS corresponds to the transmission system multiplexing segment in the resource management system model and belongs to the wavelength division multiplexing category.

[0074] An OCH (Optical Channel Communication) route passes through an OMS (Optical Management System). The resource management system manages channels in the OMS using the concept of channels, but the EMS (Electronic Management System) does not have the concept of channels; it manages them using frequencies from the OMS. Therefore, this involves the model conversion relationship between frequency and channel number. For example, the correspondence between channel number and frequency in a 120-wavelength × 100G transmission system (i.e., the parameter conversion rules corresponding to the center frequency field mentioned above) is shown in the table below.

[0075]

[0076] In other words, when the frequency occupancy relationship of OCH reported by EMS is pushed to the resource management system, it needs to be converted into the channel number corresponding to the frequency, and then the OCH and its route are pushed to the resource sharing system.

[0077] The aforementioned SDH system resources are channel resources specifically used to open SDH circuits. Their corresponding resources on the EMS are ODUk resources (divided into primary and backup), which are further subdivided into smaller granular trunk types.

[0078] The aforementioned OTN pre-connected channel resources are used in large-granularity circuit scenarios, corresponding to the ODUk resources on the EMS, without further granular division.

[0079] The logic for pushing channel resources is as follows: first push to the transmission system, then push to the OCH optical layer channel, and finally push to the SDH system and OTN pre-connection channel. Its real-time scenario awareness is the same as that of physical resources. It receives network management messages, determines whether the resource is shared or managed, and pushes updates in real-time for managed channel resources. This will not be elaborated further here.

[0080] Regarding circuit resources, the automatic conversion mechanism for circuit resources in this application embodiment is as follows.

[0081] In some embodiments of this application, the target resource further includes: circuit resources, wherein the resource name field of the circuit resource in the first format includes at least one of the following: ODUk, VCx, and the correspondence includes at least one of the following: the ODUk field in the first format corresponds to the EoO service circuit field and / or the Client service circuit field in the target format, and the VCx field in the first format corresponds to the Ethernet service circuit field and / or the Synchronous Digital Hierarchy service circuit field in the target format; the attribute parameter field corresponding to the resource name field of the circuit resource includes at least one of the following: a routing type field, and the parameter conversion rule includes: the correspondence between the routing type in the first format and the routing type in the target format.

[0082] Specifically, once channel resources are available, new circuits can be created within those resources. Each circuit occupies a time slot within the channel resources. In this embodiment, service circuits are generally divided into EoO and Client circuits transmitted via OTN, carried using ODUk, with ODUk routing via OCH; another type is EOS and SDH circuits carried via SDH, with EMS carried using VCx and routing via ODUk. See the table below.

[0083]

[0084] For scenarios involving the addition of new service circuits, the service activation system automatically triggers the circuit push function after the circuit's network management configuration is complete. The push service uses the circuit information provided by the service activation system to detect real-time changes in the routing of line resources corresponding to the EMS bearer mode of the circuit, collects circuit and routing information from the network management system, and if the message falls within the scope of the service circuit, performs model transformation on the data according to the transformation relationships in the table. Finally, the transformed data is assembled into the latest message and pushed to the resource sharing system for data update and storage, including scenarios such as adding, modifying, and deleting circuits.

[0085] This application's solution can utilize messages to perceive network changes in real time and promptly push these changes to the resource management system for data updates, reducing resource data synchronization latency from hours to seconds, significantly decreasing operational incidents caused by data asynchrony. Simultaneously, it defines a mapping rule for automatic conversion between the EMS model and the resource management system model, establishing a clear correspondence between the two models. This covers three major resource categories: physical resources, channel resources, and business circuits, achieving standardized automatic conversion of cross-vendor EMS data to the resource management system model. This solves the problems of low efficiency, error-proneness, and untimely updates associated with manual data entry into the resource management system, enabling 24 / 7 uninterrupted automated data synchronization.

[0086] According to an embodiment of this application, an embodiment of a data processing apparatus is also provided. Figure 5 This is a schematic diagram of the structure of a data processing device according to an embodiment of this application. Figure 5 As shown, the device includes:

[0087] The resource change sensing module 50 is used to acquire resource change messages pushed by the network element management system. The resource change messages are used to characterize the changes in target resources in the optical communication network.

[0088] The resource data conversion module 52 is used to determine the business category corresponding to the target resource, and when the business category is within the target push range, convert the resource data in the first format contained in the resource change message into the resource data in the target format. The target push range is used to characterize the business category range of the resources that need to be managed by the resource management system. The first format is the data format supported by the network element management system, and the target format is the data format supported by the resource management system.

[0089] The resource data push module 54 is used to push resource data in the target format to the resource management system.

[0090] Optionally, converting the resource data in the first format contained in the resource change message into resource data in the target format includes: determining the target vendor corresponding to the network element management system; obtaining the mapping rules between the first format corresponding to the target vendor and the target format supported by the resource management system, wherein the mapping rules are used to characterize the correspondence between fields in resource data of different formats; and mapping the fields in the resource data of the first format to the corresponding fields in the resource data of the target format according to the mapping rules, thereby obtaining the resource data in the target format.

[0091] Optionally, according to the mapping rules, mapping the fields in the resource data of the first format to the corresponding fields in the target format to obtain the resource data in the target format includes: determining the correspondence between the resource name field in the first format and the resource name field in the target format according to the mapping rules, and converting the resource name field in the resource data of the first format to the corresponding resource name field in the target format according to the correspondence; determining the attribute parameter field corresponding to the resource name field in the first format, and converting the attribute parameter field in the first format to the attribute parameter field in the target format according to the parameter conversion rules in the mapping rules, wherein the parameter conversion rules are used to characterize the conversion logic relationship between the attribute parameter field in the first format and the attribute parameter field required by the target format.

[0092] Optionally, the target resource includes: channel resources, wherein the resource name field of the channel resource in the first format includes at least one of the following: optical multiplexer segment, optical channel, ODUk, and the correspondence includes at least one of the following: the optical multiplexer segment field in the first format corresponds to the transmission system multiplexer segment field in the target format; the optical channel field in the first format corresponds to the optical layer channel field in the target format; the ODUk field in the first format corresponds to the synchronous digital hierarchy system field and / or the optical transport network pre-connection channel field in the target format; the attribute parameter field corresponding to the optical channel field in the first format includes at least one of the following: center frequency field, and the parameter conversion rule corresponding to the center frequency field includes: the conversion correspondence between the center frequency in the first format and the channel number in the target format.

[0093] Optionally, the target resource further includes: circuit resources, wherein the resource name field of the circuit resource in the first format includes at least one of the following: ODUk, VCx, and the correspondence includes at least one of the following: the ODUk field in the first format corresponds to the EoO service circuit field and / or the Client service circuit field in the target format, and the VCx field in the first format corresponds to the Ethernet service circuit field and / or the Synchronous Digital Architecture service circuit field in the target format; the attribute parameter field corresponding to the resource name field of the circuit resource includes at least one of the following: a routing type field, and the parameter conversion rule includes: the correspondence between the routing type in the first format and the routing type in the target format.

[0094] Optionally, before pushing the resource data in the target format to the resource management system, the method further includes: performing data integrity verification on the resource data in the target format, wherein the data integrity verification includes at least one of the following: verifying whether the data in the resource data conforms to the hierarchical structure required by the resource management system, verifying whether the resource data contains all the required fields; and performing data repair on the resource data if the data integrity verification fails, wherein the data repair is used to repair the data defects in the resource data that caused the data integrity verification to fail.

[0095] Optionally, the target resources also include: physical resources, wherein the physical resources include at least one of the following: network element, chassis, slot, board, port, and the hierarchical structure corresponding to the physical resources includes at least one of the following: at least one chassis exists under a network element, at least one slot exists under a chassis, at least one board occupies at least one slot, and at least one port is contained on a board.

[0096] It should be noted that each module in the above data processing device can be a program module (e.g., a set of program instructions to implement a certain function) or a hardware module. For the latter, it can be manifested in the following forms, but is not limited to them: each of the above modules is manifested as a processor, or the functions of each of the above modules are implemented by a processor.

[0097] It should be noted that the data processing device provided in this embodiment can be used to perform... Figure 2 The data processing method shown above is also applicable to the embodiments of this application, and will not be repeated here.

[0098] This application embodiment also provides a non-volatile storage medium, which includes a stored computer program. The device containing the non-volatile storage medium executes the following data processing method by running the computer program: obtaining a resource change message pushed by a network element management system, wherein the resource change message is used to characterize the changes in target resources in the optical communication network; determining the service category corresponding to the target resource, and if the service category falls within the target push range, converting resource data in a first format contained in the resource change message into resource data in a target format, wherein the target push range characterizes the range of service categories of resources that need to be managed by the resource management system, the first format is a data format supported by the network element management system, and the target format is a data format supported by the resource management system; and pushing the resource data in the target format to the resource management system.

[0099] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the steps of the data processing method described in various embodiments of this application: obtaining a resource change message pushed by a network element management system, wherein the resource change message is used to characterize the change of a target resource in the optical communication network; determining the service category corresponding to the target resource, and, if the service category falls within the target push range, converting the resource data in the resource change message in a first format into resource data in a target format, wherein the target push range characterizes the range of service categories of resources that need to be managed by the resource management system, the first format is a data format supported by the network element management system, and the target format is a data format supported by the resource management system; and pushing the resource data in the target format to the resource management system.

[0100] The sequence numbers of the embodiments in this application are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0101] In the above embodiments of this application, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0102] In the several embodiments provided in this application, it should be understood that the disclosed technical content can be implemented in other ways. The device embodiments described above are merely illustrative; for example, the division of units can be a logical functional division, and in actual implementation, there may be other division methods. For instance, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the displayed or discussed mutual coupling, direct coupling, or communication connection may be through some interfaces; the indirect coupling or communication connection between units or modules may be electrical or other forms.

[0103] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0104] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0105] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as a USB flash drive, read-only memory (ROM), random access memory (RAM), portable hard drive, magnetic disk, or optical disk.

[0106] The above description is only a preferred embodiment of this application. It should be noted that for those skilled in the art, several improvements and modifications can be made without departing from the principle of this application, and these improvements and modifications should also be considered within the scope of protection of this application.

Claims

1. A data processing method, characterized by, The method comprises the following steps: acquiring a resource change message pushed by a network element management system, wherein the resource change message is used to represent a change of a target resource in an optical communication network; determining a service category corresponding to the target resource, and converting resource data in a first format contained in the resource change message into resource data in a target format if the service category belongs to a target push range, wherein the target push range is used to represent a service category range of resources that need to be managed by a resource management system, the first format is a data format supported by the network element management system, and the target format is a data format supported by the resource management system; pushing the resource data in the target format to the resource management system.

2. The data processing method according to claim 1, characterized in that, The conversion of the resource data in the first format contained in the resource change message into the resource data in the target format comprises the following steps: determining a target vendor corresponding to the network element management system; acquiring a mapping rule corresponding to the target vendor between the first format and a target format supported by the resource management system, wherein the mapping rule is used to represent a corresponding relationship between fields in resource data in different formats; mapping fields in the resource data in the first format into corresponding fields in the resource data in the target format according to the mapping rule, to obtain the resource data in the target format.

3. The data processing method according to claim 2, characterized in that, The mapping of the fields in the resource data in the first format into corresponding fields in the target format according to the mapping rule to obtain the resource data in the target format comprises the following steps: determining a corresponding relationship between a resource name field in the first format and a resource name field in the target format according to the mapping rule, and converting the resource name field in the resource data in the first format into the corresponding resource name field in the target format according to the corresponding relationship; determining a property parameter field corresponding to the resource name field in the first format, and converting the property parameter field in the first format into a property parameter field in the target format according to a parameter conversion rule in the mapping rule, wherein the parameter conversion rule is used to represent a conversion logical relationship between the property parameter field in the first format and a required property parameter field in the target format.

4. The data processing method according to claim 3, characterized in that, The target resource includes a channel resource, wherein the resource name field of the channel resource in the first format includes at least one of an optical multiplex section, an optical channel, and an ODUk, and the correspondence includes at least one of the following: the optical multiplex section field in the first format corresponds to the transmission system multiplex section field in the target format, the optical channel field in the first format corresponds to the optical layer channel field in the target format, and the ODUk field in the first format corresponds to the synchronous digital hierarchy system field and / or the optical transport network pre-connection channel field in the target format; the attribute parameter field corresponding to the optical channel field in the first format includes at least one of a center frequency field, and the parameter conversion rule corresponding to the center frequency field includes a conversion correspondence between the center frequency in the first format and the channel number in the target format.

5. The data processing method according to claim 3, characterized in that, The target resource further includes a circuit resource, wherein the resource name field of the circuit resource in the first format includes at least one of an ODUk and a VCx, and the correspondence includes at least one of the following: the ODUk field in the first format corresponds to the EoO service circuit field or the Client service circuit field in the target format, and the VCx field in the first format corresponds to the Ethernet service circuit field and / or the synchronous digital hierarchy service circuit field in the target format; the attribute parameter field corresponding to the resource name field of the circuit resource includes at least one of a routing type field, and the parameter conversion rule includes a correspondence between the routing type in the first format and the routing type in the target format.

6. The data processing method of claim 1, wherein, Before pushing the resource data in the target format to the resource management system, the method further includes: performing data integrity verification on the resource data in the target format, wherein the data integrity verification includes at least one of the following: verifying whether the data in the resource data conforms to a hierarchical structure required by the resource management system, and verifying whether all required fields are included in the resource data; in a case where the data integrity verification fails, performing data repair on the resource data, wherein the data repair is used to repair data defects in the resource data that cause the data integrity verification to fail.

7. The data processing method according to claim 6, characterized in that, The target resource further includes a physical resource, wherein the physical resource includes at least one of a network element, a frame, a slot, a board, and a port, and the hierarchical structure corresponding to the physical resource includes at least one of the following: at least one frame exists under one network element, at least one slot exists under one frame, one board occupies at least one slot, and at least one port is included on one board.

8. A data processing apparatus, characterized by, The method includes: a resource change perception module configured to acquire a resource change message pushed by a network element management system, wherein the resource change message is used to represent a change of a target resource in an optical communication network; the resource change message includes at least one of the following: a resource name field, a resource type field, and a resource attribute parameter field, and the resource change message is used to represent a change of a target resource in an optical communication network. The resource data conversion module is configured to determine a service category corresponding to the target resource, and convert resource data in a first format contained in the resource change message into resource data in a target format if the service category belongs to a target push range, wherein the target push range represents a service category range of resources that need to be managed by the resource management system, the first format is a data format supported by the network element management system, and the target format is a data format supported by the resource management system. The resource data push module is configured to push the resource data in the target format to the resource management system.

9. An electronic device, comprising: The memory and the processor are configured to run a program stored in the memory, and the program performs the data processing method of any one of claims 1 to 7 when running. The non-volatile storage medium includes a stored computer program, and a device in which the non-volatile storage medium is located performs the data processing method of any one of claims 1 to 7 by running the computer program.

10. A non-volatile storage medium, comprising: The computer program is executed by the processor to implement the steps of the data processing method of any one of claims 1 to 7.

11. A computer program product comprising a computer program, characterized in that, ​

Images