Iot device management method and device in metaverse, computer device and storage medium

By managing IoT devices in the metaverse through a global device management server and dividing the virtual device tree, the issues of privacy data isolation and access control between different entities are resolved, and clear management of device operation and data transmission is achieved.

CN116032967BActive Publication Date: 2025-11-04E SURFING IOT CO LTD
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202211732442.6
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2022-12-30
Publication Date
2025-11-04
Estimated Expiration
2042-12-30

AI Technical Summary

Technical Problem

In the metaverse, the question arises of how to isolate and control the privacy data of IoT devices across different entities.

Method used

The system is initialized using a global device management server, which connects to physical IoT devices, divides atomic operations and scene sets, creates virtual devices, and manages permissions and data transfer through a virtual device tree to ensure that each data subject corresponds to a specific virtual device and records the authorization process.

Benefits of technology

It enables clear permission management and data transfer tracking for IoT devices in a metaverse environment, ensuring the isolation and security of privacy data across different entities.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN116032967B_ABST
    Figure CN116032967B_ABST
Patent Text Reader

Abstract

The application relates to an Internet of Things device management method and device in a meta universe, computer equipment and a storage medium, the method comprising: initialization of a global device management server; the global device management server accesses a physical Internet of Things device; a virtual subject in a meta universe environment initiates a device creation request; the global device management server completes virtual device creation; the virtual subject in the meta universe environment interacts with the device; and the global device management server manages the device. The application uses virtual devices to manage physical devices, divides permissions to data subjects, that is, manages in a manner that each data subject corresponds to a specific virtual device, records the authorization process of the device among different data subjects in a virtual device manner, and clearly expresses the operation and data transmission of the device in the virtual device tree, so that the whole process can be tracked.
Need to check novelty before this filing date? Find Prior Art

Description

TECHNICAL FIELD

[0001] The present application relates to the technical field of Internet of Things device management, in particular to an Internet of Things device management method and device in a meta universe, a computer device and a storage medium. BACKGROUND

[0002] The concept of meta universe further expands the digital space. When Internet of Things devices appear in the meta universe, the devices are no longer limited to a certain isolated scene and a single subject. During use, the Internet of Things devices collect some private data of users, such as photos and fingerprints of the users, and thus the situation that a single device aggregates private data of multiple different subjects occurs.

[0003] In the application of Internet of Things devices in the meta universe, the problems of mutual isolation of private data between different subjects and corresponding permission control need to be solved. SUMMARY

[0004] The present application aims to overcome the deficiencies of the prior art and provide an Internet of Things device management method and device in a meta universe, a computer device and a storage medium.

[0005] To solve the above technical problems, the present application adopts the following technical solutions:

[0006] In a first aspect, the present application provides an Internet of Things device management method in a meta universe, comprising the following steps:

[0007] Initialization of a global device management server;

[0008] Access of the global device management server to physical Internet of Things devices;

[0009] Initiation of a device creation request by a virtual subject in a meta universe environment;

[0010] Completion of virtual device creation by the global device management server;

[0011] Interaction of the virtual subject in the meta universe environment with the device;

[0012] Device management by the global device management server.

[0013] Further technical solutions are as follows: In the initialization step of the global device management server, the server is deployed, network connection with the Internet of Things devices is performed, necessary device interaction authentication parameters are set, and the unique identifier, model information, region and owner information of the Internet of Things devices are recorded.

[0014] Further technical solutions are as follows: in the step of accessing the physical Internet of Things device by the global device management server, firstly, for a specific Internet of Things device model, atomic operation division is completed to form an operation set, then the atomic operations in the operation set are arranged and combined to form a scene set, subsequently, according to the scene set, user data specification definition and virtual device metadata definition are set to form a virtual device description file, the global device management server creates a virtual device for the accessed physical device, the virtual device contains all the scene set and initial user data, and is used as a root node of a subsequent virtual device tree, and the initial user is a device administrator.

[0015] Further technical solutions are as follows: in the step of initiating a device creation request by the virtual subject in the meta universe environment, the virtual subject in the meta universe system obtains a request description interface for creating a virtual device through a business scene in the meta universe, including a place and a person, first obtains a device unique identifier, a device scene set and a virtual device description file from the request interface, encapsulates subject data handle, creates virtual device metadata according to the virtual device description file, selects a subset of the device scene set according to a required function, requests a signature of an authorized subject, encapsulates the above information into a request, sends the request to an authorized subject, the authorized subject adds a personal signature to the virtual device metadata, and sends the request to the global device management server to request virtual device creation.

[0016] Further technical solutions are as follows: in the step of completing virtual device creation by the global device management server, the global device management server receives a virtual device creation request, first verifies the virtual device unique identifier in the request and the signature of the authorized subject to ensure the legality of the request, and then verifies the matching of the operation set and the data set in the request to ensure that the operation and data function can be executed on the device, after verification succeeds, uses deep traversal to locate a virtual device of the authorized subject in a virtual device tree, adds a leaf node virtual device under the virtual device, the leaf node contains the device operation set in the request, virtual device metadata, a personal subject and signature information of an authorization process, and the device ownership belongs to the subject requesting the virtual device.

[0017] Further technical solutions are as follows: in the step of interacting between the virtual subject in the meta universe environment and the device, the owner of the virtual device in the meta universe initiates interaction on the virtual device, sends a request to the global device management server, the request parameters include a virtual device unique identifier and an atomic operation identifier, the global device service obtains the request, retrieves user data transmitted through a handle in advance according to the virtual device unique identifier, executes related operations on the physical device, and feeds back the operation result of the physical device to the virtual subject requesting the device interaction.

[0018] Further technical solutions are that in the device management step of the global device management server, the global device management server periodically performs deep traversal on the virtual device tree, searches each virtual device node, checks the metadata of the virtual device, ensures the validity period and signature consistency of the virtual device, marks the state of the invalid node and all subsequent child nodes as unusable when inconsistency occurs, and when the device metadata in the virtual device node changes, first performs deep traversal on all subordinate nodes of the node, transmits the changed user data to each subordinate node, and changes the metadata of each terminal node.

[0019] In a second aspect, the embodiment provides an Internet of Things device management apparatus in a meta universe, including an initialization unit, an access unit, an initiation unit, a completion unit, an interaction unit and a management unit.

[0020] The initialization unit is configured to initialize the global device management server.

[0021] The access unit is configured to access the physical Internet of Things device by the global device management server.

[0022] The initiation unit is configured to initiate a device creation request by a virtual subject in the meta universe environment.

[0023] The completion unit is configured to complete the virtual device creation by the global device management server.

[0024] The interaction unit is configured to interact with the device by the virtual subject in the meta universe environment.

[0025] The management unit is configured to manage the device by the global device management server.

[0026] In a third aspect, the embodiment provides a computer device, including a memory and a processor, the memory stores a computer program, and the processor implements the Internet of Things device management method in the meta universe when executing the computer program.

[0027] In a fourth aspect, the embodiment provides a storage medium, which stores a computer program, the computer program includes program instructions, and the program instructions can implement the Internet of Things device management method in the meta universe when executed by a processor.

[0028] Compared with the prior art, the beneficial effects of the present application are that the virtual device is used to manage the physical device, the permission is divided to the data subject, that is, each data subject corresponds to a specific virtual device for management, the authorization process of the device between different data subjects is recorded in the form of the virtual device, and the operation and data transmission of the device are clearly expressed in the virtual device tree, and the whole process can be tracked.

[0029] The application will be further described below in conjunction with the accompanying drawings and specific embodiments. BRIEF DESCRIPTION OF DRAWINGS

[0030] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the embodiments or prior art description will be briefly introduced below. Obviously, the drawings in the following description are only some embodiments of the present application, and other drawings can be obtained by those skilled in the art without creative labor.

[0031] Figure 1 A flowchart of the method for managing Internet of Things devices in the meta universe provided by the embodiments of the present application is shown in the figure.

[0032] Figure 2 A schematic diagram of the creation process of a virtual device provided by the embodiments of the present application is shown in the figure.

[0033] Figure 3 A schematic diagram of the data structure of a virtual device provided by the embodiments of the present application is shown in the figure.

[0034] Figure 4 A schematic diagram of a virtual device management tree provided by the embodiments of the present application is shown in the figure.

[0035] Figure 5 A schematic block diagram of the device for managing Internet of Things devices in the meta universe provided by the embodiments of the present application is shown in the figure.

[0036] Figure 6 A schematic block diagram of the computer device provided by the embodiments of the present application is shown in the figure. DETAILED DESCRIPTION

[0037] The technical solutions in the embodiments of the present application will be described clearly and completely below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only some embodiments of the present application, not all embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative labor are within the scope of protection of the present application.

[0038] It should be understood that when used in the present specification and the appended claims, the terms "comprise" and "include" indicate the presence of the described features, integers, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and / or groups thereof.

[0039] It is also to be understood that the terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting. As used in this specification and the appended claims, the singular forms "a," "an" and "the" include plural referents unless the context clearly dictates otherwise.

[0040] It is further to be understood that the term "and / or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items, and that the term "at least one of' encompasses one or more items.

[0041] Referring now to the specific embodiments shown in the drawings, the present application discloses a method for managing Internet of Things devices in a meta-universe, comprising the following steps: Figure 1

[0042] S1, initialization of the global device management server;

[0043] In an embodiment, in the initialization step of the global device management server, the server is deployed, network connection with the Internet of Things devices is established, necessary device interaction authentication parameters are set, and the unique identifier, model information, region, and owner information of the Internet of Things devices are recorded.

[0044] S2, the global device management server accesses the physical Internet of Things devices;

[0045] In an embodiment, in the step of the global device management server accessing the physical Internet of Things devices, first, for a specific Internet of Things device model, the division of atomic operations is completed, forming an operation set, then the atomic operations in the operation set are arranged and combined to form a scene set, subsequently, according to the scene set, the user data specification definition and the virtual device metadata definition are set, forming a virtual device description file, the global device management server creates a virtual device for the accessed physical device, the virtual device contains all the scene set and initial user data, which is used as the root node of the subsequent virtual device tree, and the initial user is the device administrator.

[0046] Specifically, the definition and creation of the virtual device:

[0047] For a specific Internet of Things physical device, according to its operation function, the atomic function is combed and split to form an atomic function set, denoted as OSet:

[0048] OSet={op1,op2,...,op i};

[0049] Wherein, op i ​The executable operations, such as turning on the device, turning off the device, etc., each operation in OSet can be executed independently, but there are allowed dependencies (such as the device can only be turned off after being turned on).

[0050] For a specific Internet of Things physical device, according to its operating function, define its global state data, denoted as S. The state data S is a matrix used to manage the basic information of the device, such as device signal strength, power, switch state, etc. At the same time, for the user data managed by the device, define the user information set DSet:

[0051] DSet={D1,D2,...,D i};

[0052] Where D i represents the matrix of each user information managed by the device, i.e. D i and D j are data belonging to completely independent subjects, such as user fingerprints, mobile phone numbers, etc. D i and D j can also be set as different range data of the same user, such as desensitized photos and original photos, etc.

[0053] The matrix structure and data definition of D i and D j are consistent. For a specific user data, denoted as D. At this point, a subject's specific operation on a physical device can be expressed as: op i (S, D). Where S can be empty, i.e. the operation can not interact with the global device information, such as pressing the switch, but it does not need to know whether the device is turned on after the switch operation.

[0054] According to the device functions that need to be opened in the meta-universe business scenario, design the operation scenario, and the operation scenario set is denoted as ASet.

[0055] ASet={A1,A2,...,A i};

[0056] Wherein, each A i contains several non-repeating op i .

[0057] In the meta-universe scenario, for a real physical device, a virtual device is created for the user only when the user needs to obtain the use permission, including:

[0058] Obtain the user's authorization data, corresponding to D i user data;

[0059] According to the business context, determine the scene A x that the user can operate;

[0060] According to A x Determined op i Confirm whether to contain global state data S;

[0061] Record the effective period, ID, associated user ID, etc. of the virtual device;

[0062] Virtual device creation is completed, and its elements include device scene A x User data D i Device metadata, global state data S (may be empty).

[0063] Use of virtual device:

[0064] The user updates or enters his personal data, and the data is synchronized to the virtual device under his name;

[0065] The user selects the virtual device and performs the operation op i Its corresponding op i (S, D) process is sent to the physical device for actual execution;

[0066] After the physical device performs the operation, the corresponding S and D change, and the user obtains the results.

[0067] S3, the virtual subject in the meta-universe environment initiates a device creation request;

[0068] In an embodiment, in the step of initiating a device creation request by a virtual subject in the meta-universe environment, the virtual subject in the meta-universe system obtains a request description interface for creating a virtual device through a business scene in the meta-universe, including a place and a character, first obtains a device unique identifier, a device scene set, and a virtual device description file from the request interface, encapsulates the subject data handle, creates virtual device metadata according to the virtual device description file, selects a subset of the device scene set according to the required function, requests the signature of the authorized subject, and encapsulates the above information as a request, sends the request to the authorized subject of the virtual device, the authorized subject adds the personal signature to the virtual device metadata, and sends the request to the global device management service end to request the creation of the virtual device.

[0069] Referring to Figure 2 the schematic diagram of the creation process of the virtual device and Figure 3 the schematic diagram of the virtual device data structure; virtual device authorization and secondary creation:

[0070] For the virtual device owned by the user subject, obtain its device scene and user data;

[0071] User selects authorized content, authorized operation is a subset of device scene, but needs to exist in the physical device scene set;

[0072] User selects authorized data content, which is a subset of personal data, and checks the compatibility of the device scene subset and the personal data subset, i.e. the operation is executable within the authorized data range;

[0073] For authorized users, combine their personal data with the authorized data subset to form a new personal data set;

[0074] According to the scene subset, the new personal data set, define device metadata, and create a new virtual device.

[0075] S4, the global device management server completes the virtual device creation;

[0076] In an embodiment, in the step of completing the virtual device creation by the global device management server, the global device management server receives a virtual device creation request, first verifies the virtual device unique identifier in the request against the signature of the authorized principal to authenticate, ensures the request legality, secondly verifies the matching of the operation set and the data set in the request, ensures the operation and data function have execution on the device, after verification success, uses depth traversal to locate the authorized principal's virtual device in the virtual device tree, adds a leaf node virtual device under it, the leaf node contains the device operation set in the request, virtual device metadata, personal principal and signature information of the authorization process, the device ownership belongs to the principal of the request virtual device.

[0077] S5, the virtual principal in the meta universe environment interacts with the device;

[0078] In an embodiment, in the step of virtual principal in the meta universe environment interacting with the device, in the meta universe, the principal of the virtual device initiates interaction with the virtual device under his name, sends a request to the global device management server, the request parameters include virtual device unique identifier, atomic operation identifier, the global device service gets the request, and according to the virtual device unique identifier, retrieves the user data transmitted by the handle in advance, executes the related operation on the physical device, and the operation result of the physical device is fed back to the virtual principal requesting device interaction through the user data.

[0079] Referring to Figure 4 The schematic diagram of the virtual device management tree is shown, and the life cycle management of the virtual device is as follows:

[0080] Define the root node of the device tree, the root node contains the global data of the physical device, its scene subset is the full set, and the user data is the device administrator data;

[0081] For each user, a corresponding virtual device is generated, which is the first layer tree node, and for the second authorized device of the user and the third authorized device, the nodes are continuously generated along the branch of the corresponding tree until the nth time;

[0082] For each node of the global virtual device tree, when the user data and global device data change, the corresponding data of the child node is changed, and the actual operation interaction of the virtual device corresponding to the child node with the user is performed;

[0083] When a certain node is deleted, the corresponding child nodes are all deleted first, and then the node itself is deleted, and the virtual device deletion information corresponding to the node is no longer available to the user.

[0084] Among them, the natural person with data ownership is taken as the granularity, which is the finest division, the virtual device can be infinitely divided on the physical device, the user can authorize others to use the virtual device, the data flow process is clear, and there is a strict permission traceability relationship.

[0085] S6, the global device management server performs device management.

[0086] In an embodiment, in the device management step performed by the global device management server, the global device management server periodically performs deep traversal on the virtual device tree, searches each virtual device node, checks the metadata of the virtual device, ensures the validity period and signature consistency of the virtual device, when inconsistency occurs, marks the state of the invalid node and all subsequent child nodes as unusable, when the device metadata in the virtual device node changes, first perform deep traversal on all subordinate nodes under the node, pass the changed user data to each subordinate node, and change the metadata of each terminal node.

[0087] The application uses virtual devices to manage physical devices, divides permissions to data subjects, that is, manages each data subject corresponding to a specific virtual device, records the authorization process of the device between different data subjects in the form of virtual devices, and clearly expresses the operation and data transmission of the device in the virtual device tree, which can be tracked throughout the process.

[0088] Please refer to Figure 5 The application also discloses an Internet of Things device management apparatus in a meta universe, which comprises an initialization unit 10, an access unit 20, an initiation unit 30, a completion unit 40, an interaction unit 50 and a management unit 60.

[0089] The initialization unit 10 is used for initializing the global device management server.

[0090] The access unit 20 is used for accessing the physical Internet of Things device by the global device management server.

[0091] The initiating unit 30 is configured to initiate a device creation request by a virtual subject in the metaverse environment.

[0092] The completing unit 40 is configured to complete virtual device creation by the global device management server.

[0093] The interacting unit 50 is configured to interact with the device by the virtual subject in the metaverse environment.

[0094] The management unit 60 is configured to perform device management by the global device management server.

[0095] It should be noted that the specific implementation process of the above-mentioned metaverse Internet of Things device management apparatus and each unit can be clearly understood by those skilled in the art, which can be referred to the corresponding description in the foregoing method embodiments. For the convenience and brevity of description, it will not be repeated here.

[0096] The above-mentioned metaverse Internet of Things device management apparatus can be implemented in the form of a computer program, which can run on a computer device as shown in the computer device. Figure 6 The computer device can be a terminal or a server.

[0097] Please refer to Figure 6 , Figure 6 is a schematic block diagram of a computer device provided by an embodiment of the present application; the computer device 500 can be a terminal or a server, wherein the terminal can be a smart phone, a tablet computer, a notebook computer, a desktop computer, a personal digital assistant, a wearable device, and an electronic device with a communication function. The server can be a stand-alone server or a server cluster composed of multiple servers.

[0098] Refer to Figure 6 , the computer device 500 includes a processor 502, a memory, and a network interface 505 connected through a system bus 501, wherein the memory can include a non-volatile storage medium 503 and an internal memory 504.

[0099] The non-volatile storage medium 503 can store an operating system 5031 and a computer program 5032. The computer program 5032 includes program instructions, which when executed, can cause the processor 502 to execute a metaverse Internet of Things device management method.

[0100] The processor 502 is configured to provide computing and control capabilities to support the operation of the entire computer device 500.

[0101] The memory 504 provides an environment for running the computer program 5032 in the nonvolatile storage medium 503, which, when executed by the processor 502, enables the processor 502 to perform an Internet of Things device management method in a meta universe.

[0102] The network interface 505 is used for network communication with other devices. Those skilled in the art can understand that, Figure 6 The structure shown in the figure is only a block diagram of part of the structure related to the scheme of the present application, and does not constitute a limitation on the computer device 500 to which the scheme of the present application is applied. The specific computer device 500 can include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0103] The processor 502 is configured to run the computer program 5032 stored in the memory to implement the following steps:

[0104] Initialization of a global device management server; the global device management server accesses a physical Internet of Things device; a virtual subject in a meta universe environment initiates a device creation request; the global device management server completes virtual device creation; the virtual subject in the meta universe environment interacts with the device; and the global device management server manages the device.

[0105] It should be understood that, in the embodiments of the present application, the processor 502 can be a central processing unit (CPU), and the processor 502 can also be other general-purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or the processor can also be any conventional processor.

[0106] Those of ordinary skill in the art can understand that all or part of the processes in the method of the above-mentioned embodiments can be completed by a computer program instructing related hardware. The computer program includes program instructions, and the computer program can be stored in a storage medium, which is a computer-readable storage medium. The program instructions are executed by at least one processor in the computer system to implement the process steps of the above-mentioned embodiments of the method.

[0107] Therefore, the application further provides a storage medium. The storage medium can be a computer-readable storage medium. The storage medium stores a computer program, where the computer program includes program instructions, which, when executed by a processor, can implement the method for managing Internet of Things devices in a meta universe described above. The storage medium stores a computer program, where the computer program includes program instructions, which, when executed by a processor, can implement the method described above. The program instructions include the following steps:

[0108] Initialization of the global device management server; the global device management server accesses a physical Internet of Things device; a virtual subject in a meta universe initiates a device creation request; the global device management server completes virtual device creation; the virtual subject in the meta universe interacts with the device; and the global device management server performs device management.

[0109] The storage medium can be a U disk, a mobile hard disk, a read-only memory (ROM), a magnetic disk, or an optical disk, and various computer-readable storage media that can store program codes.

[0110] Those skilled in the art can appreciate that the units and algorithm steps of the examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, computer software, or a combination of both. In order to clearly illustrate the interchangeability of hardware and software, the components and steps of the examples have been described in the above description in general terms. Whether the functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. A person skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of the present application.

[0111] In several embodiments provided by 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 each unit is only a logical function division, and actual implementation can have another division manner. For example, a plurality of units or components can be combined or integrated into another system, or some features can be omitted or not executed.

[0112] The steps in the method embodiments of the present application can be adjusted, combined, and reduced in sequence according to actual needs. The units in the device embodiments of the present application can be combined, divided, and reduced according to actual needs. In addition, each functional unit in each embodiment of the present application can be integrated in one processing unit, or each unit can exist physically, or two or more units can be integrated in one unit.

[0113] The integrated unit, if implemented in the form of a software function unit and sold or used as an independent product, can be stored in a storage medium. Based on such an understanding, the technical solutions of the present application, in essence or the part that contributes to the prior art, or the whole or part of the technical solutions can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes a plurality of instructions for causing a computer device (which can be a personal computer, a terminal, or a network device, etc.) to execute all or part of the steps of the method described in the various embodiments of the present application.

[0114] The above embodiments are the preferred implementation of the present application, and in addition, the present application can be implemented in other ways, and any obvious replacement without departing from the technical solution concept is within the protection scope of the present application.

Claims

1. A method for managing IoT devices in a metaverse, characterized by, Comprising the following steps: Initialization of the global device management service end; Global device management service end access physical Internet of Things device; Virtual subject in the meta universe environment initiates a device creation request; Global device management service end completes virtual device creation; Virtual subject in the meta universe environment interacts with the device; Global device management service end performs device management; In the step of the virtual subject in the meta universe environment initiating a device creation request, the virtual subject in the meta universe system obtains a request description interface for creating a virtual device through a business scenario in the meta universe, including a place and a person, first obtains a device unique identifier, a device scenario set, and a virtual device description file from the request interface, requests a virtual device creation subject, encapsulates the subject data handle, creates virtual device metadata according to the virtual device description file, selects a subset of the device scenario set according to the required function, requests the signature of the authorized subject, and encapsulates the above information as a request, sends the virtual device authorization subject, the authorized subject adds a personal signature to the virtual device metadata, and sends the request to the global device management service end to request virtual device creation; In the step of the global device management service end completing virtual device creation, the global device management service end receives the virtual device creation request, first verifies the virtual device unique identifier in the request and the signature of the authorized subject for authentication, ensures the legality of the request, and then verifies the matching of the operation set and the data set in the request, ensures the execution of the operation and the data function on the device, after successful verification, uses deep traversal to locate the virtual device of the authorized subject in the virtual device tree, adds a leaf node virtual device under it, the leaf node contains the device operation set in the request, the virtual device metadata, the personal subject, and the signature information of the authorization process, and the ownership of the device belongs to the subject requesting the virtual device; In the step of the virtual subject in the meta universe environment interacting with the device, the virtual device owner in the meta universe initiates an interaction with the virtual device under his name, sends a request to the global device management service end, the request parameters include a virtual device unique identifier and an atomic operation identifier, the global device service obtains the request, retrieves the user data transmitted through the handle in advance according to the virtual device unique identifier, executes the related operation on the physical device, and the operation result of the physical device is fed back to the virtual subject requesting the device interaction through the user data.

2. The IoT device management method in the meta universe according to claim 1, wherein, In the step of initializing the global device management service end, the service end is deployed, network connection with the Internet of Things device is performed, necessary device interaction authentication parameters are set, and the unique identifier, model information, region, and owner information of the Internet of Things device are recorded.

3. The IoT device management method in the meta universe according to claim 1, wherein, The global device management server accesses the physical Internet of Things device, first divides the atomic operation for a specific Internet of Things device model, forms an operation set, then arranges and combines the atomic operation in the operation set to form a scene set, subsequently sets user data specification definition and virtual device metadata definition according to the scene set to form a virtual device description file, and the global device management server creates a virtual device for the accessed physical device, the virtual device contains all the scene set and initial user data, and is used as a root node of a subsequent virtual device tree, and the initial user is a device administrator.

4. The IoT device management method in the meta universe according to claim 1, wherein, In the device management step of the global device management server, the global device management server periodically performs deep traversal on the virtual device tree, searches each virtual device node, checks the metadata of the virtual device, ensures the validity period and signature consistency of the virtual device, marks the state of the invalid node and all subsequent child nodes as unusable when inconsistency occurs, and changes the metadata of the virtual device node.

5. An IoT device management apparatus in a metaverse, characterized by Comprise: An initialization unit, an access unit, an initiation unit, a completion unit, an interaction unit and a management unit; The initialization unit is configured to initialize the global device management server; The access unit is configured to access the physical Internet of Things device by the global device management server; The initiation unit is configured to initiate a device creation request by a virtual subject in the meta universe environment; The completion unit is configured to complete virtual device creation by the global device management server; The interaction unit is configured to interact with the device by the virtual subject in the meta universe environment; The management unit is configured to manage the device by the global device management server; In the initiation unit, the virtual subject in the meta universe system obtains a request description interface for creating a virtual device through a business scene in the meta universe, including a place and a person, first obtains a device unique identifier, a device scene set and a virtual device description file from the request interface, encapsulates subject data handle, creates virtual device metadata according to the virtual device description file, selects a subset of the device scene set according to the required function, requests a signature of the authorized subject, encapsulates the above information as a request, sends the request to the authorized subject of the virtual device, adds the personal signature to the virtual device metadata, and sends the request to the global device management server to request virtual device creation. In the completion unit, the global device management server receives a virtual device creation request, first verifies the virtual device unique identifier in the request against the signature of the authorized subject to ensure the request is legitimate, and then verifies the matching of the operation set and the data set in the request to ensure that the operation and data functions have execution on the device. After successful verification, a leaf node virtual device is added under the virtual device of the authorized subject using deep traversal, which contains the device operation set, virtual device metadata, personal subject, and signature information of the authorization process in the request. The ownership of the device belongs to the subject of the request virtual device; In the interaction unit, the owner of the virtual device in the meta universe initiates interaction with the virtual device under his name, sends a request to the global device management server, and the request parameters include the virtual device unique identifier and atomic operation identifier. The global device service obtains the request and retrieves the user data previously transmitted through the handle according to the virtual device unique identifier, executes the related operation on the physical device, and the operation result of the physical device is fed back to the virtual subject requesting device interaction through the user data.

6. A computer device, comprising: The computer device includes a memory and a processor, the memory stores a computer program, and the processor executes the computer program to realize the IoT device management method in the meta universe as claimed in any one of claims 1-4.

7. A storage medium, characterized by The storage medium stores a computer program, the computer program includes program instructions, and the program instructions can realize the IoT device management method in the meta universe as claimed in any one of claims 1-4 when executed by the processor.

Citation Information

Patent Citations

  • Internet of Things control system processing method and system, cloud server and medium

    CN111885170A

  • Control method, system and device, electronic device and computer readable storage medium

    CN115167165A