Store issued ticket management system and store issued ticket management device

Abstract

To provide a store issued ticket management system capable of retaining data while keeping confidentiality, and a store issued ticket management device.SOLUTION: In a store issued ticket management system, when using a coupon, if a user can be authenticated, a server 100 determines stores in an area from a present position of a portable terminal 200 of the user, determines secret coupons in the area and acquired normal coupons from acquired coupons of the user (S77) and transmits a storage file URL of such coupons to the portable terminal 200 (79). In a case where coupon data are received, the portable terminal 200 displays the coupons (S85). In a case where the portable terminal 200 is positioned outside of the area of shops, the secret coupons are nor displayed on the portable terminal 200.SELECTED DRAWING: Figure 9

Description

[Technical field]

[0001] The present invention relates to a store-issued ticket management system, and more particularly to a process for hiding store-issued ticket data on a user terminal. [Background technology]

[0002] Patent Document 1 discloses a system for distributing electronic coupons that can be used in a store as a method for encouraging more customers to visit the store and improving the store's profits.

[0003] In addition, there are various ways to obtain such coupons, such as sending a URL for obtaining the coupon via email, or reading a QR code prepared by the store when a customer visits the store. [Prior art documents] [Patent documents]

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

[0005] However, the above-mentioned coupon distribution system has the following problems: A user who receives such a coupon must keep the coupon in his / her terminal. In that case, coupons that the user does not want family members to see are discarded, resulting in the problem that the coupon cannot be used.

[0006] It is necessary to hold promotional information securely while preventing others from finding out that they are holding the coupon.

[0007] Such confidential data storage may also be required for store-issued tickets other than coupons, as well as bookmarks in browser programs, users registered in SNS services, and applications installed on smartphones.

[0008] SUMMARY OF THE PRESENT EMBODIMENT An object of the present invention is to provide a management system capable of solving the above problems and holding data while maintaining confidentiality. [Means for solving the problem]

[0009] (1) A store-issued ticket management system according to the present invention comprises: A) a server having the following a1) to a5); a1) a store-issued ticket data storage means for storing store-issued ticket data including a store-issued ticket ID and issued entity data; a2) a store data storage means for storing a store ID, an area identification data, and an issued store-issued ticket data ID in association with each other; a3) a user data storage means for storing a user ID and an acquired store-issued ticket data ID; a4) a control means for identifying acquired store-issued ticket data of a user identified by a user ID by referring to the user data storage means; a5) a distribution means for distributing the issued entity data of the identified store-issued ticket data; B) a user terminal having the following b1) to b4); b1) a position data acquisition means for acquiring current location data; b2) a transmission means for transmitting a user ID and the position data to the server; b3) a receiving means for receiving the issued entity data from the server; and b4) a notification means for notifying the issued entity data. Furthermore, C) the user data storage means of the server stores a user-set display flag, which is determined by the user as to whether the acquired store-issued ticket data is to be displayed or hidden on the user terminal, in association with the store-issued ticket data ID, and D) the control means of the server, based on the user ID and location data provided from the user terminal, does not specify acquired store-issued ticket data of the user as a target for distribution to the user terminal if the location is not within a range specified by the area specification data of the store that issued the acquired store-issued ticket. Thus, a management system capable of holding data while maintaining confidentiality can be provided.

[0010] (2) The store-issued ticket management system of the present invention comprises: A) a server having the following a1) to a5); a1) a store-issued ticket data storage means for storing store-issued ticket data including a store-issued ticket ID and issued entity data; a2) a store data storage means for storing a store ID, an area identification data, and an issued store-issued ticket data ID in association with each other; a3) a user data storage means for storing a user ID and an acquired store-issued ticket data ID; a4) a control means for identifying the acquired store-issued ticket data of a user identified by a user ID by referring to the user data storage means; a5) a distribution means for distributing the issued entity data of the identified store-issued ticket data; B) a user terminal having the following b1) to b4); b1) a position data acquisition means for acquiring current position data; b2) a transmission means for transmitting the user ID and the position data to the server; b3) a receiving means for receiving the issued entity data from the server; and b4) a notification means for notifying the issued entity data. Furthermore, D) the issuing entity data includes first issuing entity data indicating the existence of the store-issued ticket for the user and second issuing entity data indicating the benefit of the store-issued ticket, and E) the control means of the server determines, based on the user ID and location data provided from the user terminal, the acquired store-issued ticket data whose location is within the range specified by the area specification data of the store that issued the acquired store-issued ticket and the acquired store-issued ticket data whose location is outside the range, and for the acquired store-issued ticket data whose location is outside the range, the first issuing entity data is set as the issuing entity data, and for the acquired store-issued ticket data whose location is within the range, the first issuing entity data and the second issuing entity data are set as the issuing entity data. Therefore, for the acquired store-issued ticket data whose location is within the range, the first issuing entity data and the second issuing entity data are notified, but for the acquired store-issued ticket data whose location is outside the range, the first issuing entity data is notified. This makes it possible to treat a part of the issuing entity data as not to be notified depending on the location of the user terminal.

[0011] (3) In the store-issued ticket management system according to the present invention, the store-issued ticket data is a stamp card for the store. Therefore, depending on the location of the user terminal, the existence of the stamp card itself can be hidden, or part of the stamp card can be excluded from notification.

[0012] (4) In the store-issued ticket management system according to the present invention, the store-issued ticket data is a coupon that can be used at the store. Therefore, depending on the location of the user terminal, the existence of the coupon itself can be hidden, or part of the coupon can be excluded from notification.

[0013] (5) In the store-issued ticket management system of the present invention, the store data storage means is set with a group ID that enables multiple stores to be managed as the same group, and if there is store-issued ticket data of other stores in the group to which the store containing the acquired store-issued ticket data to be distributed belongs, the control means of the server also identifies the store-issued ticket data of the other stores as the acquired store-issued ticket data.

[0014] (6) A store-issued ticket management system according to the present invention includes: A) a server having the following a1) to a5): a1) a store-issued ticket data storage means for storing store-issued ticket data including a store-issued ticket ID and issued entity data; a2) a store data storage means for storing a store ID, area identification data, and an issued store-issued ticket data ID in association with each other; a3) a user data storage means for storing a user ID and an acquired store-issued ticket data ID; a4) a control means for identifying the acquired store-issued ticket data of a user identified by the user ID by referring to the user data storage means; and a5) a distribution means for distributing the issued entity data of the identified store-issued ticket data. B) A user terminal having the following b1) to b4): b1) a location data acquisition means for acquiring current location data; b2) a location data transmission means for transmitting a user ID and the location data to the server; b3) a receiving means for receiving the issued entity data from the server; b4) a notification means for notifying the issued entity data; b5) an input means for a user to input a user setting display flag for hiding the acquired store-issued ticket data in the user terminal for the notified issued entity data; and b6) a user setting display flag transmission means for transmitting the input user setting display flag to the server. Furthermore, the control means of the server d1) upon receiving the user setting display flag stores the user setting display flag in the user data storage means, and d2) based on the user ID and location data provided from the user terminal, determines whether or not the location of acquired store-issued ticket data for which the user setting display flag is in a hidden state is within the range specified by the area specification data of the store that issued the acquired store-issued ticket, and if not within the range, does not specify the acquired store-issued ticket data as a target for distribution to the user terminal. Therefore, if the location of the user terminal is not within the range specified by the area specification data of the store that issued the acquired store-issued ticket, the acquired store-issued ticket data is not distributed to the user terminal.

[0015] (7) A store-issued ticket management system according to the present invention includes: A) a server having the following a1) to a5): a1) a store-issued ticket data storage means for storing store-issued ticket data including a store-issued ticket ID and issued entity data; a2) a store data storage means for storing a store ID, area identification data, and an issued store-issued ticket data ID in association with each other; a3) a user data storage means for storing a user ID and an acquired store-issued ticket data ID; a4) a control means for referring to the user data storage means to identify acquired store-issued ticket data of a user identified by a user ID; and a5) a control means for distributing the issued entity data of the identified store-issued ticket data. The present invention is provided with: a distribution means; B) a user terminal having the following b1) to b4); b1) location data acquisition means for acquiring current location data; b2) assignment means for providing a user ID and the location data to the server; b3) notification means for notifying the issued entity data when it is received from the server; b4) input means for a user to input a user setting display flag for making the acquired store-issued ticket data hidden in the user terminal for the notified issued entity data; and b5) user setting display flag transmission means for transmitting the input user setting display flag to the server. Furthermore, D) the issuing entity data includes first issuing entity data indicating the existence of the store-issued ticket for the user, and second issuing entity data indicating a benefit provided by the store-issued ticket, and E) the control means, based on the user ID and location data provided from the user terminal, determines, from the acquired store-issued ticket data of the user, acquired store-issued ticket data whose location is within a range specified by the area specification data of the store that issued the acquired store-issued ticket and acquired store-issued ticket data whose location is outside that range, and determines the first issuing entity data for acquired store-issued ticket data that is outside that range, and the first issuing entity data and second issuing entity data for acquired store-issued ticket data that is within that range. Therefore, for acquired store-issued ticket data that is within that range, the first issuing entity data and second issuing entity data are notified, but for acquired store-issued ticket data that is outside that range, the first issuing entity data are notified.This makes it possible to treat a portion of the issuing entity data as not to be notified depending on the location of the user terminal.

[0016] (8) A store-issued ticket management system according to the present invention includes a store-issued ticket data storage means for storing store-issued ticket data including a store-issued ticket ID and issued entity data, a store data storage means for storing a store ID, area identification data, and an issued store-issued ticket data ID in association with each other, a user data storage means for storing a user ID and an acquired store-issued ticket data ID, a control means for identifying the acquired store-issued ticket data of a user identified by a user ID by referring to the user data storage means, and a distribution means for distributing the issued entity data of the identified store-issued ticket data, wherein the user data storage means stores a user-set display flag determined by a user as to whether the acquired store-issued ticket data is to be displayed or hidden on the user terminal, in association with the store-issued ticket data ID, and the control means, based on the user ID and location data provided from the user terminal, does not identify the acquired store-issued ticket data of the user as a target for distribution to the user terminal if the location of the acquired store-issued ticket data is not within a range identified by the area identification data of the store that issued the acquired store-issued ticket. Therefore, it is possible to provide a management system that is capable of holding data while maintaining confidentiality.

[0017] (9) A store-issued ticket management system according to the present invention includes a store-issued ticket data storage means for storing store-issued ticket data including a store-issued ticket ID and issued entity data, a store data storage means for storing a store ID, area identification data, and an issued store-issued ticket data ID in association with each other, a user data storage means for storing a user ID and an acquired store-issued ticket data ID, a control means for identifying the acquired store-issued ticket data of a user identified by the user ID by referring to the user data storage means, and a distribution means for distributing the issued entity data of the identified store-issued ticket data, wherein the issued entity data is a first issuing entity data indicating the existence of the store-issued ticket for the user. The control means determines, based on the user ID and location data provided from the user terminal, acquired store-issued ticket data of the user that is within a range specified by the area specification data of the store that issued the acquired store-issued ticket and acquired store-issued ticket data that is outside the range, and sets the first issuing entity data as the issuing entity data for the acquired store-issued ticket data that is outside the range, and sets the first issuing entity data and the second issuing entity data as the issuing entity data for the acquired store-issued ticket data that is within the range. Therefore, for acquired store-issued ticket data that is within the range, the first issuing entity data and the second issuing entity data are notified, but for acquired store-issued ticket data that is outside the range, the first issuing entity data is notified. This makes it possible to treat a part of the issuing entity data as not to be notified depending on the location of the user terminal.

[0018] (10) A store-issued ticket management server according to the present invention includes a store-issued ticket data storage means for storing store-issued ticket data including a store-issued ticket ID and issued entity data, a store data storage means for storing a store ID, area identification data, and an issued store-issued ticket data ID in association with each other, a user data storage means for storing a user ID and an acquired store-issued ticket data ID, a control means for identifying acquired store-issued ticket data of a user identified by a user ID by referencing the user data storage means, and a distribution means for distributing the issued entity data of the identified store-issued ticket data, and the control means is configured to: 1) receive from a user terminal the acquired store-issued ticket data for a specific store, When a user-set display flag that hides store-issued ticket data on the user terminal is received, the user-set display flag is stored in the user data storage means as the user-set display flag for the store of the user, and 2) for acquired store-issued ticket data for which the user-set display flag is hidden based on the user ID and location data provided from the user terminal, the location data is used to determine whether or not the location is within a range specified by the area identification data of the store that issued the acquired store-issued ticket, and if not within the range, the acquired store-issued ticket data is not specified as a target for distribution to the user terminal. Therefore, if the location of the user terminal is not within a range specified by the area identification data of the store that issued the acquired store-issued ticket, the acquired store-issued ticket data is not distributed to the user terminal.

[0019] (11) A store-issued ticket management server according to the present invention includes a store-issued ticket data storage means for storing store-issued ticket data including a store-issued ticket ID and issued entity data, a store data storage means for storing a store ID, area identification data, and an issued store-issued ticket data ID in association with each other, a user data storage means for storing a user ID and an acquired store-issued ticket data ID, a control means for identifying the acquired store-issued ticket data of a user identified by the user ID by referring to the user data storage means, and a distribution means for distributing the issued entity data of the identified store-issued ticket data, wherein the issued entity data is a first issue indicating the existence of the store-issued ticket for the user. The control means includes a user ID and location data provided by the user terminal, and determines, among the acquired store-issued ticket data of the user, acquired store-issued ticket data whose location is within a range specified by the area specification data of the store that issued the acquired store-issued ticket and acquired store-issued ticket data whose location is outside the range, and determines the first issued entity data for acquired store-issued ticket data that is outside the range, and the first issued entity data and the second issued entity data for acquired store-issued ticket data that is within the range. Therefore, for acquired store-issued ticket data that is within the range, the first issued entity data and the second issued entity data are notified, but for acquired store-issued ticket data that is outside the range, the first issued entity data is notified. This makes it possible to treat a part of the issued entity data as not to be notified depending on the location of the user terminal.

[0020] (12) A store-issued ticket management system according to the present invention comprises: A) a server having the following a1) to a5); a1) a store-issued ticket data storage means for storing store-issued ticket data including a store-issued ticket ID and issued entity data; a2) a store data storage means for storing a store ID, an area identification data, and an issued store-issued ticket data ID in correspondence with each other; a3) a user data storage means for storing a user ID and an acquired store-issued ticket data ID; a4) a control means for identifying acquired store-issued ticket data of a user identified by a user ID by referring to the user data storage means; a5) a distribution means for distributing the issued entity data of the identified store-issued ticket data; B) a user terminal having the following b1) to b4); b1) a location data acquisition means for acquiring current location data; b2) a transmission means for transmitting a user ID to the server; b3) a receiving means for receiving the issued entity data from the server; and b4) a notification means for notifying the issued entity data; and C) the following means. a user-set display flag storage means for storing a user-set display flag, determined by the user as to whether the acquired store-issued ticket data should be displayed or hidden in the user terminal, in correspondence with the store-issued ticket data ID, and a non-notification decision means for, when receiving store-issued ticket data from the server, not causing the notification means to notify the received acquired store-issued ticket data of the user based on the location data of the user terminal and the area identification data stored in the store data storage means if the location of the acquired store-issued ticket data of the user is outside the range identified by the area identification data of the store that issued the acquired store-issued ticket. Thus, a management system capable of holding data while maintaining confidentiality can be provided.

[0021] (13) A system for displaying message exchanges between users according to the present invention comprises: A) a server having the following a1) to a4): a1) a user data storage means for storing user data including a user ID; a2) a message user storage means for storing a user ID of a user determined as a user with whom messages will be exchanged, the user ID being a message exchange user; a3) a message storage means for storing messages exchanged between the message exchange user and the message exchange user; a4) a distribution means for, upon receiving a user ID, referring to the message exchange user storage means and the message storage means, specifying a message exchange user of a user specified by the user ID, and distributing screen generation data for generating a message list display screen displaying a list of the message exchange users and a message display screen displaying message exchanges with the message exchange user; B) a user terminal having the following b1) to b3); b1) a location data acquisition means for acquiring a current location as current location data; and b2) a transmission means for transmitting the user ID to the server; b3) a display means for displaying a message list display screen based on the screen generation data when the screen generation data is received from the server, and for displaying a message display screen with a specific user when the specific user is selected on the message list display screen, and the user data storage means stores area specific data identifying the location of the user; C) the user-to-user message exchange display system has the following means: a user setting display flag storage means for storing a user setting display flag set by the user of the user terminal, which is a flag that determines whether the message exchange user is displayed or not on the message list display screen; D) a limited display means for determining whether the current location of the user terminal that transmitted the user ID is within a range in which the registered user is displayed on the message list display screen, and if not within the range, for displaying a message list display screen in which the message exchange user is not displayed on the message list display screen.Therefore, it is possible to provide a system that allows messages exchanged between users to be displayed while maintaining confidentiality.

[0022] (14) A web browsing system according to the present invention comprises: A) a server having the following a1) to a5), a website data storage means for storing website URIs and corresponding notification target data, and a distribution means for distributing notification target data corresponding to a specified website URI to a user terminal based on a distribution request from the user terminal; B) a user terminal having the following b1) to b4), b1) location data acquisition means for acquiring current location data, b2) transmission means for making a distribution request for notification target data corresponding to a website URI along with a user ID and the location data, and b3) notification means for receiving the notification target data from the server and notifying it; C) user setting display flag storage means for storing a user setting display flag determined by a user as to whether the notification target data should be displayed or hidden in the user terminal, in correspondence with the store-issued ticket data ID; and D) limited display means for hiding the requested notification target data on the user terminal if the location of the requested notification target data is not within a specified range based on the user ID and location data provided from the user terminal. Therefore, it is possible to provide a web browsing system that enables web browsing while maintaining confidentiality.

[0023] (15) In the web browsing system according to the present invention, the server stores a dummy screen indicating that the notification target data does not exist together with the notification target data corresponding to the URI, and the limited display means displays the dummy screen when the notification target data is not specified as a target for distribution to the user terminal. Thus, it is possible to provide a web browsing system that enables web browsing while maintaining confidentiality.

[0024] The terms used in this specification are explained below.

[0025] The term "store-issued ticket" refers to a ticket distributed by a store to attract customers, and in this embodiment, it corresponds to a coupon. Also, it may be a membership card or a point card other than a coupon. If a membership card is displayed when it is located within a certain range from the store, it can be displayed to encourage customers to visit the store.

[0026] In the first embodiment, the "issued entity data" corresponds to the image data of the coupon shown in Fig. 4C. In the second embodiment, the "issued entity data" corresponds to the first and second display data shown in Fig. 11. In the embodiments, the "area specific data" corresponds to the position data detected by the position data detection unit and a range at a certain distance from the position data, but instead of specifying the area by the center and a certain distance, the area may be the name of an area on a map (for example, Ginza 4-chome) or an area divided into meshes on the map data.

[0027] The "user-set display flag" refers to a flag that allows the user to determine whether the acquired store-issued ticket data is to be displayed or hidden on the user terminal.

[0028] In the second embodiment, the "first issued entity data" and the "second issued entity data" correspond to the first and second display data shown in FIG.

[0029] The "notification means" includes not only the display means shown in the embodiment, but also any other means capable of notifying the user by voice or the like.

[0030] A "message exchanging user" refers to a user who is registered as a person with whom to exchange messages on an SNS service; for example, in the case of LINE (registered trademark), this would be a friend.

[0031] A "message list display screen" is a screen that displays a list of users exchanging messages. A "user-set display flag" is a flag that the user decides whether to display or hide. It includes flags that are set by default by the store and approved by the user. A "dummy screen" is a form of hidden display, and is data that actively notifies the user that something does not exist. [Brief description of the drawings]

[0032] [Figure 1] FIG. 2 is a functional block diagram of the store-issued ticket management system 1 (when a coupon is used). [Diagram 2] FIG. 1 is a diagram illustrating an example of a hardware configuration in which a server 100 is realized using a CPU. [Diagram 3] FIG. 2 illustrates an example of a hardware configuration of a user terminal 200. [Figure 4] 4A and 4B are diagrams illustrating data structures of store data and coupon data. [Diagram 5] FIG. 11 is a diagram showing user data. [Figure 6] 13 is a flowchart showing a process for registering a coupon. [Figure 7] 13 is a flowchart showing a process for a user to obtain a coupon. [Figure 8] 13 is an example of an acquired coupon displayed on a screen of the user terminal 200. [Figure 9] 11 is a flowchart when a coupon is used in the first embodiment. [Figure 10] 13 is an example of a display screen in which the outer frame of a coupon and the coupon's benefit details are displayed, and in which only the outer frame of a coupon is displayed. [Figure 11] 1 is a data structure of coupon data. [Figure 12] 13 is a flowchart showing a process for using an acquired coupon in the second embodiment. [Figure 13] FIG. 2 is a functional block diagram of a store-issued ticket management system 51 (when a coupon is obtained). DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0033] Hereinafter, an embodiment of the present invention will be described with reference to the drawings.

[0034] (1. Overall Structure) FIG. 1 shows the overall configuration of a store-issued ticket management system 1 according to an embodiment of the present invention.

[0035] The shop-issued ticket management system 1 includes a server 100 and a user terminal 200.

[0036] The server 100 comprises a store-issued ticket data storage means 3, a store data storage means 6, a user data storage means 5, a control means 4, and a distribution means 7.

[0037] The store-issued ticket data storage means 3 stores store-issued ticket data including a store-issued ticket ID and issued entity data. The store data storage means 6 stores the store ID, area identification data, and issued store-issued ticket data ID in association with each other. The user data storage means 5 stores the user ID and the acquired store-issued ticket data ID. The control means 4 refers to the user data storage means 5 to identify the acquired store-issued ticket data of the user identified by the user ID. The distribution means 7 distributes the issued entity data of the identified store-issued ticket data.

[0038] The user terminal 200 comprises a location data acquisition means 12, a transmission means 11, a reception means 13, and a notification means 14.

[0039] The position data acquisition means 12 acquires the position data of the current position.

[0040] The transmitting means 11 transmits the user ID and the location data to the server 100 .

[0041] The receiving means 13 receives the issuing entity data from the server 100. The notifying means 14 notifies the issuing entity data.

[0042] Furthermore, the user data storage means 5 of the server 100 stores a user-set display flag, which is determined by the user as to whether the acquired store-issued ticket data is to be displayed or hidden on the user terminal, in association with the store-issued ticket data ID. Furthermore, based on the user ID and location data provided from the user terminal 200, the control means 4 does not specify the acquired store-issued ticket data of the user as a target for distribution to the user terminal if the location is not within the range specified by the area specification data of the store that issued the acquired store-issued ticket.

[0043] As a result, if the user terminal 200 is not within the range specified by the store's area specification data, the acquired store-issued ticket data is not distributed to the user terminal. Therefore, the fact that the user terminal 200 holds store-issued ticket data for a certain store is not known to anyone other than the operator of the user terminal 200.

[0044] (2. Hardware Configuration of Server 100) The hardware configuration of the server 100 shown in Fig. 1 will be described with reference to Fig. 2. This figure shows an example of a hardware configuration of the server 100 configured using a CPU.

[0045] The server 100 includes a CPU 23, a memory 27, a hard disk 26, a monitor 30, a telephone communication unit 32, a data communication unit 31, an input device 28, a voice input / output unit 24, an optical drive 25, and a bus line 29. The CPU 23 controls each unit via the bus line 29 in accordance with each program stored in the hard disk 26.

[0046] The hard disk 26 includes an operating system program 26o (hereinafter abbreviated as OS), a main program 26p, a store data storage section 26d, a coupon data storage section 26c, and a user data storage section 26u.

[0047] The processing of the main program 26p will be described later.

[0048] The data structure of the store data stored in store data storage unit 26d is shown in Fig. 4A. The store data includes a store ID, name, location, address, and issued coupon ID. The data structure of the coupon data stored in coupon data storage unit 26c is shown in Fig. 4B. The coupon data includes a coupon ID, expiration date, remaining usable number, image data, a store-set secret flag, and a storage file URL.

[0049] In addition, the store that issued each coupon can be identified by referring to the issued coupon ID stored in the store data. Also, the issuing store ID may be registered in the coupon data storage unit.

[0050] The data structure of the user data stored in the user data storage unit 26u is shown in Fig. 5A. The user data includes a user ID (UID), an authentication destination ID, a customer key, a token secret, an authentication service, an acquired coupon ID, and a user-set secret flag. The customer key, token secret, and authentication service are data for "OAuth authentication," a mechanism used to operate multiple Web services in cooperation with each other. By using OAuth authentication, not only is it unnecessary for the system to manage IDs and passwords, but it is also unnecessary for users to verify their identity when using the system.

[0051] The data communication unit 31 performs data communication with the user terminal 200 .

[0052] In this embodiment, LINUX (registered trademark or trademark) is used as the operating system program (OS) 26o, but the present invention is not limited to this.

[0053] Each of the above programs is read from the DVD-ROM 25a in which the programs are stored, via the optical drive 25, and installed on the hard disk 26. The programs may be installed on the hard disk from a computer-readable recording medium such as a USB memory, other than the DVD-ROM. Furthermore, the programs may be downloaded using a communication line.

[0054] In this embodiment, the program stored in the DVD-ROM is installed on the hard disk 26 from the DVD-ROM, thereby causing the computer to indirectly execute the program. However, without being limited to this, the program stored in the DVD-ROM may be executed directly from the optical drive 25. Programs executable by a computer include not only those that can be executed directly by simply installing them as they are, but also those that require conversion to another format (for example, decompressing compressed data) and those that can be executed in combination with other modules.

[0055] (3. Hardware Configuration of User Terminal 200) The hardware configuration of the user terminal 200 shown in Fig. 1 will be described with reference to Fig. 3. This figure shows an example of a hardware configuration of the user terminal 200 configured using a CPU.

[0056] The user terminal 200 has the configuration of a typical smartphone, and includes a CPU 123, a memory 127, a flash memory 126, a display unit 130, a communication unit 128, an operation unit 125, an audio input / output unit 124, a position information detection unit 122, a camera unit 121, and a bus line 129.

[0057] The location information detection unit 122 is a module that detects location information using the Global Navigation Satellite System (GNNS).

[0058] The CPU 123 controls each unit via a bus line 129 in accordance with each program stored in a flash memory 126 .

[0059] The flash memory 126 includes an operating system program 126o (hereinafter abbreviated as OS) and a main program 126m. In this embodiment, AndroidOS (trademark) is used as the OS.

[0060] The processing of the main program 126m will be described later. If the data received by the communication unit 128 is data to be displayed, the browser program 126b displays it on the display unit .

[0061] (5. Coupon registration process) The store manager, who is the coupon manager, logs in to server 100 and registers a new coupon. Figure 6 shows a flowchart of the coupon registration process between the coupon manager PC and server 100. The following describes a case where the coupon manager of store "EFG" issues coupon "C306".

[0062] The coupon manager PC (store terminal 300: not shown) logs in to the server 100 and requests the issuance of a coupon (step S1 in FIG. 6). The CPU 23 of the server 100 (hereinafter sometimes abbreviated to server 100) sends a coupon registration screen to the store terminal 300 (step S2). The CPU of the store terminal 300 (hereinafter sometimes abbreviated to store terminal 300) displays the coupon registration screen. In this embodiment, the coupon registration screen is a screen on which the expiration date, remaining number of usable times, image data of the coupon, and a secret flag can be input (not shown).

[0063] The image data of the coupon may be prepared separately by the coupon administrator, or may be data preregistered in the server 100 and partially modified.

[0064] When the operator of the store terminal 300 inputs the necessary data (step S5), the store terminal 300 determines whether a secret flag has been specified (step S7), and if so, turns the secret flag ON (step S9). If the answer is NO in step S7 and a coupon registration button (not shown) is selected, the input coupon is sent to the server 100 (step S12). The server 100 determines whether a secret flag has been added (step S13), and if so, registers it as a secret coupon (step S14), and if not, registers it as a normal coupon (step S15).

[0065] Coupon data after the new coupon is registered is shown in FIG. 4C. In FIG. 4C, coupon ID "C306", expiration date "2023.8.14", remaining number of available times "100", image data "C306.JPG", store-set secret flag "1", and storage file URL "WWW.a / c / cc306jpg" are added. The storage file URL may be determined by server 100.

[0066] The server 100 converts the storage file URL of the coupon into a two-dimensional barcode and transmits it to the store terminal 300 (step S16). The store terminal 300 stores this two-dimensional barcode (step S17) and ends the process.

[0067] As a result, a new coupon "C306" is stored as shown in FIG. 4C.

[0068] (5.2 Processing when obtaining a coupon (between user terminal and server)) When a customer comes to a store, the store encourages them to obtain a coupon. Specifically, the store presents the customer (user) with a piece of paper on which the coupon's two-dimensional barcode is printed, and the customer is asked to read the two-dimensional barcode with the user's device.

[0069] This allows the coupon to be distributed to the user terminal 200. This process will be described with reference to FIG.

[0070] In the following, we will explain the case where a new user "EN23022" who has not registered obtains coupon "C306" at store "EFG" on his / her user terminal and registers the coupon as a secret coupon at his / her own discretion.

[0071] The operator of the user terminal 200 reads from the user terminal 200 a two-dimensional code for issuing a coupon to obtain a coupon "C306" at the store "EFG" (step S21 in FIG. 7). By reading the two-dimensional code for issuing a coupon, the CPU 123 of the user terminal 200 (hereinafter sometimes abbreviated as the user terminal 200) starts a browser program from the main program 126m. As a result, the user terminal 200 makes a coupon acquisition request to the server 100 (step S23).

[0072] The server 100 determines whether there is a coupon acquisition request (step S25), and when there is a coupon acquisition request, transmits a login screen (not shown) (step S27) along with cookie data.

[0073] The user terminal 200 displays the login screen (step S29).

[0074] In this embodiment, the login process is executed by OAuth authentication approval process. OAuth authentication approval is a process in which, if a user has already registered with a social networking service (SNS) provider, the user allows the server 100 to obtain desired user information from the service, and the server 100 obtains the necessary personal information of the user, thereby enabling the user to log in to the system without registering a separate ID.

[0075] FIG. 8A shows an example of a login screen. On this screen, multiple SNS providers for LINE authentication and Google authentication are displayed as candidate sites for OAuth authentication approval. When the user selects the Google authentication button 151, a confirmation screen for approving OAuth authentication with Google is displayed on the user terminal, and if the user approves, OAuth authentication is performed. As a result, the server 100 is provided with an "access token" and a "token secret" from the Google site selected by the user. The server 100 registers the SNS service provider, the "access token" and the "token secret", and receives user information using the information as a key.

[0076] The server 100 judges whether to accept the "access token" and "token secret" (step S35 in FIG. 7), and if so, judges that authentication has been successful and registers the user as a new user in the system (step S38). In this way, new user "EN23022" is registered. User data before and after registration is shown in FIGS. 5A and B. In FIG. 5B, user ID "U4" and authentication destination ID "EN23022" are registered. At that time, the user ID "U4" is sent to the user terminal 200 as cookie information and stored in the browser program.

[0077] If authentication is not possible in step S35 of FIG. 7, an error message is sent to user terminal 200 (step S37).

[0078] If authentication is successful in step S35, the server 100 sends the coupon "C306" to the user terminal 200. The user terminal 200 determines whether to receive a coupon or an error message (including a re-login screen) (step S41). If an error message is received, the process returns to step S31 and the user attempts to log in again.

[0079] If a coupon is received in step S41, the acquired coupon is displayed on the screen (step S45). An example of the display is shown in Fig. 8B. In this case, the store-set secret flag is "1" and it is a normal coupon, so nothing is displayed in area 153a, but if the store-set secret flag is "0" and it is a secret coupon, the word "Secret" is displayed in area 153a to indicate that it is a secret coupon.

[0080] If the operator of the user terminal 200 wishes to change this coupon to a secret coupon, he or she selects the type change button 155 in Fig. 8B. When the type change button 155 is selected, the user terminal 200 determines that an instruction to change the type has been given (step S47), and changes the type (step S49). In other words, the normal coupon becomes a secret coupon.

[0081] After issuing such a change instruction, or if such a change instruction is not necessary, the operator of the user terminal 200 selects the Confirm button 156 in Fig. 8B. When the CPU 123 determines that the Confirm button has been selected (step S51), it transmits a confirmation instruction (step S52).

[0082] The server 100 receives the confirmation instruction and, if there is a change to the specified type, stores the change in the user data (step S53). In this case, as shown in FIG. 5C, the user-set secret flag "0" is registered for the acquired coupon "C306" of the user "EN23022."

[0083] If the confirmation button is not pressed in step S51, the mobile terminal 200 repeats the processes from step S47 onwards.

[0084] (5.3 Processing when coupon is displayed (between user terminal and server)) Next, the display process of the acquired coupon will be described with reference to Fig. 9. The operator of the user terminal 200 reads a two-dimensional code for connecting to MyPage with a camera (step S61).

[0085] The two-dimensional code for connecting to the My Page may be read from a printed material prepared at the store, or may be sent as an email or message.

[0086] The user terminal 200 launches a browser program and sends a My Page screen request to the server 100 (step S63). The server 100 determines whether or not there is a screen request (step S65), and when there is a screen request, it transmits HTML data for displaying the My Page screen (step S67). At that time, cookie information is also transmitted.

[0087] The user terminal 200 receives this HTML data and displays it (step S69). An example of the My Page screen is shown in FIG.

[0088] The operator of the user terminal 200 selects the acquired coupon display button 157. The user terminal 200 determines that the acquired coupon display button has been selected (step S70), and makes a request to display acquired coupons including the UID and current location data stored as a cookie (step S72). The current location data may be detected by the location data detection unit 122.

[0089] The server 100 refers to the user data storage unit (see FIG. 5), identifies the user from the received UID, identifies the customer key, token secret, and authentication service, and performs user authentication.

[0090] The server 100 determines whether or not the user has been authenticated (step S73), and if the user has been authenticated, it determines the stores in the area from among the coupons that the user has acquired, and determines the secret coupons in the area and the regular coupons that have been acquired (step S77).

[0091] The server 100 determines whether or not there is one or more coupons determined in step S77 (step S78), and if there is one or more coupons, reads out the storage file URL of the coupon from the coupon data storage unit and transmits it to the user terminal 200 (step S79). If the user cannot be authenticated in step S73, or if there is no coupon in step S78, an error message is sent to user terminal 200 (step S75).

[0092] The user terminal 200 determines whether to receive coupon data or an error message (step S81), and if coupon data is received, the browser program retrieves HTML data from the URL and displays the coupon (step S85). If multiple coupons have been received, the next coupon can be displayed in the coupon display section by selecting the next coupon display button 159.

[0093] If an error message is received in step S81, the user terminal 200 displays the error message (step S83), and repeats the processes from step S69 onwards.

[0094] When the button "Use coupon" is selected in Fig. 8D, the user terminal 200 determines that a request for confirmation of use has been made for the displayed coupon (step S87), and transmits the request for confirmation of use to the server 100 (step S89). In response to the request, the server 100 performs a deletion process (step S91). In this embodiment, the remaining number of usable coupons in the coupon data storage unit is decremented by one, and the acquired coupon ID stored in the user data storage unit of the user is deleted.

[0095] In this way, when the user terminal that requested the My Page screen display is located within a certain distance from the location of a certain store, the server 100 determines that the user terminal is located within the area and transmits the URL data of the secret coupon of the store, but when the user terminal is located outside the area, the URL data of the secret coupon of the store is not transmitted. Therefore, it is possible to keep the acquired coupon hidden from family members and the like.

[0096] In this embodiment, if there are no coupons in step S78, an error message is sent, just as in the case where authentication is not possible in step S73. However, it is also possible to distinguish between sending an error message saying "Authentication not possible" if authentication is not possible in step S73, and sending an error message saying "No coupons exist" if there are no coupons in step S78.

[0097] In this embodiment, whether or not the store is within a certain range is determined based on whether or not the store is within a certain distance from the store's location, but the distance may be set by the user. For example, when the screen for obtaining coupons is displayed in step S45 of FIG. 7, the range to be excluded from the range may be displayed and the user may input the range.

[0098] In this embodiment, the server 100 registers coupons to be hidden with hidden store information, and the coupons are not displayed on the user terminal 200 unless the user terminal 200 is located within the area of ​​the store. This makes it possible to hide even the existence of the coupons from the user.

[0099] The non-display store information may be the store itself or a category including the area name.

[0100] The present invention can also be understood as a system that performs the following process when registering a coupon, rather than when using the coupon.

[0101] 6) A) A server having the following a1) to a5): a1) a store-issued ticket data storage means for storing store-issued ticket data including a store-issued ticket ID and issuing entity data; a2) a store data storage means for storing a store ID, area identification data, and a store-issued ticket data ID in association with each other; a3) a user data storage means for storing a user ID and an acquired store-issued ticket data ID; a4) a control means for referring to the user data storage means and identifying store-issued ticket data already acquired by a user identified by a user ID; a5) a distribution means for distributing the issue entity data of the specified store-issued ticket data; B) A user terminal having the following b1) to b4): b1) a location data acquisition means for acquiring current location data; b2) a location data transmission means for transmitting a user ID and the location data to the server; b3) a receiving means for receiving the issuing entity data from the server; b4) a notification means for notifying the issuing entity data; b5) an input means for a user to input a user setting display flag for hiding the acquired store-issued ticket data in the user terminal with respect to the notified issued entity data; b6) a user setting display flag transmission means for transmitting the input user setting display flag to the server; C) A store ticket management system comprising: D) The control means of the server d1) upon receiving the user setting display flag, storing the user setting display flag in the user data storage means; d2) for acquired store-issued ticket data for which the user setting display flag is in a hidden state, based on the user ID and location data provided from the user terminal, determining whether or not the location is within a range specified by area specification data of the store that issued the acquired store-issued ticket, and if the location is not within the range, not specifying the acquired store-issued ticket data as a target for distribution to the user terminal; A store ticket issuing management system characterized by the above.

[0102] (6.1 Second embodiment) In the above embodiment, the secret coupon information is not sent to user terminals that are not located within the area of ​​the store that issued the secret coupon. This prevents the user from knowing about the existence of the coupon and its contents if the user terminal is not located within the area of ​​the store that issued the secret coupon.

[0103] In contrast to this, in this embodiment, the existence of the coupon itself is notified to the user.

[0104] FIG. 10A shows an example of a coupon in the second embodiment in which the contents of the coupon are hidden but the existence of the coupon itself is notified to the user. This coupon is issued by a store "Store ABC" to give the user some kind of benefit. The user who receives this coupon can be encouraged to visit Store ABC. In this case, the contents of the coupon are not displayed, so the user can look forward to the fun of visiting the store.

[0105] In order to issue a coupon indicating the existence of such a coupon while concealing the contents of the coupon, in the second embodiment, coupon data shown in Fig. 11 is stored in hard disk 26 of server 100. In Fig. 11, first display data indicating the existence of the coupon and second display data indicating the contents of the coupon are stored separately.

[0106] The other hardware configuration is the same as in the first embodiment.

[0107] A display process using the first display data and the second display data will be described with reference to Fig. 12. In the following, a case will be described in which a coupon is issued by email from the server 100 to the user terminal 200 of the user "EN23022" with UID "U4".

[0108] The process of registering a coupon from the store terminal 300 is the same as that in the first embodiment. As a result, the coupon data as shown in Fig. 11 is stored in the coupon data storage unit 26c (see Fig. 2) of the server 100, and the issuance URL of the coupon is transmitted to the store terminal 300.

[0109] The store terminal 300 distributes the URL to customers who have registered separately by email or the like. Such distribution may be performed by the server 100. In this case, an email address may be registered separately, or since OAuth authentication is performed, a message function in the service may be used. The users to be selected may be users who have visited the store, users who have visited a store in the same business, or the like, using existing coupon distribution marketing methods.

[0110] The operator of the user terminal 200 clicks on the received URL. This causes the user terminal 200 to launch a browser program and send a My Page screen request to the server 100 (step S163). The server 100 determines whether or not there is a screen request (step S165), and when there is a screen request, transmits HTML data for displaying the My Page screen (step S167). At that time, cookie information is also transmitted.

[0111] The user terminal 200 receives this HTML data and displays it (step S169). The My Page screen is the same as in the first embodiment.

[0112] The operator of the user terminal 200 selects a coupon display button (not shown) displayed on the My Page screen. The coupon display button may be the same as the acquired coupon display button shown in FIG. 8C.

[0113] When the coupon display button is selected, the user terminal 200 determines that the coupon display button has been selected (step S170), and makes a request to display a coupon including the UID and current location data stored as cookie data (step S172). The current location data is the same as in the first embodiment.

[0114] The server 100 performs user authentication based on the received UID, as in the first embodiment.

[0115] The server 100 judges whether the user authentication is successful (step S173), and if the user authentication is successful, judges whether the user terminal 200 is within the area of ​​the store of the coupon (step S177). If the user terminal 200 is within the area, the server 100 transmits the first display data and the second display data to the user terminal 200 (step S179).

[0116] FIG. 10A shows a display example when the first display data and the second display data are received.

[0117] On the other hand, if it is determined in step S177 that the user is not within the area, the first display data is transmitted to the user terminal 200 (step S180).

[0118] An example of the display when the first display data is received is shown in FIG. 10B.

[0119] In addition, in the figure, when coupon 167 is selected, a message saying "The special offer is a surprise when you visit the store" may be displayed.

[0120] If the user cannot be authenticated in step S173 of FIG. 12, CPU 123 of server 100 sends an error message to user terminal 200 (step S175).

[0121] User terminal 200 determines whether to receive coupon data or an error message (step S181), and if coupon data is received, CPU 123 uses the browser program to obtain the HTML data of the URL and display the coupon (step S185).

[0122] If an error message is received in step S181, the error message is displayed (step S183).

[0123] The coupon erasing process is the same as in the first embodiment, so a description thereof will be omitted.

[0124] In this embodiment, the coupon is displayed after the My Page screen is displayed, but clicking on the URL in the email in step S161 may proceed to a coupon display request in step S171.

[0125] Also, the coupon registered at the store terminal 300 may be displayed on the terminal of the user who has been OAuth authenticated without clicking on a URL. In this case, the operator of the user terminal 200 may register and store the coupon in the same manner as in step S14 or step S15 of FIG.

[0126] In this way, it is possible to issue a coupon in which the contents of the coupon (benefit details) are displayed or not depending on whether the user terminal 200 is within the area or outside the area. This makes the benefit details a fun surprise when customers visit the store, encouraging them to visit the store.

[0127] This embodiment can be understood as the following invention.

[0128] 2) A) A server having the following a1) to a5): a1) a store-issued ticket data storage means for storing store-issued ticket data including a store-issued ticket ID and issuing entity data; a2) a store data storage means for storing a store ID, area identification data, and a store-issued ticket data ID in association with each other; a3) a user data storage means for storing a user ID and an acquired store-issued ticket data ID; a4) a control means for referring to the user data storage means and identifying store-issued ticket data already acquired by a user identified by a user ID; a5) a distribution means for distributing the issue entity data of the specified store-issued ticket data; B) A user terminal having the following b1) to b4): b1) a location data acquisition means for acquiring current location data; b2) a transmission means for transmitting a user ID and the location data to the server; b3) a receiving means for receiving the issuing entity data from the server; b4) a notification means for notifying the issuing entity data; C) A store ticket management system comprising: D) the issuing entity data includes, for the user, first issuing entity data indicating the existence of the store-issued ticket and second issuing entity data indicating a benefit provided by the store-issued ticket; E) the control means of the server determines, based on the user ID and location data provided from the user terminal, among the acquired store-issued ticket data of the user, acquired store-issued ticket data whose location is within a range specified by the area specification data of the store that issued the acquired store-issued ticket and acquired store-issued ticket data whose location is outside that range, and sets the first issuing entity data as the issuing entity data for acquired store-issued ticket data that is outside the range, and sets the first issuing entity data and the second issuing entity data as the issuing entity data for acquired store-issued ticket data that is within the range; A store ticket issuing management system characterized by the above.

[0129] The system can also be understood as carrying out the following process when registering a coupon, rather than when the coupon is used.

[0130] 7) A) A server having the following a1) to a5): a1) a store-issued ticket data storage means for storing store-issued ticket data including a store-issued ticket ID and issuing entity data; a2) a store data storage means for storing a store ID, area identification data, and a store-issued ticket data ID in association with each other; a3) a user data storage means for storing a user ID and an acquired store-issued ticket data ID; a4) a control means for referring to the user data storage means and identifying store-issued ticket data already acquired by a user identified by a user ID; a5) a distribution means for distributing the issue entity data of the specified store-issued ticket data; B) A user terminal having the following b1) to b4): b1) a location data acquisition means for acquiring current location data; b2) a means for providing a user ID and the location data to the server; b3) a notification means for notifying the issuing entity data upon receiving the issuing entity data from the server; b4) an input means for a user to input a user setting display flag for hiding the acquired store-issued ticket data in the user terminal with respect to the notified issued entity data; b5) a user setting display flag transmission means for transmitting the input user setting display flag to the server; C) A store ticket management system comprising: D) the issuing entity data includes, for the user, first issuing entity data indicating the existence of the store-issued ticket and second issuing entity data indicating a benefit provided by the store-issued ticket; E) based on the user ID and location data provided from the user terminal, the control means determines, from the acquired store-issued ticket data of the user, acquired store-issued ticket data whose location is within a range specified by the area specification data of the store that issued the acquired store-issued ticket and acquired store-issued ticket data whose location is outside that range, and determines the first issuing entity data for acquired store-issued ticket data that is outside that range, and determines the first issuing entity data and the second issuing entity data for acquired store-issued ticket data that is within that range; A store ticket issuing management system characterized by the above.

[0131] 7. Other Embodiments (7.1 Bulk secret settings) In the first embodiment, the user can specify the secret flag on a coupon-by-coupon basis. In contrast, it may be possible to specify the secret flag on a store-by-store basis, so that the secret flag can be managed collectively. For example, a selection button for whether or not to set a secret flag on a store-by-store basis may be displayed, and when the button is selected, a secret flag may be added to the store-by-store basis as attribute data for the user. This allows all coupons for the store, both those already acquired and those to be acquired in the future, to be kept secret. Also, some stores may have multiple group stores. In this case, it may also be possible to set the secret flag on a group-by-group basis.

[0132] The same registration is also applicable when a store registers a coupon. That is, when a store registers a new coupon, the store may be allowed to set a secret flag for each store, shop, or group. The secret flag for each store or group can be switched on or off at the user's discretion.

[0133] (7.2 Regarding using a dedicated app instead of a browser program) When displaying a coupon acquired using a browser program on a user terminal, the coupon acquired by the user must be stored in server 100. However, a dedicated app for this system may be installed on the user terminal. In this case, data may be stored in server 100 in the same way, or the acquired coupon may be stored in the terminal. In this case, the display may be restricted by determining whether or not a secret flag is present.

[0134] (7.3 Application to other than store-issued ticket data) In this embodiment, the case of issuing store-issued ticket data has been described as an example, but it can also be applied to list display processing in SNS services. For example, even if a certain target person is registered as a friend, the person will not be displayed in the chat list with friends unless the person is within a certain area. As a result, if the user terminal is not in a specific location, the friend will not be displayed in the chat list.

[0135] This allows the friend to appear in the chat list only when the friend is in the specified location, so even if the SNS screen is displayed outside the specified location, family members and others will not know about the relationship with the friend.

[0136] In this case, the invention can be understood as follows.

[0137] 13) A) A server having the following a1) to a4): a1) a user data storage means for storing user data including a user ID; a2) a message exchange user storage means for storing a user ID of a user determined as a message exchange user; a3) a message storage means for storing messages exchanged between the message exchange user and the message exchange user; a4) a distribution means for, upon receiving a user ID, referring to the message exchange user storage means and the message storage means, identifying message exchange users of the user identified by the user ID, and distributing screen generation data for generating a message list display screen displaying a list of the message exchange users and a message display screen displaying message exchanges with the message exchange users; B) A user terminal having the following b1) to b3): b1) a position data acquisition means for acquiring a current position as current position data; b2) a transmission means for transmitting a user ID to the server; b3) a display means for displaying a message list display screen based on the screen generation data when the screen generation data is received from the server, and for displaying a message display screen with a specific user when the specific user is selected on the message list display screen; A user-to-user message exchange display system comprising: The user data storage means stores area identification data for identifying the location of the user, C) the user-to-user message exchange display system includes the following means: a user setting display flag storage means for storing a user setting display flag which is a flag for determining whether to display or not display the message exchange user on a message list display screen and which is set by the user of the user terminal; D) for a messaging user whose user setting display flag is in a hidden state, a limited display means for determining whether or not the current location of the user terminal that transmitted the user ID is within a range in which the registered user is displayed on the message list display screen, and if it is not within the range, displaying a message list display screen in which the messaging user is not displayed on the message list display screen; A system for displaying message exchanges between users.

[0138] The store-issued ticket data management system may also be applied to the display data control in a browser program. For example, in a browser program, a flag for bookmarks or history data that is not to be displayed may be stored in the browser program itself or in a server, and the bookmarks or history data may be displayed if the user terminal is in the specified location, and "404 NOT FIND" may be displayed if the user terminal is not in the specified location.

[0139] In this case, the invention can be understood as follows.

[0140] 14) A) A server having the following a1) to a5): a website data storage means for storing the URI of a website and the corresponding notification target data; a distribution means for distributing notification target data corresponding to a specified website URI to the user terminal based on a distribution request from the user terminal; B) A user terminal having the following b1) to b4): b1) a location data acquisition means for acquiring current location data; b2) a transmission means for requesting delivery of notification target data corresponding to a website URI together with the user ID and the location data; b3) a notification means for receiving the notification target data from the server and notifying the same; A web browsing system comprising: The following means are provided: C) a user-defined display flag storage means for storing a user-defined display flag, which is determined by a user as to whether the data to be notified is to be displayed or not displayed on the user terminal, in association with the store-issued ticket data ID; D) a limited display means for displaying the requested notification target data on the user terminal when the location of the requested notification target data is outside a specified range based on the user ID and location data provided from the user terminal; A web browsing system comprising:

[0141] In addition, the server may be configured to store, together with the notification data corresponding to the URL (URI), a dummy screen indicating that the notification data does not exist, and if the limited display means does not identify the notification data as a target for delivery to the user terminal, the dummy screen may be displayed.

[0142] The same can be applied to apps downloaded onto smartphones. For example, an app for receiving a certain service may not be displayed if the smartphone is not within a specified range.

[0143] By using such an app, it is possible to determine whether or not a secret flag is present and restrict the display of the coupon when it is displayed, and it is also possible to keep the fact that the dedicated app for this system has been installed hidden from family members and others.

[0144] (7.4 Regarding cases where some functions are provided on the server or user terminal) The user setting display flag storage means and the limited display means may have some functions in the server or the user terminal. For example, all the means may be provided in the user terminal. In this case, all data transmitted from the server is sent regardless of the location, and the list display is performed by filtering the data in the user terminal.

[0145] For example, the browser program itself may determine whether the user is within or outside the set area. In this way, the server can transmit data to be hidden from the user terminal 200, and the user terminal 200 can determine whether the data is hidden from the user terminal 200.

[0146] Also, the server may make the list display itself inapplicable to users outside the area.

[0147] (7.5 Other) In this embodiment, GNNS is used to detect the position of the user terminal, but beacons or the like may also be used.

[0148] The present invention can also be understood as a store-issued ticket management system 510 shown in FIG.

[0149] 6) A) A server 100 having the following a1) to a5): a1) store-issued ticket data storage means 3 for storing store-issued ticket data including a store-issued ticket ID and issuing entity data; a2) a store data storage means 6 for storing a store ID, area identification data, and a store-issued ticket data ID in association with each other; a3) a user data storage means 5 for storing a user ID and an acquired store-issued ticket data ID; a4) A control means 4 that refers to the user data storage means 5 and identifies the store-issued ticket data already acquired for the user identified by the user ID; a5) a distribution means 7 for distributing the issue entity data of the specified store-issued ticket data; B) A user terminal 520 having the following b1) to b4): b1) a location data acquisition means 512 for acquiring current location data; b2) a location data transmission means 515 for transmitting a user ID and the location data to the server; b3) a receiving means 513 for receiving the issuing entity data from the server; b4) a notification means 514 for notifying the issuing entity data; b5) an input means 518 for a user to input a user setting display flag for hiding the acquired store-issued ticket data in the user terminal with respect to the notified issued entity data; b6) a user setting display flag transmission means 511 for transmitting the input user setting display flag to the server; C) A store ticket management system comprising: D) The control means 4 of the server d1) when the user setting display flag is received, the user setting display flag is stored in the user data storage means 5; d2) for acquired store-issued ticket data for which the user setting display flag is in a hidden state, based on the user ID and location data provided from the user terminal, determining whether or not the location is within a range specified by area specification data of the store that issued the acquired store-issued ticket, and if the location is not within the range, not specifying the acquired store-issued ticket data as a target for distribution to the user terminal; A store ticket issuing management system characterized by the above.

[0150] In the above embodiment, the functions shown in Fig. 1 are realized by software using the CPU 23. However, part or all of the functions may be realized by hardware such as a logic circuit. Note that part of the processing of the program may be performed by an operating system (OS).

Claims

1. A) A server that has the following a1) to a5): a1) a store-issued ticket data storage means for storing store-issued ticket data including a store-issued ticket ID and issuing entity data; a2) a store data storage means for storing a store ID, area identification data, and a store-issued ticket data ID in association with each other; a3) a user data storage means for storing a user ID and an acquired store-issued ticket data ID; a4) a control means for referring to the user data storage means and identifying store-issued ticket data already acquired by a user identified by a user ID; a5) a distribution means for distributing the issue entity data of the specified store-issued ticket data; B) A user terminal having the following b1) to b4): b1) a location data acquisition means for acquiring current location data; b2) a transmission means for transmitting a user ID and the location data to the server; b3) a receiving means for receiving the issuing entity data from the server; b4) a notification means for notifying the issuing entity data; A store ticket issuing management system comprising: C) the user data storage means of the server stores a user-set display flag, which is determined by a user as to whether the acquired store-issued ticket data is to be displayed or hidden in the user terminal, in association with the store-issued ticket data ID; D) the control means of the server, based on the user ID and location data provided from the user terminal, determines not to specify the acquired store-issued ticket data of the user as a target for distribution to the user terminal if the location of the user is not within the range specified by the area specification data of the store that issued the acquired store-issued ticket; A store ticket issuing management system characterized by the above.

2. A) A server that has the following a1) to a5): a1) a store-issued ticket data storage means for storing store-issued ticket data including a store-issued ticket ID and issuing entity data; a2) a store data storage means for storing a store ID, area identification data, and a store-issued ticket data ID in association with each other; a3) a user data storage means for storing a user ID and an acquired store-issued ticket data ID; a4) a control means for referring to the user data storage means and identifying store-issued ticket data already acquired by a user identified by a user ID; a5) a distribution means for distributing the issue entity data of the specified store-issued ticket data; B) A user terminal having the following b1) to b4): b1) a location data acquisition means for acquiring current location data; b2) a transmission means for transmitting a user ID and the location data to the server; b3) a receiving means for receiving the issuing entity data from the server; b4) a notification means for notifying the issuing entity data; C) a store ticket issuing management system comprising: D) the issuing entity data includes, for the user, first issuing entity data indicating the existence of the store-issued ticket and second issuing entity data indicating a benefit provided by the store-issued ticket; E) the control means of the server determines, based on the user ID and location data provided from the user terminal, among the acquired store-issued ticket data of the user, acquired store-issued ticket data whose location is within a range specified by the area specification data of the store that issued the acquired store-issued ticket and acquired store-issued ticket data whose location is outside that range, and sets the first issuing entity data as the issuing entity data for acquired store-issued ticket data that is outside the range, and sets the first issuing entity data and the second issuing entity data as the issuing entity data for acquired store-issued ticket data that is within the range; A store ticket issuing management system characterized by the above.

3. In the store ticket issuing management system according to claim 1 or 2, The store-issued ticket data is a stamp card for the store; A store ticket issuing management system characterized by the above.

4. In the store ticket issuing management system according to claim 1 or 2, The store-issued ticket data indicates a coupon that can be used at the store; A store ticket issuing management system characterized by the above.

5. In the store ticket issuing management system according to claim 1 or 2, A group ID that enables a plurality of stores to be managed as the same group is set in the store data storage means, the control means of the server, when there is store-issued ticket data of another store in a group to which the store having the acquired store-issued ticket data to be distributed belongs, also identifies the store-issued ticket data of the other store as the acquired store-issued ticket data; A store ticket issuing management system characterized by the above.

6. A) A server that has the following a1) to a5): a1) a store-issued ticket data storage means for storing store-issued ticket data including a store-issued ticket ID and issuing entity data; a2) a store data storage means for storing a store ID, area identification data, and a store-issued ticket data ID in association with each other; a3) a user data storage means for storing a user ID and an acquired store-issued ticket data ID; a4) a control means for referring to the user data storage means and identifying store-issued ticket data already acquired by a user identified by a user ID; a5) a distribution means for distributing the issue entity data of the specified store-issued ticket data; B) A user terminal having the following b1) to b4): b1) a location data acquisition means for acquiring current location data; b2) a location data transmission means for transmitting a user ID and the location data to the server; b3) a receiving means for receiving the issuing entity data from the server; b4) a notification means for notifying the issuing entity data; b5) an input means for a user to input a user setting display flag for hiding the acquired store-issued ticket data in the user terminal with respect to the notified issued entity data; b6) a user setting display flag transmission means for transmitting the input user setting display flag to the server; C) a store ticket issuing management system comprising: D) The control means of the server d1) upon receiving the user setting display flag, storing the user setting display flag in the user data storage means; d2) for acquired store-issued ticket data for which the user setting display flag is in a hidden state, based on the user ID and location data provided from the user terminal, determining whether or not the location is within a range specified by area specification data of the store that issued the acquired store-issued ticket, and if the location is not within the range, not specifying the acquired store-issued ticket data as a target for distribution to the user terminal; A store ticket issuing management system characterized by the above.

7. A) A server that has the following a1) to a5): a1) a store-issued ticket data storage means for storing store-issued ticket data including a store-issued ticket ID and issuing entity data; a2) a store data storage means for storing a store ID, area identification data, and a store-issued ticket data ID in association with each other; a3) a user data storage means for storing a user ID and an acquired store-issued ticket data ID; a4) a control means for referring to the user data storage means and identifying store-issued ticket data already acquired by a user identified by a user ID; a5) a distribution means for distributing the issue entity data of the specified store-issued ticket data; B) A user terminal having the following b1) to b4): b1) a location data acquisition means for acquiring current location data; b2) a means for providing a user ID and the location data to the server; b3) a notification means for notifying the issuing entity data upon receiving the issuing entity data from the server; b4) an input means for a user to input a user setting display flag for hiding the acquired store-issued ticket data in the user terminal with respect to the notified issued entity data; b5) a user setting display flag transmission means for transmitting the input user setting display flag to the server; C) a store ticket issuing management system comprising: D) the issuing entity data includes, for the user, first issuing entity data indicating the existence of the store-issued ticket and second issuing entity data indicating a benefit provided by the store-issued ticket; E) based on the user ID and location data provided from the user terminal, the control means determines, from the acquired store-issued ticket data of the user, acquired store-issued ticket data whose location is within a range specified by the area specification data of the store that issued the acquired store-issued ticket and acquired store-issued ticket data whose location is outside that range, and determines the first issuing entity data for acquired store-issued ticket data that is outside that range, and determines the first issuing entity data and the second issuing entity data for acquired store-issued ticket data that is within that range; A store ticket issuing management system characterized by the above.

8. a store-issued ticket data storage means for storing store-issued ticket data including a store-issued ticket ID and issuing entity data; a store data storage means for storing a store ID, area identification data, and an issued store-issued ticket data ID in association with each other; A user data storage means for storing a user ID and an acquired store-issued ticket data ID; A control means for referring to the user data storage means and identifying store-issued ticket data already acquired by a user identified by a user ID; a distribution means for distributing the issue entity data of the specified store-issued ticket data; Equipped with the user data storage means stores a user-set display flag, which is determined by a user as to whether the acquired store-issued ticket data is to be displayed or hidden in the user terminal, in association with the store-issued ticket data ID; the control means, based on the user ID and location data provided from the user terminal, when the location of the user's acquired store-issued ticket data is not within a range specified by area specification data of the store that issued the acquired store-issued ticket, does not specify the acquired store-issued ticket data as a target for distribution to the user terminal; A store issued ticket management server comprising:

9. a store-issued ticket data storage means for storing store-issued ticket data including a store-issued ticket ID and issuing entity data; a store data storage means for storing a store ID, area identification data, and an issued store-issued ticket data ID in association with each other; A user data storage means for storing a user ID and an acquired store-issued ticket data ID; A control means for referring to the user data storage means and identifying store-issued ticket data already acquired by a user identified by a user ID; a distribution means for distributing the issue entity data of the specified store-issued ticket data; Equipped with The issuing entity data includes, for the user, first issuing entity data indicating the existence of the store-issued ticket, and second issuing entity data indicating a benefit provided by the store-issued ticket, the control means determines, based on the user ID and location data provided from the user terminal, from the acquired store-issued ticket data of the user, within-range acquired store-issued ticket data whose location is within a range specified by area specification data of the store that issued the acquired store-issued ticket, and outside-range acquired store-issued ticket data whose location is outside the range, and sets the first issuing entity data as the issuing entity data for the outside-range acquired store-issued ticket data, and sets the first issuing entity data and the second issuing entity data as the issuing entity data for the within-range acquired store-issued ticket data; A store issued ticket management server comprising:

10. a store-issued ticket data storage means for storing store-issued ticket data including a store-issued ticket ID and issuing entity data; a store data storage means for storing a store ID, area identification data, and an issued store-issued ticket data ID in association with each other; A user data storage means for storing a user ID and an acquired store-issued ticket data ID; A control means for referring to the user data storage means and identifying store-issued ticket data already acquired by a user identified by a user ID; a distribution means for distributing the issue entity data of the specified store-issued ticket data; Equipped with The control means 1) When a user setting display flag for hiding acquired store-issued ticket data for a specific store is received from the user terminal, the user setting display flag is stored in the user data storage means as the user setting display flag for the store of the user, 2) for acquired store-issued ticket data for which the user setting display flag is in a hidden state based on the user ID and location data provided from the user terminal, determine based on the location data whether or not the location is within a range specified by the area specification data of the store that issued the acquired store-issued ticket, and if the location is not within the range, do not specify the acquired store-issued ticket data as a target for distribution to the user terminal; A store issued ticket management server comprising:

11. a store-issued ticket data storage means for storing store-issued ticket data including a store-issued ticket ID and issuing entity data; a store data storage means for storing a store ID, area identification data, and an issued store-issued ticket data ID in association with each other; A user data storage means for storing a user ID and an acquired store-issued ticket data ID; A control means for referring to the user data storage means and identifying store-issued ticket data already acquired by a user identified by a user ID; a distribution means for distributing the issue entity data of the specified store-issued ticket data; Equipped with The issuing entity data includes, for the user, first issuing entity data indicating the existence of the store-issued ticket, and second issuing entity data indicating a benefit provided by the store-issued ticket, the control means, based on the user ID and location data provided from the user terminal, determines, from among the acquired store-issued ticket data of the user, acquired store-issued ticket data whose location is within a range specified by area specification data of the store that issued the acquired store-issued ticket and acquired store-issued ticket data whose location is outside that range, and determines, for acquired store-issued ticket data that is outside that range, as the first issuing entity data, and for acquired store-issued ticket data that is within that range, as the first issuing entity data and the second issuing entity data; A store issued ticket management server comprising:

12. A) A server that has the following a1) to a5): a1) a store-issued ticket data storage means for storing store-issued ticket data including a store-issued ticket ID and issuing entity data; a2) a store data storage means for storing a store ID, area identification data, and a store-issued ticket data ID in association with each other; a3) a user data storage means for storing a user ID and an acquired store-issued ticket data ID; a4) a control means for referring to the user data storage means and identifying store-issued ticket data already acquired by a user identified by a user ID; a5) a distribution means for distributing the issue entity data of the specified store-issued ticket data; B) A user terminal having the following b1) to b4): b1) a location data acquisition means for acquiring current location data; b2) a transmission means for transmitting a user ID to the server; b3) a receiving means for receiving the issuing entity data from the server; b4) a notification means for notifying the issuing entity data; A store ticket issuing management system comprising: C) The following measures are in place: a user-set display flag storage means for storing a user-set display flag, determined by a user as to whether the acquired store-issued ticket data is to be displayed or hidden in the user terminal, in association with the store-issued ticket data ID; a non-notification decision means for, when receiving store-issued ticket data from the server, not causing the notification means to notify the received acquired store-issued ticket data of the user if the location of the acquired store-issued ticket data of the user is outside the range specified by the area specification data of the store that issued the acquired store-issued ticket, based on the location data of the user terminal and the area specification data stored in the store data storage means; A store ticket issuing management system characterized by the above.

13. A) A server that has the following a1) to a4): a1) a user data storage means for storing user data including a user ID; a2) a message exchange user storage means for storing a user ID of a user determined as a message exchange user; a3) a message storage means for storing messages exchanged between the message exchange user and the message exchange user; a4) a distribution means for, upon receiving a user ID, referring to the message exchange user storage means and the message storage means, identifying message exchange users of the user identified by the user ID, and distributing screen generation data for generating a message list display screen displaying a list of the message exchange users and a message display screen displaying message exchanges with the message exchange users; B) A user terminal having the following b1) to b3): b1) a position data acquisition means for acquiring a current position as current position data; b2) a transmission means for transmitting a user ID to the server; b3) a display means for displaying a message list display screen based on the screen generation data when the screen generation data is received from the server, and for displaying a message display screen with a specific user when the specific user is selected on the message list display screen; A user-to-user message exchange display system comprising: The user data storage means stores area identification data for identifying the location of the user, C) the user-to-user message exchange display system includes the following means: a user setting display flag storage means for storing a user setting display flag which is a flag for determining whether to display or not display the message exchange user on a message list display screen and which is set by the user of the user terminal; D) for a messaging user whose user setting display flag is in a hidden state, a limited display means for determining whether or not the current location of the user terminal that transmitted the user ID is within a range in which the registered user is displayed on the message list display screen, and if not within the range, displaying a message list display screen in which the messaging user is not displayed on the message list display screen; A system for displaying message exchanges between users.

14. A) A server that has the following a1) to a5): a website data storage means for storing the URI of a website and the corresponding notification target data; a distribution means for distributing notification target data corresponding to a URI of a specified website to a user terminal based on a distribution request from the user terminal; B) A user terminal having the following b1) to b4): b1) a location data acquisition means for acquiring current location data; b2) a transmission means for requesting delivery of notification target data corresponding to a URI of a website together with a user ID and the location data; b3) a notification means for receiving the notification target data from the server and notifying the same; A web browsing system comprising: The following means are provided: C) a user-defined display flag storage means for storing a user-defined display flag, which is determined by a user as to whether the data to be notified is to be displayed or not displayed on the user terminal, in association with the store-issued ticket data ID; D) a limited display means for displaying the requested notification target data on the user terminal when the location of the requested notification target data is outside a specified range based on the user ID and location data provided from the user terminal; A web browsing system comprising:

15. 15. The web browsing system of claim 14, the server stores, together with the notification target data corresponding to the URI, a dummy screen indicating that the notification target data does not exist; the limited display means displays the dummy screen when the notification target data is not specified as a target for delivery to the user terminal; A web browsing system comprising:

Images