Event management system, event management device, event management method, and program

Abstract

To provide an event management system, an event management device, an event management method, and a program that a participant participating in one space first is able to participate in a prescribed event without performing any participation processing to the other space when the prescribed event is executed in a state that a physical space and a virtual space are associated with each other.SOLUTION: A generation part of an event management server 6 generates a notification including an event name for displaying an event participation dialogue, a participant name in an event, necessary URL information required for a connection request to a virtual reality hybrid event described later, and a necessary event ID required for an event participation request described later, as an event participation notification (step S87). A transmission / reception part transmits the generated event participation notification to a communication terminal 3 (step S88).SELECTED DRAWING: Figure 23B

Description

[Technical field]

[0001] The present invention relates to an event management system, an event management device, an event management method, and a program. [Background technology]

[0002] In recent years, technology has become known that allows participants in a physical space and avatars in a virtual space (virtual reality space) to participate in the same online conference by using an app on a communication terminal present in the physical space. References: https: / / news.microsoft.com / ja-jp / 2021 / 11 / 04 / 211104-mesh-for-microsoft-teams /

[0003] For example, a technique is known for participating in a virtual conference from a display in order to show the reactions of participants (see Patent Document 1). Summary of the Invention [Problem to be solved by the invention]

[0004] However, in conventional technology, when a specific event is carried out in a state in which a physical space and a virtual space are associated with each other, participants who first join one space must carry out some sort of joining process for the other space, which is time-consuming. [Means for solving the problem]

[0005] In order to solve the above-mentioned problems, the invention of claim 1 provides an event management system having a first communication terminal that exists in a physical space and is used to execute a specified event, a second communication terminal that is used to execute the specified event via a virtual space, and an event management device that manages information related to the specified event when the specified event is executed using the first communication terminal and the second communication terminal, wherein the event management device has a generation means for generating an event participation notification that prompts the other communication terminal that is scheduled to participate in the specified event but has not yet participated to participate in the specified event after a participation process for the specified event is performed by one of the first communication terminal or the second communication terminal, and a transmission means for transmitting the generated event participation notification to the other communication terminal. Effect of the Invention

[0006] As described above, according to the present invention, when a specified event is carried out with a physical space and a virtual space associated with each other, a participant who first participates in one space can participate in the specified event without having to perform any participation processing for the other space. [Brief description of the drawings]

[0007] [Figure 1] 1 is a diagram illustrating an example of an overall configuration of an information processing system according to a first embodiment. [Diagram 2] FIG. 2 is a diagram showing an example of an overhead view of a physical space (event space) according to the embodiment. [Diagram 3] FIG. 2 is a diagram showing an example of an overhead view of a virtual space (metaverse) according to an embodiment. [Figure 4] FIG. 2 is a diagram illustrating an example of a hardware configuration of a communication terminal according to an embodiment. [Diagram 5] FIG. 2 is a diagram illustrating an example of a hardware configuration of an information processing device and a PC according to an embodiment. [Figure 6]A figure showing an example of the hardware configuration of a user management server, an event management server, a virtual reality hybrid event management server, and a metaverse management server according to an embodiment. [Figure 7A] FIG. 1 is a diagram illustrating an example of a functional configuration of an information processing system according to an embodiment. [Figure 7B] FIG. 1 is a diagram illustrating an example of a functional configuration of an information processing system according to an embodiment. [Figure 7C] FIG. 1 is a diagram illustrating an example of a functional configuration of an information processing system according to an embodiment. [Figure 8] FIG. 4 is a conceptual diagram illustrating an example of a user management table according to the embodiment. [Figure 9] FIG. 13 is a conceptual diagram illustrating an example of an event management table according to the embodiment. [Figure 10] 11 is a conceptual diagram illustrating an example of an event user management table according to the embodiment. FIG. [Figure 11] 10 is a conceptual diagram illustrating an example of an event management table according to the embodiment. FIG. [Figure 12] FIG. 13 is a conceptual diagram illustrating an example of a hybrid event management table according to the embodiment. [Figure 13] FIG. 13 is a diagram showing an example of a registration screen for an event schedule according to the embodiment. [Figure 14] FIG. 11 is a sequence diagram illustrating an example of a process including a process for displaying a list of events associated with a device according to [Figure 15] FIG. 11 is a diagram illustrating an example of an event list display screen associated with a device according to the embodiment. [Figure 16] 11 is a sequence diagram illustrating an example of a process including a process for displaying a list of events associated with a user according to the embodiment [Figure 17] FIG. 13 is a diagram illustrating an example of an event list display screen associated with a user according to the embodiment. [Figure 18] FIG. 11 is a sequence diagram illustrating an example of an event participation process from a communication terminal according to the embodiment. [Figure 19] FIG. 13 is a diagram illustrating an example of a password information input screen according to the embodiment. [Figure 20] FIG. 11 is a sequence diagram illustrating an example of a process including a process for displaying a list of events associated with the metaverse according to the embodiment. [Figure 21] FIG. 13 is a diagram illustrating an example of an event list display screen of the metaverse according to the embodiment. [Figure 22] 11 is a sequence diagram illustrating an example of a process including a process for displaying a list of events associated with a user according to the embodiment. FIG. [Figure 23A] 11 is a sequence diagram showing an example of a process including a coordination process between a communication terminal and a metaverse event participation according to an embodiment. FIG. [Figure 23B] FIG. 11 is a sequence diagram showing another example of a process including a coordination process between a communication terminal and a metaverse event participation according to an embodiment. [Figure 23C] FIG. 11 is a sequence diagram showing another example of a process including a coordination process between a communication terminal and a metaverse event participation according to an embodiment. [Figure 23D] FIG. 11 is a sequence diagram showing another example of a process including a coordination process between a communication terminal and a metaverse event participation according to an embodiment. [Figure 23E] FIG. 11 is a sequence diagram showing another example of a process including a coordination process between a communication terminal and a metaverse event participation according to an embodiment. [Figure 24] FIG. 13 is a diagram illustrating an example of an event participation dialogue screen according to the embodiment. [Figure 25A] 11 is a sequence diagram showing an example of a process including a linking process of event participation from the metaverse according to an embodiment. FIG. [Figure 25B] FIG. 11 is a sequence diagram showing another example of a process including a linking process of event participation from the metaverse according to an embodiment. [Figure 25C] FIG. 11 is a sequence diagram showing another example of a process including a linking process of event participation from the metaverse according to an embodiment. [Figure 25D] FIG. 11 is a sequence diagram showing another example of a process including a linking process of event participation from the metaverse according to an embodiment. [Figure 26]FIG. 13 is a diagram illustrating an example of a request dialog according to the embodiment. [Figure 27] FIG. 13 is a diagram illustrating an example of a request waiting dialog according to the embodiment. [Figure 28] FIG. 11 is a diagram illustrating an example of a request dialog according to the embodiment. [Figure 29] 11 is a flowchart illustrating an example of a metaverse usage process according to an embodiment. [Diagram 30] FIG. 13 is a diagram illustrating an example of a screen for participating in a virtual reality hybrid event as a communication terminal according to an embodiment. [Diagram 31] A figure showing an example of a participation screen when participating in a virtual reality hybrid event as a user in an embodiment. [Diagram 32] 11 is a sequence diagram illustrating an example of a process including a request to exit from a conference room in the metaverse according to an embodiment. FIG. [Diagram 33] FIG. 11 is a diagram showing an example of a display screen of an exit icon when overlooking a virtual space (metaverse) according to an embodiment. [Diagram 34] FIG. 13 is a diagram showing an example of a waiting message display screen according to the embodiment. [Diagram 35] FIG. 11 is a diagram illustrating an example of an overall configuration of an information processing system according to a second embodiment. [Diagram 36] FIG. 11 is a diagram showing an example of a three-dimensional metaverse screen displayed in the VR goggles according to the second embodiment. [Figure 37] FIG. 13 is a diagram showing an example of a three-dimensional metaverse screen displayed in VR goggles according to a modified example of the second embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0008] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. In the description of the drawings, the same elements are given the same reference numerals, and the description of overlapping parts will be omitted.

[0009] [First embodiment] [Overall configuration of information processing system] FIG. 1 is a diagram showing an example of the overall configuration of an information processing system. As shown in FIG. 1, the information processing system 1 includes a communication terminal 3 (an example of a first communication terminal), an information processing device 4, and one or more PCs 9 (an example of a second communication terminal). The information processing system 1 also includes a user management server 5 (an example of a user management device), an event management server 6 (an example of an event management device), a virtual reality hybrid event management server 7 (an example of a virtual reality hybrid event management device), and a metaverse management server 8 (an example of a metaverse management device). The information processing system 1 further includes an event management system 2 including the communication terminal 3, the event management server 6, and the PC 9. In the information processing system 1, the above-mentioned devices, the metaverse, and the servers are connected to each other via a communication network 100.

[0010] The communication network 100 is a wired or wireless communication network in which an unspecified number of communications are carried out, and is constructed by the Internet, an intranet, a LAN (Local Area Network), etc. The communication network 100 may include a communication network using wireless communication such as 4G (4th Generation), 5G (5th Generation), WiMAX (Worldwide Interoperability for Microwave Access), LTE (Long Term Evolution), etc. The communication terminal 3 and each server may be connected to each other by a dedicated local area network, etc.

[0011] <Communication terminal> The communication terminal 3 is a communication terminal that exists in a physical space and is used to execute a predetermined event. The communication terminal 3 is used as, for example, a commonly known IFPD (Interactive Flat-Panel Display) by one or more users (users) who use the information processing system 1 (event management system 2) at an event such as a conference.

[0012] The communication terminal 3 is realized by an information processing device (computer system) equipped with a general OS or the like for performing communication, and is one of the components that configure the information processing system 1. The communication terminal 3 is capable of installing and storing in a storage means a communication application for communicating with each server and the PC 9 via the communication network 100, and of operating browser software and various application software.

[0013] In this embodiment, the communication terminal 3 functions as a first communication terminal.

[0014] <Information processing device> The information processing device 4 is a device (communication terminal) used by a user (user) who participates in a given event. The information processing device 4 is realized by an information processing terminal (computer system) for communication equipped with a general OS, and is one of the components that configure the information processing system 1. The information processing device 4 is capable of installing and storing communication applications and the like for communicating with the communication terminal 3 and the like in a storage means, and of operating browser software and various application software.

[0015] The information processing device 4 may be a communication terminal having a communication function, such as a commonly used PC (Personal Computer), a portable notebook PC, a mobile phone, a smartphone, a tablet terminal, or a wearable terminal (sunglasses type, wristwatch type).

[0016] <User management server> The user management server 5 is a server (device) that manages user information. The user management server 5 is realized by an information processing terminal (computer system) for communication equipped with a general OS or the like, and is one of the components that configure the information processing system 1. The user management server 5 further installs and stores in a storage means communication applications and the like for communicating with the communication terminal 3 and each server, and is capable of running browser software and various application software.

[0017] The user management server 5 manages user information such as the user type, user name, user email address, etc. The user management server 5 also has a function of authenticating users.

[0018] The user management server 5 may be a communication terminal having a communication function, such as a commonly used PC (Personal Computer), a portable notebook PC, a mobile phone, a smartphone, or a tablet terminal.

[0019] Furthermore, the user management server 5 may notify (transmit) data (information) by push notification (transmission) to other communication terminals etc. connected via the communication network 100. In this case, the user management server 5 may also perform push notification via, for example, FCM (Firebase Cloud Messaging), which is an example of a push notification server.

[0020] <Event management server> The event management server 6 is a server (device) that manages information related to a specific event when the specific event is executed using the communication terminal 3 (first communication terminal) and the PC 9 (second communication terminal). The event management server 6 is realized by an information processing terminal (computer system) for communication equipped with a general OS or the like, and is one of the components that configure the information processing system 1. The event management server 6 further installs and stores in a storage means communication applications and the like for communicating with the communication terminal 3, the PC 9, and each server, and is capable of running browser software and various application software.

[0021] The event management server 6 manages conference information such as the conference organizer, title, conference time, conference password, conference URL, etc. The event management server 6 manages conference participants based on the user management table as a conference user management table, linked to each conference. The event management server 6 also manages the participation status of each conference together with information such as the user and participation time.

[0022] The event management server 6 may be a communication terminal having a communication function, such as a commonly used PC (Personal Computer), a portable notebook PC, a mobile phone, a smartphone, or a tablet terminal.

[0023] Furthermore, the event management server 6 may notify (transmit) data (information) by push notification (transmission) to other communication terminals etc. connected via the communication network 100. In this case, the event management server 6 may also perform push notification via, for example, FCM (Firebase Cloud Messaging), which is an example of a push notification server.

[0024] <Virtual reality hybrid event management server> The virtual reality hybrid event management server 7 is a server (device) that has a URL for holding an event between devices and terminals connected via the communication network 100, and enables users who have participated in the URL to hold video conferences, etc. The event management server 6 is realized by an information processing terminal (computer system) for communication equipped with a general OS, etc., and is one of the components that configure the information processing system 1. The virtual reality hybrid event management server 7 further installs and stores in a storage means communication applications, etc. for communicating with the communication terminal 3, the PC 9, and each server, and is capable of running browser software and various application software.

[0025] The virtual reality hybrid event management server 7 is, for example, a server that has a URL for holding a conference between terminals connected via the communication network 100, and allows users who participate in the URL to hold a video conference or the like.

[0026] The virtual reality hybrid event management server 7 may be a communication terminal having a communication function, such as a commonly used PC (Personal Computer), a portable notebook PC, a mobile phone, a smartphone, or a tablet terminal.

[0027] Furthermore, the virtual reality hybrid event management server 7 may notify (transmit) data (information) by push notification (transmission) to other communication terminals etc. connected via the communication network 100. In this case, the virtual reality hybrid event management server 7 may also perform push notification via, for example, FCM (Firebase Cloud Messaging), which is an example of a push notification server.

[0028] <Metaverse Management Server> The metaverse management server 8 is a server (device) that has a URL for executing an event between devices and terminals connected via the communication network 100, and that enables users who have joined the URL to hold video conferences and provide a larger virtual space. The metaverse management server 8 is realized by an information processing terminal (computer system) for communication that is equipped with a general OS or the like, and is one of the components that configure the information processing system 1. The metaverse management server 8 further installs and stores in a storage means communication applications and the like for communicating with the communication terminal 3, the PC 9, and each server, and is capable of running browser software and various application software.

[0029] The metaverse management server 8 provides a metaverse space that can be accessed from a browser or the like.

[0030] The metaverse management server 8 may be a communication terminal having a communication function, such as a commonly used PC (Personal Computer), a portable notebook PC, a mobile phone, a smartphone, or a tablet terminal.

[0031] Furthermore, the metaverse management server 8 may notify (transmit) data (information) by push notification (transmission) to other communication terminals etc. connected via the communication network 100. In this case, the metaverse management server 8 may also perform push notification via, for example, FCM (Firebase Cloud Messaging), which is an example of a push notification server.

[0032] In this embodiment, each of the above-mentioned servers may exist independently, or may exist as a single server combining the various functions. In addition, each server may utilize a conference reservation system, a Web conference system, or the like that is provided as general groupware.

[0033] <pc> The PC 9 is a communication terminal used to execute a predetermined event through a virtual space. The PC 9 is realized by an information processing terminal (computer system) for communication equipped with a general OS, and is one of the components that construct the information processing system 1 (event management system 2). The PC 9 further installs and stores in a storage means communication applications for communicating with the communication terminal 3, the information processing device 4, and each server, and is capable of running browser software and various application software.

[0034] The PC 9 may be a communication terminal having a communication function, such as a commonly used PC (Personal Computer), a portable notebook PC, a mobile phone, a smartphone, a tablet terminal, or a wearable terminal (sunglasses type, wristwatch type).

[0035] In this embodiment, the PC 9 functions as a second communication terminal.

[0036] As described above, in the information processing system 1, an IFPD is installed in a conference room that exists in a physical space, and a user in the conference room can participate in the virtual reality hybrid event using the IFPD. Meanwhile, a user at home or the like can enter the metaverse as a virtual space from a browser or the like, and participate in the virtual reality hybrid event using the conference room in the metaverse.

[0037] ●About terminology● In this embodiment, a user refers to a person who uses or utilizes the information processing system 1 (event management system 2). In addition, a user refers to a participant who participates in a specific event. In this embodiment, a user further refers to a conference room (IFPD) in an office, a conference room in the metaverse, etc.

[0038] In this embodiment, an event refers to an execution target such as a meeting, a discussion, a lecture, a class, etc., which is held face-to-face in a physical space and online using a virtual space. Based on this, a predetermined event in this embodiment refers to the same execution target including a meeting, a discussion, a lecture, a class, etc., which is held at the same time in a physical space and a virtual space. In addition, a virtual reality hybrid event refers to an event that is realized by simultaneously holding an event such as a meeting held in a conference room or the like in a physical space online using a virtual space.

[0039] <Example of physical space (event space) layout> 2 is a diagram showing an example of an overhead view of a physical space (event space) according to an embodiment. The IFPD existing in the physical space is based on an electronic whiteboard, for example, and is integrated with a web conferencing system in addition to the function of a whiteboard. In such an environment, the IFPD is used in meetings that are completed within a conference room, hybrid work meetings, etc.

[0040] <Example of virtual space (metaverse) layout> FIG. 3 is a diagram showing an example of a bird's-eye view of a virtual space (metaverse) according to an embodiment. In recent years, in remote work, the metaverse is also used to activate communication, and there is a service that allows you to connect to a Web conference system from within the metaverse. In addition, a service is provided for customizing the metaverse space, and the space can be designed similarly to a real office. In the metaverse space, you can move your own avatar (a circle including a person icon, or a person icon inside a circle) to a destination, sit down, or enter a conference room. In addition, when a user enters a conference room using an avatar, there is a function that allows an ad-hoc Web conference to be held only by the members in the conference room.

[0041] [Hardware configuration] Next, the hardware configuration of the device or apparatus constituting the information processing system according to the embodiment will be described with reference to Figures 4 to 6. Note that components may be added or deleted from the hardware configuration of the communication terminal or apparatus shown in Figures 4 to 6 as necessary.

[0042] <Hardware configuration of communication terminal> Fig. 4 is a diagram showing an example of a hardware configuration of a communication terminal according to an embodiment. As shown in Fig. 4, an IFPD (electronic whiteboard), which is an example of a communication terminal 3, is constructed by, for example, a computer, and includes a CPU (Central Processing Unit) 301, a ROM (Read Only Memory) 302, a RAM (Random Access Memory) 303, an SSD (Solid State Drive) 304, a network I / F 305, an external device connection I / F 306, and a bus line 310.

[0043] Of these, the CPU 301 controls the overall operation of the communication terminal 3. The ROM 302 stores programs used to drive the CPU 301, such as the CPU 301 and an IPL (Initial Program Loader). The RAM 303 is used as a work area for the CPU 301. The SSD 304 stores various data, such as programs for the communication terminal 3. The network I / F 305 controls communication with the communication network 100. The external device connection I / F 306 is an interface for connecting various external devices. In this case, the external devices are, for example, a Universal Serial Bus (USB) memory 330 and external devices (a microphone 340, a speaker 350, and a camera 360).

[0044] The communication terminal 3 further includes a capture device 311, a GPU 312, a display controller 313, a contact sensor 314, a sensor controller 315, an electronic pen controller 316, a near-field communication circuit 319 and an antenna 319a for the near-field communication circuit 319, a power switch 322, and selection switches 323.

[0045] Of these, the capture device 311 displays video information as still images or moving images on the display of an external PC (Personal Computer) 370. The GPU (Graphics Processing Unit) 312 is a semiconductor chip that specializes in graphics. The display controller 313 controls and manages the screen display to output an output image from the GPU 312 to a display 380 or the like. The contact sensor 314 detects that an electronic pen 390, a user's hand H, or the like has contacted the display 380. The sensor controller 315 controls the processing of the contact sensor 314. The contact sensor 314 inputs and detects coordinates by an infrared blocking method. The method of inputting and detecting the coordinates is a method in which two light receiving and emitting devices installed at both ends of the upper side of the display 380 emit a plurality of infrared rays in parallel to the display 380, and receive the light that is reflected by a reflecting member installed around the display 380 and returns along the same optical path as the optical path of the light emitted by the light receiving element. The contact sensor 314 outputs the ID of the infrared light radiated by the two light receiving and emitting devices that is blocked by the object to the sensor controller 315, and the sensor controller 315 specifies the coordinate position that is the contact position of the object. The electronic pen controller 316 determines whether the pen tip or the pen tail touches the display 380 by communicating with the electronic pen 390. The short-range communication circuit 319 is a communication circuit such as NFC (Near Field Communication) or Bluetooth (registered trademark). The power switch 322 is a switch for switching the power of the communication terminal 3 ON / OFF. The selection switches 323 are, for example, a group of switches for adjusting the brightness and color of the display 380.

[0046] Furthermore, the communication terminal 3 includes a bus line 310. The bus line 310 is an address bus, a data bus, or the like for electrically connecting the components such as the CPU 301 shown in FIG.

[0047] The contact sensor 314 is not limited to an infrared blocking type, and may use various detection means such as a capacitive touch panel that identifies the contact position by detecting a change in capacitance, a resistive film touch panel that identifies the contact position by a voltage change between two opposing resistive films, or an electromagnetic induction touch panel that identifies the contact position by detecting electromagnetic induction caused by a contacting object touching the display unit. The electronic pen controller 316 may determine whether or not a part of the electronic pen 390 that is held by the user or other parts of the electronic pen 390 has been touched, in addition to the tip and bottom of the electronic pen 390.

[0048] <Hardware configuration of information processing device, PC> Fig. 5 is a diagram showing an example of the hardware configuration of an information processing device and a PC according to an embodiment. As shown in Fig. 5, the information processing device 4 is constructed by, for example, a computer, and includes a CPU 401, a ROM 402, a RAM 403, an EEPROM 404, a HD (Hard Disk) 405, a HDD (Hard Disk Drive) controller 406, a display 407, a short-range communication I / F 408, a CMOS sensor 409, and an image sensor I / F 410. The information processing device 4 further includes a network I / F 411, a keyboard 412, a pointing device 413, a media I / F 415, an external device connection I / F 416, a sound input / output I / F 417, a microphone 418, a speaker 419, and a bus line 420.

[0049] Among these, the CPU 401 controls the operation of the entire information processing device 4. The ROM 402 stores programs and the like used to drive the CPU 401. The RAM 403 is used as a work area for the CPU 401. The EEPROM 404 reads or writes various data such as applications under the control of the CPU 401. The HD 405 stores various data such as programs. The HDD controller 406 controls the reading or writing of various data from the HD 405 under the control of the CPU 401. Here, the information processing device 4 may have a hardware configuration in which an SSD (Solid State Drive) is mounted instead of the HD 405 and the HDD controller 406. The display 407 displays various information such as a cursor, a menu, a window, a character, or an image. In this embodiment, the display 407 functions as an example of a display means. The short-range communication I / F 408 is a communication circuit for performing data communication with a communication device or a communication terminal having a wireless communication interface such as NFC (Near Field Communication), Bluetooth (registered trademark; omitted below), or Wi-Fi (registered trademark; omitted below). The CMOS sensor 409 is a type of built-in imaging means that captures an image of a subject under the control of the CPU 401 to obtain image data or video data. The imaging means may be an imaging means constituted by a CCD (Charge Coupled Device) sensor or the like instead of a CMOS sensor. The image sensor I / F 410 is a circuit that controls the driving of the CMOS sensor 409.

[0050] The network I / F 411 is an interface for data communication using the communication network 100. The keyboard 412 is a type of input means having a plurality of keys for inputting characters, numbers, various instructions, etc. Note that, instead of or in addition to the keyboard 412, an input means such as a touch panel for operating a predetermined button, icon, etc. may be used. The pointing device 413 is a type of input means for selecting and executing various instructions, selecting a processing target, moving a cursor, etc. The media I / F 415 controls reading or writing (storing) data from and to a recording medium 414 such as a flash memory. The external device connection I / F 416 is an interface for connecting various external devices. In this case, the external device may be, for example, a USB (Universal Serial Bus) memory, etc. The sound input / output I / F 417 is a circuit for processing input / output of sound signals between a microphone 418 and a speaker 419 according to the control of the CPU 401. The microphone 418 is a built-in circuit that converts sound into an electrical signal, and obtains information using the electrical signal by acquiring voice or sound waves emitted from an external speaker or the like. The speaker 419 is a built-in circuit that converts an electrical signal into physical vibrations to generate sounds such as music or voice. The bus line 420 is an address bus, a data bus, or the like for electrically connecting each component such as the CPU 401.

[0051] The PC 9 is constructed by, for example, a computer, and includes a CPU 901, a ROM 902, a RAM 903, an EEPROM 904, an HD (Hard Disk) 905, an HDD (Hard Disk Drive) controller 906, a display 907, a short-range communication I / F 908, a CMOS sensor 909, and an image sensor I / F 910. The PC 9 further includes a network I / F 911, a keyboard 912, a pointing device 913, a media I / F 915, an external device connection I / F 916, an audio input / output I / F 917, a microphone 918, a speaker 919, and a bus line 920. These hardware resources are similar to the CPU 401, ROM 402, RAM 403, EEPROM 404, HD (Hard Disk) 405, HDD (Hard Disk Drive) controller 406, display 407, short-range communication I / F 408, CMOS sensor 409, image sensor I / F 410, network I / F 411, keyboard 412, pointing device 413, media I / F 415, external device connection I / F 416, sound input / output I / F 417, microphone 418, speaker 419 and bus line 420 of the information processing device 4, and therefore will not be described here.

[0052] <Hardware configuration of various servers> 6 is a diagram showing an example of the hardware configuration of a user management server, an event management server, a virtual reality hybrid event management server, and a metaverse management server according to an embodiment. As shown in FIG. 6, the user management server 5 is constructed by, for example, a computer, and includes a CPU 501, a ROM 502, a RAM 503, an EEPROM 504, a HD (Hard Disk) 505, a HDD (Hard Disk Drive) controller 506, and a short-range communication I / F 908. The user management server 5 further includes a network I / F 511, a keyboard 512, a pointing device 513, a media I / F 515, an external device connection I / F 516, and a bus line 920.

[0053] Among these, the CPU 501 controls the operation of the entire user management server 5. The ROM 502 stores programs and the like used to drive the CPU 501. The RAM 503 is used as a work area for the CPU 501. The EEPROM 504 reads or writes various data such as applications under the control of the CPU 501. The HD 505 stores various data such as programs. The HDD controller 506 controls the reading or writing of various data from the HD 505 under the control of the CPU 501. Here, the user management server 5 may have a hardware configuration equipped with an SSD (Solid State Drive) instead of the HD 505 and the HDD controller 506. The short-distance communication I / F 508 is a communication circuit for performing data communication with a communication device or a communication terminal having a wireless communication interface such as NFC (Near Field Communication), Bluetooth (registered trademark, omitted below), or Wi-Fi (registered trademark, omitted below).

[0054] The network I / F 511 is an interface for data communication using the communication network 100. The keyboard 512 is a type of input means having a plurality of keys for inputting characters, numbers, various instructions, etc. Note that, instead of or in addition to the keyboard 512, an input means such as a touch panel for operating a predetermined button, icon, etc. may be used. The pointing device 513 is a type of input means for selecting and executing various instructions, selecting a processing target, moving a cursor, etc. The media I / F 515 controls reading or writing (storing) data from and to a recording medium 514 such as a flash memory. The external device connection I / F 516 is an interface for connecting various external devices. In this case, the external device may be, for example, a USB (Universal Serial Bus) memory, etc. The bus line 520 is an address bus, a data bus, etc. for electrically connecting each component such as the CPU 501.

[0055] The event management server 6 is constructed, for example, by a computer, and includes hardware resources assigned with reference numbers in the 600 range similar to the hardware resources in the 500 range explained for the user management server 5. Therefore, explanation of the hardware resources related to the event management server 6 will be omitted.

[0056] The virtual reality hybrid event management server 7 is constructed, for example, by a computer, and includes hardware resources assigned with reference numbers in the 700 series similar to the hardware resources in the 500 series described for the user management server 5. Therefore, a description of the hardware resources related to the virtual reality hybrid event management server 7 will be omitted.

[0057] The metaverse management server 8 is constructed, for example, by a computer, and includes hardware resources assigned with reference numbers in the 800 series similar to the hardware resources in the 500 series described for the user management server 5. Therefore, a description of the hardware resources related to the metaverse management server 8 will be omitted.

[0058] The above program may be recorded in a computer-readable recording medium as an installable or executable file, or may be distributed by downloading via a network. Examples of recording media include CD-Rs (Compact Disc Recordable), DVDs (Digital Versatile Disks), Blu-ray Discs (Blu-ray is a registered trademark; omitted below), SD cards, and USB memories. The recording media may be provided domestically or internationally as a program product. For example, the event management server 6 realizes the event management method according to the present invention by executing the program according to the present invention.

[0059] [Functional configuration of information processing system] Next, the functional configuration of this embodiment will be described with reference to Fig. 7 to Fig. 12. Fig. 7 is a diagram showing an example of the functional configuration of an information processing system according to an embodiment. Fig. 7 (Fig. 7A, Fig. 7B, Fig. 7C) shows communication terminals or devices (servers) shown in Fig. 1 that are related to processes or operations described below.

[0060] <Functional configuration of communication terminal> First, the functional configuration of the communication terminal 3 will be described with reference to FIG. 7A. As shown in FIG. 7A, the communication terminal 3 has a transmission / reception unit 31, an operation reception unit 32, an acquisition unit 33, a display control unit 34, an execution processing unit 38, and a storage / reading unit 39. Each of these functional units is a function or means realized by operating any of the hardware resources shown in FIG. 4 by an instruction from the CPU 301 according to a program for the communication terminal 3 that is loaded from at least one of the ROM 302, the SSD 304, and the USB memory 330 to the RAM 303. The communication terminal 3 also has a storage unit 3000 (an example of a storage unit) constructed by at least one of the ROM 302, the SSD 304, and the USB memory 330 shown in FIG. 4. A communication program (communication application) for communicating with the user management server 5, the event management server 6, and the like via the communication network 100 is installed and stored in the storage unit 3000.

[0061] <<Functional configuration of communication terminal>> Next, each functional configuration of the communication terminal 3 will be described in detail. The transmission / reception unit 31 of the communication terminal 3 shown in Fig. 7A is mainly realized by the processing of the CPU 301 on the network I / F 305 and the short-range communication circuit 319, and transmits and receives various data (information) between the user management server 5, the event management server 6, etc. via the communication network 100. The transmission / reception unit 31 also receives an event participation notification transmitted by the event management server 6. In this embodiment, the transmission / reception unit 31 functions as an example of at least one of a transmitting means and a receiving means.

[0062] The operation reception unit 32 is realized by the CPU 301 processing signals generated by various operations received by at least one of the power switch 322, the selection switches 323, and the display 380, and receives operations for the communication terminal 3. In this embodiment, the operation reception unit 32 functions as an example of a reception means.

[0063] The acquisition unit 33 is mainly realized by the processing of the CPU 301, and acquires various information received by the transmission / reception unit 31. In this embodiment, the acquisition unit 33 functions as an example of an acquisition means.

[0064] The display control unit 34 is mainly realized by the processing of the CPU 301, and controls the display of various UI screens displayed on the communication terminal 3. The display control unit 34 also causes an event participation notification generated by the event management server 6 to be displayed on the display 380. The display control unit 34 further causes a dialogue that can be operated on the communication terminal 3 or the PC 9 by a user of the communication terminal 3 or the PC 9, to be displayed as the event participation notification. In this embodiment, the display control unit 34 functions as an example of a display control means.

[0065] The determination unit 35 is mainly realized by the processing of the CPU 301, and performs various determinations in the communication terminal 3. In this embodiment, the determination unit 35 functions as an example of a determination means.

[0066] The generation unit 37 is mainly realized by the processing of the CPU 301, and generates various information (or data), UI screen data, and the like in the communication terminal 3. In this embodiment, the generation unit 37 functions as an example of a generation means.

[0067] The execution processing unit 38 is realized mainly by the processing of the CPU 301, and executes various processes in the communication terminal 3. In this embodiment, the execution processing unit 38 functions as an example of an execution means or a processing means.

[0068] The storage / reading unit 39 is mainly realized by processing of the CPU 301 on at least one of the ROM 302, the SSD 304, and the USB memory 330, and stores various data (or information) in the storage unit 3000 and reads various data (or information) from the storage unit 3000. In this embodiment, the storage / reading unit 39 functions as an example of a storage control means.

[0069] <Functional configuration of information processing device> Next, the functional configuration of the information processing device 4 will be described. As shown in FIG. 7A, the information processing device 4 has a transmission / reception unit 41, an operation reception unit 42, an acquisition unit 43, a display control unit 44, an execution control unit 48, and a storage / reading unit 49. Each of these functional units is a function or means realized by operating any of the hardware resources shown in FIG. 5 by an instruction from the CPU 401 according to a program for the information processing device 4 expanded from at least one of the ROM 402, the EEPROM 404, the HD 405, and the recording medium 414 to the RAM 403. The information processing device 4 also has a storage unit 4000 (an example of a storage unit) constructed by at least one of the EEPROM 404, the HD 405, and the recording medium 414 shown in FIG. In addition, a communication program (communication application) for communicating with the communication terminal 3, the user management server 5, the event management server 6, and the like via the communication network 100 is installed and stored in the storage unit 4000.

[0070] <<Functional configuration of information processing device>> Next, each functional configuration of the information processing device 4 will be described in detail. The transmitting / receiving unit 41 of the information processing device 4 shown in Fig. 7A is mainly realized by the processing of the CPU 401 on the network I / F 411 and the short-range communication I / F 408, and transmits and receives various data (information) between the communication terminal 3, the user management server 5, the event management server 6, etc. via the communication network 100. In this embodiment, the transmitting / receiving unit 41 functions as an example of at least one of a transmitting means and a receiving means.

[0071] The operation reception unit 42 is mainly realized by the CPU 401 processing signals generated by various operations received by at least one of the keyboard 412 and the pointing device 413, and receives operations on the information processing apparatus 4. In the present embodiment, the operation reception unit 42 functions as an example of reception means.

[0072] The acquisition unit 43 is mainly realized by the processing of the CPU 401, and acquires various information received by the transmission / reception unit 41. In the present embodiment, the acquisition unit 43 functions as an example of acquisition means.

[0073] The display control unit 44 is mainly realized by the processing of the CPU 401 on the display 407, and controls the display of various UI screens displayed on the communication terminal 3. In the present embodiment, the display control unit 34 functions as an example of display control means.

[0074] The execution control unit 48 is mainly realized by the processing of the CPU 401, and controls the execution of various processes in the information processing apparatus 4. In the present embodiment, the execution control unit 48 functions as an example of execution control means.

[0075] The memory readout unit 49 is mainly realized by the processing of the CPU 401 on at least one of the ROM 402, EEPROM 404, HD 405, and recording medium 414, stores various data (or information) in the storage unit 4000, or reads out various data (or information) from the storage unit 4000. In the present embodiment, the memory readout unit 49 functions as an example of memory control means.

[0076] <Functional Configuration of PC> Next, the functional configuration of the PC9 will be described. As shown in FIG. 7A, the PC9 includes a transmission / reception unit 91, an operation reception unit 92, an acquisition unit 93, a display control unit 94, a determination unit 95, an execution control unit 98, and a memory readout unit 99. Each of these functional units is a function or means realized by any of the hardware resources shown in FIG. 5 operating according to instructions from the CPU 901 in accordance with a program for the PC9 developed from at least one of the ROM 902, EEPROM 904, HD 905, and recording medium 914 to the RAM 903. Further, the PC9 has a storage unit 9000 (an example of storage means) constructed by at least one of the ROM 902, EEPROM 904, HD 905, and recording medium 914 shown in FIG. 5. In the storage unit 9000, a communication program (communication application) for communicating with the communication terminal 3, information processing device 4, user management server 5, event management server 6, etc. via the communication network 100 is installed and stored.

[0077] <<Functional Configuration of Each PC>> Next, the functional configuration of each part of the PC9 will be described in detail. The transmission / reception unit 91 of the PC9 shown in FIG. 7A is mainly realized by the processing of the CPU 901 for the network I / F 911 and the short-range communication I / F 908, and transmits and receives various data (information) to and from the communication terminal 3, information processing device 4, user management server 5, event management server 6, etc. via the communication network 100. Further, the transmission / reception unit 91 receives an event participation notification transmitted by the event management server 6. In the present embodiment, the transmission / reception unit 91 functions as an example of at least one of a transmission means and a reception means.

[0078] The operation reception unit 92 is mainly realized by the CPU 901 processing signals generated by various operations received by at least one of the keyboard 912 and the pointing device 913, and receives operations on the PC9. In the present embodiment, the operation reception unit 92 functions as an example of a reception means.

[0079] The acquisition unit 93 is mainly realized by the processing of the CPU 901, and acquires various information received by the transmission / reception unit 91. In this embodiment, the acquisition unit 93 functions as an example of an acquisition means.

[0080] The display control unit 94 is mainly realized by processing of the CPU 901 for the display 907, and controls the display of various UI screens displayed on the PC 9. The display control unit 94 also causes the display 907 to display an event participation notification generated by the event management server 6. In this embodiment, the display control unit 94 functions as an example of a display control means.

[0081] The execution control unit 98 is mainly realized by the processing of the CPU 901, and controls the execution of various processes in the PC 9. In this embodiment, the execution control unit 98 functions as an example of an execution control means.

[0082] The storage / reading unit 99 is mainly realized by processing of the CPU 901 on at least one of the ROM 902, the EEPROM 904, the HD 905, and the recording medium 914, and stores various data (or information) in the storage unit 9000 and reads various data (or information) from the storage unit 9000. In this embodiment, the storage / reading unit 99 functions as an example of a storage control means.

[0083] <User management server functional configuration> Next, the functional configuration of the user management server 5 will be described with reference to FIG. 7B. As shown in FIG. 7B, the user management server 5 has a transmission / reception unit 51, an acquisition unit 53, an authentication processing unit 58, and a storage / reading unit 59. Each of these functional units is a function or means realized by operating any of the hardware resources shown in FIG. 6 by an instruction from the CPU 501 according to a program for the user management server 5 expanded from at least one of the ROM 502, the EEPROM 504, the HD 505, and the recording medium 514 to the RAM 503. The user management server 5 also has a storage unit 5000 (an example of a storage unit) constructed by at least one of the ROM 502, the EEPROM 504, the HD 505, and the recording medium 514 shown in FIG. 6. A communication program (communication application), a browser application, and the like for communicating with the event management server 6 and the like via the communication network 100 are installed and stored in the storage unit 5000.

[0084] <<User management server functional configuration>> Next, a detailed description will be given of each functional configuration of the user management server 5. The transmission / reception unit 51 of the user management server 5 shown in Fig. 7B is mainly realized by processing of the CPU 501 on the network I / F 511 and the short-range communication I / F 508, and transmits and receives various data (or information) between the communication terminal 3 and the PC 9 via the communication network 100. In this embodiment, the transmission / reception unit 51 functions as an example of at least one of a transmitting means and a receiving means.

[0085] The acquisition unit 53 is mainly realized by the processing of the CPU 501. The acquisition unit 53 also acquires the user ID and password included in the user authentication request transmitted from the communication terminal 3 and the PC 9 via the transmission / reception unit 51. In this embodiment, the acquisition unit 53 functions as an example of an acquisition means.

[0086] The authentication processing unit 58 is mainly realized by the processing of the CPU 501, and executes the authentication processing carried out by the user management server 5. In this embodiment, the authentication processing unit 58 functions as an example of an authentication means and an example of a processing means.

[0087] The storage / reading unit 59 is mainly realized by processing of the CPU 501 on at least one of the ROM 502, the EEPROM 504, the HD 505, and the recording medium 514, and stores various data (or information) in the storage unit 5000 and reads various data (or information) from the storage unit 5000. In this embodiment, the storage / reading unit 59 functions as an example of a storage control means.

[0088] ●User management table● Fig. 8 is a conceptual diagram showing an example of a user management table according to an embodiment. Note that the structure and contents of the data table described below are merely examples and are not limited thereto. A user management DB 5001 configured by a user management table as shown in Fig. 8 is constructed in the storage unit 5000. In the user management table, an account type, a user name, an e-mail address, and a password are stored and managed in association with each user ID.

[0089] Of these, the user ID is identification information that identifies a user who uses or utilizes the information processing system 1 (event management system 2). The account type indicates the type of participant who will participate in a specific event, and includes a person who is a user, a place such as a conference room that exists in physical space, and a metaverse (metaverse space) used as a virtual space. The user name is a person who will participate in a specific event. The email address is an email address assigned to the account type. The password is information including English letters and numbers that is assigned in association with the user name and used for user authentication.

[0090] In this embodiment, the user management table (user management DB 5001) functions as an example of a user management means.

[0091] <Event management server functional configuration> Returning to FIG. 7, the functional configuration of the event management server 6 will be described. As shown in FIG. 7B, the event management server 6 has a transmission / reception unit 61, an acquisition unit 63, a registration unit 66, a generation unit 67, an execution processing unit 68, and a storage / reading unit 69. Each of these functional units is a function or means realized by operating any of the hardware resources shown in FIG. 6 by an instruction from the CPU 601 according to a program for the event management server 6 expanded from at least one of the ROM 602, the EEPROM 604, the HD 605, and the recording medium 614 to the RAM 603. The event management server 6 also has a storage unit 6000 (an example of a storage unit) constructed by at least one of the ROM 602, the EEPROM 604, the HD 605, and the recording medium 614 shown in FIG. 6. A communication program (communication application), a browser application, and the like for communicating with the user management server 5 and the like via the communication network 100 are installed and stored in the storage unit 6000.

[0092] <<Event Management Server Functional Configuration>> Next, each functional configuration of the event management server 6 will be described in detail. The transmission / reception unit 61 of the event management server 6 shown in Fig. 7B is mainly realized by the processing of the CPU 601 on the network I / F 611 and the short-range communication I / F 608, and transmits and receives various data (or information) between the communication terminal 3, the user management server 5, etc. via the communication network 100. In addition, the transmission / reception unit 61 transmits an event participation notification generated by a generation unit 67 described later to the other communication terminal that is scheduled to participate in a predetermined event but has not yet participated. In this embodiment, the transmission / reception unit 61 functions as an example of at least one of the transmission means and the reception means.

[0093] The acquisition unit 63 is mainly realized by the processing of the CPU 601, and acquires various information (data) transmitted from the communication terminal 3, the PC 9, etc., and data of various databases managed by the event management server 6. In this embodiment, the acquisition unit 63 functions as an example of an acquisition means.

[0094] The registration unit 66 is mainly realized by the processing of the CPU 601, and registers various information for the event management server 6. The registration unit 66 also associates a user ID (an example of user identification information) included in a request to participate in a specific event (event participation request) transmitted by the communication terminal 3 with participation date and time information indicating the participation date and time at which the specific event was participated, and registers them in the held event management DB 6003 (see FIG. 11). In this embodiment, the registration unit 66 functions as an example of a registration means.

[0095] The generating unit 67 is mainly realized by the processing of the CPU 601. After a process of participating in a predetermined event is performed by one of the communication terminals 3 and the PC 9, the generating unit 67 generates an event participation notification that prompts the other communication terminal that is scheduled to participate in the predetermined event but has not yet participated to participate in the predetermined event. The generating unit 67 generates the event participation notification based on the participation date and time when one of the communication terminals 3 and the PC 9 participated in the predetermined event. The generating unit 67 further generates, as the event participation notification, a notification that includes an event name indicating the predetermined event being executed and the names of participants participating in the predetermined event. In this embodiment, the registering unit 66 functions as an example of a registering means.

[0096] The execution processing unit 68 is mainly realized by the processing of the CPU 601, and executes various processes in the event management server 6. The execution processing unit 68 also executes a participation process for a predetermined event. The execution processing unit 68 also executes a participation process for a predetermined event based on a request from the communication terminal 3 for either a schedule associated with the communication terminal 3 or a schedule associated with a user participating in a predetermined event executed in a physical space. The execution processing unit 68 further executes a participation process for a predetermined event based on a request from the PC 9 for either a schedule associated with the PC 9, a schedule associated with a user participating in a predetermined event executed in a virtual space, or a schedule represented by a predetermined event being executed. In this embodiment, the execution processing unit 68 functions as an example of an execution means.

[0097] The storage / reading unit 69 is mainly realized by processing of the CPU 601 on at least one of the ROM 602, the EEPROM 604, the HD 605, and the recording medium 614, and stores various data (or information) in the storage unit 6000 and reads various data (or information) from the storage unit 6000. In this embodiment, the storage / reading unit 69 functions as an example of a storage control means.

[0098] ●Event Management Table● Fig. 9 is a conceptual diagram showing an example of an event management table according to an embodiment. Note that the structure and contents of the data table described below are merely examples and are not limited to these. An event management DB 6001 configured with an event management table as shown in Fig. 9 is constructed in the storage unit 6000. In the event management table, for each event ID, the organizer ID, event content, start date and time, end date and time, password, and event location link (URL information) are stored and managed in association with each other.

[0099] Of these, the event ID is identification information that identifies an event such as a conference. The organizer ID is identification information that identifies the user who organizes the event among the users who will participate in the event. The event content represents the content that will be carried out as the event. The start date and time and the end date and time represent the dates and times when the event starts and ends. The password is information used when carrying out the event and is associated with the event content. The event location link (URL information) represents location information for holding a conference between terminals (devices) connected via the communication network 100.

[0100] In this embodiment, the event management table (event management DB 6001) functions as an example of an event management means.

[0101] ●Event user management table● Fig. 10 is a conceptual diagram showing an example of an event user management table according to an embodiment. Note that the structure and contents of the data table described below are merely examples and are not limited thereto. An event user management DB 6002 configured by an event user management table as shown in Fig. 10 is constructed in the storage unit 6000. In the event user management table, an event ID and a user ID are associated with each event user ID and stored and managed.

[0102] Among these, the event user ID represents identification information for identifying a user who will participate in a specific event.

[0103] In this embodiment, the event user management table (event user management DB 6002) functions as an example of an event user management means.

[0104] ●Event Management Table● Fig. 11 is a conceptual diagram showing an example of an event management table according to an embodiment. Note that the structure and contents of the data table described below are merely examples and are not limited thereto. An event management DB 6003 configured with an event management table as shown in Fig. 11 is constructed in the storage unit 6000. In the event management table, an event ID, a user ID, and a participation date and time are stored and managed in association with each event ID.

[0105] Among these, the event ID indicates identification information for identifying the event being held, and the participation date and time indicates the date and time when the user identified by the user ID participated in the event identified by the event ID.

[0106] In this embodiment, the event management table (event management DB 6003) functions as an example of an event management means.

[0107] <Functional configuration of virtual reality hybrid event management server> Next, the functional configuration of the virtual reality hybrid event management server 7 will be described. As shown in FIG. 7C, the virtual reality hybrid event management server 7 has a transmission / reception unit 71, an acquisition unit 73, a connection processing unit 78, and a storage / reading unit 79. Each of these functional units is a function or means realized by operating any of the hardware resources shown in FIG. 6 by an instruction from the CPU 701 according to a program for the virtual reality hybrid event management server 7 expanded from at least one of the ROM 702, EEPROM 704, HD 705, and recording medium 714 to the RAM 703. In addition, the virtual reality hybrid event management server 7 has a storage unit 7000 (an example of a storage unit) constructed by at least one of the ROM 702, EEPROM 704, HD 705, and recording medium 714 shown in FIG. 6. In addition, a communication program (communication application), a browser application, etc. for communicating with the communication terminal 3, the event management server 6, the PC 9, etc. via the communication network 100 are installed and stored in the storage unit 7000.

[0108] <<Functional configuration of virtual reality hybrid event management server>> Next, a detailed description will be given of each functional configuration of the virtual reality hybrid event management server 7. The transmission / reception unit 71 of the virtual reality hybrid event management server 7 shown in Fig. 7C is mainly realized by processing of the CPU 701 on the network I / F 750 and the short-range communication I / F 708, and transmits and receives various data (or information) between the communication terminal 3, the event management server 6, the PC 9, etc. via the communication network 100. In this embodiment, the transmission / reception unit 71 functions as an example of at least one of a transmission means and a reception means.

[0109] The acquisition unit 73 is mainly realized by the processing of the CPU 701, and acquires various information (data) received through communication with the communication terminal 3, the event management server 6, the PC 9, etc. In this embodiment, the acquisition unit 73 functions as an example of an acquisition means.

[0110] The connection processing unit 78 is mainly realized by the processing of the CPU 701, and executes various processes for connecting to the virtual reality hybrid event management server 7. In this embodiment, the connection processing unit 78 functions as an example of a processing means.

[0111] The storage / reading unit 79 is mainly realized by processing of the CPU 701 on at least one of the ROM 702, the EEPROM 704, the HD 705, and the recording medium 714, and stores various data (or information) in the storage unit 7000 and reads various data (or information) from the storage unit 7000. In this embodiment, the storage / reading unit 79 functions as an example of a storage control means.

[0112] ●Hybrid event management table● Fig. 12 is a conceptual diagram showing an example of a hybrid event management table according to an embodiment. Note that the structure and contents of the data table described below are merely examples and are not limited to these. A hybrid event management DB 7001 configured with a hybrid event management table as shown in Fig. 12 is constructed in the storage unit 7000. In the hybrid event management table, an event ID and a venue link (URL information) are associated with each hybrid event ID, stored, and managed.

[0113] Among these, the hybrid event ID represents identification information for identifying a hybrid event that is held using both a physical space and a virtual space.

[0114] In this embodiment, the hybrid event management table (hybrid event management DB 7001) functions as an example of a hybrid event management means.

[0115] <Metaverse Management Server Functionality Configuration> Next, the functional configuration of the metaverse management server 8 will be described. As shown in FIG. 7C, the metaverse management server 8 has a transmission / reception unit 81, an acquisition unit 83, an execution processing unit 88, and a storage / reading unit 89. Each of these functional units is a function or means realized by operating any of the hardware resources shown in FIG. 6 by an instruction from the CPU 801 according to a program for the metaverse management server 8 expanded from at least one of the ROM 802, EEPROM 804, HD 805, and recording medium 814 to the RAM 803. The metaverse management server 8 also has a storage unit 8000 (an example of a storage unit) constructed by at least one of the ROM 802, EEPROM 804, HD 805, and recording medium 814 shown in FIG. 6. In addition, a communication program (communication application), a browser application, etc. for communicating with the communication terminal 3, the event management server 6, the PC 9, etc. via the communication network 100 are installed and stored in the storage unit 8000.

[0116] <<Metaverse Management Server Functional Configuration>> Next, a detailed description will be given of each functional configuration of the metaverse management server 8. The transmission / reception unit 81 of the metaverse management server 8 shown in Fig. 7C is mainly realized by processing of the CPU 801 on the network I / F 850 ​​and the short-range communication I / F 808, and transmits and receives various data (or information) to and from the PC 9 and the like via the communication network 100. In this embodiment, the transmission / reception unit 81 functions as an example of at least one of a transmission means and a reception means.

[0117] The acquisition unit 83 is mainly realized by the processing of the CPU 801, and acquires various information (data) received through communication with the PC 9 etc. In this embodiment, the acquisition unit 83 functions as an example of an acquisition unit.

[0118] The execution processing unit 88 is mainly realized by the processing of the CPU 801, and executes various processes in the metaverse management server 8. In this embodiment, the execution processing unit 88 functions as an example of an execution means.

[0119] The storage / reading unit 89 is mainly realized by processing of the CPU 801 on at least one of the ROM 802, the EEPROM 804, the HD 805, and the recording medium 814, and stores various data (or information) in the storage unit 8000 and reads various data (or information) from the storage unit 8000. In this embodiment, the storage / reading unit 89 functions as an example of a storage control means.

[0120] [Processing or Operation of the Embodiment] Next, each process or operation in the information processing system according to the first embodiment will be described with reference to FIGS.

[0121] ●Example of the screen display for maintenance notification● Fig. 13 is a diagram showing an example of an event schedule registration screen according to the embodiment. In Fig. 13, an event schedule registration screen 4111 is displayed by the display control unit 44 of the information processing device 4. This event schedule registration screen 4111 may be displayed on the information processing device 4 based on preset information prior to processing in various sequence diagrams described later.

[0122] The event schedule registration screen 4111 displays an overview of an event, which is an example of an event, including the event name, organizer, date and time, participants, the location in the physical space, and the metaverse in the virtual space. The event schedule registration screen 4111 further displays an edit button 4151 for editing the various information described above, a close button 4152 for closing the event schedule registration screen 4111, and a copy button 4153 for copying invitation information.

[0123] <Display list of events associated with device> Fig. 14 is a sequence diagram showing an example of processing including an event list display process associated with a device according to the embodiment. Note that the sequence diagram shown in Fig. 14 is an example, and is not limited to this. In the first embodiment, the explanation will be given on the assumption that a predetermined communication is established between the communication terminal 3 and the user management server 5, and between the communication terminal 3 and the event management server 6, and that they are in a communicable state. The following explanation will be given on the assumption that a predetermined communication is established between other devices, terminals, and each server, and that they are in a communicable state.

[0124] First, the operation acceptance unit 32 of the communication terminal 3 accepts a start-up operation (step S11). Specifically, the operation acceptance unit 32 accepts a start-up operation performed on the power switch 322 and the selection switches 323 of the communication terminal 3 by the user who uses the communication terminal 3.

[0125] Next, the transmitting / receiving unit 31 of the communication terminal 3 transmits a device authentication request to the user management server 5 (step S12). As a result, the transmitting / receiving unit 51 of the user management server 5 receives the device authentication request transmitted by the communication terminal 3. At this time, the device authentication request includes authentication information generated from the certificate information and the private key.

[0126] Next, the authentication processing unit 58 of the user management server 5 executes device authentication processing (step S13). Specifically, the authentication processing unit 58 searches the user management DB 5001 (see FIG. 8) via the storage and reading unit 59 using the certificate information and private key information included in the device authentication request received in step S12 as search keys, and checks whether the information matches the information managed in the user management DB 5001. A case where the device authentication is successful will be described below.

[0127] Next, the transmitting / receiving unit 51 transmits a device authentication response to the communications terminal 3 (step S14). Specifically, the transmitting / receiving unit 51 transmits the access token read in step S13 as a response to the device authentication request received in step S12. As a result, the transmitting / receiving unit 31 of the communications terminal 3 receives the access token transmitted by the user management server 5.

[0128] Next, the transmitting / receiving unit 31 of the communication terminal 3 transmits a communication terminal event list acquisition request to the event management server 6 (step S15). As a result, the transmitting / receiving unit 61 of the event management server 6 receives the communication terminal event list acquisition request transmitted by the communication terminal 3. At this time, the communication terminal event list acquisition request includes the access token received in step S14. Note that the access token includes a user ID (organizer ID) that identifies the user.

[0129] Next, the acquisition unit 63 of the event management server 6 acquires the event list information (step S16). Specifically, the acquisition unit 63 searches the event management DB 6001 (see FIG. 9) via the storage and reading unit 59 using the organizer ID (user ID) in the access token included in the communication terminal event list acquisition request received in step S15 as a search key, thereby reading out the event list information corresponding to the event for which the acquisition unit 63 is the organizer. The event list information read out at this time includes, for example, the event ID, event content (event name), start date and time, and end date and time.

[0130] Next, the transmitting / receiving unit 61 transmits a communication terminal event list acquisition response to the communication terminal 3 (step S17). Specifically, the transmitting / receiving unit 61 transmits a communication terminal event list acquisition response including the event list information acquired in step S16 as a response to the communication terminal event list acquisition request received in step S15. As a result, the transmitting / receiving unit 31 of the communication terminal 3 receives the communication terminal event list acquisition response transmitted by the user management server 5. At this time, the communication terminal event list acquisition response includes data for displaying an event list screen (event ID, event content (event name), start date and time, end date and time, etc.). As a result, the acquiring unit 33 acquires data including the event ID via the transmitting / receiving unit 31.

[0131] Next, the display control unit 34 of the communication terminal 3 displays an event list screen (step S18). Specifically, the display control unit 34 displays the event list screen including the event details, start date and time, end date and time, the event location link (URL information), etc., on the display 380 of the communication terminal 3.

[0132] ●Example of a screen display of a list of events associated with a device● FIG. 15 is a diagram showing an example of an event list display screen associated with a device according to the embodiment. In FIG. 15, an event list screen 3111 is displayed by the display control unit 34 of the communication terminal 3. The event list screen 3111 displays the current date and time, and an event ID, an event name, a start date and time, and an end date and time as a list of events held (being held) using the communication terminal 3 near that date and time. However, since the event ID and the event name (event content) are information associated with each other, when the event name is displayed, the display of the event ID may be omitted. The event list screen 3111 further displays a participation button 3151. This allows a user who wishes to participate in a specific event to select a desired event and operate the participation button 3151 to participate in the event.

[0133] <Event list display process associated with user> Fig. 16 is a sequence diagram showing an example of a process including a process for displaying a list of events associated with a user according to the embodiment. Note that the sequence diagram shown in Fig. 16 is an example, and the process is not limited to this.

[0134] First, the operation acceptance unit 32 of the communication terminal 3 accepts an input operation of login information (step S21). Specifically, the operation acceptance unit 32 accepts an input operation of login information by a user who uses the communication terminal 3.

[0135] Next, the transmitting / receiving unit 31 of the communication terminal 3 transmits a user authentication request to the user management server 5 (step S22). As a result, the transmitting / receiving unit 51 of the user management server 5 receives the user authentication request transmitted by the communication terminal 3. At this time, the user authentication request includes the email address and password given to the user who inputted the login information.

[0136] Next, the authentication processing unit 58 of the user management server 5 executes user authentication processing (step S23). Specifically, the authentication processing unit 58 searches the user management DB 5001 (see FIG. 8) via the storage and reading unit 59 using the email address and password included in the user authentication request received in step S22 as search keys, and checks whether they match the information managed in the user management DB 5001. A case where the user authentication is successful will be described below.

[0137] Next, the transmitting / receiving unit 51 transmits a user authentication response to the communications terminal 3 (step S24). Specifically, the transmitting / receiving unit 51 transmits the access token read in step S23 as a response to the user authentication request received in step S22. As a result, the transmitting / receiving unit 31 of the communications terminal 3 receives the access token transmitted by the user management server 5.

[0138] Next, the transmitting / receiving unit 31 of the communication terminal 3 transmits a request to acquire a list of events for the user to the event management server 6 (step S25). As a result, the transmitting / receiving unit 61 of the event management server 6 receives the request to acquire a list of events for the user transmitted by the communication terminal 3. At this time, the request to acquire a list of events for the user includes the access token received in step S24. Note that the access token includes a user ID (organizer ID) that identifies the user.

[0139] Next, the acquisition unit 63 of the event management server 6 acquires the event list information (step S26). Specifically, the acquisition unit 63 searches the event management DB 6001 (see FIG. 9) via the storage and reading unit 59 using the organizer ID (user ID) in the access token included in the user's event list acquisition request received in step S25 as a search key, thereby reading out the event list information corresponding to the event for which the acquisition unit 63 is the organizer. The event list information read out at this time includes, for example, the event ID, event content (event name), start date and time, and end date and time.

[0140] Next, the transmitting / receiving unit 61 transmits a user's event list acquisition response to the communications terminal 3 (step S27). Specifically, the transmitting / receiving unit 61 transmits a user's event list acquisition response including the event list information acquired in step S26 as a response to the user's event list acquisition request received in step S25. As a result, the transmitting / receiving unit 31 of the communications terminal 3 receives the user's event list acquisition response transmitted by the event management server 6. At this time, the user's event list acquisition response includes data for displaying an event list screen (event ID, event content (event name), start date and time, end date and time, etc.).

[0141] Next, the display control unit 34 of the communication terminal 3 displays an event list screen (step S28). Specifically, the display control unit 34 displays the event list screen including the event details, start date and time, end date and time, the event location link (URL information), etc., on the display 380 of the communication terminal 3.

[0142] In the information processing system 1 according to the present embodiment, for example, when the processes of steps S12 and S14, and steps S22 and S24 described above are executed, other devices, etc. may be present between the communication terminal 3 and the user management server 5. In other words, each piece of information (data) transmitted and received between the communication terminal 3 and the user management server 5 may be configured to be transmitted and received once via another device, etc. The above-mentioned configuration can be applied even when other processing steps exist between the communication terminal 3 and the user management server 5.

[0143] Furthermore, in the information processing system 1 according to the present embodiment, for example, when the processes of steps S15 and S17, and steps S25 and S27 described above are executed, other devices, etc. may be present between the communication terminal 3 and the event management server 6. In other words, each piece of information (data) transmitted and received between the communication terminal 3 and the event management server 6 may be configured to be transmitted and received once via another device, etc. The above-described configuration can be applied even when other processing steps exist between the communication terminal 3 and the event management server 6.

[0144] ●Example of a screen display of a list of events associated with a user● Fig. 17 is a diagram showing an example of an event list display screen associated with a user according to the embodiment. In Fig. 17, an event list screen 3112 is displayed by the display control unit 34 of the communication terminal 3. The event list screen 3112 displays the current date and time and a list of events (meetings) associated with user A near that date and time. The event list screen 3112 further displays a participation button 3152. This allows a user who wishes to participate in a specific event to select a desired event and operate the participation button 3152 to participate in the event.

[0145] <Event participation processing from communication terminals> FIG. 18 is a sequence diagram illustrating an example of an event participation process from a communication terminal according to the embodiment.

[0146] First, the operation reception unit 32 of the communication terminal 3 receives an operation to select an event to attend (step S31). Specifically, the operation reception unit 32 receives an operation to select an event to attend by a user who uses the communication terminal 3. Note that in many cases, there are no restrictions on the use of the communication terminal 3. In such cases, all users in the conference room as a physical space can use the communication terminal 3. On the other hand, access restrictions may be set for the conference information and the virtual reality hybrid event (conference). In that case, authentication using a password or the like may be applied when acquiring details of the conference.

[0147] ●Password information input screen● Fig. 19 is a diagram showing an example of a password information input screen according to the embodiment. In Fig. 19, a password information input screen 3113 is displayed by the display control unit 34 of the communication terminal 3. The password information input screen 3113 displays a password input area for inputting a password, an OK button 3153, and a cancel button 3154. This makes it possible to provide a mechanism that prevents the details of a conference from being obtained unless authentication by inputting a password or the like is cleared.

[0148] 18, the transmitting / receiving unit 31 of the communication terminal 3 transmits a request to acquire event detailed information to the event management server 6 (step S32). As a result, the transmitting / receiving unit 61 of the event management server 6 receives the request to acquire event detailed information transmitted by the communication terminal 3. At this time, the request to acquire event detailed information contains event information including the event ID, an access token, and password information provided as necessary.

[0149] Next, the acquisition unit 63 of the event management server 6 acquires the event details information (step S33). Specifically, the acquisition unit 63 searches the event management DB 6001 (see FIG. 9) via the storage and reading unit 69 using the access token included in the event details information received in step S32 as a search key, thereby reading out the corresponding event details information. At this time, the event details information includes a link (URL information) to the event location as data for displaying an event details screen.

[0150] Next, the transmitting / receiving unit 61 transmits an event detail information acquisition response to the communications terminal 3 (step S34). Specifically, the transmitting / receiving unit 61 transmits the event detail information read out in step S33 as a response to the event detail information acquisition request received in step S32. As a result, the transmitting / receiving unit 31 of the communications terminal 3 receives the event detail information acquisition response. At this time, the event detail information acquisition response includes data for displaying an event detail screen (event ID, event content (event name), start date and time, end date and time, participant names, venue link (URL information), etc.).

[0151] Next, the display control unit 34 of the communication terminal 3 displays an event details screen (step S35). Note that the display screen in this process may have the same content as the event schedule registration screen 4111 shown in FIG.

[0152] Next, the operation acceptance unit 32 accepts an operation to participate in the event (step S36). Specifically, the operation acceptance unit 32 accepts an operation on a participation button or the like for participating in a predetermined event by the user.

[0153] Next, the transmitting / receiving unit 31 transmits a connection request to the virtual reality hybrid event to the virtual reality hybrid event management server 7 (step S37). As a result, the transmitting / receiving unit 71 of the virtual reality hybrid event management server 7 receives the connection request to the virtual reality hybrid event transmitted by the communication terminal 3. At this time, the connection request to the virtual reality hybrid event includes the access token and URL information indicating a link to the location of the virtual reality hybrid event included in the event details information.

[0154] Next, the connection processing unit 78 of the virtual reality hybrid event management server 7 executes a connection process for the virtual reality hybrid event (step S38). Specifically, the connection processing unit 78 executes a connection process for the virtual reality hybrid event based on the URL information included in the connection request for the virtual reality hybrid event received in step S37.

[0155] Next, the transmission / reception unit 71 transmits a connection response to the virtual reality hybrid event to the communication terminal 3 (step S39). Specifically, the transmission / reception unit 71 transmits the connection response to the virtual reality hybrid event to the communication terminal 3 as a response to the connection request to the virtual reality hybrid event received in step S37. As a result, the transmission / reception unit 31 of the communication terminal 3 receives the connection response to the virtual reality hybrid event transmitted by the virtual reality hybrid event management server 7.

[0156] Next, the transmitting / receiving unit 31 of the communication terminal 3 transmits an event participation request to the event management server 6 (step S40). As a result, the transmitting / receiving unit 61 of the event management server 6 receives the event participation request transmitted by the communication terminal 3. At this time, the event participation request includes the access token and the event ID.

[0157] Next, the execution processing unit 68 of the event management server 6 executes the participation process for the event, and the registration unit 66 registers the event information (step S41). Specifically, after the execution processing unit 68 executes the participation process for the predetermined event, the registration unit 66 registers the user ID and participation date and time associated with the event ID received in step S40 for each event ID managed in the event management DB 6003 (see FIG. 11). The participation date and time may be the date and time when the event participation request was received in step S40, or may be the date and time when the process of step S41 was executed.

[0158] Next, the transmitting / receiving unit 61 transmits an event participation response to the communication terminal 3 (step S42). Specifically, the transmitting / receiving unit 61 transmits the event participation response to the communication terminal 3 as a response to the event participation request received in step S40. At this time, there is no limitation on the content of the event participation response as long as it is information indicating participation in the event.

[0159] In the information processing system 1 according to the present embodiment, for example, when the processes of steps S37 and S39 described above are executed, other devices or the like may be present between the communication terminal 3 and the virtual reality hybrid event management server 7. In other words, each piece of information (data) transmitted and received between the communication terminal 3 and the virtual reality hybrid event management server 7 may be configured to be transmitted and received once via another device or the like. The above-described configuration can be applied even when other processing steps are present between the communication terminal 3 and the virtual reality hybrid event management server 7.

[0160] <Displaying the list of events associated with the metaverse> FIG. 20 is a sequence diagram illustrating an example of a process including a process for displaying a list of events associated with the metaverse according to the embodiment.

[0161] First, the operation acceptance unit 92 of the PC 9 accepts an input operation of login information (step S51). Specifically, the operation acceptance unit 92 accepts an input operation of login information by the user who uses the communication terminal 3.

[0162] Next, the transmitting / receiving unit 91 of the PC 9 transmits a user authentication request to the user management server 5 (step S52). As a result, the transmitting / receiving unit 51 of the user management server 5 receives the user authentication request transmitted by the PC 9. At this time, the user authentication request includes a user ID and a password for authenticating the user.

[0163] Next, the authentication processing unit 58 of the user management server 5 executes a user authentication process (step S53). Specifically, the authentication processing unit 58 searches the user management DB 5001 (see FIG. 8) via the storage / reading unit 59 using the user ID and password included in the user authentication request received in step S52 as search keys, thereby reading out the corresponding access token.

[0164] Next, the transmitting / receiving unit 51 transmits a user authentication response to the PC 9 (step S54). As a result, the transmitting / receiving unit 91 of the PC 9 receives the user authentication response transmitted by the user management server 5. At this time, the user authentication response includes an access token.

[0165] Next, the operation acceptance unit 92 of the PC 9 accepts an operation for using the metaverse (step S55). Specifically, the operation acceptance unit 92 accepts an operation for using the metaverse operated by the user.

[0166] Next, the transmitting / receiving unit 91 of the PC 9 transmits a metaverse event list acquisition request to the event management server 6 (step S56). As a result, the transmitting / receiving unit 61 of the event management server 6 receives the metaverse event list acquisition request transmitted by the PC 9. At this time, the metaverse event list acquisition request includes an access token and a user ID capable of identifying the metaverse.

[0167] Next, the acquisition unit 63 of the event management server 6 acquires the metaverse event list information (step S57). Specifically, the acquisition unit 63 searches the event management DB 6001 (see FIG. 9) via the storage and reading unit 69 using the user's login information (user ID) included in the metaverse event list acquisition request received in step S56 as a search key, thereby reading out the corresponding event list information. The event list information read out at this time includes, for example, the event ID, event content (event name), start date and time, and end date and time.

[0168] Next, the transmitting / receiving unit 61 transmits a metaverse event list acquisition response to the PC 9 (step S58). Specifically, the transmitting / receiving unit 61 transmits a metaverse event list acquisition response including the metaverse event list information acquired in step S57 as a response to the metaverse event list acquisition request received in step S56. As a result, the transmitting / receiving unit 91 of the PC 9 receives the metaverse event list acquisition response transmitted by the event management server 6. At this time, the metaverse event list acquisition response includes the event ID, organizer ID (user ID), event content, start date and time, end date and time, event location link (URL information), and participant information for the ongoing event as data for displaying the metaverse event list screen.

[0169] Next, the display control unit 94 of the PC 9 displays the metaverse event list screen (step S59). Specifically, the display control unit 94 displays the metaverse event list screen on the display 907 of the PC 9.

[0170] In the information processing system 1 according to this embodiment, for example, when the processes of steps S52 and S54 described above are executed, other devices, etc. may exist between the PC 9 and the user management server 5. In other words, each piece of information (data) transmitted and received between the PC 9 and the user management server 5 may be configured to be transmitted and received once via another device, etc. The above-mentioned configuration can be applied even when other processing steps exist between the PC 9 and the user management server 5.

[0171] Furthermore, in the information processing system 1 according to this embodiment, for example, when the processes of steps S56 and S58 described above are executed, other devices may exist between the PC 9 and the event management server 6. In other words, each piece of information (data) transmitted and received between the PC 9 and the event management server 6 may be configured to be transmitted and received once via another device. The above-mentioned configuration can be applied even when other processing steps exist between the PC 9 and the event management server 6.

[0172] ●Example of the Metaverse event list screen● FIG. 21 is a diagram illustrating an example of an event list display screen of the metaverse according to the embodiment. 21, an event list screen 9111 is displayed by the display control unit 94 of the PC 9. A list of events in the metaverse is displayed on the event list screen 9111. The event list screen 9111 further displays a participation button 9151 for participating in the event, and a non-participation button 9152 for not participating in the event. This allows a user who wishes to participate in a specific event to select a desired event and operate the participation button 9151 to participate in the event.

[0173] <Display process for the list of events associated with a user> FIG. 22 is a sequence diagram illustrating an example of processing including a process for displaying a list of events associated with a user according to the embodiment.

[0174] First, the operation acceptance unit 92 of the PC 9 accepts an input operation of login information (step S61). Specifically, the operation acceptance unit 92 accepts an input operation of login information by the user who uses the communication terminal 3.

[0175] Next, the transmitting / receiving unit 91 of the PC 9 transmits a user authentication request to the user management server 5 (step S62). As a result, the transmitting / receiving unit 51 of the user management server 5 receives the user authentication request transmitted by the PC 9. At this time, the user authentication request includes a user ID and a password for authenticating the user.

[0176] Next, the authentication processing unit 58 of the user management server 5 executes a user authentication process (step S63). Specifically, the authentication processing unit 58 searches the user management DB 5001 (see FIG. 8) via the storage / reading unit 59 using the user ID and password included in the user authentication request received in step S62 as search keys, thereby reading out the corresponding access token.

[0177] Next, the transmitting / receiving unit 51 transmits a user authentication response to the PC 9 (step S64). As a result, the transmitting / receiving unit 91 of the PC 9 receives the user authentication response transmitted by the user management server 5. At this time, the user authentication response includes an access token.

[0178] Next, the operation acceptance unit 92 of the PC 9 accepts an operation for using the metaverse (step S65). Specifically, the operation acceptance unit 92 accepts an operation for using the metaverse (virtual space) operated by the user.

[0179] Next, the transmitting / receiving unit 91 of the PC 9 transmits a request to acquire a list of events for the user to the event management server 6 (step S66). As a result, the transmitting / receiving unit 61 of the event management server 6 receives the request to acquire a list of events for the user transmitted by the PC 9. At this time, the request to acquire a list of events for the metaverse includes an access token and a user ID capable of identifying the metaverse.

[0180] Next, the acquisition unit 63 of the event management server 6 acquires the event list information of the user (step S67). Specifically, the acquisition unit 63 searches the event management DB 6001 (see FIG. 9) via the storage and reading unit 69 using the user's login information (user ID) included in the user's event list acquisition request received in step S66 as a search key, thereby reading out the corresponding event list information. The event list information read out at this time includes, for example, the event ID, event content (event name), start date and time, and end date and time.

[0181] Next, the transmitting / receiving unit 61 transmits a user's event list acquisition response to the PC 9 (step S68). Specifically, the transmitting / receiving unit 61 transmits a user's event list acquisition response including the user's event list information acquired in step S67 as a response to the user's event list acquisition request received in step S66. As a result, the transmitting / receiving unit 91 of the PC 9 receives the user's event list acquisition response transmitted by the event management server 6. At this time, the user's event list acquisition response contains the event ID, organizer ID (user ID), event content, start date and time, end date and time, event location link (URL information), and participant information for the ongoing event as data for displaying the user's event list screen.

[0182] Next, the display control unit 94 of the PC 9 displays the user's event list screen (step S69). Specifically, the display control unit 94 displays the user's event list screen on the display 907 of the PC 9.

[0183] <Event participation coordination process between communication terminals and the metaverse> Next, a description will be given of a process of linking a communication terminal and a metaverse to participate in an event, Fig. 23A is a sequence diagram showing an example of a process including a process of linking a communication terminal and a metaverse to participate in an event according to an embodiment.

[0184] First, the operation acceptance unit 92 of the PC 9 accepts an operation to select an event to attend (step S71). Specifically, the operation acceptance unit 92 accepts an operation to select an event to attend by a user who uses the PC 9.

[0185] Next, the transmitting / receiving unit 91 of the PC 9 transmits a request to acquire event detailed information to the event management server 6 (step S72). As a result, the transmitting / receiving unit 61 of the event management server 6 receives the request to acquire event detailed information transmitted by the PC 9. At this time, the request to acquire event detailed information includes event information including an event ID, and an access token. At this time, the request to acquire event detailed information includes event information, an access token, and password information provided as necessary.

[0186] Next, the acquisition unit 63 of the event management server 6 acquires the event details information (step S73). Specifically, the acquisition unit 63 searches the event management DB 6001 (see FIG. 9) via the storage and reading unit 69 using the access token included in the event details information received in step S72 as a search key, thereby reading out the corresponding event details information. At this time, the event details information includes a link (URL information) to the event location as data for displaying an event details screen.

[0187] Next, the transmitting / receiving unit 61 transmits an event detail information acquisition response to the PC 9 (step S74). Specifically, the transmitting / receiving unit 61 transmits the event detail information read out in step S73 as a response to the event detail information acquisition request received in step S72. As a result, the transmitting / receiving unit 91 of the PC 9 receives the event detail information acquisition response. At this time, the event detail information acquisition response includes data for displaying an event detail screen (such as a venue link (URL information)).

[0188] Next, the display control unit 94 of the PC 9 displays an event details screen (step S75). Note that the display screen in this process may have the same contents as the event schedule registration screen 4111 shown in FIG.

[0189] FIG. 23B is a sequence diagram illustrating another example of the process including the cooperation process of the communication terminal and the metaverse event participation according to the embodiment.

[0190] First, the operation acceptance unit 92 of the PC 9 accepts an operation to participate in the event (step S81). Specifically, the operation acceptance unit 92 accepts an operation to participate in the event by a user who uses the PC 9.

[0191] Next, the transmitting / receiving unit 91 of the PC 9 transmits a connection request to the virtual reality hybrid event to the virtual reality hybrid event management server 7 (step S82). As a result, the transmitting / receiving unit 61 of the event management server 6 receives the connection request to the virtual reality hybrid event transmitted by the PC 9. At this time, the connection request to the virtual reality hybrid event includes URL information.

[0192] Next, the connection processing unit 78 of the virtual reality hybrid event management server 7 executes a process of connecting to the virtual reality hybrid event (step S83).

[0193] Next, the transmission / reception unit 61 transmits a connection response to the virtual reality hybrid event to the PC 9 (step S84). Specifically, the transmission / reception unit 61 transmits a result of the connection process to the virtual reality hybrid event executed in step S83 as a response to the connection request to the virtual reality hybrid event received in step S82. As a result, the transmission / reception unit 91 of the PC 9 receives the connection response to the virtual reality hybrid event.

[0194] Next, the transmitting / receiving unit 91 of the PC 9 transmits an event participation request to the event management server 6 (step S85). As a result, the transmitting / receiving unit 61 of the event management server 6 receives the event participation request transmitted by the PC 9. At this time, the event participation request includes an access token and an event ID as one piece of user identification information for identifying the user.

[0195] Next, the execution processing unit 68 of the event management server 6 executes the participation process for the event, and the registration unit 66 registers the event information (step S86). Specifically, after the execution processing unit 68 executes the participation process for the predetermined event, the registration unit 66 registers the event ID and participation date and time associated with the user ID received in step S85 for each event ID managed in the event management DB 6003 (see FIG. 11). The participation date and time may be the date and time when the event participation request was received in step S85, or may be the date and time when the process of step S86 was executed.

[0196] Next, the generating unit 67 of the event management server 6 generates an event participation notification (step S87). Specifically, the generating unit 67 generates a notification including an event name for displaying an event participation dialogue described later, names of participants in the event, URL information required for a connection request for a virtual reality hybrid event described later, and an event ID required for an event participation request described later, as the event participation notification. Note that in step S87, the generating unit 67 generates the event participation notification based on the participation date and time when any one of the communication terminals 3 and the PC 9 participated in a specific event. Furthermore, in step S87, the generating unit 67 generates a notification including an event name representing a specific event being executed and names of participants participating in the specific event, as the event participation notification.

[0197] Next, the transmitting / receiving unit 61 of the event management server 6 transmits the event participation notification generated in step S87 to the communication terminal 3 (step S88). As a result, the transmitting / receiving unit 31 of the communication terminal 3 receives the event participation notification transmitted by the event management server 6.

[0198] Meanwhile, the operation acceptance unit 32 of the communication terminal 3 accepts a start-up operation asynchronously with respect to the processes of steps S81 to S88 described above (step S91).

[0199] 23C is a sequence diagram showing another example of processing including a linking process of event participation between a communication terminal and the metaverse according to an embodiment. The display control unit 34 of the communication terminal 3 displays an event participation dialog (step S92). Specifically, the display control unit 34 causes the display 380 to display the event participation dialog as an example of an event participation notification received from the event management server 6. More specifically, the display control unit 34 causes the display 380 to display a dialog that a user of the communication terminal 3 can operate on the communication terminal 3 as an event participation notification.

[0200] ●Event participation dialogue screen● Fig. 24 is a diagram showing an example of an event participation dialogue screen according to the embodiment. In Fig. 24, an event participation dialogue 3114 is displayed by the display control unit 34 of the communication terminal 3. In the event participation dialogue 3114, a message that a meeting is being held, the names of participating users, a participation button 3155, and a cancel button 3156 are displayed. This allows a user who is scheduled to participate in a specific event but has not yet participated to participate in the specific event by operating the participation button 3155.

[0201] 23C, the operation acceptance unit 32 of the communication terminal 3 accepts an event participation notification (operation) (step S93). Specifically, the operation acceptance unit 32 accepts an operation on the participation button 3155 described in FIG.

[0202] Next, the transmitting / receiving unit 31 transmits a connection request to the virtual reality hybrid event to the virtual reality hybrid event management server 7 (step S94). As a result, the transmitting / receiving unit 71 of the virtual reality hybrid event management server 7 receives the connection request to the virtual reality hybrid event transmitted by the communication terminal 3. At this time, the connection request to the virtual reality hybrid event includes URL information.

[0203] Next, the connection processing unit 78 of the virtual reality hybrid event management server 7 executes a process of connecting to the virtual reality hybrid event (step S95).

[0204] Next, the transmitting / receiving unit 71 transmits a connection response to the virtual reality hybrid event to the communications terminal 3 (step S96). Specifically, the transmitting / receiving unit 71 transmits a result of the connection process to the hybrid event executed in step S95 as a response to the connection request to the virtual reality hybrid event received in step S94. As a result, the transmitting / receiving unit 31 of the communications terminal 3 receives the connection response to the virtual reality hybrid event transmitted by the virtual reality hybrid event management server 7.

[0205] Next, the transmitting / receiving unit 31 of the communication terminal 3 transmits an event participation request to the event management server 6 (step S97). As a result, the transmitting / receiving unit 61 of the event management server 6 receives the event participation request transmitted by the communication terminal 3. At this time, the event participation request includes an access token and an event ID as one piece of user identification information for identifying the user.

[0206] Next, the execution processing unit 68 executes a process for participating in the event, and the registration unit 66 registers the event information (step S98). Specifically, after the execution processing unit 68 executes a process for participating in a predetermined event, the registration unit 66 registers the event-related information (event ID, event ID, and participation date and time) received in step S97 for each event ID managed in the event management DB 6003 (see FIG. 11). The participation date and time may be the date and time when the event participation request was received in step S97, or may be the date and time when the process of step S98 was executed.

[0207] In the information processing system 1 according to the present embodiment, for example, when the processes of steps S82 and S84 described above are executed, other devices, etc. may be present between the PC 9 and the virtual reality hybrid event management server 7. In other words, each piece of information (data) transmitted and received between the PC 9 and the virtual reality hybrid event management server 7 may be configured to be transmitted and received once via another device, etc. The above-described configuration can be applied even when other processing steps exist between the PC 9 and the virtual reality hybrid event management server 7.

[0208] FIG. 23D is a sequence diagram illustrating another example of the process including the cooperation process of the communication terminal and the metaverse event participation according to the embodiment.

[0209] First, the execution processing unit 98 of the PC 9 performs a user authentication process of the PC (step S92). Note that the process of step S92 is similar to the user authentication process in the PC 9 described above, and therefore a detailed description thereof will be omitted.

[0210] First, the operation acceptance unit 32 of the communication terminal 3 accepts a start-up operation asynchronously with respect to the process of step S92 described above (step S101).

[0211] Next, the transmitting / receiving unit 31 transmits a connection request to the virtual reality hybrid event to the virtual reality hybrid event management server 7 (step S102). As a result, the transmitting / receiving unit 71 of the virtual reality hybrid event management server 7 receives the connection request to the virtual reality hybrid event transmitted by the communication terminal 3. At this time, the connection request to the virtual reality hybrid event includes URL information.

[0212] Next, the connection processing unit 78 of the virtual reality hybrid event management server 7 executes a process of connecting to the virtual reality hybrid event (step S103).

[0213] Next, the transmitting / receiving unit 71 transmits a connection response to the virtual reality hybrid event to the communication terminal 3 (step S104). Specifically, the transmitting / receiving unit 71 transmits a result of the connection process to the hybrid event executed in step S103 as a response to the connection request to the virtual reality hybrid event received in step S102. As a result, the transmitting / receiving unit 31 of the communication terminal 3 receives the connection response to the virtual reality hybrid event transmitted by the virtual reality hybrid event management server 7.

[0214] Next, the transmitting / receiving unit 31 of the communication terminal 3 transmits an event participation request to the event management server 6 (step S105). As a result, the transmitting / receiving unit 61 of the event management server 6 receives the event participation request transmitted by the communication terminal 3. At this time, the event participation request includes an access token and an event ID as one piece of user identification information for identifying the user.

[0215] Next, the execution processing unit 68 executes a process for participating in the event, and the registration unit 66 registers the event information (step S106). Specifically, after the execution processing unit 68 executes a process for participating in a predetermined event, the registration unit 66 registers the event-related information (event ID, event ID, and participation date and time) received in step S105 for each event ID managed in the event management DB 6003 (see FIG. 11). The participation date and time may be the date and time when the event participation request was received in step S97, or may be the date and time when the process of step S98 was executed.

[0216] Next, the generating unit 67 of the event management server 6 generates an event participation notification (step S107). Specifically, the generating unit 67 generates a notification including an event name for displaying an event participation dialogue described later, names of participants in the event, URL information required for a connection request for a virtual reality hybrid event described later, and an event ID required for an event participation request described later. Note that in step S107, the generating unit 67 generates the event participation notification based on the participation date and time when any one of the communication terminals 3 and the PC 9 participated in a specific event. Furthermore, in step S107, the generating unit 67 generates a notification including an event name representing a specific event being executed and names of participants participating in the specific event as the event participation notification.

[0217] Next, the transmitting / receiving unit 61 of the event management server 6 transmits the event participation notification generated in step S87 to the communication terminal 3 (step S108). As a result, the transmitting / receiving unit 31 of the communication terminal 3 receives the event participation notification transmitted by the event management server 6.

[0218] 23E is a sequence diagram showing another example of processing including a linkage process between a communication terminal and a metaverse event participation according to an embodiment. First, the display control unit 94 of the PC 9 causes the display 907 to display an event participation dialogue as an example of an event participation notification received from the event management server 6 (step S109). Specifically, the display control unit 94 causes the display 907 to display the event participation dialogue as an example of an event participation notification received from the event management server 6. More specifically, the display control unit 94 causes the display 907 to display a dialogue that a user using the PC 9 can operate on the PC 9 as an event participation notification.

[0219] Next, the operation acceptance unit 92 accepts an operation to participate in the event (step S110). Specifically, the operation acceptance unit 92 accepts an operation to participate in the event by the user who uses the PC 9.

[0220] Next, the transmitting / receiving unit 91 of the PC 9 transmits a connection request to the virtual reality hybrid event to the virtual reality hybrid event management server 7 (step S111). As a result, the transmitting / receiving unit 61 of the event management server 6 receives the connection request to the virtual reality hybrid event transmitted by the PC 9. At this time, the connection request to the virtual reality hybrid event includes URL information.

[0221] Next, the connection processing unit 78 of the virtual reality hybrid event management server 7 executes a process of connecting to the virtual reality hybrid event (step S112).

[0222] Next, the transmission / reception unit 61 transmits a connection response to the virtual reality hybrid event to the PC 9 (step S113). Specifically, the transmission / reception unit 61 transmits a result of the connection process to the virtual reality hybrid event executed in step S112 as a response to the connection request to the virtual reality hybrid event received in step S111. As a result, the transmission / reception unit 91 of the PC 9 receives the connection response to the virtual reality hybrid event.

[0223] Next, the transmitting / receiving unit 91 of the PC 9 transmits an event participation request to the event management server 6 (step S114). As a result, the transmitting / receiving unit 61 of the event management server 6 receives the event participation request transmitted by the PC 9. At this time, the event participation request includes an access token and an event ID as one piece of user identification information for identifying the user.

[0224] Next, the execution processing unit 68 of the event management server 6 executes the participation process for the event, and the registration unit 66 registers the event information (step S115). Specifically, after the execution processing unit 68 executes the participation process for the predetermined event, the registration unit 66 registers the event ID and participation date and time associated with the user ID included in the access token received in step S114 for each event ID managed in the event management DB 6003 (see FIG. 11). The participation date and time may be the date and time when the event participation request was received in step S114, or may be the date and time when the process of step S115 was executed.

[0225] <Event participation coordination process from the metaverse> Next, a linking process of event participation from the metaverse will be described. Fig. 25A is a sequence diagram showing an example of a process including a linking process of event participation from the metaverse according to the embodiment. Note that each process by PC9A and PC9B described later is executed by each function unit to which a code in the 90s shown in Fig. 7A is assigned.

[0226] First, the PCs 9 (PCs 9A and 9B) used by one or more users who use the metaverse and the event management server 6 execute the metaverse usage process through the event detail display process (step S120). Note that the process of step S120 (steps S61 to S69 and steps S71 to S75) is a compilation of the above-mentioned processes (external reference process), so a description thereof will be omitted.

[0227] Next, the operation acceptance unit 92 of the PC 9A used by the user A accepts an operation to participate in the event (step S121). Specifically, the operation acceptance unit 92 accepts an operation to participate in the event by the user using the PC 9.

[0228] Next, the transmitting / receiving unit 91 transmits a connection request to the virtual reality hybrid event to the virtual reality hybrid event management server 7 (step S122). As a result, the transmitting / receiving unit 71 of the virtual reality hybrid event management server 7 receives the connection request to the virtual reality hybrid event transmitted by the PC 9A. At this time, the connection request to the virtual reality hybrid event includes URL information indicating the execution destination of the virtual reality hybrid event included in the event detail information.

[0229] Next, the connection processing unit 78 of the virtual reality hybrid event management server 7 executes a process of connecting to the virtual reality hybrid event (step S123). Specifically, the connection processing unit 78 executes a process of connecting to the virtual reality hybrid event based on the URL information received in step S122.

[0230] Next, the transmission / reception unit 71 transmits a connection response to the virtual reality hybrid event to the PC 9A (step S124). Specifically, the transmission / reception unit 71 transmits a connection response to the virtual reality hybrid event to the PC 9A as a response to the connection request to the virtual reality hybrid event received in step S122. As a result, the transmission / reception unit 91 of the PC 9A receives the connection response to the virtual reality hybrid event transmitted by the virtual reality hybrid event management server 7.

[0231] Next, the transmitting / receiving unit 91 of the PC 9A transmits an event participation request to the event management server 6 (step S125). As a result, the transmitting / receiving unit 61 of the event management server 6 receives the event participation request transmitted by the PC 9A. At this time, the event participation request includes an access token and an event ID as one piece of user identification information for identifying the user.

[0232] Next, the execution processing unit 68 of the event management server 6 executes the participation process for the event, and the registration unit 66 registers the event information (step S126). Specifically, after the execution processing unit 68 executes the participation process for the predetermined event, the registration unit 66 registers the event ID and participation date and time associated with the user ID received in step S125 for each event ID managed in the event management DB 6003 (see FIG. 11). The participation date and time may be the date and time when the event participation request was received in step S125, or may be the date and time when the process of step S126 was executed.

[0233] Next, the transmitting / receiving unit 61 transmits an event participation response to the communication terminal 3 (step S127). Specifically, the transmitting / receiving unit 61 transmits the event participation response to the communication terminal 3 as a response to the event participation request received in step S125. At this time, there is no limitation on the content of the event participation response as long as it is information indicating participation in the event.

[0234] Next, the operation acceptance unit 92 of the PC 9B accepts a metaverse usage operation operated by the user B (step S128). Specifically, the operation acceptance unit 92 accepts a usage operation for the screen of the metaverse (virtual space) displayed on the PC 9B used by the user B.

[0235] Next, the transmitting / receiving unit 91 transmits a metaverse event list acquisition request to the event management server 6 (step S129). As a result, the transmitting / receiving unit 61 of the event management server 6 receives the metaverse event list acquisition request transmitted by PC 9B. At this time, the metaverse event list acquisition request includes the login information (user ID) of user B who uses PC 9B.

[0236] Next, the acquisition unit 63 of the event management server 6 acquires the event list information of the metaverse (step S130). Specifically, the acquisition unit 63 acquires the corresponding event list information by searching the event management DB 6001 (see FIG. 9) using the login information (user ID) received in step S129 as a search key. At this time, the event list information includes the event content, start date and time, end date and time, and the venue link (URL information).

[0237] Next, the transmitting / receiving unit 61 transmits a metaverse event list acquisition response to the PC 9B (step S131). Specifically, the transmitting / receiving unit 61 transmits a metaverse event list acquisition response including the metaverse event list information acquired in step S130 as a response to the metaverse event list acquisition request received in step S129. As a result, the transmitting / receiving unit 91 of the PC 9B receives the metaverse event list acquisition response transmitted by the event management server 6. At this time, the metaverse event list acquisition response includes the event ID, organizer ID (user ID), event content, start date and time, end date and time, event location link (URL information), and participant information for the event being held.

[0238] <Processing when included as a participant in an ongoing event> Next, a process in the case where a user is included in a participant of an ongoing event will be described. Fig. 25B is a sequence diagram showing another example of the process including a linking process of event participation from the metaverse according to the embodiment.

[0239] First, the transmitting / receiving unit 91 of the PC 9B used by the user B who will participate in the metaverse event transmits a connection request to the virtual reality hybrid event to the virtual reality hybrid event management server 7 (step S141). As a result, the transmitting / receiving unit 71 of the virtual reality hybrid event management server 7 receives the connection request to the virtual reality hybrid event transmitted by the PC 9B. At this time, the connection request to the virtual reality hybrid event includes URL information.

[0240] Next, the connection processing unit 78 of the virtual reality hybrid event management server 7 executes a process of connecting to the virtual reality hybrid event (step S142).

[0241] Next, the transmission / reception unit 71 transmits a response to the connection to the virtual reality hybrid event to the PC 9B (step S143). Specifically, the transmission / reception unit 71 transmits a result of the connection process to the virtual reality hybrid event executed in step S142 as a response to the connection request to the virtual reality hybrid event received in step S141. As a result, the transmission / reception unit 91 of the PC 9B receives the connection response to the virtual reality hybrid event.

[0242] Next, the transmitting / receiving unit 91 of PC 9B transmits an event participation request to the event management server 6 (step S144). As a result, the transmitting / receiving unit 61 of the event management server 6 receives the event participation request transmitted by PC 9B. At this time, the event participation request includes an access token and an event ID as one piece of user identification information for identifying the user.

[0243] Next, the execution processing unit 68 of the event management server 6 executes the participation process for the event, and the registration unit 66 registers the event information (step S145). Specifically, after the execution processing unit 68 executes the participation process for the predetermined event, the registration unit 66 registers the event ID and participation date and time associated with the user ID received in step S144 for each event ID managed in the event management DB 6003 (see FIG. 11). The participation date and time may be the date and time when the event participation request was received in step S144, or may be the date and time when the process of step S145 was executed.

[0244] <Processing if you are not a participant of an ongoing event> Next, a process for a case where a user is not included in the participants of an ongoing event will be described. Fig. 25C is a sequence diagram showing another example of a process including a linking process of event participation from the metaverse according to the embodiment.

[0245] First, the display control unit 94 of the PC 9B displays a request dialog (step S151). Specifically, the display control unit 94 displays the request dialog on the display 907 of the PC 9B. The request dialog will be described in detail later with reference to an example screen.

[0246] Next, the operation acceptance unit 92 accepts a participation request operation (step S152). Specifically, the operation acceptance unit 92 accepts a participation request operation (operation on a "request button" to be described later) in the request dialog displayed in step S151.

[0247] Next, the display control unit 94 displays a request waiting dialog (step S153). This display process is executed after the participation request operation in step S152. Specifically, the display control unit 94 displays the request waiting dialog on the display 907 of the PC 9B. The request waiting dialog will be described in detail with reference to a screen example described later.

[0248] Next, the transmitting / receiving unit 91 transmits a participation request to the event management server 6 (step S154). As a result, the transmitting / receiving unit 61 of the event management server 6 receives the participation request transmitted by the PC 9B. At this time, the participation request includes an access token and an event ID as a participation request.

[0249] Next, the transmitting / receiving unit 61 transmits a participation request to the PC 9A used by the user A who is already participating in the virtual reality hybrid event (step S155). As a result, the transmitting / receiving unit 91 of the PC 9A receives the participation request transmitted by the event management server 6. At this time, the participation request includes the user ID and the user name as the participation request.

[0250] Next, the display control unit 94 of the PC 9A displays the request dialog (step S156). Specifically, the display control unit 94 causes the display 907 of the PC 9A to display the request dialog.

[0251] Next, the operation acceptance unit 92 of the PC 9A accepts a request permission operation (step S157). Specifically, the operation acceptance unit 92 accepts a request permission operation (operation on a "permission button" described later) in the request dialog displayed in step S156.

[0252] Next, the transmitting / receiving unit 91 transmits a participation response to the event management server 6 (step S158). Specifically, the transmitting / receiving unit 91 transmits the participation response as a response to the participation request received in step S165 as a participation request. As a result, the transmitting / receiving unit 61 of the event management server 6 receives the participation response transmitted by PC 9A. At this time, the participation response includes the user ID that permitted the participation request and the event ID that identifies the event being participated in.

[0253] FIG. 25D is a sequence diagram showing another example of the process including the linking process of event participation from the metaverse according to the embodiment.

[0254] First, the transmitting / receiving unit 61 of the event management server 6 issues a participation request permission to the PC 9B used by user B (step S161). Specifically, the transmitting / receiving unit 61 transmits a participation request permission representing information permitting the participation request to the PC 9B used by user B as a response to the participation request received in step S154. As a result, the transmitting / receiving unit 91 of the PC 9B receives the participation request permission transmitted by the event management server 6.

[0255] Next, the transmitting / receiving unit 91 of the PC 9B transmits a connection request to the virtual reality hybrid event to the virtual reality hybrid event management server 7 (step S162). As a result, the transmitting / receiving unit 71 of the virtual reality hybrid event management server 7 receives the connection request to the virtual reality hybrid event transmitted by the PC 9B. At this time, the connection request to the virtual reality hybrid event includes a location link (URL information) where the virtual reality hybrid event is held.

[0256] Next, the connection processing unit 78 of the virtual reality hybrid event management server 7 executes a process of connecting to the virtual reality hybrid event (step S163). Specifically, the connection processing unit 78 executes a process of connecting to the virtual reality hybrid event based on the URL information received in step S162.

[0257] Next, the transmission / reception unit 71 transmits a connection response to the virtual reality hybrid event to the PC 9B (step S164). Specifically, the transmission / reception unit 71 transmits a connection response to the virtual reality hybrid event to the PC 9B as a response to the connection request to the virtual reality hybrid event received in step S162. As a result, the transmission / reception unit 91 of the PC 9B receives the connection response to the virtual reality hybrid event transmitted by the virtual reality hybrid event management server 7.

[0258] Next, the transmitting / receiving unit 91 of the PC 9B transmits an event participation request to the event management server 6 (step S165). As a result, the transmitting / receiving unit 61 of the event management server 6 receives the event participation request transmitted by the PC 9B. At this time, the event participation request includes an access token and an event ID as one piece of user identification information for identifying the user.

[0259] Next, the execution processing unit 68 of the event management server 6 executes the participation process for the event, and the registration unit 66 registers the event information (step S166). Specifically, after the execution processing unit 68 executes the participation process for the predetermined event, the registration unit 66 registers the event ID and participation date and time associated with the user ID received in step S165 for each event ID managed in the event management DB 6003 (see FIG. 11). The participation date and time may be the date and time when the event participation request was received in step S165, or may be the date and time when the process of step S166 was executed.

[0260] Example of the request dialog screen Here, a screen display example in the process of step S151 described above will be described. FIG. 26 is a diagram showing an example of a request request dialog according to the embodiment. In FIG. 26, a request request dialog 9111 is displayed by the display control unit 94 of the PC 9B. In the request request dialog 9111, a message is displayed indicating that the user is not a participant of the metaverse event (conference), and a message is displayed asking whether or not to request participation in the event (conference). In other words, the request request dialog 9111 is an example of a screen that prohibits use by anyone other than the participants of the schedule being held in the metaverse conference room. In the request request dialog 9111, a request button 9151 for requesting participation in the event and an exit button 9152 for exiting the event without participating are further displayed. As a result, a user who wants to participate in a specific event can request participation in the event by operating the request button 9151.

[0261] ●Example of the request waiting dialog screen● Here, a screen display example in the process of step S153 described above will be described. FIG. 27 is a diagram showing an example of a request waiting dialog according to the embodiment. In FIG. 27, a request waiting dialog 9112 is displayed by the display control unit 94 of the PC 9B. In the request waiting dialog 9112, a message that a request has been sent and a message that prompts the user to wait until approval are displayed. In the request waiting dialog 9112, an exit button 9153 is further displayed. This allows a user who has attempted to participate in an event to cancel a request operation in the request request dialog 9111, but who wishes to cancel the participation request for some reason.

[0262] ●Example of the request dialog screen● Here, a screen display example in the process of step S156 described above will be described. FIG. 28 is a diagram showing an example of a request dialog according to the embodiment. In FIG. 28, a request dialog 9113 is displayed by the display control unit 94 of the PC 9A. In the request dialog 9113, a message is displayed prompting the user who has requested the request to give permission or not. In the request dialog 9113, a permission button 9154 for allowing participation in the event and a permission / deny button 9155 for denying participation in the event are further displayed. This allows a user participating in a specific event to grant or deny participation to a user who has requested participation in the event.

[0263] <<Example of metaverse usage process>> Here, a specific example of the above-mentioned metaverse usage process will be described. FIG. 29 is a flowchart showing an example of the metaverse usage process according to the embodiment. In FIG. 29, the metaverse usage process executed in the PC 9B used by the user B who uses (uses) the metaverse to participate in the virtual reality hybrid event will be described. However, the control subject of each of the following processes in step S120 executed as the external reference process is not limited to the PC 9B, but may be a device or server appropriate for each process among the PCs 9 (PC 9A, PC 9B) used by one or more users, the event management server 6, and the virtual reality hybrid event management server 7. Note that the flowchart shown in FIG. 29 is an example of the details of the process of step S120, but is not limited thereto.

[0264] First, the acquisition unit 93 of the PC 9B acquires event information of the metaverse (step S120-1).

[0265] Next, the determination unit 95 determines whether or not an event is being held in the conference room (step S12-2).

[0266] If an event is being held in the conference room (step S120-2: YES), the determination unit 95 further determines whether the request is to participate in an event being held (step S120-3).

[0267] If the request is for participation in an event that is currently being held (step S120-3: YES), the execution processing unit 98 connects to the event that is currently being held and exits this flow (step S120-4).

[0268] On the other hand, if the request is not for participation in an ongoing event (step S120-3: NO), the display control unit 94 displays the request dialog shown in FIG. 26 on the display 907, and exits this flow (step S120-5).

[0269] Furthermore, if there is no event being held in the conference room in the determination process of step S120-2 (step S120-2: NO), the display control unit 94 displays a list of events in the metaverse on the display 907 and exits this flow (step S120-6).

[0270] ●Example of screen display when participating in a virtual reality hybrid event as a communication device● Here, a screen display example when participating in a virtual reality hybrid event will be described. FIG. 30 is a diagram showing an example of a screen for participating in a virtual reality hybrid event as a communication terminal according to an embodiment. In FIG. 30, for example, a virtual reality hybrid event screen 3121 is displayed on a display 380 by a display control unit 34 of a communication terminal 3, which uses an IFPD as an example. However, the virtual reality hybrid event screen 3121 is also displayed on a PC 9 used by a user at home or the like. In the virtual reality hybrid event screen 3121, a physical space display area 3121a, a virtual space display area 3121b, and a participant information display area 3121c are allocated, and a conference room A and participants using the IFPD, a conference room and avatars using the metaverse, and participant information are displayed, respectively. Note that the participant information displays the conference room name (IFPD conference room A) as a physical space and an icon of a user (avatar) participating using the metaverse, respectively. As a result, a user using the virtual reality hybrid event screen 3121 can see at a glance who is participating in which space and with what expression while a specific event (conference) is being held as a virtual reality hybrid event. In addition, the virtual reality hybrid event screen 3121 also has an exit button, which allows a user to exit the event (meeting) at any time.

[0271] ●Example of screen display when participating in a virtual reality hybrid event as a user● Fig. 31 is a diagram showing an example of a participation screen when participating in a virtual reality hybrid event as a user according to an embodiment. In Fig. 31, similar to Fig. 30, for example, a virtual reality hybrid event screen 3122 is displayed on the display 380 by the display control unit 34 of the communication terminal 3, which uses an IFPD as an example. In the virtual reality hybrid event screen 3122, a physical space display area 3122a, a virtual space display area 3122b, and a participant information display area 3122c are allocated, and the conference room A and participants using the IFPD, the conference room and avatars using the metaverse, and participant information are displayed, respectively.

[0272] The difference between the virtual reality hybrid event screen 3121 and the virtual reality hybrid event screen 3122 is the content displayed in the participant information display area. Whereas the virtual reality hybrid event screen 3121 displays information such as the conference room name (communication terminal name), the virtual reality hybrid event screen 3122 displays information on participants participating in a conference room (conference room A) that exists in a physical space. These participants are users who have participated in a schedule representing a specific event on a user-by-user basis authenticated by the IFPD. In this way, by displaying the virtual reality hybrid event screen 3121 (or 3122) including either information, the user can grasp the participation status of the event being held in detail.

[0273] <Processing for leaving (leaving) a conference room in the metaverse> Next, a process for exiting (leaving) a conference room in the metaverse will be described. Fig. 32 is a sequence diagram showing an example of a process including a process for requesting exit from a conference room in the metaverse according to an embodiment.

[0274] First, the event participation process of user A is executed as an external reference process by the PC 9A used by user A, the PC 9B used by user B, and the event management server 6 (step S170). As with step S120, the process of step S170 is a combination of the processes already described above, and therefore a description thereof will be omitted.

[0275] Next, a login process for user B to the metaverse is executed (step S180). The process of step S170 is also a combination of the processes already described above, similar to the external reference processes of steps S120 and S170, and therefore will not be described here.

[0276] Next, the transmitting / receiving unit 61 of the event management server 6 transmits an event holding time exceeded notification to the PC 9B (step S181). As a result, the transmitting / receiving unit 91 of the PC 9B receives the event holding time exceeded notification transmitted by the event management server 6. At this time, the event holding time exceeded notification includes the user ID of the metaverse conference room where the event end date and time has passed, and an event ID that identifies the event being held in the metaverse.

[0277] Next, the display control unit 94 of the PC 9B displays an exit icon (step S182). Specifically, the display control unit 94 displays the exit icon on the display 907 of the PC 9B. The screen on which this exit icon is displayed will be described below.

[0278] ●Exit icon screen display example● FIG. 33 is a diagram showing an example of a display screen of an exit icon when a virtual space (metaverse) according to an embodiment is viewed from above. In FIG. 33, for example, a state in which user A is using (utilizing) a conference room A existing in a physical space to participate in a specific event (conference) is shown as an exit request screen 9121. In the exit request screen 9121, an exit icon 9122 for requesting exit is displayed in the vicinity (for example, at a door) of the physical space (conference room A) in which user A is participating. In addition, the exit request screen 9121 displays the scheduled end time of the specific event (conference) in which user A is participating. This allows another user (user B) who encourages the user to leave to request the participants to leave the conference room A in which user A is participating.

[0279] 32, the operation acceptance unit 92 of the PC 9B accepts an exit request operation (step S183). Specifically, the operation acceptance unit 92 accepts a user operation on the exit icon 9122 displayed on the exit request screen 9121 shown in FIG.

[0280] Next, the transmitting / receiving unit 91 transmits an exit request to the event management server 6 (step S184). As a result, the transmitting / receiving unit 61 of the event management server 6 receives the exit request transmitted by the PC 9B. At this time, the exit request includes the access token and the event ID.

[0281] Next, the transmitting / receiving unit 61 of the event management server 6 transmits an exit request notification to the PC 9A (step S185). Specifically, the transmitting / receiving unit 61 transmits the exit request notification to the PC 9A of the user A who is participating in a specific event (conference) using the conference room A as the physical space. As a result, the transmitting / receiving unit 91 of the PC 9A receives the exit request notification transmitted by the event management server 6.

[0282] Next, the display control unit 94 of the PC 9A displays a wait message (step S186). Specifically, the display control unit 94 causes the display 907 to display a wait message in response to the exit request notification received in step S185.

[0283] ●Example of a waiting message screen● FIG. 34 is a diagram showing an example of a waiting message display screen according to an embodiment. In FIG. 34, for example, a waiting message display screen 9123 similar to that in FIG. 31 is displayed. In addition, the waiting message display screen 9123 displays a pop-up message indicating that the next user is waiting in front of the conference room. In other words, the waiting message display screen 9123 is an example of a screen when a request to leave is issued from outside the conference room of the metaverse when a predetermined time approaches the end date and time of the scheduled schedule, or when the end date and time of the scheduled schedule has passed. This allows a user (user A) using the conference room A to recognize that the end time of the conference is approaching.

[0284] [Major Effects of the First Embodiment] As described above, according to this embodiment, the generation unit 67 of the event management server 6 generates an event participation notification including the event name for displaying the event participation dialogue, the names of the participants in the event, URL information required for a connection request to a virtual reality hybrid event described later, and an event ID required for an event participation request described later (step S87), and the transmission / reception unit 61 transmits the generated event participation notification to the communication terminal 3 (step S88). This provides the effect that, when a predetermined event is executed in a state in which the physical space and the virtual space are associated with each other, a participant who has previously participated in one space can participate in the predetermined event without having to perform any participation processing for the other space.

[0285] Second Embodiment Next, a second embodiment will be described. FIG. 35 is a diagram showing an example of the overall configuration of an information processing system according to the second embodiment. In the second embodiment, a case will be described in which each user who uses one or more PCs 9 (an example of a second communication terminal) participates in a virtual reality hybrid event while wearing VR goggles 10. Note that the second embodiment is similar to the system configuration that constructs the information processing system 1 described in the first embodiment, the hardware configuration of each device and the communication terminal, and the functional configuration, and therefore, the same symbols are given to those having the same configuration and function, and their description will be omitted.

[0286] As shown in FIG. 35, the PC 9 and the VR goggles 10 (10A, 10B, . . . ) at each user's home are connected to a Wi-Fi router at each user's home via wireless LAN. In addition, the operation controller operated by each user is connected to the VR goggles 10 via, for example, Bluetooth. The operation controller has, for example, a menu display button, a pointer display button, and a confirmation button, and transmits the pressing information of these buttons to the VR goggles 10 via Bluetooth. Then, the VR goggles 10 transfers each pressing information to the metaverse management server 8. The operation controller further has a 6-axis acceleration / angular velocity sensor. The 6-axis acceleration / angular velocity sensor detects the direction and movement of the operation controller from each data of acceleration and angular velocity obtained from this sensor, and transmits this information to the VR goggles 10 via Bluetooth. The VR goggles 10 transfers this information to the metaverse management server 8. The metaverse management server 8 transmits screen data of the three-dimensional metaverse to the VR goggles 10, and the VR goggles 10 display a screen represented by the transmitted screen data on the display.

[0287] Meanwhile, the PC 9 uses a remote desktop function to transmit screen data to the metaverse management server 8. The metaverse management server 8 displays the screen data transmitted by the PC 9 in the three-dimensional metaverse space, and transmits the updated screen data of the three-dimensional metaverse space to the VR goggles 10. The VR goggles 10 displays a screen represented by the transmitted screen data. This allows each user at home to view the screen displayed on the PC 9 on the VR goggles 10.

[0288] Furthermore, each user at home wears the respective VR goggles 10 (10A, 10B, ...) and operates the menu displayed on the display of the VR goggles 10 using the operation controller. This allows each user to enter conference room A in the three-dimensional metaverse. The processing operation after entering conference room A is the same as the method described in the first embodiment.

[0289] It should be noted that a commonly used VR goggle can be used for the VR goggles 10. Therefore, in this embodiment, a detailed description of the hardware configuration and the functional configuration will be omitted.

[0290] ●Example of the screen displayed on VR goggles● FIG. 36 is a diagram showing an example of a three-dimensional metaverse screen displayed in the VR goggles according to the second embodiment. In FIG. 36, a metaverse screen 10011 is displayed in the image display portion of the VR goggles 10. On the metaverse screen 10011, avatars of other participants who are participating in the same event (conference) using the metaverse are simultaneously displayed in the metaverse conference room A space as a virtual reality hybrid event. This allows one or more users wearing the VR goggles 10 to participate in the event (conference) while watching the movements of the avatars of other participants who are participating in the same event (conference). This allows participation in an event (conference) with a sense of realism.

[0291] [Major Effects of the Second Embodiment] As described above, according to this embodiment, it is possible for users who participate in a virtual reality hybrid event using the metaverse to wear VR goggles, enabling them to participate in a immersive event (conference).

[0292] [Modification of the second embodiment] Here, a modified example of the second embodiment will be described. FIG. 37 is a diagram showing an example of a three-dimensional metaverse screen displayed in the VR goggles according to the modified example of the second embodiment. As shown in FIG. 37, in the modified example of the second embodiment, a metaverse screen 10021 including participants participating in the conference room A existing in the physical space is displayed among the display screens shown in FIG. 30, FIG. 31, and FIG. 34 in the screen displayed in the metaverse screen 10011 shown in FIG. 36. That is, the metaverse screen 10021 displayed on the VR goggles 10 displays not only the appearance of the user (avatar) participating in the event using the virtual space, but also information on the user participating in the event held in the conference room A existing in the physical space. In other words, the modified example of the second embodiment displays an image in the virtual space and an image in the physical space by synthesizing (combining) them on a display device (VR goggles) capable of displaying the virtual space. This makes it possible to share an image (information) in the virtual space and an image (information) in the physical space on the VR goggles 10.

[0293] [Major Effects of the Modification of the Second Embodiment] As described above, according to this embodiment, it is possible to provide a user using the virtual space through the VR goggles with a composite (combined) screen in which an avatar of a user wearing a VR goggle and using a virtual space and a participant participating in a specific event using a conference room in a physical space are combined (combined) in the VR goggles (on the VR goggles). This makes it possible for the user using the virtual space to understand the details of the event being held, and also makes it possible to provide information rich in variety and realism regarding the event being held.

[0294] [Supplementary description of the embodiment] Each function of the above-mentioned embodiment can be realized by one or more processing circuits. Here, the term "processing circuit" in this specification includes a device programmed to execute each function by software, such as a processor implemented by an electronic circuit. This device refers to, for example, a processor, an ASIC (Application Specific Integrated Circuit), a DSP (digital signal processor), an FPGA (field programmable gate array), a SOC (System on a chip), a GPU (Graphics Processing Unit), and a conventional circuit module designed to execute each function described above.

[0295] In the above-described embodiment, the information processing system 1 may be configured to execute various judgments in the above-described various processes by machine learning (learning using artificial intelligence: AI). This eliminates the need to use corresponding data tables.

[0296] Here, machine learning is a technology for making a computer acquire a human-like learning ability, and refers to a technology in which a computer autonomously generates an algorithm required for judgment such as data identification from learning data that is previously loaded, and applies this to new data to make predictions. The learning method for machine learning may be any of supervised learning, unsupervised learning, semi-supervised learning, reinforcement learning, and deep learning. The learning method for machine learning may further be a combination of these learning methods, and any learning method for machine learning is acceptable.

[0297] So far, an event management system, an event management device, an event management method, and a program according to one embodiment of the present invention have been described. However, the present invention is not limited to the above-described embodiment, and other embodiments may be added, modified, or deleted, etc., within the scope that can be conceived by a person skilled in the art. In any aspect, as long as the functions and effects of the present invention are achieved, it is included in the scope of the present invention.

[0298] ■ Summary ■ For example, aspects of the present invention are as follows.

[0299] <First aspect> The event management system 2 (an example of an event management system; omitted below) as a first aspect has a communication terminal 3 (an example of a first communication terminal; omitted below) used to execute a predetermined event, a PC 9 (an example of a second communication terminal; omitted below) used to execute a predetermined event via a virtual space, and an event management server 6 (an example of an event management device; omitted below) that manages information related to the predetermined event when the predetermined event is executed using the communication terminal 3 and the PC 9, and the event management server 6: The communication terminal has a generation unit 67 (an example of a generation means; omitted below) that generates an event participation notification to encourage the other communication terminal, which is scheduled to participate in the specified event but has not yet participated, to participate in the specified event after one of the communication terminals, either the communication terminal 3 or the PC 9, has performed a process for participating in a specified event, and a transmission / reception unit 61 (an example of a transmission means; omitted below) that transmits the generated event participation notification to the other communication terminal.

[0300] According to the first aspect, when a specified event is held with the physical space and the virtual space associated with each other, a participant who first joins one space can join the specified event without having to perform any joining process for the other space.

[0301] <Second aspect> The generating unit 67 of the event management server 6 as the second aspect generates an event participation notification based on the participation date and time when either the communication terminal 3 or the PC 9 participated in a predetermined event in the first aspect.

[0302] According to the second aspect, it is possible to obtain the same effect as that of the first aspect.

[0303] <Third aspect> The generation unit 67 of the event management server 6 as a third aspect generates, in the first or second aspect, a notification as an event participation notification including an event name representing a specific event that is being carried out and the names of participants participating in the specific event.

[0304] According to the third aspect, in addition to the effect of the first or second aspect, it becomes possible to provide more detailed information to participants who plan to participate in a specific event.

[0305] <Fourth aspect> The communication terminal 3 or PC 9 to which the event participation notification of the fourth aspect is sent has, in any of the first to third aspects, a transmission / reception unit 31 or a transmission / reception unit 91 (an example of a receiving means; omitted below) that receives the event participation notification sent by the event management server 6, and a display control unit 34 or a display control unit 94 (an example of a display control means; omitted below) that displays the received event participation notification on the display 380 or the display 907 (an example of a display means; omitted below).

[0306] According to the fourth aspect, participants who plan to participate in a given event can check a detailed event participation notification.

[0307] <Fifth aspect> The display control unit 34 or the display control unit 94 in the fifth aspect displays, as an event participation notification, a dialogue that the user of the communication terminal 3 or the PC 9 can operate on the communication terminal 3 or the PC 9 in the fourth aspect.

[0308] According to the fifth aspect, participants who plan to participate in a predetermined event can perform a desired operation in response to the displayed event participation notification.

[0309] <Sixth aspect> The event management server 6 as a sixth aspect further has a registration unit 66 (an example of a registration means; omitted below) that, in any of the first to fifth aspects, registers user identification information included in a request to participate in a specified event sent by the communication terminal 3 in association with participation date and time information indicating the date and time at which the specified event was participated.

[0310] According to the sixth aspect, it is possible to obtain the same effect as that of the first aspect.

[0311] <Seventh aspect> The event management server 6 as a seventh aspect further includes an execution processing unit 68 (an example of an execution means; hereinafter omitted) that executes a participation process for a predetermined event in any one of the first to fifth aspects, and the execution processing unit 68: A process for participating in a specified event based on a request from the communication terminal 3 is executed for either a schedule associated with the communication terminal 3 or a schedule associated with a user participating in a specified event executed in a physical space, and a process for participating in a specified event based on a request from the PC 9 is executed for either a schedule associated with the PC 9, a schedule associated with a user participating in a specified event executed in a virtual space, or a schedule represented by a specified event currently being executed.

[0312] According to the seventh aspect, it is possible to obtain the same effect as that of the first aspect.

[0313] <Eighth aspect> The predetermined event executed in the event management system 2 as the eighth aspect includes a conference, meeting, lecture, or class executed in the same time period in the physical space and the virtual space in any of the first to seventh aspects.

[0314] According to the eighth aspect, it is possible to obtain the same effect as the first aspect for various types of events.

[0315] <Ninth aspect> The event management server 6 (an example of an event management device; omitted below) of the ninth aspect exists in a physical space, and when a specific event is executed using a communication terminal 3 (an example of a first communication terminal; omitted below) used to execute a specific event, and a PC 9 (an example of a second communication terminal; omitted below) used to execute a specific event via a virtual space, manages information related to the specific event, and has a generation unit 67 (an example of a generation means; omitted below) that generates an event participation notification to encourage the other communication terminal that is scheduled to participate in the specific event but has not yet participated, to participate in the specific event, after the specific event is executed by one of the communication terminals 3 and the PC 9, and a transmission / reception unit 61 (an example of a transmission means; omitted below) that transmits the generated event participation notification to the other communication terminal.

[0316] According to the ninth aspect, similar to the first aspect, when a specified event is held with the physical space and the virtual space associated with each other, a participant who first joins one space can join the specified event without having to perform any joining process for the other space.

[0317] <Tenth aspect> An event management server 6 (an example of an event management device; omitted below) as a tenth aspect manages information related to a specific event when the specific event is executed using a communication terminal 3 (an example of a first communication terminal; omitted below) that exists in a physical space and is used to execute a specific event, and a PC 9 (an example of a second communication terminal; omitted below) that is used to execute the specific event via a virtual space, and the event management method executed by the event management server 6 is as follows: After a process of participating in a specified event is performed by one of the communication terminals 3 and PC 9, a process is executed that includes a generation step of generating an event participation notification that prompts the other communication terminal, which is scheduled to participate in the specified event but has not yet participated, to participate in the specified event, and a transmission step of transmitting the generated event participation notification to the other communication terminal.

[0318] According to the tenth aspect, as in the first aspect, when a specified event is held with the physical space and the virtual space associated with each other, a participant who first joins one space can join the specified event without having to perform any joining process for the other space.

[0319] <Eleventh aspect> A program as an eleventh aspect is executed by an event management server 6 (an example of an event management device; the rest omitted) that manages information related to a specific event when the specific event is executed using a communication terminal 3 (an example of a first communication terminal; the rest omitted) that exists in a physical space and is used to execute the specific event, and a PC 9 (an example of a second communication terminal; the rest omitted) that is used to execute the specific event via a virtual space, After one of the communication terminals 3 and PC 9 has performed processing to participate in a specified event, the communication terminal executes processing including a generation step of generating an event participation notification that prompts the other communication terminal, which is scheduled to participate in the specified event but has not yet participated, to participate in the specified event, and a transmission step of transmitting the generated event participation notification to the other communication terminal.

[0320] According to the eleventh aspect, as in the first aspect, when a specified event is held with the physical space and the virtual space associated with each other, a participant who first joins one space can join the specified event without having to perform any joining process for the other space. [Explanation of symbols]

[0321] 1. Information Processing Systems 2. Event Management System 3. Communication terminal (an example of a first communication terminal) 31 Transmitting / receiving unit (an example of a transmitting means, an example of a receiving means) 32 Operation reception unit (an example of a reception means) 33 Acquisition unit (an example of an acquisition means) 34 Display control unit (an example of a display control means) 39 Memory readout unit (an example of a memory control means) 380 Display (an example of a display means) 3000 Memory unit (an example of a memory means) 4. Information processing equipment 44 Display control unit (an example of a display control means) 407 Display (an example of a display means) 5. User management server (an example of a user management device) 51 Transmitting / receiving unit (an example of a transmitting means, an example of a receiving means) 59 Memory readout unit (an example of a memory control means) 5000 Memory unit (an example of a memory means) 6 Event management server (an example of an event management device) 61 Transmitting / receiving unit (an example of a transmitting means, an example of a receiving means) 63 Acquisition unit (an example of acquisition means) 64 Display control unit (an example of a display control means) 69 Memory readout unit (an example of a memory control means) 7 Virtual reality hybrid event management server (an example of a virtual reality hybrid event management device) 8 Metaverse management server (an example of a metaverse management device) 9 PC (an example of a second communication terminal) 94 Display control unit (an example of a display control means) 907 Display (an example of a display means) [Prior art documents] [Patent documents]

[0322] [Patent Document 1] Special Publication No. 2020-525946< / pc>

Claims

1. a first communication terminal that exists in a physical space and is used to execute a predetermined event; a second communication terminal used to execute the predetermined event through a virtual space; an event management device that manages information related to the predetermined event when the predetermined event is executed using the first communication terminal and the second communication terminal; An event management system comprising: The event management device includes: a generation means for generating an event participation notification for prompting the other communication terminal, which is scheduled to participate in the predetermined event but has not yet participated, to participate in the predetermined event after a participation process for the predetermined event is performed by one of the first communication terminal and the second communication terminal; a transmission means for transmitting the generated event participation notification to the other communication terminal; having An event management system.

2. The generating means includes: generating the event participation notification based on a participation date and time when either the first communication terminal or the second communication terminal participated in the predetermined event; The event management system according to claim 1 .

3. The generating means includes: generating a notification including an event name representing the specific event being executed and names of participants participating in the specific event as the event participation notification; 3. The event management system according to claim 1 or 2.

4. The first communication terminal or the second communication terminal to which the event participation notification is transmitted, a receiving means for receiving the event participation notification transmitted by the event management device; A display control means for displaying the received event participation notification on a display means; having 3. The event management system according to claim 1 or 2.

5. The display control means a user of the first communication terminal or the second communication terminal causes a dialogue operable on the first communication terminal or the second communication terminal to be displayed as the event participation notification; The event management system according to claim 4 .

6. The event management device further comprises: a registration means for registering user identification information included in the request to participate in the specific event transmitted by the first communication terminal and participation date and time information indicating a date and time at which the user participated in the specific event in association with each other; having 3. The event management system according to claim 1 or 2.

7. The event management device further comprises: An execution means for executing a participation process for the predetermined event, The execution means includes: execute a process for participating in the predetermined event based on a request from the first communication terminal for either a schedule associated with the first communication terminal or a schedule associated with a user who will participate in the predetermined event held in the physical space; executing a process of participating in the specified event based on a request from the second communication terminal for any one of a schedule associated with the second communication terminal, a schedule associated with a user participating in the specified event executed in the virtual space, and a schedule represented by the specified event being executed; 3. The event management system according to claim 1 or 2.

8. The predetermined event is Including meetings, discussions, lectures, and classes held in the same time period in the physical space and the virtual space, 3. The event management system according to claim 1 or 2.

9. 1. An event management device that manages information related to a predetermined event when the predetermined event is executed using a first communication terminal that exists in a physical space and is used to execute the predetermined event, and a second communication terminal that is used to execute the predetermined event via a virtual space, comprising: a generation means for generating an event participation notification for prompting the other communication terminal, which is scheduled to participate in the predetermined event but has not yet participated, to participate in the predetermined event after a participation process for the predetermined event is performed by one of the first communication terminal and the second communication terminal; a transmission means for transmitting the generated event participation notification to the other communication terminal; having 1. An event management device comprising:

10. 1. An event management method executed by an event management device that manages information related to a specific event when the specific event is executed using a first communication terminal that exists in a physical space and is used to execute the specific event, and a second communication terminal that is used to execute the specific event via a virtual space, the method comprising: a generation step of generating an event participation notification for prompting the other communication terminal, which is scheduled to participate in the predetermined event but has not yet participated, to participate in the predetermined event after a participation process for the predetermined event is performed by one of the first communication terminal and the second communication terminal; a transmission step of transmitting the generated event participation notification to the other communication terminal; Perform a process that includes 13. An event management method comprising:

11. When a predetermined event is executed using a first communication terminal that exists in a physical space and is used to execute the predetermined event, and a second communication terminal that is used to execute the predetermined event via a virtual space, an event management device that manages information related to the predetermined event, a generation step of generating an event participation notification for prompting the other communication terminal, which is scheduled to participate in the predetermined event but has not yet participated, to participate in the predetermined event after a participation process for the predetermined event is performed by one of the first communication terminal and the second communication terminal; a transmission step of transmitting the generated event participation notification to the other communication terminal; A program that executes a process including:

Images