IP Library Granted Patent US 11,212,314
Granted Patent B2
US 11,212,314 · App. 16/654,602 · Granted Dec 28, 2021

Method for an object to communicate with a connected objects network to report that a clone may be impersonating the object in the network

Inventors: Yoann Fages-Tafanelli (Courbevoie, FR); Aurélien Cuzzolin (Courbevoie, FR); Fabien Blanco (Courbevoie, FR); Maël Berthier (Courbevoie, FR)
Assignee: IDEMIA IDENTITY & SECURITY FRANCE
H04L63/1483H04L63/102H04L63/1416
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,212,314
App. No.
16/654,602
Granted
Dec 28, 2021
Kind
B2
Abstract

The invention proposes a method for an object ( 1 ) to communicate with a server ( 2 ) of a connected objects network to report that a clone may be impersonating the object in the network, which method comprises the following steps implemented by the object ( 1 ): transmitting ( 106 ) to the server ( 2 ) a request from the object ( 1 ) to join the connected objects network; after transmitting the join-request, detecting ( 110 ) whether a reference message (uplink) transmitted by the object ( 1 ) to the server ( 2 ) was rejected or ignored; in response to the detection, transmitting ( 114 ) to the server ( 2 ) an alert message indicating the rejection or ignoring.

Claims (17)

1. A method for an object ( 1 ) to communicate with a server ( 2 ) of a connected objects network to report that a clone may be impersonating the object in the network, which method comprises the following steps implemented by the object ( 1 ):

transmitting ( 106 ) to the server ( 2 ) a request from the object ( 1 ) to join the connected objects network,

after transmitting the request, detecting ( 110 ) whether a reference message (uplink) transmitted by the object ( 1 ) to the server ( 2 ) was rejected or ignored,

in response to the detection, transmitting ( 114 ) to the server ( 2 ) an alert message indicating the rejection or ignoring, wherein the request transmitted before the detection comprises a nonce, the alert message is a new request to join the connected objects network, and the new request comprises, in place of the nonce, a value indicating that the reference message transmitted by the object to the server was rejected or ignored.

2. The method according to claim 1 , wherein the first value occupies a predetermined slot of N bits in the join-request transmitted before detection, the second value occupies the same predetermined slot of N bits in the new join-request, and the second value is equal to zero or 2N1.

3. The method according to claim 1 , wherein the first value and the second value occupy the DevNonce field defined by the LoRaWAN specification.

4. The method according to claim 1 , wherein the reference message is transmitted by the object ( 1 ) to the server after the join-request, and carries, for instance, useful data.

5. The method according to claim 1 , wherein the reference message is detected as having been ignored when no acknowledgment of receipt of the reference message is received by the object within a predetermined length of time following the transmission of the reference message.

6. The method according to claim 1 , further comprising the server rejecting or ignoring a join-request that is transmitted to the server after the alert message and comprises a unique identifier specific to the object.

7. The method according to claim 1 , wherein the join-request or the reference message comprises an integrity code generated based on a first secret key specific to the object ( 1 ), and wherein the alert message comprises an integrity code generated based on a second secret key specific to the object ( 1 ), different from the first secret key.

8. The method according to the preceding claim, wherein the integrity code of the join-request or of the reference message is generated by applying a predetermined function to the first secret key specific to the object ( 1 ), and wherein the integrity code of the alert message is generated by applying the same predetermined function to the second secret key specific to the object ( 1 ).

9. An object ( 1 ) comprising an interface for communicating ( 14 ) with a server ( 2 ) of a connected objects network, the object ( 1 ) further comprising a processor ( 10 ) configured to:

order a request for the object ( 1 ) to join the connected objects network, to be transmitted to the server ( 2 ),

after transmitting the request, detect whether a reference message transmitted by the object ( 1 ) to the server ( 2 ) was rejected or ignored,

in response to the detection, order that an alert message indicating the rejection or ignoring be transmitted to the server ( 2 ), wherein the request tranmitted before the detection comprises a nonce, the alert message is a new request to join the connected objects network and the new request comprises, in place of the first nonce, a value indicating that the reference message transmitted by the object to the server was rejected or ignored.

10. A system comprising an object according to the preceding claim, and the server of the connected objects network configured to:—upon receipt of the alert message, implement processing making it possible to detect whether a clone is impersonating the object in the network.

11. The system according to the preceding claim, wherein the server is further configured to reject or ignore a join-request that is transmitted to the server after the alert message and comprises a unique identifier specific to the object.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 26, 2025
From: IDEMIA IDENTITY & SECURITY FRANCE
To: IDEMIA FRANCE
Reel/Frame 070632/0157 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 16, 2019
From: FAGES-TAFANELLI, YOANN; CUZZOLIN, AURÉLIEN; BLANCO, FABIEN; BERTHIER, MAËL
To: IDEMIA IDENTITY & SECURITY FRANCE
Reel/Frame 050735/0984 →
Priority Claims (1)
FR 1871190 · Oct 16, 2018 · national
Continuity (1)
Related Publication 20200120132A1 · Apr 16, 2020
Cited By (1)
US 12,627,977