Information processing system, information processing method, information processing device, terminal and storage medium

Abstract

A system including at least an information processing apparatus for providing a messaging service comprises: a chat storage unit that stores chat information, including messages sent by a second user to a first user, in association with a first user identification information of a first user; and one or more control units that perform the following processing: outputting specific information for a specific one or more registration messages based on the acquisition of one or more registration messages; appending a first registration message specified by the first specific information to the chat storage unit based on a request containing the first user identification information and the first specific information; and appending a second registration message specified by the second specific information to the chat storage unit based on a request containing the first user identification information and the second specific information.

Description

Technical Field

[0001] This disclosure relates to information processing systems, information processing methods, information processing devices, terminals, and storage media. Background Technology

[0002] Technology related to a messaging service that enables multiple users to send, receive, and view messages using their respective terminals has been proposed (e.g., Patent Document 1).

[0003] Prior art literature

[0004] Patent documents

[0005] Patent Document 1: Japanese Patent Application Publication No. 2014-160467 Summary of the Invention

[0006] According to a first aspect of the present invention, a system comprising at least an information processing apparatus for providing a messaging service includes: a chat storage unit that stores chat information, including messages sent by a second user to a first user, in association with a first user identification information of a first user; and one or more control units that perform the following processing: based on the case of obtaining one or more registration messages, outputting specific information for a specific one or more registration messages; based on a request carrying the first user identification information and the first specific information in the specific information, appending a first registration message specified by the first specific information to the chat storage unit; and based on a request carrying the first user identification information and the second specific information in the specific information, appending a second registration message specified by the second specific information to the chat storage unit.

[0007] According to a second aspect of the present invention, an information processing method of a system including at least an information processing apparatus for providing a messaging service includes the following processing: storing chat information, including messages sent by a second user to a first user, in a chat storage unit of the system in association with a first user identification information of a first user; outputting specific information for a specific one or more registration messages using one or more control units in the system based on the case of obtaining one or more registration messages; appending a first registration message specified by the first specific information to the chat storage unit using one or more control units based on a request carrying the first user identification information and the first specific information in the specific information; and appending a second registration message specified by the second specific information to the chat storage unit using one or more control units based on a request carrying the first user identification information and the second specific information in the specific information.

[0008] According to a third aspect of the present invention, an information processing apparatus for providing a messaging service includes: a chat storage unit that stores chat information, including messages sent by a second user to a first user, in association with a first user identification information of a first user; and a control unit that performs the following processing: outputting specific information for specifying one or more registration messages based on the case that one or more registration messages have been obtained; appending a first registration message specified by the first specific information to the chat storage unit based on a request that includes the first user identification information and the first specific information in the specific information; and appending a second registration message specified by the second specific information to the chat storage unit based on a request that includes the first user identification information and the second specific information in the specific information.

[0009] According to a fourth aspect of the present invention, the program is executed by an information processing device for providing messaging services, wherein the information processing device performs the following processes: storing chat information, including messages sent by a second user to a first user, in a chat storage unit of the information processing device in association with a first user identification information of a first user; outputting specific information for a specific one or more registration messages based on the case that more than one registration message has been obtained; appending a first registration message specified by the first specific information to the chat storage unit based on a request containing the first user identification information and the first specific information in the specific information; and appending a second registration message specified by the second specific information to the chat storage unit based on a request containing the first user identification information and the second specific information in the specific information.

[0010] According to a fifth aspect of the present invention, a terminal performing processing related to a messaging service comprises: a chat storage unit that stores chat information, including messages sent by a second user to the first user, in association with a first user identification information of a user of the terminal, i.e., a first user; and a control unit that performs the following processing: acquiring specific information for specifying one or more registration messages specified by the specific information; appending a first registration message specified by the first specific information to the chat storage unit based on a request carrying the first user identification information and the first specific information in the specific information; and appending a second registration message specified by the second specific information to the chat storage unit based on a request carrying the first user identification information and the second specific information in the specific information.

[0011] According to a sixth aspect of the present invention, a program is used to cause a terminal to perform message service-related processing, wherein the terminal performs the following processing: establishing an association with the terminal's user, i.e., the first user's, first user identification information, and storing chat information, including messages sent by the second user to the first user, in the terminal's chat storage unit; obtaining specific information, which is used to specify one or more registration messages specified by the specific information; appending a first registration message specified by the first specific information to the chat storage unit based on a request carrying the first user identification information and the first specific information in the specific information; and appending a second registration message specified by the second specific information to the chat storage unit based on a request carrying the first user identification information and the second specific information in the specific information. Attached Figure Description

[0012] Figure 1-1 This is a diagram illustrating an example of the system configuration of a communication system according to one implementation scheme.

[0013] Figure 1-2 This diagram illustrates an example of the functions implemented by the control unit of the server in the first embodiment.

[0014] Figure 1-3 This is a diagram illustrating an example of the information stored in the storage unit of the server in the first embodiment.

[0015] Figure 1-4 This is a diagram illustrating an example of user registration data in the first embodiment.

[0016] Figure 1-5 This is a diagram illustrating an example of OA operator registration data in the first embodiment.

[0017] Figure 1-6 This is a diagram illustrating an example of friend management data in the first embodiment.

[0018] Figure 1-7 This is a diagram illustrating an example of the database for managing OA operator registration messages in the first embodiment.

[0019] Figure 1-8 This diagram illustrates an example of the functions implemented by the control unit of the terminal in the first embodiment.

[0020] Figure 1-9 This is a diagram illustrating an example of the information stored in the storage unit of the terminal in the first embodiment.

[0021] Figure 1-10 This is a diagram showing an example of a screen displayed on the display unit of the terminal according to the first embodiment.

[0022] Figure 1-11 This is a diagram showing an example of a screen displayed on the display unit of the terminal according to the first embodiment.

[0023] Figure 1-12 This is a flowchart illustrating an example of the processing flow performed by each device in the first embodiment.

[0024] Figure 1-13 This is a diagram showing an example of the screen displayed on the display unit of the terminal in the first modified example.

[0025] Figure 1-14 This is a flowchart illustrating an example of the processing flow performed by each device in the first variation.

[0026] Figure 1-15 This is a diagram showing an example of the screen displayed on the display unit of the terminal in the first modified example.

[0027] Figure 1-16 This diagram illustrates an example of the functions implemented by the control unit of the terminal in the first embodiment.

[0028] Figure 2 This is a diagram illustrating an example of registration message management data in the second embodiment.

[0029] Figure 3-1 This is a diagram illustrating an example of registration message management data in the third embodiment.

[0030] Figure 3-2 This is a diagram showing an example of a screen displayed on the display unit of the terminal according to the third embodiment.

[0031] Figure 3-3 This is a flowchart illustrating an example of the processing flow performed by each device in the third embodiment.

[0032] Figure 3-4 This is a diagram representing an example of the registration message management data of the third variant.

[0033] Figure 4-1 This is a diagram illustrating an example of the registration message management data in the fourth embodiment.

[0034] Figure 4-2 This is a diagram showing an example of the screen displayed on the display unit of the terminal according to the fourth embodiment.

[0035] Figure 4-3 This is a diagram showing an example of the screen displayed on the display unit of the terminal according to the fourth embodiment.

[0036] Figure 4-4 This is a flowchart illustrating an example of the processing flow performed by each device in the fourth embodiment.

[0037] Figure 5-1 This is a diagram illustrating an example of access history data in the fifth embodiment.

[0038] Figure 5-2This is a diagram illustrating an example of official account statistics from the fifth embodiment.

[0039] Figure 6 This is a diagram illustrating an example of the system configuration of a communication system according to another embodiment. Detailed Implementation

[0040] <Compliance with Legal Matters>

[0041] It should be noted that the disclosure described in this specification is contingent upon compliance with the laws of the implementing country, such as those concerning the secrecy of communications, which are necessary for the implementation of this disclosure.

[0042] An example of an implementation method for a system or the like that implementing this disclosure will be described with reference to the accompanying drawings.

[0043] <System Composition>

[0044] Figure 1-1 is a diagram showing an example of the system configuration of a communication system 1A according to an embodiment of the present disclosure.

[0045] In communication system 1A, server 10, multiple terminals 20 (terminal 20A, terminal 20B, terminal 20C, ...) and multiple OA operator devices 40 (OA operator device 40A, OA operator device 40B, OA operator device 40C, ...) are connected via network 30 without limitation or by way of example.

[0046] Server 10 has the function of providing messaging services via network 30 to terminal 20 (user of terminal 20) and OA operator device 40 (OA operator) without limitation, as an example. Server 10 may also be described as a message server, etc.

[0047] Network 30 serves to connect one or more terminals 20, one or more servers 10, and one or more OA operator devices 40. That is, network 30 means a communication network that provides connection paths in a way that enables data transmission and reception after connecting the aforementioned devices.

[0048] It should be noted that the number of devices connected to network 30 is not limited.

[0049] One or more parts of network 30 may be wired or wireless networks, or not. Network 30 is not limited and, as examples, may include ad hoc networks, intranets, extranets, virtual private networks (VPNs), local area networks (LANs), wireless LANs (WLANs), wide area networks (WANs), wireless WANs (WWANs), metropolitan area networks (MANs), a portion of the Internet, a portion of the Public Switched Telephone Network (PSTN), portable telephone networks, ISDN (integrated service digital networks), wireless LANs, LTE (long-term evolution), CDMA (code division multiple access), Bluetooth (a registered trademark), satellite communications, etc., or combinations of two or more of them. Network 30 may include one or more networks 30.

[0050] Terminal 20 (terminal 20A, terminal 20B, terminal 20C, ...) can be any information processing terminal capable of implementing the functions described in each embodiment. Terminal 20 is not limited; examples include smartphones, mobile phones (feature phones), computers (not limited, examples include desktops, laptops, tablets, etc.), media computer platforms (not limited, examples include cable TVs, satellite set-top boxes, digital video recorders), handheld computer devices (not limited, examples include PDAs (personal digital assistants), email clients, etc.), wearable terminals (glasses devices, watch devices, etc.), or other types of computers and communication platforms. Alternatively, terminal 20 can also be described as an information processing terminal.

[0051] Terminals 20A, 20B, and 20C have essentially the same structure. Alternatively, as needed, the terminal used by user X can be referred to as terminal 20X, and the user information in the prescribed service established with user X or terminal 20X can be referred to as user information X.

[0052] It should be noted that user information refers to the information of a user that corresponds to the user's account within the specified service. User information is not limited and, for example, includes information that corresponds to the user, such as the user's name, user icon, user's age, user's gender, user's address, user's preferences, and user identifiers, either entered by the user or assigned by the specified service. It can also be one or a combination of these information, or it may not be any of them.

[0053] Server 10 can be any device as long as it is an information processing apparatus capable of performing the functions described in each embodiment. Server 10 is not limited; examples include server devices, computers (not limited, examples include desktops, laptops, tablets, etc.), media computer platforms (not limited, examples include cable TVs, satellite set-top boxes, digital video recorders), handheld computer devices (not limited, examples include PDAs, email clients, etc.), or other types of computers and communication platforms. Alternatively, server 10 can also be described as an information processing apparatus. Where there is no need to distinguish between server 10 and terminal 20, server 10 and terminal 20 can be described as information processing apparatuses respectively, or not.

[0054] [Hardware (HW) Configuration of Each Device]

[0055] The HW configuration of each device included in the communication system 1A is described.

[0056] (1) Terminal HW structure

[0057] Figure 1-1 shows an example of the HW configuration of terminal 20.

[0058] Terminal 20 includes a control unit 21 (CPU: central processing unit), a storage unit 28, a communication I / F 22 (interface), an input / output unit 23, and a clock unit 29. The components of the terminal's power control (HW) are not limited, and as an example, they are interconnected via bus B. It should be noted that the HW configuration of terminal 20 does not need to include all components. It is not limited; as an example, terminal 20 may be a structure that removes a single component or multiple components, or it may not be otherwise.

[0059] The communication I / F22 transmits and receives various data via the network 30. Communication can be performed in either wired or wireless form, and any communication protocol can be used as long as communication is possible. The communication I / F22 has the function of communicating with various devices such as the server 10 via the network 30. The communication I / F22 sends various data to various devices such as the server 10 according to instructions from the control unit 21. In addition, the communication I / F22 receives various data sent from various devices such as the server 10 and transmits it to the control unit 21. Sometimes, the communication I / F22 is simply referred to as a communication unit. Furthermore, when the communication I / F22 is composed of physically structured circuits, it is sometimes referred to as a communication circuit.

[0060] The input / output unit 23 includes means for inputting various operations performed on the terminal 20 and means for outputting the processing results processed by the terminal 20. The input / output unit 23 may be an integrated input and output unit, or it may be a separate input and output unit, or neither may be configured otherwise.

[0061] The input unit is implemented by any one or a combination of all kinds of devices capable of accepting input from the user and transmitting the input-related information to the control unit 21. The input unit is not limited, and examples include touch panels, touch displays, physical keys such as keyboards, pointing devices such as mice, cameras (operational input via moving images), microphones (operational input via sound), etc.

[0062] The output unit is implemented by any one or a combination of all kinds of devices capable of outputting the processing results processed by the control unit 21. The output unit is not limited, and examples include touch panels, touch displays, speakers (sound output), lenses (not limited, examples include 3D (three dimensions) output, hologram output), printers, etc.

[0063] As one embodiment, the input / output unit 23 is not limited and, by example, includes a display unit 24, a sound input unit 25, a sound output unit 26, and a camera unit 27.

[0064] Display unit 24 is implemented by any one or a combination of all kinds of devices capable of displaying data written to the frame buffer. Display unit 24 is not limited to any particular type and includes, for example, touch panels, touch displays, monitors (not limited to any particular type, for example, liquid crystal displays, OLEDs), head-mounted displays (HDMs), projection mapping, holograms, and devices capable of displaying images, text information, etc., in air (which may or may not be a vacuum). It should be noted that the aforementioned display unit 24 may or may not be a display unit capable of displaying data in 3D.

[0065] When the input / output unit 23 is a touch panel, the input / output unit 23 and the display unit 24 can also be arranged opposite each other with approximately the same size and shape.

[0066] The sound input unit 25 is used to input sound data (including voice data, hereinafter the same). The sound input unit 25 includes a microphone, etc.

[0067] The sound output unit 26 is used to output sound data. The sound output unit 26 includes a speaker, etc.

[0068] The imaging unit 27 is used to acquire dynamic image data. The imaging unit 27 includes a camera, etc.

[0069] Clock unit 29 is the built-in clock of terminal 20, used to output time information (timing information). Clock unit 29 is not limited; as an example, it may be configured with a clock utilizing a quartz oscillator, etc. Clock unit 29 is not limited; as an example, it is sometimes also described as a timing unit or a time information detection unit.

[0070] It should be noted that the clock unit 29 may or may not have a clock that complies with the NITZ (Network Identity and TimeZone) standard.

[0071] The control unit 21 has a physically structured circuit for performing functions implemented through code or commands contained in the program. This is not limited to a single circuit; for example, it may be implemented using a data processing device built into the hardware. Therefore, the control unit 21 may be described as a control circuit, or it may not be described in this way.

[0072] The control unit 21 is not limited, but includes, for example, a central processing unit (CPU), a microprocessor, a processor core, a multiprocessor, an ASIC (application-specific integrated circuit), or a FPGA (field programmable gate array).

[0073] The storage unit 28 has the functions of storing various programs and data required for the storage terminal 20 to perform its operations. The storage unit 28 is not limited to any particular type, and examples include various storage media such as HDD (hard disk drive), SSD (solid state drive), flash memory, RAM (random access memory), and ROM (read only memory). Alternatively, the storage unit 28 can be described as a memory, but this is not mandatory.

[0074] The terminal 20 stores program P in the storage unit 28 and executes program P, thereby enabling the control unit 21 to perform the processing of each unit included in the control unit 21. That is, program P stored in the storage unit 28 enables the terminal 20 to perform the functions executed by the control unit 21. Alternatively, program P can be described as a program module, but this is not mandatory.

[0075] (2) Server HW structure

[0076] Figure 1-1 shows an example of the HW configuration of server 10.

[0077] Server 10 includes a control unit 11 (CPU), a storage unit 15, a communication I / F 14 (interface), an input / output unit 12, and a clock unit 19. The components of the server 10's power control (HW) are not limited; as an example, they are interconnected via bus B. It should be noted that the server 10's HW does not need to include all components. It is not limited; as an example, the server 10's HW may be configured without the display unit 13, or it may not be.

[0078] The control unit 11 has a physically structured circuit for performing functions implemented by code or commands contained in the program. This is not limited to any particular type of circuit; for example, it may be implemented by a data processing device built into the hardware.

[0079] The control unit 11 is typically a central processing unit (CPU), but it may also be a microprocessor, processor core, multiprocessor, ASIC, FPGA, or something else. In this disclosure, the control unit 11 is not limited to this.

[0080] The storage unit 15 has the function of storing various programs and data required for the operation of the server 10. The storage unit 15 is implemented using various storage media such as HDD, SSD, and flash memory. However, in this disclosure, the storage unit 15 is not limited to these. In addition, the storage unit 15 may be described as a memory, or not.

[0081] The communication I / F14 transmits and receives various data via the network 30. Communication can be performed in either wired or wireless form, and any communication protocol can be used as long as communication is possible. The communication I / F14 has the function of communicating with various devices such as the terminal 20 via the network 30. The communication I / F14 transmits various data to various devices such as the terminal 20 according to instructions from the control unit 11. Furthermore, the communication I / F14 receives various data sent from various devices such as the terminal 20 and transmits it to the control unit 11. Sometimes, the communication I / F14 is simply referred to as a communication unit. Also, when the communication I / F14 is composed of physically structured circuits, it is sometimes referred to as a communication circuit.

[0082] The input / output unit 12 includes means for inputting various operations performed on the server 10 and means for outputting the processing results processed by the server 10. The input / output unit 12 may be configured as an integrated input and output unit, or it may be configured as a separate input and output unit, or it may not be configured in this way.

[0083] The input unit is implemented by any one or a combination of all kinds of devices capable of accepting input from the user and transmitting the input information to the control unit 11. The input unit is typically implemented by a hard key, such as a keyboard, or a pointing device such as a mouse. It should be noted that the input unit is not limited; for example, it may include a touch panel, a camera (operational input via moving images), or a microphone (operational input via sound), or not.

[0084] The output unit is implemented by any one or a combination of all kinds of devices capable of outputting the processing results processed by the control unit 11. The output unit is not limited, and examples include touch panels, touch displays, speakers (sound output), lenses (not limited, examples include 3D (three dimensions) output, hologram output), printers, etc.

[0085] As one implementation, the input / output unit 12 is not limited, and for example, it includes the display unit 13.

[0086] Display unit 13 is typically implemented using a monitor (not limited to, examples include liquid crystal displays and OLEDs). It should be noted that display unit 13 may also be a head-mounted display (HDM) or something else entirely. It should also be noted that the aforementioned display unit 13 may be a display unit capable of displaying data in 3D form, or it may not be. In this disclosure, display unit 13 is not limited to this.

[0087] Clock unit 19 is the built-in clock of server 10, used to output time information (timing information). Clock unit 19 is not limited; as an example, it can be configured with an RTC (Real Time Clock) or a system clock, which are hardware clocks. Clock unit 19 is not limited; as an example, it can also be described as a timing unit or a time information detection unit.

[0088] In this specification, the operator providing the message service (the operator using and managing the server 10) is referred to as the "message service operator," and the information processing device used to provide message services based on message applications (the information processing device that manages information related to the message service) is described as the server 10.

[0089] (3) HW configuration of OA operator's device

[0090] OA operator device 40 is a device used and managed by an operator (hereinafter, appropriately referred to as "OA: Official Account") who has an official account in the messaging service (messaging application). OA operator device 40 is not limited and, as an example, can be implemented through a server, personal computer, terminal (not limited, portable terminal is an example), etc.

[0091] It should be noted that the HW configuration of the OA operator device 40 is omitted because it can be configured in the same way as the server 10 and the terminal 20.

[0092] There are no restrictions on OA operators. For example, they can include operators of various business formats such as convenience stores, supermarkets, fast food restaurants, restaurants, pharmacies, and department stores.

[0093] The OA operator is one example of an operator in this disclosure.

[0094] (4) Other

[0095] The server 10 stores program P in storage unit 15 and executes program P, thereby enabling the control unit 11 to perform the processing of each unit included in the control unit 11. That is, program P stored in storage unit 15 enables the server 10 to perform the various functions executed by the control unit 11. This program P can be described as a program module, or it can be described otherwise.

[0096] The same applies to other devices.

[0097] In various embodiments of this disclosure, it is described that the CPU of terminal 20 and / or server 10 is implemented by executing program P.

[0098] The same applies to other devices.

[0099] It should be noted that the control unit 21 of terminal 20 and / or the control unit 11 of server 10 can implement each process not only through a CPU with control circuitry, but also through logic circuits (hardware) or dedicated circuits formed on integrated circuits (ICs, LSIs) or other similar devices. Furthermore, the aforementioned circuits can be implemented using one or more integrated circuits, or multiple processes shown in each embodiment can be implemented using a single integrated circuit. Additionally, LSIs are sometimes referred to as VLSI, SLSI, ULSI, etc., depending on their level of integration. Therefore, the control unit 21 can be described as a control circuit, but this is not mandatory.

[0100] The same applies to other devices.

[0101] Furthermore, the program P (not limited to, for example, a software program, computer program, or program module) of each embodiment of this disclosure may or may not be provided in a state stored in a storage medium readable by a computer. The storage medium can store the program P in a "non-transitory tangible medium." Additionally, the program P may or may not be used to implement a portion of the functionality of each embodiment of this disclosure. Furthermore, it may be a so-called differential file (differential program) capable of implementing the functionality of each embodiment of this disclosure through combination with the program P already recorded in the storage medium, or it may not be.

[0102] Storage media may include integrated circuits (ICs) on one or more semiconductor substrates (not limited to, examples include field-programmable gate arrays (FPGAs) or application-specific integrated circuits (ASICs), hard disk drives (HDDs), hybrid hard disk drives (HHDs), optical discs, optical disc drives (ODDs), optical disks, optical magnetic drives, floppy disks, floppy disk drives (FDDs), magnetic tapes, solid-state drives (SSDs), RAM drives, SD cards, drives, any other suitable storage media, or two or more suitable combinations thereof. Where appropriate, storage media may be non-volatile, volatile, or a combination of non-volatile and volatile. It should be noted that storage media are not limited to the examples above; they can be any device or medium as long as they are capable of storing a program P. Furthermore, storage media may be described as memory, or not.

[0103] The server 10 and / or terminal 20 can realize the functions of the multiple functional units shown in each embodiment by reading the program P stored in the storage medium and executing the read program P.

[0104] The same applies to other devices.

[0105] Furthermore, the program P disclosed herein can be provided to the server 10 and / or the terminal 20 via any transmission medium capable of transmitting programs (communication network, broadcast wave, etc.), or not. The server 10 and / or the terminal 20 are not limited. As an example, the functions of the multiple functional units shown in each embodiment are implemented by executing the program P downloaded via the Internet or the like.

[0106] The same applies to other devices.

[0107] Furthermore, the various embodiments of this disclosure can also be implemented in the form of data signals transmitted electronically via program P.

[0108] At least a portion of the processing in server 10 and / or terminal 20 can be achieved through cloud computing consisting of more than one computer, or not.

[0109] It can be configured such that at least a portion of the processing in the terminal 20 is performed via the server 10, or it can be configured otherwise. In this case, it can be configured such that at least a portion of the processing of each functional unit of the control unit 21 of the terminal 20 is performed via the server 10, or it can be configured otherwise.

[0110] It can be configured to perform at least a portion of the processing in the server 10 via the terminal 20, or it can be configured otherwise. In this case, it can be configured to perform at least a portion of the processing of each functional unit of the control unit 11 of the server 10 via the terminal 20, or it can be configured otherwise.

[0111] Unless explicitly mentioned, the determination criteria in the embodiments of this disclosure are not mandatory. The prescribed processing action can be performed if the determination criteria are met, or the prescribed processing can be performed if the determination criteria are not met. This is also optional.

[0112] It should be noted that the program disclosed herein is not limited. As an example, scripting languages ​​such as ActionScript and JavaScript (registered trademark), object-oriented programming languages ​​such as Objective-C and Java (registered trademark), and markup languages ​​such as HTML5 are used for installation.

[0113] In addition, the phrase "via communication I / F" is used appropriately in this specification. This means that the device is not limited, and as an example, various information and data are sent and received via communication I / F (via communication unit) based on the control of the control unit (processor, etc.).

[0114] <First Embodiment>

[0115] There exists a technology that, based on a user's action (specification) on specific information (unrestricted, for example, a URL) on terminal 20, performs control corresponding to that specific information (unrestricted, for example, launching a specific application, causing the application to perform specific processing, etc.). However, in this technology, the same processing and control are performed even if the user's purpose and motivation are different, so it is not convenient enough from the perspective of user convenience.

[0116] In the embodiments described below, a messaging service is used as an example to illustrate embodiments of processing and control that are consistent with the user's purpose and motivation.

[0117] The first embodiment is as follows: Based on a request from terminal 20 containing specific information, server 10 appends and updates the message obtained from OA operator device 40 to the chat room between the user's account and the OA operator's account on terminal 20.

[0118] The content described in the first embodiment can also be applied to any of the other embodiments and other variations.

[0119] In the embodiments described below, the messaging service is described as an Instant Messaging Service (IMS) that enables simple message sending and receiving between multiple devices via server 10. Furthermore, the application used to implement this messaging service is referred to as a "messaging application" and appropriately illustrated and described as a "messaging app".

[0120] Messages can include anything beyond simple text, and for example, can include image information (including emoticons, still images, and animated images), operational information (including buttons and icons), specific information / communication information / link information (URLs, URIs), and other types of information that can be sent and received between devices.

[0121] It should be noted that in this specification, the information sent and received through the messaging service is referred to as a "message," but it can also be expressed in a broader sense as "content."

[0122] In addition, in this case, without limitation, as an example, the text message can be distinguished from the various types of information mentioned above (image information, operational information, specific information, etc.) and they can be collectively referred to as "content".

[0123] In addition, in this specification, the user of terminal 20 using the messaging service (messaging application) is referred to as a "regular user" and the account of the regular user is referred to as a "regular account".

[0124] In contrast, the user of the OA operator device 40 that utilizes the messaging service is referred to as the "OA operator," and the OA operator's account is referred to as the "official account."

[0125] In other words, in this specification, the messaging service accounts include regular accounts and official accounts.

[0126] The OA operator device 40, which has an official account, can send and receive messages with other devices via the server 10, just like the terminal 20 with a regular account. Without limitation, as an example, just as with sending messages to other terminals 20, messages sent from a terminal 20 with a regular account to the OA operator device 40 also reach the OA operator device 40 via the server 10. Furthermore, the history of these messages is displayed on the display section of the OA operator device 40 (not shown) in the form of a chat room or similar format.

[0127] Additionally, in the following embodiments, "URL (Uniform ResourceLocator)" will be used as an example of specific information for illustration.

[0128] A URL is a data format used to record the location (address) of information (information resources) existing on networks such as the Internet. It is usually a type of "URI (Uniform Resource Identifier)".

[0129] It should be noted that messaging services (including IMS) can also be considered a form of social networking services (SNS). Therefore, messaging services and social networking services can be distinguished or not. That is, messaging services can be included in social networking services or not.

[0130] <Functional Composition>

[0131] (1) Server

[0132] Figures 1-2 are diagrams illustrating an example of the functions implemented by the control unit 11 of the server 10 in this embodiment.

[0133] The control unit 11 is not limited, and as an example, it may include a registration URL generation unit 111, a chat information management unit 112, a chat information update unit 113, a registration message management unit 114, a registration message specific unit 115, and a friend management unit 116 as functional units.

[0134] The registration URL generation unit 111 is used to obtain messages sent by the OA operator on its official account (OA). In other words, it is used to obtain messages in the chat room between the user's account to be added to terminal 20 and the OA operator's official account. In this case, there are no limitations; for example, the method of obtaining the messages can be receiving messages sent from the OA operator device 40, downloading messages uploaded by the OA operator device 40 in a designated location, etc. Furthermore, the registration URL generation unit 111 generates (assigns) a unique URL for each obtained message.

[0135] The generation of this URL can also be seen as an example of outputting specific information for a specific registration message.

[0136] Chat Information Management Department 112 is used to manage chat information between accounts (including regular accounts and official accounts).

[0137] Chat messages encompass a series of chat content, including messages exchanged between accounts (including one-on-one and group messages), and a history of message exchanges (the history of sent and received messages). Additionally, the imaginary room used to display chat messages as a type of UI (user interface) is called a "chat room."

[0138] In the following description, it will be stated as "appending a message to the chat room," which is essentially the same as adding and updating the chat information of the corresponding account in the chat information management database 156 (chat storage department). Therefore, a chat room can also be considered a type of chat information.

[0139] The chat information update unit 113 updates the chat information stored and managed in the chat information management database 156 based on the official account and registration message specified by the registration message specification unit 115.

[0140] The registration message management department 114 associates the URL generated by the registration URL generation department 111 with the message obtained from the OA operator device 40 according to the official account and stores it in the OA operator registration message management database 155, and manages this information.

[0141] The URLs and messages stored in the OA operator registration message management database 155 are referred to as "registration URLs" and "registration messages," respectively.

[0142] In this embodiment, the registration URL functions as a request from terminal 20 to server 10 to append registration messages associated with that registration URL to the chat room of the user's account and the official account of the OA operator. This request is referred to as the "registration message append request".

[0143] Based on an additional request for a registration message with a registration URL, the registration message specific unit 115 specifically associates the official account and registration message stored in the OA operator registration message management database 155 with the registration URL.

[0144] The Friend Management Department 116 manages the friend relationships between multiple accounts (including regular accounts and official accounts).

[0145] Figures 1-3 are diagrams illustrating an example of the information stored in the storage unit 15 of the server 10 in this embodiment.

[0146] The storage unit 15 is not limited to any particular type, but for example stores a message management processing program 151 executed by the control unit 11 as a message management process, user registration data 152, OA operator registration data 153, friend management data 154, a message management database 155 based on OA operator registration, and a chat information management database 156.

[0147] User registration data 152 is registration data related to terminal 20 using the messaging application or the user of terminal 20, and its data structure is shown in Figures 1-4 for example.

[0148] In user registration data 152, without limitation, as an example, username, application ID, contact information, attribute information and other registration information are stored in an associated manner.

[0149] The username is the name of the user of terminal 20 using the messaging application, and is not limited. For example, it stores the name registered by the user of terminal 20 when using the messaging application.

[0150] The application ID is information or the account itself used to identify the messaging application account corresponding to the username. This application ID is preferably a unique value for each account, but is not limited to any specific value; as an example, it is stored by server 10 with a unique value set for it.

[0151] Without limitation, as an example, the user of terminal 20 can also be called a "regular user". In addition, the application ID registered in user registration data 152 can be called a "regular account" since it is a regular user's account.

[0152] Contact information refers to the contact information of the user with the username. It is not limited to any specific information. For example, it may include the user's phone number (not limited to any specific information, such as a mobile phone number) and email address (not limited to any specific information, such as a mobile email address).

[0153] Attribute information refers to the user's attributes, which are not limited. Examples include gender, age, occupation (job type), etc.

[0154] Other registration information is not limited. For example, it may include authentication information such as passwords used by the user for various authentications in the messaging application (including login password, authentication password, etc.), image data of the icon used by the user (icon image), user profile (user profile), etc.

[0155] OA operator registration data 153 is registration data related to OA operator device 40 or OA operator using messaging applications, and its data structure is shown in Figures 1-5 for example.

[0156] The OA operator registration data 153 is not limited. As an example, the operator's name, application ID, operator contact information, official account name and other registration information are linked and stored.

[0157] The operator name is the name of the OA operator using the messaging application. It is not limited. As an example, it stores the name registered by the OA operator when using the messaging application.

[0158] The application ID is information or the account itself used to identify the messaging application account of the OA operator corresponding to the operator name. This application ID is preferably a unique value for the account, but is not limited to any specific value; for example, server 10 sets a unique value for storage.

[0159] Without limitation, as an example, the user (OA operator) of OA operator device 40 can also be called "official account user (OA user)". In addition, the application ID registered in OA operator registration data 153 can be called "official account" since it is the account of the official account user.

[0160] The operator's contact information is the contact information of the OA operator with that operator name. It is not limited. For example, it includes the OA operator's phone number or email address, the IP address of the OA operator's device 40, the URL of the OA operator's homepage, etc.

[0161] The official account name is the name of the official account that the operator has registered in the messaging application.

[0162] Other registration information is not limited. For example, it may include image data of the icon used by the OA operator of the operator's name (icon image), advertising information, etc.

[0163] It should be noted that in this embodiment, each OA operator is shown with only one official account for illustration and explanation, but it is also possible for each OA operator to register multiple official accounts.

[0164] In addition, in this embodiment, for ease of understanding, user registration data 152 and OA operator registration data 153 are set as different registration data, but they can also be set as one registration data and managed and stored on the server 10 side.

[0165] In addition, in either case where user registration data 152 and OA operator registration data 153 are set as different registration data or one registration data, the information used to distinguish and identify ordinary accounts and official accounts can be linked in advance as an example to the information indicating the type (category) of the account.

[0166] Alternatively, it can be configured to differentiate between ordinary accounts and official accounts by using different ID systems.

[0167] Friend management data 154 is used to manage friend data in messaging applications, and its data structure is shown in Figure 1-6.

[0168] The friend management data is unlimited (154). As an example, the application ID, the friend's application ID, and the friend's username are linked and stored.

[0169] In the context of this manual's messaging application (message service), a friend is a relationship that needs to be registered in order to send and receive messages (including two-way and one-way messages).

[0170] Registering friends can also be seen as linking multiple accounts (application IDs).

[0171] In the example in the diagram, the user with application ID "ac0001" registered "ac0003", "ac0020", "ac030", ... as application IDs of their friends.

[0172] The application ID of “ac0003” is a regular account, and its friend’s username is “Z.Z”.

[0173] The application ID “ac0020” is the official account, and its friend’s username is “Shop A”.

[0174] The application ID “ac0030” is the official account, and its friend’s username is “Shop B”.

[0175] The database 155, which manages the correspondence between registration URLs and registration messages for each OA operator, is a database used to manage the correspondence between registration URLs and registration messages for each OA operator. Its data structure is shown in Figure 1-7.

[0176] The database 155 containing OA operator registration information management data is used as data for OA operators.

[0177] The registration message management data for each OA operator is not limited; for example, it includes the OA operator's application ID and registration message management data.

[0178] Registration message management data is used to manage the registration messages of the official account owned by the OA operator of the application ID. It stores the official account name and, as an example, stores the registration URL, text, and attached image in an associated manner without limitation.

[0179] In this example, the text and attached image stored in association with the registration URL constitute the registration message.

[0180] The text is the registration message in text form that is associated with the registration URL.

[0181] The attached image is a registration message in the form of an image that is associated with the registration URL.

[0182] In this example, the registration message (text, attached image) stores a registration message associated with coupon information (also simply referred to as "coupon") that can be obtained by terminal 20 and used in the OA operator's store. The coupon information is an example of service information related to services provided by the OA operator. It can also be described as an example of information related to discounts.

[0183] In this diagram, at the very front of the database 155 for OA operator registration information management, the OA operator registration information management data for application ID "ac0020" (= Store A) is shown.

[0184] The OA operator registration message management data stores registration message management data, which includes the official account name ("Store A" in this example) and, as an example without limitation, includes registration messages that establish a connection with coupons for products sold by Store A.

[0185] Store A is not limited to any particular type; for example, it could be a convenience store.

[0186] In the first registration URL, text data such as "20% off all sports drinks" is stored in association with image data such as "https: / / coupon1 / img11111xxx.jpg".

[0187] In the second registration URL, text data such as "Please enjoy our newly launched premium roasted coffee at half price." is stored in association with image data such as "https: / / coupon2 / img22222xxx.jpg".

[0188] The control unit 11 of server 10 is not limited; for example, it can display the content of data stored and managed in the OA operator registration message management database 155 on the display unit 13. This display is an example of outputting specific information for a specific registration message. In this way, the message service operator can grasp the correspondence between the registration URL and the registration message.

[0189] Furthermore, the control unit 11 of server 10 is not limited; for example, it can send registration message management data contained in the OA operator registration message management database 155 to the corresponding OA operator's OA operator device 40 via communication I / F 14. This transmission is an example of outputting specific information for a specific registration message. In this way, the OA operator can publish the registration URL associated with its registration message on various SNS, homepages, websites, web pages, news, magazines, advertisements, etc., to inform users.

[0190] A page that can be accessed from terminal 20 and has a registered URL is called a "registered URL publishing page".

[0191] Chat message management database 156 is a database that stores chat information (chat history, etc.) between users who are registered as friends in friend management data 154, including messages between users of each application ID.

[0192] (2) Terminal

[0193] Figures 1-8 are diagrams illustrating an example of the functions implemented by the control unit 21 of the terminal 20 in this embodiment.

[0194] The control unit 21 is not limited; for example, it may include a registration URL acquisition unit 211 as a functional unit.

[0195] The registration URL acquisition unit 211 acquires the registration URL based on the fact that an operation has been performed on the registration URL published on any registration URL publishing page. Furthermore, the registration URL acquisition unit 211 sends an append request with the acquired registration URL to the server 10 via communication I / F 22.

[0196] Figures 1-9 are diagrams showing an example of the information stored in the storage unit 28 of the terminal 20 in this embodiment.

[0197] Storage unit 28 is not limited to storing, but for example, a message processing program 281, user information data 282, and chat information data 286 that are executed by control unit 21 as message processing.

[0198] User information data 282 is data that stores user information related to the user of this terminal 20 in the messaging application, and at least stores the application ID of the user of this terminal 20.

[0199] Chat information data 286 is data that stores chat information (chat history, etc.) between users whose application IDs are registered as friends, including the application IDs of the users of this terminal 20.

[0200] <Display screen>

[0201] Hereinafter, without limitation, we will show, by way of example, the case where the terminal 20 is a smartphone with a display unit 24 having an elongated display.

[0202] In smartphones, without limitation, as an example, a touch panel that functions as an input unit is configured opposite the display, thus forming a touchscreen. When elements such as icons, buttons, items, or input areas are displayed on the display, if the area opposite the area displaying the element, which is part of the touch panel, is operated (touched, clicked) by the user, the program or subroutine associated with that element is executed.

[0203] In the following display example, referring to the example of the official account name "Store A" shown at the front of the OA operator registration message management database 155 (Figure 1-7), the process of adding registration information to the official account is illustrated.

[0204] Additionally, in the following display example, let's assume that the user of terminal 20 is "User X.X" and that User X.X has already registered Store A's official account as a friend in the messaging application.

[0205] Furthermore, the changes in the display screen described below are merely one example of changes in the display screen used to implement the solution of this disclosure. Regarding the changes in the display screen illustrated below, the display of a portion of the display screen may be omitted, or additional display screens may be added.

[0206] Figures 1-10 and 1-11 are diagrams showing an example of the screen displayed on the display unit 24 of the terminal 20 in this embodiment.

[0207] The following state is shown on the left side of Figure 1-10: In the terminal 20 of user X.X, the messaging application is in the running state, and a timeline screen, which is a function of the messaging application, is displayed.

[0208] The messaging app's timeline is not limited, and as an example, it has the ability to share one's recent activities or things one wants others to know between accounts registered as friends, in the form of text and images (including still images and animated images).

[0209] On this timeline screen, information posted by a user who registered as a friend of user X.X is displayed, including descriptive text, registration URL, and banner ad images with links based on the registration URL, indicating that if users register as friends with the official account of "Store A", they can enjoy a service such as "20% off all sports drinks".

[0210] Without limitation, as an example, when a user performs an action (without limitation, as an example, clicking) on ​​the displayed registration URL or banner ad image, an additional request for a registration message associated with the registration URL is sent from terminal 20 to server 10.

[0211] "Click" is not limited to any particular meaning. As an example, it means the user taps the display unit 24 (touch screen) which is integrated with the touch panel with a finger or pen tip, and then leaves the touch.

[0212] In this example, assume terminal 20 is already logged into the messaging application. Also, as mentioned earlier, assume user X has completed registering store A's official account as a friend.

[0213] In this case, without limitation, as an example, a registration message is sent from server 10 to terminal 20, and through redirection, the chat room of the official account of store A, as shown on the right side of Figure 1-10, is displayed via the central screen of Figure 1-10 (without limitation, as an example, a screen used to confirm with the user whether to open the chat room of store A's official account).

[0214] It should be noted that the display of the screen shown in the center of Figure 1-10, which is used to confirm with the user whether to open the chat room of the official account, can also be omitted.

[0215] In the official account's chat room, without limitation, as an example, the top left column displays the logo of Store A and the text "Store A," indicating the current location within the messaging application. Below this, a chat area is constructed for user X.X to chat with Store A in a conversational format. This chat area is configured such that messages from Store A are displayed on the left side of the screen (facing the viewpoint), and messages from user X.X are displayed on the right side (facing the viewpoint).

[0216] In this example, the message for Store A, displayed on the left side of the screen, shows a registration message associated with the first registration URL mentioned above. Specifically, the text displayed is "20% off all sports drinks," and an accompanying image shows a coupon image illustrating the 20% discount on all sports drinks. Below the coupon image is a "Get Coupon" button, which allows users to download and obtain the coupon.

[0217] The provision and distribution of coupons can be handled by server 10. That is, terminal 20 can download coupons from server 10.

[0218] It should be noted that this is not the only option; terminal 20 can also download coupons from OA operator device 40, or it can be done differently.

[0219] On the left side of Figure 1-11, similar to Figure 1-10, the timeline screen displaying the messaging application is shown. Unlike Figure 1-10, this timeline screen displays information such as a description, registration URL, and banner ad image indicating that registering "Store A's" official account as a friend will entitle users to a "50% discount on newly launched premium roasted coffee."

[0220] Without limitation, as an example, when an operation is performed on the displayed registration URL or banner ad image, the terminal 20 sends an additional request to the server 10 for a registration message associated with the registration URL.

[0221] In this case, without limitation, as an example, similar to Figure 1-10, the chat room of the official account of Store A, as shown on the right side of Figure 1-11, is displayed via the central screen of Figure 1-11 (without limitation, as an example, a screen used to confirm with the user whether to open the chat room of Store A's official account).

[0222] The chat room for the official account of store A is the same as the chat room for the official account of store A shown on the right side of Figure 1-10. That is, in this embodiment, since store A has only one official account registered on server 10, the chat room for the official account is also one type.

[0223] Nevertheless, the registration message added to this chat room is different from the registration message added on the right side of Figure 1-10.

[0224] Specifically, in this chat room, the message displayed on the left side of the screen, belonging to Store A, shows a registration message associated with the aforementioned second registration URL. Specifically, the text displayed is "Please try our newly launched premium roast coffee at half price." Additionally, as an attached image, a coupon image illustrating a 50% discount on the premium roast coffee is shown. Below the coupon image is a "Get Coupon" button; by clicking this button, the coupon can be downloaded and obtained.

[0225] It should be noted that the page displaying registration URLs and other information is not limited to the timeline page within the aforementioned messaging application.

[0226] It can also be set to a page within any SNS application that is different from the messaging application, any webpage, website, homepage that can be displayed in a web browser, etc., details of which will be described later.

[0227] That is, the registration URL and other information can be displayed anywhere on the network 30 that the user can view with the terminal 20.

[0228] <Processing>

[0229] Figures 1-12 are flowcharts illustrating an example of the processing flow performed by each device in this embodiment. In these figures, the processing performed by the control unit 21 of the terminal 20 is shown on the left, and the processing performed by the control unit 11 of the server 10 is shown on the right.

[0230] Here, we will use the assumption that the user (ordinary account) in terminal 20 of the messaging application and the OA operator (official account) have registered as friends for explanation.

[0231] It should be noted that this process is merely one example of the process used to implement the solution disclosed herein, and is not limited to this process. Other steps may be added to this process, or some steps may be omitted (deleted).

[0232] This applies to the various flowcharts (processes) described below.

[0233] First, the registration URL acquisition unit 211 of terminal 20 acquires the registration URL according to the user operation performed on input / output unit 23 from any location on network 30, and sends an append request (A110) with the acquired registration URL to server 10 via communication I / F 22.

[0234] Upon receiving the additional request, the control unit 11 of server 10 requests the application ID (in this example, a regular account) from terminal 20 via communication I / F14 (not limited to any specific user identification information) (S110).

[0235] Upon receiving the request, the control unit 21 of terminal 20 sends the application ID (A120) of the user of this terminal 20 to the server 10 via communication I / F 22.

[0236] It should be noted that in this processing example, terminal 20 receives a request for application ID from server 10 (S110) and sends the application ID of the user of terminal 20 to server 10 (A120). However, it can also be configured that terminal 20 sends the application ID of the user of terminal 20 to server 10 in A110.

[0237] In addition, as user identification information, it can also replace the application ID or, in addition to the application ID, send the information required for login authentication of the messaging application (unrestricted, such as email address, password, phone number, etc.) from terminal 20 to server 10.

[0238] When an application ID is received from terminal 20 via communication I / F14, the registration message specifying unit 115 (registration message management unit 114) of server 10 refers to the registration message management database 155 for OA operators stored in storage unit 15 to specify the official account (official account name) corresponding to the registration URL specified by the additional request from terminal 20, and the registration message (text, attached image) stored in association with the registration URL (S120).

[0239] Afterwards, the chat information update unit 113 (chat information management unit 112) of server 10 will set the registration message specified in S120 as a message to be added to the chat room of the official account (hereinafter referred to as "addition target message"). (S130).

[0240] Next, the chat information update unit 113 (or chat information management unit 112) of server 10 will append the append target message set in S130 to the chat room of the official account specified in S120 (S140). Specifically, the append target message will be appended and updated to the chat information between the application ID (ordinary account) of the user of the corresponding terminal 20 and the application ID (official account) of the corresponding OA operator in the chat information management database 156.

[0241] Afterwards, the control unit 11 of server 10 sends the additional content (the registration message added to the chat room) to terminal 20 via communication I / F22 (S150). Then, the control unit 11 of server 10 ends the processing.

[0242] When additional content is received from server 10 via communication I / F22, control unit 21 of terminal 20 displays the chat room of the official account, including the additional registration message, on display unit 24 (A150). Then, control unit 21 of terminal 20 ends processing.

[0243] <Effect>

[0244] The first embodiment is as follows: In a communication system 1A (not limited, but an example of a system that includes at least an information processing device for providing message services), a server 10 (not limited, but an example of an information processing device) includes: a storage unit 15 that stores chat information, including messages sent by an OA operator (not limited, but an example of a second user) to the user of terminal 20, in association with the application ID (not limited, but an example of a first user) of the user of terminal 20; a chat information management database 156 (not limited, but an example of a chat storage unit); and a control unit 11 (not limited, but an example of a control unit).

[0245] Based on the fact that the registration message is obtained from the OA operator device 40, the control unit 11 generates (not limited, but an example of outputting specific information) a registration URL for the specific registration message, displays the registration URL on the display unit 13 (not limited, but an example of outputting specific information), or sends the registration URL to the OA operator device 40 via the communication I / F 14 (not limited, but an example of outputting specific information).

[0246] Furthermore, the control unit 11 appends a first registration message specific to the first registration URL to the chat information management database 156 based on the application ID of the user with terminal 20 and the registration message appending request of the first registration URL, and appends a second registration message specific to the second registration URL to the chat information management database 156 based on the application ID of the user with terminal 20 and the registration message appending request of the second registration URL.

[0247] As an example of the effect obtained through this configuration, the first registration message specified by the first specific information and the second registration message specified by the second specific information can be added to the chat storage unit respectively, thereby improving the user's convenience.

[0248] In addition, the first embodiment shows the following configuration: the chat information management database 156 stores chat information in a manner that is associated with the application ID (not limited, but an example of first user identification information of the first category) as a regular account. The chat information includes messages sent by the OA operator (not limited, but an example of second user) identified according to the application ID (not limited, but an example of second user identification information of the second category) to the user (not limited, but an example of first user) of the terminal 20.

[0249] As an example of the effect achieved through this configuration, messages from a second user to a first user can be stored in the chat storage unit, targeting different categories of user identification information.

[0250] Furthermore, the first embodiment shows that the first registration message specified by the first specific information and the second registration message specified by the second specific information are different messages.

[0251] As an example of the effect achieved through this configuration, different registration messages specific to different information can be added to the chat storage. As a result, different registration messages can be provided to the first user based on the first user's opportunity, purpose, and motivation for accessing the second user's official account, thus improving user convenience.

[0252] <First Variation Example (1)>

[0253] In the first embodiment, it is set that the user (ordinary account) of terminal 20 in the messaging application and the OA operator (official account) have registered as friends, but it is not limited to this.

[0254] There are no restrictions. As an example, it can also be designed so that in the initial state, the user (ordinary account) of terminal 20 and the OA operator (official account) are not registered as friends. Based on the request from terminal 20 to server 10 with the registration URL, the control unit 11 of server 10 registers them as friends. Alternatively, it can be designed differently.

[0255] <Display screen>

[0256] Figure 1-13 is a diagram showing an example of the screen displayed on the display unit 24 of the terminal 20 in this modified example. Here, the screen displayed on the display unit 24 of the terminal 20 of user X.X is shown in the same way as in Figures 1-10 and 1-11.

[0257] Without limitation, as an example, when user X.X operates on the registration URL, etc. in the screen on the left side of Figure 1-10, without limitation, as an example, the friend registration screen shown in the center of Figure 1-13 is displayed on the display unit 24.

[0258] The friend registration screen, without limitation, displays the text "Add Friend" as an example, below which information related to Store A is displayed. Specifically, without limitation, it displays the icon image of Store A, the text "Store A" as the store name, the total number of users (regular accounts) who have registered Store A's official account as friends, and the URL of Store A's homepage.

[0259] Additionally, below this is a "Add Friend" button, which, for example, includes the text "Add Now" to indicate whether or not to add the official account of store A as a friend. When user X.X clicks the "Add Friend" button, server 10 performs friend registration processing to associate the official account of store A with user X.X's account. Then, for example, the screen in the center of Figure 1-10 switches between display modes to finally display the screen on the right side of Figure 1-10.

[0260] It should be noted that, in this case, the display changes are the same as described above when the message related to the coupon for top-roasted coffee, as illustrated in Figure 1-11, is displayed in the chat room of Store A's official account. Therefore, the illustration and explanation are omitted here.

[0261] <Processing>

[0262] Figure 1-14 is a flowchart illustrating an example of the processing flow performed by each device in this modified example. In this figure, the processing performed by the control unit 21 of the terminal 20 is shown on the left, and the processing performed by the control unit 11 of the server 10 is shown on the right.

[0263] It should be noted that steps identical to those in previously shown flowcharts are marked with the same symbol and further explanations are omitted.

[0264] This also applies to the other embodiments and variations.

[0265] After S120, the control unit 11 of server 10 refers to the friend management data 154 stored in storage unit 15 to determine whether the application ID (ordinary account) received from terminal 20 is registered as a friend with the official account specified in S120 (S220). If it is determined that they are registered as friends (S220: yes), the control unit 11 of server 10 will proceed to S130.

[0266] On the other hand, if it is determined that the terminal 20 is not registered as a friend (S220: No), the friend management unit 116 of the server 10 performs friend registration processing on the terminal 20 (S230).

[0267] Specifically, without limitation, as an example, a reminder message is sent to terminal 20 via communication I / F14, causing the official account specified in S120 to be registered as a friend. Furthermore, if terminal 20 receives a message agreeing to register as a friend, without limitation, as an example, the application ID corresponding to the official account specified in S120 is stored in friend management data 154 as the friend's application ID, along with the friend's username (official account name), and associated with the application ID of the user of terminal 20. Then, the control unit 11 of server 10 proceeds to S130.

[0268] The control unit 21 of terminal 20 performs friend registration processing (A230) according to the processing of server 10 described above. Furthermore, the control unit 21 of terminal 20 proceeds the processing to A150.

[0269] It should be noted that, in the above process, the control unit 11 of the server 10 may, as an example, perform the process of confirming with the user of the terminal 20 whether they agree to the terms of use of the official account at any time before or after the friend registration process (S230) or at the same time as the friend registration process, without limitation.

[0270] In this case, the control unit 11 of server 10, without limitation, allows the user of terminal 20 to confirm whether they agree to have their username, user attribute information, etc., notified from server 10 to OA operator device 40 (from message service operator to OA operator). Furthermore, the control unit 11 of server 10 can, upon obtaining confirmation of consent, configure permission to add registration messages to the chat room of the official account.

[0271] <First Variation Example (2)>

[0272] As an example of an application that utilizes an SNS (hereinafter referred to as an "SNS application"), which is different from the messaging application described in the first embodiment.

[0273] In this modified SNS application, the configuration is such that, instead of the "friends" function of the messaging application described in the first embodiment, a function such as "follow" can be used to establish relationships between users of terminal 20, without limitation. This SNS application is not limited; as an example, it is a public form SNS application capable of sending messages (content) that can be viewed by virtually anyone from terminal 20.

[0274] "Following" is not limited to any specific term; as an example, it means linking one user's account with other users' accounts in a social networking application (linking one user with other users). Furthermore, it is not limited to any specific term; as an example, a user who follows you or that user's account is called a "follower."

[0275] In this case, information sent from one user's terminal 20 in an SNS application can be viewed by other users, different from that user, on their own terminals 20.

[0276] Furthermore, without limitation, as an example, if other users are interested in information sent from a user, the other users can follow a user from their own terminals 20 via the SNS application's server (not shown).

[0277] Furthermore, without limitation, as an example, information sent from a user's terminal 20 in an SNS application can be transmitted at any time to the terminal 20 of a user who is a follower via the SNS application's server. In this case, the information transmitted via the SNS application's server is displayed on the timeline screen of the SNS application on the terminal 20 of the follower user.

[0278] <Display screen>

[0279] Figure 1-15 shows an example of the change in the screen of the display unit 24 of the terminal 20 corresponding to Figure 1-10, showing an example of the screen displayed on the display unit 24 of the terminal 20 of user X. X.

[0280] In this example, as shown on the left side of Figure 1-15, the timeline screen of the SNS application displays information posted by users followed by user X.X, including: "If you register as a friend of the official account of 'Shop A' in the messaging application, you can enjoy a service such as '20% off all sports drinks'", as well as the registration URL and banner ad image.

[0281] Furthermore, when the registration URL or banner ad image is accessed, a login screen as shown in the center of Figure 1-15 is displayed on user X's terminal 20, without limitation, as an example, for logging into the messaging application.

[0282] It should be noted that this is just one example. Considering security issues, it is designed as follows: In order to authenticate whether a user is a legitimate user of the messaging service on the server 10 side, the web browser on the terminal 20 is used to open and display the login screen of the web version of the messaging application.

[0283] The login screen displays, for example only, an input field for entering user registration information (email address, password, phone number, etc.). When the user enters the registration information and clicks the login button, server 10 performs login authentication. Furthermore, if the login authentication result is "passed" and the user successfully logs into the messaging application, terminal 20 sends an append request to server 10 to establish an association with the aforementioned registration URL.

[0284] Then, without limitation, as an example, via the screen on the right side of Figure 1-15 (without limitation, as an example, the screen used to confirm whether to open the chat room of the official account of store A using the messaging application installed on terminal 20), the same chat room as the right side of Figure 1-10 above is displayed.

[0285] It should be noted that, in this case, the display changes are the same as described above when the message related to the coupon for top-roasted coffee, as illustrated in Figure 1-11, is displayed in the chat room of Store A's official account. Therefore, the illustration and explanation are omitted here.

[0286] <First Variation Example (3)>

[0287] As illustrated in Figures 1-9, not only does the server 10 store the information, but the terminal 20 also stores the history of its own chat information in the chat information data 286 of the storage unit 28.

[0288] Therefore, the control unit 21 of the terminal 20 can execute a portion of the processing performed by the server 10 in the above embodiment.

[0289] Figure 1-16 is a diagram illustrating an example of the function implemented by the control unit 21 of the terminal 20 in this modified example.

[0290] Control unit 21 is not limited to having a chat information update unit 213 instead of registration URL acquisition unit 211, as an example.

[0291] In this case, without limitation, in the process A110 of Figure 1-12, the control unit 21 of the terminal 20 sends a request to the server 10 via communication I / F 22 to obtain the official account and registration message obtained from the registration URL publishing page, etc.

[0292] Upon receiving the request, the control unit 11 of server 10 sends the official account and registration message specified in S120 to terminal 20 via communication I / F14.

[0293] When the official account and registration message are received from the server 10 via communication I / F22, the chat information update unit 213 of the terminal 20 appends the received registration message to the chat information stored in the chat information data 286 (Figure 1-9) of the storage unit 28, and updates the chat information of the user of the terminal 20 with the received official account.

[0294] It should be noted that, alternatively, the control unit 21 of the terminal 20 may establish a registration message associated with the obtained registration URL, append the specified registration message, and update it.

[0295] Specifically, without limitation, in the process A110 of Figure 1-12, the control unit 21 of terminal 20 sends a request to server 10 via communication I / F 22 to obtain OA operator registration message management data or official account registration message management data associated with the OA operator that was obtained from the registration URL publishing page, etc.

[0296] Upon receiving the request, the control unit 11 of server 10 sends the corresponding OA operator registration message management data or the corresponding official account registration message management data stored in the OA operator registration message management database 155 to terminal 20 via communication I / F 14.

[0297] When the aforementioned data is received from server 10 via communication I / F22, control unit 21 of terminal 20 establishes a registration message associated with the registration URL based on the received data. Furthermore, chat information update unit 213 of terminal 20 appends the received registration message to the chat information stored in chat information data 286 (Figures 1-9) of storage unit 28, updating the chat information between the user's ordinary account and the received official account of terminal 20.

[0298] It should be noted that this also applies to the embodiments described later.

[0299] In this modified example, terminal 20 includes: a storage unit 28 that stores chat information, including messages sent by an OA operator (a second user) to a user of terminal 20, in a manner associated with a user (not limited to a first user)'s ordinary account (not limited to a first user's identification information); chat information data 286 (not limited to a chat storage unit); and a control unit 21 (not limited to a control unit).

[0300] The control unit 21 (registration URL acquisition unit 211) acquires the registration URL for one or more registration messages specified by the registration URL (not limited, for example, specific information).

[0301] Furthermore, based on the request of the application ID (not limited, for example, the first user identification information) and the first registration URL (not limited, for example, the first specific information) of the user of this terminal 20, the control unit 21 (chat information update unit 213) appends the first registration message specific to the first registration URL to the chat information data 286, and based on the request of the application ID and the second registration URL (not limited, for example, the second specific information) of the user of this terminal 20, appends the second registration message specific to the second registration URL to the chat information data 286.

[0302] As an example of the effect achieved through this configuration, the first registration message specified by the first specific information and the second registration message specified by the second specific information can be easily appended to the chat storage unit on the terminal side. Furthermore, a portion of the server's processing can be omitted, thus reducing the server's processing load.

[0303] <First Variation Example (4)>

[0304] In the first embodiment, a registration message associated with coupon information, which is an example of service information, is illustrated. The service information is related to services provided by the OA operator, but is not limited to this. It is not limited to coupon information; information related to certain services provided by the OA operator can be associated with the registration message. That is, the information that can be associated with the registration message is not limited to coupon information.

[0305] Furthermore, the registration message does not necessarily need to be associated with service information. Specifically, there are no restrictions. For example, messages used to promote, advertise, or conduct public relations for the OA operator or the services provided by the OA operator, as well as notices sent regularly by the OA operator, can also be registered as registration messages.

[0306] It should be noted that the above-mentioned different types (categories) of registration messages can be distinguished and identified by means of pre-establishing an association between the information representing the type (category) of the message, without limitation, as an example.

[0307] <First Variation Example (5)>

[0308] In the first embodiment, the first registration message specified by the first specific information and the second registration message specified by the second specific information are set as different messages, but it is not limited to this.

[0309] Specifically, the first registration message specified by the first specific information and the second registration message specified by the second specific information can be set to be the same message.

[0310] <Second Embodiment>

[0311] The second embodiment is an example of associating multiple (two or more) registration messages with a registration URL.

[0312] The content described in the second embodiment can be applied to any of the other embodiments and other variations.

[0313] In addition, for constituent elements that are the same as those that have appeared before, the same symbol is used and further explanation is omitted.

[0314] Figure 2 This is a diagram illustrating an example of registration message management data in this embodiment.

[0315] Here, an example is shown of the registration message management data contained in the OA operator registration message management data for the OA operator (= Store A) with application ID "ac0020" shown at the front of the OA operator registration message management database 155 in Figure 1-7.

[0316] In this registration message management data, two registration messages (text and attached image) are stored and associated with the first registration URL and the second registration URL, respectively. The first registration message stored and associated with the first registration URL and the second registration URL is the same registration message as shown in Figure 1-7.

[0317] On the other hand, a common message (the same message) is stored and associated with both the first and second registration URLs as the second registration message.

[0318] Specifically, common text data such as "able to conduct electronic currency settlement" is stored in association with both the first and second registration URLs as the text of the second registration message, and common image data is also stored as an additional image.

[0319] In this case, the control unit 11 of server 10 is not limited. As an example, in S130 of Figure 1-12 or Figure 1-14, the two registration messages associated with the registration URL are set as append object messages.

[0320] It should be noted that you can also choose not to set all the multiple registration messages associated with the registration URL as append object messages, but only set a portion of the registration messages as append object messages. This is also acceptable.

[0321] Additionally, this example illustrates a scenario where multiple registration messages associated with different registration URLs share some common information, but it is also possible to make all registration messages different for each registration URL.

[0322] Alternatively, the number of registration messages can be different for each registration URL.

[0323] <Effect>

[0324] The second embodiment shows the following configuration: the control unit 11 of the server 10 adds multiple registration messages (not limited, for example, multiple first registration messages) specified by the first registration URL (not limited, for example, first specific information) to the chat storage unit. In addition, the control unit 11 of the server 10 adds multiple registration messages (not limited, for example, multiple second registration messages) specified by the second registration URL (not limited, for example, second specific information) to the chat storage unit.

[0325] As an example of the effect obtained through this configuration, multiple first registration messages specified by first specific information and multiple second registration messages specified by second specific information can be added to the chat storage unit respectively, thereby improving the convenience for users utilizing the messaging service.

[0326] In addition, the second embodiment shows the following configuration: multiple registration messages (not limited, an example of multiple first registration messages) specified by a first registration URL (not limited, an example of multiple specific information) and multiple registration messages (not limited, an example of multiple second registration messages) specified by a second registration URL (not limited, an example of second specific information) are a part of common messages.

[0327] As an example of the effect achieved through this configuration, since multiple first registration messages and multiple second registration messages are partially common messages, the user can be notified of common content even when specific information differs, thereby improving user convenience.

[0328] <Third Embodiment>

[0329] The third embodiment, like the second embodiment, is an embodiment that associates multiple (two or more) registration messages with a registration URL.

[0330] The difference from the second embodiment is that, in the third embodiment, based on conditions, an additional object message is selectively set from among multiple registration messages associated with the registration URL.

[0331] The content described in the third embodiment can be applied to any of the other embodiments and other variations.

[0332] In addition, for constituent elements that are the same as those that have appeared before, the same symbol is used and further explanation is omitted.

[0333] <Data Composition>

[0334] Figure 3-1 is a diagram illustrating an example of registration message management data in the second embodiment.

[0335] Here, an example is shown of the registration message management data contained in the OA operator registration message management data for the OA operator (= Store A) with application ID "ac0020" shown at the front of the OA operator registration message management database 155 in Figure 1-7.

[0336] The registration message management data contains registration messages that are linked to coupon information for products sold by store A, similar to those in Figures 1-7, but the data structure and content are different in some aspects.

[0337] Specifically, in this registration message management data, without limitation, as an example, the registration URL, conditions, text, attached image, maximum number of downloads, and number of downloads are stored in an associated manner.

[0338] The condition is used to set the registration message associated with the registration URL as an append object message.

[0339] The download limit is a set number of times that the terminal 20 can download the coupon associated with the registration message (text, attached image), or a pre-defined number of times. This download limit is not limited; for example, it can be set by the server 10 or the OA operator device 40.

[0340] The download count is the number of times the coupon associated with the registration message (text, attached image) has actually been downloaded by terminal 20. This download count is incremented by "1" and updated each time a coupon is downloaded.

[0341] In the example shown in the diagram, the registration message for the first registered URL does not set a download limit but is instead set to "- (None)". Along with this, the condition is also set to "- (None)". Additionally, the total number of downloads is stored in the download count.

[0342] It should be noted that in this example, the download count is also counted for registration messages that do not have a set download limit, but it is also possible not to count the download count.

[0343] In contrast, a download limit of "1000" was set for the registration message of the second registration URL. Along with this, as conditions, "download limit not reached" and "download limit reached" were specified.

[0344] "Download limit not reached" means that the number of downloads is below the download limit (number of downloads ≤ download limit).

[0345] Furthermore, the corresponding text specifies "Please enjoy our newly launched premium roasted coffee at half price. ※A coupon is available for the first 1000 customers only," and similarly specifies the image data for the attached image.

[0346] In contrast, "reaching the download limit" means that the number of downloads has exceeded the download limit (number of downloads > number of downloads).

[0347] Furthermore, the corresponding text specifies, "The participation of the first 1000 guests has been completed, therefore this event has ended. Please wait for the next event." The text data also specifies the image data for the attached image.

[0348] Thus, in the example above, before the download limit is reached (download count ≤ download limit), the registration message for the period before the download limit is reached is appended to the official account's chat room. After the download limit is reached (download count > download limit), the registration message for the period when the download limit is reached is appended to the official account's chat room.

[0349] It should be noted that in Figure 3-1, columns such as "Conditions" and "Download Limit" are set for ease of understanding, but the settings of these columns are not limited. As an example, they can also be implemented through a program instead of being managed as data.

[0350] In addition, the download limit can be associated with different values ​​by official account and / or by registered URL, or it can be associated with the same value.

[0351] <Display screen>

[0352] Figure 3-2 shows an example of a screen displayed on the display unit 24 of the terminal 20 in this embodiment, showing an example of the chat room of the official account of the aforementioned store A.

[0353] This chat room is the chat room of the official account corresponding to Figure 1-11, but the additional registration messages are different.

[0354] Figure 3-2(a) shows an example of a chat room displayed during the period before the download limit for coupons is reached. Specifically, it shows the following state: as a message from Store A displayed on the left side of the screen, the text corresponding to the text in the registration message associated with the second registration URL in Figure 3-1 when the download limit has not been reached is appended.

[0355] Specifically, the text displayed reads, "Please enjoy our newly launched premium roast coffee at half price. ※A coupon is available for the first 1000 customers only." An additional image shows a coupon illustration illustrating the 50% discount on the premium roast coffee and the limited availability for the first 1000 customers. Furthermore, since the promotion is still ongoing, a "Get Coupon" button is displayed below the coupon image. By clicking this button, you can download and obtain the coupon.

[0356] Figure 3-2(b) shows an example of a chat room that appears after the number of downloads for a coupon has reached the download limit. Specifically, the following state is shown: as a message from Store A displayed on the left side of the screen, the content corresponding to the text in the registration message associated with the second registration URL in Figure 3-1 when the download limit was reached is appended.

[0357] Specifically, the text displayed reads, "The first 1000 guests have participated, therefore this event has ended. Please wait for the next event." Additionally, as an accompanying image, an image containing the text "Sold Out" is overlaid on top of the aforementioned coupon image.

[0358] In addition, since the event has ended, unlike Figure 3-2(a), the coupon acquisition button is not displayed in Figure 3-2(b), so it is impossible to obtain the coupon.

[0359] <Processing>

[0360] Figure 3-3 is a flowchart illustrating an example of the processing flow performed by each device in this embodiment. In this figure, the processing performed by the control unit 21 of the terminal 20 is shown on the left, and the processing performed by the control unit 11 of the server 10 is shown on the right.

[0361] Here, we will use the assumption that the user (ordinary account) in terminal 20 of the messaging application and the OA operator (official account) have registered as friends for explanation.

[0362] After S110, when the application ID is received from the terminal 20 via communication I / F14, the registration message specifying unit 115 (registration message management unit 114) of the server 10 refers to the registration message management database 155 for OA operators stored in the storage unit 15 to specify the official account (official account name) corresponding to the registration URL specified by the additional request from the terminal 20 (S320).

[0363] Then, the registration message specific unit 115 (registration message management unit 114) of server 10 refers to the OA operator registration message management database 155 stored in storage unit 15 to determine whether a download limit is set in association with the above-mentioned registration URL (S330).

[0364] If it is determined that no download limit has been set (S330: No), the control unit 11 of server 10 sets the registration message stored in association with the aforementioned registration URL as an append object message (S340). Then, the control unit 11 of server 10 proceeds to S140.

[0365] On the other hand, if it is determined that there is a maximum number of downloads set (S330: Yes), the control unit 11 of the server 10 sets an append object message based on whether the condition of establishing an association with the above-mentioned registered URL is met (S350).

[0366] Specifically, if the download limit is not reached, the registration message for the period when the download limit is not reached, which is stored in association with the aforementioned registration URL, will be set as an append object message.

[0367] In contrast, when the download limit is reached, the registration message associated with the aforementioned registration URL when the download limit is reached is set as an append object message.

[0368] Furthermore, the control unit 11 of server 10 will proceed the processing to S140.

[0369] <Effect>

[0370] The third embodiment shows the following configuration: the control unit 11 of the server 10 appends any one of the multiple registration messages (not limited, an example of multiple first registration messages) specified by the first registration URL (not limited, an example of first specific information) to the chat storage unit. In addition, the control unit 11 of the server 10 appends any one of the multiple registration messages (not limited, an example of multiple second registration messages) specified by the second registration URL (not limited, an example of second specific information) to the chat storage unit.

[0371] As an example of the effect obtained through this configuration, any one of the multiple first registered messages specified by the first specific information can be added to the chat storage unit, thereby improving the convenience for users utilizing the messaging service.

[0372] Similarly, any one of the multiple second registration messages specified by the second specific information can be appended to the chat storage, thereby improving the convenience for users utilizing the messaging service.

[0373] In addition, the third embodiment shows that the control unit 11 of the server 10 determines the composition of the registration message to be added to the chat storage unit based on conditions.

[0374] As one example of the effect achieved through this configuration, it allows for flexible decision-making regarding which registered messages to add to the chat storage, and also improves the versatility of the messaging service.

[0375] Furthermore, the third embodiment shows the following configuration: coupon information (not limited, but an example of service information related to a service provided by a second user) is associated with the registration message, and the control unit 11 of the server 10 determines the registration message to be added to the chat storage unit based on conditions related to the number of times the coupon information is downloaded (not limited, but an example of conditions related to the number of times the service information associated with the registration message is obtained based on the registration message being added to the chat storage unit).

[0376] As an example of the effect achieved through this configuration, it is possible to flexibly and appropriately decide which registration messages to add to the chat storage based on conditions related to the number of times service information is obtained, wherein the service information is information related to the service provided by the second user.

[0377] <Third variation example (1)>

[0378] In connection with the description in the second embodiment, in the third embodiment, it is also possible, without limitation, to allow multiple registration messages associated with different registration URLs to share some of their messages, and to selectively set an additional object message from the multiple registration messages associated with the registration URL based on conditions.

[0379] Figure 3-4 is a diagram illustrating an example of registration message management data in this variant.

[0380] Here, an example is shown of the registration message management data contained in the OA operator registration message management data for the OA operator (= Store A) with application ID "ac0020" shown at the front of the OA operator registration message management database 155 in Figure 1-7.

[0381] In the registration message management data, conditions and download limits are set for the first and second registration URLs, respectively.

[0382] For the first and second registration URLs, the registration messages associated with the condition "download limit not reached" are the same as those in Figure 3-1.

[0383] On the other hand, for the first and second registration URLs, the same message (common message) is stored as an association with the registration message associated with the condition "download limit reached". Specifically, the text of the registration message associated with the condition "download limit reached" specifies "This activity has ended. Please wait for the next activity." This common text data also specifies common image data as an additional image.

[0384] This variation illustrates a common message structure in which multiple registration messages (unlimited, an example of multiple first registration messages) specific to a first registration URL and multiple registration messages (unlimited, an example of multiple second registration messages) specific to a second registration URL are part of a common message.

[0385] As an example of the effect achieved through this configuration, since multiple first registration messages and multiple second registration messages are partially common messages, the user can be notified of common content even when specific information differs, thereby improving user convenience.

[0386] Furthermore, according to this variation, since one of the registration messages corresponding to whether a condition is true or false is a unique message but the other registration message is a common message, it is possible to notify the user of the unique content and the common content separately based on whether the condition is true or false, thereby improving user convenience.

[0387] <Third Variation Example (2)>

[0388] In the third embodiment, different registration messages are appended to the chat room of the official account based on the number of times the coupon is downloaded by the terminal 20, but it is not limited to this.

[0389] Specifically, regardless of whether coupons or other downloads exist, and without limitation, as an example, different registration messages can be appended to the official account's chat room based on the number of append requests (or "access counts") made from terminal 20 to server 10 with the registration URL. This is not mandatory.

[0390] Alternatively, instead of the number of times coupons are downloaded or the number of times server 10 is accessed, different registration messages can be added to the official account's chat room based on the frequency of coupons being downloaded or the frequency of accessing server 10 within a pre-set unit period (unlimited, for example, a week or a month). This is also acceptable.

[0391] In addition, in these cases, as long as the number and frequency of visits can be counted, the registration information does not necessarily need to be related to coupons.

[0392] As an example of the effect obtained through this variation, it is possible to flexibly and appropriately determine the registration messages to be added to the chat storage based on conditions related to the number or frequency of requests with specific information.

[0393] <Third variation example (3)>

[0394] Alternatively, the user's attribute information from terminal 20 can be used to add different registration messages to the official account's chat room, or this method can be used in addition to the above.

[0395] Specifically, without limitation, as an example, it can be designed as follows: the registration message is predefined according to the user's attribute information such as gender, age, occupation (job type), and based on the case that the terminal 20 receives an append request for a registration message with a registration URL, the control unit 11 of the server 10 specifies the user's attribute information of the terminal 20, and the control unit 11 of the server 10 appends the registration message corresponding to the specified attribute information to the chat room of the official account, or it can be done differently.

[0396] As an example of the effect obtained by this variation, it is possible to flexibly and appropriately determine the registration message to be added to the chat storage unit based on the number of times the service information is acquired or conditions related to the frequency of acquisition of the service information in addition to the number of times, wherein the aforementioned service information is information related to the service provided by the second user.

[0397] Furthermore, as an example of the effect obtained through this variation, it is possible to flexibly and appropriately determine the registration message to be added to the chat storage based on the attribute information of the first user.

[0398] <Fourth Embodiment>

[0399] The fourth embodiment is an embodiment that determines (sets) the append object message based on the history of page changes on the terminal 20.

[0400] The content described in the fourth embodiment can be applied to any of the other embodiments and other variations.

[0401] In addition, for constituent elements that are the same as those that have appeared before, the same symbol is used and further explanation is omitted.

[0402] Figure 4-1 is a diagram illustrating an example of registration message management data in the fourth embodiment.

[0403] Here, an example is shown of the registration message management data contained in the OA operator registration message management data for the OA operator (= Store A) with application ID "ac0020" shown at the front of the OA operator registration message management database 155 in Figure 1-7.

[0404] In this registration message management data, without limitation, as an example, the registration URL, inflow path identification URL, text, and attached image are stored in an associated manner.

[0405] The registration URL is a URL equivalent to the registration URL described in the previous embodiment, and is generated by the registration URL generation unit 111 based on the situation of obtaining a message from the OA operator device 40.

[0406] The inflow path identification URL is a URL used to identify the inflow path of the terminal 20 to the loading page. It is generated by the registration URL generation unit 111 based on the registration URL and the inflow path of the terminal 20 to the loading page.

[0407] The inflow path indicates which page terminal 20 was inbounded from to the loading page; that is, it indicates the page from which the link source was used when terminal 20 was inbounded to the loading page. It can also be described as a history of page changes.

[0408] In the accompanying diagram, for convenience, the inflow path identification URL is illustrated by appending " / &{URL of the inflow source page (https~)}" to the registered URL.

[0409] In addition, for convenience, the default inflow path identification URL is illustrated by appending " / &{default}" to the registered URL.

[0410] The aforementioned registration URL and inflow path identification URL are examples of specific information in this disclosure.

[0411] In this embodiment, the page that changes due to the operation of the advertisement on the page where an advertisement related to the OA operator (an advertisement related to the services provided by the OA operator) is published (hereinafter referred to as the "advertisement publishing page") is called the "loading page". Furthermore, the URL of the advertisement publishing page is called the "advertisement publishing URL", and the URL of the loading page is called the "loading URL". The loading page in this embodiment is equivalent to the registration URL publishing page in the aforementioned embodiment.

[0412] Let's take the first registration URL as an example to illustrate.

[0413] The first inflow path identified is the URL when the inflow path is a sports-related page. Furthermore, text such as "20% off all sports drinks" and its corresponding attached image are stored as the first registration message, and text such as "Answer the questionnaire and go to the Tokyo Olympics!..." and its corresponding attached image are stored as the second registration message. The intention is to add registration messages related to sports drink coupons and other sports-related registration messages as supplementary registration messages since the inflow path is a sports-related page.

[0414] The second inflow path identified is the URL when the inflow path is a food-related page. Furthermore, the text "Please try our newly launched premium roast coffee at half price" along with its corresponding image is stored as the first registration message, and the text "Answer the questionnaire and receive an invitation to a hotel dinner!..." along with its corresponding image is stored as the second registration message. The intention is to add a registration message related to the premium roast coffee coupon, and other food-related registration messages as supplementary registration messages, since the inflow path is a food-related page.

[0415] The third inflow path identification URL is the default inflow path identification URL. This is for pages where there is no inflow source.

[0416] There are no restrictions on the case where there is no source page. For example, a page is loaded in terminal 20, bookmarked, and added to the bookmarks.

[0417] The "favorites" feature is one of the functions of Terminal 20, which means the ability to register the URL of any website into a web browser.

[0418] This function allows the completed registration loading page to be displayed directly on terminal 20 without showing the advertisement publishing page. In this case, there is no page from the inflow source.

[0419] In this example, the text "Thank you for adding this to your favorites." along with its corresponding image is stored as the first registration message; the text "All sports drinks are 20% off" along with its corresponding image is stored as the second registration message; and the text "Please try our newly launched premium roast coffee at half price" along with its corresponding image is stored as the third registration message. The intention is to add the "Thank you for adding this to your favorites" registration message because there is a possibility that the loaded page will be added to the favorites list, and because there is no source page (or rather, the inflow path cannot be identified), registration messages related to sports drink coupons and premium roast coffee coupons are added.

[0420] <Display screen>

[0421] Figures 4-2 and 4-3 are illustrations showing an example of the changes in the display screen displayed on the display unit 24 of the terminal 20 in this embodiment.

[0422] Figure 4-2 shows the status of the portal website displayed on the display unit 24 of the terminal 20. The portal website includes multiple categories such as "General", "News", "Sports", "Society" and "Entertainment". In this example, the "Sports" category is selected and a page with sports-related information is displayed.

[0423] In addition to sports-related information, this page also displays, as an example, advertisements related to services provided by OA operators, without limitation.

[0424] Specifically, in this example, an advertisement is displayed indicating that a beverage extravaganza is being held at store A. That is, this page is an advertising page.

[0425] When a user on terminal 20 interacts with the aforementioned advertisement, the page changes from the advertisement display page to the loading page. In this example, the loading page is the webpage of store A. It displays text indicating that "by adding store A's official account as a friend in the messaging app, you can receive a beverage coupon," an advertisement indicating that store A is hosting a beverage extravaganza, and an "Participate in the Event" button for obtaining the coupon.

[0426] When the "Participate in Event" button is pressed on the loading page, similar to the previous embodiment, the chat room of the official account of Store A, which is already installed in the messaging application on terminal 20, is displayed after logging into the messaging application and registering as a friend without adding Store A's official account as a friend.

[0427] In this example, the page displaying the advertisement before the page loads is a sports-related page. Therefore, the chat room displays registration messages related to sports drink coupons.

[0428] Furthermore, within this chat room, registration messages originating from Store A's official account displayed registration messages related to participating in a questionnaire to obtain tickets to the Tokyo Olympics. In other words, since the advertising page prior to the loading page was a sports-related page, in addition to displaying registration messages related to sports drink coupons, different sports-related registration messages were also displayed.

[0429] Figure 4-3 shows the status of a food website being displayed on the display unit 24 of the terminal 20.

[0430] This food website, in addition to food-related information, also displays, as an example without limitation, advertisements from OA (Office Automation) operators with official accounts on messaging applications. Specifically, in this example, similar to Figure 4-2, an advertisement is displayed indicating a beverage extravaganza is being held at store A. That is, this page is an advertising page.

[0431] When a user on terminal 20 interacts with the advertisement, the page changes from the food website to the loading page. In this example, the loading page is the same as the one shown in Figure 4-2.

[0432] When the "Participate in Event" button is pressed on the loading page, similar to the previous embodiment, the chat room of the official account of Store A, which is already installed in the messaging application on terminal 20, is displayed after logging into the messaging application and registering as a friend without adding Store A's official account as a friend.

[0433] In this example, the page that was previously displaying ads before the page loaded was a food-related page. Therefore, the chat room now displays registration messages related to coupons for top-roasted coffee.

[0434] Furthermore, within this chat room, registration messages originating from Store A's official account displayed registration messages related to participating in a survey to obtain an invitation voucher for a hotel dinner. That is, since the advertising page prior to the loading page was a food-related page, in addition to registration messages related to coupons for top-roasted coffee, different food-related registration messages were also displayed.

[0435] <Processing>

[0436] Figure 4-4 is a flowchart illustrating an example of the processing flow performed by each device in this embodiment. In this figure, the processing performed by the control unit 21 of the terminal 20 is shown on the left, and the processing performed by the control unit 11 of the server 10 is shown on the right.

[0437] Here, we will use the assumption that the user (ordinary account) in terminal 20 of the messaging application and the OA operator (official account) have registered as friends for explanation.

[0438] Initially, the control unit 21 of terminal 20 selects an advertisement to be published on the advertisement publishing page according to the user's operation on the input / output unit 23 (A101). Afterwards, the control unit 21 of terminal 20 sends the advertisement publishing URL of the selected advertisement publishing page to server 10 via communication I / F 22 (A103).

[0439] Accordingly, the control unit 11 of the server 10, based on the advertisement publishing URL received from the terminal 20, establishes a registration URL associated with the advertisement published on the advertisement publishing page specified by the advertisement publishing URL. Furthermore, the registration URL generation unit 111 of the server 10 generates an inflow path identification URL by appending the advertisement publishing URL to the specified registration URL, and sends the generated inflow path identification URL and loading URL to the terminal 20 via communication I / F14 (S103).

[0440] The control unit 21 of the terminal 20 displays the loading page on the display unit 24 (A105) based on the loading URL received from the server 10.

[0441] On the loading page, there are no restrictions; for example, this includes objects associated with the advertisement selected in A101. Any object that can be interacted with by the user is acceptable; there are no restrictions, and examples include buttons, icons, etc.

[0442] An example of this object is the activity participation button in Figures 4-2 and 4-3.

[0443] Then, the control unit 21 of the terminal 20 associates the incoming path identification URL received from the server 10 with the objects in the loading page mentioned above (A107).

[0444] The default inflow path identification URL is associated with the object without limitation, but as an example. In A107, the default inflow path identification URL associated with the object is overridden and updated using the inflow path identification URL received from server 10.

[0445] Subsequently, when the user operates the object via the input / output unit 23, the control unit 21 of the terminal 20 sends the inflow path identification URL associated with the operated object to the server 10 via the communication I / F 22 (A109).

[0446] When the incoming path identification URL is received from the terminal 20 via communication I / F14, the control unit 11 of the server 10 performs the processing of S110.

[0447] In addition, the control unit 21 of terminal 20 executes the processing of A120. Furthermore, the control unit 21 of terminal 20 proceeds the processing to A150.

[0448] When the application ID is received from the terminal 20 via communication I / F14, the registration message identification unit 115 (registration message management unit 114) of the server 10 refers to the OA operator registration message management database 155 stored in the storage unit 15 to identify the official account corresponding to the inflow path identification URL received from the terminal 20 (S420).

[0449] Then, the control unit 11 of the server 10 determines whether the inflow path identification URL received from the terminal 20 contains the advertisement publishing URL (S430).

[0450] Here, when the process reaches S430 via the processing of A101 to A107 of terminal 20 and the processing of S103 of server 10 respectively, the inflow path identification URL received from terminal 20 includes the advertisement publishing URL.

[0451] On the other hand, as mentioned earlier, if the terminal 20 has saved the loading page URL, processing in the terminal 20 starts from A105, and processing in A107 is skipped. As a result, the inflow path identification URL sent from the terminal 20 to the server 10 in A109 becomes the default inflow path identification URL, and therefore the ad posting URL is not included in the inflow path identification URL received from the terminal 20.

[0452] If it is determined that the ad posting URL is not included in the inflow path identification URL (S430: No), the control unit 11 of the server 10 sets the registration message corresponding to the default inflow path identification URL as an append object message (S440). Then, the control unit 11 of the server 10 proceeds to S140.

[0453] On the other hand, if it is determined that the inflow path identification URL contains the advertising posting URL (S430: Yes), the control unit 11 of the server 10 sets the registration message corresponding to the inflow path identification URL (advertising posting URL), that is, the registration message that matches the inflow path, as an append object message (S450). Then, the control unit 11 of the server 10 proceeds to S140.

[0454] <Effect>

[0455] The fourth embodiment shows the following configuration: the control unit 11 of the server 10 determines to add object messages based on conditions related to the history of changes to the loading page (not limited, but an example of a place where specific information is published).

[0456] As an example of the effect achieved through this configuration, the system can determine which registration message to add to the chat storage based on conditions related to the history of changes in the posting location for specific information. Therefore, it is possible to implement, without limitation, operations such as adding the same registration message if the history of changes is the same, and adding different registration messages if the history of changes is different. In other words, it allows for different controls based on the user's purpose and motivation for obtaining registration messages associated with specific information, thereby improving user convenience.

[0457] In addition, the fourth embodiment shows the following configuration: the control unit 11 of the server 10 adds the registration message associated with the registration URL and the type of page that was displayed by the terminal 20 before it changed to a loading page (not limited, but an example of a place where specific information is published) to the chat storage unit.

[0458] As an example of the effect achieved through this structure, registration messages that are associated with specific information and that correspond to the type of page before the change to the posting location of the specific information are added to the chat storage. Therefore, different controls can be made based on the user's purpose and motivation for obtaining registration messages, thereby improving user convenience.

[0459] In addition, the fourth embodiment shows the following configuration: In the above, the control unit 11 of the server 10 adds a registration message associated with the registration URL and matching the type of page that was displayed by the terminal 20 before it changed to a loading page, along with other registration messages of the same type, to the chat storage unit.

[0460] As an example of the effect achieved through this configuration, a registration message that is associated with specific information and matches the type of page that was previously used to publish the specific information can be added to the chat storage along with other registration messages of the same type. This allows the user to be notified of similar information in addition to the other messages, thereby further improving user convenience.

[0461] <Fourth variation example (1)>

[0462] In the fourth embodiment, the control unit 11 of the server 10 may also determine the append object message based on the type of the loaded page, rather than based on the history of changes to the loaded page.

[0463] Specifically, when the loading page is a page related to sports, the same registration message as in Figure 4-2 is set as an additional object message; when the loading page is a page related to food, the same registration message as in Figure 4-3 is set as an additional object message.

[0464] This variation illustrates how the control unit 11 of server 10 determines the composition of the appended object message based on the type of page loaded (not limited, but an example of conditions related to the place where specific information is published).

[0465] As an example of the effect achieved through this configuration, the system can determine which registration messages to add to the chat storage based on conditions such as the type of place where specific information is posted. Therefore, it is possible to implement, without limitation, the following operation: if the types of places where specific information is posted are the same, the same registration message is added; but if the types of places where specific information is posted are different, different registration messages are added. In other words, different controls can be implemented based on the user's purpose and motivation for obtaining registration messages associated with specific information, thereby improving user convenience.

[0466] <Fourth variation example (2)>

[0467] In the fourth embodiment, a portion of the registration messages among multiple different registration messages can also be set to be common or different based on the inflow path.

[0468] Specifically, without limitation, in the example of Figure 4-1, the first registration message of the two registration messages associated with the first inflow path identification URL and the second inflow path identification URL can be set as a common message (without limitation, as an example, a 20% discount coupon for all sports drinks), and only the second registration message (questionnaire participation) can be different.

[0469] Alternatively, the number of registration messages matching the inflow path can be made different according to the inflow path.

[0470] Specifically, without limitation, in the example of Figure 4-1, it can be set as follows: set one registration message associated with the first inflow path identification URL (without limitation as an example, a 20% discount coupon for all sports drinks), and set two registration messages associated with the second inflow path identification URL (without limitation as an example, a half-price coupon for premium roasted coffee + participation in a questionnaire, or a 20% discount coupon for all sports drinks + a half-price coupon for premium roasted coffee).

[0471] <Fourth variation example (3)>

[0472] In the fourth embodiment, the server 10 can identify a specific inflow path by associating the inflow path identification URL with an object within the loaded page, but is not limited to this.

[0473] In addition, it can be set as an example without limitation: the server 10 can specify the inflow path based on the information of the page from which the user is inflowed to the loaded page, which is a type of data recorded in the access log, namely the "referrer". This is not required.

[0474] <Fifth Embodiment>

[0475] The fifth embodiment is an embodiment that statistically analyzes information related to the tendency to make additional requests to the server 10, the tendency to download coupon information, etc., as described in the above embodiments.

[0476] The content described in the fifth embodiment can be applied to any of the other embodiments and other variations.

[0477] In addition, for constituent elements that are the same as those that have appeared before, the same symbol is used and further explanation is omitted.

[0478] <Data Composition>

[0479] Figure 5-1 is a diagram showing an example of access history data 158 stored in the storage unit 15 of the server 10 in this embodiment.

[0480] In this access history data 158, without limitation, as an example, the access date and time, registration URL, application ID (ordinary account), and attribute information are stored in a time-series manner in an associated manner.

[0481] The access date and time is stored as the date and time when an append request (access) with the registered URL from terminal 20 was made.

[0482] Store the registration URL specified by the append request in the registration URL.

[0483] The application ID (ordinary account) of the user of terminal 20 who made the request is stored in the application ID.

[0484] The attribute information stores the attribute information of the user of terminal 20 who made the request.

[0485] Figure 5-2 is a diagram illustrating an example of official account statistics 159 in this embodiment.

[0486] The official account statistics 159 are data collected by server 10 based on the official account of each OA operator, and related to requests (accesses) from terminal 20 with registered URLs.

[0487] Here, we show the official account statistics 159 corresponding to the official account name (store A) of the OA operator (=store A) with the application ID "ac0020" shown at the front of the OA operator registration message management database 155 in Figure 1-7.

[0488] In the official account statistics 159, there are no restrictions. For example, it includes the official account name and multiple registration URL statistics. The registration URL statistics are the data stored in the registration message management data (see Figure 1-7) corresponding to the official account name.

[0489] The statistics by registered URL are not limited to any one of them; examples include registered URL, independent statistics on visits, and combined statistics on visits.

[0490] Independent visit statistics are data obtained by independently counting visits based on statistical items such as attribute information and time period. They are not limited. As an example, the statistical items are stored in association with the visit count.

[0491] The comprehensive statistics on visit counts are generated based on independent statistics on visit counts and are not limited to any specific data. As an example, the comprehensive data is obtained by counting visit counts based on various combinations of attribute information and time periods.

[0492] <Processing>

[0493] Based on an append request from a registration message with a registration URL from a terminal 20, the control unit 11 of server 10 identifies the application ID (ordinary account) and attribute information of the user of terminal 20 by referring to user registration data 152 (Figures 1-4). Furthermore, the access date and time, the registration URL corresponding to the request, the identified application ID, and the identified attribute information are associated and stored in access history data 158 (Figure 5-1).

[0494] The control unit 11 of server 10 performs access count statistics processing at specified statistical times (not limited, for example, once a week, once a month, etc.).

[0495] It should be noted that the timing of the statistics is not limited to regular times; it can also be set at irregular times, times when statistical operations have been performed manually, etc.

[0496] In the access count statistics processing, the control unit 11 of server 10 is not limited. As an example, based on the access history data 158 (the latest access history data 158) and user registration data 152 at the time of its statistics, the official accounts of each OA operator are taken as objects, and the access count is independently counted according to the access time period information, the user attribute information of terminal 20, and other statistical items, and the results are stored in the access count independent statistics data.

[0497] In addition, the control unit 11 of the server 10 counts accesses based on independent access statistics, and counts accesses for various combinations of attribute information and time periods, and stores the results in the comprehensive access statistics.

[0498] The statistical data (independent access statistics and comprehensive access statistics) generated during the access count processing can be sent, as an example, by the control unit 11 of server 10 to the OA operator device 40 via communication I / F 14. In this way, the OA operator can confirm and understand the statistical data.

[0499] It should be noted that it can also replace the statistics of visits, or in addition to the statistics of downloads of the aforementioned coupon information, etc.

[0500] Alternatively, it can replace the number of visits and downloads, or in addition to these, it can also count the frequency of visits and downloads.

[0501] <Effect>

[0502] This variation illustrates the configuration of the control unit 11 of server 10 to statistically analyze the tendency of additional requests (access to server 10) to register messages (unrestricted, an example of information related to requests with user identification information and specific information).

[0503] As an example of the effect achieved through this configuration, since it is possible to statistically analyze information related to the tendency of requests containing user identification information and specific information, it is possible, without limitation, for example, for message service operators and OA operators to grasp information such as which registered URL was selected by which type of user at what time (and what kind of response to which activity). As a result, it helps to improve and enhance the quality of services provided by OA operators.

[0504] <Other Implementation Methods>

[0505] (1) Specific information

[0506] In the above-described embodiment, a URL is exemplified as specific information associated with the registration message, but it is not limited to this. The specific information is not limited as long as it is unique enough to be used for a specific registration message; for example, it could be a token, hash value, etc. In this case, the control unit 21 of the terminal 20 obtains the specific information such as the token and hash value using any method. Furthermore, the control unit 21 of the terminal 20 establishes a communication connection with the server 10 according to user operations and sends the obtained specific information to the server 10 via communication I / F 22.

[0507] The control unit 11 of server 10 establishes an association between the official account and registration message with the specific information received from terminal 20, and appends the specific registration message to the chat room of the specific official account.

[0508] (2) Establishing the association between specific information and registration messages

[0509] In the above-described embodiment, the control unit 11 of the server 10 stores specific information in association with the registration message in the storage unit 15, but is not limited thereto. That is, it is not necessary to store specific information in association with the registration message in the storage unit 15.

[0510] Without limitation, as an example, the control unit 11 of server 10 generates information (hereinafter referred to as "recoverable information") that is unique to each message (registration message) obtained from OA operator device 40, and can reversibly restore the registration message based on its data.

[0511] In this case, the control unit 21 of terminal 20 obtains recoverable information using any method. Without limitation, as an example, the control unit 21 of terminal 20 downloads and obtains recoverable information from the OA operator's website. Furthermore, the control unit 21 of terminal 20 establishes a communication connection with server 10 according to user operations, and sends an additional request message containing the obtained recoverable information to server 10 via communication I / F 22.

[0512] Upon receiving the additional request, the control unit 11 of server 10 restores the registration message based on the restoreable information received from terminal 20, and appends the restored registration message to the chat room of the corresponding official account.

[0513] (3) System

[0514] The configuration of the communication system 1A described in the above embodiments is merely an example and is not limited thereto. Without limitation, as an example, in the communication system 1A, other devices may also perform part or all of the processing performed by the server 10 (not limited, but an example of an information processing device).

[0515] Figure 6 This is a diagram illustrating an example of the system configuration of the communication system 1B in this embodiment.

[0516] In communication system 1B, the message service operator's server 10 is not limited to functioning as a chat message management server for managing chat messages, but is used as an example.

[0517] In addition, in the communication system 1B, the OA operator device 40 is not limited, and for example it has a registration message management device 41 and a specific information management device 42.

[0518] In communication system 1B, without limitation, as an example, the control unit of the registration message management device 41 generates more than one registration message. Furthermore, the control unit of the specific information management device 42, based on the more than one registration message obtained from the registration message management device 41, outputs specific information for that specific registration message. That is, without limitation, as an example, it performs control functions such as generating specific information for the more than one registration message received from the registration message management device 41, displaying the generated specific information, and sending data (association data) that associates the specific information with the more than one registration message to the server 10.

[0519] It should be noted that the associated data can also be stored in the storage unit of either the registration message management device 41 or the specific information management device 42.

[0520] Furthermore, without limitation, as an example, server 10 (chat message management server) includes a chat storage unit. Moreover, the control unit 11 of server 10 performs the following processing: referring to associated data received from OA operator device 40, based on a request containing first user identification information and first specific information from specific information, a first registration message specified by the first specific information is appended to the chat storage unit; and based on a request containing first user identification information and second specific information from specific information, a second registration message specified by the second specific information is appended to the chat storage unit.

[0521] It should be noted that the above composition is just one example and is not limited to this.

[0522] Without limitation, as an example, the control unit 11 of server 10 sends the specific information to the specific information management device 42 based on a request containing first user identification information and specific information. Furthermore, the specific information management device 42 identifies the registration message associated with the specific information received from server 10 based on association data, and indirectly executes the control of appending the registration message to the chat storage unit by sending instructions to server 10, wherein the instructions are used to instruct the appending of the identified registration message to the chat storage unit.

[0523] That is, in the system disclosed herein, the control unit (control device) does not necessarily need to be one, and there may be multiple control units (multiple control devices).

[0524] Furthermore, these multiple control units can share the responsibility of executing various controls.

[0525] Alternatively, the chat storage unit described in this disclosure can be located in a device external to server 10. The device equipped with the chat storage unit can be a device of a messaging service operator or an OA (Office Automation) operator.

[0526] That is, in the system disclosed herein, a device other than server 10 (information processing device) may also have a chat storage unit.

[0527] Symbol Explanation

[0528] 1 (1A, 1B) Communication System

[0529] 10 servers

[0530] 20 terminals

[0531] 30 Network

[0532] 40 OA operator devices

[0533] 41 Registration Message Management Device

[0534] 42 Specific Information Management Device

Claims

1. An information processing system, comprising at least an information processing device for providing message services, wherein, The information processing system has the following features: A chat storage unit, which stores chat information, including messages sent by a second user to the first user, identified according to a second user identification information of a second category, in association with the first user's first user identification information of a first user; and One or more control units, The one or more control units perform the following processing: Based on the case of obtaining more than one registration message, output specific information for the specific one or more registration messages; Based on a request containing the first user identification information and the first specific information from the specific information, a first registration message specific to the first specific information is appended to the chat storage unit; as well as Based on a request containing the first user identification information and the second specific information from the specific information, a second registration message specific to the second specific information is appended to the chat storage unit.

2. The information processing system according to claim 1, wherein, The control unit will append any one of the multiple first registration messages specified by the first specific information to the chat storage unit.

3. The information processing system according to claim 2, wherein, The control unit will append any one of the multiple second registration messages specified by the second specific information to the chat storage unit.

4. The information processing system according to claim 3, wherein, The plurality of first registration messages and the plurality of second registration messages are a portion of common messages.

5. The information processing system according to claim 2, wherein, The control unit determines which registration messages to add to the chat storage unit based on conditions.

6. The information processing system according to claim 5, wherein, The conditions include those related to the number or frequency of the requests.

7. The information processing system according to claim 5, wherein, The registration message is associated with service information, wherein the service information is related to the service provided by the second user. The conditions include those related to the number or frequency with which the service information associated with the registration message is obtained based on the registration message being appended to the chat storage.

8. The information processing system according to claim 5, wherein, The conditions include those related to the place where the specific information is published.

9. The information processing system according to claim 8, wherein, The conditions include those related to historical changes to the publishing location.

10. The information processing system according to claim 1, wherein, The system includes a statistics unit that performs statistical analysis on information related to the tendency of the request.

11. An information processing method, comprising at least an information processing apparatus for providing message services, wherein... The information processing method includes the following processes: Chat information, including messages sent by a second user to the first user based on a second user identification information of a second category, is stored in the chat storage unit of the system in association with the first user identification information of the first user of a first category; Based on the situation of obtaining more than one registration message, one or more control units in the system are used to output specific information for a specific one or more registration messages; Based on a request containing the first user identification information and the first specific information from the specific information, the one or more control units append a first registration message specific to the first specific information to the chat storage unit; as well as Based on a request containing the first user identification information and the second specific information from the specific information, the one or more control units append a second registration message specific to the second specific information to the chat storage unit.

12. An information processing apparatus for providing message services, wherein, The information processing device includes: A chat storage unit, which stores chat information, including messages sent by a second user to the first user, identified according to a second user identification information of a second category, in association with the first user's first user identification information of a first user; and Control Department The control unit performs the following processing: Based on the case of obtaining more than one registration message, output specific information for the specific one or more registration messages; Based on a request containing the first user identification information and the first specific information from the specific information, a first registration message specific to the first specific information is appended to the chat storage unit; as well as Based on a request containing the first user identification information and the second specific information from the specific information, a second registration message specific to the second specific information is appended to the chat storage unit.

13. A storage medium storing a program that is executed by an information processing device for providing message services, wherein, The information processing device performs the following processing: Chat information, including messages sent by a second user to the first user based on a second user identification information of a second category, is stored in the chat storage unit of the information processing device in association with the first user identification information of the first user of a first category; Based on the situation of obtaining more than one registration message, specific information for the specific one or more registration messages is output; Based on a request containing the first user identification information and the first specific information from the specific information, a first registration message specific to the first specific information is appended to the chat storage unit; as well as Based on a request containing the first user identification information and the second specific information from the specific information, a second registration message specific to the second specific information is appended to the chat storage unit.

14. A terminal that performs processing related to a messaging service, wherein, The terminal has: A chat storage unit, which associates with the user of the terminal, i.e., the first user's first user identification information of the first category, to store chat information including messages sent by the second user to the first user, identified according to the second user identification information of the second category; and Control Department The control unit performs the following processing: Obtain specific information, which is used to specify one or more registration messages that are specified by the specific information; Based on a request containing the first user identification information and the first specific information from the specific information, a first registration message specific to the first specific information is appended to the chat storage unit; as well as Based on a request containing the first user identification information and the second specific information from the specific information, a second registration message specific to the second specific information is appended to the chat storage unit.

15. A storage medium storing a program for causing a terminal to perform processing related to a messaging service, wherein, The terminal performs the following processing: Chat information, including messages sent by a second user to the first user based on a second user identification information of a second category, is stored in the chat storage unit of the terminal in association with the first user identification information of the first user ... Obtain the specific information used for one or more registration messages specified by specific information; Based on a request containing the first user identification information and the first specific information from the specific information, a first registration message specific to the first specific information is appended to the chat storage unit; as well as Based on a request containing the first user identification information and the second specific information from the specific information, a second registration message specific to the second specific information is appended to the chat storage unit.

Images