GB2599179A

GB2599179A - System and method for communicating information

Info

Publication number: GB2599179A
Application number: GB2102834.5A
Authority: GB
Inventors: Nagar Rajen
Original assignee: Your Octo Ltd
Current assignee: Your Octo Ltd
Priority date: 2020-09-29
Filing date: 2021-02-26
Publication date: 2022-03-30
Also published as: GB202015417D0; GB202102834D0

Abstract

A method and system for communicating information associated with a user of a first device 102 to a user of a second device 108, by determining, at the first device, information associated with a unique ID, obtaining the unique ID at the second device by scanning using the second device an object (240, fig 2E) comprising a near-field communications (NFC) tag encoded with the unique ID; and retrieving, at the second device, the information associated with the unique ID.

Description

Intellectual Property Office Application No G132102834.5 RUM Date:16 August 2021 The following terms are registered trade marks and should be read as such wherever they occur in this document: Facebook, Instagram, Youtube, Twitter Linkedin, Amazon, Ebay and Etsy Intellectual Property Office is an operating name of the Patent Office www.gov.uk/ipo SYSTEM AND METHOD FOR COMMUNICATING INFORMATION Technical Field The present disclosure relates to systems and methods of communicating information in a peer-to-peer setting.

Background to the Invention

In the present day, the average consumer is affiliated with an abundance of online services and platforms. For example, a user may use several social media platforms such as: Facebook, Instagram, Youtube, Twitter, LinkedIn etc. A user may also use several online business marketplaces including Amazon, Ebay, Etsy etc. For each of these third party services or platforms, the user is given a corresponding username or ID, also referred to as a tag or a handle. The username is used by the third party online services to identify the user. Usually, with knowledge of the username, the user's online activity (e.g. social media pages, posts, business activity) on the corresponding third party service or platform can be viewed, for example via their profile page. It is often the case that the user has a different username for different platforms or services. With the ever increasing use of online services and platforms, and with more of the user's information being online, a user's username and online activity increasingly becomes part of their personal identity.

A user may wish to share aspects of their online identity with other people, e.g. so that another person can view the user's online activity on the corresponding third party services/platforms. At present, this may be achieved by the user verbally communicating the relevant username(s) to the recipient. The recipient must then manually write down the username and/or manually search for the user on the corresponding third party service/platform. This can be a cumbersome and time consuming process, especially if the recipient must manually search for the user on multiple services/platforms, and/or the user has different usernames for different platforms. Furthermore, verbal communication poses a security risk if the user wishes to keep their online activity private from others to protect their personal identity, since an eavesdropper may overhear and be able to find the user's online activity. This may also open the user to hacking or scams.

In a further scenario, the user may send the recipient their username(s) or a link to the user's online profile(s) via a messaging service. However, this is still time consuming for the same reasons as above, and may still pose a security risk if the messaging service is breached or compromised.

In other scenarios, the user may print the relevant usernames and IDs on business cards, along with other information such as their telephone number and email address. The business card is usually handed over permanently to another person. However, printing of business cards is an ongoing cost to both the user and the environment. Moreover, once a batch of business cards are printed, it is not possible to change the information that is printed on them. Therefore, the user is committed to sharing the same information in each interaction, and has limited options if they decide that they no longer want to share certain aspects of their online identity. The handing over of business cards may also be viewed as unhygienic. Furthermore, misplacing or losing business cards can lead to security risks as described above.

There is therefore a need for a fast, efficient, adaptable and secure way of communicating the user's information (e.g. username(s), links to the user's profile(s) on the third party services/platforms) to the recipient.

Summary of the Invention

The present disclosure provides a method and a system aimed at solving the above

deficiencies of the prior art.

In a first aspect of the present invention, there is provided a method of communicating information associated with a first user of a first user device to a second user of a second user device, the method comprising: determining, at the first user device, information associated with a unique ID; obtaining the unique ID at the second user device by scanning, using the second user device, an object comprising a near-field communications (NFC) tag encoded with the unique ID; and retrieving, at the second user device, the information associated with the unique ID.

Advantageously, the method provides a fast, efficient, adaptable and secure way of communicating the first user's information to the second user. The method may be faster than the alternatives, since the information transfer can be near-instant when using a suitable network once the NFC tag has been scanned. The method is efficient because the method does not rely on disposable resources, such as paper business cards. The method is adaptable because the first user is able to determine the information that is going to be retrieved by the second user device. The method is secure because the second user device must have knowledge of the unique ID that is uniquely encoded on the object and is uniquely associated with the first user. As such no verbal or written communication is required.

In some examples, the method further comprises: transmitting, over a network, the information determined at the first user device to a server configured to store the determined information in association with the unique ID; wherein the second user device retrieves the information associated with the unique ID from the server in response to obtaining the unique ID from the object.

In some examples, the retrieving further comprises requesting the information from the server based at least in part on the unique ID, and receiving the information over the network.

In some examples, the method comprises retrieving, with the first user device, information that is already stored on the server in association with the unique ID, and wherein determining the information associated with the unique ID comprises providing user input to the first user device to delete information that is already stored on the server in association with the unique ID and/or add to information that is already stored on the server in association with the unique ID. Advantageously, the first user has complete control over what information is communicated to the second user, and can change the information by addition or deletion at any point.

In some examples, the information determined at the first user device comprises public information associated with the unique ID and private information associated with the unique ID, and wherein the retrieving comprises retrieving at least the public information and not the private information. Determining the public information and the private information may comprise receiving user input at the first user device to select which of the determined information is public information or private information. Advantageously, this allows the first user to more easily customise which information is communicated to the second user, without having to delete and re-add information.

In some examples, the determined information is indicative of the first user's identification according to at least one third party service and/or platform.

In some examples, the method further comprises displaying the retrieved information on the second user device, and optionally performing an action on the second user device that is associated with the retrieved information in response to receiving user input to select the retrieved information. Optionally, the retrieved information is associated with an application on the second user device, and the action comprises opening, on the second user device, the application that is associated with the retrieved information. Advantageously, the second user can easily use the retrieved information to access the first user's online profile and activities.

In some examples, the method includes automatically performing an action at the second user device in response to retrieving the information. Optionally, the retrieved information is associated with an application on the second user device, and the automatic action comprising automatically opening, on the second user device, the application that is associated with the retrieved information. Advantageously, the second user can more easily access the first user's online activity at near instant speeds.

In a second aspect of the present invention, there is provided a computer program, or suite of computer programs, configured to, when run on a processors, cause a computing devices to carry out the method of the first aspect.

In a third aspect of the present invention, there is provided a computer-readable storage medium or a plurality of computer-readable storage media comprising the computer program or suite of computer programs of the second aspect.

In a fourth aspect of the present disclosure, there is provided a system for communicating information, comprising: a first user device configured to receive user input to determine information associated with a unique ID, the unique ID being associated with a first user of the first user device; and a second user device configured to: obtain the unique ID by scanning an object comprising a near-field communications (NFC) tag encoded with the unique ID; and retrieve the information associated with the unique ID based on the unique ID.

In a fifth aspect of the present invention, there is provided an object comprising a body embedded with a near-field communications (NFC) tag, the NFC tag being encoded with a unique ID.

Advantageously, the object is made unique to a user, such as the first user. Therefore, the object can be used in the above described methods and systems for fast, efficient, adaptable and secure transfer of information between the first and second users.

In some examples, the object is substantially rectangular, optionally wherein the object has a length of less than 90mm, a width of less than 60mm, and a thickness of less than 2mm. In other examples, the object is substantially circular, optionally wherein the object has a diameter of less than 50mm, and a thickness of less than 2mm. Advantageously, the object can be handheld and kept on the user's person to be used at the user's convenience.

In some examples, the body has first major surface and a second major surface, the object comprising a ferrite coating on the first or the second major surface. Advantageously, accidental communication and interference can be avoided when the object is stored in close proximity with the object owner's device.

In some examples, the body is made of a plastic material. Advantageously, a plastic material permits external devices to read the information encoded on the NFC tag. Furthermore, plastic may be relatively flexible making the object more comfortable to hold and store.

In some examples, the object further comprises an adhesive coating on the ferrite layer. Advantageously, the object can be adhered to another object, such as the user's device, wallet, keys, bag etc. As such, the user is less likely to lose the object, and the object is more readily accessible for convenient usage.

Description of the Drawings

Some embodiments of apparatus, system as and/or methods in accordance with embodiments of the present invention are now described, by way of example only, and with reference to the accompanying drawings, in which: FIGURE 1 shows a system according to an embodiment of the present disclosure; FIGURE 2A shows an object comprising a NFC tag according to an example of the present 30 disclosure; FIGURE 2B shows an object comprising a NFC tag according to an alternative example of the present disclosure; FIGURE 2C shows an object comprising a NFC tag according to another alternative example

of the present disclosure;

10 15 20 FIGURE 2D shows an object comprising a NFC tag according to another alternative example of the present disclosure; FIGURE 2E shows an object comprising a NFC tag according to another alternative example

of the present disclosure;

FIGURE 3 shows a flow chart illustrating a method of communicating information according to an embodiment of the present disclosure; and FIGURE 4 shows an architecture of a computing device according to examples of the

present disclosure.

Detailed Description

The present disclosure relates to a method of communicating information between users in a peer-to-peer setting. A first user is in possession of a first user device (e.g. a smartphone or mobile device) and an object (e.g. a handheld object or a wearable object) comprising a NFC tag. The NFC tag encodes a unique ID, which is unique to the first user. The unique ID may be a unique URL. A server stores various information about the first user, in association with the unique ID of the first user. The first user is able to choose, customise and otherwise determine which information of theirs is stored on the server. A second user has a second user device (e.g. a smartphone or mobile device) that comprises a NEC tag reader. In an example interaction, the second user scans the first user's object with the second device. The second user obtains the first user's unique ID. Based on the unique ID, the second device retrieves the first user's information from the server over a network. The second user can then use the retrieved information in connection with various third party services or platforms. However, since the first user is able to choose which information of theirs is stored on the server, the first user can customise which of their information is retrievable by the second user in the above described interaction.

Figure 1 shows a computing system 100 according to an embodiment of the present disclosure. The system 100 comprises a first user device 102 associated with a first user, a second user device 108 associated with a second user, and a network server 106. The first user device 102, second user device 108, and server 106 are in data communication with one another via a network 104.

The network 104 may be any type of network that is configured to facilitate the communication and transmission of data between the each user device 102/108 and the server 106. For example, the network 104 may be a cellular network, Wi-Fi network, the Internet, a local area network or any other type of network that is suitable for providing data communication between each user device 102, 108 and the server 106.

The server 106 may be any type of server known by the skilled person that is suitable for carrying out the methods of the present disclosure. Furthermore, the server 106 may comprise a computer readable storage medium that is suitable for storing data for the purposes and methods of the present disclosure. For example, the server 106 may comprise one or more hard drives, servers, and/or flash storage devices for storing data.

The server 106 may also comprise one or more processors to carry out computer executable instructions, and any other hardware or software to facilitate the communication of data over the network 104.

The server 106 is further configured to store user information associated with the user of the first user device 102. For example, the user information may include the first user's personal information and contact information. The user information may include one or more of the following data fields or data instances: * <full name>; * <email address>; * <mobile number>; * <postal address>.

The first user may be a user or a member of one or more third party services. Therefore, the user information may also include information that identifies the first user on said third party services, which may more generally be referred to as third party identification information. For example, the user information of the first user that is stored on the server 106 may also include the following data: * <thirdpartyID#1>; * <thirdpartyID#2>; * <thirdpartyID#3>.

The data <thirdpartyID#1> may correspond to information that identifies the first user on a first third-party service. The data <thirdpartyID#2> may correspond to information that identifies the first user on a second third-party service. The data <thirdpartyID#3> may correspond to information that identifies the first user on a third third-party service. The first, second and third third-party services may differ from one another. Although only three instances of third party identification information is indicated above, it should be appreciated that the server 106 may store any number of one or more instances of third party identification information. Moreover, before the first user has registered with the server 106, the server 106 may not store any instances of third party identification information.

Example third party services may at least include: social media platforms (e.g. Facebook, Twitter, Instagram, TikTok, Snapchat), online marketplaces (e.g. Amazon, eBay, Etsy), media services (e.g. Spotify, Youtube, Twitch), and payment services (e.g. Venmo, Monzo, PayPal). Each third party service may use different information to identify the first user.

For example, some third party services may identify the first user with respective usernames (i.e. "handles"), or with URLs that identify the first user's profile on the third party service. As such, one or more of the instances of third party identification information <thirdpartyID#1>, <thirdpartyID#2> or <thirdpartyID#3> may be a string of characters, symbols and/or numbers that represents a username, handle or URL that identifies the first user on the respective third party service. Other third party services may identify the first user with other information such as ID numbers, codes, usernames, phone numbers, email addresses or any combination thereof. For example, a payment service may identify the first user based on a combination of (or one of) their email address and their mobile number, e.g. in order to facilitate a payment. As such, at least one of the third party identification information <thirdpartyID#1>, <thirdpartyID#2> or <thirdpartyID#3> may be a data object that contains a plurality of data instances for identifying the first user on the respective third party service.

The server 106 further stores a unique ID in association with the first user, and therefore in association with each of the above information fields/instances stored on the server 106. The unique ID is uniquely associated with the user of the first user device 102 (i.e. the first user). Preferably, the unique ID is a URL (uniform resource locator), i.e. an internet web address, that is uniquely associated with the first user. The unique ID may alternatively be any other string of characters and/or symbols that uniquely identifies the first user.

Figure 1 also illustrates an object 110, which may or may not be considered as part of the system 100. The object 110 is encoded with the unique ID that is associated with the first user. In particular, the object 110 comprises a NFC (near field communication) tag (not shown). The NFC tag is encoded with the unique ID associated with the first user.

Each user device 102, 108 in Figure 1 may be any computing device that is suitable for executing the methods disclosed herein. Preferably, the user devices 102, 108 are personal or portable devices that may be kept on their respective users' person, such as a smartphone, tablet, or portable PC (personal computer). However, the user devices 102, 108 may be any other type of computer, such as a desktop computer.

Figure 4 shows an example architecture of each user device 102, 108 according to an embodiment of the present disclosure. Each user device 102, 108 comprises a processor 450 in data communication with an input module 454, output module 456, communication module 458, a near-field communication (NFC) tag reader 452, and a local storage device 460.

The processor 450 may be any processor configured to execute computer readable instructions to perform the methods described in the present disclosure.

The input module 454 is configured to receive user inputs. For example the input module 454 may comprise one or more of: a touchscreen, a mouse, a computing keyboard, a keypad, or any other input device that enables the respective user to perform the methods of the present disclosure.

The output module 456 is configured to output and/or display data to the respective user. In particular, the output module 456 is configured to display a graphical user interface (GUI) to enable a user to perform the methods described in the present disclosure. In some embodiments, the display is a touchscreen interface.

The NFC reader 452 is configured to read data from a NFC tag, such as the NFC tag in the object 110 in Figure 1. In particular, the NFC reader 452 is configured to read the unique ID or URL from the NFC tag. As such, the second user device 108 can obtain the unique ID from the object 110 by scanning the object 110, e.g. using the NFC reader 452. In particular, the second user device 108 is configured to read or scan the NFC tag embedded in the object 110. By reading the NFC tag, the second user device 108 may obtain the unique ID from the object 110, e.g. via the NFC tag reader 452. The first user device 102 may also be configured to read or scan the unique ID from the object 110, e.g. using a respective NFC tag reader 452, in the same way as described above in respect of the second user device 108.

The communications module 458 is configured to facilitate data communication between the respective user device 102, 108, and the network 104 in Figure 1. In particular, the communications module 458 is configured to send and receive data, to and from the network storage device 106, over the network 104, as required by the methods disclosed herein.

The local storage device 460 is configured to locally store any software instructions and data to enable the execution of the methods described in the present disclosure.

Figure 2A illustrates a view of an object 200 according to an exemplary embodiment of the object 110 of Figure 1. The object 200 comprises a body 202 having a first major surface 206 and a second major surface 208 separated by a thickness 209. The second major surface 208 is on an opposite side of the body 202 to the first major surface 206.

The first and second major surfaces may be considered as being parallel to one another.

As illustrated in Figure 2A, the body 202 may generally have a rectangular shape. Preferably, the body 202 is sized and dimensioned such that the object 110 fits in a user's hand and/or pocket. Preferably, the body 202 has a length of less than 90mm, a width of less than 60mm, and a thickness of less than 2mm. Preferably the thickness is approximately lmm. More preferably, the body 202 has a length of approximately 65-70mm, a width of approximately 40-45mm. However, any other size and shape of object 200 is also within the scope of the present invention.

The body 202 may be formed of any suitable material known in the art. In one example, the body 202 may be a plastic. Advantageously, a plastic material permits external devices to read the information encoded on the NFC tag 204. Furthermore, plastic may be relatively flexible making the object 200 more comfortable to hold and store.

The body 202 is embedded with an NEC tag 204, corresponding to the NEC tag as previously described above. Preferably, the NFC tag 204 is embedded in the thickness 209 of the body 202 such that the NFC tag 204 is not visible from the exterior of the object 110. Advantageously, the body 202 surrounding the NFC tag 204 may protect the NEC tag 204 from damage. In other examples, the NEC tag 204 may be provided on or close to one of the first or the second major surfaces 206 or 208.

Figure 2B illustrates an object 210 according to an alternative example of the object 110 shown in Figure 1. The object 210 in Figure 2B mostly corresponds to the object 200 shown in Figure 2A. However, the object 210 in Figure 25 further comprises a ferrite coating 211 on the second major surface 208. Advantageously, the ferrite coating 211 will prevent interference between the object 210 and another device that comprises a NEC tag reader (e.g. the first user device 102) when the object 210 is stored in close proximity to that device. In particular, without the ferrite layer 211, another device may accidentally read or scan the NFC tag 204 when stored in close proximity with the object 210. This may waste power and battery in the device as the device may perform unnecessary processing of the information retrieved from the NFC tag 204. The ferrite layer 211 however may block communication between the NFC tag 204 and the other device through the second surface 208. Therefore, the object 210 can be stored with the second surface 208 facing the device without the risk of accidental communications between the NEC tag 204 and the device.

Figure 2C illustrates an object 220 according to another alternative example of the object 110 shown in Figure 1. The object 220 in Figure 2C mostly corresponds to the object 200 shown in Figure 2A. However, the object 220 in Figure 2C comprises a generally circular body 222 instead of a rectangular body. Similarly to the object 200, the object 220 is preferably sized and dimensioned to be handheld and fit into a user's pocket. Preferably, the body 222 has a diameter of less than 50mm, and a thickness of less than 2mm.

Preferably the thickness is approximately lmm. More preferably, the body 222 has a diameter of approximately 25-30mm. However, any other size and shape of object 220 is also within the scope of the present invention.

Although not shown in Figure 2C, the object 220 may comprise a ferrite coating on the second surface 208 of the body 222, similarly to the ferrite coating described above in relation to Figure 2B.

Figure 2D illustrates an object 230 according to another alternative example of the object 110 shown in Figure 1. The object 230 in Figure 2D mostly corresponds to the object 220 shown in Figure 2C. However, the object 230 further comprises a ferrite coating 235 on the second major surface 208 similar to the ferrite coating described in relation to Figure 2B, and an adhesive layer 237 on the ferrite coating layer 235. The adhesive layer 237 may allow the object 230 to be adhered to the surface of another object or device. For example, the first user of the first user device 102 may adhere the object 230 to the first user device 102 so that they are less likely to lose or misplace the object 230. This may further improve the security and convenience of using the system 100. However, due to the close proximity between the object 230 and the first user device 102, the ferrite layer 235 is provided in between the adhesive layer 237 and the second surface 208 to prevent accidental communications interference between the NEC tag 204 and the NEC tag reader of the first user device 102.

In some examples, the object 110 can be a wearable object, such as a bracelet or a ring. Figure 2E illustrates a wearable object 240 according to another alternative example of the object 110 shown in Figure 1. The object 240 in Figure 2E is similar to the object 200 shown in Figure 2A in that the object 240 is embedded with the NFC tag 204. However, the object 240 in Figure 2E has a body 242 formed of a ring shape. The ring shaped object 240 comprises an inner surface 246 and an outer surface 248. The object 240 has a thickness between the inner surface 246 and the outer surface 248. The object 240 also has a width 249 in a direction parallel to the axis of the ring shaped object 240. The NEC tag 204 is embedded in the thickness of the object 240. The NFC tag 204 is shown in dotted lines in Figure 2E for illustrative purposes, but it will be appreciated that the NEC tag 204 may not be visible from the exterior of the object 240.

The object 240 is preferably sized and dimensioned to snugly fit around a user's finger. In particular, the object 240 should have a diameter and a width 249 such that the object 240 can fit on a human finger. Preferably, the object 240 has a diameter of between 10- 30mm, and a width 249 of between 5-15mm. However, any other size or dimension of the object 240 is also within the scope of the present invention.

In other examples, the object 240 is preferably sized and dimensioned to fit around a user's wrist.

The thickness of the object 240 is preferably dimensioned such that the NFC tag 204, and the circuitry 245 where used, can be embedded in the thickness of the object 240. For example, the thickness is preferably at least 1mm.

Optionally, the object 240 can comprise electronic circuitry 245. The electronic circuitry 245 may also be embedded in the thickness of the object 240. Preferably, the circuitry 245 is located in the object 240 in a different location to the NFC tag 204. For example as illustrated in Figure 2E, the electronic circuitry 245 may be on an opposite side of the object 240. However, in other examples the circuitry 245 can be located anywhere in the thickness of the object 240 relative to the NFC tag 204.

The circuitry 245 is configured to communicate with a computing device to perform a communication protocol that is different to the communications performed with the NFC tag 204. In particular, the circuitry 245 is configured perform a contactless payment protocol with a payment terminal, such as a point of sale payment terminal or a contactless automatic teller machine (ATM). The circuitry 245 is configured to perform the payment protocol when in proximity to the payment terminal. For example, according to contactless payment standards, the circuitry 245 may be configured to perform the payment protocol when within 10cm, preferably 4cm, of an antenna of the payment terminal.

The circuitry 245 may comprise any circuitry known in the art that supports the performing of contactless payment protocols according to contactless payment standards (e.g. "Europay, Mastercard and Visa" (EMV) standards, ISO/IEC 14443 standard or otherwise).

For example, the circuitry 245 comprise any suitable combination of integrated circuitry, logic circuitry, an antenna, an RFID tag and/or a second NFC tag. Moreover, the circuitry 245 can store payment information associated with a bank account of the first user. The first user's payment information may be stored in the second NFC tag. As such, following the execution of the payment protocol between the circuitry 245 and a payment terminal, the first user's bank account is debited accordingly. The payment terminal also adheres to contactless payment standards corresponding to that of the circuitry 245.

In an example interaction, the object 240 is brought into proximity with the payment terminal (preferably such that the circuitry 245 is less than 10cm or less than 4cm from an antenna of the payment terminal, as discussed above). The payment terminal energises the circuitry 245 over wireless medium. A radio connection is established between the payment terminal and the circuitry 245. The payment terminal sends the circuitry 245 an encryption key using a private key. The circuitry 245 decrypts the encryption key allowing all future communication to take place using the encryption key. The payment terminal sends details of a proposed transaction to the circuitry 245. The circuitry 245 sends to the payment terminal payment details of the first user (e.g. a bank or debit/credit card number of the first user) and the details of the transaction back to the payment terminal, both details being encrypted with the private key. The payment terminal then completes the payment via a payment processing system.

It will be appreciated that any of the objects described herein, such as the objects 200, 210, 220 or 230, may also comprise the electronic circuitry 245 that is described in connection with the object 240. Such objects will have the added functionality of the electronic circuitry 245 as is described herein.

Figure 3 illustrates a flow chart 300 that depicts a method of communicating information using the system 100. As described above, prior to executing the method 300, the object encodes a unique ID associated with the user of the first user device 102 (i.e. the first user). Additionally, the server 106 stores information associated with the first user and the unique ID.

At step S301, the second user uses the second user device 108 to scan the object 110 to read the unique ID encoded on the object 110. In an example interaction, the first user may be in possession of the first user device 102 and the object 110. The first user may present the object 110 to the second user. The second user may scan the object 110 using the second user device 108. After the interaction, the first user maintains possession of the object 110.

At step S303, as a result of scanning the object 110, the second user device 108 obtains the unique ID. In particular, the second user device 108 receives the unique ID that is encoded in the NFC tag embedded within the object 110. Communication between the second user device 108 and the object 108 may take place via close or near field communication protocols as is known in the art.

At step 5305, the second user device 108 retrieves the information associated with the unique ID from the server 106. For example, the second user device 108 may attempt to open the URL that is the unique ID, in a web browser. This may trigger the second user device 108 to transmit an information request to the server 106 over the network 104. In particular, the second user device 108 may transmit a request for the information that is associated with the unique ID from the server 106. The server 106 may receive the information request for information that is associated with the unique ID. The server 106 may then transmit the information associated with the unique ID to the second user device 108. In particular, the server 106 may transmit some or all of the following information to the second user device 108: * <full name>; * <email address>; * <mobile number>; * <postal add ress>; * <thirdpartyID#1>; * <thirdpartyID#2>; * <thirdpartyID#3>.

Steps 5307-5311 present optional ways in which the first user's information can be used by the second user at the second user device 108.

At step 5307, the retrieved information may be displayed on the second user device 108. The retrieved information fields may be displayed or represented as icons in the web browser.

At step 5309, the second user may provide user input to the second user device 108 to select one of the information fields.

At step S310, in response to the second user selecting an information field, the second user device 108 may then perform an action corresponding to the selected information

field.

In one example, the second user selects the <thirdpartyID#1> information field. The <thirdpartyID#1> information may comprise information that identifies the first user according to a first third party service. At step 5310, the second user device 108 may open a third party application corresponding to the first third party service and perform a corresponding action. For example, if the first third party service is a social media platform or a media service, the second user device 108 may open the corresponding application and automatically direct to the first user's profile or page on the third party service. As another example, if the first third party service is a payment service, the second user device 108 may open the corresponding application and automatically initiate a payment to the first user via that payment service. Note that if the third party application is not installed on the second user device 108, the second user device 108 may prompt the second user to install said application.

In another example, the second user may select the <telephone number> information field. The second user device 108 may open a corresponding native application. The second user device 108 may then prompt the user to add <telephone number> to the second user's address book on the second user device 108.

In another example, the second user may select the <email address> information field. The second user device 108 may open a corresponding email application. The second user device 108 may then prompt a new email to the first user using the <email address> information populated in the "To" field of the new email.

As will be now described, the first user may customise which of their information that is stored on the server 106, is retrievable by other devices, such as the second user device 1081 using the method 300. In one example, the first user may be able to view the information stored on the server 106 in association with their unique ID, using the first user device 102. For example, the first user device 102 may communicate with server 106 over the network 104 to view the information stored on the server 106 in association with their unique ID. Each information field may be associated with a respective access level setting or security setting. Each access level setting may be selectable between a "private" or "public" option. Information fields associated with a "private" setting may not be retrievable by the second user device 108. On the other hand, information fields associated with a "public" access setting may be retrievable by the second user device 108. As such, in step S305 of the method 300, the second user device 108 may only retrieve the information associated with the first user that is "public" according to the access setting.

Advantageously, the first user can dynamically change which information is public or private to other user devices. Being able to dynamically change the access setting for each individual information field adds a layer of personal security for the first user. In particular, each information field may be sensitive as it constitutes part of the first user's online identity. Therefore, the first user is able to dynamically adapt which sensitive information is shared using the method 300. Furthermore, the information shared using the method of Figure 3 can be adapted based on the situation, environment or circumstances in which the method 300 is being executed. For example, the first user may attend a first event where they expect to share information in accordance with the method of Figure 3. The first user may be comfortable sharing all of the above information fields with attendees of the first event, and therefore the user may set all of the information fields to "public".

However, the first user may then attend a second event, where the first user is not comfortable sharing all of the information fields with attendees of the second event, and/or not all of the information fields are appropriate for sharing at the second event. Therefore, prior to attending the second event, the first user may use the first device 102 to set certain information fields to "private". Then, when the method of Figure 3 is performed, only the "public" information fields may be shared with a second user of the second device 108.

In further examples, each information field may also be associated with a "direct" setting. The direct setting can be turned on in respective of one of the information fields. Referring back to Figure 3, if the redirect setting is "on" for an information field, then the second user device 108 only receives that information field at step 5305. The second user device 108 may detect that it has only received one information field as a result of the "direct" setting being turned on. In this case, the method in Figure 3 will proceed to step S111 instead of step 5307. At step 5311, the second user device 108 may perform an automatic action in response to retrieving the one information field. In particular, the second user device 108 may automatically perform the action that would be performed at step 5310 in respect of the one information field. Effectively, the display step 5307 and the selection step 5309 are bypassed.

Advantageously, the "direct" option allows the first user to emphasise a particular information field that is important for sharing with the second user. For example, the first user may be in a scenario where it is particularly important and/or appropriate to share <thirdpartyID#1> with the second user. Before executing the method 300, the first user may use the first user device 102 to turn the "direct" setting to "on" in respect of the <thirdpartyID#1> information field. Then, at step 5311, the second user device 108 may automatically open a third party application corresponding to the first third party service and perform an action in the application (e.g. direct to the first user's profile, or initiate another process flow in the application based on the <thirdpartyID#1> data). As such, the redirect option also allows the second user to more quickly and efficiently obtain and use the first user's information.

It is now described how the object 110 and the unique ID encoded on the object may be registered to the first user and the first user device 102. In an example registration process, the first user of the first user device 102 may scan the object 110 and read the unique ID. The first user may then input their personal information (e.g. <Name>, <telephone number>, <thirdpartyID#1> etc.) using the first user device 102. The unique ID and the first user's information may then be transmitted to the server 106 over the network 104. The first user's information is subsequently stored to the server 106 in association with the unique ID, thereby registering the object 110 to the first user and the first user device 102.

At any point during or after registration, the first user may customise which personal information is stored on the server 106. For example, the first user may view which information is stored on the server 106, using the first user device 102. The first user may then provide user input to the first user device 102 to add, delete or change the information in the information fields. As such, in step 905 of the method 300, the second user device 108 may only retrieve the information associated with the first user that is stored on the server 106. Advantageously, this allows the first user to only store information on the server 106 that the first user is comfortable with being shared the other user devices, such as the second user device 108.

Advantageously, the above described methods add multiple layers of security for the first user, when the first user desires to share personal information with a second user.

As one layer of security, the first user is able to adaptively change which of their personal information is shared when the method 300 is performed, e.g. by setting some information fields to "private" and others to "public", as described above. This adds a layer of personal security to the user, so that the user is able to adapt to their personal situation, or to wider situations such as data leaks.

As another layer of security, the second user device 108 must have knowledge of the unique ID of the first user, in order to successfully request and retrieve any of the information associated with the unique ID of the first user from the server. Consequently, a malicious user or device who does not have knowledge of the unique ID, cannot obtain any of the first user's information.

Preferably, the unique ID of the first user is only obtainable from scanning the object 110.

In particular, the second user device 108 may only obtain the unique ID through scanning the first user's object 110 as described in step S301. This step behaves as a form of consent from the first user, to allow the second user device 108 to obtain the unique ID and access the first user's information from the server 106.

In some examples, to ensure that the second device's 108 knowledge of the unique ID is consensual, at step 5305, the system 100 may be configured to implement any suitable security and authentication protocol known in the art, to further ensure that the second user device 108 has obtained the unique ID in an authentic manner from the object 110.

In particular, the network server 106 may be configured to perform an authentication protocol to ensure that the second user device 108 has obtained the unique ID from the object 110 according to step S301 above. As such, it can be determined that the second user device 108 has not obtained the unique ID from an unreliable or black market source.

In some examples, the unique ID may be encrypted with a timestamp indicative of the time at which step S301 is performed to ensure that the unique ID is current. Then, at step 5305, the server 106 may only sent the first user's information to the second user device 108 if the time-stamp is within a predetermined threshold. In other examples, the unique ID may be encrypted with a physical unclonable function (PUF) of the object 110, so that authentic communication of the unique ID to the server 106 cannot be unauthentically replicated.

In further examples of authentication protocols, the system 100 may be configured to perform 2-factor authentication. At step 5305, the server 106 may transmit a message to the first user device 102 informing the first user that the second user device 108 is attempting to retrieve the first user's information using the unique ID. The first user may use the first user device 102 to provide either a positive or a negative response to the message. If the server 106 receives a positive response to the message, the server 106 may then transmit the first user's information to the second user device 108 as described above. Otherwise, if the server 106 receives a negative response or no response to the message, the server 106 may determine that the second user device 108 is malicious, and may not proceed to send the first user's information to the second user device 108.

In other examples, authentication may be location based. In particular, the first and second user devices may be configured to determine their respective locations, e.g. using GPS and/or GNSS protocols. At step 5305, the first and second user device may transmit location data to the server 106. The sever 106 may determine whether the first and second user devices are within a threshold distance to one another. If the devices are within a threshold distance, the server 106 may determine that the second user device 108 is authentic and may proceed to transmit the first user's information to the second user device over the network. Otherwise, if the devices are not within a threshold distance, the server 106 may decline the second device's information request.

Other security protocols known in the art may also be used to ensure that the second user device 108 is in possession of the unique ID and is requesting the first user's information as a result of an authentic interaction according to the method of Figure 3.

The system 100 illustrated in Figure 1 corresponds to a centralised architecture comprising a server 106 that centrally stores the first user's information. In some embodiments, the system 100 may be implemented in a decentralised manner, e.g. using blockchain and/or distributed ledger technology. In such embodiments, the first user's information may be stored decentrally on the blockchain ledger instead of centrally on the server 106. This may provide further improved security to the system.

The object 110 is described above as comprising a NFC tag and the unque ID encoded on the NFC tag is read using NFC technology and protocols. However, in some embodiments, the NFC tag may be replaced with a RFID (radio frequency identification) tag. In such embodiments, the first and second devices may be configured to read the RFID tag using corresponding RFID technology and protocols as is known in the art.

Claims

CLAIMS1. A method of communicating information associated with a first user of a first user device to a second user of a second user device, the method comprising: determining, at the first user device, information associated with a unique ID; obtaining the unique ID at the second user device by scanning, using the second user device, an object comprising a near-field communications (NFC) tag encoded with the unique ID; and retrieving, at the second user device, the information associated with the unique ID.
2. The method of claim 1, further comprising: transmitting, over a network, the information determined at the first user device to a server that stores the determined information in association with the unique ID; wherein the second user device retrieves the information associated with the unique ID from the server in response to obtaining the unique ID from the object.
3. The method of any preceding claim, wherein the retrieving further comprises requesting the information from the server based at least in part on the unique ID, and receiving the information over the network.
4. The method of any preceding claim, further comprising retrieving, with the first user device, information that is already stored on the server in association with the unique ID, and wherein determining the information associated with the unique ID comprises providing user input to the first user device to delete information that is already stored on the server in association with the unique ID and/or add to information that is already stored on the server in association with the unique ID.
5. The method of any preceding claim, wherein the information determined at the first user device comprises public information associated with the unique ID and private information associated with the unique ID, and wherein the retrieving comprises retrieving at least the public information and not the private information, optionally wherein determining the public information and the private information comprises receiving user input at the first user device to select which of the determined information is public information or private information.
6. The method of any preceding claim, further comprising displaying the retrieved information on the second user device, and optionally performing an action on the second user device that is associated with the retrieved information in response to receiving user input to select the retrieved information, optionally wherein the retrieved information is associated with an application on the second user device, and the action comprises opening, on the second user device, the application that is associated with the retrieved information.
7. The method of any preceding claim, further comprising automatically performing an action at the second user device in response to retrieving the information, optionally wherein the retrieved information is associated with an application on the second user device, and the automatic action comprising automatically opening, on the second user device, the application that is associated with the retrieved information.
8. The method of any preceding claim, wherein the determined information is indicative of the first user's identification according to at least one third party service and/or platform.
9. The method of any preceding claim, wherein the object further comprises electronic circuitry configured to perform a contactless payment protocol with a point of sale payment terminal and/or wherein the object is a wearable object.
10. A computer program, or suite of computer programs, configured to, when run on a processors, cause a computing devices to carry out the steps of any of claims 1 to 9.
11. A computer-readable storage medium or a plurality of computer-readable storage media comprising the computer program or suite of computer programs of claim 10.
12. A system for communicating information, comprising: a first user device configured to receive user input to determine information associated with a unique ID, the unique ID being associated with a first user of the first user device; and a second user device configured to: obtain the unique ID by scanning an object comprising a near-field communications (NFC) tag encoded with the unique ID; and retrieve the information associated with the unique ID based on the unique ID.
13. The system of claim 12, further comprising: transmitting, over a network, the information determined at the first user device to a server configured to store the determined information in association with the unique ID; and wherein the second user device is configured to retrieve the information associated with the unique ID from the server in response to obtaining the unique ID.
14. The system of any of claims 12 or 13, wherein the second user device is configured to retrieve the information by requesting the information from the server over the network based at least in part on the unique ID, and receive the information over the network.
15. The system of any of claims 12 to 14, wherein the first user device is configured to receive user input to deleting information that is already stored on the server in association with the unique ID and/or add to information that is already stored on the server in association with the unique ID.
16. The system of any of claims 12 to 15, wherein the information determined at the first user device comprises public information associated with the unique ID and private information associated with the unique ID, and wherein the retrieving comprises retrieving at least the public information and not the private information, optionally wherein the first user device is configured to receive user input to select which of the determined information is public information or private information.
17. The system of any of claims 12 to 16, wherein the second user device is configured to display the retrieved information, and optionally perform an action that is associated with the retrieved information in response to receiving user input to select the retrieved information, optionally wherein the retrieved information is associated with an application on the second user device, and the action comprises opening, on the second user device, the application that is associated with the retrieved information.
18. The system of any of claims 12 to 17, wherein the second user device is configured to automatically perform an action device in response to retrieving the information, and optionally wherein the retrieved information is associated with an application on the second user device, and the automatic action comprises automatically opening, on the second user device, the application that is associated with the retrieved information.
19. The system of any of claims 12 to 18, wherein the determined information is indicative of the first user's identification according to a third party service and/or platform.
20. The system of any of claims 12 to 19, wherein the object further comprises electronic circuitry configured to perform a contactless payment protocol with a point of sale payment terminal and/or wherein the object is a wearable object.
21. An object for use in the method of any of claims 1 to 11 or the system of any of claims 12 to 20, comprising a body embedded with a near-field communications (NFC) tag, the NFC tag being encoded with a unique ID.
22. The object of claim 21, wherein the object is: substantially rectangular, optionally having a length of less than 90mm, a width of less than 60mm, and a thickness of less than 2mm; or substantially circular, optionally having a diameter of less than 50mm, and a thickness of less than 2mm.
23. The object of any of claims 21 to 22, wherein the body has a first major surface and a second major surface, the object comprising a ferrite coating on the first or the second major surface, optionally wherein: the body is made of a plastic material and/or the object further comprises an adhesive coating on the ferrite layer.
24. The object of any of claims 21 to 23, wherein the object further comprises electronic circuitry configured to perform a contactless payment protocol with a point of sale payment terminal.
25. The object of any of claims 21 to 24, wherein the object is a wearable object, optionally wherein the object is a ring or a bracelet.