WO2017154467A1 - 識別情報提供システム、識別情報提供装置、識別情報提供プログラムおよび識別情報提供方法 - Google Patents
識別情報提供システム、識別情報提供装置、識別情報提供プログラムおよび識別情報提供方法 Download PDFInfo
- Publication number
- WO2017154467A1 WO2017154467A1 PCT/JP2017/005097 JP2017005097W WO2017154467A1 WO 2017154467 A1 WO2017154467 A1 WO 2017154467A1 JP 2017005097 W JP2017005097 W JP 2017005097W WO 2017154467 A1 WO2017154467 A1 WO 2017154467A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- identification information
- beacon
- list
- content
- specific
- Prior art date
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/02—Protecting privacy or anonymity, e.g. protecting personally identifiable information [PII]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/06—Authentication
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/04—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
- H04L63/0428—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
- H04L63/0876—Network architectures or network communication protocols for network security for authentication of entities based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/32—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols including means for verifying the identity or authority of a user of the system or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/12—Detection or prevention of fraud
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W12/00—Security arrangements; Authentication; Protecting privacy or anonymity
- H04W12/60—Context-dependent security
- H04W12/69—Identity-dependent
- H04W12/73—Access point logical identity
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W4/00—Services specially adapted for wireless communication networks; Facilities therefor
- H04W4/80—Services using short range communication, e.g. near-field communication [NFC], radio-frequency identification [RFID] or low energy communication
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W84/00—Network topologies
- H04W84/02—Hierarchically pre-organised networks, e.g. paging networks, cellular networks, WLAN [Wireless Local Area Network] or WLL [Wireless Local Loop]
- H04W84/10—Small scale networks; Flat hierarchical networks
- H04W84/12—WLAN [Wireless Local Area Networks]
Definitions
- the present invention relates to an identification information providing system, an identification information providing device, an identification information providing program, and an identification information providing method.
- a beacon is used as a method of knowing the position of a mobile terminal in an indoor environment where GPS radio waves do not reach.
- a signal including information such as a beacon ID associated with position information is transmitted from a beacon that emits a broadcast signal or an ultrasonic signal using radio waves of BLE (Bluetooth Low Energy), and the mobile terminal is based on the information received from the beacon.
- Get location information Such acquisition of position information is used for a content service that provides information according to the position of the user. For example, a plurality of beacons are installed on an area ceiling of an indoor facility such as a shopping mall, and a beacon ID is transmitted from each. Then, the mobile terminal such as a smartphone that has received the beacon ID notifies the content server of the beacon ID received via the network, and the position information itself associated with the beacon ID, the guidance information related to the location, Get content such as coupons.
- BLE Bluetooth Low Energy
- beacons that imitates signals transmitted from beacons are important in the provision of information using beacons described above.
- the ultrasonic signal is recorded, reproduced at an arbitrary location at a later date, and received by the mobile terminal, whereby content that cannot be originally acquired can be obtained. It is also conceivable that the acquisition of normal content on another person's mobile terminal may be confused.
- the present invention has been proposed in view of the above-mentioned conventional problems, and an object thereof is to prevent spoofing of identification information in a beacon or the like.
- transmission means for transmitting a specific signal including identification information, setting and changing the identification information, and managing the set or changed specific identification information
- a receiving means capable of receiving the specific signal and capable of synchronizing by acquiring the specific identification information from the managing means, wherein the receiving means The result of collating the specific identification information with the received specific signal is used for determining the suitability of the transmission means.
- spoofing of identification information in a beacon or the like can be prevented.
- FIG. (1) which shows the example of a change of the various data in a 1st process example.
- FIG. (2) which shows the example of a change of the various data in a 1st process example.
- FIG. (The 3) which shows the example of a change of the various data in a 1st process example.
- FIG. 3. which shows the example of a change of the various data in a 1st process example.
- FIG. (4) which shows the example of a change of the various data in a 1st process example. It is a sequence diagram which shows the 2nd process example. It is FIG. (1) which shows the example of the change of the various data in a 2nd process example. It is FIG. (2) which shows the example of the change of the various data in a 2nd process example. It is FIG. (3) which shows the example of a change of the various data in a 2nd process example. It is FIG. (4) which shows the example of a change of the various data in a 2nd process example. It is a sequence diagram which shows the 3rd process example. It is FIG. (1) which shows the example of the change of the various data in a 3rd process example.
- FIG. 2 which shows the example of the change of the various data in a 3rd process example.
- FIG. 3 which shows the example of a change of the various data in a 3rd process example.
- FIG. (4) which shows the example of a change of the various data in a 3rd process example.
- FIG. (1) which shows the example of the change of the various data in a 4th process example.
- FIG. (2) which shows the example of a change of the various data in a 4th process example.
- FIG. (The 3) which shows the example of a change of the various data in a 4th process example.
- FIG. 3 which shows the example of a change of the various data in a 4th process example. It is FIG.
- FIG. 4 which shows the example of a change of the various data in a 4th process example.
- FIG. (5) which shows the example of a change of the various data in a 4th process example.
- FIG. (5) which shows the example of a change of the various data in a 4th process example.
- FIG. (5) which shows the example of a change of the various data in a 4th process example.
- FIG. (5) which shows the example of a change of the various data in a 4th process example.
- FIG. a sequence diagram which shows the 5th process example.
- FIG. (1) which shows the example of the change of the various data in a 5th process example.
- FIG. (2) which shows the example of a change of the various data in a 5th process example.
- FIG. (The 3) which shows the example of a change of the various data in a 5th process example.
- FIG. (4) which shows the example of a change of the various data in a 5th process example.
- FIG. 1 is a diagram showing a configuration example of a system according to an embodiment of the present invention.
- a plurality of beacons 2 are installed on an area ceiling of an indoor facility 1 such as a shopping mall.
- the beacon 2 is an information transmission device that can transmit a broadcast signal and an ultrasonic signal using radio waves of BLE (Bluetooth Low Energy).
- a content server 3 is provided in the indoor facility 1 or at an arbitrary place, and the beacon 2 and the content server 3 are communicably connected via a wired or wireless network 4.
- the content server 3 manages the setting / change of the beacon ID transmitted from the beacon 2, and holds contents such as position information (latitude / longitude information), map information, notification information, and coupons associated with the beacon ID.
- a mobile terminal 5 such as a smartphone, a PC (Personal Computer), or a wearable device possessed by a user in the indoor facility 1 can receive signals such as radio waves or ultrasonic waves transmitted from the beacon 2. Further, the mobile terminal 5 can be connected to the content server 3 via the network 4 as necessary, and acquires the content corresponding to the beacon ID received from the beacon 2.
- FIG. 2 is a diagram showing an example of the functional configuration of each device.
- the beacon 2 has an ID transmission unit 21 that transmits individually set / changed beacon IDs as radio wave signals and ultrasonic signals.
- the content server 3 includes an ID management unit 31 that manages setting / changing of a beacon ID for the beacon 2 and a content management unit 32 that manages content associated with the beacon ID.
- the mobile terminal 5 receives a beacon ID, determines whether or not the beacon ID is appropriate, and obtains an ID / content management unit 51 that performs acquisition of content associated with the beacon ID, and an ID list that lists valid beacon IDs. It has an ID list holding unit 52 for holding, and a content holding unit 53 for holding acquired content.
- FIG. 3 is a diagram illustrating a hardware configuration example of the beacon 2.
- a beacon 2 includes a CPU (Central Processing Unit) 201, a ROM (Read Only Memory) 202, a RAM (Random Access Memory) 203, and an HDD (Hard Disk Drive) / SSD connected to each other via a bus 200. (Solid State Drive) 204 is provided.
- the CPU 201 performs overall control of the operation of the beacon 2 by executing a program stored in the ROM 202 or the HDD / SSD 204 or the like using the RAM 203 as a work area.
- the beacon 2 includes an input / output I / F (Interface) 205, a wireless LAN AP (Local Area Network Access Point) unit 206, a BLE communication unit 207, and a speaker unit 208.
- the input / output I / F 205 is an interface that accepts user operations and the like.
- the wireless LAN AP unit 206 is an interface for communicating with other information processing apparatuses via the wireless LAN.
- the BLE communication unit 207 is a part that performs BLE communication. In this embodiment, the BLE communication unit 207 uses transmission of broadcast signals by radio waves.
- the speaker unit 208 is a part that transmits an ultrasonic signal. The speaker unit 208 can be omitted when only the BLE transmission function is used, and the BLE communication unit 207 can be omitted when only the ultrasonic wave is used.
- the function (ID transmission unit 21) of the beacon 2 described in FIG. 2 is realized by executing a predetermined program in the CPU 201.
- the program may be acquired via a recording medium, may be acquired via a network, or may be embedded in a ROM.
- the ID transmission unit 21 of the beacon 2 functions as a reception function unit (a wireless LAN AP unit 206 shown in FIG. 3 or a wired LAN unit not shown) that accepts a beacon ID change request from the content server 3, and stores and holds a beacon ID.
- a functional unit for example, HDD / SSD 204, RAM 203, and ROM 202 shown in FIG. 3) is also included.
- FIG. 4 is a diagram illustrating a hardware configuration example of the content server 3.
- the content server 3 includes a CPU 301, a ROM 302, a RAM 303, and an HDD / SSD 304 that are connected to each other via a bus 300.
- the CPU 301 performs overall control of the operation of the content server 3 by executing a program stored in the ROM 302 or the HDD / SSD 304 or the like using the RAM 303 as a work area.
- the content server 3 includes an operation unit 305, a display unit 306, a communication unit 307, and an input / output I / F 308.
- the operation unit 305 is a part that receives a user operation.
- the display unit 306 is a part that displays an operation menu, a processing state, and the like to the user.
- the communication unit 307 is a part that communicates with other information processing apparatuses.
- the input / output I / F 308 is an interface for inputting / outputting data to / from an external device or the like.
- the function of the content server 3 described in FIG. 2 is realized by executing a predetermined program in the CPU 301.
- the program may be acquired via a recording medium, may be acquired via a network, or may be embedded in a ROM.
- FIG. 5 is a diagram illustrating a hardware configuration example of the mobile terminal 5.
- the mobile terminal 5 includes a CPU 501, a ROM 502, a RAM 503, and an HDD / SSD 504 connected to each other via a bus 500.
- the CPU 501 comprehensively controls the operation of the mobile terminal 5 by executing a program stored in the ROM 502 or the HDD / SSD 504 using the RAM 503 as a work area.
- the mobile terminal 5 includes a display unit 505, a camera unit 506, a microphone unit 507, a speaker unit 508, a wireless communication unit 509, an input / output I / F 510, a wireless LAN communication unit 511, and a BLE communication unit 512.
- a display unit 505 is a part that displays an operation menu, a processing state, and the like to the user.
- the camera unit 506 is a part that performs shooting with a built-in camera.
- the microphone unit 507 is a part that acquires sound using a built-in microphone.
- the speaker unit 508 is a part that outputs sound.
- the wireless communication unit 509 is a part that performs voice communication or data communication.
- the input / output I / F 510 is an interface for inputting / outputting data to / from an external device or the like.
- the wireless LAN communication unit 511 is a part that communicates with other devices via a wireless LAN.
- the BLE communication unit 512 is a part that communicates with other devices by BLE.
- the functions of the mobile terminal 5 described in FIG. 2 are realized by the CPU 501 executing a predetermined program.
- the program may be acquired via a recording medium, may be acquired via a network, or may be embedded in a ROM.
- FIG. 6 is a sequence diagram showing a first processing example, and the beacon ID included in a signal transmitted from the beacon 2 by radio waves or ultrasonic waves is periodically changed from the content server 3 via the network in order to prevent spoofing. The process and the process at the time of subsequent operation are shown.
- the ID management unit 31 of the content server 3 performs a beacon ID change process at a predetermined timing.
- the implementation timing is regularly implemented in accordance with the security requirement of what level of security is required. For example, it is conceivable to automatically execute every 24 hours every day at midnight when there is no system user.
- the ID management unit 31 changes the ID list on the server side (step S101).
- the ID list after the change is managed and set so that the ID list before the change and the beacon ID do not overlap.
- the ID list is a list assuming that there are a plurality of beacons 2, but when there is only one beacon 2, it is not necessary to hold the list as a list.
- FIG. 7A shows an example of the ID list before the change and the ID list after the change, and the beacon IDs “1111” “2222” with respect to the beacon numbers (No) “1” “2” “3” before the change. “3333” is changed to “5555”, “6666”, and “7777”, respectively.
- the beacon ID format (number of digits, characters used, etc.) is not limited to that shown in the figure.
- the ID management unit 31 requests the content management unit 32 to change the content list in which the content is associated with the beacon ID (step S102), and the content management unit 32 manages the managed content. Change the list to match the changed ID list. In addition, in the case of the initial setting, it is the same except that it is empty before the change. Further, the content list is assumed to have a plurality of beacons 2, but when there is only one beacon 2, it is not necessary to hold it as a list.
- FIG. 7B shows an example of the content list before the change and the content list after the change, and the content IDs “AAAA”, “BBBB”, and “CCCC” are assigned to the beacon IDs “1111”, “2222”, and “3333” before the change, respectively.
- the linked contents are changed so that the content IDs “AAAA”, “BBBB”, and “CCCC” are associated with the beacon IDs “5555”, “6666”, and “7777”, respectively.
- the content ID is a unique number that uniquely represents the content. Although the content itself may be associated instead of the content ID, it is described as an ID for convenience.
- the ID management unit 31 requests the beacon 2 (the ID transmission unit 21) to change the beacon ID (step S103), and the beacon 2 (the ID transmission unit 21) Change the ID.
- the same processing is performed for each beacon 2.
- FIG. 7C shows an example of the beacon ID before the change and the beacon ID after the change in the beacon 2, and the beacon 2 (corresponding to the beacon number “1”) whose beacon ID is “1111” before the change is The beacon ID is changed to “5555”.
- the mobile terminal 5 receives a signal including the beacon ID from the beacon 2 during operation, and the signal and the ID list in the ID list holding unit 52 cannot be normally verified.
- the ID list held in the mobile terminal 5 is synchronized with the content server 3 side (overwritten (updated) with information on the content server 3 side). As a result, synchronization can be automatically performed when necessary.
- the ID transmission unit 21 of the beacon 2 transmits a radio wave signal or an ultrasonic signal including its own beacon ID (step S111).
- the transmission of this signal may be performed intermittently or continuously.
- step S112 when the ID / content management unit 51 of the mobile terminal 5 receives the signal transmitted from the beacon 2, is the beacon ID included in the received signal included in the ID list held in the ID list holding unit 52? It is confirmed whether or not (step S112).
- the case where the ID list does not exist is a case where the mobile terminal 5 first receives a signal from the beacon 2.
- the beacon ID set in the beacon 2 is changed and becomes a new beacon ID, or a malicious third party It is assumed that the beacon ID being impersonated is received (including the case where the impersonating person is receiving).
- the ID / content management unit 51 requests and acquires an ID list from the ID management unit 31 of the content server 3 (step S113), and overwrites and updates the ID list of the ID list holding unit 52 with the acquired ID list.
- FIG. 7D shows an example of the ID list before the change and the ID list after the change in the mobile terminal 5, and is the same as FIG. 7A.
- the ID / content management unit 51 confirms again whether or not the beacon ID included in the signal received from the beacon 2 is included in the ID list held in the ID list holding unit 52. (Step S115).
- the ID / content management unit 51 acquires content associated with the corresponding beacon ID from the content holding unit 53 (step S116).
- the ID / content management unit 51 designates the beacon ID to the content management unit 32 of the content server 3.
- the content is requested (step S117).
- the content management unit 32 responds to the mobile terminal 5 with content corresponding to the specified beacon ID based on the content list.
- the ID / content management unit 51 associates the acquired content with the content ID and saves (caches) it in the content holding unit 53 (step S118).
- the ID / content management unit 51 leads to processing in accordance with the contents of the service, such as presenting the acquired content to the user of the mobile terminal 5.
- the ID / content management unit 51 may identify and notify the content server 3 of a beacon ID that may be spoofed. In this case, the content server 3 may make a black list so that the beacon ID is not used immediately or in the future.
- the content server stores the ID list held in the mobile terminal 5 at the timing when the mobile terminal 5 determines that a predetermined time has elapsed since the previous acquisition of the ID list during a predetermined user operation.
- Processing to synchronize with the third side acquisition of the ID list on the content server 3 side and update the ID list of the ID list holding unit 52) is performed. Thereby, the frequency of a synchronous process can be made low and a processing load can be reduced.
- FIG. 8 is a sequence diagram showing a second processing example.
- the ID management unit 31 of the content server 3 performs a beacon ID change process at a predetermined timing.
- the implementation timing is regularly implemented in accordance with the security requirement of what level of security is required. For example, it is conceivable to automatically execute every 24 hours every day at midnight when there is no system user.
- the ID management unit 31 changes the server-side ID list (step S201).
- the ID list after the change is managed and set so that the ID list before the change and the beacon ID do not overlap.
- the ID list is a list assuming that there are a plurality of beacons 2, but when there is only one beacon 2, it is not necessary to hold the list as a list.
- FIG. 9A shows an example of an ID list before change and an ID list after change.
- the beacon ID format (number of digits, characters used, etc.) is not limited to that shown in the figure.
- the ID management unit 31 requests the content management unit 32 to change the content list in which the content is linked to the beacon ID (step S202), and the content management unit 32 manages the managed content. Change the list to match the changed ID list.
- the content list is assumed to have a plurality of beacons 2, but when there is only one beacon 2, it is not necessary to hold it as a list.
- FIG. 9B shows an example of the content list before the change and the content list after the change.
- the ID management unit 31 requests the ID transmission unit 21 of the beacon 2 to change the beacon ID (step S203), and the ID transmission unit 21 of the beacon 2 changes its own beacon ID. .
- the same processing is performed for each beacon 2.
- FIG. 9C shows an example of the beacon ID before the change in the beacon 2 and the beacon ID after the change.
- the user has activated the ID / content management unit 51 (activation of the application constituting the ID / content management unit 51) in the mobile terminal 5 during operation (step S211).
- the activated ID / content management unit 51 determines whether or not a predetermined time or more has elapsed since the last update time of the ID list, and performs the following processing when determining that it has elapsed.
- the predetermined elapsed time is desirably matched with the time interval for changing the ID list in the content server 3.
- the update date and time is recorded in the ID list, and the elapsed time is determined by comparing the update date and time with the current date and time.
- the ID / content management unit 51 requests and acquires an ID list from the ID management unit 31 of the content server 3 (step S212), and overwrites and updates the ID list of the ID list holding unit 52 with the acquired ID list. (Step S213).
- FIG. 9D shows an example of the ID list before the change and the ID list after the change in the mobile terminal 5, and shows that the elapsed time is determined to have passed, for example, 24 hours and updated. Yes.
- the ID transmission unit 21 of the beacon 2 transmits a radio wave signal or an ultrasonic signal including its own beacon ID (step S ⁇ b> 221), and the ID / content management unit 51 of the mobile terminal 5
- the signal transmitted from is received, it is confirmed whether or not the beacon ID included in the received signal is included in the ID list held in the ID list holding unit 52 (step S222).
- the ID / content management unit 51 acquires content associated with the corresponding beacon ID from the content holding unit 53 (step S223).
- the ID / content management unit 51 designates the beacon ID to the content management unit 32 of the content server 3.
- the content is requested (step S224).
- the content management unit 32 responds to the mobile terminal 5 with content corresponding to the specified beacon ID based on the content list.
- the ID / content management unit 51 associates the acquired content with the content ID and saves (caches) the content in the content holding unit 53 (step S225).
- the ID / content management unit 51 leads to processing in accordance with the contents of the service, such as presenting the acquired content to the user of the mobile terminal 5.
- the ID / content management unit 51 may identify and notify the content server 3 of a beacon ID that may be spoofed. In this case, the content server 3 may make a blacklist so that the beacon ID is not used in the future.
- the content server 3 side stores the ID list held in the mobile terminal 5 at the timing when the mobile terminal 5 determines that a predetermined time has elapsed since the previous acquisition of the ID list during a predetermined user operation. The process to synchronize with.
- the push-type ID list held in the mobile terminal 5 is synchronized with the content server 3 side (from the content server 3 side, the ID list is updated).
- the process of transmitting and updating the ID list of the ID list holding unit 52 is performed. Thereby, the frequency of a synchronous process can be made low and a processing load can be reduced.
- FIG. 10 is a sequence diagram showing a third processing example.
- the ID management unit 31 of the content server 3 performs a beacon ID change process at a predetermined timing.
- the implementation timing is regularly implemented in accordance with the security requirement of what level of security is required. For example, it is conceivable to automatically execute every 24 hours every day at midnight when there is no system user.
- the ID management unit 31 changes the ID list on the server side (step S301).
- the ID list after the change is managed and set so that the ID list before the change and the beacon ID do not overlap.
- the ID list is a list assuming that there are a plurality of beacons 2, but when there is only one beacon 2, it is not necessary to hold the list as a list.
- FIG. 11A shows an example of an ID list before change and an ID list after change.
- the beacon ID format (number of digits, characters used, etc.) is not limited to that shown in the figure.
- the ID management unit 31 requests the content management unit 32 to change the content list in which the content is linked to the beacon ID (step S302), and the content management unit 32 manages the managed content. Change the list to match the changed ID list.
- the content list is assumed to have a plurality of beacons 2, but when there is only one beacon 2, it is not necessary to hold it as a list.
- FIG. 11B shows an example of the content list before the change and the content list after the change.
- the ID management unit 31 requests the ID transmission unit 21 of the beacon 2 to change the beacon ID (step S303), and the ID transmission unit 21 of the beacon 2 changes its own beacon ID.
- FIG. 11C shows an example of the beacon ID before the change in the beacon 2 and the beacon ID after the change.
- the ID management unit 31 transmits the changed ID list (push notification, mail transmission, etc.) to the mobile terminal 5 (the ID / content management unit 51) (step S304).
- the ID / content management unit 51 overwrites and updates the ID list in the ID list holding unit 52 with the received ID list (step S305).
- FIG. 11D shows an example of the ID list before change and the ID list after change in the mobile terminal 5.
- the ID transmission unit 21 of the beacon 2 transmits a radio wave signal or an ultrasonic signal including its own beacon ID (step S ⁇ b> 311), and the ID / content management unit 51 of the mobile terminal 5
- the signal transmitted from is received, it is confirmed whether or not the beacon ID included in the received signal is included in the ID list held in the ID list holding unit 52 (step S312).
- the ID / content management unit 51 acquires content associated with the corresponding beacon ID from the content holding unit 53 (step S313).
- the ID / content management unit 51 designates the beacon ID to the content management unit 32 of the content server 3.
- the content is requested (step S314).
- the content management unit 32 responds to the mobile terminal 5 with content corresponding to the specified beacon ID based on the content list.
- the ID / content management unit 51 associates the acquired content with the content ID and stores (caches) it in the content holding unit 53 (step S315).
- the ID / content management unit 51 leads to processing in accordance with the contents of the service, such as presenting the acquired content to the user of the mobile terminal 5.
- the ID / content management unit 51 may identify and notify the content server 3 of a beacon ID that may be spoofed. In this case, the content server 3 may make a blacklist so that the beacon ID is not used in the future.
- the ID list provided to the mobile terminal 5 is one for each change.
- a plurality of ID lists including future changes are included. A list is provided. Accordingly, even when the mobile terminal 5 cannot perform the synchronization process with the content server 3, an appropriate process can be performed if the ID list provided in advance can be used.
- FIG. 12 is a sequence diagram showing a fourth processing example.
- FIG. 12 can apply similarly to the 2nd, 3rd process example.
- the ID management unit 31 of the content server 3 performs a beacon ID change process at a predetermined timing.
- the implementation timing is regularly implemented in accordance with the security requirement of what level of security is required. For example, it is conceivable to automatically execute every 24 hours every day at midnight when there is no system user.
- the current ID list is held, and the ID list for the next and subsequent changes is held.
- the ID list after the change is managed and set so that the ID list before the change and the beacon ID do not overlap.
- the ID list is a list assuming that there are a plurality of beacons 2, but when there is only one beacon 2, it is not necessary to hold the list as a list.
- the ID management unit 31 changes the current ID list on the server side in accordance with the validity period of the ID list (step S401).
- FIG. 13B shows an example of the ID list before the change and the ID list after the change.
- the ID management unit 31 requests the content management unit 32 to change the content list in which the content is linked to the beacon ID (step S402), and the content management unit 32 manages the managed content. Change the list to match the changed ID list. Further, the content list is assumed to have a plurality of beacons 2, but when there is only one beacon 2, it is not necessary to hold it as a list.
- FIG. 13C shows an example of the content list before the change and the content list after the change.
- the ID management unit 31 requests the ID transmission unit 21 of the beacon 2 to change the beacon ID (step S403), and the ID transmission unit 21 of the beacon 2 changes its own beacon ID. .
- the same processing is performed for each beacon 2.
- FIG. 13D shows an example of the beacon ID before the change in the beacon 2 and the beacon ID after the change. If the beacon 2 has a function for determining the current date and time and changing its own beacon ID, the content server 3 provides the beacon 2 with a plurality of ID lists including future changes. You may do it. In this case, even when the beacon ID cannot be set from the content server 3 to the beacon 2, if the ID list provided in advance can be used, an appropriate process can be performed.
- the ID transmission unit 21 of the beacon 2 transmits a radio wave signal or an ultrasonic signal including its own beacon ID (step S411).
- the transmission of this signal may be performed intermittently or continuously.
- step S412 when the ID / content management unit 51 of the mobile terminal 5 receives the signal transmitted from the beacon 2, is the beacon ID included in the received signal included in the ID list held in the ID list holding unit 52? It is confirmed whether or not (step S412).
- the case where the ID list does not exist is a case where the mobile terminal 5 first receives a signal from the beacon 2.
- the beacon ID set in the beacon 2 is changed and becomes a new beacon ID, or a malicious third party It is assumed that the beacon ID being impersonated is received (including the case where the impersonating person is receiving).
- the ID / content management unit 51 requests and acquires an ID list from the ID management unit 31 of the content server 3 (step S413). At this time, a plurality of ID lists to be acquired are included including future changes. Note that only the unprovided ID list may be acquired by informing the content server 3 of the expiration date of the acquired ID list on the mobile terminal 5 side.
- the ID / content management unit 51 updates the ID list holding unit 52 with the acquired ID list (step S414).
- a list having a current date and time within the valid period is a current valid ID list.
- FIG. 13E shows an example of the ID list before change and the ID list after change in the mobile terminal 5.
- the ID / content management unit 51 confirms again whether or not the beacon ID included in the signal received from the beacon 2 is included in the ID list held in the ID list holding unit 52. (Step S415).
- the ID / content management unit 51 acquires content associated with the corresponding beacon ID from the content holding unit 53 (step S416).
- the ID / content management unit 51 designates the beacon ID to the content management unit 32 of the content server 3.
- the content is requested (step S417).
- the content management unit 32 responds to the mobile terminal 5 with content corresponding to the specified beacon ID based on the content list.
- the ID / content management unit 51 associates the acquired content with the content ID and saves (caches) the content in the content holding unit 53 (step S418).
- the ID / content management unit 51 leads to processing in accordance with the contents of the service, such as presenting the acquired content to the user of the mobile terminal 5.
- the ID / content management unit 51 may identify and notify the content server 3 of a beacon ID that may be spoofed. In this case, the content server 3 may make a blacklist so that the beacon ID is not used in the future.
- the beacon ID in the ID list is used as the beacon ID transmitted from the beacon 2 as it is, and at the time of change, the beacon ID is changed so that there is no duplication. Therefore, there is a concern that the beacon ID candidates may be exhausted, and the contents are easily analyzed. Therefore, in the fifth processing example, the beacon ID of the ID list is expressed by combining the basic ID and the description of the encryption method, and the basic ID is encrypted from the beacon 2 according to the description encryption method. The description (encryption ID) and the description of the encryption method are transmitted. As a result, it is only necessary to change the encryption method while keeping the basic ID fixed, so that the beacon ID can be changed without worrying about exhaustion or analysis.
- FIG. 14 is a sequence diagram showing a fifth processing example. Although the case where the present invention is applied to the first processing example will be described, the present invention can be similarly applied to the second to fourth processing examples.
- the ID management unit 31 of the content server 3 performs a beacon ID change process at a predetermined timing.
- the implementation timing is regularly implemented in accordance with the security requirement of what level of security is required. For example, it is conceivable to automatically execute every 24 hours every day at midnight when there is no system user.
- the ID management unit 31 changes the server-side ID list (step S501).
- the ID list is a list assuming that there are a plurality of beacons 2, but when there is only one beacon 2, it is not necessary to hold the list as a list.
- the beacon ID in the ID list in this processing example is a combination of the basic ID and the description of the encryption method.
- the ID list can be changed without duplication.
- the basic ID may be changed together.
- FIG. 15A shows an example of the ID list before the change and the ID list after the change, and the beacon IDs “1111X” “2222X” with respect to the beacon numbers (No) “1” “2” “3” before the change.
- “3333X” is changed to “1111Y”, “2222Y”, and “3333Y”, respectively.
- “1111”, “2222”, and “3333” are basic IDs
- “X” and “Y” are descriptions of encryption methods.
- the description of the encryption method includes a description for specifying an encryption algorithm and an encryption key. When specifying the encryption algorithm, only the encryption key may be used. Further, although the encryption method is uniformly changed from “X” to “Y”, the encryption method may be changed for each beacon 2.
- the ID management unit 31 requests the content management unit 32 to change the content list in which the content is associated with the beacon ID (step S502), and the content management unit 32 manages the managed content. Change the list to match the changed ID list. Further, the content list is assumed to have a plurality of beacons 2, but when there is only one beacon 2, it is not necessary to hold it as a list.
- FIG. 15B shows an example of the content list before the change and the content list after the change, and the content IDs “AAAA”, “BBBB”, and “CCCC” are assigned to the beacon IDs “1111X”, “2222X”, and “3333X” before the change, respectively.
- the linked contents are changed so that the content IDs “AAAA”, “BBBB”, and “CCCC” are associated with the beacon IDs “1111Y”, “2222Y”, and “3333Y”, respectively.
- the ID management unit 31 requests the ID transmission unit 21 of the beacon 2 to change the beacon ID (step S503), and the ID transmission unit 21 of the beacon 2 changes its own beacon ID. .
- the operation is to change only the encryption method, only the description of the encryption method may be notified to the beacon 2.
- FIG. 15C shows an example of the beacon ID before the change and the beacon ID after the change in the beacon 2, and the basic ID (base) before the change is “1111” and the encryption method is “X”.
- the beacon 2 (corresponding to the beacon number “1”) is changed to “Y” while the basic ID (base) remains “1111”.
- FIG. 15C also shows the encrypted ID after the basic ID is encrypted by the encryption method.
- the ID transmission unit 21 of the beacon 2 encrypts the basic ID with the encryption method and transmits the radio signal including the encryption ID and the description of the encryption method.
- a sound wave signal is transmitted (step S511). The transmission of this signal may be performed intermittently or continuously.
- the encryption ID is described based on the encryption ID and the description of the encryption method included in the received signal.
- the decryption method is decrypted, and the decrypted ID (corresponding to the basic ID) and the description of the encryption method are combined as a beacon ID (step S512).
- the ID / content management unit 51 confirms whether or not the generated beacon ID is included in the ID list held in the ID list holding unit 52 (step S513).
- the following processing is performed.
- the case where the ID list does not exist is a case where the mobile terminal 5 first receives a signal from the beacon 2. Also, when the generated beacon ID does not exist in the ID list, the encryption method set in the beacon 2 has been changed to become a new beacon ID, or a malicious third It is assumed that the person who received the beacon ID being impersonated (including the case where the person impersonating the person is receiving).
- the ID / content management unit 51 requests and acquires an ID list from the ID management unit 31 of the content server 3 (step S514), and overwrites and updates the ID list of the ID list holding unit 52 with the acquired ID list. (Step S515).
- FIG. 15D shows an example of the ID list before change and the ID list after change in the mobile terminal 5.
- the ID / content management unit 51 confirms again whether the beacon ID generated from the signal received from the beacon 2 is included in the ID list held in the ID list holding unit 52. (Step S516).
- the ID / content management unit 51 acquires content associated with the corresponding beacon ID from the content holding unit 53 (step S517).
- the ID / content management unit 51 designates the beacon ID to the content management unit 32 of the content server 3.
- the content is requested (step S518).
- the content management unit 32 responds to the mobile terminal 5 with content corresponding to the specified beacon ID based on the content list.
- the ID / content management unit 51 associates the acquired content with the content ID and saves (caches) it in the content holding unit 53 (step S519).
- the ID / content management unit 51 leads to processing in accordance with the contents of the service, such as presenting the acquired content to the user of the mobile terminal 5.
- the ID / content management unit 51 may identify and notify the content server 3 of a beacon ID that may be spoofed. In this case, the content server 3 may make a blacklist so that the beacon ID is not used in the future.
- spoofing of identification information in a beacon or the like can be prevented.
- the beacon ID is an example of “identification information”.
- the beacon 2 is an example of “transmitting means”.
- the content server 3 is an example of “management means”.
- the mobile terminal 5 is an example of a “reception unit”.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Hardware Design (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Power Engineering (AREA)
- Mobile Radio Communication Systems (AREA)
- Information Transfer Between Computers (AREA)
- Telephonic Communication Services (AREA)
Abstract
Description
図1は本発明の一実施形態にかかるシステムの構成例を示す図である。図1において、ショッピングモール等の屋内施設1のエリア天井部等には、複数のビーコン2が設置されている。ビーコン2は、BLE(Bluetooth Low Energy)の電波によるブロードキャスト信号や超音波信号を発信することが可能な情報発信デバイスである。また、屋内施設1内または任意の場所にコンテンツサーバ3が設けられており、ビーコン2とコンテンツサーバ3の間は有線または無線のネットワーク4を介して通信可能に接続されている。コンテンツサーバ3は、ビーコン2から発信するビーコンIDの設定・変更の管理を行うとともに、ビーコンIDに紐付く位置情報(緯度経度情報)、地図情報、告知情報、クーポン等のコンテンツを保持する。
図6は第1の処理例を示すシーケンス図であり、ビーコン2から電波や超音波で発信する信号に含まれるビーコンIDを、なりすまし防止のためにコンテンツサーバ3からネットワーク経由で定期的に変更する処理と、その後の運用時の処理を示している。
上述した第1の処理例では、運用時において移動端末5がビーコン2からビーコンIDを含んだ信号を受信し、照合が正常に行えないと判断したタイミングで、移動端末5内で保持するIDリストをコンテンツサーバ3側と同期(コンテンツサーバ3側のIDリストを取得し、IDリスト保持部52のIDリストを更新)する処理を行っていた。
上述した第2の処理例では、移動端末5が所定のユーザ操作時に前回のIDリストの取得から所定時間を経過したと判断したタイミングで、移動端末5内で保持するIDリストをコンテンツサーバ3側と同期する処理を行っていた。
上述した第1~第3の処理例では、移動端末5に提供するIDリストは変更を行う毎に1個であったが、第4処理例では、将来の変更分を含めて複数個のIDリストを提供するようにしている。これにより、移動端末5においてコンテンツサーバ3との間で同期処理ができなかった場合にも、予め提供を受けたIDリストで対応できる場合には、適切な処理を行うことができる。
上述した第1~第4の処理例では、IDリストのビーコンIDをそのままビーコン2から発信するビーコンIDとしており、変更時には変更前と重複が生じないように変更していた。そのため、ビーコンIDの候補が枯渇する心配があるとともに、内容が解析されやすいものであった。そこで、第5の処理例では、IDリストのビーコンIDを基礎的なIDと暗号化方式の記述を合体したもので表現し、ビーコン2からは基礎的なIDを記述の暗号化方式に従って暗号化したもの(暗号化ID)と暗号化方式の記述を発信する。これにより、基礎的なIDを固定としたままで暗号化方式だけを変更すればよいので、枯渇や解析される心配なくビーコンIDを変更することができる。
以上説明したように、本実施形態によれば、ビーコン等における識別情報のなりすましを防止することができる。
ビーコンIDは「識別情報」の一例である。ビーコン2は「発信手段」の一例である。コンテンツサーバ3は「管理手段」の一例である。移動端末5は「受信手段」の一例である。
1 屋内施設
2 ビーコン
21 ID発信部
3 コンテンツサーバ
31 ID管理部
32 コンテンツ管理部
4 ネットワーク
5 移動端末
51 ID・コンテンツ管理部
52 IDリスト保持部
53 コンテンツ保持部
Claims (11)
- 識別情報を含む特定の信号を発信する発信手段と、
前記識別情報の設定および変更を行い、設定または変更された特定の識別情報を管理する管理手段と、
前記特定の信号を受信することが可能で、かつ、前記管理手段から前記特定の識別情報を取得することにより同期が可能な受信手段と
を備え、
前記受信手段は、取得した前記特定の識別情報と受信した前記特定の信号とを照合した結果を、前記発信手段の適否判定に用いることを特徴とする識別情報提供システム。 - 前記管理手段は、前記受信手段が前記照合を正常に行えないと判断したタイミングで発する問い合わせに応じて前記特定の識別情報を前記受信手段に提供することを特徴とする請求項1に記載の識別情報提供システム。
- 前記管理手段は、前記受信手段が所定のユーザ操作時に前回の識別情報の取得から所定時間を経過したと判断したタイミングで発する問い合わせに応じて前記特定の識別情報を前記受信手段に提供することを特徴とする請求項1に記載の識別情報提供システム。
- 前記管理手段は、所定のタイミングで前記特定の識別情報を前記受信手段に提供することを特徴とする請求項1に記載の識別情報提供システム。
- 前記管理手段は、前記発信手段が適切であると判定した場合、判定された前記特定の識別情報に対応するコンテンツを前記受信手段に提供することを特徴とする請求項1乃至4のいずれか一項に記載の識別情報提供システム。
- 前記受信手段は、前記発信手段が適切でないと判定した場合、判定された前記特定の識別情報を前記管理手段に通知することを特徴とする請求項1乃至5のいずれか一項に記載の識別情報提供システム。
- 前記管理手段は、前記受信手段に対し、今後変更される予定の前記特定の識別情報の値を複数提供することを特徴とする請求項1乃至6のいずれか一項に記載の識別情報提供システム。
- 前記識別情報を、基礎識別情報に暗号化方式を示す記述を加えたものとして表現し、
前記発信手段は、前記基礎識別情報を前記暗号化方式で暗号化した暗号化識別情報と前記暗号化方式を示す記述を含む特定の信号を発信し、
前記受信手段は、受信した前記暗号化方式を示す記述により前記暗号化識別情報を復号して得た前記基礎識別情報に前記暗号化方式を示す記述を加えて比較のための識別情報を生成することを特徴とする請求項1乃至7のいずれか一項に記載の識別情報提供システム。 - 識別情報を含む特定の信号を発信する発信手段の前記識別情報の設定および変更を行い、設定または変更された特定の識別情報を管理し、
受信手段からの要求により前記特定の識別情報を提供し、前記受信手段において同期を行わせ、
前記受信手段が、取得した前記特定の識別情報に基づき、受信した前記特定の信号と照合した結果を、前記発信手段の適否判定に用いることを支援することを特徴とする識別情報提供装置。 - 識別情報を含む特定の信号を発信する発信手段の前記識別情報の設定および変更を行い、設定または変更された特定の識別情報を管理し、
受信手段からの要求により前記特定の識別情報を提供し、前記受信手段において同期を行わせる処理をコンピュータに実行させ、
前記受信手段が、取得した前記特定の識別情報に基づき、受信した前記特定の信号と照合した結果を、前記発信手段の適否判定に用いることを支援することを特徴とする識別情報提供プログラム。 - 識別情報を含む特定の信号を発信する発信手段の前記識別情報の設定および変更を行い、設定または変更された特定の識別情報を管理し、
受信手段からの要求により前記特定の識別情報を提供し、前記受信手段において同期を行わせる処理をコンピュータが実行し、
前記受信手段が、取得した前記特定の識別情報に基づき、受信した前記特定の信号と照合した結果を、前記発信手段の適否判定に用いることを支援することを特徴とする識別情報提供方法。
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP17762811.2A EP3429247B1 (en) | 2016-03-09 | 2017-02-13 | Identification information provision system, identification information provision device, identification information provision program, and identification information provision method |
JP2018504070A JP6587032B2 (ja) | 2016-03-09 | 2017-02-13 | 識別情報提供システム、識別情報提供装置、識別情報提供プログラムおよび識別情報提供方法 |
US16/117,292 US10856147B2 (en) | 2016-03-09 | 2018-08-30 | Identification information providing system, identification information providing apparatus, identification information providing method, and non-transitory recording medium |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2016-046162 | 2016-03-09 | ||
JP2016046162 | 2016-03-09 |
Related Child Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US16/117,292 Continuation US10856147B2 (en) | 2016-03-09 | 2018-08-30 | Identification information providing system, identification information providing apparatus, identification information providing method, and non-transitory recording medium |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2017154467A1 true WO2017154467A1 (ja) | 2017-09-14 |
Family
ID=59790310
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2017/005097 WO2017154467A1 (ja) | 2016-03-09 | 2017-02-13 | 識別情報提供システム、識別情報提供装置、識別情報提供プログラムおよび識別情報提供方法 |
Country Status (4)
Country | Link |
---|---|
US (1) | US10856147B2 (ja) |
EP (1) | EP3429247B1 (ja) |
JP (1) | JP6587032B2 (ja) |
WO (1) | WO2017154467A1 (ja) |
Families Citing this family (2)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
SE542530C2 (en) * | 2017-11-02 | 2020-06-02 | Crunchfish Proximity Ab C/O Crunchfish Ab | Mobile identification using thin client devices |
RU2714298C1 (ru) * | 2019-07-05 | 2020-02-14 | Общество с ограниченной ответственностью "Метка" | Система радиочастотной кодовой локации объектов |
Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2007006320A (ja) * | 2005-06-27 | 2007-01-11 | Nakayo Telecommun Inc | 無線lanシステムおよび通信方法 |
JP2011097437A (ja) * | 2009-10-30 | 2011-05-12 | Toshiba Corp | 通信システム、当該システムの携帯端末、および当該システムのセンタ |
US20140254466A1 (en) * | 2013-02-21 | 2014-09-11 | Qualcomm Incorporated | Interleaving Advertising Packets For Improved Detectability And Security |
WO2015076345A1 (ja) * | 2013-11-25 | 2015-05-28 | 京セラ株式会社 | 通信制御方法、ユーザ端末、及びプロセッサ |
WO2015151981A1 (ja) * | 2014-03-31 | 2015-10-08 | 株式会社Nttドコモ | 通信システム、通信端末、通信方法、及びプログラム |
JP2016046651A (ja) * | 2014-08-21 | 2016-04-04 | 株式会社ビーマップ | ビーコン検出・判定システム |
Family Cites Families (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP3271460B2 (ja) | 1995-01-12 | 2002-04-02 | ケイディーディーアイ株式会社 | 無線通信における識別子秘匿方法 |
JP2004032133A (ja) | 2002-06-24 | 2004-01-29 | Tdk Corp | 無線lanシステム、並びに、これに用いられるアクセスポイント装置及び無線端末装置 |
US20140133656A1 (en) * | 2012-02-22 | 2014-05-15 | Qualcomm Incorporated | Preserving Security by Synchronizing a Nonce or Counter Between Systems |
JP6051658B2 (ja) | 2012-07-30 | 2016-12-27 | 株式会社リコー | 無線通信装置、無線通信方法及びプログラム |
US9967713B2 (en) * | 2012-11-15 | 2018-05-08 | SSI America, Inc. | Locator beacon and radar application for mobile device |
US10771173B2 (en) * | 2013-02-04 | 2020-09-08 | Shopkick, Inc. | Presence detection using bluetooth and hybrid-mode transmitters |
WO2015061673A1 (en) * | 2013-10-25 | 2015-04-30 | Roximity, Inc. | Beacon security |
EP3091768A1 (en) * | 2014-02-06 | 2016-11-09 | Aplix IP Holdings Corporation | Communication system |
JP6314595B2 (ja) | 2014-03-28 | 2018-04-25 | 日本電気株式会社 | 測位装置、測位システム、測位方法および測位プログラム |
CN104980918B (zh) * | 2014-04-04 | 2019-09-17 | 阿里巴巴集团控股有限公司 | 信标数据传输、基于信标提供服务的方法及装置 |
US9525968B2 (en) * | 2014-10-07 | 2016-12-20 | Broadsoft, Inc. | Methods, systems, and computer readable media for using bluetooth beacon information to obtain and publish fine grained user location information |
JP6565607B2 (ja) * | 2015-10-30 | 2019-08-28 | 株式会社リコー | 通信システム、コンテンツ取得方法、およびプログラム |
-
2017
- 2017-02-13 EP EP17762811.2A patent/EP3429247B1/en active Active
- 2017-02-13 WO PCT/JP2017/005097 patent/WO2017154467A1/ja active Application Filing
- 2017-02-13 JP JP2018504070A patent/JP6587032B2/ja active Active
-
2018
- 2018-08-30 US US16/117,292 patent/US10856147B2/en active Active
Patent Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JP2007006320A (ja) * | 2005-06-27 | 2007-01-11 | Nakayo Telecommun Inc | 無線lanシステムおよび通信方法 |
JP2011097437A (ja) * | 2009-10-30 | 2011-05-12 | Toshiba Corp | 通信システム、当該システムの携帯端末、および当該システムのセンタ |
US20140254466A1 (en) * | 2013-02-21 | 2014-09-11 | Qualcomm Incorporated | Interleaving Advertising Packets For Improved Detectability And Security |
WO2015076345A1 (ja) * | 2013-11-25 | 2015-05-28 | 京セラ株式会社 | 通信制御方法、ユーザ端末、及びプロセッサ |
WO2015151981A1 (ja) * | 2014-03-31 | 2015-10-08 | 株式会社Nttドコモ | 通信システム、通信端末、通信方法、及びプログラム |
JP2016046651A (ja) * | 2014-08-21 | 2016-04-04 | 株式会社ビーマップ | ビーコン検出・判定システム |
Non-Patent Citations (1)
Title |
---|
See also references of EP3429247A4 * |
Also Published As
Publication number | Publication date |
---|---|
US10856147B2 (en) | 2020-12-01 |
EP3429247A1 (en) | 2019-01-16 |
US20190014474A1 (en) | 2019-01-10 |
EP3429247B1 (en) | 2020-09-23 |
EP3429247A4 (en) | 2019-01-16 |
JP6587032B2 (ja) | 2019-10-09 |
JPWO2017154467A1 (ja) | 2019-01-31 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US9247387B2 (en) | Proximity based reminders | |
EP4032248B1 (en) | End-to-end encryption with distributed key management in a tracking device environment | |
US20160078738A1 (en) | A system and method for tracking people | |
JPWO2008117556A1 (ja) | ログ取得システム、ログ収集端末、ログ取得端末、それらを用いたログ取得方法及びプログラム | |
US11876892B2 (en) | Key diversification in a tracking device environment | |
EP3217624A1 (en) | Information processing method, program, information processing apparatus, and system | |
WO2015151981A1 (ja) | 通信システム、通信端末、通信方法、及びプログラム | |
US20210144132A1 (en) | Distributed encryption | |
US20220060338A1 (en) | Data protection in a tracking device environment | |
CA2564334A1 (en) | System and method for obtaining certificate status of subkeys | |
JP6587032B2 (ja) | 識別情報提供システム、識別情報提供装置、識別情報提供プログラムおよび識別情報提供方法 | |
JP2007241907A (ja) | 位置情報付きファイル暗号化システム及び復号化システム、並びにその方法 | |
WO2015198660A1 (ja) | 通信装置、通信方法およびプログラム | |
JP2007189651A (ja) | 位置時刻情報検証サーバ、位置証明情報検証システム及び位置時刻情報の検証方法 | |
JP4585529B2 (ja) | 移動端末、id情報の秘匿化方法およびid情報の問い合わせ方法 | |
US11206201B2 (en) | Detection of a network issue with a single device | |
JP7039921B2 (ja) | 所在管理システム及びプログラム | |
AU2015249158A1 (en) | Communication system equipped with a radio beacon | |
JP5770329B2 (ja) | 端末認証システム、端末認証方法、サーバ、及び、プログラム | |
JP2017050659A (ja) | 配信システム、機器、及び配信管理装置 | |
JP2017163467A (ja) | 制御装置、端末装置、位置確認システム及びプログラム | |
JP2016111665A (ja) | 無線通信装置、無線通信方法及びプログラム | |
WO2017219759A1 (zh) | 一种用户签到的方法和系统 | |
JP2022137199A (ja) | クレジットカード、使用可能化方法、およびプログラム | |
JP4836034B2 (ja) | コンテンツ配信システム、端末装置、対象装置、コンテンツ配信装置及びコンテンツ配信方法 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
WWE | Wipo information: entry into national phase |
Ref document number: 2018504070 Country of ref document: JP |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2017762811 Country of ref document: EP |
|
ENP | Entry into the national phase |
Ref document number: 2017762811 Country of ref document: EP Effective date: 20181009 |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 17762811 Country of ref document: EP Kind code of ref document: A1 |