ETSI TR 126 907-2017 Universal Mobile Telecommunications System (UMTS) LTE HTML5 for a new presentation layer in 3GPP services (V14 0 0 3GPP TR 26 907 version 14 0 0 Release 14)《通用.pdf

1、 ETSI TR 126 907 V14.0.0 (2017-04) Universal Mobile Telecommunications System (UMTS); LTE; HTML5 for a new presentation layer in 3GPP services (3GPP TR 26.907 version 14.0.0 Release 14) TECHNICAL REPORT ETSI ETSI TR 126 907 V14.0.0 (2017-04)13GPP TR 26.907 version 14.0.0 Release 14Reference RTR/TSGS

2、-0426907ve00 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-Prfecture de Grasse (06) N 7803/88 Important notice The present docu

3、ment 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 be modified without the prior written authorization of ETSI. In ca

4、se 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 Secretariat. Users of the present document should be aware that the docum

5、ent 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, please send your comment to one of the following services: https:/po

6、rtal.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 permission of ETSI. The content of the PDF version shall not be modi

7、fied 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 the ETSI logo are Trade Marks of ETSI registered for the benefit

8、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 126 907 V14.0.0 (2017-04)23GPP TR 26.907 version 14.0.0 Release 14I

9、ntellectual 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-members, and can be found in ETSI SR 000 314: “Intellectual Property

10、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 to the ETSI IPR Policy, no investigation, including IPR searches

11、, 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 document. Foreword This Technical Report (TR) has been produced by ETSI

12、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 corresponding ETSI deliverables. The cross reference between GSM, UM

13、TS, 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 interpreted as described in clause 3.2 of the ETSI Drafting Rules (Verb

14、al 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 907 V14.0.0 (2017-04)33GPP TR 26.907 version 14.0.0 Release 14Contents Intellectual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g

15、3Foreword . 4g31 Scope 5g32 References 5g33 Definitions and abbreviations . 6g33.1 Definitions 6g33.2 Abbreviations . 6g34 Introduction 7g34.1 HTML5 7g34.1.1 Introduction. 7g34.1.2 New Tags 7g34.1.3 New HTML5 APIs . 8g34.1.3.1 Introduction . 8g34.1.3.2 Canvas API . 8g34.1.3.3 Cross-document messagin

16、g API . 8g34.1.3.4 Geolocation API 8g34.1.3.5 Audio and Video APIs 8g34.1.3.7 Media Source Extensions 8g34.1.3.8 Encrypted Media Extensions . 8g34.1.3.9 Forms API . 9g34.1.3.10 Server-Sent Events (SSE) . 9g34.1.3.11 WebSocket API and protocol 9g34.1.3.12 Web Storage API and Indexed DB API 9g34.1.3.1

17、3 Indexed DB API 9g34.1.3.14 Drag and Drop API . 9g34.1.3.15 XMLHttpRequest 9g34.1.3.16 Web Workers 9g34.1.3.17 Navigation Timing 9g34.1.3.18 WebGL 10g34.1.3.19 WebCrypto 10g34.2 Current Scene Description Solutions 10g34.2.1 Introduction. 10g34.2.2 XHTML Mobile Profile 10g34.2.3 DIMS 11g34.2.4 3GPP

18、SMIL Language Profile 12g35 Feature Analysis . 12g35.1 Presentation layer characteristics . 12g35.2 Comparison of SVG Animation based on SMIL vs. JavaScript . 12g36 HTML5 Profile for 3GPP Services 14g36.1 Features in the 3GPP Profile 14g36.2 Support for Scene Updates . 15g36.2.1 Introduction. 15g36.

19、2.2 Scene Update Description . 15g36.2.3 Scene Update Distribution 15g37 Conclusion 16g3Annex A: Change history 17g3History 18g3ETSI ETSI TR 126 907 V14.0.0 (2017-04)43GPP TR 26.907 version 14.0.0 Release 14Foreword This Technical Report has been produced by the 3rdGeneration Partnership Project (3G

20、PP). 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 the TSG with an identifying change of release date and an increase in version nu

21、mber 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 incremented for all changes of substance, i.e. technical enhancements, corrections, u

22、pdates, etc. z the third digit is incremented when editorial only changes have been incorporated in the document. ETSI ETSI TR 126 907 V14.0.0 (2017-04)53GPP TR 26.907 version 14.0.0 Release 141 Scope The present document is a study of existing scene description solutions for 3GPP services and an ev

23、aluation of HTML5 as an alternative and unified solution for providing a presentation layer for 3GPP services. 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

24、 date of publication, edition number, version number, etc.) or non-specific. - For a specific reference, subsequent 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 i

25、mplicitly refers to the latest version of that document in the same Release as the present document. 1 W3C Candidate Recommendation 6 August 2013, HTML5: “A vocabulary and associated APIs for HTML and XHTML“, http:/www.w3.org/TR/html5/. 2 W3C Candidate Recommendation 6 August2013: “HTML Canvas 2D Co

26、ntext“, http:/www.w3.org/TR/2dcontext/. 3 W3C Recommendation 24 October 2013: “Geolocation API Specification“, http:/www.w3.org/TR/geolocation-API/. 4 W3C Candidate Recommendation 11 December 2012: “Server-Sent Events“, http:/www.w3.org/TR/eventsource/. 5 W3C Candidate Recommendation 20 September 20

27、12: “The WebSocket API“, http:/www.w3.org/TR/websockets/. 6 W3C Recommendation 30 July 2013: “Web Storage“, http:/www.w3.org/TR/webstorage/. 7 W3C Working Draft 6 December 2012: “XMLHttpRequest Level 1“, http:/www.w3.org/TR/XMLHttpRequest/. 8 W3C Candidate Recommendation 01 May 2012: “Web Workers“,

28、http:/www.w3.org/TR/workers/. 9 3GPP TS 26.234: “Transparent end-to-end Packet-switched Streaming Service (PSS); Protocols and codecs“. 10 3GPP TS 26.346: “Multimedia Broadcast/Multicast Service (MBMS); Protocols and codecs“. 11 3GPP TS 26.247: “Transparent end-to-end Packet-switched Streaming Servi

29、ce (PSS); Progressive Download and Dynamic Adaptive Streaming over HTTP (3GP-DASH)“. 12 3GPP TS 26.114: “IP Multimedia Sybsystem (IMS); Multimedia Telephony Media handling and Interaction (MTSI)“. 13 3GPP TS 26.140: “Multimedia Messaging Service (MMS); Media formats and codecs“. 14 3GPP TS 26.246: “

30、Transparent end-to-end Packet-switched Streaming Service (PSS); 3GPP SMIL language profile“. 15 WAP Forum Specification: “XHTML Mobile Profile“, October 2001. 16 3GPP TS 26.142: “Dynamic and Interactive Multimedia Scenes (DIMS)“. ETSI ETSI TR 126 907 V14.0.0 (2017-04)63GPP TR 26.907 version 14.0.0 R

31、elease 1417 W3C Candidate Recommendation 09 January 2014: “Media Source Extensions“, http:/www.w3.org/TR/media-source/. 18 Void 19 ISO BMFF Byte Stream Format, http:/www.w3.org/2013/12/byte-stream-format-registry/isobmff-byte-stream-format.html 20 W3C Working Draft 18 February 2014: “Encrypted Media

32、 Extensions“, http:/www.w3.org/TR/encrypted-media/ 21 W3C Candidate Recommendation 09 May 2013: “HTML Media Capture“, http:/www.w3.org/TR/2013/CR-html-media-capture-20130509/. 22 W3C Recommendation 17 December 2012: “Navigation Timing“, http:/www.w3.org/TR/navigation-timing/. 23 Khronos Group, 01 Ma

33、rch 2013, WebGL Specification, version 1.0.2, https:/www.khronos.org/registry/webgl/specs/1.0/. 24 W3C Last Call Working Draft, 25 March 2014: “Web Cryptography API“, http:/www.w3.org/TR/WebCryptoAPI/. 25 W3C Candidate Recommendation 04 July 2012: “Indexed Database API“, http:/www.w3.org/TR/IndexedD

34、B/ 26 IETF RFC 5261: “An Extensible Markup Language (XML) Patch Operations Framework Utilizing XML Path Language (XPath) Selectors“. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definitions given in TR 21.905 1 and the following apply. A ter

35、m defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 1. 3.2 Abbreviations For the purposes of the present document, the abbreviations given in TR 21.905 1 and the following apply. An abbreviation defined in the present document takes precedenc

36、e over the definition of the same abbreviation, if any, in TR 21.905 1. API Application Programming Interface CSS Cascading Style Sheet DIMS Dynamic and Interactive Multimedia Scenes DOM Document Object Model EME Encrypted Media Extensions HTML5 Hyper-Text Mark-up Language ISO BMFF ISO Base Media Fi

37、le Format MBMS Multimedia Broadcast/Multicast Service MMS Multimedia Messaging Service MSE Media Source Extensions PSS Packet-switched Streaming Service RAP Random Access Point RTC Real-Time Communications RTP Real Time Protocol SMIL Synchronized Multimedia Integration Language SSE Server-Sent Event

38、s SVG Scalable Vector Graphics XML EXtensible Markup Language ETSI ETSI TR 126 907 V14.0.0 (2017-04)73GPP TR 26.907 version 14.0.0 Release 144 Introduction 4.1 HTML5 4.1.1 Introduction HTML5 was specified with the target of creating convergence among a wide range of interoperable browsers, which res

39、ulted from proprietary extensions of earlier HTML versions to fill identified gaps. HTML5 also defines and for the first time error handling procedures to deal with document processing errors to help circumvent minor but common syntactical mistakes. As part of the simplicity goal, HTML5 aims at oper

40、ating in a plugin-free environment by providing APIs to fulfil most of the plugin needs. Finally, HTML5 aims at simplifying the syntax to ease authoring of web applications. 4.1.2 New Tags HTML5 defines a set of new elements that are discussed in the following list: - Video: a standard way to embed

41、video content on a web page without using browser plugins. The playback controls are provided through Javascript. - Audio: a standard way to embed audio content on a web page without using browser plugins. - Canvas: a resolution-dependent bitmap canvas together with scripts that are used for renderi

42、ng graphs, game graphics, or other visual images on the fly. - Svg: HTML5 provides support for inline SVG fragments as well as a fallback mechanism for browsers that do not support SVG. - Article: specifies independent self-contained content. An article should make sense on its own and should be dis

43、tributable independently from the rest of the site. - Header: specifies a header for a document or section. This element should be used as a container for introductory content or set of navigational links. - Footer: defines a footer for a document or section. A footer element should contain informat

44、ion about its containing element. - Output: represents the result of a calculation. - Source: is used to specify multiple media resources for media elements such as video and audio. The source tag allows to specific alternative video/audio files, which the browser may choose from, based on its media

45、 type or codec support. - Time: defines either a time or a date in the Gregorian calendar, optionally with a time and time-zone. - Input/capture: although the tag is not new for HTML5, the capture attribute is. This allows for media capture and file upload 21. ETSI ETSI TR 126 907 V14.0.0 (2017-04)8

46、3GPP TR 26.907 version 14.0.0 Release 144.1.3 New HTML5 APIs 4.1.3.1 Introduction HTML5 can be considered as an umbrella set of specifications, that includes the markup language specification and additionally a wide range of APIs. The following sections briefly introduce the APIs that are currently

47、part of HTML5. Only specifications that have reached Candidate Recommendation status in the W3C are described. However, several specifications under development related to areas such as local media capture, peer-to-peer real time communications (WebRTC), sensors (proximity, gyroscope, etc.), rich au

48、dio processing, and technologies impacting mobile devices should be considered for any 3GPP presentation layer in the near future. 4.1.3.2 Canvas API The canvas API 2 defines a canvas element and a set of drawing operations. A canvas element creates a rectangular area on the page. Javascript is used

49、 to perform the drawing operations. 4.1.3.3 Cross-document messaging API HTML5 introduces an API 1 to enable safe communication between different parts of the document (e.g. different frames). Additionally, HTML5 introduces the security concept of origin. This is used to enable secure cross-referencing between documents that are located on the same origin, identified through a shared URL path. 4.1.3.4 Geolocation API The Geolocation API 3 allows the user to share their location with web applic