Method for processing circuit routing data and electronic device

Abstract

Embodiments of the present disclosure provide a circuit routing data processing method and an electronic device, comprising: obtaining circuit routing data in a service storage service; constructing a unified circuit routing model based on the circuit routing data; converting the circuit routing data through the unified circuit routing model to obtain converted data; and reporting the converted data to one or more circuit routing unified reporting interfaces. Through the present disclosure, the problem of redundant functions of routing data collection systems of various operators and government and enterprise systems in the related art is solved, and when the underlying routing model is changed or newly added, each collection system needs to be modified, which requires a large amount of manpower cost, and the reliability and maintainability are very poor. Thus, the effect of reducing redundant development and input cost for different operator systems and improving the efficiency of generating whole network service routing concatenation is achieved.

Description

Technical Field

[0001] This disclosure relates to the field of communications, and more specifically, to a method and electronic device for processing circuit routing data. Background Technology

[0002] In optical transport networks (OTN) and software-defined networking (SDN) scenarios, network management systems for operators and government / enterprise organizations rely on circuit routing data provided by equipment manufacturers for network planning, monitoring, maintenance, and troubleshooting. Traditional routing data acquisition and testing methods primarily focus on network management, addressing how to parse and reconstruct data from different equipment vendors to accurately restore circuit routes. However, from the perspective of equipment manufacturers, how to efficiently and accurately acquire and verify circuit routing data to meet the high requirements of operators and government / enterprise organizations is a less-discussed but crucial area of ​​concern.

[0003] In related technical solutions, most equipment manufacturers develop a customized routing data acquisition system for each service provider. While these systems can meet the needs of specific operators, they suffer from the following problems:

[0004] 1. System redundancy and redundant development: For each new operator or government / enterprise unit connected to, the equipment manufacturer needs to redesign and implement a new routing data acquisition system, resulting in a lot of repetitive work and waste of resources, and increasing development and maintenance costs.

[0005] 2. Challenges of changing the underlying model: When the underlying routing model changes or new elements are introduced, all existing data acquisition systems need to be modified and upgraded accordingly. This process is not only complex and time-consuming, but also prone to causing new problems.

[0006] 3. Data accuracy and reliability are difficult to guarantee: There is a lack of a universal testing method to verify whether the collected routing data is accurate. Errors are often only discovered after the data has been used, resulting in long problem feedback cycles and affecting service quality and user experience.

[0007] 4. Reliability and maintainability issues: Due to the limitations of the data acquisition system design, they often exhibit low reliability and poor maintainability when facing large-scale and complex network environments, resulting in low efficiency in problem diagnosis and resolution. Summary of the Invention

[0008] This disclosure provides a method and electronic device for processing circuit routing data, which at least solves the problems of redundant functions in the routing data acquisition systems of various operators and government and enterprise systems in the related art. When the underlying routing model is changed or added, each acquisition system must be modified, resulting in large human resource costs, extremely poor reliability and maintainability, and no data detection tools.

[0009] According to one embodiment of this disclosure, a method for processing circuit routing data is provided, comprising: acquiring circuit routing data in a service storage service; constructing a unified circuit routing model based on the circuit routing data; converting the circuit routing data through the unified circuit routing model to obtain converted data; and reporting the converted data to one or more unified circuit routing reporting interfaces.

[0010] According to yet another embodiment of this disclosure, a computer-readable storage medium is also provided, in which a computer program is stored, wherein the computer program is configured to perform the steps in any of the above method embodiments when it is run.

[0011] According to yet another embodiment of this disclosure, an electronic device is also provided, including a memory and a processor, wherein a computer program is stored in the memory and the processor is configured to run the computer program to perform the steps in any of the above method embodiments.

[0012] According to yet another embodiment of this disclosure, a computer program product is also provided, including a computer program that, when executed by a processor, implements the steps in any of the above method embodiments.

[0013] Through the embodiments described above, a unified circuit routing model is constructed based on circuit routing data obtained from business storage services. This unified circuit routing model is used to transform the circuit routing data, and the transformed data is reported to one or more unified circuit routing reporting interfaces. Therefore, this addresses the problems of functional redundancy in routing data acquisition systems of various operators and government / enterprise systems in related technologies. These problems include the need to modify each acquisition system when the underlying routing model changes or is added, resulting in high manpower costs, poor reliability and maintainability, and a lack of data testing tools. This approach reduces redundant development and investment costs across different operator systems and improves the efficiency of generating network-wide business routing connections. Attached Figure Description

[0014] Figure 1 This is a hardware structure block diagram of the computer terminal used in the embodiments of the methods disclosed herein;

[0015] Figure 2 This is a flowchart (a) of a circuit routing data processing method according to an embodiment of the present disclosure;

[0016] Figure 3 This is a schematic diagram of the routing detection logic according to an embodiment of the present disclosure;

[0017] Figure 4 This is a flowchart (II) of a method for processing circuit routing data according to an embodiment of the present disclosure. Detailed Implementation

[0018] The embodiments of this disclosure will be described in detail below with reference to the accompanying drawings and examples.

[0019] It should be noted that the terms "first," "second," etc., in the specification, claims, and drawings of this disclosure are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence.

[0020] The methods and embodiments provided in this disclosure can be executed on a mobile terminal, a computer terminal, or a similar computing device. Taking running on a computer terminal as an example, Figure 1 This is a hardware structure block diagram of the computer terminal used in the embodiments of the methods disclosed herein. For example... Figure 1 As shown, a computer terminal may include one or more ( Figure 1 Only one is shown in the diagram. A processor 102 (which may include, but is not limited to, a microprocessor MCU or a programmable logic device FPGA, etc.) and a memory 104 for storing data are also shown. The computer terminal may further include a transmission device 106 for communication functions and an input / output device 108. 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 computer terminal described above. For example, the computer terminal may also include components that are more complex than those described above. Figure 1 The more or fewer components shown, or having the same Figure 1 The different configurations shown.

[0021] The memory 104 can be used to store computer programs, such as application software programs and modules, like the computer program corresponding to the circuit routing data processing method in this embodiment of the present disclosure. The processor 102 executes various functional applications and data processing by running the computer program stored in the memory 104, thereby implementing the above-described 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 a computer terminal 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.

[0022] 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 a communication provider for the computer terminal. 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.

[0023] This embodiment provides a method for processing circuit routing data running on the aforementioned computer terminal. Figure 2 This is a flowchart (a) of a circuit routing data processing method according to an embodiment of the present disclosure, as follows: Figure 2 As shown, the process includes the following steps:

[0024] Step S202: Obtain circuit routing data from the business storage service.

[0025] For example, circuit routing data in the business storage service can be obtained based on the globally unique circuit identifier (UUID).

[0026] For example, business storage services can use Structured Query Language (SQL) to interact with a database to store and retrieve circuit routing data.

[0027] Step S204: Construct a unified circuit routing model based on circuit routing data.

[0028] For example, a unified circuit routing model can be built based on circuit routing data using a software development kit (SDK).

[0029] In one exemplary embodiment, the attributes of the unified circuit routing model include at least one of the following: a globally unique circuit identifier (UUID), circuit direction, working route set, protection route set, and actual route set.

[0030] For example, the structure of the unified circuit routing model is shown in Table 1.

[0031] Table 1

[0032]

[0033] Circuit UU ID ensures the uniqueness and traceability of circuit data when it is exchanged between different operators and government and enterprise units.

[0034] The circuit direction attribute defines the transmission characteristics of the circuit, how data is transmitted from the beginning to the end.

[0035] The working route set includes the working path, the working recovery path, and the working optimization path. These paths are the paths taken when the circuit is operating normally.

[0036] The protection route set includes protection paths, protection recovery paths, and protection optimization paths. It provides backup paths in case of failure.

[0037] The actual route set describes the specific physical path of the circuit in a real network deployment. The actual route set contains the circuit's actual routing information within the current network architecture, used to verify the feasibility of operational and protection routes.

[0038] In an exemplary embodiment, after step S204, the process includes: constructing a circuit-level routing model based on the unified circuit routing model; and constructing a routing element model based on the circuit-level routing model.

[0039] In an exemplary embodiment, the attributes of the circuit-level routing model include at least one of the following: route type, forward route element set, reverse route element set, error message, and prompt message;

[0040] The attributes of a route element model include at least one of the following: route element type, route number, route start point, and route end point.

[0041] For example, the structure of the circuit-level routing model is shown in Table 2.

[0042] Table 2

[0043]

[0044] Routing type defines the different routing strategies for a circuit under normal operation, fault protection, recovery, and optimization states.

[0045] The forward routing element set contains network elements for forward transmission of a circuit, such as cross-connects, Virtual Concatenation Group Binding (VCG) bindings, Synchronous Digital Hierarchy Binding (SDH) bindings, Enhanced Time Triggered Interface Binding (ETTI) bindings, service layer circuits, and topology links. This set is arranged in forward transmission order and describes the routing path of the circuit from its start to its end.

[0046] The reverse routing element set contains the network elements for the circuit's reverse transmission, i.e., the path elements from the terminating end to the starting end. This set corresponds to the forward routing element set and is used to describe the circuit's reverse transmission path.

[0047] Error messages help locate and repair problems in the network, ensuring the correctness and reliability of routing data. When routing data is abnormal, such as incomplete data, configuration errors, or logical conflicts, the specific error information is recorded in this field.

[0048] The information prompts are used to mark and describe routing data in special scenarios, such as temporary routing changes during network maintenance, cutovers, or upgrades, or routing details that require special attention under specific conditions. These prompts enhance the interpretability and controllability of the data, facilitating network management and maintenance.

[0049] For example, the structure of the routing element model is shown in Table 3.

[0050] Table 3

[0051]

[0052] Routing element types include Cross Connection (CC or XC), Virtual Concatenation Group (VCG), Synchronous Digital Hierarchy (SDH), Ethernet (ETH), Service Layer Circuit, and Topology Link, representing different types of network resources in the circuit path.

[0053] The route number is used to identify the order of each routing element in the circuit path.

[0054] The route start point (CTP) represents the starting point of a route hop, i.e., the starting endpoint of a route element in the circuit path.

[0055] The route termination point (CTP) represents the end point of a route hop, i.e., the destination endpoint of a route element in the circuit path.

[0056] Step S206: The circuit routing data is transformed using a unified circuit routing model to obtain the transformed data.

[0057] For example, circuit routing data can be transformed using a unified circuit routing model to facilitate standardized, universal processing and reporting of the data to different operators or government and enterprise units.

[0058] In an exemplary embodiment, step S206 includes: converting circuit routing data into first data conforming to the circuit routing model using a unified circuit routing model;

[0059] The first data is converted into second data that conforms to the circuit-level routing model by the circuit-level routing model.

[0060] The second data is transformed into target data that conforms to the routing element model through the routing element model.

[0061] For example, circuit routing data is transformed sequentially through a unified circuit routing model, a circuit-level routing model, and a routing element model to obtain target data to be reported to one or more unified circuit routing reporting interfaces.

[0062] In one exemplary embodiment, converting circuit routing data into first data conforming to the circuit routing model using a unified circuit routing model includes:

[0063] Determine the corresponding circuit routing model conversion processor based on the hierarchical information of the business;

[0064] The circuit routing model conversion processor transforms the circuit routing data within the corresponding level into first data that conforms to the unified circuit routing model.

[0065] For example, the corresponding circuit routing model conversion processor is determined based on the layer information of the service, and the circuit routing data in the corresponding layer is converted into first data that conforms to the unified circuit routing model (for example, converting the internal routing data of this layer into data that is common to all operators).

[0066] For example, the layer information of the business can be ETH, SDH, Optical Channel Data Unit (ODU), or Optical Channel (OCH).

[0067] In one exemplary embodiment, converting the first data into second data conforming to the circuit-level routing model through the circuit-level routing model includes:

[0068] Using the circuit-level routing model, the first data within the corresponding layer is grouped according to the routing type and direction, so as to convert the first data into second data that conforms to the circuit-level routing model.

[0069] For example, the first data group within the corresponding layer can be grouped according to two dimensions: routing type (protection / operation) and routing direction (forward / reverse) through the circuit-level routing model.

[0070] In one exemplary embodiment, transforming the second data into target data conforming to the routing element model through the routing element model includes:

[0071] By using the routing element model, the second data within the group is sorted to obtain the routing element queue;

[0072] Use the queue of routing elements as target data that conforms to the routing element model.

[0073] In one exemplary embodiment, sorting the second data within a group to obtain a routing element queue using a routing element model includes:

[0074] In response to the completeness of the route start and end points, the correctness of the route direction, and the consecutiveness of the route sequence numbers, the second data in the group is sorted according to the route sequence number to obtain the route element queue.

[0075] For example, the routing element model can be used to check the second data within a group (whether the route start point and end point are complete, whether the direction is correct, and whether the route sequence number is consecutive) to form a correctly sorted queue of routing elements.

[0076] Step S208: The converted data is reported to one or more circuit routing unified reporting interfaces.

[0077] For example, reporting the converted data to one or more unified circuit routing reporting interfaces can reduce the manpower cost of developing different unified circuit routing reporting interfaces (such as unified circuit routing reporting interfaces developed by different operators for their own systems), and improve the reliability and maintainability of the data acquisition system.

[0078] In an exemplary embodiment, step S208 includes: merging the routing element queues within the corresponding layer into the interface response results of one or more circuit routing unified reporting interfaces.

[0079] For example, merging the routing element queues within the corresponding level into the interface response results of one or more unified circuit routing reporting interfaces can reduce the cost investment for different unified circuit routing reporting interfaces (e.g., different operators need to develop unified circuit routing reporting interfaces for different collection systems) and provide high-quality routing data.

[0080] In one exemplary embodiment, before step S208, the method includes: detecting the routing element queue within the corresponding level.

[0081] For example, before reporting the converted data to one or more unified circuit routing reporting interfaces (e.g., the unified circuit routing reporting interface of operators and government and enterprise network management platforms), the correctness and resource correlation of the routing element queues in the corresponding layer can be detected, which can provide a high-quality guarantee for the routing data and provide risk warning for the overall optical network system.

[0082] In one exemplary embodiment, detecting the queue of routing elements within the corresponding level includes:

[0083] In response to the fact that this hop route is the first hop, check whether the starting point of the route in the route element queue matches the starting point of the circuit in the circuit route data;

[0084] In response to a match between the starting point of a route in the route element queue and the starting point of a circuit in the circuit routing data, check whether the ending point of the current hop in the route element queue matches the starting point of the next hop.

[0085] In response to the fact that this hop is the last hop, check whether the route termination point of this hop in the route element queue matches the circuit termination point in the circuit routing data.

[0086] For example, detecting the routing element queue within the corresponding layer can be divided into two stages. The first stage is circuit route connectivity detection, which reads the circuit (Service Network Layer Asset File, SNL) asset file containing circuit route data and the circuit route (Service Network Topo logy File, SNT) file containing the routing element queue. One circuit route is selected, and the start and end endpoints of the circuit are found in the circuit (SNT) file through its associated circuit UUID. It is then determined whether the start and end endpoints of the routing element queue correspond to the circuit route.

[0087] For example, Figure 3This is a schematic diagram of the routing detection logic according to an embodiment of this disclosure, such as... Figure 3 As shown, these include: Switching Interface Function (SIF), Service Network Layer (SNL), and Topology Physical Link (TPL). SNL(OCH) is the Service Network Link at the Optical Channel level; SNL(OTS) is the Service Network Link at the Optical Transmission Segment level; and SNL(OMS) is the Service Network Link at the Optical Multiplex Segment level.

[0088] For circuit routing that is bidirectional (CD_BI) or unidirectional (CD_UNI) forward routing: check whether the service (such as OCH service in the above figure) point A (circuit start point in circuit routing data) and endpoint 1 (routing start point in routing element queue) match. If they match, check whether the routing termination point of this hop and the routing start point of the next hop in the routing element queue match.

[0089] For a reverse route with route CD_UNI (one-way), then... Figure 3 The A and Z endpoints need to be reversed for matching: check whether the Z point (circuit start point in circuit routing data) of the service (such as OCH service in the figure above) matches the 10 endpoint (routing start point in the routing element queue). If they match, check whether the routing termination point of the current hop in the routing element queue matches the routing start point of the next hop of the current hop.

[0090] In an exemplary embodiment, detecting whether the route termination point of the current hop in the route element queue matches the route start point of the next hop of the current hop includes:

[0091] Update the route termination point of the current hop in the route element queue to the endpoint to be matched, and check whether the endpoint to be matched matches the route start point of the next hop of the current hop.

[0092] For example, in combination Figure 3 For circuit routes that are CD_BI (bidirectional) or CD_UNI (unidirectional) forward routes:

[0093] For example, if the circuit start point A and circuit end point correspond to endpoints 1 and 10 respectively, update the routing end point 2 of SIF to the endpoint to be matched, `lastEndPoint`, and check if `lastEndPoint` matches the start point 3 of the next hop. If they match, update endpoint 4 to the endpoint to be matched, `lastEndPoint`, and check if `lastEndPoint` matches endpoint 5. If they match, update endpoint 6 to the endpoint to be matched, `lastEndPoint`, and check if `lastEndPoint` matches endpoint 7. If they match, update endpoint 8 to the endpoint to be matched, `lastEndPoint`, and check if `lastEndPoint` matches endpoint 9. If they match, update endpoint 10 to the endpoint to be matched, `lastEndPoint`.

[0094] For example, if the circuit start point A and circuit end point correspond to endpoints 2 and 9 respectively, the SNL route end point 4 endpoint is updated to the endpoint to be matched, l_astEndPoint. It is then checked whether l_astEndPoint matches the start point 5 of the next hop. If they match, endpoint 6 is updated to the endpoint to be matched, l_astEndPoint, and it is checked whether l_astEndPoint matches endpoint 7. If they match, endpoint 8 is updated to the endpoint to be matched, l_astEndPoint, and it is checked whether l_astEndPoint matches endpoint 9. If they match, endpoint 9 is updated to the endpoint to be matched, l_astEndPoint.

[0095] For example, the circuit start point A and the circuit end point correspond to endpoints 12 and 17, respectively. Check if endpoints 12 and 13 match. If they match, update endpoint 14 to the endpoint to be matched, lastEndPoint, and check if lastEndPoint matches endpoint 15. If they match, update endpoint 16 to the endpoint to be matched, lastEndPoint, and check if lastEndPoint matches endpoint 17.

[0096] For a reverse route with route CD_UNI (one-way), then... Figure 3The A and Z endpoints need to be reversed for matching; the specific process will not be described in detail in this embodiment. Compared with the solutions in related technologies, the method in this embodiment does not require different processing and detection logic based on different first-hop routing element types. For example, when the first-hop routing element type is SNL, the solutions in related technologies need to drill down layer by layer until all routing elements are SIF or TPL.

[0097] In an exemplary embodiment, detecting whether the route termination point of the current hop in the route element queue matches the circuit termination point in the circuit routing data includes:

[0098] Update the route termination point of this hop to the endpoint to be matched, and check whether the endpoint to be matched matches the circuit termination point in the circuit routing data.

[0099] For example, in combination Figure 3 For circuit routes of CD_BI (bidirectional) or CD_UNI (unidirectional) forward routing: When this hop is the last hop, the updated lastEndPoint needs to be matched with the circuit termination point Z endpoint. If a match is found, the route concatenation for this service is successful; otherwise, the concatenation fails. For example, if the circuit termination point Z is endpoint 10, check if the updated lastEndPoint (to endpoint 10) matches the circuit termination point Z endpoint. If the circuit termination point Z is endpoint 9, check if the updated lastEndPoint (to endpoint 9) matches the circuit termination point Z endpoint. If the circuit termination point Z is endpoint 17, check if the updated lastEndPoint (to endpoint 17) matches the circuit termination point Z endpoint.

[0100] For a reverse route with route CD_UNI (one-way), then... Figure 3 The A and Z endpoints need to be reversed for matching; the specific process will not be described in detail in this embodiment.

[0101] In one exemplary embodiment, before detecting the queue of routing elements within the corresponding level, the process includes:

[0102] The routing element queue is reported to the northbound routing resource;

[0103] Obtain the routing element queue from the northbound routing resources based on the UUID generated by the northbound adaptation layer.

[0104] For example, the routing element queue is reported to the northbound routing resource. The routing element queue, including SIF (cross-connect), SNL (service layer service), TPL (fiber optic connection) and other routing elements, is obtained from the northbound routing resource based on the circuit UUID generated by the northbound adaptation layer.

[0105] In one exemplary embodiment, the method further includes:

[0106] In response to the matching of the route termination point of the current hop in the route element queue with the circuit termination point in the circuit routing data, check whether there is a resource in the resource storage service that corresponds to each hop in the route element queue.

[0107] For example, the second stage of detecting the routing element queue within the corresponding level is the integrity detection of the resources used by the circuit routing. It queries whether the resources used by each hop of the routing element queue can be found in the resource storage service. If they can all be found, it means that the various resources of the circuit routing are real and complete. Otherwise, the circuit routing resources are incomplete, which may pose a risk of communication interruption.

[0108] For example, resource storage services can use SQL to interact with a database to store and retrieve circuit routing data.

[0109] For example, if the route termination point of the current hop in the route element queue matches the circuit termination point in the circuit routing data, it is also necessary to check whether there is a resource in the resource storage service that corresponds to each hop in the route element queue. If it exists, it indicates that the current route status is correct and the route is fully available; otherwise, the route is unavailable.

[0110] In one exemplary embodiment, the method further includes:

[0111] If the route start point in the route element queue does not match the circuit start point in the circuit routing data, or the route end point of the current hop in the route element queue does not match the route start point of the next hop, or the route end point of the current hop in the route element queue does not match the circuit end point in the circuit routing data, or the resource storage service does not have the resource corresponding to each hop in the route element queue, report the route element queue detection failure information in the corresponding level.

[0112] For example, when a detection failure occurs, the detection results of the routing element queue in the corresponding layer can be reported. For example, a detection failure message such as "the business endpoint and the routing hop endpoint do not match" can be reported, or an email can be sent to the corresponding business personnel according to the error code (which can be a combination of numbers or alphanumeric characters, and sometimes also includes descriptive text), or a routing connection success rate and availability detection report can be sent.

[0113] For example, when the detection is successful, the detection results of the routing element queue in the corresponding layer can also be reported. For example, information such as "the business endpoint matches the routing hop endpoint" can be reported as a successful detection, or an email can be sent to the corresponding business personnel based on the success code (which can be a combination of numbers or alphanumeric characters, and sometimes also includes descriptive text), or a routing connection success rate and availability detection report can be sent.

[0114] For example, the above detection method can be a pluggable service plugin that can be integrated into automation to routinely monitor the quality of northbound routing data, handle anomalies in a timely manner, prevent problems from being leaked to customers, and improve customer satisfaction.

[0115] It should be noted that the method described above in this disclosure focuses on the bearing relationship between the current layer's business and its direct service layer during the detection process. Compared with related technologies that start from the client layer endpoint and drill down layer by layer to search for the next hop until searching for complete routing elements, the method in this disclosure significantly improves the efficiency of overall network routing data collection and interconnection detection.

[0116] The above steps resolve the issues of redundant routing data acquisition systems in various operators and government / enterprise systems, where modifications are required for each acquisition system when the underlying routing model changes or is added, resulting in high manpower costs, poor reliability and maintainability, and a lack of data testing tools. This approach reduces redundant development and investment costs across different operator systems, improves the efficiency of routing concatenation generation for the entire network, provides high-quality assurance for northbound routing data reporting, enhances the success rate of routing concatenation across the entire network, and improves the health of the network's services managed by the network vendor.

[0117] Figure 4 This is a flowchart (II) of a circuit routing data processing method according to an embodiment of the present disclosure, as follows: Figure 4 As shown:

[0118] The Business Manager is responsible for managing all business-related operations, including but not limited to the creation, modification, and deletion of businesses, as well as monitoring their status. When performing functions such as business creation, storage, querying, and status monitoring, the Business Manager exchanges data with the "Business Storage Service" to ensure the accuracy and timeliness of business data. It may also interact with the user interface or API components to receive user commands or provide query results. When a new business is created, corresponding routes need to be generated based on business requirements.

[0119] Once the service is created and routes are successfully generated, the service storage service will store the corresponding circuit routing data. At this point, a unified circuit routing model can be built based on the circuit routing data. This unified circuit routing model is then used to transform the circuit routing data to obtain the transformed data. For example, a circuit-level routing model can be built based on the unified circuit routing model, and a routing element model can be built based on that model. The unified circuit routing model transforms the circuit routing data into first data conforming to the circuit routing model; the circuit-level routing model transforms the first data into second data conforming to the circuit-level routing model; and the routing element model transforms the second data into target data (routing element queue) conforming to the routing element model.

[0120] Circuit routing data can be reported to the northbound routing resource in the form of circuit (SNL) asset files, and the routing element queue can be reported to the northbound routing resource in the form of SNT files. The routing element queue can be obtained from the northbound routing resource based on the UUID generated by the northbound adaptation layer.

[0121] The system checks the routing element queue within the corresponding layer. For example, if the current hop is the first hop, it checks whether the starting point of the route in the routing element queue matches the starting point of the circuit in the circuit routing data. If the starting point of the route in the routing element queue matches the starting point of the circuit in the circuit routing data, it checks whether the ending point of the current hop in the routing element queue matches the starting point of the next hop. If the current hop is the last hop, it checks whether the ending point of the current hop in the routing element queue matches the ending point of the circuit in the circuit routing data. If the ending point of the current hop in the routing element queue matches the ending point of the circuit in the circuit routing data, it checks whether the resource storage service exists for each hop in the routing element queue.

[0122] If the route termination point of the current hop in the route element queue matches the route start point of the next hop, and the resource corresponding to each hop exists in the resource storage service, then the qualified route element queues within the corresponding layer will be merged into the interface response results of one or more circuit routing unified reporting interfaces.

[0123] The above embodiments solve the problems of redundant routing data acquisition systems of various operators and government and enterprise systems in related technologies. When the underlying routing model changes or is added, each acquisition system must be modified, resulting in large human resource costs, extremely poor reliability and maintainability, and no data detection tools. The solutions reduce the development and investment costs of redundant systems for different operators, improve the efficiency of routing connection generation for the entire network, provide high-quality assurance for northbound reporting of routing data, improve the success rate of routing connection for the entire network, and enhance the health of the network services of the network management system of the vendor.

[0124] Embodiments of this disclosure also provide a computer-readable storage medium storing a computer program configured to perform the steps in any of the above method embodiments when executed.

[0125] In one exemplary embodiment, the aforementioned computer-readable storage medium may include, but is not limited to, various media capable of storing computer programs, such as a USB flash drive, read-only memory (ROM), random access memory (RAM), portable hard drive, magnetic disk, or optical disk.

[0126] Embodiments of this disclosure also provide an electronic device including a memory and a processor, the memory storing a computer program and the processor being configured to run the computer program to perform the steps in any of the above method embodiments.

[0127] In one exemplary embodiment, the electronic device may further include a transmission device and an input / output device, wherein the transmission device is connected to the processor and the input / output device is connected to the processor.

[0128] Specific examples in this embodiment can be found in the examples described in the above embodiments and exemplary implementations, and will not be repeated here.

[0129] It is obvious to those skilled in the art that the modules or steps of this disclosure described above can be implemented using general-purpose computing devices. They can be centralized on a single computing device or distributed across a network of multiple computing devices. They can be implemented using computer-executable program code, and thus can be stored in a storage device for execution by a computing device. In some cases, the steps shown or described can be performed in a different order than those presented herein, or they can be fabricated as separate integrated circuit modules, or multiple modules or steps can be fabricated as a single integrated circuit module. Thus, this disclosure is not limited to any particular combination of hardware and software.

[0130] The above are merely preferred embodiments of this disclosure and are not intended to limit this disclosure. Various modifications and variations can be made to this disclosure by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the principles of this disclosure should be included within the scope of protection of this disclosure.

Claims

1. A method for processing circuit routing data, characterized in that, include: Retrieve circuit routing data from the business storage service; A unified circuit routing model is constructed based on the circuit routing data; The circuit routing data is transformed using the unified circuit routing model to obtain the transformed data. The converted data is reported to one or more circuit routing unified reporting interfaces.

2. The method according to claim 1, characterized in that, After constructing a unified circuit routing model based on the circuit routing data, the following steps are included: Construct a circuit-level routing model based on the unified circuit routing model; A routing element model is constructed based on the routing model of this circuit layer.

3. The method according to claim 2, characterized in that, The circuit routing data is transformed using the unified circuit routing model to obtain the transformed data, which includes: The circuit routing data is transformed into first data that conforms to the circuit routing model through the unified circuit routing model. The first data is converted into second data that conforms to the circuit-level routing model using the circuit-level routing model. The second data is transformed into target data that conforms to the routing element model using the routing element model.

4. The method according to claim 3, characterized in that, Transforming the circuit routing data into first data conforming to the circuit routing model using the unified circuit routing model includes: Determine the corresponding circuit routing model conversion processor based on the hierarchical information of the business; The circuit routing model conversion processor converts the circuit routing data within the corresponding level into first data that conforms to the unified circuit routing model.

5. The method according to claim 4, characterized in that, Transforming the first data into second data conforming to the circuit-level routing model using the circuit-level routing model includes: Using the circuit-level routing model, the first data within the corresponding layer is grouped according to the routing type and routing direction, so as to convert the first data into second data that conforms to the circuit-level routing model.

6. The method according to claim 5, characterized in that, Transforming the second data into target data that conforms to the routing element model using the routing element model includes: The second data within the group is sorted using the routing element model to obtain the routing element queue; The routing element queue is used as target data that conforms to the routing element model.

7. The method according to claim 6, characterized in that, Reporting the converted data to one or more unified reporting interfaces for circuit routing includes: The queue of routing elements within the corresponding level is merged into the interface response result of the one or more circuit routing unified reporting interfaces.

8. The method according to claim 6, characterized in that, Sorting the second data within the group to obtain the route element queue using the route element model includes: In response to the completeness of the route start and end points, the correctness of the route direction, and the continuity of the route sequence numbers, the second data within the group is sorted according to the route sequence numbers to obtain the route element queue.

9. The method according to claim 6, characterized in that, Before reporting the converted data to one or more unified reporting interfaces for circuit routing, the following steps are included: Inspect the queue of routing elements within the corresponding level.

10. The method according to claim 9, characterized in that, Detecting the queue of routing elements within the corresponding level includes: In response to the fact that this hop route is the first hop, it is checked whether the route start point in the route element queue matches the circuit start point in the circuit route data; In response to a match between the route start point in the route element queue and the circuit start point in the circuit routing data, it is detected whether the route end point of the current hop in the route element queue matches the route start point of the next hop of the current hop. In response to the fact that this hop is the last hop, it checks whether the route termination point of this hop in the route element queue matches the circuit termination point in the circuit routing data.

11. The method according to claim 10, characterized in that, Detecting whether the route termination point of the current hop in the route element queue matches the route start point of the next hop of the current hop includes: Update the route termination point of the current hop in the route element queue to the endpoint to be matched, and check whether the endpoint to be matched matches the route start point of the next hop of the current hop.

12. The method according to claim 10, characterized in that, Detecting whether the route termination point of the current hop in the route element queue matches the circuit termination point in the circuit routing data includes: Update the routing termination point of this hop to the endpoint to be matched, and check whether the endpoint to be matched matches the circuit termination point in the circuit routing data.

13. The method according to claim 9, characterized in that, Before inspecting the queue of routing elements within the corresponding level, the process includes: The routing element queue is reported to the northbound routing resources; The routing element queue is obtained from the northbound routing resources based on the UUID generated by the northbound adaptation layer.

14. The method according to claim 10, characterized in that, The method further includes: In response to a match between the routing termination point of the current hop in the routing element queue and the circuit termination point in the circuit routing data, the system checks whether there is a resource in the resource storage service that corresponds to each hop in the routing element queue.

15. The method according to claim 10 or 14, characterized in that, The method further includes: In response to a mismatch between the route start point in the route element queue and the circuit start point in the circuit routing data, or a mismatch between the route end point of the current hop in the route element queue and the route start point of the next hop of the current hop, or a mismatch between the route end point of the current hop in the route element queue and the circuit end point in the circuit routing data, or a lack of resources in the resource storage service corresponding to each hop in the route element queue, information indicating a failure to detect the route element queue within the corresponding level is reported.

16. The method according to claim 1, characterized in that, The attributes of the unified circuit routing model include at least one of the following: circuit globally unique identifier (UUID), circuit direction, working route set, protection route set, and actual route set.

17. The method according to claim 2, characterized in that, The attributes of the routing model at this layer of the circuit include at least one of the following: route type, forward route element set, reverse route element set, error message, and prompt message; The attributes of the routing element model include at least one of the following: routing element type, route number, route start point, and route end point.

18. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program, wherein the computer program, when executed by a processor, implements the steps of the method described in any one of claims 1 to 17.

19. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the steps of the method described in any one of claims 1 to 17.

20. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method described in any one of claims 1 to 17.

Images