JP7759458B2 - Program and information processing system - Google Patents

Description

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

Services that provide virtual spaces (in other words, metaverses) where users can interact with each other have been known for some time (see, for example, Patent Document 1).

JP 2011-216073 A

However, there was a demand for such services to be more entertaining.

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

According to one embodiment shown in the present disclosure,
Computer,
A program is provided that functions as a recommendation means for recommending predetermined things in the metaverse to a user based on the user's behavior history in the metaverse.

This invention can improve the interest of services.

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. 1 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 representing a virtual space according to an embodiment. 1 is a top view of a user's head wearing an HMD according to an embodiment. 10 is a diagram showing a YZ cross section of a field of view in a virtual space as viewed from the X direction. 10 is a diagram showing an XZ cross section of a field of view in a virtual space as viewed from the Y direction. FIG. 2 is a diagram illustrating a schematic configuration of a controller according to an embodiment. FIG. 10 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. 10 is a sequence chart showing a process executed in an HMD set according to an embodiment. FIG. 1 is a schematic diagram illustrating 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 a user 5A in FIG. 12(A). 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 modules in a computer according to an embodiment. FIG. 2 is a block diagram illustrating a modular configuration of a server according to an embodiment. FIG. 10 is a diagram illustrating attributes set for a user according to an embodiment. FIG. 10 is a diagram illustrating a display that provides a predetermined recommendation to a user according to an embodiment. FIG. 10 is a diagram illustrating a display that provides a predetermined recommendation to a user according to an embodiment. 10 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. 10 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. 10 is a sequence chart illustrating an example of a process for making recommendations regarding things in the metaverse based on a behavior history in the real world according to an embodiment. 10 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.

Embodiments of this technical concept will be described in detail below with reference to the drawings. In the following description, identical components are assigned 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 combined result also forms 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 business use. The HMD system 100 provides predetermined services 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 will be 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 device 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. Therefore, when the user 5 views the three-dimensional image displayed on the monitor 130, the user 5 can become immersed in the virtual space. In one aspect, the virtual space includes, for example, a background, objects that the user 5 can manipulate, and images of menus that the user 5 can select. In another aspect, the monitor 130 can be realized as a liquid crystal monitor or organic EL (Electro Luminescence) monitor that is provided on a 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 the real space may be made visible by setting the transmittance of a portion of the monitor 130 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 light. 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 tilt 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 tilt 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 tilt 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 tilt of the HMD 120 based on the change in angle over time.

The gaze sensor 140 detects the direction in which the right and left eyes of the user 5 are looking. In other words, the gaze sensor 140 detects the gaze of the user 5. Detection of the gaze direction is achieved, for example, by a known eye tracking function. The gaze sensor 140 is achieved by a sensor having this eye tracking function. In certain aspects, 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 and left eyes of the user 5 with infrared light and detects the rotation angle of each eyeball by receiving light reflected from the cornea and iris of 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 captures the lower part of the face of the user 5. More specifically, the first camera 150 captures the nose, mouth, etc. of the user 5. The second camera 160 captures 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 from the user 5 is defined as the outside of the HMD 120. In one aspect, the first camera 150 may be positioned outside the HMD 120, and the second camera 160 may be positioned 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 implemented as a single camera, and the face of the user 5 may be captured 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 via a wired or wireless connection. The controller 300 accepts commands input 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 wearable on 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 objects 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 the 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 user 5's hand. 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 real space, the controller 300 is attached to something that is worn on the user 5's hand, such as a glove, so that it will not easily fly away. In yet another aspect, a sensor not worn by the user 5 may detect the movement of the user 5's hand. For example, a signal from a camera capturing an image of the user 5 may be input to the computer 200 as a signal representing the user 5's movement. The motion sensor 420 and the computer 200 are connected to each other wirelessly, for example. In the case of wireless communication, the communication format is not particularly limited, and for example, Bluetooth (registered trademark) or other known communication methods may be 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 the same image as 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 HMDs 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 each user's actions 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 each user's actions with the other computers 200 without going through the server 600.

External device 700 may be any device that can communicate with computer 200. External device 700 may be, for example, a device that can communicate with computer 200 via network 2, or a device that can communicate directly with computer 200 via short-range wireless communication or a wired connection. External device 700 may also be, for example, a device that can communicate with server 600 via network 2. Examples of external device 700 include, but are not limited to, smart devices, PCs (Personal Computers), and peripheral devices for computer 200.

[Computer hardware configuration]
A computer 200 according to this embodiment will be described with reference to Fig. 2. Fig. 2 is a block diagram showing an example of the hardware configuration of computer 200 according to this embodiment. 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.

Processor 210 executes a series of instructions contained in a program stored in memory 220 or storage 230 based on a signal provided to computer 200 or based on the fulfillment of a predetermined condition. In some aspects, processor 210 is realized as a CPU (Central Processing Unit), GPU (Graphics Processing Unit), MPU (Micro Processor Unit), 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 implemented as RAM (Random Access Memory) or other volatile memory.

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

In another aspect, the storage 230 may be implemented 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. Such a configuration makes it possible to collectively update programs and data in situations where multiple HMD systems 100 are used, such as in amusement facilities.

The input/output interface 240 communicates signals between the HMD 120, HMD sensor 410, motion sensor 420, and display 430. The monitor 130, gaze sensor 140, first camera 150, second camera 160, microphone 170, and 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 implemented using a USB (Universal Serial Bus), DVI (Digital Visual Interface), HDMI (High-Definition Multimedia Interface), or other terminal. The input/output interface 240 is not limited to those described 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. Upon receiving the instructions, the controller 300 performs one of the following actions in response to the instructions: vibration, sound output, or light emission.

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 some aspects, the communication interface 250 is implemented 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), or NFC (Near Field Communication). 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 that can be executed in the virtual space, etc. 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.

In the example shown in FIG. 2, the computer 200 is configured to be external to 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, it is possible to provide the same virtual space 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 preset 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 light 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 in response 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 for the HMD 120 based on the tilt of the HMD 120 in the real coordinate system. The uvw field of view coordinate system set for the HMD 120 corresponds to the viewpoint coordinate system when a user 5 wearing the HMD 120 views an object in 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 illustrating the uvw field of view coordinate system set in the HMD 120 according to an embodiment. The HMD sensor 410 detects the position and tilt of the HMD 120 in the real coordinate system when the HMD 120 is started up. 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-to-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 these three new directions as the pitch axis (u-axis), yaw axis (v-axis), and roll axis (w-axis) of the uvw field of view coordinate system for the HMD 120.

In a certain situation, when a user 5 wearing the HMD 120 is standing upright and looking straight ahead, the processor 210 sets a uvw field of view coordinate system parallel to the real coordinate system in the HMD 120. 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 has moved 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 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 obtained based on the output from the infrared sensor and the relative positional relationships between multiple points (e.g., the distances between each point). 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 conceptual diagram illustrating one mode of expressing a virtual space 11 according to an embodiment. The virtual space 11 has a spherical structure that covers the entire 360-degree area from a center 12. To avoid complicating the explanation, FIG. 4 illustrates only the upper half of the celestial sphere in the virtual space 11. Meshes are defined in the virtual space 11. The position of each mesh is defined in advance as coordinate values in an XYZ coordinate system, which is a global coordinate system defined in the virtual space 11. The computer 200 associates each partial image that constitutes a panoramic image 13 (still image, video, etc.) that can be deployed in the virtual space 11 with a corresponding mesh in the virtual space 11.

In a certain situation, an XYZ coordinate system is defined in virtual space 11 with center 12 as its origin. The XYZ coordinate system is, for example, parallel to the real coordinate system. The horizontal direction, vertical direction (up and down direction), and front and 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 and 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 positioned 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 conjunction with the movement of the HMD 120 in real space. This allows changes in the position and tilt of the HMD 120 in real space to be reproduced in the virtual space 11 in the same way.

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 defines a field of view 15 in the virtual space 11 based on the position and tilt (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 visible to 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 diagram showing the head of the user 5 wearing the HMD 120 according to an embodiment, viewed from above.

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

When computer 200 receives the detection values of lines of sight R1 and L1 from gaze sensor 140 as the gaze detection result, it identifies gaze point N1, which is the intersection of lines of sight R1 and L1, based on the detection values. On the other hand, when computer 200 receives the detection values of lines of sight R2 and L2 from gaze sensor 140, it identifies the intersection of lines of sight R2 and L2 as the gaze point. Computer 200 identifies user 5's gaze NO based on the position of identified gaze point N1. For example, computer 200 detects as gaze NO the direction in which a line passing through gaze point N1 and the midpoint of a line connecting user 5's right eye R and left eye L extends. Gaze NO is the direction in which user 5 actually looks with both eyes. Gaze NO corresponds to the direction in which user 5 actually looks relative to field of view 15.

In another aspect, the HMD system 100 may be equipped with a television broadcast receiving tuner. With this 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 call function for connecting to a telephone line.

[Visibility area]
The field of view 15 will be described with reference to Figures 6 and 7. Figure 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. Figure 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 area 18. 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 in the virtual space centered on the reference line of sight 16 and including the polar angle α as 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 the virtual camera 14, the reference line of sight 16, and the XZ cross section of the virtual space 11. The processor 210 defines the range including the azimuth angle β centered on the reference line of sight 16 in the virtual space 11 as area 19. The polar angles α and β are determined according to the position of the virtual camera 14 and the tilt (orientation) of the 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 corresponding to the 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 their head, the virtual camera 14 also moves in conjunction with that movement. As a result, the position of the field of view 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 15 in the direction 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 tilt 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 placed corresponds to the viewpoint of the user 5 in the virtual space 11. Therefore, by changing the position or tilt 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. As a result, the HMD system 100 can give the user 5 a highly immersive feeling in the virtual space 11.

In some situations, 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 determines the image area (field of view 15) to be projected onto the monitor 130 of the HMD 120 based on the position and tilt 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 implemented using 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 concept 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 with the right hand of the user 5. The left controller is operated with the left hand of the user 5. In one aspect, the right controller 300R and the left controller are configured symmetrically as separate devices. Therefore, 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 can be operated with 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 some aspects, 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 multiple infrared LEDs 360 arranged circumferentially. The infrared LEDs 360 emit infrared light in accordance with the progress of a program that uses the controller 300 while the program is running. 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 Figure 8, the infrared LEDs 360 are arranged in two rows, but the number of rows is not limited to that shown in Figure 8. An arrangement in one row or three or more rows may also be used.

The top surface 330 is equipped with 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 user's 5 right hand. 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 objects placed in the virtual space 11.

In one aspect, the right controller 300R and the left controller include batteries for powering the infrared LED 360 and other components. Batteries include, but are not limited to, rechargeable, button-type, and dry cell types. In another aspect, the right controller 300R and the left controller can be connected to, for example, the USB interface of the computer 200. In this case, the right controller 300R and the left controller do not require batteries.

As shown in states (A) and (B) in Figure 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 yaw axis and the roll axis is defined as the pitch direction.

[Server hardware configuration]
Server 600 according to this 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.

Processor 610 executes a series of instructions contained in a program stored in memory 620 or storage 630 based on a signal provided to server 600 or based on the fulfillment of a predetermined condition. In some aspects, processor 610 is implemented as a CPU, GPU, MPU, 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 implemented as RAM or other volatile memory.

Storage 630 permanently stores programs and data. Storage 630 is realized, for example, as a ROM, a hard disk drive, flash memory, or other non-volatile storage device. Programs stored in storage 630 may include programs for providing a virtual space in HMD system 100, simulation programs, game programs, user authentication programs, and programs 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 implemented 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 630 built into the server 600. Such a configuration makes it possible to collectively update programs and data in situations where multiple HMD systems 100 are used, such as in amusement facilities.

The input/output interface 640 communicates signals with input/output devices. In some aspects, the input/output interface 640 is implemented 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 some aspects, 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, or NFC. The communication interface 650 is not limited to the above.

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

[HMD control device]
The control device of the HMD 120 will be described with reference to Fig. 10. In one embodiment, the control device is realized by a computer 200 having a known configuration. Fig. 10 is a block diagram showing the modular configuration of the computer 200 according to one embodiment.

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 implemented 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 implemented by the memory 220 or the storage 230. The communication control module 540 is implemented 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, for example, in the memory module 530. The control module 510 may generate the virtual space data or obtain the virtual space data from a 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, for example, in the memory module 530. The control module 510 may generate the object data or obtain it from the server 600 or the like. The objects may include, for example, an avatar object representing the user 5, a character object, an operational object such as a virtual hand operated by the controller 300, landscapes including forests, mountains, and the like, cityscapes, animals, etc. that are placed as the game story progresses, etc.

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

The control module 510 determines the tilt of the HMD 120 based on the output of the HMD sensor 410. In another aspect, the control module 510 determines the tilt of the HMD 120 based on the output of the sensor 190, which functions 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 values 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 tilt 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 in 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 in the face of the avatar object placed in the virtual space 11. The control module 510 receives gaze information of another user 5 from the server 600 and reflects this information in the gaze of the avatar object of the other user 5. In some aspects, the control module 510 reflects the movement of the controller 300 in the avatar object or the control 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 include 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 a control object in the virtual space 11 to receive operations from the user 5 in the virtual space 11. The user 5 operates the control object to, for example, operate an object placed in the virtual space 11. In one aspect, the control 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 user 5's hand in real space based on the output of the motion sensor 420. In one aspect, the control 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, for example, detect the timing when the collision area of one object comes into contact with the collision area of another object, and performs predetermined processing when this detection is made. The control module 510 can detect the timing when two objects no longer come into contact with each other, and performs predetermined processing when this detection is made. The control module 510 can detect when two objects are in contact with each other. For example, when a control object comes into contact with another object, the control module 510 detects this contact and performs predetermined processing.

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 (orientation) of the virtual camera 14. The control module 510 defines a 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 audio data corresponding to the speech is to be sent. The audio data is sent to the computer 200 identified by the control module 510. When the control module 510 receives audio data from another user's computer 200 via the network 2, it outputs audio (speech) corresponding to the audio data from the speaker 180.

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

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

The object information includes multiple panoramic images 13 that make up 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. Examples of images of unreal space include images generated using 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 set on the computer 200 used by the user. In another aspect, the user ID may be set by the user. The user information includes programs and the like that cause the computer 200 to function as a control device for the HMD system 100. The user information also includes information 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 communication devices via network 2.

In one aspect, the control module 510 and the rendering module 520 may be implemented 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 implemented as a combination of circuit elements that implement each process.

Processing in computer 200 is realized by hardware and software executed by processor 210. Such software may be pre-stored on a hard disk or other memory module 530. Software may also 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 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 the 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 viewing the field of view image.

In step S1134, the HMD sensor 410 detects the position and tilt 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 movement 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, processor 210 executes the application program and places objects in virtual space 11 based on instructions included in the application program.

In step S1160, controller 300 detects an operation by user 5 and outputs detection data representing the detected operation to computer 200. In another aspect, the operation by user 5 may be detected based on images from a camera positioned around 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 this embodiment will be described with reference to FIGS. 12A and 12B. Hereinafter, avatar objects of each user 5 of HMD sets 110A and 110B will be described. Hereinafter, the user of HMD set 110A will be referred to as user 5A, the user of HMD set 110B as user 5B, the user of HMD set 110C as user 5C, and the user of HMD set 110D as user 5D. A is added to the reference symbol of each component related to HMD set 110A, B is added to the reference symbol of each component related to HMD set 110B, C is added to the reference symbol of each component related to HMD set 110C, and D is added to the reference symbol of each component related to HMD set 110D. For example, HMD 120A is included in HMD set 110A.

Figure 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 Figure 12(A), virtual space 11A and virtual space 11B are configured using the same data. In other words, computers 200A and 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. Avatar object 6A in virtual space 11A and avatar object 6B in virtual space 11B are each wearing an HMD 120, but this is for ease of explanation; in reality, these objects do not wear HMDs 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. 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 also displayed in the field of view image of user 5B.

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

The actions of user 5B (the movements of HMD 120B and controller 300B) are reflected by processor 210A in avatar object 6B placed in virtual space 11A. As a result, user 5A can view avatar object 6B, which is manipulated and moves by user 5B.

Figure 13 is a sequence chart showing part of the processing executed in the HMD system 100 according to the present embodiment. Although HMD set 110D is not shown in Figure 13, HMD set 110D operates in the same manner as HMD sets 110A, 110B, and 110C. In the following description, A will be added to the reference number of each component related to HMD set 110A, B will be added to the reference number of each component related to HMD set 110B, C will be added to the reference number of each component related to HMD set 110C, and D will be added to the reference number of each component related to 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. This avatar information includes information about the avatar, such as movement information, face tracking data, and audio data. The movement information includes information indicating temporal changes in the position and tilt of the HMD 120A, information indicating the hand movement of the user 5A detected by the motion sensor 420A, and information indicating the user's operation detected by the controller 300. The face tracking data includes data specifying the position and size of each feature of the user 5A's face. The face tracking data includes data indicating the movement of each organ constituting the user 5A's face and gaze data. The audio 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 identifying the avatar object 6A and the user 5A include a user ID. Examples of information 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, 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 time.

Next, each HMD set 110A-110C executes steps S1330A-S1330C based on the avatar information transmitted from the server 600 to each HMD set 110A-110C. Step S1330A corresponds to step S1180 in Figure 11.

In step S1330A, the processor 210A in the HMD set 110A updates the information on the avatar objects 6B and 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 11A 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 11A 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 on the avatar objects 6A and 6C of 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 on the avatar objects 6A and 6B of users 5A and 5B in the virtual space 11C.

[Module detailed configuration]
The modular configuration of computer 200 will be described in detail with reference to Fig. 14. Fig. 14 is a block diagram showing the detailed modular configuration 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 facial organ detection module 1424, a movement 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 and orientation (tilt) of the virtual camera 14 in the virtual space 11. 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 facial organ detection module 1424 detects the organs that make up the face of the user 5 (e.g., mouth, eyes, eyebrows) from the images of the user 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 facial 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. Objects may include, for example, landscapes including forests, mountains, and other elements, animals, etc., which are placed according to the progression of the game's story.

The control object control module 1428 places control objects in the virtual space 11 to receive user operations in the virtual space 11. The user operates the control objects to, for example, operate objects placed in the virtual space 11. In some situations, the control objects may include, for example, hand objects corresponding to the hands of a user wearing the HMD 120. In some situations, the control objects may correspond to the hand portion of an avatar object, which will be described later.

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

The avatar control module 1429 reflects the movement of the HMD 120 detected by the HMD sensor 410 in 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 in 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 in 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 in the avatar object 6. In this way, the avatar object 6 is controlled (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 implemented by processor 610. Memory module 1630 is implemented by memory 620 or storage 630. Communication control module 1640 is implemented 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 stores data used by computer 200 to provide virtual space 11 to user 5. In one aspect, memory module 1630 stores space information, object information, and user information. The space information, object information, and user information of memory module 1630 may include the space information, object information, and user information of memory module 530 described above, respectively. Therefore, a description thereof will be omitted here.

The communication control module 1640 receives various types of 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 space information, object information, user information, and avatar information. The communication control module 1640 transmits various types of 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 space information, object information, user information, and avatar information.

Processing in server 600 is realized by hardware and software executed by processor 610. Such software may be pre-stored on a hard disk or other memory module 1630. The software may also 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 communication control module 1640, and then temporarily stored in memory module 1630. The software is read from memory module 1630 by processor 610 and stored in RAM in the form of an executable program. Processor 610 executes the program.

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

Furthermore, in this embodiment, the processor 210 of the computer 200 or the processor 610 of the server 600 will be described as performing the above-mentioned or later-described processes by executing a program stored in the HMD system 100. However, at least a portion of the above-mentioned or later-described processes performed by the processor 210 may be performed by a processor other than the processor 210. Furthermore, at least a portion of the above-mentioned or later-described processes performed by the processor 610 may be performed by a processor other than the processor 610. In other words, the computer that executes the program 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 user's behavioral history. The HMD system 100 of this embodiment provides a metaverse as a virtual space 11 in which 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 avatars can be considered users in the metaverse.

Note that the metaverse may or may not contain locations based on (e.g., imitations of) locations (e.g., areas or facilities) that actually 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 within the metaverse]
Recommendation module 1731 makes recommendations regarding predetermined things in the metaverse based on the behavioral history of user 5 in the metaverse. Specifically, for example, recommendation module 1731 determines things to recommend based on the behavioral history of user 5 in the metaverse, and transmits information about the recommended things (hereinafter referred to as "recommended information") to recommendation information presentation module 1721. Recommendation information presentation module 1721 is provided, for example, in control module 510 of user 5's computer 200. Upon receiving the recommendation information, recommendation information presentation module 1721 displays the information about the recommended things on monitor 130.

The recommendation module 1731 makes predetermined recommendations regarding friendships within the metaverse, for example, based on the behavioral history of user 5. Specifically, the recommendation module 1731, for example, recommends to user 5 other users 5 who are likely to be compatible with user 5 (in other words, avatars of those other users 5) as recommendations regarding friendships. More specifically, the recommendation module 1731 recommends to user 5 other users 5 who are likely to become friends with user 5. In this case, the recommendation module 1731, for example, determines other users 5 to recommend to user 5 (hereinafter referred to as "recommended users") from among multiple users 5, and transmits recommendation information indicating the recommended users to the recommendation information presentation module 1721 of user 5's computer 200. Furthermore, upon receiving the recommendation information, the recommendation information presentation module 1721 displays a display regarding the recommendation of the recommended users to user 5 on the monitor 130. The display related to the recommendation may include, for example, a display of the username of the recommended user, a display related to accepting contact with the recommended user, a display showing the location of the recommended user, etc. In other words, when the display related to the recommendation is displayed, an operation by user 5 to contact the recommended user (for example, an operation using controller 300, etc.) may be accepted. Note that here, a display related to accepting contact with the recommended user includes, for example, a display related to accepting a request to register the recommended user as a friend. In other words, when the display related to the recommendation is displayed, an operation to request registration as a friend of the recommended user may be accepted.

Furthermore, as a recommendation regarding friendships, 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 that is likely to include other compatible users 5), rather than recommending another specific user 5 to the user 5. In this case, the recommendation module 1731 determines a group to recommend to the user 5, for example, based on the user 5's behavioral history, and transmits recommendation information indicating the recommended group to the recommendation information presentation module 1721 of the user 5's computer 200. Furthermore, upon receiving the recommendation information, the recommendation information presentation module 1721 displays a display on the monitor 130 related to the recommendation of the group to the user 5. The display related to the recommendation may include, for example, a display of the group name of the recommended group, a display related to accepting contact with the group (e.g., the user 5 representing the group), a display showing the location of the group's headquarters, etc. Note that here, a display related to accepting contact with the group includes, for example, a display related to accepting applications to join the group.

The recommendation module 1731 also makes predetermined recommendations regarding content within the metaverse, for example, based on the behavioral history of the user 5. Specifically, for example, the recommendation module 1731 may recommend a predetermined location within the metaverse (e.g., a region or facility) to the user 5 as a content recommendation. The recommendation module 1731 may also recommend a predetermined service within the metaverse to the user 5 as a content recommendation.

The behavioral history of each user 5 within 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 within 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 a user 5 performs various actions within the metaverse. An example of a behavioral history within 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 information regarding the number of times the avatar's outfit (e.g., clothing (e.g., clothes, hats, accessories, footwear, etc.) or hairstyle, etc.) has been changed. The behavioral history may also include information regarding the number of clothing items (e.g., total number or number of types, etc.) that the avatar has acquired (in other words, possesses).

The behavioral history may also relate to communication between users. Specifically, the behavioral history may include, for example, information about the person with whom a conversation took place, 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 piece of content was used together, or information about the number or frequency of content used together with a specific person. Here, using content together may mean, for example, playing a specific game together in the metaverse (e.g., teaming up or competing), 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 (e.g., information about conversations, sharing 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 with which each user has accessed (in other words, logged in to) the metaverse. The behavioral history may also include information regarding places visited within the metaverse, or information regarding the time at which a particular place was visited. In other words, the behavioral history may include information based on movement within the metaverse (for example, information regarding the distance traveled, places visited during movement, etc.).

The behavioral history within the metaverse can also be considered information about the operations performed by the user 5. Specifically, the behavioral history within the metaverse can also be considered information about the operations performed by the user 5 on the avatar object 6.

Recommendations to user 5 regarding specific things in the metaverse based on their behavioral 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 their behavioral 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 user 5's virtual space attributes based on user 5's behavioral history in the metaverse, and store user 5's virtual space attributes in user attribute storage unit 1752 included in memory module 1630. Furthermore, recommendation module 1731 may make recommendations to user 5 based on the virtual space attributes set for user 5, for example.

It is also possible for multiple in-virtual space attributes to be assigned to one user 5, or for only one in-virtual space attribute to be assigned to one user 5.

Virtual space attributes indicate the characteristics and qualities of User 5 within the Metaverse. Here, as an example, we will explain a case where virtual space attributes such as "active," "otaku," "fashionable," "gourmet," and "inactive" are set for User 5, but the types of virtual space attributes are not limited to these.

For example, as shown in FIG. 16, the attribute setting module 1732 may determine that user 5 is "active" and assign an "active" virtual space attribute to user 5 based on the following: the distance traveled in the metaverse is above a predetermined threshold (in other words, a predetermined level), the number or frequency of logins is above a predetermined threshold, the number or frequency of conversations with other users in the metaverse is above a predetermined threshold, the number of users with whom user conversed in the metaverse, the number of users with whom user used predetermined content in the metaverse, the number of users registered as friends, etc. are above a predetermined threshold. Note that conversations may be exchanges of text messages, voice calls, 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, whether the distance traveled within the metaverse, as indicated by user 5's behavioral history, is less than a predetermined threshold, whether the person with whom the user converses within the metaverse is mostly fixed, or whether the number or frequency of use of two-dimensional content such as anime, manga, and games is greater than a predetermined threshold.

Furthermore, the attribute setting module 1732 may determine that user 5 is "fashionable" and assign the virtual space attribute of "fashionable" to user 5, for example, based on whether the number or frequency of outfit changes within the metaverse, as indicated by user 5's behavioral history, is above a predetermined threshold, or the number of acquired clothing items (e.g., total number or number of types) is above a predetermined threshold.

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

In addition, the attribute setting module 1732 may determine that user 5 is "inactive" based on, for example, whether the distance traveled within the metaverse, as indicated by 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 virtual space attribute of "inactive" to user 5.

When setting an attribute based on some distance, number, frequency, etc. (in other words, when setting an attribute based on whether a certain parameter is above or below a certain level), the distance, number, frequency, etc. may be, for example, the total distance, total number, or frequency within a certain period of time, or the average distance, average number, or average frequency within a certain period of time. The certain period of time may be the period from when user 5 first accesses the metaverse to the time the attribute is determined, or it may be within a few days, a few months, or the period until the number of logins reaches a certain number. For example, setting a certain attribute based on a certain parameter being above a certain threshold does not impose any particular restrictions on the internal processing, as long as the certain attribute is assigned when the certain parameter is above a certain threshold.

The condition for setting a predetermined attribute for user 5 may be a single condition or multiple conditions. If multiple conditions are set, user 5's attribute may be determined based on one of the multiple conditions being satisfied, or may be determined based on multiple or all of the multiple conditions being satisfied. In this embodiment, a value for each virtual space attribute (hereinafter referred to as an "attribute value") is set for each condition, such as "a certain parameter being equal to or greater than a predetermined threshold," and when a certain condition is satisfied, attribute setting module 1732 assigns the user the attribute value set for that condition. Then, attribute setting module 1732 sets the virtual space attribute based on the cumulative value of the attribute values. In other words, an attribute in the virtual space is set for each action that user 5 can perform in the metaverse (in other words, each condition that can be achieved), and the attribute setting module 1732 assigns user 5 the attribute value of the attribute in the virtual space set for the action performed by user 5. 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 for user 5. Specifically, for example, when user 5's travel distance in the metaverse exceeds a predetermined threshold or when user 5's login frequency exceeds a predetermined threshold, the cumulative value of the attribute value of the attribute in the virtual space "active" increases. Furthermore, when user 5's travel distance in the metaverse exceeds a predetermined threshold, the cumulative value of the attribute value of the attribute in the virtual space "otaku" decreases. Furthermore, for example, when user 5 changes their outfit frequently in the metaverse exceeds a predetermined threshold, the cumulative value of the attribute value of the attribute in the virtual space "fashionable" increases. Then, for example, when the cumulative value of the attribute value for the virtual space attribute "active" reaches a predetermined value, the attribute setting module 1732 sets the virtual space attribute "active" for user 5.

Furthermore, each piece of content in the metaverse may have one or more virtual space attributes, and the attribute setting module 1732 may assign to user 5 the attribute value of the virtual space attribute of the content used (in other words, accessed) by user 5, depending on the virtual space attribute of the content used by user 5. 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 user 5. In such a case, a virtual space attribute is set for each action that user 5 may perform in the metaverse (e.g., using content with a virtual space attribute set), and the attribute setting module 1732 can be said to assign to user 5 the attribute value related to the virtual space attribute set for the action performed by user 5. In other words, some content in the metaverse has attributes set, and the attribute setting module 1732 may set a certain attribute to user 5 based on 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 content with a specific virtual space attribute set is equal to or exceeds a predetermined threshold. The setting information for the virtual space attributes related to content in the metaverse may be stored in advance in the memory module 1630 of the server 600, for example.

For example, there may be multiple locations in the metaverse that are assigned virtual space attributes, and the attribute setting module 1732 may assign to user 5 the attribute values of the virtual space attributes assigned to locations that user 5 has visited (in other words, used). In other words, the attribute setting module 1732 may assign to user 5 attribute values according to the locations that user 5 has visited. Specifically, for example, there may be multiple regions in the metaverse that are assigned virtual space attributes (specifically, for example, "virtual Shibuya" and "virtual Harajuku" that are assigned the virtual space attribute of "stylish," and "virtual Akihabara" that is assigned 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 assigned to a region based on user 5's visit to that region in the metaverse. Furthermore, for example, the metaverse may contain multiple facilities with virtual space attributes (specifically, for example, a commercial facility with the virtual space attribute "stylish," and a game center and mahjong parlor with the virtual space attribute "otaku"), and the attribute setting module 1732 may assign to user 5 the attribute value of the virtual space attribute assigned to that facility based on user 5's visit to that facility in the metaverse.

Furthermore, for example, multiple entertainments (e.g., games) each assigned a virtual space attribute may be provided in the metaverse, and the attribute setting module 1732 may assign to user 5 the attribute value of the entertainment that user 5 has used. For example, entertainments provided in the metaverse include mahjong, which is assigned the virtual space attribute of "otaku," karaoke, which is assigned the virtual space attribute of "active," and audiovisual content, each assigned a virtual space attribute. The attribute setting module 1732 may assign to user 5 the attribute value of the virtual space attribute assigned to a certain entertainment based on user 5's use (in other words, experience) of that entertainment in the metaverse.

Furthermore, for example, multiple events (e.g., music concerts, festivals, sporting events, etc.) with virtual space attributes are prepared within 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 a user 5 other users 5 (in other words, the avatars of the other users 5) who have virtual space attributes set that correspond to the virtual space attributes set for the user 5. Specifically, the recommendation module 1731 may perform the following processing, for example. That is, for example, as shown in FIG. 16, the recommendation module 1731 may recommend other users who have virtual space attributes set to "active" or "stylish" to a user who has the virtual space attribute set to "active." Also, for example, the recommendation module 1731 may recommend other users who have virtual space attributes set to "otaku" or "inactive" to a user who has the virtual space attribute set to "stylish." Also, for example, the recommendation module 1731 may recommend other users who have virtual space attributes set to "stylish" or "active" to a user who has the virtual space attribute set to "stylish." Furthermore, for example, the recommendation module 1731 may recommend other users who have set the virtual space attribute "gourmet" to a user who has set the virtual space attribute "gourmet." Furthermore, for example, the recommendation module 1731 may recommend other users who have set the virtual space attribute "inactive" or "otaku" to a user who has set the virtual space attribute "inactive."

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

Furthermore, the recommendation module 1731 may, for example, recommend to the user 5 other users 5 who have a specific relationship with the user 5 in the metaverse and things in the metaverse that have a specific association. Here, the other users 5 who have a specific relationship with the user 5 may, for example, be other users 5 who interact with the user 5. Furthermore, the other users 5 who interact with the user 5 may, for example, be 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. Furthermore, the other users 5 who have a specific relationship may, for example, be other users 5 who interact with the user 5 frequently (for example, other users 5 whose total number of interactions is greater than or equal to a predetermined threshold, or whose number of interactions within a predetermined period is greater than or equal to a predetermined threshold (i.e., high frequency of interactions)). Furthermore, the other users 5 who interact frequently may, for example, be other users 5 with whom the user 5 frequently converses or other users 5 with whom the user frequently uses content together. Furthermore, other users 5 having a specific relationship with user 5 may be, for example, other users 5 who share (e.g., the same) virtual space attributes or real-world attributes as user 5. Furthermore, things in the metaverse that have a specific relationship with other users 5 may be, for example, content in the metaverse (e.g., frequently visited facilities or frequently used games) that the other user 5 uses frequently (e.g., the total number of uses is greater than or equal to a predetermined threshold or the number of uses within a predetermined period is greater than or equal to a predetermined threshold (i.e., high usage frequency)), or users 5 (e.g., friends) who interact with the other user 5. In other words, the recommendation module 1731 may recommend to user 5 favorite content of the other user 5. The frequently used content of the other user 5 may be determined based on the behavioral history of the other user 5 in the metaverse (e.g., from the number of uses of each content indicated by the behavioral history). Furthermore, with regard to the number of interactions or number of uses, "high" may mean, for example, that the number of interactions or number of uses is relatively high among that user 5, or that the number of interactions or number of uses is higher than a predetermined threshold. In other words, when referring to a number equal to or greater than a predetermined threshold, the predetermined threshold may be fixed or variable (for example, variable depending on the number of interactions with each of multiple other users 5, the number of uses of each of multiple pieces of content, etc.).

Note that the attributes within the virtual space may be more specific. For example, the attributes within the virtual space may classify users 5 according to their hobbies and preferences. Furthermore, the attribute setting module 1732 may set the attributes within the virtual space of users 5 according to their usage history of content within the metaverse. For example, if each user is able to set background music within the metaverse, the attribute setting module 1732 may assign attributes such as "classical music lover," "rock lover," "pop music lover," or "anime song lover" to users 5 based on the type of background music they frequently use. Furthermore, the attribute setting module 1732 may assign the attribute "movie lover" to users 5 who frequently watch movies within the metaverse, or the attribute "mahjong lover" to users 5 who frequently play mahjong within the metaverse. Furthermore, the attribute setting module 1732 may assign the attribute "visited virtual Shibuya" to users 5 who have visited virtual Shibuya within the metaverse. Additionally, the attribute setting module 1732 may assign an attribute of "fan of a specific idol" to a user 5 who frequently uses content of that specific idol in the metaverse. Additionally, the attribute setting module 1732 may assign an attribute in the virtual space such as "street style," "fashion style," "natural style," or "rock style" to the user 5, depending on the type of outfit that the user 5 sets for their avatar in the metaverse (for example, the number of times or frequency that a specific type of outfit is worn).

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

The recommendation module 1731 may, for example, recommend other users who share the same behavioral history among multiple behavioral histories. Furthermore, the recommendation module 1731 may, for example, recommend to user 5 other users who share a common content usage history. For example, if the behavioral history of user 5 and the behavioral history of another user 5 indicate that multiple pieces of content that each user has 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 user 5 other users 5 who share characteristics in common with user 5, such as other users 5 with corresponding attributes or other users 5 with common behavioral histories.

[Recommendations for 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 also 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, for example, set real-world attributes for user 5 based on user 5's real-world behavior history, and store the real-world attributes of user 5 in user attribute storage unit 1752 included in memory module 1630. Furthermore, recommendation module 1731 may, for example, make recommendations to user 5 based on the real-world attributes set for that user 5.

It is also possible for multiple real-world attributes to be assigned to one user 5, or for only one real-world attribute to be assigned to one user 5.

Real-world attributes indicate the characteristics and traits of user 5 in the real world. Here, as an example, we will explain a case where real-world attributes such as "active," "otaku," "stylish," "gourmet," and "inactive" are set for user 5, but the types of real-world attributes are not limited to these. Furthermore, real-world attributes may also be more specific, as in the case of virtual space attributes. Note that the types of attributes included in virtual space attributes and real-world attributes may differ. In other words, virtual space attributes and real-world attributes may be classified differently.

For example, as shown in FIG. 16, the attribute setting module 1732 may determine that user 5 is "active" and assign the real-world attribute of "active" to user 5 based on the following information indicated in user 5's behavioral history: the distance traveled in the real world is equal to or greater than a predetermined threshold; the calories burned in the real world are equal to or greater than a predetermined threshold; the number or frequency of exercise sessions 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.

Furthermore, the attribute setting module 1732 may determine that user 5 is an "otaku" based on, for example, whether the distance traveled in the real world as indicated by 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 also determine that user 5 is "fashionable" and assign the real-world attribute of "fashionable" to user 5 based on, for example, whether the number or frequency of selfie posts on SNS, as indicated by user 5's behavioral history, is above a predetermined threshold, or whether the number or frequency of reactions (so-called likes, etc.) to fashion-related posts on SNS is above a predetermined threshold. The attribute setting module 1732 may also set the real-world attribute of user 5 to "street style," "fashion style," "natural style," "rock style," etc., depending on the user's tendency to dress in the real world (e.g., the number or frequency of wearing a particular type of outfit), as detected by, for example, image recognition of photos of user 5 in user 5's SNS posts, etc.

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

Furthermore, the attribute setting module 1732 may determine that user 5 is "inactive" and assign the real-world attribute of "inactive" to user 5 based on, for example, the fact that the distance traveled in the real world indicated by user 5's behavioral history 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.

When setting real-world attributes for 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 the actions taken by user 5, and set the real-world attributes based on the cumulative values, just 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 an attribute value of the real-world attribute of the place, service, or object used by the user 5, depending on the real-world attributes 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, the specific real-world attribute may be set for the user 5. In other words, some real-world things have attributes set, and the attribute setting module 1732 may set a certain attribute for the user 5 based on the user 5's use of a real-world thing with a certain attribute set. Note that setting information for 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, real-world attributes may be set for specific locations in the real world, and attribute setting module 1732 may assign user 5 the attribute value of the real-world attribute assigned to a location visited by user 5. Specifically, for example, there may be multiple 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 "stylish" is assigned, and "Akihabara" to which the real-world attribute of "otaku" is assigned), and attribute setting module 1732 may assign user 5 the attribute value of the real-world attribute assigned to a certain area in the real world based on user 5's visit to that area. Furthermore, for example, the real world may contain multiple facilities to which real-world attributes are assigned (specifically, for example, a commercial facility to which the real-world attribute "stylish" is assigned, a game center and 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.

Furthermore, for example, real-world attributes may be set for specific events in the real world (e.g., 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 that event based on user 5's participation in the real-world event.

For example, the recommendation module 1731 recommends to a user 5 other users 5 (in other words, avatars of other users 5) who have virtual space attributes set that correspond to the real-world attributes set for the user 5. Specifically, for example, the recommendation module 1731 may perform the following processing. That is, for example, as shown in FIG. 16 , the recommendation module 1731 may recommend other users 5 who have virtual space attributes set to "active" or "stylish" to a user 5 who has the real-world attribute set to "active." Also, for example, the recommendation module 1731 may recommend other users 5 who have virtual space attributes set to "otaku" or "inactive" to a user 5 who has the real-world attribute set to "stylish." Also, for example, the recommendation module 1731 may recommend other users 5 who have virtual space attributes set to "stylish" or "active" to a user 5 who has the real-world attribute set to "stylish." Furthermore, for example, the recommendation module 1731 may recommend other users 5 who have set the virtual space attribute "gourmet" to a user 5 who has set the real world attribute "gourmet." Furthermore, for example, the recommendation module 1731 may recommend other users 5 who have set the virtual space attribute "inactive" or "otaku" to a user 5 who has set the real world attribute "inactive."

Furthermore, recommendation module 1731 may recommend to user 5, for example, content in the metaverse that corresponds to the real-world attributes set for user 5. Specifically, for example, content in the metaverse may have recommended attributes set to indicate which attributes of user 5 the content is recommended to, and recommendation module 1731 may recommend to user 5 content that has recommended attributes set to correspond to the real-world attributes set for user 5. That is, for example, content in the metaverse may have recommended attributes such as "active," "otaku," "fashionable," "gourmet," and "inactive," and the content may be recommended to user 5 that has real-world attributes that match the recommended attributes set for the content. More specifically, for example, recommendation module 1731 may recommend content that has recommended attributes set to "active" to a user that has a real-world attribute set to "active."

Note that in this embodiment, the attribute setting module 1732 sets real-world attributes for user 5 based on user 5's behavioral history in the real world, and the recommendation module 1731 recommends specific things in the metaverse to user 5 based on the real-world attributes. However, the recommendation module 1731 may make recommendations based on behavioral history without the attribute setting module 1732 setting real-world attributes. Specifically, for example, if there is a place in the metaverse that corresponds to a specific place in the real world (e.g., a specific facility in virtual Shibuya that imitates a specific facility in real Shibuya), and user 5's behavioral history in the real world indicates that the specific place is frequently visited (in other words, if the behavioral history itself indicates user 5's attribute of frequently visiting the specific place; in other words, if the specific place is frequently used), the recommendation module 1731 may recommend to user 5 a place in the metaverse that corresponds to the specific place.

Furthermore, recommendations regarding specific things in the metaverse based on user 5's behavioral history in the real world may be as follows. That is, for example, the behavioral history may be a history of user 5's searches using the user device 700 described below (e.g., searches using a specific web browser, etc.), or a history of product purchases (e.g., purchase history on a specific e-commerce site, etc.). Then, recommendation module 1731 may recommend a music concert in the metaverse, for example, if user 5's behavioral history in the real world indicates, for example, that a search for music concerts has been conducted or that a musical instrument has been purchased on a specific e-commerce site.

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, if the history of credit card usage as user 5's behavioral history in the real world indicates that user 5 has purchased home appliances.

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

Recommendations of specific real-world objects to user 5 based on behavioral history within the metaverse may be performed, for example, as follows. That is, attributes within 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 within the virtual space.

The recommendation module 1731, for example, recommends to a user 5 real-world objects (e.g., places, services, objects, etc.) that correspond to the virtual space attributes set for the user 5. Specifically, for example, some real-world objects have recommendation target attributes set that indicate which users the objects are recommended to, and the recommendation module 1731 may recommend to a user 5 objects that have recommendation target attributes that correspond to the virtual space attributes set for the user 5. That is, for example, some real-world objects have recommendation target attributes such as "active," "otaku," "stylish," "gourmet," and "inactive," and the objects may be recommended to a user 5 that has virtual space attributes that match the recommendation target attributes set for the objects. More specifically, for example, the recommendation module 1731 may recommend real-world services, facilities, etc. that have the recommendation target attribute "active" set for a user with the virtual space attribute set to "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.

Furthermore, the metaverse may contain multiple pieces of content that are associated with (in other words, related to) real-world objects, and recommendation module 1731 may recommend an object associated with a specific piece of content based on user 5's access to that specific piece of content. Information indicating the correspondence between real-world objects and content within the metaverse may be stored in advance in memory module 1630 of server 600, for example. Here, content associated with a real-world object may be, for example, a place within the metaverse that is modeled after (e.g., a region or facility) an actual place in the real world. Specifically, for example, if a virtual facility modeled after a specific real-world facility exists within a virtual town modeled after a specific real-world town, recommendation module 1731 may recommend the specific facility to user 5 based on user 5's visit to the virtual facility within the metaverse.

Furthermore, content associated with real-world events may be, for example, events in the metaverse that are similar to events that actually exist in the real world. Specifically, for example, if a music concert similar to a specific music concert held in the real world is held in the metaverse (for example, a concert with a similar musical genre or a concert featuring the same artist), 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 (for example, actual participation or reservations to participate).

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

Note that while there may be a one-to-one correspondence between real-world objects and each piece of content in the metaverse, it does not have to be. In other words, multiple pieces of content in the metaverse may be associated with one real-world object, or one piece of content in the metaverse may be associated with multiple real-world objects. For example, there may be multiple casinos in the metaverse, and these casinos may be associated with one casino in the real world. Or, there may be one casino in the metaverse, and this casino may be associated with multiple casinos in the real world.

Note that recommendations regarding specific real-world objects based on user 5's behavioral history within the metaverse may be as follows. That is, for example, the behavioral history may be a history of shopping within the metaverse. Then, for example, if user 5's behavioral history within the metaverse indicates the purchase of a specific product that can be used within the metaverse (e.g., clothing to be worn by an avatar, furniture to be placed in a house within the metaverse, etc.), recommendation module 1731 may recommend real-world products related to the specific product. More specifically, for example, recommendation module 1731 may change the real-world products displayed as recommended products to user 5 on the website of a real-world store associated with a specific store, depending on the products that user 5 purchased at the specific store within the metaverse.

The recommendation module 1731 may also recommend real-world behavior (e.g., recommended behavior) based on the behavioral history of the user 5 within the metaverse. Specifically, the recommendation module 1731 may recommend exercise in the real world based on the fact that the user 5 has moved little within 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 habits in the real world based on the user's behavioral history within 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 user's behavioral history within the metaverse.

The recommendation module 1731 may also recommend to user 5, for example, real-world objects that have a specific relationship with other users who have a specific relationship with user 5 in the metaverse. Real-world objects that have a specific relationship with other user 5 may be, for example, real-world objects that other user 5 uses frequently (e.g., frequently visited facilities or frequently used services). The real-world objects that other user 5 uses frequently may be determined based on the user's real-world behavioral history (e.g., from the number of times each facility or service is used as indicated by the behavioral history). Real-world objects that have a specific relationship with other user 5 may also be, for example, real-world objects that correspond to content in the metaverse that other user 5 uses frequently. Other users 5 with a specific relationship are as described above. With this configuration, for example, if another user 5 who has a specific relationship with user 5 in the metaverse (e.g., frequently interacts with user 5) frequently participates in a specific live event in the metaverse, it may be possible to recommend to user 5 a real-world live event that corresponds to the specific live event. Therefore, it will be possible to extend relationships that exist only within the metaverse to the real world.

In the metaverse, users 5 may be able to visually recognize at least one of their own virtual space attributes or real-world attributes. In the metaverse, users 5 may also be able to visually recognize at least one of other users 5's virtual space attributes or real-world attributes. Specifically, for example, the avatar control module 1429 may reflect the user 5's attributes in the avatar object 6 and control the avatar object 6 to be displayed on the monitor 130 in a display mode that reflects the attributes. Reflecting the attributes in the avatar object 6 may involve changing the skin (e.g., clothing) of the avatar object 6 in accordance with the attributes. Reflecting the attributes in the avatar object 6 may also involve adding a display (e.g., an icon) indicating the attributes to the avatar object 6 around the avatar object 6 (e.g., above the head). In other words, reflecting the attributes in the avatar object 6 may involve setting the display mode of the avatar object 6 to a display mode in which an object (e.g., clothing, icon, etc.) corresponding to the attributes is added to the avatar object 6. Furthermore, the attributes may be displayed (e.g., indicated by letters, symbols, etc.) on a screen (such as a so-called profile screen) that displays a list of information about the user 5. Furthermore, for example, if 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 the existence of the gap may be displayed. Specifically, the display mode of the avatar object 6 may change to a display mode indicating the existence of the gap (e.g., a display mode in which an icon indicating the existence of the gap is displayed above the head of the avatar object 6), or a display indicating the existence of the gap may be displayed on a profile screen, etc. Each user 5 may be able to set whether or not to visually indicate the attributes or gaps to other users 5. Furthermore, for example, when reflecting attributes to the avatar object 6, the reflection may be performed automatically or based on an operation by 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, attributes of user 5 that are set based on behavioral history within the metaverse (i.e., attributes within the virtual space) and attributes of user 5 that are set based on behavioral history in the real world (i.e., attributes within the real world) are managed separately. However, attributes that are set based on behavioral history within the metaverse and attributes that are set based on behavioral history in the real world do not necessarily need to be distinguished. In other words, the attributes within the virtual space and the attributes within the real world in this embodiment may both be read simply as "attributes."

The behavioral history of 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 be equipped with a behavioral history acquisition module 1733. Furthermore, the behavioral history acquisition module 1733 may acquire information about the behavioral history of user 5 in the real world from, for example, a device carried by user 5 as external equipment 700 (hereinafter referred to as "user device 700"), and store the behavioral history of user 5 in the real world in the real-world history storage unit 1753 provided in the memory module 1630 based on the acquired information. Here, the device carried by user 5 may be, for example, a smartphone, feature phone, PDA (Personal Digital Assistant), tablet computer, personal computer, etc., or a device worn by user 5 (for example, a wearable device such as a watch, wristband, ring, clothing, glasses, or contact lens, or an implantable device), etc.

The behavioral history acquisition module 1733 may acquire, as behavioral history, information about the distance traveled by user 5, information about places visited by user 5, and information about services used by user 5, based on location information indicating the location of user 5 acquired by the user device 700 via GPS or a predetermined wireless communication (e.g., 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, for example, information about user 5's actions on SNS (e.g., information about images posted, information about the date and time of posting, information indicating the content of the post, information about posts to which users reacted, etc.) from the user device 700, and based on this information, acquire, as behavioral history, information about places visited by user 5, information about services used by user 5, and information about clothing worn by user 5. The behavioral history acquisition module 1733 may also acquire, for example, from the user device 700, a history of user 5's web browser searches, a history of product purchases, etc. Additionally, the behavioral history acquisition module 1733 may acquire these histories as behavioral history from a predetermined server that stores history of the use of a predetermined application on the user device 700, a predetermined server that stores history of the use of user 5's credit card, etc.

The behavioral history acquisition module 1733 may also acquire behavioral history based on, for example, information related to biometric information acquired by the user device 700. Here, the biometric information may be, for example, data such as heart rate, blood pressure, body temperature, blood oxygen level, exhaled air, sweat rate, number of steps, electrocardiogram, or brain waves 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 just exercised), information indicating the amount of sleep, or information indicating a full stomach, which is obtained by analyzing the biometric information. The behavioral history acquisition module 1733 may also acquire, as behavioral history, information related to the number or frequency of exercises performed by the user 5, information related to the calories burned by the user 5, or information related to the amount of sleep the user 5 has.

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 healthcare application or a household accounting application of the user device 700. In other words, the behavioral history may be acquired in real time in accordance with the user 5's behavior, or may be acquired by the user 5 manually inputting specified information after performing the behavior.

The control module 1610 also includes a collaboration management module 1741 that manages information regarding collaboration with the user device 700 of each user 5. The collaboration management module 1741 (in other words, a collaboration information registration means) registers information regarding collaboration with the user device 700 used by the user 5 based on the user's 5 operation (e.g., operation by the controller 300, operation on the user device 700, etc.). Here, the information regarding collaboration with the user device 700 may be information indicating the user device 700 used by the user 5 (e.g., a wearable device, etc.). In other words, the information regarding collaboration with the user device 700 may be information indicating the user device 700 that the user 5 has authorized for collaboration. The information regarding collaboration with the user device 700 may also be information regarding collaboration between an application in the user device 700 (e.g., an application that acquires biometric information, an SNS application, etc.) and an application that provides the metaverse. In other words, the information regarding the collaboration with the user device 700 may be information indicating applications in the user device 700 that the user 5 has authorized to collaborate (in other words, applications that can be used on the user device 700). That is, the information regarding the collaboration with the user device 700 can also be considered information regarding permission to acquire information regarding the user 5's behavioral history in the real world via the user device 700. The collaboration management module 1741 stores information regarding the collaboration with the user device 700 in the memory module 1630 based on an operation by the user 5. Furthermore, when the collaboration management module 1741 registers the information regarding the collaboration with the user device 700, the behavior history acquisition module 1733 can acquire the behavioral history of the user 5 based on the information acquired by the user device 700. In other words, when the information regarding the collaboration 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. Furthermore, the collaboration management module 1741 (in other words, the notification means) notifies a user 5 who has not registered information regarding collaboration with the user device 700 to prompt them to register information regarding collaboration with the user device 700. Specifically, for example, the collaboration management module 1741 notifies the user 5 that by allowing collaboration with the user device 700, predetermined recommendations will be made. More specifically, for example, the collaboration management module 1741 transmits information indicating that information regarding collaboration with the user device 700 has not been registered to the control module 510 of the user's computer 200. Furthermore, upon receiving this information, the control module 510 displays on the monitor 130 a display informing the user 5 that collaboration with the user device 700 has not been established, or a display informing the user 5 that by allowing collaboration with the user device 700, recommendations regarding predetermined things in the metaverse will be made based on their behavioral history in the real world.

Whether or not to allow the behavioral history acquisition module 1733 to acquire behavioral history (in other words, whether or not to permit it) may be configurable (in other words, switchable between ON and OFF) based on the operation of the user 5. For example, the behavioral history acquisition module 1733 may determine whether or not to acquire behavioral history based on setting information (specifically, setting information regarding whether or not to acquire behavioral history) set by the operation of the user 5 (e.g., operation of the controller 300 on a predetermined setting screen). Furthermore, whether or not to acquire behavioral history may be configurable for each behavioral history acquisition path. Specifically, for example, a setting may be possible such that acquisition of behavioral history from the user device 700 is permitted while acquisition of history related to credit card usage is not permitted. In other words, it may be configurable for each user as to which of multiple media (e.g., the user device 700, credit card, etc.) the behavioral history acquisition module 1733 is permitted to acquire behavioral history from. Furthermore, whether or not recommendation module 1731 is to make various recommendations based on various behavioral histories (in other words, whether or not to permit such recommendations) may be configurable (in other words, switchable between ON and OFF) based on an operation by user 5. For example, recommendation module 1731 may determine whether or not to make a recommendation based on setting information (specifically, setting information regarding whether or not to make a recommendation) set by an operation by user 5 (for example, an operation by controller 300 on a predetermined setting screen). Furthermore, whether or not to make a recommendation may be configurable for each thing to be recommended. With such a configuration, for example, in a configuration in which recommendations regarding things in the metaverse are made based on behavioral history in the real world, it becomes possible to switch recommendations regarding things in the metaverse ON and OFF, thereby preventing 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 a thing in the metaverse or the real world to recommend to user 5 based on user 5's behavioral history in the metaverse or the real world, it outputs recommendation information indicating that thing and transmits it to recommendation information presentation module 1721. Furthermore, recommendation information presentation module 1721 displays a display recommending that thing (hereinafter referred to as "recommendation display 30") on monitor 130 based on the recommendation information from recommendation module 1731.

An example of a recommendation display 30 is shown in Figure 17. Figure 17 shows an example display when recommending content and other users 5 in the metaverse based on behavioral history in the real world. As shown in Figure 17, the recommendation information presentation module 1721 may cause the monitor 130 to display a recommendation display 30 including a display of the name of the recommended content, etc. Also, as shown in Figure 17, the recommendation information presentation module 1721 may cause the monitor 130 to display a recommendation display 30 including a display of the name in the metaverse of the other user 5 being 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., username). Note that the recommendation display 30 related to the recommendation of another user 5 may include, for example, a display related to the receipt of contact for the other user 5 or a display indicating the location of the other user 5 in the metaverse. Also, a recommendation display recommending content in the metaverse may include, for example, a display indicating the location of a location related to the content (e.g., the location of a facility representing the content, or the location of a place where a service representing the content is available, etc.). Note that the recommendation display 30 when recommending content or other users within the metaverse based on behavioral history within the metaverse may also be as illustrated in FIG. 17. Note that the recommendation display 30 may be displayed across the entire display area of the monitor 130, or may be displayed in only a portion of the display area.

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

As shown in FIG. 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 item or the price of the recommended service, etc.). The recommendation display 30 may also include a display indicating the location of a location related to the recommended thing. Here, the display indicating the location may be, for example, a text display such as an address, or a map display. The recommendation display 30 may also include a display related to accepting reservations for the recommended thing. In other words, while the recommendation display 30 is displayed, an operation by the user 5 related to making a reservation for the recommended thing (e.g., an operation using the controller 300 or an operation using eye contact, etc.) may be accepted. The recommendation display 30 may also include a display related to accepting an operation to set the location related to the recommended thing as an actual destination in the real world. In other words, when the recommendation display 30 is displayed, the user 5 may receive an operation (e.g., an operation using the controller 300 or an operation using a line of sight) to set a location related to the recommended object as a destination to be traveled to in the real world. The recommendation display 30 may also include a display for accepting addition of the recommended object to a predetermined list. In other words, when the recommendation display 30 is displayed, the user 5 may receive an operation (e.g., an operation using the controller 300 or an operation using a line of sight) to add the recommended object to a predetermined list. Here, the predetermined list may be, for example, a list for registering candidate locations to be visited in the future, a list for registering a location to be traveled to now, or a list for registering items to be purchased. The predetermined list may be viewable using a predetermined application on the user device 700. When the recommendation display 30 is displayed and the user receives an operation for setting a location related to the recommended object as a destination to be traveled to in the real world, the location 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.

Furthermore, when the recommendation module 1731 determines a thing in the metaverse or the real world to recommend to user 5 based on user 5's behavioral history 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 real-world thing recommended to user 5 by the recommendation module 1731 may be presented to user 5 on the user device 700 (e.g., a smartphone, a wearable device, etc.), or may be presented to user 5 in the metaverse. Furthermore, 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, a recommendation display 30 is displayed on the user device 700, and an operation related to making a reservation for the recommended thing, an operation related to setting a location related to the recommended thing as a destination to actually travel to in the real world, or an operation related to adding the recommended thing to a predetermined list is accepted. Based on each operation, the recommendation information may be registered in an application (e.g., a calendar application) that manages the reservation date and time or the date and time to travel to the destination, an application that manages the predetermined list, a navigation application, etc. Furthermore, when recommendation information recommending a predetermined thing in the real world is sent to the user device 700, the user device 700 may store the recommendation information 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), send a predetermined notification to the user 5. Here, the predetermined notification may be, for example, a notification notifying the user that the user is approaching the predetermined thing, a notification notifying the user that the user has arrived at the predetermined thing, a notification notifying the user that detailed information about the predetermined thing has been provided, or the like. 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 obtained by the user device 700 using GPS or the like. Furthermore, when the user 5 actually visits a location related to the recommended thing, the user device 700 may detect that the user 5 has visited the location and transmit information notifying the user 5 of the visit to the server 600. Then, the control module 1610 may grant the user 5 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) based on this information (in other words, based on the user 5 having taken an action in accordance with 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 to request a recommendation (for example, an operation to request the display of recommendation display 30) on a menu screen displaying multiple menu items (in other words, a user interface displayed on monitor 130). Note that the timing of making a recommendation here refers to the timing when information related to the recommendation is provided to user 5 (for example, the timing when recommendation display 30 is displayed to user 5), but may also refer to the timing when recommendation module 1731 decides on the item to recommend.

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

Recommendations may also be made when user 5 accesses the metaverse. That is, for example, recommendations may be made when user 5 puts on the HMD 120 and launches an application for accessing the metaverse. Specifically, recommendations may be made, for example, after the application for accessing the metaverse is launched and before user 5 is able to operate the avatar object 6. As an example, recommendations may be made on a screen (e.g., a so-called home screen) on which settings related to the metaverse space are configured. This configuration provides the following advantages, for example, when recommending things in the metaverse based on user 5's behavioral history in the real world. That is, when user 5 accesses the metaverse for the first time in a while, user 5 is shown in a clear manner that their real-world actions will be reflected in the metaverse space. This gives user 5 a sense of connection with the metaverse even during periods of inactivity, thereby eliminating psychological barriers to re-accessing the metaverse. Furthermore, when recommendations regarding things in the metaverse are made based on user 5's behavioral history in the real world, recommendations may be made when the metaverse is accessed for the first time. In this case, for example, the recommendation may be made after 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 user 5 should do first when starting activities in the metaverse, tailored to the characteristics of user 5.

Recommendations may also be made when user 5 accesses specific content in the metaverse. For example, when recommending a real-world object corresponding to specific content in the metaverse, or when recommending an object in the metaverse corresponding to specific content in the metaverse, the recommendation may be made when user 5 accesses the specific content. For example, as shown in FIG. 18 , if a virtual facility based on a specific real-world facility exists in a virtual town based on a specific real-world town, when user 5 visits the virtual facility in the metaverse (specifically, when user 5 visits a location where the virtual facility is visible or enters the virtual facility), recommendation module 1731 may recommend the specific real-world facility to user 5. Note that when making recommendations to user 5 using the display shown in FIG. 18 or the like, the recommendation may be, for example, as follows: That is, recommendation module 1731 and/or recommendation information presentation module 1721 may recommend different objects to user 5 based on where user 5 is located in the metaverse. Furthermore, 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-world town, the recommendation information presentation module 1721 may cause the monitor 130 to display a recommendation display 30 recommending a real facility corresponding to a virtual facility in the virtual town. In other words, the recommendation module 1731 may recommend a predetermined thing in the real world or the metaverse based on the user 5's current location in the metaverse (in other words, a predetermined thing corresponding to the current location). Furthermore, for example, when the user 5 is looking at a first virtual facility 31, the recommendation information presentation module 1721 may cause the monitor 130 to display a recommendation display 30 recommending a real facility corresponding to the first virtual facility 31. Furthermore, for example, when user 5 is looking at second virtual facility 32, recommendation information presentation module 1721 may display recommendation display 30 on monitor 130 recommending a real facility corresponding to second virtual facility 32. In other words, recommendation module 1731 may recommend a specific object in the real world or metaverse (in other words, a specific object corresponding to the location) based on the location where user 5 is looking in the metaverse. Note that the location where user 5 is looking (in other words, which facility, etc.) may be determined based on field of view image 17, or may be determined based on user 5's line of sight identified based on a signal from gaze sensor 140. Specifically, for example, the area shown in field of view image 17 may be determined as the location where user 5 is looking, or a specific range based on the point where user 5's line of sight may be determined as the location where user 5 is looking.

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

The control module 1610 of this embodiment also includes an access control module 1734 that controls whether or not access is permitted to specific content within the metaverse. When the recommendation module 1731 recommends specific content to user 5, the access control module 1734 allows user 5 to access the specific content. Specifically, for example, the metaverse may include a location (e.g., an area or facility) that user 5 cannot enter unless recommended. In this case, the access control module 1734 may allow user 5 to enter (i.e., access) the location based on the recommendation of the location to user 5 by the recommendation module 1731. Also, for example, the metaverse may include a service that user 5 cannot use unless recommended. In this case, the access control module 1734 may allow user 5 to use (i.e., access) the service based on the recommendation of the service to user 5 by the recommendation module 1731. Also, for example, the metaverse may include an item that user 5 cannot acquire (e.g., purchase) unless recommended. In this case, the access control module 1734 may, for example, enable user 5 to acquire (i.e., access) an item based on a recommendation of the item to user 5 by the recommendation module 1731. In this way, enabling access to recommended items based on recommendations can increase motivation and a sense of purpose for activities within the metaverse or in the real world.

In addition, 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 specific spaces within the metaverse if the users 5 have specific attributes. With this configuration, it is possible to provide spaces within the metaverse where similar users 5 can gather.

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

[Processing related to recommendation of 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 the description here will be made taking as an example a case where recommendations are made to user 5A.

First, we will explain an example of a process for recommending other users based on their behavioral history within the metaverse, with reference to Figure 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 within the metaverse stored in the virtual space history storage unit 1751.

Next, in step S102, the recommendation module 1731 determines other users 5 to recommend to user 5A based on user 5A's attributes in the virtual space. Specifically, the recommendation module 1731 extracts other users 5 who have attributes in the virtual space that correspond to user 5A's attributes in the virtual space from among multiple users 5 who use the metaverse, and determines them as other users 5 to recommend to user 5A. Here, as an example, it is assumed that user 5C has been determined as the other user 5 to recommend to user 5A. Note that the recommendation module 1731 may preferentially extract other users 5 with highly relevant attributes (e.g., users 5 with a large number of corresponding attributes). Furthermore, the recommendation module 1731 may preferentially extract other users 5 who are highly relevant to the user 5's location in the metaverse as indicated by his or her behavioral history in the metaverse (e.g., other users 5 who are currently nearby, other users 5 with a similar range of behavior, other users 5 who frequently visit the same places, etc.). Furthermore, the recommendation module 1731 may preferentially extract other users 5 who are highly relevant to the user 5's location in the real world as indicated by the user's 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 places, etc.).

Next, in step S103, the recommendation module 1731 transmits recommendation information about another user 5C to be recommended to 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 another user 5C to user 5A.

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

Next, we will explain an example of a process for recommending content within the metaverse based on behavioral history within the metaverse, with reference to Figure 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 within the metaverse stored in the virtual space history storage unit 1751.

Next, in step S152, the recommendation module 1731 determines content in the metaverse to recommend to user 5A based on user 5A's attributes in the virtual space. Specifically, the recommendation module 1731 extracts content having recommendation target attributes that correspond to user 5A's attributes in the virtual space from among multiple pieces of content in the metaverse, and determines this content as the content to recommend to user 5A. Note that the recommendation module 1731 may preferentially extract content that is highly relevant to user 5A's location in the metaverse as indicated by their behavioral history in the metaverse (e.g., content close to the current location or content within user 5A's range of activity). The recommendation module 1731 may also preferentially extract content that is highly relevant to user 5A's location in the real world as indicated by their behavioral history in the real world (e.g., content corresponding to real-world locations close to the current location or content corresponding to real-world locations within user 5A's range of activity).

Next, in step S153, the recommendation module 1731 transmits recommendation information regarding the content to be recommended to 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 specific content to user 5A.

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

[Processing related to recommendation of 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 the description here will be made taking as an example a case where recommendations are made to user 5A.

In step S201, the behavioral history acquisition module 1733 acquires the real-world behavioral history of user 5A based on information about user 5A's behavior in the real world. Here, the information about 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. Furthermore, the information about user 5A's behavior in the real world may be, for example, information about user 5A's actions on SNS. Furthermore, the information about user 5A's behavior in the real world may be, for example, location information indicating user 5A's location in the real world. Such information about 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 user 5A's actions on SNS may be sent to the control module 1610 from a server that provides the SNS, etc. Note that actions on SNS include posting on SNS and reacting (such as liking) 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 what objects in the metaverse to recommend to user 5A based on user 5A's real-world attributes. Specifically, the recommendation module 1731 extracts content having recommendation target attributes that correspond to user 5A's real-world attributes from among multiple pieces of content in the metaverse, and determines the content to recommend to user 5A. Note that the recommendation module 1731 may preferentially extract content that is highly relevant to the real-world location of user 5A indicated by the user's real-world behavior history (e.g., content corresponding to a real-world location close to the user's current location, or content corresponding to a real-world location within the user's 5A's range of activity, etc.). The recommendation module 1731 may also preferentially extract content that is highly relevant to the user's location in the metaverse indicated by the user's behavior history in the metaverse (e.g., content close to the user's current location, or content within the user's 5A's range of activity, etc.).

Next, in step S204, the recommendation module 1731 transmits recommendation information regarding the thing (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 thing in the metaverse to the user 5A.

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

[Processing related to recommendation of 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 the description here will be made taking as an example a case where recommendations are made to user 5A.

In step S301, the recommendation module 1731 identifies a real-world object that corresponds to the content in the metaverse accessed by user 5A. The recommendation module 1731 then determines the identified object as the object to be recommended to user 5A. Specifically, the recommendation module 1731 identifies the content accessed by user 5A based on user 5A's behavioral history, and determines the real-world object that corresponds to the content accessed by user 5A based on information indicating the correspondence between real-world objects and 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 the object to be recommended to user 5A based on user 5A's access to a virtual facility based on the specific facility in the real world. Note that the recommendation module 1731 may, for example, determine the specific facility as the object to be recommended when user 5A accesses the virtual facility in the metaverse. Furthermore, the recommendation module 1731 may, for example, determine as the thing to recommend, from among a plurality of pieces of content that the user 5A has accessed (specifically, a plurality of pieces of content to which corresponding real-world things are set), a real-world thing that corresponds to content that has been used frequently by the user 5A (for example, the total number of times used is equal to or exceeds a predetermined threshold, or the number of times used within a predetermined period is equal to or exceeds a predetermined threshold (i.e., high frequency of use)) at the time of displaying the recommendation display 30 to the user 5A.

Next, in step S302, the recommendation module 1731 transmits recommendation information regarding a specific facility in the real world to be recommended to 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 user 5A. Note that the recommendation module 1731 may also transmit recommendation information regarding a real-world object to be recommended to user 5A to the user device 700 of user 5A.

Next, in step S303, the recommendation information presentation module 1721A displays on the monitor 130A 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.

The present invention is not limited to the above-described embodiment, and various modifications can be made 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. Furthermore, the processing flow described in this specification is merely an example, and the order and configuration of each process may be different.

[Note]
The matters described in the above embodiment can also be described as follows:

(Appendix 1)
Computer,
A program that functions as a recommendation means (e.g., recommendation module 1731) that makes recommendations to a user regarding predetermined things in the metaverse based on the user's behavioral history in the metaverse.
This configuration makes it possible to recommend other users and content that suit each user based on the characteristics of the user as revealed in the user's behavior, thereby broadening the scope of user activities within the metaverse and improving the interest of the service.

(Appendix 2)
The program described in Appendix 1, wherein the recommendation means recommends to the user other users who have characteristics in common with the user based on the user's behavioral history in the metaverse and the behavioral history of other users in the metaverse.
This configuration allows users to be introduced to other users who share common characteristics, thereby helping to expand friendships within the metaverse and increasing the interest of the service.

(Appendix 3)
The program according to claim 1, wherein the recommendation means recommends content in the metaverse to the user.
This configuration makes it possible to introduce content that is suited to each user, thereby broadening the scope of user activities within the metaverse and increasing the interest of the service.

(Appendix 4)
The program described in Appendix 1, wherein the recommendation means makes recommendations to the user regarding things in the metaverse that have a specific association with other users who interact with the user in the metaverse.
Things that have a specific relationship with other users who interact with the user are likely to interest the user. With this configuration, it is possible to recommend to the user things that are likely to interest the user. It is also possible to create opportunities to deepen interactions with the other users. This can therefore improve the interest of the service.

(Appendix 5)
The program according to claim 4, wherein the recommendation means recommends to the user content in the metaverse that has been used by other users who have interactions with the user a predetermined threshold or more.
This configuration allows the user to be recommended content that is popular with other users with whom the user interacts, thereby broadening the scope of user activities within the metaverse and increasing the interest of the service.

(Appendix 6)
The computer is further caused to function as an attribute setting means (e.g., an attribute setting module 1732) that sets attributes to the user according to the user's behavior history,
The program according to claim 1, wherein the recommendation unit recommends, to the user, other users corresponding to the set attribute.
This configuration allows users to be classified into attributes based on their behavioral history, and to recommend other users with matching attributes or compatible attributes to the user, etc. This can broaden the range of user activities within the metaverse and improve the interest of the service.

(Appendix 7)
The computer is further caused to function as an attribute setting means (e.g., an attribute setting module 1732) that sets attributes for the user according to the user's behavior history,
The program according to claim 1, wherein the recommendation means recommends content in the metaverse according to the attribute to the user.
This configuration allows users to be classified into attributes based on their behavioral history and to recommend content that matches their attributes to them, thereby broadening the scope of user activities within the metaverse and increasing the interest of the service.

(Appendix 8)
The computer is further configured to function as an access control means (e.g., an access control module 1734) that controls whether or not access is permitted to specific content within the metaverse;
The program according to any one of claims 3, 5 and 7, wherein the access control means enables the user to access the specific content based on the recommendation of the specific content to the user by the recommendation means.
This configuration makes it possible to provide content that can be accessed through recommendations, thereby increasing motivation and a sense of purpose for activities within the metaverse, and thus improving the interest of the service.

(Appendix 9)
The user's behavioral history includes information based on at least one of communication between the user and other users within the metaverse and movement of the user within the metaverse.
With this configuration, it is possible to make recommendations based on the characteristics of a user that are manifested in the user's communication with other users or movements within the metaverse.

(Appendix 10)
An information processing system comprising a recommendation means (for example, a recommendation module 1731) that makes recommendations to a user regarding predetermined things in the metaverse based on the user's behavior history in the metaverse.
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 gaze identification module, 1424 Facial 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, 1732: Attribute setting module, 1733: Behavior history acquisition module, 1734: Access control module, 1741: Collaboration management module, 1751: Virtual space history storage unit, 1752: User attribute storage unit, 1753: Real-world history storage unit

Claims (4)

Computer,
The system functions as a recommendation means for recommending a specific place to a user based on information about the use of a specific place in the metaverse by other users who have a specific relationship with the user ;
The other user is a user whose conversation with the certain user or use of content in the metaverse satisfies a predetermined condition.
program. Computer,
attribute setting means for setting attributes indicating the characteristics or properties of a certain user to the certain user based on the user's behavior history in the metaverse ;
and functioning as a recommendation means for recommending a specific place to a certain user based on information about the use of the specific place in the metaverse by another user to whom an attribute corresponding to the attribute set for the certain user is set.
program . a recommendation means for recommending a specific place in the metaverse to a certain user based on information about the use of the specific place by another user having a specific relationship with the certain user ;
The other user is a user whose conversation with the certain user or use of content in the metaverse satisfies a predetermined condition.
Information processing system. attribute setting means for setting attributes indicating the characteristics or properties of a certain user to the certain user based on the user's behavior history in the metaverse;
and a recommendation means for recommending a specific place to the certain user based on information about a specific place in the metaverse that has been used by another user to whom an attribute corresponding to the attribute set for the certain user has been set.
Information processing system.