CN100426745C - Method for tracing oppsite end narrow-band signaling link break reson and broken state - Google Patents

Abstract

The present invention relates to a method for tracking the cause of disconnection of the peer narrowband signaling link and the status of the disconnection, which is applicable to the MTP2 narrowband signaling link, including: defining the code of the cause of the disconnection and the extension code of the cause of the disconnection; defining the disconnection of the link Reason bit and link-break reason extension bit; when the local MTP2 entity breaks the link, fill the link-break reason code into the link-break cause bit, and the link-break reason extension code into the link-break cause extension bit, and send it to the peer end along with the SIOS message MTP2 entity: After receiving the SIOS message, the opposite end MTP2 entity takes out and analyzes the link disconnection cause bit and the link disconnection cause extension bit, decodes the link disconnection cause and the status of the link disconnection and reports it to the opposite end MTP3 or OAM. Adopting the present invention, when the opposite end MTP2 entity actively breaks the link, the exact cause and context information of the opposite end link breaking can be easily known at the local end, so that corresponding measures can be taken to solve the problem, making remote debugging possible and helping to speed up the remote end The progress of troubleshooting.

Description

A method for tracking the cause of disconnection of the peer-end narrowband signaling link and the status of the disconnection

technical field

The present invention relates to the implementation method of the No. 7 signaling system, in particular to tracking the cause of the disconnection of the peer-end narrowband signaling link and the status of the disconnection at the protocol layer of the message transfer part 2 (Message Transfer Part 2) (hereinafter referred to as MTP2) Methods.

Background technique

MTP2 is the link layer protocol of the narrowband SS7 system, which provides point-to-point reliable message transmission services. It has been widely used, and its typical application protocol stack is shown in Figure 1.

The normal operation of the MTP2 narrowband signaling link and the service state are the prerequisites for the normal operation of all narrowband No. 7 upper-layer signaling protocol entities. Therefore, once a narrowband signaling link is disconnected, it is necessary to locate the exact cause and current status of the disconnection, so as to take corresponding measures to solve it.

The current MTP2 protocol (International Communication Standard Protocol ITU-T Q.703) stipulates that when the near-end MTP2 entity of the narrowband signaling link is disconnected, it will send an exit service message (hereinafter referred to as SIOS message) to the remote MTP2 entity, and Report the disconnection event to the near-end Message Transfer Part 3 (hereinafter referred to as MTP3), and trigger the corresponding disconnection processing flow of the near-end MTP3. After receiving the SIOS message, the remote MTP2 entity reports a link disconnection event to the remote MTP3, triggering a corresponding link disconnection processing procedure of the remote MTP3.

It can be seen from the disconnection processing flow described above that when the near-end MTP2 entity is disconnected, it can conveniently report the cause of the disconnection and the current status to the near-end MTP3 or Operation And Maintenance (hereinafter referred to as OAM) ), the near-end upper-layer signaling protocol entity or network management can easily understand the cause of the disconnection of the narrowband signaling link and the status of the disconnection, so as to take corresponding measures to solve it. However, because the SIOS message in the MTP2 protocol does not define a field for storing information related to link disconnection, the remote MTP2 entity can only know that the near-end request link disconnection after receiving the SIOS message, and the remote MTP3 or OAM cannot know the status of the near-end link disconnection. The exact cause and current status. Because in the actual networking application environment, the two ends of the MTP2 narrowband signaling link may be far apart physically, and when the near-end MTP2 entity is disconnected, the near-end link disconnection information may be temporarily difficult to obtain at the far end. Some reasons can only be analyzed and located at the remote end, which will affect the progress of problem solving. It can be seen that remote debugging is a very necessary auxiliary positioning method, but the current MTP2 protocol cannot meet the needs of remote debugging, and no patents and documents that can solve the above-mentioned prior art problems have been retrieved yet.

Contents of the invention

For the defects existing in the above-mentioned background technology, the purpose of the present invention is to provide a method for tracking the cause of the disconnection of the opposite end narrowband signaling link and the state of the disconnection, which is applicable to the MTP2 narrowband signaling link, so that the opposite end MTP2 entity When a link break occurs actively, the local end can easily know the exact cause and context information of the peer end link break, and then take corresponding measures to solve it, making remote debugging possible and helping to speed up the progress of remote fault resolution.

In order to achieve the above object, a kind of method of the present invention tracks the cause of the disconnection of the peer narrowband signaling link and the state of the disconnection, is applicable to the MTP2 narrowband signaling link, and the method comprises the following steps:

Step 1: The MTP2 entity at the local end defines the link-break reason code and the link-break cause extension code;

Step 2: The above-mentioned local MTP2 entity defines the disconnection reason bit and the disconnection reason extension bit in the SIOS message of the MTP2 protocol;

Step 3: When the above-mentioned local MTP2 entity is disconnected, fill in the code corresponding to the cause of the disconnection into the disconnection cause bit of the above SIOS message, and fill in the extension code corresponding to the status or sub-reason of the disconnection in the link-breakage reason extension bit , and send it to the peer MTP2 entity along with the above SIOS message; the code corresponding to the above-mentioned link-break reason is the above-mentioned link-break reason code, and the extension code corresponding to the above-mentioned link-break state or sub-reason is the above-mentioned link-break cause extension coding;

Step 4: After receiving the above SIOS message, the peer MTP2 entity takes out and analyzes the disconnection cause bit and the disconnection cause extension bit, and decodes the above link disconnection reason and status or sub-reasons into primitives or primitives A part of the language is reported to the peer MTP3 or OAM, and is processed by the peer MTP3 or OAM.

Wherein, the above step 1 includes the following steps:

Step 101: The above-mentioned local MTP2 entity defines a link-break reason code for all possible link-break reasons that appear in the MTP2 protocol and have nothing to do with the specific implementation mode;

Step 102: The above-mentioned local MTP2 entity judges whether the above-mentioned link disconnection reason has only one state, and if so, defines the link-breakage reason extension code for the sub-reason of the link-breakage reason; otherwise, defines all states occurring under the above-mentioned link-breakage reason Extended encoding of the cause of the link break.

The above step 2 includes the following steps:

The above-mentioned local MTP2 entity extends the SIOS message of the MTP2 protocol, and defines the link disconnection cause bit and the link disconnection cause extension bit in the spare field (hereinafter referred to as the Spare field) therein.

Wherein the method for defining the link-break cause bit and the link-break reason extension bit in the Spare field of the above-mentioned SIOS message is at least:

Use the SIOS message with a State Field (hereinafter referred to as SF) length of 16 bits, define the low 1st to 4th bits of its high-order byte as the cause of link disconnection, and define the low 5th to 7th bits of its high-order byte Defined as the link break reason extension bit.

The method for tracking the disconnection cause and status of the peer narrowband signaling link provided by the present invention is applicable to the MTP2 narrowband signaling link, and can be easily understood at the local end when the peer MTP2 entity is disconnected The exact cause and context information of the disconnection of the peer end can be obtained, so that corresponding measures can be taken to solve it, making remote debugging possible and helping to speed up the progress of remote fault resolution.

The specific implementation of the method of the present invention will be further described in detail below in conjunction with the accompanying drawings. The above and other objects, features and advantages of the present invention will be apparent to those skilled in the art from the detailed description of the method of the present invention.

Description of drawings

Fig. 1 is the position diagram of the MTP2 agreement involved in the present invention in the narrowband No. 7 signaling system;

Fig. 2 is the realization flowchart of the present invention;

Fig. 3 is the link state signaling unit (Link StateSignal Unit) (hereinafter referred to as LSSU) format diagram, SIOS message definition diagram and the SIOS message of existing MTP2 agreement in step 2 of the present invention to carry out in the MTP2 agreement that the present invention relates to Schematic diagram of a feasible scheme of extending, defining the link-break cause bit and the link-break cause extension bit in its Spare field.

Detailed ways

The technical solutions of the present invention will be described in detail below in conjunction with embodiments and with reference to the accompanying drawings.

Fig. 2 is the implementation flow chart of the present invention, as shown in Fig. 2, a kind of method for tracking the disconnection cause of the peer narrowband signaling link and the state of the disconnection according to the present invention is applicable to the MTP2 narrowband signaling link , including the following steps:

Step 1: The MTP2 entity at the local end defines the link-break reason code for all possible link-break reasons that appear in the MTP2 protocol and has nothing to do with the specific implementation; If there is only one possible state for the cause of the disconnection, define the extension code of the disconnection reason for the sub-reason of the disconnection reason;

Among them, the "all possible" requirement is to track the integrity of the cause of the disconnection of the peer end, and will not miss any reason for the disconnection stipulated in the MTP2 protocol; the requirement of "unrelated to the specific implementation method" is for compatibility between different manufacturers. , for example, "send buffer overflow causing link disconnection" should not be defined as a separate link disconnection reason for encoding, because MTP2 implementations of different manufacturers do not necessarily stipulate that the link must be disconnected in this case, but such link disconnection reasons can be used as a "Other" disconnection reasons are coded to ensure that the disconnection reason definition scheme can cover all possible disconnection events; the disconnection reason coding indicates a specific disconnection reason, because MTP2 entities may have the same disconnection in different states The reason is that it is necessary to obtain the state of the MTP2 entity when a link break occurs, so it is necessary to expand the code for the state of the MTP2 entity when a link break occurs; if there is only one possible cause of the link break state, the sub-reasons of this link-breaking reason can be expanded and coded to obtain more detailed and specific link-breaking reasons; all possible link-breaking reasons and extended information in the existing MTP2 protocol summarized by the present invention, which have nothing to do with the specific implementation mode, can be found in Table 1, Table 1 also provides a feasible coding scheme for the cause of disconnection and the expansion of the coding scheme for the reason of disconnection;

Table 1

Step 2: The above-mentioned local MTP2 entity extends the SIOS message of the MTP2 protocol, and defines the link-break cause bit and the link-break reason extension bit in the Spare field;

The SIOS message is a type of LSSU specified in the MTP2 protocol. The LSSU format diagram is shown in part 3_1 of Figure 3, and the SIOS message definition diagram is shown in part 3_2 of Figure 3; because the SF field of the LSSU exists in the MTP2 protocol, no specific purpose is defined The Spare domain of the SIOS message, the present invention defines the link-break reason bit and the link-break reason extension bit in the Spare field of the SIOS message, wherein the definition method of the link-break reason bit and the link-break cause extension bit has multiple options, and the one adopted in the present embodiment A feasible definition method is shown in part 3_3 in Fig. 3; MTP2 protocol stipulates that the SF field of LSSU can be 8bit or 16bit; the present embodiment has used the SIOS message that the SF field length is 16bit, and the low 4bit of its high order byte It is defined as the link-break cause bit (D4D3D2D1), and the 5th to 7th bits of its high-order byte are defined as the link-break cause extension bit (D7D6D5);

Step 3: When the local MTP2 entity is disconnected, fill the code corresponding to the cause of the disconnection into the disconnection cause bit of the above SIOS message, and fill in the extended code corresponding to the status or sub-reason of the disconnection in the link disconnection reason extension bit, and send it to the peer MTP2 entity along with the above SIOS message;

Step 4: After receiving the above-mentioned SIOS message, the above-mentioned peer MTP2 entity takes out and analyzes the disconnection cause bit and the disconnection cause extension bit, and decodes the above-mentioned disconnection reason and status at the time of disconnection into a primitive or a part of a primitive Report to the peer MTP3 or OAM, and be processed accordingly by the peer MTP3 or OAM.

In the above process, steps 1 and 2 are the preparatory stages of the processing flow of the present invention, and steps 3 and 4 are the realization stages of the processing flow of the present invention.

The working principle of the present invention has been described in detail above, but this is only a vivid example for easy understanding, and should not be regarded as limiting the scope of the present invention. Similarly, any ordinary professional in the technical field can make various possible equivalent changes or replacements according to the technical solution of the present invention and the description of its preferred embodiments, but all these changes or replacements should belong to the scope of the present invention. The scope of the claims.

Claims (4)

1. A method for tracking the disconnection reason of the opposite end narrowband signaling link and the state of the disconnection, which is applicable to the message transmission part 2-layer narrowband signaling link, and is characterized in that it comprises the following steps: Step 1: The Layer 2 entity in the message transmission part of the local end defines the link-break reason code and the link-break cause extension code; Step 2: The layer 2 entity of the message transmission part of the local end defines the disconnection cause bit and the link disconnection cause extension bit in the exit service message of the layer 2 protocol of the message transmission part; Step 3: When the above-mentioned layer 2 entity in the message transmission part of the local end is disconnected, fill in the code corresponding to the cause of the disconnection into the disconnection cause bit of the above-mentioned exit service message, and fill in the extended code corresponding to the state or sub-reason at the time of disconnection Link-break reason extension bit, and send it to the layer 2 entity of the peer message transmission part along with the above exit service message; the code corresponding to the above-mentioned link-break reason is the above-mentioned link-break reason code, and the above-mentioned link-break state or sub-reason corresponds to The extended code of is the above-mentioned extended code of the cause of the broken link; Step 4: After receiving the exit service message, the Layer 2 entity of the above-mentioned peer message transmission part takes out and analyzes the link-break cause bit and the link-break cause extension bit, and decodes the above-mentioned link-break reason and the state or sub-reason at the time of link break It is a primitive or a part of a primitive and reported to the layer 3 of the message transmission part of the opposite end or the operation and maintenance station, and is processed by the layer 3 of the message transmission part of the opposite end or the operation and maintenance station. 2. The method according to claim 1, wherein said step 1 comprises the following steps: Step 101: The above-mentioned layer 2 entity of the message transmission part of the local end defines the code of the reason for disconnection for all the reasons for disconnection occurring in the layer 2 protocol of the message transmission part; Step 102: The layer 2 entity of the message transmission part of the local end judges whether the above-mentioned link disconnection reason has only one state, and if so, defines the link-breakage reason extension code for the sub-reason of the link-breakage reason; All states define the link-break reason extension encoding. 3. The method according to claim 1, wherein said step 2 comprises the following steps: The Layer 2 entity of the message transmission part of the above-mentioned local end extends the out-of-service message of the Layer 2 protocol in the message transmission part, and defines the link disconnection cause bit and the link disconnection cause extension bit in the free field. 4. The method according to claim 3, characterized in that the method of defining the disconnection cause bit and the link disconnection reason extension bit in the idle field of the above-mentioned exit service message is at least: Use an exit service message with a status field length of 16 bits, define the lower 1st to 4th bits of its high-order byte as the cause of link disconnection, and define the lower 5th to 7th bits of its high-order byte as the link-disconnection cause extension bit.

Images