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.280  Word version:  19.3.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.17…   10.17.3…   10.17.5…   11…   11.3…   11.5…   11.5.2…   11.5.3…   11.5.3.3.2A…   A…   B…   C…   E… 
11.5.3 MBMS support for MC clients residing on non-3GPP devices  11.5.3.1 General  11.5.3.2 Information flows  11.5.3.2.1 MC GW MBMS bearer announcement  11.5.3.2.2 MC GW MBMS listening status report  11.5.3.2.3 MC GW MapGroupToBearer request  11.5.3.2.4 MC GW MapGroupToBearer response  11.5.3.2.5 MC GW MBMS bearer quality report  11.5.3.2.6 MC GW MBMS bearer suspension indication  11.5.3.2.7 MC GW UnMapGroupToBearer request  11.5.3.2.8 MC GW UnMapGroupToBearer response  11.5.3.3 Procedures  11.5.3.3.1 Procedure for handling MBMS bearer announcement  11.5.3.3.2 Procedure for handling MapGroupToBearer message 
...

 

11.5.3  MBMS support for MC clients residing on non-3GPP devices |R19|  p. 344

11.5.3.1  General  p. 344

This subclause addresses the MBMS support for the MC clients residing on the non-3GPP devices associated with an MC gateway UE. The MC clients instruct the MC gateway UE about the corresponding MBMS bearer details to enable MC gateway listening on them. On demand, MC gateway UE forwards the traffic received over MBMS bearer to the MC clients residing on non-3GPP devices. With the procedure defined in this subclause, MBMS bearer can be supported for the MC clients residing on non-3GPP devices. Changes required are confined to the reference point between MC gateway UE and the MC clients residing on non-3GPP devices. MC service server may consider the location of the corresponding MC clients as defined in subclause 11.5.2 while deciding to establish MBMS bearer.
Up

11.5.3.2  Information flows  p. 344

11.5.3.2.1  MC GW MBMS bearer announcement  p. 344
Table 11.5.3.2.1-1 describes the information flow from the MC client which resides on a non-3GPP device to the MC gateway UE for sharing the details of MBMS bearer announcement received by the MC Client from the MC Service server.
Information element Status Description
MC GW service IDMThe MC GW service ID of the requesting MC client.
TMGIMTMGI information
List of service area identifierMA list of service area identifier for the applicable MBMS broadcast area.
FrequencyOIdentification of frequency if multi carrier support is provided
SDP informationMSDP with media and floor control information applicable to groups that can use this bearer (e.g. codec, protocol id, FEC information)
Monitoring stateOThe monitoring state is used to control if the client is actively monitoring the MBMS bearer quality or not.
ROHC informationOIndicate the usage of ROHC and provide the parameters of the ROHC channel to signal to the ROHC decoder.
Up
11.5.3.2.2  MC GW MBMS listening status report  p. 345
Table 11.5.3.2.2-1 describes the information flow from the MC gateway UE to the MC client which resides on a non-3GPP device for the MC GW MBMS listening status report.
Information element Status Description
TMGI(s)MTMGI(s) information.
MBMS listening status(s)MThe MBMS listening status per TMGI.
MBMS reception quality levelOThe reception quality level per TMGI
Non 3GPP transport resources establishment parameters (see NOTE)OThis element contains the details of the non-3GPP transport resources establishment parameters (IP address, Port etc.) which are used by the MC gateway UE to forward the MC service communication traffic received over 3GPP MBMS bearer to the MC client.
NOTE:
These parameters are implementation specific and are dependent on the non 3GPP transport mechanism used between the MC client and MC gateway UE. This parameter can be present mandatorily if the MBMS bearer listening status is success.
Up
11.5.3.2.3  MC GW MapGroupToBearer request  p. 345
Table 11.5.3.2.3-1 describes the information flow from the MC client which resides on a non-3GPP device to the MC gateway UE for sharing the details of MapGroupToBearer message received from the MC service server.
Information element Status Description
MC GW service IDMThe GW MC service ID of the MC service user.
MCPTT group IDMThis element identifies the MCPTT group, in which the call is started.
Media stream identifierMThis element identifies the media stream of the SDP used for the group call (e.g. MBMS subchannel).
TMGIMThe MBMS bearer identifier.
Up
11.5.3.2.4  MC GW MapGroupToBearer response  p. 345
Table 11.5.3.2.4-1 describes the information flow from the MC gateway UE to the MC client which resides on a non-3GPP device for the MC GW MapGroupToBearer response.
Information element Status Description
MapGroupToBearer StatusMSuccess or failure response
Non 3GPP transport resources establishment parameters (see NOTE)MThis element contain the details of the non 3GPP transport resources establishment parameters(IP address, Port etc.,) which are used by the MC gateway UE to forward the MC service Group communication traffic received over 3GPP MBMS bearer to the MC client.
NOTE:
These parameters are implementation specific and are dependent on the non-3GPP transport mechanism used between the MC client and MC gateway UE
Up
11.5.3.2.5  MC GW MBMS bearer quality report  p. 345
Table 11.5.3.2.5-1 describes the information flow from the MC gateway UE to the MC client which resides on a non-3GPP device for the MC GW MBMS bearer quality report.
Information element Status Description
TMGI(s)MTMGI(s) information.
MBMS listening status(s)MThe MBMS listening status per TMGI.
MBMS reception quality levelOThe reception quality level per TMGI
Up
11.5.3.2.6  MC GW MBMS bearer suspension indication  p. 346
Table 11.5.3.2.6-1 describes the information flow from the MC gateway UE to the MC client which resides on a non-3GPP device for the MC GW MBMS bearer suspension indication.
Information element Status Description
TMGI(s)MTMGI(s) information.
MBMS suspension status(s)MThe MBMS suspension status per TMGI.
Up
11.5.3.2.7  MC GW UnMapGroupToBearer request  p. 346
Table 11.5.3.2.7-1 describes the information flow from the MC client which resides on a non-3GPP device to the MC gateway UE for sharing the details of UnMapGroupToBearer message received from the MC service server.
Information element Status Description
MC GW service IDMThe GW MC service ID of the MC service user.
MCPTT group IDMThis element identifies the MC service group related to a group call to be dissociated over the MBS session.
Media stream identifierMThis element identifies the media stream of the SDP, which is no longer used for the group call within the MBMS session.
TMGIMThe MBMS bearer identifier.
Up
11.5.3.2.8  MC GW UnMapGroupToBearer response  p. 346
Table 11.5.3.2.8-1 describes the information flow from the MC gateway UE to the MC client which resides on a non-3GPP device for the MC GW UnMapGroupToBearer response.
Information element Status Description
UnMapGroupToBearer StatusMSuccess or failure response
Up

11.5.3.3  Procedures  p. 346

11.5.3.3.1  Procedure for handling MBMS bearer announcement  p. 346
MC clients residing on non-3GPP devices receive MBMS bearer announcements from the MC system, MC clients share the details of the MBMS bearer received in MBMS bearer announcement to the MC gateway UE. This enables the MC gateway UE to start monitoring the corresponding MBMS bearer.
Figure 11.5.3.3.1-1 illustrates the procedure for handling the MBMS bearer announcement by the MC client and the MC gateway UE.
Pre-conditions
  1. The MC client has been configured with the necessary parameters to enable the use of 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.1-1: Handling of MBMS bearer announcement
Figure 11.5.3.3.1-1: Handling of MBMS bearer announcement
Up
Step 1.
The MC service server establishes the MBMS bearer(s) according to the procedures defined in TS 23.468. Service description associated with the MBMS bearer(s) is returned from the BM-SC.
Step 2.
The MC service server provides service description information associated with the MBMS bearer to the MC client residing on non-3GPP devices via MC gateway UE.
Step 3.
The MC client sends the MC GW MBMS bearer announcement to the MC Gateway UE containing the MBMS bearer related information received from the MC service server.
Step 4.
The MC gateway UE stores the information associated with the TMGI(s). The MC gateway UE uses the TMGI and other MBMS bearer related information to activate the monitoring of the MBMS bearer.
Step 5.
The MC gateway UE that enters or is in the service area of at least one announced TMGI notifies to the MC client that it can receive data over MBMS by sending the MC GW MBMS listening status report. The MC GW MBMS listening status report also contains the details of the non-3GPP transport resources related parameters. The MC gateway UE may choose to send the details of existing transport resources information as part of non-3GPP transport resources establishment parameters IE if existing communication channel can be reused.
Step 6.
The MC client establishes the transport resources with the MC gateway UE based on the parameters received in step 5 to receive the MC service data from the MC gateway UE, if these parameters are not referring to any of the already established transport resources. The MC Gateway UE forwards the MC service data it received over the MBMS bearer from the MC service server to the MC client over this transport resources.
Step 7.
The MC client sends the MBMS Listening Status Report to the MC service server indicating that it is able to receive the media over MBMS.
Up
11.5.3.3.2  Procedure for handling MapGroupToBearer message  p. 348
Whenever the MC client detects that traffic received from MC service server is MapGroupToBearer message and if the MC client participates in the group session or communication identified by the MapGroupToBearer message then it should inform the details contained in the MapGroupToBearer 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 forward the traffic received over MBMS bearer accordingly.
Figure 11.5.3.3.2-1 illustrates the procedure for handling the MapGroupToBearer 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.2-1: Handling of MapGroupToBearer message
Figure 11.5.3.3.2-1: Handling of MapGroupToBearer message
Up
Step 1.
The MC service server sends a MapGroupToBearer message over a previously activated MBMS bearer to all users that will receive the call over an MBMS bearer. The MapGroupToBearer message includes association information between the group call and MBMS bearer. The MapGroupToBearer message includes MC service group ID and information about the media stream identifier of the activated MBMS bearer and may include the identifier (i.e. the TMGI) of the MBMS bearer broadcasting the call.
Step 2.
If the MC client is participating in the MC group communication identified by the MapGroupToBearer message, it sends the details contained in the MapGroupToBearer message to the MC gateway UE through MC GW MapGroupToBearer request message.
Step 3.
The MC gateway UE on receiving the MC GW MapGroupToBearer Request message from the MC client it maintains the association between the GW MC Service ID and the corresponding MBMS sub channel.
Step 4.
The MC gateway UE sends the MC GW MapGroupToBearer response message to the MC client which contains the details of the non-3GPP transport resources related parameters. The MC gateway UE may choose to send the details of existing communication channel information as part of non-3GPP transport resources establishment parameters IE if existing transport resources can be reused.
Step 5.
The MC client establishes the communication channel with the MC gateway UE based on the parameters received in step 4 to receive the MC service group communication data from the MC gateway UE, if these parameters are not referring to any of the already established transport resources. The MC Gateway UE forwards the MC service group communication data it received over the MBMS bearer from the MC service server to the MC client over this transport resources.
Step 6.
The MC service server sends the downlink media for the group communication session over the MBMS bearer.
Step 7.
The MC gateway UE checks which MC clients should receive the media of the MC group communication based on Step 3.
Step 8.
The MC gateway UE forwards the downlink media to the intended MC clients over the transport resources established as in step 5.
Up

Up   Top   ToC