JP2024049926A - Program and information processing system - Google Patents

Abstract

[Problem] To improve the interest of a service. [Solution] A program causes a computer to function as an acquisition means for acquiring information related to a user who uses a metaverse, and a change means for changing an environment in a metaverse for a plurality of users based on information related to the users for at least two or more users. [Selected Figure] Figure 1

Description

The present invention relates to a program and an information processing system.

Services that provide a virtual space (in other words, a metaverse) in which users can interact with each other have been known (see, for example, Patent Document 1).

JP 2011-216073 A

However, there is a demand for services like this to be more entertaining.

The present invention was made in consideration of the above circumstances, and aims to improve the interest of the service.

According to one embodiment shown in the present disclosure,
Computer,
An acquisition means for acquiring information related to a user who uses the metaverse;
A program is provided that functions as a change means for changing an environment within the metaverse of a plurality of users based on the information about at least two or more users.

The present invention can improve the interest of the service.

FIG. 1 is a diagram illustrating an outline of the configuration of an HMD system according to an embodiment. FIG. 1 is a block diagram illustrating an example of a hardware configuration of a computer according to an embodiment. FIG. 2 is a diagram conceptually illustrating a uvw field of view coordinate system set in an HMD according to an embodiment. FIG. 1 is a diagram conceptually illustrating one mode of expressing a virtual space according to an embodiment. 1 is a top view of a user's head wearing an HMD according to an embodiment. 1 is a diagram showing a YZ cross section of a field of view in a virtual space as viewed from an X direction. 13 is a diagram showing an XZ cross section of a field of view in a virtual space as viewed from a Y direction. FIG. 2 is a diagram illustrating a schematic configuration of a controller according to an embodiment. FIG. 2 illustrates an example of yaw, roll, and pitch directions defined relative to a user's right hand according to one embodiment. FIG. 2 is a block diagram illustrating an example of a hardware configuration of a server according to an embodiment. FIG. 1 is a block diagram illustrating a modular configuration of a computer according to an embodiment. 1 is a sequence chart showing a process executed in an HMD set according to an embodiment. 1 is a schematic diagram showing a situation in which each HMD provides a virtual space to a user in a network. FIG. 13 is a diagram showing a field of view image of user 5A in FIG. 1 is a sequence chart showing a process executed in an HMD system according to an embodiment. FIG. 2 is a block diagram illustrating a detailed configuration of a module of a computer according to an embodiment. FIG. 2 is a block diagram illustrating a server according to an embodiment in a modular configuration. FIG. 11 is a diagram for explaining attributes set for a user according to an embodiment. FIG. 13 is a diagram illustrating a display for making a predetermined recommendation to a user according to an embodiment. FIG. 13 is a diagram illustrating a display for making a predetermined recommendation to a user according to an embodiment. 11 is a sequence chart illustrating an example of a process for recommending other users based on a behavior history in the metaverse according to an embodiment. 11 is a sequence chart illustrating an example of a process for recommending content in the metaverse based on a behavior history in the metaverse according to an embodiment. 1 is a sequence chart illustrating an example of a process for making recommendations regarding things in the metaverse based on behavioral history in the real world according to an embodiment. 1 is a sequence chart illustrating an example of a process for making recommendations regarding real-world objects based on a behavior history in the metaverse according to an embodiment. FIG. 13 is a diagram illustrating a display when an environment in the metaverse changes according to an embodiment. FIG. 13 is a diagram for explaining environmental recommendations for a user in a specific area according to an embodiment. FIG. 13 is a diagram illustrating a display when BGM is recommended according to an embodiment. FIG. 13 is a diagram illustrating a display in which the environment of multiple users in a specific area is changed based on a selection by a specific user according to an embodiment. 1 is a sequence chart illustrating an example process for changing an environment in a metaverse for multiple users based on user-related information for two or more users according to one embodiment.

The following describes in detail an embodiment of this technical idea with reference to the drawings. In the following description, the same components are given the same reference numerals. Their names and functions are also the same. Therefore, detailed descriptions thereof will not be repeated. In one or more embodiments shown in this disclosure, the elements included in each embodiment can be combined with each other, and the result of such combination is also considered to be part of the embodiment shown in this disclosure.

[Configuration of HMD system]
The configuration of an HMD (Head-Mounted Device) system 100 will be described with reference to Fig. 1. Fig. 1 is a diagram showing an outline of the configuration of the HMD system 100 according to the present embodiment. The HMD system 100 is provided as a system for home use or a system for commercial use. The HMD system 100 provides a predetermined service to the user.

The HMD system 100 includes a server 600, HMD sets 110A, 110B, 110C, and 110D, an external device 700, and a network 2. Each of the HMD sets 110A, 110B, 110C, and 110D is configured to be able to communicate with the server 600 and the external device 700 via the network 2. Hereinafter, the HMD sets 110A, 110B, 110C, and 110D are collectively referred to as the HMD set 110. The number of HMD sets 110 constituting the HMD system 100 is not limited to four, and may be three or less, or five or more. The HMD set 110 includes an HMD 120, a computer 200, an HMD sensor 410, a display 430, and a controller 300. The HMD 120 includes a monitor 130, a gaze sensor 140, a first camera 150, a second camera 160, a microphone 170, and a speaker 180. The controller 300 may include a motion sensor 420.

In one aspect, the computer 200 can be connected to the Internet or other network 2, and can communicate with a server 600 or other computers connected to the network 2. Examples of other computers include computers of other HMD sets 110 and external devices 700. In another aspect, the HMD 120 can include a sensor 190 instead of the HMD sensor 410.

The HMD 120 is worn on the head of the user 5 and can provide a virtual space to the user 5 during operation. More specifically, the HMD 120 displays an image for the right eye and an image for the left eye on the monitor 130. When each eye of the user 5 views the respective image, the user 5 can recognize the image as a three-dimensional image based on the parallax between the two eyes. The HMD 120 can include both a so-called head-mounted display equipped with a monitor and a head-mounted device to which a smartphone or other terminal equipped with a monitor can be attached.

The monitor 130 is realized, for example, as a non-transparent display device. In one aspect, the monitor 130 is disposed on the main body of the HMD 120 so as to be positioned in front of both eyes of the user 5. Thus, when the user 5 visually recognizes the three-dimensional image displayed on the monitor 130, the user 5 can be immersed in the virtual space. In one aspect, the virtual space includes, for example, images of a background, objects that the user 5 can operate, and menus that the user 5 can select. In one aspect, the monitor 130 can be realized as a liquid crystal monitor or an organic EL (Electro Luminescence) monitor provided in a so-called smartphone or other information display terminal.

In another aspect, the monitor 130 may be realized as a transmissive display device. In this case, the HMD 120 may be an open type such as a pair of glasses, rather than a closed type that covers the eyes of the user 5 as shown in FIG. 1. The transmissive monitor 130 may be temporarily configurable as a non-transmissive display device by adjusting its transmittance. The monitor 130 may include a configuration that simultaneously displays a portion of an image that constitutes a virtual space and the real space. For example, the monitor 130 may display an image of the real space captured by a camera mounted on the HMD 120, or may make the real space visible by setting the transmittance of a portion of the image high.

In one aspect, the monitor 130 may include a sub-monitor for displaying an image for the right eye and a sub-monitor for displaying an image for the left eye. In another aspect, the monitor 130 may be configured to display an image for the right eye and an image for the left eye as a single unit. In this case, the monitor 130 includes a high-speed shutter. The high-speed shutter operates to alternately display an image for the right eye and an image for the left eye so that the image is perceived by only one of the eyes.

In one aspect, the HMD 120 includes multiple light sources (not shown). Each light source is realized, for example, by an LED (Light Emitting Diode) that emits infrared rays. The HMD sensor 410 has a position tracking function for detecting the movement of the HMD 120. More specifically, the HMD sensor 410 reads multiple infrared rays emitted by the HMD 120 and detects the position and tilt of the HMD 120 in real space.

In another aspect, the HMD sensor 410 may be realized by a camera. In this case, the HMD sensor 410 can detect the position and inclination of the HMD 120 by performing image analysis processing using image information of the HMD 120 output from the camera.

In another aspect, the HMD 120 may include a sensor 190 as a position detector instead of or in addition to the HMD sensor 410. The HMD 120 may use the sensor 190 to detect the position and inclination of the HMD 120 itself. For example, if the sensor 190 is an angular velocity sensor, a geomagnetic sensor, or an acceleration sensor, the HMD 120 may use any of these sensors instead of the HMD sensor 410 to detect the position and inclination of the HMD 120 itself. As an example, if the sensor 190 is an angular velocity sensor, the angular velocity sensor detects the angular velocity of the HMD 120 around three axes in real space over time. The HMD 120 calculates the change in angle of the HMD 120 around the three axes over time based on each angular velocity, and further calculates the inclination of the HMD 120 based on the change in angle over time.

The gaze sensor 140 detects the direction in which the gaze of the right eye and left eye of the user 5 is directed. In other words, the gaze sensor 140 detects the gaze of the user 5. The detection of the gaze direction is realized, for example, by a known eye tracking function. The gaze sensor 140 is realized by a sensor having the eye tracking function. In one aspect, the gaze sensor 140 preferably includes a sensor for the right eye and a sensor for the left eye. The gaze sensor 140 may be, for example, a sensor that irradiates the right eye and left eye of the user 5 with infrared light and detects the rotation angle of each eyeball by receiving reflected light from the cornea and iris in response to the irradiated light. The gaze sensor 140 can detect the gaze of the user 5 based on each detected rotation angle.

The first camera 150 photographs the lower part of the face of the user 5. More specifically, the first camera 150 photographs the nose, mouth, etc. of the user 5. The second camera 160 photographs the eyes, eyebrows, etc. of the user 5. The housing of the HMD 120 on the user 5 side is defined as the inside of the HMD 120, and the housing of the HMD 120 on the opposite side to the user 5 is defined as the outside of the HMD 120. In one aspect, the first camera 150 may be disposed outside the HMD 120, and the second camera 160 may be disposed inside the HMD 120. The images generated by the first camera 150 and the second camera 160 are input to the computer 200. In another aspect, the first camera 150 and the second camera 160 may be realized as a single camera, and the face of the user 5 may be photographed by this single camera.

The microphone 170 converts the speech of the user 5 into an audio signal (electrical signal) and outputs it to the computer 200. The speaker 180 converts the audio signal into sound and outputs it to the user 5. In another aspect, the HMD 120 may include earphones instead of the speaker 180.

The controller 300 is connected to the computer 200 by wire or wirelessly. The controller 300 accepts input of commands from the user 5 to the computer 200. In one aspect, the controller 300 is configured to be held by the user 5. In another aspect, the controller 300 is configured to be attached to a part of the body or clothing of the user 5. In yet another aspect, the controller 300 may be configured to output at least one of vibration, sound, and light based on a signal transmitted from the computer 200. In yet another aspect, the controller 300 accepts operations from the user 5 to control the position and movement of an object placed in a virtual space.

In one aspect, the controller 300 includes multiple light sources. Each light source is realized, for example, by an LED that emits infrared light. The HMD sensor 410 has a position tracking function. In this case, the HMD sensor 410 reads multiple infrared rays emitted by the controller 300 and detects the position and tilt of the controller 300 in real space. In another aspect, the HMD sensor 410 may be realized by a camera. In this case, the HMD sensor 410 can detect the position and tilt of the controller 300 by performing image analysis processing using image information of the controller 300 output from the camera.

In one aspect, the motion sensor 420 is attached to the hand of the user 5 and detects the movement of the hand of the user 5. For example, the motion sensor 420 detects the rotation speed, number of rotations, etc. of the hand. The detected signal is sent to the computer 200. The motion sensor 420 is provided, for example, in the controller 300. In one aspect, the motion sensor 420 is provided, for example, in the controller 300 configured to be held by the user 5. In another aspect, for safety in the real space, the controller 300 is attached to something that is not easily blown away by being worn on the hand of the user 5, such as a glove type. In yet another aspect, a sensor that is not worn by the user 5 may detect the movement of the hand of the user 5. For example, a signal from a camera that captures the user 5 may be input to the computer 200 as a signal representing the movement of the user 5. The motion sensor 420 and the computer 200 are connected to each other wirelessly, as an example. In the case of wireless communication, the communication form is not particularly limited, and for example, Bluetooth (registered trademark) or other known communication methods are used.

The display 430 displays an image similar to the image displayed on the monitor 130. This allows users other than the user 5 wearing the HMD 120 to view an image similar to that of the user 5. The image displayed on the display 430 does not need to be a three-dimensional image, and may be an image for the right eye or an image for the left eye. Examples of the display 430 include a liquid crystal display and an organic EL monitor.

The server 600 may transmit a program to the computer 200. In another aspect, the server 600 may communicate with other computers 200 to provide virtual reality to the HMD 120 used by other users. For example, in an amusement facility, when multiple users play a participatory game, each computer 200 communicates signals based on the actions of each user with the other computers 200 via the server 600, allowing multiple users to enjoy a common game in the same virtual space. Each computer 200 may also communicate signals based on the actions of each user with the other computers 200 without going through the server 600.

The external device 700 may be any device capable of communicating with the computer 200. The external device 700 may be, for example, a device capable of communicating with the computer 200 via the network 2, or a device capable of directly communicating with the computer 200 via short-range wireless communication or a wired connection. The external device 700 may also be, for example, a device capable of communicating with the server 600 via the network 2. Examples of the external device 700 include, but are not limited to, a smart device, a PC (Personal Computer), and peripheral devices of the computer 200.

[Computer hardware configuration]
A computer 200 according to the present embodiment will be described with reference to Fig. 2. Fig. 2 is a block diagram showing an example of a hardware configuration of the computer 200 according to the present embodiment. The computer 200 includes, as main components, a processor 210, a memory 220, a storage 230, an input/output interface 240, and a communication interface 250. Each component is connected to a bus 260.

The processor 210 executes a series of instructions contained in a program stored in the memory 220 or the storage 230 based on a signal provided to the computer 200 or based on the satisfaction of a predetermined condition. In one aspect, the processor 210 is realized as a CPU (Central Processing Unit), a GPU (Graphics Processing Unit), an MPU (Micro Processor Unit), an FPGA (Field-Programmable Gate Array), or other device.

Memory 220 temporarily stores programs and data. Programs are loaded, for example, from storage 230. Data includes data input to computer 200 and data generated by processor 210. In one aspect, memory 220 is realized as RAM (Random Access Memory) or other volatile memory.

The storage 230 permanently holds programs and data. The storage 230 is realized, for example, as a ROM (Read-Only Memory), a hard disk drive, a flash memory, or other non-volatile storage device. The programs stored in the storage 230 include a program for providing a virtual space in the HMD system 100, a simulation program, a game program, a user authentication program, and a program for realizing communication with other computers 200. The data stored in the storage 230 includes data and objects for defining the virtual space, etc.

In another aspect, the storage 230 may be realized as a removable storage device such as a memory card. In yet another aspect, a configuration may be used in which programs and data stored in an external storage device are used instead of the storage 230 built into the computer 200. With such a configuration, for example, in a situation where multiple HMD systems 100 are used, such as an amusement facility, it becomes possible to perform updates of programs and data collectively.

The input/output interface 240 communicates signals between the HMD 120, the HMD sensor 410, the motion sensor 420, and the display 430. The monitor 130, the gaze sensor 140, the first camera 150, the second camera 160, the microphone 170, and the speaker 180 included in the HMD 120 can communicate with the computer 200 via the input/output interface 240 of the HMD 120. In some aspects, the input/output interface 240 is realized using a terminal such as a Universal Serial Bus (USB), a Digital Visual Interface (DVI), a High-Definition Multimedia Interface (HDMI (registered trademark)), or other terminal. The input/output interface 240 is not limited to those mentioned above.

In one aspect, the input/output interface 240 may further communicate with the controller 300. For example, the input/output interface 240 receives input of signals output from the controller 300 and the motion sensor 420. In another aspect, the input/output interface 240 sends instructions output from the processor 210 to the controller 300. The instructions instruct the controller 300 to vibrate, output sound, emit light, etc. When the controller 300 receives the instructions, it executes either vibration, sound output, or light emission according to the instructions.

The communication interface 250 is connected to the network 2 and communicates with other computers (e.g., the server 600) connected to the network 2. In one aspect, the communication interface 250 is realized as, for example, a LAN (Local Area Network) or other wired communication interface, or a wireless communication interface such as Wi-Fi (registered trademark), Bluetooth (registered trademark), NFC (Near Field Communication), or other wireless communication interface. The communication interface 250 is not limited to the above.

In one aspect, the processor 210 accesses the storage 230, loads one or more programs stored in the storage 230 into the memory 220, and executes a series of instructions contained in the programs. The one or more programs may include an operating system for the computer 200, an application program for providing a virtual space, game software executable in the virtual space, and the like. The processor 210 sends a signal for providing the virtual space to the HMD 120 via the input/output interface 240. The HMD 120 displays an image on the monitor 130 based on the signal.

2, the computer 200 is shown as being provided outside the HMD 120, but in another aspect, the computer 200 may be built into the HMD 120. As an example, a portable information and communication terminal (e.g., a smartphone) including the monitor 130 may function as the computer 200.

The computer 200 may be configured to be shared by multiple HMDs 120. With such a configuration, for example, the same virtual space can be provided to multiple users, allowing each user to enjoy the same application as other users in the same virtual space.

In one embodiment, a real coordinate system, which is a coordinate system in real space, is set in advance in the HMD system 100. The real coordinate system has three reference directions (axes) that are parallel to the vertical direction in real space, the horizontal direction perpendicular to the vertical direction, and the front-to-back direction perpendicular to both the vertical and horizontal directions. The horizontal direction, vertical direction (up-down direction), and front-to-back direction in the real coordinate system are defined as the x-axis, y-axis, and z-axis, respectively. More specifically, in the real coordinate system, the x-axis is parallel to the horizontal direction in real space. The y-axis is parallel to the vertical direction in real space. The z-axis is parallel to the front-to-back direction in real space.

In one aspect, the HMD sensor 410 includes an infrared sensor. When the infrared sensor detects infrared rays emitted from each light source of the HMD 120, it detects the presence of the HMD 120. The HMD sensor 410 further detects the position and tilt (orientation) of the HMD 120 in real space according to the movement of the user 5 wearing the HMD 120, based on the values of each point (each coordinate value in the real coordinate system). More specifically, the HMD sensor 410 can detect changes over time in the position and tilt of the HMD 120, using each value detected over time.

Each tilt of the HMD 120 detected by the HMD sensor 410 corresponds to each tilt around the three axes of the HMD 120 in the real coordinate system. The HMD sensor 410 sets a uvw field of view coordinate system in the HMD 120 based on the tilt of the HMD 120 in the real coordinate system. The uvw field of view coordinate system set in the HMD 120 corresponds to the viewpoint coordinate system when the user 5 wearing the HMD 120 views an object in the virtual space.

[uvw visual coordinate system]
The uvw field of view coordinate system will be described with reference to Fig. 3. Fig. 3 is a diagram conceptually showing the uvw field of view coordinate system set in the HMD 120 according to an embodiment. The HMD sensor 410 detects the position and inclination of the HMD 120 in the real coordinate system when the HMD 120 is started. The processor 210 sets the uvw field of view coordinate system in the HMD 120 based on the detected values.

As shown in FIG. 3, the HMD 120 sets a three-dimensional uvw field of view coordinate system with the head of the user 5 wearing the HMD 120 as its center (origin). More specifically, the HMD 120 tilts the horizontal, vertical, and front-back directions (x-axis, y-axis, z-axis) that define the real coordinate system around each axis by the tilt of the HMD 120 around each axis in the real coordinate system, and sets the three newly obtained directions as the pitch axis (u-axis), yaw axis (v-axis), and roll axis (w-axis) of the uvw field of view coordinate system in the HMD 120.

In a certain situation, when the user 5 wearing the HMD 120 stands upright and looks straight ahead, the processor 210 sets a uvw field of view coordinate system in the HMD 120 that is parallel to the real coordinate system. In this case, the horizontal direction (x-axis), vertical direction (y-axis), and front-to-back direction (z-axis) in the real coordinate system coincide with the pitch axis (u-axis), yaw axis (v-axis), and roll axis (w-axis) of the uvw field of view coordinate system in the HMD 120.

After the uvw field of view coordinate system is set in the HMD 120, the HMD sensor 410 can detect the tilt of the HMD 120 in the set uvw field of view coordinate system based on the movement of the HMD 120. In this case, the HMD sensor 410 detects the pitch angle (θu), yaw angle (θv), and roll angle (θw) of the HMD 120 in the uvw field of view coordinate system as the tilt of the HMD 120. The pitch angle (θu) represents the tilt angle of the HMD 120 around the pitch axis in the uvw field of view coordinate system. The yaw angle (θv) represents the tilt angle of the HMD 120 around the yaw axis in the uvw field of view coordinate system. The roll angle (θw) represents the tilt angle of the HMD 120 around the roll axis in the uvw field of view coordinate system.

The HMD sensor 410 sets the uvw field of view coordinate system of the HMD 120 after the HMD 120 moves on the HMD 120 based on the detected tilt of the HMD 120. The relationship between the HMD 120 and the uvw field of view coordinate system of the HMD 120 is always constant regardless of the position and tilt of the HMD 120. When the position and tilt of the HMD 120 change, the position and tilt of the uvw field of view coordinate system of the HMD 120 in the real coordinate system change in conjunction with the change in the position and tilt.

In one aspect, the HMD sensor 410 may identify the position of the HMD 120 in real space as a relative position with respect to the HMD sensor 410 based on the infrared light intensity and the relative positional relationship between multiple points (e.g., the distance between each point) acquired based on the output from the infrared sensor. The processor 210 may determine the origin of the uvw field of view coordinate system of the HMD 120 in real space (actual coordinate system) based on the identified relative position.

[Virtual space]
The virtual space will be further described with reference to FIG. 4. FIG. 4 is a diagram conceptually showing one mode of expressing the virtual space 11 according to an embodiment. The virtual space 11 has a spherical structure covering the entire 360-degree direction of the center 12. In FIG. 4, in order to avoid complicating the description, the upper half of the celestial sphere in the virtual space 11 is illustrated. Each mesh is defined in the virtual space 11. The position of each mesh is defined in advance as a coordinate value in the XYZ coordinate system, which is a global coordinate system defined in the virtual space 11. The computer 200 associates each partial image constituting the panoramic image 13 (still image, video, etc.) that can be deployed in the virtual space 11 with each corresponding mesh in the virtual space 11.

In a certain aspect, an XYZ coordinate system is defined in the virtual space 11 with the center 12 as the origin. The XYZ coordinate system is, for example, parallel to the real coordinate system. The horizontal direction, vertical direction (up-down direction), and front-to-back direction in the XYZ coordinate system are defined as the X-axis, Y-axis, and Z-axis, respectively. Therefore, the X-axis (horizontal direction) of the XYZ coordinate system is parallel to the x-axis of the real coordinate system, the Y-axis (vertical direction) of the XYZ coordinate system is parallel to the y-axis of the real coordinate system, and the Z-axis (front-to-back direction) of the XYZ coordinate system is parallel to the z-axis of the real coordinate system.

When the HMD 120 is started up, i.e., in the initial state of the HMD 120, the virtual camera 14 is placed at the center 12 of the virtual space 11. At a certain stage, the processor 210 displays an image captured by the virtual camera 14 on the monitor 130 of the HMD 120. The virtual camera 14 moves in the virtual space 11 in a similar manner in conjunction with the movement of the HMD 120 in the real space. This allows changes in the position and tilt of the HMD 120 in the real space to be reproduced in the virtual space 11 in a similar manner.

A uvw field of view coordinate system is defined for the virtual camera 14, as in the case of the HMD 120. The uvw field of view coordinate system of the virtual camera 14 in the virtual space 11 is defined so as to be linked to the uvw field of view coordinate system of the HMD 120 in real space (actual coordinate system). Therefore, when the tilt of the HMD 120 changes, the tilt of the virtual camera 14 also changes accordingly. The virtual camera 14 can also move in the virtual space 11 in conjunction with the movement in real space of the user 5 wearing the HMD 120.

The processor 210 of the computer 200 determines the field of view 15 in the virtual space 11 based on the position and inclination (reference line of sight 16) of the virtual camera 14. The field of view 15 corresponds to the area of the virtual space 11 that is viewed by the user 5 wearing the HMD 120. In other words, the position of the virtual camera 14 can be said to be the viewpoint of the user 5 in the virtual space 11.

The line of sight of user 5 detected by gaze sensor 140 is the direction in the viewpoint coordinate system when user 5 views an object. The uvw field of view coordinate system of HMD 120 is equal to the viewpoint coordinate system when user 5 views monitor 130. The uvw field of view coordinate system of virtual camera 14 is linked to the uvw field of view coordinate system of HMD 120. Therefore, in a certain aspect, the HMD system 100 can consider the line of sight of user 5 detected by gaze sensor 140 to be the line of sight of user 5 in the uvw field of view coordinate system of virtual camera 14.

[User's gaze]
Determining the line of sight of the user 5 will be described with reference to Fig. 5. Fig. 5 is a top view of the head of a user 5 wearing an HMD 120 according to an embodiment.

In one aspect, the gaze sensor 140 detects the gaze of each of the right and left eyes of the user 5. In one aspect, when the user 5 is looking at something close, the gaze sensor 140 detects the gazes R1 and L1. In another aspect, when the user 5 is looking at something far away, the gaze sensor 140 detects the gazes R2 and L2. In this case, the angle that the gazes R2 and L2 make with respect to the roll axis w is smaller than the angle that the gazes R1 and L1 make with respect to the roll axis w. The gaze sensor 140 transmits the detection result to the computer 200.

When the computer 200 receives the detection values of the gazes R1 and L1 from the gaze sensor 140 as the gaze detection result, the computer 200 identifies the gaze point N1, which is the intersection of the gazes R1 and L1, based on the detection values. On the other hand, when the computer 200 receives the detection values of the gazes R2 and L2 from the gaze sensor 140, the computer 200 identifies the intersection of the gazes R2 and L2 as the gaze point. The computer 200 identifies the gaze N0 of the user 5 based on the position of the identified gaze point N1. For example, the computer 200 detects the direction of the line that passes through the gaze point N1 and the midpoint of the line connecting the right eye R and the left eye L of the user 5 as the gaze N0. The gaze N0 is the direction in which the user 5 is actually looking with both eyes. The gaze N0 corresponds to the direction in which the user 5 is actually looking with respect to the field of view 15.

In another aspect, the HMD system 100 may be equipped with a television broadcast receiving tuner. With such a configuration, the HMD system 100 can display television programs in the virtual space 11.

In yet another aspect, the HMD system 100 may be equipped with a communication circuit for connecting to the Internet or a calling function for connecting to a telephone line.

[View Area]
The field of view 15 will be described with reference to Fig. 6 and Fig. 7. Fig. 6 is a diagram showing a YZ cross section of the field of view 15 in the virtual space 11 as viewed from the X direction. Fig. 7 is a diagram showing an XZ cross section of the field of view 15 in the virtual space 11 as viewed from the Y direction.

As shown in FIG. 6, the field of view 15 in the YZ cross section includes an area 18. The area 18 is defined by the position of the virtual camera 14, the reference line of sight 16, and the YZ cross section of the virtual space 11. The processor 210 defines the range including the polar angle α centered on the reference line of sight 16 in the virtual space as the area 18.

As shown in FIG. 7, the field of view 15 in the XZ cross section includes area 19. Area 19 is defined by the position of virtual camera 14, reference line of sight 16, and the XZ cross section of virtual space 11. Processor 210 defines a range including azimuth angle β centered on reference line of sight 16 in virtual space 11 as area 19. Polar angles α and β are determined according to the position of virtual camera 14 and the inclination (direction) of virtual camera 14.

In one aspect, the HMD system 100 provides the user 5 with a field of view in the virtual space 11 by displaying a field of view image 17 on the monitor 130 based on a signal from the computer 200. The field of view image 17 is an image that corresponds to a portion of the panoramic image 13 that corresponds to the field of view area 15. When the user 5 moves the HMD 120 worn on the head, the virtual camera 14 also moves in conjunction with the movement. As a result, the position of the field of view area 15 in the virtual space 11 changes. As a result, the field of view image 17 displayed on the monitor 130 is updated to an image of the panoramic image 13 that is superimposed on the field of view area 15 in the direction in which the user 5 is facing in the virtual space 11. The user 5 can view the desired direction in the virtual space 11.

In this way, the inclination of the virtual camera 14 corresponds to the line of sight (reference line of sight 16) of the user 5 in the virtual space 11, and the position at which the virtual camera 14 is positioned corresponds to the viewpoint of the user 5 in the virtual space 11. Therefore, by changing the position or inclination of the virtual camera 14, the image displayed on the monitor 130 is updated and the field of view of the user 5 is moved.

While wearing the HMD 120, the user 5 can only view the panoramic image 13 displayed in the virtual space 11, without being able to see the real world. Therefore, the HMD system 100 can give the user 5 a high sense of immersion in the virtual space 11.

In one aspect, the processor 210 may move the virtual camera 14 in the virtual space 11 in conjunction with the movement in real space of the user 5 wearing the HMD 120. In this case, the processor 210 identifies the image area (field of view area 15) to be projected onto the monitor 130 of the HMD 120 based on the position and inclination of the virtual camera 14 in the virtual space 11.

In one aspect, the virtual camera 14 may include two virtual cameras, i.e., a virtual camera for providing an image for the right eye and a virtual camera for providing an image for the left eye. An appropriate parallax is set for the two virtual cameras so that the user 5 can recognize the three-dimensional virtual space 11. In another aspect, the virtual camera 14 may be realized by a single virtual camera. In this case, an image for the right eye and an image for the left eye may be generated from an image obtained by the single virtual camera. In this embodiment, the technical idea of the present disclosure is illustrated by assuming that the virtual camera 14 includes two virtual cameras and is configured so that the roll axis (w) generated by combining the roll axes of the two virtual cameras is adapted to the roll axis (w) of the HMD 120.

[controller]
An example of the controller 300 will be described with reference to Fig. 8. Fig. 8 is a diagram showing a schematic configuration of the controller 300 according to an embodiment.

As shown in FIG. 8, in one aspect, the controller 300 may include a right controller 300R and a left controller (not shown). The right controller 300R is operated by the right hand of the user 5. The left controller is operated by the left hand of the user 5. In one aspect, the right controller 300R and the left controller are configured symmetrically as separate devices. Thus, the user 5 can freely move both the right hand holding the right controller 300R and the left hand holding the left controller. In another aspect, the controller 300 may be an integrated controller that accepts operation from both hands. The right controller 300R will be described below.

The right controller 300R includes a grip 310, a frame 320, and a top surface 330. The grip 310 is configured to be held by the right hand of the user 5. For example, the grip 310 can be held by the palm and three fingers (middle finger, ring finger, and little finger) of the right hand of the user 5.

Grip 310 includes buttons 340, 350 and a motion sensor 420. Button 340 is located on the side of grip 310 and is operated by the middle finger of the right hand. Button 350 is located on the front of grip 310 and is operated by the index finger of the right hand. In one aspect, buttons 340, 350 are configured as trigger-type buttons. Motion sensor 420 is built into the housing of grip 310. If the movements of user 5 can be detected from around user 5 by a camera or other device, grip 310 does not need to include motion sensor 420.

The frame 320 includes a number of infrared LEDs 360 arranged along its circumference. During execution of a program that uses the controller 300, the infrared LEDs 360 emit infrared light in accordance with the progress of the program. The infrared light emitted from the infrared LEDs 360 can be used to detect the positions and attitudes (tilt, direction) of the right controller 300R and the left controller. In the example shown in FIG. 8, the infrared LEDs 360 are arranged in two rows, but the number of rows is not limited to that shown in FIG. 8. An arrangement in one row or three or more rows may be used.

The top surface 330 includes buttons 370, 380 and an analog stick 390. The buttons 370, 380 are configured as push buttons. The buttons 370, 380 are operated by the thumb of the right hand of the user 5. In a certain situation, the analog stick 390 is operated in any direction within 360 degrees from the initial position (neutral position). Such operations include, for example, operations for moving an object placed in the virtual space 11.

In one aspect, the right controller 300R and the left controller include a battery for driving the infrared LED 360 and other components. The battery may be, but is not limited to, a rechargeable battery, a button type battery, or a dry cell battery. In another aspect, the right controller 300R and the left controller may be connected to, for example, a USB interface of the computer 200. In this case, the right controller 300R and the left controller do not require a battery.

As shown in states (A) and (B) of FIG. 8, for example, the yaw, roll, and pitch directions are defined for the right hand of user 5. When user 5 extends his thumb and index finger, the direction in which the thumb extends is defined as the yaw direction, the direction in which the index finger extends is defined as the roll direction, and the direction perpendicular to the plane defined by the axis of the yaw direction and the axis of the roll direction is defined as the pitch direction.

[Server hardware configuration]
Server 600 according to the present embodiment will be described with reference to Fig. 9. Fig. 9 is a block diagram showing an example of a hardware configuration of server 600 according to an embodiment. Server 600 includes, as main components, a processor 610, a memory 620, a storage 630, an input/output interface 640, and a communication interface 650. Each component is connected to a bus 660.

The processor 610 executes a series of instructions contained in a program stored in the memory 620 or the storage 630 based on a signal provided to the server 600 or based on the satisfaction of a predetermined condition. In one aspect, the processor 610 is realized as a CPU, a GPU, an MPU, an FPGA, or other device.

Memory 620 temporarily stores programs and data. Programs are loaded, for example, from storage 630. Data includes data input to server 600 and data generated by processor 610. In one aspect, memory 620 is realized as RAM or other volatile memory.

Storage 630 permanently holds programs and data. Storage 630 is realized, for example, as a ROM, a hard disk drive, a flash memory, or other non-volatile storage device. Programs stored in storage 630 may include a program for providing a virtual space in HMD system 100, a simulation program, a game program, a user authentication program, and a program for realizing communication with computer 200. Data stored in storage 630 may include data and objects for defining the virtual space, etc.

In another aspect, the storage 630 may be realized as a removable storage device such as a memory card. In yet another aspect, instead of the storage 630 built into the server 600, a configuration may be used in which programs and data stored in an external storage device are used. With such a configuration, for example, in a situation where multiple HMD systems 100 are used, such as an amusement facility, it becomes possible to perform updates of programs and data collectively.

The input/output interface 640 communicates signals with input/output devices. In some aspects, the input/output interface 640 is realized using a USB, DVI, HDMI, or other terminal. The input/output interface 640 is not limited to the above.

The communication interface 650 is connected to the network 2 and communicates with the computer 200 connected to the network 2. In one aspect, the communication interface 650 is realized as, for example, a LAN or other wired communication interface, or a wireless communication interface such as Wi-Fi, Bluetooth, NFC, or other wireless communication interface. The communication interface 650 is not limited to the above.

In one aspect, the processor 610 accesses the storage 630, loads one or more programs stored in the storage 630 into the memory 620, and executes a series of instructions contained in the programs. The one or more programs may include an operating system of the server 600, an application program for providing a virtual space, game software executable in the virtual space, and the like. The processor 610 may send a signal for providing the virtual space to the computer 200 via the input/output interface 640.

[HMD Control Device]
A control device for the HMD 120 will be described with reference to Fig. 10. In an embodiment, the control device is realized by a computer 200 having a known configuration. Fig. 10 is a block diagram showing the computer 200 according to an embodiment as a modular configuration.

As shown in FIG. 10, the computer 200 includes a control module 510, a rendering module 520, a memory module 530, and a communication control module 540. In one aspect, the control module 510 and the rendering module 520 are realized by the processor 210. In another aspect, multiple processors 210 may operate as the control module 510 and the rendering module 520. The memory module 530 is realized by the memory 220 or the storage 230. The communication control module 540 is realized by the communication interface 250.

The control module 510 controls the virtual space 11 provided to the user 5. The control module 510 defines the virtual space 11 in the HMD system 100 using virtual space data representing the virtual space 11. The virtual space data is stored in, for example, the memory module 530. The control module 510 may generate the virtual space data or acquire the virtual space data from the server 600 or the like.

The control module 510 places objects in the virtual space 11 using object data representing the objects. The object data is stored in the memory module 530, for example. The control module 510 may generate the object data or obtain the object data from the server 600 or the like. The objects may include, for example, an avatar object that is an avatar of the user 5, a character object, an operational object such as a virtual hand that is operated by the controller 300, landscapes including forests, mountains, and the like that are placed according to the progress of the game story, cityscapes, animals, and the like.

The control module 510 places in the virtual space 11 an avatar object of the user 5 of another computer 200 connected via the network 2. In one aspect, the control module 510 places in the virtual space 11 an avatar object of the user 5. In one aspect, the control module 510 places in the virtual space 11 an avatar object that resembles the user 5 based on an image including the user 5. In another aspect, the control module 510 places in the virtual space 11 an avatar object that has been selected by the user 5 from among multiple types of avatar objects (e.g., objects that resemble animals or deformed human objects).

The control module 510 determines the inclination of the HMD 120 based on the output of the HMD sensor 410. In another aspect, the control module 510 determines the inclination of the HMD 120 based on the output of the sensor 190 functioning as a motion sensor. The control module 510 detects the organs that make up the face of the user 5 (e.g., mouth, eyes, eyebrows) from the images of the face of the user 5 generated by the first camera 150 and the second camera 160. The control module 510 detects the movement (shape) of each detected organ.

The control module 510 detects the line of sight of the user 5 in the virtual space 11 based on a signal from the gaze sensor 140. The control module 510 detects the viewpoint position (coordinate value in the XYZ coordinate system) where the detected line of sight of the user 5 intersects with the celestial sphere of the virtual space 11. More specifically, the control module 510 detects the viewpoint position based on the line of sight of the user 5 defined in the uvw coordinate system and the position and inclination of the virtual camera 14. The control module 510 transmits the detected viewpoint position to the server 600. In another aspect, the control module 510 may be configured to transmit line of sight information representing the line of sight of the user 5 to the server 600. In such a case, the server 600 may calculate the viewpoint position based on the line of sight information received.

The control module 510 reflects the movement of the HMD 120 detected by the HMD sensor 410 to the avatar object. For example, the control module 510 detects that the HMD 120 has been tilted and tilts and positions the avatar object. The control module 510 reflects the detected movement of the facial organs to the face of the avatar object placed in the virtual space 11. The control module 510 receives gaze information of the other user 5 from the server 600 and reflects it in the gaze of the avatar object of the other user 5. In a certain aspect, the control module 510 reflects the movement of the controller 300 to the avatar object or the operation object. In this case, the controller 300 may be equipped with a motion sensor, an acceleration sensor, or multiple light-emitting elements (e.g., infrared LEDs) for detecting the movement of the controller 300. The movement of the controller 300 may also be the movement of the analog stick 390 or the movement of the buttons 370 and 380. The control module 510 may then, for example, move the avatar object within the virtual space 11 based on the movement of the analog stick 390 (in other words, the user's operation on the analog stick 390).

The control module 510 places an operation object in the virtual space 11 for receiving an operation by the user 5 in the virtual space 11. The user 5 operates, for example, an object placed in the virtual space 11 by operating the operation object. In one aspect, the operation object may include, for example, a hand object that is a virtual hand corresponding to the hand of the user 5. In one aspect, the control module 510 moves the hand object in the virtual space 11 in conjunction with the movement of the hand of the user 5 in the real space based on the output of the motion sensor 420. In one aspect, the operation object may correspond to the hand portion of an avatar object.

The control module 510 detects a collision when each of the objects placed in the virtual space 11 collides with another object. The control module 510 can detect, for example, the timing when a collision area of one object comes into contact with a collision area of another object, and performs a predetermined process when this detection is made. The control module 510 can detect the timing when objects are no longer in contact with each other, and performs a predetermined process when this detection is made. The control module 510 can detect when objects are in contact with each other. For example, when a control object comes into contact with another object, the control module 510 detects that the control object has come into contact with the other object, and performs a predetermined process.

In one aspect, the control module 510 controls the image display on the monitor 130 of the HMD 120. For example, the control module 510 places a virtual camera 14 in the virtual space 11. The control module 510 controls the position of the virtual camera 14 in the virtual space 11 and the tilt (direction) of the virtual camera 14. The control module 510 determines the field of view 15 according to the tilt of the head of the user 5 wearing the HMD 120 and the position of the virtual camera 14. The rendering module 520 generates a field of view image 17 to be displayed on the monitor 130 based on the determined field of view 15. The field of view image 17 generated by the rendering module 520 is output to the HMD 120 by the communication control module 540.

When the control module 510 detects speech from the user 5 using the microphone 170 from the HMD 120, it identifies the computer 200 to which voice data corresponding to the speech is to be sent. The voice data is sent to the computer 200 identified by the control module 510. When the control module 510 receives voice data from another user's computer 200 via the network 2, it outputs the voice (speech) corresponding to the voice data from the speaker 180.

The memory module 530 holds data that is used by the computer 200 to provide the virtual space 11 to the user 5. In one aspect, the memory module 530 holds space information, object information, and user information.

The spatial information holds one or more templates defined to provide the virtual space 11.

The object information includes a plurality of panoramic images 13 that constitute the virtual space 11, and object data for placing objects in the virtual space 11. The panoramic images 13 may include still images and moving images. The panoramic images 13 may include images of unreal space and images of real space. Images of unreal space include, for example, images generated by computer graphics.

The user information holds a user ID that identifies the user 5. The user ID may be, for example, an IP (Internet Protocol) address or a MAC (Media Access Control) address that is set in the computer 200 used by the user. In another aspect, the user ID may be set by the user. The user information includes a program for causing the computer 200 to function as a control device for the HMD system 100. The user information also includes information that is managed for each service account (in other words, for each user ID).

The data and programs stored in the memory module 530 are input by the user 5 of the HMD 120. Alternatively, the processor 210 downloads the programs or data from a computer (e.g., server 600) operated by the operator providing the content, and stores the downloaded programs or data in the memory module 530.

The communication control module 540 can communicate with the server 600 and other information and communication devices via the network 2.

In one aspect, the control module 510 and the rendering module 520 may be realized using, for example, Unity (registered trademark) provided by Unity Technologies, Inc. In another aspect, the control module 510 and the rendering module 520 may be realized as a combination of circuit elements that realize each process.

Processing in computer 200 is realized by hardware and software executed by processor 210. Such software may be stored in advance on a hard disk or other memory module 530. The software may be stored on a CD-ROM or other computer-readable non-volatile data recording medium and distributed as a program product. Alternatively, the software may be provided as a downloadable program product by an information provider connected to the Internet or other network. Such software is read from the data recording medium by an optical disk drive or other data reading device, or downloaded from server 600 or other computer via communication control module 540, and then temporarily stored in memory module 530. The software is read from memory module 530 by processor 210 and stored in RAM in the form of an executable program. Processor 210 executes the program.

[Control structure of HMD system]
The control structure of the HMD set 110 will be described with reference to Fig. 11. Fig. 11 is a sequence chart showing a part of the processing executed in the HMD set 110 according to an embodiment.

As shown in FIG. 11, in step S1110, the processor 210 of the computer 200, as the control module 510, identifies virtual space data and defines the virtual space 11.

In step S1120, the processor 210 initializes the virtual camera 14. For example, the processor 210 places the virtual camera 14 in a work area of the memory at a predefined center 12 in the virtual space 11, and points the line of sight of the virtual camera 14 in the direction in which the user 5 is facing.

In step S1130, the processor 210, as the rendering module 520, generates field of view image data for displaying an initial field of view image. The generated field of view image data is output to the HMD 120 by the communication control module 540.

In step S1132, the monitor 130 of the HMD 120 displays a field of view image based on the field of view image data received from the computer 200. The user 5 wearing the HMD 120 can recognize the virtual space 11 by visually recognizing the field of view image.

In step S1134, the HMD sensor 410 detects the position and inclination of the HMD 120 based on the multiple infrared lights emitted from the HMD 120. The detection results are output to the computer 200 as motion detection data.

In step S1140, the processor 210 determines the field of view direction of the user 5 wearing the HMD 120 based on the position and tilt contained in the motion detection data of the HMD 120.

In step S1150, the processor 210 executes the application program and places objects in the virtual space 11 based on instructions included in the application program.

In step S1160, the controller 300 detects an operation by the user 5 and outputs detection data representing the detected operation to the computer 200. In another aspect, the operation by the user 5 may be detected based on an image from a camera arranged around the user 5.

In step S1170, the processor 210 detects the operation of the controller 300 by the user 5 based on the detection data acquired from the controller 300.

In step S1180, the processor 210 generates field of view image data based on the operation of the controller 300 by the user 5. The generated field of view image data is output to the HMD 120 by the communication control module 540.

In step S1190, the HMD 120 updates the field of view image based on the received field of view image data and displays the updated field of view image on the monitor 130.

[Avatar Object]
Avatar objects according to the present embodiment will be described with reference to Figs. 12(A) and (B). Hereinafter, avatar objects of each user 5 of the HMD sets 110A and 110B will be described. Hereinafter, the user of the HMD set 110A will be referred to as user 5A, the user of the HMD set 110B as user 5B, the user of the HMD set 110C as user 5C, and the user of the HMD set 110D as user 5D. A is added to the reference symbol of each component related to the HMD set 110A, B is added to the reference symbol of each component related to the HMD set 110B, C is added to the reference symbol of each component related to the HMD set 110C, and D is added to the reference symbol of each component related to the HMD set 110D. For example, the HMD 120A is included in the HMD set 110A.

FIG. 12(A) is a schematic diagram showing a situation in which each HMD 120 provides a virtual space 11 to a user 5 in a network 2. Computers 200A-200D provide virtual spaces 11A-11D to users 5A-5D, respectively, via HMDs 120A-120D. In the example shown in FIG. 12(A), virtual space 11A and virtual space 11B are configured with the same data. In other words, computer 200A and computer 200B share the same virtual space. In virtual space 11A and virtual space 11B, there exist an avatar object 6A of user 5A and an avatar object 6B of user 5B. Although avatar object 6A in virtual space 11A and avatar object 6B in virtual space 11B are each wearing an HMD 120, this is for ease of explanation, and in reality, these objects do not wear an HMD 120.

In one aspect, the processor 210A may position a virtual camera 14A that captures a field of view image 17A of the user 5A at the eye position of the avatar object 6A.

Figure 12 (B) is a diagram showing a field of view image 17A of user 5A in Figure 12 (A). Field of view image 17A is an image displayed on monitor 130A of HMD 120A. This field of view image 17A is an image generated by virtual camera 14A. An avatar object 6B of user 5B is displayed in field of view image 17A. Although not specifically shown, avatar object 6A of user 5A is similarly displayed in the field of view image of user 5B.

In the state of FIG. 12(B), user 5A can communicate with user 5B through dialogue via virtual space 11A. More specifically, the voice of user 5A picked up by microphone 170A is transmitted to HMD 120B of user 5B via server 600 and output from speaker 180B provided on HMD 120B. The voice of user 5B is transmitted to HMD 120A of user 5A via server 600 and output from speaker 180A provided on HMD 120A.

The movements of user 5B (movement of HMD 120B and movement of controller 300B) are reflected by processor 210A in avatar object 6B placed in virtual space 11A. As a result, avatar object 6B, which moves as operated by user 5B, is visible to user 5A.

Figure 13 is a sequence chart showing a part of the processing executed in the HMD system 100 according to the present embodiment. Although the HMD set 110D is not shown in Figure 13, the HMD set 110D operates in the same manner as the HMD sets 110A, 110B, and 110C. In the following description, A will be added to the reference number of each component related to the HMD set 110A, B will be added to the reference number of each component related to the HMD set 110B, C will be added to the reference number of each component related to the HMD set 110C, and D will be added to the reference number of each component related to the HMD set 110D.

In step S1310A, the processor 210A in the HMD set 110A acquires avatar information for determining the movement of the avatar object 6A in the virtual space 11A. The avatar information includes information about the avatar, such as, for example, movement information, face tracking data, and voice data. The movement information includes information indicating a temporal change in the position and inclination of the HMD 120A, information indicating the movement of the hand of the user 5A detected by the motion sensor 420A, and information indicating the operation of the user detected by the controller 300. The face tracking data includes data specifying the position and size of each part of the face of the user 5A. The face tracking data includes data indicating the movement of each organ constituting the face of the user 5A and gaze data. The voice data includes data indicating the voice of the user 5A acquired by the microphone 170A of the HMD 120A. The avatar information may include information specifying the avatar object 6A, or the user 5A associated with the avatar object 6A, and information specifying the virtual space 11A in which the avatar object 6A exists. Examples of information for identifying the avatar object 6A and the user 5A include a user ID. Examples of information for identifying the virtual space 11A in which the avatar object 6A exists include a room ID. The processor 210A transmits the avatar information acquired as described above to the server 600 via the network 2.

In step S1310B, the processor 210B in the HMD set 110B acquires avatar information for determining the movement of the avatar object 6B in the virtual space 11B, similar to the processing in step S1310A, and transmits it to the server 600. Similarly, in step S1310C, the processor 210C in the HMD set 110C acquires avatar information for determining the movement of the avatar object 6C in the virtual space 11C, and transmits it to the server 600.

In step S1320, the server 600 temporarily stores the avatar information received from each of the HMD sets 110A, 110B, and 110C. The server 600 integrates the avatar information of all users (in this example, users 5A to 5C) associated with the common virtual space 11 based on the user ID and room ID, etc., included in each piece of avatar information. The server 600 then transmits the integrated avatar information to all users associated with the virtual space 11 at a predetermined timing. This executes a synchronization process. This synchronization process allows the HMD sets 110A, 110B, and 110C to share each other's avatar information at approximately the same timing.

Next, based on the avatar information transmitted from the server 600 to each of the HMD sets 110A to 110C, each of the HMD sets 110A to 110C executes the process of steps S1330A to S1330C. The process of step S1330A corresponds to the process of step S1180 in FIG. 11.

In step S1330A, the processor 210A in the HMD set 110A updates the information of the avatar objects 6B and avatar objects 6C of the other users 5B and 5C in the virtual space 11A. Specifically, the processor 210A updates the position, orientation, etc. of the avatar object 6B in the virtual space 11 based on the movement information included in the avatar information transmitted from the HMD set 110B. For example, the processor 210A updates the information (position, orientation, etc.) of the avatar object 6B included in the object information stored in the memory module 530. Similarly, the processor 210A updates the information (position, orientation, etc.) of the avatar object 6C in the virtual space 11 based on the movement information included in the avatar information transmitted from the HMD set 110C.

In step S1330B, the processor 210B in the HMD set 110B updates the information of the avatar objects 6A and 6C of the users 5A and 5C in the virtual space 11B, similar to the processing in step S1330A. Similarly, in step S1330C, the processor 210C in the HMD set 110C updates the information of the avatar objects 6A and 6B of the users 5A and 5B in the virtual space 11C.

[Module detailed configuration]
The details of the module configuration of computer 200 will be described with reference to Fig. 14. Fig. 14 is a block diagram showing the detailed configuration of modules of computer 200 according to an embodiment.

As shown in FIG. 14, the control module 510 includes a virtual camera control module 1421, a field of view determination module 1422, a reference gaze identification module 1423, a face organ detection module 1424, a motion detection module 1425, a virtual space definition module 1426, a virtual object generation module 1427, an operation object control module 1428, and an avatar control module 1429. The rendering module 520 includes a field of view image generation module 1438.

The virtual camera control module 1421 places the virtual camera 14 in the virtual space 11. The virtual camera control module 1421 controls the placement position of the virtual camera 14 in the virtual space 11 and the orientation (tilt) of the virtual camera 14. The field of view determination module 1422 defines the field of view 15 according to the orientation of the head of the user wearing the HMD 120 and the placement position of the virtual camera 14. The field of view image generation module 1438 generates the field of view image 17 to be displayed on the monitor 130 based on the determined field of view 15.

The reference gaze identification module 1423 identifies the gaze of the user 5 based on a signal from the gaze sensor 140. The face organ detection module 1424 detects the organs (e.g., mouth, eyes, eyebrows) that make up the face of the user 5 from the images of the user's 5's face generated by the first camera 150 and the second camera 160. The movement detection module 1425 detects the movement (shape) of each organ detected by the face organ detection module 1424.

The virtual space definition module 1426 defines the virtual space 11 in the HMD system 100 by generating virtual space data representing the virtual space 11.

The virtual object generation module 1427 generates objects to be placed in the virtual space 11. The objects may include, for example, landscapes including forests, mountains, and other things, animals, etc. that are placed according to the progress of the game story.

The operation object control module 1428 places an operation object in the virtual space 11 for receiving operations by the user in the virtual space 11. The user operates the operation object to, for example, operate an object placed in the virtual space 11. In one aspect, the operation object may include, for example, a hand object corresponding to the hand of the user wearing the HMD 120. In one aspect, the operation object may correspond to the hand portion of an avatar object described below.

The avatar control module 1429 generates data for placing an avatar object 6 of a user of another computer 200 connected via the network 2 in the virtual space 11. In one aspect, the avatar control module 1429 generates data for placing an avatar object 6 of a user 5 in the virtual space 11. In one aspect, the avatar control module 1429 generates an avatar object 6 that imitates a user 5 based on an image including the user 5. In another aspect, the avatar control module 1429 generates data for placing an avatar object 6 selected by the user 5 from among multiple types of avatar objects 6 (e.g., objects imitating animals or deformed human objects) in the virtual space 11.

The avatar control module 1429 reflects the movement of the HMD 120 detected by the HMD sensor 410 to the avatar object 6. For example, the avatar control module 1429 detects that the HMD 120 has been tilted and generates data for tilting and positioning the avatar object 6. In one aspect, the avatar control module 1429 reflects the movement of the controller 300 to the avatar object 6. In another aspect, the avatar control module 1429 reflects the movement of the facial organs detected by the movement detection module 1425 to the face of the avatar object 6 placed in the virtual space 11. In other words, the avatar control module 1429 reflects the facial movement of the user 5A to the avatar object 6. In this way, the avatar object 6 is operated (in other words, moved) by the movement detected by the HMD sensor 410, the controller 300, or the movement detection module 1425.

The rendering module 520 displays the avatar object 6 on the monitor 130 of the HMD 120 in the display format set by the avatar control module 1429.

[Server module configuration]
The module configuration of server 600 will be described with reference to Fig. 15. Fig. 15 is a block diagram showing the module configuration of server 600 according to an embodiment. As shown in Fig. 15, server 600 includes a control module 1610, a memory module 1630, and a communication control module 1640. In one aspect, control module 1610 is realized by processor 610. Memory module 1630 is realized by memory 620 or storage 630. Communication control module 1640 is realized by communication interface 650.

The control module 1610 includes a recommendation module 1731, an attribute setting module 1732, a behavior history acquisition module 1733, an access control module 1734, and a collaboration management module 1741.

Memory module 1630 holds data used by computer 200 to provide virtual space 11 to user 5. In one aspect, memory module 1630 holds spatial information, object information, and user information. The spatial information, object information, and user information of memory module 1630 may respectively include the spatial information, object information, and user information of memory module 530 described above. Therefore, a description thereof will be omitted here.

The communication control module 1640 receives various information and various requests from each HMD set 110. As an example, the information that the communication control module 1640 receives from each HMD set 110 may include spatial information, object information, user information, and avatar information. The communication control module 1640 transmits various information and various requests to each HMD set 110. As an example, the information that the communication control module 1640 transmits to each HMD set 110 may include spatial information, object information, user information, and avatar information.

The processing in the server 600 is realized by hardware and software executed by the processor 610. Such software may be stored in advance on a hard disk or other memory module 1630. The software may be stored on a CD-ROM or other computer-readable non-volatile data recording medium and distributed as a program product. Alternatively, the software may be provided as a downloadable program product by an information provider connected to the Internet or other network. Such software is read from the data recording medium by an optical disk drive or other data reading device, or downloaded from a specific computer via the communication control module 1640, and then temporarily stored in the memory module 1630. The software is read from the memory module 1630 by the processor 610 and stored in the RAM in the form of an executable program. The processor 610 executes the program.

The above-described module configuration of computer 200 and server 600 is merely an example. Each device of computer 200 and server 600 may have at least some of the modules (in other words, functions) of the other devices. Furthermore, each device such as computer 200 and server 600 does not have to be realized by a single device, and may be realized, for example, by multiple devices connected via a network, etc.

In addition, in this embodiment, the processor 210 of the computer 200 or the processor 610 of the server 600 will be described as executing the programs stored in the HMD system 100 to perform the processes described above or below. However, at least a part of the processes described above or below that are performed by the processor 210 may be executed by a processor other than the processor 210. Also, at least a part of the processes described above or below that are performed by the processor 610 may be executed by a processor other than the processor 610. In other words, the computer that executes the programs in this embodiment may be either the computer 200 or the server 600, or may be realized by a combination of multiple devices.

The HMD system 100 of this embodiment makes recommendations to the user 5 based on the behavioral history. The HMD system 100 of this embodiment provides a metaverse as a virtual space 11 in which the users 5 can interact with each other via avatar objects 6. Hereinafter, the virtual space 11 will be referred to as the metaverse. Also, below, the avatar objects 6 placed in the virtual space 11 may be simply referred to as avatars. Note that the avatars can be considered as users in the metaverse.

The metaverse may or may not contain locations based on (e.g., imitating) locations (e.g., regions or facilities) that exist in the real world (in other words, real space). In this embodiment, the metaverse will be described as containing virtual Shibuya, virtual Harajuku, and virtual Akihabara, which respectively imitate Shibuya, Harajuku, and Akihabara in the real world.

[Recommendations about things in the metaverse based on behavioral history in the metaverse]
The recommendation module 1731 makes recommendations regarding a specific thing in the metaverse based on the behavior history of the user 5 in the metaverse. Specifically, for example, the recommendation module 1731 determines a thing to recommend based on the behavior history of the user 5 in the metaverse, and transmits information about the recommended thing (hereinafter referred to as "recommended information") to the recommendation information presentation module 1721. The recommendation information presentation module 1721 is provided, for example, in the control module 510 of the computer 200 of the user 5. Upon receiving the recommendation information, the recommendation information presentation module 1721 causes the monitor 130 to display information about the recommended thing.

The recommendation module 1731 makes a predetermined recommendation regarding friendships in the metaverse, for example, based on the behavioral history of the user 5. Specifically, the recommendation module 1731 recommends to the user 5, for example, other users 5 (in other words, avatars of the other users 5) who are likely to be compatible with the user 5 as a recommendation regarding friendships. More specifically, the recommendation module 1731 recommends to the user 5 other users 5 who are likely to become friends with the user 5. In this case, the recommendation module 1731, for example, determines other users 5 (hereinafter referred to as "recommended users") to be recommended to the user 5 from among multiple users 5, and transmits recommendation information indicating the recommended users to the recommendation information presentation module 1721 of the computer 200 of the user 5. In addition, when the recommendation information presentation module 1721 receives the recommendation information, it displays a display related to the recommendation of the recommended user to the user 5 on the monitor 130. The display related to the recommendation may include, for example, a display of the user name of the recommended user, a display related to the reception of contact with the recommended user, a display indicating the location of the recommended user, and the like. In other words, when the display related to the recommendation is displayed, an operation by user 5 to contact the recommended user (e.g., an operation by controller 300, etc.) may be accepted. Note that, here, a display related to accepting a contact with the recommended user includes, for example, a display related to accepting an application to register the recommended user as a friend. In other words, when the display related to the recommendation is displayed, an operation to apply to register the recommended user as a friend may be accepted.

In addition, the recommendation module 1731 may recommend to the user 5, for example, a group that is likely to be compatible with the user 5 (in other words, a group to which other users 5 who are compatible with the user 5 are likely to belong) as a recommendation regarding friendship, rather than recommending other specific users 5 to the user 5. In this case, the recommendation module 1731 determines a group to be recommended to the user 5 based on, for example, the behavioral history of the user 5, and transmits recommendation information indicating the recommended group to the recommendation information presentation module 1721 of the computer 200 of the user 5. In addition, when the recommendation information is received, the recommendation information presentation module 1721 displays a display related to the recommendation of the group to the user 5 on the monitor 130. The display related to the recommendation may include, for example, a display of the group name of the recommended group, a display related to the reception of contact with the group (for example, the user 5 representing the group), a display showing the location of the group's headquarters, and the like. Note that, here, the display related to the reception of contact with the group includes, for example, a display related to the reception of an application to join the group, and the like.

Furthermore, the recommendation module 1731 makes a predetermined recommendation regarding content in the metaverse based on, for example, the behavioral history of the user 5. Specifically, for example, the recommendation module 1731 may recommend a predetermined location (e.g., an area or a facility) in the metaverse to the user 5 as a recommendation regarding content. Also, for example, the recommendation module 1731 may recommend a predetermined service in the metaverse to the user 5 as a recommendation regarding content.

The behavioral history of each user 5 in the metaverse is stored in the virtual space history storage unit 1751 provided in the memory module 1630 of the server 600. Note that the behavioral history in the metaverse may be stored in the virtual space history storage unit 1751 by the control module 1610 (in other words, the virtual space history acquisition means) each time the user 5 performs various actions in the metaverse. An example of the behavioral history in the metaverse stored in the virtual space history storage unit 1751 is shown below.

The behavioral history may, for example, relate to the outfit (in other words, appearance) of the avatar. Specifically, the behavioral history may include, for example, information regarding the number of times the avatar's outfit (for example, clothing accessories (e.g., clothes, hats, accessories, footwear, etc.) or hairstyle, etc.) has been changed. The behavioral history may also include, for example, information regarding the number of clothing accessories (e.g., total number or number of types, etc.) that the avatar has acquired (in other words, possesses).

The behavioral history may also be related to communication between users. Specifically, the behavioral history may include, for example, information about the person with whom a conversation was held, or information about the number or frequency of conversations with a specific person. The behavioral history may also include information about the person with whom a specific content was used together, or information about the number or frequency of use of content with a specific person together. Here, using content together may mean, for example, playing a specific game together in the metaverse (for example, playing together or against each other), participating together in a specific event in the metaverse, or being at a specific location in the metaverse at the same time. In other words, the behavioral history may include information based on communication between users in the metaverse (for example, information about conversations, use of content together, etc.).

The behavioral history may also include information regarding the distance traveled within the metaverse. The behavioral history may also include information regarding the number or frequency of times each user has accessed (in other words, logged into) the metaverse. The behavioral history may also include information regarding places visited within the metaverse, information regarding the time a particular place was visited, and so on. In other words, the behavioral history may include information based on movement within the metaverse (e.g., information regarding the distance traveled, places visited by movement, etc.).

The behavioral history in the metaverse can be considered as information regarding operations performed by the user 5. Specifically, the behavioral history in the metaverse can be considered as information regarding operations performed by the user 5 on the avatar object 6.

Recommendations to user 5 regarding specific things in the metaverse based on the behavior history in the metaverse may be made, for example, as follows. That is, attributes (hereinafter referred to as "virtual space attributes") may be set for each user 5 based on the behavior history in the metaverse, and recommendation module 1731 may make recommendations based on the virtual space attributes. In this case, attribute setting module 1732 may set virtual space attributes for user 5 based on the behavior history of user 5 in the metaverse, for example, and store the virtual space attributes of user 5 in user attribute storage unit 1752 provided in memory module 1630. Also, recommendation module 1731 may make recommendations to user 5 based on the virtual space attributes set for user 5, for example.

Note that multiple virtual space attributes may be assigned to one user 5, and only one virtual space attribute may be assigned to one user 5.

Attributes in virtual space indicate the characteristics and qualities of user 5 in the metaverse. Here, as an example, a case will be described in which attributes in virtual space such as "active," "otaku," "fashionable," "gourmet," and "inactive" are set for user 5, but the types of attributes in virtual space are not limited to these.

The attribute setting module 1732 may determine that the user 5 is "active" and assign the virtual space attribute of "active" to the user 5, for example, as shown in FIG. 16, based on the following: the distance traveled in the metaverse is equal to or greater than a predetermined threshold (in other words, a predetermined level), the number or frequency of logins is equal to or greater than a predetermined threshold, the number or frequency of conversations with other users in the metaverse is equal to or greater than a predetermined threshold, the number of users with whom the user has conversations in the metaverse, the number of users with whom the user has used predetermined content together in the metaverse, the number of users registered as friends, etc. are equal to or greater than a predetermined threshold. Note that the conversation may be an exchange of text messages or a voice call, etc.

The attribute setting module 1732 may also determine that user 5 is an "otaku" and assign the virtual space attribute of "otaku" to user 5 based on, for example, the fact that the distance traveled in the metaverse indicated by the user 5's behavioral history is less than a predetermined threshold, that the people with whom the user converses in the metaverse are almost fixed, and that the number or frequency of use of two-dimensional content such as anime, manga, and games is greater than or equal to a predetermined threshold.

The attribute setting module 1732 may also determine that user 5 is "fashionable" and assign an in-virtual space attribute of "fashionable" to user 5 based on, for example, the number or frequency of outfit changes in the metaverse as indicated by the user 5's behavioral history being equal to or greater than a predetermined threshold, or the number of acquired clothing items (e.g., total number or number of types, etc.) being equal to or greater than a predetermined threshold.

The attribute setting module 1732 may also determine that user 5 is a "gourmet" based on, for example, the number or frequency of use of cooking-related content in the metaverse as indicated by the user 5's behavioral history being equal to or greater than a predetermined threshold, and assign the virtual space attribute of "gourmet" to user 5.

The attribute setting module 1732 may also determine that user 5 is "inactive" based on, for example, the fact that the distance traveled in the metaverse, as indicated by the user 5's behavioral history, is less than a predetermined threshold, or the number or frequency of logins is less than a predetermined threshold, and assign the user 5 an in-virtual space attribute of "inactive."

When an attribute is set based on some distance, number, frequency, or the like (in other words, when an attribute is set based on a parameter being equal to or greater than a predetermined level), the distance, number, frequency, or the like may be, for example, the total distance, total number, or frequency within a predetermined period, or the average distance, average number, or average frequency within a predetermined period. The predetermined period may be the period from when the user 5 first accesses the metaverse to the time when the attribute is determined, or may be within a few days, within a few months, or until the number of logins reaches a predetermined number. For example, when a parameter is set based on a parameter being equal to or greater than a predetermined threshold, there is no particular limitation on the internal processing, as long as the predetermined attribute is assigned when the parameter is equal to or greater than a predetermined threshold.

The condition for setting a predetermined attribute for the user 5 may be one condition or multiple conditions. When multiple conditions are set, the attribute of the user 5 may be determined based on one of the multiple set conditions being satisfied, or the attribute of the user 5 may be determined based on multiple or all of the multiple set conditions being satisfied. In this embodiment, a value related to each attribute in the virtual space (hereinafter referred to as an "attribute value") is set for each condition such as "a certain parameter is equal to or greater than a predetermined threshold value," and when a certain condition is satisfied, the attribute setting module 1732 assigns the attribute value set for that condition to the user. The attribute setting module 1732 sets the attribute in the virtual space based on the cumulative value of the attribute values. In other words, an attribute in the virtual space is set for each action that the user 5 can perform in the metaverse (in other words, each condition that can be achieved), and the attribute setting module 1732 assigns the attribute value of the attribute in the virtual space set for the action performed by the user 5 to the user 5, and when the cumulative value of the attribute value of a certain attribute in the virtual space reaches a predetermined value, the certain attribute in the virtual space may be set to the user 5. Specifically, for example, when the moving distance of the user 5 in the metaverse becomes equal to or exceeds a predetermined threshold, or when the login frequency of the user 5 becomes equal to or exceeds a predetermined threshold, the cumulative value of the attribute value of the attribute "active" in the virtual space increases. Also, when the moving distance of the user 5 in the metaverse becomes equal to or exceeds a predetermined threshold, the cumulative value of the attribute value of the attribute "otaku" in the virtual space decreases. Also, for example, when the frequency of changing the outfit of the user 5 in the metaverse becomes equal to or exceeds a predetermined threshold, the cumulative value of the attribute value of the attribute "fashionable" in the virtual space increases. Then, for example, when the cumulative value of the attribute value of the attribute "active" in the virtual space reaches a predetermined value, the attribute setting module 1732 sets the attribute "active" in the virtual space for user 5.

In addition, each content in the metaverse has one or more virtual space attributes, and the attribute setting module 1732 may assign to the user 5 an attribute value of the virtual space attribute of the content used by the user 5 according to the virtual space attribute of the content used by the user 5 (in other words, accessed). Then, when the attribute value of a specific virtual space attribute (specifically, the cumulative value of the attribute value) reaches a threshold, the attribute setting module 1732 may set the specific virtual space attribute to the user 5. In such a case, an attribute in the virtual space is set for each action that the user 5 may perform in the metaverse (for example, use of content with a virtual space attribute set), and the attribute setting module 1732 may assign to the user 5 an attribute value related to the virtual space attribute set for the action performed by the user 5. In other words, the content in the metaverse includes content with an attribute set, and the attribute setting module 1732 may set a certain attribute to the user 5 based on the user 5's use of content with a certain attribute set. The attribute setting module 1732 may assign to the user 5 the attribute value of the virtual space attribute set for the content used each time the user 5 uses the content, or may assign to the user 5 the attribute value of a specific virtual space attribute when the number of times or frequency of use of the content with a specific virtual space attribute is equal to or exceeds a predetermined threshold. The setting information of the virtual space attribute related to the content in the metaverse may be stored in advance in the memory module 1630 of the server 600, for example.

For example, in the metaverse, there are a plurality of locations to which virtual space attributes are attached, and the attribute setting module 1732 may assign to the user 5 an attribute value of the virtual space attribute attached to the location visited (in other words, used) by the user 5. In other words, the attribute setting module 1732 may assign to the user 5 an attribute value according to the location visited by the user 5. Specifically, for example, in the metaverse, there are a plurality of areas to which virtual space attributes are attached (specifically, for example, "virtual Shibuya" and "virtual Harajuku" to which the virtual space attribute of "fashionable" is attached, and "virtual Akihabara" to which the virtual space attribute of "otaku" is attached, etc.), and the attribute setting module 1732 may assign to the user 5 an attribute value of the virtual space attribute attached to the area based on the user 5's visit to the area in the metaverse. Also, for example, in the metaverse there are multiple facilities with virtual space attributes (specifically, for example, a commercial facility with the virtual space attribute of "fashionable," and a game center and a mahjong parlor with the virtual space attribute of "otaku"), and the attribute setting module 1732 may assign to user 5 the attribute value of the virtual space attribute attached to a facility based on user 5's visit to that facility in the metaverse.

In addition, for example, multiple entertainments (e.g., games) with virtual space attributes are provided in the metaverse, and the attribute setting module 1732 may assign the attribute value of the entertainment used by the user 5 to the user 5. For example, entertainments provided in the metaverse include mahjong with the virtual space attribute "otaku," karaoke with the virtual space attribute "active," and audiovisual content with each virtual space attribute, and the attribute setting module 1732 may assign the attribute value of the virtual space attribute attached to an entertainment to the user 5 based on the user 5's use (in other words, experience) of that entertainment in the metaverse.

In addition, for example, multiple events (e.g., live music concerts, festivals, sporting events, etc.) with virtual space attributes are prepared in the metaverse, and the attribute setting module 1732 may assign to user 5 the attribute value of the virtual space attribute attached to an event based on user 5's participation (in other words, use) in that event.

For example, the recommendation module 1731 recommends to the user 5, another user 5 (in other words, the avatar of the other user 5) to which a virtual space attribute corresponding to the virtual space attribute set to the user 5 is set. Specifically, for example, the recommendation module 1731 may perform the following process. That is, for example, as shown in FIG. 16, the recommendation module 1731 may recommend other users to which a virtual space attribute of "active" or "fashionable" is set to a user to which a virtual space attribute of "active" is set. Also, for example, the recommendation module 1731 may recommend other users to which a virtual space attribute of "otaku" or "inactive" is set to a user to which a virtual space attribute of "fashionable" is set. Also, for example, the recommendation module 1731 may recommend other users to which a virtual space attribute of "fashionable" or "active" is set to a user to which a virtual space attribute of "fashionable" is set to a user. Also, for example, the recommendation module 1731 may recommend other users to whom the virtual space attribute "gourmet" is set to a user to whom the virtual space attribute "gourmet" is set. Also, for example, the recommendation module 1731 may recommend other users to whom the virtual space attribute "inactive" or "otaku" is set to a user to whom the virtual space attribute "inactive" is set.

The recommendation module 1731 may also recommend to the user 5, for example, content according to the virtual space attribute set for the user. Specifically, for example, content in the metaverse is prepared with a recommended target attribute indicating which attribute the content is recommended to the user 5, and the recommendation module 1731 may recommend to the user 5 content with a recommended target attribute corresponding to the virtual space attribute set for the user 5. That is, for example, content in the metaverse may include content with recommended target attributes such as "active", "otaku", "fashionable", "gourmet", and "inactive" set as recommended target attributes, and the content may be recommended to the user 5 with a virtual space attribute that matches the recommended target attribute set for the content. More specifically, for example, the recommendation module 1731 may recommend content with a recommended target attribute of "active" to a user with a virtual space attribute of "active". Note that the setting information of the recommended target attribute for the content in the metaverse may be stored in advance in the memory module 1630 of the server 600, for example. Additionally, the attributes within the virtual space set for each piece of content may be used as recommended attributes.

In addition, the recommendation module 1731 may recommend to the user 5, for example, other users 5 who have a specific relationship with the user 5 in the metaverse and things in the metaverse that have a specific relationship. Here, the other users 5 who have a specific relationship with the user 5 may be, for example, other users 5 who have interactions with the user 5. In addition, the other users 5 who have interactions with the user 5 may be, for example, other users 5 who have had conversations with the user 5, other users 5 who have used content together, or other users 5 who are friends of the user 5. In addition, the other users 5 who have a specific relationship may be, for example, other users 5 who have a large number of interactions with the user 5 (for example, the total number of interactions is equal to or greater than a predetermined threshold or the number of interactions within a predetermined period is equal to or greater than a predetermined threshold (i.e., the frequency of interactions is high)). In addition, the other users 5 who have a large number of interactions may be, for example, other users 5 who have a large number of conversations with the user 5, or other users 5 who use content together. Further, the other user 5 having a specific relationship with the user 5 may be, for example, another user 5 having a common (for example, the same) virtual space attribute or a real world attribute to be described later with the user 5. Furthermore, the thing in the metaverse having a specific relationship with the other user 5 may be, for example, a content in the metaverse that is used frequently by the other user 5 (for example, a facility frequently visited or a game frequently used) (for example, a total number of uses is a predetermined threshold or more, or a number of uses within a predetermined period is a predetermined threshold or more (i.e., a high frequency of use)), or a user 5 (for example, a friend, etc.) who has interactions with the other user 5. In other words, the recommendation module 1731 may recommend the favorite content of the other user 5 to the user 5. The content that is used frequently by the other user 5 may be determined based on the behavior history of the other user 5 in the metaverse (for example, from the number of uses of each content indicated by the behavior history). Furthermore, regarding the number of interactions or the number of uses, a large number may be, for example, a relatively large number of interactions or uses among the user 5, or a number of interactions or uses that is greater than a predetermined number. In other words, when it is said to be equal to or greater than a certain threshold, the certain threshold may be fixed or variable (for example, variable depending on the number of interactions with each of the multiple other users 5, the number of times each of the multiple pieces of content is used, etc.).

The attributes in the virtual space may be more finely divided. For example, the attributes in the virtual space may classify the user 5 according to the hobbies and preferences of the user 5. The attribute setting module 1732 may set the attributes in the virtual space of the user 5 according to the usage history of the content in the metaverse. For example, when each user can set BGM in the metaverse, the attribute setting module 1732 may assign attributes such as "classical music lover", "rock lover", "pop music lover", and "anime song lover" to the user 5 according to which type of BGM is used frequently. The attribute setting module 1732 may assign the attribute "movie lover" to the user 5 who frequently watches movies in the metaverse, or the attribute "mahjong lover" to the user 5 who frequently plays mahjong in the metaverse. The attribute setting module 1732 may assign the attribute "visited virtual Shibuya" to the user 5 who has visited virtual Shibuya in the metaverse. The attribute setting module 1732 may also assign an attribute of "fan of a particular idol" to a user 5 who frequently uses content of a particular idol in the metaverse. The attribute setting module 1732 may also assign an attribute in the virtual space, such as "street type," "mode type," "natural type," or "rock type," to the user 5, depending on the type of outfit that the user 5 sets for the avatar in the metaverse (e.g., the number of times or frequency of wearing a particular type of outfit).

In this embodiment, the attribute setting module 1732 sets attributes in the virtual space for the user 5 based on the behavioral history of the user 5 in the metaverse, and the recommendation module 1731 makes recommendations regarding specific things in the metaverse based on the attributes in the virtual space. However, the recommendation module 1731 may make recommendations based on the behavioral history without the attribute setting module 1732 setting attributes in the virtual space.

The recommendation module 1731 may, for example, recommend other users who have the same behavioral history among multiple behavioral histories. The recommendation module 1731 may also, for example, recommend to the user 5 other users who have a common content usage history. For example, when the behavioral history of the user 5 and the behavioral history of the other user 5 indicate that multiple pieces of content that the user 5 and the other user 5 have used overlap, the recommendation module 1731 may recommend the other user 5 to the user 5. In other words, the recommendation module 1731 may recommend to the user 5 other users 5 who have characteristics in common with the user 5, such as other users 5 who have corresponding attributes or other users 5 who have common behavioral histories.

[Recommendations about things in the metaverse based on real-world behavioral history]
Instead of or in addition to making recommendations regarding specific things in the metaverse based on user 5's behavioral history within the metaverse, recommendation module 1731 may make recommendations regarding specific things in the metaverse based on user 5's behavioral history in the real world (in other words, outside the metaverse).

Recommendations to user 5 regarding specific things in the metaverse based on their real-world behavior history may be made, for example, as follows. That is, attributes (hereinafter referred to as "real-world attributes") may be set for each user 5 based on their real-world behavior history, and recommendation module 1731 may make recommendations based on the real-world attributes. In this case, attribute setting module 1732 may set real-world attributes for user 5 based on, for example, user 5's real-world behavior history, and store the real-world attributes of user 5 in user attribute storage unit 1752 provided in memory module 1630. Also, recommendation module 1731 may make recommendations to user 5 based on the real-world attributes set for user 5, for example.

Note that multiple real-world attributes may be assigned to one user 5, and only one real-world attribute may be assigned to one user 5.

Real-world attributes indicate the characteristics and qualities of user 5 in the real world. Here, as an example, a case will be described in which real-world attributes such as "active," "otaku," "fashionable," "gourmet," and "inactive" are set for user 5, but the types of real-world attributes are not limited to these. Also, like the attributes in virtual space, real-world attributes may be further subdivided. Note that the types of attributes included in the attributes in virtual space and the attributes in the real world may differ. In other words, the attributes in virtual space and the attributes in the real world may be classified differently.

The attribute setting module 1732 may determine that user 5 is "active" and assign a real-world attribute of "active" to user 5, for example, based on the following information shown in FIG. 16 : the distance traveled in the real world is equal to or greater than a predetermined threshold, the calories burned in the real world is equal to or greater than a predetermined threshold, the number or frequency of exercise in the real world is equal to or greater than a predetermined threshold, the number or frequency of posts on a social networking service (SNS) is equal to or greater than a predetermined threshold, the number or frequency of conversations with other users in a predetermined application outside the metaverse is equal to or greater than a predetermined threshold, or the number of users with whom user 5 has conversations in a predetermined application outside the metaverse is equal to or greater than a predetermined threshold.

The attribute setting module 1732 may also determine that user 5 is an "otaku" based on, for example, the fact that the distance traveled in the real world, as indicated by the user 5's behavioral history, is less than a predetermined threshold, and assign the real-world attribute of "otaku" to user 5.

The attribute setting module 1732 may determine that the user 5 is "fashionable" and assign the real-world attribute of "fashionable" to the user 5 based on, for example, the number or frequency of selfie photos posted on SNS being equal to or greater than a predetermined threshold, or the number or frequency of reactions (so-called "likes" or the like) to fashion-related posts on SNS being equal to or greater than a predetermined threshold, as indicated by the user 5's behavioral history. Note that the attribute setting module 1732 may set the real-world attribute of the user 5 to "street type", "mode type", "natural type", "rock type", or the like, depending on the tendency of the user's outfit type in the real world (for example, the number or frequency of wearing a particular type of outfit) detected by, for example, performing image recognition on photos of the user 5 in the user 5's SNS posts, or the like.

The attribute setting module 1732 may also determine that user 5 is a "gourmet" and assign a real-world attribute of "gourmet" to user 5 based on, for example, the number or frequency of posts about food on SNS being equal to or greater than a predetermined threshold, the number or frequency of reactions to posts about eating and drinking on SNS being equal to or greater than a predetermined threshold, or the number or frequency of visits to high-end restaurants being equal to or greater than a predetermined threshold, as indicated by the user 5's behavioral history.

The attribute setting module 1732 may also determine that user 5 is "inactive" and assign a real-world attribute of "inactive" to user 5 based on, for example, the fact that the distance traveled in the real world is less than a predetermined threshold, the calories burned in the real world are less than a predetermined threshold, or the number or frequency of exercise in the real world is less than a predetermined threshold, as indicated by the user 5's behavioral history.

When setting the real-world attributes of user 5 based on the above-mentioned conditions, the attribute setting module 1732 may assign values for each real-world attribute (hereinafter referred to as "attribute values") to user 5 according to actions taken by user 5, and set the real-world attributes based on the accumulated values, in the same manner as in the case of attributes in virtual space.

In addition, real-world attributes may be set in advance for real-world things (e.g., places, services, objects, etc.), and the attribute setting module 1732 may assign to the user 5 the attribute value of the real-world attribute of the place, service, or object used by the user 5 in accordance with the real-world attribute of the place, service, or object used by the user 5. Then, when the attribute value of a specific real-world attribute (specifically, the cumulative value of the attribute value) reaches a threshold value, the specific real-world attribute may be set to the user 5. In other words, some real-world things have attributes set, and the attribute setting module 1732 may set a certain attribute to the user 5 based on the user 5's use of a real-world thing to which a certain attribute has been set. Note that the setting information of the real-world attributes related to real-world things may be stored in advance in the memory module 1630 of the server 600, for example.

For example, a real-world attribute may be set for a particular location in the real world, and the attribute setting module 1732 may assign to the user 5 the attribute value of the real-world attribute assigned to the location visited by the user 5. Specifically, for example, there are a plurality of areas in the real world to which real-world attributes are assigned (specifically, for example, "Shibuya" and "Harajuku" to which the real-world attribute of "fashionable" is assigned, and "Akihabara" to which the real-world attribute of "otaku" is assigned), and the attribute setting module 1732 may assign to the user 5 the attribute value of the real-world attribute assigned to a certain area in the real world, based on the user 5 having visited that area. Also, for example, in the real world, there are a number of facilities to which real-world attributes are set (specifically, for example, a commercial facility to which the real-world attribute "fashionable" is set, a game center and a mahjong parlor to which the real-world attribute "otaku" is assigned, and a restaurant to which the real-world attribute "gourmet" is assigned), and the attribute setting module 1732 may assign to user 5, based on user 5's visit to a facility in the real world, the attribute value of the real-world attribute set for that facility.

In addition, for example, real-world attributes may be set for certain events in the real world (e.g., live music concerts, festivals, sporting events, etc.), and the attribute setting module 1732 may assign user 5 an attribute value of the real-world attribute of the event based on user 5's participation in the event in the real world.

For example, the recommendation module 1731 recommends to the user 5, other users 5 (in other words, avatars of the other users 5) to which attributes in the virtual space corresponding to the attributes in the real world set for the user 5 are set. Specifically, for example, the recommendation module 1731 may perform the following process. That is, for example, as shown in FIG. 16, the recommendation module 1731 may recommend other users 5 to which attributes in the virtual space of "active" or "fashionable" are set for a user 5 to which an attribute in the real world of "active" is set. Also, for example, the recommendation module 1731 may recommend other users 5 to which attributes in the virtual space of "otaku" or "inactive" are set for a user 5 to which an attribute in the real world of "otaku" is set. Also, for example, the recommendation module 1731 may recommend other users 5 to which attributes in the virtual space of "fashionable" or "active" are set for a user 5 to which an attribute in the real world of "fashionable" is set. Also, for example, the recommendation module 1731 may recommend other users 5 to whom the attribute in the virtual space is set as "gourmet" to a user 5 to whom the attribute in the real world is set as "gourmet." Also, for example, the recommendation module 1731 may recommend other users 5 to whom the attribute in the virtual space is set as "inactive" or "otaku" to a user 5 to whom the attribute in the real world is set as "inactive."

In addition, the recommendation module 1731 may recommend to the user 5, for example, content in the metaverse according to the real-world attribute set for the user 5. Specifically, for example, content in the metaverse may have a recommendation target attribute set to indicate which attribute the content is recommended to for the user 5, and the recommendation module 1731 may recommend to the user 5 content in which a recommendation target attribute corresponding to the real-world attribute set for the user 5 is set. That is, for example, content in the metaverse may have a recommendation target attribute set to "active," "otaku," "fashionable," "gourmet," "inactive," etc., and the content may be recommended to the user 5 in which a real-world attribute matching the recommendation target attribute set for the content is set. More specifically, for example, the recommendation module 1731 may recommend content in which a recommendation target attribute of "active" is set for a user in which a real-world attribute of "active" is set.

In this embodiment, the attribute setting module 1732 sets real-world attributes for the user 5 based on the behavior history of the user 5 in the real world, and the recommendation module 1731 recommends a specific thing in the metaverse to the user 5 based on the real-world attributes. However, the recommendation module 1731 may make a recommendation based on the behavior history without the attribute setting module 1732 setting the real-world attributes. Specifically, for example, when a place corresponding to a specific place in the real world exists in the metaverse (for example, a specific facility in virtual Shibuya that imitates a specific facility in real Shibuya), and the behavior history of the user 5 in the real world indicates that the specific place is frequently visited (in other words, when the behavior history itself indicates the attribute of the user 5 that the user frequently visits the specific place. In other words, when the number of times the specific place is used is high), the recommendation module 1731 may recommend to the user 5 a place in the metaverse that corresponds to the specific place.

Recommendations for specific things in the metaverse based on the behavioral history of user 5 in the real world may be as follows. That is, for example, the behavioral history may be a history of searches by user 5 using user device 700 described below (e.g., searches in a specific web browser, etc.), or a history of purchases of products, etc. (e.g., purchase history on a specific EC site, etc.). And, for example, when the behavioral history of user 5 in the real world indicates, for example, a search for music concerts or a purchase of an instrument on a specific EC site, the recommendation module 1731 may recommend a music concert in the metaverse.

The behavioral history may also be a history of credit card usage, etc. Then, the recommendation module 1731 may recommend a home appliance retailer in the metaverse, for example, when the history of credit card usage as the behavioral history of user 5 in the real world indicates that user 5 has purchased home appliances.

[Recommendations for real-world objects based on behavioral history in the metaverse]
The recommendation module 1731 may make recommendations regarding specific things in the metaverse based on the behavioral history of user 5 in the metaverse, or recommendations regarding specific things in the metaverse based on the behavioral history of user 5 in the real world, instead of or in addition to these recommendations, or recommendations regarding specific things in the real world based on the behavioral history of user 5 in the metaverse.

Recommendations of specific real-world objects to user 5 based on behavioral history in the metaverse may be performed, for example, as follows. That is, attributes in the virtual space are set for each user 5 by attribute setting module 1732, and recommendation module 1731 may make recommendations regarding specific real-world objects based on the attributes in the virtual space.

The recommendation module 1731, for example, recommends to the user 5 real-world things (e.g., places, services, objects, etc.) according to the virtual space attributes set to the user 5. Specifically, for example, among real-world things, things are prepared with recommended target attributes indicating which attribute the thing is recommended to, and the recommendation module 1731 may recommend to the user 5 things with recommended target attributes corresponding to the virtual space attributes set to the user 5. That is, for example, among real-world things, there are things with recommended target attributes such as "active", "otaku", "fashionable", "gourmet", and "inactive", and the thing may be recommended to the user 5 with a virtual space attribute that matches the recommended target attribute set to the thing. More specifically, for example, the recommendation module 1731 may recommend real-world services, facilities, etc. with a recommended target attribute of "active" to a user with a virtual space attribute of "active". Note that information indicating the recommended attributes of each real-world object may be stored in advance in, for example, the memory module 1630 of the server 600.

In addition, in the metaverse, there are multiple contents that are associated with real-world things (in other words, associated with them), and the recommendation module 1731 may recommend a thing associated with a specific content based on the user 5's access to a specific content among the multiple contents that are associated with a real-world thing. Note that information indicating the correspondence between real-world things and content in the metaverse may be stored in advance in the memory module 1630 of the server 600, for example. Here, the content associated with a real-world thing may be, for example, a place in the metaverse that is based on (for example, imitates) a place (for example, a region or facility) that actually exists in the real world. Specifically, for example, in a virtual town based on a specific real town, a virtual facility based on a specific real facility exists, and the recommendation module 1731 may recommend the specific facility to the user 5 based on the user 5's visit to the virtual facility in the metaverse.

Furthermore, content associated with real-world objects may be, for example, an event in the metaverse that is similar to an event that actually exists in the real world. Specifically, for example, if a music concert similar to a specific music concert held in the real world (e.g., a concert with a similar musical genre or a concert featuring the same artist) is held in the metaverse, recommendation module 1731 may recommend the specific music concert held in the real world to user 5 based on user 5's participation in the music concert in the metaverse (e.g., actual participation or reservation for participation, etc.).

Also, for example, if a service corresponding to a particular real-world service is available in the metaverse, recommendation module 1731 may recommend the particular real-world service to user 5 based on user 5's use of that service in the metaverse.

Note that real-world objects and each piece of content in the metaverse may correspond one-to-one, but they do not have to correspond one-to-one. In other words, multiple pieces of content in the metaverse may correspond to one object in the real world, and one piece of content in the metaverse may correspond to multiple objects in the real world. For example, there may be multiple casinos in the metaverse, and the multiple casinos may correspond to one casino in the real world. Also, there may be one casino in the metaverse, and the one casino may correspond to multiple casinos in the real world.

Recommendations for specific real-world objects based on the behavioral history of user 5 in the metaverse may be as follows. That is, for example, the behavioral history may be a history of shopping in the metaverse. Then, for example, when the behavioral history of user 5 in the metaverse indicates the purchase of a specific product that can be used in the metaverse (for example, clothing worn by an avatar or furniture to be placed in a house in the metaverse), the recommendation module 1731 may recommend a real-world product related to the specific product. More specifically, for example, the recommendation module 1731 may change the real-world product displayed as a product recommended to user 5 on the website of a real-world store associated with a specific store in accordance with a product purchased by user 5 at the specific store in the metaverse.

Furthermore, the recommendation module 1731 may recommend actions in the real world (e.g., recommended actions) based on the behavioral history of the user 5 in the metaverse. Specifically, the recommendation module 1731 may recommend exercising in the real world based on the fact that the user 5 has moved little in the metaverse (e.g., the distance moved is less than a threshold). The recommendation module 1731 may also recommend a review of the user's lifestyle in the real world based on the user's behavioral history in the metaverse. With this configuration, it is possible to provide useful advice for the user 5's life in the real world based on the characteristics of the user 5 that appear in the behavioral history in the metaverse.

In addition, the recommendation module 1731 may recommend to the user 5, for example, real-world things that have a specific relationship with other users who have a specific relationship with the user 5 in the metaverse. The real-world things that have a specific relationship with the other user 5 may be, for example, things in the real world that the other user 5 uses frequently (for example, facilities that are frequently visited or services that are frequently used). The real-world things that the other user 5 uses frequently may be determined based on the behavior history of the other user 5 in the real world (for example, from the number of times each facility or service is used as indicated by the behavior history). The real-world things that have a specific relationship with the other user 5 may be, for example, things in the real world that correspond to content in the metaverse that the other user 5 uses frequently. The other users 5 who have a specific relationship are as described above. According to this configuration, for example, when another user 5 who has a specific relationship in the metaverse (for example, frequently interacts with the other user 5) often participates in a specific live event in the metaverse, it is possible to recommend to the user 5 a real-world live event that corresponds to the specific live event. This makes it possible to extend relationships that exist within the metaverse to the real world.

In addition, in the metaverse, the user 5 may be able to visually know at least one of the attributes in the virtual space or the attributes in the real world of the user 5. In addition, in the metaverse, the user 5 may be able to visually know at least one of the attributes in the virtual space or the attributes in the real world of the other users 5. Specifically, for example, the avatar control module 1429 may reflect the attributes of the user 5 in the avatar object 6 and control the avatar object 6 to be displayed on the monitor 130 in a display mode in which the attributes are reflected. Here, the reflection of the attributes in the avatar object 6 may be a change of the skin (e.g., clothes) of the avatar object 6 according to the attributes. Also, the reflection of the attributes in the avatar object 6 may be a display (e.g., an icon) indicating the attributes added to the periphery (e.g., above the head) of the avatar object 6. In other words, the reflection of the attributes in the avatar object 6 may be a display mode in which an object (e.g., clothes or an icon, etc.) according to the attributes is added to the avatar object 6. Also, the attribute may be, for example, displayed (for example, indicated by characters, symbols, etc.) on a screen (so-called profile screen, etc.) that displays information about the user 5 in a list. Also, for example, when there is a gap (in other words, a specific difference) between the attributes in the virtual space set for a certain user 5 and the attributes in the real world, a display indicating that there is a gap may be made. Specifically, the display mode of the avatar object 6 may be changed to a display mode indicating that there is a gap (for example, a display mode in which an icon indicating that there is a gap is displayed above the head of the avatar object 6), or a display indicating that there is a gap may be made on the profile screen, etc. Note that each user 5 may be able to set whether or not to make the attributes or gaps, etc., visually noticeable to other users 5. Also, for example, when reflecting attributes to the avatar object 6, the reflection may be performed automatically or based on the operation of the user 5. For example, the recommendation module 1731 may recommend a skin (e.g., clothing) for the avatar object 6 according to the attributes of the user 5 (in other words, the behavioral history), and when the user 5 performs an operation to change to the recommended skin, the skin of the avatar object 6 may change to the recommended skin.

In this embodiment, the attributes of user 5 that are set based on the behavioral history in the metaverse (i.e., virtual space attributes) and the attributes of user 5 that are set based on the behavioral history in the real world (i.e., real world attributes) are managed separately. However, the attributes that are set based on the behavioral history in the metaverse and the attributes that are set based on the behavioral history in the real world do not have to be differentiated. In other words, the attributes in the virtual space and the attributes in the real world in this embodiment may both be read simply as "attributes".

The behavior history of the user 5 in the real world may be acquired, for example, as follows. That is, for example, the control module 1610 of the server 600 may include a behavior history acquisition module 1733. In addition, the behavior history acquisition module 1733 may acquire information about the behavior history of the user 5 in the real world from a device carried by the user 5 as the external device 700 (hereinafter referred to as the "user device 700"), and store the behavior history of the user 5 in the real world in the real world history storage unit 1753 provided in the memory module 1630 based on the information. Here, the device carried by the user 5 may be, for example, a smartphone, a feature phone, a PDA (Personal Digital Assistant), a tablet computer, a personal computer, or the like, or a device worn by the user 5 (for example, a wearable device such as a watch type, a wristband type, a ring type, a clothing type, a glasses type, or a contact lens type, or an implanted device), etc.

The behavioral history acquisition module 1733 may acquire information on the distance traveled by the user 5, information on places visited by the user 5, and information on services used by the user 5 as behavioral history based on location information indicating the location of the user 5 acquired by the user device 700 through GPS or a predetermined wireless communication (for example, short-range wireless communication such as Wi-Fi communication, Bluetooth communication, or UWB (Ultra Wide Band) communication). The behavioral history acquisition module 1733 may also acquire information on the actions of the user 5 on the SNS (for example, information on posted images, information on the date and time of posting, information indicating the content of the post, information on posts to which the user reacted, etc.) from the user device 700, and based on the information, acquire information on places visited by the user 5, information on services used by the user 5, and information on clothing worn by the user 5 as behavioral history. The behavioral history acquisition module 1733 may also acquire, for example, a history of searches on the user 5's web browser and a history of purchases of products, etc. from the user device 700 as behavioral history. In addition, the behavioral history acquisition module 1733 may acquire these histories as behavioral history from a specified server that stores history regarding the use of a specified application on the user device 700, a specified server that stores history regarding the use of the user 5's credit card, etc.

The behavioral history acquisition module 1733 may also acquire behavioral history based on information on biometric information acquired by the user device 700, for example. Here, the biometric information may be, for example, data such as heart rate, blood pressure, body temperature, blood oxygen content, exhaled air, sweat volume, number of steps, electrocardiogram, or brainwaves measured by a device worn by the user 5. The user device 700 or the behavioral history acquisition module 1733 may also acquire information obtained by analyzing the biometric information (hereinafter referred to as "analysis result information"). Here, the analysis result information may be, for example, information indicating that the user is exercising (or has exercised) or after exercising, information indicating the amount of sleep, or information indicating a full stomach, which is obtained by analyzing the biometric information. Then, the behavioral history acquisition module 1733 may acquire information on the number or frequency of exercises performed by the user 5, information on the calories consumed by the user 5, or information on the amount of sleep by the user 5 as behavioral history, based on the biometric information or branching result information.

The behavioral history acquisition module 1733 may acquire the behavioral history based on information manually input by the user 5 into the user device 700, etc. For example, the behavioral history may be acquired based on information input by the user 5 into a health care application of the user device 700, information input into a household accounting application, etc. In other words, the behavioral history may be acquired in real time in accordance with the behavior of the user 5, or may be acquired by the user 5 manually inputting specified information after performing the behavior.

The control module 1610 includes a cooperation management module 1741 that manages information regarding cooperation with the user device 700 of each user 5. The cooperation management module 1741 (in other words, cooperation information registration means) registers information regarding cooperation with the user device 700 used by the user 5 based on the operation of the user 5 (for example, an operation by the controller 300 or an operation on the user device 700, etc.). Here, the information regarding cooperation with the user device 700 may be information indicating the user device 700 used by the user 5 (for example, a wearable device, etc.). In other words, the information regarding cooperation with the user device 700 may be information indicating the user device 700 that the user 5 has permitted to cooperate. The information regarding cooperation with the user device 700 may also be information regarding cooperation between an application in the user device 700 (for example, an application for acquiring biometric information, an SNS application, etc.) and an application that provides a metaverse. In other words, the information regarding the cooperation with the user device 700 may be information indicating an application in the user device 700 that the user 5 has permitted to cooperate with (in other words, an application that can be used in the user device 700). That is, the information regarding the cooperation with the user device 700 may be information regarding permission to acquire information regarding the behavior history of the user 5 in the real world via the user device 700. The cooperation management module 1741 stores information regarding the cooperation with the user device 700 in the memory module 1630 based on the operation of the user 5. In addition, when the information regarding the cooperation with the user device 700 is registered by the cooperation management module 1741, the behavior history acquisition module 1733 can acquire the behavior history of the user 5 based on the information acquired by the user device 700. In other words, when the information regarding the cooperation with the user device 700 is registered, for example, an application providing a metaverse can acquire information from an application in the user device 700. In addition, the cooperation management module 1741 (in other words, the notification means) notifies the user 5, who has not registered information regarding cooperation with the user device 700, to prompt the user 5 to register information regarding cooperation with the user device 700. Specifically, for example, the cooperation management module 1741 notifies the user 5 that a predetermined recommendation will be made by permitting cooperation with the user device 700. More specifically, for example, the cooperation management module 1741 transmits information indicating that information regarding cooperation with the user device 700 has not been registered to the control module 510 of the computer 200 of the user 5. In addition, the control module 510 that has received the information causes the monitor 130 to display a display notifying the user 5 that cooperation with the user device 700 has not been made, or a display notifying the user 5 that cooperation with the user device 700 has been permitted, and that recommendations regarding predetermined things in the metaverse will be made based on the behavior history in the real world.

In addition, whether or not to allow the behavior history acquisition module 1733 to acquire the behavior history (in other words, whether or not to permit it) may be set based on the operation of the user 5 (in other words, it may be possible to switch between ON and OFF). For example, the behavior history acquisition module 1733 may determine whether or not to acquire the behavior history based on setting information (specifically, setting information on whether or not to acquire the behavior history) set by the operation of the user 5 (for example, the operation of the controller 300 on a predetermined setting screen). In addition, whether or not to acquire the behavior history may be set for each acquisition path of the behavior history. Specifically, for example, it may be possible to set such that while the acquisition of the behavior history from the user device 700 is permitted, the acquisition of the history related to the use of the credit card is not permitted. In other words, it may be possible to set for each user which of a plurality of media (for example, the user device 700, a credit card, etc.) the behavior history acquisition module 1733 is permitted to acquire. In addition, whether or not to allow the recommendation module 1731 to perform various recommendations based on various behavioral histories (in other words, whether or not to permit them) may be set (in other words, switchable between ON and OFF) based on the operation of the user 5. For example, the recommendation module 1731 may determine whether or not to perform a recommendation based on setting information (specifically, setting information on whether or not to perform a recommendation) set by the operation of the user 5 (for example, an operation by the controller 300 on a predetermined setting screen). In addition, whether or not to perform a recommendation may be set for each thing to be recommended. According to such a configuration, for example, in a configuration in which recommendations regarding things in the metaverse are made based on behavioral histories in the real world, it is possible to switch ON/OFF of the recommendation regarding things in the metaverse, and it is possible to prevent actions in the real world from being revealed by the recommended things.

The display provided to user 5 when recommendation module 1731 makes various recommendations may be, for example, as follows. That is, for example, when recommendation module 1731 determines an object in the metaverse or in the real world to be recommended to user 5 based on user 5's behavioral history in the metaverse or in the real world, it outputs recommendation information indicating the object and transmits it to recommendation information presentation module 1721. In addition, recommendation information presentation module 1721 displays a display (hereinafter referred to as "recommendation display 30") recommending the object on monitor 130 based on the recommendation information from recommendation module 1731.

An example of the recommendation display 30 is shown in FIG. 17. FIG. 17 shows a display example in the case where content and other users 5 in the metaverse are recommended based on the behavior history in the real world. As shown in FIG. 17, the recommendation information presentation module 1721 may display the recommendation display 30 including a display of the name of the recommended content on the monitor 130. Also, as shown in FIG. 17, the recommendation information presentation module 1721 may display the recommendation display 30 including a display of the name of the other user 5 in the metaverse to be recommended (in other words, the name of the avatar of the other user 5), in other words, the identification information of the other user 5 (e.g., the user name), on the monitor 130. The recommendation display 30 related to the recommendation of the other user 5 may include, for example, a display related to the reception of a contact with the other user 5, a display indicating the location of the other user in the metaverse, etc. Also, the recommendation display recommending content in the metaverse may include, for example, a display indicating the location of the location related to the content (e.g., the location of a facility as the content, or the location of a place where the service as the content can be used, etc.). The recommendation display 30 when recommending content or other users in the metaverse based on a behavioral history in the metaverse may be as illustrated in FIG. 17. The recommendation display 30 may be displayed over the entire display area of the monitor 130, or may be displayed in a portion of the display area.

Another example of a recommendation display is shown in FIG. 18. FIG. 18 shows a display example when recommending real-world objects based on behavioral history in the metaverse. Note that the recommendation display 30 when recommending content or other users in the metaverse based on behavioral history in the metaverse or behavioral history in the real world may also be as shown in FIG. 18.

18, the recommendation display 30 may include a display of the name of the recommended thing. The recommendation display 30 may also include a display explaining the recommended thing (e.g., a display of an explanatory text, etc.). The recommendation display 30 may also include a display regarding the price of the recommended thing (e.g., the price of the recommended thing or the price of the recommended service, etc.). The recommendation display 30 may also include a display indicating the location of the place related to the recommended thing. Here, the display indicating the location may be, for example, a display using characters such as an address, or a display using a map, etc. The recommendation display 30 may also include a display related to the reception of a reservation for the recommended thing. In other words, when the recommendation display 30 is displayed, an operation related to the reservation of the recommended thing by the user 5 (e.g., an operation using the controller 300 or an operation using gaze, etc.) may be accepted. The recommendation display 30 may also include a display related to the reception of an operation to set the place related to the recommended thing as a destination to be actually headed to in the real world. In other words, in a state where the recommendation display 30 is displayed, an operation by the user 5 to set a place related to the recommended thing as a destination to be actually headed to in the real world (for example, an operation by the controller 300 or an operation by gaze, etc.) may be accepted. Furthermore, the recommendation display 30 may include an indication related to the reception of addition of the recommended thing to a predetermined list. In other words, in a state where the recommendation display 30 is displayed, an operation by the user 5 to add the recommended thing to a predetermined list (for example, an operation by the controller 300 or an operation by gaze, etc.) may be accepted. Here, the predetermined list may be, for example, a list for registering candidates for places to be visited in the future, a list for registering a place to be headed to now, or a list for registering items to be purchased. Furthermore, here, the predetermined list may be one that can be viewed using a predetermined application in the user device 700. Furthermore, when an operation to set a place related to the recommended thing as a destination to be actually headed to in the real world is performed in a state where the recommendation display 30 is displayed, the place may be set as a destination in a navigation application of the user device 700. These various settings can be implemented using known technologies, such as technologies that link applications for accessing the metaverse with other applications and websites.

In addition, when the recommendation module 1731 determines a thing in the metaverse or the real world to be recommended to the user 5 based on the behavior history of the user 5 in the metaverse or the real world, it may output recommendation information indicating the thing and transmit it to the user device 700. Then, the computer of the user device 700 may display a recommendation display 30 recommending the thing on the monitor of the user device 700 based on the recommendation information from the recommendation module 1731. In other words, information regarding the thing in the real world recommended to the user 5 by the recommendation module 1731 may be presented to the user 5 on the user device 700 (e.g., a smartphone or a wearable device, etc.), or may be presented to the user 5 in the metaverse. In addition, when the recommendation information is sent to the user device 700, the recommendation information may be registered in a specified application of the user device 700 by performing a specified operation on the user device 700. Specifically, for example, when recommendation information is sent, the recommendation display 30 is displayed on the user device 700, and an operation related to a reservation for the recommended thing, an operation to set a place related to the recommended thing as a destination to actually go to in the real world, or an operation related to adding the recommended thing to a predetermined list is accepted, and information related to the recommendation may be registered in an application (e.g., a calendar application) that manages the date and time of the reservation or the date and time to go to the destination, an application that manages the predetermined list, a navigation application, or the like based on each operation. In addition, when recommendation information recommending a predetermined thing in the real world is sent to the user device 700, the user device 700 may store information related to the recommendation, and when the user 5 approaches the predetermined thing (in other words, when the user 5 is located within a predetermined range from the predetermined thing), may give a predetermined notification to the user 5. Here, the predetermined notification may be, for example, a notification that notifies the user that the predetermined thing has been approached, a notification that the user has arrived, or a notification that notifies the user of detailed information about the predetermined thing. Whether or not the user 5 has approached the specified thing may be determined based on, for example, location information indicating the location of the user 5 acquired by the user device 700 using a GPS or the like. In addition, when the user 5 actually visits a place related to the recommended thing, the user device 700 may detect the visit and transmit information notifying the visit to the server 600. Then, the control module 1610 may grant a specified reward (for example, a reward that can be used in the metaverse or a reward that can be used in the real world) to the user 5 based on the information (in other words, based on the user 5 having taken an action in response to the recommendation).

The timing of making a recommendation to user 5 is not particularly limited, but can be, for example, as follows. That is, the recommendation may be made when user 5 performs an operation requesting a recommendation (e.g., an operation requesting the display of recommendation display 30) on a menu screen (in other words, a user interface displayed on monitor 130) on which multiple menu items are displayed. Note that the timing of making a recommendation here means the timing when information related to the recommendation is provided to user 5 (e.g., the timing when recommendation display 30 is displayed to user 5), but can also mean the timing when recommendation module 1731 decides on the thing to be recommended.

Recommendations may also be made when the behavioral history of user 5 is accumulated and an item to be recommended to user 5 is identified (in other words, when the amount of behavioral history that allows recommendation module 1731 to make a recommendation is accumulated), etc. Specifically, recommendations may be made each time the behavioral history of user 5 is accumulated and an item to be recommended to user 5 is newly extracted.

The recommendation may be made when the user 5 accesses the metaverse. That is, for example, the recommendation may be made when the user 5 wears the HMD 120 and starts an application for accessing the metaverse. Specifically, for example, the recommendation may be made after the application for accessing the metaverse is started and before the user 5 can operate the avatar object 6. As an example, the recommendation may be made on a screen (for example, a so-called home screen) on which settings related to the metaverse space are made. According to such a configuration, for example, the following effects can be obtained when making recommendations regarding things in the metaverse based on the behavior history of the user 5 in the real world. That is, when the user 5 accesses the metaverse for the first time in a long time, the user 5 is shown in a way that makes it clear that the actions he or she took in the real world will be utilized in the metaverse space, so that the user 5 can feel that he or she is involved in the metaverse even during periods when he or she is not active in the metaverse, and a psychological barrier to re-accessing the metaverse can be removed. When making recommendations regarding things in the metaverse based on the behavior history of the user 5 in the real world, the recommendation may be made when the metaverse is accessed for the first time. In this case, for example, the recommendation may be made after the user 5 has been given some explanation about the operation method (in other words, during or after the tutorial). With this configuration, it is possible to present what the user 5 should do first when starting activities in the metaverse, in accordance with the characteristics of the user 5.

The recommendation may be made at the timing when the user 5 accesses a specific content in the metaverse. For example, in the case of recommending a real-world thing corresponding to a specific content in the metaverse, or in the case of recommending a thing in the metaverse corresponding to a specific content in the metaverse, the recommendation may be made at the timing when the user 5 accesses the specific content. For example, as shown in FIG. 18, in a virtual town that is based on a specific real-world town, a virtual facility based on a specific real-world facility exists, and when the user 5 visits the virtual facility in the metaverse (specifically, for example, when the user visits a place where the virtual facility is in view or when the user enters the virtual facility), the recommendation module 1731 may recommend the specific real-world facility to the user 5. In addition, when making a recommendation to the user 5 by the display shown in FIG. 18, the recommendation may be, for example, as follows. That is, the recommendation module 1731 and/or the recommendation information presentation module 1721 may vary the thing recommended to the user 5 based on where the user 5 is in the metaverse. The recommendation module 1731 and/or the recommendation information presentation module 1721 may vary the things recommended to the user 5 based on where the user 5 is looking in the metaverse. That is, for example, when the user 5 is in a virtual town based on a specific real town, the recommendation information presentation module 1721 may display on the monitor 130 a recommendation display 30 that recommends a real facility corresponding to a virtual facility in the virtual town. In other words, the recommendation module 1731 may recommend a specific thing in the real world or in the metaverse based on the current position of the user 5 in the metaverse (in other words, a specific thing according to the current position). Also, the recommendation information presentation module 1721 may display on the monitor 130 a recommendation display 30 that recommends a real facility corresponding to the first virtual facility 31, for example, when the user 5 is looking at a first virtual facility 31. In addition, the recommendation information presentation module 1721 may display, for example, a recommendation display 30 on the monitor 130 that recommends a real facility corresponding to the second virtual facility 32 when the user 5 is looking at the second virtual facility 32. In other words, the recommendation module 1731 may recommend a specific thing in the real world or the metaverse (in other words, a specific thing according to the location where the user 5 is looking) based on the location where the user 5 is looking in the metaverse. Note that the location where the user 5 is looking (in other words, which facility the user 5 is looking at, etc.) may be determined, for example, based on the field of view image 17, or may be determined based on the line of sight of the user 5 identified based on a signal from the gaze sensor 140. Specifically, for example, the range shown in the field of view image 17 may be determined as the location where the user 5 is looking, or a specific range based on the point where the user 5's line of sight is directed may be determined as the location where the user 5 is looking.

The recommendation may also be made when the user 5 exits the metaverse. That is, for example, the recommendation may be made when the user 5 performs an operation to log out of the metaverse (e.g., an operation by the controller 300).

In addition, the control module 1610 of this embodiment includes an access control module 1734 that controls whether or not access is permitted for a specific content in the metaverse. When the recommendation module 1731 recommends a specific content to the user 5, the access control module 1734 enables the user 5 to access the specific content. Specifically, for example, there may be a place (e.g., a region or a facility) in the metaverse that the user 5 cannot enter unless it is recommended. In this case, the access control module 1734 may enable the user 5 to enter (i.e., access) the place based on the recommendation of the place to the user 5 by the recommendation module 1731. In addition, for example, there may be a service in the metaverse that the user 5 cannot use unless it is recommended. In this case, the access control module 1734 may enable the user 5 to use (i.e., access) the service based on the recommendation of the service to the user 5 by the recommendation module 1731. In addition, for example, there may be an item in the metaverse that the user 5 cannot obtain (e.g., purchase) unless it is recommended. In this case, the access control module 1734 may, for example, enable the user 5 to acquire (i.e., access) the item based on the recommendation of the item to the user 5 by the recommendation module 1731. In this way, by enabling access to the recommended thing based on the recommendation, it is possible to increase motivation and a sense of purpose for activities in the metaverse or in the real world.

In addition, the spaces to which access is controlled by the access control module 1734 may include spaces that can only be accessed by users 5 with specific attributes. In other words, the access control module 1734 may permit access to a specific space in the metaverse if the user 5 has a specific attribute. With this configuration, a space where similar users 5 gather can be prepared in the metaverse.

Next, the flow of processing executed by the HMD system 100 will be explained with reference to Figures 19 to 22.

[Processing related to recommendations regarding things in the metaverse based on behavioral history in the metaverse]
An example of a process for making recommendations regarding things in the metaverse based on a behavior history in the metaverse will be described with reference to Fig. 19 and Fig. 20. Note that, here, a case where a recommendation is made to a user 5A will be described as an example.

First, an example of a process for recommending other users based on their behavioral history in the metaverse will be described with reference to FIG. 19.

In step S101, the attribute setting module 1732 determines the virtual space attributes of user 5A based on the behavioral history of user 5A in the metaverse stored in the virtual space history storage unit 1751.

Next, in step S102, the recommendation module 1731 determines other users 5 to be recommended to the user 5A based on the attributes in the virtual space of the user 5A. Specifically, the recommendation module 1731 extracts other users 5 having attributes in the virtual space corresponding to the attributes in the virtual space of the user 5A from among the multiple users 5 using the metaverse, and determines them as other users 5 to be recommended to the user 5A. Here, as an example, it is assumed that the user 5C is determined as the other user 5 to be recommended to the user 5A. Note that the recommendation module 1731 may preferentially extract other users 5 with high relevance of attributes (e.g., users 5 with a large number of corresponding attributes, etc.). In addition, the recommendation module 1731 may preferentially extract other users 5 with high relevance to the location of the user 5 in the metaverse indicated by the behavior history in the metaverse (e.g., other users 5 who are currently located nearby, other users 5 who have a similar range of behavior, other users 5 who often visit the same place, etc.). Furthermore, the recommendation module 1731 may preferentially extract other users 5 who are highly relevant to the location of the user 5 in the real world as indicated by the real-world behavior history (for example, other users 5 who are currently in a nearby location, other users 5 who have a similar range of behavior, other users 5 who often visit the same location, etc.).

Next, in step S103, the recommendation module 1731 transmits recommendation information about the other user 5C to be recommended to the user 5A to the recommendation information presentation module 1721A. In other words, the recommendation module 1731 outputs recommendation information for displaying a recommendation display 30 that recommends the other user 5C to the user 5A.

Next, in step S104, the recommendation information presentation module 1721A causes the monitor 130A to display a recommendation display 30 recommending another user 5C to the user 5A based on the recommendation information transmitted from the recommendation module 1731.

Next, an example of a process for recommending content within the metaverse based on behavioral history within the metaverse will be described with reference to FIG. 20.

In step S151, the attribute setting module 1732 determines the virtual space attributes of user 5A based on the behavioral history of user 5A in the metaverse stored in the virtual space history storage unit 1751.

Next, in step S152, the recommendation module 1731 determines the content in the metaverse to be recommended to the user 5A based on the attributes in the virtual space of the user 5A. Specifically, the recommendation module 1731 extracts content having a recommendation target attribute corresponding to the attributes in the virtual space of the user 5A from among a plurality of contents in the metaverse, and determines it as the content to be recommended to the user 5A. The recommendation module 1731 may preferentially extract content that is highly relevant to the location of the user 5A in the metaverse indicated by the behavior history in the metaverse (e.g., content close to the current location, content that exists within the behavior range of the user 5A, etc.). The recommendation module 1731 may also preferentially extract content that is highly relevant to the location of the user 5A in the real world indicated by the behavior history in the real world (e.g., content corresponding to a real-world location close to the current location, content corresponding to a real-world location that exists within the behavior range of the user 5A, etc.).

Next, in step S153, the recommendation module 1731 transmits recommendation information regarding the content to be recommended to the user 5A to the recommendation information presentation module 1721A. In other words, the recommendation module 1731 outputs recommendation information for displaying a recommendation display 30 that recommends a specific content to the user 5A.

Next, in step S154, the recommendation information presentation module 1721A causes the monitor 130A to display a recommendation display 30 that recommends a specific content to the user 5A based on the recommendation information transmitted from the recommendation module 1731.

[Processing related to recommendations regarding things in the metaverse based on behavioral history in the real world]
An example of a process for making recommendations regarding things in the metaverse based on a behavior history in the real world will be described with reference to Fig. 21. Note that, here, a case where a recommendation is made to a user 5A will be described as an example.

In step S201, the behavior history acquisition module 1733 acquires the behavior history of the user 5A in the real world based on information about the user 5A's behavior in the real world. Here, the information about the user 5A's behavior in the real world may be, for example, biometric information acquired by the user device 700 or analysis result information obtained by analyzing the biometric information. The information about the user 5A's behavior in the real world may be, for example, information about the user 5's actions in the SNS. The information about the user 5A's behavior in the real world may be, for example, location information indicating the location of the user 5A in the real world. Such information about the user 5A's behavior in the real world is acquired by, for example, the user device 700 and sent to the control module 1610. Note that information about the user 5's actions in the SNS may be sent to the control module 1610 from a server that provides the SNS. Note that actions in the SNS include posting on the SNS and reacting (so-called likes, etc.) to posts made by others.

Next, in step S202, the attribute setting module 1732 determines the real-world attributes of user 5A based on user 5A's behavioral history in the real world.

Next, in step S203, the recommendation module 1731 determines things in the metaverse to be recommended to the user 5A based on the real-world attributes of the user 5A. Specifically, the recommendation module 1731 extracts content having recommendation target attributes corresponding to the real-world attributes of the user 5A from among a plurality of contents in the metaverse, and determines them as content to be recommended to the user 5A. The recommendation module 1731 may preferentially extract content that is highly relevant to the location of the user 5A in the real world indicated by the action history in the real world (e.g., content corresponding to a real-world location close to the current location, content corresponding to a real-world location within the action range of the user 5A, etc.). The recommendation module 1731 may also preferentially extract content that is highly relevant to the location of the user 5A in the metaverse indicated by the action history in the metaverse (e.g., content close to the current location, content within the action range of the user 5A, etc.).

Next, in step S204, the recommendation module 1731 transmits recommendation information regarding an object (e.g., content) to be recommended to the user 5A to the recommendation information presentation module 1721A. In other words, the recommendation module 1731 outputs recommendation information for displaying a recommendation display 30 that recommends a specific object in the metaverse to the user 5A.

Next, in step S205, the recommendation information presentation module 1721A causes the monitor 130A to display a recommendation display 30 that recommends a specific thing (e.g., a specific content) to the user 5A based on the recommendation information transmitted from the recommendation module 1731.

[Processing related to recommendations about real-world objects based on behavioral history in the metaverse]
An example of a process for making recommendations regarding real-world objects based on a behavior history in the metaverse will be described with reference to Fig. 22. Note that, here, a case where a recommendation is made to a user 5A will be described as an example.

In step S301, the recommendation module 1731 identifies a real-world thing corresponding to the content in the metaverse accessed by the user 5A. Then, the recommendation module 1731 determines the identified thing as a thing to be recommended to the user 5A. Specifically, the recommendation module 1731 identifies the content accessed by the user 5A based on the behavior history of the user 5A, and determines the real-world thing corresponding to the content accessed by the user 5A based on the information indicating the correspondence between the real-world thing and the content in the metaverse stored in the memory module 1630. Here, as an example, it is assumed that a specific facility in the real world is determined as a thing to be recommended to the user 5A based on the user 5A's access to a virtual facility based on a specific facility in the real world. Note that the recommendation module 1731 may determine the specific facility as a thing to be recommended, for example, at the timing when the user 5A accesses the virtual facility in the metaverse. Furthermore, the recommendation module 1731 may, for example, determine as the thing to be recommended, among multiple pieces of content that the user 5A has accessed (specifically, multiple pieces of content to which corresponding real-world things are set), a real-world thing that corresponds to a piece of content that the user 5A has used frequently (for example, the total number of times that the content has been used is equal to or exceeds a predetermined threshold, or the number of times that the content has been used within a predetermined period is equal to or exceeds a predetermined threshold (i.e., the frequency of use is high)) at the timing of displaying the recommendation display 30 to the user 5A.

Next, in step S302, the recommendation module 1731 transmits recommendation information related to a specific facility in the real world recommended to the user 5A to the recommendation information presentation module 1721A. In other words, the recommendation module 1731 outputs recommendation information for displaying a recommendation display 30 recommending a specific facility in the real world to the user 5A. Note that the recommendation module 1731 may transmit recommendation information related to real-world objects recommended to the user 5A to the user device 700 of the user 5A.

Next, in step S303, the recommendation information presentation module 1721A causes the monitor 130A to display a recommendation display 30 that recommends a specific facility in the real world to the user 5A based on the recommendation information transmitted from the recommendation module 1731.

[Environment settings in the metaverse]
In this embodiment, the HMD system 100 sets the environment in the metaverse based on information about the user 5. This point will be described below.

As shown in FIG. 15, the HMD system 100 has a user information acquisition module 1736 that acquires information related to the user 5 (hereinafter referred to as "user-related information"). The user information acquisition module 1736 acquires the behavior history of the user 5 in the metaverse as user-related information. The behavior history may be information indicating where the user 5 has gone, information indicating the games the user 5 has played, information indicating the contents of the conversations in the voice chat or text chat of the user 5, and the like. The user information acquisition module 1736 also acquires information such as the age, sex, and language used (e.g., Japanese, English, Chinese, etc.) of the user (in other words, the avatar) input by the user 5 as user-related information. The user information acquisition module 1736 may also acquire information (e.g., IP address, etc.) related to the access point used by the user 5 to access the server 600 as user-related information. The user-related information may also include the above-mentioned attributes in the virtual space. The user-related information may also include the behavior history of the user 5 in the real world, attributes in the real world, and the like. In other words, the user information acquisition module 1736 may include the behavioral history acquisition module 1733. The user-related information may also include information related to the user's hobbies and preferences. The information related to the user's hobbies and preferences may be input by the user 5 himself (for example, input by operating the controller 300, etc.), or may be acquired by the control module 1610 analyzing the behavioral history of the user 5 in the metaverse and the behavioral history in the real world. The user information acquisition module 1736 stores the acquired user-related information in the memory module 1630, which serves as a user-related information storage means.

The recommendation module 1731 makes recommendations regarding specific things in the metaverse based on the user-related information acquired by the user information acquisition module 1736. Specifically, the recommendation module 1731 makes recommendations regarding environments in the metaverse to the user 5 based on the user-related information about multiple users 5 (in other words, at least two or more) acquired by the user information acquisition module 1736.

Here, recommendations regarding the environment in the metaverse may be, for example, recommendations regarding background music (in other words, background music played in the metaverse), background, brightness, etc.

Recommendations regarding the environment in the metaverse may be performed, for example, as follows. That is, for example, when the recommendation module 1731 determines that a specific BGM is to be recommended to the user 5, it changes the BGM output from the speaker 180 of the HMD set 110 of the user 5 to the specific BGM. In other words, the recommendation module 1731 transmits information related to the output of the specific BGM from the speaker 180 to the control module 510 of the HMD set 110 of the user 5. Then, the control module 510 outputs the specific BGM to the speaker 180 based on the information. Note that the information may be sound data of the specific BGM, or may be information that enables the specific BGM to be identified, etc.

For example, when the recommendation module 1731 determines that a specific background is to be recommended to the user 5, the recommendation module 1731 changes the background displayed on the monitor 130 of the HMD set 110 of the user 5 to the specific background. In other words, the recommendation module 1731 transmits information for changing the background displayed on the monitor 130 to the specific background to the control module 510 of the HMD set 110 of the user 5. The control module 510 then sets the background to the specific background based on the information. Note that changing the background here may be, for example, changing the color of the sky in the metaverse (in other words, the weather), the exterior of a building, the interior of a room, or the like. Changing the background may be, for example, changing the color of the penlights of the surrounding audience at a live concert venue, or the like.

For example, when the recommendation module 1731 determines that a specific brightness is the brightness to be recommended to the user 5, it changes the display brightness of the monitor 130 of the HMD set 110 of the user 5 to the specific brightness. In other words, the recommendation module 1731 transmits information for setting the display brightness of the monitor 130 to the specific brightness to the control module 510 of the HMD set 110 of the user 5. Then, the control module sets the display brightness of the monitor 130 to the specific brightness based on the information. Note that changing the display brightness here may mean, for example, making a predetermined change to the lighting of buildings and rooms in the metaverse or the sun.

In addition, when the recommendation module 1731 changes the environment in the metaverse of the user 5 to a specific BGM, a specific background, or a specific brightness, etc., the environment may be changed through the selection (in other words, operation) of the user 5, or the environment may be changed without the need for the selection of the user 5. Specifically, for example, when the recommendation module 1731 determines the recommended BGM, background, brightness, etc., it transmits information related to the recommended BGM, background, brightness, etc. to the control module 510 of the user 5, and the control module 510 may automatically output the BGM according to the recommendation to the speaker 180 without the operation of the user 5, or execute display on the monitor 130 with the background and brightness according to the recommendation, based on the information. Alternatively, for example, when the recommendation module 1731 determines the recommended BGM, background, brightness, etc., it may transmit an instruction to the control module 510 to display a display prompting the user to select whether or not to change the environment to the recommended BGM, background, brightness, etc. In a state where the control module 510 is displaying a display on the monitor 130 prompting the user to make the selection based on the instruction, when an operation (for example, an operation by the controller 300) is performed to select changing the environment, the environment may change to the recommended content, and when an operation is performed to select not to change the environment, the environment may not change to the recommended content. That is, in this embodiment, the recommendation regarding the environment does not only include notifying the user 5 of the recommended BGM, background, brightness, etc. by text, etc., but also includes automatically changing the environment of the user 5 to the recommended BGM, background, brightness, etc. In other words, in this embodiment, the recommendation module 1731 changes the environment in the metaverse based on the user-related information, but the change may occur through the selection of the user 5 or may occur without the selection of the user 5. In other words, the recommendation module 1731 makes a recommendation regarding the environment based on the user-related information, but this can also be rephrased as setting the environment based on the user-related information.

In addition, when the recommendation module 1731 changes the environment in the metaverse based on the user-related information, the control module 510 may display a display related to the return of the environment to a state before the change on the monitor 130, as shown in FIG. 23. In other words, after the recommendation module 1731 changes the environment in the metaverse, the control module 510 may accept an operation (e.g., an operation by the controller 300) to return the environment (specifically, for example, BGM, background, or brightness) to a state before the change. Then, the recommendation module 1731 may return the environment to a state before the change based on the operation by the user 5. In addition, when the recommendation module 1731 changes the environment in the metaverse based on the user-related information, the control module 510 may display a display related to the adjustment of settings related to the environment on the monitor 130, as shown in FIG. 23. In other words, after the recommendation module 1731 changes the environment in the metaverse, the control module 510 may accept an operation (e.g., an operation by the controller 300) to adjust the settings of the environment (specifically, for example, brightness). Then, the environmental settings may change based on the operation by user 5.

In the following, an example will be described in which the recommendation module 1731 (hereinafter also referred to as the "environment setting module 1731") changes the BGM as a change in the environment in the metaverse based on user-related information about multiple users 5. In addition, in the following, the environment setting module 1731 will be described as automatically changing the BGM of user 5 without the operation of user 5 when it has determined the BGM to be recommended to user 5. Note that "BGM" in the following description may be read as "background" or "brightness", etc. Also, the environment setting module 1731 may change one of "BGM", "background", "brightness", etc., or may change multiple of them.

The environment setting module 1731 analyzes user-related information (e.g., the age, gender, behavioral history, etc. of each user 5) of the multiple users 5 to be analyzed (hereinafter also referred to as "target users") and calculates features. The environment setting module 1731 then compares the calculated features with features previously set for each BGM, and determines, from among the multiple BGM, the BGM with features similar to the calculated features as the BGM to be recommended to the user 5.

The environment setting module 1731 makes recommendations regarding the environment based on user-related information of multiple users 5 in a specific area (hereinafter referred to as the "target area") in the metaverse. Specifically, the environment setting module 1731 makes settings regarding the environment of all users 5 in the target area based on the user-related information of the users 5. In other words, in this embodiment, all users 5 in the target area are target users as analysis targets for BGM recommendations. The target users may be all users 5 in the target area, users 5 who have a predetermined attribute among all users 5 in the target area, or multiple users 5 randomly extracted from all users 5 in the target area. Here, the predetermined attribute may be the above-mentioned attribute in the virtual space or attribute in the real world. The predetermined attribute may also be an attribute related to the age, gender, etc. of the user 5.

The target area may be, for example, a specific building or a specific room in the metaverse. Specifically, it may be, for example, a specific live venue, a sports viewing facility, a party venue, or a store. The target area may also be a specific town in the metaverse. The target area may also be, for example, a specific range centered on the user 5 to whom environmental recommendations are made. In the following, as shown in FIG. 24, the target area will be described as including multiple spaces including a first space and a second space.

For example, if at least some of all target users in the first space are talking about classical music in voice chat or text chat, the environment setting module 1731 may change the background music of all target users in the first space (in other words, the background music output from the speaker 180 of each target user) to classical music. In other words, if the user-related information of at least two or more users 5 in the first space indicates that they are talking about a specific type of music (e.g., a specific genre (classical, rock, jazz, pop, etc.), a specific artist, a specific song, etc.), the environment setting module 1731 may set the background music of multiple users 5 in the first space to the specific type of music.

Specifically, for example, assume that there are three users, user 5A, user 5B, and user 5C, in the first space, user 5A and user 5B are having a conversation about classical music, and user 5C is not participating in the conversation. At this time, the environment setting module 1731 analyzes the user-related information of user 5A, user 5B, and user 5C. Then, based on the fact that user 5A and user 5B are having a conversation about classical music, the environment setting module 1731 determines that the BGM suitable for the first space is classical music, and determines the music to be recommended to user 5 in the first space to be classical music. Then, the environment setting module 1731 changes the BGM of all target users in the first space to classical music. That is, the environment setting module 1731 may change the environment in the metaverse of multiple users 5 (specifically, all target users in the target area) based on the history of conversations of at least two or more users 5 (specifically, all target users in the target area).

In addition, for example, if the result of analyzing the user-related information of at least two or more users 5 in the first space indicates that there are many users 5 in the first space who prefer a particular type of music (e.g., a particular genre, a particular artist, a particular song, etc.) (in other words, for example, if the number of users 5 who prefer the particular type of music is equal to or greater than a predetermined threshold (specifically, for example, if the proportion of users 5 who prefer the particular type of music is equal to or greater than a predetermined proportion)), the environment setting module 1731 may set the background music for the multiple users 5 in the first space to the particular type of music.

Specifically, for example, assume that there are three users, user 5A, user 5B, and user 5C, in the first space, and user 5A and user 5B like music by a specific artist, and user 5C likes music by another artist. At this time, the environment setting module 1731 analyzes the user-related information of user 5A, user 5B, and user 5C. Then, based on the fact that there is a high proportion of users 5 in the first space who like the music of the specific artist, the environment setting module 1731 determines that the BGM suitable for the first space is the music of the specific artist, and determines the music to be recommended to user 5 in the first space to be the music of the specific artist. Then, the environment setting module 1731 changes the BGM of all target users in the first space to the music of the specific artist. That is, the environment setting module 1731 may change the environment in the metaverse of multiple users 5 (specifically, all target users in the target area) based on the hobbies and preferences of at least two or more users 5 (specifically, all target users in the target area). As mentioned above, the music preferences of each user 5 (in other words, hobbies and preferences) may be input by the user himself/herself as profile information or the like as user-related information, or may be determined based on the user 5's behavioral history in the metaverse or in the real world.

Also, for example, if the proportion of women in their twenties is high when all target users in the first space are classified by age and gender, the environment setting module 1731 may change the background music of all target users in the first space to music preferred by women in their twenties. In other words, if the user-related information of at least two or more users 5 in the first space indicates that there are many users 5 of a specific gender or age (e.g., age group) (in other words, for example, if the number of users 5 of the specific gender or age is equal to or greater than a predetermined threshold (specifically, for example, if the proportion of users 5 of the specific gender or age is equal to or greater than a predetermined proportion)), the environment setting module 1731 may set the background music of all target users in the first space to music preferred by users 5 of the specific age or gender.

Specifically, for example, assume that there are three users, user 5A, user 5B, and user 5C, in the first space, user 5A and user 5B are women in their 20s, and user 5C is a man in his 50s. At this time, the environment setting module 1731 analyzes the user-related information of user 5A, user 5B, and user 5C. Then, when all target users in the first space are classified by age and gender, the environment setting module 1731 determines that the BGM suitable for the first space is music preferred by women in their 20s based on the high proportion of women in their 20s, and determines the music to be recommended to user 5 in the first space as music preferred by women in their 20s. Then, the environment setting module 1731 changes the BGM of all target users in the first space to music preferred by women in their 20s. That is, the environment setting module 1731 may change the environment in the metaverse of multiple users 5 (specifically, all target users in the target area) based on the age and gender of at least two or more users 5 (specifically, all target users in the target area).

The environment setting module 1731 may change the BGM of users other than the target user to the same BGM as the target user. Specifically, for example, when the user-related information is analyzed by analyzing only female users among all users 5 in the target area (in other words, when the target users are only female users), the BGM may be changed to the BGM recommended as a result of the analysis not only for female users but also for male users in the target area. When the user-related information is analyzed by analyzing only female users among all users 5 in the target area, the BGM may be changed to the BGM recommended as a result of the analysis only for female users in the target area. Then, the user-related information may be separately analyzed by analyzing only male users among all users 5 in the target area, and the BGM may be changed to the BGM recommended as a result of the analysis only for male users in the target area.

As described above, the environment setting module 1731 may change the background or brightness instead of or in addition to changing the BGM based on the user-related information of the multiple users 5. For example, when at least a part of all the target users in the first space are complaining in voice chat or text chat, the environment setting module 1731 may change the background or brightness of all the target users in the first space to a darker one that matches the mood. Conversely, the environment setting module 1731 may change the background or brightness of all the target users in the first space to a brighter one to encourage a change of topic. In other words, the environment setting module 1731 may set the environment in the metaverse of the multiple users 5 in the first space (specifically, all the target users in the target area) to an environment suitable for the content of the conversation in the first space based on the content of the conversation of at least two or more users 5 in the first space (specifically, all the target users in the target area).

In this way, the environment setting module 1731 sets predetermined settings for the environment in the metaverse of multiple users 5 to the same settings based on user-related information for at least two or more users 5. Specifically, the environment setting module 1731 sets the BGM, background, brightness, etc. to the same BGM, background, brightness, etc. between multiple users 5 (e.g., all target users in the target area). In other words, the environment setting module 1731 makes similar changes to the environment in the metaverse of multiple users 5. This provides a similar environment to multiple users 5, and experiences are shared among the multiple users 5.

For the second space, the environment setting module 1731 changes the environment in the metaverse of multiple users 5 in the second space based on the user-related information of the multiple users 5 in the second space. The change in the environment can be made in the same way as in the first space, so a description thereof will be omitted.

The trigger for the environment setting module 1731 to analyze the user-related information of the target user and determine the BGM of the target user is not particularly limited, but may be, for example, as follows. That is, for example, when the number of users 5 in the target area becomes equal to or greater than a predetermined threshold, the environment setting module 1731 may analyze the user-related information of the target user in the target area and determine the BGM of the target user. In addition, after analyzing the user-related information of the target user in the target area and determining the BGM of the target user to be a specific BGM (in other words, when the specific BGM is being output from the speaker 180 of the target user), if another user 5 enters the target area, the environment setting module 1731 may change the BGM of the other user 5 to the specific BGM, and may reanalyze the user-related information of the target user in the target area (in other words, multiple users 5 including the other user 5) and re-determine the BGM of the target user at the timing when the other user 5 enters.

Furthermore, when the environment setting module 1731 determines that the BGM of the target user in the target area is a specific BGM, it may analyze the user-related information of the target user in the target area again when the specific BGM has been played once, and determine the next BGM. Here, the timing when the specific BGM has been played once may be, for example, the timing when one song ends, or the timing when a playlist (in other words, an album, etc.) consisting of multiple songs ends. Furthermore, when the environment setting module 1731 determines that the BGM of the target user in the target area is a specific BGM, it may analyze the user-related information of the target user in the target area again when a predetermined period (e.g., 5 minutes) has elapsed since the determination, and determine the next BGM.

In other words, the user-related information may be acquired in real time by the user information acquisition module 1736, but the BGM may not change in real time (in other words, immediately) in response to a change in the type of user 5 present in the target area (in other words, a user 5 entering the target area or a user 5 exiting the target area), but may change upon a specified trigger.

In addition, the change in BGM when user 5 moves from one target area to another can be done, for example, as follows. Here, as shown in FIG. 24, an example will be described in which initially three users, user 5A, user 5B, and user 5C, exist in the first space, and two users, user 5D and user 5E, exist in the second space, and then user 5C moves from the first space to the second space.

First, the environment setting module 1731 determines that the BGM suitable for the first space is the first BGM based on the user-related information of users 5A, 5B, and 5C, and sets the BGM for users 5A, 5B, and 5C as the first BGM. Also, the environment setting module 1731 determines that the BGM suitable for the second space is the second BGM based on the user-related information of users 5D and 5E, and sets the BGM for users 5D and 5E as the second BGM.

In this state, when user 5C moves from the first space to the second space, the environment setting module 1731 re-determines the BGM suitable for the first space based on the user-related information of user 5A and user 5B, and changes the BGM for user 5A and user 5B. The timing for changing the BGM for user 5A and user 5B (in other words, the timing for re-determining the BGM) may be the timing when user 5C leaves the first space, the timing when the first BGM has been played for one cycle, or the timing when a predetermined period (e.g., 5 minutes) has elapsed since the BGM for the first space was determined as the first BGM. Here, the change in BGM when user 5 leaves the target area has been described using an example in which user 5C moves from the first space to the second space, but the same can be applied to the case in which user 5 leaves the target area by logging out of the metaverse.

Furthermore, when user 5C moves from the first space to the second space, the environment setting module 1731 re-determines the BGM suitable for the second space based on the user-related information of user 5C, user 5D, and user 5E, and changes the BGM for user 5C, user 5D, and user 5E. The timing for changing the BGM for user 5D and user 5E (in other words, the timing for re-determining the BGM) may be the timing when user 5C enters the second space, or the timing when the second BGM has been played for one cycle, or the timing when a predetermined period of time (e.g., 5 minutes) has elapsed since the BGM for the second space was determined to be the second BGM, etc.

In this way, once background music is set for a target area (in other words, the environment is set), environmental control may be performed so that no new background music changes (in other words, changes in the environment) occur until a predetermined period of time has passed since the background music was set, even if the type or number of users present in the target area changes.

The environment setting module 1731 may change the BGM of user 5C as follows. That is, for example, when user 5C enters the second space, the environment setting module 1731 may change the BGM of user 5C to the second BGM set for users 5D and 5E who were in the second space before user 5C entered the second space. In this case, for user 5C, the second BGM may be played from the playback point when users 5D and 5E are listening, or may be played from the beginning. Then, after that, when the second BGM has been played for one cycle, or when a predetermined period (e.g., 5 minutes) has elapsed since the BGM of the second space was determined as the second BGM, the BGM of users 5C, 5D, and 5E may be changed to the BGM determined by the environment setting module 1731 based on the user-related information of users 5C, 5D, and 5E. Alternatively, the environment setting module 1731 may analyze user-related information for users 5C, 5D, and 5E when user 5C enters the second space, and change the BGM for users 5C, 5D, and 5E to BGM determined based on the analysis.

In addition, when moving from the first space to the second space, the control module 510 may change the BGM of the user 5C so that the first BGM gradually becomes inaudible and the second BGM gradually becomes inaudible. In other words, the control module 510 may control the BGM so that when the user 5 leaves a certain target area, the BGM set for the target user in the certain target area fades out. In addition, the control module 510 may control the BGM so that when the user 5 approaches a certain target area, the BGM set for the target user in the certain target area fades in. In other words, the first BGM (in other words, the setting for the environment) set for the user 5C as the target user in the first space by the environment setting module 1731 may be continuously output from the speaker 180 of the user 5C even after the user 5C leaves the first space. In addition, the first BGM set by the environment setting module 1731 for the user 5C as the target user in the first space may be configured to stop being output from the speaker 180 of the user 5C when the user 5C leaves the first space.

In addition, the BGM (herein referred to as "recommended BGM") that the environment setting module 1731 determines based on the user-related information of the target user and that is set as the BGM for the target users including the specific user 5 may be made available for the specific user 5 to listen to at any time. Specifically, for example, when the environment setting module 1731 determines a specific BGM as the BGM to be recommended to the specific user 5, it changes the BGM output from the speaker 180 of the HMD set 110 of the specific user 5 to the specific BGM. For example, when the environment setting module 1731 determines the recommended BGM to be recommended to the specific user 5, it transmits information related to the output of the recommended BGM from the speaker 180 to the control module 510 of the HMD set 110 of the specific user 5. Then, when the control module 510 receives the information, it outputs the recommended BGM to the speaker 180. Furthermore, when the control module 510 receives the information, it causes the monitor 130 to display a display related to the registration of the recommended BGM as a favorite (hereinafter, referred to as a "favorite registration display 35") as shown in Fig. 25. Specifically, when the control module 510 receives the information, it may cause the monitor 130 to automatically (in other words, without the operation of the user 5) display the favorite registration display 35 related to the registration of the recommended BGM as a favorite. Alternatively, when the control module 510 receives the information and is in a state where the recommended BGM is being output to the speaker 180, it may cause the monitor 130 to display the favorite registration display 35 related to the registration of the recommended BGM as a favorite when a predetermined operation (for example, an operation by the controller 300) is performed. Alternatively, the control module 510 may receive the information, and when the user 5 performs an operation related to logging out from the metaverse after the output of the recommended BGM from the speaker 180 has started (for example, while the recommended BGM is playing or after the recommended BGM has finished playing), the control module 510 may display a favorite registration display 35 related to the registration of the recommended BGM as a favorite on the monitor 130 before executing the logout. Then, when a predetermined operation is performed while the favorite registration display 35 is displayed on the monitor 130, the recommended BGM may be registered as a favorite. Note that information on the BGM registered as a favorite is stored, for example, in the memory module 530 or the memory module 1630 as a favorite storage means. Then, when a predetermined operation (for example, an operation by the controller 300 on a predetermined menu screen) is performed by the user 5 during an activity in the metaverse, the control module 510 may output the BGM registered as a favorite to the speaker 180. Note that "registration as a favorite" may be setting as the default BGM. Default BGM refers to, for example, BGM that is normally played as BGM for user 5 in areas other than the target area. Note that the default BGM may be, for example, BGM output from speaker 180 outside the metaverse (for example, while a screen that accepts operations for logging in to the metaverse is being displayed). In other words, control module 510 may cause speaker 180 to output BGM registered as a favorite outside the metaverse (for example, automatically or based on a predetermined operation by user 5).

In addition, information about the recommended BGM once recommended to user 5 may be stored as log information in memory module 530 or memory module 1630. Then, when user 5 performs a predetermined operation (e.g., an operation using controller 300 on a predetermined menu screen) during activities in the metaverse, control module 510 may cause monitor 130 to display a list of recommended BGM previously recommended to user 5 based on the log information, and may cause speaker 180 to output the recommended BGM previously recommended based on a selection from the list by user 5.

In addition, when the environment setting module 1731 changes the environment in the metaverse of multiple target users in the target area to a specific BGM, a specific background, or a specific brightness, the environment may be changed through the selection (in other words, operation) of a specific user 5 in the target area. Specifically, for example, a DJ (Disc Jockey) may exist as the specific user 5 in the target area. The BGM of multiple target users in the target area may be changed according to the selection of the DJ. The method of setting the DJ (in other words, the specific user 5) is not particularly limited, but for example, if the target area is a specific live venue, a sports viewing facility, a party venue, or a store, a user 5 who is set as the organizer of an event (in other words, the invitee) or the owner of the venue in the metaverse may be set as the DJ. In addition, the control module 1610 may determine the DJ based on a specific rule or randomly from multiple target users in the target area. The DJ may or may not be included in the target users.

A control example in which the BGM of multiple target users in the target area is changed based on the DJ's selection will be described with reference to FIG. 26. In this control example, the environment setting module 1731 extracts multiple BGMs to be recommended as BGM for the multiple target users in the target area (in other words, BGM candidates to be set for the multiple target users) based on the user-related information of the multiple target users in the target area. At this time, the environment setting module 1731 also outputs information on the recommendation level of the multiple recommended BGMs (in other words, the recommendation level of each candidate). The environment setting module 1731 then transmits information indicating the recommended BGM and information on the recommendation level of the recommended BGM to the DJ's control module 510. Note that, for example, the recommendation level is higher for BGM that is suitable for (in other words, is likely to be liked by) more target users in the target area.

Based on the information transmitted from the environment setting module 1731, the DJ control module 510 displays on the monitor 130 a display showing the multiple BGMs recommended and the recommendation level of each BGM. Specifically, the control module 510 displays on the monitor 130 the song titles and artist names of the multiple BGMs. The control module 510 also displays on the monitor 130 a percentage display as a display showing the recommendation level of each BGM. The percentage display may show the proportion of users 5 to whom each BGM is suitable (in other words, who are likely to like each BGM). The recommendation level of each BGM may be shown by the display order on the monitor 130. Specifically, for example, the higher the BGM displayed on the monitor 130, the higher the recommendation level. The recommendation level of each BGM may be shown not as a percentage display, but by displaying the number of users 5 to whom each BGM is suitable, as shown in FIG. 26.

In addition, when a display showing multiple recommended BGM and the recommendation level of each BGM is displayed on the monitor 130, and the DJ selects one of the multiple recommended BGM (for example, an operation by the controller 300), the control module 510 transmits information indicating the selected BGM to the environment setting module 1731. Then, based on the information, the environment setting module 1731 changes the BGM of all target users in the target area to the selected BGM. In other words, the environment setting module 1731 changes the environment in the metaverse of multiple target users in the target area according to a candidate selected by a specific user in the target area from multiple candidates extracted based on user-related information about the multiple target users in the target area.

The multiple recommended BGMs presented to the DJ (in other words, displayed on the DJ's monitor 130) may include music that each target user likes and that has been registered in advance as their profile information, etc. The multiple recommended BGMs presented to the DJ may also include music that is suitable for the target user and is extracted based on the target user's behavioral history.

In addition, the environment setting module 1731 may set the importance of the user-related information of the user 5 who has made a certain payment higher than the importance of the user-related information of the user 5 who has not made the certain payment when recommending BGM. In other words, the environment setting module 1731 changes the BGM of multiple users 5 based on the user-related information of the multiple users 5, and at this time, the BGM suitable for the user 5 who has made a payment may be controlled to be played preferentially over the BGM suitable for the user 5 who has not made a payment. Also, for example, the environment setting module 1731 may control so that the BGM suitable for the user 5 who has made a payment is more highly recommended than the BGM suitable for the user 5 who has not made a payment, in the display on the DJ's monitor 130. In addition, for example, when sending information indicating the BGM to be recommended to the DJ's control module 510, the environment setting module 1731 may send information indicating whether each BGM is suitable for the user 5 who has made a payment. Based on the information transmitted from the environment setting module 1731, the control module 510 may cause the monitor 130 to display a display indicating whether or not each of the recommended BGMs is suitable for the user 5 who has paid. Note that information on whether or not each user 5 has paid is stored in, for example, the memory module 1630.

The environment setting module 1731 may also change the environment in the metaverse based on user-related information of multiple users 5 participating in a specific game in the metaverse, etc. For example, the environment setting module 1731 may compile the occupations (e.g., warrior, wizard, etc.) that the target users have set for their characters (here, the character includes an avatar) as an analysis of the user-related information of the target users who are in a specific target area in the game. Then, for example, when the analysis result of analyzing all the target users in the specific target area shows that there are many users 5 in the target area who have set their occupation to warrior, the environment setting module 1731 may change the background music of all the target users in the target area (in other words, multiple users 5 including users 5 who have set their occupation to something other than warrior) to brave background music corresponding to warrior.

In addition, the environment setting module 1731 as a change means may bring about the following changes to things in the metaverse based on the user-related information of multiple users 5 participating in a specified game. That is, for example, the environment setting module 1731 may change items that can be obtained in the metaverse or events that occur, etc., based on the user-related information of multiple target users who are in a specified target area. Also, for example, the environment setting module 1731 may apply buffs to multiple target users who are in a specified target area or debuff enemies of the multiple target users based on the user-related information of the multiple target users. In other words, the environment setting module 1731 may change the specified target area to a place advantageous to the multiple target users based on the user-related information of the multiple target users who are in the specified target area. Specifically, for example, in a game in which a plurality of users 5 defeat an enemy in a target area, if there are a predetermined number or more users 5 in the target area who have set their occupation to a specific occupation (e.g., wizard) (specifically, for example, if all target users in the target area have set their occupation to a specific occupation), a buff may be applied to all target users in the target area (in other words, to the characters of all target users). Note that, for example, in a game in which a plurality of users form a group (in other words, a party) to defeat an enemy, if all users in the group have set their occupation to a specific occupation (e.g., wizard), the environment setting module 1731 may apply a buff to all users in the group (in other words, to the characters of all target users). In other words, the environment setting module 1731 may change a certain parameter that affects the achievement of a certain objective in a certain game (e.g., clearing a certain stage or defeating a certain enemy) based on the user-related information of multiple users 5 (specifically, for example, changing the effect (e.g., damage) that a certain action (e.g., an attack) of a character of user 5 has on the enemy).

As described above, the environment setting module 1731 changes the environment in the metaverse of multiple users 5 based on user-related information about two or more users 5, but the two or more users 5 do not have to be users 5 that are all in the same specific area. For example, the environment setting module 1731 may change the environment (e.g., background music) in the metaverse of multiple users 5 based on user-related information about the multiple users 5 that form a specific group. The specific group may be, for example, a group of users 5 that converse with each other in voice chat or text chat. The specific group may also be, for example, a group formed by the user himself and his friends. The specific group may also be a group (in other words, a party) that aims to achieve a specific goal together in a game.

The environment setting module 1731 changes the environment in the metaverse of the multiple users 5 based on the user-related information about the two or more users 5, and at least one of the two or more users 5 and the multiple users 5 may include an unspecified user 5. In other words, for example, one of the two or more users 5 and the other users may not have a specific relationship (for example, a friend relationship, a relationship of having a conversation with each other (for example, participating in the same group chat), a relationship of forming a party, etc.) other than the relationship of being in the same target area. Also, one of the multiple users 5 and the other users may not have a specific relationship other than the relationship of being in the same target area. In other words, the target area may be an area that the unspecified user 5 can enter as a target user.

When changing the environment, etc. in the metaverse of multiple users 5 based on user-related information about two or more users 5 in the target area, the environment setting module 1731 may change the environment, etc. in the metaverse based not only on the user-related information, but also on the user-related information and the image of the target area itself. In other words, the background music, background, brightness, etc. recommended by the environment setting module 1731 to the target user may reflect the image of the target area itself.

Next, an example of a process for changing the environment in the metaverse for multiple users 5 based on user-related information for two or more users 5 will be described with reference to FIG. 27.

In step S401, the user information acquisition module 1736 acquires user-related information for each user 5 in the metaverse and stores it in the memory module 1630, which serves as a user-related information storage means.

Next, in step S402, the environment setting module 1731 determines the BGM to be set as the BGM for multiple users 5 (e.g., all users 5) within a specific target area based on the user-related information of the multiple users 5.

Next, in step S403, the environment setting module 1731 transmits information about the determined BGM to the HMD set 110 of each of the multiple users 5.

Next, in step S404, the control module 510 of the HMD set 110 of each of the multiple users 5 outputs the background music determined by the environment setting module 1731 to the speaker 180 based on the information transmitted in step S403.

The present invention is not limited to the above-described embodiment, and can be modified in various ways without departing from the spirit of the invention. Within the scope of the invention, the components can be freely combined, any component can be modified, or any component can be omitted. The process flow described in this specification is merely an example, and the order and configuration of each process can be different.

[Additional Notes]
The matters described in the above embodiment can also be described as follows.

(Appendix 1)
Computer,
An acquisition means (e.g., a user information acquisition module 1736) for acquiring information related to a user who uses the metaverse;
A program that functions as a change means (e.g., a recommendation module 1731) that changes the environment of multiple users in the metaverse based on the information about at least two or more users.
According to such a configuration, the environment in the metaverse of multiple users changes according to the user-related information for two or more users. Therefore, the environment in the metaverse of the multiple users can be changed by comprehensively judging the user-related information for two or more users. Therefore, the environment in the metaverse for the multiple users, in other words, for a specific group, can be set to an appropriate environment according to the group, and the interest of the service can be improved. That is, according to such a configuration, it is possible to solve the problem that the environment cannot be set appropriately according to the group in the metaverse.

(Appendix 2)
The program described in Appendix 1, wherein the change means changes the environment in the metaverse of multiple users in a specific area based on the information about at least two or more users in the specific area in the metaverse.
According to this configuration, it is possible to comprehensively determine information related to two or more users in a specific area and change the environment in the metaverse of multiple users in the specific area. Therefore, the environment in the metaverse for the users in the specific area can be set appropriately according to the group of users in the specific area, and the interest of the service can be improved.

(Appendix 3)
The program described in Appendix 1, wherein the change means changes the environment in the metaverse of all users in a specific area based on the information about all users in the specific area in the metaverse.
According to this configuration, it is possible to comprehensively determine information related to all users in a specific area and change the environment in the metaverse of all users in the specific area. Therefore, the environment in the metaverse for users in the specific area can be set to be suitable for the specific area, and the interest of the service can be improved.

(Appendix 4)
The program described in Appendix 1, wherein the change means changes the environment in the metaverse of a plurality of users in a specific area in the metaverse in accordance with a candidate selected by a specific user in the specific area from a plurality of candidates extracted based on the information about the plurality of users in the specific area in the metaverse.
According to this configuration, when changing the environment in the metaverse of multiple users in a specific area based on the user-related information of the multiple users, the content of the change can be determined according to the selection of a specific user in the specific area. Therefore, the characteristics of each user who has the right to select can be reflected in the change in the environment, thereby improving the interest of the service.

(Appendix 5)
The program according to any one of appendices 1 to 4, wherein the change means changes background music played within the metaverse as a change in the environment within the metaverse.
According to such a configuration, background music for a plurality of users can be changed in accordance with user-related information for two or more users, thereby making the service more interesting.

(Appendix 6)
An acquisition means (e.g., a user information acquisition module 1736) for acquiring information related to a user who uses the metaverse;
An information processing system comprising: a change means (e.g., a recommendation module 1731) for changing the environment of multiple users in the metaverse based on the information about at least two or more users.
With this configuration, the same effects as those of the program described in Supplementary Note 1 can be achieved.

5 User, 6 Avatar object, 11 Virtual space, 100 HMD system, 110 HMD set, 120 HMD, 130 Monitor, 200 Computer, 210 Processor, 220 Memory, 230 Storage, 240 Input/output interface, 250 Communication interface, 300 Controller, 410 HMD sensor, 420 Motion sensor, 510 Control module, 520 Rendering module, 530 Memory module, 540 Communication control module, 600 Server, 610 Processor, 620 Memory, 630 Storage, 640 Input/output interface, 650 Communication interface, 700 External device, 1421 Virtual camera control module, 1422 Viewing area determination module, 1423 Reference line of sight identification module, 1424 Face organ detection module, 1425 Motion detection module, 1426 Virtual space definition module, 1427 Virtual object generation module, 1428 Operation object control module, 1429 Avatar control module, 1438 View image generation module, 1610 Control module, 1630 Memory module, 1640 Communication control module, 1721 Recommendation information presentation module, 1731 Recommendation module (environment setting module), 1732 Attribute setting module, 1733 Action history acquisition module, 1734 Access control module, 1736 User information acquisition module, 1741 Collaboration management module, 1751 Virtual space history storage unit, 1752 User attribute storage unit, 1753 Real world history storage unit

Claims (6)

Computer,
An acquisition means for acquiring information related to a user who uses the metaverse;
A program that functions as a change means for changing the environment of multiple users in the metaverse based on the information about at least two or more users. The program according to claim 1 , wherein the change means changes the environment in the metaverse of a plurality of users in a specific area based on the information about at least two or more users in the specific area in the metaverse. The program according to claim 1 , wherein the change means changes an environment in the metaverse of all users in a specific area based on the information about all users in the specific area in the metaverse. The program of claim 1, wherein the change means changes the environment of a plurality of users in the metaverse in accordance with a candidate selected by a specific user in a specific area from among a plurality of candidates extracted based on the information about the plurality of users in the specific area of the metaverse. The program according to any one of claims 1 to 4, wherein the change means changes background music played within the metaverse as a change in the environment within the metaverse. An acquisition means for acquiring information related to a user who uses the metaverse;
A change means for changing the environment of a plurality of users in the metaverse based on the information about at least two or more users.

Images