CN113259732A

CN113259732A - Data transmission method

Info

Publication number: CN113259732A
Application number: CN202010082574.3A
Authority: CN
Inventors: 刘名扬; 李文; 李孟伟; 张伟; 黄鹏; 许益章
Original assignee: China Telecom Corp Ltd
Current assignee: China Telecom Corp Ltd
Priority date: 2020-02-07
Filing date: 2020-02-07
Publication date: 2021-08-13
Anticipated expiration: 2040-02-07
Also published as: CN113259732B

Abstract

The invention relates to a method of data transmission, comprising a first device sending a data transmission request for a second device to a server via a first network, wherein the data transmission request comprises an identification of the second device; the server inquires corresponding second equipment according to the received identifier; and the server establishes connection with the second equipment through a second network and transmits data to the second equipment according to the data transmission request.

Description

Data transmission method

Technical Field

The present disclosure relates to the field of communications, and more particularly, to a method, a server, a non-transitory computer-readable storage medium, and a system for data transmission of multiple network planes.

Background

With the introduction and development of the telecommunication industry, a new generation telecommunication network based on an Internet Protocol Television (IPTV) network can provide a variety of multimedia information services, and has a wide application prospect in various fields such as video on demand, remote education, electronic commerce, remote medical treatment, and the like. In these application scenarios, a user generally desires to use a terminal device (e.g., a mobile phone, a smart wearable device, etc.) in possession to implement cross-screen interaction of an IPTV device (e.g., an IPTV set-top box) and a display device connected to the IPTV device, for example, to control the IPTV device or play multimedia content via the IPTV device.

However, since the IPTV network and a network (e.g., Wifi network, LTE network, etc.) used by a terminal device held by a user do not belong to the same network plane, the local area network pairing technology (e.g., DLNA, airlay, Miracast) adopted by the conventional television box cannot be applied to the IPTV network scenario. In addition, existing local area network pairing techniques all use a long connection mode (i.e., after both communication parties establish a connection and transmit data, the connection is still maintained), so that overhead of a system and a communication channel is large.

Therefore, a new method for data transmission of multiple network planes is needed.

Disclosure of Invention

The following presents a simplified summary of the disclosure in order to provide a basic understanding of some aspects of the disclosure. However, it should be understood that this summary is not an exhaustive overview of the disclosure. It is not intended to identify key or critical elements of the disclosure or to delineate the scope of the disclosure. Its sole purpose is to present some concepts of the disclosure in a simplified form as a prelude to the more detailed description that is presented later.

According to one aspect of the present disclosure, there is provided a method of data transmission, comprising a first device sending a data transmission request for a second device to a server via a first network, wherein the data transmission request comprises an identification of the second device; the server inquires corresponding second equipment according to the received identifier; and the server establishes connection with the second equipment through a second network and transmits data to the second equipment according to the data transmission request.

According to another aspect of the present disclosure, there is provided a method of data transmission, comprising receiving, via a first network, a data transmission request from a first device for a second device, wherein the data transmission request comprises an identification of the second device; inquiring corresponding second equipment according to the received identifier; and establishing connection with the second device via the second network, and transmitting data to the second device according to the data transmission request.

According to another aspect of the present invention, there is provided a server for data transmission, the server comprising: one or more processors; and one or more memories configured to store a series of computer-executable instructions, wherein the series of computer-executable instructions, when executed by the one or more processors, cause the one or more processors to perform the method as described above.

According to another aspect of the invention, there is provided a non-transitory computer-readable medium having stored thereon computer-executable instructions which, when executed by one or more processors, cause the one or more processors to perform a method as described above.

Other features of the present disclosure and advantages thereof will become more apparent from the following detailed description of exemplary embodiments thereof, which proceeds with reference to the accompanying drawings.

Drawings

The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments of the disclosure and together with the description, serve to explain the principles of the disclosure.

The present disclosure may be more clearly understood from the following detailed description, taken with reference to the accompanying drawings, in which:

fig. 1 is a diagram showing a configuration example of a data transmission system according to an exemplary embodiment of the present invention.

Fig. 2 is an exemplary flowchart illustrating a method of data transmission according to an exemplary embodiment of the present invention.

Fig. 3 is a detailed flowchart illustrating a method of data transmission according to an exemplary embodiment of the present invention.

Fig. 4 is a detailed sequence diagram illustrating a method of data transmission according to an exemplary embodiment of the present invention.

Fig. 5 is an exemplary configuration diagram illustrating a computing device in which embodiments in accordance with the invention may be implemented.

Note that in the embodiments described below, the same reference numerals are used in common between different drawings to denote the same portions or portions having the same functions, and a repetitive description thereof will be omitted. In some cases, similar reference numbers and letters are used to denote similar items, and thus, once an item is defined in one figure, it need not be discussed further in subsequent figures.

For convenience of understanding, the positions, sizes, ranges, and the like of the respective structures shown in the drawings and the like do not sometimes indicate actual positions, sizes, ranges, and the like. Therefore, the present disclosure is not limited to the positions, dimensions, ranges, and the like disclosed in the drawings and the like.

Detailed Description

Various exemplary embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings. It should be noted that: the relative arrangement of the components and steps, the numerical expressions, and numerical values set forth in these embodiments do not limit the scope of the present disclosure unless specifically stated otherwise.

The following description of at least one exemplary embodiment is merely illustrative in nature and is in no way intended to limit the disclosure, its application, or uses. That is, the structures and methods herein are shown by way of example to illustrate different embodiments of the structures and methods of the present disclosure. Those skilled in the art will understand, however, that they are merely illustrative of exemplary ways in which the disclosure may be practiced and not exhaustive. Furthermore, the figures are not necessarily to scale, some features may be exaggerated to show details of particular components.

The present disclosure proposes that the first device sends a data transfer request for the second device to the server via the first network, wherein the data transfer request comprises an identification of the second device. Then, the server queries the corresponding second device according to the received identifier. Then, the server establishes a connection with the second device via the second network, and transmits data to the second device according to the data transmission request.

Compared with the traditional cross-screen data transmission method, the first device (for example, a mobile phone held by a user) and the second device (for example, an IPTV set-top box) in the technical scheme of the disclosure do not need to be in the same local area network. And compared with a method of data transmission requiring continuous maintaining connection (i.e. long connection), the technical scheme of the present disclosure can reduce the overhead of the system and the communication channel.

Fig. 1 is an example illustrating a data transmission system 100 including a first device, a second device, and a server. As shown in fig. 1, the system 100 may include a first device UE1, a server 110, a second device 120, and a display device 130, wherein the server 110 may include a processing unit 112, a storage unit 114, a first network interface 116, and a second network interface 118. In the data transmission system 100, the first device UE1 communicates with the first network interface 116 of the server 110 via a first network, and the second device 120 communicates with the second network interface 118 of the server 110 via a second network. In addition, the second device 120 may communicate with the display device 130 for data transmission and control.

In some embodiments, the server 110 may comprise a single web server, a server group of multiple web servers, or a cloud of numerous computers or web servers. The first network may comprise a network that wirelessly communicates using one or more of a cellular system, a wireless local area technology. The second network may include an IPTV network, a private network, an intranet, or the like, a wired or wireless network different from the first network. The first device UE1 may be a terminal device held by a user, including but not limited to a tablet, a smart phone, a smart wearable device, a PDA, a computer, and so on. The second device may be an IPTV device, a smart tv set-top box, etc. The display device may be a television, a display, a projector, etc. Note that although a separate second device 120 and display device 130 are shown in fig. 1, the second device 120 and display device 130 may be integrated in one smart display device, such as an IPTV television or smart television.

Fig. 2 is an exemplary flow chart illustrating a method 200 of data transmission according to one exemplary embodiment of the invention. As shown in fig. 2, the method 200 of data transmission may include: a data transmission requesting step 110, a querying step 120 and a connection establishing step 130. Wherein the method 200 may be performed by a data transmission system 100 as shown in fig. 1.

First, in a data transfer request step 210, the first device UE1 sends a data transfer request for the second device 120 to the server 110 via the first network. Wherein the data transmission request includes an identification of the second device 120 that can uniquely identify the second device 120. Processing then proceeds to step 220.

In some embodiments, the identification of the second device 120 may include an IP address, a MAC address, an identification code of the second device 120 in the second network, a model number of the second device, an account number of the second device, and the like. However, the identification of the second device 120 is not limited thereto, and any information that can uniquely identify the second device may be used as the identification of the second device.

In some embodiments, the first device UE1 obtains the identity of the second device 120 in advance. For example, a two-dimensional code or barcode may be provided at the second device 120, and the first device UE1 obtains the identity of the second device 120 by scanning the two-dimensional code or barcode. In some embodiments, where the first device UE1 has previously acquired the identities of the plurality of second devices 120, a prompt may be given at the first device UE1 that the identities of the plurality of second devices 120 are present so that the user may select the second device 120 that he wants to transmit data.

In some embodiments, the data transfer request sent to the processor 110 includes, in addition to the identification of the second device 120, a control request and/or a content playback request for the second device 120, e.g., remote control, live broadcast, on demand, voice recognition, jump link, etc.

At query step 220, the server 110 queries the corresponding second device 120 according to the received identifier, and the second device 120 will be the executing party of the data transmission process. Subsequently, the process proceeds to step 230.

In some embodiments, after querying the corresponding second device 120, the server 110 may further determine whether the second device 120 may perform data transmission based on the heartbeat information sent by the second device 120 in the standby phase, which will be described in detail below with reference to fig. 3. The heartbeat information refers to information sent between the client (e.g., the second device) and the server in a time range in which no service information is transmitted, so as to inform the server of the online \ available state of the server.

At step 230, the server 110 establishes a connection with the queried second device 120 via the second network and transmits data to the second device 120 according to the previously received data transmission request. In some embodiments, in the case where the data transmission request includes a control request for the second device 120, control may be performed on the second device 120; where the data transmission request includes a content play request for the second device 120, the content may be played on the second device 120 (e.g., where the second device 120 includes a display unit) or on a display device 130 in communication with the second device 130. In some embodiments, the second device 120 listens for a connection establishment request from the server 110 via the second network and closes the connection after the data transfer is complete.

Based on the technical solution of the method 100, when the first device 110 and the second device 120 are in different networks, the data transmission can still be completed. Compared with the traditional long connection mode, the connection is established only when a data transmission request is received, and the data channel is prevented from being occupied. In addition, since the second device 120 monitors the connection establishment request from the server 110 via the second network and responds, it is possible to save processing pressure on the server side and improve the stability of the entire system.

A specific embodiment according to the present invention will be described below with reference to fig. 3. Fig. 3 is a detailed flow diagram illustrating a method 300 of data transmission including heartbeat status determination of a second device according to an example embodiment of the present invention. Wherein the method 300 may be performed by a data transmission system 100 as shown in fig. 1.

First, at step 310, the second device 120 periodically transmits heartbeat information to the server 110 via the second network, wherein the heartbeat information may include an identification of the second device 120. Specifically, the second device 120 immediately transmits heartbeat information to the server 110 when being powered on, and then transmits heartbeat information to the server 110 once at predetermined intervals. The server 110 may continuously listen for receiving heartbeat information from the second device 120. When the heartbeat information transmission fails (e.g., due to a network failure), the second device 120 will retransmit the heartbeat information after a short time interval (e.g., 1 minute). When the server 110 does not receive the heartbeat information transmitted from the second device 120 after a predetermined period, the heartbeat information is judged to be invalid. In some implementations, the heartbeat information can include a timestamp based on the time that the heartbeat information was sent in addition to the identification of the second device 120. Subsequently, the process proceeds to step 320.

At step 320, the server 110 stores the received heartbeat information. Specifically, the server first identifies the identity of the second device 120 in the heartbeat information and overwrites the received heartbeat information with the previous heartbeat information corresponding to the identity. In some implementations, the server 110 also stores the time at which the heartbeat information was received in association with the heartbeat information. In other embodiments, since the heartbeat information has a timestamp in addition to the identification of the second device 120, the server 110 may store the identification of the second device 120 and the timestamp directly in the storage unit 114 without processing it. Subsequently, the process proceeds to step 330.

At step 330, the first device UE1 sends a data transfer request for the second device 120 to the server 110 via the first network. At step 340, the server 110 queries the corresponding second device 120 according to the received identification.

Steps

330, 340 correspond to

steps

210, 220 in method 200, and repeated detailed description thereof is omitted for the sake of brevity. Subsequently, the process proceeds to step 350.

At step 350, after querying the corresponding second device 120 according to the received identifier, the server 110 determines whether the data transmission is possible according to whether the heartbeat information of the second device stored in the storage unit 114 is valid. Specifically, whether the heartbeat information is valid is determined according to a preset time interval for updating the heartbeat information. In the case where the heartbeat information is valid, the process proceeds to step 360. In the case where the heartbeat information fails, the process proceeds to step 370.

At step 360, the server 110 establishes a connection with the queried second device 120 via the second network and transmits data to the second device 120 according to the previously received data transmission request. Step 360 corresponds to step 230 of method 200, and repeated detailed description thereof is omitted for brevity.

At step 370, the server 110 provides a prompt to the first device UE1 via the first network for a data transfer failure. In some embodiments, the prompt for a data transfer failure provided to the first device UE1 via the first network includes error information and error codes of the second device and possibly a processing policy for selection by the user. For example, in the event that the heartbeat information fails (e.g., because of a timeout), a processing policy may be given to the user at the first device (e.g., "reboot the second device"), with the corresponding processing being performed online by the user (e.g., reboot the second device by the user).

In order to more clearly and clearly embody the method flow of the present invention, a specific embodiment of the present invention, which takes the mobile phone to project the screen of the IPTV system as an example, will be described below with reference to fig. 4. Fig. 4 is a detailed sequence diagram illustrating a data transmission method according to an exemplary embodiment of the present invention. According to one embodiment of the present invention, the above steps are performed at a first device (e.g., a user handset), a second device (e.g., an IPTV set-top box device), and a server (e.g., an IPTV server), wherein the handset communicates with the IPTV server via a wireless local area network or a cellular network, and the set-top box communicates with the IPTV server via the IPTV network.

First, in step S401, the user handset acquires the identifier of the set-top box in advance in an offline manner. For example, according to a prompt given by an application, the mobile phone number and the account number of the set-top box are bound by scanning a two-dimensional code on the set-top box through the application installed in the mobile phone, so that the identifier of the set-top box is stored in the application. As described above, the identifier may be an IP address, a MAC address, a model number of the set-top box, a device identification code of the set-top box, an IPTV account number, and the like of the set-top box in the IPTV network.

At step S402, the set-top box periodically transmits heartbeat information with the set-top box identifier to the IPTV server. At step S403, the set-top box stores the received heartbeat information. Note that in the standby phase of the set-top box, the set-top box and the server may repeat steps S402 and S403 periodically. The period of sending the heartbeat information may be set based on the stress of the server, and for example, the heartbeat information may be set to be sent every four hours.

It will be understood by those skilled in the art that although step S401 is drawn in fig. 4 followed by steps S402 and S403, this is merely an example and is not intended to limit the present invention. As described above, in some embodiments, steps S402 and S403 in the standby phase may be periodically executed at regular time, and step S401 occurring offline may be executed at any time according to needs, and the two steps are not necessarily in order, and may also be executed simultaneously.

Subsequently, in the interaction phase, when the user needs to perform data transmission, the user handset sends a data transmission request to the IPTV server via a wireless communication network (e.g., Wifi or cellular network) (step S410). In some embodiments, the data transfer request may include an identification of the set top box that desires to interact and a request for an operation that is desired to be performed. For example, the data transmission request may include an identification of "IPTV set-top box in living room" and a content play request of "play a movie on screen" or a control request of "manipulate an IPTV set-top box with a cell phone as a remote controller". Subsequently, the process proceeds to step S411.

At step S411, the server queries the corresponding set-top box and the heartbeat information status thereof according to the received data transmission request. Specifically, if the update time of the heartbeat information of the corresponding set-top box is less than a predetermined period (for example, four hours), the heartbeat information is determined to be valid, otherwise, the heartbeat information is determined to be invalid. In the case where the heartbeat information is valid, the processing proceeds to step S413.

At step S413, the server transmits a request for connection establishment to the set-top box via the IPTV network. Note that the set-top box keeps listening for connection establishment requests from the server. At step S414, the set-top box responds to the connection establishment request.

Upon receiving the response from the set-top box, the server establishes a connection with the set-top box via the IPTV network and transmits data to the set-top box according to the previously received data transmission request at step S415.

At steps S416 and S417, the set-top box returns the result of the data transmission (e.g., "screen-casting success" or "the set-top box in living room is playing ' a ' program", etc.) to the server and transparently passes it to the user ' S handset via the server.

In the case where the heartbeat information is invalid, the process proceeds to step S414. At step S414, the server provides a prompt to the handset that the data transfer failed. In some embodiments, as described above, the server further sends the reason for the failure of data transmission with the set-top box and the corresponding processing policy to the mobile phone, so as to facilitate the user to select the corresponding processing for the set-top box offline.

FIG. 5 illustrates an exemplary configuration of a computing device 2000, in which embodiments in accordance with the invention may be implemented. Computing device 2000 is an example of a hardware device in which the above-described aspects of the invention may be applied. Computing device 2000 may be any machine configured to perform processing and/or computing. The computing device 2000 may be, but is not limited to, a workstation, a server, a desktop computer, a laptop computer, a tablet computer, a Personal Data Assistant (PDA), a smart phone, an in-vehicle computer, or a combination thereof. The aforementioned server 110 may be implemented in whole or at least in part by the aforementioned computing device 2000 or a device or system similar thereto.

As shown in fig. 5, computing device 2000 may include one or more elements connected to or in communication with bus 2002, possibly via one or more interfaces. For example, computing device 2000 may include a bus 2002, one or more processors 2004, one or more input devices 2006, and one or more output devices 2008. Bus 2002 may include, but is not limited to, an Industry Standard Architecture (ISA) bus, a Micro Channel Architecture (MCA) bus, an enhanced ISA (eisa) bus, a Video Electronics Standards Association (VESA) local bus, and a Peripheral Component Interconnect (PCI) bus, among others. The one or more processing devices 2004 can be any kind of processor and can include, but are not limited to, one or more general-purpose processors or special-purpose processors (such as special-purpose processing chips). Input device 2006 may be any type of input device capable of inputting information to a computing device and may include, but is not limited to, a mouse, a keyboard, a touch screen, a microphone, and/or a remote control. Output device 2008 may be any type of device capable of presenting information and may include, but is not limited to, a display, speakers, a video/audio output terminal, a vibrator, and/or a printer. The computing device 2000 may also include or be connected to a non-transitory storage device 2010, which non-transitory storage device 2010 may be any non-transitory and may implement a data storage device, and may include, but is not limited to, a disk drive, an optical storage device, a solid state memory, a floppy disk, a flexible disk, a hard disk, a magnetic tape, or any other magnetic medium, a compact disk, or any other optical medium, a ROM (read only memory), a RAM (random access memory), a cache memory, and/or any other memory chip or unit, and/or any other medium from which a computer may read data, instructions, and/or code. The non-transitory storage device 2010 may be removably connected with any interface. The non-transitory storage device 2010 may have stored thereon data/instructions/code for implementing the aforementioned methods and/or steps for consensus in a blockchain network. Computing device 2000 may also include a communication device 2012, which communication device 2012 may be any kind of device or system capable of enabling communication with external devices and/or networks and may include, but is not limited to, modems, network cards, infrared communication devices, wireless communication devices, and/or chipsets (such as 1302.11 devices, WiFi devices, WiMax devices, cellular communication facilities, and the like).

The computing device 2000 may also include a working memory 2014. The working memory 2014 may be any type of working memory capable of storing instructions and/or data useful to the processor 2004 and may include, but is not limited to, Random Access Memory (RAM) and Read Only Memory (ROM).

The software elements located on the above-described working memory may include, but are not limited to, an operating system 2016, one or more application programs 2018, drivers, and/or other data and code. One or more of the applications 2018 may include instructions for performing the methods and steps for identifying named entities as described above. The various components/units/elements of the aforementioned data transmission system 100, such as the first device UE1, the processing unit 112 in the server 110, the second device 120, etc., may be implemented by a processor that reads and executes one or more application programs 2018. Executable code or source code of the instructions of the software elements may be stored in a non-transitory computer-readable storage medium (such as storage device 2010 as described above) and may be read into working memory 2014 by compilation and/or installation. Executable or source code for the instructions of the software elements may also be downloaded from a remote location.

It will be appreciated that variations may be made in accordance with specific requirements. For example, customized hardware might be used and/or particular elements might be implemented in hardware, software, firmware, middleware, microcode, hardware description languages, or any combination thereof. In addition, connections to other computing devices (such as network input/output devices) may be employed. For example, some or all of the methods and apparatus of the present invention may be implemented in accordance with the present invention by a hardware programming language (e.g., VERILOG, VHDL, C + +) using assembly language programming hardware (e.g., programmable logic circuits including Field Programmable Gate Arrays (FPGAs) and/or Programmable Logic Arrays (PLAs)) or logic and algorithms.

It should be further understood that the elements of computing device 2000 may be distributed throughout a network. For example, some processes may be performed using one processor while other processes are performed using other remote processors. Other elements of the computer system 2000 may be similarly distributed. Thus, the computing device 2000 may be understood as a distributed computing system that performs processing at multiple sites.

The method and apparatus of the present invention can be implemented in a number of ways. For example, the methods and apparatus of the present invention may be implemented in software, hardware, firmware, or any combination thereof. The order of the method steps described above is merely illustrative and the method steps of the present invention are not limited to the order specifically described above unless explicitly stated otherwise. Furthermore, in some embodiments, the present invention may also be embodied as a program recorded in a recording medium, which includes machine-readable instructions for implementing a method according to the present invention. Thus, the present invention also covers a recording medium storing a program for implementing the method according to the present invention.

While some specific embodiments of the present invention have been shown in detail by way of example, it should be understood by those skilled in the art that the foregoing examples are intended to be illustrative only and are not intended to limit the scope of the invention. It will be appreciated by those skilled in the art that the above-described embodiments may be modified without departing from the scope and spirit of the invention. The scope of the invention is defined by the appended claims.

Claims

1. A method of data transmission comprising

The method comprises the steps that a first device sends a data transmission request aiming at a second device to a server through a first network, wherein the data transmission request comprises an identification of the second device;

the server inquires corresponding second equipment according to the received identifier; and

the server establishes connection with the second device through the second network and transmits data to the second device according to the data transmission request.

2. The method of claim 1, further comprising:

the second device periodically sends heartbeat information to the server through a second network, wherein the heartbeat information has the identification of the second device; and

the server stores the heartbeat information.

3. The method of claim 2, further comprising:

when receiving a data transmission request from the first device, the server determines whether data transmission is possible according to whether the heartbeat information of the second device is effective.

4. The method of claim 2, further comprising upon determining that the status of the second device is invalid for heartbeat information, the server providing a prompt to the first device via the first network for a failure of data transfer.

5. The method of claim 1, wherein the data transfer request further comprises one or more of a control request and a content playback request to the second device.

6. The method of claim 1, further comprising the first device obtaining the identification of the second device by utilizing one or more of two-dimensional codes on the second device, offline viewing, and background auto-injection.

7. The method of claim 1, wherein the identification further comprises at least one of an IP address, a MAC address, a model number of the second device, and an identification code of the second device in the second network.

8. The method of claim 1, wherein the second network comprises an IPTV network and the first network comprises a network that wirelessly communicates using one or more of a cellular system, a wireless local area technology.

9. A method of data transmission comprising

Receiving, via a first network, a data transmission request from a first device for a second device, wherein the data transmission request includes an identification of the second device;

inquiring corresponding second equipment according to the received identifier; and

and establishing connection with the second equipment through the second network, and transmitting data to the second equipment according to the data transmission request.

10. The method of claim 9, further comprising:

periodically receiving, via a second network, heartbeat information from a second device, the heartbeat information having an identification of the second device; and

and storing the heartbeat information.

11. The method of claim 10, further comprising:

and when receiving a data transmission request from the first equipment, determining whether the data transmission is possible according to whether the heartbeat information of the second equipment is effective.

12. The method of claim 10, further comprising providing a prompt to the first device via the first network for a failure of the data transfer upon determining that the status of the second device is invalid for the heartbeat information.

13. The method of claim 9, wherein the data transfer request further comprises one or more of a control request and a content playback request to the second device.

14. The method of claim 9, wherein the identification comprises at least one of an IP address, a MAC address, a model number of the second device, and an identification code of the second device in the second network.

15. The method of claim 9, wherein the second network comprises an IPTV network and the first network comprises a network that wirelessly communicates using one or more of a cellular system, a wireless local area technology.

16. A server for data transmission, comprising:

one or more processors; and

one or more memories configured to store a series of computer-executable instructions,

wherein the series of computer-executable instructions, when executed by the one or more processors, cause the one or more processors to perform the method of any one of claims 9-15.

17. A non-transitory computer readable storage medium, on which a program is stored, wherein the program, when executed by a processor, implements the steps of the method of any one of claims 9-15.

18. A system for data transmission, comprising:

a first device, a second device, and the processor of claim 16, wherein the first device communicates with the server via a first network and the second device communicates with the server via a second network.