Support device, support method, and information processing method

The support device addresses the lack of support for challenged users by providing store information and clerk assistance, improving the usability of payment methods for challenged users.

JP2024168687APending Publication Date: 2024-12-05THE JAPAN RES INST
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
JP2023085564
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2023-05-24
Publication Date
2024-12-05

AI Technical Summary

Technical Problem

Existing systems lack support mechanisms for challenged users when using payment methods.

Method used

A support device that includes a terminal information receiving unit, support acquisition unit, and transmission unit to provide information to a user's terminal device or store clerk, utilizing store and user management units to determine suitable stores and assist with payment methods.

Benefits of technology

Enables support for challenged users by providing store information, clerk assistance, and recording payment situations, enhancing the usability of payment methods.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2024168687000001_ABST
    Figure 2024168687000001_ABST
Patent Text Reader

Abstract

To solve such a problem that there has been no mechanism for support when a challenged user uses settlement means in a conventional support device.SOLUTION: A challenged user is supported to use settlement means by a support device 1 which comprises: a terminal information reception unit 121 that receives a user identifier to identify the challenged user; a support acquisition unit 134 that acquires support information to support the user who is identified by the user identifier to use the settlement means at a store; and a support transmission unit 142 that transmits the support information to a terminal device 2 of the user.SELECTED DRAWING: Figure 2
Need to check novelty before this filing date? Find Prior Art

Description

[Technical field]

[0001] The present invention relates to an assistance device and the like that assists challenged users in using payment methods. The term "challenged" refers to people with disabilities. [Background technology]

[0002] Conventionally, there has been a customer support device that allows a store to provide some kind of support to customers who need assistance from those around them (see Patent Document 1). This customer support device is characterized by having an input unit to which image information of a customer waiting to pay at a store is input, and an output unit that outputs notification instruction information to a notification unit that notifies a store clerk when a recognition unit recognizes that the input image information includes a predetermined mark. [Prior art documents] [Patent documents]

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

[0004] However, in the prior art, there was no mechanism to assist challenged users in using payment methods. [Means for solving the problem]

[0005] The support device of the first invention is a support device that includes a terminal information receiving unit that receives terminal information including a user identifier that identifies a challenged user, a support acquisition unit that acquires support information that assists a user identified by the user identifier in using a payment method at a store, and a support transmission unit that transmits the support information to the user's terminal device.

[0006] With this configuration, it is possible to provide information to assist a challenged user in using a payment method.

[0007] In addition, in the support device of the second invention, compared to the first invention, the support acquisition unit refers to a store management unit in which one or more pieces of store information each having one or more store attribute values ​​corresponding to a store identifier are stored, determines a store whose one or more store attribute values ​​match the recommendation conditions, and acquires support information which is the store information of the store.

[0008] With this configuration, it is possible to provide information on stores suitable for using payment methods for challenged users.

[0009] In addition, the support device of the third invention, compared to the second invention, includes an evaluation source acquisition unit that acquires one or more types of evaluation source information, such as the time from when the user leaves home to when payment is completed, the time from when the user arrives at the store to when payment is completed, or the user's evaluation of the store after payment, in association with a store identifier, and an evaluation unit that acquires an evaluation value for the store using the one or more types of evaluation source information and accumulates the evaluation value in association with the store identifier of the store, and the support acquisition unit refers to the store management unit and uses one or more store attribute values ​​of good stores corresponding to evaluation values ​​greater than or equal to a threshold value to determine similar stores whose similarity to good stores is greater than or equal to a threshold value, and acquires support information, which is store information of the similar stores.

[0010] With this configuration, it is possible to provide information on stores suitable for using payment methods for challenged users.

[0011] In addition, compared to the first invention, the support device of the fourth invention is a support device in which the support acquisition unit refers to a user management unit in which one or more pieces of user information having one or more user attribute values ​​are stored, and acquires store clerk presented information, which is one or more attribute values ​​of the user and is information to be presented to a store clerk.

[0012] With this configuration, user information can be provided to a store clerk who assists a challenged user when the user uses a payment method.

[0013] Further, in the support device of the fifth invention, in comparison with the fourth invention, the support transmitter transmits store clerk presented information when the terminal information satisfies a transmission condition.

[0014] With this configuration, it is possible to provide information at an appropriate time to assist a challenged user in using a payment method.

[0015] In addition, the support device of the sixth invention, compared to the first invention, further includes a payment receiving unit that receives payment information regarding a payment made using a payment means in association with a user identifier, and the support acquisition unit is a support device that acquires support information, which is historical graphical information, which is graphical information regarding the history of use of the payment means, using one or more payment information associated with the user identifier.

[0016] With this configuration, a challenged user can be provided with a payment method usage history in an easy-to-understand manner.

[0017] In addition, the support device of the seventh invention is an support device in which, compared to the first invention, the terminal information receiving unit receives record information including sound recording information or video recording information from the terminal device, and further includes a recording unit that accumulates the record information, and a record transmitting unit that transmits the record information.

[0018] With this configuration, the circumstances under which a challenged user uses a payment method can be recorded.

[0019] In addition, the terminal device of the eighth invention is a terminal device having a terminal receiving unit that receives input which is one or more types of recorded information of audio and image, and a terminal transmitting unit that transmits the recorded information to the support device when the recorded information satisfies a recording condition.

[0020] With this configuration, the circumstances under which a challenged user uses a payment method can be recorded. Effect of the Invention

[0021] The support device according to the present invention can support a challenged user when using a payment method. [Brief description of the drawings]

[0022] [Figure 1] Conceptual diagram of support system A in embodiment 1. [Diagram 2] Block diagram of the support system A [Diagram 3] A flowchart for explaining an example of the operation of the support device 1. [Figure 4] A flowchart illustrating an example of the support acquisition process. [Diagram 5] Flowchart for explaining an example of the store determination process [Figure 6] A flowchart illustrating an example of the store clerk support information acquisition process. [Figure 7] A flowchart illustrating an example of the evaluation value acquisition process [Figure 8] A flowchart for explaining an example of the operation of the terminal device 2 [Figure 9] A diagram showing the store management table [Figure 10] The user management table [Figure 11] The figure shows the settlement management table. [Figure 12] The figure shows the settlement management table. [Figure 13] A diagram showing an example of the output [Figure 14] Overview of the computer system [Figure 15] Block diagram of the computer system DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0023] Hereinafter, an embodiment of the support device etc. will be described with reference to the drawings. Note that, in the embodiments, components with the same reference numerals perform similar operations, so that repeated description may be omitted.

[0024] (Embodiment 1) In this embodiment, a support device that transmits support information to support a challenged user (hereinafter referred to as "user") in using a payment method to the user's terminal device or a store device of a store clerk will be described. Note that the support information is, for example, store information of a store where a challenged user can appropriately use a payment method, information about a challenged user, information to be presented to a store clerk, or information based on the challenged user's usage history of a payment method.

[0025] In this embodiment, a support device that determines stores similar to a good store and transmits support information, which is information on the similar stores, to a user's terminal device will be described.

[0026] In this embodiment, a support device that transmits information to be presented to a store clerk to a user's terminal device when a predetermined condition is satisfied will be described.

[0027] Furthermore, in this embodiment, we will explain a user's terminal device that transmits recording information, which is audio or video information at the store, when the recording conditions are met, and a support device that receives and stores the recording information from the terminal device.

[0028] In this specification, information X being associated with information Y means that information Y can be obtained from information X, or information X can be obtained from information Y, and the method of association is not important. Information X and information Y may be linked, may exist in the same buffer, information X may be included in information Y, or information Y may be included in information X, etc.

[0029] 1 is a conceptual diagram of a support system A according to the present embodiment. The support system A includes a support device 1, one or more terminal devices 2, and one or more store devices 3.

[0030] The support device 1 is a device that supports a challenged user in using a payment method. The support device 1 is a server in this embodiment. The support device 1 is, for example, a cloud server, an ASP server, or the like.

[0031] The support device 1 and one or more terminal devices 2 are usually capable of communicating with each other via a network such as the Internet. The support device 1 and one or more store devices 3 are usually capable of communicating with each other via a network such as the Internet.

[0032] The terminal device 2 is a terminal used by a user. The terminal device 2 may be, for example, a so-called personal computer, a tablet terminal, a smartphone, or the like, and the type of the terminal device 2 is not important.

[0033] The in-store device 3 is a device used in a store. The in-store device 3 may be a device used by a store clerk. The in-store device 3 may be, for example, a so-called personal computer, a tablet terminal, a smartphone, or the like, and the type does not matter. The in-store device 3 may be, for example, a server, a cloud server, an ASP server, or the like.

[0034] 2 is a block diagram of a support system A according to the present embodiment. A support device 1 constituting the support system A includes a storage unit 11, a receiving unit 12, a processing unit 13, and a transmitting unit .

[0035] The storage unit 11 includes a store management unit 111 and a user management unit 112. The receiving unit 12 includes a terminal information receiving unit 121 and a payment receiving unit 122. The processing unit 13 includes an evaluation source acquisition unit 131, a recording unit 132, an evaluation unit 133, and a support acquisition unit 134. The transmitting unit 14 includes a record transmitting unit 141 and a support transmitting unit 142.

[0036] The terminal device 2 includes a terminal storage unit 21, a terminal reception unit 22, a terminal processing unit 23, a terminal transmission unit 24, a terminal reception unit 25, and a terminal output unit 26. The device processing unit 23 includes a terminal recording unit 231.

[0037] Various types of information are stored in the storage unit 11 constituting the support device 1. The various types of information are, for example, store information (to be described later), user information (to be described later), one or more pieces of payment information, and recommendation conditions.

[0038] Payment information is information regarding a payment being made using a payment means. The payment information includes, for example, the amount paid using the payment means, the store identifier of the store where the payment means was used, and a product identifier. The product identifier is an identifier of the product. The product identifier is, for example, the product name and the product ID. The payment information includes, for example, time information specifying when the payment means was used. The time information is, for example, the date, time, and day. The payment information includes, for example, supporting clerk and record information. The supporting clerk is information regarding the clerk who supported the user at the time of payment. The supporting clerk is, for example, the name of the clerk and the clerk ID. The record information here includes audio or video recorded when the user was shopping.

[0039] A payment method is a method that can be used when making a purchase. A payment method is a method other than cash. For example, a payment method is a credit card, electronic money, or a point card. However, the type of payment method is not important.

[0040] Recommendation conditions are conditions for recommending a store to a user. Recommendation conditions are, for example, conditions based on one or more store attribute values. Recommendation conditions are, for example, conditions based on one or more user attribute values. Recommendation conditions are, for example, conditions based on one or more store attribute values ​​and one or more user attribute values. Recommendation conditions are, for example, common recommendation conditions or specific recommendation conditions. Common recommendation conditions are conditions that apply to all users when recommending a store. Specific recommendation conditions are conditions for one user.

[0041] The store management unit 111 stores one or more pieces of store information. Store information is information related to a store. The store information corresponds to a store identifier. The store information has one or more store attribute values. The store information corresponds to, for example, one or more user identifiers. Such user identifiers are identifiers of one or more users who recommend the use of the store.

[0042] The store identifier is information for identifying a store. The store identifier is, for example, a store ID or a store name.

[0043] The store attribute value is an attribute value of a store, such as a store address, store location information, store type, staff presence / absence flag, product display method information, wheelchair information, and evaluation value.

[0044] Store location information is information about the location of a store. Location information is information that identifies a location. Location information is usually (latitude, longitude), but it may be an address or part of an address (for example, up to the name of the city, town, or village). Store type is information that identifies the type of store.

[0045] The store clerk presence / absence flag is information indicating whether or not a store clerk is available to assist with shopping. The store clerk presence / absence flag can be, for example, "yes" (e.g., "1") or "no" (e.g., "0").

[0046] The product display method information is information that specifies the method of displaying products. For example, the product display method information is "messy (e.g., "0")", "tidy (e.g., "1"), and "name of the sales floor that is neatly arranged."

[0047] The information relating to wheelchairs is, for example, information relating to whether or not a road can be passed by a wheelchair, whether or not a road is suitable for shopping in a wheelchair, or the degree of suitability.

[0048] The evaluation value is information that indicates the evaluation of a store. The evaluation value is, for example, one of five levels from "1" to "5", one of "A", "B", or "C", or a score from 0 to 100. However, the range or level of the evaluation value is not important.

[0049] The user management unit 112 stores one or more pieces of user information. The user information is information about a challenged user. The user information corresponds to a user identifier. The user information has one or more user attribute values. The user information may correspond to one or more pieces of payment information.

[0050] The user identifier is information for identifying a user, and is, for example, a user ID, a user name, a phone number, a credit card number, or an electronic money application ID.

[0051] The user attribute value is a user's attribute value. The user attribute value is, for example, an address, home location information, the user's disability level, the user's disability content, one or more unique recommendation conditions, one or more payment method identifiers, an upper limit, and a guardian identifier. The disability content is information indicating the content of the user's disability.

[0052] The payment method identifier is information that identifies a payment method. For example, the payment method identifier is a credit card number or an ID of an electronic money application.

[0053] The upper limit is the upper limit of a user's purchases. The upper limit is the upper limit of purchases that a user can make using a payment method. The upper limit is usually the amount of money, but it can also be the number of purchases. The upper limit is, for example, the upper limit of the amount of money or the number of purchases in a unit period (e.g., one month).

[0054] A guardian identifier is information that identifies a user's guardian. Examples of the guardian identifier include the name of the guardian, the guardian's ID, and notification information for the guardian. Notification information is information for sending information. Examples of the notification information include a phone number, an email address, and an IP address of a terminal.

[0055] The receiving unit 12 receives various instructions and information, such as user information, a user identifier, terminal information, record information, and payment information.

[0056] The receiving unit 12 receives various instructions and information, for example, from the terminal device 2. The receiving unit 12 may receive various instructions and information from the in-store device 3. The various instructions and information include, for example, terminal information, support instructions, payment information, output instructions, evaluations, and store recommendation instructions, which will be described later.

[0057] The assistance instruction is an instruction to assist the user. The assistance instruction usually includes a user identifier.

[0058] An output instruction is an instruction to output user information. An output instruction usually includes one or more user identifiers.

[0059] The evaluation here is the user's evaluation of the store. The evaluation here is usually information indicating the degree of support the store provides to the user. The evaluation here is, for example, from "1" to "5", "A", "B", "C", etc., but the level is not important.

[0060] The store recommendation instruction is an instruction to recommend a store to be used by the user. The store recommendation instruction usually includes a user identifier.

[0061] The terminal information receiving unit 121 receives terminal information. The terminal information is information transmitted from the terminal device 2 or the store device 3. The terminal information is information acquired by the terminal device 2 or the store device 3. The terminal information is, for example, a user identifier or recorded information. The terminal information is, for example, a part or all of the user information. Note that a part or all of the user information may simply be referred to as user information. The recorded information is audio information recorded in the store, or video information recorded in the store. The recorded information is information recorded when a user is making noise in the store. The recorded information may include audio information of the user, or may include audio information of a store clerk.

[0062] The payment receiving unit 122 receives the payment information in association with the user identifier. The payment receiving unit 122 receives the payment information from, for example, the terminal device 2. The payment receiving unit 122 receives the payment information from, for example, the in-store device 3.

[0063] The processing unit 13 performs various types of processing. The various types of processing are, for example, processing performed by an evaluation source acquisition unit 131, a recording unit 132, an evaluation unit 133, and a support acquisition unit .

[0064] The rating source acquisition unit 131 acquires one or more pieces of rating source information. The rating source acquisition unit 131 acquires one or more types of rating source information in association with a store identifier.

[0065] The evaluation source information is information used when evaluating a store. One or more types of evaluation source information may be, for example, the time from when the user leaves home to when payment is completed, the time from when the user arrives at the store to when payment is completed, or the user's evaluation of the store after payment.

[0066] The evaluation source acquisition unit 131 receives, for example, the time from when the user leaves home until the payment is completed from the terminal device 2 of the user.

[0067] The evaluation source acquisition unit 131 receives, for example, the time from arrival at the store to completion of payment from the terminal device 2 or the store device 3 of the user.

[0068] The evaluation source acquisition unit 131 receives, for example, a user's evaluation of a store after payment from the user's terminal device 2. Such a user's evaluation may be an evaluation by a parent or guardian of the user.

[0069] The recording unit 132 accumulates the record information received by the terminal information receiving unit 121. The recording unit 132 accumulates the record information in association with a user identifier. The recording unit 132 accumulates the record information in association with, for example, payment information. The recording unit 132 usually accumulates the record information in the storage unit 11, but may accumulate the record information in another device (not shown).

[0070] The evaluation unit 133 obtains an evaluation value for a store using one or more types of evaluation source information, and stores the evaluation value in association with the store identifier of the store. There is no restriction on the algorithm by which the evaluation unit 133 obtains the evaluation value.

[0071] The evaluation unit 133 normally acquires a higher evaluation value the shorter the time from when the user leaves home to when the payment is completed.

[0072] The evaluation unit 133 normally acquires a higher evaluation value the shorter the time from arrival at the store to completion of payment.

[0073] The evaluation unit 133 normally acquires a higher evaluation value as the user's evaluation of the store after payment becomes higher.

[0074] The evaluation unit 133, for example, substitutes one or more pieces of evaluation source information into an arithmetic formula to calculate an evaluation value. The evaluation unit 133, for example, calculates an evaluation value using a decreasing function with a parameter being the time from when the user leaves home to when payment is completed or the time from when the user arrives at the store to when payment is completed. The evaluation unit 133, for example, calculates an evaluation value using an increasing function with a parameter being one or more users' evaluations of the store after payment.

[0075] The evaluation unit 133 obtains an evaluation value by machine learning prediction processing using, for example, a vector having two or more pieces of evaluation source information as elements and a learning model. The evaluation unit 133, for example, substitutes a vector having two or more pieces of evaluation source information as elements, a learning model, and a machine learning prediction module, executes the prediction module, and obtains an evaluation value.

[0076] The learning model is information configured by the learning process of machine learning, and is information used in the prediction process of machine learning. The learning model may be called a learner, a classifier, a classification model, or the like. The machine learning algorithm may be deep learning, random forest, decision tree, SVM, or the like. For machine learning, various machine learning functions such as the TensorFlow (registered trademark) library, the random forest module of the R language, fastText, TinySVM, and various existing libraries can be used.

[0077] In addition, the learning model is information acquired by a learning means (not shown) that provides two or more pieces of teacher data each having two or more pieces of evaluation source information and an evaluation value to a machine learning learning module and executes the learning module.

[0078] The evaluation unit 133 acquires, for example, an evaluation value paired with a vector that is closest to a vector having two or more pieces of evaluation source information as elements from the correspondence table. Note that the correspondence table is a table having two or more pieces of correspondence information that have vectors having two or more pieces of evaluation source information as elements and evaluation values.

[0079] The support acquisition unit 134 acquires one or more pieces of support information. The support information is information that supports a user identified by a user identifier in using a payment method in a store.

[0080] Support information is information for supporting a user. Support information is information for supporting a user's shopping. Support information is information for supporting a user's shopping using a payment method. Support information may also be information for supporting a store clerk. Support information is, for example, store information, store clerk presented information described below, and history information described below. History information is, for example, historical graphical information described below.

[0081] The support acquisition unit 134, for example, refers to the store management unit 111, determines one or more stores whose one or more store attribute values ​​match the recommendation conditions, and acquires support information that is store information of each of the one or more stores. The store information acquired by the support acquisition unit 134 is information on stores that are proposed to be used by the user.

[0082] The support acquisition unit 134 determines one or more stores that match the recommendation conditions, for example, using one or more store attribute values ​​and one or more user attribute values, and acquires support information that is store information for each of the one or more stores.

[0083] The support acquisition unit 134 determines one or more stores that match the user's unique recommendation conditions, for example, by using one or more types of information among one or more store attribute values ​​and one or more user attribute values, and acquires support information, which is store information for each of the one or more stores.

[0084] The support acquisition unit 134 determines one or more stores that meet the common recommendation conditions using, for example, one or more types of information among one or more store attribute values ​​and one or more user attribute values, and acquires support information, which is store information for each of the one or more stores.

[0085] The support acquisition unit 134 determines one or more stores that match the user's unique recommendation conditions and common recommendation conditions, for example, by using one or more types of information among one or more store attribute values ​​and one or more user attribute values, and acquires support information, which is store information for each of the one or more stores.

[0086] The support acquisition unit 134, for example, refers to the store management unit 111 and uses one or more store attribute values ​​of a good store corresponding to an evaluation value above a threshold or greater than the threshold to determine similar stores whose similarity to the good store is above a threshold or greater than the threshold, and acquires support information, which is store information of the similar stores.

[0087] The support acquisition unit 134, for example, refers to the user management unit 112 and acquires store clerk presented information, which is one or more attribute values ​​of the user. The store clerk presented information is information that should be presented to the store clerk. The store clerk presented information is, for example, one or more attribute values ​​of the user. The store clerk presented information includes, for example, the degree of disability of the user or the content of the user's disability. The support acquisition unit 134, for example, transmits the store clerk presented information.

[0088] The support acquisition unit 134 acquires support information, which is graphical information about the history of using the payment means, by using one or more pieces of payment information associated with the user identifier. The support acquisition unit 134 acquires support information, which is different graphical information about the history, depending on the user, for example.

[0089] The transmitting unit 14 transmits various types of information, such as record information and support information.

[0090] The record transmitting unit 141 transmits the record information received by the terminal information receiving unit 121. The record transmitting unit 141 transmits the record information received by the terminal information receiving unit 121 to a guardian terminal (not shown) identified by a guardian identifier associated with a user identifier paired with the record information.

[0091] For example, when the recording information meets the transmission conditions, the record transmission unit 141 transmits the recording information to a parent's terminal (not shown) identified by a parent identifier associated with the user identifier paired with the recording information.

[0092] The transmission condition is a condition for transmitting information. For example, the transmission condition is a condition for transmitting recorded information. For example, the transmission condition is a condition for transmitting store clerk-presented information. For example, the transmission condition is that the feature amount of the voice information of the recorded information, which is an example of terminal information received by the terminal information receiving unit 121, is information indicating that the user is making noise. For example, the transmission condition is that after a challenged person's entry into a store is detected, the time from the entry to the payment is equal to or longer than a threshold value.

[0093] The transmission condition is, for example, that a predetermined user identifier is included in the terminal information received by the terminal information receiving unit 121. For example, when the terminal information includes the user identifier of a user who needs support, the support information is transmitted to the user's terminal device 2 or the store device 3 so that the store clerk can see the user's information (for example, the details of the problem).

[0094] When a transmission instruction is received, the record transmitting unit 141 transmits one or more pieces of record information corresponding to the transmission instruction to the terminal that transmitted the transmission instruction.

[0095] In other words, the transmission of the record information by the record transmission unit 141 may be automatic transmission or may be transmission based on an instruction.

[0096] The support transmitting unit 142 transmits the support information acquired by the support acquisition unit 134. For example, the support transmitting unit 142 transmits the support information acquired by the support acquisition unit 134 to the terminal device 2. For example, the support transmitting unit 142 may transmit the support information acquired by the support acquisition unit 134 to the in-store device 3.

[0097] For example, when the terminal information received by the terminal information receiving unit 121 satisfies a transmission condition, the support transmitting unit 142 transmits store clerk presented information.

[0098] Various types of information are stored in the terminal storage unit 21 constituting the terminal device 2. The various types of information include, for example, a user identifier and recording conditions to be described later.

[0099] The terminal reception unit 22 receives various information, instructions, and the like. The various information, instructions, and the like may be called input. The input is, for example, a voice, an image, or a touch. The input is, for example, information indicating the start of a user's movement, information indicating that the user has arrived at a store, a payment instruction, an output instruction, an evaluation, sound information, or a video.

[0100] A payment instruction is an instruction to make a payment. The payment instruction includes all or part of the payment information.

[0101] Here, reception typically refers to reception of information input from an input device such as a microphone, camera, keyboard, mouse, or touch panel, but may also be a concept including reception of information transmitted via a wired or wireless communication line, and reception of information read from a recording medium such as an optical disk, a magnetic disk, or a semiconductor memory.

[0102] The means for inputting various information and instructions may be anything, such as a microphone, a camera, a touch panel, a keyboard, a mouse, or a menu screen.

[0103] The terminal processing unit 23 performs various types of processing. For example, the various types of processing are processing for converting received information, instructions, etc. into information or instructions with a structure to be transmitted. For example, the various types of processing are processing for converting received information into information with a structure to be output.

[0104] The terminal recording unit 231 constituting the device processing unit 23 starts audio or video recording and acquires the recording information when the input satisfies the recording conditions. The terminal recording unit 231 may store the recording information in the terminal storage unit 21.

[0105] The recording condition is, for example, a condition for transmitting audio or video information. The recording condition is, for example, a condition for starting audio or video information. The recording condition is, for example, a condition related to one or more features of the received sound information. The condition related to the feature of the sound information is, for example, that the volume is equal to or greater than a threshold. The condition related to the feature of the sound information is, for example, that the frequency is equal to or greater than a threshold. The recording condition is, for example, that an assistance instruction is input.

[0106] The terminal recording unit 231 may automatically record audio or video when it detects that a user has entered a store, and obtain the recorded information. In this case, the recording condition is that the user's entry into a store is detected. The terminal recording unit 231 may also record audio or video when an instruction is accepted, and obtain the recorded information. In this case, the recording condition is that an instruction to record audio or video is accepted. The terminal recording unit 231 may also record audio or video information together with payment availability information (e.g., information indicating that an attempt to make a payment was unsuccessful).

[0107] The terminal transmitting unit 24 transmits the record information acquired by the terminal recording unit 231 to the support device 1 .

[0108] The terminal receiving unit 25 receives various types of information, instructions, etc. The various types of information, instructions, etc. are, for example, support information, record information, etc.

[0109] The terminal output unit 26 outputs various types of information, such as support information and record information.

[0110] Here, output usually means display on a display, but it may also be a concept that includes projection using a projector, printing on a printer, sound output, transmission to an external device, storage on a recording medium, and handing over the processing results to other processing devices or other programs.

[0111] The in-store device 3 receives and outputs information from, for example, the support device 1. Such information is, for example, support information. The support information is, for example, store clerk-presented information.

[0112] The storage unit 11, the store management unit 111, the user management unit 112, and the terminal storage unit 21 are preferably non-volatile recording media, but may also be realized as volatile recording media.

[0113] There is no restriction on the process by which information is stored in the storage unit 11, etc. For example, information may be stored in the storage unit 11, etc. via a recording medium, information transmitted via a communication line, etc. may be stored in the storage unit 11, etc., or information inputted via an input device may be stored in the storage unit 11, etc.

[0114] The receiver 12, the terminal information receiver 121, the payment receiver 122, and the terminal receiver 25 are usually realized by wireless or wired communication means, but may be realized by means for receiving broadcast.

[0115] The processing unit 13, the evaluation source acquisition unit 131, the recording unit 132, the evaluation unit 133, the support acquisition unit 134, and the device processing unit 23 can usually be realized by a processor, a memory, etc. The processing procedure of the processing unit 13, etc. is usually realized by software, and the software is recorded in a recording medium such as a ROM. However, it may be realized by hardware (dedicated circuit). The processor may be a CPU, MPU, GPU, etc., and the type is not important.

[0116] The transmitting unit 14, the record transmitting unit 141, the support transmitting unit 142, and the terminal transmitting unit 24 are usually realized by wireless or wired communication means, but may be realized by broadcasting means.

[0117] The terminal reception unit 22 can be realized by a device driver for an input means such as a touch panel or a keyboard, or control software for a menu screen.

[0118] The terminal output unit 26 may or may not include an output device such as a display, a speaker, etc. The terminal output unit 26 may be realized by driver software for an output device, or a combination of driver software for an output device and an output device, etc.

[0119] Next, a description will be given of an example of the operation of the support system A. First, a description will be given of an example of the operation of the support device 1 with reference to the flowchart of FIG.

[0120] (Step S301) The terminal information receiving unit 121 judges whether or not a support instruction has been received from the terminal device 2. If a support instruction has been received, the process proceeds to step S302, and if a support instruction has not been received, the process proceeds to step S304.

[0121] The support instruction is, for example, a first support instruction or a second support instruction. The first support instruction and the second support instruction differ in the information requested. The first support instruction is, for example, an instruction that does not require a user attribute value. The second support instruction is, for example, an instruction that requires a user attribute value.

[0122] (Step S302) The support acquisition unit 134 acquires support information. An example of such support acquisition processing will be described with reference to the flowchart of FIG.

[0123] (Step S303) The support transmitter 142 transmits the support information acquired in step S302 to the terminal device 2. The process returns to step S301.

[0124] (Step S304) The terminal information receiving unit 121 judges whether or not the recording information, etc. has been received. If the recording information, etc. has been received, the process proceeds to step S305, and if the recording information, etc. has not been received, the process proceeds to step S311. The recording information, etc. is associated with a user identifier. It is preferable that the recording information, etc. is associated with a store identifier. Furthermore, the recording information, etc. may be just the recording information, or may include a user identifier and a store identifier.

[0125] (Step S305) The recording unit 132 stores the record information received in step S304 in the user management unit 112 in association with the user identifier. It is preferable that the recording unit 132 stores the record information received in step S304 in the user management unit 112 in association with the store identifier.

[0126] (Step S306) The processing unit 13 judges whether or not the record information received in step S304 matches the transmission condition. If the transmission condition is matched, the process proceeds to step S307, and if the transmission condition is not matched, the process proceeds to step S309.

[0127] (Step S307) The assistance acquisition unit 134 acquires sales clerk assistance information. An example of the sales clerk assistance information acquisition process will be described with reference to the flowchart of FIG.

[0128] (Step S308) The support sending unit 142 transmits the store clerk support information acquired in step S307, for example, to the terminal device 2 that transmitted the record information, etc. The support sending unit 142 acquires, for example, a store identifier that pairs with the received record information, etc., acquires a store device identifier that corresponds to the store identifier from the store management unit 111, and transmits the store clerk support information acquired in step S307 to the store device 3 identified by the store device identifier.

[0129] (Step S309) The processing unit 13 judges whether or not to transmit the record information to the user's guardian. If the record information is to be transmitted to the user's guardian, the process proceeds to step S310. If not, the process returns to step S301.

[0130] The processing unit 13 determines to transmit the record information to the user's guardian, for example, when a guardian identifier is paired with a user identifier and managed by the user management unit 112. The processing unit 13 determines to transmit the record information to the user's guardian, for example, when a flag indicating that the record information is to be transmitted to the guardian, paired with a user identifier, is managed by the user management unit 112. The processing unit 13 determines to transmit the record information to the user's guardian, for example, when it is determined in step S306 that the transmission conditions are met.

[0131] (Step S310) The record transmitting unit 141 transmits the record information to the guardian of the user. Then, the process returns to step S301.

[0132] For example, the record sending unit 141 obtains a guardian identifier that pairs with the user identifier of the user from the user management unit 112, and sends the record information to the guardian specified by the guardian identifier.

[0133] (Step S311) The payment receiving unit 122 determines whether or not payment information, etc. has been received. If payment information, etc. has been received, the process proceeds to step S312, and if not, the process proceeds to step S313.

[0134] The payment information, etc., is associated with the user identifier. It is preferable that the payment information, etc., has a store identifier, amount information, and purchased product information. It is preferable that the payment information, etc., is associated with the store identifier. The payment information, etc., may be payment information alone, or may include payment information plus one or more times of a first time and a second time. It is preferable that the product information is information related to a product, and includes, for example, product type information and product name.

[0135] (Step S312) The processing unit 13 associates the payment information received in step S311 with the user identifier and stores it in the user management unit 112. The process returns to step S301.

[0136] It is preferable that the processing unit 13 stores in the storage unit 11 one or more of the first time and the second time received in step S311 in association with the user identifier and the store identifier.

[0137] Furthermore, the processing unit 13 may perform processing for payment using the received payment information, and the device that performs processing for payment may be a payment device (not shown).

[0138] (Step S313) The receiving unit 12 judges whether or not an output instruction has been received from the terminal device 2. If an output instruction has been received, the process proceeds to step S314, and if not, the process proceeds to step S316. The output instruction includes a user identifier.

[0139] (Step S314) The support acquisition unit 134 acquires user information corresponding to the user identifier included in the output instruction from the user management unit 112. Such user information is, for example, one or more pieces of record information of the user, a rating input by the user, and one or more pieces of payment information of the user.

[0140] (Step S315) The transmission unit 14 transmits the user information acquired in step S314 to the terminal device 2 that has transmitted the output instruction. Return to step S301.

[0141] (Step S316) The receiving unit 12 judges whether or not a rating corresponding to the user identifier and the shop identifier has been received. If a rating has been received, the process proceeds to step S317. If a rating has not been received, the process proceeds to step S319.

[0142] (Step S317) The processing unit 13 stores the evaluation received in step S316 in the store management unit 111 in association with the user identifier and the store identifier.

[0143] (Step S318) The evaluation unit 133 acquires an evaluation value of the store identified by the store identifier. Return to step S301. An example of such evaluation value acquisition processing will be described with reference to the flowchart of FIG.

[0144] The evaluation value of a store here is usually information indicating evaluations of the store by two or more users. The evaluation unit 133 acquires one or more types of information from, for example, an evaluation paired with the store identifier, a first time paired with the store identifier, and a second time paired with the store identifier. Next, the evaluation unit 133 acquires an evaluation value using the acquired two or more types of information.

[0145] Furthermore, the evaluation unit 133 may obtain the evaluation value of each store at any timing or trigger.

[0146] (Step S319) The receiving unit 12 judges whether or not an instruction to recommend a store has been received. If an instruction to recommend a store has been received, the process proceeds to step S320, and if an instruction to recommend a store has not been received, the process returns to step S301.

[0147] (Step S320) The support acquisition unit 134 performs a store determination process. An example of the store determination process will be described with reference to the flowchart of FIG.

[0148] (Step S321) The support sending unit 142 sends the store information of one or more stores acquired in step S320 to the terminal device 2 that has sent the store recommendation instruction. Return to step S301.

[0149] In the flowchart of FIG. 3, the process ends when the power is turned off or an interrupt for ending the process occurs.

[0150] Next, an example of the support acquisition process in step S302 will be described with reference to the flowchart in FIG.

[0151] (Step S401) The support acquisition unit 134 acquires a user identifier.

[0152] (Step S402) The support acquisition unit 134 acquires one or more pieces of payment information paired with the user identifier from the user management unit 112. Here, the support acquisition unit 134 may acquire payment information for a specific period (e.g., the most recent month) from among the one or more pieces of payment information paired with the user identifier, or may acquire all payment information.

[0153] (Step S403) The support acquisition unit 134 acquires history information by using one or more pieces of payment information acquired in step S402.

[0154] History information is information relating to the history of use of a payment method. History information is, for example, the total amount spent. History information is, for example, the total amount spent in a unit period. History information is, for example, the total amount spent per store. History information is, for example, the total amount spent per type of product. The total amount may be the total amount spent to date or the total amount spent in a unit period.

[0155] (Step S404) The support acquisition unit 134 uses the history information acquired in step S403 to generate history graphical information that graphically represents the history information. The history graphical information is information that graphically indicates, for example, the ratio of the amount used to the upper limit or the ratio of the remaining amount.

[0156] (Step S405) The support acquisition unit 134 judges whether or not to acquire a user attribute value. If the user attribute value is to be acquired, the process proceeds to step S406, and if the user attribute value is not to be acquired, the process proceeds to step S407.

[0157] In addition, when the user attribute value is acquired, for example, the received assistance instruction may be a second assistance instruction, whereas when the user attribute value is not acquired, for example, the received assistance instruction may be a first assistance instruction.

[0158] (Step S406) The support acquisition unit 134 acquires from the user management unit 112 one or more user attribute values ​​that are paired with the user identifier acquired in step S401.

[0159] (Step S407) The support acquisition unit 134 judges whether or not to recommend the store. If the store is to be recommended, the process proceeds to step S408, and if the store is not to be recommended, the process proceeds to step S409.

[0160] In addition, when a store is recommended, for example, the received support instruction may be a first support instruction, and when a store is not recommended, for example, the received support instruction may be a second support instruction.

[0161] (Step S408) The support acquisition unit 134 performs a store determination process. An example of the store determination process will be described with reference to the flowchart of FIG.

[0162] (Step S409) The support acquisition unit 134 configures support information to be transmitted, which includes the acquired information, and returns to the upper level process.

[0163] The acquired information includes, for example, historical graphical information, and for example, one or more types of information among one or more user attribute values ​​and one or more store information.

[0164] Next, an example of the store determination process in step S320 and step S408 will be described with reference to the flowchart in FIG.

[0165] (Step S501) The support acquisition unit 134 acquires a user position. It is assumed that the user position has been received from the terminal device 2. The user position is included in, for example, a support instruction.

[0166] (Step S502) The support acquisition unit 134 acquires, from the user management unit 112, one or more user attribute values ​​that are paired with the user identifier included in the received instruction.

[0167] (Step S503) The support acquisition unit 134 assigns 1 to a counter i.

[0168] (Step S504) The support acquisition unit 134 judges whether or not the i-th store information exists in the store management unit 111. If the i-th store information exists, the process proceeds to step S505, and if the i-th store information does not exist, the process proceeds to step S513.

[0169] (Step S505) The support acquisition unit 134 acquires from the store management unit 111 one or more store attribute values ​​included in the i-th store information.

[0170] (Step S506) The support acquisition unit 134 assigns 1 to a counter j.

[0171] (Step S507) The support acquisition unit 134 judges whether or not the j-th recommendation condition exists. If the j-th recommendation condition exists, the process proceeds to step S508, and if not, the process proceeds to step S512.

[0172] (Step S508) The support acquisition unit 134 acquires the j-th recommendation condition from the storage unit 11.

[0173] (Step S509) The support acquisition unit 134 uses one or more types of information among one or more user attribute values ​​and one or more store attribute values ​​to determine whether the j-th recommendation condition is met. If the j-th recommendation condition is met, the process proceeds to step S510. If the j-th recommendation condition is not met, the process proceeds to step S511.

[0174] (Step S510) The support acquisition unit 134 increments the counter j by 1. The process returns to step S507.

[0175] (Step S511) The support acquisition unit 134 increments the counter i by 1. The process returns to step S504.

[0176] (Step S512) The support acquisition unit 134 acquires a store identifier corresponding to the i-th store information from the store management unit 111, and temporarily stores the store identifier in a buffer (not shown).

[0177] (Step S513) The support acquisition unit 134 acquires one or more store identifiers from one or more store identifiers in a buffer (not shown).

[0178] The store identifiers acquired here may be all store identifiers in a buffer (not shown), or may be one or more store identifiers that satisfy a specific condition. The one or more store identifiers that satisfy a specific condition may be, for example, store identifiers of stores with evaluation values ​​in the top N (N is a natural number equal to or greater than 1).

[0179] (Step S514) The support acquisition unit 134 acquires store information of the stores identified by the one or more store identifiers acquired in step S513, and then returns to the upper processing.

[0180] Next, an example of the store clerk assistance information acquisition process in step S307 will be described with reference to the flowchart in FIG.

[0181] (Step S601) The support acquisition unit 134 acquires a user identifier of a target user. Note that the user identifier of the target user is associated with information or an instruction received from the terminal device 2, for example.

[0182] (Step S602) The support acquisition unit 134 acquires from the user management unit 112 one or more user attribute values ​​that are paired with the user identifier acquired in step S601.

[0183] (Step S603) The assistance acquisition unit 134 configures store clerk assistance information having one or more user attribute values ​​acquired in step S602. The process returns to the upper level process. The store clerk assistance information may also include the received record information.

[0184] Next, an example of the evaluation value acquisition process in step S318 will be described with reference to the flowchart in FIG.

[0185] (Step S701) The evaluation unit 133 acquires a store identifier of the store to be evaluated.

[0186] (Step S702) The evaluation unit 133 assigns 1 to a counter i.

[0187] (Step S703) The evaluation unit 133 judges whether or not the i-th evaluation source information for acquiring the evaluation value exists. If the i-th evaluation source information exists, the process proceeds to step S704, and if not, the process proceeds to step S706.

[0188] (Step S704) The evaluation unit 133 acquires from the store management unit 111 information that is paired with the store identifier acquired in step S701 and is the i-th evaluation source information.

[0189] (Step S705) The evaluation unit 133 increments the counter i by 1. The process returns to step S703.

[0190] (Step S706) The evaluation unit 133 acquires an evaluation value using one or more types of evaluation source information acquired in step S704. The evaluation unit 133 accumulates the evaluation value in the store management unit 111 in a pair with the store identifier.

[0191] Next, an example of the operation of the terminal device 2 will be described with reference to the flowchart of FIG.

[0192] (Step S801) The terminal reception unit 22 judges whether or not an input has been received. If an input has been received, the process proceeds to step S802, and if an input has not been received, the process proceeds to step S825.

[0193] (Step S802) The device processing unit 23 judges whether the input received in step S801 is information indicating the start of movement. If it is information indicating the start of movement, the process proceeds to step S803, and if it is not information indicating the start of movement, the process proceeds to step S806.

[0194] The information indicating the start of movement is received based on, for example, the pressing of a specific button by the user or guardian, or the launch of an application that supports the user.

[0195] (Step S803) The device processing unit 23 starts the operation of a first timer that starts operating when the user starts moving from home.

[0196] (Step S804) When starting to move from home, the device processing unit 23 judges whether or not the user needs assistance. If assistance is needed, the process proceeds to step S805, and if assistance is not needed, the process returns to step S801.

[0197] For example, a first flag indicating whether or not to provide support when starting travel from home is stored in the terminal storage unit 21.

[0198] (Step S805) The terminal transmitting unit 24 acquires a user identifier from the terminal storage unit 21, and transmits a first support instruction in association with the user identifier to the support device 1. The process returns to step S801.

[0199] (Step S806) The terminal processing unit 23 judges whether the input received in step S801 is information indicating arrival at the store. If the information indicates arrival at the store, the process proceeds to step S807, and if the information does not indicate arrival at the store, the process proceeds to step S810.

[0200] The information indicating arrival at the store is received, for example, when a user or a store clerk presses a specific button, or when information is received from a terminal (not shown) in the store or the store device 3.

[0201] (Step S807) The terminal processing unit 23 starts the operation of a second timer that starts operating upon arrival at the store.

[0202] (Step S808) When the user arrives at the store, the terminal processing unit 23 judges whether or not assistance is required for the user. If assistance is required, the process proceeds to step S809, and if assistance is not required, the process returns to step S801.

[0203] For example, a second flag indicating whether or not to provide support upon arrival at the store is stored in the terminal storage unit 21.

[0204] (Step S809) The terminal transmitting unit 24 acquires a user identifier from the terminal storage unit 21, and transmits a second support instruction in association with the user identifier to the support device 1. The process returns to step S801.

[0205] (Step S810) The terminal processing unit 23 judges whether or not the input accepted in step S801 is a payment instruction. If it is a payment instruction, the process proceeds to step S811, and if it is not a payment instruction, the process proceeds to step S815.

[0206] The payment instruction may be input by a user or a store clerk, or may be received from a store terminal (not shown) or the store device 3, for example.

[0207] (Step S811) The terminal processing unit 23 acquires the payment information included in the input accepted in step S801.

[0208] (Step S812) The device processing unit 23 acquires the first time, which is the time indicated by the first timer. The device processing unit 23 resets the first timer.

[0209] (Step S813) The device processing unit 23 acquires the second time indicated by the second timer. The device processing unit 23 resets the second timer.

[0210] (Step S814) The terminal processing unit 23 composes payment information, etc. The terminal transmission unit 24 transmits the payment information, etc. to the support device 1. Return to step S801. The payment information, etc. includes, for example, payment information, a first time, a second time, a user identifier, and a store identifier.

[0211] (Step S815) The terminal processing unit 23 judges whether or not the input accepted in step S801 is an output instruction. If it is an output instruction, the process proceeds to step S816, and if it is not an output instruction, the process proceeds to step S819.

[0212] The output instruction may be input by a user or a store clerk, or may be received from a store terminal (not shown) or the store device 3, for example.

[0213] (Step S816) The terminal transmitting unit 24 acquires the user identifier from the terminal storage unit 21, and transmits an output instruction having the user identifier to the support device 1.

[0214] (Step S817) The terminal receiving unit 25 judges whether or not user information has been received from the support device 1. If user information has been received, the process proceeds to step S818, and if user information has not been received, the process returns to step S817.

[0215] (Step S818) The terminal processing unit 23 outputs the user information received in step S817. Return to step S801. Note that the output here is, for example, display on a display, but may also be storage in the terminal storage unit 21, etc.

[0216] (Step S819) The terminal processing unit 23 judges whether the input accepted in step S801 is a store evaluation. If it is an evaluation, the process proceeds to step S820, and if it is not an output instruction, the process proceeds to step S821. The evaluation is associated with the store identifier.

[0217] (Step S820) The terminal transmitting unit 24 transmits the evaluation received in step S801 in association with the shop identifier and the user identifier to the support device 1. The process returns to step S801.

[0218] (Step S821) The terminal receiving unit 22 acquires sound information or video.

[0219] (Step S822) The terminal recording unit 231 judges whether the sound information or video acquired in step S821 matches the recording conditions. If the recording conditions are met, the process proceeds to step S823, and if the recording conditions are not met, the process returns to step S801.

[0220] (Step S823) The terminal transmission unit 24 transmits the recorded information, which is sound information or video, to the support device 1 in association with the user identifier. It is preferable that the terminal transmission unit 24 transmits the recorded information to the support device 1 in association with the store identifier.

[0221] (Step S824) The terminal recording unit 231 stores the audio information or video. Then, the process returns to step S801.

[0222] (Step S825) The terminal receiving unit 25 judges whether or not information has been received from the support device 1. If information has been received, the process proceeds to step S826, and if information has not been received, the process returns to step S801. The information is, for example, support information.

[0223] (Step S826) The device processing unit 23 composes information to be output using the information received in step S825. The terminal output unit 26 outputs the information. Return to step S801.

[0224] In the flowchart of FIG. 8, the process ends when the power is turned off or an interrupt occurs to end the process.

[0225] A specific example of the operation of the support system A in this embodiment will be described below. A conceptual diagram of the support system A is shown in FIG.

[0226] Now, the store management unit 111 of the support device 1 stores a store management table having a structure shown in FIG. 9. The store management table is a table for managing store information. The store management table manages one or more records having an "ID", "store identifier", and "store attribute value". The "store attribute value" here includes an "address", "store type", "presence or absence of support staff", "product display method", "wheelchair", and "evaluation value". The "ID" is information for identifying a record. The "address" is the address of the store. The "store type" is the type of store. The "presence or absence of support staff" is an attribute indicating whether or not a support staff member is present in the store. The "product display method" is information indicating the method of product display in the store (for example, "messy" or "tidy"). The "wheelchair" is information indicating whether or not a wheelchair can pass through the store (for example, "OK" or "NG"). The "evaluation value" is an evaluation value of the store.

[0227] The user management unit 112 stores a user management table having a structure shown in FIG. 10. The user management table is a table for managing user information. The user management table manages one or more records having an "ID", a "user identifier", and a "user attribute value". The "user attribute value" here has a "home address", a "disability level", a "disability content", a "unique recommendation condition", a "payment method identifier", and a "limit". The "ID" is information for identifying a record. The "home address" is the home address of the user. The "disability level" indicates the degree of the user's disability, and is in five stages from "1" to "5" here. The "disability content" indicates the content of the user's disability. The "unique recommendation condition" is a user-specific condition when recommending a store to the user. The "payment method identifier" is a user-specific ID (e.g., a credit card number, a user ID of an electronic money application) of the user's payment method (e.g., a credit card, electronic money). The "limit" is the maximum amount of money that the user can purchase in a unit period (here, one month).

[0228] The storage unit 11 stores a payment management table having a structure shown in FIG. 11. The payment management table is a table for managing payment information. The payment management table manages one or more records having "ID", "user identifier", "date and time", "store identifier", "amount", "product identifier", "assisting clerk", and "recorded information". "ID" is information for identifying a record. "Date and time" is the date and time when the payment was made. "User identifier" is the identifier of the user who made the payment. "Store identifier" is the identifier of the store where the user shopped. "Amount" is the amount paid by the user. "Product identifier" is the identifier of the product purchased by the user. "Assisting clerk" is the identifier of the clerk who supported the user's shopping. "Recorded information" is information recorded at the store when the user shopped.

[0229] Furthermore, it is assumed that the common recommendation condition "evaluation value >= 3" is stored in the storage unit 11.

[0230] In this situation, the following two specific examples will be described. In the first example, store information and historical graphical information of a recommended store are presented to the user. In the second example, the details of the user's problem are presented to a store clerk.

[0231] (Example 1) Now, user A, who is challenged, is about to leave his / her home and go shopping. Then, user A or his / her guardian starts the app "challenged support app" installed in user A's terminal device 2, and inputs "support instructions" including the user identifier "user A" to the app. Next, terminal device 2 (app) accepts the "support instructions" including "user A" and transmits it to the support device 1.

[0232] Next, the terminal information receiving unit 121 of the support device 1 receives the support instruction from the terminal device 2. Next, the support acquisition unit 134 acquires support information as follows.

[0233] The support acquisition unit 134 acquires the received user identifier "user A". Next, the support acquisition unit 134 acquires one or more pieces of payment information paired with the user identifier "user A" from the payment management table (FIG. 12). Next, the support acquisition unit 134 acquires history information using the acquired one or more pieces of payment information. Here, an example of history information is the total amount (yen) paired with a date and time including March 2023, which is "3500 (yen)". In addition, the support acquisition unit 134 acquires the upper limit "6000 yen" paired with the user identifier "user A" from the user management table (FIG. 10). Then, the support acquisition unit 134 acquires the amount up to the upper limit, "2500 (yen)", which is another example of history information.

[0234] Next, the support acquisition unit 134 uses the acquired history information "3,500 (yen)" and the upper limit "6,000 yen" to construct historical graphical information that is a diagram that allows challenged user A to easily visualize the ratio of the amount spent to the amount remaining, so that it is easy to understand.

[0235] The support acquisition unit 134 also acquires unique recommendation conditions paired with the user identifier "user A" from the user management table (FIG. 10). The support acquisition unit 134 also acquires a common recommendation condition "rating value >= 3" from the storage unit 11. Next, the support acquisition unit 134 determines one or more pieces of store information having a store attribute value that satisfies the acquired unique recommendation condition and the common recommendation condition from the store management table (FIG. 9). Here, it is assumed that the support acquisition unit 134 has determined three pieces of store information. Next, the support acquisition unit 134 acquires store identifiers (here, store names) included in the three pieces of store information.

[0236] Next, the support acquisition unit 134 generates support information including the historical graphical information and the names of the three recommended stores. Next, the support transmission unit 142 transmits the support information to the terminal device 2.

[0237] Next, the terminal device 2 receives and outputs the support information. An example of such output is shown in Fig. 12. In Fig. 12, 1201 is information on the recommended store. 1202 is historical graphical information. Note that Fig. 12 also shows the amount of money that can be purchased up to the upper limit.

[0238] As described above, in this specific example, support information can be provided to challenged users so that they can use payment methods appropriately.

[0239] (Example 2) Assume that user A selects one store (convenience store YXXX station front store) from the stores suggested in specific example 1 and arrives at the store. Note that during this time, the app continues to run.

[0240] Then, it is assumed that after the user A enters the store, the terminal device 2 acquires sound information from the microphone of the terminal device 2.

[0241] Then, it is assumed that the terminal recording unit 231 of the terminal device 2 determines that the acquired sound information matches the recording condition. Here, it is assumed that the recording condition is "volume is equal to or greater than a threshold", which is a feature of the sound. In other words, it is assumed that the user A is raising his / her voice. Then, the terminal recording unit 231 starts recording the sound information. Furthermore, the terminal transmission unit 24 transmits the recording information, which is the sound information, to the support device 1 in association with the user identifier "user A".

[0242] Next, the terminal information receiving unit 121 of the support device 1 receives record information associated with "user A" from the terminal device 2. Next, the recording unit 132 stores the received record information in the user management table (FIG. 10) by associating the user identifier with "user A." Note that, when a payment is made at the store, the record information may be stored in association with the payment information.

[0243] Next, the processing unit 13 determines that the received record information matches the transmission condition (here, "volume is equal to or greater than a threshold").

[0244] Then, the support acquisition unit 134 acquires the store clerk support information. That is, the support acquisition unit 134 acquires the problem content "simple greeting..." that is paired with "User A" from the user management table (FIG. 10). Note that the problem content here is an example of the store clerk support information.

[0245] Next, the assistance transmission unit 142 transmits the acquired store clerk assistance information to the terminal device 2 that transmitted the record information and the like.

[0246] Next, the terminal device 2 receives and outputs the details of the failure. An example of such output is shown in Fig. 13. In Fig. 13, 1301 is store clerk assistance information. By looking at the store clerk assistance information, the store clerk will be able to provide appropriate service to the challenged user.

[0247] Also, assume that the store clerk selects the “Store Clerk Assistance” button 1302 on the terminal device 2 of user A and inputs his / her name. The terminal device 2 then accepts the name, associates it with “User A”, and transmits the name to the support device 1.

[0248] Next, the receiving unit 12 of the support device 1 receives the name in association with "user A." The processing unit 13 stores the name in association with "user A."

[0249] Then, it is assumed that the user A subsequently purchases a product using the credit card of the user A. Then, for example, it is assumed that the terminal device 2 or the store device 3 transmits payment information associated with “user A” to the support device 1.

[0250] Next, the payment receiving unit 122 of the support device 1 receives the payment information associated with "user A." Next, the processing unit 13 stores the received payment information in the payment management table (FIG. 11) in association with the user identifier "user A." Such a record is, for example, the record of "ID=3" in the payment management table (FIG. 11).

[0251] As described above, in this specific example, information can be provided for a store clerk to assist a challenged user.

[0252] As described above, according to this embodiment, when a challenged user uses a payment method, information for supporting the user can be provided.

[0253] In addition, according to the present embodiment, in order for a challenged user to use a payment method,

[0254] Furthermore, according to this embodiment, appropriate information for supporting a challenged user can be provided to a store clerk who assists the challenged user when the user uses a payment method.

[0255] Furthermore, according to this embodiment, user information can be provided to a store clerk who assists a challenged user when the user uses a payment method.

[0256] Furthermore, according to this embodiment, it is possible to provide information at an appropriate time to assist a challenged user in using a payment method.

[0257] Furthermore, according to this embodiment, a challenged user can be provided with a payment method usage history in an easily understandable manner.

[0258] Furthermore, according to this embodiment, the circumstances under which a challenged user uses a payment method can be recorded.

[0259] The process in this embodiment may be realized by software. This software may be distributed by software download or the like. This software may be recorded on a recording medium such as a CD-ROM and distributed. This also applies to other embodiments in this specification. The software that realizes the support device 1 in this embodiment is a program as follows. That is, this program is a program that causes a computer to function as a terminal information receiving unit that receives a user identifier that identifies a challenged user, a support acquiring unit that acquires support information that supports the user identified by the user identifier in using a payment means at a store, and a support transmitting unit that transmits the support information to the user's terminal device.

[0260] The software for realizing the terminal device 2 is the following program. That is, this program causes a computer to function as a terminal reception unit that receives input of at least one type of recorded information of audio and image, and as a terminal transmission unit that transmits the recorded information to a support device when the recorded information satisfies a recording condition.

[0261] Fig. 14 shows the appearance of a computer that executes the programs described in this specification to realize the support devices and the like of the various embodiments described above. The above-mentioned embodiments can be realized by computer hardware and computer programs executed thereon. Fig. 14 is an overview of this computer system 300, and Fig. 15 is a block diagram of the system 300.

[0262] In FIG. 14, a computer system 300 includes a computer 301 including a CD-ROM drive, a keyboard 302, a mouse 303, and a monitor 304.

[0263] 15, computer 301 includes, in addition to CD-ROM drive 3012, MPU 3013, bus 3014 connected to CD-ROM drive 3012 etc., ROM 3015 for storing programs such as a boot-up program, RAM 3016 connected to MPU 3013 for temporarily storing instructions of application programs and providing temporary storage space, and hard disk 3017 for storing application programs, system programs, and data. Although not shown here, computer 301 may further include a network card for providing connection to a LAN.

[0264] A program for causing computer system 300 to execute the functions of the support device or the like of the above-mentioned embodiment may be stored on CD-ROM 3101, inserted into CD-ROM drive 3012, and further transferred to hard disk 3017. Alternatively, the program may be transmitted to computer 301 via a network (not shown) and stored on hard disk 3017. The program is loaded into RAM 3016 when executed. The program may also be loaded directly from CD-ROM 3101 or the network.

[0265] The program does not necessarily include an operating system (OS) or a third party program that causes the computer 301 to execute the functions of the support device of the above-mentioned embodiment. The program only needs to include an instruction portion that calls appropriate functions (modules) in a controlled manner to obtain a desired result. How the computer system 300 operates is well known, and a detailed description will be omitted.

[0266] In addition, in the above program, the steps of transmitting information and receiving information do not include processing performed by hardware, such as processing performed by a modem or interface card in the transmitting step (processing that is performed only by hardware).

[0267] The program may be executed by a single computer or a plurality of computers. That is, the program may be executed by a centralized processing or a distributed processing.

[0268] Furthermore, in each of the above embodiments, it goes without saying that two or more communication means present in one device may be physically realized by one medium.

[0269] In each of the above embodiments, each process may be realized by centralized processing in a single device, or may be realized by distributed processing in a plurality of devices.

[0270] The present invention is not limited to the above-described embodiment, and various modifications are possible, and it goes without saying that these modifications are also included within the scope of the present invention. [Industrial Applicability]

[0271] INDUSTRIAL APPLICABILITY As described above, the support device according to the present invention has the effect of being able to support challenged users when they use payment methods, and is useful as a support device, etc. [Explanation of symbols]

[0272] A Support System 1 Support equipment 2 Terminal Equipment 3. Store equipment 11 Storage area 12 Receiving section 13 Processing section 14 Transmitter 21 Terminal storage section 22 Terminal Reception 23 Terminal Processing Section 24 Terminal transmitter 25 Terminal receiving section 26 Terminal Output Section 111 Store Management Department 112 User Management Department 121 Terminal information receiving unit 122 Payment Receiving Department 131 Evaluation Source Acquisition Department 132 Recording Section 133 Evaluation Department 134 Support Acquisition Department 141 Recording and Transmission Unit 142 Support Transmission Department 231 Terminal Recording Section

Claims

1. a terminal information receiving unit for receiving a user identifier for identifying a challenged user; a support acquisition unit that acquires support information that supports the user identified by the user identifier in using a payment method at a store; a support transmitting unit that transmits the support information to the user's terminal device.

2. The support acquisition unit, The support device according to claim 1 , further comprising: a store management unit that stores one or more pieces of store information each having one or more store attribute values ​​corresponding to a store identifier; a store whose one or more store attribute values ​​match a recommendation condition; and an assistance device that acquires the support information, which is the store information of the store.

3. an evaluation source acquisition unit that acquires, in association with a store identifier, one or more types of evaluation source information among a time from when a user leaves home until a payment is completed, a time from when a user arrives at a store until a payment is completed, and a user's evaluation of the store after the payment; an evaluation unit that uses the one or more types of evaluation source information to obtain an evaluation value for the store and stores the evaluation value in association with a store identifier of the store; The support acquisition unit, The support device described in claim 2 refers to the store management unit, and uses one or more store attribute values ​​of a good store corresponding to an evaluation value above or greater than a threshold to determine similar stores whose similarity to the good store is above or greater than a threshold, and obtains the support information, which is store information of the similar stores.

4. The support acquisition unit, Refer to a user management unit in which one or more pieces of user information having one or more user attribute values ​​are stored, and acquire store clerk presentation information which is one or more attribute values ​​of the user and is information to be presented to a store clerk at the store; The terminal information receiving unit Receive the terminal information acquired by the terminal device; The support transmission unit is 2. The support device according to claim 1, wherein the store clerk-presented information is transmitted when the terminal information satisfies a transmission condition.

5. A payment receiving unit that receives payment information related to a payment being made using the payment means in association with a user identifier, The support acquisition unit, The support device according to claim 1 , further comprising: a step of acquiring the support information, which is graphical information relating to a history of use of the payment means, by using one or more pieces of payment information associated with the user identifier.

6. The terminal information receiving unit receiving recording information including audio or video recording information from the terminal device; A recording unit that accumulates the record information; 2. The support device according to claim 1, further comprising a record transmitting unit for transmitting the record information.

7. A support method implemented by a terminal information receiving unit, a support acquisition unit, and a support sending unit, a terminal information receiving step in which the terminal information receiving unit receives a user identifier that identifies a challenged user; a support acquisition step of acquiring support information for supporting the user identified by the user identifier in using a payment method at a store; a support transmitting step in which the support transmitting unit transmits the support information to a terminal device of the user.

8. An information processing method implemented by a terminal reception unit and a terminal transmission unit, a terminal reception step in which the terminal reception unit receives an input of at least one type of recorded information of audio and image; and a terminal transmitting step of transmitting, by the terminal transmitting unit, the record information to a support device when the record information satisfies a recording condition.

Citation Information

Patent Citations

  • Customer support device and customer support system

    JP2021043635A