Device information transmission method, device, electronic device and storage medium

By aggregating and splitting device information acquisition requests in the configuration components of the cloud platform, the problems of large traffic consumption and high cost caused by frequent requests from the cloud platform are solved, and the effect of reducing traffic consumption and cost is achieved.

CN119363825BActive Publication Date: 2025-04-01HANGZHOU HIKVISION DIGITAL TECHNOLOGY CO LTD
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
CN202411896405.8
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2024-12-20
Publication Date
2025-04-01
Estimated Expiration
2044-12-20

AI Technical Summary

Technical Problem

In device information management, cloud platforms need to frequently send large amounts of device information acquisition requests to cloud services, resulting in large traffic consumption and high cost.

Method used

By setting configuration components in the cloud platform, aggregating device information obtains requests, splitting and encapsulating the aggregated requests according to the communication protocol requirements, reducing the number of requests and interactions.

Benefits of technology

It effectively reduces the number of information requests transmitted to cloud services by the cloud platform and the number of information requests sent, and reduces traffic consumption and cost.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119363825B_ABST
    Figure CN119363825B_ABST
Patent Text Reader

Abstract

The embodiments of the present application provide a device information transmission method, apparatus, electronic device and storage medium, and relate to the field of device information management technology. The method is applied to a cloud platform, the cloud platform is connected to a cloud service in communication, the cloud service is connected to a device in communication, and the cloud platform is provided with a configuration component. The method comprises: receiving a first type of information request sent by the configuration component, wherein the first type of information request is obtained by aggregating device information acquisition requests based on a preset information aggregation dimension by the configuration component; splitting the first type of information request according to the communication protocol requirements between the cloud platform and the cloud service, and encapsulating the split first type of information request to obtain a second type of information request; sending the second type of information request to the cloud service, and receiving the device information of the target device returned by the cloud service. By aggregating the device information acquisition requests, the amount of information sent by the cloud platform is reduced, and the traffic consumption is reduced.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the technical field of device information management, and in particular to a device information transmission method, apparatus, electronic device and storage medium. Background Art

[0002] For devices such as alarm hosts and access control hosts, according to the business attributes of the business they belong to, the devices need to be put on the cloud so that they can be remotely operated and maintained in conjunction with the cloud environment. The cloud environment can include a cloud platform and cloud services. The cloud platform can obtain device information through the cloud service that is connected to the device communication, and display the device information to the user, so that the user can perform corresponding operations on the device based on the device information displayed on the device information interface. For example, the user can manage the alarm host and related sub-devices installed in the factory on the cloud, so as to remotely manage the device or receive alarm information through the cloud platform and cloud services.

[0003] The amount of device information for each device increases with the number of sub-devices added to the device and the number of functions supported by each sub-device. Limited by the message size supported by the protocol, when obtaining device information, the amount of data in each message that can be transmitted between the cloud platform and the cloud service is small, while the number of messages is large. For example, if a device has 50 sub-devices added, and each sub-device has at least 4 functions, the cloud platform needs to send at least 200 requests to the cloud service to obtain device information, resulting in a large amount of traffic consumption on the cloud platform, and thus a high cost for the cloud platform. Summary of the invention

[0004] The purpose of the embodiments of the present application is to provide a device information transmission method, apparatus, electronic device and storage medium, which aggregates device information acquisition requests, reduces the amount of transmitted request information, reduces the number of interactions, and reduces traffic consumption. The specific technical solution is as follows:

[0005] In a first aspect, an embodiment of the present application provides a device information transmission method, which is applied to a cloud platform, wherein the cloud platform is connected to a cloud service for communication, the cloud service is connected to a device for communication, and the cloud platform is provided with a configuration component, wherein the method includes:

[0006] Receiving a first type of information request sent by the configuration component, wherein the first type of information request carries a device identifier of a target device, and the first type of information request is obtained by the configuration component by aggregating device information acquisition requests based on a preset information aggregation dimension;

[0007] According to the communication protocol requirements between the cloud platform and the cloud service, the first type of information request is split, and the split first type of information request is encapsulated to obtain a second type of information request;

[0008] The second type of information request is sent to the cloud service, and the device information of the target device returned by the cloud service based on the device identification of the target device carried in the second type of information request is received.

[0009] Optionally, the communication protocol requirement includes a first format requirement and a data volume requirement;

[0010] The step of splitting the first type of information request according to the communication protocol requirements between the cloud platform and the cloud service, and encapsulating the split first type of information request to obtain the second type of information request includes:

[0011] determining whether the data volume of the first type of information request meets the data volume requirement;

[0012] When the data volume of the first-category information request does not meet the data volume requirement, the first-category information request is split according to the data volume requirement, and the split first-category information request is encapsulated according to the first format requirement to obtain a second-category information request.

[0013] Optionally, the step of determining whether the data volume of the first-category information request meets the data volume requirement includes:

[0014] Traversing multiple first-category information requests received by the preset batch interface, and determining, when traversing each first-category information request, whether the data volume of the first-category information request is not greater than the limit of the data volume requirement;

[0015] When the data amount of the first type of information request is not greater than the limit, encapsulating the first type of information request according to the first format requirement to obtain a second type of information request;

[0016] When the data volume of the first type of information request is greater than the limit, the steps of splitting the first type of information request according to the data volume requirement and encapsulating the split first type of information request according to the first format requirement are executed to obtain the second type of information request.

[0017] Optionally, the information aggregation dimension is the type of sub-device corresponding to the target device; the transmission parameter of the preset batch interface between the configuration component and the cloud platform is defined as: all function identifiers of each sub-device corresponding to each sub-device type; the generation method of the first type of information request includes:

[0018] The configuration component aggregates various device information acquisition requests for sub-devices of the same type to obtain a first type of information request corresponding to each sub-device type corresponding to the target device.

[0019] Optionally, the information aggregation dimension is the function identifier of the sub-device corresponding to the target device; the transmission parameter of the preset batch interface between the configuration component and the cloud platform is defined as: all common function identifiers of each sub-device, and the common function identifier is the same function identifier of each sub-device; the generation method of the first type of information request includes:

[0020] The configuration component aggregates multiple device information acquisition requests regarding the same function identifier to obtain a first type of information request corresponding to each function identifier.

[0021] Optionally, the cloud platform includes a cloud platform front end and a cloud platform back end; the cloud platform front end is communicatively connected to the configuration component, and the cloud platform back end is communicatively connected to the cloud service;

[0022] The step of determining whether the data volume of the first type of information request meets the data volume requirement comprises:

[0023] The cloud platform front end determines whether the data volume of the first type of information request meets the data volume requirement;

[0024] The step of splitting the first type of information request according to the data volume requirement, and encapsulating the split first type of information request according to the first format requirement to obtain the second type of information request includes:

[0025] The cloud platform front end splits the first type of information request according to the data volume requirement, and encapsulates the split first type of information request according to the second format requirement between the cloud platform front end and the cloud platform back end to obtain the encapsulated first type of information request;

[0026] The cloud platform front end sends the encapsulated first type of information request to the cloud platform back end;

[0027] The cloud platform backend encapsulates the encapsulated first-category information request according to the first format requirement to obtain a second-category information request.

[0028] Optionally, the method further includes:

[0029] The configuration component and the device information of the target device are used to display a display interface of the device information of the target device.

[0030] Optionally, the step of using the configuration component and the device information of the target device to display a display interface of the device information of the target device includes:

[0031] Receiving static resources sent by the configuration component for generating a display interface;

[0032] The device information of the target device and the static resource are used to render a display interface of the device information of the target device.

[0033] In a second aspect, an embodiment of the present application provides a device information transmission method, which is applied to a cloud service, wherein the cloud service is communicatively connected to a cloud platform, the cloud service is communicatively connected to a device, and the cloud platform is provided with a configuration component, wherein the method includes:

[0034] receiving a second type of information request sent by the cloud platform and carrying a device identification of a target device, wherein the second type of information request is obtained by the cloud platform splitting the first type of information request sent by the configuration component according to the communication protocol requirements between the cloud platform and the cloud service, and encapsulating the split first type of information request; the first type of information request carries the device identification of the target device, and the first type of information request is obtained by the configuration component aggregating device information acquisition requests based on a preset information aggregation dimension;

[0035] Based on the device identification, the device information of the target device is sent to the cloud platform.

[0036] Optionally, before the step of receiving the second type of information request carrying the device identification of the target device sent by the cloud platform, the method further includes:

[0037] Cache device information reported regularly by the device;

[0038] The step of sending the device information of the target device to the cloud platform based on the device identification includes:

[0039] The device information corresponding to the device identifier is searched in the cached device information to obtain the device information of the target device, and the device information of the target device is sent to the cloud platform.

[0040] Optionally, the step of sending the device information of the target device to the cloud platform includes:

[0041] Assembling the device information of the target device according to the communication protocol requirements between the cloud platform and the cloud service;

[0042] The assembled device information is sent to the cloud platform so that the cloud platform parses the assembled device information, records the parsed device information, aggregates the parsed device information according to the information aggregation dimension, and sends the aggregated device information to the configuration component.

[0043] In a third aspect, an embodiment of the present application provides a device information transmission device, which is applied to a cloud platform, wherein the cloud platform is connected to a cloud service for communication, the cloud service is connected to a device for communication, and the cloud platform is provided with a configuration component, wherein the device includes:

[0044] A first receiving module is used to receive a first type of information request sent by the configuration component, wherein the first type of information request carries a device identifier of a target device, and the first type of information request is obtained by the configuration component by aggregating device information acquisition requests based on a preset information aggregation dimension;

[0045] An encapsulation module, configured to split the first type of information request according to the communication protocol requirements between the cloud platform and the cloud service, and to encapsulate the split first type of information request to obtain a second type of information request;

[0046] The second receiving module is used to send the second type of information request to the cloud service, and receive the device information of the target device returned by the cloud service based on the device identification of the target device carried in the second type of information request.

[0047] Optionally, the communication protocol requirement includes a first format requirement and a data volume requirement;

[0048] The packaging module comprises:

[0049] a determination unit, configured to determine whether the data volume of the first-category information request meets the data volume requirement; and trigger a splitting unit if the data volume of the first-category information request does not meet the data volume requirement;

[0050] The splitting unit is used to split the first type of information request according to the data volume requirement, and encapsulate the split first type of information request according to the first format requirement to obtain the second type of information request.

[0051] Optionally, the determining unit includes:

[0052] A traversal subunit is used to traverse multiple first-category information requests received by the preset batch interface, and when traversing each first-category information request, determine whether the data volume of the first-category information request is not greater than the limit of the data volume requirement; when the data volume of the first-category information request is not greater than the limit, trigger the first encapsulation subunit; when the data volume of the first-category information request is greater than the limit, trigger the splitting unit;

[0053] The first encapsulation subunit is used to encapsulate the first type of information request according to the first format requirement to obtain a second type of information request.

[0054] Optionally, the information aggregation dimension is the type of sub-device corresponding to the target device; the transmission parameter of the preset batch interface between the configuration component and the cloud platform is defined as: all function identifiers of each sub-device corresponding to each sub-device type; the device further includes a first generation module, the first generation module being used to:

[0055] The configuration component aggregates various device information acquisition requests for sub-devices of the same type to obtain a first type of information request corresponding to each sub-device type corresponding to the target device.

[0056] Optionally, the information aggregation dimension is the function identifier of the sub-device corresponding to the target device; the transmission parameter of the preset batch interface between the configuration component and the cloud platform is defined as: all common function identifiers of each sub-device, and the common function identifier is the same function identifier of each sub-device; the device also includes a second generation module, and the second generation module is used to:

[0057] The configuration component aggregates multiple device information acquisition requests regarding the same function identifier to obtain a first type of information request corresponding to each function identifier.

[0058] Optionally, the cloud platform includes a cloud platform front end and a cloud platform back end; the cloud platform front end is communicatively connected to the configuration component, and the cloud platform back end is communicatively connected to the cloud service;

[0059] The determining unit comprises:

[0060] A determination subunit, configured for the cloud platform front end to determine whether the data volume of the first type of information request meets the data volume requirement;

[0061] The splitting unit comprises:

[0062] a splitting subunit, configured for the cloud platform front end to split the first type of information request according to the data volume requirement, and to encapsulate the split first type of information request according to the second format requirement between the cloud platform front end and the cloud platform back end to obtain the encapsulated first type of information request;

[0063] A sending subunit, configured for the cloud platform front end to send the encapsulated first-category information request to the cloud platform back end;

[0064] The second encapsulation subunit is used for the cloud platform backend to encapsulate the encapsulated first-category information request according to the first format requirement to obtain a second-category information request.

[0065] Optionally, the device further comprises:

[0066] The display module is used to display a display interface of the device information of the target device by using the configuration component and the device information of the target device.

[0067] Optionally, the display module includes:

[0068] A resource receiving unit, used to receive static resources sent by the configuration component for generating a display interface;

[0069] The rendering unit is used to render a display interface of the device information of the target device by using the device information of the target device and the static resource.

[0070] In a fourth aspect, an embodiment of the present application provides a device information transmission apparatus, which is applied to a cloud service, wherein the cloud service is communicatively connected to a cloud platform, the cloud service is communicatively connected to a device, and the cloud platform is provided with a configuration component, wherein the apparatus comprises:

[0071] a third receiving module, configured to receive a second type of information request sent by the cloud platform and carrying a device identifier of a target device, wherein the second type of information request is obtained by the cloud platform splitting the first type of information request sent by the configuration component according to the communication protocol requirements between the cloud platform and the cloud service, and encapsulating the split first type of information request; the first type of information request carries the device identifier of the target device, and the first type of information request is obtained by the configuration component aggregating device information acquisition requests based on a preset information aggregation dimension;

[0072] An information sending module is used to send the device information of the target device to the cloud platform based on the device identification.

[0073] Optionally, the device further comprises:

[0074] a cache module, used for caching device information regularly reported by the device before the step of receiving the second type of information request carrying the device identification of the target device sent by the cloud platform;

[0075] The information sending module comprises:

[0076] The information sending unit is used to search for the device information corresponding to the device identifier in the cached device information, obtain the device information of the target device, and send the device information of the target device to the cloud platform.

[0077] Optionally, the information sending module includes:

[0078] An assembling unit, configured to assemble the device information of the target device according to the communication protocol requirements between the cloud platform and the cloud service;

[0079] A recording unit is used to send the assembled device information to the cloud platform so that the cloud platform parses the assembled device information, records the parsed device information, aggregates the parsed device information according to the information aggregation dimension, and sends the aggregated device information to the configuration component.

[0080] In a fifth aspect, an embodiment of the present application provides an electronic device, including:

[0081] Memory, used to store computer programs;

[0082] The processor is used to implement any method described in the first aspect or the second aspect when executing the program stored in the memory.

[0083] In a sixth aspect, an embodiment of the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method described in either the first aspect or the second aspect is implemented.

[0084] In a seventh aspect, an embodiment of the present application further provides a computer program product comprising instructions, which, when executed on a computer, enables the computer to execute any of the methods described in the first or second aspect above.

[0085] Beneficial effects of the embodiments of the present application:

[0086] The technical solution provided by the embodiment of the present application is that the cloud platform can receive the first type of information request sent by the configuration component, wherein the first type of information request carries the device identification of the target device, and the first type of information request is obtained by the configuration component aggregating the device information acquisition request based on the preset information aggregation dimension; split the first type of information request according to the communication protocol requirements between the cloud platform and the cloud service, and encapsulate the split first type of information request to obtain the second type of information request; send the second type of information request to the cloud service, and receive the device information of the target device returned by the cloud service based on the device identification of the target device carried by the second type of information request. By aggregating the device information acquisition request according to the preset information aggregation dimension, the number of information requests is reduced, thereby reducing the number of information requests transmitted by the cloud platform to the cloud service during the device information transmission process, reducing the number of times the cloud platform sends information requests, reducing the traffic consumption of the cloud platform, and thus reducing the device information transmission cost. In addition, since the second information request sent by the cloud platform is obtained by splitting and encapsulating the aggregated first information request according to the communication protocol requirements, the second information request meets the communication protocol requirements and can be received by the cloud service, ensuring the normal interaction between the cloud platform and the cloud service. Of course, implementing any product or method of the present application does not necessarily require achieving all of the advantages described above at the same time. BRIEF DESCRIPTION OF THE DRAWINGS

[0087] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application, and for ordinary technicians in this field, other embodiments can also be obtained based on these drawings.

[0088] Figure 1 A schematic diagram of a process flow of a device information transmission method provided in an embodiment of the present application;

[0089] Figure 2 for Figure 1 A specific flow chart of step S102 in the illustrated embodiment;

[0090] Figure 3 A schematic diagram of the transmission process of the device information acquisition request provided in the embodiment of the present application;

[0091] Figure 4 Another schematic diagram of the transmission process of the device information acquisition request provided in the embodiment of the present application;

[0092] Figure 5 Another schematic diagram of the transmission process of the device information acquisition request provided in the embodiment of the present application;

[0093] FIG6 (a) is a schematic diagram of an example of device information transmission provided in an embodiment of the present application;

[0094] FIG6 ( b ) is a device web interface provided in an embodiment of the present application;

[0095] Figure 7 An interactive diagram of the device information transmission process provided in the embodiment of the present application;

[0096] Figure 8 A flowchart of another device information transmission method provided in an embodiment of the present application;

[0097] Fig. 9 A schematic diagram of the structure of a device information transmission apparatus provided in an embodiment of the present application;

[0098] Fig.10 A schematic diagram of the structure of another device information transmission apparatus provided in an embodiment of the present application;

[0099] Fig.11 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0100] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field based on the present application belong to the scope of protection of the present application.

[0101] The following is an explanation of the professional terms involved in the embodiments of this application:

[0102] Device model: It is a complete description of the functions of the device and a combination of multiple fields and resources.

[0103] Domain: A collection of related functions that are business independent.

[0104] Functional identifier: a function that describes business characteristics in a certain field.

[0105] Configuration resources: a collection of web (page) software programs that support various types of devices.

[0106] Cloud platform: A system that connects to a large number of heterogeneous sensing devices to achieve unified access management of device resources, data collection, processing and storage functions, and relies on cloud services to achieve public network access, remote access and other scenarios.

[0107] Low-memory devices: Due to cost constraints, they generally have small memory and limited performance. Due to performance limitations, the message size of each interaction needs to be defined during network transmission in order to communicate normally with other devices, such as microcontroller devices.

[0108] Usually, users can use the web software program installed inside the device to install, deliver, activate, configure, and operate and maintain the device in a local area network environment. However, for devices such as alarm hosts and access control hosts, depending on the nature of their business, it is often necessary to put the device on the cloud and use the cloud environment to remotely operate and maintain the device. Especially for low-memory devices, which have small memory and no extra memory space to store web software program resources, it is necessary to put the device on the cloud and use the cloud environment to achieve installation, delivery, activation, configuration, and operation and maintenance.

[0109] The cloud environment includes a cloud platform and cloud services, among which the cloud platform integrates device web resources. After low-memory devices or other devices that need to be remotely operated through the cloud environment are put on the cloud, users can use the device web resources integrated in the cloud platform to operate and maintain the devices.

[0110] However, due to the limited performance of the device itself, the size of the message that the device can transmit is limited. Therefore, when defining the communication protocol, the messages supported by the communication protocol tend to be minimized to achieve normal interaction with other devices. For the same amount of information, the smaller the message, the more messages there are. Based on this, the miniaturization of messages leads to the need for devices to interact frequently in the cloud environment during information transmission in order to achieve effective transmission of device information. However, high-frequency interaction will lead to high traffic consumption of cloud platforms, cloud services, and devices in the cloud environment, resulting in higher cloud platform costs or higher costs for users to use devices.

[0111] Before operating and maintaining a device, you need to first obtain the device information of the device you want to operate, and use the device information to build a device model, which can fully describe the functions of the device. In this way, users can perform corresponding configuration operations on the device based on the device information described by the device model. Among them, each device can be connected to multiple sub-devices, and a type of sub-device can be understood as a field, that is, a collection of a group of related functions, and this group of functions has business independence. Correspondingly, the device information of each device can include the device information of the sub-device, and the sub-device information contains various categories of device information such as basic parameters, status parameters, associated parameters, and support information of the sub-device. Each category can be understood as a function identifier. If you need to view the list of sub-devices under the device and the device information, you need to obtain information such as associated parameters, basic parameters, status information, and support information of each type of sub-device.

[0112] For devices, according to their device functions and communication protocol limitations, there is usually a message size limit for the messages supported for transmission. Once the message size limit is exceeded, the device will reject the request, resulting in the request not being delivered normally. Therefore, when it comes to device information, each interaction can interact with a single device information of a single sub-device. For example, through one interaction, the basic parameters of sub-device A can be obtained; through one interaction, the status parameters of sub-device B can be obtained, etc. In other words, each device information request is used to request an information interaction process about a functional identifier of a sub-device, and the device information returned by the device based on the device information request is device information about a functional identifier of a sub-device.

[0113] If the device has more sub-devices connected, the amount of device information that needs to be obtained will be more, the number of times the device needs to interact with the cloud environment will be more, and the traffic consumption will be more. Correspondingly, when displaying device information, the page rendering waiting time will be longer.

[0114] Exemplarily, the alarm host can support the access of 8 types of sub-devices such as smoke sensors and temperature sensors. When you want to display the device information of the alarm host product, you can first obtain the device information of all sub-devices connected to the alarm host product. The alarm host is connected to 50 sub-devices covering 8 sub-device types, and each sub-device has at least 4 functional identifiers. In order to display the device information of the alarm host, the cloud platform interface responds to the device information display instruction and sends at least 200 device information acquisition requests to the cloud platform. Correspondingly, the cloud platform needs to send at least 200 device information acquisition requests to the cloud service, and the cloud service needs to send at least 200 device information acquisition requests to the alarm host. It can be seen that in the link of requesting device information from the alarm host, both the cloud platform and the cloud service need to send a large number of requests, resulting in a large traffic consumption of the cloud platform and the cloud service.

[0115] In actual applications, the types and quantity of sub-devices supported by each device and the number of functional identifiers of each type of sub-device are set according to the actual scenario. For example, in actual scenarios, the alarm host supports 256 sub-devices. The requests required to transmit in the process of obtaining device information of low-memory devices will cause the cloud platform to generate large traffic consumption.

[0116] In order to reduce the traffic consumption of the cloud platform during the device information transmission process, the present application provides a device information transmission method, apparatus, cloud platform, cloud service, computer-readable storage medium and computer program product. The following first introduces a device information transmission method provided by an embodiment of the present application. The device information transmission method provided by an embodiment of the present application is applied to a cloud platform, the cloud platform is connected to a cloud service for communication, the cloud service is connected to a device for communication, and the cloud platform is provided with a configuration component. Figure 1 As shown, a device information transmission method, the method comprising:

[0117] S101: Receive a first type of information request sent by the configuration component.

[0118] The first type of information request carries a device identifier of a target device, and the first type of information request is obtained by aggregating device information acquisition requests by the configuration component based on a preset information aggregation dimension.

[0119] S102: splitting the first category information request according to the communication protocol requirements between the cloud platform and the cloud service, and encapsulating the split first category information request to obtain a second category information request.

[0120] S103: Send the second type of information request to the cloud service, and receive the device information of the target device returned by the cloud service based on the device identifier of the target device carried in the second type of information request.

[0121] It can be seen that in the solution provided by the embodiment of the present application, the cloud platform can receive the first type of information request sent by the configuration component, wherein the first type of information request carries the device identification of the target device, and the first type of information request is obtained by the configuration component aggregating the device information acquisition request based on the preset information aggregation dimension; according to the communication protocol requirements between the cloud platform and the cloud service, the first type of information request is split, and the split first type of information request is encapsulated to obtain the second type of information request; the second type of information request is sent to the cloud service, and the device information of the target device returned by the cloud service based on the device identification of the target device carried by the second type of information request is received. By aggregating the device information acquisition request according to the preset information aggregation dimension, the number of information requests is reduced, thereby reducing the number of information requests transmitted by the cloud platform to the cloud service during the device information transmission process, reducing the number of times the cloud platform sends information requests, reducing the traffic consumption of the cloud platform, and thus reducing the device information transmission cost. In addition, since the second information request sent by the cloud platform is obtained by splitting and encapsulating the aggregated first information request according to the communication protocol requirements, the second information request meets the communication protocol requirements and can be received by the cloud service, ensuring the normal interaction between the cloud platform and the cloud service.

[0122] The device communicates with the cloud service, and the cloud service communicates with the cloud platform. Users can view the device information of the connected device through the cloud platform interface, and operate and maintain the device. For example, users can display the cloud platform interface through their own devices and view device information through the cloud platform interface; users can view the cloud platform interface on the front-end device of the cloud platform, etc.

[0123] In the above step S101, the cloud platform may receive a first type of information request sent by the configuration component.

[0124] Among them, the first type of information request carries the device identification of the target device, and the first type of information request is obtained by aggregating the device information acquisition request based on the preset information aggregation dimension by the configuration component.

[0125] The cloud platform is provided with a configuration component, which is integrated with a device web resource and can obtain a device information acquisition request about a target device. The device information acquisition request can be sent to the configuration component by the cloud platform interface in response to a user's device information display operation about a target device; it can also be sent to the configuration component by the cloud platform interface at a preset time interval, or it can be generated by the configuration component based on a device information acquisition operation about a target device performed by a user on the cloud platform interface, etc. Each device information acquisition request carries the device identification, sub-device identification, sub-device type, and function identification of the target device.

[0126] After receiving the device information acquisition request, the configuration component may aggregate the device information acquisition request according to a preset information aggregation dimension to obtain a first type of information request, wherein the first type of information request carries a device identifier of the target device.

[0127] Among them, the preset information aggregation dimension can be the type of each sub-device of the target device; it can also be the function identifier of the sub-device corresponding to the target device; it can also be the type of each sub-device of the target device and the function identifier of the sub-device corresponding to the target device.

[0128] Since the first type of information requests are aggregated according to a preset information aggregation dimension, the number of the first type of information requests is less than the number of device information acquisition requests received by the configuration component.

[0129] For example, a low-memory device is connected to 50 sub-devices of type 1 to type 3. The configuration component aggregates the device information acquisition requests about the low-memory device according to the type of each sub-device of the low-memory device, and obtains three first-category information requests. Each sub-device type corresponds to a first-category information request, that is, a first-category information request A corresponding to sub-device type 1 is obtained, and the first-category information request A carries the type identifier of sub-device type 1, a first-category information request B corresponding to sub-device type 2 carries the type identifier of sub-device type 2, and a first-category information request C corresponding to sub-device type 3 carries the type identifier of sub-device type 3.

[0130] In the above step S102, the first type of information request is split according to the communication protocol requirements between the cloud platform and the cloud service, and the split first type of information request is encapsulated to obtain the second type of information request.

[0131] The messages exchanged between the cloud service and the cloud platform must meet the communication protocol requirements between the cloud platform and the cloud service. The communication protocol requirements limit the amount of data in the messages transmitted by the cloud service.

[0132] Since the first type of information request is obtained by aggregation according to the preset information aggregation dimension, the data volume of each first type of information request is relatively large. Based on this, after receiving the first type of information request, the cloud platform cannot directly send the first type of information request to the cloud service. The cloud platform can split the first type of information request according to the communication protocol requirements between the cloud platform and the cloud service, and encapsulate the split first type of information request to obtain the encapsulated second type of information request.

[0133] Among them, the second type of information request is obtained by splitting the first type of information request, and each second type of information request meets the preset information aggregation dimension, that is, each second type of information request is actually aggregated according to the preset information aggregation dimension and the communication protocol requirements between the cloud platform and the cloud service. The number of second type of information requests is less than the number of device information acquisition requests received by the configuration component, and the second type of information request carries the device identification of the target device.

[0134] In the above step S103, the second type of information request is sent to the cloud service, and the device information of the target device returned by the cloud service based on the device identifier of the target device carried in the second type of information request is received.

[0135] The cloud platform may send the second type of information request to the cloud service. In this way, the cloud service may receive the second type of information request, parse the second type of information request, and then obtain the device information of the target device according to the device identifier of the target device carried in the second type of information request, and send the device information of the target device to the cloud platform.

[0136] In one implementation, the device can periodically report its own device information to the cloud service at a preset time interval. The cloud service is provided with a device information cache mechanism, which can cache the device information regularly uploaded by the device. After receiving the second type of information request, the cloud service can search for the device information corresponding to the device identification of the target device in the cached device information of each device, and send the device information of the target device to the cloud platform. In this way, the cloud service can obtain the device information of the target device without transparently transmitting the request sent by the cloud platform to the target device, thereby reducing the traffic consumption of the cloud service and the target device.

[0137] In one implementation, after receiving the second type of information request, the cloud service can parse the second type of information request, and send each device information acquisition request obtained by the analysis to the target device, and receive the device information returned by the target device based on each device information acquisition request, and then send the device information of the target device to the cloud platform.

[0138] In one implementation, the cloud service may aggregate the device information of the target device according to the communication protocol requirements between the cloud platform and the cloud service, and encapsulate the aggregated device information, and then send the encapsulated device information to the cloud platform. In this way, by aggregating the device information, the traffic consumption of the cloud service is reduced.

[0139] It can be seen that in the solution provided by the embodiment of the present application, the cloud platform can receive the first type of information request sent by the configuration component, wherein the first type of information request carries the device identification of the target device, and the first type of information request is obtained by the configuration component aggregating the device information acquisition request based on the preset information aggregation dimension; according to the communication protocol requirements between the cloud platform and the cloud service, the first type of information request is split, and the split first type of information request is encapsulated to obtain the second type of information request; the second type of information request is sent to the cloud service, and the device information of the target device returned by the cloud service based on the device identification of the target device carried by the second type of information request is received. By aggregating the device information acquisition request according to the preset information aggregation dimension, the number of information requests is reduced, thereby reducing the number of information requests transmitted by the cloud platform to the cloud service during the device information transmission process, reducing the number of times the cloud platform sends information requests, reducing the traffic consumption of the cloud platform, and thus reducing the device information transmission cost.

[0140] As an implementation method of the embodiment of the present application, the communication protocol requirement includes a first format requirement and a data volume requirement. Figure 2 As shown, the above step S102, i.e., the step of splitting the first type of information request according to the communication protocol requirements between the cloud platform and the cloud service, and encapsulating the split first type of information request to obtain the second type of information request, may include:

[0141] S201: Determine whether the data volume of the first type of information request meets the data volume requirement;

[0142] S202: When the data volume of the first-category information request does not meet the data volume requirement, the first-category information request is split according to the data volume requirement, and the split first-category information request is encapsulated according to the first format requirement to obtain a second-category information request.

[0143] The communication protocol requirements between the cloud platform and the cloud service include first format requirements and data volume requirements.

[0144] Since all information requests sent by the cloud platform to the cloud service must meet the above-mentioned first format requirement and data volume requirement, when the cloud platform receives the first type of information request, it can determine whether the data volume of the first type of information request meets the above-mentioned data volume requirement.

[0145] When the data volume of the first type of information request does not meet the data volume requirement, the cloud platform may split the first type of information request according to the above data volume requirement, and encapsulate the split first type of information request according to the first format requirement to obtain a second type of information request.

[0146] For example, the data volume requirement for interactive messages between the cloud platform and the cloud service is 100kb (kilobyte). When the cloud platform receives a first-category information request, it can determine whether the data volume of the first-category information request is greater than 100kb. When the data volume of the first-category information request is 560kb, the data volume of the first-category information request does not meet the data volume requirement. The cloud platform can split the first-category information request into 5 100kb information requests and 1 60kb information request, and encapsulate the 6 split information requests according to the first format requirement to obtain 6 second-category information requests.

[0147] In this embodiment, the first type of information request is split according to the data volume requirements between the cloud platform and the cloud service, and the split first type of information request is encapsulated according to the first format requirements between the cloud platform and the cloud service. The obtained second type of information request meets the communication protocol requirements between the cloud platform and the cloud service, thereby ensuring that the second type of information request can be smoothly sent to the cloud service, avoiding the failure to transmit due to failure to meet the communication protocol requirements, and improving the accuracy of information transmission.

[0148] As an implementation of an embodiment of the present application, the above step S201, i.e., the step of determining whether the data volume of the first type of information request meets the data volume requirement, may include:

[0149] Traversing multiple first-category information requests received by the preset batch interface, and determining, when traversing each first-category information request, whether the data volume of the first-category information request is not greater than the limit of the data volume requirement;

[0150] When the data amount of the first type of information request is not greater than the limit, encapsulating the first type of information request according to the first format requirement to obtain a second type of information request;

[0151] When the data volume of the first type of information request is greater than the limit, the steps of splitting the first type of information request according to the data volume requirement and encapsulating the split first type of information request according to the first format requirement are executed to obtain the second type of information request.

[0152] In order to improve the interaction efficiency between the cloud platform and the configuration component, a set of preset batch interfaces can be defined between the cloud platform and the configuration component. The cloud platform and the configuration component perform batch message interaction through the preset batch interface, that is, the cloud platform receives multiple first-category information requests sent by the configuration component through the preset batch interface.

[0153] The cloud platform may traverse multiple first-category information requests received by the preset batch interface. For each first-category information request, when the first-category information request is traversed, the cloud platform determines whether the data volume of the first-category information request is not greater than the limit of the data volume requirement. The data volume requirement limits the maximum data volume of a single message that can be normally interacted between the cloud platform and the cloud service.

[0154] When the data volume of the first type of information request is not greater than the limit of the data volume requirement, that is, the data volume of the first type of information request is not greater than the maximum data volume of a single message that can normally interact between the cloud platform and the cloud service, the cloud platform can encapsulate the first type of information request according to the first format requirement to obtain a second type of information request.

[0155] In the case where the data volume of the first type of information request is greater than the limit, that is, the data volume of the first type of information request is greater than the maximum data volume of a single message that can be normally exchanged between the cloud platform and the cloud service, the cloud platform can split the first type of information request according to the data volume requirement, and split the first type of information request into multiple information requests with data volumes not greater than the limit of the data volume requirement. After that, the cloud platform can encapsulate the split first type of information request according to the first format requirement to obtain a second type of information request.

[0156] In this embodiment, the cloud platform traverses each first-category information request received by a preset batch interface, and when traversing each first-category information request, determines whether the data volume of the first-category information request is not greater than the limit of the data volume requirement; when the data volume of the first-category information request is not greater than the limit, the first-category information request is encapsulated according to the first format requirement to obtain a second-category information request; when the data volume of the first-category information request is greater than the limit, the first-category information request is split according to the data volume requirement, and the split first-category information request is encapsulated according to the first format requirement to obtain a second-category information request, so that the second-category information request meets the communication protocol requirements between the cloud platform and the cloud service, ensures that the second-category information request can be smoothly sent to the cloud service, avoids the inability to transmit due to failure to meet the communication protocol requirements, and improves the accuracy of information transmission while achieving throttling.

[0157] As an implementation method of an embodiment of the present application, the information aggregation dimension is the type of sub-device corresponding to the target device; the transmission parameter of the preset batch interface between the configuration component and the cloud platform is defined as: all function identifiers of each sub-device corresponding to each sub-device type; the generation method of the first type of information request includes:

[0158] The configuration component aggregates various device information acquisition requests for sub-devices of the same type to obtain a first type of information request corresponding to each sub-device type corresponding to the target device.

[0159] The preset information aggregation dimension may be the type of sub-device corresponding to the target device.

[0160] Adapting to the above information aggregation dimension, a preset batch interface can be defined between the configuration component and the cloud platform, and the transmission parameters of the preset batch interface are defined as: all functional identifiers of each sub-device corresponding to each sub-device type. That is, by defining the transmission parameters of the preset batch interface, the batch communication interface can exchange information requests and information data of all functional identifiers of each sub-device corresponding to each sub-device type.

[0161] Exemplarily, the device supports access to sub-devices of multiple sub-device types such as A, B, and C, and the sub-devices under each sub-device type have at least 4 function identifiers. The preset batch interface BatchUtil (batch processing) between the configuration component and the cloud platform may include BatchUtil (A), BatchUtil (B), and BatchUtil (C), wherein the transmission parameters of BatchUtil (A) are defined as: BatchUtil[[A1], [A2], …, [An]], where n is the number limit of sub-devices supported for access by the device, and the content of [A1] is designed to be all function identifiers of the sub-devices, that is, [a1, a2, …, am], where m is the number limit of the function identifiers of the sub-devices, that is, by defining the transmission parameters of BatchUtil (A), BatchUtil (B), and BatchUtil (C) in the preset batch interface BatchUtil, BatchUtil (A) can receive a device information acquisition request for each function identifier of each sub-device of type A, BatchUtil (B) can receive a device information acquisition request for each function identifier of each sub-device of type B, and BatchUtil (C) can receive an information request and information data for each function identifier of each sub-device of type C.

[0162] The configuration component can aggregate the device information acquisition requests according to the type of sub-device corresponding to the target device, that is, aggregate the various device information acquisition requests for the same type of sub-device into a first-class information request, thereby obtaining the first-class information request corresponding to each type of sub-device corresponding to the target device. For example, the device has added 50 sub-devices, covering 8 types of sub-devices, and each type has 4 functional identifiers. For example, the configuration component aggregates 200 device information acquisition requests according to the type of sub-device, and aggregates the device information acquisition requests for the same type of sub-devices into a first-class information request, thereby obtaining 8 first-class information requests. The number of requests that the configuration component needs to transmit can be reduced from the original 200 to 8, greatly reducing the number of requests required for interaction. Among them, the device information acquisition requests are aggregated according to the type of sub-device corresponding to the target device, that is, the device information acquisition requests are aggregated from the domain dimension.

[0163] The configuration component then sends the first type of information request corresponding to each sub-device type to the cloud platform through a preset batch interface.

[0164] By setting the above-mentioned information aggregation dimensions and configuring preset batch interfaces between components and the cloud platform, the number of requests can be controlled at the source, and the aggregated information requests can be transmitted in batches through pre-built communication links, thereby reducing the number of interactions, reducing traffic consumption and transmission time, and improving transmission efficiency.

[0165] Correspondingly, in the case where the cloud platform includes a cloud platform front end and a cloud platform back end, a set of batch communication interfaces can be defined between the cloud platform front end and the cloud platform back end to process the first type of information requests sent by the configuration component, and a set of batch communication interfaces can be defined between the cloud platform thick end and the cloud service. In this way, by defining a complete batch communication link from the configuration component to the cloud platform front end to the cloud platform back end and then to the cloud service, the number of interactions in each link can be reduced.

[0166] Exemplarily, taking the alarm host as an example, the alarm host supports access to 8 types of sub-devices, and each type of sub-device has a set of operations, events, and attribute functions. If you need to view the list of sub-devices and device information under the alarm host, if you need to view the list of sub-devices and device information under the device, you need to obtain the associated parameters, basic parameters, status information, support information, etc. of each type of sub-device. If the alarm host is connected to 50 sub-devices and covers 8 sub-device types, each sub-device is counted as a minimum of 4 functional identifiers, and this page needs to issue 200 protocols. The configuration component transmits the device information acquisition request for each functional identifier of each sub-device through the communication link, where A1, A2, A..., B1, B2,... in the figure represent sub-device 1, sub-device 2, sub-device... respectively. A1, A2, A... are sub-devices of the same type A; B1, B2, B... are sub-devices of the same type B. a1, a2, a... are the function identifiers of the A-type sub-devices, b1, b2, b... are the function identifiers of the B-type sub-devices, and the message information categories of a1 and b1 are the same. Figure 3 As shown, the cloud platform includes a cloud platform control, a cloud platform front end and a cloud platform back end. The configuration component sends multiple device information acquisition requests such as A1 (a1), A1 (a2), A2 (a1), A2 (a2), B1 (b1), B1 (b2) to the cloud platform control, and the cloud platform control sends multiple device information acquisition requests such as A1 (a1), A1 (a2), A2 (a1), A2 (a2), B1 (b1), B1 (b2) to the cloud platform front end. The cloud platform front end encapsulates the multiple device information acquisition requests such as A1 (a1), A1 (a2), A2 (a1), A2 (a2), B1 (b1), B1 (b2) according to the second format requirement between the cloud platform front end and the cloud platform back end, and sends the encapsulated P-A1 (a1), P-A1 (a2), P-A2 (a1), P-A2 (a2), P-B1 (b1), P-B1 (b2) to the cloud platform back end. The backend of the cloud platform encapsulates multiple device information acquisition requests such as P-A1 (a1), P-A1 (a2), P-A2 (a1), P-A2 (a2), P-B1 (b1), P-B1 (b2) according to the communication protocol requirements between the cloud platform and the cloud service, and sends the encapsulated multiple device information acquisition requests such as E-A1 (a1), E-A1 (a2), E-A2 (a1), E-A2 (a2), E-B1 (b1), E-B1 (b2) to the cloud service, and the cloud service returns the device information reported by the device. In this process, the number of requests required to be transmitted in each link is large, and the traffic consumption is large.

[0167] like Figure 4As shown, the configuration component aggregates multiple device information acquisition requests such as A1 (a1), A1 (a2), A2 (a1), A2 (a2), B1 (b1), B1 (b2) according to the type of sub-device corresponding to the target device, and obtains multiple first-category information requests such as Batch A, Batch B, Batch C, and sends the multiple first-category information requests such as BatchA, BatchB, BatchC to the cloud platform control through the preset batch interface between the configuration component and the cloud platform control. The cloud platform control sends the multiple first-category information requests such as BatchA, BatchB, BatchC to the cloud platform front end through the preset batch interface between the cloud platform front end and the cloud platform back end. The cloud platform front end encapsulates the first-category information requests such as BatchA, BatchB, BatchC according to the second format requirement between the cloud platform front end and the cloud platform back end, and sends the encapsulated P-Batch A, P-Batch B, P-Batch C, and multiple information requests to the cloud platform back end. The cloud platform backend encapsulates multiple information requests such as P-BatchA, P-BatchB, and P-BatchC according to the communication protocol requirements between the cloud platform and the cloud service, and sends the encapsulated multiple second-class information requests such as E-Batch (batch) A, E-Batch (batch) B, and E-Batch (batch) C to the cloud service, and the cloud service returns the device information reported by the device. In this way, the interaction link 410 reduces the number of requests from the source and reduces the communication links; the interaction link 420 reduces the interaction, and the interaction link 430 reduces the traffic consumption.

[0168] In this embodiment, the information aggregation dimension is the type of sub-device corresponding to the target device; the transmission parameters of the preset batch interface between the configuration component and the cloud platform are defined as: all functional identifiers of each sub-device corresponding to each sub-device type; the configuration component can aggregate the various device information acquisition requests for sub-devices of the same type to obtain the first type of information request corresponding to each sub-device type corresponding to the target device. In this way, by pre-setting the information aggregation dimension and pre-defining the transmission parameters of the interface of each communication link, a communication link that is compatible with the above-mentioned information aggregation dimension can be constructed to avoid the inability to transmit the information requests obtained by aggregation according to the above-mentioned information aggregation dimension. By aggregating the device information acquisition requests according to the type of sub-device and transmitting the information requests through the preset batch interface, the number of requests that the configuration component needs to transmit can be reduced, and the transmission traffic consumption and transmission time can be reduced.

[0169] As an implementation method of an embodiment of the present application, the information aggregation dimension is the function identifier of the sub-device corresponding to the target device; the transmission parameter of the preset batch interface between the configuration component and the cloud platform is defined as: all common function identifiers of each sub-device, and the common function identifier is the same function identifier of each sub-device; the generation method of the first type of information request includes:

[0170] The configuration component aggregates multiple device information acquisition requests regarding the same function identifier to obtain a first type of information request corresponding to each function identifier.

[0171] The preset information aggregation dimension may be a function identifier of a sub-device corresponding to the target device.

[0172] Adapting to the above information aggregation dimension, a preset batch interface can be defined between the configuration component and the cloud platform, and the transmission parameters of the preset batch interface are defined as: all common function identifiers of each sub-device, wherein the common function identifier is the same function identifier of each sub-device. That is, by defining the transmission parameters of the preset batch interface, the batch communication interface can transmit information requests and information data of all common function identifiers of each sub-device.

[0173] Exemplarily, the device supports access to multiple sub-devices of sub-device types such as A, B, and C, and each sub-device has x common function identifiers. The preset batch interface between the configuration component and the cloud platform includes the transmission parameters of BatchUtil (ab) designed as: BatchUtil [[ab...]1, [ab...]2, ..., [ab...]x], and the content of [ab...]1 is designed as the common function identifier of each sub-device [A1, A2, ..., An].

[0174] The configuration component can aggregate the device information acquisition requests according to the functional identifiers of the sub-devices corresponding to the target device, that is, multiple device information acquisition requests for the same functional identifier are aggregated to obtain the first-class information request corresponding to each functional identifier. For example, the device has added 50 sub-devices, covering 8 sub-device types, and each type has 4 functional identifiers. For example, the configuration component aggregates 200 device information acquisition requests according to the functional identifier, and aggregates the device information acquisition requests for the same functional identifier into one first-class information request, thereby obtaining 4 first-class information requests. The number of requests that the configuration component needs to transmit can be reduced from the original 200 to 8, greatly reducing the number of requests required for interaction. Among them, the device information acquisition requests are aggregated according to the functional identifiers of the sub-devices corresponding to the target device, that is, the device information acquisition requests are aggregated from the dimension of functional identifiers.

[0175] The configuration component will then send each first-category information request to the cloud platform through a preset batch interface.

[0176] By setting the above information aggregation dimensions and configuring the preset batch interface between components and the cloud platform, the number of requests can be controlled at the source and the link time can be reduced.

[0177] Correspondingly, in the case where the cloud platform includes a cloud platform front end and a cloud platform back end, a set of batch communication interfaces can be defined between the cloud platform front end and the cloud platform back end to process the first type of information requests sent by the configuration component, and a set of batch communication interfaces can be defined between the cloud platform thick end and the cloud service. In this way, the number of interactions in each link can be reduced by defining a complete batch communication link.

[0178] like Figure 5 As shown, the configuration component is configured according to the function identifier corresponding to the target device. Figure 3 The multiple device information acquisition requests such as A1(a1), A1(a2), A2(a1), A2(a2), B1(b1), B1(b2) are aggregated to obtain multiple first-category information requests such as Batch(batch)(ab...)1, Batch(batch)(ab...)2, Batch(batch)(ab...)3, and the multiple first-category information requests such as Batch(ab...)1, Batch(ab...)2, Batch(ab...)3 are sent to the cloud platform control through the preset batch interface between the configuration component and the cloud platform control. The cloud platform control communicates with the cloud platform front end through The preset batch interface sends multiple first-category information requests such as Batch (ab...) 1, Batch (ab...) 2, Batch (ab...) 3 to the cloud platform front end. The cloud platform front end encapsulates the first-category information requests such as Batch (ab...) 1, Batch (ab...) 2, Batch (ab...) 3 according to the second format requirements between the cloud platform front end and the cloud platform back end, and sends the encapsulated P-Batch (batch) (ab...) 1, P-Batch (batch) (ab...) 2, P-Batch (batch) (ab...) 3 to the cloud platform back end. The cloud platform back end encapsulates multiple information requests such as P-Batch (ab...) 1, P-Batch (ab...) 2, P-Batch (ab...) 3 according to the communication protocol requirements between the cloud platform and the cloud service, and sends the encapsulated E-Batch (batch) (ab...) 1, E-Batch (batch) (ab...) 2, E-Batch (batch) (ab...) 3 to the cloud service, and the cloud service returns the device information reported by the device. The interactive link 510 reduces the number of requests from the source and reduces the communication links; the interactive link 520 reduces the interaction, and the interactive link 530 reduces the traffic consumption.

[0179] In this embodiment, the information aggregation dimension is the functional identifier of the sub-device corresponding to the target device. The transmission parameters of the preset batch interface between the configuration component and the cloud platform are defined as: all common functional identifiers of each sub-device. The configuration component can aggregate the device information acquisition requests for the same functional identifier to obtain the first type of information request corresponding to each functional identifier. In this way, by pre-setting the information aggregation dimension and pre-defining the transmission parameters of the interface of each communication link, a communication link that is compatible with the above-mentioned information aggregation dimension can be constructed to avoid the inability to transmit the information requests obtained by aggregation according to the above-mentioned information aggregation dimension. By aggregating the device information acquisition requests according to the functional identification dimension and transmitting the information requests through the preset batch interface, the number of information requests that need to be transmitted by the configuration component can be reduced, the number of information requests can be reduced from the source, the transmission traffic consumption and transmission time can be reduced, and the device information display that is adapted to different business scenarios can be displayed.

[0180] As an implementation method of the embodiment of the present application, the cloud platform includes a cloud platform front end and a cloud platform back end; the cloud platform front end is communicatively connected to the configuration component, and the cloud platform back end is communicatively connected to the cloud service;

[0181] The above step S201, i.e., the step of determining whether the data volume of the first type of information request meets the data volume requirement, may include:

[0182] The cloud platform front end determines whether the data volume of the first type of information request meets the data volume requirement;

[0183] Accordingly, the above step S202, i.e., the step of splitting the first type of information request according to the data volume requirement, and encapsulating the split first type of information request according to the first format requirement to obtain the second type of information request, may include:

[0184] The cloud platform front end splits the first type of information request according to the data volume requirement, and encapsulates the split first type of information request according to the second format requirement between the cloud platform front end and the cloud platform back end to obtain the encapsulated first type of information request;

[0185] The cloud platform front end sends the encapsulated first type of information request to the cloud platform back end;

[0186] The cloud platform backend encapsulates the encapsulated first-category information request according to the first format requirement to obtain a second-category information request.

[0187] The cloud platform may include a cloud platform front end and a cloud platform back end. The cloud platform front end is connected to the configuration component for communication, and the cloud platform front end may receive the first type of information request sent by the configuration component; the cloud platform back end is connected to the cloud service for communication, and the cloud platform back end may send the second type of information request to the cloud service.

[0188] In one implementation, the cloud platform may include a cloud platform control, a cloud platform front end, and a cloud platform back end. The cloud platform control is connected to the configuration component in communication, the cloud platform control is connected to the cloud platform front end in communication, the cloud platform front end is connected to the cloud platform back end in communication, and the cloud platform back end is connected to the cloud service in communication. The cloud platform control may receive a first-class information request sent by the configuration component, and verify the first-class information request, for example, verify whether the device identifier of the target device carried by the first-class information request is the device identifier of the device connected to the cloud platform, verify whether the authentication information carried by the first-class information request is compliant, and verify whether the first-class information request meets the communication protocol requirements between the cloud platform and the configuration component. And if the first-class information request passes the verification, the first-class information request is sent to the cloud platform front end.

[0189] After receiving the first type of information request, the cloud platform front end can determine whether the data volume of the first type of information request meets the data volume requirement between the cloud platform and the cloud service.

[0190] When the data volume of the first category information request does not meet the data volume requirement between the cloud platform and the cloud service, the cloud platform front end may split the first category information request according to the above data volume requirement. Then, in order for the cloud platform back end to receive and read the split first category information request, the cloud platform front end may encapsulate the split first category information request according to the second format requirement between the cloud platform front end and the cloud platform back end to obtain the encapsulated first category information request.

[0191] When the data volume of the first type of information request meets the data volume requirement between the cloud platform and the cloud service, the cloud platform front end can encapsulate the first type of information request according to the second format requirement between the cloud platform front end and the cloud platform back end to obtain the encapsulated first type of information request.

[0192] Then the cloud platform front end can send the encapsulated first-category information request to the cloud platform back end, and the cloud platform back end can receive the encapsulated first-category information request. Since the data volume of the encapsulated first-category information request meets the data volume requirement between the cloud platform and the cloud service, the cloud platform back end can encapsulate the encapsulated first-category information request again according to the first format requirement between the cloud platform and the cloud service to obtain a second-category information request, and the second-category information request meets the data volume requirement and the first format requirement between the cloud platform and the cloud service.

[0193] The cloud platform backend can send the second type of information request to the cloud service. The cloud service receives the second type of information request and returns the device information of the target device to the cloud platform backend based on the device identifier of the target device carried in the second type of information request. After receiving the device information returned by the cloud service, the cloud platform returns the device information to the cloud platform frontend.

[0194] In this embodiment, the cloud platform may include a cloud platform front end and a cloud platform back end. The cloud platform front end determines whether the data volume of the first type of information request meets the data volume requirement. In the case where the data volume of the first type of information request does not meet the data volume requirement between the cloud platform and the cloud service, the cloud platform front end may split the first type of information request according to the data volume requirement, and encapsulate the split first type of information request according to the second format requirement between the cloud platform front end and the cloud platform back end, and send the encapsulated first type of information request to the cloud platform back end. The cloud platform back end may encapsulate the encapsulated first type of information request according to the first format requirement to obtain the second type of information request. In this way, by constructing the communication link of the configuration component, the cloud platform front end, the cloud platform back end and the cloud service, and by processing the information request accordingly according to the communication protocol requirements between each link, the information request can be smoothly transmitted in the communication link, thereby improving the communication efficiency, and since the information request in the communication link is obtained by aggregation according to the preset information aggregation dimension, compared with the unaggregated device information acquisition request, the number of interactions required for each link is reduced, thereby reducing the traffic consumption during the information request transmission process.

[0195] As an implementation of an embodiment of the present application, a device information transmission method provided in an embodiment of the present application may also include:

[0196] The configuration component and the device information of the target device are used to display a display interface of the device information of the target device.

[0197] The configuration component includes a variety of device web (page) resources, and the configuration component is integrated in the cloud platform. When the cloud platform receives the device information of the target device returned by the cloud service, it can use the device web resources in the configuration component and the device information of the target device to display the display interface of the device information of the target device. For example, the cloud platform can display the display interface on the front-end display device.

[0198] Furthermore, in the process of displaying the device information of the target device, the user can operate the device information in the display interface. In response to the user operation, the device operation instruction can be transmitted to the cloud platform through the above link, and the cloud platform will send it to the device to configure the device.

[0199] In this embodiment, the cloud platform can use the configuration components and the device information of the target device to display the display interface of the device information of the target device. In this way, for devices connected to the cloud environment, especially low-memory devices, the cloud environment can display the device information of the device to the user, making it easier for the user to operate and maintain the device through the cloud environment and the device information of the device, thereby improving the user experience and saving the device cost and user usage cost.

[0200] In one implementation, the cloud platform can also send the device web resources in the configuration component and the device information of the target device to the user device, so that the user device displays the display interface of the device information of the target device according to the device web resources in the configuration component and the device information of the target device.

[0201] As an implementation of an embodiment of the present application, the above-mentioned step of using the configuration component and the device information of the target device to display the display interface of the device information of the target device may include:

[0202] Receiving static resources sent by the configuration component for generating a display interface;

[0203] The device information of the target device and the static resource are used to render a display interface of the device information of the target device.

[0204] The cloud platform can receive the static resources sent by the configuration component for generating the display interface, and use the device information and static resources of the target device to render the display interface of the device information of the target device.

[0205] In one implementation, upon receiving a first type of information request sent by a configuration component, the cloud platform may send a static resource acquisition request that matches the first type of information request to the configuration component. In response to the static resource acquisition request, the configuration component returns the static resources used to generate a display interface to the cloud platform. The cloud platform may receive the static resources and render a display interface of the device information of the target device based on the static resources and the device information of the target device returned by the cloud service.

[0206] In one implementation, the configuration component may send a static resource acquisition request matching the first type of information request to the cloud platform when sending the first type of information request to the cloud platform. The cloud platform may receive the static resource and render a display interface of the device information of the target device based on the static resource and the device information of the target device returned by the cloud service.

[0207] By obtaining device information, the target device can be described using a device model, which is a collection of multiple fields and resources that can fully describe the functions of the device.

[0208] In this embodiment, the cloud platform can receive the static resources sent by the configuration component for generating the display interface, and use the device information and static resources of the target device to render the display interface of the device information of the target device. In this way, the purpose of displaying the device information can be achieved, and it is convenient for the user to remotely operate the device through the display interface.

[0209] In one implementation, when the user device sends a device information acquisition request through the cloud platform interface, it can also send a static resource acquisition request. The cloud platform can forward the static resource acquisition request to the configuration component. The configuration resource can return the static resource that matches the static resource acquisition request to the user device. The user device can render a display interface of the device information of the target device based on the static resources and the device information of the target device returned by the cloud platform to display the device information of the target device to the user.

[0210] To facilitate understanding of a device information transmission method provided in an embodiment of the present application, the transmission process of a device information acquisition request and the interaction process between various links in the device information transmission process are specifically described below in conjunction with the specific embodiments shown in FIG. 6 (a) - FIG. 6 (b).

[0211] The cloud platform is integrated with configuration components and includes a cloud platform front end and a cloud platform back end. The transmission process of device information is shown in Figure 6 (a). The user can click login on the cloud platform page of the cloud platform front end to send a page jump instruction carrying basic information such as device information, authentication information, and protocol type to the cloud platform front end. The control integrated in the cloud platform front end performs information verification, verifies whether the device identifier of the target device carried by the first type of information request is the device identifier of the device connected to the cloud platform, verifies whether the authentication information carried by the first type of information request is compliant, and verifies whether the first type of information request meets the communication protocol requirements between the cloud platform and the configuration component.

[0212] When the information verification is passed, the cloud platform front-end sends a static resource request to the cloud platform back-end. The cloud platform back-end matches the static resources and sends the resource delivery instruction carrying the resource identifier of the matched static resource to the configuration component (web (page) configuration package collection), which includes multiple device web resources such as device web (page) resource 1 and device web (page) resource 2. After receiving the resource delivery instruction, the configuration component responds to the resource delivery instruction and returns the static resource to the cloud platform front-end.

[0213] The cloud platform front end displays the device page based on static resources. Users can perform information acquisition operations on the device page and send device information acquisition requests to the configuration component. The configuration component aggregates the device information acquisition requests according to the preset information aggregation dimension, and sends the aggregated first-class information requests to the cloud platform front end. The cloud platform front end splits the first-class information request according to the data volume requirements between the cloud service, and encapsulates the split first-class information request according to the second format requirements with the cloud platform back end, and sends the encapsulated first-class information request to the cloud platform back end. For example, as shown in Figure 6 (b), the device page can display the name of each device and the sub-devices connected to each device. The device page displays the network connection status and device power of the electronic doorbell and the alarm host. Among them, the converter is connected to sub-device A and sub-device B. Users can view, set and delete the electronic doorbell and converter on this interface. You can also view and delete sub-devices A and sub-device B connected to the alarm host. In addition, users can also add devices and update pages on this device page. The user can send a device information acquisition request to the configuration component by clicking the setting option of the converter to obtain the device information of the converter and the sub-device connected to the converter.

[0214] The cloud platform backend matches the protocol request, and according to the matched protocol request, encapsulates the encapsulated first-category information request again to obtain the second-category information request, and sends the second-category information request to the cloud service. That is, in response to user operations, device information is obtained from the cloud service. The cloud service parses the second-category information request and returns the device information regularly reported by the device cached by itself to the cloud platform backend. Through the above-mentioned communication link, the interaction link 610 between the cloud platform and the cloud service reduces the request data required for interaction, thereby reducing the traffic consumption of the cloud platform; the cloud service is provided with a device information caching mechanism, which can cache the device information regularly reported by the device. The cloud service does not need to execute the interaction link 620 with the device every time it receives the second-category information request, and can send the device information to the cloud platform, thereby reducing the traffic consumption of the cloud service and the device.

[0215] Among them, the interaction process between users, configuration components, cloud platform front-end and cloud platform back-end, such as Figure 7 As shown, the interaction process includes:

[0216] S701: The user enters the device information interface and performs an operation;

[0217] S702: configure component assembly batch interface;

[0218] The user enters the device information interface and performs operations. Based on the user operations, the configuration component assembles the device information acquisition request into a batch interface (i.e., the first type of information request) according to the type of sub-devices to which the device is connected, and obtains batch interface A, which is the input / output data of the preset batch interface between the configuration component and the cloud platform.

[0219] S703: The configuration component sends a batch interface A to the cloud platform front end;

[0220] The configuration component sends the batch interface A to the cloud platform front end through the preset batch interface between the configuration component and the cloud platform.

[0221] S704: The cloud platform front end determines whether A meets the data volume requirements of the cloud service; if so, execute steps S705-S710; if not, execute steps S711-S717;

[0222] The cloud platform receives batch interface A and determines whether batch interface A meets the data volume requirements of the cloud service; if batch interface A meets the data volume requirements of the cloud service, execute the following steps S705-S710; if batch interface A does not meet the data volume requirements of the cloud service, execute the following steps S711-S717.

[0223] S705: The cloud platform front end is encapsulated into a batch feature interface with the back end and sent to the cloud platform back end;

[0224] When the batch interface A meets the data volume requirements of the cloud service, the cloud platform front end encapsulates the batch interface A into a batch feature interface with the back end according to the protocol requirements of the back end, and sends the batch feature interface of the back end to the cloud platform back end. The batch feature interface of the back end is the input / output data of the preset batch interface between the cloud platform front end and the cloud platform back end.

[0225] S706: The cloud platform backend encapsulates the data into a cloud service batch communication interface and sends the interface to the cloud service.

[0226] The cloud platform backend traverses and loops the batch feature interface of each backend according to the protocol requirements of the cloud service, encapsulates the batch feature interface of each backend into the batch communication interface of the cloud service (i.e., the second type of information request), and sends the batch communication interface of the cloud service to the cloud service. The batch communication interface of the cloud service is the input / output data of the preset batch interface between the cloud platform backend and the cloud service.

[0227] S707: The cloud service returns the device information to the cloud platform backend;

[0228] The cloud service receives the batch communication interface of the cloud service, parses the batch communication interface of the cloud service, and searches for the device information corresponding to the device identifier in the device information regularly reported by the device in its own cache based on the device identifier, sub-device identifier and function identifier carried in the parsed batch communication interface. The device information is assembled into a device information package and sent to the backend of the cloud platform.

[0229] S708: The back-end encapsulated data is transparently transmitted to the front-end;

[0230] The cloud platform backend receives the device information packet returned by the cloud service, encapsulates the device information packet into the front-end data packet, and transparently transmits it to the cloud platform front-end.

[0231] S709: The front end sends the data to the configuration component;

[0232] The cloud platform front end sends the data to the configuration component.

[0233] S710: Page rendering is successful;

[0234] The configuration component sends data and static resources to the user device, and the user device renders the device information interface based on the data and static resources.

[0235] S711: The cloud platform front end traverses, packages, and encapsulates it into a batch feature interface with the back end, and sends it to the cloud platform back end;

[0236] When batch interface A does not meet the data volume requirements of the cloud service, the cloud platform front end traverses the batch interfaces, subpackages each batch interface, and encapsulates the subpackaged batch interfaces into batch feature interfaces with the back end according to the protocol requirements of the back end, and sends the batch feature interfaces of the back end to the cloud platform back end.

[0237] S712: The cloud platform backend is encapsulated into a cloud service batch communication interface and sent to the cloud service;

[0238] The cloud platform backend traverses the batch communication interface of each backend in accordance with the protocol requirements of the cloud service, encapsulates the batch communication interface of each backend into the batch communication interface of the cloud service (i.e., the second type of information request), and sends the batch communication interface of the cloud service to the cloud service.

[0239] S713: The cloud service returns the device information to the cloud platform backend;

[0240] The cloud service receives the batch communication interface of the cloud service, parses the batch communication interface of the cloud service, and searches for the device information corresponding to the device identifier in the device information regularly reported by the device cached by itself based on the device identifier, sub-device identifier and function identifier carried by the parsed batch communication interface. The device information is assembled into device information packages to obtain device information package 1, device information package 2, etc., and each device information package is sent to the back end of the cloud platform.

[0241] S714: The cloud platform backend returns the result to the cloud platform frontend;

[0242] The cloud platform backend encapsulates the device information package according to the protocol requirements of the cloud platform frontend, and returns the encapsulated device information package to the cloud platform frontend.

[0243] S715: Data assembly at the cloud platform front end;

[0244] The cloud platform front end receives the device information packet, records the device information packet, and assembles the data according to the type of sub-device connected to the device;

[0245] S716: The cloud platform front end sends data to the configuration component:

[0246] The cloud platform front end sends the assembled data to the configuration component.

[0247] S717: Page rendering is successful.

[0248] The configuration component sends data and static resources to the user device, and the user device renders the device information interface based on the data and static resources.

[0249] Corresponding to the device information transmission method applied to the cloud platform provided in the embodiment of the present application, the embodiment of the present application also provides another device information transmission method, which is applied to the cloud service, the cloud service is connected to the cloud platform for communication, the cloud service is connected to the device for communication, and the cloud platform is provided with a configuration component, such as Figure 8 As shown, the method includes:

[0250] S801: Receive a second type of information request carrying a device identification of a target device sent by the cloud platform.

[0251] The second type of information request is obtained by the cloud platform splitting the first type of information request sent by the configuration component according to the communication protocol requirements between the cloud platform and the cloud service, and encapsulating the split first type of information request; the first type of information request carries the device identifier of the target device, and the first type of information request is obtained by the configuration component aggregating the device information acquisition request based on the preset information aggregation dimension;

[0252] S802: Based on the device identifier, the device information of the target device is sent to the cloud platform.

[0253] The cloud service is connected in communication with the cloud platform, and the cloud service is connected in communication with the device, and the cloud platform is provided with a configuration component.

[0254] The configuration component may aggregate the device information acquisition request according to a preset information aggregation dimension to obtain a first type of information request, and send the first type of information request to the cloud platform.

[0255] The cloud platform can receive the first type of information request sent by the configuration component, split the first type of information request according to the communication protocol requirements between the cloud platform and the cloud service, and encapsulate the split first type of information request to obtain the second type of information request. The cloud platform sends the second type of information request to the cloud service, and the cloud service can receive the second type of information request and return the device information of the target device according to the device identifier of the target device carried by the second type of information request.

[0256] It can be seen that in the solution provided by the embodiment of the present application, by aggregating the device information acquisition request according to the preset information aggregation dimension, the number of information requests transmitted by the cloud platform to the cloud service during the device information transmission process is reduced, the number of times the cloud platform sends information requests is reduced, the traffic consumption of the cloud platform is reduced, and the device information transmission cost is reduced. In addition, since the second information request sent by the cloud platform is obtained by splitting and encapsulating the aggregated first information request according to the communication protocol requirements, the second information request meets the communication protocol requirements and can be received by the cloud service, ensuring the normal interaction between the cloud platform and the cloud service.

[0257] As an implementation of an embodiment of the present application, before the above step S801, that is, before the step of receiving the second type of information request carrying the device identification of the target device sent by the cloud platform, a device information transmission method provided in an embodiment of the present application may also include:

[0258] Cache device information reported regularly by the device;

[0259] Accordingly, the above step S802, i.e., the step of sending the device information of the target device to the cloud platform based on the device identifier, may include:

[0260] The device information corresponding to the device identifier is searched in the cached device information to obtain the device information of the target device, and the device information of the target device is sent to the cloud platform.

[0261] The cloud service is equipped with a device information cache mechanism, which can cache the device information regularly reported by the device.

[0262] When the cloud service receives the second type of information request sent by the cloud platform, it can search for device information corresponding to the device identifier in the cached device information, obtain the device information of the target device, and send the device information of the target device to the cloud platform.

[0263] In this embodiment, the cloud service is provided with a device information caching mechanism, which can cache the device information regularly reported by the device. The cloud service does not need to interact with the device every time it receives a second type of information request, and can send the device information to the cloud platform, thereby reducing the traffic consumption of the cloud service and the device.

[0264] As an implementation of an embodiment of the present application, the above step S802, i.e., the step of sending the device information of the target device to the cloud platform, may include:

[0265] Assembling the device information of the target device according to the communication protocol requirements between the cloud platform and the cloud service;

[0266] The assembled device information is sent to the cloud platform so that the cloud platform parses the assembled device information, records the parsed device information, aggregates the parsed device information according to the information aggregation dimension, and sends the aggregated device information to the configuration component.

[0267] After obtaining the device information of the target device, the cloud service can assemble the device information of the target device according to the communication protocol requirements between the cloud platform and the cloud service, that is, aggregate the device information according to the data volume requirements, and encapsulate the aggregated device information according to the first format requirements.

[0268] Afterwards, the cloud service sends the assembled device information to the cloud platform. The cloud platform can parse the assembled device information, record the parsed device information, re-aggregate the parsed device information according to the information aggregation dimension, and send the aggregated device information to the configuration component.

[0269] In this embodiment, the cloud service can reduce the number of data interactions between the cloud service and the cloud platform and save traffic resources by assembling the device information of the target device according to the communication protocol requirements between the cloud platform and the cloud service. The cloud platform can reduce the number of interactions with the configuration components and improve the interaction efficiency by aggregating the device information according to the information aggregation dimension.

[0270] Corresponding to a device information transmission method applied to a cloud platform provided in an embodiment of the present application, an embodiment of the present application also provides a device information transmission device applied to a cloud platform. The device information transmission device provided in an embodiment of the present application is introduced below. The device information transmission device is applied to a cloud platform, the cloud platform is connected to a cloud service for communication, the cloud service is connected to a device for communication, and the cloud platform is provided with a configuration component. Fig. 9 As shown, a device information transmission device includes:

[0271] A first receiving module 910 is configured to receive a first type of information request sent by the configuration component, wherein the first type of information request carries a device identifier of a target device, and the first type of information request is obtained by the configuration component by aggregating device information acquisition requests based on a preset information aggregation dimension;

[0272] The encapsulation module 920 is used to split the first type of information request according to the communication protocol requirements between the cloud platform and the cloud service, and to encapsulate the split first type of information request to obtain a second type of information request;

[0273] The second receiving module 930 is used to send the second type of information request to the cloud service, and receive the device information of the target device returned by the cloud service based on the device identification of the target device carried in the second type of information request.

[0274] It can be seen that in the solution provided by the embodiment of the present application, the cloud platform can receive the first type of information request sent by the configuration component, wherein the first type of information request carries the device identification of the target device, and the first type of information request is obtained by the configuration component aggregating the device information acquisition request based on the preset information aggregation dimension; according to the communication protocol requirements between the cloud platform and the cloud service, the first type of information request is split, and the split first type of information request is encapsulated to obtain the second type of information request; the second type of information request is sent to the cloud service, and the device information of the target device returned by the cloud service based on the device identification of the target device carried by the second type of information request is received. By aggregating the device information acquisition request according to the preset information aggregation dimension, the number of information requests is reduced, thereby reducing the number of information requests transmitted by the cloud platform to the cloud service during the device information transmission process, reducing the number of times the cloud platform sends information requests, reducing the traffic consumption of the cloud platform, and thus reducing the device information transmission cost. In addition, since the second information request sent by the cloud platform is obtained by splitting and encapsulating the aggregated first information request according to the communication protocol requirements, the second information request meets the communication protocol requirements and can be received by the cloud service, ensuring the normal interaction between the cloud platform and the cloud service.

[0275] As an implementation method of the embodiment of the present application, the communication protocol requirement includes a first format requirement and a data volume requirement;

[0276] The packaging module 920 includes:

[0277] a determination unit, configured to determine whether the data volume of the first-category information request meets the data volume requirement; and trigger a splitting unit if the data volume of the first-category information request does not meet the data volume requirement;

[0278] The splitting unit is used to split the first type of information request according to the data volume requirement, and encapsulate the split first type of information request according to the first format requirement to obtain the second type of information request.

[0279] As an implementation of the embodiment of the present application, the determining unit includes:

[0280] A traversal subunit is used to traverse multiple first-category information requests received by the preset batch interface, and when traversing each first-category information request, determine whether the data volume of the first-category information request is not greater than the limit of the data volume requirement; when the data volume of the first-category information request is not greater than the limit, trigger the first encapsulation subunit; when the data volume of the first-category information request is greater than the limit, trigger the splitting unit;

[0281] The first encapsulation subunit is used to encapsulate the first type of information request according to the first format requirement to obtain a second type of information request.

[0282] As an implementation method of an embodiment of the present application, the information aggregation dimension is the type of sub-device corresponding to the target device; the transmission parameter of the preset batch interface between the configuration component and the cloud platform is defined as: all function identifiers of each sub-device corresponding to each sub-device type; the device also includes a first generation module, the first generation module is used to:

[0283] The configuration component aggregates various device information acquisition requests for sub-devices of the same type to obtain a first type of information request corresponding to each sub-device type corresponding to the target device.

[0284] As an implementation method of an embodiment of the present application, the information aggregation dimension is the function identifier of the sub-device corresponding to the target device; the transmission parameter of the preset batch interface between the configuration component and the cloud platform is defined as: all common function identifiers of each sub-device, and the common function identifier is the same function identifier of each sub-device; the device also includes a second generation module, and the second generation module is used to:

[0285] The configuration component aggregates multiple device information acquisition requests regarding the same function identifier to obtain a first type of information request corresponding to each function identifier.

[0286] As an implementation method of the embodiment of the present application, the cloud platform includes a cloud platform front end and a cloud platform back end; the cloud platform front end is communicatively connected to the configuration component, and the cloud platform back end is communicatively connected to the cloud service;

[0287] The determining unit comprises:

[0288] A determination subunit, configured for the cloud platform front end to determine whether the data volume of the first type of information request meets the data volume requirement;

[0289] The splitting unit comprises:

[0290] a splitting subunit, configured for the cloud platform front end to split the first type of information request according to the data volume requirement, and to encapsulate the split first type of information request according to the second format requirement between the cloud platform front end and the cloud platform back end to obtain the encapsulated first type of information request;

[0291] A sending subunit, configured for the cloud platform front end to send the encapsulated first-category information request to the cloud platform back end;

[0292] The second encapsulation subunit is used for the cloud platform backend to encapsulate the encapsulated first-category information request according to the first format requirement to obtain a second-category information request.

[0293] As an implementation of the embodiment of the present application, the device further includes:

[0294] The display module is used to display a display interface of the device information of the target device by using the configuration component and the device information of the target device.

[0295] As an implementation of the embodiment of the present application, the display module includes:

[0296] A resource receiving unit, used to receive static resources sent by the configuration component for generating a display interface;

[0297] The rendering unit is used to render a display interface of the device information of the target device by using the device information of the target device and the static resource.

[0298] Corresponding to a device information transmission method applied to a cloud service provided in an embodiment of the present application, an embodiment of the present application also provides a device information transmission device applied to a cloud service. The device information transmission device provided in an embodiment of the present application is introduced below. The device information transmission device is applied to a cloud service, a cloud platform is connected to a cloud service for communication, a cloud service is connected to a device for communication, and a cloud platform is provided with a configuration component. Fig.10 As shown, a device information transmission device includes:

[0299] The third receiving module 1010 is used to receive a second type of information request sent by the cloud platform and carrying a device identification of a target device, wherein the second type of information request is obtained by the cloud platform splitting the first type of information request sent by the configuration component according to the communication protocol requirements between the cloud platform and the cloud service, and encapsulating the split first type of information request; the first type of information request carries the device identification of the target device, and the first type of information request is obtained by the configuration component aggregating device information acquisition requests based on a preset information aggregation dimension;

[0300] The information sending module 1020 is used to send the device information of the target device to the cloud platform based on the device identification.

[0301] It can be seen that in the solution provided in the embodiment of the present application, the number of information requests is reduced by aggregating the device information acquisition requests according to the preset information aggregation dimension, thereby reducing the number of information requests transmitted by the cloud platform to the cloud service during the device information transmission process, reducing the number of times the cloud platform sends information requests, reducing the traffic consumption of the cloud platform, and thereby reducing the device information transmission cost.

[0302] As an implementation of the embodiment of the present application, the device further includes:

[0303] a cache module, used for caching device information regularly reported by the device before the step of receiving the second type of information request carrying the device identification of the target device sent by the cloud platform;

[0304] The information sending module 1020 includes:

[0305] The information sending unit is used to search for the device information corresponding to the device identifier in the cached device information, obtain the device information of the target device, and send the device information of the target device to the cloud platform.

[0306] As an implementation of the embodiment of the present application, the information sending module 1020 includes:

[0307] An assembling unit, configured to assemble the device information of the target device according to the communication protocol requirements between the cloud platform and the cloud service;

[0308] A recording unit is used to send the assembled device information to the cloud platform so that the cloud platform parses the assembled device information, records the parsed device information, aggregates the parsed device information according to the information aggregation dimension, and sends the aggregated device information to the configuration component.

[0309] The present application also provides an electronic device, such as Fig.11 As shown, including:

[0310] Memory 1101, used for storing computer programs;

[0311] The processor 1102 is used to implement the above-mentioned device information transmission method applied to the cloud platform, or the device information transmission method applied to the cloud service when executing the program stored in the memory 1101.

[0312] In addition, the cloud platform may further include a communication bus and / or a communication interface, and the processor 1102, the communication interface, and the memory 1101 communicate with each other via the communication bus.

[0313] It can be seen that in the solution provided in the embodiment of the present application, by aggregating device information acquisition requests according to preset information aggregation dimensions, the number of information requests transmitted by the cloud platform to the cloud service during the device information transmission process is reduced, the number of times the cloud platform sends information requests is reduced, the traffic consumption of the cloud platform is reduced, and the device information transmission cost is reduced.

[0314] The communication bus mentioned in the above electronic device can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. The communication bus can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, only one thick line is used in the figure, but it does not mean that there is only one bus or one type of bus.

[0315] The communication interface is used for communication between the above electronic device and other devices.

[0316] The memory may include a random access memory (RAM) or a non-volatile memory (NVM), such as at least one disk memory. Optionally, the memory may also be at least one storage device located away from the aforementioned processor.

[0317] The above-mentioned processor can be a general-purpose processor, including a central processing unit (CPU), a network processor (NP), etc.; it can also be a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components.

[0318] In another embodiment provided in the present application, a computer-readable storage medium is provided, in which a computer program is stored. When the computer program is executed by a processor, the steps of any of the above-mentioned device information transmission methods are implemented.

[0319] In another embodiment provided in the present application, a computer program product including instructions is also provided, which, when executed on a computer, enables the computer to execute any device information transmission method in the above embodiments.

[0320] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. 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 a computer-readable storage medium, 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 to another website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium may be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrated. The available medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a tape), an optical medium (e.g., a DVD), or a solid-state hard disk (SSD), etc.

[0321] It should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or device including the elements.

[0322] Each embodiment in this specification is described in a related manner, and the same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the device, electronic device, computer-readable storage medium, and computer program product embodiments, since they are basically similar to the method embodiments, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiments.

[0323] The above description is only a preferred embodiment of the present application and is not intended to limit the protection scope of the present application. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present application are included in the protection scope of the present application.

Claims

1. A device information transmission method, characterized in that: Applied to a cloud platform, the cloud platform is connected to a cloud service in communication, the cloud service is connected to a device in communication, the cloud platform is provided with a configuration component, and the method includes: Receiving a first type of information request sent by the configuration component, wherein the first type of information request carries a device identifier of a target device, and the first type of information request is obtained by the configuration component by aggregating device information acquisition requests based on a preset information aggregation dimension; According to the communication protocol requirements between the cloud platform and the cloud service, the first type of information request is split, and the split first type of information request is encapsulated to obtain a second type of information request; Sending the second type of information request to the cloud service, and receiving the device information of the target device returned by the cloud service based on the device identifier of the target device carried in the second type of information request; The information aggregation dimension is the type of sub-device corresponding to the target device; the transmission parameter of the preset batch interface between the configuration component and the cloud platform is defined as: all function identifiers of each sub-device corresponding to each sub-device type; the generation method of the first type of information request includes: the configuration component aggregates each device information acquisition request for the same type of sub-device to obtain the first type of information request corresponding to each type of sub-device corresponding to the target device; and / or, The information aggregation dimension is the function identifier of the sub-device corresponding to the target device; the transmission parameter of the preset batch interface between the configuration component and the cloud platform is defined as: all common function identifiers of each sub-device, and the common function identifier is the same function identifier of each sub-device; the generation method of the first type of information request includes: the configuration component aggregates multiple device information acquisition requests for the same function identifier to obtain the first type of information request corresponding to each function identifier.

2. The method according to claim 1, characterized in that: The communication protocol requirements include a first format requirement and a data volume requirement; The step of splitting the first type of information request according to the communication protocol requirements between the cloud platform and the cloud service, and encapsulating the split first type of information request to obtain the second type of information request includes: determining whether the data volume of the first type of information request meets the data volume requirement; When the data volume of the first-category information request does not meet the data volume requirement, the first-category information request is split according to the data volume requirement, and the split first-category information request is encapsulated according to the first format requirement to obtain a second-category information request.

3. The method according to claim 2, characterized in that The step of determining whether the data volume of the first type of information request meets the data volume requirement includes: Traversing multiple first-category information requests received by the preset batch interface, and determining, when traversing each first-category information request, whether the data volume of the first-category information request is not greater than the limit of the data volume requirement; When the data amount of the first type of information request is not greater than the limit, encapsulating the first type of information request according to the first format requirement to obtain a second type of information request; When the data volume of the first type of information request is greater than the limit, the step of splitting the first type of information request according to the data volume requirement and encapsulating the split first type of information request according to the first format requirement is executed to obtain the second type of information request.

4. The method according to claim 2, characterized in that: The cloud platform includes a cloud platform front end and a cloud platform back end; the cloud platform front end is communicatively connected with the configuration component, and the cloud platform back end is communicatively connected with the cloud service; The step of determining whether the data volume of the first type of information request meets the data volume requirement includes: The cloud platform front end determines whether the data volume of the first type of information request meets the data volume requirement; The step of splitting the first type of information request according to the data volume requirement, and encapsulating the split first type of information request according to the first format requirement to obtain the second type of information request includes: The cloud platform front end splits the first type of information request according to the data volume requirement, and encapsulates the split first type of information request according to the second format requirement between the cloud platform front end and the cloud platform back end to obtain the encapsulated first type of information request; The cloud platform front end sends the encapsulated first type of information request to the cloud platform back end; The cloud platform backend encapsulates the encapsulated first-category information request according to the first format requirement to obtain a second-category information request.

5. The method according to any one of claims 1 to 3, characterized in that: The method further comprises: The configuration component and the device information of the target device are used to display a display interface of the device information of the target device.

6. The method according to claim 5, characterized in that The step of displaying a display interface of the device information of the target device by using the configuration component and the device information of the target device includes: Receiving static resources sent by the configuration component for generating a display interface; The device information of the target device and the static resource are used to render a display interface of the device information of the target device.

7. A device information transmission method, characterized in that: Applied to a cloud service, the cloud service is connected to a cloud platform for communication, the cloud service is connected to a device for communication, the cloud platform is provided with a configuration component, the method comprises: Receive a second type of information request carrying a device identification of a target device sent by the cloud platform, wherein the second type of information request is obtained by the cloud platform splitting the first type of information request sent by the configuration component according to the communication protocol requirements between the cloud platform and the cloud service, and encapsulating the split first type of information request; the first type of information request carries the device identification of the target device, and the first type of information request is obtained by the configuration component aggregating device information acquisition requests based on a preset information aggregation dimension; the information aggregation dimension is the type of sub-device corresponding to the target device; the transmission parameters of the preset batch interface between the configuration component and the cloud platform are defined as: each sub-device type all function identifiers of each corresponding sub-device; the first type of information request is the first type of information request corresponding to each type of sub-device corresponding to the target device obtained by the configuration component aggregating various device information acquisition requests for sub-devices of the same type; and / or the information aggregation dimension is the function identifier of the sub-device corresponding to the target device; the transmission parameter of the preset batch interface between the configuration component and the cloud platform is defined as: all common function identifiers of each sub-device, and the common function identifier is the same function identifier of each sub-device; the first type of information request is the first type of information request corresponding to each function identifier obtained by the configuration component aggregating multiple device information acquisition requests for the same function identifier; Based on the device identification, the device information of the target device is sent to the cloud platform.

8. The method according to claim 7, characterized in that Before the step of receiving the second type of information request carrying the device identification of the target device sent by the cloud platform, the method further includes: Cache device information reported regularly by the device; The step of sending the device information of the target device to the cloud platform based on the device identification includes: The device information corresponding to the device identifier is searched in the cached device information to obtain the device information of the target device, and the device information of the target device is sent to the cloud platform.

9. The method according to claim 7 or 8, characterized in that: The step of sending the device information of the target device to the cloud platform includes: Assembling the device information of the target device according to the communication protocol requirements between the cloud platform and the cloud service; The assembled device information is sent to the cloud platform so that the cloud platform parses the assembled device information, records the parsed device information, aggregates the parsed device information according to the information aggregation dimension, and sends the aggregated device information to the configuration component.

10. A device information transmission apparatus, characterized in that: Applied to a cloud platform, the cloud platform is connected to a cloud service in communication, the cloud service is connected to a device in communication, the cloud platform is provided with a configuration component, and the device includes: A first receiving module is used to receive a first type of information request sent by the configuration component, wherein the first type of information request carries a device identifier of a target device, and the first type of information request is obtained by the configuration component by aggregating device information acquisition requests based on a preset information aggregation dimension; An encapsulation module, configured to split the first type of information request according to the communication protocol requirements between the cloud platform and the cloud service, and to encapsulate the split first type of information request to obtain a second type of information request; A second receiving module, configured to send the second type of information request to the cloud service, and receive device information of the target device returned by the cloud service based on the device identifier of the target device carried in the second type of information request; The information aggregation dimension is the type of sub-device corresponding to the target device; the transmission parameter of the preset batch interface between the configuration component and the cloud platform is defined as: all function identifiers of each sub-device corresponding to each sub-device type; the device also includes a first generation module, the first generation module is used for: the configuration component aggregates each device information acquisition request for the same type of sub-device to obtain a first type of information request corresponding to each sub-device type corresponding to the target device; and / or, The information aggregation dimension is the function identifier of the sub-device corresponding to the target device; the transmission parameter of the preset batch interface between the configuration component and the cloud platform is defined as: all common function identifiers of each sub-device, and the common function identifier is the same function identifier of each sub-device; the device also includes a second generation module, and the second generation module is used for: the configuration component aggregates multiple device information acquisition requests for the same function identifier to obtain a first type of information request corresponding to each function identifier.

11. The device according to claim 10, characterized in that The communication protocol requirements include a first format requirement and a data volume requirement; The packaging module comprises: a determination unit, configured to determine whether the data volume of the first-category information request meets the data volume requirement; and trigger a splitting unit if the data volume of the first-category information request does not meet the data volume requirement; The splitting unit is used to split the first type of information request according to the data volume requirement, and encapsulate the split first type of information request according to the first format requirement to obtain a second type of information request; and / or, The determining unit comprises: A traversal subunit is used to traverse multiple first-category information requests received by the preset batch interface, and when traversing each first-category information request, determine whether the data volume of the first-category information request is not greater than the limit of the data volume requirement; when the data volume of the first-category information request is not greater than the limit, trigger the first encapsulation subunit; when the data volume of the first-category information request is greater than the limit, trigger the splitting unit; The first encapsulation subunit is used to encapsulate the first type of information request according to the first format requirement to obtain a second type of information request; and / or, The cloud platform includes a cloud platform front end and a cloud platform back end; the cloud platform front end is communicatively connected with the configuration component, and the cloud platform back end is communicatively connected with the cloud service; The determining unit comprises: A determination subunit, configured for the cloud platform front end to determine whether the data volume of the first type of information request meets the data volume requirement; The splitting unit comprises: a splitting subunit, configured for the cloud platform front end to split the first type of information request according to the data volume requirement, and to encapsulate the split first type of information request according to the second format requirement between the cloud platform front end and the cloud platform back end to obtain the encapsulated first type of information request; A sending subunit, configured for the cloud platform front end to send the encapsulated first-category information request to the cloud platform back end; A second encapsulation subunit is used for the cloud platform backend to encapsulate the encapsulated first-category information request according to the first format requirement to obtain a second-category information request; and / or, The device also includes: A display module is used to display a display interface of the device information of the target device by using the configuration component and the device information of the target device; and / or, The display module comprises: A resource receiving unit, used to receive static resources sent by the configuration component for generating a display interface; The rendering unit is used to render a display interface of the device information of the target device by using the device information of the target device and the static resource.

12. A device information transmission apparatus, characterized in that: Applied to a cloud service, the cloud service is connected to a cloud platform for communication, the cloud service is connected to a device for communication, the cloud platform is provided with a configuration component, and the device comprises: The third receiving module is used to receive a second type of information request sent by the cloud platform and carrying the device identification of the target device, wherein the second type of information request is obtained by the cloud platform splitting the first type of information request sent by the configuration component according to the communication protocol requirements between the cloud platform and the cloud service, and encapsulating the split first type of information request; the first type of information request carries the device identification of the target device, and the first type of information request is obtained by the configuration component aggregating the device information acquisition request based on a preset information aggregation dimension; the information aggregation dimension is the type of sub-device corresponding to the target device; the transmission parameters of the preset batch interface between the configuration component and the cloud platform are defined as: each sub- all function identifiers of each sub-device corresponding to the device type; the first type of information request is the first type of information request corresponding to each type of sub-device corresponding to the target device obtained by the configuration component aggregating various device information acquisition requests for sub-devices of the same type; and / or the information aggregation dimension is the function identifier of the sub-device corresponding to the target device; the transmission parameter of the preset batch interface between the configuration component and the cloud platform is defined as: all common function identifiers of each sub-device, and the common function identifier is the same function identifier of each sub-device; the first type of information request is the first type of information request corresponding to each function identifier obtained by the configuration component aggregating multiple device information acquisition requests for the same function identifier; An information sending module is used to send the device information of the target device to the cloud platform based on the device identification.

13. The device according to claim 12, characterized in that The device also includes: a cache module, used for caching device information regularly reported by the device before the step of receiving the second type of information request carrying the device identification of the target device sent by the cloud platform; The information sending module comprises: an information sending unit, configured to search the cached device information for the device information corresponding to the device identifier, obtain the device information of the target device, and send the device information of the target device to the cloud platform; and / or, The information sending module comprises: An assembling unit, configured to assemble the device information of the target device according to the communication protocol requirements between the cloud platform and the cloud service; A recording unit is used to send the assembled device information to the cloud platform so that the cloud platform parses the assembled device information, records the parsed device information, aggregates the parsed device information according to the information aggregation dimension, and sends the aggregated device information to the configuration component.

14. An electronic device, characterized in that: include: Memory, used to store computer programs; A processor, for implementing the method described in any one of claims 1-6 or 7-9 when executing a program stored in a memory.

15. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the method described in any one of claims 1-6 or 7-9 is implemented.

Citation Information

Patent Citations

  • Data transmission method and device

    CN111314339A