KR20230163103A - Method for financial service based on product distribution data on metaverse and apparatus for performing the method - Google Patents

Abstract

The present invention relates to a financial service method based on product distribution data on the metaverse and a device for performing such method. A financial service method based on product distribution data on the metaverse may include the steps of a second metaverse implementation device providing a first-dimensional financial service and a second metaverse implementation device providing a second-dimensional financial service. You can.

Description

Financial service method based on product distribution data on metaverse and apparatus for performing the method {Method for financial service based on product distribution data on metaverse and apparatus for performing the method}

The present invention relates to a financial service method based on product distribution data on the metaverse and a device for performing such method. More specifically, it relates to a method for providing financial services based on product distribution data on the metaverse in order to provide metaverse-based product distribution services and financial services, and a device for performing this method.

The growth of major companies providing the Metaverse platform and content is continuing, and the related market is expanding, including increased investment and technology development and the launch of financial products.

Since its launch in 2018, Naver's metaverse platform Zepeto has had more than 200 million users. Roblox in the United States has gained great popularity as a gaming platform, with daily active users (DAU) reaching 46.6 million as of June 2021, an increase of 28% compared to July 2020.

Global big tech companies such as Facebook, Apple, and Microsoft are presenting investments and visions for technological innovation in the metaverse field and are actively pursuing team reorganization and acquisition of technology companies. In addition, interest in investment is increasing, with domestic and foreign financial companies launching various financial products such as metaverse-related funds, ETFs, and ETNs.

In the case of the financial industry, it is expected that the ability to transmit information and customer convenience will be improved through the metaverse, and the number of financial companies that provide services linked to the metaverse, such as VR (virtual reality) and AR (augmented reality), is increasing. .

As the scope of use of the metaverse expands due to the development of technology, the basis for various communication activities, including finance, can move from the mobile environment to the metaverse (virtual world). When a metaverse environment is established, the visual constraints of smartphone displays can be liberated, and communication methods can also expand from touch to voice or movement.

Financial companies can deliver more accurate and detailed information, and customers can conveniently use services without visiting a store. This metaverse technology can be used not only in the financial industry but also in distribution such as logistics. Metaverse technology enables more accurate and intuitive judgments about the distribution and status of products, and it is also possible to create new services by applying Metaverse to these various fields.

Related technology includes domestic application No. 10-2021-0116417.

The purpose of the present invention is to solve all of the above-mentioned problems.

Additionally, the present invention aims to provide a financial service method based on product distribution data on the metaverse.

Additionally, the purpose of the present invention is to provide financial services to sellers based on the value of pre-sale products that were previously not subject to financial services.

A representative configuration of the present invention to achieve the above object is as follows.

According to an embodiment of the present invention, a financial service method based on product distribution data on the metaverse includes the steps of a second metaverse implementation device providing a first-dimensional financial service and the second metaverse implementation device providing a second dimension financial service. It may include steps of providing dimensional financial services.

Meanwhile, the first dimensional financial service is a financial service based on first data generated by the first data processing server group, and the second dimensional financial service is a financial service based on first data generated by the first metaverse data processing server group. 1 It may be a financial service based on metaverse data.

In addition, the second-dimensional financial service can determine financial service limits and interest rates based on the results of the final collateral value evaluation considering the collateral value evaluation at each distribution stage based on product distribution data collected on the first metaverse. there is.

According to another embodiment of the present invention, a second metaverse implementation device that provides financial services based on product distribution data on the metaverse may be implemented to provide first-dimensional financial services and provide second-dimensional financial services. You can.

Meanwhile, the first dimensional financial service is a financial service based on first data generated by the first data processing server group, and the second dimensional financial service is a financial service based on first data generated by the first metaverse data processing server group. 1 It may be a financial service based on metaverse data.

In addition, the second-dimensional financial service can determine financial service limits and interest rates based on the results of the final collateral value evaluation considering the collateral value evaluation at each distribution stage based on product distribution data collected on the first metaverse. there is.

According to the present invention, a financial service method based on product distribution data on the metaverse can be provided.

Additionally, according to the present invention, financial services can be provided to sellers based on the value of pre-sale products that were previously not subject to financial services.

Figure 1 is a conceptual diagram showing a metaverse implementation system according to an embodiment of the present invention.
Figure 2 is a conceptual diagram showing a first metaverse implementation device according to an embodiment of the present invention.
Figure 3 is a conceptual diagram showing a second metaverse implementation device according to an embodiment of the present invention.
Figure 4 is a conceptual diagram showing a metaverse implementation method based on a plurality of servers included in the first data processing server group according to an embodiment of the present invention.
Figure 5 is a conceptual diagram showing a plurality of servers included in a second data processing server group according to an embodiment of the present invention.
Figure 6 is a conceptual diagram showing a data processing method on a blockchain according to an embodiment of the present invention.
Figure 7 is a conceptual diagram showing the operation of the metaverse data processing unit according to an embodiment of the present invention.
Figure 8 is a conceptual diagram showing the operation for linking between metaverses according to an embodiment of the present invention.
Figure 9 is a conceptual diagram showing a method for generating and managing product distribution data according to an embodiment of the present invention.
Figure 10 is a conceptual diagram showing a method for managing product distribution data on a blockchain according to an embodiment of the present invention.
Figure 11 is a conceptual diagram showing a method for managing product data on a blockchain according to an embodiment of the present invention.
Figure 12 is a conceptual diagram showing a financial service method based on product distribution data on the metaverse according to an embodiment of the present invention.
Figure 13 is a conceptual diagram showing a second-dimensional financial service according to an embodiment of the present invention.
Figure 14 is a conceptual diagram showing a token-based transaction method on the metaverse according to an embodiment of the present invention.

The detailed description of the present invention described below refers to the accompanying drawings, which show by way of example specific embodiments in which the present invention may be practiced. These embodiments are described in sufficient detail to enable those skilled in the art to practice the invention. It should be understood that the various embodiments of the present invention are different from one another but are not necessarily mutually exclusive. For example, specific shapes, structures and characteristics described herein may be implemented with changes from one embodiment to another without departing from the spirit and scope of the invention. Additionally, it should be understood that the location or arrangement of individual components within each embodiment may be changed without departing from the spirit and scope of the present invention. Accordingly, the detailed description described below is not intended to be limited, and the scope of the present invention should be taken to encompass the scope claimed by the claims and all equivalents thereof. Like reference numbers in the drawings indicate identical or similar elements throughout various aspects.

Hereinafter, several preferred embodiments of the present invention will be described in detail with reference to the attached drawings in order to enable those skilled in the art to easily practice the present invention.

Figure 1 is a conceptual diagram showing a metaverse implementation system according to an embodiment of the present invention.

In Figure 1, a metaverse implementation system for implementing supply chain services and financial services on the metaverse is disclosed.

Referring to FIG. 1, the metaverse implementation system includes a first metaverse implementation device 110, a second metaverse implementation device 120, an inter-metaverse interlocking network implementation device 150, a supply chain service device 130, and May include a financial service device 140.

The first metaverse implementation device 110 may be implemented for a metaverse related to supply chain services. The metaverse related to supply chain services can be expressed in terms of the first metaverse 116. The first metaverse 116 is linked to the first blockchain network 113, and processing of some data can be performed based on the first blockchain network 113.

The second metaverse implementation device 120 may be implemented for a metaverse related to financial services. The metaverse related to financial services can be expressed in terms of the second metaverse 126. The second metaverse 126 is linked to the second blockchain network 123, and processing of some data may be performed based on the second blockchain network 123.

The inter-metaverse interconnection network implementation device 150 may be implemented for interconnection between the first metaverse 116 and the second metaverse 126. Interconnection between metaverses involves a process on the second metaverse 126 based on the first metaverse data generated in the first metaverse 116 and the second metaverse data generated in the second metaverse 126. It can be performed for a process on the first metaverse 116 based on it. The device 150 for implementing interconnection networks between metaverses can define a separate third blockchain network 155 for interconnection between metaverses.

The supply chain service device 130 is a device that provides supply chain-based services. The supply chain service device 130 can generate product distribution data generated on the supply chain. Supply chain data can generate product distribution actions on the first metaverse 116 and change the metaverse environment. Additionally, at least one piece of supply chain data may be recorded on the first blockchain network 113.

The financial service device 140 is a device that provides financial services. The financial service device 140 may generate financial service data generated from financial services. Financial service data can generate financial actions on the second metaverse 126 and change the metaverse environment. Additionally, at least one piece of financial service data may be recorded on the second blockchain network 123.

Figure 2 is a conceptual diagram showing a first metaverse implementation device according to an embodiment of the present invention.

In Figure 2, a first metaverse implementation device for implementing a metaverse related to supply chain services is disclosed.

Referring to FIG. 2, the first metaverse implementation device includes a first data processing server group 210, a first metaverse data processing server group 220, a first metaverse data processing unit 230, and a first blockchain network. It may include 240 and a first metaverse environment implementation unit 250.

The first data processing server group 210 may include a data processing server that processes supply chain data generated on the supply chain service. Supply chain services provide services related to product distribution such as production, sales, storage, distribution, and purchasing of products, and can collect and process supply chain data, which is data generated during product distribution.

A plurality of data processing servers included in the first data processing server group 210 may be layered, and data of the data processing servers collected for each layer may be selectively utilized to implement a metaverse. The first metaverse environment implementation unit 250 may implement a supply chain service on the metaverse based on data generated by at least one data processing server located in each layer.

Hereinafter, for convenience of explanation, data generated in the first data processing server group 210 is expressed as first data.

The first metaverse data processing server group 220 may be implemented to process necessary data on the metaverse. The first metaverse data processing server group 220 may process the first data generated by the first data processing server group 210 to generate first metaverse data.

Each of the plurality of metaverse data processing servers included in the first metaverse data processing server group 220 may be linked with each of the plurality of data processing servers included in the first data processing server group 210. Each of the plurality of data processing servers transmits data to each of the plurality of linked metaverse data processing servers, and each of the plurality of metaverse data processing servers processes the received data to generate first metaverse data.

The first metaverse data generated in the first metaverse data processing server group 220 may be transmitted to the first metaverse data processing unit 230.

The first metaverse data processing unit 230 receives the first metaverse data and processes the first metaverse data into the first blockchain network 240 and the first metaverse environment implementation unit 250. data can be transmitted. Specifically, the first metaverse data processing unit 230 classifies the first metaverse data into data to be recorded on the first blockchain network 240 and data to be recorded in the first metaverse environment implementation unit 250. can do.

After classification of the first metaverse data, the processed data can be transmitted in real time or periodically to the first blockchain network 240 and the first metaverse environment implementation unit 250.

The first blockchain network 240 may be implemented to receive first metaverse data and record the first metaverse data on the blockchain. The first blockchain network includes a smart contract for processing the first metaverse data, and can implement the metaverse environment by processing the first metaverse data based on the stored smart contract.

The first metaverse environment implementation unit 250 may implement the first metaverse environment based on the first metaverse data. The first metaverse environment may be an environment on the metaverse corresponding to the supply chain. The first metaverse environment may include a commonly implemented first common metaverse environment, an individual user, and a first individual metaverse environment for an individual user group. Through the first metaverse environment, users can confirm in the metaverse space that supply chain services for products are provided, and expansion to other services (for example, financial services) based on the supply chain confirmed on the metaverse is possible. It can be done.

Figure 3 is a conceptual diagram showing a second metaverse implementation device according to an embodiment of the present invention.

In Figure 3, a second metaverse implementation device for implementing a metaverse related to financial services is disclosed.

Referring to FIG. 3, the second metaverse implementation device includes a second data processing server group 310, a second metaverse data processing server group 320, a second metaverse data processing unit 330, and a second blockchain network. It may include 340 and a second metaverse environment implementation unit 350.

The second data processing server group 310 may include a data processing server that processes data generated on financial services. Financial services include financial-related services such as loans, interest rates, repayments, investments, deposits, etc., and can collect and process financial data, which is data generated from financial services.

A plurality of data processing servers included in the second data processing server group 310 may be layered, and data of the data processing servers collected for each layer may be selectively utilized to implement a metaverse. The second metaverse environment implementation unit 350 may implement financial services on the metaverse based on data generated by at least one data processing server located in each layer.

Hereinafter, for convenience of explanation, data generated in the second data processing server group 310 is expressed as second data.

There is a network between the above-described first data processing server group and the second data processing server group 310, and mutual exchange of data will occur on the network between the first data processing server group and the second data processing server group 310. You can. For example, when interaction occurs between the first metaverse environment and the second metaverse environment, mutual exchange of data may occur between the first metaverse environment and the second metaverse environment. The exchanged data can be delivered in a separate format to a device that implements an inter-metaverse interconnection network to enable interaction between metaverses.

The second metaverse data processing server group 320 may be implemented to process necessary data on the metaverse. The second metaverse data processing server group 320 may process the second data generated by the second data processing server group 310 to generate second metaverse data.

Each of the plurality of metaverse data processing servers included in the second metaverse data processing server group 320 may be linked with each of the plurality of data processing servers included in the second data processing server group 310. Each of the plurality of data processing servers transmits data to each of the plurality of linked metaverse data processing servers, and each of the plurality of metaverse data processing servers processes the received data to generate second metaverse data.

The second metaverse data generated in the second metaverse data processing server group 320 may be transmitted to the second metaverse data processing unit 330.

The second metaverse data processing unit 330 receives the second metaverse data and processes the second metaverse data into the second blockchain network 340 and the second metaverse environment implementation unit 350. data can be transmitted. Specifically, the second metaverse data processing unit 330 classifies the second metaverse data into data to be recorded on the second blockchain network 340 and data to be recorded in the second metaverse environment implementation unit 350. can do.

After classification of the second metaverse data, the processed data in real time or periodically may be transmitted to the second blockchain network 340 and the second metaverse environment implementation unit 350.

The second blockchain network 340 may be implemented to receive second metaverse data and record the second metaverse data on the blockchain. The second blockchain network 340 includes a smart contract for processing second metaverse data, and can implement a metaverse environment by processing the second metaverse data based on the stored smart contract.

The second metaverse environment implementation unit 350 may implement the metaverse environment based on the second metaverse data. The second metaverse environment may be an environment on the metaverse corresponding to financial services. The second metaverse environment may include a commonly implemented second common metaverse environment, an individual user, and a second individual metaverse environment for individual user groups. Through the second metaverse environment, users can confirm in the metaverse space that financial services are being performed, and expansion to other services (for example, supply chain services) based on financial services confirmed on the metaverse can be made. .

Figure 4 is a conceptual diagram showing a metaverse implementation method based on a plurality of servers included in the first data processing server group according to an embodiment of the present invention.

In Figure 4, a layering operation of a first data processing server group to implement a metaverse based on a supply chain service is initiated.

Referring to FIG. 4, the first data processing server group for the supply chain service may be first stratified 400 into first to nth layers from the lower layer to the upper layer.

The plurality of data processing servers may be servers that collect supply chain data occurring on the supply chain, and the hierarchy of the plurality of data processing servers may be determined by considering the occurrence of data on the supply chain. In a supply chain, activities such as production, sales, storage, distribution, and purchasing can occur sequentially. These actions on the supply chain can be accomplished by passing data from the lower layer to the upper layer. For example, the first layer 410 is a production layer, the second layer 420 is a sales layer, the third layer 430 is a storage layer, the fourth layer 440 is a distribution layer, and the fifth layer 450 is set as a purchasing layer, and the process from when a product is produced to being delivered to the buyer through the sales process can be stratified.

Production, sales, storage, distribution, and purchasing are examples of activities that occur in the supply chain, and activities that occur in the supply chain can be defined in various other service stages.

A plurality of data processing servers within the same layer may be reclassified by metaverse environment or may be secondary layered (460). For example, the metaverse environment has various dimensions, such as metaverse 1 (470) for seller A, metaverse 2 (480) for seller group A including seller A, and metaverse 3 (490) for all sellers. It can be implemented as: Alternatively, the metaverse environment may be implemented in various dimensions, such as metaverse 4 for product A that is not the seller, metaverse 5 for product group A including product A, and metaverse 6 for all products.

The metaverse environment can be implemented in various ways depending on the variables (e.g., seller, product) and variable settings (single variable, group of variables, all variables, etc.) that implement the metaverse environment, and in order to implement the metaverse environment, Data processing servers of the same layer may be reclassified and secondary layered (460).

A method for implementing metaverse 1 and metaverse 2 for seller A and seller group A, respectively, is disclosed as an example.

(1) Metaverse 1(470)

Data processing servers related to seller a may be classified and grouped. When Seller A sells products through Coupang or Naver Smart Store, data processing server 1 corresponding to Coupang and data processing server 2 corresponding to Naver Smart Store are classified as data processing servers for implementing Metaverse 1 (470). can be grouped.

The first data 475 generated corresponding to the seller in each of Server 1 and Server 2 may be collected from the first data processing server group and transmitted to the first metaverse data processing server group. First metaverse data for creating metaverse 1 (470) is generated in the first metaverse data processing server group, and the first metaverse data may be transmitted to the first metaverse data processing unit.

(2) Metaverse 2 (480)

Servers related to seller group a may be classified and grouped. A seller group with similar sales characteristics to seller A may be seller group A. Seller Group A can sell products on various platforms (Coupang, Naver Smart Store, 11th Street, G Market, etc.). Each of a plurality of servers corresponding to various platforms may be classified and grouped as servers for implementing Metaverse 2 (480).

Metaverse 2 (480) is a structure that includes Metaverse 1 (470), and at least one server for Metaverse 1 (470) may be included within a plurality of servers for Metaverse 2 (480) or may exist in a layered manner. . At least one server that collects data for each of Seller A, Seller A1, Seller A2,??, and Seller A3 included in Seller Group A may be layered to form a server that collects data corresponding to Seller Group A.

Likewise, first data generated corresponding to seller group A may be collected from the first data processing server group and transmitted to the first metaverse data processing server group. First metaverse data for creating metaverse 2 480 is generated in the first metaverse data processing server group, and the first metaverse data may be transmitted to the first metaverse data processing unit.

In this way, data processing servers are layered or grouped according to settings, so that the metaverse environment for individual sellers, individual seller groups, individual products, product groups, etc. can be adaptively implemented as needed.

According to an embodiment of the present invention, data transmission can be performed considering the metaverse structure for efficient processing of data. For example, the first data for metaverse 1 may be the first data for metaverse 2 and metaverse 3, which include metaverse 1 at the same time. Additionally, the first data for Metaverse 2 may be the first data for Metaverse 3 including Metaverse 2. Therefore, in order to prevent duplicate processing of data, selective transmission can be performed considering the relationship between metaverses based on the first layer header and the second layer header included in the header of the generated first data. The relationship between metaverses can be determined based on the first layer header and the second layer header, and metaverse data can be classified and transmitted to the metaverse environment implementation unit based on the first layer header and the second layer header.

Figure 5 is a conceptual diagram showing a plurality of servers included in a second data processing server group according to an embodiment of the present invention.

In Figure 5, the layering operation of the second data processing server group for providing financial services is initiated.

Referring to FIG. 5, the second data processing server group 555 for financial services may be primarily stratified 500 into first to nth layers from the lower layer to the upper layer.

The plurality of servers may be data processing servers that collect financial service data generated on financial services, and the hierarchy of the plurality of servers may be determined by considering the generation of data on financial services. In financial services, activities such as lending, repayment (interest, principal), and delinquency may occur sequentially. These financial service activities can be performed by transferring data from the lower layer to the upper layer. For example, the first layer is set as the loan layer 510, the second layer is set as the repayment layer 520, and the third layer is set as the delinquency layer 530, so that the process of providing and completing financial services can be layered. .

Loan, repayment, and delinquency are examples of actions that occur in financial services, and actions that occur in financial services may be defined by various other service stages.

Multiple servers within the same layer may be reclassified by metaverse environment or may be secondary layered (560). Like the supply chain service, the metaverse environment is diverse, such as metaverse 1 (570) for seller A, metaverse 2 (580) for seller group A including seller A, and metaverse 3 (590) for all sellers. It can be implemented dimensionally.

Financial services are provided to individual sellers, but in order to determine the financial services provided to individual sellers, the characteristics of the seller group in which the seller is included and the characteristics of all sellers may be reflected. For example, Seller A may be a seller selling women's clothes, and Seller Group A may be a seller group including a plurality of sellers selling women's clothes.

In order to provide financial services to Seller A, not only must supply chain data for Seller A be collected, but supply chain data for Seller Group A may also need to be collected.

Therefore, the server for financial services can collect supply chain data in connection with the server layer for supply chain services and provide financial services based on the supply chain data. A plurality of servers included in the second data processing server group 555 may be linked with a plurality of servers included in the first data processing server group 550 to provide financial services.

In this way, the second data processing server group 555 is subordinate to the first data processing server group 550 and receives not only financial service data, but also supply chain data for financial services to generate second data 575. You can.

The second data 575 is transmitted to the second metaverse data processing server group, and the second metaverse data processing server group generates metaverse 1 (570), metaverse 2 (580), and metaverse 3 (590). Second metaverse data may be created to do this. The second metaverse data may be transmitted to the second metaverse data processing unit.

Figure 6 is a conceptual diagram showing metaverse data generation according to an embodiment of the present invention.

In Figure 6, the metaverse data generation operation of the metaverse data processing server group is initiated.

Referring to FIG. 6, the metaverse data processing server group can generate metaverse data to be transmitted to the metaverse data processing unit from among the received data.

Metaverse data can be created by adding metaverse header information to the received data according to settings at the time of creation.

The header 600 of metaverse data may include first and second layer information of the data processing server group, seller information, and product information.

The first layer information is layered information based on the above-described first layering and may include information about the first layer that generated the data.

The secondary layer information is layered information based on the above-described secondary layering and may include information about the secondary layer that generated the data.

Seller information may include information for classifying sellers who sell products and receive financial services on the supply chain.

Product information may include information for classifying products that are distributed and sold on the supply chain and are the basis of financial services.

The metaverse can be implemented based on various variables (seller, product, etc.), and a header 600 of metaverse data can be added to provide a metaverse environment that takes various variables into account.

The header 600 may include a first layer header 610, a second layer header 620, a product header 630, and a seller header 660, and the product header 630 and seller header 650, respectively. Can be divided into standard headers 640 and 670 and individual headers 650 and 680.

Each of the standard header 640 and individual header 650 of the product header 630 can be set to n header levels.

The standard header 640 may include n header levels for product classification defined as a standard for integration on different metaverses. The individual header 650 may include n header levels for individually defined product classification to manage only a specific metaverse. Based on the standard header 640, a plurality of different supply chains and financial services can be integrated and implemented as a metaverse, but individual supply chains and individual financial services can be implemented adaptively as needed. Header 650 may be defined.

The n header levels of each of the standard header 640 and the individual header 650 of the product header 630 have a hierarchical structure, and each of the n header levels can have a higher concept as it is set to a higher layer. For example, the first header level of the standard header 640 may be set to include products such as pencils at the second header level, stationery at the second header level, and industrial products at higher levels. The n header levels corresponding to the product header may change depending on settings, and changes in the header may occur according to these changes.

Similarly, each of the standard header 670 and the individual header 680 of the seller header 660 can be set to m header levels. The m header levels of the standard header 670 and the individual header 680 of the seller header 660 have a hierarchical structure, and each of the m header levels can have a higher concept as it is set to a higher layer. For example, the first header level of the standard header 670 includes seller A, the second header level includes the first seller group, the third header level includes the second seller group, etc. It can be set as a concept. The m header levels corresponding to the seller header 660 may change depending on settings, and header changes may occur according to these changes.

Header levels that are not set for the product header 630 and seller header 660 can be left blank without separate settings, if necessary.

Additionally, according to an embodiment of the present invention, the standard headers 640 and 670 may be adjusted based on the use of the individual headers in relation to the standard headers 640 and 670 and the individual headers 650 and 680. For example, by considering individual headers (650, 680) used in a specific metaverse, information on the level of actually commonly used headers is reflected, so that standard headers (640, 670) can be adjusted to better fit the actual business classification. It may be possible. Additionally, in the case of the header, considering the metaverse implementation environment, a separate metaverse header may be additionally defined only for a specific metaverse environment and used separately for implementation of the metaverse only.

Figure 7 is a conceptual diagram showing the operation of the metaverse data processing unit according to an embodiment of the present invention.

In Figure 7, the metaverse data processing operation of the metaverse data processing unit is initiated.

Referring to FIG. 7, the metaverse data processing unit can receive metaverse data and transmit the processed data to the blockchain network and metaverse environment implementation unit through processing of the metaverse data.

The Metaverse data processing department can classify Metaverse data into data to be recorded on the blockchain network and data to be recorded in the Metaverse environment implementation department.

The metaverse data processing unit may perform primary filtering (710) based on header information. First, considering the currently implemented metaverse environment, metaverse data that is not necessary for implementing the current metaverse environment can be removed. For example, if there is no separate request for a metaverse environment for seller B and product X, metaverse data for seller B and product X may be filtered.

After the first filtering (710), the metaverse data processing unit can transmit the metaverse data to the metaverse environment implementation unit through metaverse data classification. For example, if the metaverse for Seller A and Seller Group A must be implemented, metaverse data corresponding to Seller A and Seller Group A must be classified through header filtering and transmitted to the Metaverse Environment Implementation Unit 730. You can.

The Metaverse data processing unit can generate a hash value by grouping the Metaverse data for recording on the blockchain and store the generated hash value on the blockchain network 740. In the present invention, time units are set for each metaverse, and hash values for metaverse data collected for each time unit can be recorded on the blockchain network 740.

For example, a first time unit for seller A and a second time unit for seller group A may be set. Metaverse data for Seller A generated on the first time unit may be grouped and generated as a hash value along with Seller A's identification information. The generated hash value may be stored on the blockchain network 740. Likewise, the metaverse data for seller group A generated on the second time unit may be grouped and generated as a hash value along with the identification information of seller group A. The generated hash value may be stored on the blockchain network 740. The first time unit and the second time unit can be adjusted based on the creation rate of metaverse data. The faster the metaverse data creation rate, the shorter the time unit can be set.

In addition, according to an embodiment of the present invention, metaverse data (time), which is time-critical data among metaverse data, is not grouped by time and can be preferentially stored on the blockchain network. For example, among supply chain data, data on products with an expiration date is not grouped by time, but can be stored on the blockchain as soon as it is generated. Additionally, time-critical metaverse data related to financial services, such as loan timing, repayment timing, and delinquency timing, can be recorded directly on the blockchain without considering time units.

Figure 8 is a conceptual diagram showing the operation for linking between metaverses according to an embodiment of the present invention.

In Figure 8, an operation for linking between a first metaverse based on supply chain services and a second metaverse based on financial services is initiated.

Referring to FIG. 8, the first metaverse data generated based on the supply chain service may be processed by the first metaverse data processing unit and transmitted to the first blockchain network and the first metaverse environment implementation unit.

The second metaverse data generated based on financial services may be processed by the second metaverse data processing unit and transmitted to the second blockchain network and the second metaverse environment implementation unit.

In the present invention, some second data may be determined based on the first data, and some first metaverse data and some second metaverse data may have a dependent relationship. For example, financial services that take supply chain data into account may be provided, and metaverse data may be created due to these financial services.

The first metaverse data, the second metaverse data, and the interdependency subject information (e.g., seller A, seller group A, product . The interdependency subject information may be information about the subject that generated the first metaverse data and the second metaverse data that have mutual dependency.

The inter-metaverse interconnection network implementation device 800 stores first metaverse data, second metaverse data, and interdependency subject information having interdependence, and first metaverse data and second metaverse data related to the interdependency subject. Data can be processed and stored in a third blockchain network 810.

The first metaverse data is data related to supply chain services, so it is generated continuously, and the second metaverse data is data related to financial services, so it may be generated more intermittently than the first metaverse data. Accordingly, the first metaverse data may be periodically grouped and stored on the third blockchain network 810 as a first format hash value. When the second metaverse data is generated, a second format hash value combining the first format hash value of each of the existing grouped first metaverse data and the second metaverse data is generated, and the third blockchain network (810) ) can be stored on

Through this operation, when financial services are provided based on specific supply chain data, tracking of changes in supply chain data and financial services is possible on the metaverse, and data can also be verified on the blockchain. In this way, interaction between the first metaverse environment and the second metaverse environment is possible.

Figure 9 is a conceptual diagram showing a method for generating and managing product distribution data according to an embodiment of the present invention.

In Figure 9, a method for generating and managing product distribution data is disclosed.

Referring to FIG. 9, product distribution data may be generated differently depending on the type of product in order to track the movement of the product along the distribution path. A product that requires identification of individual products may be a first type product 910, and a product that does not require identification of individual products may be a second type product 920. The first type product 910 may be created based on a non-fungible token (NFT) and managed as an NFT, and the second type product 920 may be created based on a fungible token (FT) and managed as an FT. Expensive products or products requiring specification may be defined and managed as first type products 910, and other products may be defined and managed as second type products 920.

For example, a TV with serial number XXXXXX is defined as a first type product 910, and one NFT corresponding to a TV with serial number XXXXXX can be issued. 1000 pencils are defined as a second type product 920, so 1000 FTs corresponding to the pencils can be issued.

In order to manage product distribution data such as product production data (955), product storage data (965), and product sales data (975) on the blockchain, product production address (950) corresponding to product production, product corresponding to product storage There may be a storage address 960 and a product sales address 970 corresponding to product sales. Based on the movement of NFTs and FTs corresponding to products on the blockchain, operations corresponding to the production, sale, and distribution of products in the metaverse can be confirmed.

Product production data 355, product storage data 365, and product sales data 975 corresponding to NFT and FT are generated in the data processing server group or the first metaverse data processing server group and are stored as first metaverse data. 1 Can be used to implement a metaverse environment.

Figure 10 is a conceptual diagram showing a method for managing product distribution data on a blockchain according to an embodiment of the present invention.

In Figure 10, a method of processing NFT-based product distribution data of a first type product is disclosed.

Referring to Figure 10, management of NFT and product distribution data based on blockchain during product production, product storage, and product sales is initiated.

(1) Product production procedure (type 1 product) (1010)

When producing a product, an NFT for the product can be created at the product production address. An NFT for the product is created, and the NFT can be matched with product production data. NFT and product production data are created with a first hash value (1015), and the first hash value (1015) can be recorded on the blockchain.

(2) Product storage procedures (type 1 product) (1020)

When storing a product, the NFT for the product can be sent to the product storage address. When the NFT is moved to the product storage address, the NFT can be matched with the product storage data. NFT and product storage data are generated as a second hash value (1025), and the second hash value (1025) can be recorded on the blockchain.

(3) Product sales procedure (type 1 product) (1030)

When selling a product, the NFT for the product can be sent to the product sales address. When an NFT is moved to a product sales address, the NFT can be matched with product sales data. NFT and product sales data are generated as a third hash value 1035, and the third hash value 1035 can be recorded on the blockchain.

The product production address, product storage address, and product sales address may be wallet addresses that generate transactions on the blockchain. Based on the movement and hash value of the NFT for the product, the movement of the first type of product on the supply chain is tracked, and the movement of the product on the supply chain can be confirmed on the metaverse.

This method can be expressed in terms of a single NFT product distribution data management method.

In another method, a hash value may not be generated, and an NFT may be created based on product production data, product storage data, and product sales data in each of the product production procedure, product storage procedure, and product sales procedure.

More specifically, at the product production stage, NFT (product production) can be created based on product production data. In the product storage stage, NFT (product storage) can be created based on product storage data and NFT (product production). At the product sales stage, NFTs (product sales) can be created based on product sales data and NFTs (product storage).

This method can be expressed in terms of a step-by-step NFT product distribution data management method.

If continuous management of NFT-based product distribution data is required outside of a single supply chain-based metaverse, a single NFT product distribution data management method can be used. If management of product distribution data is required only in one supply chain-based metaverse, a step-by-step NFT product distribution data management method can be used.

Figure 11 is a conceptual diagram showing a method for managing product data on a blockchain according to an embodiment of the present invention.

In Figure 11, a FT-based trading method for a second type product is disclosed.

Referring to Figure 11, management of FT and product distribution data based on blockchain during product production, product storage, and product sales is initiated.

(1) Product production procedure (second type product) (1110)

When producing a product, a FT for the product may be created at the product production address. For example, if there are 1000 shampoos, 1000 FTs can be created. FT can be matched with product production data. FT, number of FTs, and product production data are generated as a first hash value, and the first hash value 1150 can be recorded on the blockchain.

(2) Product storage procedures (type 2 products) (1120)

When storing a product, FT for the product can be sent to the product storage address. A plurality of FTs may be stored in different storage locations, and when the storage location changes, different storage data may be generated or transmitted to different product storage addresses to reflect changes in product storage.

For example, 1000 shampoos may be created with 1000 FTs, 500 shampoos may be stored in a first storage location, and the remaining 500 shampoos may be stored in a second storage location.

In this case, 500 FTs may be transmitted to the first product storage address, and first product storage data may be generated. The remaining 500 FTs are sent to the second product storage address, and second product storage data can be generated.

(500 FTs, first product storage address, first product storage data) generates the second hash value (1160), and (500 FTs, second product storage address, second product storage data) generates the third hash A value (1170) can be generated. The second hash value 1160 and the third hash value 1170 can be recorded on the blockchain.

(3) Product sales procedure (second type product) (1130)

When selling a product, the FT for the product can be sent to the product sales address. Similar to the product storage procedure, each of the 1000 FTs is moved to the product sales address according to the shipment quantity, and when the FT corresponding to the sales quantity is moved, the FT can be matched with product sales data. FT of the sales quantity sold and product sales data are generated as a fourth hash value 1180, and the fourth hash value 1180 can be recorded on the blockchain.

The product production address, product storage address, and product sales address may be wallet addresses that generate transactions on the blockchain. Based on the FT movement and hash value for the product, the movement of the second type product is tracked in the supply chain and metaverse, and users can accurately check the movement of the product on the metaverse.

For FT-based products, only a single FT product management method can be used.

The processing of the above NFT or FT-based product production data, product storage data, and product sales data is performed by the first metaverse data processing group of the first metaverse implementation device, and NFT or FTized product production data and product storage are performed by the first metaverse data processing group. Data and product sales data can be used to implement a metaverse environment.

Additionally, according to an embodiment of the present invention, the block creation time on the blockchain can be adjusted to implement a metaverse environment based on FT and NFT data.

The blockchain for processing product distribution data of the present invention can adaptively adjust the block creation time by considering the time when product distribution data is generated and the time when product distribution data is not generated. In addition, the transaction amount for product distribution data can be additionally considered and the block creation time can be relatively adjusted by taking into account the characteristics of the product (for example, fresh food) for which product distribution data must be generated immediately.

The blockchain data processing device (or blockchain data processing unit) can determine the expected block creation time based on the block creation time that changes adaptively as above. To generate blocks on a blockchain, a blockchain data processing device may include a plurality of block generation consensus nodes. In the present invention, records of transactions occurring on the blockchain are collected for each time zone, and block creation times can be adaptively determined for each time zone based on the transaction records.

Transactions can be classified into two types. The first type of transaction is a transaction in which block creation time is important and may include, for example, transactions related to product receipt and product shipment. The second type of transaction is a transaction in which block creation time is not important and may include, for example, a transaction related to product storage or a transaction for determining the appropriate price of a product.

The block creation time determination device can determine the block creation time based on the transaction that occurs. The block creation time determination device may filter the second type transaction, extract the first type transaction, and perform learning to determine the block creation time for block creation.

First, product distribution data creation time (or product receipt, storage, and shipment time) and product distribution data non-generation time (or time when product receipt, storage, and shipment do not occur) are distinguished, and transaction time is hierarchically divided into Learning about the transaction volume that occurs over time can be performed by dividing it into:

The block creation time determination device may perform learning to determine the block creation time based on the first type transaction and the block creation time when the first type transaction occurs.

For learning to determine the block creation time, the first type transaction may include product distribution data creation time information and time layer information regarding whether it is a product distribution data creation time or a non-product distribution data creation time. Time layer information is information that stratifies time units and can be used to stratify time units to perform block generation considering the time sensitivity of the block creation time.

The first time layer is the smallest time unit and may be in seconds, the second time layer may be in minutes, and the third time layer may be in hours. Through the setup of these time layers, learning about block creation times based on sensitivity in seconds, learning about block creation times based on sensitivity in minutes, and learning about block creation times based on sensitivity in hours are performed. It can be.

The block creation time determination device can set time sensitivity (sensitivity in seconds, sensitivity in minutes, sensitivity in hours) and generate blocks so that the block creation time is less than or equal to the critical block creation time based on the learned results. For example, if the device for determining the block creation time sets the time sensitivity to a sensitivity in seconds, a block can be created with the sensitivity in seconds so that the block creation time is less than or equal to the critical block creation time.

Figure 12 is a conceptual diagram showing a financial service method based on product distribution data on the metaverse according to an embodiment of the present invention.

In Figure 12, a method for providing financial services to sellers of products based on product distribution data on the metaverse is disclosed.

Referring to FIG. 12, financial services on the second metaverse 1220 may be provided based on two dimensions based on data before being converted to metaverse data. In the first-dimensional financial service 1200, second data 1225 is generated based on first data 1215, and financial services on the second metaverse 1220 are based on the second data 1225. can be provided. The second-dimensional financial service 1250 may provide a financial service on the second metaverse 1220 based on the first metaverse data 1260 on the first metaverse 1210.

(1) First dimension financial services (1200)

The first dimensional financial service 1200 may be a financial service based on the first data 1215 generated by the first data processing server group, as described above with reference to FIG. 5 . By receiving the first data 1215, the second data processing server group for financial services receives the accounts receivable from sales, as well as the first tier (production tier) and the second tier (sales tier) of the first data processing server group. , financial services can be provided based on the first data 1215 generated on the third layer (storage layer) and the fourth layer (distribution layer).

For example, the first data 1215 generated in the first layer (production layer) is collected by the second data processing server group to provide financial services, and loan data and repayment data that are financial service data according to the financial service. , overdue data may be generated as second data 1225. The second data 1225 can be converted into second metaverse data and used to implement the second metaverse 1220.

The first-dimensional financial service 1200 may be a method in which actual financial services are generated in a non-metaverse space, and financial services generated in a non-metaverse space are provided and expressed on the second metaverse 1220.

(2) Second-dimensional financial services (1250)

The second-dimensional financial service 1250 may provide financial services on the second metaverse 1220 by directly utilizing the first metaverse data 1260 generated by the first metaverse data processing server group. The second-dimensional financial service 1250 provides financial services on the second metaverse 1220 based on product distribution data, which is the first metaverse data 1260 generated on the first metaverse 1210, and the second This is how metaverse data 1270 is generated. That is, the second-dimensional financial service 1250 may be a financial service provided on the metaverse based on information generated in the metaverse.

In the second-dimensional financial service 1250, transactions can be performed based on tokens negotiable in the metaverse, and loans can be made for fiat currency based on tokens negotiable in the metaverse. That is, loans for tokens are made based on digitized assets or distribution data on the metaverse on the first metaverse (1210), and loans of fiat currency and fiat currency collateralized by tokens are made on the second metaverse (1220). repayment can be made.

The second-dimensional financial service 1250 will be described in detail later.

In the present invention, the first-dimensional financial service 1200 and the second-dimensional financial service 1250 can be provided simultaneously. The first dimensional financial service 1200 and the second dimensional financial service 1250 are divided into basic assets and data for the first dimensional financial service 1200 and basic assets and data for the second dimensional financial service 1250 so as not to overlap. can be processed to avoid duplication.

To this end, the first data used for first-dimensional financial services can be managed by adding a tag indicating that it is used data, and when converted to first metaverse data for second-dimensional financial services, the first data used for first-dimensional financial services can be managed. It can be converted by adding a tag indicating that it is data used for . Therefore, filtering is performed based on these tags, and the filtered first metaverse data may not be used as direct data for second-dimensional financial services.

Figure 13 is a conceptual diagram showing a second-dimensional financial service according to an embodiment of the present invention.

In Figure 13, a method for providing token-based second-dimensional financial services in the second metaverse is disclosed.

Referring to FIG. 13, the second-dimensional financial service can receive product distribution data generated on the first metaverse 1310. The second metaverse 1380 for financial services can collect product distribution data on multiple metaverses existing on the first metaverse 1310.

On the second metaverse (1380), product distribution data is grouped as a grouping unit for various financial services such as sellers, seller groups, all sellers, etc., in the production stage (1320), sales stage (1330), storage stage (1340), distribution stage ( 1350), and may be collected for each purchase step (1360). Additionally, on the second metaverse 1380, result information on various financial services such as sellers, seller groups, all sellers, etc. can be collected.

When a financial service is requested by the seller, product distribution data generated by the seller on the first metaverse 1310 may be collected.

Collateral value evaluation at each distribution stage can be performed based on the collected seller's product distribution data. First collateral valuation (1325) for the seller product in the production stage (1320), second collateral valuation (1335) for the seller product in the sales stage (1330), and third collateral valuation for the seller product in the storage stage (1340). A collateral value evaluation (1345), a fourth collateral value evaluation (1355) for the seller's product in the distribution stage (1350), and a fifth collateral value evaluation (1365) for the seller's product in the purchase stage (1360) may be performed.

At this time, among the product distribution data on the first metaverse 1310, the product distribution data that is the basis of the first-dimensional financial service may be excluded.

The first collateral valuation (1325), second collateral valuation (1335), third collateral valuation (1345), fourth collateral valuation (1355), and fifth collateral valuation (1365) are aggregated and the seller's A final collateral valuation 1370 for the product may be performed. The final collateral value evaluation 1370 may be performed on the second metaverse 1380 by considering result information about various financial services such as seller, seller group, and all sellers. Financial service limits and interest rates may be determined based on the results of the final collateral valuation (1370).

If the seller requests financial services considering financial service limits and interest rates, tokens can be provided to the seller's blockchain wallet on the second metaverse (1380). Tokens provided through blockchain wallets are used on the first metaverse 1310 and the second metaverse 1380, and may be tokens that can be used in place of fiat currency in actual supply chains and financial services. That is, product transactions, token-based repayments, interest payments, etc. are performed based on tokens, which are the actual supply chain corresponding to the first metaverse (1310) and the financial corresponding to the second metaverse (1380). It can be reflected in the service.

Tokens may be issued differently by setting separate standards for each product, seller, and seller group, and the price of the token may change based on product distribution data and financial service data on the metaverse collected later. Tokens can also be cashed out through exchanges on the Metaverse.

The operations of FIGS. 12 and 13 may be performed by a second metaverse implementation device.

Figure 14 is a conceptual diagram showing a token-based transaction method on the metaverse according to an embodiment of the present invention.

In Figure 14, a method for issuing tokens and adjusting token value for providing financial services on the metaverse is disclosed.

Referring to FIG. 14, the token price 1450 may change in consideration of changes in product value 1410, changes in product distribution data 1420, and changes in sales receivables 1430.

For example, when the product value increases relatively, the token price (1450) may increase to reflect the change in product value (1410). Conversely, if the product value becomes relatively low, the token price (1450) may be lowered to reflect the change in product value.

Alternatively, if the product distribution volume relatively increases based on product distribution data, the token price (1450) may be increased taking into account predictions of an increase in product sales volume and an increase in product receivables. Conversely, if the product distribution volume is relatively reduced based on product distribution data, the token price (1450) may be lowered in consideration of predictions of a decrease in product sales volume and a decrease in product receivables.

Alternatively, if sales receivables increase relatively more than predicted based on sales receivables data, the token price (1450) may increase. Conversely, if sales receivables are relatively reduced based on sales receivables data, the token price (1450) may be lowered to take into account the decrease in sales receivables.

Through changes in the token price (1450), financial services can be provided adaptively by reflecting changes in collateral value, and financial risks can also be lowered by directly reflecting changes in collateral value.

Therefore, the spirit of the present invention should not be limited to the above-described embodiments, and the scope of the patent claims described below as well as all scopes equivalent to or equivalently changed from the scope of the claims are within the scope of the spirit of the present invention. It will be said to belong to

The embodiments according to the present invention described above can be implemented in the form of program instructions that can be executed through various computer components and recorded on a computer-readable recording medium. The computer-readable recording medium may include program instructions, data files, data structures, etc., singly or in combination. Program instructions recorded on the computer-readable recording medium may be specially designed and configured for the present invention, or may be known and usable by those skilled in the computer software field. Examples of computer-readable recording media include magnetic media such as hard disks, floppy disks, and magnetic tapes, optical recording media such as CD-ROMs and DVDs, and magneto-optical media such as floptical disks. medium), and hardware devices specifically configured to store and execute program instructions, such as ROM, RAM, flash memory, etc. Examples of program instructions include not only machine language code such as that created by a compiler, but also high-level language code that can be executed by a computer using an interpreter or the like. A hardware device can be converted into one or more software modules to perform processing according to the invention and vice versa.

In the above, the present invention has been described in terms of specific details, such as specific components, and limited embodiments and drawings, but this is only provided to facilitate a more general understanding of the present invention, and the present invention is not limited to the above embodiments. Anyone with ordinary knowledge in the technical field to which the invention pertains can make various modifications and changes from this description.

Claims (6)

The financial service method based on product distribution data on the metaverse is:
A second metaverse implementation device providing a first-dimensional financial service; and
A financial service method comprising providing a second-dimensional financial service by the second metaverse implementation device. According to paragraph 1,
The first dimensional financial service is a financial service based on first data generated by a first data processing server group,
The second-dimensional financial service is a financial service based on first metaverse data generated by a first metaverse data processing server group. According to clause 2,
The second-dimensional financial service is characterized by determining financial service limits and interest rates based on the results of the final collateral value evaluation considering the collateral value evaluation at each distribution stage based on product distribution data collected on the first metaverse. How to do financial services. The second metaverse implementation device that provides financial services based on product distribution data on the metaverse is,
Providing first-level financial services,
A second metaverse implementation device implemented to provide second-dimensional financial services. According to clause 4,
The first dimensional financial service is a financial service based on first data generated by a first data processing server group,
The second dimensional financial service is a second metaverse implementation device, characterized in that it is a financial service based on the first metaverse data generated by the first metaverse data processing server group. According to clause 5,
The second-dimensional financial service is characterized by determining financial service limits and interest rates based on the results of the final collateral value evaluation considering the collateral value evaluation at each distribution stage based on product distribution data collected on the first metaverse. A second metaverse implementation device.

Images