WO2009152753A1

WO2009152753A1 - Method, network node and network system for negotiating the port attribute parameters

Info

Publication number: WO2009152753A1
Application number: PCT/CN2009/072269
Authority: WO
Inventors: 韩建蕊
Original assignee: 华为技术有限公司
Priority date: 2008-06-20
Filing date: 2009-06-15
Publication date: 2009-12-23
Also published as: CN101610126B; CN101610126A

Abstract

A method for negotiating the port attribute parameters comprises: the port information of the first node and the second node in the network is acquired, wherein the port information comprises the port attribute parameters; when the port attribute parameters of the first node and the second node are not consistent, and the port attribute parameters of at least one of the first node and the second node can be configured, the port attribute parameters of the second node and /or the first node that can be configured are adjusted so that the port attribute parameters of the first node and the second node can be consistent.

Description

Port attribute parameter negotiation method, network node and network system

This application claims priority to Chinese Patent Application No. 200810126977.2, entitled "Port Attribute Parameter Negotiation Method, Network Node and Network System", submitted on June 20, 2008, the entire contents of which are incorporated by reference. In this application.

Technical field

The present invention relates to the field of communications technologies, and in particular, to a port attribute parameter negotiation method, a network node, and a network system.

Background technique

Wavelength Division Multiplexing (WDM) network is the core of future wide area network and metropolitan area network, including: Optical Terminal Multiplexer (ΟΤΜ), Optical Line Amplifier (OLA) The optical add/drop multiplex network element (OADM) and the electrical relay network element (Regenerator, REG) are shown in Figure 1.

The OTM is placed at the terminal station and can be divided into a transmitting part and a receiving part. The transmitting part is for optical wavelength conversion, multiplexing, and merging of optical signals output by a plurality of client devices for amplification and transmission in one optical fiber. The receiving part separates all the channels transmitted in one optical fiber and sends them to the corresponding client devices. In the transmitting part of the open OTM, the non-standard wavelength multi-path optical signal of the client is converted into a standard wavelength optical signal by an Optical Transponder Unit (OTU), so that signals of different interface characteristics of different manufacturers can be accessed. . For integrated OTM, multi-channel signals from the client that conform to the WDM standard (such as STM-64 (Synchronous Transfer Mode 16) SDH (Synchronous Digital Hierarchy) signals are directly copied With the main channel, there is no need to use the OTU unit for wavelength conversion. Among them, the OTU unit used for wavelength conversion has many important parameters, such as supported service type, line code modulation type, code stream rate mode parameter and the like.

An optical line amplifying network element (OLA) is placed on the relay station to perform optical signal amplification and dispersion compensation for bidirectional transmission.

The optical add/drop multiplex network element (OADM) needs to use the optical splitter to perform the download service for the channel service on the optical path, and use the optical multiplexer to perform the upload service, and the channel service that does not need the upper and lower channels is punched through. An electrical relay network element (REG) shapes, retimes, and regenerates signals from an optical line amplifying unit (OLA).

In a WDM network, the service attribute parameters of the OTU units for wavelength conversion in the two OTMs that transmit services to each other must be the same (such as the OTU units in OTM1 and OTM2 in Figure 1).

In the research and practice of the prior art, the inventors found that the prior art has the following problems: In the prior art, after the service connection is established, some service attribute parameters of the OTU unit in the two OTMs may not be configured. At this time, the service attribute parameters may be manually configured, but the service attribute parameters of the OTU unit in the two OTMs may be inconsistent, or some parameters of the OTU unit in the two OTMs do not support configuration after the service connection is established, but The default business attributes of these parameters are inconsistent, so even if the connection between the two clients is established, the service cannot be delivered. Summary of the invention

The technical problem to be solved by the embodiments of the present invention is to provide a port attribute parameter negotiation method, a network node, and a network system, which can ensure normal transmission of services after the connection is established.

In view of this, the embodiments of the present invention provide:

A method for negotiating port attribute parameters, including:

Obtaining port information of the first node and the second node in the network, where the port information includes: a port attribute parameter;

Adjusting the second node and/or the first node when the port attribute parameters of the first node and the second node are inconsistent, and the port attribute parameter of the at least one node of the first node and the second node is configurable Configure the port attribute parameters to make the port attribute parameters of the first node and the second node consistent.

A network node, including:

An obtaining unit, configured to acquire port information of the first node and the network node in the network, where the port information includes: a port attribute parameter;

a first determining unit, configured to determine whether the port attribute parameters of the first node and the network node are consistent;

a second determining unit, configured to determine, when the determining result of the first determining unit is negative, whether the port attribute parameter of the at least one node of the first node and the network node is configurable; An adjusting unit, configured to: when the determination result of the second determining unit is yes, adjust a configurable port attribute parameter of the network node and/or the first node, so that a port attribute of the first node and the network node The parameters are consistent.

A network system, comprising: a first node, a second node;

The first node is configured to send, to the second node, port information of the first node; the port information includes a port attribute parameter;

The second node is configured to receive port information of the first node, when the port attribute parameters of the first node and the second node are inconsistent, and the port attribute parameter of the second node is configurable, The configurable port attribute parameter is such that the port attribute parameters of the first node and the second node are consistent.

A network system, comprising: a first node, a second node;

The first node is configured to send, to the second node, port information of the first node; the port information includes a port attribute parameter; and the port attribute parameter is changed after receiving the notification from the second node;

The second node is configured to receive the port information of the first node, where the port attribute parameters of the first node and the second node are inconsistent, and the port attribute parameter of the first node is configurable, The first node changes the configurable port attribute parameter to make the port attribute parameters of the first node and the second node consistent.

A network system, comprising: a first node, a second node;

The first node is configured to send, to the second node, port information of the first node; the port information includes a port attribute parameter, and the port attribute parameter is changed after receiving the notification from the second node;

The second node is configured to receive the port information of the first node, where the port attribute parameters of the first node and the second node are inconsistent, and the port attribute parameters of the first node and the second node are configurable The port attribute parameter of the second node is changed, and the first node is notified to change the port attribute parameter, so that the port attribute parameters of the first node and the second node are consistent.

One of the above technical solutions has the following beneficial effects:

In the embodiment of the present invention, when the port attribute parameters of the first node and the second node of the WDM network are inconsistent, the first node is adjusted by adjusting the configurable port attribute parameter in the first node and/or the second node. It is consistent with the port attribute parameter of the second node to ensure that the service can be delivered normally after the service connection is established.

DRAWINGS

Figure 1 is a schematic diagram of a WDM network structure;

2 is a schematic structural diagram of a transparent network according to Embodiment 1 and Embodiment 2 of the present invention; FIG. 3 is a flowchart of a method for negotiating a port attribute parameter according to Embodiment 1 of the present invention;

4 is a flowchart of a port attribute parameter negotiation method according to Embodiment 2 of the present invention;

FIG. 5 is a schematic structural diagram of a translucent network according to Embodiment 3 of the present invention; FIG.

FIG. 6 is a flowchart of a port attribute parameter negotiation method according to Embodiment 3 of the present invention;

FIG. 7 is a schematic structural diagram of a network node according to Embodiment 4 of the present invention.

detailed description

The embodiment of the present invention provides a port attribute parameter negotiation method, including: acquiring port information of a first node and a second node in the network, where the port information includes: a port attribute parameter; when the first node, the second node If the port attribute parameters of the node are inconsistent, and the port attribute parameter of the at least one node of the first node and the second node is configurable, adjust the configurable port attribute parameter of the second node and/or the first node to make the first The port attribute parameters of the node and the second node are the same. The port attribute parameters of the first node and the second node are respectively optical port attribute parameters of the source client and the target client; or the port attribute parameters of the first node and the second node are respectively access by the source client. The service attribute parameter of the optical forwarding unit of the access network element of the network element and the target client; or the port attribute parameters of the first node and the second node are respectively the light of the access network element of the relay network element and the target client The service attribute parameter of the forwarding unit. The optical forwarding unit of the access network element of the source client and the access network element of the target client may be an OTU unit; the optical forwarding unit of the relay network element may be a relay unit, and the relay unit may be an OTU unit.

In order to make the embodiment of the present invention more clear, the OTU unit is first introduced as follows: The OTU unit is used for wavelength conversion, and can support different service types, code modulation techniques, and Forward Error Correction (FEC). Mode, etc.

Among them, OTU units with different service types cannot communicate with each other. For example, some OTU units only support SDH type services, and some OTU units only support GE (Gigabit Ethernet, Gigabit). The access of the Ethernet service cannot be established between the OTU unit supporting only the SDH type service access and the OTU unit supporting only the GE service access.

Among them, the supported OTU units with different coding and modulation technologies cannot communicate with each other. Coded modulation technology is one of the key technologies for long-distance, high-speed optical transmission systems. Due to the different capabilities of different line patterns against noise, dispersion, and nonlinear effects in fiber-optic channels, choosing the appropriate pattern can increase the number of other devices. Increase the maximum transmission distance of the optical communication system under the condition. The current coded modulation techniques can be classified into three categories according to their information bearing objects: 1) On-Off Keying (OOK) modulation series based on the intensity modulation principle, such as Return to Zero Modulation (RZ) ), Non Return to Zero Modulation (NRZ), etc.; 2) Phase Shift Keying (PSK) modulation series based on phase modulation principle, such as differential phase shift modulation format (Differential Phase Shift) Keying Modulation (DPSK), Differential Quadrature Phase Shift Keying Modulation (DQPSK), Differential 8-level Phase Shift Keying Modulation (4-DPSK), etc. 3) Polarization-shift keying modulation (PoISK) series based on polarization modulation principle, such as Duo-binary Polarization-shift keying (DPolSK); Some of these different modulation methods must be consistent at both ends of the business process, Service is not on, the unit OTU between different PSK modulation mode can not communicate traffic.

Among them, OTU units with different FEC modes cannot communicate with each other. FEC technology reduces the requirement of receiving signal-to-noise ratio by adding redundant error correction codes to the transmission code sequence to improve system performance, reduce system cost and extend transmission distance. In-band FEC (acquisition coding gain 3dB ~ 4dB) and normal out-of-band FEC (acquired coding gain 4dB ~ 5dB) are used in conventional WDM systems, while in ULH (Ultra Long Haul) systems, More enhanced FEC (EFEC) or super FEC (Super FEC) with cascading codes, resulting in a coding gain of 7dB ~ 9dB. There is no communication between OTU units with different FEC modes. For example, the in-band FEC and the out-of-band FEC cannot communicate with each other. The standard FEC cannot be interworked with the enhanced FEC (EFEC) or the super FEC (Super FEC). Currently only standard The FEC is standard coded. The OTUs that support the standard FEC mode can communicate with each other. However, other types of FEC, such as enhanced FEC and super FEC, are not standardized at present. Only the same coding method such as BCH is used. (Bose-Chaudhuri-Hocquenghem, Boss-Chad Huri-Hokungem) (1020,900) coded OTUs are likely to interoperate.

The service attribute parameters (service type, code modulation technology, FEC mode, etc.) of the above OTU unit can be changed through configuration. For example, some OTU units can support SDH services, specifically whether to support STM-1 or support STM-4 can be changed through configuration. For FEC mode, it can also be modified by configuration parameters. For example, it can be configured to disable FEC, can be configured to enable FEC, or can modify standard FEC to enhanced FEC mode. In this document, the configurable and configurable range of the service attribute parameters of the OTU unit is called the configurable characteristic of the service attribute parameter.

In a WDM (Wavelength Division Multiplexing) network, since the optical signal transmits loss, dispersion, etc. in the transmission medium, the relay unit is required to perform 3R (power amplification, signal shaping, and retiming) processing on the optical signal. To ensure the transmission distance of the optical signal. An optical network with a relay unit is called a semi-transparent optical network, and an optical network without a relay unit is called a transparent optical network. The relay unit may be an electrical relay network element (REG). The OTU unit in the relay unit also has the aforementioned service attributes and service attribute parameter configurable characteristics. In a semi-transparent network, a service connection starts from the access network element of the source client, and needs to go through the relay unit to the access network element of the destination client, and the access network element and the relay unit of the source client on the service connection. The service attributes of the OTU unit on the access NE of the destination client should be consistent.

The following describes the port attribute parameter negotiation method when the service connection between the client network side R1 and the R2 needs to be established on the customer network side, and the method is applicable to the transparent network.

Referring to FIG. 2 to FIG. 3, the first embodiment of the present invention provides a method for negotiating a port attribute parameter, which is applicable to a transparent optical network, where FIG. 2 shows an optical network including two domains AS1 and AS2, where R1 and R2 It is a client device, R1 is the source client, R2 is the target client, PE11 is the access network element of the source client, and PE22 is the access network element of the target client. PE11 and PE22 can be OTM1 and OTM2, respectively. And PE21 are the boundary nodes between the two domains respectively, and the domains AS1 and AS2 are connected through the two boundary nodes. FIG. 3 shows a flow of a port attribute parameter negotiation method, The method assumes that R1 and R2 have respectively obtained access to the nodes PE11 and PE22 on the network side, and the PE11 and the PE22 have respectively selected one OTU unit. The method includes:

Step 301: The source client R1 sends a call request to the PE11, where the call request is a signaling message of the control plane, and the call request carries routing information, where the routing information includes: an address of the access network element PE22 of the R2.

Step 302: The PE11 selects an OTU unit, and sends a call request to the PE22 according to the address of the PE22 in the routing information. The call request may include: an identifier of the PE11, an identifier of the OTU unit selected by the PE11, a service attribute parameter, and a service attribute parameter. Configurable features.

Step 303: The PE22 receives the call request sent by the PE11, where the call request carries the identifier of the PE11, the identifier of the OTU unit selected by the PE11, the service attribute parameter, and the configurable characteristic of the service attribute parameter, and sends a call request to the target client R2. .

Step 304: R2 returns a call request response message to the PE 22.

Step 305: The PE22 determines whether the service attribute parameter of the received OTU unit of the PE11 is consistent with the service attribute parameter of the OTU unit of the PE11. If yes, go to step 309. If no, go to step 306.

Step 306: Determine whether the service attribute parameter configurable characteristic of the OTU unit of the PE11 and the PE22 is represented as a non-configurable service attribute parameter. If yes, go to step 307. If no, go to step 308.

Step 307: The PE22 sends a call request response message to the PE11 node, where the message carries the information indicating that the OTU unit service attribute parameter of the PE11. PE22 is inconsistent and the identifier of the OTU unit in the call request received in step 303 (ie, step 301). The identifier of the OTU unit selected by PE11).

In this step, sending the information indicating that the OTU unit service attribute parameters of the PE11 and the PE22 are inconsistent to the PE11 node and the identifier of the OTU unit in the call request received in the step 303 are optional, and do not affect the implementation of the present invention.

The message indicates that the PE11 node can re-select an OTU unit to access. After receiving the information indicating that the OTU unit service attribute parameters of the PE11 and the PE22 are inconsistent, the PE11 can select a new OTU unit if the new OTU unit is available. PE22 sends the identifier of the new OTU unit, The configurable characteristics of the service attribute parameter and the service attribute parameter are returned to step 303. If there is no new OTU unit, the call setup fails.

Step 308: The configurable characteristic of the service attribute parameter of the OTU unit of the at least one node of the PE1 and the PE22 is configurable as the service attribute parameter of the corresponding OTU unit, and whether the configurable service attribute parameter can be adjusted to reach the PE11 and the PE22. The service attribute parameters of the OTU unit are consistent. If yes, go to step 309; if no, go back to step 307.

The specific implementation of the step is as follows: If the service attribute parameter of the OTU unit of the PE11 is configurable, the service attribute parameter of the OTU unit of the PE22 is not configurable, and the PE22 confirms whether the PE11 can change the service attribute parameter of the OTU unit to be the same as the PE22. The service attribute parameters of the OTU unit are consistent. If the service attribute parameter of the OTU unit of the PE22 is configurable and the service attribute parameter of the OTU unit of the PE11 is not configurable, the PE22 confirms whether the service attribute parameter of the OTU unit can be changed to The service attribute parameters of the OTU unit of the PE11 are the same. If the service attribute parameters of the OTU unit of the PE11 and PE22 are configurable, the service attribute parameters of the OTU unit of the PE11 and PE22 can be adjusted to make the service attribute parameters of the OTU units consistent. Specifically, how to adjust the service attribute parameters of the OTU unit of the PE11 and/or the PE22 may be adjusted according to the policy configured by the user, or may be adjusted according to other rules, without affecting the implementation of the present invention.

Step 309: The PE22 sends a call request response message to the PE11.

If the process proceeds from step 305 to step 309, the call request response message in step 309 is the same as the prior art call request response message;

If the step 308 is performed after the step 308, it is assumed that the PE22 determines that the service attribute parameter of the OTU unit of the PE11 needs to be changed to the unified parameter in the foregoing step 308, and the notification information is carried by the call request response message to notify the first node to change the service attribute. And the notification information includes: an identifier of the OTU unit selected by the PE11 (that is, an identifier of the OUT unit that needs to change the service attribute parameter) and the unified parameter; the unified parameter is a service attribute of the OTU unit of the PE11 and the PE22. Consistent parameters for subsequent establishment of business connections.

Step 310: If the call request response message carries the notification information, the PE11 changes the service attribute parameter of the OTU unit indicated by the OTU unit identifier in the notification information to the unified parameter.

Step 311: PE22 and PE11 are based on the unified parameters determined in the previous call request process. Establish a business connection.

Preferably, in step 302, the PE 11 can notify the PE 22 of its own damage tolerance range (such as the optical signal noise ratio (OSNR) tolerance range of the PE11) by using the call request. In step 309, the PE 22 can call the call. The request response message notifies PEll of its own damage tolerance range (such as the OSNR tolerance range of PE22). Before PE22 and PE11 establish a connection, PE11 calculates the damage value of the path from PE11 to PE22 (such as the path from PE11 to PE22). OSNR), PEll compares the calculated damage value of the path from PE11 to PE22 (such as the OSNR of the path from PE11 to PE22) within the damage tolerance range of PE22 (such as the OSNR tolerance range of PE22). If yes, then A service connection is established between PE22 and PE11. If no, no service connection is established between PE22 and PE11.

Referring to FIG. 2 and FIG. 4, the second embodiment of the present invention provides a method for negotiating a port attribute parameter, which is applicable to a transparent optical network, and the method assumes that R1 and R2 respectively obtain nodes PE11 and PE22 that are connected to the network side, and the embodiment The difference is that PE11 and PE22 do not determine a specific OTU unit. The method specifically includes:

Step 401: The source client R1 sends a call request to the PE11, where the call request carries routing information, and the routing information includes the address of the PE22.

Step 402: The PE11 sends a call request to the PE22 according to the address of the PE22 in the routing information, where the call request includes: an identifier of the PE11, an identifier of multiple OTU units of the PE11, a service attribute parameter, and a configurable characteristic of the service attribute parameter.

Step 403: The PE22 receives the identifiers of the multiple OTU units of the PE11, the service attribute parameters, and the configurable characteristics of the service attribute parameters, and sends a call request to the target client R2.

Step 404: R2 returns a call request response message to the PE 22.

Step 405: The PE22 obtains the traits of the service attribute parameter and the service attribute parameter of the OTU unit, and compares the service attribute parameter of the OTU unit with the service attribute parameter of the OTU unit of the PE11, and first searches for the service attribute parameter. The OTU unit group obtains the identifier of the OTU unit of the PE11 in the OTU unit group with the same service attribute parameter, and determines whether the service attribute parameter of the OTU unit of the PE22 and/or the PE11 is configurable if the service attribute parameter is inconsistent with the OTU unit, if no service is found. The OTU unit group with the same attribute parameters, and at the same time judges the PE22 and/or If the service attribute parameter of the OTU unit of the PE11 is not configurable, step 406 is performed. If it is determined that the service attribute parameter of the OTU unit of the ΡΕ22 and/or the PE11 is configurable, step 408 is performed; if an OTU unit group with the same service attribute parameter is found, When it is determined that the service attribute parameters of the OTU unit of the ΡΕ22 and/or the PE11 are not configurable, step 409 is performed;

Step 406: The ΡΕ22 sends a call request response message to the PE11, where the message carries the information indicating that the OTU service attribute parameters of the PE11 and the ΡΕ22 are inconsistent, and the message may also carry the reason that the service attribute parameter is inconsistent.

In this step, the information indicating that the OTU unit service attribute parameters indicating the ΡΕ11 and ΡΕ22 are inconsistent to the PE11 node is optional, and does not affect the implementation of the present invention.

Step 407: The PE11 sends a call request response message to the R1, where the message carries the information indicating that the OTU service attribute parameters of the PE11 and the ΡΕ22 are inconsistent, and the message may also carry the reason that the service attribute parameter is inconsistent.

After receiving the information indicating that the OTU service attribute parameters of PE11 and ΡΕ22 are inconsistent, R1 reselects the new ΟΤΜ access, and sends a call request to the new ,, and proceeds to step 402.

Steps 408 and ΡΕ22 determine whether the configurable service attribute parameter can be adjusted to reach ΡΕ11.

The service attribute parameter of the OTU unit of ΡΕ22 is consistent, if yes, step 409 is performed; if no, and the OTU unit group with the same service attribute parameter is not found in step 405, the execution step is returned.

406.

The implementation of the step is similar to the step 308. The difference is that the PE22 determines whether the multiple OTU units of the PE11 and the multiple OTU units of the PE11 can be adjusted by adjusting the service attribute parameters. When any of the OTU units of its own and the service attributes of any one of the OTU units of the PE11 are consistent, the process returns to step 406.

Step 409: The PE22 sends a call request response message to the PE11.

If the process proceeds from step 405 to step 409, the call request response message includes: an identifier of the OTU unit of the PE11 in the OTU unit group in which the service attribute parameters obtained in step 405 are consistent;

If the step 408 is performed to the step 409, the call request response message includes: the label of the OTU unit of the PE11 in the OTU unit group in which the service attribute parameters obtained in step 405 are consistent. It is necessary to change the identity of the OTU unit of PE11 and the corresponding unified parameters of the service attribute parameter. The identifier of the OTU unit of the PE11 that needs to change the service attribute parameter may be multiple. Step 410: The PE11 changes the service attribute parameter of the OTU unit indicated by the OTU unit identifier that needs to change the service attribute parameter to the corresponding unified parameter, and saves the identifier of the OTU unit used to establish the service connection and the corresponding service attribute parameter, where The identifier of the OTU unit that establishes the service connection includes: an identifier of the OTU unit of the PE11 in the OTU unit group in which the service attribute parameters obtained in step 405 are consistent, and an identifier of the OTU unit in which the service attribute parameter has been changed.

Step 411: The PE22 and the PE11 establish a service connection based on the previous call request process.

The step is different from the step 311 of the first embodiment in that the step 311 establishes the service connection using the OTU unit selected in step 302; and in the step 411, when the service connection is established, the PE 11 may select the one saved in step 410. OTU unit used to establish a service connection.

Preferably, in step 402, the PE 11 can notify the PE 22 of its own damage tolerance range (such as the optical signal noise ratio (OSNR) tolerance range of the PE11) by using the call request. In step 409, the PE 22 can call the call. The request response message notifies PEll of its own damage tolerance range (such as the OSNR tolerance range of PE22). Before PE22 and PE11 establish a connection, PE11 calculates the damage value of the path from PE11 to PE22 (such as the path from PE11 to PE22). OSNR), PEll compares the calculated damage value of the path from PE11 to PE22 (such as the OSNR of the path from PE11 to PE22) within the damage tolerance range of PE22 (such as the OSNR tolerance range of PE22). If yes, then A service connection is established between PE22 and PE11. If no, no service connection is established between PE22 and PE11.

In a specific case, R1 and R2 directly output color light. In this case, the OTU units in PE11 and PE22 are no longer required for service access, but are directly transmitted. The optical port attribute parameters of R1 and R2 need to be negotiated. The R2 sends the signaling of the configurable characteristic of the optical port attribute parameter and the optical port attribute parameter. The specific negotiation process is similar to that in the first embodiment, and details are not described herein again. If the path between R1 and R2 cannot be directly reached, R1 sends the signaling of its own optical port attribute parameter and the configurable characteristic of the optical port attribute parameter to PE11, and then PE1 sends it to PE22 and PE22 to R2. Preferably, the signaling of the configurable characteristic of the optical port attribute parameter and the optical port attribute parameter that is sent by R1 to R2 carries the damage tolerance range of R1 (such as the OSNR tolerance range of R1), and the subsequent R2 is in the direction. The response message sent by R1 carries the damage tolerance range of R2 (such as the OSNR tolerance range of R2). Before R1 and R2 establish a connection, R1 calculates the damage value of the path from R1 to R2 (such as the OSNR of the path from R1 to R2), and R1 compares the calculated damage value of the path from R1 to R2 (eg, from R1 to R2). Whether the OSNR of the path is within the damage tolerance range of R2 (such as the OSNR tolerance range of R2). If yes, a service connection is established between R2 and R1. If not, no service connection is established between R2 and R1.

Referring to FIG. 5 - FIG. 6 , a third embodiment of the present invention provides a method for negotiating a port attribute parameter, which is applicable to a semi-transparent optical network, where FIG. 2 shows an optical network including two domains AS1 and AS2, and Embodiment 1 The difference is that the PE12 and the PE21 are the relay network elements between the two domains, and the domains AS1 and AS2 are connected through the two relay network elements. FIG. 6 shows a flow of a method for negotiating a port attribute parameter, where the method 4 determines that R1 and R2 have respectively acquired nodes PE11 and PE22 connected to the network side, and PE11 and PE22 have respectively selected one OTU unit, and the method is applicable to Translucent network, the method specifically includes:

Step 601: The source client R1 sends a call request to the PE11, and the call request carries the routing information, where the routing information includes: an address of the node on the route, specifically an address of the PE12, the PE21, and the PE22.

Step 602: The PE11 selects an OTU unit, and sends a call request to the PE12 according to the address of the PE12 in the routing information. The call request includes: an identifier of the PE11, an identifier of the OTU unit selected by the PE11, a service attribute parameter, and a service attribute parameter. Configuration features.

Step 603: The PE12 selects an OTU unit, and sends a call request to the PE21 according to the address of the PE21 in the routing information. The call request includes: an identifier of the PE11, an identifier of the OTU unit selected by the PE11, a service attribute parameter, and a service attribute parameter. Configuration features, and, the identity of the PE12, the identity of the OTU unit selected by the PE12, the service attribute parameter, and the configurable characteristics of the service attribute parameter.

Step 604: The PE21 selects an OTU unit, and according to the address of the PE22 in the routing information,

The PE22 sends a call request, where the call request includes: an identifier of the PE11, an identifier of the OTU unit selected by the PE11, a service attribute parameter, and a configurable characteristic of the service attribute parameter, and an identifier of the PE12, an identifier of the OTU unit selected by the PE12, Configurable properties of business attribute parameters and business attribute parameters, And, the identity of the PE21, the identity of the OTU unit selected by the PE21, the service attribute parameter, and the configurable characteristic of the service attribute parameter.

Step 605: The PE22 obtains the identifier of the PE11, the identifier of the OTU unit selected by the PE11, the service attribute parameter, and the configurable characteristic of the service attribute parameter, and the identifier of the PE12, the identifier of the OTU unit selected by the PE12, the service attribute parameter, and the service. The configurable characteristic of the attribute parameter, and the identifiable characteristic of the PE21, the identifier of the OTU unit selected by the PE21, the service attribute parameter, and the service attribute parameter; and the call request is sent to the target client R2.

Step 606: R2 returns a call request response message to the PE 22.

Step 607: The PE22 determines whether the service attribute parameter of the OTU unit selected by the PE11, the PE12, and the PE21 is consistent with the service attribute parameter of the OTU unit. If yes, go to step 611. If no, go to step 608.

Step 608: According to the traits of the service attribute parameter of the OTU unit of the PE11, the PE12, the PE21, and the PE22, determine whether the service attribute parameters of the OTU unit of the PE11, PE12, PE21, and PE22 are unconfigurable. If yes, go to step 609. If yes, go to step 610.

Step 609: The PE22 sends a call request response message to the PE11 node, where the message carries the indication

The information of the OTU unit service attribute parameters of the PE11, PE12, PE21, and PE22 is inconsistent. The message may also be inconsistent with the OTU service attribute parameters of PE11, PE12, PE21, and PE22.

In this step, the information that the PE22 sends the OTU unit service attribute parameters of the PE11 and the PE22 to the PE11 node is optional, and does not affect the implementation of the present invention.

If the OTU service attribute parameters of the PE11, PE12, PE21, and PE22 are inconsistent, the OTU service attribute parameters of the PE11, PE12, PE21, and PE22 are inconsistent. If a new OTU unit is available, PE11 is available. The node reselects an OTU unit, sends a new configurable characteristic of the OTU unit identifier, the service attribute parameter, and the service attribute parameter to the PE12, and returns to step 602. If no new OTU unit is available, the call fails.

If the OTU service attribute parameters of the PE11, PE12, PE21, and PE22 are inconsistent, the service attribute is inconsistent due to the OTU unit of PE12 and PE21. When the call is requested, the request message will notify the PE 12 and/or the PE 21 to exclude the OTU unit that causes the service attributes to be inconsistent.

Step 610: The PE22 configures the service attribute parameters of the PE11, the PE12, the PE21, and the PE22 according to the service attribute parameters of the PE11, the PE12, the PE21, and the PE22, and determines whether the service attribute parameter of the OTU unit of the PE11, PE12, PE21, and PE22 is consistent by adjusting the configurable service attribute parameter. , go to step 611; if no, go back to step 609.

The implementation of this step is similar to the implementation of step 308, except that the service attribute parameters of the OTU unit of the secondary network element PE12, PE21 need to be considered.

Step 611: The PE22 sends a call request response message to the PE11 through the PE12 and the PE21. If the process proceeds from step 607 to step 611, the call request response message in the step 611 is the same as the call request response message in the prior art.

If the step 611 is performed after the foregoing step 610, the call request response message further includes: an identifier of the node that needs to change the service attribute parameter, and an identifier and a unified parameter of the OTU unit of the node that needs to change the service attribute parameter; Is the parameter used to establish a business connection.

Assume that the PE22 determines that the OTU unit of the PE12 needs to change the service attribute parameter, the message includes: the identifier of the PE12, the identifier of the OTU unit whose PE12 needs to change the service attribute parameter, and the unified parameter.

Step 612: The network element (PE12, PE21, or PE11) where the OTU unit needs to change the service attribute parameter changes the service attribute parameter of the OTU unit represented by the OTU unit identifier to a unified parameter; PE11, PE12, PE21, and PE22 are based on the front. The unified parameters determined during the call request process establish a service connection.

Correspondingly, for the semi-transparent optical network, the technical solution similar to that provided by the second embodiment can also be adopted, except that the service attribute parameter of the OTU unit of the relay network element needs to be considered, and the idea is similar to that of the second embodiment. No longer.

The relay network element in the foregoing embodiment 3 of the present invention is a border node. In the existing application, the relay network element may not be in the domain but in the domain, and may also be implemented by using the technical solution provided by the embodiment of the present invention. Negotiation of port attribute parameters does not affect the implementation of the present invention.

In the above embodiment of the present invention, the PE22 node performs the negotiation of the port attribute parameters (that is, the OTU is performed). For comparison and reconfiguration of the service attribute parameters of the unit, other nodes may also be used for negotiation of port attribute parameters, which does not affect the implementation of the present invention.

The foregoing embodiment of the present invention performs the negotiation of the port attribute parameter in the process of the call. The method for negotiating the port attribute parameter provided by the present invention may also be performed in the process of establishing a service connection, for example, the PE11 and the PE12 are transmitted through the service connection establishment request. The service attribute parameters of PE21 can also achieve the object of the present invention.

A person skilled in the art can understand that all or part of the steps of implementing the foregoing embodiments may be performed by a program to instruct related hardware, and the program may be stored in a computer readable storage medium, such as a read only memory. Disk or disc, etc.

Referring to FIG. 7, a fourth embodiment of the present invention provides a network node, where the network node may be a node.

PE22, including:

The obtaining unit 701 is configured to obtain port information of the first node and the network node in the network, where the port information includes: a port attribute parameter;

The first determining unit _{702 is} configured to determine whether the port attribute parameters of the first node and the network node are consistent;

The second determining unit 703 is configured to determine, when the determining result of the first determining unit 702 is negative, whether the port attribute parameter of the at least one node of the first node and the network node is configurable; the adjusting unit 704, configured to: When the determination result of the second determining unit 703 is YES, the configurable port attribute parameter of the network node and/or the first node is adjusted, so that the port attribute parameters of the first node and the network node are consistent.

The port information acquired by the acquiring unit 701 further includes: an identifier of the port and a configurable characteristic of a port attribute parameter; and a second determining unit 703, configured to: when the determining result of the first determining unit 702 is negative, And determining, according to the configurable characteristic of the network node and the port attribute parameter of the first node, whether the port attribute parameter of the at least one node of the first node and the network node is configurable.

The network node also includes:

The third determining unit 705 is configured to determine whether the port attribute parameter of the first node and the network node is consistent by adjusting the configurable port attribute parameter; the adjusting unit 704 is configured to be used by the second determining unit 703. And when the determination result of the third determining unit 705 is YES, adjusting the network The configurable port attribute parameter of the network node and/or the first node.

The first sending unit 706 is configured to: when the determining result of the second determining unit 703 is negative, or when the determining result of the third determining unit 705 is negative, if the port attribute parameter is an optical port attribute parameter, the source client The sending a notification message that the port attribute parameter is inconsistent; if the port attribute parameter is a service attribute parameter, sending a notification message that the service attribute parameter is inconsistent to the access network element of the source client.

The adjusting unit 704 includes a notification message sending subunit, configured to determine, when the determining result of the second determining unit 703 is YES, that the port attribute parameter of the first node needs to be changed to a unified parameter, and send the parameter to the first node. And the notification message is configured to notify the first node to change the port attribute parameter, where the notification message includes: an identifier of the port that the first node needs to change the port attribute parameter, and the unified parameter; or the adjusting unit 704 includes a modification subunit, When the determination result of the second determining unit 703 is YES, it is determined that the port attribute parameter of the user is changed to the unified parameter, and the own port attribute parameter is changed to the unified parameter.

The port attribute parameter of the first node and the network node are respectively the access network element of the source client and the service attribute parameter of the optical forwarding unit of the access network element of the target client; or the first node and the network node The port attribute parameter is a service attribute parameter of the optical forwarding unit of the access network element of the relay network element and the target client, and the network node further includes: a searching unit, configured to acquire, when the obtaining unit 701, multiple lights of the network node When the port attribute parameter of the forwarding unit and the port attribute parameter of the plurality of optical forwarding units of the first node are used, whether the optical forwarding unit of the network node and the plurality of optical forwarding units of the first node have the same service attribute parameter And a forwarding unit, if yes, sending the identifier of the discovered optical forwarding unit of the first node to the first node.

The fifth embodiment of the present invention provides a network system, which is used in a WDM network, and includes: a first node, a second node;

The sixth embodiment of the present invention provides a network system, which is used in a WDM network, and includes: a first node, Second node; wherein

The seventh embodiment of the present invention provides a network system, which is used in a WDM network, and includes: a first node and a second node;

It can be seen from the above analysis that the embodiments of the present invention have the following beneficial effects:

In the embodiment of the present invention, when the port attribute parameters of the first node and the second node of the WDM network are inconsistent, the first node and the second node are configured by adjusting configurable port attribute parameters in the first node and/or the second node. The port attribute parameters are the same to ensure that the service can be delivered normally after the service connection is established.

The port attribute parameter negotiation method, the network node, and the network system provided by the embodiment of the present invention are described in detail. For those skilled in the art, according to the idea of the embodiment of the present invention, the specific implementation manner and the application range are In the above, the contents of the specification are not to be construed as limiting the invention.

Claims

Rights request

A method for negotiating a port attribute parameter, comprising:

2. The method of claim 1 wherein

The port attribute parameters of the first node and the second node are optical port attribute parameters of the source client and the target client, respectively;

Or,

The port attribute parameters of the first node and the second node are respectively the access network element of the source client and the service attribute parameter of the optical forwarding unit of the access network element of the target client;

Or,

The port attribute parameters of the first node and the second node are respectively a service attribute parameter of the relay network element and the optical forwarding unit of the access network element of the target client.

3. The method of claim 1 wherein:

The obtaining the port information of the first node is specifically:

The second node receives the control plane signaling message sent by the first node, where the control plane signaling message includes: port information of the first node.

4. The method of claim 3, wherein

The control plane signaling message is a call request;

After the second node receives the control plane signaling message sent by the first node, the method further includes:

The second node sends a call request response message to the first node, where the call request response message includes: a damage tolerance range of the second node;

Determining, by the first node, a damage value of a path from the first node to the second node, determining whether to establish a second node and the method according to whether the damage value is within a damage tolerance range of the second node The connection between the first nodes.

The method according to claim 1 or 2, wherein the port information further includes: an identifier of the port, and a configurable characteristic of a port attribute parameter;

Before adjusting the configurable port attribute parameters of the second node and/or the first node, the method further includes:

Determining, according to the configurable characteristic of the port attribute parameter of the second node and the first node, whether the port attribute parameter of the at least one node of the first node and the second node is configurable, and if yes, performing the adjusting the second node And/or the step of the configurable port attribute parameter of the first node.

The method according to claim 5, wherein when it is determined that the port attribute parameters of the second node and the first node are not configurable, or cannot be adjusted by adjusting the second node and/or the first node When the configured port attribute parameter is consistent with the port attribute parameter of the first node and the second node, the method further includes:

If the port attribute parameter is an optical port attribute parameter, the second node sends a notification message that the port attribute parameter is inconsistent to the source client;

And if the port attribute parameter is a service attribute parameter, the second node sends a notification message that the service attribute parameter is inconsistent to the access network element of the source client.

7. The method of claim 1 wherein:

The adjusting the configurable port attribute parameter of the second node and/or the first node includes: the second node determining that the port attribute parameter of the first node needs to be changed to a unified parameter, and sending a notification to the first node The message is configured to notify the first node to change a port attribute parameter, where the notification message includes: an identifier of a port that the first node needs to change a port attribute parameter, and the unified parameter;

Or,

The second node determines that its own port attribute parameter needs to be changed to a uniform parameter, and changes its own port attribute parameter to the unified parameter.

8. Method according to claim 1 or 7, characterized in that

The port information of the first node includes: a service attribute parameter of the multiple optical forwarding units of the first node; after acquiring the port information of the first node, the method further includes:

And searching, according to the port information of the first node, an optical forwarding unit that has the same service attribute parameter on the first node and the second node, and sends the identifier of the optical forwarding unit of the first node that is found to the first node.

9. The method of claims 1 and 2, characterized in that

The negotiation method of the port attribute parameter is used in a wavelength division multiplexing WDM network.

10. A network node, comprising:

a second determining unit, configured to determine, when the determining result of the first determining unit is negative, whether the port attribute parameter of the at least one node of the first node and the network node is configurable;

An adjusting unit, configured to: when the determination result of the second determining unit is yes, adjust a configurable port attribute parameter of the network node and/or the first node, so that a port attribute of the first node and the network node The parameters are consistent.

11. The network node of claim 10, wherein:

The port information acquired by the acquiring unit further includes: an identifier of the port, and a configurable characteristic of a port attribute parameter;

The second determining unit is configured to determine, according to the configurable characteristic of the network node and the port attribute parameter of the first node, the first node, the network node, when the determining result of the first determining unit is negative Whether the port attribute parameter of at least one node is configurable.

The network node according to claim 10 or 11, wherein the network node further comprises:

The first sending unit is configured to: when the determination result of the second determining unit is negative, send a notification message that the port attribute parameter is inconsistent.

13. A network node according to claim 10 or 11, characterized in that

The adjusting unit includes a notification message sending subunit, configured to: when the determining result of the second determining unit is yes, determine that the port attribute parameter of the first node needs to be changed to a unified parameter, and send a notification message to the first node. Instructing the first node to change a port attribute parameter, where the notification message includes: an identifier of a port that the first node needs to change a port attribute parameter, and the unified parameter;

Or,

The adjusting unit includes a modification subunit, and when the judgment result of the second judging unit is yes When determining your own port attribute parameters, you need to change to the uniform parameters and change your own port attribute parameters to the unified parameters.

A network system, comprising: a first node, a second node; the first node, configured to send port information of the first node to the second node; the port information includes a port attribute Parameter

A network system, comprising: a first node, a second node; the first node, configured to send port information of the first node to the second node; the port information includes a port attribute a parameter; changing the port attribute parameter after receiving a notification from the second node;

A network system, comprising: a first node, a second node; the first node, configured to send, to the second node, port information of the first node; the port information includes a port attribute And changing the port attribute parameter after receiving the notification from the second node;