System
The system addresses ticket purchasing challenges by allowing users to input event details, automatically search and purchase tickets with notifications, and prevent resale, ensuring easy and fair ticket acquisition.
Patent Information
- Application Number
- JP2024123951
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2024-07-30
- Publication Date
- 2026-02-12
AI Technical Summary
Users often miss out on purchasing event tickets due to unawareness of event dates and sales periods, and tickets for popular events are frequently bought by scalpers and resold at inflated prices, creating a complex ticket purchasing and resale problem.
A system that allows users to input event names or keywords, automatically searches for event information, sends notifications when tickets go on sale, confirms purchase intentions, automatically purchases tickets, and provides them in an electronic format with resale restrictions.
Enables users to easily obtain tickets for desired events without missing out and prevents resale, ensuring fair pricing and efficient ticket acquisition.
Smart Images

Figure 2026022434000001_ABST
Abstract
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] When purchasing event tickets, users often miss out on purchasing tickets because they are unaware of the dates and sales periods of the events they want. Another serious problem is that tickets to popular events are purchased in bulk by scalpers and then resold at unreasonably high prices. There is a need to solve these complex ticket purchasing and resale problems and provide an environment where users can purchase tickets easily and fairly. [Means for solving the problem]
[0005] The present invention is a system that includes a means for inputting an event name or keyword of interest, a means for searching for event information based on the input event name or keyword, a means for sending a notification when tickets for an event included in the searched event information go on sale, a means for confirming the purchase intention of the user who received the notification, a means for automatically purchasing tickets after confirming the purchase intention, and a means for providing purchased tickets in an electronic format with a restriction that they cannot be resold. This allows users to easily obtain tickets for their desired events without missing out and also solves the problem of resale.
[0006] "Event name or keyword" is a character string that a user enters to identify an event in which the user is interested.
[0007] "Event information" refers to information about the event's dates, location, and ticket sales, searched based on the event name or keywords entered.
[0008] "Notification" means an alert or message sent to a User when tickets go on sale.
[0009] "Purchase request" is an operation by which a user indicates their intention to purchase a ticket after receiving a notification.
[0010] The "means for automatically purchasing tickets" is a program or system that uses the necessary information to purchase tickets based on the user's purchase wishes.
[0011] "Electronic Format" means the format in which a purchased ticket is stored and displayed digitally.
[0012] "No Resale Restrictions" means technological measures or restrictions that prevent a purchased electronic ticket from being sold or transferred to another person. [Brief explanation of the drawings]
[0013] [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
[0014] 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.
[0015] First, the terms used in the following description will be explained.
[0016] 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).
[0017] 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.
[0018] 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.
[0019] 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.
[0020] 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."
[0021] [First embodiment]
[0022] FIG. 1 shows an example of the configuration of a data processing system 10 according to the first embodiment.
[0023] 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.
[0024] 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).
[0025] 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.
[0026] 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.
[0027] 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.
[0028] 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.
[0029] FIG. 2 shows an example of the main functions of the data processing device 12 and the smart device 14.
[0030] 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.
[0031] 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.
[0032] 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.
[0033] 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."
[0034] The system of the present invention is an automated ticket purchasing system that allows users to easily obtain tickets for events of interest and simultaneously solves the problem of ticket resale. This system operates using a user terminal, a server, and a generation AI. Specific embodiments are described below.
[0035] 1. User event registration
[0036] The user inputs the event name or keyword of interest into the user terminal, via an application or a web interface.
[0037] The terminal transmits the input event name and keywords to the server.
[0038] 2. Event information monitoring
[0039] The server stores the received event names and keywords in a database.
[0040] The server uses generative AI to periodically search the web and social networking services (SNS) to find ticket sales information for the event.
[0041] 3. Sending notifications
[0042] If the server detects relevant ticket sales information, it sends a push notification to the user's device, letting the user know that tickets for the event are now on sale.
[0043] 4. Ticket purchase confirmation and automatic purchase
[0044] The user receives the notification and performs an operation to confirm the purchase request, for example, by clicking the "Request to Purchase" button in the notification.
[0045] The terminal transmits the user's purchase request to the server, which then initiates the purchase procedure.
[0046] The server uses pre-saved user information (such as name and credit card information) to access the designated ticket purchasing site and automatically complete the purchase procedure.
[0047] 5. Ticket issuance and anti-resale measures
[0048] After the purchase process is completed, the server generates an electronic ticket, which includes a restriction that prohibits resale.
[0049] The server transmits the generated electronic ticket to the user terminal.
[0050] The terminal stores the received electronic ticket in the user's account so that it can be displayed as needed.
[0051] Specific examples
[0052] 1. User registration and notification flow
[0053] A user is interested in "Rock Festival 2024" and enters the event name "Rock Festival 2024" into the application.
[0054] The terminal sends the entered information to the server, which stores the event name in a database.
[0055] The server uses generative AI to periodically search the web and social media for information on "Rock Festival 2024 ticket sales."
[0056] When sales information is detected, the server sends a notification to the device, which includes the date and time the sale starts and a URL.
[0057] 2. Automating ticket purchasing
[0058] The user receives the notification, checks the details, and then clicks a button to select their purchase.
[0059] The terminal transmits a purchase request to the server, and the server accesses the ticket purchase site.
[0060] The server automatically fills in the purchase form using pre-stored user information (name, credit card information) and completes the purchase process.
[0061] 3. Issuance and provision of tickets
[0062] The server generates the ticket in electronic format immediately upon purchase and includes a no-resale restriction.
[0063] The server sends the generated ticket to the terminal, which stores it in the user's account for viewing.
[0064] This allows users to easily obtain tickets for the events they want and also prevents the problem of resale.
[0065] The processing flow will be explained below.
[0066] Step 1:
[0067] A user launches the application and enters the name of an event or keyword they are interested in, for example, "Rock Festival 2024."
[0068] Step 2:
[0069] The device sends the input event name and keywords to the server. The transmitted data includes the event name, such as "Rock Festival 2024."
[0070] Step 3:
[0071] The server stores the received event names and keywords in a database, then starts the generation AI, which periodically searches for related event information from the web and social media.
[0072] Step 4:
[0073] The server collects relevant event information from the search results, such as "Ticket sales for Rock Festival 2024 have begun."
[0074] Step 5:
[0075] The server then sends a push notification to the device based on the collected information, including the date and time when tickets for the event go on sale and the URL where they can be purchased.
[0076] Step 6:
[0077] The user checks the notification received on the device, confirms the details of the event, and clicks the "Purchase" button to select whether they wish to purchase the item.
[0078] Step 7:
[0079] The terminal transmits the user's purchase request to the server, which includes information such as "Event name: Rock Festival 2024" and "Purchase request: Yes."
[0080] Step 8:
[0081] When the server receives the purchase request, it uses the pre-stored user information to access the specified ticket purchase site, for example, "https: / / example.com / ticket-purchase."
[0082] Step 9:
[0083] The server automatically fills in the necessary information (such as name and credit card information) on the purchase site form, which is provided by the user in advance.
[0084] Step 10:
[0085] The server executes the purchase process and receives a success notification, such as a message saying "ticket purchase successful."
[0086] Step 11:
[0087] Once the purchase is complete, the server generates the ticket in electronic format, with a no-resale restriction attached to the ticket.
[0088] Step 12:
[0089] The server then sends the generated electronic ticket to the terminal, which includes data such as "Electronic ticket ID: 987654321" and "Not for resale."
[0090] Step 13:
[0091] The device stores the received e-ticket in the user's account and makes it available for viewing as needed. The user can view the ticket within the application.
[0092] By following these steps, users can easily and reliably obtain tickets to events they are interested in, while also preventing the problem of resale.
[0093] Example 1
[0094] 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."
[0095] When purchasing event tickets, it is important to ensure that users can quickly and accurately obtain tickets for their desired event while preventing the problem of resale. In particular, tickets for popular events tend to sell out quickly, and resellers often buy up all the tickets, making it difficult for ordinary users to purchase them at the regular price. Furthermore, manually gathering information on the Internet is time-consuming and inefficient.
[0096] 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.
[0097] In this invention, the server includes means for inputting an event name or keyword of interest, means for searching for event information based on the input event name or keyword, means for sending a notification when tickets for the event included in the searched event information go on sale, means for confirming a purchase intention of a user who received the notification, means for automatically purchasing tickets after confirming the purchase intention, means for providing the purchased tickets in an electronic format with a no-resale restriction, and means for periodically searching the web and social networking services using a generative language model. This allows users to efficiently obtain tickets for desired events and prevents resale problems.
[0098] "Means for inputting event names and keywords of interest" refers to an interface that allows users to input into a terminal the names of events that they are interested in or wish to participate in, as well as related keywords.
[0099] "Means for searching event information" refers to software and algorithms for retrieving related information from websites and social networking services on the Internet based on the event name or keywords entered.
[0100] "Means for sending notifications" refers to push notifications or message sending functions that notify user devices that tickets for an event are on sale.
[0101] "Means for confirming purchase intention" refers to the interface that allows the user to perform an operation to indicate their intention to purchase a ticket in response to the notification they received, and the function that receives and processes this information.
[0102] "Means for automatically purchasing tickets" refers to software and algorithms that, after confirming a user's purchase request, access a designated ticket purchasing site using pre-saved user information, automatically input and submit the necessary information to make the purchase.
[0103] "Means for adding a restriction that prevents resale and providing it in electronic format" refers to the function of adding a restriction that prevents resale of a ticket after purchase, generating it as an electronic ticket, and providing it to the user's terminal.
[0104] "Means for searching using generative language models" refers to the ability to utilize generative AI models to periodically extract and analyze event ticket sales information from large datasets using natural language processing techniques.
[0105] The system of the present invention is an automatic purchasing system that allows users to easily obtain tickets for events they are interested in, while at the same time solving the problem of ticket resale. This system is built using a user terminal, a server, and a generative language model.
[0106] First, a user uses their device to enter the name of an event or keywords they are interested in, such as "Rock Festival 2024," using a smartphone application or web browser. This entry is made through the device's interface, and the information is sent to the server using the HTTPS protocol.
[0107] The server then stores the received event names and keywords in a relational database (e.g., MySQL). The stored data is then used to search for relevant information from websites and social networking services (SNS) on the Internet using a generative AI model (e.g., OpenAI GPT-4) running on the server. This search is performed periodically and uses APIs for web search (e.g., Google Custom Search API) and APIs for SNS (e.g., Twitter API).
[0108] The server analyzes the search results, and when it detects ticket sales information related to a specific event, it sends a notification to the user's device. This notification is sent using a push notification API (e.g., Firebase Cloud Messaging, Apple Push Notification Service). The notification content may include information such as "Ticket sales for Rock Festival 2024 have begun. For details, click here: URL."
[0109] The user receives the notification, checks the details, and then performs an operation to indicate their desire to purchase. Specifically, they click the "Request to Purchase" button in the notification. This operation causes the user's device to send a request to purchase to the server. This information is also sent via the REST API.
[0110] The server receives the user's purchase request, accesses the specified ticket purchasing site (e.g., Ticketmaster, e+) using pre-stored user information (e.g., name, credit card information), and automatically completes the purchase process, which includes using web scraping technology to automatically fill in forms and click necessary buttons.
[0111] Once the purchase is complete, the server instantly generates an electronic ticket with a no-resale restriction. This electronic ticket is generated as a PDF file containing a QR code and embedded restriction information. The generated electronic ticket is sent from the server to the user's device, where it is stored in local storage or a database (e.g., SQLite) and can be displayed as needed.
[0112] This allows users to quickly and efficiently obtain tickets for their desired events, and effectively prevents resale issues.
[0113] As a concrete example, a user is interested in "Rock Festival 2024" and enters the event name into the application. The server then periodically searches the web and social media for information on "Rock Festival 2024 ticket sales," and sends a notification to the user when it finds sales information. When the user receives the notification and clicks "I want to buy," the server automatically processes the ticket purchase, generates an electronic ticket, and sends it to the user's device.
[0114] Example prompt sentence:
[0115] "Please explain the flow of a system that automates ticket purchasing for events of interest to users and prevents resale. The system operates using a user device, a server, and a generative AI model."
[0116] The flow of the identification process in the first embodiment will be described with reference to FIG.
[0117] Step 1: Registering users for an event
[0118] Input: The user inputs the event name or keyword of interest into the interface of the user terminal.
[0119] Processing: The user terminal converts the input event name and keywords into JSON format and sends it to the server using the HTTPS protocol.
[0120] Output: The server stores the received event names and keywords in a database.
[0121] Specific operation: The user opens the event registration screen on the smartphone app, enters "Rock Festival 2024," and taps the send button.
[0122] Step 2: Monitor event information
[0123] Input: The server periodically generates search queries based on the event names and keywords saved in step 1.
[0124] Processing: The server uses the generative AI model to gather information from the web and social networking services, specifically by performing searches through the Google Custom Search API and Twitter API, and parsing the results.
[0125] Output: Extract relevant ticket sales information from the search results and temporarily store that information in a cache.
[0126] Specific operation: The server periodically performs searches for keywords such as "Rock Festival 2024 ticket sales," analyzes the obtained information, and stores it in a cache.
[0127] Step 3: Sending notifications
[0128] Input: The server prepares to send a notification to the user based on the ticket sales information found in step 2.
[0129] Processing: The server uses Firebase Cloud Messaging (FCM) or Apple Push Notification Service (APNS) to send a push notification to the user device.
[0130] Output: The user terminal displays the received notification.
[0131] Specific operation: The server sends a push notification with the notification content such as "Ticket sales for Rock Festival 2024 have begun. For details, click here: URL."
[0132] Step 4: Ticket purchase confirmation
[0133] Input: The user clicks on the received notification and operates the screen to indicate their desire to purchase.
[0134] Processing: The user terminal sends a purchase request to the server. The server receives this information and sets the purchase request flag for the corresponding user.
[0135] Output: The server updates the data with the purchase flag set.
[0136] Specific behavior: When the user taps the notification, the app opens and they click the "Want to buy" button.
[0137] Step 5: Automatic ticket purchase
[0138] Input: The server retrieves pre-stored personal information (e.g., name, credit card information) based on the user information for which the purchase wish flag is set.
[0139] Processing: The server uses this information to access ticket purchasing sites and perform automated form-fill and submission operations, for example, using web scraping techniques.
[0140] Output: The purchase is completed and the purchase confirmation is saved on the server.
[0141] Specific operation: The server automatically enters the user's name and credit card information into the purchase site's form and clicks the purchase button.
[0142] Step 6: Ticketing and Delivery
[0143] Input: The server generates a ticket in electronic format based on the purchase confirmation information.
[0144] Processing: The server adds the restriction information that prohibits resale, generates the ticket as a PDF file, and then sends the generated ticket to the user's terminal.
[0145] Output: The electronic ticket is sent to the user's terminal and saved.
[0146] Specific operation: The server uses a PDF generator to generate an electronic ticket containing a QR code, then BASE64 encodes it and sends it in JSON format to the user's device. The user can then view and save the ticket in the app.
[0147] (Application example 1)
[0148] 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."
[0149] The present invention aims to enable users to efficiently and quickly purchase or reserve products they are interested in, thereby reducing competition for popular products, and also to solve the problems of missed purchases and inventory shortages by enabling users to reliably receive products at physical stores.
[0150] 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.
[0151] In this invention, the server includes means for inputting product names and keywords of interest, means for searching for product information based on the input product names and keywords, means for sending a notification when sales of a product included in the searched product information begin, means for confirming a reservation request from a user who has received the notification, means for automatically reserving the product after confirming the reservation request, and means for allowing the reserved product to be picked up at a physical store. This allows users to reliably reserve products of interest and smoothly pick them up at the physical store.
[0152] "Goods" means any goods or services sold or provided.
[0153] "Product Names or Keywords of Interest" means names or related words associated with specific goods or services that you are interested in purchasing or reserving.
[0154] "Product information" refers to detailed information about a particular product, such as stock status, release date, price, specifications, etc.
[0155] "Availability" refers to the date and time when a particular product is officially available for purchase in the marketplace.
[0156] "Notification" means a message or alert that notifies a user of specific information or events.
[0157] A "reservation request" is a user's expression of intent to reserve a specific product in advance for purchase or collection at a later date.
[0158] "Means for automatically reserving products" refers to the process by which the system receives the user's intention and reserves a specific product without manual operation.
[0159] "Electronic format" refers to data or information recorded in digital form.
[0160] "Brick and mortar store" refers to a retail store that has a physical location and conducts face-to-face transactions with customers.
[0161] The present invention is a system that allows users to efficiently and quickly purchase or reserve products they are interested in. This system includes a means for inputting and searching for product names and keywords, a means for sending and receiving notifications, a means for automatically reserving products, and a means for receiving products at a physical store.
[0162] System Configuration
[0163] This system is constructed mainly using the following hardware and software.
[0164] 1. User Device
[0165] A smartphone application with an input function that allows users to input product names and keywords. It is implemented on the Android or iOS platform.
[0166] Push notification functionality to receive notifications and confirm reservation requests, using Google Firebase Cloud Messaging (FCM) and Apple Push Notification Service (APNs).
[0167] Provides an interface to display reservation completion and redemption information.
[0168] 2. Server
[0169] Product information is stored in a database and a means of searching for product information is provided using generative AI. The generative AI model is a generative AI (e.g., GPT-4).
[0170] A function that works with push notification services to send notifications to users.
[0171] A function that automatically processes product reservations. Reservation information is managed using a web framework such as Django and a task scheduler such as Celery.
[0172] A function that sends information to the user's device to pick up the product at a physical store.
[0173] System Operation
[0174] 1. Register your interest in products
[0175] A user uses a smartphone app to input product names and keywords that they are interested in. The input information is sent to the server.
[0176] 2. Search for product information
[0177] The server stores the received product names and keywords in a database and periodically searches the web and social media using the generative AI model to collect information about product availability and sales start dates.
[0178] Example: Prompt sentence to generative AI model: "Please check the stock status of limited edition premium shoes and notify the user when they are in stock."
[0179] 3. Sending notifications
[0180] When related product information appears in the search results, the server sends a push notification to the user's device, including the reservation start date and time and a URL.
[0181] Example: Notification: "Pre-orders for limited edition premium shoes have begun. Please see the link below for details."
[0182] 4. Automated booking process
[0183] The user receives the notification and clicks a button to select a reservation request, which causes the terminal to send the reservation request to the server.
[0184] The server automatically processes the reservation using pre-stored user information (such as name and contact information).
[0185] 5. Reservation confirmation and collection
[0186] When the reservation is completed, the server sends a reservation completion notice to the user terminal.
[0187] The user can present this notification at the physical store and pick up the reserved item.
[0188] The above system configuration and operation allows users to efficiently reserve and purchase products they are interested in and reliably pick them up at a physical store.
[0189] The flow of the specific processing in the application example 1 will be described with reference to FIG.
[0190] Step 1:
[0191] Users enter product names and keywords of interest into a smartphone app. After input, the device sends this information to a server. By sending the entered product names and keywords to the server, the data necessary for subsequent processing is provided.
[0192] Step 2:
[0193] The server stores the received product names and keywords in a database. This input data is used as a prompt for a generative AI model (e.g., GPT-4) to collect the latest information related to the product from the web and social media. By storing the information in the database, the server periodically searches using these keywords to check the latest sales start information and inventory information.
[0194] Step 3:
[0195] The server uses a web scraping tool (e.g., BeautifulSoup) to extract relevant product information. It passes prompts to a generative AI model, which analyzes the search results and extracts product information (e.g., stock availability, release date, etc.). The extracted data is then stored back in the database.
[0196] Step 4:
[0197] The server sends a push notification to the user when product information is updated. It uses a push notification service (e.g., Google FCM or Apple APNs) to send the notification to the user's device. In this step, the server compares the information in the database and sends the notification only if the new notification conditions are met.
[0198] Step 5:
[0199] The user receives a push notification, clicks the link in the notification to check the details, and selects whether they wish to make a reservation. The device then sends the reservation request to the server. By specifically communicating the user's intention to the server, the automatic reservation process begins.
[0200] Step 6:
[0201] The server automatically processes reservations based on pre-stored user information (such as name and contact information). The server then enters the necessary information into a pre-set reservation form and confirms the product reservation. Because reservations are made automatically, it saves the user time and effort.
[0202] Step 7:
[0203] Once the reservation process is complete, the server sends the user a confirmation notification, which includes details on how to collect the reserved item and the physical store location, so the user knows exactly how to secure and collect the reserved item.
[0204] Step 8:
[0205] The user presents the notification to the physical store and collects the reserved product. The collection procedure at the physical store is carried out based on confirmation and verification by the store staff. Once collection is complete, the entire system process is completed.
[0206] 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.
[0207] The present invention is a system that recognizes a user's emotions and assists in purchasing event tickets based on those emotions. This system operates by combining a user terminal, a server, an emotion engine, and a generation AI. Specific embodiments are described below.
[0208] User event registration and emotion recognition
[0209] 1. User event registration
[0210] A user launches the application and enters the name of an event or keyword they are interested in, for example, "Rock Festival 2024."
[0211] The terminal transmits the input event name and keywords to the server.
[0212] 2. Emotional Recognition
[0213] The device is equipped with a camera and microphone, and the emotion engine analyzes the user's facial expressions and tone of voice.
[0214] The emotion engine analyzes the user's emotion data in real time to determine the user's emotional state for the events entered by the user.
[0215] Event information monitoring and notification
[0216] 1. Event information monitoring
[0217] The server stores the required event names and keywords in a database, and then uses generative AI to periodically collect relevant event information from web searches and social networking services (SNS).
[0218] 2. Sending notifications
[0219] When the collected event information is related to the start of ticket sales, the server sends a push notification to the device, and the emotion engine customizes the content of the notification based on the user's emotional state.
[0220] For example, if the user is excited, the notification will have emotional content such as "An event you can't miss! Check it out now."
[0221] Ticket purchase confirmation and automatic purchase
[0222] 1. User Verification
[0223] The user receives a notification, checks the details, and if they are interested in purchasing tickets, selects "I want to buy."
[0224] 2. Automatic ticket purchase
[0225] The device sends the user's purchase request to the server, which uses the stored user information (such as name and credit card information) to initiate the purchase process.
[0226] The server automatically accesses the ticket purchasing site, fills out the purchase form, and completes the process.
[0227] Ticket issuance and distribution
[0228] 1. Ticket issuance
[0229] Once the purchase is complete, the server generates an electronic version of the ticket, which is restricted from resale.
[0230] 2. Ticket Offer
[0231] The server sends the generated electronic ticket to the terminal, which stores the received ticket in the user's account and displays it as needed.
[0232] Specific examples
[0233] 1. User registration and emotion recognition flow
[0234] A user is interested in "Rock Festival 2024" and enters the event name "Rock Festival 2024" into the application.
[0235] The terminal sends the entered information to the server, which stores the event name in a database.
[0236] The emotion engine analyzes the user's facial expressions and tone of voice using the device's built-in camera and microphone to determine the user's emotional state.
[0237] 2. Customizing notifications
[0238] The server uses generative AI to periodically search the web and social media for information on "Rock Festival 2024 ticket sales."
[0239] When a sale is detected, the server sends a notification to the terminal.
[0240] If the emotion engine detects that the user is excited, the notification will be customized to say, "An event you absolutely cannot miss! Check it out now."
[0241] This allows users to receive event notifications at the right time and in the right way based on their emotions, allowing them to secure tickets when they are most interested in them. It also prevents ticket resale issues, improving the ticket purchasing experience.
[0242] The processing flow will be explained below.
[0243] Step 1:
[0244] A user launches the application and enters the name of an event or keyword they are interested in, for example, "Rock Festival 2024."
[0245] Step 2:
[0246] The device sends the input event name and keywords to the server. The transmitted data includes the event name "Rock Festival 2024."
[0247] Step 3:
[0248] The server stores the received event names and keywords in a database, then uses generative AI to schedule collection of related event information from the web and social media.
[0249] Step 4:
[0250] The device uses a camera and microphone to collect the user's facial expressions and tone of voice, and the emotion engine analyzes this data in real time to determine the user's emotional state.
[0251] Step 5:
[0252] The server uses generative AI to periodically search for relevant information, such as "Rock Festival 2024 ticket sales," and collects any new information it finds.
[0253] Step 6:
[0254] The server sends push notifications to the device based on the collected information. The content of the notification is customized according to the user's emotional state. For example, if the user is excited, the notification might say, "This is an event you definitely can't miss! Check it out now."
[0255] Step 7:
[0256] The user receives a push notification, checks the details of the event, and clicks the button to select "I want to buy."
[0257] Step 8:
[0258] The terminal transmits the user's purchase request to the server. The transmitted data includes "Event name: Rock Festival 2024" and "Purchase request: Yes."
[0259] Step 9:
[0260] When the server receives the purchase request, it uses the pre-stored user information (name, credit card information, etc.) to access the specified ticket purchase site. For example, it accesses "https: / / example.com / ticket-purchase."
[0261] Step 10:
[0262] The server automatically fills in the necessary information on the purchase site's form, including the user's name, credit card number, and expiration date.
[0263] Step 11:
[0264] After the form is filled out, the server executes the purchase process. If the purchase is successful, the server receives a "ticket purchase successful" message.
[0265] Step 12:
[0266] Once the purchase is complete, the server generates the ticket in electronic format, with a no-resale restriction attached to the electronic ticket.
[0267] Step 13:
[0268] The server sends the generated electronic ticket to the terminal. The sent data includes "Electronic ticket ID: 987654321" and "Not for resale."
[0269] Step 14:
[0270] The device stores the received e-ticket in the user's account and provides the functionality to display it as needed. The user can check the ticket within the application.
[0271] Through these steps, users can obtain event tickets in a more personalized way using emotion recognition, and the problem of ticket resale can be prevented.
[0272] Example 2
[0273] 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."
[0274] Conventional ticket purchasing systems provide uniform notifications without considering the user's emotional state, making it impossible to effectively provide information at a time when users are interested. Furthermore, the manual ticket purchasing process required an inconvenient purchasing experience. Furthermore, fraudulent transactions due to ticket resale after purchase were a problem.
[0275] 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.
[0276] In this invention, the server includes means for inputting an event name or keyword of interest, means for searching for event information based on the input event name or keyword, means for sending a notification when tickets for the event included in the searched event information go on sale, means for confirming the purchase intention of the user who received the notification, means for automatically purchasing the ticket after confirming the purchase intention, means for attaching a no-resale restriction to the purchased ticket and providing it in an electronic format, means for recognizing the user's emotion, and means for customizing the content of the notification based on the recognized emotion. This allows for notifications to be sent with optimal timing and content according to the user's emotional state, enabling easy and automatic ticket purchases and preventing resale issues.
[0277] "Event names and keywords of interest" are the names of events and related words that interest users and are the subject of searches and notifications.
[0278] "Event Information" refers to data and news related to a specific event collected from websites and social networking services.
[0279] The "means for sending a notification when ticket sales begin" is a mechanism for sending a push notification to the user's device when ticket sales for an event begin.
[0280] "Means for confirming purchase intent" refers to the interface or process by which a user confirms their intention to purchase a ticket.
[0281] The "means for automatically purchasing tickets" is a system in which, after the user's purchase request has been confirmed, the server automatically carries out the ticket purchase procedure based on the user information stored on the server.
[0282] "Means of providing tickets in electronic format with restrictions preventing resale" refers to a system in which purchased tickets are provided to users in electronic format with restrictions attached to prevent resale.
[0283] "Means for recognizing emotions" refers to technologies or systems that analyze a user's facial expressions and tone of voice to determine their emotional state at that time.
[0284] "Means for customizing notification content based on emotions" refers to a mechanism that adjusts the wording and content of notifications sent according to the user's recognized emotional state.
[0285] This invention is a system that recognizes a user's emotions and supports the purchase of event tickets based on those emotions. This system operates by combining a user terminal, a server, an emotion engine, and a generation AI.
[0286] User event registration and emotion recognition
[0287] 1. The user launches the application and enters the name of an event or keyword they are interested in. For example, they might enter "Rock Festival 2024."
[0288] 2. The device sends the entered event name and keywords to the server.
[0289] 3. The device is equipped with a camera and microphone, and the emotion engine analyzes the user's facial expressions and tone of voice.
[0290] 4. The emotion engine analyzes the user's emotion data in real time and determines the user's emotional state for the events entered by the user.
[0291] Event information monitoring and notification
[0292] 1. The server stores the required event names and keywords in a database.
[0293] 2. The server periodically collects relevant event information from web searches and social networking services (SNS) using generative AI.
[0294] 3. If the collected event information is related to the start of ticket sales, the server sends a push notification to the device. At this time, the emotion engine customizes the content of the notification based on the user's emotional state. For example, if the user is excited, the server sends a notification with the content "This is an event you cannot miss! Check it out now!"
[0295] Ticket purchase confirmation and automatic purchase
[0296] 1. The user receives a notification, checks the details, and if they are interested in purchasing a ticket, selects "I want to buy."
[0297] 2. The terminal sends the user's purchase request to the server.
[0298] 3. The server initiates the purchase process using the stored user information (name, credit card information, etc.).
[0299] 4. The server automatically accesses the ticket purchasing site, fills in the purchase form, and completes the process.
[0300] Ticket issuance and distribution
[0301] 1. Once the purchase is complete, the server generates an electronic ticket, which is restricted from resale.
[0302] 2. The server sends the generated electronic ticket to the terminal, which stores it in the user's account and displays it as needed.
[0303] Specific examples
[0304] User registration and emotion recognition flow
[0305] A user is interested in "Rock Festival 2024" and enters the event name "Rock Festival 2024" into the application.
[0306] The terminal sends the entered information to the server, which stores the event name in a database.
[0307] Using the device's built-in camera and microphone, the emotion engine analyzes the user's facial expressions and tone of voice to determine their emotional state.
[0308] Customizing notifications
[0309] The server uses generative AI to periodically search the web and social media for information on "Rock Festival 2024 ticket sales."
[0310] When a sale is detected, the server sends a notification to the terminal.
[0311] If the emotion engine detects that the user is excited, the notification will be customized to say, "An event you absolutely cannot miss! Check it out now."
[0312] An example prompt is, "Get real-time ticket sales information for Rock Festival 2024 and optimize the notification content based on user sentiment."
[0313] This allows users to receive event notifications at the right time and in the right way based on their emotions, allowing them to secure tickets when they are most interested in them. It also prevents ticket resale issues, improving the ticket purchasing experience.
[0314] The flow of the identification process in the second embodiment will be described with reference to FIG.
[0315] Step 1:
[0316] User event registration
[0317] The user launches the application and enters the name of an event or keywords of interest. An example input is "Rock Festival 2024." The device sends this information to the server. The input here is the event name or keywords, and the first output is the user's search intent, which is sent to the server.
[0318] Step 2:
[0319] emotion recognition
[0320] The device is equipped with a camera and microphone, which capture the user's facial expressions and tone of voice. The emotion engine analyzes this captured data in real time to determine the user's emotional state. For example, if the user is smiling, it is determined to be "excited." The input is the captured facial and voice data, and the output is the analyzed user's emotional state. The device sends this information to a server.
[0321] Step 3:
[0322] Monitoring event information
[0323] The server stores the received event names and keywords in a database. Using generative AI, the server periodically collects related event information from web searches and social networking services (SNS). Specifically, it inputs a search query as a prompt and uses the generative AI model to output newly discovered event information. This output is stored in the database and updated as necessary.
[0324] Step 4:
[0325] Sending notifications
[0326] The server pushes the collected event information to the user's device. At this time, the emotion engine customizes the notification content. For example, if the analysis finds that the user is excited, a notification such as "This is an event you absolutely cannot miss! Check it out now" is sent. The input is the collected event information and the analyzed emotional state, and the output is the customized notification content.
[0327] Step 5:
[0328] Ticket purchase confirmation
[0329] The user receives a push notification. If the user sees the notification and is interested in purchasing a ticket, they select "purchase" within the application. The input is the user's selection information, and the output is the purchase request information sent to the server.
[0330] Step 6:
[0331] Automatic ticket purchase
[0332] The terminal sends the user's purchase request to the server. The server uses the saved user information (e.g., name, credit card information) to access the ticket purchasing site and automatically enter the required information. The input is the user's purchase request and saved personal information, and the output is confirmation of the completed ticket purchase.
[0333] Step 7:
[0334] Ticketing and distribution
[0335] Once the ticket purchase is complete, the server generates an electronic ticket and adds a non-resale restriction. The generated electronic ticket is sent to the terminal, which then stores the received ticket in the user's account. The input is the purchase completion information, and the output is the electronic ticket.
[0336] These steps allow users to receive event notifications at the most convenient time and in the most convenient way, purchase tickets conveniently and efficiently, and prevent ticket resale issues.
[0337] (Application example 2)
[0338] 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."
[0339] Conventional event ticket purchasing systems simply notify users of event information and are unable to consider the user's emotional state or interests, making it difficult to maximize the user's purchasing motivation. Furthermore, in brick-and-mortar stores, product recommendations are not based on the user's emotions, making it difficult to effectively promote products at the right time. This leaves the improvement of user satisfaction and purchasing experience as a challenge.
[0340] The identification process by the identification processing unit 290 of the data processing device 12 in Application Example 2 is realized by the following means. In this invention, the server includes means for recognizing emotions, means for inputting an event name or keyword of interest, means for searching for event information based on the input event name or keyword, means for sending a notification when ticket sales for an event included in the searched event information begin, means for customizing the content of the notification according to the user's emotional state, means for confirming the purchase intention of the user who received the notification, means for automatically purchasing tickets after confirming the purchase intention, and means for attaching a non-resale restriction to purchased tickets and providing them in an electronic format. This enables notifications and promotions to be provided at the appropriate time based on the user's emotions, maximizing the user's interest.
[0341] - "Means for recognizing emotions" refers to a function that analyzes the user's facial expressions and tone of voice to determine their emotional state in real time.
[0342] The "means for inputting the event name or keyword of interest" is an interface through which the user inputs the event name or keyword on the application and transmits the data to the server.
[0343] The "means for searching for event information" is a function that allows the server to collect related event information from the web or social networking services based on the input event name or keywords.
[0344] The "means for sending a notification" is a function for sending a push notification to a user terminal based on the event information collected by the server.
[0345] The "means for customizing notification content according to emotional state" is a function in which the emotion engine analyzes the user's emotional state and changes the notification content based on the results.
[0346] The "means for confirming purchase intent" is a function that allows the user to confirm their willingness to purchase tickets through the application after receiving the notification.
[0347] The "means for automatically purchasing tickets" is a function in which the server automatically purchases tickets using the stored user information after the user's purchase request has been confirmed.
[0348] "Means for adding restrictions preventing resale and providing them in electronic format" is a function that adds restrictions to purchased tickets on the system to prevent resale and provides them to users in electronic format.
[0349] This invention is a system that recognizes a user's emotions and supports the purchase of event tickets based on those emotions. This system operates by combining a user terminal, a server, an emotion engine, and a generation AI. Specific embodiments are described below.
[0350] Hardware Configuration
[0351] User terminal
[0352] The user device consists of a device equipped with a camera and microphone, such as smart glasses, a smartphone, or a head-mounted display, which collects the user's facial expressions and tone of voice in real time.
[0353] server
[0354] The server has high-performance computing resources to run the emotion engine and generative AI model.
[0355] Specific software used includes Microsoft Azure Emotion API for the emotion engine and OpenAI's GPT-3 for the generative AI model.
[0356] Software Configuration
[0357] Emotion Recognition Module
[0358] The emotion recognition module collects the user's facial expressions and tone of voice through the camera and microphone installed on the user's device, and analyzes the data using the Microsoft Azure Emotion API, thereby recognizing the user's emotional state in real time.
[0359] Event information collection module
[0360] The event information collection module is implemented on the server and automatically collects event information of interest from the web and social networking services. This module periodically monitors the Internet to obtain new event information.
[0361] Notification Customization Module
[0362] The notification customization module analyzes the user's emotional state based on data from the emotion recognition module. Using a generative AI model, it customizes the notification content based on the user's emotions. For example, if the user is excited, it generates a strong message saying, "This is an event you can't miss! Check it out now!"
[0363] Automatic ticket purchasing module
[0364] The automatic ticket purchasing module automatically purchases tickets using the saved user information after confirming the user's purchase request. During this process, the server automatically fills in the purchase form and provides the necessary information.
[0365] Electronic ticket provision module
[0366] The electronic ticket providing module assigns a non-resale restriction to the purchased ticket and sends it to the user's terminal in electronic format. This ticket is stored in the user's account and displayed as needed.
[0367] Specific examples
[0368] A user puts on smart glasses and expresses interest in a particular event.
[0369] 1. The camera and microphone on the user's device collect the user's facial expressions and tone of voice, recognizing emotions in real time.
[0370] 2. The server monitors web and social networking services to collect certain event information.
[0371] 3. Based on the user's emotional state, the generative AI model will customize and send a notification saying, "This event is a must-see!"
[0372] 4. After the user receives the notification and confirms their purchase, the server automatically purchases the tickets and provides them in electronic format.
[0373] Examples of prompt statements
[0374] Emotion Recognition Data Analysis Prompt: "Analyze the user's facial expression and tone of voice and output their current emotional state."
[0375] Product suggestion generation prompt: "Generate product suggestions when the user is excited. For example, limited edition items."
[0376] This system enables notifications and promotions to be delivered at the right time based on the user's emotions, maximizing the user's interest and improving user satisfaction.
[0377] The flow of the specific processing in the application example 2 will be described with reference to FIG.
[0378] Step 1:
[0379] The user puts on the smart glasses and launches the application. The user inputs the name of an event or keyword of interest (e.g., "Rock Festival 2024") by voice or text. The input data is then sent from the user's device to the server.
[0380] Step 2:
[0381] The server passes the received event name and keywords to an event information collection module, which searches for related event information from the web and social networking services based on the input event name and keywords and stores it in a database.
[0382] Step 3:
[0383] The camera and microphone on the user's device continuously capture the user's facial expressions and tone of voice, and send the data to the server in real time. The emotion recognition module analyzes the collected data using the Microsoft Azure Emotion API to recognize the user's emotional state. The input is the user's facial and voice data, and the output is their emotional state (e.g., "excited").
[0384] Step 4:
[0385] The server determines the notification content based on the event information and the user's emotional state. The notification customization module uses a generative AI model (e.g., OpenAI's GPT-3) to generate notification content based on the prompt. The input is the event information and the user's emotional state, and the output is a customized notification. It generates a strong message such as "This event is a must-see!"
[0386] Step 5:
[0387] The server pushes the customized notification to the user's device and waits until the user confirms the notification and responds. For example, the user selects "purchase request" and sends the response from the device to the server.
[0388] Step 6:
[0389] The server receives the user's purchase request, and the automatic ticket purchasing module starts the purchase process. Using saved user information (name, credit card information, etc.), the module automatically accesses the ticket purchasing site, fills in a form, and makes the purchase. The input is the user's purchase request and saved user information, and the output is a notification of purchase completion.
[0390] Step 7:
[0391] After the purchase is complete, the server assigns a no-resale restriction to the purchased ticket and provides it in electronic format. The electronic ticket provision module generates an electronic ticket and sends it to the user's terminal. The user terminal stores the received electronic ticket in the user's account and can display it as needed. The input is purchase completion information, and the output is the electronic ticket.
[0392] 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.
[0393] 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.
[0394] 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.
[0395] [Second embodiment]
[0396] FIG. 3 shows an example of the configuration of a data processing system 210 according to the second embodiment.
[0397] 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.
[0398] 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).
[0399] 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.
[0400] 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.
[0401] 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).
[0402] 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.
[0403] 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.
[0404] 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.
[0405] 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.
[0406] 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.
[0407] 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."
[0408] The system of the present invention is an automated ticket purchasing system that allows users to easily obtain tickets for events of interest and simultaneously solves the problem of ticket resale. This system operates using a user terminal, a server, and a generation AI. Specific embodiments are described below.
[0409] 1. User event registration
[0410] The user inputs the event name or keyword of interest into the user terminal, via an application or a web interface.
[0411] The terminal transmits the input event name and keywords to the server.
[0412] 2. Event information monitoring
[0413] The server stores the received event names and keywords in a database.
[0414] The server uses generative AI to periodically search the web and social networking services (SNS) to find ticket sales information for the event.
[0415] 3. Sending notifications
[0416] If the server detects relevant ticket sales information, it sends a push notification to the user's device, letting the user know that tickets for the event are now on sale.
[0417] 4. Ticket purchase confirmation and automatic purchase
[0418] The user receives the notification and performs an operation to confirm the purchase request, for example, by clicking the "Request to Purchase" button in the notification.
[0419] The terminal transmits the user's purchase request to the server, which then initiates the purchase procedure.
[0420] The server uses pre-saved user information (such as name and credit card information) to access the designated ticket purchasing site and automatically complete the purchase procedure.
[0421] 5. Ticket issuance and anti-resale measures
[0422] After the purchase process is completed, the server generates an electronic ticket, which includes a restriction that prohibits resale.
[0423] The server transmits the generated electronic ticket to the user terminal.
[0424] The terminal stores the received electronic ticket in the user's account so that it can be displayed as needed.
[0425] Specific examples
[0426] 1. User registration and notification flow
[0427] A user is interested in "Rock Festival 2024" and enters the event name "Rock Festival 2024" into the application.
[0428] The terminal sends the entered information to the server, which stores the event name in a database.
[0429] The server uses generative AI to periodically search the web and social media for information on "Rock Festival 2024 ticket sales."
[0430] When sales information is detected, the server sends a notification to the device, which includes the date and time the sale starts and a URL.
[0431] 2. Automating ticket purchasing
[0432] The user receives the notification, checks the details, and then clicks a button to select their purchase.
[0433] The terminal transmits a purchase request to the server, and the server accesses the ticket purchase site.
[0434] The server automatically fills in the purchase form using pre-stored user information (name, credit card information) and completes the purchase process.
[0435] 3. Issuance and provision of tickets
[0436] The server generates the ticket in electronic format immediately upon purchase and includes a no-resale restriction.
[0437] The server sends the generated ticket to the terminal, which stores it in the user's account for viewing.
[0438] This allows users to easily obtain tickets for the events they want and also prevents the problem of resale.
[0439] The processing flow will be explained below.
[0440] Step 1:
[0441] A user launches the application and enters the name of an event or keyword they are interested in, for example, "Rock Festival 2024."
[0442] Step 2:
[0443] The device sends the input event name and keywords to the server. The transmitted data includes the event name, such as "Rock Festival 2024."
[0444] Step 3:
[0445] The server stores the received event names and keywords in a database, then starts the generation AI, which periodically searches for related event information from the web and social media.
[0446] Step 4:
[0447] The server collects relevant event information from the search results, such as "Ticket sales for Rock Festival 2024 have begun."
[0448] Step 5:
[0449] The server then sends a push notification to the device based on the collected information, including the date and time when tickets for the event go on sale and the URL where they can be purchased.
[0450] Step 6:
[0451] The user checks the notification received on the device, confirms the details of the event, and clicks the "Purchase" button to select whether they wish to purchase the item.
[0452] Step 7:
[0453] The terminal transmits the user's purchase request to the server, which includes information such as "Event name: Rock Festival 2024" and "Purchase request: Yes."
[0454] Step 8:
[0455] When the server receives the purchase request, it uses the pre-stored user information to access the specified ticket purchase site, for example, "https: / / example.com / ticket-purchase."
[0456] Step 9:
[0457] The server automatically fills in the necessary information (such as name and credit card information) on the purchase site form, which is provided by the user in advance.
[0458] Step 10:
[0459] The server executes the purchase process and receives a success notification, such as a message saying "ticket purchase successful."
[0460] Step 11:
[0461] Once the purchase is complete, the server generates the ticket in electronic format, with a no-resale restriction attached to the ticket.
[0462] Step 12:
[0463] The server then sends the generated electronic ticket to the terminal, which includes data such as "Electronic ticket ID: 987654321" and "Not for resale."
[0464] Step 13:
[0465] The device stores the received e-ticket in the user's account and makes it available for viewing as needed. The user can view the ticket within the application.
[0466] By following these steps, users can easily and reliably obtain tickets to events they are interested in, while also preventing the problem of resale.
[0467] Example 1
[0468] 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."
[0469] When purchasing event tickets, it is important to ensure that users can quickly and accurately obtain tickets for their desired event while preventing the problem of resale. In particular, tickets for popular events tend to sell out quickly, and resellers often buy up all the tickets, making it difficult for ordinary users to purchase them at the regular price. Furthermore, manually gathering information on the Internet is time-consuming and inefficient.
[0470] 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.
[0471] In this invention, the server includes means for inputting an event name or keyword of interest, means for searching for event information based on the input event name or keyword, means for sending a notification when tickets for the event included in the searched event information go on sale, means for confirming a purchase intention of a user who received the notification, means for automatically purchasing tickets after confirming the purchase intention, means for providing the purchased tickets in an electronic format with a no-resale restriction, and means for periodically searching the web and social networking services using a generative language model. This allows users to efficiently obtain tickets for desired events and prevents resale problems.
[0472] "Means for inputting event names and keywords of interest" refers to an interface that allows users to input into a terminal the names of events that they are interested in or wish to participate in, as well as related keywords.
[0473] "Means for searching event information" refers to software and algorithms for retrieving related information from websites and social networking services on the Internet based on the event name or keywords entered.
[0474] "Means for sending notifications" refers to push notifications or message sending functions that notify user devices that tickets for an event are on sale.
[0475] "Means for confirming purchase intention" refers to the interface that allows the user to perform an operation to indicate their intention to purchase a ticket in response to the notification they received, and the function that receives and processes this information.
[0476] "Means for automatically purchasing tickets" refers to software and algorithms that, after confirming a user's purchase request, access a designated ticket purchasing site using pre-saved user information, automatically input and submit the necessary information to make the purchase.
[0477] "Means for adding a restriction that prevents resale and providing it in electronic format" refers to the function of adding a restriction that prevents resale of a ticket after purchase, generating it as an electronic ticket, and providing it to the user's terminal.
[0478] "Means for searching using generative language models" refers to the ability to utilize generative AI models to periodically extract and analyze event ticket sales information from large datasets using natural language processing techniques.
[0479] The system of the present invention is an automatic purchasing system that allows users to easily obtain tickets for events they are interested in, while at the same time solving the problem of ticket resale. This system is built using a user terminal, a server, and a generative language model.
[0480] First, a user uses their device to enter the name of an event or keywords they are interested in, such as "Rock Festival 2024," using a smartphone application or web browser. This entry is made through the device's interface, and the information is sent to the server using the HTTPS protocol.
[0481] The server then stores the received event names and keywords in a relational database (e.g., MySQL). The stored data is then used to search for relevant information from websites and social networking services (SNS) on the Internet using a generative AI model (e.g., OpenAI GPT-4) running on the server. This search is performed periodically and uses APIs for web search (e.g., Google Custom Search API) and APIs for SNS (e.g., Twitter API).
[0482] The server analyzes the search results, and when it detects ticket sales information related to a specific event, it sends a notification to the user's device. This notification is sent using a push notification API (e.g., Firebase Cloud Messaging, Apple Push Notification Service). The notification content may include information such as "Ticket sales for Rock Festival 2024 have begun. For details, click here: URL."
[0483] The user receives the notification, checks the details, and then performs an operation to indicate their desire to purchase. Specifically, they click the "Request to Purchase" button in the notification. This operation causes the user's device to send a request to purchase to the server. This information is also sent via the REST API.
[0484] The server receives the user's purchase request, accesses the specified ticket purchasing site (e.g., Ticketmaster, e+) using pre-stored user information (e.g., name, credit card information), and automatically completes the purchase process, which includes using web scraping technology to automatically fill in forms and click necessary buttons.
[0485] Once the purchase is complete, the server instantly generates an electronic ticket with a no-resale restriction. This electronic ticket is generated as a PDF file containing a QR code and embedded restriction information. The generated electronic ticket is sent from the server to the user's device, where it is stored in local storage or a database (e.g., SQLite) and can be displayed as needed.
[0486] This allows users to quickly and efficiently obtain tickets for their desired events, and effectively prevents resale issues.
[0487] As a concrete example, a user is interested in "Rock Festival 2024" and enters the event name into the application. The server then periodically searches the web and social media for information on "Rock Festival 2024 ticket sales," and sends a notification to the user when it finds sales information. When the user receives the notification and clicks "I want to buy," the server automatically processes the ticket purchase, generates an electronic ticket, and sends it to the user's device.
[0488] Example prompt sentence:
[0489] "Please explain the flow of a system that automates ticket purchasing for events of interest to users and prevents resale. The system operates using a user device, a server, and a generative AI model."
[0490] The flow of the identification process in the first embodiment will be described with reference to FIG.
[0491] Step 1: Registering users for an event
[0492] Input: The user inputs the event name or keyword of interest into the interface of the user terminal.
[0493] Processing: The user terminal converts the input event name and keywords into JSON format and sends it to the server using the HTTPS protocol.
[0494] Output: The server stores the received event names and keywords in a database.
[0495] Specific operation: The user opens the event registration screen on the smartphone app, enters "Rock Festival 2024," and taps the send button.
[0496] Step 2: Monitor event information
[0497] Input: The server periodically generates search queries based on the event names and keywords saved in step 1.
[0498] Processing: The server uses the generative AI model to gather information from the web and social networking services, specifically by performing searches through the Google Custom Search API and Twitter API, and parsing the results.
[0499] Output: Extract relevant ticket sales information from the search results and temporarily store that information in a cache.
[0500] Specific operation: The server periodically performs searches for keywords such as "Rock Festival 2024 ticket sales," analyzes the obtained information, and stores it in a cache.
[0501] Step 3: Sending notifications
[0502] Input: The server prepares to send a notification to the user based on the ticket sales information found in step 2.
[0503] Processing: The server uses Firebase Cloud Messaging (FCM) or Apple Push Notification Service (APNS) to send a push notification to the user device.
[0504] Output: The user terminal displays the received notification.
[0505] Specific operation: The server sends a push notification with the notification content such as "Ticket sales for Rock Festival 2024 have begun. For details, click here: URL."
[0506] Step 4: Ticket purchase confirmation
[0507] Input: The user clicks on the received notification and operates the screen to indicate their desire to purchase.
[0508] Processing: The user terminal sends a purchase request to the server. The server receives this information and sets the purchase request flag for the corresponding user.
[0509] Output: The server updates the data with the purchase flag set.
[0510] Specific behavior: When the user taps the notification, the app opens and they click the "Want to buy" button.
[0511] Step 5: Automatic ticket purchase
[0512] Input: The server retrieves pre-stored personal information (e.g., name, credit card information) based on the user information for which the purchase wish flag is set.
[0513] Processing: The server uses this information to access ticket purchasing sites and perform automated form-fill and submission operations, for example, using web scraping techniques.
[0514] Output: The purchase is completed and the purchase confirmation is saved on the server.
[0515] Specific operation: The server automatically enters the user's name and credit card information into the purchase site's form and clicks the purchase button.
[0516] Step 6: Ticketing and Delivery
[0517] Input: The server generates a ticket in electronic format based on the purchase confirmation information.
[0518] Processing: The server adds the restriction information that prohibits resale, generates the ticket as a PDF file, and then sends the generated ticket to the user's terminal.
[0519] Output: The electronic ticket is sent to the user's terminal and saved.
[0520] Specific operation: The server uses a PDF generator to generate an electronic ticket containing a QR code, then BASE64 encodes it and sends it in JSON format to the user's device. The user can then view and save the ticket in the app.
[0521] (Application example 1)
[0522] 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."
[0523] The present invention aims to enable users to efficiently and quickly purchase or reserve products they are interested in, thereby reducing competition for popular products, and also to solve the problems of missed purchases and inventory shortages by enabling users to reliably receive products at physical stores.
[0524] 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.
[0525] In this invention, the server includes means for inputting product names and keywords of interest, means for searching for product information based on the input product names and keywords, means for sending a notification when sales of a product included in the searched product information begin, means for confirming a reservation request from a user who has received the notification, means for automatically reserving the product after confirming the reservation request, and means for allowing the reserved product to be picked up at a physical store. This allows users to reliably reserve products of interest and smoothly pick them up at the physical store.
[0526] "Goods" means any goods or services sold or provided.
[0527] "Product Names or Keywords of Interest" means names or related words associated with specific goods or services that you are interested in purchasing or reserving.
[0528] "Product information" refers to detailed information about a particular product, such as stock status, release date, price, specifications, etc.
[0529] "Availability" refers to the date and time when a particular product is officially available for purchase in the marketplace.
[0530] "Notification" means a message or alert that notifies a user of specific information or events.
[0531] A "reservation request" is a user's expression of intent to reserve a specific product in advance for purchase or collection at a later date.
[0532] "Means for automatically reserving products" refers to the process by which the system receives the user's intention and reserves a specific product without manual operation.
[0533] "Electronic format" refers to data or information recorded in digital form.
[0534] "Brick and mortar store" refers to a retail store that has a physical location and conducts face-to-face transactions with customers.
[0535] The present invention is a system that allows users to efficiently and quickly purchase or reserve products they are interested in. This system includes a means for inputting and searching for product names and keywords, a means for sending and receiving notifications, a means for automatically reserving products, and a means for receiving products at a physical store.
[0536] System Configuration
[0537] This system is constructed mainly using the following hardware and software.
[0538] 1. User Device
[0539] A smartphone application with an input function that allows users to input product names and keywords. It is implemented using the Android or iOS platform.
[0540] Push notification functionality to receive notifications and confirm reservation requests, using Google Firebase Cloud Messaging (FCM) and Apple Push Notification Service (APNs).
[0541] Provides an interface to display reservation completion and redemption information.
[0542] 2. Server
[0543] Product information is stored in a database and a means of searching for product information is provided using generative AI. The generative AI model is a generative AI (e.g., GPT-4).
[0544] A function that works with push notification services to send notifications to users.
[0545] A function that automatically processes product reservations. Reservation information is managed using a web framework such as Django and a task scheduler such as Celery.
[0546] A function that sends information to the user's device to pick up the product at a physical store.
[0547] System Operation
[0548] 1. Register your interest in products
[0549] A user uses a smartphone app to input product names and keywords that they are interested in. The input information is sent to the server.
[0550] 2. Search for product information
[0551] The server stores the received product names and keywords in a database and periodically searches the web and social media using the generative AI model to collect information about product availability and sales start dates.
[0552] Example: Prompt sentence to generative AI model: "Please check the stock status of limited edition premium shoes and notify the user when they are in stock."
[0553] 3. Sending notifications
[0554] When related product information appears in the search results, the server sends a push notification to the user's device, including the reservation start date and time and a URL.
[0555] Example: Notification: "Pre-orders for limited edition premium shoes have begun. Please see the link below for details."
[0556] 4. Automated booking process
[0557] The user receives the notification and clicks a button to select a reservation request, which causes the terminal to send the reservation request to the server.
[0558] The server automatically processes the reservation using pre-stored user information (such as name and contact information).
[0559] 5. Reservation confirmation and collection
[0560] When the reservation is completed, the server sends a reservation completion notice to the user terminal.
[0561] The user can present this notification at the physical store and pick up the reserved item.
[0562] The above system configuration and operation allows users to efficiently reserve and purchase products they are interested in and reliably pick them up at a physical store.
[0563] The flow of the specific processing in the application example 1 will be described with reference to FIG.
[0564] Step 1:
[0565] Users enter product names and keywords of interest into a smartphone app. After input, the device sends this information to a server. By sending the entered product names and keywords to the server, the data necessary for subsequent processing is provided.
[0566] Step 2:
[0567] The server stores the received product names and keywords in a database. This input data is used as a prompt for a generative AI model (e.g., GPT-4) to collect the latest information related to the product from the web and social media. By storing the information in the database, the server periodically searches using these keywords to check the latest sales start information and inventory information.
[0568] Step 3:
[0569] The server uses a web scraping tool (e.g., BeautifulSoup) to extract relevant product information. It passes prompts to a generative AI model, which analyzes the search results and extracts product information (e.g., stock availability, release date, etc.). The extracted data is then stored back in the database.
[0570] Step 4:
[0571] The server sends a push notification to the user when product information is updated. It uses a push notification service (e.g., Google FCM or Apple APNs) to send the notification to the user's device. In this step, the server compares the information in the database and sends the notification only if the new notification conditions are met.
[0572] Step 5:
[0573] The user receives a push notification, clicks the link in the notification to check the details, and selects whether they wish to make a reservation. The device then sends the reservation request to the server. By specifically communicating the user's intention to the server, the automatic reservation process begins.
[0574] Step 6:
[0575] The server automatically processes reservations based on pre-stored user information (such as name and contact information). The server then enters the necessary information into a pre-set reservation form and confirms the product reservation. Because reservations are made automatically, it saves the user time and effort.
[0576] Step 7:
[0577] Once the reservation process is complete, the server sends the user a confirmation notification, which includes details on how to collect the reserved item and the physical store location, so the user knows exactly how to secure and collect the reserved item.
[0578] Step 8:
[0579] The user presents the notification to the physical store and collects the reserved product. The collection procedure at the physical store is carried out based on confirmation and verification by the store staff. Once collection is complete, the entire system process is completed.
[0580] 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.
[0581] The present invention is a system that recognizes a user's emotions and assists in purchasing event tickets based on those emotions. This system operates by combining a user terminal, a server, an emotion engine, and a generation AI. Specific embodiments are described below.
[0582] User event registration and emotion recognition
[0583] 1. User event registration
[0584] A user launches the application and enters the name of an event or keyword they are interested in, for example, "Rock Festival 2024."
[0585] The terminal transmits the input event name and keywords to the server.
[0586] 2. Emotional Recognition
[0587] The device is equipped with a camera and microphone, and the emotion engine analyzes the user's facial expressions and tone of voice.
[0588] The emotion engine analyzes the user's emotion data in real time to determine the user's emotional state for the events entered by the user.
[0589] Event information monitoring and notification
[0590] 1. Event information monitoring
[0591] The server stores the required event names and keywords in a database, and then uses generative AI to periodically collect relevant event information from web searches and social networking services (SNS).
[0592] 2. Sending notifications
[0593] When the collected event information is related to the start of ticket sales, the server sends a push notification to the device, and the emotion engine customizes the content of the notification based on the user's emotional state.
[0594] For example, if the user is excited, the notification will have emotional content such as "An event you can't miss! Check it out now."
[0595] Ticket purchase confirmation and automatic purchase
[0596] 1. User Verification
[0597] The user receives a notification, checks the details, and if they are interested in purchasing tickets, selects "I want to buy."
[0598] 2. Automatic ticket purchase
[0599] The device sends the user's purchase request to the server, which uses the stored user information (such as name and credit card information) to initiate the purchase process.
[0600] The server automatically accesses the ticket purchasing site, fills out the purchase form, and completes the process.
[0601] Ticket issuance and distribution
[0602] 1. Ticket issuance
[0603] Once the purchase is complete, the server generates an electronic version of the ticket, which is restricted from resale.
[0604] 2. Ticket Offer
[0605] The server sends the generated electronic ticket to the terminal, which stores the received ticket in the user's account and displays it as needed.
[0606] Specific examples
[0607] 1. User registration and emotion recognition flow
[0608] A user is interested in "Rock Festival 2024" and enters the event name "Rock Festival 2024" into the application.
[0609] The terminal sends the entered information to the server, which stores the event name in a database.
[0610] The emotion engine analyzes the user's facial expressions and tone of voice using the device's built-in camera and microphone to determine the user's emotional state.
[0611] 2. Customizing notifications
[0612] The server uses generative AI to periodically search the web and social media for information on "Rock Festival 2024 ticket sales."
[0613] When a sale is detected, the server sends a notification to the terminal.
[0614] If the emotion engine detects that the user is excited, the notification will be customized to say, "An event you absolutely cannot miss! Check it out now."
[0615] This allows users to receive event notifications at the right time and in the right way based on their emotions, allowing them to secure tickets when they are most interested in them. It also prevents ticket resale issues, improving the ticket purchasing experience.
[0616] The processing flow will be explained below.
[0617] Step 1:
[0618] A user launches the application and enters the name of an event or keyword they are interested in, for example, "Rock Festival 2024."
[0619] Step 2:
[0620] The device sends the input event name and keywords to the server. The transmitted data includes the event name "Rock Festival 2024."
[0621] Step 3:
[0622] The server stores the received event names and keywords in a database, then uses generative AI to schedule collection of related event information from the web and social media.
[0623] Step 4:
[0624] The device uses a camera and microphone to collect the user's facial expressions and tone of voice, and the emotion engine analyzes this data in real time to determine the user's emotional state.
[0625] Step 5:
[0626] The server uses generative AI to periodically search for relevant information, such as "Rock Festival 2024 ticket sales," and collects any new information it finds.
[0627] Step 6:
[0628] The server sends push notifications to the device based on the collected information. The content of the notification is customized according to the user's emotional state. For example, if the user is excited, the notification might say, "This is an event you definitely can't miss! Check it out now."
[0629] Step 7:
[0630] The user receives a push notification, checks the details of the event, and clicks the button to select "I want to buy."
[0631] Step 8:
[0632] The terminal transmits the user's purchase request to the server. The transmitted data includes "Event name: Rock Festival 2024" and "Purchase request: Yes."
[0633] Step 9:
[0634] When the server receives the purchase request, it uses the pre-stored user information (name, credit card information, etc.) to access the specified ticket purchase site. For example, it accesses "https: / / example.com / ticket-purchase."
[0635] Step 10:
[0636] The server automatically fills in the necessary information on the purchase site's form, including the user's name, credit card number, and expiration date.
[0637] Step 11:
[0638] After the form is filled out, the server executes the purchase process. If the purchase is successful, the server receives a "ticket purchase successful" message.
[0639] Step 12:
[0640] Once the purchase is complete, the server generates the ticket in electronic format, with a no-resale restriction attached to the electronic ticket.
[0641] Step 13:
[0642] The server sends the generated electronic ticket to the terminal. The sent data includes "Electronic ticket ID: 987654321" and "Not for resale."
[0643] Step 14:
[0644] The device stores the received e-ticket in the user's account and provides the functionality to display it as needed. The user can check the ticket within the application.
[0645] Through these steps, users can obtain event tickets in a more personalized way using emotion recognition, and the problem of ticket resale can be prevented.
[0646] Example 2
[0647] 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."
[0648] Conventional ticket purchasing systems provide uniform notifications without considering the user's emotional state, making it impossible to effectively provide information at a time when users are interested. Furthermore, the manual ticket purchasing process required an inconvenient purchasing experience. Furthermore, fraudulent transactions due to ticket resale after purchase were a problem.
[0649] 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.
[0650] In this invention, the server includes means for inputting an event name or keyword of interest, means for searching for event information based on the input event name or keyword, means for sending a notification when tickets for the event included in the searched event information go on sale, means for confirming the purchase intention of the user who received the notification, means for automatically purchasing the ticket after confirming the purchase intention, means for attaching a no-resale restriction to the purchased ticket and providing it in an electronic format, means for recognizing the user's emotion, and means for customizing the content of the notification based on the recognized emotion. This allows for notifications to be sent with optimal timing and content according to the user's emotional state, enabling easy and automatic ticket purchases and preventing resale issues.
[0651] "Event names and keywords of interest" are the names of events and related words that interest users and are the subject of searches and notifications.
[0652] "Event Information" refers to data and news related to a specific event collected from websites and social networking services.
[0653] The "means for sending a notification when ticket sales begin" is a mechanism for sending a push notification to the user's device when ticket sales for an event begin.
[0654] "Means for confirming purchase intent" refers to the interface or process by which a user confirms their intention to purchase a ticket.
[0655] The "means for automatically purchasing tickets" is a system in which, after the user's purchase request has been confirmed, the server automatically carries out the ticket purchase procedure based on the user information stored on the server.
[0656] "Means of providing tickets in electronic format with restrictions preventing resale" refers to a system in which purchased tickets are provided to users in electronic format with restrictions attached to prevent resale.
[0657] "Means for recognizing emotions" refers to technologies or systems that analyze a user's facial expressions and tone of voice to determine their emotional state at that time.
[0658] "Means for customizing notification content based on emotions" refers to a mechanism that adjusts the wording and content of notifications sent according to the user's recognized emotional state.
[0659] This invention is a system that recognizes a user's emotions and supports the purchase of event tickets based on those emotions. This system operates by combining a user terminal, a server, an emotion engine, and a generation AI.
[0660] User event registration and emotion recognition
[0661] 1. The user launches the application and enters the name of an event or keyword they are interested in. For example, they might enter "Rock Festival 2024."
[0662] 2. The device sends the entered event name and keywords to the server.
[0663] 3. The device is equipped with a camera and microphone, and the emotion engine analyzes the user's facial expressions and tone of voice.
[0664] 4. The emotion engine analyzes the user's emotion data in real time and determines the user's emotional state for the events entered by the user.
[0665] Event information monitoring and notification
[0666] 1. The server stores the required event names and keywords in a database.
[0667] 2. The server periodically collects relevant event information from web searches and social networking services (SNS) using generative AI.
[0668] 3. If the collected event information is related to the start of ticket sales, the server sends a push notification to the device. At this time, the emotion engine customizes the content of the notification based on the user's emotional state. For example, if the user is excited, the server sends a notification with the content "This is an event you cannot miss! Check it out now!"
[0669] Ticket purchase confirmation and automatic purchase
[0670] 1. The user receives a notification, checks the details, and if they are interested in purchasing a ticket, selects "I want to buy."
[0671] 2. The terminal sends the user's purchase request to the server.
[0672] 3. The server initiates the purchase process using the stored user information (name, credit card information, etc.).
[0673] 4. The server automatically accesses the ticket purchasing site, fills in the purchase form, and completes the process.
[0674] Ticket issuance and distribution
[0675] 1. Once the purchase is complete, the server generates an electronic ticket, which is restricted from resale.
[0676] 2. The server sends the generated electronic ticket to the terminal, which stores it in the user's account and displays it as needed.
[0677] Specific examples
[0678] User registration and emotion recognition flow
[0679] A user is interested in "Rock Festival 2024" and enters the event name "Rock Festival 2024" into the application.
[0680] The terminal sends the entered information to the server, which stores the event name in a database.
[0681] Using the device's built-in camera and microphone, the emotion engine analyzes the user's facial expressions and tone of voice to determine their emotional state.
[0682] Customizing notifications
[0683] The server uses generative AI to periodically search the web and social media for information on "Rock Festival 2024 ticket sales."
[0684] When a sale is detected, the server sends a notification to the terminal.
[0685] If the emotion engine detects that the user is excited, the notification will be customized to say, "An event you absolutely cannot miss! Check it out now."
[0686] An example prompt is, "Get real-time ticket sales information for Rock Festival 2024 and optimize the notification content based on user sentiment."
[0687] This allows users to receive event notifications at the right time and in the right way based on their emotions, allowing them to secure tickets when they are most interested in them. It also prevents ticket resale issues, improving the ticket purchasing experience.
[0688] The flow of the identification process in the second embodiment will be described with reference to FIG.
[0689] Step 1:
[0690] User event registration
[0691] The user launches the application and enters the name of an event or keywords of interest. An example input is "Rock Festival 2024." The device sends this information to the server. The input here is the event name or keywords, and the first output is the user's search intent, which is sent to the server.
[0692] Step 2:
[0693] emotion recognition
[0694] The device is equipped with a camera and microphone, which capture the user's facial expressions and tone of voice. The emotion engine analyzes this captured data in real time to determine the user's emotional state. For example, if the user is smiling, it is determined to be "excited." The input is the captured facial and voice data, and the output is the analyzed user's emotional state. The device sends this information to a server.
[0695] Step 3:
[0696] Monitoring event information
[0697] The server stores the received event names and keywords in a database. Using generative AI, the server periodically collects related event information from web searches and social networking services (SNS). Specifically, it inputs a search query as a prompt and uses the generative AI model to output newly discovered event information. This output is stored in the database and updated as necessary.
[0698] Step 4:
[0699] Sending notifications
[0700] The server pushes the collected event information to the user's device. At this time, the emotion engine customizes the notification content. For example, if the analysis finds that the user is excited, a notification such as "This is an event you absolutely cannot miss! Check it out now" is sent. The input is the collected event information and the analyzed emotional state, and the output is the customized notification content.
[0701] Step 5:
[0702] Ticket purchase confirmation
[0703] The user receives a push notification. If the user sees the notification and is interested in purchasing a ticket, they select "purchase" within the application. The input is the user's selection information, and the output is the purchase request information sent to the server.
[0704] Step 6:
[0705] Automatic ticket purchase
[0706] The terminal sends the user's purchase request to the server. The server uses the saved user information (e.g., name, credit card information) to access the ticket purchasing site and automatically enter the required information. The input is the user's purchase request and saved personal information, and the output is confirmation of the completed ticket purchase.
[0707] Step 7:
[0708] Ticketing and distribution
[0709] Once the ticket purchase is complete, the server generates an electronic ticket and adds a non-resale restriction. The generated electronic ticket is sent to the terminal, which then stores the received ticket in the user's account. The input is the purchase completion information, and the output is the electronic ticket.
[0710] These steps allow users to receive event notifications at the most convenient time and in the most convenient way, purchase tickets conveniently and efficiently, and prevent ticket resale issues.
[0711] (Application example 2)
[0712] 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."
[0713] Conventional event ticket purchasing systems simply notify users of event information and are unable to consider the user's emotional state or interests, making it difficult to maximize the user's purchasing motivation. Furthermore, in brick-and-mortar stores, product recommendations are not based on the user's emotions, making it difficult to effectively promote products at the right time. This leaves the improvement of user satisfaction and purchasing experience as a challenge.
[0714] The identification process by the identification processing unit 290 of the data processing device 12 in Application Example 2 is realized by the following means. In this invention, the server includes means for recognizing emotions, means for inputting an event name or keyword of interest, means for searching for event information based on the input event name or keyword, means for sending a notification when ticket sales for an event included in the searched event information begin, means for customizing the content of the notification according to the user's emotional state, means for confirming the purchase intention of the user who received the notification, means for automatically purchasing tickets after confirming the purchase intention, and means for attaching a non-resale restriction to purchased tickets and providing them in an electronic format. This enables notifications and promotions to be provided at the appropriate time based on the user's emotions, maximizing the user's interest.
[0715] - "Means for recognizing emotions" refers to a function that analyzes the user's facial expressions and tone of voice to determine their emotional state in real time.
[0716] The "means for inputting the event name or keyword of interest" is an interface through which the user inputs the event name or keyword on the application and transmits the data to the server.
[0717] The "means for searching for event information" is a function that allows the server to collect related event information from the web or social networking services based on the input event name or keywords.
[0718] The "means for sending a notification" is a function for sending a push notification to a user terminal based on the event information collected by the server.
[0719] The "means for customizing notification content according to emotional state" is a function in which the emotion engine analyzes the user's emotional state and changes the notification content based on the results.
[0720] The "means for confirming purchase intent" is a function that allows the user to confirm their willingness to purchase tickets through the application after receiving the notification.
[0721] The "means for automatically purchasing tickets" is a function in which the server automatically purchases tickets using the stored user information after the user's purchase request has been confirmed.
[0722] "Means for adding restrictions preventing resale and providing them in electronic format" is a function that adds restrictions to purchased tickets on the system to prevent resale and provides them to users in electronic format.
[0723] This invention is a system that recognizes a user's emotions and supports the purchase of event tickets based on those emotions. This system operates by combining a user terminal, a server, an emotion engine, and a generation AI. Specific embodiments are described below.
[0724] Hardware Configuration
[0725] User terminal
[0726] The user device consists of a device equipped with a camera and microphone, such as smart glasses, a smartphone, or a head-mounted display, which collects the user's facial expressions and tone of voice in real time.
[0727] server
[0728] The server has high-performance computing resources to run the emotion engine and generative AI model.
[0729] Specific software used includes Microsoft Azure Emotion API for the emotion engine and OpenAI's GPT-3 for the generative AI model.
[0730] Software Configuration
[0731] Emotion Recognition Module
[0732] The emotion recognition module collects the user's facial expressions and tone of voice through the camera and microphone installed on the user's device, and analyzes the data using the Microsoft Azure Emotion API, thereby recognizing the user's emotional state in real time.
[0733] Event information collection module
[0734] The event information collection module is implemented on the server and automatically collects event information of interest from the web and social networking services. This module periodically monitors the Internet to obtain new event information.
[0735] Notification Customization Module
[0736] The notification customization module analyzes the user's emotional state based on data from the emotion recognition module. Using a generative AI model, it customizes the notification content based on the user's emotions. For example, if the user is excited, it generates a strong message saying, "This is an event you can't miss! Check it out now!"
[0737] Automatic ticket purchasing module
[0738] The automatic ticket purchasing module automatically purchases tickets using the saved user information after confirming the user's purchase request. During this process, the server automatically fills in the purchase form and provides the necessary information.
[0739] Electronic ticket provision module
[0740] The electronic ticket providing module assigns a non-resale restriction to the purchased ticket and sends it to the user's terminal in electronic format. This ticket is stored in the user's account and displayed as needed.
[0741] Specific examples
[0742] A user puts on smart glasses and expresses interest in a particular event.
[0743] 1. The camera and microphone on the user's device collect the user's facial expressions and tone of voice, recognizing emotions in real time.
[0744] 2. The server monitors web and social networking services to collect certain event information.
[0745] 3. Based on the user's emotional state, the generative AI model will customize and send a notification saying, "This event is a must-see!"
[0746] 4. After the user receives the notification and confirms their purchase, the server automatically purchases the tickets and provides them in electronic format.
[0747] Examples of prompt statements
[0748] Emotion Recognition Data Analysis Prompt: "Analyze the user's facial expression and tone of voice and output their current emotional state."
[0749] Product suggestion generation prompt: "Generate product suggestions when the user is excited. For example, limited edition items."
[0750] This system enables notifications and promotions to be delivered at the right time based on the user's emotions, maximizing the user's interest and improving user satisfaction.
[0751] The flow of the specific processing in the application example 2 will be described with reference to FIG.
[0752] Step 1:
[0753] The user puts on the smart glasses and launches the application. The user inputs the name of an event or keyword of interest (e.g., "Rock Festival 2024") by voice or text. The input data is then sent from the user's device to the server.
[0754] Step 2:
[0755] The server passes the received event name and keywords to an event information collection module, which searches for related event information from the web and social networking services based on the input event name and keywords and stores it in a database.
[0756] Step 3:
[0757] The camera and microphone on the user's device continuously capture the user's facial expressions and tone of voice, and send the data to the server in real time. The emotion recognition module analyzes the collected data using the Microsoft Azure Emotion API to recognize the user's emotional state. The input is the user's facial and voice data, and the output is their emotional state (e.g., "excited").
[0758] Step 4:
[0759] The server determines the notification content based on the event information and the user's emotional state. The notification customization module uses a generative AI model (e.g., OpenAI's GPT-3) to generate notification content based on the prompt. The input is the event information and the user's emotional state, and the output is a customized notification. It generates a strong message such as "This event is a must-see!"
[0760] Step 5:
[0761] The server pushes the customized notification to the user's device and waits until the user confirms the notification and responds. For example, the user selects "purchase request" and sends the response from the device to the server.
[0762] Step 6:
[0763] The server receives the user's purchase request, and the automatic ticket purchasing module starts the purchase process. Using saved user information (name, credit card information, etc.), the module automatically accesses the ticket purchasing site, fills in a form, and makes the purchase. The input is the user's purchase request and saved user information, and the output is a notification of purchase completion.
[0764] Step 7:
[0765] After the purchase is complete, the server assigns a no-resale restriction to the purchased ticket and provides it in electronic format. The electronic ticket provision module generates an electronic ticket and sends it to the user's terminal. The user terminal stores the received electronic ticket in the user's account and can display it as needed. The input is purchase completion information, and the output is the electronic ticket.
[0766] 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.
[0767] 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.
[0768] 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.
[0769] [Third embodiment]
[0770] FIG. 5 shows an example of the configuration of a data processing system 310 according to the third embodiment.
[0771] 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.
[0772] 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).
[0773] 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.
[0774] 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.
[0775] 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).
[0776] 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.
[0777] 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.
[0778] 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.
[0779] 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.
[0780] 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.
[0781] 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."
[0782] The system of the present invention is an automated ticket purchasing system that allows users to easily obtain tickets for events of interest and simultaneously solves the problem of ticket resale. This system operates using a user terminal, a server, and a generation AI. Specific embodiments are described below.
[0783] 1. User event registration
[0784] The user inputs the event name or keyword of interest into the user terminal, via an application or a web interface.
[0785] The terminal transmits the input event name and keywords to the server.
[0786] 2. Event information monitoring
[0787] The server stores the received event names and keywords in a database.
[0788] The server uses generative AI to periodically search the web and social networking services (SNS) to find ticket sales information for the event.
[0789] 3. Sending notifications
[0790] If the server detects relevant ticket sales information, it sends a push notification to the user's device, letting the user know that tickets for the event are now on sale.
[0791] 4. Ticket purchase confirmation and automatic purchase
[0792] The user receives the notification and performs an operation to confirm the purchase request, for example, by clicking the "Request to Purchase" button in the notification.
[0793] The terminal transmits the user's purchase request to the server, which then initiates the purchase procedure.
[0794] The server uses pre-saved user information (such as name and credit card information) to access the designated ticket purchasing site and automatically complete the purchase procedure.
[0795] 5. Ticket issuance and anti-resale measures
[0796] After the purchase process is completed, the server generates an electronic ticket, which includes a restriction that prohibits resale.
[0797] The server transmits the generated electronic ticket to the user terminal.
[0798] The terminal stores the received electronic ticket in the user's account so that it can be displayed as needed.
[0799] Specific examples
[0800] 1. User registration and notification flow
[0801] A user is interested in "Rock Festival 2024" and enters the event name "Rock Festival 2024" into the application.
[0802] The terminal sends the entered information to the server, which stores the event name in a database.
[0803] The server uses generative AI to periodically search the web and social media for information on "Rock Festival 2024 ticket sales."
[0804] When sales information is detected, the server sends a notification to the device, which includes the date and time the sale starts and a URL.
[0805] 2. Automating ticket purchasing
[0806] The user receives the notification, checks the details, and then clicks a button to select their purchase.
[0807] The terminal transmits a purchase request to the server, and the server accesses the ticket purchase site.
[0808] The server automatically fills in the purchase form using pre-stored user information (name, credit card information) and completes the purchase process.
[0809] 3. Issuance and provision of tickets
[0810] The server generates the ticket in electronic format immediately upon purchase and includes a no-resale restriction.
[0811] The server sends the generated ticket to the terminal, which stores it in the user's account for viewing.
[0812] This allows users to easily obtain tickets for the events they want and also prevents the problem of resale.
[0813] The processing flow will be explained below.
[0814] Step 1:
[0815] A user launches the application and enters the name of an event or keyword they are interested in, for example, "Rock Festival 2024."
[0816] Step 2:
[0817] The device sends the input event name and keywords to the server. The transmitted data includes the event name, such as "Rock Festival 2024."
[0818] Step 3:
[0819] The server stores the received event names and keywords in a database, then starts the generation AI, which periodically searches for related event information from the web and social media.
[0820] Step 4:
[0821] The server collects relevant event information from the search results, such as "Ticket sales for Rock Festival 2024 have begun."
[0822] Step 5:
[0823] The server then sends a push notification to the device based on the collected information, including the date and time when tickets for the event go on sale and the URL where they can be purchased.
[0824] Step 6:
[0825] The user checks the notification received on the device, confirms the details of the event, and clicks the "Purchase" button to select whether they wish to purchase the item.
[0826] Step 7:
[0827] The terminal transmits the user's purchase request to the server, which includes information such as "Event name: Rock Festival 2024" and "Purchase request: Yes."
[0828] Step 8:
[0829] When the server receives the purchase request, it uses the pre-stored user information to access the specified ticket purchase site, for example, "https: / / example.com / ticket-purchase."
[0830] Step 9:
[0831] The server automatically fills in the necessary information (such as name and credit card information) on the purchase site form, which is provided by the user in advance.
[0832] Step 10:
[0833] The server executes the purchase process and receives a success notification, such as a message saying "ticket purchase successful."
[0834] Step 11:
[0835] Once the purchase is complete, the server generates the ticket in electronic format, with a no-resale restriction attached to the ticket.
[0836] Step 12:
[0837] The server then sends the generated electronic ticket to the terminal, which includes data such as "Electronic ticket ID: 987654321" and "Not for resale."
[0838] Step 13:
[0839] The device stores the received e-ticket in the user's account and makes it available for viewing as needed. The user can view the ticket within the application.
[0840] By following these steps, users can easily and reliably obtain tickets to events they are interested in, while also preventing the problem of resale.
[0841] Example 1
[0842] 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."
[0843] When purchasing event tickets, it is important to ensure that users can quickly and accurately obtain tickets for their desired event while preventing the problem of resale. In particular, tickets for popular events tend to sell out quickly, and resellers often buy up all the tickets, making it difficult for ordinary users to purchase them at the regular price. Furthermore, manually gathering information on the Internet is time-consuming and inefficient.
[0844] 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.
[0845] In this invention, the server includes means for inputting an event name or keyword of interest, means for searching for event information based on the input event name or keyword, means for sending a notification when tickets for the event included in the searched event information go on sale, means for confirming a purchase intention of a user who received the notification, means for automatically purchasing tickets after confirming the purchase intention, means for providing the purchased tickets in an electronic format with a no-resale restriction, and means for periodically searching the web and social networking services using a generative language model. This allows users to efficiently obtain tickets for desired events and prevents resale problems.
[0846] "Means for inputting the name of an event or keywords of interest" refers to an interface that allows a user to input the name of an event that the user is interested in or wishes to participate in, or related keywords, into the terminal.
[0847] "Means for searching event information" refers to software and algorithms for retrieving related information from websites and social networking services on the Internet based on the event name or keywords entered.
[0848] "Means for sending notifications" refers to push notifications or message sending functions that notify user devices that tickets for an event are on sale.
[0849] "Means for confirming purchase intention" refers to the interface that allows the user to perform an operation to indicate their intention to purchase a ticket in response to the notification they received, and the function that receives and processes this information.
[0850] "Means for automatically purchasing tickets" refers to software and algorithms that, after confirming a user's purchase request, access a designated ticket purchasing site using pre-saved user information, automatically input and submit the necessary information to make the purchase.
[0851] "Means for adding a restriction that prevents resale and providing it in electronic format" refers to the function of adding a restriction that prevents resale of a ticket after purchase, generating it as an electronic ticket, and providing it to the user's terminal.
[0852] "Means for searching using generative language models" refers to the ability to utilize generative AI models to periodically extract and analyze event ticket sales information from large datasets using natural language processing techniques.
[0853] The system of the present invention is an automatic purchasing system that allows users to easily obtain tickets for events they are interested in, while at the same time solving the problem of ticket resale. This system is built using a user terminal, a server, and a generative language model.
[0854] First, a user uses their device to enter the name of an event or keywords they are interested in, such as "Rock Festival 2024," using a smartphone application or web browser. This entry is made through the device's interface, and the information is sent to the server using the HTTPS protocol.
[0855] The server then stores the received event names and keywords in a relational database (e.g., MySQL). The stored data is then used to search for relevant information from websites and social networking services (SNS) on the Internet using a generative AI model (e.g., OpenAI GPT-4) running on the server. This search is performed periodically and uses APIs for web search (e.g., Google Custom Search API) and APIs for SNS (e.g., Twitter API).
[0856] The server analyzes the search results, and when it detects ticket sales information related to a specific event, it sends a notification to the user's device. This notification is sent using a push notification API (e.g., Firebase Cloud Messaging, Apple Push Notification Service). The notification content may include information such as "Ticket sales for Rock Festival 2024 have begun. For details, click here: URL."
[0857] The user receives the notification, checks the details, and then performs an operation to indicate their desire to purchase. Specifically, they click the "Request to Purchase" button in the notification. This operation causes the user's device to send a request to purchase to the server. This information is also sent via the REST API.
[0858] The server receives the user's purchase request, accesses the specified ticket purchasing site (e.g., Ticketmaster, e+) using pre-stored user information (e.g., name, credit card information), and automatically completes the purchase process, which includes using web scraping technology to automatically fill in forms and click necessary buttons.
[0859] Once the purchase is complete, the server instantly generates an electronic ticket with a no-resale restriction. This electronic ticket is generated as a PDF file containing a QR code and embedded restriction information. The generated electronic ticket is sent from the server to the user's device, where it is stored in local storage or a database (e.g., SQLite) and can be displayed as needed.
[0860] This allows users to quickly and efficiently obtain tickets for their desired events, and effectively prevents resale issues.
[0861] As a concrete example, a user is interested in "Rock Festival 2024" and enters the event name into the application. The server then periodically searches the web and social media for information on "Rock Festival 2024 ticket sales," and sends a notification to the user when it finds sales information. When the user receives the notification and clicks "I want to buy," the server automatically processes the ticket purchase, generates an electronic ticket, and sends it to the user's device.
[0862] Example prompt sentence:
[0863] "Please explain the flow of a system that automates ticket purchasing for events of interest to users and prevents resale. The system operates using a user device, a server, and a generative AI model."
[0864] The flow of the identification process in the first embodiment will be described with reference to FIG.
[0865] Step 1: Registering users for an event
[0866] Input: The user inputs the event name or keyword of interest into the interface of the user terminal.
[0867] Processing: The user terminal converts the input event name and keywords into JSON format and sends it to the server using the HTTPS protocol.
[0868] Output: The server stores the received event names and keywords in a database.
[0869] Specific operation: The user opens the event registration screen on the smartphone app, enters "Rock Festival 2024," and taps the send button.
[0870] Step 2: Monitor event information
[0871] Input: The server periodically generates search queries based on the event names and keywords saved in step 1.
[0872] Processing: The server uses the generative AI model to gather information from the web and social networking services, specifically by performing searches through the Google Custom Search API and Twitter API, and parsing the results.
[0873] Output: Extract relevant ticket sales information from the search results and temporarily store that information in a cache.
[0874] Specific operation: The server periodically performs searches for keywords such as "Rock Festival 2024 ticket sales," analyzes the obtained information, and stores it in a cache.
[0875] Step 3: Sending notifications
[0876] Input: The server prepares to send a notification to the user based on the ticket sales information found in step 2.
[0877] Processing: The server uses Firebase Cloud Messaging (FCM) or Apple Push Notification Service (APNS) to send a push notification to the user device.
[0878] Output: The user terminal displays the received notification.
[0879] Specific operation: The server sends a push notification with the notification content such as "Ticket sales for Rock Festival 2024 have begun. For details, click here: URL."
[0880] Step 4: Ticket purchase confirmation
[0881] Input: The user clicks on the received notification and operates the screen to indicate their desire to purchase.
[0882] Processing: The user terminal sends a purchase request to the server. The server receives this information and sets the purchase request flag for the corresponding user.
[0883] Output: The server updates the data with the purchase flag set.
[0884] Specific behavior: When the user taps the notification, the app opens and they click the "Want to buy" button.
[0885] Step 5: Automatic ticket purchase
[0886] Input: The server retrieves pre-stored personal information (e.g., name, credit card information) based on the user information for which the purchase wish flag is set.
[0887] Processing: The server uses this information to access ticket purchasing sites and perform automated form-fill and submission operations, for example, using web scraping techniques.
[0888] Output: The purchase is completed and the purchase confirmation is saved on the server.
[0889] Specific operation: The server automatically enters the user's name and credit card information into the purchase site's form and clicks the purchase button.
[0890] Step 6: Ticketing and Delivery
[0891] Input: The server generates a ticket in electronic format based on the purchase confirmation information.
[0892] Processing: The server adds the restriction information that prohibits resale, generates the ticket as a PDF file, and then sends the generated ticket to the user's terminal.
[0893] Output: The electronic ticket is sent to the user's terminal and saved.
[0894] Specific operation: The server uses a PDF generator to generate an electronic ticket containing a QR code, then BASE64 encodes it and sends it in JSON format to the user's device. The user can then view and save the ticket in the app.
[0895] (Application example 1)
[0896] 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."
[0897] The present invention aims to enable users to efficiently and quickly purchase or reserve products they are interested in, thereby reducing competition for popular products, and also to solve the problems of missed purchases and inventory shortages by enabling users to reliably receive products at physical stores.
[0898] 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.
[0899] In this invention, the server includes means for inputting product names and keywords of interest, means for searching for product information based on the input product names and keywords, means for sending a notification when sales of a product included in the searched product information begin, means for confirming a reservation request from a user who has received the notification, means for automatically reserving the product after confirming the reservation request, and means for allowing the reserved product to be picked up at a physical store. This allows users to reliably reserve products of interest and smoothly pick them up at the physical store.
[0900] "Goods" means any goods or services sold or provided.
[0901] "Product Names or Keywords of Interest" means names or related words associated with specific goods or services that you are interested in purchasing or reserving.
[0902] "Product information" refers to detailed information about a particular product, such as stock status, release date, price, specifications, etc.
[0903] "Availability" refers to the date and time when a particular product is officially available for purchase in the marketplace.
[0904] "Notification" means a message or alert that notifies a user of specific information or events.
[0905] A "reservation request" is a user's expression of intent to reserve a specific product in advance for purchase or collection at a later date.
[0906] "Means for automatically reserving products" refers to the process by which the system receives the user's intention and reserves a specific product without manual operation.
[0907] "Electronic format" refers to data or information recorded in digital form.
[0908] "Brick and mortar store" refers to a retail store that has a physical location and conducts face-to-face transactions with customers.
[0909] The present invention is a system that allows users to efficiently and quickly purchase or reserve products they are interested in. This system includes a means for inputting and searching for product names and keywords, a means for sending and receiving notifications, a means for automatically reserving products, and a means for receiving products at a physical store.
[0910] System Configuration
[0911] This system is constructed mainly using the following hardware and software.
[0912] 1. User Device
[0913] A smartphone application with an input function that allows users to input product names and keywords. It is implemented on the Android or iOS platform.
[0914] Push notification functionality to receive notifications and confirm reservation requests, using Google Firebase Cloud Messaging (FCM) and Apple Push Notification Service (APNs).
[0915] Provides an interface to display reservation completion and redemption information.
[0916] 2. Server
[0917] Product information is stored in a database and a means of searching for product information is provided using generative AI. The generative AI model is a generative AI (e.g., GPT-4).
[0918] A function that works with push notification services to send notifications to users.
[0919] A function that automatically processes product reservations. Reservation information is managed using a web framework such as Django and a task scheduler such as Celery.
[0920] A function that sends information to the user's device to pick up the product at a physical store.
[0921] System Operation
[0922] 1. Register your interest in products
[0923] A user uses a smartphone app to input product names and keywords that they are interested in. The input information is sent to the server.
[0924] 2. Search for product information
[0925] The server stores the received product names and keywords in a database and periodically searches the web and social media using the generative AI model to collect information about product availability and sales start dates.
[0926] Example: Prompt sentence to generative AI model: "Please check the stock status of limited edition premium shoes and notify the user when they are in stock."
[0927] 3. Sending notifications
[0928] When related product information appears in the search results, the server sends a push notification to the user's device, including the reservation start date and time and a URL.
[0929] Example: Notification: "Pre-orders for limited edition premium shoes have begun. Please see the link below for details."
[0930] 4. Automated booking process
[0931] The user receives the notification and clicks a button to select a reservation request, which causes the terminal to send the reservation request to the server.
[0932] The server automatically processes the reservation using pre-stored user information (such as name and contact information).
[0933] 5. Reservation confirmation and collection
[0934] When the reservation is completed, the server sends a reservation completion notice to the user terminal.
[0935] The user can present this notification at the physical store and pick up the reserved item.
[0936] The above system configuration and operation allows users to efficiently reserve and purchase products they are interested in and reliably pick them up at a physical store.
[0937] The flow of the specific processing in the application example 1 will be described with reference to FIG.
[0938] Step 1:
[0939] Users enter product names and keywords of interest into a smartphone app. After input, the device sends this information to a server. By sending the entered product names and keywords to the server, the data necessary for subsequent processing is provided.
[0940] Step 2:
[0941] The server stores the received product names and keywords in a database. This input data is used as a prompt for a generative AI model (e.g., GPT-4) to collect the latest information related to the product from the web and social media. By storing the information in the database, the server periodically searches using these keywords to check the latest sales start information and inventory information.
[0942] Step 3:
[0943] The server uses a web scraping tool (e.g., BeautifulSoup) to extract relevant product information. It passes prompts to a generative AI model, which analyzes the search results and extracts product information (e.g., stock availability, release date, etc.). The extracted data is then stored back in the database.
[0944] Step 4:
[0945] The server sends a push notification to the user when product information is updated. It uses a push notification service (e.g., Google FCM or Apple APNs) to send the notification to the user's device. In this step, the server compares the information in the database and sends the notification only if the new notification conditions are met.
[0946] Step 5:
[0947] The user receives a push notification, clicks the link in the notification to check the details, and selects whether they wish to make a reservation. The device then sends the reservation request to the server. By specifically communicating the user's intention to the server, the automatic reservation process begins.
[0948] Step 6:
[0949] The server automatically processes reservations based on pre-stored user information (such as name and contact information). The server then enters the necessary information into a pre-set reservation form and confirms the product reservation. Because reservations are made automatically, it saves the user time and effort.
[0950] Step 7:
[0951] Once the reservation process is complete, the server sends the user a confirmation notification, which includes details on how to collect the reserved item and the physical store location, so the user knows exactly how to secure and collect the reserved item.
[0952] Step 8:
[0953] The user presents the notification to the physical store and collects the reserved product. The collection procedure at the physical store is carried out based on confirmation and verification by the store staff. Once collection is complete, the entire system process is completed.
[0954] 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.
[0955] The present invention is a system that recognizes a user's emotions and assists in purchasing event tickets based on those emotions. This system operates by combining a user terminal, a server, an emotion engine, and a generation AI. Specific embodiments are described below.
[0956] User event registration and emotion recognition
[0957] 1. User event registration
[0958] A user launches the application and enters the name of an event or keyword they are interested in, for example, "Rock Festival 2024."
[0959] The terminal transmits the input event name and keywords to the server.
[0960] 2. Emotional Recognition
[0961] The device is equipped with a camera and microphone, and the emotion engine analyzes the user's facial expressions and tone of voice.
[0962] The emotion engine analyzes the user's emotion data in real time to determine the user's emotional state for the events entered by the user.
[0963] Event information monitoring and notification
[0964] 1. Event information monitoring
[0965] The server stores the required event names and keywords in a database, and then uses generative AI to periodically collect relevant event information from web searches and social networking services (SNS).
[0966] 2. Sending notifications
[0967] When the collected event information is related to the start of ticket sales, the server sends a push notification to the device, and the emotion engine customizes the content of the notification based on the user's emotional state.
[0968] For example, if the user is excited, the notification will have emotional content such as "An event you can't miss! Check it out now."
[0969] Ticket purchase confirmation and automatic purchase
[0970] 1. User Verification
[0971] The user receives a notification, checks the details, and if they are interested in purchasing tickets, selects "I want to buy."
[0972] 2. Automatic ticket purchase
[0973] The device sends the user's purchase request to the server, which uses the stored user information (such as name and credit card information) to initiate the purchase process.
[0974] The server automatically accesses the ticket purchasing site, fills out the purchase form, and completes the process.
[0975] Ticket issuance and distribution
[0976] 1. Ticket issuance
[0977] Once the purchase is complete, the server generates an electronic version of the ticket, which is restricted from resale.
[0978] 2. Ticket Offer
[0979] The server sends the generated electronic ticket to the terminal, which stores the received ticket in the user's account and displays it as needed.
[0980] Specific examples
[0981] 1. User registration and emotion recognition flow
[0982] A user is interested in "Rock Festival 2024" and enters the event name "Rock Festival 2024" into the application.
[0983] The terminal sends the entered information to the server, which stores the event name in a database.
[0984] The emotion engine analyzes the user's facial expressions and tone of voice using the device's built-in camera and microphone to determine the user's emotional state.
[0985] 2. Customizing notifications
[0986] The server uses generative AI to periodically search the web and social media for information on "Rock Festival 2024 ticket sales."
[0987] When a sale is detected, the server sends a notification to the terminal.
[0988] If the emotion engine detects that the user is excited, the notification will be customized to say, "An event you absolutely cannot miss! Check it out now."
[0989] This allows users to receive event notifications at the right time and in the right way based on their emotions, allowing them to secure tickets when they are most interested in them. It also prevents ticket resale issues, improving the ticket purchasing experience.
[0990] The processing flow will be explained below.
[0991] Step 1:
[0992] A user launches the application and enters the name of an event or keyword they are interested in, for example, "Rock Festival 2024."
[0993] Step 2:
[0994] The device sends the input event name and keywords to the server. The transmitted data includes the event name "Rock Festival 2024."
[0995] Step 3:
[0996] The server stores the received event names and keywords in a database, then uses generative AI to schedule collection of related event information from the web and social media.
[0997] Step 4:
[0998] The device uses a camera and microphone to collect the user's facial expressions and tone of voice, and the emotion engine analyzes this data in real time to determine the user's emotional state.
[0999] Step 5:
[1000] The server uses generative AI to periodically search for relevant information, such as "Rock Festival 2024 ticket sales," and collects any new information it finds.
[1001] Step 6:
[1002] The server sends push notifications to the device based on the collected information. The content of the notification is customized according to the user's emotional state. For example, if the user is excited, the notification might say, "This is an event you definitely can't miss! Check it out now."
[1003] Step 7:
[1004] The user receives a push notification, checks the details of the event, and clicks the button to select "I want to buy."
[1005] Step 8:
[1006] The terminal transmits the user's purchase request to the server. The transmitted data includes "Event name: Rock Festival 2024" and "Purchase request: Yes."
[1007] Step 9:
[1008] When the server receives the purchase request, it uses the pre-stored user information (name, credit card information, etc.) to access the specified ticket purchase site. For example, it accesses "https: / / example.com / ticket-purchase."
[1009] Step 10:
[1010] The server automatically fills in the necessary information on the purchase site's form, including the user's name, credit card number, and expiration date.
[1011] Step 11:
[1012] After the form is filled out, the server executes the purchase process. If the purchase is successful, the server receives a "ticket purchase successful" message.
[1013] Step 12:
[1014] Once the purchase is complete, the server generates the ticket in electronic format, with a no-resale restriction attached to the electronic ticket.
[1015] Step 13:
[1016] The server sends the generated electronic ticket to the terminal. The sent data includes "Electronic ticket ID: 987654321" and "Not for resale."
[1017] Step 14:
[1018] The device stores the received e-ticket in the user's account and provides the functionality to display it as needed. The user can check the ticket within the application.
[1019] Through these steps, users can obtain event tickets in a more personalized way using emotion recognition, and the problem of ticket resale can be prevented.
[1020] Example 2
[1021] 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."
[1022] Conventional ticket purchasing systems provide uniform notifications without considering the user's emotional state, making it impossible to effectively provide information at a time when users are interested. Furthermore, the manual ticket purchasing process required an inconvenient purchasing experience. Furthermore, fraudulent transactions due to ticket resale after purchase were a problem.
[1023] 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.
[1024] In this invention, the server includes means for inputting an event name or keyword of interest, means for searching for event information based on the input event name or keyword, means for sending a notification when tickets for the event included in the searched event information go on sale, means for confirming the purchase intention of the user who received the notification, means for automatically purchasing the ticket after confirming the purchase intention, means for attaching a no-resale restriction to the purchased ticket and providing it in an electronic format, means for recognizing the user's emotion, and means for customizing the content of the notification based on the recognized emotion. This allows for notifications to be sent with optimal timing and content according to the user's emotional state, enabling easy and automatic ticket purchases and preventing resale issues.
[1025] "Event names and keywords of interest" are the names of events and related words that interest users and are the subject of searches and notifications.
[1026] "Event Information" refers to data and news related to a specific event collected from websites and social networking services.
[1027] The "means for sending a notification when ticket sales begin" is a mechanism for sending a push notification to the user's device when ticket sales for an event begin.
[1028] "Means for confirming purchase intent" refers to the interface or process by which a user confirms their intention to purchase a ticket.
[1029] The "means for automatically purchasing tickets" is a system in which, after the user's purchase request has been confirmed, the server automatically carries out the ticket purchase procedure based on the user information stored on the server.
[1030] "Means of providing tickets in electronic format with restrictions preventing resale" refers to a system in which purchased tickets are provided to users in electronic format with restrictions attached to prevent resale.
[1031] "Means for recognizing emotions" refers to technologies or systems that analyze a user's facial expressions and tone of voice to determine their emotional state at that time.
[1032] "Means for customizing notification content based on emotions" refers to a mechanism that adjusts the wording and content of notifications sent according to the user's recognized emotional state.
[1033] This invention is a system that recognizes a user's emotions and supports the purchase of event tickets based on those emotions. This system operates by combining a user terminal, a server, an emotion engine, and a generation AI.
[1034] User event registration and emotion recognition
[1035] 1. The user launches the application and enters the name of an event or keyword they are interested in. For example, they might enter "Rock Festival 2024."
[1036] 2. The device sends the entered event name and keywords to the server.
[1037] 3. The device is equipped with a camera and microphone, and the emotion engine analyzes the user's facial expressions and tone of voice.
[1038] 4. The emotion engine analyzes the user's emotion data in real time and determines the user's emotional state for the events entered by the user.
[1039] Event information monitoring and notification
[1040] 1. The server stores the required event names and keywords in a database.
[1041] 2. The server periodically collects relevant event information from web searches and social networking services (SNS) using generative AI.
[1042] 3. If the collected event information is related to the start of ticket sales, the server sends a push notification to the device. At this time, the emotion engine customizes the content of the notification based on the user's emotional state. For example, if the user is excited, the server sends a notification with the content "This is an event you cannot miss! Check it out now!"
[1043] Ticket purchase confirmation and automatic purchase
[1044] 1. The user receives a notification, checks the details, and if they are interested in purchasing a ticket, selects "I want to buy."
[1045] 2. The terminal sends the user's purchase request to the server.
[1046] 3. The server initiates the purchase process using the stored user information (name, credit card information, etc.).
[1047] 4. The server automatically accesses the ticket purchasing site, fills in the purchase form, and completes the process.
[1048] Ticket issuance and distribution
[1049] 1. Once the purchase is complete, the server generates an electronic ticket, which is restricted from resale.
[1050] 2. The server sends the generated electronic ticket to the terminal, which stores it in the user's account and displays it as needed.
[1051] Specific examples
[1052] User registration and emotion recognition flow
[1053] A user is interested in "Rock Festival 2024" and enters the event name "Rock Festival 2024" into the application.
[1054] The terminal sends the entered information to the server, which stores the event name in a database.
[1055] Using the device's built-in camera and microphone, the emotion engine analyzes the user's facial expressions and tone of voice to determine their emotional state.
[1056] Customizing notifications
[1057] The server uses generative AI to periodically search the web and social media for information on "Rock Festival 2024 ticket sales."
[1058] When a sale is detected, the server sends a notification to the terminal.
[1059] If the emotion engine detects that the user is excited, the notification will be customized to say, "An event you absolutely cannot miss! Check it out now."
[1060] An example prompt is, "Get real-time ticket sales information for Rock Festival 2024 and optimize the notification content based on user sentiment."
[1061] This allows users to receive event notifications at the right time and in the right way based on their emotions, allowing them to secure tickets when they are most interested in them. It also prevents ticket resale issues, improving the ticket purchasing experience.
[1062] The flow of the identification process in the second embodiment will be described with reference to FIG.
[1063] Step 1:
[1064] User event registration
[1065] The user launches the application and enters the name of an event or keywords of interest. An example input is "Rock Festival 2024." The device sends this information to the server. The input here is the event name or keywords, and the first output is the user's search intent, which is sent to the server.
[1066] Step 2:
[1067] emotion recognition
[1068] The device is equipped with a camera and microphone, which capture the user's facial expressions and tone of voice. The emotion engine analyzes this captured data in real time to determine the user's emotional state. For example, if the user is smiling, it is determined to be "excited." The input is the captured facial and voice data, and the output is the analyzed user's emotional state. The device sends this information to a server.
[1069] Step 3:
[1070] Monitoring event information
[1071] The server stores the received event names and keywords in a database. Using generative AI, the server periodically collects related event information from web searches and social networking services (SNS). Specifically, it inputs a search query as a prompt and uses the generative AI model to output newly discovered event information. This output is stored in the database and updated as necessary.
[1072] Step 4:
[1073] Sending notifications
[1074] The server pushes the collected event information to the user's device. At this time, the emotion engine customizes the notification content. For example, if the analysis finds that the user is excited, a notification such as "This is an event you absolutely cannot miss! Check it out now" is sent. The input is the collected event information and the analyzed emotional state, and the output is the customized notification content.
[1075] Step 5:
[1076] Ticket purchase confirmation
[1077] The user receives a push notification. If the user sees the notification and is interested in purchasing a ticket, they select "purchase" within the application. The input is the user's selection information, and the output is the purchase request information sent to the server.
[1078] Step 6:
[1079] Automatic ticket purchase
[1080] The terminal sends the user's purchase request to the server. The server uses the saved user information (e.g., name, credit card information) to access the ticket purchasing site and automatically enter the required information. The input is the user's purchase request and saved personal information, and the output is confirmation of the completed ticket purchase.
[1081] Step 7:
[1082] Ticketing and distribution
[1083] Once the ticket purchase is complete, the server generates an electronic ticket and adds a non-resale restriction. The generated electronic ticket is sent to the terminal, which then stores the received ticket in the user's account. The input is the purchase completion information, and the output is the electronic ticket.
[1084] These steps allow users to receive event notifications at the most convenient time and in the most convenient way, purchase tickets conveniently and efficiently, and prevent ticket resale issues.
[1085] (Application example 2)
[1086] 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."
[1087] Conventional event ticket purchasing systems simply notify users of event information and are unable to consider the user's emotional state or interests, making it difficult to maximize the user's purchasing motivation. Furthermore, in brick-and-mortar stores, product recommendations are not based on the user's emotions, making it difficult to effectively promote products at the right time. This leaves the improvement of user satisfaction and purchasing experience as a challenge.
[1088] The identification process by the identification processing unit 290 of the data processing device 12 in Application Example 2 is realized by the following means. In this invention, the server includes means for recognizing emotions, means for inputting an event name or keyword of interest, means for searching for event information based on the input event name or keyword, means for sending a notification when ticket sales for an event included in the searched event information begin, means for customizing the content of the notification according to the user's emotional state, means for confirming the purchase intention of the user who received the notification, means for automatically purchasing tickets after confirming the purchase intention, and means for attaching a non-resale restriction to purchased tickets and providing them in an electronic format. This enables notifications and promotions to be provided at the appropriate time based on the user's emotions, maximizing the user's interest.
[1089] - "Means for recognizing emotions" refers to a function that analyzes the user's facial expressions and tone of voice to determine their emotional state in real time.
[1090] The "means for inputting the event name or keyword of interest" is an interface through which the user inputs the event name or keyword on the application and transmits the data to the server.
[1091] The "means for searching for event information" is a function that allows the server to collect related event information from the web or social networking services based on the input event name or keywords.
[1092] The "means for sending a notification" is a function for sending a push notification to a user terminal based on the event information collected by the server.
[1093] The "means for customizing notification content according to emotional state" is a function in which the emotion engine analyzes the user's emotional state and changes the notification content based on the results.
[1094] The "means for confirming purchase intent" is a function that allows the user to confirm their willingness to purchase tickets through the application after receiving the notification.
[1095] The "means for automatically purchasing tickets" is a function in which the server automatically purchases tickets using the stored user information after the user's purchase request has been confirmed.
[1096] "Means for adding restrictions preventing resale and providing them in electronic format" is a function that adds restrictions to purchased tickets on the system to prevent resale and provides them to users in electronic format.
[1097] This invention is a system that recognizes a user's emotions and supports the purchase of event tickets based on those emotions. This system operates by combining a user terminal, a server, an emotion engine, and a generation AI. Specific embodiments are described below.
[1098] Hardware Configuration
[1099] User terminal
[1100] The user device consists of a device equipped with a camera and microphone, such as smart glasses, a smartphone, or a head-mounted display, which collects the user's facial expressions and tone of voice in real time.
[1101] server
[1102] The server has high-performance computing resources to run the emotion engine and generative AI model.
[1103] Specific software used includes Microsoft Azure Emotion API for the emotion engine and OpenAI's GPT-3 for the generative AI model.
[1104] Software Configuration
[1105] Emotion Recognition Module
[1106] The emotion recognition module collects the user's facial expressions and tone of voice through the camera and microphone installed on the user's device, and analyzes the data using the Microsoft Azure Emotion API, thereby recognizing the user's emotional state in real time.
[1107] Event information collection module
[1108] The event information collection module is implemented on the server and automatically collects event information of interest from the web and social networking services. This module periodically monitors the Internet to obtain new event information.
[1109] Notification Customization Module
[1110] The notification customization module analyzes the user's emotional state based on data from the emotion recognition module. Using a generative AI model, it customizes the notification content based on the user's emotions. For example, if the user is excited, it generates a strong message saying, "This is an event you can't miss! Check it out now!"
[1111] Automatic ticket purchasing module
[1112] The automatic ticket purchasing module automatically purchases tickets using the saved user information after confirming the user's purchase request. During this process, the server automatically fills in the purchase form and provides the necessary information.
[1113] Electronic ticket provision module
[1114] The electronic ticket providing module assigns a non-resale restriction to the purchased ticket and sends it to the user's terminal in electronic format. This ticket is stored in the user's account and displayed as needed.
[1115] Specific examples
[1116] A user puts on smart glasses and expresses interest in a particular event.
[1117] 1. The camera and microphone on the user's device collect the user's facial expressions and tone of voice, recognizing emotions in real time.
[1118] 2. The server monitors web and social networking services to collect certain event information.
[1119] 3. Based on the user's emotional state, the generative AI model will customize and send a notification saying, "This event is a must-see!"
[1120] 4. After the user receives the notification and confirms their purchase, the server automatically purchases the tickets and provides them in electronic format.
[1121] Examples of prompt statements
[1122] Emotion Recognition Data Analysis Prompt: "Analyze the user's facial expression and tone of voice and output their current emotional state."
[1123] Product suggestion generation prompt: "Generate product suggestions when the user is excited. For example, limited edition items."
[1124] This system enables notifications and promotions to be delivered at the right time based on the user's emotions, maximizing the user's interest and improving user satisfaction.
[1125] The flow of the specific processing in the application example 2 will be described with reference to FIG.
[1126] Step 1:
[1127] The user puts on the smart glasses and launches the application. The user inputs the name of an event or keyword of interest (e.g., "Rock Festival 2024") by voice or text. The input data is then sent from the user's device to the server.
[1128] Step 2:
[1129] The server passes the received event name and keywords to an event information collection module, which searches for related event information from the web and social networking services based on the input event name and keywords and stores it in a database.
[1130] Step 3:
[1131] The camera and microphone on the user's device continuously capture the user's facial expressions and tone of voice, and send the data to the server in real time. The emotion recognition module analyzes the collected data using the Microsoft Azure Emotion API to recognize the user's emotional state. The input is the user's facial and voice data, and the output is their emotional state (e.g., "excited").
[1132] Step 4:
[1133] The server determines the notification content based on the event information and the user's emotional state. The notification customization module uses a generative AI model (e.g., OpenAI's GPT-3) to generate notification content based on the prompt. The input is the event information and the user's emotional state, and the output is a customized notification. It generates a strong message such as "This event is a must-see!"
[1134] Step 5:
[1135] The server pushes the customized notification to the user's device and waits until the user confirms the notification and responds. For example, the user selects "purchase request" and sends the response from the device to the server.
[1136] Step 6:
[1137] The server receives the user's purchase request, and the automatic ticket purchasing module starts the purchase process. Using saved user information (name, credit card information, etc.), the module automatically accesses the ticket purchasing site, fills in a form, and makes the purchase. The input is the user's purchase request and saved user information, and the output is a notification of purchase completion.
[1138] Step 7:
[1139] After the purchase is complete, the server assigns a no-resale restriction to the purchased ticket and provides it in electronic format. The electronic ticket provision module generates an electronic ticket and sends it to the user's terminal. The user terminal stores the received electronic ticket in the user's account and can display it as needed. The input is purchase completion information, and the output is the electronic ticket.
[1140] 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.
[1141] 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.
[1142] 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.
[1143] [Fourth embodiment]
[1144] FIG. 7 shows an example of the configuration of a data processing system 410 according to the fourth embodiment.
[1145] 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.
[1146] 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).
[1147] 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.
[1148] 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.
[1149] 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).
[1150] 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.
[1151] 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.
[1152] 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.
[1153] 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.
[1154] 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.
[1155] 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.
[1156] 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."
[1157] The system of the present invention is an automated ticket purchasing system that allows users to easily obtain tickets for events of interest and simultaneously solves the problem of ticket resale. This system operates using a user terminal, a server, and a generation AI. Specific embodiments are described below.
[1158] 1. User event registration
[1159] The user inputs the event name or keyword of interest into the user terminal, via an application or a web interface.
[1160] The terminal transmits the input event name and keywords to the server.
[1161] 2. Event information monitoring
[1162] The server stores the received event names and keywords in a database.
[1163] The server uses generative AI to periodically search the web and social networking services (SNS) to find ticket sales information for the event.
[1164] 3. Sending notifications
[1165] If the server detects relevant ticket sales information, it sends a push notification to the user's device, letting the user know that tickets for the event are now on sale.
[1166] 4. Ticket purchase confirmation and automatic purchase
[1167] The user receives the notification and performs an operation to confirm the purchase request, for example, by clicking the "Request to Purchase" button in the notification.
[1168] The terminal transmits the user's purchase request to the server, which then initiates the purchase procedure.
[1169] The server uses pre-saved user information (such as name and credit card information) to access the designated ticket purchasing site and automatically complete the purchase procedure.
[1170] 5. Ticket issuance and anti-resale measures
[1171] After the purchase process is completed, the server generates an electronic ticket, which includes a restriction that prohibits resale.
[1172] The server transmits the generated electronic ticket to the user terminal.
[1173] The terminal stores the received electronic ticket in the user's account so that it can be displayed as needed.
[1174] Specific examples
[1175] 1. User registration and notification flow
[1176] A user is interested in "Rock Festival 2024" and enters the event name "Rock Festival 2024" into the application.
[1177] The terminal sends the entered information to the server, which stores the event name in a database.
[1178] The server uses generative AI to periodically search the web and social media for information on "Rock Festival 2024 ticket sales."
[1179] When sales information is detected, the server sends a notification to the device, which includes the date and time the sale starts and a URL.
[1180] 2. Automating ticket purchasing
[1181] The user receives the notification, checks the details, and then clicks a button to select their purchase.
[1182] The terminal transmits a purchase request to the server, and the server accesses the ticket purchase site.
[1183] The server automatically fills in the purchase form using pre-stored user information (name, credit card information) and completes the purchase process.
[1184] 3. Issuance and provision of tickets
[1185] The server generates the ticket in electronic format immediately upon purchase and includes a no-resale restriction.
[1186] The server sends the generated ticket to the terminal, which stores it in the user's account for viewing.
[1187] This allows users to easily obtain tickets for the events they want and also prevents the problem of resale.
[1188] The processing flow will be explained below.
[1189] Step 1:
[1190] A user launches the application and enters the name of an event or keyword they are interested in, for example, "Rock Festival 2024."
[1191] Step 2:
[1192] The device sends the input event name and keywords to the server. The transmitted data includes the event name, such as "Rock Festival 2024."
[1193] Step 3:
[1194] The server stores the received event names and keywords in a database, then starts the generation AI, which periodically searches for related event information from the web and social media.
[1195] Step 4:
[1196] The server collects relevant event information from the search results, such as "Ticket sales for Rock Festival 2024 have begun."
[1197] Step 5:
[1198] The server then sends a push notification to the device based on the collected information, including the date and time when tickets for the event go on sale and the URL where they can be purchased.
[1199] Step 6:
[1200] The user checks the notification received on the device, confirms the details of the event, and clicks the "Purchase" button to select whether they wish to purchase the item.
[1201] Step 7:
[1202] The terminal transmits the user's purchase request to the server, which includes information such as "Event name: Rock Festival 2024" and "Purchase request: Yes."
[1203] Step 8:
[1204] When the server receives the purchase request, it uses the pre-stored user information to access the specified ticket purchase site, for example, "https: / / example.com / ticket-purchase."
[1205] Step 9:
[1206] The server automatically fills in the necessary information (such as name and credit card information) on the purchase site form, which is provided by the user in advance.
[1207] Step 10:
[1208] The server executes the purchase process and receives a success notification, such as a message saying "ticket purchase successful."
[1209] Step 11:
[1210] Once the purchase is complete, the server generates the ticket in electronic format, with a no-resale restriction attached to the ticket.
[1211] Step 12:
[1212] The server then sends the generated electronic ticket to the terminal, which includes data such as "Electronic ticket ID: 987654321" and "Not for resale."
[1213] Step 13:
[1214] The device stores the received e-ticket in the user's account and makes it available for viewing as needed. The user can view the ticket within the application.
[1215] By following these steps, users can easily and reliably obtain tickets to events they are interested in, while also preventing the problem of resale.
[1216] Example 1
[1217] 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."
[1218] When purchasing event tickets, it is important to ensure that users can quickly and accurately obtain tickets for their desired event while preventing the problem of resale. In particular, tickets for popular events tend to sell out quickly, and resellers often buy up all the tickets, making it difficult for ordinary users to purchase them at the regular price. Furthermore, manually gathering information on the Internet is time-consuming and inefficient.
[1219] 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.
[1220] In this invention, the server includes means for inputting an event name or keyword of interest, means for searching for event information based on the input event name or keyword, means for sending a notification when tickets for the event included in the searched event information go on sale, means for confirming a purchase intention of a user who received the notification, means for automatically purchasing tickets after confirming the purchase intention, means for providing the purchased tickets in an electronic format with a no-resale restriction, and means for periodically searching the web and social networking services using a generative language model. This allows users to efficiently obtain tickets for desired events and prevents resale problems.
[1221] "Means for inputting event names and keywords of interest" refers to an interface that allows users to input into a terminal the names of events that they are interested in or wish to participate in, as well as related keywords.
[1222] "Means for searching event information" refers to software and algorithms for retrieving related information from websites and social networking services on the Internet based on the event name or keywords entered.
[1223] "Means for sending notifications" refers to push notifications or message sending functions that notify user devices that tickets for an event are on sale.
[1224] "Means for confirming purchase intention" refers to the interface that allows the user to perform an operation to indicate their intention to purchase a ticket in response to the notification they received, and the function that receives and processes this information.
[1225] "Means for automatically purchasing tickets" refers to software and algorithms that, after confirming a user's purchase request, access a designated ticket purchasing site using pre-saved user information, automatically input and submit the necessary information to make the purchase.
[1226] "Means for adding a restriction that prevents resale and providing it in electronic format" refers to the function of adding a restriction that prevents resale of a ticket after purchase, generating it as an electronic ticket, and providing it to the user's terminal.
[1227] "Means for searching using generative language models" refers to the ability to utilize generative AI models to periodically extract and analyze event ticket sales information from large datasets using natural language processing techniques.
[1228] The system of the present invention is an automatic purchasing system that allows users to easily obtain tickets for events they are interested in, while at the same time solving the problem of ticket resale. This system is built using a user terminal, a server, and a generative language model.
[1229] First, a user uses their device to enter the name of an event or keywords they are interested in, such as "Rock Festival 2024," using a smartphone application or web browser. This entry is made through the device's interface, and the information is sent to the server using the HTTPS protocol.
[1230] The server then stores the received event names and keywords in a relational database (e.g., MySQL). The stored data is then used to search for relevant information from websites and social networking services (SNS) on the Internet using a generative AI model (e.g., OpenAI GPT-4) running on the server. This search is performed periodically and uses APIs for web search (e.g., Google Custom Search API) and APIs for SNS (e.g., Twitter API).
[1231] The server analyzes the search results, and when it detects ticket sales information related to a specific event, it sends a notification to the user's device. This notification is sent using a push notification API (e.g., Firebase Cloud Messaging, Apple Push Notification Service). The notification content may include information such as "Ticket sales for Rock Festival 2024 have begun. For details, click here: URL."
[1232] The user receives the notification, checks the details, and then performs an operation to indicate their desire to purchase. Specifically, they click the "Request to Purchase" button in the notification. This operation causes the user's device to send a request to purchase to the server. This information is also sent via the REST API.
[1233] The server receives the user's purchase request, accesses the specified ticket purchasing site (e.g., Ticketmaster, e+) using pre-stored user information (e.g., name, credit card information), and automatically completes the purchase process, which includes using web scraping technology to automatically fill in forms and click necessary buttons.
[1234] Once the purchase is complete, the server instantly generates an electronic ticket with a no-resale restriction. This electronic ticket is generated as a PDF file containing a QR code and embedded restriction information. The generated electronic ticket is sent from the server to the user's device, where it is stored in local storage or a database (e.g., SQLite) and can be displayed as needed.
[1235] This allows users to quickly and efficiently obtain tickets for their desired events, and effectively prevents resale issues.
[1236] As a concrete example, a user is interested in "Rock Festival 2024" and enters the event name into the application. The server then periodically searches the web and social media for information on "Rock Festival 2024 ticket sales," and sends a notification to the user when it finds sales information. When the user receives the notification and clicks "I want to buy," the server automatically processes the ticket purchase, generates an electronic ticket, and sends it to the user's device.
[1237] Example prompt sentence:
[1238] "Please explain the flow of a system that automates ticket purchasing for events of interest to users and prevents resale. The system operates using a user device, a server, and a generative AI model."
[1239] The flow of the identification process in the first embodiment will be described with reference to FIG.
[1240] Step 1: Registering users for an event
[1241] Input: The user inputs the event name or keyword of interest into the interface of the user terminal.
[1242] Processing: The user terminal converts the input event name and keywords into JSON format and sends it to the server using the HTTPS protocol.
[1243] Output: The server stores the received event names and keywords in a database.
[1244] Specific operation: The user opens the event registration screen on the smartphone app, enters "Rock Festival 2024," and taps the send button.
[1245] Step 2: Monitor event information
[1246] Input: The server periodically generates search queries based on the event names and keywords saved in step 1.
[1247] Processing: The server uses the generative AI model to gather information from the web and social networking services, specifically by performing searches through the Google Custom Search API and Twitter API, and parsing the results.
[1248] Output: Extract relevant ticket sales information from the search results and temporarily store that information in a cache.
[1249] Specific operation: The server periodically performs searches for keywords such as "Rock Festival 2024 ticket sales," analyzes the obtained information, and stores it in a cache.
[1250] Step 3: Sending notifications
[1251] Input: The server prepares to send a notification to the user based on the ticket sales information found in step 2.
[1252] Processing: The server uses Firebase Cloud Messaging (FCM) or Apple Push Notification Service (APNS) to send a push notification to the user device.
[1253] Output: The user terminal displays the received notification.
[1254] Specific operation: The server sends a push notification with the notification content such as "Ticket sales for Rock Festival 2024 have begun. For details, click here: URL."
[1255] Step 4: Ticket purchase confirmation
[1256] Input: The user clicks on the received notification and operates the screen to indicate their desire to purchase.
[1257] Processing: The user terminal sends a purchase request to the server. The server receives this information and sets the purchase request flag for the corresponding user.
[1258] Output: The server updates the data with the purchase flag set.
[1259] Specific behavior: When the user taps the notification, the app opens and they click the "Want to buy" button.
[1260] Step 5: Automatic ticket purchase
[1261] Input: The server retrieves pre-stored personal information (e.g., name, credit card information) based on the user information for which the purchase wish flag is set.
[1262] Processing: The server uses this information to access ticket purchasing sites and perform automated form-fill and submission operations, for example, using web scraping techniques.
[1263] Output: The purchase is completed and the purchase confirmation is saved on the server.
[1264] Specific operation: The server automatically enters the user's name and credit card information into the purchase site's form and clicks the purchase button.
[1265] Step 6: Ticketing and Delivery
[1266] Input: The server generates a ticket in electronic format based on the purchase confirmation information.
[1267] Processing: The server adds the restriction information that prohibits resale, generates the ticket as a PDF file, and then sends the generated ticket to the user's terminal.
[1268] Output: The electronic ticket is sent to the user's terminal and saved.
[1269] Specific operation: The server uses a PDF generator to generate an electronic ticket containing a QR code, then BASE64 encodes it and sends it in JSON format to the user's device. The user can then view and save the ticket in the app.
[1270] (Application example 1)
[1271] 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."
[1272] The present invention aims to enable users to efficiently and quickly purchase or reserve products they are interested in, thereby reducing competition for popular products, and also to solve the problems of missed purchases and inventory shortages by enabling users to reliably receive products at physical stores.
[1273] 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.
[1274] In this invention, the server includes means for inputting product names and keywords of interest, means for searching for product information based on the input product names and keywords, means for sending a notification when sales of a product included in the searched product information begin, means for confirming a reservation request from a user who has received the notification, means for automatically reserving the product after confirming the reservation request, and means for allowing the reserved product to be picked up at a physical store. This allows users to reliably reserve products of interest and smoothly pick them up at the physical store.
[1275] "Goods" means any goods or services sold or provided.
[1276] "Product Names or Keywords of Interest" means names or related words associated with specific goods or services that you are interested in purchasing or reserving.
[1277] "Product information" refers to detailed information about a particular product, such as stock status, release date, price, specifications, etc.
[1278] "Availability" refers to the date and time when a particular product is officially available for purchase in the marketplace.
[1279] "Notification" means a message or alert that notifies a user of specific information or events.
[1280] A "reservation request" is a user's expression of intent to reserve a specific product in advance for purchase or collection at a later date.
[1281] "Means for automatically reserving products" refers to the process by which the system receives the user's intention and reserves a specific product without manual operation.
[1282] "Electronic format" refers to data or information recorded in digital form.
[1283] "Brick and mortar store" refers to a retail store that has a physical location and conducts face-to-face transactions with customers.
[1284] The present invention is a system that allows users to efficiently and quickly purchase or reserve products they are interested in. This system includes a means for inputting and searching for product names and keywords, a means for sending and receiving notifications, a means for automatically reserving products, and a means for receiving products at a physical store.
[1285] System Configuration
[1286] This system is constructed mainly using the following hardware and software.
[1287] 1. User Device
[1288] A smartphone application with an input function that allows users to input product names and keywords. It is implemented on the Android or iOS platform.
[1289] Push notification functionality to receive notifications and confirm reservation requests, using Google Firebase Cloud Messaging (FCM) and Apple Push Notification Service (APNs).
[1290] Provides an interface to display reservation completion and redemption information.
[1291] 2. Server
[1292] Product information is stored in a database and a means of searching for product information is provided using generative AI. The generative AI model is a generative AI (e.g., GPT-4).
[1293] A function that works with push notification services to send notifications to users.
[1294] A function that automatically processes product reservations. Reservation information is managed using a web framework such as Django and a task scheduler such as Celery.
[1295] A function that sends information to the user's device to pick up the product at a physical store.
[1296] System Operation
[1297] 1. Register your interest in products
[1298] A user uses a smartphone app to input product names and keywords that they are interested in. The input information is sent to the server.
[1299] 2. Search for product information
[1300] The server stores the received product names and keywords in a database and periodically searches the web and social media using the generative AI model to collect information about product availability and sales start dates.
[1301] Example: Prompt sentence to generative AI model: "Please check the stock status of limited edition premium shoes and notify the user when they are in stock."
[1302] 3. Sending notifications
[1303] When related product information appears in the search results, the server sends a push notification to the user's device, including the reservation start date and time and a URL.
[1304] Example: Notification: "Pre-orders for limited edition premium shoes have begun. Please see the link below for details."
[1305] 4. Automated booking process
[1306] The user receives the notification and clicks a button to select a reservation request, which causes the terminal to send the reservation request to the server.
[1307] The server automatically processes the reservation using pre-stored user information (such as name and contact information).
[1308] 5. Reservation confirmation and collection
[1309] When the reservation is completed, the server sends a reservation completion notice to the user terminal.
[1310] The user can present this notification at the physical store and pick up the reserved item.
[1311] The above system configuration and operation allows users to efficiently reserve and purchase products they are interested in and reliably pick them up at a physical store.
[1312] The flow of the specific processing in the application example 1 will be described with reference to FIG.
[1313] Step 1:
[1314] Users enter product names and keywords of interest into a smartphone app. After input, the device sends this information to a server. By sending the entered product names and keywords to the server, the data necessary for subsequent processing is provided.
[1315] Step 2:
[1316] The server stores the received product names and keywords in a database. This input data is used as a prompt for a generative AI model (e.g., GPT-4) to collect the latest information related to the product from the web and social media. By storing the information in the database, the server periodically searches using these keywords to check the latest sales start information and inventory information.
[1317] Step 3:
[1318] The server uses a web scraping tool (e.g., BeautifulSoup) to extract relevant product information. It passes prompts to a generative AI model, which analyzes the search results and extracts product information (e.g., stock availability, release date, etc.). The extracted data is then stored back in the database.
[1319] Step 4:
[1320] The server sends a push notification to the user when product information is updated. It uses a push notification service (e.g., Google FCM or Apple APNs) to send the notification to the user's device. In this step, the server compares the information in the database and sends the notification only if the new notification conditions are met.
[1321] Step 5:
[1322] The user receives a push notification, clicks the link in the notification to check the details, and selects whether they wish to make a reservation. The device then sends the reservation request to the server. By specifically communicating the user's intention to the server, the automatic reservation process begins.
[1323] Step 6:
[1324] The server automatically processes reservations based on pre-stored user information (such as name and contact information). The server then enters the necessary information into a pre-set reservation form and confirms the product reservation. Because reservations are made automatically, it saves the user time and effort.
[1325] Step 7:
[1326] Once the reservation process is complete, the server sends the user a confirmation notification, which includes details on how to collect the reserved item and the physical store location, so the user knows exactly how to secure and collect the reserved item.
[1327] Step 8:
[1328] The user presents the notification to the physical store and collects the reserved product. The collection procedure at the physical store is carried out based on confirmation and verification by the store staff. Once collection is complete, the entire system process is completed.
[1329] 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.
[1330] The present invention is a system that recognizes a user's emotions and assists in purchasing event tickets based on those emotions. This system operates by combining a user terminal, a server, an emotion engine, and a generation AI. Specific embodiments are described below.
[1331] User event registration and emotion recognition
[1332] 1. User event registration
[1333] A user launches the application and enters the name of an event or keyword they are interested in, for example, "Rock Festival 2024."
[1334] The terminal transmits the input event name and keywords to the server.
[1335] 2. Emotional Recognition
[1336] The device is equipped with a camera and microphone, and the emotion engine analyzes the user's facial expressions and tone of voice.
[1337] The emotion engine analyzes the user's emotion data in real time to determine the user's emotional state for the events entered by the user.
[1338] Event information monitoring and notification
[1339] 1. Event information monitoring
[1340] The server stores the required event names and keywords in a database, and then uses generative AI to periodically collect relevant event information from web searches and social networking services (SNS).
[1341] 2. Sending notifications
[1342] When the collected event information is related to the start of ticket sales, the server sends a push notification to the device, and the emotion engine customizes the content of the notification based on the user's emotional state.
[1343] For example, if the user is excited, the notification will have emotional content such as "An event you can't miss! Check it out now."
[1344] Ticket purchase confirmation and automatic purchase
[1345] 1. User Verification
[1346] The user receives a notification, checks the details, and if they are interested in purchasing tickets, selects "I want to buy."
[1347] 2. Automatic ticket purchase
[1348] The device sends the user's purchase request to the server, which uses the stored user information (such as name and credit card information) to initiate the purchase process.
[1349] The server automatically accesses the ticket purchasing site, fills out the purchase form, and completes the process.
[1350] Ticket issuance and distribution
[1351] 1. Ticket issuance
[1352] Once the purchase is complete, the server generates an electronic version of the ticket, which is restricted from resale.
[1353] 2. Ticket Offer
[1354] The server sends the generated electronic ticket to the terminal, which stores the received ticket in the user's account and displays it as needed.
[1355] Specific examples
[1356] 1. User registration and emotion recognition flow
[1357] A user is interested in "Rock Festival 2024" and enters the event name "Rock Festival 2024" into the application.
[1358] The terminal sends the entered information to the server, which stores the event name in a database.
[1359] The emotion engine analyzes the user's facial expressions and tone of voice using the device's built-in camera and microphone to determine the user's emotional state.
[1360] 2. Customizing notifications
[1361] The server uses generative AI to periodically search the web and social media for information on "Rock Festival 2024 ticket sales."
[1362] When a sale is detected, the server sends a notification to the terminal.
[1363] If the emotion engine detects that the user is excited, the notification will be customized to say, "An event you absolutely cannot miss! Check it out now."
[1364] This allows users to receive event notifications at the right time and in the right way based on their emotions, allowing them to secure tickets when they are most interested in them. It also prevents ticket resale issues, improving the ticket purchasing experience.
[1365] The processing flow will be explained below.
[1366] Step 1:
[1367] A user launches the application and enters the name of an event or keyword they are interested in, for example, "Rock Festival 2024."
[1368] Step 2:
[1369] The device sends the input event name and keywords to the server. The transmitted data includes the event name "Rock Festival 2024."
[1370] Step 3:
[1371] The server stores the received event names and keywords in a database, then uses generative AI to schedule collection of related event information from the web and social media.
[1372] Step 4:
[1373] The device uses a camera and microphone to collect the user's facial expressions and tone of voice, and the emotion engine analyzes this data in real time to determine the user's emotional state.
[1374] Step 5:
[1375] The server uses generative AI to periodically search for relevant information, such as "Rock Festival 2024 ticket sales," and collects any new information it finds.
[1376] Step 6:
[1377] The server sends push notifications to the device based on the collected information. The content of the notification is customized according to the user's emotional state. For example, if the user is excited, the notification might say, "This is an event you definitely can't miss! Check it out now."
[1378] Step 7:
[1379] The user receives a push notification, checks the details of the event, and clicks the button to select "I want to buy."
[1380] Step 8:
[1381] The terminal transmits the user's purchase request to the server. The transmitted data includes "Event name: Rock Festival 2024" and "Purchase request: Yes."
[1382] Step 9:
[1383] When the server receives the purchase request, it uses the pre-stored user information (name, credit card information, etc.) to access the specified ticket purchase site. For example, it accesses "https: / / example.com / ticket-purchase."
[1384] Step 10:
[1385] The server automatically fills in the necessary information on the purchase site's form, including the user's name, credit card number, and expiration date.
[1386] Step 11:
[1387] After the form is filled out, the server executes the purchase process. If the purchase is successful, the server receives a "ticket purchase successful" message.
[1388] Step 12:
[1389] Once the purchase is complete, the server generates the ticket in electronic format, with a no-resale restriction attached to the electronic ticket.
[1390] Step 13:
[1391] The server sends the generated electronic ticket to the terminal. The sent data includes "Electronic ticket ID: 987654321" and "Not for resale."
[1392] Step 14:
[1393] The device stores the received e-ticket in the user's account and provides the functionality to display it as needed. The user can check the ticket within the application.
[1394] Through these steps, users can obtain event tickets in a more personalized way using emotion recognition, and the problem of ticket resale can be prevented.
[1395] Example 2
[1396] 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 robot 414 will be referred to as a "terminal."
[1397] Conventional ticket purchasing systems provide uniform notifications without considering the user's emotional state, making it impossible to effectively provide information at a time when users are interested. Furthermore, the manual ticket purchasing process required an inconvenient purchasing experience. Furthermore, fraudulent transactions due to ticket resale after purchase were a problem.
[1398] 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.
[1399] In this invention, the server includes means for inputting an event name or keyword of interest, means for searching for event information based on the input event name or keyword, means for sending a notification when tickets for the event included in the searched event information go on sale, means for confirming the purchase intention of the user who received the notification, means for automatically purchasing the ticket after confirming the purchase intention, means for attaching a no-resale restriction to the purchased ticket and providing it in an electronic format, means for recognizing the user's emotion, and means for customizing the content of the notification based on the recognized emotion. This allows for notifications to be sent with optimal timing and content according to the user's emotional state, enabling easy and automatic ticket purchases and preventing resale issues.
[1400] "Event names and keywords of interest" are the names of events and related words that interest users and are the subject of searches and notifications.
[1401] "Event Information" refers to data and news related to a specific event collected from websites and social networking services.
[1402] The "means for sending a notification when ticket sales begin" is a mechanism for sending a push notification to the user's device when ticket sales for an event begin.
[1403] "Means for confirming purchase intent" refers to the interface or process by which a user confirms their intention to purchase a ticket.
[1404] The "means for automatically purchasing tickets" is a system in which, after the user's purchase request has been confirmed, the server automatically carries out the ticket purchase procedure based on the user information stored on the server.
[1405] "Means of providing tickets in electronic format with restrictions preventing resale" refers to a system in which purchased tickets are provided to users in electronic format with restrictions attached to prevent resale.
[1406] "Means for recognizing emotions" refers to technologies or systems that analyze a user's facial expressions and tone of voice to determine their emotional state at that time.
[1407] "Means for customizing notification content based on emotions" refers to a mechanism that adjusts the wording and content of notifications sent according to the user's recognized emotional state.
[1408] This invention is a system that recognizes a user's emotions and supports the purchase of event tickets based on those emotions. This system operates by combining a user terminal, a server, an emotion engine, and a generation AI.
[1409] User event registration and emotion recognition
[1410] 1. The user launches the application and enters the name of an event or keyword they are interested in. For example, they might enter "Rock Festival 2024."
[1411] 2. The device sends the entered event name and keywords to the server.
[1412] 3. The device is equipped with a camera and microphone, and the emotion engine analyzes the user's facial expressions and tone of voice.
[1413] 4. The emotion engine analyzes the user's emotion data in real time and determines the user's emotional state for the events entered by the user.
[1414] Event information monitoring and notification
[1415] 1. The server stores the required event names and keywords in a database.
[1416] 2. The server periodically collects relevant event information from web searches and social networking services (SNS) using generative AI.
[1417] 3. If the collected event information is related to the start of ticket sales, the server sends a push notification to the device. At this time, the emotion engine customizes the content of the notification based on the user's emotional state. For example, if the user is excited, the server sends a notification with the content "This is an event you cannot miss! Check it out now!"
[1418] Ticket purchase confirmation and automatic purchase
[1419] 1. The user receives a notification, checks the details, and if they are interested in purchasing a ticket, selects "I want to buy."
[1420] 2. The terminal sends the user's purchase request to the server.
[1421] 3. The server initiates the purchase process using the stored user information (name, credit card information, etc.).
[1422] 4. The server automatically accesses the ticket purchasing site, fills in the purchase form, and completes the process.
[1423] Ticket issuance and distribution
[1424] 1. Once the purchase is complete, the server generates an electronic ticket, which is restricted from resale.
[1425] 2. The server sends the generated electronic ticket to the terminal, which stores it in the user's account and displays it as needed.
[1426] Specific examples
[1427] User registration and emotion recognition flow
[1428] A user is interested in "Rock Festival 2024" and enters the event name "Rock Festival 2024" into the application.
[1429] The terminal sends the entered information to the server, which stores the event name in a database.
[1430] Using the device's built-in camera and microphone, the emotion engine analyzes the user's facial expressions and tone of voice to determine their emotional state.
[1431] Customizing notifications
[1432] The server uses generative AI to periodically search the web and social media for information on "Rock Festival 2024 ticket sales."
[1433] When a sale is detected, the server sends a notification to the terminal.
[1434] If the emotion engine detects that the user is excited, the notification will be customized to say, "An event you absolutely cannot miss! Check it out now."
[1435] An example prompt is, "Get real-time ticket sales information for Rock Festival 2024 and optimize the notification content based on user sentiment."
[1436] This allows users to receive event notifications at the right time and in the right way based on their emotions, allowing them to secure tickets when they are most interested in them. It also prevents ticket resale issues, improving the ticket purchasing experience.
[1437] The flow of the identification process in the second embodiment will be described with reference to FIG.
[1438] Step 1:
[1439] User event registration
[1440] The user launches the application and enters the name of an event or keywords of interest. An example input is "Rock Festival 2024." The device sends this information to the server. The input here is the event name or keywords, and the first output is the user's search intent, which is sent to the server.
[1441] Step 2:
[1442] emotion recognition
[1443] The device is equipped with a camera and microphone, which capture the user's facial expressions and tone of voice. The emotion engine analyzes this captured data in real time to determine the user's emotional state. For example, if the user is smiling, it is determined to be "excited." The input is the captured facial and voice data, and the output is the analyzed user's emotional state. The device sends this information to a server.
[1444] Step 3:
[1445] Monitoring event information
[1446] The server stores the received event names and keywords in a database. Using generative AI, the server periodically collects related event information from web searches and social networking services (SNS). Specifically, it inputs a search query as a prompt and uses the generative AI model to output newly discovered event information. This output is stored in the database and updated as necessary.
[1447] Step 4:
[1448] Sending notifications
[1449] The server pushes the collected event information to the user's device. At this time, the emotion engine customizes the notification content. For example, if the analysis finds that the user is excited, a notification such as "This is an event you absolutely cannot miss! Check it out now" is sent. The input is the collected event information and the analyzed emotional state, and the output is the customized notification content.
[1450] Step 5:
[1451] Ticket purchase confirmation
[1452] The user receives a push notification. If the user sees the notification and is interested in purchasing a ticket, they select "purchase" within the application. The input is the user's selection information, and the output is the purchase request information sent to the server.
[1453] Step 6:
[1454] Automatic ticket purchase
[1455] The terminal sends the user's purchase request to the server. The server uses the saved user information (e.g., name, credit card information) to access the ticket purchasing site and automatically enter the required information. The input is the user's purchase request and saved personal information, and the output is confirmation of the completed ticket purchase.
[1456] Step 7:
[1457] Ticketing and distribution
[1458] Once the ticket purchase is complete, the server generates an electronic ticket and adds a non-resale restriction. The generated electronic ticket is sent to the terminal, which then stores the received ticket in the user's account. The input is the purchase completion information, and the output is the electronic ticket.
[1459] These steps allow users to receive event notifications at the most convenient time and in the most convenient way, purchase tickets conveniently and efficiently, and prevent ticket resale issues.
[1460] (Application example 2)
[1461] 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 robot 414 will be referred to as a "terminal."
[1462] Conventional event ticket purchasing systems simply notify users of event information and are unable to consider the user's emotional state or interests, making it difficult to maximize the user's purchasing motivation. Furthermore, in brick-and-mortar stores, product recommendations are not based on the user's emotions, making it difficult to effectively promote products at the right time. This leaves the improvement of user satisfaction and purchasing experience as a challenge.
[1463] The identification process by the identification processing unit 290 of the data processing device 12 in Application Example 2 is realized by the following means. In this invention, the server includes means for recognizing emotions, means for inputting an event name or keyword of interest, means for searching for event information based on the input event name or keyword, means for sending a notification when ticket sales for an event included in the searched event information begin, means for customizing the content of the notification according to the user's emotional state, means for confirming the purchase intention of the user who received the notification, means for automatically purchasing tickets after confirming the purchase intention, and means for attaching a non-resale restriction to purchased tickets and providing them in an electronic format. This enables notifications and promotions to be provided at the appropriate time based on the user's emotions, maximizing the user's interest.
[1464] - "Means for recognizing emotions" refers to a function that analyzes the user's facial expressions and tone of voice to determine their emotional state in real time.
[1465] The "means for inputting the event name or keyword of interest" is an interface through which the user inputs the event name or keyword on the application and transmits the data to the server.
[1466] The "means for searching for event information" is a function that allows the server to collect related event information from the web or social networking services based on the input event name or keywords.
[1467] The "means for sending a notification" is a function for sending a push notification to a user terminal based on the event information collected by the server.
[1468] The "means for customizing notification content according to emotional state" is a function in which the emotion engine analyzes the user's emotional state and changes the notification content based on the results.
[1469] The "means for confirming purchase intent" is a function that allows the user to confirm their willingness to purchase tickets through the application after receiving the notification.
[1470] The "means for automatically purchasing tickets" is a function in which the server automatically purchases tickets using the stored user information after the user's purchase request has been confirmed.
[1471] "Means for adding restrictions preventing resale and providing them in electronic format" is a function that adds restrictions to purchased tickets on the system to prevent resale and provides them to users in electronic format.
[1472] This invention is a system that recognizes a user's emotions and supports the purchase of event tickets based on those emotions. This system operates by combining a user terminal, a server, an emotion engine, and a generation AI. Specific embodiments are described below.
[1473] Hardware Configuration
[1474] User terminal
[1475] The user device consists of a device equipped with a camera and microphone, such as smart glasses, a smartphone, or a head-mounted display, which collects the user's facial expressions and tone of voice in real time.
[1476] server
[1477] The server has high-performance computing resources to run the emotion engine and generative AI model.
[1478] Specific software used includes Microsoft Azure Emotion API for the emotion engine and OpenAI's GPT-3 for the generative AI model.
[1479] Software Configuration
[1480] Emotion Recognition Module
[1481] The emotion recognition module collects the user's facial expressions and tone of voice through the camera and microphone installed on the user's device, and analyzes the data using the Microsoft Azure Emotion API, thereby recognizing the user's emotional state in real time.
[1482] Event information collection module
[1483] The event information collection module is implemented on the server and automatically collects event information of interest from the web and social networking services. This module periodically monitors the Internet to obtain new event information.
[1484] Notification Customization Module
[1485] The notification customization module analyzes the user's emotional state based on data from the emotion recognition module. Using a generative AI model, it customizes the notification content based on the user's emotions. For example, if the user is excited, it generates a strong message saying, "This is an event you can't miss! Check it out now!"
[1486] Automatic ticket purchasing module
[1487] The automatic ticket purchasing module automatically purchases tickets using the saved user information after confirming the user's purchase request. During this process, the server automatically fills in the purchase form and provides the necessary information.
[1488] Electronic ticket provision module
[1489] The electronic ticket providing module assigns a non-resale restriction to the purchased ticket and sends it to the user's terminal in electronic format. This ticket is stored in the user's account and displayed as needed.
[1490] Specific examples
[1491] A user puts on smart glasses and expresses interest in a particular event.
[1492] 1. The camera and microphone on the user's device collect the user's facial expressions and tone of voice, recognizing emotions in real time.
[1493] 2. The server monitors web and social networking services to collect certain event information.
[1494] 3. Based on the user's emotional state, the generative AI model will customize and send a notification saying, "This event is a must-see!"
[1495] 4. After the user receives the notification and confirms their purchase, the server automatically purchases the tickets and provides them in electronic format.
[1496] Examples of prompt statements
[1497] Emotion Recognition Data Analysis Prompt: "Analyze the user's facial expression and tone of voice and output their current emotional state."
[1498] Product suggestion generation prompt: "Generate product suggestions when the user is excited. For example, limited edition items."
[1499] This system enables notifications and promotions to be delivered at the right time based on the user's emotions, maximizing the user's interest and improving user satisfaction.
[1500] The flow of the specific processing in the application example 2 will be described with reference to FIG.
[1501] Step 1:
[1502] The user puts on the smart glasses and launches the application. The user inputs the name of an event or keyword of interest (e.g., "Rock Festival 2024") by voice or text. The input data is then sent from the user's device to the server.
[1503] Step 2:
[1504] The server passes the received event name and keywords to an event information collection module, which searches for related event information from the web and social networking services based on the input event name and keywords and stores it in a database.
[1505] Step 3:
[1506] The camera and microphone on the user's device continuously capture the user's facial expressions and tone of voice, and send the data to the server in real time. The emotion recognition module analyzes the collected data using the Microsoft Azure Emotion API to recognize the user's emotional state. The input is the user's facial and voice data, and the output is their emotional state (e.g., "excited").
[1507] Step 4:
[1508] The server determines the notification content based on the event information and the user's emotional state. The notification customization module uses a generative AI model (e.g., OpenAI's GPT-3) to generate notification content based on the prompt. The input is the event information and the user's emotional state, and the output is a customized notification. It generates a strong message such as "This event is a must-see!"
[1509] Step 5:
[1510] The server pushes the customized notification to the user's device and waits until the user confirms the notification and responds. For example, the user selects "purchase request" and sends the response from the device to the server.
[1511] Step 6:
[1512] The server receives the user's purchase request, and the automatic ticket purchasing module starts the purchase process. Using saved user information (name, credit card information, etc.), the module automatically accesses the ticket purchasing site, fills in a form, and makes the purchase. The input is the user's purchase request and saved user information, and the output is a notification of purchase completion.
[1513] Step 7:
[1514] After the purchase is complete, the server assigns a no-resale restriction to the purchased ticket and provides it in electronic format. The electronic ticket provision module generates an electronic ticket and sends it to the user's terminal. The user terminal stores the received electronic ticket in the user's account and can display it as needed. The input is purchase completion information, and the output is the electronic ticket.
[1515] The specific processing unit 290 transmits the result of the specific processing to the robot 414. In the robot 414, the control unit 46A causes the speaker 240 and the control target 443 to output the result of the specific processing. The microphone 238 acquires voice indicating a user input regarding the result of the specific processing. The control unit 46A transmits voice 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 voice data.
[1516] 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.
[1517] 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 robot 414.
[1518] The emotion identification model 59 as an emotion engine may determine the user's emotion according to a specific mapping. Specifically, the emotion identification model 59 may determine the user's emotion according to an emotion map (see FIG. 9), which is a specific mapping. Similarly, the emotion identification model 59 may determine the robot's emotion, and the identification processing unit 290 may perform identification processing using the robot's emotion.
[1519] FIG. 9 is a diagram illustrating an emotion map 400 on which multiple emotions are mapped. In the emotion map 400, emotions are arranged in concentric circles radiating from the center. Emotions closer to the center of the concentric circles are more primitive. Emotions representing states and actions arising from a state of mind are arranged on the outer edges of the concentric circles. The concept of emotion includes both affect and mental states. Emotions generally generated from reactions occurring in the brain are arranged on the left side of the concentric circles. Emotions generally induced by situational judgment are arranged on the right side of the concentric circles. Emotions generally generated from reactions occurring in the brain and induced by situational judgment are arranged on the upper and lower sides of the concentric circles. Furthermore, the emotion of "pleasure" is arranged on the upper side of the concentric circles, and the emotion of "discomfort" is arranged on the lower side. In this way, in the emotion map 400, multiple emotions are mapped based on the structure by which emotions are generated, and emotions that tend to occur simultaneously are mapped close to each other.
[1520] These emotions are distributed in the 3 o'clock direction on emotion map 400, and typically fluctuate between relief and anxiety. In the right half of emotion map 400, situational awareness dominates over internal sensations, resulting in a sense of calm.
[1521] The inside of emotion map 400 represents what is going on in the mind, and the outside of emotion map 400 represents behavior, so the further you go outside emotion map 400, the more visible the emotions become (the more they are expressed in behavior).
[1522] Human emotions are based on various balances, such as posture and blood sugar levels. When these balances deviate from the ideal, a state of discomfort is indicated, and when they approach the ideal, a state of pleasure is indicated. Emotions can also be created for robots, automobiles, and motorcycles, based on various balances, such as posture and remaining battery life. When these balances deviate from the ideal, a state of discomfort is indicated, and when they approach the ideal, a state of pleasure is indicated. An emotion map can be generated, for example, based on Dr. Mitsuyoshi's emotion map (Research on Voice Emotion Recognition and Emotional Brain Physiological Signal Analysis Systems, Tokushima University, Doctoral Dissertation: https: / / ci.nii.ac.jp / naid / 500000375379). The left half of the emotion map lists emotions belonging to the "reaction" domain, where sensation is dominant. The right half of the emotion map lists emotions belonging to the "situation" domain, where situational awareness is dominant.
[1523] The emotion map defines two emotions that promote learning. One is a negative emotion on the situation side, around the middle of "repentance" or "reflection." In other words, this occurs when the robot experiences negative emotions such as "I never want to feel this way again" or "I don't want to be scolded again." The other is a positive emotion on the response side, around "desire." In other words, this occurs when the robot experiences positive feelings such as "I want more" or "I want to know more."
[1524] The emotion identification model 59 inputs user input into a pre-trained neural network, obtains emotion values indicating each emotion shown in the emotion map 400, and determines the user's emotion. This neural network is pre-trained based on multiple pieces of training data that are combinations of user input and emotion values indicating each emotion shown in the emotion map 400. Furthermore, this neural network is trained so that emotions that are located close to each other have similar values, as in the emotion map 900 shown in FIG. 10. FIG. 10 shows an example in which multiple emotions, "relieved," "calm," and "reassuring," have similar emotion values.
[1525] The system according to the present disclosure has been described above mainly with respect to the functions of the data processing device 12, but the system according to the present disclosure is not necessarily implemented on a server. The system according to the present disclosure may be implemented as a general information processing system. The present disclosure may be implemented, for example, as a software program running on a personal computer or an application running on a smartphone, etc. The method according to the present disclosure may be provided to users in the form of SaaS (Software as a Service).
[1526] In the above embodiment, an example was given in which the specific processing is performed by one computer 22, but the technology of the present disclosure is not limited to this, and the specific processing may be distributed and performed by a plurality of computers including the computer 22. For example, the data generation model 58 may be provided in an external device of the data processing device 12, and data may be generated in the external device in accordance with input data.
[1527] In the above embodiment, an example in which the specific processing program 56 is stored in the storage 32 has been described, but the technology of the present disclosure is not limited to this. For example, the specific processing program 56 may be stored in a portable, computer-readable, non-transitory storage medium such as a USB (Universal Serial Bus) memory. The specific processing program 56 stored in the non-transitory storage medium is installed in the computer 22 of the data processing device 12. The processor 28 executes the specific processing in accordance with the specific processing program 56.
[1528] Alternatively, the specific processing program 56 may be stored in a storage device such as a server connected to the data processing device 12 via the network 54, and the specific processing program 56 may be downloaded and installed on the computer 22 in response to a request from the data processing device 12.
[1529] It is not necessary to store all of the specific processing program 56 in a storage device such as a server connected to the data processing device 12 via the network 54, or to store all of the specific processing program 56 in the storage 32; only a portion of the specific processing program 56 may be stored.
[1530] The hardware resource for executing a specific process can be any of the following processors: An example of a processor is a CPU, which is a general-purpose processor that functions as a hardware resource for executing a specific process by executing software, i.e., a program. Another example of a processor is a dedicated electrical circuit, such as an FPGA (Field-Programmable Gate Array), a PLD (Programmable Logic Device), or an ASIC (Application Specific Integrated Circuit), which is a processor with a circuit configuration designed specifically for executing a specific process. Each processor has built-in or connected memory, and each processor uses the memory to execute the specific process.
[1531] The hardware resource that executes the specific processing may be configured with one of these various processors, or may be configured with a combination of two or more processors of the same or different types (for example, a combination of multiple FPGAs, or a combination of a CPU and an FPGA). Also, the hardware resource that executes the specific processing may be a single processor.
[1532] As an example of a system configured with a single processor, first, one processor is configured by combining one or more CPUs and software, and this processor functions as a hardware resource that executes a specific process. Second, there is a system that uses a processor that realizes the functions of an entire system including multiple hardware resources that execute a specific process on a single IC chip, as typified by SoC (System-on-a-chip). In this way, a specific process is realized using one or more of the above-mentioned various processors as hardware resources.
[1533] Furthermore, the hardware structure of these various processors can be, more specifically, an electric circuit that combines circuit elements such as semiconductor devices. The specific processing described above is merely an example. Therefore, it goes without saying that unnecessary steps may be deleted, new steps may be added, or the processing order may be rearranged, without departing from the spirit of the invention.
[1534] The above-described description and illustrations are a detailed explanation of the parts related to the technology of the present disclosure and are merely an example of the technology of the present disclosure. For example, the above description of the configuration, functions, actions, and effects is an explanation of an example of the configuration, functions, actions, and effects of the parts related to the technology of the present disclosure. Therefore, it goes without saying that unnecessary parts may be deleted, new elements may be added, or replacements may be made to the above-described description and illustrations within the scope of the gist of the technology of the present disclosure. Furthermore, to avoid confusion and facilitate understanding of the parts related to the technology of the present disclosure, the above-described description and illustrations omit explanations of common technical knowledge that do not require particular explanation to enable the implementation of the technology of the present disclosure.
[1535] All publications, patent applications, and technical standards mentioned in this specification are herein incorporated by reference to the same extent as if each individual publication, patent application, or technical standard was specifically and individually indicated to be incorporated by reference.
[1536] The following is further disclosed regarding the above embodiment.
[1537] (Claim 1)
[1538] A way to enter event names or keywords of interest;
[1539] A means for searching for event information based on the input event name or keyword;
[1540] means for sending a notification when tickets for the event included in the searched event information go on sale;
[1541] A means for confirming the purchase intention of the user who received the notification;
[1542] means for automatically purchasing tickets after confirming said purchase request;
[1543] means for providing said purchased tickets in an electronic format with a no-resale restriction;
[1544] A system including:
[1545] (Claim 2)
[1546] The system of claim 1 , wherein the event information is collected from the web and social networking services.
[1547] (Claim 3)
[1548] 2. The system according to claim 1, wherein the ticket purchasing procedure is carried out automatically using pre-stored user information.
[1549] "Example 1"
[1550] (Claim 1)
[1551] A way to enter event names or keywords of interest;
[1552] A means for searching for event information based on the input event name or keyword;
[1553] means for sending a notification when tickets for the event included in the searched event information go on sale;
[1554] A means for confirming the purchase intention of the user who received the notification;
[1555] means for automatically purchasing tickets after confirming said purchase request;
[1556] means for providing said purchased tickets in an electronic format with a no-resale restriction;
[1557] means for periodically searching the web and social networking services using the generative language model;
[1558] A system including:
[1559] (Claim 2)
[1560] The system of claim 1 , wherein the event information is collected from the web and social networking services.
[1561] (Claim 3)
[1562] 2. The system according to claim 1, wherein the ticket purchasing procedure is carried out automatically using pre-stored user information.
[1563] "Application Example 1"
[1564] (Claim 1)
[1565] A way to enter product names or keywords of interest,
[1566] A means for searching for product information based on the input product name and keywords;
[1567] means for transmitting a notification when the product included in the searched product information is released for sale;
[1568] A means for confirming the reservation request of the user who received the notification;
[1569] means for automatically reserving the product after confirming said reservation request;
[1570] A means for allowing the reserved product to be picked up at a physical store;
[1571] A system including:
[1572] (Claim 2)
[1573] The system of claim 1, wherein the product information is collected from the web and social networking services.
[1574] (Claim 3)
[1575] 2. The system according to claim 1, wherein the product reservation procedure is automatically performed using pre-stored user information.
[1576] "Example 2: Combining Emotion Engines"
[1577] (Claim 1)
[1578] A way to enter event names or keywords of interest;
[1579] A means for searching for event information based on the input event name or keyword;
[1580] means for sending a notification when tickets for the event included in the searched event information go on sale;
[1581] A means for confirming the purchase intention of the user who received the notification;
[1582] means for automatically purchasing tickets after confirming said purchase request;
[1583] means for providing said purchased tickets in an electronic format with a no-resale restriction;
[1584] a means for recognizing a user's emotion;
[1585] means for customizing notification content based on the recognized emotion;
[1586] A system including:
[1587] (Claim 2)
[1588] The system of claim 1 , wherein the event information is collected from the web and social networking services.
[1589] (Claim 3)
[1590] 2. The system according to claim 1, wherein the ticket purchasing procedure is carried out automatically using pre-stored user information.
[1591] "Application example 2 when combining emotion engines"
[1592] Rewriting of claims
[1593] (Claim 1)
[1594] A means of recognizing emotions;
[1595] A way to enter event names or keywords of interest;
[1596] A means for searching for event information based on the input event name or keyword;
[1597] means for sending a notification when tickets for the event included in the searched event information go on sale;
[1598] means for customizing the notification content according to an emotional state;
[1599] A means for confirming the purchase intention of the user who received the notification;
[1600] means for automatically purchasing tickets after confirming said purchase request;
[1601] means for providing said purchased tickets in an electronic format with a no-resale restriction;
[1602] A system including:
[1603] (Claim 2)
[1604] The system of claim 1 , wherein the event information is collected from the web and social networking services.
[1605] (Claim 3)
[1606] 2. The system according to claim 1, wherein the ticket purchasing procedure is carried out automatically using pre-stored user information. [Explanation of symbols]
[1607] 10, 210, 310, 410 Data Processing Systems 12 Data Processing Device 14 Smart Devices 214 Smart Glasses 314 Headset-type terminal 414 Robot< / url:> < / url:> < / url:> < / url:>
Claims
1. A way to enter event names or keywords of interest; A means for searching for event information based on the input event name or keyword; means for sending a notification when tickets for the event included in the searched event information go on sale; A means for confirming the purchase intention of the user who received the notification; means for automatically purchasing tickets after confirming said purchase request; means for providing said purchased tickets in an electronic format with a no-resale restriction; A system including:
2. The system of claim 1 , wherein the event information is collected from the web and social networking services.
3. 2. The system according to claim 1, wherein the ticket purchasing procedure is automatically performed using pre-stored user information.
Citation Information
Patent Citations
Persona chatbot control method and system
JP2022180282A