Information processing system, information processing method, and program

Abstract

To provide an information processing device for improving the convenience of a data recording medium that can be read by using a user terminal device.SOLUTION: A server 1 that is an information processing device is provided with: a redirection destination holding unit 31 for recording a first URL in a data recording medium 7 installed at a sales base to be readable by a reader provided in a user terminal 9b of a customer and holding the combination of a second URL and the first URL in the server device 1; a redirect setting unit 32 for specifying the second URL based on information notified from a sales base terminal 9a used by a staff member at the sales base and holding the combination of the second URL and the first URL in the redirection destination holding unit 31; and a redirect unit 33 for causing, when receiving access from the user terminal 9b that has read the first URL from the data recording medium 7, the user terminal 9b to access the second URL held in combination with the first URL by the redirection destination holding unit 31.SELECTED DRAWING: Figure 2

Description

Technical Field

[0001] The present disclosure relates to short-range wireless communication technology.

Background Art

[0002] Conventionally, a technology has been proposed (see Non-Patent Document 1) and put into practical use, in which a user calls a service by touching a terminal device to an RFID tag.

Prior Art Documents

Non-Patent Documents

[0003]

Non-Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] Conventionally, an integrated circuit (hereinafter, "RF tag") as a data recording medium in which data for being read by a reader using a short-range wireless communication technology such as NFC (Near Field Communication) (Radio Frequency IDentification; hereinafter, "RFID") has been recorded has been used. Further, an optically readable code such as a two-dimensional barcode is used as a data recording medium in which data for being read using an optical reader (for example, a camera or the like) provided in an information processing apparatus has been recorded. Then, an action (for example, a URL of an access destination) is recorded in the RF tag, the two-dimensional barcode, or the like, and the user terminal (so-called smartphone or the like) having an RFID reader function or an optical reader function is caused to read the action and execute the action, so that the user terminal is brought close to (touched) the RF tag, or a technique for causing the user terminal to execute a predetermined function only by imaging the two-dimensional barcode with the user terminal has been variously proposed.

[0005] However, when causing the user terminal having a reader for the RF tag to be brought close (touched) or executing a function by an action of only imaging the two-dimensional barcode with the user terminal, since the function to be executed by the user terminal is one function for one data recording medium, when it is desired to selectively execute a plurality of functions on the user terminal, it has been necessary to prepare a plurality of data recording media in which different actions are set.

[0006] In view of the above-described problems, an object of the present disclosure is to improve the convenience of a data recording medium readable using a user terminal device.

Means for Solving the Problem

[0007] An example of the present disclosure is an information processing system including a data recording medium installed at a sales base and a server device. The data recording medium is a data recording medium on which a first URL is recorded so as to be readable by a reader included in a user terminal of a customer who visits the sales base. The server device includes a redirect destination holding means for holding a combination of a second URL that is returned to the user terminal of the access source when access to the first URL is received and the first URL, and receives information that can specify the second URL to be combined with the first URL, which is notified from a sales base terminal used by a staff member of the sales base. A redirect setting means for causing the redirect destination holding means to hold a combination of the second URL specified based on the notification and the first URL, and when receiving access to the first URL from the user terminal of the customer who has read the first URL from the data recording medium, the redirect means for causing the user terminal to access the second URL by returning the second URL held in combination with the first URL by the redirect destination holding means to the user terminal.

[0008] In addition, an example of the present disclosure is an information processing system including a data recording medium installed at a sales base and a server device. The data recording medium is a data recording medium in which a second URL is recorded so as to be readable by a reader included in a user terminal of a customer who visited the sales base. The second URL includes address information of an external SNS, information capable of specifying the address information of the server device by the external SNS, and a parameter capable of specifying a target to which the customer wishes to receive a notification. The server device includes an association means for performing notification registration by recording, in a notification registration management table, notification registration data in which the customer ID of the customer is associated with the identification information of the target to which the customer wishes to receive information. The association means specifies the identification information of the target to which the customer wishes to receive information based on a third URL including the address information of the server device and a parameter capable of specifying the target to which the customer wishes to receive a notification, which is notified to the user terminal from the external SNS that has received an access to the second URL, and records, in the notification registration management table, notification registration data in which the customer ID of the customer is associated with the identification information of the target to which the customer wishes to receive information.

[0009] The present disclosure can be understood as an information processing apparatus, a system, a method executed by a computer, or a program to be executed by a computer. Further, the present disclosure can also be understood as a recording medium in which such a program is recorded and can be read by a computer or other devices, machines, etc. Here, a recording medium readable by a computer or the like refers to a recording medium that accumulates information such as data and programs by an electrical, magnetic, optical, mechanical, or chemical action and can be read by a computer or the like.

Advantages of the Invention

[0010] According to the present disclosure, it is possible to improve the convenience of a data recording medium readable by using a user terminal device.

Brief Description of the Drawings

[0011]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Mode for Carrying Out the Invention

[0012] Hereinafter, embodiments of an information processing system, method, and program according to the present disclosure will be described with reference to the drawings. However, the embodiments described below are merely illustrative of the embodiments, and do not limit the information processing system, method, and program according to the present disclosure to the specific configurations described below. In implementation, specific configurations according to the implementation mode may be appropriately adopted, and various improvements and modifications may be made.

[0013] In the present embodiment, an embodiment will be described in the case where the information processing system, method, and program according to the present disclosure are implemented in a system that provides a notification registration service to customers via RF tags installed at sales bases. However, the information processing system, method, and program according to the present disclosure can be widely used for data recording media that can be read by a short-range wireless communication reader, and the application target of the present disclosure is not limited to the examples shown in the embodiments.

[0014] When the sales base is a physical store, even if a customer visits the physical store, there may be cases where the desired product is out of stock or the customer wants to postpone the purchase decision because they are hesitant to make a purchase. Conventionally, in such cases, the customer contacts the store staff, the store staff obtains the customer's contact information to contact the customer when the target product arrives at the sales base, and the staff contacts the customer by phone, email, etc. when the product arrives. However, such a response is cumbersome, leading to the store missing sales opportunities for products. Also, when a customer visits a physical store, it is also possible for the customer to search for an online store, search for a product in the online store to display the product details page, search for a store on the product details page, and operate the notification request button to perform notification registration. However, in this case as well, although the burden on the customer and store staff is reduced compared to the past, it requires many operations from the customer.

[0015] Therefore, in an example of the information processing system according to the present disclosure, the customer-side user terminal 9b is caused to access the distribution management server 1 according to the search result of the target product and / or the target sales base at the store-side user terminal 9a, and a notification request for the target product and / or the target sales base is registered.

[0016] <Configuration of the System> FIG. 1 is a schematic diagram showing the configuration of the system according to the present embodiment. The system according to the present embodiment includes a distribution management server 1 that can communicate with each other by being connected to a network, a store-side user terminal 9a that is a sales base terminal used by a staff member of the sales base, and a data recording medium 7 (in this embodiment, an RF tag) installed at the sales base. Further, it is connected to an external social networking service (hereinafter referred to as "external SNS") 8, a store server, and a customer-side user terminal 9b via the network.

[0017] The distribution management server 1 is an information processing device including a CPU (Central Processing Unit) 11, a ROM (Read Only Memory) 12, a RAM (Random Access Memory) 13, a storage device 14 such as an EEPROM (Electrically Erasable and Programmable Read Only Memory) or an HDD (Hard Disk Drive), a communication unit 15 such as a NIC (Network Interface Card), and the like. However, regarding the specific hardware configuration of the distribution management server 1, appropriate omission, replacement, or addition can be made according to the implementation mode. Further, the distribution management server 1 is not limited to a device composed of a single housing. The distribution management server 1 may be realized by a plurality of devices using so-called cloud or distributed computing technologies.

[0018] The store-side user terminal 9a is a computer used by the staff at the sales base (the staff of the operator who operates the sales base and is located at the sales base such as a physical store), and the customer-side user terminal 9b is a computer used by the customers of the store. Both the user terminals 9a and 9b are computers equipped with a CPU, ROM, RAM, storage device, communication unit, input device, output device, etc. (illustrations are omitted), and may be, for example, a so-called smartphone, tablet, personal computer, etc. However, regarding the specific hardware configuration of the user terminals 9a and 9b, appropriate omissions, replacements, and additions are possible according to the implementation mode. Also, the user terminals 9a and 9b are not limited to devices consisting of a single housing. The user terminals 9a and 9b may be realized by a plurality of devices using technologies such as so-called cloud or distributed computing.

[0019] The user uses the distribution management server 1 via these user terminals 9a and 9b. However, it is also possible for the user to use the information processing system according to the present disclosure as a store-side user and at the same time use the information processing system according to the present disclosure as a customer-side user from one user terminal.

[0020] The data recording medium 7 is a data recording medium on which a first URL is recorded so as to be readable by a near-field wireless communication (RFID) reader provided in the customer-side user terminal 9b of a customer who visits the sales base (physical store). Here, the first URL is a unique URL for the sales base to be installed, and may be, for example, a URL including a sales base ID as a parameter in addition to the address information for accessing the server. In the present embodiment, a URL including address information for accessing the distribution management server 1 and a parameter indicating the sales base ID is used as the first URL.

[0021] An example of the first URL is shown below. For example, when the sales base ID of the Shinjuku store is "51" and the sales base ID of the Shibuya store is "52", the first URL set in the data recording medium 7 (RF tag 7) installed in each store may be set as follows. Here, "type" is a parameter indicating the registration target (product, sales base, staff, brand, etc.), and "type = 1" indicates that the registration target is a sales base. The first URL set in the RF tag 7 of the Shinjuku store: https: / / <address of distribution management server 1>?type=1&shopId=51 The first URL set in the RF tag 7 of the Shibuya store: https: / / <address of distribution management server 1>?type=1&shopId=52

[0022] However, the first URL only needs to be a unique URL for the installed sales base, and its format is not limited. Note that the data recording medium 7 only needs to be installable in the sales base, and the possible external forms are not limited. In this embodiment, an example in which a so-called RF tag is used as the data recording medium 7 will be described. The specific installation mode of the RF tag 7 in the sales base is not limited. For example, installation modes such as being installed at the cash register of the sales base, being installed in the showcase, or being carried by the staff may be adopted.

[0023] The store server is a server for EC services provided by an external information processing system including a CPU, ROM, RAM, storage device, communication unit, etc. (not shown). The store server receives a request for the Web page of the store server sent from the customer-side user terminal 9b that executes applications such as an Internet browser or an e-commerce application, and then sends the requested Web page to the customer-side user terminal 9b and sells the ordered products to the customer. The store server is connected to an inventory database (not shown) for managing the inventory of products.

[0024] When the store server receives a request for a Web page of an online store sent from a customer-side user terminal 9b that executes an application capable of viewing the online store, such as an Internet browser or an e-commerce application, the store server sends the requested Web page to the customer-side user terminal 9b. At this time, among the contents of the Web page sent to the customer-side user terminal 9b, for contents such as product names, product images (videos / still images), product prices, color variations (if any), product details (product descriptions), and buttons for adding to the shopping cart, data generated / managed by the store server is used, and for the generation and management of these contents, the same technology as in the prior art may be used. Here, in the present embodiment, in the Web page, a display according to the inventory status for each sales base of the target product is performed.

[0025] The external SNS 8 is an external information processing system including a CPU, a ROM, a RAM, a storage device, a communication unit, etc. (not shown), and provides a social networking service that enables online communication between users. In the present embodiment, the external SNS 8 is an external system provided by a service provider different from the service provider that manages or operates the distribution management server 1, and is restricted from acquiring resources related to the user without obtaining the user's authorization.

[0026] FIG. 2 is a diagram showing an outline of the functional configuration of the system according to the present embodiment. In the distribution management server 1, the program recorded in the storage device 14 is read into the RAM 13 and executed by the CPU 11, and each hardware provided in the distribution management server 1 is controlled, so that the product database 21, the redirect destination holding unit 31, the redirect setting unit 32, the redirect unit 33, the search unit 34, the access instruction unit 61, the related information storage unit 62, the SNS user ID acquisition unit 63, the target ID specifying unit 64, the association unit 65, the notification information acquisition unit 66, the distribution destination determination unit 67, the distribution request unit 68, the search ID specifying unit 22, and the registration number acquisition unit 23 function as an information processing device. In the present embodiment and other embodiments described later, each function provided in the distribution management server 1 is executed by the CPU 11 which is a general-purpose processor, but a part or all of these functions may be executed by one or a plurality of dedicated processors.

[0027] The product database 21 is a database in which product data of products handled by stores is accumulated. In the present embodiment, the product data is generated by the distribution management server 1 performing data crawling on the store server and collecting the obtained data for each product. By acquiring product data through data crawling, it becomes possible to introduce the system according to the present embodiment without imposing a development burden such as incorporating a mechanism for delivering product feeds into an existing store server. However, the method for generating product data is not limited to the method of performing crawling exemplified in the present embodiment. The product data may be obtained by a method of referring to the database of the store server, a method of importing a table (such as a table in CSV format) extracted from the database of the store server, a method of acquiring a product feed from the store server, or the like.

[0028] The redirect destination holding unit 31 holds a combination of a second URL to be returned to the access source user terminal when receiving an access to the first URL and the first URL. As described above, the first URL is a URL unique to the sales base to be installed. That is, the redirect destination holding unit 31 acquires the first URL unique to the sales base at the sales base and holds, in combination with the first URL, the second URL as the redirect destination to be returned to the user terminal that has accessed the first URL.

[0029] The redirect setting unit 32 receives information that can identify the second URL to be combined with the first URL, which is notified from the store-side user terminal 9a used by the staff of the sales base, and causes the redirect destination holding unit 31 to hold a combination of the second URL specified based on the notification and the first URL.

[0030] When receiving an access to the first URL from the customer-side user terminal 9b that has read the first URL from the data recording medium 7 (RF tag in this embodiment), the redirect unit 33 returns, as the redirect destination, the second URL held in combination with the first URL by the redirect destination holding unit 31 to the user terminal, thereby causing the user terminal to access the second URL.

[0031] Here, the second URL includes, as parameters, information (in this embodiment, product ID and sales base ID) that can identify the target for which the customer wishes to receive a notification among matters related to the sales base (in this embodiment, the products handled at the sales base). Note that, in this embodiment, the matters related to the sales base are described by taking the products handled at the sales base as an example, but the specific content of the matters related to the sales base is not limited to the examples given in this embodiment. For example, the matters related to the sales base may be products, stores, staff, brands, manufacturers, hashtags, regions, genders, or other items for which the customer wishes to receive a notification. When the matters related to the sales base are staff, the second URL can include, for example, the staff ID as information that can identify the target for which the customer wishes to receive a notification. Also, in this embodiment, the second URL includes, as parameters, the ID of the target (in this embodiment, product ID and sales base ID) for identifying the target for which the customer wishes to receive a notification, but the second URL only needs to be something that can identify the target for which the customer wishes to receive a notification, and it only needs to be a unique URL for the target.

[0032] The search unit 34 searches a database (in this embodiment, the product database) that manages matters related to the sales base (in this embodiment, the products handled at the sales base) according to the conditions specified from the store-side user terminal 9a, thereby finding matters related to the sales base that match or approximate the conditions, and notifies the store-side user terminal 9a of the search results. The store-side user terminal 9a that has received the notification of the search results notifies the server device of the information that can identify the second URL by designating, from the search results, the target for which the customer wishes to receive a notification.

[0033] When the access instruction unit 61 receives an instruction to start an authorization process for authorizing access to a resource related to a customer held in the external SNS 8 from the customer's user terminal (customer-side user terminal 9b), it causes the customer-side user terminal 9b to access a cooperation library (API) for the authorization process provided by the external SNS 8. In the present embodiment, OAuth is adopted as the protocol used for authorizing access to the resource, and the start instruction received here is an OAuth start instruction. However, the protocol used for authorizing access to the resource is not limited to OAuth. Also, in the present embodiment, the API for the authorization process, in addition to the authorization process, permits message delivery in the external SNS 8 from an organization (in the present embodiment, the operator to which the staff belongs or the management entity of the distribution management server 1) to the customer (for example, registers as a so-called "friend"), and is an API that also executes a delivery permission process (friend addition).

[0034] In the present embodiment, the start instruction and the accompanying API access are the start instruction and access transmitted from the customer-side user terminal 9b in response to the execution of an access process to a third URL notified from the server of the external SNS 8 in the customer-side user terminal 9b.

[0035] The related information storage unit 62 stores the information related to the target transmitted from the customer-side user terminal 9b together with the start instruction, in association with information (for example, session information and / or Cookie) that can identify the customer-side user terminal 9b.

[0036] When authorization is obtained, the SNS user ID acquisition unit 63 acquires the SNS user ID of the customer in the external SNS 8 from the external SNS 8 via the cooperation library operating on the customer-side user terminal 9b.

[0037] Upon the acquisition of the customer's SNS user ID by the SNS user ID acquisition unit 63, the target ID identification unit 64 identifies the product ID and the sales base ID of the notification registration target associated with the start instruction based on the information stored (received together with the start instruction) by the related information storage unit 62. The product ID and the sales base ID identified here are the ID of the product of the business operator that the customer wishes to receive information about and the ID of the sales base (physical store, etc.).

[0038] The association unit 65 performs notification registration by recording the notification registration data in which the customer ID (in this embodiment, the SNS user ID of the customer on the external SNS) of the customer is associated with the identification information of the target for which the customer wishes to receive information in the notification registration management table. More specifically, in this embodiment, the association unit 65 associates the SNS user ID of the customer on the external SNS 8 acquired by the SNS user ID acquisition unit 63 with the product ID and the sales base ID of the notification registration target that is the target for which the customer wishes to receive information and is identified by the target ID identification unit 64. In this embodiment, an example in which the SNS user ID of the customer on the external SNS is used as the customer ID is described, but the customer ID may be any information that can identify the customer and is not limited to the SNS user ID. For example, as the customer ID, the user ID assigned in the company's own system may be used.

[0039] The notification information acquisition unit 66 acquires notification information including the product ID and the sales base ID related to the notification information updated after the previous acquisition of the notification information (for example, inventory information) by the notification information acquisition unit 66 on the website of the organization related to the notification registration target (in this embodiment, the store server of the business operator to which the staff belongs).

[0040] The delivery destination determination unit 67 searches for the customer ID (in this embodiment, the SNS user ID of the customer) associated with the identification information of the target (in this embodiment, the product ID and the sales base ID included in the notification information), and determines the retrieved customer ID (SNS user ID) as the delivery destination.

[0041] The distribution request unit 68 sends a distribution request for a message to the message transmission system (in this embodiment, the external SNS 8), where the SNS user ID of the organization is the source and the SNS user ID of the customer determined by the destination determination unit 67 is the destination, and the message notifies the customer of the information related to the target (in this embodiment, the notification information registered for notification related to the product ID and the sales base ID has been updated).

[0042] The search ID specifying unit 22 specifies at least one of the product ID and the sales base ID based on a search key that can specify at least one of the product and the sales base specified by the staff of the sales base.

[0043] The registration number acquisition unit 23 searches the notification registration management table based on the product ID and / or the sales base ID specified by the search ID specifying unit 22 to acquire the number of notification registrations in which at least one of the product and the sales base is narrowed down.

[0044] <Flow of processing> Next, the flow of processing executed in the system according to this embodiment will be described. Note that the specific content and processing order of the processing described below are examples for implementing the present disclosure. The specific processing content and processing order may be appropriately selected according to the embodiment of the present disclosure.

[0045] FIG. 3 is a flowchart showing an outline of the flow of the redirection setting process according to the present embodiment. The process shown in this flowchart is executed on the store-side user terminal 9a when an operation for requesting a store-side product search screen is performed by a staff member at the sales base. By the process shown in this flowchart, the staff member at the sales base can set products and sales bases registered by a touch operation on the RF tag in response to the request of the customer who visited the sales base during customer service. The staff member can perform an operation to request a store-side product search screen from a dedicated application executed on the store-side user terminal 9a or a management screen displayed on a browser. Note that, in the present embodiment, an example of searching for and setting products and sales bases is described, but the registration targets that can be searched for and set in the redirection setting process are not limited to the examples in the present embodiment. In the redirection setting process, for example, various registration targets such as staff members and brands can be searched for and redirection can be set.

[0046] From step S101 to step S106, a combination of a sales base and products based on a search key specified by a staff member at the sales base is retrieved. The store-side user terminal 9a requests a store-side product search screen from the distribution management server 1 in response to an operation by a staff member at the sales base (step S101), and the accessed distribution management server 1 distributes a store-side product search screen to the store-side user terminal 9a in response to the request (step S102). The store-side user terminal 9a displays the store-side product search screen and accepts input or selection of a search key from a staff member at the sales base (step S103), and transmits the received search key to the distribution management server 1 in response to an operation by a staff member at the sales base (in this embodiment, an operation of a "narrow down" button described later) (step S104).

[0047] Upon receiving the search key, the search unit 34 of the distribution management server 1 searches the product database 21 based on a search key that can identify at least one of the product and the sales location specified by the staff at the sales location, and finds combinations of candidate sales locations and products that can be sold at the sales locations (step S105). Then, the search unit 34 of the distribution management server 1 transmits the search results to the store-side user terminal 9a (step S106). Thereafter, the process proceeds to step S107.

[0048] FIG. 4 is a diagram showing an example of a store-side product search screen in the present embodiment. The store-side product search screen is a screen that can be displayed when the store-side user terminal 9a accesses the distribution management server 1, and is a screen that allows a staff member to search for the target of a notification request using at least one of a sales location (store), product number, SKU code, and product name as a search key by operating it. In the example shown in FIG. 4, the staff member accesses the distribution management server 1, inputs the above-described search key on the store-side user terminal 9a that has displayed the store-side product search screen, and operates the "Narrow down" button to cause the distribution management server 1 to execute a search, and the search results obtained from the distribution management server 1 can be displayed on the store-side user terminal 9a.

[0049] Here, the sales location (store) input field of the search key may have the sales location (store) automatically input in advance without any operation by the staff. The automatically input sales location is identified by the distribution management server 1 based on the staff ID or sales location ID of the staff logged in to the store-side user terminal 9a, or the location information of the store-side user terminal 9a, and may be automatically input in advance on the search page distributed in step S102, or may be automatically input by the store-side user terminal 9a.

[0050] In steps S107 and S108, a redirection setting request is sent. The store-side user terminal 9a receives the search results sent from the distribution management server 1 in step S106 and displays the search results to the user. In this embodiment, an example in which the search results are displayed on the store-side product search screen (see FIG. 4) is described, but the search results may be displayed on a screen different from the store-side product search screen. A "tag setting" button is displayed in the search results together with the product information. When the store-side user terminal 9a receives an operation of the "tag setting" button by the staff (step S107), it sends a redirection setting request to the distribution management server 1 (step S108). Thereafter, the process proceeds to step S109.

[0051] In steps S109 and S110, redirection settings are made. The redirection setting unit 32 of the distribution management server 1 that has received the redirection setting request issues a second URL for the combination of the sales base and the product related to the redirection setting request (step S109). In this embodiment, the second URL specifies an address for accessing a front-end framework platform that provides an SNS user ID providing service or the like as an access destination by an external SNS 8 (hereinafter referred to as the "address of the external SNS cooperation service"). Further, information that can identify the target for which the customer desires notification (in this embodiment, the product ID and the sales base ID of the corresponding product and the sales base) and the business operator identification information for the external SNS to identify the address of the distribution management server are URLs specified by parameters and the like.

[0052] Here, the business operator identification information is business operator identification information for the external SNS cooperation service issued by the external SNS 8. The external SNS 8 can identify the address information of the distribution management server 1 to be specified by the third URL by referring to this identification information. Therefore, in this embodiment, the redirection setting unit 32 identifies the product ID and the sales base ID based on the product information and the sales base information related to the search results specified in the redirection setting request.

[0053] Then, the redirection setting unit 32 issues a second URL using the specified product ID and / or sales base ID. When the second URL is issued, the redirection setting unit 32 causes the redirection destination holding unit 31 to save the combination of the issued second URL and the first URL, thereby setting the second URL as the redirection destination URL when the first URL is accessed (step S110). Thereafter, the processing shown in this flowchart ends.

[0054] An example of the second URL is shown below. As described above, the second URL includes the operator identification information, and the external SNS acquires the address of the distribution management server based on this information. For example, when a staff member at the Shibuya store with a sales base ID of "52" sets the redirection destination for the product ID "12034", the second URL may be set as follows. Here, "type = 3" indicates that the registration target is a combination of a sales base and a product. https: / / <address of external SNS> / <operator identification information>?type=3&shopId=52&skuId=12034

[0055] FIGS. 5 to 8 are sequence diagrams showing an overview of the flow of the notification registration process according to the present embodiment. The processing shown in the sequence diagram is executed after the redirection setting process is executed according to the operation of the staff member at the sales base, triggered by an operation (for example, a touch operation) in which a customer user brings the RFID reader of the customer-side user terminal 9b close to the RF tag 7 installed in the store, and is processed in order toward FIGS. 5 to 8.

[0056] In steps S201 and S202, access is made to the first URL read from the RF tag 7. When the customer user brings the RFID reader of the customer-side user terminal 9b close to the RF tag 7 installed in the store, the customer-side user terminal 9b reads the first URL from the RF tag 7 installed in the store using the RFID reader (step S201). The customer-side user terminal 9b starts an application (general-purpose browser or dedicated application) for processing the read first URL and accesses the read first URL (step S202).

[0057] From step S203 to step S205, the access to the first URL is redirected to the second URL. The received delivery management server 1 refers to the accessed URL (step S203). If the accessed URL is not an access to the first URL (NO in step S203), the processing shown in this flowchart ends. On the other hand, if the accessed URL is an access to the first URL (YES in step S203), the redirect section 33 of the delivery management server 1 reads out the second URL corresponding to the first URL preset in step S110 of the redirect setting process (step S204) and notifies the customer-side user terminal 9b of the second URL as the redirect destination (step S205). At this point, since the sales base ID can be specified based on the first URL, the sales base ID may be specified based on the first URL at this stage. Then, the process proceeds to step S301.

[0058] In steps S301 and S302, the access to the second URL is redirected to the third URL. The customer-side user terminal 9b accesses the second URL notified in step S205 (step S301). In this embodiment, as described above, the address of the external SNS cooperation service is set in the second URL. When the server of the external SNS 8 receives the access, it refers to the accessed URL. If the accessed URL is not the access to the second URL, it separately executes the process corresponding to the accessed URL. On the other hand, when the accessed URL is the access to the second URL, the server of the external SNS 8 identifies the address of the distribution management server 1 based on the business operator identification information included in the second URL, and creates a third URL by setting the parameters set in the second URL as they are in the address of the distribution management server 1. Then, the server of the external SNS 8 notifies the customer-side user terminal 9b of the third URL as the redirect destination, and the customer-side user terminal 9b accesses the notified third URL (step S302). After that, the process proceeds to step S303.

[0059] An example of the third URL is shown below. The third URL shown below corresponds to the second URL generated when the staff of the Shibuya store with the above-mentioned sales base ID "52" sets the redirect destination for the product ID "12034". Similar to the second URL, "type = 3" indicates that the registration target is a combination of a sales base and a product. Third URL corresponding to Shibuya store (sales base ID: 52) and product ID: 12034: https: / / <address of distribution management server 1>?type=3&shopId=52&skuId=12034

[0060] In step S303, the product ID and the sales base ID are acquired and saved based on the parameters. The distribution management server 1 receives an access from the customer-side user terminal 9b that has executed an access process to the third URL notified from the server of the external SNS 8. At this time, the customer-side user terminal 9b notifies the distribution management server 1 of information capable of specifying the corresponding product and information capable of specifying the sales base. In the system according to the present embodiment, the product ID is notified as information capable of specifying the product, and the sales base ID is notified as information capable of specifying the sales base. That is, the third URL includes the product ID and the sales base ID as parameters, and when an access is made from the customer-side user terminal 9b to the distribution management server 1, the product ID and the sales base ID are notified to the distribution management server 1. Here, as the product ID, for example, an SKU (Stock Keeping Unit, the minimum unit of a product type treated as the same product in inventory management) code may be used. The related information storage unit 62 saves the product ID and the sales base ID in association with information capable of specifying the customer-side user terminal 9b (for example, session information and / or Cookie). Then, the process proceeds to step S304.

[0061] In steps S304 and S305, the cooperation application is launched on the customer-side user terminal 9b. The access instruction unit 61 transmits an activation instruction for the cooperation application operating on the customer-side user terminal 9b to the customer-side user terminal 9b (step S304). The cooperation application operates on the customer-side user terminal 9b and is an application for using an API provided by a cooperation library provided by the external SNS 8. The customer-side user terminal 9b that has received the activation instruction for the cooperation application launches the cooperation application (step S305). Then, the process proceeds to step S306.

[0062] From step S306 to step S308, a login process to the external SNS 8 is performed. The cooperation application operating on the customer-side user terminal 9b sends a login request to the authorization server of the external SNS 8 including authentication information such as the customer's SNS user ID and password to the external SNS 8 via the cooperation library (steps S306 and S307), and logs in to the external SNS 8 (step S308). Here, the authentication information may be, for example, a user ID such as an email address and a password. However, the authentication information is not limited to the ID and password, and for example, other authentication information such as biometric authentication, one-time password, and electronic certificate may be used, or a combination of multiple authentication means may be used. In addition, if the authentication information is already stored in the customer-side user terminal 9b for reasons such as the second or subsequent external SNS login process, the input of the authentication information by the user is omitted, and the customer-side user terminal 9b sends the authentication information to the external SNS 8 and logs in to the external SNS 8.

[0063] When the customer-side user terminal 9b successfully logs in to the external SNS 8, the cooperation library sends an authorization request including the operator's SNS user ID to the authorization server of the external SNS 8.

[0064] When the authorization server of the external SNS 8 that has received the authorization request is in a state where the customer-side user terminal 9b has logged in to the external SNS 8, it sends a URL for confirming the delegation of authority to display a confirmation screen for the delegation of authority on the customer-side user terminal 9b, and asks the customer whether the external SNS 8 can provide information about the customer (in this embodiment, the customer's SNS user ID, etc.) held by the external SNS 8 to the distribution management server 1. When the customer performs an operation (for example, pressing an approval button) indicating consent to the delegation of authority on the customer-side user terminal 9b, the cooperation library notifies the authorization server of the external SNS 8 that the customer has consented to the delegation of authority, and the authorization server that has received the notification sends an authorization response to the cooperation library.

[0065] Here, when the authorization server of the external SNS8 has not received permission from the target merchant to send messages on the SNS8 from the target merchant to the target customer at the time of receiving the notice of consent to delegation of authority (for example, the state of being registered as a so-called "friend". Hereinafter, it will be described as "friend").), the external SNS8, before sending the authorization response, sends a URL for registering the merchant as a friend to the cooperation library, causing the customer-side user terminal 9b to display a friend addition screen, and asking the customer whether they can register the target merchant as a friend. At this time, the external SNS8 determines whether the target merchant and the customer have already been registered as friends based on the SNS user ID of the merchant received in the authorization request and the SNS user ID of the customer identified during SNS login. When the customer performs an operation indicating consent to add a friend on the customer-side user terminal 9b (for example, pressing the consent button), the cooperation library notifies the external SNS8 that the customer has consented to add a friend. The external SNS8 that has received the notice sets the state to allow message sending on the SNS8 from the target merchant to the target customer (in this embodiment, registering as a "friend").

[0066] Note that the above-described delegation of authority process and friend addition process (the processes surrounded by the dashed line in the figure) can be omitted after the second time. When these processes are omitted, other processes are automatically performed without the user's operation or additional input by the user, so that the customer user can complete the registration of the notification request by simply touching the customer-side user terminal 9b to the RF tag. Also, in the example described above, an embodiment in which a confirmation screen and a friend addition screen are displayed on the customer-side user terminal 9b for each of the delegation of authority process and the friend addition process has been described. However, the confirmation screen and the friend addition screen for the delegation of authority process and the friend addition process may be displayed together on one screen. In this case, the process from the authorization request to the consent transmission for the delegation of authority and the process from the display of the friend addition screen to the consent transmission for adding a friend are executed in parallel.

[0067] When an authorization response is received, the cooperation library sends a token request for the customer's SNS user ID to the authorization server of the external SNS8 (step S309). The authorization server that has received the token request confirms that the source of the token request is the source to which the customer (the SNS user who has an account on the SNS8) has consented to delegation of authority, issues an access token that permits access to the resources held by the SNS8 for the target SNS user, and sends a token response including the issued access token to the cooperation library.

[0068] The authorization server issues an access token that permits access to the resources held by the SNS8 for the target SNS user. The cooperation library receives the access token issued by the SNS8 (step S310) and notifies the customer-side user terminal 9b of the success of login and access token acquisition. Thereafter, the process proceeds to step S311.

[0069] From step S311 to step S313, resources for the customer are acquired. When an access token that permits access to the resources for the customer is acquired, the customer-side user terminal 9b requests the cooperation library to acquire a resource (here, the SNS user ID of the target customer) (step S311). The cooperation library that has received the request sends a resource access including the access token to the resource server of the external SNS8 (step S312). The resource server confirms that the source of the resource access (the cooperation library) has received delegation of authority from the user by referring to the received access token, and provides the resource (here, the SNS user ID of the target customer) to the source of the resource access. The cooperation library receives the SNS user ID of the target customer from the resource server of the external SNS8 and notifies this to the customer-side user terminal 9b (step S313). Thereafter, the process proceeds to step S314.

[0070] In steps S314 and S315, the customer's SNS user ID is notified to the distribution management server 1. The customer-side user terminal 9b that has acquired the customer's SNS user ID notifies the customer's SNS user ID to the distribution management server 1. At this time, the session (connection) established for the communication from step S302 to step S304 is used for the communication from the customer-side user terminal 9b to the distribution management server 1. In this way, the SNS user ID acquisition unit 63 of the distribution management server 1 receives the SNS user ID of the target customer from the customer-side user terminal 9b (step S315). Then, the process proceeds to step S316.

[0071] In step S316, the product ID and the sales base ID for notification registration are specified, and the customer's SNS user ID is associated with the product ID and the sales base ID. The target ID specifying unit 64 specifies the product ID and the sales base ID for notification registration associated with the access in step S303 based on the information stored by the related information storage unit 62. Then, the associating unit 65 creates notification registration data by associating the received customer's SNS user ID with the combination of the product ID and the sales base ID, and registers the created notification registration data in the notification registration management table (step S316). Here, the target ID specifying unit 64 specifies the product ID and the sales base ID related to the registration request from the customer-side user terminal 9b, that is, the product ID and the sales base ID to be associated with the customer's SNS user ID, based on the session information and / or Cookie held in step S303. More specifically, the target ID specifying unit 64 uses the session information and / or Cookie related to the customer-side user terminal 9b that is the access source in step S314 to search for the association data stored by the related information storage unit 62 in step S303, thereby specifying the product ID and the sales base ID to be associated with the customer's SNS user ID.

[0072] At this time, a notification registration ID for identifying the notification registration data may be issued and recorded in the notification registration management table together with the SNS user ID, product ID, and sales base ID. In this embodiment, an example using a table for notification registration management will be described, but the management format of data associating the SNS user ID, product ID, and sales base ID for notification registration management is not limited to a table. When the association between the customer's SNS user ID, product ID, and sales base ID is completed, the process proceeds to step S317.

[0073] In steps S317 and S318, a registration completion page display for notifying the completion of registration is performed. When the notification registration (association between the customer's SNS user ID, product ID, and sales base ID) is completed, the distribution management server 1 transmits a registration completion page for notifying the completion of registration to the customer-side user terminal 9b (step S317). The customer-side user terminal 9b that has received the registration completion page displays the registration completion page and notifies the customer that the notification registration of the product has been completed (step S318). Thereafter, the process shown in this sequence diagram ends.

[0074] That is, in this embodiment, the customer-side user terminal 9b touches the RF tag 7 installed at the sales base, accesses the first URL read from the RF tag 7, receives a redirect to the second URL, accesses the second URL, and makes a notification registration request. By adopting the above-described embodiment, the procedure that the customer performs to make a notification request is only to touch the store-installed RF tag 7 using the customer-side user terminal 9b, which is greatly simplified. Also, the work by the staff at the sales base can omit obtaining the customer's contact information, contacting the customer when there is a receipt, price reduction, etc., and efficiency can be improved.

[0075] FIG. 9 is a diagram showing the configuration of a registration completion page for notifying that the notification registration of a product has been completed in the present embodiment. On the registration completion page, a message "Registration has been completed. A notice of arrival will be distributed." is displayed. Also, on the registration completion page, information on the product for which notification registration has been performed, that is, product image (video / still image), product number, brand name, product name, color, size, product price, product details (description of the product), business type name, and sales base (store) name, etc. may be displayed. Further, a button for "canceling notification registration" and a "close" button (not shown in the figure) may be displayed. The parentheses in the figure indicate that the information of the attribute described in the parentheses is displayed in the part within the parentheses. These data can be acquired from the product database 21 by the distribution management server 1 and arranged on the registration completion page.

[0076] Also, on the registration completion page, in addition to the information on the product, a link to the staff page of the staff who recommends the product, a search tag for searching for the product, the inventory status of the product, the content of the posted data posted by the staff regarding the product, comments by the staff, an additional button to the shopping cart, etc. may be further posted.

[0077] FIG. 10 is a flowchart showing an outline of the message distribution process according to the present embodiment. The process shown in this flowchart is executed periodically (for example, once a day at a preset time) at a preset frequency. However, the execution timing of the process shown in this flowchart is not limited to the examples in the present disclosure. The process shown in this flowchart may be executed, for example, triggered by receiving an instruction for message distribution by an administrator.

[0078] Based on the reflection process of the inspection work results of incoming products by the staff at the sales base, and update operations using the store-side user terminal 9a, etc., when the notification information for each sales base of the products on the operator site is updated, the display regarding the products on the operator site changes. The content of the changed display is, for example, the display of "In Stock", "Low Stock", "Out of Stock", etc. on the product page, product price (price reduction / price increase), product image, product description, etc. The distribution management server 1 obtains the updated notification information for each sales base by using methods such as directly referring to the inventory database that the operator refers to and updating the product database 21, obtaining the notification information for each sales base by receiving the inventory data from the operator's inventory database and updating the product database 21, or referring to and updating the product database 21 by crawling or scraping the operator site, etc. At this time, the data provided from the operator to the distribution management server 1 is the sales base list, product information, inventory information of each sales base, etc., and these data may be provided in, for example, CSV format. Also, the distribution management server 1 stores the notification information for each sales base obtained from the operator site in the product database 21. That is, the distribution management server 1 stores the notification information for each sales base and each product in the product database 21, associated with the combination of the product ID and the sales base ID.

[0079] In step S501, an update of the notification information is confirmed. The notification information acquisition unit 66 transmits a request for inquiring about the presence or absence of updated notification information to the product database 21 (step S501). Here, the request may include the product ID and the sales base ID of the inquiry target. The product database 21 that has received the request identifies the notification information updated after the previously received request (for example, the inventory has been restored) based on the update time of the notification information or the response history to the request, and transmits a response notifying the latest notification information related to the product (here, SKU) for which the notification information has been updated to the notification information acquisition unit 66. Note that when the request includes the product ID and the sales base ID of the inquiry target here, the product database 21 identifies only the notification information related to the target product ID and sales base ID, and transmits a response notifying the identified notification information to the notification information acquisition unit 66. Further, the response may include the product ID and the sales base ID related to the notification information and the URL of the page (for example, the product detail page) where the target product can be viewed. Thereafter, the process proceeds to step S502.

[0080] In steps S502 and S503, the notification information is acquired and the delivery destination is determined. The notification information acquisition unit 66 receives the response transmitted by the product database 21 and stores the notification information included in the response (step S502). The delivery destination determination unit 67 that has received the response searches the notification registration management table using the product ID and the sales base ID included in the target notification information as keys, searches for the SNS user ID of the customer associated with the combination of the product ID and the sales base ID (that is, the SNS user ID of the customer who has registered for the product notification), and determines the retrieved SNS user ID as the delivery destination (step S503). Thereafter, the process proceeds to step S504.

[0081] In step S504, a message delivery is requested. The delivery request section 68 transmits a delivery request for a notification based on the notification information to the external SNS 8 (step S504). Here, the delivery request to the external SNS 8 is made through an API for mass message delivery provided by the external SNS 8, and the delivery request includes the delivery source, the delivery destination, and the delivery content. The business operator's SNS user ID is specified as the delivery source, the customer's SNS user ID determined in step S503 is specified as the delivery destination, and the delivery content is specified to notify that the information related to the sales base and the product registered for notification by the customer has been updated (for example, the product registered for notification has been received at the specified sales base or the price of the product registered for notification has been reduced at the specified sales base). That is, the delivery request section 68 makes a delivery request to the external SNS 8, specifying only the customers who have registered for notification of the target sales base and product among the customers (users who are permitted to send messages on the SNS) registered as friends of the business operator on the SNS 8.

[0082] In this embodiment, a mode is described in which the process of first acquiring the products to be delivered and then determining the delivery destinations corresponding to the acquired products is adopted. However, the order of determining the delivery targets and the delivery destinations is not limited to the examples in the present disclosure. For example, first, the SNS user ID of the customer as the delivery destination may be determined, and then, the notification information related to one or more targets (here, products) registered for notification for the SNS user ID may be acquired, and delivery may be performed on a user-by-user basis. By doing so, for example, when product A and C are price-reduced or restocked while user A has registered for notification of products A, B, and C, it is possible to send a notification saying "Products A and C have been price-reduced / restocked" in one delivery.

[0083] FIG. 11 is a diagram showing the content of a message sent to a customer when a product notified and registered by the customer arrives. In this embodiment, as a message notifying that a product notified and registered by the customer has arrived, a standard message "We would like to inform you that the product you have been waiting for has arrived at the store" is used. However, the notification content is not limited to the exemplified standard message. For example, the message may be created in the distribution management server 1 by a method of fitting the product name etc. into a standard sentence, or a method of having it generated by AI. Further, the notification message may include the name of the business operator, the name of the sales base (for example, a physical store) where the product has arrived, the product name, the product image (video / still image), the brand name, the product price, the color variation (if any), the size, the product details (description of the product), and the access means to the product order. Here, the access means to the product order is, for example, a link for making a phone call from the customer-side user terminal 9b to the sales base, the URL of the product details page, or a link for putting the product into the cart, etc.

[0084] The external SNS 8 that has received the distribution request performs message distribution according to the distribution request. Specifically, the external SNS 8 transmits a message including the SNS user ID of the business operator as the sender and the distribution content specified in the distribution request as the content, to the SNS user ID of the customer specified in the distribution request as the destination. By doing so, the business operator can automatically distribute information indicating that the information related to the sales base and the product has been updated only to the customers who have notified and registered the target product from the SNS account of the store.

[0085] By executing the above-described processing, according to the information processing system disclosed in the present embodiment, a user can notify and register a product for which the user desires information notification, and can also receive information notification of the notified and registered product. By doing so, compared to the method of contacting a staff member at a conventional store to request a notification, receiving the notification, visiting the store, and contacting the staff member again, a customer can easily and conveniently register a notification request and check the product at the store without contacting the staff member after receiving the notification. Further, according to the information processing system disclosed in the present embodiment, the update of the notification information that triggers the notification is obtained by using a method of updating the product database 21 by directly referring to the inventory database referred to by the business operator, a method of obtaining the notification information for each sales base by receiving the inventory data from the business operator's inventory database and updating the product database 21, or a method of referring to and updating the product database 21 by crawling or scraping the business operator's website, etc. Therefore, it is possible to introduce a system that notifies a customer of a message regarding the product inventory status without linking the system for message delivery with the product master / inventory quantity / store list, etc.

[0086] FIG. 12 is a diagram showing a list of notification registrations in the present embodiment. As described above, in the present embodiment, the association unit 65 records notification registration data in which a specified SNS user ID is associated with a received product ID and a sales base ID in a notification registration management table (step S409). Therefore, according to the system according to the present embodiment, the store-side user can access the notification registration management table via the store-side user terminal 9a and obtain and refer to the number of notification registrations for each sales base and / or for each product. Specifically, the search ID specifying unit 22 specifies at least one of the product ID and the sales base ID based on a search key that can specify at least one of the product and the sales base designated by the staff of the sales base, and the registration number acquisition unit 23 searches the notification registration management table based on the product ID and / or the sales base ID specified by the search ID specifying unit 22, thereby obtaining the number of notification registrations in which at least one of the product and the sales base is narrowed down. FIG. 12 shows an example of a file in which the number of notification registrations for each product (SKU) obtained from the notification registration management table by narrowing down the date range and the sales base (physical store) is recorded. Although FIG. 12 illustrates a list of notification registrations, a list of the number of deliveries (the number of times notifications were actually delivered to the SNS user ID of the customer after the notification registration) narrowed down using at least one of the product ID and the sales base ID may be obtainable. Regarding the list of the number of deliveries, similar to the list of notification registrations, at least one of the product ID and the sales base ID is specified based on a search key that can specify at least one of the product and the sales base designated by the staff of the sales base, and the notification registration management table is searched based on the product ID and / or the sales base ID specified by the search ID specifying unit 22, thereby obtaining a list of the number of deliveries in which at least one of the product and the sales base is narrowed down.

[0087] <Other variations> In the above-described embodiment, an example was described in which an RF tag is used as the data recording medium and a short-range wireless communication reader is used as the reader provided in the customer's user terminal. However, the types of the data recording medium and the reader provided in the customer's user terminal are not limited to the above-described examples. For example, an optically readable code such as a two-dimensional barcode (any optically readable code is acceptable, not limited to barcodes) may be used as the data recording medium, and an optical reader such as a camera may be used as the reader provided in the customer's user terminal.

[0088] Further, in the above-described embodiment, the first URL to be redirected by the distribution management server 1 is set in the data recording medium. However, the redirection by the distribution management server 1 may be omitted, and a URL specifying the address of the external SNS may be directly set in the data recording medium. In this case, for example, if the following URL is set in the data recording medium, the customer user can register the sales base as the notification target. URL set for the RF tag 7 of the Shinjuku store: https: / / <Address of external SNS> / <Business operator identification information>?type=1&shopId=51 URL set for the RF tag 7 of the Shibuya store: https: / / <Address of external SNS> / <Business operator identification information>?type=1&shopId=52

[0089] When the said variation is adopted, since the said URL corresponds to the second URL in the above-described embodiment, the redirection setting process shown in FIG. 3 is omitted. Also, since the address acquired by the customer-side user terminal in step S201 of FIG. 5 in the notification registration process is the address of the external SNS, the processes from step S202 to step S205 in the notification registration process are omitted. The processes described with reference to FIGS. 6 to 8 are substantially the same except that the registration target is only the sales base ID instead of the combination of the product ID and the sales base ID.

[0090] Also, in the above-described embodiments, an example in which the process of obtaining an access token and acquiring a user's resources is processed by causing the customer-side user terminal 9b to execute a script (program) for executing these processes has been described. However, the process of obtaining an access token and acquiring a user's resources may be executed by other devices. For example, the process of obtaining an access token and acquiring a user's resources may be processed by causing the distribution management server 1 to execute a program for executing these processes.

[0091] Also, in the above-described embodiments, an example in which an external SNS is used as a message transmission system for transmitting a message has been described. However, the message transmission system that can be adopted for message transmission is not limited to the above-described example. For example, as the message transmission system, an e-mail, a short message system, or a push notification by an application installed in the user terminal may be adopted.

[0092] In the above-described embodiments and variations, the information of products at the sales bases has been described as an example of the target for which customers desire information notifications. However, the target of the notifications is not limited to the examples described above. For example, the types of organizations and online stores may be apparel, real estate sales, used car sales, home appliances, food, furniture, education, job offers, media, construction, fortune-telling, musical instruments, etc. And the targets of the notifications may be, for example, products, stores, staff, brands, manufacturers, hashtags, regions, genders, and other items that customers desire to be notified about. More specifically, when the business type is apparel, it may be product categories, brands, manufacturers, stores, people, staff, prices, colors, materials, genders, heights, discount rates, sizes, rankings, new products, used products, etc. When the business type is real estate sales, it may be regions, floor plans, rent ranges, housing types (apartment or detached house, new construction or used), train lines, stations, prefectures, etc. When the business type is used car sales, it may be model years, engine displacements, mileage, car types, presence or absence of vehicle inspections, drive types (4WD or 2WD), vehicle types (coupe, SUV, etc.), etc. When the business type is home appliances, it may be the size of the room, capacity (such as for refrigerators), etc. When the business type is food, it may be product brands, etc. When the business type is furniture, it may be room types (living room, bedroom, etc.), etc. When the business type is education, it may be courses, grades, desired schools, qualifications, etc. When the business type is job offers, it may be annual incomes, employment forms, company names, etc. When the business type is media, it may be events, article genres, etc. When the business type is construction, it may be areas of expertise, etc. When the business type is fortune-telling, it may be constellations, birth months, nine-star astrology, Chinese zodiac signs, 27 constellations, etc. When the business type is musical instruments, it may be playing methods, music genres, etc. In this case, the second URL and the third URL only need to be unique for the notification target, and the notification registration can be performed by associating the customer ID with the notification target ID.

[0093] As described above, according to the technology related to the present disclosure, it is possible to perform notification registration for various targets. At this time, the staff at the sales base or the staff of the business operator may select the category of the notification target and make the target searchable for that category.

[0094] FIG. 13 is a diagram showing an example of a category selection screen in the present embodiment. The category selection screen is a screen that can be displayed by the store-side user terminal 9a accessing the distribution management server 1. By operating the staff, the target sales base of the notification request can be narrowed down using the sales base (store) key, and the target of the notification request can be selected using the category (distribution category) of the notification request as a key. In the example shown in FIG. 13, the staff selects the distribution category on the store-side user terminal 9a that has accessed the distribution management server 1 to display the category selection screen, thereby executing the narrowing down of the distribution category and displaying a search screen suitable for the distribution category on the store-side user terminal 9a. For example, when "product" is selected as the distribution category here, the store-side product search screen described with reference to FIG. 4 is displayed as the search screen, and the sales base (store) and products can be searched.

Explanation of reference numerals

[0095] 1 Server (information processing device) 9a Store-side user terminal 9b Customer-side user terminal

Claims

1. An information processing system comprising a data recording medium installed at a sales base and a server device, wherein the data recording medium is a data recording medium in which a first URL is recorded so as to be readable by a reader provided in a user terminal of a customer who visited the sales base, and the server device is, a redirect destination holding means for holding a combination of a second URL to be returned to the user terminal of the access source when access to the first URL is received and the first URL; a redirect setting means for receiving information capable of specifying a second URL to be combined with the first URL notified from a sales base terminal used by a staff member of the sales base, and causing the redirect destination holding means to hold a combination of the second URL specified based on the notification and the first URL; a redirect means for, when receiving access to the first URL from the user terminal of the customer who has read the first URL from the data recording medium, returning the second URL held in combination with the first URL by the redirect destination holding means to the user terminal, thereby causing the user terminal to access the second URL, an information processing system.

2. The second URL includes, as a parameter, information capable of specifying a target for which the customer wishes to receive notification among matters related to the sales base, The information processing system according to claim 1.

3. further comprising a sales base terminal used by a staff member of the sales base, and the server device is, a search means for searching a database for managing matters related to the sales base according to conditions specified from the sales base terminal, thereby retrieving matters related to the sales base that match or approximate the conditions, and notifying the sales base terminal of the retrieval result; The sales base terminal notifies information capable of specifying the second URL by designating a target for which the customer wishes to receive notification from the retrieval result notified from the server device and notifying the server device, The information processing system according to claim 2.

4. The server device is, an association means for performing notification registration by recording notification registration data associating the customer ID of the customer and the identification information of the target for which the customer wishes to receive information notification in a notification registration management table, Delivery destination determination means for retrieving the customer ID associated with the identification information of the target and determining the retrieved customer ID as the delivery destination; Delivery request means for sending a delivery request to the message transmission system for a message in which the customer ID determined by the delivery destination determination means is specified as the delivery destination and which notifies the customer of information related to the target; The information processing system according to claim 2, further comprising:

5. The customer ID is the SNS user ID of the customer in an external SNS, The delivery destination determination means retrieves the SNS user ID of the customer associated with the identification information and determines the retrieved SNS user ID as the delivery destination, The delivery request means sends a delivery request to the external SNS for a message in which the SNS user ID of the customer determined by the delivery destination determination means is specified as the delivery destination and which notifies the customer of information related to the target; The information processing system according to claim 4.

6. The second URL includes the address information of the external SNS, information that enables the external SNS to identify the address information of the server device, and a parameter that enables identification of the target that the customer wishes to be notified of, Based on a third URL including the address information of the server device and the parameter that enables identification of the target that the customer wishes to be notified of, which is notified to the user terminal from the external SNS that has received an access to the second URL, the association means identifies the identification information of the target that the customer wishes to be notified of and records, in a notification registration management table, notification registration data in which the customer ID of the customer is associated with the identification information of the target that the customer wishes to be notified of; The information processing system according to claim 5.

7. An information processing system comprising a data recording medium installed at a sales base and a server device, The data recording medium is a data recording medium in which a second URL is recorded so as to be readable by a reader provided in a user terminal of a customer who has visited the sales base, The second URL includes the address information of an external SNS, information that enables the external SNS to identify the address information of the server device, and a parameter that enables identification of the target that the customer wishes to be notified of, The server device is A linking means for performing notification registration is provided by recording notification registration data in which the customer ID of the customer and the identification information of the target for which the customer wishes to receive information are linked, in a notification registration management table. The linking means specifies the identification information of the target for which the customer wishes to receive information based on a third URL including the address information of the server device and a parameter capable of specifying the target for which the customer wishes to receive information, which is notified to the user terminal from the external SNS that has received access to the second URL, and records, in the notification registration management table, notification registration data in which the customer ID of the customer and the identification information of the target for which the customer wishes to receive information are linked. An information processing system.

8. Delivery destination determination means for retrieving the customer ID linked to the identification information of the target and determining the retrieved customer ID as the delivery destination, Delivery request means for transmitting, to a message transmission system, a delivery request for a message in which the customer ID determined by the delivery destination determination means is specified as the delivery destination and which notifies the customer of information related to the target. The information processing system according to claim 7.

9. The second URL includes, as the parameter, at least one of a product ID of a product and a sales base ID of the sales base. The information processing system according to claim 2.

10. The second URL includes, as the parameter, a staff ID of a staff member of the sales base. The information processing system according to claim 2.

11. The data recording medium is a data recording medium in which a first URL is recorded so as to be readable by a near-field wireless communication reader provided in a user terminal of a customer who has visited the sales base. The information processing system according to any one of claims 1 to 10.

12. The data recording medium is a data recording medium in which a first URL is recorded so as to be readable by an optical reader provided in a user terminal of a customer who has visited the sales base. The information processing system according to any one of claims 1 to 10.

13. A computer of an information processing system including a data recording medium installed at a sales base and in which a first URL is recorded so as to be readable by a reader provided in a user terminal of a customer who has visited the sales base, and a server device. A redirect destination holding step of holding a combination of a second URL to be returned to the user terminal of the access source when accessing the first URL, and the first URL; A redirect setting step of receiving information capable of specifying a second URL to be combined with the first URL notified from a sales point terminal used by a staff member of the sales point, and causing the redirect destination holding step to hold a combination of the second URL specified based on the notification and the first URL; A redirect step of, when receiving an access to the first URL from the user terminal of the customer who has read the first URL from the data recording medium, returning the second URL held in combination with the first URL by the redirect destination holding step to the user terminal, thereby causing the user terminal to access the second URL, comprising: An information processing method for executing.

14. A data recording medium installed at a sales point and having a second URL recorded thereon that is readable by a reader provided in a user terminal of a customer who has visited the sales point, the second URL including address information of an external SNS, information capable of specifying the address information of the server device by the external SNS, and a parameter capable of specifying a target to which the customer wishes to receive a notification, and a server device, a computer of an information processing system comprising: Performing an association step of registering a notification by recording notification registration data associating the customer ID of the customer and identification information of a target for which the customer wishes to receive information notification in a notification registration management table; In the association step, based on a third URL including the address information of the server device and a parameter capable of specifying a target for which the customer wishes to receive information notification, notified from the external SNS that has received an access to the second URL to the user terminal, identifying the identification information of the target for which the customer wishes to receive information notification, and recording, in the notification registration management table, notification registration data associating the customer ID of the customer and the identification information of the target for which the customer wishes to receive information notification; An information processing method.

15. A data recording medium installed at a sales point and having a first URL recorded thereon that is readable by a reader provided in a user terminal of a customer who has visited the sales point, and a server device, a computer of an information processing system comprising: A redirect destination holding means for holding a combination of a second URL to be returned to the user terminal of the access source when accessing the first URL and the first URL; A redirect setting means for receiving information capable of specifying a second URL to be combined with the first URL notified from a sales point terminal used by a staff member of the sales point, and causing the redirect destination holding means to hold a combination of the second URL specified based on the notification and the first URL; A redirect means for, when receiving an access to the first URL from the user terminal of the customer who has read the first URL from the data recording medium, returning the second URL held in combination with the first URL by the redirect destination holding means to the user terminal, thereby causing the user terminal to access the second URL. A program for causing it to function.

16. A computer of an information processing system including a data recording medium in which a second URL including address information of an external SNS that can be read by a reader provided in a user terminal of a customer who has visited the sales point installed at the sales point, information capable of specifying the address information of the server device by the external SNS, and a parameter capable of specifying a target to which the customer wishes to receive a notification is recorded, and a server device; Functioning as an association means for performing notification registration by recording notification registration data associating the customer ID of the customer and the identification information of the target for which the customer wishes to receive information notification in a notification registration management table; Based on a third URL including the address information of the server device and a parameter capable of specifying a target for which the customer wishes to receive information notification, which is notified to the user terminal from the external SNS that has received an access to the second URL, the association means specifies the identification information of the target for which the customer wishes to receive information notification, and records the notification registration data associating the customer ID of the customer and the identification information of the target for which the customer wishes to receive information notification in the notification registration management table. Program.

Images