WO2012000204A1

WO2012000204A1 - Method and system for assigning service board

Info

Publication number: WO2012000204A1
Application number: PCT/CN2010/074930
Authority: WO
Inventors: 张华�; 张朋波; 张涛; 王晓燕; 许丽华; 李非
Original assignee: 中兴通讯股份有限公司
Priority date: 2010-07-02
Filing date: 2010-07-02
Publication date: 2012-01-05

Abstract

A method for assigning service boards is provided in the present invention. The method includes steps: configuring required data models for a service to be processed in wave division network; according to the configured data models, carrying out a service layout and determining a route and wavelength for the service in wave division network; after completing the service layout, assigning corresponding service boards for nodes on the service route of the wave division network according to the configured physical equipment models. A system for assigning service boards is provided in the present invention too. The solution of the prior art is to assign the service boards according to the result of the service layout. This technical solution is manpower-consuming, time-consuming and error-prone, and even needs several adjustments time and time again. All these problems of the prior art can be solved by the method and system of the present invention.

Description

Method and system for allocating business boards

The present invention relates to the technical field of planning of a wavelength division network, and in particular to a method and system for allocating service boards. Background technique

In a WDM network with increasingly complex services, it is a very complicated process to allocate service boards to service planning results. The current practice is to manually assign devices (that is, service boards) after the route and wavelength assignment are completed, without considering the constraints of the device. However, due to the complexity of the WDM network and the service equipment, it may be possible to reverse the route and wavelength planned before the service after the device is manually allocated. As a result, the service planning result needs to be adjusted again. Doing so will cost a lot of manpower and time, and it is easy to make mistakes, and there may even be repeated adjustments. Summary of the invention

In view of the above, the main purpose of the present invention is to provide a method and a system for allocating service boards, so as to solve the current operation of allocating service boards for service planning results, which requires a lot of manpower and time, is prone to errors, and may even occur more. Repeated adjustments.

In order to achieve the above object, the technical solution of the present invention is achieved as follows:

The invention also provides a method for allocating a service board, the method comprising:

Configuring the required data model for the WDM network service to be processed;

Performing service planning according to the configured data model to determine the routing and wavelength of the WDM network service;

After the service planning is completed, the wavelength division network industry is configured according to the configured physical device model. The site on the service route is assigned the corresponding service board.

The data model required for configuring the WDM network service to be processed is specifically: determining whether the WDM network service to be processed is a cross service, and if the WDM network service is a non-cross service, The aggregation board model required for the non-crossover service configuration;

If the WDM network service is a cross-service, configure the cross-board model and the cross-backplane model required for the cross-service.

When the service of the WDM network is a non-cross service, the service plan is specifically: the multiple non-cross services of the same, the same, and the same aggregation mode, if the number of services of the multiple non-cross services is not If the sum of the service rates of the multiple non-interleaved services is not greater than the group path rate set in the aggregation board model, the multiple non-crossings are performed. The service is bound to a virtual service with the same path and the same wavelength.

When the service of the WDM network is a non-cross-service, the service plan further includes: performing secondary aggregation on the virtual service that is in the same segment, and the virtual service after the second aggregation is transmitted in the same wavelength.

When the WDM network service is a non-cross-service, the physical device model is configured to allocate a corresponding service card to the site on the WDM network service route, specifically:

Traversing each service in the WDM network, searching for services that are up or down or requiring relaying in each site, and reorganizing the found services according to directions and wavelengths to generate a directional traffic set according to directions;

Traversing the wavelength service set, determining a corresponding service access mode according to the route of the wavelength service, and generating the wavelength according to the configured aggregation board model and the physical device model, for each wavelength service in the set The service is on the service board of each site on the route.

When the WDM network service is a cross-service, the service plan is specifically:

Finding a route for each service in the cross-service, traversing the route Have idle wavelengths;

For each idle wavelength, according to the corresponding cross-board model, it is determined whether each of the cross-services on the service route configured with the cross-backplane model can pass the site model constraint check, and the site model constraints include: The path constraint and the cross constraint; if the check can be constrained by the site model, it is determined that the corresponding idle wavelength is available, otherwise, the other idle wavelengths are traversed until an available wavelength that satisfies the site model constraint check is obtained.

When the WDM network service is a cross-service, the service plan further includes: when all the idle wavelengths on the found route cannot pass the site model constraint check, continue to find other routes for the cross-service, and Find available wavelengths on the other routes that satisfy the site model constraint check.

When the WDM network service is a cross-service, the physical device model is configured to allocate a corresponding service card to the site on the WDM network service route, which is specifically:

Reading a cross-backboard model of the site configuration, and configuring a cross-type shelf of a specified type for each cross-backplane model;

The cross-board model of each cross-backplane model is cyclically read, and the corresponding single-board device is generated according to the service board configured on the cross-board model and the configured physical device model.

The present invention also provides a distribution system for a service board, the system comprising:

a data model configuration module, configured to configure a required data model for the WDM network service to be processed;

a service planning module, configured to perform service planning according to the configured data model, and determine a route and a wavelength of the wavelength division network service;

The service board allocation module is configured to allocate a corresponding service board to the site on the service of the WDM network service according to the configured physical device model after the service planning is completed.

The data model configuration module is further configured to: determine whether the WDM network service to be processed is a cross service, and when the WDM network service is a non-cross service, the non-cross service Configure the required aggregation board model. When the WDM network service is a cross-service, configure the required cross-board model and cross-backplane model for the cross-service.

The service planning module is further configured to: when the WDM network service is a non-cross service, the services of the multiple non-cross services for the multiple non-cross services of the same, the same, and the same aggregation mode When the number of the tributary ports is not greater than the number of the tributary ports set in the aggregation card model, and the sum of the service rates of the multiple non-crossing services is not greater than the group trajectory rate set in the aggregation board model, the multiple The non-cross-service is bound to a virtual service with the same path and the same wavelength.

The service planning module is further configured to perform two aggregations on the virtual services that are in the same segment, and the virtual services in the second aggregation are transmitted in the same wavelength.

The service board allocation module is further configured to: traverse each service in the wavelength division network, find a service that has up and down or need to be relayed in each station, and reorganize the found services according to directions and wavelengths, Generating a set of wavelength services by direction;

The service planning module is further configured to: when the WDM network service is a cross service, find a route for each service in the cross service, and traverse all idle wavelengths on the route;

The service planning module is further configured to: when all the idle wavelengths on the found route are unable to pass the site model constraint check, continue to find other routes for the cross service, and look up The available wavelengths on the other routes that satisfy the site model constraint check.

The service board allocation module is further configured to: read a cross backplane model configured by the site, configure a crossover subrack of a specified type for each cross backplane model; and cyclically read each cross backplane model The cross-board model is generated, and the corresponding single-board device is generated according to the service board configured in the cross-board model and the configured physical device model.

The method and system for allocating a service board provided by the present invention, by defining and configuring a related device model, can directly associate physical device constraints in the service planning process, and finally automatically configure a service board directly after the service planning is completed. device. The invention avoids the problem of a large amount of manpower and time, is prone to error, and even has repeated adjustments when the operation of the service board is allocated for the business planning result. DRAWINGS

1 is a flowchart of a method for allocating a service board according to the present invention;

2 is a flow chart of cross-sectional constraint checking of cross-services in the present invention;

3 is a flow chart of cross-service cross-constraint verification in the present invention;

4 is a schematic diagram of a network topology of a non-cross service according to an embodiment of the present invention;

FIG. 5 is a schematic diagram of a network topology of a cross service according to an embodiment of the present invention; FIG.

FIG. 6 is a schematic structural diagram of a distribution system of a service board according to the present invention. Detailed ways

The technical solutions of the present invention are further elaborated below in conjunction with the accompanying drawings and specific embodiments. The present invention configures four data models: a physical device model, a converged single-board model, a cross-board model, and a cross-backplane model, so that related device constraints can be directly associated in the business planning process, and finally automatically configured after the business planning is completed. Equipment such as business boards. The four data models are described separately below.

1. Physical device model: It mainly includes the device model of the service board and the cross subrack. The service board model encapsulates the service transmission board and represents a service transmission capability. It can include specific physical board devices or abstract single board devices (for example, in the research of single board devices, future hypotheses). The board device) meets the requirements of the planning software for single-board devices in various scenarios.

The attributes of the service board model include:

The board type indicates the type of the service board. For example, the Gigabit Ethernet Multiplex (GEM) type, the Optical Transmit Unit (OTU) type, and so on.

The service type of the service, which indicates the type of service that the service board supports for transmission, for example: Supports the synchronous transmission mode 16 (STM-16, Synchronous Transfer Module-16), STM-64 service;

The information about the slot, including the slot height and width of the service board, is used to facilitate drawing the device panel when the device is subsequently assigned.

The attributes of the cross subrack model include: Subrack type, which indicates the type of subrack device. The cross-rack provides a cross-backplane for cross-scheduling services when the cross-services pass through the service boards.

All physical device models can be provided by default in the form of a device library, or they can be customized and extended by separate tools.

2, the convergence of the single board model

For the non-interleaving services of different granules in the WDM network, in order to make full use of the network bandwidth and resources in the planning process, multiple low-rate services of the same origin and the same address need to be aggregated into one high-speed virtual service. A basic unit of business when routing and wavelength are allocated. In addition, the aggregated virtual services are re-aggregated (there is no requirement for homologous and homogeneous), which is called secondary aggregation.

To this end, the present invention defines a service aggregation board model to describe the access aggregation capability of the service, and to map different service board devices through the definition of the model, so that the configuration software can be more intelligently configured to process various services. Convergent boards, which are stipulated here: only homologous, homogeneous, and same The business of the poly-board model is allowed to come together. The model is used to display the mapping between the service cards of the different types of services and the service boards and the relay boards. This facilitates the automatic configuration of subsequent service boards.

The attributes of the aggregation board model include:

ID, the only symbol that represents the model;

Convergence business type, record the type of business that the model allows to aggregate (the business type can be one or more), that is, what type of business can use the model; the same business type can be set in different models to meet different needs ;

Group rate, group rate of the board model after service aggregation;

Branch rate, the number of services allowed to access at a specific rate, define constraints: number of tributaries X traffic rate ≤ group path rate;

Whether the identifier of the secondary aggregation is allowed to indicate whether the non-homologous and homogeneous services aggregated by the same aggregation board model can be re-aggregated by the model to save wavelength;

A service board and a trunk card, which are used to process the aggregation and service cards of the aggregation service, including board types and slots.

The aggregation board model can be provided by default in the form of a model library, or it can be customized and extended by a separate tool.

For the services on the network, you need to configure the aggregation card model before the planning, that is, the unified configuration of services of the same service type, so that all services of the same type can use a specific aggregation board model.

A single configuration of a single service, that is, configuring its aggregation board model for a single service according to actual needs.

3, cross veneer model

For the cross-services of different granules in the WDM network, in the planning process, in order to make full use of the network bandwidth and resources, a cross-board model of the service is established. Implemented by the definition of the model The access aggregation and encapsulation of the cross-services, and the definition of the support capabilities of the line-side boards, to support the abstraction of the real boards and the unknown boards, and to facilitate the planning of smarter configuration of the software to handle business orders of various services. board.

The properties of the cross-board model include:

ID, the only symbol that represents the model;

Cross-board type. This type indicates the processing service of the cross-board. It is divided into three types: customer side, line side, and customer side + line side.

Access service type, model attribute with client side attribute, record type of service allowed by the model (the type of service can be one or more), that is, what type of service can use the model, the same type can be defined in different In the model, it can meet different requirements. It also supports access of multiple service types. This attribute is applicable to the client-side board and the client-side + line-side board.

Rate of the backplane, the rate of the lower backplane of the cross-board;

Single-path group rate, model attribute with line-side attribute, indicates the single-way group intersection rate of the line-side board; Definition constraint: Number of group-ports X-way group-way rate ≤ backplane rate; This attribute is only applicable to the line side Single board, customer side + line side board;

Number of intersections, with model attributes on the line side, indicating the number of group intersections on the line side board; Definition Constraints: Number of group intersections X single way group rate ≤ backplane rate; This attribute is only applicable to line side boards, customer side + line side veneer;

Maximum number of tributaries, indicating the number of cross-services allowed to access, defining constraints: ∑ service rate ≤ backplane rate, and ∑ service number ≤ tributary port number; this attribute is only applicable to line side boards, customer side + line side orders Board

Service board model, which indicates the service board that processes the cross-service, including the board type and slot width.

The cross-board model can be provided by default in the form of a model library or by a separate tool. 4, cross backplane model

In the planning process, in order to reflect different cross-capacity constraints, the cross-capability constraints are achieved by setting different cross-backplane models. Through the definition of the cross-backplane model, in the planning process, according to the capacity constraints generated by the cross-board model supported by the cross-backplane model, the cross-service planning is provided to constrain the subsequent cross-subracks and services. Automatic configuration of the board.

The properties of the cross-backboard model include:

ID, the only symbol that represents the model;

Cross-grained, indicates the granularity of the cross-service scheduling cross-service, including the maximum granularity and the minimum granularity; the maximum granularity can be equal to the minimum granularity; when the granularity of a certain service is smaller than the minimum granularity, scheduling according to the minimum granularity; when the granularity of a certain service When the maximum granularity is greater than the maximum granularity, the service cannot be scheduled using the backplane model;

The subrack type indicates the type of the subrack where the cross backplane corresponding to the backplane model is located, so as to facilitate subsequent device configuration; the type is provided by the subrack model in the device library, and the subrack may be an existing device, or Is a custom abstract device to support subsequent devices;

The cross-capacity indicates the cross-capacity corresponding to the backplane model. During the service planning process, when the total number of scheduled services exceeds the cross-capacity, the scheduling fails.

Slot information, including the slot rate and the number. If the number of slots is determined during the planning process, the number of slots must be limited. The definition constraint: the rate of the cross traffic on the slot ≤ slot rate , ∑ (slot rate X slot number) ≤ cross capacity;

Cross-board model, which represents the cross-board model supported by the cross-backboard model. The abstract definition of a cross-device is realized by the combination of the cross-backboard model and the cross-board model.

The cross-backplane model can be provided by default in the form of a model library or by a separate tool.

On the basis of the above data model configuration, the distribution of a service board provided by the present invention is provided. The method, as shown in Figure 1, mainly includes the following steps:

Step 101: Determine whether the WDM network service to be processed is a cross service, if it is a non-cross service, perform step 102; if it is a cross service, perform step 106.

Step 102: Configure an aggregation board model, specify a unique identifier, a service type that supports aggregation, a group path rate, a number of branch ports, whether to perform secondary aggregation, and use the service of the model in the transmission process. Business boards and trunks.

Step 103: Specify a convergence board model for the specific service, so that the service board and the relay board of the service route site are automatically allocated after the planning is completed.

Step 104: Non-cross-service planning, determining routing and wavelength of the WDM network service.

If the service number N is not greater than the number of branches defined by the model, and the sum of the service rates is not greater than the group-defined group path rate, then these services are bound to the N-type service of the same, the same, and the same aggregation mode. A service can be bound to a virtual service as a planning unit, so that the N services can be transmitted using the same path and the same wavelength.

In addition, during the planning, for a virtual service A that is aggregated using the same aggregation card model, if there are other virtual services B that are in the same route as A (not required to be the same or the same as service A), The secondary aggregation flags defined in the respective aggregation models determine whether secondary aggregation can be performed; if the corresponding flag bits of both models are true, then A and B can be aggregated again, using the same wavelength transmission.

Step 105: Assign a corresponding service board to the site on the VB network service route according to the configured physical device model.

First, traverse the entire network service, find services that are up or down or need to be relayed in each site, reorganize these services according to direction and wavelength, and generate a set of wavelength services according to directions;

Then, traversing the wavelength service set, determining the service access mode (terminal access, relay access) according to the service routing information for each wavelength service; finding the aggregation board model of the service configuration, according to the aggregation board model Configured service boards and trunk boards, as defined in the device library. The device model is generated, and the corresponding board device is generated. If the terminal access mode is used, the corresponding service board is generated.

Step 106: Configure a cross-board model. In the model, first determine the type of the cross-board, and then specify the corresponding attributes according to the type of the cross-board.

Step 107: Configure a cross-backplane model. In the model, determine model-related attributes, and focus on specifying the cross-board model used by the cross-backplane model.

Step 108: Configure a cross-backplane type for the service site that needs to cross the service, and specify information about the specific cross-subrack used by the site.

Step 109: Cross-service planning, determining routing and wavelength of the WDM network service.

In the planning process, according to the planning rules, plan each business and execute:

9.1 Find a route for the service, which can be a work route, a protection route, or a recovery route.

9.2 traversing all the idle wavelengths of the route, and for each idle wavelength, combined with the relevant cross-board model, determining whether the service site configured with the cross-backplane model of the cross-service on the service route can pass the site model constraint check; For the constraint checking of the site model, there are two types of constraints, including: Up and down road constraints, cross-services at the source/sink site using a certain wavelength to complete the up and down; Cross-constraint, cross-service at the route site crossing one wavelength direction to another Wavelength direction. The flow of the upper and lower road constraint check is shown in Figure 2, which mainly includes the following steps:

Step 201: Obtain site information, and information such as the wavelength and direction of the cross-road service at the site.

Step 202: Determine whether the site is a cross-site, that is, whether the site is configured with a cross-backplane model. If the cross-plane model is configured on the site, it indicates that it is a cross-site, and step 203 is performed; otherwise, step 213 is performed.

Step 203: Determine whether the cross-service can go up and down through the uplink and the downlink, that is, determine whether the cross-service satisfies the constraint of the optical layer scheduling. If the optical layer scheduling constraint is met, step 204 is performed; otherwise, Go to step 213.

Step 204, traversing all the line side boards, determining whether the line side board includes the wavelength and direction of the cross service, if yes, indicating that the line side board is the line side board of the cross service, and then proceeds to step 208; Then, step 205 is performed.

Step 205, traversing all the line side boards, determining whether there is an idle group road on the line side board, if yes, setting the line side board as the line side board of the cross service, and then going to step 208; if not, then Go to step 206.

Steps 206 to 207, determining whether the line side board can be created according to the board cross-over model supported by the backplane and the backplane, and the slot information of the board and the backboard that have been set on the backplane. If the board is created, the cross-service is created. Line side board; otherwise, go to step 208.

Step 208, traversing all the customer side boards, determining whether there is a customer side board supporting the cross service up and down, if present, the customer side board is the customer side board of the cross service, and then going to step 211; if not, executing Step 209.

Steps 209-210: According to the board cross-over model supported by the backplane and the backplane, and the slot information of the board and the backplane that have been set on the backplane, it is determined whether the client sideboard can be created. If it can be created, the cross-service is created. Customer side panel; otherwise, go to step 213.

In step 211, the cross-service is obtained according to the cross-service, and the cross-service is determined to meet the cross-capacity constraint of the backplane. If the cross-capacity constraint is met, step 212 is performed; otherwise, step 213 is performed.

Step 212: According to the line side board, the customer side board, and the back board, set the cross-service service to and from the road, and return true (true), that is, the cross-service uplink and downlink constraint check is satisfied.

Step 213: Set the return value to false (false), that is, the cross-service link constraint check is not satisfied.

The process of cross-constraint verification is shown in Figure 3, which mainly includes the following steps:

Step 301, obtaining site information, and cross-service inflow <wavelength, direction> and outflow <wave Long, direction> and other information.

Step 302: Incoming cross-service inflow <wavelength, direction> and outflow <wavelength, direction>, and the through-service already existing at the station, determining whether the cross-service can be directly connected at the site, if it can be directly connected, performing step 314; otherwise, Go to step 303.

Step 303: Determine whether the site is a cross-site, that is, whether the site is configured with a cross-backplane model. If the cross-backplane model is configured on the site, it indicates that it is a cross-site, and then step 304 is performed; otherwise, step 315 is performed.

In step 304, it is determined whether the cross-service inflow <wavelength, direction> and outflow <wavelength, direction> can be up and down through the uplink and the downlink, that is, whether the cross-service is satisfied by the optical layer scheduling constraint. If the optical layer scheduling constraint is met, step 305 is performed. Otherwise, go to step 315.

Step 305, traversing all the line side boards, determining whether the line side board includes the cross-service inflow <wavelength, direction>, if yes, indicating that the line side board is a line side board of the cross service, and then proceeds to step 309. Otherwise, go to step 306.

Step 306: Traverse all the line side boards, determine whether there is an idle group road on the line side board, if yes, set it as one line side board of the cross service, and then go to step 309; otherwise, go to step 307.

Steps 307 to 308, determining whether the line side board can be created according to the board crossover model supported by the backplane and the backplane, and the slot information of the board and the backboard that have been set on the backplane. If yes, create one for the cross service. Line side board; otherwise, go to step 315.

Step 309, traversing all the line side boards, determining whether the line side board includes the cross service outflow <wavelength, direction>, if yes, indicating that the line side board is another line side board of the cross service, and then going to the step 313; Otherwise, go to step 310.

Step 310: Traverse all the line side boards, determine whether there is an idle group road on the line side board, if yes, set it as another line side board of the cross service, and then go to step 313; otherwise, go to step 311. Steps 311 to 312, based on the board crossover model supported by the backplane and the backplane, and the slot information of the board and the backplane that have been set on the backplane, determine whether the line side board can be created. If it can be created, create the cross service. Another line side panel; otherwise, go to step 315.

In step 313, the cross-service is obtained according to the cross-service, and the cross-service is determined to meet the cross-capacity constraint of the backplane. If the cross-capacity constraint is met, step 314 is performed; otherwise, step 315 is performed.

Step 314, according to the two line side boards and the back board, set the cross service crossover, and set the return value to true, that is, the cross service constraint check verification is satisfied.

Step 315, setting the return value to false, that is, the cross-service cross-constraint check is not satisfied.

9.3 If the idle wavelength is not passed through the site model constraint check, indicating that the wavelength is not available, return 9.2 and continue to traverse other idle wavelengths until an available wavelength is found that satisfies the site model constraints.

9.4 If all idle wavelengths on the service route cannot pass the constraint check of the site model, indicating that the service route is unavailable, you need to return to 9.1 to continue to find other service routes for the service.

9.5 If the service uses a certain route and an idle wavelength on the route to pass the site model constraint check, indicating that the wavelength, the route is available, the service plan is completed.

Step 110: Assign a corresponding service board to the site on the VB network service route according to the configured physical device model.

Specifically: Read the cross-backplane model of the site configuration, each model instance is configured with a specified type of cross-subrack; cyclically read the cross-board model under each cross-backplane model, and configure the service according to the cross-board model The board is combined with the physical device model defined by the device library to generate the corresponding single-board device.

The method for allocating the service boards in the following is further elaborated in conjunction with the specific embodiments. In the first embodiment of the present invention, a service board allocation operation when processing a non-cross service is described. Suppose there are three reconfigurable optical add/drop multiplexers (ROADMs in the network, Reconfigurable Optical Add-Drop Multiplexer) The service topology A, B, and C, the network topology is shown in Figure 4. The solid line in the figure indicates the inter-site fiber connection, and the dotted line with the arrow indicates the existence of services between the two sites. Among them, there are 8 non-interleaved Gigabit Ethernet (GE) services between the A and C sites.

The purpose of this embodiment is to enable eight GE services to be aggregated into one 10G service for co-wave transmission. The GEM board is used in the transmission process. In addition, the service needs to be relayed at the B site, and the service relay board uses the OTU single. board.

The specific processing includes the following steps:

Step 401: Create a convergence board model.

Create an aggregation board model for the target GE type service. The model parameters are set as follows: Model Name: GE10G

Number of tributaries: 8

Group rate: 10G

Business Type: GE

Business board: GEM

Relay board: OTU

It should be noted that if the aggregation board model of the corresponding function already exists in the model library, step 401 may be omitted. If the aggregation board model of the corresponding function does not exist in the model library, the newly created aggregation board may be added. Models are added to the model library for backup.

Step 402: Configure a convergence board model for the service.

Set the access aggregation models of the eight services to the GE10G model created in step 401. The aggregation board model of the service can be set in batches according to the service type. After the configuration is complete, all services of the same service type are designated as the access aggregation model.

Step 403, business planning.

Bind the service during planning: Since these 8 services are homogenous, homogeneous, and access aggregation The model, and the number of services is not greater than the number of tributaries defined by the model. The sum of the service rates is not greater than the group path rate defined by the model. Therefore, it can be bound as a virtual service as a planning unit, so that the eight services can be used. Same path, same wavelength transmission. By planning to set the route A-B-C for the virtual service, the wavelength λ1 is allocated.

Step 403, assigning a device.

First, traverse the entire network service, find services in the A, B, and C sites that have upper and lower or need to be relayed, reorganize these services according to direction and wavelength, and generate a set of wavelength services according to direction.

Then, traversing the wavelength service set, and determining the service access mode (terminal access, relay access) according to the service route (A→B→C) information for each wavelength service. In this embodiment, the service is at A, The C site is the terminal access mode, and the B site is the relay access mode. For each wavelength service, the aggregation card model of the service configuration is found, and the service card and the relay card configured in the aggregation card model are obtained. The physical device model defined in the device library is used to generate the corresponding single-board device. Specifically, the service is in the terminal access mode of the A and C sites, and the corresponding GEM service card is generated. The corresponding OTU trunk board is generated.

After the planning is completed, the board devices of each site are allocated as shown in Table 1 below:

In the second embodiment of the present invention, a service board allocation operation when processing a cross service is described. Assume that there are four ROADM sites A, B, C, and D in the network. The network topology is shown in Figure 5. The solid line in the figure indicates the inter-site fiber connection, and the dotted line with arrows indicates the existence of services between the two sites. There are two GE cross-cut services in the figure, A-C and A→D.

The specific processing includes the following steps: Step 501: Set a cross-board model.

Create a client-side cross-board model for GE-type cross-services. The parameters are as follows: Model Name: CH1

Slot width: 1

Board position: Customer side

Backplane speed: 40G

Number of tributaries: 32

Business Type: GE

Customer side business board: CH1

Create a line-side cross-board model for GE-type cross-services. The parameters are as follows: Model Name: L02

Slot width: 1

Board position: Line side

Backplane speed: 80G

Line rate: ODU2

Number of intersections: 8

Line side service board: L02

It should be noted that if the above model of the corresponding function already exists in the model library, step 501 may be omitted; if the above model of the corresponding function does not exist in the model library, the newly created model may be added to the model library for backup. .

Step 502, setting a cross backplane model.

Create a cross-backplane model for the site with the following parameters:

Model Name: 800G

Cross granularity: ODU0, ODUl, ODU2

Subrack type: X type (this type can be provided by the physical device model in the device library or Definition)

Cross capacity: 800G

10G slot number: 0

20G slot number: 0

Number of slots in 40G: 10

80G slot number: 5

Cross-board model: CH1, L02 (created in step 501 above)

It should be noted that if there is already a cross-backplane model corresponding to the function in the model library, step 502 may be omitted; if there is no cross-backboard model corresponding to the function in the model library, the newly created model may be added to the model. In the library to spare.

Step 503, setting a cross backplane model for each site.

Set the cross-backplane models of Sites A, B, C, and D to the 800G model created in step 502.

Step 504, business planning.

In the planning process, each business is planned in turn according to the planning rules. Specific: a. For business A→C

Find a working route A-B-C for service A→C, traverse all idle wavelengths (λ1~λ40) on the route; for idle wavelength λΐ, service A→C goes through the service at source and sink C sites Constraint, in the constraint verification process, according to the configuration model information, the device configuration information of the A and C sites is obtained: 1 X-type cross subrack, 1 customer side board CH1, 1 line side board L02; Route B sites can be directly connected and meet business cross constraints. Since the service is directly connected to the B site, it is not necessary to go up and down through the cross-backplane. Therefore, the B-site is not bound by the previously configured cross-backplane model, and the transmission of the service at the B-site does not require a separate device. At this point, the planning of service A→C is completed, routing A→B→C, wavelength λ1.

b, for business A→D Find a working route A-B-D for service A→D, traverse all idle wavelengths (λ1~λ40) on the route; for idle wavelength λΐ, service A→D goes through the service at source and destination D sites In the constraint check process, according to the configuration model information, the device configuration information of the A and D sites is obtained: one X-type cross subrack, one customer side board CH1, and one line side board L02. In addition, the service A-D can reuse the equipment configured in the service A-C planning at the A site, because both services are GE services, and there is no capacity constraint in the cross model of the A site configuration in the transmission process. . At the route B, it is found that the service A→C uses λΐ to pass to the C site. If the λΐ continues to be used, the two services must be moved up and down through the cross backplane at the defect. After the service is up and down, it can be cross-constrained by the service, which leads to three directions (A, C, D) at the site λ. According to the configuration model information, the device configuration information of the B site is: 3 line side boards L02. At this point, the service A→D planning is completed, routing A→B→D, wavelength λ1.

The reason why the wavelength λΐ is assigned to the service A→D in this embodiment is to better explain the impact of the related cross model on the business plan.

Step 505, assign a device.

First, read the cross-backplane model of the site configuration, and configure a specified type of cross-subrack for each model instance;

Then, the cross-board model of each cross-backplane model is cyclically read, and the corresponding single-board device is generated based on the service board configured in the cross-board model and the physical device model defined in the device library.

After the planning is completed, the site device allocation is as shown in Table 2 below: Station Cross capacity Board use

Subracks Boards Board Usage and Usage Cross Capacity

Two branches are used, respectively cm 2 ODU0

A X subrack 4 ODU0 access two GE services

L02 2 ODU0 uses a group intersection, corresponding Wavelength is 1 and direction is B

Used a group intersection, corresponding

L02 2 ODU0

The wavelength is 1 and the direction is A. A group intersection is used, corresponding

B X subrack 4 ODU0 L02 1 ODU0

The wavelength is 1 and the direction is C. A group intersection is used, corresponding

L02 1 ODU0

The wavelength is 1 and the direction is D. A branch is used, and cm 1 ODU0 is connected.

a GE business

C X subrack 2 ODU0

Used a group intersection, corresponding

L02 1 ODU0

The wavelength is 1 and the direction is B. A branch is used, and cm 1 ODU0 is connected.

a GE business

D X subrack 2 ODU0

Used a group intersection, corresponding

L02 1 ODU0

The wavelength is 1 and the direction is B. Table 2

In addition, corresponding to the method for allocating the service boards, the present invention further provides a service board distribution system. As shown in FIG. 6, the system includes: a data model configuration module 10, a service planning module 20, and a service board allocation. Module 30.

The data model configuration module 10 is configured to configure a required data model for the WDM network service to be processed. The service planning module 20 is configured to perform service planning according to the configured data model, and determine a route and a wavelength of the wavelength division network service. The service board allocation module 30 is configured to allocate a corresponding service board to the site on the VB network service route according to the configured physical device model after the service planning is completed. Preferably, the data model configuration module 10 is further configured to determine the wavelength division network to be processed If the service is a cross-service, configure the required aggregation board model for the non-cross-connection service when the WDM network service is a non-cross-service service. If the WDM network service is a cross-service, configure the cross-board required for the cross-service. Model and cross-backboard model.

When the WDM network service is a non-cross service, the service planning module 20 is further configured to: for the multiple non-cross services of the same, the same, and the same aggregation mode, the number of services in the multiple non-cross services is not greater than Binding the multiple non-cross services to one of the number of tributary ports set in the aggregation card model, and the sum of the service rates of the multiple non-interleaved services is not greater than the group path rate set in the aggregation board model. Use virtual services with the same path and the same wavelength. It can also be used to perform secondary aggregation on virtual services that have passed the same route, and the virtual services after secondary aggregation are transmitted in the same wavelength.

The service board allocation module 30 is further configured to: traverse each service in the wavelength division network, find services that are up or down or need to be relayed in each site, and reorganize the found services according to directions and wavelengths, and generate directions according to directions. The traversing of the wavelength service set; traversing the wavelength service set, determining the corresponding service access mode according to the route of the wavelength service for each wavelength service in the set, and generating the wavelength service route according to the configured aggregation board model and the physical device model Service boards of the sites.

When the WDM network service is a cross-service, the service planning module 20 is further configured to: find a route for each service in the cross-service, traverse all idle wavelengths on the route; for each idle wavelength, according to the corresponding Cross-board model, judging whether the cross-services on each service route can be verified by the site model constraint. The site model constraints include: up-and-down constraints and cross-constraints; if the site model can be constrained by the site model If it is determined, the corresponding idle wavelength is determined to be available. Otherwise, other idle wavelengths are traversed until an available wavelength that satisfies the site model constraint check is obtained. It can also be used to continue to find other routes for the cross service when all idle wavelengths on the found route cannot pass the site model constraint check, and find that the other routes meet the site model constraint check availability. wavelength. The service board allocation module 30 is further configured to: read a cross-backboard model of the site configuration, configure a cross-type subrack of the specified type for each cross-backboard model; and cyclically read the cross-boards of each cross-backboard model. The model, based on the service board configured with the cross-board model, and the configured physical device model, generates the corresponding single-board device.

The above is only the preferred embodiment of the present invention and is not intended to limit the scope of the present invention.

Claims

Claim

A method for allocating a service board, the method comprising:

After the service planning is completed, the corresponding service board is allocated to the site on the WDM network service route according to the configured physical device model.

The method for allocating a service board according to claim 1, wherein the data model required for configuring the wavelength division network service to be processed is specifically:

Determining whether the WDM network service to be processed is a cross-service, and if the WDM network service is a non-cross service, configuring a required aggregation board model for the non-cross service;

The method for allocating a service board according to claim 2, wherein when the wavelength division network service is a non-cross service, the service plan is specifically:

If the number of services of the multiple non-interleaving services is not greater than the number of branches set in the aggregation board model, and the multiple non-crossing services are the same, If the service rate of the cross-connection service is not greater than the group-wide rate set in the aggregation board model, the multiple non-cross-services are bound to one virtual service with the same path and the same wavelength.

The method for allocating a service board according to claim 3, wherein when the wavelength division network service is a non-cross service, the service plan further includes:

The secondary services of the same segment of the virtual service are aggregated, and the secondary services are transmitted at the same wavelength.

The method for allocating a service board according to claim 3 or 4, wherein When the WDM network service is a non-crossover service, the physical device model is configured to allocate a corresponding service card to the site on the WDM network service route, specifically:

The method for allocating a service board according to claim 2, wherein when the wavelength division network service is a cross service, the service plan is specifically:

Finding a route for each service in the cross service, traversing all idle wavelengths on the route;

The method for allocating a service board according to claim 6, wherein when the wavelength division network service is a cross service, the service plan further includes:

When all idle wavelengths on the found route cannot pass the site model constraint check, continue to find other routes for the cross service and look up the available wavelengths on the other routes that satisfy the site model constraint check.

The method for allocating a service board according to claim 6 or 7, wherein, when the WDM network service is a cross-service, the physical device model according to the configuration is used to route the WDM network service. The site is assigned the corresponding service board, which is specifically: Reading the cross-backplane model of the site configuration, and configuring a cross-type shelf of a specified type for each cross-backplane model;

A distribution system for a service board, characterized in that the system comprises:

The distribution system of the service board according to claim 9, wherein the data model configuration module is further configured to: determine whether the wavelength division network service to be processed is a cross service, in the wavelength division network When the service is a non-cross-service, the required aggregation board model is configured for the non-cross-service; when the WDM network service is a cross-service, the cross-board model and the cross-back are configured for the cross-service. Board model.

The service board of the service board according to claim 10, wherein the service planning module is further configured to: when the WDM network service is a non-cross service, for the same, the same, and the convergence list a plurality of non-interleaved services of the board model, where the number of services of the plurality of non-interleaved services is not greater than the number of tributary ports set in the aggregation card model, and the sum of service rates of the plurality of non-cross-over services is not greater than When the group rate is set in the aggregation board model, the multiple non-interleaving services are bound to one virtual service with the same path and the same wavelength.

The service board of the service board of claim 11, wherein the service planning module is further configured to perform secondary aggregation on the virtual service that is routed through the same segment, and use the virtual service after the second aggregation. Same wavelength transmission.

The service board allocation system according to claim 11 or 12, wherein the service board allocation module is further configured to traverse each service in the wavelength division network, and find that each station has Up and down or services that need to be relayed, and re-organize the found services according to direction and wavelength to generate a set of wavelength services according to directions;

The service board distribution system according to claim 10, wherein the service planning module is further configured to: for each service in the cross-service, when the WDM network service is a cross-service Searching for a route, traversing all the idle wavelengths on the route; for each idle wavelength, according to the corresponding cross-board model, determining whether the cross-service is configured on the service route for each site configured with the cross-backplane model Through the site model constraint check, the site model constraints include: an up-and-down path constraint and a cross-constraint; if the check can be constrained by the site model, it is determined that the corresponding idle wavelength is available, otherwise, the other idle wavelengths are continued to be traversed until obtained The available wavelengths that satisfy the site model constraint check.

The service board distribution system according to claim 14, wherein the service planning module is further configured to continue, when all idle wavelengths on the found route cannot pass the site model constraint check The cross-service looks for other routes and looks for available wavelengths on the other routes that satisfy the site model constraint check.

The service board distribution system according to claim 14 or 15, wherein the service board allocation module is further configured to: read a cross backplane model configured by the site, for each cross backplane The model is configured with a cross-subrack of a specified type. The cross-board model of each cross-backplane model is cyclically read, and the service board configured according to the cross-board model and the configured physical device model are generated. Board equipment.