Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 23.434  Word version:  18.6.0

Top   Top   Up   Prev   Next
0…   4…   5   6…   6.4…   6.5…   6.5.3…   7…   8…   8.2.2…   9…   9.3…   9.3.2.21…   9.3.3…   9.3.6…   9.3.11…   9.3.13…   9.3.14…   9.4…   9.4.6…   9.5…   10…   10.3…   10.3.2.22…   10.3.3…   10.3.7…   10.3.10…   10.4…   11…   11.3…   11.3.3…   11.4…   12…   12.3…   13…   14…   14.2.2.2…   14.3…   14.3.2.20…   14.3.2.40…   14.3.3…   14.3.3.3…   14.3.4…   14.3.4.6   14.3.4.7…   14.3.4A…   14.3.4A.3…   14.3.4A.4…   14.3.4A.6…   14.3.4A.8…   14.3.4A.9…   14.3.4A.10…   14.3.5…   14.3.6…   14.3.9…   14.3.12…   14.4…   15…   16…   17…   18…   A   B…

 

14.3.4A.8  Service continuity between 5G MBS delivery and unicast deliveryp. 222

14.3.4A.8.1  Generalp. 222
This clause addresses the issue of VAL data delivery over MBS session, specifically, to maintain the service continuity when switching between 5G MBS delivery and unicast delivery.
14.3.4A.8.2  Service continuity for broadcast MBS sessionp. 222
14.3.4A.8.2.1  Generalp. 222
This solution provides the procedure which allows the NRM client to report the broadcast reception quality to the NRM server which is used to make the decision whether to use the unicast delivery to the VAL UE(s) which are suffering bad broadcast reception quality due to e.g., move out of the broadcast service area.
An NRM client monitors the broadcast MBS session to receive VAL data. Based on the received quality (e.g., radio level quality, RTP packet loss), the NRM client needs to inform the NRM server that the NRM client is able to receive the VAL data on the broadcast MBS session with sufficient quality or not.
This estimation of the broadcast reception quality may be dependent on, for example, the modulation and coding scheme (MCS) and measurements from the reference signals from the NG-RAN node(s), RTP packet loss, BLER of the received VAL data.
Up
14.3.4A.8.2.2  Proceduresp. 223
14.3.4A.8.2.2.1  Service continuity from broadcast to unicastp. 223
The procedure in Figure 14.3.4A.8.2.2.1-1 illustrates the VAL UE which is receiving VAL data via broadcast MBS session is switched to unicast delivery because the VAL UE suffers from bad broadcast reception quality due to e.g., moving out of the broadcast service area. It shows only one of the receiving VAL UEs receiving the broadcast MBS session.
Pre-conditions:
  1. The VAL group communication is ongoing and the VAL data (e.g., DL media, application layer control signalling) is transmitted via broadcast MBS session.
  2. The NRM client is receiving the VAL data (e.g., DL media, application layer control signalling) via the broadcast MBS session.
  3. The NRM client(s) already have the associated information (e.g., SDP) to receive the unicast delivery during the group communication establishment phase.
  4. An VAL group communication session is ongoing and the DL VAL data is transmitted over broadcast MBS session.
Reproduction of 3GPP TS 23.434, Fig. 14.3.4A.8.2.2.1-1: Service continuity from broadcast to unicast
Up
Step 1.
The NRM client detects that it suffers bad broadcast reception due to e.g., moving out of the broadcast service area of the announced MBS session ID. The NRM client may determine the broadcast reception quality by using the BLER of the received media. When no media is received, the quality estimation can consider the reference signals and the modulation and coding scheme (MCS).
Step 2.
The NRM client sends MBS listening status report which indicates the broadcast reception quality associated with the MBS session ID is not sufficient to receive media. The NRM client may also map the determined broadcast reception quality to a broadcast reception quality level. The broadcast reception quality level indicates at which specific broadcast reception quality level the VAL data has been received.
Step 3.
The NRM server based on the report from the participant, determines that the UE is not able to receive the media or the QoS requirements is not satisfied. The NRM server determines the VAL media (e.g., DL media, application layer control signalling) needs to be delivered via the unicast delivery to the reported NRM client.
Step 4.
If the unicast QoS flow is not satisfied, the NRM server interacts with the 5GC to update the QoS requirements.
Step 5.
The NRM server informs the VAL server to send the VAL data via the unicast delivery towards the reported NRM client by sending a user plane delivery mode message.
Step 6.
The NRM server sends the VAL media via the unicast delivery towards the NRM client which suffers bad broadcast reception quality.
Step 7.
The NRM client then receives the DL VAL data via both broadcast MBS session and unicast delivery.
Up
14.3.4A.8.2.2.2  Service continuity from unicast to broadcastp. 224
The procedure in Figure 14.3.4A.8.2.2.2-1 illustrates the VAL UE receiving VAL data via unicast delivery being switched to broadcast MBS session as the UE enters the broadcast service area where the NG-RAN is broadcasting the VAL media of the ongoing group communication. The VAL UE now is able to receive the VAL data via the broadcast MBS session. Only one of the receiving VAL UEs receiving the broadcast MBS session is shown.
Pre-conditions:
  1. The VAL group communication is ongoing and the VAL data (e.g., DL media, application layer control signalling) is transmitted via broadcast MBS session in the broadcast service areas.
  2. The VAL UE is receiving the VAL data (e.g., DL media, application layer control signalling) via the unicast delivery.
  3. The NRM client has already received the broadcast MBS session announcement, MapVALGroupToSessionStream information and enters the broadcast service area.
  4. A VAL group communication session is ongoing and the broadcast MBS session is used by the VAL server to deliver the VAL data of the group communication. The VAL UE is receiving the VAL data via the unicast delivery.
Reproduction of 3GPP TS 23.434, Fig. 14.3.4A.8.2.2.2-1: Service continuity from unicast to broadcast
Up
Step 1.
The NRM client detects that it is able to receive the broadcast media due to e.g., moving into the broadcast service area of the announced MBS session ID. The NRM client may determine the broadcast reception quality by using the BLER of the received media. When no media is received, the quality estimation can consider the reference signals and the modulation and coding scheme (MCS).
Step 2.
The NRM client sends MBS listening status report which indicates the broadcast reception quality associated with the MBS session ID is sufficient to receive VAL data. The NRM client may also map the determined broadcast reception quality to a broadcast reception quality level. The broadcast reception quality level indicates at which specific broadcast reception quality level the VAL data has been received.
Step 3.
The NRM server determines the VAL UE is able to receive the VAL data via the the broadcast MBS session, and the NRM server sends a user plane delivery mode to the VAL server indicating to stop the unicast delivery.
Step 4.
Based on the MapVALGroupToSessionStream received before, the NRM client receives the DL VAL data via both the broadcast MBS session and the unicast delivery.
Step 5.
The VAL server, based on the user plane delivery mode message, determines to stop sending the VAL data (e.g., DL media, application layer control signalling) via the unicast delivery to the reporting NRM client. After then, the NRM client receives the VAL data only via the broadcast MBS session.
Up
14.3.4A.8.3  Service continuity for multicast MBS sessionp. 226
14.3.4A.8.3.1  Generalp. 226
The NRM server may also switch between multicast and unicast by utilizing application layer mechanisms similar to switching between broadcast and unicast as specified in clause 14.3.4A.8.2. If indicated in the MBS session announcement information, the NRM client reports the monitoring state (i.e., the reception quality of the MBS session) back to the NRM server.
Up

Up   Top   ToC