CN1301604C

CN1301604C - Method for detecting H.248 protocol abnormal context

Info

Publication number: CN1301604C
Application number: CNB200310112214XA
Authority: CN
Inventors: 刘其锋; 王传政; 胡宪利
Original assignee: ZTE Corp
Current assignee: ZTE Corp
Priority date: 2003-11-14
Filing date: 2003-11-14
Publication date: 2007-02-21
Anticipated expiration: 2023-11-14
Also published as: CN1545240A

Abstract

The present invention discloses a method for detecting an H. 248 protocol abnormal context the field of communication, which comprises an MGW abnormal context detecting process and an MGC abnormal context detecting process, wherein the MGC abnormal context detecting process comprises the following steps: 1. an MGC transmits a service change command to an assigned MGW; 2. after the MGW receives a request, a context ID is looked up, one error is transmitted back to the MGC if the context does not exist, and one normal replay is transmitted if the context exists; 3. after the MGC receives the replay of the MGW, the parameters of the replay are analyzed, if the context is abnormal, an abnormal treatment needs to be carried out, and the context is forced to be deleted. The present invention can effectively clean up the abnormal context of the MGC and the MGW and can cause the abnormal context in the whole system of the MGW and the MGC to be capable of being automatically deleted, and therefore, the present invention ensures the stabilization of the system.

Description

Detect the H.248 contextual method of protocol anomaly

Technical field

The present invention relates to the communications field, specifically, relate in the communications field that MGC and MGW go up unusual contextual detection method in the NGN system.

Background technology

Along with mobile communcations system in the increasingly extensive application of every field such as economic and social life, mobile communcations system technology itself is also among fast development, from at present just at widely used second generation mobile communcations system, arrive ripe perfect third generation mobile system, the demand of user for communication system satisfied in technical development day by day.3GPP of International Standards Organization (3rd Generation Partnership project) and 3GPP2 (3rd GenerationPartnership project 2) are responsible for the formulation and the modification of third generation mobile system international standard WCDMA standard and CDMA2000 standard respectively.In two types standard, H.248 agreement is extensively adopted by tissues such as 3GPP/3GPP2, as NGN (NextGeneration Network, as SOFTSWITCH/WCDMA/CDMA2000/TD-SCDMA) network carrying and the consensus standard that separates of control, H.248 agreement be mainly used in MGC (Media Gateway Control: Media Gateway Controller) and MGW (Media Gateway: gateway control media gateway) and carrying foundation are controlled.

In the application of agreement H.248, the operation of all affairs all is contextual at certain, context identifies by context ID, we can say that context ID is that to connect affairs, order, terminal be the tie of Termination, and all operations all center on the context ID expansion.Context ID is that MGC keeps a key parameter that is connected with MGW.In a complete calling procedure, tend to relate to contextual establishment, delete procedure.In fact, contextual establishment, delete procedure also are one of most important processes H.248, context ID is distributed by MGW, MGW returns to MGC with its context distributed ID, thereby make MGC obtain the data of this context ID, follow-up MGC and MGW are maintaining each other calling by context ID, in case a side context ID is rewritten or lost, entanglement will take place in calling, thereby cause the context ID of MGC, MGW unusual.Unusual context is in case produce, all it must be found out and delete it to MGC or to MGW no matter be, otherwise this unusual context is present in the system, can produce serious consequence to the stable operation of system, and by patent retrieval and open source literature inquiry, find the prior art that can effectively detect unusual context, also in existing product, find relevant solution.

Summary of the invention

Technical problem to be solved by this invention provides the H.248 contextual method of protocol anomaly of a kind of detection, can't effectively detect the H.248 contextual problem of protocol anomaly in the hope of overcoming prior art, so that system can effectively detect H.248 protocol anomaly context, the stability of enhanced system operation.

For achieving the above object, the present invention proposes the H.248 contextual method of protocol anomaly of a kind of detection, it is characterized in that, may further comprise the steps:

First aspect: MGC detects unusual context procedures:

It is the MGW that Service Change orders appointment that the first step: MGC sends professional the change, wherein content number is the context ID of Context ID for detecting, and method is that Method is that the business change method of expansion is Service Change Method X-Testcx;

Second step: the MGW searches Context ID after receiving the next request of MGC, if context does not exist, then returns mistake to MGC, and returning a normal feedback if context exists is Reply;

The 3rd step: after MGC receives the Reply of MGW,,, illustrate that this context ID is normal, otherwise context is unusual, need carries out abnormality processing, this context of Force Deletion if Reply is normal by analyzing its parameter.

Second aspect: MGW detects unusual context procedures:

The first step: MGW sends Service Change and orders MGC, and wherein Context ID is the context ID of detection, and Method is the Service Change MethodX-Testcx of expansion;

Second step: the MGC searches Context ID after receiving the next request of MGW, if context does not exist, then returns mistake to MGW, if context exists then returns a normal Reply;

The 3rd step: after MGW receives the Reply of MGC,,, illustrate that this context ID is normal, otherwise context is unusual, need carries out abnormality processing, this context of Force Deletion if Reply is normal by analyzing its parameter.

Adopt the unusual contextual method of detection of the present invention, make full use of H.248 agreement Service Change order, and extendible Service Change Method parameter, make full use of unusual contextual characteristics, utilize MGW with carrying out the mutual of ServiceChange order between the MGC, reach the unusual contextual purpose of detection by analyzing its Service Change Method X-Testcx.Can effectively remove the unusual context of MGC, MGW, make the deletion that unusual context in MGW, the MGC whole system can be voluntarily, guarantee the stable of system.

Description of drawings

Fig. 1 is that MGC detects unusual context method flow diagram in the method for the invention.

Fig. 2 is that MGW detects unusual context method flow diagram in the method for the invention.

Embodiment

Below in conjunction with accompanying drawing, concrete enforcement of the present invention is described in further detail.

The front was introduced, and context is the key parameter that MGW, MGC carry out call communication, in case this parameter has taken place unusually, this calling can't discharge, be easy to hang a side data field, the context of hanging makes system exception, and therefore searching unusual context seems important all the more.Unusual contextual judgement needs MGC, MGW both sides all will carry out.Unusual contextual Rule of judgment is relative, and whether a context among the MGC is unusual, has only corresponding MGW to know whether a context among the same MGW is unusual, also has only relevant MGC to know.

Suppose that MGC has set up a contextual connection with MGW, context ID is 1, and MGC is 1 data with having an identical context ID on the MGW.But through the long time, MGC finds that this context ID is that 1 data still exist, and MGC begins to suspect that this context ID may be unusual, carries out following processing (as shown in Figure 1):

The first step: MGC suspects that this context is unusual, such as the overlong time that exists etc., just the MGW to appointment sends a request transaction, context ID is 1, order is ServiceChange, its Service Change Method is X-Testcx, and whether detect this context ID unusual, and the transmission of this message can not produce any harmful effect to calling out.

Second step: after MGW receives Service Change message, analyze the content of Service Change message, find that Service Change Method is X-Testcx, analyze the data field of this context ID then, if this context ID exists, MGW returns normal Reply to MGC, otherwise returns to mistake of MGC, error code is 412, and illustrating has not had this context ID on the MGW.

The 3rd step: after MGC receives the Reply of MGW,,, illustrate that this context is normal if Reply is a normal Reply by analyzing the parameter among the Reply; If wrong error code is 412 among the Reply, illustrate that this context is unusual, need be with this context deletion.

Same: the MGW start detection detects unusual contextual flow process as shown in Figure 2:

The first step: MGW suspects that this context is unusual, such as the overlong time that exists etc., just send a request transaction to its MGC that registers, context ID is 1, order ServiceChange, its Service Change Method is X-Testcx, whether detect this context ID unusual.

Second step: after MGC receives Service Change message, analyze the content of Service Change message, find that Service Change Method is X-Testcx, analyze the data field of this context ID then, if this context ID exists, MGC returns normal Reply to MGW, otherwise returns to mistake of MGW, error code is 412, and illustrating has not had this context ID on the MGC.

The 3rd step: after MGW receives this Reply,,, illustrate that this context is normal if Reply is a normal Reply by analyzing the parameter among the Reply; If wrong error code is 412 among the Reply, illustrate that context is unusual, need be with this context deletion.

Adopt this method can not influence normal call flow, MGC or MGW suspect by the time of computational context ID survival whether it is unusual, start our contextual abnormality detection flow process, and the context deletion with unusual guarantees the healthy and stable of system.

Claims

1, a kind of detection contextual method of protocol anomaly H.248 is characterized in that, may further comprise the steps:

First aspect: Media Gateway Controller is that MGC detects unusual context procedures:

The first step: MGC send professional change be Service Change to order the media gateway of appointment be MGW, wherein content number is the context ID of Context ID for detecting;

After second step: the MGW receives the request of MGC transmission, search Context ID,, then reply to errored response of MGC, reply a normal response if context exists if context does not exist;

The 3rd step: after MGC receives the response of MGW,,, illustrate that this context ID is normal, otherwise context is unusual, need carries out abnormality processing, this context of Force Deletion if response is normal by analyzing its parameter;

Second aspect: MGW detects unusual context procedures:

It is that Service Change orders MGC that the first step: MGW sends professional the change, wherein the context ID of Context ID for detecting;

After second step: the MGC receives the request of MGW transmission, search Context ID,, then reply to errored response of MGW, reply a normal response if context exists if context does not exist;

The 3rd step: after MGW receives the response of MGC,,, illustrate that this context ID is normal, otherwise context is unusual, need carries out abnormality processing, this context of Force Deletion if response is normal by analyzing its parameter.

2, the detection according to claim 1 contextual method of protocol anomaly H.248 is characterized in that, when MGC suspects that context is unusual, just to request transaction of the MGW of appointment transmission.

3, the detection according to claim 2 contextual method of protocol anomaly H.248 is characterized in that, described context is meant the overlong time that context exists unusually.

4, the detection according to claim 1 contextual method of protocol anomaly H.248 is characterized in that, when MGW suspects that context is unusual, just to request transaction of MGC transmission that this MGW registered.

5, the detection according to claim 4 contextual method of protocol anomaly H.248 is characterized in that, described context is meant the overlong time that context exists unusually.