System and method for SIP user agent identification and efficient binding

• US 9,148,482 B2
• Filed: 08/26/2014
• Issued: 09/29/2015
• Est. Priority Date: 04/05/2011
• Status: Active Grant

• Current Assignee: Malikie Innovations Limited (Key Patent Innovations Limited)
• Original Assignee: Blackberry Limited
• Inventors: Rozinov, Boris, John Chuan, Mee Tchin Jane, Pang, Swee Tuan, Kramarenko, Valentina Iqorevna
• Primary Examiner(s): Kim, Hee Soo
• Application Number:
  US14/468,414
• Publication Number:
  US 20140365674A1
• Time in Patent Office: 399 Days
• US Class Current: 1/1
• CPC Class Codes: H04L 2101/30 Types of network names
• CPC Class Codes: H04L 2101/385 Uniform resource identifier for session initiation protocol [SIP URI]
• CPC Class Codes: H04L 61/2575 using address mapping retrieval, e.g. simple traversal of user datagram protocol through session traversal utilities for NAT [STUN]
• CPC Class Codes: H04L 61/4535 using an address exchange platform which sets up a session between two nodes, e.g. rendezvous servers, session initiation protocols [SIP] registrars or H.323 gatekeepers
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 63/083 using passwords cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226
• CPC Class Codes: H04L 63/108 when the policy decisions are valid for a limited amount of time
• CPC Class Codes: H04L 63/1458 Denial of Service
• CPC Class Codes: H04L 63/20 for managing network security; network security policies in general filtering policies H04L63/0227
• CPC Class Codes: H04L 65/1073 Registration or de-registration
• CPC Class Codes: H04L 65/1104 Session initiation protocol [SIP]
• CPC Class Codes: H04L 67/143 Termination or inactivation of sessions, e.g. event-controlled end of session
• CPC Class Codes: H04L 67/147 Signalling methods or messages providing extensions to protocols defined by standardisation

Abstract

The present disclosure provides a system and method for Session Initiation Protocol (SIP) user agent identification and efficient binding. In accordance with one example embodiment, there is provided a method for use on a Session Initiation Protocol (SIP) registration server for registering user agents, comprising: receiving a REGISTER message which includes a binding key; determining whether a prior binding associated with the binding key exists in a registration repository; and creating a new binding associated with the binding key and adding the new binding to the registration repository when no prior binding associated with the binding key exists in the registration repository.

Claims

1. A non-transitory computer-readable medium storing program instructions that when executed by a processor cause the processor to:

register user agents on a Session Initiation Protocol (SIP) registration server;

receive a REGISTER message which includes a binding key located in a Contact header of the REGISTER message, wherein the binding key comprises a Contact Uniform Resource Identifier (URI) and identifying information for a device associated with a user agent to be registered;

determine whether a prior binding associated with the binding key exists in a registration repository;

create a new binding associated with the binding key and adding the new binding to the registration repository when no prior binding associated with the binding key exists in the registration repository; and

refresh the prior binding in the registration repository when the prior binding associated with the binding key exists in the registration repository.

2. The non-transitory computer-readable medium of claim 1, that when executed by the processor further cause the processor to:

determine whether the REGISTER message specifies an expiration interval when the prior binding associated with the binding key exists in the registration repository;

remove the prior binding from the registration repository when the REGISTER message specifies an expiration interval of 0; and

refresh the prior binding in the registration repository when the REGISTER message does not specify an expiration interval of 0.

3. The non-transitory computer-readable medium of claim 1, further comprising:

validating registration parameters for the prior binding in the registration repository when the prior binding associated with the binding key exists in the registration repository.

4. The non-transitory computer-readable medium of claim 1, wherein the identifying information is a unique identifier.

5. The non-transitory computer-readable medium of claim 1, wherein the identifying information is a personal identification number (PIN).

6. The non-transitory computer-readable medium of claim 1, wherein the identifying information is a personal identification number (PIN) and user name.

7. The non-transitory computer-readable medium of claim 1, further comprising:

adding a connection-binding mapping to the registration repository when a user agent to be registered uses a connection-oriented protocol.

8. A non-transitory computer-readable medium storing program instructions that when executed by a processor of a user agent, cause the processor to register with a Session Initiation Protocol (SIP) registration server, the method comprising:

sending a REGISTER message to the SIP registration server, wherein the REGISTER message includes a binding key located in a Contact header of the REGISTER message, wherein the binding key comprises a Contact Uniform Resource Identifier (URI) and identifying information for a device associated with a user agent to be registered.

9. The non-transitory computer-readable medium of claim 8, wherein the identifying information is a unique identifier.

10. The non-transitory computer-readable medium of claim 8, wherein the identifying information is a personal identification number (PIN).

11. The non-transitory computer-readable medium of claim 8, wherein the identifying information is a personal identification number (PIN) and user name.

12. A user agent for registering with a Session Initiation Protocol (SIP) registration server, the user agent having a processor coupled to a memory, the processor being configured to:

send a REGISTER message to the SIP registration server, wherein the REGISTER message includes a binding key located in a Contact header of the REGISTER message, wherein the binding key comprises a Contact Uniform Resource Identifier (URI) and identifying information for a device associated with the user agent to be registered.

13. The user agent of claim 12, wherein the identifying information is a unique identifier.

14. The user agent of claim 12, wherein the identifying information is a personal identification number (PIN).

15. The user agent of claim 12, wherein the identifying information is a personal identification number (PIN) and user name.