CN1177450C - Implementation method of "heartbeat" technology in Internet personal number service - Google Patents

Abstract

The present invention relates to an implementation method of a 'heartbeat' technology in an internet personal number service, which can be used for ensuring reliable communication between an internet personal number service server and a user server (US) after a communication linkage is established, and simultaneously, the method can also be used for reducing the quantity of interaction data between the internet personal number service server and the user server to save the bandwidth. The method comprises: a heartbeat timer is started by an active heartbeat party (the internet personal number service server) after the communication linkage to start timing; the heartbeat timer is reset in a heartbeat time interval as long as the active party receives any response message of a passive party (US); the active heartbeat party transmits a heartbeat message to the US when the timing time of the heartbeat timer reaches the heartbeat time interval but the active heartbeat party still does not receive any response message from the passive party, and the communication linkage is judged as out of order when continuous execution reaches a maximal number of retries. The heartbeat time interval and the maximal number of retries are designated in a response message for responding to a login request, and the response message for responding to a login request is transmitted by the US to the internet personal number service server.

Description

Implementation method of "heartbeat" technology in Internet personal number service

technical field

The present invention relates to IP (Internet Protocol: Internet protocol) communication technology, and more precisely relates to a new Internet personal number service (ONLY: One Number Link You), which realizes interactive connection between two communication devices "Heartbeat" technology.

Background technique

With the development of the Internet, Internet users are increasingly demanding a convenient means of communicating with each other and obtaining information anytime and anywhere. The ONLY service is designed to meet the needs of users by integrating traditional telecommunications technology and IP technology. An innovative business developed on the basis of The core idea of the ONLY service is to assign an ONLY number to each user, regardless of whether he is a telephone user or a PC user, and regardless of whether the user is surfing the Internet, through the ONLY system and using the ONLY number, the call can be made to the fixed line of the ONLY user. (office phone, home phone), mobile phone (mobile phone), pager, PC, etc. are connected to realize four services: phone to phone, phone to PC, PC to phone, and PC to PC.

The ONLY service solves the number problems, billing problems, mapping problems of multiple phone numbers, and user mobility problems when PC users and ordinary phone users communicate with each other. To use the ONLY service, the user only needs to apply for an ONLY number (a virtual number, such as a special service number 166 plus an 8-digit number ×××××××× including the area code), and no matter where the user goes, other Users can use the ONLY number to contact him by using equipment such as telephones and PCs. The method for ONLY users to receive information can be based on the user's own settings, establish real-time contact with the calling user by telephone or PC, or listen to the message by voice mailbox.

To realize ONLY business, it is necessary to set up an ONLY server (ONLY Server) and a user server (User Server, which can be shortened to US). The ONLY server is used to complete the connection control of all business users. Once the ONLY number of the called user is obtained, the call will be connected to the ONLY server first, and then the ONLY server will perform subsequent connection operations according to the user's pre-customization to ensure the unified management of PC users and Phone users; User Server (US) Responsible for call policy control, policy control can be customized by the user (such as rules for transferring calls when busy), and stored in the ONLY database.

When an ONLY call arrives, the ONLY server queries the user server, and the user server obtains the user's pre-customized call path (number) by accessing the database, and then transfers it to the corresponding communication device. If the call is made to an ordinary phone or a mobile phone, the ONLY server initiates a call to the IP telephony gateway (GW) where the called number is located; if the call is made to a PC client, the ONLY server initiates a call directly to the called user end; , the ONLY server transfers the call to the user's voice mailbox.

Shown in Fig. 1 is to realize the networking structure and call flow of ONLY business, the calling party user calls the ONLY number, and the call of all calling ONLY numbers can be all routed on the ONLY server 104 through gateway (GW) 102 or 103, ONLY server 104 Send a request to the user server (US) 105, the user server (US) 105 queries the database 106, obtains the actual phone number or IP address that should be connected at present according to the current state of the called user and the registration data, and returns to the ONLY server 104, the ONLY server 104 initiates a call to the actual telephone number or IP address of the called user via the gateway (GW) 102 or 103 and the public telephone network (PSTN) 109 or 123 under the support of the gatekeeper (GK) 101 . What the user server (US) 105 returns to the ONLY server 104 is one or more phone numbers and IP addresses customized in advance according to the called user. The telephone (Telephone) 110,119 shown in the figure, facsimile machine (Fax) 111,120, portable computer (Laptopcomputer) 113,122, modem (Modem) 112,121 are all user equipments, and 115 is PC client ( PCC: PC Client).

As we all know, between two communicating terminals, in order to obtain the connection status (TCP connection or UDP connection) between the two terminals in real time, a "heartbeat" interaction is generally required.

The existing "heartbeat" design generally sends a heartbeat request message from one end (client) to the other end (server) regularly, and the other end (server) receives the heartbeat request message from the opposite end (client). After that, it will respond with a heartbeat response message. If one end (client or server) does not receive a heartbeat message (heartbeat request message or heartbeat response message) from the other end (server or client) within a predetermined period of time, the connection between the two is considered The situation is abnormal.

This heartbeat design can certainly maintain a reliable connection between the client and the server, but there are actually other data interactions between the client and the server, such as call data, billing data, etc., where normal interaction can take place In the case of , it can be proved that the connection between the client and the server is reliable and there is no problem. If the "heartbeat" interaction is still performed at this time, it is obviously unnecessary.

In the ONLY new business introduced above, ONLY Server and US are the two main functional components in the ONLY system, and TCP connection is used between ONLY Server and US. In order to ensure its TCP connection in real time and reduce unnecessary data packet interaction, a new concept of high-efficiency heartbeat technology is required in the ONLY business.

Contents of the invention

The purpose of the present invention is to design a method for realizing the "heartbeat" technology in the Internet personal number service (ONLY), which can ensure reliable communication between the ONLY Server and the US, and can also reduce the amount of interactive data between the ONLY Server and the US, to save bandwidth.

The technical scheme that realizes the object of the present invention is such: a kind of realization method of " heartbeat " technology in Internet personal number service (ONLY), it is characterized in that comprising:

A. The active party of the heartbeat of the communication connection starts the heartbeat timer to start timing after sending a login request message to the passive party and responding to the login response message in the passive direction. There is a heartbeat in the login response message Time interval and maximum number of retries;

B. In the heartbeat time interval, when the active side of the heartbeat receives any response message from the passive side, reset the heartbeat timer and start timing again;

C. After the timing time of the heartbeat timer reaches the heartbeat time interval, when the active party of the heartbeat does not receive any response message from the passive party, it sends a heartbeat message to the passive party. When step C is continuously executed and the maximum number of retries is reached , judging that the communication connection between the active party and the passive party is faulty.

The step A is to start the heartbeat after the Internet personal number service (ONLY) server sends a login request message to the user server, and after the Internet personal number service (ONLY) server receives the response login request response message sent by the user server The timer starts counting.

In the step B, any response message includes any data message and heartbeat message between the Internet Personal Number Service (ONLY) server and the user server.

The maximum number of retries is specified in the response message of the login request sent by the user server to the Internet Personal Number Service (ONLY) server.

The heartbeat time interval is specified in the login request response message sent by the user server to the Internet Personal Number Service (ONLY) server.

The timing time of the heartbeat timer is set as the heartbeat time interval.

The implementation method of the "heartbeat" technology in the Internet personal number service (ONLY) of the present invention, the heartbeat interaction is only performed when the data interaction between the two communicating terminals is idle. Through the heartbeat design of this new concept, the reliability of data interaction between two communicating terminals can be guaranteed, and at the same time, the amount of interactive data can be effectively reduced and bandwidth can be saved.

The method of the present invention can also be applied to new IP communication services besides the ONLY service.

Description of drawings

FIG. 1 is a schematic diagram of a network structure and a call flow for realizing an ONLY service by using an existing gateway function.

Fig. 2 is a block diagram of the interactive connection flow of "heartbeat" and response messages between the ONLY server and the user server.

Implementation

The description of Fig. 1 has been mentioned above, and will not be repeated here.

Referring to Figure 2, the figure shows the process of the ONLY server interacting with the User server to complete the TCP connection.

(1) When a TCP connection is established between ONLY SERVER and US, ONLY SERVER sends a login (registration) request message to US;

(2) The US judges the legality according to the user identification (ID) and password, and returns the corresponding response login response message;

(3) After the ONLY SERVER registers successfully, it sends a heartbeat message to the US;

(4) US responds to ONLY SERVER with a heartbeat response message;

(5) When the ONLY SERVER stops running, it sends a logout request message to the US.

The transmission of the above message adopts the TCP protocol.

When the ONLY Server starts, the ONLY Server sends a login request to the User Server, and the request information contains the identification (ID) number and password of the ONLY Server; When it is busy, it should return the response message of the login pass, which contains the heartbeat time interval and the maximum number of retries, and the system enters the heartbeat signal process and call process.

ONLY Server should send a heartbeat message after the communication link between ONLY Server and User Server is idle for a certain period of time. After the system enters the heartbeat signal process, start the heartbeat timer to start timing. The heartbeat time interval and the maximum number of retries are specified in the login request response message provided by the User Server to the ONLY Server. For example, the default value is sent once every 10 seconds. The maximum number of retries is 5. If the ONLY Server does not receive any message from the User Server within 10 seconds from the start of the heartbeat timer, it will send a heartbeat message. If no response is received after sending 5 times, the User Server will be considered If there is a fault, within 10 seconds from the start of the heartbeat timer, if the ONLY Server receives any message from the User Server, it will reset the heartbeat timer and start timing again.

When the ONLY Server stops running, the ONLY Server sends a logout request to the User Server. After receiving the message, the User Server should consider that the ONLY Server has left the login state. At this time, the User Server does not need to send a response message to the ONLY Server.

The above embodiments can be generalized and applied, assuming that two terminals are connected by communication, one is the active side and the other is the passive side. The heartbeat timer is started by the active party of the heartbeat. When the active party sends any data message to the passive party, including the heartbeat message, if the active party receives any response message from the passive party, it can be considered that the relationship between the passive party and the active party is If the connection between them is normal, reset the heartbeat timer and start timing again. Of course, if the heartbeat timer event has occurred, the active party should still send a heartbeat message to the passive party.

The heartbeat interaction method of the present invention is used in the ONLY service and has good practicability. It can also be applied to any IP communication service.

Claims (6)

1. An implementation method of "heartbeat" technology in Internet personal number services, characterized in that it comprises the following processing steps: A. The active party of the heartbeat of the communication connection starts the heartbeat timer to start timing after sending a login request message to the passive party and responding to the login response message in the passive direction. There is a heartbeat in the login response message Time interval and maximum number of retries; B. In the heartbeat time interval, when the active side of the heartbeat receives any response message from the passive side, reset the heartbeat timer and start timing again; C. After the timing time of the heartbeat timer reaches the heartbeat time interval, when the active party of the heartbeat does not receive any response message from the passive party, it sends a heartbeat message to the passive party. When step C is continuously executed and the maximum number of retries is reached , judging that the communication connection between the active party and the passive party is faulty. 2. The implementation method of "heartbeat" technology in a kind of Internet personal number service according to claim 1, characterized in that: said step A is sending a login request message from the Internet personal number service server to the user server, and After the Internet personal number service server receives the login request response message sent by the user server, it starts the heartbeat timer to start timing. 3. The implementation method of "heartbeat" technology in a kind of Internet personal number service according to claim 1, characterized in that: in said step B, any response message includes Internet personal number service server and user server Any data packets and heartbeat packets between. 4. The implementation method of "heartbeat" technology in a kind of Internet personal number service according to claim 1, characterized in that: the maximum number of retries is the response log sent by the user server to the Internet personal number service server specified in the request-reply message. 5. The implementation method of "heartbeat" technology in a kind of Internet personal number service according to claim 1, characterized in that: the heartbeat time interval is the response login request sent by the user server to the Internet personal number service server specified in the reply message. 6. A method for implementing "heartbeat" technology in Internet personal number service according to claim 1, characterized in that: the timing time of the heartbeat timer is set as the heartbeat time interval.

Images