Content for TS 24.174 Word version: 17.6.0
1 Scope p. 7
The present document provides the protocol details for the multi-device and multi-identity aspects in the IP Multimedia (IM) Core Network (CN) subsystem based on the requirements from TS 22.173.
The present document is applicable to user equipment (UE) and application servers (AS) which are intended to support multi-device and multi-identity aspects in the IMS.
2 References p. 7
The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
- References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
- For a specific reference, subsequent revisions do not apply.
- For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1]
TR 21.905: "Vocabulary for 3GPP Specifications".
[2]
TS 22.173: "IP Multimedia Core Network Subsystem (IMS) Multimedia Telephony Service and supplementary services; Stage 1".
[3]
TS 24.229: "IP multimedia call control protocol based on Session Initiation Protocol (SIP) and Session Description Protocol (SDP); Stage 3".
[4]
TS 24.607: "Originating Identification Presentation (OIP) and Originating Identification Restriction (OIR) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification".
[5]
RFC 3323: "A Privacy Mechanism for the Session Initiation Protocol (SIP)".
[6]
RFC 3325: "Private Extensions to the Session Initiation Protocol (SIP) for Network Asserted Identity within Trusted Networks".
[7]
TS 24.623: "Extensible Markup Language (XML) Configuration Access Protocol (XCAP) over the Ut interface for Manipulating Supplementary Services".
[8]
RFC 8946: "Personal Assertion Token (PASSporT) Extension for Diverted Calls".
[9]
OMA-TS-CPM_Message_Storage_Using_RESTFul_API-V1_0-20181025-D: "CPM Message Store using RESTFul API, Draft Version 1.0 - 25 Oct 2018", http://member.openmobilealliance.org/ftp/Public_documents/COM/COM-CPM/Permanent_documents/OMA-TS-Message_Storage_Using_RESTFul_API-V1_0-20181025-D.zip .
[10]
OMA-TS-REST_NetAPI_NMS-V1_0-20190528-C: "RESTful Network API for Network Message Storage, Candidate Version 1.0 - 28 May 2019", http://member.openmobilealliance.org/ftp/Public_documents/ARCH/Permanent_documents/OMA-TS-REST_NetAPI_NMS-V1_0-20190528-C.zip .
[11]
TS 24.629: "Explicit Communication Transfer (ECT) using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification".
[12]
TS 24.147: "Conferencing using the IP Multimedia (IM) Core Network (CN) subsystem; Stage 3".
[13]
TS 24.175: "Management Object (MO) for Multi-Device and Multi-Identity in IMS; Stage 3".
[14]
TS 23.003: "Numbering, addressing and identification".
[15]
RFC 3261: "SIP: Session Initiation Protocol".
[16]
RFC 4235: "An INVITE-Initiated Dialog Event Package for the Session Initiation Protocol (SIP)".
[17]
TS 24.628: "Common Basic Communication procedures using IP Multimedia (IM) Core Network (CN) subsystem; Protocol specification".
[18]
RFC 4122 (July 2005): "A Universally Unique IDentifier (UUID) URN Namespace".
[19]
TS 24.173: "IMS Multimedia telephony communication service and supplementary services; Stage 3".
3 Definitions, symbols and abbreviations p. 8
3.1 Definitions p. 8
For the purposes of the present document, the terms and definitions given in TR 21.905 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905.
native identity:
an identity of form tel URI or SIP URI, used by the UE and which is associated with the IMSI which is currently used by the UE for IMS registration. The native identity is IMS registered by the UE.
alternative identity:
an identity of form tel URI or SIP URI, used by the UE and which is not associated with the IMSI which is currently used by the UE for IMS registration and is associated with a different IMSI for the same IMS subscription owned by the same IMS network. The alternative identity can be IMS registered by the UE or can be configured in the service data of the UE's IMS subscription.
call pull:
procedure in which a UE takes over an ongoing session from another UE in the set of federated UEs.
call push:
procedure in which a UE pushes an ongoing session to another UE in the set of federated UEs.
external alternative identity:
an identity of form tel URI or SIP URI, used by the UE and which is not associated with the IMSI which is currently used by the UE for IMS registration but is associated with a different IMSI for another IMS subscription owned by the same or a different IMS network. The external alternative identity is not IMS registered by the UE but is configured in the service data of the UE's IMS subscription.
virtual identity:
an identity of form tel URI or SIP URI, used by the UE and which is not associated as native identity with any IMSI that is associated with ISIM or USIM in the UE. The virtual identity can be IMS registered by the UE or can be configured in the service data of the UE's IMS subscription.The virtual identity can be used by a single user only or by several users having IMS subscriptions in the same or different IMS networks.
non-native identity:
an identity which is not the native identity. The non-native identity may be an alternative identity, external alternative identity or a virtual identity.
federated UEs:
a group of UEs which are configured to use the same public user identity.
user A:
user A is the originating user, in the present document user A calls user B, where A can be using the identity C.
user B:
user B is the terminating user, in the present document user A calls user B, where B can be reached under the identity D.
identity C:
identity C is a non-native identity that can be used by user A and is not registered by user A.
identity D:
identity D is a non-native identity that can be used by user B and is not registered by user B.
3.2 Abbreviations p. 9
For the purposes of the present document, the abbreviations given in TR 21.905 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905.
3pcc
Third party call control
AS
Application Server
MiD
Multi-iDentity
MuD
Multi-Device
