Information processing system, method, and program

Abstract

To prevent a service from being used at a place other than an installation place of a tag.SOLUTION: An acquisition unit 21 that acquires, as an authentication code, a code acquired by an information processing terminal accessing a tag that transmits a different code each time the tag is accessed through short-range wireless communication, or a decrypted code obtained by performing decryption processing on the code in a case where the code is an encrypted code, and a code determination unit 23 that determines whether or not the authentication code acquired by the acquisition unit 21 is a code that has been acquired by the acquisition unit 21 in the past; And an execution unit 26 that executes processing for arranging a taxi vehicle when it is determined that the acquired authentication code is not a code that has been acquired before.SELECTED DRAWING: Figure 2

Description

[Technical Field]

[0001] The present disclosure relates to techniques for providing services. [Background technology]

[0002] Conventionally, an action control system has been proposed in which a tag installed at a location where a user is expected to be when the action to be controlled is executed sends an encrypted code obtained by performing encryption processing on a verification code whose value changes with each access in response to access from a mobile device via short-range wireless communication, the mobile device transmits the encrypted code obtained from the tag to a verification server, and the verification server and a device control server operating in conjunction with it perform decryption processing on the encrypted code received from the mobile device, and as a result, if the decryption processing is successful and the verification code obtained in this decryption processing is different from the verification codes obtained in the previous decryption processing, the system instructs the execution of the action corresponding to the tag (see Patent Document 1). [Prior art documents] [Patent documents]

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

[0004] Conventionally, there are known systems that allow users to receive services by holding a mobile device over a tag capable of short-range wireless communication, such as an NFC (Near Field Communication) tag. However, there is a problem in that the information read from the tag by holding the mobile device over the tag (such as the tag's unique ID) is stored, allowing unauthorized use of the service in places other than where the tag is installed.

[0005] In view of the above-mentioned problems, an object of the present disclosure is to prevent a service from being used in a location other than the location where the tag is installed. [Means for solving the problem]

[0006] An example of the present disclosure is an information processing system including: an acquisition means for acquiring, as an authentication code, a code acquired by an information processing terminal accessing a tag that transmits a different code each time it is accessed via short-range wireless communication, or a decrypted code obtained by performing a decryption process on the code if the code is an encrypted code; a code determination means for determining whether the authentication code acquired by the acquisition means is a code that has been acquired by the acquisition means before; and an execution means for executing a process to arrange for a taxi vehicle when it is determined that the acquired authentication code is not a code that has been acquired before.

[0007] Another example of the present disclosure is an information processing system including: a tag position storage means for storing position information regarding an installation location of a tag that transmits a different code each time it is accessed via near-field wireless communication; an acquisition means for acquiring, as an authentication code, the code acquired by an information processing terminal accessing the tag, or a decrypted code obtained by performing a decryption process on the code if the code is an encrypted code, and acquiring position information of the information processing terminal; a code determination means for determining whether the authentication code acquired by the acquisition means is a code that has been previously acquired by the acquisition means; a position determination means for determining whether a positional relationship between the installation location of the tag and the information processing terminal satisfies a predetermined positional relationship condition, based on the position information regarding the installation location of the tag stored in the tag position storage means and the position information of the information processing terminal acquired by the acquisition means; and an execution means for executing processing to provide the predetermined service when it is determined that the acquired authentication code is not a code that has been previously acquired and that the positional relationship between the installation location of the tag and the information processing terminal satisfies the predetermined positional relationship condition.

[0008] The present disclosure can be understood as an information processing device, a system, a method executed by a computer, or a program executed by a computer. The present disclosure can also be understood as such a program recorded on a recording medium readable by a computer or other device, machine, etc. Here, a recording medium readable by a computer, etc. refers to a recording medium that stores information such as data and programs by electrical, magnetic, optical, mechanical, or chemical action and can be read by a computer, etc. [Effects of the Invention]

[0009] According to the present disclosure, it is possible to prevent a service from being used in a place other than where a tag is installed. [Brief explanation of the drawings]

[0010] [Figure 1] 1 is a schematic diagram illustrating an outline of a hardware configuration of a system according to an embodiment. [Figure 2] FIG. 1 is a diagram illustrating an outline of the functional configuration of a system according to an embodiment. [Figure 3] 1 is a flowchart and a communication sequence (1) showing an outline of a vehicle dispatch process flow according to an embodiment. [Figure 4] 10 is a flowchart and a communication sequence (2) showing an outline of a vehicle dispatch process flow according to an embodiment. [Figure 5] FIG. 10 is a diagram illustrating an outline of the functional configuration of a system according to a first variation. [Figure 6] 10 is a flowchart showing an outline of a vehicle dispatch processing flow and a communication sequence according to Variation 1. [Figure 7] FIG. 10 is a schematic diagram showing an outline of the hardware configuration of a system according to Variation 2. [Figure 8] FIG. 10 is a diagram illustrating an outline of the functional configuration of a system according to Variation 2. [Figure 9]10 is a flowchart and a communication sequence showing an outline of a vehicle dispatch processing flow according to Variation 2. DETAILED DESCRIPTION OF THE INVENTION

[0011] Hereinafter, embodiments of the system, method, and program according to the present disclosure will be described with reference to the drawings. However, the embodiments described below are merely examples, and the system, method, and program according to the present disclosure are not limited to the specific configurations described below. In implementing the present disclosure, a specific configuration according to the embodiment may be appropriately adopted, and various improvements and modifications may be made.

[0012] In this embodiment, an embodiment will be described in which the system, method, and program according to the present disclosure are implemented in a system for dispatching (reserving) taxi vehicles. However, the system, method, and program according to the present disclosure can be widely used in technologies for providing services, and the application of the present disclosure is not limited to the examples shown in the embodiment.

[0013] <System configuration> 1 is a schematic diagram showing an outline of the hardware configuration of a system according to this embodiment. The system according to this embodiment includes an authentication server (authentication device) 1 connected to a network, a providing device 3 communicably connected to the authentication server 1 via the network, one or more tags 8, and a user terminal 9 used by a user to read the tags 8. When a user (such as a passenger) holds (touches) the user terminal 9 over (touches) the tag 8 and data read from the tag 8 is transmitted from the user terminal 9 to the authentication server 1, the authentication server 1 performs authentication using the data. Depending on the result of authentication by the authentication server 1, the authentication server 1 instructs the providing device 3 to provide a service. In this embodiment, the providing device 3 provides a taxi dispatch service (taxi ride service).

[0014] The authentication server 1 is a computer including a central processing unit (CPU) 11, a read-only memory (ROM) 12, a random access memory (RAM) 13, a storage device 14 such as an electrically erasable and programmable read-only memory (EEPROM) or a hard disk drive (HDD), an input device 15 such as a keyboard, a mouse, or a touch panel, an output device 16 such as a display, and a communication unit 17 such as a network interface card (NIC). However, the specific hardware configuration of the authentication server 1 may be omitted, replaced, or added as appropriate depending on the embodiment. Furthermore, the authentication server 1 is not limited to a device consisting of a single housing. The authentication server 1 may be realized by multiple devices using so-called cloud or distributed computing technology. Furthermore, the authentication server 1 may be a cloud server. The authentication server 1 performs authentication using data transmitted from the user terminal 9 (such as data read from the tag 8).

[0015] The providing device 3 is a computer including a CPU 31, a ROM 32, a RAM 33, a storage device 34, an input device 35, an output device 36, a communication unit 37, and the like. However, the specific hardware configuration of the providing device 3 can be omitted, replaced, or added as appropriate depending on the embodiment. Furthermore, the providing device 3 is not limited to a device consisting of a single housing. The providing device 3 may be realized by multiple devices using so-called cloud or distributed computing technology, etc. The providing device 3 is a device that provides a predetermined service in response to an instruction from the authentication server 1. In this embodiment, the providing device 3 is exemplified as a dispatching device (dispatch system) that arranges taxis. Specifically, a taxi call center that provides a taxi dispatch service is exemplified. However, the service provided by the providing device 3 may be any service other than a taxi dispatch service. For example, the service provided by the providing device 3 may be any service such as a service that controls a device connected to the providing device 3 via a network so as to be able to communicate with the providing device 3 (such as a service that issues control commands to the device), a service that provides various information, a payment service, etc. When the service provided by the providing device 3 is a device control service, the controlled device may be any device such as an air conditioner, a lighting device, an electric lock, a power supply device, etc. The system according to this embodiment may be configured such that the functions of the authentication server 1 and the providing device 3 are respectively provided in a device formed in a single housing.

[0016] The tag 8 is a small tag (IC tag) equipped with an integrated circuit (IC). The tag 8 according to this embodiment transmits (sends) a different code (URL) each time it is accessed via near-field wireless communication. In this embodiment, an NFC tag, which is an IC tag capable of near-field wireless communication, is exemplified as an example of the tag 8. Specifically, an NFC tag equipped with an IC chip having a SUN (Secure Unique NDEF (NFC Data Exchange Format)) message function is exemplified. Normally, if a URL is written in a tag defined by NDEF, it becomes possible to direct a user to the URL by holding an information processing terminal over the tag and reading the information (data such as a URL). However, the SUN message function changes the parameters of this URL each time an information processing terminal is held over the tag (accessed via near-field wireless communication), making it possible to generate and send a different URL each time even with the same tag.

[0017] The URL sent by an NFC tag equipped with an IC chip with a SUN message function includes, for example, address information, a code, and signature data (signature data (signature) generated based on the code) as URL parameters. The code is information (data) consisting of a combination of data indicating the model number of the tag 8, an ID unique to the tag 8, and the number of times the tag 8 has been accessed. The number of times the tag 8 has been accessed (counter) is the number of times the tag 8 has been accessed via near-field wireless communication (the total number of accesses including the current access), that is, the number of times an information processing terminal has been held over (touched) the tag 8. For example, if the tag 8 has been accessed (N-1) times by the information processing terminals of an unspecified number of users, and a certain user's information processing terminal accesses the tag 8, the number of times the access is included in the acquired code will be a value indicating N (times). In the NFC tag 8 (IC chip), the access number (counter) is counted up (for example, incremented by 1) each time the tag 8 is accessed, thereby making it possible to vary (change) the code (URL parameter). That is, in the NFC tag 8, by including the number of accesses in the code, which is a parameter of the URL to be sent, it becomes possible to send a different URL (code) every time it is accessed by short-range wireless communication.

[0018] However, the number of accesses is an example of "data (identifier) ​​capable of identifying access to the tag 8," and the code may include data other than (data indicating) the number of accesses as data (identifier) ​​capable of identifying access to the tag 8. For example, the code may include, as the identifier, an identifier (data) indicating a value that decreases each time the tag 8 is accessed (for example, decreases by 1 from a predetermined value). Note that (data indicating) the number of accesses and the identifier (data) indicating the value that decreases each time the tag 8 is accessed are examples of "data corresponding to the number of accesses." Furthermore, for example, the data (identifier) ​​capable of identifying access to the tag 8 may be an identifier that indicates a random value each time the tag 8 is accessed.

[0019] Furthermore, the tag 8 according to this embodiment only needs to transmit a different code each time it is accessed by short-range wireless communication, and the code transmitted from the tag 8 is not limited to the above-described example. Therefore, for example, the code may not include data indicating the model number of the tag (such as information consisting of a combination of the tag's unique ID and the number of accesses (data that can identify accesses)), or may further include other information. Furthermore, in the case of a system that does not use the unique ID of the tag 8, the code transmitted from the tag 8 does not need to include the unique ID of the tag 8.

[0020] In the NFC tag 8 (IC chip), the plaintext code is encrypted, and the encrypted code (hereinafter referred to as the "encrypted code") is included in the URL as a URL parameter. Specifically, the URL includes an encrypted code (e.g., "A12B345C67D891EF1A23465B98732D") obtained by encrypting the plaintext code, which is a combination of data indicating the tag model number (e.g., "ABC1"), a tag-unique ID (e.g., "11111a222233"), and the number of accesses (e.g., "06e"). However, the number of digits in the code and the number of digits of the data indicating the tag model number, the tag-unique ID, and the number of accesses included in the code are not limited to the above example and may be any number of digits. In this way, the NFC tag 8 according to this embodiment is capable of generating a secure unique code (URL). Any encryption key may be used for encrypting the code, such as a public key in a public key cryptosystem or a shared key in a common key cryptosystem. A common encryption key may be used for multiple tags, or different encryption keys may be used for each tag or each tag installation area.

[0021] As described above, the NFC tag 8 according to this embodiment uses the SUN message function to provide high security and code uniqueness, enabling highly reliable data communication. However, the tag 8 is not limited to the above-described example and may be any IC tag as long as it transmits a different code each time it is accessed via near-field wireless communication. Furthermore, the one or more tags 8 included in the system according to this embodiment may all be tags of the same type (model number), or may be tags of different types. In this embodiment, the one or more tags 8 are each installed at a predetermined location, such as a station or a facility. Furthermore, in this embodiment, the URL transmitted from the tag 8 includes signature data, such as a Cipher-based Message Authentication Code (CMAC), to prevent data tampering. However, the URL transmitted from the tag 8 does not necessarily have to include signature data.

[0022] The user terminal 9 (referred to as "information processing terminal" in the present application) is a computer equipped with a CPU 91, a ROM 92, a RAM 93, a storage device 94, an input device 95, an output device 96, and a communication unit 97. The user terminal 9 is, for example, a terminal such as a smartphone or a tablet PC. However, the specific hardware configuration of the user terminal 9 can be omitted, replaced, or added as appropriate depending on the embodiment. Furthermore, the user terminal 9 is not limited to a device consisting of a single housing. The user terminal 9 may be realized by multiple devices using so-called cloud or distributed computing technology, etc.

[0023] 2 is a diagram showing an outline of the functional configuration of the system according to this embodiment. The functional configurations of the authentication server 1, the providing device 3, and the user terminal 9 included in the system according to this embodiment will be described below.

[0024] (Authentication Server) The authentication server 1 is provided with an acquisition unit 21, a code storage unit 22, a code determination unit 23, a notification unit 24, a page data transmission unit 25, and an execution unit 26, by a program recorded in a storage device 14 being read into a RAM 13 and executed by a CPU 11, which controls each piece of hardware provided in the authentication server 1. Note that in this embodiment and other embodiments described later, each function provided in the authentication server 1 is executed by the CPU 11, which is a general-purpose processor, but some or all of these functions may be executed by one or more dedicated processors.

[0025] The acquiring unit 21 acquires data acquired from the tag 8 by the user terminal 9 accessing the tag 8. Specifically, the acquiring unit 21 acquires, from the user terminal 9, the code acquired by the user terminal 9 from the tag 8. In this embodiment, an NFC tag that transmits an encrypted code is exemplified as the tag 8, so the acquiring unit 21 acquires the encrypted code from the user terminal 9. First, when the user holds the user terminal 9 over the tag 8, the user terminal 9 acquires a URL including address information, the encrypted code, and signature data from the tag 8 and accesses the acquired URL. In other words, the user terminal 9 connects via a network to a computer (authentication server 1) indicated by the address information included in the acquired URL. As a result, the encrypted code read from the tag 8 is transmitted to the authentication server 1, and the acquiring unit 21 can acquire the encrypted code. However, if the tag 8 is a tag that transmits a plaintext code (an unencrypted code), the acquiring unit 21 may acquire the plaintext code from the user terminal 9. In this case, the decryption process by the acquiring unit 21, which will be described later, is not performed.

[0026] The acquisition unit 21 performs a decryption process on the encrypted code acquired from the user terminal 9 to acquire a decrypted code (plaintext code) that is not encrypted (information consisting of a combination of plaintext data indicating the model number of the tag 8, the unique ID of the tag 8, and the number of accesses to the tag 8). Any type of encryption key (decryption key) may be used for the encryption key (decryption key) used in the decryption process by the acquisition unit 21. For example, if the encrypted code is generated in the tag 8 by encryption processing using a public key of a public key encryption system, a private key corresponding to the public key is used for the decryption process. For example, if the encrypted code is generated in the tag 8 by encryption processing using a shared key of a symmetric key encryption system, the same shared key is used for the decryption process. The encryption key (decryption key) used for the decryption process may be stored in advance in the authentication server 1.

[0027] The code acquired by the acquisition unit 21 is the target of determination in the initial determination by the code determination unit 23, which will be described later. Hereinafter, the code that is the target of determination in the initial determination by the code determination unit 23 (the code that is the target of determination as to whether it is the first use or not) will be referred to as the "authentication code." The authentication code is a code (plain text code or encrypted code) acquired by the user terminal 9 when accessing the tag 8, or a decrypted code obtained by performing a decryption process on the acquired code when the acquired code is an encrypted code. In other words, the authentication code is a plain text code or an encrypted code. The acquisition unit 21 acquires, as the authentication code, the code (plain text code or encrypted code) acquired by the user terminal 9 when accessing the tag 8, or a decrypted code obtained by performing a decryption process on the code when the code is an encrypted code. In this embodiment, a case where a decrypted code is used as the authentication code will be illustrated.

[0028] The acquisition unit 21 also acquires location information of the user terminal 9 and information input by the user (including "selective input") in relation to the service provided. In this embodiment, information related to taxi rides (dispatch), such as the number of passengers (hereinafter referred to as "ride information"), is acquired as information input by the user in relation to the service provided. Note that in this embodiment, the acquisition unit 21 acquires this information by receiving a dispatch request transmitted from the user terminal 9.

[0029] The code storage unit 22 stores the code acquired by the acquisition unit 21. In this embodiment, if the code acquired by the acquisition unit 21 is not a code that has been acquired by the acquisition unit 21 before, the code storage unit 22 stores the acquired code. In other words, a code that has not been acquired (used) before (a code that is being used for the first time) is stored in the code storage unit 22. As a result, acquired codes (used codes) including the code that has been acquired (used) for the first time this time are stored in the authentication server 1.

[0030] The code stored in the code storage unit 22 may be an encrypted code or a plain code, but the code storage unit 22 stores a code (encrypted code or plain code) corresponding to the code to be determined in the initial determination described below. In this embodiment, in order to determine whether the decrypted code (plain code) acquired by the acquisition unit 21 is a code used for the first time, the code storage unit 22 stores the decrypted code acquired by the acquisition unit 21. Specifically, the code storage unit 22 stores information consisting of a combination of data indicating the tag model number, a tag-unique ID, and the number of accesses. In other words, the data indicating the tag model number, the tag-unique ID, and the number of accesses are stored in association with each other. However, if one or more tags 8 included in the system according to this embodiment are all of the same type (model number), data indicating the same model number (e.g., "ABC1") is acquired from all the tags 8. Therefore, the data indicating the tag model number may be omitted (removed), and information consisting of a combination of the tag-unique ID and the number of accesses may be stored. In other words, the tag-unique ID and the number of accesses may be stored in association with each other. Furthermore, if the code to be judged in the initial judgment is an encrypted code, the code storage unit 22 stores the encrypted code acquired by the acquisition unit 21.

[0031] In this embodiment, the code storage unit 22 stores all codes (decoded codes) acquired by the acquisition unit 21. However, among the acquired codes, for codes having the same combination of data indicating the tag model number and the tag-unique ID, only the code (decoded code) with the largest access count value may be stored. Furthermore, if an identifier indicating a value that decreases each time the tag 8 is accessed is used as data (identifier) ​​for identifying access to the tag 8, among the acquired codes having the same combination of data indicating the tag model number and the tag-unique ID, only the code (decoded code) with the smallest identifier value may be stored. In other words, among the codes acquired by the authentication server 1, only the code acquired in the most recent access (access to the tag 8) may be stored.

[0032] The code determination unit 23 determines whether the acquired code is a correct code. The code determination unit 23 determines whether the code acquired by the acquisition unit 21 is a genuine (legal) code, that is, whether it is an inauthentic code such as a counterfeit code. Specifically, if the acquisition unit 21 fails to decrypt the encrypted code in the decryption process, the code determination unit 23 determines that the acquired code is not a correct code. Furthermore, for example, if the decrypted code obtained by the decryption process by the acquisition unit 21 does not correspond to a predetermined format (standard format), the code determination unit 23 may determine that the acquired code is not a correct code.

[0033] Furthermore, the code determination unit 23 determines whether or not the unique ID acquired by the acquisition unit 21 is an ID (tag) that can be used in the system according to this embodiment. By registering the unique IDs of one or more tags 8 that can be used in this system in advance in the storage device 14 or the like of the authentication server 1, the code determination unit 23 can determine whether an ID identical to the unique ID acquired by the acquisition unit 21 is registered in the authentication server 1, that is, whether or not the acquired unique ID is a usable ID.

[0034] Furthermore, the code determination unit 23 determines whether the code (authentication code) acquired by the authentication server 1 (acquisition unit 21) has been acquired before by the authentication server 1 (acquisition unit 21). That is, the code determination unit 23 determines whether the code acquired by the acquisition unit 21 is a used code or a first-time use code (first-time determination). The code determination unit 23 performs the first-time determination by referring to the code (used code) stored in the code storage unit 22. In this embodiment, the code determination unit 23 determines whether a code matching the decryption code (authentication code) acquired by the acquisition unit 21 is stored in the code storage unit 22. If a code matching the acquired authentication code is not stored, it can be determined that the authentication code is a first-time use code. On the other hand, if a code matching the acquired authentication code is already stored, it can be determined that the authentication code is not a first-time use code (already used). In this way, by determining that the acquired code is a correct code and a first-time use code, the code determination unit 23 (authentication server 1) authenticates the code.

[0035] As described above, when the code storage unit 22 stores only the code with the largest access count among the acquired codes (plaintext codes), the code determination unit 23 may perform the initial determination by determining whether the acquired authentication code (access count) is greater than the code (access count) stored in the code storage unit 22. When the acquired authentication code has a larger value than the code stored in the code storage unit 22, it can be determined that the authentication code is used for the first time. On the other hand, when the value of the acquired authentication code is equal to or less than the value of the code stored in the code storage unit 22, it can be determined that the authentication code is not used for the first time (has already been used). Furthermore, as described above, when the code storage unit 22 stores only the code with the smallest value of an identifier (an identifier indicating a value that decreases each time the tag 8 is accessed) that can identify access to the tag 8 among the acquired codes (plaintext codes), the code determination unit 23 may perform the initial determination by determining whether the acquired authentication code (the value of the identifier) ​​is smaller than the code (the value of the identifier) ​​stored in the code storage unit 22.

[0036] Furthermore, as described above, if one or more tags 8 provided in the system according to this embodiment all have the same model number, the code storage unit 22 may store only information consisting of a combination of a tag-unique ID and the number of accesses, without storing data indicating the model number of the tag 8. In this case, the code determination unit 23 determines whether the code (decoded code) acquired by the acquisition unit 21 is a used code by determining whether the combination of the tag-unique ID and the number of accesses included in the decoded code acquired by the acquisition unit 21 is stored in the code storage unit 22.

[0037] The notification unit 24 issues various notifications. When the code determination unit 23 determines that the acquired code is incorrect, when the acquired unique ID is unusable, or when the acquired code has already been used, the notification unit 24 issues an error notification to the user terminal 9 (user). This makes it possible to deny the user access to the system (taxi dispatch service). The error notification may be any notification to deny access to the user, such as a notification that the read code is not authentic, a notification that the code (URL) has already been used, or a notification that the web page cannot be sent.

[0038] In addition, when the notification unit 24 receives a vehicle dispatch request from the user terminal 9 (user) and issues or has issued a vehicle dispatch instruction to the vehicle dispatch device (providing device) 3, it may notify the user terminal 9 that it has issued or issued a vehicle dispatch instruction to the vehicle dispatch device 3.

[0039] The page data transmission unit 25 transmits page data (web page data) to the user terminal 9 (browser). In this embodiment, the page data transmission unit 25 transmits page data corresponding to a URL (code) accessed by the user terminal 9 (user).

[0040] When it is determined that the authentication code acquired by the acquisition unit 21 is not a code that has been acquired by the acquisition unit 21 before (first use), the execution unit 26 executes a process for providing a predetermined service. In this embodiment, a taxi dispatch service (a service for dispatching a taxi) is exemplified as the "predetermined service." That is, in this embodiment, the execution unit 26 executes a process for dispatching a taxi as the "process for providing the predetermined service." Specifically, as the "process for dispatching a taxi," an instruction to dispatch the taxi (an instruction to execute (provide) a taxi dispatch service) is given to the dispatch device 3. That is, a request for dispatching a taxi is transmitted to the dispatch device 3. The dispatch request transmitted by the execution unit 26 includes, for example, location information of the user terminal 9 and information related to the service to be provided (boarding information such as the number of passengers) acquired by the acquisition unit 21. In this way, in this embodiment, the execution unit 26 issues a service provision (execution) instruction (including an instruction to permit provision of the service) to the providing device 3 that provides the predetermined service as the "process for providing the predetermined service."

[0041] As described above, the "predetermined service" is not limited to a taxi dispatch service and may be any other service. Therefore, the "predetermined service" may be a service that controls devices connected to the providing device 3 via a network, a service that provides various information, a payment service, or the like. For example, a tag 8 may be installed in a space such as a hotel or spa, and only users who hold their user terminal 9 over the installed tag 8 and view a predetermined advertisement on the user terminal 9 may use a home appliance (such as a hairdryer) installed in the space. In this case, the user terminal 9 notifies the authentication server 1 that the advertisement has been viewed. Upon receiving the notification from the user terminal 9, the authentication server 1 (execution unit 26) enables the provision of the service. However, the provision of the service is enabled on the premise that the authentication code is determined to be the first use. As the "process for providing the service," the execution unit 26 instructs, for example, a device (providing a home appliance usage service) 3 that manages the electric lock of the home appliance (such as a hairdryer) to unlock the electric lock (to make the home appliance usable). Furthermore, for example, the execution unit 26 may instruct the power supply device 3 that supplies power to the home appliance (such as a dryer) to supply power to the home appliance (make the home appliance available) for a predetermined time (for example, 10 minutes) from the time the advertisement is viewed or the time the notification is received.

[0042] The content of the "predetermined service" and the content of the "processing for providing the predetermined service" performed by the execution unit 26 may be stored in the authentication server 1 (storage device 14). Also, for example, the authentication server 1 may store, for each of one or more tags 8, the unique ID of the tag 8 and the content of the service corresponding to the tag 8 and / or the content of the processing performed by the execution unit 26, in association with each other. This makes it possible to provide the predetermined service corresponding to the tag 8.

[0043] (Providing device) The providing device 3 is provided with a receiving unit 41, a display control unit 42, a vehicle dispatch processing unit 43, and a user notification unit 44, by a program recorded in a storage device 34 being read into a RAM 33 and executed by a CPU 31, which controls each piece of hardware provided in the providing device 3. Note that in this embodiment and other embodiments described later, each function provided in the providing device 3 is executed by the CPU 31, which is a general-purpose processor, but some or all of these functions may be executed by one or more dedicated processors.

[0044] The receiving unit 41 receives a vehicle dispatch request (taxi dispatch instruction) from the authentication server 1. The receiving unit 41 receives, as information included in the vehicle dispatch request, location information of the user terminal 9 and information related to the service to be provided (boarding information such as the number of passengers).

[0045] The display control unit 42 controls various displays. The display control unit 42 notifies the operator of the vehicle dispatch request by displaying the vehicle dispatch request received from the authentication server 1 via the output device 36. As the display of the vehicle dispatch request, for example, location information of the user terminal 9 and information related to the service to be provided (boarding information such as the number of passengers) are displayed.

[0046] The dispatch processing unit 43 executes processing to provide a service (taxi dispatch service). In response to the dispatch request displayed by the display control unit 42, an operator who dispatches a taxi searches for an available taxi that is closest to the user (user terminal 9). Specifically, the available taxi that is closest to the user is extracted by referring to the location information of the user (user terminal 9), the location information of each taxi vehicle, and the operation information of each taxi vehicle. The operator performs a dispatch operation via the dispatch device 3 (input device 35) to request a taxi from the extracted taxi vehicle. In response to the operator's dispatch operation, the dispatch processing unit 43 executes dispatch processing for the taxi vehicle. For example, the dispatch processing unit 43 transmits a dispatch request (a dispatch request requesting a response (confirmation notification) from the taxi vehicle) to the taxi vehicle, and upon receiving a response from the taxi vehicle indicating that the taxi is available for dispatch, transmits a formal dispatch instruction to the taxi vehicle. In this embodiment, the taxi vehicle closest to the user is searched for using the location information of the user terminal 9, but since it is assumed that the user is near the location where the tag 8 is installed, the taxi vehicle closest to the user may also be searched for using information regarding the location where the tag 8 is installed (such as location information of the location where the tag 8 is installed or location information indicating the area of ​​the installation location).

[0047] The user notification unit 44 provides various notifications to the user (user terminal 9). The user notification unit 44 notifies the user terminal 9 that a taxi vehicle is being searched for, that a taxi has been dispatched (that a taxi vehicle is on its way), and the like.

[0048] (user terminal) The user terminal 9 is provided with a tag reading unit 61, a transmitting unit 62, a display control unit 63, an input receiving unit 64, and a position acquiring unit 65, by a program recorded in a storage device 94 being read into a RAM 93 and executed by a CPU 91, which controls each piece of hardware provided in the user terminal 9. Note that in this embodiment and other embodiments described later, each function provided in the user terminal 9 is executed by the CPU 91, which is a general-purpose processor, but some or all of these functions may be executed by one or more dedicated processors.

[0049] The tag reader 61 performs a reading process on the tag 8. In this embodiment, the tag reader 61 reads data (URL) from the tag 8 by performing near field communication (NFC communication) with the tag 8.

[0050] The transmission unit 62 transmits various information to the authentication server 1. The transmission unit 62 connects to the server (authentication server) 1 indicated by the address information of the URL read by the tag reading unit 61, and transmits a code (e.g., an encrypted code) included in the URL to the authentication server 1. In other words, the URL read by the tag reading unit 61 is accessed. The transmission unit 62 also transmits a vehicle dispatch request to the authentication server 1, including boarding information such as the number of passengers accepted by the input accepting unit 64 and location information of the user (user terminal 9) acquired by the location acquiring unit 65.

[0051] The display control unit 63 controls various displays. The display control unit 63 displays page data received from the authentication server 1 via the output device 96. As a result, a web page (web UI (User Interface) screen) is displayed on the browser of the user terminal 9. The web page according to this embodiment is a screen used by the user to request dispatch of a taxi vehicle, and boarding information such as the number of passengers is input on this screen. In addition, the display control unit 63 displays information notified from the authentication server 1 and the dispatch device 3 via the output device 96.

[0052] The input receiving unit 64 receives input from the user. The input receiving unit 64 receives input of boarding information such as the number of passengers.

[0053] The location acquisition unit 65 acquires location information of its own device (user terminal 9). The location information of the user terminal 9 is acquired, for example, by receiving radio waves from an artificial satellite (GPS (Global Positioning System) satellite). However, any method may be used to acquire the location information, and the location information may be acquired based on a Wi-Fi (registered trademark) access point or a mobile phone base station communicating with the user terminal 9.

[0054] 3 and 4 are a flowchart and a communication sequence showing an outline of the vehicle dispatch process flow according to this embodiment. The process shown in this flowchart is started when the user brings the user terminal 9 close to (holds over) the tag 8, etc.

[0055] In steps S101 and S102, the URL is read from the tag 8 in the user terminal 9, and the URL is accessed. The tag reading unit 61 reads the URL from the tag 8 by performing NFC communication with the tag 8 (step S101), and the transmission unit 62 connects to the server (authentication server) 1 indicated by the read URL and transmits data included in the URL (such as a code (encrypted code)) to the authentication server 1 (step S102). For example, when the URL is read, the URL is displayed via the output device 96, and the user accesses the URL by touching or otherwise specifying it. Thus, in step S102, the code included in the URL is acquired in the authentication server 1 (by the acquisition unit 21). Thereafter, the process proceeds to step S103.

[0056] In step S103, the authentication server 1 performs a code decryption process. When the acquisition unit 21 acquires the encrypted code transmitted in step S102, the acquisition unit 21 performs a decryption process on the encrypted code. As a result, the acquisition unit 21 acquires a decrypted code (authentication code). Then, the process proceeds to step S104.

[0057] In step S104, the authentication server 1 determines whether the acquired code is a correct (authentic) code. The code determination unit 23 determines whether the authentication code acquired in step S103 is a correct code. If the acquired authentication code is a correct code (Yes in step S104), the process proceeds to step S105. On the other hand, if the acquired authentication code is not a correct code (No in step S104), the process proceeds to step S107.

[0058] In step S105, it is determined whether the acquired unique ID is a usable ID. The code determination unit 23 determines whether the unique ID included in the authentication code (decryption code) acquired in step S103 is a usable ID (an ID pre-registered in the authentication server 1). If it is a usable ID (Yes in step S105), the process proceeds to step S106. On the other hand, if it is not a usable ID (No in step S105), the process proceeds to step S107.

[0059] In step S106, the authentication server 1 determines whether the acquired code is used for the first time. The code determination unit 23 determines whether the authentication code acquired in step S103 is used for the first time (whether it is a code not stored in the code storage unit 22). If it is used for the first time (Yes in step S106), the process proceeds to step S108. On the other hand, if it is not used for the first time (No in step S106), the process proceeds to step S107. Note that in step S106, it may be determined whether the acquired decryption code is used for the first time by determining whether the combination of the unique ID of the tag 8 and the number of accesses (data that can identify accesses to the tag 8) included in the authentication code acquired in step S103 is used for the first time (is not stored in the code storage unit 22). Furthermore, when an encrypted code is used as the authentication code, it may be determined in step S106 whether the encrypted code acquired in step S102 is used for the first time (is not stored in the code storage unit 22).

[0060] In step S107, the authentication server 1 notifies the user terminal 9 of an error. The notification unit 24 notifies the user terminal 9 of the error because the code acquired by the acquisition unit 21 is not the correct code or is not the first use. Thereafter, the process proceeds to step S110.

[0061] In step S108, page data is transmitted from authentication server 1 to user terminal 9. Page data transmission unit 25 transmits page data corresponding to the URL (code) accessed in step S102 to user terminal 9. Thereafter, the process proceeds to step S109 and step S110.

[0062] In step S109, the code is recorded in the authentication server 1. The code storage unit 22 stores the authentication code (decryption code) that was recently used and obtained in step S103. In this way, used codes (codes that have been used (sent) by one or more users (user terminals 9)) are stored in the authentication server 1. The code storage unit 22 may also store part of the authentication code (decryption code) (a combination of a unique ID and the number of accesses).

[0063] In step S110, it is determined whether an error or page data has been received in the user terminal 9. If an error has been received ("Error Received" in step S110), the process proceeds to step S111. On the other hand, if page data has been received ("Page Data Received" in step S110), the process proceeds to step S112.

[0064] In step S111, an error is displayed on the user terminal 9. The display control unit 63 displays the error notified in step S107 via the output device 96. Thereafter, the processing shown in this flowchart ends.

[0065] In step S112, a Web UI screen is displayed on the user terminal 9. The display control unit 63 displays the page data (Web UI screen) received in step S108 via the output device 96. The Web UI may be multilingual. Thereafter, the process proceeds to step S113.

[0066] In step S113, input of the number of passengers is accepted at the user terminal 9. The input accepting unit 64 accepts the input of the number of passengers entered by the user on the Web UI screen displayed in step S112. Note that input of boarding information other than the number of passengers may also be accepted. Thereafter, the process proceeds to step S114.

[0067] In step S114, the number of passengers and location information are transmitted from the user terminal 9 to the authentication server 1. The transmission unit 62 requests the authentication server 1 to arrange for a taxi by transmitting a vehicle dispatch request including the number of passengers acquired in step S113 and the location information of the user terminal 9 acquired by the location acquisition unit 65 to the authentication server 1. Note that the location information of the user terminal 9 is acquired in step S114, but may be acquired at a point in time before step S114. Thus, in step S114, the authentication server 1 (by the acquisition unit 21) acquires the vehicle dispatch request (including the number of passengers and the location information of the user terminal 9). Thereafter, the process proceeds to step S115.

[0068] In step S115, the authentication server 1 transmits a vehicle dispatch request to the vehicle dispatch device (taxi call center) 3. The execution unit 26 transmits a vehicle dispatch request (including the number of passengers acquired in step S114 and the location information of the user terminal 9) to the vehicle dispatch device 3 based on the vehicle dispatch request received in step S114. That is, the execution unit 26 performs processing for dispatching a taxi (issuing a taxi dispatch instruction to the vehicle dispatch device 3). Thereby, in step S115, the vehicle dispatch request is received in the vehicle dispatch device 3 (by the receiving unit 41). Also in step S115, the notification unit 24 issues a vehicle dispatch instruction to the vehicle dispatch device 3 or notifies the user terminal 9 that the instruction has been issued. Thereafter, the processing proceeds to steps S116 and S117. Note that the vehicle dispatch request transmitted from the authentication server 1 to the vehicle dispatch device 3 may be the vehicle dispatch request itself transmitted from the user terminal 9 to the authentication server 1. In this case, the execution unit 26 transfers (notifies) the vehicle allocation request received in step S114 to the vehicle allocation device 3. In addition, the vehicle allocation request transmitted from the authentication server 1 to the vehicle allocation device 3 may include other information in addition to the information included in the vehicle allocation request transmitted from the user terminal 9 to the authentication server 1.

[0069] In step S116, a message indicating that a vehicle dispatch instruction is being given to the vehicle dispatch device 3 is displayed on the user terminal 9. Upon receiving the notification from the authentication server 1 in step S115, the display control unit 63 causes the output device 96 to display a message indicating that a vehicle dispatch instruction is being given to the vehicle dispatch device 3 (for example, a message such as "We are currently informing the call center").

[0070] In step S117, the dispatch device 3 notifies the operator of a dispatch request. The display control unit 42 notifies the operator who will be dispatching the vehicle by displaying the dispatch request (taxi dispatch instruction) received in step S115 via the output device 36. The display control unit 42 displays, for example, the number of passengers and the location information of the user terminal 9 as the display of the dispatch request. Thereafter, the process proceeds to step S118.

[0071] In step S118, the operator performs a vehicle dispatch operation. After confirming the vehicle dispatch request displayed in step S117, the operator determines the taxi vehicle (driver) to be dispatched, and performs an operation (dispatch operation) to dispatch the taxi vehicle (notify the taxi vehicle of the content of the vehicle dispatch request from the user). The operator extracts the taxi vehicle that is closest to the user and can be dispatched by, for example, referring to the location information of the user terminal 9 displayed in step S117, the location information of each taxi vehicle, and the operation information of each taxi vehicle, and determines the extracted taxi vehicle as the taxi vehicle to be dispatched. After that, the process proceeds to step S119.

[0072] In step S119, the dispatch device 3 transmits a dispatch request (a request regarding whether or not a dispatch is possible) to a taxi. The dispatch processing unit 43 transmits the dispatch request to the taxi determined by the operator in step S118. The dispatch request transmitted by the dispatch processing unit 43 includes information regarding the dispatch request from the user (such as the number of passengers received in step S115 and the location information of the user terminal 9). Thereafter, the process proceeds to step S120 and step S122.

[0073] In step S120, the vehicle dispatch device 3 notifies the user terminal 9 that a vehicle search is in progress. The user notification unit 44 notifies the user terminal 9 that a taxi vehicle is being searched for. Note that the processing of step S120 may be performed at any time after the processing of step S117 is performed and before the processing of step S119 is performed. Thereafter, the processing proceeds to step S121.

[0074] In step S121, a message indicating that a vehicle search is in progress is displayed on the user terminal 9. Upon receiving the notification from the vehicle dispatching device 3 in step S120, the display control unit 63 displays a message indicating that a taxi vehicle is being searched for (for example, a message such as "Searching for an available driver") via the output device 96.

[0075] In step S122, a confirmation is sent to the taxi. The taxi (driver) sends a notification to the dispatch device 3 that the dispatch request sent in step S119 has been confirmed (a reply that the dispatch is possible). Then, the process proceeds to step S123.

[0076] In step S123, the dispatch device 3 issues a dispatch instruction to the taxi vehicle. Having received a response from the taxi vehicle in step S122 that dispatch is possible, the dispatch processing unit 43 transmits a formal dispatch instruction to the taxi vehicle. Note that the dispatch instruction transmitted by the dispatch processing unit 43 may include information related to the dispatch request from the user (such as the number of passengers received in step S115 and the location information of the user terminal 9). Thereafter, the process proceeds to step S124 and step S125.

[0077] In step S124, a vehicle dispatch notification is sent from the vehicle dispatch device 3 to the user terminal 9. The user notification unit 44 notifies the user that a vehicle has been dispatched (that a taxi is on its way). After that, the process proceeds to step S126.

[0078] In step S125, the taxi heads to the user's location. The driver (taxi) who has sent the confirmation notification in step S122 heads to the location indicated by the location information of the user terminal 9. Note that the driver (taxi) may also head to the location where the tag 8 is installed.

[0079] In step S126, a message indicating that a vehicle has been dispatched is displayed on the user terminal 9. Upon receiving the notification from the vehicle dispatch device 3 in step S124, the display control unit 63 displays a message indicating that a vehicle has been dispatched (for example, a message such as "The driver is on his way now, please wait a moment") via the output device 96. Thereafter, the processing shown in this flowchart ends.

[0080] In steps S114 and S115, the user terminal 9 transmits the number of passengers and their location information to the authentication server 1, and the authentication server 1 transmits the number of passengers and their location information to the vehicle dispatching device 3. However, the boarding information and location information may be transmitted directly from the user terminal 9 to the vehicle dispatching device 3 without going through the authentication server 1. In this case, the authentication server 1 (execution unit 26) may transmit a permission notice to provide the service to the vehicle dispatching device 3 (an instruction to permit the provision of the service). In addition, the vehicle search in progress notice in step S120 and the vehicle dispatch notice in step S124 may be transmitted from the vehicle dispatching device 3 to the user terminal 9 via the authentication server 1. In addition, the method of providing a taxi dispatching service by the vehicle dispatching device 3 and the operator is not limited to the above-described example, and various methods may be used. For example, in steps S119 and S123, the vehicle dispatching device 3 transmits a notice or instruction to the taxi, but the operator may also transmit a notice or instruction to the taxi driver using a telephone, a walkie-talkie, or the like.

[0081] As described above, according to this embodiment, when an authentication code obtained by accessing a tag that transmits a different code each time it is accessed, or a decrypted code obtained by decrypting the code if the code is an encrypted code, is determined to be a code that has not been previously obtained, a process for providing the service is performed, thereby preventing the service from being used in a location other than the tag installation location. In other words, even if a user stores a code (URL) that has been used once, for example by copying it, and attempts to use the code (URL) again in a location other than the tag installation location, the service will not be provided (the service cannot be received) because the code has been used (obtained) before. This makes it possible to prevent fraudulent use (using a service without holding the user terminal 9 over the tag 8) by storing a code (URL) that has been used once and receiving the service. In other words, it is possible to prevent replay attacks. On the other hand, when a URL (code) is obtained by holding the user terminal 9 over the tag 8, a new (unused) code (URL) can be obtained because the tag 8 transmits a different code each time it is accessed. The code thus obtained is determined by the authentication server 1 to be a code for first use, and therefore the service can be provided (service can be received).

[0082] In this embodiment, if it is determined that the authentication code is not a code that has been previously obtained, a process for dispatching a taxi vehicle is executed, thereby making it possible to prevent the taxi dispatch service from being used in a location other than the location where the tag is installed. With this configuration, the taxi vehicle (driver) only needs to head near the location where the tag is installed, and it is possible to prevent the taxi vehicle from heading to a location other than the location where the tag is installed. This improves convenience for the taxi driver.

[0083] <Variation 1> In the embodiment described above, a determination is made as to whether the acquired code is a code used for the first time as a determination for authenticating the user (use of the tag 8), but other determinations may also be made. In this variation, an example is given in which a determination is made as to the user's location (the location of the user terminal 9) in addition to a determination as to whether the acquired code is a code used for the first time as a determination for authenticating the user. Note that in this variation, a description of the configuration common to the embodiment described above will be omitted, and only differences will be described. Note that the system configuration of this variation is generally similar to the system configuration in the embodiment described above with reference to FIG. 1, and therefore a description thereof will be omitted.

[0084] 5 is a diagram showing an outline of the functional configuration of the system according to this variation. In this variation, authentication server 1b includes an acquisition unit 21, a code storage unit 22, a code determination unit 23, a notification unit 24, a page data transmission unit 25, and an execution unit 26, as well as a tag position storage unit 27 and a position determination unit 28.

[0085] The tag position storage unit 27 stores position information relating to the installation location of one or more tags 8. In this embodiment, the tags 8 are installed in predetermined locations such as stations or facilities, and the tag position storage unit 27 stores position information of the locations where the tags 8 are installed in association with the tags 8. For example, the tag position storage unit 28 stores the unique ID of each tag 8 in association with the position information of the location where the tag 8 is installed. However, the position information relating to the installation location of the tag 8 is not limited to the position information of the location where the tag 8 is installed, and may be position information indicating the area where the tag 8 is installed, for example. For example, if the tag 8 is installed within a facility, position information indicating the entire facility (area) may be stored. Alternatively, position information indicating a range (area) within a predetermined distance from the installation location of the tag 8 may be stored.

[0086] The position determination unit 28 determines whether the position of the user terminal 9 (user) satisfies a predetermined condition. Specifically, the position determination unit 28 determines whether the positional relationship between the installation location of the tag 8 and the user terminal 9 satisfies a predetermined positional relationship condition, based on the position information regarding the installation location of the tag 8 stored in the tag position storage unit 27 and the position information of the user terminal 9 acquired by the acquisition unit 21. For example, the position determination unit 28 may determine whether the installation location of the tag 8 and the user terminal 9 are in the same area (e.g., in the same facility) based on the position information indicating the area where the tag 8 is installed and the position information of the user terminal 9. Furthermore, for example, the position determination unit 28 may determine whether the distance between the installation location of the tag 8 and the user terminal 9 satisfies a predetermined distance condition, based on the position information regarding the installation location of the tag 8 and the position information of the user terminal 9. As an example, the position determination unit 28 determines whether the distance between the installation location of the tag 8 and the user terminal 9 is equal to or shorter than a predetermined distance (e.g., several meters or shorter). Note that the determination may be made whether the distance is less than the predetermined distance, rather than equal to or shorter than the predetermined distance. In this way, it is determined whether the location where the tag 8 is installed and the user terminal 9 are in close proximity (not too far apart).

[0087] In this variation, the execution unit 26 executes processing to provide a predetermined service when it is determined that the acquired authentication code is not a code that has been acquired before and that the positional relationship between the installation location of the tag 8 and the user terminal 9 satisfies a predetermined positional relationship condition. For example, the execution unit 26 executes processing to provide a predetermined service when it is determined that the acquired authentication code is not a code that has been acquired before and that the distance between the installation location of the tag 8 and the user terminal 9 is equal to or less than a predetermined distance (or shorter). In this way, by using location information related to the installation location of the tag 8 rather than the current location information of the tag 8 during authentication, it is possible to prevent the tag 8 from being used in a location other than the installation location (installation area) of the tag 8, such as by taking the tag 8 home from the installation location. This makes it possible to prevent mischief, such as taking the tag 8 home.

[0088] FIG. 6 shows a flowchart and a communication sequence outlining the vehicle dispatch process flow according to this variation. The process shown in this flowchart is initiated when the user brings the user terminal 9 close to (holds over) the tag 8, for example. Note that the processes of steps S101 to S111 shown in FIG. 6 are generally similar to the processes of steps S101 to S111 shown in FIG. 3, and therefore detailed description thereof will be omitted. However, in step S102 in this variation, the location information of the user terminal 9 acquired by the location acquisition unit 65 is transmitted to the authentication server 1 by the transmission unit 62 together with the encrypted code. Note that the location information of the user terminal 9 is acquired in step S102, but may be acquired in step S101. Thus, in step S102, the authentication server 1 (by the acquisition unit 21) acquires the encrypted code and the location information. In this variation, if it is determined in step S106 that this is the first use (Yes in step S106), the process proceeds to step S201.

[0089] In step S201, it is determined whether the user position satisfies a condition. The position determination unit 28 determines whether the positional relationship between the installation location of the tag 8 and the user terminal 9 satisfies a predetermined positional relationship condition, using the position information of the user terminal 9 acquired in step S102 and the position information (position information related to the installation location of the tag 8 stored by the tag position storage unit 27) stored in association with the unique ID included in the decryption code acquired in step S103. If the predetermined positional relationship condition is satisfied (Yes in step S201), the process proceeds to step S108, and the page data is transmitted to the user terminal 9. On the other hand, if the predetermined positional relationship condition is not satisfied, for example, because the user terminal 9 is too far from the installation location of the tag 8 (No in step S201), the process proceeds to step S107, and an error is notified to the user terminal 9.

[0090] The processing from step S112 onwards (the processing from step S112 to step S126) according to this variation is generally similar to the processing shown in Fig. 4, and therefore description thereof will be omitted. However, since the location information of the user terminal 9 has already been transmitted in step S102, the location information does not need to be transmitted in step S114.

[0091] As in this variation, by determining whether the positional relationship between the installation location of the tag 8 and the user terminal 9 satisfies a predetermined positional relationship condition and performing processing to provide the service if the predetermined positional relationship condition is met, it is possible to prevent the tag 8 from being used in a location other than the installation location, such as by taking the tag 8 home and using it, thereby preventing mischief such as taking the tag 8 home. Furthermore, by performing processing to provide the service if the positional relationship between the installation location of the tag 8 and the user terminal 9 satisfies a predetermined positional relationship condition, it is possible to prevent the URL read from the tag 8 from being accessed, and to prevent the URL from being accessed and the service from being used in a location other than the installation location of the tag 8. As described above, this variation makes it possible to further prevent the service from being used in a location other than the installation location of the tag 8. Furthermore, by performing processing to provide the service if the positional relationship between the installation location of the tag 8 and the user terminal 9 satisfies a predetermined positional relationship condition, as in the embodiment described above, it is possible to prevent the taxi vehicle (driver) from heading to a location near the installation location of the tag, and to prevent the taxi vehicle (driver) from heading to a location other than the installation location of the tag. This improves convenience for taxi drivers.

[0092] <Variation 2> In the embodiment described above, the provision of a predetermined service is performed by the providing device 3, but the predetermined service may be performed by another device. For example, in the embodiment described above, the case where the dispatching device 3 performs a taxi dispatch service (dispatch instructions to a taxi vehicle (driver)) is exemplified, but the authentication server 1 may also perform the taxi dispatch service. In this variation, a case where the authentication server 1 determines a taxi vehicle (driver) to be sent to the user's location and issues a dispatch instruction to the taxi vehicle (in the case of automatic dispatch) is exemplified. Note that in this variation, explanation of the configuration common to the embodiment described above will be omitted, and differences will be explained.

[0093] FIG. 7 is a schematic diagram showing an outline of the hardware configuration of a system according to this variation. The system according to this embodiment includes an authentication server (authentication device) 1 connected to a network, a user terminal 9 connected so as to be able to communicate with the authentication server 1 via the network, and one or more tags 8. In this variation, when a user holds the user terminal 9 over the tag 8 and data read from the tag 8 is transmitted from the user terminal 9 to the authentication server 1, authentication is performed by the authentication server 1. Depending on the result of this authentication by the authentication server 1, the authentication server 1 issues dispatch instructions to a taxi vehicle, etc. Note that the hardware configurations of the authentication server 1 and the user terminal 9 in the system according to this variation are generally similar to the hardware configurations of the authentication server 1 and the user terminal 9 in the embodiment described above with reference to FIG. 1, and therefore description thereof will be omitted.

[0094] FIG. 8 is a diagram illustrating an outline of the functional configuration of a system according to this variation. The functional configuration of the authentication server 1 and the user terminal 9 in the system according to this variation is generally similar to the functional configuration of the authentication server 1 and the user terminal 9 in the embodiment described above with reference to FIG. 2, and therefore description thereof will be omitted. However, in this variation, the execution unit 26 determines a taxi vehicle to be dispatched (dispatched) and issues a dispatch instruction to the taxi vehicle as a process for dispatching a taxi vehicle. That is, in this variation, the execution unit 26 executes a process for providing a predetermined service (taxi dispatch service). For example, the execution unit 26 extracts a taxi vehicle that is closest to the user and is available for dispatch based on, for example, location information of the user terminal 9, location information of each taxi vehicle, operation information of each taxi vehicle, etc., and transmits a dispatch request to the extracted taxi vehicle.

[0095] FIG. 9 is a flowchart and communication sequence showing an overview of the dispatch processing flow according to this variation. Note that in this variation as well, the processing shown in FIG. 3 (processing of steps S101 to S111) is performed when the user brings the user terminal 9 close to (holds over) the tag 8, etc. The processing shown in the flowchart in FIG. 9 is started when it is determined in step S110 shown in FIG. 3 that page data has been received. The processing of steps S101 to S111 in this variation is generally similar to the processing of steps S101 to S111 in the embodiment described above with reference to FIG. 3, and therefore will not be described again.

[0096] In steps S301 to S303, a Web UI screen is displayed on the user terminal 9, and when input of the number of passengers and the like from the user is accepted on the Web UI screen, the input number of passengers and location information of the user terminal 9 are transmitted to the authentication server 1. The processing of steps S301 to S303 according to this variation is generally similar to the processing of steps S112 to S114 in the embodiment described above with reference to Fig. 4, and therefore description thereof will be omitted. Thereafter, the processing proceeds to steps S304 and S305.

[0097] In step S304, a message indicating that the vehicle dispatch request has been confirmed is displayed on the user terminal 9. The display control unit 63 displays the message indicating that the vehicle dispatch request has been confirmed (for example, a message such as "Request confirmed") via the output device 96. Note that the message may be displayed upon receiving a notification from the authentication server 1 that the vehicle dispatch request has been sent to the authentication server 1 in step S303, or that the vehicle dispatch request sent in step S303 has been received.

[0098] In step S305, the authentication server 1 determines a taxi vehicle to be dispatched and transmits a dispatch request. The execution unit 26 determines a taxi vehicle (driver) based on the information (dispatch request) such as the number of passengers received in step S303, and transmits a dispatch request to the taxi vehicle. The execution unit 26 extracts a dispatchable taxi vehicle closest to the user based on, for example, the location information of the user terminal 9, the location information of each taxi vehicle, and the operation information of each taxi vehicle received in step S303, and transmits a dispatch request to the extracted taxi vehicle. The dispatch request transmitted by the execution unit 26 includes information related to the dispatch request from the user (such as the number of passengers and the location information of the user terminal 9 received in step S303). Thereafter, the process proceeds to step S306 and step S308.

[0099] In steps S306 and S307, the authentication server 1 notifies the user terminal 9 that a vehicle search is in progress, and a message indicating that a vehicle search is in progress is displayed on the user terminal 9. The notification unit 24 notifies the user terminal 9 that a taxi vehicle is being searched for (step S306), and the display control unit 63 displays a message indicating that a taxi vehicle is being searched for (for example, a message such as "Searching for available driver") via the output device 96 (step S307).

[0100] In steps S308 to S310, the taxi vehicle sends a confirmation notification to the authentication server 1, and the authentication server 1 sends a dispatch instruction to the taxi vehicle and a dispatch notification to the user terminal 9. The taxi vehicle sends a notification to the authentication server 1 that it has confirmed the dispatch request sent in step S305 (a response that the taxi is available) (step S308). Then, the execution unit 26 sends a formal dispatch instruction to the taxi vehicle (step S309), and the notification unit 24 sends a notification to the user terminal 9 that the taxi has been dispatched (that the taxi is on its way) (step S310). The dispatch instruction sent by the execution unit 26 may include information related to the dispatch request from the user (such as the number of passengers received in step S303 and the location information of the user terminal 9). Thereafter, the process proceeds to steps S311 and S312.

[0101] In steps S311 and S312, a taxi heads to the user's location, and a message indicating that the taxi has been dispatched is displayed on the user terminal 9. Thereafter, the processing shown in this flowchart ends. Note that the processing in steps S311 to S312 is generally similar to the processing in steps S125 to S126 shown in FIG. 4, and therefore description thereof will be omitted. Note that in this variation, the authentication server 1 (execution unit 26) transmits a dispatch request to one taxi vehicle that is closest to the user and available for dispatch. However, this is not limited to this example, and the dispatch request may be transmitted to multiple taxi vehicles. For example, from the taxi vehicles under the management of the authentication server 1, one or more taxi vehicles that are close to the user (for example, within a predetermined distance from the user terminal 9) and available for dispatch (available) are extracted (identified), and the dispatch request is transmitted to the extracted one or more taxi vehicles. In this case, the authentication server 1 (execution unit 26) issues a dispatch instruction only to the taxi vehicle (driver) that first sent a confirmation notification (dispatch availability notification) to the authentication server 1.

[0102] As in this variation, by providing a service without going through the providing device 3, it is possible to provide the service automatically without manual operation. For example, as described above, by having the authentication server 1 determine a taxi vehicle that can be dispatched and issue a dispatch instruction to the taxi vehicle (execute a taxi dispatch service) without going through the dispatch device 3, it is possible to automatically dispatch a taxi vehicle without going through manual operation by an operator or the like. Note that the system according to the present disclosure may be implemented as an embodiment that combines Variation 1 and Variation 2. [Explanation of symbols]

[0103] 1 Authentication Server 3. Provision device (dispatch device) 9 User terminals

Claims

1. an acquisition means for acquiring, as an authentication code, a code acquired by an information processing terminal accessing a tag that transmits a different code each time the tag is accessed via short-range wireless communication, or a decrypted code obtained by performing a decryption process on the encrypted code if the code is an encrypted code; a code determination means for determining whether the authentication code acquired by the acquisition means is a code that has been acquired by the acquisition means before; and an execution means for executing a process for dispatching a taxi vehicle when it is determined that the acquired authentication code is not a code that has been acquired before. Information processing system.

2. a tag location storage means for storing location information relating to the installation location of a tag that transmits a different code each time it is accessed by short-range wireless communication; an acquisition means for acquiring, as an authentication code, the code acquired by an information processing terminal accessing the tag, or a decrypted code obtained by performing a decryption process on the code if the code is an encrypted code, and for acquiring location information of the information processing terminal; a code determination means for determining whether the authentication code acquired by the acquisition means is a code that has been acquired by the acquisition means before; a position determination means for determining whether or not a positional relationship between the tag installation location and the information processing terminal satisfies a predetermined positional relationship condition, based on the position information relating to the tag installation location stored in the tag position storage means and the position information of the information processing terminal acquired by the acquisition means; and an execution means for executing a process to provide a predetermined service when it is determined that the acquired authentication code is not a code that has been acquired before and that the positional relationship between the installation location of the tag and the information processing terminal satisfies the predetermined positional relationship condition. Information processing system.

3. the position determination means determines whether or not the distance between the tag installation location and the information processing terminal satisfies a predetermined distance condition; the execution means executes a process for providing the predetermined service when it is determined that the acquired authentication code is not a code that has been acquired before and that the distance between the installation location of the tag and the information processing terminal satisfies a predetermined distance condition. The information processing system according to claim 2 .

4. the position determination means determines whether or not the distance between the tag installation location and the information processing terminal is equal to or less than a predetermined distance; the execution means executes a process for providing the predetermined service when it is determined that the acquired authentication code is not a code that has been acquired before and that the distance between the installation location of the tag and the information processing terminal is equal to or shorter than a predetermined distance. The information processing system according to claim 3 .

5. the execution means executes a process for arranging a taxi vehicle as the process for providing the predetermined service. The information processing system according to claim 2 .

6. The execution means, as the process for arranging the taxi vehicle, instructs a taxi vehicle arrangement device, or determines a taxi vehicle to be arranged and instructs the taxi vehicle to be arranged.

6. The information processing system according to claim 1 or 5.

7. The authentication code is a code including a combination of a unique ID of the tag and data that can identify access to the tag. The information processing system according to any one of claims 1 to 5.

8. The data that can identify access to the tag is data corresponding to the number of times the tag has been accessed. The information processing system according to claim 7 .

9. One or more computers an acquisition step of acquiring, as an authentication code, the code acquired by an information processing terminal accessing a tag that transmits a different code each time it is accessed via short-range wireless communication, or, if the code is an encrypted code, acquiring a decrypted code obtained by performing a decryption process on the code; a code determination step of determining whether the authentication code acquired in the acquisition step is a code that has been acquired in the acquisition step before; an execution step of executing a process for dispatching a taxi vehicle when it is determined that the acquired authentication code is not a code that has been acquired before; How to do it.

10. one or more computers, an acquisition means for acquiring, as an authentication code, a code acquired by an information processing terminal accessing a tag that transmits a different code each time the tag is accessed via short-range wireless communication, or a decrypted code obtained by performing a decryption process on the encrypted code if the code is an encrypted code; a code determination means for determining whether the authentication code acquired by the acquisition means is a code that has been acquired by the acquisition means before; an execution means for executing a process for dispatching a taxi vehicle when it is determined that the acquired authentication code is not a code that has been acquired before; A program that functions as a

Images