System and method for determining trust for SIP messages
A method performed by a first network node of an IMS Network is provided. The method includes 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 message conveying information about the first network node.
1. 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;
responsive to the receiving, sending a second SIP message, wherein the second SIP message is a SIP 200 OK response; and
based on the received token, sending a third SIP message including the received URI, the third SIP message conveying information about the first network node.
2. The method as claimed in claim 1 , further comprising: receiving a fourth SIP message triggered by the first SIP message.
3. The method as claimed in claim 2 , wherein the fourth 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 fourth 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 the second network node is in a 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;
responsive to the received token, send a second SIP message, wherein the second SIP message is a SIP 200 OK response; and
based on the received token, send a third SIP message including the received URI, the third 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 fourth SIP message triggered by the first SIP message.
11. The system as claimed in claim 10 , wherein the fourth 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 fourth 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 the second network node is in a 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;
responsive to the receiving, sending a second SIP message, wherein the second SIP message is a SIP 200 OK response; and
based on the received token, sending a third SIP message including the received URI, the third SIP message conveying information about the first network node.
18. The computer program product as claimed in claim 17 , further comprising: receiving a fourth SIP message triggered by the first SIP message.
19. The computer program product as claimed in claim 18 , wherein the fourth 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 fourth 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 the second network node is in a 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.