S2-08xyzw
CR-Form-v9.3
For HELP on using this form look at the pop-up text over the symbols. Comprehensive instructions on how to use this form can be found at http://www.3gpp.org/specs/CR.htm. Proposed change affects: Title: Source to WG: Source to TSG: Category: UICC apps ME X Radio Access Network X Core Network X
EPS and E-UTRAN MBMS QoS Management 3, SA2 Date: 4/2/2008 Release: Rel-8 B
Use one of the following categories: Use one of the following releases: F (correction) R97 (Release 1997) A (corresponds to a correction in an earlier release) R98 (Release 1998) B (addition of feature), R99 (Release 1999) C (functional modification of feature) Rel-4 (Release 4) D (editorial modification) Rel-5 (Release 5) Detailed explanations of the above categories can Rel-6 (Release 6) be found in 3GPP TR 21.900. Rel-7 (Release 7) Rel-8 (Release 8)
Introduce QoS requirements and attributes for E-UTRAN and EPS into the specification. Allow for additional capabilities of parallel data flows within the same bearer. Motivations for multiple bearers are described in the CR itself namely the ability to separate media components to different QoS differentiated flows. Other usecases are described in S2-062684.
Summary of change: Based on the R6/R7 MBMS QoS section 6.3 a new section for E-UTRAN and EPS QoS requirements and attributes is added. The update includes: 1. Revisions to the original R6/R7 QoS section to match the EPS vocabulary of EPS bearers and data flows 2. Capabilities of delivering multiple SDFs as part of the same bearers are added. Consequences if not approved: Clauses affected: Other specs affected: EPS QoS concepts not introduced into R8 specification 3.2, 6 Y N X Other core specifications X Test specifications X O&M Specifications
Other comments:
This contribution is in part the result of work done as part of the IST C-Mobile project (http://c-mobile.ptinovacao.pt/). The C-Mobile project deals with enhancements to MBMS radio and core network capabilities, mobile broadcast service infrastructure capabilities and convergent architecture taking into account future usage scenarios, profiles, requirements and business models.
3.2 Abbreviations
For the purposes of the present document, the abbreviations in TR 21.905 [1] and TS 22.146 [2] apply. GBR SDF TFT TMGI TPF Guaranteed Bit Rate Service Data Flow Traffic Flow Template Temporary Mobile Group Identity Traffic Plane Function
For Guaranteed Bit-Rate (GBR) bearers the following additional parameters apply: Guaranteed bit-rate for each MBMS SDF Maximum bit-rate for each MBMS SDF
Additional to the QoS parameters each MBMS SDF may be associated with an MBMS service area identifier. The E-UTRAN shall transmit all traffic of an MBMS bearer in a manner which allows reception of all SDFs by an MBMS capable UE. For example all MBMS service data flows of a single MBMS bearer are to be transmitted on the same frequency. The mapping of multiple SDFs to a single MBMS bearer service allows for different media components delivered on the same MBMS bearer to be provided with differing QoS levels. For example a video streaming service might provision an SDF for video (e.g. low error rate, low delay, high GBR), an SDF for audio (e.g. medium error rate, low delay, low GBR) and another SDF for control traffic such a traffic key re-keying messages (e.g. very low error rate, medium delay, very low bit-rate GBR). Non-GBR MBMS bearer services are best suited for the transport of MBMS user services such as messaging or downloading. Buffering, shaping schemes and packet dropping may be applied to the traffic flow to adapt to the available resources and changing network conditions. The total transfer time is not critical for non-GBR bearer services since the content must normally have been received in totality and stored in the UE before the user can access it. GBR MBMS bearer services are best suited for the transport of MBMS user services such as streaming. As for point-topoint bearer services, the network should minimise the packet transfer delay of GBR bearer services as far as possible. Packet dropping should be the preferred traffic conditioning action applied to the traffic flow to adapt to the available resources. For MBMS, no indication is provided to the UE in cases where the RAN cannot provide the requested QoS. As a result, some UEs may not receive the MBMS session or parts of it. For non-GBR QoS, the RAN may continue to distribute data in congestion conditions but at potentially high packet loss rates, therefore the MBMS user service will have to provide sufficient redundancy within the data to be able to cope with the high packet loss.
3GPP
MBMS user services that would normally use non-GBR MBMS bearer services may however decide to use a streaming class MBMS bearer service if the MBMS user service cannot cope with high packet loss. The Allocation and Retention Priority of the MBMS bearer service allows for prioritisation between MBMS bearer services, and between MBMS bearer services and non MBMS bearer services. When low SDU error ratios are difficult to achieve, or when prevention of data loss is required, an MBMS user service may perform retransmission of MBMS data over a point-to-point PDP context.
3GPP