System and method for determining trust for SIP messages

• US 9,401,935 B2
• Filed: 10/29/2010
• Issued: 07/26/2016
• Est. Priority Date: 04/13/2009
• Status: Active Grant

• Current Assignee: Blackberry Limited
• Original Assignee: Blackberry Limited
• Inventors: Bakker, Jan Hendrik Lucas, Buckley, Adrian, Allen, Andrew
• Primary Examiner(s): BURGESS, BARBARA N
• Application Number:
  US12/915,649
• Publication Number:
  US 20110047277A1
• Time in Patent Office: 2,097 Days
• Field of Search: 709/203, 709/206, 709/207, 709/223, 709/224, 709/227
• US Class Current: 1/1
• CPC Class Codes: G06F 11/2007 using redundant communication media
• CPC Class Codes: G06F 3/1203 Improving or facilitating administration, e.g. print management
• CPC Class Codes: H04L 2101/385 Uniform resource identifier for session initiation protocol [SIP URI]
• CPC Class Codes: H04L 51/212 using filtering or selective blocking
• CPC Class Codes: H04L 63/126 the source of the received data
• CPC Class Codes: H04L 65/1016 IP multimedia subsystem [IMS]
• CPC Class Codes: H04L 65/1073 Registration or de-registration
• CPC Class Codes: H04L 65/1101 Session protocols
• CPC Class Codes: H04L 65/1104 Session initiation protocol [SIP]
• CPC Class Codes: H04L 65/403 Arrangements for multi-party communication, e.g. for conferences data switching systems for conference H04L12/18; arrangements for connecting several subscribers to a common circuit, i.e. affording conference facilities H04M3/56; television conferencing systems H04N7/15
• CPC Class Codes: H04L 65/611 for multicast or broadcast systems for broadcast or conference H04L12/18; arrangements for broadcast or distribution combined with broadcast H04H20/00; arrangements for broadcast applications with a direct linkage to broadcast information or to broadcast space-time H04H60/00; selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS], H04W4/06
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
• CPC Class Codes: H04L 69/22 Parsing or analysis of headers
• CPC Class Codes: H04L 69/40 for recovering from a failure of a protocol instance or entity, e.g. service redundancy protocols, protocol state redundancy or protocol service redirection management of faults, events, alarms or notifications in data switching networks H04L41/06
• CPC Class Codes: H04L 9/083 involving central third party, e.g. key distribution center [KDC] or trusted third party [TTP]
• CPC Class Codes: H04W 12/10 Integrity

Abstract

A method for performing initial registration is provided. The method includes receiving a server timeout message, the server timeout message including at least a field set to a value equal to a value received during a first registration. The method further includes initiating restoration procedures by performing an initial registration.

Claims

1. A method for handling service restoration by a network node in a Session Initiation Protocol (SIP) based network, the method comprising:

receiving a SIP request from a user equipment (UE), and responsive to receiving the SIP request, attempting to retrieve a user'"'"'s profile from a home subscriber server; and

responsive to detecting a failure to retrieve the user'"'"'s profile from the home subscriber server, sending a first SIP response to the UE of the user, the first SIP response being a SIP server timeout message, the SIP server timeout message including an indication indicating support for restoration procedures, the SIP server timeout message further including at least a first field set to a value equal to a value provided in a Service-Route header field, the Service-Route header field included in a second SIP response to a SIP REGISTER request of the UE, the SIP REGISTER request sent by the UE of the user;

wherein the value sent in the SIP server timeout message includes a Uniform Resource Identifier (URI) representative of the network node in the SIP-based network, the value being usable by the UE to compare with the value provided in the Service-Route header field.

2. The method as claimed in claim 1, wherein the URI is a SIP URI.

3. The method as claimed in claim 1, wherein the first field comprises a P-Asserted-Identify header field.

4. The method as claimed in claim 1, wherein the network node is a Serving Call Session Control Function (S-CSCF).

5. The method as claimed in claim 1, wherein the network node is a network node within a trust domain.

6. The method as claimed in claim 1, wherein the network node is a network node performing services.

7. The method as claimed in claim 1, wherein the SIP request from the user equipment (UE) comprises one of an initial request for a dialog and a request for a standalone transaction.

8. The method as claimed in claim 1, wherein the UE determines that a network node represented by the value provided in the Service-Route header field is the same as the network node represented by the URI by a comparison of the value sent in the SIP server timeout message and the value provided in the Service-Route header field resulting in a match therebetween.

9. The method as claimed in claim 1, wherein the attempt to retrieve the user profile from the home subscriber server is based upon one of:

the network node does not have the user profile, or does not trust data that it has.

10. A user agent (UA) to handle service restoration by a network node in a Session Initiation Protocol (SIP) based network, the UA comprising:

at least one storage device, and

one or more processors configured to execute instructions stored on the at least one storage device such that when executed, cause the one or more processors to;

receive, via at least one transceiver on the UA, a SIP request from a user equipment (UE), and responsive to receiving the SIP request, attempt to retrieve a user'"'"'s profile from a home subscriber server; and

responsive to detecting a failure to retrieve the user'"'"'s profile from the home subscriber server, send, via the at least one transceiver, a first SIP response to the UE of the user, the first SIP response being a SIP server timeout message, the SIP server timeout message including an indication indicating support for restoration procedures, the SIP server timeout message further including a first field set to a value equal to a value provided in a Service-Route header field during a first registration, the Service-Route header field included in a second SIP response to a SIP REGISTER request, the SIP REGISTER request sent by the UE of the user;

wherein the value sent in the SIP server timeout message includes a Uniform Resource Identifier (URI) representative of the network node, the value being usable by the UE to compare with the value provided in the Service-Route header field.

11. The UA as claimed in claim 10, wherein the URI is a SIP URI.

12. The UA as claimed in claim 10, wherein the first field comprises a P-Asserted-Identity header field.

13. The UA as claimed in claim 10, wherein the network node is a Serving Call Session Control Function (S-CSCF).

14. The UA as claimed in claim 10, wherein the network node is a network node within a trust domain.

15. The UA as claimed in claim 10, wherein the network node is a network node performing services.

16. The UA as claimed in claim 10, wherein the SIP request from the user equipment (UE) comprises one of an initial request for a dialog and a request for a standalone transaction.

17. The UA as claimed in claim 10, wherein the UE determines that a network node represented by the value provided in the Service-Route header field is the same as the network node represented by the URI by a comparison of the value sent in the SIP server timeout message and the value provided in the Service-Route header field resulting in a match therebetween.

18. The UA as claimed in claim 10, wherein the attempt to retrieve the user profile from the home subscriber server is based upon one of:

the network node does not have the user profile, or does not trust data that it has.