System and method for addressing a unique device from a common address book

• US 9,396,225 B2
• Filed: 09/06/2013
• Issued: 07/19/2016
• Est. Priority Date: 01/29/2008
• Status: Active Grant

• Current Assignee: Malikie Innovations Limited (Key Patent Innovations Limited)
• Original Assignee: Blackberry Limited
• Inventors: Kim, Youngae, Buckley, Adrian, Allen, Andrew Michael, Bakker, Jan Hendrik Lucas, Alfano, Nicholas Patrick, Linkert, Barry, Martin-Cocher, Galle Christine, Chitturi, Suresh, McColgan, Brian Edward Anthony
• Primary Examiner(s): BAYOU, YONAS A
• Application Number:
  US14/020,044
• Publication Number:
  US 20140006460A1
• Time in Patent Office: 1,047 Days
• Field of Search: 726/9
• US Class Current: 1/1
• CPC Class Codes: G06F 16/2291 User-Defined Types; Storage management thereof
• CPC Class Codes: H04L 2101/39 Globally routable user-agent uniform resource identifier [GRUU] for the session initiation protocol [SIP]
• CPC Class Codes: H04L 61/30 Managing network names, e.g. use of aliases or nicknames name-to-address mapping H04L61/45
• CPC Class Codes: H04L 61/45 Network directories; Name-to-address mapping
• CPC Class Codes: H04L 61/4594 Address books, i.e. directories containing contact information about correspondents telephone directories in user terminals H04M1/27453
• CPC Class Codes: H04L 65/1016 IP multimedia subsystem [IMS]
• CPC Class Codes: H04M 1/2535 adapted for voice communication over an Internet Protocol [IP] network Voice over Internet Protocol (VoIP) network equipment and services H04M7/006; implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP] H04L69/16
• CPC Class Codes: H04M 1/2753 providing data content

Abstract

A method and system for addressing a unique device from an address book, the method having the steps of: receiving a message having a root token and a secondary token; checking whether the root token exists within the address book, if no, creating a record in the address book with the root and secondary token; and if yes, checking whether the secondary token exists within the address book, if yes, providing a representation of the unique device; and if no, storing the secondary token against the root token in the address book.

Claims

1. A method for storing device data for a device in an address book stored in a memory, the method comprising:

using a processor operably coupled with a communications subsystem and the memory, performing;

receiving an electronic message from the device comprising a public user identity of a user and an instance identifier for the device;

determining that the public user identity exists within the address book and the instance identifier does not exist within the address book; and

responsive to the determining, performing;

storing the instance identifier in the address book in association with the public user identity, wherein the instance identifier in combination with the public user identity uniquely identifies the device;

assigning a device identifier nickname representing a relationship between the public user identity and the device;

storing in the address book the device identifier nickname in a device identifier nickname field associated with the instance identifier;

storing in the address book device capabilities of the device in a device capabilities field associated with the instance identifier;

receiving a user selection from a user interface associated with the address book, the user selection identifying the device identifier nickname; and

initiating a communication with the device based on the user selection.

2. The method of claim 1, wherein the public user identity is selected from the group consisting of a session initiation protocol uniform resource identifier, a telephone uniform resource identifier;

and a mobile systems international subscriber identity number.

3. The method of claim 1, wherein the device identifier nickname is at least one of alphanumeric text, a graphic, a picture, a sound, a link to alphanumeric text, a link to a graphic, a link to a picture, and a link to a sound.

4. The method of claim 1, wherein storing the device capabilities further comprises adding contact properties.

5. The method of claim 1, wherein the storing in the address book device capabilities of the device in the device capabilities field associated with the instance identifier further comprises associating tokens identifying device capabilities against the instance identifier.

6. The method of claim 5, wherein the tokens identifying device capabilities include one or a plurality of tokens selected from the group of:

a media token;

an instant messaging service communication service identifier;

a user agent profile;

an instant messaging service application reference identifier; and

a device profile evolution.

7. The method of claim 1, wherein storing the device capabilities further comprises storing a realm in which the unique device is operating.

8. The method of claim 1, wherein the address book is a network based address book.

9. The method of claim 1, wherein the message has a message type selected from the group consisting of:

a session initiation protocol message;

an email message, and

a hypertext transfer protocol message.

10. A computing device adapted for storing device data for a device in an address book stored in a memory, the computing device comprising:

a communications subsystem configured to receive an electronic message from the device comprising a public user identity of a user and an instance identifier for the device; and

a processor operably coupled with the communications subsystem and the memory, wherein the processor is configured to;

determine that the public user identity exists within the address book and the instance identifier does not exist within the address book;

when it is determined that the public user identity exists within the address book and the instance identifier does not exist within the address book;

store the instance identifier in the address book in association with the public user identity, wherein the instance identifier in combination with the public user identity uniquely identifies the device;

assign a device identifier nickname representing a relationship between the public user identity and the device;

store in the address book the device identifier nickname in a device identifier nickname field associated with the instance identifier;

store in the address book device capabilities of the device in a device capabilities field associated with the instance identifier

receive a user selection from a user interface associated with the address book, the user selection identifying the device identifier nickname; and

initiate a communication with the device based on the user selection.

11. The computing device of claim 10, wherein the device identifier nickname is at least one of alphanumeric text, a graphic, a picture, a sound, a link to alphanumeric text, a link to a graphic, a link to a picture, and a link to a sound.

12. The computing device of claim 11, wherein the processor is further configured to store the device capabilities as tokens identifying device capabilities against the instance identifier.

13. The computing device of claim 12, wherein the tokens identifying device capabilities include one or a plurality of tokens selected from the group of:

a media token;

an instant messaging service communication service identifier;

a user agent profile,

an instant messaging service application reference identifier; and

a device profile evolution.

14. The computing device of claim 10, wherein the message has a message type selected from the group consisting of:

a session initiation protocol message;

an email message, and a hypertext transfer protocol message.

15. A non-transitory computer readable medium storing a computer program product, which when executed by a processor of a computing device is configured to:

receive an electronic message from the device comprising a public user identity of a user and an instance identifier for a device;

determine that the public user identity exists within an address book stored in a memory of the device and the instance identifier does not exist within the address book;

when it is determined that the public user identity exists within the address book and the instance identifier does not exist within the address book;

store the instance identifier in the address book in association with the public user identity, wherein the instance identifier in combination with the public user identity uniquely identifies the device;

assign a device identifier nickname representing a relationship between the public user identity and the device;

store in the address book the device identifier nickname in a device identifier nickname field associated with the instance identifier;

store in the address book device capabilities of the device in a device capabilities field associated with the instance identifier;

receive a user selection from a user interface associated with the address book, the user selection identifying the device identifier nickname; and

initiate a communication with the device based on the user selection.