Event management system, event management method and program

Abstract

To solve the problem of a conventional technology, where in the case of participating in a predetermined event using a plurality of communication terminals, a participant must perform start processing to the respective communication terminals.SOLUTION: An event management device 2, after receiving operation on a start button, receives an event start request for starting a "conference 1" transmitted by a communication terminal 3A(1) (step S52). After that, the event management device 2 transmits an event participation request for the "conference 1" to a communication terminal 3A(2) and a shared terminal 4 which are associated with the "conference 1" and on which a "just now participation button" 3301 is operated for the "conference 1", where pairing setting is performed between the communication terminal 3A(1) and the terminals (steps S61, S65).SELECTED DRAWING: Figure 1

Description

[Technical Field]

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

[0002] 2. Description of the Related Art In recent years, technology has become known for connecting devices located at distant locations via a network to hold various events such as remote conferences.

[0003] Furthermore, in order to reliably send a conference start notification to devices that can be used by participants when the conference starts, a technique is known in which the remote conference server 100 performs a conference start notification process (S40) and sends the conference start notification to an event management device 200C that can be used by user A, who is a conference participant, and an event management device 200F that can be used by user C (S120) (see, for example, Patent Document 1). Summary of the Invention [Problem to be solved by the invention]

[0004] However, in the conventional technology, when participants use multiple communication terminals to participate in a given event, they have to perform startup processing on each of their communication terminals. [Means for solving the problem]

[0005] In order to solve the above-mentioned problem, the invention of claim 1 provides an event management system having a plurality of communication terminals used in a predetermined event, and an event management device that manages the plurality of communication terminals in association with the predetermined event, wherein the event management device has a receiving means for receiving an event start request transmitted by one of the plurality of communication terminals to request the start of the predetermined event, and a transmitting means for transmitting an event participation request, in response to the event start request received by the receiving means, to another of the plurality of communication terminals that is associated with the predetermined event and is associated with a participant who will participate in the predetermined event using the one communication terminal, to request participation in the predetermined event. The one communication terminal has a display control means for displaying a terminal combination setting accepting means for associating and setting the one communication terminal with the other communication terminal on a display means. The present invention provides an event management system characterized by: [Effects of the Invention]

[0006] As described above, according to the present invention, when a participant uses multiple communication terminals to participate in a specified event, the participant can make a start request to one communication terminal, thereby allowing the other communication terminals to also participate in the specified event. [Brief explanation of the drawings]

[0007] [Figure 1] 1 is an overall configuration diagram illustrating an example of an event management system. [Figure 2] FIG. 1 illustrates an example of a hardware configuration of a computer. [Figure 3] FIG. 2 is a diagram illustrating an example of a hardware configuration of a shared terminal. [Figure 4] FIG. 2 illustrates an example of a functional configuration of an event management system. [Figure 5A] FIG. 10 is a conceptual diagram illustrating an example of a terminal management table. [Figure 5B] FIG. 10 is a conceptual diagram illustrating an example of a pair setting management table. [Figure 5C] FIG. 10 is a conceptual diagram illustrating an example of a shared terminal management table. [Figure 5D]FIG. 10 is a conceptual diagram illustrating an example of a participant management table. [Figure 5E] FIG. 10 is a conceptual diagram illustrating an example of a participating terminal management table. [Figure 5F] FIG. 10 is a conceptual diagram illustrating an example of an equipment management table. [Figure 6] FIG. 10 is a sequence diagram illustrating an example of a login and event participation process. [Figure 7] 10 is an example of a screen display when reserving an online conference. [Figure 8] FIG. 10 is a sequence diagram illustrating an example of a pairing setting start process. [Figure 9] FIG. 10 is a sequence diagram illustrating an example of a terminal pairing setting process. [Figure 10] FIG. 10 is a sequence diagram illustrating an example of a communication terminal selection process for terminal pairing. [Figure 11] This is an example of a screen display when participating in an online conference. [Figure 12] 10 is an example of a screen display of a dialog for selecting device pairing settings. [Figure 13] 10 is an example of a screen display of a dialog box for creating a new device pairing. [Figure 14] 10 is a screen display example of a dialogue for selecting a pair name and a communication terminal for terminal pairing. [Figure 15A] 10 is a screen display example of a dialog box for setting device pairing including a shared device. [Figure 15B] 10 is a screen display example of another dialog for setting device pairing including a shared device. [Figure 16] FIG. 4 is a sequence diagram illustrating an example of an event start process according to the first embodiment. [Figure 17] 10 is a flowchart showing an example of a process for determining whether or not there is a paired terminal according to the first embodiment. [Figure 18] FIG. 4 is a sequence diagram illustrating an example of an event participation process according to the first embodiment. [Figure 19] 10 is an example of a screen of a dialogue box for requesting another communication terminal to participate in an event according to the first embodiment. [Figure 20]FIG. 10 is a sequence diagram illustrating an example of an event start process according to the second embodiment. [Figure 21] 10 is a flowchart showing an example of a process for determining whether or not there is a paired terminal according to the second embodiment. [Figure 22] 10 is a flowchart showing an example of a process for determining whether or not pair participation is necessary according to the second embodiment. [Figure 23] FIG. 10 is a sequence diagram illustrating an example of an event participation process according to the second embodiment. [Figure 24] 10 is a diagram illustrating an example of a screen display of a pair participation confirmation dialogue according to the second embodiment. [Figure 25] FIG. 11 is a sequence diagram illustrating an example of an event start process according to a modified example of the second embodiment. [Figure 26] FIG. 11 is a sequence diagram illustrating an example of an event participation process according to a modified example of the second embodiment. [Figure 27] 10 is a diagram illustrating an example of a screen display on a shared terminal according to a modified example of the second embodiment. DETAILED DESCRIPTION OF THE INVENTION

[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 if there are overlapping parts, the description thereof will be omitted.

[0009] [First embodiment] The first embodiment will be described with reference to FIGS.

[0010] [Overall configuration of the event management system] FIG. 1 is an overall configuration diagram illustrating an example of an event management system. As shown in FIG. 1, the event management system 1 includes various devices, including an event management device 2, a communication terminal 3A, a communication terminal 3B, and a shared terminal 4. Here, the event management device 2, the communication terminal 3A, the communication terminal 3B, and the shared terminal 4 are connected to each other via a communication network 100. The communication network 100 is constructed using the Internet, a mobile communication network, a local area network (LAN), or the like. Note that the communication network 100 may include not only wired communication networks but also wireless communication networks such as 3G (3rd Generation), 4G (4th Generation), 5G (5th Generation), WiMAX (Worldwide Interoperability for Microwave Access), or LTE (Long Term Evolution). The event management system 1 may also include a commonly known reservation management system that manages reservations for specific events, user schedules, and the like.

[0011] <Event management device> The event management device 2 is realized by an information processing device (computer system) that is equipped with a general OS and has server functions. The event management device 2 is capable of communicating with the communication terminal 3A, the communication terminal 3B, and the shared terminal 4, and exchanges various data (information) with the communication terminal 3A, the communication terminal 3B, and the shared terminal 4. The event management device 2 may also be a general PC (Personal Computer).

[0012] <Communication terminal> The communication terminal 3A and the communication terminal 3B (hereinafter, simply referred to as the communication terminal 3 unless otherwise specified) are realized by an information processing device (computer system) equipped with a general OS. The communication terminal 3 is a communication terminal used by a participant participating in a predetermined event, and communicates with the event management device 2 and the shared terminal 4 via the communication network 100. Note that in this embodiment, it is assumed that one participant uses multiple communication terminals 3A or 3B, such as communication terminals 3A(1), 3A(2), ..., communication terminals 3B(1), 3B(2), .... Furthermore, the communication terminal 3 may be, for example, a smartphone, a tablet terminal, a PDA (Personal Digital Assistant), or a wearable PC (such as a sunglasses-type, wristwatch-type, or ring-type PC) with communication functions. In other words, one participant can use multiple different types of communication terminals in the same event, for example, communication terminal 3A(1) being a PC and communication terminal 3A(2) being a smartphone. Furthermore, the communication terminal 3 may be a commonly used PC (Personal Computer). That is, the communication terminal 3 may be a terminal capable of running software such as browser software.

[0013] <Shared terminal> The shared terminal 4 is realized by an information processing device (computer system) equipped with a general OS. The shared terminal 4 is a communication terminal that is installed or placed in various resources and can be used by participants in a predetermined event, and communicates with the event management device 2 and the communication terminal 3 via the communication network 100. The shared terminal 4 is an example of a communication terminal having a communication function, such as an interactive whiteboard (IWB, hereinafter referred to as an electronic whiteboard), a projector, or a video conference system (Unified Communication System: UCS).

[0014] ●About terminology● In this embodiment, the term "event" refers to a general event that takes place at a specific indoor or outdoor location or space and has a set date and time, such as a conference, meeting, entertainment, lecture, exhibition, or concert. Furthermore, in this embodiment, events also include customary events that are held at a specific date and time. In this embodiment, a conference will be used as an example of an event.

[0015] In this embodiment, "start" refers to, for example, starting an event. Examples of this include enabling a communication terminal to be used for the event or performing a login process to enable communication at the event. Furthermore, "participate" refers to, for example, being involved in an event. Examples of this include performing a login process on a communication terminal to enable communication at the event.

[0016] Furthermore, a resource refers to a resource owned, leased, or managed by a company, group, or organization. Examples of resources for a company, group, or organization include conference rooms, equipment, devices, and people (receptionists) that can be used in conference rooms. Other resources include free address spaces, desks, chairs, booths, company cars, bicycles, parking lots, bicycle parking areas, remote conference systems, and printing services and systems. Resources that are difficult to move are called equipment. For ease of explanation, this embodiment uses the term conference room as an example of a resource. Other resources that can be treated as resources include accommodation facilities such as hotels, rental offices, rental studios, and event venues, as well as electronic devices, lockers, rental bicycles, and rental cars (shared cars).

[0017] [Hardware configuration] <Event management device and communication terminal hardware configuration> Fig. 2 is a diagram showing an example of the hardware configuration of a computer. As shown in Fig. 2, the event management device 2 is constructed by a computer and has hardware resources including a CPU (Central Processing Unit) 201, a ROM (Read Only Memory) 202, a RAM (Random Access Memory) 203, a HD (Hard Disk) 204, an HDD controller 205, a display 206, an external device connection I / F (Interface) 208, a network I / F 209, a bus line 210, a keyboard 211, a pointing device 212, a DVD-RW (Digital Versatile Disk Rewritable) drive 214, a media I / F 216, an audio input / output I / F 217, a microphone 218, and a speaker 219.

[0018] Of these, the CPU 201 controls the overall operation of the event management device 2. The ROM 202 stores programs used to drive the CPU 201. The RAM 203 is used as a work area for the CPU 201. The HD 204 stores various data such as programs. The HDD controller 205 controls the reading and writing of various data from and to the HD 204 under the control of the CPU 201. The display 206 is an example of display means for displaying various information such as a cursor, menu, window, text, or image. The display 206 may also be a touch panel display equipped with input means. The external device connection I / F 208 is an interface for connecting various external devices. In this case, the external device is, for example, a USB memory or USB device. The network I / F 209 is an interface for data communication using the communication network 100. The bus line 210 is an address bus or data bus for electrically connecting the components such as the CPU 201 shown in FIG. 2.

[0019] The keyboard 211 is a type of input means having multiple keys for inputting characters, numbers, various instructions, etc. The pointing device 212 is a type of input means for selecting or executing various instructions, selecting a processing target, moving a cursor, etc. The input means may be not only the keyboard 211 and the pointing device 212, but also a touch panel, a voice input device, etc. The DVD-RW (Digital Versatile Disk Rewritable) drive 214 controls reading and writing of various data from and to a DVD-RW 213, which is an example of a removable recording medium. The DVD-RW is not limited to a DVD-RW, and may be a DVD-R or a Blu-ray (registered trademark) Disc, etc. The media I / F 216 controls reading and writing (storing) of data from and to a recording medium 215, such as a flash memory.

[0020] The communication terminal 3 is constructed by a computer, and as shown in FIG. 2, the hardware resources from the CPU 301 to the media I / F 316 have the same configuration as the hardware resources from the CPU 201 to the media I / F 216 of the event management device 2, so detailed description will be omitted. The communication terminal 3 further includes an audio input / output I / F 317, a microphone 318, and a speaker 319. The microphone 318 is a type of built-in sound collection means that inputs audio (audio signals). The speaker 319 is a type of audio output means that outputs audio (audio signals). The audio input / output I / F 317 is a circuit that processes input and output of audio signals between the microphone 318 and the speaker 319 under the control of the CPU 301.

[0021] Note that the computer shown in FIG. 2 is just an example, and the communication terminal 3 may be a HUD (Head Up Display) device, industrial machinery, network home appliances, mobile phones, smartphones, tablet terminals, game consoles, PDAs (Personal Digital Assistants), etc.

[0022] Furthermore, each of the above programs may be recorded in an installable or executable file format on a computer-readable recording medium, or may be distributed by downloading via a network. Examples of recording media include CD-Rs (Compact Disc Recordables), DVDs (Digital Versatile Disks), Blu-ray (registered trademark) Discs, SD cards, and USB memory. Recording media may also be provided domestically or internationally as program products. For example, the event management device 2 realizes the event management method according to the present invention by executing the program according to the present invention.

[0023] <Hardware configuration of shared terminal> 3 is a diagram showing an example of a shared terminal 4. As shown in FIG. 3, the shared terminal 4 includes a CPU 401, a ROM 402, a RAM 403, an SSD (Solid State Drive) 404, a network I / F 405, and an external device connection I / F 406.

[0024] Of these, the CPU 401 controls the overall operation of the shared terminal 4. The ROM 402 stores programs used to drive the CPU 401, such as the CPU 401 and an IPL (Initial Program Loader). The RAM 403 is used as a work area for the CPU 401. The SSD 404 stores various data, such as programs for the shared terminal 4. The network I / F 405 controls communication with the communication network 100. The external device connection I / F 406 controls communication with a USB (Universal Serial Bus) memory 4600, a PC 4700, and external devices (a microphone 4200, a speaker 4300, and a camera 4400). The shared terminal 4 further includes a capture device 411, a GPU 412, a display controller 413, a contact sensor 414, a sensor controller 415, an electronic pen controller 416, a short-range communication circuit 419, an antenna 419a for the short-range communication circuit 419, and a power switch 422.

[0025] Of these, the capture device 411 acquires image data displayed on a display 420, which is an example of a display unit (display means), via a display controller 413 and stores the image data in a RAM 403 or the like. The GPU (Graphics Processing Unit) 412 is a semiconductor chip that specializes in graphics. The display controller 413 controls and manages screen display in order to output an output image from the capture device 411 or the GPU 412 to the display 420 or the like. The contact sensor 414 detects contact of the electronic pen 4500, the user's hand H, or the like on the display 420. The sensor controller 415 controls the processing of the contact sensor 414. The contact sensor 414 inputs and detects coordinates using an infrared blocking method. This coordinate input and coordinate detection method involves two light receiving and emitting devices installed at both ends of the upper side of the display 420 emitting multiple infrared rays parallel to the display 420, which are reflected by reflecting members installed around the display 420 and return along the same optical path as the light emitted by the light receiving element. The contact sensor 414 outputs the ID of the infrared light emitted by the two light receiving and emitting devices that has been blocked by the object to the sensor controller 415, and the sensor controller 415 identifies the coordinate position of the contact position of the object. The electronic pen controller 416 communicates with the electronic pen 4500 to determine whether the pen tip or the pen tail has touched the display 420. The short-range communication circuit 419 is a communication circuit such as NFC (Near Field Communication) or Bluetooth (registered trademark). The power switch 422 is a switch for turning the power of the shared terminal 4 on and off.

[0026] Furthermore, shared terminal 4 includes bus line 410. Bus line 410 is an address bus, a data bus, etc. for electrically connecting the components such as CPU 401 shown in FIG.

[0027] The contact sensor 414 is not limited to an infrared blocking type, and various detection means may be used, 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 coming into contact with the display unit. Also, the electronic pen controller 416 may determine whether or not a part of the electronic pen 4500 that is held by the user or other parts of the electronic pen has been touched, in addition to the pen tip and pen butt.

[0028] [Event management system functional configuration] Next, a functional configuration according to one embodiment will be described with reference to Fig. 4 and Fig. 5 (Fig. 5A to Fig. 5F). Fig. 4 is a diagram showing an example of the functional configuration of an event management system.

[0029] <Functional configuration of the event management device> 4, the event management device 2 includes a transmission / reception unit 21, an operation reception unit 22, a display control unit 24, a determination unit 25, an authentication unit 26, a generation unit 27, and a storage / readout unit 29. Each of these functional units is a function or means realized by operating any of the hardware resources shown in FIG. 2 in response to an instruction from the CPU 201 in accordance with a program for the event management device 2 that is loaded from at least one of the ROM 202 and the HD 204 to the RAM 203. The event management device 2 also includes a storage unit 2000 that is constructed from at least one of the ROM 202 and the HD 204 shown in FIG. 2.

[0030] ●Device Management Table● Fig. 5A is a conceptual diagram showing an example of a terminal management table. A terminal management DB 2001 configured by a terminal management table such as that shown in Fig. 5A is constructed in the storage unit 2000. In this terminal management table, participant names, terminal identification information, and usage history terminal names are associated with each participant identification information, and are stored and managed. Of these, participant identification information is information for identifying participants participating in a specified event, and is given, for example, as JID001, JID002, etc.

[0031] The participant name indicates a participant who will be attending a specific event, and is given as, for example, participant 1, organizer 1, etc.

[0032] The terminal identification information is information for identifying the communication terminal (also called a device) that a participant uses at a given event, and is given as, for example, DID001, DID002, etc.

[0033] The usage history device name manages what communication device a participant, given by the participant name, has used to participate in an event in the past, and is given as, for example, a notebook PC 1, a smartphone 1, a tablet device 1, an electronic whiteboard 1, etc. In other words, in this case, a record is managed that participant 1 has previously participated in a specified event using a notebook PC 1, a smartphone 1, and a tablet device 1.

[0034] ●Pair setting management table● Fig. 5B is a conceptual diagram showing an example of a pair setting management table. A pair setting management DB 2002 configured by a pair setting management table such as that shown in Fig. 5B is constructed in the storage unit 2000. In this pair setting management table, a terminal name, default setting, pair identification information, and set pair name are associated with each piece of terminal identification information, and are stored and managed. Of these, for the terminal name, the usage history terminal name corresponding to the terminal identification information managed in the terminal management DB 2001 (see Fig. 5A) is managed as the communication terminal corresponding to the terminal identification information managed in this pair setting management table.

[0035] The default settings manage which communication device is set as the default pair for each communication device. For example, participants can set the default pairing for laptop 1 as pair 1, smartphone 1 as not participating in the pairing, and tablet device 1 as pair 2 in advance.

[0036] The pair identification information is information for identifying a pair group, and is given, for example, as PID001, PID002, etc. The set pair name indicates which communication terminals are actually used as a pair with which set pair name, and is given, for example, as Pair 1, Pair 2, etc. In this case, the notebook PC 1 and smartphone 1 are managed as Pair 1, and the notebook PC 1 and tablet terminal 1 are managed as Pair 2.

[0037] ●Shared terminal management table● FIG. 5C is a conceptual diagram showing an example of a shared terminal management table. A shared terminal management DB 2003 configured by the shared terminal management table shown in FIG. 5C is created in the storage unit 2000. In this shared terminal management table, a participant name, terminal identification information, terminal name, and shared terminal are associated with and stored and managed for each participant identification information. Among these, the participant identification information, participant name, terminal identification information, and terminal name are the same as the items with the same names described in the terminal management DB 2001 (see FIG. 5A) and the pair setting management DB 2002 (see FIG. 5B). Furthermore, a shared terminal refers to a communication terminal that can be shared and used by participants participating in a specific event, separate from the individual communication terminals used by the specific participants, when a communication terminal represented by a terminal name is used in the specific event. In other words, in this embodiment, the electronic whiteboard 1 and the electronic whiteboard 2 installed or placed in a resource (e.g., a conference room) where the specific event is held are treated as shared terminals.

[0038] ●Participant Management Table● FIG. 5D is a conceptual diagram showing an example of a participant management table. A participant management DB 2004 configured with a participant management table such as that shown in FIG. 5D is constructed in the storage unit 2000. In this participant management table, the event name, participant identification information, participant name, and participation status are associated and stored and managed for each event identification information. Among these, the event identification information is information for identifying an event held on a specific date and time, and is given, for example, as EID001, EID002, etc. Furthermore, the participation status is managed by managing a check-in status indicating whether a participant who is scheduled to participate in an event represented by an event name is participating in the event, or a check-out status indicating whether the participant has withdrawn from the event.

[0039] ●Participating device management table● FIG. 5E is a conceptual diagram illustrating an example of a participation terminal management table. A participation terminal management DB 2005 configured by the participation terminal management table shown in FIG. 5E is configured in the storage unit 2000. In this participation terminal management table, participant names, event identification information, event names, set pair names, terminal identification information, and participation terminal names are stored and managed in association with each participant identification information. Among these, the set pair name is the name of a pair to which a communication terminal managed by the participation terminal name is set. For example, among the participation terminal names managed in this table, notebook PC 1 is set as both Pair 1 and Pair 2. In this case, the partner in Pair 1 for notebook PC 1 is smartphone 1. In other words, Pair 1 is set between smartphone 1 and notebook PC 1. Similarly, Pair 2 is set for tablet terminal 1. In this case, the partner in Pair 2 for tablet terminal 1 is notebook PC 1. In other words, notebook PC 1 will be used in both events, Meeting 1 and Meeting 3. Furthermore, electronic whiteboard 1 is not set as a pair and is treated as a shared device. In this way, the participating terminal management table may be managed in association with the above-described pair setting management DB 2002 (see FIG. 5B) in order to manage set pair names.

[0040] ●Equipment Management Table● FIG. 5F is a conceptual diagram showing an example of an equipment management table. An equipment management DB 2006 configured with an equipment management table such as that shown in FIG. 5F is constructed in the storage unit 2000. In this equipment management table, resource names, event identification information, event names, terminal identification information, and equipped terminal names are stored and managed in association with each resource identification information. Of these, resource identification information is information for identifying resources, and is given, for example, RID001, RID002, etc. Resource names manage the names of resources where specific events are held, and are given, for example, conference room 1, conference room 2, etc. Equipment terminal names are the names of terminals equipped to resources with the corresponding resource names, and are given, for example, electronic whiteboard 1, electronic whiteboard 2, etc.

[0041] <<Functional configuration of the event management device>> Next, a detailed description will be given of each functional configuration of the event management device 2. The transmitter / receiver 21 of the event management device 2 shown in Fig. 4 is mainly realized by processing of the CPU 201 on the external device connection I / F 208 and network I / F 209 shown in Fig. 2, and transmits and receives various data (or information) to and from the communication terminal 3 and the shared terminal 4 via the communication network 100. In this embodiment, the transmitter / receiver 21 functions as an example of at least one of a transmitting means and a receiving means.

[0042] The operation reception unit 22 is realized by the CPU 201 processing various signals received mainly from the keyboard 211 and pointing device 212 shown in Fig. 2, and receives input of various operations and selections from an administrator who manages the event management device 2. Furthermore, the operation reception unit 22 may use not only the keyboard 211 and pointing device 212, but also an operation button (having a UI (User Interface) that can be pressed, tapped, etc.) as another input means. In this embodiment, the operation reception unit 22 functions as an example of an operation reception means.

[0043] The display control unit 24 is mainly realized by the processing of the CPU 201 on the display 206 shown in Fig. 2, and controls the display of various data (information) to be displayed on the display 206. In this embodiment, the display control unit 24 functions as an example of a display control means.

[0044] The determination unit 25 is mainly realized by the processing of the CPU 201 shown in Fig. 2, and performs various determinations in the event management device 2. In this embodiment, the determination unit 25 functions as an example of a determination means.

[0045] 2, and generates various types of information to be transmitted to the communication terminal 3 and the shared terminal 4. In the present embodiment, the generation unit 27 functions as an example of a generation means.

[0046] Management unit 28 is mainly realized by the processing of CPU 201 shown in Fig. 2, and manages the participation (check-in) and withdrawal (check-out) of communication terminal 3 and shared terminal 4 in a predetermined event based on the participant identification information, user identification information, and terminal name transmitted by communication terminal 3 or shared terminal 4. Furthermore, management unit 28 manages (searches) previously used terminals based on the participant identification information. In this embodiment, management unit 28 functions as an example of management means.

[0047] 2, and stores various data (or information) in the storage unit 2000 and reads various data (or information) from the storage unit 2000. In this embodiment, the storage and reading unit 29 functions as an example of a storage and reading means.

[0048] <Functional configuration of communication terminal> As shown in FIG. 4, the communication terminal 3 includes a transmission / reception unit 31A (31B), an operation reception unit 32A (32B), a display control unit 34A (34B), a determination unit 35A (35B), an authentication unit 36A (36B), an execution unit 38A (38B), and a memory / readout unit 39A (39B). Unless otherwise specified, the functional units of the communication terminal 3 are referred to as the transmission / reception unit 31, the operation reception unit 32, the display control unit 34, the determination unit 35, the authentication unit 36, the execution unit 38, and the memory / readout unit 39. These units are functions or means realized by the operation of any of the hardware resources shown in FIG. 2 in response to instructions from the CPU 201 in accordance with a program for the communication terminal 3 loaded onto the RAM 203 from at least one of the ROM 202 and the HD 204. The communication terminal 3 also includes a memory unit 3000 implemented by at least one of the ROM 202 and the HD 204 shown in FIG. 2. The storage unit 3000 also stores a communication processing program executed by the communication terminal 3. Furthermore, the storage unit 3000 also has installed and manages, for example, a communication app for communicating with the event management device 2 and the shared terminal 4, and a conference app for running an online conference.

[0049] <<Functional configuration of communication terminal>> Next, a detailed description will be given of each functional configuration of the communication terminal 3. The transmission / reception unit 31 of the communication terminal 3 shown in Fig. 4 is mainly realized by processing of the CPU 301 on the external device connection I / F 308 and the network I / F 309 shown in Fig. 2, and transmits and receives various data (or information) to and from the event management device 2 via the communication network 100. In this embodiment, the transmission / reception unit 31 functions as an example of at least one of a transmitting means and a receiving means.

[0050] The operation acceptance unit 32 is realized by the CPU 301 processing various signals received mainly from the keyboard 311 and pointing device 312 shown in Fig. 2, and accepts various operations and selections from the user. The operation acceptance unit 32 may use not only the keyboard 311 and pointing device 312, but also an operation button (having a UI (User Interface) that can be pressed, tapped, etc.) as another input means. In this embodiment, the operation acceptance unit 32 functions as an example of an operation acceptance means.

[0051] 2, and performs control for displaying various images, characters, code information, etc. on the display 306. In this embodiment, the display control unit 34 functions as an example of a display control means.

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

[0053] 2, and performs login processing (request) by inputting user identification information and a predetermined password when a user of the communication terminal 3 performs authentication processing or the like for the event management device 2. In this embodiment, the authentication unit 35 functions as an example of authentication means.

[0054] 2, and executes a process for participating in various events in the communication terminal 3. In this embodiment, the execution unit 38 functions as an example of an execution means.

[0055] 2, 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 unit 39 functions as an example of a storage / reading means.

[0056] <Functional configuration of shared terminals> As shown in FIG. 4, the shared terminal 4 includes a transmission / reception unit 41, an operation reception unit 42, a display control unit 44, a determination unit 45, an authentication unit 46, an execution unit 48, and a storage / readout unit 49. Each of these units is a function or means realized by operating any of the hardware resources shown in FIG. 3 in response to an instruction from the CPU 401 in accordance with a program for the shared terminal 4 that is loaded onto the RAM 403 from at least one of the ROM 402 and the SSD 404. The shared terminal 4 also includes a storage unit 4000 constructed by at least one of the ROM 402 and the SSD 404 shown in FIG. 3. The storage unit 4000 also stores a communication processing program to be executed by the shared terminal 4. In addition, the storage unit 4000 has installed therein and managed, for example, a communication app for communicating with the event management device 2 and the communication terminal 3, and a conference app for conducting an online conference.

[0057] <<Functional configuration of shared terminals>> Next, a detailed description will be given of each functional configuration of the shared terminal 4. The transmitter / receiver 41 of the shared terminal 4 shown in Fig. 4 is mainly realized by processing of the CPU 401 on the external device connection I / F 406 and the short-range communication circuit 419 shown in Fig. 3, and transmits and receives various data (or information) to and from the event management device 2 and the communication terminal 3 via the communication network 100. In this embodiment, the transmitter / receiver 41 functions as an example of at least one of a transmitting means and a receiving means.

[0058] The operation acceptance unit 42 is realized by the CPU 401 processing various signals received mainly from the electronic pen controller 416, the contact sensor 414, and the sensor controller 415 shown in Fig. 3, and accepts various operations and selections from the user, as well as information input by electronic pen input and manual input. Furthermore, the operation acceptance unit 42 may use an operation button (having a UI (User Interface) that can be pressed, tapped, etc.) as another input means in addition to electronic pen input and manual input. In this embodiment, the operation acceptance unit 42 functions as an example of an operation acceptance means.

[0059] 3 and the display controller 213, and performs control to display various images, characters, numbers, code information, etc. on the display 420. In this embodiment, the display controller 44 functions as an example of a display control means.

[0060] 3, and performs various determinations in shared terminal 4. In this embodiment, determination unit 45 functions as an example of a determination means.

[0061] 3, and performs login processing (request) by inputting user identification information and a predetermined password when a user using the shared terminal 4 performs authentication processing or the like for the event management device 2. In this embodiment, the authentication unit 46 functions as an example of authentication means.

[0062] 3, and executes processing for participating in various events in shared terminal 4. In this embodiment, execution unit 48 functions as an example of an execution means.

[0063] 3, and stores various data (or information) in the storage unit 4000 and reads various data (or information) from the storage unit 4000. In this embodiment, the storage unit 49 functions as an example of a storage and reading means.

[0064] [Processing or Operation of the Embodiment] Next, each process or operation in the event management system 1 according to the first embodiment will be described with reference to Fig. 6 to Fig. 19. Fig. 6 is a sequence diagram showing an example of a login and event participation process.

[0065] <Login and event participation process> First, a participant 1 who is participating in a predetermined event performs a login process and an event participation process using a notebook PC 1, which is an example of the communication terminal 3A(1) that the participant 1 uses. As a result, the operation acceptance unit 32(1) of the notebook PC 1 accepts the login process and the event participation process performed by the participant 1 (step S1).

[0066] Next, the transmitter / receiver 31(1) transmits an event participation request to the event management device 2 (step S2). As a result, the event management device 2 receives the event participation request transmitted by the communication terminal 3A(1). At this time, the event participation request includes the participant identification information, the terminal identification information, and the terminal name, laptop PC1.

[0067] The management unit 28 of the event participation device 2 that has received the event participation request performs an event participation process for PC 1 (step S3). Specifically, the management unit 28 cooperates with the storage and reading unit 29 to register the received "Participant 1," "DID001," and "Notebook PC 1" in the items of participant name, terminal identification information, and usage history terminal name corresponding to the participant identification information in the terminal management DB 2001 (see FIG. 5A), respectively.

[0068] After performing the event participation process, the transmitter / receiver 21 transmits an event participation response to the communication terminal 3A(1) (step S4). As a result, the transmitter / receiver 31(1) of the communication terminal 3A(1) receives the event participation response transmitted by the event management device 2. At this time, the event participation response may include participant identification information.

[0069] Similarly, the processes from step S1 to step S4 described above are performed on the communication terminal 3A(2) used by the participant 1. That is, the participant 1 performs the login process and the event participation process using the smartphone 1, which is an example of the communication terminal 3A(2) used by the participant 1. Then, the operation accepting unit 32(2) of the smartphone 1 accepts the login process and the event participation process performed by the participant 1 (step S5).

[0070] Next, the transmitter / receiver 31(2) transmits an event participation request to the event management device 2 (step S6). As a result, the event management device 2 receives the event participation request transmitted by the communication terminal 3A(2). At this time, the event participation request includes the participant identification information, the terminal identification information, and the terminal name, which is smartphone 1.

[0071] The management unit 28 of the event participation device 2 that has received the event participation request performs an event participation process for the smartphone 1 (step S7). Specifically, the management unit 28 cooperates with the storage and reading unit 29 to register the received "Participant 1," "DID002," and "Smartphone 1" in the items of participant name, terminal identification information, and usage history terminal name corresponding to the participant identification information in the terminal management DB 2001 (see FIG. 5A), respectively.

[0072] After performing the event participation process, the transmitter / receiver 21 transmits an event participation response to the communication terminal 3A(2) (step S8). As a result, the transmitter / receiver 31(2) of the communication terminal 3A(2) receives the event participation response transmitted by the event management device 2. At this time, the event participation response may include participant identification information.

[0073] Similarly, the processes from step S1 to step S4 described above are also performed on the shared terminal 4 used by the organizer 1 who is hosting a specific event. That is, the organizer 1 performs the login process and the event participation process using the electronic whiteboard 1, which is an example of the shared terminal 4 that the organizer 1 uses. Then, the operation accepting unit 42 of the electronic whiteboard 1 accepts the login process and the event participation process performed by the organizer 1 (step S9).

[0074] Next, the transmitter / receiver 41 transmits an event participation request to the event management device 2 (step S10). As a result, the event management device 2 receives the event participation request transmitted by the shared terminal 4. At this time, the event participation request includes the participant identification information, terminal identification information, and the terminal name, ie, the electronic whiteboard 1.

[0075] The management unit 28 of the event participation device 2 that has received the event participation request performs an event participation process on the electronic whiteboard 1 (step S11). Specifically, in cooperation with the storage and reading unit 29, the management unit 28 registers the received "host 1," "DID004," and "electronic whiteboard 1" in the items of participant name, terminal identification information, and usage history terminal name corresponding to the participant identification information in the terminal management DB 2001 (see FIG. 5A), respectively.

[0076] After performing the event participation process, the transmitter / receiver 21 transmits an event participation response to the shared terminal 4 (step S12). As a result, the transmitter / receiver 41 of the shared terminal 4 receives the event participation response transmitted by the event management device 2. At this time, the event participation response may include participant identification information.

[0077] In the above-described processing from steps S1 to S12, the processing related to each communication terminal used by participant 1 has been described, but participants may be different. In this case, the participant identification information and participant name registered in the participant management DB 2004 (see FIG. 5D) are changed and registered.

[0078] Furthermore, the functional units described above as the communication terminal 3A(1) and the communication terminal 3A(2) will hereinafter be described as the functional units in the communication terminal 3 for the sake of convenience.

[0079] In the event management system according to this embodiment, for example, when the processes of steps S2 and S4, steps S6 and S8, and steps S10 and S12 described above are executed, other devices may be present between each communication terminal 3 and the event management device 2. In other words, each piece of information (data) exchanged between each communication terminal 3 and the event management device 2 may be exchanged once via another device. The above-described configuration and processing method may also be applied to other processing steps between each communication terminal 3 and the event management device 2.

[0080] ●Screen display example● FIG. 7 shows an example of a screen display when reserving an online conference. As shown in FIG. 7, in step S1, participant 1 operates, for example, communication terminal 3 (notebook PC 1) to display an “online conference reservation dialog” 3201 on display 306. Specifically, when operation reception unit 32 receives an event participation operation from participant 1, display control unit 34 executes a conference app installed on communication terminal 3 to display “online conference reservation dialog” 3102 on display screen 3101 on display 306. The “online conference reservation dialog” 3102 displays items including, for example, the title of the event to be held (here, “Meeting 1”), start time, end time, and location (here, “Conference Room 1”). Furthermore, the “online conference reservation dialog” 3102 includes information links, including a predetermined link for joining the conference added by participant 1 (here, “Click here to join the conference”). The above-described “online conference reservation dialog” 3102 is also displayed in the same way on each communication terminal in steps S5 and S9.

[0081] <Pair addition, setting start process> Next, a description will be given of a process for adding and setting a pair of communication terminals by a participant. Fig. 8 is a sequence diagram showing an example of a pairing setting start process. As shown in Fig. 8, the display control unit 34 of the communication terminal 3 displays a "UI framework review dialog" 3202 on a display screen 3101 on a display 306 (described later). Thereafter, the operation accepting unit 32 accepts an operation on a "setting button" 3300 (a gear button in Fig. 11 (described later)) by the participant (step S21).

[0082] Next, the transmitting / receiving unit 31 transmits a setting request to the event management device 2 (step S22). As a result, the transmitting / receiving unit 21 of the event management device 2 receives the setting request transmitted by the communication terminal 3. At this time, the setting request includes participant identification information, terminal identification information, and event identification information. Note that the event identification information is associated with, for example, the "online conference reservation dialog" 3102 and the "UI framework review dialog" 3202 displayed in step S21, and is stored in the communication terminal 3.

[0083] Upon receiving the setting request, the event management device 2 searches for previously used terminals based on the participant identification information (step S23). Specifically, the management unit 28, in cooperation with the storage / readout unit 29, searches the terminal management DB 2001 (see FIG. 5A) using the received participant identification information as a search key, thereby reading out the corresponding used terminal name. This allows the management unit 28 to search for a communication terminal associated with the participant identification information. Note that the searched usable terminal is not limited to one for each participant.

[0084] Next, the memory readout unit 29 reads out the setting screen information stored and managed in a predetermined area of the memory unit 2000 (step S24), and the transmitter / receiver 21 transmits, to the communication terminal 3, dialog information for configuring a dialog box (hereinafter simply referred to as "dialog") included in the read setting screen information (step S25). As a result, the transmitter / receiver 31 of the communication terminal 3 receives the dialog information transmitted by the event management device 2. At this time, the dialog information includes dialog information for "settings."

[0085] ●Screen display example● FIG. 11 is an example of a screen display when reserving an online conference. As shown in FIG. 11, a "UI Framework Review Dialog" 3202 is displayed by the display control unit 34 on a display screen 3101 on the display 306 of the communication terminal 3. The "UI Framework Review Dialog" 3202 further displays a "Settings button" 3300 and a "Join Now button" 3301. Participants can transition to other screens by operating these buttons as needed. In this embodiment, the "Join Now button" 3301 functions as an example of an event starting means.

[0086] <Pair addition and setting process> 9 is a sequence diagram showing an example of a terminal pairing setting process. As shown in FIG. 9, the display control unit 34 of the communication terminal 3 displays a "setting dialog" 3203 on a display screen 3101 on the display 306 (described later). Thereafter, the operation accepting unit 32 accepts an operation on a "terminal pairing setting button" 3303 by a participant (step S31). In this embodiment, the "terminal pairing setting button" 3303 functions as an example of a terminal combination setting accepting unit.

[0087] ●Screen display example● 12 is an example of a screen display of a dialog for selecting device pairing settings. As shown in FIG. 12, a "settings dialog" 3203 is displayed by the display control unit 34 on the display screen 3101 on the display 306 of the communication terminal 3. The "settings dialog" 3203 further displays various setting buttons, including a "communication terminal settings (microphone / speaker) button" 3302 and a "device pairing setting button" 3303. Participants can move to other screens by operating these buttons as needed.

[0088] 9, the transmitter / receiver 31 transmits terminal pairing setting button information to the event management device 2 (step S32). As a result, the transmitter / receiver 21 of the event management device 2 receives the terminal pairing setting transmitted by the communication terminal 3. At this time, the terminal pairing setting information includes terminal identification information.

[0089] The storage and reading unit 29 of the event management device 2 that has received the terminal pairing setting information reads out the terminal pairing setting information (step S33). Specifically, the storage and reading unit 29 searches the pair setting management DB 2002 (see FIG. 5B) using the received terminal identification information as a search key, and reads out the corresponding set pair name (pair 1, pair 2, etc.). The set pair name read out at this time is the set pair name that is set as the default. Furthermore, the storage and reading unit 29 reads out terminal pairing setting screen information that is stored and managed in a predetermined area of the storage unit 2000.

[0090] Next, the transmitter / receiver 21 transmits dialogue information based on the read set pair name to the communication terminal 3 (step S34). As a result, the transmitter / receiver 31 of the communication terminal 3 receives the dialogue information based on the set pair name transmitted by the event management device 2. At this time, the dialogue information includes dialogue information for "terminal pairing setting."

[0091] Next, the display control unit 34 of the communication terminal 3 displays a "terminal pairing setting dialog" 3203 (described later) on the display screen 3101 of the display 306. Thereafter, the operation accepting unit 32 accepts an operation on the "terminal pairing setting button" 3303 by the participant (step S35).

[0092] ●Screen display example● 13 is an example of a screen display of a dialog for creating a new device pairing. As shown in FIG. 13, a "device pairing setting dialog" 3204 is displayed by the display control unit 34 on a display screen 3101 on the display 306 of the communication terminal 3. An add button 3304 and a delete button 3305 are displayed for each set pair name on the "device pairing setting dialog" 3204. Furthermore, a "+ create new button" 3306 is displayed. Participants can transition to other screens by operating these buttons as necessary.

[0093] 9, the transmitter / receiver 31 of the communication terminal 3 transmits the operation content information set by the participant to the event management device 2 (step S36). As a result, the transmitter / receiver 21 of the event management device 2 receives the operation content information transmitted by the communication terminal 3. At this time, the operation content information includes information on the operation of the "+New creation button" 3306 shown in FIG. 13, which will be described later.

[0094] The storage reading unit 29 of the event management device 2 that has received the information that the "+New Creation Button" 3306 has been operated reads out new creation screen information (step S37). Specifically, the storage reading unit 29 reads out the new creation screen information stored and managed in a predetermined area of the storage unit 2000.

[0095] Next, the transmitter / receiver 21 transmits the read dialogue information constituting the new creation screen to the communication terminal 3 (step S38). As a result, the transmitter / receiver 31 of the communication terminal 3 receives the dialogue information constituting the new creation screen transmitted by the event management device 2. At this time, the dialogue information includes the dialogue information for terminal pairing setting and the previously used terminal name information read in step S23.

[0096] <Device pairing communication device selection process> 10 is a sequence diagram showing an example of a communication terminal selection process for terminal pairing. As shown in Fig. 10, the display control unit 34 of the communication terminal 3 displays a "new terminal pairing setting dialog" 3205 (described later) on the display screen 3101 of the display 306. Thereafter, the operation accepting unit 32 accepts an operation on the "new terminal pairing setting dialog" 3305 by the participant (step S41).

[0097] ●Screen display example● FIG. 14 is an example of a screen display of a dialog for selecting a pair name and communication terminals for device pairing. As shown in FIG. 14, a "new device pairing setting dialog" 3205 is displayed by the display control unit 34 on the display screen 3101 on the display 306 of the communication terminal 3. The "new device pairing setting dialog" 3205 displays a pair name input area in which a pair name can be input, and check boxes for each communication terminal for selecting the communication terminal to be paired. Furthermore, the "new device pairing setting dialog" 3205 displays an "OK button" 3307 and a "cancel button" 3308, which can be set after inputting the pair name and the check boxes. Participants can transition to other screens by operating these buttons as necessary.

[0098] 10, the transmitter / receiver 31 transmits new pairing setting information to the event management device 2 (step S42). As a result, the transmitter / receiver 21 of the event management device 2 receives the new pairing setting transmitted by the communication terminal 3. At this time, the new pairing setting information includes event identification information, pair name information indicating the set pair name, selected terminal name information indicating the terminal name, and OK button information related to the operation of the "OK button" 3307. Note that the event identification information transmitted by the communication terminal 3 to the event management device 2 is not limited to the process of step S42 described above.

[0099] The storage / reading unit 29 of the event management device 2 that has received the terminal pairing setting information stores and registers the received pair name information and selected terminal name information in the pair setting management DB 2002 (see FIG. 5B) (step S43).

[0100] Next, memory reading unit 29 searches the shared terminal management DB (see FIG. 5C) using the event identification information received in step S42 as a search key, thereby reading out the corresponding terminal name and shared terminal. Furthermore, memory reading unit 29 reads out pair-specific setting screen information stored and managed in a predetermined area of memory unit 2000 (step S44). This pair-specific setting screen information includes dialog information, shared terminal name information indicating the shared terminal name, OK button information, and cancel button information.

[0101] Next, the transmitter / receiver 21 transmits dialog information based on the read pair-specific setting screen information to the communication terminal 3 (step S45). As a result, the transmitter / receiver 31 of the communication terminal 3 receives the dialog information based on the pair-specific setting screen information transmitted by the event management device 2. At this time, the dialog information includes dialog information for displaying the communication terminals selected for each pair, shared terminal information, OK button information representing the "OK button," and cancel button information representing the "cancel button."

[0102] Next, the display control unit 34 of the communication terminal 3 displays a "pair-specific dialog" 3206 or 3027, which will be described later, on the display screen 3111 of the display 306 (step S46).

[0103] ●Screen display example● FIG. 15A is an example of a screen display of a dialog for setting device pairing including a shared device. As shown in FIG. 15A, on a display screen 3111 on the display 306 of the communication terminal 3, the display control unit 34 displays a “pair-specific dialog” 3206 with the pair name as a tab. This “pair-specific dialog” 3206 displays the names of the devices set as the pair indicated by the pair name, along with check marks in check boxes. Here, a state is shown in which a laptop PC 1 and a smartphone 1 have been selected as pair 1. Also, on the display screen 3111, the display control unit 34 displays an electronic whiteboard 1 representing the shared device 4, along with a check mark in the check box. Furthermore, on the display screen 3111, the display control unit 34 displays an “OK button” 3309 and a “cancel button” 3310. Participants can transition to other screens by operating the “OK button” 3309 and the “cancel button” 3310 as necessary.

[0104] ●Screen display example● FIG. 15B is an example of a screen display of another dialog for setting device pairing including a shared device. As shown in FIG. 15B, on a display screen 3112 on the display 306 of the communication terminal 3, the display control unit 34 displays a “pair-specific dialog” 3206 with the pair name as a tab. In this “pair-specific dialog” 3207, the names of the devices set as the pair indicated by the pair name are displayed with check marks in check boxes. Here, a state is shown in which a notebook PC 1 and a tablet device 1 have been selected as pair 1. Also, on the display screen 3112, the display control unit 34 displays an electronic whiteboard 1 representing the shared device 4 with a check mark in the check box. Furthermore, on the display screen 3112, the display control unit 34 displays an “OK button” 3311 and a “cancel button” 3312. Participants can transition to other screens by operating the “OK button” 3311 and the “cancel button” 3312 as necessary.

[0105] <Event start request> 16 is a sequence diagram showing an example of an event start process according to the first embodiment. As shown in FIG. 16, the operation accepting unit 32 of the communication terminal 3 (communication terminal 3A(1)) accepts an operation of a start button by a participant to start a predetermined event ("Conference 1") (step S51). The start button at this time is, for example, the "Join Now Button" 3301 displayed in the "UI Framework Review Dialog" 3202 shown in FIG. 11, and the operation of the "Join Now Button" 3301 is an example of an operation to participate in the predetermined event. In this case, the communication terminal 3 (communication terminal 3A(1)) is an example of one of the multiple communication terminals.

[0106] After accepting the operation of the start button, the transmitter / receiver 31 of the communication terminal 3 (communication terminal 3A(1)) transmits an event start request to start "Meeting 1", which is an example of a predetermined event, to the event management device 2 (step S52). As a result, the transmitter / receiver 21 of the event management device 2 receives the event start request to start "Meeting 1" transmitted by the communication terminal 3. At this time, the event start request includes the event identification information indicated by Conference 1 and the terminal identification information of the laptop PC 1.

[0107] After receiving the event start request, the judgment unit 25 searches the pair setting management DB 2002 (see Figure 5B), the shared terminal management DB 2003 (see Figure 5C), and the equipment management DB 2006 (see Figure 5F) to perform a process to determine whether or not there are paired terminals (step S53).

[0108] After determining whether or not there is a paired terminal, the transmitter / receiver 21 transmits an event start response to the event start request to the communication terminal 3 (step S54). As a result, the transmitter / receiver 31 of the communication terminal 3 receives the event start response transmitted by the event management device 2.

[0109] <Process to determine whether a paired device is present> 17 is a flowchart showing an example of a process for determining whether or not a paired terminal exists according to the first embodiment. First, the storage / reading unit 29 searches the pair setting management DB 2002 (see FIG. 5B) using the received terminal identification information as a search key, thereby reading out the pair name of the corresponding default setting item. Then, the determination unit 25 determines whether or not a pair has been set by default (step S53-1).

[0110] If a pair is set by default, that is, if a pair with a default setting exists (step S53-1; YES), the determination unit 25 determines whether or not there is a communication terminal for which a new pairing setting has been set (step S53-2).

[0111] On the other hand, if there is no pair with the default setting (step S53-1; NO), the generation unit 27 generates an event participation request to allow only the communication terminal that operated the start button in step S51 to participate in the target event, and then exits this flow (step S53-4).

[0112] If there is a newly paired communication terminal (step S53-2; YES), the determination unit proceeds to the process of step S53-3. On the other hand, if there is no newly paired communication terminal (step S53-2; NO), the generation unit 27 generates an event participation request for allowing the paired terminal set as default to participate in the target event, and then exits this flow (step S53-5).

[0113] If there is a communication terminal for which pairing has been newly set, the memory reading unit 29 searches the pair setting management DB 2002 (see FIG. 5B) again using the received terminal identification information as a search key to read out the corresponding set pair name. Thereafter, the generation unit 27 generates an event participation request for allowing all communication terminals indicated by the read pair names to participate in the target event, and the process exits from this flow (step S53-3).

[0114] <Processing event participation requests for other communication devices> FIG. 18 is a sequence diagram illustrating an example of an event participation process according to the first embodiment. As illustrated in FIG. 18, the transmitter / receiver 21 of the event management device 2 transmits an event participation request for "Meeting 1" to the communication terminal 3A(2) that is associated with "Meeting 1," which is an example of a predetermined event, and that is paired with the communication terminal 3A(1) (step S61). As a result, the transmitter / receiver 31(2) of the communication terminal 3A(2), i.e., the smartphone 1, receives the event participation request for the target event transmitted by the event management device 2. At this time, the event participation request includes information on the event identification information and the event name, "Meeting 1." Note that the communication terminal 3A(1) is the communication terminal on which the "Join Now Button" 3301 for "Meeting 1" was operated, as described in step S51. In this case, the communication terminal 3 (communication terminal 3A(2)) is an example of another communication terminal among the multiple communication terminals.

[0115] The operation accepting unit 32(2) of the smartphone 1 that has received the event participation request accepts the participation operation by the participant, and the executing unit 38(2) performs the process of participating in the target event (step S62).

[0116] After the execution unit 38(2) executes the participation process, the transmission / reception unit 31(2) transmits an event participation response to the event management device 2 (step S63). As a result, the transmission / reception unit 21 of the event management device 2 receives the event participation response transmitted by the communication terminal 3. This event participation response includes the participant identification information and the terminal identification information.

[0117] The memory readout unit 29 of the event management device 2 that has received the event participation response performs a registration process for the participant and the communication terminal (step S64). Specifically, the memory readout unit 29, in cooperation with the management unit 28, sets the participation status corresponding to the participant name indicated by the participant identification information in the participant management DB 2004 (see FIG. 5D) to "participating." Furthermore, the memory readout unit 29, in cooperation with the management unit 28, sets the participation terminal name (smartphone 1) corresponding to the terminal identification information as the terminal name of the communication terminal in the participation terminal management DB 2005 (see FIG. 5E).

[0118] Next, the transmitter / receiver 21 transmits a request to participate in the target event ("Meeting 1") to the shared terminal 4 (electronic whiteboard 1) (step S65). As a result, the transmitter / receiver 41 of the shared terminal 4 receives the request to participate in the target event transmitted by the event management device 2. At this time, the event participation request includes the event identification information and information on the event name "Meeting 1". In addition, in this case, the shared terminal 4 is another example of another communication terminal among the multiple communication terminals. In the processes of steps S61 and S65 described above, the notebook PC 1, which is an example of a communication terminal 3A(1), the smartphone 1, which is an example of a communication terminal 3A(2), and the electronic whiteboard 1, which is an example of a shared terminal 4, are communication terminals associated with "Meeting 1," which is an example of a predetermined event, and "Conference Room 1," which is an example of a predetermined resource where "Meeting 1" is held.

[0119] The operation accepting unit 42 of the shared terminal 4 that has received the event participation request accepts the participation operation by the organizer (or a participant participating in the same "Meeting 1"), and the executing unit 48 performs the participation process for the target event (step S66).

[0120] After the execution unit 48 executes the participation process, the transmission / reception unit 41 transmits a participation response to the event management device 2 (step S67). As a result, the transmission / reception unit 21 of the event management device 2 receives the participation response transmitted by the communication terminal 3. This participation response includes the participant identification information and the terminal identification information.

[0121] The memory readout unit 29 of the event management device 2 that has received the event participation response performs a registration process for the participant and the communication terminal (step S68). Specifically, the memory readout unit 29, in cooperation with the management unit 28, sets the participation status corresponding to the participant name indicated by the participant identification information in the participant management DB 2004 (see FIG. 5D) to "participating." Furthermore, in cooperation with the management unit 28, the memory readout unit 29 sets the participant terminal name (electronic whiteboard 1) corresponding to the terminal identification information as the terminal name of that communication terminal in the participant terminal management DB 2005 (see FIG. 5E). Note that the processes from step S61 to S68 are repeatedly performed for all communication terminals that are the targets of the event participation request.

[0122] Note that similar to the processing for Pair 1 described above, processing is also performed for each communication terminal paired as Pair 2. Furthermore, the smartphone 1 and tablet terminal 1 paired with the laptop PC 1 may be used by the participants themselves who have participated in "Conference 1" held in "Conference Room 1," or may be lent to other participants who have participated in "Conference 1" and used by them.

[0123] In the event management system according to this embodiment, for example, when the processes of steps S65 and S67 described above are executed, another device may be present between the event management device 2 and the shared terminal 4. In other words, the configuration may be such that each piece of information (data) transmitted and received between the event management device 2 and the shared terminal 4 is transmitted and received once via another device. The configuration and processing method described above can also be applied to other processing steps between the event management device 2 and the shared terminal 4.

[0124] ●Screen display example● 19 is an example of a screen of a dialog box for requesting participation in an event to another communication terminal according to the first embodiment. As shown in FIG. 19, an "event participation dialog box" 3601 similar to the "UI framework review dialog box" 3202 shown in FIG. 11 is displayed by the display control unit 34 on a display screen 3501 on the display 306 of the smartphone 1, which is an example of another communication terminal 3. Furthermore, a "join now button" 3611 is displayed by the display control unit 34 on the "event participation dialog box" 3601. A participant can start the process of participating in the target event by operating the "join now button" 3611 as needed, and can transition from this dialog box to another screen.

[0125] [Major Effects of the First Embodiment] As described above, according to this embodiment, after accepting operation of the start button, the event management device 2 receives an event start request for starting "Conference 1" transmitted from the communication terminal 3A(1) (step S52). Thereafter, the event management device 2 transmits an event participation request for the target event to the communication terminal 3A(2) that is associated with "Conference 1" and that has been paired with the communication terminal 3A(1) on which the "Join Now button" 3301 for "Conference 1" was operated, and to the shared terminal 4 (steps S61 and S65). This provides an advantage that, when a participant uses multiple communication terminals to participate in a predetermined event, by issuing a start request to one communication terminal, the participant can have the predetermined event in which the participant is participating and other communication terminals associated with that participant also participate in the predetermined event.

[0126] Second Embodiment Next, a second embodiment will be described with reference to Figures 20 to 24. In the second embodiment, when a participant starts a predetermined event, the event management device 2 adds a process of displaying a pair participation confirmation dialog on the communication terminal 3 to prompt the participant to select pair participation. Note that the configuration of the event management system according to the second embodiment is the same as the devices, hardware configurations, and functional configurations in the event management system according to the first embodiment, and therefore description thereof will be omitted here.

[0127] <Event start request> Fig. 20 is a sequence diagram showing an example of an event start process according to the second embodiment. Here, the processes of steps S71 and S72 shown in Fig. 20 are the same as the processes of steps S51 and S52 in the sequence diagram shown in Fig. 16, and therefore will not be described.

[0128] Next, the determination unit 25 of the event management device 2 performs processing to determine whether or not there is a paired terminal (step S73).

[0129] <Process to determine whether a paired device is present> Fig. 21 is a flowchart showing an example of a process for determining whether or not a paired terminal exists according to the second embodiment. As shown in Fig. 21, the storage / reading unit 29 searches the pair setting management DB 2002 (see Fig. 5B) using the received terminal identification information as a search key, and reads out the pair name of the corresponding default setting item. Thereafter, the determination unit 25 determines whether or not a pair has been set by default (step S73-1).

[0130] If a pair is set by default, that is, if a pair with a default setting exists (step S73-1; YES), the determination unit 25 determines whether or not there is a communication terminal with which a new pairing setting has been set (step S73-2).

[0131] On the other hand, if there is no pair with the default setting (step S73-1; NO), the decision unit 25 exits this flow.

[0132] If there is a communication terminal for which pairing has been newly set (step S73-2; YES), the generation unit 27 generates a pair participation confirmation dialogue and exits this flow (step S73-3). On the other hand, if there is no communication terminal for which pairing has been newly set (step S73-2; NO), the determination unit 25 exits this flow.

[0133] 20 , after determining whether or not there is a paired terminal, the transmitter / receiver 21 transmits pair participation confirmation dialog information including button information to the communication terminal 3 (step S74). As a result, the transmitter / receiver 31 of the communication terminal 3 receives the pair participation confirmation dialog information transmitted by the event management device 2.

[0134] The display control unit 34 of the communication terminal 3 that has received the pair participation confirmation dialogue information displays a "pair participation confirmation dialogue" 3208 (described later) on the display screen 3101 of the display 306 (step S75).

[0135] ●Screen display example● FIG. 24 is an example of a screen display of a pair participation confirmation dialog according to the second embodiment. As shown in FIG. 24, a "pair participation confirmation dialog" 3208 is displayed by the display control unit 34 on a display screen 3101 on the display 306 of the communication terminal 3. Furthermore, in the "pair participation confirmation dialog" 3208, a "pair name selection display section" 3213 from which a pair name can be selected in a drop-down manner is displayed by the display control unit 34. Furthermore, in the "pair participation confirmation dialog" 3208, an "OK button" 3314 and a "Participate with this communication terminal only button" 3315 are displayed by the display control unit 34 for confirming whether or not the communication terminal paired with the pair name selected in the "pair name selection display section" 3213 will participate in the target event. Note that in this embodiment, the "pair participation confirmation dialog" 3208 functions as an example of a pair participation confirmation means.

[0136] 20 again, after the display control unit 24 displays the "pair participation confirmation dialog" 3208, the transmitter / receiver 31 transmits the confirmation result to the event management device 2 (step S76). As a result, the transmitter / receiver 21 of the event management device 2 receives the confirmation result transmitted by the communication terminal 3. At this time, the confirmation result includes the selected pair information or information indicating that the pair will not participate, and the "OK" button information or "Participate with only this communication terminal" button information operated on the dialog.

[0137] Next, the determination unit 25 of the event management device 2 performs processing to determine whether or not pair participation is required (step S77).

[0138] <Process to determine whether or not pair participation is necessary> 22 is a flowchart showing an example of a process for determining whether or not pair participation is required according to the second embodiment. First, the determination unit 25 determines, based on the received button information, whether or not the paired communication terminals are to participate (step S77-1). If the paired communication terminals are to participate, that is, if the "OK button" 3314 is operated (step S77-1; YES), the generation unit 27 generates an event participation request for allowing all communication terminals indicated by the read pair names to participate in the target event, and then exits this flow (step S77-2).

[0139] On the other hand, if the paired communication terminal is not to be allowed to participate, that is, if the "Participate with this communication terminal only button" 3315 is operated (step S77-1; NO), the generation unit 27 generates an event participation request for allowing only the communication terminal that operated the start button in step S71 to participate in the target event, and then exits this flow (step S77-3). Note that the processes from step S81 to S88 are repeatedly performed for all communication terminals that are the targets of the event participation request.

[0140] <Event Start Sequence> Fig. 23 is a sequence diagram showing an example of an event participation process according to the second embodiment. As shown in Fig. 23, the event management device 2 executes the following process for all pair target terminals when a pair is to participate. Note that the basic processes of each process in the sequence diagram shown in Fig. 23 are similar to those of each process in the sequence diagram shown in Fig. 18.

[0141] First, the transmitter / receiver 21 of the event management device 2 transmits a request to participate in an event to a communication terminal 3A(2) that is associated with "Meeting 1" and that has been paired with the communication terminal 3A(1) on which the "Join Now Button" 3301 for the event of "Meeting 1" has been operated (step S81). As a result, the transmitter / receiver 31(2) of the communication terminal 3A(2), i.e., the smartphone 1, receives the request to participate in the event to the target event transmitted by the event management device 2. At this time, the event participation request includes information on the event identification information and the event name, "Meeting 1." Note that the communication terminal 3A(1) is the communication terminal on which the "Join Now Button" 3301 for "Meeting 1" has been operated, as described in step S51. In this case, the communication terminal 3 (communication terminal 3A(2)) is an example of another communication terminal among the multiple communication terminals.

[0142] The operation accepting unit 32(2) of the smartphone 1 that has received the event participation request accepts the participation operation by the participant, and the executing unit 38(2) performs the process of participating in the target event (step S82).

[0143] After the execution unit 38(2) executes the participation process, the transmission / reception unit 31(2) transmits an event participation response to the event management device 2 (step S83). As a result, the transmission / reception unit 21 of the event management device 2 receives the event participation response transmitted by the communication terminal 3A(2). This event participation response includes the participant identification information and the terminal identification information.

[0144] The memory readout unit 29 of the event management device 2 that has received the event participation response performs a registration process for the participant and the communication terminal (step S84). Specifically, the memory readout unit 29, in cooperation with the management unit 28, sets the participation status corresponding to the participant name indicated by the participant identification information in the participant management DB 2004 (see FIG. 5D) to "participating." Furthermore, in cooperation with the management unit 28, the memory readout unit 29 sets the participation terminal name (smartphone 1) corresponding to the terminal identification information as the terminal name of the communication terminal in the participation terminal management DB 2005 (see FIG. 5E).

[0145] Next, the transmitter / receiver 21 transmits a request to participate in the target event ("Meeting 1") to the shared terminal 4 (electronic whiteboard 1) (step S85). As a result, the transmitter / receiver 41 of the shared terminal 4 receives the request to participate in the target event transmitted by the event management device 2. At this time, the event participation request includes the event identification information and information on the event name, "Meeting 1." In addition, in this case, the shared terminal 4 is another example of another communication terminal among the multiple communication terminals. In the processes of steps S81 and S85 described above, the notebook PC 1, which is an example of a communication terminal 3A(1), the smartphone 1, which is an example of a communication terminal 3A(2), and the electronic whiteboard 1, which is an example of a shared terminal 4, are communication terminals associated with "Meeting 1," which is an example of a predetermined event, and "Conference Room 1," which is an example of a predetermined resource where "Meeting 1" is held.

[0146] The operation accepting unit 42 of the shared terminal 4 that has received the event participation request accepts the participation operation by the organizer (or a participant participating in the same "Meeting 1"), and the executing unit 48 performs the participation process for the target event (step S86).

[0147] After the execution unit 48 executes the participation process, the transmitter / receiver 41 transmits an event participation response to the event management device 2 (step S87). As a result, the transmitter / receiver 21 of the event management device 2 receives the event participation response transmitted by the shared terminal 4. This participation response includes the participant identification information and the terminal identification information.

[0148] The memory readout unit 29 of the event management device 2 that has received the event participation response performs a registration process for the participant and the communication terminal (step S88). Specifically, the memory readout unit 29, in cooperation with the management unit 28, sets the participation status corresponding to the participant name indicated by the participant identification information in the participant management DB 2004 (see FIG. 5D) to "participating." Furthermore, in cooperation with the management unit 28, the memory readout unit 29 sets the participant terminal name (electronic whiteboard 1) corresponding to the terminal identification information as the terminal name of that communication terminal in the participant terminal management DB 2005 (see FIG. 5E). Note that the processes from step S81 to S88 are repeatedly performed for all communication terminals that are the targets of the event participation request.

[0149] Similar to the processing for Pair 1 described above, processing is also performed for each communication terminal paired as Pair 2. Furthermore, the smartphone 1 and tablet terminal 1 paired with the laptop PC 1 may be used by the participants themselves who have participated in "Conference 1" held in "Conference Room 1," or may be lent to other participants who have participated in "Conference 1" and used by them.

[0150] [Major Effects of the Second Embodiment] As described above, according to this embodiment, after accepting the operation of the start button, the event management device 2 receives an event start request for starting "Conference 1" transmitted by the communication terminal 3A(1) (step S72). Thereafter, the event management device 2 transmits pair participation confirmation dialog information including button information to the communication terminal 3 (step S74). This not only produces the effect of the first embodiment, but also produces the effect of being able to prompt other communication terminals that have been paired with the communication terminal 3 to confirm whether or not they want to participate in a predetermined event.

[0151] [Modification of the second embodiment] Next, a modified example of the second embodiment will be described with reference to Figures 25 to 27. In the modified example of the second embodiment, when a participant starts a predetermined event, the shared terminal 4 used in the predetermined event performs conference start processing on the event management device 2. Note that the configuration of the event management system according to the modified example of the second embodiment is the same as the devices, hardware configurations, and functional configurations in the event management system according to the second embodiment, and therefore description thereof will be omitted here.

[0152] <Event start request from electronic whiteboard> 25 is a sequence diagram showing an example of an event start process according to a modified example of the second embodiment. As shown in FIG. 25, the operation accepting unit 42 of the shared terminal 4 (electronic whiteboard 1) accepts an operation of the start button by a participant or the organizer of "Meeting 1," which is an example of a predetermined event (Step S111). The start button at this time may be any button provided on the electronic whiteboard 1, and there are no particular restrictions as long as the function is associated with starting the predetermined event. In this case, the shared terminal 4 is another example of one of the multiple communication terminals.

[0153] After accepting the operation of the start button, the transmitter / receiver 41 of the shared terminal 4 transmits an event start request to the event management device 2 (step S112). As a result, the transmitter / receiver 21 of the event management device 2 receives the event start request transmitted by the shared terminal 4. At this time, the event start request includes the event identification information indicated by "Meeting 1" and the terminal identification information of the shared terminal 4.

[0154] Next, the determination unit 25 of the event management device 2 performs a process of determining whether or not there is a paired terminal (step S113). Note that the process of determining whether or not there is a paired terminal in step S113 is the same as the process described in step S73 above, and therefore a detailed description thereof will be omitted.

[0155] After determining whether or not there is a paired terminal, the transmitter / receiver 21 transmits pair participation confirmation dialog information including button information to the shared terminal 4 (step S114). As a result, the transmitter / receiver 41 of the shared terminal 4 receives the pair participation confirmation dialog information transmitted by the event management device 2.

[0156] Display control unit 44 of shared terminal 4 that has received the pair participation confirmation dialogue information displays "pair participation confirmation dialogue" 4201, which will be described later, on display screen 4101 on display 420 (step S115).

[0157] ●Screen display example● FIG. 27 is an example of a screen display of a pair participation confirmation dialog according to a modified example of the second embodiment. As shown in FIG. 27, a "pair participation confirmation dialog" 4201 is displayed by the display control unit 44 on a display screen 4101 on the display 420 of the shared terminal 4. Furthermore, on the "pair participation confirmation dialog" 4201, a "pair name selection display section" 4211 in which a pair name can be selected in a drop-down manner is displayed by the display control unit 44. Furthermore, on the "pair participation confirmation dialog" 4201, an "OK button" 4221 and a "participate with this communication terminal only button" 4222 are displayed by the display control unit 44 for confirming whether or not the communication terminal paired with the pair name selected in the "pair name selection display section" 4211 is to participate in the target event. Furthermore, on the display screen 4101, a "various function selection button" 4301 and a "various setting button" 4302 are displayed by the display control unit 44. The "various function selection buttons" 4301 allow the selection of functions such as video camera, microphone, and exiting the event, and the "various setting buttons" 4302 allow the addition and setting of participants.

[0158] 25 again, after the display control unit 44 displays the "pair participation confirmation dialog" 4201, the transmitter / receiver 41 transmits the confirmation result to the event management device 2 (step S116). As a result, the transmitter / receiver 21 of the event management device 2 receives the confirmation result transmitted by the shared terminal 4. At this time, the confirmation result includes the selected pair information or information indicating no pair participation, and the "OK" button information or "Participate with only this communication terminal" button information operated on the dialog.

[0159] Next, the determination unit 25 of the event management device 2 performs a process of determining whether or not the pair participation is necessary (step S117). Note that the process of determining whether or not the pair participation is necessary is the same as the process of step S77 described above, and therefore a description thereof will be omitted.

[0160] <Event Start Sequence> Fig. 26 is a sequence diagram showing an example of an event participation process according to a modified example of the second embodiment. As shown in Fig. 26, the event management device 2 executes the following process for all pair target terminals when a pair is to participate. Note that the processes in the sequence diagram shown in Fig. 26 are basically the same as the processes in the sequence diagram shown in Fig. 23.

[0161] First, the transmitter / receiver 21 of the event management device 2 transmits a request to participate in the event to communication terminal 3A(1), which is associated with "Meeting 1" and is a communication terminal that has been paired with the shared terminal 4 whose start button has been operated for the event "Meeting 1" (step S121). As a result, communication terminal 3A(1), i.e., the transmitter / receiver 31(1) of the notebook PC 1, receives the request to participate in the event to the target event that has been transmitted by the event management device 2. At this time, the event participation request includes information about the event identification information and the event name, "Meeting 1." Note that, as described in step S111, the shared terminal 4 is the communication terminal whose start button has been operated for "Meeting 1." In this case, the communication terminal 3 (communication terminal 3A(1)) is an example of another communication terminal among the multiple communication terminals.

[0162] The operation accepting unit 32(1) of the notebook PC 1 that has received the event participation request accepts the participation operation by the participant, and the executing unit 38(1) performs the process of participating in the target event (step S122).

[0163] After the execution unit 38(1) executes the participation process, the transmission / reception unit 31(1) transmits an event participation response to the event management device 2 (step S123). As a result, the transmission / reception unit 21 of the event management device 2 receives the participation response transmitted by the communication terminal 3A(1). This event participation response includes the participant identification information and the terminal identification information.

[0164] The memory readout unit 29 of the event management device 2 that has received the event participation response performs a registration process for the participant and the communication terminal (step S124). Specifically, the memory readout unit 29, in cooperation with the management unit 28, sets the participation status corresponding to the participant name indicated by the participant identification information in the participant management DB 2004 (see FIG. 5D) to "participating." Furthermore, the memory readout unit 29, in cooperation with the management unit 28, sets the participation terminal name (notebook PC1) corresponding to the terminal identification information as the terminal name of that communication terminal in the participation terminal management DB 2005 (see FIG. 5E).

[0165] Next, the transmitter / receiver 21 transmits an event participation request for the target event ("Meeting 1") to the communication terminal 3A(2), which is the paired communication terminal (step S125). As a result, the transmitter / receiver 31(2) of the communication terminal 3A(2) receives the event participation request for the target event transmitted by the event management device 2. At this time, the event participation request includes event identification information and information on the event name, "Meeting 1." In addition, in this case, the communication terminal 3 (communication terminal 3A(2)) is another example of another communication terminal among the multiple communication terminals. In the processes of steps S121 and S125 described above, the notebook PC 1, which is an example of the communication terminal 3A(1), the smartphone 1, which is an example of the communication terminal 3A(2), and the electronic whiteboard 1, which is an example of the shared terminal 4, are communication terminals associated with "Meeting 1," which is an example of a predetermined event, and "Conference Room 1," which is an example of a predetermined resource where "Meeting 1" is held.

[0166] The operation accepting unit 32(2) of the communication terminal 3A(2) that has received the event participation request accepts the participation operation by the organizer (or a participant participating in the same "Meeting 1"), and the executing unit 38(2) performs the participation process for the target event (step S126).

[0167] After the execution unit 38(2) executes the participation process, the transmission / reception unit 31(2) transmits an event participation response to the event management device 2 (step S127). As a result, the transmission / reception unit 21 of the event management device 2 receives the event participation response transmitted by the communication terminal 3A(2). This event participation response includes the participant identification information and the terminal identification information.

[0168] The memory readout unit 29 of the event management device 2 that has received the event participation response performs a process of registering the participant and the communication terminal (step S128). Specifically, the memory readout unit 29, in cooperation with the management unit 28, sets the participation status corresponding to the participant name indicated by the participant identification information in the participant management DB 2004 (see FIG. 5D) to "participating." Furthermore, the memory readout unit 29, in cooperation with the management unit 28, sets the participation terminal name (smartphone 1) corresponding to the terminal identification information as the terminal name of the communication terminal in the participation terminal management DB 2005 (see FIG. 5E). Note that the processes from step S121 to S128 are repeatedly performed for all communication terminals that are the targets of the event participation request.

[0169] Note that similar to the processing for Pair 1 described above, processing is also performed for each communication terminal paired as Pair 2. Furthermore, the notebook PC 1 and smartphone 1 paired with the shared terminal 4 may be used by the participants who have participated in "Conference 1" held in "Conference Room 1," or may be lent to other participants who have participated in "Conference 1" and used by them.

[0170] <When a communication terminal or a shared terminal has the function of an event management device (P2P)> In this embodiment, a case will be described in which the various functions of the event management device 2 are provided to a communication terminal 3 or a shared terminal 4 participating in a predetermined event. In this case, the event management system 1 does not require the event management device 2, and P2P (Peer to Peer) communication may be performed between each communication terminal 3 and the shared terminal 4 to execute the event participation start process, event participation response process, and event participation request process for the predetermined event. In such a case, data tables may be managed separately for the terminal (inviting terminal) that starts participation in the predetermined event and the terminal (invited terminal) that is requested to participate in the predetermined event. Furthermore, if a usage scenario is anticipated in which a single communication terminal alternates between being an inviting terminal and an invited terminal, a "P2P event management system" may be constructed in which a dedicated server that stores and manages various data tables is accessed via communication network 100, the server downloads the required data table, and the table is used as needed.

[0171] [Major Effects of the Modification of the Second Embodiment] As described above, according to this embodiment, the event management device 2 accepts the operation of the start button by the organizer of "Meeting 1" transmitted from the electronic whiteboard 1, which is an example of the shared terminal 4 (step S111). After that, the event management device 2 transmits pair participation confirmation dialog information including button information to the shared terminal 4 (step S114). This provides the effect that, through the operation of the organizer who hosts a specific event, it is possible to prompt other communication terminals that have been paired with the shared terminal 4 to confirm whether or not they want to participate in the specific event.

[0172] [Supplementary explanation of the embodiment] The data tables stored and managed by the event management device 2 are merely examples, and the definitions of each item, the setting conditions and setting timing, and the exchange of information (data) with each data table are not limited to those described above.

[0173] Furthermore, each function of the above-described embodiments can be realized by one or more processing circuits. Here, the term "processing circuit" in this specification includes a device programmed to perform each function by software, such as a processor implemented by electronic circuits. This device refers to, for example, a processor, an application-specific integrated circuit (ASIC), a digital signal processor (DSP), a field programmable gate array (FPGA), a system on a chip (SOC), a graphics processing unit (GPU), or a conventional circuit module designed to perform each of the above-described functions.

[0174] Furthermore, the text and various tables obtained by the OCR processing in the above-described embodiments may be generated by the learning effects of machine learning, or data for each associated item may be classified using machine learning, eliminating the need for OCR or tables. Here, machine learning refers to a technology that allows a computer to acquire human-like learning capabilities, in which the computer autonomously generates algorithms necessary for judgments such as data identification from previously acquired learning data and applies these algorithms 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. Furthermore, the learning method for machine learning may be a combination of these learning methods, or any learning method for machine learning.

[0175] So far, we have described an event management system, an event management device, an event management method, and a program according to one embodiment of the present invention. However, the present invention is not limited to the above-described embodiment, and other embodiments can be added, modified, or deleted 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. [Explanation of symbols]

[0176] 1. Event Management System 2. Event Management Device 3. Communication terminals 4 Shared terminals 21 Transmitting / receiving unit (an example of receiving means, an example of transmitting means) 31 Transmitting / receiving unit (an example of receiving means, an example of transmitting means) 38 Execution unit (an example of execution means) 48 Execution unit (an example of execution means) 3208 Pair participation confirmation dialog (an example of a method for confirming pair participation) 3303 Device pairing setting button (an example of a device combination setting acceptance means) [Prior art documents] [Patent documents]

[0177] [Patent Document 1] Japanese Patent Application Laid-Open No. 2015-211316

Claims

1. An event management system having a plurality of communication terminals used in a predetermined event, and an event management device that manages the plurality of communication terminals and the predetermined event in association with each other, the event management device, a receiving means for receiving an event start request for requesting the start of the predetermined event, the event start request being transmitted from one of the plurality of communication terminals; a transmitting means for transmitting an event participation request to another communication terminal among the plurality of communication terminals associated with the predetermined event and associated with a participant who will use the one communication terminal to participate in the predetermined event in response to the event start request received by the receiving means; and and The one communication terminal a display control means for displaying on a display means a terminal combination setting accepting means for associating and setting the one communication terminal with the other communication terminal; having An event management system.

2. The receiving means receiving the event start request generated by an operation to participate in the predetermined event performed on the one communication terminal; The event management system of claim 1 .

3. The transmitting means transmitting an event start response to the event start request received by the receiving means to the one communication terminal; 3. The event management system according to claim 1 or 2.

4. The transmitting means transmitting the event participation request to the other communication terminals that are used together with the one communication terminal in a predetermined resource where the predetermined event is to be held; The event management system according to any one of claims 1 to 3.

5. 5. An event management system according to claim 1, further comprising: The other communication terminal a receiving means for receiving the event participation request transmitted by the event management device; an execution means for executing a process for participating in the predetermined event in response to the event participation request received by the receiving means; having An event management system.

6. The other communication terminal a communication terminal associated with event identification information for identifying the predetermined event; The event management system according to any one of claims 1 to 5.

7. The other communication terminal a communication terminal associated with participant identification information for identifying participants participating in the predetermined event; The event management system according to any one of claims 1 to 5.

8. The other communication terminal a shared terminal used in the resource where the predetermined event is performed; The event management system according to any one of claims 1 to 7.

9. The display control means displaying on the display means the other communication terminals and the shared terminals to be used in the predetermined event; The event management system of claim 8 .

10. The display control means displaying on the display means a combination participation confirmation means for inquiring of the participant as to whether or not the one communication terminal and the other communication terminal will participate in the predetermined event in a combination set in association with each other; 10. The event management system according to claim 8 or 9.

11. An event management method executed by an event management device that manages a predetermined event in association with one of a plurality of communication terminals used in the predetermined event, the method comprising: a receiving step of receiving an event start request transmitted by the one communication terminal to request the start of the predetermined event; a transmitting step of transmitting an event participation request to another communication terminal among the plurality of communication terminals associated with the predetermined event and associated with a participant who will use the one communication terminal to participate in the predetermined event in response to the event start request received by the receiving step; a display control step of displaying on a display means a terminal combination setting accepting means for associating and setting the one communication terminal with the other communication terminal; Performing a process including An event management method comprising:

12. an event management device that manages one of a plurality of communication terminals used in a predetermined event in association with the predetermined event; a receiving step of receiving an event start request transmitted by the one communication terminal to request the start of the predetermined event; a transmitting step of transmitting an event participation request to another communication terminal among the plurality of communication terminals associated with the predetermined event and associated with a participant who will use the one communication terminal to participate in the predetermined event in response to the event start request received by the receiving step; a display control step of displaying on a display means a terminal combination setting accepting means for associating and setting the one communication terminal with the other communication terminal; A program that executes processing including

Images