METHOD FOR ASSOCIATING AN OBJECT WITH A USER, DEVICE, OBJECT, AND CORRESPONDING COMPUTER PROGRAM PRODUCT

Abstract

A method for associating a communicating object with at least one user. A remote server receives a signal requesting an association between an user identifier and an object identifier. The server verifies an authorization for the association between the object identifier and the user identifier, including verification of whether or not there is pre-existing association of the object identifier with at least one other user identifier. If association is authorized, the object identifier is associated with the user identifier in a database which can be accessed by the remote server. The database includes at least one user identifier list and one object identifier list.

Claims

1-15. (canceled)

16. A method for associating a communicating object with at least one user, comprising steps of: receiving by a remote server, a signal requesting association between an user identifier and an object identifier; verifying by the remote server, an authorization for association between the object identifier and the user identifier; associating the object identifier with the user identifier in a database accessible by the remote server in response to a determination that the association is authorized, the database comprises at least one list of user identifiers and one list of object identifiers; and wherein the step of verifying comprises a step of verifying a pre-existing association or not of the object identifier with at least one other user identifier, the association of the user identifier with the object identifier being authorized in response to a finding that the verification of the pre-existing association is negative.

17. The method as claimed in claim 16, wherein the step of verifying comprises steps of transmitting, by the remote server, a signal requesting authorization for association to a terminal associated with said at least one other user identifier in response to a finding that the verification of the pre-existing association is positive; and authorizing the association of the user identifier with the object identifier upon receipt of an authorization signal subsequent to the signal requesting authorization for association.

18. The method as claimed in claim 17, further comprising a step of assigning a main or secondary user status to each user identifier for each object identifier with which the user identifier is associated in the said database; and wherein the signal requesting authorization for association is sent to other user having a status of the main user.

19. The method as claimed in claim 18, wherein the authorization signal originating from said other user comprises a status to be assigned to the user identifier for the communicating object.

20. The method as claimed in claim 16, wherein the step of verifying the pre-existing association comprises a step of searching the database to determine whether the object identifier is associated with another user identifier.

21. The method as claimed in claim 16, wherein the step of verifying the pre-existing association comprises steps of sending a state request signal to the communicating object via a wireless communications protocol; receiving a state signal originating from the communicating object subsequent to the state request signal; and wherein the state signal comprises at least one indicator of pre-existing association.

22. The method as claimed in claim 21, further comprising a step of transmitting by the remote server according to the wireless communication protocol to the communicating object, a configuration signal comprising at least one command for updating an indicator of association, subsequent to a successful association between the user identifier and the object identifier.

23. The method as claimed in claim 21, wherein the wireless communications protocol is a low-rate protocol.

24. The method as claimed in claim 23, wherein the low-rate wireless communications protocol is compatible with an ultra-narrow-band radio technology.

25. The method as claimed in claim 16, further comprising a step of assigning a main or secondary user status to each user identifier for each object identifier with which the user identifier is associated in the database.

26. The method as claimed in claim 16, further comprising a step of communicating by the communicating object with at least one terminal of each user with which the communicating object is associated via the remote server.

27. A device to associate an object with a user, comprising a remote server having access to a database, the database comprising at least one list of user identifiers and one list of object identifiers; wherein the remote server is configured to communicate with at least a remote object and a remote terminal; and wherein the remote server is configured to implement the steps of the method for associating as claimed in claim 16.

28. A communicating object identified by a unique object identifier, comprising a network connector operating according to a low-rate wireless communications protocol; and a processor to respond to all or part of requests from the method for associating as claimed in claim 16.

29. The communicating object as claimed in claim 28, wherein the low-rate wireless communications protocol is compatible with an ultra-narrow-band radio technology.

30. A computer program product downloadable from a communications network or recorded on a non-transitory media readable by a computer or executable by a processor, comprising program code instructions for implementing all or part of the method for associating as claimed in claim 16.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0061] Other features and advantages of the invention will become more clearly apparent from its description presented hereinafter, by way of example and in no way limiting, with reference to the appended drawings, in which:

[0062] FIG. 1 is a schematic representation of a communications system implementing a method of pairing according to one embodiment of the invention; and

[0063] FIG. 2 shows, by way of illustration, a flow diagram of the pairing method implemented by the communications system illustrated in FIG. 1.

DETAILED DESCRIPTION OF ONE PARTICULAR EMBODIMENT

[0064] With reference to FIG. 1, a communications system designed for the implementation of the pairing according to one particular embodiment notably comprises: [0065] a remote server 1 having access to a database 2; [0066] a first user terminal 3; and [0067] a communicating object 4.

[0068] In this particular embodiment, the remote server 1 is notably affiliated, in other words connected via a global communications network 7, with a first communications network 5. This first communications network is preferably of the wireless type and preferably of the low-rate type, for example compatible with UNB radio technology. In practice, the messages sent by the server to the first network 5 are relayed via a base station 51 connected both to the global network 7, for example of the internet type or of the GSM type, and to the first network 5. Accordingly, the server 1 and the base station 51 therefore comprise all the hardware and software means for communicating via the network(s) to which they are connected.

[0069] Furthermore, the communicating object 4 and the first user terminal 3, for example a smartphone or, alternatively, a tablet or a computer, are also equipped with hardware and software means for connecting to the first network 5 and communicating via this first communications protocol.

[0070] The communicating objects in question, in this particular case, are of the type of those that allow what is referred to as the “Internet of Things” to be formed, namely a connected physical network of objects carrying a certain amount of information and capable of communicating it. Such communicating objects correspond to a wide diversity of devices, such as for example cardiac implants, biocompatible transponders, automobile vehicles with various on-board sensors, information acquisition devices such as for example water or electricity consumption meters, smoke detectors, actuators controlling various devices such as street lighting or the opening of a gate, connected thermostats, remote control washing machines, etc.

[0071] Thus, a communicating object may be an object equipped with means for interacting with its environment, in the form of sensors and/or of actuators for example, and with means for exchanging information with terminals or others communicating objects, in the form of a communications module, typically wireless. For example, such a communicating object may be capable: [0072] of acquiring information relating to its own actual state or to its environment via sensors for example, [0073] of processing and storing information, [0074] of exchanging information with a terminal or any other communicating object via a communications module, typically wireless, for example for sending the information acquired or for receiving commands, [0075] of performing actions on its own actual state or on the environment via actuators for example.

[0076] Typically, the communicating object 4 is identified by an object identifier, which may be contained within a code 41 such as a bar code, a two-dimensional code of the “flashcode” or “QR code” type, or else an alphanumerical code. For example, this object identifier may be affixed by the manufacturer directly onto the object 4 or printed on the packaging 40 of the object or in a user instruction sheet. It goes without saying that the code 41 containing the object identifier may also contain other information relating to the object.

[0077] Similarly, each user is identified by the server 1 by a user identifier, for example in the form of a login coupled with a password. Furthermore, several users may be grouped under the same user account.

[0078] The database 2 accessible by the server 1, either directly or via the global network 7, notably comprises a list of pre-recorded user identifiers and, potentially, a list of pre-recorded object identifiers. Furthermore, the database 2 may also be enhanced by complementary information relating to each user identifier and/or each object identifier, such as for example the type of object, the date of acquisition of the object, information relating to the warranty, or else the preferences of use for each of the users, such as for example the IP address to which the messages must be sent, the electronic address, the telephone number, etc. Among this complementary information may also be mentioned the status of the user for each of the objects with which it is associated. For example, a main or secondary user status may be assigned to each user identifier for each object identifier with which this user identifier is associated in the database. Generally, the status of main user endows the holder with all the rights over the object and the status of secondary user endows the user with all or part of the rights over the object.

[0079] FIG. 2 shows a flow diagram summary of the main steps implemented during the pairing of an object identifier with a user identifier, appropriate to the communications system in FIG. 1.

[0080] As a first step, the user obtains (step A) the object identifier of the object, for example manually or automatically via the first user terminal 3. For example, the terminal 3 may be equipped with a flashcode reader.

[0081] Subsequently, the user sends (step B), via the first user terminal 3, a request for association to the server 1. This request for association notably takes the form of a frame containing, in particular, the object identifier of the object and the user identifier to be associated with this object. It goes without saying that this frame may contain other information relating to the user and/or the object like that contained in the bar code containing the object identifier for example.

[0082] In practice, the transmission of this frame may be carried out via an application installed in the first terminal 3. For example, the user can manually enter the user identifier and the object identifier via an interface for this application. In one variant, the application may be designed in such a manner as to allow the automatic input of the code containing the object identifier, for example via a bar code reader, and to allow the automatic transmission of the pairing request to the server.

[0083] When the server 1 receives the pairing request, the server 1 verifies (step C) whether the association requested is authorized, with the aim of eliminating any bogus request for association.

[0084] In practice, the server 1 verifies whether the object identifier is already associated with another user identifier.

[0085] For example, the server 1 can verify whether the object identifier is recorded in the database 2 and whether the object identifier is already associated with another user identifier.

[0086] It is of course possible that the object identifier might not be recorded in the database 2 prior to the pairing request. In this case, the object identifier will be added to the database during the association procedure, and the verification of the authorization for association may be obtained by sending a state request signal to the object via the first communications protocol. When this state request signal is received, the object 4 sends a state signal in the form of a frame notably containing an indicator of pre-existing association. Aside from this indicator of pre-existing association, the frame may also contain other types of information, for example the identifier of the main user of the object, the maximum number of users that can be associated, an indicator stating whether a new association is authorized.

[0087] According to one variant, the indicator of pre-existing association may be directly contained in the request for association. For example, it is possible to envision the case where the object is itself capable of generating an updated code, for example a bar code, containing not only the object identifier but also the updated information relating to the pre-existing association which could be sent automatically during the request for association. Of course, if the object 4 is already associated with another user, the code generated by the object may also contain the identifier of this other user. Moreover, when the object 4 is associated with several others users, it is preferable for the user identifier contained in the code to correspond to a user identifier having the status of main user.

[0088] Whatever the solution envisioned, if the result of the verification of a pre-existing association is negative, the association of the user identifier with the object identifier is therefore authorized, and the server 1 accordingly updates the database 2 (step E) for associating the object identifier with the user identifier.

[0089] In contrast, if the result of the verification of a pre-existing association is positive, in the example illustrated in FIG. 2, the server 1 sends a signal requesting authorization for association to a terminal 6 associated with this other user identifier (step D). The communication between the server 1 and the terminal 6 of this other user may conform to the first communications protocol or conform to another communications protocol.

[0090] In the case illustrated in FIG. 1, the server 1 communicates with the terminal 6 of the other user via a second communications protocol, different from the first communications protocol. The remote server 1 is therefore also affiliated with a second communications network 8, compatible with one of the existing communications standards, for example WI-FI®, and hence also comprises all the hardware and software means for communicating via this second communications protocol.

[0091] When a signal is received for authorizing association coming from the terminal 6 of this other user, the server 1 carries out the association of the user identifier with the object identifier by updating the database 2 (step E).

[0092] Once the association has been made in the database 2, the server 1 sends (step F) a signal indicating the success of the association requested to the first user terminal 3.

[0093] Of course, if the authorization for association is negative, the server does not implement the pairing and sends (step G) a signal indicating the failure of association requested to the first terminal 3 of the user having requested the association.

[0094] Furthermore, subsequent to the success of the association, the server 1 may also send a configuration signal to the object 4 containing, for example, an instruction for updating the association indicator and potentially the user identifier having the corresponding status of main user.

[0095] Subsequently, the object 4 communicates with the user with which it is associated via the remote server 1. It is of course possible for the user to use the first terminal 3 or a second terminal, distinct from the first terminal, for communicating with the server, via the first communications protocol or via a second communications protocol.

[0096] Furthermore, the case may also readily be envisaged where the first user terminal uses a communications protocol different from the first wireless communications protocol for communicating with the server.

[0097] What has been presented hereinabove therefore demonstrates that the solution provided is a solution for pairing between an object and a user, which does not require complex manual operations or configuration steps on the part of the user. Furthermore, the constraint on the number of objects to be paired, on the number of users to be associated and on the distance between the object and the terminal no longer exists. By virtue of the invention, the communicating object may be configured so as to take into account only frames originating from the server, which allows systematic processing by the object of all the irrelevant surrounding frames to be avoided. Furthermore, the user can communicate with the object via the server using any given terminal, and this is possible even if the communications protocol supported by this terminal is incompatible with that supported by the object.

[0098] The solution of the invention is particularly suited to communicating objects of the type of those used in M2M (Machine-to-Machine) applications, or of those that allow “The Internet of Things” to be formed, and preferably incorporating means of low-rate wireless communication compatible with UNB technology.