System

Abstract

A system is provided.SOLUTION: The system includes a means for collecting event information across the country and notifying the user according to the user's preference, a means for providing and evaluating a ticket sales schedule and a ticket purchase method, a means for providing transportation means to an event venue and accommodation facility information around the venue and supporting reservations, a means for proposing an action plan based on the user's itinerary and event schedule, and a means for providing a community function that allows users having the same purpose to interact with each other.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The technology of the present disclosure relates to a system. [Background technology]

[0002] Patent document 1 discloses a persona chatbot control method performed by at least one processor, the method including the steps of receiving a user utterance, adding the user utterance to a prompt including an instruction sentence related to a description of the chatbot character, encoding the prompt, and inputting the encoded prompt into a language model to generate a chatbot utterance in response to the user utterance. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Publication No. 2022-180282 Summary of the Invention [Problem to be solved by the invention]

[0004] In recent years, the number of individuals participating in events and activities has increased, but this has also led to challenges such as the difficulty of centralizing related information.Specific issues include scattered event information, unclear ticket purchasing information, complicated transportation and accommodation arrangements, and a lack of communication between event participants.These issues make it difficult for users to participate in events efficiently, so a system that solves these issues is needed. [Means for solving the problem]

[0005] The present invention solves the above problems by providing a system that includes a means for collecting event information from around the country and notifying users based on their preferences, a means for providing and rating ticket sales schedules and purchasing methods, a means for providing information on transportation to event locations and accommodations near the venues to support reservations, a means for suggesting an action plan based on the user's itinerary and event schedule, and a means for providing a community function that allows users with similar goals to interact with each other. This system unifies event information, promotes efficient user participation in events, and promotes smooth communication between users.

[0006] "Event information" is detailed data about various events held across the country, including information on the date, time, location, participation conditions, performers, and content.

[0007] "Notifications" is a feature that notifies users of information of interest in real time, and takes the form of push notifications or emails.

[0008] A "ticket release schedule" is a plan for the dates and times when tickets for an event will go on sale.

[0009] "How to buy" refers to specific steps to obtain tickets and information about available platforms.

[0010] "Rating" refers to the analysis results used to provide users with information on the difficulty of obtaining tickets and their purchase value.

[0011] "Transportation" means public transportation or other means of travel used to travel to the Event location.

[0012] "Accommodation Information" means data about hotels and other accommodations located near the Event Venue, including rates and availability.

[0013] An "itinerary" is a plan regarding travel, accommodation, and schedule for a user's participation in an event.

[0014] An "action plan" is a set of specific steps or recommended schedules that will help users efficiently reach their destination and enjoy the event.

[0015] The "community function" is an online platform where users with the same events or interests can exchange information and interact with each other. [Brief explanation of the drawings]

[0016] [Figure 1] 1 is a conceptual diagram showing an example of the configuration of a data processing system according to a first embodiment. [Figure 2] 1 is a conceptual diagram showing an example of main functions of a data processing device and a smart device according to a first embodiment. [Figure 3] FIG. 10 is a conceptual diagram showing an example of the configuration of a data processing system according to a second embodiment. [Figure 4] FIG. 10 is a conceptual diagram showing an example of main functions of a data processing device and smart glasses according to a second embodiment. [Figure 5] FIG. 10 is a conceptual diagram showing an example of the configuration of a data processing system according to a third embodiment. [Figure 6] FIG. 11 is a conceptual diagram showing an example of main functions of a data processing device and a headset-type terminal according to a third embodiment. [Figure 7] FIG. 10 is a conceptual diagram showing an example of the configuration of a data processing system according to a fourth embodiment. [Figure 8] FIG. 10 is a conceptual diagram showing an example of main functions of a data processing device and a robot according to a fourth embodiment. [Figure 9] 1 shows an emotion map onto which multiple emotions are mapped. [Figure 10] 1 shows an emotion map onto which multiple emotions are mapped. [Figure 11] FIG. 3 is a sequence diagram showing a processing flow of the data processing system according to the first embodiment. [Figure 12] FIG. 10 is a sequence diagram showing the flow of processing in the data processing system in Application Example 1. [Figure 13] FIG. 10 is a sequence diagram showing the flow of processing in the data processing system according to the second embodiment when an emotion engine is combined. [Figure 14] FIG. 10 is a sequence diagram showing the flow of processing in the data processing system in Application Example 2 when an emotion engine is combined. DETAILED DESCRIPTION OF THE INVENTION

[0017] An example of an embodiment of a system according to the technology of the present disclosure will be described below with reference to the accompanying drawings.

[0018] First, the terms used in the following description will be explained.

[0019] In the following embodiments, a coded processor (hereinafter simply referred to as a "processor") may be a single arithmetic device or a combination of multiple arithmetic devices. Furthermore, a processor may be a single type of arithmetic device or a combination of multiple types of arithmetic devices. Examples of arithmetic devices include a CPU (Central Processing Unit), a GPU (Graphics Processing Unit), a GPGPU (General-Purpose computing on Graphics Processing Units), and an APU (Accelerated Processing Unit).

[0020] In the following embodiments, a coded RAM (Random Access Memory) is a memory in which information is temporarily stored and is used as a working memory by a processor.

[0021] In the following embodiments, the coded storage is one or more non-volatile storage devices that store various programs, various parameters, etc. Examples of non-volatile storage devices include flash memory (SSD (Solid State Drive)), magnetic disks (e.g., hard disks), and magnetic tapes.

[0022] In the following embodiments, a communication I / F (Interface) with a symbol is an interface including a communication processor, an antenna, etc. The communication I / F controls communication between multiple computers. Examples of communication standards applied to the communication I / F include wireless communication standards including 5G (5th Generation Mobile Communication System), Wi-Fi (registered trademark), Bluetooth (registered trademark), etc.

[0023] In the following embodiments, "A and / or B" is synonymous with "at least one of A and B." In other words, "A and / or B" means that it may be only A, only B, or a combination of A and B. Furthermore, in this specification, the same concept as "A and / or B" is also applied when three or more things are expressed connected by "and / or."

[0024] [First embodiment]

[0025] FIG. 1 shows an example of the configuration of a data processing system 10 according to the first embodiment.

[0026] 1, a data processing system 10 includes a data processing device 12 and a smart device 14. An example of the data processing device 12 is a server.

[0027] The data processing device 12 includes a computer 22, a database 24, and a communication I / F 26. The computer 22 is an example of a "computer" according to the technology of the present disclosure. The computer 22 includes a processor 28, a RAM 30, and a storage 32. The processor 28, the RAM 30, and the storage 32 are connected to a bus 34. The database 24 and the communication I / F 26 are also connected to the bus 34. The communication I / F 26 is connected to a network 54. Examples of the network 54 include a WAN (Wide Area Network) and / or a LAN (Local Area Network).

[0028] The smart device 14 includes a computer 36, a reception device 38, an output device 40, a camera 42, and a communication I / F 44. The computer 36 includes a processor 46, a RAM 48, and a storage 50. The processor 46, the RAM 48, and the storage 50 are connected to a bus 52. The reception device 38, the output device 40, and the camera 42 are also connected to the bus 52.

[0029] The reception device 38 includes a touch panel 38A, a microphone 38B, and the like, and receives user input. The touch panel 38A detects contact with an indicator (for example, a pen or a finger) to receive user input by the touch of the indicator. The microphone 38B detects the user's voice to receive user input by voice. The control unit 46A transmits data indicating the user input received by the touch panel 38A and the microphone 38B to the data processing device 12. In the data processing device 12, the specific processing unit 290 acquires the data indicating the user input.

[0030] The output device 40 includes a display 40A and a speaker 40B, and presents data to the user 20 by outputting the data in a form of expression that the user 20 can perceive (for example, audio and / or text). The display 40A displays visible information such as text and images in accordance with instructions from the processor 46. The speaker 40B outputs audio in accordance with instructions from the processor 46. The camera 42 is a compact digital camera equipped with an optical system including a lens, aperture, and shutter, and an imaging element such as a CMOS (Complementary Metal-Oxide-Semiconductor) image sensor or a CCD (Charge Coupled Device) image sensor.

[0031] The communication I / F 44 is connected to a network 54. The communication I / Fs 44 and 26 control the exchange of various information between the processor 46 and the processor 28 via the network 54.

[0032] FIG. 2 shows an example of the main functions of the data processing device 12 and the smart device 14.

[0033] 2, in the data processing device 12, a specific process is performed by the processor 28. A specific processing program 56 is stored in the storage 32. The specific processing program 56 is an example of a "program" according to the technology of the present disclosure. The processor 28 reads the specific processing program 56 from the storage 32 and executes the read specific processing program 56 on the RAM 30. The specific process is realized by the processor 28 operating as a specific processing unit 290 in accordance with the specific processing program 56 executed on the RAM 30.

[0034] The storage 32 stores a data generation model 58 and an emotion identification model 59. The data generation model 58 and the emotion identification model 59 are used by the identification processing unit 290.

[0035] In the smart device 14, the processor 46 performs the reception output process. The storage 50 stores a reception output program 60. The reception output program 60 is used in conjunction with the specific processing program 56 by the data processing system 10. The processor 46 reads the reception output program 60 from the storage 50 and executes the read reception output program 60 on the RAM 48. The reception output process is realized by the processor 46 operating as the control unit 46A in accordance with the reception output program 60 executed on the RAM 48.

[0036] Next, a description will be given of the specific processing performed by the specific processing unit 290 of the data processing device 12. In the following description, the data processing device 12 will be referred to as a "server" and the smart device 14 will be referred to as a "terminal."

[0037] The system of the present invention provides a series of support functions for users to participate in events. Specifically, it includes functions for collecting event information, notifications, ticket guides, providing transportation and accommodation information, schedule planning, and community functions. The operation of this system is explained based on the following main steps.

[0038] Event information collection and notification

[0039] The server collects event data from external event information sources (official sites, APIs, etc.) and stores it in a database. Based on the user's preferences, the server filters the relevant event information and sends the results to the device. The device notifies the user of the information via push notification or email according to the user's settings.

[0040] Example: If a user specifies that they want to see events by a particular artist, the server will automatically notify the user when new events by that artist are added.

[0041] Providing ticket guides

[0042] The server stores the ticket sales schedule and purchase method in a database based on the collected event information. When a user views ticket information, the device retrieves the relevant information from the server and displays it on the user interface. In addition, the server evaluates the difficulty of obtaining tickets and sends feedback to the device.

[0043] Example: When a user checks ticket information on an event's details page, the device displays information from the server about the release date, how to purchase, and how easy it is to obtain tickets.

[0044] Providing transportation and accommodation information and reservation support

[0045] The server collects information on transportation to the event venue and accommodation options around the venue and stores it in a database. When a user needs transportation or accommodation information, the terminal retrieves the optimal transportation and accommodation options from the server and displays them on the user interface. In addition, the terminal provides reservation support functions, allowing users to complete reservations directly.

[0046] Example: When a user searches for transportation to an event, the device retrieves and displays the most suitable train and bus information from the server. At the same time, it also displays information about nearby accommodations and provides a reservation link if necessary.

[0047] Schedule planner function

[0048] Users register their travel itineraries and event schedules in the schedule planner. The device sends this information to the server, which stores it in a database and analyzes it. Based on the analysis results, the server calculates an optimal action plan and sends it to the device. The device then presents it to the user and helps them participate in events based on that action plan.

[0049] Example: When a user registers the mode of transportation and arrival time for the day of an event in their schedule planner, the server analyzes this and suggests which mode of transportation to use at what time.

[0050] Community Features

[0051] The server provides an online community function that allows users to interact with each other. Users can access the community page through their devices and post or comment on the message board. The server stores these posts in a database and makes them available to other users.

[0052] Example: A user asks on a community message board for recommendations on restaurants near the venue just before an event, and other users reply and share that information.

[0053] As described above, the system of the present invention streamlines the series of procedures required to participate in an event and provides optimal support to users. This system allows users to smoothly complete all processes, including information gathering, ticket purchase, transportation and accommodation arrangements, schedule management, and community participation.

[0054] The processing flow will be explained below.

[0055] Step 1:

[0056] The user enters information into the new registration form. The user enters their name, email address, password, etc. on the device and presses the registration button.

[0057] Step 2:

[0058] The device sends registration information to the server. The front end sends a POST request to the backend API, sending user information to the server.

[0059] Step 3:

[0060] The server saves the user information in the database. The server receives the user information, validates it (checks for format and duplication), and saves it in the database. After saving, a confirmation email is sent to the user.

[0061] Step 4:

[0062] The user receives a confirmation email and activates the account. The user opens the confirmation email and clicks the link to activate the account.

[0063] Step 5:

[0064] The server confirms the account activation. The server receives the link click, updates the account status in the database to activated, and notifies the user that activation is complete.

[0065] Step 6:

[0066] A user opens the event listing page. A user opens the event listing page on their device.

[0067] Step 7:

[0068] The device requests the latest event information from the server. The front end sends a GET request to the back end API to obtain the latest event information.

[0069] Step 8:

[0070] The server retrieves event information from the database. The server searches for the necessary event information from the database and returns it in JSON format.

[0071] Step 9:

[0072] The terminal displays the event information. The front end parses the received JSON data and displays the event information in the user interface.

[0073] Step 10:

[0074] The user sets notification settings. The user turns on notification settings for specific idle times.

[0075] Step 11:

[0076] The device sends the notification settings to the server. The front end sends a PUT request to the backend API to update the notification settings.

[0077] Step 12:

[0078] The server saves the notification settings in the database. The server saves the notification settings it receives in the database.

[0079] Step 13:

[0080] User selects a specific event and opens the details page. User visits the event details page on their device to view more information.

[0081] Step 14:

[0082] The terminal requests ticket information from the server. The front end sends a GET request to the backend API to obtain the ticket information.

[0083] Step 15:

[0084] The server retrieves ticket information from the database. The server searches the database for ticket information based on the event ID and returns it in JSON format.

[0085] Step 16:

[0086] The terminal displays the ticket information. The front-end parses the received JSON data and displays the ticket information on the page.

[0087] Step 17:

[0088] The user purchases a ticket. The user presses the ticket purchase button to begin the purchase process.

[0089] Step 18:

[0090] The terminal sends a purchase request to the server. The front end sends a POST request to the backend API to complete the purchase.

[0091] Step 19:

[0092] The server sends a request to the payment service. The server sends a request to the external payment service to process the payment.

[0093] Step 20:

[0094] The server receives the payment result and updates the database. If the payment is successful, the server saves the purchase data in the database and sends a confirmation email to the user.

[0095] Step 21:

[0096] The user plans their trip, using the in-app schedule planner to select transportation and accommodations.

[0097] Step 22:

[0098] The terminal sends the schedule information to the server. The front end sends a POST request to the backend API to send the schedule information to the server.

[0099] Step 23:

[0100] The server calculates the optimal itinerary and saves it in the database.The server calculates the optimal itinerary based on the schedule information and saves it in the database.

[0101] Step 24:

[0102] A user opens the community page. A user accesses the community page on their device and browses the message board.

[0103] Step 25:

[0104] The terminal requests bulletin board information from the server. The front end sends a GET request to the back end API to retrieve the bulletin board information.

[0105] Step 26:

[0106] The server retrieves bulletin board information from the database. The server searches the bulletin board information from the database and returns it in JSON format.

[0107] Step 27:

[0108] The terminal displays the message board information. The front end parses the received JSON data and displays the message board information on the page.

[0109] Step 28:

[0110] A user posts: A user creates a new post on the message board and presses the send button.

[0111] Step 29:

[0112] The device sends the post content to the server. The front end sends a POST request to the backend API, sending the new post to the server.

[0113] Step 30:

[0114] The server saves the posted content in a database. The server saves the posted content received in a database and updates the bulletin board information.

[0115] Example 1

[0116] Next, a description will be given of Example 1. In the following description, the data processing device 12 will be referred to as a "server" and the smart device 14 will be referred to as a "terminal."

[0117] In the past, gathering information, purchasing tickets, and arranging transportation and accommodation to participate in an event required time and effort, placing a burden on users. Furthermore, the management of event information and participation plans was dispersed, making it difficult to participate in events efficiently. Furthermore, opportunities to share information through interactions with other participants were limited.

[0118] The specific processing by the specific processing unit 290 of the data processing device 12 in the first embodiment is realized by the following means.

[0119] In this invention, the server includes: means for collecting event information from across the country and notifying users based on their preferences; means for providing and rating ticket sales schedules and purchasing methods; means for providing information on transportation to event locations and accommodations near the venues and supporting reservations; means for suggesting an action plan based on the user's itinerary and event schedule; means for providing a community function that allows users with similar interests to interact with each other; means for periodically collecting event information from external sources and storing it in a database; means for filtering the information based on the database and notifying users of the most appropriate event information via push notification or email; and means for calculating the difficulty of obtaining tickets and providing the information to users. This allows users to efficiently collect event information and smoothly purchase tickets and make arrangements for transportation and accommodation. Users can also obtain more information by interacting with other participants.

[0120] "National event information" refers to information about events of various genres held throughout the country, not limited to a specific region.

[0121] "Notifying based on user preferences" means selecting and notifying the user of relevant event information based on the user's pre-defined interests and preferences.

[0122] "Providing and evaluating ticket release schedules and purchasing methods" means providing information about when event tickets go on sale and how to purchase them, and based on that information evaluating the difficulty and convenience of obtaining tickets and communicating that information to users.

[0123] Providing "information on transportation to the event venue and accommodations in the vicinity" and supporting reservations means providing information on transportation and accommodations for users to attend the event, and supporting the reservation process.

[0124] "Suggesting an action plan based on the user's itinerary and event schedule" means calculating and suggesting an optimal action plan to the user based on the event dates and transportation details entered by the user.

[0125] "Providing a community function that allows users with the same goals to interact with each other" means providing an online platform where event participants can share information, exchange opinions, and ask questions.

[0126] "Regularly collect from external sources and store in a database" means periodically obtaining event information from reliable external sources such as official websites and APIs and storing it in a database.

[0127] "Filtering based on a database" means sorting stored event information based on user settings and preferences.

[0128] "Notifying users of the most appropriate event information via push notification or email" means notifying users directly of filtered event information in a manner that suits their settings.

[0129] "Calculating the difficulty of obtaining tickets" means assessing the difficulty of obtaining event tickets based on past data and current demand, and providing this to users.

[0130] The system of this invention provides a series of support functions for users to participate in events. Specifically, it provides a comprehensive range of functions, including event information collection, notification, ticket guide, transportation and accommodation information, schedule planner, and community functions. To realize the operation of this system, the server, terminals, and users each play different roles.

[0131] First, the server periodically retrieves event data from external event information sources (such as official event websites or APIs). The collected data is stored in a database containing information such as the event name, date and time, location, and details. For example, a library such as the Apache HTTP client can be used to collect the information.

[0132] When a user logs in to the system and selects the genres and artists they are interested in, the server filters the relevant event information from the database based on the user's preferences. This filtering is done using database queries and stored procedures. The filtered results are sent to the device, which then notifies the user via push notification or email.

[0133] For example, if a user specifies that they want to receive notifications for events by a specific artist, the server will automatically notify the user when new events for that artist are added. An example of a prompt would be, "How do I set up notifications for events by a specific artist?"

[0134] Next, when a user views an event's details page, the device requests ticket information for that event from the server. The server retrieves ticket information (release date, price, purchase method, etc.) from the database and returns it to the device. The server then calculates the difficulty of obtaining tickets using past sales data and a demand forecasting algorithm, and sends feedback to the device.

[0135] For example, when a user checks ticket information on an event's details page, the device displays information from the server about the release date, how to purchase, and the difficulty of obtaining tickets. An example of a prompt sentence is, "Please tell me how to rate the difficulty of obtaining tickets for an event."

[0136] The server also retrieves information about transportation options to the event location (trains, buses, taxis, etc.) and accommodations near the venue from travel APIs and hotel booking site APIs, and stores this information in a database. When a user needs this information, the device retrieves the optimal options from the server and presents them to the user. Users can then use the reservation support function to complete their reservations directly.

[0137] For example, when a user searches for transportation, the device retrieves and displays the best transportation options from the server. Similarly, it displays accommodation information and provides a booking link if necessary. An example of a prompt is, "How do I search for transportation and accommodation information for an event?"

[0138] With the schedule planner function, users can register their event schedules. The device then sends the schedules to the server, which stores them in a database and analyzes them. Based on the analysis results, the server calculates an optimal action plan and sends it to the device. Users can then act accordingly.

[0139] For example, when a user enters information into a schedule planner, the server suggests which means of transportation to use at which time. An example of a prompt sentence is, "Please tell me how to calculate the optimal itinerary by entering the mode of transportation and arrival time on the day of the event."

[0140] Finally, the server provides an online community function that allows users to interact with each other. Users can access the community page through their devices and post or comment on the message board. The server stores these posts in a database and makes them available to other users.

[0141] For example, if a user asks for information about restaurants near the venue on a community bulletin board just before an event, other users will reply and share that information. An example of a prompt sentence is, "Please tell me how to ask for recommended restaurant information on a community bulletin board just before an event."

[0142] As described above, the system streamlines the entire process for users to participate in events efficiently and provides a wealth of information and support.

[0143] The flow of the identification process in the first embodiment will be described with reference to FIG.

[0144] Step 1: Gather event information

[0145] The server periodically collects event data from external event information sources (e.g., official event websites, APIs, etc.). Specifically, the server sends API requests, parses the returned data in JSON format, and stores it in a database.

[0146] Input: API request from external information source

[0147] Output: Parsed event data stored in a database

[0148] Step 2: Filtering event information

[0149] When a user logs into the system and selects the genres and artists they are interested in, the server uses a database query to filter relevant event information from the database based on the user's preferences.

[0150] Input: User interests and preferences

[0151] Output: Filtered event information

[0152] Step 3: Event information notification

[0153] The filtered event information is sent to the device, and the device notifies the user via push notification or email, depending on the user settings.

[0154] Input: Filtered event information

[0155] Output: Push notification and email notification

[0156] Step 4: Get ticket information

[0157] When a user views an event's details page, the device requests ticket information for that event from the server. The server retrieves ticket information (release date, price, purchase method, etc.) from the database and returns that information to the device.

[0158] Input: Ticket information request from user

[0159] Output: Retrieved ticket information

[0160] Step 5: Calculating ticket difficulty

[0161] The server calculates the difficulty of obtaining tickets using past sales data and demand forecasting algorithms, and provides this information to users via their devices.

[0162] Input: Past sales data, demand data

[0163] Output: Ticket acquisition difficulty rating

[0164] Step 6: Providing transportation and accommodation information

[0165] When a user searches for transportation or accommodation information for an event, the device sends a request to the server, which returns the best options to the user based on information retrieved from travel APIs and hotel booking site APIs.

[0166] Input: User request for transportation and accommodation information

[0167] Output: Best transportation and accommodation information

[0168] Step 7: Schedule Planner

[0169] Users register their event participation schedule in the schedule planner. The device sends this to the server, which stores it in a database and analyzes it. The optimal action plan is calculated and provided to the user via the device.

[0170] Input: User's schedule information

[0171] Output: Optimal action plan

[0172] Step 8: Community Features

[0173] Users can access the community page through their devices and post or comment on the message board. The server stores these posts in a database and makes them available to other users.

[0174] Input: User posts and comments

[0175] Output: Saved posts, comments displayed

[0176] (Application example 1)

[0177] Next, a description will be given of Application Example 1. In the following description, the data processing device 12 will be referred to as a "server" and the smart device 14 will be referred to as a "terminal."

[0178] Currently, when users participate in a virtual event, they must use multiple methods, such as gathering event information, purchasing tickets, checking access methods, managing schedules, and interacting with the community, which takes a lot of time and effort.In addition, access guides and real-time event information updates, which are specific to virtual events, are often not provided sufficiently.

[0179] The specific processing by the specific processing unit 290 of the data processing device 12 in the application example 1 is realized by the following means.

[0180] In this invention, the server includes means for collecting information on events across the country and notifying users based on their preferences, means for providing and rating ticket sales schedules and purchasing methods, means for providing access methods to the event location or virtual event venue and information on nearby accommodations and supporting reservations, means for proposing an action plan based on the user's itinerary and event schedule, means for providing a community function that allows users with the same goals to interact with each other, and means for providing a guide to accessing the virtual venue.This significantly reduces the effort and time required for users to participate in virtual events, allowing them to enjoy the event more smoothly.

[0181] "Collecting event information nationwide" means gathering data on various events across the country.

[0182] "Providing notifications based on user preferences" means notifying users of appropriate event information based on the interests and concerns they have set.

[0183] "Providing and evaluating ticket release schedules and purchasing methods" means providing information about the sale period and purchasing methods of event tickets and evaluating the difficulty of obtaining them.

[0184] "How to access the event location or virtual event venue" means directions to the physical location where the event is being held or how to access the online virtual space.

[0185] "Providing information about nearby accommodations and supporting reservations" means providing information about accommodations near the venue and helping people make reservations.

[0186] "Suggesting an action plan based on the user's itinerary and event schedule" means proposing the optimal action plan based on the schedule of events and plans set by the user.

[0187] "Providing a community function that allows users with the same goals to interact with each other" means providing a function that allows users with common interests and goals to exchange opinions and share information.

[0188] "Providing a guide to accessing the virtual venue" means providing instructions and procedures for accessing the virtual space where the event will be held online.

[0189] "Push notifications about specific events and areas of interest based on user preferences" means providing real-time notifications about relevant events and areas of interest based on user-specified preferences.

[0190] The present invention is a system that comprehensively supports users' participation in events, and includes the following configuration and operation.

[0191] Event information collection and notification

[0192] The server collects event data from external event information sources (such as official websites and APIs) and stores it in a database. Based on the user's preferences, the server filters the relevant event information and sends the results to the device. The device then notifies the user of the information via push notifications or emails, depending on the user's settings.

[0193] For example, if a user specifies that they want to see events by a particular artist, the server will collect event information for that artist and automatically send notifications.

[0194] Providing ticket guides

[0195] The server stores the ticket sales schedule and purchase method in a database based on the collected event information. When a user views ticket information, the device retrieves the relevant information from the server and displays it on the user interface. The server also evaluates the difficulty of obtaining tickets and sends the evaluation results to the device.

[0196] For example, when a user checks ticket information on an event's details page, the device displays information from the server about the release date, how to purchase tickets, and how difficult it is to obtain tickets.

[0197] Providing transportation and accommodation information and reservation support

[0198] The server collects information on how to access the event venue or virtual event venue and accommodation information around the venue and stores it in a database. When a user needs transportation or accommodation information, the terminal retrieves the optimal transportation and accommodation options from the server and displays them on the user interface. In addition, the terminal provides reservation support functions, allowing users to complete reservations directly.

[0199] For example, when a user searches for transportation to an event, the device retrieves the optimal transportation and accommodation information from the server and displays it, and also provides a reservation link if necessary.

[0200] Schedule planner function

[0201] Users register their travel itineraries and event schedules in the schedule planner. The device sends this information to the server, which stores it in a database and analyzes it. Based on the analysis results, the server calculates an optimal action plan and sends it to the device. The device then presents it to the user and helps them participate in events based on that action plan.

[0202] As a concrete example, when a user registers the mode of transportation and arrival time for the day of the event in their schedule planner, the server analyzes this and suggests which mode of transportation to use at what time.

[0203] Community Features

[0204] The server provides an online community function that allows users to interact with each other. Users can access the community page through their devices and post or comment on the message board. The server stores these posts in a database and makes them available to other users.

[0205] For example, if a user asks on a community bulletin board for information about recommended restaurants near the venue just before an event, other users will reply and share that information.

[0206] Virtual Venue Access Guide

[0207] For virtual events, the server provides information on how to access the online event venue and the necessary procedures, allowing users to easily access the virtual venue through their devices and smoothly participate in the event.

[0208] For example, when a user wants to join a virtual event, the server provides an access link and connection instructions to the virtual venue, facilitating the process for the user.

[0209] Prompt Sentence Examples

[0210] "Tell me about the event. The artist you're interested in is 'The Beatles.'"

[0211] As described above, the present invention provides a system that comprehensively supports all procedures related to event participation and places little burden on users.

[0212] The flow of the specific processing in the application example 1 will be described with reference to FIG.

[0213] Step 1:

[0214] The server collects event data from external event information sources (official sites, APIs, etc.) and stores it in a database. The input includes the URL of the event information source and authentication information such as an API key. This allows the server to obtain new event information and create a database entry to store it. The output is the stored event information.

[0215] Step 2:

[0216] If a user is interested in events by a specific artist or genre, that information is set on the device. The input includes a prompt about the user's interests, such as "Tell me about the event. The artist I'm interested in is The Beatles." The device then saves the user's settings. The output is the user's interest information.

[0217] Step 3:

[0218] The server filters the collected event information based on the user's preferences. The input includes the user's preference settings and the event information in the database. The server then selects the relevant event information and sends it to the terminal. The output is the filtered event information.

[0219] Step 4:

[0220] The device notifies the user of the event information received from the server via push notification or email. The input includes filtered event information. This allows the device to notify the user of events of interest in real time. The output is a notification to the user.

[0221] Step 5:

[0222] The server collects event ticket information (release date, purchase method, difficulty of obtaining tickets, etc.) and stores it in a database. The input includes event information and related ticket sales information, which allows the server to provide detailed ticket information. The output is the stored ticket information.

[0223] Step 6:

[0224] When a user views ticket information for an event, the device retrieves the relevant information from the server and displays it on the user interface. The input includes the ID and keywords of the event that the user is interested in. This allows the device to provide detailed ticket information to the user. The output is the ticket information displayed on the screen.

[0225] Step 7:

[0226] The server collects access and accommodation information for the event location or virtual event venue and stores it in a database. Inputs include the location of the event venue and the URL of the virtual room, which enables the server to provide access and accommodation information to users. Outputs include the stored access and accommodation information.

[0227] Step 8:

[0228] When a user searches for transportation or accommodation information, the device retrieves the best options from the server and displays them in the user interface. The input includes the user's search query, which enables the device to provide the best transportation and accommodation information. The output is the recommended transportation and accommodation options for the user.

[0229] Step 9:

[0230] Users register their travel and event schedules in the schedule planner. The input includes details such as the event time, location, transportation, and arrival time. The device then saves and manages the user's schedule. The output is the registered schedule information.

[0231] Step 10:

[0232] The server analyzes the user's schedule, calculates the optimal action plan, and sends it to the terminal. The input includes the user's schedule information and event information. The server calculates the optimal action plan and presents it to the user. The output is the calculated action plan.

[0233] Step 11:

[0234] The server provides an online community where users can interact with each other and allows access to its functionality through the device. Input includes user posts and comments. The server then stores the posts in a database for other users to view. Output is the stored posts.

[0235] Step 12:

[0236] In the case of a virtual event, the server provides the user with access instructions and procedures to the virtual venue and guides them through the terminal. The input includes access information for the virtual venue, which allows the server to smoothly participate in the virtual event. The output is the provided access information.

[0237] Furthermore, an emotion engine that estimates the user's emotion may be combined. That is, the identification processing unit 290 may estimate the user's emotion using the emotion identification model 59 and perform identification processing using the user's emotion.

[0238] The system of the present invention provides a series of support functions for users to participate in events. Specifically, it includes functions for collecting event information, notifications, ticket guides, providing transportation and accommodation information, schedule planners, and community functions. It also incorporates an emotion engine that recognizes the user's emotions and provides optimal services according to their emotional state. The operation of this system is explained based on the following main steps.

[0239] Event information collection and notification

[0240] The server collects event data from external event information sources (official sites, APIs, etc.) and stores it in a database. Based on the user's preferences, the server filters the relevant event information and sends the results to the device. The device notifies the user of the information via push notification or email according to the user's settings.

[0241] Furthermore, the emotion engine analyzes the user's current emotional state and delivers notifications with appropriate timing and content. For example, if the user is feeling stressed, notifications of events that will help them relax will be prioritized.

[0242] Example: If a user specifies that they want to see events by a specific artist, the server will automatically notify the user when new event information for that artist is added. If the emotion engine determines that the user's emotional state is "excited," the notification content will be bright and positive.

[0243] Providing ticket guides

[0244] The server stores the ticket sales schedule and purchase method in a database based on the collected event information. When a user views ticket information, the device retrieves the relevant information from the server and displays it on the user interface. The server also evaluates the difficulty of obtaining tickets and sends feedback to the device. The emotion engine adjusts messages to encourage purchases based on the user's emotions.

[0245] Example: When a user checks ticket information on an event's details page, the device displays information from the server about the release date, how to purchase, and the difficulty of obtaining tickets. The emotion engine determines the user's emotion as "curiosity" and displays an active message encouraging them to purchase.

[0246] Providing transportation and accommodation information and reservation support

[0247] The server collects information on transportation to the event venue and accommodation options around the venue and stores it in a database. When a user needs transportation or accommodation information, the device retrieves the optimal transportation and accommodation options from the server and displays them on the user interface. In addition, the device provides reservation support, allowing users to complete reservations directly. The emotion engine suggests the optimal plan based on the user's emotional state.

[0248] Example: When a user searches for transportation to attend an event, the device retrieves and displays information on the most suitable train or bus from the server. At the same time, it also displays information on nearby accommodations and provides a reservation link if necessary. If the emotion engine determines that the user is feeling "fatigue," it will prioritize suggestions for comfortable accommodations.

[0249] Schedule planner function

[0250] Users register their travel itineraries and event schedules in the schedule planner. The device sends this information to the server, which stores it in a database and analyzes it. Based on the analysis results, the server calculates an optimal action plan and sends it to the device. The device presents it to the user and helps them participate in events based on that action plan. The emotion engine takes into account the user's past emotional data and suggests the most satisfying plan.

[0251] Example: When a user registers their transportation method and arrival time for the day of an event in their schedule planner, the server analyzes this and suggests which transportation method to use at which time. If the emotion engine determines that the user's past emotional data indicates "excessive tension," it will recommend a less stressful transportation method.

[0252] Community Features

[0253] The server provides an online community function that allows users to interact with each other. Users can access the community page through their devices and post or comment on the message board. The server stores these posts in a database and makes them available for other users to view. The emotion engine analyzes interactions within the community and prioritizes displaying content that has a positive impact on users' emotions.

[0254] Example: When a user asks for recommendations on restaurants near the venue on a community message board just before an event, other users reply and share that information. The emotion engine performs sentiment analysis and prioritizes positive posts and encouraging content.

[0255] As described above, the system according to the present invention provides optimal support according to the user's emotional state by incorporating an emotion engine in addition to conventional functions, thereby enabling the user to participate in events in a more comfortable and satisfying way.

[0256] The processing flow will be explained below.

[0257] Step 1:

[0258] The user enters information into the new registration form. The user enters their name, email address, password, etc. on the device and presses the registration button.

[0259] Step 2:

[0260] The device sends registration information to the server. The front end sends a POST request to the backend API, sending user information to the server.

[0261] Step 3:

[0262] The server saves the user information in the database. The server receives the user information, validates it (checks for format and duplication), and saves it in the database. After saving, a confirmation email is sent to the user.

[0263] Step 4:

[0264] The user receives a confirmation email and activates the account. The user opens the confirmation email and clicks the link to activate the account.

[0265] Step 5:

[0266] The server confirms the account activation. The server receives the link click, updates the account status in the database to activated, and notifies the user that activation is complete.

[0267] Step 6:

[0268] A user opens the event listing page. A user opens the event listing page on their device.

[0269] Step 7:

[0270] The device requests the latest event information from the server. The front end sends a GET request to the back end API to obtain the latest event information.

[0271] Step 8:

[0272] The server retrieves event information from the database. The server searches for the necessary event information from the database and returns it in JSON format.

[0273] Step 9:

[0274] The terminal displays the event information. The front end parses the received JSON data and displays the event information in the user interface.

[0275] Step 10:

[0276] Users can set notification preferences. Users can turn on notification preferences for specific idols and events.

[0277] Step 11:

[0278] The device sends the notification settings to the server. The front end sends a PUT request to the backend API to update the notification settings.

[0279] Step 12:

[0280] The server saves the notification settings in the database. The server saves the notification settings it receives in the database.

[0281] Step 13:

[0282] The server continues to collect event information and updates it in real time, adding newly acquired event information to the database.

[0283] Step 14:

[0284] User selects a specific event and opens the details page. User visits the event details page on their device to view more information.

[0285] Step 15:

[0286] The terminal requests ticket information from the server. The front end sends a GET request to the backend API to obtain the ticket information.

[0287] Step 16:

[0288] The server retrieves ticket information from the database. The server searches the database for ticket information based on the event ID and returns it in JSON format.

[0289] Step 17:

[0290] The terminal displays the ticket information. The front-end parses the received JSON data and displays the ticket information on the page.

[0291] Step 18:

[0292] The user purchases a ticket. The user presses the ticket purchase button to begin the purchase process.

[0293] Step 19:

[0294] The terminal sends a purchase request to the server. The front end sends a POST request to the backend API to complete the purchase.

[0295] Step 20:

[0296] The server sends a request to the payment service. The server sends a request to an external payment service to process the payment.

[0297] Step 21:

[0298] The server receives the payment result and updates the database. If the payment is successful, the server saves the purchase data in the database and sends a confirmation email to the user.

[0299] Step 22:

[0300] The user plans their trip, using the in-app schedule planner to select transportation and accommodations.

[0301] Step 23:

[0302] The terminal sends the schedule information to the server. The front end sends a POST request to the backend API to send the schedule information to the server.

[0303] Step 24:

[0304] The server calculates the optimal itinerary and saves it in the database.The server calculates the optimal itinerary based on the schedule information and saves it in the database.

[0305] Step 25:

[0306] The device collects the user's emotional data. When the user uses the app, the device analyzes the user's facial expressions and input content to obtain emotional data.

[0307] Step 26:

[0308] The device sends emotion data to the server, which then sends a POST request to the backend API to receive the emotion data.

[0309] Step 27:

[0310] The server stores the emotional data in a database and analyzes it. The server then uses an emotion engine to analyze the user's emotional state.

[0311] Step 28:

[0312] The server recommends the most appropriate event information based on the emotional state, and based on the analysis results, filters the event information appropriate to the emotional state and sends it to the device.

[0313] Step 29:

[0314] The terminal displays event information based on emotions. The front-end analyzes the event information received from the server and displays it on the user interface.

[0315] Step 30:

[0316] A user opens the community page. A user accesses the community page on their device and browses the message board.

[0317] Step 31:

[0318] The terminal requests bulletin board information from the server. The front end sends a GET request to the back end API to retrieve the bulletin board information.

[0319] Step 32:

[0320] The server retrieves bulletin board information from the database. The server searches the bulletin board information from the database and returns it in JSON format.

[0321] Step 33:

[0322] The terminal displays the message board information. The front end parses the received JSON data and displays the message board information on the page.

[0323] Step 34:

[0324] A user posts: A user creates a new post on the message board and presses the send button.

[0325] Step 35:

[0326] The device sends the post content to the server. The front end sends a POST request to the backend API, sending the new post to the server.

[0327] Step 36:

[0328] The server saves the posted content in a database. The server saves the posted content received in a database and updates the bulletin board information.

[0329] Step 37:

[0330] The server analyzes interactions within the community and selects content that will have a positive impact on users. The emotion engine analyzes the message board content and prioritizes positive posts to display to users.

[0331] Step 38:

[0332] The terminal displays the analysis results of the emotion engine. Based on the analysis results received by the front end, positive posts are displayed preferentially on the message board.

[0333] Example 2

[0334] Next, a description will be given of Example 2. In the following description, the data processing device 12 will be referred to as a "server" and the smart device 14 will be referred to as a "terminal."

[0335] Conventional event participation support systems often handle each function separately: information collection and notification, ticket purchase, transportation and accommodation information, schedule planning, and community functions. As a result, they do not provide optimal services based on the user's emotional state, making it difficult to improve user satisfaction. Another issue is that they do not provide sufficient support to reduce the stress and hassle of participating in events.

[0336] The specific processing by the specific processing unit 290 of the data processing device 12 in the second embodiment is realized by the following means.

[0337] In this invention, the server includes means for collecting information on events across the country and notifying users according to their preferences, means for providing and rating ticket sales schedules and purchasing methods, means for providing information on transportation to event locations and accommodations around the venues and supporting reservations, means for proposing an action plan based on the user's itinerary and event schedule, means for providing a community function that allows users with the same goals to interact with each other, and means for analyzing the user's emotional state using an emotion engine and providing optimal services. This allows users to receive consistent and optimal support for participating in events, and also allows them to receive detailed support tailored to their emotional state.

[0338] "National event information" refers to information about events in all regions and genres, not limited to a specific region or genre.

[0339] "User preferences" refers to the user's interests and concerns that are inferred based on the events the user has previously selected and the genres in which the user has expressed interest.

[0340] "Notification" refers to a message, such as a push notification or email, sent to a user to convey specific information.

[0341] "Ticket sales schedule" refers to information regarding the date, time, and period when tickets for a particular event will go on sale.

[0342] "How to Buy" refers to information regarding the procedures and means for purchasing tickets to a particular event.

[0343] "Event Location" means the location where a particular Event takes place.

[0344] "Transportation" means any means of travel, such as train, bus, or plane, used to travel to the Event location.

[0345] "Accommodation Information" refers to information about hotels and accommodations around the event location.

[0346] "Supporting booking" means helping users smoothly book transportation and accommodation.

[0347] "Itinerary" refers to the series of travel, accommodation, and event participation plans that a User makes to attend an Event.

[0348] An "action plan" refers to suggestions regarding the optimal schedule and route for users to efficiently participate in an event.

[0349] "Users with the same purpose" refers to multiple users who share the same events or interests.

[0350] "Community function" refers to a function that allows users to exchange information and opinions online.

[0351] An "emotion engine" refers to algorithms and technologies that analyze a user's emotional state and provide optimal information and services based on the results.

[0352] The system according to the present invention provides a series of support functions for users to participate in an event. This system is realized by using the following various server functions, terminal functions, and user interfaces.

[0353] Event information collection and notification

[0354] The server collects event data from external event information sources (official sites, APIs, etc.). Specifically, it obtains the latest event information using, for example, web crawling technology or API integration. The collected data is then stored in a database such as MySQL or MongoDB. The server filters relevant event information based on the user's profile information and past participation history and sends it to the device. The device then provides the information to the user via push notifications or email notifications. The emotion engine analyzes the user's current emotional state and notifies them with the appropriate timing and content.

[0355] Example: If a user sets their preference for events by a specific artist, the server will collect new event information for that artist and send notifications to the user. For example, if the emotion engine determines that the user's emotional state is "excited," the notification content will be arranged to be bright and positive.

[0356] Providing ticket guides

[0357] The server stores the ticket sales schedule and purchase procedures in a database based on the collected event information. When a user views ticket information, the device retrieves the relevant ticket information from the server and displays it on the UI. The server also evaluates the difficulty of obtaining tickets and sends feedback to the device. The emotion engine adjusts messages encouraging purchases based on the user's emotional state.

[0358] Example: When a user checks ticket information on an event's details page, the device displays information from the server about the release date, how to purchase, and the difficulty of obtaining tickets. The emotion engine determines the user's emotion as "curiosity" and displays an active message encouraging them to purchase.

[0359] Providing transportation and accommodation information and reservation support

[0360] The server collects information on transportation to the event venue and accommodations near the venue and stores it in a database. When a user needs transportation or accommodation information, the device retrieves the optimal transportation and accommodation options from the server and displays them on the UI. In addition, the device provides reservation support, allowing users to complete reservations directly. The emotion engine suggests the optimal plan based on the user's emotional state.

[0361] Example: When a user searches for transportation to attend an event, the device retrieves and displays the most suitable train or bus information from the server. It also simultaneously displays information about accommodations and provides a link to make reservations. If the emotion engine determines that the user is feeling "fatigue," it will prioritize suggestions for comfortable accommodations.

[0362] Schedule planner function

[0363] Users register their travel itineraries and event schedules in the schedule planner. The device sends this information to the server, which stores it in a database and analyzes it. Based on the analysis results, the server calculates the optimal action plan and sends it to the device. The device then presents this action plan to the user and supports their event participation. The emotion engine takes into account the user's past emotional data and suggests the most satisfying plan.

[0364] Example: When a user registers their transportation method and arrival time for the day of an event in their schedule planner, the server analyzes this and suggests which transportation method to use at which time. If the emotion engine determines that the user's past emotional data indicates "excessive tension," it will recommend a less stressful transportation method.

[0365] Community Features

[0366] The server provides an online community function that allows users to interact with each other. Users can access the community page through their devices and post or comment on the message board. The server stores these posts in a database and makes them available for other users to view. The emotion engine analyzes interactions within the community and prioritizes displaying content that has a positive impact on users' emotions.

[0367] Example: When a user asks for recommendations on restaurants near the venue on a community bulletin board just before an event, other users reply and share that information. The emotion engine performs sentiment analysis and prioritizes positive posts and encouraging content.

[0368] The system of the present invention integrates various functions in this way and provides services that take into consideration the user's emotional state, thereby supporting users in participating in events in a comfortable manner.

[0369] The flow of the identification process in the second embodiment will be described with reference to FIG.

[0370] Event information collection and notification

[0371] Step 1:

[0372] The server collects data from external event information sources (official sites, APIs, etc.). It uses web crawling technology and API requests to efficiently obtain large amounts of data. The input requires the URL and API key of the event information source, and the output is the raw event information.

[0373] Step 2:

[0374] The server formats the collected event information data and stores it in a database such as MySQL or MongoDB. The input is raw event information data, and the output is formatted database entries.

[0375] Step 3:

[0376] The server filters the event information suitable for the user based on the user's profile information and past event participation history. The input is the user's profile information and the event information in the database, and the output is the filtered event information.

[0377] Step 4:

[0378] The server sends filtered event information to the terminal in real time. Here, data can be sent quickly using WebSocket, etc. The input is the filtered event information, and the output is a notification to the terminal that data transmission has been completed.

[0379] Step 5:

[0380] The device notifies the user of the information via push notification or email according to the user's settings. The input is the event information sent from the server, and the output is the notification message sent to the user.

[0381] Providing ticket guides

[0382] Step 1:

[0383] The server collects ticket release dates and purchasing procedures for events and stores them in a database. The input is the URL of the ticket information source, the API key, and the collected ticket information, and the output is the entries stored in the database.

[0384] Step 2:

[0385] A user visits an event details page and requests ticket information. The input is the user's request, and the output is a request sent to the server.

[0386] Step 3:

[0387] The server searches the database for the relevant ticket information and sends it to the terminal. The input is the user's request and the ticket information in the database, and the output is the data sent to the terminal.

[0388] Step 4:

[0389] The terminal displays the ticket information obtained from the server on the user interface (UI). The input is the ticket information sent from the server, and the output is the ticket information displayed on the UI.

[0390] Providing transportation and accommodation information and reservation support

[0391] Step 1:

[0392] The server collects transportation information to the event location and accommodation information around the venue and stores it in a database. The inputs are the sources of the transportation and accommodation information and the collected data, and the output is the entries stored in the database.

[0393] Step 2:

[0394] A user requests transportation and accommodation information. The input is the user request and the output is the submission of the request to the server.

[0395] Step 3:

[0396] The server searches the database for the best transportation and accommodation information and sends it to the terminal. The input is the user's request and the transportation and accommodation information in the database, and the output is the data transmission to the terminal.

[0397] Step 4:

[0398] The information acquired by the device is displayed on the UI, providing reservation support functions. The input is transportation and accommodation information sent from the server, and the output is the information displayed on the UI and a reservation link.

[0399] Schedule planner function

[0400] Step 1:

[0401] A user registers his / her travel itinerary or event schedule in the schedule planner. The input is the itinerary or schedule information entered by the user, and the output is the data sent to the server.

[0402] Step 2:

[0403] The terminal sends the input schedule information to the server. The input is the user's schedule information, and the output is data transmission to the server.

[0404] Step 3:

[0405] The server analyzes the data and calculates the optimal action plan. The input is schedule information and past data, and the output is the action plan as a result of the analysis.

[0406] Step 4:

[0407] The server sends the calculation results to the terminal. The input is the action plan, and the output is the data transmission to the terminal.

[0408] Step 5:

[0409] The terminal presents the action plan to the user. The input is the action plan sent from the server, and the output is the action plan displayed in the UI.

[0410] Community Features

[0411] Step 1:

[0412] The server provides online community functionality, where the input is information for building a community page, and the output is a user-accessible community page.

[0413] Step 2:

[0414] A user accesses a community page and posts or comments. The input is the content of the user's post or comment, and the output is data sent to the server.

[0415] Step 3:

[0416] The server stores the posts in a database. The input is the user's post or comment, and the output is the entry stored in the database.

[0417] Step 4:

[0418] The server makes the posts available for viewing by other users. The input is the saved posts, and the output is the data provided in a viewable form.

[0419] In this way, the system of the present invention comprehensively supports users' participation in events and integrates various functions to provide detailed support according to the user's emotional state.

[0420] (Application example 2)

[0421] Next, a description will be given of Application Example 2. In the following description, the data processing device 12 will be referred to as a "server" and the smart device 14 will be referred to as a "terminal."

[0422] Today's event participants and shoppers demand quick access to a wide variety of information and services. However, with so many information sources and services scattered across multiple platforms, it is difficult for users to obtain a consistent, optimal experience. Furthermore, there is a risk of stress increasing as information is not provided in a way that responds to users' emotions or individual needs. This often leads to dissatisfaction with the event participation or shopping experience.

[0423] The specific processing by the specific processing unit 290 of the data processing device 12 in the application example 2 is realized by the following means.

[0424] In this invention, the server includes means for collecting information on events across the country and notifying users based on their preferences, means for providing and rating ticket sales schedules and purchasing methods, means for providing information on transportation to event locations and accommodations around the venues and supporting reservations, means for proposing an action plan based on the user's itinerary and event schedule, means for providing a community function that allows users with similar goals to interact with each other, means for analyzing the user's emotional state and, based on that, suggesting optimal products and notifying users of promotions, and means for providing navigation within physical stores. This allows users to have a consistently comfortable and satisfying event participation and shopping experience.

[0425] "National event information" refers to data on all events held within the country.

[0426] "Preference-based notification" means a mechanism for selecting and notifying users of relevant event information based on their preferences and interests.

[0427] "Means for providing and rating ticket release schedules and purchasing methods" refers to a system that provides users with information about the release dates and purchasing methods for event tickets, as well as rating information for those tickets.

[0428] "Means of providing information on transportation and accommodation facilities around the venue and supporting reservations" refers to a function that provides information on access to the event venue and information on nearby accommodation facilities and supports reservations for these.

[0429] "A means for proposing an action plan based on the user's itinerary and event schedule" refers to a system that formulates and proposes an optimal action plan based on the user's specified itinerary and the schedule of events they plan to attend.

[0430] "Means for providing community functions" refers to a mechanism for providing functions that allow users with the same goals to interact online.

[0431] "A means of analyzing the user's emotional state and providing optimal product suggestions and promotional notifications based on that" refers to a mechanism that analyzes the user's current emotions and provides appropriate product and promotional information based on the results.

[0432] "A means for providing navigation within a physical store" refers to a system that provides guidance to users to quickly reach a specific location within a physical store.

[0433] The system of the present invention provides a series of support functions to enable users to participate in events and enjoy shopping comfortably and efficiently. This system is composed of a server, a terminal, and an emotion engine. The specific operation of the system and its details are explained below.

[0434] 1. Event information collection and notification

[0435] The server collects event data from external event information sources (official sites, APIs, etc.) and stores it in a database. Based on the user's preferences, the server filters out relevant event information and sends the results to the device. The device then notifies the user of the information via push notification or email according to the user's settings. In addition, the emotion engine analyzes the user's current emotional state and notifies them with appropriate timing and content.

[0436] Example: If a user sets up event information for their favorite artist, the server will automatically send a notification when new event information for that artist is added. If the emotion engine determines that the user's emotional state is "excited," the notification content will be positive.

[0437] 2. Providing ticket guides

[0438] The server stores the ticket sales schedule and purchase method in a database based on the collected event information. When a user views ticket information, the device retrieves the relevant information from the server and displays it on the user interface. The server also evaluates the difficulty of obtaining tickets and provides feedback to the device. The emotion engine adjusts messages to encourage purchases based on the user's emotions.

[0439] Example: When a user checks ticket information on an event's details page, the device displays information from the server, such as the release date, how to purchase, and the difficulty of obtaining tickets. The emotion engine determines the user's emotion as "curiosity" and sends an active message to encourage the purchase.

[0440] 3. Providing transportation and accommodation information and reservation support

[0441] The server collects information on transportation to the event venue and accommodations in the vicinity of the venue and stores it in a database. When a user needs transportation or accommodation information, the device retrieves the optimal options from the server and displays them on the user interface. The device also provides reservation support, allowing users to complete reservations directly. The emotion engine suggests the optimal plan based on the user's emotional state.

[0442] Example: When a user searches for transportation to attend an event, the device retrieves and displays the optimal train and bus information from the server. At the same time, it also displays information about nearby accommodations and provides a reservation link if necessary. If the emotion engine determines that the user is feeling "fatigue," it will prioritize suggestions for comfortable accommodations.

[0443] 4. Schedule planner function

[0444] Users register their travel itinerary and event schedule in the schedule planner. The device sends this to the server, which stores the data in a database and analyzes it. Based on the analysis results, the server calculates an optimal action plan and sends it to the device. The device presents it to the user and helps them participate in events based on that action plan. The emotion engine takes past emotion data into consideration and suggests the most satisfying plan.

[0445] Example: When a user registers their transportation method and arrival time on the day of an event, the server analyzes the information and suggests which transportation method to use and when. If the emotion engine determines that the user's past emotions are "excessive tension," it will recommend a less stressful transportation method.

[0446] 5. Community Features

[0447] The server provides an online community function that allows users to interact with each other. Users can access the community page through their devices and post or comment on the message board. The server stores these posts in a database and makes them available for other users to view. The emotion engine analyzes interactions within the community and prioritizes the display of content that has a positive impact on users' emotions.

[0448] Example: When a user asks for recommendations on restaurants near the venue on a community bulletin board just before an event, other users reply and share the information. The emotion engine performs sentiment analysis and prioritizes positive posts and encouraging content.

[0449] 6. In-store navigation

[0450] The device provides navigation functions to help users quickly find specific products or locations within physical stores, and an emotion engine calculates the optimal route based on the user's emotional state.

[0451] Example: If a user wants to find a specific product quickly, the device will show the shortest route. If the emotion engine determines that the user is feeling "relaxed," the device will guide the user to a scenic route.

[0452] 7. Emotion-based product recommendations and promotions

[0453] The emotion engine analyzes the user's emotional state in real time and suggests optimal products and promotions, which the device notifies the user of, increasing their desire to purchase.

[0454] Example: If a user types "I feel tired today," generate a prompt that prioritizes relaxation products (aromatherapy candles and herbal tea).

[0455] Prompt sentences for AI model generating concrete examples

[0456] "If a user types, 'I feel tired today,' the system should interpret that emotion as 'relaxation' and generate prompts that prioritize relaxation products like scented candles and herbal teas."

[0457] The flow of the specific processing in the application example 2 will be described with reference to FIG.

[0458] Step 1:

[0459] The server collects event data from external event information sources (official sites, APIs, etc.) and stores it in a database. At this time, the server also stores filtering information based on the user's preferences in the database. Event data from external information sources is input, and filtered event data is output and stored in the database. The server also obtains the user's current emotional state from the emotion engine to optimize the timing and content of notifications.

[0460] Step 2:

[0461] When a user uses a device to view event information, the device retrieves the relevant event information from the server and displays it on the user interface. The input is the user's viewing request, and the output is the displayed event information. Furthermore, the emotion engine analyzes the user's current emotional state and adjusts the notification content accordingly. For example, if the user is determined to be "excited," the notification content is adjusted to be more positive.

[0462] Step 3:

[0463] When a user views ticket information, the device retrieves the release schedule, purchase method, and ticket acquisition difficulty from the server and displays these on the user interface. The input is a ticket information request, and the output is detailed ticket information. The emotion engine also analyzes the user's emotions and adjusts messages to encourage purchases. For example, if the user is determined to be "curious," an active message will be displayed to encourage purchase.

[0464] Step 4:

[0465] When a user searches for information on transportation or accommodation, the device retrieves the optimal transportation and accommodation options from the server and displays them on the user interface. The input is a request for transportation or accommodation information, and the output is the display of the optimal options. In addition, an emotion engine analyzes the user's emotional state and suggests optimal plans, such as comfortable accommodation. For example, if the user is determined to be "fatigued," it will prioritize suggestions for comfortable accommodation.

[0466] Step 5:

[0467] When a user registers an itinerary or event schedule in the schedule planner, the device sends it to the server, which then calculates an optimal action plan and sends it to the device. The input is the itinerary or event schedule data, and the output is an optimal action plan. The emotion engine also takes into account past emotion data and suggests plans that will result in high satisfaction. For example, if the user is judged to be "excessively nervous," it will recommend a less stressful mode of transportation.

[0468] Step 6:

[0469] The server provides an online community function that allows users to interact with each other. Users can access the community page via their devices and post or comment. The input is the user's message board posting data, and the output is saved in a form that can be viewed by other users. The emotion engine performs emotion analysis and prioritizes the display of posts that have a positive impact. For example, if a user is judged to be "positive," encouraging posts will be displayed to the front.

[0470] Step 7:

[0471] The device provides navigation functions to help users quickly find specific products or locations within a physical store. The input is the user's destination request, and the output is navigation information to the destination. The emotion engine suggests the optimal route based on the user's emotional state. For example, if the user is judged to be "relaxed," the device will guide them to a scenic route.

[0472] Step 8:

[0473] The emotion engine analyzes the user's emotional state in real time and suggests the most suitable products and promotions. The device notifies the user of this, encouraging them to purchase. The input is the user's emotional data and product information, and the output is product suggestions and promotion information tailored to the emotion. In concrete terms, if the user inputs "I feel tired today," relaxation products will be suggested first.

[0474] Prompt sentences for AI model generating concrete examples

[0475] If the user types "I feel tired today," the system should interpret that emotion as "relaxation" and generate prompts that prioritize relaxation products like scented candles and herbal tea.

[0476] The specific processing unit 290 transmits the result of the specific processing to the smart device 14. In the smart device 14, the control unit 46A causes the output device 40 to output the result of the specific processing. The microphone 38B acquires audio indicating a user input regarding the result of the specific processing. The control unit 46A transmits audio data indicating the user input acquired by the microphone 38B to the data processing device 12. In the data processing device 12, the specific processing unit 290 acquires the audio data.

[0477] The data generation model 58 is a so-called generative AI (Artificial Intelligence). An example of the data generation model 58 is ChatGPT (Internet Search<URL: https: / / openai.com / blog / chatgpt> ), Gemini (Internet search <url: https: gemini.google.com ?hl="ja">) and other generation AIs. The data generation model 58 is obtained by performing deep learning on a neural network. A prompt including an instruction is input to the data generation model 58, and inference data such as voice data indicating voice, text data indicating text, and image data indicating an image is also input. The data generation model 58 performs inference on the input inference data in accordance with the instruction indicated by the prompt, and outputs the inference result in a data format such as voice data and text data. Here, inference refers to, for example, analysis, classification, prediction, and / or summarization.

[0478] In the above embodiment, an example in which the specific process is performed by the data processing device 12 has been given, but the technology of the present disclosure is not limited to this, and the specific process may be performed by the smart device 14.

[0479] [Second embodiment]

[0480] FIG. 3 shows an example of the configuration of a data processing system 210 according to the second embodiment.

[0481] 3, the data processing system 210 includes the data processing device 12 and smart glasses 214. An example of the data processing device 12 is a server.

[0482] The data processing device 12 includes a computer 22, a database 24, and a communication I / F 26. The computer 22 is an example of a "computer" according to the technology of the present disclosure. The computer 22 includes a processor 28, a RAM 30, and a storage 32. The processor 28, the RAM 30, and the storage 32 are connected to a bus 34. The database 24 and the communication I / F 26 are also connected to the bus 34. The communication I / F 26 is connected to a network 54. Examples of the network 54 include a WAN (Wide Area Network) and / or a LAN (Local Area Network).

[0483] The smart glasses 214 include a computer 36, a microphone 238, a speaker 240, a camera 42, and a communication I / F 44. The computer 36 includes a processor 46, a RAM 48, and a storage 50. The processor 46, the RAM 48, and the storage 50 are connected to a bus 52. The microphone 238, the speaker 240, and the camera 42 are also connected to the bus 52.

[0484] The microphone 238 receives instructions and the like from the user 20 by receiving voice uttered by the user 20. The microphone 238 captures the voice uttered by the user 20, converts the captured voice into audio data, and outputs it to the processor 46. The speaker 240 outputs audio in accordance with instructions from the processor 46.

[0485] Camera 42 is a small digital camera equipped with an optical system including a lens, aperture, and shutter, and an imaging element such as a CMOS (Complementary Metal-Oxide-Semiconductor) image sensor or a CCD (Charge Coupled Device) image sensor, and captures images of the surroundings of user 20 (for example, an imaging range defined by an angle of view equivalent to the field of vision of a typical healthy person).

[0486] The communication I / F 44 is connected to a network 54. The communication I / Fs 44 and 26 are responsible for the exchange of various information between the processor 46 and the processor 28 via the network 54. The exchange of various information between the processor 46 and the processor 28 using the communication I / Fs 44 and 26 is carried out in a secure state.

[0487] Fig. 4 shows an example of the main functions of the data processing device 12 and the smart glasses 214. As shown in Fig. 4, in the data processing device 12, a specific process is performed by the processor 28. A specific process program 56 is stored in the storage 32.

[0488] The specific processing program 56 is an example of a "program" according to the technology of the present disclosure. The processor 28 reads the specific processing program 56 from the storage 32 and executes the read specific processing program 56 on the RAM 30. The specific processing is realized by the processor 28 operating as a specific processing unit 290 in accordance with the specific processing program 56 executed on the RAM 30.

[0489] The storage 32 stores a data generation model 58 and an emotion identification model 59. The data generation model 58 and the emotion identification model 59 are used by the identification processing unit 290.

[0490] In the smart glasses 214, the reception output process is performed by the processor 46. A reception output program 60 is stored in the storage 50. The processor 46 reads the reception output program 60 from the storage 50 and executes the read reception output program 60 on the RAM 48. The reception output process is realized by the processor 46 operating as the control unit 46A in accordance with the reception output program 60 executed on the RAM 48.

[0491] Next, a description will be given of the identification process performed by the identification processing unit 290 of the data processing device 12. In the following description, the data processing device 12 will be referred to as the "server" and the smart glasses 214 will be referred to as the "terminal."

[0492] The system of the present invention provides a series of support functions for users to participate in events. Specifically, it includes functions for collecting event information, notifications, ticket guides, providing transportation and accommodation information, schedule planning, and community functions. The operation of this system is explained based on the following main steps.

[0493] Event information collection and notification

[0494] The server collects event data from external event information sources (official sites, APIs, etc.) and stores it in a database. Based on the user's preferences, the server filters the relevant event information and sends the results to the device. The device notifies the user of the information via push notification or email according to the user's settings.

[0495] Example: If a user specifies that they want to see events by a particular artist, the server will automatically notify the user when new events by that artist are added.

[0496] Providing ticket guides

[0497] The server stores the ticket sales schedule and purchase method in a database based on the collected event information. When a user views ticket information, the device retrieves the relevant information from the server and displays it on the user interface. In addition, the server evaluates the difficulty of obtaining tickets and sends feedback to the device.

[0498] Example: When a user checks ticket information on an event's details page, the device displays information from the server about the release date, how to purchase, and how easy it is to obtain tickets.

[0499] Providing transportation and accommodation information and reservation support

[0500] The server collects information on transportation to the event venue and accommodation options around the venue and stores it in a database. When a user needs transportation or accommodation information, the terminal retrieves the optimal transportation and accommodation options from the server and displays them on the user interface. In addition, the terminal provides reservation support functions, allowing users to complete reservations directly.

[0501] Example: When a user searches for transportation to an event, the device retrieves and displays the most suitable train and bus information from the server. At the same time, it also displays information about nearby accommodations and provides a reservation link if necessary.

[0502] Schedule planner function

[0503] Users register their travel itineraries and event schedules in the schedule planner. The device sends this information to the server, which stores it in a database and analyzes it. Based on the analysis results, the server calculates an optimal action plan and sends it to the device. The device then presents it to the user and helps them participate in events based on that action plan.

[0504] Example: When a user registers the mode of transportation and arrival time for the day of an event in their schedule planner, the server analyzes this and suggests which mode of transportation to use at what time.

[0505] Community Features

[0506] The server provides an online community function that allows users to interact with each other. Users can access the community page through their devices and post or comment on the message board. The server stores these posts in a database and makes them available to other users.

[0507] Example: A user asks on a community message board for recommendations on restaurants near the venue just before an event, and other users reply and share that information.

[0508] As described above, the system of the present invention streamlines the series of procedures required to participate in an event and provides optimal support to users. This system allows users to smoothly complete all processes, including information gathering, ticket purchase, transportation and accommodation arrangements, schedule management, and community participation.

[0509] The processing flow will be explained below.

[0510] Step 1:

[0511] The user enters information into the new registration form. The user enters their name, email address, password, etc. on the device and presses the registration button.

[0512] Step 2:

[0513] The device sends registration information to the server. The front end sends a POST request to the backend API, sending user information to the server.

[0514] Step 3:

[0515] The server saves the user information in the database. The server receives the user information, validates it (checks for format and duplication), and saves it in the database. After saving, a confirmation email is sent to the user.

[0516] Step 4:

[0517] The user receives a confirmation email and activates the account. The user opens the confirmation email and clicks the link to activate the account.

[0518] Step 5:

[0519] The server confirms the account activation. The server receives the link click, updates the account status in the database to activated, and notifies the user that activation is complete.

[0520] Step 6:

[0521] A user opens the event listing page. A user opens the event listing page on their device.

[0522] Step 7:

[0523] The device requests the latest event information from the server. The front end sends a GET request to the back end API to obtain the latest event information.

[0524] Step 8:

[0525] The server retrieves event information from the database. The server searches for the necessary event information from the database and returns it in JSON format.

[0526] Step 9:

[0527] The terminal displays the event information. The front end parses the received JSON data and displays the event information in the user interface.

[0528] Step 10:

[0529] The user sets notification settings. The user turns on notification settings for specific idle times.

[0530] Step 11:

[0531] The device sends the notification settings to the server. The front end sends a PUT request to the backend API to update the notification settings.

[0532] Step 12:

[0533] The server saves the notification settings in the database. The server saves the notification settings it receives in the database.

[0534] Step 13:

[0535] User selects a specific event and opens the details page. User visits the event details page on their device to view more information.

[0536] Step 14:

[0537] The terminal requests ticket information from the server. The front end sends a GET request to the backend API to obtain the ticket information.

[0538] Step 15:

[0539] The server retrieves ticket information from the database. The server searches the database for ticket information based on the event ID and returns it in JSON format.

[0540] Step 16:

[0541] The terminal displays the ticket information. The front-end parses the received JSON data and displays the ticket information on the page.

[0542] Step 17:

[0543] The user purchases a ticket. The user presses the ticket purchase button to begin the purchase process.

[0544] Step 18:

[0545] The terminal sends a purchase request to the server. The front end sends a POST request to the backend API to complete the purchase.

[0546] Step 19:

[0547] The server sends a request to the payment service. The server sends a request to the external payment service to process the payment.

[0548] Step 20:

[0549] The server receives the payment result and updates the database. If the payment is successful, the server saves the purchase data in the database and sends a confirmation email to the user.

[0550] Step 21:

[0551] The user plans their trip, using the in-app schedule planner to select transportation and accommodations.

[0552] Step 22:

[0553] The terminal sends the schedule information to the server. The front end sends a POST request to the backend API to send the schedule information to the server.

[0554] Step 23:

[0555] The server calculates the optimal itinerary and saves it in the database.The server calculates the optimal itinerary based on the schedule information and saves it in the database.

[0556] Step 24:

[0557] A user opens the community page. A user accesses the community page on their device and browses the message board.

[0558] Step 25:

[0559] The terminal requests bulletin board information from the server. The front end sends a GET request to the back end API to retrieve the bulletin board information.

[0560] Step 26:

[0561] The server retrieves bulletin board information from the database. The server searches the bulletin board information from the database and returns it in JSON format.

[0562] Step 27:

[0563] The terminal displays the message board information. The front end parses the received JSON data and displays the message board information on the page.

[0564] Step 28:

[0565] A user posts: A user creates a new post on the message board and presses the send button.

[0566] Step 29:

[0567] The device sends the post content to the server. The front end sends a POST request to the backend API, sending the new post to the server.

[0568] Step 30:

[0569] The server saves the posted content in a database. The server saves the posted content received in a database and updates the bulletin board information.

[0570] Example 1

[0571] Next, a description will be given of Example 1. In the following description, the data processing device 12 will be referred to as a "server" and the smart glasses 214 will be referred to as a "terminal."

[0572] In the past, gathering information, purchasing tickets, and arranging transportation and accommodation to participate in an event required time and effort, placing a burden on users. Furthermore, the management of event information and participation plans was dispersed, making it difficult to participate in events efficiently. Furthermore, opportunities to share information through interactions with other participants were limited.

[0573] The specific processing by the specific processing unit 290 of the data processing device 12 in the first embodiment is realized by the following means.

[0574] In this invention, the server includes: means for collecting event information from across the country and notifying users based on their preferences; means for providing and rating ticket sales schedules and purchasing methods; means for providing information on transportation to event locations and accommodations near the venues and supporting reservations; means for suggesting an action plan based on the user's itinerary and event schedule; means for providing a community function that allows users with similar interests to interact with each other; means for periodically collecting event information from external sources and storing it in a database; means for filtering the information based on the database and notifying users of the most appropriate event information via push notification or email; and means for calculating the difficulty of obtaining tickets and providing the information to users. This allows users to efficiently collect event information and smoothly purchase tickets and make arrangements for transportation and accommodation. Users can also obtain more information by interacting with other participants.

[0575] "National event information" refers to information about events of various genres held throughout the country, not limited to a specific region.

[0576] "Notifying based on user preferences" means selecting and notifying the user of relevant event information based on the user's pre-defined interests and preferences.

[0577] "Providing and evaluating ticket release schedules and purchasing methods" means providing information about when event tickets go on sale and how to purchase them, and based on that information evaluating the difficulty and convenience of obtaining tickets and communicating that information to users.

[0578] Providing "information on transportation to the event venue and accommodations in the vicinity" and supporting reservations means providing information on transportation and accommodations for users to attend the event, and supporting the reservation process.

[0579] "Suggesting an action plan based on the user's itinerary and event schedule" means calculating and suggesting an optimal action plan to the user based on the event dates and transportation details entered by the user.

[0580] "Providing a community function that allows users with the same goals to interact with each other" means providing an online platform where event participants can share information, exchange opinions, and ask questions.

[0581] "Regularly collect from external sources and store in a database" means periodically obtaining event information from reliable external sources such as official websites and APIs and storing it in a database.

[0582] "Filtering based on a database" means sorting stored event information based on user settings and preferences.

[0583] "Notifying users of the most appropriate event information via push notification or email" means notifying users directly of filtered event information in a manner that suits their settings.

[0584] "Calculating the difficulty of obtaining tickets" means assessing the difficulty of obtaining event tickets based on past data and current demand, and providing this to users.

[0585] The system of this invention provides a series of support functions for users to participate in events. Specifically, it provides a comprehensive range of functions, including event information collection, notification, ticket guide, transportation and accommodation information, schedule planner, and community functions. To realize the operation of this system, the server, terminals, and users each play different roles.

[0586] First, the server periodically retrieves event data from external event information sources (such as official event websites or APIs). The collected data is stored in a database containing information such as the event name, date and time, location, and details. For example, a library such as the Apache HTTP client can be used to collect the information.

[0587] When a user logs in to the system and selects the genres and artists they are interested in, the server filters the relevant event information from the database based on the user's preferences. This filtering is done using database queries and stored procedures. The filtered results are sent to the device, which then notifies the user via push notification or email.

[0588] For example, if a user specifies that they want to receive notifications for events by a specific artist, the server will automatically notify the user when new events for that artist are added. An example of a prompt would be, "How do I set up notifications for events by a specific artist?"

[0589] Next, when a user views an event's details page, the device requests ticket information for that event from the server. The server retrieves ticket information (release date, price, purchase method, etc.) from the database and returns it to the device. The server then calculates the difficulty of obtaining tickets using past sales data and a demand forecasting algorithm, and sends feedback to the device.

[0590] For example, when a user checks ticket information on an event's details page, the device displays information from the server about the release date, how to purchase, and the difficulty of obtaining tickets. An example of a prompt sentence is, "Please tell me how to rate the difficulty of obtaining tickets for an event."

[0591] The server also retrieves information about transportation options to the event location (trains, buses, taxis, etc.) and accommodations near the venue from travel APIs and hotel booking site APIs, and stores this information in a database. When a user needs this information, the device retrieves the optimal options from the server and presents them to the user. Users can then use the reservation support function to complete their reservations directly.

[0592] For example, when a user searches for transportation, the device retrieves and displays the best transportation options from the server. Similarly, it displays accommodation information and provides a booking link if necessary. An example of a prompt is, "How do I search for transportation and accommodation information for an event?"

[0593] With the schedule planner function, users can register their event schedules. The device then sends the schedules to the server, which stores them in a database and analyzes them. Based on the analysis results, the server calculates an optimal action plan and sends it to the device. Users can then act accordingly.

[0594] For example, when a user enters information into a schedule planner, the server suggests which means of transportation to use at which time. An example of a prompt sentence is, "Please tell me how to calculate the optimal itinerary by entering the mode of transportation and arrival time on the day of the event."

[0595] Finally, the server provides an online community function that allows users to interact with each other. Users can access the community page through their devices and post or comment on the message board. The server stores these posts in a database and makes them available to other users.

[0596] For example, if a user asks for information about restaurants near the venue on a community bulletin board just before an event, other users will reply and share that information. An example of a prompt sentence is, "Please tell me how to ask for recommended restaurant information on a community bulletin board just before an event."

[0597] As described above, the system streamlines the entire process for users to participate in events efficiently and provides a wealth of information and support.

[0598] The flow of the identification process in the first embodiment will be described with reference to FIG.

[0599] Step 1: Gather event information

[0600] The server periodically collects event data from external event information sources (e.g., official event websites, APIs, etc.). Specifically, the server sends API requests, parses the returned data in JSON format, and stores it in a database.

[0601] Input: API request from external information source

[0602] Output: Parsed event data stored in a database

[0603] Step 2: Filtering event information

[0604] When a user logs into the system and selects the genres and artists they are interested in, the server uses a database query to filter relevant event information from the database based on the user's preferences.

[0605] Input: User interests and preferences

[0606] Output: Filtered event information

[0607] Step 3: Event information notification

[0608] The filtered event information is sent to the device, and the device notifies the user via push notification or email, depending on the user settings.

[0609] Input: Filtered event information

[0610] Output: Push notification and email notification

[0611] Step 4: Get ticket information

[0612] When a user views an event's details page, the device requests ticket information for that event from the server. The server retrieves ticket information (release date, price, purchase method, etc.) from the database and returns that information to the device.

[0613] Input: Ticket information request from user

[0614] Output: Retrieved ticket information

[0615] Step 5: Calculating ticket difficulty

[0616] The server calculates the difficulty of obtaining tickets using past sales data and demand forecasting algorithms, and provides this information to users via their devices.

[0617] Input: Past sales data, demand data

[0618] Output: Ticket acquisition difficulty rating

[0619] Step 6: Providing transportation and accommodation information

[0620] When a user searches for transportation or accommodation information for an event, the device sends a request to the server, which returns the best options to the user based on information retrieved from travel APIs and hotel booking site APIs.

[0621] Input: User request for transportation and accommodation information

[0622] Output: Best transportation and accommodation information

[0623] Step 7: Schedule Planner

[0624] Users register their event participation schedule in the schedule planner. The device sends this to the server, which stores it in a database and analyzes it. The optimal action plan is calculated and provided to the user via the device.

[0625] Input: User's schedule information

[0626] Output: Optimal action plan

[0627] Step 8: Community Features

[0628] Users can access the community page through their devices and post or comment on the message board. The server stores these posts in a database and makes them available to other users.

[0629] Input: User posts and comments

[0630] Output: Saved posts, comments displayed

[0631] (Application example 1)

[0632] Next, a description will be given of Application Example 1. In the following description, the data processing device 12 will be referred to as a "server" and the smart glasses 214 will be referred to as a "terminal."

[0633] Currently, when users participate in a virtual event, they must use multiple methods, such as gathering event information, purchasing tickets, checking access methods, managing schedules, and interacting with the community, which takes a lot of time and effort.In addition, access guides and real-time event information updates, which are specific to virtual events, are often not provided sufficiently.

[0634] The specific processing by the specific processing unit 290 of the data processing device 12 in the application example 1 is realized by the following means.

[0635] In this invention, the server includes means for collecting information on events across the country and notifying users based on their preferences, means for providing and rating ticket sales schedules and purchasing methods, means for providing access methods to the event location or virtual event venue and information on nearby accommodations and supporting reservations, means for proposing an action plan based on the user's itinerary and event schedule, means for providing a community function that allows users with the same goals to interact with each other, and means for providing a guide to accessing the virtual venue.This significantly reduces the effort and time required for users to participate in virtual events, allowing them to enjoy the event more smoothly.

[0636] "Collecting event information nationwide" means gathering data on various events across the country.

[0637] "Providing notifications based on user preferences" means notifying users of appropriate event information based on the interests and concerns they have set.

[0638] "Providing and evaluating ticket release schedules and purchasing methods" means providing information about the sale period and purchasing methods of event tickets and evaluating the difficulty of obtaining them.

[0639] "How to access the event location or virtual event venue" means directions to the physical location where the event is being held or how to access the online virtual space.

[0640] "Providing information about nearby accommodations and supporting reservations" means providing information about accommodations near the venue and helping people make reservations.

[0641] "Suggesting an action plan based on the user's itinerary and event schedule" means proposing the optimal action plan based on the schedule of events and plans set by the user.

[0642] "Providing a community function that allows users with the same goals to interact with each other" means providing a function that allows users with common interests and goals to exchange opinions and share information.

[0643] "Providing a guide to accessing the virtual venue" means providing instructions and procedures for accessing the virtual space where the event will be held online.

[0644] "Push notifications about specific events and areas of interest based on user preferences" means providing real-time notifications about relevant events and areas of interest based on user-specified preferences.

[0645] The present invention is a system that comprehensively supports users' participation in events, and includes the following configuration and operation.

[0646] Event information collection and notification

[0647] The server collects event data from external event information sources (such as official websites and APIs) and stores it in a database. Based on the user's preferences, the server filters the relevant event information and sends the results to the device. The device then notifies the user of the information via push notifications or emails, depending on the user's settings.

[0648] For example, if a user specifies that they want to see events by a particular artist, the server will collect event information for that artist and automatically send notifications.

[0649] Providing ticket guides

[0650] The server stores the ticket sales schedule and purchase method in a database based on the collected event information. When a user views ticket information, the device retrieves the relevant information from the server and displays it on the user interface. The server also evaluates the difficulty of obtaining tickets and sends the evaluation results to the device.

[0651] For example, when a user checks ticket information on an event's details page, the device displays information from the server about the release date, how to purchase tickets, and how difficult it is to obtain tickets.

[0652] Providing transportation and accommodation information and reservation support

[0653] The server collects information on how to access the event venue or virtual event venue and accommodation information around the venue and stores it in a database. When a user needs transportation or accommodation information, the terminal retrieves the optimal transportation and accommodation options from the server and displays them on the user interface. In addition, the terminal provides reservation support functions, allowing users to complete reservations directly.

[0654] For example, when a user searches for transportation to an event, the device retrieves the optimal transportation and accommodation information from the server and displays it, and also provides a reservation link if necessary.

[0655] Schedule planner function

[0656] Users register their travel itineraries and event schedules in the schedule planner. The device sends this information to the server, which stores it in a database and analyzes it. Based on the analysis results, the server calculates an optimal action plan and sends it to the device. The device then presents it to the user and helps them participate in events based on that action plan.

[0657] As a concrete example, when a user registers the mode of transportation and arrival time for the day of the event in their schedule planner, the server analyzes this and suggests which mode of transportation to use at what time.

[0658] Community Features

[0659] The server provides an online community function that allows users to interact with each other. Users can access the community page through their devices and post or comment on the message board. The server stores these posts in a database and makes them available to other users.

[0660] For example, if a user asks on a community bulletin board for information about recommended restaurants near the venue just before an event, other users will reply and share that information.

[0661] Virtual Venue Access Guide

[0662] For virtual events, the server provides information on how to access the online event venue and the necessary procedures, allowing users to easily access the virtual venue through their devices and smoothly participate in the event.

[0663] For example, when a user wants to join a virtual event, the server provides an access link and connection instructions to the virtual venue, facilitating the process for the user.

[0664] Prompt Sentence Examples

[0665] "Tell me about the event. The artist you're interested in is 'The Beatles.'"

[0666] As described above, the present invention provides a system that comprehensively supports all procedures related to event participation and places little burden on users.

[0667] The flow of the specific processing in the application example 1 will be described with reference to FIG.

[0668] Step 1:

[0669] The server collects event data from external event information sources (official sites, APIs, etc.) and stores it in a database. The input includes the URL of the event information source and authentication information such as an API key. This allows the server to obtain new event information and create a database entry to store it. The output is the stored event information.

[0670] Step 2:

[0671] If a user is interested in events by a specific artist or genre, that information is set on the device. The input includes a prompt about the user's interests, such as "Tell me about the event. The artist I'm interested in is The Beatles." The device then saves the user's settings. The output is the user's interest information.

[0672] Step 3:

[0673] The server filters the collected event information based on the user's preferences. The input includes the user's preference settings and the event information in the database. The server then selects the relevant event information and sends it to the terminal. The output is the filtered event information.

[0674] Step 4:

[0675] The device notifies the user of the event information received from the server via push notification or email. The input includes filtered event information. This allows the device to notify the user of events of interest in real time. The output is a notification to the user.

[0676] Step 5:

[0677] The server collects event ticket information (release date, purchase method, difficulty of obtaining tickets, etc.) and stores it in a database. The input includes event information and related ticket sales information, which allows the server to provide detailed ticket information. The output is the stored ticket information.

[0678] Step 6:

[0679] When a user views ticket information for an event, the device retrieves the relevant information from the server and displays it on the user interface. The input includes the ID and keywords of the event that the user is interested in. This allows the device to provide detailed ticket information to the user. The output is the ticket information displayed on the screen.

[0680] Step 7:

[0681] The server collects access and accommodation information for the event location or virtual event venue and stores it in a database. Inputs include the location of the event venue and the URL of the virtual room, which enables the server to provide access and accommodation information to users. Outputs include the stored access and accommodation information.

[0682] Step 8:

[0683] When a user searches for transportation or accommodation information, the device retrieves the best options from the server and displays them in the user interface. The input includes the user's search query, which enables the device to provide the best transportation and accommodation information. The output is the recommended transportation and accommodation options for the user.

[0684] Step 9:

[0685] Users register their travel and event schedules in the schedule planner. The input includes details such as the event time, location, transportation, and arrival time. The device then saves and manages the user's schedule. The output is the registered schedule information.

[0686] Step 10:

[0687] The server analyzes the user's schedule, calculates the optimal action plan, and sends it to the terminal. The input includes the user's schedule information and event information. The server calculates the optimal action plan and presents it to the user. The output is the calculated action plan.

[0688] Step 11:

[0689] The server provides an online community where users can interact with each other and allows access to its functionality through the device. Input includes user posts and comments. The server then stores the posts in a database for other users to view. Output is the stored posts.

[0690] Step 12:

[0691] In the case of a virtual event, the server provides the user with access instructions and procedures to the virtual venue and guides them through the terminal. The input includes access information for the virtual venue, which allows the server to smoothly participate in the virtual event. The output is the provided access information.

[0692] Furthermore, an emotion engine that estimates the user's emotion may be further combined. That is, the identification processing unit 290 may estimate the user's emotion using the emotion identification model 59, and perform identification processing using the user's emotion.

[0693] The system of the present invention provides a series of support functions for users to participate in events. Specifically, it includes functions for collecting event information, notifications, ticket guides, providing transportation and accommodation information, schedule planners, and community functions. It also incorporates an emotion engine that recognizes the user's emotions and provides optimal services according to their emotional state. The operation of this system is explained based on the following main steps.

[0694] Event information collection and notification

[0695] The server collects event data from external event information sources (official sites, APIs, etc.) and stores it in a database. Based on the user's preferences, the server filters the relevant event information and sends the results to the device. The device notifies the user of the information via push notification or email according to the user's settings.

[0696] Furthermore, the emotion engine analyzes the user's current emotional state and delivers notifications with appropriate timing and content. For example, if the user is feeling stressed, notifications of events that will help them relax will be prioritized.

[0697] Example: If a user specifies that they want to see events by a specific artist, the server will automatically notify the user when new event information for that artist is added. If the emotion engine determines that the user's emotional state is "excited," the notification content will be bright and positive.

[0698] Providing ticket guides

[0699] The server stores the ticket sales schedule and purchase method in a database based on the collected event information. When a user views ticket information, the device retrieves the relevant information from the server and displays it on the user interface. The server also evaluates the difficulty of obtaining tickets and sends feedback to the device. The emotion engine adjusts messages to encourage purchases based on the user's emotions.

[0700] Example: When a user checks ticket information on an event's details page, the device displays information from the server about the release date, how to purchase, and the difficulty of obtaining tickets. The emotion engine determines the user's emotion as "curiosity" and displays an active message encouraging them to purchase.

[0701] Providing transportation and accommodation information and reservation support

[0702] The server collects information on transportation to the event venue and accommodation options around the venue and stores it in a database. When a user needs transportation or accommodation information, the device retrieves the optimal transportation and accommodation options from the server and displays them on the user interface. In addition, the device provides reservation support, allowing users to complete reservations directly. The emotion engine suggests the optimal plan based on the user's emotional state.

[0703] Example: When a user searches for transportation to attend an event, the device retrieves and displays information on the most suitable train or bus from the server. At the same time, it also displays information on nearby accommodations and provides a reservation link if necessary. If the emotion engine determines that the user is feeling "fatigue," it will prioritize suggestions for comfortable accommodations.

[0704] Schedule planner function

[0705] Users register their travel itineraries and event schedules in the schedule planner. The device sends this information to the server, which stores it in a database and analyzes it. Based on the analysis results, the server calculates an optimal action plan and sends it to the device. The device presents it to the user and helps them participate in events based on that action plan. The emotion engine takes into account the user's past emotional data and suggests the most satisfying plan.

[0706] Example: When a user registers their transportation method and arrival time for the day of an event in their schedule planner, the server analyzes this and suggests which transportation method to use at which time. If the emotion engine determines that the user's past emotional data indicates "excessive tension," it will recommend a less stressful transportation method.

[0707] Community Features

[0708] The server provides an online community function that allows users to interact with each other. Users can access the community page through their devices and post or comment on the message board. The server stores these posts in a database and makes them available for other users to view. The emotion engine analyzes interactions within the community and prioritizes displaying content that has a positive impact on users' emotions.

[0709] Example: When a user asks for recommendations on restaurants near the venue on a community message board just before an event, other users reply and share that information. The emotion engine performs sentiment analysis and prioritizes positive posts and encouraging content.

[0710] As described above, the system according to the present invention provides optimal support according to the user's emotional state by incorporating an emotion engine in addition to conventional functions, thereby enabling the user to participate in events in a more comfortable and satisfying way.

[0711] The processing flow will be explained below.

[0712] Step 1:

[0713] The user enters information into the new registration form. The user enters their name, email address, password, etc. on the device and presses the registration button.

[0714] Step 2:

[0715] The device sends registration information to the server. The front end sends a POST request to the backend API, sending user information to the server.

[0716] Step 3:

[0717] The server saves the user information in the database. The server receives the user information, validates it (checks for format and duplication), and saves it in the database. After saving, a confirmation email is sent to the user.

[0718] Step 4:

[0719] The user receives a confirmation email and activates the account. The user opens the confirmation email and clicks the link to activate the account.

[0720] Step 5:

[0721] The server confirms the account activation. The server receives the link click, updates the account status in the database to activated, and notifies the user that activation is complete.

[0722] Step 6:

[0723] A user opens the event listing page. A user opens the event listing page on their device.

[0724] Step 7:

[0725] The device requests the latest event information from the server. The front end sends a GET request to the back end API to obtain the latest event information.

[0726] Step 8:

[0727] The server retrieves event information from the database. The server searches for the necessary event information from the database and returns it in JSON format.

[0728] Step 9:

[0729] The terminal displays the event information. The front end parses the received JSON data and displays the event information in the user interface.

[0730] Step 10:

[0731] Users can set notification preferences. Users can turn on notification preferences for specific idols and events.

[0732] Step 11:

[0733] The device sends the notification settings to the server. The front end sends a PUT request to the backend API to update the notification settings.

[0734] Step 12:

[0735] The server saves the notification settings in the database. The server saves the notification settings it receives in the database.

[0736] Step 13:

[0737] The server continues to collect event information and updates it in real time, adding newly acquired event information to the database.

[0738] Step 14:

[0739] User selects a specific event and opens the details page. User visits the event details page on their device to view more information.

[0740] Step 15:

[0741] The terminal requests ticket information from the server. The front end sends a GET request to the backend API to obtain the ticket information.

[0742] Step 16:

[0743] The server retrieves ticket information from the database. The server searches the database for ticket information based on the event ID and returns it in JSON format.

[0744] Step 17:

[0745] The terminal displays the ticket information. The front-end parses the received JSON data and displays the ticket information on the page.

[0746] Step 18:

[0747] The user purchases a ticket. The user presses the ticket purchase button to begin the purchase process.

[0748] Step 19:

[0749] The terminal sends a purchase request to the server. The front end sends a POST request to the backend API to complete the purchase.

[0750] Step 20:

[0751] The server sends a request to the payment service. The server sends a request to an external payment service to process the payment.

[0752] Step 21:

[0753] The server receives the payment result and updates the database. If the payment is successful, the server saves the purchase data in the database and sends a confirmation email to the user.

[0754] Step 22:

[0755] The user plans their trip, using the in-app schedule planner to select transportation and accommodations.

[0756] Step 23:

[0757] The terminal sends the schedule information to the server. The front end sends a POST request to the backend API to send the schedule information to the server.

[0758] Step 24:

[0759] The server calculates the optimal itinerary and saves it in the database.The server calculates the optimal itinerary based on the schedule information and saves it in the database.

[0760] Step 25:

[0761] The device collects the user's emotional data. When the user uses the app, the device analyzes the user's facial expressions and input content to obtain emotional data.

[0762] Step 26:

[0763] The device sends emotion data to the server, which then sends a POST request to the backend API to receive the emotion data.

[0764] Step 27:

[0765] The server stores the emotional data in a database and analyzes it. The server then uses an emotion engine to analyze the user's emotional state.

[0766] Step 28:

[0767] The server recommends the most appropriate event information based on the emotional state, and based on the analysis results, filters the event information appropriate to the emotional state and sends it to the device.

[0768] Step 29:

[0769] The terminal displays event information based on emotions. The front-end analyzes the event information received from the server and displays it on the user interface.

[0770] Step 30:

[0771] A user opens the community page. A user accesses the community page on their device and browses the message board.

[0772] Step 31:

[0773] The terminal requests bulletin board information from the server. The front end sends a GET request to the back end API to retrieve the bulletin board information.

[0774] Step 32:

[0775] The server retrieves bulletin board information from the database. The server searches the bulletin board information from the database and returns it in JSON format.

[0776] Step 33:

[0777] The terminal displays the message board information. The front end parses the received JSON data and displays the message board information on the page.

[0778] Step 34:

[0779] A user posts: A user creates a new post on the message board and presses the send button.

[0780] Step 35:

[0781] The device sends the post content to the server. The front end sends a POST request to the backend API, sending the new post to the server.

[0782] Step 36:

[0783] The server saves the posted content in a database. The server saves the posted content received in a database and updates the bulletin board information.

[0784] Step 37:

[0785] The server analyzes interactions within the community and selects content that will have a positive impact on users. The emotion engine analyzes the message board content and prioritizes positive posts to display to users.

[0786] Step 38:

[0787] The terminal displays the analysis results of the emotion engine. Based on the analysis results received by the front end, positive posts are displayed preferentially on the message board.

[0788] Example 2

[0789] Next, a description will be given of Example 2. In the following description, the data processing device 12 will be referred to as a "server" and the smart glasses 214 will be referred to as a "terminal."

[0790] Conventional event participation support systems often handle each function separately: information collection and notification, ticket purchase, transportation and accommodation information, schedule planning, and community functions. As a result, they do not provide optimal services based on the user's emotional state, making it difficult to improve user satisfaction. Another issue is that they do not provide sufficient support to reduce the stress and hassle of participating in events.

[0791] The specific processing by the specific processing unit 290 of the data processing device 12 in the second embodiment is realized by the following means.

[0792] In this invention, the server includes means for collecting information on events across the country and notifying users according to their preferences, means for providing and rating ticket sales schedules and purchasing methods, means for providing information on transportation to event locations and accommodations around the venues and supporting reservations, means for proposing an action plan based on the user's itinerary and event schedule, means for providing a community function that allows users with the same goals to interact with each other, and means for analyzing the user's emotional state using an emotion engine and providing optimal services. This allows users to receive consistent and optimal support for participating in events, and also allows them to receive detailed support tailored to their emotional state.

[0793] "National event information" refers to information about events in all regions and genres, not limited to a specific region or genre.

[0794] "User preferences" refers to the user's interests and concerns that are inferred based on the events the user has previously selected and the genres in which the user has expressed interest.

[0795] "Notification" refers to a message, such as a push notification or email, sent to a user to convey specific information.

[0796] "Ticket sales schedule" refers to information regarding the date, time, and period when tickets for a particular event will go on sale.

[0797] "How to Buy" refers to information regarding the procedures and means for purchasing tickets to a particular event.

[0798] "Event Location" means the location where a particular Event takes place.

[0799] "Transportation" means any means of travel, such as train, bus, or plane, used to travel to the Event location.

[0800] "Accommodation Information" refers to information about hotels and accommodations around the event location.

[0801] "Supporting booking" means helping users smoothly book transportation and accommodation.

[0802] "Itinerary" refers to the series of travel, accommodation, and event participation plans that a User makes to attend an Event.

[0803] An "action plan" refers to suggestions regarding the optimal schedule and route for users to efficiently participate in an event.

[0804] "Users with the same purpose" refers to multiple users who share the same events or interests.

[0805] "Community function" refers to a function that allows users to exchange information and opinions online.

[0806] An "emotion engine" refers to algorithms and technologies that analyze a user's emotional state and provide optimal information and services based on the results.

[0807] The system according to the present invention provides a series of support functions for users to participate in an event. This system is realized by using the following various server functions, terminal functions, and user interfaces.

[0808] Event information collection and notification

[0809] The server collects event data from external event information sources (official sites, APIs, etc.). Specifically, it obtains the latest event information using, for example, web crawling technology or API integration. The collected data is then stored in a database such as MySQL or MongoDB. The server filters relevant event information based on the user's profile information and past participation history and sends it to the device. The device then provides the information to the user via push notifications or email notifications. The emotion engine analyzes the user's current emotional state and notifies them with the appropriate timing and content.

[0810] Example: If a user sets their preference for events by a specific artist, the server will collect new event information for that artist and send notifications to the user. For example, if the emotion engine determines that the user's emotional state is "excited," the notification content will be arranged to be bright and positive.

[0811] Providing ticket guides

[0812] The server stores the ticket sales schedule and purchase procedures in a database based on the collected event information. When a user views ticket information, the device retrieves the relevant ticket information from the server and displays it on the UI. The server also evaluates the difficulty of obtaining tickets and sends feedback to the device. The emotion engine adjusts messages encouraging purchases based on the user's emotional state.

[0813] Example: When a user checks ticket information on an event's details page, the device displays information from the server about the release date, how to purchase, and the difficulty of obtaining tickets. The emotion engine determines the user's emotion as "curiosity" and displays an active message encouraging them to purchase.

[0814] Providing transportation and accommodation information and reservation support

[0815] The server collects information on transportation to the event venue and accommodations near the venue and stores it in a database. When a user needs transportation or accommodation information, the device retrieves the optimal transportation and accommodation options from the server and displays them on the UI. In addition, the device provides reservation support, allowing users to complete reservations directly. The emotion engine suggests the optimal plan based on the user's emotional state.

[0816] Example: When a user searches for transportation to attend an event, the device retrieves and displays the most suitable train or bus information from the server. It also simultaneously displays information about accommodations and provides a link to make reservations. If the emotion engine determines that the user is feeling "fatigue," it will prioritize suggestions for comfortable accommodations.

[0817] Schedule planner function

[0818] Users register their travel itineraries and event schedules in the schedule planner. The device sends this information to the server, which stores it in a database and analyzes it. Based on the analysis results, the server calculates the optimal action plan and sends it to the device. The device then presents this action plan to the user and supports their event participation. The emotion engine takes into account the user's past emotional data and suggests the most satisfying plan.

[0819] Example: When a user registers their transportation method and arrival time for the day of an event in their schedule planner, the server analyzes this and suggests which transportation method to use at which time. If the emotion engine determines that the user's past emotional data indicates "excessive tension," it will recommend a less stressful transportation method.

[0820] Community Features

[0821] The server provides an online community function that allows users to interact with each other. Users can access the community page through their devices and post or comment on the message board. The server stores these posts in a database and makes them available for other users to view. The emotion engine analyzes interactions within the community and prioritizes displaying content that has a positive impact on users' emotions.

[0822] Example: When a user asks for recommendations on restaurants near the venue on a community bulletin board just before an event, other users reply and share that information. The emotion engine performs sentiment analysis and prioritizes positive posts and encouraging content.

[0823] The system of the present invention integrates various functions in this way and provides services that take into consideration the user's emotional state, thereby supporting users in participating in events in a comfortable manner.

[0824] The flow of the identification process in the second embodiment will be described with reference to FIG.

[0825] Event information collection and notification

[0826] Step 1:

[0827] The server collects data from external event information sources (official sites, APIs, etc.). It uses web crawling technology and API requests to efficiently obtain large amounts of data. The input requires the URL and API key of the event information source, and the output is the raw event information.

[0828] Step 2:

[0829] The server formats the collected event information data and stores it in a database such as MySQL or MongoDB. The input is raw event information data, and the output is formatted database entries.

[0830] Step 3:

[0831] The server filters the event information suitable for the user based on the user's profile information and past event participation history. The input is the user's profile information and the event information in the database, and the output is the filtered event information.

[0832] Step 4:

[0833] The server sends filtered event information to the terminal in real time. Here, data can be sent quickly using WebSocket, etc. The input is the filtered event information, and the output is a notification to the terminal that data transmission has been completed.

[0834] Step 5:

[0835] The device notifies the user of the information via push notification or email according to the user's settings. The input is the event information sent from the server, and the output is the notification message sent to the user.

[0836] Providing ticket guides

[0837] Step 1:

[0838] The server collects ticket release dates and purchasing procedures for events and stores them in a database. The input is the URL of the ticket information source, the API key, and the collected ticket information, and the output is the entries stored in the database.

[0839] Step 2:

[0840] A user visits an event details page and requests ticket information. The input is the user's request, and the output is a request sent to the server.

[0841] Step 3:

[0842] The server searches the database for the relevant ticket information and sends it to the terminal. The input is the user's request and the ticket information in the database, and the output is the data sent to the terminal.

[0843] Step 4:

[0844] The terminal displays the ticket information obtained from the server on the user interface (UI). The input is the ticket information sent from the server, and the output is the ticket information displayed on the UI.

[0845] Providing transportation and accommodation information and reservation support

[0846] Step 1:

[0847] The server collects transportation information to the event location and accommodation information around the venue and stores it in a database. The inputs are the sources of the transportation and accommodation information and the collected data, and the output is the entries stored in the database.

[0848] Step 2:

[0849] A user requests transportation and accommodation information. The input is the user request and the output is the submission of the request to the server.

[0850] Step 3:

[0851] The server searches the database for the best transportation and accommodation information and sends it to the terminal. The input is the user's request and the transportation and accommodation information in the database, and the output is the data transmission to the terminal.

[0852] Step 4:

[0853] The information acquired by the device is displayed on the UI, providing reservation support functions. The input is transportation and accommodation information sent from the server, and the output is the information displayed on the UI and a reservation link.

[0854] Schedule planner function

[0855] Step 1:

[0856] A user registers his / her travel itinerary or event schedule in the schedule planner. The input is the itinerary or schedule information entered by the user, and the output is the data sent to the server.

[0857] Step 2:

[0858] The terminal sends the input schedule information to the server. The input is the user's schedule information, and the output is data transmission to the server.

[0859] Step 3:

[0860] The server analyzes the data and calculates the optimal action plan. The input is schedule information and past data, and the output is the action plan as a result of the analysis.

[0861] Step 4:

[0862] The server sends the calculation results to the terminal. The input is the action plan, and the output is the data transmission to the terminal.

[0863] Step 5:

[0864] The terminal presents the action plan to the user. The input is the action plan sent from the server, and the output is the action plan displayed in the UI.

[0865] Community Features

[0866] Step 1:

[0867] The server provides online community functionality, where the input is information for building a community page, and the output is a user-accessible community page.

[0868] Step 2:

[0869] A user accesses a community page and posts or comments. The input is the content of the user's post or comment, and the output is data sent to the server.

[0870] Step 3:

[0871] The server stores the posts in a database. The input is the user's post or comment, and the output is the entry stored in the database.

[0872] Step 4:

[0873] The server makes the posts available for viewing by other users. The input is the saved posts, and the output is the data provided in a viewable form.

[0874] In this way, the system of the present invention comprehensively supports users' participation in events and integrates various functions to provide detailed support according to the user's emotional state.

[0875] (Application example 2)

[0876] Next, a description will be given of Application Example 2. In the following description, the data processing device 12 will be referred to as a "server" and the smart glasses 214 will be referred to as a "terminal."

[0877] Today's event participants and shoppers demand quick access to a wide variety of information and services. However, with so many information sources and services scattered across multiple platforms, it is difficult for users to obtain a consistent, optimal experience. Furthermore, there is a risk of stress increasing as information is not provided in a way that responds to users' emotions or individual needs. This often leads to dissatisfaction with the event participation or shopping experience.

[0878] The specific processing by the specific processing unit 290 of the data processing device 12 in the application example 2 is realized by the following means.

[0879] In this invention, the server includes means for collecting information on events across the country and notifying users based on their preferences, means for providing and rating ticket sales schedules and purchasing methods, means for providing information on transportation to event locations and accommodations around the venues and supporting reservations, means for proposing an action plan based on the user's itinerary and event schedule, means for providing a community function that allows users with similar goals to interact with each other, means for analyzing the user's emotional state and, based on that, suggesting optimal products and notifying users of promotions, and means for providing navigation within physical stores. This allows users to have a consistently comfortable and satisfying event participation and shopping experience.

[0880] "National event information" refers to data on all events held within the country.

[0881] "Preference-based notification" means a mechanism for selecting and notifying users of relevant event information based on their preferences and interests.

[0882] "Means for providing and rating ticket release schedules and purchasing methods" refers to a system that provides users with information about the release dates and purchasing methods for event tickets, as well as rating information for those tickets.

[0883] "Means of providing information on transportation and accommodation facilities around the venue and supporting reservations" refers to a function that provides information on access to the event venue and information on nearby accommodation facilities and supports reservations for these.

[0884] "A means for proposing an action plan based on the user's itinerary and event schedule" refers to a system that formulates and proposes an optimal action plan based on the user's specified itinerary and the schedule of events they plan to attend.

[0885] "Means for providing community functions" refers to a mechanism for providing functions that allow users with the same goals to interact online.

[0886] "A means of analyzing the user's emotional state and providing optimal product suggestions and promotional notifications based on that" refers to a mechanism that analyzes the user's current emotions and provides appropriate product and promotional information based on the results.

[0887] "A means for providing navigation within a physical store" refers to a system that provides guidance to users to quickly reach a specific location within a physical store.

[0888] The system of the present invention provides a series of support functions to enable users to participate in events and enjoy shopping comfortably and efficiently. This system is composed of a server, a terminal, and an emotion engine. The specific operation of the system and its details are explained below.

[0889] 1. Event information collection and notification

[0890] The server collects event data from external event information sources (official sites, APIs, etc.) and stores it in a database. Based on the user's preferences, the server filters out relevant event information and sends the results to the device. The device then notifies the user of the information via push notification or email according to the user's settings. In addition, the emotion engine analyzes the user's current emotional state and notifies them with appropriate timing and content.

[0891] Example: If a user sets up event information for their favorite artist, the server will automatically send a notification when new event information for that artist is added. If the emotion engine determines that the user's emotional state is "excited," the notification content will be positive.

[0892] 2. Providing ticket guides

[0893] The server stores the ticket sales schedule and purchase method in a database based on the collected event information. When a user views ticket information, the device retrieves the relevant information from the server and displays it on the user interface. The server also evaluates the difficulty of obtaining tickets and provides feedback to the device. The emotion engine adjusts messages to encourage purchases based on the user's emotions.

[0894] Example: When a user checks ticket information on an event's details page, the device displays information from the server, such as the release date, how to purchase, and the difficulty of obtaining tickets. The emotion engine determines the user's emotion as "curiosity" and sends an active message to encourage the purchase.

[0895] 3. Providing transportation and accommodation information and reservation support

[0896] The server collects information on transportation to the event venue and accommodations in the vicinity of the venue and stores it in a database. When a user needs transportation or accommodation information, the device retrieves the optimal options from the server and displays them on the user interface. The device also provides reservation support, allowing users to complete reservations directly. The emotion engine suggests the optimal plan based on the user's emotional state.

[0897] Example: When a user searches for transportation to attend an event, the device retrieves and displays the optimal train and bus information from the server. At the same time, it also displays information about nearby accommodations and provides a reservation link if necessary. If the emotion engine determines that the user is feeling "fatigue," it will prioritize suggestions for comfortable accommodations.

[0898] 4. Schedule planner function

[0899] Users register their travel itinerary and event schedule in the schedule planner. The device sends this to the server, which stores the data in a database and analyzes it. Based on the analysis results, the server calculates an optimal action plan and sends it to the device. The device presents it to the user and helps them participate in events based on that action plan. The emotion engine takes past emotion data into consideration and suggests the most satisfying plan.

[0900] Example: When a user registers their transportation method and arrival time on the day of an event, the server analyzes the information and suggests which transportation method to use and when. If the emotion engine determines that the user's past emotions are "excessive tension," it will recommend a less stressful transportation method.

[0901] 5. Community Features

[0902] The server provides an online community function that allows users to interact with each other. Users can access the community page through their devices and post or comment on the message board. The server stores these posts in a database and makes them available for other users to view. The emotion engine analyzes interactions within the community and prioritizes the display of content that has a positive impact on users' emotions.

[0903] Example: When a user asks for recommendations on restaurants near the venue on a community bulletin board just before an event, other users reply and share the information. The emotion engine performs sentiment analysis and prioritizes positive posts and encouraging content.

[0904] 6. In-store navigation

[0905] The device provides navigation functions to help users quickly find specific products or locations within physical stores, and an emotion engine calculates the optimal route based on the user's emotional state.

[0906] Example: If a user wants to find a specific product quickly, the device will show the shortest route. If the emotion engine determines that the user is feeling "relaxed," the device will guide the user to a scenic route.

[0907] 7. Emotion-based product recommendations and promotions

[0908] The emotion engine analyzes the user's emotional state in real time and suggests optimal products and promotions, which the device notifies the user of, increasing their desire to purchase.

[0909] Example: If a user types "I feel tired today," generate a prompt that prioritizes relaxation products (aromatherapy candles and herbal tea).

[0910] Prompt sentences for AI model generating concrete examples

[0911] "If a user types, 'I feel tired today,' the system should interpret that emotion as 'relaxation' and generate prompts that prioritize relaxation products like scented candles and herbal teas."

[0912] The flow of the specific processing in the application example 2 will be described with reference to FIG.

[0913] Step 1:

[0914] The server collects event data from external event information sources (official sites, APIs, etc.) and stores it in a database. At this time, the server also stores filtering information based on the user's preferences in the database. Event data from external information sources is input, and filtered event data is output and stored in the database. The server also obtains the user's current emotional state from the emotion engine to optimize the timing and content of notifications.

[0915] Step 2:

[0916] When a user uses a device to view event information, the device retrieves the relevant event information from the server and displays it on the user interface. The input is the user's viewing request, and the output is the displayed event information. Furthermore, the emotion engine analyzes the user's current emotional state and adjusts the notification content accordingly. For example, if the user is determined to be "excited," the notification content is adjusted to be more positive.

[0917] Step 3:

[0918] When a user views ticket information, the device retrieves the release schedule, purchase method, and ticket acquisition difficulty from the server and displays these on the user interface. The input is a ticket information request, and the output is detailed ticket information. The emotion engine also analyzes the user's emotions and adjusts messages to encourage purchases. For example, if the user is determined to be "curious," an active message will be displayed to encourage purchase.

[0919] Step 4:

[0920] When a user searches for information on transportation or accommodation, the device retrieves the optimal transportation and accommodation options from the server and displays them on the user interface. The input is a request for transportation or accommodation information, and the output is the display of the optimal options. In addition, an emotion engine analyzes the user's emotional state and suggests optimal plans, such as comfortable accommodation. For example, if the user is determined to be "fatigued," it will prioritize suggestions for comfortable accommodation.

[0921] Step 5:

[0922] When a user registers an itinerary or event schedule in the schedule planner, the device sends it to the server, which then calculates an optimal action plan and sends it to the device. The input is the itinerary or event schedule data, and the output is an optimal action plan. The emotion engine also takes into account past emotion data and suggests plans that will result in high satisfaction. For example, if the user is judged to be "excessively nervous," it will recommend a less stressful mode of transportation.

[0923] Step 6:

[0924] The server provides an online community function that allows users to interact with each other. Users can access the community page via their devices and post or comment. The input is the user's message board posting data, and the output is saved in a form that can be viewed by other users. The emotion engine performs emotion analysis and prioritizes the display of posts that have a positive impact. For example, if a user is judged to be "positive," encouraging posts will be displayed to the front.

[0925] Step 7:

[0926] The device provides navigation functions to help users quickly find specific products or locations within a physical store. The input is the user's destination request, and the output is navigation information to the destination. The emotion engine suggests the optimal route based on the user's emotional state. For example, if the user is judged to be "relaxed," the device will guide them to a scenic route.

[0927] Step 8:

[0928] The emotion engine analyzes the user's emotional state in real time and suggests the most suitable products and promotions. The device notifies the user of this, encouraging them to purchase. The input is the user's emotional data and product information, and the output is product suggestions and promotion information tailored to the emotion. In concrete terms, if the user inputs "I feel tired today," relaxation products will be suggested first.

[0929] Prompt sentences for AI model generating concrete examples

[0930] If the user types "I feel tired today," the system should interpret that emotion as "relaxation" and generate prompts that prioritize relaxation products like scented candles and herbal tea.

[0931] The specific processing unit 290 transmits the result of the specific processing to the smart glasses 214. In the smart glasses 214, the control unit 46A causes the speaker 240 to output the result of the specific processing. The microphone 238 acquires audio indicating a user input regarding the result of the specific processing. The control unit 46A transmits audio data indicating the user input acquired by the microphone 238 to the data processing device 12. In the data processing device 12, the specific processing unit 290 acquires the audio data.

[0932] The data generation model 58 is a so-called generative AI (Artificial Intelligence). An example of the data generation model 58 is ChatGPT (Internet Search<URL: https: / / openai.com / blog / chatgpt> ), Gemini (Internet search <url: https: gemini.google.com ?hl="ja">) and other generation AIs. The data generation model 58 is obtained by performing deep learning on a neural network. A prompt including an instruction is input to the data generation model 58, and inference data such as voice data indicating voice, text data indicating text, and image data indicating an image is also input. The data generation model 58 performs inference on the input inference data in accordance with the instruction indicated by the prompt, and outputs the inference result in a data format such as voice data and text data. Here, inference refers to, for example, analysis, classification, prediction, and / or summarization.

[0933] In the above embodiment, an example in which the specific processing is performed by the data processing device 12 has been given, but the technology of the present disclosure is not limited to this, and the specific processing may be performed by the smart glasses 214.

[0934] [Third embodiment]

[0935] FIG. 5 shows an example of the configuration of a data processing system 310 according to the third embodiment.

[0936] 5, the data processing system 310 includes the data processing device 12 and a headset type terminal 314. An example of the data processing device 12 is a server.

[0937] The data processing device 12 includes a computer 22, a database 24, and a communication I / F 26. The computer 22 is an example of a "computer" according to the technology of the present disclosure. The computer 22 includes a processor 28, a RAM 30, and a storage 32. The processor 28, the RAM 30, and the storage 32 are connected to a bus 34. The database 24 and the communication I / F 26 are also connected to the bus 34. The communication I / F 26 is connected to a network 54. Examples of the network 54 include a WAN (Wide Area Network) and / or a LAN (Local Area Network).

[0938] The headset type terminal 314 includes a computer 36, a microphone 238, a speaker 240, a camera 42, a communication I / F 44, and a display 343. The computer 36 includes a processor 46, a RAM 48, and a storage 50. The processor 46, the RAM 48, and the storage 50 are connected to a bus 52. The microphone 238, the speaker 240, the camera 42, and the display 343 are also connected to the bus 52.

[0939] The microphone 238 receives instructions and the like from the user 20 by receiving voice uttered by the user 20. The microphone 238 captures the voice uttered by the user 20, converts the captured voice into audio data, and outputs it to the processor 46. The speaker 240 outputs audio in accordance with instructions from the processor 46.

[0940] Camera 42 is a small digital camera equipped with an optical system including a lens, aperture, and shutter, and an imaging element such as a CMOS (Complementary Metal-Oxide-Semiconductor) image sensor or a CCD (Charge Coupled Device) image sensor, and captures images of the surroundings of user 20 (for example, an imaging range defined by an angle of view equivalent to the field of vision of a typical healthy person).

[0941] The communication I / F 44 is connected to a network 54. The communication I / Fs 44 and 26 are responsible for the exchange of various information between the processor 46 and the processor 28 via the network 54. The exchange of various information between the processor 46 and the processor 28 using the communication I / Fs 44 and 26 is carried out in a secure state.

[0942] Fig. 6 shows an example of the main functions of the data processing device 12 and the headset type terminal 314. As shown in Fig. 6, in the data processing device 12, a specific process is performed by the processor 28. A specific process program 56 is stored in the storage 32.

[0943] The specific processing program 56 is an example of a "program" according to the technology of the present disclosure. The processor 28 reads the specific processing program 56 from the storage 32 and executes the read specific processing program 56 on the RAM 30. The specific processing is realized by the processor 28 operating as a specific processing unit 290 in accordance with the specific processing program 56 executed on the RAM 30.

[0944] The storage 32 stores a data generation model 58 and an emotion identification model 59. The data generation model 58 and the emotion identification model 59 are used by the identification processing unit 290.

[0945] In the headset type terminal 314, a reception output process is performed by the processor 46. A reception output program 60 is stored in the storage 50. The processor 46 reads the reception output program 60 from the storage 50 and executes the read reception output program 60 on the RAM 48. The reception output process is realized by the processor 46 operating as the control unit 46A in accordance with the reception output program 60 executed on the RAM 48.

[0946] Next, a description will be given of the identification process performed by the identification processing unit 290 of the data processing device 12. In the following description, the data processing device 12 will be referred to as the "server" and the headset type terminal 314 will be referred to as the "terminal."

[0947] The system of the present invention provides a series of support functions for users to participate in events. Specifically, it includes functions for collecting event information, notifications, ticket guides, providing transportation and accommodation information, schedule planning, and community functions. The operation of this system is explained based on the following main steps.

[0948] Event information collection and notification

[0949] The server collects event data from external event information sources (official sites, APIs, etc.) and stores it in a database. Based on the user's preferences, the server filters the relevant event information and sends the results to the device. The device notifies the user of the information via push notification or email according to the user's settings.

[0950] Example: If a user specifies that they want to see events by a particular artist, the server will automatically notify the user when new events by that artist are added.

[0951] Providing ticket guides

[0952] The server stores the ticket sales schedule and purchase method in a database based on the collected event information. When a user views ticket information, the device retrieves the relevant information from the server and displays it on the user interface. In addition, the server evaluates the difficulty of obtaining tickets and sends feedback to the device.

[0953] Example: When a user checks ticket information on an event's details page, the device displays information from the server about the release date, how to purchase, and how easy it is to obtain tickets.

[0954] Providing transportation and accommodation information and reservation support

[0955] The server collects information on transportation to the event venue and accommodation options around the venue and stores it in a database. When a user needs transportation or accommodation information, the terminal retrieves the optimal transportation and accommodation options from the server and displays them on the user interface. In addition, the terminal provides reservation support functions, allowing users to complete reservations directly.

[0956] Example: When a user searches for transportation to an event, the device retrieves and displays the most suitable train and bus information from the server. At the same time, it also displays information about nearby accommodations and provides a reservation link if necessary.

[0957] Schedule planner function

[0958] Users register their travel itineraries and event schedules in the schedule planner. The device sends this information to the server, which stores it in a database and analyzes it. Based on the analysis results, the server calculates an optimal action plan and sends it to the device. The device then presents it to the user and helps them participate in events based on that action plan.

[0959] Example: When a user registers the mode of transportation and arrival time for the day of an event in their schedule planner, the server analyzes this and suggests which mode of transportation to use at what time.

[0960] Community Features

[0961] The server provides an online community function that allows users to interact with each other. Users can access the community page through their devices and post or comment on the message board. The server stores these posts in a database and makes them available to other users.

[0962] Example: A user asks on a community message board for recommendations on restaurants near the venue just before an event, and other users reply and share that information.

[0963] As described above, the system of the present invention streamlines the series of procedures required to participate in an event and provides optimal support to users. This system allows users to smoothly complete all processes, including information gathering, ticket purchase, transportation and accommodation arrangements, schedule management, and community participation.

[0964] The processing flow will be explained below.

[0965] Step 1:

[0966] The user enters information into the new registration form. The user enters their name, email address, password, etc. on the device and presses the registration button.

[0967] Step 2:

[0968] The device sends registration information to the server. The front end sends a POST request to the backend API, sending user information to the server.

[0969] Step 3:

[0970] The server saves the user information in the database. The server receives the user information, validates it (checks for format and duplication), and saves it in the database. After saving, a confirmation email is sent to the user.

[0971] Step 4:

[0972] The user receives a confirmation email and activates the account. The user opens the confirmation email and clicks the link to activate the account.

[0973] Step 5:

[0974] The server confirms the account activation. The server receives the link click, updates the account status in the database to activated, and notifies the user that activation is complete.

[0975] Step 6:

[0976] A user opens the event listing page. A user opens the event listing page on their device.

[0977] Step 7:

[0978] The device requests the latest event information from the server. The front end sends a GET request to the back end API to obtain the latest event information.

[0979] Step 8:

[0980] The server retrieves event information from the database. The server searches for the necessary event information from the database and returns it in JSON format.

[0981] Step 9:

[0982] The terminal displays the event information. The front end parses the received JSON data and displays the event information in the user interface.

[0983] Step 10:

[0984] The user sets notification settings. The user turns on notification settings for specific idle times.

[0985] Step 11:

[0986] The device sends the notification settings to the server. The front end sends a PUT request to the backend API to update the notification settings.

[0987] Step 12:

[0988] The server saves the notification settings in the database. The server saves the notification settings it receives in the database.

[0989] Step 13:

[0990] User selects a specific event and opens the details page. User visits the event details page on their device to view more information.

[0991] Step 14:

[0992] The terminal requests ticket information from the server. The front end sends a GET request to the backend API to obtain the ticket information.

[0993] Step 15:

[0994] The server retrieves ticket information from the database. The server searches the database for ticket information based on the event ID and returns it in JSON format.

[0995] Step 16:

[0996] The terminal displays the ticket information. The front-end parses the received JSON data and displays the ticket information on the page.

[0997] Step 17:

[0998] The user purchases a ticket. The user presses the ticket purchase button to begin the purchase process.

[0999] Step 18:

[1000] The terminal sends a purchase request to the server. The front end sends a POST request to the backend API to complete the purchase.

[1001] Step 19:

[1002] The server sends a request to the payment service. The server sends a request to the external payment service to process the payment.

[1003] Step 20:

[1004] The server receives the payment result and updates the database. If the payment is successful, the server saves the purchase data in the database and sends a confirmation email to the user.

[1005] Step 21:

[1006] The user plans their trip, using the in-app schedule planner to select transportation and accommodations.

[1007] Step 22:

[1008] The terminal sends the schedule information to the server. The front end sends a POST request to the backend API to send the schedule information to the server.

[1009] Step 23:

[1010] The server calculates the optimal itinerary and saves it in the database.The server calculates the optimal itinerary based on the schedule information and saves it in the database.

[1011] Step 24:

[1012] A user opens the community page. A user accesses the community page on their device and browses the message board.

[1013] Step 25:

[1014] The terminal requests bulletin board information from the server. The front end sends a GET request to the back end API to retrieve the bulletin board information.

[1015] Step 26:

[1016] The server retrieves bulletin board information from the database. The server searches the bulletin board information from the database and returns it in JSON format.

[1017] Step 27:

[1018] The terminal displays the message board information. The front end parses the received JSON data and displays the message board information on the page.

[1019] Step 28:

[1020] A user posts: A user creates a new post on the message board and presses the send button.

[1021] Step 29:

[1022] The device sends the post content to the server. The front end sends a POST request to the backend API, sending the new post to the server.

[1023] Step 30:

[1024] The server saves the posted content in a database. The server saves the posted content received in a database and updates the bulletin board information.

[1025] Example 1

[1026] Next, a description will be given of Example 1. In the following description, the data processing device 12 will be referred to as a "server" and the headset type terminal 314 will be referred to as a "terminal."

[1027] In the past, gathering information, purchasing tickets, and arranging transportation and accommodation to participate in an event required time and effort, placing a burden on users. Furthermore, the management of event information and participation plans was dispersed, making it difficult to participate in events efficiently. Furthermore, opportunities to share information through interactions with other participants were limited.

[1028] The specific processing by the specific processing unit 290 of the data processing device 12 in the first embodiment is realized by the following means.

[1029] In this invention, the server includes: means for collecting event information from across the country and notifying users based on their preferences; means for providing and rating ticket sales schedules and purchasing methods; means for providing information on transportation to event locations and accommodations near the venues and supporting reservations; means for suggesting an action plan based on the user's itinerary and event schedule; means for providing a community function that allows users with similar interests to interact with each other; means for periodically collecting event information from external sources and storing it in a database; means for filtering the information based on the database and notifying users of the most appropriate event information via push notification or email; and means for calculating the difficulty of obtaining tickets and providing the information to users. This allows users to efficiently collect event information and smoothly purchase tickets and make arrangements for transportation and accommodation. Users can also obtain more information by interacting with other participants.

[1030] "National event information" refers to information about events of various genres held throughout the country, not limited to a specific region.

[1031] "Notifying based on user preferences" means selecting and notifying the user of relevant event information based on the user's pre-defined interests and preferences.

[1032] "Providing and evaluating ticket release schedules and purchasing methods" means providing information about when event tickets go on sale and how to purchase them, and based on that information evaluating the difficulty and convenience of obtaining tickets and communicating that information to users.

[1033] Providing "information on transportation to the event venue and accommodations in the vicinity" and supporting reservations means providing information on transportation and accommodations for users to attend the event, and supporting the reservation process.

[1034] "Suggesting an action plan based on the user's itinerary and event schedule" means calculating and suggesting an optimal action plan to the user based on the event dates and transportation details entered by the user.

[1035] "Providing a community function that allows users with the same goals to interact with each other" means providing an online platform where event participants can share information, exchange opinions, and ask questions.

[1036] "Regularly collect from external sources and store in a database" means periodically obtaining event information from reliable external sources such as official websites and APIs and storing it in a database.

[1037] "Filtering based on a database" means sorting stored event information based on user settings and preferences.

[1038] "Notifying users of the most appropriate event information via push notification or email" means notifying users directly of filtered event information in a manner that suits their settings.

[1039] "Calculating the difficulty of obtaining tickets" means assessing the difficulty of obtaining event tickets based on past data and current demand, and providing this to users.

[1040] The system of this invention provides a series of support functions for users to participate in events. Specifically, it provides a comprehensive range of functions, including event information collection, notification, ticket guide, transportation and accommodation information, schedule planner, and community functions. To realize the operation of this system, the server, terminals, and users each play different roles.

[1041] First, the server periodically retrieves event data from external event information sources (such as official event websites or APIs). The collected data is stored in a database containing information such as the event name, date and time, location, and details. For example, a library such as the Apache HTTP client can be used to collect the information.

[1042] When a user logs in to the system and selects the genres and artists they are interested in, the server filters the relevant event information from the database based on the user's preferences. This filtering is done using database queries and stored procedures. The filtered results are sent to the device, which then notifies the user via push notification or email.

[1043] For example, if a user specifies that they want to receive notifications for events by a specific artist, the server will automatically notify the user when new events for that artist are added. An example of a prompt would be, "How do I set up notifications for events by a specific artist?"

[1044] Next, when a user views an event's details page, the device requests ticket information for that event from the server. The server retrieves ticket information (release date, price, purchase method, etc.) from the database and returns it to the device. The server then calculates the difficulty of obtaining tickets using past sales data and a demand forecasting algorithm, and sends feedback to the device.

[1045] For example, when a user checks ticket information on an event's details page, the device displays information from the server about the release date, how to purchase, and the difficulty of obtaining tickets. An example of a prompt sentence is, "Please tell me how to rate the difficulty of obtaining tickets for an event."

[1046] The server also retrieves information about transportation options to the event location (trains, buses, taxis, etc.) and accommodations near the venue from travel APIs and hotel booking site APIs, and stores this information in a database. When a user needs this information, the device retrieves the optimal options from the server and presents them to the user. Users can then use the reservation support function to complete their reservations directly.

[1047] For example, when a user searches for transportation, the device retrieves and displays the best transportation options from the server. Similarly, it displays accommodation information and provides a booking link if necessary. An example of a prompt is, "How do I search for transportation and accommodation information for an event?"

[1048] With the schedule planner function, users can register their event schedules. The device then sends the schedules to the server, which stores them in a database and analyzes them. Based on the analysis results, the server calculates an optimal action plan and sends it to the device. Users can then act accordingly.

[1049] For example, when a user enters information into a schedule planner, the server suggests which means of transportation to use at which time. An example of a prompt sentence is, "Please tell me how to calculate the optimal itinerary by entering the mode of transportation and arrival time on the day of the event."

[1050] Finally, the server provides an online community function that allows users to interact with each other. Users can access the community page through their devices and post or comment on the message board. The server stores these posts in a database and makes them available to other users.

[1051] For example, if a user asks for information about restaurants near the venue on a community bulletin board just before an event, other users will reply and share that information. An example of a prompt sentence is, "Please tell me how to ask for recommended restaurant information on a community bulletin board just before an event."

[1052] As described above, the system streamlines the entire process for users to participate in events efficiently and provides a wealth of information and support.

[1053] The flow of the identification process in the first embodiment will be described with reference to FIG.

[1054] Step 1: Gather event information

[1055] The server periodically collects event data from external event information sources (e.g., official event websites, APIs, etc.). Specifically, the server sends API requests, parses the returned data in JSON format, and stores it in a database.

[1056] Input: API request from external information source

[1057] Output: Parsed event data stored in a database

[1058] Step 2: Filtering event information

[1059] When a user logs into the system and selects the genres and artists they are interested in, the server uses a database query to filter relevant event information from the database based on the user's preferences.

[1060] Input: User interests and preferences

[1061] Output: Filtered event information

[1062] Step 3: Event information notification

[1063] The filtered event information is sent to the device, and the device notifies the user via push notification or email, depending on the user settings.

[1064] Input: Filtered event information

[1065] Output: Push notification and email notification

[1066] Step 4: Get ticket information

[1067] When a user views an event's details page, the device requests ticket information for that event from the server. The server retrieves ticket information (release date, price, purchase method, etc.) from the database and returns that information to the device.

[1068] Input: Ticket information request from user

[1069] Output: Retrieved ticket information

[1070] Step 5: Calculating ticket difficulty

[1071] The server calculates the difficulty of obtaining tickets using past sales data and demand forecasting algorithms, and provides this information to users via their devices.

[1072] Input: Past sales data, demand data

[1073] Output: Ticket acquisition difficulty rating

[1074] Step 6: Providing transportation and accommodation information

[1075] When a user searches for transportation or accommodation information for an event, the device sends a request to the server, which returns the best options to the user based on information retrieved from travel APIs and hotel booking site APIs.

[1076] Input: User request for transportation and accommodation information

[1077] Output: Best transportation and accommodation information

[1078] Step 7: Schedule Planner

[1079] Users register their event participation schedule in the schedule planner. The device sends this to the server, which stores it in a database and analyzes it. The optimal action plan is calculated and provided to the user via the device.

[1080] Input: User's schedule information

[1081] Output: Optimal action plan

[1082] Step 8: Community Features

[1083] Users can access the community page through their devices and post or comment on the message board. The server stores these posts in a database and makes them available to other users.

[1084] Input: User posts and comments

[1085] Output: Saved posts, comments displayed

[1086] (Application example 1)

[1087] Next, a description will be given of Application Example 1. In the following description, the data processing device 12 will be referred to as a "server" and the headset type terminal 314 will be referred to as a "terminal."

[1088] Currently, when users participate in a virtual event, they must use multiple methods, such as gathering event information, purchasing tickets, checking access methods, managing schedules, and interacting with the community, which takes a lot of time and effort.In addition, access guides and real-time event information updates, which are specific to virtual events, are often not provided sufficiently.

[1089] The specific processing by the specific processing unit 290 of the data processing device 12 in the application example 1 is realized by the following means.

[1090] In this invention, the server includes means for collecting information on events across the country and notifying users based on their preferences, means for providing and rating ticket sales schedules and purchasing methods, means for providing access methods to the event location or virtual event venue and information on nearby accommodations and supporting reservations, means for proposing an action plan based on the user's itinerary and event schedule, means for providing a community function that allows users with the same goals to interact with each other, and means for providing a guide to accessing the virtual venue.This significantly reduces the effort and time required for users to participate in virtual events, allowing them to enjoy the event more smoothly.

[1091] "Collecting event information nationwide" means gathering data on various events across the country.

[1092] "Providing notifications based on user preferences" means notifying users of appropriate event information based on the interests and concerns they have set.

[1093] "Providing and evaluating ticket release schedules and purchasing methods" means providing information about the sale period and purchasing methods of event tickets and evaluating the difficulty of obtaining them.

[1094] "How to access the event location or virtual event venue" means directions to the physical location where the event is being held or how to access the online virtual space.

[1095] "Providing information about nearby accommodations and supporting reservations" means providing information about accommodations near the venue and helping people make reservations.

[1096] "Suggesting an action plan based on the user's itinerary and event schedule" means proposing the optimal action plan based on the schedule of events and plans set by the user.

[1097] "Providing a community function that allows users with the same goals to interact with each other" means providing a function that allows users with common interests and goals to exchange opinions and share information.

[1098] "Providing a guide to accessing the virtual venue" means providing instructions and procedures for accessing the virtual space where the event will be held online.

[1099] "Push notifications about specific events and areas of interest based on user preferences" means providing real-time notifications about relevant events and areas of interest based on user-specified preferences.

[1100] The present invention is a system that comprehensively supports users' participation in events, and includes the following configuration and operation.

[1101] Event information collection and notification

[1102] The server collects event data from external event information sources (such as official websites and APIs) and stores it in a database. Based on the user's preferences, the server filters the relevant event information and sends the results to the device. The device then notifies the user of the information via push notifications or emails, depending on the user's settings.

[1103] For example, if a user specifies that they want to see events by a particular artist, the server will collect event information for that artist and automatically send notifications.

[1104] Providing ticket guides

[1105] The server stores the ticket sales schedule and purchase method in a database based on the collected event information. When a user views ticket information, the device retrieves the relevant information from the server and displays it on the user interface. The server also evaluates the difficulty of obtaining tickets and sends the evaluation results to the device.

[1106] For example, when a user checks ticket information on an event's details page, the device displays information from the server about the release date, how to purchase tickets, and how difficult it is to obtain tickets.

[1107] Providing transportation and accommodation information and reservation support

[1108] The server collects information on how to access the event venue or virtual event venue and accommodation information around the venue and stores it in a database. When a user needs transportation or accommodation information, the terminal retrieves the optimal transportation and accommodation options from the server and displays them on the user interface. In addition, the terminal provides reservation support functions, allowing users to complete reservations directly.

[1109] For example, when a user searches for transportation to an event, the device retrieves the optimal transportation and accommodation information from the server and displays it, and also provides a reservation link if necessary.

[1110] Schedule planner function

[1111] Users register their travel itineraries and event schedules in the schedule planner. The device sends this information to the server, which stores it in a database and analyzes it. Based on the analysis results, the server calculates an optimal action plan and sends it to the device. The device then presents it to the user and helps them participate in events based on that action plan.

[1112] As a concrete example, when a user registers the mode of transportation and arrival time for the day of the event in their schedule planner, the server analyzes this and suggests which mode of transportation to use at what time.

[1113] Community Features

[1114] The server provides an online community function that allows users to interact with each other. Users can access the community page through their devices and post or comment on the message board. The server stores these posts in a database and makes them available to other users.

[1115] For example, if a user asks on a community bulletin board for information about recommended restaurants near the venue just before an event, other users will reply and share that information.

[1116] Virtual Venue Access Guide

[1117] For virtual events, the server provides information on how to access the online event venue and the necessary procedures, allowing users to easily access the virtual venue through their devices and smoothly participate in the event.

[1118] For example, when a user wants to join a virtual event, the server provides an access link and connection instructions to the virtual venue, facilitating the process for the user.

[1119] Prompt Sentence Examples

[1120] "Tell me about the event. The artist you're interested in is 'The Beatles.'"

[1121] As described above, the present invention provides a system that comprehensively supports all procedures related to event participation and places little burden on users.

[1122] The flow of the specific processing in the application example 1 will be described with reference to FIG.

[1123] Step 1:

[1124] The server collects event data from external event information sources (official sites, APIs, etc.) and stores it in a database. The input includes the URL of the event information source and authentication information such as an API key. This allows the server to obtain new event information and create a database entry to store it. The output is the stored event information.

[1125] Step 2:

[1126] If a user is interested in events by a specific artist or genre, that information is set on the device. The input includes a prompt about the user's interests, such as "Tell me about the event. The artist I'm interested in is The Beatles." The device then saves the user's settings. The output is the user's interest information.

[1127] Step 3:

[1128] The server filters the collected event information based on the user's preferences. The input includes the user's preference settings and the event information in the database. The server then selects the relevant event information and sends it to the terminal. The output is the filtered event information.

[1129] Step 4:

[1130] The device notifies the user of the event information received from the server via push notification or email. The input includes filtered event information. This allows the device to notify the user of events of interest in real time. The output is a notification to the user.

[1131] Step 5:

[1132] The server collects event ticket information (release date, purchase method, difficulty of obtaining tickets, etc.) and stores it in a database. The input includes event information and related ticket sales information, which allows the server to provide detailed ticket information. The output is the stored ticket information.

[1133] Step 6:

[1134] When a user views ticket information for an event, the device retrieves the relevant information from the server and displays it on the user interface. The input includes the ID and keywords of the event that the user is interested in. This allows the device to provide detailed ticket information to the user. The output is the ticket information displayed on the screen.

[1135] Step 7:

[1136] The server collects access and accommodation information for the event location or virtual event venue and stores it in a database. Inputs include the location of the event venue and the URL of the virtual room, which enables the server to provide access and accommodation information to users. Outputs include the stored access and accommodation information.

[1137] Step 8:

[1138] When a user searches for transportation or accommodation information, the device retrieves the best options from the server and displays them in the user interface. The input includes the user's search query, which enables the device to provide the best transportation and accommodation information. The output is the recommended transportation and accommodation options for the user.

[1139] Step 9:

[1140] Users register their travel and event schedules in the schedule planner. The input includes details such as the event time, location, transportation, and arrival time. The device then saves and manages the user's schedule. The output is the registered schedule information.

[1141] Step 10:

[1142] The server analyzes the user's schedule, calculates the optimal action plan, and sends it to the terminal. The input includes the user's schedule information and event information. The server calculates the optimal action plan and presents it to the user. The output is the calculated action plan.

[1143] Step 11:

[1144] The server provides an online community where users can interact with each other and allows access to its functionality through the device. Input includes user posts and comments. The server then stores the posts in a database for other users to view. Output is the stored posts.

[1145] Step 12:

[1146] In the case of a virtual event, the server provides the user with access instructions and procedures to the virtual venue and guides them through the terminal. The input includes access information for the virtual venue, which allows the server to smoothly participate in the virtual event. The output is the provided access information.

[1147] Furthermore, an emotion engine that estimates the user's emotion may be further combined. That is, the identification processing unit 290 may estimate the user's emotion using the emotion identification model 59, and perform identification processing using the user's emotion.

[1148] The system of the present invention provides a series of support functions for users to participate in events. Specifically, it includes functions for collecting event information, notifications, ticket guides, providing transportation and accommodation information, schedule planners, and community functions. It also incorporates an emotion engine that recognizes the user's emotions and provides optimal services according to their emotional state. The operation of this system is explained based on the following main steps.

[1149] Event information collection and notification

[1150] The server collects event data from external event information sources (official sites, APIs, etc.) and stores it in a database. Based on the user's preferences, the server filters the relevant event information and sends the results to the device. The device notifies the user of the information via push notification or email according to the user's settings.

[1151] Furthermore, the emotion engine analyzes the user's current emotional state and delivers notifications with appropriate timing and content. For example, if the user is feeling stressed, notifications of events that will help them relax will be prioritized.

[1152] Example: If a user specifies that they want to see events by a specific artist, the server will automatically notify the user when new event information for that artist is added. If the emotion engine determines that the user's emotional state is "excited," the notification content will be bright and positive.

[1153] Providing ticket guides

[1154] The server stores the ticket sales schedule and purchase method in a database based on the collected event information. When a user views ticket information, the device retrieves the relevant information from the server and displays it on the user interface. The server also evaluates the difficulty of obtaining tickets and sends feedback to the device. The emotion engine adjusts messages to encourage purchases based on the user's emotions.

[1155] Example: When a user checks ticket information on an event's details page, the device displays information from the server about the release date, how to purchase, and the difficulty of obtaining tickets. The emotion engine determines the user's emotion as "curiosity" and displays an active message encouraging them to purchase.

[1156] Providing transportation and accommodation information and reservation support

[1157] The server collects information on transportation to the event venue and accommodation options around the venue and stores it in a database. When a user needs transportation or accommodation information, the device retrieves the optimal transportation and accommodation options from the server and displays them on the user interface. In addition, the device provides reservation support, allowing users to complete reservations directly. The emotion engine suggests the optimal plan based on the user's emotional state.

[1158] Example: When a user searches for transportation to attend an event, the device retrieves and displays information on the most suitable train or bus from the server. At the same time, it also displays information on nearby accommodations and provides a reservation link if necessary. If the emotion engine determines that the user is feeling "fatigue," it will prioritize suggestions for comfortable accommodations.

[1159] Schedule planner function

[1160] Users register their travel itineraries and event schedules in the schedule planner. The device sends this information to the server, which stores it in a database and analyzes it. Based on the analysis results, the server calculates an optimal action plan and sends it to the device. The device presents it to the user and helps them participate in events based on that action plan. The emotion engine takes into account the user's past emotional data and suggests the most satisfying plan.

[1161] Example: When a user registers their transportation method and arrival time for the day of an event in their schedule planner, the server analyzes this and suggests which transportation method to use at which time. If the emotion engine determines that the user's past emotional data indicates "excessive tension," it will recommend a less stressful transportation method.

[1162] Community Features

[1163] The server provides an online community function that allows users to interact with each other. Users can access the community page through their devices and post or comment on the message board. The server stores these posts in a database and makes them available for other users to view. The emotion engine analyzes interactions within the community and prioritizes displaying content that has a positive impact on users' emotions.

[1164] Example: When a user asks for recommendations on restaurants near the venue on a community message board just before an event, other users reply and share that information. The emotion engine performs sentiment analysis and prioritizes positive posts and encouraging content.

[1165] As described above, the system according to the present invention provides optimal support according to the user's emotional state by incorporating an emotion engine in addition to conventional functions, thereby enabling the user to participate in events in a more comfortable and satisfying way.

[1166] The processing flow will be explained below.

[1167] Step 1:

[1168] The user enters information into the new registration form. The user enters their name, email address, password, etc. on the device and presses the registration button.

[1169] Step 2:

[1170] The device sends registration information to the server. The front end sends a POST request to the backend API, sending user information to the server.

[1171] Step 3:

[1172] The server saves the user information in the database. The server receives the user information, validates it (checks for format and duplication), and saves it in the database. After saving, a confirmation email is sent to the user.

[1173] Step 4:

[1174] The user receives a confirmation email and activates the account. The user opens the confirmation email and clicks the link to activate the account.

[1175] Step 5:

[1176] The server confirms the account activation. The server receives the link click, updates the account status in the database to activated, and notifies the user that activation is complete.

[1177] Step 6:

[1178] A user opens the event listing page. A user opens the event listing page on their device.

[1179] Step 7:

[1180] The device requests the latest event information from the server. The front end sends a GET request to the back end API to obtain the latest event information.

[1181] Step 8:

[1182] The server retrieves event information from the database. The server searches for the necessary event information from the database and returns it in JSON format.

[1183] Step 9:

[1184] The terminal displays the event information. The front end parses the received JSON data and displays the event information in the user interface.

[1185] Step 10:

[1186] Users can set notification preferences. Users can turn on notification preferences for specific idols and events.

[1187] Step 11:

[1188] The device sends the notification settings to the server. The front end sends a PUT request to the backend API to update the notification settings.

[1189] Step 12:

[1190] The server saves the notification settings in the database. The server saves the notification settings it receives in the database.

[1191] Step 13:

[1192] The server continues to collect event information and updates it in real time, adding newly acquired event information to the database.

[1193] Step 14:

[1194] User selects a specific event and opens the details page. User visits the event details page on their device to view more information.

[1195] Step 15:

[1196] The terminal requests ticket information from the server. The front end sends a GET request to the backend API to obtain the ticket information.

[1197] Step 16:

[1198] The server retrieves ticket information from the database. The server searches the database for ticket information based on the event ID and returns it in JSON format.

[1199] Step 17:

[1200] The terminal displays the ticket information. The front-end parses the received JSON data and displays the ticket information on the page.

[1201] Step 18:

[1202] The user purchases a ticket. The user presses the ticket purchase button to begin the purchase process.

[1203] Step 19:

[1204] The terminal sends a purchase request to the server. The front end sends a POST request to the backend API to complete the purchase.

[1205] Step 20:

[1206] The server sends a request to the payment service. The server sends a request to an external payment service to process the payment.

[1207] Step 21:

[1208] The server receives the payment result and updates the database. If the payment is successful, the server saves the purchase data in the database and sends a confirmation email to the user.

[1209] Step 22:

[1210] The user plans their trip, using the in-app schedule planner to select transportation and accommodations.

[1211] Step 23:

[1212] The terminal sends the schedule information to the server. The front end sends a POST request to the backend API to send the schedule information to the server.

[1213] Step 24:

[1214] The server calculates the optimal itinerary and saves it in the database.The server calculates the optimal itinerary based on the schedule information and saves it in the database.

[1215] Step 25:

[1216] The device collects the user's emotional data. When the user uses the app, the device analyzes the user's facial expressions and input content to obtain emotional data.

[1217] Step 26:

[1218] The device sends emotion data to the server, which then sends a POST request to the backend API to receive the emotion data.

[1219] Step 27:

[1220] The server stores the emotional data in a database and analyzes it. The server then uses an emotion engine to analyze the user's emotional state.

[1221] Step 28:

[1222] The server recommends the most appropriate event information based on the emotional state, and based on the analysis results, filters the event information appropriate to the emotional state and sends it to the device.

[1223] Step 29:

[1224] The terminal displays event information based on emotions. The front-end analyzes the event information received from the server and displays it on the user interface.

[1225] Step 30:

[1226] A user opens the community page. A user accesses the community page on their device and browses the message board.

[1227] Step 31:

[1228] The terminal requests bulletin board information from the server. The front end sends a GET request to the back end API to retrieve the bulletin board information.

[1229] Step 32:

[1230] The server retrieves bulletin board information from the database. The server searches the bulletin board information from the database and returns it in JSON format.

[1231] Step 33:

[1232] The terminal displays the message board information. The front end parses the received JSON data and displays the message board information on the page.

[1233] Step 34:

[1234] A user posts: A user creates a new post on the message board and presses the send button.

[1235] Step 35:

[1236] The device sends the post content to the server. The front end sends a POST request to the backend API, sending the new post to the server.

[1237] Step 36:

[1238] The server saves the posted content in a database. The server saves the posted content received in a database and updates the bulletin board information.

[1239] Step 37:

[1240] The server analyzes interactions within the community and selects content that will have a positive impact on users. The emotion engine analyzes the message board content and prioritizes positive posts to display to users.

[1241] Step 38:

[1242] The terminal displays the analysis results of the emotion engine. Based on the analysis results received by the front end, positive posts are displayed preferentially on the message board.

[1243] Example 2

[1244] Next, a description will be given of Example 2. In the following description, the data processing device 12 will be referred to as a "server" and the headset type terminal 314 will be referred to as a "terminal."

[1245] Conventional event participation support systems often handle each function separately: information collection and notification, ticket purchase, transportation and accommodation information, schedule planning, and community functions. As a result, they do not provide optimal services based on the user's emotional state, making it difficult to improve user satisfaction. Another issue is that they do not provide sufficient support to reduce the stress and hassle of participating in events.

[1246] The specific processing by the specific processing unit 290 of the data processing device 12 in the second embodiment is realized by the following means.

[1247] In this invention, the server includes means for collecting information on events across the country and notifying users according to their preferences, means for providing and rating ticket sales schedules and purchasing methods, means for providing information on transportation to event locations and accommodations around the venues and supporting reservations, means for proposing an action plan based on the user's itinerary and event schedule, means for providing a community function that allows users with the same goals to interact with each other, and means for analyzing the user's emotional state using an emotion engine and providing optimal services. This allows users to receive consistent and optimal support for participating in events, and also allows them to receive detailed support tailored to their emotional state.

[1248] "National event information" refers to information about events in all regions and genres, not limited to a specific region or genre.

[1249] "User preferences" refers to the user's interests and concerns that are inferred based on the events the user has previously selected and the genres in which the user has expressed interest.

[1250] "Notification" refers to a message, such as a push notification or email, sent to a user to convey specific information.

[1251] "Ticket sales schedule" refers to information regarding the date, time, and period when tickets for a particular event will go on sale.

[1252] "How to Buy" refers to information regarding the procedures and means for purchasing tickets to a particular event.

[1253] "Event Location" means the location where a particular Event takes place.

[1254] "Transportation" means any means of travel, such as train, bus, or plane, used to travel to the Event location.

[1255] "Accommodation Information" refers to information about hotels and accommodations around the event location.

[1256] "Supporting booking" means helping users smoothly book transportation and accommodation.

[1257] "Itinerary" refers to the series of travel, accommodation, and event participation plans that a User makes to attend an Event.

[1258] An "action plan" refers to suggestions regarding the optimal schedule and route for users to efficiently participate in an event.

[1259] "Users with the same purpose" refers to multiple users who share the same events or interests.

[1260] "Community function" refers to a function that allows users to exchange information and opinions online.

[1261] An "emotion engine" refers to algorithms and technologies that analyze a user's emotional state and provide optimal information and services based on the results.

[1262] The system according to the present invention provides a series of support functions for users to participate in an event. This system is realized by using the following various server functions, terminal functions, and user interfaces.

[1263] Event information collection and notification

[1264] The server collects event data from external event information sources (official sites, APIs, etc.). Specifically, it obtains the latest event information using, for example, web crawling technology or API integration. The collected data is then stored in a database such as MySQL or MongoDB. The server filters relevant event information based on the user's profile information and past participation history and sends it to the device. The device then provides the information to the user via push notifications or email notifications. The emotion engine analyzes the user's current emotional state and notifies them with the appropriate timing and content.

[1265] Example: If a user sets their preference for events by a specific artist, the server will collect new event information for that artist and send notifications to the user. For example, if the emotion engine determines that the user's emotional state is "excited," the notification content will be arranged to be bright and positive.

[1266] Providing ticket guides

[1267] The server stores the ticket sales schedule and purchase procedures in a database based on the collected event information. When a user views ticket information, the device retrieves the relevant ticket information from the server and displays it on the UI. The server also evaluates the difficulty of obtaining tickets and sends feedback to the device. The emotion engine adjusts messages encouraging purchases based on the user's emotional state.

[1268] Example: When a user checks ticket information on an event's details page, the device displays information from the server about the release date, how to purchase, and the difficulty of obtaining tickets. The emotion engine determines the user's emotion as "curiosity" and displays an active message encouraging them to purchase.

[1269] Providing transportation and accommodation information and reservation support

[1270] The server collects information on transportation to the event venue and accommodations near the venue and stores it in a database. When a user needs transportation or accommodation information, the device retrieves the optimal transportation and accommodation options from the server and displays them on the UI. In addition, the device provides reservation support, allowing users to complete reservations directly. The emotion engine suggests the optimal plan based on the user's emotional state.

[1271] Example: When a user searches for transportation to attend an event, the device retrieves and displays the most suitable train or bus information from the server. It also simultaneously displays information about accommodations and provides a link to make reservations. If the emotion engine determines that the user is feeling "fatigue," it will prioritize suggestions for comfortable accommodations.

[1272] Schedule planner function

[1273] Users register their travel itineraries and event schedules in the schedule planner. The device sends this information to the server, which stores it in a database and analyzes it. Based on the analysis results, the server calculates the optimal action plan and sends it to the device. The device then presents this action plan to the user and supports their event participation. The emotion engine takes into account the user's past emotional data and suggests the most satisfying plan.

[1274] Example: When a user registers their transportation method and arrival time for the day of an event in their schedule planner, the server analyzes this and suggests which transportation method to use at which time. If the emotion engine determines that the user's past emotional data indicates "excessive tension," it will recommend a less stressful transportation method.

[1275] Community Features

[1276] The server provides an online community function that allows users to interact with each other. Users can access the community page through their devices and post or comment on the message board. The server stores these posts in a database and makes them available for other users to view. The emotion engine analyzes interactions within the community and prioritizes displaying content that has a positive impact on users' emotions.

[1277] Example: When a user asks for recommendations on restaurants near the venue on a community bulletin board just before an event, other users reply and share that information. The emotion engine performs sentiment analysis and prioritizes positive posts and encouraging content.

[1278] The system of the present invention integrates various functions in this way and provides services that take into consideration the user's emotional state, thereby supporting users in participating in events in a comfortable manner.

[1279] The flow of the identification process in the second embodiment will be described with reference to FIG.

[1280] Event information collection and notification

[1281] Step 1:

[1282] The server collects data from external event information sources (official sites, APIs, etc.). It uses web crawling technology and API requests to efficiently obtain large amounts of data. The input requires the URL and API key of the event information source, and the output is the raw event information.

[1283] Step 2:

[1284] The server formats the collected event information data and stores it in a database such as MySQL or MongoDB. The input is raw event information data, and the output is formatted database entries.

[1285] Step 3:

[1286] The server filters the event information suitable for the user based on the user's profile information and past event participation history. The input is the user's profile information and the event information in the database, and the output is the filtered event information.

[1287] Step 4:

[1288] The server sends filtered event information to the terminal in real time. Here, data can be sent quickly using WebSocket, etc. The input is the filtered event information, and the output is a notification to the terminal that data transmission has been completed.

[1289] Step 5:

[1290] The device notifies the user of the information via push notification or email according to the user's settings. The input is the event information sent from the server, and the output is the notification message sent to the user.

[1291] Providing ticket guides

[1292] Step 1:

[1293] The server collects ticket release dates and purchasing procedures for events and stores them in a database. The input is the URL of the ticket information source, the API key, and the collected ticket information, and the output is the entries stored in the database.

[1294] Step 2:

[1295] A user visits an event details page and requests ticket information. The input is the user's request, and the output is a request sent to the server.

[1296] Step 3:

[1297] The server searches the database for the relevant ticket information and sends it to the terminal. The input is the user's request and the ticket information in the database, and the output is the data sent to the terminal.

[1298] Step 4:

[1299] The terminal displays the ticket information obtained from the server on the user interface (UI). The input is the ticket information sent from the server, and the output is the ticket information displayed on the UI.

[1300] Providing transportation and accommodation information and reservation support

[1301] Step 1:

[1302] The server collects transportation information to the event location and accommodation information around the venue and stores it in a database. The inputs are the sources of the transportation and accommodation information and the collected data, and the output is the entries stored in the database.

[1303] Step 2:

[1304] A user requests transportation and accommodation information. The input is the user request and the output is the submission of the request to the server.

[1305] Step 3:

[1306] The server searches the database for the best transportation and accommodation information and sends it to the terminal. The input is the user's request and the transportation and accommodation information in the database, and the output is the data transmission to the terminal.

[1307] Step 4:

[1308] The information acquired by the device is displayed on the UI, providing reservation support functions. The input is transportation and accommodation information sent from the server, and the output is the information displayed on the UI and a reservation link.

[1309] Schedule planner function

[1310] Step 1:

[1311] A user registers his / her travel itinerary or event schedule in the schedule planner. The input is the itinerary or schedule information entered by the user, and the output is the data sent to the server.

[1312] Step 2:

[1313] The terminal sends the input schedule information to the server. The input is the user's schedule information, and the output is data transmission to the server.

[1314] Step 3:

[1315] The server analyzes the data and calculates the optimal action plan. The input is schedule information and past data, and the output is the action plan as a result of the analysis.

[1316] Step 4:

[1317] The server sends the calculation results to the terminal. The input is the action plan, and the output is the data transmission to the terminal.

[1318] Step 5:

[1319] The terminal presents the action plan to the user. The input is the action plan sent from the server, and the output is the action plan displayed in the UI.

[1320] Community Features

[1321] Step 1:

[1322] The server provides online community functionality, where the input is information for building a community page, and the output is a user-accessible community page.

[1323] Step 2:

[1324] A user accesses a community page and posts or comments. The input is the content of the user's post or comment, and the output is data sent to the server.

[1325] Step 3:

[1326] The server stores the posts in a database. The input is the user's post or comment, and the output is the entry stored in the database.

[1327] Step 4:

[1328] The server makes the posts available for viewing by other users. The input is the saved posts, and the output is the data provided in a viewable form.

[1329] In this way, the system of the present invention comprehensively supports users' participation in events and integrates various functions to provide detailed support according to the user's emotional state.

[1330] (Application example 2)

[1331] Next, a description will be given of Application Example 2. In the following description, the data processing device 12 will be referred to as a "server" and the headset type terminal 314 will be referred to as a "terminal."

[1332] Today's event participants and shoppers demand quick access to a wide variety of information and services. However, with so many information sources and services scattered across multiple platforms, it is difficult for users to obtain a consistent, optimal experience. Furthermore, there is a risk of stress increasing as information is not provided in a way that responds to users' emotions or individual needs. This often leads to dissatisfaction with the event participation or shopping experience.

[1333] The specific processing by the specific processing unit 290 of the data processing device 12 in the application example 2 is realized by the following means.

[1334] In this invention, the server includes means for collecting information on events across the country and notifying users based on their preferences, means for providing and rating ticket sales schedules and purchasing methods, means for providing information on transportation to event locations and accommodations around the venues and supporting reservations, means for proposing an action plan based on the user's itinerary and event schedule, means for providing a community function that allows users with similar goals to interact with each other, means for analyzing the user's emotional state and, based on that, suggesting optimal products and notifying users of promotions, and means for providing navigation within physical stores. This allows users to have a consistently comfortable and satisfying event participation and shopping experience.

[1335] "National event information" refers to data on all events held within the country.

[1336] "Preference-based notification" means a mechanism for selecting and notifying users of relevant event information based on their preferences and interests.

[1337] "Means for providing and rating ticket release schedules and purchasing methods" refers to a system that provides users with information about the release dates and purchasing methods for event tickets, as well as rating information for those tickets.

[1338] "Means of providing information on transportation and accommodation facilities around the venue and supporting reservations" refers to a function that provides information on access to the event venue and information on nearby accommodation facilities and supports reservations for these.

[1339] "A means for proposing an action plan based on the user's itinerary and event schedule" refers to a system that formulates and proposes an optimal action plan based on the user's specified itinerary and the schedule of events they plan to attend.

[1340] "Means for providing community functions" refers to a mechanism for providing functions that allow users with the same goals to interact online.

[1341] "A means of analyzing the user's emotional state and providing optimal product suggestions and promotional notifications based on that" refers to a mechanism that analyzes the user's current emotions and provides appropriate product and promotional information based on the results.

[1342] "A means for providing navigation within a physical store" refers to a system that provides guidance to users to quickly reach a specific location within a physical store.

[1343] The system of the present invention provides a series of support functions to enable users to participate in events and enjoy shopping comfortably and efficiently. This system is composed of a server, a terminal, and an emotion engine. The specific operation of the system and its details are explained below.

[1344] 1. Event information collection and notification

[1345] The server collects event data from external event information sources (official sites, APIs, etc.) and stores it in a database. Based on the user's preferences, the server filters out relevant event information and sends the results to the device. The device then notifies the user of the information via push notification or email according to the user's settings. In addition, the emotion engine analyzes the user's current emotional state and notifies them with appropriate timing and content.

[1346] Example: If a user sets up event information for their favorite artist, the server will automatically send a notification when new event information for that artist is added. If the emotion engine determines that the user's emotional state is "excited," the notification content will be positive.

[1347] 2. Providing ticket guides

[1348] The server stores the ticket sales schedule and purchase method in a database based on the collected event information. When a user views ticket information, the device retrieves the relevant information from the server and displays it on the user interface. The server also evaluates the difficulty of obtaining tickets and provides feedback to the device. The emotion engine adjusts messages to encourage purchases based on the user's emotions.

[1349] Example: When a user checks ticket information on an event's details page, the device displays information from the server, such as the release date, how to purchase, and the difficulty of obtaining tickets. The emotion engine determines the user's emotion as "curiosity" and sends an active message to encourage the purchase.

[1350] 3. Providing transportation and accommodation information and reservation support

[1351] The server collects information on transportation to the event venue and accommodations in the vicinity of the venue and stores it in a database. When a user needs transportation or accommodation information, the device retrieves the optimal options from the server and displays them on the user interface. The device also provides reservation support, allowing users to complete reservations directly. The emotion engine suggests the optimal plan based on the user's emotional state.

[1352] Example: When a user searches for transportation to attend an event, the device retrieves and displays the optimal train and bus information from the server. At the same time, it also displays information about nearby accommodations and provides a reservation link if necessary. If the emotion engine determines that the user is feeling "fatigue," it will prioritize suggestions for comfortable accommodations.

[1353] 4. Schedule planner function

[1354] Users register their travel itinerary and event schedule in the schedule planner. The device sends this to the server, which stores the data in a database and analyzes it. Based on the analysis results, the server calculates an optimal action plan and sends it to the device. The device presents it to the user and helps them participate in events based on that action plan. The emotion engine takes past emotion data into consideration and suggests the most satisfying plan.

[1355] Example: When a user registers their transportation method and arrival time on the day of an event, the server analyzes the information and suggests which transportation method to use and when. If the emotion engine determines that the user's past emotions are "excessive tension," it will recommend a less stressful transportation method.

[1356] 5. Community Features

[1357] The server provides an online community function that allows users to interact with each other. Users can access the community page through their devices and post or comment on the message board. The server stores these posts in a database and makes them available for other users to view. The emotion engine analyzes interactions within the community and prioritizes the display of content that has a positive impact on users' emotions.

[1358] Example: When a user asks for recommendations on restaurants near the venue on a community bulletin board just before an event, other users reply and share the information. The emotion engine performs sentiment analysis and prioritizes positive posts and encouraging content.

[1359] 6. In-store navigation

[1360] The device provides navigation functions to help users quickly find specific products or locations within physical stores, and an emotion engine calculates the optimal route based on the user's emotional state.

[1361] Example: If a user wants to find a specific product quickly, the device will show the shortest route. If the emotion engine determines that the user is feeling "relaxed," the device will guide the user to a scenic route.

[1362] 7. Emotion-based product recommendations and promotions

[1363] The emotion engine analyzes the user's emotional state in real time and suggests optimal products and promotions, which the device notifies the user of, increasing their desire to purchase.

[1364] Example: If a user types "I feel tired today," generate a prompt that prioritizes relaxation products (aromatherapy candles and herbal tea).

[1365] Prompt sentences for AI model generating concrete examples

[1366] "If a user types, 'I feel tired today,' the system should interpret that emotion as 'relaxation' and generate prompts that prioritize relaxation products like scented candles and herbal teas."

[1367] The flow of the specific processing in the application example 2 will be described with reference to FIG.

[1368] Step 1:

[1369] The server collects event data from external event information sources (official sites, APIs, etc.) and stores it in a database. At this time, the server also stores filtering information based on the user's preferences in the database. Event data from external information sources is input, and filtered event data is output and stored in the database. The server also obtains the user's current emotional state from the emotion engine to optimize the timing and content of notifications.

[1370] Step 2:

[1371] When a user uses a device to view event information, the device retrieves the relevant event information from the server and displays it on the user interface. The input is the user's viewing request, and the output is the displayed event information. Furthermore, the emotion engine analyzes the user's current emotional state and adjusts the notification content accordingly. For example, if the user is determined to be "excited," the notification content is adjusted to be more positive.

[1372] Step 3:

[1373] When a user views ticket information, the device retrieves the release schedule, purchase method, and ticket acquisition difficulty from the server and displays these on the user interface. The input is a ticket information request, and the output is detailed ticket information. The emotion engine also analyzes the user's emotions and adjusts messages to encourage purchases. For example, if the user is determined to be "curious," an active message will be displayed to encourage purchase.

[1374] Step 4:

[1375] When a user searches for information on transportation or accommodation, the device retrieves the optimal transportation and accommodation options from the server and displays them on the user interface. The input is a request for transportation or accommodation information, and the output is the display of the optimal options. In addition, an emotion engine analyzes the user's emotional state and suggests optimal plans, such as comfortable accommodation. For example, if the user is determined to be "fatigued," it will prioritize suggestions for comfortable accommodation.

[1376] Step 5:

[1377] When a user registers an itinerary or event schedule in the schedule planner, the device sends it to the server, which then calculates an optimal action plan and sends it to the device. The input is the itinerary or event schedule data, and the output is an optimal action plan. The emotion engine also takes into account past emotion data and suggests plans that will result in high satisfaction. For example, if the user is judged to be "excessively nervous," it will recommend a less stressful mode of transportation.

[1378] Step 6:

[1379] The server provides an online community function that allows users to interact with each other. Users can access the community page via their devices and post or comment. The input is the user's message board posting data, and the output is saved in a form that can be viewed by other users. The emotion engine performs emotion analysis and prioritizes the display of posts that have a positive impact. For example, if a user is judged to be "positive," encouraging posts will be displayed to the front.

[1380] Step 7:

[1381] The device provides navigation functions to help users quickly find specific products or locations within a physical store. The input is the user's destination request, and the output is navigation information to the destination. The emotion engine suggests the optimal route based on the user's emotional state. For example, if the user is judged to be "relaxed," the device will guide them to a scenic route.

[1382] Step 8:

[1383] The emotion engine analyzes the user's emotional state in real time and suggests the most suitable products and promotions. The device notifies the user of this, encouraging them to purchase. The input is the user's emotional data and product information, and the output is product suggestions and promotion information tailored to the emotion. In concrete terms, if the user inputs "I feel tired today," relaxation products will be suggested first.

[1384] Prompt sentences for AI model generating concrete examples

[1385] If the user types "I feel tired today," the system should interpret that emotion as "relaxation" and generate prompts that prioritize relaxation products like scented candles and herbal tea.

[1386] The specific processing unit 290 transmits the result of the specific processing to the headset type terminal 314. In the headset type terminal 314, the control unit 46A causes the speaker 240 and the display 343 to output the result of the specific processing. The microphone 238 acquires audio indicating a user input regarding the result of the specific processing. The control unit 46A transmits audio data indicating the user input acquired by the microphone 238 to the data processing device 12. In the data processing device 12, the specific processing unit 290 acquires the audio data.

[1387] The data generation model 58 is a so-called generative AI (Artificial Intelligence). An example of the data generation model 58 is ChatGPT (Internet Search<URL: https: / / openai.com / blog / chatgpt> ), Gemini (Internet search <url: https: gemini.google.com ?hl="ja">) and other generation AIs. The data generation model 58 is obtained by performing deep learning on a neural network. A prompt including an instruction is input to the data generation model 58, and inference data such as voice data indicating voice, text data indicating text, and image data indicating an image is also input. The data generation model 58 performs inference on the input inference data in accordance with the instruction indicated by the prompt, and outputs the inference result in a data format such as voice data and text data. Here, inference refers to, for example, analysis, classification, prediction, and / or summarization.

[1388] In the above embodiment, an example was given in which the specific processing is performed by the data processing device 12, but the technology of the present disclosure is not limited to this, and the specific processing may be performed by the headset type terminal 314.

[1389] [Fourth embodiment]

[1390] FIG. 7 shows an example of the configuration of a data processing system 410 according to the fourth embodiment.

[1391] 7, a data processing system 410 includes a data processing device 12 and a robot 414. An example of the data processing device 12 is a server.

[1392] The data processing device 12 includes a computer 22, a database 24, and a communication I / F 26. The computer 22 is an example of a "computer" according to the technology of the present disclosure. The computer 22 includes a processor 28, a RAM 30, and a storage 32. The processor 28, the RAM 30, and the storage 32 are connected to a bus 34. The database 24 and the communication I / F 26 are also connected to the bus 34. The communication I / F 26 is connected to a network 54. Examples of the network 54 include a WAN (Wide Area Network) and / or a LAN (Local Area Network).

[1393] The robot 414 includes a computer 36, a microphone 238, a speaker 240, a camera 42, a communication I / F 44, and a control target 443. The computer 36 includes a processor 46, a RAM 48, and a storage 50. The processor 46, the RAM 48, and the storage 50 are connected to a bus 52. The microphone 238, the speaker 240, the camera 42, and the control target 443 are also connected to the bus 52.

[1394] The microphone 238 receives instructions and the like from the user 20 by receiving voice uttered by the user 20. The microphone 238 captures the voice uttered by the user 20, converts the captured voice into audio data, and outputs it to the processor 46. The speaker 240 outputs audio in accordance with instructions from the processor 46.

[1395] Camera 42 is a small digital camera equipped with an optical system including a lens, aperture, and shutter, and an imaging element such as a CMOS (Complementary Metal-Oxide-Semiconductor) image sensor or a CCD (Charge Coupled Device) image sensor, and captures images of the surroundings of user 20 (for example, an imaging range defined by an angle of view equivalent to the field of vision of a typical healthy person).

[1396] The communication I / F 44 is connected to a network 54. The communication I / Fs 44 and 26 are responsible for the exchange of various information between the processor 46 and the processor 28 via the network 54. The exchange of various information between the processor 46 and the processor 28 using the communication I / Fs 44 and 26 is carried out in a secure state.

[1397] The control object 443 includes a display device, LEDs in the eyes, and motors for driving the arms, hands, and feet. The posture and gestures of the robot 414 are controlled by controlling the motors of the arms, hands, and feet. Some of the emotions of the robot 414 can be expressed by controlling these motors. In addition, the facial expressions of the robot 414 can also be expressed by controlling the light emission state of the LEDs in the eyes of the robot 414.

[1398] Fig. 8 shows an example of the main functions of the data processing device 12 and the robot 414. As shown in Fig. 8, in the data processing device 12, a specific process is performed by the processor 28. A specific process program 56 is stored in the storage 32.

[1399] The specific processing program 56 is an example of a "program" according to the technology of the present disclosure. The processor 28 reads the specific processing program 56 from the storage 32 and executes the read specific processing program 56 on the RAM 30. The specific processing is realized by the processor 28 operating as a specific processing unit 290 in accordance with the specific processing program 56 executed on the RAM 30.

[1400] The storage 32 stores a data generation model 58 and an emotion identification model 59. The data generation model 58 and the emotion identification model 59 are used by the identification processing unit 290.

[1401] In the robot 414, the processor 46 performs the reception output process. A reception output program 60 is stored in the storage 50. The processor 46 reads the reception output program 60 from the storage 50 and executes the read reception output program 60 on the RAM 48. The reception output process is realized by the processor 46 operating as the control unit 46A in accordance with the reception output program 60 executed on the RAM 48.

[1402] Next, a description will be given of the specific processing performed by the specific processing unit 290 of the data processing device 12. In the following description, the data processing device 12 will be referred to as a "server" and the robot 414 will be referred to as a "terminal."

[1403] The system of the present invention provides a series of support functions for users to participate in events. Specifically, it includes functions for collecting event information, notifications, ticket guides, providing transportation and accommodation information, schedule planning, and community functions. The operation of this system is explained based on the following main steps.

[1404] Event information collection and notification

[1405] The server collects event data from external event information sources (official sites, APIs, etc.) and stores it in a database. Based on the user's preferences, the server filters the relevant event information and sends the results to the device. The device notifies the user of the information via push notification or email according to the user's settings.

[1406] Example: If a user specifies that they want to see events by a particular artist, the server will automatically notify the user when new events by that artist are added.

[1407] Providing ticket guides

[1408] The server stores the ticket sales schedule and purchase method in a database based on the collected event information. When a user views ticket information, the device retrieves the relevant information from the server and displays it on the user interface. In addition, the server evaluates the difficulty of obtaining tickets and sends feedback to the device.

[1409] Example: When a user checks ticket information on an event's details page, the device displays information from the server about the release date, how to purchase, and how easy it is to obtain tickets.

[1410] Providing transportation and accommodation information and reservation support

[1411] The server collects information on transportation to the event venue and accommodation options around the venue and stores it in a database. When a user needs transportation or accommodation information, the terminal retrieves the optimal transportation and accommodation options from the server and displays them on the user interface. In addition, the terminal provides reservation support functions, allowing users to complete reservations directly.

[1412] Example: When a user searches for transportation to an event, the device retrieves and displays the most suitable train and bus information from the server. At the same time, it also displays information about nearby accommodations and provides a reservation link if necessary.

[1413] Schedule planner function

[1414] Users register their travel itineraries and event schedules in the schedule planner. The device sends this information to the server, which stores it in a database and analyzes it. Based on the analysis results, the server calculates an optimal action plan and sends it to the device. The device then presents it to the user and helps them participate in events based on that action plan.

[1415] Example: When a user registers the mode of transportation and arrival time for the day of an event in their schedule planner, the server analyzes this and suggests which mode of transportation to use at what time.

[1416] Community Features

[1417] The server provides an online community function that allows users to interact with each other. Users can access the community page through their devices and post or comment on the message board. The server stores these posts in a database and makes them available to other users.

[1418] Example: A user asks on a community message board for recommendations on restaurants near the venue just before an event, and other users reply and share that information.

[1419] As described above, the system of the present invention streamlines the series of procedures required to participate in an event and provides optimal support to users. This system allows users to smoothly complete all processes, including information gathering, ticket purchase, transportation and accommodation arrangements, schedule management, and community participation.

[1420] The processing flow will be explained below.

[1421] Step 1:

[1422] The user enters information into the new registration form. The user enters their name, email address, password, etc. on the device and presses the registration button.

[1423] Step 2:

[1424] The device sends registration information to the server. The front end sends a POST request to the backend API, sending user information to the server.

[1425] Step 3:

[1426] The server saves the user information in the database. The server receives the user information, validates it (checks for format and duplication), and saves it in the database. After saving, a confirmation email is sent to the user.

[1427] Step 4:

[1428] The user receives a confirmation email and activates the account. The user opens the confirmation email and clicks the link to activate the account.

[1429] Step 5:

[1430] The server confirms the account activation. The server receives the link click, updates the account status in the database to activated, and notifies the user that activation is complete.

[1431] Step 6:

[1432] A user opens the event listing page. A user opens the event listing page on their device.

[1433] Step 7:

[1434] The device requests the latest event information from the server. The front end sends a GET request to the back end API to obtain the latest event information.

[1435] Step 8:

[1436] The server retrieves event information from the database. The server searches for the necessary event information from the database and returns it in JSON format.

[1437] Step 9:

[1438] The terminal displays the event information. The front end parses the received JSON data and displays the event information in the user interface.

[1439] Step 10:

[1440] The user sets notification settings. The user turns on notification settings for specific idle times.

[1441] Step 11:

[1442] The device sends the notification settings to the server. The front end sends a PUT request to the backend API to update the notification settings.

[1443] Step 12:

[1444] The server saves the notification settings in the database. The server saves the notification settings it receives in the database.

[1445] Step 13:

[1446] User selects a specific event and opens the details page. User visits the event details page on their device to view more information.

[1447] Step 14:

[1448] The terminal requests ticket information from the server. The front end sends a GET request to the backend API to obtain the ticket information.

[1449] Step 15:

[1450] The server retrieves ticket information from the database. The server searches the database for ticket information based on the event ID and returns it in JSON format.

[1451] Step 16:

[1452] The terminal displays the ticket information. The front-end parses the received JSON data and displays the ticket information on the page.

[1453] Step 17:

[1454] The user purchases a ticket. The user presses the ticket purchase button to begin the purchase process.

[1455] Step 18:

[1456] The terminal sends a purchase request to the server. The front end sends a POST request to the backend API to complete the purchase.

[1457] Step 19:

[1458] The server sends a request to the payment service. The server sends a request to the external payment service to process the payment.

[1459] Step 20:

[1460] The server receives the payment result and updates the database. If the payment is successful, the server saves the purchase data in the database and sends a confirmation email to the user.

[1461] Step 21:

[1462] The user plans their trip, using the in-app schedule planner to select transportation and accommodations.

[1463] Step 22:

[1464] The terminal sends the schedule information to the server. The front end sends a POST request to the backend API to send the schedule information to the server.

[1465] Step 23:

[1466] The server calculates the optimal itinerary and saves it in the database.The server calculates the optimal itinerary based on the schedule information and saves it in the database.

[1467] Step 24:

[1468] A user opens the community page. A user accesses the community page on their device and browses the message board.

[1469] Step 25:

[1470] The terminal requests bulletin board information from the server. The front end sends a GET request to the back end API to retrieve the bulletin board information.

[1471] Step 26:

[1472] The server retrieves bulletin board information from the database. The server searches the bulletin board information from the database and returns it in JSON format.

[1473] Step 27:

[1474] The terminal displays the message board information. The front end parses the received JSON data and displays the message board information on the page.

[1475] Step 28:

[1476] A user posts: A user creates a new post on the message board and presses the send button.

[1477] Step 29:

[1478] The device sends the post content to the server. The front end sends a POST request to the backend API, sending the new post to the server.

[1479] Step 30:

[1480] The server saves the posted content in a database. The server saves the posted content received in a database and updates the bulletin board information.

[1481] Example 1

[1482] Next, a description will be given of Example 1. In the following description, the data processing device 12 will be referred to as a "server" and the robot 414 will be referred to as a "terminal."

[1483] In the past, gathering information, purchasing tickets, and arranging transportation and accommodation to participate in an event required time and effort, placing a burden on users. Furthermore, the management of event information and participation plans was dispersed, making it difficult to participate in events efficiently. Furthermore, opportunities to share information through interactions with other participants were limited.

[1484] The specific processing by the specific processing unit 290 of the data processing device 12 in the first embodiment is realized by the following means.

[1485] In this invention, the server includes: means for collecting event information from across the country and notifying users based on their preferences; means for providing and rating ticket sales schedules and purchasing methods; means for providing information on transportation to event locations and accommodations near the venues and supporting reservations; means for suggesting an action plan based on the user's itinerary and event schedule; means for providing a community function that allows users with similar interests to interact with each other; means for periodically collecting event information from external sources and storing it in a database; means for filtering the information based on the database and notifying users of the most appropriate event information via push notification or email; and means for calculating the difficulty of obtaining tickets and providing the information to users. This allows users to efficiently collect event information and smoothly purchase tickets and make arrangements for transportation and accommodation. Users can also obtain more information by interacting with other participants.

[1486] "National event information" refers to information about events of various genres held throughout the country, not limited to a specific region.

[1487] "Notifying based on user preferences" means selecting and notifying the user of relevant event information based on the user's pre-defined interests and preferences.

[1488] "Providing and evaluating ticket release schedules and purchasing methods" means providing information about when event tickets go on sale and how to purchase them, and based on that information evaluating the difficulty and convenience of obtaining tickets and communicating that information to users.

[1489] Providing "information on transportation to the event venue and accommodations in the vicinity" and supporting reservations means providing information on transportation and accommodations for users to attend the event, and supporting the reservation process.

[1490] "Suggesting an action plan based on the user's itinerary and event schedule" means calculating and suggesting an optimal action plan to the user based on the event dates and transportation details entered by the user.

[1491] "Providing a community function that allows users with the same goals to interact with each other" means providing an online platform where event participants can share information, exchange opinions, and ask questions.

[1492] "Regularly collect from external sources and store in a database" means periodically obtaining event information from reliable external sources such as official websites and APIs and storing it in a database.

[1493] "Filtering based on a database" means sorting stored event information based on user settings and preferences.

[1494] "Notifying users of the most appropriate event information via push notification or email" means notifying users directly of filtered event information in a manner that suits their settings.

[1495] "Calculating the difficulty of obtaining tickets" means assessing the difficulty of obtaining event tickets based on past data and current demand, and providing this to users.

[1496] The system of this invention provides a series of support functions for users to participate in events. Specifically, it provides a comprehensive range of functions, including event information collection, notification, ticket guide, transportation and accommodation information, schedule planner, and community functions. To realize the operation of this system, the server, terminals, and users each play different roles.

[1497] First, the server periodically retrieves event data from external event information sources (such as official event websites or APIs). The collected data is stored in a database containing information such as the event name, date and time, location, and details. For example, a library such as the Apache HTTP client can be used to collect the information.

[1498] When a user logs in to the system and selects the genres and artists they are interested in, the server filters the relevant event information from the database based on the user's preferences. This filtering is done using database queries and stored procedures. The filtered results are sent to the device, which then notifies the user via push notification or email.

[1499] For example, if a user specifies that they want to receive notifications for events by a specific artist, the server will automatically notify the user when new events for that artist are added. An example of a prompt would be, "How do I set up notifications for events by a specific artist?"

[1500] Next, when a user views an event's details page, the device requests ticket information for that event from the server. The server retrieves ticket information (release date, price, purchase method, etc.) from the database and returns it to the device. The server then calculates the difficulty of obtaining tickets using past sales data and a demand forecasting algorithm, and sends feedback to the device.

[1501] For example, when a user checks ticket information on an event's details page, the device displays information from the server about the release date, how to purchase, and the difficulty of obtaining tickets. An example of a prompt sentence is, "Please tell me how to rate the difficulty of obtaining tickets for an event."

[1502] The server also retrieves information about transportation options to the event location (trains, buses, taxis, etc.) and accommodations near the venue from travel APIs and hotel booking site APIs, and stores this information in a database. When a user needs this information, the device retrieves the optimal options from the server and presents them to the user. Users can then use the reservation support function to complete their reservations directly.

[1503] For example, when a user searches for transportation, the device retrieves and displays the best transportation options from the server. Similarly, it displays accommodation information and provides a booking link if necessary. An example of a prompt is, "How do I search for transportation and accommodation information for an event?"

[1504] With the schedule planner function, users can register their event schedules. The device then sends the schedules to the server, which stores them in a database and analyzes them. Based on the analysis results, the server calculates an optimal action plan and sends it to the device. Users can then act accordingly.

[1505] For example, when a user enters information into a schedule planner, the server suggests which means of transportation to use at which time. An example of a prompt sentence is, "Please tell me how to calculate the optimal itinerary by entering the mode of transportation and arrival time on the day of the event."

[1506] Finally, the server provides an online community function that allows users to interact with each other. Users can access the community page through their devices and post or comment on the message board. The server stores these posts in a database and makes them available to other users.

[1507] For example, if a user asks for information about restaurants near the venue on a community bulletin board just before an event, other users will reply and share that information. An example of a prompt sentence is, "Please tell me how to ask for recommended restaurant information on a community bulletin board just before an event."

[1508] As described above, the system streamlines the entire process for users to participate in events efficiently and provides a wealth of information and support.

[1509] The flow of the identification process in the first embodiment will be described with reference to FIG.

[1510] Step 1: Gather event information

[1511] The server periodically collects event data from external event information sources (e.g., official event websites, APIs, etc.). Specifically, the server sends API requests, parses the returned data in JSON format, and stores it in a database.

[1512] Input: API request from external information source

[1513] Output: Parsed event data stored in a database

[1514] Step 2: Filtering event information

[1515] When a user logs into the system and selects the genres and artists they are interested in, the server uses a database query to filter relevant event information from the database based on the user's preferences.

[1516] Input: User interests and preferences

[1517] Output: Filtered event information

[1518] Step 3: Event information notification

[1519] The filtered event information is sent to the device, and the device notifies the user via push notification or email, depending on the user settings.

[1520] Input: Filtered event information

[1521] Output: Push notification and email notification

[1522] Step 4: Get ticket information

[1523] When a user views an event's details page, the device requests ticket information for that event from the server. The server retrieves ticket information (release date, price, purchase method, etc.) from the database and returns that information to the device.

[1524] Input: Ticket information request from user

[1525] Output: Retrieved ticket information

[1526] Step 5: Calculating ticket difficulty

[1527] The server calculates the difficulty of obtaining tickets using past sales data and demand forecasting algorithms, and provides this information to users via their devices.

[1528] Input: Past sales data, demand data

[1529] Output: Ticket acquisition difficulty rating

[1530] Step 6: Providing transportation and accommodation information

[1531] When a user searches for transportation or accommodation information for an event, the device sends a request to the server, which returns the best options to the user based on information retrieved from travel APIs and hotel booking site APIs.

[1532] Input: User request for transportation and accommodation information

[1533] Output: Best transportation and accommodation information

[1534] Step 7: Schedule Planner

[1535] Users register their event participation schedule in the schedule planner. The device sends this to the server, which stores it in a database and analyzes it. The optimal action plan is calculated and provided to the user via the device.

[1536] Input: User's schedule information

[1537] Output: Optimal action plan

[1538] Step 8: Community Features

[1539] Users can access the community page through their devices and post or comment on the message board. The server stores these posts in a database and makes them available to other users.

[1540] Input: User posts and comments

[1541] Output: Saved posts, comments displayed

[1542] (Application example 1)

[1543] Next, a description will be given of Application Example 1. In the following description, the data processing device 12 will be referred to as a "server" and the robot 414 will be referred to as a "terminal."

[1544] Currently, when users participate in a virtual event, they must use multiple methods, such as gathering event information, purchasing tickets, checking access methods, managing schedules, and interacting with the community, which takes a lot of time and effort.In addition, access guides and real-time event information updates, which are specific to virtual events, are often not provided sufficiently.

[1545] The specific processing by the specific processing unit 290 of the data processing device 12 in the application example 1 is realized by the following means.

[1546] In this invention, the server includes means for collecting information on events across the country and notifying users based on their preferences, means for providing and rating ticket sales schedules and purchasing methods, means for providing access methods to the event location or virtual event venue and information on nearby accommodations and supporting reservations, means for proposing an action plan based on the user's itinerary and event schedule, means for providing a community function that allows users with the same goals to interact with each other, and means for providing a guide to accessing the virtual venue.This significantly reduces the effort and time required for users to participate in virtual events, allowing them to enjoy the event more smoothly.

[1547] "Collecting event information nationwide" means gathering data on various events across the country.

[1548] "Providing notifications based on user preferences" means notifying users of appropriate event information based on the interests and concerns they have set.

[1549] "Providing and evaluating ticket release schedules and purchasing methods" means providing information about the sale period and purchasing methods of event tickets and evaluating the difficulty of obtaining them.

[1550] "How to access the event location or virtual event venue" means directions to the physical location where the event is being held or how to access the online virtual space.

[1551] "Providing information about nearby accommodations and supporting reservations" means providing information about accommodations near the venue and helping people make reservations.

[1552] "Suggesting an action plan based on the user's itinerary and event schedule" means proposing the optimal action plan based on the schedule of events and plans set by the user.

[1553] "Providing a community function that allows users with the same goals to interact with each other" means providing a function that allows users with common interests and goals to exchange opinions and share information.

[1554] "Providing a guide to accessing the virtual venue" means providing instructions and procedures for accessing the virtual space where the event will be held online.

[1555] "Push notifications about specific events and areas of interest based on user preferences" means providing real-time notifications about relevant events and areas of interest based on user-specified preferences.

[1556] The present invention is a system that comprehensively supports users' participation in events, and includes the following configuration and operation.

[1557] Event information collection and notification

[1558] The server collects event data from external event information sources (such as official websites and APIs) and stores it in a database. Based on the user's preferences, the server filters the relevant event information and sends the results to the device. The device then notifies the user of the information via push notifications or emails, depending on the user's settings.

[1559] For example, if a user specifies that they want to see events by a particular artist, the server will collect event information for that artist and automatically send notifications.

[1560] Providing ticket guides

[1561] The server stores the ticket sales schedule and purchase method in a database based on the collected event information. When a user views ticket information, the device retrieves the relevant information from the server and displays it on the user interface. The server also evaluates the difficulty of obtaining tickets and sends the evaluation results to the device.

[1562] For example, when a user checks ticket information on an event's details page, the device displays information from the server about the release date, how to purchase tickets, and how difficult it is to obtain tickets.

[1563] Providing transportation and accommodation information and reservation support

[1564] The server collects information on how to access the event venue or virtual event venue and accommodation information around the venue and stores it in a database. When a user needs transportation or accommodation information, the terminal retrieves the optimal transportation and accommodation options from the server and displays them on the user interface. In addition, the terminal provides reservation support functions, allowing users to complete reservations directly.

[1565] For example, when a user searches for transportation to an event, the device retrieves the optimal transportation and accommodation information from the server and displays it, and also provides a reservation link if necessary.

[1566] Schedule planner function

[1567] Users register their travel itineraries and event schedules in the schedule planner. The device sends this information to the server, which stores it in a database and analyzes it. Based on the analysis results, the server calculates an optimal action plan and sends it to the device. The device then presents it to the user and helps them participate in events based on that action plan.

[1568] As a concrete example, when a user registers the mode of transportation and arrival time for the day of the event in their schedule planner, the server analyzes this and suggests which mode of transportation to use at what time.

[1569] Community Features

[1570] The server provides an online community function that allows users to interact with each other. Users can access the community page through their devices and post or comment on the message board. The server stores these posts in a database and makes them available to other users.

[1571] For example, if a user asks on a community bulletin board for information about recommended restaurants near the venue just before an event, other users will reply and share that information.

[1572] Virtual Venue Access Guide

[1573] For virtual events, the server provides information on how to access the online event venue and the necessary procedures, allowing users to easily access the virtual venue through their devices and smoothly participate in the event.

[1574] For example, when a user wants to join a virtual event, the server provides an access link and connection instructions to the virtual venue, facilitating the process for the user.

[1575] Prompt Sentence Examples

[1576] "Tell me about the event. The artist you're interested in is 'The Beatles.'"

[1577] As described above, the present invention provides a system that comprehensively supports all procedures related to event participation and places little burden on users.

[1578] The flow of the specific processing in the application example 1 will be described with reference to FIG.

[1579] Step 1:

[1580] The server collects event data from external event information sources (official sites, APIs, etc.) and stores it in a database. The input includes the URL of the event information source and authentication information such as an API key. This allows the server to obtain new event information and create a database entry to store it. The output is the stored event information.

[1581] Step 2:

[1582] If a user is interested in events by a specific artist or genre, that information is set on the device. The input includes a prompt about the user's interests, such as "Tell me about the event. The artist I'm interested in is The Beatles." The device then saves the user's settings. The output is the user's interest information.

[1583] Step 3:

[1584] The server filters the collected event information based on the user's preferences. The input includes the user's preference settings and the event information in the database. The server then selects the relevant event information and sends it to the terminal. The output is the filtered event information.

[1585] Step 4:

[1586] The device notifies the user of the event information received from the server via push notification or email. The input includes filtered event information. This allows the device to notify the user of events of interest in real time. The output is a notification to the user.

[1587] Step 5:

[1588] The server collects event ticket information (release date, purchase method, difficulty of obtaining tickets, etc.) and stores it in a database. The input includes event information and related ticket sales information, which allows the server to provide detailed ticket information. The output is the stored ticket information.

[1589] Step 6:

[1590] When a user views ticket information for an event, the device retrieves the relevant information from the server and displays it on the user interface. The input includes the ID and keywords of the event that the user is interested in. This allows the device to provide detailed ticket information to the user. The output is the ticket information displayed on the screen.

[1591] Step 7:

[1592] The server collects access and accommodation information for the event location or virtual event venue and stores it in a database. Inputs include the location of the event venue and the URL of the virtual room, which enables the server to provide access and accommodation information to users. Outputs include the stored access and accommodation information.

[1593] Step 8:

[1594] When a user searches for transportation or accommodation information, the device retrieves the best options from the server and displays them in the user interface. The input includes the user's search query, which enables the device to provide the best transportation and accommodation information. The output is the recommended transportation and accommodation options for the user.

[1595] Step 9:

[1596] Users register their travel and event schedules in the schedule planner. The input includes details such as the event time, location, transportation, and arrival time. The device then saves and manages the user's schedule. The output is the registered schedule information.

[1597] Step 10:

[1598] The server analyzes the user's schedule, calculates the optimal action plan, and sends it to the terminal. The input includes the user's schedule information and event information. The server calculates the optimal action plan and presents it to the user. The output is the calculated action plan.

[1599] Step 11:

[1600] The server provides an online community where users can interact with each other and allows access to its functionality through the device. Input includes user posts and comments. The server then stores the posts in a database for other users to view. Output is the stored posts.

[1601] Step 12:

[1602] In the case of a virtual event, the server provides the user with access instructions and procedures to the virtual venue and guides them through the terminal. The input includes access information for the virtual venue, which allows the server to smoothly participate in the virtual event. The output is the provided access information.

[1603] Furthermore, an emotion engine that estimates the user's emotion may be further combined. That is, the identification processing unit 290 may estimate the user's emotion using the emotion identification model 59, and perform identification processing using the user's emotion.

[1604] The system of the present invention provides a series of support functions for users to participate in events. Specifically, it includes functions for collecting event information, notifications, ticket guides, providing transportation and accommodation information, schedule planners, and community functions. It also incorporates an emotion engine that recognizes the user's emotions and provides optimal services according to their emotional state. The operation of this system is explained based on the following main steps.

[1605] Event information collection and notification

[1606] The server collects event data from external event information sources (official sites, APIs, etc.) and stores it in a database. Based on the user's preferences, the server filters the relevant event information and sends the results to the device. The device notifies the user of the information via push notification or email according to the user's settings.

[1607] Furthermore, the emotion engine analyzes the user's current emotional state and delivers notifications with appropriate timing and content. For example, if the user is feeling stressed, notifications of events that will help them relax will be prioritized.

[1608] Example: If a user specifies that they want to see events by a specific artist, the server will automatically notify the user when new event information for that artist is added. If the emotion engine determines that the user's emotional state is "excited," the notification content will be bright and positive.

[1609] Providing ticket guides

[1610] The server stores the ticket sales schedule and purchase method in a database based on the collected event information. When a user views ticket information, the device retrieves the relevant information from the server and displays it on the user interface. The server also evaluates the difficulty of obtaining tickets and sends feedback to the device. The emotion engine adjusts messages to encourage purchases based on the user's emotions.

[1611] Example: When a user checks ticket information on an event's details page, the device displays information from the server about the release date, how to purchase, and the difficulty of obtaining tickets. The emotion engine determines the user's emotion as "curiosity" and displays an active message encouraging them to purchase.

[1612] Providing transportation and accommodation information and reservation support

[1613] The server collects information on transportation to the event venue and accommodation options around the venue and stores it in a database. When a user needs transportation or accommodation information, the device retrieves the optimal transportation and accommodation options from the server and displays them on the user interface. In addition, the device provides reservation support, allowing users to complete reservations directly. The emotion engine suggests the optimal plan based on the user's emotional state.

[1614] Example: When a user searches for transportation to attend an event, the device retrieves and displays information on the most suitable train or bus from the server. At the same time, it also displays information on nearby accommodations and provides a reservation link if necessary. If the emotion engine determines that the user is feeling "fatigue," it will prioritize suggestions for comfortable accommodations.

[1615] Schedule planner function

[1616] Users register their travel itineraries and event schedules in the schedule planner. The device sends this information to the server, which stores it in a database and analyzes it. Based on the analysis results, the server calculates an optimal action plan and sends it to the device. The device presents it to the user and helps them participate in events based on that action plan. The emotion engine takes into account the user's past emotional data and suggests the most satisfying plan.

[1617] Example: When a user registers their transportation method and arrival time for the day of an event in their schedule planner, the server analyzes this and suggests which transportation method to use at which time. If the emotion engine determines that the user's past emotional data indicates "excessive tension," it will recommend a less stressful transportation method.

[1618] Community Features

[1619] The server provides an online community function that allows users to interact with each other. Users can access the community page through their devices and post or comment on the message board. The server stores these posts in a database and makes them available for other users to view. The emotion engine analyzes interactions within the community and prioritizes displaying content that has a positive impact on users' emotions.

[1620] Example: When a user asks for recommendations on restaurants near the venue on a community message board just before an event, other users reply and share that information. The emotion engine performs sentiment analysis and prioritizes positive posts and encouraging content.

[1621] As described above, the system according to the present invention provides optimal support according to the user's emotional state by incorporating an emotion engine in addition to conventional functions, thereby enabling the user to participate in events in a more comfortable and satisfying way.

[1622] The processing flow will be explained below.

[1623] Step 1:

[1624] The user enters information into the new registration form. The user enters their name, email address, password, etc. on the device and presses the registration button.

[1625] Step 2:

[1626] The device sends registration information to the server. The front end sends a POST request to the backend API, sending user information to the server.

[1627] Step 3:

[1628] The server saves the user information in the database. The server receives the user information, validates it (checks for format and duplication), and saves it in the database. After saving, a confirmation email is sent to the user.

[1629] Step 4:

[1630] The user receives a confirmation email and activates the account. The user opens the confirmation email and clicks the link to activate the account.

[1631] Step 5:

[1632] The server confirms the account activation. The server receives the link click, updates the account status in the database to activated, and notifies the user that activation is complete.

[1633] Step 6:

[1634] A user opens the event listing page. A user opens the event listing page on their device.

[1635] Step 7:

[1636] The device requests the latest event information from the server. The front end sends a GET request to the back end API to obtain the latest event information.

[1637] Step 8:

[1638] The server retrieves event information from the database. The server searches for the necessary event information from the database and returns it in JSON format.

[1639] Step 9:

[1640] The terminal displays the event information. The front end parses the received JSON data and displays the event information in the user interface.

[1641] Step 10:

[1642] Users can set notification preferences. Users can turn on notification preferences for specific idols and events.

[1643] Step 11:

[1644] The device sends the notification settin...

Claims

1. A means of collecting information on events across the country and sending notifications based on user preferences; A means of providing and evaluating ticket release schedules and purchasing methods, and Providing information on transportation to the event venue and accommodations around the venue, and assisting with reservations; A means to suggest action plans based on the user's itinerary and event schedule, A means to provide a community function where users with the same goals can interact with each other, A system including:

2. 10. The system of claim 1, wherein the collected event information is stored in a database and updated in real time.

3. The system of claim 1 , wherein the notification function pushes notifications about specific events or areas of interest based on user settings.

Images