CN106612307A - Always-on service implementation method and device - Google Patents

Abstract

The embodiment of the present invention discloses a method for realizing an always-on service. The method includes: at least once, the CS deployed outside the firewall sends a CS registration request message to the PS deployed inside the firewall, and the CS correspondingly receives the at least once The CS registration response message returned by the PS, establish at least one first long connection with the PS; receive the AOE registration request message sent by the AOE, and select a first long connection from the at least one first long connection as The first long connection of the AOE, and forward the AOE registration request message to the PS through the first long connection of the AOE; receive the AOE registration response message returned by the PS through the first long connection of the AOE, and send The PS Session ID in the AOE registration response message is deleted and forwarded to the AOE. The embodiment of the invention also discloses a device for realizing the always-on service.

Description

Method and device for realizing always-on service

technical field

The invention relates to the field of data services, in particular to a method and device for realizing an always-on service.

Background technique

The always-on (Always On/IP Push) technology is a technology in which a server actively sends information to a client, and is currently widely used in the field of mobile communications. Through the always-on technology, the server can actively and timely push important information to the user terminal, so that the user terminal can receive information anytime and anywhere, which provides great convenience for the user.

Always-on technology is a long connection technology based on Transmission Control Protocol/Internet Protocol (TCP/IP, Transmission Control Protocol/Internet Protocol). The user terminal includes a business-related client, and the client needs to maintain a TCP connection with the server. Long connection, the server can push information to the client when the connection is valid.

For the convenience of description, the client side in the always-on technology is defined as the always-on engine (AOE, Always-On Engine), and the server side is defined as the always-on gateway (AOG, Always-OnGateway). The gateway's TCP long connection, and receive the message pushed by the AOG gateway. AOG maintains a long TCP connection with the user terminal AOE, and pushes important messages to the user terminal AOE when needed.

The AOG needs to save relevant data of the user terminal, such as the identifier of the user terminal, offline messages, and the like. In order to ensure the security of user terminal data, avoid potential network attacks, and ensure the stability of the AOG system, AOG and its database need to be deployed within the firewall device. The TCP persistent connection between AOE and AOG of the user terminal needs to pass through the firewall device.

As shown in Figure 1, the AOE of the user terminal maintains a TCP persistent connection with the AOG through the firewall, and each online user terminal (such as terminal A and terminal B) exclusively occupies a TCP persistent connection of the firewall device. As the number of online user terminals continues to grow , the number of concurrent connections passing through the firewall will continue to increase, and the pressure on the firewall will be high. Since the number of concurrent connections supported by firewall devices is limited, in order to support more online users, higher-end firewall devices need to be deployed, which greatly increases operating costs.

Contents of the invention

In view of this, the embodiments of the present invention expect to provide a method and device for implementing an always-on service, which can reduce the pressure on the firewall and further reduce the operating cost of the system.

In order to achieve the above object, technical solution of the present invention is achieved in that way:

A method for implementing an always-on service, the method being applied to a connection server CS deployed outside a firewall, comprising:

Sending a CS registration request message to the push service server PS deployed in the firewall at least once, the CS registration request message includes the IP address of the CS, and the IP address of the CS is used to make the CS registration request message pass through Firewall to said PS;

Corresponding to receiving at least one CS registration response message returned by the PS, establishing at least one first long connection with the PS;

Receive the AOE registration request message sent by the always-on engine AOE, create a corresponding CS session session for the AOE according to the AOE registration request message, and record the CS Session ID corresponding to the CS Session;

Selecting a first persistent connection from the at least one first persistent connection as the first persistent connection of the AOE, and forwarding the AOE registration request message to the PS through the first persistent connection of the AOE;

receiving the AOE registration response message returned by the PS through the first long connection of the AOE, the AOE registration response message carrying the PSSession ID of the PS Session created by the PS for the AOE;

The CS saves the PS Session ID, deletes the PSSession ID in the AOE registration response message and forwards it to the AOE;

receiving the AOE message sent by the AOE, adding a CS-PS message header to the AOE message and forwarding it to the PS through the first long connection of the AOE, and the CS-PS message header includes the AOE identifier, PS Session ID and CS Session ID;

Receive the PS message returned by the PS through the first long connection of the AOE, delete the CS-PS message header in the PS message, and forward it to the AOE.

In the above solution, after establishing at least one first long connection with the PS, the method further includes:

Sending the CS load information to the PS at regular intervals through any one of the first long connections.

A method for realizing an always-on service, the method being applied to a push service server PS deployed outside a firewall, comprising:

receiving a CS registration request message sent by a connection server CS deployed outside the firewall, and returning a CS registration response message to the CS, and establishing a first long connection with the CS;

Receive the AOE registration request forwarded by the CS through the first persistent connection of the always-on engine AOE in the first persistent connection, create a corresponding PS session session for the AOE according to the AOE registration request message, and record the PS session corresponding PS Session ID;

sending an AOE registration response message to the CS through the first long connection of the AOE, where the AOE registration response message carries the PS Session ID;

Receive the AOE message forwarded by the CS through the first long connection of the AOE, the AOE message carries the CS-PS message header, and the CS-PS message header includes the AOE identifier, PS SessionID and CS Session ID;

Locate the AOE Session according to the AOE ID and the PS Session ID, and complete the processing of the AOE message;

Returning a PS message to the CS through the first long connection of the AOE, where the PS message carries the CS-PS message header.

In the above solution, after establishing at least one first long connection with the CS, the method further includes:

receiving CS load information sent by the CS, and sending the CS load information to a state synchronization device;

receiving CS load information of each CS synchronized by the state synchronization device;

Receive the passing request message sent by the AOE, select the CS with the lightest load according to the CS load information of the CSs, and return a passing response message, the passing response message carrying the IP address of the CS with the lightest load.

A method for implementing an always-on service, the method being applied to an always-on engine AOE on a user terminal, including:

Send an AOE registration request message to the connection server CS;

receiving the AOE registration response message forwarded by the CS;

sending an AOE message to the CS;

Receive the push service server PS message forwarded by the CS.

In the above solution, before sending the AOE registration request message to the CS, the method further includes:

Send a pass request message to PS;

receiving a passing response message returned by the PS, where the passing response message carries the IP address of the CS with the lightest load;

Correspondingly, the sending the AOE registration request message to the CS includes:

An AOE registration request message is sent to the CS corresponding to the IP address of the CS with the lightest load.

A connection server CS, comprising:

The first sending unit is configured to send a CS registration request message to the push service server PS deployed in the firewall at least once, the CS registration request message includes the IP address of the CS, and the IP address of the CS is used to use The CS registration request message passes through the firewall to the PS;

The first receiving unit is configured to correspondingly receive at least one CS registration response message returned by the PS, and establish at least one first long connection with the PS;

The first receiving unit is further configured to receive the AOE registration request message sent by the always-on engine AOE, create a corresponding CS session session for the AOE according to the AOE registration request message, and record the CS Session ID corresponding to the CS session ;

The first sending unit is further configured to select a first long connection from the at least one first long connection as the first long connection of the AOE, and send a message to the PS through the first long connection of the AOE Forwarding the AOE registration request message;

The first receiving unit is further configured to receive the AOE registration response message returned by the PS through the first long connection of the AOE, and the AOE registration response message carries the PS Session created by the PS for the AOE PS Session ID;

The first sending unit is further configured to save the PS Session ID, delete the PS Session ID in the AOE registration response message and forward it to the AOE;

The first receiving unit is further configured to receive an AOE message sent by the AOE;

The first sending unit is further configured to add a CS-PS message header to the AOE message received by the first receiving unit and forward it to the PS through the first long connection of the AOE, and the CS-PS The message header includes AOE ID, PS Session ID and CS Session ID;

The first receiving unit is further configured to receive the PS message returned by the PS through the first long connection of the AOE;

The first sending unit is further configured to delete the CS-PS message header in the PS message received by the first receiving unit and forward it to the AOE.

In the above solution, the first sending unit is further configured to regularly send CS load information to the PS through any first long connection after establishing at least one first long connection with the PS.

A push service server PS, comprising:

The second receiving unit is configured to receive a CS registration request message sent by a connection server CS deployed outside the firewall;

a second sending unit, configured to return a CS registration response message to the CS, and establish a first long connection with the CS;

The second receiving unit is further configured to receive the AOE registration request forwarded by the CS through the first persistent connection of the always-on engine AOE in the first persistent connection, and create a corresponding PS for the AOE according to the AOE registration request message Session Session, recording the PS Session ID corresponding to the PS Session;

The second sending unit is further configured to send an AOE registration response message to the CS through the first long connection of the AOE, and the AOE registration response message carries the PS Session ID;

The second receiving unit is further configured to receive an AOE message forwarded by the CS through the first long connection of the AOE, the AOE message carries a CS-PS message header, and the CS-PS message header includes AOE logo, PS Session ID and CS Session ID;

The second sending unit is further configured to locate the AOE Session according to the AOE identifier and PSSession ID received by the second receiving unit, and complete the processing of the AOE message; The CS returns a PS message, and the PS message carries the CS-PS message header.

In the above solution, the second receiving unit is further configured to receive the CS load information sent by the CS after establishing at least one first long connection with the CS;

The second sending unit is further configured to send the CS load information received by the second receiving unit to a state synchronization device;

The second receiving unit is further configured to receive CS load information of each CS synchronized by the state synchronization device;

The second receiving unit is further configured to receive a pass request message sent by the AOE;

The second sending unit is further configured to select the CS with the lightest load according to the CS load information of each CS received by the second receiving unit, and return a passing response message, the passing response message carrying the CS with the lightest load The IP address of the light CS.

An always-on engine AOE, including:

A third sending unit, configured to send an AOE registration request message to the connection server CS;

a third receiving unit, configured to receive the AOE registration response message forwarded by the CS;

The third sending unit is further configured to send an AOE message to the CS;

The third receiving unit is further configured to receive the push service server PS message forwarded by the CS.

In the above solution, the third sending unit is further configured to send a pass request message to the PS before sending the AOE registration request message to the CS;

The third receiving unit is further configured to receive a pass reply message returned by the PS, where the pass reply message carries the IP address of the CS with the lightest load;

Correspondingly, the third sending unit is specifically configured to send an AOE registration request message to the CS corresponding to the IP address of the CS with the lightest load.

The embodiment of the present invention provides a method and device for implementing an always-on service. The AOE of the user terminal establishes a long connection with the PS through the CS. Multiple user terminals can be connected to one CS, and the AOE on each user terminal corresponds to a A TCP long connection communicates with the CS. The TCP long connection between the AOE on the user terminal and the CS does not pass through the firewall; each CS communicates with the PS through a small number of TCP long connections, and multiple user terminals can share the connection between the CS and the PS. A TCP long-term connection between the push services. As the number of online user terminals continues to grow, the AOE of multiple user terminals can share the first long connection between CS and PS, so the number of first long connections passing through the firewall is smaller than the number of user terminals, which greatly reduces the The number of TCP connections passing through the firewall is measured, and in the embodiment of the present invention, the PS related to the data of the user terminal is deployed in the firewall. In this way, under the premise of ensuring the data security of the always-on terminal users and the stability of the server, the number of concurrent connections of the firewall device will not increase significantly with the increase of the number of online users, reducing the demand for firewall capacity, reducing operating costs, and providing user terminals with Safe, stable, and low-cost push service.

Description of drawings

Fig. 1 is a system structure diagram of an always-on service in the prior art;

FIG. 2 is a system structural diagram of an always-on service provided by an embodiment of the present invention;

FIG. 3 is a schematic flowchart of a method for implementing an always-on service provided by an embodiment of the present invention;

FIG. 4 is a schematic flowchart of a CS equalization method provided by an embodiment of the present invention;

FIG. 5 is a structural block diagram of a CS provided by an embodiment of the present invention;

FIG. 6 is a structural block diagram of a PS provided by an embodiment of the present invention;

FIG. 7 is a structural block diagram of an AOE provided by an embodiment of the present invention.

detailed description

The following will clearly and completely describe the technical solutions in the embodiments of the present invention with reference to the drawings in the embodiments of the present invention.

In the prior art, the function of the AOG is to establish and maintain a TCP persistent connection with the AOE on the user terminal, and to perform push services through the TCP persistent connection. Because AOG needs to save relevant data of user terminals; in order to ensure the security of these data, avoid potential network attacks, and ensure the stability of AOG, AOG must be deployed within the firewall; each online user terminal exclusively occupies a TCP port of the firewall device Long connection, as the number of online user terminals continues to grow, the number of concurrent connections passing through the firewall will continue to increase. In order to solve the problem that the always-on service in the prior art is limited by the number of concurrent connections of the firewall, the embodiment of the present invention is based on the system architecture shown in Figure 2 to realize the always-on service. The embodiment of the present invention combines the AOG in the prior art Divided into two modules, one module is defined as AOG's connection server (CS, Connection Server), and the other module is defined as AOG's push service server (PS, Push Server).

PS involves the data of user terminals, and has high requirements for security and stability, so it is deployed within the firewall; CS is only responsible for establishing and maintaining long-term connections with AOE on user terminals, and does not involve user data and systems The core push business has relatively low requirements on system security, relatively simple logic, and strong anti-attack capabilities, so it is deployed outside the firewall.

In the system provided by the embodiment of the present invention, multiple user terminals can be connected to one CS, and the AOE on each user terminal corresponds to a TCP long connection to communicate with the CS, and the TCP long connection between the AOE on the user terminal and the CS The connection does not pass through the firewall; each CS communicates with the PS through a small number of TCP long connections, and multiple user terminals can share a TCP long connection between the CS and the PS for push services. Since the TCP long connection between AOE and CS on the user terminal does not pass through the firewall, only a small number of long connections between CS and PS pass through the firewall, thus greatly reducing the number of TCP connections passing through the firewall and reducing the pressure on the firewall. Reduced system operating costs.

Example 1

The embodiment of the present invention provides a method for implementing an always-on service. As shown in FIG. 3 , the processing flow of the method in this embodiment includes the following steps:

Step 301, the CS sends at least one CS registration request message to the PS deployed inside the firewall at least once, and the PS receives the CS registration request message sent by the CS deployed outside the firewall.

When the CS is started, a TCP persistent connection between the CS and the PS needs to be established through the CS registration process. Since the firewall device restricts the IP address of the CS, the CS registration process does not require complex authentication logic.

After starting the CS registration process, the CS sends a CS registration request message to the PS. Since the CS is deployed outside the firewall and the PS is deployed inside the firewall, the firewall needs to set IP address filtering rules. Only the CS can establish a TCP long connection to the PS. Ensure system security. The CS registration request message includes the CS's IP address, and the CS's IP address enables the CS registration request message to pass through the firewall to the PS.

It should be noted here that the messages transmitted between the devices in this embodiment are all TCP/IP protocol messages, and these messages follow the regulations of the TCP/IP protocol, and the data format is:

Data frame: frame header + IP data packet + frame tail (the frame header includes the initial MAC addresses and types of the source and target hosts, and the frame tail is the checksum word);

IP data packet: IP header + TCP data information (IP header includes source and destination host IP address, type, lifetime, etc.);

TCP data information: TCP header + actual data (TCP header includes source and destination host port numbers, sequence numbers, confirmation numbers, checksums, etc.).

In this step, the source host is CS, the target host is PS, and the CS registration request message sent by CS to PS must carry the IP address of the CS, so that the firewall can allow the CS registration request message to reach the PS.

The CS may send a CS registration request message to the PS multiple times to request to establish multiple TCP long connections with the PS, and the CS uses a different file descriptor when sending the CS registration request message to the PS each time .

Step 302, the PS returns a CS registration response message to the CS, and the CS correspondingly receives the CS registration response message returned by the PS at least once, and establishes at least one first long connection between the CS and the PS.

After receiving the CS registration request message sent by the CS, the PS will create a Session, and return a CS registration response message to the CS, thus establishing a first long connection with the PS. The data format of the CS registration response message complies with the provisions of the TCP/IP protocol.

After the first long connection is established, the CS will periodically send heartbeat messages to maintain the first long connection. When the first long connection is disconnected due to abnormality, the CS needs to perform step 301 again to initiate the CS registration process, and restore the CS and The first longest connection between PSs.

The CS may send a CS registration request message to the PS multiple times, and the PS may create a session corresponding to the CS according to the received CS registration request message each time, and return a corresponding CS registration response message to the CS, so that After each registration is completed, a first long connection between the CS and the PS can be established. That is, for a CS and a corresponding PS, multiple first long connections may be established between the CS and the PS, and these long connections are independent of each other. Multiple first long-term connections can realize load balancing and failover between CS and PS. When a first long-term connection is abnormal, CS can only restore the abnormal connection through the registration process without affecting other first long-term connections, and Another normal first long connection can still be used between the CS and the PS to provide services for the AOE of other user terminals.

Step 303, the AOE sends an AOE registration request message to the CS, and the CS receives the AOE registration request message sent by the AOE, creates a corresponding CS Session for the AOE according to the AOE registration request message, and records the CS Session ID corresponding to the CS Session.

After the first long connection between the CS and the PS is established, the AOE on the user terminal can start the AOE registration process and establish a long connection between the AOE and the PS, so that the PS can push the AOE to the AOE through the long connection. data. When the AOE starts registration, the AOE sends an AOE registration request message to the CS, and the CS receives the AOE registration request message sent by the AOE.

The data format of the AOE registration request message follows the provisions of the TCP/IP protocol.

After receiving the AOE registration request message sent by the AOE, the CS will create a CS Session corresponding to the AOE, and record the CS Session ID corresponding to the CS Session.

Step 304, the CS selects a first persistent connection from the at least one first persistent connection as the first persistent connection of the AOE, and forwards the AOE registration request to the PS through the first persistent connection of the AOE message, the PS receives the AOE registration request forwarded by the CS through the first long connection of the AOE.

After the CS receives the AOE registration request message, it will select a first long connection from at least one first long connection between the CS and the PS as the first long connection of the AOE, and pass the AOE The first long connection forwards the AOE registration request message to the PS.

Step 305, the PS creates a corresponding PSSession for the AOE according to the AOE registration request message, records the PS Session ID corresponding to the PS Session, and returns the AOE registration response message to the CS through the first long connection of the AOE, so The CS receives the AOE registration response message, where the AOE registration response message carries the PS Session ID.

After the PS receives the AOE registration request message through the first long connection of the AOE, it will create a PS Session corresponding to the AOE, and return an AOE registration response message to the CS through the first long connection of the AOE , the AOE registration response message carries the PS Session ID corresponding to the PS Session. The CS receives the AOE registration response message returned by the PS through the first persistent connection of the AOE.

Step 306, the CS saves the PS Session ID, deletes the PS Session ID in the AOE registration response message and forwards it to the AOE, and the AOE receives the AOE registration response message.

After the CS receives the AOE registration response message returned by the PS through the first long connection of the AOE, it saves the PS Session ID in the AOE registration response message, and stores the PS Session ID in the AOE registration response message After deletion, it is forwarded to the AOE.

In this way, the TCP long connection between the AOE and the PS is established, and the TCP long connection between the AOE and the PS includes the TCP long connection between the AOE and the CS, and the first long connection between the CS and the PS.

Multiple AOEs can be registered to one PS through one CS. For example, as shown in Figure 2, there is a corresponding TCP long connection between the AOE of user terminal A and the CS, and the connection between the AOE of user terminal B and the CS There is also a TCP long connection between the CS and the PS. There is only one first long connection between the CS and the PS. The AOE of the user terminal A and the AOE of the user terminal B can share the first long connection between the CS and the PS and the PS to communicate.

In the case where there are N user terminals, the firewall in the prior art needs to support N TCP long connections. Using the method of this embodiment, there need to be N TCP long connections between the N user terminals and the CS, but the N TCP long connections The connection does not pass through the firewall, and the AOE of multiple user terminals can share the first long connection between CS and PS, so the number of first long connections must be less than N, that is, the number of first long connections passing through the firewall is less than N , which greatly reduces the number of TCP connections passing through the firewall, reduces the pressure on the firewall, and reduces the operating cost of the system.

Step 307, the AOE sends an AOE message to the CS, and the CS receives the AOE message sent by the AOE.

Step 308: The CS adds a CS-PS message header to the AOE message and forwards it to the PS through the first long connection of the AOE, and the PS receives the first long connection of the CS through the AOE The AOE message forwarded by the connection.

After the AOE completes the registration process, message transmission can be performed between the AOE and the PS. The AOE may send an AOE message to the CS, and the CS may forward the AOE message to the PS through the first persistent connection of the AOE selected during the AOE registration.

Since the AOEs of multiple user terminals can share a first long connection, when the CS uses the first long connection of the AOE to forward the AOE message to the PS, it needs to add CS- PS message header, so as to distinguish which AOE of the user terminal the AOE message belongs to.

The CS-PS message header includes AOE identification, PS Session ID and CS Session ID; wherein,

AOE identification: the unique identification of the AOE of the user terminal inside the system;

PS Session ID: the ID of the Session created by the PS for the AOE of the user terminal, the PS can quickly locate the Session object of the AOE of the user terminal on the PS by using the PSSession ID (the Session object of the AOE on the PS is that the PS is performing step 305 , and send the corresponding PS Session ID to CS during the registration process);

CS Session ID: The ID of the Session created by the CS for the AOE of the user terminal. The CS can quickly locate the Session object of the AOE of the user terminal on the CS by using the CS Session ID (the Session object of the AOE on the CS is the process in progress of the CS) 303, CS itself records the corresponding CS Session ID).

Step 309, the PS locates the Session of the AOE according to the AOE identifier and the PS Session ID, completes the processing of the AOE message, and returns the PS message to the CS through the first long connection of the AOE, and the CS receives the PS news.

After the PS receives the AOE message forwarded by the CS, it locates the Session object of the AOE according to the AOE identifier and the PS Session ID in the CS-PS message header, and completes the processing of the AOE message; then the PS constructs a PS message, the PS message also needs to carry the CS-PS message header.

Step 310, the CS deletes the CS-PS message header in the PS message and forwards it to the AOE, and the AOE receives the PS message forwarded by the CS.

After the CS receives the PS message sent by the PS, it locates the AOE Session object of the user terminal according to the CSSession ID in the CS-PS message header, removes the CS-PS message header, and only forwards the message content to The AOE of the user terminal, thus realizing the communication between PS and AOE.

When the PS actively pushes data services to the AOE of the user terminal, the PS will first obtain the content to be pushed from other devices, and push the information of the target AOE, namely the AOE ID, PS Session ID and CSSession ID; and then construct it into a PS message to send To the CS, after the CS receives the PS message sent by the PS, according to the CS Session ID in the CS-PS message header, locate the Session object of the AOE of the user terminal, and remove the CS-PS message header, and only The pushed content is forwarded to the AOE of the user terminal, so that the PS actively sends the pushed content to the AOE of the user terminal.

In order to improve the capacity and availability of the AOG system, multiple CSs can be deployed outside the firewall, and through linear expansion, it can support massive user requests. Since the AOE on the user terminal is directly connected to the CS, there is no load balancer device between the AOE and the CS, and different AOEs can be connected to different CSs. Therefore, the AOG system needs to implement CS load balancing logic to ensure that the load between CSs is basically balanced. .

In this embodiment, a state synchronization device is deployed in the PS cluster, and the load balancing of the CS can be realized through the PS and the state synchronization device, as shown in FIG. 4 , the specific method includes the following steps:

Step 401, the CS regularly sends CS load information to the PS through any first long connection, and the PS receives the CS load information sent by the CS.

After step 302, at least one first long connection is established between the CS and the PS, the CS regularly sends CS load information to the PS through any one of the first long connections, and the PS receives the information sent by the CS CS load information. The load information includes the number of AOEs of user terminals loaded by the CS.

Step 402, the PS sends the CS load information to the state synchronization device.

After any PS receives the CS load information sent by the CS, it will send the CS load information to the state synchronization device.

Step 403, the state synchronization device synchronizes the CS load information of each CS to all PSs, and each PS receives the CS load information of each CS synchronized by the state synchronization device.

The state synchronization device can receive the CS load information of each CS synchronized by each PS, and the state synchronization device will synchronously send the CS load information of the CS to all PSs, so that all PSs can obtain the CS load information of each CS. load information.

Step 404, before the AOE sends the AOE registration request message to the CS, it sends a pass request message to the PS, and the PS receives the pass request message sent by the AOE.

Before sending the AOE registration request message to the CS, the AOE will first send a pass request message to the PS, requesting the PS to allocate a CS for registration.

Step 405, the PS selects the CS with the lightest load according to the CS load information of each CS, and returns a passing response message, and the AOE receives the passing response message returned by the PS, and the passing response message carries the load The IP address of the lightest CS.

Due to steps 401-403, all PSs can obtain the CS load information of each CS, so the PS can select the CS with the lightest load according to the CS load information of each CS, and return a pass response message, and the pass response message carries the IP address of the CS with the lightest load.

In steps 404-405, the AOE and the PS communicate by establishing a TCP short connection. After the processing of the request message is completed, the TCP short connection will be automatically disconnected. Therefore, the TCP short connection applied in steps 404-405 connection without putting a huge strain on the firewall.

Step 406, sending an AOE registration request message to the CS corresponding to the IP address of the CS with the lightest load.

According to the IP address of the returned CS, the AOE initiates a registration process to the CS corresponding to the IP address of the CS with the lightest load (refer to step 303), and establishes a TCP long connection. Therefore, the AOE will preferentially register to the CS with the lightest load, thus realizing load balancing of CSs.

Example 2

An embodiment of the present invention provides a CS. As shown in FIG. 5 , the CS includes: a first sending unit 501 and a first receiving unit 502, wherein,

The first sending unit 501 is configured to send a CS registration request message to the push service server PS deployed in the firewall at least once, the CS registration request message includes the IP address of the CS, and the IP address of the CS is used for passing the CS registration request message through the firewall to the PS;

The first receiving unit 502 is configured to correspondingly receive at least one CS registration response message returned by the PS, and establish at least one first long connection with the PS;

The first receiving unit 502 is further configured to receive the AOE registration request message sent by the always-on engine AOE, create a corresponding CS session session for the AOE according to the AOE registration request message, and record the CS session corresponding to the CS session ID;

The first sending unit 501 is further configured to select a first long connection from the at least one first long connection as the first long connection of the AOE, and send a message to the AOE through the first long connection of the AOE The PS forwards the AOE registration request message;

The first receiving unit 502 is further configured to receive the AOE registration response message returned by the PS through the first long connection of the AOE, and the AOE registration response message carries the PS created by the PS for the AOE Session PS Session ID;

The first sending unit 501 is further configured to save the PS Session ID, delete the PS Session ID in the AOE registration response message and forward it to the AOE;

The first receiving unit 502 is further configured to receive the AOE message sent by the AOE;

The first sending unit 501 is further configured to add a CS-PS message header to the AOE message received by the first receiving unit 502 and forward it to the PS through the first long connection of the AOE, and the CS -PS message header includes AOE logo, PS Session ID and CS Session ID;

The first receiving unit 502 is further configured to receive the PS message returned by the PS through the first long connection of the AOE;

The first sending unit 501 is further configured to delete the CS-PS message header in the PS message received by the first receiving unit 502 and forward it to the AOE.

Optionally, the first sending unit 501 is further configured to, after establishing at least one first long connection with the PS, periodically send CS load information to the PS through any first long connection.

The embodiment of the present invention also provides a PS. As shown in FIG. 6, the PS includes: a second receiving unit 601 and a second sending unit 602; wherein,

The second receiving unit 601 is configured to receive a CS registration request message sent by a connection server CS deployed outside the firewall;

The second sending unit 602 is configured to return a CS registration response message to the CS, and establish a first long connection with the CS;

The second receiving unit 601 is further configured to receive the AOE registration request forwarded by the CS through the first persistent connection of the always-on engine AOE in the first persistent connection, and create a corresponding PS session for the AOE according to the AOE registration request message Session, recording the PS Session ID corresponding to the PS Session;

The second sending unit 602 is further configured to send an AOE registration response message to the CS through the first long connection of the AOE, where the AOE registration response message carries the PS Session ID;

The second receiving unit 601 is further configured to receive the AOE message forwarded by the CS through the first long connection of the AOE, the AOE message carries a CS-PS message header, and the CS-PS message header includes the AOE Logo, PS Session ID and CS Session ID;

The second sending unit 602 is further configured to locate the AOE Session according to the AOE identifier and PS Session ID received by the second receiving unit 601, and complete the processing of the AOE message; and through the first session of the AOE The persistent connection returns a PS message to the CS, and the PS message carries the CS-PS message header.

Optionally, the second receiving unit 601 is further configured to receive CS load information sent by the CS after establishing at least one first long connection with the CS;

The second sending unit 602 is further configured to send the CS load information received by the second receiving unit 601 to the state synchronization device;

The second receiving unit 601 is further configured to receive CS load information of each CS synchronized by the state synchronization device;

The second receiving unit 601 is also configured to receive the pass request message sent by the AOE;

The second sending unit 602 is further configured to select the CS with the lightest load according to the CS load information of each CS received by the second receiving unit 601, and return a passing response message, the passing response message carrying the IP address of the CS with the lightest load.

The embodiment of the present invention also provides an AOE. As shown in FIG. 7, the AOE includes: a third sending unit 701 and a third receiving unit 702, wherein,

The third sending unit 701 is configured to send an AOE registration request message to the connection server CS;

The third receiving unit 702 is configured to receive the AOE registration response message forwarded by the CS;

The third sending unit 701 is further configured to send an AOE message to the CS;

The third receiving unit 702 is further configured to receive the push service server PS message forwarded by the CS.

Optionally, the third sending unit 701 is further configured to send a pass request message to the PS before sending the AOE registration request message to the CS;

The third receiving unit 702 is further configured to receive a passing response message returned by the PS, where the passing response message carries the IP address of the CS with the lightest load;

Correspondingly, the third sending unit 701 is specifically configured to send the AOE registration request message to the CS corresponding to the IP address of the CS with the lightest load received by the third receiving unit 702 .

In practical applications, the first sending unit 501 and the first receiving unit 502 described in this embodiment may be composed of a central processing unit (CPU), a microprocessor (MPU), a digital signal processor (DSP) or Field Programmable Gate Array (FPGA) and other devices to achieve. The second receiving unit 601 and the second sending unit 602 described in this embodiment can be composed of a central processing unit (CPU), a microprocessor (MPU), a digital signal processor (DSP) or a field programmable gate array on the PS. (FPGA) and other devices to achieve. The third sending unit 701 and the third receiving unit 702 described in this embodiment can be composed of a central processing unit (CPU), a microprocessor (MPU), a digital signal processor (DSP) or a field programmable gate on the test instrument Array (FPGA) and other devices to achieve.

Those skilled in the art should understand that the embodiments of the present invention may be provided as methods, systems, or computer program products. Accordingly, the present invention can take the form of a hardware embodiment, a software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention may take the form of a computer program product embodied on one or more computer-usable storage media (including but not limited to disk storage and optical storage, etc.) having computer-usable program code embodied therein.

The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It should be understood that each procedure and/or block in the flowchart and/or block diagram, and a combination of procedures and/or blocks in the flowchart and/or block diagram can be realized by computer program instructions. These computer program instructions may be provided to a general purpose computer, special purpose computer, embedded processor, or processor of other programmable data processing equipment to produce a machine such that the instructions executed by the processor of the computer or other programmable data processing equipment produce a An apparatus for realizing the functions specified in one or more procedures of the flowchart and/or one or more blocks of the block diagram.

These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing apparatus to operate in a specific manner, such that the instructions stored in the computer-readable memory produce an article of manufacture comprising instruction means, the instructions The device realizes the function specified in one or more procedures of the flowchart and/or one or more blocks of the block diagram.

These computer program instructions can also be loaded onto a computer or other programmable data processing device, causing a series of operational steps to be performed on the computer or other programmable device to produce a computer-implemented process, thereby The instructions provide steps for implementing the functions specified in the flow chart or blocks of the flowchart and/or the block or blocks of the block diagrams.

The above descriptions are only preferred embodiments of the present invention, and are not intended to limit the protection scope of the present invention.

Claims (12)

1. A method for implementing an always-on service, which is applied to a Connection Server (CS) deployed outside a firewall, includes:

sending a CS registration request message to a push service server (PS) deployed in a firewall at least once, wherein the CS registration request message comprises an IP address of the CS, and the IP address of the CS is used for enabling the CS registration request message to pass through the firewall to the PS;

correspondingly receiving CS registration response messages returned by the PS at least once, and establishing at least one first long connection with the PS;

receiving an AOE registration request message sent by an always online engine AOE, creating a corresponding CS Session for the AOE according to the AOE registration request message, and recording a CS Session ID corresponding to the CS Session;

selecting one first long connection from the at least one first long connection as the first long connection of the AOE, and forwarding the AOE registration request message to the PS through the first long connection of the AOE;

receiving an AOE registration response message returned by the PS through a first long connection of the AOE, wherein the AOE registration response message carries a PSSession ID of a PS Session created by the PS for the AOE;

the CS saves the PS Session ID, deletes the PS Session ID in the AOE registration response message and forwards the PSSession ID to the AOE;

receiving an AOE message sent by the AOE, adding a CS-PS message header to the AOE message, and forwarding the AOE message to the PS through the first long connection of the AOE, wherein the CS-PS message header comprises an AOE identifier, a PS Session ID and a CS Session ID;

and receiving the PS message returned by the PS through the first long connection of the AOE, deleting the CS-PS message header in the PS message, and forwarding the CS-PS message header to the AOE.

2. The method of claim 1, wherein after establishing at least one first long connection with the PS, the method further comprises:

and sending the CS load information to the PS through any one first long connection timing.

3. A method for implementing an always-on service is applied to a push service server PS deployed outside a firewall, and includes:

receiving a CS registration request message sent by a Connection Server (CS) deployed outside a firewall, returning a CS registration response message to the CS, and establishing a first long connection with the CS;

receiving an AOE registration request forwarded by the CS through a first long connection of an always-on engine AOE in the first long connection, creating a corresponding PS Session for the AOE according to the AOE registration request message, and recording a PS Session ID corresponding to the PS Session;

sending an AOE registration response message to the CS through the first long connection of the AOE, wherein the AOE registration response message carries the PS Session ID;

receiving an AOE message forwarded by the CS through a first long connection of the AOE, wherein the AOE message carries the CS-PS message header, and the CS-PS message header comprises an AOE identifier, a PS Session ID and a CS Session ID;

positioning the Session of the AOE according to the AOE identification and the PS Session ID, and finishing the processing of the AOE message;

and returning a PS message to the CS through the first long connection of the AOE, wherein the PS message carries the CS-PS message header.

4. The method of claim 3, wherein after establishing at least one first long connection with the CS, the method further comprises:

receiving CS load information sent by the CS, and sending the CS load information to state synchronization equipment;

receiving CS load information of each CS synchronized by the state synchronization equipment;

and receiving a passing request message sent by the AOE, selecting the CS with the lightest load according to the CS load information of all the CSs, and returning a passing response message, wherein the passing response message carries the IP address of the CS with the lightest load.

5. A method for implementing an always-on service, the method being applied to an always-on engine AOE on a user terminal, and comprising:

sending an AOE registration request message to a connection server CS;

receiving the AOE registration response message forwarded by the CS;

sending an AOE message to the CS;

and receiving the PS message of the push service server forwarded by the CS.

6. The method of claim 5, wherein before sending the AOE registration request message to the CS, the method further comprises:

sending a pass request message to the PS;

receiving a passing response message returned by the PS, wherein the passing response message carries the IP address of the CS with the lightest load;

correspondingly, the sending the AOE registration request message to the CS includes:

and sending an AOE registration request message to the CS corresponding to the IP address of the CS with the lightest load.

7. A connection server CS, comprising:

a first sending unit, configured to send a CS registration request message to a push service server PS deployed within a firewall at least once, where the CS registration request message includes an IP address of the CS, and the IP address of the CS is used to enable the CS registration request message to pass through the firewall to the PS;

a first receiving unit, configured to correspondingly receive a CS registration response message returned by the PS at least once, and establish at least one first long connection with the PS;

the first receiving unit is further configured to receive an AOE registration request message sent by an always online engine AOE, create a corresponding CS Session for the AOE according to the AOE registration request message, and record a CS Session ID corresponding to the CS Session;

the first sending unit is further configured to select one first long connection from the at least one first long connection as the first long connection of the AOE, and forward the AOE registration request message to the PS through the first long connection of the AOE;

the first receiving unit is further configured to receive, through the first long connection of the AOE, an AOE registration response message returned by the PS, where the AOE registration response message carries a PS Session ID of a PS Session created by the PS for the AOE;

the first sending unit is further configured to store the PS Session ID, delete the PS Session ID in the AOE registration response message, and forward the deleted PS Session ID to the AOE;

the first receiving unit is further configured to receive an AOE message sent by the AOE;

the first sending unit is further configured to forward a CS-PS message header to the PS through the first long connection of the AOE after adding a CS-PS message header to the AOE message received by the first receiving unit, where the CS-PS message header includes an AOE identifier, a PS Session ID, and a CS Session ID;

the first receiving unit is further configured to receive, through the first long connection of the AOE, a PS message returned by the PS;

the first sending unit is further configured to forward the CS-PS message header to the AOE after deleting the CS-PS message header in the PS message received by the first receiving unit.

8. The CS according to claim 7,

the first sending unit is further configured to send CS load information to the PS at any one first long connection timing after at least one first long connection with the PS is established.

9. A push service server PS, comprising:

a second receiving unit, configured to receive a CS registration request message sent by a connection server CS deployed outside a firewall;

a second sending unit, configured to return a CS registration response message to the CS, and establish a first long connection with the CS;

the second receiving unit is further configured to receive an AOE registration request forwarded by the CS through a first long connection of an always-on engine AOE in the first long connection, create a corresponding PS Session for the AOE according to the AOE registration request message, and record a PS Session ID corresponding to the PS Session;

the second sending unit is further configured to send an AOE registration response message to the CS through the first long connection of the AOE, where the AOE registration response message carries the PS Session ID;

the second receiving unit is further configured to receive an AOE message forwarded by the CS through the first long connection of the AOE, where the AOE message carries a CS-PS message header, and the CS-PS message header includes an AOE identifier, a PS Session ID, and a CS Session ID;

the second sending unit is further configured to locate the Session of the AOE according to the AOE identifier and the PSSession ID received by the second receiving unit, and complete processing of the AOE message; and returning a PS message to the CS through the first long connection of the AOE, wherein the PS message carries the CS-PS message header.

10. The PS according to claim 9,

the second receiving unit is further configured to receive CS load information sent by the CS after at least one first long connection with the CS is established;

the second sending unit is further configured to send the CS load information received by the second receiving unit to a state synchronization device;

the second receiving unit is further configured to receive CS load information of each CS synchronized by the state synchronization device;

the second receiving unit is further configured to receive a pass request message sent by the AOE;

the second sending unit is further configured to select a CS with the lightest load according to the CS load information of each CS received by the second receiving unit, and return a passing response message, where the passing response message carries an IP address of the CS with the lightest load.

11. An always-on engine, AOE, comprising:

a third sending unit, configured to send an AOE registration request message to the connection server CS;

a third receiving unit, configured to receive the AOE registration response message forwarded by the CS;

the third sending unit is further configured to send an AOE message to the CS;

the third receiving unit is further configured to receive a PS message of the push service server forwarded by the CS.

12. The AOE of claim 11,

the third sending unit is further configured to send a pass request message to the PS before sending the AOE registration request message to the CS;

the third receiving unit is further configured to receive a passing response message returned by the PS, where the passing response message carries the IP address of the CS with the lightest load;

correspondingly, the third sending unit is specifically configured to send an AOE registration request message to the CS corresponding to the IP address of the CS with the lightest load.