Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 23.280  Word version:  19.0.1

Top   Top   Up   Prev   Next
1…   5…   5.2.8…   6   7…   7.3.2   7.4…   7.4.3…   7.5…   8…   9…   9.2.2…   9.2.2.2…   9.3…   10…   10.1.2…   10.1.3…   10.1.4.3…   10.1.4.5…   10.1.5…   10.1.6…   10.2…   10.2.3…   10.2.4.2…   10.2.4.3…   10.2.5…   10.2.7…   10.3…   10.6…   10.7…   10.7.3…   10.7.3.4…   10.7.3.7…   10.7.3.7.3   10.7.3.8…   10.7.3.10…   10.8…   10.8.4…   10.8.5…   10.9…   10.9.3…   10.9.3.5…   10.9.3.8…   10.9.3.9…   10.9.3.9.3…   10.9.3.9.4…   10.9.3.10…   10.9.3.10.4…   10.9.3.10.6…   10.10…   10.10.1.2.3…   10.10.2…   10.10.3…   10.10.3.3…   10.10.3.4…   10.11…   10.11.5…   10.12…   10.13…   10.13.3…   10.13.7…   10.13.10…   10.14…   10.15…   10.15.3…   10.15.3.3…   10.15.3.4…   10.16…   10.16.3…   11…   11.3…   11.5…   11.5.2…   11.5.3…   11.5.3.3.2A…   11.5.4…   A…   B…   C…

 

11.5.3.3.2A  Procedure for handling UnmapGroupFromBearer messagep. 326
Whenever the MC client receives UnmapGroupFromBearer message and if the MC client participates in the group session or communication identified by the UnmapGroupFromBearer message then it should inform the details contained in the UnmapGroupFromBearer message to MC gateway UE. When the association of group call, MBMS bearer and the MC GW service ID of the MC client is known to the MC gateway UE, it can remove the association and stop forwarding of the traffic received over MBMS bearer accordingly.
Figure 11.5.3.3.2A-1 illustrates the procedure for handling the UnmapGroupFromBearer message by the MC client and the MC gateway UE.
Pre-conditions:
  1. The MC client has been configured with the necessary parameters needed for connectivity with the MC gateway UE.
  2. The MC client successfully completed service authorization via MC gateway UE.
Reproduction of 3GPP TS 23.280, Fig. 11.5.3.3.2A-1: Handling of UnmapGroupFromBearer message
Up
Step 1.
An MCPTT group call is ongoing; the MC gateway UE forwards the downlink media to the intended MC client over the transport resources established.
Step 2.
MCPTT server has determined to disconnect the call over the MBMS bearer for the MC client.
Step 3.
An UnmapGroupFromBearer message is sent by the MCPTT server to MC client (if in MBMS coverage area) on MBMS bearer(s).
Step 4.
If the MC client is participating in the MC group communication identified by the UnmapGroupFromBearer message, it sends the details contained in the UnmapGroupFromBearer message to the MC gateway UE through MC GW UnMapGroupToBearer request message.
Step 5.
The MC gateway UE on receiving the MC GW UnMapGroupToBearer Request message from the MC client it removes the association maintained between the GW MC Service ID and the corresponding MBMS sub channel.
Step 6.
The MC gateway UE sends the MC GW MapGroupToBearer response message to the MC client.
Up
11.5.3.3.3  Procedure for MBMS bearer suspension notificationp. 327
The MC service server can choose to instruct some MC clients to send the MBMS bearer suspension report when notified by RAN. When the MC clients are residing on non 3GPP devices, MC gateway UE would be the one listening on the MBMS bearers. When RAN decides to suspend the MBMS bearer it indicates the MC gateway UE. MC gateway UE to notify the MC clients it is serving so that MC clients can report the same to the MC service server. This procedure is applicable only if the MC client is instructed to report the MBMS bearer suspension. Irrespective of whether the MC clients need to send the MBMS bearer suspension report to the MC service server, MC gateway can choose to notify the MC clients it is serving whenever RAN suspends the MBMS bearer. MC clients can then decide to send the MBMS bearer suspension report to the MC service server only if they are instructed by the MC service server.
Figure 11.5.3.3.3-1 illustrates the procedure for MC clients residing on non-3GPP devices reporting the MC service server about the MBMS bearer suspension.
Reproduction of 3GPP TS 23.280, Fig. 11.5.3.3.3-1: MBMS bearer suspension notification
Up
Step 1.
The MC service server sends an MBMS suspension reporting instruction to the MC client residing on non-3GPP device.
Step 2.
RAN decides to suspend the MBMS bearer, according to existing procedures in TS 36.300.
Step 3.
An MBMS suspension indication is sent to the MC gateway UE in the MSI (MCH Scheduling Information), according to existing procedures in TS 36.300.
Step 4.
The MC gateway UE detect the MBMS suspension and sends an MC GW MBMS suspension indication to the MC Client residing on non-3GPP device.
Step 5.
The MC client MBMS suspension report to the MC Service server via MC gateway UE.
Up
11.5.3.3.4  Procedure for reporting MBMS bearer qualityp. 328
The MC gateway UE listening on the MBMS bearer has to report the MBMS bearer quality to the MC clients so that MC clients can report the same to the MC service server. MC Gateway UE monitors an MBMS bearer to receive MC service media. Based on the received quality (e.g. radio level quality) the MC gateway UE needs to inform the MC Clients which requested the MC gateway UE to listen on MBMS bearer, whether it is able to receive the MC service media on the MBMS bearer with sufficient quality or not the MC Clients can inform the MC service server accordingly.
Figure 11.5.3.3.4-1 illustrates the procedure for MC clients residing on non-3GPP devices reporting the MC service server about the MBMS bearer quality.
Pre-conditions
  1. There is an MBMS bearer activated and the MBMS bearer information is announced to the MC gateway UE.
  2. The MC gateway UE is located in the MBMS broadcasting area
  3. The MC gateway UE monitors SIB-13 (or SIB-20) and (SC-)MCCH to receive the modulation and coding scheme.
  4. The MC gateway UE monitors the cell specific reference signal and when MBSFN transmission is used, the MBSFN specific reference signals.
Reproduction of 3GPP TS 23.280, Fig. 11.5.3.3.4-1: Reporting MBMS bearer quality
Up
Step 1.
The MC gateway UE follows the Step 1 of the procedure as described in clause 10.7.3.6.2 for the MC service UE. The corresponding MBMS bearer quality information is forwarded to all the MC clients which have asked the MC gateway UE to listen on the particular MBMS bearer.
Step 2.
If the MBMS bearer quality reaches a certain threshold, the MC gateway UE sends an MC GW MBMS bearer quality report to the MC client. The threshold is used to define the MBMS listening status, which indicates if the MBMS bearer quality has been acceptable or not to receive a specific MC service media. If the MBMS bearer quality is mapped to a different MBMS reception quality level, the MC gateway UE may send an MBMS Bearer Quality report including the MBMS reception quality level to the MC Client.
Step 3.
The MC Client sends the MBMS listening status report to the MC Service server via MC gateway UE containing the information received in the MC GW MBMS bearer quality report.
Step 4.
The MC service server may send an additional proposal for measurements e.g. information about neighbouring MBMS bearers. This message may be an MBMS bearer announcement message.
Up

Up   Top   ToC