Information processing system, control method therefor, and program

Abstract

This information processing system for creating an event page to be published online comprises: an acquisition unit for acquiring character string information that is input via a social networking service (SNS) and that pertains to an event; an extraction unit for using a large language model to extract event information for creating an event page for the event from the character string information; and a creation unit for using the event information to create the event page for the event.

Description

Information processing system, control method therefor, and program

[0001] The present invention relates to an information processing system, a control method therefor, and a program.

[0002] Conventionally, various events such as music and sports have been held, and reference to information related to such events, ticket sales and purchases, and the like are performed via websites. Portal sites that allow reference to information on various events organized by different organizers are also widespread. In such portal sites, pages are generated and published for each individual event.

[0003] On the other hand, with the spread of generative artificial intelligence (Generative AI), including large language models (LLM: Large Language Model) in recent years, the convenience of services related to natural language processing has improved. For example, Patent Document 1 discloses a configuration that utilizes a large language model to generate websites.

[0004] Japanese Patent No. 7621025

[0005] In the work of creating a site for each event as described above, the event organizer needs to individually exchange information related to the event with the administrator of the portal site, or individually input information into a predetermined input form. For this reason, labor and time for creating the page have been required. Accordingly, there is a need to reduce the time and effort required for a user to input event information when creating, registering, editing, or the like an event page. Citation Document 1 does not sufficiently consider the convenience of inputting each item related to event information.

[0006] In view of the above problems, an object of the present invention is to reduce the time and effort required for data input related to sites for various events, and to improve the convenience of work related to the sites.

[0007] To solve the above problems, one embodiment of the present invention has the following configuration. That is, an information processing system for creating an event page to be published online, comprising: an acquisition unit that acquires string information relating to an event input via SNS (Social Networking Service); an extraction unit that uses a large-scale language model to extract event information for creating an event page for the event from the string information; and a creation unit that uses the event information to create an event page for the event.

[0008] Another embodiment of the present invention has the following configuration: a control method for an information processing system that creates an event page to be published online, comprising: an acquisition step of acquiring string information relating to an event input via SNS (Social Networking Service); an extraction step of extracting event information for creating an event page for the event from the string information using a large-scale language model; and a creation step of creating an event page for the event using the event information.

[0009] Another embodiment of the present invention has the following configuration: a program that causes a computer to function as: an acquisition unit that acquires string information relating to an event entered via SNS (Social Networking Service); an extraction unit that extracts event information from the string information using a large-scale language model for creating an event page for the event; and a creation unit that creates an event page for the event using the event information.

[0010] Another embodiment of the present invention has the following configuration: an information processing system for managing event pages published online, comprising: an acquisition unit that acquires information about events entered via a communication tool; an extraction unit that extracts event information relating to the events from the information using a generation AI; and an execution unit that performs processing on the event page of the events based on the event information.

[0011] Another embodiment of the present invention has the following configuration: a control method for an information processing system that manages event pages published online, comprising: an acquisition step of acquiring information about an event entered via a communication tool; an extraction step of extracting event information relating to the event from the information using a generating AI; and an execution step of performing processing on the event page of the event based on the event information.

[0012] Another embodiment of the present invention has the following configuration: a program that causes a computer to function as: an acquisition unit that acquires information about an event input via a communication tool; an extraction unit that extracts event information related to the event from the information using a generation AI; and an execution unit that performs processing on the event page of the event based on the event information.

[0013] According to the present invention, it is possible to reduce the effort required for data entry related to various event websites and improve the convenience of website-related work.

[0014] Block diagram showing an example configuration of an event management system according to the first embodiment of the present invention. Functional block diagram showing an event management server according to the first embodiment of the present invention. Functional block diagram showing a user terminal according to the first embodiment of the present invention. Example diagram showing an example configuration of a UI screen Processing sequence of each device according to the first embodiment of the present invention. Flowchart showing the event page creation process according to the first embodiment of the present invention.

[0015] Hereinafter, embodiments for carrying out the present invention will be described with reference to the drawings and other documents. The embodiments described below are merely examples for illustrating the present invention and are not intended to be interpreted as limiting the invention. Furthermore, not all configurations described in each embodiment are necessarily essential for solving the problems of the present invention. In each drawing, the same components are given the same reference numeral to indicate their correspondence. To avoid unnecessary redundancy and to facilitate understanding by those skilled in the art, some parts of the description may be omitted or simplified. For example, detailed explanations of already well-known matters or redundant explanations of substantially identical configurations may be omitted.

[0016] <First Embodiment> [System Configuration] Figure 1 is a schematic diagram showing an example configuration of an event management system (information processing system) according to the first embodiment of the present invention. The event management system 1 is a system for collecting and managing information related to an event (hereinafter also referred to as "event information") and publishing a site related to the event. The event management system 1 may also manage the buying and selling of event tickets and information of purchasers. In this embodiment, "event" may include various events such as concerts, sports, plays, movies, and exhibitions, and is not particularly limited in content.

[0017] The event management system 1 consists of an event management server 100, a user terminal 200, an SNS server 300, and a generation AI server 350. Each device constituting the event management system 1 is configured to communicate via a network NW.

[0018] The event management server 100 collects event information and creates event pages based on that information. The event management server 100 also publishes the created event pages online, such as on the internet, and configures them to be viewable using a web browser (not shown). Furthermore, the event management server 100 is configured to utilize various functions provided by the SNS server 300 and the generation AI server 350, which will be described later.

[0019] The event management server 100 may be configured on-premises using a general-purpose computer such as a workstation or personal computer, or it may be logically implemented through cloud computing. In this embodiment, for the sake of explanation, one event management server 100 is given as an example, but it is not limited to this, and there may be multiple servers, or there may be servers with different roles, such as an authentication server and a database server.

[0020] The user terminal 200 is an operating terminal used by event organizers and related parties. The user terminal 200 may be composed of information processing devices such as a personal computer, tablet terminal, smartphone, or POS terminal. The user terminal 200 is configured to be able to use the SNS described later and a browser (not shown) for viewing the event page. The type of SNS is not particularly limited. In this embodiment, it is assumed that accounts for services provided by the event management server 100 and accounts used by event organizers are registered as accounts for using the SNS. It is sufficient that users can send messages to the event management server 100 via the SNS, and the account configuration is not particularly limited. In the example in Figure 1, one user terminal 200 is shown, but many user terminals 200 used by each event organizer may be used. The configurations of the multiple user terminals 200 may be different or the same.

[0021] The SNS server 300 is a server that provides an SNS for communication between multiple users. An SNS, which is a communication tool, is configured such that, for example, multiple users belonging to a room can view a message by posting string information as a message in a room for communication. The configuration of a room and the way messages are displayed in an SNS are not particularly limited, but an example will be described later. Examples of message-posting type SNSs include LINE®, WhatsApp®, and Skype®.

[0022] The Generative AI Server 350 is a server that provides services using Generative AI in response to requests from external sources. The Generative AI takes data in a predetermined format (text, images, audio, etc.) and prompts that define instructions for the data as input, and provides output corresponding to the prompts. The Generative AI is configured, for example, as a Large Language Model (LLM) trained using deep learning technology. The type of Generative AI and the training method are not particularly limited, and it is sufficient if it can provide the functions described later.

[0023] A network (NW) consists of the Internet, intranet, wireless LAN (Local Area Network), WAN (Wide Area Network), etc. The communication standards and wired / wireless connections used in the network (NW) are not particularly limited, and a network (NW) may be composed of a combination of multiple communication standards.

[0024] Figure 2 is a block diagram showing an example of the functional configuration of the event management server 100 according to this embodiment. The event management server 100 is composed of a control unit 110, a communication unit 120, and a storage unit 130. Each part is configured to communicate with each other via an internal bus or the like.

[0025] The control unit 110 is responsible for controlling the operation of the event management server 100. The control unit 110 is composed of, for example, a CPU (Central Processing Unit) and a GPU (Graphics Processing Unit), and provides various functions by reading and executing various programs and data stored in the storage unit 130. The control unit 110 functions as a data management unit 111, an instruction reception unit 112, an SNS linkage unit 113, a generation AI linkage unit 114, a site management unit 115, an event page creation unit 116, a display control unit 117, and a communication control unit 118.

[0026] The data management unit 111 works in conjunction with the storage unit 130 to manage various types of data and provides, registers, updates, etc., data in response to requests from external devices. The instruction receiving unit 112 receives various instructions entered via SNS. An example of an instruction in this embodiment is an instruction related to the creation of an event website. Specific examples of instructions will be described later.

[0027] The SNS integration unit 113 performs coordination with the SNS server 300 regarding the sending and receiving of data. The generation AI integration unit 114 performs coordination with the generation AI server 350 regarding the sending and receiving of data.

[0028] The site management unit 115 manages a portal site that allows users to view and search multiple event pages corresponding to various events. The site management unit 115 may also perform authentication processing for users who create or register event pages. The event page creation unit 116 creates event pages corresponding to events. The creation process and specific examples of event pages will be described later.

[0029] The display control unit 117 controls the display of messages displayed via SNS and generated event pages. The communication control unit 118 controls communication with external devices (e.g., user terminal 200, SNS server 300, generation AI server 350, etc.) and transmits and receives data.

[0030] The communication unit 120 is a communication interface for communicating with external devices via a network NW. The communication unit 120 may be configured to support multiple communication standards depending on the configuration of the network NW.

[0031] The memory unit 130 is a storage device for storing programs, data, etc., for executing various control processes and functions within the control unit 110. The memory unit 130 is composed of volatile / non-volatile storage devices such as RAM (Random Access Memory), ROM (Read Only Memory), HDD (Hard Disk Drive), and flash memory. The memory unit 130 includes a database (hereinafter referred to as DB) for managing data corresponding to the functions described later.

[0032] Event DB131 manages event information. The information items included in the event information may include, but are not limited to, the organizer, title, performance date and time, venue, price, performers, event images, and notes.

[0033] Event page DB132 manages event pages created based on event information. Event pages are published online based on specified publication date and time information. Ticket DB133 manages ticket information for tickets associated with events. Information items included in ticket information may include, but are not limited to, the corresponding event, ticket type, purchaser, sales date and time, target audience, and maximum number of tickets.

[0034] User DB134 manages user information for users, including event organizers and ticket purchasers. Information items included in user information may include, but are not limited to, username, identification information, attribute information, and usage history information. Usage history information may include ticket purchase history and event page creation history.

[0035] Form DB 135 manages the form information of the forms that make up the event page. The form information may be managed in various forms depending on the type and purpose of the event. Furthermore, the form information may also be used together with prompts as input to the generation AI described later. Prompt DB 136 is used as input to the generation AI described later and manages prompts for instructing the output by the generation AI. Prompts are predetermined and may be used differently depending on the event page to be generated.

[0036] The configurations of the functional units and databases shown above are merely examples and are not limiting. For example, one functional unit may be divided into multiple units, or multiple functional units may be combined into one. Furthermore, additional functional units and databases other than those mentioned above may be provided.

[0037] Figure 3 is a block diagram showing an example of the functional configuration of the user terminal 200 according to this embodiment. The user terminal 200 is composed of a control unit 210, a storage unit 220, a communication unit 230, an operation unit 240, a display unit 250, and an external IF (Interface) 260.

[0038] The control unit 210 is responsible for controlling the operation of the user terminal 200. The control unit 210 is composed of, for example, a CPU (Central Processing Unit) and a GPU (Graphics Processing Unit), and provides various functions by reading and executing various programs and data stored in the storage unit 220.

[0039] The memory unit 220 is a storage device for storing programs and data for executing various control processes and functions of the control unit 210. The memory unit 220 is composed of volatile / non-volatile storage devices such as RAM (Random Access Memory), ROM (Read Only Memory), HDD (Hard Disk Drive), and flash memory. In this embodiment, the memory unit 220 contains programs for an SNS application 221 and a web browser 222. The SNS application 221 functions as a communication tool and is used when creating an event page, which will be described later in this embodiment. The web browser 222 functions as a tool for browsing online sites and the like.

[0040] The communication unit 230 is a communication interface for communicating with external devices via a network NW. The communication unit 230 may be configured to support multiple communication standards depending on the configuration of the network NW.

[0041] The operation unit 240 is an interface for receiving operations from the user of the user terminal 200. The operation unit 240 may consist of a mouse, keyboard, etc. The display unit 250 is an interface for displaying various screens and consists of a display, etc. A touch panel display that integrates the operation unit 240 and the display unit 250 may be used. The external IF 260 is an interface for connecting to various devices and may be a connection interface to, for example, an imaging unit (not shown) for taking images or sensors for acquiring predetermined information.

[0042] [Example of UI Screen Configuration] An example of creating an event page according to this embodiment using SNS will be described. Figures 4A to 4H show examples of the display of the SNS application 221 on the user terminal 200 when creating an event page. Here, an example is shown in which a user, such as the event organizer, operates the user terminal 200 to create an event page. In addition, the processing flow may include processes such as authentication, authorization, and user registration, but here we will focus on the functions according to this embodiment in our explanation.

[0043] First, the user launches the SNS application 221 on the user terminal 200 and opens the account on the event management server 100. Figure 4A shows the SNS screen 400 of the event management server 100 account opened in the SNS application 221. The SNS screen 400 consists of account information 401 indicating the communication partner and a display area 402 showing the communication content. Note that here, the display of input areas for text input and soft keyboards is omitted, and the focus is on the display of messages in the display area 402. Also, posted messages are displayed in chronological order from top to bottom in the display area 402. In the display area 402, right-aligned messages indicate messages posted by the user on the user terminal 200, and left-aligned messages indicate messages posted by the communication partner (event management server 100 in this example). Note that the layout and display manner of messages in the display area 402 are not limited to this and can be adjusted as desired.

[0044] In the SNS application 221, when communication with the event management server 100 is started, a message 403 is posted from the event management server 100 side to the user to instruct a desired processing content. Such a message may be a default character string, or processable contents that can be instructed may be presented in a selectable manner.

[0045] Figure 4B shows a state where the user has posted a message 404 stating "Create a new event". That is, the user instructs the event management server 100 to create a new event via the SNS application 221. Information of the posted message 404 is notified to the event management server 100 via the SNS server 300.

[0046] Figure 4C shows a state where, in response to the user posting the message 404, the event management server 100 posts a message 405 prompting submission of event information. That is, the event management server 100 prompts input while exemplifying information items necessary for creating an event page. The information items suggested for input in the message 405 are not limited to the contents illustrated in the figure.

[0047] Figure 4D shows a state where, in response to the event management server 100 posting the message 405, the user posts a message 406 including event information. In the example of Figure 4D, the message 406 is input by the user with content conforming to the message 405 from the event management server 100. However, character string input to the SNS application 221 is in free format, and the event information input by the user may not necessarily conform to the content of the message 405. In other words, user input in various states (such as irregular arrangement of items or missing items) is assumed. In the present embodiment, excess or deficiency of event information in the input at this point is allowed. As an example, the following event information may be input to the SNS application 221.

[0048] (Input Example 1) [3 / 28 (Fri) Shibuya 15 Performance Overview] ▼Title: XXYY ▼Date: 3 / 28 (Fri) ▼OPEN / START: 19:10 / 19:30 ▼Venue: Shibuya 15 ▼Address: XX-YY-ZZ Shibuya, Shibuya-ku, Tokyo ▼Price: Priority ¥2,500 / Regular ¥1,000 / +¥500 on the day (drink fee not included in each) ▼Admission Order: (1) Priority by assigned number (2) Regular by assigned number (3) Door admission ▼Performers: XXXX / YYYY 18:00 Arrival 19:10 OPEN 19:30 (1) 20:00 (2) 20:30 Merchandise sale after show 21:40 Merchandise sale ends 22:00 Full clearance · Maximum 8 microphones used

[0049] (Input Example 2) [Title] PoP PLACE [Venue] UU Live House [Performer] poppi [Date and Time] 3 / 19 (Wed) OPEN 18:30 START 19:00 [URL] https: / / ttt.com / poppi0319 [General Advance Reservation] 3 / 14 12:00 ~ 3 / 19 15:00 ■Priority Admission Ticket ¥3,000+D 100 tickets A1~ *Credit card payment only ■General Admission Ticket ¥1,500+D 130 tickets B1~

[0050] (Input Example 3) 4 / 13 (Sun) Fille A Tokyo-Nagoya-Osaka Tour Final One-Man Show Venue: Umeda Hall Time: 18:00 / 18:30 Price: SS Ticket with Benefits ¥10,000 / Priority S ¥3,000 / General A ¥1,000 Performer Fille A 18:30-19:50 LIVE 20:00-22:00 Benefit event Sales URL: https: / / ttt.com / fillea_final_oneman [Announcement Embargo Lift] 3 / 13 (Thu) 20:00 [Benefit & Priority Tickets] 3 / 14 (Fri) 20:00 - 4 / 1 (Mon) 23:59 [General & Complimentary Tickets] 3 / 15 (Sat) 20:00 - 4 / 13 (Sun) 20:00

[0051] (Input Example 4) 〇April 18 (Fri) Title: I Wish I Can Ask As An Idol Fan Location: Number One Gate Time: OPEN 18:15 / START 18:35 Price: Priority ¥2,000 / General ¥1,000 (+1D) Performers: TTT / CCC / OOO

[0052] Figure 4E shows the state in which the event management server 100 posts a message 407 prompting the user to confirm the address information of the event page corresponding to the event, in response to the user posting a message 406 containing event information. The address information is shown as a URL (Uniform Resource Locator), and the event management server 100 determines the address information that is unique to the event. In this example, "https: / / ttt.com / ladyp250405" is presented as the address information for the newly created event page. The address information may be determined using the string in the message 406 posted by the user, or by combining unpublished strings. Message 407 displays buttons 408 and 409 that can be selected to indicate whether or not to accept the presented address information. In this example, the user selects button 408, and as a result, a message 410 indicating acceptance of the presented address information, "Yes," is posted.

[0053] Figure 4F shows the state in which the event management server 100 posts a message 411 prompting the user to post additional information to be used to create the event page, in response to the user posting a message 410. In this example, the user is prompted to post image data as additional information, but this is not the only option. In addition, multiple types of additional information may be requested in sequence. Furthermore, in this example, in response to the event management server 100 posting a message 411, the user posts a message 412 indicating that there is no image data.

[0054] Figure 4G shows the state in which the event management server 100 has created an event page in response to the user posting message 412, and has posted message 413 prompting the user to enter instructions regarding the result. This example assumes that the event page has been successfully generated. In this example, the instructions available to the user are to display a preview screen of the event page (button 414), publish the event page immediately (button 415), schedule publication to specify the publication date and time of the event page (button 416), and edit the created event page (button 417). If any of buttons 414 to 417 are selected, the user will be redirected to the corresponding screen. These screens may be displayed, for example, using the web browser 222 on the user terminal 200. Note that the instructions are not limited to these, and other processes may be presented as selectable options.

[0055] Figure 4H shows the state in which the event management server 100 creates an event page based on event information posted by a user (for example, message 406), and posts a message 418 indicating that an inconsistency has occurred. In this example, the event management server 100 identifies an inconsistency in the date (event schedule) information included in the event information when creating the event page. Message 418 includes a button 419 to instruct the user to transition to the event information editing screen (not shown). This editing screen may be displayed using, for example, a web browser 222 on the user terminal 200.

[0056] The SNS-based communication between the user and the event management server 100 shown in Figures 4A to 4H is merely an example and is not limited to this. For example, in Figures 4A to 4B, processing does not necessarily start with a message display from the event management server 100, but may start with a message posted by the user. Furthermore, the system may be configured to handle the omission of some message exchanges. For example, even if messages 404 and 405 in Figure 4C are omitted and the user posts message 406, which corresponds to event information, processing may proceed as if a request for the creation of a new event page has been made.

[0057] Furthermore, Figure 4H is shown as an example of when inconsistencies in event information are identified, but it is not limited to this. For example, the event management server 100 may be configured to display the information item in which the inconsistency has been identified and its detected value, and then accept corrections to the value by having the user post the corrected value via SNS. In that case, the event management server 100 may check the value entered as the corrected value again and then update the event page.

[0058] Figures 5A and 5B show an example of the configuration of an event page created on the event management server 100. Figure 5A shows a preview screen 500 of an event page before publication. The attribute area 501 shows the attribute information of the displayed preview screen 500. In this example, it shows that the screen is a preview screen and information about the planned publication date. The information items of the attribute information are not limited to this example, and other information items may be shown.

[0059] The event information area 502 displays various event-related information. Each event information is extracted and used from various messages posted on the SNS app 221. The preview screen 500 displays an image 503 (flyer image) and detailed event information 504 as event information.

[0060] Figure 5B shows an example of the configuration of the display screen 510 of the event page after it has been published. The display screen 510 may include an image 511, overview information 512, ticket information 513, and detailed information 514 as event information. The overview information 512 may use predefined information items from among multiple information items in the event information. The ticket information 513 may show information items related to tickets from the event information. The detailed information 514 may include more detailed information items related to the event from the event information.

[0061] Note that the event page configuration shown in Figures 5A and 5B is just an example, and the configuration and display content may differ depending on the type of event. The event page configuration information may be registered as multiple types of forms in Form DB 135 and used interchangeably. More specifically, the event details 504 and details 514 may include a summary based on event information entered by the user (for example, message 406), or text corresponding to a predetermined form (such as notes or access information) may be added. Alternatively, a predetermined form may be used or predetermined text may be embedded in the event page based on the creation history of past event pages.

[0062] [Event Page Creation Process] The process for creating an event page using the SNS and generation AI according to this embodiment will be described. Each information item of the event information included in the generated event page is extracted from the message (string information) posted to the SNS application 221 using the generation AI. Then, the event page is generated using the extracted event information. The flow of this process will be explained with reference to Figures 6 and 7.

[0063] Figure 6 shows the processing sequence for event creation according to this embodiment. This processing sequence is realized through the cooperation of each device constituting the event management system 1. Each process is carried out, for example, by the control unit of the processing-main device reading and executing programs and data stored in the storage unit.

[0064] In step S601, the user terminal 200 receives a message from the user via the SNS application 221 instructing the creation of an event page, and posts the message. Specifically, based on the user's instructions, the user terminal 200 posts message 404 as shown in Figure 4B. The information of the posted message is sent to the SNS server 300.

[0065] In step S602, the SNS server 300 notifies the event management server 100, which is the recipient of the message, of the information about the message posted by the user terminal 200 in step S601.

[0066] In step S603, the event management server 100 obtains information about the message notified from the SNS server 300.

[0067] In step S604, the event management server 100 analyzes the message obtained in step S603 and identifies the processing requested in the message. This processing may involve, for example, using known natural language processing to extract predefined strings or words and identifying the processing associated with those strings or words. Alternatively, specific strings may be extracted using known matching processing. Or, the event management server 100 may request the generation AI server 350 to identify the processing requested by the user based on the message obtained here. In this case, the processing request is made to the generation AI server 350 separately from the use of the generation AI to extract event information in a later stage. In this example, it will be explained assuming that an instruction to create a new event page has been given.

[0068] In step S605, the event management server 100 posts a message to the SNS corresponding to the process identified in step S604. Specifically, the event management server 100 posts a message as shown in message 405 in Figure 4C. The content of the message corresponding to each requested process may be predefined.

[0069] In step S606, the SNS server 300 notifies the user terminal 200, which is the recipient of the message, of the information of the message posted by the event management server 100 in step S605.

[0070] In step S607, the user terminal 200 displays the message notified by the SNS server 300 using the SNS application 201. Specifically, the user terminal 200 displays the message as shown in Figure 4C.

[0071] In step S608, the user terminal 200 posts a message containing event information via the SNS application 221 based on instructions from the user. Specifically, the user terminal 200 posts message 406 as shown in Figure 4D based on user instructions. As shown in input examples 1 to 4 above, the posted messages are not necessarily in a uniform form. The posted messages are sent to the SNS server 300.

[0072] In step S609, the SNS server 300 notifies the event management server 100, which is the recipient of the message, of the information of the message posted by the user terminal 200 in step S608.

[0073] In step S610, the event management server 100 obtains information about the message notified from the SNS server 300.

[0074] In step S611, the event management server 100 sends an analysis request to the generation AI server 350 that includes the message information acquired in step S610. The analysis request includes a prompt indicating the processing to be performed on the message information. The content of the prompt may be predefined in association with the processing content identified in step S604. Alternatively, the instructions to be included in the prompt may be changed based on the past operation history or creation history of the user requesting the creation of the event page. For example, it may be instructed to also refer to past messages and event information posted by the user. Furthermore, the event management server 100 may perform predetermined preprocessing on the message string information before sending the analysis request to the generation AI server 350. The preprocessing here is not particularly limited, but for example, predetermined characters may be deleted, or predetermined information may be added to facilitate analysis. Preprocessing may also be performed according to the specifications and characteristics of the generation AI provided by the generation AI server 350.

[0075] In step S612, the generating AI server 350 performs an analysis using the message information and prompts included in the analysis request as input data, in response to the analysis request from the event management server 100. The output data of the analysis process consists of information items of event information extracted from the message information and their corresponding values. If there are information items from which values ​​could not be extracted, the output data may indicate this fact.

[0076] In step S613, the generating AI server 350 notifies the event management server 100 of the results of the analysis process in step S612.

[0077] In step S614, the event management server 100 obtains the analysis results from the generation AI server 350 and stores them as event information to be used to create the event page. Furthermore, the event management server 100 issues the address information of the event page. The address information may use the event information string obtained as the analysis result, or it may use an unassigned string based on a predetermined rule.

[0078] In step S615, the event management server 100 posts a message to the SNS requesting confirmation of the address information generated in step S614. Specifically, the event management server 100 posts a message as shown in message 407 in Figure 4E.

[0079] In step S616, the SNS server 300 notifies the user terminal 200, which is the recipient of the message, of the information of the message posted by the event management server 100 in step S615.

[0080] In step S617, the user terminal 200 displays the message notified by the SNS server 300 using the SNS application 221. Specifically, the user terminal 200 displays a message 407 prompting the user to confirm the address information, as shown in Figure 4E.

[0081] In step S618, the user terminal 200 posts a message indicating whether to allow or deny access to address information via the SNS application 221, based on instructions from the user. Specifically, the user terminal 200 posts message 410 as shown in Figure 4E, based on user instructions. The message containing the address information is sent to the SNS server 300.

[0082] In step S619, the SNS server 300 notifies the event management server 100, which is the recipient of the message, of the information about the message posted by the user terminal 200 in step S618.

[0083] In step S620, the event management server 100 obtains information about the message notified from the SNS server 300.

[0084] In step S621, the event management server 100 identifies information items to be obtained from the user as additional information, based on the message obtained in step S620 and the event information obtained in step S614. The additional information may be, for example, image data or audio data. Also, if address information is instructed to be disallowed in step S618, address information may be used as additional information. Furthermore, the information items of event information necessary for creating an event page may differ depending on the type of event. Depending on the number of additional information items identified, steps S622 to S627 may be repeated.

[0085] In step S622, the event management server 100 posts a message to the SNS requesting additional information. Specifically, the event management server 100 posts a message as shown in message 411 in Figure 4F.

[0086] In step S623, the SNS server 300 notifies the user terminal 200, which is the recipient of the message, of the information of the message posted by the event management server 100 in step S622.

[0087] In step S624, the user terminal 200 displays the message notified by the SNS server 300 in the SNS application 221. Specifically, the user terminal 200 displays a message 411 prompting the user to post additional information, as shown in Figure 4F.

[0088] In step S625, the user terminal 200 posts a message containing additional information via the SNS application 221 based on instructions from the user. Specifically, the user terminal 200 posts message 412 as shown in Figure 4F based on user instructions. The message containing the address information is sent to the SNS server 300.

[0089] In step S626, the SNS server 300 notifies the event management server 100, which is the recipient of the message, of the information of the message posted by the user terminal 200 in step S625.

[0090] In step S627, the event management server 100 obtains information about the message notified from the SNS server 300.

[0091] In step S628, the event management server 100 creates an event page using the event information extracted using the generation AI and the information obtained as additional information. The event page may be created by pre-defining a form according to the type of event, etc., and filling in the values ​​of each item of the event information into that form. Alternatively, a separate generation AI for creating event pages may be prepared, and the event information, additional information, and prompts may be input to the generation AI to output the event page. The generation AI for generating event pages may be provided by the event management server 100 or by an external server. Furthermore, the event management server 100 checks the consistency of the event information obtained up to this point. For example, the event management server 100 may check whether there are any inconsistencies or obvious errors in the date and time of the event, the location of the event, the fee, etc. If inconsistencies or obvious errors are detected, they may be treated as requiring user verification.

[0092] In step S629, the event management server 100 posts a message to the SNS regarding the result of creating the event page. Specifically, if the event page is created successfully, the event management server 100 posts a message like the one shown in message 413 in Figure 4G. On the other hand, if it is determined that user confirmation is required when creating the event page in step S628, the event management server 100 posts a message like the one shown in message 418 in Figure 4H.

[0093] In step S630, the SNS server 300 notifies the user terminal 200, which is the recipient of the message, of the information of the message posted by the event management server 100 in step S629.

[0094] In step S631, the user terminal 200 displays the message notified by the SNS server 300 using the SNS application 221. Specifically, the user terminal 200 displays a message prompting instructions for the generated event page, as shown in Figures 4G and 4H. By operating various buttons in response to these messages, the user can, for example, display the corresponding screen via the web browser 222. Subsequent processing may be performed via the web browser 222. Alternatively, editing processing targeting an already created event page may be performed in a similar flow to the processing sequence in Figure 6.

[0095] Figure 7 is a flowchart of the event page creation process in the event management server 100 according to this embodiment. This process flow shows the flow focusing on the processing of the event management server 100 in Figure 6. This process flow is realized, for example, when the control unit 110 of the event management server 100 reads and executes programs and various data stored in the storage unit 130, thereby operating as each part shown in Figure 2. For the sake of simplicity, the processing entity is described here as the event management server 100.

[0096] In step S701, the event management server 100 receives a request to create an event page from the user terminal 200 via the SNS server 300. Specifically, the event management server 100 analyzes the message posted to the SNS and identifies that the requested process is the process of creating an event page. This process corresponds to steps S603 to S604 in Figure 6.

[0097] In step S702, the event management server 100 requests the user terminal 200 via the SNS server 300 to input the event information necessary for creating the event page. This step corresponds to step S605 in Figure 6.

[0098] In step S703, the event management server 100 receives string information containing event information via the SNS server 300. This step corresponds to step S610 in Figure 6.

[0099] In step S704, the event management server 100 sends an analysis request to the generation AI, which includes the acquired string information and a prompt corresponding to the request received in step S701, thereby acquiring the event information items and their values ​​contained in the string information. This extracts the event information used to create the event page from the string information. This process corresponds to steps S611 and S614.

[0100] In step S705, the event management server 100 generates address information for the event page to be created. This address information corresponds to the URL when the event page is published online. This step corresponds to step S614 in Figure 6.

[0101] In step S706, the event management server 100 requests the user terminal 200 to confirm the address information generated in step S706 via the SNS server 300. This step corresponds to step S615 in Figure 6.

[0102] In step S707, the event management server 100 obtains the address information verification result via the SNS server 300. If the address information is accepted as a result of the verification (step S707: YES), the event management server 100 proceeds to step S709. On the other hand, if the address information is not accepted (step S707: NO), the event management server 100 proceeds to step S708.

[0103] In step S708, the event management server 100 is configured to treat the address information as additional information. That is, by treating it as additional information, it may be controlled to accept new address information from the user or to reissue and reconfirm the address information. This step corresponds to step 621 in Figure 6.

[0104] In step S709, the event management server 100 identifies information items that the user is requested to input as additional information. The additional information is information items necessary when creating the address page, and may be information items that could not be extracted in step S704. This step corresponds to step 621 in Figure 6.

[0105] In step S710, the event management server 100 requests input from the user terminal 200 via the SNS server 300 for information items that have not yet been acquired from the information items identified as additional information in step S709. As a result, the event management server 100 acquires the values ​​of the information items as additional information via the SNS server 300. At this time, the acquired message (string information) may be further analyzed by the generation AI server 350 or processed by the event management server 100 using natural language processing to extract the values ​​of the event information. Note that additional information is not always input, as shown in message 412 in Figure 4F. This process corresponds to step S622 in Figure 6.

[0106] In step S711, the event management server 100 determines whether it has requested input for all of the additional information identified in step S709. If there are any unrequested information items (step S711: NO), the event management server 100 returns to step S710 and repeats the process. On the other hand, if the request for input of all additional information has been completed (step S711: YES), the event management server 100 proceeds to step S712.

[0107] In step S712, the event management server 100 creates an event page using the event information and additional information acquired so far, as well as the form information for the event page. This step corresponds to step S628 in Figure 6.

[0108] In step S713, the event management server 100 verifies the consistency of the event information and additional information acquired so far. For example, the event management server 100 may check for inconsistencies or obvious errors in the date and time of the event, location, fees, etc. The items to be checked may be predetermined. If the results of this process determine that the information is inconsistent, it is determined that user verification is required. This process corresponds to step S628 in Figure 6.

[0109] In step S714, the event management server 100 determines whether user confirmation is required based on the results of the processing in step S712. If user confirmation is required (step S714: YES), the event management server 100 proceeds to step S716. On the other hand, if user confirmation is not required (step S714: NO), the event management server 100 proceeds to step S715.

[0110] In step S715, the event management server 100 notifies the user terminal 200 of the event page creation result via the SNS server 300. This step corresponds to step S629 in Figure 6, and more specifically, a post like the message 413 shown in Figure 4G is made.

[0111] In step S716, the event management server 100 notifies the user terminal 200 of the creation result, including a request to confirm the event page, via the SNS server 300. This step corresponds to step S629 in Figure 6, and more specifically, a post like the message 418 shown in Figure 4H is made. Then, this processing flow ends.

[0112] In summary, this embodiment makes it possible to reduce the effort required for data entry on various event websites and improve the convenience of website-related work. In particular, by combining SNS and generation AI to create event pages, users can easily input text on SNS, and the information necessary for creating the event page can be appropriately extracted and used from the information contained in the message. As a result, the workload of both event organizers and event page creators can be significantly reduced.

[0113] <Other Embodiments> The above embodiments describe an example of an SNS in which strings can be entered as messages. However, the invention is not limited to this, and other data formats may be used, or it may be applied to communication tools different from the SNS described above. For example, in addition to string information, files in data formats such as PDF (Portable Document Format), Excel®, Word®, and text format may be used as input. In this case, the string data may be extracted from the files in each data format and used as event information for creating an event page. Furthermore, the functions of the present invention may be combined with other forms of communication tools such as Slack®, Teams®, Chatwork®, and email.

[0114] Furthermore, as shown in Figures 4A to 4B, the above embodiment was explained using the creation of a new event as an example. The processing requested in response to message 403 in Figure 4A may be other than the creation of a new event page. For example, examples of processing that can be requested via SNS may include editing an already created event page, previewing an event page, searching an event page, and analyzing ticket purchase information via an event page.

[0115] For example, the result of obtaining and analyzing the string in step S603 of Figure 6 may indicate a request for processing related to editing the event page. In this case, the process may be performed from step S626 onwards after identifying an event page that has already been created. Alternatively, the process may be performed from step S621 onwards after determining whether or not there is additional information necessary to edit the event page.

[0116] Examples of ticket analysis processes may include analyzing ticket sales via the event page, statistical information related to the same organizer (such as the organizer or participating artists), inventory levels, and attribute distribution of purchasing users. The analysis methods are not particularly limited, and publicly known methods may be used. Some of this analytical information may be instructed to be included, for example, on event pages under development or already published event pages.

[0117] Furthermore, some parts of the processing flow shown in Figures 6 and 7 may be rearranged, or multiple processes may be performed together in a single step. In other words, the timing of message processing by the generation AI and the timing of communication between the user and the event management server 100 via SNS are not limited to the examples of the above embodiments, and may be rearranged, integrated, omitted, or added as appropriate.

[0118] Furthermore, in the present invention, the functions of one or more embodiments described above can also be realized by supplying a program or application to a system or device using a network or storage medium, and one or more processors in the computer of that system or device reading and executing the program.

[0119] Alternatively, one or more functions may be implemented using a circuit (for example, an ASIC (Application Specific Integrated Circuit) or an FPGA (Field Programmable Gate Array)).

[0120] Although various embodiments have been described above with reference to the drawings, it goes without saying that this disclosure is not limited to these examples. It will be clear to those skilled in the art that various modifications, alterations, substitutions, additions, deletions, and equivalents can occur within the scope of the claims, and these will naturally fall within the technical scope of this disclosure. Furthermore, the components of the various embodiments described above can be combined arbitrarily without departing from the spirit of the invention.

[0121] Thus, the present invention is not limited to the embodiments described above. It is also intended and within the scope of protection to be provided for the combination of each configuration of the embodiments, as well as for modifications and applications by those skilled in the art based on the description in the specification and well-known technology.

[0122] As described above, the following matters are disclosed in this specification:

[0123] (Technology 1) An information processing system (e.g., 1,100) for creating an event page (e.g., 510) to be published online, comprising: an acquisition unit (e.g., 110, 113) for acquiring string information about an event entered via SNS (Social Networking Service); an extraction unit (e.g., 110, 114) for extracting event information from the string information using a large-scale language model for creating an event page for the event; and a creation unit (e.g., 110, 116) for creating an event page for the event using the event information. This configuration makes it possible to reduce the effort required for data entry related to various event sites and improve the convenience of site-related work.

[0124] (Technology 2) An information processing system according to Technology 1, comprising: an identification unit (e.g., 110, 116) that identifies information items that require user confirmation from the event information extracted by the extraction unit; and a display control unit (e.g., 110, 113, 117) that allows the user to confirm the contents of the information items identified by the identification unit via the SNS. With this configuration, for example, a user can easily grasp the event information that needs to be confirmed when creating an event page via the SNS.

[0125] (Technology 3) The information processing system according to Technology 2, wherein the identification unit further identifies unacquired information items among the information items required to create an event page for the event, based on the event information extracted by the extraction unit, and the display control unit notifies the user of the unacquired information items identified by the identification unit via the SNS, and prompts the user to input the uninputted information items via the SNS. With this configuration, for example, it is possible to present the user with the information necessary to create an event page via the SNS and prompt them to input it. In addition, the user can easily grasp the information that needs to be entered via the SNS.

[0126] (Technical 4) The information processing system according to Technical 2 or Technical 3, wherein the display control unit further receives additional information including at least one of image data and audio data via the SNS, and the creation unit further creates an event page for the event using the additional information. With this configuration, for example, by receiving data of other formats in addition to text data via the SNS, it becomes possible to easily create an event page using such data.

[0127] (Technical 5) The information processing system according to any one of Technical 2 to 4, wherein the display control unit displays instructions via the SNS to display a preview screen of the event page created by the creation unit. With this configuration, for example, a user can easily check the preview screen of the event page created via the SNS.

[0128] (Technical 6) The information processing system according to any one of Technical 2 to 5, wherein the display control unit displays instructions via the SNS for immediately publishing the event page created by the creation unit. With this configuration, for example, a user can easily instruct the immediate publication of an event page created via the SNS.

[0129] (Technical 7) An information processing system according to any one of Technical 2 to Technical 6, wherein the display control unit displays instructions via the SNS for setting the date and time for publishing the event page created by the creation unit. With this configuration, for example, a user can easily instruct the SNS to make a publication reservation for an event page created.

[0130] (Technical 8) The information processing system according to any one of Technical 2 to Technical 7, wherein the display control unit displays instructions via the SNS to display the editing screen of the event page created by the creation unit. With this configuration, for example, a user can easily instruct access to the editing screen of the event page created via the SNS.

[0131] (Technology 9) The information processing system according to any one of Technology 1 to Technology 8, wherein the creation unit creates the event page by using the event information as input data for a generating AI (Artificial Intelligence). With this configuration, for example, an event page can be easily created using a generating AI and event information extracted from messages posted on SNS.

[0132] (Technical 10) A control method for an information processing system (e.g., 1,100) that creates an event page (e.g., 510) to be published online, comprising: an acquisition step of acquiring string information relating to an event entered via SNS (Social Networking Service); an extraction step of extracting event information for creating an event page for the event from the string information using a large-scale language model; and a creation step of creating an event page for the event using the event information. This configuration makes it possible, for example, to reduce the effort required to input data related to various event sites and to improve the convenience of site-related work.

[0133] (Technical 11) A program to cause a computer (e.g., 100) to function as: an acquisition unit (e.g., 110, 113) that acquires string information about an event entered via SNS (Social Networking Service); an extraction unit (e.g., 110, 114) that extracts event information from the string information using a large-scale language model to create an event page for the event; and a creation unit (e.g., 110, 116) that creates an event page for the event using the event information. This configuration makes it possible to reduce the effort required to input data for various event sites and improve the convenience of site-related work.

[0134] (Technical 12) An information processing system (e.g., 1,100) for managing event pages published online, comprising: an acquisition unit (e.g., 110, 113) that acquires information about an event entered via a communication tool; an extraction unit (e.g., 110, 114) that extracts event information related to the event from the information using a generation AI; and an execution unit (e.g., 110, 116) that performs processing on the event page of the event based on the event information. This configuration makes it possible, for example, to reduce the effort required to input data for various event sites and to improve the convenience of site-related work.

[0135] (Technical 13) A control method for an information processing system (e.g., 1,100) that manages event pages published online, comprising: an acquisition step of acquiring information about an event entered via a communication tool; an extraction step of extracting event information related to the event from the information using a generating AI; and an execution step of performing processing on the event page of the event based on the event information. This configuration makes it possible, for example, to reduce the effort required to input data for various event sites and to improve the convenience of site-related work.

[0136] (Technical 14) A program to cause a computer (e.g., 100) to function as: an acquisition unit (e.g., 110, 113) that acquires information about an event entered via a communication tool; an extraction unit (e.g., 110, 114) that extracts event information about the event from the information using a generation AI; and an execution unit (e.g., 110, 116) that performs processing on the event page of the event based on the event information. This configuration makes it possible, for example, to reduce the effort required to input data for various event sites and to improve the convenience of site-related work.

[0137] The present invention is useful, for example, as an apparatus, system, or method for creating and publishing websites for various events.

[0138] Although various embodiments have been described above with reference to the drawings, it goes without saying that the present invention is not limited to these examples. It is clear to those skilled in the art that various modifications or alterations can be conceived within the scope of the claims, and these will naturally also fall within the technical scope of the present invention. Furthermore, the components of the above embodiments may be combined in any way without departing from the spirit of the invention.

[0139] This application is based on a Japanese patent application (JP 2025-054506) filed on March 27, 2025, the contents of which are incorporated herein by reference.

[0140] 1...Event Management System 100...Event Management Server 110...Control Unit 111...Data Management Unit 112...Instruction Reception Unit 113...SNS Integration Unit 114...Generation AI Integration Unit 115...Site Management Unit 116...Event Page Creation Unit 117...Display Control Unit 118...Communication Control Unit 120...Communication Unit 130...Storage Unit 131...Event DB 132...Event Page DB 133...Ticket DB 134...User DB 135...Form DB 136...Prompt DB 200...User Terminal 210...Control Unit 220...Storage Unit 221...SNS App 222...Web Browser 230...Communication Unit 240...Operation Unit 250...Display Unit 260...External IF 300...SNS Server 350...Generation AI Server

Claims

1. An information processing system for creating an event page to be published online, comprising: an acquisition unit that acquires string information relating to an event entered via SNS (Social Networking Service); an extraction unit that uses a large-scale language model to extract event information for creating an event page for the event from the string information; and a creation unit that uses the event information to create an event page for the event.

2. The information processing system according to claim 1, further comprising: an identification unit that identifies information items that require user confirmation from the event information extracted by the extraction unit; and a display control unit that allows the user to confirm the contents of the information items identified by the identification unit via the SNS.

3. The information processing system according to claim 2, wherein the identification unit further identifies unacquired information items among the information items required to create an event page for the event, based on the event information extracted by the extraction unit, and the display control unit notifies the unacquired information items identified by the identification unit via the SNS, and prompts the user to input the unentered information items via the SNS.

4. The information processing system according to claim 2, wherein the display control unit further receives additional information including at least one of image data and audio data via the SNS, and the creation unit further creates an event page for the event using the additional information.

5. The information processing system according to claim 2, wherein the display control unit displays instructions via the SNS for displaying a preview screen of the event page created by the creation unit.

6. The information processing system according to claim 2, wherein the display control unit displays instructions via the SNS for immediately publishing the event page created by the creation unit.

7. The information processing system according to claim 2, wherein the display control unit displays instructions via the SNS for displaying a screen for setting the date and time to publish the event page created by the creation unit.

8. The information processing system according to claim 2, wherein the display control unit displays instructions via the SNS for displaying the editing screen of the event page created by the creation unit.

9. The information processing system according to claim 1, wherein the creation unit creates the event page by using the event information as input data for an Artificial Intelligence (AI) generation AI.

10. A control method for an information processing system that creates an event page to be published online, comprising: an acquisition step of acquiring string information relating to an event entered via SNS (Social Networking Service); an extraction step of extracting event information for creating an event page for the event from the string information using a large-scale language model; and a creation step of creating an event page for the event using the event information.

11. A program to cause a computer to function as: an acquisition unit that acquires string information about an event entered via SNS (Social Networking Service); an extraction unit that extracts event information from the string information using a large-scale language model for creating an event page for the event; and a creation unit that creates an event page for the event using the event information.

12. An information processing system for managing event pages published online, comprising: an acquisition unit that acquires information about an event entered via a communication tool; an extraction unit that extracts event information related to the event from the information using a generation AI; and an execution unit that performs processing on the event page of the event based on the event information.

13. A control method for an information processing system that manages event pages published online, comprising: an acquisition step of acquiring information about an event entered via a communication tool; an extraction step of extracting event information relating to the event from the information using a generating AI; and an execution step of performing processing on the event page of the event based on the event information.

14. A program to cause a computer to function as: an acquisition unit that acquires information about an event entered via a communication tool; an extraction unit that extracts event information related to the event from the information using a generating AI; and an execution unit that performs processing on the event page of the event based on the event information.

Images