Equipment management method and device based on block chain, electronic equipment and storage medium

Abstract

The embodiment of the invention provides an equipment management method and device based on a block chain, electronic equipment and a storage medium, and relates to the technical field of block chains, and the method comprises the steps: responding to a use request for target shared equipment initiated by a leasing terminal, terminal information of the leasing terminal and first use permission information of the target sharing equipment are obtained through the intelligent contract; authority verification is performed on the leasing terminal according to the first use authority information and the terminal information through the smart contract, and if the verification result is passed, the target shared device is unlocked, so that the authority information of the shared device is configured in the smart contract, the security and credibility of the authority information are ensured, and the user experience is improved in the process of leasing the shared device by the user. Authority verification is carried out based on the terminal information and the authority information, the security and legality of access are ensured, unauthorized use is reduced, the use security of the shared device is ensured, and meanwhile, the real-time performance of device use can be effectively ensured based on the real-time verification process.

Description

Technical Field

[0001] The present invention relates to the field of blockchain technology, and in particular to a device management method based on blockchain, a device management device based on blockchain, an electronic device, and a computer-readable storage medium. Background Art

[0002] With the development of science and technology, shared devices have become a hot topic, and the areas of shared device management include but are not limited to public places, corporate offices, hotels, shopping malls, etc. However, in the process of managing shared devices, there are limitations in security, real-time performance, flexibility, and privacy protection, which makes it impossible to effectively manage shared devices. Summary of the invention

[0003] The embodiments of the present invention provide a device management method, apparatus, electronic device and computer-readable storage medium based on blockchain to solve or partially solve the problems of security, real-time performance and flexibility in the device management process based on blockchain.

[0004] The embodiment of the present invention discloses a device management method based on blockchain, which relates to a blockchain network, wherein a smart contract is deployed on the blockchain network, and permission information corresponding to a shared device is configured in the smart contract. The method includes:

[0005] In response to a use request for a target shared device initiated by a rental terminal, obtaining terminal information of the rental terminal and first use permission information of the target shared device through the smart contract;

[0006] The smart contract performs permission verification on the rental terminal according to the first usage permission information and the terminal information, and if the verification result is passed, the target shared device is unlocked.

[0007] In some feasible implementations, the terminal information includes at least one of a user identifier, a current time point, a geographic location, and a target device type, and the performing permission verification on the rental terminal according to the first usage permission information and the terminal information, and if the verification result is passed, unlocking the target shared device, includes:

[0008] If the user identifier is an identifier registered in the blockchain network, at least one of the current time point, the geographic location, and the target device type is matched with the usage right information to perform permission verification on the rental terminal, and if the verification result is passed, the target shared device is unlocked.

[0009] In some feasible implementations, the first usage permission information includes at least a usage time period, a usage location range, a standard usage frequency, and a usage device type, and matching at least one of the current time point, the geographic location, and the target device type with the usage right information to perform permission verification on the rental terminal, and if the verification result is passed, unlocking the target shared device includes:

[0010] If the rental terminal uses the shared device for the first time within a preset time period, and the current time point is within the usage time period, the geographical location is within the usage location range, and the target device type belongs to the usage device type, then the target shared device is unlocked.

[0011] In some feasible implementations, the first usage permission information further includes a standard usage frequency, and the at least one of the current time point, the geographical location, and the target device type is matched with the usage right information to perform permission verification on the rental terminal, and if the verification result is passed, unlocking the target shared device includes:

[0012] If the rental terminal does not use the shared device for the first time within the preset time period, extracting the actual usage frequency from the terminal information;

[0013] If the actual usage frequency is less than or equal to the standard usage frequency, the current time point is in the usage time period, the geographical location is in the usage location range, and the target device type belongs to the usage device type, then the target shared device is unlocked.

[0014] Some possible implementations also include:

[0015] If the actual usage frequency is greater than the standard usage frequency, and / or the current time point is not within the usage time period, and / or the geographical location is not within the usage location range, and / or the target device type does not belong to the usage device type, a rejection message is sent to the rental terminal, and the rejection message is used to prompt the rental terminal that it does not have the authority to use the target shared device.

[0016] Some possible implementations also include:

[0017] Obtaining a device usage record corresponding to the target shared device;

[0018] The device usage record is broadcast to each node in the blockchain network.

[0019] Some possible implementations also include:

[0020] In response to a permission modification request for the target sharing device, modify the first usage permission information according to the permission modification request to obtain second usage permission information of the target sharing device;

[0021] The second usage permission information is broadcast to each node in the blockchain network.

[0022] Some possible implementations also include:

[0023] Receiving a device registration request for the shared device sent by a management terminal, obtaining a device identification corresponding to the shared device, authenticating the device identification, and generating device authentication information for the shared device;

[0024] When the device identification authentication is successful, receiving permission configuration information for the shared device sent by the management terminal;

[0025] The device authentication information and the permission configuration information are stored on the blockchain network in the form of the smart contract, and the permission configuration information is broadcast to each node of the blockchain network.

[0026] The embodiment of the present invention further discloses a device management apparatus based on blockchain, which relates to a blockchain network, wherein a smart contract is deployed on the blockchain network, and permission information corresponding to a shared device is configured in the smart contract. The device comprises:

[0027] a request receiving module, configured to respond to a use request initiated by a rental terminal for a target shared device, and obtain terminal information of the rental terminal and first use permission information of the target shared device through the smart contract;

[0028] A verification module is used to verify the permission of the rental terminal according to the first usage permission information and the terminal information through the smart contract, and if the verification result is passed, unlock the target shared device.

[0029] In some feasible implementations, the terminal information includes at least one of a user identifier, a current time point, a geographic location, and a target device type, and the verification module is specifically configured to:

[0030] If the user identifier is an identifier registered in the blockchain network, at least one of the current time point, the geographic location, and the target device type is matched with the usage right information to perform permission verification on the rental terminal, and if the verification result is passed, the target shared device is unlocked.

[0031] In some feasible implementations, the first usage permission information includes at least a usage time period, a usage location range, a standard usage frequency, and a usage device type, and the verification module is specifically used to:

[0032] If the rental terminal uses the shared device for the first time within a preset time period, and the current time point is within the usage time period, the geographical location is within the usage location range, and the target device type belongs to the usage device type, then the target shared device is unlocked.

[0033] In some feasible implementations, the first usage permission information further includes a standard usage frequency, and the verification module is specifically configured to:

[0034] If the rental terminal does not use the shared device for the first time within the preset time period, extracting the actual usage frequency from the terminal information;

[0035] If the actual usage frequency is less than or equal to the standard usage frequency, the current time point is in the usage time period, the geographical location is in the usage location range, and the target device type belongs to the usage device type, then the target shared device is unlocked.

[0036] Some possible implementations also include:

[0037] An information sending module is used to send a rejection message to the rental terminal if the actual usage frequency is greater than the standard usage frequency, and / or the current time point is not within the usage time period, and / or the geographical location is not within the usage location range, and / or the target device type does not belong to the usage device type, and the rejection message is used to prompt the rental terminal that it does not have the authority to use the target shared device.

[0038] Some possible implementations also include:

[0039] A record acquisition module, used to acquire the device usage record corresponding to the target shared device;

[0040] The broadcast module is used to broadcast the device usage record to each node in the blockchain network.

[0041] Some possible implementations also include:

[0042] a permission modification module, configured to respond to a permission modification request for the target sharing device, modify the first usage permission information according to the permission modification request, and obtain second usage permission information of the target sharing device;

[0043] A permission broadcasting module is used to broadcast the second usage permission information to each node in the blockchain network.

[0044] Some possible implementations also include:

[0045] A registration module, configured to receive a device registration request for the shared device sent by a management terminal, obtain a device identification corresponding to the shared device, authenticate the device identification, and generate device authentication information for the shared device;

[0046] A permission configuration module, configured to receive permission configuration information for the shared device sent by a management terminal when the device identification authentication is successful;

[0047] The permission storage module is used to store the device authentication information and the permission configuration information on the blockchain network in the form of the smart contract, and broadcast the permission configuration information to each node of the blockchain network.

[0048] The embodiment of the present invention further discloses an electronic device, comprising a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other via the communication bus;

[0049] The memory is used to store computer programs;

[0050] The processor is used to implement the method described in the embodiment of the present invention when executing the program stored in the memory.

[0051] The embodiment of the present invention further discloses a computer-readable storage medium having instructions stored thereon, which, when executed by one or more processors, enables the processors to execute the method described in the embodiment of the present invention.

[0052] The embodiments of the present invention include the following advantages:

[0053] In an embodiment of the present invention, a blockchain network is involved, and a smart contract is deployed on the blockchain network. The smart contract is configured with permission information corresponding to the shared device. The rental terminal can be a terminal for renting the shared device for use. When a user wants to rent a shared device for use, a use request for the target shared device can be initiated through the rental terminal. In response to the use request for the target shared device initiated by the rental terminal, the terminal information of the rental terminal and the first use permission information of the target shared device are obtained through the smart contract. Then, the rental terminal is verified for permission based on the first use permission information and the terminal information. If the verification result is passed, the target shared device is unlocked. By configuring the permission information of the shared device in the smart contract, the security and credibility of the permission information are ensured. In the process of users renting shared devices, permission verification is performed based on the terminal information and permission information, which can ensure the security and legality of access, reduce unauthorized use, and ensure the safety of shared device use. At the same time, based on the real-time verification process, the real-time use of the device can be effectively guaranteed. BRIEF DESCRIPTION OF THE DRAWINGS

[0054] Figure 1 It is a flowchart of a device management method based on blockchain provided in an embodiment of the present invention;

[0055] Figure 2 It is a structural block diagram of a device management device based on blockchain provided in an embodiment of the present invention;

[0056] Figure 3 It is a block diagram of an electronic device provided in an embodiment of the present invention. DETAILED DESCRIPTION

[0057] In order to make the above-mentioned objects, features and advantages of the present invention more obvious and easy to understand, the present invention is further described in detail below with reference to the accompanying drawings and specific embodiments.

[0058] As an example, with the development of sharing technology, more and more shared devices are appearing in people's lives. When users go out, they can rent corresponding shared devices to meet corresponding needs, such as renting shared bicycles, shared power banks, shared WiFi hotspots, etc. Among them, for shared devices, they usually adopt a centralized network permission management method to restrict users, and the centralized permission management method has limitations in terms of security, real-time, flexibility, and privacy protection. The centralized permission management structure is easy to become a target of network attacks. Once the central server is attacked, the security of the network will be threatened. Secondly, the traditional permission management method usually needs to rely on manual intervention, and the permission adjustment is not timely and flexible enough to meet the real-time demand changes in different scenarios. In addition, the user privacy protection under the traditional permission management method is not perfect, and the user's identity information and access records may be exposed on the central server, which poses a risk of information leakage.

[0059] In this regard, in the present invention, the permissions of shared devices are managed based on the blockchain network. A smart contract is deployed on the blockchain network, and the permission information corresponding to the shared device is configured in the smart contract. The rental terminal can be a terminal for renting a shared device for use. When a user wants to rent a shared device for use, a use request for the target shared device can be initiated through the rental terminal. In response to the use request for the target shared device initiated by the rental terminal, the smart contract obtains the terminal information of the rental terminal and the first use permission information of the target shared device, and then performs permission verification on the rental terminal according to the first use permission information and the terminal information. If the verification result is passed, the target shared device is unlocked. By configuring the permission information of the shared device in the smart contract, the security and credibility of the permission information are ensured. In the process of users renting shared devices, permission verification is performed based on the terminal information and permission information, which can ensure the security and legality of access, reduce unauthorized use, and ensure the safety of shared device use. At the same time, based on the real-time verification process, the real-time use of the device can be effectively guaranteed.

[0060] Reference Figure 1 , shows a flowchart of a device management method based on blockchain provided in an embodiment of the present invention, involving a blockchain network, wherein a smart contract is deployed on the blockchain network, and the smart contract is configured with permission information corresponding to a shared device, which may specifically include the following steps:

[0061] Step 101, in response to a use request for a target shared device initiated by a rental terminal, obtaining terminal information of the rental terminal and first use permission information of the target shared device through the smart contract;

[0062] In an embodiment of the present invention, the blockchain network can be a distributed database that records the history of all relevant permission management to ensure the transparency and immutability of the data. The blockchain network can be composed of multiple nodes, and each node has a complete copy of the permission management record, so that the data consistency on all nodes can be guaranteed through the consensus algorithm in the blockchain network.

[0063] It should be noted that by registering the shared device on the blockchain network, the shared device can become a corresponding node on the blockchain network, so as to perform permission management on the shared device based on the blockchain network. Among them, a corresponding smart contract can be deployed on the blockchain network, which can be a computer protocol that automatically executes the terms of the contract. The smart contract can be stored on the blockchain and executed by the nodes of the blockchain network, which can automatically execute preset conditions and rules. Among them, the shared device can include a shared power bank, a shared WiFi hotspot, a shared car, a shared drone, etc., and the present invention does not limit this.

[0064] Smart contracts are deployed on blockchain networks, using the decentralized nature of blockchain to ensure that the execution of contracts is not controlled by a single entity. When the conditions of a smart contract are triggered, the blockchain network will automatically execute the contract code and record the results on the blockchain to ensure that all operations are transparent and unchangeable. The blockchain network provides the infrastructure for the operation of smart contracts, while smart contracts use the characteristics of blockchain to achieve automated and reliable contract execution. Based on the cooperation of the two, the permission management of shared devices can be effectively realized.

[0065] In some feasible implementations, before performing permission management on shared devices, the shared devices can be registered and authenticated on the blockchain network, thereby ensuring the legitimacy of all shared devices on the blockchain network. In an embodiment of the present invention, a communication connection can be established between a shared device and a management terminal first, so that a user can configure the shared device on a blockchain network through the management terminal. Specifically, for a blockchain network, it can obtain a device identification corresponding to the shared device by receiving a device registration request for the shared device sent by the management terminal, authenticate the device identification, and generate device authentication information for the shared device. When the device identification authentication is successful, it receives permission configuration information for the shared device sent by the management terminal, and then stores the device authentication information and the permission configuration information on the blockchain network in the form of a smart contract, and broadcasts the permission configuration information to each node of the blockchain network. Thus, on the one hand, by registering the shared device on the blockchain network, the legitimacy of the shared device on the blockchain network is ensured. On the other hand, after successful registration, the user can configure the permission configuration information for the shared device so that the smart contract can perform permission management on the shared device based on the configured permission configuration information, and by broadcasting the permission configuration information to all nodes on the blockchain network, the security and integrity of the permission record are ensured, and the permission record information is prevented from being tampered with or deleted.

[0066] In one example, assuming that the shared device is a shared WiFi hotspot, the user can register, authenticate, and configure usage permissions for the shared WiFi hotspot on the blockchain network through the management terminal, as follows:

[0067] 1. Device registration:

[0068] For providers of public shared WiFi hotspots, relevant device managers can use the blockchain network to manage shared WiFi hotspots. Each shared WiFi hotspot has a unique device identifier (for example, a MAC address or serial number).

[0069] Management terminal: management platform for shared WiFi hotspot providers.

[0070] Device registration request: The management platform sends a device registration request to the blockchain network, which contains the device identifier of the shared WiFi hotspot.

[0071] 2. Equipment identification authentication:

[0072] After receiving the device registration request, the blockchain network will authenticate the device identification.

[0073] Device identity authentication: The blockchain network verifies whether the device identity is unique and valid.

[0074] Device authentication information: If the device identification authentication is successful, the blockchain network generates a device authentication information, which includes the device identification and authentication status.

[0075] 3. Permission configuration information:

[0076] After the device identification authentication is successful, the management terminal can send permission configuration information.

[0077] Permission configuration information: The management platform sends permission configuration information for the shared WiFi hotspot, such as which users are allowed to connect, usage time, usage frequency, usage frequency, and device type.

[0078] 4. Smart Contract Storage:

[0079] The blockchain network stores device authentication information and permission configuration information in the form of smart contracts.

[0080] Smart Contracts: Smart contracts ensure that this information is tamper-proof and transparent.

[0081] Stored on the blockchain network: Device authentication information and permission configuration information are stored on the distributed ledger of the blockchain network.

[0082] 5. Broadcast to nodes:

[0083] Finally, the blockchain network broadcasts the permission configuration information to each node in the network.

[0084] Broadcast: Ensure that all nodes are synchronized with the latest permission configuration information, thereby ensuring the transparency and security of the system.

[0085] Summary of the specific process: ① Device registration: the management terminal sends a device registration request; ② Device identification authentication: the blockchain network authenticates the device identification; ③ Permission configuration information: the management terminal sends permission configuration information; ④ Smart contract storage: device authentication information and permission configuration information are stored in the smart contract; ⑤ Broadcast to nodes: the permission configuration information is broadcast to all nodes, so that on the one hand, by registering the shared device to the blockchain network, the legitimacy of the shared device on the blockchain network is ensured; on the other hand, after successful registration, the user can configure the permission configuration information for the shared device so that the smart contract can manage the permissions of the shared device based on the configured permission configuration information, and by broadcasting the permission configuration information to all nodes on the blockchain network, the security and integrity of the permission record are ensured to prevent the permission record information from being tampered with or deleted.

[0086] After completing the registration, authentication and permission configuration of the shared device through the above process, in the actual management process, the user can enter the corresponding operation on the rental terminal to unlock the corresponding shared device so as to use the shared device to obtain the corresponding service. Specifically, the rental terminal can initiate a use request for the target shared device, and the blockchain network can respond to the use request for the target shared device initiated by the rental terminal. The smart contract obtains the terminal information of the rental terminal and the first use permission information of the target shared device, so as to determine whether the rental terminal is allowed to use the target shared device based on the terminal information and the first use permission information, thereby ensuring the security and legality of access through the permission verification mechanism to prevent unauthorized use. Among them, the rental terminal can be a terminal device that initiates a use request for the target shared device.

[0087] Step 102: Verify the permission of the rental terminal according to the first usage permission information and the terminal information through the smart contract. If the verification result is passed, unlock the target shared device.

[0088] After determining the terminal information that initiates the use request and the first usage permission information of the target shared device, the smart contract can verify the permission of the rental terminal based on the first usage permission information and the terminal information. If the verification result is passed, the target shared device is unlocked; if the verification result is failed, a rejection message is sent to the rental terminal, and the rejection message is used to prompt the rental terminal that the rental terminal does not have the permission to use the target shared device. Therefore, by configuring the permission information of the shared device in the smart contract, the security and credibility of the permission information are ensured. In the process of users renting shared devices, permission verification is performed based on terminal information and permission information, which can ensure the security and legality of access, reduce unauthorized use, and ensure the safety of shared device use. At the same time, based on the real-time verification process, the real-time use of the device can be effectively guaranteed.

[0089] In some feasible implementations, the terminal information includes at least one of a user identifier, a current time point, a geographic location, and a target device type. The smart contract can match the terminal information with the first usage permission information. If the user identifier is an identifier registered in the blockchain network, at least the current time point, the geographic location, and the target device type are matched with the usage right information to perform permission verification on the rental terminal. If the verification result is passed, the target shared device is unlocked.

[0090] Among them, the first usage permission information includes at least the usage time period, the usage location range, the standard usage frequency and the usage device type. If the rental terminal uses the shared device for the first time within the preset time period, and the current time point is in the usage time period, the geographical location is in the usage location range, and the target device type belongs to the usage device type, the target shared device is unlocked.

[0091] Furthermore, the first usage permission information also includes a standard usage frequency, so the smart contract can also determine whether the rental terminal has the right to use the target shared device based on the usage frequency. If the rental terminal is not using the shared device for the first time within the preset time period, the actual usage frequency is extracted from the terminal information; if the actual usage frequency is less than or equal to the standard usage frequency, and the current time point is in the usage time period, the geographical location is in the usage location range, and the target device type belongs to the usage device type, the target shared device is unlocked.

[0092] In addition, if the actual usage frequency is greater than the standard usage frequency, and / or the current time point is not within the usage time period, and / or the geographical location is not within the usage location range, and / or the target device type does not belong to the usage device type, a rejection message is sent to the rental terminal. The rejection message is used to prompt the rental terminal that it does not have the authority to use the target shared device.

[0093] It should be noted that for each shared device in the blockchain network, the same usage permission information or different usage permission information may correspond to each shared device. For example, assuming that a shared WiFi hotspot corresponds to the same usage permission information, the usage permission information includes usage time period, usage location range, standard usage frequency and usage device type. Among them, the usage time period represents the specific time period in which the shared device is allowed to be used, the usage location range represents the geographical location range in which the shared device is allowed to be used, etc. The standard usage frequency represents the number of times a user is restricted from using the shared device within a certain period of time (such as no more than 3 times a day or a week, etc.), and the usage device type represents the type of device that can use the shared device, etc., so that by configuring the permission information for the shared device on the smart contract, on the one hand, the smart contract can automatically execute the pre-set rules according to the set execution conditions, and automatically authorize the unlocking of the rental device usage permission or refuse the authorization to use the specified device when the conditions are met, and lock it. On the other hand, the corresponding verification mechanism ensures the security and legality of device access to prevent unauthorized use.

[0094] In some examples, assuming that the shared device is a shared WiFi hotspot, the management process of the shared WiFi hotspot may be as follows:

[0095] 1. The user ID matches the first usage permission information:

[0096] Assume that rental terminal A wants to connect to a shared WiFi hotspot. The device identity of rental terminal A has been registered in the blockchain network.

[0097] User ID: the device ID of the rental terminal A (for example, the MAC (Media Access Control) address of the mobile phone).

[0098] First, usage permission information: including usage time period, usage location range, standard usage frequency, and usage device type, etc.

[0099] 2. Permission verification:

[0100] The smart contract matches the terminal information of the rental terminal A with the first usage permission information.

[0101] Current time: Assume that the current time is 10:00 AM.

[0102] Location: Rental Terminal A is located in a cafe in the city center.

[0103] Target device type: The device at rental terminal A is a smartphone.

[0104] 3. Usage Permission Information:

[0105] Available time: 9am to 6pm.

[0106] Scope of use: city center area.

[0107] Standard usage frequency: no more than 5 connections per hour.

[0108] Device type: Smartphone.

[0109] 4. Verification process:

[0110] Time matching: The current time is 10:00 AM, which is within the usage time period (9:00 AM to 6:00 PM).

[0111] Location matching: Rental terminal A is located in the city center area and within the usage location range.

[0112] Device type matching: The device of rental terminal A is a smart phone, which belongs to the usage device type.

[0113] Usage frequency matching: Assuming that rental terminal A uses the shared device for the first time within a preset time period (for example, within the past 1 hour), the actual usage frequency is 1 time, which is less than or equal to the standard usage frequency (5 times).

[0114] 5. Unlock the target shared device:

[0115] Since all conditions are met, the smart contract verification result is passed, so the target shared device (i.e., shared WiFi hotspot) is unlocked and rental terminal A is allowed to connect.

[0116] 6. Rejection Information:

[0117] Suppose that rental terminal B wants to connect to the same shared WiFi hotspot at the same time, but the device identifier of rental terminal B is not registered in the blockchain network, or the actual usage frequency of rental terminal B exceeds the standard usage frequency, or rental terminal B is located outside the range of the usage location, or the device type of rental terminal B does not belong to the usage device type.

[0118] Rejection information: The smart contract sends a rejection message to the rental terminal of rental terminal B, prompting that rental terminal B does not have the authority to use the target shared device.

[0119] Summary of the specific process: ① User ID matching: verify whether the user ID is registered in the blockchain network; ② Permission verification: match the current time point, geographic location, target device type and usage permission information; ③ Usage frequency verification: check whether the actual usage frequency is less than or equal to the standard usage frequency; ④ Unlock device: if all conditions are met, unlock the target shared device; ⑤ Rejection message: if any condition is not met, send a rejection message.

[0120] Through the above process, by configuring the permission information of the shared device in the smart contract, the security and credibility of the permission information are ensured. In the process of users renting shared devices, permission verification is performed based on terminal information and permission information, which can ensure the security and legality of access, reduce unauthorized use, and ensure the safety of shared equipment. At the same time, based on the real-time verification process, the real-time use of the equipment can be effectively guaranteed.

[0121] In addition, in the above process, after the shared device is used, its own device usage record can be broadcast to all nodes in the blockchain. Specifically, the device usage record corresponding to the target shared device can be obtained, and then the device usage record can be broadcast to each node in the blockchain network, ensuring the security and integrity of the usage record and preventing the permission record from being tampered with or deleted.

[0122] In some feasible implementations, for shared devices, the permission information can also be modified so as to flexibly adjust the permissions of the shared devices according to actual needs, and then the updated permission information is written into the blockchain to ensure the traceability and non-tamperability of the permission operation. The permission information can be modified through the management terminal. Specifically, the shared device can respond to the permission modification request for the target shared device, modify the first use permission information according to the permission modification request, obtain the second use permission information of the target shared device, and then broadcast the second use permission information to each node in the blockchain network.

[0123] For example, the increase in permission types includes but is not limited to the following examples:

[0124] For the extension of usage time:

[0125] Originally, users could only use the device from 9:00 to 17:00 every day, but now users are allowed to use it from 8:00 to 18:00 every day. Specifically, the time range in the smart contract can be updated to expand the time period allowed for use. The usage time can also be expanded by increasing the number of days of use. Specifically, originally users could only use the device on weekdays, but now users are allowed to use it on weekends. Accordingly, the date range in the smart contract is updated to increase the number of days allowed for use.

[0126] For extended geolocation range:

[0127] Originally, users could only use the device in a certain city, but now users are allowed to use it across the entire country. Specifically, the geographical scope of permitted use can be expanded by updating the geographical location conditions in the smart contract.

[0128] Adjustment of usage frequency:

[0129] Originally, users could only use the device once a day, but now they are allowed to use the device three times a day. Specifically, the frequency of allowed use can be increased by updating the usage limit in the smart contract.

[0130] For adjustments to increase bandwidth:

[0131] Originally, users could only use 1Mbps of bandwidth, but now they are allowed to use 5Mbps of bandwidth. Specifically, the bandwidth allowed can be increased by updating the bandwidth limit in the smart contract.

[0132] Through the above process, the permission information of the shared device can be adjusted to increase or decrease the usage permissions of the shared device, and the adjustment of the permission information can include unified adjustment of all shared devices, adjustment of specific shared devices, adjustment for specific user terminals, etc., and the present invention is not limited to this.

[0133] It should be noted that the embodiments of the present invention include but are not limited to the above examples. It is understandable that those skilled in the art can also make settings according to actual needs under the guidance of the ideas of the embodiments of the present invention, and the present invention is not limited to this.

[0134] In an embodiment of the present invention, a blockchain network is involved, and a smart contract is deployed on the blockchain network. The smart contract is configured with permission information corresponding to the shared device. The rental terminal can be a terminal for renting the shared device for use. When a user wants to rent a shared device for use, a use request for the target shared device can be initiated through the rental terminal. The smart contract can respond to the use request for the target shared device initiated by the rental terminal. The smart contract obtains the terminal information of the rental terminal and the first use permission information of the target shared device, and then performs permission verification on the rental terminal according to the first use permission information and the terminal information. If the verification result is passed, the target shared device is unlocked. By configuring the permission information of the shared device in the smart contract, the security and credibility of the permission information are ensured. In the process of users renting shared devices, permission verification is performed based on the terminal information and permission information, which can ensure the security and legality of access, reduce unauthorized use, and ensure the safety of shared device use. At the same time, based on the real-time verification process, the real-time use of the device can be effectively guaranteed.

[0135] In order to enable those skilled in the art to better understand the technical solutions in the embodiments of the present invention, the following examples are used for exemplary description:

[0136] 1. Device registration:

[0137] First, a blockchain network is established. A decentralized network is established using blockchain technology. All Wi-Fi rental devices are registered on the blockchain network. Each sub-device has a unique ID. When a sub-device is added to the network, the device identity is authenticated using a digital identity authentication method based on the blockchain network. Device registration is the starting point of the system, ensuring the identity of all devices and the legitimacy of participating in the network.

[0138] 2. Permission release:

[0139] The device owner can publish permission information through the blockchain network to define who can use the leased device, when to use it, and the validity period of use. The permission information will be stored on the blockchain in the form of a smart contract, ensuring the security and credibility of the permission information. The smart contract can execute pre-set rules according to the requirements of the device owner, and automatically authorize the unlocking of the leased device usage permission or deny the use authorization of the specified device and lock it when the conditions are met.

[0140] 3. Permission verification:

[0141] When a user requests to use a rental device, the request will be verified through the blockchain network. The verification process is based on smart contracts, which will determine whether the user has the right to use the device based on the permission information stored on the blockchain. If the request meets the permission requirements, the smart contract will automatically authorize the device to be unlocked; otherwise, the device will be locked and the user cannot use it. This permission verification mechanism ensures the security and legitimacy of access and prevents unauthorized use.

[0142] 4. Permission update:

[0143] The device owner can update the permission information at any time through the blockchain network to achieve dynamic management of the use rights of the leased device. For example, the device owner can increase or decrease the device use rights of a specific user, adjust the access time or number of accesses, etc. The updated permission information will be written to the blockchain, ensuring the traceability and non-tamperability of the permission operation.

[0144] 5. Permission record:

[0145] All permission operations will be recorded on the blockchain, forming a growing permission record chain. These permission records include device registration information, permission release information, permission verification information, and permission update information. The distributed accounting mechanism of the blockchain ensures the security and integrity of permission records and prevents permission records from being tampered with or deleted.

[0146] It should be noted that, for the sake of simplicity, the method embodiments are described as a series of action combinations, but those skilled in the art should be aware that the embodiments of the present invention are not limited by the order of the actions described, because according to the embodiments of the present invention, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all preferred embodiments, and the actions involved are not necessarily required by the embodiments of the present invention.

[0147] Reference Figure 2, shows a structural block diagram of a device management device based on blockchain provided in an embodiment of the present invention, involving a blockchain network, on which a smart contract is deployed, and the smart contract is configured with permission information corresponding to a shared device, which may specifically include the following modules:

[0148] The request receiving module 201 is used to respond to the use request for the target shared device initiated by the rental terminal, and obtain the terminal information of the rental terminal and the first use permission information of the target shared device through the smart contract;

[0149] The verification module 202 is used to verify the permission of the rental terminal according to the first usage permission information and the terminal information through the smart contract, and if the verification result is passed, unlock the target shared device.

[0150] In some feasible implementations, the terminal information includes at least one of a user identifier, a current time point, a geographic location, and a target device type, and the verification module 202 is specifically configured to:

[0151] If the user identifier is an identifier registered in the blockchain network, at least one of the current time point, the geographic location, and the target device type is matched with the usage right information to perform permission verification on the rental terminal, and if the verification result is passed, the target shared device is unlocked.

[0152] In some feasible implementations, the first usage permission information at least includes a usage time period, a usage location range, a standard usage frequency, and a usage device type, and the verification module 202 is specifically used to:

[0153] If the rental terminal uses the shared device for the first time within a preset time period, and the current time point is within the usage time period, the geographical location is within the usage location range, and the target device type belongs to the usage device type, then the target shared device is unlocked.

[0154] In some feasible implementations, the first usage permission information further includes a standard usage frequency, and the verification module 202 is specifically configured to:

[0155] If the rental terminal does not use the shared device for the first time within the preset time period, extracting the actual usage frequency from the terminal information;

[0156] If the actual usage frequency is less than or equal to the standard usage frequency, the current time point is in the usage time period, the geographical location is in the usage location range, and the target device type belongs to the usage device type, then the target shared device is unlocked.

[0157] Some possible implementations also include:

[0158] An information sending module is used to send a rejection message to the rental terminal if the actual usage frequency is greater than the standard usage frequency, and / or the current time point is not within the usage time period, and / or the geographical location is not within the usage location range, and / or the target device type does not belong to the usage device type, and the rejection message is used to prompt the rental terminal that it does not have the authority to use the target shared device.

[0159] Some possible implementations also include:

[0160] A record acquisition module, used to acquire the device usage record corresponding to the target shared device;

[0161] The broadcast module is used to broadcast the device usage record to each node in the blockchain network.

[0162] Some possible implementations also include:

[0163] a permission modification module, configured to respond to a permission modification request for the target sharing device, modify the first usage permission information according to the permission modification request, and obtain second usage permission information of the target sharing device;

[0164] A permission broadcasting module is used to broadcast the second usage permission information to each node in the blockchain network.

[0165] Some possible implementations also include:

[0166] A registration module, configured to receive a device registration request for the shared device sent by a management terminal, obtain a device identification corresponding to the shared device, authenticate the device identification, and generate device authentication information for the shared device;

[0167] A permission configuration module, configured to receive permission configuration information for the shared device sent by a management terminal when the device identification authentication is successful;

[0168] The permission storage module is used to store the device authentication information and the permission configuration information on the blockchain network in the form of the smart contract, and broadcast the permission configuration information to each node of the blockchain network.

[0169] As for the device embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0170] In addition, an embodiment of the present invention further provides an electronic device, including: a processor, a memory, and a computer program stored in the memory and executable on the processor. When the computer program is executed by the processor, each process of the above-mentioned blockchain-based device management method embodiment is implemented, and the same technical effect can be achieved. To avoid repetition, it will not be described here.

[0171] The embodiment of the present invention also provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, each process of the device management method embodiment based on blockchain is implemented, and the same technical effect can be achieved. To avoid repetition, it is not repeated here. The computer-readable storage medium is, for example, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0172] Figure 3 A schematic diagram of the hardware structure of an electronic device for implementing various embodiments of the present invention.

[0173] The electronic device 300 includes but is not limited to: a radio frequency unit 301, a network module 302, an audio output unit 303, an input unit 304, a sensor 305, a display unit 306, a user input unit 307, an interface unit 308, a memory 309, a processor 310, and a power supply 311. Those skilled in the art will appreciate that the electronic device structure involved in the embodiments of the present invention does not constitute a limitation on the electronic device, and the electronic device may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently. In the embodiments of the present invention, the electronic device includes but is not limited to a mobile phone, a tablet computer, a laptop computer, a PDA, a vehicle-mounted terminal, a wearable device, and a pedometer.

[0174] It should be understood that in the embodiment of the present invention, the radio frequency unit 301 can be used for receiving and sending signals during information transmission or communication. Specifically, after receiving downlink data from the base station, it is sent to the processor 310 for processing; in addition, uplink data is sent to the base station. Generally, the radio frequency unit 301 includes but is not limited to an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, etc. In addition, the radio frequency unit 301 can also communicate with the network and other devices through a wireless communication system.

[0175] The electronic device provides users with wireless broadband Internet access through the network module 302, such as helping users to send and receive emails, browse web pages, and access streaming media.

[0176] The audio output unit 303 can convert the audio data received by the RF unit 301 or the network module 302 or stored in the memory 309 into an audio signal and output it as sound. Moreover, the audio output unit 303 can also provide audio output related to a specific function performed by the electronic device 300 (for example, a call signal reception sound, a message reception sound, etc.). The audio output unit 303 includes a speaker, a buzzer, a receiver, etc.

[0177] The input unit 304 is used to receive audio or video signals. The input unit 304 may include a graphics processor (GPU) 3041 and a microphone 3042, and the graphics processor 3041 processes the image data of a static picture or video obtained by an image capture device (such as a camera) in a video capture mode or an image capture mode. The processed image frame can be displayed on the display unit 306. The image frame processed by the graphics processor 3041 can be stored in the memory 309 (or other storage medium) or sent via the radio frequency unit 301 or the network module 302. The microphone 3042 can receive sound and can process such sound into audio data. The processed audio data can be converted into a format output that can be sent to a mobile communication base station via the radio frequency unit 301 in the case of a telephone call mode.

[0178] The electronic device 300 also includes at least one sensor 305, such as a light sensor, a motion sensor, and other sensors. Specifically, the light sensor includes an ambient light sensor and a proximity sensor, wherein the ambient light sensor can adjust the brightness of the display panel 3061 according to the brightness of the ambient light, and the proximity sensor can turn off the display panel 3061 and / or the backlight when the electronic device 300 is moved to the ear. As a type of motion sensor, the accelerometer sensor can detect the magnitude of acceleration in each direction (generally three axes), and can detect the magnitude and direction of gravity when stationary, which can be used to identify the posture of the electronic device (such as horizontal and vertical screen switching, related games, magnetometer posture calibration), vibration recognition related functions (such as pedometer, tapping), etc.; the sensor 305 can also include a fingerprint sensor, a pressure sensor, an iris sensor, a molecular sensor, a gyroscope, a barometer, a hygrometer, a thermometer, an infrared sensor, etc., which will not be repeated here.

[0179] The display unit 306 is used to display information input by the user or information provided to the user. The display unit 306 may include a display panel 3061, which may be configured in the form of a liquid crystal display (LCD), an organic light-emitting diode (OLED), or the like.

[0180] The user input unit 307 can be used to receive input digital or character information, and to generate key signal input related to user settings and function control of the electronic device. Specifically, the user input unit 307 includes a touch panel 3071 and other input devices 3072. The touch panel 3071, also known as a touch screen, can collect the user's touch operation on or near it (such as the user's operation on the touch panel 3071 or near the touch panel 3071 using any suitable object or accessory such as a finger, stylus, etc.). The touch panel 3071 may include two parts: a touch detection device and a touch controller. Among them, the touch detection device detects the user's touch orientation, detects the signal brought by the touch operation, and transmits the signal to the touch controller; the touch controller receives the touch information from the touch detection device, converts it into the contact point coordinates, and then sends it to the processor 310, receives the command sent by the processor 310 and executes it. In addition, the touch panel 3071 can be implemented using multiple types such as resistive, capacitive, infrared and surface acoustic waves. In addition to the touch panel 3071, the user input unit 307 may also include other input devices 3072. Specifically, other input devices 3072 may include but are not limited to a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which are not described in detail here.

[0181] Further, the touch panel 3071 may be covered on the display panel 3061. When the touch panel 3071 detects a touch operation on or near it, it is transmitted to the processor 310 to determine the type of the touch event, and then the processor 310 provides a corresponding visual output on the display panel 3061 according to the type of the touch event. It can be understood that in one embodiment, the touch panel 3071 and the display panel 3061 are used as two independent components to implement the input and output functions of the electronic device, but in some embodiments, the touch panel 3071 and the display panel 3061 can be integrated to implement the input and output functions of the electronic device, which is not limited here.

[0182] The interface unit 308 is an interface for connecting an external device to the electronic device 300. For example, the external device may include a wired or wireless headset port, an external power supply (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting a device with an identification module, an audio input / output (I / O) port, a video I / O port, a headphone port, etc. The interface unit 308 may be used to receive input (e.g., data information, power, etc.) from an external device and transmit the received input to one or more elements within the electronic device 300 or may be used to transmit data between the electronic device 300 and an external device.

[0183] The memory 309 can be used to store software programs and various data. The memory 309 can mainly include a program storage area and a data storage area, wherein the program storage area can store an operating system, at least one application required for a function (such as a sound playback function, an image playback function, etc.), etc.; the data storage area can store data created according to the use of the mobile phone (such as audio data, a phone book, etc.), etc. In addition, the memory 309 can include a high-speed random access memory, and can also include a non-volatile memory, such as at least one disk storage device, a flash memory device, or other volatile solid-state storage devices.

[0184] The processor 310 is the control center of the electronic device. It uses various interfaces and lines to connect various parts of the entire electronic device. By running or executing software programs and / or modules stored in the memory 309 and calling data stored in the memory 309, it performs various functions of the electronic device and processes data, thereby monitoring the electronic device as a whole. The processor 310 may include one or more processing units; preferably, the processor 310 may integrate an application processor and a modem processor, wherein the application processor mainly processes the operating system, user interface, and application programs, and the modem processor mainly processes wireless communications. It is understandable that the above-mentioned modem processor may not be integrated into the processor 310.

[0185] The electronic device 300 may also include a power supply 311 (such as a battery) for supplying power to each component. Preferably, the power supply 311 may be logically connected to the processor 310 through a power management system, thereby implementing functions such as charging, discharging, and power consumption management through the power management system.

[0186] In addition, the electronic device 300 includes some functional modules not shown, which will not be described in detail here.

[0187] It should be noted that, in this article, the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, an element defined by the sentence "comprises a ..." does not exclude the existence of other identical elements in the process, method, article or device including the element.

[0188] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present invention, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, a magnetic disk, or an optical disk), and includes a number of instructions for enabling a terminal (which can be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to execute the methods described in each embodiment of the present invention.

[0189] The embodiments of the present invention are described above in conjunction with the accompanying drawings, but the present invention is not limited to the above-mentioned specific implementation modes, which are merely illustrative rather than restrictive. Under the guidance of the present invention, ordinary technicians in this field can also make many forms without departing from the scope of protection of the present invention and the claims, all of which are within the protection of the present invention.

[0190] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed in the embodiments of the present invention can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the present invention.

[0191] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0192] In the embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0193] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0194] In addition, each functional unit in each embodiment of the present invention may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0195] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, or the part that contributes to the prior art, or the part of the technical solution, can be embodied in the form of a software product. The computer software product is stored in a storage medium, including several instructions for a computer device (which can be a personal computer, server, or network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present invention. The aforementioned storage medium includes: various media that can store program codes, such as USB flash drives, mobile hard disks, ROM, RAM, magnetic disks, or optical disks.

[0196] The above is only a specific embodiment of the present invention, but the protection scope of the present invention is not limited thereto. Any person skilled in the art can easily think of changes or substitutions within the technical scope disclosed by the present invention, which should be included in the protection scope of the present invention. Therefore, the protection scope of the present invention should be based on the protection scope of the claims.

Claims

1. A device management method based on blockchain, characterized in that: A blockchain network is involved, wherein a smart contract is deployed on the blockchain network, and permission information corresponding to a shared device is configured in the smart contract. The method includes: In response to a use request for a target shared device initiated by a rental terminal, obtaining terminal information of the rental terminal and first use permission information of the target shared device through the smart contract; The smart contract performs permission verification on the rental terminal according to the first usage permission information and the terminal information, and if the verification result is passed, the target shared device is unlocked.

2. The method according to claim 1, characterized in that The terminal information includes at least one of a user identifier, a current time point, a geographic location, and a target device type, and the performing permission verification on the rental terminal according to the first usage permission information and the terminal information, and if the verification result is passed, unlocking the target shared device, includes: If the user identifier is an identifier registered in the blockchain network, at least one of the current time point, the geographic location, and the target device type is matched with the usage right information to perform permission verification on the rental terminal, and if the verification result is passed, the target shared device is unlocked.

3. The method according to claim 2, characterized in that The first usage permission information at least includes a usage time period, a usage location range, a standard usage frequency, and a usage device type, and matching at least one of the current time point, the geographic location, and the target device type with the usage right information to perform permission verification on the rental terminal, and if the verification result is passed, unlocking the target shared device includes: If the rental terminal uses the shared device for the first time within a preset time period, and the current time point is within the usage time period, the geographical location is within the usage location range, and the target device type belongs to the usage device type, then the target shared device is unlocked.

4. The method according to claim 3, characterized in that The first usage permission information also includes a standard usage frequency, and the at least one of the current time point, the geographical location, and the target device type is matched with the usage right information to perform permission verification on the rental terminal, and if the verification result is passed, the target shared device is unlocked, including: If the rental terminal does not use the shared device for the first time within the preset time period, extracting the actual usage frequency from the terminal information; If the actual usage frequency is less than or equal to the standard usage frequency, the current time point is in the usage time period, the geographical location is in the usage location range, and the target device type belongs to the usage device type, then the target shared device is unlocked.

5. The method according to claim 4, characterized in that Also includes: If the actual usage frequency is greater than the standard usage frequency, and / or the current time point is not within the usage time period, and / or the geographical location is not within the usage location range, and / or the target device type does not belong to the usage device type, a rejection message is sent to the rental terminal, and the rejection message is used to prompt the rental terminal that it does not have the authority to use the target shared device.

6. The method according to any one of claims 1 to 5, characterized in that: Also includes: Obtaining a device usage record corresponding to the target shared device; The device usage record is broadcast to each node in the blockchain network.

7. The method according to any one of claims 1 to 5, characterized in that: Also includes: In response to a permission modification request for the target sharing device, modify the first usage permission information according to the permission modification request to obtain second usage permission information of the target sharing device; The second usage permission information is broadcast to each node in the blockchain network.

8. The method according to any one of claims 1 to 5, characterized in that: Also includes: Receiving a device registration request for the shared device sent by a management terminal, obtaining a device identification corresponding to the shared device, authenticating the device identification, and generating device authentication information for the shared device; When the device identification authentication is successful, receiving permission configuration information for the shared device sent by the management terminal; The device authentication information and the permission configuration information are stored on the blockchain network in the form of the smart contract, and the permission configuration information is broadcast to each node of the blockchain network.

9. A device management device based on blockchain, characterized in that: A blockchain network is involved, wherein a smart contract is deployed on the blockchain network, and permission information corresponding to a shared device is configured in the smart contract. The device includes: a request receiving module, configured to respond to a use request initiated by a rental terminal for a target shared device, and obtain terminal information of the rental terminal and first use permission information of the target shared device through the smart contract; A verification module is used to verify the permission of the rental terminal according to the first usage permission information and the terminal information through the smart contract, and if the verification result is passed, unlock the target shared device.

10. An electronic device, characterized in that: It includes a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory communicate with each other through the communication bus; The memory is used to store computer programs; The processor is used to implement the method according to any one of claims 1 to 8 when executing the program stored in the memory.

11. A computer-readable storage medium having instructions stored thereon, which, when executed by one or more processors, cause the processors to perform the method according to any one of claims 1 to 8.

Images