Driving experience system, and server

Abstract

This driving experience system comprises a terminal (4) that is operated by a user, and a server that is provided so as to be able to communicate with the terminal (4). The terminal (4) displays, on a display screen (4d) thereof, a metaverse space including an avatar (Au) of the user, and when an operation for purchasing a prescribed digital vehicle (D) in the metaverse space is performed, transmits a purchase signal for the digital vehicle (D) to the server. Upon receiving the purchase signal, the server associates the digital vehicle (D) and a garage (G) in which the digital vehicle (D) is stored with the user, and configures the digital vehicle (D) and the garage (G) to be usable using the terminal (4). The terminal (4) displays, on the display screen (4d), the digital vehicle (D) in a mode in which the same can be used in the metaverse space, and when driving of the digital vehicle (D) is selected, displays, on the display screen (4d), the digital vehicle (D) in which the avatar (Au) has boarded the driver's seat, in a mode in which driving operation is possible.

Description

Drive experience system and server

[0001] This case relates to a drive experience system and a server provided in the system.

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

[0003] Japanese Patent No. 6644928

[0004] The merit of the metaverse is that it can relatively easily realize things that cannot be realized or are difficult to realize in the real world. For example, in the real world, owning a vehicle naturally requires a high cost, and securing a parking lot and maintenance are also necessary, so the hurdle for owning a vehicle in the real world is relatively high. In contrast, in the metaverse space, it is possible to lower this hurdle. Therefore, by using the metaverse space, users who have difficulty owning a vehicle in the real world (such as young people in their twenties and elderly people after returning their driver's licenses) can easily experience owning their own vehicle, and an improvement in user experience such as the emotions experienced by users, the impressions held by users, and the reactions of users through owning a vehicle can be expected.

[0005] This case was devised in light of the above problems, and one of its purposes is to improve the user experience through owning a vehicle by using the metaverse space. In addition, not limited to this purpose, achieving effects that can be derived from each configuration shown in the "Mode for Carrying Out the Invention" described later and that cannot be obtained by the conventional technology is also another purpose of this case.

[0006] The disclosed drive experience system and server can be implemented in the following manner (examples of application) and solve at least some of the above-mentioned problems. Manners 1 to 8 relate to the drive experience system. Manners 2 to 8 are all additional manners that can be appropriately selected and all are optional. Manners 2 to 8 do not disclose any manners or configurations that are indispensable to this case. Furthermore, manner 9 relates to the server. Manner 9 can be modified to include configurations corresponding to manners 2 to 7.

[0007] Embodiment 1. The disclosed drive experience system comprises a terminal operated by a user and a server provided to communicate with the terminal. The terminal displays a metaverse space including the user's avatar on its display screen, and when an operation to purchase a predetermined digital vehicle is performed in the metaverse space, it sends a purchase signal for the digital vehicle to the server, and when the server receives the purchase signal, it associates the digital vehicle and the garage in which the digital vehicle is stored with the user and makes the digital vehicle and the garage available for use by the terminal, and the terminal displays the digital vehicle on the display screen in a manner that allows it to be used in the metaverse space, and when driving the digital vehicle is selected, the digital vehicle with the avatar seated in the driver's seat is displayed on the display screen in a manner that allows it to be driven.

[0008] Embodiment 2. In Embodiment 1 described above, it is preferable that the digital vehicle is a digital representation of a vehicle that the automobile manufacturer has handled in the real world. In this case, it is preferable that the terminal stores behavior information of the digital vehicle generated based on control information set in the vehicle, and when the driving operation is performed, the terminal displays the behavior of the digital vehicle corresponding to the driving operation on the display screen based on the behavior information obtained from the server.

[0009] Embodiment 3. In Embodiment 1 or 2 described above, the server or the terminal preferably performs gaze control to change the gaze of the avatar sitting in the driver's seat in accordance with the gaze change operation on the terminal when the driving operation is performed on the terminal, and the terminal preferably displays at least one of the surrounding scenery of the digital vehicle and the interior scenery of the digital vehicle, including the interior, on the display screen based on the gaze changed by the gaze control.

[0010] Embodiment 4. In any one of embodiments 1 to 3 above, it is preferable that the drive experience system comprises a plurality of friend terminals operated by friends registered in the user's friend list on the server. In this case, it is preferable that when an operation to invite a friend to a drive is performed on the terminal, the server sends an invitation notification to the friend terminal of the invited friend, and permits the friend terminal to ride in the digital vehicle, and when the permitted friend terminal performs an operation to ride in the digital vehicle, the server places the friend's friend avatar in a predetermined seat in the digital vehicle. Furthermore, it is preferable that the predetermined seat is the passenger seat when the ride operation is performed on one friend terminal, and any seat in the passenger seat and rear seats when the ride operation is performed on multiple friend terminals.

[0011] Embodiment 5. In Embodiment 4 described above, it is preferable that the server, the terminal, or the friend terminal performs gaze control to change the gaze of the avatar and the friend avatar riding in the digital vehicle, respectively, in accordance with the gaze change operations on the terminal and the friend terminal, when the driving operation is performed on the terminal. In this case, it is preferable that the terminal displays at least one of the interior scenery of the digital vehicle and the friend avatar on the display screen based on the gaze of the avatar changed by the gaze control, and the friend terminal displays at least one of the interior scenery and the avatar on the display screen of the friend terminal based on the gaze of the friend avatar changed by the gaze control.

[0012] Embodiment 6. In Embodiment 5 described above, it is preferable that, while the gaze control is being performed, the server or the terminal switches control to overhead view control when the terminal is switched to a third-person view, and the terminal displays an overhead view image on its display screen, including the overall appearance of the digital vehicle and the surrounding scenery, based on the overhead view control. Furthermore, it is preferable that, while the gaze control is being performed, the friend terminal switches control to overhead view control when the friend terminal is switched to a third-person view, and the friend terminal displays the overhead view image on its display screen, based on the overhead view control.

[0013] Embodiment 7. In any one of embodiments 4 to 6 described above, it is preferable that the server or the terminal performs user return control to return the digital vehicle to the garage when an operation to terminate the driving operation is performed on the terminal, and the server or the friend terminal of the passenger performs friend return control to return only the friend avatar of the friend terminal to the garage when an operation to terminate the ride is made from the friend terminal.

[0014] Embodiment 8. In any one of embodiments 1 to 7 described above, the drive experience system preferably further comprises an NFT issuing unit that issues NFTs and an NFT management server that manages an NFT marketplace. In this case, the server preferably receives an NFT conversion request from the terminal to convert the drive video of the digital vehicle into an NFT, the NFT issuing unit preferably issues an NFT based on the drive video to the user in response to the NFT conversion request received by the server, and the NFT management server preferably prefers to list the NFT on the NFT marketplace when it receives a listing request for the NFT from the terminal.

[0015] Embodiment 9. The disclosed server is a server that sends and receives data to and from a terminal operated by a user, and comprises: a first control unit that performs first control to display the metaverse space and the user's avatar on the display screen of the terminal; a receiving unit that receives a signal from the terminal to purchase a predetermined digital vehicle; a storage unit that, upon receiving the signal in the receiving unit, stores the digital vehicle and the garage in which the digital vehicle is stored in association with the user; a second control unit that, after the association, performs second control to display the digital vehicle in the metaverse space in a manner usable by the terminal; and a third control unit that, when driving the digital vehicle is selected, performs third control to display the digital vehicle with the avatar seated in the driver's seat on the display screen in a manner that allows it to be driven.

[0016] According to the disclosed drive experience system and server, it is possible to improve the user experience through vehicle ownership by utilizing the metaverse space.

[0017] This figure shows the flow of digital products in a digital product utilization system including a drive experience 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 drive experience system and a digital product utilization system including the same 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.

[0018] Referring to the drawings, a drive experience system and a server as embodiments (examples) will be described. The embodiments shown below are merely illustrative, and there is no intention to exclude various modifications and applications of technologies not explicitly stated 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.

[0019] [1. Overview] The driving experience system is a system that allows users to experience driving a digital vehicle in a metaverse space (virtual space, also simply called the metaverse). A digital vehicle is a vehicle such as a car, truck, bus, or motorcycle in digital form that can be owned, used, and bought and sold as digital data.

[0020] The types of digital vehicles are not particularly limited and may include, for example, gasoline vehicles, electric vehicles (EVs), hybrid vehicles (HEVs), and plug-in hybrid vehicles (PHEVs). A plug-in hybrid vehicle refers to a hybrid vehicle that can be externally charged to its battery or receive external power from its battery. Plug-in hybrid vehicles are equipped with a charging port (inlet) for inserting a charging cable that receives power from an external charging facility, and an outlet for external power supply.

[0021] The driving experience system may be included in a digital product utilization system (hereinafter also referred to as the "utilization system") that enhances the value of digital products usable in the metaverse space. A digital product is a product in a digital format that can be owned, used, or bought and sold as digital data, and is also called a digital commodity, object, digital asset, or digital content. The digital vehicle described above is an example of a digital product. In addition to the digital vehicle described above, digital products may include digital data such as audio, music, images (pictures and drawings), and videos. Furthermore, "use" as used here includes viewing, appreciating, listening to, operating, modifying, editing, and customizing digital products.

[0022] The following explanation will first detail the application system, including the driving experience system. Note that in the application system, digital products will be described instead of digital vehicles, but "digital products" can be replaced with "digital vehicles." Next, the driving experience system will be described in detail as a specific example of the application system. Before describing the driving experience system, the system for experiencing digital vehicles (hereinafter referred to as the "experience system") will also be described in detail. The experience system allows users to experience various aspects of digital vehicles, not just driving.

[0023] 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).

[0024] 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.

[0025] 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.

[0026] 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.

[0027] [2. Utilization System and Method] Below, a utilization system including a drive experience system according to one embodiment will be described in detail with reference to Figures 1 to 3. Figure 1 is a diagram showing the flow of digital products in this 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 this utilization system.

[0028] [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.

[0029] 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.

[0030] 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.

[0031] 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.

[0032] 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.

[0033] 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.

[0034] 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 ensures 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 to an NFT (when the user performs the operation to convert it to an NFT).

[0035] 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.

[0036] 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, by selling digital products as NFTs instead of selling them as they are, it is possible to give asset value to one's own unique digital product (NFT) 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.

[0037] 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.

[0038] When a second user requests the digitalization of an NFT purchased by the second user (see code A7), the application provision 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 provision 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. With this configuration, a system (creator economy) in which services related to digital products circulate can be constructed.

[0039] [2-2. Hardware Configuration Example] Each function of the drive experience system and the utilization system including it according to one embodiment (hereinafter abbreviated as "drive experience system, etc.") can be implemented 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 implement each function of the drive experience system, etc. Furthermore, at least a part of each function of the drive experience system, etc. may be implemented using hardware resources and network resources provided by a cloud environment.

[0040] Figure 2 is a block diagram illustrating the hardware configuration of a computer 50 that implements various functions of a driving experience system. When multiple computers are used as hardware resources to implement various functions of a driving experience 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.

[0041] 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.

[0042] 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.

[0043] The storage unit 53 is an example of hardware that stores various data, programs, and other information. Examples of the storage unit 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 memories. Examples of non-volatile memories include flash memories, SCMs (Storage Class Memories), ROMs (Read Only Memories), and the like. The storage unit 53 may store a program 58 (a digital product utilization program, a digital vehicle experience program, a drive experience program) that realizes all or part of the various functions of the computer 50. For example, the processor 51 can realize functions as a drive experience system or the like (for example, the app providing server 1 and the NFT management server 2 in FIG. 1) by expanding and executing the program 58 stored in the storage unit 53 in the memory 52.

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

[0045] The IO unit 55 includes at least one of an input device and an output device. Examples of the input device include a keyboard, a touch panel, a camera, a mouse, a microphone, a gaze detection device that detects a gaze, a gesture reading device that detects a gesture operation, and the like. Examples of the output device include display devices (monitors) such as liquid crystal displays and organic EL (Electro-Luminescence) displays, projectors, and the like. Further, the IO unit 55 may include a touch panel device in which an input device and a display device are integrated.

[0046] 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.

[0047] 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 connection terminals or devices 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 for accessing a recording disk, a card reader for accessing a flash memory such as an SD card, and the like. Note that 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.

[0048] 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 disk include a flexible disk, a CD (Compact Disc), a DVD (Digital Versatile Disc), a Blu-ray Disc, an HVD (Holographic Versatile Disc), and the like. The flash memory is, for example, a semiconductor memory such as a USB memory or an SD card.

[0049] 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 a bus, etc. of the hardware in the computer 50 may be appropriately performed. Also, the functions of the experience system can be realized by the above-described computer.

[0050] 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 a hardware configuration similar to the computer 50 illustrated in Figure 2, or they may have a hardware configuration that omits at least one component from computer 50, for example, the graphics processing unit 56. If the graphics processing unit 56 is omitted in terminals 4 and 5, the processor 51 may perform screen display control for the display device. [2-3. Software Configuration Example] Next, with reference to Figure 3, a software configuration example of a drive experience system, etc., according to one embodiment will be described. For convenience, in the following description, user terminal 4 will be used as an example, but similar functions may be applied to friend terminal 5.

[0051] <Application Provisioning Server> The application provisioning server 1 of this embodiment comprises an application function unit 10, an NFT function unit 11, and a database (hereinafter referred to as "DB") 12. The functions of the application function unit 10 and the NFT function unit 11 may be realized by a processor 51, shown in Figure 2, provided in the computer 50 which serves as the application provisioning server 1, loading a program 58 into memory 52 and executing it.

[0052] The application function unit 10 communicates with the user management server 3 and the user terminal 4, and mainly performs the display control and output control described above. As shown in Figure 3, the application function unit 10 of this embodiment comprises a user management unit 10a, a digital product management unit 10b, and a display output control unit 10c.

[0053] The user management unit 10a (storage unit) handles overall user management. For example, the user management unit 10a manages the user database 12b (described later), performs authentication processing when creating a user account and when logging in, retrieves user information stored in the user database 12b, and associates users with digital products (recording in the owned digital products database 12d (described later)). As part of the authentication process, the user management unit 10a may, for example, send authentication information from the user terminal 4 to the user management server 3, and provide the functions of the main application 40 to the user if authentication is permitted by the user management server 3.

[0054] The Digital Product Management Unit 10b (receiving unit) handles 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 related to digital products (hereinafter referred to as "digital product information") in the digital product DB 12c 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 the Digital Product Management Unit 10b receives a signal to purchase a predetermined digital product (purchase signal) from the user terminal 4 and sells the digital product to the user in the shop (the user becomes the owner of the digital product), the User Management Unit 10a associates the user with the digital product. The signal to purchase a predetermined digital product is one of the user request signals transmitted from the user terminal 4.

[0055] 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).

[0056] The display output control unit 10c (first control unit, second control unit, third control unit) mainly performs the above-mentioned display control and output control. Display control (first control) is the control to display a metaverse space including the user's avatar on the display screen 4d of the user terminal 4 (see Figures 4 to 6 described later). The metaverse space displayed here may include, in addition to the user's avatar, backgrounds related to the digital product, avatars other than the user, etc. Output control (second control) is the control to output (display) the digital product in a usable manner to the metaverse space displayed on the display screen 4d. Output control may include, for example, control that allows the user to view the digital product or operate and move the digital product in the metaverse space using the user terminal 4. Output control in this embodiment also includes control (third control) that, when driving a digital vehicle is selected, displays a digital vehicle with the user's avatar in the driver's seat on the display screen 4d in a drivable manner.

[0057] 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.

[0058] The Mint function unit 11a 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.

[0059] 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.

[0060] The digital product conversion unit 11b 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.

[0061] 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.

[0062] 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.

[0063] 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.

[0064] 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.

[0065] 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.

[0066] 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.

[0067] 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.

[0068] <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.

[0069] 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.

[0070] 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.

[0071] <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.

[0072] 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.

[0073] 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.

[0074] <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.

[0075] 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.

[0076] 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.

[0077] 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.

[0078] 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.

[0079] [3. Specific Examples] Next, as specific examples of the utilization system, we will explain the experience system and the driving experience system, using Figures 4 to 7. Users can have the following experiences in the experience system. The following experiences are examples of ways in which digital vehicles are "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 views - Become friends with other users - Communicate with friends and show each other your digital vehicles and garages - Test drive a digital vehicle - View information about your digital vehicle - Drive a digital vehicle

[0080] Furthermore, users can experience the following in the driving experience system: • Driving alone (free driving) • Participating in races alone (races) • Inviting friends to drive together (group drives) • Switching between first-person and third-person views while driving • Changing your viewpoint while driving to see the surrounding scenery and interior of the digital vehicle

[0081] [3-1. Digital Vehicle Experience System] The experience system described in this embodiment is part of the utilization system described above. First, the content realized by the application provision server 1 and terminals 4 and 5 of the experience system will be explained. The digital vehicle in this embodiment is to be sold to the user by a real-world automobile manufacturer. Furthermore, the digital vehicle is a digitized version of a vehicle that the automobile manufacturer has handled in the real world. This allows the user to more easily experience in the metaverse space an experience similar to "buying and owning a vehicle" in the real world. Note that "vehicles that have been handled" include not only vehicles currently for sale, but also vehicles that have been sold in the past, vehicles that are currently for sale or have been sold in foreign countries, and vehicles that have been exhibited at motor shows or exhibitions. In other words, the user can 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.

[0082] 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.

[0083] 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.

[0084] 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).

[0085] This type of experience system allows users to easily own a digital vehicle 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.

[0086] 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.

[0087] 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.

[0088] 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 vehicles, including the My Garage, can be 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.

[0089] 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.

[0090] 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.

[0091] 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.

[0092] 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.

[0093] 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.

[0094] 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.

[0095] 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.

[0096] 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.

[0097] 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.

[0098] 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.

[0099] 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.

[0100] 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.

[0101] 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.

[0102] 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.

[0103] 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.

[0104] 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.

[0105] [3-2. Drive Experience System] Next, the drive experience system will be described. The drive experience system in this embodiment is a part of the utilization system described above, and will be described as a system specifically for driving within the experience 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, in this embodiment, the drive experience system can be implemented while the experience system described above is being implemented.

[0106] 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."

[0107] 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.

[0108] 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 "characteristics" of digital product information, and "behavior information" is an example of "characteristics" recorded in, for example, the digital product DB 12c.

[0109] 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.

[0110] 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 makes it feel closer to actually driving in the metaverse space.

[0111] 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.

[0112] 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.

[0113] 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.

[0114] 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.

[0115] 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.

[0116] 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).

[0117] 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."

[0118] Here, the "designated seat" mentioned above becomes the passenger seat if the passenger ride operation is performed on one friend terminal 5, and 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 is realized in the metaverse space. 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.

[0119] 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.

[0120] 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.

[0121] 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.

[0122] 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.

[0123] 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.

[0124] 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 realizes the unique enjoyment of driving in the metaverse space (i.e., an experience that cannot be experienced in the real world). Note that the overhead view displayed on the friend terminal 5 does not necessarily match the overhead view displayed on the user terminal 4, as it changes according to the changes made on the friend terminal 5. Also, the user terminal 4 may display a first-person view, while the friend terminal 5 displays a third-person view. However, although the appearance is different, the user and friend share the same driving space.

[0125] To realize (6) above, the application provider server 1 or user terminal 4 performs user return control to return 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 to return 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. This increases the freedom of friends to return.

[0126] 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.

[0127] When the application provider 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 for sale, it lists the NFT on the NFT marketplace. This makes it possible to circulate the scenes experienced by the user (drive video) with asset value in the form of an NFT.

[0128] [4. Effects] (1) In the above-described drive experience system, when an operation to purchase a predetermined digital vehicle D is performed in the metaverse space displayed on the display screen 4d of the user terminal 4, a purchase signal for the digital vehicle D is transmitted from the user terminal 4 to the application provision server 1. Upon receiving this purchase signal, the application provision server 1 associates the digital vehicle D and My Garage G with the user and makes them available for use on the user terminal 4. The user terminal 4 then displays the digital vehicle D and My Garage G on the display screen 4d in a manner that allows them to be used in the metaverse space. Furthermore, when driving the digital vehicle D is selected (when the user decides to go for a drive), the user terminal 4 displays the digital vehicle D with the user avatar Au in the driver's seat on the display screen 4d in a manner that allows for driving operation.

[0129] Therefore, according to the aforementioned driving experience system, users can easily own a digital vehicle D in the metaverse space as long as they have a user terminal 4, and can drive the digital vehicle D with their own avatar (user avatar Au). This improves the user experience. In addition, when a digital vehicle D is purchased, a My Garage G where the digital vehicle D is stored is included as a set, so an environment similar to the real world is realized in the metaverse space. Therefore, the added value of the digital vehicle D, including My Garage G, can be increased, and the user experience can be further improved.

[0130] (2) The digital vehicles described above are digitized versions of vehicles that automobile manufacturers have handled in the real world. The application server 1 stores behavioral information of the digital vehicle D, which is generated based on control information set in the real-world vehicle. When a driving operation is performed on the user terminal 4 (i.e., while driving), the behavioral information is used to display the behavior of the digital vehicle D corresponding to that driving operation on the display screen 4d. This makes it possible to give the user the same feeling as when driving an actual vehicle when driving the digital vehicle D in the metaverse space, thereby improving the user experience.

[0131] (3) In the above-described driving experience system, the gaze of the user avatar Au, who is sitting in the driver's seat, is changed according to the gaze change operation on the user terminal 4. Based on the changed gaze of the user avatar Au, the user terminal 4 displays the surrounding scenery and the interior scenery of the digital vehicle D on the display screen 4d. In other words, when the 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 display screen 4d also changes to the scenery that the user avatar Au is seeing. As a result, the user can see the scenery that the user avatar Au is seeing on the display screen 4d, which brings the user closer to the feeling of actually driving in the metaverse space.

[0132] (4) The above-described drive experience system includes multiple friend terminals 5 in addition to the user terminal 4. 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 corresponding friend terminal 5 and grants that friend terminal 5 permission to ride in the digital vehicle D. This allows the user to invite friends and enjoy a drive together in the metaverse space. Furthermore, when a ride-along operation is performed on an authorized friend terminal 5, the application provider server 1 places the friend avatar Af in the designated seat. Specifically, if only one friend performs the ride-along operation, the friend avatar Af is automatically placed in the passenger seat, and if multiple friends perform the ride-along operation, the friend avatar Af is placed randomly. With this configuration, a scene similar to a real-world drive can be realized in the metaverse space, improving the user experience.

[0133] (5) According to the above-described driving experience system, the viewpoints of user avatar Au and friend avatar Af, who are both riding in the same digital vehicle D, can be changed by user terminal 4 and friend terminal 5, respectively. The view from user avatar Au is displayed on user terminal 4, and the view from friend avatar Af is displayed on friend terminal 5. This configuration provides both the user and their friend with a feeling similar to driving in the real world, thereby improving the user experience.

[0134] (6) In the above-described driving experience system, when the user terminal 4 switches to a third-person view, an overhead view is displayed on the display screen 4d of the user terminal 4, and when the friend terminal 5 switches to a third-person view, an overhead view is displayed on the display screen 5d of the friend terminal 5. In this way, both the user and the friend can switch to an overhead view (third-person view) that includes the overall appearance of the digital vehicle and the surrounding scenery. This makes it possible to realize the unique enjoyment of driving in a metaverse space (which cannot be experienced in the real world) and further enhance the user experience.

[0135] (7) In the above-described driving experience system, if the user terminal 4 performs an operation to end the driving operation, the digital vehicle D, along with the user avatar Au and friend avatar Af, returns to My Garage G. On the other hand, if the friend terminal 5, which is a passenger, performs an operation to end the ride, only the friend avatar Af on that friend terminal 5 returns to the user's My Garage G. This increases the freedom of friends to return, allowing friends to easily participate in drives. Furthermore, by making My Garage G the destination of the user who invited the drive, My Garage G can be made the starting point of the drive, creating a situation unique to the metaverse space.

[0136] (8) Furthermore, the aforementioned drive experience system can convert the drive video of the digital vehicle D into an NFT and list that NFT on an NFT marketplace. This allows users to give asset value to the scenes they experienced in the metaverse space and sell them, which can contribute to further improving the user experience.

[0137] (9) The same effect as in (1) above can be obtained if the above-mentioned application provision server 1 (server) includes a display output control unit 10c as a first control unit that displays the metaverse space on the display screen 4d, a digital product management unit 10b as a receiving unit that receives a purchase signal for the digital vehicle D from the user terminal 4, a user management unit 10a as a storage unit that stores the digital vehicle D and My Garage G in association with the user, a display output control unit 10c as a second control unit that outputs the digital vehicle D in a manner that can be used by the user terminal 4 in the metaverse space, and a display output control unit 10c as a third control unit that, when driving the digital vehicle D is selected, displays the digital vehicle D with the user avatar Au in the driver's seat on the display screen 4d in a manner that can be operated.

[0138] [5. Other] The above-described drive experience system is just one example and is not limited to the above configuration. For example, the drive experience system does not have to be included in the utilization system. In other words, the drive experience system does not have to be part of the digital product flow shown in Figure 1. The drive experience system comprises at least a user terminal 4 and a server (e.g., application provision server 1) that is configured to communicate with the user terminal 4, and the user can purchase a digital vehicle in a metaverse space that includes their own avatar, and the purchased digital vehicle and garage are associated with the user as a set, and the user terminal 4 displays the digital vehicle on the display screen 4d in a manner that allows it to be used in the metaverse space, and when driving the digital vehicle is selected, the user avatar is displayed in the driver's seat of the digital vehicle in a manner that allows it to be driven. Other configurations may be changed as appropriate.

[0139] For example, when a driving operation is performed, the behavior of the digital vehicle in response to that operation does not necessarily have to be based on behavior information generated based on control information set in the real-world vehicle. In this case, it is not necessary to store the behavior information of the digital vehicle on the application provision server 1. Furthermore, the digital vehicle does not have to be a digital version of a vehicle that the automobile manufacturer has handled in the real world, nor is it necessary for various information of the real-world vehicle to be accessible in the digital vehicle.

[0140] Furthermore, user return control and friend return control, which are implemented when a user and a friend are driving together, are just examples. Eye-line control and overhead view control are also just examples, and the images displayed on screens 4d and 5d do not necessarily have to correspond to the changes in the gaze of the avatars Au and Af. In addition, the function to convert the driving video of the digital vehicle into NFT is also optional in the driving experience system. Moreover, the friend does not necessarily have to be a user who owns a digital vehicle. In this case, the friend terminal 5 does not need to be equipped with the NFT application 42 (or an equivalent browser function) described above.

[0141] The aforementioned utilization systems and experience systems are merely examples and may be omitted. Furthermore, the aforementioned drive experience system, etc., was given as an example where each of the client terminals 4 and 5 and each of the server terminals (application provision server 1, NFT management server 2, and user management server 3) are in a client-server type communication and processing configuration, but it is not limited to this. At least a part of the communication and processing performed in the drive experience system, etc., 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.

[0142] 1. Application provision server (server) 2. NFT management server 4, 4A. Terminal, user terminal 4B. Terminal, second terminal, user terminal 4d. Terminal display screen 5. Friend terminal (terminal) 5d. Friend terminal display screen 10. Application function unit 10a. User management unit (storage unit) 10b. Digital product management unit (receiving unit) 10c. Display output control unit (first control unit, second control unit, third control unit) 11. NFT function unit 11a. Mint function unit (NFT issuing unit, issuing unit) 12. DB (database) Au. User avatar (user's avatar) Af. Friend avatar (friend's avatar) D. Digital vehicle (digital product) G. My garage (garage)

Claims

1. A driving experience system comprising: a terminal operated by a user; and a server provided to communicate with the terminal, wherein the terminal displays a metaverse space including the user's avatar on its display screen; when an operation to purchase a predetermined digital vehicle is performed in the metaverse space, it transmits a purchase signal for the digital vehicle to the server; when the server receives the purchase signal, it associates the digital vehicle and the garage in which the digital vehicle is stored with the user, and makes the digital vehicle and the garage available for use by the terminal; the terminal displays the digital vehicle on its display screen in a manner that allows it to be used in the metaverse space; and when driving the digital vehicle is selected, it displays the digital vehicle with the avatar seated in the driver's seat on its display screen in a manner that allows it to be driven.

2. The drive experience system according to claim 1, characterized in that the digital vehicle is a digitized version of a vehicle that an automobile manufacturer has handled in the real world, the server stores behavior information of the digital vehicle generated based on control information set in the vehicle, and when a driving operation is performed, the terminal displays the behavior of the digital vehicle corresponding to the driving operation on the display screen based on the behavior information obtained from the server.

3. The drive experience system according to claim 1, characterized in that when the driving operation is performed on the terminal, the server or the terminal performs gaze control to change the gaze of the avatar sitting in the driver's seat in accordance with the gaze change operation on the terminal, and the terminal displays on the display screen at least one of the surrounding scenery of the digital vehicle and the interior scenery of the digital vehicle, including the interior of the vehicle, based on the gaze changed by the gaze control.

4. The drive experience system according to claim 1, wherein the server comprises a plurality of friend terminals operated by friends registered in the user's friend list, and when an operation to invite a friend to a drive is performed on one of the terminals, the server sends an invitation notification to the friend terminal of the invited friend and grants permission for the friend terminal to ride in the digital vehicle, and when an operation to ride in the digital vehicle is performed on the permitted friend terminal, the server places the friend's friend avatar in a predetermined seat of the digital vehicle, wherein the predetermined seat is the passenger seat when the ride-in operation is performed on one of the friend terminals, and is any seat in the passenger seat and rear seats when the ride-in operation is performed on multiple of the friend terminals.

5. The drive experience system according to claim 4, characterized in that when the driving operation is performed on the terminal, the server, the terminal, or the friend terminal performs gaze control to change the gaze of the avatar and the friend avatar riding in the digital vehicle in accordance with the gaze change operation on the terminal and the friend terminal, respectively; the terminal displays on its display screen, on the interior view of the digital vehicle and at least one of the friend avatar, based on the gaze of the avatar changed by the gaze control; and the friend terminal displays on its display screen, on the interior view of the digital vehicle and at least one of the avatar, based on the gaze of the friend avatar changed by the gaze control.

6. The drive experience system according to claim 5, characterized in that, while the eye-tracking control is being performed, the server or the terminal switches control to overhead view control from eye-tracking control to overhead view control when the terminal is switched to a third-person view; the terminal displays an overhead view image on its display screen, including the overall appearance of the digital vehicle and the surrounding scenery, based on the overhead view control; the server or the friend terminal switches control to overhead view control from eye-tracking control to overhead view control when the friend terminal is switched to a third-person view during the eye-tracking control; and the friend terminal displays the overhead view image on its display screen, based on the overhead view control.

7. The drive experience system according to claim 4, characterized in that the server or the terminal performs user return control to return the digital vehicle to the garage when an operation to terminate the driving operation is performed on the terminal, and the server or the friend terminal of a passenger performs friend return control to return only the friend avatar of the friend terminal to the garage when an operation to terminate the ride is performed from the friend terminal.

8. A drive experience system according to any one of claims 1 to 7, further comprising: an NFT issuing unit that issues NFTs; and an NFT management server that manages an NFT marketplace, wherein the server receives an NFT conversion request from the terminal to convert the drive video of the digital vehicle into an NFT; the NFT issuing unit issues an NFT based on the drive video to the user in response to the NFT conversion request received by the server; and the NFT management server, upon receiving a request from the terminal to list the NFT, lists the NFT on the NFT marketplace.

9. A server that sends and receives data to and from a terminal operated by a user, comprising: a first control unit that performs a first control to display a metaverse space including the user's avatar on the display screen of the terminal; a receiving unit that receives a signal from the terminal to purchase a predetermined digital vehicle; a storage unit that, upon receiving the signal in the receiving unit, stores the digital vehicle and the garage in which the digital vehicle is stored in association with the user; a second control unit that, after the association, performs a second control to display the digital vehicle in the metaverse space in a manner usable by the terminal; and a third control unit that, when driving the digital vehicle is selected, performs a third control to display the digital vehicle with the avatar seated in the driver's seat on the display screen in a manner that allows it to be driven.

Images