WO2007134479A1

WO2007134479A1 - A method for coordinating automatic switched optical network link resoruce

Info

Publication number: WO2007134479A1
Application number: PCT/CN2006/000986
Authority: WO
Inventors: Desheng Sun
Original assignee: Zte Corporation
Priority date: 2006-05-16
Filing date: 2006-05-16
Publication date: 2007-11-29
Also published as: CN101218846B; CN101218846A

Abstract

A method for coordinating automatic switched optical network link resource comprises: link resource management part of network unit of service transmitting or receiving side acquires the status of channel occupy and link coordinating strategy from the corresponding link resource database according to the resource coordinating request of link, and transfers the service of coordinated channel to the corresponding target channel according to the coordinating strategy; link resource management part of service transmitting side transmits service on the coordinated channel and the target channel at the same time, and ends the service transmission of the coordinated channel until it determines that link resource management part of receiving side is switched to the target channel by changing information. The present invention realizes resource coordinating of the whole network link by combined transmitting service at service transmitting side and realizing switching at the service receiving side later, under the condition of non-damnification service, and by stepwise coordinating the free resource. The present invention has advantage that the present invention is simple and reliable.

Description

Automatic exchange optical network link resource sorting method

The present invention relates to the field of optical networks, and in particular, to a resource sorting method for automatically exchanging optical network links. Background technique

Optical networks, such as OTN (Optical Transmission Network), WDM (Wavelength-division multiplexing), SDH (Synchronous Digital Hierarchy), or SONET (Synchronous Optical Network) The network has been widely used in the field of telecommunications.

Automatic switched optical network (ASON) is a research hotspot in the field of optical networks in recent years. The ITU- TG.8080 recommendation proposes the concept of AS0N, which is implemented by setting up a special Control Plane (CP). ITU-TG.7713 recommends an implementation framework for distributed calls and connections in AS0N networks, providing implementation specifications for the automatic establishment, modification and deletion of calls and connections.

In recent years, the rapidly growing Internet business has grown in granularity, from the 100-megabit level to the current 1000-level. The optical network serves as the bearer layer of the user service. After the AS0N technology is introduced, the cascading mode can dynamically create services of different granularity according to user requirements. For example, an SDH optical network can bundle eight consecutive VC4s (high-order channels of SDH optical networks with a rate class of 155M, or VC4 for short) to carry Gigabit Ethernet services. However, AS0N continuously adds and deletes connections during the running process. Although there is idle VC4 on the last link, it is not continuous. For example, in the case shown in Figure 1, the maximum capacity of the fiber is 2. 5G, which provides 16 VC4 bearer capacity. The VC4 channel indicated by the solid line is already occupied, and the VC4 channel indicated by the dotted line is idle. Thus, although the maximum free capacity of the fiber is eight VC4s, it cannot carry services that need to cascade eight VC4s.

In this way, how to provide a method in the AS0N network to organize the scattered idle resources into a continuous resource area is very necessary. The following section of this article refers to "organizing scattered free resources into continuous resource areas" for "defragmentation" or "resource sorting." Invention disclosure

The technical problem to be solved by the present invention is to provide an automatic exchange optical network link resource collating party The law solves the technical problem that the current ASON network cannot provide resource sorting functions.

In order to achieve the above object, the present invention provides a method for collating an automatic switched optical network link resource, which is characterized in that: the link resource management component of the service sending end or the receiving end network element according to the resource sorting request of the link, Obtaining the channel occupancy status and the link organization policy of the link from the corresponding link resource library, and transferring the service of the channel to the corresponding target channel according to the sorting policy, and the link resource management component of the service sending end is in the The collated channel and the target channel simultaneously transmit services until the link resource management component of the service receiving end has switched to the target channel by the information exchange to stop the service transmission in the collated channel.

The above method is characterized in that: the channel occupation situation includes information of the occupied channel and the idle channel of the link to be collated, and if all the idle channels are continuous, the link resource collation ends.

The foregoing method is characterized in that: the sorting policy is dynamically selected or pre-configured by the network element, and the sorting policy includes: mode one, all occupied channels are arranged at the top of the link; and mode 2, the occupied channels are all arranged in The bottom end of the link; mode 3, the link resource management component determines one of the first mode or the second mode according to the principle of the minimum number of connected connections.

The above method is characterized in that it further comprises the following steps:

Step 1: The resource management component of the sending end/receiving end detects the resource sorting request of the link, and if it detects that the resource sorting request of starting a link is started, the process proceeds to the next step;

Step 2: The resource management component of the sending end/receiving end searches for the occupied channel, the idle channel, and the collating policy of the to-be-collected link from the local link resource library; if all the idle channels are continuous, the link resource collation ends. Otherwise, the network element is queried for the connection information corresponding to the occupied channel. Step 3: The resource management component of the sending end/receiving end determines the corresponding corresponding channel according to the queried connection information and the tidying policy. Target channels and sorting order;

Step 4: The link resource management component of the service sending end sends the service at the same time in the sorted channel and the target channel, until the link resource management component of the service receiving end has been switched to the target channel by the information exchange. The service of the sorted channel is sent, and the services of the sorted channels are switched to corresponding target channels by one by one or batch.

The above method is characterized in that, in the steps one, two, and three, the resource management component of the sending end/receiving end is a resource management component of the sending end, and the step four adopts a one-by-one manner, and the step four further Includes:

Step a, the resource management component of the sending end passes the channel and connection information that need to be collated this time. Knowing the resource management component of the receiving end, the resource management component of the receiving end determines whether the channel and the connection can be started, and returns response information;

Step b: The resource management component of the sending end determines whether the response information is agreed to be collated, and the resource management component of the sending end establishes a new subnet connection, and sends the service to the target while sending the service to the sorted channel. Channel, and sending the concurrent service message to the receiving resource management component; otherwise, the return link resource collation fails, and the link resource sorting process ends;

Step c: After receiving the concurrent service message, the receiving end resource management component modifies the subnet connection of the receiving service to receive the service from the target channel, notifies the link resource library of the updated information, and sends the message to the The resource management component of the end sends back the information that has been switched to the target channel;

Step d: The resource management component of the sending end deletes the subnet connection that sends the service to the to-be-scheduled channel, and the to-be-collected channel becomes an idle channel, and the target channel becomes a channel for carrying the service, and notifies the link resource library of the updated information;

Step e: Determine whether there are any remaining channels to be collated, if the resource management component of the sending end selects the remaining channels and connections to be collated, and proceeds to step a; otherwise, the link resource collation ends.

Step A: The resource management component of the sending end establishes a new subnet connection, sends the service to the target channel, sends the service to the target channel, updates the information to the link resource library, and the channel and connection information to be collated Notifying the resource management component of the receiving end;

Step B: The resource management component of the receiving end determines, according to the received information, whether the channel and the connection can be started. The subnet connection that modifies the receiving service receives the service from the target channel, and the updated information notifies the link resource library. And returning, to the resource management component of the sending end, the return information that agrees to start the collation and the service has been switched to the target channel; otherwise, returns the corresponding return information to the resource management component of the receiving end;

Step C: determining whether the returned information is agreed to start the collation and the service has been switched to the target channel, where the resource management component of the sending end deletes the subnet connection that sends the service to the channel to be collated, and the collating channel becomes the idle channel, and the target channel The channel is the bearer service, and the new link information is sent to the link resource pool; otherwise, the resource management component of the sending end deletes the subnet connection to the target channel to send the service, and returns the link resource collation failure to end the resource sorting process or Into step D; Step D determines whether there are any remaining channels to be collated, and the resource management component of the transmitting end selects the remaining channels and connections to be collated, and proceeds to step A or the link resource collation ends.

The above method is characterized in that, in the steps one, two, and three, the resource management component of the sending end/receiving end is a resource management component of the receiving end, and the step four adopts a one-by-one manner, and the step four further Includes:

Step a, the resource management component of the receiving end notifies the resource management component of the sending end of the channel and connection information that needs to be collated, and the resource management component of the sending end determines whether the channel and the connection can be started according to the received information. If it can be started, a new subnet connection is established, and when the service is sent to the collated channel, the service is sent to the target channel, the updated information is notified to the link resource library, and a corresponding response is returned to the resource management component of the receiving end. Information; if it can not be started, the shell U returns corresponding response information to the resource management component of the receiving end;

Step bl, the resource management component of the receiving end determines whether the response information is agreed to be collated and the service has been concurrently sent, and the resource management component of the receiving end modifies the subnet connection of the receiving service to receive the service from the target channel, and the updated information notification Linking the resource library, and sending the information that has been switched to the target channel to the resource management component of the sending end; otherwise, the returning link resource collation fails, and the link resource sorting process ends;

Step cl: The resource management component of the sending end deletes the subnet connection for sending the service to the channel to be collated, and the channel to be collated becomes the idle channel, the target channel becomes the channel for carrying the service, and the updated information is notified to the link resource library;

Step dl: determining whether there is any remaining channels to be collated, wherein the resource management component of the receiving end selects the remaining channels and connections to be collated, and proceeds to step a1 _; otherwise, the link resource collation ends.

The above method is characterized in that, in the steps one, two, and three, the resource management component of the sending end/receiving end is a resource management component of the sending end, and the step 4 adopts a batch mode, and the step 4 Further includes:

Step a2: The resource management component of the sending end notifies the resource management component of the receiving end of all the channels and connection information to be collated, and the resource management component of the receiving end determines whether the link can be started and returned according to the received information. Respond to information;

Step b2: determining whether the response information is agreed to be collated, wherein the resource management component of the sending end establishes a new subnet connection for all the connections to be collated, and sends the service to each of the connections while sending the service to the collated channel. Sent to the corresponding target channel, the updated information informs the link repository, and Sending, to the resource management component of the receiving end, information that the related connection service has been concurrently sent to the target channel; otherwise, the return link resource collation fails, and the link resource collation process ends;

Step c2: After receiving the information that the service has been concurrently sent to the target channel, the resource management component of the receiving end modifies the subnet connection of each connection receiving service, receives the service from each target channel, and updates the information to the link resource library. And returning, to the resource management component of the sending end, information that the service has been switched to the target channel;

Step d2: After receiving the information that the service has been switched to the target channel, the resource management component of the sending end deletes the subnet connection that each connection sends to the to-be-scheduled channel, and the to-be-collected channel becomes the idle channel, and the target channel becomes the channel for the bearer service. The updated link information is entered into the link resource library, and the link resource collation ends.

The above method is characterized in that, in the steps one, two, and three, the resource management component of the sending end/receiving end is a resource management component of the receiving end, and the step 4 adopts a batch mode, and the step 4 Further includes:

In step a3, the resource management component of the receiving end notifies the resource management component of the sending end of all the channels and connection information to be collated, and the resource management component of the sending end determines whether the link can be started according to the received information. Establishing a new subnet connection for all the connections to be tidy, sending the services carried by each connection to the corresponding target channel, and updating the information to the link resource library and to the receiving end The resource management component returns corresponding response information; otherwise, the corresponding response information is returned to the resource management component of the receiving end;

In step b3, it is determined whether the response information is agreed to be collated and the service is concurrent. The resource management component of the receiving end modifies the subnet connection of all the receiving and receiving services to receive the service from the target channel, and the updated information notifies the link resource. And sending, to the resource management component of the sending end, information that each service has been switched to the target channel;

Step c3: After receiving the information that the service has been switched to the target channel, the resource management component of the sending end deletes the subnet connection that each connection sends to the to-be-scheduled channel, and the to-be-collected channel becomes the idle channel, and the target channel becomes the channel for the bearer service. The updated link information is entered into the link resource library, and the link resource collation ends.

The above method is characterized in that, in the steps one, two, and three, the resource management component of the sending end/receiving end is a resource management component of the sending end, and the step 4 adopts a batch mode, and the step 4 Further includes: Step a4: The resource management component of the sending end establishes a new subnet connection for all the connections to be collated, sends the service carried by each connection to the target channel, and updates the information to notify the link resource. The library, and the resource management component of the receiving end is notified to the channel and connection information to be collated;

In step b4, the resource management component of the receiving end determines whether the link can be started according to the received information, and the subnet connection of each connection receiving service is modified to receive services from each target channel, and the updated information notification chain And returning the return information of each service to the target channel to the resource management component of the sending end; otherwise, returning the corresponding return information to the resource management component of the sending end;

In step c4, after receiving the information that the service has been switched to the target channel, the resource management component of the sending end deletes the subnet connection that each connection sends to the to-be-scheduled channel, and the to-be-collected channel becomes the idle channel, and the target channel becomes the channel for the bearer service. The updated link information is entered into the link resource library, and the link resource collation ends.

The advantages of the invention are:

The technology of the present invention is based on the link between the optical network elements, and the services are concurrently transmitted at the service sending end, and then the services are switched at the service receiving end, and the idle resources are gradually put together without damaging the service. , finally complete the defragmentation of the entire network, with the advantages of simplicity and reliability. BRIEF DESCRIPTION OF THE DRAWINGS

1 is a schematic diagram of resource occupancy of an optical network link;

2 is a schematic diagram of a link determining target channel and a sorting sequence of the present invention;

3 is a schematic diagram of the LRM-A boot link resource collation and preliminary negotiation with the LR-Z of the present invention; FIG. 4 is a schematic diagram of the LRM-A concurrent service of the present invention and notifying the LRM-Z;

Figure 5 is a schematic diagram of the LRM-Z switching service of the present invention;

6 is a schematic diagram of the LRM-A deletion original transmission SNC of the present invention;

Figure Ί is a flowchart of Embodiment 1 of the present invention;

Figure 8 is a flow chart of Embodiment 2 of the present invention;

Figure 9 is a flow chart showing a simplified embodiment of the embodiment of the present invention;

FIG. 10 is a flowchart of the first embodiment of the present invention after batch processing;

11 is a flowchart of the second embodiment of the present invention after batch processing; Fig. 12 is a flow chart showing a simplified embodiment of the first embodiment of the present invention after batch processing. The best way to implement the invention

The present invention will be further described in detail below with reference to the accompanying drawings and embodiments.

The present invention solves the problem that the current AS0N network cannot provide resource sorting function, and proposes an implementation strategy according to the prior art. The core of the present invention is based on the channel protection technology of the existing optical network, and the unoccupied resources are put together in the unit of the link between the optical network elements without damaging the existing services, and finally the entire Defragmentation of the network.

FIG. 1 is a schematic diagram of resource occupancy of an optical network link. FIG. 2 is a schematic diagram of determining a target channel and a sorting sequence of a link that needs to be sorted; FIG. 3 is an LRM of the A-side network element. -A is a schematic diagram of initiating a link resource collation and initial negotiation with the LRM-Z of the Z-end network element; FIG. 4 is a schematic diagram of the LRM-A concurrent service of the A-end network element and notifying the LRM-Z of the Z-end network element; 5 is a schematic diagram of the LRM-Z switching service receiving channel of the Z-end network element; FIG. 6 is a schematic diagram of the LRM-A of the A-side network element deleting the original transmitting SNC; FIG. 7 is a flowchart of Embodiment 1 of the present invention; FIG. 9 is a flow chart of a simplified embodiment of the present invention; FIG. 10 is a flow chart after batch processing according to Embodiment 1 of the present invention; FIG. 11 is a batch processing according to Embodiment 2 of the present invention; FIG. 12 is a flow chart of the simplified embodiment of the first embodiment after the batch processing;

Referring to FIG. 1 to FIG. 7, the first and third channels of FIG. 3 are occupied by the existing connection, and the links of the 2# and 4# channels are taken as an example, and an embodiment corresponding to the first embodiment is described.

The specific implementation includes the following steps:

Step 701: The LRM-A of the A-side network element of the link shown in Figure 3 detects that the resource-collating request of the link goes to the next step.

Step 702: The LRM-A searches from the LDB to the occupied channels 1# and 3# of the to-be-column link, and the idle channels 2# and 4#. LRM-A queries the other components of the network element for the connection information corresponding to 1# and 3#.

Step 703: The LRM-A queries the connection information according to step 702, and uses the collation strategy of the occupied resources at the top to determine the collation 3# channel, and the target channel is 2#. And select the connection corresponding to the 3# channel and go to the next step.

Step 704: The LRM-A notifies the LRM-Z of the Z-end network element of the 3# channel and the connection information to be collated. LRM-Z judges that the 3# channel and connection can be started according to the received information, and generates response information. Go back to LRM-A.

Step 705: The LRM-A receives the response information that the LRM-Z agrees to collate, and establishes a new SNC, that is, sends the service to the 2# channel while sending the service to the 3# channel, as shown in FIG. step. The updated information informs LDB. The service that sends the relevant connection to the LRM-Z has been concurrently sent to the 2# channel.

Step 706: After receiving the message that the LRM-A has concurrently sent the service, the LRM-Z modifies the received service.

SNC, which originally received the service from the 3# channel, will receive the service from the 2# channel after modifying the SNC. As shown in Figure 5. The updated information informs LDB. And return the information that the service has switched to the 2# channel to the LRM-A.

Step 707: After receiving the information of the LRM-Z, the LRM-A has switched to the information of the 2# channel. Delete the SNC that sends the service to the 3# channel, as shown in Figure 6. The 3# channel becomes the idle channel, and the 2# channel becomes the channel for the carrier service. The updated information informs LDB.

Step 708: There is no other channel to be collated, and the link resource collation ends. The occupied resources are 1# and 2# channels, and the unoccupied resources are 3# and 4#, each of which is continuous.

Referring to FIG. 1, 2, 3, 4, 5, 6, and 8, the first #3 and 3# channels shown in FIG. 3 are occupied by the existing connection, and the 2# and 4# channels are idle as an example, indicating the implementation. The second embodiment corresponds to the implementation.

The specific implementation includes the following steps: Step 801, the link shown in FIG. 3, the LRM-Z of the Z-end network element detects that the resource preparation request of the link is transferred to the next step.

Step 802: The LRM-Z searches from the LDB to the occupied channels 1# and 3# of the to-be-column link, and the idle channels 2# and 4#. L crawl -Z queries the other components of the network element for the connection information corresponding to 1# and 3#.

Step 803: The LRM-Z queries the connection information according to step 802, and uses the collation strategy of the occupied resources at the top to determine the collation 3# channel, and the target channel is 2#. And select the connection corresponding to the 3# channel and go to the next step.

Step 804: The LRM-Z notifies the LRM-A of the A-side network element of the 3# channel and the connection information to be collated. According to the received information, the LRM-A can start the sorting of the 3# channel and the connection, and establish a new SNC, that is, send the service to the 2# channel while sending the service to the 3# channel, as shown in FIG. Updated information Notify LDB. The service that sends the relevant connection to the LRM-Z has been concurrently sent to the 2# channel.

Step 805: After receiving the message that the LRM-A has agreed to collate and concurrently send the service, the LRM-Z judges that the resource can be started and the SNC of the received service is modified, that is, the service is received from the 3# channel, and the SNC is modified after the SNC. Channel receiving service. As shown in Figure 5. The updated information informs LDB. And return the information that the service has switched to the 2# channel to the LRM-A. Step 806: After receiving the information of the LRM-Z, the LRM-A has switched to the information of the 2# channel. Delete the SNC that sends the service to the 3# channel, as shown in Figure 6. The 3# channel becomes the idle channel, and the 2# channel becomes the channel for carrying the service. The updated information informs LDB.

Step 807: If there are no other channels to be collated, the link resource collation ends. The occupied resources are 1# and 2# channels, and the unoccupied resources are 3# and 4#, each of which is continuous.

Referring to FIG. 1, 2, 3, 4, 5, 6, and 9, the first #3 and 3# channels shown in FIG. 3 are occupied by the existing connection, and the 2# and 4# channel idle links are taken as an example to illustrate the implementation. The first method simplifies the corresponding embodiment.

The specific implementation of Figure 9 includes the following steps:

Step 901: The LRM-A of the A-side network element of the link shown in Figure 3 detects that the resource-collating request of the link goes to the next step.

Step 902: The LRM-A searches from the LDB to the occupied channels 1# and 3#, the idle channels 2# and 4# of the link to be collated. LRM-A queries the other components of the network element for the connection information corresponding to 1# and 3#.

Step 903: The LRM-A queries the connection information according to step 902, and uses the collation strategy of the occupied resources at the top to determine the collation 3# channel, and the target channel is 2#. And select the connection corresponding to the 3# channel and go to the next step.

Step 904: The LRM-A establishes a new SNC, that is, sends the service to the 2# channel while sending the service to the 3# channel, as shown in FIG. And execute the result and the 3# channel and connection information to be notified to notify the LRM-Z of the Z-side network element.

Step 905: After receiving the message that the LRM-A has concurrently sent the service, the LRM-Z modifies the received service.

SNC, which originally received the service from the 3# channel, will receive the service from the 2# channel after modifying the SNC. As shown in Figure 5. The updated information informs LDB. And the LRM-A returns the information that the service has switched to the 2# channel.

Step 906 _: LRM _: A receives the information that the LRM-Z service has switched to the 2tt channel. Delete the SNC that sends services to the 3# channel, as shown in Figure 6. The 3# channel becomes the idle channel, and the 2# channel becomes the channel for carrying the service. The updated information informs LDB.

Step 907: If there are no other channels to be collated, the link resource collation ends. The occupied resources are 1# and 2# channels, and the unoccupied resources are 3# and 4#, each of which is continuous.

Referring to Figures 1, 2, 3, 4, 5, 6, and 10, the link capacity and occupancy shown in Figure 3 are as shown in Figure 2, namely, #1, 3#, 5#, 8#, 9# and The 12# channel is occupied by the existing connection, and the 2#, 4#, 6#, 7#, 10#, and 11# channels are idle, for example, and the corresponding implementation scheme after the batch processing is used in the first embodiment. The specific embodiment of Figure 10 includes the following steps:

Step 101: The LRM-A of the A-side network element of the link shown in Figure 2 detects the resource-collating request of the link and moves to the next step.

Step 102: The LRM-A searches from the LDB to the occupied channels 1#, 3#, 5#, 8#, 9#, and 12# of the to-be-organized link, and the idle channels 2#, 4#, 6#, 7# , 10# and 11#. LRM-A queries the other components of the network element for the connection information corresponding to 1#, 3#, 5#, 8#, 9#, and 12#.

Step 103: The LRM-A queries the connection information according to the step, and uses the collation strategy of the occupied resources at the top to determine the collation 12#, 9#, 8# channels, and the target channels are 2#, 4#, and 6#.

Step 104: L body-A notifies the LRM-Z of the Z-end network element of all the 12#, 9#, 8# channels and connection information to be collated. The LRM-Z judges that the 12tt, 9#, and 8# channels and connections can be started according to the received information, and generates response information, and returns to the LRM-A.

Step 105, L-leg A receives the response information of the LRM-Z and organizes the new SNC, that is, sends the service to the ##, 9#, and 8# channels, and sends the service to 2#, 4# and 6# channel, the concurrent business situation is similar to the way shown in Figure 4, and proceeds to the next step. The updated information informs LDB. The service that sends the relevant connection to LRM-Z has been concurrently sent to the 2tt, 4# and 6# channels.

Step 106: After receiving the message that the LRM-A has concurrently sent the service, the LRM-Z modifies the SNC that receives the service, that is, the original service is received from the 12#, 9#, and 8# channels, and after the SNC is modified, the 2#, 4# and 6# channel receiving service. The way to switch channels is similar to the situation shown in Figure 5. The updated information informs LDB. And the LRM-A returns the information that the service has switched to the 2#, 4#, and 6# channels.

Step 107: After receiving the information of the L#-Z, the LRM-A has switched to the information of the 2#, 4#, and 6# channels. Delete the SNC that sends services to the 12#, 9#, and 8# channels, similar to the situation shown in Figure 6. The 9# and 8# channels become idle channels, and the 2#, 4#, and 6# channels become channels for carrying services. Updated information informs LDB. The link resource collation ends. The occupied resources are 1#, 2#, 3#, 4#, 5#, 6# channels, and the unoccupied resources are 7#, 8#, 9#, 10#, 11#, 12#, each of which is continuous. .

Referring to Figures 1, 2, 3, 4, 5, 6, and 11, when the capacity and occupancy of the link shown in Figure 3 is as shown in Figure 2, that is, #1#, 5#, 8#, 9 earned 12# The channel is occupied by the existing connection, and the 2#. 4#, 6#, 7# 10#, and 11# channel idle are taken as an example, and the corresponding implementation scheme after the batch processing is used in the second embodiment.

The specific implementation includes the following steps: Step 111: The LRM-Z of the Z-end network element of the link shown in FIG. 2 detects that the resource collation request of the link goes to the next step. Step 112: The LRM-Z searches from the LDB to the occupied channels 1#, 3#, 5#, 8#, 9#, and 12# of the to-be-organized link, and the idle channels 2#, 4#, 6#, 7# , 10# and 11#. LRM-Z queries the other components of the network element for the connection information corresponding to 1#, 3#, 5#, 8#, 9#, and 12#.

Step 113: The LRM-Z queries the connection information according to step 112, and uses the collation strategy in which the occupied resources are arranged at the top to determine the collation 12#, 9#, and 8# channels, and the target channels are 2#, 4#, and 6 #.

Step 114: The LRM-Z notifies the LRM-A of the A-side network element of the 12#, 9#, and 8# channels and connection information that need to be collated. LRM-A judges that the 12#, 9#, and 8# channels and connections can be started according to the received information, and a new SNC is established, that is, the service is sent to the 12#, 9#, and 8# channels, and the service is sent to 2 #, 4# and 6# channels, the concurrency situation is similar to the situation shown in Figure 4. The updated information informs LDB. The service that sends the relevant connection to the LRM-Z has been concurrently transmitted to the 2#, 4#, and 6# channels.

Step 115: After receiving the message that the L-body has agreed to collate and concurrently transmit the service, the LRM-Z determines that the resource can be started and modifies the SNC of the received service, that is, the service is received from the 12#, 9#, and 8# channels. After modifying the SNC, services will be received from the 2#, 4#, and 6# channels. The situation is similar to that shown in Figure 5. The updated information informs LDB. It also sends back information to the LRM-A that the service has switched to the 2#, 4#, and 6# channels.

Step 116: After the LRM-A receives the information of the LRM-Z and has switched to the information of the 2#, 4#, and 6# channels. The SNCs that send services to the 12#, 9#, and 8# channels are deleted, and the situation is similar to that shown in Figure 6. The 12#, 9#, and 8# channels become idle channels, and the 2#, 4#, and 6# channels become channels for carrying services. Updated information informs LDB. The link resource collation ends. The occupied resources are , 2#, 3#, 4#, 5#, 6# channels, and the unoccupied resources are 7#, 8#, 9#, 10#, 11#, 12#, each of which is continuous.

Referring to Figures 1, 2, 3, 4, 5, 6, and 12, the link capacity and occupancy shown in Figure 3 are as shown in Figure 2, namely, #1, 3#, 5#, 8#, 9# and The 12# channel is occupied by the existing connection, and the 2#, 4#, 6#, 7#, 10#, and 11# channels are idle, and the simplified implementation of the first embodiment adopts the corresponding implementation after the batch processing.

The specific implementation includes the following steps:

Step 121: The LRM-A of the A-side network element of the link shown in Figure 2 detects that the resource-collating request of the link goes to the next step.

Step 122: The LRM-A searches from the LDB to the occupied channels 1#, 3#, 5#, 8#, 9#, and 12# of the to-be-organized link, and the idle channels 2#, 4#, 6#, 7# , 10# and 11#. LRM-A queries the other components of the network element for the connection information corresponding to 11, 3#, 5#, 8#, 9#, and 12#. Step 123: The LRM-A queries the connection information according to step 122, and uses the collation strategy that the occupied resources are arranged at the top to determine the finishing channels ##, 9#, and 8#, and the target channels are 2#, 4#, 6#. .

Step 124: The LRM-A establishes a new SNC, that is, sends the service to the 2#, 4#, and 6# channels while transmitting the services to the 12#, 9#, and 8# channels, and the situation is similar to the case shown in FIG. And execute the results and the 12tt, 9tt and 8# channels and connection information that need to be sorted to inform the LRM-Z of the Z-side network element.

Step 125: After receiving the message that the LRM-A has concurrently sent the service, the LRM-Z modifies the SNC that receives the service, that is, receives the service from the 12#, 9#, and 8# channels, and after modifying the SNC, the slave will be 2#, 4# 6 #Channel receives business. The situation is similar to the situation shown in Figure 5. The updated information informs LDB. And return the information that the service has been switched to the 2#, 4#, 6# channels to the LRM-A.

Step 126: After receiving the information of the LRM-Z, the LRM-A has switched to the information of the 2#, 4#, and 6# channels. The SNCs that send services to the 12#, 9#, and 8# channels are deleted, similar to the situation shown in Figure 6. The 12#, 9#, and 8# channels become idle channels, and the 2# and 6# channels become channels for carrying services. Updated information informs LDB. The link resource collation ends. The occupied resources are 1#, 2#, 3#, 4#, 5#, 6# channels, and the unoccupied resources are 7#, 8#, 9#, 10#, 1 W, 12#, each of which is continuous. .

According to the analysis of the foregoing specific implementation manners, the present invention uses the link between the optical network elements as a unit to perform the service switching at the service receiving end, and then completes the service switching at the service receiving end without damaging the service. Gradually tidy up the idle resources and finally complete the resource sorting of the entire network link, which has the advantages of simplicity and reliability.

Of course, the present invention may be embodied in various other various modifications and changes without departing from the spirit and scope of the invention. Changes and modifications are intended to be included within the scope of the appended claims. Industrial applicability

The method of the present invention, in the unit of the link between the optical network elements, performs the service concurrently on the service sending end, and then completes the service switching at the service receiving end, and gradually frees the idle resources without damaging the service. Finished together, and finally complete the resource sorting of the entire network link, with the advantages of simplicity and reliability. The method of the present invention is suitable for resource sorting of automatically switched optical network links in the field of communications, and the method of the present invention is equally applicable to other fields in which similar applications exist.

Claims

Claim

A method for collating an automatic switched optical network link resource, comprising: a link resource management component of a service sending end or a receiving end network element, according to a resource sorting request of a link, from a corresponding link resource pool; Obtaining a channel occupation condition and a link organization policy of the link, and transferring the service of the channel to be corresponding to the corresponding target channel according to the sorting policy, and the link resource management component of the service sending end is in the sorted channel and the target The channel simultaneously transmits the service until the link resource management component of the service receiving end has switched to the target channel by the information exchange to stop the service transmission in the sorted channel.

2. The method according to claim 1, wherein the channel occupancy situation includes information of the occupied channel and the idle channel of the link to be collated, and if all the idle channels are continuous, the link resource collation ends. .

The method according to claim 1, wherein the tidying policy is dynamically selected or pre-configured by the network element, and the tidying policy includes: mode 1, all occupied channels are arranged at the top of the link; The occupied channels are all arranged at the bottom of the link. In the third manner, the link resource management component determines one of the first mode or the second mode according to the principle that the number of the connected connections is the smallest.

The method according to claim 1, further comprising the following steps: Step 1: The resource management component of the sending end/receiving end detects a resource sorting request of the link, and if it detects that a certain link is started Resource reorganization request, then move to the next step;

Step 2: The resource management component of the sending end/receiving end searches for the occupied channel, the idle channel, and the sorting policy of the to-be-collected link from the local link resource library; if all the idle channels have been continuous, the link resource is collated Ending, otherwise, the network element is queried for the connection information corresponding to the occupied channel; Step 3: The resource management component of the sending end/receiving end determines the corresponding corresponding channel according to the queryed connection information and the collating strategy Target channels and sorting order;

The method according to claim 4, wherein in the steps one, two, and three, the resource management component of the sending end/receiving end is a resource management component of the sending end, and the step 4 is In a one-by-one manner, the step four further includes:

Step a, the resource management component of the sending end notifies the resource management component of the receiving end of the channel and connection information that needs to be collated, and the resource management component of the receiving end determines whether the channel and the connection can be started, and returns a response. Information

The method according to claim 4, wherein in the steps one, two, and three, the resource management component of the sending end/receiving end is a resource management component of the sending end, and the step four is adopted one by one. The method, the step four step by step includes:

Step C: determining whether the returned information is agreed to start the collation and the service has been switched to the target channel, where the resource management component of the sending end deletes the subnet connection that sends the service to the channel to be collated, and the collating channel becomes the idle channel, and the target channel Become the channel for carrying services, and the new link information is chained. The resource management component of the sending end deletes the subnet connection for sending the service to the target channel, and returns the link resource collation failure to end the resource sorting process or proceeds to step D;

Step D determines whether there are any remaining channels to be collated, and the resource management component of the sending end selects the remaining channels and connections to be collated, and proceeds to step A, otherwise the link resource collation ends.

The method according to claim 4, wherein in the steps one, two, and three, the resource management component of the sending end/receiving end is a resource management component of the receiving end, and the step four is adopted one by one. The method, the step 4 further includes:

Step a, the resource management component of the receiving end notifies the resource management component of the sending end of the channel and connection information that needs to be collated, and the resource management component of the sending end determines whether the channel and the connection can be started according to the received information. If it can be started, a new subnet connection is established, and when the service is sent to the collated channel, the service is sent to the target channel, the updated information is notified to the link resource library, and a corresponding response is returned to the resource management component of the receiving end. Information; if it can not be started, the shell IJ returns corresponding response information to the resource management component of the receiving end;

Step dl: Determine whether there are any remaining channels to be collated, if the resource management component of the receiving end selects the remaining channels and connections to be collated, and proceeds to step al; otherwise, the link resource collation ends.

The method according to claim 4, wherein in the steps one, two, and three, the resource management component of the sender/receiver is a resource management component of the sender, and the batch is used in the step four. The method of step 4 further includes:

Step b2: determining whether the response information is agreed to be collated, and the resource management of the sending end is The component establishes a new subnet connection for all the connections to be collated, sends the service carried by each connection to the corresponding target channel, sends the service carried by each connection to the corresponding target channel, and the updated information informs the link resource library and receives the received information. The resource management component of the terminal sends the information that the related connection service has been concurrently sent to the target channel; otherwise, the return link resource collation fails, and the link resource collation process ends;

The method according to claim 4, wherein in the steps one, two, and three, the resource management component of the sending end/receiving end is a resource management component of the receiving end, and the batch is used in the step four The method of step 4 further includes:

In step b3, it is determined whether the response information is agreed to be collated and the service has been concurrently sent. The resource management component of the receiving end modifies the subnet connection of all the receiving and receiving services to receive the service from the target channel, and the updated information notifies the link resource. And sending, to the resource management component of the sending end, information that each service has been switched to the target channel;

10. The method according to claim 4, wherein in the steps one, two, three, The resource management component of the sending end/receiving end is a resource management component of the sending end, and the step 4 adopts a batch mode, and the step 4 further includes:

Step a4: The resource management component of the sending end establishes a new subnet connection for all the connections to be collated, sends the service carried by each connection to the target channel, and updates the information to notify the link resource. The library, and the resource management component of the receiving end is notified to the channel and connection information to be collated;

Step b4, the resource management component of the receiving end determines, according to the received information, whether the link can be started, and the subnet connection that modifies the connection receiving service receives the service from each target channel, and the updated information notifies the link resource. And returning, to the resource management component of the sending end, the return information that each service has switched to the target channel; otherwise, the resource management component of the sending end also returns corresponding return information;