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 23.284  Word version:  17.0.0

Top   Top   Up   Prev   Next
1…   4…   4.2…   4.3…   5   6…   6.3…   6.3.2   6.3.3   6.3.4   6.3.5   7…   7.2.4…   7.2.4.2   7.2.4.3   7.2.4.4   7.2.4.5   7.2.4.6   7.3…   7.3.4…   7.3.4.2   7.3.4.3   7.3.4.4   8…   8.2.3   8.3…   8.3.2   8.4…   8.4.1.1.7…   8.4.1.2…   8.4.2…   8.4.2.2…   8.4.5…   8.4.5.6   8.4.5.7   8.4.5.8…   9…   13…   13.4…   13.4.3…   13.4.4…   13.5…   13.6…   13.7…   14…   16…   A…   A.2… 
13.7 Multiparty (MPTY)  13.8 Closed User Group (CUG)  13.9 Advice of Charge (AoC)  13.10 User-to-User Signalling (UUS)  13.11 Call Barring Services  13.12 Explicit Call Transfer (ECT)  13.13 Completion of Calls to Busy Subscriber (CCBS)  13.14 Multiple Subscriber Profile (MSP)  13.15 Multicall  13.16 Calling Name Presentation (CNAP)  13.17 Alternate Speech/Fax  13.18 Modification of the Access Bearer  13.19 GSM Fax  13.20 Voice group call service (VGCS), Voice broadcast service (VBS) 
...

 

13.7  Multiparty (MPTY)  p. 159

If LCLS is established for a call it shall be released while the Multiparty (MPTY) service is utilised, see LCLS break procedure in clause 7.2 of this specification. After MPTY is ended LCLS may be re-established if it is still feasible, see LCLS re-establishment procedure in clause 7.3 of this specification.

13.8  Closed User Group (CUG)  p. 159

No impact. There are no LCLS related requirements for the Closed User Group (CUG) service.

13.9  Advice of Charge (AoC)  p. 159

No impact. There are no LCLS related requirements for the Advice of Charge (AoC) service.

13.10  User-to-User Signalling (UUS)  p. 159

No impact. There are no LCLS related requirements for the User-to-User Signalling (UUS) service.

13.11  Call Barring Services  p. 159

No impact. There are no LCLS related requirements for the Call Barring Services.

13.12  Explicit Call Transfer (ECT)  p. 160

In order to perform Explicit Call Transfer, if LCLS is established for the first call this will be broken when it is put on hold as per the procedures specified in clause 13.6. If LCLS is established for the second call then the local switching of the call shall be released in order to be connected to the held party.
Procedures to establish LCLS for the transferred call are not supported.

13.13  Completion of Calls to Busy Subscriber (CCBS)  p. 160

No impact. There are no LCLS related requirements for the Completion of Calls to Busy Subscriber (CCBS) service.

13.14  Multiple Subscriber Profile (MSP)  p. 160

No impact. There are no LCLS related requirements for the Multiple Subscriber Profile (MSP) service.

13.15  Multicall  p. 160

There are no specific LCLS related requirements for the Multicall service.

13.16  Calling Name Presentation (CNAP)  p. 160

No impact. There are no LCLS related requirements for the Calling Name Presentation (CNAP) service.

13.17  Alternate Speech/Fax  p. 160

LCLS shall not be allowed for the Alternate Speech/Fax calls.

13.18  Modification of the Access Bearer  p. 160

During the call establishment phase, the modification of the access bearer procedure shall be performed in accordance with TS 23.205 for a BICC based CS core network and in accordance with TS 23.231 for a SIP-I based CS core network.
When the call is locally switched, if the MSC Server requires modification of the access bearer, an LCLS Break procedure as specified in clause 7.2.1 may occur.
Up

13.19  GSM Fax  p. 160

LCLS shall not be allowed for the GSM Fax calls.

13.20  Voice group call service (VGCS), Voice broadcast service (VBS)  p. 160

LCLS shall not be allowed when the Voice group call service (VGCS) or the Voice broadcast service (VBS) is utilised.

Up   Top   ToC