WO2020063086A1

WO2020063086A1 - Data transmission method based on internet of things, and communication apparatus

Info

Publication number: WO2020063086A1
Application number: PCT/CN2019/098059
Authority: WO
Inventors: 何国洲
Original assignee: 华为技术有限公司
Priority date: 2018-09-26
Filing date: 2019-07-27
Publication date: 2020-04-02
Also published as: CN110958281B; CN110958281A

Abstract

Provided are a data transmission method based on the Internet of Things, and a communication apparatus, the method involving: for a specific third-party application, an application layer device performing signaling interaction with an Internet-of-Things platform to establish N long connections, and sending first data to the Internet-of-Things platform based on the N long connections, or receiving, based on the N long connections, second data regarding the third-party application and sent by the Internet-of-Things platform. In this process, for a third-party application, the N long connections are established between the application layer device and the Internet-of-Things platform, and the N long connections of different third-party applications are different, such that the various third-party applications do not affect each other when the Internet-of-Things platform pushes data to the third-party applications on an application layer terminal device. In addition, there are multiple long connections, and therefore, compared with one long connection, the plurality of long connections can improve the real-time performance of data pushing.

Description

Data transmission method and communication device based on internet of things

This application claims the priority of a Chinese patent application filed on September 26, 2018 with the State Intellectual Property Office of China, with an application number of 201811126917.0, and an application name of "Data Transmission Method and Communication Device Based on the Internet of Things", the entire contents of which are incorporated by reference Incorporated in this application.

Technical field

The embodiments of the present application relate to the technical field of the Internet of Things, and in particular, to a data transmission method and a communication device based on the Internet of Things.

Background technique

The Internet of Things (IoT) is an important part of the new generation of information technology, which refers to the Internet connected to things. From the perspective of technical architecture, the Internet of Things includes a perception layer, an IoT platform, and an application layer. Among them, the perception layer includes sensor gateways, sensors, and other sensing layer terminal devices for collecting information. The Internet of Things platform is responsible for storing, transmitting, and Processes the information collected by the terminal devices at the perception layer; the application layer includes application layer devices, which mainly provide data analysis, control, and human-machine interfaces for the Internet of Things. During the data transmission process, the sensing layer terminal device collects data and reports it to the IoT platform. The IoT platform transmits the data to the application layer terminal device. The user uses a third-party application loaded on the application layer terminal device to implement data query and data Analysis, etc.

In the prior art, after receiving the data reported by the terminal device at the perception layer, the IoT platform pushes the data to a third-party application loaded on the application layer device through a Hypertext Transfer Protocol (HTTP) push method. Specifically, the HTTP push method includes a synchronous HTTP push method and an asynchronous HTTP push method. In the synchronous HTTP push method, the application-layer terminal device sends an HTTP request to the IoT platform to request a callback address based on the short connection. Then, the IoT platform pushes the data to the third-party application on the application-layer terminal device through the callback address. . In this process, each time the IoT platform sends data to the application-level terminal device, it is necessary for the application-level terminal device to send an HTTP request to apply for a resource (that is, a callback address), and release the resource after the data is sent. For a third-party application, the third-party application does not occupy the resource all the time, which causes the third-party applications to interact with each other when the IoT platform pushes data to different third-party applications. In extreme cases, if one third-party application occupies all resources, it will cause other third-party applications to have no resources available and cannot receive data pushed by the IoT platform. In the asynchronous push method, HTTP requests from different third-party applications form a waiting queue, and resources are sequentially obtained from the resource pool. In this process, different third application shared resource pools are still in essence. When a third-party application reports data concurrently and instantaneously, the third-party application occupies all resources, resulting in that other third-party applications cannot apply for resources.

In the foregoing synchronous push method and asynchronous push method, different third-party applications will affect each other. Therefore, in the Internet of Things technology, how the Internet of Things platform pushes data to third-party applications loaded on application-layer devices is an urgent issue.

Summary of the Invention

The embodiments of the present application provide a data transmission method and communication device based on the Internet of Things, so as to achieve the purpose of not affecting each other when the Internet of Things platform pushes data to a third-party application on an application-layer terminal device.

In a first aspect, an embodiment of the present application provides a data transmission method based on the Internet of Things. The method can be applied to an application layer device or a chip in the application layer device. The method is described below using an application layer device as an example. The method includes: establishing N long connections between the application layer device and the IoT platform, where N≥2, and being an integer; the application layer device passes the N long connections send first data to the IoT platform, or receive second data sent by the IoT platform through the N long connections, the first data and the second data are loaded in Data interacted between a third-party application on the application layer device and the IoT platform. With this solution, for a specific third-party application, the application layer device performs signaling interaction with the IoT platform to establish N long-term connections, and receives information about the third-party application sent by the IoT platform based on the N-long connections. The second data, or the first data about the third-party application is sent to the IoT platform based on the N long connections. In this process, through a third-party application, N long connections are established between the application layer device and the Internet of Things platform. Different N third-party applications have different long connections. When third-party applications push data, the purpose of each third-party application does not affect each other. In addition, since the long connection is multiple long connections, compared with one long connection, the real-time performance of data push can be improved.

In a feasible design, the application layer device establishes N long connections with the IoT platform, including:

A. The application layer device selects an i-th long connection identifier from M long-connection identifiers, where the i-th long-connection identifier is any one of the M long-connection identifiers, 1≤i≤N;

B. The application layer device sends a persistent connection establishment request message to the IoT platform, where the persistent connection establishment request message carries the i-th persistent connection identifier;

C. The application layer device receives a long connection establishment response message sent by the IoT platform, and the long connection establishment response message is used to indicate to the application layer device that a long corresponding to the i-th long connection identifier is successfully established. connection;

D. The application layer device receives a first notification message sent by the IoT platform through the i-th long connection, and the first notification message is used to instruct the application layer device to continue to establish a next long connection;

A-D is executed cyclically until the N long connections are established with the IoT platform.

With this solution, during the process of establishing N long-term connections between the application layer device and the IoT device, after each long-term connection is established, the IoT platform will report to the perception layer device about the The TPS of the three-party application data determines whether it is necessary to continue to establish the next long connection. By sequentially establishing N long connections, it is possible to avoid establishing multiple long connections for a third-party application at the same time, and the multiple long connections do not satisfy the third-party application. Requirements, resulting in the inability to transmit data about third-party applications in a timely manner; or avoid establishing multiple long connections to a third-party application at the same time, which exceed the needs of third-party applications, causing waste of resources or affecting other third parties Disadvantages of applications establishing long connections.

The application layer device selects N long connection identifiers from M long connection identifiers;

The application layer device sends a long connection establishment request message to the IoT platform, and the long connection establishment request message carries the N long connection identifiers;

The application layer device receives a long connection establishment response message sent by the IoT platform, and the long connection establishment response message is used to indicate to the application layer device that a long connection corresponding to the N long connection identifiers is successfully established.

With this solution, during the process of establishing N long connections between the application layer device and the IoT device, the IoT platform determines the number of long connections M and sends the M long connection identifiers to the application layer device. Then, the application layer device selects N long connections from the M long connection identifiers, and interacts with the IoT platform to establish N long connections at the same time. In this process, the application layer device selects N permanent connection identifiers from M permanent connection identifiers, and establishes N permanent connections for third-party applications based on the N permanent connection identifiers, and N permanent connections for different third-party applications. Differently, when the IoT platform pushes data to a third-party application on the application-layer terminal device, the third-party application does not affect each other.

In a feasible design, after the application layer device establishes N long connections with the IoT platform, the method further includes: the application layer device receives a second notification message sent by the IoT platform, and the second notification message It is used to instruct the application layer terminal device to remove at least one long connection among the N long connections; the application layer device removes at least one long connection among the N long connections according to the second notification message. With this solution, a second notification message is sent to the application layer device through the Internet of Things platform to remove at least one of the N long connections to achieve the purpose of timely releasing the resources occupied by third-party applications.

In a feasible design, before the application layer device and the IoT platform establish N long connections, the method further includes: the application layer device sends a request message to the IoT platform, and the request message is used to request a long connection Identification; the application layer device receives a response message sent by the IoT platform, where the response message carries the M long connection identifiers, M≥N. With this solution, for a specific third-party application, the number of long-connection identifiers M allocated to the third-party application is determined by the IoT platform. When establishing a long-connection, the application-layer device establishes a long-connection for the third-party application. The number N is less than or equal to M, to achieve the purpose of the third-party applications do not affect each other when the IoT platform pushes data to third-party applications on the application layer terminal device.

In a feasible design, the application layer device establishes N long connections with the IoT platform, including: the IoT platform includes multiple distributed IoT platforms, and the application layer device and the multiple distributed IoT platforms One or more distributed IoT platforms in the IoT platform establish the N long connections. This solution is adopted to achieve the purpose of establishing multiple long-term connections between the application layer device and the distributed IoT platform.

In a feasible design, the application layer device includes a terminal device or an application server.

In a second aspect, an embodiment of the present application provides a data transmission method based on the Internet of Things. The method can be applied to an Internet of Things platform or a chip in the Internet of Things platform. The method is described below as an example applied to the Internet of Things platform, and the method includes: the Internet of Things platform establishes N long connections with application layer devices, where N≥2;

The IoT platform receives the first data sent by the application layer device through the N long connections, or sends the second data to the IoT platform through the N long connections, and the first data and The second data is data interacting between a third-party application loaded on the application layer device and the IoT platform. With this solution, for a specific third-party application, the application layer device performs signaling interaction with the IoT platform to establish N long-term connections, and receives information about the third-party application sent by the IoT platform based on the N-long connections. The second data, or the first data about the third-party application is sent to the IoT platform based on the N long connections. In this process, through a third-party application, N long connections are established between the application layer device and the Internet of Things platform. Different N third-party applications have different long connections. When third-party applications push data, the purpose of each third-party application does not affect each other. In addition, since the long connection is multiple long connections, compared with one long connection, the real-time performance of data push can be improved.

In a feasible design, the IoT platform and the application layer device establish N long connections, including:

E. The IoT platform receives a persistent connection establishment request message sent by the application layer device, the persistent connection establishment request message carries an i-th persistent connection identifier, and the i-th persistent connection identifier is the application layer device Any one of the long connection identifiers selected from the N long connection identifiers, 1≤i≤N;

F. The IoT platform sends a long connection establishment response message to the application layer device, and the long connection establishment response message is used to indicate to the application layer device that a long connection corresponding to the i-th long connection identifier is successfully established. ;

G. The IoT platform determines the TPS of the established long connection transaction per second and the TPS of the sensing layer device, and determines whether to forward the TPS of the established long connection and the TPS of the sensing layer device to Sending, by the application layer device, a first notification message, where the first notification message is used to instruct the application layer device to continue to establish a next long connection;

E-G is executed cyclically until the N long connections are established by the application layer device.

In a feasible design, the IoT platform establishes N long-term connections with the application layer device, including: the IoT platform sends a second notification message to the application layer device, and the second notification message is used to indicate The application layer device establishes N long connections; the IoT platform receives a long connection establishment request message sent by the application layer device, and the long connection establishment request message carries the N long connections; the IoT platform Sending a long connection establishment response message to the application layer device, where the long connection establishment response message is used to indicate to the application layer device that the long connections corresponding to the N long connection identifiers are successfully established. With this solution, during the process of establishing N long connections between the application layer device and the IoT device, the IoT platform determines the number of long connections M and sends the M long connection identifiers to the application layer device. Then, the application layer device selects N long connections from the M long connection identifiers, and interacts with the IoT platform to establish N long connections at the same time. In this process, the application layer device selects N permanent connection identifiers from M permanent connection identifiers, and establishes N permanent connections for third-party applications based on the N permanent connection identifiers, and N permanent connections for different third-party applications. Differently, when the IoT platform pushes data to a third-party application on the application-layer terminal device, the third-party application does not affect each other.

In a feasible design, after the IoT platform and the application layer device establish N long connections, the method further includes:

The IoT platform sends a second notification message to the application layer device, and the second notification message is used to instruct the application layer terminal device to dismantle at least one of the N long connections. With this solution, a second notification message is sent to the application layer device through the Internet of Things platform to remove at least one of the N long connections to achieve the purpose of timely releasing the resources occupied by third-party applications.

In a feasible design, before the IoT platform and the application layer device establish N long connections, the method further includes: the IoT platform receives a request message sent by the application layer device, and the request message is used to request a long connection identifier. ; The IoT platform sends a response message to the application layer device, where the response message carries the M long connection identifiers, M≥N. With this solution, for a specific third-party application, the number of long-connection identifiers M allocated to the third-party application is determined by the IoT platform. When establishing a long-connection, the application-layer device establishes a long-connection for the third-party application. The number N is less than or equal to M, to achieve the purpose of the third-party applications do not affect each other when the IoT platform pushes data to third-party applications on the application layer terminal device.

In a feasible design, the IoT platform establishes N long connections with application layer devices, including: the IoT platform includes multiple distributed IoT platforms, and one of the multiple distributed IoT platforms Or multiple distributed IoT platforms establish the N long connections with the application layer device. This solution is adopted to achieve the purpose of establishing multiple long-term connections between the application layer device and the distributed IoT platform.

In a third aspect, an embodiment of the present application provides a communication apparatus, which has a behavior function of an application layer device in the foregoing method embodiment. The functions can be implemented by hardware, and can also be implemented by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the functions described above. The modules may be software and / or hardware.

In a possible design, the structure of the application layer device includes a processor, a memory, and a transceiver. The memory stores a computer program that can be run on the processor, and the processor executes the computer program and establishes an IoT platform. N long connections, where N≥2 and being an integer, the processor also controls the transceiver to send the first data to the IoT platform through the N long connections, or through the N bars The long connection receives second data sent by the Internet of Things platform, and the first data and the second data are data interacting between a third-party application loaded on the application layer device and the Internet of Things platform.

According to a fourth aspect, an embodiment of the present application provides a communication device, and the communication device is configured to implement a function of the behavior of an IoT platform in the foregoing method. The functions may be implemented by hardware, and may also be implemented by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the functions described above.

In a possible design, the structure of the IoT platform includes a processor, a memory, and a transceiver. The memory stores a computer program that can run on the processor, and the processor executes the computer program to establish an application-layer device. The length of the connection is N≥2; the processor further controls the transceiver to receive the first data sent by the application layer device through the N length of connection, or to the The IoT platform sends second data, and the first data and the second data are data interacting between a third-party application loaded on the application layer device and the IoT platform.

In a fifth aspect, an embodiment of the present application provides a communication device including a unit, a module, or a circuit for performing the method provided in the first aspect or each possible implementation manner of the first aspect. The communication device may be an application layer device or a module applied to the application layer device, for example, it may be a chip applied to the application layer device.

According to a sixth aspect, an embodiment of the present application provides a communication device including a unit, a module, or a circuit for performing the method provided in the second aspect or each possible implementation manner of the second aspect. The communication device may be an IoT platform or a module applied to the IoT platform, for example, it may be a chip applied to the IoT platform.

In a seventh aspect, an embodiment of the present application provides a computer program product containing instructions, which when executed on a computer, causes the computer to execute the foregoing first aspect or the methods in the various possible implementation manners of the first aspect.

In an eighth aspect, an embodiment of the present application provides a computer program product including instructions, which when executed on a computer, causes the computer to execute the foregoing second aspect or the methods in various possible implementation manners of the second aspect.

In a ninth aspect, an embodiment of the present application provides a computer-readable storage medium, where the computer-readable storage medium stores instructions, and when the computer-readable storage medium runs on the computer, causes the computer to execute the foregoing first aspect or each of the first aspect Of the possible implementations.

According to a tenth aspect, an embodiment of the present application provides a computer-readable storage medium, where the computer-readable storage medium stores instructions, and when the computer-readable storage medium runs on the computer, the computer executes the second aspect or each of the second aspect Of the possible implementations.

The data transmission method and communication device based on the Internet of Things provided in the embodiments of the present application. For a specific third-party application, the application layer device performs signaling interaction with the Internet of Things platform to establish N long connections, and based on the N long connections Send the first data to the IoT platform, or receive the second data about the third-party application sent by the IoT platform based on the N long connections. In this process, through a third-party application, N long connections are established between the application layer device and the Internet of Things platform. Different N third-party applications have different long connections. When third-party applications push data, the purpose of each third-party application does not affect each other. In addition, since the long connection is multiple long connections, compared with one long connection, the real-time performance of data push can be improved.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic diagram of a process of pushing data to a third-party application on an application layer device through an HTTP push method by the IoT platform;

FIG. 2A is a schematic diagram of an IoT architecture provided by an embodiment of the present application; FIG.

2B is a schematic diagram of another IoT architecture provided by an embodiment of the present application;

3A is a flowchart of a data transmission method based on the Internet of Things provided by an embodiment of the present application;

3B is a flowchart of another Internet of Things-based data transmission method according to an embodiment of the present application;

4 is a schematic diagram of a network logical architecture of a data transmission method based on the Internet of Things provided by an embodiment of the present application;

FIG. 5 is a logical schematic diagram of sequentially establishing a long connection applicable to a data transmission method based on the Internet of Things provided by an embodiment of the present application; FIG.

6 is an authentication flowchart applicable to an Internet of Things-based data transmission method according to an embodiment of the present application;

7 is a schematic structural diagram of a communication device according to an embodiment of the present application;

8 is a schematic structural diagram of a communication device according to an embodiment of the present application;

9 is a schematic structural diagram of a communication device according to an embodiment of the present application;

FIG. 10 is a schematic structural diagram of a communication device according to an embodiment of the present application.

detailed description

Figure 1 is a schematic diagram of the process of pushing data by the IoT platform to a third-party application on the application layer device through HTTP push, including:

11. The application layer terminal device sends an HTTP request to the ELB module.

In this step, the application-layer terminal device sends an HTTP request to an elastic load balance (ELB) module, and the HTTP request carries a callback address of a third-party application loaded on the application-layer terminal device. The ELB module is a functional module of the IoT platform, which is used to route and distribute data from third-party applications to different push modules of the IoT platform.

12. The ELB module sends an HTTP request to the IoT platform.

The push module is a functional module on the Internet of Things platform, which is used to handle data push related services.

13. The IoT platform sends an HTTP response to the ELB module.

In this step, the IoT platform sends an HTTP response to the ELB module, indicating that the callback address is successfully assigned to the third-party application.

14. The ELB module sends an HTTP response to the application-layer terminal device.

15. The IoT platform sends data from the third-party application to ELB through the callback address.

In this step, the IoT platform sends data of the third-party application to the ELB through the callback address.

16. The ELB module sends data of the third-party application to the application-layer terminal device.

17. The application-layer terminal device sends a positive response message to the ELB module.

For example, after a third-party application on the application layer terminal device successfully receives data, the application layer terminal device sends an Acknowledgement (ACK) message to the ELB module. The ACK message is, for example, 200 Ok.

18. The ELB module sends an ACK message to the IoT platform.

In the above HTTP push method, it is necessary for the application-layer terminal device to send an HTTP request to apply for a resource (that is, a callback address). When multiple third-party applications share a resource pool, different third-party applications affect each other.

In view of this, the embodiment of the present application provides a data transmission method based on the Internet of Things. By establishing multiple long connections between a third-party application on an application layer device and the Internet of Things platform, each third-party application does not affect each other. purpose.

FIG. 2A is a schematic diagram of an IoT architecture provided by an embodiment of the present application. Referring to FIG. 2A, the architecture includes: an application layer device, an IoT platform, and a perception layer device. These devices are described in detail below.

First, the application layer device.

A third-party application (Application, APP) is deployed on the application layer device. The application layer device can be a terminal device or an application server. The terminal device is a device that can provide users with voice and / or data connectivity. Device, or other processing device connected to the wireless modem. The terminal device may be a mobile terminal device, such as a mobile phone (also called a "cellular" phone) and a computer with a mobile terminal device, for example, it may be a portable, compact, handheld, computer-built or vehicle-mounted mobile device, which Exchange language and / or data with the radio access network. For example, personal communication service (PCS) phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants, PDA), handheld devices with wireless communication capabilities, computing devices or other processing devices connected to wireless modems, in-vehicle devices, wearable devices, terminals in future 5G networks, or public land mobile networks that have evolved in the future (public land mobile network) , PLMN), etc., this embodiment of the present application is not limited to this. The terminal device can also be called a system, a subscriber unit, a subscriber station, a mobile station, a mobile station, a remote station, an access point, Remote terminal equipment (remote terminal), access terminal equipment (access terminal), user terminal equipment (user terminal), user agent (user agent), user equipment (user device), or user equipment (user equipment).

Second, the Internet of Things platform.

The Internet of Things is the Internet connected to things, and it is a network that realizes intelligent identification, positioning, tracking, monitoring and management. Due to different access objects, different application fields or industries, and the functional differences of third-party applications, a variety of IoT systems will be formed. The Internet of Things system has a variety of functions, such as communication with the background, device access, device management, data storage, access strategy, security policy, data push, etc. The carrier that carries the Internet of Things with multiple functions is called Internet of things platform. Internet of things platform is a kind of middleware based on the Internet that connects objects and implements the functions of the Internet of Things.

In terms of physical form, the IoT platform can be an independent server or a distributed server.

Finally, the perception layer device.

The sensing layer includes terminal devices such as sensor gateways and sensors.

Please refer to FIG. 2A again, the sensing layer device is used to collect data, etc .; the IoT platform is responsible for storing, transmitting, and processing the data collected by the sensing layer terminal device; the application layer includes the application layer device, which mainly provides data analysis, control, and human Machine interface, etc. During the data transmission process, the sensing layer terminal device collects data and reports it to the IoT platform. The IoT platform transmits the data to the application layer terminal device. The user uses a third-party application loaded on the application layer terminal device to implement data query and data Analysis, etc.

FIG. 2B is a schematic diagram of another IoT architecture provided by an embodiment of the present application. Compared to FIG. 2A, the IoT platform is an independent IoT platform. In this embodiment, the IoT platform includes multiple distributed IoT platforms.

In the embodiment of the present application, for a specific third-party application, N long connections are established between the application layer device and the IoT platform, and the application layer device sends data about the third-party application to the IoT platform through the N long connections; In addition, the application layer device receives data about the third-party application sent by the IoT platform through the N long connections. For clarity, the data sent by the application layer device to the IoT platform is called first data, and the data sent by the IoT platform to the application layer device is called second data.

In the embodiment of the present application, the N long connections are for a specific third-party application, and specifically include the following scenarios:

Scenario 1: A third-party application is deployed on an application layer device, and the IoT platform is an independent IoT platform.

For example, referring to FIG. 2A, APP2 is deployed on the application layer device 1. At this time, the N long connections include long connection 4 and long connection 5.

Scenario 2: The third-party application is deployed in a distributed manner, and the IoT platform is an independent IoT platform.

For example, referring to FIG. 2A, APP1 is deployed on application layer device 1 and application layer device 2. At this time, N long connections include long connection 1, long connection 2, and long connection 5.

Scenario 3: Third-party applications are deployed on an application layer device, and the IoT platform is a distributed IoT platform.

For example, referring to FIG. 2B, APP2 is deployed on the application layer device 1. The IoT platform includes distributed IoT platform 1 and distributed IoT platform 2. At this time, N long connections include long connections 8 and long connections 9.

Scenario 4: Third-party application deployment is distributed. The IoT platform is a distributed IoT platform.

For example, referring to FIG. 2B, APP1 is deployed on application layer device 1 and application layer device 2. The IoT platform includes distributed IoT platform 1 and distributed IoT platform 2. At this time, N long connections include application layer devices Long connection 6 and long connection 7 between 1 and distributed IoT platform 1, and long connection 10 between application layer device 2 and distributed IoT platform 2.

It should be noted that the number of the application layer devices, the distributed IoT platform, and the number of sensing layer devices shown in FIG. 2A and FIG. 2B are merely exemplary, and the embodiments of the present application are not limited.

Hereinafter, based on the above FIG. 2A and FIG. 2B, the data transmission method based on the Internet of Things described in the embodiment of the present application will be described in detail. Specifically, refer to FIG. 3A.

FIG. 3A is a flowchart of a data transmission method based on the Internet of Things provided by an embodiment of the present application. This embodiment describes the above-mentioned data transmission method based on the Internet of Things in detail from the perspective of the interaction between the application layer device and the Internet of Things platform, and the perspective that the Internet of Things platform sends the second data to the application layer device. This embodiment includes:

101a. An application layer device establishes N long connections with an IoT platform.

Wherein, N ≧ 2 and is an integer.

In this step, for a specific third-party application, that is, a specific APP, the application layer device performs signaling interaction with the IoT platform to establish N long connections, and the application layer device and the IoT platform transmit based on the N long connections. Data about the app.

In this embodiment, the long connection is a transmission control protocol (TCP) connection. After the TCP connection is established, after completing the data once, it continues to maintain the connection state without being disconnected, and the next data transmission is continued to use the TCP connection. This kind of TCP connection is a long connection as described in the embodiments of the present application.

102a. The second data sent by the IoT platform to the application layer device through the N long connections.

The second data is data that is exchanged between a third-party application loaded on the application layer device and the IoT platform. Exemplarily, the second data is data sent by the sensing layer device to the IoT platform, and the data is data related to a third-party application. After the IoT platform receives the second data, it needs to push the second data to the application layer device for use by a third-party application on the application layer device.

In this step, the IoT platform sends the second data about the APP to the application layer device through the above N long connections; accordingly, the application layer device connects to the APP about the APP sent by the IoT platform through the above N long connections.第二数据。 The second data.

The data transmission method based on the Internet of Things provided by the embodiments of this application. For a specific third-party application, the application layer device performs signaling interaction with the Internet of Things platform to establish N long connections, and receives the Internet of Things based on the N long connections. The second data sent by the platform about the third-party application. In this process, through a third-party application, N long connections are established between the application layer device and the Internet of Things platform. Different N third-party applications have different long connections. When third-party applications push data, the purpose of each third-party application does not affect each other. In addition, since the long connection is multiple long connections, compared with one long connection, the real-time performance of data push can be improved.

FIG. 3B is a flowchart of another Internet of Things-based data transmission method provided by an embodiment of the present application. This embodiment describes the above-mentioned data transmission method based on the Internet of Things in detail from the perspective of the interaction between the application layer device and the Internet of Things platform, and the perspective of the application layer device sending the first data to the Internet of Things platform. This embodiment includes:

101b. The application layer device establishes N long connections with the IoT platform.

Wherein, N ≧ 2 and is an integer.

Specifically, reference may be made to the description of step 101a, and details are not described herein again.

102b. The application layer device sends first data to the IoT platform through the N long connections,

The first data is data interacting between a third-party application loaded on the application layer device and the IoT platform. Exemplarily, the second data is data sent by the application layer device to the sensing layer device, and the data is a control instruction sent by the user to the sensing layer device through a third-party application. After the IoT platform receives the first data, it needs to push the first data to the sensing layer device, so as to achieve the purpose that the user controls the sensing layer device through a third-party application on the application layer device.

Specifically, reference may be made to the description of step 101b, and details are not described herein again.

The data transmission method based on the Internet of Things provided by the embodiments of the present application. For a specific third-party application, the application layer device performs signaling interaction with the Internet of Things platform to establish N long connections, and based on the N long connections to the Internet of Things. The first data sent by the platform about the third-party application. In this process, through a third-party application, N long connections are established between the application layer device and the Internet of Things platform. Different N third-party applications have different long connections. When third-party applications push data, the purpose of each third-party application does not affect each other.

In the above embodiment, in the process of establishing N connections between the application layer device and the IoT platform, the size of N is determined by the IoT platform. The following describes in detail how the IoT platform notifies N to the application layer device.

In a feasible implementation manner, before the application layer device establishes N long connections with the IoT platform, it further sends a request message to the IoT platform, the request message is used to request a long connection identifier; the application layer The device receives a response message sent by the Internet of Things platform, and the response message carries M long-connection identifiers.

In the embodiment of the present application, the persistent connection identifier is a unique identifier of the persistent connection and is used for authentication and the like. In this embodiment, before N long connections are established, the application layer device sends a request message to the IoT platform to request to obtain the long connection identifier; accordingly, the IoT platform receives the request message. After receiving the request message, the IoT platform allocates a specific third-party application on the application layer device according to its ability to carry the number of long connections and / or the amount of data reported by the third-party application on the perception layer device. M long connections, and carry the M long connection identifiers in a response message to send to the application layer device; correspondingly, the application layer device receives the response message carrying the M long connection identifiers. For example, assuming that the IoT platform can establish a maximum of 30 long connections, and currently 15 long connections have been established, and the amount of data reported by the perception layer device about third-party applications is large, the IoT platform can take a larger value of M, Such as 4, and then select 4 long connection identifiers to be carried in the response message and send to the application layer device; for another example, suppose that the IoT platform can establish up to 30 long connections, and 27 long connections have been established at this time. The amount of data reported by third-party devices on third-party applications is relatively large. The IoT platform also sets the value of M to 1, etc., and then selects a long connection identifier to be carried in the response message and sends it to the application-layer device. The platform pre-allocates 5 long-connection identifiers for any third-party application, that is, M = 5.

In this embodiment, for a specific third-party application, the number of persistent connection identifiers M allocated to the third-party application is determined by the Internet of Things platform. When establishing a persistent connection, the application-layer device establishes a persistent connection for the third-party application. The number N is less than or equal to M, to achieve the purpose of the third-party applications do not affect each other when the IoT platform pushes data to third-party applications on the application layer terminal device.

In the above embodiment, when N long connections are established between the application layer device and the IoT platform, N long connections may be established at the same time, or N long connections may be established in sequence. The two methods are described in detail below.

In a feasible implementation manner, the application layer device and the IoT platform establish N long connections in turn. At this time, the application layer device establishes N long connections with the IoT platform, including:

Step A: The application layer device selects an i-th long-connection identifier from the M long-connection identifiers, where the i-th long-connection identifier is any one of the M long-connection identifiers, and 1≤i ≤N.

Step B: The application layer device sends a long connection establishment request message to the IoT platform, where the long connection establishment request message carries the i-th long connection identifier;

Step C: The application layer device receives a long connection establishment response message sent by the IoT platform, where the long connection establishment response message is used to indicate to the application layer device that the i-th long connection identifier corresponding to the successful establishment of the Long connection;

Step D: The application layer device receives a first notification message sent by the IoT platform through the i-th long connection, and the first notification message is used to instruct the application layer device to continue to establish a next long connection;

Specifically, when the first long connection among the N long connections is established, the application layer device randomly selects one long connection identifier (for example, the i-th long connection identifier) from the M long-connection identifiers, and then, The long connection identifier is carried in the long connection establishment request message and sent to the IoT platform; correspondingly, the IoT platform receives the long connection establishment request carrying the i-th long connection identifier, that is, step E; The long connection request of the i long connection identifier performs identity authentication. For example, the long connection request carries the i-th long connection identifier, the identity of the third-party application, and the key. The IoT platform performs the identity identification of the third-party application. Identity authentication; then, the IoT platform sends a long connection establishment response message to the application layer device to successfully establish the first long connection, step F; correspondingly, the application layer device receives the long connection establishment sent by the IoT platform A response message, where the long connection establishment response message is used to indicate to the application layer device that a long connection corresponding to the i-th long connection identifier is successfully established. After that, the IoT platform determines the transaction per second (TPS) of the first long connection, and the TPS of the sensing layer device. The TPS of the first long connection is used to indicate the transmission of the first long connection. Data capability. The TPS of the sensing layer device is used to indicate the ability of the sensing layer device to collect data about third-party applications. The IoT platform determines whether to continue to establish a second-day long connection based on the two TPS. For a long connection, a first notification message is sent to the application layer device, that is, step G; correspondingly, the application layer device receives the first notification message, and randomly selects a long connection from the remaining M-1 long connection identifiers, and the cycle Steps A to D described above are performed; for the Internet of Things platform, steps E to G are performed cyclically.

In the above process of establishing N long connections, after each long connection is established, the IoT platform will determine whether to continue to establish the next long connection according to the TPS of the long connection that has been established and the TPS of the sensing layer device. For example, assuming that two long connections have been established, the TPS of each long connection is 100 bits / second, and the TPS of data reported by the sensing layer device is 300 bits / second, the IoT platform determines that a total of 3 long connections need to be established At this time, the IoT platform sends a first notification message to the application layer device through any one of the two established long connections. The first notification message is used to instruct the application layer device to continue to establish the second long connection. . After the third long connection is established, the IoT platform determines that the TPS of the three long connections is 300 bits / second, which is the same as the TPS of the data reported by the sensing layer device. At this time, the IoT platform no longer needs to send a first notification message to the application layer device to establish the fourth long connection.

In this embodiment, in the process of establishing N long connections between the application layer device and the IoT device, after each long connection is established, the IoT platform will report to the perceptual layer device on the first long connection based on the established TPS of the long connection. The TPS of the three-party application data determines whether it is necessary to continue to establish the next long connection. By sequentially establishing N long connections, it is possible to avoid establishing multiple long connections for a third-party application at the same time, and the multiple long connections do not satisfy the third-party application. Requirements, resulting in the inability to transmit data about third-party applications in a timely manner; or avoid establishing multiple long connections to a third-party application at the same time, which exceed the needs of third-party applications, causing waste of resources or affecting other third parties Disadvantages of applications establishing long connections.

In a feasible implementation manner, the application layer device and the IoT platform simultaneously establish N long connections. At this time, the application layer device establishes N long connections with the IoT platform, including:

The application layer device sends a long connection establishment request message to the IoT platform, and the long connection establishment request message carries the N long connection identifiers; the application layer device receives the long connection establishment response message sent by the IoT platform The long connection establishment response message is used to indicate to the application layer device that the long connections corresponding to the N long connection identifiers are successfully established.

Specifically, for a specific third-party application, the application layer device selects N long connection identifiers from the M long connection identifiers, and carries the N long connection identifiers in a long connection establishment request message and sends it to the IoT platform; After the IoT platform receives a request for establishing a long connection carrying N long connection identifiers, it performs identity authentication on the N long connection identifiers, the identity of a third-party application, etc., and sends a long connection to the application layer device after the authentication is passed The establishment response message is used to indicate to the application layer device that the long connections corresponding to the N long connection identifiers are successfully established.

In the above process of establishing N long connections, the IoT platform allocates M long connection identifiers for a third application on the application layer device, and carries the M long connection identifiers in a response message and sends it to the application layer device. The application layer After the device receives M persistent connection identifiers, it selects N persistent connection identifiers from the M persistent connection identifiers, and carries the N persistent connection identifiers in the persistent connection establishment request and sends them to the IoT platform to establish N concurrently. Long connection. For example, if N = 4, the application layer device sends a long connection establishment request message carrying the four long connection identifiers to the IoT platform. After receiving the long connection establishment request message, the IoT platform establishes the four long connections with the application layer device. The long connection corresponding to the connection ID.

In this embodiment, during the process of establishing N long connections between the application layer device and the IoT device, the IoT platform determines the number of long connections M, and sends the M long connection identifiers to the application layer device. Then, the application layer device selects N long connections from the M long connection identifiers, and interacts with the IoT platform to establish N long connections at the same time. In this process, the application layer device selects N permanent connection identifiers from M permanent connection identifiers, and establishes N permanent connections for third-party applications based on the N permanent connection identifiers, and N permanent connections for different third-party applications. Differently, when the IoT platform pushes data to a third-party application on the application-layer terminal device, the third-party application does not affect each other.

In the above embodiment, in order to prevent a third-party application from occupying N long connections for a long time, after the application layer device establishes N long connections with the IoT platform, it receives a second notification message sent by the IoT platform, and the second notification The message is used to instruct the application-layer terminal device to remove at least one of the N long connections.

Specifically, after N long connections are established between the application layer device and the IoT platform, after a certain period of time (such as half an hour), the IoT platform determines that the TPS of the data reported by the sensing layer device is much smaller than the TPS of the N long connections. Then, a second notification message is sent to the application layer device to remove at least one long connection. For example, if N = 4, the TPS of each long connection is 100 bits / second, and the TPS of the data reported by the device at the sensing layer is 200 bits / second. 2 long connections. After the application layer device receives the second notification message, it performs signaling interaction with the IoT platform to remove any two of the four long connections.

In this embodiment, a second notification message is sent to the application layer device through the Internet of Things platform to remove at least one of the N long connections to achieve the purpose of timely releasing the resources occupied by the third-party application.

In the following, a specific example is used to describe the above-mentioned data transmission method based on the Internet of Things in detail. For example, see FIG. 4.

FIG. 4 is a schematic diagram of a network logical architecture of a data transmission method based on the Internet of Things provided by an embodiment of the present application. In this network logical architecture, the application layer equipment establishes N long-term connections with the Internet of Things platform. The Internet of Things platform includes an ELB module, at least one push module, at least one service bus, and at least one metadata server. Modules, at least one server bus forms a cluster. The push module includes at least one message queue proxy sub-module, at least one message queue client sub-module, and at least one consumer sub-module. Each long connection corresponds to one message queue proxy sub-module, one message queue client sub-module, one service bus, and one consumer. Submodule. Next, based on FIG. 4, the above-mentioned data transmission method based on the Internet of Things will be described in detail by taking the Internet of Things platform to send second data to the application layer device as an example. Exemplarily, taking the establishment of N long connections in sequence as an example, the main flow of FIG. 4 is as follows:

201. The application layer device sends a request message to the ELB.

In this step, for a screenshot of the APP, the application layer device sends a request message to the ELB to request the allocation of a persistent connection identifier.

In this step, the application layer device only initiates a request message. As for the number of requests for allocation of long-connection identifiers, the application layer device cannot be determined, but is determined by the IoT platform.

202. The ELB module sends a request message to the metadata service module.

After receiving the request message, the metadata service module assigns a certain number of persistent connection identifiers to the above-mentioned APP, such as M persistent connection identifiers, and carries the M persistent connection identifiers in the response message, and sends it to the ELB module. The ELB module sends the M long connection identifiers to the application layer device (this step is not shown in the figure). The ELB module is used to connect a third-party application on the application layer device to a long connection between the IoT platform and the application layer device.

203. The application layer device interacts with the ELB module to complete the establishment of the long connection and the subscription request.

204. The ELB module interacts with the message queue agent sub-module in the IoT platform to complete the establishment and subscription of the long connection.

205. The message queue agent sub-module in the IoT platform interacts with the metadata service module to complete the authentication of the long connection.

In the above steps 203 to 205, the detailed process is as follows:

Long connection identity acquisition phase: The application layer device sends the long connection establishment request to the message queue (MQ) broker sub-module in the push module of the IoT platform through the ELB module. The MQ broker sub-module is a third-party application. Allocate M long connection identifiers, and carry the M long connection identifiers in a response message and send them to the application layer device through the ELB module.

Long connection establishment phase (the first day long connection is established): the application layer device selects a long connection identifier for the third-party application. Send a permanent connection establishment request to the MQ broker through the ELB module. The long connection establishment request carries the identity, long-term connection identifier, secret key, etc. of the third-party application. The MQ broker sub-module sends an authentication request to the metadata service module, and the metadata server module authenticates the identity of the third-party application, the identity of the persistent connection, and the like. After the authentication is passed, the metadata service module sends an authentication pass response message to the MQbroker submodule. The MQbroker submodule successfully establishes a long connection artificially, and sends a long connection establishment response message to the application layer device through the ELB module.

In this process, the long-distance connection identifier is allocated to the third-party application through the Internet of Things platform, so as to achieve the purpose of the Internet of Things platform to control the number of long-connections.

206. The metadata service module sends the second data to the service bus.

207. The consumption submodule pulls data from the service bus.

208: The consumption submodule pushes the second data to the message queue client submodule.

209. The message queue client sub-module pushes the second data to the MQ broker sub-module.

After that, the MQ broker sub-module pushes the second data to the ELB module through the long connection, and the ELB module further pushes the second data to the application layer device through the long connection. After the application layer device receives the second data about the third-party application, it responds to the IoT platform with a confirmation message according to the quality of service (QoS).

In the embodiment of the present application, during the process of establishing a long connection, the TPS of the data reported by the sensing layer device and the TPS of the established long connection determine whether the next long connection needs to be established or whether the established long connection needs to be dismantled. Or reduce the number of long connections, achieve the ability to adaptively manage long connections, and improve the flexibility of the IoT platform. Further, after establishing multiple long connections, for a piece of second data, the metadata service module selects only one long link to push the second data to the service bus, which is then pulled by a consumer submodule and pushed to the message queue In the client submodule, additional fields are added in the header field of each second data, such as a message queue gateway identity (MSGID), and a third-party application can identify the uniqueness of the message according to the MSGID. In other words, the second data in the message queue client submodule is different from each other, and the second data transmitted by each long connection is different, so as to avoid the disadvantages of repeated data push. In addition, during the above data transmission process, each third-party application corresponds to a single message queue proxy submodule, a message queue client submodule, and a service bus in the service bus cluster. The second data from the service bus is not pushed in chronological order. To the message queue agent sub-module to ensure timing.

It should be noted that, although the message queue agent submodule is used as a submodule of the push module to describe the method described in this embodiment in detail in the above embodiment, the embodiment of the present application is not limited, for example, the message queue agent submodule Modules, message queue client submodules, etc. can also be deployed independently of the push module.

Next, how to push data and establish the remaining long connections after the first long connection is established in FIG. 4 described above is described in detail. Specifically, reference may be made to FIG. 5, which is a logical schematic diagram of sequentially establishing a long connection applicable to an Internet of Things-based data transmission method provided in an embodiment of the present application. In this logical architecture, the message queue proxy module and the push module are independently set The IoT platform also includes a determination module. The main process of this embodiment is as follows:

301: Push the module to the service bus to pull the second data.

Exemplarily, the sensing layer device accesses the metadata service module of the IoT platform through a cloud access gateway (CIG). The metadata service module stores the second data collected by the sensing layer device, and pushes the first data to the service bus. Two data. After the first long connection is established, push the module to the service bus to pull data.

302: The push module pushes the second data to the message queue proxy module.

303. The message queue proxy module pushes the second data to the ELB module.

304. The application layer device sends an ACK message to the ELB module.

305. The ELB module sends an ACK message to the message queue agent module.

306. The message queue proxy module sends an ACK message to the push module.

In the above steps 301 to 306, the push module pushes the second data to the third-party application on the application layer device through the established first long connection.

307. The push module sends a message requesting to determine the TPS to the determination module.

In this step, after receiving the message requesting the determination of the TPS, the determination module determines the TPS of the first long connection and the TPS of the data reported by the sensing layer device.

Exemplarily, the IoT platform calculates the ability of the first long connection to receive data according to the average delay and the like, and converts the ability to TPS.

The perception layer device reports the second data to the metadata service module of the IoT platform. The metadata service module pushes the second data to the service bus, the determination module counts the second data about the third-party application, and obtains the perception layer device according to the statistical result. The TPS of the second data reported about the third-party application. Then, the determination module compares the two TPS. If the TPS of the data reported by the sensing layer device exceeds a certain multiple of the TPS of the first long connection (configurable, such as 1.2), and continues for a period of time, such as half an hour, then The determining module determines to send a first notification message to the application layer device to notify the application layer device to continue to establish the next long connection.

308. The determining module sends a first notification message to the pushing module.

After receiving the first notification message, the push module sends the first notification message to the application layer device through the established long connection (such as the first long connection). Exemplarily, a fixed header field may be set for the first notification message. The fixed header field includes a long connection identifier, and the application layer device parses the header field and establishes a long connection corresponding to the long connection identifier with the Internet of Things platform.

In addition, in the above step 307, if the TPS of the data reported by the sensing layer device is less than a certain multiple of the TPS of the first long connection and continues for a period of time, the determining module sends a second notification message to the application layer device to remove the first 1 long connection. Each time a new long connection is established, 306 to 308 are executed cyclically to establish N long connections in turn.

In the following, how the Internet of Things platform performs security authentication is described in detail. For example, see FIG. 6. FIG. 6 is an authentication flowchart applicable to an Internet of Things-based data transmission method according to an embodiment of the present application, including:

Persistent ID acquisition phase:

401. An application layer device sends a request message to an ELB module.

In this step, the application layer device sends a request message carrying the identity (APP ID) of the third-party application to the ELB module. The request message is, for example, an HTTP request.

402. The ELB module sends a request message to the metadata service module.

403. The metadata service module sends a 200 OK message to the ELB module.

The metadata service module allocates M persistent connection identifiers to the third-party application, and sends the M persistent connection identifiers to the ELB module in a 200 OK message.

404. The ELB module sends a 200 OK message to the application layer device.

Long connection establishment phase:

405. The application layer device sends a persistent connection establishment request message to the ELB module.

In this step, the application layer device sends the identity identifier, the secret key, and the persistent connection identifier of the third-party application to the ELB in a persistent connection establishment request message.

406. The ELB module sends a persistent connection establishment request message to the message queue agent module.

407. The message queue proxy module sends an authentication callback message to the push module.

408. The push module sends an authentication request message to the metadata service module.

409. The metadata service module sends an authentication response message to the push module.

410: The push module sends a long connection successful establishment callback message to the message queue agent module.

411. The message queue proxy module sends an authentication success response message to the ELB module.

412. The ELB module sends an authentication success response message to the application layer device.

413: The push module sends a status update message to the metadata service module.

In this step, the push module sends a status update message to the metadata service module, so that the metadata service module updates the status of the third-party application of the application layer device, such as successfully establishing a long connection.

It should be noted that there is no strict sequence of the above steps 410 and 413.

Subscription phase:

414. The application layer device sends a subscription request to the ELB.

After the long connection is successfully established, in this step, the application layer device carries the long connection identifier, the message queue identifier, and the identifier of the third-party application to the ELB module in a subscription request.

415. The ELB sends a subscription request to the message queue proxy module, where the subscription request carries a long-connection identifier, an identifier of the message queue, and an identity identifier of a third-party application.

415. The message queue proxy module sends an authorization callback message to the push module.

416. The push module sends a verification message to the metadata service module.

418. The metadata service module sends a verification response message to the push module.

419. The push module sends a subscription success callback message to the message queue agent module.

420: The message queue proxy module sends a subscription success response message to the ELB module.

421. The ELB module sends a subscription success response message to the application layer device.

Data push phase:

422. The metadata service module reports the second data to the service bus.

423. The consumption module pulls the second data from the service bus.

In this step, the consumption module pulls the second data from the service bus through a long connection.

424. The push module obtains the second data from the consumption module.

In this step, the consumption module pushes the second data to the push module in chronological order.

425: The push module pushes the second data to the message queue module.

426. The message queue agent module pushes the second data to the ELB module.

427. The ELB module pushes the second data to the application layer device.

After that, the application layer device sends an OK message to the ELB, which is not shown in the figure.

Long connection abnormal phase:

428. The message queue agent module detects an abnormal long connection.

429. The message queue proxy module sends a persistent connection exception message to the push module.

430: The push module sends a long connection logout message to the consumption module.

In this step, the push module sends a long connection logout message (for example, the above-mentioned second notification message) to the consumption module.

431: The consumption module sends a long connection logout message to the service bus.

After receiving the persistent connection logout message, the service bus logs off the persistent connection.

If the long connection is abnormal, all or some of the long connections are abnormal and eventually dismantled, resulting in no long connection, or the remaining long connection cannot meet the data requirements of the third-party application, repeat the above long connection identification acquisition phase, The long connection establishment phase, the subscription phase re-establishes and subscribes to the long connection, and then pushes the data.

FIG. 7 is a schematic structural diagram of a communication device according to an embodiment of the present application. The communication device involved in this embodiment may be an application layer device or a chip applied to an application layer device. The communication apparatus may be configured to execute a function of an application layer device in the foregoing method embodiment. As shown in FIG. 7, the communication device may include a processing module 11 and a transceiver module 12. among them,

A processing module 11 configured to establish N long connections with the IoT platform, where N≥2, and is an integer;

The transceiver module 12 is configured to send first data to the IoT platform through the N long connections established by the processing module 11, or receive the IoT through the N long connections established by the processing module 11. The second data sent by the platform, the first data and the second data are data interacting between a third-party application loaded on the application layer device and the IoT platform.

In a feasible design, the processing module 11 and the transceiver module 12 are specifically configured to execute A-D in a loop until the N long-term connections are established with the IoT platform, and the A-D includes:

A. The processing module 11 selects an i-th long connection identifier from M long-connection identifiers, where the i-th long-connection identifier is any one of the M long-connection identifiers, 1≤i≤N;

B. The transceiver module 12 sends a long connection establishment request message to the IoT platform, where the long connection establishment request message carries the i-th long connection identifier;

C. The transceiver module 12 receives a long connection establishment response message sent by the IoT platform, and the long connection establishment response message is used to indicate to the application layer device that a long corresponding to the i-th long connection identifier is successfully established. connection;

D. The transceiver module 12 receives a first notification message sent by the IoT platform through the i-th long connection, and the first notification message is used to instruct the application layer device to continue to establish a next long connection.

In a feasible design, the processing module 11 is specifically configured to select N long connection identifiers from M long connection identifiers; and the transceiver module 12 is configured to send a long connection establishment request to the IoT platform Message, the persistent connection establishment request message carries the N persistent connection identifiers, and receives a persistent connection establishment response message sent by the IoT platform, where the persistent connection establishment response message is used to indicate to the application layer device that the establishment is successful The long connections corresponding to the N long connections are identified.

In a feasible design, the transceiver module 12 is further configured to receive a second notification message sent by the IoT platform after the processing module 11 establishes N long-term connections with the IoT platform. The notification message is used to instruct the application-layer terminal device to remove at least one of the N long connections;

The processing module is further configured to remove at least one of the N long connections according to the second notification message.

In a feasible design, the transceiver module 12 is further configured to send a request message to the IoT platform before the processing module 11 establishes N long connections with the IoT platform, and the request message is used to request Long connection identifier; receiving a response message sent by the IoT platform, the response message carrying the M long connection identifiers, M≥N.

In a feasible design, when the IoT platform includes multiple distributed IoT platforms, the processing module 11 communicates with one or more of the multiple distributed IoT platforms. Establishing the N long connections.

The communication device provided in the embodiment of the present application can perform the actions of the application layer device in the foregoing method embodiments. The implementation principles and technical effects are similar, and details are not described herein again.

FIG. 8 is a schematic structural diagram of a communication device according to an embodiment of the present application. The communication device involved in this embodiment may be an IoT platform or a chip applied to the IoT platform. The communication device may be configured to execute a function of the Internet of Things platform in the foregoing method embodiment. As shown in FIG. 8, the communication device may include a processing module 21 and a transceiver module 22. among them,

A processing module 21, configured to establish N long connections with the application layer device, where N≥2;

The transceiver module 22 is configured to receive the first data sent by the application layer device through the N long connections established by the processing module 21, or send the N long connections to the network through the N long connections established by the processing module 21. The IoT platform sends second data, and the first data and the second data are data interacting between a third-party application loaded on the application layer device and the IoT platform.

In a feasible design, the processing module 21 and the transceiver module 22 are configured to perform E-G in a loop until the application layer device establishes the N long connections, and the E-G includes:

E. The transceiver module 22 receives a persistent connection establishment request message sent by the application layer device. The persistent connection establishment request message carries an i-th persistent connection identifier, and the i-th persistent connection identifier is the application layer device. Any one of the long connection identifiers selected from the N long connection identifiers, 1≤i≤N;

F. The transceiver module 22 sends a long connection establishment response message to the application layer device, where the long connection establishment response message is used to indicate to the application layer device that a long connection corresponding to the i-th long connection identifier is successfully established. ;

G. The processing module 21 determines the TPS of the established long connection transaction per second and the TPS of the sensing layer device, and determines whether to forward the TPS of the established long connection and the TPS of the sensing layer device. Sending, by the application layer device, a first notification message, where the first notification message is used to instruct the application layer device to continue to establish a next long connection;

In a feasible design, the processing module 21 is specifically configured to use the transceiver module 22 to send a second notification message to the application layer device when establishing N long-term connections with the application layer device. The notification message is used to instruct the application layer device to establish N long connections; receive a long connection establishment request message sent by the application layer device, and the long connection establishment request message carries the N long connections; to the application layer The device sends a long connection establishment response message, and the long connection establishment response message is used to indicate to the application layer device that the long connections corresponding to the N long connection identifiers are successfully established.

In a feasible design, the transceiver module 22 is further configured to send a second notification message to the application layer device after the processing module 21 establishes N long-term connections with the application layer device. The message is used to instruct the application-layer terminal device to remove at least one of the N long connections.

In a feasible design, before the processing module 21 establishes N long connections with the application layer device, the transceiver module 22 is further configured to receive a request message sent by the application layer device, and the request message is used to request the long Connection identifier; sending a response message to the application layer device, the response message carrying the M long connection identifiers, M≥N.

In a feasible design, when the IoT platform includes multiple distributed IoT platforms, the processing module 21 controls one or more distributed IoT platforms in the multiple distributed IoT platforms. Establishing the N long connections with the application layer device.

The communication device provided in the embodiment of the present application can perform the actions of the IoT platform in the foregoing method embodiments. The implementation principles and technical effects are similar, and details are not described herein again.

It should be noted that it should be understood that when the above transceiver module is actually implemented, it may be a transceiver. The processing module can be implemented in the form of software calling through processing elements; it can also be implemented in the form of hardware. For example, the processing module may be a separately established processing element, or it may be integrated and implemented in a certain chip of the above-mentioned device. In addition, it may also be stored in the memory of the above-mentioned device in the form of a program code. Invoke and execute the functions of the above processing modules. In addition, all or part of these modules can be integrated together, or they can be implemented independently. The processing element described herein may be an integrated circuit with signal processing capabilities. In the implementation process, each step of the above method or each of the above modules may be completed by an integrated logic circuit of hardware in a processor element or an instruction in the form of software.

For example, the above modules may be one or more integrated circuits configured to implement the above method, for example, one or more application specific integrated circuits (ASICs), or one or more microprocessors (digital signal processor (DSP), or one or more field programmable gate array (FPGA). As another example, when one of the above modules is implemented in the form of a processing element scheduler code, the processing element may be a general-purpose processor, such as a central processing unit (CPU) or other processors that can call program code. As another example, these modules can be integrated together and implemented in the form of a system-on-a-chip (SOC).

FIG. 9 is a schematic structural diagram of a communication device according to an embodiment of the present application. As shown in FIG. 9, the communication device 30 may include: a processor 31 (such as a CPU), a memory 32, and a transceiver 33; the transceiver 33 is coupled to the processor 31, and the processor 31 controls the receiving action of the transceiver 33; the memory 32 May include high-speed random access memory (random-access memory, RAM), and may also include non-volatile memory (non-volatile memory (NVM)), such as at least one disk memory. The memory 32 may store various instructions to It is used to complete various processing functions and implement the method steps of the present application. Optionally, the communication device involved in this application may further include a power source 34, a communication bus 35, and a communication port 36. The transceiver 33 may be integrated in the transceiver of the communication device, or may be an independent transceiver antenna on the communication device. The communication bus 35 is used to implement a communication connection between the components. The communication port 36 is used to implement connection and communication between the communication device and other peripheral devices.

In the embodiment of the present application, the memory 32 is used to store computer-executable program code, and the program code includes instructions. When the processor 31 executes the instructions, the instructions cause the processor 31 of the communication device to execute the application-layer device in the foregoing method embodiment. The processing action causes the transceiver 33 to perform the sending and receiving actions of the application layer device in the foregoing embodiment, and the implementation principles and technical effects thereof are similar, and details are not described herein again.

FIG. 10 is a schematic structural diagram of a communication device according to an embodiment of the present application. As shown in FIG. 10, the communication device 40 may include: a processor 41 (such as a CPU), a memory 42, and a transceiver 43; the transceiver 43 is coupled to the processor 41, and the processor 41 controls the transmitting and receiving actions of the transceiver 43; the memory 42 It may include high-speed random-access memory (RAM), or it may also include non-volatile memory (NVM), such as at least one disk memory, and various instructions can be stored in the memory 42 to It is used to complete various processing functions and implement the method steps of the present application. Optionally, the communication device involved in this application may further include a communication bus 44. The transceiver 43 may be integrated in the transceiver of the communication device, or may be an independent transceiver antenna on the communication device. The communication bus 44 is used to implement a communication connection between the components. The communication port 46 is used to implement connection and communication between the communication device and other peripheral devices.

In the embodiment of the present application, the above-mentioned memory 42 is configured to store computer-executable program code, and the program code includes instructions. When the processor 41 executes the instructions, the instructions cause the processor 41 of the communication device to execute the above-mentioned embodiment or the optional embodiment. The processing action of the Internet of Things platform causes the transceiver 43 to perform the receiving action of the Internet of Things platform in the above method embodiment. The implementation principles and technical effects are similar, which are not described again here.

In the above embodiments, it may be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented in software, it may be implemented in whole or in part in the form of a computer program product. A computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the processes or functions according to the embodiments of the present application are wholly or partially generated. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable device. The computer instructions may be stored in or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from a website site, computer, server, or data center via a wired (e.g., Coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) transmission to another website site, computer, server or data center. The computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, a data center, or the like that includes one or more available medium integrations. The usable medium may be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid state disk (Solid State Disk (SSD)), and the like.

The term "plurality" herein refers to two or more. The term "and / or" in this document is only a kind of association relationship describing related objects, which means that there can be three kinds of relationships, for example, A and / or B can mean: A exists alone, A and B exist simultaneously, and exists alone B these three cases. In addition, the character "/" in this article generally indicates that the related objects are an "or" relationship; in the formula, the character "/" indicates that the related objects are a "divide" relationship.

It can be understood that the various numerical numbers involved in the embodiments of the present application are only for the convenience of description and are not used to limit the scope of the embodiments of the present application.

It can be understood that, in the embodiment of the present application, the size of the sequence numbers of the above processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not deal with the implementation of this application. The implementation process of the example constitutes any limitation.

Claims

A data transmission method based on the Internet of Things, which is characterized by:

The application layer device establishes N long connections with the IoT platform, where N≥2, and is an integer;

The application layer device sends first data to the IoT platform through the N long connections, or receives second data sent by the IoT platform through the N long connections, and the first data and The second data is data interacting between a third-party application loaded on the application layer device and the IoT platform.
The method according to claim 1, characterized in that the application layer device establishes N long connections with the IoT platform, comprising:

A. The application layer device selects an i-th long connection identifier from M long-connection identifiers, where the i-th long-connection identifier is any one of the M long-connection identifiers, 1≤i≤N;

B. The application layer device sends a persistent connection establishment request message to the IoT platform, where the persistent connection establishment request message carries the i-th persistent connection identifier;

C. The application layer device receives a long connection establishment response message sent by the IoT platform, and the long connection establishment response message is used to indicate to the application layer device that a long corresponding to the i-th long connection identifier is successfully established. connection;

D. The application layer device receives a first notification message sent by the IoT platform through the i-th long connection, and the first notification message is used to instruct the application layer device to continue to establish a next long connection;

A-D is executed cyclically until the N long connections are established with the IoT platform.
The method according to claim 1, characterized in that the application layer device establishes N long connections with the IoT platform, comprising:

The application layer device selects N long connection identifiers from M long connection identifiers;

The application layer device sends a long connection establishment request message to the IoT platform, and the long connection establishment request message carries the N long connection identifiers;

The application layer device receives a long connection establishment response message sent by the IoT platform, and the long connection establishment response message is used to indicate to the application layer device that a long connection corresponding to the N long connection identifiers is successfully established.
The method according to any one of claims 1 to 3, wherein after the application layer device establishes N long connections with the Internet of Things platform, the method further comprises:

Receiving, by the application layer device, a second notification message sent by the IoT platform, where the second notification message is used to instruct the application layer terminal device to remove at least one of the N long connections;

The application layer device removes at least one long connection among the N long connections according to the second notification message.
The method according to any one of claims 2 to 4, before the application layer device and the IoT platform establish N long connections, further comprising:

The application layer device sends a request message to the IoT platform, the request message is used to request a long connection identifier;

The application layer device receives a response message sent by the Internet of Things platform, and the response message carries the M long connection identifiers, M≥N.
The method according to any one of claims 1 to 5, wherein the application layer device establishes N long-term connections with the Internet of Things platform, including:

The IoT platform includes multiple distributed IoT platforms, and the application layer device establishes the N long connections with one or more of the multiple distributed IoT platforms.
The method according to any one of claims 1 to 6, wherein the application layer device comprises a terminal device or an application server.
A data transmission method based on the Internet of Things, which is characterized by:

The IoT platform establishes N long connections with the application layer devices, where N≥2;

The IoT platform receives the first data sent by the application layer device through the N long connections, or sends the second data to the IoT platform through the N long connections, and the first data and The second data is data interacting between a third-party application loaded on the application layer device and the IoT platform.
The method according to claim 8, wherein the establishment of N long-term connections between the IoT platform and the application layer device comprises:

E. The IoT platform receives a persistent connection establishment request message sent by the application layer device, the persistent connection establishment request message carries an i-th persistent connection identifier, and the i-th persistent connection identifier is the application layer device Any one of the long connection identifiers selected from the N long connection identifiers, 1≤i≤N;

F. The IoT platform sends a long connection establishment response message to the application layer device, and the long connection establishment response message is used to indicate to the application layer device that a long connection corresponding to the i-th long connection identifier is successfully established. ;

G. The IoT platform determines the TPS of the established long connection transaction per second and the TPS of the sensing layer device, and determines whether to forward the TPS of the established long connection and the TPS of the sensing layer device to Sending, by the application layer device, a first notification message, where the first notification message is used to instruct the application layer device to continue to establish a next long connection;

E-G is executed cyclically until the N long connections are established by the application layer device.
The method according to claim 8, wherein the establishment of N long-term connections between the IoT platform and the application layer device comprises:

Sending, by the IoT platform, a second notification message to the application layer device, where the second notification message is used to instruct the application layer device to establish N long connections;

The IoT platform receives a long connection establishment request message sent by the application layer device, and the long connection establishment request message carries the N long connections;

The IoT platform sends a long connection establishment response message to the application layer device, and the long connection establishment response message is used to indicate to the application layer device that a long connection corresponding to the N long connection identifiers is successfully established.
The method according to any one of claims 8 to 10, wherein after the IoT platform and the application layer device establish N long connections, the method further comprises:

The IoT platform sends a second notification message to the application layer device, and the second notification message is used to instruct the application layer terminal device to dismantle at least one of the N long connections.
The method according to any one of claims 8 to 11, before the NIoT platform and the application layer device establish N long connections, further comprising:

Receiving, by the IoT platform, a request message sent by an application layer device, where the request message is used to request a long connection identifier;

The IoT platform sends a response message to the application-layer device, where the response message carries M long-connection identifiers, M≥N.
The method according to any one of claims 8 to 12, wherein the establishment of N long-term connections between the IoT platform and an application layer device includes:

The IoT platform includes multiple distributed IoT platforms, and one or more of the multiple distributed IoT platforms establish the N long connections with the application layer device.
A communication device includes a processor, a memory, a transceiver, and a computer program stored on the memory and executable on the processor. The communication device controls the transceiver when the processor executes the program. Implement the method according to any of the preceding claims 1-7.
A communication device includes a processor, a memory, a transceiver, and a computer program stored on the memory and executable on the processor. The communication device controls the transceiver when the processor executes the program. Implement the method according to any one of the preceding claims 8-13.
A computer-readable storage medium, characterized in that it stores computer programs or instructions, and when the computer programs or instructions are run on a computer, the computer causes the computer to execute the method according to any one of claims 1-7 .
A computer-readable storage medium, characterized in that it is used to store a computer program or instructions, and when the computer program or instructions are run on a computer, cause the computer to execute the method according to any one of claims 8-13 .
A computer program product, wherein when the computer program product is run on a computer, the computer is caused to execute the method according to any one of claims 1-7.
A computer program product, wherein when the computer program product runs on a computer, the computer is caused to execute the method according to any one of claims 8-13.