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

• US 8,549,603 B2
• Filed: 01/29/2009
• Issued: 10/01/2013
• Est. Priority Date: 01/29/2008
• Status: Active Grant

• Current Assignee: Malikie Innovations Limited (Key Patent Innovations Limited)
• Original Assignee: Blackberry Limited
• Inventors: Buckley, Adrian, Allen, Andrew Michael, Kim, Young Ae, Bakker, Jan Hendrik Lucas, Alfano, Nicholas, Linkert, Barry, Martin-Cocher, Gaelle Christine, Chitturi, Suresh, McColgan, Brian Edward Anthony
• Primary Examiner(s): Zand, Kambiz
• Assistant Examiner(s): BAYOU, YONAS A
• Application Number:
  US12/361,982
• Publication Number:
  US 20090193512A1
• Time in Patent Office: 1,706 Days
• Field of Search: 726/9
• US Class Current: 726/9
• 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 addressing a unique device from an address book comprising:

receiving a message including a public user identity and an instance identifier for the unique device;

determining that the public user identity exists within the address book and the instance identifier does not exist within the address book, storing the instance identifier against the public user identity in said address book; and

associating tokens identifying device capabilities against the instance identifier;

wherein the instance identifier is selected from the group consisting of;

a medium access control address, an international mobile equipment identity, an electronic serial number, and a personal identification number.

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 at least one of the creating step and the storing step further comprises adding a nickname for the unique device.

4. The method of claim 3, wherein the 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.

5. The method of claim 1, wherein at least one of the creating step and the storing step further comprises adding contact properties.

6. The method of claim 1, 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 tokens identifying device capabilities are stored based on a realm the unique device is operating in.

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 addressing a unique device from an address book stored in a memory comprising:

a communications subsystem configured to receive a message including a public user identity and an instance identifier for the unique device; and

a processor, 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, store the instance identifier against the public user identity in said address book;

associate tokens identifying device capabilities against the instance identifier;

wherein the instance identifier is selected from the group consisting of;

a medium access control address, an international mobile equipment identity, an electronic serial number, and a personal identification number.

11. The computing device of claim 10, further comprising a nickname stored in the memory for the unique device.

12. The computing device of claim 11, wherein the 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.

13. The computing device of claim 10, 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 computer program product, comprising a non-transitory computer usable medium having a computer readable data structure embodied therein, said computer readable data structure comprising:

a contact card, the contact card comprising an instance identifier field, the instance identifier field uniquely identifying a device;

a device identifier nickname field;

a device capabilities field, the device capabilities field identifying the capabilities of the device; and

a contact properties field,

wherein the instance identifier field or device identifier nickname field provide an address book with a relationship between a public user identity and the device.

16. The computer program product of claim 15, wherein the contact properties field provides a status of a contact.

17. The computer program product of claim 15, wherein the device capabilities field provides service and media capabilities of a device of a contact.

18. The computer program product of claim 15, wherein the contact card is a versitcard.