WO2008003211A1

WO2008003211A1 - A method and apparatus for signaling transport configuration matching detection

Info

Publication number: WO2008003211A1
Application number: PCT/CN2007/001305
Authority: WO
Inventors: Jianxing Hou
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2006-06-27
Filing date: 2007-04-20
Publication date: 2008-01-10
Also published as: CN100456709C; CN1996903A

Abstract

A method for signaling transport configuration matching detection, includes the following steps: set the matching detection information in the message which is sent to the opposite end by the sending end, and the matching detection information reflects the configuration of the sending end, in which the message transport between the sending end and the opposite end complies with the signaling transport protocol stack specification; after the opposite end received the matching detection information, it verifies the consistency of the configuration of the sending end with its configuration; determine whether to enable the two ends turn into service state according to the result of the consistency verify. An apparatus for signaling transport configuration matching detection is also provided.

Description

Method and device for signaling transmission configuration matching detection

The present invention relates to the field of communications, and in particular, to a method and apparatus for signaling transmission configuration matching detection. Background technique

In order to meet the requirements of transmitting signaling protocols over IP (Internet Protocol) networks, the Internet Engineering Task Force (IETF) has established a dedicated signaling transmission group to develop signaling signaling (Signalling). Transport, SIGTRAN) The protocol stack supports the transmission of circuit-switched signaling over IP networks. The SIGTRAN protocol stack supports the inter-layer standard primitive interface in the layered model definition of the circuit-switched signaling protocol, thereby ensuring that the existing circuit-switched signaling can be used without modification, and also using the standard IP transmission protocol as the transmission underlayer. Meet the special transmission requirements of circuit-switched signaling by adding its own functions.

SIGTRAN is a protocol stack consisting of a set of protocols, including M2UA (SS7 MTP2 User Adaptation Layer, NO.7 signaling messaging part second level user adaptation layer), M3UA (SS7 MTP3 User Adaptation Layer, N0.7 Signaling message passing part of the third level user adaptation layer), SUA (Signaling Connection Control Part User Adaptation Layer), IUA (ISDN Q.921 - User Adaptation Layer, ISDN Q921 user adaptation layer), V5UA (V5.2-User Adaptation Layer, V5.2 User Adaptation Layer) is used to implement Signaling No. 7, ISDN (Integrated Services Digital Network) signaling, and V5 access network signaling messages. Signaling interworking between the IP network and the original circuit network.

Fig. 1 shows an application model specified by the related art M2UA standard.

Taking M2UA as an example, the application model specified by the M2UA standard is shown in Figure 1:

If there are four MTP links on the SG, such as links 0, 1, 2, and 3. MTP is the abbreviation of the "message delivery part" protocol. It is a set of protocols defined by the ITU. It is divided into three layers. MTP 1 is the physical layer, MTP 2 Is the link layer, responsible for reliable transmission of messages, MTP 3 is the network layer, responsible for signaling network status maintenance and message routing Management, the interface identifiers are 0, 1, 2, 3; respectively, MTP link 0 (MTP link 0) on the SG (Signaling Gateway) is managed by the MGC1 (Media Gateway Controller). And link 1 (MTP link 1), MGC 2 manages MTP link 2 (MTP link 2) and 3 (MTP link 3) on the SG. The MTP link 0 and the MTP link 1 on the SG belong to the AS (Application Server) 0. This AS has ASP 1 and ASP 2 to provide services.

However, one problem is that if both ASP 0 and ASP 1 have entered the service state, both MTP link 0 and MTP link 1 have established a link and data communication, if the user accidentally ASP when configuring ASP 2 2 is configured to be also AS (W), because the standard does not define a configuration check mechanism, ASP 2 will also enter the service state. If the services from the MTP 0 and MTP 1 links are distributed to ASP 2, ASP 2 It will find that it cannot process the service messages sent by the two links, and may send a message to the SG to remove the two MTP links, or at least send an ERROR message to the SG (because the interface identifier does not exist); SG After receiving this message, it is considered that the MGC can not handle the services on the two links, and the MTP link 0 and the MTP link 1 are also removed, causing the two link services to be interrupted. Because the MTP link may serve A large number of users, if a large number of MTP links are interrupted, will bring huge losses to operators and users.

Figure 2 shows the basic business processes in the M2UA, IUA, SUA, M3UA, and V5UA protocols. As shown in Figure 2, in the M2UA, IUA, SUA, M3UA, and V5UA protocols, the basic business process is completed in four steps:

Step 201: After the SCTP connection is established between the two devices, the ASP (Application Server Process) side initiates an ASP UP message to the peer SG side.

Step 202: After receiving the ASP UP message, the SG side responds to the ASP UP ACK message to the ASP side. Step 203: After receiving the ASP UP ACK message, the ASP side may send an ASP ACTIVE message to the SG side.

Step 204: After receiving the ASP ACTIVE message, the SG side responds to the ASP ACTIVE ACK message to the ASP side.

The ASP ACTIVE message sent by the user may have an interface identifier parameter (the interface identifier is optional, generally not included). After receiving the ASP ACTIVE message, the SG side compares the SG on the interface identifier. Check whether the link corresponding to the interface identifier is configured. If no interface is configured on the SG, you can not respond to the ASP ACTIVE ACK message or send an ERROR message.

In the process of implementing the present invention, the inventor has noticed that the above solution has a problem in that, in the above process, since the MTP link is configured on the SG and the MGC, respectively, there may be a configuration that is out of synchronization. When an ASP ACTIVE message is sent by the ASP side, an MTP2 link is not configured on the MGC. The transmitted ASP ACTIVE message does not contain the Interface Id (interface identifier). Therefore, the ASP ACTIVE message sent by the MGC does not have the configured interface identifier. In this case, this mechanism will not work.

On the other hand, the above solution still has a problem. An MGC often controls an MTP link on multiple SGs. The interface identifiers on the SG are generally started from 0, so that the ASP ACTIVE message sent by the ASP side that does not match is The interface identifier may be the same as the interface identifier of the link configured on the SG. Because the two ends of the device are not synchronized, the exact match cannot be strictly required. As long as one interface identifier is the same, the SG side should respond to ASP ACTIVE ACK. The message, if this is configured incorrectly, can't be checked.

Therefore, in the prior art of the M2UA, IUA, SUA, M3UA, and V5UA protocols, when the configuration of the two ends does not match, a large number of link services are interrupted due to a small configuration error of the user, causing significant loss to the user. . Summary of the invention

The embodiment of the present invention provides a method and a device for detecting and matching SIGTRAN configurations, which are used to solve the problem that a large number of link services are interrupted due to a small configuration error of the user, and the user is lost.

The embodiment of the present invention provides a signaling transmission configuration matching detection method, which includes the following steps: setting matching detection information in a message sent by a transmitting end to a peer end, and matching detection information reflects a configuration of a transmitting end, where the transmitting end and the opposite end The message transmission is in accordance with the signaling transmission protocol stack specification; after receiving the message containing the matching detection information, the peer end performs the consistency check on the configuration of the sending end according to the configuration of the local end; Determine whether to make both ends enter the service state according to the consistency check result.

The embodiment of the present invention further provides a signaling transmission configuration matching detection apparatus, including: a matching detection information setting module, configured to set matching detection information in a message sent by the transmitting end to the opposite end, and the matching detection information reflects the configuration of the transmitting end, Wherein, the message transmission between the sender and the peer follows the signaling transport protocol stack specification;

The consistency check module is configured to perform consistency check on the configuration of the sender after receiving the message containing the matching detection information on the peer end.

The service state determining module is configured to determine, according to the consistency check result, whether the two ends enter the service state. The embodiment of the invention further provides a media gateway controller, including:

a matching detection information setting module, configured to set a matching detection information in a message sent by the sending end to the opposite end, where the matching detection information reflects a configuration of the sending end, where the message between the sending end and the opposite end The transmission follows the signaling transport protocol stack specification;

And the message of the matching detection information is used to perform consistency check on the configuration of the sending end according to the configuration of the local end, and determine whether to enable the two ends to enter according to the consistency check result. State of business.

The embodiment of the invention further provides a signaling gateway, including:

The consistency check module is configured to perform consistency check on the configuration of the sending end according to the configuration of the local end, and the matching detection information is sent by the sending end to reflect the configuration of the sending end. Message, wherein the message transmission of the sender follows a signaling transport protocol stack specification;

And a service state determining module, configured to determine, according to the consistency check result, whether to enter the two ends into the service state.

In the embodiment of the present invention, the configuration matching detection information of the sending end is set in the message sent by the sending end to the opposite end, and the peer end receives the message including the matching detection information, and performs consistency check on the configuration of the sending end according to the configuration of the local end. Therefore, it is determined whether the two ends are brought into the service state, so that the embodiment of the present invention can solve the problem of a large number of link service interruptions caused by small configuration errors of the user, and avoids loss to the user. DRAWINGS

1 is a schematic diagram of an application model specified by the M2UA standard in the background art;

2 is a schematic diagram of implementation of a basic service flow in the M2UA, IUA, SUA, M3UA, and V5UA protocols in the background art;

FIG. 3 is a schematic diagram of a flow of implementation of the SIGTRAN configuration matching detection method according to an embodiment of the present invention; FIG. 4 is a schematic structural diagram of a SIGTRAN configuration matching detection apparatus according to an embodiment of the present invention; and FIG. 5 is a media gateway control used for SIGTRAN configuration matching detection. FIG. 6 is a schematic structural diagram of a signaling gateway used for SIGTRAN configuration matching detection;

7 is a schematic flowchart of an implementation process of a SIGTRAN configuration matching detection method in an M2UA according to an embodiment of the present invention;

FIG. 8 is a schematic diagram of a process for establishing an M3UA basic service flow according to the prior art; FIG. 9 is a schematic diagram of an implementation process for detecting an M3UA layer configuration match when establishing an M3UA basic service according to an embodiment of the present invention. detailed description

Specific embodiments of the present invention will be described below with reference to the accompanying drawings.

In the embodiment of the present invention, the service testing process of the M2UA, the IUA, the SUA, the M3UA, and the V5UA is introduced, so as to solve the deficiencies in the prior art, that is, the configuration of the two ends may be mismatched, so that the user can intervene in time. Measures to correct the configuration to avoid a large number of link service interruptions caused by small configuration errors of the user, causing significant losses to the user.

FIG. 3 is a schematic diagram of an implementation process of a SIGTRAN configuration matching detection method; as shown in the figure, an implementation of the SIGTRAN configuration matching detection method includes the following steps:

Step 301: Set the matching detection information in the message sent by the sending end to the peer end, where the information reflects the configuration of the sending end, where the message transmission between the sending end and the opposite end follows the SIGTRAN protocol stack; Step 302, the peer end receives the After the matching detection information is matched, the matching detection process is started, and the configuration reflected in the information is checked for consistency according to the configuration of the local end; Step 303: Determine, according to the consistency check result, whether the two ends enter the service state.

In the foregoing method, in step 301, the configuration reflected in the implementation may include: an MGC device identifier, a device unique identification number, a device preferred IP address, or a signaling point where the device is located, or other content that can identify the device plus a combination of an AS identifier or a link set identifier;

The SIGTRAN protocol stack includes M2UA, IUA, V5UA, SUA, M3UA, etc.; detection information can be included in ASP UP, ASP UP ACK:, ASP ACTIVE, ASP ACTIVE

ACK, NOTIFY, ERROR, HEARTBEAT, HEARTBEAT ACK, etc.

In step 303, if the configuration of the two ends is found to be inconsistent, the continuing message interaction process is terminated, otherwise the normal message interaction process is continued;

If the configuration matches, the two sides are allowed to enter the service state. Otherwise, an error message is reported to prevent the entry into the service processing state.

4 is a schematic structural diagram of a SIGTRAN configuration matching detecting apparatus; as shown in the figure, the SIGTRAN configuration matching detecting apparatus 400 includes:

The matching detection information setting module 401 is configured to set the matching detection information in the message sent by the sending end to the opposite end, where the information reflects the configuration of the sending end, wherein the message transmission between the sending end and the opposite end follows the SIGTRAN protocol;

The consistency insurance module 402 is configured to start a matching detection process after the peer receives the matching detection information, and perform consistency check on the configuration reflected in the information according to the configuration of the local end;

The service state determining module 403 is configured to determine whether to bring the two ends into the service state according to the consistency check result, where, optionally, the service state determining module 403 includes:

Allow access to the module (not shown) for allowing the two ends to enter the service state if the consistency check result is a configuration match;

An error handling module (not shown) is used to report an error message to prevent both ends from entering the service processing state.

FIG. 5 is a schematic structural diagram of a media gateway controller for SIGTRAN configuration matching detection; as shown in the figure, the media gateway controller includes:

The matching detection information setting module is configured to set a matching check in the message sent by the sending end to the opposite end. Detecting information, the matching detection information reflects the configuration of the sending end, wherein the message transmission between the transmitting end and the opposite end follows the signaling transmission protocol stack specification;

FIG. 6 is a schematic structural diagram of a signaling gateway used for SIGTRAN configuration matching detection. As shown in the figure, the signaling gateway includes:

a consistency check module, configured to perform consistency check on the configuration of the sending end according to the configuration of the local end, and the matching detection information is sent by the sending end to reflect the sending end a configured message, where the message transmission of the sender follows a signaling transport protocol stack specification;

The signaling gateway may further include: a sending module, configured to send a message carrying the local configuration information to the sending end.

The service state determining module may include:

Allowing the entry module to allow the two ends to enter the service state if the consistency check result is a configuration match;

The error processing module is configured to prevent the two ends from entering the service processing state if the consistency check result is a configuration mismatch.

In the embodiment of the present invention, in the M2UA message interaction process, the detection information is added to some messages in the message interaction process, and the detection information may be added in the form of a new parameter, or may be added to the original parameter, After receiving the message, the device removes the information from the message and checks whether the match is matched. If the configuration is matched, the M2UA is allowed to enter the service state. Otherwise, the error message is sent to prevent the service from being processed. .

It can be seen from the foregoing embodiment that the configuration detection mechanism is introduced, and the problem that the configurations of the two ends are matched cannot be detected. Wake up the configuration of the two sides of the user does not match, to avoid waiting for the failure of the large number of calls to locate the failure, resulting in a large number of communication interruptions, causing huge losses to operators and users.

A specific embodiment of the present invention will be described below with reference to Fig. 7, taking M2UA as an example.

7 is a schematic flowchart of an implementation process of a SIGTRAN configuration matching detection method in an M2UA, as shown in the figure, when there are two or more ASPs serving the AS on the ASP side (for a link set using a link set) The model is that an M2UA link set has two or more M2UA links to provide services for it. If ASP 1 is the first ASP that sends ASP UP messages for the AS service, ASP2 is for the AS service. The ASP that sends the ASP UP message (for the link set-link model, the M2UA link 1 sends the ASP UP message first, and the M2UA link 2 sends the ASP UP message). In this embodiment, the following processing steps are performed:

Step 701: On the ASP, ASP 1 sends an ASP UP message to the SG side, where the INFO String parameter (which may also be a new parameter) in the ASP UP message is added with the local configuration information (such as the MGC device identifier and the AS identifier. The link set-link model may use the M2UA link set number, etc.); Step 702: After receiving the ASP UP message on the SG, the corresponding ASP configured on the SG is found (for the link set-link) The model may be to find the corresponding M2UA link), and then find the AS served by the ASP (for the link set-link model, the corresponding M2UA link set may be found), and the current SG corresponds to the AS. The configuration detection information of the peer is not saved (because the ASP that receives the ASP UP message is the first in the ASP service ASP on the SG side). If the discovery message contains configuration detection information, the SG side configures the ASP UP ACK message. The detection information is saved, and then the ASP side responds to the ASP UP ACK message. As an option, the INFO String parameter in the ASP UP ACK message (or a new parameter) can be used to add the local configuration information on the SG (such as an IP address configured on the SG plus the AS identifier. The link model can use an IP address configured on the SG plus the M2UA link set number, or any other information that can uniquely identify the AS. After adding the local configuration information, the sender can use the information to enable the sender. Understand the status of the peer, such as positioning, check the configuration match, and understand the reasons for the failure.

Step 703: On the MGC, ASP 1 receives the responded ASP UP ACK message, and finds the AS served by the ASP according to the corresponding ASP (for the link set-link model, the corresponding one is found. M2UA link set); The configuration detection information of the peer end has not been saved in the corresponding AS on the current MGC (because the ASP that sent the ASP UP message for the first AS service on the ASP side), if the ASP UP ACK is received If the message includes the configuration detection information, the configuration detection information in the ASP UP ACK message is saved; and the ASP ACTIVE message is continuously sent to the SG side;

Step 704: After receiving the ASP ACTIVE message on the SG side, the ASP ACTIVE ACK message is sent to the ASP side, and the ASP side enters the service processing state after receiving the ASP ACTIVE message.

Step 705: On the MGC, ASP2 sends an ASP UP message to the SG side, where the INFO String parameter in the ASP UP message (which may also add a parameter) includes adding local configuration information.

Step 706: After receiving the ASP UP message on the SG, find the ASP configured on the SG (for the link set-link model, the corresponding M2UA link may be found), and then find the AS served by the ASP (for The link set-link model may be used to find the corresponding M2UA link set, and the configuration detection information of the peer end is saved in the corresponding AS on the current SG, and the received message also includes configuration detection information. The configuration detection information in the received ASP UP message is compared with the configuration detection information stored in the corresponding AS in the corresponding AS on the SG. If the information contained in the two is identical, the configurations on both ends are matched, and the response is ASP UP ACK. The message is sent to the ASP side; if the content of the two is different, it needs to be handled according to different situations:

1. If the gateway supports multiple homing, that is, one SG may have multiple ASPs on the MGC to provide services for the MG. The configuration detection content sent by the AS on different MGCs may be different. For example, the SG can parse the content of the configuration detection. The MGC device ID and the AS ID are distinguished from each other. If the device ID is the same and the ASP ID is different, the configuration error is considered. Some measures can be taken to terminate further message interaction on both sides. If the device ID cannot be resolved, directly respond to ASP UP. ACK message; and

2. If the gateway support does not support multi-homing, then an SG has only one ASP on the MGC to provide services for it, and it is considered that a configuration error has occurred. Some measures can be taken to terminate further message interaction on both sides.

There are [more] ways to terminate further message interactions on both sides, but it is not limited to using some measures like the following: When the ASP UP ACK message is not responded, an error message may be output to allow the SG side user to intervene; when responding to an abnormal message such as ERROR, NOTIFY > ASP DOWN ACK, the message may include error cause information;

When responding to the ASP UP ACK message, but the message contains configuration error information, or the configuration information of the local end is also included in the issued ASP UP ACK message, etc., which can inform the peer that the configuration parameter or content is abnormal;

When the established SCTP couple chain is removed, an error message can be output.

Step 707: After receiving the ASP UP ACK message, the ASP2 on the MGC may perform the following processing according to the content included in the message:

1. If the message contains configuration error information, the error message is output to remind the user to intervene;

2. There is no error message in the message, but there is configuration information of the peer. If the configuration detection information of the peer is saved in the corresponding AS on the current MGC, the configuration detection information in the ASP UP ACK message and the pair saved in the corresponding AS on the MGC are obtained. The configuration detection information of the end is compared, if it is consistent, the processing is continued, and if it is inconsistent, an error message is output to prompt the user to intervene;

3. If the message does not contain configuration detection information and no error message, continue to send the ASP ACTIVE message according to the original processing.

The specific embodiment of the present invention will be described below by taking M3 UA as an example.

In order to be compatible with the M3UA protocol, the service flow defined by the M3UA protocol is used in this embodiment. The difference is that, in the embodiment, the message sending end is added to some messages in the message interaction before or after the M3UA layer enters the service state. The information is sent to the peer end. The configuration information can be in the form of new parameters or the original parameters of the message. After receiving the information about the configuration information, the peer end obtains the configuration information for detecting the matching, and performs the consistency check with the configuration information of the peer. If the configuration information matches, the two ends connected to the M3UA layer are allowed to enter the service. State, otherwise, return an error message to the message sender to prevent access to the business processing state.

Figure 8 is a schematic diagram of the implementation process of the basic service flow of the M3UA. As shown in the figure, taking the SG-ASP mode as an example, the basic business process of the M3UA layer is established as follows: Step 801: According to the service process defined by the M3UA protocol, after the SG completes the configuration of the ASP serving the AS, the SG initiates an SCTP connection with the MGC where the configured ASP is located; for example, it is assumed that ASP0 on the MGC1 is configured as AS0. Service, the SG initiates establishment of an SCTP protocol layer connection with the MGC1;

Step 802: After the connection of the SCTP protocol layer is completed, the MGC1 sends an eighth message to 80. Step 803: After receiving the ASP UP message, the SG returns an ASP UP ACK message to the MGC1. Step 804: The MGC1 receives the ASP. After the UP ACK message, enter the inactive state, and send an ASP ACTIVE message to the SG;

Step 805: After receiving the ASP ACTIVE message, the SG enters an active state, and returns an ASP ACTIVE ACK message to the MGC1.

Step 806: After the entire M3UA message interaction is completed, the SG and the MGC1 enter the service state, and the upper layer service message can be delivered. It is assumed that the SG in this step receives the signaling message of the destination narrowband network and the destination signaling point code is 0x111111 ( MGC1 ), and can be processed according to the destination signaling point code of the message, for example, AS0 on the SG.

Step 807: AS0 can select ASP0 on MGC1 to serve it, so that the signaling message encoding the destination signaling point received by the traditional narrowband network to 0x111111 (MGC1) is sent to MGC1.

For the IPSP-IPSP mode, the process of establishing the basic service flow of the M3UA layer is the same as that of the basic service flow of the M3UA layer in the SG-ASP mode. The SG is replaced by an IPSEP (for example, IPSEP1) and the MGC1 is replaced. Another IPSEP (such as IPSEP2), IPSEP1 and IPSEP2 replace SG and MGC1 respectively for corresponding message interaction. In this way, after the M3UA message interaction is completed, IPSEP1 and IPSEP2 can enter the service state and transmit the upper layer service message.

In the process of upper-layer service message delivery, the M3UA layer can detect the M3UA layer connection by periodically sending a heartbeat message.

In the above process, the ASP UP message and the ASP ACTIVE message sent by the MGC1 or IPSEP1, and the ASP UP ACK message and the ASP ACTIVE ACK message returned by the SG or IPSEP2 do not include the information of the signaling point code, for example, the sender's letter. Point coding (source signaling point coding), The signaling point coding (destination signaling point coding) of the receiving end, and the network identification of the transmitting end and the receiving end, etc., therefore, it is impossible to detect whether the configuration information matches. Therefore, the above process can only ensure that the M3UA layer is established between the transmitting end and the peer M3UA layer of the receiving end, but the receiving end is not the destination signaling point for receiving data. That is to say, since the signaling point code and the network identifier of the receiving end are not detected during the connection establishment process of the M3UA layer, in the case of a configuration mismatch, the receiving end may not be the destination signaling point for data reception.

For example, it is assumed that the AS0 is configured to be served by ASP2 on MGC2 due to a configuration error, as shown by the dotted line in FIG. 1, and the SG and MGC2 perform SCTP connection and M3UA connection establishment, namely: SG initiation and MGC2 The establishment of the SCTP protocol layer connection, after the SCTP protocol layer connection is completed, the MPC2 sends an ASP UP message to the SG; after receiving the ASP UP message, the SG returns an ASP UP ACK message to the MGC2; the MGC2 receives the ASP UP ACK message. Afterwards, it enters the inactive state and sends an ASP ACTIVE message to the SG. After receiving the ASP ACTIVE message, the SG enters an active state and returns an ASP ACTIVE ACK message to MGC2. After that, SG and MGC2 enter the service state, if the destination signaling point received by the SG from the traditional narrowband network is coded as 0x111111.

The signaling message of ( MGC1 ) is allocated to AS0 for processing, and AS0 selects ASP2 on the misconfigured MGC2 to serve it, then the SG will encode the destination signaling point to 0x111111.

The signaling message of (MGC1) is sent to MGC2 with the signaling point coded as 0x222222. However, MGC2 will discard the signaling message with the destination signaling point of 0x111111, which will cause the communication to fail.

Therefore, because the existing messages in the process of establishing an M3UA connection between the SG and the MGC do not include configuration information, and the SG and the MGC do not perform configuration matching detection, it may cause a potentially undetectable communication failure.

In order to check whether the configuration information matches, and thus the actual receiving end of the above data may not be the problem that the data needs to be sent to the receiving end, the M3UA protocol may define a message, for example, an ASP UP message, an ASP ACTIVE message, an ASP UP ACK message, The configuration information for checking is added to at least one of the ASP ACTIVE ACK message, the heartbeat message, or the heartbeat response message, for example, the signaling point code of the transmitting end, the signaling point code of the receiving end, and the signaling point of the transmitting end and the receiving end. Network identification, etc.

According to the definition of the M3UA protocol, the INFO String parameter in the ASP UP message is an optional parameter. Therefore, configuration information for checking may also be added therein, for example, signaling point coding at the transmitting end, signaling point coding at the receiving end, and Network identifiers of the sender and receiver. Of course, new parameters can also be defined in the M3UA protocol for recording the above configuration information, so that the configuration information can be checked according to the newly defined parameters, and the definition of the M3UA protocol should be modified accordingly.

FIG. 9 is a schematic diagram of an implementation process for detecting an M3UA layer configuration match when establishing an M3UA basic service. The configuration information for checking is added to the INFO String parameter in the ASP UP message as an example. The M3UA is described with reference to the flowchart of FIG. 8. Layer configuration matching detection implementation, as shown in the figure, the detection includes the following steps:

Step 901: After the SG completes the configuration of the ASP served by the AS, the SG initiates an SCTP connection with the MGC where the configured ASP is located. For example, if the ASP0 on the MGC1 is configured as the AS0 service, the SG initiates an association with the MGC1. The establishment of the SCTP protocol layer connection.

Step 902: After the connection of the SCTP protocol layer is completed, the ASP UP message with the configuration information of the MGC1 is sent by the MGC1 to the SG; that is, after the SCTP protocol layer connection is established between the SG and the MGC 1, the ASP UP message is sent by the MGC1. The INFO String parameter of the ASP UP message includes configuration information for checking whether the configuration of the two ends matches the destination. The configuration information may be the signaling point code of the transmitting end MGC1, the destination signaling point code, and the transmitting end of the MGC1. The network identifier of the signaling point, or other check code agreed upon by the two ends of the network configuration.

Step 903: After receiving the ASP UP message sent by the MGC1, the SG extracts the configuration information from the ASP UP message, and performs consistency check with the configuration information of the SG.

For example, the SG checks the signaling point code of the transmitting end MGC1 included in the ASP UP message, the destination destination signaling point code, the network identifier of the signaling point, and the destination signaling point code of the corresponding ASP configured on the SG, and the local end. Whether the signaling point code is consistent with the network identifier of the destination signaling point, or whether the check code of the sender MGCl included in the ASP UP message is consistent with the ASP check code configured on the SG. If the detection is consistent, go to step 906, otherwise go to step 904.

Step 906: The foregoing configuration information is consistent, and returns a normal ASP UP ACK message to the MGCl. The flow thus proceeds to step 907.

Step 907: After receiving the ASP UP ACK message, the MGC1 detects that the message is a normal ASP UP ACK message that does not include a check result, so that the message can be transferred to the active state, and the ASP ACTIVE message is sent to the SG.

Step 908: After receiving the ASP ACTIVE message, the SG transits to the active state and returns to the ASP.

The ACTIVE ACK message is sent to MGC1.

Steps 909, SG, and MGC1 can perform delivery of upper layer service messages. The SG may send a signaling message encoding the destination signaling point received from the traditional narrowband network to 0x111111 ( MGC1 ) to the MGCL.

If the application server process ASP2 on the MGC2 is configured as the AS0 service due to the configuration error, the SG initiates the establishment of the SCTP protocol layer connection with the MGC2, and the MPC2 sends the ASP UP message with the configuration information of the MGC2 to the SG. Therefore, in the detection of step 903, the SG will find a configuration error condition (the signaling point code 0x222222 of the transmitting end MGC2 is inconsistent with the destination signaling point code 0x111111 of the signaling message to be sent), that is, the signaling point code is configured as When the application server process ASP2 on the MGC 2 of 0x222222 serves the AS0 (the application server responsible for processing the destination signaling point code bit 0x111111), it can be determined that the configuration error of the M3UA layer has occurred, and the flow proceeds to step 904.

Step 904: The SG reports information such as a configuration error, a cause of the error (for example, a parameter indicating a mismatch) to the user, and includes information such as a configuration error and a cause of the error in the ASP UP ACK message and returns it to the MGC2.

In addition, in this step, the SG may also send an exception message including a check result, such as an ERROR message, a NOTIFY message, or an ASP DOWN ACK message to the MGC2. Alternatively, the SG may also actively release the SCTP connection that has been established between the MGC and the M3UA, and report the error to the user.

Step 905: After receiving the ASP UP ACK message or the abnormal message returned by the SG, the MGC2 detects that the configuration error and the cause of the error are included, and may report the configuration error and the cause of the error to the user, and may further disconnect. SCTP protocol layer connection. The implementation of the M3UA layer configuration matching detection shows that after the MGC completes the SCTP connection with the SG, the configuration information is included in the ASP UP message and sent to the SG, so that the SG can Compare the self information to check whether it matches. When the mismatch is found, you can report the configuration error to the user in time to avoid the situation where it is difficult to find the configuration error.

The foregoing describes by way of example only the implementation information that the MGC includes configuration information in the ASP UP message and sends it to the SG for consistency check. However, it should be understood by those skilled in the art that the configuration information of the MGC may be included by the MGC in the ASPUP message established during the M3UA establishment process, the ASP ACTIVE message, or any one of the heartbeat messages after the M3UA connection is established. Within the optional parameters, send to the SG for consistency check.

Alternatively, the ASP may send an ASP UP message, an ASP ACTIVE message, or a heartbeat message that does not contain its own configuration information to the SG. The SG returns its configuration information to the MGC in the SG's response message such as ASP UP ACK message, ASP ACTIVE ACK message, and heartbeat message response message, and the MGC performs consistency check according to its configuration information.

For example, the destination signaling point code of the signaling message to be sent by the SG, the local signaling point code, the network identifier of the destination signaling point, or the check code agreed by the signaling devices at both ends are included in the response message and returned. The MGC, the destination signaling point code of the sender SG included in the MGC check response message, the network identifier of the destination signaling point is consistent with its own signaling point code and the signaling point network identifier, or the check message includes Whether the check code is the same as the check code configured on the MGC.

When the MGC finds that the configuration does not match, you can take the disconnection of the SCTP connection, or send an exception message containing the check result, such as an ERROR message, a NOTIFY message, or an ASP DOWN ACK message to the SG, and report the verification result by the SG.

The SG-ASP mode is used as an example to describe the configuration matching detection process. For the IPSP-IPSP mode, the configuration matching detection process is the same as the configuration matching detection process in the SG-ASP mode, except that the SG is replaced by an IPSEP ( For example, IPSEP1) and the above MGC are replaced by another IPSEP (for example, IPSEP2), and SGEP1 and IPSEP2 replace SG and MGC respectively for corresponding message interaction.

It can be seen from the foregoing embodiment that the M3UA layer configuration detection can solve the M3UA layer cannot be solved. It is detected whether the configuration of the two sides of the message interaction matches. Further, in the case where the configurations of the two sides of the message interaction are inconsistent, the user is promptly reminded to avoid the failure cause location after the discovery of a large number of call failures, which wastes a lot of time and brings economic loss to the user.

The foregoing is only a few embodiments of the present invention. It is obvious that the actual configuration detection information may be the device identification number, the device preferred IP address, or the device unique identification number, or the device preferred identification address. The signaling point of the device or other device that can identify the device plus the combination of the AS identifier or the link set identifier, and the detection information can be in the ASP UP, ASP UP ACK, ASP ACTIVE, ASP ACTIVE ACK, HeartBeat, HeartBeat ACK messages. Carrying in any one message; after receiving the message, the peer can also check the consistency of the content in the message;

Obviously, for those skilled in the art, the above process is applicable not only to M2UA, but also to other protocols of SIGTRAN such as IUA, V5UA, M3UA, SUA, and the like.

From the above description, it can be seen that the following technical effects are implemented in the embodiment of the present invention: In the SIGTRAN protocol stack, the configuration detection mechanism is configured, that is, the configuration matching detection that reflects the sending end is set in the message sent by the sending end to the opposite end. After the peer receives the message containing the matching detection information, it performs the consistency check on the configuration of the sender with the configuration of the local end, and then determines whether the two ends enter the service state. The problem is that when the configuration of the two ends is inconsistent, the user is reminded that the configuration on both sides does not match, so as to avoid the failure of the positioning after the discovery of a large number of call failures, so as to cause huge losses to the user.

The above description is only the preferred embodiment of the present invention, and is not intended to limit the present invention, and various modifications and changes can be made to the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and scope of the present invention are intended to be included within the scope of the present invention.

Claims

Rights request

A signaling transmission configuration matching detection method, comprising the steps of: setting matching detection information in a message sent by a transmitting end to a peer end, where the matching detection information reflects a configuration of the transmitting end, where The message transmission between the sender and the peer follows the signaling transport protocol stack specification;

After receiving the message that includes the matching detection information, the peer end performs a consistent school face configuration on the sending end according to the configuration of the local end;

Determining whether to enable the two ends to enter a service state according to the consistency check result.

The signaling transmission configuration matching detection method according to claim 1, wherein the determining, according to the consistency check result, whether the two ends enter the service state step comprises the following steps:

If the consistency check result is a configuration match, the two ends are allowed to enter the service state; otherwise

4. The error message prevents the two ends from entering the service processing state.

3. The signaling transmission configuration matching detection method according to claim 2, further comprising the steps of:

After reporting the error information, the peer sends a message carrying the local configuration information to the sending end.

The signaling transmission configuration matching detection method according to any one of claims 1 to 3, wherein the signaling transmission protocol stack comprises at least one of the following: M2UA, IUA, SUA, M3UA, and V5UA protocols.

The signaling transmission configuration matching detection method according to any one of claims 1 to 3, wherein the message comprises at least one of the following: ASP UP, ASP UP ACK, ASP ACTIVE, ASP ACTIVE ACK:, NOTIFY ^ ERROR, HEARTBEAT^, and HEARTBEAT ACK messages.

The signaling transmission configuration matching detection method according to any one of claims 1 to 3, wherein the reflected configuration comprises at least one of the following or a combination thereof: MGC device identification, device only An identification number, a preferred IP address of the device, a signaling point where the device is located, and other content that can identify the device plus an AS identifier or a link set identifier, a local signaling point, a destination signaling point, and a network identifier.

A signaling transmission configuration matching detection device, comprising:

a consistency check module, configured to perform consistency check on the configuration of the sending end by using the configuration of the local end after receiving the message that includes the matching detection information;

And a service state determining module, configured to determine, according to the consistency check result, whether the two ends enter the service state.

The signaling transmission configuration matching detecting apparatus according to claim 7, wherein the service state determining module comprises:

The error processing module is configured to report an error message if the consistency check result is a configuration mismatch, and prevent the two ends from entering the service processing state.

9. The signaling transmission configuration matching detecting apparatus according to claim 8, further comprising:

The sending module is configured to send a message carrying the local configuration information to the sending end after the error processing module reports the error information.

The signaling transmission configuration matching detecting apparatus according to any one of claims 7 to 9, wherein the signaling transmission protocol stack comprises at least one of the following: M2UA, IUA, SUA, M3UA> and V5UA protocols.

The signaling transmission configuration matching detecting apparatus according to any one of claims 7 to 9, wherein the message comprises at least one of the following: ASP UP, ASP UP ACK, ASP ACTIVE ACK, ASP ACTIVE NOTIFY, ERROR , HEARTBEAT, and HEARTBEAT ACK messages.

The signaling transmission configuration matching detecting apparatus according to any one of claims 7 to 9, wherein the reflected configuration comprises at least one of the following: an MGC device identifier, a device unique identification number, a device preferred IP address, and a device. The combination of the signaling point, and other content that can identify the device plus the AS identity or link set identifier.

13. A media gateway controller, comprising:

14. A signaling gateway, comprising:

The signaling gateway according to claim 14, further comprising: a sending module, configured to send a message carrying the local configuration information to the sending end.

The signaling gateway according to claim 14, wherein the service state determining module comprises: