15 Presence service
29.1653GPPInter-IMS Network to Network Interface (NNI)Release 18TS
15.0 General
In order to assure the end-to-end service interoperability through the Inter-IMS Network to Network Interface (II-NNI), the associated functions of the Presence service may be supported on the II-NNI between two IMS networks. The support of each function is based on agreement between operators.
If a function is supported, the related procedures from the 3GPP TS 24.141 [132] shall be applied with the requirements in the relevant clause below due to the crossing of the II-NNI.
15.1 Subscription of presence information
Service specific requirements in accordance with 3GPP TS 24.141 [132] shall be supported over the II-NNI.
A PUBLISH request identifying the presentity using a SIP URI, a tel URI or a PRES URI and the Event header field with the value "presence" and containing an "application/pidf+xml" MIME body shall be supported at the roaming II-NNI.
Additionally to the above and in any combination, a Content-Type header field with the value "multipart/related" and an "application/pidf-diff+xml" MIME body can be included in the PUBLISH request and shall be supported at the roaming II-NNI.
A SUBSCRIBE request with a Request-URI containing a SIP URI, a tel URI or a pres URI, the Event header field set to "presence" and Accept header fields with values "application/pidf+xml" and "multipart/related" shall be supported at the II-NNI.
Additionally to the above an "application/simple-filter+xml" MIME body can appear in the SUBSCRIBE request and shall be supported at the II-NNI.
Additionally to the above and in any combination a Content-Type header field with the value "multipart/mixed" and an "application/resource-lists" MIME body can appear in the SUBSCRIBE request and shall be supported at the roaming II-NNI.
A NOTIFY request including an Event header field with the value "presence" and an "application/pidf" MIME body shall be supported at the II-NNI.
NOTE: The NOTIFY request can contain substantial amount of data and TCP is expected to be used as the transport protocol.
The Allow-Events header field with the value "presence" shall be supported at the roaming II-NNI and may be supported at the non-roaming II-NNI.
15.2 Watcher subscribing to Presence List
Service specific requirements in accordance with 3GPP TS 24.141 [132] shall be supported over the II-NNI.
The requirements for the watcher subscribing to the Presence List are the same as subscribing to presence information as specified in clause 15.1 with the following additional requirement:
– The SUBSCRIBE request containing a Supported header field with the value "eventlist" shall also be supported at the roaming II-NNI;
– The SUBSCRIBE request containing a Accept header field with the value "application/rlmi+xml" shall be supported at the roaming II-NNI;
– A response code 200 (OK) to the SUBSCRIBE request containing the Require header field with the value "eventlist" shall be supported at the roaming II-NNI; and
– A NOTIFY message containing the "multipart/related" content type and an "application/rlmi+xml" MIME body shall be supported at the roaming II-NNI.
NOTE: The NOTIFY request can contain substantial amount of data and TCP is expected to be used as the transport protocol.
15.3 Subscription to Watcher Information
Service specific requirements in accordance with 3GPP TS 24.141 [132] shall be supported over the II-NNI.
A SUBSCRIBE request containing an Event header field with the value "presence.wininfo" and an Accept header field with value "application/watcherinfo+xml" shall be supported at the roaming II-NNI.
A NOTIFY request containing the Event header field with the value "presence.wininfo" and an "application/watcherinfo+xml" MIME body shall be supported at the roaming II-NNI.
NOTE: The NOTIFY request can contain substantial amount of data and TCP is expected to be used as the transport protocol.
The Allow-Events header field with the value "presence.wininfo" shall be supported at the roaming II-NNI and may be supported at the non-roaming II-NNI.
15.4 Subscription to state changes in XML documents
Service specific requirements in accordance with 3GPP TS 24.141 [132] shall be supported over the II-NNI.
A SUBSCRIBE request containing the Event header field with the value "xcap-diff" and parameters specified in IETF RFC 5875 [134], using the updated procedures from IETF RFC 6665 [20], shall be supported at the roaming II-NNI.
A NOTIFY request containing the Event header field with the value "xcap-diff", the Content-Type header field with the value "multipart/mixed" and any MIME body shall be supported at the roaming II-NNI.
NOTE: The NOTIFY request can contain substantial amount of data and TCP is expected to be the transport protocol.
The Allow-Events header field with the value "xcap-diff" shall be supported at the roaming II-NNI and may be supported at the non-roaming II-NNI.
For backward compatible reasons the Event header field with the value "ua-profile" should be supported at the roaming II-NNI.
15.5 Presence enhancements specified in Open Mobile Alliance (OMA) Release 1.1
15.5.1 General
In order to assure the end-to-end service interoperability through the Inter-IMS Network to Network Interface (II-NNI), the associated functions of the OMA Presence service may be supported on the II-NNI between two IMS networks. The support of each function is based on agreement between operators.
If a function of the OMA Presence Release 1.1 is supported, the related procedures from the OMA-TS-Presence_SIMPLE-V1_1_1 [142] shall be applied with the requirements in the relevant clause below due to the crossing of the II-NNI.
15.5.2 OMA subscription of presence information
The requirements for the OMA subscription of presence information are the same as clause 15.1.
15.5.3 OMA watcher subscribing to Presence List
The requirements for the OMA watcher subscribing to Presence List are the same as clause 15.2.
15.5.4 OMA subscription to Watcher Information
The requirements for the OMA subscription to Watcher Information are the same as clause 15.3.
15.6 Presence enhancements specified in Open Mobile Alliance (OMA) Release 2.0
15.6.1 General
In order to assure the end-to-end service interoperability through the Inter-IMS Network to Network Interface (II-NNI), the associated functions of the OMA Presence service may be supported on the II-NNI between two IMS networks. The support of each function is based on agreement between operators.
If a function of the OMA Presence Release 2.0 is supported, the related procedures from the OMA-TS-Presence_SIMPLE-V2_0 [138] shall be applied with the requirements in the relevant clause below due to the crossing of the II-NNI.
15.6.2 OMA subscription of presence information
The requirements for the OMA subscription of presence information are the same as clause 15.5.2 with the following additional requirement:
– An Allow header field containing the value "REFER" in a PUBLISH request shall be supported at the II-NNI.
– A Policy-Contact header field defined in IETF RFC 6794 [133] in a 488 (Not Acceptable Here) response to a PUBLISH request shall be supported at the II-NNI.
NOTE: Conveyance of this header field in a 488 response to a PUBLISH request is not supported by IETF RFC 6794 [133] but is required to support Presence services according to OMA specifications OMA-TS-Presence_SIMPLE-V2_0 [138].
– A Suppress-If- Match header field in a SUBSCRIBE request shall be supported at the II-NNI.
– An Accept-Encoding header field containing the value "gzip" in a SUBSCRIBE request shall be supported at the II-NNI.
– An "application/vnd.oma.suppnot+xml" MIME body in a SUBSCRIBE request shall be supported at the II-NNI.
– A Content-Encoding header field containing the value "gzip" in a NOTIFY request shall be supported at the II-NNI.
– A Content-Type header field with the value "multipart/mixed" in a SUBSCRIBE request shall be supported at the II-NNI.
– A Refer-To header field with the value "method=PUBLISH?event=presence", a Refer-Sub header field and a SIP-If-Match header field in a REFER request shall be supported at the II-NNI.
15.6.3 OMA watcher subscribing to Presence List
The requirements for the OMA watcher subscribing to Presence List are the same as clause 15.5.3 with the following additional requirements:
– A Suppress-If-Match header field in a SUBSCRIBE request shall be supported at the II-NNI.
– An Accept-Encoding header field containing the value "gzip" in a SUBSCRIBE request shall be supported at the II-NNI.
– An "application/vnd.oma.suppnot+xml" MIME body in a SUBSCRIBE request shall be supported at the II-NNI.
– An "application/resource-lists+xml" MIME body in a SUBSCRIBE request shall be supported at the II-NNI.
– A Content-Type header field with the value "multipart/mixed" in a SUBSCRIBE request shall be supported at the II-NNI.
– A NOTIFY request with a Content-Encoding header field containing the value "gzip" shall be supported at the II-NNI.
15.6.4 OMA subscription to Watcher Information
The requirements for the OMA subscription to Watcher Information are the same as clause 15.5.4 with the following additional requirements:
– Indicating support for "multipart/mixed" and "application/simple-filter+xml" in the Accept header field of the SUBSCRIBE request shall be supported at the II-NNI.
– Multiple "application/simple-filter+xml" MIME bodies in the NOTIFY request shall be supported at the II-NNI.
– A Suppress-If-Match header field in a SUBSCRIBE request shall be supported at the II-NNI.
– An Accept-Encoding header field containing the value "gzip" in the SUBSCRIBE request shall be supported at the II-NNI.
– A Content-Type header field with the value "multipart/mixed" in a NOTIFY request shall be supported at the II-NNI.
– A Content-Encoding header field with the value "gzip" in a NOTIFY request shall be supported at the II-NNI.
– A Refer-To header field with the value "method=SUBSCRIBE?Event=presence.winfo" and a Refer-Sub header field in a REFER request sent to a Watcher Information Subscriber shall be supported at the II-NNI.
15.6.5 Subscription to state changes in XML documents
The requirements for the OMA watcher subscribing to Presence List are the same as clause 15.4 with the following additional requirements:
– An Accept header field indicating the support for "application/xcap-diff+xml", "application/rlmi+xml" and "multipart/related" in a SUBSCRIBE request shall be supported at the II-NNI.
– An Accept-Encoding header field with the value "gzip" in a SUBSCRIBE request shall be supported at the II-NNI.
– A Content-Encoding header field containing the value "gzip" in a NOTIFY request shall be supported at the II-NNI.
– Multiple "multipart/related" MIME bodies in a NOTIFY request shall be supported at the II-NNI.
– An "application/rlmi+xml" MIME bodies in a NOTIFY request shall be supported at the II-NNI.