System and method for session initiation protocol header modification
View Patent ↗A user agent (UA) for communicating with a communications network implementing an internet protocol (IP) multimedia subsystem (IMS) is presented. The UA is configured to send and receive session initiation protocol (SIP) messages. The UA includes a processor configured to send a message to the network. The message identifies an application policy. The application policy defines at least one of a SIP message header field to include, a SIP message header field to remove, a SIP message header field to allow, and a SIP message header field to modify. The processor is configured to receive a SIP message from the network. The SIP message includes a set of SIP message header fields. The set of SIP message header fields are modified in accordance with the application policy.
1. A user agent (UA) for communicating with a communications network implementing an internet protocol (IP) multimedia subsystem (IMS), the UA being configured to send and receive session initiation protocol (SIP) messages, the UA comprising:
a processor, the processor being configured to:
receive a request for an application policy from a network entity;
send a message to the network entity in response to the request for the application policy, the message identifying an application policy, and
receive, from the network entity, status information of an application of the application policy, wherein the status information identifies a first portion of the application policy that was successfully applied and a second portion of the application policy that was not successfully applied.
2. The UA of claim 1 , wherein the UA is at least one of a third generation partnership project (3GPP) user equipment, a wireless device, a set-top box, a phone, a computer, and a SIP user agent.
3. The UA of claim 1 , wherein the message includes a uniform resource identifier (URI), the URI identifying a location of the application policy within a database.
4. The UA of claim 1 , wherein the message contains the application policy.
5. The UA of claim 4 , wherein the application policy is encoded using extensible markup language (XML).
6. The UA of claim 1 , wherein the message includes at least one of a SIP SUBSCRIBE, a SIP REGISTER, a SIP MESSAGE, a SIP INFO, a SIP OPTION, a SIP PUBLISH, and a SIP REFER request.
7. The UA of claim 1 , wherein the message includes a SIP signaling compression (SigComp) transmission.
8. The UA of claim 1 , wherein the message includes a message session relay protocol (MSRP) message after a SIP session is established between the UA and a policy provider.
9. The UA of claim 1 , wherein the application policy identifies a SIP message header field to remove, and wherein the processor is configured to:
receive a modified SIP message, wherein the SIP message header field identified by the application policy is not included in the modified SIP message.
10. The UA of claim 1 , wherein the application policy identifies a SIP message header field to modify, and wherein the processor is configured to:
receive a modified SIP message, wherein the SIP message header field identified by the application policy is modified in accordance with the application policy in the modified SIP message.
11. The UA of claim 1 , wherein the application policy identifies a SIP message header field to include, and wherein the processor is configured to:
receive a modified SIP message, wherein the SIP message header field identified by the application policy is included in the modified SIP message.
12. The UA of claim 11 , wherein the application policy further identifies an attribute of the at least one of a SIP message header field to include, a SIP message header field to remove, and a SIP message header field to modify, the attribute including at least one of an indication of message direction, an identifier of a service or application, a SIP method name, and a SIP response code.
13. A user agent (UA) for communicating with a communications network implementing an internet protocol (IP) multimedia subsystem (IMS), the UA being configured to send and receive session initiation protocol (SIP) messages, the UA comprising:
a processor, the processor being configured to:
receive, from the network entity, status information identifying a first portion of an application policy associated with the UA that was successfully applied and a second portion of the application policy that was not successfully applied, and
receive a SIP message from the network, the SIP message including a set of modified via headers, the set of modified via headers being modified by an application server of the communications network in accordance with the first portion of the application policy associated with the UA.
14. The UA of claim 13 , wherein the UA is at least one of a third generation partnership project (3GPP) user equipment, a wireless device, a set-top box, a phone, a computer, and a SIP user agent.
15. The UA of claim 13 , wherein the application policy identifies a SIP message header field to remove, and wherein the processor is configured to:
receive a modified SIP message, wherein the SIP message header field identified by the application policy is not included in the modified SIP message.
16. The UA of claim 13 , wherein the application policy identifies a SIP message header field to modify, and wherein the processor is configured to:
receive a modified SIP message, wherein the SIP message header field identified by the application policy is modified in accordance with the application policy in the modified SIP message.
17. The UA of claim 13 , wherein the application policy identifies a SIP message header field to include, and wherein the processor is configured to:
receive a modified SIP message, wherein the SIP message header field identified by the application policy is included in the modified SIP message.
18. The UA of claim 13 , wherein the application policy further identifies an attribute of the at least one of a SIP message header field to include, a SIP message header field to remove, a SIP message header field to allow, and a SIP message header field to modify, the attribute including at least one of an indication of message direction, an identifier of a service or application, a SIP method name, and a SIP response code.
19. A method of communicating with a communications network implementing an internet protocol (IP) multimedia subsystem (IMS), comprising:
receiving a request for an application policy from a network entity;
sending a message to the network entity in response to the request for the application policy, the message identifying an application policy, and
receiving, from the network entity, status information of an application of the application policy, wherein the status information identifies a first portion of the application policy that was successfully applied and a second portion of the application policy that was not successfully applied.
20. The method of claim 19 , wherein the message includes a uniform resource identifier (URI), the URI identifying a location of the application policy within a database.
21. The method of claim 19 , wherein the message contains the application policy.
22. The method of claim 21 , wherein the application policy is encoded using extensible markup language (XML).
23. The method of claim 19 , wherein the message includes at least one of a SIP SUBSCRIBE, a SIP REGISTER, a SIP MESSAGE, a SIP INFO, a SIP OPTION, a SIP PUBLISH, and a SIP REFER request.
24. The method of claim 19 , wherein the message includes a SIP signaling compression (SigComp) transmission.
25. The method of claim 19 , wherein the message includes a message session relay protocol (MSRP) message after a SIP session is established between the UA and a policy provider.