Method, system, device and medium for automatically generating snc and snc routing based on service circuit

Abstract

The application discloses a kind of based on service circuit automatic generation SNC and SNC routing method, system, equipment and medium, including to equipment service information is collected;Restoring service topology and carrying out service internal link judgment;Judge whether service link is complete, complete then check whether there is common port or resource, not complete then return to the step of restoring service topology and carrying out service internal link judgment;For the case of having common port or resource, common resource corresponding hierarchical SNC does not need to be repeatedly generated, for the case of not having common port or resource, generate new SNC;According to service type, connection cross type generates relevant service resource and SNC;The SNC route of service is generated;If service changes, return to the step of restoring service topology and carrying out service internal link judgment.The application can meet the formation of each hierarchical data in the service model involved by access type OTN equipment after service is issued, facilitate the management and monitoring of service data.

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of OTN device service management processing, in particular to a method, system, device and medium for automatically generating SNC and SNC routing based on service circuits. BACKGROUND

[0002] With the evolution of transmission network technology, different manufacturers' access type OTN devices are put into market production and application. After the device carries the service, the user or the upper management system needs to pay attention to the correctness of the service SNC and SNC routing and the integrity of the data, especially in the automatic concatenation application of automatic processing of service data.

[0003] In order to meet the market demand for cost reduction and efficiency increase in the development of device hardware and the construction of manufacturer network management support functions of access segment OTN small factory devices, the device can be put into production and application under the condition of guaranteeing the function of carrying service. With the development of informatization and digitization, if the upper system or the user wants to confirm the service SNC or SNC routing data after the device carries the service, there is a certain difference in the evolution target of informatization and digitization management due to the lack of or non-provision of device basic data. If the service SNC and routing data are to be confirmed, manual checking and output or customized development are needed to make all device manufacturers generate data before providing data to the upper system. In this process, the manual checking method has large data volume and takes a long time to check, the customized method has a large influence range and difficulty in unified standard. It is necessary to automatically process the SNC and SNC routing of the service in the digital management. SUMMARY

[0004] The purpose of the present application is to provide a method, system, device and medium for automatically generating SNC and SNC routing based on service circuits, which can form various levels of data in the service model related to the access type OTN device after the service is issued, and facilitate the management and monitoring of service data.

[0005] To achieve the above purpose, the technical solution provided by the present application is:

[0006] The first aspect of the present application provides a method for automatically generating SNC and SNC routing based on service circuits, comprising the following steps:

[0007] Issue services to different devices to make the devices carry services; collect device service information;

[0008] Restore the service topology and perform service internal link judgment;

[0009] Judge whether the service link is complete, if yes, check whether there are common ports or resources, and if not, return to restore the service topology and perform service internal link judgment;

[0010] For the case of having common ports or resources, the common resource corresponding to the hierarchical SNC does not need to be repeatedly generated, and for the case of not having common ports or resources, a new SNC is generated.

[0011] According to the service type and the connection cross type, relevant service resources and SNCs are generated, and the SNC route of the service is generated.

[0012] If the service changes, the service topology is restored and the intra-service link judgment is performed, and then the next step is continued. If the service does not change, the step is completed.

[0013] To optimize the above technical solutions, the specific measures taken also include:

[0014] In the device management system, the device is subjected to service delivery or the device has already carried the service, the device service information is collected, the CONNECTION, CTP, FTP, PG and PTP of the service are obtained, and according to the PTP port of the device subjected to the service, the service topology is restored through the network topology, and the intra-service link integrity is judged.

[0015] Further, if the service link is not complete, it is known that there are other devices in the service to be continued to be delivered, at this time, the link judgment is continued to be waited for completion; if the link is complete, it is known whether it is a complete service or an incomplete service; at the same time, according to the service data resources, it is known whether there are multiplexed ports and multiplexed time slots in the service, if there are, the SNC of the same level does not need to be generated again, if there are not, the SNC is generated according to the new SNC in the subsequent logic, at this time, the SNC of all levels of the service can be generated, and the SNC of the direction of the incomplete service is the same as the incomplete case, and the SNC of each segment is complete data.

[0016] Further, after the SNC is stored, according to the relevant SNC of the service, the SNC data of the lower layer is used and combined with the CTP, FTP, PG and PTP data to generate the SNC route data of each hierarchical SNC in turn.

[0017] Further, according to the known service information, the service type, the service data cross type, the port object of the CONNECTION connection two ends and the associated or bound data relationship are automatically identified, and then the corresponding SNC is automatically generated according to the service granularity matching relationship between the interconnected devices; the SNC route is automatically generated according to the SNC and the service layer of the SNC.

[0018] Further, based on the case that the existing network service changes, the service topology is restored and the intra-service link judgment step is dynamically executed according to the change of the service data, so that the service link continues to execute the subsequent step, and the automatic update of the SNC and the SNC route data under the service change condition is realized.

[0019] The application makes the service data pass through the service-related cross-connection (CONNECTION) data and the corresponding CTP, FTP, PG, PTP and topology data to automatically generate the relevant service resource of the feature type of the service data under the premise of the complete service topology link.

[0020] The second aspect of the application provides a system for automatically generating SNC and SNC routing based on service circuit, comprising:

[0021] A service issuing module is configured to issue services to different devices so that the devices bear the services.

[0022] A service collection module is configured to collect device service information.

[0023] A link judgment module is configured to restore service topology and perform intra-service link judgment, and check whether there is a shared port or resource. If there is a shared port or resource, the corresponding hierarchical SNC does not need to be generated repeatedly. If there is no shared port or resource, a new SNC needs to be generated.

[0024] An SNC generation module is configured to automatically identify the service type, the service data cross type, the port object and the associated or bound data relationship of the two ends of the CONNECTION connection, and automatically generate the corresponding SNC in combination with the service granularity matching relationship between the interconnected devices.

[0025] An SNC routing generation module is configured to automatically generate SNC routing based on the SNC and the service layer of the SNC.

[0026] A service change processing module is configured to dynamically execute the step of restoring service topology and performing intra-service link judgment based on the change of the existing network service, so that the service link continues to execute the subsequent steps.

[0027] The system is configured to execute the method for automatically generating SNC and SNC routing based on service circuit.

[0028] The third aspect of the application provides an electronic device, characterized in that comprising a memory, a processor and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, the method for automatically generating SNC and SNC routing based on service circuit is realized.

[0029] The fourth aspect of the application provides a computer-readable storage medium storing a computer program, which makes a computer execute the method for automatically generating SNC and SNC routing based on service circuit.

[0030] Compared with the prior art, the application has the following advantages:

[0031] The application can restore service topology through network topology according to PTP port of the device under service, judge link integrity in service, and generate relevant service resources automatically according to characteristic type of service data based on service topology link integrity, service related cross connection (CONNECTION) data, and corresponding CTP, FTP, PG, PTP, and topology data, so as to form each level data in service model related to access type OTN device after service is issued, and facilitate management and monitoring of service data.

[0032] The method of the application supports that the device CONNECTION connection, cross, PTP, CTP, FTP, and PG object report or collect after service is issued in the service management of access type OTN device of the same manufacturer or different manufacturers.

[0033] The application automatically identifies service type, service data cross type, port object and associated or bound data relationship of two ends of CONNECTION connection according to known service information, and generates corresponding SNC by combining service granularity matching relationship between interconnected devices.

[0034] The application can be compatible with SNC and SNC route sharing situation under different service resource multiplexing scenarios, realize quick query or resource reporting of service SNC and SNC route, and can be compatible with automatic regeneration of SNC and SNC route under service data change. BRIEF DESCRIPTION OF DRAWINGS

[0035] Figure 1 The flowchart of the method for automatically generating SNC and SNC route based on service circuit of the application.

[0036] Figure 2 The data generation reference model diagram under the condition that the service type of the access type OTN device in the embodiment of the application is EOO, EOS, and OTN.

[0037] Figure 3 The data generation reference model diagram under the condition that the service type of the access type OTN device in the embodiment of the application is EOO, EOS, and OTN.

[0038] Figure 4 The data generation model diagram under the condition that the service type of the access type OTN device in the embodiment of the application is pure Ethernet, Ethernet with cross, pure EOS, and mixed use mode with final bearing to OTN interface. DETAILED DESCRIPTION

[0039] The above content of the present application will be further explained in detail by way of examples below, but this should not be understood as limiting the scope of the above subject matter of the present application to the examples below, and any technology realized based on the above content of the present application falls within the scope of the present application.

[0040] Some terms in the present application are explained as follows:

[0041] PTP: physical port.

[0042] CTP: connection port.

[0043] FTP: floating port.

[0044] PG: protection group.

[0045] CONNECTION: service connection.

[0046] The present application proposes in an embodiment a method for automatically generating SNC and SNC route based on service circuit, as shown in Figure 1 The method comprises the following steps:

[0047] Service is issued to different devices, so that the devices bear the service; device service information is collected;

[0048] Service topology is restored and service internal link is judged;

[0049] It is judged whether the service link is complete, if yes, it is checked whether there is a common port or resource, if not, the service topology is restored and service internal link is judged again;

[0050] For the case of having common port or resource, the common resource corresponding to the hierarchical SNC does not need to be repeatedly generated, and for the case of not having common port or resource, a new SNC is generated;

[0051] According to the service type and connection cross type, relevant service resource and SNC are generated; SNC route of the service is generated;

[0052] If the service changes, the service topology is restored and service internal link is judged again, and then the following steps are continued, if the service does not change, the steps are completed.

[0053] In the present application, SNC and SNC route of relevant service are automatically generated after service management under configuration of OTN devices of same manufacturer or different manufacturers. The device type under service is automatically judged whether there is a fiber transceiver, if the service has a fiber transceiver type device, data starts from the fiber transceiver, if there is no fiber transceiver, data starts from the position of CPE under the service.

[0054] The whole service type includes EOO, EOS, OTN, OSU, EOOSU of the line side standard OTN bearing mode which can be uploaded by the access type OTN device, and at the same time covers the non-standard service of the single device customer side port-customer side end has complete class, or the service type composed of the mixed mode of such non-standard and standard. After the service creation is completed, each level SNC automatically identifies the respective AZ end port according to the related service data, and the service resource data automatically generates cc cross according to the CONNECTION connection type sdh, odu, odu connection, and automatically generates mfdfr when the CONNECTION connection type is eth connection. Each type of service automatically generates each layer SNC from the service layer according to the service type, until the TL level, and the SNC routing of each layer SNC is automatically connected in series and generated according to the SNC of the lower layer. Finally, the complete SNC and SNC routing data of the service are formed.

[0055] In combination Figure 1 The process of automatically generating SNC and SNC routing from service creation in the application is described in detail.

[0056] In the device management system, when the device is subjected to service delivery or the device has already carried the service, the service information of the device is collected to obtain the CONNECTION, CTP, FTP, PG, PTP of the service, and the service topology data can be obtained from the PTP and the network topology, so that the link data of the service can be restored. That is, it can be judged whether the service link is complete, if not, it can be known that there are other devices in the service to be continued to be delivered, at this time, the link is continued to be judged to be complete. If the link has been complete, it can be further known whether it is a complete service or an incomplete service. At the same time, according to the service data resource, it can be known whether there are multiplexing ports, multiplexing time slots and the like in the service, if there are, the SNC of the same level does not need to be generated again, if there are not, the SNC is generated according to the new SNC in the subsequent logic. At this time, the SNC of all levels of the service can be generated, and the SNC of the direction of the incomplete service is the same as the incomplete case, and the SNC of each segment in the complete case is complete data.

[0057] After the SNC is stored, the SNC routing data of each level SNC can be generated in turn according to the related SNC of the service and by using the lower layer SNC data and combining the CTP, FTP, PG, PTP, PG data.

[0058] If the existing network service needs to be replaced due to necessary reasons such as device abnormality, according to the change of the service data, the service topology is restored and the link judgment step in the service is performed dynamically, that is, the service link is from complete to incomplete and then complete again, and the subsequent steps are automatically executed, so that the SNC and SNC routing data can be automatically updated under the service change.

[0059] In some embodiments, in combination with Figure 2 The reference model for generating data in the access type OTN device in the application is described in detail under the condition that the service type carried by the OTN device is EOO, EOS and OTN.

[0060] After the service is created, all connection information of the service can be known, the mfdfr is automatically generated according to the eth connection, and the cc cross is automatically generated according to the odu and osu connection. Similarly, according to the physical port type involved in the service, the customer side port is ETH, and the corresponding service starting from the Ethernet port can be known, such as Figure 2 The left and middle views in the figure, the CTP associated with the PTP of the ETH can directly generate the FDFR, and the generation is simultaneously based on whether the current service is a half circuit to generate an uncompleted FDFR, or a complete circuit to generate the FDFR in the figure. The lower SNC is L2 link. If the customer side port is ODU, the corresponding service can be known as OTN service, such as Figure 2 The right view in the figure, the CTP associated with the PTP of the ODU can directly generate the DSR, and the generation is simultaneously based on whether the current service is a half circuit to generate an uncompleted DSR, or a complete circuit to generate the DSR in the figure. Figure 2 The left view, and the lower layer is based on the service granularity EOO service to generate the SNC of the ODU0 or ODUflex level. Since the access segment small manufacturer device is almost 10G port, the lower layer is ODU2, OTU2, OCH and TL in turn. Figure 2 The middle view is the vc level SNC when the EOS continues to generate, and the vc4 server continues to generate when the low order cross is generated, and the lower layer is MS, RS, ODU0 / ODU1, ODU2, OTU2, OCH and TL in turn. Figure 2 The middle right view is the ODU0 / ODU1 / ODUflex / ODU2 when the OTN continues to generate. When the current layer is ODU0 / ODU1 / ODUflex, the lower layer is ODU2, OTU2, OCH and TL in turn. If it is directly ODU2, the lower layer is OTU2, OCH and TL. Thus, the SNC of the access type OTN service class under the common EOO, EOS and OTN scene is generated completely. The SNC of each layer is automatically generated according to all SNCs of the lower layer and the same layer of the service layer, and the corresponding mfdfr, cc and pg data.

[0061] In some embodiments, in combination with Figure 3 The reference model for generating data in the access type OTN device in the application is described in detail under the condition that the service type carried by the OTN device is EOO, EOS and OTN.

[0062] After the service is created, all connection information under the service can be viewed. For ETH connections, an MFDFR is automatically generated; for SDH, ODU, and OSU connections, a CC cross-connect is automatically generated. Similarly, based on the physical port type involved in the service, if the client-side port is ETH, then the corresponding service originates from an Ethernet port. Figure 3 The left-hand view shows that the CTP associated with the PTP of this ETH can directly generate FDFRs. The generation process involves simultaneously determining whether the current service is a half-circuit; if so, an unfinished FDFR is generated. If it's a complete circuit, an incomplete FDFR is generated. The lower-level SNC is L2link. If the client-side port is an OSU, it indicates that the corresponding service is an OSU service, such as... Figure 3 The right-hand view shows that the CTP associated with the OSU's PTP can directly generate a CLIENT. The generation process depends on whether the current service is a half-circuit; if so, an unfinished CLIENT is generated. If it's a complete circuit, an in-process CLIENT is generated. The next layer down is OSUflex, ODU0 / flex / 2. If the current layer is ODU0 / ODUflex, the next layer down is ODU2, OTU2, OCH, TL. If it's directly ODU2, the next layer is OTU2, OCH, TL. At this point, the SNC in the EOOSU and OSU scenarios is fully generated. The SNC reason for each layer is automatically generated based on all SNCs in the same layer of the service layer below, combined with the corresponding mfdfr, cc, and pg data.

[0063] In some specific implementations, combined with Figure 4 The data generation of the access-type OTN device in this invention is described in detail when the service types are pure Ethernet, Ethernet with cross-connect, pure EOS, and mixed with the final OTN interface.

[0064] After service creation, all connection information under the service is available. If a single device within the service has client-side ports (not OTN ports) for both upstream and downstream connections, an MFDFR will be automatically generated based on the eth connection. For sdh, odu, and osu connections, a CC cross-connection will be automatically generated. If it is a pure Ethernet service for a single device, the SNC level ends at L2link. If it is a pure EOS service with a CC cross-connection, a relevant VC-level SNC will be generated. If the service involves multiple interconnected devices (client-side ports connected between two devices), it is compatible with all situations. Relevant SNC data is generated according to the actual internal data, level, connection relationship, and whether the service circuit is terminated or not. At this point, the actual AZ port from the service end to the port will also be determined. Similarly, the SNC route is automatically generated by referring to all SNCs in the same layer of the service layer and combining the corresponding MFDFR, CC, and PG data.

[0065] The application provides a system for automatically generating SNC and SNC routing based on service circuits in another embodiment, comprising:

[0066] A service issuing module is used for issuing services to different devices so that the devices bear the services.

[0067] A service collecting module is used for collecting device service information.

[0068] A link judging module is used for restoring service topology and judging the links in the services, checking whether there are shared ports or resources, and generating a new SNC if there are no shared ports or resources.

[0069] An SNC generating module is used for automatically identifying service types, service data cross types, port objects at two ends of a CONNECTION connection and associated or bound data relations, and automatically generating corresponding SNCs in combination with service granularity matching relations between interconnected devices.

[0070] An SNC routing generating module is used for automatically generating SNC routing based on SNC and service layers of the SNC.

[0071] A service change processing module is used for dynamically executing the step of restoring service topology and judging the links in the services based on the change of service data, and making the service links continue to execute subsequent steps.

[0072] The system is used for executing the method for automatically generating SNC and SNC routing based on service circuits.

[0073] The third aspect of the application provides an electronic device, which comprises a memory, a processor and a computer program stored in the memory and executable on the processor, and when the processor executes the computer program, the method for automatically generating SNC and SNC routing based on service circuits is realized.

[0074] The fourth aspect of the application provides a computer readable storage medium, which stores a computer program, and the computer program enables a computer to execute the method for automatically generating SNC and SNC routing based on service circuits.

[0075] In embodiments disclosed herein, a computer storage medium can be a tangible medium that can contain or store a program for use by or in connection with an instruction execution system, apparatus, or device. Computer storage media can include, but are not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of computer storage media can include, but are not limited to, an electrical connection based on one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0076] The above description is only the preferred embodiment of the present application, not any form of limitation to the present application, any skilled person in the art, without departing from the technical solution of the present application, according to the technical essence of the present application, any simple modification, equivalent replacement and improvement of the above embodiment, etc., still belongs to the protection scope of the technical solution of the present application.

Claims

1. A method for automatically generating SNCs and SNC routes based on service circuits, characterized in that, Includes the following steps: Distribute services to different devices to enable the devices to carry out the services; Collect equipment business information; Reconstruct the business topology and determine the internal links within the business; Determine if the business link is complete. If it is complete, check if there are shared ports or resources. If it is incomplete, return to restore the business topology and perform a business link judgment. If there are shared ports or resources, the SNC at the corresponding level of the shared resources does not need to be generated again; if there are no shared ports or resources, a new SNC is generated. Generate relevant business resources and SNCs based on business type and connection cross-type; Generate SNC routes for the service; If the service changes, the system returns to restore the service topology and performs an internal link judgment, which can realize the automatic update of SNC and SNC routing data in the event of service changes. Based on changes in existing network services, the system dynamically executes steps to restore the service topology and determine intra-service links according to changes in service data, enabling the service links to continue executing subsequent steps, thereby achieving automatic updates of SNC and SNC routing data in the event of service changes.

2. The method for automatically generating SNCs and SNC routes based on service circuits according to claim 1, characterized in that: When a device is issuing services to another device or when a device is already carrying services, the device's service information is collected in the device management system. This allows the collection of the service's CONNECTION, CTP, FTP, PG, and PTP. Based on the PTP port of the device under the service, the service topology can be restored through the network topology to determine the integrity of the service's internal links.

3. The method for automatically generating SNCs and SNC routes based on service circuits according to claim 2, characterized in that: If the service link is incomplete, it indicates that there are other devices within the service that need to be further distributed. At this point, we continue to wait for the link to be determined to be complete. If the link is complete, it indicates whether it is a terminated or unterminated complete service. At the same time, based on the service data resources, it can be determined whether there are reused ports or reused time slots within the service. If they exist, the SNC at the same level does not need to be generated again. If they do not exist, they will be generated according to the new SNC in the subsequent logic. Thus, SNCs at all levels under the service can be generated. Similarly, the SNCs for unterminated service directions are also considered unterminated. In the terminated case, the SNCs for each segment are complete data.

4. The method for automatically generating SNCs and SNC routes based on service circuits according to claim 3, characterized in that: After storing the SNC, the SNC routing data for each level of SNC is generated sequentially based on the relevant SNC under the business, using the lower-level SNC data and combining it with CONNECTION, CTP, FTP, PG, and PTP data.

5. The method for automatically generating SNCs and SNC routes based on service circuits according to claim 1 or 4, characterized in that: Based on known business information, the system automatically identifies the business type, business data cross-type, port objects at both ends of the CONNECTION connection, and associated or bound data relationships. It then automatically generates the corresponding SNC based on the business granularity matching relationship between interconnected devices. Based on the SNC and the SNC service layer, the system automatically generates SNC routes.

6. The method for automatically generating SNCs and SNC routes based on service circuits according to claim 1, characterized in that: Under the premise of complete business topology links, business data can be automatically generated by using business-related cross-connection CONNECTION data, as well as corresponding CTP, FTP, PG, PTP, and topology data to identify the characteristic types of business data and generate relevant business resources.

7. A system for automatically generating SNCs and SNC routes based on service circuits, characterized in that, include: The service delivery module is used to deliver services to different devices, enabling the devices to carry the services; The service acquisition module is used to collect equipment service information; The link judgment module is used to restore the service topology and judge the links within the service, as well as check whether there are shared ports or resources. If there are shared ports or resources, the corresponding SNC at the level of the shared resources does not need to be generated again. If there are no shared ports or resources, a new SNC needs to be generated. The SNC generation module is used to automatically identify the service type, service data cross type, port objects at both ends of the CONNECTION connection and associated or bound data relationship based on known service information, and then automatically generate the corresponding SNC based on the service granularity matching relationship between interconnected devices. The SNC route generation module is used to automatically generate SNC routes based on the SNC and its service layer. The business change processing module is used to dynamically execute the steps of restoring the business topology and judging the internal links of the business based on the changes in the business data when changes occur in the existing network services, so that the business links can continue to execute subsequent steps. Based on changes in existing network services, the system dynamically executes steps to restore the service topology and determine intra-service links according to changes in service data, enabling the service links to continue executing subsequent steps, thereby achieving automatic updates of SNC and SNC routing data in the event of service changes. The system is used to perform the method of automatically generating SNCs and SNC routes based on service circuits as described in any one of claims 1 to 6.

8. An electronic device, characterized in that, include: A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein when the processor executes the computer program, it implements the method for automatically generating SNCs and SNC routes based on service circuits as described in any one of claims 1 to 6.

9. A computer-readable storage medium storing a computer program that causes a computer to perform a method for automatically generating SNCs and SNC routes based on service circuits as described in any one of claims 1 to 6.

Images