Content for TS 24.174 Word version: 18.0.0
4.6.8 Conference calling (CONF)
4.6.8.2.1 UE procedures for MiD service
4.6.8.2.2 Actions at the AS serving the conference call initiator
4.6.8.2.3 Actions at the AS serving the identity C or identity D
4.6.9 Closed User Group (CUG)
4.6.10 Completion of Communications to Busy Subscriber (CCBS)
4.6.11 Communication Diversion (CDIV)
4.6.12 Malicious Communication Identification (MCID)
4.6.13 Anonymous Communication Rejection (ACR) and Communication Barring (CB)
4.6.14 Message Waiting Indication (MWI)
4.6.15 Flexible Alerting (FA)
4.6.16 Enhanced Calling Name (eCNAM)
4.6.17 Multi-Device (MuD)
4.6.18 Multi-Identity (MiD)
4.6.19 Customized Alerting Tones (CAT)
4.6.20 Customized Ringing Signal (CRS)
...
...
4.6.8 Conference calling (CONF) p. 17
4.6.8.1 Interactions for MuD service p. 17
No impact, i.e. neither service shall affect the operation of the other service.
4.6.8.2 Interactions for MiD service p. 17
4.6.8.2.1 UE procedures for MiD service p. 17
To be able to later use the CONF service, when the UE sends an INVITE request to a second user, the UE shall use the same identity as the UE used when setting up the first communication.
When creating the conference with an INVITE request the UE shall use the same identity as the UE used in the communications now on HOLD. If the UE uses identity C or identity D for the established sessions, the UE shall add the Addditional-Identity header field containing this identity. The UE sets the Request-URI to the same conference factory URI as the UE uses for the native identities.
When the UE adds a conference participant using the procedures in clause 5.3.1.5.3 in TS 24.147, the UE shall set the Referred-By header field in the REFER request to the same identity as the one used when creating the original session(s). If this identity is a non-registered identity (identity C or identity D) the UE adds the Additional-Identity header field containing this identity.
4.6.8.2.2 Actions at the AS serving the conference call initiator p. 17
If the AS receives an INVITE request with a Request-URI to a conference factory used in the serving network and an Additional-Identity header field, the AS in addition to the procedures in clause 4.5.3.2.1 replaces the Request-URI with a default conference factory URI for MMTel (as specified in TS 23.003) valid in the home network of the identity in the Additional-Identity header field.
4.6.8.2.3 Actions at the AS serving the identity C or identity D p. 18
If the AS receives an INVITE request, addressed to a default conference conference factory URI for MMTel as specified in TS 23.003, including an Additional-Identity header field the AS may in additon to the procedures in clause 4.5.3.3 modify the Request-URI to include any conference factory URI of the serving network.
If the AS receives a REFER request containing an Additional-Identity header field, the AS shall in additon to the procedures in clause 4.5.3.3 verify that the identity in the Referred-By header field is consistent with the Additional-Identity header field, and if necessary replace the Referred-By header field value with the identity in the received Additional-Identity header field. The AS then forwards the REFER request following normal procedures.
4.6.9 Closed User Group (CUG) p. 18
For MuD no impact, i.e. neither service shall affect the operation of the other service.
For MiD, CUG imposes restrictions on both incoming and outgoing calls. The MiD shall not use any identity C or identity D that are restricted by the CUG service.
4.6.10 Completion of Communications to Busy Subscriber (CCBS) p. 18
No impact, i.e. neither service shall affect the operation of the other service.
4.6.11 Communication Diversion (CDIV) p. 18
At the AS serving the user holding the terminating external alternative or virtual identity, the CFU (communication forwarding unconditional) take precedence over execution of MiD and MuD services.
At the terminating side, it is implementation specific to select CDIV service when different CDIV services apply to different federated UEs.
4.6.12 Malicious Communication Identification (MCID) p. 18
4.6.13 Anonymous Communication Rejection (ACR) and Communication Barring (CB) p. 18
The Incoming Communications Barring (ICB), Outgoing Communications Barring (OCB) and Anonymous Call Rejection (ACR) of the non-native identity take precedence over MuD and MiD services.
4.6.14 Message Waiting Indication (MWI) p. 18
In case of the MuD service, there is no impact on the operation of the other service.
The MWI is not supported for the identities, which are shared.
4.6.15 Flexible Alerting (FA) p. 18
MuD service can be combined with FA with no impacts.
Terminating MiD service is competing with FA.
4.6.16 Enhanced Calling Name (eCNAM) p. 18
In case of the MuD service, if the terminating user with MuD service has eCNAM activated, incoming calls to an identity shall apply eCNAM to all federated UEs.
4.6.17 Multi-Device (MuD) p. 19
When a user has the MiD service, any external alternative or virtual identity that is authorized to be used and activated by the MiD service can be activated on any of the Federated UEs as part of the user's MuD service.
4.6.18 Multi-Identity (MiD) p. 19
No impact. The activation of an identity by the MiD service is a condition for that identity to be active on a federated UE by the MuD service.
4.6.19 Customized Alerting Tones (CAT) p. 19
No impact.
4.6.20 Customized Ringing Signal (CRS) p. 19
No impact.
