Abstract:
The present invention discloses a method for implementing link state passing-through in network, for informing the peer of link fault, said method comprising the following steps: the service device detecting whether there is a link fault in the network; in case of link fault, the service device transferring link fault information to peer service device with a control frame; in response to said control frame containing link fault information, the peer service device disconnecting the user&#39;s link and performing corresponding processes; the user at the faulty peer communicating with peer user through the spare network; when said link recovers to normal, the service device at the recovery peer sending a control frame containing link fault recovery information to peer service device to reestablish communication between said users on said link. The present invention is capable of informing the peer of link fault and reducing extra overhead under normal network conditions as much as possible.

Description:
FIELD OF THE INVENTION  
       [0001]     The present invention relates to network communication, in particular to a method for implementing passing-through of access point link state and service link state in point-to-point access network.  
       BACKGROUND OF THE INVENTION  
       [0002]     In engineering applications, the data between users enters into the network via access devices, in order to implement data interaction.  FIG. 1  is a schematic diagram of data interaction by user through a point-to-point access network. As shown in  FIG. 1 , under normal conditions, user  1  and user  2  establish communication with each other through service devices and links; said links mainly comprise access point link  1 , service network, and access point link  2 . In case the links are faulty, i.e., either the access point links or the service network are faulty, the communication between user  1  and user  2  will be interrupted. For important users, in case of such faults, the spare network has to be initiated to ensure normal transmission of important data. The spare network may be in any form, e.g., an additionally leased link, or a wireless communication or satellite communication link established between user  1  and user  2 . In case the access point link is faulty, the user can detect link fault and initiate the spare network, trying to communicate with the remote user through the spare network. However, at that time, the remote user does not know the link fault and still communicates through the original network; as a result, the communication between the two users will be in a disconnecting state. In case the service network is faulty, neither of the users knows the network is out of service; as a result, the communication will be disconnected. If the link state can be delivered to the remote user, i.e., link state passing-through function can be achieved, the remote user can initiate the spare network and reestablish the linking with user  1  or user  2  through the spare network.  
         [0003]     There are diverse ways to inform the remote user of link fault. A typical method is: user  1  and user  2  inform the linking information at the local to remote peer through periodical peer-to-peer inform; in case there is no linking information sent from the remote user for long, it indicates the link is faulty; in that case, the user stops the peer-to-peer inform of linking information and automatically initiates the spare network to communicate. Another typical method is: user  1  and user  2  detect the using of the spare network in real time; as long as the using of the spare network is detected, the other party will also switch to the spare network.  
         [0004]     Though above methods can solve the problem to a certain degree, they have some drawbacks: first, normally the periodical peer-to-peer inform of linking information will occupy network bandwidth and result extra network overhead; second, in case of network congestion, the peer-to-peer inform of linking information will be delayed and may result in misoperation due to a wrong judgment; third, detection of the spare network will occupy some bandwidth of the spare network and result in extra overhead of the network; fourth, when the links recover to normal, it is a trouble that how the two users leave the spare network and return to the working network.  
       SUMMARY OF THE INVENTION  
       [0005]     To overcome above drawbacks in prior art, the present invention provides a method for implementing link state passing-through in the network, which is capable of informing remote peer of link fault and reducing extra overhead during normal network operation as much as possible.  
         [0006]     To attain above object of the present invention, there is provided a method for implementing link state passing-through in the network comprising: the service device detecting whether the link in the network is faulty; if the link is faulty, the service device transmitting link fault information to the remote service device with a control frame; in response to the received control frame containing link fault information, the remote service device disconnecting the user&#39;s link and performing corresponding processes; and the user at the faulty peer communicating with the remote user through the spare network.  
         [0007]     The method described in the present invention also comprises the following step:  
         [0008]     When the said link recovers to normal, the service device at the recovering peer sends a control frame containing link fault recovery information to the remote service device, and reestablishes the communication between said users through said link.  
         [0009]     Control frame contains at least network state information, which indicates whether there is a link fault. Control frame may be a standard Ethernet frame, with said network state information filled in the operation code field of said standard Ethernet frame; an encapsulation protocol control frame, with said network state information filled in the control field of said encapsulation protocol control frame; or a signal label byte, with said network state information filled in it.  
         [0010]     Step A further comprises the following steps for de-dithering treatment:  
         [0011]     judging the link is faulty only when the link is unavailable for a predefined time period; and  
         [0012]     judging the link recovers to normal only when the link is available for a predefined time period.  
         [0013]     If said link fault is an access point fault, the service device at the faulty peer sends a control frame containing access point fault information to the remote service device; when receiving said control frame containing access point fault information, said remote service device disconnects the connection with the remote user; and then, the user at the faulty peer communicates with the remote user through the spare network;  
         [0014]     if said link fault is a service network fault, the service device at the faulty peer sends a control frame containing service network fault information to the remote service device and disconnects the link with the user at the faulty peer; when receiving said control frame containing service network fault information, said remote service device disconnects the connection with the remote user; and then the user at the faulty peer communicates with the remote user through the spare network.  
         [0015]     In case the link fault is a service network fault, the processing steps corresponding to the service network fault are performed only after determining the protection function of said service network per se fails.  
         [0016]     The present invention has the following benefits: 1) when the link works normally, no control frame will be sent for controlling, and thereby the bandwidth of the working network and the spare network will not be occupied, reducing extra overhead; 2) utilizing the control frame mechanism to control link disconnection and recovery has no side effect to the original network, and thereby facilitates network upgrade and maintenance; 3) in the present invention, “de-dithering” treatment is used for judgment of link fault and recovery, enhancing network&#39;s reliability and ease of use. 
     
    
     BRIEF DESCRIPTION OF THE DRAWINGS  
       [0017]      FIG. 1  is a schematic diagram of data interaction by user through a point-to-point access network;  
         [0018]      FIG. 2  is a flow block diagram of the method for link state passing-through as described in the present invention;  
         [0019]      FIG. 3  is a process diagram of link state passing-through in standard mode as described in an embodiment of the present invention;  
         [0020]      FIG. 4  is a process diagram of link state passing-through in extended mode as described in an embodiment of the present invention;  
         [0021]      FIG. 5  is a timing diagram of de-dithering treatment as described in an embodiment of the present invention;  
         [0022]      FIG. 6  is a diagram of alarm and event reporting as described in an embodiment of the present invention;  
         [0023]      FIG. 7  is a diagram showing the state transition implemented through link passing-through as described in an embodiment of the present invention;  
         [0024]      FIG. 8  is a schematic diagram showing the composition of a control frame as described in an embodiment of the present invention;  
         [0025]      FIG. 9  shows a network structure to which the link state passing-through method as described in the present invention can be applied;  
         [0026]      FIG. 10  shows another network structure to which the link state passing-through method as described in the present invention can be applied. 
     
    
     DETAILED DESCRIPTION OF THE EMBODIMENTS  
       [0027]      FIG. 2  is a general technical flow diagram of the method for link state passing-through as described in the present invention. As shown in  FIG. 2 , first, the service device detects whether the link in the network is faulty S 1 ; if the link is faulty S 2 , the service device at the faulty peer transfers a link fault information to the remote service device through the service network with a control frame S 3 ; when receiving the control frame from said service device, the remote service device performs corresponding processes S 4 ; then, the user at the faulty peer communicates with the remote user through the spare network S 5 .  
         [0028]     Control frame may be defined in different ways. Hereunder 3 ways are introduced.  
         [0029]     (1) Define a Control Frame Using a Standard Ethernet Frame and Implement Link State Passing-Through Function  
         [0030]     In an IP OVER SDH network, a user is an Ethernet switch, and a service device is a SDH Ethernet access device. First, the control frame shown in  FIG. 8  is defined in an Ethernet frame format; the control frame comprises:  
         [0031]     Destination address (6 bytes): globally unique Media Access Control (MAC) address;  
         [0032]     Source address (6 bytes): globally unique MAC address;  
         [0033]     Type field (2 bytes): 0xE140—indicates the frame is a control frame for link state passing-through function;  
         [0034]     Operation code field (2 bytes):  
         [0035]     0x0000—network fault disappears (Non_Broken message),  
         [0036]     0x0200—network is faulty (Broken message);  
         [0037]     Padding field (44 bytes): filled with padding bytes;  
         [0038]     Check field (4 bytes): filled with cyclic redundancy Crc32 check value of Ethernet.  
         [0039]     Second, several time parameters are defined; for reference, T0=500 ms, T1=1˜5 s, T2=5˜10 s, T3=20 ms˜1 s, and T4=30 s˜300 s can be used.  
         [0040]     After the control frame format and time parameters are defined, the service device detects working condition of the service network and linking condition of the access point link, and carries out control as described above, to implement link state passing-through function.  
         [0041]     In view that the faulty points are sometimes needed to be distinguished in network maintenance to facilitate the network maintenance, the operation code field shall be extended. The extended operation codes are defined as:  
         [0042]     0x0000—access point fault disappears (Non_Broken message),  
         [0043]     0x0100—service network fault disappears (Non_Broken message),  
         [0044]     0x0200—access point is faulty (Broken message);  
         [0045]     0x0300—service network is faulty (Broken message);  
         [0046]     When the faulty peer detects an access point fault, it will send an access point fault message; if it detects a service network fault, it will send a service network fault message. The device can choose whether to support extended operation codes or not.  
         [0047]     (2) Use Encapsulation Protocol Control Frame to Implement Link State Passing-Through Function  
         [0048]     When encapsulation protocol is used to implement link state passing-through function, a control field in encapsulation protocol can be used to define the control frame. If link access regulation-SDHLAPS/Peer-to-Peer Protocol PPP/High Digital Link Control HDLC encapsulation protocol is used, the control field can be defined as follows:  
         [0049]     0x70—network fault disappears (Non_Broken message), 0x72—network is faulty (Broken message);  
         [0050]     Normally, the control field is filled with the default control value. In case of link fault, the device at the faulty peer will fill a control value with above special meaning into the control field, to inform the remote device of the current link state. When the remote device receives the control value that represents link fault, it will carry out treatment according to the control value. When the link recovers, the device will send normal control value.  
         [0051]     Similarly, the device may choose to use extended control values; the extended control field is defined as follows:  
         [0052]     0x70—access point fault disappears (Non_Broken message), 0x71—service network fault disappears (Non_Broken message), 0x72—access point is faulty (Broken message), 0x73—service network is faulty (Broken message);  
         [0053]     (3) In SDH, Use Signal Label Byte to Implement Link State Passing-Through Function  
         [0054]     The signal label is defined in particular as follows:  
         [0055]     0x70—network fault disappears (Non_Broken message), 0x72—network is faulty (Broken message);  
         [0056]     The extended definition is as follows:  
         [0057]     0x70—access point fault disappears (Non_Broken message), 0x71—service network fault disappears (Non_Broken message), 0x72—access point is faulty (Broken message), 0x73—service network is faulty (Broken message);  
         [0058]     In SDH, the signal label is transmitted using byte C 2 /V 5  in channel overhead.  
         [0059]     For VC3/VC4 level services, normally byte C 2  is used to transmit the normal value of signal label. In case of link fault, the device at fault detection peer will transmit link fault C 2  value to inform the remote device of the current link state. When the remote device receives byte C 2  representing link fault, it should not send a signal mismatch alarm; instead, it shall execute link state passing-through function and carry out state transfer according to the state machine of the link state passing-through function. After the link at the faulty peer recovers and the device returns to normal working state, the device will resend normal C 2  value.  
         [0060]     For VC1/2 level services, byte V 5  is used to transmit a control frame for link state passing-through function, with the working mechanism identical to that for VC3/VC4 level services. It is to be noted that normally bits  5 ˜ 7  in byte V 5  is used to transmit the normal signal label. Since the link state passing-through function is added, byte V 5  is needed to be used extensively. According to the standard, when extensively used, bits  5 ˜ 7  in byte V 5  is filled with 101, and the extended signal label is filled into bit  1  in byte K 4 ; the bits  1  in K 4  of 32 frames constitute a 32 bit string, using bits  12 ˜ 19  to transmit the extended signal label.  
         [0061]     1. Link State Passing-Through in Access Point Fault Mode  
         [0062]      FIG. 3  is a process diagram of link state passing-through in standard mode as described in an embodiment of the present invention; as shown in  FIG. 3 , the processing steps are as follows:  
         [0063]     At t 0 , the link between user  1  and service device A is faulty. Service device A sends consecutive Broken primitives to the remote service device B, informing service device B of the link fault at the local; the primitives is in control frame format.  
         [0064]     At t 1 , service device B receives the link fault Broken primitives; after processing it, service device B knows link is faulty at service device A and thereby disconnects the link with user  2 ; the linking state of link between user  1  and service device A passes-through to the linking state of link between service device B and user  2 . At this time, user  1  and user  2  can use the spare network to communicate with each other.  
         [0065]     At t 2 , the link between user  1  and service device A is recovered; at this time, service device A sends Non_Broken primitive to service device B, informing service device B of the link recovery at the local.  
         [0066]     At t 3 , service device B receives the Non_Broken primitive; after processing it, service device B knows the link fault at service device A has been eliminated, and thereby reestablishes the link with user  2  in the original network.  
         [0067]     2. Link State Passing-Through in Service Network Fault Mode  
         [0068]      FIG. 4  is a process diagram of link state passing-through in extended mode as described in an embodiment of the present invention; as shown in  FIG. 4 , the processing step are as follows:  
         [0069]     At t 0 , service device A detects the service network is unavailable, and sends Broken primitive to the remote peer and disconnects the link with the user at the local;  
         [0070]     At t 1 , service device receives the Broken primitive and then disconnects the link with user  2 ; after that, user  1  and user  2  use the spare network to communicated with each other, till the service network is recovered.  
         [0071]     It is noted that the service network usually has its own network protection function, having certain network protection capability. To avoid disorder, the link state passing-through function is required to be initiated late, i.e., initiated only after the protection function of the service network is determined as faulty.  
         [0072]     3. De-Dithering Treatment of Link State Passing-Through Function  
         [0073]     In implementation of the link state passing-through function, misoperation may occur if the link state is not stable (dithering). In order to eliminate link dithering, de-dithering treatment may be carried out.  FIG. 5  is the timing diagram of de-dithering treatment as described in an embodiment of the present invention; as shown in  FIG. 5 , the major processing steps are:  
         [0074]     judging the link as faulty only when the link is unavailable for a period of time T 0 ; if the link fault duration is less than T 0 , keeping the original link state;  
         [0075]     judging the link as normal only when the link is available for a period of time T 0 .  
         [0076]     4. Alarms and Events During Implementation of the Link State Passing-Through Function  
         [0077]     During the link state passing-through process, various situations shall be monitored and reported.  FIG. 6  shows the alarms and events during implementation of the link state passing-through function; as shown in  FIG. 6 , the main contents are:  
         [0078]     □. when the service device detects access point link fault, it reporting an access point fault alarms; it stopping alarm reporting only when it detects the access point link fault disappears;  
         [0079]     □. when the service device receives the Broken control frame for the first time, it reporting a remote peer link fault event; similarly, when receiving the Non_Broken control frame for the first time, it reporting a remote peer link fault disappearing event;  
         [0080]     □. when the service device detects service network fault, it reporting the event with an existing alarm in the service network or with a special alarm.  
         [0081]     5. State Machine Transfer of Link State Passing-Through Function  
         [0082]     There are many states for the link state passing-through function. As the link conditions change, those states can transfer between each other. Hereunder the various states and their transfer for link state passing-through function are detailed, with reference to  FIG. 7 .  FIG. 7  is a state transition diagram implemented with the link passing-through function as described in an embodiment of the present invention; as shown in  FIG. 7 , the detailed implementation steps of link state passing-through function consist of a state machine with 4 basic states; said  4  basic states are defined as follows:  
         [0083]     Normal-working state: both the access points and the service network are in normal state;  
         [0084]     Waiting-for-recovery state: after the service device receives Broken control frame, it enters into waiting-for-recovery state;  
         [0085]     Access-point-faulty state: the path between a user and the service device is faulty, and normal communication between the user and the service device could not be performed;  
         [0086]     Service-network-faulty state: the service network between the service devices is faulty, and normal communication could not be performed.  
         [0087]     The state transition process is summarized as follows:  
         [0088]     Normal-working state:  
         [0089]     1) If detecting the service network is unavailable for a period of time T 0 , a device will send Broken control frame to the remote device, informing the remote device that the local has detected the service network is unavailable, and then enter into service-network-faulty state;  
         [0090]     2) If detecting the access point network is unavailable for a period of time T 1 , the device will send Broken control frame to the remote device, informing the remote device that the local has detected the access point network is unavailable, and then enter into access-point-faulty state;  
         [0091]     3) If receiving Broken control frame, which indicates the local network is faulty, the local service device will disconnect linking with the user, and then enter into waiting-for-recovery state;  
         [0092]     Waiting-for-recovery state: if a device enters into this state, it is indicated that the device has received Broken control frame. In that case, the access point network at the local may be normal; therefore, linking to the access point network should not be tried.  
         [0093]     1) If the device detects that the service network is unavailable for a period of time T 0 , it will send Broken control frame to the remote device, informing the remote device that the local has detected the service network is unavailable, and then enter into service-network-faulty state; this step is optional;  
         [0094]     2) The device disconnects the link with the user in a time interval T 1 , to avoid an accident in which the service device does not disconnect the link to the user; if it can be ensured that the linking between the device and the user&#39;s access point disconnected before entering into waiting-for-recovery state, this step is also optional;  
         [0095]     3) If the device has not received Broken message for a period of time T 2 , it is possible that the remote peer has entered into normal-working state or waiting-for-recovery state; in that case, the device at the local should link the access point link with the user and return to normal-working state actively, to avoid deadlock;  
         [0096]     4) If the device receives Non_Broken control frame, which indicates the remote peer has recovered from the link fault to normal-working state, it should link the access point link with the user and then enter into normal-working state;  
         [0097]     5) If the device receives Broken message, which indicates the link of the remote device is still in fault state, T 2  will be recounted;  
         [0098]     Service-network-faulty state: When a device enters into this state, it is indicated that the service network fault has been detected.  
         [0099]     1) The device continues checking whether the service network is normal; if the service network is still faulty, the device will send Broken message every T 3  to inform the remote device of the service network fault (regardless whether or not the remote device can receive the message);  
         [0100]     2) The device continues checking whether the service network is normal; if there is no fault in the service network for a period of time T 0 , it indicates the service network has recovered to normal; in that case, the device will send Non_Broken message to the remote peer and return to normal-working state directly, and start a new detection.  
         [0101]     Access-point-faulty state: when a device enters into this state, it is indicated that an access point fault at the local has been detected. In that case, it is required to try to recover the access point link periodically.  
         [0102]     1) The device checks the service network state at the local; if the service network is detected as unavailable, the device will send Broken message and enter into service-network-faulty state; this step is optional;  
         [0103]     2) T 1  and T 4  periods are alternated; during T 1  (it shall at least ensure the time required for normal linking between the service device and the user), the device tries to link the access point link; if the linking is successful, the device will send Non_Broken control frame to the remote peer and then enter into normal-working state; otherwise it will disconnect the access point link again and enter into T 4  stage; during T 4 , the service device sends Broken message to the remote peer every T 3 , to inform the remote peer of the network fault at the local; after T 4  stage, the device will reenter into T 1  stage;  
         [0104]     3) If the device receives Broken control frame, which indicates the service network or the remote access point is faulty, T 4  will be recounted;  
         [0105]     4) If the device receives Non_Broken message, it is indicated that the remote network has recovered; in that case, the device at the local shall enter into T 1  stage immediately and try to recover the network linking.  
         [0106]     Though the present invention is described with reference to specific embodiments as above, it is understood that the present invention shall not be limited to those embodiments. For instance, in above embodiment, the link state passing-through technique is applied in the network structure shown in  FIG. 1 . However, that technique is also applicable to network structures in other forms.  FIG. 9  and  FIG. 10  show two network structures where the link passing-through technique described in the present invention can be applied. As shown in  FIG. 9 , the first type of network structure is: user  1  and user  2  can activate a service with two ports; said two ports may be one working and the other spare or serve as working/spare for each other. In that case, link state passing-through function can be applied to both ports. However, when the service network is faulty, the communication between user  1  and user  2  will still be disconnected. As shown in  FIG. 10 , the second type of network structure is: the working link and the spare link are in different networks, completely independent of each other. User  1  activates the service at service device A 0  and service device A 1 , respectively; likewise, user  2  activates the service at service device B 0  and service device B 1 . Under normal conditions, user  1  and user  2  communicate with each other through service network  0 ; in case of fault, user  1  and user  2  communicate with each other through service network  1 . Such structure can ensure communication between the users even when service network  0  is faulty. Therefore, the scope of the present invention is only defined by the Claims, and any modification or transformation to the present invention can be made without departing from the spirit and scope of the present invention.