# Patent

## Title
Globally routable user agent uniform resource identifier system and method

## Abstract

A system and method for concealing an identity by receiving a Session Initiation Protocol (SIP) message, the SIP message containing a field, the field containing a Globally Routable User Agent Uniform Resource Identifier (GRUU) identifying a node, the GRUU containing a public user identity (PUID), a ‘gr’ parameter, and a ‘gr’ parameter value; evaluating a subscription option; and in response to evaluating the subscription option, concealing an identity of the node by removing the ‘gr’ parameter and the ‘gr’ parameter value from the field.

## Background
CROSS-REFERENCE TO RELATED APPLICATIONS
The present application claims priority to U.S. Provisional Patent Application No. 60/955,272, filed Aug. 10, 2007, by John-Luc Bakker, et al, entitled “System and Method for Configuring and Executing CDIV with GRUU”; U.S. Provisional Patent Application No. 60/972,602, filed Sep. 14, 2007, by John-Luc Bakker, et al, entitled “System and Method for Configuring and Executing CDIV with GRUU”; U.S. Provisional Patent Application No. 60/979,018, filed Oct. 10, 2007, by John-Luc Bakker, et al, entitled “Communication Diversion using GRUUS”; and U.S. Provisional Patent Application No. 60/985,902, filed Nov. 6, 2007, by John-Luc Bakker, et al., entitled “Communication Diversion and Notification using GRUUS”, by John-Luc Bakker, et al, entitled “System and Method for Configuring and Executing CDIV with GRUU”, all of which are incorporated by reference herein as if reproduced in their entirety.


BACKGROUND
The IP (Internet Protocol) Multimedia Subsystem (IMS) is a standardized architecture for providing multimedia services and voice-over-IP calls to both mobile and fixed user agents (UAs). The Session Initiation Protocol (SIP) been standardized and governed primarily by the Internet Engineering Task Force (IETF) as a protocol for setting up and managing IMS-based calls. As used herein, the terms “user agent” and “UA” might in some cases refer to mobile devices such as mobile telephones, personal digital assistants, handheld or laptop computers, network nodes, and similar devices, etc., that have telecommunications capabilities. Such a UA might consist of a wireless device and its associated Universal Integrated Circuit Card (UICC) that includes a Subscriber Identity Module (SIM) application, a Universal Subscriber Identity Module (USIM) application, or a Removable User Identity Module (R-UIM) application or might consist of the device itself without such a card. In other cases, the term “UA” may refer to devices that have similar capabilities but that are not transportable, such as fixed line telephones, desktop computers, set-top boxes, or network nodes. When a UA is a network node, the network node could act on behalf of another function such as a wireless device or a fixed line device and simulate or emulate the wireless device or fixed line device. For example, for some wireless devices, the IMS SIP client that would typically reside on the device actually resides in the network and relays SIP message information to the device using optimized protocols. In other words, some functions that were traditionally carried out by a wireless device can be distributed in the form of a remote UA, where the remote UA represents the wireless device in the network. The term “UA” can also refer to any hardware or software component that can terminate a SIP session. Also, the terms “UA”, “user equipment”, “UE”, and “node” might be used synonymously herein.
Some nodes communicate in a circuit switched mode, wherein a dedicated communication path exists between two devices. For the duration of a call or session, all data exchanged between the two devices travels along the single path. Some nodes have the capability to communicate in a packet switched mode, wherein a data stream representing a portion of a call or session is divided into packets that are given unique identifiers. The packets might then be transmitted from a source to a destination along different paths and might arrive at the destination at different times. Upon reaching the destination, the packets are reassembled into their original sequence based on the identifiers.
Communications that take place via circuit switching can be said to occur in the circuit switched domain and communications that take place via packet switching can be said to occur in the packet switched domain. Within each domain, several different types of networks, protocols, or technologies can be used. In some cases, the same network, protocol, or technology can be used in both domains. The wireless communication networks may be based on Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiplexing (OFDM), or some other multiple access scheme. A CDMA-based network may implement one or more standards such as 3GPP2 IS-2000 (commonly referred to as CDMA 1x), 3GPP2 IS-856 (commonly referred to as CDMA 1xEV-DO), or 3GPP UMTS (Universal Mobile Telecommunications System). A TDMA-based network may implement one or more standards such as 3GPP Global System for Mobile Communications (GSM) or 3GPP General Packet Radio Service (GPRS).
GSM is an example of a wireless network standard that uses only the circuit switching mode. Examples of wireless network standards that use only packet switching include GPRS, CDMA 1x EV-DO, Worldwide Interoperability for Microwave Access (WiMAX), and Wireless Local Area Network (WLAN), which might comply with Institute of Electrical and Electronics Engineers (IEEE) standards such as 802.16, 802.16e, 802.11a, 802.11b, 802.11g, 802.11n, and similar standards. Examples of wireless network standards that may use both circuit switching and packet switching modes include CDMA 1x and UMTS. An example of an application-layer protocol that can be used in a packet switching wireless network is the Session Initiation Protocol (SIP). SIP has been standardized and governed primarily by the Internet Engineering Task Force (IETF). The IP (Internet Protocol) Multimedia Subsystem (IMS) is a packet switched technology that allows multimedia content to be transmitted between nodes.



BRIEF DESCRIPTION OF THE DRAWINGS
For a more complete understanding of this disclosure, reference is now made to the following brief description, taken in connection with the accompanying drawings and detailed description, wherein like reference numerals represent like parts.
FIG. 1 is a block diagram of a telecommunications system according to an embodiment of the disclosure.
FIG. 2 is a block diagram of a method for diverting a SIP message (i.e. SIP request or response) according to an embodiment of the disclosure.
FIG. 3 is a diagram of a wireless communications system including a node operable for some of the various embodiments of the disclosure.
FIG. 4 is a block diagram of a node operable for some of the various embodiments of the disclosure.
FIG. 5 is a diagram of a software environment that may be implemented on a node operable for some of the various embodiments of the disclosure.
FIG. 6 illustrates a processor and related components suitable for implementing the several embodiments of the present disclosure.



DETAILED DESCRIPTION
It should be understood at the outset that although illustrative implementations of one or more embodiments of the present disclosure are provided below, the disclosed systems and/or methods may be implemented using any number of techniques, whether currently known or in existence. The disclosure should in no way be limited to the illustrative implementations, drawings, and techniques illustrated below, including the exemplary designs and implementations illustrated and described herein, but may be modified within the scope of the appended claims along with their full scope of equivalents.
In an embodiment, a method for diverting a Session Initiation Protocol (SIP) message is provided. The method includes using at least one Globally Routable User Agent Uniform Resource Identifier (GRUU) to determine a recipient to which the SIP message is diverted. The method also includes concealing an identity present in the SIP message.
In an alternative embodiment, a system implementing a Communication Diversion (CDIV) service is provided. The system includes a plurality of nodes. At least some of the nodes are addressable by different Globally Routable User Agent Uniform Resource Identifiers (GRUUs). The system also includes a privacy rule for concealing an identity of at least one of the plurality of nodes.
In an alternative embodiment, a telecommunications network is provided. The telecommunications network includes a first component configured to store a rule for diverting a SIP message based on a comparison of a first Globally Routable User Agent Uniform Resource Identifier (GRUU) specified by a node in the network and a second GRUU in a header field part of the SIP message. When the first GRUU matches the second GRUU, the rule is followed to determine at least one of an intermediate target node from which the SIP message is diverted, a target node from which the SIP message is diverted, and a recipient node to which the SIP message is diverted. The telecommunications network also includes a second component configured to store a privacy rule for preventing an identity of at least one of the nodes from being revealed to the intermediate target node or the recipient node.
In a packet switched network, multiple nodes or user agents might use the same address of record, such as a Uniform Resource Identifier (URI) or other public user identity. For example, a single user might have a mobile telephone, a laptop computer, and a home computer that all have the same URI. When a message is sent to the URI, the message might be directed to all three nodes substantially simultaneously. In some cases it might be desirable for a SIP message to be directed to only one of a plurality of nodes that share a single URI. To provide such a capability, packet switched networks can include a feature known as a GRUU (Globally Routable User Agent URI), which allows a SIP message, or other SIP based service, to be directed to a specific node when that node has the same URI as other nodes.
As an example, a user with a user name of ‘user_abc’ who receives wireless telecommunications services from a company called ‘company_x’ might have the URI ‘user_abc@company_x.com’. A first device using this URI might have the GRUU ‘user_abc@company_x.com;gr=urn:uuid:f81d4fae-7dec-11d0-a765-00a0c91e6bf6’ and a second device using this URI might have the GRUU ‘user_abc@company_x.com gr=urn:uuid:d84d4fbe-10dec-12d0-a768-a0a0c51a6bf6’. The portion of the GRUU that Identifies a specific node, the URNs that follows the ‘gr’ parameter in these cases, can be referred to as the GR parameter value or GR parameter. The portion of the GRUU that corresponds to the URI, ‘user_abc@company_x.com’ in this case, can be referred to as the public user identity (PUID). For simplicity, hereinafter the gr parameter values or gr parameters will be given short and readable strings such as ‘nodeA’, ‘nodeB’, etc.
In an embodiment, a system is provided that allows the use of Communication Diversion (CDIV) in conjunction with GRUUs. CDIV is a script-based or rule-based service available for packet switched sessions such as SIP-based calls. CDIV can provide features such as call forwarding, call forwarding on busy, and similar options that allow a SIP session to be redirected to a node different from the node to which the call was originally directed. Any such forwarding or retargeting of a call will be referred to herein as diversion of the session. When the GRUU address feature is mapped to elements in a CDIV script, a session can be redirected to the GRUU of a node that, for example, shares a URI with other nodes. In addition, when a session is originated by a node that indicates itself or the circuit switched (CS) device that originated the call using a GRUU, the session can be handled differently depending on which of the nodes placed the call. Note that a CS device can also originate calls; when such a call is routed to a SIP based network, the call can be subjected to CDIV.
FIG. 1 is a block diagram of an embodiment of a system 100 that illustrate an implementation of CDIV for nodes that are addressable by their GRUUs. The system 100 includes a wireless telecommunications network 102. While the network 102 is depicted as a single entity, the network 102 might include a plurality of interconnected networks that allow a packet switched session to pass from one node to another. The network 102 includes a communication diversion policy 104 that might include one or more forwarding rules 106 for one or more nodes that specify how SIP messages are to be diverted based on the GRUUs of the nodes or CS devices from which the SIP messages originated or to which the SIP messages are targeted or re-targeted. The communication diversion policy 104 might also include one or more privacy rules 108, as described below. The forwarding rules 106 in the communication diversion policy 104 might be CDIV-based scripts that have been modified to support URIs that include a GR parameter. In particular, if the rule 106 is compliant to Internet Engineering Task Force (IETF) Request for Comments (RFC) 4745 and Open Mobile Alliance (OMA) common policy extensions, the modification includes matching an “identity” condition (RFC 4745 and OMA common policy extensions) value or similar condition values in OMA common policy extensions to the Contact header field value if said condition values include a GR parameter. The network 102 might also include appropriate processing components to implement the communication diversion policy 104. The communication diversion policy 104 and the components that implement the communication diversion policy 104 might reside on an application server or a similar component within the network 102.
The network 102 also includes a plurality of nodes under the control of a plurality of call origination parties and/or call target parties. Node A 110 and node D 140 are under the control of a first party 150 and share a first URI but have different GR parameters. (It should be noted that multiple nodes sharing a PUID is not a precondition for using GRUU). Node B 120 and node C 130 are under the control of a second party 160 and share a second URI but have different GR parameters. For example, if the first party 150 has a URI of ‘userAB@companyXY’, then node A 110 might have a GRUU of ‘userAB@companyXY;gr=nodeA and node D 140 might have a GRUU of ‘userAB@companyXY;gr=nodeD. If the second party 160 has a URI of ‘userBC@companyYZ’, then node B 120 might have a GRUU of ‘userBC@companyYZ;gr=nodeB and node C 130 might have a GRUU of ‘userBC@companyYZ;gr=nodeC. A third party 170 that might include a plurality of nodes might also be present.
In the following discussion, it will be assumed that the first party 150 causes a SIP message to be sent in a network towards the second party 160. The SIP message may used to establish a SIP-based call, which may be diverted based on one or more GRUUs of the nodes under the control of the first party 150 and/or the second party 160. The following discussion relates to SIP-based calls; however, considerations similar to the following discussion regarding calls would apply to other SIP messages originated by and/or targeted to other parties shown in the system 100. The call might be initiated by the first party 150 or might be initiated by another source, sent to the first party 150, and then forwarded by the first party 150 to the second party 160. In either case, the first party 150 will be considered herein to be the originator of the call. The node to which the originator directs the SIP message will be referred to herein as the target of the call. The node to which the SIP message is ultimately diverted will be referred to herein as the recipient of the call. The device of recipient of the call might also be addressed by its GRUU.
In an embodiment, a party that wishes to implement CDIV based on one or more GRUUs might specify in the communication diversion policy 104 the SIP URIs including GR parameters that pertain to the nodes that originate the SIP messages, the nodes to which the SIP messages are targeted, and/or the nodes to which the SIP messages are to be diverted. For instance, if the second party 160 wished to have SIP messages from the first party 150 forwarded based on the GRUUs of the first party 150 and/or based on the GRUUs of the second party 160, the second party 160 might send a message to the network 102 establishing the forwarding rules 106 in the communication diversion policy 104 that will divert SIP messages to the appropriate recipient.
As an example, the forwarding rules 106 in the communication diversion policy 104 might be set to specify that any SIP messages that are targeted to the GRUU of node B 120 are to be forwarded to node C 130, regardless of the node that originates the calls. In another example, the forwarding rules 106 might be set to specify that any SIP messages that are originated by the GRUU of node A 110 are to be forwarded to node B 120, regardless of the node of the second party 160 to which the SIP messages are targeted. In another example, the forwarding rules 106 might be set to specify that any calls originating from either the GRUU of node A 110 or the GRUU of node D 140 and targeted to either the GRUU of node B 120 or the GRUU of node C 130 are to be forwarded to the third party 170. Other examples of forwarding rules 106 that could be established based on the GRUUs of the originating nodes and/or the GRUUs of the target nodes may be apparent to one of skill in the art.
When a SIP message is transmitted to a node for which one or more forwarding rules 106 have been established, information in the SIP message's ‘To’ header field, ‘From’ header field, ‘Contact’ header field, ‘P-Asserted-Identity’ header field (RFC 3325), ‘History’ header field, or some other well known SIP-based part of the start-line, message-header, message-body in the SIP message can be examined for the presence of one or more SIP URIs including GR parameters. If one or more SIP URIs including GR parameters are present in the SIP message, those SIP URIs including GR parameters are compared to the SIP URIs including GR parameters in the communication diversion policy 104 of the target node. If no SIP URIs including GR parameters are present in the SIP message, or if the SIP URIs including GR parameters that are present do not match any SIP URIs including GR parameters in the communication diversion policy 104, or if no other forwarding rule matches as described in RFC 4745, the SIP message (e.g. SIP request) is sent in a standard manner to the target node. It should be noted that a SIP URI can be wildcarded.
If one or more SIP URIs including GR parameters in the SIP message do match one or more SIP URIs including GR parameters in the communication diversion policy 104, subject to other conditions and evaluations per RFC 4745, the forwarding rules 106 established for the target node in the communication diversion policy 104 are implemented. That is, if there is a rule in the communication diversion policy 104 that applies to a SIP URI including GR parameter in the information part of a SIP message, the SIP message might be diverted based on that SIP URI including GR parameter.
In a first example of such a diversion, call forwarding might be based on the node to which a call is targeted, with no consideration of the originating node. For instance, if node A 110 wished to place a call specifically to node B 120 rather than to the general URI of the second party 160, node A 110 might use the GRUU of node B 120 to target the call to node B 120. However, the second party 160 may wish for calls targeted to node B 120 to be forwarded to node C 130, regardless of the originating node. The second party 160, in such a case, might send appropriate instructions to the network 102 to establish the communication diversion policy 104 such that all calls that are targeted to node B 120 should be forwarded to node C 130. The SIP message from node A 110 would be matched against rules and conditions as generally described in RFC 4745, and it is determined if the SIP URI including GR parameter for node B 120 is present in the call's ‘To’ header (or in a similar SIP-based data field, e.g., the P-Asserted-Identity header field in SIP messages transmitted within the IM CN subsystem or IMS). Since the SIP URI including GR parameter for node B 120 would be present, subject to other conditions and evaluations, the forwarding rule 106 established by the second party 160 would be followed and the call would be diverted to node C 130.
In a second example, call forwarding might be based on the node from which a call originates, with no consideration of the target node. For instance, the second party 160 might send appropriate instructions to the network 102 to establish the communication diversion policy 104 such that any calls that are sent from node A 110 should be sent only to node B 120, regardless of the node or nodes to which the calls are targeted. If node A 110 placed a call specifically to node B 120, specifically to node C 130, or to the second party 160 in general, the call's ‘Contact’ header field (or a similar SIP-based data field) would be examined to determine if the SIP URI including GR parameter for node A 110 is present. Since the SIP URI including GR parameter for node A 110 would be present in the ‘Contact’ header in such a case, subject to other conditions and evaluations, the forwarding rule 106 established by the second party 160 for calls from node A 110 would be followed and the call would be sent only to node B 120.
In a third example, call forwarding might be based on a combination of the originating node and the target node. For instance, the second party 160 might specify that all calls sent from node A 110 and targeted to node B 120 should be diverted to node C 130. Calls sent from node D 140 and targeted to node C 130 might be diverted to node B 120. In these cases, both the ‘To’ header and the ‘Contact’ header (or similar headers) of a call from the first party 150 to the second party 160 might be examined for the SIP URIs including GR parameters that correspond to node A 110, node B 120, node C 130, and node D 140. If the designated SIP URIs including GR parameters are found in the headers, subject to other conditions and evaluations, the applicable forwarding rules 106 would be followed.
In a fourth example, calls from the first party 150 might be forwarded to the third party 170 rather than or in addition to being forwarded to a node under the control of the second party 160. For instance, the second party 160 could establish a forwarding rule 106 in the communication diversion policy 104 that states that calls from node A 110 targeted to node B 120 should be forwarded to the third party 170 or to a specific node under the control of the third party 170. A further rule 106 could state that calls from node A 110 targeted to node C 130 should be sent to node C 130 and also forwarded to the third party 170. A further rule 106 could state that for calls from node D 140, no forwarding should occur and the calls should be sent to their target node. One of skill in the art might recognize other possible rules 106 or combinations of rules 106 for diverting calls based on the GRUUs of node A 110, node B 120, node C 130, node D 140, and the node or nodes under the control of the third party 170.
When a SIP message is transmitted, the URI of the sending party is typically included in a ‘Contact’ field, a ‘History-Info’ field, a ‘P-Asserted-Identity’ field, and/or other locations in the headers or elsewhere in the SIP message. When the message is sent from a node that has a GRUU, the URI of the sending party might include both the PUID portion and the GR parameter portion of the GRUU. In some cases, a party involved in a session in which GRUUs are used in conjunction with CDIV may not wish to make the GR parameter of one or more of its nodes known to a node of the party to which the session is transferred. For example, if node A 110 is calling node B 120 and the second party 160 has specified that such SIP messages are to be redirected to the third party 170, the second party 160 may not want the GR parameter of node B 120 to be known to the third party 170.
In an embodiment, to keep a GR parameter private in such cases, one or more privacy rules 108 can be established in the communication diversion policy 104. When one of the privacy rules 108 is implemented and applied to a SIP message that includes a GRUU, the GR parameter and its value might be deleted from the applicable URIs in the SIP message. In some cases, only the GR parameter portion of the GRUU is deleted, and the forwarded SIP message includes only the PUID portion of the GRUU. For example, if the GRUU for a node is ‘user_abc@company_x.com;gr=nodeD, the ‘nodeD’ portion might be deleted and the ‘user_abc@company_x.com’ portion might be forwarded, as would be the case for a standard forwarded SIP message. In other cases, the entire GRUU might be deleted or replaced and no information about the forwarding party would be made available to the call recipient. The GR parameter or the entire GRUU might be removed from the ‘History-Info’ field, and/or any other location where that information appears. Many other ways of obfuscating or otherwise preventing the identity of a node from becoming known will readily suggest themselves to one skilled in the art, all of which are within the spirit and scope of the present disclosure.
In other cases where one of the privacy rules 108 is implemented for a SIP message forwarded from a node with a GRUU, the GR parameter might be replaced with other information that the forwarding party does not object to making known to the call recipient. For example, a temporary GRUU (TGRUU) might be used instead of a public GRUU. As is well known in the art, a TGRUU is a URI that is temporarily associated with a publicly available GRUU and that can be made available for a limited time, e.g. for the length of the SIP registration or less. Since a party that receives a message that uses a TGRUU to identify the sending party cannot determine the association between the original GRUU and the TGRUU, the use of a TGRUU can conceal the identity of the node that is or was involved in the session.
FIG. 2 illustrates an embodiment of a method 200 for implementing CDIV based on a GRUU. At block 210, a forwarding policy based on one or more GRUUs is established. The GR parameters that will be used as the basis for SIP message diversion decisions and one or more forwarding rules for diverting SIP messages based on the GR parameters are specified at this point. Privacy rules for concealing the identity of nodes mentioned at one time or another as part of the session might also be specified at this point. Alternatively, the forwarding rules and the privacy rules could be established at different times.
At block 220, when a SIP-based message is transmitted, a GR parameter in the SIP message might be compared to a GR parameter in the forwarding policy. At block 230, a decision is made based on whether a match is found between the GR parameter in the SIP message and the GR parameter in the forwarding policy. At block 240, if no SIP URIs including GR parameters are present in the SIP message, or if the SIP URIs including GR parameters that are present do not match any SIP URIs including GR parameters in the forwarding policy, or if no other forwarding rule matches as described in RFC 4745, the SIP message (e.g. SIP request) is sent in a standard manner to the target node. At block 250, if a match is found, one or more rules in the forwarding policy are followed and the SIP message might be diverted to a recipient node other than its target node. If one or more privacy rules have been established, the privacy rules might be applied to the diverted session at block 250 to prevent revealing information about one or more nodes to the eventual recipient of the SIP message or other intermediary nodes.
The following provides additional details and further embodiments of the present disclosure:
Provision/withdrawal. The CDIV services (Communication forwarding unconditional, Communication forwarding busy, Communication forwarding no reply, Communication forwarding not logged-in, Communication deflection and Communication Diversion Notification) shall be provided after prior arrangement with the service provider. The CDIV services shall be withdrawn at the served user's request or for administrative reasons.
The CDIV simulation services can be offered separately with subscription options. The notification service CDIVN is offered together with at least one CDIV simulation service. For each subscription option, only one value can be selected. These subscription options are part of the call diversion profile for the served user. The subscription options are shown in below table.







TABLE







Subscription options for CDIV services









Subscription options
Value
Applicability





Served user receives indication
No (default)
CFU


that a communication has been
        
CFB


forwarded (indication of
Yes
CFNR


communication diversion to the

CFNRc


diverting user).

CD


Originating user receives
No
CFU


notification that his
        
CFB


communication has been diverted
Yes (default)
CFNR


(forwarded or deflected).

CFNRc




CFNL




CD


Served user allows the
No
CFU


presentation of forwarded to URI
        
CFB


to originating user in diversion
Not reveal as GRUU
CFNR


notification.
        
CFNRc



Yes (default)
CFNL




CD


Served user receives reminder
No (default)
CFU


indication on outgoing
        
CFB


communication that CDIV is
Yes
CFNR


currently activated.

CFNRc




CFNL




CDIVN


Served user allows the
No
CFU


presentation of his/her URI to
        
CFB


diverted-to user.
Not reveal as GRUU
CFNR



        
CFNRc



Yes (default)
CFNL




CD


Served user allows the
No
CFU


presentation of his/her URI to
        
CFB


originating user in diversion
Not reveal as GRUU
CFNR


notification
        
CFNRc



Yes (default)
CFNL




CD


Served user receives notifications
No (default)
CDIVN


(CDIVN) of their communication
        



diversions
Yes









SIP-Messages. The following SIP messages are used due to the coding rules in ES 283 003.







TABLE







SIP Header information for redirection









SIP Message
Ref.
SIP Header





INVITE
[8]
“gr” parameter in the



[14]
uri-parameter



See draft-ietf-sip-gruu-13 in 
History-Info-Header



Bibliography
Privacy header




cause-parameter in the




uri-parameter


180 (Ringing)
[8]
“gr” URI parameter in



[14]
the Contact



See draft-ietf-sip-gruu-13 in 
History-Info-Header



Bibliography
Privacy header




cause-parameter in the




uri-parameter


181 (Call Is Being
[8]
“gr” URI parameter in


Forwarded)
[14]
the Contact



See draft-ietf-sip-gruu-13 in 
History-Info-Header



Bibliography
Privacy header




cause-parameter in the




uri-parameter


200 (OK) response
[8]
“gr” URI parameter in



[14]
the Contact



See draft-ietf-sip-gruu-13 in 
History-Info-Header



Bibliography
Privacy header




cause-parameter in the




uri-parameter


302 (Moved
[14]
Contact header


Temporarily)

cause-parameter in the


(see note)

uri-parameter





NOTE:


The 302 (Moved Temporarily) regarding the present document will be only used for the CD services. For more information on the cause-parameter is given in annex C. An AS that implements the CDIV service shall support the REFER method RFC 3515 [16], to be able to handle the interaction with ECT TS 183 029 [15].






Parameters. The Privacy header is described in ES 283 003. The present document refers for the History header to RFC 4244, for the Privacy header and P.-Asserted-Identity to RFC 3325, for GRUU the draft-ietf-sip-gruu-13 and for the Cause-Code to RFC 4458.
First diversion; no History header received. When this is the first diversion the communication has undergone, the following information is to be set in the retargeted request:
the diverting parties address;
the diverted-to party address;
diversion information.
The following header fields shall be included or modified with the specified values:


    
    
        a) The Request URI—shall be set to the SIP, TEL or SIPS URI where the communication is to be diverted to (see <target> element under the below heading “Communication Diversion Rule Actions.”).
        b) The History-Info header field—Two hist-info entries that shall be generated.
        
            b.1) The first entry includes the hi-targeted-to-uri of the served user.
            
                The privacy header “history” shall be escaped within the hi-targeted-to-uri, if:
                
                    If the served user wishes privacy (e.g. the served user is subscribed to the OIR Service); or
                    if the served used has the subscription option “Served user allows the presentation of his/her URI to diverted-to user” set to false.
                
                
            
            
        
        
    
    


If the first entry contains the “gr” parameter and the subscription option “Served user allows the presentation of his/her URI to diverted-to user” is set to “not-reveal-as-GRUU”, then it shall be changed as follows:

    
    
        
        
            
            
                
                
                    replace the first entry with the public user identity of the served user.
                    The Index is set to index=1 according to the rules specified in RFC 4244.
                
                
            
            
            b.2) The second entry includes the hi-targeted-to-uri of the address where the communication is diverted to. The index is set to index=1.1, The cause param parameter (redirecting reason and redirecting indicator) included in the history-info header field shall be set according to the diversion conditions and notification subscription option. The mapping between the diversion conditions and the coding of the cause param parameter is as follows:
            
                Communication forwarding busy, the cause value “486” as defined by RFC 4458 shall be used;
                Communication forwarding no reply, the cause value “408” as defined by RFC 4458 shall be used;
                Communication forwarding unconditional, the cause value “302” as defined by RFC 4458 shall be used;
                Communication deflection (Immediate response), the cause value “480” as defined by RFC 4458 shall be used;
                Communication Forwarding Not Logged in , the cause value “404” as defined by RFC 4458 is used;
                Communication deflection during alerting, the cause value “487” as defined by RFC 4458 shall be used;
                Communication Forwarding on Subscriber Not reachable, the cause value “503” as defined by RFC 4458 shall be used.
            
            
            according to the rules specified in RFC 4244.
        
        
        c) The To header field:
        
            c.1) If the To header contains the “gr” parameter and the served user has the subscription option “Served user allows the presentation of his/her URI to diverted-to user” set to “not-reveal-as-GRUU”, then the To header field shall be changed to a public user identity of the served user.
            c.2) If the served user does not want to reveal its identity to the diverted-to party, then the To header shall be changed to the URI where the communication is diverted to. The served user does not want to reveal its identity when one of the following conditions holds true:
            
                If the served user wishes privacy (e.g. the served user is subscribed to the OIR Service); or
                if the served used has the subscription option “Served user allows the presentation of his/her URI to diverted-to user” set to “false”.
            
            
        
        
    
    


In all other cases the To header shall not be changed.
Subsequent diversion; a History-Info header received. When this is the second or greater diversion the communication has undergone, a new history-info entry shall be added to the History-Info header field according to the rules defined in RFC 4244. The following information has to be added to the retargeted request:

    
    
        the diverted-to party address;
        diversion information.
    
    


The following header fields shall be included or modified with the specified values

    
    
        a) Request URI—shall be set to the SIP, TEL or SIPS URI where the communication is to be diverted to (see <target>element under the below heading “Communication Diversion Rule Actions”).
        b) History-Info header The history entry representing the served user may be modified. One history entry is added.
        
            b.1) if the history entry representing the served user contains the “gr” parameter and the subscription option “Served user allows the presentation of his/her URI to diverted-to user” set to “not-reveal-as-GRUU”, it shall be changed to the public user identity of the served user.
            
                The history entry representing the served user privacy header “history” shall be escaped within the hi-targeted-to-uri, if:
                
                    If the served user wishes privacy (e.g. the served user is subscribed to the OIR Service); or
                    if the served used has the subscription option “Served user allows the presentation of his/her URI to diverted-to user” set to false.
                
                
                If the history entry is already escaped with the correct privacy value no modification is needed.
                In all other cases the history entry representing the served user shall not be changed.
            
            
            b.2) A history entry shall be added where the hi-targeted-to-uri shall be set to the SIP, TEL or SIPS URI were the communication is diverted to cause param parameter (redirecting reason) included in the History-Info header field shall be set according to the diversion conditions and notification subscription option.
            
                The mapping between the diversion conditions and the coding of the cause param parameter is as follows:
                
                    Communication forwarding busy, the Cause value “486” as defined by RFC 4458 shall be used;
                    Communication forwarding no reply, the Cause value “408” as defined by RFC 4458 shall be used;
                    Communication forwarding unconditional, the Cause value “302” as defined by RFC 4458 shall be used;
                    Communication deflection (Immediate response), the Cause value “480” as defined by RFC 4458 shall be used;
                    Communication Forwarding Not Logged in, The Cause value “404” as defined by RFC 4458 shall be used;
                    Communication deflection during alerting, the cause value “487” as defined by RFC 4458 shall be used;
                    Communication Forwarding on Subscriber Not reachable, the cause value “503” as defined by RFC 4458 shall be used.
                
                
                The Index shall be incremented according to the Basic Forwarding rules specified in “Indexing in the History-Info Header” of RFC 4244 the new level index “1” shall be used.
            
            
        
        
        c) To header:
        
            c.1) If the served user does not want to reveal its identity to the diverted-to party, then the To header shall be changed to the URI where the communication is diverted to. The served user does not want to reveal its identity when one of the following conditions holds true:
            
                if the served user wishes privacy (e.g. the served user is subscribed to the OIR Service); or
                if the served used has the subscription option “Served user allows the presentation of his/her URI to diverted-to user” set to false.
            
            
            c.2) If the To header contains the “gr” parameter and the served user has the subscription option “Served user allows the presentation of his/her URI to diverted-to user” set to “not-reveal-as-GRUU”, then the To header shall be changed to a public user identity of the served user.
        
        
    
    


In all other cases the To header shall not be changed.
Notification procedures of the originating user (Subscription Option). When Communication Diversion occurs and if served user has the subscription option “Originating user receives notification that his communication has been diverted (forwarded or deflected).” set to true then a 181 (Call Is Being Forwarded) response shall be sent towards the originating user.
The following header fields shall be included or modified with the specified values:
a) The P-Asserted-Identity includes the URI of the diverting user.
b) The Privacy header with the value “id” shall be included, if:

    
    
        the served user wishes privacy (e.g. the served user is subscribed to the TIR Service); or
        the served used has the subscription option “ Served user allows the presentation of his/her URI to originating user in diversion notification” set to false.
    
    


c) The following entries shall be added to the History-Info header field:

    
    
        c.1) If this is the first diversion then the first entry shall be populated with the hi-targeted-to-uri of the served user. The Index is set to index=1 according to the rules specified in RFC 4244.
        c.2) On the history entry that represents the served user,
        
            c.2.1) if the history entry representing the served user contains the “gr” parameter and the served user has the subscription option “Served user allows the presentation of his/her URI to originating user in diversion notification” set to “not-reveal-as-GRUU”, it shall be changed to the public user identity of the diverted-to user.
            c.2.2) the privacy header with value “history” shall be escaped within the hi-targeted-to-uri, if:
            
                the served user wishes privacy (e.g. the served user is subscribed to the TIR Service); or
                the served used has the subscription option “Served user allows the presentation of his/her URI to originating user in diversion notification.” set to false.
                If the history is already escaped with the correct privacy value no modification is needed.
            
            
            c.2.3) In all other cases the history entry representing the served user shall not be changed.
        
        
        c.3) A history entry shall be added according to the rules under the heading “Subsequent diversion; a History-Info header received” item b.2. In addition, for this entry:
        
            c.2.1) if the history entry representing the forwarded to URI contains the “gr” parameter and the served user has the subscription option “Served user allows the presentation of forwarded to URI to originating user in diversion notification ” set to “not-reveal-as-GRUU”, it shall be changed to the public user identity of the diverted-to user.
            c.2.2) the privacy header with value “history” shall be escaped within the hi-targeted-to-uri, if the served used has the subscription option “served user allows the presentation of forwarded to URI to originating user in diversion notification” set to false.

Additional the AS may initiate an announcement to be included towards the calling user in order to inform about the diversion. Announcements may be played according to procedures as are described in TS 183 028.

        
        
    
    


Communication Diversion Rule Conditions. The following conditions are allowed by the XML Schema for the communication diversion service:
busy: This condition evaluates to true when the called user is busy. In all other cases the condition evaluates to false. Rules with this condition are evaluated when a busy indication is received from the called party.
not-registered: This condition evaluates to true when the called user is not registered. In all other cases the condition evaluates to false.
presence-status: This condition evaluates to true when the called user's current presence activity status is equal to the value set for this condition. In all other cases the condition evaluates to false.
cp:identity: This condition evaluates to true when the calling user's identity matches with the value of the identity element. The interpretation of all the elements of this condition is described in OMA-TS-XDM-Core-V1-0. In all other cases the condition evaluates to false. The Identity shall be matched against the value taken from the P-Asserted-Identity header field, unless the Identity contains a “gr” parameter, then it shall be matched against the value taken from the Contact header field.

anonymous: This condition evaluates to true when the P-Asserted-Identity of the calling user is not provided or privacy restricted.

cp:sphere: Not applicable in the context of the Communication Diversion service.

cp:validity: Specifies a period. The condition evaluates to true when the current time is within the validity period expressed by the value of this condition. In all other cases the condition evaluates to false.

media: When the incoming call request for certain media, the forwarding rule can decide to forward the call for this specific media. This condition evaluates to true when the value of this condition matches the media field in one of the “m=” lines in the SDP (RFC 4566) offered in an INVITE (RFC 3261).

no-answer: This condition evaluates to true when the called user does not answer. In all other cases the condition evaluates to false. Rules with this condition are evaluated when a no-answer timeout is detected.

The condition elements that are not taken from the common policy schema (RFC 4745) or OMA common policy schema (see OMA-TS-XDM-Core-V1-0) are defined in the simservs document schema (3GPP TS 24.623).

Communication Diversion Rule Actions. The action supported by the communication service can is forwarding of calls. For this the forward-to action has been defined. The forward-to action takes the following elements:
target: Specifies the address of the forwarding rule. It should be a valid SIP or SIPS URI (RFC 3261, TEL URL (RFC 3966).
notify-caller: An optional element that can be used to disable the default behaviour that the caller is notified that the call is being forwarded.
reveal-originating-identity-to-caller: An optional element that can be used to disable the default behaviour that the caller, when notified that the call is being forwarded, receives some originating party's identity information.
reveal-identity-to-caller: An optional element that can be used to disable the default behaviour that the caller, when notified that the call is being forwarded, receives some diverted-to party's identity information.
notify-served-user: An optional element that can be used to enable that the served user is notified that calls are being forwarded. Default this is switched off.
notify-served-user-on-outbound-call: An optional element that can be used to enable that the served user is notified that calls are being forwarded when he makes a call attempt. Default this is switched off.
reveal-identity-to-target: An optional element that can be used to disable the default behaviour that the diverted-to party receives some identity information of the diverting party.
XML Schema
<?xml version=“1.0” encoding=“UTF-8”?>
<xs:schema xmins:xs=“http://www.w3.org/2001/XMLSchema”
xmlns:ss=“http://uri.etsi.org/ngn/params/xml/simservs/xcap”
xmlns:cp=“urn:ietf:params:xml:ns:common-policy”
xmlns:ocp=“urn:oma:xml:xdm:common-policy”
targetNamespace=“http://uri.etsi.org/ngn/params/xml/simservs/xcap”
elementFormDefault=“qualified”
attributeFormDefault=“unqualified”>
<!--import common policy definitions-->
<xs:import namespace=“urn:ietf:params:xml:ns:common-policy”
schemaLocation=“common-policy.xsd”/>
<!--import OMA common policy extensions-->
<xs:import namespace=“urn:oma:xml:xdm:common-policy”
schemaLocation=“xdm_CommonPolicy-V1—0—2.xsd”/>
<!--communication diversion rule set based on the common policy rule set.-->
<xs:element name=“communication-diversion” substitutionGroup=“ss:absService”>
<xs:annotation>

    
    
        <xs:documentation>This is the communication diversion configuration document.</xs:documentation>
    
    


</xs:annotation>
<xs:complexType>

    
    
        <xs:complexContent>
        
            <xs:extension base=“ss:simservType”>
            
                <xs:sequence>
                
                    <!--add service specific elements here-->
                    <xs:element ref=“cp:ruleset” minOccurs=“0”/>
                
                
                </xs:sequence>
            
            
            </xs:extension>
            <!--service specific attributes can be defined here-->
        
        
        </xs:complexContent>
    
    


</xs:complexType>
</xs:element>
<!--communication diversion specific extensions to IETF common policy actions-->
<xs:element name=“forward-to” type=“ss:forward-to-type”/>
<xs:simpleType name=“reveal-URI-options-type”>
<xs:restriction base=“xs:string”>
<xs:enumeration value=“false”/>
<xs:enumeration value=“not-reveal-GRUU”/>
<xs:enumeration value=“true”/>
</xs:restriction>
</xs:simpleType>
<!--communication diversion specific type declarations-->
<xs:complexType name=“forward-to-type”>
<xs:sequence>

    
    
        <xs:element name=“target” type=“xs:anyURI” minOccurs=“1” maxOccurs=“1”/>
        <xs:element name=“notify-caller” type=“xs:boolean” default=“true” minOccurs=“0”/>
        <xs:element name=“reveal-identity-to-caller” type=“reveal-options-type” default=“true” minOccurs=“0”/>
        <xs:element name=“reveal-originating-identity-to-caller” type=“reveal-options-type” default=“true” minOccurs=“0”/>
        <xs:element name=“notify-served-user” type=“xs:boolean” default=“false” minOccurs=“0”/>
        <xs:element name=“notify-served-user-on-outbound-call” type=“xs:boolean” default=“false” minOccurs=“0”/>
        <xs:element name=“reveal-identity-to-target” type=“reveal-options-type” default=“true” minOccurs=“0”/>
    
    


</xs:sequence>
</xs:complexType>
</xs:schema>
FIG. 3 illustrates a wireless communications system including an embodiment of one of the nodes of FIG. 1, in this case, node A 110. A similar illustration and description could apply to node B 120, node C 130, or node D 140. The node 110 is operable for implementing aspects of the disclosure, but the disclosure should not be limited to these implementations. Though illustrated as a mobile phone, the node 110 may take various forms including a wireless handset, a pager, a personal digital assistant (PDA), a portable computer, a tablet computer, or a laptop computer. Many suitable devices combine some or all of these functions. In some embodiments of the disclosure, the node 110 is not a general purpose computing device like a portable, laptop or tablet computer, but rather is a special-purpose communications device such as a mobile phone, wireless handset, pager, fixed line device, or PDA. In another embodiment, the node 110 may be a portable, laptop or other computing device. The node 110 may support specialized activities such as gaming, inventory control, job control, and/or task management functions, and so on.
The node 110 includes a display 402. The node 110 also includes a touch-sensitive surface, a keyboard or other input keys generally referred as 404 for input by a user. The keyboard may be a full or reduced alphanumeric keyboard such as QWERTY, Dvorak, AZERTY, and sequential types, or a traditional numeric keypad with alphabet letters associated with a telephone keypad. The input keys may include a trackwheel, an exit or escape key, a trackball, and other navigational or functional keys, which may be inwardly depressed to provide further input function. The node 110 may present options for the user to select, controls for the user to actuate, and/or cursors or other indicators for the user to direct. The node 110 may further accept data entry from the user, including numbers to dial or various parameter values for configuring the operation of the node 110. The node 110 may further execute one or more software or firmware applications in response to user commands. These applications may configure the node 110 to perform various customized functions in response to user interaction. Additionally, the node 110 may be programmed and/or configured over-the-air, for example from a wireless base station, a wireless access point, or a peer node 110.
Among the various applications executable by the node 110 are a web browser, which enables the display 402 to show a web page. The web page may be obtained via wireless communications with a wireless network access node, a cell tower, a peer node 110, or any other wireless communication network or system 400. The network 400 is coupled to a wired network 408, such as the Internet. Via the wireless link and the wired network, the node 110 has access to information on various servers, such as a server 410. The server 410 may provide content that may be shown on the display 402. Alternately, the node 110 may access the network 400 through a peer node 110 acting as an intermediary, in a relay type or hop type of connection.
FIG. 4 shows a block diagram of the node 110. While a variety of known components of nodes 110 are depicted, in an embodiment a subset of the listed components and/or additional components not listed may be included in the node 110. The node 110 includes a digital signal processor (DSP) 502 and a memory 504. As shown, the node 110 may further include an antenna and front end unit 506, a radio frequency (RF) transceiver 508, an analog baseband processing unit 510, a microphone 512, an earpiece speaker 514, a headset port 516, an input/output interface 518, a removable memory card 520, a universal serial bus (USB) port 522, a short range wireless communication sub-system 524, an alert 526, a keypad 528, a liquid crystal display (LCD), which may include a touch sensitive surface 530, an LCD controller 532, a charge-coupled device (CCD) camera 534, a camera controller 536, and a global positioning system (GPS) sensor 538. In an embodiment, the node 110 may include another kind of display that does not provide a touch sensitive screen. In an embodiment, the DSP 502 may communicate directly with the memory 504 without passing through the input/output interface 518.
The DSP 502 or some other form of controller or central processing unit operates to control the various components of the node 110 in accordance with embedded software or firmware stored in memory 504 or stored in memory contained within the DSP 502 itself. In addition to the embedded software or firmware, the DSP 502 may execute other applications stored in the memory 504 or made available via information carrier media such as portable data storage media like the removable memory card 520 or via wired or wireless network communications. The application software may comprise a compiled set of machine-readable instructions that configure the DSP 502 to provide the desired functionality, or the application software may be high-level software instructions to be processed by an interpreter or compiler to indirectly configure the DSP 502.
The antenna and front end unit 506 may be provided to convert between wireless signals and electrical signals, enabling the node 110 to send and receive information from a cellular network or some other available wireless communications network or from a peer node 110. In an embodiment, the antenna and front end unit 506 may include multiple antennas to support beam forming and/or multiple input multiple output (MIMO) operations. As is known to those skilled in the art, MIMO operations may provide spatial diversity which can be used to overcome difficult channel conditions and/or increase channel throughput. The antenna and front end unit 506 may include antenna tuning and/or impedance matching components, RF power amplifiers, and/or low noise amplifiers.
The RF transceiver 508 provides frequency shifting, converting received RF signals to baseband and converting baseband transmit signals to RF. In some descriptions a radio transceiver or RF transceiver may be understood to include other signal processing functionality such as modulation/demodulation, coding/decoding, interleaving/deinterleaving, spreading/despreading, inverse fast Fourier transforming (IFFT)/fast Fourier transforming (FFT), cyclic prefix appending/removal, and other signal processing functions. For the purposes of clarity, the description here separates the description of this signal processing from the RF and/or radio stage and conceptually allocates that signal processing to the analog baseband processing unit 510 and/or the DSP 502 or other central processing unit. In some embodiments, the RF Transceiver 508, portions of the Antenna and Front End 506, and the analog baseband processing unit 510 may be combined in one or more processing units and/or application specific integrated circuits (ASICs).
The analog baseband processing unit 510 may provide various analog processing of inputs and outputs, for example analog processing of inputs from the microphone 512 and the headset 516 and outputs to the earpiece 514 and the headset 516. To that end, the analog baseband processing unit 510 may have ports for connecting to the built-in microphone 512 and the earpiece speaker 514 that enable the node 110 to be used as a cell phone. The analog baseband processing unit 510 may further include a port for connecting to a headset or other hands-free microphone and speaker configuration. The analog baseband processing unit 510 may provide digital-to-analog conversion in one signal direction and analog-to-digital conversion in the opposing signal direction. In some embodiments, at least some of the functionality of the analog baseband processing unit 510 may be provided by digital processing components, for example by the DSP 502 or by other central processing units.
The DSP 502 may perform modulation/demodulation, coding/decoding, interleaving/deinterleaving, spreading/despreading, inverse fast Fourier transforming (IFFT)/fast Fourier transforming (FFT), cyclic prefix appending/removal, and other signal processing functions associated with wireless communications. In an embodiment, for example in a code division multiple access (CDMA) technology application, for a transmitter function the DSP 502 may perform modulation, coding, interleaving, and spreading, and for a receiver function the DSP 502 may perform despreading, deinterleaving, decoding, and demodulation. In another embodiment, for example in an orthogonal frequency division multiplex access (OFDMA) technology application, for the transmitter function the DSP 502 may perform modulation, coding, interleaving, inverse fast Fourier transforming, and cyclic prefix appending, and for a receiver function the DSP 502 may perform cyclic prefix removal, fast Fourier transforming, deinterleaving, decoding, and demodulation. In other wireless technology applications, yet other signal processing functions and combinations of signal processing functions may be performed by the DSP 502.
The DSP 502 may communicate with a wireless network via the analog baseband processing unit 510. In some embodiments, the communication may provide Internet connectivity, enabling a user to gain access to content on the Internet and to send and receive e-mail or text messages. The input/output interface 518 interconnects the DSP 502 and various memories and interfaces. The memory 504 and the removable memory card 520 may provide software and data to configure the operation of the DSP 502. Among the interfaces may be the USB interface 522 and the short range wireless communication sub-system 524. The USB interface 522 may be used to charge the node 110 and may also enable the node 110 to function as a peripheral device to exchange information with a personal computer or other computer system. The short range wireless communication sub-system 524 may include an infrared port, a Bluetooth interface, an IEEE 802.11 compliant wireless interface, or any other short range wireless communication sub-system, which may enable the node 110 to communicate wirelessly with other nearby mobile devices and/or wireless base stations.
The input/output interface 518 may further connect the DSP 502 to the alert 526 that, when triggered, causes the node 110 to provide a notice to the user, for example, by ringing, playing a melody, or vibrating. The alert 526 may serve as a mechanism for alerting the user to any of various events such as an incoming call, a new text message, and an appointment reminder by silently vibrating, or by playing a specific pre-assigned melody for a particular caller.
The keypad 528 couples to the DSP 502 via the interface 518 to provide one mechanism for the user to make selections, enter information, and otherwise provide input to the node 110. The keyboard 528 may be a full or reduced alphanumeric keyboard such as QWERTY, Dvorak, AZERTY and sequential types, or a traditional numeric keypad with alphabet letters associated with a telephone keypad. The input keys may include a trackwheel, an exit or escape key, a trackball, and other navigational or functional keys, which may be inwardly depressed to provide further input function. Another input mechanism may be the LCD 530, which may include touch screen capability and also display text and/or graphics to the user. The LCD controller 532 couples the DSP 502 to the LCD 530.
The CCD camera 534, if equipped, enables the node 110 to take digital pictures. The DSP 502 communicates with the CCD camera 534 via the camera controller 536. In another embodiment, a camera operating according to a technology other than Charge Coupled Device cameras may be employed. The GPS sensor 538 is coupled to the DSP 502 to decode global positioning system signals, thereby enabling the node 110 to determine its position. Various other peripherals may also be included to provide additional functions, e.g., radio and television reception.
FIG. 5 illustrates a software environment 602 that may be implemented by the DSP 502. The DSP 502 executes operating system drivers 604 that provide a platform from which the rest of the software operates. The operating system drivers 604 provide drivers for the node hardware with standardized interfaces that are accessible to application software. The operating system drivers 604 include application management services (“AMS”) 606 that transfer control between applications running on the node 110. Also shown in FIG. 5 are a web browser application 608, a media player application 610, and Java applets 612. The web browser application 608 configures the node 110 to operate as a web browser, allowing a user to enter information into forms and select links to retrieve and view web pages. The media player application 610 configures the node 110 to retrieve and play audio or audiovisual media. The Java applets 612 configure the node 110 to provide games, utilities, and other functionality. A component 614 might provide functionality related to the use of GRUUs with CDIV.
The nodes of FIG. 1 may include a processing component that is capable of executing instructions related to the actions described above. FIG. 6 illustrates an example of a system 1300 that includes a processing component 1310 suitable for implementing one or more embodiments disclosed herein. In addition to the processor 1310 (which may be referred to as a central processor unit or CPU), the system 1300 might include network connectivity devices 1320, random access memory (RAM) 1330, read only memory (ROM) 1340, secondary storage 1350, and input/output (I/O) devices 1360. In some cases, some of these components may not be present or may be combined in various combinations with one another or with other components not shown. These components might be located in a single physical entity or in more than one physical entity. Any actions described herein as being taken by the processor 1310 might be taken by the processor 1310 alone or by the processor 1310 in conjunction with one or more components shown or not shown in the drawing.
The processor 1310 executes instructions, codes, computer programs, or scripts that it might access from the network connectivity devices 1320, RAM 1330, ROM 1340, or secondary storage 1350 (which might include various disk-based systems such as hard disk, floppy disk, or optical disk). While only one processor 1310 is shown, multiple processors may be present. Thus, while instructions may be discussed as being executed by a processor, the instructions may be executed simultaneously, serially, or otherwise by one or multiple processors. The processor 1310 may be implemented as one or more CPU chips.
The network connectivity devices 1320 may take the form of modems, modem banks, Ethernet devices, universal serial bus (USB) interface devices, serial interfaces, token ring devices, fiber distributed data interface (FDDI) devices, wireless local area network (WLAN) devices, radio transceiver devices such as code division multiple access (CDMA) devices, global system for mobile communications (GSM) radio transceiver devices, worldwide interoperability for microwave access (WiMAX) devices, and/or other well-known devices for connecting to networks. These network connectivity devices 1320 may enable the processor 1310 to communicate with the Internet or one or more telecommunications networks or other networks from which the processor 1310 might receive information or to which the processor 1310 might output information.
The network connectivity devices 1320 might also include one or more transceiver components 1325 capable of transmitting and/or receiving data wirelessly in the form of electromagnetic waves, such as radio frequency signals or microwave frequency signals. Alternatively, the data may propagate in or on the surface of electrical conductors, in coaxial cables, in waveguides, in optical media such as optical fiber, or in other media. The transceiver component 1325 might include separate receiving and transmitting units or a single transceiver. Information transmitted or received by the transceiver 1325 may include data that has been processed by the processor 1310 or instructions that are to be executed by processor 1310. Such information may be received from and outputted to a network in the form, for example, of a computer data baseband signal or signal embodied in a carrier wave. The data may be ordered according to different sequences as may be desirable for either processing or generating the data or transmitting or receiving the data. The baseband signal, the signal embedded in the carrier wave, or other types of signals currently used or hereafter developed may be referred to as the transmission medium and may be generated according to several methods well known to one skilled in the art.
The RAM 1330 might be used to store volatile data and perhaps to store instructions that are executed by the processor 1310. The ROM 1340 is a non-volatile memory device that typically has a smaller memory capacity than the memory capacity of the secondary storage 1350. ROM 1340 might be used to store instructions and perhaps data that are read during execution of the instructions. Access to both RAM 1330 and ROM 1340 is typically faster than to secondary storage 1350. The secondary storage 1350 is typically comprised of one or more disk drives or tape drives and might be used for non-volatile storage of data or as an over-flow data storage device if RAM 1330 is not large enough to hold all working data. Secondary storage 1350 may be used to store programs that are loaded into RAM 1330 when such programs are selected for execution.
The I/O devices 1360 may include liquid crystal displays (LCDs), touch screen displays, keyboards, keypads, switches, dials, mice, track balls, voice recognizers, card readers, paper tape readers, printers, video monitors, or other well-known input devices. Also, the transceiver 1325 might be considered to be a component of the I/O devices 1360 instead of or in addition to being a component of the network connectivity devices 1320. Some or all of the I/O devices 1360 may be substantially similar to various components depicted in the previously described drawing of the UA 110, such as the display 402 and the input 404.
European Telecommunications Standards Institute (ETSI) Technical Specification (TS) 183 004: “Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN)” is incorporated herein by reference for all purposes. Also incorporated herein by reference for all purposes are IETF RFCs 3325, 4244, 4458, and 4745.
While several embodiments have been provided in the present disclosure, it should be understood that the disclosed systems and methods may be embodied in many other specific forms without departing from the spirit or scope of the present disclosure. The present examples are to be considered as illustrative and not restrictive, and the intention is not to be limited to the details given herein. For example, the various elements or components may be combined or integrated in another system or certain features may be omitted, or not implemented.
Also, techniques, systems, subsystems and methods described and illustrated in the various embodiments as discrete or separate may be combined or integrated with other systems, modules, techniques, or methods without departing from the scope of the present disclosure. Other items shown or discussed as coupled or directly coupled or communicating with each other may be indirectly coupled or communicating through some interface, device, or intermediate component, whether electrically, mechanically, or otherwise. Other examples of changes, substitutions, and alterations are ascertainable by one skilled in the art and could be made without departing from the spirit and scope disclosed herein.

## Claims

1. A method for concealing an identity, comprising:
receiving a SIP message including a field, the field comprising a Globally Routable User Agent Uniform Resource Identifier (GRUU) identifying a node, wherein the GRUU comprises a public user identity (PUID), a ‘gr’ parameter, and a ‘gr’ parameter value;
evaluating a subscription option; and
in response to evaluating the subscription option, concealing an identity of the node by removing the ‘gr’ parameter and the ‘gr’ parameter value from the field.

2. The method of claim 1, further comprising:
establishing at least one rule with at least one condition specifying a recipient to which the SIP message is to be diverted when the GRUU of the SIP message matches a second GRUU containing a ‘gr’ URI parameter;
comparing the GRUU of the SIP message to the second GRUU; and
when the GRUU of the SIP message matches the second GRUU, subject to other conditions, following the rule.

3. The method of claim 2, wherein the second GRUU identifies a UE instance of one of:
a node that might be an intermediate target of the SIP message;
a node that might be an originator of the SIP message; and
a node that might be a target of the SIP message.

4. The method of claim 2, wherein the GRUU of the SIP message specifies one of:
a previous target of the SIP message;
an originator of the SIP message; and
a target of the SIP message.

5. The method of claim 4, wherein the field is one of:
a Contact header field in the SIP message;
a History-Info header field in the SIP message;
a P-Asserted-Identity header field in the SIP message;
a To header field in the SIP message; and
a From header field in the SIP message.

6. The method of claim 1, wherein the SIP message is a SIP INVITE request.

7. The method of claim 1, wherein the method is implemented through a modification of a Communication Diversion (CDIV) user configuration.

8. The method of claim 1, wherein the subscription option comprises “not reveal as GRUU”.

9. The method of claim 1, wherein removing the ‘gr’ parameter and the ‘gr’ parameter value from the field comprises replacing the GRUU with the public user identity.

10. The method of claim 1, wherein the identity of the node is concealed in a retargeted request message, a forwarded message, or a response message.

11. A non-transitory computer readable medium storing computer readable instructions executable by a processor of a computing device to cause said device to implement the method of claim 1.

12. A component in a telecommunications network, comprising:
a storage device storing instructions; and
a processor configured to execute the instructions such that the component receives a Session Initiation Protocol (SIP) message, the SIP message including a filed, the field comprising a Globally Routable User Agent Uniform Resource Identifier (GRUU) identifying a node, wherein the GRUU comprises a public user identity (PUID), a ‘gr’ parameter, and a ‘gr’ parameter value; the processor further configured to execute the instructions such that the component evaluates a subscription option; and in response to evaluating the subscription option, conceals an identity of the node by removing the ‘gr’ parameter and the ‘gr’ parameter value from the field.

13. The component of claim 12, further comprising instructions when executed by the processor such that the component:
establishes at least one rule with at least one condition specifying a recipient to which the SIP message is to be diverted when the GRUU of the SIP message matches a second GRUU containing a ‘gr’ URI parameter;
compares the GRUU of the SIP message to the second GRUU; and
when the GRUU of the SIP message matches the second GRUU, subject to other conditions, follows the rule.

14. The component of claim 13, wherein the GRUU of the SIP message specifies one of:
a previous target of the SIP message;
an originator of the SIP message; and
a target of the SIP message.

15. The component of claim 14, wherein the field is at least one of:
a Contact header field in the SIP message;
a History-Info header field in the SIP message;
a P-Asserted-Identity header field in the SIP message;
a To header field in the SIP message; and
a From header field in the SIP message.

16. The component of claim 13, wherein the second GRUU identifies a UE instance of one of:
a node that might be an intermediate target of the SIP message;
a node that might be an originator of the SIP message; and
a node that might be a target of the SIP message.

17. The component of claim 12, wherein the SIP message is a SIP INVITE request.

18. The component of claim 12, wherein the instructions are implemented through a modification of a Communication Diversion (CDIV) user configuration.

19. The component of claim 12, wherein the subscription option comprises “not reveal as GRUU”.

20. A method for concealing an identity, the method comprising:
receiving a SIP message including a field, the field comprising a public user identity (PUID), a ‘gr’ parameter, and a ‘gr’ parameter value that identify a node;
evaluating a subscription option for communication diversion; and
in response to evaluating the subscription option, concealing an identity of the node by removing the ‘gr’ parameter and the ‘gr’ parameter value from the field in a communication diversion message.

21. The method of claim 20, wherein the subscription option comprises “not reveal as GRUU”.

22. The method of claim 21, wherein the SIP message is a SIP INVITE request and the communication diversion message is one of: a retargeted request message, a forwarded message, or a response message.

23. A non-transitory computer readable medium storing computer readable instructions executable by a processor of a computing device to cause said device to implement the method of claim 20.