Content for TS 23.280 Word version: 19.3.1
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…
10.7 Use of MBMS transmission
10.7.1 General
10.7.2 Information flows for MBMS transmission
10.7.2.1 MBMS bearer announcement
10.7.2.2 MBMS listening status report
10.7.2.3 MBMS suspension reporting instruction
10.7.2.4 Discover bearer request
10.7.2.5 Discover bearer response
10.7.2.6 Media distribution request
10.7.2.7 Media distribution response
10.7.2.8 Identify multicast participants request
10.7.2.9 Remove call from bearer request
10.7.2.10 Media distribution release
10.7.2.11 Media broadcasting notification
10.7.2.12 Group status notification
10.7.2.13 MBMS suspension report
...
...
10.7 Use of MBMS transmission p. 132
10.7.1 General p. 132
This subclause defines information flows and procedures for MBMS usage that applies to MC services. MBMS bearers can be used by any MC service for any MC service group. A single MBMS bearer can be used for one or more MC services within a single group or by multiple group communications in parallel.
The following subclauses specify the procedures and information flows for the usage of MBMS transmission that are utilised by the following MC services:
MC service specific pre-requisites and resultant behaviour by functional entities in performing these procedures are specified in the respective MC service TSs as listed above.
10.7.2 Information flows for MBMS transmission p. 132
10.7.2.1 MBMS bearer announcement p. 132
Table 10.7.2.1-1 describes the information flow MBMS bearer announcement from the MC service server to the MC service client.
| Information element | Status | Description |
|---|---|---|
| TMGI | M | TMGI information |
| Alternative TMGI | O | A list of additional alternative TMGI may be included and used in roaming scenarios. |
| QCI | O | QCI information used by the ProSe UE-Network Relay to determine the ProSe Per-Packet Priority value to be applied for the multicast packets relayed to Remote UE over PC5 |
| List of service area identifier | M | A list of service area identifier for the applicable MBMS broadcast area. |
| Frequency | O | Identification of frequency if multi carrier support is provided |
| SDP information | M | SDP with media and floor control information applicable to groups that can use this bearer (e.g. codec, protocol id, FEC information) |
| Monitoring state | O | The monitoring state is used to control if the client is actively monitoring the MBMS bearer quality or not. |
| Announcement acknowledgment | O | Indicate if the MC service server requires an acknowledgement of the MBMS bearer announcement. |
| ROHC information | O | Indicate the usage of ROHC and provide the parameters of the ROHC channel to signal to the ROHC decoder. |
|
NOTE
When MBMS bearer announcement is done on a MBMS bearer all attributes above are optional except the TMGI.
|
||
10.7.2.2 MBMS listening status report p. 133
Table 10.7.2.2-1 describes the information flow for the MBMS listening status report from MC service client to MC service server. The information is used for the decision on the switching from MBMS bearer to unicast bearer or vice versa.
| Information element | Status | Description |
|---|---|---|
| MC service ID | M | The identity of the MC service user who wants to report the MBMS listening status. |
| TMGI(s) | M | TMGI(s) information. |
| MBMS listening status(s) | M | The MBMS listening status per TMGI. |
| MBMS reception quality level | O | The reception quality level per TMGI (see NOTE) |
|
NOTE:
The set of quality levels helps service continuity in MBMS scenarios. A reception quality level may help to make an efficient switching decision to another bearer. How these levels are used is implementation specific.
|
||
10.7.2.3 MBMS suspension reporting instruction p. 133
Table 10.7.2.3-1 describes the information flow for the MBMS suspension reporting instruction from MC service server to MC service client in a unicast bearer for MBMS suspension reporting.
| Information element | Status | Description |
|---|---|---|
| MC service ID | M | The MC service identity |
| Suspension reporting | M | Enables or disable the suspension reporting for a specific MC service client |
Table 10.7.2.3-2 describes the information flow for the MBMS suspension reporting instruction from MC service server to MC service client in a multicast bearer for MBMS suspension reporting.
| Information element | Status | Description |
|---|---|---|
| Suspension reporting client subset | M | Contains a uniquely defined subset of MC service clients that shall report MBMS suspension |
10.7.2.4 Discover bearer request p. 134
Table 10.7.2.4-1 describes the information flow discover bearer request from the MC service server to another MC service server (MBMS bearer control role).
| Information element | Status | Description |
|---|---|---|
| List of service area identifiers | M | A list of service area identifier for the applicable MBMS broadcast area. |
| Bandwidth | M | Maximum bandwidth required |
| QCI | O | Desired QCI |
10.7.2.5 Discover bearer response p. 134
Table 10.7.2.5-1 describes the information flow discover bearer response from an MC service server (MBMS bearer control role) to the MC service server.
| Information element | Status | Description |
|---|---|---|
| TMGIs | M | List of TMGIs and related information |
| List of service area identifiers | M | A list of service area identifiers for the applicable MBMS broadcast areas, corresponding to the listed TMGIs, over which the request was successful. |
| Frequency | O | Identification of the frequency if multi-carrier support is provided |
| QCI | O | QCI information used by the ProSe UE-Network relay to determine the ProSe per-packet priority value to be applied for the multicast packets relayed to a remote UE over PC5. |
10.7.2.6 Media distribution request p. 134
Table 10.7.2.6-1 describes the information flow media distribution request from the MC service server to an MC service server (MBMS bearer control role) that has a desired bearer.
| Information element | Status | Description |
|---|---|---|
| TMGI | M | TMGI information |
| Bandwidth | M | Maximum bandwidth required |
| Separate floor control | M | Whether or not a separate bearer is required for floor control |
| SDP information | M | SDP with media and floor control information applicable to groups that can use this bearer (e.g. codec, protocol id) |
| QCI | O | Desired QCI |
| MC Group ID | O | The MC group id for when the request is sent for a specific group call. |
10.7.2.7 Media distribution response p. 135
Table 10.7.2.7-1 describes the information flow media distribution response from an MC service server (MBMS bearer control role) that has a desired bearer to the MC service server.
| Information element | Status | Description |
|---|---|---|
| TMGI | M | TMGI information |
| Bandwidth | M | Maximum bandwidth required |
| SDP information | M | SDP with media and floor control information applicable to groups that can use this bearer (e.g. codec, protocol id) |
| QCI | O | Actual QCI |
| Media stream identifier | O | This element identifies the media stream of the SDP used for the group call (e.g. MBMS subchannel). |
| Media distribution indicator | O | Indicates to the MC service server whether the media in the ongoing group communication should be sent or not |
10.7.2.8 Identify multicast participants request p. 135
Void
10.7.2.9 Remove call from bearer request p. 135
Void
10.7.2.10 Media distribution release |R15| p. 135
Table 10.7.2.10-1 describes the information flow media distribution release from the MC service server to an MC service server (MBMS bearer control role) that has the used bearer.
| Information element | Status | Description |
|---|---|---|
| TMGI | M | TMGI information |
| Bandwidth | M | The bandwidth released by the MC service server that used the bearer |
| MC Group ID | O | The MC group id for when the request is sent for a specific group call. |
10.7.2.11 Media broadcasting notification |R15| p. 135
Void.
10.7.2.12 Group status notification |R16| p. 135
Table 10.7.2.12-1 describes the information flow for the group status notification from MC service server to MC service client.
| Information element | Status | Description |
|---|---|---|
| MC service group ID | M | The MC service group ID of the group |
| Status of the group | M | Indicate the group has on-going call or not |
10.7.2.13 MBMS suspension report |R17| p. 136
Table 10.7.2.13-1 describes the information flow for the MBMS suspension report from MC service client to MC service server.
| Information element | Status | Description |
|---|---|---|
| MC service ID | M | The identity of the MC service user who wants to report the MBMS suspension status. |
| TMGI(s) | M | TMGI(s) information. |
| MBMS suspension status(s) | M | The MBMS suspension status per TMGI. |
