Digital product utilization system, digital product utilization method, and server

Abstract

A digital product utilization system according to the present disclosure comprises a first server (1), an NFT-issuing unit, and a second server (2). The first server (1) includes: a first control unit that performs display control for displaying a metaverse space on terminal (4) of a user, and performs output control for outputting a digital product associated with the user in a mode usable by the terminal (4) in the metaverse space; and a second control unit that receives, from the terminal (4), an NFT-ization request relating to the digital product. The NFT-issuing unit issues an NFT based on the digital product to the user in response to the NFT-ization request received by the second control unit. The second server (2) manages an NFT marketplace and, upon receiving an NFT exhibition request from the terminal (4), exhibits the NFT in the NFT marketplace.

Description

Digital product utilization system, digital product utilization method, and server

[0001] This case relates to a system and method for utilizing digital products, and a server provided in the system.

[0002] In recent years, the recognition of the metaverse space (virtual space, also simply referred to as "metaverse"), which is a virtual digital space accessible through networks such as the Internet, has been increasing. In the metaverse space, multiple users in different locations in the real world can communicate in real time, so it is actively used in the field of entertainment such as games and events (for example, see Patent Document 1).

[0003] Japanese Patent No. 6644928

[0004] There is room for improvement in the method of utilizing digital products (objects, digital assets) used in the metaverse space.

[0005] This case was created in light of the above problems, and one of its purposes is to realize a system with a high utilization value of digital products. In addition to this purpose, the effects derived from each configuration shown in the "Mode for Carrying Out the Invention" described later, which are effects that cannot be obtained by the conventional technology, are also other purposes of this case.

[0006] The disclosed digital product utilization system, digital product utilization method, and server can be realized as the following disclosed modes (application examples) and solve at least some of the above problems. Modes 1 to 6 relate to the digital product utilization system. Each of Modes 2 to 6 is an aspect that can be additionally and appropriately selected, and each is an aspect that can be omitted. None of Modes 2 to 6 disclose aspects or configurations that are essential for this case. Also, Modes 7 and 8 relate to the digital product utilization method, and Modes 9 and 10 relate to the server. Corresponding configurations to Modes 3 to 6 can be added to Modes 7, 8 and Modes 9, 10 respectively.

[0007] Embodiment 1. The disclosed digital product utilization system comprises a first server, an NFT issuing unit, and a second server. The first server includes a first control unit that performs display control to display the metaverse space on the user's terminal and output control to output the digital product associated with the user in the metaverse space in a manner usable by the terminal, and a second control unit that receives an NFT conversion request for the digital product from the terminal. The NFT issuing unit issues an NFT based on the digital product to the user in response to the NFT conversion request received by the second control unit. The second server manages an NFT marketplace and, when it receives a request to list an NFT from the terminal, lists the NFT on the NFT marketplace.

[0008] Embodiment 2. In Embodiment 1 described above, it is preferable that the digital product utilization system further comprises an NFT invalidation unit for invalidating the NFT sold by the second server. In this case, it is preferable that the second server, upon receiving a purchase request for the NFT listed on the NFT marketplace, sells the NFT to a second user who has a second terminal that sent the purchase request. Furthermore, it is preferable that the first server has a third control unit that receives a digital productization request for the NFT sold by the second server from the second terminal, and in response to the digital productization request received by the third control unit, the NFT sold by the second server is invalidated by the NFT invalidation unit to become the digital product, the first control unit associates the digital product with the second user and performs the display control and output control for the second terminal, and the second control unit receives an NFTization request for the digital product associated with the second user from the second terminal.

[0009] Embodiment 3. In Embodiment 1 or 2 above, it is preferable that the first control unit disables the digital product in the output control after the NFT based on the digital product has been issued by the NFT issuing unit. Embodiment 4. In any one of Embodiments 1 to 3 above, it is preferable that the digital product is a digital vehicle usable in the metaverse space. In this case, it is preferable that the first control unit outputs the digital vehicle in the output control in a manner that allows for driving operation and a manner that allows for customization.

[0010] Embodiment 5. In Embodiment 4 above, the digital vehicle is sold to the user by the automobile manufacturer, and it is preferable that the first control unit associates the digital vehicle with the user who purchased it. Embodiment 6. In Embodiment 5 above, the digital vehicle is a digitized version of a vehicle that the automobile manufacturer has handled in the real world, and it is preferable that the first server, in output control, causes the digital vehicle to exhibit performance similar to that of the actual vehicle.

[0011] Embodiment 7. The disclosed digital product utilization method is implemented by a first server, an NFT issuing unit, and a second server. The first server, through its first control unit, performs display control to display the metaverse space on the user's terminal and outputs the digital product associated with the user in the metaverse space in a manner usable by the terminal. The second control unit receives an NFT request for the digital product from the terminal. The NFT issuing unit issues an NFT based on the digital product to the user in response to the NFT request received by the second control unit. The second server manages an NFT marketplace and, when it receives a request to list an NFT from the terminal, lists the NFT on the NFT marketplace.

[0012] Embodiment 8. In Embodiment 7 described above, the second server, upon receiving a purchase request for the NFT listed on the NFT marketplace, sells the NFT to a second user who has a second terminal that sent the purchase request; the first server, via its third control unit, receives a digital productization request for the NFT sold by the second server from the second terminal; the NFT invalidation unit, in response to the digital productization request received by the third control unit, invalidates the NFT sold by the second server to create the digital product; the first server, via its first control unit, associates the digital product with the second user and performs the display control and output control for the second terminal; and the second control unit receives an NFT conversion request for the digital product associated with the second user from the second terminal.

[0013] Embodiment 9. The disclosed server is a server that sends and receives data with a user's terminal and includes a first control unit that performs display control to display a metaverse space on the terminal and output control to output a digital product associated with the user in a manner usable by the terminal in the metaverse space; a second control unit that receives an NFT request for the digital product from the terminal; and an issuing unit that, in response to the NFT request, issues an NFT to the user based on the digital product and that can be listed on an NFT marketplace managed by the second server.

[0014] Embodiment 10. In Embodiment 9 described above, the server preferably further comprises a third control unit that receives a request to digitize the NFT sold by the second server from a second terminal that has sent a purchase request for the NFT listed on the NFT marketplace, and a deactivation unit that, in response to the request to digitize the NFT sold by the second server, deactivates the NFT to digitize it in response to the request to digitize it received by the third control unit. In this case, the first control unit associates the digital product with a second user having the second terminal and performs the display control and output control for the second terminal, and the second control unit preferably receives an NFT request from the second terminal regarding the digital product associated with the second user.

[0015] The disclosed digital product utilization system, digital product utilization method, and server will enable the construction of a system that maximizes the value of digital product utilization.

[0016] This is a diagram showing the flow of digital products in a digital product utilization system according to one embodiment. This is a block diagram showing an example of the hardware configuration of a computer that realizes the functions of a server according to one embodiment. This is a block diagram showing an example of the software configuration of a digital product utilization system according to one embodiment. This is an example of an image displayed on the terminal's display screen, showing a scene where a digital vehicle is stored in a garage. This is an example of an image displayed on the display screen when driving operations are being performed on the terminal, showing a first-person perspective. This is an example of an image displayed on the display screen when driving operations are being performed on the terminal, showing a third-person perspective. This is an example of an image displayed on the display screen of a friend's terminal while driving operations are being performed on the user's terminal, showing a first-person perspective.

[0017] Referring to the drawings, a digital product utilization system, a digital product utilization method, and a server will be described as embodiments (examples). The embodiments shown below are merely illustrative, and there is no intention to exclude various modifications or applications of technologies not explicitly shown in the embodiments below. Each configuration of the embodiments can be modified in various ways without departing from their spirit. Furthermore, they can be selected or combined as needed.

[0018] [1. Overview] The Digital Product Utilization System (hereinafter also referred to as the "Utilization System") is a system for enhancing the utilization value of digital products usable in the metaverse space (virtual space, also simply called the metaverse). Here, "digital product" refers to a product in digital format that can be owned, used, or bought and sold as digital data, and is also called a digital product, object, digital asset, or digital content. Examples of digital products include digital vehicles, audio, music, images (pictures and drawings), and digital data such as videos. Furthermore, "use" here includes viewing, appreciating, listening to, operating, modifying, editing, and customizing digital products.

[0019] In this utilization system, users associated with digital products can use those digital products in the metaverse space. Furthermore, it is possible to convert the digital products associated with users into NFTs (Non-Fungible Tokens) and list them on an NFT marketplace (NFT exchange). Here, "association" means that the fact that "the owner of the digital product = the user" is stored (linked) in a designated database on the first server that constitutes the utilization system. NFTs are used to prove ownership of digital products and are issued (minted) according to the ERC-721 standard on the ETHEREUM® blockchain (distributed ledger).

[0020] NFT creation means recording digital data (digital products) as tokens on a blockchain. NFT-created digital data is associated with a token ID to identify the NFT and owner information of the NFT owner. An NFT consists of a token ID, owner's address (owner information), token URI (Uniform Resource Identifier), etc. This information is recorded on the blockchain. The token ID has a unique value in itself. The token URI is information that indicates the location of the metadata of the content (NFT-created digital data) associated with the NFT. Metadata includes attribute information such as the content's name, description, URL (Uniform Resource Locator), content owner, and the owner's history. NFTs are managed in an NFT management system that includes the blockchain and a second server (NFT management server 2) described later.

[0021] In short, the utilization system allows a user to use a digital product they own on a terminal operated by that user (hereinafter also referred to as the "user terminal"), and also allows the used digital product to be converted into an NFT (minted) and sold. When a digital product is used, it is used in the metaverse space displayed on the user terminal, but when it is sold on the NFT marketplace, it is converted into an NFT rather than remaining as a digital product, thereby guaranteeing its uniqueness and immutability. The NFT marketplace is an online platform where NFTs can be bought, sold, and exchanged.

[0022] Furthermore, in the utilization system, it is preferable that a user who purchases an NFT listed on the NFT marketplace (hereinafter referred to as the "second user") can deactivate (burn) that NFT, returning it to its original (pre-NFT) digital product state, and then make that digital product usable in the metaverse space displayed on their own terminal (hereinafter also referred to as the "second terminal"). Moreover, in the utilization system, it is preferable that the second user, like the user described above, can also NFT the digital product associated with them and list it on the NFT marketplace. This creates a flow (cycle) of use, NFT conversion, sale, purchase, NFT deactivation, use, NFT conversion, etc., for digital products. As a result, it becomes possible for companies providing utilization systems to build a business model based on a service cycle, and also to realize a creator economy.

[0023] [2. Digital Product Utilization System and Method] A digital product utilization system (utilization system) according to one embodiment will be described in detail below with reference to Figures 1 to 3. Figure 1 is a diagram showing the flow of digital products in the utilization system, and Figure 2 is a block diagram showing an example of the hardware configuration of the computer 50 that realizes the functions of servers 1 to 3 and terminals 4 and 5 according to this embodiment. Figure 3 is a block diagram showing an example of the software configuration of the utilization system.

[0024] [2-1. Flow of Digital Products] As shown in Figure 1, the utilization system is equipped with at least two servers 1 and 2. The first server 1 transmits and receives data with the user's terminal 4 and mainly performs display control to display the metaverse space on the user terminal 4, and also has the function of output control to output digital products associated with the user (hereinafter referred to as "owned digital products") in a form that can be used by the user terminal 4 in the metaverse space.

[0025] The provision of functions to the user by the first server 1 is described as being achieved, for example, by an application installed on the user terminal 4 (the main application 40 in Figure 3, described later) communicating with multiple servers of the utilization system (including the first server 1) via the network N (see Figure 3). This main application 40 may be a dedicated application intended for accessing and using the utilization system. Hereinafter, this first server 1 will be referred to as the "application provision server 1". The application provision server 1 can also be described as a server that provides the main application 40 and the services through the main application 40 to the user. Note that the network N may be formed by at least one of the following networks: the Internet, a LAN (Local Area Network), or a mobile network.

[0026] Second Server 2 primarily has the function of managing the NFT marketplace. Hereafter, Second Server 2 will be referred to as "NFT Management Server 2". NFT Management Server 2 may perform tasks such as authenticating and registering users of the NFT marketplace, listing NFTs on the NFT marketplace, and selling NFTs that are currently listed.

[0027] User terminal 4 is a computer (or group of computers) such as a smartphone, tablet, PC (Personal Computer), smartwatch, or PDA (Personal Digital Assistant), and is operated by the user. Multiple user terminals 4 may be used in the utilization system. In addition, a friend terminal 5 (see Figure 3) may be used separately from the user terminal 4 in the utilization system.

[0028] A friend terminal 5 is a terminal operated by a user's friend, and there is no limit to the number of such terminals. Focusing on one of the multiple user terminals 4, some or all of the remaining user terminals 4 may become friend terminals 5. In this case, user terminals 4 and friend terminals 5 have the same configuration, differing only in name. Note that user terminals 4 and friend terminals 5 do not necessarily have the same configuration. As shown in Figure 3, the application provision server 1, NFT management server 2, user management server 3 (described later), and multiple terminals 4 and 5 are each connected to each other via the network N so that they can communicate with one another. In addition, the main application 40 for implementing the utilization system is installed on each terminal 4 and 5.

[0029] As shown in Figure 1, in the utilization system, first, the application provision server 1 associates digital products with users (see symbol A1). This process A1 is performed in the application provision server 1, for example, when a user purchases a digital product by spending paid coins (e.g., digital currency) usable in the main application 40, or when a user acquires a digital product by spending free coins (e.g., points) granted in the main application 40. Alternatively, when digital data originally stored in the user terminal 4 is uploaded to the application provision server 1, the application provision server 1 may associate it with the user's digital product.

[0030] Owned digital products are used in the metaverse space by the user (terminal 4) through the application provision server 1, which performs the display and output control described above. When a user requests NFT conversion of a used digital product (see code A2), the application provision server 1 issues an NFT based on the digital product to the user in response to that request (see code A3). In this case, the digital product on which the NFT was based becomes unusable. This guarantees the uniqueness and immutability of the digital product. An NFT conversion request is one of the user request signals transmitted from the user terminal 4 when the user wishes to convert a digital product into an NFT (when the user performs the operation to convert it into an NFT).

[0031] The issued NFTs are stored (stored, registered) in the user's wallet (account). Note that in order for a user to use the NFT marketplace, they need to create, register, and authenticate an account with the NFT management server 2, but these processes will not be explained here. Furthermore, it will be assumed that the user's wallet has already been created on the NFT management server 2. The wallet may be created within the NFT management server 2, provided that it is accessible from at least the user terminal 4 (terminal 4A in Figure 1) and the NFT management server 2, or it may be created and managed on another server (including the application provision server 1) that is compatible with the NFT management server 2.

[0032] NFTs based on digital products are listed on the NFT marketplace by the NFT management server 2 when a user requests to list them (see code A4). A listing request is one of the user request signals sent from the user terminal 4 when a user wishes to list (sell) an NFT stored in their wallet (when the user performs an operation to list it). In addition, the user may be allowed to set the price of the NFT along with the listing request. The NFT may be considered sold by the user when it is listed on the NFT marketplace. According to the flow of codes A1 to A4, since the digital product is sold as an NFT rather than as is, it becomes possible to give the unique digital product (NFT) asset value and allow it to be traded in secondary markets. This makes it possible to build a system that has high utilization value for digital products.

[0033] When a purchase request is received for an NFT listed (displayed) on the NFT marketplace (see symbol A5), the NFT management server 2 sells the NFT to the user (second user) whose user terminal 4 (second terminal 4B in Figure 1) sent the purchase request (see symbol A6). In this case, the sold NFT is stored in the wallet (account) of the purchasing second user and becomes unavailable for purchase on the NFT marketplace. A purchase request is one of the user request signals sent from the second terminal 4B when the second user wishes to purchase an NFT listed on the NFT marketplace (when the second user performs an operation to purchase it). Normally, the user listing the NFT and the second user purchasing it are different people (terminal 4A and second terminal 4B are different), but if the user who listed the NFT buys it back, they are the same person. In other words, the seller (user) and the buyer (second user) can be the same person or different people.

[0034] When a second user requests the digitalization of an NFT purchased by the second user (see code A7), the application provider server 1 invalidates (burns) the NFT in response to that request. A digitalization request is one of the user request signals sent from the second terminal 4B when the second user wishes to use the NFT (when the second user performs an operation to use it). As a result, the NFT owned by the second user returns to its original (pre-NFT) digital product form and is associated with the second user. This digital product is then used in the metaverse space by the second user (second terminal 4B) through the application provider server 1's display and output control (see code A8). The digital product used by the second user may be utilized in the flow shown by codes A2 to A8. This configuration establishes a system (creator economy) in which services related to digital products circulate.

[0035] [2-2. Hardware Configuration Example] The functions of the utilization system according to one embodiment can be realized by a computer. Examples of computers include information processing devices such as servers and PCs. The computer may be a virtual server (VM: Virtual Machine) or a physical server. There is no particular limit to the number of computers required to realize the functions of the utilization system. Furthermore, at least a part of the functions of the utilization system may be realized using hardware resources and network resources provided by a cloud environment.

[0036] Figure 2 is a block diagram illustrating the hardware configuration of a computer 50 that implements the functions of the utilization system. When multiple computers are used as hardware resources to implement the functions of the utilization system, each computer may have the hardware configuration illustrated in Figure 2. The computers that implement the functions of each server 1 to 3, and the computers that implement the functions of terminals 4 and 5, may each have the same hardware configuration. The hardware configurations of these computers will be explained below using the computer 50 shown in Figure 2 as an example. As shown in Figure 2, the computer 50 includes, for example, a processor 51, memory 52, storage unit 53, IF (Interface) unit 54, IO (Input / Output) unit 55, graphics processing unit 56, and reading unit 57.

[0037] The processor 51 is an example of an arithmetic processing unit that performs various control and calculations. The processor 51 is connected to each block in the computer 50 via a bus 59 so that they can communicate with each other. The processor 51 may be a multiprocessor containing multiple processors, a multicore processor having multiple processor cores, or a configuration having multiple multicore processors. Examples of the processor 51 include integrated circuits (ICs) such as CPU (Central Processing Unit), MPU (Micro Processing Unit), APU (Accelerated Processing Unit), DSP (Digital Signal Processor), ASIC (Application Specific IC), and FPGA (Field-Programmable Gate Array). A combination of multiple such integrated circuits may also be used as the processor 51.

[0038] Memory 52 is an example of hardware that stores various data and program information. Examples of memory 52 include volatile memory such as DRAM (Dynamic Random Access Memory) and non-volatile memory such as PM (Persistent Memory), and it may be either one or both.

[0039] The storage unit 53 is an example of hardware that stores various data and information such as programs. Examples of storage units 53 include magnetic disk devices such as HDDs (Hard Disk Drives), semiconductor drive devices such as SSDs (Solid State Drives), and various storage devices such as non-volatile memory. Examples of non-volatile memory include flash memory, SCM (Storage Class Memory), and ROM (Read Only Memory). The storage unit 53 may store programs 58 (digital product utilization programs) that realize all or part of the various functions of the computer 50. For example, the processor 51 can realize the functions of a utilization system (for example, the application provision server 1 and NFT management server 2 in Figure 1) by loading the program 58 stored in the storage unit 53 into the memory 52 and executing it.

[0040] The IF unit 54 is an example of a communication IF that controls the connection and communication between the utilization system (application provision server 1, NFT management server 2, user management server 3) and terminals 4 and 5 operated by the user. The IF unit 54 may include an adapter compliant with, for example, a LAN such as Ethernet (registered trademark) or optical communication such as FC (Fibre Channel). This adapter may support wireless, wired, or both communication methods. The program 58 may be downloaded from the network to the computer 50 via the IF unit 54 and stored in the storage unit 53.

[0041] The I / O unit 55 includes at least one of an input device and an output device. Examples of input devices include a keyboard, touch panel, camera, mouse, microphone, gaze detection device for detecting gaze, and gesture reading device for detecting gesture operations. Examples of output devices include display devices (monitors) such as liquid crystal displays and organic EL (Electro-Luminescence) displays, and projectors. The I / O unit 55 may also include a touch panel device in which the input device and display device are integrated.

[0042] The graphic processing device 56 controls the screen display for the display device in the IO unit 55. Examples of the graphic processing device 56 include various arithmetic processing devices, such as integrated circuits (ICs) like GPUs (Graphics Processing Units), APUs, DSPs, ASICs, or FPGAs. The display device of the IO unit 55 may be connected to the graphic processing device 56.

[0043] The reading unit 57 is an example of a reader that reads data and program information recorded on the recording medium 60. The reading unit 57 may include a connection terminal or device to which the recording medium 60 can be connected or inserted. Examples of the reading unit 57 include an adapter compliant with, for example, USB (Universal Serial Bus), a drive device that accesses a recording disk, and a card reader that accesses a flash memory such as an SD card. The program 58 may be stored in the recording medium 60, and the reading unit 57 may read the program 58 from the recording medium 60 and store it in the storage unit 53.

[0044] Examples of the recording medium 60 include non-temporary computer-readable recording media such as magnetic / optical disks and flash memories. Examples of the magnetic / optical disks include flexible disks, CDs (Compact Discs), DVDs (Digital Versatile Discs), Blu-ray discs, and HVDs (Holographic Versatile Discs). The flash memory is, for example, a semiconductor memory such as a USB memory or an SD card.

[0045] The above-described hardware configuration of the computer 50 is an example, and increases or decreases (for example, addition or deletion of any block), division, integration in any combination, addition or deletion of buses, etc. of the hardware within the computer 50 may be appropriately performed.

[0046] The computers that implement the functions of each of the servers 1 to 3 and the computers that implement the functions of the terminals 4 and 5 may each have the same hardware configuration as the computer 50 illustrated in FIG. 2, or may have a hardware configuration in which at least one component, for example, the graphic processing unit 56, is omitted from the computer 50. When the graphic processing unit 56 is omitted in the terminals 4 and 5, the processor 51 may perform screen display control for the display device.

[0047] [2-3. Software Configuration Example] Next, a software configuration example of the utilization system according to an embodiment will be described with reference to FIG. 3. In the following description, for convenience, the user terminal 4 is taken as an example, but the same functions may be applied to the friend terminal 5.

[0048] <App Provision Server> The app provision server 1 of the present embodiment includes an app function unit 10, an NFT function unit 11, and a database (hereinafter referred to as "DB") 12. The functions of the app function unit 10 and the NFT function unit 11 may be realized by the processor 51 shown in FIG. 2 provided in the computer 50 as the app provision server 1 expanding and executing the program 58 in the memory 52.

[0049] The app function unit 10 (first control unit) communicates with the user management server 3 and the user terminal 4 and mainly performs the above-described display control and output control. As shown in FIG. 3, the app function unit 10 of the present embodiment includes a user management unit 10a, a digital product management unit 10b, and a display output control unit 10c.

[0050] The user management unit 10a performs overall management of users. The user management unit 10a performs, for example, management of the user DB 12b described later, authentication processing at the time of user account creation and login, acquisition of user information stored in the user DB 12b, association of a user with a digital product (recording in the owned digital product DB 12d described later), etc. As the authentication processing, the user management unit 10a may, for example, transmit authentication information from the user terminal 4 to the user management server 3 and provide the user with the functions of the main app 40 when authentication is permitted by the user management server 3.

[0051] The Digital Product Management Unit 10b is responsible for the overall management of digital products. For example, the Digital Product Management Unit 10b manages information and sales of digital products within the main application 40, and manages the usage status of digital products for each user. Information management includes, for example, recording (registering, updating) information about digital products (hereinafter referred to as "digital product information") in the digital product DB 12c, which will be described later. Sales management includes providing the main application 40 with the functionality of a shop that can sell, provide, or exchange (hereinafter collectively referred to as "sales") digital products to users. In sales management, when a digital product is sold to a user at the shop (the user becomes the owner of the digital product), the User Management Unit 10a associates the user with the digital product.

[0052] Furthermore, usage status management may include, for example, recording the usage status of digital products owned by a user, or the status of digital products (e.g., modified, processed, or customized) in the owned digital product DB 12d (updating the status of digital products associated with the user). In addition, usage status management may include recording in the owned digital product DB 12d that the digital product on which the NFT was based is unusable when an NFT based on a digital product associated with a user is issued (updating information such as a flag indicating whether the digital product on which the NFT was based by the user is usable to a value indicating unusable).

[0053] The display output control unit 10c performs the display control and output control described above. Display control is the control to display the metaverse space on the display screen 4d of the user terminal 4 (see Figures 4 to 6 described later). The metaverse space displayed here may include, for example, backgrounds related to the digital product, the user's avatar, and avatars of other users. Output control is the control to output (display) the digital product in a usable form to the metaverse space displayed on the display screen 4d. Output control may include, for example, control to output so that the user can view the digital product or operate and move the digital product in the metaverse space using the user terminal 4.

[0054] The NFT function unit 11 communicates with the NFT management server 2 and the user terminal 4, and mainly transmits and receives signals related to NFT. As shown in Figure 3, the NFT function unit 11 in this embodiment includes a mint function unit 11a and a digital product conversion unit 11b.

[0055] The Mint function unit 11a (second control unit) receives an NFT request for a digital product from the user terminal 4 (for example, terminal 4A in Figure 1). The Mint function unit 11a may also have a function (NFT issuing unit) that issues an NFT based on the digital product to the user in response to the NFT request. When the Mint function unit 11a issues an NFT, it stores the NFT in the wallet corresponding to the user.

[0056] Furthermore, the function of an NFT issuing unit may be provided by a server other than the application provision server 1 (for example, an NFT management server 2 or other external server). In this case, the mint function unit 11a will have the function of sending the received NFT conversion request to the other server (NFT issuing unit), and the NFT issued by the other server (NFT issuing unit) will be stored in the wallet corresponding to the user. The wallet may be provided in the NFT function unit 11 of the application provision server 1, in the NFT management server 2, or on any other external server.

[0057] The digital product conversion unit 11b (third control unit) receives a digital product conversion request from the user terminal 4 (for example, the second terminal 4B in Figure 1) regarding an NFT sold by the NFT management server 2 (purchased by the second user). Upon receiving the digital product conversion request, the digital product conversion unit 11b may also have a function (NFT invalidation unit) to invalidate the NFT and convert it into a digital product in response to the digital product conversion request. The NFT invalidation unit performs an NFT invalidation process to burn the NFT to the wallet in response to the digital product conversion request, and also performs a digital product activation process to associate the digital product on which the burned NFT was based with the second user as a valid digital product. The digital product activation process includes, for example, a process to notify the application function unit 10 of information indicating the digital product on which the burned NFT was based and information indicating the second user. Note that the function of the NFT invalidation unit may be provided by a server other than the application provision server 1 (NFT management server 2 or other external servers). In this case, the digital product conversion unit 11b will have the function of sending the received digital product conversion request to another server (NFT deactivation unit) and the function of receiving notifications in the digital product activation process.

[0058] Furthermore, digital products with NFT disabled are registered in the owned digital product DB 12d, associated with the second user, by the user management unit 10a of the application function unit 10, and the display output control unit 10c performs the display control and output control described above for the second terminal 4B. In addition, the mint function unit 11a can receive an NFT request from the second terminal 4B regarding a digital product associated with the second user. In this case, the NFT issuing unit may issue an NFT based on that digital product to the second user in response to the NFT request.

[0059] DB12 may be implemented by a storage area in at least one of the memory 52 and storage unit 53 shown in Figure 2, which are provided in the computer 50 acting as the application provision server 1, or by a storage area provided in another computer or other system. DB12 may be a DB with various database structures. For example, the information to be stored in DB12, as described later, may be distributed and stored and managed in multiple structured tables.

[0060] As shown in Figure 3, the DB 12 of this embodiment includes an application DB 12a, a user DB 12b, a digital product DB 12c, and an owned digital product DB 12d. The application DB 12a stores general information about the main application 40 and general information about NFTs. General information about the main application 40 includes, for example, information used by the application function unit 10, such as sales information for digital products, background information about digital products, and information used when using digital products. General information about NFTs includes, for example, information about wallets, information about mintable digital products, transmission and reception history of NFT requests, information about burnable NFTs, and transmission and reception history of digital product requests.

[0061] User DB 12b stores information about users (hereinafter referred to as "user information"). User information includes, for example, user ID, username, avatar, icon, contact information such as the user's email address, information on functions (permissions) available in the main application 40, and user IDs of friends registered with that user. Note that the above-mentioned second users and friends are also "users," just with different names, so their respective user information is stored in User DB 12b. The mapping between user IDs and friend user IDs may be used as a friend list.

[0062] The digital product DB12c stores digital product information. Examples of digital product information include the digital product ID, product name, characteristics, purchase information, and information associated with the digital product.

[0063] The owned digital product DB 12d stores information about owned digital products (hereinafter referred to as "owned digital product information"). Examples of owned digital product information include the user ID, the ID of the digital product owned by the user with that user ID, unique information about the owned digital product, the usage status of the owned digital product, the status of the owned digital product after use, whether it is minted or burned, and information associated with the digital product. The user ID and the digital product ID indicate that the user and the digital product are associated (ownership of the digital product held by the user). Entries containing these IDs and unique information about the owned digital product (e.g., unique serial number) are registered in the owned digital product DB 12d during sales management by the digital product management unit 10b and NFT disabling by the NFT disabling unit.

[0064] The presence or absence of minting and burning are examples of information such as flags that indicate whether a digital product is usable or unusable. The presence or absence of minting is information (e.g., a flag) that indicates whether a digital product has been minted (NFT enabled), and the presence or absence of burning is information (e.g., a flag) that indicates whether a minted digital product has been burned (NFT disabled) by the user who minted it (the same user). For example, if a digital product is "not minted," it is usable regardless of whether it has been burned or not, and if it is "minted," it is unusable if it is "not burned." However, even if it is "minted," it is usable if it is "burned" (if the NFT was disabled by the same user). The usage status of owned digital products, the status of owned digital products after use, and the presence or absence of minting are updated in the usage status management by the digital product management unit 10b. The presence or absence of burning is updated in the NFT disabling function of the NFT disabling unit. Furthermore, just as in the case where a second user burns an NFT, a new entry may be registered in the owned digital products DB12d when the same user burns an NFT. In this case, the item indicating whether or not a burn occurred may be omitted.

[0065] <NFT Management Server> The NFT management server 2 of this embodiment includes a marketplace function unit 20, a listing acceptance unit 21, and a sales unit 22. The functions of the marketplace function unit 20, the listing acceptance unit 21, and the sales unit 22 may be realized by a processor 51, shown in Figure 2, provided in the computer 50 as the NFT management server 2, which loads a program 58 into memory 52 and executes it. The NFT management server 2 also includes a database (not shown) which stores information about the NFT application 42 in general. When the NFT management server 2 creates and manages a wallet, the database may also store information about the wallet.

[0066] The marketplace function unit 20 communicates with the application server 1 and the user terminal 4, and mainly manages the marketplace in general, registers and authenticates accounts, and creates and manages wallets. The marketplace function unit 20 may be implemented using publicly known technology. The listing reception unit 21 communicates with the application server 1 and the user terminal 4, and receives NFT listing requests from the user terminal 4 (for example, terminal 4A in Figure 1). Furthermore, when the listing reception unit 21 receives a listing request, it lists the NFT on the NFT marketplace. This makes it possible for any user with an account on the NFT management server 2 to purchase the NFT.

[0067] The sales unit 22 receives a purchase request from a user terminal 4 (for example, the second terminal 4B in Figure 1) for an NFT listed on the NFT marketplace. Furthermore, when the sales unit 22 receives a purchase request, it sells the NFT to the second user who has the second terminal 4B that sent the purchase request. The sold NFT is stored in the second user's wallet. Once an NFT is sold, it may be managed in a way that prevents duplicate purchases by being deleted from the NFT marketplace.

[0068] <User Management Server> The user management server 3 in this embodiment includes a user authentication unit 30 and an authentication database 31. The function of the user authentication unit 30 may be realized by a processor 51, shown in Figure 2, provided in the computer 50 which serves as the user management server 3, loading a program 58 into memory 52 and executing it.

[0069] The user authentication unit 30 performs authentication based on information received from the user management unit 10a when a user creates an account for the main application 40, and records the account in the authentication database 31. Furthermore, when a user logs into the main application 40, the user authentication unit 30 performs authentication by referring to the authentication database 31 based on information received from the user management unit 10a, and transmits the authentication result to the user management unit 10a.

[0070] The authentication DB 31 may be implemented, for example, by a storage area in at least one of the memory 52 and storage unit 53 shown in Figure 2, which are provided in the computer 50 acting as the user management server 3, or by a storage area provided in another computer or other system. The authentication DB 31 may be a DB with various database structures. The authentication DB 31 stores information necessary for authentication, such as user IDs and passwords.

[0071] <Terminal> The user terminal 4 of this embodiment includes a main application 40, application data 41, an NFT application 42, an input / output control unit 43, and a communication unit 44. The functions of the main application 40 and the NFT application 42 may be realized by a processor 51, shown in Figure 2, provided in the computer 50 which serves as the user terminal 4, loading a program 58 into memory 52 and executing it.

[0072] The main application 40 is an application provided by the application provision server 1. The main application 40 is launched on the user terminal 4 when a user uses a digital product in the metaverse space, and becomes available to the user after predetermined authentication is performed. The main application 40 is also used when a user digitizes an NFT. The contents of the main application 40 will be explained in the specific examples described later. The application data 41 is information stored in the application DB 12a that should be stored on the user terminal 4, and may be a DB with a database structure, for example. The main application 40 refers to the application data 41 when using a digital product.

[0073] The NFT application 42 is an application related to NFTs. The NFT application 42 is launched on the user terminal 4 when the user logs in to the NFT marketplace, lists NFTs stored in the wallet to the NFT marketplace, or purchases NFTs from the NFT marketplace. After the prescribed authentication is performed, the application becomes available for use by the user. Although Figure 3 shows an example where the main application 40 and the NFT application 42 are provided separately, they may be provided as a single application, for example, the main application 40 may have the functionality of the NFT application 42. Alternatively, the system may be configured to log in to the NFT marketplace using a browser, in which case the browser functions as the NFT application 42. The NFT application 42 may store data related to NFTs and owned NFTs.

[0074] The input / output control unit 43 is a functional unit that provides a user interface and controls input and output on the user terminal 4. At least part of the functions of the input / output control unit 43 may be realized, for example, by the I / O unit 55 shown in Figure 2, which is provided in the computer 50 as the user terminal 4. The input / output control unit 43 receives input from the user of various operations (touch operations, slide operations, etc.) on the display screen 4d (touch panel), and controls output to the user terminal 4 (display on the display screen 4d, sound output, etc.) based on this input and data stored in the user terminal 4 (application data 41, data in the NFT application 42, etc.). For example, when the main application 40 is running, the input / output control unit 43 may control the movement of digital products or the change of viewpoint in the metaverse space. Also, when the NFT application 42 is running, the input / output control unit 43 may control the display of the NFT marketplace on the display screen 4d.

[0075] The communication unit 44 communicates with the user terminal 4 and each of the application provision server 1, NFT management server 2, and user management server 3. Specifically, the communication unit 44 communicates with the servers 1 to 3 to which the main application 40 and NFT application 42 are connected, receives data necessary for each application 40 and 42, transmits input content (various selections and decisions, etc.) received by the input / output control unit 43, transmits various user request signals according to the input content, and receives control signals (including control signals for display control and output control) from the servers 1 to 3 to which they are connected. At least a part of the functions of the communication unit 44 may be realized, for example, by the IF unit 54 shown in Figure 2, which is provided in the computer 50 as the user terminal 4.

[0076] [3. Specific Examples] Next, specific examples of application systems will be explained using Figures 4 to 7. The following examples describe the case where the digital product described above is a digital vehicle usable in the metaverse space. Digital vehicles may include digital automobiles, trucks, buses, motorcycles, etc. Furthermore, the type of digital vehicle is not particularly limited and may include, for example, gasoline cars, electric vehicles (EVs), hybrid vehicles (HEVs), plug-in hybrid vehicles (PHEVs), etc. A plug-in hybrid vehicle means a hybrid vehicle that can be externally charged to or receive power from the battery. Plug-in hybrid vehicles are equipped with a charging port (inlet) for inserting a charging cable into which power is supplied from an external charging facility, and an outlet for external power supply.

[0077] This specific example will first describe a system for experiencing digital vehicles in a metaverse space (hereinafter also referred to as the "Experience System"). In the Experience System, users can have the following experiences, for example. The following experiences are examples of ways in which digital vehicles can be "used": • Purchase a digital vehicle and own your own digital vehicle • Acquire your own garage when you purchase a digital vehicle • Customize your digital vehicle • Customize the garage where your digital vehicle is stored • Communicate with other users who own digital vehicles • Switch between first-person and third-person perspectives • Become friends with other users • Communicate with friends and show off your digital vehicles and garages • Test drive a digital vehicle • View information about your digital vehicle • Drive a digital vehicle

[0078] This specific example will also detail the drive-specific system described at the end of the above section (hereinafter referred to as the "Drive Experience System"). Users can have the following experiences in the Drive Experience System: - Drive alone (Free Driving) - Participate in a race alone (Race) - Invite friends and drive together (Group Drive) - Switch between first-person and third-person views while driving - Change your viewpoint while driving to see the surrounding scenery and interior of the digital vehicle

[0079] [3-1. Digital Vehicle Experience System] The experience system is part of the utilization system described above. First, we will explain what the experience system is implemented by the application server 1 and terminals 4 and 5. In this specific example, the digital vehicle will be sold to the user by a real-world automobile manufacturer. Furthermore, the digital vehicle will be a digitized version of a vehicle that the automobile manufacturer has handled in the real world. This will make it possible to have an experience in the metaverse space that is the same as in the real world. Note that "vehicles that have been handled" include not only vehicles currently on sale, but also vehicles that have been sold in the past, vehicles that are currently on sale or have been sold in foreign countries, and vehicles that have been exhibited at motor shows or exhibitions. In other words, the user will be able to have the above experience in the metaverse space with a digital vehicle that is the same as a vehicle that has existed in the real world.

[0080] In the above-mentioned application server 1, if a digital vehicle has already been associated with a user, the above-mentioned application function unit 10 outputs the digital vehicle in a manner that allows for driving operation and customization in the above-mentioned output control. In other words, in this experience system, the above-mentioned "use" includes at least driving operation of the digital vehicle and customization of the digital vehicle, and may also include viewing and riding the digital vehicle.

[0081] Furthermore, if a digital vehicle is available for sale in the main application 40, the application function unit 10 associates the digital vehicle with the user who purchased it. Specifically, the user terminal 4 displays a metaverse space on its display screen 4d. When an operation to purchase a specific digital vehicle is performed in that metaverse space (for example, when a user selects a digital vehicle they want to purchase and performs the necessary operations for purchase), it sends a digital vehicle purchase signal to the application server 1. Upon receiving this purchase signal, the application server 1 associates the purchased digital vehicle with the user. This allows the user to own their own digital vehicle.

[0082] In this trial system, the application server 1 associates the user with both the digital vehicle and the garage where the digital vehicle is stored. In other words, the application server 1 makes the digital vehicle and garage available for use on the user terminal 4. Thus, in this trial system, when a user purchases a digital vehicle, they are automatically provided with a user-exclusive garage (hereinafter referred to as "My Garage") for storing (parking) the digital vehicle. The user terminal 4 then displays the digital vehicle and My Garage on the display screen 4d in a manner that allows them to be used in the metaverse space. My Garage is an example of information associated with a digital product (digital vehicle).

[0083] This type of experience system allows users to easily own digital vehicles in the metaverse space, provided they have a user terminal 4. This improves the user experience, including the emotions, impressions, and reactions users have when they "own a car." Furthermore, purchasing a digital vehicle comes with a personal garage where the vehicle is stored. This creates a real-world-like environment in the metaverse space, increasing the added value of the digital vehicle, including the personal garage.

[0084] My Garage is a place where digital vehicles are stored, a starting point for driving and customization, and a special space that can only be entered by the user and their friends. When a user purchases a digital vehicle for the first time, they are given a My Garage corresponding to that digital vehicle. On the other hand, if a user already owns a My Garage, they may be given a My Garage each time they purchase a digital vehicle, or the purchased digital vehicle may be stored in an existing My Garage. In the former case, the user will own multiple My Garages, so the user may be able to toggle the display of their My Garage on and off. In the latter case, the user will own only one My Garage.

[0085] The application server 1 only allows a friend's terminal 5 to enter the user's My Garage if the user's terminal 4 is logged into the main application 40 (experience system). In other words, if the user is not using the main application 40, even a friend cannot enter that user's My Garage. A friend is any other user registered in the user's friend list on the application server 1. My Garage expands the opportunities for interaction among users (including friends) using the experience system, thereby improving the user experience.

[0086] The application provider server 1 preferably sets the configuration of the My Garage based on at least one of the type, size, and number of digital vehicles. For example, if the digital vehicle is an electric vehicle or a plug-in hybrid vehicle, the application provider server 1 may install external charging equipment in the My Garage. Also, if the digital vehicle is a large vehicle or if the user owns multiple digital vehicles, the application provider server 1 may expand the size of the My Garage. By providing users with a My Garage that corresponds to their digital vehicles in this way, the added value of the digital vehicle, including the My Garage, is further enhanced. Furthermore, an upper limit may be set for the size of the My Garage, and if the user owns more digital vehicles than can be stored in the My Garage, the display and hiding of the digital vehicles in the My Garage may be toggled.

[0087] Figure 4 is an example of the image displayed on the display screen 4d of the user terminal 4, showing a scene where a digital vehicle (hereinafter referred to as D) is stored in My Garage (hereinafter referred to as G). The user terminal 4 displays the digital vehicle D and My Garage G on the display screen 4d in a manner that can be used in the metaverse space, as shown in Figure 4, for example. In Figure 4, the user's avatar Au (hereinafter referred to as "user avatar Au") is displayed next to the digital vehicle D, and the friend's avatar Af (hereinafter referred to as "friend avatar Af") is also displayed.

[0088] In the metaverse space, avatars can communicate with each other, for example, through chat (text input) or voice conversation. Furthermore, in the metaverse space, the image displayed on the 4D display screen (the user's perspective) may be switchable between first-person and third-person viewpoints. In first-person view, the 4D display screen shows an image where the user's perspective and the user avatar Au's perspective (the image of their gaze) are the same. On the other hand, in third-person view, a wider area including the user avatar Au is displayed on the 4D display screen.

[0089] By the way, since friends also own their own digital vehicles and garages, users can visit their friends' garages and view their digital vehicles. In addition, avatars of other users besides the user and their friends may be present in the space outside the garage G (not shown in the diagram, hereinafter referred to as the "lobby"). Users may communicate with other users' avatars in the lobby or send friend requests to become friends with them.

[0090] In this specific example, a virtual pad 61 operated by the user is displayed on the display screen 4d of the terminal 4. Preferably, the virtual pad 61 is displayed only when the user's finger is touching the display screen 4d, and is hidden when not being operated. By tapping or sliding the virtual pad 61, the user can change the orientation of the metaverse space displayed on the display screen 4d, view and customize information on the digital vehicle D, customize My Garage G, operate the user avatar Au, select menu M, etc. In Figure 4, virtual pads 61 are provided on both the left and right sides of the display screen 4d, but the arrangement and number of virtual pads 61 are not limited to this. Furthermore, the parts operated by the user are not limited to the virtual pad 61, and may include, for example, buttons 62 to 65 (see Figures 5 and 7) described later, as well as other forms of virtual pads (e.g., cross-shaped keys or buttons) depending on the image (situation) displayed on the display screen 4d, or a virtual keyboard (software keyboard) for text input. Furthermore, the display objects themselves, such as digital vehicles, garages, and users, may include parts that can be manipulated by the user.

[0091] Menu M may include items related to the driving experience system described later, such as "Race," "Free Practice," and "Group Drive," as well as items related to the use of the digital vehicle D, such as "Customize," "Test Drive," and "Details." In Figure 4, Menu M is displayed in the upper right corner of the display screen 4d, but the display position of Menu M is not limited to this. Also, the items in Menu M are not limited to those shown in Figure 4.

[0092] The "Custom" option in Menu M is selected by the user when customizing either the Digital Vehicle D or My Garage G. Customizing the Digital Vehicle D includes, for example, changing the body color, applying stickers, and equipping devices that are manufacturer options in the real world. Customizing My Garage G includes, for example, changing the color of the garage walls, ceiling, and floor, and arranging decorations that suit the garage space.

[0093] The "Test Drive" option in Menu M is selected when the user wants to temporarily ride in a digital vehicle D rather than actually driving it. When the user selects "Test Drive" from Menu M, an animation of the user avatar Au getting into the driver's seat of digital vehicle D is displayed on screen 4d, and the view from the user avatar Au's perspective (the direction they are looking) is displayed on screen 4d. If multiple digital vehicles D are stored in My Garage G, the user may be prompted to select the digital vehicle D they want to test drive.

[0094] The "Details" option in Menu M is selected by the user when viewing information about the digital vehicle D. The application server 1 stores various information about the real-world vehicle as information about the digital vehicle D. Examples of information stored here include vehicle size (overall length, overall width, overall height), wheelbase, vehicle weight, type of drive source, maximum output, maximum torque, and drive system. When the user terminal 4 performs an operation to view information about the digital vehicle D in My Garage G, it displays the above information obtained from the application server 1 on the display screen 4d. In addition to selecting "Details" from Menu M, the viewing operation may also include operations such as tapping the digital vehicle D. The timing of when the user terminal 4 obtains information from the application server 1 may be when the digital vehicle D is purchased or when the viewing operation is performed.

[0095] According to the above configuration, users can view various information about vehicles that have existed in the real world within the digital vehicle D. Therefore, if the digital vehicle D corresponds to a vehicle currently sold in the real world, users can utilize the metaverse space as if it were a showroom. Furthermore, if the digital vehicle corresponds to a vehicle that has already been discontinued in the real world or a vehicle that was exhibited at a motor show, users can access information about vehicles that are difficult to see in the real world within the metaverse space.

[0096] Furthermore, it is preferable that the information of the digital vehicle D can also be viewed by the friend terminal 5. That is, when a friend avatar Af is in the user's My Garage G, it is preferable that the friend terminal 5 displays the information obtained from the application provider server 1 on the display screen 5d (see Figure 7) of the friend terminal 5 when the operation to view the above information is performed. This allows friends to also see the information of the digital vehicle D owned by the user, and the same effects as those for the user can be expected for friends. In this case, at least the "Details" menu must be displayed on the display screen 4d of the friend terminal 5, and the friend terminal 5 only needs to obtain the information from the application provider server 1 when the friend performs the viewing operation.

[0097] Furthermore, in this experience system, the use of the digital vehicle includes at least driving, customization, viewing, and riding, but the application provider server 1 prohibits friend terminal 5 from driving, customizing, and riding. In other words, friends cannot drive, customize, or ride in the digital vehicle D owned by the user. However, the application provider server 1 will lift the prohibition on friend terminal 5 from riding in digital vehicle D only if it receives a ride request notification from user terminal 4 indicating that the friend wishes to ride along while driving digital vehicle D. That is, a friend can ride in the user's digital vehicle D only if the user has given permission for them to do so.

[0098] This configuration allows users to drive (experience driving) and customize their digital vehicle D in the metaverse space, thereby further enhancing the user experience. On the other hand, while friends can view the user's digital vehicle D, they cannot drive or customize it, thus protecting the user's digital vehicle D. However, if the user wishes for a friend to ride along, the friend can ride in the digital vehicle D. In this way, by allowing friends only minimal (trial) usage, there is a possibility that friends will want to own the digital vehicle themselves, thus establishing an effective business model.

[0099] Finally, we will explain the contents of the experience system, including the NFT management server 2. In the experience system, the NFT management server 2 and the NFT issuing unit described above may also perform their functions. For example, a user may NFT their customized digital vehicle D, or NFT digital vehicle D and My Garage G as a set. In this case, the user selects the digital product they want to NFT on the user terminal 4 and performs the operation to NFT. Here, we will illustrate the case of NFT digital vehicle D and My Garage G as a set.

[0100] When the application server 1 (Mint function unit 11a) receives an NFT request from the user terminal 4 to create an NFT of the set of digital vehicle D and My Garage G, the NFT issuing unit (for example, Mint function unit 11a or another server) issues an NFT to the user based on the set of digital vehicle D and My Garage G in response to the received NFT request. The NFT is then stored in the user's wallet. When the set of digital vehicle D and My Garage G is created as an NFT, the application function unit 10 manages both the digital vehicle D and My Garage G as unusable.

[0101] When the NFT management server 2 receives a request to list an NFT from the user terminal 4, it lists the NFT on the NFT marketplace. This allows the user to resell their previously owned (used) digital vehicle D and My Garage G while giving them asset value as NFTs, thereby enhancing the user experience. Note that the digital products to be converted into NFTs are not limited to the set of digital vehicle D and My Garage G; it can be just one digital vehicle D, a set of multiple digital vehicle Ds, or a set of multiple digital vehicle Ds and My Garage Gs.

[0102] Furthermore, if a user who owns only one digital vehicle D converts digital vehicle D into an NFT and sells it, only the empty My Garage G, which does not contain digital vehicle D, may continue to be displayed, or it may be hidden. Also, for a second user who acquires digital vehicle D by burning the purchased NFT, a My Garage associated with the second user may be assigned at the time of burning, or if the second user already owns a My Garage, a My Garage may not be assigned.

[0103] [3-2. Drive Experience System] Next, the drive experience system will be explained. The drive experience system is also part of the utilization system described above. As with the drive experience system, we will first explain what is implemented by the application provision server 1 and terminals 4 and 5. The digital vehicle D is the same as that of the experience system described above. The drive experience system is implemented when the drive experience system item is selected from the menu M exemplified in Figure 4. In other words, the drive experience system can be implemented while the experience system described above is being implemented.

[0104] The user terminal 4 displays a metaverse space including the user avatar Au on its display screen 4d, and also displays the digital vehicle D in a manner that allows it to be used in the metaverse space. Furthermore, when driving the digital vehicle D (for example, one of the "Race," "Free Drive," or "Drive Together" options in menu M in Figure 4) is selected, the user terminal 4 displays the digital vehicle D with the user avatar Au seated in the driver's seat in a manner that allows it to be driven on the display screen 4d. This allows the user to put their own avatar Au in the digital vehicle D and operate it, thereby improving the user experience through the feeling of "owning a car."

[0105] Furthermore, a predetermined animation may be displayed when the user avatar Au gets into the driver's seat. This animation may be fixed or variable, and may be the same as the animation that plays when "Test Drive" is selected, for example. Displaying the animation can give the user the same sense of excitement as when actually getting into a vehicle. This animation may be controlled by the application server 1 or by the user terminal 4. The animation may also be omitted.

[0106] The driving experience system allows for a driving experience similar to that of the real world. For example, when a user operates a digital vehicle D, the digital vehicle D behaves similarly to a real-world vehicle (e.g., acceleration during EV or hybrid driving, quietness during EV driving, cornering behavior, braking behavior, etc.). To achieve this, the application provision server 1 stores behavior information of the digital vehicle D, which is generated based on control information set for a real-world vehicle. When a driving operation is performed on the user terminal 4, the system displays the behavior of the digital vehicle D corresponding to that operation on the display screen 4d, based on the behavior information obtained from the application provision server 1. In other words, the application provision server 1, in output control, causes the digital vehicle D to exhibit performance in the metaverse space similar to that of a real-world vehicle. This makes it possible to give the user the same feeling as when driving an actual vehicle when operating the digital vehicle D. Here, "performance" is an example of the characteristics of digital product information, and "behavior information" is an example of "characteristics" recorded in, for example, the digital product DB 12c.

[0107] Furthermore, in this specific example, even when driving operations are performed on the user terminal 4 (i.e., while driving), it is possible to switch the image displayed on the display screen 4d (the user's view) between a first-person perspective and a third-person perspective. When the first-person perspective is set during driving, the application provider server 1 or the user terminal 4 performs gaze control to change the gaze of the user avatar Au, who is sitting in the driver's seat, according to the gaze change operation on the user terminal 4. Then, based on the gaze of the user avatar Au changed by the gaze control, the user terminal 4 displays at least one of the surrounding scenery of the digital vehicle D and the interior scenery of the vehicle D, including the interior of the digital vehicle D, on the display screen 4d.

[0108] In other words, when a user performs an operation to change the gaze of the user avatar Au (gaze change operation), the direction in which the user avatar Au looks changes, and in conjunction with this, the image displayed on the 4D display screen also changes to reflect the scenery that the user avatar Au is seeing. As a result, the user can see the exact scenery that the user avatar Au is seeing on the 4D display screen, which brings them closer to the feeling of actually driving in the metaverse space.

[0109] For example, Figures 5 and 6 show examples of images displayed on the display screen 4d when driving operations are being performed on the user terminal 4. In Figure 5, the display screen 4d shows the user avatar Au facing forward and driving, from the user avatar Au's first-person perspective. In this example, only the hands holding the steering wheel are displayed for the user avatar Au, and the interior view of the vehicle, such as the instrument panel and steering wheel, as seen from the user avatar Au seated in the driver's seat, as well as the surrounding scenery in front of the vehicle, are displayed. In Figure 6, the display screen 4d shows the digital vehicle D from the third-person perspective of either the digital vehicle D or the user avatar Au. In this example, the user avatar Au is not displayed, and an overhead view of the digital vehicle D, seen from behind and above, is displayed along with the surrounding scenery.

[0110] Figures 5 and 6 show a back button 62, which is operated when ending a drive, and a view switching button 63, which is operated when switching between first-person and third-person views. The user can end a drive by tapping the back button 62. In this case, the digital vehicle D returns to My Garage G. The user can also switch between first-person and third-person views by tapping the view switching button 63. These buttons 62 and 63 are just examples. Other operation buttons (for example, the camera mode switching button 64 and voice chat button 65, and the autopilot button shown in Figure 7 later) may be provided, and ending a drive or switching views does not have to be done by button operation. Figure 5 also shows a timer 66 that counts the drive time, and Figure 6 also shows two meters 67 (speedometer, power meter, tachometer, etc.), but these are also just examples and can be changed or omitted. For example, the two meters 67 may be displayed on the instrument panel of the display screen 4d shown in Figure 5.

[0111] The above-mentioned gaze control may be performed by the application server 1 or by the user terminal 4. In the former case, the application server 1 receives a signal based on the gaze change operation from the user terminal 4 and sends the result of the gaze control performed based on that signal (a signal related to the gaze of the user avatar Au) to the user terminal 4. On the other hand, in the latter case, the user terminal 4 receives the gaze change operation, performs gaze control based on that operation, and changes the gaze of the user avatar Au, so the processing is completed by the user terminal 4 alone.

[0112] By the way, the menu M of the driving experience system in this example has three options: "Race," "Free Driving," and "Drive Together." "Race" is a mode in which the user participates alone in a race held in the metaverse space and competes for the best time. "Free Driving" is a mode in which the user can drive freely alone in the metaverse space. All of these modes have in common that only the user avatar Au is in the digital vehicle D, and the user controls the driving on the user terminal 4.

[0113] On the other hand, "Drive Together" is a mode in the metaverse space where users can drive with their friends. "Drive Together" can be implemented mainly in the following way: (1) The user selects a friend from the friend list to drive with. (2) An invitation notification is sent to the selected friend's friend terminal 5. (3) The friend's terminal 5 performs an operation to accept the invitation notification. (4) The user avatar Au is placed in the driver's seat of the digital vehicle D stored in My Garage G, and the friend avatar Af is placed in a different position. (5) The user terminal 4 takes the driving operation and sets off on a drive together. (6) When the user terminal 4 performs the operation to end the driving operation, the digital vehicle D returns to My Garage G. (7) When the friend terminal 5 performs the operation to end the ride, only the friend avatar Af returns to the user's My Garage G.

[0114] To achieve (1) and (2) above, when the user terminal 4 performs an operation to invite a friend to a drive, the application provider server 1 sends an invitation notification to the friend terminal 5 of the invited friend and grants permission to this friend terminal 5 to ride in the digital vehicle D. The "operation to invite someone to a drive" is, for example, the operation of displaying a friend list on the display screen 4d and selecting a friend from that friend list. The upper limit of the number of friends that can be selected is set to the number obtained by subtracting 1 from the passenger capacity of the digital vehicle D (for example, 3 if the digital vehicle D is a 4-seater).

[0115] To achieve (3) and (4) above, the application server 1 places the friend avatar Af in the designated seat of the digital vehicle D when the authorized friend terminal 5 performs a passenger boarding operation in the digital vehicle D. "A passenger boarding operation is performed" refers, for example, to a situation where the invitation notification sent to the friend terminal 5 includes the options "Accept" and "Reject," and "Accept" is selected within a specified time after the invitation notification is sent. On the other hand, if "Accept" is not selected within the specified time, or if "Reject" is selected, it can be determined that the friend does not wish to drive together, and this does not constitute "a passenger boarding operation is performed."

[0116] Here, the "designated seat" mentioned above becomes the passenger seat if the passenger ride operation is performed on one friend terminal 5, and becomes any seat in the passenger seat or rear seat if the passenger ride operation is performed on multiple friend terminals 5. In other words, if only one friend rides along within a predetermined time after the invitation notification is sent, that friend avatar Af will always be placed in the passenger seat. On the other hand, if multiple friends ride along within a predetermined time after the invitation notification is sent, each friend avatar Af will be randomly placed in a seat (passenger seat or rear seat). With this configuration, a scene similar to driving in the real world can be realized in the metaverse space, improving the user experience. Note that the animation mentioned above may also be displayed on the display screen 5d of the friend terminal 5 when a friend avatar Af gets into the digital vehicle D.

[0117] To realize (5) above, the user terminal 4 displays the digital vehicle D on the display screen 4d in a manner that allows it to be driven in the metaverse space. If a first-person perspective is set during this drive, the application server 1 or the user terminal 4 may perform the gaze control described above. The application server 1 or the friend terminal 5 may also perform the same type of control as described above, that is, gaze control that changes the gaze of the friend avatar Af riding in the digital vehicle D according to the gaze change operation on the friend terminal 5.

[0118] The user terminal 4 displays at least one of the in-car scenery and the friend avatar Af on the display screen 4d based on the gaze of the user avatar Au, which is changed by the gaze control described above. Similarly, the friend terminal 5 displays at least one of the in-car scenery and the user avatar Au on the display screen 5d based on the gaze of the friend avatar Af, which is changed by the gaze control described above. This configuration provides both the user and their friend with a feeling similar to driving in the real world, further improving the user experience.

[0119] Figure 7 shows an example of the image displayed on the display screen 5d of a friend's terminal 5 while driving operations are being performed on the user terminal 4. The display screen 5d in Figure 7 shows the user avatar Au facing forward and driving, from the first-person perspective of the friend avatar Af positioned in the passenger seat. In this example, both the user avatar Au and the interior scenery of the car are displayed on the display screen 5d. In addition to the interior scenery and at least one of the avatars Au and Af, the surrounding scenery may also be displayed.

[0120] Figure 7 also shows a camera mode switch button 64, which is operated when switching to camera mode; a voice chat button 65, which is operated when making a voice chat; and a chat display unit 68, which displays an open chat window. By tapping the camera mode switch button 64, the user can switch to camera mode to take pictures or record the video displayed on the display screen 5d; by tapping the voice chat button 65, the user can have a voice conversation with a friend; and by tapping the chat display unit 68, the user can exchange messages in an open chat window.

[0121] In this example, if the user terminal 4 performs an operation to switch to a third-person view while the above-mentioned gaze control is being implemented, the application server 1 or user terminal 4 switches the control over the user terminal 4 from the above-mentioned gaze control to an overhead view control. Based on the overhead view control, the user terminal 4 displays an overhead view image on the display screen 4d, which includes the overall appearance of the digital vehicle D and the surrounding scenery. The overhead view control is a control that changes the overhead view image of the digital vehicle D, which is displayed together with the surrounding scenery, according to the change operation performed by the user terminal 4. With the overhead view control, for example, it is possible to get closer to the digital vehicle D, view the digital vehicle D from a higher vantage point, or view the digital vehicle D from the side.

[0122] Similarly, if the app provider server 1 or friend terminal 5 switches to a third-person view while the above-mentioned gaze control is being implemented, the friend terminal 5 switches control to the above-mentioned overhead view control. Based on this overhead view control, the friend terminal 5 displays the overhead view on the display screen 5d. This configuration enhances the user experience by realizing the unique enjoyment of driving in the metaverse space (i.e., an experience that cannot be had in the real world). Note that the overhead view displayed on the friend terminal 5 changes according to the changes made on the friend terminal 5, and therefore does not necessarily match the overhead view displayed on the user terminal 4. Also, the user terminal 4 may display a first-person view, while the friend terminal 5 displays a third-person view. However, although the view is different, the user and friend share the same driving space.

[0123] To realize (6) above, the application provider server 1 or user terminal 4 performs user return control, which returns the digital vehicle D to My Garage G when an operation to end the driving operation is performed on the user terminal 4 (i.e., during a drive). The "operation to end the driving operation" is, for example, tapping the back button 62 on the display screen 4d. To realize (7) above, the application provider server 1 or friend terminal 5 performs friend return control, which returns only the friend avatar Af on the friend terminal 5 to My Garage when an operation to end the ride is performed on the friend terminal 5. In other words, if the user ends the drive during a drive with a friend, the digital vehicle D returns to My Garage G, but if the friend leaves the drive, only the friend returns to the user's My Garage G. In this way, by increasing the freedom of friends to return, friends can easily participate in drives.

[0124] Finally, the details of the drive experience system, including the NFT management server 2, will be explained. In the drive experience system, the NFT management server 2 and the NFT issuing unit described above may also perform their functions. For example, a user may create an NFT of video footage (drive video) of themselves driving their customized digital vehicle D. In this case, the user takes a picture or records the drive video they want to create an NFT of on the user terminal 4 by tapping the camera mode switching button 64 displayed on the display screen 4d, and performs the operation to create the NFT.

[0125] When the application provision server 1 (Mint function unit 11a) receives an NFT conversion request from the user terminal 4 to convert the drive video of the digital vehicle D into an NFT, the NFT issuing unit (e.g., Mint function unit 11a or another server) issues an NFT based on the drive video to the user in response to the received NFT conversion request. The NFT is then stored in the user's wallet. Once the drive video has been converted into an NFT, the application function unit 10 manages the drive video by making it unavailable to the user terminal 4. When the NFT management server 2 receives a request from the user terminal 4 to list an NFT, it lists the NFT on the NFT marketplace. This allows the user's experienced scenes (drive video) to be circulated with asset value in the form of an NFT, thereby enhancing the user experience.

[0126] [4. Effects] (1) According to the above-described utilization system and method, users can use digital products in the metaverse space (e.g., view, watch, operate, customize) using their own terminal 4, and furthermore, they can convert those digital products (digital products after use) into NFTs and sell them. When selling, by converting the digital products they have used into NFTs, the uniqueness and immutability of the digital products can be guaranteed. In other words, by selling the used digital products as NFTs instead of selling them as they are, the unique digital products (NFTs) can be given asset value and circulated in the secondary market. Therefore, it becomes possible to build a system with high utilization value for digital products.

[0127] (2) Furthermore, a second user who purchases an NFT listed on the NFT marketplace can own that NFT as an asset, and can also deactivate (burn) the NFT to turn it into a digital product and use that digital product in the metaverse space. Moreover, they can turn the used digital product into an NFT and sell it. In this way, according to the utilization system and method described above, it is possible to build a system (creator economy) in which services related to digital products circulate.

[0128] (3) In the above-described utilization system and method, the application function unit 10 disables the digital product in the output control after the NFT based on the digital product has been issued by the NFT issuing unit. In other words, after the digital product has been converted into an NFT, even the original user will not be able to use the digital product, thus ensuring the uniqueness and non-tampering of the digital product.

[0129] (4) Furthermore, if the digital product is a digital vehicle, the application function unit 10 outputs the digital vehicle in a manner that allows it to be driven and customized in the output control described above. In other words, it is possible to own one's own vehicle (digital vehicle) in the metaverse space, and to drive and customize that vehicle in the metaverse space. This can improve the user experience, such as the emotions the user experiences through "owning a car," the impressions the user has, and the user's reactions. It is also possible to sell one's own customized car as an NFT, which can provide an experience similar to "selling a used car" in the real world, and can contribute to further improvement of the user experience.

[0130] (5) If the digital product is a digital vehicle sold by an automobile manufacturer to a user, the application function unit 10 associates the digital vehicle with the user who purchased it. In other words, the user can purchase a digital vehicle sold by an automobile manufacturer in the metaverse space, just as in the real world, and the purchased digital vehicle is associated with the user. This allows the user to more easily experience something similar to "buying and owning a vehicle" in the real world, which can contribute to further improvement of the user experience.

[0131] (6) If the digital product is a digital vehicle that has been digitized from a vehicle that an automobile manufacturer has handled in the real world, the application function unit 10 may, in the output control described above, cause the digital vehicle to exhibit the same performance as the real-world vehicle. In this case, the user can drive a digital vehicle in the metaverse space that has the same performance (features, specifications) as a real-world vehicle, and thus easily obtain an experience similar to that of driving a real-world vehicle.

[0132] (7) If the above-described application provision server 1 (server) is equipped with an application function unit 10 as a first control unit, a mint function unit 11a as a second control unit, and a function as an issuing unit (NFT issuing unit), the flow of symbols A1 to A4 shown in Figure 1 can be realized. Therefore, the same effect as in (1) above can be obtained. (8) Furthermore, if the above-described application provision server 1 (server) is further equipped with a digital product conversion unit 11b as a third control unit and a function as an invalidation unit (NFT invalidation unit), the flow of symbols A1 to A8 shown in Figure 1 can be realized. Therefore, the same effect as in (2) above can be obtained.

[0133] [5. Others] The above-mentioned utilization systems and methods are merely examples. For example, the digital product does not have to be the digital vehicle described above; it may also be digital data such as voice, music, images (pictures or drawings), or videos. Furthermore, even if the digital product is a digital vehicle, it does not have to be a digitized version of a vehicle that the automobile manufacturer has actually handled in the real world. It should be noted that the above-mentioned specific examples are, of course, not essential components for the utilization system.

[0134] In the utilization system, the flow shown by symbols A5 to A8 in Figure 1 may be omitted. Also, the software configuration of the utilization system shown in Figure 3 may be merged in any combination, or each component may be separated.

[0135] The above-described utilization system uses a client-server type communication and processing configuration as an example, with terminals 4 and 5 acting as clients and application provision server 1, NFT management server 2, and user management server 3 acting as servers. However, it is not limited to this configuration. At least a portion of the communication and processing performed in the utilization system may include, for example, a P2P (Peer to Peer) configuration in which communication and processing are performed between terminals 4 and 5, or various other configurations.

[0136] 1. Application provision server (first server, server) 2. NFT management server (second server) 4, 4A. Terminal, user terminal 4B. Terminal, second terminal, user terminal 10. Application function unit (first control unit) 11. NFT function unit 11a. Mint function unit (second control unit, NFT issuing unit, issuing unit) 11b. Digital product conversion unit (third control unit, NFT deactivation unit, deactivation unit) 12. DB (database) D. Digital vehicle (digital product)

Claims

1. A digital product utilization system comprising: a first server having a first control unit that performs display control to display a metaverse space on a user's terminal and output control to output a digital product associated with the user in the metaverse space in a manner usable by the terminal; and a second control unit that receives an NFT request for the digital product from the terminal; an NFT issuing unit that issues an NFT based on the digital product to the user in response to the NFT request received by the second control unit; and a second server that manages an NFT marketplace and, when it receives a request to list the NFT from the terminal, lists the NFT in the NFT marketplace.

2. The digital product utilization system according to claim 1, further comprising an NFT invalidation unit for invalidating the NFT sold by the second server, wherein the second server, upon receiving a purchase request for the NFT listed on the NFT marketplace, sells the NFT to a second user having a second terminal that sent the purchase request, the first server has a third control unit that receives a digital productization request for the NFT sold by the second server from the second terminal, the third control unit, in response to the digital productization request received, invalidates the NFT sold by the second server using the NFT invalidation unit to make it a digital product, the first control unit associates the digital product with the second user and performs the display control and output control for the second terminal, and the second control unit receives an NFTization request from the second terminal for the digital product associated with the second user.

3. The digital product utilization system according to claim 1, characterized in that the first control unit disables the digital product in output control after the NFT based on the digital product has been issued by the NFT issuing unit.

4. The digital product is a digital vehicle usable in the metaverse space, and the first control unit outputs the digital vehicle in a manner that allows it to be driven and customized, as described in any one of claims 1 to 3.

5. The digital product utilization system according to claim 4, wherein the digital vehicle is sold to the user by an automobile manufacturer, and the first control unit associates the digital vehicle with the user who purchased it.

6. The digital vehicle is a digitalized version of a vehicle that the automobile manufacturer has handled in the real world, and the first server, in output control, causes the digital vehicle to exhibit performance similar to that of the vehicle, as described in claim 5.

7. A method for utilizing digital products, characterized in that the first server, through its first control unit, performs display control to display a metaverse space on the user's terminal and outputs a digital product associated with the user in the metaverse space in a manner usable by the terminal; the second control unit receives an NFT request for the digital product from the terminal; the NFT issuing unit issues an NFT based on the digital product to the user in response to the NFT request received by the second control unit; and the second server manages an NFT marketplace and, when it receives a request to list the NFT from the terminal, lists the NFT in the NFT marketplace.

8. The method for utilizing a digital product according to claim 7, characterized in that the second server, upon receiving a purchase request for the NFT listed on the NFT marketplace, sells the NFT to a second user who has a second terminal that sent the purchase request; the first server, via a third control unit, receives a digital productization request from the second terminal regarding the NFT sold by the second server; the NFT invalidation unit, in response to the digital productization request received by the third control unit, invalidates the NFT sold by the second server to make it a digital product; the first server, via a first control unit, associates the digital product with the second user and performs the display control and output control for the second terminal; and the second control unit receives an NFTization request from the second terminal regarding the digital product associated with the second user.

9. A server that sends and receives data with a user's terminal, comprising: a first control unit that performs display control to display a metaverse space on the terminal and output control to output a digital product associated with the user in the metaverse space in a manner usable by the terminal; a second control unit that receives an NFT request for the digital product from the terminal; and an issuing unit that, in response to the NFT request, issues an NFT to the user based on the digital product and that can be listed on an NFT marketplace managed by the second server.

10. The server according to claim 9, further comprising: a third control unit that receives a request to digitize the NFT sold by the second server from a second terminal that has sent a purchase request for the NFT listed on the NFT marketplace; and a deactivation unit that, in response to the request to digitize the NFT sold by the second server, deactivates the NFT to digitize it in response to the request to digitize it received by the third control unit, wherein the first control unit associates the digital product with a second user having the second terminal and performs the display control and output control for the second terminal; and the second control unit receives an NFT request from the second terminal regarding the digital product associated with the second user.

Images