A method, device and equipment for automatically opening a transmission network service and a storage medium

Abstract

The application discloses a kind of transmission network service automatic opening method, device and equipment and storage medium, belong to the technical field of telecommunication transmission network.The method comprises: obtaining multiple management domain sub-paths and control parameters by coordinator;Based on multiple management domain sub-paths and the control parameters, the network level where the management domain is located is identified, and an identification result is obtained;Based on the identification result and the control parameters, the protection configuration of each link in the management domain and the cross-domain interface position is determined;The protection configuration is converted into device identifiable end-to-end service automatic opening instruction, and is issued to each network element, so that each network element executes the end-to-end service automatic opening instruction.By the present application, the technical problem of low success rate and reliability of service automatic opening in the prior art is solved.

Description

Technical Field

[0001] This application belongs to the field of telecommunications transmission network technology, and specifically relates to a method, apparatus, equipment and storage medium for automatic activation of transmission network services. Background Technology

[0002] With the rapid development of transport network services, automated commissioning has become a core means to improve network operation and maintenance efficiency. Currently, mainstream automated commissioning solutions for transport networks generally adopt a layered architecture and centralized control mode. This mainly includes a coordinator, controller, network management system, and equipment layer.

[0003] However, in complex environments with multiple vendors, multiple operators, and multiple management domains, the northbound interface (the interface that the lower layer (e.g., the controller) opens to the upper layer (e.g., the coordinator)) lacks a unified standard. Different vendors implement interface definitions based on different data models, resulting in differences in parameter expression and semantics. In complex networking environments with multiple management domains, it is difficult to support segmented protection, asymmetric protection, and pass-through scenarios, affecting the success rate and reliability of service activation.

[0004] Therefore, there is an urgent need for a method that can improve the success rate and reliability of automatic service activation in complex environments with multiple management domains. Summary of the Invention

[0005] This application provides a method, apparatus, device, and storage medium for automatic activation of transmission network services, which can solve the technical problems of low success rate and low reliability of automatic service activation in the prior art.

[0006] To achieve the above objectives, this application provides the following technical solution: A method for automatically activating transmission network services, the method comprising: Obtain multiple management domain sub-paths and control parameters through the coordinator; The network layer of this management domain is identified based on multiple management domain sub-paths and the control parameters, and the identification result is obtained. Based on the identification results and the control parameters, the protection configuration of each link segment and cross-domain interface location within this management domain is determined; The protection configuration is converted into an end-to-end service auto-enabling instruction that can be recognized by the device, and then sent to each network element so that each network element can execute the end-to-end service auto-enabling instruction.

[0007] Based on the same inventive concept, embodiments of this application also provide an automatic transmission network service activation device, the device comprising: The information acquisition module is configured to acquire multiple management domain sub-paths and control parameters through the coordinator; The network hierarchy identification module is configured to identify the network hierarchy of the current management domain based on multiple management domain sub-paths and the control parameters, and obtain the identification result; The protection configuration derivation module is configured to determine the protection configuration of each link segment and cross-domain interface location within this management domain based on the identification results and the control parameters. The service activation instruction generation module is configured to convert the protection configuration into an end-to-end service automatic activation instruction that can be recognized by the device, and send it to each network element so that each network element can execute the end-to-end service automatic activation instruction.

[0008] Based on the same inventive concept, this application also provides an electronic device, including: a memory and a processor; the processor is used to read and execute a computer program stored in the memory to implement the steps of the aforementioned method for automatically activating transmission network services.

[0009] Based on the same inventive concept, this application also provides a computer storage medium storing computer-executable instructions, which, when executed, implement the steps of the aforementioned method for automatically activating transmission network services.

[0010] Compared with the prior art, this application has the following advantages: The system acquires multiple management domain sub-paths and control parameters; identifies the network layer of the management domain based on these sub-paths and control parameters, obtains identification results, and determines the protection configuration for each link segment and cross-domain interface location within the management domain based on these results and control parameters; converts the protection configuration into an end-to-end automatic service activation instruction recognizable by the device and distributes it to each network element for execution; the coordinator only needs to uniformly distribute inter-domain mode control parameters to determine the protection configuration for each cross-domain segment, eliminating the need for complex private coordination and negotiation between management domains, directly achieving consistency in cross-domain protection policies, and eliminating the need for complex multi-domain collaborative calculations; it also supports a single service request carrying multiple independent policy sub-fields of management domains, with each management domain only needing to execute protection logic locally based on its own policy sub-fields; domains without distributed policies directly reuse the system's default policy, eliminating the need for unified centralized calculations based on the global network topology, allowing each domain to independently complete protection decisions, reducing overall system complexity, and improving the success rate and reliability of automatic service activation; This application solves the technical problems of low success rate and low reliability of automatic service activation in the prior art.

[0011] Other features and advantages of this application will be set forth in the description which follows, and will be apparent in part from the description, or may be learned by practicing the application. The objectives and other advantages of this application may be realized and obtained by means of the structures pointed out in the description, claims and drawings. Attached Figure Description

[0012] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0013] Figure 1 This is a schematic diagram of the overall architecture of an embodiment of this application; Figure 2 A flowchart illustrating the method provided in the embodiments of this application; Figure 3 This is a schematic diagram of a cross-domain segmentation protection control mechanism according to an embodiment of this application; Figure 4 This is a typical network topology and layering diagram of cross-domain services according to an embodiment of this application; Figure 5 This is a schematic diagram of the functional modules of an embodiment of the automatic service activation device for the transmission network of this application. Figure 6 This is a schematic diagram of the structure of an electronic device according to an embodiment of this application. Detailed Implementation

[0014] To make the objectives, technical solutions, and advantages of the embodiments of this application clearer, the technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0015] To address the shortcomings of existing technologies, refer to Figure 1 , Figure 1 This is a schematic diagram of the overall architecture of an embodiment of this application. Figure 1As shown, in this embodiment, the architecture, from top to bottom, includes a service request module, a coordinator module, and multiple management domain control modules. Each management domain control module is connected to the corresponding network management system and device network. Module 3_Management Domain Control Module A, Module 6_Network Management System A, and Network A_Device Network belong to one management domain A; Module 4_Management Domain Control Module B, Module 7_Network Management System B, and Network B_Device Network belong to management domain B; Module 5_Management Domain Control Module C, Module 8_Network Management System C, and Network C_Device Network belong to management domain C.

[0016] Sub-services in management domain A are cross-domain services originating from the destination; sub-services in management domain B are cross-domain services originating from both ends; and sub-services in management domain C are cross-domain services originating from the source. The two management domains connect via an NNI interface.

[0017] Among them, Module 1_Service Request Module is used to receive end-to-end service activation requests issued by the user side. The request includes parameters such as source and destination network element information, service type, and service level constraints.

[0018] Module 2, the Coordinator module, is used to uniformly parse service requests, perform path calculations based on the entire network topology, identify cross-domain boundary locations, decompose end-to-end services into multiple management domain sub-services, and convert user intents into control parameters supported by the lower-level controller. Simultaneously, it allocates service-level policy parameters, cross-domain interface NNIs (Network Node Interfaces), and their inter-domain mode control parameters (mode parameters) to each management domain.

[0019] Each management domain control module corresponds to an independent management domain. Within each management domain, its own network management system manages devices and controls resources. Different management domains interconnect via NNI interfaces. The NNI interface carries cross-domain service connections, and its inter-domain mode control parameters describe the cross-domain protection method. Boundary network elements between management domain A and management domain B are interconnected through the same number of NNI ports, as are boundary network elements between management domain B and management domain C. The inter-domain mode control parameters of the NNIs connected to management domains A and C can be configured independently. This technology supports asymmetric protection scenarios at both ends.

[0020] For example: Management domain A has two NNIs, NNI-A1 and NNI-A2, and two NNIs connected to management domain B are NNI-B1 and NNI-B2. The two NNIs of the destination in management domain B are NNI-B3 and NNI-B4, and two NNIs connected to management domain C are NNI-C1 and NNI-C2.

[0021] The inter-domain mode control parameters for NNI-A1, NNI-B1, NNI-A2, and NNI-B2 are set to sncp; the inter-domain mode control parameters for NNI-B3 and NNI-B4 are set to pass-through; and the inter-domain mode control parameters for NNI-C1 and NNI-C2 are set to sncp. This achieves asymmetric protection configuration for the two interconnected segments in management domain B.

[0022] In another embodiment, for SDH services on the same network, the inter-domain mode control parameters for NNI-A1, NNI-B1, NNI-A2, and NNI-B2 are set to msp, while the inter-domain mode control parameters for NNI-B3, NNI-C1, NNI-B4, and NNI-C2 are set to sncp. This achieves asymmetric protection configuration by adjusting the protection type of the two interconnected segments in management domain B.

[0023] In management domain B, the source-destination boundary network element role is a core network element, while in management domains A and C, the boundary network element role is a metropolitan area interconnection network element. The network management system then performs network layer identification based on the boundary network element roles in the sub-service path and determines the layer scope involved in each management domain according to the aforementioned rules. Management domains A and C include the access layer and metropolitan area layer, while management domain B includes the core layer. Next, each management domain can apply its own policy from the service layer policy parameters issued by the coordinator. Each domain uses this policy to configure different protection types or no protection for certain parts within its domain.

[0024] Each network management system controls its subordinate device network, which consists of multiple network elements used for actual service connections and protection group configuration. Devices from different manufacturers can be interconnected within the same device network, and the network management system achieves unified control through standard or adapter interfaces.

[0025] The above architecture enables unified orchestration of end-to-end services in a multi-management domain environment. The coordinator is responsible for cross-domain coordination, the management domain control module is responsible for intra-domain execution, and the NNI interface is responsible for cross-domain connection, thereby supporting the decoupling mechanism of cross-domain protection and intra-domain protection proposed in this invention.

[0026] Furthermore, referring to Figure 2 This application discloses a method for automatically activating transmission network services, including: Step S10: Obtain multiple management domain sub-paths and control parameters; In some specific embodiments, multiple management domain sub-paths are obtained, including: Based on the network topology resource information, the coordinator, upon receiving a service request, performs path calculation to obtain an end-to-end basic service path that meets the service level constraint parameters. The service request includes the source user interface or network element, the destination user interface or network element, the service type, the service bandwidth constraint, and the service level constraint parameters. Identify the multiple management domain boundaries involved in the basic business path, divide them according to the management domain, decompose the end-to-end path into multiple management domain sub-paths and send them to the local domain network management system.

[0027] In this embodiment, the service request module sends an end-to-end service request to the coordinator. The service request includes at least the source user interface or network element, the destination user interface or network element, the service type, the service bandwidth constraint, and the service level constraint parameters. The service level constraint parameters describe the service's requirements for reliability, bandwidth, latency, and protection level.

[0028] After receiving a service request, the coordinator performs path calculation based on the network topology resource information to obtain an end-to-end basic service path that satisfies the service constraints. The basic path includes the service source and destination, as well as the constraint resources and boundary resources that the source and destination pass through in sequence.

[0029] During path calculation, the coordinator identifies multiple management domain boundaries involved in the path and divides them according to the management domain, breaking down the end-to-end business basic path into multiple management domain sub-paths, while determining the cross-domain interface between adjacent management domains. During the business basic path decomposition process, it automatically identifies source-end cross-domain network elements, destination-end cross-domain network elements, cascade network elements, and through-network elements, and sets differentiated processing rules for different roles (cascade network elements are independently configured with protection based on their respective NNI inter-domain mode control parameters, while through-network elements only transmit data without establishing protection groups). This design, which finely distinguishes protection logic according to network element roles, can flexibly adapt to various complex business scenarios such as segmented protection, asymmetric protection, and hybrid protection under multi-domain networking, and can meet diverse business needs. Cross-domain interfaces are represented in NNI (Network Node Interface) format and carry inter-domain mode control parameters to describe the protection method of the cross-domain interface. Different cross-domain interfaces can correspond to different inter-domain mode control values ​​to express the protection requirements or pass-through requirements of each cross-domain segment. Inter-domain mode control parameters include no protection, SNCP protection (subnet connection protection), MSP protection (multiplex section protection), and pass-through, which are used to uniquely determine the protection configuration of the cross-domain segment.

[0030] Specifically, refer to Figure 3 , Figure 3 This is a schematic diagram of a cross-domain segmentation protection control mechanism according to an embodiment of this application. Figure 3 As shown, in a multi-management-domain service path, adjacent management domains are connected via NNI interfaces. Each NNI interface is configured with inter-domain mode control parameters to indicate the protection method for that cross-domain segment. These inter-domain mode control parameters can represent modes such as SNCP protection, MSP protection, no protection, or pass-through.

[0031] During service activation, the coordinator orchestrates the inter-domain mode control parameters for each NNI interface, using these parameters as the sole basis for cross-domain protection. For NNI interfaces with protection-type inter-domain mode control parameters, the management domains on both sides of the interface must establish a consistent primary / backup path relationship and form a protection connection at the boundary network element.

[0032] For NNI interfaces with unprotected inter-domain mode control parameters, only a single-path connection is established, and no protection group configuration is involved. For NNI interfaces with pass-through inter-domain mode control parameters, no protection configuration is established on both sides of the interface; only the existing path is passed through.

[0033] Through the above mechanism, the decoupling of cross-domain protection control and intra-domain policies is achieved. That is, cross-domain protection is completely controlled by inter-domain mode control parameters, and is not directly affected by the internal policies of each management domain, thereby ensuring the consistency and controllability of protection configurations between different management domains.

[0034] In some specific embodiments, obtaining control parameters includes: The coordinator performs semantic parsing on business requests, transforms business service level constraint parameters into executable control parameters, and sends them to the local network management system.

[0035] In this embodiment, after path decomposition, the coordinator performs semantic parsing on service requests, transforming service level constraint parameters into executable control parameters. These control parameters include inter-domain mode control parameters for the primary / backup path cross-domain interface control parameters, and service-level policy fields for control parameters within each management domain. The service-level policy fields describe the protection configuration and default processing rules for paths within each management domain, and are organized by network layer. These service-level policies include access layer policies, metropolitan area layer policies, and core layer policies. Each layer policy can independently define protection type priority, whether protection is enabled, and the degradation processing method under resource shortage conditions. The service-level policy fields do not directly apply to cross-domain segments; the protection configuration at the cross-domain interface is determined only by the inter-domain mode control parameters of the corresponding NNI. The service-level policy fields support carrying multiple layer policies simultaneously within the same service, with each management domain applying the policy at its corresponding network layer.

[0036] Since the business-level policy field of the control parameters is used to describe the protection configuration of the internal paths of each management domain, and the inter-domain mode control parameter (mode parameter) of the control parameters determines the protection configuration at the cross-domain interface, a separation mechanism is implemented in which cross-domain protection is controlled by the inter-domain mode control parameter of the control parameters and intra-domain protection is controlled by the business-level policy field of the control parameters. This separates cross-domain protection and intra-domain protection in terms of architecture, making the decoupled control of intra-domain protection and cross-domain protection clearer, the system structure clearer, and the division of responsibilities more explicit.

[0037] On the other hand, by abstracting complex protection logic into fixed inter-domain mode control parameters and structured business layer policy fields, it is no longer necessary to pass a large number of fragmented private configuration parameters through the northbound interface. The parameter semantics are unified and the combination rules are clear, reducing parameter coupling and adaptation ambiguity, reducing the configuration complexity of the northbound interface, and improving the success rate of automatic service activation from the root.

[0038] Step S20: Identify the network layer of this management domain based on multiple management domain sub-paths and the control parameters to obtain the identification result; In some specific embodiments, step S20 includes: The default processing rules for paths within the management domain are determined based on the control parameters. Based on the boundary network element roles in multiple management domain sub-paths, the network layer of this management domain is identified according to the mapping relationship between network element roles and network layers, the default processing rules, and the combination rules, and the identification results are obtained.

[0039] In this embodiment, the coordinator encapsulates the end-to-end service decomposition results, inter-domain mode control parameters, and service hierarchy policy fields in a unified manner, and distributes them to the corresponding controllers according to the management domain. After receiving the sub-services, each controller completes the service model adaptation and fully transmits the service hierarchy policy and the inter-domain mode control parameter fields of each NNI to the local network management system. For management domains where no policy is explicitly distributed, the controller adopts the default policy pre-configured by the system.

[0040] Within each management domain, the network management system performs intra-domain network layering processing for sub-services based on pre-configured or coordinated network element role information. These network element roles are maintained by the network management system and include access network elements, metropolitan area aggregation network elements, metropolitan area interconnection network elements, and core network elements.

[0041] The network management system performs network layer identification based on the boundary network element roles in the sub-service path, and determines the layer scope involved in this management domain according to the following rules.

[0042] The network management system determines the network layer of its management domain based on the roles of boundary network elements in the sub-service path. The determination is divided into single-end cross-domain scenarios and dual-end cross-domain scenarios, and follows unified layer mapping and combination rules.

[0043] To ensure consistency in judgment, the mapping relationship between network element roles and network layers is first defined as follows: Access network elements correspond to the access layer, metropolitan area aggregation network elements correspond to the metropolitan area layer, metropolitan area interconnection network elements correspond to the metropolitan area layer, and core network elements correspond to the core layer.

[0044] Based on this, the network management system determines the hierarchy according to the following combination of rules: Single-end cross-domain scenario: When there is only one cross-domain boundary network element in this management domain, the hierarchical range of this management domain is determined based on the role of that boundary network element.

[0045] When the boundary network element role is an access network element, this management domain is determined to be the access layer; when the boundary network element role is a metropolitan area aggregation network element or a metropolitan area interconnection network element, this management domain is determined to contain at least the access layer and the metropolitan area layer; when the boundary network element role is a core network element, this management domain is determined to contain the access layer, the metropolitan area layer, and the core layer; when the boundary network element role is missing, the default rule is adopted, and this management domain is determined to be the access layer.

[0046] Dual-end cross-domain scenario: When there are two cross-domain boundary network elements in this management domain, the roles of the source boundary network element and the destination boundary network element are obtained respectively, and a merging judgment is made based on the hierarchical range of the roles on both sides.

[0047] The specific rules are as follows: When both source and destination boundary network elements are core network elements, this management domain is designated as the core layer; when both source and destination boundary network elements are metropolitan area aggregation network elements or metropolitan area docking network elements, this management domain is designated as the metropolitan area layer; when the source and destination boundary network elements are metropolitan area aggregation network elements and metropolitan area docking network elements respectively, this management domain is designated as the metropolitan area layer; when the source and destination boundary network elements are metropolitan area aggregation network elements or metropolitan area docking network elements and core network elements respectively, this management domain is designated as having at least the metropolitan area layer and the core layer; when the source and destination boundary network element roles are missing, the default rule is adopted, and this management domain is designated as the core layer.

[0048] Taking a cross-domain sub-service at the destination as an example, this illustrates the method of analyzing network layers using boundary network elements. If the boundary network element interfacing with the next domain is an access network element, then this management domain corresponds to the access layer. If the boundary network element is a metropolitan area interfacing network element, then this management domain corresponds to the access layer and the metropolitan area layer. If the boundary network element is a core network element, then this management domain corresponds to the access layer, the metropolitan area layer, and the core layer. If the boundary network element is a metropolitan area aggregation network element, then this management domain corresponds to the access layer, the metropolitan area layer, the core layer, and the metropolitan area layer. If the boundary network element has no role, this management domain defaults to the access layer.

[0049] Furthermore, referring to Figure 4 , Figure 4 This is a typical network topology and layering diagram of cross-domain services according to an embodiment of this application. For example... Figure 4 As shown, in this network architecture, cross-domain services pass through multiple management domains sequentially from the source network element to the destination network element. Each management domain typically contains one or more network layers, including the access layer, metropolitan area layer, and core layer. Based on the distribution of the management domains where the source and destination network elements reside, cross-domain services are classified into three types: source-end cross-domain, destination-end cross-domain, and dual-end cross-domain.

[0050] Adjacent management domains are interconnected through Network Node Interfaces (NNIs), and network elements participating in cross-domain connections are defined as boundary network elements. Boundary network elements can be pre-configured into different network element roles, including access network elements, metropolitan area aggregation network elements, metropolitan area docking network elements, and core network elements, to support network hierarchy identification and policy matching.

[0051] exist Figure 4 In this context, network element A and network element Z serve as the source and destination of a service, respectively. The service originates from network element A, passes through management domain A, management domain B, and management domain C in sequence, and finally reaches network element Z.

[0052] Management domain A contains the service source, and the service path passes through the access layer and the metropolitan area layer in sequence, and is interconnected with management domain B through metropolitan area layer boundary network element D. Boundary network element D is connected to boundary network element E of management domain B through two pairs of NNI interfaces.

[0053] Management domain B is located in the middle of the service path and does not contain service sources or destinations, belonging to a two-end cross-domain scenario. This management domain receives services from management domain A through core layer boundary network element E and interconnects with management domain C through core layer boundary network element F. Boundary network element E and boundary network element F respectively achieve cross-domain connection through two pairs of NNI interfaces.

[0054] Management domain C contains service destinations, which receive services from management domain B through metropolitan area layer boundary network element G, and ultimately reach destination network element Z via the access layer. Boundary network element G is connected to boundary network element F of management domain B through two pairs of NNI interfaces.

[0055] exist Figure 4 In this context, the roles of boundary network elements are configured as follows: boundary network elements D and G are configured as metropolitan area connection network elements, and boundary network elements E and F are configured as core network elements.

[0056] During the service activation process, each management domain automatically completes network hierarchy identification and policy matching based on the sub-service type and boundary network element role: For management domain A, its sub-services include service sources but not service destinations, thus it is determined to be a cross-domain scenario at the destination end. Based on the role of boundary network element D as a metropolitan area interface network element, it is determined that this management domain includes both access layer and metropolitan area layer. The network management system extracts access layer and metropolitan area layer policies from the service layer policy fields issued by the coordinator and executes the corresponding policy configurations on network elements A, B, C, and D within this domain. For the cross-domain interface portion, its protection configuration is controlled by the inter-domain mode control parameters of the NNI issued by the coordinator.

[0057] For management domain B, its sub-services contain neither service sources nor service destinations, thus it is determined to be a cross-domain scenario. Since boundary network elements E and F are both core network elements, this management domain is identified as the core layer. The network management system extracts core layer policies from the service-level policy fields and executes policy configurations on network elements E and F. The cross-domain interface is also controlled by the NNI's inter-domain mode control parameters.

[0058] For management domain C, its sub-services include service destinations but not service sources, thus it is determined to be a cross-domain scenario at the source end. Based on the fact that boundary network element G is a metropolitan area interconnection network element, it is determined that this management domain includes both the metropolitan area layer and the access layer. The network management system extracts the corresponding layer policies and executes policy configurations on network elements G, H, I, and Z. The cross-domain interface portion is controlled by inter-domain mode control parameters.

[0059] Based on the above layered model, it can support a variety of different networking and application scenarios: There can be one or more management domains. When there is only one management domain, the business is regarded as a single-domain business. At this time, there is no need for cross-domain interfaces, but the business-level policy fields issued by the coordinator are still valid and used to guide the protection configuration of different levels within the domain.

[0060] Each management domain can contain one or more layers from the access layer, metropolitan area layer, and core layer. For example, in a certain scenario, management domain A contains network elements A and B, and management domain B contains network elements C, D, E, F, E1, F1, I, and Z. When boundary network element B is configured as an access network element and boundary network element C is configured as a metropolitan area aggregation network element, the management domain layer can be automatically identified based on the boundary network element roles.

[0061] When the network element role is not explicitly configured, the network management system can use default rules to deduce the hierarchical level of the management domain, or simplify the management domain into a single level among the access layer, metropolitan area layer, or core layer for processing.

[0062] Regarding cross-domain interface processing, the number of NNI interfaces between adjacent management domains must be consistent, and can be either single-interface interconnection or multi-interface interconnection. The number of boundary network elements can be one or more.

[0063] When the cross-domain connection is a single pair of NNI interfaces, for example, the first NNI interface of boundary network element D is connected to the first NNI interface of boundary network element E. If the inter-domain mode control parameter is set to subnet connection protection, but the protection group establishment conditions are not met, the inter-domain mode control parameter will automatically degenerate to no protection mode.

[0064] When a cross-domain connection consists of multiple pairs of NNI interfaces located in different network elements, such as the connection between management domain B and management domain C, where the first NNI interface of boundary network element G is connected to the first NNI interface of boundary network element F, and the second NNI interface of boundary network element G is connected to the NNI interface of another network element F1, the two NNI interfaces are not located in the same network element. The network management system automatically determines that the cross-domain segment is a pass-through scenario and converts the inter-domain mode control parameters of the corresponding NNI to pass-through mode processing.

[0065] The above methods enable complex networking environments with multiple management domains, multiple levels, and multiple NNIs: The NNI-based inter-domain mode control parameters provide unified control over cross-domain protection configuration; the NNI-based service-level policy fields provide flexible control over intra-domain protection policies; the NNI-based network element roles enable automatic network level identification and policy matching; and the NNI-based distribution relationships enable automatic identification of protection degradation and through-pass scenarios.

[0066] This enables automated configuration and adaptive optimization of cross-domain service protection, improving service activation success rate and network resource utilization efficiency.

[0067] Step S40: Based on the identification results and the control parameters, determine the protection configuration for each link segment and cross-domain interface location within this management domain; In some specific embodiments, step S40 includes: Based on the identification result, the corresponding business layer policy content is matched from the business layer policy field of the control parameter; Based on the business-level policy content, protection derivation is performed to determine the protection configuration of each link segment within the domain. The protection configuration includes protection type, primary / backup path relationship, and protection group establishment location. Based on the inter-domain mode control parameters of the primary / backup path cross-domain interface control parameters, the protection configuration at the cross-domain interface is determined.

[0068] In this embodiment, after completing the layer identification, based on the identification result—that is, the identified set of layers included in this management domain, which includes one or more layers from the access layer, metropolitan area layer, and core layer—the service layer parameters sent by the coordinator to the controller contain policies for each layer. The policies for each layer included in this management domain are extracted from the service layer parameters sent by the controller to the network management system. For example, if this management domain corresponds to the access layer and the metropolitan area layer, the access layer policy and the metropolitan area layer policy are obtained from the service layer parameters.

[0069] After policy matching is completed, the network management system performs protection derivation based on the service-level policy content to determine the protection configuration of each link segment within the domain, including protection type, primary / backup path relationship, and protection group establishment location. Protection groups are established for network elements that meet the protection conditions; no protection groups are established for network elements that only perform forwarding functions or are identified as pass-through. The protection derivation mainly adopts the path calculation and protection calculation mechanisms of the existing transport network management system, generating corresponding primary paths, backup paths, and protection configurations according to different policy constraints. Specifically, when the policy requires SNCP protection, the network management system performs SNCP protection path calculation; when the policy requires MSP protection, the network management system performs MSP protection calculation; when the policy requires no protection, only service paths are generated. When this management domain contains multiple network layers, each layer applies the corresponding layer's policy for calculation, and the interconnection part uses the policy of the higher-level adjacent layer for calculation. Each layer calculates paths according to the specified policy, supporting intra-layer convergence path calculation. When path calculation fails, the layer is downgraded to no protection.

[0070] For cross-domain interface locations, the network management system determines the protection configuration of the cross-domain segment based on the inter-domain mode control parameters of the cross-domain interface. When the inter-domain mode control parameters indicate protection mode, a consistent primary / backup relationship is established on both sides of the cross-domain interface. When the inter-domain mode control parameters indicate pass-through mode, only a service transparent connection is established without establishing a protection group.

[0071] If there are no network elements in a certain management domain that can distinguish between primary and backup paths or bearer protection groups, it is determined that the management domain does not have protection bearing capabilities. Therefore, no protection group will be established in the management domain, and the service will be downgraded to no protection in the management domain.

[0072] When two NNI interfaces of one management domain and another management domain are not on the same network element, the inter-domain mode control parameters of these two NNI interfaces are automatically identified as pass-through. The protection group establishment location is adjusted to the boundary network element of the adjacent management domain. If there are also two boundary network elements of the adjacent management domain, the protection group establishment location is further adjusted to the network element that supports the creation of protection groups.

[0073] The inter-domain mode control parameters are uniformly defined as four types of standard values: no protection, SNCP, MSP, and pass-through. All cross-domain NNI interfaces adopt the same set of parameter semantic definitions. The coordinator only needs to uniformly issue the inter-domain mode control parameters to determine the protection configuration of each cross-domain segment. There is no need for complex private collaboration and negotiation between each management domain, which directly achieves the consistency of cross-domain protection strategies and eliminates the need for complex multi-domain collaborative calculations.

[0074] This embodiment can automatically identify whether a management domain has the capacity to carry primary and backup paths and protection groups. For domains without carrying capacity, the protection group is adaptively moved to the boundary network element of the adjacent management domain to take over, ensuring uninterrupted end-to-end protection. At the same time, the overall design adopts a modular approach with standardized parameters, expandable roles, and configurable policies. It can be compatible with new protection types and network configurations without changing the overall process, and has good scalability and feasibility for on-site engineering.

[0075] Step S50: Convert the protection configuration into an end-to-end service auto-enabling instruction that the device can recognize, and send it to each network element so that each network element can execute the end-to-end service auto-enabling instruction.

[0076] In this embodiment, each management domain network management system converts the configuration into instructions that the device can recognize and sends them to each network element to complete resource allocation, cross-connection establishment and protection group configuration, thereby realizing the automatic activation of end-to-end services.

[0077] The above technical solution enables unified control of cross-domain protection configuration using NNI inter-domain mode control parameters, flexible control of protection policies within each management domain using service-level policy fields, and automatic policy implementation through network element roles. It supports segmented protection, asymmetric protection, and pass-through scenarios in complex multi-management domain networking environments, significantly improving the success rate and reliability of automatic service activation.

[0078] In this embodiment, multiple management domain sub-paths and control parameters are obtained through a coordinator; the network layer of the management domain is identified based on the multiple management domain sub-paths and the control parameters to obtain the identification result; based on the identification result and the control parameters, the protection configuration of each link segment and cross-domain interface location within the management domain is determined; the protection configuration is converted into an end-to-end service auto-enabling instruction that can be recognized by the device and sent to each network element so that each network element can execute the end-to-end service auto-enabling instruction.

[0079] This embodiment utilizes a separation mechanism where cross-domain protection is controlled by inter-domain mode control parameters and intra-domain protection is controlled by business layer policy fields. This architecturally separates cross-domain protection from intra-domain protection, achieving decoupled control between intra-domain and cross-domain protection, making the system structure clearer and the division of responsibilities more explicit. The inter-domain mode control parameters are uniformly defined as four categories of standard values: no protection, SNCP, MSP, and pass-through. All cross-domain NNI interfaces adopt the same set of parameter semantic definitions. The coordinator only needs to uniformly issue the inter-domain mode control parameters to determine the protection configuration of each cross-domain segment. There is no need for complex private collaboration and negotiation between each management domain, which directly achieves the consistency of cross-domain protection strategies and eliminates the need for complex multi-domain collaborative calculations. It supports a single business request carrying multiple independent policy sub-fields of management domains. Each management domain only needs to execute the protection logic locally according to its own policy sub-fields. Domains that have not been issued policies directly reuse the system's default policies. There is no need to rely on the global topology of the entire network for unified centralized calculation. Each domain can complete the protection decision independently, which reduces the overall complexity of the system. During the business decomposition process, the system automatically identifies source-end cross-domain network elements, destination-end cross-domain network elements, cascade network elements, and through-network elements, and sets differentiated processing rules for different roles (cascade network elements are independently configured with protection based on their respective NNI inter-domain mode control parameters, while through-network elements only transmit information without establishing protection groups). This design of finely distinguishing protection logic according to network element roles can flexibly adapt to various complex business scenarios such as segmented protection, asymmetric protection, and hybrid protection under multi-domain networking, and can meet diverse business needs. The complex protection logic is abstracted into fixed inter-domain mode control parameters and structured business layer policy fields, eliminating the need for the northbound interface to transmit a large number of fragmented private configuration parameters. The parameter semantics are unified and the combination rules are clear, reducing parameter coupling and adaptation ambiguity, reducing the configuration complexity of the northbound interface, and improving the success rate of automatic service activation from the root. It can automatically identify whether the management domain has the capacity to carry primary and backup paths and protection groups. For domains without the capacity, the protection group will be adaptively moved to the boundary network element of the adjacent management domain to take over, ensuring uninterrupted end-to-end protection. At the same time, the whole adopts a modular design with standardized parameters, expandable roles, and configurable policies. It can be compatible with new protection types and network configurations without changing the overall process, and has good scalability and field engineering feasibility.

[0080] This embodiment solves the technical problems of low success rate and low reliability of automatic service activation in the prior art.

[0081] Furthermore, this application will be explained by taking the example of a business request to open an OTN leased line service from network element A to network element Z, with a service level requirement of high reliability.

[0082] Example 1: A transport network is constructed comprising three management domains (Management Domain A, Management Domain B, and Management Domain C). The network topology consists of network elements A through Z forming a complete service path. A through B constitutes the access layer, C through D the metropolitan area layer, E through F the core layer, G through H the metropolitan area layer, and I through Z the access layer. Management Domain A includes network elements A, B, C, and D; Management Domain B includes network elements E and F; and Management Domain C includes network elements G, H, I, and Z. Management Domain A and Management Domain B are interconnected through two pairs of network node interfaces, as are Management Domain B and Management Domain C. Network elements B and I act as access network elements, network elements C and H act as metropolitan area aggregation elements, network elements D and G act as metropolitan area interconnection elements, and network elements E and F act as core network elements.

[0083] After receiving the service request, the coordinator calculates the end-to-end path as A→…→D→E→…→F→G→…→Z based on the network topology, and identifies two pairs of cross-domain interfaces between the first management domain A and the second management domain B, as well as two pairs of cross-domain interfaces between the second management domain B and the third management domain C.

[0084] The coordinator performs semantic parsing of service level constraints and transforms them into control parameters. The inter-domain mode control parameters for cross-domain interfaces are uniformly set to SNCP subnet connection protection. At the same time, it generates service-level policy fields, where access layer policies enable protection and prioritize SNCP subnet connection protection, metropolitan area layer policies enable protection and prioritize SNCP subnet connection protection, and core layer policies enable protection and prioritize SNCP subnet connection protection.

[0085] The coordinator splits the above parameters according to management domain and distributes them to the controllers of each management domain. The controllers then pass the parameters through to their respective network management systems.

[0086] In the first management domain A, the network management system identifies that this domain includes both the access layer and the metropolitan area layer based on the role of boundary network element D as a metropolitan area interface network element. It calculates that the primary and backup logical channels from A to D all traverse the path A→B→C→D. According to the service layer policy, network element B's role is access; an access layer protection group is established in the A-B segment, an access layer protection group is established in the B-C segment, and a metropolitan area layer protection group is established in the C-D segment. Since there are two pairs of cross-domain interfaces between the first management domain A and the second management domain B, located on the same network element, the network management system establishes a cross-domain protection group on the D side based on the inter-domain mode control parameters SNCP subnet connection protection issued by the two NNIs.

[0087] In the second management domain B, network elements E and F are core network elements, and the network management system identifies this domain as the core layer. It is calculated that the primary and backup logical channels from E to F both pass through the path E→F. Based on the service hierarchy policy, and since both sides interface with the adjacent management domain through two pairs of NNIs respectively, and the cross-domain interfaces are located on the same network element, and their inter-domain mode control parameters are protected by SNCP, a protection group is established in the E to F segment.

[0088] In the third management domain C, the network management system identifies the metropolitan area layer and access layer as the role of the boundary network element G as a metropolitan area interconnection network element. It calculates that the primary and backup logical channels from G to Z all pass through the path G→H→I→Z. Based on the service layer policy, a metropolitan area layer protection group is established in the G to H segment. Since network element I plays the role of access, an access layer protection group is established in the H to I segment, and an access layer protection group is established in the I to Z segment. Because there are two pairs of cross-domain interfaces between the first management domain C and the second management domain B, located on the same network element, the network management system establishes a cross-domain protection group on the G side based on the inter-domain mode control parameters SNCP subnet connection protection of the two issued NNIs.

[0089] Ultimately, protection groups are established in the access layer and metropolitan area layer of the first management domain A, the core layer of the second management domain B, and the metropolitan area layer and access layer of the third management domain C, thereby forming an end-to-end segmented protection service with protection capabilities across all domains.

[0090] This embodiment verifies that in scenarios where protection conditions are met across multiple management domains, multiple levels, and multiple pairs of cross-domain interfaces, unified and coordinated configuration of cross-domain protection and intra-domain protection can be achieved through the coordinated control of inter-domain mode control parameters and business-level policy fields, combined with the automatic inference mechanism of network element roles, thus completing end-to-end full-path protection coverage.

[0091] As a variant implementation, in another embodiment, no network element role information is configured for each network element.

[0092] In this implementation: The network management system of the first management domain A adopts the pre-set path layering rules of this domain to perform layer division on the path A→B→C→D, and generates the corresponding protection configuration based on the division result; or, the domain is uniformly regarded as the same network layer, and a unified layer strategy is used to generate protection configuration for the path A→B→C→D.

[0093] In the second management domain B, the network management system establishes protection relationships in segments E to F based on the core layer policy.

[0094] In the third management domain C, the network management system uses the pre-set path layering rules of this domain to perform layer division on the path G→H→I→Z, and generates the corresponding protection configuration based on the division result; or, this domain is uniformly regarded as the same network layer, and a unified layer strategy is used to generate protection configuration for the path G→H→I→Z.

[0095] The cross-domain interface configuration and inter-domain mode control parameters between management domains remain unchanged, and the method of establishing cross-domain protection relationships is the same as in Embodiment 1 above.

[0096] This variant implementation demonstrates that even without configuring network element role information, the present invention can still complete hierarchical identification and protection derivation based on pre-set rules within the management domain, thus possessing good compatibility and engineering adaptability.

[0097] Example 2: In this embodiment, a transport network with three management domains is constructed. The network topology consists of network elements A to Z forming a complete service path. A to B constitute the access layer, C, D, and D1 constitute the metropolitan area layer, E, F, E1, and F1 constitute the core layer, G, G1, and H constitute the metropolitan area layer, and I to Z constitute the access layer. The first management domain A includes network elements A, B, C, D, and D1; the second management domain B includes network elements E, F, E1, and F1; and the third management domain C includes network elements G, G1, H, I, and Z.

[0098] Unlike Embodiment 1, the two pairs of cross-domain interfaces between the first management domain A and the second management domain B are located on different network elements D and D1, respectively, and the two pairs of cross-domain interfaces between the second management domain B and the third management domain C are located on different network elements G and G1, respectively. Therefore, the conditions for establishing a protection group for SNCP subnet connection protection on a single boundary network element are not met.

[0099] After receiving a service request, the coordinator calculates the end-to-end primary path as A→…→D→E→…→F→G→…→Z and the backup path as A→…→D1→E1→…→F1→G1→…→Z. It then sets the inter-domain mode control parameters of the cross-domain interface to SNCP subnet connection protection and generates service layer policy fields, where SNCP protection is enabled for the access layer, metropolitan area layer, and core layer.

[0100] The coordinator splits the above parameters by management domain and distributes them to the controllers of each management domain.

[0101] In the first management domain A, the network management system identifies that this domain includes the access layer and the metropolitan area layer, and calculates two intra-domain paths based on the primary and backup paths: A→B→C→D and A→B→C→D1. Access layer protection groups are established in the A to B segment and the B to C segment, and metropolitan area layer protection groups are established in the C to D / D1 branch segment. Since the cross-domain interfaces are located on different boundary network elements D and D1, the condition for establishing an SNCP protection group at a single node is not met; therefore, no cross-domain protection group is established at the boundary. Furthermore, based on the topology of the primary and backup paths within this domain, the network management system determines the nearest common node of the primary and backup paths as network element C, and completes the closure of the protection group at this node.

[0102] In the second management domain B, the network management system identifies this domain as the core layer and calculates the two intra-domain paths, E→F and E1→F1, as primary and backup paths, respectively. Although the core layer is protected in the service-level policy, the cross-domain interfaces on both sides of this domain do not meet the conditions for establishing an SNCP protection group, and there is no common convergence node for the primary and backup paths within this domain. Therefore, this management domain does not have the topology conditions to independently establish a protection group, and only the primary and backup paths are transparently transmitted without establishing a protection group.

[0103] In the third management domain C, the network management system identifies that this domain includes both the metropolitan area layer and the access layer, and calculates the two intra-domain paths for primary and backup protection as G→H→I→Z and G1→H→I→Z, respectively. Since the cross-domain interfaces are located on different network elements G and G1, the conditions for establishing an SNCP protection group at the boundary are not met; therefore, no cross-domain protection group is established at the boundary. Based on the topology of the primary and backup paths within this domain, the network management system determines that the primary and backup paths converge at network element H. Therefore, a metropolitan area layer protection group is established in the segment from G / G1 to H, and access layer protection groups are established in the segments from H to I and from I to Z.

[0104] Ultimately, protection groups are established within the first and third management domains through path convergence nodes, while the second management domain, as a through domain, does not carry protection groups, thus forming an end-to-end protection structure of "protection at the edge + through domain in the middle".

[0105] This embodiment verifies that when the cross-domain interface does not meet the conditions for SNCP establishment, the protection group can achieve adaptive closure within the domain and automatically degrade to cross-domain pass-through mode by means of coordinated control of inter-domain mode control parameters and business-level policies, combined with the automatic identification mechanism of primary and backup path convergence nodes.

[0106] As a variant implementation, in another embodiment, the two pairs of cross-domain interfaces between the second management domain B and the third management domain C are located on the same boundary network element, but by explicitly configuring the inter-domain mode control parameters of the corresponding NNI interface to pass-through mode, the establishment of SNCP protection groups at this boundary is prohibited.

[0107] In this case, the third management domain C still establishes a protection group at network element H according to the convergence relationship of the primary and backup paths. The remaining processing is the same as in the above embodiment, and the end-to-end service effect of "edge protection + intermediate pass-through" can still be achieved.

[0108] This variant implementation shows that the present invention is applicable not only to scenarios where the physical topology does not meet the protection conditions, but also to scenarios where cross-domain protection capabilities are actively disabled through policy control, further enhancing the flexibility and controllability of the solution.

[0109] Example 3: In this embodiment, a transport network with three management domains is constructed. The network topology consists of network elements A to Z forming a complete service path. A to B constitute the access layer, C, D, and D1 constitute the metropolitan area layer, E, F, E1, and F1 constitute the core layer, G and H constitute the metropolitan area layer, and I to Z constitute the access layer. The first management domain A includes network elements A, B, C, D, and D1; the second management domain B includes network elements E, F, E1, and F1; and the third management domain C includes network elements G, H, I, and Z.

[0110] Unlike Embodiment 2, the two pairs of cross-domain interfaces between the first management domain A and the second management domain B are located on different network elements D and D1, respectively, thus failing to meet the condition for SNCP subnet connection protection to establish a protection group on a single boundary network element; while the two pairs of cross-domain interfaces between the second management domain B and the third management domain C are located on the same boundary network element F, thus meeting the condition for SNCP subnet connection protection to establish a protection group on a single boundary network element.

[0111] After receiving a service request, the coordinator calculates the end-to-end primary path as A→…→D→E→…→F→G→…→Z and the backup path as A→…→D1→E1→…→F→G→…→Z. It sets the cross-domain interface inter-domain mode control parameter between the first management domain A and the second management domain B to pass-through mode, and sets the cross-domain interface inter-domain mode control parameter between the second management domain B and the third management domain C to SNCP subnet connection protection. At the same time, it generates a service layer policy field, in which SNCP protection is enabled in the access layer, metropolitan area layer and core layer.

[0112] The coordinator splits the above parameters by management domain and distributes them to the controllers of each management domain.

[0113] In the first management domain A, the network management system identifies that this domain includes the access layer and the metropolitan area layer, and calculates the two intra-domain paths A→B→C→D and A→B→C→D1 based on the primary and backup paths. Access layer protection groups are established in the A to B segment and the B to C segment, and metropolitan area layer protection groups are established in the C to D / D1 branch segment. Since the cross-domain interfaces are located on different boundary network elements D and D1, and the inter-domain mode control parameter is pass-through mode, no cross-domain protection groups are established at the boundaries. Furthermore, based on the topology relationship of the primary and backup paths within this domain, the network management system determines the nearest common node of the primary and backup paths as network element C, and completes the closure of the protection group at this node.

[0114] In the second management domain B, the network management system identifies this domain as the core layer and calculates the two intra-domain paths based on the primary and backup paths: E→F and E1→F1→F. Since the cross-domain interface between this domain and the first management domain A is in pass-through mode, no cross-domain protection group is established on this side. However, the two pairs of cross-domain interfaces between this domain and the third management domain C are located on the same boundary network element F, and the inter-domain mode control parameter is SNCP subnet connection protection, satisfying the condition for establishing a protection group at a single node. Therefore, a cross-domain protection group is established at network element F. Simultaneously, according to the service layer strategy, a core layer protection group is established in the E / E1 to F segment, thus forming a protection structure within this domain with network element F as the endpoint.

[0115] In the third management domain C, the network management system identifies that this domain contains both the metropolitan area layer and the access layer, and calculates the two intra-domain paths, G→H→I→Z, as primary and backup. Since the two pairs of cross-domain interfaces between this domain and the second management domain B are located on the same boundary network element G, and the inter-domain mode control parameter is SNCP subnet connection protection, a cross-domain protection group is established at network element G. Based on this, a metropolitan area layer protection group is established in the G to H segment, and access layer protection groups are established in the H to I segment and the I to Z segment.

[0116] Finally, a protection group is established within the first management domain through path convergence nodes. A through-pass mode is adopted between the first and second management domains. A cross-domain protection group is established on the side of the second management domain closer to the third management domain. SNCP segmented protection is formed between the second and third management domains. At the same time, a cross-domain protection group is established at the boundary of the third management domain, thus forming an end-to-end protection structure of "front-end through-pass + rear-end SNCP segmented + middle single-end protection".

[0117] This embodiment verifies that, under inconsistent cross-domain interface conditions, by configuring inter-domain mode control parameters for different cross-domain segments separately, a combined control can be achieved to enable some cross-domain segments to pass through while others establish SNCP protection. At the same time, by establishing a protection group in the management domain that meets the conditions, the protection capability can be implemented on one side of the cross-domain boundary, thereby improving the flexibility and controllability of cross-domain configuration while ensuring service reliability.

[0118] As a variant implementation, in another embodiment, although the conditions for establishing a protection group between the second management domain B and the third management domain C are met, the mode control parameters between these domains are configured to pass-through mode through a strategy, so that the second management domain does not establish a protection group, and only the third management domain establishes an SNCP protection group at the boundary.

[0119] In this case, the third management domain C establishes a cross-domain protection group at network element G, and the remaining processing procedures are the same as in the above embodiment, which can still achieve end-to-end service protection coverage.

[0120] This variant implementation demonstrates that the present invention supports fine-grained control over the location of cross-domain protection establishment, enabling not only automatic decision-making based on topology conditions but also manual intervention through strategy parameters, thereby further enhancing the flexibility and engineering adaptability of the solution.

[0121] Example 4: In this embodiment, a transport network with three management domains is constructed. The network topology consists of network elements A to Z forming a complete service path. A to B constitute the access layer, C to D the metropolitan area layer, E to F the core layer, G to H the metropolitan area layer, and I to Z the access layer. The first management domain A includes network elements A, B, C, and D; the second management domain B includes network elements E and F; and the third management domain C includes network elements G, H, I, and Z. The first management domain A and the second management domain B are interconnected through two pairs of network node interfaces, and the second management domain B and the third management domain C are interconnected through two pairs of network node interfaces. Network elements B and I act as access network elements, network elements C and H act as metropolitan area aggregation elements, network elements D and G act as metropolitan area interconnection elements, and network elements E and F act as core network elements.

[0122] After receiving the service request, the coordinator calculates the end-to-end path as A→…→D→E→…→F→G→…→Z based on the network topology, and identifies two pairs of cross-domain interfaces between the first management domain A and the second management domain B, as well as two pairs of cross-domain interfaces between the second management domain B and the third management domain C.

[0123] The coordinator performs semantic parsing on the service level constraints and transforms them into control parameters. The inter-domain mode control parameters for the first cross-domain segment are set to SNCP subnet connection protection, and the inter-domain mode control parameters for the second cross-domain segment are set to MSP protection. At the same time, it generates service-level policy fields, in which the access layer policy enables MSP protection, the metropolitan area layer policy enables SNCP protection, and the core layer policy enables SNCP protection.

[0124] The coordinator splits the above parameters according to management domain and distributes them to the controllers of each management domain. The controllers then pass the parameters through to their respective network management systems.

[0125] In the first management domain A, the network management system identifies that this domain includes both the access layer and the metropolitan area layer, and calculates that the two intra-domain paths, primary and backup paths, are both A→B→C→D. According to the service layer policy, an access layer MSP protection group is established in the A to B segment, an access layer MSP protection group is established in the B to C segment, and a metropolitan area layer SNCP protection group is established in the C to D segment. Since the two pairs of cross-domain interfaces between the first management domain A and the second management domain B are located on the same network element D, and the inter-domain mode control parameter is SNCP subnet connection protection, a cross-domain SNCP protection group is established on the D side.

[0126] In the second management domain B, the network management system identifies this domain as the core layer and calculates the intra-domain path as E→F. Based on the service layer policy, a core layer SNCP protection group is established in the E to F segment. Simultaneously, since the cross-domain interface with the first management domain A is in SNCP mode, the network management system establishes a cross-domain SNCP protection group on the interface side with A; while the cross-domain interface with the third management domain C uses MSP protection for inter-domain mode control parameters, therefore a cross-domain MSP protection group is established at the boundary where it interfaces with C.

[0127] In the third management domain C, the network management system identifies that this domain includes both the metropolitan area layer and the access layer, and calculates the intra-domain path as G→H→I→Z. Based on the service layer policy, a metropolitan area layer SNCP protection group is established in the G to H segment, and an access layer MSP protection group is established in the H to I segment and the I to Z segment. Since the inter-domain mode control parameter of the cross-domain interface with the second management domain B is MSP protection, the network management system establishes a cross-domain MSP protection group on the G side, thus completing the combined implementation of cross-domain and intra-domain protection.

[0128] Ultimately, protection groups are established for the access layer MSP and metropolitan area layer SNCP in the first management domain A, the core layer SNCP in the second management domain B, and the metropolitan area layer SNCP and access layer MSP in the third management domain C. SNCP protection is provided between management domains A and B, and MSP protection is provided between management domains B and C, thus forming an end-to-end service with cross-domain SNCP+MSP combination and differentiated protection at each level within the domain.

[0129] This embodiment verifies that in multi-management-domain and multi-level scenarios, by coordinating the control of cross-domain interface inter-domain mode control parameters and business-level policy fields, different protection modes can be adopted for different cross-domain segments. At the same time, each layer selects MSP or SNCP protection according to the policy, thereby forming a combination of end-to-end cross-domain protection and intra-domain differentiated protection for services, meeting the reliability and flexibility requirements of complex business scenarios.

[0130] All the above embodiments introduce inter-domain mode control parameters at the cross-domain interface and combine them with network element roles for automatic derivation, thereby achieving decoupled control between cross-domain protection and intra-domain protection. This allows for the automatic activation of multi-management domain services without requiring users to configure each segment, demonstrating good feasibility and engineering applicability.

[0131] Based on the same inventive concept, embodiments of this application also provide a device for automatically activating transmission network services.

[0132] In one embodiment, reference is made to Figure 5 , Figure 5 This is a functional module diagram of an embodiment of the automatic service activation device for the transmission network of this application. Figure 5 As shown, the automatic service activation device for the transmission network includes: Information acquisition module 10 is configured to acquire multiple management domain sub-paths and control parameters through the coordinator; The network hierarchy identification module 20 is configured to identify the network hierarchy of the current management domain based on multiple management domain sub-paths and the control parameters, and obtain the identification result; The protection configuration derivation module 30 is configured to determine the protection configuration of each link segment and cross-domain interface location within the management domain based on the identification results and the control parameters. The service activation instruction generation module 40 is configured to convert the protection configuration into an end-to-end service automatic activation instruction that can be recognized by the device, and send it to each network element so that each network element can execute the end-to-end service automatic activation instruction.

[0133] Optionally, in one embodiment, the information acquisition module 10 is configured to: Based on the network topology resource information, the coordinator, upon receiving a service request, performs path calculation to obtain an end-to-end basic service path that meets the service level constraint parameters. The service request includes the source user interface or network element, the destination user interface or network element, the service type, the service bandwidth constraint, and the service level constraint parameters. Identify the multiple management domain boundaries involved in the basic business path, divide them according to the management domain, decompose the end-to-end path into multiple management domain sub-paths and send them to the local domain network management system.

[0134] Optionally, in one embodiment, the information acquisition module 10 is configured to: The coordinator performs semantic parsing on business requests, transforms business service level constraint parameters into executable control parameters, and sends them to the local network management system.

[0135] Optionally, in one embodiment, the control parameters include inter-domain mode control parameters of the primary / backup path cross-domain interface control parameters and business-level policy fields of the intra-domain control parameters of each management domain. Among them, the inter-domain mode control parameters of the primary and backup path cross-domain interface control parameters are used to determine the protection configuration at the cross-domain interface; The service-level policy field is used to describe the protection configuration and default processing rules of the internal paths of each management domain, and is organized according to the network layer. The service-level policy includes access layer policy, metropolitan area layer policy and core layer policy.

[0136] Optionally, in one embodiment, the network layer identification module 20 is configured to: The default processing rules for paths within the management domain are determined based on the control parameters. Based on the boundary network element roles in multiple management domain sub-paths, the network layer of this management domain is identified according to the mapping relationship between network element roles and network layers, the default processing rules, and the combination rules, and the identification results are obtained.

[0137] Optionally, in one embodiment, the combination rule is as follows: When there is only one cross-domain boundary network element in this management domain, the network hierarchy of this management domain is identified based on the role of that boundary network element. When there are two cross-domain boundary network elements in this management domain, the roles of the source-side boundary network element and the destination-side boundary network element are obtained respectively, and the network level of this management domain is jointly identified based on the roles of the boundary network elements on both sides.

[0138] Optionally, in one embodiment, the protection configuration derivation module 30 is configured to: Based on the identification result, the corresponding business layer policy content is matched from the business layer policy field of the control parameter; Based on the business-level policy content, protection derivation is performed to determine the protection configuration of each link segment within the domain. The protection configuration includes protection type, primary / backup path relationship, and protection group establishment location. Based on the inter-domain mode control parameters of the primary / backup path cross-domain interface control parameters, the protection configuration at the cross-domain interface is determined.

[0139] The functions of each module in the above-mentioned automatic activation device for transmission network services correspond to the steps in the above-mentioned automatic activation method embodiment for transmission network services, and their functions and implementation processes will not be described in detail here.

[0140] Based on the same inventive concept, embodiments of this application also provide an electronic device, the structure of which is as follows: Figure 6 As shown, it includes: a memory and a processor, wherein the processor is used to read and execute the computer program stored in the memory to implement the aforementioned method for automatically activating transmission network services.

[0141] Based on the same inventive concept, this application also provides a computer storage medium storing computer-executable instructions, which, when executed, implement the aforementioned method for automatically activating transmission network services.

[0142] Finally, it should be noted that while some processes described in the embodiments of this application include multiple operations or steps that appear in a specific order, it should be understood that these operations or steps may not be executed in the order they appear in the embodiments of this application, or may be executed in parallel. The sequence number of the operation is only used to distinguish different operations, and the sequence number itself does not represent any execution order. In addition, these processes may include more or fewer operations, and these operations or steps may be executed sequentially or in parallel, and these operations or steps may be combined.

[0143] Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application.

Claims

1. A method for automatically activating transmission network services, characterized in that, The method includes: Obtain multiple management domain sub-paths and control parameters through the coordinator; The network layer of this management domain is identified based on multiple management domain sub-paths and the control parameters, and the identification result is obtained. Based on the identification results and the control parameters, the protection configuration of each link segment and cross-domain interface location within this management domain is determined; The protection configuration is converted into an end-to-end service auto-enabling instruction that can be recognized by the device, and then sent to each network element so that each network element can execute the end-to-end service auto-enabling instruction.

2. The method for automatically activating transmission network services according to claim 1, characterized in that, Retrieve multiple management domain sub-paths, including: Based on the network topology resource information, the coordinator, upon receiving a service request, performs path calculation to obtain an end-to-end basic service path that meets the service level constraint parameters. The service request includes the source user interface or network element, the destination user interface or network element, the service type, the service bandwidth constraint, and the service level constraint parameters. Identify the multiple management domain boundaries involved in the basic business path, divide them according to the management domain, decompose the end-to-end path into multiple management domain sub-paths and send them to the local domain network management system.

3. The method for automatically activating transmission network services according to claim 1, characterized in that, Obtain control parameters, including: The coordinator performs semantic parsing on business requests, transforms business service level constraint parameters into executable control parameters, and sends them to the local network management system.

4. The method for automatically activating transmission network services according to claim 1, characterized in that, The control parameters include the mode field of the primary / backup path cross-domain interface control parameters and the business-level policy field of the control parameters within each management domain. Among them, the inter-domain mode control parameters of the primary and backup path cross-domain interface control parameters are used to determine the protection configuration at the cross-domain interface; The service-level policy field is used to describe the protection configuration and default processing rules of the internal paths of each management domain, and is organized according to the network layer. The service-level policy includes access layer policy, metropolitan area layer policy and core layer policy.

5. The method for automatically activating transmission network services according to claim 1 or 4, characterized in that, The identification of the network layer of this management domain based on multiple management domain sub-paths and the control parameters yields the following identification results: The default processing rules for paths within the management domain are determined based on the control parameters. Based on the boundary network element roles in multiple management domain sub-paths, the network layer of this management domain is identified according to the mapping relationship between network element roles and network layers, the default processing rules, and the combination rules, and the identification results are obtained.

6. The method for automatically activating transmission network services according to claim 5, characterized in that, The combination rules are as follows: When there is only one cross-domain boundary network element in this management domain, the network hierarchy of this management domain is identified based on the role of that boundary network element. When there are two cross-domain boundary network elements in this management domain, the roles of the source-side boundary network element and the destination-side boundary network element are obtained respectively, and the network level of this management domain is jointly identified based on the roles of the boundary network elements on both sides.

7. The method for automatically activating transmission network services according to claim 1 or 4, characterized in that, The step of determining the protection configuration for each link segment and cross-domain interface location within this management domain based on the identification results and the control parameters includes: Based on the identification result, the corresponding business layer policy content is matched from the business layer policy field of the control parameter; Based on the business-level policy content, protection derivation is performed to determine the protection configuration of each link segment within the domain. The protection configuration includes protection type, primary / backup path relationship, and protection group establishment location. Based on the inter-domain mode control parameters of the primary / backup path cross-domain interface control parameters, the protection configuration at the cross-domain interface is determined.

8. A device for automatically activating transmission network services, characterized in that, The device includes: The information acquisition module is configured to acquire multiple management domain sub-paths and control parameters through the coordinator; The network hierarchy identification module is configured to identify the network hierarchy of the current management domain based on multiple management domain sub-paths and the control parameters, and obtain the identification result; The protection configuration derivation module is configured to determine the protection configuration of each link segment and cross-domain interface location within this management domain based on the identification results and the control parameters. The service activation instruction generation module is configured to convert the protection configuration into an end-to-end service automatic activation instruction that can be recognized by the device, and send it to each network element so that each network element can execute the end-to-end service automatic activation instruction.

9. An electronic device, characterized in that, include: Memory, processor; The processor is configured to read and execute the computer program stored in the memory to implement the steps of the automatic activation method for transmission network services as described in any one of claims 1-7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed, implement the steps of the automatic activation method for transmission network services as described in any one of claims 1-7.

Images