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:  18.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… 
A Case studies for LCLS Negotiation  A.1 oMSC LCLS-Negotiation handling when receiving UL bicast and sending DL data 

 

A  Case studies for LCLS Negotiation  p. 181

Annex A provides examples of LCLS negotiation in the CN and LCLS configuration in the BSS. The examples also illustrate optional isolation scenarios and the change of the initial set of preferences during LCLS negotiation.

A.1  oMSC LCLS-Negotiation handling when receiving UL bicast and sending DL data  p. 181

Case study 1:
If the oMSC server requires receiving UL data from the terminating UE and sending DL data to the originating UE then it shall perform one of the following:
  • send LCLS-Negotiation (request) set to "LCLS-Not-Allowed" or;
  • send LCLS-Negotiation (request) set to "Need_Receive Backward = Yes, Need_Send_Backward = Yes", set LCLS-Configuration IE to "connected both-way in the BSS and send access DL from the Core Network, block local DL" on the originating call leg (as shown in Figure X.1.1). If the BSS supports this configuration then LCLS will be allowed; otherwise LCLS will not be permitted.
Copy of original 3GPP image for 3GPP TS 23.284, Fig. A.1.1: oMSC requesting UL data from tUE plus sending DL data to oUE
Figure A.1.1: oMSC requesting UL data from tUE plus sending DL data to oUE
(⇒ copy of original 3GPP image)
Up
Case study 2:
If the oMSC server requires receiving UL data from the originating UE it shall either:
  • send LCLS-Negotiation (request) set to "Need_Receive Forward = Yes" and set LCLS-Configuration IE to "connected both-way in the BSS and bi-cast UL" on the originating call leg after confirmation (as shown in Figure X1.2). If the BSS supports this configuration then LCLS will be allowed; otherwise LCLS will not be permitted. The data in the forward direction is passed to the tBSS due to the result of LCLS negotiation process on the originating call leg.
Copy of original 3GPP image for 3GPP TS 23.284, Fig. A.1.2: oMSC requesting UL data from oUE indicated in LCLS-Negotiation
Figure A.1.2: oMSC requesting UL data from oUE indicated in LCLS-Negotiation
(⇒ copy of original 3GPP image)
Up
  • In order to avoid the forwarding of the data in the forward direction to the tMGW the oMSC can send LCLS-Negotiation (request) to the succeeding node set to "Need_Receive_Forward = No" and if it does not receive "Need_Receive_Forward = Yes" in the LCLS-Negotiation (response) then it may configure its MGW to isolate the network side termination from the access side termination (as shown in Figure X.1.3).
Copy of original 3GPP image for 3GPP TS 23.284, Fig. A.1.3: oMSC requesting UL data from oUE not indicated in LCLS-Negotiation
Figure A.1.3: oMSC requesting UL data from oUE not indicated in LCLS-Negotiation
(⇒ copy of original 3GPP image)
Up
  • If the initial setting "Need_Receive_Forward = No" is overwritten by a succeeding Core Network node and the oMSC server receives "Need_Receive_Forward = Yes" in the LCLS-Negotiation (response) then it shall configure its MGW to be bothway through-connected (as shown in Figure X.1.4).
Copy of original 3GPP image for 3GPP TS 23.284, Fig. A.1.4: UL data requested from oUE by iMSC/tMSC, oMGW bothway through-connected
Figure A.1.4: UL data requested from oUE by iMSC/tMSC, oMGW bothway through-connected
(⇒ copy of original 3GPP image)
Up
Case study 3:
If the oMSC server receives a LCLS-Negotiation (response) set to "Need_Send_Backward = Yes" and "Need_Receive_Backward = Yes" (succeeding node of the oMSC server requires to send data to the oUE and to receive data from the tUE) then it shall perform one of the following:
  • send an LCLS-Negotiation (request) set to "LCLS-Not-Allowed" or;
  • set the LCLS-Configuration IE to "connected both-way in the BSS and send access DL from the Core Network, block local DL" on the originating leg (as shown in Figure X.1.5).
    If the BSS supports this configuration then LCLS will be allowed and the requested LCLS configuration will be confirmed; otherwise LCLS will not be permitted.
Copy of original 3GPP image for 3GPP TS 23.284, Fig. A.1.5: iMSC requesting UL data from tUE plus sending DL data to oUE
Figure A.1.5: iMSC requesting UL data from tUE plus sending DL data to oUE
(⇒ copy of original 3GPP image)
Up

Up   Top   ToC