CN1866850A - Method for H.323 gatekeeper realizing H.323 terminal timely registration - Google Patents
Method for H.323 gatekeeper realizing H.323 terminal timely registration Download PDFInfo
- Publication number
- CN1866850A CN1866850A CN 200510070767 CN200510070767A CN1866850A CN 1866850 A CN1866850 A CN 1866850A CN 200510070767 CN200510070767 CN 200510070767 CN 200510070767 A CN200510070767 A CN 200510070767A CN 1866850 A CN1866850 A CN 1866850A
- Authority
- CN
- China
- Prior art keywords
- terminal
- registration
- message
- registered
- request
- 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
Abstract
The invention discloses a H.323 net guard realizing H.323 terminal registring method, which comprises the following steps: (1) H.323 net guard receives H.323 terminal registration request and decides the type of the request and the registration state of H.323 terminal; (2) if the H.323 net guard judges the request registration H.323 terminal conflicts with registered H.323 terminal and the registration request doesn't keep registration request, the H.323 terminal sends one registration detecting information to the registered H.323 terminal; (3) if the registered H.323 terminal response message doesn't receive in given time, the registration state of registered H.323 terminal is changed into non registration state.
Description
Technical field
The present invention relates to a kind of H.323 gatekeeper and realize the H.323 method of endpoint registration, specifically, relate to a kind of H.323 gatekeeper and realize the H.323 timely process registration of terminal.
Background technology
H.323 stipulated in (Packet-based multimedia communications systems publishes in July, 2003, the 7.2nd joint, the 64th～66 page) that terminal (H.323endpoint) H.323 is to H.323 gatekeeper process registration.H.323 terminal is after H.323 gatekeeper succeeds in registration, H.323 terminal can periodically send registration message according to gatekeeper strategy H.323, this registration message always has certain time to live, if in time to live, do not receive the registration message that refreshes, so H.323, gatekeeper thinks that this terminal has been not a login state, and then this terminal has been in not registered state the gatekeeper.To refuse this calling if be in the gatekeeper that H.323 terminal H.323 of not registered state make a call.
When terminal H.323 during to H.323 gatekeeper registers of registration, the gatekeeper finds that this registration is to register first or keep registration message, gatekeeper to allow to register and reply the message of confirming registration.When certain H.323 terminal withdraw from unusually as power down or terminal program for some reason and during off-line, gatekeeper H.323 in the registration time to live, still think this H.323 terminal be in the active registration state, remain with every log-on message of this terminal simultaneously.Within the survival registration period of this terminal, if gatekeeper H.323 receives the call request to this terminal use, because the gatekeeper still preserves the log-on message of this terminal, H.323 gatekeeper can make a call to terminal according to canned data, this calling can cause unusual service to occur, as call failure or the like.In addition, in this terminal that withdraws from unusually survival registration period, if this terminal restarts or re-registers, this moment, the registration transport address of terminal may change, according to gatekeeper's strategy H.323, the gatekeeper can refuse re-registering of this user, and this user may can't register before existing survival registration period finishes so, can't make a call simultaneously and also can't be called out, other every supplementary service also can't provide.Along with the time of time to live is long more, influence also greatly more, occurring the short time easily can not provide the serious problems of service suddenly.
Summary of the invention
Technical problem to be solved by this invention provides a kind of H.323 gatekeeper and realizes the H.323 timely process registration of terminal, make the register requirement in its former survival registration period, initiated because of the improper H.323 terminal that withdraws to be accepted by gatekeeper H.323, can redefine the H.323 login state of terminal at short notice, and the login state of new terminal more timely, terminal can in time provide every call service thereby make H.323.
For solving the problems of the technologies described above, it is as follows to the invention provides scheme:
A kind of H.323 gatekeeper realizes the H.323 timely process registration of terminal, comprises the steps:
Step 1: H.323 the gatekeeper receives one H.323 after the registration information of terminal, judges H.323 login state of terminal of the type of this request and this;
Step 2: if determine this request registration H.323 terminal exist with the H.323 terminal registered and conflict, and this register requirement is not when keeping register requirement, then sends one to this registered H.323 terminal that clashes and registers detect-message;
Step 3: if do not receive the response message of this registered H.323 terminal at the appointed time, login state that then will this registered H.323 terminal is updated to not registered state.
Further, the method for the invention also further comprises step:
Step 4: to this request registration H.323 terminal send the message that succeeds in registration, and preserve this H.323 log-on message of terminal, it is set is the normal registration state.
Described in the described step 4 to this request registration H.323 terminal send succeed in registration message by gatekeeper H.323 directly to this request registration H.323 terminal send the acknowledge message that succeeds in registration and realize.
Described in the described step 4 to this request registration H.323 terminal send the message that succeeds in registration be by: when gatekeeper H.323 receives this request registration H.323 during the request registration message of terminal once more, to this request registration H.323 terminal send that the acknowledge message that succeeds in registration realizes.
In the method for the invention, described step 1, if do not determine conflict, then to this request registration H.323 terminal respond the message that succeeds in registration, and preserve this H.323 log-on message of terminal, it is set is the normal registration state.
In the method for the invention, in the described step 1, if determine this solicited message type for keeping register requirement, then to this H.323 terminal respond and keep succeeding in registration, H.323 the login state of terminal is still effective for this.
In the method for the present invention, in described step 1 and the step 2, be to judge and send message according to the log-on message of the registered H.323 terminal of in gatekeeper H.323, preserving.
In the method for the invention, in the described step 2, if receive the response message of this registered H.323 terminal at the appointed time, then this H.323 the login state of terminal is still effective, to this request registration H.323 terminal send the refusal registration message.
In the method for the present invention, in the described step 2,, a timer can be set when the registered H.323 terminal that clashes to this sends a registration detect-message, this timer not then before, no longer to this H.323 terminal send the registration detect-message.
In the method for the invention, in the described step 2, described request is registered terminal H.323, and to have conflict with a H.323 terminal of having registered be that the registration another name is consistent, but the address difference of registering; Or registered address unanimity, but the another name difference of registration; Or registration is called, the address is all identical.
Compared with prior art, the invention has the advantages that:
The present invention sends the registration detect-message by gatekeeper H.323 to terminal H.323 and judges H.323 whether the former registration state of terminal is effective, thereby can be implemented in the former registration time to live of terminal internal cause H.323 H.323 improper the withdrawing from of terminal and the successful registration of the register requirement initiated once more.
Technical problem to be solved by this invention, characteristics and advantage will be in conjunction with the embodiments, are further described with reference to accompanying drawing.
Description of drawings
Fig. 1 is that H.323 gatekeeper of the present invention realizes the H.323 flow chart of the timely register method of terminal.
Fig. 2 be H.323 endpoint registration online after, H.323 the gatekeeper receives the flow chart of a repeated registration request message again.
Fig. 3 be the H.323 terminal registered of success because of withdraw from unusually restart after, initiate the flow chart of register requirement to gatekeeper H.323 immediately.
Embodiment
With reference to Fig. 1, be that H.323 gatekeeper of the present invention realizes the H.323 flow chart of the timely register method of terminal.
A kind of H.323 gatekeeper realizes the H.323 timely process registration of terminal, comprises the steps:
1, H.323 the gatekeeper receives one H.323 after the registration information of terminal, judges the login state of type and this terminal of this request;
The judgement here is to judge according to the log-on message of the registered H.323 terminal of preserving in gatekeeper H.323;
In this step, if do not determine conflict, then to this request registration H.323 terminal respond the message that succeeds in registration, and preserve this H.323 log-on message of terminal, it is set is the normal registration state.
If determine this solicited message type for keeping register requirement, then to this H.323 terminal respond and keep succeeding in registration, H.323 the login state of terminal is still effective for this.
If 2 determine this request registration H.323 terminal exist with the H.323 terminal registered and conflict, and this register requirement is not when keeping register requirement, then sends one to this registered H.323 terminal that clashes and registers detect-message;
Here, described request is registered terminal H.323, and to have conflict with a H.323 terminal of having registered be that the registration another name is consistent, but the address difference of registering; Or registered address unanimity, but the another name difference of registration; Or registration is called, the address is all identical.
Described conflict also is to judge according to the log-on message of the registered H.323 terminal of preserving in gatekeeper H.323.
In this step, if receive the response message of this registered H.323 terminal at the appointed time, then this H.323 the login state of terminal is still effective, to this request registration H.323 terminal send the refusal registration message.
In this step, when the registered H.323 terminal that clashes to this sends a registration detect-message, a timer can be set, this timer not then before, no longer to this H.323 terminal send the registration detect-message.
If 3 do not receive the response message of this registered H.323 terminal at the appointed time, login state that then will this registered H.323 terminal is updated to not registered state.
Here can also increase a step:
4, to this request registration H.323 terminal send the message that succeeds in registration, and preserve this H.323 log-on message of terminal, it is set is the normal registration state.
Here, described to this request registration H.323 terminal send succeed in registration message can by gatekeeper H.323 directly to this request registration H.323 terminal send the acknowledge message that succeeds in registration and realize.
Also can be by: when gatekeeper H.323 receives this request registration H.323 during the request registration message of terminal once more, to this request registration H.323 terminal send that the acknowledge message that succeeds in registration realizes.
With reference to Fig. 2, when H.323 having registered when online, H.323 the gatekeeper receives the H.323 login request message of terminal B, the entrained log-on message of this registration message conflicts mutually with the log-on message of registering online H.323 terminal A, H.323 the gatekeeper sends the detection registration message, and the relevant treatment flow process is as follows:
201, H.323 terminal A sends RRQ request registration message to gatekeeper's normal registration H.323;
202, H.323 the gatekeeper sends the affirmation message RCF that succeeds in registration to terminal A H.323, preserves the H.323 log-on message of terminal A, and is provided with H.323 that terminal is in the normal registration state;
203, H.323 terminal B sends RRQ request registration message to gatekeeper's normal registration H.323, and the entrained log-on message of this registration message conflicts with the log-on message of terminal A H.323;
204, H.323 the gatekeeper sends registration detect-message CHECKMSG to terminal A H.323;
205, H.323 terminal A sends the response message RESPONDMSG of detection to gatekeeper H.323, and H.323 the gatekeeper knows that the login state of terminal A is effective;
206, H.323 the gatekeeper sends refusal registration message RRJ to terminal B H.323.
In above-mentioned steps 203, described afoul registration message is consistent as the another name of registering, but the address of registration is different.
With reference to accompanying drawing 3, H.323 terminal A registration is withdrawed from after online unusually, H.323 terminal A initiates register requirement immediately again, H.323 the gatekeeper receives the H.323 login request message of terminal A, this registration message is when registering online H.323 terminal A registration message and conflict, the gatekeeper initiatively sends the registration detect-message, and the relevant treatment flow process is as follows:
301, H.323 terminal A sends RRQ request registration message to gatekeeper's normal registration H.323;
302, H.323 the gatekeeper sends the affirmation message RCF that succeeds in registration to terminal A H.323, preserves the H.323 log-on message of terminal A, and is provided with H.323 that terminal is in the normal registration state;
303, H.323 initiate register requirement to gatekeeper H.323 immediately behind the terminal A power-off restarting, send RRQ request registration message, the entrained log-on message of this login request message conflicts with the log-on message of terminal A H.323;
304, H.323 the gatekeeper sends registration detect-message CHECKMSG to terminal A H.323;
305, H.323 the gatekeeper does not receive that in official hour H.323 the RESPONDMSG of terminal A transmission responds;
306, H.323 H.323 the gatekeeper changes that the login state of terminal A is invalid; And the H.323 terminal A after above-mentioned restarting sends the message RCF that succeeds in registration.
In above-mentioned steps 303, described afoul registration message is consistent as the another name of registering, but the address of registration is different.
H.323 gatekeeper of the present invention realizes the H.323 timely process registration of terminal, be not restricted to listed utilization in specification and the execution mode, it can be applied to various suitable the present invention's field fully, for those skilled in the art, can easily realize additional advantage and make amendment, therefore under the situation of the spirit and scope of the universal that does not deviate from claim and equivalency range and limited, the examples shown that the present invention is not limited to specific details, representational equipment and illustrates here and describe.
Claims (10)
1, a kind of H.323 gatekeeper realizes the H.323 timely process registration of terminal, it is characterized in that comprising the steps:
(1) H.323 the gatekeeper receives one H.323 after the registration information of terminal, judges H.323 login state of terminal of the type of this request and this;
(2) if determine this request registration H.323 terminal exist with the H.323 terminal registered and conflict, and this register requirement is not when keeping register requirement, then sends one to this registered H.323 terminal that clashes and registers detect-message;
(3) if do not receive the response message of this registered H.323 terminal at the appointed time, login state that then will this registered H.323 terminal is updated to not registered state.
2, the method for claim 1 is characterized in that further comprising the steps:
(4) to this request registration H.323 terminal send the message that succeeds in registration, and preserve this H.323 log-on message of terminal, it is set is the normal registration state.
3, method as claimed in claim 2 is characterized in that: described in the described step (4) to this request registration H.323 terminal send succeed in registration message by gatekeeper H.323 directly to this request registration H.323 terminal send the acknowledge message that succeeds in registration and realize.
4, method as claimed in claim 2, it is characterized in that: described in the described step (4) to this request registration H.323 terminal send the message that succeeds in registration be by: when gatekeeper H.323 receives this request registration H.323 during the request registration message of terminal once more, to this request registration H.323 terminal send that the acknowledge message that succeeds in registration realizes.
5, the method for claim 1 is characterized in that described step (1), if do not determine conflict, then to this request registration H.323 terminal respond the message that succeeds in registration, and preserve this H.323 log-on message of terminal, it is set is the normal registration state.
6, the method for claim 1 is characterized in that described step (1), if determine this solicited message type for keeping register requirement, then to this H.323 terminal respond and keep succeeding in registration, H.323 the login state of terminal is still effective for this.
7, the method for claim 1 is characterized in that described step (1) and step (2), is to judge and send message according to the log-on message of the registered H.323 terminal of preserving in gatekeeper H.323.
8, the method for claim 1, it is characterized in that described step (2), if receive the response message of this registered H.323 terminal at the appointed time, then this H.323 the login state of terminal is still effective, to this request registration H.323 terminal send the refusal registration message.
9, the method for claim 1, it is characterized in that described step (2),, a timer can be set when the registered H.323 terminal that clashes to this sends a registration detect-message, this timer not then before, no longer to this H.323 terminal send the registration detect-message.
10, the method for claim 1 is characterized in that in the described step (2), and described request is registered terminal H.323, and to have conflict with a H.323 terminal of having registered be that the registration another name is consistent, but the address difference of registering; Or registered address unanimity, but the another name difference of registration; Or registration is called, the address is all identical.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2005100707672A CN100440797C (en) | 2005-05-18 | 2005-05-18 | Method for H.323 gatekeeper realizing H.323 terminal timely registration |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CNB2005100707672A CN100440797C (en) | 2005-05-18 | 2005-05-18 | Method for H.323 gatekeeper realizing H.323 terminal timely registration |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN1866850A true CN1866850A (en) | 2006-11-22 |
| CN100440797C CN100440797C (en) | 2008-12-03 |
Family
ID=37425741
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CNB2005100707672A Expired - Fee Related CN100440797C (en) | 2005-05-18 | 2005-05-18 | Method for H.323 gatekeeper realizing H.323 terminal timely registration |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN100440797C (en) |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2013082887A1 (en) * | 2011-12-08 | 2013-06-13 | 中兴通讯股份有限公司 | Method for detecting abnormal exit of client and webserver |
| US8537779B2 (en) | 2007-05-11 | 2013-09-17 | Huawei Technologies Co., Ltd. | Method, system, and apparatus for registration processing |
| CN105634778A (en) * | 2014-11-04 | 2016-06-01 | 中兴通讯股份有限公司 | Method and system to achieve VNF instantiation, NFVO and VNFM |
Family Cites Families (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR100326332B1 (en) * | 1999-09-06 | 2002-03-08 | 윤종용 | Method for communicating between terminal of packet-based network and terminal to be connected through remote access server |
| KR100408048B1 (en) * | 2001-12-31 | 2003-12-01 | 엘지전자 주식회사 | Method for redundancy ip-telephone service system server based on internet |
| CN1317854C (en) * | 2002-04-20 | 2007-05-23 | 中兴通讯股份有限公司 | Method for detecting medium gateway controller and medium between-gateways link state |
| US20050018652A1 (en) * | 2003-07-21 | 2005-01-27 | Siemens Information And Communication Networks, Inc. | System and method for proxy gatekeeper in H.323 based IP telephony systems |
-
2005
- 2005-05-18 CN CNB2005100707672A patent/CN100440797C/en not_active Expired - Fee Related
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8537779B2 (en) | 2007-05-11 | 2013-09-17 | Huawei Technologies Co., Ltd. | Method, system, and apparatus for registration processing |
| US8787314B2 (en) | 2007-05-11 | 2014-07-22 | Huawei Technologies Co., Ltd. | Method, system, and apparatus for registration processing |
| USRE48067E1 (en) | 2007-05-11 | 2020-06-23 | Huawei Technologies Co., Ltd. | Method, system, and apparatus for registration processing |
| USRE49675E1 (en) | 2007-05-11 | 2023-09-26 | Huawei Technologies Co., Ltd. | Method, system, and apparatus for registration processing |
| WO2013082887A1 (en) * | 2011-12-08 | 2013-06-13 | 中兴通讯股份有限公司 | Method for detecting abnormal exit of client and webserver |
| CN105634778A (en) * | 2014-11-04 | 2016-06-01 | 中兴通讯股份有限公司 | Method and system to achieve VNF instantiation, NFVO and VNFM |
| CN105634778B (en) * | 2014-11-04 | 2020-09-22 | 南京中兴软件有限责任公司 | Method and system for realizing VNF instantiation, NFVO and VNFM |
Also Published As
| Publication number | Publication date |
|---|---|
| CN100440797C (en) | 2008-12-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN1845554A (en) | Control method for dynamically distributing IP address in 3G network | |
| CN101069144A (en) | Computer and method for on-demand network access control | |
| CN1650656A (en) | Address de-registration from IP multimedia networks | |
| CN101056306A (en) | Network device and its access control method | |
| CN101075910A (en) | Method and device for fastly registering | |
| CN101056275A (en) | A setting method for group message receiving mode in the instant communication system | |
| CN101039312A (en) | Method and apparatus for preventing service function entity of general authentication framework from attack | |
| CN1835515A (en) | Method and device of going repeating in configuration procedue of dynamic host address | |
| CN1866850A (en) | Method for H.323 gatekeeper realizing H.323 terminal timely registration | |
| CN1748388A (en) | Transmit the method for binding update messages and binding response message | |
| CN101056273A (en) | Session-based network speed limit method and device | |
| CN1161924C (en) | Data upgrading method of two-layer exchange equipment | |
| CN1917427A (en) | Method and equipment for quick recovering environment of portal authentication | |
| CN1561043A (en) | Multi-user concurrent insertion device and its method | |
| CN1863202A (en) | Method for improving load balance apparatus and servicer processing performance | |
| CN101030878A (en) | Method for grouping visual-information network, DHCP server and visual information terminal | |
| CN101079892A (en) | Processing method, system and device for subscription and registration status | |
| CN101039332A (en) | Method, system and server for transmitting page data | |
| CN1798060A (en) | Method and device for detecting conflict of IP addresses in networked computers | |
| CN101064940A (en) | Method for realizing call | |
| CN1286309C (en) | A method and system for H.248 message processing in distributed processing gateway | |
| CN1815954A (en) | Method for realizing user information synchronization and identifying authority of user's terminaal | |
| CN1175632C (en) | Method for checking validity of data message transmitting sequence number | |
| CN1697551A (en) | Mobility management of an inactive terminal in a mobile network in packet mode | |
| CN101043332A (en) | System for recognizing true-false client in IM software and method thereof |
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 | ||
| TR01 | Transfer of patent right | ||
| TR01 | Transfer of patent right |
Effective date of registration: 20180426 Address after: California, USA Patentee after: Global innovation polymerization LLC Address before: 518057, Nanshan District high tech Industrial Park, Guangdong province Shenzhen science and technology south road Zhongxing building A block 6 Patentee before: ZTE Corp. |
|
| CF01 | Termination of patent right due to non-payment of annual fee | ||
| CF01 | Termination of patent right due to non-payment of annual fee |
Granted publication date: 20081203 |