16 Messaging service
29.1653GPPInter-IMS Network to Network Interface (NNI)Release 18TS
16.1 General
In order to assure the end-to-end service interoperability through the Inter-IMS Network to Network Interface (II-NNI), the associated function of the messaging service may be supported on the II-NNI between two IMS networks.
If a function is supported, the related procedures from the 3GPP TS 24.247 [139] shall be applied with the requirements in the relevant clause below due to the crossing of the II-NNI.
16.2 Page-mode messaging
Service specific requirements in accordance with clause 5 of 3GPP TS 24.247 [139] shall be supported over the II-NNI.
A MESSAGE request containing the "application/recipient-list" MIME body specified in IETF RFC 5365 [67], a Required header field with the ‘recipient-list-message’ option-tag; and a body carrying payload shall be supported at the roaming II-NNI.
A MESSAGE request containing:
– a body that carrying payload; or
– the "application/im-iscomposing+xml" MIME body,
shall be supported at the II-NNI.
The response code 415 (Unsupported Media Type) and the response code 202 (Accepted) shall be supported at the II-NNI.
16.4 Session-mode messaging
Service specific requirements in accordance with clause 6 of 3GPP TS 24.247 [139] shall be supported over the II-NNI.
No restrictions at the II-NNI identified.
16.5 Session-mode messaging conferences
Service specific requirements in accordance with clause 7 of 3GPP TS 24.247 [139] and 3GPP TS 24.147 [106] shall be supported over the II-NNI.
The "application/resource-lists+xml" MIME body included in the INVITE request shall be supported at the roaming II-NNI.
The media feature tag "isfocus" in the Contact header field of the INVITE request and responses to the INVITE request shall be supported at the II-NNI.
The SUBSCRIBE request including the "conference" event package name in the Event header field and the Accept header field containing an "application/conference-info+xml" MIME type shall be supported at the II-NNI.
The NOTIFY request including an "application/conference-info+xml" MIME body shall be supported at the II-NNI.
The REFER request containing a Referred-By header field and NOTIFY requests procedures shall be supported at the II-NNI.
The REFER request containing the BYE method URI parameter in the Refer-To header field shall be supported at the II-NNI.
The Referred-By header field in the INVITE request shall be supported at the II-NNI.
The Allow-Events header field in the INVITE request with the value "conference" shall be supported at the roaming II-NNI and may be supported at the non-roaming II-NNI.