1、 ETSI TR 126 957 V14.1.0 (2017-04) Universal Mobile Telecommunications System (UMTS); LTE; Study on Server And Network-assisted Dynamic Adaptive Streaming over HTTP (DASH) (SAND) for 3GPP multimedia services (3GPP TR 26.957 version 14.1.0 Release 14) TECHNICAL REPORT ETSI ETSI TR 126 957 V14.1.0 (20
2、17-04)13GPP TR 26.957 version 14.1.0 Release 14Reference RTR/TSGS-0426957ve10 Keywords LTE,UMTS ETSI 650 Route des Lucioles F-06921 Sophia Antipolis Cedex - FRANCE Tel.: +33 4 92 94 42 00 Fax: +33 4 93 65 47 16 Siret N 348 623 562 00017 - NAF 742 C Association but non lucratif enregistre la Sous-Prf
3、ecture de Grasse (06) N 7803/88 Important notice The present document can be downloaded from: http:/www.etsi.org/standards-search The present document may be made available in electronic versions and/or in print. The content of any electronic and/or print versions of the present document shall not b
4、e modified without the prior written authorization of ETSI. In case of any existing or perceived difference in contents between such versions and/or in print, the only prevailing document is the print of the Portable Document Format (PDF) version kept on a specific network drive within ETSI Secretar
5、iat. Users of the present document should be aware that the document may be subject to revision or change of status. Information on the current status of this and other ETSI documents is available at https:/portal.etsi.org/TB/ETSIDeliverableStatus.aspx If you find errors in the present document, ple
6、ase send your comment to one of the following services: https:/portal.etsi.org/People/CommiteeSupportStaff.aspx Copyright Notification No part may be reproduced or utilized in any form or by any means, electronic or mechanical, including photocopying and microfilm except as authorized by written per
7、mission of ETSI. The content of the PDF version shall not be modified without the written authorization of ETSI. The copyright and the foregoing restriction extend to reproduction in all media. European Telecommunications Standards Institute 2017. All rights reserved. DECTTM, PLUGTESTSTM, UMTSTMand
8、the ETSI logo are Trade Marks of ETSI registered for the benefit of its Members. 3GPPTM and LTE are Trade Marks of ETSI registered for the benefit of its Members and of the 3GPP Organizational Partners. GSM and the GSM logo are Trade Marks registered and owned by the GSM Association. ETSI ETSI TR 12
9、6 957 V14.1.0 (2017-04)23GPP TR 26.957 version 14.1.0 Release 14Intellectual Property Rights IPRs essential or potentially essential to the present document may have been declared to ETSI. The information pertaining to these essential IPRs, if any, is publicly available for ETSI members and non-memb
10、ers, and can be found in ETSI SR 000 314: “Intellectual Property Rights (IPRs); Essential, or potentially Essential, IPRs notified to ETSI in respect of ETSI standards“, which is available from the ETSI Secretariat. Latest updates are available on the ETSI Web server (https:/ipr.etsi.org/). Pursuant
11、 to the ETSI IPR Policy, no investigation, including IPR searches, has been carried out by ETSI. No guarantee can be given as to the existence of other IPRs not referenced in ETSI SR 000 314 (or the updates on the ETSI Web server) which are, or may be, or may become, essential to the present documen
12、t. Foreword This Technical Report (TR) has been produced by ETSI 3rd Generation Partnership Project (3GPP). The present document may refer to technical specifications or reports using their 3GPP identities, UMTS identities or GSM identities. These should be interpreted as being references to the cor
13、responding ETSI deliverables. The cross reference between GSM, UMTS, 3GPP and ETSI identities can be found under http:/webapp.etsi.org/key/queryform.asp. Modal verbs terminology In the present document “should“, “should not“, “may“, “need not“, “will“, “will not“, “can“ and “cannot“ are to be interp
14、reted as described in clause 3.2 of the ETSI Drafting Rules (Verbal forms for the expression of provisions). “must“ and “must not“ are NOT allowed in ETSI deliverables except when used in direct citation. ETSI ETSI TR 126 957 V14.1.0 (2017-04)33GPP TR 26.957 version 14.1.0 Release 14Contents Intelle
15、ctual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g31 Scope 6g32 References 6g33 Abbreviations . 7g34 Overview of MPEG Server And Network Assisted DASH (SAND) in ISO/IEC 23009-5 . 7g35 Architectural considerations for SAND . 12g35.1 SAND in PSS architecture . 12g35.2 SAND
16、 architecture for OTT streaming services 12g35.3 Alternative SAND architecture for OTT streaming services 14g35.4 SAND architecture for generic OTT streaming services 15g36 SAND use cases and relevance to 3GPP environment . 16g36.1 Use Case # 1: Content-Provider Optimized Zero-Rating . 16g36.1.1 Use
17、 case description 16g36.1.2 Recommended requirements and working assumptions . 17g36.1.3 Gap analysis w.r.t. existing 3GPP technologies 17g36.1.4 Potential solutions including relevant SAND functionality 17g36.2 Use Case # 2: Consistent QoE/QoS for DASH Users 17g36.2.1 Use case description 17g36.2.2
18、 Recommended requirements and working assumptions . 18g36.2.3 Gap analysis w.r.t. existing 3GPP technologies 18g36.2.4 Potential solutions including relevant SAND functionality 18g36.3 Use Case # 3 Proxy Caching 20g36.3.1 Use case description 20g36.3.2 Recommended requirements and working assumption
19、s . 20g36.3.3 Gap analysis w.r.t. existing 3GPP technologies 20g36.3.3.1 Partial representation caching . 20g36.3.3.2 Next segment caching . 20g36.3.3.3 Multi-CDN offering 21g36.3.4 Potential solutions including relevant SAND functionality 21g36.4 Use Case # 4 Network Assistance for DASH . 23g36.4.1
20、 Use case description 23g36.4.1.0 Introduction . 23g36.4.1.1 Network Assistance . 23g36.4.1.2 Relationship between Network Assistance and media server communication 24g36.4.1.3 UE considerations . 25g36.4.1.3.1 Mitigation of unwarranted usage of the Network Assistance function 25g36.4.1.3.2 UE acces
21、s to the Network Assistance function . 25g36.4.2 Recommended requirements and working assumptions . 25g36.4.3 Gap analysis w.r.t. existing 3GPP technologies 25g36.4.4 Potential solutions including relevant SAND functionality 26g36.4.5 Simulation and test results 28g37 MOOD for handling TLS protected
22、 unicast traffic 31g37.1 Description of the Release 12 solution for MOOD 31g37.2 Overview of a SAND WebSocket solution for MOOD . 32g37.2.1 Architecture 32g37.2.2 Procedures. 33g38 Streaming enhancements from QoE-Aware resource allocation 35g38.1 Introduction 35g3ETSI ETSI TR 126 957 V14.1.0 (2017-0
23、4)43GPP TR 26.957 version 14.1.0 Release 148.2 Simulation methodology and setup 35g38.3 Video-Aware QoS optimizations at the Core . 38g38.4 Video QoE-Aware scheduling at the RAN . 41g38.5 Relationship to SAND 44g38.6 Performance evaluation results . 44g39 Cross-Origin Resource Sharing (CORS) 49g39.1
24、 Introduction 49g39.2 CORS Considerations for SAND . 49g310 Connections to RAN Study on Context-Aware service delivery . 50g311 Conclusions and Recommendations . 50g3Annex A: Change history 52g3History 53g3ETSI ETSI TR 126 957 V14.1.0 (2017-04)53GPP TR 26.957 version 14.1.0 Release 14Foreword This T
25、echnical Report has been produced by the 3rdGeneration Partnership Project (3GPP). The contents of the present document are subject to continuing work within the TSG and may change following formal TSG approval. Should the TSG modify the contents of the present document, it will be re-released by th
26、e TSG with an identifying change of release date and an increase in version number as follows: Version x.y.z where: x the first digit: 1 presented to TSG for information; 2 presented to TSG for approval; 3 or greater indicates TSG approved document under change control. y the second digit is increme
27、nted for all changes of substance, i.e. technical enhancements, corrections, updates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. ETSI ETSI TR 126 957 V14.1.0 (2017-04)63GPP TR 26.957 version 14.1.0 Release 141 Scope The present document
28、evaluates the MPEG DASH SAND (ISO/IEC 23009-5) specification to: - Ensure that 3GPP and MPEG remain aligned on their respective DASH specifications. - Identify enhancements offered by MPEG DASH SAND (ISO/IEC 23009-5) in the 3GPP environment, and recommend necessary modifications to the 3GPP specific
29、ations including DASH to enable these enhancements. In particular, the following elements of functionality may be of particular 3GPP relevance and are studied: - Streaming enhancements via intelligent caching, processing and delivery optimizations on the server and/or network side, based on feedback
30、 from clients on anticipated DASH Segments, accepted alternative DASH Representations and Adaptation Sets, and requested bandwidth. - Improved adaptation on the client side, based on network/server-side information such as cached Segments, alternative Segment availability, and network throughput/QoS
31、. 2 References The following documents contain provisions which, through reference in this text, constitute provisions of the present document. - References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. - For a specific reference, subs
32、equent revisions do not apply. - For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document. 1 3GPP T
33、R 21.905: “Vocabulary for 3GPP Specifications“. 2 ISO/IEC 23009-5:2016: “Information Technology Dynamic adaptive streaming over HTTP (DASH) Part 5: Server and network assisted DASH (SAND)“. 3 ISO/IEC 23009-1:2014: “ Information technology - Dynamic adaptive streaming over HTTP (DASH) - Part 1: Media
34、 presentation description and segment formats“. 4 3GPP TS 26.247: “3GPP TS 26.247: “Transparent end-to-end Packet-switched Streaming Service (PSS); Progressive Download and Dynamic Adaptive Streaming over HTTP (3GP-DASH)“. 5 3GPP TS 26.233: “Transparent end-to-end packet switched streaming service (
35、PSS); General description“. 6 3GPP TR 26.938: “Packet-switched Streaming Service (PSS); Improved support for dynamic adaptive streaming over HTTP in 3GPP“. 7 3GPP TS 23.203: “Policy and Charging Control Architecture“. 8 3GPP TS 23.207: “End-to-End Quality of Service (QoS) Concept and Architecture“.
36、9 3GPP TS 29.213: “Policy and charging control signalling flows and Quality of Service (QoS) parameter mapping“. 10 3GPP TS 29.214: “Policy and charging control over Rx reference point“. 11 M. Andrews, Q. Lijun, and A. Stolyar, “Optimal utility based multi-user throughput allocation subject to throu
37、ghput constraints,“ in Proc. IEEE INFOCOM 2005, vol. 4, pp. 2415-2424 vol. 4, 2005. ETSI ETSI TR 126 957 V14.1.0 (2017-04)73GPP TR 26.957 version 14.1.0 Release 1412 V. Ramamurthi and O. Oyman, “Video-QoE Aware Radio Resource Allocation for HTTP Adaptive Streaming “, in Proc. IEEE International Conf
38、erence on Communications (ICC), 2014, Sydney, Australia, June 2014. 13 A. Jalali, R. Padovani, and R. Pankaj, “Data throughput of CDMA-HDR a high efficiency-high data rate personal communication wireless system,“ in Proc. IEEE 51st Vehicular Technology Conference, Tokyo, vol. 3, pp. 1854-1858, 2000.
39、 14 Z. Xiaoqing, T. Schierl, T. Wiegand, and B. Girod, “Distributed Media-Aware Rate Allocation for Video Multicast Over Wireless Networks,“ IEEE Transactions on Circuits and Systems for Video Technology, vol. 21, pp. 1181-1192, 2011. 15 S. Singh, O. Oyman, A. Papathanassiou, D. Chatterjee, and J. G
40、. Andrews, “Video capacity and QoE enhancements over LTE,“ in Proc. IEEE International Conference on Communications (ICC), 2012 pp. 7071-7076, 2012. 16 W3C Recommendation, Cross-Origin Resource Sharing, http:/www.w3.org/TR/cors/. 17 IETF RFC 6455: “The WebSocket Protocol“. 18 OMA-ERELD-DM-V1_2-20070
41、209-A: “Enabler Release Definition for OMA Device Management, Approved Version 1.2“. 19 3GPP TR 36.933: “Study on Context Aware Service Delivery in RAN for LTE“. 3 Abbreviations For the purposes of the present document, the abbreviations given in TR 21.905 1 and the following apply. An abbreviation
42、defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905 1. CDN Content Delivery Network CORS Cross-Origin Resource Sharing DANE DASH-Aware Network Element DASH Dynamic Adaptive Streaming over HTTP MPD Media Presentation Description OTT Over
43、-The-Top PED Parameters Enhancing Delivery PER Parameters Enhancing ReceptionRNE Regular Network Element SAND Server and Network Assisted DASH XML Extensible Markup Language 4 Overview of MPEG Server And Network Assisted DASH (SAND) in ISO/IEC 23009-5 MPEGs Server and Network Assisted DASH (SAND) te
44、chnology, i.e., specified in ISO/IEC 23009-5 2 offers standardized interfaces for service providers and operators to enhance streaming experience. In order to enhance the delivery of DASH content, SAND introduces messages between DASH clients and network elements or between various network elements
45、for the purpose to improve efficiency of streaming sessions by providing information about real-time operational characteristics of networks, servers, proxies, caches, CDNs as well as DASH clients performance and status. SAND addresses the following: - Unidirectional/bidirectional, point-to-point/mu
46、ltipoint communication with and without session (management) between servers/CDNs and DASH clients, - Mechanisms for providing content-awareness and service-awareness towards the underlying protocol stack including server and/or network assistance, - Various impacts on elements of the existing Inter
47、net infrastructure such as servers, proxies, caches and CDNs, ETSI ETSI TR 126 957 V14.1.0 (2017-04)83GPP TR 26.957 version 14.1.0 Release 14- QoS and QoE support for DASH-based services, - Scalability in general and specifically for logging interfaces, and - Analytics and monitoring of DASH-based s
48、ervices. The SAND reference architecture is based on four broad categories of elements: i) DASH streaming clients. ii) Regular network elements (RNE), which are DASH content unaware and treat DASH-related video delivery objects as any other object, but are present on the path between origin server a
49、nd DASH clients, e.g. transparent caches. iii) DASH-aware network elements (DANE), which have at least minimum intelligence about DASH; for instance they may be aware that the delivered objects are DASH-formatted objects such as the MPD or DASH segments, and may prioritize, parse or even modify such objects, and iv) Metrics server, which are DASH aware and are in charge of gathering metrics from DASH clients. Based on these elements, the SAND reference architecture is defined as shown in Figure 4.2. Within this architecture
