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   None
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.2 tMSC LCLS-Negotiation handling when receiving UL bicast and sending DL data  $ Change history 

 

A.2  tMSC LCLS-Negotiation handling when receiving UL bicast and sending DL data  p. 184

Case study 1:
If the tMSC server receives LCLS-Negotiation (request) with "Need_Send_Forward = Yes" and "Need_Receive_Forward = Yes" then it shall either:
  • return LCLS-Negotiation (response) set to "LCLS-Not-Allowed" or;
  • return LCLS-Negotiation (response) with value "Need_Send_Forward = Yes" and "Need_Receive_Forward = Yes" and set LCLS-Configuration IE to "Send Access DL, block local DL" (as shown in Figure X.2.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.2.1: iMSC requesting UL data from oUE and sending DL data to tUE
Figure A.2.1: iMSC requesting UL data from oUE and sending DL data to tUE
(⇒ copy of original 3GPP image)
Up
Case study 2:
If the tMSC server requires sending DL data to the terminating UE and receives LCLS-Negotiation (request) with "Need_Receive_Forward = Yes" and "Need_Send_Forward = No" during a LCLS negotiation request it shall either:
  • return LCLS-Negotiation (response) set to "LCLS-Not-Allowed" or;
  • set LCLS-Configuration IE to "connected both-way in the BSS and send access DL", return LCLS-Negotiation (response) with value "Need_Send_Forward = No" and "Need_Receive_Forward = Yes" and configure its Access MGW to isolate the network side termination from the access side termination when LCLS is established in order to avoid the forwarding of data from the oMGW/iMGW in the forward direction (as shown in Figure X.2.2), or;
Copy of original 3GPP image for 3GPP TS 23.284, Fig. A.2.2: iMSC requesting UL data from oUE and tMSC requesting DL data to tUE: option isolate access side termination from network side termination
Figure A.2.2: iMSC requesting UL data from oUE and tMSC requesting DL data to tUE: option isolate access side termination from network side termination
(⇒ copy of original 3GPP image)
Up
  • return LCLS-Negotiation (response) with value "Need_Send_Forward = Yes" and "Need_Receive_Forward = Yes" and set LCLS-Configuration IE to "Send Access DL, block local DL" (as shown in Figure X.2.3). 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.2.3: iMSC requesting UL data from oUE and tMSC requesting DL data to tUE: option send Access DL, block local DL
Figure A.2.3: iMSC requesting UL data from oUE and tMSC requesting DL data to tUE: option send Access DL, block local DL
(⇒ copy of original 3GPP image)
Up
Case study 3:
If the tMSC server requires receiving UL data from the terminating UE and it receives LCLS-Negotiation (request) with "Need_Receive_Backward = No" (as shown in Figure X.2.4) during a LCLS negotiation request then it shall either:
  • set LCLS-Configuration IE to "connected both-way in the BSS and bi-cast UL" and return LCLS-Negotiation (response) with "Need_Receive Backward = Yes" or;
  • set LCLS-Configuration IE to "connected both-way in the BSS and bi-cast UL", return LCLS-Negotiation (response) with "Need_Receive Backward = No" and configure its MGW to isolate its access side termination from the network side termination in order to avoid the forwarding of data in the backward direction through the CN.
Copy of original 3GPP image for 3GPP TS 23.284, Fig. A.2.4: tMSC requires DL data from tUE: option isolate access side termination from network side termination
Figure A.2.4: tMSC requires DL data from tUE: option isolate access side termination from network side termination
(⇒ copy of original 3GPP image)
Up

$  Change history  p. 189

Up   Top