Visualization method, device and equipment for data uplink of Internet of Things equipment and medium

Abstract

One or more embodiments of the invention provide an Internet of Things device data uplink visualization method and apparatus, a device and a medium, and the method is applied to a client corresponding to a target Internet of Things device. Comprising the following steps: visually presenting an SDK (Software Development Kit) which is provided by an operator of a block chain and is used for storing Internet of Things equipment data into the block chain in a visual interface; selecting a target SDK (Software Development Kit) corresponding to the target Internet of Things equipment in the visual interface through a visual operation; generating demonstration equipment data corresponding to the target Internet of Things equipment, and performing real-time visual presentation on the demonstration equipment data in a visual interface; the demonstration data is used for representing equipment data of the target Internet of Things equipment acquired by running the target SDK; generating a demonstration block based on the demonstration equipment data, and visually presenting the demonstration block in a visual interface; the demonstration block is used for representing a block generated when the device data of the target Internet of Things device is stored in the block chain by running the target SDK.

Description

Technical Field

[0001] One or more embodiments of the present application relate to the field of Internet of Things technology, and in particular, to a method, apparatus, device and medium for visualizing data on a chain of Internet of Things devices. Background Art

[0002] The Internet of Things (IoT) refers to a network that connects various information sensing devices (such as radio frequency identification, infrared sensors, laser scanners, global positioning systems, etc.) with objects (such as home appliances, cars, buildings, etc.) through the Internet to exchange information and communicate, so as to achieve intelligent identification, positioning, tracking, monitoring and management. It expands the concept of the Internet and is no longer limited to information exchange between people, but allows information exchange between things and between things and people.

[0003] IoT devices refer to physical objects that can connect to the Internet and exchange data with other devices or systems. These devices are usually embedded with sensors, software and other technologies to achieve data collection, data interaction with the Internet or other devices, and automation functions. Common types of IoT devices include smart home devices (such as smart sockets, smart door locks, smart cameras, etc.), smart home appliances (such as smart refrigerators, smart air conditioners, smart washing machines, etc.), wearable devices (such as smart watches, fitness trackers, etc.), Internet of Vehicles devices (such as vehicle-mounted units, smart traffic lights, etc.), healthcare IoT devices (such as remote patient monitoring equipment, drug management devices, etc.), etc.

[0004] With the development of information technology, the Internet of Things has become a bridge connecting the physical world and the digital world, greatly promoting the intelligent process of all walks of life. However, with the rapid growth in the number of IoT devices, the traditional centralized data processing model faces many challenges, including but not limited to data security, privacy protection, trust building and operational efficiency. These issues not only limit the wider application and development of IoT technology, but also pose a potential threat to user security and privacy.

[0005] Blockchain is a distributed ledger, one of the core features of which is that once data is recorded, it is almost impossible to tamper with it. In order to ensure the integrity, authenticity and reliability of the data of logistics network equipment, the data of IoT devices can be uploaded to the blockchain, that is, the device itself or the relevant data of the device during operation is stored in the blockchain. However, the process of uploading IoT device data to the blockchain is usually not user-oriented, and users cannot perceive the process of uploading IoT device data to the blockchain. Therefore, how to improve user participation and user experience when uploading IoT device data to the blockchain has become an urgent problem to be solved. Summary of the invention

[0006] One or more embodiments of the present application provide the following technical solutions:

[0007] The present application provides a visualization method for uploading data of an IoT device to a chain, which is applied to a client corresponding to a target IoT device; the method comprises:

[0008] Visually presenting at least one SDK provided by the operator of the blockchain in a visual interface; wherein the SDK encapsulates a component for storing IoT device data in the blockchain;

[0009] Selecting a target SDK corresponding to the target IoT device from the at least one SDK through a visual operation in the visual interface;

[0010] Generate demonstration device data corresponding to the target IoT device, and present the demonstration device data in real time in the visualization interface; wherein the demonstration data is used to represent the device data of the target IoT device collected by running the components encapsulated in the target SDK;

[0011] A demonstration block is generated based on the demonstration device data, and the demonstration block is visually presented in the visualization interface; wherein the demonstration block is used to represent a block generated when the device data of the target IoT device is stored in the blockchain by running the components encapsulated in the target SDK.

[0012] The present application also provides a visualization device for uploading data of an IoT device to a chain, which is applied to a client corresponding to a target IoT device; the device includes:

[0013] An SDK demonstration module that visually presents at least one SDK provided by the operator of the blockchain in a visual interface; wherein the SDK encapsulates a component for storing IoT device data in the blockchain;

[0014] An SDK selection module, which selects a target SDK corresponding to the target IoT device from the at least one SDK through visual operations in the visual interface;

[0015] A collection demonstration module generates demonstration device data corresponding to the target IoT device, and presents the demonstration device data in real time in the visualization interface; wherein the demonstration data is used to represent the device data of the target IoT device collected by running the components encapsulated in the target SDK;

[0016] The on-chain demonstration module generates a demonstration block based on the demonstration device data, and visually presents the demonstration block in the visualization interface; wherein the demonstration block is used to represent the block generated when the device data of the target IoT device is stored in the blockchain by running the components encapsulated in the target SDK.

[0017] The present application also provides an electronic device, including:

[0018] processor;

[0019] a memory for storing processor-executable instructions;

[0020] The processor implements the steps of any of the above methods by running the executable instructions.

[0021] The present application also provides a computer-readable storage medium having computer instructions stored thereon, which implement the steps of any of the above methods when executed by a processor.

[0022] In the above technical solution, for the IoT device to be put on the chain, the SDK provided by the operator of the blockchain and encapsulating the component for storing the IoT device data in the blockchain can be visually presented in a visual interface, and the target SDK corresponding to the IoT device can be selected through visual operation in the visual interface, so that demonstration device data for representing the device data of the IoT device collected by running the component encapsulated in the target SDK can be generated, and the demonstration device data can be visually presented in real time in the visual interface. Furthermore, a demonstration block for representing the block generated when the device data of the IoT device is stored in the blockchain by running the component encapsulated in the target SDK can be generated based on the demonstration device data, and the demonstration block can be visually presented in the visual interface.

[0023] By adopting the above method, through a user-interactive visual interface, users can participate in selecting the SDK for uploading IoT device data to the chain, and the demonstration data and demonstration blocks are visually presented to the users, wherein the demonstration data can represent the device data of the IoT device collected by running the components encapsulated in the SDK, and the demonstration block can represent the block generated when the device data of the IoT device is stored in the blockchain by running the components encapsulated in the SDK. In this way, the visualization of the entire process of storing the device itself of the IoT device or the relevant data during the operation of the device in the blockchain can be realized, thereby improving the user participation in the visualization of the IoT device data uploading to the chain and enhancing the user experience. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] The following is a description of the accompanying drawings required for describing the exemplary embodiments, wherein:

[0025] Figure 1 It is a schematic diagram of a blockchain system shown in an exemplary embodiment of the present application.

[0026] Figure 2 It is a flowchart of a visualization method for uploading IoT device data to a chain, shown as an exemplary embodiment of the present application.

[0027] Figure 3 It is a schematic diagram of a visualization interface shown in an exemplary embodiment of the present application.

[0028] Figure 4 It is a schematic diagram of another visual interface shown in an exemplary embodiment of the present application.

[0029] Figure 5 It is a schematic diagram of another visual interface shown in an exemplary embodiment of the present application.

[0030] Figure 6 It is a schematic diagram of another visual interface shown in an exemplary embodiment of the present application.

[0031] Figure 7 It is a schematic diagram of another visual interface shown in an exemplary embodiment of the present application.

[0032] Figure 8 It is a schematic diagram of another visual interface shown in an exemplary embodiment of the present application.

[0033] Fig. 9 It is a schematic diagram of another visual interface shown in an exemplary embodiment of the present application.

[0034] Fig.10 It is a schematic diagram of another visual interface shown in an exemplary embodiment of the present application.

[0035] Fig.11 It is a structural schematic diagram of a device shown in an exemplary embodiment of the present application.

[0036] Fig.12 It is a block diagram of a visualization device for uploading IoT device data to a chain, shown as an exemplary embodiment of the present application. DETAILED DESCRIPTION

[0037] Here, exemplary embodiments will be described in detail, and examples thereof are shown in the accompanying drawings. When the following description relates to the accompanying drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with one or more embodiments of the present application. On the contrary, they are only examples consistent with some aspects of one or more embodiments of the present application.

[0038] It should be noted that in other embodiments, the steps of the corresponding method are not necessarily performed in the order shown and described in this application. In some other embodiments, the steps included in the method may be more or less than those described in this application. In addition, a single step described in this application may be decomposed into multiple steps for description in other embodiments; and multiple steps described in this application may also be combined into a single step for description in other embodiments.

[0039] Blockchain is generally divided into three types: public blockchain, private blockchain and consortium blockchain. In addition, there can be a combination of the above types, such as the combination of private blockchain and consortium blockchain, the combination of consortium blockchain and public blockchain, etc.

[0040] Among the three types of blockchains mentioned above, the public chain is the most decentralized. Participants who join the public chain (also called nodes in the blockchain) can read data records on the chain, participate in transactions, compete for the right to record new blocks, etc. Moreover, each node can freely join or exit the network and perform related operations.

[0041] On the contrary, the private chain has a network write permission controlled by a certain organization (or entity), and the data read permission is regulated by the organization. In other words, the private chain can be regarded as a weakly centralized system with strict restrictions on nodes and a small number of nodes. This type of blockchain is more suitable for use within a specific organization.

[0042] The alliance chain is between the public chain and the private chain, and can achieve "partial decentralization". Each node in the alliance chain usually has a corresponding organization (or entity); the nodes join the network through authorization and form a stakeholder alliance to jointly maintain the operation of the blockchain.

[0043] Based on the basic characteristics of blockchain, blockchain is usually composed of several blocks. In each of these blocks, a timestamp corresponding to the creation time of the block is recorded. All blocks strictly follow the timestamp recorded in the block to form a data chain that is ordered in time.

[0044] For data generated outside the blockchain, these data can be constructed into a standard transaction format supported by the blockchain, and then published to the blockchain. The nodes participating in the consensus in the blockchain system will reach a consensus on the transaction and execute the transaction after the consensus is reached, so that the transaction and the execution results can be persistently stored in the blockchain.

[0045] In the blockchain system, different participants can establish a distributed blockchain network through the deployed nodes. In practical applications, the connection relationship between each node and different nodes can be regarded as the blockchain network, and the connection relationship between each node and different nodes, data interaction, etc. can be regarded as the blockchain system. Among them, the decentralized (or multi-centralized) distributed ledger constructed by the chain block structure is stored on each node (or most nodes, such as consensus nodes) in the distributed blockchain network. This type of blockchain system needs to solve the problem of consistency and correctness of the ledger data on multiple decentralized (or multi-centralized) nodes. The blockchain program is running on each node in the blockchain system. Under the design of certain fault tolerance requirements, the consensus protocol is used to ensure that all loyal nodes have the same transactions, thereby ensuring that all loyal nodes have consistent execution results for the same transaction, and the transactions and execution results are packaged to generate blocks.

[0046] Nodes in a blockchain system can generally be divided into two categories: consensus nodes and non-consensus nodes. Among them, consensus nodes are nodes that run consensus protocols. Non-consensus nodes can forward transactions received from clients to consensus nodes. Consensus nodes can propose transactions, try to construct blocks, and send the constructed blocks to other nodes, so that both consensus nodes and non-consensus nodes can store the blocks.

[0047] Specifically, the consensus nodes in the blockchain system can reach a consensus on the transactions contained in the new block to be connected to the chain block structure based on the consensus protocol to ensure that each consensus node agrees on the content and order of the transactions contained in the block, thereby realizing the construction of the block. After the consensus is completed, the consensus node can send the constructed block to other nodes, so that each node can execute the transactions contained in the block in order, and complete the finalization of the block after confirming that the transaction execution results of each node are consistent. Among them, finalization means that the execution of the transactions contained in the block is completed and the transaction execution results are recognized by all nodes (or a certain number of nodes, such as two-thirds of the nodes).

[0048] Any consensus node in the blockchain system can broadcast a message after executing the transactions contained in a block that has been completed by consensus. The message can indicate that the block has been completed by consensus and the transactions contained in it have been completed. Therefore, based on the message, it can be confirmed whether the transaction execution results of each consensus node for the block are consistent, so that the finalization of the block can be completed when the transaction execution results of each consensus node are confirmed to be consistent.

[0049] Please refer to Figure 1 , Figure 1 It is a schematic diagram of a blockchain system shown in an exemplary embodiment of the present application.

[0050] like Figure 1 As shown, the blockchain system can maintain one or more blockchains (e.g., public blockchains, private blockchains, alliance blockchains, etc.), and can include multiple blockchain nodes for hosting the above one or more blockchains; for example, Figure 1 Blockchain node 1, blockchain node 2, blockchain node 3, blockchain node 4, blockchain node i, etc. shown in the figure can jointly carry one or more blockchains. Cross-chain data access can also be performed between the blockchains included in each blockchain system and between each blockchain system.

[0051] A node is a logical communication entity; multiple blockchain nodes of different types can run on the same physical server or on different physical servers. In one embodiment shown, a blockchain node can be a physical device or a virtual device implemented in a server or server cluster; for example, a blockchain node can be a physical host in a server cluster, or a virtual machine created by virtualizing the hardware resources of a server or server cluster based on virtualization technology. Each blockchain node can be coupled together to form a network through various types of communication methods (e.g., TCP / IP, etc.) to carry one or more blockchains.

[0052] As a distributed ledger technology, blockchain technology has attracted much attention due to its unique characteristics. Its main advantages are as follows:

[0053] Immutability: Blockchain ensures that every transaction record cannot be easily modified or deleted once it is confirmed and added to the chain, thus ensuring the integrity and authenticity of the data.

[0054] Security: Through consensus protocols, blockchain effectively prevents unauthorized access and malicious tampering, providing a highly secure data storage and transmission solution.

[0055] Transparency and traceability: All transaction information is open, transparent, permanently stored and traceable, which is of great significance for improving supply chain transparency and tracking product sources.

[0056] Decentralized architecture: The blockchain adopts a peer-to-peer network structure with no single control node, which reduces the risk of single point failure and enhances the system's anti-censorship capabilities.

[0057] Smart Contract Support: Built-in programming capabilities allow the creation of code snippets that automatically execute contract terms, i.e. smart contracts, which can streamline business processes and reduce human intervention.

[0058] Given the characteristics of the above-mentioned blockchain technology, there are many advantages to putting IoT device data on the chain. The immutable nature of blockchain provides a strong guarantee for the authenticity of IoT device data, ensuring that data consistency and reliability can be maintained at every stage from source collection to final use. With the help of blockchain's security protection measures, unauthorized data access and malware intrusion can be effectively prevented. By recording IoT device data on the blockchain, the entire life cycle of the product can be tracked, making it easier to quickly locate the source of the problem and take corresponding measures. Based on the blockchain platform, different companies and institutions can share valuable information without sacrificing their respective data sovereignty, and jointly promote industry standards and technological progress. Using smart contracts to automate certain types of transactions, such as automatic payments, conditionally triggered tasks, etc., can significantly improve efficiency and reduce costs.

[0059] It can be seen that uploading IoT device data to the chain can ensure the integrity, authenticity and reliability of logistics network device data, and lay a solid technical foundation for a wider range of interconnection and intelligent applications. However, the process of uploading IoT device data to the chain is usually not user-oriented, and users cannot perceive the process of uploading IoT device data to the chain. For users, in the process of uploading IoT device data to the chain, user participation is low and user experience is poor.

[0060] One or more embodiments of the present application provide a technical solution for visualization of IoT device data on a chain. In the technical solution, for IoT devices to be on the chain, an SDK provided by a blockchain operator and encapsulating components for storing IoT device data in the blockchain can be visualized in a visualization interface, and a target SDK corresponding to the IoT device can be selected from the visualization interface through visualization operations, so that demonstration device data representing the device data of the IoT device collected by running the components encapsulated in the target SDK can be generated, and the demonstration device data can be visualized in real time in the visualization interface. Furthermore, a demonstration block can be generated based on the demonstration device data to represent the block generated when the device data of the IoT device is stored in the blockchain by running the components encapsulated in the target SDK, and the demonstration block can be visualized in the visualization interface.

[0061] By adopting the above method, through a user-interactive visual interface, users can participate in selecting the SDK for uploading IoT device data to the chain, and the demonstration data and demonstration blocks are visually presented to the users, wherein the demonstration data can represent the device data of the IoT device collected by running the components encapsulated in the SDK, and the demonstration block can represent the block generated when the device data of the IoT device is stored in the blockchain by running the components encapsulated in the SDK. In this way, the visualization of the entire process of storing the device itself of the IoT device or the relevant data during the operation of the device in the blockchain can be realized, thereby improving the user participation in the visualization of the IoT device data uploading to the chain and enhancing the user experience.

[0062] Please refer to Figure 2 , Figure 2 It is a flowchart of a visualization method for uploading IoT device data to a chain, shown as an exemplary embodiment of the present application.

[0063] In this embodiment, the visualization method for uploading the data of the IoT device can be applied to the client corresponding to the IoT device to be uploaded (which can be called the target IoT device), and the client can output a user-interactive visualization interface. In practical applications, the client can be a client directly deployed on the IoT device; for example, the client can be directly deployed on a larger home appliance such as a smart refrigerator, and output a user-interactive visualization interface through a display screen installed on the home appliance. Alternatively, the client can be a client deployed on other electronic devices that have established a connection with the IoT device (for example, a short-range wireless connection such as a WiFi connection or a Bluetooth connection); for example, the client can be deployed on a mobile phone, which has established a connection with a smaller home appliance such as a smart socket, and the client can output a user-interactive visualization interface through the display screen of the mobile phone.

[0064] like Figure 2 As shown, the above-mentioned method for visualizing the data of IoT devices on the chain may specifically include the following steps:

[0065] Step 202: Visually present at least one SDK provided by the operator of the blockchain in a visual interface; wherein the SDK encapsulates a component for storing IoT device data in the blockchain.

[0066] In this embodiment, the operator of the above-mentioned blockchain can encapsulate the component codes used to store IoT device data in the blockchain, and encapsulate these component codes into SDK (Software Development Kit). Among them, different SDKs can be used to store different IoT device data in the blockchain. For example, different IoT devices may use different chips for intelligent processing such as data collection, data transmission, and data calculation, or they may use the same chip; in this case, the same SDK can be used to store device data of IoT devices with the same chip in the blockchain, and different SDKs can be used to store device data of IoT devices with different chips in the blockchain.

[0067] After the above-mentioned operator encapsulates the above-mentioned component codes into SDK, it can further integrate the SDK into the communication hardware so that the communication hardware can be used to upload data of IoT devices to the chain. Among them, a communication hardware can integrate multiple different SDKs or only one SDK.

[0068] In the above case, the user of the IoT device can obtain the above communication hardware from the above operator, and deploy the communication hardware accordingly for the IoT device, so that the communication hardware can provide data uplink services for the IoT device. Specifically, if the above client is deployed on the IoT device, the communication hardware can be directly deployed on the IoT device; if the above client is deployed on other electronic devices that have established a connection with the IoT device, the communication hardware can be deployed on other electronic devices. In actual applications, the IoT device or other electronic devices may have an expansion card slot, and the communication hardware can be inserted into the expansion card slot as an expansion card, so that data uplink services can be directly provided for the IoT device, or data uplink services can be provided for the IoT device through other electronic devices.

[0069] Based on the above content, when visually presenting the process of uploading device data of the above-mentioned target IoT device, at least one SDK provided by the above-mentioned operator can be visually presented in a visual interface, so that users can view these SDKs and select an available and suitable SDK from these SDKs, that is, an SDK that is adapted to the IoT device.

[0070] Step 204: Select a target SDK corresponding to the target IoT device from the at least one SDK through a visual operation in the visual interface.

[0071] In this embodiment, a specific SDK (which may be referred to as a target SDK) may be selected from the at least one SDK through a visual operation in the visual interface. The target SDK may represent an SDK for storing the target IoT device data in the blockchain.

[0072] Step 206: Generate demonstration device data corresponding to the target IoT device, and visualize the demonstration device data in real time in the visualization interface; wherein the demonstration data is used to represent the device data of the IoT device collected by running the components encapsulated in the target SDK.

[0073] In this embodiment, the device data of the above-mentioned target IoT device can be collected by running the components encapsulated in the above-mentioned target SDK.

[0074] Accordingly, when visually presenting the process of uploading the device data of the target IoT device, demonstration device data corresponding to the target IoT device can be generated, and the demonstration device data can be visualized in real time in the visualization interface. The demonstration device data can be used to represent the device data of the target IoT device collected by running the components encapsulated in the target SDK. That is, the process of collecting the device data of the demonstration IoT device can be visualized in the visualization interface.

[0075] Step 208: Generate a demonstration block based on the demonstration device data, and visualize the demonstration block in the visualization interface; wherein the demonstration block is used to represent a block generated when the device data of the target IoT device is stored in the blockchain by running the components encapsulated in the target SDK.

[0076] In this embodiment, the collected device data of the target IoT device can also be stored in the blockchain by running the components encapsulated in the target SDK.

[0077] Accordingly, when visually presenting the process of uploading the device data of the target IoT device, a demonstration block can be generated based on the demonstration device data, and the demonstration block can be visualized in real time in the visualization interface. The demonstration block can be used to represent the block generated when the device data of the target IoT device is stored in the blockchain by running the components encapsulated in the target SDK.

[0078] The following is combined with Figures 3 to 10 The visualization interface shown provides a detailed explanation of the visualization method for uploading the above-mentioned IoT device data to the chain.

[0079] In some embodiments, in order to reduce the number of SDKs output to users through the above-mentioned visualization interface, so that users can select the above-mentioned target SDK from these SDKs faster and better, at least one industry corresponding to the SDK provided by the above-mentioned operator can be firstly visualized in the visualization interface, and a specific industry (which can be called the target industry) can be selected from the at least one industry through visualization operation in the visualization interface. Among them, the target industry can specifically be the industry to which the IoT device to be chained belongs, such as: batteries, two-wheeled vehicles, energy storage power stations, etc.

[0080] Subsequently, when visually presenting at least one SDK provided by the operator in the visualization interface, specifically, at least one SDK provided by the operator and corresponding to the target industry may be visually presented in the visualization interface.

[0081] like Figure 3 As shown, the visualization interface at this time can be specifically a visualization interface for industry selection. In the visualization interface, the industry can be visualized, for example, industry-related pictures, industry names, industry main application scenarios and other information can be displayed. In the visualization interface, the user can perform a selection operation by clicking anywhere in the frame where a certain industry is located, so as to select this industry as the above-mentioned target industry.

[0082] It should be noted that, in order to further enhance the user experience, in the above visualization interface, the frameworks of various industries as interface visual elements may have appearance features corresponding to the appearance features of the above communication hardware. For example, the appearance outline of the framework may be similar to the appearance outline of the communication hardware, and the material of the framework may be the same as the material of the communication hardware.

[0083] In such Figure 3 After selecting the above target industry in the visual interface shown in the figure, you can jump to Figure 4 The visual interface shown.

[0084] like Figure 4As shown, the visualization interface at this time can be specifically a visualization interface for SDK selection. In the visualization interface, at least one SDK corresponding to the above target industry can be visualized, for example, the communication hardware model, device chip model, SDK number, component number in the SDK and other information can be displayed. In the visualization interface, the user can perform a selection operation by clicking anywhere in the frame where a certain SDK is located to select this SDK as the above target SDK.

[0085] In some embodiments, in order to further improve user participation when uploading data to the IoT device chain and enable users to understand the main components used for data uploading in the above-mentioned communication hardware, after selecting the above-mentioned target SDK and before running the component code encapsulated in the target SDK, the components included in the target SDK can be visualized in the visualization interface, and then the components included in the target SDK can be confirmed through visualization operations in the visualization interface, so that users can view and confirm the components included in the target SDK.

[0086] In some embodiments, in order to enable users to better understand the main components used for data uplink in the above-mentioned communication hardware, when confirming the components included in the above-mentioned target SDK through visual operations in the above-mentioned visualization interface, the various components included in the target SDK can be taken as target components in turn, so that the target components can be confirmed through visual operations in the visualization interface, and after the confirmation of the target components is completed, the descriptive text corresponding to the target components will be visually presented in the visualization interface.

[0087] In such Figure 4 After selecting the target SDK in the visual interface shown above, you can jump to Figure 5 The visual interface shown.

[0088] like Figure 5 As shown, the visualization interface at this time can specifically be a visualization interface for component confirmation. In this visualization interface, the components contained in the above-mentioned target SDK can be visualized, such as: trusted firmware, object model, chain configuration information, etc. Among them, the object model can refer to some iconic information of the IoT device. In this visualization interface, the user can drag the frame where a component is located from the frame on the right representing the SDK to the frame on the left representing the IoT device to be chained, and perform the operation of dragging to the preset position to confirm this component. After dragging the frame where this component is located to the preset position, so that the confirmation of this component is completed, the description text corresponding to this component can also be displayed in the frame on the right representing the SDK at the position of the frame where this component was originally located.

[0089] It should be noted that, in order to further enhance the user experience, in the above-mentioned visualization interface, the framework of each component serves as an interface visual element, and its appearance characteristics may correspond to the appearance characteristics of the above-mentioned communication hardware. For example, the appearance outline of the framework may be similar to the appearance outline of the communication hardware, and the material of the framework may be the same as the material of the communication hardware. In addition, in order to enrich the content of the visualization interface, some interface visual elements similar to the hardware board elements may also be displayed in the visualization interface, such as: chips, memory, heat dissipation vias, etc.

[0090] In addition, you can also Figure 5 The visual interface shown shows a progress bar indicating the progress of component confirmation. After the confirmation of the trusted firmware is completed, the progress bar can be updated to indicate that "trusted firmware integration" has been completed; after the confirmation of the physical model is completed, the progress bar can be updated to indicate that "physical model integration" has been completed; after the confirmation of the uplink configuration information is completed, the progress bar can be updated to indicate that "uplink configuration information integration" has been completed.

[0091] In such Figure 5 After confirming the components included in the target SDK in the visual interface shown above, you can jump to Figure 6 The visual interface shown.

[0092] like Figure 6 As shown, the visualization interface at this time can specifically be a visualization interface for data collection. In this visualization interface, the above-mentioned demonstration device data can be visualized in real time, that is, the collection process of the demonstrative device data can be visualized. Specifically, the demonstration device data can be divided into multiple data blocks according to the order of generation time, and the loading of the demonstration device data can be represented by flipping and staggered data blocks, and the real-time collection of the demonstrative device data can be represented by the scrolling of the data blocks from top to bottom, so that the collection process of the demonstrative device data can be dynamically output.

[0093] It should be noted that, in order to further enhance the user experience, in the above-mentioned visualization interface, the entire framework is used as an interface visual element, and its appearance characteristics can correspond to the appearance characteristics of the above-mentioned communication hardware. For example, the appearance outline of the framework can be similar to the appearance outline of the communication hardware, and the material of the framework can be the same as the material of the communication hardware. In addition, in order to enrich the content of the visualization interface, some interface visual elements similar to the hardware board elements can also be displayed in the visualization interface, such as: chips, memory, heat dissipation vias, etc.

[0094] In addition, you can also Figure 6The progress bar indicating the progress of data collection and data on-chain is displayed in the visual interface shown. During the data collection process, the progress bar can be pushed to the "data collection" node; during the process of trusted processing of the collected device data, the progress bar can be pushed to the "data encryption" node; during the process of sending the trusted processed device data to the above-mentioned blockchain platform, the progress bar can be pushed to the "data transmission" node; after the data transmission is completed, the progress bar can be pushed to the "data on-chain" node when the blockchain platform stores the device data in the blockchain.

[0095] In some embodiments, in order to ensure the security of the on-chain data, a trusted firmware can be encapsulated in the SDK as a component. In this case, when the IoT device data is stored in the above-mentioned blockchain, the IoT device data can be specifically processed in a trusted manner based on the trusted firmware, and the IoT device data after the trusted processing can be stored in the blockchain. For example, the trusted firmware can be a cryptographic algorithm, and the IoT device data can be encrypted based on the trusted firmware, and the encrypted IoT device data can be stored in the blockchain.

[0096] Accordingly, when visually presenting the process of uploading the device data of the target IoT device, demonstration encrypted data corresponding to the demonstration device data can be generated, and the demonstration encrypted data can be visually presented in the visualization interface. The demonstration encrypted data can be used to represent the encrypted data obtained by encrypting the device data of the target IoT device based on the trusted firmware encapsulated in the target SDK. In this case, when generating a demonstration block based on the demonstration device data, the demonstration block can be specifically generated based on the demonstration encrypted data.

[0097] In such Figure 6 After completing the collection of device data in the visual interface shown in the figure, you can jump to Figure 7 The visual interface shown.

[0098] like Figure 7 As shown, the visualization interface at this time can specifically be a visualization interface for trusted data processing. In this visualization interface, the above-mentioned demonstration encrypted data can be visualized. Specifically, the above-mentioned demonstration device data can be divided into multiple data blocks according to the order of generation time, and each data block can be trusted in turn; after the trusted processing of a data block is completed, a "lock" mark can be added to this data block to indicate that the data block is converted into demonstration encrypted data; at the same time, the loading of the demonstration encrypted data can be indicated by flipping and staggered data blocks, and the trusted processing process of the demonstration device data can be indicated by the scrolling of the data blocks from top to bottom.

[0099] In such Figure 7 After completing the trusted processing of device data in the visual interface shown in the figure, you can jump to Figure 8 The visual interface shown.

[0100] like Figure 8 As shown, the visualization interface at this time can specifically be a visualization interface for data transmission. In the visualization interface, the above-mentioned demonstration encrypted data and data transmission protocol can be visualized; for example, the demonstration encrypted data can be moved on a transmission belt marked with "4G+MQTT" to indicate that data transmission is carried out under the support of the "4G+MQTT" capability.

[0101] In some embodiments, since the process of uploading real IoT device data to the chain is invisible to users, in order to further improve user participation when uploading IoT device data to the chain and enhance user experience, while storing the above-mentioned demonstration device data in the above-mentioned blockchain, the demonstration device data can be divided into multiple data blocks in the order of generation time. Subsequently, corresponding demonstration blocks can be generated based on each data block in turn, and the generated demonstration blocks can be visualized in the visualization interface. Among them, referring to the characteristics of the real block, the N+1th demonstration block contains the data blocks divided from the demonstration device data for generating the N+1th demonstration block, and the hash value of the data blocks divided from the demonstration device data for generating the Nth demonstration block contained in the Nth demonstration block; the hash value can be used as the block header of the N+1th demonstration block.

[0102] In such Figure 8 After completing the device data transfer in the visual interface shown in the figure, you can jump to Fig. 9 The visual interface shown.

[0103] like Fig. 9 As shown, the visualization interface at this time can specifically be a visualization interface for data on-chain. In this visualization interface, the above-mentioned demonstration blocks can be visualized; for example, a chain structure can be used to visualize these demonstration blocks in sequence.

[0104] In some embodiments, after the above-mentioned device data is stored in the above-mentioned blockchain, a data chain result corresponding to the device data can be generated. For example, the industry, device model, chip manufacturer and other data in the device data can be extracted as the data chain result corresponding to the device data, and the data chain result can be visualized in the above-mentioned visualization interface.

[0105] In such Fig. 9 After completing the device data chain in the visual interface shown, you can jump to Fig.10The visual interface shown.

[0106] like Fig.10 As shown, the visualization interface at this time can specifically be a visualization interface for displaying the data on-chain results. In this visualization interface, the above-mentioned data on-chain results can be visualized, for example: industry, equipment model, chip manufacturer and other information.

[0107] It should be noted that, in order to further enhance the user experience, in the above-mentioned visualization interface, the entire framework is used as an interface visual element, and its appearance characteristics can correspond to the appearance characteristics of the above-mentioned communication hardware. For example, the appearance outline of the framework can be similar to the appearance outline of the communication hardware, and the material of the framework can be the same as the material of the communication hardware. In addition, in order to enrich the content of the visualization interface, some interface visual elements similar to the hardware board elements can also be displayed in the visualization interface, such as: chips, memory, heat dissipation vias, etc.

[0108] In the above technical solution, for the IoT device to be put on the chain, the SDK provided by the operator of the blockchain and encapsulating the component for storing the IoT device data in the blockchain can be visually presented in a visual interface, and the target SDK corresponding to the IoT device can be selected through visual operation in the visual interface, so that demonstration device data for representing the device data of the IoT device collected by running the component encapsulated in the target SDK can be generated, and the demonstration device data can be visually presented in real time in the visual interface. Furthermore, a demonstration block for representing the block generated when the device data of the IoT device is stored in the blockchain by running the component encapsulated in the target SDK can be generated based on the demonstration device data, and the demonstration block can be visually presented in the visual interface.

[0109] By adopting the above method, through a user-interactive visual interface, users can participate in selecting the SDK for uploading IoT device data to the chain, and the demonstration data and demonstration blocks are visually presented to the users, wherein the demonstration data can represent the device data of the IoT device collected by running the components encapsulated in the SDK, and the demonstration block can represent the block generated when the device data of the IoT device is stored in the blockchain by running the components encapsulated in the SDK. In this way, the visualization of the entire process of storing the device itself of the IoT device or the relevant data during the operation of the device in the blockchain can be realized, thereby improving the user participation in the visualization of the IoT device data uploading to the chain and enhancing the user experience.

[0110] It should be noted that the demonstration data in this application is not necessarily real data, but is only a kind of demonstration data for real data.

[0111] Corresponding to the aforementioned method embodiments, the present application also provides device embodiments.

[0112] Please refer to Fig.11 , Fig.11 It is a structural diagram of a device shown in an exemplary embodiment of the present application. At the hardware level, the device includes a processor 1102, an internal bus 1104, a network interface 1106, a memory 1108 and a non-volatile memory 1110, and of course may also include other required hardware. One or more embodiments of the present application can be implemented based on software, such as the processor 1102 reading the corresponding computer program from the non-volatile memory 1110 into the memory 1108 and then running it. Of course, in addition to the software implementation, one or more embodiments of the present application do not exclude other implementations, such as logic devices or a combination of software and hardware, etc., that is to say, the execution subject of the following processing flow is not limited to each logic module, but can also be hardware or logic devices.

[0113] Please refer to Fig.12 , Fig.12 It is a block diagram of a visualization device for uploading IoT device data to a chain, shown as an exemplary embodiment of the present application.

[0114] The above-mentioned visualization device for uploading data of IoT devices can be applied to Fig.11 The device shown in the figure is used to implement the technical solution of the present application. Among them, a client corresponding to the target IoT device can be deployed on the device; the device includes:

[0115] SDK demonstration module 1202, visually presenting at least one SDK provided by the operator of the blockchain in a visual interface; wherein the SDK encapsulates a component for storing IoT device data in the blockchain;

[0116] An SDK selection module 1204 selects a target SDK corresponding to the target IoT device from the at least one SDK through a visual operation in the visual interface;

[0117] The acquisition demonstration module 1206 generates demonstration device data corresponding to the target IoT device, and presents the demonstration device data in real time in the visualization interface; wherein the demonstration data is used to represent the device data of the target IoT device collected by running the components encapsulated in the target SDK;

[0118] The on-chain demonstration module 1208 generates a demonstration block based on the demonstration device data, and visually presents the demonstration block in the visualization interface; wherein the demonstration block is used to represent a block generated when the device data of the target IoT device is stored in the blockchain by running the components encapsulated in the target SDK.

[0119] In some embodiments, the device is further used to:

[0120] Visually presenting at least one industry corresponding to the SDK provided by the operator in the visualization interface;

[0121] Selecting a target industry from the at least one industry through visual operation in the visual interface;

[0122] The visual presentation of at least one SDK provided by the operator of the blockchain in a visual interface includes:

[0123] At least one SDK corresponding to the target industry provided by the operator of the blockchain is visually presented in a visual interface.

[0124] In some embodiments, the device is further used to:

[0125] Before generating demonstration device data corresponding to the target IoT device, visually presenting components included in the target SDK in the visual interface;

[0126] The components included in the target SDK are confirmed through visual operations in the visual interface.

[0127] In some embodiments, the confirming the components included in the target SDK through visual operations in the visual interface includes:

[0128] Through visual operations in the visual interface, each target component included in the target SDK is confirmed, and after the confirmation of the target component is completed, the description text corresponding to the target component is visually presented in the visual interface.

[0129] In some embodiments, the components included in the SDK include trusted firmware;

[0130] The device is also used for:

[0131] Before generating a demonstration block based on the demonstration device data, generate demonstration encrypted data corresponding to the demonstration device data, and visually present the demonstration encrypted data in the visualization interface; wherein the demonstration encrypted data is used to represent encrypted data obtained by encrypting the device data based on the trusted firmware encapsulated in the target SDK;

[0132] The generating a demonstration block based on the demonstration device data comprises:

[0133] A demonstration block is generated based on the demonstration encrypted data.

[0134] In some embodiments, generating a demonstration block based on the demonstration device data includes:

[0135] Dividing the demonstration device data into a plurality of data blocks according to the order of generation time;

[0136] Generate corresponding demonstration blocks based on each data block in turn, and visualize the demonstration blocks in the visualization interface; wherein the demonstration blocks include the data blocks and the hash value of the data blocks included in the previous demonstration blocks.

[0137] In some embodiments, the device is further used to:

[0138] Generate a data chain result corresponding to the demonstration device data, and visualize the data chain result in the visualization interface.

[0139] In some embodiments, appearance characteristics of interface visual elements in the visualization interface correspond to appearance characteristics of the communication hardware.

[0140] In some embodiments, the appearance features include one or more of the following: appearance outline of the SDK; material; hardware board elements.

[0141] For the device embodiment, it basically corresponds to the method embodiment, so the relevant parts can refer to the partial description of the method embodiment. The device embodiment described above is only schematic, wherein the modules described as separate components may or may not be physically separated, and the components displayed as modules may or may not be physical modules, that is, they may be located in one place, or they may be distributed on multiple network modules. Some or all of the modules may be selected according to actual needs to achieve the purpose of the technical solution of the present application.

[0142] The systems, devices, modules or units described in the above embodiments may be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer, which may be in the form of a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email transceiver, a game console, a tablet computer, a wearable device or a combination of any of these devices.

[0143] In a typical configuration, a computer includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0144] The memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0145] Computer-readable media include permanent and non-permanent, removable and non-removable media that can store information by any method or technology. Information can be computer-readable instructions, data structures, program modules or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, read-only compact disk read-only memory (CD-ROM), digital versatile disk (DVD) or other optical storage, magnetic cassettes, disk storage, quantum memory, graphene-based storage media or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer-readable media does not include temporary computer-readable media (transitory media), such as modulated data signals and carrier waves.

[0146] It should be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity 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, commodity or device. In the absence of further restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0147] The above specific embodiments of the present application are described. Other embodiments are within the scope of the present application. In some cases, the actions or steps recorded in the present application can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the process depicted in the accompanying drawings does not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0148] The terms used in one or more embodiments of the present application are only for the purpose of describing specific embodiments, and are not intended to limit one or more embodiments of the present application. The singular forms of "a", "said" and "the" are also intended to include plural forms, unless the context clearly indicates other meanings. The term "and / or" refers to and includes any or all possible combinations of one or more associated listed items.

[0149] The description of the terms "one embodiment", "some embodiments", "example", "specific example" or "an implementation method" etc. used in one or more embodiments of the present application means that the specific features or characteristics described in conjunction with the embodiment are included in at least one embodiment of the present application. The schematic description of these terms is not necessarily for the same embodiment. Moreover, the specific features or characteristics described can be combined in a suitable manner in one or more embodiments of the present application. In addition, different embodiments and specific features or characteristics in different embodiments can be combined without contradicting each other.

[0150] It should be understood that, although the terms first, second, third, etc. may be used to describe various information in one or more embodiments of the present application, these information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of one or more embodiments of the present application, the first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information. Depending on the context, the word "if" as used herein may be interpreted as "at the time of" or "when" or "in response to determination".

[0151] The above description is merely a preferred embodiment of one or more embodiments of the present application and is not intended to limit one or more embodiments of the present application. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of one or more embodiments of the present application shall be included in the scope of protection of one or more embodiments of the present application.

[0152] The user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with the relevant laws, regulations and standards of relevant countries and regions, and provide corresponding operation entrances for users to choose to authorize or refuse.

Claims

1. A visualization method for uploading data of an IoT device to a chain, applied to a client corresponding to a target IoT device; the method comprises: Visually presenting at least one SDK provided by the operator of the blockchain in a visual interface; wherein the SDK encapsulates a component for storing IoT device data in the blockchain; Selecting a target SDK corresponding to the target IoT device from the at least one SDK through a visual operation in the visual interface; Generate demonstration device data corresponding to the target IoT device, and present the demonstration device data in real time in the visualization interface; wherein the demonstration data is used to represent the device data of the target IoT device collected by running the components encapsulated in the target SDK; A demonstration block is generated based on the demonstration device data, and the demonstration block is visually presented in the visualization interface; wherein the demonstration block is used to represent a block generated when the device data of the target IoT device is stored in the blockchain by running the components encapsulated in the target SDK.

2. The method according to claim 1, further comprising: Visually presenting at least one industry corresponding to the SDK provided by the operator in the visualization interface; Selecting a target industry from the at least one industry through visual operation in the visual interface; The visual presentation of at least one SDK provided by the operator of the blockchain in a visual interface includes: At least one SDK corresponding to the target industry provided by the operator of the blockchain is visually presented in a visual interface.

3. The method according to claim 1, before generating the demonstration device data corresponding to the target IoT device, the method further comprises: Visually presenting the components included in the target SDK in the visualization interface; The components included in the target SDK are confirmed through visual operations in the visual interface.

4. The method according to claim 3, wherein the confirming the components included in the target SDK through visual operations in the visual interface comprises: Through visual operations in the visual interface, each target component included in the target SDK is confirmed, and after the confirmation of the target component is completed, the description text corresponding to the target component is visually presented in the visual interface.

5. The method according to claim 1, wherein the components included in the SDK include trusted firmware; Before generating a demonstration block based on the demonstration device data, the method further includes: Generate demonstration encrypted data corresponding to the demonstration device data, and visually present the demonstration encrypted data in the visualization interface; wherein the demonstration encrypted data is used to represent encrypted data obtained by encrypting the device data based on the trusted firmware encapsulated in the target SDK; The generating a demonstration block based on the demonstration device data comprises: A demonstration block is generated based on the demonstration encrypted data.

6. The method according to claim 1, wherein generating a demonstration block based on the demonstration device data comprises: Dividing the demonstration device data into a plurality of data blocks according to the order of generation time; Generate a corresponding demonstration block based on each data block in turn; wherein the demonstration block includes the data block and a hash value of the data block included in the previous demonstration block.

7. The method according to claim 1, further comprising: Generate a data chain result corresponding to the demonstration device data, and visualize the data chain result in the visualization interface. 8 . The method according to claim 1 , wherein appearance features of interface visual elements in the visualization interface correspond to appearance features of the communication hardware.

9. According to the method of claim 8, the appearance features include one or more of the following: appearance outline of SDK; material; hardware board elements.

10. A visualization device for uploading data of an IoT device to a chain, applied to a client corresponding to a target IoT device; the device comprises: An SDK demonstration module that visually presents at least one SDK provided by the operator of the blockchain in a visual interface; wherein the SDK encapsulates a component for storing IoT device data in the blockchain; An SDK selection module, which selects a target SDK corresponding to the target IoT device from the at least one SDK through visual operations in the visual interface; A collection demonstration module generates demonstration device data corresponding to the target IoT device, and presents the demonstration device data in real time in the visualization interface; wherein the demonstration data is used to represent the device data of the target IoT device collected by running the components encapsulated in the target SDK; The on-chain demonstration module generates a demonstration block based on the demonstration device data, and visually presents the demonstration block in the visualization interface; wherein the demonstration block is used to represent the block generated when the device data of the target IoT device is stored in the blockchain by running the components encapsulated in the target SDK.

11. An electronic device, comprising: processor; a memory for storing processor-executable instructions; The processor implements the method according to any one of claims 1 to 9 by running the executable instructions.

12. A computer-readable storage medium having computer instructions stored thereon, wherein the instructions are executed by a processor to implement the method according to any one of claims 1 to 9.

Images