WO2010102484A1

WO2010102484A1 - Label switch path processing method based upon link bundle

Info

Publication number: WO2010102484A1
Application number: PCT/CN2009/074057
Authority: WO
Inventors: 付锡华; 张新灵
Original assignee: 中兴通讯股份有限公司
Priority date: 2009-03-13
Filing date: 2009-09-21
Publication date: 2010-09-16

Abstract

A label switch path (LSP) processing method based upon link bundle is provided by the present invention, which includes: a router computing and wavelength assigning entity determines one or more bundled links and unbundled links through which the LSP passes; the router computing and wavelength assigning entity selects component links from every bundled link according to a first predetermined strategy; according to a second predetermined strategy, the router computing and wavelength assigning entity determines the wavelengths used by the selected component links and the unbundled links in the LSP for transmission, and determines the wavelength conversions used by the nodes through which the LSP passes. By means of the present invention, a solution of realizing the LSP establishment procedure in link bundle technology is provided, so that the gap in prior art is supplied.

Description

TECHNICAL FIELD The present invention relates to the field of optical network transmission, and relates to a method for processing a label switched path based on link bundling, and more particularly to a wavelength switched optical network (WRON) ) A label switching path processing method based on link bundling. BACKGROUND In a wavelength-switched optical network, multiple links may exist between a pair of nodes. Based on the requirements of route scalability, the multiple links may be required as an independent traffic engineering (Traffic Engineering). TE) Link flooding to Open Shortest Path First (OSPF) or Intermediate System to Intermediate System Routing Protocol (IS-IS) Furthermore, in the IETF standard RFC4201, the corresponding implementation mechanism is described and the concept of bundled link is introduced. When the link bundling technique is used, the traffic parameter information related to the bundle link is Will be flooded, but the information related to the component link will not be flooded, and the open shortest path with traffic engineering can be extended according to RFC4201 (Open Shortest) Path First Traffic Engineering, called OSPF-TE) and Resource Reserve Protocol Traffic Engineering (RSVP-TE) A wavelength division multiplexing (WDM) node has the ability to convert wavelengths, that is, one wavelength can be exchanged to another wavelength in different directions. However, the number of wavelength converters is limited. In this case, not every wavelength of each fiber can be switched to any other wavelength on any other fiber, so the constraint of wavelength conversion capability directly affects the potential wavelength connectivity in the wavelength-switched optical network. The wavelength that a fiber can support is pre-configured and is static attribute information. To change the attribute information, you need to upgrade the hardware. For each fiber, you only need to pre-configure once or through a routing protocol. Flooding once, because the wavelength supported by the fiber does not need to be changed frequently when the network is running. Nodes that perform path calculations can only perform at the TE link level if they do not know the available information of the wavelength (also called label). Path calculation, and coordinate wavelength selection through signaling protocol mechanism (that is, using a distributed wavelength assignment mechanism), unless some nodes on the optical channel are full wavelength conversion, it will result in lower processing efficiency and cause higher blocking. In general, the available information of the wavelength is especially important for the effective and accurate calculation of the wavelength channel when the wavelength conversion capability is limited or there is no wavelength conversion capability. Since the path computation entity also needs to know the connectivity constraint information, the wavelength conversion capability constraint information, and the wavelength conversion available information in the WDM node, five factors need to be considered in the calculation of the wavelength channel: node wavelength conversion capability constraint and wavelength conversion available information, node Wavelength connectivity constraint information, available wavelength information for each fiber, and wavelength constraint information. The Draft-ietf-ccamp-rwa-info draft of the Common Control and Management Plane (CCAMP) Working Group of the Internet Engineering Task Force (IETF) extends the Routing Protocol (OSPF-TE). The entity performing the routing and wavelength assignment (referred to as RWA) (for example: PCE-Path Computation Element) can know the wavelength constraint information of the TE link of the whole network, the available wavelength information, and the connectivity constraint of the node. , wavelength conversion capability constraints and wavelength conversion available information. However, after the link bundling technology is applied to the wavelength-switched optical network, the wavelength constraint information and available wavelength information of the link will be hidden, and the entity that performs RWA cannot meet the requirements of the full-network TE link wavelength constraint information and available wavelengths. The need for information. Unless the entity performing the RWA is able to collect this information. In a wavelength-switched optical network, the wavelength can be treated as a tag, not from the perspective of the client layer, which is considered to be a ΤΕ link or a member link. After the bundled links in WSON are bundled, the MPLS working group draft draft-ietf-mpls-explicit-resource-control-bundle of IETF will be extended and used for RFC3209, RFC3471 and RFC3473, jt匕You can explicitly specify <Bundle link, member link, label (wavelength)> by the extended ERO (Explicit Record Route) sub-object. If distributed wavelength assignment and distributed member link selection are used, each node on the connection is required to select member links and wavelengths. Of course, the label (wavelength) can be explicitly specified by the draft ERO object, and each node is responsible for member link selection during the connection establishment process. The draft draft-ietf-mpls-explicit-resource-control-bundle "4.1 Processing of Component Interface Identifier ERO Subobject" section gives the principle of explicit resource control using both tag and member links. It can be seen that in the absence of wavelength conversion capability or limited wavelength conversion capability, the connection establishment process using distributed wavelength allocation produces a large blockage. According to RFC4201, when the link bundling technique is used, only the bundle link can be flooded as a 链路 link in the routing protocol, and the information of the member link is not flooded in the routing protocol. In order to solve the wavelength conversion constraint problem in wavelength-switched optical networks, the existing WSON draft of the IETF's CCAMP working group (for example, draft-ietf-ccamp-rwa-info) specifies: by extending the routing protocol (OSPF-TE) (eg RFC3630), flooding the wavelength constraint information and available wavelength information of the link. However, after the link bundling technique is applied, this method contradicts the flooding requirements of the bundle link information mentioned in RFC4201. That is, the entity performing the RWA needs to know the wavelength constraint information and the wavelength available information of the TE link. However, after the link bundling technique is used, the wavelength constraint information and the wavelength available information of the TE link are hidden, which is in the wavelength exchange. After using the link bundling technology in the optical network, there are problems. In this way, in the bundle link technology, the existing technical solutions do not give a specific solution to how to obtain the hidden information and realize the establishment process of the LSP based on the link bundling technology in the wavelength-switched optical network. Program. SUMMARY OF THE INVENTION The present invention has been made in view of the problems in the related art in how to implement the LSP establishment process in the bundle link technology. To this end, the main object of the present invention is to provide a wavelength switched optical network (WSON). A link bundle path processing method based on link bundling to solve one of the above problems. According to an aspect of the present invention, a link bundle processing method based on link bundling is provided. A link bundle-based label switched path processing method according to the present invention includes: a route calculation and a wavelength assignment entity determining one or more bundle links and a non-bundle link via which an LSP passes; a route calculation and a wavelength assignment entity according to a first predetermined policy, selecting a member link from each bundle link; the route calculation and the wavelength assignment entity determine that the selected member link and the non-bundled link are used in the LSP according to the second predetermined policy The wavelength of the transmission and the wavelength conversion used by the node through which the LSP passes. Optionally, the method further includes: the route calculation and the wavelength assignment entity knowing in advance the link bundling information in all the bundle links for supporting route calculation and wavelength assignment, wherein the link bundling information comprises: bundling The wavelength constraint information of the link and the wavelength available information of the bundle link. Preferably, the route calculation and the wavelength assignment entity obtain the wavelength constraint information of the bundle link by calculating the wavelength constraint information of all member links in the bundle link, wherein the bundle constraint information of the bundle link refers to: bundle The union of all wavelength constraint information supported by all member links in the link. Alternatively, the route calculation and wavelength assignment entity may obtain wavelength available information of the bundle link by calculating wavelength available information of all member links in the bundle link, wherein the wavelength available information of the bundle link refers to : the union of the available wavelengths of all member links in the bundle link; and, when one wavelength is available on multiple member links of the bundle link, the number of available wavelengths in the bundle link is multiple members The sum of the number of available wavelengths for this link. Preferably, in the label switching path establishment and teardown process, when the available wavelengths supported by the member links in the bundle link through which the label switching path passes are occupied, the occupied wavelengths are concentrated from all available wavelengths. Removing, and reducing the number of wavelengths 被 occupied by the corresponding wavelength available in the bundle link; adding the occupied wavelength to all wavelengths in the case of the occupied wavelength end occupancy, and The number of wavelengths occupied by the corresponding wavelength in the bundle link is increased; and, when the available wavelength information of the member links in the bundle link changes, the wavelength available information of the bundle link is recalculated, and The result of the flooding calculation, wherein the calculation result is a union of the available information of the link wavelengths of all members. Preferably, when the member link wavelength constraint information in the bundle link is changed, the method further includes: recalculating the wavelength constraint information of the bundle link, wherein the calculation result is still all member link wavelength constraint information The union of; the flooding recalculated wavelength constraint information. Preferably, in the method, the link bundling information needs to be flooded, and if the link bundling information changes, the changed link bundling information is re-flooded. In this method, the manner in which the link bundling information for supporting route calculation and wavelength assignment in all bundle links is known includes one of the following: path calculation and link bundling obtained by the wavelength assignment entity in a pre-configured manner Information; each node sends its own link bundling information to the path computation and wavelength assignment entity, wherein each node reconfigures or transmits the changed link bundling information when the link bundling information changes. Optionally, the method may further include: the route calculation and the wavelength assignment entity pre-obtaining parameter information of all member links, where the parameter information includes: all member links included in each bundle link, each member link Supported wavelength constraint information and wavelength available information. Preferably, the route calculation and the wavelength assignment entity acquire parameter information of each node in advance, where the parameter information includes at least one of the following: between each bundle link in the node and other bundle links Connectivity constraint information, wavelength conversion capability constraint information, wavelength conversion available information; connectivity constraint information between each bundle link and non-bundle link, wavelength conversion capability constraint information, wavelength conversion available information; Connectivity constraint information, wavelength conversion capability constraint information, and wavelength conversion available information between bundled links. Preferably, obtaining parameter information of each node comprises: a route calculation and a wavelength assignment entity calculating a member link between all member links and non-bundle links in the bundle link and other bundle links Connectivity constraint information, wavelength conversion capability constraint information, wavelength conversion available information, connectivity constraint information between the bundle link and other bundle links, and non-bundled links, wavelength conversion Capacity constraint information, wavelength conversion available information; wherein connectivity constraint information between the bundle link and the non-bundle link, wavelength conversion capability constraint information, and wavelength conversion available information are all member links in the bundle link Integration of connectivity constraint information, wavelength conversion capability constraint information, and wavelength conversion available information with the non-bundled link; connectivity constraint information between bundle links, wavelength conversion capability constraint information, and wavelength conversion available Information is connectivity constraint information, wavelength conversion capability constraint information, and wavelength conversion available information between all member links in these bundle links. And the wavelength conversion between the two wavelength pairs in the bundle link and other links (including other non-bundled links and member links in other bundle links) When both are available, the number of wavelengths available for the wavelength conversion between the bundle link and other links (including other non-bundled links and bundle links) is all member links and other links in the bundle link. The sum of the wavelength conversion available numbers between links (including other non-bundled links and member links in other bundle links). Preferably, the route calculation and the wavelength assignment entity obtain the parameter information of each node, and the path calculation and the wavelength assignment entity may obtain the parameter information of the node in a pre-configured manner, or may send the parameters of the node to the path calculation and each node. When the wavelength assignment entity, and the parameter information of the node changes, it must be able to be reconfigured or sent. Preferably, the method may further comprise: the available wavelength conversion capability between the member links in the bundle link and other links (including member links in other bundle links and other non-bundle links) is After occupancy or release, the available wavelength conversion capability information between the corresponding bundle link and other links (including other bundle links and other non-bundled links) must be recalculated and the result is still bundled The wavelength conversion of all member links in the link with other links (including member links in other non-bundled links and other bundle links) is a combination of information available and needs to be re-broadcast. Preferably, the foregoing first predetermined policy may include one of: randomly selecting a member link in the bundle link; Sorting all available member links in the bundled link according to a predetermined policy, selecting a member link at a predetermined position after sorting; according to the number of times the member links in the bundle link are used, from the available member links Select the member link that has been used the most; select member links from the bundle link based on network load. Preferably, the second predetermined policy may include one of: performing random selection in available wavelengths of the member links; sorting all available wavelengths of the member links according to a predetermined policy, and selecting wavelengths of the predetermined positions after sorting; The number of times the wavelength in the link has been used, from the available wavelengths, the wavelength that has been used the most; the network wavelength is selected from the available wavelengths of the member links. Optionally, the method can be applied to the following architectures combining routing calculation, wavelength allocation, and member link selection: centralized routing calculation + centralized wavelength allocation + centralized member link selection; centralized Route calculation + centralized wavelength assignment + distributed member link selection; centralized routing calculation + distributed wavelength assignment + centralized member link selection centralized routing calculation + distributed wavelength assignment + distributed Member link selection; distributed route calculation + distributed wavelength assignment + distributed member link selection. Moreover, the method may further include: before the label switching path is established, both the route calculation and the wavelength assignment entity must obtain the wavelength constraint information and the wavelength available information of the bundle link in advance, between the internal bundle links of the node, and the non-bundle Connectivity constraint information between the bundle links and between the bundled links and the non-bundled links, wavelength conversion capability constraint information, and wavelength conversion available information. With the above at least one technical solution of the present invention, a solution for implementing a label switching path (Label Switch Path) is established in the bundle link technology, which fills the existing The gap in technology. The drawings are intended to provide a further understanding of the invention, and are intended to be a part of the description of the invention. In the drawings: FIG. 1 is a flowchart of a method for processing a label-switched path based on a link bundle according to an embodiment of the present invention; FIG. 2 is a schematic diagram of a scenario of a WDM node according to an embodiment of the present invention; Schematic diagram of the extension of the routing protocol (OSPF-TE/IS-IS) by draft-ietf-ccamp-rwa-info; FIG. 4 is a schematic diagram of the specification of the traffic parameters of the bundle link in RFC4201 in the prior art; FIG. 6 is a schematic diagram of a format of wavelength available information of a bundle link according to an embodiment of the present invention; FIG. 7 is a topology of a WSON network using link bundling technology; FIG. 8 is a schematic diagram showing the topology of the WSON network obtained by the path calculation and the wavelength assignment entity when the wavelength constraint information and the wavelength available information are used as the traffic parameters of the bundle link; FIG. 9 is a distributed wavelength allocation and distribution. Schematic diagram of a label switched path signaling setup procedure for member link selection. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENT After the introduction of the bundle link technology in a wavelength-switched optical network, a specific solution is not provided for the label switching path (LSP) establishment process, and, for distributed wavelength assignment Each node on the connection is responsible for the selection of member links and wavelength (label) allocation. However, there are no wavelength conversion or limited wavelength conversion constraints in the wavelength-switched optical network. Compared with the connection establishment of controlling TDM services, there are resources. (Bandwidth) competition, there is also a tag (wavelength) competition, which will result in higher blocking, although the Crankback mechanism can solve such problems. However, it also leads to frequent backtracking of signaling and inefficiency. Based on this, the object of the present invention is to apply the link bundling technology to a wavelength-switched optical network, and propose an architecture combining member link selection, wavelength assignment and route calculation, and implement a routing protocol (OSPF). -TE) A solution to solve the problem of link bundling in wavelength-switched optical networks. This solution maintains the advantages of the RFC4201 link bundling technology and solves the problem of beam-switched optical network link bundling. The embodiments in the present application and the features in the embodiments may be combined with each other without conflict. The preferred embodiments of the present invention are described in the following with reference to the accompanying drawings, which are intended to illustrate and illustrate the invention. According to an embodiment of the invention, a link-switching path processing method based on link bundling in a wavelength switched optical network (WSON) is provided. 1 is a flowchart of a method for processing a label-switched path based on a link bundle according to an embodiment of the present invention. As shown in FIG. 1, the method includes the following steps: Step S102: A route calculation and a wavelength assignment entity determine a path through which an LSP passes. One or more bundle links and non-bundle links; Step S104, the route calculation and wavelength assignment entity selects the member links from each bundle link according to the first predetermined policy; Step S106, route calculation And the wavelength assignment entity determines, according to the second predetermined policy, the wavelength of each of the selected member links and non-bundled links used for transmission in the LSP and the wavelength conversion used by the node through which the LSP passes. The above steps will be described in detail below.

(1) Step S102: The route calculation and the wavelength assignment entity need to know in advance the link bundling information for supporting the route calculation and the wavelength assignment in all the bundle links before calculating the route, where the link bundling information includes: The wavelength constraint information of the bundle link, the wavelength available information of the bundle link, in particular, the route calculation and the wavelength assignment entity can obtain the chain by routing 10 (OSPF-TE or IS-IS-TE) Road bundle information. The wavelength constraint information and the wavelength available information of the non-bundled link are obtained by the prior art method. The route calculation and the wavelength assignment entity obtain the wavelength constraint information of the bundle link by calculating the wavelength constraint information of all the member links in the bundle link, where the wavelength constraint information of the bundle link refers to: the bundle chain The union of all wavelength constraint information supported by all member links in the path. That is to say, the wavelength constraint information of the bundle link is a union of all member link wavelength constraint information, and when a wavelength is supported in at least one member link, the bundle link can support the wavelength. The route calculation and wavelength assignment entity obtains the wavelength available information of the bundle link by calculating the wavelength available information of all member links in the bundle link, wherein the wavelength available information of the bundle link refers to: bundle link The union of available wavelengths for all member links in . And, when one wavelength is available for multiple member links, the available number of wavelengths of the bundle link is the sum of the available numbers of the wavelengths of all member links. During the label switching path establishment and teardown process, when the available wavelengths supported by the member links in the bundle link through which the label switching path passes are occupied, the occupied wavelengths are collectively removed from the sum of all available wavelengths. The corresponding number of wavelengths in the bundle link is reduced by a corresponding number, and in the case where the wavelength ends, the wavelength is added to all wavelengths and concentrated, and the corresponding number of wavelengths in the bundle link is increased by a corresponding number. When the available wavelength information of the member link in the bundle link changes, then the wavelength available information of the bundle link needs to be recalculated, and the calculation result is still the union of the available information of all member link wavelengths, and the bundle The wavelength available information of the bundle link needs to be re-broadcast. When the member link wavelength constraint information in the bundle link changes, the wavelength constraint information of the bundle link needs to be recalculated, and the calculation result is still a union of all member link wavelength constraint information, and the bundle is The wavelength constraint information of the link needs to be broadcast again (ie, flooding above). The link bundle information is flooded by a routing protocol (OSPF-TE or IS-IS-TE), and any information related to the member link in the bundle link cannot be flooded. If it changes, it needs to be The changed link bundle information is again flooded. The path calculation and the wavelength assignment entity may obtain the link bundling information obtained in a pre-configured manner (for example, configuring the link bundling information into the path calculation and the wavelength assignment entity through the management plane), or each node may have its own The link bundle information is sent to the path calculation and the wavelength assignment entity, and when the link bundle information changes, the changed link bundle information needs to be re-enabled. Configured or sent. When centralized routing calculation, centralized wavelength allocation, and centralized or distributed member link selection, the route calculation and wavelength assignment entities need to know the parameter information of all member links in advance before the label switching path is established. The parameter information includes: all member links included in each bundle link, wavelength constraint information supported by each member link, and wavelength available information. If the route calculation and the wavelength assignment entity have to obtain these parameter information through a routing protocol, then There is no need to use link bundling techniques. The path calculation and the wavelength assignment entity may also obtain the link bundling information obtained by the pre-configured manner (for example, configuring the information into the entity through the management plane), or may send the link bundling information of each node to the path. The calculation and wavelength assignment entities, and when the link bundle information changes, must be reconfigurable or sent. Before calculating the route, the route calculation and the wavelength assignment entity need to obtain the parameter information of each node in advance. The parameter information includes: After the link bundling technology is used, each bundle link and other links in the node (including Connectivity constraint information between bundled links and non-bundled links), non-bundled links, wavelength conversion capability constraint information, wavelength conversion available information. The route calculation and the wavelength assignment entity can obtain the above parameter information through a routing protocol (OSPF-TE or IS-IS-TE), and can also obtain link bundle information obtained by a pre-configured manner (for example, configuring information through the management plane to In this entity, it is also possible that each node sends its parameter information to the path calculation and wavelength assignment entity, and when the parameter information of the node changes, it must be able to be reconfigured or sent. After the available wavelength conversion capability between the member links in the bundle link and other links (including member links in other bundle links and other non-bundle links) is occupied or released, the corresponding bundle The available wavelength conversion capability information between the link and other links (including other bundle links and other non-bundled links) can be calculated, and the result is still all member links and other links in the bundle link. The wavelength conversion available information (including other non-bundled links and member links in other bundle links) is aggregated and needs to be re-broadcast. Before the label switching path is established, the route calculation and wavelength assignment entity must obtain the following information in advance: wavelength constraint information of the bundle link and wavelength available information, between the bundle links inside the node, and between the bundle links Interconnection constraint information between the bundled link and the non-bundled link, wavelength conversion capability constraint information, and wavelength conversion available information. The method shown in Figure 1 can be applied to the following four combinations of route calculation, wavelength assignment and member link selection:

1. Centralized route calculation + centralized wavelength assignment + centralized member link selection;

2, centralized routing calculation + centralized wavelength allocation + distributed member link selection; 3, centralized routing calculation + distributed wavelength allocation + centralized member link selection;

4. Centralized route calculation + distributed wavelength assignment + distributed member link selection;

5. Distributed route calculation + distributed wavelength assignment + distributed member link selection. When using any of the above architectures, the route calculation and the wavelength assignment entity must obtain the wavelength constraint information and the wavelength available information of the bundle link before the label switching path is established, and the non-bundling between the internal bundle links of the nodes. Connectivity constraint information between the links and between the bundled links and the non-bundled links, wavelength conversion capability constraint information, and wavelength conversion available information. The route calculation and wavelength assignment entity needs to know the parameter information of all bundle links before determining one or more bundle links and non-bundle links through which the LSP passes, the parameter information including: each bundle link The wavelength constraint information and the wavelength available information of the non-bundled link, and the connectivity constraint information between the non-bundled links, the bundled link and the non-bundled link between the internal bundle links , wavelength conversion capability constraint information and wavelength conversion available information. After the routing calculation and the wavelength assignment entity learn the parameter information of all the bundle links, when establishing an LSP link, one or more bundle links through which the LSP passes may be determined according to the parameter information. The parameter information is connected to different member links of the same node through different interfaces. The interfaces have different connectivity. For example, a typical WDM node as shown in FIG. 2, the WDM node is configured by a wavelength conversion module (Wavelength Converter). It consists of a multiplexing/demultiplexing module (Multix/De Multiplex) and a wavelength switching module (Wavelength Switch). In an 80-wave system, each fiber contains 80 wavelengths. Due to the limitations of the wavelength conversion module, not every wavelength on each fiber can be exchanged to any wavelength on any fiber. Set up the following scenario 1: Fiber 1 is connected to Fiber 4, Fiber 2 is connected to Fiber 6 , and Fiber 3 is connected to Fiber 5. Fiber 1 wavelength lambda 1 is 3⁄4 enough to convert wavelengths on Fiber 4 to lambda 2, lambda 3 and lambda 4; Fiber 1 wavelength lambda 2 is 3⁄4 enough to convert wavelengths on Fiber 4 to lambda 7 and lambda 8. The other wavelengths on Fiber 1 can only be exchanged to the same wavelength on Fiber 4 .

The wavelength of the Fiber 2 lambda 1 is 3⁄4 enough to exchange the wavelengths on the Fiber 6 lambda 4 and lambda 5. The other wavelengths on the fiber Fiber 2 can only be exchanged to the same wavelength on the fiber Fiber 6.

Fiber 3 wavelength lambda 3 is 3⁄4 enough to convert wavelengths on Fiber 5 to lambda 7 and lambda 8; Fiber 3 wavelength lambda 1 is 3⁄4 enough to convert wavelengths on Fiber 5 to lambda 5 and lambda 6, fiber optic Fiber 3 can only be converted on other wavelengths To the same wavelength on fiber optic Fiber 5. The connectivity information in the WDM node is as follows: [Fiber 1—>Fiber 4]

[Fiber 2—>Fiber 6]

[Fiber 3— >Fiber 5] The wavelength conversion capability constraint information in this WDM node is as follows:

[Fiber 1: lambda 1 > Fiber 4: lambda 2 , lambda 3 , lambda 4] [Fiber 1 : lambda 2 > Fiber 4: lambda 7 , lambda 8]

[Fiber 2: lambda 1 > Fiber 6: lambda 4 , lambda 5]

[Fiber 3: lambda 1 > Fiber 5: lambda 5 , lambda 6]

[Fiber 3: lambda 3 > Fiber 5: lambda 7 , lambda 8] The available wavelength conversion information for this WDM node is as follows: [Fiber 1: lambda 1 > Fiber 4: lambda 2 , lambda 3 , lambda 4]

[Fiber 1 : lambda 2 > Fiber 4: lambda 7 , lambda 8]

[Fiber 2: lambda 1 > Fiber 6: lambda 4 , lambda 5]

[Fiber 3: lambda 1 > Fiber 5: lambda 5 , lambda 6] [Fiber 3: lambda 3 > Fiber 5: lambda 7 , lambda 8] According to RFC4201, only the same Link Type, Traffic Engineering metric, Resource Class, and the same pair of LSRs ( Label Switch Router) The member links between them can be bundled together. Although the above-mentioned fibers have different connectivity, they can also be bundled into a bundle link, but the connectivity constraint information and wavelength conversion capability between bundle links, bundle links and non-bundled links. Constraint information and wavelength conversion available information will be affected. After the link is bundled, the connectivity information constraint information, the wavelength conversion capability constraint information, and the wavelength conversion available information in the node must be summarized. The following scenario 1 is used as an example to describe the use of the link bundling technique. How to calculate a summary of this information ( Summary ). Scenario 2: The bundle bundles Fiber 1, Fiber 2, and Fiber 3 into one TE link.

(Link 1), the path computation entity needs (such as PCE) to know the connectivity of Link 1 to Fiber 4, Fiber 5, and Fiber 6 in advance. Fiber Optic Fiber 1 and Fiber 4, Fiber 2 and Fiber 6, Fiber 3 and Fiber 5 connectivity information should not be flooded, but it is not excluded that path computation entities can obtain this information through other paths. The connectivity information between the bundle link and the non-bundle link, the wavelength conversion capability constraint information, and the wavelength conversion available information should be connectivity information between the member link and the non-bundle link in the bundle link. , the wavelength conversion capability constraint information and the union of the wavelength conversion available information ( Union ). After bundle binding, the path computation entity (such as PCE) needs to know that the node's information becomes: The connectivity information in the WDM node is as follows: [Link 1— >Fiber 4]

[Link 1— >Fiber 5] [Link 1— >Fiber 6] The wavelength conversion capability constraint information in this WDM node is as follows:

[Link 1: lambda 1 > Fiber 4: lambda 2 , lambda 3 , lambda 4] [Link 1 : lambda 2 > Fiber 4: lambda 7 , lambda 8]

[Link 1 : lambda 1 > Fiber 6: lambda 4 , lambda 5]

[Link 1 : lambda 3 > Fiber 5: lambda 7 , lambda 8] [Link 1 : lambda 1 -- > Fiber 5: lambda 5 , lambda 6] The available wavelength conversion information for this WDM node is as follows:

[Link 1: lambda 1 - > Fiber 4: lambda 2 , lambda 3 , lambda 4]

[Link 1 : lambda 2 -- > Fiber 4: lambda 7 , lambda 8]

[Link 1.'lambda 1 - > Fiber 6.'lambda 4, lambda 5]

[Link 1 : lambda 3 -- > Fiber 5: lambda 7 , lambda 8]

[Link 1 : lambda 1 -- > Fiber 5: lambda 5 , lambda 6] Scenario 3: 光纤Fiber Fiber 5 and Fiber 6 are further bundled to form a bundle link Link, then the path computation entity (such as PCE) needs to know The information of the node becomes: The connectivity in the WDM node is as follows:

[Link 1— >Fiber 4]

[Link 1— >Link 2]

The wavelength conversion capability constraint information in the WDM node is as follows:

[Link 1: lambda 1 - > Fiber 4: lambda 2 , lambda 3 , lambda 4]

[Link 1 : lambda 2 -- > Fiber 4: lambda 7 , lambda 8]

[Link 1 : lambda 1 -- > Link 2: lambda 4 , lambda 5 , lambda 6]

[Link 1 : lambda 3 -- > Link 2: lambda 7 , lambda 8] Node The available wavelength conversion information for Link 1 in WDM is as follows:

[Link 1: lambda 1 - > Fiber 4: lambda 2 , lambda 3 , lambda 4]

[Link 1 : lambda 2 -- > Fiber 4: lambda 7 , lambda 8]

[Link 1 : lambda 1 -- > Link 2: lambda 4 , lambda 6]

[Link 1 : lambda 1— -> Link 2: lambda 5 , lambda 5] (two wavelengths 4 for ability to change use)

[Link 1 : lambda 3 > Link 2: lambda 7 , lambda 8] Scenario 4: A wavelength switching path is supported through the fibers Fiber 3 and Fiber 5, and the wavelength conversion between lambda 1 and lambda 5 is used. Then the fiber connectivity constraint information and the wavelength conversion capability constraint information will remain unchanged; the wavelength conversion available information will change. There are two wavelength conversion capabilities between lambda 1 and lambda 5, which will now be reduced to one. Then the path computation entity (such as PCE) needs to know the following information:

[Link 1: lambda 1 > Fiber 4: lambda 2 , lambda 3 , lambda 4]

[Link 1 : lambda 2 > Fiber 4: lambda 7 , lambda 8] [Link 1 : lambda 1 > Link 2: lambda 4 , lambda 6]

[Link 1 :lambda 1— -> Link 2:lambda 5] (only one wavelength conversion capability left)

[Link 1: lambda 3 > Link 2: lambda 7 , lambda 8] It should be noted that the path calculation and wavelength assignment entities can obtain the above parameter information in a pre-configured manner (for example, configuring information to the entity through the management plane) The node may send the foregoing parameter information to the path calculation and the wavelength assignment entity, and the path calculation and the wavelength assignment entity may also obtain the parameter information by using a routing protocol (for example, the node uses the prior art routing protocol to the foregoing parameter) Information is flooded). Another example of parameter information is: 光纤Fibre Fiber 1 supports wavelengths lambda 1 , lambda 2 , lambda 3 , lambda 4 , lambda 5 , lambda 8 , lambda 9 , lambda 10 , lambda 11 ; Fiber 2 supports wavelength lambda 4 , lambda 5 , lambda 6, lambda 9, lambda 10, lambda 11, lambda 12. The wavelength constraint information and wavelength available information for Fiber 1 and Fiber 2 are as follows: Wavelength Constraint Information:

Fiber 1: [lambda 1 -lambda 5] , [lambda 8-lambda 11]

Fiber 2: [lambda 4-lambda 6] , [lambda 9-lambda 12] Wavelength available information:

Fiber 1: [lambda 1 -lambda 5] , [lambda 8-lambda 11]

Fiber 2: [lambda 4-lambda 6] , [lambda 9-lambda 12] When the two fibers are bundled into one link, such as Link 1, the wavelength constraint information and wavelength available information of the bundle link are as follows Show: Wavelength constraint information:

Linkl: [lambda 1 -lambda 6] , [lambda 8-lambda 12] Wavelength available information:

Linkl: lambda 1 -lambda 3]

Linkl: lambda 4, lambda 4) (Note: two lambda 4 are available)

Linkl: lambda 5 , lambda 5) (Note: two lambda 5 are available)

Linkl: lambda 6-lambda 8]

Linkl: lambda 9 , lambda 9) (Note: two lambda 9 are available)

Linkl: lambda 10-lambda 12] When a wavelength switching path uses the wavelength 1 of lamb 1 and lambda 5, the available wavelength of the member link changes, which causes the available wavelength of the bundle link to change. The available wavelength information should be recalculated. Therefore, only one of the available lambda 5 and lambda 4 wavelengths of the bundle link is left. The latest wavelength available information needs to be flooded again. If a member link in the bundle link fails (for example, fiber breakage), the wavelength available information of the bundle link should have to eliminate the wavelength available information of the failed member link. When all member links of the bundle link fail, the bundle link must no longer flood out. In addition, in the link bundling technology, when the link bundling information of each bundle link is flooded, the bundle link wavelength constraint information and the wavelength available information are not flooded, but It will hinder the establishment of LSP. The path calculation entity may obtain the foregoing parameter information in a pre-configured manner, or each node may send the foregoing parameter information to the path calculation entity, and the path calculation entity may also obtain the parameter information by using a routing protocol (for example, the node passes the routing protocol pair). The above mentioned The number of information is flooded). Therefore, consider adding the bundle link wavelength constraint information and the wavelength available information to the traffic parameters of the link bundle (for example, extending the routing protocol), flooding the two information, and how to route the route The protocol was developed to obtain wavelength constraint information and wavelength available information for these bundle links. The link bundle information routing calculation and wavelength assignment entity learns the link bundle information for each of the bundle links and floods the link bundle information. The link bundling information includes: wavelength constraint information of the bundle link, and wavelength available information of the bundle link. The wavelength constraint information of the bundle link refers to: the union of all wavelengths supported by all member links in the bundle link. The wavelength available information of the bundle link means: the union of all the wavelengths supported by all member links in the bundle link, when the wavelength supported by the member links in the bundle link is occupied, The occupied wavelength is removed from all of the available wavelengths in a concentrated manner, and at the end of the wavelength occupancy, the wavelength is added to the sum of all available wavelengths. Regardless of whether centralized wavelength distribution or distributed wavelength assignment is used, the wavelength constraint information and wavelength available information of the member links in the bundle link can be summarized, together with the traffic engineering parameters of the bundle link defined in RFC4201. Flooding, while other information about member links cannot be flooded with bundle links. (OSPF/IS-IS). The link bundling information stored by the nodes at both ends of the bundle link can be obtained through configuration or by automatic discovery as defined by RFC4204 (LMP). Since the entity performing the wavelength allocation can obtain the wavelength constraint information and the available wavelength information of the bundle link, the entity performing the wavelength assignment can perform the wavelength channel calculation and the wavelength assignment efficiently and accurately, regardless of the wavelength distribution and the member link selection. Wavelength assignment is also a distributed wavelength assignment. In this way, the relevant IETF standard of the existing bundle link needs to be extended, and the extension of the routing protocol is divided into two steps as described below. First: The wavelength constraint information of the bundle link IETF draft draft-ietf-ccamp-rwa-info extends the routing ten protocol (OSPF-TE/IS-IS), adding wavelength constraint information to the TE link, Available wavelength information, as well as wavelength connectivity information for nodes, wavelength conversion capability constraint information, and description of wavelength conversion available information, Figure 3 is a draft draft-ietf-ccamp-rwa-info pair routing protocol (OSPF-TE/IS-IS) Schematic diagram of the extension. By extending the relevant standards for existing bundle links (for example, RFC4201), After the wavelength constraint information and available wavelength information of the member links in the bundle link are summarized, they are flooded together with the traffic engineering parameters of the bundle link defined in RFC4201, and the bundle link wavelength constraint information is all member chains. The road wavelength constraint information is aggregated. FIG. 4 is a schematic diagram of the specification of the traffic parameters of the bundle link in RFC4201 in the prior art. The present invention expands the traffic engineering parameters shown in FIG. 4, increases the wavelength constraint information of the bundle link (PortWavelengthRestriction in FIG. 5), and floods to the IGP (Route Protocol) along with other traffic parameters of the bundle link. Wherein, calculating the wavelength constraint information of the bundle link is a local policy problem within the node. Adding the wavelength constraint information of the member link will increase the TE information of the bundle link, but the information only needs to be flooded once, and other traffic parameter information of the member link cannot be flooded, so for the routing protocol Performance has no effect. Moreover, since the maintenance of the RSVP-TE signaling state and the maintenance of the OSPF-TE neighbors are not required for each member link, the advantages of the link bundling do not change after the link bundling technology is applied to the WSON. In addition, the wavelengths that a fiber can support are pre-configured and static, and changing these attributes usually requires a hardware upgrade. If the wavelength constraint information of the member link really needs to change, the change of the wavelength constraint information of the member link may cause the wavelength constraint information of the bundle link to change, and the wavelength constraint information of the bundle link should be recalculated. If it is aggregated by multiple links, the bundle link wavelength constraint information is still the union of all member link wavelength constraint information. Second: Bundle link wavelength available information The present invention extends the traffic engineering parameters already defined by RFC4201, adding a wavelength available information (such as AvailableWavelengthInfo in Figure 5), indicating the available wavelength (tag) information of the bundle link, along with the bundle The other traffic parameters of the bundle link are flooded together into the IGP. The bundled link available wavelength information is the union of the available wavelength information for all member links. Since the available wavelength of the member link changes during the connection establishment and teardown of the LSP, the available wavelength of the member link changes, and the available wavelength of the bundle link changes. The available wavelength information of the bundle link should be Recalculated. If it is aggregated by multiple links, the wavelength available information of the bundle link is still the union of the available information of all member link wavelengths, wherein calculating the available wavelength information of the bundle link is a local strategy within the node problem. After the link bundling technology is applied to the wavelength-switched optical network, the maximum reservable bandwidth (Unreserved Bandwidth) and the unreserved bandwidth (Breakfast Bandwidth) of the bundle link are The Maximum LSP Bandwidth and bundle link bandwidth calculation methods follow the processing principles specified in RFC4201. A specific example of routing protocol extension is provided below using the existing IETF protocol standard. FIG. 5 is a schematic diagram of a route extension method according to an embodiment of the present invention, which is based on the RFC4201 standard. Two sub-TLVs. The first sub-TLV is PortWavelengthRestriction. Considering that draft-ietf-ccamp-rwa-info has become the IETF working group draft, this example is directly defined by the same format of PortWavelengthRestriction in draft-ietf-ccamp-rwa-info. The sub-TLV describes the wavelength constraint information of the bundle link. The second sub-TLV is Available WavelengthInfo, which describes the wavelength available information of the bundle link. Its format definition is shown in Figure 6. The details are described as follows: W: 3 bits, the number of bits used to indicate the wavelength state. For example, when W = 1, it means that the value of one bit is used to indicate the state of the corresponding wavelength (whether or not the wavelength has been allocated). These wavelengths are associated with the wavelengths involved in PortWavelengthRestriction described above, and are one-to-one; Available WavelengthInfo: Length: 16 bits for the length of Available WavelengthInfo; Available WavelengthInfo: Wavelength of the dog, each bit or bits (passed "W" indication) Indicates the available state of a wavelength. For example, in the case of W=l, when the bit is 1, it means that the corresponding wavelength is available, and when the bit is 0, it means that the wavelength has been allocated. Padded bit: A byte that is padded to guarantee 32-bit alignment. (2) Step S104 to step S106. In this step, the route calculation and the wavelength assignment entity learn the parameter information of all member links, where the parameter information includes: all member links and each member included in each bundle link The information of all the wavelengths supported by the link, wherein the information of all wavelengths supported by each member link includes at least one of the following: available wavelength information of the member link, and wavelength constraint information of the member link. The first predetermined strategy includes one of the following: randomly selecting a member link in the bundle link; sorting all available member links in the bundle link according to a certain policy (such as the weight of the link), and selecting the sorted a member link of a predetermined location; selecting according to the number of times the member links in the bundle link have been used, selecting the member links that have been used the most frequently from the available member links; from the bundle link according to the network load Select member links in . The second predetermined policy includes one of: performing a random selection among available wavelengths of the member links; All available wavelengths of the member link are sorted according to a certain strategy (such as the weight of the wavelength), and the wavelength of the predetermined position after sorting is selected; according to the number of times the wavelength in the member link is used, the number of used times is selected from the available wavelengths. The most wavelengths; select from the available wavelengths of the member links according to the network load. The following is an example of how to implement the label switching path establishment in steps S102, S104, and S106 by taking the wavelength-switched optical network topology diagram using the link bundling technique shown in FIG. 7 as an example. As shown in Figure 7, Linkl2 is connected to Component Link25-1 and Component Link25-2 in the bundle link Link25; Link23 is connected to Component Link34-1 and Component Link34-2 in the bundle link Link34; Link54 and Component Link25-1 and Component Link25-2 in bundle link Link25 are connected; Link46 is connected to Component Link34-1 and Component Link34-2 in Link bundle link 34; Link54 and 4 bundle link Link46 Connected. The wavelength conversion capability λΐ— >λ2 between Component Link24-1 and Link54 and between Component Link24-2 and Link54. Between Component Link 34-1 and Link 46, between Component Link 34-2 and Link 46, and between Link 54 and Link 46, there are wavelength conversion capabilities λ2 -> λ1, λ2 -> λ4, and λ3 - > λ4. According to the wavelength-switched optical network topology shown in FIG. 7, the route calculation and wavelength assignment entity must know the topology of the wavelength-switched optical network shown in FIG. 8 in advance, and obtain the network topology diagram shown in FIG. The following information: (1) Obtain the connectivity constraint information in each node, as follows: Node 2:

[Link 12— >Bundled Link25] [Link 12— >Link23] Node 3: [Link 23— >Bundled Link34] Node 4:

[Bundled Link34— >Link46] [Link54— >Link46]

Node 5:

[Bundled Link25— >Link54]

(2) Obtaining the wavelength conversion capability constraint information in each node, as follows: Node 5:

[Bundled Link 25: λΐ — -> Link54: λ2]

Node 4:

[Bundled Link 34: λ2— -> Link46: λΐ, λ4]

[Bundled Link 34: λ3— -> Link46: λ4]

[Link 54: λ2— -> Link46: λΐ, λ4]

[Link 54: λ3— -> Link46: λ4]

(3) Obtain the available wavelength conversion information in each node, as follows: Node 5:

[Bundled Link 25: λΐ — -> Link54: λ2]

Node 4:

[Bundled Link 34: λ2— -> Link46: λΐ, λ4]

[Bundled Link 34: λ3— -> Link46: λ4]

[Link 54: λ2— -> Link46: λΐ, λ4]

[Link 54: λ3— -> Link46: λ4]

(4) Obtain the wavelength constraint information of each link, as follows:

Linkl2: λΐ, XI, λ3

Link23: λΐ, XI, λ3 Link54: λ2, λ3, λ5

Link46: λΐ, λ4

Bundled Link25: λΐ, XI, λ3, λ6

Bundled Link34: λΐ, XI, λ3, λ4 (5), obtain the available information of the wavelength of each link, as follows:

Linkl2: λΐ, XI, λ3

Link23: λΐ, XI, λ3

Link54: λ2, λ3, λ5

Link46: λΐ, λ4

Bundled Link25: λΐ, XI, λ2, λ3, λ6 (two λ2 available)

Bundled Link34: λΐ, XI, λ3, λ4 Scenario: Suppose the customer needs to establish a wavelength switching path between node 1 and node 6, then there are several optional routes as follows (note: no wavelength conversion capability) In the case where one wavelength on one fiber can only be exchanged to the same fiber on another connected fiber): Optional Route 1: After nodes 1, 2, 3, 4 and 6, using wavelength λΐ, The entire path has a weight of 4; no wavelength conversion capability is used inside any of the nodes. Optional route 2: After 1, 2, 3, and 4 nodes, using wavelength λ2, at node 4, after wavelength conversion λ2 → λ1 or λ2 → λ4 reaches node 6, the weight of the entire path is 4; A total of wavelength conversion capabilities are used for routing. Optional route 3: After 1, 2, 3, and 4 nodes, using wavelength λ3, at node 4, after wavelength conversion λ3 → λ4 reaches node 6, the weight of the entire path is 4; A wavelength conversion capability. Optional route 4: After 1, 2, 5, and 4 nodes, using wavelength λ2, at node 4, after wavelength conversion λ2 → λ1 or λ2 → λ4 reaches node 6, the weight of the entire path is 5; Road A total wavelength conversion capability is used. Optional route 5: After 1, 2, 5, and 4 nodes, using wavelength λ3, at node 4, after wavelength conversion λ3 → λ4 reaches node 6, the weight of the entire path is 5; A wavelength conversion capability. Optional route 6: After nodes 1, 2, and 5, using the wavelength λΐ, at node 5, after wavelength conversion λ1→λ2 reaches node 4, at node 4, after wavelength conversion λ2→λ1 or λ2→ Λ4 reaches node 6, and the weight of the entire path is 5; the route uses a total of two wavelength conversion capabilities. The route calculation and the wavelength assignment entity are required to select an optional route for establishing a label switching path according to a certain policy. These policies may be determined by default implementation or by configuration. For example, it is configured by the management plane). For example, the routing calculation and the wavelength allocation entity get the following strategies: priority weighting, wavelength conversion capability second, under this strategy, the route with the largest weight should be selected first, for example, there are three routes with the maximum weight of 5, Select the route with the least wavelength conversion capability among the three routes with the weight 5, such as the optional route 4 and the optional route 5. If the wavelength conversion capability is prioritized and the weight is second, then Optional Route 1 should be chosen because it does not cost the wavelength conversion capability of any node, consumes the least network resources, and saves the most cost. The entire path uses the wavelength λ1. If the strategy adopted is weight priority, and the wavelength conversion capability is second, then the route calculation and wavelength assignment entity determines the route between node 1 and node 6, which passes Linkl2, Bundled Link25, Link54, and Link46. Subsequent steps S104 and S106啫P take the route as an example, and describe the corresponding implementation method in combination with the architecture of route calculation, wavelength assignment and member link selection. At this time, the wavelengths on the member links, the non-bundling links, and the member links through which the label switching passes, and the wavelength conversion used in the nodes have not yet been determined. In the present invention, if centralized wavelength allocation and centralized member link selection are used, the entity performing route calculation and wavelength assignment can be extended by the draft draft-ietf-mpls-explicit-resource-control-bundle. The ERO sub-object, during the connection establishment process, if the performing route calculation and the wavelength assignment entity can know the wavelength constraint information and the wavelength available information of the member link, the <bundle link, member link, label> is explicitly specified. Combine centralized wavelength assignment and link bundling techniques. That is, RWA needs to know each member link The wavelength constraint information and the available wavelength information can be used for wavelength assignment. Centralized route calculation + centralized wavelength assignment + centralized member link selection In step S102, route calculation and routing between the node 1 and node 6 determined by the wavelength assignment entity (it passes Linkl2, Bundled) Link25, Link54 and Link46), if the centralized routing calculation + centralized wavelength allocation architecture is selected, in the absence of wavelength conversion or limited wavelength conversion, in order to reduce the probability of connection establishment blocking, member links are also concentrated. The selection is made, so the entity performing the wavelength allocation needs to know the wavelength constraint information and the wavelength available information on the member link before the label switching path is established, and can determine which member link is selected. According to the example shown in Figure 8, the route calculation and wavelength assignment entity determines the route between node 1 and node 6 (which passes through Linkl2, Bundled Link25, Link54, and Link46). The route calculation and wavelength assignment entity also needs to know the wavelength constraint information and wavelength available information of the member links included in the Bundled Link 25. After knowing this information, since the route can select the wavelength λ2 or λ3 of the bundle link (if λΐ is selected, the entire route takes two wavelength conversion capabilities), so it needs to select a condition that satisfies the condition in Bundled Link25. Member link. According to FIG. 7, since there are two member links satisfying the condition, a member link can be selected according to the policy mentioned in the patent S104.路由The route calculation and the wavelength assignment entity select Component Link25-2, then there are two wavelengths satisfying the condition on the bundle link, respectively λ2 or λ3, and a suitable one can be selected according to the strategy mentioned in the patent S106. Wavelength, such as λ2. At this point, the route calculation and wavelength assignment entity determines the detailed route: After 1, 2, 5, 4, Linkl2, Bundled Link25, Link54 use wavelength λ2, at node 4, after wavelength conversion λ2->λ1 or λ2— >λ4, after Link46 reaches the node No.6, the weight of the whole path is 5, and the bundle link Bundled Link25 selects the member link Component Link25-2; the route uses a wavelength conversion capability, and at 4 On the node, λ2 can be converted to λΐ or λ4, and λ3 can only be converted to λ4. The route calculation and wavelength assignment entity should determine whether to select λ2 or λ3 according to a certain strategy. For example, choose λ2-->λ4 or λ2 >λ1 (because one of them is selected, λ2 is still able to be converted at this node), instead of λ3 -> λ4, 1 is set to finally select λ2 - > λ4. After the route calculation and wavelength assignment entity determines the wavelength of the bundle link, the member link in the bundle link, the non-bundle link, and the associated link wavelength and the wavelength conversion capability used, the route can be passed through the IETF. The raft working group draft draft-ietf-mpls-explicit-resource-control-bundle extended ERO sub-object, in the label switching path establishment process, for each bundle link and non-bundle link, respectively Specify < bundle Beam links, member links, labels (wavelengths) > and <non-bundles, labels (wavelengths) >, for explicit control of resources. When centralized routing calculation + centralized wavelength allocation + centralized member link selection, you can follow the following steps: Step 1: Obtain the bundle chain in the entity that performs route calculation and wavelength assignment (such as PCE) The wavelength constraint information and the wavelength available information of the link member of the road can be configured in a centralized manner (for example, by configuring the information to the entity performing the path calculation through the management plane) or each node sends the information to the entity performing the path calculation. Step 2: The route calculation and wavelength assignment entities perform route calculation, member link selection, and wavelength assignment procedures. The bundle links that pass through, the member links in the bundle link, the non-bundling links, and the wavelengths of the associated links and the internal wavelength conversion capabilities of the nodes used are determined. Step 3: ERO sub-object by draft draft-ietf-mpls-explicit- resource-control-bundle MPLS working group of the IETF was widely show, ¹ J of step

2 output results (route calculation and wavelength assignment results), in the connection establishment process, for each bundle link and non-bundle link, respectively, specify <bundle link, member link, label ( Wavelength) > and <non-bundled links, label (wavelength) >, for explicit control of resources. For example, according to the above example, explicitly specify the resources in Figure 7 as <Linkl2, λ2>, <Bundled Link25, Component Link25-2, λ2>, <Link54, λ2>, <Link46, λ4> Step 4: Source Node ( The node 1 in FIG. 8 initiates a distributed establishment process of the connection, and the signaling (Path message) carries the ERO sub-object generated in step 3. Step 5: After receiving the connection establishment signaling (Path message), the intermediate node (the nodes 2, 5, and 4 in Figure 8) respectively specifies the <non-bundled link, label (wavelength) according to the ERO and ERO sub-objects. > and <Bundle link, member link, label (wavelength) > Perform member link selection and wavelength assignment. Step 6: After receiving the connection establishment signaling acknowledgement (Resv message), the intermediate node (nodes 2, 5, and 4 in Figure 8) configures the resources of the transport plane (such as ROADM or OXC) according to the reserved wavelength. . Step 7: The route calculation and the wavelength assignment entity re-collect the topology information after the network change. The configuration can be configured in a centralized manner (for example, the changed topology information is configured to the execution path through the management plane). The computed entity) or each node sends the changed topology information to the entity performing the path computation. Centralized Route Calculation + Centralized Wavelength Assignment + Distributed Member Link Selection In step S102, route calculation and routing between the nodes 1 and 6 determined by the wavelength assignment entity (it passes Linkl2, Bundled) Link25, Link54, and Link46), if centralized routing calculation + centralized wavelength allocation + distributed member link selection architecture is selected, routing calculation and wavelength assignment entities are required to further specify the entire label switching path. The wavelengths used on bundled links and non-bundled links. The above examples mentioned that 1, 2, 5, 4 nodes, Linkl2, Bundled Link25 and Link54 links can be used: λ2 or λ3 (if λΐ is selected, the entire route takes twice the wavelength conversion capability), and On node 4, λ2 can be converted to λΐ or λ4, and λ3 can only be converted to λ4. The route calculation and wavelength assignment entities should determine XI or λ3 according to certain strategies. At this time, you should choose a wavelength with more wavelength conversion capability, such as λ2->λ4 or λ2— >λ1 (because one of them is selected, λ2 can still be converted at this node) instead of λ3 >λ4. After the λ2 > λ4 is finally selected, the wavelength of the entire label switching path is determined, that is, Linkl2, Bundled Link25, Link54 select wavelength λ2, and Link46 selects wavelength λ4. When centralized routing calculation + centralized wavelength allocation + distributed member link selection is used, the following steps can be taken: Step 1: Source node (node 1 in Figure 8) is calculated according to route and wavelength The route between the node 1 and the node 6 determined by the distribution entity (which passes through Linkl2, Bundled Link25, Link54, and Link46), generates the corresponding ERO object by using the prior art, and indicates the bundle link through which the label switching path passes. And non-bundled links, and the wavelengths used by these links, for example, according to the above example, explicitly specify the resources in Figure 8 as <Linkl2, λ2>, <Bundled Link25, λ2>, <Link54, λ2>, <Link46, λ4>, and ^) take the ERO object into the Path message, then ^) take the available wavelength λ2 into the Label Set object in the Path message, and finally send the Path message to the downstream node 2. Step 2: After receiving the upstream Path message, Node 2 finds that it is sending a Path message to the downstream Node 5 on the bundle link Bundled Link 25. It needs to select one of the bundle links to meet the wavelength specified by the ERO object. It is found that the wavelengths λ2啫f of Component Link25-1 and Component Link25-2 can be used to select a member link according to the first predetermined strategy. For example, if the result of the selection is Component Link25-2, then node 2 puts the selected wavelength λ2 into a newly generated Label Set object, and the newly generated Label Set object is placed in Path elimination. In the end, finally, the Path message is sent to the downstream node 5. Step 3: After receiving the upstream Path message, Node 5 finds that it needs to send a Path message to the downstream Node 4 on the non-bundled link Link54. Node 5 selects the wavelength specified by the ERO object from the available wavelength of Link54, that is, λ2, puts the selected wavelength λ2 into a newly generated Label Set object, and places the newly generated Label Set object into Path. In the message, finally, the Path message is sent to the downstream node 4. Step 4: After receiving the upstream Path message, Node 4 finds that it needs to send the Path message to the downstream node 6 on the non-bundling link Link46. Node 4 selects from the available wavelengths of Link 46 to meet the wavelength specified by the ERO object, which is λ4. At this point, it finds that the wavelength λ2 on Link 54 needs to be converted to λ4 on Link 46, and λ2 in node 4 can indeed be converted to λ4 on Link 46; then node 4 occupies this wavelength conversion capability. At this point, a new Label Set object is generated, and λ4 is placed in the object, and the newly generated Label Set object is placed in the Path message, and finally, the Path message is sent to the downstream Node 6. Step 5: After receiving the upstream Path message, Node 6 finds that the Label Set object specifies the λ4 wavelength. Node 6 then decrements the available number of λ4 in the available wavelengths of Link 46 by 1 and re-floods. Node 6 generates a Label object, puts λ4 into the Label object, and puts the Label object into the Resv message. Finally, Node 6 sends a Resv message to Node 4. Step 6: After receiving the downstream Resv message, node 4 generates a Label object according to the wavelength conversion capability λ2 > λ4 specified by the Label object, and puts λ2 into the Label object. In the middle, the Label object is placed in the Resv message. Finally, Node 4 sends a Resv message to Node 5 and configures the resources of the transport plane (such as ROADM or OXC). Node 4 decrements the available number of λ4 in the available wavelengths of Link 46 by one, decrements the available number of λ2 in the available wavelengths of Link 54 by one, and floods again. The λ2 > λ4 usable number in the wavelength conversion capability information between Link54 and Link 46 is decremented by 1 and re-flooded. Step 7: After receiving the downstream Resv message, the node 5 configures the resource (such as ROADM or OXC) of the transmission plane between the member link Component Link 25-2 and the Link 54 according to the wavelength (λ2 ) specified by the Label object. Node 5 generates a Label object, puts λ2 into the Label object, and puts the Label object into the Resv message. Finally, Node 5 sends a Resv message to Node 2 on the Bundled Link. Node 5 decrements the available number of λ2 in the available wavelengths of Link 54 by one, and decrements the available number of available wavelengths λ2 of the bundled link Bundled Link 25 by one (finally, one available wavelength remains). Step 8: After receiving the downstream Resv message, node 2 configures the resources (such as ROADM or OXC) of the transmission plane between member links Component Link 25-2 and Linkl2 according to the wavelength (λ2) specified by the Label object. . Node 2 generates a Label object, puts λ2 into the Label object, and puts the Label object into the Resv message. Finally, Node 2 sends a Resv message to Node 1. Node 5 decrements the available number of λ2 in the available wavelengths of Linkl2 by one, and decrements the available number of available wavelengths λ2 of the bundled link Bundled Link 25 by one (finally, one available wavelength remains). Step 9: After receiving the downstream Resv message, Node 1 modifies the available wavelength information of Linkl2 according to the wavelength (λ2) specified by the Label object, decrements the available number of λ2 wavelength by 1 and re-floods. Centralized route calculation + distributed wavelength assignment + centralized member link selection In step S102, route calculation and routing between the nodes 1 and 6 determined by the wavelength assignment entity (it passes Linkl2, Bundled) Link25, Link54 and Link46), if centralized routing calculation + distributed wavelength allocation + centralized member link selection architecture is selected, the entity performing route calculation and wavelength assignment needs to know the member chain before the label switching path is established. The wavelength constraint information and wavelength available information on the road can determine which member link to select. According to the routing information and the wavelength assignment entity, the topology information in Figure 8 is known. It knows that there are several wavelength selection schemes for the route between node 1 and node 6 (it passes Linkl2, Bundled Link25, Link54 and Link46): 1) After 1, 2, 5, 4, using wavelength λ2, at node 4, after wavelength conversion λ2->λ1 or λ2->λ4 reaches node 6, the weight of the whole path is 5; A wavelength conversion capability.

(2) After 1, 2, 5, 4, using wavelength λ3, at node 4, after wavelength conversion λ3->λ4 reaches node 6, the weight of the whole path is 5; the route uses a wavelength conversion ability. At this time, the routing calculation and the wavelength assignment entity involve selecting a member link for the Bundled Link 25, and a member link can be selected according to the policy mentioned in the patent S104. The component routing calculation and the wavelength assignment entity select Component Link 25 -2, then the optional wavelengths on the Component Link 25-2 that satisfy the condition include λ2 and λ3. As for which wavelength to select, it needs to be determined by the local behavior of the node during the label switching path establishment process. If centralized routing calculation + distributed wavelength allocation + centralized member link selection is used, the following steps can be taken: Step 1: The source node (node 1 in Figure 8) is calculated according to the route and The route between the node 1 and the node 6 determined by the wavelength assignment entity (which passes through Linkl2, Bundled Link25, Link54, and Link46), generates corresponding ERO and ERO sub-objects by using the prior art, and indicates the path through which the label switching path passes. Bundled links, member links, and non-bundled links (for example, according to the above example, explicitly specify the resources in Figure 8 as Linkl2, <Bundled Link25, Component Link25-2>, Link54, Link46), and ^) Take the ERO and ERO sub-objects into the Path message. The available wavelengths λ2, λ3 of Link 12 are placed in the Label Set object in the Path message. Finally, the Path message is sent to the downstream node 2. Step 2: After receiving the upstream Path message, Node 2 finds that it is sending a Path message to the downstream Node 5 on the bundle link Bundled Link 25. It selects the wavelength of the wavelength range specified by the upstream Label Set object from the available wavelengths of the Component Link 25-2 according to the member link Component Link25-2 specified by the ERO sub-object, and then selects the selected wavelength (λ2, λ3). Put a newly generated Label Set object, the newly generated Label Set object is placed in the Path message, and finally, send the Path message to the downstream node 5. Step 3: After receiving the upstream Path message, Node 5 finds that it needs to send a Path message to the downstream Node 4 on the non-bundled link Link54. Node 5 selects the wavelength that satisfies the wavelength range specified by the upstream Label Set object from the available wavelengths of Link54, and then places the selected wavelength (λ2, λ3) into a newly generated Label Set object, and the newly generated Label The Set object is placed in the Path message, and finally, the Path message is sent to the downstream Node 4. Step 4: After receiving the upstream Path message, Node 4 finds that it needs to send the Path message to the downstream node 6 on the non-bundling link Link46. However, it found that the wavelength specified by the Label Set object in the Path message was not met on Link 46. At this time, it needs to check whether the wavelength specified by the Label Set object can be converted to some available wavelengths on Link 46 inside the node. It is found that the λ2 specified in the Label Set object can be converted to λΐ, λ4 on Link46; the λ3 specified in the Label Set object can be converted to λ4 on Link46; thus, node 4 generates a new Label Set object, and Put λΐ and λ4 into the object, and put the newly generated Label Set object into the Path message. Finally, send the Path message to the downstream node 6. Step 5: After receiving the upstream Path message, Node 6 finds that the Label Set object specifies multiple wavelengths (λΐ, λ4). Selecting a wave according to the second predetermined strategy mentioned in this patent Long. 1 Set λ4. Node 6 generates a Label object, puts λ4 into the Label object, and puts the Label object into the Resv message. Finally, Node 6 sends a Resv message to Node 4. Node 6 captures the available number of λ4 in the available wavelengths of Link 46 minus one and re-floods. Step 6: After receiving the downstream Resv message, node 4 can only use the wavelength (λ4) specified by the Label object, and the available wavelength conversion capability λ2-->λ4 and λ3--> according to a certain strategy. Select one of λ4. At this time, you should choose a wavelength with more wavelength conversion capability, such as λ2-->λ4 or λ2 >λ1 (because one of them is selected, λ2 can still be converted at this node) instead of λ3 - >λ4. The branch selects λ2 -> λ4, then node 4 generates a Label object, puts λ2 into the Label object, and puts the Label object into the Resv message. Finally, node 4 sends a Resv message to node 5. And configure the resources of the transport plane (such as ROADM or OXC). Node 4 decrements the available number of λ4 in the available wavelengths of Link 46 by one, decrements the available number of XIs in the available wavelengths of Link 54 by 1 and re-floods. The λ2 -> λ4 usable number in the wavelength conversion capability information between Link 54 and Link 46 is decremented by 1 and re-flooded. Step 7: After receiving the downstream Resv message, the node 5 configures the resource (such as ROADM or OXC) of the transmission plane between the member link Component Link 25-2 and the Link 54 according to the wavelength (λ2 ) specified by the Label object. Node 5 generates a Label object, puts λ2 into the Label object, and puts the Label object into the Resv message. Finally, Node 5 sends a Resv message to Node 2. Node 5 decrements the available number of λ2 in the available wavelengths of Link 54 by one, and decrements the available number of available wavelengths λ2 of the bundled link Bundled Link 25 by one (finally, one available wavelength remains). Step 8: After receiving the downstream Resv message, Node 2 configures the resources of the transport plane between member links Component Link 25-2 and Linkl2 (such as ROADM or OXC) according to the wavelength (λ2) specified by the Label object. . Node 2 generates a Label object, puts λ2 into the Label object, and puts the Label object into the Resv message. Finally, Node 2 sends a Resv message to Node 1. Node 5 decrements the available number of λ2 in the available wavelengths of Linkl2 by one, and decrements the available number of available wavelengths λ2 of the bundled link Bundled Link 25 by one (finally, one available wavelength remains). Step 9: After receiving the downstream Resv message, Node 1 modifies the available wavelength information of Linkl2 according to the wavelength (λ2) specified by the Label object, decrements the available number of λ2 wavelength by 1 and re-floods. (Centralized Route Calculation or Distributed Route Calculation) + Distributed Wavelength Assignment + Distributed Member Link Selection In step S104, the route calculation and the wavelength assignment entity determine between node 1 and node 6 Routing (which passes Linkl2, Bundled Link25, Link54, and Link46). If distributed wavelength allocation + distributed member link selection architecture is used, then wavelength assignment and member link selection are performed when the label switched path is established. The route calculation and wavelength assignment entities on the node are completed. When distributed wavelength allocation + distributed member link selection is adopted, the following steps are performed. Figure 9 depicts the signaling interaction process of the entire label switching path establishment: Step 1: Source node (Figure 9 Node 1) uses the existing technology to generate the corresponding ERO object according to the route between Node 1 and Node 6 determined by the route calculation and wavelength assignment entity (it passes Linkl2, Bundled Link25, Link54 and Link46). Indicate the bundled link and the non-bundled link through which the label switched path passes (for example, according to the above example, explicitly specify the resources in Figure 8 as Linkl2, Bundled Link25, Link54, Link46), and ^) win the ERO object Put it in the Path message. ^) The available wavelengths λ ΐ , λ2, λ3 of Link 12 are placed in the Label Set object in the Path message. Finally, the Path message is sent to the downstream node 2. Step 2: After receiving the upstream Path message, Node 2 finds that it is sending a Path message to the downstream Node 5 on the bundle link Bundled Link 25. It needs to select one of the bundle links to meet the wavelength range specified by the Label Set object. It turns out that both Component Link 25-1 and Component Link 25-2 meet the requirements, and then select one according to the first predetermined strategy mentioned in this patent. The member link, for example, the result of the selection is Component Link25-2, then node 2 selects the wavelength that satisfies the wavelength range specified by the upstream Label Set object from the available wavelengths of Component Link 25-2, and selects the selected wavelength (λ2, Λ3 ) Put a newly generated Label Set object, • fc newly generated Label Set object into the Path message, and finally send a Path message to the downstream node 5. Step 3: After receiving the upstream Path message, Node 5 finds that it needs to send a Path message to the downstream Node 4 on the non-bundled link Link54. Node 5 selects the wavelength that meets the wavelength range specified by the upstream Label Set object from the available wavelengths of Link54, and places the selected wavelength (λ2, λ3) into a newly generated Label Set object, and the newly generated Label Set. The object is placed in the Path message, and finally, the Path message is sent to the downstream node 4. Step 4: After receiving the upstream Path message, Node 4 finds that it needs to send the Path message to the downstream node 6 on the non-bundling link Link46. However, it found that the wavelength specified by the Label Set object was not met on Link 46. At this time, it needs to check whether the wavelength specified by the Label Set object can be converted to some available wavelengths on Link 46 inside the node. It turns out that the λ2 specified in the Label Set object can be converted to λΐ, λ4 on Link46; the λ3 specified in the Label Set object can be converted to λ4 on Link46; thus, node 4 generates a new Label Set object, and Put λΐ and λ4 into the object, and the newly generated Label Set object is placed in the Path message. Finally, the Path message is sent to the downstream node 6. Step 5: After receiving the upstream Path message, Node 6 finds that the Label Set object specifies multiple wavelengths (λΐ, λ4). A wavelength can be selected in accordance with the second predetermined strategy mentioned in this patent. 1 Set λ4. Node 6 generates a Label object, puts λ4 into the Label object, and puts the Label object into the Resv message. Finally, Node 6 sends a Resv message to Node 4. Node 6 captures the available number of λ4 in the available wavelengths of Link 46 minus one and re-floods. Step 6: After receiving the downstream Resv message, node 4 can only use the wavelength (λ4) specified by the Label object, and the available wavelength conversion capability λ2-->λ4 and λ3--> according to a certain strategy. Select one of λ4, then you should choose the wavelength with more wavelength conversion capability, such as λ2-->λ4 or λ2 >λ1 (because one of them is selected, λ2 can still be converted at this node) instead of λ3— >λ4. The branch selects λ2 -> λ4, then node 4 generates a Label object, puts λ2 into the Label object, and puts the Label object into the Resv message. Finally, node 4 sends a Resv message to node 5. And configure the resources of the transport plane (such as ROADM or OXC). Node 4 decrements the available number of λ4 in the available wavelengths of Link 46 by one, decrements the available number of XIs in the available wavelengths of Link 54 by 1 and re-floods. The λ2 -> λ4 usable number in the wavelength conversion capability information between Link 54 and Link 46 is decremented by 1 and re-flooded. Step 7: After receiving the downstream Resv message, the node 5 configures the resource (such as ROADM or OXC) of the transmission plane between the member link Component Link 25-2 and the Link 54 according to the wavelength (λ2 ) specified by the Label object. Node 5 generates a Label object, puts λ2 into the Label object, and puts the Label object into the Resv message. Finally, Node 5 sends a Resv message to Node 2. Node 5 decrements the available number of λ2 in the available wavelengths of Link 54 by one, and decrements the available number of available wavelengths λ2 of the bundled link Bundled Link 25 by one (finally, one available wavelength remains). Step 8: After receiving the downstream Resv message, the node 2 configures the transmission plane between the member link Component Link 25-2 and Linkl 2 according to the wavelength (λ2 ) specified by the Label object. Resources (such as ROADM or OXC). Node 2 generates a Label object, puts XI into the Label object, and puts the Label object into the Resv message. Finally, Node 2 sends a Resv message to Node 1. Node 5 decrements the available number of λ2 in the available wavelengths of Linkl2 by one, and decrements the available number of available wavelengths λ2 of the bundled link Bundled Link 25 by one (finally, one available wavelength remains). Step 9: After receiving the downstream Resv message, Node 1 modifies the available wavelength information of Linkl2 according to the wavelength (λ2) specified by the Label object, decrements the available number of λ2 wavelength by 1 and re-floods. As described above, with the link bundle-based label switching path processing method provided by the present invention, a scheme for implementing an LSP establishment process in the bundle link technology is provided, which fills a gap in the prior art. The invention solves the problems encountered in applying the link bundling technology to the wavelength-switched optical network, in particular, after adopting the routing protocol (OSPF-TE) extension technology of the present invention, whether distributed or centralized Wavelength allocation solves the problem that the RWA entity needs to know the wavelength constraint information and the wavelength available information of the member link, and provides a standardized method for automatic wavelength-switched optical network interconnection, while maintaining the advantages of link bundling technology. . The above is only the preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes can be made to the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the scope of the present invention are intended to be included within the scope of the present invention.

Claims

Claim

A method for processing a label switching path based on a link bundle, comprising:

A route calculation and wavelength assignment entity determines one or more bundled links and non-bundled links through which the LSP passes;

The route calculation and wavelength assignment entity selects a member link from each bundle link according to a first predetermined policy;

The route calculation and wavelength assignment entity determines the wavelength conversion used by the selected node in accordance with the second predetermined policy.

2. The method according to claim 1, wherein the method further comprises:

The route calculation and wavelength assignment entity knows link bundle information for supporting route calculation and wavelength assignment in all bundle links in advance, wherein the link bundle information includes: wavelength constraint information of the bundle link The wavelength of the bundle link is available.

The method according to claim 2, wherein the route calculation and the wavelength assignment entity acquire the wavelength constraint information of the bundle link by calculating wavelength constraint information of all member links in the bundle link. The wavelength constraint information of the bundle link refers to: a union of all wavelength constraint information supported by all member links in the bundle link.

4. The method according to claim 2, characterized in that

The route calculation and the wavelength assignment entity obtain the wavelength available information of the bundle link by calculating the wavelength available information of all member links in the bundle link, wherein the wavelength available information of the bundle link refers to : a union of available wavelengths of all member links in the bundle link; and, when one wavelength is available on a plurality of member links of the bundle link, the wavelength in the bundle link The available number is the sum of the wavelength available numbers for the plurality of member links.

The method according to claim 4, wherein in the label switching path establishment and removal process, the available wavelengths supported by the member links in the bundle link through which the label switching path passes are occupied. And concentrating the occupied wavelength from the sum of all available wavelengths, and reducing the corresponding wavelength availability in the bundle link by the number of occupied wavelengths; Adding the wavelength occupied by the end to the sum of all the wavelengths, and increasing the wavelength of the corresponding wavelength in the bundle link to increase the wavelength occupied by the end in the case that the occupied wavelength ends. And recalculating the wavelength available information of the bundle link when the available wavelength information of the member link in the bundle link changes, and flooding the calculation result, wherein the calculation result is The union of the available information for all member link wavelengths.

The method according to claim 3, wherein, when the member link wavelength constraint information in the bundle link is changed, the method further includes:

Recalculating the wavelength constraint information of the bundle link, wherein the calculation result is still a union of all member link wavelength constraint information;

Flooding the recalculated wavelength constraint information.

The method according to claim 2, wherein the link bundling information is flooded, and if the link bundling information changes, the link bundling after the change is re-flooded information.

8. The method according to claim 2, wherein the manner of knowing link bundle information for supporting route calculation and wavelength assignment in all bundle links includes one of the following:

The path calculation and wavelength assignment entity obtains the link bundling information by a pre-configured manner;

Each node transmits its own link bundling information to the path computation and wavelength assignment entity, wherein each node reconfigures or transmits the changed link bundling information when the link bundling information changes.

The method according to claim 1, wherein the method further comprises: the route calculation and the wavelength assignment entity knowing parameter information of all member links in advance, wherein the parameter information comprises: each bundle All member links included in the bundle link, wavelength constraint information supported by each member link, and wavelength available information.

The method according to claim 1, wherein the route calculation and the wavelength assignment entity acquire parameter information of each node in advance, wherein the parameter information includes at least one of the following: each bundle in the node Connectivity constraint information between the bundle link and other bundle links, wavelength conversion capability constraint information, wavelength conversion available information; connectivity constraint information between each bundle link and non-bundled link, Wavelength conversion capability constraint information, wavelength conversion available letter Information; connectivity constraint information, wavelength conversion capability constraint information, and wavelength conversion available information between non-bundled links within the node.

The method according to claim 10, wherein the obtaining parameter information of each node comprises: the route calculation and the wavelength assignment entity calculating all member links and non-bundles in the bundle link Connectivity constraint information, wavelength conversion capability constraint information, wavelength conversion available information between bundle links, and member links in other bundle links, obtaining the bundle link and the other bundles Connectivity constraint information between links, and with non-bundled links, wavelength conversion capability constraint information, wavelength conversion available information; wherein connectivity constraint information between bundle links and non-bundled links The wavelength conversion capability constraint information and the wavelength conversion available information are a union of connectivity constraint information, wavelength conversion capability constraint information, and wavelength conversion available information between all member links and the non-bundle link in the bundle link. Connectivity constraint information, wavelength conversion capability constraint information, and wavelength conversion available information between bundled links are all member chains in these bundle links a union of connectivity constraint information, wavelength conversion capability constraint information, and wavelength conversion available information; and, two wavelength pairs in a bundle link, multiple member links and other links (including other non-bundled chains) When wavelength conversion between the road and the member links in other bundle links is available, the wavelength pair is between the bundle link and other links (including other non-bundling links and bundle links) The available number of wavelength conversions is the sum of the number of wavelength conversions available between all member links in the bundle link and other links, including member links in other non-bundled links and other bundle links.

The method according to claim 11, wherein the route calculation and the wavelength assignment entity obtain the parameter information of each node, and the path calculation and the wavelength assignment entity may further obtain the parameter information of the node by using a pre-configured manner. It is also possible that each node sends the parameters of the node to the path calculation and wavelength assignment entity, and when the parameter information of the node changes, it must be able to be reconfigured or sent.

13. The method according to claim 11, further comprising:

After the available wavelength conversion capability between the member links in the bundle link and other links (including member links in other bundle links and other non-bundle links) is occupied or released, the corresponding bundle The available wavelength conversion capability information between the link and other links (including other bundle links and other non-bundled links) must be recalculated, and the result is still all member links and other links in the bundled link. The wavelength conversion of the links (including the member links of other non-bundled links and other bundle links) is a union of the available information and needs to be re-broadcast.

The method according to any one of claims 1 to 13, wherein the first predetermined policy comprises one of the following:

Randomly selecting member links in the bundle link;

Sorting all available member links in the bundled link according to a predetermined policy, and selecting a member link at a predetermined position after the sorting;

Selecting the member link that has been used the most frequently from the available member links according to the number of times the member links in the bundle link have been used;

A member link is selected from the bundle link according to the network load.

The method according to any one of claims 1 to 13, wherein the second predetermined policy comprises one of the following:

Random selection in the available wavelengths of the member links;

All available wavelengths of the member links are sorted according to a predetermined strategy, and the wavelengths of the predetermined positions after sorting are selected;

Selecting the wavelength that has been used the most from the available wavelengths based on the number of times the wavelength in the member link has been used;

Select from the available wavelengths of the member links based on the network load.

16. The method of claim 1, wherein the method is applicable to the following architectures that combine routing calculation, wavelength assignment, and member link selection:

Centralized routing calculation + centralized wavelength allocation + centralized member link selection; centralized routing calculation + centralized wavelength allocation + distributed member link selection; centralized routing calculation + distributed wavelength Allocation + centralized member link selection; centralized routing calculation + distributed wavelength assignment + distributed member link selection; distributed routing calculation + distributed wavelength assignment + distributed member link selection.

The method according to claim 16, further comprising: before the label switching path is established, both the route calculation and the wavelength assignment entity must obtain the wavelength constraint information and the wavelength available information of the bundle link in advance, the node Connectivity constraint information, wavelength conversion capability constraint information, and wavelength conversion available information between internal bundle links, between non-bundled links, and bundled links and non-bundled links.