Internet of Things Data Transfer Method and System

Abstract

A data transmission method and system for Internet of Things, the method includes the following downlink transmission steps: obtaining first downlink data distributed by an Internet of Things platform; analyzing the first downlink data to obtain a target meter and a transmission priority of the meter task in the first message; obtaining second downlink data; adding the second downlink data to an asynchronous distribution queue based on the transmission priority; and distributing the second downlink data to the target meter based on the asynchronous distribution queue so that the target meter completes the meter task, making full use of the role of an intermediate device of a concentrator and maintaining the integrity of core task data, while also reducing channel requirements due to asynchronous execution, particularly applicable to periodic meter tasks.

Description

[Technical field]

[0001] The present invention relates to the technical field of platform data collection for Internet of Things, and in particular to a method and system for transmitting data for Internet of Things. [Background technology]

[0002] The Internet of Things (abbreviated as IOT) refers to the real-time collection of any object or process that requires monitoring, connection, or interaction through a network of devices and technologies such as various information sensors, radio frequency identification technology, global positioning systems, infrared sensors, and laser scanners, and the collection of various necessary information such as sound, light, heat, electricity, mechanics, chemistry, biology, and location. Here, devices that collect information such as sound, light, heat, electricity, mechanics, chemistry, biology, and location are collectively called meters, and various meters within a fixed area communicate data with the Internet of Things platform through a concentrator.

[0003] Since different meters have various transmission protocols, how the Internet of Things system can communicate with different transmission protocols is a key point in building the Internet of Things. Traditionally, there are two main data transmission methods for the Internet of Things:

[0004] First, the Internet of Things platform performs message organization and message analysis only for a certain communication protocol, and the concentrator is responsible for operations compatible with various protocols, such as framework protocols such as MODBUSTCP, IEC104, and MQTT. Although this enhances the function of the concentrator, it causes the communication between the Internet of Things platform and the concentrator and the communication between the concentrator and the meter to be divided, so that the time flag when the data is obtained from the concentrator is not accurate, and the Internet of Things platform lacks the ability to remotely upgrade the base meter, the concentrator, and the meters below it, which is disadvantageous to function expansion.

[0005] The second type is to weaken the function of the concentrator, and form synchronous intercommunication between the Internet of Things platform, concentrator, and meter, with the concentrator only serving as a hardware interface for transparent transmission of data messages. For example, for the Q / GDW376.1 protocol, the Internet of Things platform uses the original message of the meter to communicate directly with the lowest-level meter, and the communication content is wrapped at the head and tail of the protocol message. The meter's unmarshaling of different protocols is completed by the Internet of Things platform. However, the synchronous collection method has high requirements for the real-time performance of the communication channel, and the collection is prone to errors. Especially for periodic meter tasks, the Internet of Things platform must actively start collection every time, and the role of the concentrator is ignored. Summary of the Invention [Problem to be solved by the invention]

[0006] The embodiment of the present invention aims to provide a data transmission method and system for the Internet of Things that not only solves the problem of upper and lower layer transmission division existing in the prior art, but also solves the problem of high requirements for synchronous transmission channels. [Means for solving the problem]

[0007] In view of this, an embodiment of the present invention provides a data transmission method and system for the Internet of Things, which is designed respectively from the Internet of Things platform side, the concentrator side, and the Internet of Things system side including the Internet of Things platform, the concentrator and the target meter, not only resolving the problem of upper and lower layer transmission division, but also solving the problem of high requirements for synchronous transmission channels.

[0008] A first form of an embodiment of the present invention provides an Internet of Things data transfer method including a downlink forwarding step, the downlink forwarding step comprising: a step of acquiring first downlink data distributed by an Internet of Things platform, the first downlink data including a first message generated by a first message format, a communication protocol message of a target meter, and a meter task; a step of analyzing the first downlink data to acquire a target meter and a transmission priority of the meter task in the first message; a step of acquiring second downlink data including the communication protocol message and meter task of the target meter; a step of adding the second downlink data to an asynchronous distribution queue based on the transmission priority; and a step of distributing the second downlink data to the target meter based on the asynchronous distribution queue so that the target meter completes the meter task.

[0009] A second form of the embodiment of the present invention provides an Internet of Things data transfer method, including a downlink transfer step and an uplink transfer step, wherein the downlink transfer step includes: a step of acquiring a meter task; a step of performing message format processing on the meter task according to a first message format and a communication protocol of a target meter, to generate first downlink data including a first message generated by the first message format, a communication protocol message of the target meter, and a meter task; and a step of distributing the first downlink data to a concentrator 8, so that the concentrator 8 analyzes and acquires second downlink data including the communication protocol message and meter task of the target meter, and sends the second downlink data to a corresponding target meter; and the uplink transfer step includes a step of acquiring second uplink data uploaded by the concentrator, wherein the second uplink data includes the first message formed by the first message format, the communication protocol message of the target meter, and a meter task result.

[0010] A third embodiment of the present invention provides an Internet of Things data transmission system, including an Internet of Things platform, M concentrators, and N types of meters, where M and N are all natural numbers, the Internet of Things platform includes: a first downlink data generation module for performing message format processing for a meter task based on the first message format to generate first downlink data, the first downlink data including a first message generated by the first message format, a communication protocol message of a target meter, and a meter task; and a first downlink data distribution module for distributing the first downlink data; the concentrator includes: a first downlink data acquisition module for acquiring the first downlink data distributed by the Internet of Things platform; a first downlink data analysis module for analyzing the first downlink data and acquiring a target meter and a transmission priority of the meter task; a second downlink data acquisition module for acquiring second downlink data including the communication protocol message and meter task of the target meter; and a second downlink data distribution module for transmitting the second downlink data to the corresponding target meter based on the transmission priority. An Internet of Things data transfer system comprising: a first uplink data acquisition module for acquiring first uplink data uploaded by the target meter, the first uplink data including a communication protocol message and a meter task result of the target meter; a second uplink data generation module for generating second uplink data including the first message and the first uplink data; and a second uplink data reporting module for reporting the second uplink data to the Internet of Things platform. Effect of the Invention

[0011] The advantageous effects of the embodiments of the present invention compared with the prior art are at least as follows: In the embodiments of the present invention, the concentrator queues meter tasks according to the priorities of different meter tasks and performs asynchronous execution, thus periodic tasks that need to be repeatedly executed can be completed and proactively reported by the concentrator independently, without the need to timely start the tasks by the Internet of Things platform every time, reducing the workload of the Internet of Things platform, making full use of the intermediate function of the concentrator, while maintaining the integrity of core task data, being less prone to errors, and the channel requirements are also reduced by asynchronous execution, and this method is particularly applicable to periodic meter tasks. [Brief description of the drawings]

[0012] In order to more clearly describe the technical solutions in the embodiments of the present invention, the following briefly introduces drawings required for describing the embodiments or prior art. Obviously, the drawings described below are only some embodiments of the present invention, and those skilled in the art can obtain other drawings based on these drawings without any creative work.

[0013] [Figure 1] FIG. 2 is a schematic diagram of the implementation process of the downlink forwarding step of the concentrator provided in an embodiment of the present invention; [Diagram 2] FIG. 2 is a schematic diagram illustrating the implementation process of the uplink forwarding step of the concentrator provided in the first embodiment of the present invention; [Diagram 3] FIG. 2 is a schematic diagram illustrating the implementation process of the uplink forwarding step of the concentrator provided in the second embodiment of the present invention; [Figure 4] FIG. 11 is a schematic diagram illustrating the implementation process of the step in which the concentrator provided in the second embodiment of the present invention responds to an inquiry about the task execution status from the Internet of Things platform. [Diagram 5] FIG. 2 is a schematic diagram of a complete implementation process of the Internet of Things platform downlink forwarding step provided in an embodiment of the present invention; [Figure 6] FIG. 11 is a schematic diagram of a complete implementation process of the step in which the Internet of Things platform provided in Example 2 of the present invention obtains the second uplink data uploaded by the concentrator. [Figure 7] FIG. 2 is a schematic diagram illustrating a complete implementation process of the step of the Internet of Things platform inquiring about the execution status of a task provided in Example 2 of the present invention; [Figure 8] FIG. 1 is a schematic diagram of an Internet of Things transmission system provided in an embodiment of the present invention. [Figure 9] FIG. 1 is a schematic configuration diagram of an Internet of Things transmission system provided in Example 1 of the present invention. [Figure 10] FIG. 1 is a schematic configuration diagram of an Internet of Things transmission system provided in Example 2 of the present invention. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0014] In the following description, specific details such as specific system structures, techniques, etc. are provided for the purpose of explanation, not limitation, to thoroughly understand the embodiments of the present invention. However, those skilled in the art should understand that the present invention can be realized in other embodiments without these specific details. In other cases, detailed descriptions of well-known systems, devices, circuits, and methods are omitted to avoid unnecessary details from obscuring the description of the present invention. All other embodiments obtained by those skilled in the art from the described embodiments of the present invention are within the scope of protection of the present invention. Unless otherwise specified, the technical means used in the embodiments are common means well known to those skilled in the art.

[0015] As used in this specification and the appended claims, the term "comprising" refers to the presence of stated features, wholes, steps, operations, elements and / or assemblies, but is to be understood as not excluding the presence or addition of one or more other features, wholes, steps, operations, elements, assemblies and / or combinations thereof.

[0016] Furthermore, the terminology used herein in the specification of the present application is for the purpose of describing particular embodiments only and is not intended to be limiting of the present application. As used in the specification of the present application and the appended claims, the singular forms "a," "one," and "the" should also be understood to include the plural forms unless the context clearly dictates otherwise.

[0017] Furthermore, the term "and / or" as used in the specification and appended claims of this application should be understood to refer to and include any and all possible combinations of one or more of the associated listed items.

[0018] As used herein and in the appended claims, the term "upon" can be interpreted as "when" or "once," or "responsive to determining" or "responsive to detecting," depending on the context. Similarly, the phrase "upon determining" or "upon detecting [a described condition or event]" can be interpreted to mean "once determining" or "responsive to determining," or "upon detecting [a described condition or event]," depending on the context.

[0019] In order to illustrate the technical solution described in the present invention, specific examples are given below.

[0020] Example 1 As shown in FIG. 8, this embodiment provides an Internet of Things data transmission system, which includes an Internet of Things platform 7, M concentrators 8, and N types of meters 9, where M and N are all natural numbers.

[0021] 9, the Internet of Things platform 7 includes a first downlink data generating module 71 and a first downlink data distributing module 72. Here, the first downlink data generating module 71 is used for performing message format processing for a meter task according to a first message format, and generating first downlink data, and the first downlink data distributing module 72 is used for distributing the first downlink data.

[0022] The concentrator 8 includes a first downlink data acquisition module 81, a first downlink data analysis module 82, a second downlink data acquisition module 83, a second downlink data distribution module 84, a first uplink data acquisition module 85, a second uplink data generation module 86, and a second uplink data reporting module 87. Here, the first downlink data acquisition module 81 is used for acquiring the first downlink data distributed by the Internet of Things platform 7, the first downlink data analysis module 82 is used for analyzing the first downlink data to acquire the target meter and transmission priority of the meter task, the second downlink data acquisition module 83 is used for acquiring second downlink data, the second downlink data distribution module 84 is used for sending the second downlink data to the corresponding target meter based on the transmission priority, the first uplink data acquisition module 85 is used for acquiring the first uplink data uploaded by the target meter, the second uplink data generation module 86 is used for generating second uplink data, and the second uplink data reporting module 87 is used for reporting the second uplink data to the Internet of Things platform 7.

[0023] In this embodiment, the meter 9 includes a second downlink data acquisition module 91 and a first uplink data uploading module 92, where the second downlink data acquisition module 91 is used to acquire the second downlink data distributed by the concentrator 8, and the first uplink data uploading module 92 is used to upload the first uplink data to the concentrator 8.

[0024] The data transfer method in this embodiment will now be described.

[0025] First, a specific data transmission implementation situation will be described in terms of the Internet of Things platform 7. That is, the Internet of Things data transmission method implemented by the Internet of Things platform 7 includes a downlink transmission step and an uplink transmission step. As shown in FIG. 5, the downlink transmission step: A step S401 of acquiring a meter task; S402: performing message format processing on a meter task according to a first message format and a communication protocol of a target meter, and generating first downlink data including a first message generated by the first message format, a communication protocol message of the target meter, and a meter task; and step S403 of distributing the first downlink data to the concentrator 8, so that the concentrator 8 analyzes and obtains second downlink data including a communication protocol message and a meter task of the target meter, and sends the second downlink data to the corresponding target meter.

[0026] Preferably, the first message format in this embodiment includes a present frame task quantity and a first data unit format for each meter task, and the first data unit format includes a task number, a task flag, a transmission priority, a report flag, a storage depth, a task start time, a task period attribute, a task period interval, a task end time, a communication protocol type, a rule option, a task scheduled response length, a task message length, and a task message content.

[0027] In this embodiment, the task flag indicates the need for task execution, preferably "00H" indicates that the task cannot be executed, "55H" indicates that the task is enabled, "AAH" indicates that the task is stopped, and other values ​​indicate that the task is disabled, and when the task is disabled, the task is deleted.

[0028] The send priority is the priority at which this task will be executed in the concentrator's asynchronous queue, with "00" preferably representing the lowest priority.

[0029] The report flag indicates the reporting status after the task is executed, and is preferably set as follows: “0” - no report, “1” - report immediately after the task is completed, “2” - report a task that has not been reported every day, “3” - report a task that has not been reported every hour, and the reporting format is AFN=0D,F306.

[0030] The storage depth is preferably a value between 0 and 255, and indicates storage of the results of the most recent few tasks, with "0" indicating storage of data for the most recent three days.

[0031] The task start time represents the start time when the task needs to be executed, and is preferably set to represent "99-99-99 99:99" according to the current time when the task is executed; otherwise, the task is executed periodically based on the specified time, and if there is an invalid time in the periodic execution, the task will not be executed in this period; when setting the alignment of the task start time, if the task start time is 1 o'clock and the task execution period is once per hour, the task execution result will be stored with "01:00", "02:00", "03:00" ... and so on, with "00" representing general purpose and valid for year, month, and day, and set to represent each year, month, and day, respectively.

[0032] The task periodic attribute represents the time unit of the periodic task execution, and preferably includes year, month, day, hour, minute, and second, as shown in FIG.

[0033] The task cycle interval is a specific interval value after the task cycle attribute is set, and is preferably set to a value range of 0 to 255, with "0" representing one-time execution.

[0034] The task end time indicates the final time of the task execution, i.e., the task ends when the task reaches the task end time. Preferably, "99-99-99 99:99" indicates the task end, and "00" indicates general purpose, which is valid for year, month and day, and can be set to indicate every year, month and day respectively.

[0035] The communication protocol type is the communication protocol of the target meter, and is preferably set as follows: "00H" is transparent protocol, "01H" is DL / T645-1997, "02H" is DL / T645-2007, "03H" is DL / T698.45, and others are extensible; The rule option is a preparation option description; The task planned response length is a response time interval from when the Internet of Things platform distributes a task to when the target meter finally receives the task, and the Internet of Things platform is set according to the demand of the task; The task message length is the data length of the task content; The task message content is the meter task.

[0036] The specific format of the first message format in this embodiment is set as shown in Table 1. JPEG0007624927000001.jpg212170

[0037] Here, BIN represents binary code, BS16 represents a combination of independent bits whose length is 16, and L1 represents the user data length.

[0038] Table 2 in Table 1 is as follows: JPEG0007624927000002.jpg51170

[0039] Table 3 in Table 1 is as follows: JPEG0007624927000003.jpg74170

[0040] In this embodiment, the Internet of Things platform 7 passively waits for data upload by the concentrator 8, but the uplink forwarding step is The step S500 includes acquiring second uplink data uploaded by the concentrator 8; The Internet of Things data transfer method, wherein the second uplink data includes a first message formed according to the first message format, a communication protocol message of the target meter, and a meter task result.

[0041] Next, a specific data transmission implementation situation will be described from the concentrator 8. That is, the Internet of Things data transmission method implemented by the concentrator 8 includes a downlink transmission step. Referring to FIG. 1, the downlink transmission step includes: Step S101: acquiring first downlink data distributed by the Internet of Things platform 7, the first downlink data including a first message generated by a first message format, a communication protocol message of a target meter, and a meter task; S102: analyzing the first downlink data to obtain a target meter and a transmission priority of the meter task in the first message; S103: acquiring second downlink data including a communication protocol message and a meter task of the target meter; S104 adding the second downlink data to an asynchronous distribution queue based on the transmission priority; and S105, distributing the second downlink data to the target meter according to the asynchronous distribution queue, so that the target meter completes the meter task.

[0042] In this embodiment, the method of wrapping the data that the target meter needs to process in a specific message format in the prior art is still adopted, and the transparent transmission of the upper and lower layers is performed, and the meter task that the target meter needs to execute and the corresponding different communication protocols are regarded as one whole data, that is, the second downlink data including the communication protocol message and the meter task of the target meter is obtained. The concentrator does not need to process the whole data, but only analyzes and transmits the first message, which is the specific message wrapped outside, so that the core task data is complete during the transmission process and is not easily affected, and the error rate during transmission can be greatly reduced. However, the conventional synchronous transparent transmission has very high requirements for the channel, and wraps the message information such as port, baud rate, check, etc. that need to be transmitted in addition to the task data, so that if any one of the problems occurs, such as the Internet of Things platform timeout or the concentrator timeout, the task will fail. As for the GPRS / CDMA and downlink carrier channels commonly used for the on-site uplink, neither has the advantage of the real-time nature of single communication for its own hardware technology. At the same time, the synchronous mode is disadvantageous for the concentrator to autonomously perform periodic collection of meters, and every time a task performed by the meter must be initiated by the Internet of Things platform, which increases the complexity of the Internet of Things platform for periodic meter tasks.

[0043] Therefore, in this embodiment, meter tasks are set in the Internet of Things platform and then distributed to the concentrator, and the concentrator queues the meter tasks according to the priorities of different meter tasks and executes them asynchronously. In this way, periodic tasks that need to be executed repeatedly can be completed and reported actively by the concentrator, without the need to timely start the tasks by the Internet of Things platform every time, reducing the workload of the Internet of Things platform, making full use of the intermediate function of the concentrator, while maintaining the integrity of core task data and being less prone to errors, and channel requirements are also reduced by asynchronous execution, and this method is particularly applicable to periodic meter tasks.

[0044] In addition, when the concentrator obtains the first downlink data distributed by the Internet of Things platform as a request for data communication, it needs to respond to the Internet of Things platform to confirm whether the data is received, and if it is received, it only needs to respond with a message to confirm, and if it is not received, it responds to reject the message. This response step is a standard setting in the communication protocol, so the description is omitted in this embodiment.

[0045] Table 1 above is the downlink data content of the new communication protocol proposed in this embodiment, which can meet the execution conditions of complex periodic tasks. The Internet of Things platform only needs to issue a task command once, and the periodically repeated meter task can be completed by the concentrator without needing to be re-distributed by the Internet of Things platform each time. In addition, the impact of different meter protocols on the concentrator is small, thereby realizing a more compatible communication mode for the three-way communication between the Internet of Things platform, the concentrator and the target meter.

[0046] In this embodiment, the concentrator 8 performs the downlink forwarding step and then performs the uplink forwarding step, as shown in FIG. 2 , the uplink forwarding step includes: S201: obtaining first uplink data uploaded by the target meter, the first uplink data including a communication protocol message and a meter task result of the target meter; generating second uplink data including the first message and the first uplink data; and a step S205 of spontaneously reporting the second uplink data to the Internet of Things platform 7.

[0047] Similarly, when reporting the status of meter task completion, the task message content in the first message can be correspondingly added to the meter task result, and second uplink data can be generated, and then spontaneously reported to the Internet of Things platform based on the reporting setting in the first message.

[0048] Example 2 As shown in FIG. 8, this embodiment provides an Internet of Things data transmission system, which includes an Internet of Things platform 7, M concentrators 8, and N types of meters 9, where M and N are all natural numbers.

[0049] As shown in Fig. 10, the Internet of Things platform 7 of this embodiment includes a first downlink data generating module 71, a first downlink data distributing module 72, a meter task query module 73 and a task running status query module 74. Wherein, the first downlink data generating module 71 is used for performing message format processing for a meter task according to a first message format, and generating first downlink data, the first downlink data distributing module 72 is used for distributing the first downlink data, the meter task query module 73 is used for generating a meter task query message according to a second message format and distributing the meter task query message to the concentrator, and the task running status query module 74 is used for generating a running status query message according to a third message format and distributing the running status query message to the concentrator.

[0050] The concentrator 8 includes a first downlink data acquisition module 81, a first downlink data analysis module 82, a second downlink data acquisition module 83, a second downlink data distribution module 84, a first uplink data acquisition module 85, a second uplink data generation module 86, a second uplink data reporting module 87, a meter task inquiry message analysis module 88, a execution status inquiry message acquisition module 89, a third uplink data generation module 810 and a third uplink data reporting module 811.Wherein, the first downlink data acquisition module 81 is used for acquiring the first downlink data distributed by the Internet of Things platform 7, the first downlink data analysis module 82 is used for analyzing the first downlink data to acquire the target meter and transmission priority of the meter task, the second downlink data acquisition module 83 is used for acquiring the second downlink data, the second downlink data distribution module 84 is used for transmitting the second downlink data to the corresponding target meter according to the transmission priority, the first uplink data acquisition module 85 is used for acquiring the first uplink data uploaded by the target meter, the second uplink data generation module 86 is used for generating the second uplink data, and the second The uplink data reporting module 87 is used for reporting the second uplink data to the Internet of Things platform 7, the meter task inquiry message analysis module 88 is used for analyzing the meter task inquiry message, the running status inquiry message acquisition module 89 is used for acquiring the running status inquiry message distributed by the Internet of Things platform, the third uplink data generation module 810 is used for analyzing the running status inquiry message and generating third uplink data based on a fourth message format, and the third uplink data reporting module 811 is used for reporting the third uplink data to the Internet of Things platform.

[0051] In this embodiment, the meter 9 includes a second downlink data acquisition module 91 for acquiring the second downlink data distributed by the concentrator 8, and a first uplink data upload module 92 for uploading the first uplink data to the concentrator 8, as shown in FIG. 10.

[0052] The data transfer method in this embodiment will now be described.

[0053] First, a specific data transmission implementation situation will be described in terms of the Internet of Things platform 7. That is, the Internet of Things data transmission method implemented by the Internet of Things platform 7 includes a downlink transmission step and an uplink transmission step. As shown in FIG. 5, the downlink transmission step: A step S401 of acquiring a meter task; Step S402: performing message format processing for a meter task according to a first message format and a communication protocol of a target meter to generate first downlink data; Step S403 of distributing the first downlink data to the concentrator 8, so that the concentrator 8 analyzes and obtains the second downlink data, and sends the second downlink data to the corresponding target meter.

[0054] Similarly, the first message format in this embodiment includes a present frame task quantity and a first data unit format for each meter task, and the first data unit format includes a task number, a task flag, a transmission priority, a report flag, a storage depth, a task start time, a task period attribute, a task period interval, a task end time, a communication protocol type, a rule option, a task scheduled response length, a task message length, and a task message content.

[0055] The specific format of the first message format in this embodiment is set as shown in Tables 1, 2 and 3.

[0056] Different from the first embodiment, the Internet of Things platform 7 in this embodiment collects the second uplink data autonomously, as shown in FIG. 6 : A step S501 of generating a meter task query message based on a second message format; a step S502 of distributing the meter task query message to the concentrator 8; and a step S503 of acquiring the second uplink data reported by the concentrator 8.

[0057] Here, the second message format includes the inquiry task quantity and each inquiry task number, referring to Table 4 below. JPEG0007624927000004.jpg52170

[0058] As can be seen, the Internet of Things platform can query multiple data at one time when collecting autonomously. Preferably, when the query task quantity is "0", there is no need to specify a task number, and it may be set to represent all tasks of the query measurement point, and when querying a specific task, the query task number needs to be entered.

[0059] Similarly, to be distinguished from the first embodiment, the present embodiment further includes a step of inquiring about the task execution status. As shown in FIG. 7, the step of inquiring about the task execution status includes: Step S601 of generating an execution status inquiry message based on a third message format; A step S602 of distributing the execution status inquiry message to the concentrator 8; Step S603 of obtaining third uplink data reported by the concentrator 8, where the third uplink data is generated by the concentrator 8 according to a fourth message format.

[0060] Preferably, the third message format in this embodiment includes a task number, a query start time, and a query end time, see Table 5 below. JPEG0007624927000005.jpg42170

[0061] That is, the task execution status from time T1 to time T2 is inquired.

[0062] The fourth message format in this embodiment includes a task number, a current frame point number, and a second data unit format for each task completion, where the second data unit format includes a task time, a task response message length, a task completion time, and a task response frame. See Table 6 below. JPEG0007624927000006.jpg98170

[0063] Here, the task response frame represents the response data when the task is executed, and its number of bytes is the sum of the length of the completion time of the task message q and the length of the task message q response frame. In this embodiment, when the query task is not being executed, the overall response is “00”.

[0064] Next, a specific data transmission implementation situation will be described from the concentrator 8. That is, the Internet of Things data transmission method implemented by the concentrator 8 includes a downlink transmission step. Referring to FIG. 1, the downlink transmission step includes: Step S101: acquiring first downlink data distributed by the Internet of Things platform 7, the first downlink data including a first message generated by a first message format, a communication protocol message of a target meter, and a meter task; S102: analyzing the first downlink data to obtain a target meter and a transmission priority of the meter task in the first message; S103: acquiring second downlink data including a communication protocol message and a meter task of the target meter; S104 adding the second downlink data to an asynchronous distribution queue based on the transmission priority; and S105, distributing the second downlink data to the target meter according to the asynchronous distribution queue, so that the target meter completes the meter task.

[0065] Different from the first embodiment, in this embodiment, after the concentrator 8 performs the downlink transmission step, it passively waits for the second uplink data to be collected by the Internet of Things platform 7 when performing the uplink transmission step. As shown in FIG. 3, S201: obtaining first uplink data uploaded by the target meter, the first uplink data including a communication protocol message and a meter task result of the target meter; generating second uplink data including the first message and the first uplink data; S203: obtaining a meter task query message generated by the Internet of Things platform 7 according to a second message format and distributed by the Internet of Things platform 7; S204: analyzing the meter task inquiry message and reporting the corresponding second uplink data to the Internet of Things platform 7; and a step S205 of reporting the second uplink data to the Internet of Things platform 7.

[0066] Referring to the above-mentioned step of the Internet of Things platform 7 inquiring about the task execution status in this embodiment, after the concentrator 8 performs the downlink transmission step, the concentrator 8 further includes a step of responding to the inquiry of the task execution status by the Internet of Things platform 7. Referring to FIG. 4, the step of responding to the inquiry of the task execution status by the Internet of Things platform 7 includes: S301: obtaining an execution status inquiry message generated by the Internet of Things platform 7 according to a third message format and distributed by the Internet of Things platform 7; S302: analyzing the execution status inquiry message to generate corresponding third uplink data generated by the concentrator 8 according to a fourth message format; and step S303 of reporting the third uplink data to the Internet of Things platform 7.

[0067] This embodiment provides a complete communication protocol, especially suitable for meter tasks that are executed periodically, and only requires three commands: meter task setting (adding the first message), meter task query, and task execution status query, which is compatible with meter data collection of all kinds of protocols, reduces the software dependency on the middle-layer data concentrator, and leaves the complexity to the Internet of Things platform, which is convenient for remote operation and maintenance, modification and expansion. It reduces the technical difficulty and complexity of the bottom layer site, and avoids the impact of the instability of the bottom layer on the data collection success rate and data quality. It is ingenious in terms of the extension of the concentrator hardware interface and the protocol compatibility of the Internet of Things platform, and the completeness of the protocol implementation.

[0068] Those skilled in the art can clearly understand that for convenience and simplicity of explanation, only the division of each of the above functional units and modules is described as an example, and in actual applications, the above functions can be assigned to different functional units and modules to be completed as necessary, that is, all or part of the above-described functions can be completed by dividing the internal structure of the device into different functional units or modules. Of course, each of the above units and modules can be replaced by a processor including a computer program, and the operation of each part is completed in the form of pure software. Each of the functional units and modules in the embodiments may be integrated into one processing unit, each unit may exist physically alone, or two or more units may be integrated into one unit, and the integrated unit may be realized in the form of hardware or software functional unit. In addition, the specific names of each functional unit and module are also provided for easy distinction from each other, and do not limit the scope of protection of the present application. For the specific operation processes of the units and modules in the above system, reference may be made to the corresponding processes in the embodiments of the above method, and the description will be omitted here. In the above embodiments, the description of each embodiment has its own emphasis, and for the details or parts not described in an embodiment, reference may be made to the relevant descriptions of other embodiments.

[0069] Those skilled in the art can be aware that each example unit and algorithm step described in the embodiments disclosed herein can be realized in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software is determined by the specific application and design constraints of the technical solution. Those skilled in the art may use different methods to realize the described functions for each specific application, but such realization should not be considered to go beyond the scope of the present invention.

[0070] In the embodiments of the present invention, it should be understood that the disclosed device / terminal and method can be realized in other ways. For example, the above-described embodiments of the device / terminal are merely exemplary, and the division of the modules or units is merely a logical functional division. In actual implementation, other division methods may be applied, for example, multiple units or components may be combined or integrated into other systems, or some features may be ignored or not implemented. In addition, the couplings or direct couplings or communication connections between the units shown or discussed may be indirect couplings or communication connections through several interfaces, devices or units, and may be electrical, mechanical or other types. The units described as separate elements may or may not be physically separated, and the elements shown as units may or may not be physical units, i.e., they may be located in one place or distributed across multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of the embodiment.

[0071] In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, each unit may exist physically alone, or two or more units may be integrated into one unit. The integrated unit may be realized in the form of hardware or in the form of a software functional unit. When the integrated module / unit is realized in the form of a software functional unit and sold or used as an independent product, it may be stored in a computer-readable storage medium. With this understanding, the present invention can be realized by instructing related hardware by a computer program to realize all or part of the processes in the methods of the above embodiments, and the above computer program can be stored in a computer-readable storage medium, and when the computer program is executed by a processor, the steps of each of the above method embodiments can be realized. Here, the computer program includes a computer program code, and the computer program code may be in a source code format, an object code format, an executable file, or some intermediate format, etc. The computer readable medium may include any entity or device capable of carrying the computer program code, such as a recording medium, a U-disk, a removable hard disk, a magnetic disk, an optical disk, a computer memory, a read-only memory (ROM), a random access memory (RAM), an electrical carrier wave signal, an electrical communication signal, and a software distribution medium, etc. It should be noted that the content included in the computer readable medium may be appropriately increased or decreased as required by the legislation and patent practice in a jurisdiction, for example, in some jurisdictions, based on the legislation and patent practice, the computer readable medium does not include electrical carrier wave signals and electrical communication signals.

[0072] The above embodiments are only for illustrating the technical solutions of the present invention, and are not intended to limit the same. Although the present invention has been described in detail with reference to the above embodiments, those skilled in the art should understand the following: It is still possible to amend the technical solutions described in the above embodiments, or to equivalently replace some technical features therein. These amendments or replacements ensure that the substance of the corresponding technical solutions does not deviate from the spirit and scope of the technical solutions of the embodiments of the present invention, and all of them should be included in the protection scope of the present invention.

Claims

1. A downlink transfer step, the downlink transfer step comprising: Obtaining first downlink data distributed by an Internet of Things platform, the first downlink data including a first message generated by a first message format, a communication protocol message of a target meter, and a meter task; Analyzing the first downlink data to obtain a target meter and a transmission priority of the meter task in the first message; acquiring second downlink data including communication protocol messages and meter tasks of the target meter; adding the second downlink data to an asynchronous distribution queue based on the transmission priority; Distributing the second downlink data to the target meter according to the asynchronous distribution queue, so that the target meter completes the meter task; The Internet of Things data transfer method, wherein the first message format includes a present frame task quantity and a first data unit format for each meter task.

2. the first data unit type includes at least one of a task number, a task flag, a transmission priority, a report flag, a storage depth, a task start time, a task period attribute, a task period interval, a task end time, a communication protocol type, a rule option, a task scheduled response length, a task message length, and a task message content; The Internet of Things data transfer method according to claim 1 , wherein the first data unit type includes at least the transmission priority.

3. After the downlink transfer step, the method further includes an uplink transfer step, the uplink transfer step comprising: Obtaining first uplink data uploaded by the target meter, the first uplink data including communication protocol messages and meter task results of the target meter; generating second uplink data comprising the first message and the first uplink data; and reporting the second uplink data to the Internet of Things platform.

4. The step of reporting the second uplink data to the Internet of Things platform further comprises: Obtaining a meter task query message distributed by the Internet of Things platform, the meter task query message being generated by the Internet of Things platform according to a second message format; and parsing the meter task inquiry message and reporting the corresponding second uplink data to the Internet of Things platform.

5. After the downlink forwarding step, the method further includes a step of responding to an Internet of Things platform querying a task execution status, and the step of responding to an Internet of Things platform querying a task execution status includes: Obtaining an execution status inquiry message generated by the Internet of Things platform according to a third message format and distributed by the Internet of Things platform; parsing the execution status inquiry message to generate corresponding third uplink data generated by a concentrator according to a fourth message format; and reporting the third uplink data to the Internet of Things platform.

6. the third message format includes a task number, a query start time, and a query end time; The Internet of Things data transfer method according to claim 5, wherein the fourth message format includes a task number, a current frame point number, and a second data unit format for each meter task completed.

7. The Internet of Things data transfer method of claim 6 , wherein the second data unit format includes a task time, a task response message length, a task completion time, and a task response frame.

Images