Information providing method, program, and information providing device

Abstract

To provide a technology for a user representing a purchaser of a product to continue having interest against a purchased product and / or producer thereof.SOLUTION: A server 150 obtains, from a user terminal 100 operated by a user 300, product information for identifying a product, and a remind setting related to the product. The remind setting includes a remind setting date for prescribing a timing to remind. Then, the server 150 transmits, to the user terminal 100, remind information in response to reaching the remind setting date and, further, transmits related information related to the product prior to the remind setting date.SELECTED DRAWING: Figure 1

Description

[Technical field]

[0001] The present disclosure relates to providing information about products. [Background technology]

[0002] Conventionally, various techniques for providing information about products have been proposed. For example, Japanese Patent No. 6636904 (Patent Document 1) discloses a technique for notifying a user of reminder information encouraging replacement of a stockpile (item) at a timing set based on the expiration date of the stockpile (item). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent No. 6636904 Summary of the Invention [Problem to be solved by the invention]

[0004] Product manufacturers need technology to not only remind users who have purchased their products to exchange them, but also to retain those users so that they continue to purchase their products.

[0005] The present disclosure has been devised in light of the above-mentioned circumstances, and its purpose is to provide a technique for enabling users, who are purchasers of goods, to maintain an interest in the purchased goods and / or their producers. [Means for solving the problem]

[0006] According to one aspect of the present disclosure, there is provided an information provision method executed by a computer, the information provision method including the steps of: acquiring from a user product information identifying a purchased product and deadline information specifying the timing of a reminder regarding the purchased product; sending, when the timing corresponding to the deadline information arrives, reminder information encouraging the user to purchase the product; and sending, to the user, related information regarding the product prior to the timing corresponding to the deadline information.

[0007] Preferably, the step of transmitting the related information includes transmitting the related information in response to the passage of a certain period of time from acquisition of the product information and the expiration date information, and in response to the arrival of a date associated with the product.

[0008] Preferably, the step of transmitting the related information is performed in a manner based on an attribute of the product corresponding to the product information.

[0009] Preferably, the attribute includes a quantity of the product, and the information providing method further includes a step of determining, based on the quantity, when to perform the step of transmitting the related information.

[0010] Preferably, the step of specifying the execution time includes specifying the execution time of the step of transmitting the related information further based on a reference value of a usage amount of the product in a unit period.

[0011] Preferably, the attribute includes a classification of the product, and the information providing method further includes a step of accepting invalidation of the product information, and a step of determining when to execute the step of transmitting related information based on the length of time from acquisition of the product information to invalidation of the product information for other products having the same classification as the classification.

[0012] Preferably, the attribute includes a provider of the product, and the step of transmitting the related information includes transmitting the related information at a timing designated by the provider.

[0013] Preferably, the information providing method further includes the step of acquiring an attribute of the user, and the related information is based on the attribute.

[0014] Preferably, the information providing method further includes the step of acquiring an attribute of the user, and the step of transmitting the related information includes transmitting the related information at a timing based on the attribute.

[0015] According to another aspect of the present disclosure, there is provided a program that, when executed by a processor of a computer, causes the computer to carry out the above-described information providing method.

[0016] According to yet another aspect of the present disclosure, there is provided an information providing device including a storage device that stores the above-mentioned program, and a processor that executes the program stored in the storage device. Effect of the Invention

[0017] According to the present disclosure, when the time corresponding to the expiration information of a product arrives, reminder information encouraging the user to purchase the product is sent to the user, and related information regarding the product is sent prior to the time corresponding to the expiration information. [Brief description of the drawings]

[0018] [Figure 1] 1 is a diagram illustrating a schematic configuration of an information providing system according to the present disclosure. [Diagram 2] 1 is a block diagram showing the hardware configuration of a user terminal 100. FIG. [Diagram 3] FIG. 2 is a block diagram showing the hardware configuration of a server 150. [Figure 4] FIG. 2 is a diagram showing an example of a data configuration stored in a server 150. [Diagram 5] FIG. 13 is a diagram showing a schematic diagram of a data flow when registering a reminder setting. [Figure 6] 1 is a diagram showing a schematic diagram of data flow in various notifications (reminding information and related information) to a user terminal 100. FIG. [Figure 7] FIG. 13 is a diagram showing a schematic diagram of a data flow when a user uses a user terminal 100 to instruct a server 150 to delete a reminder setting. [Figure 8] 13 is a flowchart of a process executed in the server 150 for user registration. [Figure 9] FIG. 13 illustrates an example of a user registration screen. [Figure 10] 13 is a flowchart of a process executed in the server 150 for registering reminder settings. [Figure 11] FIG. 13 is a diagram illustrating an example of a registration screen for reminder settings. [Figure 12] FIG. 13 is a diagram showing another example of the reminder setting registration screen. [Figure 13] 13 is a flowchart of a process in which the server 150 issues various notifications to the user terminal 100. [Figure 14] FIG. 13 is a diagram showing an example of a screen that displays reminder information. [Figure 15] 13 is a flowchart of a subroutine of step S400. [Figure 16] FIG. 13 is a diagram showing an example of a registration completion notification screen. [Figure 17] FIG. 13 is a diagram showing an example of a screen displaying information according to the number of elapsed days. [Figure 18] FIG. 13 is a diagram showing an example of a screen displaying information according to the season. [Figure 19] FIG. 13 is a diagram showing an example of a screen displaying information relating to the remaining amount. [Figure 20] FIG. 13 is a diagram showing an example of a screen displaying manufacturer distribution information. [Figure 21] FIG. 13 is a diagram illustrating an example of a screen displaying related information. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0019] Hereinafter, an embodiment of an information providing system including an information providing device will be described with reference to the drawings. In the following description, the same parts and components are denoted by the same reference numerals. Their names and functions are also the same. Therefore, the description thereof will not be repeated.

[0020] [1. Information provision system configuration] 1 is a diagram illustrating a schematic configuration of an information providing system according to the present disclosure. The information providing system 10 includes a user terminal 100 and a server 150.

[0021] The user 300 uses the user terminal 100 to transmit (1) user information, (2) product information, and (3) reminder settings to the server 150.

[0022] (1) User information is information relating to user 300, and includes, for example, information identifying the destination of a message addressed to user 300 (such as an email address or an account for a social networking service (SNS)).

[0023] (2) Product information is information that identifies a product for which the user 300 needs reminder information. This product may be a product that the user 300 has purchased, a product that the user 300 has acquired by a method other than purchase, such as receiving it from an acquaintance, or a product that the user 300 has not acquired but is interested in. The user 300 may, for example, acquire identification information of the product 200 from the code 210 assigned to the product 200 and transmit the identification information to the server 150 as product information.

[0024] In this embodiment, a QR (Quick Response) code (registered trademark) is used as an example of code 210, but the code used for product identification information is not limited to a QR code and may be other types of codes such as a barcode.

[0025] (3) The reminder setting includes the date on which the user 300 wishes to be reminded about the product 200 (the reminder setting date).

[0026] The server 150 may be operated by the manufacturer of the product 200, or may be operated by a third party that provides information to the user 300.

[0027] The server 150 transmits to the user 300 reminder information regarding the product 200 in response to the arrival of a reminder date set by the user 300, and transmits related information regarding the product 200 at a given timing before the arrival of the reminder date. The user 300 receives the reminder information and related information using the user terminal 100.

[0028] In this specification, "transmit to" may be used synonymously with "transmit toward." In other words, the statement "server 150 transmits data to user terminal 100" may mean that server 150 transmits data to user terminal 100 via a network or by pia-to-pia communication.

[0029] [2. Hardware Configuration of User Terminal 100] FIG. 2 is a block diagram showing the hardware configuration of user terminal 100. As shown in FIG.

[0030] The user terminal 100 includes a CPU (Central Processing Unit) 20, an antenna 23, a communication device 24, an input switch 25, a camera 26, a flash memory 27, a RAM (Random Access Memory) 28, a ROM (Read-Only Memory) 29, a memory card drive 30, a microphone 32, a speaker 33, an audio signal processing circuit 34, a monitor 35, an LED (Light Emitting Diode) 36, a communication interface 37, a vibrator 38, a GPS (Global Positioning System) antenna 39, a GPS module 40, an acceleration sensor 41, and a geomagnetic sensor 42. The memory card 31 can be attached to the memory card drive 30.

[0031] The antenna 23 receives a signal transmitted by a base station, or transmits a signal for communication with another communication device via the base station. The signal received by the antenna 23 is subjected to front-end processing by the communication device 24, and the processed signal is sent to the CPU 20.

[0032] The CPU 20 executes processing for controlling the operation of the user terminal 100 based on instructions given to the user terminal 100. When the user terminal 100 receives a signal, the CPU 20 executes predefined processing based on the signal sent from the communication device 24, and sends the processed signal to the audio signal processing circuit 34. The audio signal processing circuit 34 executes predefined signal processing on the signal, and sends the processed signal to the speaker 33. The speaker 33 outputs sound based on the signal.

[0033] The input switch 25 accepts input of a command to the user terminal 100. The input switch 25 is realized by a touch sensor, a button provided on the housing of the user terminal 100, or the like. A signal corresponding to the input command is input to the CPU 20.

[0034] The microphone 32 receives speech to the user terminal 100 and sends a signal corresponding to the spoken voice to the voice signal processing circuit 34. The voice signal processing circuit 34 executes processing defined in advance for a call based on the signal, and sends the processed signal to the CPU 20.

[0035] The flash memory 27 stores data sent from the CPU 20. Furthermore, the CPU 20 reads out the data stored in the flash memory 27 and executes predefined processing using the data.

[0036] The RAM 28 temporarily holds data generated by the CPU 20 based on operations performed on the input switches 25. The ROM 29 stores programs or data for causing the user terminal 100 to execute predetermined operations. The CPU 20 reads out the programs or data from the ROM 29 and controls the operation of the user terminal 100.

[0037] The memory card drive 30 reads out data stored in the memory card 31 and sends it to the CPU 20. The memory card drive 30 writes the data output by the CPU 20 into the storage area of ​​the memory card 31.

[0038] The monitor 35 is a touch-operated monitor, but the mechanism for receiving the touch operation is not particularly limited. Based on data acquired from the CPU 20, the monitor 35 displays a screen defined by the data.

[0039] The LED (Light Emitting Diode) 36 emits light based on a signal output from the CPU 20. The communication interface 37 is realized by WiFi (Wireless Fidelity), Bluetooth (registered trademark), NFC (Near Field Communication), or the like. In another aspect, the communication interface 37 accepts attachment of a cable for data communication. The communication interface 37 transmits a signal output from the CPU 20. Alternatively, the communication interface 37 transmits data included in a signal received from outside the user terminal 100 to the CPU 20.

[0040] The vibrator 38 performs an oscillation operation at a predetermined frequency based on a signal output from the CPU 20 .

[0041] The GPS antenna 39 receives GPS signals transmitted from four or more satellites. The received GPS signals are input to the GPS module 40. The GPS module 40 performs positioning processing using the GPS signals and known technology, and acquires location information of the user terminal 100.

[0042] The acceleration sensor 41 detects the acceleration acting on the user terminal 100, and is realized, for example, as a three-axis acceleration sensor. The detected acceleration is input to the CPU 20. The CPU 20 detects the movement and attitude (tilt) of the user terminal 100 based on this acceleration.

[0043] The geomagnetic sensor 42 detects the direction in which the user terminal 100 is facing. The information acquired by this detection is input to the CPU 20.

[0044] [3. Hardware configuration of Server 150] FIG. 3 is a block diagram showing the hardware configuration of server 150. As shown in FIG.

[0045] The server 150 is managed, for example, by a business entity that provides the information providing system 10 shown in FIG.

[0046] The server 150 includes, as its main components, a CPU 1 that executes a program, a mouse 2 and a keyboard 3 that receive input of instructions from a user of the server 150, a RAM 4 that volatilely stores data generated by the execution of the program by the CPU 1 or data input via the mouse 2 or keyboard 3, a hard disk 5 that nonvolatilely stores data, an optical disk drive 6, a monitor 8, and a communication interface 7. The components are mutually connected by a bus. A CD-ROM 9 or other optical disk is loaded into the optical disk drive 6. The communication interface 7 includes, but is not limited to, a USB (Universal Serial Bus) interface, a wired LAN (Local Area Network), a wireless LAN, a Bluetooth (registered trademark) interface, and the like.

[0047] The processing in the server 150 is realized by the respective hardware components and software executed by the CPU 1. Such software may be stored in advance in the hard disk 5. In addition, the software may be stored in a CD-ROM 9 or other computer-readable non-volatile data recording medium and distributed as a program product. Alternatively, the software may be provided as a downloadable program product by an information provider connected to the Internet (registered trademark) or other networks. Such software is read from a data recording medium by the optical disk drive 6 or other data reading device, or downloaded via the communication interface 7, and then temporarily stored in the hard disk 5. The software is read from the hard disk 5 by the CPU 1 and stored in the RAM 4 in the form of an executable program. The CPU 1 executes the program.

[0048] The program referred to here may include not only a program that can be directly executed by the CPU 1, but also a source program format program, a compressed program, an encrypted program, and the like.

[0049] Each component constituting server 150 shown in Fig. 3 is a general one. Therefore, it can be said that the most essential part according to the present embodiment is the program stored in server 150. Since the operation of each piece of hardware of server 150 is well known, detailed description will not be repeated.

[0050] [4. Data Structure (Product DB)] 4 is a diagram showing an example of a data configuration stored in server 150. Server 150 stores various types of data as a product database (DB) 151, a user DB 152, and a delivery management DB 153.

[0051] More specifically, the product DB 151 includes information about each of one or more products. The product DB 151 stores information about each of four items: "product information," "expiration date," "sales," and "promotion."

[0052] "Product information" includes product identification information, product image, manufacturer, category, capacity, number of items, and recommended usage.

[0053] The product identification information is information for identifying a product, and is composed of, for example, a JAN (Japanese Article Number) code.

[0054] A product image is an image that represents the appearance of a product. The manufacturer is information that identifies the manufacturer of the product.

[0055] A category is information that specifies the classification of a product, and may include only one type of classification, or may include multiple types (multiple hierarchies) of classification. For example, if a product is chocolate with the product name "A Chocolate", the "category" may include only the information "food", or may include three types of information: "food" as a major classification, "confectionery" as a medium classification, and "chocolate" as a minor classification.

[0056] Volume specifies the amount of a selling unit for a product. For example, a 50g bar of chocolate has a volume of "50g" and an 800g bottle of detergent has a volume of "800g".

[0057] A quantity defines the number of units sold for a product. For example, a beer sold individually would have a quantity of "1 can," whereas a beer sold in a half-dozen pack would have a quantity of "6 cans."

[0058] The estimated usage specifies the amount of a product to be used in a unit period. For example, if 50g of detergent is used for one wash and the wash is assumed to be done once a day, the estimated amount of the product "detergent" to be used in one week is "350g."

[0059] "Expiration date" includes the standard date (standard expiration date) by which the quality of the product is guaranteed. "Sales" includes information that identifies a site that sells the product on the network (sales site) and information that identifies a physical store that sells the product (sales store). The manufacturer of the product may register and update the "sales site" and / or "sales store" on the server 150.

[0060] "Promotion" includes information directly related to the product (promo information), such as how to use and / or store the product. In this embodiment, the related information includes directly related information and indirectly related information. Indirectly related information includes information about other products of the same manufacturer as the product.

[0061] The user DB 152 includes information about each user. The types of information registered in the user DB 152 will be described later.

[0062] The distribution management DB 153 includes information that specifies the timing of delivery of reminder information and / or related information to the user. The information registered in the distribution management DB 153 is classified into "greetings," "usage / guide," "replacement guidelines," and "sales promotion."

[0063] The "greeting" defines the timing when a user first registers information about the user in the server 150. That is, in response to the user's information being registered in the server 150, the server 150 transmits information related to the greeting to the user.

[0064] "Usage / Guide" specifies the timing for transmitting guide information such as how to use and store a product. More specifically, the server 150 may transmit the guide information when a given number of days have passed since the reminder setting was registered in the server 150 (number of days elapsed since registration). The server 150 may transmit the guide information on a date set for each season (spring, summer, fall, and winter) and on other predetermined dates (date / season).

[0065] The "replacement guideline" specifies the timing for sending reminder information encouraging replacement (or replacement purchase) of a product. More specifically, the server 150 may send the reminder information in response to the arrival of a reminder setting date set by the user 300 (remind setting date). The server 150 may send the reminder information at a timing specified according to the capacity, number of items, and / or estimated usage of the registered product (capacity, number of items, estimated usage). The server 150 may send the reminder information for other products in the same category as the registered product at a timing according to the length of the period from when the reminder setting is registered in the server 150 to when the registration is invalidated (registration-deletion period).

[0066] In this specification, "disabling" a reminder setting registered by a user in server 150 is also referred to as "deleting" the registration. When a user instructs server 150 to "delete" a reminder setting registration, server 150 may delete data related to the reminder setting from server 150, or may add new data to the reminder setting to prevent the transmission of reminder information and related information without deleting the data from server 150.

[0067] "Sales promotion" specifies the timing for transmitting promotional information (an example of indirectly related information), such as information on other products from the product manufacturer. More specifically, the server 150 may transmit the sales promotion information at a timing specified by the product manufacturer (purchasing manufacturer). The server 150 may transmit the sales promotion information at a timing set for a product category (for example, for the category "sweets", a certain period before Halloween) (purchasing category). The server 150 may transmit the sales promotion information at a timing set for an area set by the user (area).

[0068] [5. User Registration] The registration of user information will be described with reference to FIG.

[0069] The user 300 uses the user terminal 100 to transmit user information (user name of the user 300, email address of the user 300, gender of the user 300, generation of the user 300, and area of ​​the user 300) to the server 150. The transmitted information is registered in the user DB 152 as the user's attributes.

[0070] [6. Registering Reminder Settings] FIG. 5 is a diagram showing a schematic diagram of the data flow when registering reminder settings.

[0071] The user 300 uses the user terminal 100 to transmit a reminder setting together with information for identifying a product to the server 150. In the example of Fig. 5, a QR code read from an image of the QR code 210 attached to the product 200 is shown as an example of information for identifying a product.

[0072] The reminder setting includes the reminder setting date (the date on which the user wishes to be reminded) and information specifying whether or not to permit delivery of related information (whether or not delivery is permitted). Information specifying the product and the reminder setting are registered in the user DB 152. In the example of FIG. 5, the server 150 registers the QR code in the user DB 152 as product identification information corresponding to the QR code acquired by referring to a given database. The server 150 further registers the date and time when the reminder setting was registered in the user DB 152 as part of the registration information (registration date and time).

[0073] Data may be stored for each product in the user DB 152. That is, when the server 150 receives a reminder setting registration for multiple products from the same user, the server 150 may register a set of data shown as the storage contents of the user DB 152 in FIG. 5 in the user DB 152 for each of the multiple products.

[0074] [7. Various Notifications] FIG. 6 is a diagram showing a schematic diagram of data flow in various notifications (reminding information and related information) to the user terminal 100. As shown in FIG.

[0075] The server 150 transmits reminding information or related information to the user terminal 100 in response to the arrival of a timing defined in the distribution management DB 153 .

[0076] The server 150 identifies, in the product DB 151, a product having the same product identification information as the product identification information registered in the user DB 152 as a product that is a target of the reminder information and the related information.

[0077] For example, when the server 150 includes an image of a product as the reminder information and / or the related information, the server 150 identifies a product in the product DB 151 that has the same product identification information as the product identification information registered in the user DB 152. Then, the server 150 uses the product image of the identified product as the image of the product.

[0078] [8. Deleting reminder settings] FIG. 7 is a diagram showing a schematic diagram of the flow of data when the user uses the user terminal 100 to instruct the server 150 to delete a reminder setting.

[0079] In response to a deletion operation from the user, the user terminal 100 instructs the server 150 to delete the reminder setting. In response to the instruction, the server 150 adds the date and time when the instruction was received (deletion date and time) to the management information of the user DB 152.

[0080] After the deletion date and time is registered, the server 150 does not transmit reminding information and related information for the reminding setting associated with the deletion date and time.

[0081] [9. Information flow (user registration)] 8 is a flowchart of a process for user registration executed in server 150. In server 150, the process is carried out by, for example, CPU 1 executing a given program.

[0082] In step S10, the server 150 determines whether or not a user registration request has been received from the user terminal 100. The user terminal 100 transmits the user registration request to the server 150, for example, by accessing a given web page.

[0083] Server 150 holds the control at step S10 until it determines that a request for user registration has been accepted (NO in step S10), and when it determines that the request has been accepted (YES in step S10), it proceeds to step S12.

[0084] In step S12, the server 150 provides the user terminal 100 with a user registration screen.

[0085] FIG. 9 is a diagram showing an example of a user registration screen. A screen 910 in FIG. 9 includes five input fields 911 to 915 for inputting information constituting user information, and a registration button 916. Each of the input fields 911, 912, 913, 914, and 915 is a field for inputting a user name, an email address, a gender, a generation (an age group to which the user belongs), and an area, respectively. Note that the user terminal 100 may acquire information to be input into each field by a method other than accepting an input operation from the user. For example, the user terminal 100 may identify an area corresponding to the user based on location information acquired by the GPS module 40, and input the identified area into the input field 519.

[0086] When the registration button 916 is operated, the user terminal 100 transmits the information (user information) entered in the entry fields 911 to 915 to the server 150.

[0087] In step S14, server 150 determines whether or not it has received user information from user terminal 100. Server 150 holds control at step S14 until it determines that it has received user information (NO in step S14), and when it determines that it has received user information (YES in step S14), it proceeds to step S16.

[0088] In step S16, server 150 registers the user information in user DB 152. Thereafter, server 150 ends the process of FIG.

[0089] [10. Information flow (Registering reminder settings)] 10 is a flowchart of a process executed by server 150 for registering a reminder setting. In server 150, the process is performed by, for example, CPU 1 executing a given program.

[0090] In step S20, the server 150 determines whether or not a request for registering a reminder setting has been received from the user terminal 100. The user terminal 100 transmits the request for registering a reminder setting to the server 150, for example, by accessing a given web page.

[0091] Server 150 holds the control at step S20 until it determines that a request for registering a reminder setting has been accepted (NO in step S20), and when it determines that the request has been accepted (YES in step S20), it proceeds to step S22.

[0092] In step S22, the server 150 provides the user terminal 100 with a registration screen for setting reminders.

[0093] 11 is a diagram showing an example of a reminder setting registration screen. The following message is displayed in a message display area 921 of a screen 920 in FIG.

[0094] "Please select a product selection method. (1) Photograph the QR code. (2) Enter product identification information." This message includes two options for the method of inputting information that identifies the product. The user selects either (1) or (2) and then operates the selection button 922 to select the method of inputting information that identifies the product.

[0095] 12 is a diagram showing another example of the reminder setting registration screen 930. The screen 930 in FIG. 12 is provided to the user terminal 100 after the method is selected according to the screen in FIG.

[0096] A screen 930 in Fig. 12 includes three display areas 931, 932, and 933. The display area 931 includes information on the identified product, and in the example of Fig. 12, displays the product name (Toppan Biscuits) and the manufacturer of the product (Company A).

[0097] Display area 932 is an area for inputting a reminder setting date. Display area 933 is an area for inputting whether or not distribution is permitted.

[0098] The screen 930 includes a send button 934. When the send button 934 is operated, the user terminal 100 sends the information input on the screen 930 to the server 150.

[0099] 10, in step S24, server 150 determines whether or not a reminder setting has been received from user terminal 100. Server 150 holds control at step S24 until it determines that a reminder setting has been received (NO in step S24), and when it determines that a reminder setting has been received (YES in step S24), it proceeds to control to step S26.

[0100] In step S26, the server 150 registers the reminder setting in the user DB 152. After that, the server 150 ends the process of FIG.

[0101] [11. Information flow (notification)] 13 is a flowchart of a process in the server 150 for performing various notifications to the user terminal 100. In the server 150, the process is performed for each product registered in the user DB 152, and the process is performed, for example, by the CPU 1 executing a given program.

[0102] In step S30, server 150 determines whether or not a deletion date and time (FIG. 7) is registered for the product to be processed in user DB 152. If server 150 determines that the deletion date and time is not registered (NO in step S30), it advances control to step S32, and if it determines that the deletion date and time is registered (YES in step S30), it ends the processing in FIG.

[0103] In step S32, server 150 determines whether the reminder setting date registered for the product to be processed has arrived. More specifically, if the reminder setting date is before the current day, server 150 determines that the reminder setting date has arrived, and if the reminder setting date is after the current day, server 150 determines that the reminder setting date has not arrived. If server 150 determines that the reminder setting date has arrived (YES in step S32), it proceeds to control to step S40, and if not (NO in step S32), it proceeds to control to step S34.

[0104] In step S40, the server 150 transmits the reminding information to the user. The user receives the reminding information at the user terminal 100.

[0105] 14 is a diagram showing an example of a screen displaying reminder information. A screen 940 includes three display areas 941, 942, and 943. The display area 941 displays a message encouraging a purchase. The display area 942 displays information about the target product, more specifically, the product name and the product manufacturer. The display area 943 displays a method for purchasing the target product, more specifically, includes an introduction to a site on the network where the target product can be purchased and the URL (universal resource locator) of the site.

[0106] Screen 940 further includes two buttons 944 and 945. Button 944 is operated to instruct the end of display of screen 940. Button 945 is operated not only to end display of screen 940 but also to instruct server 150 to delete the reminder setting for the target product.

[0107] 13, after providing the reminder notification in step S40, server 150 determines in step S42 whether or not an instruction to delete the reminder setting has been received from user terminal 100. If server 150 determines that an instruction to delete the reminder setting has been received (YES in step S42), it proceeds to control step S44, and if not (NO in step S42), it returns control to step S32.

[0108] In step S44, server 150 registers the "deletion date and time" for the reminder setting of the target product in user DB 152, and ends the process in Fig. 13. As the "deletion date and time", the date and time when step S44 is executed may be registered.

[0109] In step S34, server 150 determines whether "permission setting" is registered in the reminder setting of the product to be processed. If server 150 determines that "permission setting" is registered (YES in step S34), it proceeds to control step S400, and if server 150 determines that "permission setting not set" is registered (or "permission setting" is not registered) (NO in step S34), it proceeds to control step S36.

[0110] In step S400, server 150 notifies the user of related information. 15 is a flowchart of the subroutine of step S400. The contents of the control of step S400 will be described with reference to FIG.

[0111] In step S402, server 150 determines whether the current time is the timing when the user has registered a reminder setting in server 150. If server 150 determines that the current time is the timing when the reminder setting has been registered (YES in step S402), it advances control to step S404, and if not (NO in step S402), it advances control to step S406.

[0112] In step S404, server 150 provides user terminal 100 with a notification screen for notifying the completion of registration, and returns control to FIG.

[0113] 16 is a diagram showing an example of a screen for notifying the completion of registration. A screen 950 includes three areas 951, 952, and 953. The area 951 includes a message of thanks for the registration. The area 952 includes information on the target product. The area 953 includes a reminder setting date.

[0114] Returning to Fig. 15, in step S406, server 150 determines whether a certain period of time has passed since the date and time when the reminder setting was registered (registration date and time in Fig. 5). If server 150 determines that a certain period of time has passed since the registration date and time (YES in step S406), it advances control to step S408, and if not (NO in step S406), it advances control to step S410. Note that server 150 may advance control to step S408 in response to the fact that a predetermined period of time (for example, the standard expiration date (Fig. 4)) for the target product has passed since the date and time when the reminder setting was registered in step S406.

[0115] In step S408, server 150 provides user terminal 100 with a screen displaying information according to the number of days that have passed, and returns control to FIG.

[0116] The certain period in step S406 may be set for each product, may be set for each product category, or may be arbitrarily set by the administrator of the information provision system 10. The type of "certain period" set in the information provision system 10 may be one type or multiple types.

[0117] 17 is a diagram showing an example of a screen that displays information according to the number of days that have passed. Screen 960 includes three areas 961, 962, and 963. Area 961 includes a message asking about the usability of the target product. Area 962 includes information about the target product. Area 963 includes link information for posting comments about the target product on a word-of-mouth site or the site of the manufacturer of the target product.

[0118] Returning to Fig. 15, in step S410, server 150 determines whether the day set for transmitting seasonal information (seasonal information transmission date) has arrived. Server 150 may adjust the seasonal information transmission date based on the "area" registered in user DB 152. For example, server 150 may adjust the seasonal information transmission date so that information on the season "spring" is transmitted to users in area B, which is located north of area A, later than information on users in area A.

[0119] If server 150 determines that the seasonal information transmission date has arrived (YES in step S410), it proceeds to step S412, and if not (NO in step S410), it proceeds to step S414.

[0120] In step S412, server 150 provides user terminal 100 with a screen displaying information according to the season, and returns control to FIG.

[0121] 18 is a diagram showing an example of a screen displaying information according to the season. Screen 970 includes three areas 971, 972, and 973. Area 971 includes a message presenting information on a product related to the target product along with seasonal greetings. Area 972 includes an image of the product identified by the information presented in area 971. Area 973 includes link information of a site where the product displayed in area 972 can be purchased.

[0122] 15, in step S414, server 150 determines whether the day (expected arrival date) when the remaining amount of the target product is expected to reach or fall below a predetermined remaining amount has arrived. If server 150 determines that the expected arrival date has arrived (YES in step S414), control proceeds to step S416, and if not (NO in step S414), control proceeds to step S418.

[0123] The server 150 may calculate the expected arrival date based on the volume or number of the target product and the estimated usage. For example, assume that the target product is a "detergent", the estimated usage is 50 g per day, and the volume of the target product is 800 g. Assume that the predetermined remaining amount is 10% of the capacity. In this case, the remaining amount of the target product is predicted to reach 50 g, which is less than 10% (80 g) of the capacity, 15 days after the registration date. Therefore, in this case, the server 150 advances the control to step S416 after 15 days from the registration date.

[0124] In step S416, server 150 provides user terminal 100 with a screen displaying information relating to the remaining amount, and returns control to FIG.

[0125] 19 is a diagram showing an example of a screen displaying information referring to the remaining amount. Screen 980 includes four areas 981, 982, 983, and 984. Area 981 includes a message notifying that the remaining amount is low. Area 982 includes information on the target product. Area 983 includes information on a store where the target product displayed in area 982 can be purchased (for example, a sales store registered in product DB 151), and includes information on a store in an area specified by an area registered in user DB 152. Area 984 includes link information of a site where the target product can be purchased.

[0126] 15, in step S418, server 150 determines whether the date on which the reminder setting for the target product is scheduled to be deleted (scheduled deletion date) has arrived. If server 150 determines that the scheduled deletion date has arrived (YES in step S418), it proceeds to step S420, and if not (NO in step S418), it proceeds to step S422.

[0127] For example, the server 150 may determine the planned deletion date based on the average number of days between the registration and deletion of reminder settings for products in the same category as the target product (or the same product) from the history of the registration of multiple reminder settings in the user DB 152.

[0128] In step S420, server 150 provides user terminal 100 with a screen (eg, FIG. 19) displaying information relating to the remaining amount, and returns control to FIG.

[0129] 15, in step S422, server 150 determines whether the delivery date (delivery setting date) of the information set by the manufacturer of the target product has arrived. If server 150 determines that the delivery setting date has arrived (YES in step S422), it advances control to step S424, and if not (NO in step S422), it advances control to step S426. The delivery setting date is registered, for example, in delivery management DB 153 as the purchasing manufacturer and / or purchasing category.

[0130] In step S424, server 150 provides user terminal 100 with a screen displaying distribution information (manufacturer distribution information) registered by the manufacturer of the target product, and returns control to FIG.

[0131] 20 is a diagram showing an example of a screen displaying manufacturer distribution information. Screen 990 includes two areas 991 and 992. Area 991 includes an introduction and link information of a purchase site for a product related to the target product. Area 992 includes a message indicating that screen 990 is information on a product related to the target product.

[0132] 15, in step S426, server 150 determines whether or not the information distribution date (area distribution date) set for the area registered in user DB 152 has arrived. If server 150 determines that the area distribution date has arrived (YES in step S426), it proceeds to control to step S428, and if not (NO in step S426), it returns control to FIG.

[0133] In step S428, server 150 provides user terminal 100 with a screen displaying information related to the registered area (area-related information), and returns control to FIG. 13. Area-related information is, for example, information about an event such as a festival held in the registered area. Area-related information is information about a product related to the event, and may include information about a product of the manufacturer of the target product. Thereafter, server 150 returns control to FIG. 13.

[0134] Returning to FIG. 13, when control is returned to FIG. 13, server 150 advances control to step S36.

[0135] In step S36, the server 150 determines whether or not an instruction to delete the reminder setting has been received from the user terminal 100. The server 150 may accept an instruction to delete the reminder setting from the user terminal 100 on the various notification screens described with reference to Fig. 15. If the server 150 determines that an instruction to delete the reminder setting has been received (YES in step S36), the server 150 proceeds to control step S38, and if not (NO in step S36), the server 150 returns control to step S30.

[0136] In step S38, server 150 registers the "deletion date and time" for the reminder setting of the target product in user DB 152, and returns the control to step S30.

[0137] According to the notification of related information described above with reference to Figs. 15 to 20, the related information of the target product is transmitted at a timing before the reminder setting date arrives.

[0138] The related information is not limited to information encouraging the purchase of the target product or products related to the target product (for example, other products from the same manufacturer), but may also be useful information such as how to use or manage the target product.

[0139] 21 is a diagram showing an example of a screen displaying related information. Screen 994 includes two areas 995 and 996. Area 995 includes a message regarding a method for storing the target product. Area 996 includes an explanation that the reason screen 994 has been sent to user terminal 100 is that the user of user terminal 100 has registered a reminder setting for the target product in server 150.

[0140] 15, the provision of the screens in steps S404, S408, S412, S416, S420, S424, and S428 may be performed at the same timing. That is, for example, the provision of the screen in step S408 and the provision of the screen in step S412 may be performed on the same day. In this case, after executing the control of step S408, server 150 advances the control to step S410.

[0141] Each embodiment disclosed herein should be considered as illustrative in all respects and not restrictive. The scope of the present invention is indicated by the claims, not by the above description, and is intended to include all modifications within the meaning and scope of the claims. In addition, the inventions described in the embodiments and each modified example are intended to be implemented, as far as possible, either alone or in combination. [Explanation of symbols]

[0142] 10 information systems, 100 user terminals, 150 servers, 200 products, 210 codes, 300 users.

Claims

1. 1. A computer-implemented method for providing information, comprising: A step of acquiring, from a user, identification information for identifying a product purchased by the user or inherited by the user, and deadline information for specifying a timing of a reminder regarding the product; A step of determining whether or not a timing corresponding to the deadline information has arrived; transmitting information related to the product to the user in response to determining that the timing corresponding to the deadline information has not arrived; sending, to the user, reminder information encouraging the user to purchase the product in response to determining that a time corresponding to the deadline information has arrived; How to provide information, including:

2. The information providing method according to claim 1 , wherein the step of transmitting the related information includes transmitting the related information in response to a lapse of a certain period of time from acquisition of the identification information and the expiration date information, and in response to the arrival of a date associated with the product.

3. The information providing method according to claim 1 or claim 2, wherein the related information includes at least one of information inquiring about the usability of the product associated with the identification information in a product database, information about related products, information referring to a predicted remaining amount based on the capacity of the product and the number of days elapsed since the expiration date information was obtained, and information on storage methods.

4. the related information is information referring to a remaining amount predicted based on a volume of the product and the number of days elapsed since the expiration date information was obtained, The information providing method according to claim 3 , further comprising the step of specifying a timing for executing the step of transmitting the related information in response to the predicted remaining amount reaching a predetermined amount or less.

5. The information providing method according to claim 4 , wherein the step of specifying the execution time includes calculating the remaining amount using a reference value of a usage amount of the product in a unit period.

6. A step of accepting disabling of the reminder; The information providing method of claim 3, further comprising a step of identifying the timing at which a time has elapsed from the acquisition of the identification information to the invalidation of the reminder for another product belonging to the same classification as the product after the expiration information has been acquired as the time to execute the step of sending the reminder information.

7. The information providing method described in claim 3, wherein the step of transmitting the related information includes transmitting the related information at a timing specified by the provider of the product.

8. The method further includes the step of acquiring an attribute of the user; The attribute includes information for identifying an area, 8. The information providing method according to claim 1, wherein the related information includes information about a store in the area where the product can be purchased.

9. The method further includes the step of acquiring an attribute of the user; The attribute includes information for identifying an area, 9. The information providing method according to claim 1, wherein the step of transmitting the related information includes transmitting the related information at a timing associated with the area.

10. A program that, when executed by a processor of a computer, causes the computer to implement the information providing method according to any one of claims 1 to 9.

11. A storage device for storing the program according to claim 10; and a processor that executes a program stored in the storage device.

Images