30 IMS emergency service

29.1653GPPInter-IMS Network to Network Interface (NNI)Release 18TS

30.1 IMS emergency registration

See clause 8.1 for the signalling requirements of IMS emergency registration regarding the "sos" URI parameter on the roaming II-NNI.

30.2 IMS emergency session

Based on inter-operator agreements or national requirements, IMS emergency session may be supported over the non-roaming II-NNI.

NOTE 1: The details of the SIP signalling requirements for IMS emergency session on the non-romaing II-NNI can be defined by inter-operator agreements or national requirements.

If the IMS emergency session is supported, the related procedures in 3GPP TS 24.229 [5] shall be applied with the requirements in this clause.

The Request-URI containing a uniform resource name (URN) for emergency services, defined in IETF RFC 5031 [61] and 3GPP TS 24.229 [5], shall be supported for the IMS emergency session traversal scenario on the non-roaming II-NNI.

NOTE 2: The emergency service URN(s) to use can be defined by inter-operator agreements or national requirements.

30.3 Next-Generation Pan-European eCall emergency service

Based on inter-operator agreements or national requirements, Next-Generation Pan-European eCall emergency service may be supported over the non-roaming II-NNI.

If Next-Generation Pan-European eCall emergency service is supported, the related procedures in 3GPP TS 24.229 [5] shall be applied with the requirements in this clause.

The MSD in an INVITE and INFO request shall be supported over the non-roaming II-NNI as described in 3GPP TS 24.229 [5].