CN1545240A - Method for detecting H.248 protocol abnormal context - Google Patents
Method for detecting H.248 protocol abnormal context Download PDFInfo
- Publication number
- CN1545240A CN1545240A CNA200310112214XA CN200310112214A CN1545240A CN 1545240 A CN1545240 A CN 1545240A CN A200310112214X A CNA200310112214X A CN A200310112214XA CN 200310112214 A CN200310112214 A CN 200310112214A CN 1545240 A CN1545240 A CN 1545240A
- Authority
- CN
- China
- Prior art keywords
- context
- mgc
- mgw
- unusual
- normal
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Landscapes
- Debugging And Monitoring (AREA)
Abstract
The invention discloses a method of detecting abnormal contexts of H.248 protocol in communication field, including the course of MGW detecting abnormal contexts and the course of MGC detecting abnormal contexts; where the latter includes: 1, MGC sends Service Change command to specific MGW; 2) MGW receives the request to search Context ID: if context does not exist, return an error to MGC; otherwise return a normal Relay; 3) MGC receives the Relay to analyze parameters of the Relay: if context abnormal, it need make abnormal processing to delete the context, forcibly. It can eliminate abnormal contexts of MGC and MGW, which makes these abnormal contexts able to be deleted by themselves to assure system stability.
Description
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 GenerationPartnership project) and 3GPP2 (3rd Generation Partnership project2) 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 (Next Generation 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 the tie that connects affairs, order, Termination, and all operations all center on context ID and launch.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:
The first step: MGC sends Service Change and orders the MGW of appointment, and wherein ContextID is the context ID of detection, and Method is the Service Change Method X-Testcx of expansion;
Second step: the MGW searches Context ID after receiving the next request of MGC, if context does not exist, then returns mistake to MGC, if context exists then returns a normal 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 Method X-Testcx of expansion;
Second step: the MGC searches Context ID after receiving the next request of MGC, 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 ServiceChange order, and extendible Service Change Method parameter, make full use of unusual contextual characteristics, utilize MGW with carrying out the mutual of Service Change 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 Service Change, 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 (3)
1, a kind of detection contextual method of protocol anomaly H.248 is characterized in that, may further comprise the steps:
First aspect: MGC detects unusual context procedures:
The first step: MGC sends Service Change and orders the MGW of appointment, and wherein Context ID is the context ID of detection, and Method is the Service ChangeMethod X-Testcx of expansion;
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:
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 ChangeMethod X-Testcx of expansion;
After second step: the MGC receives the request of MGC 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 the context abnormal conditions such as overlong time that exist, just to request transaction of the MGW of appointment transmission.
3, the detection according to claim 1 contextual method of protocol anomaly H.248 is characterized in that, when MGW suspects the context abnormal conditions such as overlong time that exist, just to request transaction of its MGC that registers transmission.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CNB200310112214XA CN1301604C (en) | 2003-11-14 | 2003-11-14 | Method for detecting H.248 protocol abnormal context |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CNB200310112214XA CN1301604C (en) | 2003-11-14 | 2003-11-14 | Method for detecting H.248 protocol abnormal context |
Publications (2)
Publication Number | Publication Date |
---|---|
CN1545240A true CN1545240A (en) | 2004-11-10 |
CN1301604C CN1301604C (en) | 2007-02-21 |
Family
ID=34336440
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CNB200310112214XA Expired - Fee Related CN1301604C (en) | 2003-11-14 | 2003-11-14 | Method for detecting H.248 protocol abnormal context |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN1301604C (en) |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101022454B (en) * | 2006-02-16 | 2010-10-13 | 华为技术有限公司 | Interentity auditing method and system |
CN101599925B (en) * | 2009-07-10 | 2011-04-13 | 中国联合网络通信集团有限公司 | Method and system for re-registering media gateway, media gateway controller and media gateway |
CN101313558B (en) * | 2006-03-09 | 2011-11-16 | 华为技术有限公司 | Method realizing media gateway internal connection |
Family Cites Families (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2002084363A (en) * | 2000-09-06 | 2002-03-22 | Nec Corp | Gateway system and line control method used therefor |
JP2002290551A (en) * | 2001-03-28 | 2002-10-04 | Nec Corp | Gateway system and trouble processing method for use therein |
US6985734B2 (en) * | 2001-10-01 | 2006-01-10 | Telefonaktiebolaget Lm Ericsson (Publ) | Telecommunications system and method for implementing H. 248 media gateways within third-generation mobile access networks |
-
2003
- 2003-11-14 CN CNB200310112214XA patent/CN1301604C/en not_active Expired - Fee Related
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN101022454B (en) * | 2006-02-16 | 2010-10-13 | 华为技术有限公司 | Interentity auditing method and system |
CN101313558B (en) * | 2006-03-09 | 2011-11-16 | 华为技术有限公司 | Method realizing media gateway internal connection |
CN101599925B (en) * | 2009-07-10 | 2011-04-13 | 中国联合网络通信集团有限公司 | Method and system for re-registering media gateway, media gateway controller and media gateway |
Also Published As
Publication number | Publication date |
---|---|
CN1301604C (en) | 2007-02-21 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
CN101478407B (en) | Method and apparatus for on-line safe login | |
EP1643731B1 (en) | Method and apparatus for merging call components during call reconstruction | |
EP2629477B1 (en) | Global session identifier | |
CN111885270B (en) | Abnormal communication detection method, device, equipment and storage medium | |
EP1906589A1 (en) | An overload control method for the access media gateway and an access media gateway | |
WO2004002043B1 (en) | Methods and systems for improving trunk utilization for calls to ported numbers | |
CN1612538A (en) | Method for binding hardware address and port for Ethernet two-hier exchange equipment | |
CN111984561A (en) | IPMI command processing method, system, device and medium for BMC | |
CN1859361A (en) | Method for detecting terminal on-line state of meeting sponsored protocol server | |
CN1301604C (en) | Method for detecting H.248 protocol abnormal context | |
CN106572103B (en) | hidden port detection method based on SDN network architecture | |
CN102968479A (en) | Safety zone crossing database backup method | |
CN109067782A (en) | IMS network session abnormal interrupt attack detecting device and method | |
KR101384868B1 (en) | Enhanced call tracing | |
KR101534160B1 (en) | Apparatus and method for VoLTE session management in 4G mobile network | |
CN100359906C (en) | Method for synchronizing H.248 protocol user state | |
KR100825257B1 (en) | Detail processing method of abnormal traffic data | |
CN1559135A (en) | Method for the transmission of data in a packet-oriented data network | |
CN101594554A (en) | Called service servers, multi-service access node device and calling and called control implementation method | |
CN1638348A (en) | Method for sending multiple ephemeral terminations in a single service change message | |
CN111092911B (en) | Network agent realizing method for enhancing safety | |
CN1799036A (en) | Auto-determination of DTE/DCE connection | |
JP2001077857A (en) | Filtering processing device, network provided with it and its storage medium | |
CN106657095B (en) | Method and system for identifying unknown remote control trojan horse | |
CN1976370A (en) | Method for keeping call data uniformity after master-slave gateway replacing |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
C06 | Publication | ||
PB01 | Publication | ||
C10 | Entry into substantive examination | ||
SE01 | Entry into force of request for substantive examination | ||
C14 | Grant of patent or utility model | ||
GR01 | Patent grant | ||
CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20070221 Termination date: 20171114 |
|
CF01 | Termination of patent right due to non-payment of annual fee |