WO2022004487A1 - プログラム、情報処理方法、およびサーバ - Google Patents

プログラム、情報処理方法、およびサーバ Download PDF

Info

Publication number
WO2022004487A1
WO2022004487A1 PCT/JP2021/023601 JP2021023601W WO2022004487A1 WO 2022004487 A1 WO2022004487 A1 WO 2022004487A1 JP 2021023601 W JP2021023601 W JP 2021023601W WO 2022004487 A1 WO2022004487 A1 WO 2022004487A1
Authority
WO
WIPO (PCT)
Prior art keywords
user
remittance
server
information
terminal
Prior art date
Application number
PCT/JP2021/023601
Other languages
English (en)
French (fr)
Japanese (ja)
Inventor
亮介 濱窄
洋輔 真崎
Original Assignee
Ｌｉｎｅ株式会社
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Ｌｉｎｅ株式会社 filed Critical Ｌｉｎｅ株式会社
Priority to KR1020227046407A priority Critical patent/KR20230019164A/ko
Priority to CN202180046960.XA priority patent/CN115997227A/zh
Publication of WO2022004487A1 publication Critical patent/WO2022004487A1/ja

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/02—Payment architectures, schemes or protocols involving a neutral party, e.g. certification authority, notary or trusted third party [TTP]
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/04—Payment circuits
    • G06Q20/06—Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/08—Payment architectures
    • G06Q20/10—Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
    • G06Q50/01—Social networking
    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
    • G06Q50/10—Services
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L51/00—User-to-user messaging in packet-switching networks, transmitted according to store-and-forward or real-time protocols, e.g. e-mail
    • H04L51/04—Real-time or near real-time messaging, e.g. instant messaging [IM]

Definitions

  • the present invention relates to a program, an information processing method, and a server.
  • Patent Document 1 discloses that a user posts a message by SNS (Social Networking Service), and when the message is confirmed, a process of changing the message from an unread state to a read state is performed.
  • SNS Social Networking Service
  • the chat room including at least the first user and the second user is input to the first terminal of the first user displayed by the first user and transmitted from the first terminal.
  • the first content is transmitted to the second terminal of the second user, and the second content input by the second user to the second terminal where the chat room is displayed and transmitted from the second terminal is transmitted.
  • the communication unit of the server Based on the first setting and the input to the chat room displayed on the second terminal by the second user, information regarding the transfer of money from the second user to the first user is received by the communication unit of the server.
  • the server executes a process related to the transfer from the second user to the first user based on the information regarding the transfer from the second user to the first user. ..
  • the chat room including at least the first user and the second user is input to the first terminal of the first user displayed by the first user and transmitted from the first terminal.
  • the first content is transmitted to the second terminal of the second user, and the second content input by the second user to the second terminal in which the chat room is displayed and transmitted from the second terminal is transmitted.
  • the control unit of the server controls the chat room to set the first setting for sending money to the first user.
  • information regarding the transfer of money from the second user to the first user is received by the communication unit of the server. This includes that the control unit performs a process related to the remittance from the second user to the first user based on the information regarding the remittance from the second user to the first user.
  • the chat room including at least the first user and the second user is input to the first terminal of the first user displayed by the first user and transmitted from the first terminal.
  • the first content is transmitted to the second terminal of the second user, and the second content input by the second user to the second terminal in which the chat room is displayed and transmitted from the second terminal is transmitted.
  • a control unit that is a server that transmits to the first terminal and controls the chat room to set a first setting for remittance to the first user, and the first setting and the second user.
  • a communication unit for receiving information regarding a transfer from the second user to the first user based on an input to the chat room displayed on the second terminal is provided, and the control unit is provided from the second user. Based on the information regarding the remittance to the first user, the process related to the remittance from the second user to the first user is performed.
  • the flowchart which shows the procedure of information processing which concerns on 1st Embodiment.
  • FIG. 1 shows the configuration of the communication system 1 according to the embodiment of the present disclosure.
  • the server 10 the user terminal 20 (user terminal 20A, user terminal 20B, user terminal 20C), and the payment server 30 are connected via the network N.
  • the server 10 provides a service that realizes transmission / reception of messages and other data (including, but not limited to, video data and sound data as an example) between a plurality of user terminals 20 via a network N. Further, the server 10 executes a remittance process between the payment servers 30 via the network N.
  • the number of servers 10, user terminals 20, and payment servers 30 connected to the network N is not limited.
  • Network N plays a role of connecting one or more servers 10, one or more user terminals 20, and a payment server 30. That is, the network N means a communication network that provides a connection route so that data can be transmitted and received after the user terminal 20 connects to the server 10.
  • Network N may or may not be a wired network or a wireless network. Further, one or more parts of the network N may or may not be an IP (Internet Protocol) network.
  • Network N is not limited, but as an example, ad hoc network, intranet, extranet, virtual private network (VPN), local area network (LAN), wireless.
  • VPN virtual private network
  • LAN local area network
  • the network N can include one or more networks N.
  • the server 10 has a function of providing a predetermined service to the user terminal 20.
  • the server 10 may be any device as long as it can realize the functions described in each embodiment.
  • the server 10 is not limited, but by example, a server computer, a personal computer (not limited, by example, a desktop, a laptop, a tablet, etc.), a media computer platform (not limited, by example, a cable, a satellite set top box, a digital video). Includes recorders), handheld computer devices (for example, but not limited to PDA, e-mail clients, etc.), or other types of computers, or communication platforms.
  • the server 10 may be expressed as an information processing device.
  • the user terminal 20 may be any information processing device as long as it is an information processing device (computer) capable of realizing the functions described in each embodiment.
  • the user terminal 20 is not limited to, for example, a smartphone, a mobile phone (feature phone), a personal computer (not limited to, for example, a desktop, a laptop, a tablet, etc.), a media computer platform (not limited to, for example, a cable, etc.). Satellite set top boxes, digital video recorders), handheld computer devices (not limited to, for example, PDAs (personal digital assistants), email clients, etc.), wearable terminals (glasses-type devices, clock-type devices, etc.), and other types. Includes computers or communication platforms. Further, the user terminal 20 may be expressed as an information processing device.
  • the user information is user information associated with an account used by the user in a predetermined service.
  • the user information may include information input by the user or may include information given by a predetermined service.
  • the user information is not limited, but as an example, at least one of a plurality of items of information such as a user's name, a user's icon image, a user's age, a user's gender, a user's address, a user's hobbies and tastes, and a user's identifier. Contains information.
  • the user information is information different from the information of the above-mentioned plurality of items, and may include information associated with the user.
  • the payment server 30 has a function of providing a service related to remittance according to an instruction from the server 10.
  • the payment server 30 may be any device as long as it can realize the functions described in each embodiment.
  • the payment server 30 is not limited, but by example, a server computer, a personal computer (not limited, by example, a desktop, a laptop, a tablet, etc.), a media computer platform (not limited, by example, a cable, a satellite set top box, a digital). Includes video recorders), handheld computer devices (for example, but not limited to PDA, e-mail clients, etc.), or other types of computers, or communication platforms.
  • the payment server 30 may be expressed as an information processing device. ⁇ Hardware (HW) configuration>
  • the server 10 includes a control unit (CPU) 11, a storage unit 15, a communication I / F (interface) 14, an input unit 12, and an output unit 13.
  • Each component of the HW of the server 10 is connected to each other via the bus B1 as an example without limitation. It is not essential that the HW of the server 10 includes all the components as the configuration of the HW of the server 10. As an example, but not limited to, the HW of the server 10 may or may not have a configuration in which the output unit 13 can be removed.
  • the control unit 11 has a circuit physically structured to execute a function realized by a code or an instruction contained in the program, and is not limited to, but as an example, a data processing device built in hardware. Is realized by.
  • the control unit 11 is typically a central processing unit (CPU), and may or may not be a microprocessor, a processor core, a multiprocessor, an ASIC, or an FPGA. In the present disclosure, the control unit 11 is not limited to these.
  • the storage unit 15 has a function of storing various programs and various data required for the server 10 to operate.
  • the storage unit 15 is realized by various storage media such as HDD, SSD, and flash memory. However, in the present disclosure, the storage unit 15 is not limited to these. Further, the storage unit 15 may or may not be expressed as a memory.
  • Communication I / F14 sends and receives various data via network N.
  • Communication by communication I / F14 may be executed by wire or wireless, and any communication protocol may be used as long as mutual communication can be executed.
  • the communication I / F 14 has a function of executing communication with another device such as the user terminal 20 via the network N.
  • the communication I / F 14 transmits various data to other devices according to instructions from the control unit 11. Further, the communication I / F 14 receives various data transmitted from other devices and transmits them to the control unit 11. Further, the communication I / F 14 may be simply expressed as a communication unit. Further, when the communication I / F 14 is composed of a physically structured circuit, it may be expressed as a communication circuit.
  • the input unit 12 is realized by a device that inputs various operations to the server 10.
  • the input unit 12 is realized by any one or a combination of all kinds of devices capable of receiving an input from a user and transmitting information related to the received input to the control unit 11.
  • the input unit 12 is typically realized by a hardware key typified by a keyboard or the like, or a pointing device such as a mouse.
  • the input unit 12 may or may not include, as an example, a touch panel, a camera (operation input via a moving image), and a microphone (operation input by voice), without limitation. However, in the present disclosure, the input unit 12 is not limited to these.
  • the output unit 13 includes a display unit 13a as an example, not a limitation.
  • the display unit 13a is typically realized by a monitor (not limited to, for example, a liquid crystal display or OELD).
  • the display unit 13a may or may not be a head-mounted display (HDM) or the like. It should be noted that these display units 13a may or may not be able to display display data in 3D. However, in the present disclosure, the display unit 13a is not limited to these.
  • the server 10 stores the program P1 and the databases D11 to D15 in the storage unit 15.
  • the control unit 11 executes this program P1 to execute the processing as each unit included in the control unit 11. That is, the program 15a stored in the storage unit 15 causes the server 10 to realize each function executed by the control unit 11.
  • This program P1 may or may not be expressed as a program module.
  • the user terminal 20 includes a control unit (CPU: central processing unit) 21, a storage unit 25, a communication I / F (interface) 24, an input unit 22, and an output unit 23.
  • Each component of the HW of the user terminal 20 is connected to each other via the bus B2 as an example without limitation. It is not essential that the HW configuration of the user terminal 20 includes all the components. As an example, but not limited to, the user terminal 20 may or may not have a configuration in which individual components such as an input unit 22, an output unit 23, or a plurality of components can be removed. ..
  • the communication I / F24 transmits / receives various data via the network N.
  • Communication by communication I / F24 may be executed by wire or wireless, and any communication protocol may be used as long as mutual communication can be executed.
  • the communication I / F 24 has a function of executing communication with the server 10 via the network N.
  • the communication I / F 24 transmits various data to the server 10 according to the instruction from the control unit 21. Further, the communication I / F 24 receives various data transmitted from the server 10 and transmits the various data to the control unit 21. Further, the communication I / F 24 may be simply expressed as a communication unit. Further, when the communication I / F 24 is composed of a physically structured circuit, it may be expressed as a communication circuit.
  • the input unit 22 includes a device for inputting various operations to the user terminal 20.
  • the output unit 23 includes a device that outputs a processing result processed by the user terminal 20.
  • the input unit 22 and the output unit 23 may or may not be specified as input / output units. When specified as an input / output unit, the input / output unit may be integrated with the input unit 22 and the output unit 23, or may be separated into the input unit 22 and the output unit 23.
  • the input unit 22 is realized by any one or a combination of all kinds of devices capable of receiving an input from a user and transmitting information related to the received input to the control unit 21.
  • the input unit 22 includes, but is not limited to, an operation unit 22a, a microphone 22b, and a camera 22c.
  • the operation unit 22a includes, but is not limited to, hardware keys such as a touch panel, a touch display, and a keyboard, and a pointing device such as a mouse.
  • the microphone 22b includes, but is not limited to, a device for inputting voice as an example.
  • the microphone 22b is used for inputting voice data.
  • the camera 22c includes, but is not limited to, a device for inputting an image.
  • the camera 22c is used for acquiring image data.
  • the output unit 23 is realized by any one or a combination of all kinds of devices capable of outputting the processing result processed by the control unit 21.
  • the output unit 23 includes, but is not limited to, a display unit 23a and a speaker (audio output) 23b as an example.
  • the output unit 23 further includes, as an example, not a limitation, a touch panel, a touch display, a lens (not a limitation, as an example, a 3D (three dimensions) output, a hologram output), a printer, and the like.
  • the display unit 23a is realized by any or a combination of all kinds of devices capable of displaying an image according to the display data written in the frame buffer.
  • the display unit 23a is not limited, but as an example, a touch panel, a touch display, a monitor (not limited, as an example, a liquid crystal display or an Electroluminescence display), a head mounted display (HDM: Head Mounted Display), a projection mapping, and a hologram. , Includes a device capable of displaying images, text information, etc. in air (which may or may not be vacuum). It should be noted that these display units 23a may or may not be able to display display data in 3D.
  • the speaker 23b is used for outputting audio data.
  • the input unit 22 and the output unit 23 are not limited to each other, and may be specified as an input / output unit and configured as a touch panel as an example.
  • the operation unit 22a and the display unit 23a may be arranged so as to face each other with substantially the same size and shape.
  • the control unit 21 has a circuit physically structured to execute a function realized by a code or an instruction contained in the program, and is not limited to, but as an example, a data processing device built in hardware. Is realized by. Therefore, the control unit 21 may or may not be expressed as a control circuit.
  • the control unit 21 is not limited to, for example, a central processing unit (CPU), a microprocessor (microprocessor), a processor core (processor core), a multiprocessor (multiprocessor), an ASIC (application-specific integrated circuit), or an FPGA (field). Includes programmable gate array).
  • CPU central processing unit
  • microprocessor microprocessor
  • processor core processor core
  • multiprocessor multiprocessor
  • ASIC application-specific integrated circuit
  • FPGA field. Includes programmable gate array).
  • the storage unit 25 has a function of storing various programs and various data required for the user terminal 20 to operate.
  • the storage unit 25 includes various storage media such as HDD (hard disk drive), SSD (solid state drive), flash memory, RAM (random access memory), and ROM (read only memory), without limitation. Further, the storage unit 25 may or may not be expressed as a memory.
  • the user terminal 20 stores the program P1 and the databases D21 to D25 in the storage unit 25.
  • the control unit 21 executes this program P2 to execute the processing as each unit included in the control unit 21. That is, the program P2 stored in the storage unit 25 causes the user terminal 20 to realize each function executed by the control unit 21. Further, this program P2 may or may not be expressed as a program module. (3) HW configuration of payment server
  • the payment server 30 includes a control unit (CPU) 31, a storage unit 35, a communication I / F (interface) 34, an input unit 32, and an output unit 33.
  • Each component of the HW of the payment server 30 is connected to each other via bus B3, for example, without limitation. It is not essential that the HW of the payment server 30 includes all the components as the configuration of the HW of the payment server 30. As an example, but not limited to, the HW of the payment server 30 may or may not have a configuration in which the output unit 33 can be removed.
  • the control unit 31 has a circuit physically structured to execute a function realized by a code or an instruction contained in the program, and is not limited to, but as an example, a data processing device built in hardware. Is realized by.
  • the control unit 31 is typically a central processing unit (CPU), and may or may not be a microprocessor, a processor core, a multiprocessor, an ASIC, or an FPGA. In the present disclosure, the control unit 11 is not limited to these.
  • the storage unit 35 has a function of storing various programs and various data required for the payment server 30 to operate.
  • the storage unit 15 is realized by various storage media such as HDD, SSD, and flash memory. However, in the present disclosure, the storage unit 35 is not limited to these. Further, the storage unit 35 may or may not be expressed as a memory.
  • Communication I / F34 sends and receives various data via network N.
  • Communication by communication I / F 34 may be executed by wire or wireless, and any communication protocol may be used as long as mutual communication can be executed.
  • the communication I / F 34 has a function of executing communication with another device such as the user terminal 20 via the network N.
  • the communication I / F 34 transmits various data to other devices according to instructions from the control unit 11. Further, the communication I / F 34 receives various data transmitted from other devices and transmits them to the control unit 31. Further, the communication I / F 34 may be simply expressed as a communication unit. Further, when the communication I / F 34 is composed of a physically structured circuit, it may be expressed as a communication circuit.
  • the input unit 32 is realized by a device that inputs various operations to the server 30.
  • the input unit 32 is realized by any one or a combination of all kinds of devices capable of receiving an input from a user and transmitting information related to the received input to the control unit 31.
  • the input unit 32 is typically realized by a hardware key typified by a keyboard or the like, or a pointing device such as a mouse.
  • the input unit 32 may or may not include, as an example, a touch panel, a camera (operation input via a moving image), and a microphone (operation input by voice), without limitation. However, in the present disclosure, the input unit 32 is not limited to these.
  • the output unit 33 includes a display unit 33a as an example, not a limitation.
  • the display unit 33a is typically realized by a monitor (not limited to, for example, a liquid crystal display or OELD).
  • the display unit 33a may or may not be a head-mounted display (HDM) or the like. It should be noted that these display units 33a may or may not be able to display display data in 3D. However, in the present disclosure, the display unit 33a is not limited to these.
  • the payment server 30 stores the program P3 and the database D31 in the storage unit 35.
  • the control unit 31 executes this program P3 to execute the processing as each unit included in the control unit 31. That is, the program P3 stored in the storage unit 35 causes the payment server 30 to realize each function executed by the control unit 31.
  • This program P3 may or may not be expressed as a program module.
  • the control unit 21 of the user terminal 20 and / or the control unit 11 of the server 10 is formed not only in a CPU having a control circuit but also in an integrated circuit (IC (Integrated Circuit) chip, LSI (Large Scale Integration)) and the like. Each process may or may not be realized by a logic circuit (hardware) or a dedicated circuit. Further, these circuits may be realized by one or a plurality of integrated circuits, and the plurality of processes shown in each embodiment may or may not be realized by one integrated circuit. In addition, LSI may be referred to as VLSI, super LSI, ultra LSI, or the like depending on the degree of integration. Therefore, the control unit 21, the control unit 11, and / or the control unit 31 may or may not be expressed as a control circuit.
  • IC Integrated Circuit
  • LSI Large Scale Integration
  • the program of each embodiment of the present disclosure may be provided in a state of being stored in a computer-readable storage medium. It does not have to be done.
  • the storage medium can store the program of each embodiment in a "non-temporary tangible medium".
  • the program of each embodiment may or may not be for realizing a part of the function of each embodiment of the present disclosure. Further, it may or may not be a so-called difference file (difference program) that can realize the functions of each embodiment of the present disclosure in combination with a program already recorded in the storage medium.
  • the storage medium may be one or more semiconductor-based or other integrated circuits (ICs) (for example, but not limited to field programmable gate arrays (FPGAs) or application-specific ICs (ASICs)), hard disks.
  • the storage medium may be volatile, non-volatile, or a combination of volatile and non-volatile, where appropriate.
  • the storage medium is not limited to these examples, and may be any device or medium as long as the program P can be stored. Further, the storage medium may or may not be expressed as a memory.
  • the servers 10, 30 and / or the user terminal 20 can read the program stored in the storage medium and execute the read program to realize the functions of the plurality of functional units shown in each embodiment.
  • the program of the present disclosure may or may not be provided to the servers 10, 30 and / or the user terminal 20 via any transmission medium (communication network, broadcast wave, etc.) capable of transmitting the program. May be good.
  • the server 10, 30 and / or the user terminal 20 realizes the functions of the plurality of functional units shown in each embodiment by executing the program P downloaded via the Internet or the like, as an example without limitation.
  • each embodiment of the present disclosure can also be realized in the form of a data signal embedded in a carrier wave, in which the program is embodied by electronic transmission.
  • At least a part of the processing in the servers 10, 30 and / or the user terminal 20 may be realized by one or more computers (cloud computing composed of one or more computers, for example, but not limited to). It doesn't have to be.
  • At least a part of the processing in the user terminal 20 may or may not be performed by the server 10. In this case, at least a part of the processing of each functional unit of the control unit 21 of the user terminal 20 may or may not be performed by the server 10.
  • At least a part of the processing in the server 10 may or may not be performed by the user terminal 20. In this case, at least a part of the processing of each functional unit of the control unit 11 of the server 10 may or may not be performed by the user terminal 20.
  • At least a part or all of the processing in the payment server 30 may or may not be performed by the server 10. In this case, at least a part or all of the processing of each functional unit of the control unit 31 of the payment server 30 may or may not be performed by the server 10.
  • the configuration of the determination in the embodiment of the present disclosure is not essential, and a predetermined process may be operated when the determination condition is satisfied, or a predetermined process may be performed when the determination condition is not satisfied. It may or may not be.
  • the program of this disclosure is not limited to, but examples include 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. Implemented using.
  • the information processing according to the embodiment is not limited, but provides a service for executing remittance-related processing (not limited, but as an example, remittance processing) between user terminals 20 of a group including a plurality of users.
  • Remittance processing includes, but is not limited to, processing relating to remittances and remittance requests, as an example. The remittance process will be described later.
  • the user of the user terminal 20A is referred to as the user A
  • the user of the user terminal 20B is referred to as the user B
  • the user of the user terminal 20C is referred to as the user C.
  • the number of users included in one group is any number of 2 or more.
  • one group may be composed of user A and user B, and the number of users included in this group is two.
  • the other group may be composed of user A, user B, and user C, and the number of users included in this group is three.
  • the service provided by the information processing according to the embodiment is referred to as a messaging service as appropriate.
  • the user terminal 20 displays an image of a graphical user interface (appropriately referred to as a GUI) provided by a messaging service as an example, not limited to.
  • a GUI that allows users included in a group to view contents transmitted and received between terminals of a group including a plurality of users is referred to as a talk room.
  • the talk room may be referred to as a chat room.
  • the talk room is not limited, but as an example, is a display area in which messages can be sent and received between participating users.
  • the talk room is not limited, and as an example, a name different from the user name registered in the server 10 may be used in the area. Further, the talk room is not limited, and as an example, may be capable of sending and receiving messages even if there is no friendship, follow-up relationship, or follow-up relationship between participating users.
  • the above content is not limited, but includes at least one of text, image, and audio as an example.
  • the text contained in the content includes, but is not limited to,, as an example, at least one of national characters represented by character codes, extended characters, machine-dependent characters, numbers, symbols, figures, and symbols.
  • the text included in the content may not include at least one of the above characters, extended characters, machine-dependent characters, numbers, symbols, figures, and symbols, and may include other texts.
  • the images included in the content are not limited, but are examples, such as captured images captured by a camera, processed images obtained by processing the captured images, and computer graphics images generated using a computer (as an example, not limited). , Icon, pictogram, face character), and at least one of the text images that image the text.
  • the image included in the content may include a composite image obtained by synthesizing two or more of the above captured image, processed image, computer graphics image, and various images of the text image.
  • the image included in the content may not include at least one of the captured image, the processed image, the computer graphics image, the text image, and the composite image, and may include other images.
  • the image included in the content may be a still image, a moving image, or an image in another form.
  • the content including the image may be represented by an icon such as a thumbnail in the image of the talk room as an example without limitation.
  • the user terminal 20 may display an image included in the content based on an input to an icon representing an image included in the content.
  • the voice included in the content is not limited, but as an example, the recorded voice recorded by the microphone, the processed voice processed by the recorded voice, the synthesized voice generated by the computer, the reading function of the computer, etc. are used. Includes at least one of the read-aloud voices converted from the text.
  • the voice included in the content may include a combination voice in which two or more of the various voices of the recorded voice, the processed voice, the synthetic voice, and the read-aloud voice are combined.
  • the voice included in the content may not include at least one of the recorded voice, processed voice, synthetic voice, read-aloud voice, and combined voice, and may include other voices.
  • the voice contained in the content may include at least one of a person or a non-human organism's sound or voice, a sound made by an object such as an instrument or machine, a sound effect, an environmental sound, a noise sound, and an alarm. It may not include at least one of these sounds or voices, and may include voices different from these sounds or voices.
  • the content including audio may be represented by an icon or the like in the image of the talk room as an example without limitation.
  • the user terminal 20 may reproduce the voice included in the content based on the input to the icon representing the voice included in the content.
  • the content is not limited, but may be a combination of two or more of text, image, and voice as an example.
  • the content is not limited, but as an example, it may be content in which video and audio are played in parallel, content in which images and text are displayed in combination, and text is displayed in accordance with audio playback. Content may be used. Further, the content may be content in which audio is played in parallel with the display of text and images.
  • the content is not limited, but may be, as an example, a combination of at least one of text, image, and voice and content different from any of text, image, and voice.
  • the storage unit 15 of the server 10 stores information used in the messaging service as an example, not limited to the storage unit 15.
  • the information includes, but is not limited to, user information D11, talk room information D12, content information D13, remittance account information D14, and remittance history information D15.
  • the user information D11 includes, but is not limited to, a user ID and password associated with each account in the messaging service.
  • the user terminal 20 transmits the account information D21 to the server 10.
  • the server 10 collates the user ID and password included in the account information D21 with the user information D11 to identify the user associated with the user terminal 20.
  • the talk room information D12, the content information D13, the remittance account information D14, and the remittance history information D15 will be described later.
  • the storage unit 25 of the user terminal 20 stores information used in the messaging service as an example, not limited to the storage unit 25.
  • the information includes, but is not limited to, account information D21, talk room information D22, content information D23, remittance account information D24, and remittance history information D25.
  • the talk room information D22, the content information D23, the remittance account information D24, and the remittance history information D25 will be described later.
  • the account information D21 is the information of the account used by the user of the user terminal 20 in the messaging service.
  • the account information D21 is information used for user authentication in the messaging service.
  • Account information D21 includes, but is not limited to, user identification information and a password.
  • the user identification information is appropriately referred to as a user ID.
  • the user ID may be information registered by the user of the user terminal 20, or may be information given in the messaging service.
  • the storage unit 25 does not have to store one or both of the user ID and the password.
  • the user may operate the input / output unit 23 of the user terminal 20 to input necessary information among the user ID and the password when the user is authenticated in the messaging service.
  • the account information D21 may include information different from the user ID and password.
  • the account information D21 may include information such as a user's fingerprint, a vein pattern, and a face photograph as the information used for biometric authentication.
  • the storage unit 25 does not have to store at least a part of the information used for the messaging service (for example, not limited to the talk room information D22, the content information D23, the remittance account information D24, and the remittance history information D25).
  • the information used for the messaging service may be stored in an external storage unit (not limited to the storage unit 15 of the server 10 as an example) of the user terminal 20.
  • the user terminal 20 may store the information.
  • the information used for the service may be acquired from the external storage unit of the user terminal 20 via the network N, as an example without limitation.
  • FIG. 2 is a diagram showing information processing according to the first embodiment. The outline of this embodiment will be described.
  • the server 10 is not limited, but as an example, the content input by the user in the user terminal 20 of a certain user in which the talk room in which a plurality of users participate is displayed and transmitted from the user terminal 20 is input to the user of another user. Send to terminal 20. Further, the server 10 is not limited, but as an example, the content input by another user to the user terminal 20 of another user in which the talk room is displayed and transmitted from the user terminal 20 is transmitted to the user terminal 20 of a certain user. Send.
  • This embodiment is not limited to, but as an example, is a mode in which remittance is executed from a user terminal 20 of a certain user to a user terminal 20 of another user in a talk room.
  • the user terminal 20 of another user requests the server 10 for remittance processing via the communication unit (not limited to the communication I / F24 as an example).
  • the server 10 executes the remittance process based on the remittance process request, as an example, not the limitation.
  • the remittance process is a process of remittance from a user's remittance account to another user's remittance account in the talk room.
  • the remittance in the remittance process is not limited to the transmission and reception of information regarding a payment method utilizing information and communication technology.
  • the payment method utilizing the information and communication technology is not limited, but is, for example, electronic value, electronic money, and the like.
  • Electronic value and electronic money include, but are not limited to, information indicating gold, electronic money, points, and the like.
  • information on payment methods utilizing information and communication technology will be referred to as "value".
  • the user terminal 20 displays the remittance setting image T4 for setting the remittance content shown in FIG. 2B (e) in the display area 28 as an example without limitation. Then, in FIG. 2B (e), the user terminal 20 receives input from a certain user to the input unit 22 and specifies a remittance account and a remittance amount used for remittance. As an example, the user terminal 20 transmits a remittance processing request including information on the remittance to the server 10 when the remittance content is confirmed. The server 10 identifies the remittance account included in the information about the remittance, as an example, but not a limitation.
  • the server 10 sends information about the remittance to the payment server 30 corresponding to the specified remittance account, as an example, but not limited to.
  • the payment server 30 completes the remittance from one user to another by updating the remittance account information D31 as an example but not a limitation.
  • the user terminal 20 displays the image T7 of the talk room including the content Q2 and the content Q3 indicating the completion of the remittance process, as shown in FIG. 2B (h).
  • the content Q1 is the text "1000 yen per person”
  • the content Q2 and the content Q3 are the text "sent 1000 yen”.
  • the server 10 may or may not automatically transmit the content Q2 and the content Q3 to the user terminal 20 when the remittance process is completed.
  • Reference numeral TL in FIG. 2A (a) is an image showing a list of talk rooms.
  • the user terminal 20 displays the image TL of the list of the own terminal or the talk room associated with the user of the own terminal in the display area 28 as an example without limitation.
  • the user terminal 20 may display an image TL of a list of talk rooms that is not associated with the user of the terminal or the own terminal in the display area 28 as an example without limitation.
  • "coffee party”, “tea party”, “athletic meet”, and "baseball lover” are icons with the name of the talk room.
  • the icon is not a limitation but an image displayed in the display area 28 as an example.
  • the user terminal 20 determines that the talk room whose name is "Coffee Party" is selected when the input unit 22 receives an input for the "Coffee Party” icon.
  • the input unit 22 inputs an input to the "coffee party” icon displayed in the display area 28, the user terminal 20 determines that the talk room whose name is "coffee party” is selected, and FIG. 2A.
  • the image T1 of the talk room whose name is "Coffee Party" is displayed in the display area 28.
  • each user can generate a talk room as an example, not a limitation.
  • a talk room including the user selected by the user is generated by the server 10.
  • a talk room may be generated without each user selecting one or more users.
  • the process of generating the talk room is not limited to being executed by the server 10, and may be executed by the user terminal 20 or may be executed by the user terminal 20 and the server 10.
  • the process of generating the talk room may be executed by a device different from the user terminal 20 and the server 10.
  • the user A has generated the talk room "coffee party" in the present embodiment as appropriate. Further, it is assumed that User B and User C are participating in the talk room "Coffee Party”.
  • user A may be referred to as an "administrator”, and user B and user C may be referred to as “participants”.
  • the administrator is not limited, but is, for example, a user who has created a talk room, a user selected from users participating in the talk room, and the like.
  • the manager may be called a "master" as an example, not a limitation.
  • the participant is not limited, but as an example, a user different from the administrator and a user participating in the generated talk room.
  • the user terminal 20 of the participant is not limited, but as an example, when an input is made to the input unit 22 for an icon with the name of the talk room, it is determined that the icon is selected and the talk room is selected. Participants may be invited to join the talk room by sending a request to join the server 10. Further, the user terminal 20 of the participant is not limited, but as an example, when an input is made to the input unit 22 for a predetermined URL, it is determined that the URL is selected, and the talk room associated with the URL is used. The image may be displayed in the display area 28 and the participants may participate in the talk room. Further, the user terminal 20 of the participant is not limited, and as an example, the participant may be made to participate in the talk room based on the participation request received from the user terminal 20 of the user who generated the talk room.
  • the reference numeral Ta is the name of the talk room.
  • the name of the talk room is not limited, but is set to the name entered by the administrator as an example.
  • the name of the talk room is not limited, and may be, as an example, a name automatically given in the messaging service, or may be represented by the identification information of the talk room or the like.
  • the content Q1 is not limited, but is, as an example, the content input by the user A to the input unit 22 of the user terminal 20A.
  • the user terminal 20 is not limited, but as an example, the contents input to the input unit 22 of the own terminal are displayed side by side in the first direction with respect to the image T1 of the talk room.
  • the first direction is the vertical direction with respect to the image T1 of the talk room
  • the second direction intersecting with the first direction is the horizontal direction with respect to the image T1 of the talk room.
  • the content Q1 in the image T1 of the talk room of FIG. 2B is the content input by the own terminal (here, the user terminal 20A), and is arranged close to one side in the horizontal direction of the image T1 of the talk room. And arranged side by side in the vertical direction.
  • the reference numeral Tb is an icon for making settings related to remittance (not limited, but as an example, a remittance setting icon).
  • the remittance setting icon Tb is not limited, but as an example, multiple icons (as an example, not limited, "remittance setting”, “remittance”, “receipt setting”, “receipt cancellation”, “receipt change”, “disappearance condition”. , "Report”, “Refund”, “Remittance Request”, “Withdrawal” icon).
  • the input unit 22 When the input unit 22 receives an input for a predetermined icon included in the remittance setting icon Tb, the user terminal 20 displays an image corresponding to the icon in the display area 28.
  • the remittance setting icon Tb shown in FIG. 2A (c) is an example, and is not limited thereto.
  • the content Q2 and the content Q3 are transmitted from a terminal (here, the user terminal 20B or the user terminal 20C) different from the own terminal (here, the user terminal 20A).
  • a terminal different from the own terminal is appropriately referred to as another terminal.
  • the user terminal 20 displays the content transmitted from another terminal at a position different from the content transmitted from the own terminal in the second direction.
  • the content Q2 and the content Q3 in the image T7 of the talk room of FIG. 2B (h) are contents transmitted from another terminal (here, the user terminal 20B or the user terminal 20C), and are images of the talk room.
  • the image T4 of the talk room in FIG. 2B (e) is an image displayed in the display area 28 of the user terminal 20B, and the arrangement of the content Q1 in FIG. 2B (e) is the same as the content Q1 in FIG. 2A (b). By comparison, they are located at different positions in the second direction.
  • the user terminal 20 is not limited, but as an example, each content transmitted from another terminal and information about the user of the user terminal 20 who has transmitted this content are arranged in a set in the image of the talk room. ..
  • the information about the user includes, but is not limited to, by example at least one of the user's icon, the user's name, the user ID, and the display regarding the user's nickname.
  • the reference numerals Ua1, Ub1 and Uc1 are icons of the user A, the user B and the user C, respectively.
  • the reference numerals Ua2, Ub2, and Uc2 are the user names of the user A, the user B, and the user C, respectively.
  • the reference numeral Ub1 is an icon of the user of another terminal (here, the user terminal 20B) that has transmitted the content.
  • the user terminal 20A arranges the content Q2 and the icon Ub1 of the user (here, the user B) of the user terminal 20B who transmitted the content Q2 on the image T7 of the talk room so as to have a predetermined positional relationship.
  • the user terminal 20 is not limited, but as an example, it is assumed that the user terminal 20 can send and receive contents including a message and the like regardless of whether or not the remittance process is executed.
  • the information about the user may not include at least one of the user's icon, the user's name, the user ID, and the user's nickname, and may include the user's icon, the user's name, the user ID, and the user's nickname. It may contain information different from the display.
  • the user terminal 20 does not have to include the information about the user in the image of the talk room.
  • the user terminal 20 is not limited, but as an example, arranges the contents in each talk room in the first direction in the order of the transmission time, and displays the image of each talk room in the display area 28.
  • the content Q2 is the content transmitted after the content Q1
  • the content Q3 is the content transmitted after the content Q2
  • the content Q2 is the content of the talk room. It is arranged below the content Q1 in the vertical direction of the image T7.
  • the server 10 receives the remittance processing request from the user terminal 20, the server 10 stores the remittance processing request in the storage unit 15 as an example, not limited to the case.
  • the server 10 collates the user IDs of the remittance source and the remittance destination included in the remittance processing request with the talk room information D12, and identifies the remittance source and remittance destination users in the talk room.
  • the server 10 collates the remittance account included in the remittance processing request with the remittance account information D14, and identifies the remittance account for remittance, as an example but not a limitation.
  • the server 10 specifies the remittance amount included in the remittance processing request as an example, not a limitation.
  • the server 10 transmits remittance information for updating the value corresponding to the "remittance account ID" to the payment server 30 based on the specified remittance account and remittance amount.
  • the server 10 sets the user terminal 20 corresponding to the user ID of the remittance source and the remittance destination as the destination as a result of the process related to the remittance in the payment server 30, and the content indicating that the remittance is completed. Is transmitted (for example, delivered).
  • the server 10 updates the remittance history information D15 when transmitting the content.
  • the user terminal 20 receives the content transmitted by the server 10
  • the user terminal 20 transmits the reception notification to the server 10 as an example, not limited to the content.
  • the server 10 may delete the content associated with the reception notification from the content information D13, as an example without limitation.
  • FIG. 3A is a diagram showing an example of the talk room information D12.
  • the talk room information D12 is not limited, but as an example, [Talk room ID], [Name], [User ID], [Generator ID], [Remittance recipient ID], [Sender ID], and [Content list]. ] Items are included.
  • [Talk room ID] is an item including the identification information of the talk room.
  • the talk room ID is not limited, but is given in the messaging service when the user creates the talk room as an example.
  • [Name] is not a limitation but an item indicating the name of the talk room as an example.
  • the [name] is associated with the [talk room ID]. For example, the [name] of the talk room whose [talk room ID] is [tr01] is [coffee party]. Further, the [name] of the talk room whose [talk room ID] is [tr02] is [tea party]. Further, the [name] of the talk room whose [talk room ID] is [tr03] is [athletic meet].
  • [User ID] is not a limitation but, as an example, an item indicating identification information of a user included in a group corresponding to each talk room.
  • the [User ID] is associated with the [Talk Room ID].
  • the users included in the group corresponding to the talk room whose [talk room ID] is "tr01" are user A, user B, and user C, and the [user ID] corresponding to "tr01" is the user.
  • the user ID of A, the user ID of user B, and the user ID of user C are included.
  • the users included in the group corresponding to the talk room whose [talk room ID] is "tr02" or "tr03" are also user A, user B, and user C.
  • [Generator ID] is not a limitation, but is an item indicating identification information of the user who generated each talk room as an example.
  • the [Generator ID] is associated with the [Talk Room ID]. For example, the user who generated the talk room whose [talk room ID] is "tr01" is the user A, and the [creator ID] corresponding to "tr01" includes the user ID of the user A. Further, for example, the user who generated the talk rooms of "tr02"] and "tr03" is also user A.
  • [Remittance recipient ID] is not a limitation but an item indicating identification information of a user who can receive remittance in each talk room (as an example, not a limitation).
  • the [Remittance Recipient ID] is associated with the [Talk Room ID]. For example, in a talk room where the [talk room ID] is "tr01", the user who can receive the remittance is the user A, and the [remittance recipient ID] corresponding to the "tr01" includes the user ID of the user A. .. That is, in the talk room of "tr01", only the user A is set to receive the remittance.
  • the server 10 may automatically set the user ID of the administrator in [Remittance Recipient ID] when the talk room is generated, or based on the information set by the administrator. It may be set based on the information set by the participants at any time.
  • [Sender ID] is not a limitation but an item indicating identification information of a user who can remit in each talk room (as an example, not a limitation).
  • the [Sender ID] is associated with the [Talk Room ID]. For example, in a talk room where the [talk room ID] is "tr01", the users who can remit are the user B and the user C, and the [remittance sender ID] corresponding to the "tr01" is the user ID of the user B and the user C. including. That is, the talk room of "tr01" is set so that only user B and user C can remit money to user A. For example, in the talk room where [talk room ID] is "tr02", remittance is possible.
  • the users are the user A and the user C, and the [remittance ID] corresponding to "tr02" includes the user IDs of the user A and the user C.
  • the server 10 may automatically set the user ID set in the [sender ID] to the user ID of the participant when the user participates in the talk room. It may be set based on the information set by the administrator at an arbitrary timing, or may be set based on the information set by the participant at an arbitrary timing.
  • the talk room information D12 may not include the item of [remittance ID].
  • the server 10 may automatically set the user ID of the participant who participated in the talk room in [Remittance ID] as an example, not limited to it.
  • [Content list] is not a limitation, but is an item showing information indicating a list of contents included in each talk room as an example.
  • the [content list] is associated with the [talk room ID]. For example, the content included in the talk room whose [talk room ID] is "tr01" is represented by "List 1" which is a part of the content information D13.
  • FIG. 3B is a diagram showing an example of the content information D13.
  • FIG. 3B is a part of the content information D13 and corresponds to “List 1” in FIG. 3A.
  • the content information D13 includes, but is not limited to, the items of [content ID], [sending user ID], and [content] as an example.
  • [Content ID] is an item indicating the identification information of each content.
  • the content identification information is not limited, but is given in the messaging service when the user terminal 20 transmits the content, as an example.
  • the content whose [content ID] is "tr01c01” corresponds to the content Q1 in the image T1 of the talk room of FIG. 2A (b).
  • the content whose [content ID] is "tr01c02” corresponds to the content Q2
  • the content whose [content ID] is "tr01c03" corresponds to the content Q3.
  • [Sending user ID] is not limited, but is an item indicating a user ID corresponding to the user terminal 20 that has transmitted each content, as an example.
  • the [Sending User ID] is associated with the [Content ID]. For example, in the content whose [content ID] is "tr01c01", the user corresponding to the transmitting user terminal 20 is the user A, and the [sending user ID] corresponding to the "tr01c01” includes the user ID of the user A. In the content whose [content ID] is "tr01c02", the user corresponding to the transmitting user terminal 20 is the user B, and the [sending user ID] corresponding to "tr01c02" includes the user ID of the user B.
  • [Content] is not a limitation but an item indicating the content transmitted by the user as an example.
  • [Content] is associated with [Content ID]. If the content contains text, the text data of the content is stored in [Content].
  • the content Q1 shown in FIG. 2B is the text "It is 1,000 yen per person.”
  • the [Content] corresponding to "tr01c01” is the text indicating "It is 1,000 yen per person.” Data is stored.
  • the content Q2 and the content Q3 shown in FIG. 2 (f) are the texts “The remittance is completed.”, And "1,000 yen” is added to the [Content] corresponding to "tr01c02" and "tr01c03".
  • Text data indicating "Remittance has been sent" is stored.
  • the [content] stores the image data, the link to the image data, or the address of the storage unit in which the image data is stored.
  • the image data is not limited, and may include still image data or moving image data as an example.
  • the image data may or may not include data representing stamps, stickers, pictograms, and emoticons, as an example without limitation.
  • the [content] stores the audio data, a link to the audio data, or the address of the storage unit in which the audio data is stored.
  • FIG. 3C is a diagram showing an example of the remittance account information D14.
  • the remittance account information D14 includes, but is not limited to, the items of [user ID] and [remittance account ID] as an example.
  • [User ID] is not a limitation but an item indicating user identification information as an example.
  • [Remittance account ID] is not a limitation, but is an item indicating identification information of each remittance account as an example.
  • the [Remittance Account ID] is associated with the [User ID].
  • the remittance accounts that can be used by the user whose [user ID] is "user A" are the remittance account A, the remittance account B, and the remittance account C, and the remittance accounts of the remittance account A, the remittance account B, and the remittance account C. Includes ID.
  • FIG. 3D is a diagram showing an example of remittance history information D15.
  • the remittance history information D15 includes, but is not limited to, the items of [talk room ID], [date and time], [remittance recipient ID], [remittance sender ID], [remittance amount], and [remittance account].
  • the [Talk Room ID], [Remittance Recipient ID], and [Remittance Sender ID] are not limited to each other, and are the same as those described in FIG. 3A as an example, and thus the description thereof will be omitted.
  • [Date and time] is an item indicating the date and time when the talk room ID is assigned.
  • [Remittance amount] is an item indicating information indicating the amount of value remitted by the user.
  • [Transfer amount] is associated with [Talk room ID]. That is, in the talk room tr01 of FIG. 3D, the value of "1,000” is remitted from User B to User A at "10:00 on January 1, 2020", and “11:00 on January 1, 2020”. At “00 minutes”, the value of "1,000” is remitted from user C to user A.
  • the user terminal 20 displays the image of the talk room in the display area 28 with reference to the talk room information D22 and the content information D23 shown in FIG. 1 as an example without limitation.
  • the user terminal 20 receives input to the input unit 22 by the user, and refers to the talk room information D22 and the remittance account information D24, and relates to the remittance source, the remittance destination, the remittance amount, and the remittance account.
  • a remittance processing request including information is transmitted to the server 10.
  • the user terminal 20 receives remittance history information from the server 10 as an example, not limited to it.
  • the user terminal 20 stores the received remittance history information in the storage unit 25 as an example, not a limitation.
  • the user terminal 20 may refer to the remittance history information D25 and display an image of the talk room including the content indicating that the remittance process is completed in the display area 28.
  • the user terminal 20 does not have to store the remittance account information D24 and the remittance history information D25 in the storage unit 25 as an example without limitation.
  • the talk room information D22 is not limited to information about the talk room associated with the user of the user terminal 20 as an example. Since the items included in the talk room information D22 are the same as those in the talk room information D12, the description thereof will be omitted.
  • the content information D23 is not limited, but is, as an example, information about the content in the talk room associated with the user of the user terminal 20. Since the items included in the content information D23 are the same as those of the content information D13, the description thereof will be omitted.
  • the remittance account information D24 is not limited but, as an example, information regarding the remittance account associated with the user of the user terminal 20. Since the items included in the remittance account information D24 are the same as those in the remittance account information D14, the description thereof will be omitted.
  • the remittance history information D25 is not limited but, as an example, information regarding remittance in the talk room associated with the user of the user terminal 20. Since the items included in the remittance history information D25 are the same as those of the remittance history information D15, the description thereof will be omitted.
  • the payment server 30 When the payment server 30 receives the remittance information from the server 10, the payment server 30 stores the remittance information in the storage unit 35 as an example, not limited to the case.
  • the payment server 30 specifies, as an example, not a limitation, the remittance account IDs of the remittance source and the remittance destination included in the remittance information.
  • the payment server 30 refers to the remittance account information D31 as an example, and is not limited to the value corresponding to the remittance account ID of the remittance source, the value corresponding to the remittance amount, and the value corresponding to the remittance account ID of the remittance destination. (As an example, not limited to remittance processing).
  • the payment server 30 sends a notification regarding the result of the remittance processing to the server 10 as an example, but not a limitation.
  • the remittance account information D31 is, but not limited to, information about the remittance account associated with the user of the user terminal 20 as an example.
  • FIG. 4 is a diagram showing an example of the remittance account information D31.
  • the remittance account information D31 includes, but is not limited to, the items of [user ID], [remittance account ID], and [value] as an example. Since the [user ID] and the [remittance account ID] are the same as the [user ID] and the [remittance account ID] of the remittance account information D14, the description thereof will be omitted.
  • [Value] is not a limitation but an item indicating the amount of value as an example. [Value] is associated with [Remittance Account ID].
  • the server 10 is not limited to, and when the talk room is generated by the manager, the user ID of the manager is associated with the talk room ID as shown in the talk room information D12 of FIG. 3A, and the [user ID] is used. ] And [Producer ID] items.
  • the server 10 receives the participation request from the participant, the server 10 registers the user ID of the participant in the item of [user ID] in relation to the talk room ID, as in the talk room information D12. Then, the server 10 sets the remittance as an example, not a limitation.
  • the setting regarding remittance is not limited to, but as an example, the user IDs of the administrator and the participants are set in the items of [Remittance recipient ID] or [Sender ID].
  • the server 10 may set the remittance setting based on the information on the predetermined setting, or may set the remittance setting based on the information set by the administrator or the participant. It may be set.
  • FIG. 5 is a flowchart showing an information processing procedure according to the first embodiment.
  • the procedure from the generation of the talk room by the manager to the completion of the remittance to the manager by the participants is shown as an example, not a limitation.
  • the administrator is referred to as user A
  • the participants are referred to as user B and user C
  • the talk room in which user A, user B, and user C participate is referred to as a "coffee party".
  • step S111 the user terminal 20A generates a request for creating the talk room A for the server 10 based on the input to the input unit 22 by the user A.
  • step S112 the user terminal 20A transmits a creation request to the server 10 via the communication I / F24.
  • the server 10 receives the creation request from the user terminal 20A via the communication I / F14.
  • step S121 the server 10 registers the talk room ID, the user ID, and the generator ID in the talk room information D12 based on the creation request (see FIG. 3A). As an example, the server 10 transmits the talk room information D12 to the user terminal 20A when the talk room is registered in the talk room information D12.
  • the user terminal 20A stores the talk room information D12 (see FIG. 3A) in the storage unit 25 as an example, not a limitation.
  • the user terminal 20A reads the talk room information D22 as an example, but is not limited to it, and generates an image TL of a list of talk rooms.
  • the control unit 21 of the user terminal 20A controls the display unit 23a to display the image TL in the display area 28.
  • the input unit 22 inputs an input to the icon of the talk room "coffee party”
  • the user terminal 20A determines that the talk room "coffee party” is selected, and determines that the talk room "coffee party” is selected.
  • the image is displayed in the display area 28.
  • the server 10 may send a participation request for participating in the talk room "coffee party" to the user terminal 20 as an example without limitation.
  • step S131 the user terminal 20B displays the image TL of the talk room list as shown in FIG. 2A in the display area 28 when the application of the messaging service is started, as an example, not limited to the user terminal 20B. Display.
  • the input unit 22 receives an input for the "coffee party" icon in the list
  • the user terminal 20B determines that the talk room "coffee party” is selected.
  • the user terminal 20B generates a participation request for requesting the server 10 to participate in the talk room "coffee party” when it is determined that the "coffee party” is selected.
  • step S132 the user terminal 20B transmits a request for participation in the talk room "coffee party" to the server 10 via the communication I / F24.
  • step S131 and step S132 are similarly executed in the user terminal 20C.
  • the server 10 stores the participation request in the storage unit 15.
  • the server 10 registers the user ID of the user B in the talk room information D12 based on the participation request (see FIG. 3A).
  • the user terminal 20B receives the content information D13 from the server 10 and the content as shown in FIG. 2B.
  • the image T1 including Q1 may be displayed in the display area 28.
  • the server 10 transmits, as an example, not a limitation, a participation request for joining the talk room to the user terminal 20 (here, the user terminal 20B and the user terminal 20C). May be good.
  • the user terminal 20 may, for example, display an image including a message text requesting participation in the talk room "coffee party" in the display area 28 when the participation request is received from the server 10. Then, the image T4 as shown in FIG. 2E showing the state of participating in the talk room may be displayed in the display area 28.
  • step S133 the server 10 transmits the talk room information D12 (here, the participation information) in which the user IDs of the participants are registered to the user terminal 20A, as an example, not limited.
  • the user terminal 20A stores the participation information in the storage unit 25 as an example, not a limitation.
  • step S141 the user terminal 20A displays the image T2 of the talk room including the content Q1 as shown in FIG. 2A (b) in the display area 28 as an example, not limited to it.
  • the user terminal 20A determines that the icon PL has been selected when there is an input to the icon PL of the display area 28 with respect to the icon PL of the display area 28, as shown in FIG. 2A (c).
  • the selected image T2 including the remittance setting icon Tb is displayed in the display area 28.
  • the user terminal 20A determines that the "remittance setting" is selected when the input unit 22 receives an input for the icon "remittance setting" in FIG. 2A (c).
  • the user terminal 20A displays the remittance setting image T3 shown in FIG. 2A (d) in the display area 28 with reference to the talk room information D22 as an example, not the limitation.
  • the remittance setting image T3 includes, but is not limited to, a remittance recipient setting unit T3a, a remittance sender setting unit T3b, and a setting confirmation unit T3c.
  • the remittance recipient setting unit T3a sets, as an example, not a limitation, a user who is a remittance recipient, which displays the name of the user of the user ID associated with the talk room "coffee party" based on the talk room information D22. It is an area to do.
  • the remittance person setting unit T3b is not limited to, but as an example, in order to set a user who becomes a remittance person, which displays the name of the user of the user ID associated with the talk room "coffee party" based on the talk room information D22. Area of.
  • the remittance recipient setting unit T3a and the remittance sender setting unit T3b are not limited, but as an example, when an input is made to the input unit 22, the remittance recipient setting unit T3a is in a predetermined display format (pull-down as an example, not limited). The name of the user may be displayed.
  • the remittance recipient setting unit T3a and the remittance sender setting unit T3b are not limited, and may be, for example, a text box or the like that accepts the input of the user's name.
  • the setting confirmation unit T3c is not a limitation but an example, and when an input is made to the input unit 22, the information regarding the above remittance setting (the first setting as an example, not the limitation) (as an example, not the limitation). First setting information) is confirmed. Then, in step S142, the user terminal 20A transmits the first setting information to the server 10.
  • the manager who generated the talk room here, user A
  • the present invention is not limited to this.
  • the first setting information may be generated by a participant (here, user B or user C) of the generated talk room.
  • the server 10 has been described as setting the first setting in step S141, but the present invention is not limited to this.
  • the server 10 may set the first setting automatically when the creation request is received from the user terminal 20A in step S121 or based on the setting information generated by the administrator.
  • the first setting may be set automatically when the participation request is received from the user terminal 20 in step S131 or based on the setting information generated by the administrator, and the timing at which the first setting is set is not limited. ..
  • the first setting is not limited, but may be set automatically by the server 10 or may be set by the user as described above.
  • the “setting” is not limited to, but may be, for example, granting authority, authority, or responsibility regarding remittance to at least one user ID of the administrator or a participant.
  • the server 10 is not limited, but as an example, when the talk room is created by the administrator, the administrator's user ID is set to [Remittance Recipient ID].
  • the user ID of the participant may be registered in the [sender ID] when the participation request is received from the participant.
  • the talk room ID of FIG. 3A is "tr01”
  • the user ID of the administrator is registered in the [remittance recipient ID]
  • the user ID of the participant is registered in the [remittance sender ID].
  • the first setting is a setting in which remittance cannot be sent from the user who participates in the talk room to the participant.
  • the server 10 is not limited, but as an example, the user ID of one of the participants is registered in the [Remittance Recipient ID] as the talk room ID in FIG. 3A is "tr02", and [ The user IDs of the administrator and other participants may be registered in [Remittance ID]. This allows the manager and other participants to transfer money to one of the participants in the talk room. As an example, not a limitation, as the talk room ID in FIG.
  • 3A is "tr03", the user ID of the administrator is registered in the [remittance recipient ID], and a specific participant among the participants is registered in the [remittance ID]. User ID may be registered. As a result, it is possible to transfer money from only a specific participant to the manager in the talk room.
  • step S151 the server 10 registers the user ID in the [remittance recipient ID] and the [remittance sender ID] of the talk room information D12 based on the first setting information, not as a limitation.
  • step S161 the user terminal 20B displays the image T4 of the talk room including the content Q1 as shown in FIG. 2B (e) in the display area 28 as an example without limitation.
  • the user terminal 20B determines that the icon PL has been selected when there is an input to the icon PL of the display area 28 with respect to the icon PL of the display area 28, and the remittance setting shown in FIG. 2B (f).
  • the selected image T5 including the icon Tb is displayed in the display area 28.
  • the user terminal 20B receives an input in the input unit 22 with respect to the icon “remittance” in FIG.
  • the remittance registration image T6 includes, but is not limited to, a remittance destination T61, a remittance account setting unit T62, a remittance possible amount T63, a remittance amount input unit T64, and a remittance confirmation unit T65.
  • the remittance destination T61 is not limited, but is an area for displaying the remittance destination specified by referring to the talk room information D22 as an example.
  • the remittance account setting unit T62 is not limited, but as an example, when an input is made to the input unit 22, the remittance corresponding to the remittance account ID that can be used in a predetermined display format (pull-down as an example, not limited). This area displays the name of the account.
  • the remittance account setting unit T62 is not limited, and may be, for example, a text box that accepts and displays the input of the name of the remittance account by the user.
  • the remittanceable amount T63 is, but is not limited to, an area for displaying the remaining amount of remittanceable value in the selected remittance account.
  • the remittance amount input unit T64 is not limited, but as an example, is an area for displaying the input remittance amount when an input is made to the input unit 22.
  • the remittance confirmation unit T65 is not a limitation but an example, and when an input is made to the input unit 22, the remittance confirmation unit T65 confirms the above information regarding the remittance (as an example, not a limitation). Then, in step S162, the user terminal 20B transmits a remittance processing request including remittance information to the server 10.
  • the remittance processing request is not limited, but is, as an example, information for requesting the server 10 to process the remittance user B to remit to the user A who receives the remittance.
  • step S161 and step S162 are similarly executed in the user terminal 20C.
  • step S171 the server 10 stores the remittance processing request in the storage unit 15.
  • the server 10 collates the user ID of the user B with the user ID of the [sender ID] of the talk room information D12 based on the remittance processing request, but not as a limitation.
  • the control unit 11 shifts to the remittance process when the user ID of the user B and the user ID of the [sender ID] match as a result of collation.
  • the control unit 11 specifies, as an example, not a limitation, a user ID of a remittance source and a remittance destination, a remittance account, and a remittance amount based on the remittance information.
  • the server 10 transmits a remittance notification including information on the user ID of the remittance source and the remittance destination, the remittance account, and the remittance amount to the payment server 30.
  • the payment server 30 transfers the value corresponding to the remittance amount from the value of the remittance account corresponding to the user ID of the remittance source to the value of the remittance account corresponding to the user ID of the remittance destination.
  • the payment server 30 sends information about the result of processing related to remittance to the server 10 as an example, but not by limitation. This completes the remittance process.
  • step S172 the server 10 transmits a remittance completion notification including information on the remittance amount to the user terminal 20.
  • the user terminal 20A sent content Q2 and content Q3 (not limited but as an example, 1,000 yen) indicating the completion of remittance as shown in FIG. 2B (h) based on the remittance completion notification as an example, not limited. ) Is displayed.
  • the user terminal 20B and the user terminal 20C also display the image including the content Q2 and the content Q3 in the same manner. As a result, the user of the talk room can check the remittance status in the talk room. ⁇ First modification>
  • FIG. 6 is a diagram showing an example of the relationship information D16.
  • the information processing according to the first modification is a form in which each of the talk room manager and the participant can remit money to another user in the talk room without having a predetermined relationship in the messaging service. ..
  • the "predetermined relationship” is not limited to, but as an example, refers to a relationship that can be recognized by each other among users in a messaging service. For example, a given relationship is a friend relationship, a relationship being followed, a relationship to be followed, and the like.
  • the server 10 may have the relationship information D16 indicating the above-mentioned relationship between the users, as an example without limitation.
  • the relationship information D16 includes, but is not limited to, at least one of the items of [user ID], [friend relationship], [follow 1], and [follow 2].
  • the relationship information D16 may further include an item indicating a mutually recognizable relationship between users.
  • [Friend relationship] is an item indicating a user ID having a friend relationship with a certain user.
  • [Friend relationship] is associated with [User ID].
  • the "friend relationship" is not limited to, but as an example, in a messaging service, a relationship having information that can identify each other. Specifically, as an example, not limited to, the telephone number corresponding to the user terminal 20A of a certain user (here, user A) is contacted by the user terminal 20B of another user (here, user B). When registered as a destination, the user A and the user B are in a "friendship relationship". Further, as an example, not limited to, when the messaging account corresponding to the user B is registered in the user terminal 20A of the user A, the user A and the user B have a "friendship".
  • the user B and the user A have a "friendship".
  • the user B and the user A have a "friendship”.
  • the messaging account corresponding to the user terminal 20B of the user B registered in the user terminal 20A of the user A is also registered in the user terminal 20C of the user C, the user A and the user C is a "friendship".
  • the relationship between the user A and the user C who have the user D as a common friend.
  • [Follow 1] is an item indicating the user ID of a user who has a relationship of being followed by a certain user.
  • [Follow 1] is associated with [User ID].
  • the “followed relationship” is not limited to, but as an example, in a messaging service, an account containing content provided by a user terminal 20 of another user (here, user B) is used by a user (here, a user).
  • A) Refers to the relationship between user A and user B registered by the user terminal 20. In this case, the relationship between the user A and the user B is a relationship in which the user B is followed by the user A.
  • the user terminal 20A of the user A is an account registration unit displayed in the display area 28 in the content on the messaging service related to the user B (as an example, not the limitation, "follow"”. )
  • the input unit 22 receives an input
  • the information regarding the account registration is transmitted to the server 10.
  • the server 10 registers the relationship in which the user A is followed by the user B by updating the relationship information D16 based on the information regarding the registration of the account.
  • [Follow 2] is an item indicating a user ID of a user who has a relationship of following a certain user.
  • [Follow 2] is associated with [User ID].
  • the “following relationship” is not limited, but as an example, in a messaging service, a user terminal 20 of another user (here, user B) is provided by a user terminal 20 of a certain user (here, user A). It refers to the relationship between user B and user A who has registered an account containing content. In this case, the relationship between the user B and the user A is a relationship in which the user B follows the user A.
  • the user terminal 20B of the user B is an account registration unit (not limited but, as an example, "following"" displayed in the display area 28 in the content on the messaging service related to the user A. ),
  • the input unit 22 receives an input
  • the information regarding the account registration is transmitted to the server 10.
  • the server 10 registers the relationship in which the user B follows the user A by updating the relationship information D16 based on the information regarding the registration of the account.
  • FIG. 7 is a diagram showing an image T8 of a talk room on which a display relating to a predetermined relationship setting is displayed.
  • the information processing according to the second modification is not limited, but as an example, as shown in FIG. 7, at least one of a friend relationship, a follow relationship, and a follow relationship is set in the image of the talk room. It is a form including a display for (here, "add friend").
  • the input unit 22 receives an input for the "add friend” icon T81
  • the control unit 21 determines that "add friend” is selected, and displays an image for setting a friend relationship 28. Display on.
  • a display for setting at least one of a friend relationship, a follow relationship, and a follow relationship in the image of the talk room here, "" It does not have to include "add friend”
  • a display for setting at least one of a friend relationship, a follow relationship, and a follow relationship in the image of the talk room here, "" It does not have to include "add friend”
  • By eliminating the display regarding the setting of a predetermined relationship it is possible to eliminate the establishment of friend relationships, follow-up relationships, and follow-up relationships among users in the talk room.
  • FIG. 8 is a diagram showing an example of the remittance setting image T9.
  • the information processing according to the third modification is not limited, but as an example, the remittance destination T61 of the remittance registration image T6 in FIG. 2 (g) is displayed so that the remittance destination can be selected.
  • the input unit 22 receives an input for the icon of the remittance destination T91 (here, ⁇ )
  • the user terminal 20 determines that the icon of the remittance destination T91 is selected.
  • the control unit 21 displays a list showing the candidates of the remittance destination in the display area 28 as shown in FIG.
  • the control unit 21 may refer to the talk room information D22, arrange the user names corresponding to the user IDs associated with the talk room ID, and display a list of remittance destination candidates.
  • the server 10 transmits the content transmitted by the user A to the input unit 22 of the user terminal 20A to the user terminal 20B, and the user B inputs the content to the input unit 22 of the user terminal 20B.
  • the content transmitted by is transmitted to the user terminal 20A.
  • the control unit 11 sets the talk room with settings related to remittance to user A (settings for receiving remittance, settings for remittance, etc.).
  • the server 10 has information on remittance from user B to user A based on settings related to remittance from user terminal 20B and input by user B to the input unit 22 of user terminal 20B for the talk room (remittance destination, remittance source, Receive remittance amount, remittance account, etc.).
  • the control unit 11 executes a process related to remittance (remittance process) based on the information related to remittance.
  • the processing speed of the server 10 is reduced because it is not necessary to determine the setting related to the remittance for each user in the server 10 when the remittance process is executed as an example. Can be improved. Further, since the user who uses the talk room can transfer money in the talk room, the convenience of the user can be improved.
  • the remittance setting set by the control unit 11 includes the setting that the user A is the manager of the talk room (the person who created the talk room, etc.).
  • the setting related to the remittance is set for the administrator as an example, not limited to the above, and the setting related to the remittance by the user A can be reduced. The amount can be reduced. Further, since the amount of information transmitted from the user terminal 20 to the server 10 can be reduced, the processing speed of the server 10 can be improved.
  • the control unit 11 sets the settings related to remittance based on the creation of the talk room by the user A.
  • the setting related to remittance is set when the talk room is created, so that the server 10 communicates with the user terminal 20 regarding the setting related to remittance. Since the amount can be reduced, the processing speed of the server 10 can be improved.
  • the remittance-related settings set by the control unit 11 enable remittance to the user A based on the input to the input unit 22 of the user terminal 20 by the user participating in the talk room. Includes settings for things.
  • the convenience of the talk room can be improved because a user who can send money in the talk room can be set as an example, not limited to the information processing.
  • the remittance setting set by the control unit 11 includes the setting that the user who participates in the talk room cannot remit to the user B who is a participant.
  • the process for specifying the remittance destination on the server 10 can be reduced by setting so that the remittance can be performed only to a specific user, not as a limitation but as an example. Therefore, the processing speed of the server 10 can be improved.
  • the rules regarding remittance can be determined in the talk room, it is possible to prevent the user from misusing the talk room.
  • the server 10 stores the relationship between the user A and a user different from the user A in the storage unit 15.
  • User A and User B do not have at least one of a friendship, a relationship in which User A is followed by User B, and a relationship in which User A follows User B.
  • the user can participate in the talk room even if there is no specific relationship, so that the process for approval by the server 10 is required. Can be reduced, so that the processing speed of the server 10 can be improved. Further, since the user can participate in the talk room without considering the relationship with other users, the convenience of the talk room can be improved.
  • the server 10 does not include the display regarding the setting of the friend relationship, the follow relationship, and the follow relationship in the image of the talk room.
  • the amount of processing and the processing items in the server 10 can be reduced so that the user participating in the talk room does not establish a predetermined relationship with another user, as an example, not limited to the present invention. Therefore, the processing speed of the server 10 can be improved.
  • This embodiment is not limited to, but as an example, a user who can receive remittance in the talk room can set a setting that allows other users to receive remittance.
  • the setting that allows remittances to be received in the talk room is referred to as "remittance receipt setting”.
  • a setting that allows remittance in a talk room (a remittance setting as an example, not a limitation) is set, and a user who has a remittance receiving setting set remittance setting to another user. May include a configurable form.
  • the remittance receiving setting will be set for the participant by the administrator who has the remittance receiving setting as an example, not the limitation.
  • the administrator user terminal 20 specifies, as an example, not a limitation, one of the participants, and information regarding the setting of the remittance receipt setting (not the limitation, as an example, the remittance setting information) or the remittance. At least one of the information related to the setting of the setting (not limited, but as an example, the remittance setting information) is transmitted to the server 10. Based on this information, the server 10 sets at least one of the remittance receiving setting and the remittance setting in the user ID of any of the participants.
  • the contents described in this embodiment can be appropriately applied to each of the other embodiments.
  • FIG. 9 is a flowchart showing information processing according to the second embodiment.
  • FIG. 10 is a diagram showing an outline of information processing according to the second embodiment.
  • FIG. 11 is a diagram showing an example of the talk room information D12.
  • FIG. 12 is a diagram showing an example of the image T8 including the content indicating the completion of the setting.
  • the same components as those in the above-described embodiment are appropriately designated with the same reference numerals, and the description thereof will be omitted or simplified.
  • FIG. 9 is a flowchart on the premise that the procedures S111 to S141 in FIG. 2 have been completed.
  • the remittance receipt setting is set in the user ID of the administrator (here, user A).
  • the user A a procedure for the user A to set the remittance receiving setting for the user ID of the user B via the user terminal 20A will be described.
  • the user terminal 20A is not limited to the icon PL of the display area 28 shown in FIG. 2A (b), and the icon PL is selected when the input unit 22 receives an input.
  • the selected image T6 including the remittance setting icon Tb as shown in FIG. 10A is displayed in the display area 28.
  • the control unit 21 determines that the "receipt setting" is selected when the input unit 22 receives an input for the icon "receipt setting”.
  • the control unit 21 displays the reception setting image T7 of FIG. 10B in the display area 28 with reference to the talk room information D22, not as a limitation but as an example.
  • the 10B includes, as an example, not a limitation, a remittance recipient setting unit T71 for displaying the name of the user corresponding to the user ID associated with the talk room, and a setting confirmation unit T72. ..
  • the remittance recipient setting unit T71 may display the user's name in a predetermined display format (pull-down as an example, not a limitation) when an input is made to the input unit 22 as an example, not a limitation. ..
  • the remittance recipient setting unit T71 is not limited, but may be, for example, a text box or the like that accepts the input of the user's name.
  • the remittance recipient setting unit T71 may include, as an example, not a limitation, a check box displayed so as to correspond to each of the names of a plurality of users.
  • the control unit 21 determines the receiving setting information when the input unit 22 receives an input to the setting confirmation unit T72 displayed in the display area 28.
  • the user terminal 20A transmits a receipt setting request including the receipt setting information to the server 10.
  • the server 10 stores the receipt setting request in the storage unit 15.
  • the server 10 collates the user ID of the user A with the user ID of the [remittance recipient ID] of the talk room information D12 shown in FIG. 3A based on the receipt setting request. That is, the control unit 11 confirms that the remittance setting request has been transmitted from the user terminal 20 of the user for which the remittance receiving setting is set, as an example, not limited.
  • the control unit 11 updates the talk room information D12 when the user ID of the user A and the user ID of the [remittance recipient ID] match as a result of collation as an example, not the limitation (as an example, not the limitation). Receipt setting process). Specifically, as an example, not limited to, the control unit 11 compares the talk room information D12 shown in FIG. 3A to the [remittance recipient ID] of the user B as in the talk room information D12 shown in FIG. Register the user ID.
  • step S231 the server 10 transmits a setting completion notification including the updated talk room information D12 to each user terminal 20.
  • the user terminal 20A displays the image T8 including the content Q4 indicating the setting completion as shown in FIG. 12 (the remittance receiving setting is set to the user B as an example, not the limitation).
  • the user terminal 20B and the user terminal 20C also display the image including the content Q4 in the same manner.
  • the server 10 may or may not send the setting completion notification to each user terminal 20 as an example, not limited to the server 10. Further, the server 10 may transmit the setting completion notification only to the user terminal 20 of the user for which the remittance receiving setting is set, as an example, not limited to the server 10. In this case, the user terminal 20 that has received the setting completion notification may display an image including a message indicating the setting completion in the display area 28.
  • control unit 11 has been described so as to register the user ID of the user B in the [remittance recipient ID] (receipt change processing) as in the talk room information D12 shown in FIG. Not limited.
  • the control unit 11 may execute to set the user ID of the user B in addition to the user ID of the user A for which the remittance receiving setting is set in the [remittance recipient ID]. .. In this case, the user ID of the user A and the user ID of the user B are registered in the [remittance recipient ID].
  • the user terminal 20A displays an image including content indicating the completion of the setting (a new remittance receipt setting is set for the user B as an example, not a limitation) based on the setting completion notification. It may or may not be displayed.
  • the administrator who has set the remittance receiving setting has explained that the participant is set to set the remittance receiving setting, but the present invention is not limited to this.
  • the control unit 11 may, as an example, not limited to, execute so that a participant who has set the remittance receiving setting sets the remittance receiving setting to another participant. ⁇ Fourth modification>
  • FIG. 13 is a diagram showing an outline of information processing according to the fourth modification.
  • FIG. 14 is a diagram showing an example of the talk room information D12 according to the fourth modification.
  • the information processing according to the fourth modification is a form in which the user participating in the talk room executes a process of canceling the remittance receiving setting of the user for which the remittance receiving setting is set.
  • "cancelling the remittance receipt setting" is not limited to, but as an example, means deleting the user ID from the [remittance recipient ID] in the talk room information D12 on the server 10, that is, receiving the remittance. It means to make it impossible to do.
  • the remittance receiving setting is set to the user ID of the administrator (here, user A), and the user A cancels the remittance receiving setting set for himself / herself via the user terminal 20A. The procedure will be described.
  • the user terminal 20A determines that the icon PL has been selected when the input unit 22 receives an input to the icon PL of the display area 28 shown in FIG. 2A (b), not as a limitation.
  • the selected image T9 including the remittance setting icon Tb as shown in FIG. 13A is displayed in the display area 28.
  • the control unit 21 determines that "cancellation of receipt" is selected when the input unit 22 receives an input for the icon "cancellation of receipt”.
  • the control unit 21 displays the receipt release image T10 of FIG. 13B in the display area 28 with reference to the talk room information D22, not as a limitation but as an example.
  • the receipt cancellation image T10 includes, as an example, not limited to, a remittance recipient cancellation unit T101 displaying the name of a user for which the remittance receipt setting is set in the talk room, and a cancellation confirmation unit T102.
  • the remittance recipient release unit T101 may display the user's name in a predetermined display format (pull-down as an example, not a limitation) when an input is made to the input unit 22 as an example, not a limitation. ..
  • the remittance recipient release unit T101 is not limited, but may be, for example, a text box or the like that accepts the input of the user's name.
  • the remittance recipient setting unit T101 may include, as an example, not a limitation, a check box displayed so as to correspond to each of the names of a plurality of users.
  • the control unit 21 determines the receipt cancellation information for the release confirmation unit T102 when the input unit 22 receives an input. Then, the user terminal 20A transmits a receipt cancellation request including the receipt cancellation information to the server 10.
  • the server 10 stores the receipt cancellation request in the storage unit 15.
  • the server 10 collates the user ID of the user A with the user ID of the [remittance recipient ID] of the talk room information D12 based on the receipt cancellation request as an example, not the limitation. That is, the control unit 11 confirms that the receipt cancellation request has been transmitted from the user terminal 20 of the user for which the remittance receipt setting is set, as an example, not limited.
  • the control unit 11 updates the talk room information D12 when the user ID of the user A and the user ID of the [remittance recipient ID] match as a result of collation as an example, not the limitation (as an example, not the limitation). Receipt cancellation process). Specifically, as an example, not limited to, the control unit 11 is compared with the talk room information D12 shown in FIG. 3A by the user A from the [remittance recipient ID] as in the talk room information D12 shown in FIG. Will be deleted.
  • the process may be executed so that the remittance receipt setting is canceled by the participant.
  • the server 10 cancels the remittance receipt setting of the predetermined user based on the receipt cancellation request received from the user terminal 20 of the participant as an example, not limited to.
  • the server 10 transmits a cancellation completion notification including the updated talk room information D2 to each user terminal 20.
  • the user terminal 20A causes the display area 28 to display an image including content indicating the completion of cancellation (as an example, not limited to the message "The remittance receipt setting has been canceled from user A").
  • the user terminal 20B and the user terminal 20C also display an image including the above contents in the same manner.
  • FIG. 15 is a diagram showing an outline of information processing according to the fifth modification.
  • FIG. 16 is a diagram showing an example of the image T13 including the content related to the receipt change.
  • the information processing according to the fifth modification is a process in which a user whose remittance receipt setting is set in the talk room causes another user to change the setting of his / her own remittance receipt setting (not limited, but as an example, a receipt change process). It is a form to execute. Then, the server 10 executes a process of transferring the value corresponding to the amount of money received by a certain user from a certain user to another user (as an example, not a limitation). ..
  • a procedure will be described in which the user A to which the remittance receiving setting is set causes the user B to change the setting of his / her own remittance receiving setting via the user terminal 20A.
  • the user terminal 20 of the receiving user determines that the icon PL has been selected when there is an input to the input unit 22 with respect to the icon PL of the display area 28 shown in FIG. 2A (b), as an example without limitation. Then, the selected image T11 including the remittance setting icon Tb as shown in FIG. 15A is displayed in the display area 28. Then, as an example, not a limitation, the control unit 21 determines that the "receipt change" is selected when the input unit 22 receives an input for the icon "receipt change". Then, the control unit 21 displays the receipt change image T12 of FIG. 15B in the display area 28 with reference to the talk room information D22, not as a limitation but as an example.
  • the receipt change image T12 is not limited, but as an example, the change source setting unit T121 indicating the change source of the remittance receipt setting, the change destination setting unit T122 indicating the change destination of the remittance receipt setting, and the change completion unit for confirming the setting change. Includes T123.
  • the control unit 21 refers to the talk room information D22 as an example, not a limitation, and causes the change source setting unit T121 to display an icon with the name of the user for which the remittance receiving setting is set.
  • the control unit 21 refers to the talk room information D22 as an example, and is not limited to it, and displays an icon with the name of the user to whom the remittance receiving setting is changed can be selected and displayed on the change destination selection unit T122.
  • the change destination setting unit T122 may display the user's name in a predetermined display format (pull-down as an example, not a limitation) when an input is made to the input unit 22 as an example rather than a limitation.
  • the change destination setting unit T122 is not limited, but may be, for example, a text box or the like that accepts the input of the user's name.
  • the user terminal 20A is not limited, but as an example, it is assumed that "user B" is set in the change destination setting unit T122.
  • the control unit 21 determines the setting change information for the change completion unit T123 when the input unit 22 receives an input.
  • the user terminal 20A transmits a setting change request including the setting change information to the server 10.
  • the server 10 stores the setting change request in the storage unit 15.
  • the server 10 collates the user ID of the change source user A with the user ID of the [remittance recipient ID] of the talk room information D12 based on the setting change request as an example, not the limitation.
  • the control unit 11 executes a receipt change process for updating the talk room information D12 when the user ID of the user A and the user ID of the [remittance recipient ID] match as a result of collation.
  • the control unit 11 refers to the remittance history information D15 as shown in FIG. 3D as an example, not limited to the information regarding the remittance related to the user ID of the user A until the receipt change process is completed. To identify. Specifically, as an example, not limited to, when the receipt change process is completed at 11:01 on January 1, 2020, the control unit 11 refers to the remittance history information D15 and January 1, 2020.
  • the user ID (here, user B) sent at 10:00 and the user ID (here, user C) sent at 11:00 on January 1, 2020 are "1,". 000 "is specified.
  • control unit 11 refers to the remittance account information D14, and allocates the value indicating the total of the specified remittances to the value corresponding to the remittance account associated with the user ID set in the change destination. Therefore, the value transfer process for updating the remittance account information D31 of the payment server 30 corresponding to the remittance account is executed.
  • the server 10 receives the updated remittance account information D31 from the payment server 30 as an example, not limited to it.
  • the server 10 transmits, as an example, not limited to, a setting change notification including the remittance account information D31 to the user terminal 20.
  • the user terminal 20A Based on the setting change notification, the user terminal 20A relates to the content Q5 indicating the completion of the setting change as shown in FIG.
  • the image T13 including the content Q6 indicating the content of the remittance (as an example, not limited to the remittance of 2,000 yen to the user B) is displayed in the display area 28.
  • the user terminal 20B and the user terminal 20C also display the image including the content Q5 and the content Q6 in the display area 28.
  • the value associated with the user ID of the user A until the receipt change process is completed is the value associated with the change destination user B.
  • the control unit 11 allocates only the value corresponding to the remittance process to the user A executed after the receipt change process is completed to the value associated with the user B to be changed.
  • the value transfer process for updating the remittance account information D31 of the payment server 30 may be executed.
  • the server 10 sets settings related to remittance to a user different from the user A based on the input by the user A to the input unit 22 of the user terminal 20A.
  • the information processing of the present embodiment as an example, not limited to the information related to the management of the talk room by granting the authority to set the setting related to the remittance only to a specific user (here, user A). Since the processing can be reduced, the processing speed of the server 10 can be improved. Further, since the user A can set the remittance setting to another user as needed, the convenience of the talk room can be improved.
  • the server 10 cancels the remittance-related setting set for the user A based on the input by the user A to the input unit 22 of the user terminal 20A.
  • the authority to cancel the setting related to remittance is given only to a specific user (here, user A). Since information processing can be reduced, the processing speed of the server 10 can be improved. Further, since the user A can cancel the setting related to the remittance as needed, unnecessary remittance can be prevented, so that the safety of the talk room can be improved.
  • the server 10 sets the setting for remittance to another user different from user A
  • the amount of remittance from user B to user A is transferred from user A to another user. Execute the process of sending money to the user.
  • the present embodiment is not limited, but as an example, when the server 10 receives a participation request from the user terminal 20 of the participant who wishes to participate in the talk room and the participant satisfies a predetermined condition, the participant's It is a form of approving participation in the talk room.
  • the server 10 approves the participation of the participants (here, the user B and the user C) in the talk room, as an example but not a limitation.
  • the contents described in this embodiment can be appropriately applied to each of the other embodiments.
  • FIG. 17 is a flowchart showing information processing according to the third embodiment.
  • the same components as those in the above-described embodiment are appropriately designated with the same reference numerals, and the description thereof will be omitted or simplified.
  • FIG. 17 is a flowchart on the premise that the procedures S111 to S132 in FIG. 2 have been completed.
  • step S341 the server 10 stores the participation request in the storage unit 15, which receives the participation request, as an example, not limited to it.
  • the server 10 generates the approval confirmation image T14 as an example, not a limitation.
  • step S342 the server 10 transmits the approval confirmation image T14 shown in FIG. 18 to the user terminal 20B that is the transmission source of the participation request, as an example but not a limitation.
  • the user terminal 20B displays the approval confirmation screen T14 shown in FIG. 18 in the display area 28 as an example, not a limitation.
  • the approval confirmation image T14 includes, as an example, not limited to, a user name input field T141 that accepts input of the user name of the user B who requests participation in the talk room, and an approval request execution unit T142.
  • the control unit 21 is input when there is an input in the input unit 22 to the user name input field T141 (a text box as an example, not a limitation) displayed in the display area 28.
  • the text data is displayed in the user name input field T141.
  • the control unit 21 approves the information regarding approval (as an example, not limited). Request information) is confirmed. Then, in step S352, the user terminal 20B transmits an approval request including the approval request information to the server 10.
  • step S361 the server 10 stores the approval request in the storage unit 15. Then, the server 10 collates the user name included in the approval request information with the "user name" of the personal identification information D17 shown in FIG. 19 (not limited, but as an example, approval processing).
  • the personal identification information D17 is created by an identity verification procedure as an example, not a limitation.
  • the identity verification procedure is not limited, but is, as an example, a procedure for registering the user's personal information in the server 10 before the user makes a remittance processing request.
  • the server 10 transmits an input request image to the user terminal 20.
  • the input request image is not limited, but is, for example, an image in which information about a bank account or information about a driver's license (which may include an image or the like) is input.
  • the user terminal 20 accepts input to the input unit 22 for the input request image, registers information corresponding to each item in FIG.
  • FIG. 19 is a diagram showing an example of personal identification information D17.
  • the personal identification information D17 is not limited, but as an example, [user ID], [user name], [password], [real name], [date of birth], [address], [telephone number], and [email address]. Includes items. [User ID] is not limited, but is, as an example, identification information of a user included in a group corresponding to each talk room.
  • the [user name] is not a limitation but, as an example, a name associated with the [user ID] and set by the user, which is used in the messaging service.
  • the [password] is not limited, but is associated with the [user ID] as an example, and is a combination of letters, symbols, and numbers.
  • the [real name] is not a limitation but, as an example, the name of the user associated with the [user ID].
  • [Date of birth] is not a limitation but, as an example, the date of birth of the user associated with [User ID].
  • [Address] is not a limitation but, as an example, a user's address associated with [User ID].
  • the [telephone number] is not limited, but is, for example, a user's mobile phone number, a fixed telephone number, or the like associated with the [user ID].
  • the [email address] is not a limitation but, as an example, a user's email address associated with the [user ID].
  • the server 10 is not limited, but as an example, as a result of collation, the user name included in the approval request information and the "user name" of the [user name] associated with the user ID of the user B are used. If they match, the user ID of the user B is registered in the [user ID] of the talk room information D12 (see FIG. 3A). As an example, not limited to, when the user ID of the user B is registered in the talk room information D12 on the server 10, the user terminal 20B receives the content information D13 from the server 10 and the content as shown in FIG. 2A (b). The image T1 including Q1 may be displayed in the display area 28. As an example, not limited to this, steps S341 to S361 are similarly executed for the user terminal 20C.
  • the approval confirmation image T14 has the user name input field 141, but the present invention is not limited to this.
  • the approval confirmation image T14 is an image including an input field for inputting at least one of a user ID, a password, a real name, a date of birth, an address, a telephone number, and an e-mail address instead of the user name input field T141. May be. That is, in the present embodiment, the server 10 receives information that can identify an individual in the messaging service from the user, and if the information satisfies a predetermined condition, the server 10 participates in the talk room of the user. approve. ⁇ Sixth modification>
  • FIG. 20 is a diagram showing an example of the remittance completion image T15.
  • the information processing according to the sixth modification is a form in which the server 10 transmits information that can uniquely identify the user who sent the remittance to the user who received the remittance when the remittance process is completed in the server 10. be.
  • the user who received the remittance will be referred to as user A
  • the user who sent the remittance will be referred to as user B.
  • the server 10 identifies the "real name" associated with the user B by referring to the personal identification information D17 generated by the above-mentioned identity verification procedure, as an example, not by limitation. do.
  • the server 10 transmits the remittance completion image T15 including the “real name” of the user B to the user terminal 20A as an example, not the limitation.
  • the user terminal 20A displays the remittance completion image T15 shown in FIG. 20 in the display area 28.
  • the remittance completion image T15 is not limited, but is an image including a user display unit T151 displaying the real name of the user B, a remittance amount display unit T152 displaying the remittance amount, and a confirmation completion unit T153. ..
  • the user terminal 20A determines that the confirmation complete unit T153 is selected when the input unit 22 receives an input for the icon of the confirmation complete unit T153, and displays the remittance completion screen T15 in the display area. Erase from 28.
  • the server 10 receives information regarding approval for joining the talk room from the user terminal 20B of the user B.
  • the server 10 executes a process of causing the user B to join the talk room based on the information regarding the approval.
  • the server 10 can secure the safety of the talk room and improve the security by making the user's participation in the talk room an approval formula, as an example, not limited to the information processing. ..
  • the server 10 processes the remittance from the user B to the user A, the name information in the identity verification procedure of the user B and the information regarding the completion of the remittance from the user B to the user A. Is transmitted to the user terminal 20A of the user A.
  • the user terminal 20A of the user A who received the remittance can receive the real name of the sender and the notification indicating that the remittance is completed.
  • This embodiment is not limited to, but as an example, the server 10 deletes the "talk room ID" satisfying a predetermined condition from the [talk room ID] of the talk room information D12.
  • the predetermined conditions are not limited, but as an example, the predetermined time has passed from the date and time when the talk room was created, the preset date and time have passed, and the manager has withdrawn from the talk room. And so on.
  • FIG. 21 is a flowchart showing information processing according to the fourth embodiment.
  • FIG. 22 is a diagram showing an outline of information processing according to the fourth embodiment.
  • the same components as those in the above-described embodiment are appropriately designated with the same reference numerals, and the description thereof will be omitted or simplified.
  • FIG. 21 is a flowchart on the premise that the procedures S111 to S151 in FIG. 2 have been completed.
  • the administrator here, user A
  • the remittance receiving setting sets a predetermined condition for deleting the talk room, as an example, not a limitation.
  • the server 10 may, for example, automatically delete the talk room after a predetermined time (for example, 24 hours) after the talk room is created. Further, as an example without limitation, the timing at which the talk room is deleted may be arbitrarily set by the user (operator) of the server 10. In addition, the contents described in this embodiment can be appropriately applied to each of the other embodiments.
  • the user terminal 20A is not limited to the icon PL of the display area 28 shown in FIG. 2A (b), and the icon PL is selected when the input unit 22 receives an input.
  • the selected image T16 including the remittance setting icon Tb shown in FIG. 22A is displayed in the display area 28.
  • the control unit 21 determines that the "disappearance condition" is selected when the input unit 22 receives an input for the icon "disappearance condition”.
  • the control unit 21 displays the extinction condition image T17 of FIG. 22B in the display area 28 with reference to the extinction information D12 as an example, not a limitation.
  • the extinction condition image T17 is not limited, but as an example, sets an extinction item setting unit T171 for selectively displaying an extinction condition item, an extinction date setting unit T172 for setting an extinction date, and an extinction time. It includes an extinction time setting unit T173 for the purpose and a condition completion unit T174.
  • the control unit 21 displays the disappearance item setting unit T171 displayed in the display area 28 so that "time" or "user” can be selected when there is an input in the input unit 22. .. Then, as an example, not limited to, when the input unit 22 receives an input to the extinction date setting unit T172 displayed in the display area 28, the control unit 21 uses the input text data as the extinction date setting unit T172.
  • the control unit 21 uses the input text data as the extinction time setting unit T173.
  • the extinction date setting unit T172 and the extinction time setting unit T173 are not limited, but as an example.
  • the time may be displayed.
  • the extinction date setting unit T172 and the extinction time setting unit T173 are not limited, and may be, for example, a text box or the like that accepts input of a date or time.
  • the control unit 21 disappears information regarding the extinction condition (as an example, not a limitation). Condition information) is confirmed. Then, in step S452, the user terminal 20A transmits the extinction condition information to the server 10.
  • the server 10 stores the extinction condition information in the storage unit 15.
  • the storage unit 15 stores the extinction condition information as shown in the extinction condition information D18 shown in FIG.
  • FIG. 23 is a diagram showing an example of the extinction condition information D18.
  • the extinction condition information D18 includes, but is not limited to, the items of [talk room ID], [creation date / time], and [extinction condition].
  • [Talk room ID] is not limited, but is, as an example, identification information of each talk room.
  • [Creation date and time] is not a limitation but, as an example, the date and time when the talk room is created, which is related to [Talk room ID].
  • the [disappearance condition] is not a limitation but, as an example, an extinction condition included in the extinction condition information associated with the [talk room ID].
  • the talk room "tr01” is set so that the talk room disappears at "10:00 on January 5, 2020".
  • the talk room "tr02” is set so that the talk room disappears "20 hours later” from "10:00 on January 2, 2020”.
  • the talk room "tr03" is set so that the talk room disappears when the administrator user A withdraws from the talk room.
  • step S471 the control unit 11 of the server 10 determines whether or not the extinction condition is satisfied in each talk room.
  • the control unit 11 executes the extinction process when it is determined that the extinction condition is satisfied, not as a limitation but as an example.
  • the extinction process is not limited to the process of deleting the talk room ID from the talk room information D12 as an example.
  • step S482 the server 10 transmits the talk room information D12 to the user terminal 20 as an example without limitation. Then, when the image TL of the talk room list is displayed in the display area 28 on the user terminal 20, the icon of the talk room (here, “coffee party”) in which the talk room ID is deleted is displayed on the image TL. It may be displayed.
  • the icon "Coffee party” may be displayed together with a message indicating that the service cannot be used, such as "closed". Furthermore, the user terminal 20 determines that the "coffee party” is selected when the input unit 22 receives an input for the "coffee party” icon, for example, without limitation. Then, the user terminal 20 refers to the talk room information D22 as an example, not a limitation, and determines that the talk room ID corresponding to the "coffee party" does not exist. The control unit 21 may generate a message indicating that the talk room of the “coffee party” is unavailable, and display the message in the display area 28, as an example, but not limited to it.
  • the server 10 deletes the talk room based on the elapse of the set period or the set time.
  • the amount of information processing in the user terminal 20 can be reduced as an example, not limited to the information processing.
  • the burden of the operation related to the deletion of the talk room by the user can be eliminated as an example, and the convenience of the user can be improved.
  • This embodiment is not limited to, but as an example, in the server 10, a user participating in the talk room can make a report about another user.
  • the participants in the talk room notify the server 10 about the remittance recipient based on the information about the remittance recipient, so that the remittance recipient's remittance setting is changed on the server 10.
  • the setting related to remittance is not limited, but as an example, in addition to setting the user IDs of the manager and the participant described above in the items of [Remittance recipient ID] or [Remittance sender ID], the talk room.
  • Setting to temporarily prohibit remittance in setting to permanently prohibit remittance in talk room, setting to temporarily prohibit remittance in message service, remittance in message service It may be a setting such as a setting that permanently prohibits.
  • the information related to the report is referred to as "report information”
  • the remittance recipient is referred to as user A
  • the participant who transmits the report information about user A to the server 10 is referred to as user B.
  • the contents described in this embodiment can be appropriately applied to each of the other embodiments.
  • FIG. 24 is a flowchart showing information processing according to the fifth embodiment.
  • FIG. 25 is a diagram showing an outline of information processing according to the fifth embodiment.
  • the same components as those in the above-described embodiment are appropriately designated with the same reference numerals, and the description thereof will be omitted or simplified.
  • FIG. 24 is a flowchart on the premise that the procedures S111 to S151 in FIG. 2 have been completed.
  • a procedure for the user B to report the action of the user A in the talk room via the user terminal 20B will be described.
  • the user terminal 20B is not limited to the icon PL of the display area 28 shown in FIG. 2A (c), and the icon PL is selected when the input unit 22 receives an input.
  • the selected image T18 including the remittance setting icon Tb as shown in FIG. 25A is displayed in the display area 28.
  • the control unit 21 determines that "report” is selected.
  • the control unit 21 displays the report setting image T19 of FIG. 25B in the display area 28 with reference to the talk room information D22 as an example, not a limitation.
  • the 25B includes, as an example, not a limitation, a target person display unit T191, a notification reason display unit T192, and a notification confirmation unit T193.
  • the target display unit T191 is not limited to, but as an example, the name of the user corresponding to the user ID set in [Remittance recipient ID] is displayed.
  • the target display unit T191 is not limited, but as an example, when a plurality of remittance recipients are set in the talk room, the target display unit T191 displays the names of a plurality of users in a predetermined display format (pull-down as an example, not limited). May be good.
  • control unit 21 is not limited, but as an example, when a plurality of remittance recipients are set in the talk room, two or more of the names of the plurality of users can be selected, and a check box corresponding to each user can be selected. Etc. may be displayed in the display area 28.
  • the report reason display unit T192 may display the report reason in a predetermined display format (pull-down as an example, not a limitation) when an input is made to the input unit 22 as an example rather than a limitation.
  • the report reason display unit T192 is not limited, but may be, for example, a text box or the like that accepts input of the content of the report.
  • the control unit 21 displays a list showing candidates for the report reason in the display area 28 as shown in FIG. 25 (b). do. Then, when the input unit 22 receives an input for the predetermined icon displayed in the list, the control unit 21 determines that the icon (here, an illegal act) is selected. Then, as an example, the control unit 21 determines the notification information when the input unit 22 receives an input to the notification confirmation unit T193 displayed in the display area 28. Then, in step S552, the user terminal 20A transmits a receipt setting request including the receipt setting information to the server 10.
  • step S561 the server 10 stores the report information in the storage unit 15.
  • the server 10 collates the user ID of the user B with the user ID of the [user ID] of the talk room information D12 shown in FIG. 3A based on the notification information as an example, not the limitation. That is, the control unit 11 confirms that the notification information has been transmitted from the user terminal 20 of the user participating in the talk room, not as a limitation but as an example.
  • the server 10 executes the restriction setting process as an example, not the limitation.
  • the restriction setting process is not a limitation but, as an example, a process of setting a restriction on the user ID of the report target person (here, user A) based on the report information.
  • the restriction setting process may be a process of setting a restriction on the user ID of the user A by determining whether or not a predetermined condition is satisfied, as an example, instead of the limitation.
  • the predetermined conditions are not limited, but as an example, the number of times of notification exceeds a predetermined threshold value, and the content transmitted by the subject of the notification is determined to be fraudulent based on the result of character analysis.
  • the server 10 is not limited, but as an example, the user ID of the user A is restricted as in the first restriction information D19A shown in FIG. 26.
  • the server 10 is not limited, and as an example, a restriction may be given to the user ID for each talk room ID.
  • the server 10 is not limited, but as an example, by deleting the user ID of the user A from the item of the [remittance recipient ID] of the talk room information D12, the user A cannot receive the remittance in the talk room. Restrictions may be given. Further, the server 10 may withdraw the user A from the talk room by deleting the user ID of the user A from the talk room information D12, for example, without limitation. In this case, the server 10 is not limited, but as an example, with reference to the remittance history information D15, the remittance setter refunds the user who has previously sent the remittance to the remittance setter (here, user A). As described above, the value transfer process may be executed.
  • step S562 the server 10 transmits a setting completion notification including the first restriction information D19A to each user terminal 20.
  • Each user terminal 20 displays an image including content related to the restriction (for example, "the restriction is set for the user A") based on the setting completion notification as an example, not the limitation.
  • the server 10 is not limited to the user (remittance sender) who can remittance based on the report information. You may set the settings related to remittance.
  • the restriction setting process in S561 in this case will be described.
  • the server 10 sets a restriction on the user IDs of the participants (here, the user B and the user C) of the talk room based on the report information as an example, not the limitation.
  • the target display unit T191 is not limited, and as an example, the name of the user corresponding to the user ID set in [user ID] is displayed.
  • the target display unit T191 is not limited, and as an example, all users participating in the talk room may be displayed. Since the report reason display unit T192 and the report confirmation unit T193 are the same as above, the description thereof will be omitted.
  • the server 10 is not limited, but as an example, remittance is made to the user ID of the notified user (here, user B and user C) as in the second restriction information D19B shown in FIG. 27. Give restrictions to prohibit (disable).
  • the server 10 is not limited, but as an example, by deleting the user ID of the user notified from the [remittance ID] of the talk room information D12, a restriction is given so that remittance cannot be made to the notified user. You may.
  • the server 10 receives the notification information about the user A (administrator) from the user B, and sets the setting regarding the remittance to the user A based on the information about the user A (administrator). Change to.
  • the server 10 can change the setting related to the remittance in the talk room based on the information acquired from the user terminal 20 of the user. Safety can be improved.
  • the server 10 receives notification information about user A (administrator) from user B, and makes remittance to user A impossible based on the information about user A (administrator). You may change it to the setting.
  • the setting is changed so that the user A cannot receive the remittance in the talk room based on the information acquired from the user terminal 20 of the user. Therefore, it is possible to prevent the user A from committing an illegal act in the talk room, and thus the safety of the talk room is improved.
  • the server 10 receives the notification information about the user A (administrator) from the user B, and based on the information about the user A (administrator), suspends the use of the user A's account at least temporarily. You may.
  • This embodiment is not limited to, but as an example, in the server 10, the user who received the remittance can refund the money to the user who sent the remittance.
  • the administrator who received the remittance (as an example, not the limitation, the remittance recipient, etc.) can refund the participant who sent the remittance to the administrator.
  • the process of refunding on the server 10 is referred to as "refund processing”.
  • the refund process is not limited, but as an example, the remittance so as to transfer the value corresponding to the refund source remittance account ID to the value corresponding to the refund destination remittance account ID.
  • This is a process for updating the information of the payment server 30 corresponding to the account.
  • the contents described in this embodiment can be appropriately applied to each of the other embodiments.
  • FIG. 28 is a flowchart showing information processing according to the sixth embodiment.
  • FIG. 29 is a diagram showing an outline of information processing according to the sixth embodiment.
  • the same components as those in the above-described embodiment are appropriately designated with the same reference numerals, and the description thereof will be omitted or simplified.
  • FIG. 28 is a flowchart on the premise that the procedures S111 to S151 in FIG. 2 have been completed.
  • user A the user who refunds
  • user B and user C the user C.
  • the user terminal 20A is not limited to the icon PL of the display area 28 shown in FIG. 2A (c), and the icon PL is selected when the input unit 22 receives an input.
  • the selected image T20 including the remittance setting icon Tb as shown in FIG. 29A is displayed in the display area 28.
  • the control unit 21 determines that "refund” is selected when the input unit 22 receives an input for the icon "refund”.
  • the control unit 21 refers to the remittance history information D15 as an example, not a limitation, and extracts the remittance history that was remitted before the present time.
  • the control unit 21 displays the refund setting image T21 of FIG.
  • the refund setting image T21 includes, as an example, not a limitation, a refund condition display unit T211 and a refund completion unit T212.
  • the refund condition display unit T211 is not limited to, but as an example, the name of the user corresponding to the user ID set in the [remittance ID] is displayed. Further, as an example, not limited to, the name of only the user who sent the remittance before the present time may be displayed based on the extracted remittance history.
  • the refund condition unit T211 may display the names of a plurality of users in a predetermined display format (pull-down as an example, not a limitation) when there are a plurality of users who have remitted money before the present time. ..
  • the control unit 21 is not limited, but as an example, when there are a plurality of users who have remitted money before the present time, it is possible to select two or more of the names of the plurality of users, and a check box corresponding to each user is provided. It may be displayed in the display area 28.
  • the refund condition display unit T211 includes, as an example, not a limitation, an input area for a refund amount corresponding to a refund destination.
  • the refund amount input area is not limited, and may be, for example, a text box or the like that accepts the refund amount input.
  • the control unit 11 determines the above-mentioned information regarding refund (refund information as an example, not limitation) when the input unit 22 receives an input to the refund completion unit T212. Then, in step S552, the user terminal 20A transmits a refund request including refund information to the server 10.
  • step S661 the server 10 stores the refund request in the storage unit 15.
  • the server 10 collates the user ID of the user A with the user ID of the [remittance recipient ID] of the talk room information D12 based on the refund request as an example, not the limitation. That is, the control unit 11 confirms that the refund request has been transmitted from the user terminal 20 of the remittance recipient, not as a limitation but as an example. As an example, the control unit 11 executes a refund process when the user ID of the user A and the user ID of the [remittance recipient ID] match as a result of collation.
  • the refund process is not limited, but as an example, first, the control unit 11 determines the user ID of the refund source (here, user A) and the user ID of the refund destination (here, user B and the user) based on the refund information. C) and are specified. Next, the control unit 11 identifies the remittance account used in the remittance process based on the remittance history information D15, not by limitation but as an example.
  • the information about the remittance account used in the remittance process is not limited, but may be included in the refund information as an example.
  • the control unit 11 changes from the value corresponding to the remittance account of the refund source user ID (here, user A) to the value corresponding to the remittance account of the refund destination user ID (here, user B and user C).
  • a process of updating the remittance account information D31 of the payment server 30 corresponding to the remittance account (here, the remittance account A) is executed so as to transfer the value indicating the refund amount.
  • step S662 the server 10 transmits a refund completion notification including information regarding the refund result to the user terminal 20.
  • the user terminal 20 displays an image including content indicating the completion of refund (for example, user A has refunded 1,000 yen to user B and user C) in the display area 28. Display.
  • the user terminal 20B and the user terminal 20C also display the image including the content in the display area 28.
  • FIG. 30 is a diagram showing an outline of information processing according to the seventh modification.
  • the information processing according to the seventh modification is not limited, but is, as an example, a form in which the remittance recipient refunds to the sender based on a vote by a user who desires a refund.
  • the procedures S111 to S151 in FIG. 2 have been completed.
  • the sender is user B and user C
  • the remittance recipient is user A
  • the remittance is refunded from user A to user B and user C based on the voting results by user B and user C. The procedure will be described.
  • the user terminal 20B determines that the icon PL has been selected when the input unit 22 receives an input to the icon PL of the display area 28 shown in FIG. 2A (c), not as a limitation.
  • the selected image T22 including the remittance setting icon Tb as shown in FIG. 30A is displayed in the display area 28.
  • the control unit 21 determines that the "refund vote” is selected when the input unit 22 receives an input for the icon "refund vote”.
  • the control unit 21 refers to the remittance history information D15 as an example, not a limitation, and extracts the remittance history that was remitted before the present time.
  • the control unit 21 displays the refund voting image T23 of FIG.
  • the refund voting image T23 includes, but is not limited to, a refunder display unit T231, a refund amount display unit T232, and a voting completion unit T233.
  • the refunder display unit T231 is not limited to, but as an example, the name of the user corresponding to the user ID set in the [remittance recipient ID] is displayed. Further, the refunder display unit T231 is not limited, but as an example, when there are a plurality of user IDs set in [Remittance recipient ID], a plurality of users in a predetermined display format (pull-down as an example, not limited). The name of may be displayed.
  • control unit 21 is not limited, but as an example, when there are a plurality of user IDs set in [Remittance recipient ID], two or more of the names of the plurality of users can be selected, and the control unit 21 corresponds to each user.
  • a check box or the like may be displayed in the display area 28.
  • the refund amount display unit T232 is not limited, and may be, for example, a text box or the like that accepts input of the refund amount.
  • the voting completion unit T213 determines the above-mentioned information regarding voting (voting information as an example, not limitation) when an input is made to the input unit 22 as an example, not a limitation. Then, the user terminals 20B and 20C transmit a voting request including voting information to the server 10.
  • the server 10 stores the voting request in the storage unit 15.
  • the server 10 collates the user IDs of the user B and the user C with the user ID of the [user ID] of the talk room information D12 shown in FIG. 3A based on the voting information as an example, not the limitation. That is, the control unit 11 confirms that the voting information has been transmitted from the user terminal 20 of the user participating in the talk room, not as a limitation but as an example.
  • the server 10 executes the voting refund process based on the voting information as an example, not the limitation.
  • the voting refund process is not limited, but is, as an example, a process of causing a user who has sent a voting request to refund from a refunder by determining whether or not a predetermined condition is satisfied based on voting information.
  • the predetermined condition is not limited, but as an example, the total number of information indicating the refunder exceeds a predetermined threshold based on the information about the refunder included in the voting information, and the information indicating the refunder. For example, the total number of users exceeds a predetermined ratio to the number of users participating in the talk room.
  • the control unit 11 executes the above-mentioned value transfer process so that the refunder causes the voter to refund when it is determined that the predetermined condition is satisfied.
  • the server 10 transmits, as an example, not limited to, a refund completion notification including information regarding the result of executing the value transfer process to each user terminal 20.
  • the server 10 receives refund information regarding refunding the amount of money sent from user B (participant) to user A (administrator) to user A, and based on the refund information, the server 10 receives the refund information.
  • a process related to remittance of the amount of money sent from the user A to the user B is executed.
  • a remittance request can be executed from the remittance recipient to the remittance sender, and whether or not the user has executed the remittance in response to the remittance request is displayed. It is a form that can be done.
  • the remittance recipient is referred to as user A
  • the sender is referred to as user B and user C
  • the remittance is requested from user A to user B and user C as an example, not limited to the present.
  • the contents described in this embodiment can be appropriately applied to each of the other embodiments.
  • FIG. 31 is a flowchart showing information processing according to the seventh embodiment.
  • FIG. 32 is a diagram showing an outline of information processing according to the seventh embodiment.
  • FIG. 33 is a diagram showing an example of a remittance request image.
  • the same components as those in the above-described embodiment are appropriately designated with the same reference numerals, and the description thereof will be omitted or simplified.
  • FIG. 31 is a flowchart on the premise that the procedures S111 to S151 in FIG. 2 have been completed.
  • a remittance recipient here, user A
  • a remittance sender here, user B and user C
  • the user terminal 20A is not limited to the icon PL of the display area 28 shown in FIG. 2A (c), and the icon PL is selected when the input unit 22 receives an input.
  • the selected image T24 including the remittance setting icon Tb as shown in FIG. 32A is displayed in the display area 28.
  • the control unit 21 determines that the "remittance request" is selected when the input unit 22 receives an input for the icon "remittance request”.
  • the control unit 21 displays the remittance request image T25 of FIG. 32B in the display area 28 with reference to the talk room information D12 and the remittance history information D15 as an example, not limited to.
  • the remittance request image T25 is not limited, and includes, as an example, a remittance request destination selection unit T251 and a remittance request completion unit T252.
  • the remittance request destination display unit T251 is not limited to, but as an example, the name of the user corresponding to the user ID set in the [remittance sender ID] is displayed. Further, as an example, not limited to, the name of only the user who has not remitted may be displayed based on the remittance history information D15.
  • the remittance request destination display unit T251 may display the names of a plurality of users in a predetermined display format (pull-down as an example, not a limitation) when there are a plurality of remittance senders as an example rather than a limitation.
  • the control unit 21 is not limited, but as an example, when there are a plurality of remittance senders, two or more of the names of the plurality of users can be selected, and a check box or the like corresponding to each user is displayed in the display area 28. You may.
  • the user requesting remittance (here, user A) is a part of the user (here, user B or user C). You can request a remittance to.
  • the control unit 11 determines the above-mentioned information regarding the remittance request (as an example, not the limitation) when the input unit 22 receives an input to the remittance request completion unit T252 as an example, not as a limitation. Then, in step S752, the user terminal 20A transmits a remittance request request including the remittance request information to the server 10.
  • step S761 the server 10 stores the remittance request request in the storage unit 15.
  • the server 10 collates the user ID of the user A with the user ID of the [remittance recipient ID] of the talk room information D12 based on the remittance request request. That is, the control unit 11 confirms that the remittance request request has been transmitted from the user terminal 20 of the remittance recipient, not as a limitation but as an example.
  • the control unit 11 executes a request display process when the user ID of the user A and the user ID of the [remittance recipient ID] match as a result of collation.
  • the request display process is not limited, but as an example.
  • the control unit 11 identifies a target user who requests remittance based on the remittance request information, not as a limitation but as an example.
  • the control unit 11 generates the remittance list T261 shown in FIG. 33 (a), which can determine whether the specified user has remittance has been remitted or has not been remitted, based on the remittance history information D10, as an example but not a limitation. ..
  • the control unit 11 generates a remittance request image T26 including a remittance list T261 as an example, not a limitation.
  • the control unit 11 may generate the remittance list T241 so as to include, as an example, not a limitation, a display capable of discriminating at least one of the users who have already remitted or the users who have not remitted.
  • step S762 the server 10 transmits the remittance request image T26 including the remittance list T241 to the user terminal 20 as an example without limitation.
  • the user terminal 20 displays the remittance request image T26 shown in FIG. 33A in the display area 28.
  • the server 10 may transmit the remittance request image T26 only to the user terminal 20 of the remittance recipient (here, the user A), as an example without limitation. In this case, only the user terminal 20A displays the remittance request image T26 shown in FIG. 33A in the display area 28.
  • the remittance request image T26 includes, but is not limited to, the remittance list T261 and the content Q8 relating to the remittance request of the user A.
  • the “remittance completed” column of the remittance list T261 is shown blank, and “untransferred”.
  • the display "B" indicating the user B and the display "C” indicating the user C are displayed in the column.
  • the server 10 can determine the remittance user B (FIG. 33).
  • a remittance request image T27 including the remittance list T271 shown in b) and the content Q9 indicating that the user B has completed the remittance in response to the remittance request of the user A is generated.
  • the control unit 11 is not limited, but as an example, in the user terminal 20B, the input unit 22 by the user B inputs the content Q8 including the URL and the icon Q81 for causing the server 10 to execute the remittance process.
  • control unit 11 is not limited, but as an example, when the remittance process is completed, the content Q9 indicating that the remittance has been sent in response to the remittance request of user A (as an example, not limited, in response to the remittance request from user A).
  • Remittance request image T27 including remittance request image T27 is generated.
  • the server 10 transmits the remittance request image T27 to the user terminal 20 as an example without limitation.
  • the server 10 may transmit the remittance request image T27 only to the user terminal 20 of the remittance recipient (here, user A), as an example without limitation.
  • the server 10 is not limited, but as an example, generates a remittance request image T27 including a remittance list T271 displaying only the remittance status of the remittance user, and requests the remittance to the user terminal 20 of the remittance user.
  • Image T27 may be transmitted.
  • the server 10 transmits the remittance request image T27 to the user terminal 20 of the remittance user B
  • the display "B" to be shown is displayed, the "unremittance” field is left blank, and the remittance request image T27 is generated.
  • the user terminal 20 displays the remittance request image T27 shown in FIG. 33B in the display area 28 as an example, not limited to it.
  • FIG. 34 is a diagram showing an example of the remittance request identification image T28.
  • the information processing according to the eighth modification is, as an example, not limited to, a form in which the display indicating the user in the talk room is emphasized according to the status of unremittance or remittance completed. In the eighth modification, it is assumed that the procedure up to S781 in FIG. 31 has been completed.
  • the remittance recipient is referred to as user A
  • the remittance sender is referred to as user B and user C
  • the remittance completed user is referred to as user B
  • the unremittance user is referred to as user C.
  • the contents described in this embodiment can be appropriately applied to each of the other embodiments.
  • the server 10 is not limited, but as an example, the highlight T282 shown in FIG. 34, which can identify the untransferred user C, is attached to the icon Uc1 of the user C to generate the remittance request image T28.
  • the server 10 may generate a remittance list image T28 by attaching a highlight T282 capable of identifying the user B who has completed the remittance to the icon Ub1 of the user B.
  • the server 10 may generate a remittance request image T28 by attaching the highlighting T282 to the user's user name (here, reference numeral Ub2 or reference numeral Uc2) or content.
  • the highlight display T282 is not limited, but is, for example, a blinking display or a lighting display that surrounds the icon Uc1 of the user C. Further, the highlight display T282 is not limited, and may be, for example, a blinking display or a lighting display that surrounds the user name Uc2 of the user C. Further, the highlight display T282 is not limited, but may be, for example, a blinking display or a lighting display that surrounds the content Q10 of the user C, or a display in which the color scheme of the content Q10 is different from that of the content Q9.
  • the remittance list T281 is displayed as an example without limitation, but the remittance list T261 may or may not be included in the remittance request image T28.
  • the server 10 transmits the remittance request image T28 to the user terminal 20 as an example, not limited to it.
  • the server 10 may transmit the remittance request image T28 only to the user terminal 20 of the remittance recipient (here, user A), as an example without limitation.
  • the user terminal 20 displays the remittance request image T28 shown in FIG. 34 in the display area 28 as an example, not limited to it.
  • FIG. 35 is a diagram showing an outline of information processing according to the ninth modification.
  • the information processing according to the ninth modification is not limited, but as an example, the server 10 rejects the withdrawal request from the talk room by the user who has not remitted money.
  • "withdrawal” is not limited to, but as an example, the relationship between the talk room ID and the user ID in the talk room information D12 is canceled on the server 10. That is, when "withdrawal" is executed, the user terminal 20 of the withdrawn user cannot display the contents of the talk room in the display area 28, cannot remit money to another user, and remittance from another user. You will not be able to receive it.
  • the procedure up to S762 in FIG. 31 has been completed.
  • the remittance recipient is user A
  • the remittance is user B and user C
  • user B is a user who has remittance
  • user C is a user who has not remittance
  • a user of user C It is assumed that the terminal 20C has sent the withdrawal request to the server 10.
  • the contents described in this embodiment can be appropriately applied to each of the other embodiments.
  • the user terminal 20C determines that the icon PL has been selected when the input unit 22 receives an input to the icon PL of the display area 28 shown in FIG. 2A (c), not as a limitation.
  • the selected image T26 including the remittance setting icon Tb as shown in FIG. 35A is displayed in the display area 28.
  • the control unit 21 determines that "withdrawal" is selected when the input unit 22 receives an input for the icon "withdrawal".
  • the user terminal 20C transmits information regarding withdrawal (withdrawal information as an example, not with limitation) to the server 10 as an example, not with limitation.
  • the server 10 stores the withdrawal information in the storage unit 15 as an example, not a limitation.
  • the server 10 refers to the remittance history information D15 as an example, not a limitation, and determines whether or not the user C has not remitted money based on the withdrawal information. As an example, not a limitation, when it is determined that the user C has not remitted money, the server 10 generates a withdrawal refusal image T30 including a refusal comment image T301 indicating that the member cannot be withdrawn. The server 10 transmits the withdrawal refusal image T30 to the user terminal 20C as an example, not a limitation. Next, the user terminal 20C displays the withdrawal refusal image T30 shown in FIG. 35B in the display area 28 as an example, not limited to it.
  • the server 10 is not limited to generating the withdrawal refusal image T30
  • the user terminal 20C is not limited to generating the withdrawal refusal image T30 based on the remittance history information D25 as an example.
  • the rejected image T30 may be displayed in the display area 28.
  • FIG. 36 is a diagram showing an example of the remittance request image T31.
  • the information processing according to the tenth modification is performed from a user whose remittance receiving setting has been changed (here, user B) to a non-remittance user (here, user C) after the receipt change processing in the second embodiment.
  • the remittance is executed to the user whose settings have been changed.
  • the user terminal 20A of the user whose remittance receiving setting has been changed (here, user A) is requested to remit to the user terminal 20C of user C, and then the user whose remittance receiving setting has been changed (here, user A). It is assumed that the user terminal 20B of the user B) requests the remittance to the user terminal 20C of the user C.
  • the server 10 transmits the remittance request image T31 to the user terminal 20C as an example, not a limitation.
  • the user terminal 20C displays the remittance request image T31 shown in FIG. 36 in the display area 28.
  • the remittance request image T26 includes, as an example, not limited to, the content Q8 relating to the remittance request of the user A and the content Q10 relating to the remittance request of the user B.
  • the content Q8 is not a limitation but an example
  • the user terminal C is not a limitation but an example, and includes a URL and an icon Q81 for causing the server 10 to execute a remittance process.
  • the content Q10 includes, as an example, not limited to, a URL and an icon Q101 for causing the server 10 to execute the remittance process.
  • the user terminal 20C determines that the icon Q81 has been selected when the input unit 22 receives an input to the icon Q81, and requests the server 10 for remittance processing (as an example, not a limitation). You may send information about the destination, source, amount of money, remittance account, etc.).
  • the server 11 refers to the talk room information D12 as an example, not a limitation, and performs a remittance process so that the remittance is sent to the remittance recipient (here, user B) after the setting of the remittance receiving setting is changed.
  • the user terminal 20C is not limited, but as an example, when the input unit 22 receives an input to the icon Q101, the user terminal 20C determines that the icon Q101 has been selected, and requests the server 10 for remittance processing (example not limited). (Including information about the remittance destination, remittance source, remittance amount, remittance account, etc.) may be sent.
  • the server 11 is not limited to the remittance, but as an example, the remittance is sent to the remittance recipient (here, the user B) after the setting of the remittance receiving setting is changed by referring to the talk room information D12. Execute the process. That is, if there is an input in the input unit 22 for the display related to the remittance request displayed in the talk room after the setting of the remittance receipt setting is changed, the remittance is sent to the remittance recipient after the setting of the remittance receipt setting is changed. The remittance process is executed.
  • the server 10 when the user B remits money in response to the remittance request transmitted from the user A to the user B, the server 10 provides information indicating that the remittance has been made in response to the remittance request. include.
  • the server 10 can display the user who has sent the remittance to the user in the talk room as an example, but not limited to it, so that the convenience of the user's remittance can be improved. ..
  • the server 10 has not remitted the remittance request. Include information that indicates.
  • the user who has not sent money to the user can be displayed in the talk room as an example, not limited to the user, so that the convenience of the user's remittance can be improved.
  • the server 10 receives information indicating that the user B has remitted money and information indicating that the remittance has not been performed in response to the transmission request transmitted from the user A to the user B in the talk room. , It is displayed only in the talk room displayed in the display area 28 of the user terminal 20A of the user A.
  • the remittance is not performed with the user who has remitted the money only to the talk room displayed in the display area 28 of the user terminal 20A of the user A who is the administrator, as an example, not limited to the information processing. Since the information that the user can understand is displayed, the amount of information processing of the server 10 can be reduced. Further, as an example, but not limited to, the server 10 can provide a talk room that does not cause discomfort to a user who has not sent money.
  • the input to the input unit 22 for the talk room displayed in the display area 28 of the user terminal 20B by the user B is the input for the display regarding the remittance request from the user A to the user B displayed in the talk room.
  • the server 10 goes to the input unit 22 by the user B for the display related to the remittance request displayed in the talk room displayed in the display area 28 of the user terminal 20B, which is transmitted from the user terminal 20C of the user C to the user terminal 20B.
  • the server 10 executes a process related to the remittance from the user B to the user C based on the information regarding the remittance from the user B to the user C.
  • the remittance request can be executed even if the remittance recipient is changed, so that the convenience of the user can be improved.
  • this embodiment is not limited, but as an example, in the server 10, an image (for example, a photograph) posted on a talk room by a predetermined user can be purchased by another user.
  • the server 10 receives the photo data from the user terminal 20 of a predetermined user, and transmits the received photo data to each user terminal 20 at a low resolution.
  • the remittance recipient is referred to as user A
  • the user who uploads the photo data to the server 10 is referred to as user B
  • user who purchases the photo data is referred to as user C.
  • the contents described in this embodiment can be appropriately applied to each of the other embodiments.
  • FIG. 37 is a flowchart showing information processing according to the eighth embodiment.
  • FIG. 38 is a diagram showing an outline of information processing according to the eighth embodiment.
  • the same components as those in the above-described embodiment are appropriately designated with the same reference numerals, and the description thereof will be omitted or simplified.
  • FIG. 37 is a flowchart on the premise that the procedures S111 to S151 in FIG. 2 have been completed.
  • a procedure for a user (here, user C) who purchases photo data uploaded by a predetermined user (here, user B) to remit to a remittance recipient (here, user A) will be described.
  • step S861 the user terminal 20B is not limited to, but as an example, first-resolution photo data is generated based on the input to the input unit 22 by the user B.
  • step S862 the user terminal 20B transmits photo data of the first resolution to the server 10 as an example, not limited to the above.
  • the server 10 stores the first resolution photographic data in the storage unit 15 as an example, not a limitation.
  • the server 10 generates photographic data having a second resolution indicating a resolution lower than the first resolution, based on the photographic data having the first resolution.
  • the server 10 is not limited to, but as an example, generates a photo-posted image T31 including the second-resolution photo data shown in FIG. 38 (a) (here, the post-printing process).
  • the server 10 transmits the photo-posted image T31 to the user terminal 20 as an example, not a limitation.
  • the user terminal 20C displays the photo-posted image T32 as shown in FIG. 38 (a) in the display area 28 as an example, not a limitation.
  • the user terminal 20C determines that the purchase transition unit T321 has been selected when the input unit 22 receives an input for the icon of the purchase transition unit T321 included in the photograph posted image T32.
  • the photo purchase image T33 is displayed in the display area 28.
  • the photo purchase image T33 includes, for example, a photo selection unit T331, an amount display unit T332, a remittance destination T333, a remittance account setting unit T334, and a purchase confirmation unit T335.
  • the photo selection unit T331 is not limited to, but is, as an example, an area in which photo data of the second resolution is selectively posted.
  • the photo selection unit T331 includes, but is not limited to, the selection display icon T3311 as an example.
  • the control unit 11 determines that the selection display icon T3311 has been selected when the input unit 22 has an input to the selection display icon T3311, and changes the status of the selection display icon T3311 ( For example, give a number to change the color).
  • the amount display unit T332 is not a limitation but an area in which the purchase amount of photo data is displayed as an example.
  • the control unit 11 calculates the purchase price of the photo data corresponding to the selected selection display icon T3311 and causes the price display unit T332 to display the purchase price as an example, not limited to the control unit 11.
  • the remittance destination T333 is not limited, but is an area for displaying the remittance destination specified by referring to the talk room information D22 as an example.
  • the remittance account setting unit T334 is not limited, but as an example, when an input is made to the input unit 22, the remittance corresponding to the remittance account ID that can be used in a predetermined display format (pull-down as an example, not limited). This area displays the name of the account.
  • the control unit 11 determines the photo data to be purchased and the information regarding the purchase price (purchase information as an example, not the limitation) when the input unit 22 inputs to the purchase confirmation unit T335 as an example, not the limitation. .. Then, in step S882, the user terminal 20C transmits a purchase request including purchase information to the server 10.
  • step S891 the server 10 stores the purchase request in the storage unit 15.
  • the server 10 collates the user ID of the user C with the user ID of the [user ID] of the talk room information D12 based on the purchase request, not by limitation but as an example. That is, the control unit 11 confirms that the purchase request has been transmitted from the user terminal 20 of the user participating in the talk room, not as a limitation but as an example. As an example, the control unit 11 shifts to the remittance process when the user ID of the user C and the user ID of the [user ID] match as a result of collation. The server 10 executes the remittance process based on the purchase information as an example, not the limitation.
  • the control unit 11 specifies, as an example, not a limitation, a user ID of a remittance source and a remittance destination, a remittance account, and a purchase amount (remittance amount) based on purchase information.
  • the server 10 transmits a remittance notification including information on the user ID of the remittance source and the remittance destination, the remittance account, and the purchase amount to the payment server 30.
  • the payment server 30 transfers the value corresponding to the purchase amount from the value of the remittance account corresponding to the user ID of the remittance source to the value of the remittance account corresponding to the user ID of the remittance destination.
  • the payment server 30 sends information about the result of processing related to remittance to the server 10 as an example, but not by limitation. This completes the remittance process.
  • the server 10 acquires the first resolution photographic data from the storage unit 15 based on the purchase information. Then, the control unit 11 transmits the first resolution photographic data to the user terminal 20 of the user C.
  • the server 10 transmits a remittance completion notification including information on the purchase amount to the user terminal 20.
  • the user terminal 20A displays an image including content indicating the completion of remittance (as an example, not limited, 2,000 yen of the photo purchase price has been remitted) based on the remittance completion notification as an example, not limited.
  • the server 10 is not limited, but as an example, the content transmitted / received by the user participating in the talk room is not displayed to the user device 20 of the user who uploads the photo data to the server 10. You may send an image of the talk room.
  • the server 10 is not limited, but as an example, refers to the content information D13 to specify the content corresponding to the user other than the user B, exclude the specified content, and the user terminal of the user B.
  • the server 10 can post low-resolution photo data in the talk room and provide the user with a high-resolution photo in response to the user's purchase request.
  • the server 10 can compress the capacity of the data to be transmitted / received in order to post the photo data having a low resolution, so that the processing speed can be improved.
  • the convenience of the user can be improved.
  • B1, B2, B3 ... Bus, N ... Network, 1 ... Communication system, 10 ... Server, 20 ... User terminal, 30 ... Payment server, 11,21,31 ... -Control unit, 12, 22, 32 ... Input unit, 13, 23, 33 ... Output unit, 14, 24, 34 ... Communication I / F, 15, 25, 35 ... Storage unit.

Landscapes

  • Business, Economics & Management (AREA)
  • Engineering & Computer Science (AREA)
  • Strategic Management (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Accounting & Taxation (AREA)
  • Tourism & Hospitality (AREA)
  • Economics (AREA)
  • Primary Health Care (AREA)
  • General Health & Medical Sciences (AREA)
  • Human Resources & Organizations (AREA)
  • Marketing (AREA)
  • Health & Medical Sciences (AREA)
  • Finance (AREA)
  • Computer Security & Cryptography (AREA)
  • Development Economics (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Computing Systems (AREA)
  • Information Transfer Between Computers (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Operations Research (AREA)
PCT/JP2021/023601 2020-06-30 2021-06-22 プログラム、情報処理方法、およびサーバ WO2022004487A1 (ja)

Priority Applications (2)

Application Number Priority Date Filing Date Title
KR1020227046407A KR20230019164A (ko) 2020-06-30 2021-06-22 프로그램, 정보 처리 방법 및 서버
CN202180046960.XA CN115997227A (zh) 2020-06-30 2021-06-22 程序、信息处理方法及服务器

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2020-113639 2020-06-30
JP2020113639A JP7108361B2 (ja) 2020-06-30 2020-06-30 プログラム、情報処理方法、およびサーバ

Publications (1)

Publication Number Publication Date
WO2022004487A1 true WO2022004487A1 (ja) 2022-01-06

Family

ID=79316214

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2021/023601 WO2022004487A1 (ja) 2020-06-30 2021-06-22 プログラム、情報処理方法、およびサーバ

Country Status (4)

Country Link
JP (2) JP7108361B2 (enrdf_load_stackoverflow)
KR (1) KR20230019164A (enrdf_load_stackoverflow)
CN (1) CN115997227A (enrdf_load_stackoverflow)
WO (1) WO2022004487A1 (enrdf_load_stackoverflow)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR102723975B1 (ko) * 2022-03-14 2024-10-31 주식회사 카카오 송금 서비스를 위한 방법 및 장치

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2017531866A (ja) * 2014-10-27 2017-10-26 フェイスブック，インク． メッセージベースのコンテキスト・プロンプトを使用した支払いの送信および受信の促進
JP2018032200A (ja) * 2016-08-24 2018-03-01 Ｌｉｎｅ株式会社 プログラム、情報処理方法、及び情報処理端末
WO2018213508A1 (en) * 2017-05-16 2018-11-22 Apple Inc. User interfaces for peer-to-peer transfers

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101654261B1 (ko) * 2015-06-25 2016-09-05 주식회사 카카오 링크 정보에 대응하는 오픈 채팅방을 통해 메시지 서비스를 제공하는 메시지 서비스 제공 방법 및 상기 메시지 서비스 제공 방법을 수행하는 메시지 서버 및 단말
US11449785B2 (en) * 2016-02-24 2022-09-20 Line Corporation Method and system for artificial intelligence learning using messaging service and method and system for relaying answer using artificial intelligence
JP2019028735A (ja) 2017-07-31 2019-02-21 Ｈｒソリューションズ株式会社 メッセージ管理装置、方法およびプログラム
JP7168309B2 (ja) * 2017-11-07 2022-11-09 ＬＩＮＥ Ｐａｙ株式会社 情報処理プログラム、方法、装置、及びシステム
KR20190115652A (ko) 2018-04-03 2019-10-14 라인 페이 가부시키가이샤 송금 기능이 탑재된 메신저에서 메시지 내용을 인식하여 송금 기능을 제공하는 방법 및 시스템

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2017531866A (ja) * 2014-10-27 2017-10-26 フェイスブック，インク． メッセージベースのコンテキスト・プロンプトを使用した支払いの送信および受信の促進
JP2018032200A (ja) * 2016-08-24 2018-03-01 Ｌｉｎｅ株式会社 プログラム、情報処理方法、及び情報処理端末
WO2018213508A1 (en) * 2017-05-16 2018-11-22 Apple Inc. User interfaces for peer-to-peer transfers

Also Published As

Publication number Publication date
JP2022012086A (ja) 2022-01-17
JP7108361B2 (ja) 2022-07-28
CN115997227A (zh) 2023-04-21
KR20230019164A (ko) 2023-02-07
JP2022137185A (ja) 2022-09-21
JP7645218B2 (ja) 2025-03-13

Similar Documents

Publication Publication Date Title
US11900491B2 (en) Systems and methods for executing and delivering electronic documents
TWI706368B (zh) 基於區塊鏈的服務租賃方法、裝置、系統及電子設備
US11748469B1 (en) Multifactor identity authentication via cumulative dynamic contextual identity
US20230409679A1 (en) Systems and methods for a tokenized virtual persona for use with a plurality of software applications
EP3982281A1 (en) Digital asset custodial system
US20230254300A1 (en) Authentication of avatars for immersive reality applications
JP7189186B2 (ja) プログラム、情報処理方法、および端末
TWI746399B (zh) 基於區塊鏈的資訊讀寫方法以及裝置
US20190199965A1 (en) Server and method enabling augmented reality (ar) object sharing
US11736449B2 (en) System and method to allow anonymous users to contribute multimedia content across multiple digital workspaces
US11991286B2 (en) Systems and methods for using a non-fungible digital asset to facilitate accessing an access-restricted resource
US20190295083A1 (en) The method for executing a digital value transfer transaction and the digital value transfer system for its implementation
US20230325827A1 (en) Information processing apparatus, program, method and terminal
US12086630B2 (en) Method and system for generating and managing smart contract
WO2022004487A1 (ja) プログラム、情報処理方法、およびサーバ
US20230039832A1 (en) Method and system for transaction of digital asset
CN111435503B (zh) 用于获取电子凭据的方法和装置
US20230401550A1 (en) Fee Distribution System and Method
US12212676B2 (en) Systems and methods for sharing validated user activity
US12087253B1 (en) Transparent data display window system and method
US12159278B1 (en) Virtual asset freeze
CN120429845B (zh) 基于区块链的数字藏品确权方法及系统
US20230336558A1 (en) System aggregator and project role verification system
KR101360933B1 (ko) 상조 서비스 지원 방법 및 그 시스템
KR20240075368A (ko) 인스턴트 메시징 서비스에서 대화 기반 전자 계약 방법 및 장치

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21833021

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 20227046407

Country of ref document: KR

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21833021

Country of ref document: EP

Kind code of ref document: A1