Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x

Content for  TS 24.174  Word version:  18.0.0

Top   Top   Up   Prev   Next
1…   4…   4.5…   4.6…   4.6.8…   4.7…   A… 
4.6 Service interactions  4.6.1 Originating Identification Presentation (OIP)  4.6.2 Originating Identification Restriction (OIR)  4.6.3 Terminating Identification Presentation / Terminating Identification Restriction (TIP/TIR)  4.6.3.1 MuD  4.6.3.2 MiD  4.6.4 Advice of Charge  4.6.5 Communication Waiting (CW)  4.6.6 Communication Hold  4.6.7 Explicit Communication Transfer (ECT)  4.6.7.1 Interactions for MuD service  4.6.7.2 Interactions for MiD service  4.6.7.2.1 Actions at the UE acting as transferor  4.6.7.2.2 Actions at the AS serving the transferor  4.6.7.2.2.1 Identifying a request for communication transfer  4.6.7.2.2.2 Handling of transfer requests  4.6.7.2.2.3 Actions at the AS serving the identity C or identity D 
...

 

4.6  Service interactions  p. 16

4.6.1  Originating Identification Presentation (OIP)  p. 16

No impact. Neither service shall affect the operation of the other service.

4.6.2  Originating Identification Restriction (OIR)  p. 16

No impact.

4.6.3  Terminating Identification Presentation / Terminating Identification Restriction (TIP/TIR)  p. 16

4.6.3.1  MuD  p. 16

No impact.

4.6.3.2  MiD  p. 16

For TIP, the AS serving identity D shall in SIP responses remove the P-Asserted-Identity header field received from UE-B and insert a P-Asserted-Identity identifying the served user.
For TIR, the AS serving identity D shall pass any Privacy header field unchanged towards the originating user.

4.6.4  Advice of Charge  p. 16

No impact. Neither service shall affect the operation of the other service.

4.6.5  Communication Waiting (CW)  p. 16

For MuD, if there are ongoing communications, it is a service option whether to send an incoming initial INVITE to all federated UEs or only those UEs with ongoing communications.
For MiD, no impact.

4.6.6  Communication Hold  p. 16

No impact. Neither service shall affect the operation of the other service.

4.6.7  Explicit Communication Transfer (ECT)  p. 16

4.6.7.1  Interactions for MuD service  p. 16

No impact; i.e. neither service shall affect the operation of the other service.

4.6.7.2  Interactions for MiD service  p. 16

4.6.7.2.1  Actions at the UE acting as transferor  p. 16
When the UE initiates a communication transfer, the UE shall use the same identity in the Referred-By header field as was indicated for the established session. If the UE uses identity C or identity D for the established session, the UE shall add the Addditional-Identity header field containing this identity.
4.6.7.2.2  Actions at the AS serving the transferor  p. 17
4.6.7.2.2.1  Identifying a request for communication transfer  p. 17
See TS 24.629 on the criteria to determine that a REFER request is to be treated as a request for transfer of an existing communication.
4.6.7.2.2.2  Handling of transfer requests  p. 17
When a REFER request identified as a request for transfer is received from the served user and the Additional-Identity header field is included in the REFER request the AS shall authorize the use of the Additional-Identity header field as specified in clause 4.5.3.2.2. If the user is authorized to use the Additional-Identity header field the AS shall forward the REFER request as follows:
  1. if the REFER request was received inside the dialog, the AS forwards the request in the existing dialog towards the transferee; or
  2. if the REFER request was received outside the existing dialog, as specified in TS 24.629, the AS forwards the REFER request towards the transferee with the same considerations as specified for an initial INVITE request in clause 4.5.3.2.1.
Up
4.6.7.2.2.3  Actions at the AS serving the identity C or identity D  p. 18
When a REFER request identified as a request for transfer that contains an Additional-Identity header field containing a URI of the served user is received the AS shall in addition to the procedures in clause 4.5.3.3 verify that 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.
Up

Up   Top   ToC