Method, device and medium for visualizing data chaining of internet of things devices

Abstract

One or more embodiments of the present application provide a method, device, equipment and medium for visualizing Internet of Things device data chaining, the method is applied to a client corresponding to a target Internet of Things device, and includes: visualizing an SDK provided by an operator of a blockchain for storing Internet of Things device data into the blockchain in a visual interface; selecting a target SDK corresponding to the target Internet of Things device in the visual interface through a visual operation; generating demonstration device data corresponding to the target Internet of Things device and visualizing the demonstration device data in the visual interface in real time; the demonstration data is used to represent device data of the target Internet of Things device collected by running the target SDK; generating a demonstration block based on the demonstration device data and visualizing the demonstration block in the visual interface; the demonstration block is used to represent a block generated when the device data of the target Internet of Things device is stored into the blockchain by running the target SDK.

Description

TECHNICAL FIELD

[0001] One or more embodiments of the present application relate to the technical field of Internet of Things, and in particular to a method and device for visualizing data on-chain of Internet of Things equipment, and a medium. BACKGROUND

[0002] Internet of Things (IoT) refers to connecting various information sensing devices (such as radio frequency identification, infrared sensor, laser scanner, global positioning system, etc.) with objects (such as household appliances, cars, buildings, etc.) through the Internet to exchange and communicate information, so as to realize 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 also enables information exchange between things and people.

[0003] Internet of Things equipment refers to physical objects that can be connected through 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 Internet of Things equipment 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 in-vehicle units, smart traffic lights, etc.), healthcare Internet of Things devices (such as remote patient monitoring devices, medication management devices, etc.), etc.

[0004] With the development of information technology, Internet of Things has become a bridge connecting the physical world and the digital world, greatly promoting the intelligent process of various industries. However, with the rapid growth in the number of Internet of Things equipment, the traditional centralized management of data processing mode faces many challenges, including but not limited to data security, privacy protection, trust establishment and operational efficiency. These problems not only limit the wider application and development of Internet of Things technology, but also pose a potential threat to the safety and privacy of users.

[0005] Blockchain is a distributed ledger, one of its core features is that once data is recorded, it is almost impossible to be tampered with. In order to ensure the integrity, authenticity and reliability of the data of Internet of Things equipment, the data of Internet of Things equipment can be processed on-chain, that is, the data of Internet of Things equipment itself or the data of Internet of Things equipment running time is stored in the blockchain. However, the on-chain process of Internet of Things equipment data is usually not user-oriented, and users cannot perceive the on-chain process of Internet of Things equipment data. Therefore, how to improve user participation in the on-chain process of Internet of Things equipment data and improve user experience has become a problem to be solved. SUMMARY

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

[0007] The present application provides a visualization method for Internet of Things device data on-chain, applied to a client corresponding to a target Internet of Things device; the method comprises:

[0008] Visualize at least one SDK provided by an operator of a blockchain in a visualization interface; wherein the SDK encapsulates a component for storing Internet of Things device data into the blockchain;

[0009] In the visualization interface, a target SDK corresponding to the target Internet of Things device is selected from the at least one SDK through a visual operation;

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

[0011] 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 storing device data of the target Internet of Things device into the blockchain by running the component encapsulated in the target SDK.

[0012] The present application also provides a visualization device for Internet of Things device data on-chain, applied to a client corresponding to a target Internet of Things device; the device comprises:

[0013] An SDK demonstration module visualizes at least one SDK provided by an operator of a blockchain in a visualization interface; wherein the SDK encapsulates a component for storing Internet of Things device data into the blockchain;

[0014] An SDK selection module selects a target SDK corresponding to the target Internet of Things device from the at least one SDK in the visualization interface through a visual operation;

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

[0016] The upper chain demonstration module generates a demonstration block based on the demonstration device data, and visualizes 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 Internet of Things device is stored into the block chain by running the component encapsulated in the target SDK.

[0017] The application further provides an electronic device, comprising:

[0018] a processor;

[0019] a memory for storing processor executable instructions;

[0020] The processor implements the steps of the method according to any one of the preceding method embodiments by running the executable instructions.

[0021] The application further provides a computer readable storage medium having computer instructions stored thereon, which, when executed by a processor, implement the steps of the method according to any one of the preceding method embodiments.

[0022] In the above technical solution, for the Internet of Things device to be chained, the SDK provided by the operator of the block chain and encapsulating the component for storing the Internet of Things device data into the block chain can be visualized in the visualization interface, and the target SDK corresponding to the Internet of Things device can be selected from the visualization interface through visual operation, so that demonstration device data representing the device data of the Internet of Things device collected by running the component encapsulated in the target SDK can be generated, and the demonstration device data can be visualized in real time in the visualization interface. Furthermore, demonstration blocks representing the blocks generated when the device data of the Internet of Things device is stored into the block chain by running the component encapsulated in the target SDK can be generated based on the demonstration device data, and the demonstration blocks can be visualized in the visualization interface.

[0023] In the above manner, through the user-interactive visualization interface, the user can participate in the selection of the SDK for the Internet of Things device data chaining, and the demonstration data and the demonstration blocks can be visualized and presented to the user. The demonstration data can represent the device data of the Internet of Things device collected by running the component encapsulated in the SDK, and the demonstration blocks can represent the blocks generated when the device data of the Internet of Things device is stored into the block chain by running the component encapsulated in the SDK. Thus, the visualization of the entire process of storing the device data of the Internet of Things device into the block chain can be realized, thereby improving the user participation in the visualization of the Internet of Things device data chaining and enhancing the user experience. BRIEF DESCRIPTION OF DRAWINGS

[0024] The following will be described in the description of the exemplary embodiments using the accompanying drawings needed, in which:

[0025] Figure 1 is a schematic diagram of a blockchain system according to an exemplary embodiment of the present application.

[0026] Figure 2 is a flowchart of a method for visualizing data on a blockchain of an Internet of Things device according to an exemplary embodiment of the present application.

[0027] Figure 3 is a schematic diagram of a visual interface according to an exemplary embodiment of the present application.

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

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

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

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

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

[0033] Figure 9 is a schematic diagram of another visual interface according to an exemplary embodiment of the present application.

[0034] Figure 10 is a schematic diagram of another visual interface according to an exemplary embodiment of the present application.

[0035] Figure 11 is a schematic diagram of a device according to an exemplary embodiment of the present application.

[0036] Figure 12 is a block diagram of a visualizing apparatus for data on a blockchain of an Internet of Things device according to an exemplary embodiment of the present application. DETAILED DESCRIPTION

[0037] The exemplary embodiments will be described in detail herein with reference to the attached drawings. The description herein refers to the accompanying drawings, which show by way of example the exemplary embodiments. Wherever possible, the same reference numbers are used in the different drawings to refer to the same or similar elements. The following exemplary embodiments are described in sufficient detail to enable those skilled in the art to make and use the embodiments in accordance with the one or more embodiments of the present application. The embodiments described in the following exemplary embodiments are not meant to represent the only ways in which the one or more embodiments of the present application can be implemented but are intended to represent the way in which one or more embodiments of the present application can be implemented.

[0038] It is noted that the steps of the methods of the respective embodiments are not necessarily performed in the order shown and described herein in other embodiments. In some other embodiments, the methods can include more or less steps than described herein. Also, a single step described herein can be broken down into multiple steps in other embodiments, and multiple steps described herein can be combined into a single step 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 a combination of private blockchain and consortium blockchain, a combination of consortium blockchain and public blockchain, etc.

[0040] Among the three types of blockchains described above, the public blockchain has the highest degree of decentralization. Participants (also referred to as nodes in the blockchain) who join the public blockchain can read data records on the chain, participate in transactions, compete for the right to record new blocks, etc. Moreover, the nodes can freely join or leave the network and perform related operations.

[0041] The private blockchain is the opposite, where the write permission of the network is controlled by an organization (or an entity) and the read permission is regulated by the organization. That is, the private blockchain can be considered 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 consortium blockchain is between the public blockchain and the private blockchain and can achieve "partial decentralization". The nodes in the consortium blockchain usually have corresponding organizations (or entities); the nodes join the network by authorization and form a consortium of stakeholders to jointly maintain the operation of the blockchain.

[0043] Based on the basic characteristics of the blockchain, the blockchain is usually composed of a plurality of blocks. In these blocks, there are time stamps corresponding to the time when the block is created. All blocks strictly follow the time stamps recorded in the blocks to form a data chain that is ordered in time.

[0044] For data generated outside the blockchain, the data can be structured into a standard transaction format supported by the blockchain, and then published to the blockchain. The nodes participating in consensus in the blockchain system can reach consensus on the transaction, and execute the transaction after the consensus is completed. The transaction and the execution result can be persisted in the blockchain.

[0045] In the blockchain system, different participants can establish a distributed blockchain network through the deployed nodes. In actual applications, the connection relationship between each node and different nodes can be regarded as a blockchain network, and the connection relationship, data interaction, etc. between each node and different nodes can be regarded as a blockchain system. 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 consistency and correctness of the ledger data on each node of the decentralized (or multi-centralized) multiple nodes. Each node in the blockchain system runs a blockchain program, and under the design of a certain fault tolerance requirement, the consensus protocol is used to ensure that all loyal nodes have the same transaction, so as to ensure that all loyal nodes have the same execution result of the same transaction, and to package the transaction and the execution result to generate a block.

[0046] The nodes in the blockchain system can be generally divided into consensus nodes and non-consensus nodes. The consensus nodes are nodes running the consensus protocol. The non-consensus nodes can forward the received transactions sent by the client to the consensus nodes, the consensus nodes can propose transactions, attempt to construct blocks, and send the constructed blocks to other nodes, so that the consensus nodes and the non-consensus nodes can store the blocks.

[0047] Specifically, the consensus nodes in the blockchain system can reach consensus on the transactions contained in the new block to be connected to the chain block structure based on the consensus protocol, so as to ensure that each consensus node agrees on the content and order of the transactions contained in the block, and to realize the construction of the block. After the consensus is completed, the consensus nodes 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 under the condition that the transaction execution results of each node are consistent. The finalization refers to the completion of the execution of the transactions contained in the block, and the transaction execution results are approved 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 a transaction included in a block that has been consensus completed, and the message can indicate that the block has been consensus completed and the transaction included in the block has been executed. Therefore, the consistency of the transaction execution results of each consensus node for the block can be confirmed according to the message, so that the finalization of the block can be completed when the transaction execution results of each consensus node are consistent.

[0049] Please refer to Figure 1 , Figure 1 is a schematic diagram of a blockchain system according to an example embodiment of the present application.

[0050] As Figure 1 indicates, the blockchain system can maintain one or more blockchains (for example: public blockchain, private blockchain, consortium blockchain, etc.), and can include a plurality of blockchain nodes for carrying the one or more blockchains; for example, the blockchain node 1, the blockchain node 2, the blockchain node 3, the blockchain node 4, the blockchain node i, etc. as shown in Figure 1 , 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 the blockchain systems.

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

[0052] Blockchain technology, as a distributed ledger technology, has attracted much attention due to its unique characteristics, and its main advantages are as follows:

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

[0054] Security: Through the consensus protocol, 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 saved and traceable, which is of great significance for improving supply chain transparency, tracing product sources, etc.

[0056] Decentralized Architecture: Blockchain adopts a peer-to-peer network structure without a single control node, which reduces the risk of single-point failure and enhances the system's resistance to censorship.

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

[0058] Given the characteristics of blockchain technology described above, there are many advantages to putting IoT device data on the chain. The non-tamperable nature of blockchain provides strong protection for the authenticity of IoT device data, ensuring consistency and reliability from the source to the final use of each link. With the security measures of blockchain, unauthorized data access and malicious software 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 appropriate measures. Based on the blockchain platform, different enterprises and institutions can share valuable information without sacrificing their data sovereignty, and work together to promote industry standards and technological progress. Using smart contracts to automate certain types of transactions, such as automatic payments, condition-triggered tasks, etc., can significantly improve efficiency and reduce costs.

[0059] As can be seen, putting IoT device data on the chain can ensure the integrity, authenticity and reliability of IoT device data, laying a solid technical foundation for more extensive interconnection and intelligent applications. However, the process of putting IoT device data on the chain is usually not user-oriented, and users cannot perceive the process of putting IoT device data on the chain. For users, the user engagement is low and the user experience is poor in the process of putting IoT device data on the chain.

[0060] One or more embodiments of the present application provide a technical solution for visualizing Internet of Things device data on-chain, in which, for an Internet of Things device to be on-chain, an SDK provided by an operator of a blockchain and encapsulating components for storing Internet of Things device data in the blockchain can be visually presented in a visual interface, and a target SDK corresponding to the Internet of Things device can be selected from the visual interface through visual operations, so that demonstration device data representing device data of the Internet of Things device collected by running the components encapsulated in the target SDK can be generated and visually presented in the visual interface in real time. Further, demonstration blocks representing blocks generated when storing the device data of the Internet of Things device in the blockchain by running the components encapsulated in the target SDK can be generated based on the demonstration device data and visually presented in the visual interface.

[0061] In the above manner, through the user-interactive visual interface, the user can participate in selecting an SDK for Internet of Things device data on-chain, and demonstration data and demonstration blocks can be visually presented to the user, where the demonstration data can represent device data of the Internet of Things device collected by running the components encapsulated in the SDK, and the demonstration blocks can represent blocks generated when storing the device data of the Internet of Things device in the blockchain by running the components encapsulated in the SDK. Thus, the entire process of storing device data of the Internet of Things device itself or related data of the device runtime in the blockchain can be visualized, thereby improving user engagement in visualizing Internet of Things device data on-chain and enhancing user experience.

[0062] Please refer to Figure 2 , Figure 2 is a flowchart of an exemplary embodiment of a method for visualizing Internet of Things device data on-chain.

[0063] In the present embodiment, the above-mentioned method for visualizing Internet of Things device data on-chain can be applied to a client (Client) corresponding to an Internet of Things device to be on-chain (which can be referred to as a target Internet of Things device), and the client can output a user-interactive visual interface. In actual applications, the client can be a client directly deployed on an Internet of Things device; for example, the client can be directly deployed on a large household appliance such as a smart refrigerator, and the user-interactive visual interface can be output through a display screen installed on the household appliance. Alternatively, the client can be a client deployed on another electronic device that has established a connection (such as a WiFi connection, a Bluetooth connection, or other short-range wireless connection) with the Internet of Things device; for example, the client can be deployed on a mobile phone that has established a connection with a small household device such as a smart socket, and the user-interactive visual interface can be output through a display screen of the mobile phone.

[0064] As shown in the above-mentioned method for visualizing data on-chain of Internet of Things devices, the method can specifically include the following steps: Figure 2

[0065] Step 202: Visualize at least one SDK provided by an operator of the blockchain in the visualization interface; wherein the SDK encapsulates components for storing data of Internet of Things devices into the blockchain.

[0066] In this embodiment, the operator of the blockchain can encapsulate the component code for storing data of Internet of Things devices into the blockchain into SDK (Software Development Kit). Different SDKs can be used to store different data of Internet of Things devices into the blockchain. For example, different chips can be used by different Internet of Things devices for data collection, data transmission, data calculation, and other intelligent processing, or the same chip can be used. In this case, the same SDK can be used to store device data of Internet of Things devices with the same chip into the blockchain, and different SDKs can be used to store device data of Internet of Things devices with different chips into the blockchain.

[0067] After the operator encapsulates the component code into the SDK, the SDK can be further integrated into the communication hardware, so that the communication hardware can be used for data on-chain of Internet of Things devices. Multiple different SDKs can be integrated into one communication hardware, or only one SDK can be integrated.

[0068] In the above case, the user of the Internet of Things device can obtain the communication hardware from the operator, and deploy the communication hardware for the Internet of Things device to provide data on-chain service for the Internet of Things device. Specifically, if the client is deployed on the Internet of Things device, the communication hardware can be directly deployed on the Internet of Things device; if the client is deployed on other electronic devices connected to the Internet of Things device, the communication hardware can be deployed on other electronic devices. In actual application, the Internet of Things device or other electronic devices can have an expansion card slot, and the communication hardware can be inserted into the expansion card slot as an expansion card, thereby directly providing data on-chain service for the Internet of Things device, or providing data on-chain service for the Internet of Things device through other electronic devices.

[0069] ​Based on the above, when visualizing the device data chaining process of the target IoT device, the at least one SDK provided by the operator can be visualized in the visualization interface, so that the user can view these SDKs and select a suitable SDK, i.e., an SDK that adapts to the IoT device.

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

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

[0072] Step 206: Generating demonstration device data corresponding to the target IoT device and visualizing the demonstration device data in the visualization interface in real time; the demonstration data can represent device data of the IoT device collected by running a component encapsulated in the target SDK.

[0073] In this embodiment, device data of the target IoT device can be collected by running a component encapsulated in the target SDK.

[0074] Correspondingly, when visualizing the device data chaining process of the target IoT device, demonstration device data corresponding to the target IoT device can be generated and visualized in the visualization interface in real time. The demonstration device data can represent device data of the target IoT device collected by running a component encapsulated in the target SDK. That is, the collection process of the demonstration device data of the IoT device can be visualized in the visualization interface.

[0075] Step 208: Generating a demonstration block based on the demonstration device data and visualizing the demonstration block in the visualization interface; the demonstration block can represent a block generated when device data of the target IoT device is stored in the blockchain by running a component encapsulated in the target SDK.

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

[0077] Correspondingly, in the visual presentation of the device data chaining process of the target IoT device, a demonstration block can be generated based on the demonstration device data, and the demonstration block is visually presented in real time in the visual interface. Wherein, the demonstration block can be used to represent the block generated when the device data of the target IoT device is stored into the blockchain by running the components encapsulated in the target SDK.

[0078] The visual interface as shown in Figures 3 to 10 will be used to illustrate the visual method of the IoT device data chaining in detail.

[0079] In some embodiments, in order to reduce the number of SDKs output to the user through the visual interface, so that the user can select the target SDK from these SDKs faster and better, first, at least one industry corresponding to the SDK provided by the operator can be visually presented in the visual interface, and a specific industry (which can be referred to as a target industry) can be selected from the at least one industry through a visual operation in the visual interface. Wherein, the target industry can be the industry to which the IoT device to be chained belongs, for example: battery, two-wheeled vehicle, energy storage power station, etc.

[0080] Subsequently, when the at least one SDK provided by the operator is visually presented in the visual interface, at least one SDK corresponding to the target industry provided by the operator can be visually presented in the visual interface.

[0081] As shown in Figure 3 , the visual interface at this time can be a visual interface for industry selection. In the visual interface, industries can be visually presented, for example: industry-related pictures, industry names, industry main application scenarios, etc. The user can perform a selection operation by clicking any position within the framework of a certain industry in the visual interface to select this industry as the target industry.

[0082] It should be noted that in order to further improve the user experience, in the visual interface, the framework of each industry as an interface visual element, its appearance characteristics can correspond to the appearance characteristics of the 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.

[0083] After the target industry is selected in the visual interface as shown in Figure 3 , the visual interface as shown in Figure 4 can be jumped to.

[0084] As shown in Figure 4As shown, the visualization interface at this point can specifically be a visualization interface for SDK selection. This visualization interface can display at least one SDK corresponding to the aforementioned target industry, for example, it can display information such as communication hardware model, device chip model, SDK number, and component numbers within the SDK. Users can select an SDK as the target SDK by clicking anywhere within the frame of that SDK in this visualization interface.

[0085] In some embodiments, in order to further improve user participation when IoT device data is uploaded to the blockchain and enable users to understand the main components in the communication hardware used for data uploading, after selecting the target SDK, 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 target SDK through visual operations in the above-mentioned visualization interface, each component included in the target SDK can be taken as the target component in turn. Thus, the target component can be confirmed through visual operations in the visualization interface, and after the confirmation of the target component is completed, the description text corresponding to the target component is visually presented in the visualization interface.

[0087] In such Figure 4 After selecting the target SDK in the visualization interface shown, you will be redirected to the following page. Figure 5 The visual interface shown.

[0088] like Figure 5 As shown, the visualization interface at this point can specifically be a visualization interface for component confirmation. In this visualization interface, the components included in the target SDK can be visually presented, such as trusted firmware, object models, and on-chain configuration information. The object model can refer to some of the identifying information of an IoT device. Users can confirm a component by dragging its frame from the right-hand frame representing the SDK to the left-hand frame representing the IoT device to be added to the blockchain, thus moving it to a preset position. After confirming the component, the corresponding descriptive text is displayed in the right-hand frame representing the SDK, where the component originally resided.

[0089] It should be noted that, in order to further improve the user experience, in the above visualization interface, the frame of each component as an interface visual element, its appearance features can correspond to the appearance features of the communication hardware. For example, the appearance profile of the frame can be similar to the appearance profile of the communication hardware, and the material of the frame 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, memories, heat dissipation through holes, etc.

[0090] In addition, as shown in the visualization interface Figure 5 The progress bar representing the confirmation progress of the components can be displayed in the visualization interface. After the confirmation of the trusted firmware is completed, the progress bar can be updated to represent that "trusted firmware integration" is completed; after the confirmation of the object model is completed, the progress bar can be updated to represent that "object model integration" is completed; after the confirmation of the uplink configuration information is completed, the progress bar can be updated to represent that "uplink configuration information integration" is completed.

[0091] After the confirmation of the components contained in the above target SDK is completed in the visualization interface as shown in Figure 5 , the visualization interface as shown in Figure 6 can be jumped to.

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

[0093] It should be noted that, in order to further improve the user experience, in the above visualization interface, the frame of each component as an interface visual element, its appearance features can correspond to the appearance features of the communication hardware. For example, the appearance profile of the frame can be similar to the appearance profile of the communication hardware, and the material of the frame 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, memories, heat dissipation through holes, etc.

[0094] In addition, as shown in the visualization interface Figure 6The visualization interface displays a progress bar indicating the progress of data acquisition and data upload to the blockchain. During data acquisition, the progress bar can advance to the "Data Acquisition" node; during the trusted processing of the acquired device data, the progress bar can advance to the "Data Encryption" node; during the transmission of the trusted processed device data to the aforementioned blockchain platform, the progress bar can advance to the "Data Transmission" node; and after data transmission is completed, during the process of the blockchain platform storing the device data in the blockchain, the progress bar can advance to the "Data Upload to Blockchain" node.

[0095] In some embodiments, to ensure the security of on-chain data, trusted firmware can be encapsulated as a component within the SDK. In this case, when storing IoT device data into the aforementioned blockchain, the trusted firmware can be used to perform trusted processing on the IoT device data, and the processed IoT device data can then be stored in the blockchain. For example, the trusted firmware can be a cryptographic algorithm, which can be used to encrypt the IoT device data, and the encrypted IoT device data can then be stored in the blockchain.

[0096] Accordingly, when visualizing the process of uploading device data from the aforementioned target IoT device to the blockchain, demonstration encrypted data corresponding to the demonstration device data can be generated and visualized in the visualization interface. This demonstration encrypted data can represent 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 specifically be generated based on the demonstration encrypted data.

[0097] In such Figure 6 After completing the device data collection in the visual interface shown, you can then proceed to the following... 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 aforementioned encrypted demonstration data can be visually presented. Specifically, the demonstration device data can be divided into multiple data blocks according to the order of its generation, and trusted processing can be performed on each data block sequentially. After the trusted processing of a data block is completed, a "lock" identifier can be added to this data block to indicate that the data block has been transformed into encrypted demonstration data. Simultaneously, the loading of the encrypted demonstration data can be represented by flipping or staggering the data blocks, and the trusted processing process of the demonstration device data can be represented by scrolling the data blocks from top to bottom.

[0099] After the trusted processing of the device data is completed in the visualization interface as shown in Figure 7 , the visualization interface as shown in Figure 8 can be jumped to.

[0100] As shown in Figure 8 , the visualization interface at this time can be a visualization interface for data transmission. In this visualization interface, the above-mentioned demonstration encrypted data and data transmission protocol can be visually presented; for example, the demonstration encrypted data can be moved on a transmission belt marked "4G+MQTT", indicating that data transmission is supported by "4G+MQTT" capabilities.

[0101] In some embodiments, since the real Internet of Things device data on-chain process is invisible to the user, in order to further improve the user's participation in the Internet of Things device data on-chain process and improve the user experience, while storing the above-mentioned demonstration device data into the above-mentioned blockchain, the demonstration device data can be divided into multiple data blocks in the order of generation time. Subsequently, the corresponding demonstration blocks can be generated based on each data block in turn, and the generated demonstration blocks can be visually presented in the visualization interface. Referring to the characteristics of the real block, the N+1th demonstration block contains the data block divided by the demonstration device data for generating the N+1th demonstration block, and the Nth demonstration block contains the hash value of the data block divided by the demonstration device data for generating the Nth demonstration block; the hash value can be used as the block header of the N+1th demonstration block.

[0102] After the transmission of the device data is completed in the visualization interface as shown in Figure 8 , the visualization interface as shown in Figure 9 can be jumped to.

[0103] As shown in Figure 9 , the visualization interface at this time can be a visualization interface for data on-chain. In this visualization interface, the above-mentioned demonstration blocks can be visually presented; for example: a chain structure can be used to visually present these demonstration blocks in turn.

[0104] In some embodiments, after the above-mentioned device data is stored into the above-mentioned blockchain, a data on-chain result corresponding to the device data can be generated, for example: the industry, device model, chip manufacturer, etc. data in the device data can be extracted as the data on-chain result corresponding to the device data, and the data on-chain result can be visually presented in the above-mentioned visualization interface.

[0105] After the on-chain of the device data is completed in the visualization interface as shown in Figure 9 , the visualization interface as shown in Figure 10The visual interface shown.

[0106] As Figure 10 shown, the visual interface at this time can be a visual interface for data on-chain result display. In the visual interface, the above-mentioned data on-chain result can be visually presented, such as industry, equipment model, chip manufacturer, etc.

[0107] It should be noted that, in order to further improve the user experience, in the above-mentioned visual interface, the entire framework as an interface visual element, its appearance characteristics can correspond to the appearance characteristics of the above-mentioned communication hardware. For example, the appearance profile of the framework can be similar to the appearance profile 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 visual interface, some interface visual elements similar to the hardware board elements can also be displayed in the visual interface, such as chips, memories, heat dissipation through holes, etc.

[0108] In the above technical solution, for the Internet of Things device to be on-chain, the SDK provided by the operator of the blockchain and encapsulating the component for storing the Internet of Things device data into the blockchain can be visually presented in the visual interface, and the target SDK corresponding to the Internet of Things device can be selected from the visual interface through visual operation, so that the demonstration device data representing the device data of the Internet of Things device collected by running the component encapsulated in the target SDK can be generated, and the demonstration device data can be visually presented in the visual interface in real time. Further, the demonstration block representing the block generated when the device data of the Internet of Things device is stored into 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] In the above manner, through the user-interactive visual interface, the user can participate in selecting the SDK for the Internet of Things device data on-chain, and the demonstration data and the demonstration block can be visually presented to the user, wherein the demonstration data can represent the device data of the Internet of Things device collected by running the component encapsulated in the SDK, and the demonstration block can represent the block generated when the device data of the Internet of Things device is stored into the blockchain by running the component encapsulated in the SDK. Thus, the visualization of the entire process of storing the device itself or the related data of the device running of the Internet of Things device into the blockchain can be realized, so that the user participation in the visualization of the Internet of Things device data on-chain can be improved, and the user experience can be improved.

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

[0111] Corresponding to the embodiments of the foregoing method, the present application also provides embodiments of an apparatus.

[0112] Reference is made to Figure 11 , Figure 11 is a structural schematic diagram of a device according to 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 can also include other required hardware. One or more embodiments of the present application can be implemented in a software manner, such as reading a corresponding computer program from the non-volatile memory 1110 into the memory 1108 by the processor 1102 and then running. Of course, in addition to the software implementation, one or more embodiments of the present application do not exclude other implementation manners, such as a logic device or a combination of software and hardware, etc., that is, the execution subject of the following processing flow is not limited to each logical module, but can also be hardware or a logic device.

[0113] Reference is made to Figure 12 , Figure 12 is a block diagram of a visualization apparatus for Internet of Things device data chaining according to an exemplary embodiment of the present application.

[0114] The above-mentioned visualization apparatus for Internet of Things device data chaining can be applied to Figure 11 the device shown in the figure to implement the technical solutions of the present application. Among them, a client corresponding to a target Internet of Things device can be deployed on the device; the apparatus includes:

[0115] an SDK demonstration module 1202, which visualizes at least one SDK provided by an operator of a blockchain in a visualization interface; wherein the SDK encapsulates a component for storing Internet of Things device data into a blockchain;

[0116] an SDK selection module 1204, which selects a target SDK corresponding to the target Internet of Things device from the at least one SDK through a visual operation in the visualization interface;

[0117] a demonstration collection module 1206, which generates demonstration device data corresponding to the target Internet of Things device and performs real-time visualization of the demonstration device data in the visualization interface; wherein the demonstration data is used to represent device data of the target Internet of Things device collected by running the component encapsulated in the target SDK;

[0118] The upper chain demonstration module 1208 generates a demonstration block based on the demonstration device data, and visualizes the demonstration block in the visualization interface; wherein, the demonstration block is used to represent a block generated when device data of the target Internet of Things device is stored into the block chain by running a component encapsulated in the target SDK.

[0119] In some embodiments, the apparatus is further configured to:

[0120] visualize at least one industry corresponding to the SDK provided by the operation party in the visualization interface;

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

[0122] The visualizing at least one SDK provided by the operation party of the block chain in the visualization interface comprises:

[0123] visualizing at least one SDK provided by the operation party of the block chain and corresponding to the target industry in the visualization interface.

[0124] In some embodiments, the apparatus is further configured to:

[0125] visualize a component included in the target SDK in the visualization interface before generating the demonstration device data corresponding to the target Internet of Things device;

[0126] confirm the component included in the target SDK through a visual operation in the visualization interface.

[0127] In some embodiments, the confirming the component included in the target SDK through a visual operation in the visualization interface comprises:

[0128] confirm each target component included in the target SDK through a visual operation in the visualization interface, and visualize description text corresponding to the target component in the visualization interface after the confirmation of the target component is completed.

[0129] In some embodiments, the component included in the SDK comprises a trusted firmware.

[0130] The apparatus is further configured to:

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

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

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

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

[0135] The demonstration device data is divided into a plurality of data blocks in chronological order of generation time;

[0136] The corresponding demonstration block is generated based on each data block in turn, and the demonstration block is visualized in the visualization interface; wherein the demonstration block contains the data block and the hash value of the data block contained in the previous demonstration block.

[0137] In some embodiments, the apparatus is further configured to:

[0138] The data on-chain result corresponding to the demonstration device data is generated and visualized in the visualization interface.

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

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

[0141] For the device embodiment, it basically corresponds to the method embodiment, so for the related part, please refer to the part of the method embodiment. The device embodiments described above are only schematic, and the modules illustrated as separate components may or may not be physically separate, and the components illustrated as modules may or may not be physical modules, i.e. they may be located in one place, or distributed on multiple network modules. According to the actual needs, some or all of the modules can be selected to achieve the purpose of the technical solution of the present application.

[0142] The systems, apparatuses, modules, or components illustrated in the above examples can be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer, and the specific form of the computer can be 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 e-mail device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

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

[0144] The memory can include non-persistent memory in the computer readable medium, such as non-volatile memory, random access memory (RAM), and / or read-only memory (ROM), such as flash RAM, among others. The memory is an example of computer readable media.

[0145] Computer readable media includes permanent and non-permanent, removable and non-removable media implemented in any method or technology for storage of information such as 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 technologies, compact disc read-only memory (CD-ROM), digital versatile discs (DVDs), or other optical storage, magnetic cassettes, magnetic disks storage, quantum memories, graphene-based storage media, or other magnetic storage devices, or any other non-transmission medium that can be used to store information accessible to computing devices. According to the definition herein, computer readable media does not include transitory media, such as modulated data signals and carrier waves.

[0146] It should be noted that the terms "comprising", "including", or any other variant thereof are intended to cover non-exclusive inclusions, so that processes, methods, articles, or devices that include a series of elements not only include those elements, but also include other elements not explicitly listed, or inherent to such processes, methods, articles, or devices. Without more limitations, the element defined by the statement "including a" does not exclude the presence of additional identical elements in the process, method, article, or device that includes the element.

[0147] The foregoing has described specific embodiments of this application. Other embodiments are within the scope of this application. In some cases, the actions or steps described in this application may be performed in a different order than those shown in the embodiments and still achieve the desired results. Furthermore, the processes depicted in the accompanying drawings do not necessarily require a specific or sequential order to achieve the desired results. In some implementations, multitasking and parallel processing are also possible or may be advantageous.

[0148] The terminology used in one or more embodiments of this application is for the purpose of describing particular embodiments only and is not intended to limit the scope of one or more embodiments of this application. The singular forms “a,” “the,” and “the” are also intended to include the plural forms unless the context clearly indicates otherwise. The term “and / or” refers to and includes any or all possible combinations of one or more associated listed items.

[0149] The terms "an embodiment," "some embodiments," "example," "specific example," or "one implementation," as used in one or more embodiments of this application, refer to specific features or characteristics described in connection with that embodiment, which are included in at least one embodiment of this application. Illustrative descriptions of these terms do not necessarily refer to the same embodiment. Furthermore, the described specific features or characteristics may be combined in a suitable manner in one or more embodiments of this application. In addition, different embodiments and specific features or characteristics from different embodiments may be combined without contradiction.

[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 this application, such information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another. For example, without departing from the scope of one or more embodiments of this application, first information may also be referred to as second information, and similarly, second information may also be referred to as first information. Depending on the context, the word "if" as used herein may be interpreted as "when," "when," or "in response to a determination."

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

[0152] The user information (including but not limited to user equipment information, user personal information, etc.) and data (including but not limited to data for analysis, stored data, displayed data, etc.) involved in the present application are information and data authorized by the user or authorized by all parties, and the collection, use and processing of the related data need to comply with the relevant laws, regulations and standards of the country and region, and provide corresponding operation entrances for the user to choose authorization or refusal.

Claims

1. A visualization method for uploading data from IoT devices to the blockchain, applied to a client corresponding to a target IoT device; the method includes: At least one SDK provided by the blockchain operator is visualized in a visual interface; wherein, the SDK encapsulates components for storing IoT device data into the blockchain; Through visual operations in the visual interface, a target SDK corresponding to the target IoT device can be selected from the at least one SDK; Generate demonstration device data corresponding to the target IoT device, and visualize the demonstration device data in real time on the visualization interface; wherein, the demonstration device 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 visualized 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.

2. The method according to claim 1, further comprising: At least one industry corresponding to the SDK provided by the operator will be visualized in the visualization interface; The target industry can be selected from the at least one industry through visual operations in the visual interface. The step of visually presenting at least one SDK provided by the blockchain operator in a visual interface includes: At least one SDK provided by the blockchain operator that corresponds to the target industry will be visualized in the visualization interface.

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

4. The method according to claim 3, wherein confirming the components included in the target SDK through visual operations in the visual interface includes: In the visualization interface, the target components included in the target SDK are confirmed through visualization operations. After the confirmation of the target components is completed, the description text corresponding to the target components is visualized in the visualization interface.

5. The method according to claim 1, wherein the SDK includes trusted firmware as a component; Before generating the demonstration block based on the demonstration device data, the method further includes: Demonstration encrypted data corresponding to the demonstration device data is generated, and the demonstration encrypted data is visualized in the visualization interface; wherein, the demonstration encrypted data is used to represent the encrypted data obtained by encrypting the device data based on the trusted firmware encapsulated in the target SDK; The generation of the demonstration block based on the demonstration device data includes: A demo block is generated based on the demo encrypted data.

6. The method according to claim 1, wherein generating a demonstration block based on the demonstration device data comprises: The demonstration device data is divided into multiple data blocks according to the order in which it was generated; A corresponding demonstration block is generated sequentially based on each data block; wherein the demonstration block contains the data block and the hash value of the data block contained in the previous demonstration block.

7. The method according to claim 1, further comprising: Generate data uplink results corresponding to the data of the demonstration device, and visualize the data uplink results in the visualization interface.

8. The method according to claim 1, wherein the appearance features of the interface visual elements in the visualization interface correspond to the appearance features of the communication hardware.

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

10. A visualization device for uploading data from IoT devices to the blockchain, applied to a client corresponding to a target IoT device; the device includes: The SDK demonstration module visualizes at least one SDK provided by the blockchain operator in a visual interface; wherein, the SDK encapsulates components for storing IoT device data into the blockchain; The SDK selection module allows users to select the target SDK corresponding to the target IoT device from at least one SDK through visual operations in the visualization interface. The acquisition and demonstration module generates demonstration device data corresponding to the target IoT device, and presents the demonstration device data in real time on the visualization interface; wherein, the demonstration device 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 visualizes 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; Memory used to store processor-executable instructions; The processor implements the method as described in any one of claims 1 to 9 by executing the executable instructions.

12. A computer-readable storage medium having stored thereon computer instructions that, when executed by a processor, implement the method as described in any one of claims 1 to 9.

Images