WO2008067740A1

WO2008067740A1 - The method, system, terminal and apparatus for transferring message between terminals

Info

Publication number: WO2008067740A1
Application number: PCT/CN2007/070611
Authority: WO
Inventors: Zhihong Lian
Original assignee: Huawei Technologies Co., Ltd.
Priority date: 2006-12-05
Filing date: 2007-09-03
Publication date: 2008-06-12
Also published as: CN1996964A; CN100539553C

Abstract

A method for transferring message between terminals is disclosed, includes setting GDXS, setting GDXTS in the terminal; GDXTS thereof registering to GDXS after initiation; a source GDXTS receiving a request for connection and data switching from application inside terminal, sending to GDXS the request for transferring data; GDXS sending the application ID and data to be transferred in said request to the terminal of destination GDXTS after judging that the sail destination GDXTS is present according to received request; the destination GDXTS transferring the received data to the application corresponding to the application ID. Also a system, a terminal, a GDXS and a GDXTS for transferring data between terminals is disclosed. It makes data switch between stand-alone terminals free from constrain of domain, and it reduces developing cost for different platforms.

Description

Method, system, terminal and device for transmitting data between terminals

This application claims priority to Chinese Patent Application No. 200610161899.0, entitled "Methods, Systems and Terminals for Transferring Data between Terminals, GDXS and GDXTS" on December 5, 2006, the entire contents of which are filed on December 5, 2006. This is incorporated herein by reference. Technical field

The present invention relates to the field of communication technologies, and in particular, to a method, system, terminal and device for exchanging data between terminals.

Background technique

Various terminals, such as mobile terminals, fixed terminals, etc., often need to exchange data with other terminals. Currently, there are generally two methods: According to the exchange.

Infrared, Bluetooth and other technologies are limited by the technology itself. The range of connection is very limited, and it has a certain directivity, resulting in unstable connection, and hardware devices of different terminals are also different, and there is a matching problem.

Method 2: Use a dedicated server to implement data interaction. For example, the mobile terminal accesses through the General Data Packet Service (GPRS), communicates via the GPRS server, and exchanges data.

This method requires a dedicated server to interact. It is highly demanding on the server and needs to deal with network address translation (NAT) and private network traversal. On the terminal side, the network connection also needs to be processed, which increases the size and complexity of the software. Especially for terminals of different platforms, applications need to modify the underlying communication layer to increase development costs.

It can be seen that the data interaction between the existing stand-alone terminals is still not satisfactory.

Summary of the invention

The present invention provides a method, system, terminal and device for exchanging data between terminals, so that data exchange between the terminals of the single machine can avoid the limitation of the scope and reduce the development cost for different platforms.

The technical solution of the embodiment of the present invention includes:

A method for transmitting data between terminals, setting a general data exchange server GDXS, and setting a universal data exchange terminal server GDXTS in the terminal; after the terminal is started, the GDXTS therein is logged into the GDXS, and the method further comprises the following steps: The source GDXTS receives the connection and exchange data request from the application in the terminal, and sends a transmission data request to the GDXS, where the transmission data request includes an identifier of the application, an identifier of the at least one target GDXTS, and data to be transmitted;

The GDXS determines, according to the received request, that the target GDXTS is online, and sends the application identifier and the data to be transmitted in the request to the terminal where the target GDXTS is located;

The target GDXTS transmits the received data to the application corresponding to the application identifier.

A system for transmitting data between terminals, including a source terminal, a target terminal, and a universal data exchange server GDXS, wherein the source and target terminals include a GDXTS and an application module, where

The GDXTS in the source terminal is configured to receive a connection and exchange data request from the application module, and send an identifier including an application, an identifier of the at least one target GDXTS, and a transmission data request of the data to be transmitted to the GDXS;

The GDXS is configured to: after determining that the target GDXTS is logged in according to the received request, send the identifier of the application in the request and the data to be transmitted to the terminal where the target GDXTS is located;

The GDXTS in the target terminal is configured to receive data from the GDXS and transmit the data to the application corresponding to the application identifier.

A general data exchange server GDXS, including a GDXTS management module and a transmitting/receiving module, wherein

The GDXTS management module is configured to receive a registration and deregistration request from the GDXTS, receive a data forwarding request of the GDXTS, maintain a data transmission channel between at least two GDXTSs, and query whether a GDXTS is online;

The transmitting/receiving module is configured to send and receive data information with the GDXTS.

A terminal, comprising a universal data exchange terminal server GDXTS and an application module, wherein the application module is configured to send a connection and exchange data request to the GDXTS; and parse data from the GDXTS;

The GDXTS is configured to receive the request from an application module, send an identifier including an application, an identifier of at least one target GDXTS, and a transmission data request of the data to be transmitted to the GDXS; receive data from the GDXS, and transmit the data to the application module.

A data exchange terminal server GDXTS, comprising a registration/logout module, a data exchange module, a data exchange session management module, a sending/receiving module, wherein The registration/logout module is configured to complete registration and deregistration of the GDXTS itself on the GDXS through the sending/receiving module;

The data exchange module is configured to receive a connection and exchange data request of the application module, forward the request to the data exchange session management module, receive data transmitted from the data exchange session management module to the application module, and connect and exchange the data request Contains the identity of the application, the identity of at least one target GDXTS;

The data exchange session management module is configured to allocate a data exchange channel according to the received connection and exchange data request, and record a correspondence between the application identifier and the data channel, and send the identifier containing the application to the GDXS through the sending/receiving module. At least one target GDXTS identifier, and a data transmission request of the data to be transmitted; receiving data from the GDXS through the transmitting/receiving module, and transmitting the received data information to the data exchange module;

The transmitting/receiving module is configured to send and receive data information with the GDXS.

By applying the invention, the complexity of terminal application development is reduced, and the existing application in a single machine can be easily transformed into a network-connected application. At the same time, the limitation of the range between the single machines is avoided.

Furthermore, since multiple applications within a single machine can share one server, development costs are reduced. Through the GDXS on the network side and the GDXTS on the terminal, the application in the terminal can easily complete the traversal of the NAT and the private network to implement data exchange. The terminal does not need to consider the limitation of the network capability, and shields the difference between the operating system and the hardware device.

DRAWINGS

1 is a schematic structural diagram of a general data exchange server according to an embodiment of the present invention; FIG. 2 is a schematic structural diagram of a general data exchange terminal server according to an embodiment of the present invention; FIG. 3 is a schematic flowchart of implementing data transmission according to an embodiment of the present invention; ;

4 is a system for transferring data between terminals in accordance with an embodiment of the present invention.

detailed description

The invention will be further described in detail below with reference to the drawings and specific embodiments.

The present invention relates to a General Data Switch Server, hereinafter referred to as GDXS, and a General Data Switch Terminal Server (hereinafter referred to as GDXTS). GDXS is a stateless server that only completes GDXTS login and Data exchange between GDXTS. GDXTS is in the terminal and can be shared by one or more applications. The following description will be respectively made.

1 is a schematic structural diagram of a universal data exchange server according to an embodiment of the present invention, including a GDXTS management module (GDXTS Manager) 110 and a send/receive module (Send/Receive Module) 120, where

The GDXTS management module 110 is configured to receive a registration and deregistration request from the GDXTS, receive a data forwarding request from the GDXTS, maintain a data transmission channel between at least two GDXTSs, and query whether a GDXTS is online.

The transmit/receive module 120 is configured to transmit and receive data information with the GDXTS.

2 is a schematic structural diagram of a universal data exchange terminal server according to an embodiment of the present invention, including a registration/logout module (Login/Logout Module) 210, a data exchange module (DS, Data Switch) 240, and a data exchange session management module ( DSSM, Data Switch Session Manager 230, Send/Receive Module 220, where

The registration/logout module 210 is used to complete the registration and deregistration of the GDXTS itself on the GDXS through the transmitting and receiving module.

The data exchange module 240 is configured to receive the connection and exchange data request from the application module in the terminal, forward the request to the data exchange session management module 230, and receive the data from the data exchange session management module 230, and transmit the data to the application module. The connection and exchange data request includes an identifier of the application and an identifier of the at least one target GDXTS.

The data exchange session management module 230 is configured to allocate a data exchange channel according to the received connection and exchange data request, and record a correspondence between the application identifier and the data channel, and send, by the sending/receiving module 220, an identifier including the application to the GDXS, The identifier of the at least one target GDXTS, and the transmission data request of the data to be transmitted; receiving the data from the GDXS through the sending/receiving module 220, and transmitting the received data to the data exchange module 240 according to the saved correspondence relationship; The received data is transmitted to the corresponding application by the data exchange module 240.

The transmitting/receiving module 220 is configured to transmit and receive data information with the GDXS.

The data exchange session management module 230 is further configured to receive data from the GDXS, and determine that the application in the application module is started by the data exchange module 240 when the application corresponding to the application identifier is not started. The data exchange session management module 230 is further configured to: after receiving the data from the GDXS, return the reception response information to the sender GDXTS through the sending/receiving module.

GDXS and GDXTS are connected through a network, which can be based on GPRS, GSM, CDMA, etc., but is not limited thereto.

FIG. 3 is a schematic flow chart of implementing data transmission according to an embodiment of the present invention. In this embodiment, GDXTS is set in the terminal, the terminal 1 is the source terminal, the terminal 2 is the target terminal, the GDXTS in the terminal 1 is recorded as GDXTS 1, and the GDXTS in the terminal 2 is recorded as GDXTS2.

Step 301: After the terminal is started, the GDXTS in the UE initiates a login request to the GDXS. After the login is successful, the GDXS starts to respond to the GDXTS request. The terminal in this step includes the terminal 1 and the terminal 2.

Step 302: The application in the terminal 1 sends a connection and exchange data request to the GDXTS1, where the request includes an identifier of the application, an identifier of the at least one target GDXTS, and data to be transmitted. In this example, only the identifier of the target GDXTS is included, that is, The logo of GDXTS2.

Step 303: After receiving the request, the GDXTS1 sends a transmission data request to the GDXS, where the transmission data request includes an identifier of the application, an identifier of the at least one target GDXTS, and data to be transmitted. Similarly, only the identifier of the target GDXTS is included in this example. , that is, the logo of GDXTS2.

Step 304: The GDXS determines, according to the received request, that the GDXTS2 is online, and sends the application identifier and the data to be transmitted in the request to the terminal 2 where the GDXTS2 is located.

Step 305: The GDXTS2 transmits the received data to the application corresponding to the application identifier.

If the application corresponding to the received application identifier is not activated in the terminal 2, the method may further include: the GDXTS2 starts the application corresponding to the application identifier, and then transmits the received data to the application.

At this point, the transfer of data is completed. In the reverse direction, the terminal 2 can also send data to the terminal 1 through GDXTS2 to perform data exchange. The process is the same as the above, and will not be described again.

In step 303, the transmission data request sent by the GD X T S 1 to the GD X S may further include the identifier of the source GDXTS; thus, after the GDTXS2 receives the data from the GDXS, the method may further include: returning the reception response information to the GDXTS1 through the GDXS.

In the above step 304, if the GDXS determines that the GDXTS2 is not online after receiving the transmission data request, the GDXS returns a transmission failure information to the GDXTS1, and ends. The failure cause value may further be included in the transmission failure information. It can be seen that as long as GDXS determines that GDXTS2 is online, it is considered to have been Land registration, as long as GDXS determines that GDXTS2 is not online, it is considered to have been cancelled. GDXS determines whether there are many ways to use GDXTS2 online, such as through a timed handshake mechanism, etc. Here, the method for determining GDXS is not specifically limited.

The terminal 1 may be a mobile terminal or a fixed terminal. The terminal 2 may be a mobile terminal or a fixed terminal, and the types of the terminal 1 and the terminal 2 may be the same or different. The invention also discloses a system for transmitting data between terminals, referring to FIG. 4, including a source terminal, that is, a mobile terminal 1 (Mobilel) in FIG. 4, a target terminal, that is, a mobile terminal 2 (Mobile2) in FIG. 4, and a universal a data exchange server GDXS, and the source and target terminals include GDXTS and an application module (APP), wherein

The GDXTS in the source terminal is configured to receive a connection and exchange data request from the application module, and send an identifier containing the application, an identifier of the at least one target GDXTS, and a transmission data request of the data to be transmitted to the GDXS;

The GDXS is configured to, according to the received request, determine that the target GDXTS is logged in, and send the identifier of the application in the request and the data to be transmitted to the terminal where the target GDXTS is located; the structure of the GDXS is shown in FIG.

The GDXTS in the target terminal is used to receive data from the GDXS and transmit it to the application corresponding to the application identifier.

If the application corresponding to the received application identifier is not activated in the terminal where the target GDXTS is located, the GDXTS of the target terminal is further used to start an application corresponding to the application identifier in the application module, and transmit the received data to the application. .

If the GDXS determines that the target GDXTS is not online according to the received request, the GDXS is also used to return a transmission failure message to the source GDXTS.

If the source GDXTS sends a transmission data request to the GDXS, the source GDXTS identifier is also included; then, after receiving the data from the GDXS, the target GDTXS is also used to return the reception response information to the source GDXTS through the GDXS.

The invention also discloses a terminal, comprising a GDXTS and an application module, wherein

The application module is configured to send a connection and exchange data request to the GDXTS; parse and receive data from the GDXTS; The GDXTS is configured to receive the request from the application module, send an identifier containing the application, an identifier of the at least one target GDXTS, and a transmission data request of the data to be transmitted to the GDXS; receive the data from the GDXS, and transmit the data to the application module.

The GDXTS receives the data from the GDXS, and determines that the application in the application module is started when the application corresponding to the application identifier is not started.

The GDTXS is also used to return the receipt response information to the source GDXTS via GDXS after receiving the data from the GDXS.

See Figure 2 for the structure of the above GDXTS.

The above terminal may be a mobile terminal or a fixed terminal.

It can be seen that the application on the terminal interacts with the other server through the single server and the network side server on the terminal, exchanges data with another terminal, exchanges data through a single server, shields the difference between the operating system and the hardware device, reduces the cost, and avoids the The limits of the scope.

The above description is only the preferred embodiment of the present invention and is not intended to limit the scope of the present invention. Any modifications, equivalents, improvements, etc. made within the spirit and scope of the invention are intended to be included within the scope of the invention.

Claims

Rights request

A method for transmitting data between terminals, the method comprising the steps of: the source GDXTS receiving a connection and an exchange data request from an application in the terminal, and transmitting a transmission data request to the GDXS, wherein the transmission data request includes an application. Identification, at least one identity of the target GDXTS, and data to be transmitted;

The method according to claim 1, wherein if the application corresponding to the received application identifier is not activated in the terminal where the target GDXTS is located, the method further includes:

The target GDXTS starts the application corresponding to the application identifier, and then transmits the received data to the application.

The method according to claim 1, wherein if the GDXS determines that the target GDXTS is not online according to the received request, the method further includes:

The GDXS returns a transmission failure message to the source GDXTS, and ends.

The method according to claim 1 or 2, wherein the transmission data request sent by the source GDXTS to the GDXS further includes an identifier of the source GDXTS;

After receiving the data from the GDXS, the target GDTXS further includes: returning the receiving response information to the source GDXTS through the GDXS.

5. The method of claim 1 wherein:

The terminal where the source GDXTS is located is a mobile terminal, or a fixed terminal;

The terminal where the target GDXTS is located is a mobile terminal, or a fixed terminal.

A system for transmitting data between terminals, comprising: a source terminal, a target terminal, a universal data exchange server GDXS, and the source and target terminals each include a GDXTS and an application module, wherein

The GDXS is configured to determine, after the target GDXTS is logged in, according to the received request, Sending the identifier of the application and the data to be transmitted in the request to the terminal where the target GDXTS is located; the GDXTS in the target terminal is configured to receive data from the GDXS and transmit the data to the application corresponding to the application identifier.

The system according to claim 6, wherein, if the application corresponding to the received application identifier is not activated in the terminal where the target GDXTS is located,

The GDXTS of the target terminal is further configured to start an application corresponding to the application identifier in the application module, and then transmit the received data to the application.

The system according to claim 6, wherein if the GDXS determines that the target GDXTS is not online according to the received request,

The GDXS is also used to return transmission failure information to the source GDXTS.

The system according to claim 6, wherein the source GDXTS further includes an identifier of the source GDXTS in the transmission data request sent to the GDXS;

After receiving the data from GDXS, the target GDTXS is also used to return the receiving response information to the source GDXTS through GDXS.

A general data exchange server GDXS, comprising: a GDXTS management module and a transmitting/receiving module, wherein

A terminal, comprising: a universal data exchange terminal server GDXTS and an application module, wherein

The application module is configured to send a connection and exchange data request to the GDXTS; and parse and receive data from the GDXTS;

The GDXTS, configured to receive the request from an application module, send an identifier including an application, an identifier of at least one target GDXTS, and a transmission data request of the data to be transmitted to the GDXS; receive data from the GDXS, and transmit the data to the application Module.

The terminal according to claim 11, wherein the GDXTS is further configured to receive data from the GDXS, and determine that an application corresponding to the application identifier is not started, and the startup should be Use the application described in the module.

The terminal according to claim 11, wherein the GDTXS is further configured to: after receiving the data from the GDXS, return the reception response information to the source GDXTS through the GDXS.

The terminal according to claim 11, wherein the terminal is a mobile terminal or a fixed terminal.

A data exchange terminal server GDXTS, comprising: a registration/logout module, a data exchange module, a data exchange session management module, and a sending/receiving module, wherein

The registration/logout module is configured to complete the registration and cancellation of the GDXTS itself on the GDXS through the sending/receiving module;

The data exchange session management module is configured to allocate a data exchange channel according to the received connection and exchange data request, and record a correspondence between the application identifier and the data channel, and send the application to the GDXS through the sending/receiving module. The identifier, the identifier of the at least one target GDXTS, and the transmission data request of the data to be transmitted; receiving the data from the GDXS through the sending/receiving module, and transmitting the received data information to the data exchange module;

The GDXTS according to claim 15, wherein the data exchange session management module is further configured to receive data from the GDXS, and determine that the application corresponding to the application identifier is not started, and the data is passed. The switch module launches the application within the application module.

The GDXTS according to claim 15, wherein the data exchange session management module is further configured to: after receiving the data from the GDXS, return the reception response information to the sender GDXTS through the transmitting/receiving module.