System and Method for Determining Trust for SIP Messages

• US 20160330249A1
• Filed: 06/27/2016
• Published: 11/10/2016
• Est. Priority Date: 04/13/2009
• Status: Active Grant

• Current Assignee: Blackberry Limited
• Original Assignee: Blackberry Limited
• Inventors: Bakker, Jan Hendrik Lucas, Allen, Andrew Michael, Buckley, Adrian
• Granted Patent: US 10,135,885 B2
• Time in Patent Office: Days
• 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 performed by a first network node of an IMS Network, the method comprising:

receiving, at the first network node, a Uniform Resource Identifier (URI) in a header field in a first SIP message;

receiving, at the first network node, a token in the header field in the first SIP message, the token indicative of a type of a network node in a path of the first SIP message; and

based on the received token, sending, from the first network node, a second SIP message including the received URI, the second SIP message conveying information about the first network node.

2. The method as claimed in claim 1, further comprising:

receiving a third SIP message triggered by the first SIP message.

3. The method as claimed in claim 2, wherein the third SIP message triggered by the first SIP message involves a configuration by initial Filter Criteria.

4. The method as claimed in claim 2, wherein the third SIP message is a third party SIP REGISTER message.

5. The method as claimed in claim 1, wherein the token is a parameter associated with the received URI.

6. The method as claimed in claim 1, wherein a second network node is in the path of the first SIP message, the second network of the same type as the type of the network node in the path of the first SIP message.

7. The method as claimed in claim 1, wherein the first SIP message is a SIP REGISTER message.

8. The method as claimed in claim 1, wherein the first SIP message is one of a SIP request and a SIP response.

9. A system, comprising:

a first network node of an IMS Network, the first network node configured to;

receive a Uniform Resource Identifier (URI) in a header field in a first SIP message;

receive a token in the header field in the first SIP message, the token indicative of a type of a network node in a path of the first SIP message; and

based on the received token, send a second SIP message including the received URI, the second SIP message conveying information about the first network node.

10. The system as claimed in claim 9, wherein the first network node is further configured to receive a third SIP message triggered by the first SIP message.

11. The system as claimed in claim 10, wherein the third SIP message triggered by the first SIP message involves a configuration by initial Filter Criteria.

12. The system as claimed in claim 10, wherein the third SIP message is a third party SIP REGISTER message.

13. The system as claimed in claim 9, wherein the token is a parameter associated with the received URI.

14. The system as claimed in claim 9, wherein a second network node is in the path of the first SIP message, the second network of the same type as the type of the network node in the path of the first SIP message.

15. The system as claimed in claim 9, wherein the first SIP message is a SIP REGISTER message.

16. The system as claimed in claim 9, wherein the first SIP message is one of a SIP request and a SIP response.

17. A computer program product comprising a non-transitory tangible computer readable storage medium having instructions stored thereon that, when executed by a processing device, implement a method performed by a first network node of an IMS Network, the method comprising:

receiving a Uniform Resource Identifier (URI) in a header field in a first SIP message;

receiving a token in the header field in the first SIP message, the token indicative of a type of a network node in a path of the first SIP message; and

based on the received token, sending a second SIP message including the received URI, the second SIP message conveying information about the first network node.

18. The computer program product as claimed in claim 17, further comprising:

receiving a third SIP message triggered by the first SIP message.

19. The computer program product as claimed in claim 18, wherein the third SIP message triggered by the first SIP message involves a configuration by initial Filter Criteria.

20. The computer program product as claimed in claim 18, wherein the third SIP message is a third party SIP REGISTER message.

21. The computer program product as claimed in claim 17, wherein the token is a parameter associated with the received URI.

22. The computer program product as claimed in claim 17, wherein a second network node is in the path of the first SIP message, the second network of the same type as the type of the network node in the path of the first SIP message.

23. The computer program product as claimed in claim 17, wherein the first SIP message is a SIP REGISTER message.

24. The computer program product as claimed in claim 17, wherein the first SIP message is one of a SIP request and a SIP response.

25. A system, comprising:

a first network node of an IMS Network, the first network node comprising;

a receiver configured to receive a Uniform Resource Identifier (URI) in a header field in a first SIP message and a token in the header field in the first SIP message, the token indicative of a type of a network node in a path of the first SIP message; and

a transmitter configured to send, based on the received token, a second SIP message including the received URI, the second SIP message conveying information about the first network node.