CN102769603A - Method, system and device for data transmission - Google Patents

Abstract

The invention discloses a method, a system and an apparatus for data transmission, adopting a permanent online mechanism; a gateway is arranged between a mobile terminal and an application server; a first long connection is established between the mobile terminal and the gateway and a second long connection is respectively established between the gateway and various application servers, to realize high realtime performance of data exchange between the mobile terminal and the application server via the first long connection and the second long connection with the gateway and to reduce resources of the mobile terminal and the server distributed to long connections. In addition, aiming at the first long connection, a heartbeat packet is sent to the mobile terminal by taking a route distance, which is longer than the distance within which a data packet passes through a firewall of a core network and shorter than the distance between the data packet and a wireless communication network of the mobile terminal, as survival time of the heartbeat packet; on one hand, the heartbeat packet is enabled to pass through the firewall of the core network to keep the first long connection alive; and on the other hand, the heartbeat packet does not go into the wireless communication network to avoid load increment of the wireless communication network and occupation of a wireless channel.

Description

Method, system and device for data transmission

technical field

The present invention relates to the communication field, in particular to a data transmission method, system and equipment.

Background technique

In the current execution process of mobile data services, data interaction between the mobile terminal side and the application server side includes a Pull mode and a Push mode.

The Pull mode means that when an application program installed in a mobile terminal needs to obtain service data from a corresponding application server, the mobile terminal actively establishes a connection with the server, accesses the server for data, and obtains corresponding service data. The Pull method is a way for the mobile terminal to actively obtain data from the server. It is only applicable to the data service interaction process with low real-time requirements. This is because if the server has data that needs to be pushed to the mobile terminal The server connection will cause the problem of untimely data push. If the pull method is applied to the data service interaction process with high real-time requirements, such as the interaction of data services such as email and instant messaging, data delay will occur.

The Push method refers to a method in which the server actively pushes service data to the mobile terminal. Since the Push method can push service data to the mobile terminal in real time, it has a better real-time effect on service data push. There are many ways to implement Push, including: Short Message Push (SMS Push), Multimedia Message Push (MMS Push), Wireless Application Push (WAP Push), Internet Push (IP Push) and Internet Short Message Push Mode (EMN Push).

The specific content of the implementation scheme of the above Push methods is as follows:

SMS Push and MMS Push refer to the Push method in which the server pushes service data to the mobile terminal through a short message or multimedia message, and the user can directly view the service data in the short message or multimedia message through the mobile terminal. In the SMS Push and MMS Push solutions, the short message or multimedia message pushed by the server to the mobile terminal will be affected by the quality of the network. When the network quality is low, there will be a delay in the transmission of the short message and multimedia message, which will affect the service data push. and the business data carried in short messages and multimedia messages is in plain text, and there are hidden dangers in the security of business data; in addition, users can only read business data through mobile terminals, but cannot reply through short messages, etc. Realize information interaction with the server, and only mobile terminals with software and hardware capabilities that support multimedia messages can support MMS Push, which requires high hardware capabilities for mobile terminals and has restrictions on mobile terminals.

WAP Push means: the server pushes information containing links to the mobile terminal, and the mobile terminal accesses and obtains corresponding service data through the Uniform Resource Locator (URL) in the information. In the WAP Push scheme, it includes two operations of the server sending the link to the mobile terminal and the mobile terminal accessing the service data through the link (the operation of the mobile terminal accessing the service data through the link is actually a Pull operation), which has an impact on the real-time nature of service data push. adverse effects.

EMN Push means: when the server needs to push business data to the mail program in the dormant state in the mobile terminal, it sends a proprietary wake-up short message to the mobile terminal, so that the mail program is converted from the dormant state to the active state, and after the mail program is started , establish a long connection with the mail server to obtain business data. In the EMN Push solution, the mobile terminal does not disconnect the long-term connection after obtaining business data from the mail server, but the mail server only disconnects when there is no business data transmission for a period of time. During the waiting time of the mail server, There is no service data transmission between the mobile terminal and the mail server, but the long connection between the mobile terminal and the mail server still exists, resulting in a large system resource overhead of the mobile terminal.

IP Push means: for an application program in the mobile terminal, the application server that provides business data for the application program maintains an IP persistent connection with the mobile terminal. The above-mentioned application program pushes business data, and overcomes the delay problem of SMSPush, MMS Push and WAP Push, as well as the security risks of SMS Push and MMS Push, and the problem of interaction between mobile terminals and servers.

However, in the IP Push solution, if the application program is not running or the application program does not need to exchange data with the application server, the IP persistent connection between the mobile terminal and the application server still exists, which increases the resource overhead of the mobile terminal , leading to large power consumption of mobile terminals; in order to solve the resource overhead caused by IP persistent connections, the IP Push scheme has been changed, requiring IP persistent connections to be connected when the application is running and disconnected when the application is not running. The change will cause the IP persistent connection to be connected and disconnected frequently, which will still increase the system resource overhead of the mobile terminal.

At the same time, as far as the application server is concerned, there are a large number of mobile terminals. If the application server establishes a long connection with a corresponding application program in each mobile terminal, the resource overhead of the application server will also be very large.

The above-mentioned IP Push solution is for an application program installed in the mobile terminal. Most of the current smart mobile terminals have a large number of application programs installed. If the IP Push solution is implemented for all the application programs in the mobile terminal , that is, when multiple applications are installed in a mobile terminal, the mobile terminal needs to establish persistent connections with multiple application servers, and the mobile terminal needs to allocate a large amount of system resources for these persistent connections, resulting in excessive system overhead of the mobile terminal. It even affects the normal operation of other services of the mobile terminal.

In addition, if the persistent connection between the mobile terminal and the application server is to remain connected, the application server needs to periodically send a keep-alive message to the core network firewall through which the persistent connection passes, to notify the firewall that the persistent connection is always valid. This long connection must not be disconnected.

Since the purpose of sending the heartbeat data packet by the application server is to keep the persistent connection alive and maintain the service state of the persistent connection, the data volume of the heartbeat data packet is relatively small, but the sending frequency is relatively high. The heartbeat data packet generally only has tens of bytes, including the mobile terminal identification of the recipient of the heartbeat data packet, the application program identification installed in the mobile terminal interacting with the application server, and the heartbeat serial number. The frequency of sending heartbeat data packets varies according to different services. Taking the instant messaging business as an example, the frequency of heartbeat data packets sent by the application server to the mobile terminal can reach 30 seconds per piece.

During the transmission process of the heartbeat data packet from the application server to the mobile terminal, it needs to go through the internet network, the core network and the wireless communication network, as shown in FIG. 1 . Since the data volume of the heartbeat data packet is relatively small, even when a large number of heartbeat data packets are transmitted in the internet network and the core network, it will not cause obvious impact on the internet network and the core network. However, when the heartbeat data packet is transmitted in the wireless communication network, it is necessary to allocate a channel for the transmission of the heartbeat data packet, and the allocation process of the channel needs to use a large amount of signaling. Therefore, when the heartbeat data packet is transmitted in the wireless communication network, It will occupy a large amount of wireless channel resources (the used signaling occupies the control channel, and the transmission of heartbeat data packets occupies the business channel). If the heartbeat data packets are frequently transmitted in the wireless communication network, it will increase the network burden and reduce the performance of the wireless network; in addition , even if a transmission channel is assigned to the heartbeat data packet, the channel resources cannot be fully utilized due to the small amount of data in the heartbeat data packet, causing the channel to be idle and reducing the use efficiency of the wireless channel.

To sum up, in the current transmission process of the heartbeat data packet, the transmission of the heartbeat data packet in the wireless communication network still has the problems of increasing network burden and low efficiency of wireless channel usage.

Contents of the invention

Embodiments of the present invention provide a method, system and device for data transmission, which are used to solve the problem existing in the prior art in order to ensure the real-time performance of data transmission between the mobile terminal and the application server, resulting in excessive resource occupation of the mobile terminal or application server. The big problem, and the transmission of heartbeat data packets in the wireless communication network will increase the network burden and make the use of wireless channels inefficient.

A method for data transmission, the method comprising:

The gateway receives the uplink data message from the mobile terminal through the first long connection established with the mobile terminal, the uplink data message carries the identification of the application server, and the first long connection transmits the message generated by any application program in the mobile terminal. Uplink data message;

When the gateway determines that a second long connection has been established between application servers corresponding to the identifiers of the application servers, send the uplink data message to the application server through the second long connection;

Wherein, for the first long connection, the set routing distance is used as the survival time of the heartbeat data packet, and the heartbeat data packet is sent to the mobile terminal, and the routing distance is greater than the distance that the heartbeat data packet passes through the core network firewall, but Less than the distance to the wireless communication network where the mobile terminal is located.

A method for data transmission, the method comprising:

The gateway receives the downlink data message from the application server through the second long connection established with the application server, the downlink data message carries the first identifier used when the mobile terminal registers in the application server, and the second long connection transmits The downlink data message sent by the application server to any terminal;

The gateway sends the downlink data message to the mobile terminal through the first long connection between the mobile terminal corresponding to the first identifier;

Wherein, for the first long connection, the set routing distance is used as the survival time of the heartbeat data packet, and the heartbeat data packet is sent to the mobile terminal, and the routing distance is greater than the distance that the heartbeat data packet passes through the core network firewall, but Less than the distance to the wireless communication network where the mobile terminal is located.

A data transmission system, including a mobile terminal, a gateway, an application server and a keep-alive device, wherein:

The mobile terminal is configured to establish a first long connection with the gateway, and send an uplink data message to the gateway through the first long connection, the uplink data message carries an application server identifier, and the first long connection Transmit uplink data messages generated by any application program in the mobile terminal;

The gateway is configured to send the uplink data message to the application server through the second long connection when it is determined that a second long connection has been established between the application servers corresponding to the identifiers of the application servers;

The application server is configured to receive an uplink data message through the second persistent connection;

The keep-alive device is configured to use the set routing distance as the survival time of the heartbeat data packet for the first long connection, and send the heartbeat data packet to the mobile terminal, and the routing distance is greater than the heartbeat data packet passing through the core The distance to the network firewall, but less than the distance to the wireless communication network where the mobile terminal is located.

A data transmission system, the system includes a mobile terminal, a gateway, an application server and a keep-alive device, wherein:

The application server is configured to establish a second long connection with the gateway, and send a downlink data message to the gateway through the second long connection, and the downlink data message carries the first identifier used when the mobile terminal registers in the application server, so The downlink data message sent by the second long connection transmission application server to any terminal;

a gateway, configured to send the downlink data message to the mobile terminal through the first long connection between the mobile terminals corresponding to the first identifier;

a mobile terminal, configured to receive a downlink data message through the first persistent connection;

The keep-alive device is configured to use the set routing distance as the survival time of the heartbeat data packet for the first long connection, and send the heartbeat data packet to the mobile terminal, and the routing distance is greater than the heartbeat data packet passing through the core The distance to the network firewall, but less than the distance to the wireless communication network where the mobile terminal is located.

A gateway, said gateway comprising:

The first connection module is used to establish a first long connection with the mobile terminal, and a second long connection with the application server. The first long connection transmits an uplink data message generated by any application program in the mobile terminal. The downlink data message sent by the second long connection transmission application server to any terminal;

The transmission module is configured to transmit the uplink data message through the second long connection according to the identification of the application server carried in the uplink data message when receiving the uplink data message sent by the mobile terminal through the first long connection during the uplink transmission process sending to the corresponding application server, and during the downlink transmission process, when receiving the downlink data message sent by the application server through the second long connection, according to the first identification of the mobile terminal carried in the downlink data message, the downlink data message It is sent to the corresponding mobile terminal through the first persistent connection.

A mobile terminal, the mobile terminal comprising:

An interface module, configured to establish a first long connection with the gateway, and the first long connection transmits an uplink data message generated by any application program in the mobile terminal;

The data transceiving module is configured to send an uplink data message to the gateway through the first long connection, the uplink data message carries the identification of the application server, and receive the downlink data message pushed by the gateway through the first long connection.

An application server, the application server includes:

An interface module, configured to establish a second long connection with the gateway, and the second long connection transmits a downlink data message sent by the application server to any terminal;

A data transceiving module, configured to receive an uplink data message sent by the gateway through the second long connection, and send a downlink data message to the gateway through the second long connection, the downlink data message carrying the mobile terminal registered in the application server The first identifier used when .

A keep-alive device, characterized in that the keep-alive device comprises:

The distance detection module is used to use the set routing distance as the survival time of the heartbeat packet, and the routing distance is greater than the distance that the heartbeat packet passes through the core network firewall, but less than the distance to the wireless communication network where the mobile terminal is located;

The data packet sending module is configured to send the heartbeat data packet to the mobile terminal according to the time-to-live.

The beneficial effects of the present invention are as follows:

The embodiment of the present invention proposes a new data transmission scheme, adopts an always-online mechanism (AlwaysOnline Infrastructure, AOI), sets a gateway between the mobile terminal and the application server, establishes a long connection between the mobile terminal and the gateway, and the gateway and each application A long connection is established between the servers. During the uplink process, any uplink data message sent by any application program in the mobile terminal is transmitted uplink through a long connection with the gateway. During the downlink process, the application server sends to The downlink data message of any mobile terminal is also downlinked through a long connection with the gateway. Therefore, the high real-time performance of data interaction is realized between the mobile terminal and the application server through the first long connection and the second long connection with the gateway respectively. At the same time, the mobile terminal only needs to allocate resources for a long connection with the gateway, and the application server It also only needs to allocate resources for a long connection with the gateway, which reduces resource occupation between the mobile terminal and the application server. Simultaneously, for the first long connection, the heartbeat data packet is sent to the mobile terminal as the survival time of the heartbeat data packet by being greater than the distance that the heartbeat data packet passes through the core network firewall, but less than the distance to the wireless communication network where the mobile terminal is located, On the one hand, the heartbeat data packet can pass through the core network firewall to achieve the purpose of keeping the first long connection alive; on the other hand, the heartbeat data packet does not enter the wireless communication network, which will not increase the burden on the wireless communication network, nor will it Occupy the wireless channel.

Description of drawings

FIG. 1 is a schematic diagram of heartbeat data packet transmission through the network in the background technology;

FIG. 2 is a schematic diagram of steps of a method for uplink data transmission in Embodiment 1 of the present invention;

FIG. 3 is a schematic diagram of steps in a method for registering a mobile terminal in a gateway and establishing a first persistent connection in Embodiment 1 of the present invention;

FIG. 4 is a schematic diagram of steps in a method for transmitting a heartbeat data packet for a first long connection in Embodiment 1 of the present invention;

FIG. 5 is a schematic diagram of steps in a method for transmitting a heartbeat data packet for a first long connection in Embodiment 1 of the present invention;

FIG. 6 is a schematic diagram of method steps for downlink data transmission in Embodiment 3 of the present invention;

FIG. 7 is a schematic diagram of the system structure of data transmission in Embodiment 4 of the present invention;

FIG. 8 is a schematic structural diagram of a gateway in Embodiment 6 of the present invention;

FIG. 9 is a schematic structural diagram of a mobile terminal in Embodiment 7 of the present invention;

FIG. 10 is a schematic structural diagram of an application server in Embodiment 8 of the present invention;

FIG. 11 is a schematic structural diagram of a keep-alive device according to Embodiment 9 of the present invention;

Fig. 12 is a schematic structural diagram of a keep-alive device according to Embodiment 9 of the present invention;

FIG. 13 is a schematic structural diagram of a system including subsystems in a gateway according to an embodiment of the present invention.

Detailed ways

In order to reduce the resources occupied by the mobile terminal when establishing long-term connections between various application programs installed locally and a large number of application servers, and obtain high real-time data transmission between the mobile terminal and the application server in the IP Push scheme, the embodiment of the present invention A new data transmission scheme is proposed, using the always online mechanism (Always Online Infrastructure, AOI), a gateway is set between the mobile terminal and the application server, a long connection is established between the mobile terminal and the gateway, and between the gateway and each application server Establish a long connection respectively. During the uplink process, the uplink data message sent by any application program in the mobile terminal is transmitted uplink through a long connection with the gateway. During the downlink process, the application server sends it to any mobile terminal. The downlink data message of the terminal is also downlinked through a long connection with the gateway. For the mobile terminal side, regardless of the number of applications installed in the mobile terminal, the mobile terminal only needs to allocate resources for a long connection with the gateway to achieve high real-time data reception; for the application server side , regardless of the number of mobile terminals served by the application server, the application server only needs to allocate resources for a long connection with the gateway to push data to the mobile terminals in real time. That is to say, through the solutions of the embodiments of the present invention, during the data transmission process, resource occupation between the mobile terminal and the application server is reduced, and high real-time data transmission between the mobile terminal and the application server is ensured.

At the same time, before transmitting the heartbeat data packet for the first long connection, by monitoring the transmission process of the test data packet, determine the survival time that can make the data packet pass through the firewall of the core network but not enter the wireless communication network where the mobile terminal is located. When the heartbeat data packet is transmitted for the first time, it is transmitted according to the lifetime. On the one hand, the heartbeat data packet can pass through the core network firewall to achieve the purpose of keeping alive the first longest connection between the mobile terminal and the gateway. On the other hand, the heartbeat data packet The packets do not enter the wireless communication network, so the burden on the wireless communication network will not be increased, and the wireless channel will not be occupied.

The gateway involved in each embodiment of the present invention refers to an always-on gateway (AlwaysOnline Gateway, AOG) under the AOI mechanism. AOG can provide a unified access point for mobile Internet-based persistent connection applications. On the other hand, it serves as a channel for data transmission and synchronization between the application server and the mobile terminal side.

The mobile terminal involved in each embodiment of the present invention refers to the mobile terminal under the AOI mechanism, that is, it has functions such as orderly management of various application programs installed in the mobile terminal and long-term connection management with the gateway. The mobile terminal under the AOI mechanism may be a mobile terminal installed and running the AOI middleware with the above functions.

The application server involved in each embodiment of the present invention refers to a network server that performs service data interaction with the application program installed in the mobile terminal. For example, if an instant messaging application is installed in the mobile terminal, in order to ensure the normal operation of the instant messaging service, the instant messaging application needs to perform effective service data interaction with the instant messaging server.

The long connection established in each embodiment of the present invention refers to a connection that can continuously send multiple data packets on one connection. During the connection maintenance period, if no data packets are sent, both parties need to send link keep-alive packets. Socket (Socket) long connection, etc.

The first long connection between the terminal and the gateway can perform uplink transmission for uplink data messages generated by any application program in the mobile terminal, and receive downlink data messages sent to any application program in the terminal.

The second long connection between the application server and the gateway may be that the application server receives the uplink data message sent by any terminal, and transmits the uplink data message sent by the application server to any terminal.

The heartbeat data packet involved in each embodiment of the present invention refers to a data packet for keeping alive a certain long connection specified by the heartbeat data packet.

The core network firewall involved in each embodiment of the present invention refers to: the firewall at the Internet network boundary, the first long connection between the mobile terminal and the gateway will pass through the firewall, and the firewall will monitor whether the long connection needs to be released. If the firewall does not receive the heartbeat data packet for the long connection within the period, it means that the long connection has no data to transmit and release; if it receives the heartbeat data packet for the long connection, it will continue to maintain the long connection.

The routing distance involved in each embodiment of the present invention refers to: the routing hop count of the data packet.

The survival time of the heartbeat data packet in each embodiment of the present invention refers to the routing hop count of the heartbeat data packet during transmission.

Various embodiments of the present invention will be described in detail below in conjunction with the accompanying drawings.

Embodiment one:

As shown in Figure 2, it is a schematic diagram of the method steps for performing uplink (Mobile Original, MO) data transmission in Embodiment 1 of the present invention, comprising the following steps:

Step 101: the mobile terminal sends an uplink data message to the gateway through the first long connection established with the gateway.

The identification of the application server is carried in the uplink data message, indicating that the destination recipient of the uplink data message is the application server corresponding to the application server identification. For example, after the mail application program installed in the mobile terminal generates an uplink data message sent to the mail server, the mobile terminal carries the identification of the mail server in the uplink data message, and sends the The uplink data message is sent to the gateway. It should be noted that no matter which application program installed in the mobile terminal generates an uplink data message, the mobile terminal will send it to the gateway through the first persistent connection.

A group of keys can be jointly maintained between the mobile terminal and the gateway. When the mobile terminal sends an uplink data message to the gateway, the key can be used to encrypt the uplink data message. At the same time, the mobile terminal can also use the secure transport layer protocol (Transport Layer Sec, TLS) encrypts the transmission process of uplink data messages.

Step 102: The gateway determines the corresponding application server according to the received identifier of the application server.

The gateway can decrypt the received uplink data message according to the key maintained together with the mobile terminal.

Step 103: When the gateway determines that a second long connection has been established with the application server, the gateway sends an uplink data message to the application server through the second long connection.

Since the gateway may have established a second long connection with multiple application servers, when the gateway sends an uplink data message to a certain application server, it first checks whether there is a second long connection available with the application server. When there is an available second long connection, an uplink data message is sent to the application server through the second long connection.

When the gateway sends the uplink data message to the application server, it can also encrypt the uplink data message, and the application server decrypts the received uplink data message.

In addition, since the transmission resources occupied by the uplink data message can be reduced by compressing the data content in the uplink data message, the amount of data transmitted on the wireless network can be reduced, the network bandwidth can be saved, and the network delay can be reduced. Therefore, the uplink data message When transmitting through the first long connection, and when transmitting through the second long connection, according to the different resources of the data content (audio data, video data, text data, etc.), a reasonable compression algorithm can be used to compress and transmit, Devices (such as gateways and application servers) that receive the compressed uplink data messages can perform decompression operations.

In addition, due to the large number of mobile terminals targeted by the gateway, when multiple mobile terminals send uplink data messages to the gateway at the same time, or the same mobile terminal sends multiple uplink data messages for different applications, if the gateway is not capable of processing all uplink data messages, these uplink data messages need to be sorted and processed sequentially. In the solution of this embodiment, the ways for the gateway to sort include but are not limited to the following two:

The first sorting method: the gateway sorts according to the priority of the business. Since each uplink data message carries the identifier of the application server, the service corresponding to the uplink data message can be determined. Therefore, the gateway can sort the uplink data messages according to the service priority, and process the uplink data messages with high service priority first. For example, services with high real-time requirements have higher priorities, and services with low real-time requirements have lower priorities.

The second sorting method: the gateway sorts the mobile terminals according to their priority. The gateway can set the priority of the mobile terminal according to the current wireless network environment of the mobile terminal. A mobile terminal in a better wireless network environment corresponds to a higher priority. For a mobile terminal in a poor wireless network environment, in order to avoid sending an uplink data message to make the wireless network environment worse, the corresponding priority may be lower.

Through the technical solutions described in steps 101 to 103 above, the gateway becomes the intermediary of the real-time transmission process between the mobile terminal and the application server, so that the mobile terminal does not need to face a large number of application servers on the network side, but only needs to face a gateway for uplink transmission , and at the same time, the application server does not need to face a large number of mobile terminals, but only needs to face a gateway to receive uplink data messages, which can effectively reduce the resource overhead allocated by the mobile terminal and the application server for long connections. At the same time, according to the mobile terminal and the gateway The network architecture of the first long connection between the gateway and the second long connection between the gateway and the application server can realize real-time business data transmission between the mobile terminal and the application server, and effectively improve the real-time performance of data transmission.

The specific implementation manner of the above steps 101 to 103 will be described in detail below.

Before the uplink transmission process of the first embodiment is performed, the mobile terminal needs to manage the locally installed application programs, therefore, before step 101, there is also an internal management process of the mobile terminal, which specifically includes:

Firstly, the mobile terminal records the identifiers of the locally installed application programs, and collects the state information of each application program in real time, including the information that the application programs are in the running state, dormant state or exit state.

Then, the mobile terminal also records the identification of the application server corresponding to each application program, which is used to determine the destination receiver of the uplink data message during the uplink transmission process.

Finally, after the mobile terminal completes the information recording of the locally installed applications, it will monitor in real time whether any application needs to perform uplink data interaction. After any application generates an uplink data message, the mobile terminal will send the application The identification of the application server corresponding to the program is carried in the generated uplink data message, and then step 101 is executed.

Through the above-mentioned management of locally installed application programs by the mobile terminal, the operation of local application programs can be effectively managed, and the problems of application program operation confusion and even process conflicts can be avoided.

Specifically, in the local mobile terminal, there is an AOI middleware in the mobile terminal, which is used for orderly management of various applications and long-term connection management with the gateway. Directly connect to the AOI middleware through the Socket long connection, provide the uplink data message to be transmitted to the AOI middleware, and require the AOI middleware to transmit in real time through the first long connection.

After the mobile terminal completes the management of the local application program, it can register in the gateway and connect to the first persistent connection before step 101 . The specific process of the mobile terminal registering in the gateway and establishing the first long connection is shown in Figure 3, including the following steps:

Step 201: The mobile terminal initiates a gateway query request to Domain Name System (DNS), which carries the first identification and the second identification of the mobile terminal.

Both the first identifier and the second identifier of the mobile terminal are identifiers that can uniquely represent the mobile terminal, the difference is that the first identifier of the mobile terminal is the identifier used when the mobile terminal registers in the application server, and the second identifier is the The ID registered with the gateway.

For example, if the mobile terminal is a mobile phone, the first identifier is a mobile phone number, and the second identifier is an International Mobile Subscriber Identity (IMSI). At this time, when the mobile terminal initiates a gateway query request to the DNS in the form of a short message, the short message carries the IMSI, and the DNS can obtain the second identification (IMSI) of the mobile terminal from the information carried in the short message, and pass the short message The source information determines the first identifier (mobile phone number) of the mobile terminal.

Step 202: DNS stores the first identifier and the second identifier of the mobile terminal.

Step 203: the DNS returns the routing information of the home gateway of the mobile terminal to the mobile terminal.

In the solution of this embodiment, multiple gateways can be deployed in one network system, and each gateway provides services for mobile terminals in a certain area. For example, deploy a gateway in each province of the country to provide field connection services for mobile terminals in the province. The routing information of each gateway and the coverage of each gateway service can be manually stored in the DNS. When the DNS receives a gateway query request initiated by a mobile terminal, according to the identification of the mobile terminal (the first identification and the second identification) The attribution of the mobile terminal is determined, and then the coverage of each gateway service is inquired, and the attribution gateway is selected for the mobile terminal.

The routing information of the home gateway returned by the DNS to the mobile terminal includes but not limited to the IP address of the gateway.

Step 204: The mobile terminal initiates a registration request to the home gateway according to the received routing information of the home gateway, and carries the second identifier in the registration request.

The registration request may also carry the identification of the application program installed in the mobile terminal.

Step 205: the gateway registers the mobile terminal.

The gateway locally stores the registration information of the mobile terminal (including the registration time of the mobile terminal, the second identification, etc.) and the identification of the application program managed by the mobile terminal, completes the registration of the mobile terminal, and returns a registration success message to the mobile terminal.

In this step, after the mobile terminal is registered in the gateway, the gateway needs to manage the registered mobile terminal, including the following two aspects of management:

The first aspect: the management of mobile terminal information, such as the management of hardware information such as the second identification, version number, operating system, manufacturer, model, and screen size of the mobile terminal.

The second aspect: the management of mobile terminal services, such as the management of information such as service types and service names supported by the mobile terminal.

Step 206: the mobile terminal establishes a first long connection with the gateway.

Thereafter, when any application in the mobile terminal initiates an uplink data message, the mobile terminal sends the uplink data message to the home gateway through the first persistent connection.

After the gateway receives the uplink data message from the mobile terminal, it will execute step 103 to send the uplink data message to the application server. However, since the application server provides services for a large number of mobile terminals in parallel, the mobile terminal carries the second identifier in the uplink data message, and it is hoped that the application server can know the mobile terminal sending the uplink data message. However, the mobile terminal uses the first identifier when registering in the application server, and uses the second identifier when registering in the gateway. Therefore, if the gateway directly carries the second identifier in the uplink data message and sends it to the application server, then The application server may not be able to identify it. In order to overcome this problem, when step 103 of this implementation is running, the gateway queries the first identifier of the mobile terminal from DNS according to the second identifier of the mobile terminal, and sends the second identifier of the mobile terminal to An identifier is carried in the uplink data message and sent to the application server, so that the application server can obtain the sending mobile terminal of the uplink data message according to the first identifier of the uplink data message.

Considering that multiple gateways are deployed in the network system, the uplink data message sent by the mobile terminal to its home gateway can be transmitted according to the first long connection between the mobile terminal and the home gateway, but the application of the destination end of the uplink data message transmission The server does not necessarily establish a second long connection with the gateway to which the mobile terminal belongs. Therefore, when the second long connection needs to be established between the gateway and each application server, the gateway and the information of the second long connection respectively established with the gateway are stored in the DNS. The first corresponding relationship of the application server is used to query the gateway to which the application server belongs.

In step 103 of this embodiment, the gateway sends an uplink transmission message to the application server in the following two situations:

The first case: the gateway determines that the application server corresponding to the application server identifier in the uplink data message has established a second long connection by querying the long connection port, that is, the source end (mobile terminal) and the destination end of the uplink data message (Application servers) all establish persistent connections with the same gateway, and the uplink data message can be directly transmitted.

The second case: the gateway determines that there is no application server corresponding to the identification of the application server in the uplink data message to establish the second long connection, that is, the gateway is not the gateway to which the application server belongs, then the gateway queries DNS to find the application server Other gateways belonged to (in order to distinguish from gateways receiving uplink data messages sent by mobile terminals, the gateways to which the application server belongs are referred to as other gateways here), and after sending the uplink data messages to the other gateways, due to The other gateway is the home gateway of the destination application server and has a second long connection with the application server. Therefore, the other gateway sends the uplink data message to the application server through the second long connection.

In addition, after step 103 is executed, the gateway can also record the log information of this uplink data transmission process, and generate a bill. The bills generated here are different from the conventional bills, because: in the uplink transmission process of the mobile terminal, the scheme of Embodiment 1 of the present invention can be used, and other existing schemes can also be used. The change of generation mode, in the scheme of this embodiment one, the bill that adopts the flow of CP, SP of this embodiment one scheme is settled by the bill generated by the gateway, and it is used in conjunction with the conventional bill, and it is determined that in each uplink transmission process Costs incurred.

In the solution of the first embodiment, in order to keep the first long connection between the mobile terminal and the gateway alive in real time (that is, heartbeat data packets for the first long connection continue to pass through the core network firewall within a period of time) ), while not increasing the resource overhead of the wireless communication network, so the lifetime of the heartbeat data packet is set to be greater than the distance passing through the core network firewall, but less than the distance to the wireless communication network where the mobile terminal is located. On the one hand, the heartbeat data packet It can pass through the firewall of the core network to achieve the purpose of keeping alive the first longest connection between the mobile terminal and the gateway. On the other hand, the heartbeat data packet does not enter the wireless communication network, which will not increase the burden on the wireless communication network, nor will it Occupy the wireless channel.

In the first embodiment, a schematic diagram of the steps of the method for transmitting the heartbeat data packet for the first long connection is shown in FIG. 4, and the method includes the following steps:

Step 301: For the first long connection, detect relevant information of the mobile terminal at one end of the first long connection.

In this step, it is first determined for which long connection to transmit the heartbeat data packet, and then the mobile terminal receiving the heartbeat data packet is determined. Specifically, it is possible to establish a Transmission Control Protocol (Transmission Control Protocol, TCP) data connection with the terminal through the service server in the mobile Internet, and obtain relevant information about the mobile terminal, such as the quintuple information when the mobile terminal connects to the network, including the source IP address, source port, destination IP address, destination port, and transport layer protocol number. Wherein, the source port is the port number of the mobile terminal, and the relevant information of the mobile terminal can also be obtained by means of User Datagram Protocol (UDP).

Step 302: Determine the routing distance of the heartbeat data packet after passing through the core network firewall and arriving at the one-hop route before the wireless communication network where the mobile terminal is located.

Step 303: According to the periodic requirement of the core network firewall, send the heartbeat data packet with the determined routing distance group as the time-to-live.

In the scheme of above-mentioned steps 301～step 303, calculate reasonable routing distance, i.e. the routing hop count of the heartbeat data packet, use this routing hop count as the TTL field storage time of the IP data packet in the heartbeat data packet, make The heartbeat data packet can not only pass through the core network firewall to enter the core network provided by the operator to keep the first long connection alive, but also terminate at the one-hop router before entering the wireless communication network where the mobile terminal is located. The burden caused by the heartbeat data packet on the wireless communication network is avoided.

The specific implementation process of the above steps 301 to 303 is shown in Figure 5, including the following steps:

Step 401: Send a test data packet to the mobile terminal, and determine a first routing distance generated when the test data packet is routed to the mobile terminal.

The purpose of the present invention is to allow the heartbeat data packet to pass through the core network firewall and will not enter the wireless communication network. Therefore, it is first necessary to determine the first routing distance when the heartbeat data packet enters the wireless communication network and arrives at the mobile terminal. The first routing distance determines an appropriate second routing distance to achieve the purpose of the present invention.

Step 402: According to the first routing distance, determine the second routing distance generated when the test data packet passes through the core network firewall and arrives at the one-hop routing before the wireless communication network where the mobile terminal is located.

Because the first routing distance is the routing distance that can reach the mobile terminal, and the second routing distance does not reach the mobile terminal, so the second routing distance is smaller than the first routing distance, but the second routing distance must be greater than the distance through the firewall, therefore, the second routing distance The maximum upper limit of the second route distance is the route hop count minus 1 of the first route distance, and the lower limit is the route hop count generated when passing through the core network firewall. Preferably, the routing hop count of the first routing distance may be reduced by 1 as the second routing distance.

Step 403: Using the second routing distance as the lifetime of the heartbeat data packet, send the heartbeat data packet to the mobile terminal.

The scheme of the second embodiment includes but is not limited to gradually increasing the routing distance to determine the first routing distance, gradually reducing the routing distance to determine the first routing distance and dichotomous method to determine the first routing distance, which will be explained respectively below:

1. Determine the first routing distance by gradually increasing the routing distance:

This mode further includes TCP mode and UDP mode, and the specific description is as follows:

(1), TCP mode:

Step 1: Set the TCP header sequence number value of the test data packet to a value recognized as an error by the mobile terminal.

The TCP protocol stipulates that the data packet needs to carry the serial number value allocated for the data packet. After receiving the data packet, the receiver of the data packet can determine the relevant information of the data packet (such as the source of the data packet) according to the serial number value carried in it. , the purpose of sending the data packet).

In this step, the test data packet sent to the mobile terminal carries a wrong sequence number instead of the sequence number actually assigned to the data packet. If the test data packet arrives at the mobile terminal, then the mobile terminal will recognize the serial number carried in the test data packet as a wrong serial number, and then think that the test data packet is an illegal data packet, then the mobile terminal will return a reset (RST) A TCP message to notify the sender of the test data packet that the test data packet is wrong. If the time-to-live is reached when the test data packet does not arrive at the mobile terminal, the mobile terminal will return a Control Message Protocol (Internet Control Message Protocol, ICMP) message because the mobile terminal has not received the test data packet within the specified time length, and the The error type is timeout. The sender of the test data packet determines whether the test data packet reaches the mobile terminal according to whether the returned RST message or the ICMP message whose error type is timed out.

Step 2: Preset the distance of the third route.

The third routing distance in this step may be initially set to 1 hop.

Step 3: Gradually increase the preset third routing distance, and perform the following operations for the routing distance obtained after each increase:

Using the routing distance obtained this time as the survival time of the test data packet, sending the test data packet to the mobile terminal;

If the TCP message of RST is returned, the routing distance obtained this time is used as the first routing distance;

If the error type carried in the returned ICMP message is timeout, continue to increase the routing distance.

In the solution of the third step, if the routing hops of the third routing distance used this time are too small to allow the test data packet to reach the mobile terminal, the mobile terminal will stop at the mobile terminal due to not receiving the test data packet within the specified time. The error type carried in the returned ICMP message is timeout, which means that the third routing distance is less than the routing distance required for routing to the mobile terminal at this time. Therefore, the third routing distance needs to be increased, and the increased third routing distance Continue to send test packets as the time-to-live of the test packets. When the error type carried by ICMP is timeout in the case of the third route distance used last time, but the RST message is received in the case of the third route distance used this time, it means that the third route distance currently used can just make the test The data packet is routed to the mobile terminal, but the mobile terminal returns an RST message because the sequence number of the test data packet identified by the mobile terminal is incorrect. At this time, the third routing distance currently used is equal to the required routing distance when the test data packet is routed to the mobile terminal , the current third routing distance is used as the first routing distance.

(2), UDP mode:

Step 1: Set the destination port number carried in the test data packet as the UDP port number of the user data packet that the mobile terminal cannot correctly receive the test data packet.

In this embodiment, the 4-byte destination port number in the UDP header of the test packet can be designed as a random high-segment port number, such as using any random high-segment port greater than 32768, so that the mobile terminal cannot correctly receive the test data packet. , but as long as the survival time of the test data packet can make the test data packet reach the destination port, the route distance experienced is the same as the route distance to the mobile terminal. Therefore, it is also possible to replace the port of the mobile terminal with a port that cannot receive the test data packet Calculate the first routing distance generated when routing to the mobile terminal.

Step 2: Preset the fourth routing distance.

The third routing distance in this step may be initially set to 1 hop.

Step 3: Gradually increase the fourth routing distance, and perform the following operations cyclically for the routing distance obtained after each increase:

Using the routing distance obtained this time as the survival time of the test packet, sending the test packet to the mobile terminal, and detecting the returned ICMP message;

If the error type carried in the returned ICMP message is that the port is unreachable, the routing distance obtained this time is used as the first routing distance;

If the error type carried in the returned ICMP message is timeout, then continue to increase the routing distance until the error type carried in the returned ICMP message is received as port unreachable.

In the solution of the third step, if the routing hops of the third routing distance used this time are too small to make the test data packet reach the port corresponding to the destination port number, the ICMP message returned by the router where the test data packet finally reaches The error type carried in is timeout, which means that the fourth routing distance is less than the routing distance required for routing to the mobile terminal at this time. Therefore, the fourth routing distance needs to be increased, and the increased fourth routing distance will continue to be used as a test Packet lifetime to send test packets. When the error type carried by ICMP is timeout in the case of the fourth route distance used last time, but the error type carried by ICMP in the case of the fourth route distance used this time is port unreachable, indicating that the fourth route currently used The distance is just enough to route the test data packet to the destination port, but because the destination port cannot correctly receive the test data packet, it returns the error type that the port is unreachable. At this time, the fourth routing distance currently used is equal to the test data packet routed to the mobile For the required routing distance at the terminal, the current fourth routing distance is used as the first routing distance.

2. Determine the first routing distance by gradually reducing the routing distance:

This mode further includes TCP mode and UDP mode, and the specific description is as follows:

(1), TCP mode:

Step 1: Through the TCP connection that has determined the quintuple information, that is, the long connection to be kept alive by sending the heartbeat data packet.

Step 2: Preset the fifth routing distance.

The fifth routing distance in this step can be initially set larger to ensure that the test data packet sent for the first time can be correctly received by the mobile terminal, such as setting the fifth routing distance to 64 hops initially.

Step 3: use the routing distance obtained this time as the survival time of the test packet, send the test packet to the mobile terminal through the TCP connection that has determined the quintuple information, and judge whether to receive the test response message returned;

If so, continue to reduce the routing distance;

Otherwise, add 1 to the routing distance obtained this time as the first routing distance.

This method is to send test data packets to the mobile terminal through a TCP connection. In the third step of the scheme, the survival time in the test data packets is continuously decreasing. If the distance of the fifth route used this time is relatively large, it can make the mobile terminal If the terminal correctly receives the test data packet, the mobile terminal will return a test response message, indicating that the distance of the fifth route needs to be further reduced. When the fifth routing distance used last time can make the test data packet reach the mobile terminal (that is, the test response message is received after sending the test data packet last time), but the fifth routing distance used this time cannot make the test data packet reach the mobile terminal The terminal (which did not receive a test response message after sending the test data packet this time), indicates that the fifth routing distance used this time can only reach the last hop outside the wireless communication network, and the fifth routing distance used last time is the route to The routing distance generated when the terminal is moved, therefore, the fifth routing distance used last time is used as the first routing distance. If the routing distance is reduced by 1 hop each time, the fifth routing distance used this time plus 1 hop may be used as the first routing distance.

(2), UDP mode:

Step 1: Determine the mobile terminal receiving the test data packet according to the IP address and UDP port of the mobile terminal.

In this mode, a mobile terminal is uniquely determined through the IP address and UDP port number of the mobile terminal, and the mobile terminal determined here is the mobile terminal that needs to receive the test data packet.

If the test data packet arrives at the mobile terminal, the mobile terminal can correctly receive the test data packet and return a test response message; if the test data packet does not arrive at the mobile terminal, that is, it becomes 1 or 0 before the TTL of the test data packet before arriving at the mobile terminal, the mobile terminal If the terminal does not receive the test data packet within the specified time period, no test response message is returned, that is, the test data packet sent to the mobile terminal times out.

Step 2: Preset the sixth routing distance.

The sixth routing distance in this step can be set relatively large initially to ensure that the test data packet sent for the first time can be correctly received by the mobile terminal, such as setting the sixth routing distance to 64 hops initially.

Step 3: Gradually reduce the preset sixth routing distance, and perform the following operations for the routing distance obtained after each reduction:

Using the routing distance obtained this time as the survival time of the test packet, send the test packet to the mobile terminal determined in the first step, and judge whether to receive the test response message returned by the mobile terminal;

If so, continue to reduce the routing distance;

Otherwise, add 1 to the routing distance obtained this time as the first routing distance.

3. Dichotomy method:

The dichotomy method also includes the TCP method and the UDP method, and the details are as follows:

(1), TCP mode:

Step 1: Through the TCP connection that has determined the quintuple information, that is, the long connection to be kept alive by sending the heartbeat data packet.

Step 2: Predefine an upper limit routing distance and a lower limit routing distance. Initially, the upper limit routing distance is greater than the lower limit routing distance.

Step 3: When the upper limit routing distance or the lower limit routing distance is updated, determine whether the upper limit routing distance is not less than the lower limit routing distance. If so, perform the following operations until the upper limit routing distance is smaller than the lower limit routing distance:

The average value of the upper limit routing distance and the lower limit routing distance obtained this time is rounded to obtain the seventh routing distance, and the seventh routing distance obtained this time is used as the survival time of the test data packet, and the TCP connection determined in the first step is sent to The mobile terminal sends the test data packet, and judges whether a returned test response message is received;

If so, then subtract 1 from the routing hop count of the seventh routing distance obtained this time as the updated upper routing distance;

Otherwise, subtract 1 from the routing hop count of the seventh routing distance obtained this time as the updated lower limit routing distance.

For example, when sending a test packet for the Nth time, TTL_max=64, TTL_min=0, TTL_max is greater than TTL_min, the number of routing hops of the seventh routing distance is [(TTL_max+TTL_min)/2]=32, and 32 hops are used as the survival Time to send test packet N.

For the test data packet N, if the test response message is returned, indicating that the mobile terminal can correctly receive the test data packet at 32 hops, the current seventh routing distance 32-1=31 is used as the updated TTL_max, that is, TTL_max=31, TTL_min =0. At this time, TTL_max is still greater than TTL_min, and the number of routing hops that can be recalculated to obtain the seventh routing distance is [(TTL_max+TTL_min)/2]=15, and the test packet N+1 is sent with 15 hops as the survival time, and so on .

For the test data packet N, if no test response message is returned, it means that the mobile terminal cannot correctly receive the test data packet at 32 hops, then the current seventh routing distance 32-1=31 is used as the updated TTL_min, that is, TTL_max= 64, TTL_min=31. At this time, TTL_max is still greater than TTL_min, and the number of routing hops that can be recalculated to obtain the seventh routing distance is [(TTL_max+TTL_min)/2]=47, and the test packet N+1 is sent with 47 hops as the survival time, and so on .

Step 4: Determine the seventh routing distance obtained when the upper routing distance is smaller than the lower routing distance.

Step 5: When the seventh routing distance obtained in the fourth step is used as the survival time of the test packet, if a test timeout message is received, add 1 to the routing hop count of the seventh routing distance as the first routing distance ; If the test is correct message is received, the routing hop count of the seventh routing distance is used as the first routing distance.

(2), UDP mode:

Step 1: Determine the mobile terminal receiving the test data packet according to the IP address and UDP port of the mobile terminal.

Step 2: Predefine an upper limit routing distance and a lower limit routing distance. Initially, the upper limit routing distance is greater than the lower limit routing distance.

Step 3: When the upper limit routing distance or the lower limit routing distance is updated, determine whether the upper limit routing distance is not less than the lower limit routing distance. If so, perform the following operations until the upper limit routing distance is smaller than the lower limit routing distance:

Round the average value of the upper limit routing distance and the lower limit routing distance obtained this time to obtain the eighth routing distance, and use the eighth routing distance obtained this time as the survival time of the test data packet, and send it to the mobile terminal determined in the first step The test packet, and determine whether a returned test response message is received;

If so, then subtract 1 from the route hop count of the eighth route distance obtained this time as the updated upper limit route distance;

Otherwise, subtract 1 from the routing hop count of the eighth routing distance obtained this time as the updated lower limit routing distance.

For example, when sending a test packet for the Nth time, TTL_max=64, TTL_min=0, TTL_max is greater than TTL_min, the number of routing hops of the eighth routing distance is [(TTL_max+TTL_min)/2]=32, and 32 hops are used as the survival Time to send test packet N.

For the test data packet N, if the test response message is returned, indicating that the mobile terminal can correctly receive the test data packet at 32 hops, the current eighth routing distance 32-1=31 is used as the updated TTL_max, that is, TTL_max=31, TTL_min =0. At this time, TTL_max is still greater than TTL_min, and the number of route hops that can be recalculated to obtain the eighth route distance is [(TTL_max+TTL_min)/2]=15, and the test packet N+1 is sent with 15 hops as the survival time, and so on .

For the test data packet N, if no test response message is returned, it means that the mobile terminal cannot correctly receive the test data packet at 32 hops, then the current eighth routing distance 32-1=31 is used as the updated TTL_min, that is, TTL_max= 64, TTL_min=31. At this time, TTL_max is still greater than TTL_min, and the number of routing hops that can be recalculated to obtain the eighth routing distance is [(TTL_max+TTL_min)/2]=47, and the test packet N+1 is sent with 47 hops as the survival time, and so on .

Step 4: Determine the eighth routing distance obtained when the upper routing distance is smaller than the lower routing distance.

Step 5: When the eighth routing distance obtained in the fourth step is used as the survival time of the test packet, if a test timeout message is received, add 1 to the routing hop count of the eighth routing distance as the first routing distance ; If the test is correct message is received, the routing hop count of the eighth routing distance is used as the first routing distance.

It should be noted that, in the above-mentioned various methods, due to reasons such as the network transmission quality of the test data packet during transmission, the test data packet may be lost, so that the mobile terminal cannot receive the test data packet correctly. Therefore, when this When it is determined that the mobile terminal has not received the test data packet after sending the test data packet for the first time, the retransmission operation can be performed with the same routing distance this time. When the number of retransmissions reaches the threshold value, the mobile terminal has not received the test data packet, then The first routing distance is determined by using the routing distance used this time.

In addition, in order to ensure that the first routing distance is exactly the routing distance generated when routing to the mobile terminal, in any of the above methods, the routing distance is increased or decreased by 1 hop each time.

Embodiment two:

The solution of Embodiment 1 of the present invention can transmit control signaling and data between the mobile terminal and the application server through the first long connection and the second long connection with the gateway. In particular, if the amount of data to be transmitted is very large Large (such as a large number of attachments carried in the mail), when a large amount of data and control signaling and a small amount of data are transmitted through a long connection at the same time, it may affect the correct transmission of the control signaling. On the basis of Embodiment 1, a temporary long connection is established for data with a large amount of data to transparently transmit data.

The scheme of present embodiment two is as follows:

Step 1: A first long connection is established between the mobile terminal and the home gateway, and a second long connection is established between the application server and the home gateway.

Step 2: The mobile terminal transmits the uplink data message uplink through the first long connection, and the gateway sends the uplink data message to the application server through the second long connection.

In the solution of the second embodiment, the manner in which the mobile terminal uplinks the uplink data message to the application server is the same as that in the first embodiment.

Step 3: The mobile terminal sends a proxy request to the gateway, and the proxy request carries the identification of the application server and the amount of data to be transmitted.

In the solution of this embodiment, the gateway has the ability to support a proxy (Proxy) request from a mobile terminal.

Step 4: The gateway judges whether the amount of data reaches a threshold, and if so, executes Step 5; otherwise, requires the mobile terminal to transmit the data to be transmitted through the first long connection.

Step 5: The gateway judges whether the second long connection has been established with the corresponding application server according to the application server identification carried in the proxy request:

If so, the gateway respectively establishes a temporary long connection with the mobile terminal and the corresponding application server, receives the data to be transmitted from the mobile terminal through the temporary long connection with the mobile terminal, and releases the data to be transmitted with the mobile terminal after the transmission is completed. A temporary long connection between terminals, and transparently transmitting the data to be transmitted to the application server through the temporary long connection with the application server, and releasing the temporary long connection with the application server after the transmission is completed.

Otherwise, the gateway queries DNS for other gateways that have established a second long connection with the corresponding application server, and establishes temporary long connections with the mobile terminal and the other gateways respectively, and through the temporary long connection with the mobile terminal receiving the data to be transmitted from the mobile terminal, releasing the temporary long connection with the mobile terminal after the transmission, and transparently transmitting the data to be transmitted through the temporary long connection with the other gateways to other gateways, and release the temporary long connection with the other gateways after the transmission ends.

Through the solution of the second embodiment of the present invention, the mobile terminal, the gateway and the application server separately establish a temporary long connection for data with a large amount of data, and the gateway transparently transmits the data with a large amount of data sent by the mobile terminal to the application server or other gateways, The data is not encapsulated and controlled by the AOP layer protocol. At this time, the gateway is equivalent to a transparent proxy between the mobile terminal and the application server, which avoids the impact of large data transmission on the transmission of other control signaling. At the same time, the temporary connection is in the It will be released after the transmission is over, saving the resources of the mobile terminal and the application server to the greatest extent. In addition, since there is no heartbeat detection for the temporary long connection in the form of Proxy, in some special cases (such as the power failure of the mobile terminal), the gateway will not receive the broken link message. At this time, the gateway will always maintain the temporary connection with the mobile terminal. Long connections cause a waste of gateway resources. Therefore, the gateway can periodically detect the temporary long connection with the mobile terminal, query whether there is data transmission, and release the temporary long connection if there is no temporary long connection and no data transmission within a continuous period of time. The release process of the temporary long connection between the gateway and the application server is similar to that of the mobile terminal.

Embodiment three:

Embodiment 3 of the present invention also provides a method for downlink data transmission, as shown in FIG. 6, the method includes the following steps:

Step 601: the application server sends a downlink data message to the gateway through the second long connection established with the gateway.

In the solution of this embodiment, a second long connection is established between each application server and the home gateway. When the application server needs to push a downlink data message to any mobile terminal it serves, the second long connection will Downlink data messages are sent to the gateway.

The identification of the mobile terminal is carried in the downlink data message. According to the description of the first and second embodiments, the identification of the mobile terminal involved in the present invention includes the first identification used when the mobile terminal registers in the application server and The second identifier used when the mobile terminal is registered in the gateway. Therefore, the mobile terminal identifier stored by the application server is the first identifier of the mobile terminal (such as a mobile phone number), and the application server will carry the first identifier of the mobile terminal in the downlink data message , used to instruct the gateway to send the downlink data message to the corresponding mobile terminal.

Further, since this step is a process in which the application server actively pushes the downlink data message to the mobile terminal, at this time, the mobile terminal may establish a first long-term connection with the gateway, and may receive the downlink data message in real time, or may not establish the first long-term connection with the gateway. connection, the downlink data message cannot be received in real time; at the same time, the application program that needs to receive the downlink data message in the mobile terminal may be in the three states of running, dormant or exited, so even if the mobile terminal receives the downlink data message, it is in dormancy Or the application program in the exit state cannot receive and process the downlink data message in time. Therefore, the application server sets a flag bit in the downlink data message sent to the gateway. If the flag bit is 1, it means that the real-time performance of the downlink data message is high, and the application server hopes that the downlink data message will be received by the corresponding application in time. If the application program is in the dormant or exit state, the mobile terminal is required to wake up the application program; if the flag position is 0, it means that the real-time performance of the downlink data message is low. If the application program is in the dormancy or exit state, the mobile terminal can wait for the corresponding is sent to the application after it runs.

Step 602: The gateway determines the corresponding mobile terminal according to the first identifier of the mobile terminal carried in the downlink data message.

Similar to Embodiment 1, the mobile terminal in this embodiment is also registered in the gateway, and the first identifier and the second identifier of the mobile terminal are stored in the DNS, and the gateway and the second long-term connection respectively established with the gateway are also stored in the DNS. The first corresponding relationship of the application server, and the second corresponding relationship between the second identification and the identification of the home gateway of the mobile terminal. DNS can provide users and gateways with a friendly graphical interface to support adding, deleting, modifying and querying stored information, and the stored information will take effect and be available in a timely manner.

The gateway searches the DNS for the corresponding second identifier according to the received first identifier of the mobile terminal, and the gateway determines the corresponding mobile terminal according to the second identifier.

Step 603: The gateway sends the downlink data message to the mobile terminal through the first long connection with the mobile terminal.

Similar to Embodiment 1, the application server at the source end of the downlink data message and the mobile terminal at the destination end may belong to the same gateway, or may belong to different gateways.

1. If the application server and the mobile terminal belong to the same gateway, the specific implementation of this step is as follows:

The gateway detects whether a first long connection has been established with the mobile terminal;

If yes, then send the downlink data message to the mobile terminal through the established first long connection.

Otherwise, notify the mobile terminal to establish the first long connection with the gateway, and send the downlink data message to the mobile terminal after the first long connection is established.

It should be noted that when the gateway detects that the first long-term connection has not been established with the mobile terminal, the gateway may use a short message notification method to request the mobile terminal to establish the first long-term connection with the gateway, so as to ensure timely push of downlink data messages.

2. If the application server and the mobile terminal belong to different gateways, the specific implementation of this step is as follows:

Since the gateway receiving the downlink data message is not the gateway to which the mobile terminal belongs, the first long connection is not established between the mobile terminal and the gateway. The gateway determines that the first long connection has not been established with the mobile terminal at the destination, and queries the second identification of the mobile terminal from the DNS, and finds that the mobile terminal is not a locally registered mobile terminal, then the gateway, according to the second correspondence stored in the DNS , query other gateways to which the destination mobile terminal belongs (in order to distinguish from the gateway that receives the downlink data message sent by the application server and the gateway to which the mobile terminal belongs, the gateway to which the mobile terminal belongs is referred to as other gateways), and the downlink After the data message is sent to the other gateways, it is sent to the mobile terminal by the other gateways.

In addition, during the execution of step 603, if the gateway receives downlink data messages sent by multiple application servers, or multiple downlink data messages sent by one application server, the gateway can follow the service priority or The priorities of the mobile terminals are sorted and sent sequentially.

Step 604: After receiving the downlink data message, the mobile terminal determines the application receiving the downlink data message according to the application server identifier carried in the downlink data message.

In the solution of this embodiment, the mobile terminal manages the locally installed application programs according to the real-time example 1, and records the identifiers of the locally installed application programs and the identifiers of the application servers corresponding to each application program.

Step 605: The mobile terminal inquires whether the application program is running, and if so, notifies the application program to obtain the downlink data message; otherwise, wakes up or starts the application program, and notifies the wake-up or started application program to obtain the downlink data message data message.

If the application server sets the flag position of the pushed downlink data message to 1, indicating that it is required to wake up the application program of the mobile terminal, then after the gateway determines the mobile terminal as the destination, it wakes up the application program in the mobile terminal in the following two ways:

The first way: when the mobile terminal and the gateway have established the first long connection, the gateway sends a wake-up data packet to the mobile terminal through the first long connection, that is, the IP Push wake-up mode, requiring the mobile terminal to wake up the mobile terminal that needs to receive the downlink data message application.

The second method: the first long connection is not established between the mobile terminal and the gateway, and the gateway uses a short message notification method to require the mobile terminal to establish the first long connection with the gateway, and then send a message to the mobile terminal through the first long connection. Wake-up packet, that is, short message wake-up method.

On the local side of the mobile terminal, there is an AOI middleware in the mobile terminal, which is used for orderly management of various applications and long-term connection management with the gateway. The connection method is directly connected to the AOI middleware to obtain the downlink data message pushed by the gateway through the first long connection; if the installed application program is not running, after the mobile terminal wakes up or starts the application program, the application program passes through Connect to the AOI middleware in the way of Socket long connection, and then obtain the downlink data message pushed by the gateway through the first long connection.

Similar to Embodiment 2, the solution of Embodiment 3 can also adopt the Proxy transmission method when the amount of data to be transmitted by the application server is very large, by additionally establishing temporary long connections between the application server and the gateway, and between the gateway and the mobile terminal To transparently transmit a large amount of data.

At the same time, the solution of the third embodiment can also encrypt and compress the downlink data message for transmission according to the method of the real-time example 1, and the gateway can generate a bill for downlink transmission using the method of the third embodiment.

In the solution of the third embodiment, also in order to keep the first long connection between the mobile terminal and the gateway alive in real time without increasing the resource overhead of the wireless communication network, the lifetime of the heartbeat data packet is set to be greater than The distance through the core network firewall is less than the distance to the wireless communication network where the mobile terminal is located. On the one hand, the heartbeat data packet can pass through the core network firewall to achieve the purpose of keeping alive the first long connection between the mobile terminal and the gateway. , on the other hand, the heartbeat data packet does not enter the wireless communication network, will not increase the burden on the wireless communication network, and will not occupy the wireless channel.

The method for transmitting the heartbeat data packet for the first long connection in the third embodiment is the same as the method in the first embodiment.

Similar to Embodiment 1, through the technical solutions described in steps 601 to 605 above, the gateway becomes the intermediary of the real-time transmission process between the application server and the mobile terminal, and the application server does not need to establish long connections with a large number of mobile terminals respectively, only Establishing a second long connection with a gateway can push downlink data messages to any mobile terminal served in real time, and mobile terminals only need to establish a first long connection with a gateway to receive real-time downlink data messages pushed by the application server , in the case of ensuring high real-time data transmission, it can effectively reduce the resource overhead allocated by the mobile terminal and the application server for the long connection.

Embodiment four:

Embodiment 4 of the present invention also provides a data transmission system under the same inventive concept as Embodiment 1 and Embodiment 2, which is applied in the uplink transmission process, as shown in FIG. 7 , including a mobile terminal 11, a gateway 12, an application The server 13 and the keep-alive device 14, wherein the mobile terminal 11 is used to establish a first long connection with the gateway 12, and send an uplink data message to the gateway 12 through the first long connection, and the uplink data message carries The identification of the application server; the gateway 12 is configured to send the uplink data message through the second long connection when it is determined that a second long connection has been established between the application servers 13 corresponding to the application server identification To the application server 13; the application server 13 is used to receive the uplink data message through the second long connection; the keep-alive device 14 is used to use the set routing distance as the heartbeat for the first long connection The survival time of the data packet is to send the heartbeat data packet to the mobile terminal, and the routing distance is greater than the distance of the heartbeat data packet passing through the core network firewall, but less than the distance to the wireless communication network where the mobile terminal is located. The keep-alive device 14 may be a keep-alive subsystem in the gateway 12, or a device independent of the gateway 12 but capable of interacting with the gateway.

The application server 13 may be an application server on the Internet, or an application server within an enterprise.

The system also includes a domain name system 15, configured to receive a gateway query request initiated by the mobile terminal 11, the gateway query request carrying the first identifier used when the mobile terminal registers in the application server and the second identifier of the mobile terminal, and sending The mobile terminal 11 returns the routing information of the mobile terminal's home gateway, and stores the first identifier and the second identifier of the mobile terminal; the mobile terminal 11 is also configured to send a registration request including the second identifier to the gateway according to the routing information, And after registration, a first long connection is established with the gateway; the gateway 12 is also used for registering the mobile terminal.

It can be seen from Figure 8 that the gateway is connected to the DNS through an interface, so that the gateway can query information from the DNS in real time.

The domain name system 15 is also used to store the first corresponding relationship between the gateway and the application servers respectively establishing the second persistent connection with the gateway.

The gateway 12 is specifically configured to determine whether to establish a second long connection with the corresponding application server according to the identification of the application server carried in the uplink data message, and if so, send the uplink data message through the second long connection to The application server, otherwise, queries other gateways that have established a second long connection with the corresponding application server from the DNS, and after sending the uplink data message to the other gateways, the other gateways send the message to the other gateways. corresponding application server.

In this embodiment, the gateway needs to perform route management and query other gateways to send data messages, therefore, there is an interface between the gateway and other gateways to transmit data messages.

The mobile terminal 11 is also used to send a proxy request to the gateway, the proxy request carrying the identification of the application server and the data volume of the data to be transmitted; the gateway 12 is also used to determine that the data volume reaches a threshold According to the identification of the application server carried in the proxy request, it is judged whether a second long connection has been established with the corresponding application server, and if so, a temporary long connection is established between the mobile terminal and the corresponding application server respectively, and the connection with the mobile The temporary long connection between the terminals receives the data to be transmitted from the mobile terminal, releases the temporary long connection with the mobile terminal after the transmission, and passes the data to be transmitted through the temporary connection with the application server Transparently transmit the long connection to the application server, and release the temporary long connection with the application server after the transmission; otherwise, query the DNS for other gateways that have established the second long connection with the corresponding application server, and communicate with the corresponding application server respectively The mobile terminal establishes a temporary long connection with the other gateway, receives the data to be transmitted from the mobile terminal through the temporary long connection with the mobile terminal, and releases the temporary long connection with the mobile terminal after the transmission ends, And, transparently transmit the data to be transmitted to other gateways through the temporary long connections with the other gateways, and release the temporary long connections with the other gateways after the transmission ends.

The mobile terminal 11 is also used to record the identifiers of the locally installed applications and the identifiers of the application servers corresponding to each application, and determine the identifier of the corresponding application server after receiving an uplink data message generated by any application , and carry the identifier of the application server in the uplink data message.

In addition, according to the description of Embodiment 1 and Embodiment 2 of the present invention, the gateway also needs to notify the mobile terminal to establish the first long connection, generate a bill, and manage the mobile terminal through a short message. Therefore, the system of this embodiment can also It further includes Short Message Gateway (ISMG), Billing System (BOSS) and network management.

Embodiment five:

Embodiment 5 of the present invention also provides a data transmission system under the same inventive concept as Embodiment 3. Its structure is the same as that of Embodiment 4, and it is applied in the downlink transmission process, including: mobile terminal 11, gateway 12, The application server 13 and the keep-alive device 14, wherein: the application server 13 is used to establish a second long connection with the gateway 12, and send a downlink data message to the gateway through the second long connection, and the downlink data message carries the mobile terminal in the The first identification used when registering in the application server; the gateway 12 is used to send the downlink data message to the mobile terminal 11 through the first long connection between the mobile terminal 11 corresponding to the first identification; The terminal 11 is used to receive the downlink data message through the first long connection; the keep-alive device 14 is used to send the set routing distance as the survival time of the heartbeat packet to the mobile terminal for the first long connection. For the heartbeat data packet, the routing distance is greater than the distance passing through the firewall of the core network, but less than the distance reaching the wireless communication network where the mobile terminal is located.

The gateway 12 is specifically used to detect whether a first long connection has been established with the mobile terminal, and if so, send the downlink data message to the mobile terminal through the established first long connection; otherwise, notify the mobile terminal A first long connection with the gateway is established, and the downlink data message is sent to the mobile terminal 11 after the first long connection is established.

It also includes a domain name system 15, which is used to store the first identifier and the second identifier of the mobile terminal, and the second corresponding relationship between the second identifier and the home gateway identifier of the mobile terminal; the gateway 12 is specifically used to The first identification carried in the DNS, query the second identification of the mobile terminal from the DNS, and judge whether the mobile terminal is a locally registered mobile terminal according to the second identification inquired, and if so, connect the mobile terminal through the first long connection The downlink data message is sent to the mobile terminal; otherwise, according to the second correspondence, other gateways to which the mobile terminal belongs are queried from DNS, and after the downlink data message is sent to the other gateways, the The other gateway sends to the mobile terminal.

The application server 13 is also used to send a proxy request to the gateway 12, the proxy request carries the first identification of the mobile terminal and the data volume of the data to be transmitted; the gateway 12 is also used to determine that the data volume reaches the threshold When the limit value is reached, according to the first identifier carried in the proxy request, the corresponding second identifier is determined by querying DNS, and according to the determined second identifier, it is judged whether the corresponding mobile terminal is a locally registered mobile terminal, and if so, the gateway respectively Establish a temporary long connection with the corresponding mobile terminal and the application server sending the proxy request, receive the data to be transmitted from the application server through the temporary long connection with the application server, and release the data with the application server after the transmission is completed. The temporary long connection between the servers, and transparently transmit the data to be transmitted to the mobile terminal through the temporary long connection with the mobile terminal, and release the temporary long connection with the mobile terminal after the transmission; otherwise, the gateway Query the other gateways to which the corresponding mobile terminal belongs from DNS, and establish temporary long connections with the application server sending the proxy request and the other gateways, and receive data from the application server through the temporary long connection with the application server. data to be transmitted, release the temporary long connection with the application server after the transmission, and transparently transmit the data to be transmitted to other gateways through the temporary long connection with the other gateways, and release the temporary long connection with the application server after the transmission ends Then release the temporary long connection with the other gateways.

The mobile terminal 11 is also used to record the identifiers of the locally installed applications and the identifiers of the application servers corresponding to each application, and when receiving the downlink data message, determine the received The application program of the downlink data message, and inquire whether the application program is in a running state, if so, notify the application program to obtain the downlink data message; otherwise, wake up or start the application program, and notify the application program after waking up or starting Obtain the downlink data message.

Embodiment six:

Embodiment 6 of the present invention also provides a gateway under the same inventive concept as Embodiment 1 to Embodiment 5, as shown in FIG. 8 , including an online subsystem, a Proxy subsystem, an authentication subsystem, and a support subsystem. The following are respectively To illustrate.

1. The online subsystem follows the AOP (Always On Protocol), accepts and maintains the long connection with the mobile terminal and the application server, and provides the notification function of the long connection to the mobile terminal at the same time, requiring the long connection between the mobile terminal to exist in real time , combining the long connection method with the IP Push method to provide timely, stable and efficient data transmission services between the mobile terminal and the application server.

The online subsystem includes a first connection module and a transmission module, wherein the first connection module is used to establish a first long connection with the mobile terminal, and a second long connection with the application server; the transmission module is used for uplink transmission During the process, when receiving the uplink data message sent by the mobile terminal through the first long connection, according to the identification of the application server carried in the uplink data message, the uplink data message is sent to the corresponding application server through the second long connection, and During the downlink transmission process, when receiving the downlink data message sent by the application server through the second long connection, according to the first identification of the mobile terminal carried in the downlink data message, the downlink data message is sent to the corresponding mobile terminal.

The online subsystem also includes:

The routing management module is used to determine whether to establish a second long connection with the application server corresponding to the application server identifier carried in the uplink data message during the uplink transmission, and to query from the DNS when the second long connection is not established. The corresponding application server establishes other gateways of the second long connection. During the downlink transmission process, it is judged whether the mobile terminal is a locally registered mobile terminal. When the mobile terminal is not a locally registered mobile terminal, the DNS Query other gateways to which the mobile terminal belongs; and the transmission module is further configured to send the uplink data message or downlink data message to the other gateways.

The registration module is used to complete the registration operation of the mobile terminal, and record the second identification of the registered mobile terminal.

The VPN access module is used to perform security management on the uplink data message and the downlink data message through a virtual private network (VPN) when the uplink data message and the downlink data message are transmitted through the first long connection and the second long connection , such as adopting tunnel technology, encryption and decryption technology, key management technology and identity authentication technology to improve the security of transmitted uplink data messages and downlink data messages.

The SMS Push module is used to wake up the application program in the mobile terminal by means of a short message.

The IP Push module is used to wake up the application program in the mobile terminal through the IP Push mode.

2. The Proxy subsystem provides a transmission agent for large amount of data between the mobile terminal and the application server.

The Proxy subsystem includes a proxy module and a second connection module.

The proxy module is used to receive a proxy request from the mobile terminal during the uplink transmission process, the proxy request carries the identification of the application server and the data volume of the data to be transmitted, and when it is determined that the data volume reaches the threshold value, according to The identification of the application server carried in the proxy request, and judging whether the second long connection has been established with the corresponding application server; during the downlink transmission process, receiving the proxy request from the application server, the proxy request carrying the first identification of the mobile terminal and the amount of data to be transmitted, and when it is determined that the amount of data reaches the threshold value, judge whether the corresponding mobile terminal is a locally registered mobile terminal according to the first identifier carried in the proxy request.

The second connection module is used to establish a temporary long connection with the mobile terminal and the corresponding application server respectively if the gateway has established a second long connection with the corresponding application server during the uplink transmission, and through the connection with the mobile terminal Receive the data to be transmitted from the mobile terminal through the temporary long connection, and release the temporary long connection with the mobile terminal after the transmission, and pass the data to be transmitted through the temporary long connection with the application server Transparently transmit to the application server, and release the temporary long connection with the application server after the transmission is over; otherwise, query from the DNS for other gateways that have established the second long connection with the corresponding application server, and communicate with the mobile The terminal establishes a temporary long connection with the other gateway, receives the data to be transmitted from the mobile terminal through the temporary long connection with the mobile terminal, and releases the temporary long connection with the mobile terminal after the transmission ends, and, The data to be transmitted is transparently transmitted to other gateways through the temporary long connection with the other gateway, and the temporary long connection with the other gateway is released after the transmission is completed. In the downlink transmission process, if the corresponding mobile terminal is a locally registered mobile terminal, a temporary long connection is established between the corresponding mobile terminal and the application server sending the proxy request, through The temporary long connection receives the data to be transmitted from the application server, releases the temporary long connection with the application server after the transmission, and transparently transmits the data to be transmitted through the temporary long connection with the mobile terminal to the mobile terminal, and release the temporary long connection with the mobile terminal after the transmission is over; otherwise, query the other gateways to which the corresponding mobile terminal belongs from DNS, and communicate with the application server that sent the proxy request and the other gateways respectively Establish a temporary long connection between the gateways, receive the data to be transmitted from the application server through the temporary long connection with the application server, and release the temporary long connection with the application server after the transmission, and transfer the data to be transmitted Transparently transmit to other gateways through the temporary long connections with the other gateways, and release the temporary long connections with the other gateways after the transmission ends.

3. The authentication subsystem is responsible for authenticating the registered mobile terminal and the application server. Only the mobile terminal that passes the authentication is allowed to register and establish the first long connection, and the application server that passes the authentication is allowed to establish the second long connection. connect.

The authentication subsystem includes:

The user management module is used to record the information of the mobile terminal and the application server belonging to the gateway.

The service management module is used to record the services supported by the mobile terminal belonging to the gateway and the services supported by the application server.

The security management module is used to record security information, including encrypted information used in tunneling technology, encryption and decryption technology, key management technology and identity authentication technology.

The authentication module is used to use the information in the user management module, the service management module and the security management module to authenticate the mobile terminal and the application server that establish the first persistent connection and the second persistent connection.

4. The supporting subsystem is responsible for statistical analysis of the transmitted data messages, monitoring the uplink and downlink transmission process, and upgrading the middleware used to manage the installed application programs in the mobile terminal.

Support subsystems include:

The statistical analysis module is used for performing statistical analysis on the data messages transmitted through the first long connection and the second long connection and the data transmitted through the temporary long connection.

The monitoring module is used to monitor the transmission process through the first long connection, the second long connection and the transmission process through the temporary long connection, and give an alarm when an abnormality occurs.

The billing module is used for charging bills generated through the transmission process of the first long connection, the second long connection and the transmission process of the temporary long connection.

The upgrade module is used to detect in real time whether the middleware in the mobile terminal needs to be upgraded, and when it needs to be upgraded, send the upgrade information of the middleware to the mobile terminal.

The log module is used to record the log information generated by various operations of the gateway.

The auxiliary module is used for auxiliary management of the interface between the gateway and various external devices.

Embodiment seven:

Embodiment 7 of the present invention also provides a mobile terminal under the same inventive concept as Embodiment 1 to Embodiment 5, as shown in FIG. 9 , including an interface module, a core module, and a support module. It is a module integrated in the mobile terminal, and may also be an integrated module of the AOI middleware installed in the mobile terminal.

The following describes the interface module, core module and support module respectively:

1. The interface module is mainly responsible for establishing the first long connection with the external gateway, the long connection between the application program installed in the mobile terminal and the middleware, and the temporary long connection with the gateway.

2. The core module provides the core function of the AOI middleware, and is the main module for realizing the object of the present invention.

Core modules include:

A data transceiver module, configured to send an uplink data message to the gateway through the first long connection during the uplink transmission process, the uplink data message carries the identification of the application server, and receive the gateway through the first long connection during the downlink transmission process Pushed downlink data message.

The proxy request module is used to send a proxy request to the gateway when using the Proxy function for transmission, and the proxy request carries the identification of the application server and the data volume of the data to be transmitted;

The IP proxy module is configured to send the data to be transmitted to the gateway through the temporary long connection when using the Proxy function for transmission, and receive the data to be transmitted pushed by the gateway through the temporary long connection.

The registration module is used to obtain the routing information of the home gateway from the DNS, and register with the gateway according to the routing information.

The management module is configured to record the identifiers of the locally installed applications and the identifiers of the application servers corresponding to each application, and determine the identifier of the corresponding application server after receiving an uplink data message generated by any application, and The identifier of the application server is carried in the uplink data message.

The wake-up module is used to determine the application program receiving the downlink data message according to the application server identifier carried in the downlink data message when receiving the downlink data message, and inquire whether the application program is in a running state, and if so, notify the application program The program obtains the downlink data message; otherwise, wakes up or starts the application program, and notifies the wake-up or started application program to obtain the downlink data message.

The compression/decompression module is used to compress the sent uplink data message and decompress the received downlink data message.

3. The supporting modules include:

The log module is used to record log information generated by various operations of the mobile terminal.

The configuration module is used to configure the parameters required for various operations of the mobile terminal, such as the routing configuration from the mobile terminal to DNS.

The upgrade module is configured to upgrade the middleware when receiving the upgrade information for the middleware sent by the gateway.

Embodiment eight:

Embodiment 8 of the present invention also provides an application server under the same inventive concept as Embodiment 1 to Embodiment 5. As shown in FIG. 10 , it includes an interface module and a data sending and receiving module. Long connection: the data transceiver module is used to receive the uplink data message sent by the gateway through the second long connection, and send the downlink data message to the gateway through the second long connection, and the downlink data message carries the mobile terminal in the application server The first identifier used when registering in .

The interface module is also used to establish a temporary long connection with the gateway, and the data sending and receiving module is also used to send and receive data to be transmitted through the temporary long connection.

Embodiment nine:

Embodiment 9 of the present invention also provides a keep-alive device under the same inventive concept as Embodiment 1 to Embodiment 5, as shown in FIG. 11 , including a data collection module, a distance detection module and a data packet sending module, wherein:

The data acquisition module is used to capture the communication data packets between the mobile terminal and the application server at both ends of the long connection in real time when the data channel is in the TCP-based mode, establish and maintain the quintuple of the mobile terminal, and extract the sequence of the current mobile terminal TCP connection Information (seq), response information (ack); when the data channel is UDP-based, it is used to obtain the IP and UDP port information of the terminal device in real time.

The distance detection module is used to detect the routing distance required by the heartbeat packet.

The data packet sending module is used for sending the heartbeat data packet to the mobile terminal using the routing distance as the survival time of the heartbeat data packet.

Specifically, as shown in Figure 12, the distance detection module includes a first route determination module and a second route determination module, wherein: the first route determination module is used to send a test data packet to the mobile terminal, and determine that the test data packet is routed to The first routing distance generated when moving the terminal; the second routing determination module is used to determine the one-hop route of the test data packet after passing through the core network firewall and before arriving at the wireless communication network where the mobile terminal is located according to the first routing distance , the generated second routing distance; therefore, the data packet sending module is configured to use the second routing distance as the lifetime of the heartbeat data packet, and send the heartbeat data packet to the mobile terminal.

Similar to the solution in Embodiment 2, the first routing determination module can also determine the first routing distance by gradually increasing the routing distance, gradually reducing the routing distance to determine the first routing distance and the dichotomy method to determine the first routing distance , which are explained below:

1. Determine the first routing distance by gradually increasing the routing distance:

(1), TCP mode:

The first route determination module is specifically configured to set the sequence number value of the test data packet as the sequence number identified as an error by the mobile terminal, and gradually increase the preset third route distance, for each increase The route distance obtained after large performs the following operations:

Using the routing distance obtained this time as the survival time of the test data packet, sending the test data packet to the mobile terminal;

If the reset RST message is returned, the routing distance obtained this time is used as the first routing distance;

If the error type carried in the returned ICMP message is timeout, continue to increase the routing distance.

(2), UDP mode:

The first route determination module is specifically configured to set the destination port number carried in the test data packet as the UDP port number of the user data packet that the mobile terminal cannot correctly receive the test data packet, and gradually increase the preset For the fourth routing distance of , the following operations are performed for the routing distance obtained after each increase:

Using the routing distance obtained this time as the survival time of the test packet, sending the test packet to the mobile terminal, and detecting the received Control Message Protocol ICMP message;

If the error type carried by the ICMP message is that the port is unreachable, the routing distance obtained this time is used as the first routing distance;

If the error type carried in the ICMP message is timeout, continue to increase the routing distance.

2. Determine the first routing distance by gradually reducing the routing distance:

(1), TCP mode:

The first routing determination module is specifically configured to gradually reduce the preset fifth routing distance, and perform the following operations on the routing distance obtained after each reduction:

The routing distance obtained this time is used as the survival time of the test packet, and the test packet is sent to the mobile terminal through the TCP connection that has determined the quintuple information, and judges whether to receive the test response message returned;

If so, continue to reduce the routing distance;

Otherwise, add 1 to the routing distance obtained this time as the first routing distance.

(2), UDP mode:

The first routing determination module is specifically configured to gradually reduce the preset sixth routing distance, and perform the following operations on the routing distance obtained after each reduction:

Using the routing distance obtained this time as the survival time of the test packet, according to the IP address and the UDP port of the mobile terminal, send the test packet to the mobile terminal, and judge whether to receive the test response message returned;

If so, continue to reduce the routing distance;

Otherwise, add 1 to the routing distance obtained this time as the first routing distance.

3. Dichotomy method:

(1), TCP mode:

The first route determination module is specifically used to pre-set the upper limit routing distance and the lower limit routing distance. When the upper limit routing distance or the lower limit routing distance is updated each time, it is judged whether the upper limit routing distance is not less than the lower limit routing distance. If so, then Perform the following operations until the upper limit routing distance is smaller than the lower limit routing distance:

The average value of the upper limit routing distance and the lower limit routing distance obtained this time is rounded to obtain the seventh routing distance, and the seventh routing distance obtained this time is used as the survival time of the test data packet. Connect to send the test data packet to the mobile terminal, and judge whether to receive the returned test response message;

If so, then subtract 1 from the routing hop count of the seventh routing distance obtained this time as the updated upper routing distance;

Otherwise, subtract 1 from the routing hop count of the seventh routing distance obtained this time as the updated lower limit routing distance;

Determine the seventh routing distance obtained when the upper limit routing distance is less than the lower routing distance, when the seventh routing distance is the life time of the test packet, if a test timeout message is received, the routing jump of the seventh routing distance The number plus 1 is used as the first routing distance; if a correct test message is received, the routing hop count of the seventh routing distance is used as the first routing distance.

(2), UDP mode:

The first route determination module is specifically used to pre-set the upper limit routing distance and the lower limit routing distance. When the upper limit routing distance or the lower limit routing distance is updated each time, it is judged whether the upper limit routing distance is not less than the lower limit routing distance. If so, then Perform the following operations until the upper limit routing distance is smaller than the lower limit routing distance:

The average value of the upper limit routing distance and the lower limit routing distance obtained this time is rounded to obtain the eighth routing distance, and the eighth routing distance obtained this time is used as the survival time of the test packet, according to the IP address of the mobile terminal and UDP port, send this test packet to described mobile terminal, and judge whether to receive the test response message that returns;

If so, then subtract 1 from the route hop count of the eighth route distance obtained this time as the updated upper limit route distance;

Otherwise, subtract 1 from the routing hop count of the eighth routing distance obtained this time as the updated lower limit routing distance;

Determine the eighth route distance obtained when the upper limit route distance is less than the lower limit route distance, when the eighth route distance is the life time of the test packet, if a test timeout message is received, the route jump of the eighth route distance The number plus 1 is used as the first routing distance; if the test correct message is received, the routing hop count of the eighth routing distance is used as the first routing distance.

The second route determination module is specifically configured to subtract 1 from the routing hop count of the first routing distance as the maximum value of the second routing distance, and use the routing hop count generated when passing through the core network firewall as the The minimum value of the second routing distance, using the routing hops not greater than the maximum value and not less than the minimum value as the second routing distance.

The keep-alive device in the ninth embodiment may be the keep-alive subsystem in the gateway at the end of the first long connection, as shown in Figure 13, the first long connection is established between the gateway and the mobile terminal, and the gateway wakes up the terminal in the communication short message mode When the application program in the terminal is connected, the gateway is also connected to ISMG and SMS in the mobile communication network, and when the application program in the terminal is awakened by IP Push, the gateway is also connected to the GGSN in the mobile communication network. The keep-alive subsystem in the gateway keeps alive the first longest connection between the terminal and the gateway.

The keep-alive device may also be a device independent of the gateway, and performs keep-alive for the first long connection between the gateway and the mobile terminal.

Through the method, system and equipment provided by the embodiments of the present invention, compared with the IP Push solution in the prior art, the number of long connections can be effectively reduced on the basis of ensuring high real-time data transmission between the mobile terminal and the application server , less resource occupation for mobile terminals and application servers. At the same time, the AOI architecture of the mobile terminal in the embodiment of the present invention provides a good data channel for application service providers, network operators and users, and provides a platform for unified management and control of mobile services. At the same time, the heartbeat data packet for the first long connection can not only pass through the core network firewall to enter the core network provided by the operator to keep the long connection alive, but also terminate at the wireless communication network where the mobile terminal is located. The previous one-hop router avoids the burden of heartbeat packets on the wireless communication network.

Those skilled in the art should understand that the embodiments of the present application may be provided as methods, systems, or computer program products. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present application 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, CD-ROM, optical storage, etc.) having computer-usable program code embodied therein.

The present application is described with reference to flowcharts and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the present application. 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.

While preferred embodiments of the present application have been described, additional changes and modifications to these embodiments can be made by those skilled in the art once the basic inventive concept is appreciated. Therefore, the appended claims are intended to be construed to cover the preferred embodiment and all changes and modifications which fall within the scope of the application.

Obviously, those skilled in the art can make various changes and modifications to the present invention without departing from the spirit and scope of the present invention. Thus, if these modifications and variations of the present invention fall within the scope of the claims of the present invention and equivalent technologies thereof, the present invention also intends to include these modifications and variations.

Claims (33)

1. A method of data transmission, the method comprising:

the gateway receives an uplink data message from the mobile terminal through a first long connection established between the gateway and the mobile terminal, wherein the uplink data message carries an identifier of an application server, and the first long connection transmits the uplink data message generated by any application program in the mobile terminal;

when determining that a second long connection is established between the application servers corresponding to the identifiers of the application servers, the gateway sends the uplink data message to the application servers through the second long connection;

and aiming at the first long connection, sending the heartbeat data packet to the mobile terminal by taking a set routing distance as the survival time of the heartbeat data packet, wherein the routing distance is greater than the distance of the heartbeat data packet passing through the firewall of the core network but less than the distance of the heartbeat data packet reaching the wireless communication network where the mobile terminal is located.

2. The method of claim 1, wherein prior to the gateway receiving the upstream data message from the mobile terminal over the first long connection, the method further comprises:

a Domain Name System (DNS) receives a gateway query request initiated by a mobile terminal, wherein the gateway query request carries a first identifier used when the mobile terminal is registered in an application server and a second identifier of the mobile terminal;

the DNS returns the routing information of the home gateway of the mobile terminal to the mobile terminal and stores a first identifier and a second identifier of the mobile terminal;

and the gateway receives a registration request which is initiated by the mobile terminal according to the routing information and contains the second identifier, and establishes a first long connection with the mobile terminal after registering for the mobile terminal.

3. The method of claim 2, wherein the uplink data message further carries a second identifier of the mobile terminal;

the gateway sends the uplink data message to the application server, and specifically includes:

the gateway queries a first identifier of the mobile terminal from the DNS according to a second identifier of the mobile terminal;

and the gateway carries the first identifier of the mobile terminal in the uplink data message and sends the first identifier to the application server, so as to inform the application server of the mobile terminal sending the uplink data message.

4. The method of claim 1, wherein prior to the gateway receiving the upstream data message from the mobile terminal over the first long connection, the method further comprises:

the DNS stores a first correspondence between a gateway and application servers that respectively establish a second long connection with the gateway.

5. The method of claim 4, wherein the gateway sending the upstream data message to the application server specifically comprises:

the gateway judges whether to establish a second long connection with a corresponding application server according to the identification of the application server carried in the uplink data message;

if so, sending the uplink data message to an application server through the second long connection;

and if not, inquiring other gateways establishing second long connection with the corresponding application server from the DNS, and sending the uplink data message to the other gateways which then send the uplink data message to the corresponding application server.

6. The method of claim 4, wherein the method further comprises:

the gateway receives an agent request from the mobile terminal, wherein the agent request carries an identification of an application server and a data volume of data to be transmitted;

when the gateway determines that the data volume reaches the threshold value, judging whether a second long connection is established with the corresponding application server according to the identification of the application server carried in the proxy request;

if so, respectively establishing temporary long connection between the gateway and the mobile terminal and the corresponding application server, receiving the data to be transmitted from the mobile terminal through the temporary long connection between the gateway and the mobile terminal, releasing the temporary long connection between the gateway and the mobile terminal after the transmission is finished, transmitting the data to be transmitted to the application server through the temporary long connection between the gateway and the application server, and releasing the temporary long connection between the gateway and the application server after the transmission is finished;

otherwise, the gateway inquires other gateways establishing second long connection with the corresponding application server from the DNS, respectively establishes temporary long connection with the mobile terminal and the other gateways, receives the data to be transmitted from the mobile terminal through the temporary long connection with the mobile terminal, releases the temporary long connection with the mobile terminal after the transmission is finished, transparently transmits the data to be transmitted to the other gateways through the temporary long connection with the other gateways, and releases the temporary long connection with the other gateways after the transmission is finished.

7. The method of claim 1, wherein prior to the gateway receiving the upstream data message from the mobile terminal over the first long connection, the method further comprises:

the mobile terminal records the identification of the locally installed application program and the identification of the application server corresponding to each application program;

after receiving an uplink data message generated by any application program, the mobile terminal determines the identifier of the corresponding application server and carries the identifier of the application server in the uplink data message.

8. The method of claim 1, wherein the set routing distance is determined by:

determining a first routing distance generated when a test data packet is routed to the mobile terminal according to the test data packet sent to the mobile terminal;

and according to the first routing distance, determining a second routing distance generated when the test data packet passes through a core network firewall and reaches a one-hop route before the wireless communication network where the mobile terminal is located as a set routing distance.

9. The method of claim 8, wherein the first routing distance and the second routing distance refer to routing hops of packets.

10. The method of claim 8, wherein the first routing distance is determined by:

setting a TCP header sequence number value of the test data packet as a value which is identified as an error by the mobile terminal;

gradually increasing a preset third routing distance, and executing the following operations for the routing distance obtained after each increase:

taking the obtained routing distance as the survival time of the test data packet, and sending the test data packet to the mobile terminal;

if the TCP message of the reset RST is returned, the obtained routing distance is used as a first routing distance;

if the error type carried by the returned control message protocol ICMP message is overtime, continuing to increase the routing distance;

or

Setting the destination port number carried in the test data packet as a user data packet UDP port number which cannot be correctly received by the mobile terminal, gradually increasing a preset fourth routing distance, and executing the following operations aiming at the routing distance obtained after each increase:

taking the obtained routing distance as the survival time of a test data packet, sending the test data packet to the mobile terminal, and detecting the received control message protocol ICMP message;

if the error type carried by the ICMP message is that the port is not reachable, taking the obtained routing distance as a first routing distance;

if the error type carried by the ICMP message is overtime, continuing to increase the routing distance;

or,

gradually reducing a preset fifth routing distance, and executing the following operations for the routing distance obtained after each reduction:

taking the obtained routing distance as the survival time of the test data packet, sending the test data packet to the mobile terminal through the TCP connection with the determined quintuple information, and judging whether a returned test response message is received or not;

if yes, continuing to reduce the routing distance;

otherwise, adding 1 to the obtained routing distance to serve as a first routing distance;

or,

gradually reducing a preset sixth routing distance, and executing the following operations for the routing distance obtained after each reduction:

taking the obtained routing distance as the survival time of the test data packet, determining the mobile terminal for receiving the test data packet according to the IP address and the UDP port of the mobile terminal, sending the test data packet to the mobile terminal, and judging whether a returned test response message is received or not;

if yes, continuing to reduce the routing distance;

otherwise, adding 1 to the obtained routing distance to serve as a first routing distance;

or,

presetting an upper limit routing distance and a lower limit routing distance, judging whether the upper limit routing distance is not less than the lower limit routing distance when the upper limit routing distance or the lower limit routing distance is updated each time, if so, executing the following operations until the upper limit routing distance is less than the lower limit routing distance:

rounding the average value of the obtained upper limit routing distance and the obtained lower limit routing distance to obtain a seventh routing distance, taking the obtained seventh routing distance as the survival time of a test data packet, sending the test data packet to the mobile terminal through the TCP connection with the determined quintuple information, and judging whether a returned test response message is received or not;

if so, subtracting 1 from the route hop count of the seventh route distance obtained this time to serve as the updated upper limit route distance;

otherwise, subtracting 1 from the route hop count of the seventh route distance obtained this time, and then taking the route hop count as the updated lower limit route distance;

determining a seventh routing distance obtained when the upper limit routing distance is smaller than the lower limit routing distance, and adding 1 to the routing hop count of the seventh routing distance to serve as the first routing distance if a test timeout message is received when the seventh routing distance is taken as the survival time of the test data packet; if the message of correct test is received, taking the route hop number of the seventh route distance as the first route distance;

or,

presetting an upper limit routing distance and a lower limit routing distance, judging whether the upper limit routing distance is not less than the lower limit routing distance when the upper limit routing distance or the lower limit routing distance is updated each time, if so, executing the following operations until the upper limit routing distance is less than the lower limit routing distance:

rounding the average value of the obtained upper limit routing distance and the obtained lower limit routing distance to obtain an eighth routing distance, taking the obtained eighth routing distance as the survival time of a test data packet, determining a mobile terminal for receiving the test data packet according to the IP address and the UDP port of the mobile terminal, sending the test data packet to the mobile terminal, and judging whether a returned test response message is received or not;

if so, subtracting 1 from the route hop count of the eighth route distance obtained this time to serve as the updated upper limit route distance;

otherwise, subtracting 1 from the route hop count of the eighth route distance obtained this time, and then taking the route hop count as the updated lower limit route distance;

determining an eighth routing distance obtained when the upper limit routing distance is smaller than the lower limit routing distance, and adding 1 to the routing hop count of the eighth routing distance as the first routing distance if a test timeout message is received when the eighth routing distance is taken as the survival time of the test data packet; and if the message with correct test is received, taking the route hop count of the eighth route distance as the first route distance.

11. The method according to any one of claims 8 to 10, wherein determining the generated second routing distance according to the first routing distance specifically comprises:

subtracting 1 from the route hop count of the first route distance to be used as the maximum value of the second route distance, and using the route hop count generated when the core network firewall is passed through as the minimum value of the second route distance;

and taking the route hop number which is not greater than the maximum value and not less than the minimum value as a second route distance.

12. A method of data transmission, the method comprising:

the gateway receives a downlink data message from an application server through a second long connection established between the gateway and the application server, wherein the downlink data message carries a first identifier used when the mobile terminal is registered in the application server, and the second long connection transmits the downlink data message sent to any terminal by the application server;

the gateway sends the downlink data message to the mobile terminal through a first long connection between the mobile terminals corresponding to the first identification;

and aiming at the first long connection, sending the heartbeat data packet to the mobile terminal by taking a set routing distance as the survival time of the heartbeat data packet, wherein the routing distance is greater than the distance of the heartbeat data packet passing through the firewall of the core network but less than the distance of the heartbeat data packet reaching the wireless communication network where the mobile terminal is located.

13. The method according to claim 12, wherein the gateway sends the downlink data message to the mobile terminal via a first long connection with the mobile terminal, specifically comprising:

the gateway detects whether a first long connection is established with the mobile terminal;

if so, sending the downlink data message to the mobile terminal through the established first long connection;

otherwise, the mobile terminal is informed to establish the first long connection with the gateway, and after the first long connection is established, the downlink data message is sent to the mobile terminal.

14. The method of claim 12, wherein prior to the gateway receiving the downstream data message from the application server over the second long connection, the method further comprises:

the method comprises the steps that a DNS receives a gateway query request initiated by a mobile terminal, wherein the gateway query request carries a first identifier of the mobile terminal and a second identifier of the mobile terminal;

the DNS returns the routing information of the mobile terminal home gateway to the mobile terminal, and stores a first identifier and a second identifier of the mobile terminal, and a second corresponding relation between the second identifier and the mobile terminal home gateway identifier;

and the mobile terminal initiates a registration request containing a second identifier to the home gateway according to the routing information and establishes a first long connection with the home gateway.

15. The method according to claim 14, wherein the gateway sends the downlink data message to the mobile terminal via a first long connection, specifically comprising:

the gateway inquires a second identifier of the mobile terminal from the DNS according to the first identifier carried in the downlink data message, and judges whether the mobile terminal is a registered mobile terminal in the gateway or not according to the inquired second identifier;

if so, sending the downlink data message to the mobile terminal through a first long connection;

otherwise, according to the second corresponding relation, inquiring other gateways to which the mobile terminal belongs from the DNS, and after sending the downlink data message to the other gateways, sending the downlink data message to the mobile terminal by the other gateways.

16. The method of claim 14, wherein the method further comprises:

the gateway receives an agent request from an application server, wherein the agent request carries a first identifier of the mobile terminal and the data volume of data to be transmitted;

when the gateway determines that the data volume reaches the threshold value, according to a first identifier carried in the proxy request, determining a corresponding second identifier by inquiring the DNS, and judging whether the corresponding mobile terminal is the mobile terminal registered in the gateway according to the determined second identifier;

if so, respectively establishing temporary long connection between the gateway and the corresponding mobile terminal and an application server sending the agent request, receiving the data to be transmitted from the application server through the temporary long connection between the gateway and the application server, releasing the temporary long connection between the gateway and the application server after the transmission is finished, transmitting the data to be transmitted to the mobile terminal through the temporary long connection between the gateway and the mobile terminal, and releasing the temporary long connection between the gateway and the mobile terminal after the transmission is finished;

otherwise, the gateway inquires other gateways to which the corresponding mobile terminal belongs from the DNS, respectively establishes temporary long connections with the application server sending the agent request and the other gateways, receives the data to be transmitted from the application server through the temporary long connections with the application server, releases the temporary long connections with the application server after the transmission is finished, transparently transmits the data to be transmitted to the other gateways through the temporary long connections with the other gateways, and releases the temporary long connections with the other gateways after the transmission is finished.

17. The method of claim 12, wherein the method further comprises:

the mobile terminal records the identification of the locally installed application program and the identification of the application server corresponding to each application program;

after the gateway sends the downlink data message to the mobile terminal through the first long connection, the method further includes:

the mobile terminal determines an application program for receiving the downlink data message according to the application server identifier carried in the downlink data message, and inquires whether the application program is in an operating state;

if yes, informing the application program to acquire the downlink data message;

otherwise, the application program is awakened or started, and the awakened or started application program is informed to acquire the downlink data message.

18. The method of claim 12, wherein the set routing distance is determined by:

determining a first routing distance generated when a test data packet is routed to the mobile terminal according to the test data packet sent to the mobile terminal;

and according to the first routing distance, determining a second routing distance generated when the test data packet passes through a core network firewall and reaches a one-hop route before the wireless communication network where the mobile terminal is located as a set routing distance.

19. The method of claim 18, wherein the first routing distance and the second routing distance refer to routing hops of packets.

20. The method of claim 19, wherein the first routing distance is determined by:

setting a TCP header sequence number value of the test data packet as a value which is identified as an error by the mobile terminal;

gradually increasing a preset third routing distance, and executing the following operations for the routing distance obtained after each increase:

taking the obtained routing distance as the survival time of the test data packet, and sending the test data packet to the mobile terminal;

if the TCP message of the reset RST is returned, taking the obtained routing distance as a first routing distance;

if the error type carried by the returned control message protocol ICMP message is overtime, continuing to increase the routing distance;

or,

setting the destination port number carried in the test data packet as a user data packet UDP port number which cannot be correctly received by the mobile terminal, gradually increasing a preset fourth routing distance, and executing the following operations aiming at the routing distance obtained after each increase:

taking the obtained routing distance as the survival time of a test data packet, sending the test data packet to the mobile terminal, and detecting the received control message protocol ICMP message;

if the error type carried by the ICMP message is that the port is not reachable, taking the obtained routing distance as a first routing distance;

if the error type carried by the ICMP message is overtime, continuing to increase the routing distance;

or,

gradually reducing a preset fifth routing distance, and executing the following operations for the routing distance obtained after each reduction:

taking the obtained routing distance as the survival time of the test data packet, sending the test data packet to the mobile terminal through the TCP connection with the determined quintuple information, and judging whether a returned test response message is received or not;

if yes, continuing to reduce the routing distance;

otherwise, adding 1 to the obtained routing distance to serve as a first routing distance;

or,

gradually reducing a preset sixth routing distance, and executing the following operations for the routing distance obtained after each reduction:

taking the obtained routing distance as the survival time of the test data packet, determining the mobile terminal for receiving the test data packet according to the IP address and the UDP port of the mobile terminal, sending the test data packet to the mobile terminal, and judging whether a returned test response message is received or not;

if yes, continuing to reduce the routing distance;

otherwise, adding 1 to the obtained routing distance to serve as a first routing distance;

or,

presetting an upper limit routing distance and a lower limit routing distance, judging whether the upper limit routing distance is not less than the lower limit routing distance when the upper limit routing distance or the lower limit routing distance is updated each time, if so, executing the following operations until the upper limit routing distance is less than the lower limit routing distance:

rounding the average value of the obtained upper limit routing distance and the obtained lower limit routing distance to obtain a seventh routing distance, taking the obtained seventh routing distance as the survival time of a test data packet, sending the test data packet to the mobile terminal through the TCP connection with the determined quintuple information, and judging whether a returned test response message is received or not;

if so, subtracting 1 from the route hop count of the seventh route distance obtained this time to serve as the updated upper limit route distance;

otherwise, subtracting 1 from the route hop count of the seventh route distance obtained this time, and then taking the route hop count as the updated lower limit route distance;

determining a seventh routing distance obtained when the upper limit routing distance is smaller than the lower limit routing distance, and adding 1 to the routing hop count of the seventh routing distance to serve as the first routing distance if a test timeout message is received when the seventh routing distance is taken as the survival time of the test data packet; if the message of correct test is received, taking the route hop number of the seventh route distance as the first route distance;

or,

presetting an upper limit routing distance and a lower limit routing distance, judging whether the upper limit routing distance is not less than the lower limit routing distance when the upper limit routing distance or the lower limit routing distance is updated each time, if so, executing the following operations until the upper limit routing distance is less than the lower limit routing distance:

rounding the average value of the obtained upper limit routing distance and the obtained lower limit routing distance to obtain an eighth routing distance, taking the obtained eighth routing distance as the survival time of a test data packet, determining a mobile terminal for receiving the test data packet according to the IP address and the UDP port of the mobile terminal, sending the test data packet to the mobile terminal, and judging whether a returned test response message is received or not;

if so, subtracting 1 from the route hop count of the eighth route distance obtained this time to serve as the updated upper limit route distance;

otherwise, subtracting 1 from the route hop count of the eighth route distance obtained this time, and then taking the route hop count as the updated lower limit route distance;

determining an eighth routing distance obtained when the upper limit routing distance is smaller than the lower limit routing distance, and adding 1 to the routing hop count of the eighth routing distance as the first routing distance if a test timeout message is received when the eighth routing distance is taken as the survival time of the test data packet; and if the message with correct test is received, taking the route hop count of the eighth route distance as the first route distance.

21. The method according to any one of claims 18 to 20, wherein determining the generated second routing distance based on the first routing distance comprises:

subtracting 1 from the route hop count of the first route distance to be used as the maximum value of the second route distance, and using the route hop count generated when the core network firewall is passed through as the minimum value of the second route distance;

and taking the route hop number which is not greater than the maximum value and not less than the minimum value as a second route distance.

22. A system for data transmission, comprising a mobile terminal, a gateway, an application server and a keep-alive device, wherein:

the mobile terminal is used for establishing a first long connection with the gateway and sending an uplink data message to the gateway through the first long connection, wherein the uplink data message carries an identifier of an application server, and the first long connection transmits the uplink data message generated by any application program in the mobile terminal;

the gateway is used for sending the uplink data message to the application server through a second long connection when the second long connection is established between the application servers corresponding to the identifiers of the application servers;

the application server is used for receiving the uplink data message through the second long connection;

and the keep-alive device is used for sending the heartbeat data packet to the mobile terminal by taking the set routing distance as the survival time of the heartbeat data packet aiming at the first long connection, wherein the routing distance is greater than the distance of the heartbeat data packet passing through the core network firewall but less than the distance of the heartbeat data packet reaching the wireless communication network where the mobile terminal is located.

23. A system for data transmission, the system comprising a mobile terminal, a gateway, an application server and a keep-alive device, wherein:

the application server is used for establishing a second long connection with the gateway and sending a downlink data message to the gateway through the second long connection, wherein the downlink data message carries a first identifier used when the mobile terminal is registered in the application server, and the second long connection transmits the downlink data message sent to any terminal by the application server;

the gateway is used for sending the downlink data message to the mobile terminal through first long connection between the mobile terminals corresponding to the first identification;

the mobile terminal is used for receiving the downlink data message through the first long connection;

and the keep-alive device is used for sending the heartbeat data packet to the mobile terminal by taking the set routing distance as the survival time of the heartbeat data packet aiming at the first long connection, wherein the routing distance is greater than the distance of the heartbeat data packet passing through the core network firewall but less than the distance of the heartbeat data packet reaching the wireless communication network where the mobile terminal is located.

24. A gateway, characterized in that the gateway comprises:

the first connection module is used for establishing a first long connection with the mobile terminal and establishing a second long connection with the application server, wherein the first long connection transmits an uplink data message generated by any application program in the mobile terminal, and the second long connection transmits a downlink data message sent to any terminal by the application server;

and the transmission module is used for transmitting the uplink data message to the corresponding application server through the second long connection according to the identification of the application server carried in the uplink data message when receiving the uplink data message transmitted by the mobile terminal through the first long connection in the uplink transmission process, and transmitting the downlink data message to the corresponding mobile terminal through the first long connection according to the first identification of the mobile terminal carried in the downlink data message when receiving the downlink data message transmitted by the application server through the second long connection in the downlink transmission process.

25. The gateway of claim 24, further comprising:

the route management module is used for judging whether a second long connection is established with an application server corresponding to an identification of the application server carried in an uplink data message or not in the uplink transmission process, inquiring other gateways which establish the second long connection with the corresponding application server from a DNS when the second long connection is not established, judging whether the mobile terminal is a locally registered mobile terminal or not in the downlink transmission process, and inquiring other gateways which the mobile terminal belongs to from the DNS when the mobile terminal is not the locally registered mobile terminal;

the transmission module is further configured to send the uplink data message or the downlink data message to the other gateways.

26. The gateway of claim 24, further comprising:

the proxy module is used for receiving a proxy request from the mobile terminal in the uplink transmission process, wherein the proxy request carries an identifier of an application server and a data volume of data to be transmitted, and when the data volume is determined to reach a threshold value, whether a second long connection is established with the corresponding application server or not is judged according to the identifier of the application server carried in the proxy request; in the downlink transmission process, an agent request from an application server is received, the agent request carries a first identifier of a mobile terminal and a data volume of data to be transmitted, and when the data volume reaches a threshold value, whether the corresponding mobile terminal is a locally registered mobile terminal is judged according to the first identifier carried in the agent request.

The second connection module is used for respectively establishing temporary long connections with the mobile terminal and the corresponding application server if the gateway establishes a second long connection with the corresponding application server in the uplink transmission process, receiving the data to be transmitted from the mobile terminal through the temporary long connections with the mobile terminal, releasing the temporary long connections with the mobile terminal after the transmission is finished, transmitting the data to be transmitted to the application server through the temporary long connections with the application server, and releasing the temporary long connections with the application server after the transmission is finished; otherwise, inquiring other gateways establishing second long connection with the corresponding application server from the DNS, respectively establishing temporary long connection with the mobile terminal and the other gateways, receiving the data to be transmitted from the mobile terminal through the temporary long connection with the mobile terminal, releasing the temporary long connection with the mobile terminal after the transmission is finished, transmitting the data to be transmitted to the other gateways through the temporary long connection with the other gateways, releasing the temporary long connection with the other gateways after the transmission is finished, respectively establishing temporary long connection with the corresponding mobile terminal and the application server sending the agent request if the corresponding mobile terminal is a locally registered mobile terminal in the downlink transmission process, and receiving the data to be transmitted from the application server through the temporary long connection with the application server, after the transmission is finished, releasing the temporary long connection with the application server, transmitting the data to be transmitted to the mobile terminal through the temporary long connection with the mobile terminal, and releasing the temporary long connection with the mobile terminal after the transmission is finished; otherwise, inquiring other gateways to which the corresponding mobile terminal belongs from the DNS, respectively establishing temporary long connections between the application server sending the agent request and the other gateways, receiving data to be transmitted from the application server through the temporary long connections between the application server and the other gateways, releasing the temporary long connections between the application server and the temporary long connections after the transmission is finished, transmitting the data to be transmitted to the other gateways through the temporary long connections between the data to be transmitted and the other gateways, and releasing the temporary long connections between the data to be transmitted and the other gateways after the transmission is finished.

27. A mobile terminal, characterized in that the mobile terminal comprises:

the interface module is used for establishing a first long connection with the gateway, and the first long connection transmits uplink data messages generated by any application program in the mobile terminal;

and the data receiving and sending module is used for sending an uplink data message to the gateway through the first long connection, wherein the uplink data message carries the identifier of the application server, and receiving a downlink data message pushed by the gateway through the first long connection.

28. The mobile terminal of claim 27, further comprising:

the proxy request module is used for sending a proxy request to the gateway, wherein the proxy request carries the identifier of the application server and the data volume of the data to be transmitted;

and the IP proxy module is used for sending the data to be transmitted to the gateway through the temporary long connection and receiving the data to be transmitted pushed by the gateway through the temporary long connection.

29. The mobile terminal of claim 27, further comprising:

the management module is used for recording the identification of the locally installed application program and the identification of the application server corresponding to each application program, determining the identification of the corresponding application server after receiving the uplink data message generated by any application program, and carrying the identification of the application server in the uplink data message;

the wake-up module is used for determining an application program for receiving the downlink data message according to an application server identifier carried in the downlink data message when the downlink data message is received, inquiring whether the application program is in a running state, and if so, informing the application program to acquire the downlink data message; otherwise, the application program is awakened or started, and the awakened or started application program is informed to acquire the downlink data message.

30. An application server, comprising:

the interface module is used for establishing a second long connection with the gateway, and the second long connection transmits a downlink data message sent to any terminal by the application server;

and the data receiving and sending module is used for receiving the uplink data message sent by the gateway through the second long connection and sending the downlink data message to the gateway through the second long connection, wherein the downlink data message carries a first identifier used when the mobile terminal is registered in the application server.

31. An application server according to claim 30,

the interface module is also used for establishing temporary long connection with the gateway;

the data receiving and transmitting module is also used for receiving and transmitting data to be transmitted through temporary long connection.

32. A keep-alive device, characterized in that the keep-alive device comprises:

the distance detection module is used for taking a set routing distance as the survival time of the heartbeat data packet, wherein the routing distance is greater than the distance of the heartbeat data packet passing through the firewall of the core network but less than the distance of the heartbeat data packet reaching the wireless communication network where the mobile terminal is located;

and the data packet sending module is used for sending the heartbeat data packet to the mobile terminal according to the survival time.

33. A keep-alive device as claimed in claim 32, wherein the distance detection module comprises:

the first routing determining module is used for sending a test data packet to the mobile terminal and determining a first routing distance generated when the test data packet is routed to the mobile terminal;

and the second routing determining module is used for determining a second routing distance generated when the test data packet passes through a firewall of a core network and reaches a one-hop routing before the wireless communication network where the mobile terminal is located according to the first routing distance, and taking the second routing distance as the set routing distance.

Images