hash stringlengths 32 32 | doc_id stringlengths 5 12 | section stringlengths 5 1.47k | content stringlengths 0 6.67M |
|---|---|---|---|
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.2.3 Group creation
| Figure 10.2.3-1 below illustrates the group creation operations by authorized MC service user/ MC service administrator to create a group. It applies to the scenario of normal group creation by an MC service administrator and user regrouping operations by authorized user/dispatcher.
Pre-conditions:
1. The group manag... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.2.4 Group regrouping
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.2.4.1 Temporary group formation - group regrouping within an MC system
| Figure 10.2.4.1-1 below illustrates the group regroup operations to create a temporary group within an MC system. For simplicity, only the case of two MC service groups being combined is represented, but the procedure is the same if more than two groups are combined.
The temporary group formation is applicable only fo... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.2.4.2 Temporary group formation involving multiple MC systems
| Figure 10.2.4.2-1 below illustrates the group regroup operations to create a temporary group involving multiple MC systems. For simplicity, only the case of two MC service groups being combined is represented, but the procedure is the same if more than two groups are combined.
NOTE: The temporary group formation is ap... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.2.4.3 Temporary group tear down involving multiple group host servers
| Figure 10.2.4.3-1 below illustrates the tearing down procedure of temporary group created through the group regroup operation. The procedure can be used when, e.g., the specific task for which the temporary group was created has been completed or a busier period occurs. For simplicity, only the teardown case for a temp... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.2.4.4 Group regroup rules
| To prevent routing issues and complexity related to group regrouping, the following rules shall be applied:
- Group regroup in either single MC system or multiple MC systems can take place if:
- None of the groups to be regrouped are temporary groups; and
- The groups to be regrouped are not already regrouped into a... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.2.5 Membership and affiliation list query
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.2.5.1 General
| An MC service user can request the membership or affiliation list on an MC service group regardless the user's group membership or affiliation.
|
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.2.5.2 Procedure
| Figure 10.2.5.2-1 below illustrates the membership or affiliation list query on an MC service group.
Figure 10.2.5.2-1: membership or affiliation list query
1. The group management client of the MC service user requests the membership or affiliation list on the MC service group from the group management server by ... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.2.6 Group membership
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.2.6.1 Group membership notification
| Figure 10.2.6.1-1 illustrates the group membership notification operations to the MC service server(s) and group management clients upon the group membership change at group management server.
Pre-conditions:
1. The group management server and MC service server serve the same MC system.
Figure 10.2.6.1-1: group me... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.2.6.2 Group membership update by authorized user
| Figure 10.2.6.2-1 below illustrates the group membership update operations by an authorized user/administrator/dispatcher to change the membership a MC service group (e.g. to add or delete group members).
Pre-conditions:
1. The group management server and MC service server serve the same MC system;
2. The initiator ... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.2.7 Group configuration for interconnection
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.2.7.1 Overview
| The procedures in the following subclauses describe the process for sharing group configuration from a primary MC system of the MC service group to an interconnected partner MC system of the MC service group where MC service clients receiving MC service in the partner MC system of the MC service group need to make use ... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.2.7.2 Primary MC system provides group configuration to the partner MC system
| Figure 10.2.7.2-1 below illustrates the case where the primary MC system of the MC service group provides the group configuration to the partner MC system of the MC service group, e.g. due to an action by an administrator or because the primary MC system of some of the MC service group members is the partner MC system ... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.2.7.3 Partner MC system requests group configuration from the primary MC system
| Figure 10.2.7.3-1 below illustrates the case where the partner MC system of the MC service group requests the group configuration from the primary MC system of the MC service group, for example because an MC service user receiving service in the partner MC system of the MC service group has the group configured in the ... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.2.7.4 Partner MC system subscribes to group configuration
| The procedure for subscription from the group management server in the partner system for group configuration information to the group management server in the primary MC system of the MC service group is shown in figure 10.2.7.4-1.
Pre-conditions:
- The MC service group is defined in its primary MC system.
- One or... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.2.7.5 Primary MC system notifies group configuration
| The procedure for notification of group configuration information from the group management server in the primary MC system of the MC service group to the group management server in the partner MC system of the MC service group is shown in figure 10.2.7.5-1.
Pre-conditions:
- The group management server in the partne... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.2.8 Group deletion
| Figure 10.2.8-1 below illustrates the group deletion procedure by an authorized MC service user/ MC service administrator to delete a group in the primary MC system. Any actions taken by the group management clients on the UE after receiving the group deletion notification are outside the scope of this procedure.
Pre-... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.3 Pre-established session (on-network)
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.3.1 General
| A pre-established session is a session established between an MC service client and the MC service server, on a per MC service basis, to exchange necessary media parameters needed for the definition of media bearers, allowing a faster set-up of MC service calls/sessions.
After a pre-established session is established,... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.3.2 Procedures
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.3.2.1 General
| The pre-established session can be established after MC service authorization for the user (see 3GPP TS 23.379 [16]).
The pre-established session is a session establishment procedure between the MC service client and the MC service server to exchange necessary media parameters needed for the definition of the media be... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.3.2.2 Pre-established session establishment
| The pre-established session is a session between the MC service client and the MC service server in the MC system, and which may utilise other functional entities (e.g. a media distribution function, as defined in subclause 7.4.2.3.5, for means of obtaining media parameters and gathering ICE candidates). Figure 10.3.2.... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.3.2.3 Pre-established session modification
| Figure 10.3.2.3-1 represents the pre-established session modification flow.
Figure 10.3.2.3-1: Pre-established session modification
1. The MC service client within the MC service UE gathers ICE candidates, if necessary (e.g. depending on the information that needs to be updated).
2. The MC service client within th... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.3.2.4 Pre-established session release
| Figure 10.3.2.4-1 represents the MC service client within the MC service UE initiated pre-established session release flow and figure 10.3.2.4-2 represents the MC service server initiated pre-established session release flow.
Figure 10.3.2.4-1: MC service client within the MC service UE initiated pre-established ses... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.4 Void
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.4.1 Void
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.5 Use of UE-to-network relay
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.5.1 UE-to-network relay service authorization
| The MC service shall support the capability for UE-to-network relay to restrict the relayed group communication on a per group basis.
To meet the above requirement, ProSe (as specified in 3GPP TS 23.303 [14]) can be used with an appropriate relay service code as per the following:
- To restrict connection from only t... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.5.2 UE-to-network relay MC service
| The ProSe UE-to-network relay provides a purely layer 3 IP data routing service, when the remote UE loses the coverage of cellular network and the MC service user on the remote UE requires to access the MC service via a ProSe UE-to-network relay.
The application layer signalling for the MC service user on a remote UE ... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.6 General user authentication and authorization for MC services
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.6.1 Primary MC system
| NOTE: Figure 10.6.1-1 is a high level user authentication and authorization flow. 3GPP TS 33.180 [25] defines the specific user authentication and authorization architecture required by the MC services in order to realize the MC service user authentication and authorization requirements as defined in 3GPP TS 22.280 [3]... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.6.2 Interconnection partner MC system
| Where communications with a partner MC system using interconnection are required, user authorization takes place in the serving MC system of the MC service user, using the MCX user service authorization procedure specified in 3GPP TS 33.180 [25].
|
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.6.3 Migration to partner MC system
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.6.3.1 General
| The following subclauses describe the procedure used for user authentication and service authorization when migrating to a partner MC system.
To enable migration, the inter-domain MCX user service authorization procedures specified in 3GPP TS 33.180 [25] are used.
|
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.6.3.2 Information flows
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.6.3.2.1 Migration service authorization request
| Table 10.6.3.2.1-1 describes the information flow migration service authorization request sent from the MC service client of the migrating MC service user to the partner MC service server, and from the partner MC service server to the primary MC service server of the migrating MC service user.
Table 10.6.3.2.1-1: Mig... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.6.3.2.2 Migration service authorization response
| Table 10.6.3.2.2-1 describes the information flow migration service authorization response sent from the primary MC service server of the migrating MC service user to the partner MC service server of the migrating MC service user, and from the partner MC service server to the MC service client of the migrating MC servi... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.6.3.2.3 Migration service de-authorization notification
| Table 10.6.3.2.3-1 describes the information flow migration service de-authorization notification sent by a MC service server of Primary MC system of migrated MC service user to a migrated partner MC system from which MC service user is migrating out.
Table 10.6.3.2.3-1: Migration service de-authorization notificatio... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.6.3.2.4 MC service authorization notification
| Table 10.6.3.2.4-1 describes the information flow about the notification for successful completion of MC service user service authorization after migrating to the partner MC system.
Table 10.6.3.2.4-1: MC service user authorization notification
Information element
Status
Description
MC service ID
M
The MC servic... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.6.3.3 Procedures
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.6.3.3.1 Migration service authorization procedure
| The procedure for service authorization for migration to a partner MC system and subsequent service authorization to migration partner MC system is shown in figure 10.6.3.3.1-1.
Pre-conditions
- The MC service user wishes to migrate to the partner MC system.
- The MC service client has been configured with an MC se... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.6.3.3.2 Migration service de-authorization procedure initiated by MC service server
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.6.3.3.2.1 Migrated MC service user returns back to its primary MC system
| The procedure for migration service de-authorization from a partner MC system is shown in figure 10.6.3.3.2.1-1.
Editor's note: When the MC service from partner MC system is stopped for MC service user is FFS.
Pre-conditions
- The MC service user has successfully completed the MC service authorisation with the MC s... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.6.3.3.2.2 Migrated MC service user migrate to another partner MC system
| The procedure for migration service de-authorization from a partner MC system is shown in figure 10.6.3.3.2.2-1.
Pre-conditions
- The MC service user has successfully completed the MC service authorization with the MC service server within the partner MC system C to which the MC service user is migrating into.
... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.7 Use of MBMS transmission
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.7.1 General
| 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 subc... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.7.2 Information flows for MBMS transmission
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.7.2.1 MBMS bearer announcement
| Table 10.7.2.1-1 describes the information flow MBMS bearer announcement from the MC service server to the MC service client.
Table 10.7.2.1-1: MBMS bearer announcement
Information element
Status
Description
TMGI
M
TMGI information
Alternative TMGI
O
A list of additional alternative TMGI may be included and u... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.7.2.2 MBMS listening status report
| 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.
Table 10.7.2.2-1: MBMS listening status report
Information element
Status
Desc... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.7.2.3 MBMS suspension reporting instruction
| 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.
Table 10.7.2.3-1: MBMS suspension reporting instruction (unicast)
Information element
Status
Description
MC service ID
M
The... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.7.2.4 Discover bearer request
| 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).
Table 10.7.2.4-1: Discover bearer request
Information element
Status
Description
List of service area identifiers
M
A list of service area identifier for the... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.7.2.5 Discover bearer response
| 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.
Table 10.7.2.5-1: Discover bearer response
Information element
Status
Description
TMGIs
M
List of TMGIs and related information
List of service area identifiers... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.7.2.6 Media distribution request
| 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.
Table 10.7.2.6-1: Media distribution request
Information element
Status
Description
TMGI
M
TMGI information
Bandwidth
M
Maximum ba... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.7.2.7 Media distribution response
| 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.
Table 10.7.2.7-1: Media distribution response
Information element
Status
Description
TMGI
M
TMGI information
Bandwidth
M
Maximum ... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.7.2.8 Identify multicast participants request
| Void
|
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.7.2.9 Remove call from bearer request
| Void
|
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.7.2.10 Media distribution release
| 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.
Table 10.7.2.10-1: Media distribution release
Information element
Status
Description
TMGI
M
TMGI information
Bandwidth
M
The bandw... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.7.2.11 Media broadcasting notification
| Void.
|
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.7.2.12 Group status notification
| Table 10.7.2.12-1 describes the information flow for the group status notification from MC service server to MC service client.
Table 10.7.2.12-1: Group status notification
Information element
Status
Description
MC service group ID
M
The MC service group ID of the group
Status of the group
M
Indicate the grou... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.7.2.13 MBMS suspension report
| Table 10.7.2.13-1 describes the information flow for the MBMS suspension report from MC service client to MC service server.
Table 10.7.2.13-1: MBMS suspension report
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... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.7.3 Procedures for MBMS usage
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.7.3.1 Use of pre-established MBMS bearers
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.7.3.1.1 General
| In this scenario, the MC service server pre-establishes MBMS bearer(s) in certain pre-configured areas before the initiation of the group communication session. When a user originates a request for a group communication session for one of these areas, the pre-established MBMS bearer(s) is used for the DL media transmis... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.7.3.1.2 Procedure
| The procedure figure 10.7.3.1.2-1 shows only one of the receiving MC service clients using an MBMS bearer. There might also be MC service clients in the same MC group communication session that receive the communication on unicast bearers.
Pre-conditions:
- The participating users are already affiliated.
Figure 10... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.7.3.2 Use of dynamic MBMS bearer establishment
| In this scenario depicted in figure 10.7.3.2-1, the MC service server uses a unicast bearer for communication with the UE on the DL at the start of the group communication session. When the MC service server decides to use an MBMS bearer for the DL media transmission, the MC service server establishes an MBMS bearer us... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.7.3.3 Switching from MBMS bearer to unicast bearer
| Figure 10.7.3.3-1 shows the procedure for service continuity when a UE is about to move out of MBMS coverage by switching from MBMS bearer to unicast bearer.
Pre-conditions:
- It is assumed that the MBMS bearer has been activated by MC service server for downlink delivery.
Figure 10.7.3.3-1: Switching from MBMS d... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.7.3.4 Use of MBMS bearer for application level control signalling
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.7.3.4.1 Description
| The MC service server may use an MBMS bearer for application level control signalling, according to this subclause. An MBMS bearer for application level control signalling is typically used for the purposes beyond the benefit for using MBMS for resource efficiency, e.g. for improved MC service performance (KPIs), handl... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.7.3.4.2 Procedure
| The procedure in figure 10.7.3.4.2-1 shows only one of the receiving MC service clients using an MBMS bearer.
Figure 10.7.3.4.2-1: Use of MBMS bearer for application level control signalling
1. The MC service server determines to activate MBMS bearer for application level control signalling, The activation of the M... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.7.3.5 MBMS bearer announcement over MBMS bearer
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.7.3.5.1 Description
| The MBMS announcement may be done on either a unicast bearer or a MBMS bearer. Using a unicast bearer for MBMS bearer announcement provides an interactive way of doing announcement. The MC service server will send the MBMS bearer announcement message to the MC service client regardless if there is an MBMS bearer active... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.7.3.5.2 Procedure
| The procedure defined below enables the MC service to announcement a new MBMS bearer.
Pre-conditions:
- An MBMS bearer used for MC service application control messages must have been pre-established and announced to the MC service client.
- Additional MBMS bearer information may have already been announced to the cl... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.7.3.6 MBMS bearer quality detection
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.7.3.6.1 Description
| The MC service client and MC service server use this procedure to report and take action on the MBMS bearer quality. An MC service client monitors an MBMS bearer to receive MC service media. Based on the received quality (e.g. radio level quality, transport level quality), the MC service client needs to inform the MC s... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.7.3.6.2 Procedure
| The MC service client shall indicate the ability of the MC service client to receive the MBMS bearer.
Pre-conditions:
- There is an MBMS bearer activated and the MBMS bearer information is announced to the MC service client
- The MC service client is located in the MBMS broadcasting area
- The MC service UE monitor... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.7.3.7 Service continuity in MBMS scenarios
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.7.3.7.1 General
| This subclause specify service continuity scenario when MBMS bearers are used. There are different solutions for different scenarios.
|
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.7.3.7.2 Service continuity when moving from one MBSFN to another
| The service continuity solution described in this subclause is suitable in the scenario when multiple MBMS bearers are used with the purpose to cover a larger area. In mission critical communication several media streams may be multiplexed in one MBMS bearer. Furthermore, one media stream (e.g. MCPTT group call) may be... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.7.3.7.3 Service continuity with a UE-to-Network relay
| This procedure handles a scenario when UE is moving from a location when the UE is experiencing good reception of the MBMS bearer to a location outside the MBMS service coverage. The MC service client apply a service continuity procedure to ensure that the service can be maintained and that the packet loss can be minim... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.7.3.8 MBMS suspension notification
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.7.3.8.1 Description
| In this procedure the MC service client is requested by the MC service server to send a MBMS suspension report. This request for MBMS suspension report can be included in the MBMS bearer announcement and the MC service server may choose to only send this request for MBMS suspension report to a subset of all MC service ... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.7.3.8.2 Procedure
| The information flow below defines a procedure in which the MC service client notifies the MC service server about an MBMS suspension decision in RAN.
The MC service server can decide on a subset of all UEs in the MBMS broadcast area that shall report on MBMS bearer suspension. When the MC service server make the deci... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.7.3.9 Multi-server bearer coordination
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.7.3.9.1 General
| To avoid allocating duplicate bearers for an MBMS service area, a single MC service server may manage all the MBMS media transmission for all groups and users within a particular MBMS service area. An MC service server controlling the MBMS bearer has the MBMS bearer control role. Different MC service servers may alloca... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.7.3.9.2 Procedures
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.7.3.9.2.1 MBMS bearer coordination independent on broadcasted media
| The procedure in this sub clause may be used when two or more MC service servers are serving users in the same area and are configured to share MBMS bearers for that specific area. The MC service servers may be of the same kind or different kind. The MC service servers are not participating in the same group call, whic... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.7.3.9.2.2 MBMS bearer coordination within one group call
| The procedure in this sub clause may be used when two MC service servers are serving users in the same area and are configured to share MBMS bearers for that specific area. The MC service servers are of the same kind, and the MC service servers may participate in the same group call, and by that have a need to broadcas... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.7.3.10 MBMS bearer event notification
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.7.3.10.1 General
| The MC service server is an instantiation of a GCS AS. For the MC service server to know the status of the MBMS bearer, and thus know the networks ability to deliver the service, it is required that the network provides MBMS bearer event notifications to the MC service server. The different events notified to the MC se... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.7.3.10.2 Procedure
| The procedure in figure 10.7.3.10.2-1 shows notification information flows from MC service server to BM-SC.
Figure 10.7.3.10.2-1: MBMS bearer event notification
1. The MC service server activates an MBMS bearer. The activation of the MBMS bearer is done on the MB2-C reference point and according to 3GPP TS 23.468 [... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.7.3.11 Use of FEC to protect MBMS transmissions
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.7.3.11.1 General
| Application layer FEC can be used to recover the packet losses when delivering a MC service over MBMS, to reach its required level of QoS.
Support of FEC is optional for the MC service servers and MC service clients
Adding FEC introduces an extra latency in the end to end media transport. This extra latency is bounde... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.7.3.11.2 FEC encoding by the BM-SC
| In this procedure, depicted in figure 10.7.3.11.2-1, the MC service server asks the BM-SC to apply FEC to a set of medias, transported by a MBMS bearer, using the Setup FEC request.
This procedure can be applied when using pre-established MBMS bearers (10.7.3.1) or dynamic MBMS bearers (10.7.3.2).
Pre-condition:
1. ... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.7.3.11.3 FEC encoding by the MC service server
| In this procedure, depicted in figure 10.7.3.11.3-1, FEC encoding is performed by the MC service server. The MC service server includes the FEC information within the MBMS bearer announcement. The FEC decoding is performed by the MC service client.
Figure 10.7.3.11.3-1: Application of FEC by the MC service server
1... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.7.3.12 Header compression over MBMS with ROHC
| |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.7.3.12.1 General
| Support of ROHC over MBMS is optional for the MC service servers and MC service clients. If header compression and FEC are both applied to a communication over MBMS, the header compression shall be performed after the FEC encoding.
These procedures can be applied when using pre-established MBMS bearers (see clause 10.... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.7.3.12.2 Header compression by the MC service server
| In this procedure, depicted in figure 10.7.3.12.2-1, header compression is performed by the MC service server. The MC service server includes the ROHC information within the MBMS bearer announcement. The header decompression is performed by the MC service client.
Figure 10.7.3.12.2-1: Header compression by the MC se... |
6d5e4a70e9f91968db9c2f826133800a | 23.280 | 10.7.3.12.3 Header compression by the BM-SC
| In this procedure, depicted in figure 10.7.3.12.3-1, the MC service server asks the BM-SC to compress headers for a set of medias, transported by a MBMS bearer, using the Setup ROHC request.
Pre-condition:
1. The MC service server has already activated a MBMS Bearer, with the MBMS Bearer request specified in 3GPP TS ... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.