A method and device for batch creation of small-granularity services in a transmission network

Abstract

The present invention relates to the field of telecommunication network management, and in particular to a method and device for batch creation of small-granularity services in a transmission network. The method mainly comprises: calculating the number of large-granularity service layers required for each layer according to the number of small-granularity services, selecting the large-granularity service with the least number of routing times to create the small-granularity service; creating the corresponding large-granularity service according to the routing information of the large-granularity service, and creating all the service layers required for the small-granularity service in sequence from the bottom layer to the upper layer; creating the required customer layer service on each layer of the service layer service created, and allocating the number of time slots for the customer layer service on the logical port of the service layer in the required order, and creating all the customer layer services. The customer layer of each service layer is created in a nested loop until the customer layer service is the small-granularity service type that is ultimately required. The present invention can reduce the time consumption of batch creation and routing of small-granularity services.

Description

Technical Field

[0001] The present invention relates to the field of telecommunication network management, and in particular to a method and device for batch creation of small-granularity services in a transmission network. Background Art

[0002] In existing telecommunications network management systems, batch creation of services, whether for end-to-end or single-station services, is performed in a loop, with path creation performed one service at a time. Using direct path creation for batch service creation requires port path finding and port sub-timeslot determination for each service, significantly increasing the time required for batch service creation. This approach can lead to issues such as excessive batch creation time, repeated port path finding and determination, and repeated time slot detection.

[0003] In view of this, how to overcome the defects of the existing technology and solve the problem of high resource consumption in the current small-granularity service creation method is a problem to be solved in this technical field. Summary of the Invention

[0004] In view of the above defects or improvement needs of the prior art, the present invention solves the problems of excessively long creation time, repeated port routing and judgment, and repeated time slot detection during the current batch creation of services.

[0005] The embodiment of the present invention adopts the following technical solutions:

[0006] In its first aspect, the present invention provides a method for batch creation of small-granularity services in a transport network. Specifically, the method comprises: calculating the number of large-granularity service layers required for each layer based on the number of small-granularity services, selecting the large-granularity service with the least pathfinding to create the small-granularity services; creating the corresponding large-granular services based on the routing information of the large-granular services, and sequentially creating all the service layers required for the small-granularity services from the bottom layer to the upper layer; creating the required client layer services on each created service layer service layer, allocating the required number of time slots for the client layer services on the logical ports of the service layer, and finally creating all the client layer services. A nested loop is then used to create the client layer for each service layer until the client layer services are of the desired small-granularity service type.

[0007] Preferably, the calculation of the required number of large-granularity service layers of each layer according to the number of small-granularity services specifically includes:

[0008] The number of large-granule services at each layer is calculated based on the total bandwidth required for small-granule services, the maximum bandwidth of large-granule services, the maximum number of small-granule services that can be carried, and the large-granule service types corresponding to the small-granule services.

[0009] Preferably, for end-to-end services, all service layers required for small-granularity services are created in sequence from the bottom layer to the upper layer. When all small-granularity services are pure SDH services, the process specifically includes: allocating VC4 time slots in sequence on the SDH ports at both ends of the MS service source and destination, and combining the source and destination VC4 time slots in a consistent manner to create all required VC4 service layer large-granularity services; and then allocating the number of VC12 sub-time slots in sequence on the VC4 ports at both ends of the source and destination as needed, and the allocated VC12 time slots are also combined in a one-to-one correspondence according to the time slots to create the number required for VC12 services.

[0010] Preferably, for end-to-end services, the process of creating all service layers required for small-granularity services from the bottom layer to the upper layer in sequence includes: creating an SDHover service on the OCH port; The ODUk large-granularity service is created and bound to the corresponding VSDH ports on the ODUK source and sink ports. Then, the corresponding RS and MS services are created on the bound source and sink VSDH ports. VC4 sub-timeslots on the SDH ports and VSDH ports are sequentially allocated between the start and end nodes of a pure SDH segment and between the VSDH ports bound to the start and end nodes of an ODUk segment. VC4 timeslots are combined to create all VC4 service layer services. VC4 timeslots are allocated sequentially between SDH ports and VC4 service layer services are created. VC4 timeslots are allocated sequentially between the start and end nodes of an ODUk segment of bound VSDH ports and VC4 service layer services are created. VC12 sub-timeslots are allocated sequentially as needed for each created VC4 service layer service segment and combined to create all VC12 services by combining VC4 timeslots and VC12 timeslots in a consistent and one-to-one correspondence.

[0011] Preferably, for end-to-end services, the method of sequentially creating all service layers required for small-granularity services from the bottom layer to the upper layer, when all small-granularity services are carried on ODUk, specifically includes: creating ODUk large-granularity services for each two adjacent nodes on the path, creating and binding corresponding VSDH ports on the ODUk service source and sink ports, then creating RS services and MS services on the source and sink VSDH ports bound between each two adjacent nodes, allocating VC4 time slots in sequence on each MS service source and sink VSDH port, and creating each VC4 service layer service segment based on the consistency of VC4 time slots; then allocating the required number of VC12 sub-time slots on the source and sink VC4 ports of all newly created VC4 service layers, and creating all VC12 services based on the consistency of VC4 time slots and VC12 time slots; or creating an SDH over 4K route from the start node to the end node of the small-granularity service. ODUk large-granularity services are created and bound to corresponding VSDH ports on the ODUK service source and sink ports. Corresponding RS and MS services are created on the bound source and sink VSDH ports. VC4 timeslots are sequentially allocated on the source and sink VSDH ports of the MS services, and all VC4 service layer services are created based on the consistency of the VC4 timeslots. VC12 sub-timeslots are then allocated on the source and sink VC4 ports of the VC4 service layer services in the required order, and the required number of VC12 services are created based on the consistency and one-to-one correspondence of the VC4 timeslots and VC12 timeslots.

[0012] Preferably, for single-station services, all service layers required for small-granule services are created in sequence from the bottom layer to the upper layer. When all small-granule services are pure SDH services, it specifically includes: creating single-station RS and MS large-granule services on the two SDH ports of the small-granule services respectively; and allocating VC4 time slots in sequence on the ports of the MS services, and creating single-station VC4 service layer large-granule services; selecting VC4 service layer services with the same VC4 time slots on the two ports, and allocating the number of VC12 sub-time slots in the required order, and creating the required number of VC12 services according to the consistent one-to-one correspondence of VC4 time slots and VC12 time slots.

[0013] Preferably, for a single-station service, all service layers required for the small-granularity service are created sequentially from the bottom layer to the upper layer. When part of the small-granularity service is a pure SDH service and part of it is carried on the ODUk, it specifically includes creating single-station RS and MS large-granularity services on the SDH port, allocating VC4 time slots in sequence on the MS service, and creating a single-station VC4 service layer large-granularity service; creating a single-station ODUk service layer large-granularity service on the OCh port, creating and binding a VSDH port on the ODUK logical port, creating a single-station RS and MS large-granularity service on the VSDH port; and allocating VC4 time slots in sequence on each single-station MS service, and creating a single-station VC4 service layer large-granularity service; on the SDH port and the VSDH port, selecting a VC4 service layer service with consistent VC4 time slots, and allocating VC12 sub-time slots in sequence, and finally creating the required number of VC12 services according to the consistent one-to-one correspondence of the VC4 time slots and VC12 time slots.

[0014] Preferably, for single-station services, all service layers required for small-granularity services are created from the bottom layer to the upper layer. When both ends of the small-granularity service are VSDH ports bound to ODUk, it specifically includes: creating single-station ODUk large-granularity services on the OCh ports at both ends of the service, and creating and binding corresponding VSDH ports on each oduk port, creating single-station RS and MS large-granularity services on the two VSDHs, and allocating VC4 sub-time slots in sequence on each single-station MS service, and then creating a single-station VC4 service layer service; according to the consistency of the VC4 time slots, selecting the VC4 service layer service on the two VSDH ports, and allocating the number of VC12 sub-time slots in sequence, and creating the required number of VC12 services according to the one-to-one correspondence of the VC4 time slots and the VC12 time slots.

[0015] Preferably, the process of allocating time slots for large-granularity services to each small-granularity customer layer service in sequence until the time slots for large-granularity services are filled or the required number of small-granularity services is reached specifically includes: allocating each sub-time slot to each small-granularity customer layer service in sequence for large-granularity services that require time slot allocation, until the time slots for large-granularity services are filled or the required number of small-granularity services is reached.

[0016] On the other hand, the present invention provides a device for batch creation of small-granularity services in a transport network, specifically comprising: at least one processor and a memory, the at least one processor and the memory being connected via a data bus, the memory storing instructions that can be executed by at least one processor, and the instructions, after being executed by the processor, being used to complete the method for batch creation of small-granularity services in a transport network in the first aspect.

[0017] Compared with existing technologies, the advantages of this embodiment of the present invention include: aggregating multiple small-granularity services into one or several large-granularity services, and performing batch creation and routing based solely on these aggregated large-granularity services. This significantly reduces the number of services required for routing and the time consumed in service routing and port lookup. Furthermore, subslots are allocated directly in the order they are needed, eliminating the need for port subslot detection, thus reducing the time consumed in batch creation. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] To more clearly illustrate the technical solutions of the embodiments of the present invention, the following briefly introduces the drawings required for use in the embodiments of the present invention. Obviously, the drawings described below are only some embodiments of the present invention. Those skilled in the art can also derive other drawings based on these drawings without inventive effort.

[0019] Figure 1 A flow chart of a method for batch creation of small-granularity services in a transport network provided by an embodiment of the present invention;

[0020] Figure 2 A schematic diagram of the service hierarchy in a method for batch creation of small-granularity services in a transport network provided by an embodiment of the present invention;

[0021] Figure 3 A schematic diagram of a service scenario in a method for batch creation of small-granularity services in a transport network provided by an embodiment of the present invention;

[0022] Figure 4 A schematic diagram of a service scenario in a method for batch creation of small-granularity services in a transport network provided by an embodiment of the present invention;

[0023] Figure 5 A schematic diagram of a service scenario in a method for batch creation of small-granularity services in a transport network provided by an embodiment of the present invention;

[0024] Figure 6 A schematic diagram of a service scenario in a method for batch creation of small-granularity services in a transport network provided by an embodiment of the present invention;

[0025] Figure 7 A schematic diagram of a service scenario in a method for batch creation of small-granularity services in a transport network provided by an embodiment of the present invention;

[0026] Figure 8 A schematic diagram of a service scenario in a method for batch creation of small-granularity services in a transport network provided by an embodiment of the present invention;

[0027] Figure 9 A schematic diagram of a service scenario in a method for batch creation of small-granularity services in a transport network provided by an embodiment of the present invention;

[0028] Figure 10 A schematic diagram of a service scenario in a method for batch creation of small-granularity services in a transport network provided by an embodiment of the present invention;

[0029] Figure 11 A schematic diagram of the structure of a device for batch creation of small-granularity services in a transport network provided by an embodiment of the present invention;

[0030] The accompanying drawings are numerals as follows:

[0031] 11: Processor; 12: Memory. DETAILED DESCRIPTION

[0032] In order to make the purpose, technical solutions and advantages of the present invention more clearly understood, the present invention will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not intended to limit the present invention.

[0033] The present invention is an architecture of a specific functional system. Therefore, the specific embodiments mainly illustrate the functional logical relationship between the various structural modules, and do not limit the specific software and hardware implementation methods.

[0034] In addition, the technical features involved in the various embodiments of the present invention described below can be combined with each other as long as they do not conflict with each other. The present invention will be described in detail below with reference to the accompanying drawings and embodiments.

[0035] The service types in this embodiment include: OCh / ODU4 / ODU2 / ODU1 / ODU0 / RS / MS / VC4 / VC12. Some terms used in this embodiment are explained as follows:

[0036] (1) NE: Network Element. In the following text, NE1, NE2, NE3, etc. are the numbers of different network elements in actual scenarios. NE_S represents the source network element, and NE_D represents the sink network element.

[0037] (2)OCh ： Optical channel layer, optical channel layer network, is the service layer of ODUk.

[0038] (3) ODUk: Optical Channel Data Unit. It mainly includes the ODUk frame structure, ODUk bit rate, and bit rate tolerance. The value of K is 0, 1, 2, 3, or 4.

[0039] (4) SDH: Synchronous Digital Hierarchy. According to ITU-T recommendations, SDH is a technical system that provides information structures of corresponding levels for the transmission of digital signals at different rates, including multiplexing and mapping methods, as well as related synchronization methods. The SDH services in this embodiment of the present invention primarily include VC4, VC12, and VC3.

[0040] (5) VSDH: Virtual Synchronous Digital Hierarchy, a virtual SDH port used to bind to an ODUK port, enabling ODUK services to carry SDH services. VSDH1, VSDH2, etc. are VSDH numbers created for the current network element.

[0041] (6) STM: Synchronous Transport Mode, the information structure of SDH. Hereinafter, STM1, STM4, STM16, STM64, and STM256 represent different specified rates. The bit rate of the ODUk signal is related to the STM-N bit rate, and its bit rate tolerance is exactly the bit rate tolerance of the STM-N signal.

[0042] (7) MS: Multiplex Section, a channel layer service of SDH. There are two types of MS: one that occurs with the creation of an SDH over ODUk service and one that is automatically generated when an SDH port is connected to a fiber. MS services are created on STM ports of different rates and can carry services of the corresponding rates.

[0043] (8) RS: Regenerator Section, which is another path layer service of SDH. MS is the client layer of RS.

[0044] (9) VC: Virtual Container. VC4 is a 155M-level virtual container in the SDH standard. VC4 includes VC4 services and VC4 server layer services. VC4 server layer services are service layer services created specifically for low-order VC services. VC4 services cannot be used as a service layer for low-order services. VC12 is a 2M-level virtual container in the SDH standard and is a low-order service. VC3 is a 45M-level virtual container in the SDH standard and is a low-order service.

[0045] Example 1:

[0046] In network communications, a large-granularity service can carry multiple small-granularity services. The method provided in this embodiment creates small-granularity services, especially SDH services, in batches, selects large channels for routing, and then allocates time slots for creation, without sharing the network.

[0047] In this embodiment, small-granularity services and large-granularity services can be defined according to actual needs. The service levels supported by the method provided in this embodiment include but are not limited to the following levels from the bottom layer to the upper layer:

[0048] SDH fiber -> RS -> MS -> VC4;

[0049] SDH fiber -> RS -> MS -> VC4 server layer -> VC12;

[0050] SDH fiber -> RS -> MS -> VC4 service layer -> VC3;

[0051] OTN fiber -> OCH -> ODUK -> RS -> MS -> VC4;

[0052] OTN fiber -> OCH -> ODUK -> RS -> MS -> VC4 service layer -> VC12;

[0053] OTN fiber -> OCH -> ODUK -> RS -> MS -> VC4 service layer -> VC3.

[0054] The VC4 service only refers to the VC4 service in a narrow sense, and the VC4 service layer refers to the service layer used to carry low-order VC services. The low-order VC services that can be carried include VC12, VC3, etc.

[0055] If multiple B services of the previous level can be created on the A service of the layer, the A service is regarded as the large-granule service of the B service, and the B service is regarded as the small-granule service of the A service. For example: when VC12 is regarded as a small granule, the VC4 service layer and ODUk are both large granules; when VC4 is regarded as a small granule, ODUk is a large granule; when ODU0 is regarded as a small granule, its service layer ODU2 and ODU4 are large granules; the service layer of any granule is a large granule of the client layer. Figure 1 As shown, the specific steps of the method for batch creation of small-granularity services in a transport network provided by an embodiment of the present invention are as follows.

[0056] Step 101: Calculate the number of large-granularity service service layers required for each layer according to the number of small-granularity services, and select the large-granularity service with the least number of pathfinding times to create a bearer for the small-granularity service.

[0057] First, find all service layer types required by the small-granularity service based on the service type. Then, calculate the number of large-granularity services required for each service layer of the small-granularity service as needed. In actual implementation, the number of large-granularity services per layer is calculated based on the total bandwidth required by the small-granularity service, the maximum bandwidth of the large-granularity service, the maximum number of small-granularity services that can be carried, and the large-granularity service type corresponding to the small-granularity service. For example, if VC12 services are used as small-granularity services and 2000 VC12s need to be created, based on the granularity relationship, 34 VC4 service layer services are required to carry 2000 VC12s. One ODU2 is required to carry 34 VC4 services, so one ODU2 can carry and create 2000 VC12 services. In this case, only the timeslot check of the ODU2 service is required, and there is no need to check the availability of the sub-timeslots allocated by the ODU2, which improves creation efficiency.

[0058] On the other hand, when a large-granularity service is used to carry multiple small-granularity services, only one routing operation is required for the large-granularity service to create all the small-granularity services it carries. For example, if 2000 VC12 services require 2000 routing operations, but when they are carried on a single ODU2, only one routing operation is required for the ODU2.

[0059] To further optimize SDH service routing, you can select large-granularity services that require the least routing times. For example, if 2000 VC12s require a 10G path service layer, you can use MS services on pure SDH ports of ODU2 or STM64. Select the service layer type for each segment based on the actual scenario, as long as the routing times are minimized.

[0060] Furthermore, when routing large-granularity services, if an ODU2 MS service is selected, since there is no MS layer edge during VC4 routing, the OCh path can be used to directly route the service back to the ODUK layer. In this case, when the OCh path is used to create the SDH over ODUk service in the reverse direction, RS and MS services are also created. When creating a service, creating a client layer on the service layer service is considered forward creation; creating a client layer simultaneously with the service layer, since there is no service layer available for carrying, is considered reverse creation.

[0061] Step 102: Create corresponding large-granularity services according to the routing information of the large-granularity services, and create all service layers required for the small-granularity services from the bottom layer to the upper layer.

[0062] After selecting the granular service with the least number of pathfinding times, it is also necessary to pathfind the selected large-granular service and create the corresponding large-granular service based on the found path. Since the small-granular service that needs to be created in the end needs the support of the lower-level service layer service, it is also necessary to create the lower-level service layer services required by the small-granular service in turn. The specific creation method of each service is implemented according to the specifications of the existing network. In the specific implementation scenario, since the actual network architecture contains a multi-layer structure, it is necessary to create each required service layer in turn from the bottom to the top according to the network architecture. For example, according to Figure 2 In the service layer shown, the left side is pure SDH service, and the right side is SDH service carried on ODUk. For VC12 small-granularity service, it is necessary to create ODU4, ODU2, RS, MS, VC4 service layer and other service layer large-granularity services in sequence.

[0063] Step 103: Create the required client layer services on each created service layer service. Allocate the required number of time slots for the client layer services on the service layer logical ports in the required order, and create all client layer services. This process continues in a nested loop, creating the client layer for each service layer until the client layer services are the desired fine-grained service type.

[0064] After creating a large-granularity service, you also need to create the required small-granularity services on the service layer service of the small-granularity service and allocate time slots for each small-granularity service. Specifically: on the large-granularity service that requires time slot allocation, each sub-time slot is allocated to each small-granularity client layer service in sequence until the large-granularity service time slot is full or the required number of small-granularity services is reached. Since the large-granularity service is a newly created service, there are no sub-services occupying its sub-time slots, so there is no need to check whether the sub-time slots in the large-granularity service are occupied. For example, to create a VC12 small-granularity service on the VC4 service layer, you only need to allocate the required number of VC12 time slots on the logical ports of the VC4 service layer in sequence until the VC12 small-granularity service fills the VC4 service layer time slots or the required number of VC12 services is reached.

[0065] After steps 101 to 103 provided in this embodiment, batch creation of small-granularity services can be completed, and the large-granularity services are used to create bearers for the small-granularity services.

[0066] Furthermore, in the actual creation process, for two adjacent layers, the services of the upper layer can be regarded as small-granular services relative to the services of the lower layer. Therefore, the creation process of steps 101 to 103 can be repeated iteratively, and services are created layer by layer from the bottom layer to the top layer of the network.

[0067] The method provided in this embodiment is applicable not only to SDH services, but also to all small-granularity services, such as OTN and PTN services. During pathfinding, the required large-granularity ports are first calculated, then the large-granularity ports are searched, and then, based on the service hierarchy, service-layer services are created first and then client-layer services on the large-granularity ports. The number of sub-timeslots is allocated as needed, and a corresponding number of small-granularity services are created.

[0068] In step 102, each service layer required for the small-granularity service is created sequentially from the bottom up. Different methods are used for different service transmission modes and network architectures. The following uses the VC12 small-granularity service as an example to briefly illustrate some practical creation methods. In practice, the creation method can be tailored to meet actual needs, network structure, and service requirements. The following NEs support the creation of optical transport network services and SDH services.

[0069] (1) End-to-end services

[0070] (1) Figure 3 As shown, all small-granularity services are pure SDH services.

[0071] VC4 timeslots are allocated sequentially on the SDH ports at both ends of the MS service source and sink, and are combined in a consistent manner to create all the required VC4 service layer large-granularity services. VC12 sub-timeslots are then allocated sequentially on the VC4 ports at both ends as needed, and the allocated VC12 timeslots are also combined in a consistent one-to-one correspondence to create the required number of VC12 services.

[0072] Figure 3 In this pure SDH port model, MSs are created for SDH ports between NE1 and NE2, and between NE2 and NE3. The MSs are carried on optical fibers, and a VC cross-connect is created on NE2. Since the MS services already exist, only the VC4 service layer needs to be created in reverse order. VC4 timeslots are allocated sequentially to the ports serving the MS services as needed to create the required number of VC4 service layers. The VC4 service layers between NE1 and NE2 and between NE2 and NE3 are combined in a one-to-one correspondence based on the timeslot alignment. VC12 sub-timeslots are then allocated sequentially to the ports of the VC4 service layers, and the allocated VC12 timeslots are also combined in a one-to-one correspondence based on the timeslot alignment to create the required number of VC12 services.

[0073] (2) Figure 4 As shown, the small-granularity service portion is a pure SDH service and is partially carried on the ODUk.

[0074] Large-granularity SDH over ODUk services are created on the OCH ports, and corresponding VSDH ports are created and bound to the ODUK source and sink ports. Corresponding RS and MS services are then created on the bound source and sink VSDH ports. VC4 sub-timeslots are sequentially allocated between the bound VSDH ports at the head and tail nodes of the pure SDH segment, and all VC4 server layer services are created by combining them in a consistent manner using VC4 timeslots. VC4 timeslots are also sequentially allocated between the SDH ports at the head and tail nodes of the ODUk segment of the bound VSDH ports, and VC4 server layer services are created. Finally, the required number of VC12 sub-timeslots is allocated to each created VC4 server layer service segment, and all required VC12 services are created by combining VC4 timeslots and VC12 timeslots in a consistent, one-to-one correspondence. In the SDH over ODUk model, to enable ODUk services to carry SDH transmission, a virtual VSDH port is first created and bound to the created ODUk source and sink ports. At this point, the source and sink VSDH ports already exist. RS services are then created using these ports, followed by MS services. Both the RS and MS source and sink ports are VSDH ports, ensuring that the VSDH port rate equals the ODUk rate. In this case, the MS rate created on the VSDH port equals the ODUk service rate. When creating SDH over ODUk, you can optionally create an STM-n port for the MS to determine the transmission rate. To ensure efficient transmission, the STM-n rate must be less than or equal to the ODUk bearer rate.

[0075] like Figure 4 In the mixed SDH and OCh port model shown, an MS is created on the SDH port between NE1 and NE2, and an MS is carried on ODUk between NE2 and NE3. A VC cross-connect is created on NE2. SDH over ODUk is first created between NE2 and NE3, followed by a VSDH port binding. RS and MS are then created on the VSDH port from NE2 to NE3. VC4 timeslots are then allocated sequentially between NE1 and NE2, and between NE2 and NE3, and VC4 service layers are created. VC4 service layers with consistent VC4 timeslots are then selected, and VC12 sub-timeslots are allocated on the source and sink ports of each VC4 service layer. The required number of VC12 sub-timeslots are created, ensuring a consistent and one-to-one correspondence between VC4 timeslots and VC12 timeslots.

[0076] Specifically, a route is first found from source NE1 to sink NE3, resulting in the route {MS(NE1-NE2), OCh(NE2-NE3)}. The found route is then analyzed to determine the large-granularity service to be created. Analysis indicates that SDH over ODUk must be created on the OCh(NE2-NE3) route. The ODUk source and sink ports are bound to the VSDH1 ports on NE2 and NE3. The RS(NE1-NE2) and MS(NE1-NE2) services are created using the VSDH1 ports on both NE2 and NE3. This creates a new routing path {MS(NE1-NE2), MS(NE2-NE3)}.

[0077] There are two ways to create a VC4 service layer:

[0078] Scenario 1: Create a VC4 service layer on the new route based on the found path. Specifically: Create a VC4 service layer on the MS (NE1-NE2) route, and create a VC4 service layer on the MS (NE2-NE3), forming a new route {VC4 service layer (NE1-NE2), VC4 service layer (NE2-NE3)}, completing the creation of large-granularity services on the VC4 service layer. Finally, create VC12 on the formed VC4 service layer route. At this time, the NE2 network element only has VC12 cross-connection and no VC4 cross-connection. The final VC12 path is: {VC12 (NE1, NE2, NE3)}.

[0079] During the actual creation process, RS and MS channels are automatically created when the SDH port is connected to the optical fiber. RS and MS are automatically created when the OCh port creates SDH over ODUk. Therefore, the large-granularity services of these two service layers do not need to be created separately.

[0080] In scenario 2, a server layer service is directly created across NE1, NE2, and NE3, except that a VC4 cross-connection is created on NE2. Specifically, a VC4 server layer is created from NE1 to NE3 along the path {MS(NE1-NE2), MS(NE2-NE3)}, forming a new path {VC4 server layer (NE1, NE2, NE3)}. Finally, timeslots are allocated on the VC4 server layer to create a VC12. At this point, NE2 only has a VC4 cross-connection, not a VC12 cross-connection. The resulting VC12 path is {VC12 (NE1, NE2, NE3)}.

[0081] (3) Figure 5 As shown in FIG, all small-granularity services are carried on ODUk.

[0082] Figure 5 The OCh port model in includes two cases.

[0083] Case 1: If Figure 6 As shown, between NE1 and NE2, and between NE2 and NE3, there are MSs carrying ODUk.

[0084] In this case, create an ODUk large-granularity service for each two adjacent nodes on the path, create and bind corresponding VSDH ports to the ODUK service source and sink ports, and then create RS and MS services on the source and sink VSDH ports bound between each two adjacent nodes. Create a VC4 service layer service between each two adjacent nodes on each MS service. Specifically, allocate VC4 time slots in sequence on each MS service source and sink VSDH port as needed, and create VC4 service layer services with the required data volume for each MS segment based on the consistency of the VC4 time slots. Then, allocate the required number of VC12 sub-time slots on all newly created source and sink VC4 ports as needed, and create the required number of VC12 services based on the consistency and one-to-one correspondence of the VC4 time slots and VC12 time slots.

[0085] Specifically, create an SDH over ODUK from NE1 to NE2, binding the VSDH1 port on NE1 and the VSDH1 port on NE2. Create an SDH over ODUK from NE2 to NE3, binding the VSDH2 port on NE2 and the VSDH1 port on NE3. Use the VSDH1 port bound to NE1 and the VSDH1 port bound to NE2 to create RS and MS services from NE1 to NE2. Use the VSDH2 port bound to NE2 and the VSDH1 port bound to NE3 to create RS and MS services from NE2 to NE3.

[0086] Then, create VC4 service layer services from NE1 to NE2 and from NE2 to NE3, and finally create VC12 services. In this case, a VC12 cross-connection is created on NE2 alone.

[0087] Case 2: If Figure 7 As shown, there is only one section between NE1 and NE3 that carries the MS ODUk.

[0088] In this case: create a large-granularity SDH over ODUk service from the initiator to the tail node of the small-granularity service, create and bind the corresponding VSDH1 port to the source and sink ports of the ODUK service, create the corresponding RS service and MS service on the bound source and sink VSDH1 ports, then create the corresponding VC4 server layer service on the MS service, and then allocate the number of sub-timeslots on the VC4 server layer service in the required order, and create the required number of VC12 services.

[0089] Specifically, create an SDH over ODUk segment from NE1 to NE3. This creates a single MS path from NE1 to NE3. Create an ODUk segment from NE1 to NE3, then create RS and MS paths from NE1 to NE3. Then create a VC4 server layer service from NE1 to NE3, and finally, create a VC12 service from NE1 to NE3. In this scenario, there is only one MS segment, the source and sink nodes of the ODUk segment are NE1 and NE3, and only the ODUK segment crosses on NE2.

[0090] (2) Single-station business

[0091] (1) Figure 8 As shown, all small-granularity services are pure SDH services.

[0092] On the two SDH ports for the small-granularity service, reverse engineer the single-station RS and MS large-granularity services. VC4 timeslots are allocated sequentially on the MS service port to create the single-station VC4 server-layer large-granularity service. VC4 server-layer services with the same VC4 timeslots are then selected on both ports, and the required number of VC12 sub-timeslots are allocated sequentially. The required number of VC12 services is created by creating a consistent one-to-one correspondence between the VC4 timeslots and the VC12 timeslots.

[0093] (2) Figure 9 As shown, the small-granularity service portion is a pure SDH service and is partially carried on the ODUk.

[0094] On the SDH port, create single-station RS and MS large-granularity services in reverse order. Sequentially allocate VC4 timeslots to the MS service and create single-station VC4 server-layer large-granularity services. On the OCh port, create single-station ODUk server-layer large-granularity services, create and bind VSDH ports to the ODUK logical port, and then reversely create single-station RS and MS large-granularity services on the VSDH port. Sequentially allocate VC4 timeslots to each single-station MS service port to create the required number of VC4 server-layer large-granularity services. On the SDH and VSDH ports, select VC4 server-layer services with the same VC4 timeslots and sequentially allocate VC12 sub-timeslots. Finally, create the required number of VC12 services by aligning the VC4 timeslots with the VC12 timeslots.

[0095] Use the VC4 server layer services on the SDH and OCh ports to create the required VC12 services.

[0096] (3) Figure 10 As shown, both ends of the small-granularity service are VSDH ports bound to ODUk.

[0097] Create single-station ODUk large-granularity services on the OCh ports at both ends of the service. Create and bind a VSDH1 port to the ODUK port on one end, and a VSDH2 port to the ODUK port on the other end. Create single-station RS and MS services on the VSDH1 and VSDH2 ports, respectively. Sequentially allocate VC4 sub-timeslots on each single-station MS service port to create the required number of single-station VC4 server layer services. Based on the consistency of VC4 timeslots, select the VC4 server layer services on the VSDH1 and VSDH2 ports, sequentially allocate the required number of VC12 sub-timeslots, and create the required number of VC12 services based on the one-to-one correspondence between the VC4 timeslots and the VC12 timeslots.

[0098] It can be seen from the creation method and specific examples in the above implementation scenario that the method provided in this embodiment can be used to complete the creation of small-granularity services based on large-granularity services, achieving the technical effect of using one large-granularity service to carry multiple small-granularity services.

[0099] In the scenario where small-granularity VC3s are created in batches, using the same method as above, the final service path is {NE / STM64-1 / VC4-1 / VC3-n, NE / VSDH1 / VC4-1 / VC3-n}. Because a VC4 port can only carry three VC3 services, n in the above service path can only be 1, 2, or 3.

[0100] When creating batches of small-granularity VC4 services, using the same method as above, the resulting service path is {NE / STM64-1 / VC4-n, NE / VSDH1 / VC4-n}. Since the VC4 granule size is 155M, the value of n in the above service path is the parent interface rate divided by 155M. For example, if the parent STM64 interface is 10G, the maximum value of n is 10*1024 / 155≈66, and the timeslot value of n ranges from 1 to 66.

[0101] This embodiment provides a method for batch creation of small-granularity services on a transport network. This method aggregates multiple small-granularity services into a single large-granularity service. Batch creation and routing are performed based solely on the aggregated large-granularity service. This avoids routing and timeslot detection for a large number of small-granularity services, significantly reducing the number of small-granularity service routing attempts and the time required for service routing and port lookup. Furthermore, by eliminating the need for port sub-timeslot detection and directly allocating full timeslots, batch creation is time-consuming.

[0102] Example 2:

[0103] Based on the method for batch creation of small-granularity services on a transport network provided in Example 1, this embodiment provides an example of creating an end-to-end service in a specific scenario.

[0104] Specific scenarios such as Figure 4 As shown in the figure, 2000 VC12 small-granularity services need to be created. The source port of the VC12 services is NE1 port 1, and the sink port is NE3 port 2. The service between NE1 and NE2 is pure SDH service, and the service between NE2 and NE3 is SDH service carried on ODUk.

[0105] According to step 101, the large-granularity services that need to be created are calculated.

[0106] The bit rate required for 2000 VC12s is 2000*2M=4000M, and the service layer service requires 4000M bandwidth.

[0107] At the VC4 layer, the VC4 granularity is 155M. Since one VC4 can only create 63 VC12s, 32 VC4 service layer services are required (32*155M=4960M).

[0108] At the ODUk layer, the STM-16 frame rate is 2.5G, and the ODU1 bit rate is 239 / 238 of the STM-16 bit rate. Therefore, two ODU1 services are required: 2*2.5G = 5G = 5120M. Alternatively, two MS services with STM16 capacity can be used. Alternatively, a combined path of two ODU1 and STM16 MS services can be used.

[0109] At the ODUk layer, the STM64 granular capacity is 10G, and the ODU2 bit rate is 239 / 237, which is four times the STM-16 bit rate. Therefore, an ODU2 service (1*10G = 10G) is required, or an MS service with STM64 capacity, or a combined path of ODU2 and STM64 MS services.

[0110] According to the calculation of the above service relationship and the granularity of the bearer, for end-to-end services, only one MS routing of ODU2 or STM64 capacity is required to complete the creation of 2000 VC12 services. Alternatively, two MS routings of ODU1 or STM16 capacity can be performed to complete the creation of 2000 VC12 services. It can be seen that the method provided in Example 1 can greatly reduce the number of routing and query times for VC12 services, from 2000 routing times for end-to-end services to 1 or 2 times.

[0111] In a specific implementation, whether to use ODU2 particles / STM64 particles or ODU1 particles / STM16 particles to carry VC services can be selected based on actual needs and network configuration.

[0112] According to step 101, the source and sink ports of the VC12 are used as the source and sink ports of the ODU2 particle / STM64 particle, and a combination of an MS path for the STM64 particle and a path for the ODU2 particle is searched. An STM64 MS service between NE1 and NE2 and an OCh service between NE2 and NE3 are found between NE1 and NE3. The OCh service is used to carry and create the ODU2 service. At this point, only one path search from NE1 to NE3 is performed to obtain the path {NE1-1, STM64_MS: {NE1-2 to NE2-1}, OCh: {NE2-1 to NE3-1}, NE3-2} for creating 2000 VC12 services, where -n represents the port number of the network element. Since the ODU2 particle / STM64 particle only requires one path search, the number of path searches is minimized. Therefore, in this embodiment, the combined path of the ODU2 particle and the STM64 particle can be selected as the large-particle service.

[0113] According to step 102, corresponding large-granularity services are created layer by layer according to the found paths.

[0114] For large-granularity services routed to the path {NE1-1, STM64_MS:{NE1-2 to NE2-1}, OCh:{NE2-2 to NE3-1}, NE3-2}, you can create services at each layer as follows.

[0115] 1. Create an ODUK and bind it to a VSDH port.

[0116] Because an OCh service exists in the path, an SDH over ODUk service must first be created on the OCh service. Based on the selection in step 101, a DDU2 service is created. Then, bound VSDH ports are created on the source and sink ports of ODU2. Specifically, an SDH over ODUk service is created on the OCH port of NE2-2 and the OCH port of NE3-1. VSDH1 is bound to the ODUK logical port on NE2-2 and the ODUK logical port on NE3-1 for the ODUK service.

[0117] 2. Create RS and MS services.

[0118] When creating VSDH1 ports on NE2-2 and NE3-1, MS and RS trails are automatically created from NE2 to NE3 after the ODUK is created. The MS and RS form the trail {NE1-1, STM64_MS{NE1-2 to NE2-1}, ODU2_MS{NE2-2 to NE3-1}, NE3-2}.

[0119] 3. Create the VC4 service layer.

[0120] On the MS path STM64_MS{NE1-2~NE2-1} and the MS path ODU2_MS{NE2-2~NE3-1}, 32 VC4 service layer services are created by sequentially allocating time slots.

[0121] (1) The VC4 service layer service timeslot of path STM64_MS{NE1-2~NE2-1} is:

[0122] The first VC4 server layer service: NE1 / STM64-2 / VC4-1 to NE2 / STM64-1 / VC4-1.

[0123] Article 2 VC4 server layer service: NE1 / STM64-2 / VC4-2 to NE2 / STM64-1 / VC4-2.

[0124] Article 3 VC4 server layer service: NE1 / STM64-2 / VC4-3 to NE2 / STM64-1 / VC4-3.

[0125] …

[0126] 32nd VC4 server layer service: NE1 / STM64-2 / VC4-32 to NE2 / STM64-1 / VC4-32.

[0127] Since the STM64 physical port MS that does not carry any services will be directly selected when selecting a route, the VC4 timeslots can be directly allocated in sequence without checking whether the VC4 timeslots are occupied.

[0128] (2) The VC4 service layer service timeslot of the path ODU2_MS {NE2-2 to NE3-1} is:

[0129] Article 1 VC4 server layer service: NE2 / VSDH1 / VC4-1 to NE3 / VSDH1 / VC4-1.

[0130] Article 2 VC4 server layer service: NE2 / VSDH1 / VC4-2 to NE3 / VSDH1 / VC4-2.

[0131] Article 3 VC4 server layer service: NE2 / VSDH1 / VC4-3 to NE3 / VSDH1 / VC4-3.

[0132] …

[0133] Article 32 VC4 server layer service: NE2 / VSDH1 / VC4-32 to NE3 / VSDH1 / VC4-32.

[0134] Since ODUk is a newly built service, the bound VSDH1 port is also a newly built port and no time slot is occupied. Therefore, when allocating time slots on the VSDH1 port, there is no need to check whether the time slots are occupied. Timeslots can be allocated directly in order.

[0135] After the VC4 server layer is created, the VC4 port timeslots are aligned one-to-one to form new routing paths. A total of 32 paths based on the VC4 server layer are combined:

[0136] 1: {NE1-1, VC4 server layer {NE1 / STM64-2 / VC4-1 to NE2 / STM64-1 / VC4-1}, VC4 server layer {NE2 / VSDH1 / VC4-1 to NE3 / VSDH1 / VC4-1}, NE3-2}

[0137] 2: {NE1-1, VC4 server layer {NE1 / STM64-2 / VC4-2 to NE2 / STM64-1 / VC4-2}, VC4 server layer {NE2 / VSDH1 / VC4-2 to NE3 / VSDH1 / VC4-2}, NE3-2}

[0138] …

[0139] 32: {NE1-1, VC4 server layer {NE1 / STM64-2 / VC4-32 to NE2 / STM64-1 / VC4-32}, VC4 server layer {NE2 / VSDH1 / VC4-32 to NE3 / VSDH1 / VC4-32}, NE3-2}

[0140] According to step 103, a small-granularity service VC12 is created.

[0141] At this point, there are 32 routing paths for large-granularity services. 63 VC12 services are created by sequentially allocating time slots on each of the first 31 routing paths. 47 VC12 paths are created by allocating time slots on the last path based on attributes, completing the creation of 2,000 VC12 paths.

[0142] The 63 VC12 trails created on the VC4 timeslot 1 trail are:

[0143] The first VC12 in VC4 timeslot 1:

[0144] {NE1 / STM64-1 / VC4-1 / VC12-1,NE1 / STM64-2 / VC4-1 / VC12-1,NE2 / STM64-1 / VC4-1 / VC12 -1,NE2 / VSDH1 / VC4-1 / VC12-1,NE3 / VSDH1 / VC4-1 / VC12-1,NE3 / STM64-2 / VC4-1 / VC12-1}

[0145] The second VC12 with VC4 timeslot 2:

[0146] {NE1 / STM64-1 / VC4-1 / VC12-2,NE1 / STM64-2 / VC4-1 / VC12-2,NE2 / STM64-1 / VC4-1 / VC12 -2,NE2 / VSDH1 / VC4-1 / VC12-2,NE3 / VSDH1 / VC4-1 / VC12-2,NE3 / STM64-2 / VC4-1 / VC12-2}

[0147] …

[0148] The 63rd VC12 with VC4 timeslot 1:

[0149] :{NE1 / STM64-1 / VC4-1 / VC12-63,NE1 / STM64-2 / VC4-1 / VC12-63,NE2 / ST M64-1 / VC4-1 / VC12-63,NE2 / VSDH1 / VC4-1 / VC12-63,NE3 / VSDH1 / VC4-1 / VC12-63,NE3 / STM64-2 / VC4-1 / VC12-63}

[0150] The 63 VC12 trails created on the VC4 path with timeslot 2 are:

[0151] The first VC12 in VC4 timeslot 2:

[0152] {NE1 / STM64-1 / VC4-2 / VC12-1,NE1 / STM64-2 / VC4-2 / VC12-1,NE2 / STM64-1 / VC4-2 / VC12 -1,NE2 / VSDH1 / VC4-2 / VC12-1,NE3 / VSDH1 / VC4-2 / VC12-1,NE3 / STM64-2 / VC4-2 / VC12-1}

[0153] The second VC12 with VC4 timeslot 2:

[0154] {NE1 / STM64-1 / VC4-2 / VC12-2,NE1 / STM64-2 / VC4-2 / VC12-2,NE2 / STM64-1 / VC4-2 / VC12 -2,NE2 / VSDH1 / VC4-2 / VC12-2,NE3 / VSDH1 / VC4-2 / VC12-2,NE3 / STM64-2 / VC4-2 / VC12-2}

[0155] …

[0156] The 63rd VC12 with VC4 timeslot 2:

[0157] {NE1 / STM64-1 / VC4-2 / VC12-63,NE1 / STM64-2 / VC4-2 / VC12-63,NE2 / STM64-1 / VC4-2 / VC12- 63,NE2 / VSDH1 / VC4-2 / VC12-63,NE3 / VSDH1 / VC4-2 / VC12-63,NE3 / STM64-2 / VC4-2 / VC12-63}

[0158] As described above, 63 VC12s are created in the 3rd to 31st timeslots of VC4.

[0159] Then, 47 VC12 paths are created on the VC4 path with timeslot 32, namely:

[0160] The first VC12 with a VC4 timeslot of 32:

[0161] :{NE1 / STM64-1 / VC4-32 / VC12-1,NE1 / STM64-2 / VC4-32 / VC12-1,NE2 / ST M64-1 / VC4-32 / VC12-1,NE2 / VSDH1 / VC4-32 / VC12-1,NE3 / VSDH1 / VC4-32 / VC12-1,NE3 / STM64-2 / VC4-32 / VC12-1}

[0162] The second VC12 with a VC4 timeslot of 32:

[0163] {NE1 / STM64-1 / VC4-32 / VC12-2,NE1 / STM64-2 / VC4-32 / VC12-2,NE2 / STM64-1 / VC4-32 / VC12-2,NE2 / VSDH1 / VC4-32 / VC12-2,NE3 /

[0164] VSDH1 / VC4-32 / VC12-2,NE3 / STM64-2 / VC4-32 / VC12-2}

[0165] …

[0166] The 47th VC12 with VC4 timeslot 32:

[0167] {NE1 / STM64-1 / VC4-32 / VC12-47,NE1 / STM64-2 / VC4-32 / VC12-47,NE2 / STM64-1 / VC4-32 / VC12- 47,NE2 / VSDH1 / VC4-32 / VC12-47,NE3 / VSDH1 / VC4-32 / VC12-47,NE3 / STM64-2 / VC4-32 / VC12-47}

[0168] As can be seen from the above example, according to the method provided in Example 1, in the scenario of this embodiment, only one ODU2 service and one STM64 service need to be created, and routing performed once to complete batch creation and routing of 2000 VC12 services.

[0169] Example 3:

[0170] Based on the method for batch creation of small-granularity services on a transport network provided in Example 1, this embodiment provides an example of creating a single-station service in a specific scenario.

[0171] Specific scenarios such as Figure 9 As shown in the figure, 2000 VC12 small-granularity services need to be created. Port 1 of the NE is a pure SDH service port, and port 2 is an OCH port carrying ODUk.

[0172] According to step 101, the large-granularity services that need to be created are calculated.

[0173] Similar to the calculation method in Example 2, for single-station services, since two ports are required to create a single-station service, it is necessary to find one of the following situations:

[0174] 1. Two ODU2 OCH ports,

[0175] 2. 2 STM64 SDH ports

[0176] 3. An OCH port of an ODU2 particle and an SDH port of an STM64.

[0177] 4, OCH ports for 4 ODU1 particles

[0178] 5. 4 STM16 SDH ports

[0179] 6. Any combination of four ports, including OCH ports on ODU1 granularity and SDH ports on STM16, can create 2,000 VC12 services. Therefore, the number of services per station is reduced from 4,000 port lookups to 2 or 4.

[0180] According to step 101, search for single-station service ports. In order to create 2000 VC12 services, you can choose to create two single-station ODU2s, or two STM64 SDH physical ports, or one single-station ODU2 and one STM64 SDH physical port. The specific choice is determined according to the actual network structure and service needs. Figure 9 Take a single-station ODU2 and an STM64 SDH physical port in the example, and search for a single-station ODU2 port and an STM64 SDH physical interface in the NE.

[0181] According to step 102, corresponding large-granularity services are created layer by layer according to the found paths.

[0182] 1. Create ODUk and VSDH binding.

[0183] Find an OCh port on the network element, create an SDH over ODU2 service on the port, create VSDH1, and then bind VSDH1 to the port of the ODU2 service.

[0184] 2. Create a single-station RS and MS.

[0185] Create single-station RS and single-station MS services on VSDH1.

[0186] Create RS and MS single-station services on the STM64 SDH physical port.

[0187] 3. Create a single-station VC4 service layer on the MS.

[0188] As required, VC4 time slots need to be allocated sequentially on the VSDH1 port and SDH port to create 32 single-station VC4 service layer services.

[0189] At this time, 32 VC4 service layer services are created on the VSDH1 port as follows:

[0190] Article 1 VC4 server layer single-station service: NE / VSDH1 / VC4-1

[0191] Article 2 VC4 service layer single-station service: NE / VSDH1 / VC4-2

[0192] Article 3 VC4 service layer single-station service: NE / VSDH1 / VC4-3

[0193] …

[0194] Article 32 VC4 server layer single-station service: NE / VSDH1 / VC4-32

[0195] To create 32 VC4 service layer services on the STM64 SDH physical port:

[0196] VC4 service layer single-station service No. 1: NE / STM64-1 / VC4-1

[0197] Article 2 VC4 service layer single-station service: NE / STM64-1 / VC4-2

[0198] Article 3 VC4 service layer single-station service: NE / STM64-1 / VC4-3

[0199] …

[0200] Article 32 VC4 service layer single-station service: NE / STM64-1 / VC4-32

[0201] According to step 103, a small-granularity service VC12 is created.

[0202] In this case, you only need to create 63 VC12 single-station services on each of the first 31 VC4 service layer single-station services, and create 47 VC12 single-station services on the 32nd single-station VC4 service layer. By matching the VC4 service layers and timeslots one by one, and ensuring that the timeslots of the VC12 service sources and sinks are the same, you can create 2000 VC12 services.

[0203] Create 63 VC12s in VC4 timeslot 1.

[0204] The first VC12 service in VC4 timeslot 1:

[0205] {NE / STM64-1 / VC4-1 / VC12-1, NE / VSDH1 / VC4-1 / VC12-1}

[0206] The second VC12 service in VC4 timeslot 1:

[0207] {NE / STM64-1 / VC4-1 / VC12-2, NE / VSDH1 / VC4-1 / VC12-2}

[0208] …

[0209] VC12 service No. 63 in VC4 timeslot 1:

[0210] {NE / STM64-1 / VC4-1 / VC12-63, NE / VSDH1 / VC4-1 / VC12-63}

[0211] Create 63 VC12s in VC4 timeslot 2.

[0212] The first VC12 service in VC4 timeslot 2:

[0213] {NE / STM64-1 / VC4-2 / VC12-1, NE / VSDH1 / VC4-2 / VC12-1}

[0214] The second VC12 service in VC4 timeslot 2:

[0215] {NE / STM64-1 / VC4-2 / VC12-2, NE / VSDH1 / VC4-2 / VC12-2}

[0216] …

[0217] VC12 service No. 63 with VC4 timeslot 2:

[0218] {NE / STM64-1 / VC4-2 / VC12-63, NE / VSDH1 / VC4-2 / VC12-63}

[0219] As above, 63 VC12s are created on the 3rd to 31st timeslots of VC4.

[0220] The 47 VC12 trails created on the VC4 path with timeslot 32 are:

[0221] The first VC12 service with VC4 timeslot 32 is:

[0222] {NE / STM64-1 / VC4-32 / VC12-1, NE / VSDH1 / VC4-32 / VC12-1}

[0223] The second VC12 service with VC4 timeslot 32 is:

[0224] {NE / STM64-1 / VC4-32 / VC12-2, NE / VSDH1 / VC4-32 / VC12-2}

[0225] …

[0226] VC12 service No. 47 with VC4 timeslot 32:

[0227] {NE / STM64-1 / VC4-32 / VC12-47, NE / VSDH1 / VC4-32 / VC12-47}

[0228] As can be seen from the above example, according to the method provided in Example 1, in the scenario of this embodiment, only one single-station ODU2 and one STM64 SDH physical port need to be found to complete batch creation and routing of 2000 VC12 services.

[0229] Example 4:

[0230] Based on the method for batch creation of small-granularity services on a transport network provided in the above-mentioned embodiments 1 to 3, the present invention further provides a device for batch creation of small-granularity services on a transport network that can be used to implement the above-mentioned method, such as Figure 11 , is a schematic diagram of the device architecture of an embodiment of the present invention. The device for creating a batch of small-granularity services on a transport network in this embodiment includes one or more processors 11 and a memory 12. Figure 11 A processor 11 is taken as an example.

[0231] The processor 11 and the memory 12 may be connected via a bus or other means. Figure 11 The bus connection is taken as an example.

[0232] Memory 12, as a non-volatile computer-readable storage medium for the method for batch creation of small-granularity services on a transport network, may be used to store non-volatile software programs, non-volatile computer-executable programs, and modules, such as the method for batch creation of small-granularity services on a transport network in Examples 1 through 3. Processor 11 executes the non-volatile software programs, instructions, and modules stored in memory 12 to execute various functional applications and data processing of the apparatus for batch creation of small-granularity services on a transport network, thereby implementing the method for batch creation of small-granularity services on a transport network in Examples 1 through 3.

[0233] The memory 12 may include high-speed random access memory and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other non-volatile solid-state memory device. In some embodiments, the memory 12 may optionally include a memory remotely located relative to the processor 11, and such remote memory may be connected to the processor 11 via a network. Examples of such networks include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.

[0234] The program instructions / modules are stored in the memory 12. When executed by one or more processors 11, the method for batch creation of small-granularity services in the transport network described in the above embodiments 1 to 3 is executed. For example, the method described above is executed. Figure 1 The steps shown.

[0235] Those skilled in the art will understand that all or part of the steps in the various methods of the embodiments can be completed by instructing related hardware through a program, and the program can be stored in a computer-readable storage medium, which may include: read-only memory (ROM), random access memory (RAM), a disk or an optical disk, etc.

[0236] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions and improvements made within the spirit and principles of the present invention should be included in the scope of protection of the present invention.

Claims

1. A method for batch creation of small-granularity services in a transmission network, characterized in that: Specifically include: Calculate the number of large-granularity service layers required for each layer based on the number of small-granularity services, and select the large-granularity service with the least pathfinding times to create a bearer for the small-granularity service. Create corresponding large-granularity services based on their routing information, and then create all service layers required for small-granularity services from the bottom layer upwards. Create the required client layer services on each created service layer service, allocate the number of time slots for the client layer services on the logical ports of the service layer in the required order, and create all client layer services; The nested loop creates the client layer of each service layer until the client layer business is the small-grained business type that is ultimately required.

2. The method for batch creation of small-granularity services in a transmission network according to claim 1, characterized in that: The calculation of the number of required large-granularity service layers of each layer according to the number of small-granularity services specifically includes: The number of large-granule services at each layer is calculated based on the total bandwidth required for small-granule services, the maximum bandwidth of large-granule services, the maximum number of small-granule services that can be carried, and the large-granule service types corresponding to the small-granule services.

3. The method for batch creation of small-granularity services in a transmission network according to claim 1, characterized in that: For end-to-end services, all service layers required for small-granularity services are created from the bottom layer to the upper layer. When all small-granularity services are pure SDH services, the following are specifically included: Allocate VC4 timeslots sequentially on the SDH ports at both ends of the MS service source and sink, and create all required VC4 service layer large-granularity services based on consistent combination of source and sink VC4 timeslots. Then, as needed, the number of VC12 sub-timeslots is sequentially allocated on the VC4 ports at both the source and sink ends. The allocated VC12 timeslots are also combined in a one-to-one correspondence according to the timeslot consistency to create the number of VC12 services required.

4. The method for batch creation of small-granularity services in a transmission network according to claim 1, characterized in that: For end-to-end services, all service layers required for small-granularity services are created from the bottom layer to the upper layer. When the small-granularity service is partially a pure SDH service and partially carried on ODUk, the following are specifically included: Create a large-granularity SDH over ODUk service on the OCH port, create and bind the corresponding VSDH port on the ODUK source and sink ports, and then create the corresponding RS and MS services on the bound source and sink VSDH ports. Sequentially allocate VC4 sub-timeslots on the SDH ports and VSDH ports between the start and end nodes of a pure SDH segment and between the VSDH ports bound to the start and end nodes of an ODUk segment. Create all VC4 service layer services by combining VC4 timeslots consistently. Allocate VC4 timeslots sequentially between SDH ports and create VC4 server layer services. Allocate VC4 timeslots in sequence between the head and tail nodes of the ODUk segment of the bound VSDH ports and create VC4 server layer services. Allocate the number of VC12 sub-timeslots in the order required for each VC4 service layer service segment that has been created, and create all the VC12 service quantities by combining the VC4 time slots and VC12 time slots in a consistent and one-to-one correspondence.

5. The method for batch creation of small-granularity services in a transmission network according to claim 1, characterized in that: For end-to-end services, all service layers required for small-granularity services are created from the bottom layer to the upper layer. When all small-granularity services are carried on ODUk, the following are specifically included: Create ODUk large-granularity services for every two adjacent nodes on the path, create and bind corresponding VSDH ports to the ODUk service source and sink ports, and then create RS and MS services on the source and sink VSDH ports bound between every two adjacent nodes. Sequentially allocate VC4 timeslots on each MS service source and sink VSDH port, and create each VC4 server layer service segment based on the VC4 timeslot consistency. Then, allocate the required number of VC12 sub-timeslots on all newly created VC4 server layer source and sink VC4 ports, and create all VC12 services based on the one-to-one correspondence between VC4 timeslots and VC12 timeslots. Alternatively, create a large-granularity SDH over ODUk service from the initiator to the tail node of the small-granularity service, create and bind corresponding VSDH ports on the source and sink ports of the ODUk service, create corresponding RS services and MS services on the bound source and sink VSDH ports, then sequentially allocate VC4 timeslots on the source and sink VSDH ports of the MS service, and create all VC4 service layer services based on the consistency of VC4 timeslots. Then, allocate VC12 sub-timeslots on the source and sink VC4 ports of the VC4 service layer service in the required order, and create the required number of VC12 services based on the consistency and one-to-one correspondence of VC4 timeslots and VC12 timeslots.

6. The method for batch creation of small-granularity services in a transmission network according to claim 1, characterized in that: For single-station services, all service layers required for small-granularity services are created from the bottom layer to the upper layer. When all small-granularity services are pure SDH services, the specific steps include: Create single-station RS and MS large-granularity services on the two SDH ports for small-granularity services. Allocate VC4 timeslots sequentially on the MS service port and create single-station VC4 service layer large-granularity services. Select VC4 service layer services with the same VC4 timeslot on both ports, allocate the number of VC12 sub-timeslots in the required order, and create the required number of VC12 services by combining the VC4 timeslots and VC12 timeslots in a one-to-one correspondence.

7. The method for batch creation of small-granularity services in a transmission network according to claim 1, characterized in that: For single-station services, all service layers required for small-granularity services are created from the bottom layer to the upper layer. When the small-granularity service is partially a pure SDH service and partially carried on ODUk, the following are specifically included: Create single-station RS and MS large-granularity services on the SDH port, allocate VC4 timeslots in sequence on the MS service, and create single-station VC4 server layer large-granularity services; Create a single-station ODUk service layer large-granularity service on the OCh port, create and bind a VSDH port on the ODUK logical port, and create single-station RS and MS large-granularity services on the VSDH port. Allocate VC4 timeslots sequentially to each single-station MS service and create a single-station VC4 service layer large-granularity service. On the SDH port and VSDH port, select the VC4 server layer service with the same VC4 timeslot, allocate VC12 sub-timeslots in sequence, and finally create the required number of VC12 services by matching the VC4 timeslots with the VC12 timeslots one by one.

8. The method for batch creation of small-granularity services in a transmission network according to claim 1, characterized in that: For single-station services, all service layers required for small-granularity services are created from the bottom layer to the upper layer. When both ends of the small-granularity service are VSDH ports bound to ODUk, the following are specifically included: Create single-station ODUk large-granule services on the OCh ports at both ends of the service, create and bind corresponding VSDH ports on each ODUk port, create single-station RS and MS large-granule services on the two VSDHs, allocate VC4 sub-timeslots in sequence to each single-station MS service, and then create a single-station VC4 server layer service. According to the consistency of VC4 timeslots, select the VC4 service layer services on the two VSDH ports, allocate the number of VC12 sub-timeslots in sequence, and create the required number of VC12 services by combining the VC4 timeslots and VC12 timeslots in a one-to-one correspondence.

9. The method for batch creation of small-granularity services in a transmission network according to claim 1, characterized in that: The method of "until the large-granularity service time slot is fully occupied or the required number of small-granularity services is reached" specifically includes: For large-granularity services that require time slot allocation, each sub-time slot is allocated to each small-granularity client layer service in sequence until the large-granularity service time slot is full or the required number of small-granularity services is reached.

10. A device for batch creation of small-granularity services on a transmission network, characterized by: The method comprises at least one processor and a memory, wherein the at least one processor and the memory are connected via a data bus, and the memory stores instructions that can be executed by the at least one processor, and after being executed by the processor, the instructions are used to complete the method for batch creation of small-granularity services in a transport network according to any one of claims 1 to 9.

Images