Platform for managing metaverse based on internet of things

Abstract

The present invention relates to an IoT-based metaverse management platform, wherein IoT data generated from multiple AIoT devices or IoT devices is labeled to enable the selective provision of IoT data to multiple metaverses, thereby allowing the provision of desired IoT data to a metaverse authoring tool for creating a new metaverse without affecting or causing any existing metaverse.

Description

Technology Field

[0001] The present invention relates to an Internet of Things-based metaverse management platform, and more specifically, to an Internet of Things-based metaverse management platform that allows the provision of desired IoT data to a metaverse authoring tool for creating a new metaverse without affecting or causing any existing metaverse, by labeling IoT data generated from multiple AIoT devices or IoT devices and selectively providing IoT data to multiple metaverses. Background Technology

[0002] Public interest is focusing on the metaverse and digital twin, which can connect the virtual world and the physical real world through interaction with various platforms, including social and economic activities.

[0003] In particular, the metaverse, as a field of digital twins, operates through virtual space platforms to overcome spatiotemporal limitations and enable the formation of a non-face-to-face online culture; it also has the potential to provide new forms of interaction and experience when applied to various fields such as gaming, education, healthcare, and marketing.

[0004] This metaverse goes beyond merely implementing real-world objects into a virtual world to create results that can be reflected in the real world; it can realize the virtual world as equivalent to the real world through interaction with users.

[0005] In particular, due to the rapid development of IoT technology in recent years, a foundation is being established to easily collect user interactions and user status.

[0006] As the metaverse is based on interaction with users, if IoT data related to users collected through IoT devices can be used for metaverse authoring or reflected in the metaverse, the metaverse can be utilized more efficiently.

[0007] Accordingly, the present invention proposes a metaverse management platform (or system) that enables the use of a user's IoT data for metaverse authoring or for reflection in an existing metaverse.

[0008] More specifically, the present invention proposes a method that allows IoT data labeled for metaverse authoring and IoT data labeled for existing metaverse reflection to be uploaded from an IoT device to an IoT server for storage, and displays a list of names for the IoT data for metaverse authoring and IoT data for metaverse reflection according to the user's selection, so that the user can subscribe to the IoT server for the IoT data corresponding to the name of at least one selected IoT data, receive the said IoT data as a notification, and provide it to a metaverse authoring tool or provide it to an existing metaverse for reflection according to the label of the IoT data.

[0009] Furthermore, through the present invention, we propose a method in which, upon receiving IoT data from a user following a subscription request from an IoT server, the IoT data is parsed, and if the IoT data is for metaverse authoring, it is transmitted to a metaverse authoring tool; if the data is for existing metaverse reflection, the IoT data is mapped to the API of the metaverse server and transmitted to enable reflection.

[0010] Next, we will briefly explain the prior art existing in the technical field of the present invention, and then describe the technical details that the present invention aims to achieve differently from the said prior art.

[0011] First, Korean Registered Patent No. 2592521 (October 18, 2023) relates to an augmented reality virtual content provision system for linking weather data and the metaverse. It concerns a system that receives weather data and a user's biometric data, enabling the user to observe weather conditions in real time within a virtual space while using the metaverse, and to monitor the user's health abnormalities and stress levels.

[0012] In other words, Korean Registered Patent No. 2592521 merely describes synchronizing weather data and biometric data within a virtual space when weather data or biometric data is received.

[0013] On the other hand, regarding the present invention, which subscribes to a user's IoT data corresponding to the name of the IoT data selected by the user from an IoT server, receives and parses the user's IoT data from the IoT server whenever the user's IoT data is uploaded, and transmits the parsed result to a metaverse authoring tool or a metaverse server to author the metaverse or reflect it in the metaverse, Korean Registered Patent No. 2592521 does not describe, suggest, or imply any such technical features of the present invention.

[0014] In addition, Korean Registered Patent No. 2395940 (May 4, 2022) relates to a method for controlling user video data in a metaverse-based office environment, a storage medium having a program for executing the same, and a user video data control system including the same. It relates to a storage medium having a program for executing the method for controlling user video data in a metaverse-based office environment and a user video data control system including the same, which can enhance social bonding in a 3D office environment pursued by the metaverse by capturing the current situation of a participant corresponding to a character connected to a 3D office environment implemented in the metaverse in real time and overlapping it.

[0015] In other words, Korean Registered Patent No. 2395940 merely displays a user's video captured by a camera overlaid on the user's character, and does not describe at all the process of processing data for authoring the metaverse.

[0016] On the other hand, the present invention adds a metaverse authoring label or an existing metaverse reflection label to IoT data, receives the IoT data desired by the user from an IoT server, parses it, and provides the IoT data to a metaverse authoring tool according to the label to author a metaverse or to provide it to an existing metaverse for use. Therefore, the two inventions have significant differences in their technical configuration, effects, and purposes. The problem to be solved

[0017] The present invention was created to solve the above-mentioned problems, and aims to provide an IoT-based metaverse management platform that enables the creation of a metaverse or the reflection of an existing metaverse using said IoT data by receiving from an IoT server IoT data labeled for metaverse authoring and IoT data labeled for reflection in an existing metaverse, and by parsing said received IoT data and providing it to a metaverse authoring tool or a metaverse server according to the label.

[0018] Furthermore, the present invention aims to provide a metaverse management platform and a method thereof, wherein, while IoT / AIoT data generated from a plurality of IoT devices is being uploaded to an IoT server, when a user subscribes to IoT data corresponding to the name of the IoT data selected by the user, the user receives a notification that the corresponding IoT data has been transmitted from the IoT server, and provides the data to a metaverse authoring tool or an existing metaverse according to a label attached to the IoT data.

[0019] In addition, the present invention aims to provide a metaverse management platform and a method thereof that allows a user to subscribe to desired IoT data by requesting a list of IoT data names from an IoT server and displaying it to a user, and by allowing the user to select at least one name of the IoT data.

[0020] Furthermore, the present invention aims to provide a metaverse management platform and a method for transmitting and receiving IoT data based on the Internet of Things, including teleport information based on a user's pose, emotional information based on a user's facial expression, biometric information of the user, and surrounding environment information.

[0021] Furthermore, the present invention aims to provide a metaverse management platform and a method thereof that, when the label of IoT data is intended for reflection in the metaverse, maps the IoT data to an API of a metaverse server and transmits the result to the metaverse server, thereby enabling the IoT data to be immediately reflected in the metaverse.

[0022] Furthermore, the present invention aims to provide a metaverse management platform and a method thereof, wherein when the label of the IoT data is a metaverse author, the IoT data is transmitted from a socket client to a socket server of a metaverse authoring tool to enable interworking between the IoT data and the metaverse authoring tool. means of solving the problem

[0023] An IoT-based metaverse management platform according to one embodiment of the present invention comprises: an IoT data receiving unit that receives IoT data requested for subscription from an IoT server; and a parsing unit that parses the label of the received IoT data; and is characterized by transmitting to the corresponding metaverse according to the parsed label.

[0024] The above metaverse is characterized by including at least one existing metaverse and at least one metaverse authoring tool for performing authoring, including creating or modifying a new metaverse.

[0025] The parsing unit parses the label to classify whether the received IoT data is for metaverse authoring or for metaverse reflection, and is characterized by transmitting the received IoT data to a metaverse authoring tool if it is for metaverse authoring, and transmitting it to a metaverse server if it is for metaverse reflection. At least one metaverse and at least one metaverse authoring tool may exist for each.

[0026] In addition, the above IoT data includes teleport information for moving the user's character to a specific location in the metaverse, the user's emotional information, the user's biometric information, or a combination thereof, and is characterized by having a metaverse authoring label or a metaverse reflection label attached. Each of the metaverse authoring label or the metaverse reflection label may include at least one other label serving as a different identifier.

[0027] Additionally, the metaverse management platform further comprises: an IoT data name list requesting unit that requests an IoT data name list from the IoT server; an IoT data name list receiving unit that receives the requested IoT data name list from the IoT server; an IoT data name list processing unit that displays the received IoT data name list according to a user's request and allows at least one IoT data name to be selected; and a subscription requesting unit that requests the IoT server to subscribe to the IoT data corresponding to the selected at least one IoT data name. Each list item of the IoT data name list includes the name of the corresponding IoT data and a label of the corresponding IoT data, wherein the label includes at least one metaverse authoring label, at least one metaverse reflection label, or a combination thereof.

[0028] Additionally, the metaverse management platform further comprises a socket client that transmits the parsed IoT data to a metaverse authoring tool via socket communication if, as a result of the parsing, the received IoT data is for metaverse authoring; an API mapping unit that maps the parsed IoT data to an API of the metaverse server if, as a result of the parsing, the received IoT data is for metaverse reflection; and a metaverse client that transmits the API mapping result to the metaverse server. The API mapping unit is characterized by mapping the IoT data to a metaverse server API for reflecting the IoT data in the metaverse.

[0029] In addition, an IoT-based metaverse management method according to one embodiment of the present invention comprises an IoT data receiving step of receiving IoT data requested for subscription from an IoT server in an IoT-based metaverse management platform, and a parsing step of parsing the label of the received IoT data in the metaverse management platform, and is characterized by transmitting to the corresponding metaverse according to the parsed label.

[0030] The above metaverse is characterized by including at least one existing metaverse and at least one metaverse authoring tool for performing authoring, including creating or modifying a new metaverse.

[0031] The above parsing step is characterized by parsing the label to classify whether the received IoT data is for metaverse authoring or for metaverse reflection, and transmitting the received IoT data to a metaverse authoring tool if it is for metaverse authoring, and transmitting it to a metaverse server if it is for metaverse reflection. At least one metaverse and at least one metaverse authoring tool may exist for each.

[0032] In addition, the metaverse management method comprises: an IoT data name list request step in which, at least one IoT device in the metaverse management platform generates IoT data and requests a list of names of IoT data uploaded to an IoT server; an IoT data name list reception step in which, in the metaverse management platform, the IoT data name list is received from the IoT server as a response to the request; an IoT data name list processing step in which, in the metaverse management platform, the received list of names of IoT data is displayed or stored in a database; a subscription request step in which, in the metaverse management platform, the user requests a subscription to IoT data corresponding to at least one name of IoT data selected by the user from the IoT server; and an IoT data reception step in which, in the metaverse management platform, the IoT data is received as a notification from the IoT server in accordance with the subscription request.

[0033] Each list item of the name list of the above IoT data includes the name of the IoT data and the label of the IoT data, and the label is characterized by including at least one metaverse authoring label, at least one metaverse reflection label, or a combination thereof.

[0034] Additionally, the metaverse management method further comprises: a metaverse authoring IoT data transmission step in which, if the parsing result indicates that the received IoT data is for metaverse authoring, the parsed IoT data is transmitted from a socket client to a metaverse authoring tool via socket communication in the metaverse management platform; an API mapping step in which, if the parsing result indicates that the received IoT data is for metaverse reflection, the parsed IoT data is mapped to an API of the metaverse server; and a metaverse reflection IoT data transmission step in which the API mapping result is transmitted to the metaverse server via a metaverse client; wherein the API mapping step is characterized by mapping the IoT data to a metaverse server API for reflection in the metaverse. Effects of the invention

[0035] As described above, the present invention has the effect of enabling the selective provision of IoT data to multiple metaverses by labeling IoT data generated from multiple AIoT devices or IoT devices, thereby allowing the provision of desired IoT data to a metaverse authoring tool for creating a new metaverse without affecting or causing any existing metaverse.

[0036] In addition, the present invention has the advantage of effectively reflecting IoT data in the metaverse or in the metaverse by providing IoT data to metaverse developers who do not possess IoT technology or to users who use the existing metaverse, by providing IoT data to metaverse authoring tools or the metaverse.

[0037] In addition, the present invention allows IoT data to be designated for at least one metaverse authoring or at least one metaverse reflection through a label, and has the effect of easily providing the IoT data to a metaverse authoring tool or metaverse server by parsing the data according to the label and classifying it for metaverse authoring or reflection. Brief explanation of the drawing

[0038] FIG. 1 is a diagram illustrating an IoT-based metaverse management platform and a method thereof in accordance with one embodiment of the present invention. FIG. 2 is a diagram illustrating a method for authoring a metaverse by transmitting metaverse authoring IoT data to a metaverse authoring tool according to an embodiment of the present invention. FIG. 3 is a diagram illustrating a method for mapping IoT data and a metaverse API according to an embodiment of the present invention. FIG. 4 is a flowchart illustrating a procedure for transmitting a user's IoT data to a metaverse authoring tool through a metaverse management platform according to an embodiment of the present invention. FIG. 5 is a flowchart illustrating a procedure for transmitting a user's IoT data to a metaverse server through a metaverse management platform according to an embodiment of the present invention. FIG. 6 is a block diagram showing the hardware structure of a metaverse management platform according to one embodiment of the present invention. Specific details for implementing the invention

[0039] Hereinafter, preferred embodiments of the IoT-based metaverse management platform and method according to the present invention will be described in detail with reference to the attached drawings. Identical reference numerals in each drawing indicate identical components. Furthermore, specific structural or functional descriptions regarding embodiments of the present invention are illustrative for the purpose of explaining embodiments according to the present invention, and unless otherwise defined, all terms used herein, including technical or scientific terms, have the same meaning as generally understood by those skilled in the art to which the present invention pertains. Terms such as those defined in commonly used dictionaries should be interpreted as having a meaning consistent with their meaning in the context of the relevant technology, and unless explicitly defined in this specification, it is preferable not to interpret them in an ideal or overly formal sense.

[0040] FIG. 1 is a diagram illustrating an IoT-based metaverse management platform and a method thereof in accordance with one embodiment of the present invention.

[0041] As illustrated in FIG. 1, an IoT-based metaverse management platform (100) (hereinafter referred to as the metaverse management platform (or system)) according to one embodiment of the present invention subscribes to IoT data corresponding to the name of IoT data selected by a user from an IoT server (300), and whenever the IoT data is uploaded to the IoT server, receives it from the IoT server (300) and provides it to a metaverse authoring tool (400) or metaverse (500), thereby enabling the IoT data to be used for metaverse authoring or reflected in the existing metaverse (500).

[0042] The above IoT server (300) receives IoT / AIoT data from a plurality of IoT / AIoT (Artificial intelligence of Things) devices (200) and stores it in a database (not shown).

[0043] The above IoT device (200) generates IoT data based on sensor data collected through at least one sensor and uploads it to the IoT server (300).

[0044] The above IoT device (200) may be configured to generate and provide IoT data including pose estimation, IoT data including facial expression estimation, or user's biometric information. However, it is not limited to those listed herein.

[0045] The IoT device (200) that generates IoT data through the pose estimation above is configured to photograph a user with a camera to estimate the user's pose, extract pre-set teleport information according to the estimated user's pose, generate IoT data including the extracted teleport information, transmit the generated IoT data to TAS (Thing Adaptation Software), and then upload it to the IoT server (300) through an IoT client.

[0046] Estimating the user's pose is performed by inputting an image of the user into a pose estimation training model generated by training pose estimation training data in which poses are labeled on images of a person's body (specifically the upper body), and selecting the pose with the highest probability among the outputs of the pose estimation training model.

[0047] The above teleport information is extracted from a mapping table that maps the location (or place) to move to within the metaverse according to the pose, and the teleport information is extracted by extracting the location (or place) corresponding to the estimated pose.

[0048] Additionally, an IoT device (200) that generates IoT data through facial expression estimation is configured to photograph a user with a camera to estimate the facial expression appearing on the user's face, extract emotional information based on the estimated facial expression, generate IoT data including the extracted emotional information, transmit the generated IoT data to a TAS, and then upload it to an IoT server (300) through an IoT client.

[0049] Estimating the user's facial expression is performed by inputting an image of the user into a facial expression estimation learning model, which is generated by training facial expression estimation learning data in which facial expressions are labeled on an image of a person's body (specifically the upper body), and selecting the facial expression with the highest probability among the outputs of the corresponding facial expression estimation learning model.

[0050] The above emotional information is extracted from a mapping table that maps emotions according to facial expressions, and the IoT device (200) can extract emotional information corresponding to the estimated facial expression and generate it as IoT data.

[0051] The above facial expressions may consist of a smiling expression, a crying expression, a frowning expression, a surprised expression, an angry expression, a surprised expression, a blank expression, etc., and the emotional information may consist of happy, disgusted, fearful, happy, neutral, sad, and surprised.

[0052] The above learning model is generated through an artificial intelligence machine learning method, and the IoT device (200) equipped with the learning model is also referred to as an AIoT (artificial IoT) device.

[0053] An IoT device (200) that generates IoT data including the above biometric information can be configured to measure the user's biometric information through at least one biometric information measurement sensor, generate IoT sensor data including the measured biometric information, store it in a small storage (e.g., SQLite), synchronize it and transmit it to TAS, and upload it to an IoT server (300) through an IoT client.

[0054] The above-mentioned biometric information measurement sensor is configured to include a temperature sensor, a heart rate measurement sensor, a stress measurement sensor, etc., and the above-mentioned biometric information may include body temperature, heart rate, stress levels, etc.

[0055] The above TAS (thing adaptation software) is intended to convert IoT data generated by each IoT device (200) into a data format according to a communication protocol for IoT data transmission and reception (e.g., MQTT (message queueing telemetry transport), CoAP (constrained application protocol)).

[0056] Additionally, the IoT device (200) adds a pre-set label to the generated IoT data (labeling) and transmits it to the IoT server (300).

[0057] The above labels are configured to include a label indicating that the IoT data is intended for use in metaverse authoring (i.e., metaverse authoring) (i.e., metaverse authoring label) and a label indicating that the data is intended for use in the metaverse utilized by existing users (i.e., metaverse reflection label). These labels are configured to be added by the IoT client middleware.

[0058] For example, the metaverse authoring label can be set to 1 and the metaverse reflection label to 0, and can be labeled (added) to IoT data.

[0059] The above metaverse management platform (100) is configured to include an IoT data name list request unit (110), an IoT data name list receiving unit (120), an IoT data name list processing unit (130), a subscription request unit (140), an IoT data receiving unit (150), a parsing unit (160), a socket client (170), an API mapping unit (180), and a metaverse client (190).

[0060] The above metaverse management platform (100) is implemented as a server, device, or system to manage the metaverse.

[0061] The above IoT data name list request unit (110) requests a name list of IoT data with attached metaverse authoring labels and metaverse reflection labels from the IoT server (300) and stores it in a database.

[0062] The name list of the above IoT data refers to the type of IoT data that has been labeled. For example, if a metaverse authorship label (e.g., 1) is attached and the IoT data is biometric information, the name of the IoT data consists of biometric information with the metaverse authorship label attached. That is, it can be configured in the form of label_1_biometric_information.

[0063] At this time, the IoT server (300) manages a list of names of IoT data, and when there is a request for a list of names of IoT data from the metaverse management platform (100), it transmits the list of names of IoT data to the metaverse management platform (100) as a response. Requesting the list of names of IoT data may be performed periodically.

[0064] The above IoT data name list receiving unit (120) receives a list of IoT data names from the IoT server (300) which is a response to the request of the IoT data name list requesting unit (110).

[0065] The above IoT data name list processing unit (130) displays a name list of IoT data according to a user's request. The user can request a name list of IoT data by accessing the metaverse management platform (100) through a user terminal (not shown).

[0066] At this time, the IoT data name list processing unit (130) displays a list of IoT data names through a user interface and allows at least one IoT data name to be selected, with a metaverse authoring label or a metaverse reflection label attached.

[0067] The above subscription application unit (140) performs the function of applying to the IoT server (300) for a subscription to the user's IoT data corresponding to the name of the IoT data selected by the user.

[0068] Here, subscription refers to a service that allows a user to receive a notification when their IoT data corresponding to the name (or type) of the IoT data selected by the user is uploaded to the IoT server (300).

[0069] At this time, the IoT server (300) is configured to provide the uploaded IoT data to the metaverse management platform (100) via a notification when the user's IoT data corresponding to the name of the IoT data selected by the user is uploaded after the subscription application is completed.

[0070] The above IoT data receiving unit (150) receives IoT data from the IoT server (300) according to the subscription as a notification.

[0071] The parsing unit (160) parses the received IoT data and classifies whether the received IoT data is for metaverse authoring or for metaverse reflection. The classification is performed by referring to a label attached to the received IoT data.

[0072] The socket client (170) transmits metaverse authoring IoT data to the metaverse authoring tool (400) via socket communication.

[0073] The above metaverse authoring tool (400) is linked with the metaverse management platform (100) and is configured to include a socket server to receive metaverse authoring IoT data.

[0074] The above metaverse authoring tool (400) may be provided on the cloud separately from the metaverse management platform (100), provided on a user terminal, or provided in the metaverse (500). However, it is not limited thereto and may be provided on the metaverse management platform (100).

[0075] The above user can create a metaverse by utilizing IoT data through a metaverse authoring tool (400).

[0076] The process of transmitting the above metaverse authoring IoT data to the metaverse authoring tool (400) and authoring it will be explained in detail with reference to FIG. 2.

[0077] The above API mapping unit (180) maps the IoT data to an API of the existing metaverse if the parsing result IoT data is for reflection in the metaverse.

[0078] That is, the API mapping unit (180) maps IoT data with a label for metaverse reflection to an API so that it can be reflected in the existing metaverse, and will be explained in detail with reference to FIG. 3.

[0079] The above metaverse client (190) transmits the API mapping result, which maps metaverse authoring IoT data and metaverse APIs, to the metaverse (500) through communication with the metaverse (500).

[0080] The above metaverse (500) reflects IoT data according to the API mapping result into the metaverse. Reflecting into the above metaverse will be explained with reference to FIG. 3.

[0081] FIG. 2 is a diagram illustrating a method for authoring a metaverse by transmitting metaverse authoring IoT data to a metaverse authoring tool according to an embodiment of the present invention.

[0082] As illustrated in FIG. 2, a metaverse management platform (100) according to one embodiment of the present invention parses the user's IoT data when the user's IoT data is received from an IoT server (300) in accordance with the user's subscription to the IoT data.

[0083] As a result of the above parsing, if the received IoT data is a metaverse author (i.e., the label is 1), the metaverse management platform (100) transmits the IoT data to the metaverse author tool (400) via socket communication.

[0084] The above metaverse authoring tool (400) may be composed of Unity, which is a type of program for authoring the metaverse, including the visualization of buildings and virtual reality. However, it is not limited to this, and various authoring tools for authoring the metaverse may be used.

[0085] The user can freely write functions through the metaverse authoring tool (400) and utilize IoT data to author NPCs (non-player characters), PCs (player characters), objects, worlds, etc. that constitute the metaverse.

[0086] For example, if IoT data classified as metaverse creation is emotional information ("happy") and biometric information including heart rate, body temperature, and stress index measured through GSR (Galvanic Skin Response) sensors, and if a PC is created during metaverse creation using each IoT data, it is possible to create a character in which the PC's facial expressions according to the emotional information and the biometric information are reflected in real time.

[0087] FIG. 3 is a diagram illustrating a method for mapping IoT data and a metaverse API according to an embodiment of the present invention.

[0088] As illustrated in FIG. 3, a metaverse management platform (100) according to one embodiment of the present invention parses the IoT data of a user when the user's IoT data is received from an IoT server (300) in accordance with the user's subscription to the IoT data.

[0089] As a result of the above parsing, if the received IoT data is for reflection in the metaverse (i.e., the label is 0), the metaverse management platform (100) maps the IoT data and the API of the metaverse for reflecting the IoT data in the metaverse, and transmits the API mapping result to the metaverse (500).

[0090] For example, assuming that IoT data is teleport information and that teleport information including "ready" and teleport information including a specific location (e.g., India) are required to teleport a user's character to a specific location in the metaverse, and for the IoT data including teleport information for "ready" and the IoT data including teleport information for a specific location, the metaverse management platform (100) maps the teleport information for "ready" to an API including a chat command indicating that teleport is ready, and maps the teleport information including the specific location to an API for setting pre-set coordinates and direction vectors in the metaverse for the specific location of the teleport information for a specific location for the user's character, and transmits the API mapping result to the metaverse (500).

[0091] That is, the metaverse management platform (100) maps the IoT data classified for metaverse reflection and the metaverse API required to reflect the IoT data in the metaverse, and transmits the API mapping result to the metaverse (500). It is obvious that the metaverse API corresponding to such IoT data must be shared with the metaverse management platform (100) in advance.

[0092] At this time, the metaverse (500) reflects IoT data into the metaverse according to the API mapping result.

[0093] In the above example, when an API mapping result that maps IoT data containing teleport information for preparation and an API mapping result that maps IoT data containing teleport information for a specific location are received, the metaverse (500) displays a chat in the metaverse indicating that teleport is ready and reflects the IoT data in the metaverse by teleporting the user's character to a specific location in a specific direction.

[0094] FIG. 4 is a flowchart illustrating a procedure for transmitting a user's IoT data to a metaverse authoring tool through a metaverse management platform according to an embodiment of the present invention.

[0095] As illustrated in FIG. 4, the procedure for transmitting a user's IoT data to a metaverse authoring tool through a metaverse management platform according to one embodiment of the present invention first performs an IoT data generation step in which IoT data is generated from a plurality of IoT devices (200) (S105).

[0096] The above IoT data includes teleport information, emotional information, biometric information, or a combination thereof. However, the present invention is not limited thereto and may further include various information such as surrounding environment information including temperature, humidity, and weather conditions of the surrounding environment, in addition to teleport information, emotional information, and biometric information.

[0097] Next, an IoT data upload step (S110) is performed in which the IoT device (200) uploads the generated IoT data to the IoT server (300), and an IoT data storage step (S115) is performed in which the IoT server (300) stores the IoT data uploaded from the IoT device (200) in a database.

[0098] Next, in the metaverse management system (100), an IoT data name list request step (S120) is performed to request a list of names of IoT data with labels attached from the IoT server (300), and an IoT data name list reception step is performed to receive the list of names of the IoT data from the IoT server (300) in response to the request (S125).

[0099] Afterwards, the IoT data name list receiving step further performs the IoT data name list saving step, which stores the received IoT data name list in a database (S130).

[0100] At this time, when the IoT server (300) receives a request for a list of names of IoT data from the metaverse management platform (100), it performs a response transmission step of transmitting a list of names of IoT data as a response to the request.

[0101] Next, in the metaverse management system (100), an IoT data name list request processing step is performed, which includes an IoT data name list display step (S135) for displaying an IoT data name list through a user interface in response to a user's request for an IoT data name list, and an IoT data name selection step (S140) for selecting at least one IoT data name with a label attached.

[0102] As previously stated, the concept of "user" here includes authors who create the metaverse or users who utilize the existing metaverse.

[0103] Next, in the metaverse management platform (100), a subscription request step is performed to request a subscription to the user's IoT data corresponding to the IoT data name with a specific label selected by the user (i.e., a metaverse authoring label or a name of IoT data with a label for metaverse reflection). (S145)

[0104] That is, the metaverse management platform (100) receives the IoT data as a notification whenever the user's IoT data is uploaded to the IoT server (300) through the subscription.

[0105] Next, the IoT server (300) sets up a subscription for the IoT data of the user in accordance with the subscription application, and performs a notification step (S150) of sending the IoT data of the user as a notification to the metaverse management system (100) whenever the IoT data of the user is uploaded.

[0106] Ultimately, IoT data further includes the user's identifier (ID).

[0107] Next, in the metaverse management system (100), when the user's IoT data is received from the IoT server (300) according to the subscription (S150), a parsing step is performed to parse the IoT data (S155).

[0108] The above parsing step is configured to parse the received IoT data and classify whether it is for metaverse authoring or metaverse reflection.

[0109] Next, in the metaverse management system (100), if the parsed result IoT data is a metaverse author, a metaverse author IoT data transmission step is performed to transmit the parsed IoT data to a metaverse author tool (400) (S160).

[0110] The above metaverse authoring IoT data transmission step transmits IoT data to the metaverse authoring tool via socket communication through the socket client (170).

[0111] Next, in the metaverse authoring tool (400), a metaverse authoring step is performed to author the metaverse using IoT data (S165).

[0112] The creation of the above metaverse has been explained with reference to FIGS. 1 and FIGS. 2, so it is omitted here.

[0113] FIG. 5 is a flowchart illustrating a procedure for transmitting a user's IoT data to a metaverse server through a metaverse management platform according to an embodiment of the present invention.

[0114] As illustrated in FIG. 5, the procedure for transmitting a user's IoT data to a metaverse authoring tool through a metaverse management platform according to one embodiment of the present invention first performs an IoT data generation step in which IoT data is generated from a plurality of IoT devices (200) (S205).

[0115] Next, an IoT data upload step (S210) is performed in which the IoT device (200) uploads the generated IoT data to the IoT server (300), and an IoT data storage step (S215) is performed in which the IoT server (300) stores the IoT data uploaded from the IoT device (200) in a database.

[0116] Next, in the metaverse management system (100), an IoT data name list request step (S220) is performed to request a list of names of IoT data with labels attached from an IoT server (300), an IoT data name list reception step (S225) is performed to receive a list of names of IoT data from the IoT server (300) in response to the request, and an IoT data name list storage step is performed to store the received list of names of IoT data in a database (S230).

[0117] Next, in the metaverse management system (100), an IoT data name list processing step is performed, which includes an IoT data name list display step (S235) for displaying an IoT data name list through a user interface in response to a user's request for an IoT data name list, and an IoT data name selection step (S240) for selecting at least one IoT data name with a label attached.

[0118] Next, in the metaverse management platform (100), a subscription request step is performed to request a subscription to the user's IoT data corresponding to the IoT data name with a specific label selected by the user (i.e., a metaverse authoring label or a name of IoT data with a label for metaverse reflection). (S245)

[0119] Next, the IoT server (300) sets up a subscription for the IoT data of the user in accordance with the subscription application, and performs a notification step (S250) of sending the IoT data of the user as a notification to the metaverse management system (100) whenever the IoT data of the user is uploaded.

[0120] Next, in the metaverse management system (100), when the user's IoT data is received from the IoT server (300) according to the subscription (S150), a parsing step is performed to parse the IoT data (S255).

[0121] The above parsing step is configured to parse the received IoT data and classify whether it is for metaverse authoring or metaverse reflection.

[0122] Steps S205 to S255 above are the same process as steps S105 to S155 described with reference to FIG. 4, so a detailed explanation will be omitted.

[0123] Next, in the metaverse management system (100), if the parsed result IoT data is a metaverse author, an API mapping step is performed to map the IoT data to the API of the metaverse (S260).

[0124] The above API mapping step involves mapping the relevant IoT data to an API for reflecting the IoT data in the metaverse. Since mapping the API has been explained with reference to FIG. 3, it will be omitted here.

[0125] Next, in the metaverse management system (100), an API mapping result transmission step is performed to transmit the API mapping result of the API mapping step to the metaverse (500) (S265).

[0126] Afterwards, when the metaverse server (400) receives an API mapping result, it performs a metaverse reflection step (S270) of reflecting IoT data (i.e., IoT data for metaverse reflection) into the metaverse using the received API mapping result.

[0127] FIG. 6 is a block diagram showing the hardware structure of a metaverse management platform according to one embodiment of the present invention.

[0128] As illustrated in FIG. 6, the hardware structure of a metaverse management platform (100) according to one embodiment of the present invention comprises a processor (1000), memory (2000), user interface (3000), database interface (4000), network interface (5000), and web server (6000).

[0129] The memory (2000) stores a program (application program) that performs a method for utilizing the metaverse management platform (100), and the processor (1000) is configured to execute the program to utilize the metaverse management platform (100).

[0130] The user interface (3000) provides input and output interfaces to the user by using a graphical user interface (GUI).

[0131] The database interface (4000) provides a storage interface between the database (300) and the hardware structure.

[0132] The network interface (5000) provides a network connection between a device owned by a user (i.e., a user terminal), an IoT server (300), a metaverse authoring tool (400), and a metaverse (500). The network interface (500) supports various types of network connections.

[0133] The web server (6000) provides a means for the user to access the metaverse management platform (100) via a network. Most users can access the metaverse management platform (100) remotely by connecting to the web server.

[0134] The configuration described above and the method of utilizing the metaverse management platform (100) through each configuration may be implemented as computer-readable code on a computer-readable recording medium or transmitted via a transmission medium. A computer-readable recording medium is a data storage device capable of storing data that can be read by a computer system. Examples of computer-readable recording media include, but are not limited to, databases, ROM, RAM, CD-ROM, DVD, magnetic tape, floppy disk, and optical data storage devices. The transmission medium may include a carrier wave transmitted via the Internet or various types of communication channels.

[0135] In addition, computer-readable recording media can be distributed through a networked computer system so that computer-readable code is stored and executed in a distributed manner.

[0136] In addition, at least one component applied to the present invention may include or be implemented by a processor (1000) that performs a respective function, and two or more of the components may be combined into a single component to perform all operations or functions for the two or more combined components. In addition, a part of the at least one component applied to the present invention may be performed by another component among these components. In addition, communication between the components may be performed via a bus (not shown).

[0137] Accordingly, the metaverse management platform (100) according to the present invention stores a program in memory (2000) that performs each processing step of an IoT-based metaverse management method, and is configured to include a processor (1000) configured to execute the program stored in the memory (2000).

[0138] As explained above, the present invention has the effect of effectively managing the metaverse by classifying the user's IoT data into IoT data for metaverse creation or metaverse reflection and transmitting it to a metaverse creation tool or metaverse server, thereby enabling the creation of the metaverse using the IoT data or the reflection of the IoT data in the metaverse.

[0139] Furthermore, although preferred embodiments of the present invention have been illustrated and described above, the present invention is not limited to the specific embodiments described above. It is understood that various modifications can be made by those skilled in the art without departing from the essence of the invention as claimed in the claims, and such modifications should not be understood individually from the technical spirit or perspective of the present invention. Explanation of the symbols

[0140] 100: Metaverse Management Platform 110: IoT Data Name List Request Section 120: IoT Data Name List Receiver 130: IoT Data Name List Processing Unit 140: Subscription Application Unit 150: IoT Data Receiving Unit 160: Parsing section 170: Socket client 180: API Mapping Section 190: Metaverse Client 200: IoT device 300: IoT server 400: Metaverse Authoring Tool 500: Metaverse Server

Claims

Claim 1 An IoT-based metaverse management platform comprising: an IoT data receiving unit that receives IoT data requested for subscription from an IoT server; and a parsing unit that parses the label of the received IoT data; wherein the parsing unit further comprises parsing the label to classify whether the received IoT data is for metaverse authoring or for metaverse reflection, and transmitting the received IoT data to a metaverse authoring tool if it is for metaverse authoring, and transmitting it to a metaverse server if it is for metaverse reflection; wherein the metaverse comprises at least one existing metaverse and at least one metaverse authoring tool for performing authoring, including creating or modifying a new metaverse; wherein the IoT data comprises teleport information for moving a user's character to a specific location in the metaverse, the user's emotional information, the user's biometric information, or a combination thereof; and wherein the IoT data is characterized by having a metaverse authoring label or a metaverse reflection label attached thereto that includes at least one label that is a distinguishing element. Claim 2 delete Claim 3 The IoT-based metaverse management platform according to claim 1 further comprises: an IoT data name list requesting unit that requests an IoT data name list from an IoT server; an IoT data name list receiving unit that receives the requested IoT data name list from the IoT server; an IoT data name list processing unit that displays the received IoT data name list according to a user's request and allows at least one IoT data name to be selected; and a subscription requesting unit that requests a subscription to the IoT server for IoT data corresponding to the selected at least one IoT data name; wherein each list item of the IoT data name list includes the name of the corresponding IoT data and the label of the corresponding IoT data, and the label includes at least one metaverse authoring label, at least one metaverse reflection label, or a combination thereof. Claim 4 The IoT-based metaverse management platform according to claim 1 further comprises: a socket client that transmits the parsed IoT data to a metaverse authoring tool via socket communication if, as a result of the parsing, the received IoT data is for metaverse authoring; an API mapping unit that maps the parsed IoT data to an API of the metaverse server if, as a result of the parsing, the received IoT data is for metaverse reflection; and a metaverse client that transmits the mapped result to the metaverse server. Claim 5 An IoT-based metaverse management method comprising: an IoT data receiving step for receiving IoT data requested for subscription from an IoT server in an IoT-based metaverse management platform; and a parsing step for parsing the label of the received IoT data in the IoT-based metaverse management platform; wherein the parsing step further comprises parsing the label to classify whether the received IoT data is for metaverse creation or for metaverse reflection, and transmitting the received IoT data to a metaverse creation tool if it is for metaverse creation, and transmitting it to a metaverse server if it is for metaverse reflection; wherein the metaverse includes at least one existing metaverse and at least one metaverse creation tool for performing creation, including creating or modifying a new metaverse; wherein the IoT data includes teleport information for moving a user's character to a specific location in the metaverse, the user's emotional information, the user's biometric information, or a combination thereof; and wherein the IoT data is characterized by having a metaverse creation label or a metaverse reflection label attached thereto that includes at least one label that is a distinguishing element. Claim 6 In claim 5, the IoT-based metaverse management method comprises: an IoT data name list request step in which, at least one IoT device in the IoT-based metaverse management platform generates IoT data and requests a name list of IoT data uploaded to an IoT server; an IoT data name list reception step in which, in the IoT-based metaverse management platform, the IoT data name list is received from the IoT server as a response to the request; an IoT data name list processing step in which, in the IoT-based metaverse management platform, the received IoT data name list is displayed or stored in a database; and a subscription request step in which, in the IoT-based metaverse management platform, the IoT server is requested to subscribe to IoT data corresponding to at least one name of IoT data selected by a user. The IoT-based metaverse management method further comprises: an IoT data receiving step in which the IoT data is received as a notification from the IoT server in accordance with a request for subscription in the IoT-based metaverse management platform; wherein each list item of the name list of the IoT data includes the name of the IoT data and the label of the IoT data, and the label includes at least one metaverse authoring label, at least one metaverse reflection label, or a combination thereof. Claim 7 The IoT-based metaverse management method according to claim 5 further comprises: a metaverse authoring IoT data transmission step in which, if the received IoT data is for metaverse authoring as a result of parsing in the IoT-based metaverse management platform, the parsed IoT data is transmitted from a socket client to a metaverse authoring tool via socket communication; an API mapping step in which, if the received IoT data is for metaverse reflection as a result of parsing in the IoT-based metaverse management platform, the parsed IoT data is mapped to an API of the metaverse server; and a metaverse reflection IoT data transmission step in which the mapped result is transmitted to a metaverse server via a metaverse client in the IoT-based metaverse management platform.

Images