Device data transmission method, device and system

Abstract

The present invention provides a device data transmission method, apparatus and system, and relates to the field of data processing technology. The method comprises: parsing and processing the received data to be transmitted to obtain target data; determining the function point type corresponding to the data to be transmitted according to the target data, wherein the function point type comprises a custom function point and a system function point; and verifying the data to be transmitted according to the function point type. The device data transmission method of the embodiment of the present invention verifies the data to be transmitted before uploading or sending the data, filters out the erroneous data, and only the verified data can be transmitted. This solves the problem that the data uploaded by the device is not verified, and the erroneous data is directly stored or forwarded after being uploaded; or the data to be sent to the device by the platform is sent without verification, thereby improving the correctness and security of data transmission.

Description

Technical Field

[0001] The present invention relates to the field of data processing technology, and in particular to a device data transmission method, device and system. Background Art

[0002] After the device is connected to the IoT platform, data can be transmitted between the device and the IoT platform, and data can be reported to the platform and sent from the platform to the device. The usual steps for the current device to report data to the platform are: first define the data format that needs to be uploaded for your device; secondly, implement the device's adaptation module; then connect the device to the platform to upload data; finally, store or retransmit the uploaded data. Therefore, in the current IoT platform, the data reporting system has no retransmission mechanism or the retransmission mechanism is relatively complex, and it is difficult to ensure the correctness of the data. In addition, the data reporting system is prone to data loss when the amount of reported data is large. The data uploaded by the device is not verified, and the erroneous data will be directly stored or retransmitted after uploading, or the data to be sent to the device by the platform is not verified. Summary of the invention

[0003] The purpose of the present invention is to provide a device data transmission method, apparatus and system to solve the problems in the prior art that the data uploaded to the device is not verified, the erroneous data is directly stored or forwarded again after being uploaded, or the data to be sent to the device by the platform is not verified.

[0004] To achieve the above object, an embodiment of the present invention provides a device data transmission method, comprising:

[0005] Parse and process the received data to be transmitted to obtain target data;

[0006] Determine the function point type corresponding to the data to be transmitted according to the target data, the function point type including a user-defined function point and a system function point;

[0007] The data to be transmitted is verified according to the function point type.

[0008] Furthermore, the target data includes: attribute parameters of the device.

[0009] Further, the determining the function point type corresponding to the data to be transmitted according to the target data includes:

[0010] If the identification symbol in the attribute parameter is a preset symbol, the data to be transmitted corresponds to a system function point;

[0011] If the identification symbol in the attribute parameter is not a preset symbol, the data to be transmitted corresponds to a user-defined function point.

[0012] Furthermore, before determining the function point type corresponding to the data to be transmitted, the method includes:

[0013] At least one custom function point template is generated according to the same attributes and events of multiple devices.

[0014] Further, the verifying the data to be transmitted according to the function point type includes:

[0015] If the data to be transmitted corresponds to a system function point, verifying the data to be transmitted according to a system function point template;

[0016] If the data to be transmitted corresponds to a user-defined function point, a first function point template in the user-defined function point template is obtained according to the identification symbol in the attribute parameter, and the data to be transmitted is verified according to the first function point template.

[0017] Further, in the case where the data to be transmitted is data to be uploaded, before determining the function point type corresponding to the data to be transmitted, the method further includes:

[0018] Obtain the ID and version number of the data to be transmitted;

[0019] It is determined according to the target data whether the ID and version number of the data to be transmitted meet the preset requirements.

[0020] Furthermore, the determining whether the ID and version number of the data to be transmitted meet preset requirements includes:

[0021] If the character length of the ID of the data to be transmitted is equal to the preset length and the version number of the data is the preset version number, it is determined that the ID and version number of the data to be transmitted meet the preset requirement;

[0022] If the character length of the ID of the data to be transmitted is different from the preset length and / or the version number of the data is different from the preset version number, it is determined that the ID and version number of the data to be transmitted do not meet the preset requirement.

[0023] The embodiment of the present invention further provides a device data transmission apparatus, including:

[0024] The parsing module is used to parse the received data to be transmitted to obtain the target data;

[0025] A determination module, used to determine the function point type corresponding to the data to be transmitted according to the target data, wherein the function point type includes a custom function point and a system function point;

[0026] A verification module is used to verify the data to be transmitted according to the function point type.

[0027] Furthermore, the device also includes:

[0028] The generation module is used to generate at least one custom function point template according to the same attributes and events of multiple devices.

[0029] An embodiment of the present invention further provides a device data transmission system, comprising: the device data transmission apparatus as described above.

[0030] The beneficial effects of the above technical solution of the present invention are as follows:

[0031] The device data transmission method of the embodiment of the present invention parses and processes the received data to be transmitted to obtain target data, and converts the data to be transmitted into data in a preset format; determines the function point type corresponding to the data to be transmitted according to the target data, and the function point type includes a custom function point and a system function point; determines the function point type corresponding to the data to be transmitted according to the data in the preset format, and verifies the target data according to the function point type. The device data transmission method of the embodiment of the present invention verifies the data to be transmitted before uploading or sending the data, and only the verified data can be transmitted. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] Figure 1 A schematic diagram of a flow chart of a device data transmission method according to an embodiment of the present invention;

[0033] Figure 2 A schematic diagram of the structure of a device data transmission system according to an embodiment of the present invention;

[0034] Figure 3 A schematic diagram of a module of a device data transmission apparatus according to an embodiment of the present invention;

[0035] Figure 4 A logical schematic diagram of a device data uploading method according to an embodiment of the present invention;

[0036] Figure 5 The figure is a logical diagram of a method for sending device data according to an embodiment of the present invention. DETAILED DESCRIPTION

[0037] In order to make the technical problems, technical solutions and advantages to be solved by the present invention more clear, a detailed description will be given below with reference to the accompanying drawings and specific embodiments.

[0038] It should be understood that the references to "one embodiment" or "an embodiment" throughout the specification mean that the specific features, structures, or characteristics associated with the embodiment are included in at least one embodiment of the present invention. Therefore, the references to "in one embodiment" or "in an embodiment" appearing throughout the specification do not necessarily refer to the same embodiment. In addition, these specific features, structures, or characteristics may be combined in any suitable manner in one or more embodiments.

[0039] In various embodiments of the present invention, it should be understood that the size of the serial numbers of the following 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 constitute any limitation on the implementation process of the embodiments of the present invention.

[0040] Additionally, the terms "system" and "network" are often used interchangeably herein.

[0041] In the embodiments provided in the present application, it should be understood that "B corresponding to A" means that B is associated with A, and B can be determined according to A. However, it should also be understood that determining B according to A does not mean determining B only according to A, and B can also be determined according to A and / or other information.

[0042] like Figure 1 As shown, a device data transmission method according to an embodiment of the present invention includes the following steps:

[0043] Step 101, parsing the received data to be transmitted to obtain target data;

[0044] Step 102, determining the function point type corresponding to the data to be transmitted according to the target data, the function point type including a user-defined function point and a system function point;

[0045] Step 103: verify the data to be transmitted according to the function point type.

[0046] In one embodiment of the present invention, the device data transmission method can be implemented by an Internet of Things device data transmission system, such as Figure 2 As shown, the system includes:

[0047] Data processing services and data format definition modules;

[0048] The data processing service is used to parse and verify the received data to be transmitted;

[0049] The data format definition module is used to generate at least one custom function point template according to the same attributes and events possessed by multiple devices.

[0050] The parsing of the data to be transmitted can be understood as converting the data to be transmitted into data in a preset format. In one embodiment of the present invention, the preset format is a JSON format;

[0051] The devices that users need to report data points are generally in batches. The same attributes and events of multiple devices can be abstracted and defined as function point templates. In this way, users only need to define it once and it can be used by multiple devices. They can also use the built-in system function points of the IoT platform. The built-in system function points can be used directly without definition. Users can edit, delete, and copy the function points they define. When another batch of devices also need this function point or a similar function point, users can copy it and then make appropriate modifications to achieve the purpose. The operation is extremely convenient.

[0052] The IoT device data transmission system provides users with a web interface to define the function points of the device. When users select custom function points, they need to fill in the function point type, function name, function identifier, data type (for example, int32, int64, float, double, string, enum, struct, bitMap, bool), read and write type. When the data type is a numeric type, the value range needs to be defined, and the step size and unit are optional; when the data type is string, the data length needs to be defined; when the data type is Bool, the meanings of true and false need to be defined respectively; when the data type is enumeration enum, the meaning of each enumeration value needs to be defined; when the data type is bitmap bitMap, the meanings of binary bits 0 and 1 need to be defined as needed. The data format definition module converts the defined function points into JSON format, calls the remote call module interface of the data processing module through remote call, and calls the verification module interface through the Dubbo protocol to verify the function point template and store it in the database. When users select system function points, there is no need to define them. The system function point format is similar to the custom function point format, and can be used directly by selecting them.

[0053] Function points include properties and events, both in JSON format.

[0054] As shown in Table 1:

[0055]

[0056] Table 1 Function point format

[0057] Among them, properties represent attributes, events represent events, a property value has only one parameter, an event can have multiple parameters, and events also include three types: information, fault, and alarm.

[0058] The Internet of Things device data transmission system also includes:

[0059] Device connection service, device adaptation module and data delivery module;

[0060] The device connection service is connected to the data processing service via an open source distributed service interface (e.g., a Dubbo protocol interface);

[0061] The device connection service is used to connect different devices and perform data transmission between the connected devices.

[0062] Device adaptation module: Different users' devices use different protocols to access the platform, and the device adaptation module is used to connect devices with different protocols, shielding the differences in device protocols, so that the data reported by devices with different protocols can flow into the data processing service.

[0063] The data delivery module mainly provides two functions: setting attributes for the device and setting expected attribute values ​​for the device. The module points to the template based on the functions defined by the user for the device, and provides a web interface for the user to enter attribute values ​​and send them to the device or set expected values ​​for the device.

[0064] The JSON format for setting attribute values ​​is shown in Table 2, where ID is a string type with a length of 13 bits and is defined by the platform. The ID number of each message is unique in the current device. Version is the version number, which defaults to 1.0. Params is the attribute value map.

[0065]

[0066] Table 2 Setting attribute format

[0067] In the system, data processing service is the key service to realize the reporting and sending of device data. The service includes remote call module grpc, verification module, remote dictionary service redis cluster and database device. Among them, grpc module and verification module are the core of data processing service. The two modules are connected through Dubbo interface. The grpc module mainly provides interface service for data definition module, and the verification service mainly provides interface service for device adaptation module. However, when grpc module provides service for data definition module, it needs the related service support of verification module, which can be easily realized by using Dubbo interface. On the other hand, the layering of data format definition module, data processing service and device adaptation module, when the number of devices is large and the number of requests of grpc module is large, the number of verification modules can be increased to realize the horizontal expansion of the system, to process the data uploaded by the device and the data sent to the device, to ensure that the data is not lost, and at the same time, the function point template is cached by redis, which can speed up the verification of data and ensure the real-time nature of the data. In addition, Dubbo also provides a service registration center. When other modules call the verification module, there is no need to hard-code the address of the verification module. The registration center can automatically query the verification module IP based on the interface name, allowing other modules to call remote methods like calling local methods. Only simple configuration is required, without any API intrusion. Dubbo also integrates an automatic retransmission mechanism. When the interface call fails, it will automatically retry to ensure the integrity of the reported and sent data.

[0068] Optionally, after determining that the data to be transmitted has passed verification, the data is transmitted to the Internet of Things device through the data sending module.

[0069] The device data transmission method of the embodiment of the present invention parses and processes the received data to be transmitted to obtain target data, and converts the data to be transmitted into data in a preset format; determines the function point type corresponding to the data to be transmitted according to the target data, and the function point type includes a custom function point and a system function point; determines the function point type corresponding to the data to be transmitted according to the data in the preset format, and verifies the target data according to the function point type. The device data transmission method of the embodiment of the present invention verifies the data to be transmitted before uploading or sending the data, and only the verified data can be transmitted.

[0070] Optionally, the target data includes: attribute parameters of the device.

[0071] Optionally, the attribute parameter includes attribute reporting or attribute sending time and attribute value, and the function point type corresponding to the data to be transmitted is determined by the attribute value.

[0072] Optionally, determining the function point type corresponding to the data to be transmitted according to the target data includes:

[0073] If the identification symbol in the attribute parameter is a preset symbol, the data to be transmitted corresponds to a system function point;

[0074] If the identification symbol in the attribute parameter is not a preset symbol, the data to be transmitted corresponds to a user-defined function point.

[0075] In one embodiment of the present invention, the data processing service of the IoT device data transmission system includes:

[0076] Remote call module, verification module, remote dictionary service module and database;

[0077] The remote call module and the verification module, the verification module and the remote dictionary service module, and the remote dictionary service module and the database are all connected via an open source distributed service interface;

[0078] The remote calling module is used to call the verification module to verify the data to be transmitted;

[0079] The remote dictionary service module is used to cache function point templates.

[0080] Remote call module: This module provides interfaces for adding, modifying, deleting, copying and obtaining function points for the data definition module, and interfaces for setting device attributes and setting expected values ​​for device attributes for the data delivery module. It also provides interfaces for obtaining device expected values ​​and deleting device expected values ​​for the device adaptation module. The remote call module interacts with the verification module using Dubbo, and interacts with other modules using remote calls.

[0081] Verification module: This module is the core module of the data processing module, and mainly interacts with the remote call module and the device adapter module through Dubbo. The specific implementation of the interface provided by the remote call module to other modules is realized through the verification module. Among them, the interface for the remote call module to operate the function point is realized by the verification module to add, delete, modify and query the database. The device attribute setting is issued by the verification module through Dubbo calling the device adapter module. The device expected value setting is that the verification module stores the expected value in the remote dictionary service for the device adapter module to obtain. The acquisition and deletion of the device expected value are realized by querying and deleting the remote dictionary service through the verification module. The device adapter module calls the attribute or event verification interface of the verification service through the Dubbo interface to upload the device's attributes or event values. The verification service verifies the data. If the verification passes, the data is sent to the kafka message system for use by other services on the platform. If the verification fails, an error message is returned to the device adapter module.

[0082] The system uses Dubbo to connect the device adapter module and the verification module, which is convenient for module expansion. When the number of devices is too large, the number of verification modules can be increased, and a large amount of data uploaded by a large number of devices can be received. At the same time, the use of Dubbo and redis cache function point templates can quickly process data and send it to kafka, ensuring real-time reporting and storage of data.

[0083] Optionally, before determining the function point type corresponding to the data to be transmitted, the method includes:

[0084] At least one custom function point template is generated according to the same attributes and events of multiple devices.

[0085] In one embodiment of the present invention, the generation of the custom function point template is implemented by the data definition module.

[0086] The device data transmission method of the embodiment of the present invention provides a method for defining a set of attributes and event function points for multiple devices by generating a custom function point template. It only needs to be defined once, and multiple devices can use this defined function point template to report data. In addition, the system function points are also customized, and users can directly use the system function points without definition.

[0087] Optionally, the verifying the data to be transmitted according to the function point type includes:

[0088] If the data to be transmitted corresponds to a system function point, verifying the data to be transmitted according to a system function point template;

[0089] If the data to be transmitted corresponds to a user-defined function point, a first function point template in the user-defined function point template is obtained according to the identification symbol in the attribute parameter, and the data to be transmitted is verified according to the first function point template.

[0090] In one embodiment of the present invention, the function point template cached in the remote dictionary service or stored in the database is called by the verification module.

[0091] The device data transmission method of an embodiment of the present invention verifies the data to be transmitted by using the pre-generated system function point template and the custom function point template, thereby improving the correctness and security of data transmission.

[0092] Optionally, when the data to be transmitted is data to be uploaded, before determining the function point type corresponding to the data to be transmitted, the method further includes:

[0093] Obtain the ID and version number of the data to be transmitted;

[0094] It is determined according to the target data whether the ID and version number of the data to be transmitted meet the preset requirements.

[0095] ID is a user-defined string, for example, its length is 13, and version is the version number, which can be 1.0.

[0096] Optionally, the determining whether the ID and version number of the data to be transmitted meet preset requirements includes:

[0097] If the character length of the ID of the data to be transmitted is equal to the preset length and the version number of the data is the preset version number, it is determined that the ID and version number of the data to be transmitted meet the preset requirement;

[0098] If the character length of the ID of the data to be transmitted is different from the preset length and / or the version number of the data is different from the preset version number, it is determined that the ID and version number of the data to be transmitted do not meet the preset requirement.

[0099] In the device data transmission method of an embodiment of the present invention, when the data to be transmitted is data to be uploaded, before verifying the data to be uploaded, it is first necessary to verify the ID and version number of the data to be transmitted. Only the data to be transmitted that has been verified by the ID and version number can be verified, and data transmission can be performed only after erroneous data is filtered out.

[0100] like Figure 3 As shown, the embodiment of the present invention further provides a device data transmission apparatus 300, comprising:

[0101] The parsing module 301 is used to parse the received data to be transmitted to obtain target data;

[0102] A determination module 302 is used to determine the function point type corresponding to the data to be transmitted according to the target data, and the function point type includes a user-defined function point and a system function point;

[0103] The verification module 303 is used to verify the data to be transmitted according to the function point type.

[0104] The device data transmission apparatus of the embodiment of the present invention parses and processes the received data to be transmitted to obtain target data, and converts the data to be transmitted into data in a preset format; determines the function point type corresponding to the data to be transmitted according to the target data, and the function point type includes a custom function point and a system function point; determines the function point type corresponding to the data to be transmitted according to the data in the preset format, and verifies the target data according to the function point type. The device data transmission method of the embodiment of the present invention verifies the data to be transmitted before uploading or sending the data, and only the verified data can be transmitted.

[0105] Optionally, the device further comprises:

[0106] The generation module is used to generate at least one custom function point template according to the same attributes and events of multiple devices.

[0107] An embodiment of the present invention further provides a device data transmission system, comprising: the device data transmission apparatus as described above.

[0108] The device data transmission system of the embodiment of the present invention parses and processes the received data to be transmitted to obtain target data, and converts the data to be transmitted into data in a preset format; determines the function point type corresponding to the data to be transmitted according to the target data, and the function point type includes a custom function point and a system function point; determines the function point type corresponding to the data to be transmitted according to the data in the preset format, and verifies the target data according to the function point type. The device data transmission method of the embodiment of the present invention verifies the data to be transmitted before uploading or sending the data, and only the verified data can be transmitted.

[0109] like Figure 4 As shown, the device data transmission method according to an embodiment of the present invention may be a device data upload method:

[0110] Step 1: Receive the data uploaded by the device in JSON format, which includes device attributes and events. Convert the data according to the attribute and event templates. If the conversion is successful, continue to the next step. If it fails, return an error message to the device.

[0111] The JSON format of the uploaded data is shown in Table 3:

[0112]

[0113]

[0114] Table 3 Upload attribute format

[0115] Among them, ID is the unique identifier defined by the user for each message of his or her device; version is an optional field. If this field exists, it can only be 1.0; params is the upload request parameter, including multiple attribute values, such as Power, each attribute parameter contains value and time; value is the attribute value, and time is the data upload time. It should be noted that the IoT device data transmission system supports the simultaneous uploading of multiple attributes of the device.

[0116] The JSON format of event data is similar to that of attributes, with the same ID and version, but each attribute value in params can contain multiple attributes. The IoT device data transmission system supports uploading multiple events of a device at the same time.

[0117] Step 2: Determine whether the ID and version of the data meet the requirements. ID is a user-defined string (for example, the length is 13), and version is the version number. Currently, only 1.0 is supported. If the verification passes, continue to the following steps. If it fails, an error message is returned to the device.

[0118] Step 3: If the identifier of the attribute parameter contains a $ sign, the attribute is a system function point. The data type length is directly verified according to the system function point template. If it is not a system function point, the custom function point template in the cache is obtained according to the identifier. If it does not exist in the cache, the database is read and the function point of the identifier is stored in the cache. The attribute and event parameters are verified separately according to the function point template. If the verification is successful, continue to step 4, otherwise an error message is returned to the device.

[0119] Step 4: Send the data uploaded by the device to Kafka for use by other services, and return the correct response to the device.

[0120] like Figure 5 As shown, the device data transmission method according to an embodiment of the present invention may be a device data sending method:

[0121] Step 1: Convert the attribute value filled in by the user into JSON format according to the JSON template of the device attribute. If the conversion is successful, continue with the following steps. If it fails, the error reason is returned.

[0122] Step 2: Verify the set attribute value using the same data verification method as the device data upload method. If the verification is successful, continue with the following steps. If the verification fails, directly return the error reason.

[0123] Step 3: Send the data to the device through the device adapter module and wait for the device to respond. If the device returns success, it returns success. If it fails, it returns the reason for failure.

[0124] A readable storage medium according to an embodiment of the present invention stores a program or instruction thereon. When the program or instruction is executed by a processor, the steps in the device data transmission method described above are implemented and the same technical effect can be achieved. To avoid repetition, it will not be described here.

[0125] The readable storage medium includes a computer-readable storage medium, such as a computer read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0126] It should be further explained that the terminals described in this specification include but are not limited to smart phones, tablet computers, etc., and many of the functional components described are called modules in order to more particularly emphasize the independence of their implementation methods.

[0127] In the embodiment of the present invention, module can be implemented with software so that it can be executed by various types of processors. For example, an executable code module of an identification can include one or more physical or logical blocks of computer instructions, for example, it can be constructed as an object, process or function. Nevertheless, the executable code of the identified module does not need to be physically located together, but can include different instructions stored in different positions, and when these instructions are logically combined together, it constitutes a module and realizes the specified purpose of the module.

[0128] In fact, executable code module can be a single instruction or many instructions, and can even be distributed on a plurality of different code segments, distributed among different programs, and distributed across a plurality of memory devices. Similarly, operating data can be identified in the module, and can be implemented and organized in the data structure of any appropriate type according to any appropriate form. The operating data can be collected as a single data set, or can be distributed in different locations (including on different storage devices), and can only be present on a system or network as an electronic signal at least in part.

[0129] When a module can be implemented by software, considering the level of existing hardware technology, a person skilled in the art can build a corresponding hardware circuit to implement the corresponding function of the module that can be implemented by software without considering the cost. The hardware circuit includes a conventional very large scale integration (VLSI) circuit or gate array and existing semiconductors such as logic chips, transistors, or other discrete components. The module can also be implemented by a programmable hardware device, such as a field programmable gate array, a programmable array logic, a programmable logic device, etc.

[0130] The above exemplary embodiments are described with reference to the accompanying drawings, and many different forms and embodiments are feasible without departing from the spirit and teachings of the present invention. Therefore, the present invention should not be constructed as a limitation of the exemplary embodiments proposed herein. More specifically, these exemplary embodiments are provided so that the present invention will be perfect and complete, and the scope of the present invention will be conveyed to those who are familiar with the technology. In these figures, the component sizes and relative sizes may be exaggerated for clarity. The terms used here are only based on the purpose of describing specific exemplary embodiments and are not intended to be limiting. As used herein, unless the text clearly indicates otherwise, the singular forms "one", "an" and "the" are intended to include these multiple forms. It will be further understood that the terms "including" and / or "comprising" when used in this specification indicate the presence of the features, integers, steps, operations, components and / or components, but do not exclude the presence or increase of one or more other features, integers, steps, operations, components, components and / or their groups. Unless otherwise indicated, when stated, a range of values ​​includes the upper and lower limits of that range and any subranges therebetween.

[0131] The above is a preferred embodiment of the present invention. It should be pointed out that for ordinary technicians in this technical field, several improvements and modifications can be made without departing from the principles of the present invention. These improvements and modifications should also be regarded as the scope of protection of the present invention.

Claims

1. A device data transmission method, characterized in that: include: Parse and process the received data to be transmitted to obtain target data; Generate at least one custom function point template according to the same attributes and events of multiple devices; Determine the function point type corresponding to the data to be transmitted according to the target data, the function point type including a custom function point and a system function point; Verifying the data to be transmitted according to the function point type; The target data includes: attribute parameters of the device; The verifying the data to be transmitted according to the function point type includes: If the data to be transmitted corresponds to a system function point, verifying the data to be transmitted according to a system function point template; If the data to be transmitted corresponds to a user-defined function point, a first function point template in the user-defined function point template is obtained according to the identification symbol in the attribute parameter, and the data to be transmitted is verified according to the first function point template.

2. The device data transmission method according to claim 1, characterized in that: The determining, according to the target data, the function point type corresponding to the data to be transmitted includes: If the identification symbol in the attribute parameter is a preset symbol, the data to be transmitted corresponds to a system function point; If the identification symbol in the attribute parameter is not a preset symbol, the data to be transmitted corresponds to a user-defined function point.

3. The device data transmission method according to claim 1, characterized in that: In the case where the data to be transmitted is data to be uploaded, before determining the function point type corresponding to the data to be transmitted, the method further includes: Obtain the ID and version number of the data to be transmitted; It is determined according to the target data whether the ID and version number of the data to be transmitted meet the preset requirements.

4. The device data transmission method according to claim 3, characterized in that: The determining whether the ID and version number of the data to be transmitted meet preset requirements includes: If the character length of the ID of the data to be transmitted is equal to the preset length and the version number of the data is the preset version number, it is determined that the ID and version number of the data to be transmitted meet the preset requirement; If the character length of the ID of the data to be transmitted is different from the preset length and / or the version number of the data is different from the preset version number, it is determined that the ID and version number of the data to be transmitted do not meet the preset requirement.

5. A device data transmission apparatus, characterized in that: include: The parsing module is used to parse the received data to be transmitted to obtain the target data; A generation module, used for generating at least one custom function point template according to the same attributes and events of multiple devices; A determination module, used to determine the function point type corresponding to the data to be transmitted according to the target data, wherein the function point type includes a custom function point and a system function point; A verification module, used for verifying the data to be transmitted according to the function point type; The target data includes: attribute parameters of the device; The verification module is further used for: If the data to be transmitted corresponds to a system function point, verifying the data to be transmitted according to a system function point template; If the data to be transmitted corresponds to a user-defined function point, a first function point template in the user-defined function point template is obtained according to the identification symbol in the attribute parameter, and the data to be transmitted is verified according to the first function point template.

6. A device data transmission system, characterized in that: include: The device data transmission device as claimed in claim 5.

Images