1、 ETSI TS 126 150 V14.0.0 (2017-04) Universal Mobile Telecommunications System (UMTS); LTE; Syndicated Feed Reception (SFR) within 3GPP environments; Protocols and codecs (3GPP TS 26.150 version 14.0.0 Release 14) TECHNICAL SPECIFICATION ETSI ETSI TS 126 150 V14.0.0 (2017-04)13GPP TS 26.150 version 1
2、4.0.0 Release 14Reference RTS/TSGS-0426150ve00 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
3、 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 be modified without the prior wr
4、itten 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 Secretariat. Users of the present docum
5、ent 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, please send your comment to one of
6、 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 permission of ETSI. The content of
7、 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 the ETSI logo are Trade Marks o
8、f 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 TS 126 150 V14.0.0 (2017-04)23GPP TS
9、 26.150 version 14.0.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-members, and can be found in ETSI S
10、R 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 to the ETSI IPR Policy, no inv
11、estigation, 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 document. Foreword This Technical Spec
12、ification (TS) 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 corresponding ETSI delivera
13、bles. 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 “shall“, “shall not“, “should“, “should not“, “may“, “need not“, “will“, “will not“, “can“ and “cannot“ are to be interpre
14、ted 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 TS 126 150 V14.0.0 (2017-04)33GPP TS 26.150 version 14.0.0 Release 14Contents Intellect
15、ual Property Rights 2g3Foreword . 2g3Modal verbs terminology 2g3Foreword . 5g3Introduction 5g31 Scope 6g32 References 6g33 Definitions and abbreviations . 6g33.1 Definitions 6g33.2 Abbreviations . 7g34 System description . 7g34.1 Functional overview . 7g34.2 Operations overview. 8g35 Protocols and p
16、rocedures for optimized feed reception . 9g35.1 Introduction 9g35.2 Syndicated Feed Discovery 9g35.2.1 Feed Discovery using an external UE application 9g35.2.2 Feed Discovery using the SFR enabled Feed Reader . 9g35.3 Activation for Syndicated Feed Reception . 10g35.3.1 Introduction. 10g35.3.2 Activ
17、ation triggered by the client . 10g35.3.2.1 Activation to a default SFR server. . 10g35.3.2.2 Discovery of a new SFR server via URI scheme 10g35.3.2.3 Activation process . 12g35.3.2.4 Deactivation process . 13g35.3.3 Activation triggered by the network . 13g35.4 Optimized reception initiation of a s
18、yndicated feed . 14g35.4.1 Introduction. 14g35.4.2 Optimized reception initiation triggered by the UE 14g35.4.3 External triggered optimized reception initiation . 15g35.5 Reception Termination . 16g35.6 Content Reception 17g35.7 SFR profile of DCD . 18g35.7.1 Procedure 18g35.7.2 Metadata . 18g35.7.
19、2.1 Application Profile Metadata 18g35.7.2.2 Channel Selection Metadata 19g35.7.2.3 Delivery Personalisation Metadata 19g35.7.2.4 General Channel Metadata 19g35.7.2.5 Delivery preference metadata 20g35.7.2.6 Content Metadata 20g35.7.2.7 Other DCD Metadata 21g36 Optimized handling of enclosure . 21g3
20、6.1 Introduction 21g36.2 RSS enclosure 21g36.3 ATOM enclosure 21g36.4 Providing alternative enclosures . 22g37 Media codecs and formats for syndicated feeds . 23g37.1 Media Transport for enclosures 23g37.2 Media codecs and formats 23g3ETSI ETSI TS 126 150 V14.0.0 (2017-04)43GPP TS 26.150 version 14.
21、0.0 Release 14Annex A (informative): Interaction examples 24g3A.1 Feed Discovery using the UE browser . 24g3A.2 Feed Discovery using the Syndicated Feed Reader . 25g3A.3 SFR Server Discovery triggered by Feed Discovery . 26g3A.4 Feed Discovery using the PC browser 28g3Annex B (informative): Change h
22、istory . 30g3History 31g3ETSI ETSI TS 126 150 V14.0.0 (2017-04)53GPP TS 26.150 version 14.0.0 Release 14Foreword This Technical Specification 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
23、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 number as follows: Version x.y.z where: x the first digit: 1 presented to TSG for information; 2 p
24、resented 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, updates, etc. z the third digit is incremented when editorial only changes have been incorporated
25、 in the document. Introduction Syndicated feeds, using technologies such as Atom and Really Simple Syndication (RSS), are widely used on todays Internet for various scheduled pull applications such as podcast. There are a number of non-compatible proprietary extensions and a number of different RSS
26、variants that may need to be installed and updated. OMA DCD has defined Channel and Content Metadata and related mechanisms for content delivery (including RSS and ATOM feeds) using Content Metadata XML extensions independently of any bearers. As a consequence there are no specific optimizations for
27、 3GPP services/bearers. OMA DCD specification allows embedding of OMA DCD XML namespace elements into RSS and Atom document (RSS and Atom feed “content packaging formats“). The OMA DCD Channel and Content Metadata are intended to offer different content delivery alternatives to receivers. The Syndic
28、ated Feed Reception (SFR) specification intents to define the optimized reception for any existing syndicated feeds using 3GPP specific bearers. SFR re-uses OMA DCD procedures and metadata for client server transactions. ETSI ETSI TS 126 150 V14.0.0 (2017-04)63GPP TS 26.150 version 14.0.0 Release 14
29、1 Scope The present document defines a set of media codecs, formats and transport/application protocols to enable syndicated feed reception within the 3GPP system. The present document includes information applicable to network operators, service providers and manufacturers. 2 References The followi
30、ng 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, subsequent revisions do not ap
31、ply. - 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 TR 21.905: “Vocabulary for
32、3GPP Specifications“. 2 3GPP TS 41.001: “GSM Specification set“. 3 RSS Advisory Board: “Really Simple Syndication 2.0“. 4 IETF RFC 4287: “The Atom Syndication Format“. 5 Open Mobile Alliance: “OMA Dynamic Content Delivery V1.0“, June 2009. 6 3GPP TS 26.234: “Transparent end-to-end Packet-switched St
33、reaming Service (PSS); Protocols and codecs“. 7 3GPP TS 26.244: “Transparent end-to-end packet switched streaming service (PSS); 3GPP file format (3GP)“. 8 3GPP TS 26.346: “Multimedia Broadcast/Multicast Service (MBMS); Protocols and codecs“. 9 Open Mobile Alliance: “OMA Push V2.2“, June 2009. 10 IE
34、TF RFC 4281: “The Codecs Parameter for Bucket Media Types“, Gellens R., Singer D. and Frojdh P., November 2005. 11 Open Mobile Alliance: “User Agent Profile Version 2.0“, February 2006. 3 Definitions and abbreviations 3.1 Definitions For the purposes of the present document, the terms and definition
35、s given in TR 21.905 1 and the following apply. A term defined in the present document takes precedence over the definition of the same term, if any, in TR 21.905 1. Syndicated Feed: A document, formatted according to RSS, ATOM, DCD or other syndicated feed formats, which is frequently updated with
36、new content updates. Syndicated Feed Reader: The client, which receives and processes one or more syndicated feed formats. Syndicated feed URI: A Uniform Resource Identifier, pointing to the document, which is formatted according to RSS, ATOM or other syndicated feed formats. ETSI ETSI TS 126 150 V1
37、4.0.0 (2017-04)73GPP TS 26.150 version 14.0.0 Release 14Syndicated Feed Provider: A content provider, which uses HTTP servers to provide syndicated feeds for download. SFR enabled Feed Reader: A feed reader, which is able to use optimized receptions and/or optimized enclosure handling as defined in
38、the specification. SFR Server: Server, which offers methods for optimized reception of syndicated feeds for SFR enabled Feed Readers. 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 doc
39、ument takes precedence over the definition of the same abbreviation, if any, in TR 21.905 1. GPRS General Packet Radio Service IP Internet Protocol DCD Dynamic Content Delivery MBMS Multimedia Broadcast/Multicast Service PSS Packet Switch Streaming RSS Really Simple Syndication SFR Syndicated Feed R
40、eception UE User Equipment URI Uniform Resource Identifier URL Uniform Resource Locator XML eXtensible Markup Language 4 System description 4.1 Functional overview The following diagram (see Figure 1) illustrates the overall system for syndicated feed reception (SFR). The system is subdivided into a
41、n SFR enabled Feed Reader, a SFR server and Syndicated Feed Provider. SFR enabled Feed Readers are clients, which provide all the functionality to parse, process and (opt.) present syndicated feeds. The SFR enabled Feed Reader can interact with any legacy syndicated feed server (e.g. RSS or Atom) us
42、ing HTTP. Additionally, those clients are also able to optimize the syndicated feed reception and/or optimize the handling of enclosures as defined in this specification. SFR enabled Feed Readers may support one or more syndicated feed formats such as RSS or Atom. From an implementation/deployment p
43、erspective, the SFR enabled Feed Reader can be shared by multiple ATOM/RSS-based applications or could be incorporated as a part of such an application. SFR enabled Feed Readers, which include “optimized reception“ of feed updates and/or enclosures support interactions with SFR servers. SFR servers
44、offer the SFR enabled Feed Reader with functions to optimize the reception of feed updates, attached media and enclosures. SFR servers interact with one or more syndicated feed servers. The interaction protocols and procedures of SFR server with Syndicated feed servers are out of scope of this speci
45、fication. The SFR server is a profiled OMA DCD server dedicated to optimize syndicated feed delivery. Syndicated feed providers are legacy functions, which use HTTP to offer their syndicated feeds. ETSI ETSI TS 126 150 V14.0.0 (2017-04)83GPP TS 26.150 version 14.0.0 Release 14Figure 1: Overall SFR S
46、ystem The SFR enabled Feed Reader interacts with the SFR server in order to get an optimized reception of syndicated feeds using the “Admin“ reference point. The SFR server provides the SFR enabled Feed Reader with feed content using OMA Push or MBMS download delivery using the “Push“ reference poin
47、t. The “Pull“ reference point is used, when the SFR enabled Feed Reader pull content from the SFR server. The “Admin“, “Push“ and “Pull“ reference points are realized using a subset of the OMA DCD-3, DCD-2 and DCD-1 reference points 5. The “Admin“ transactions between SFR enabled Feed Reader and SFR
48、 server re-use a subset of the OMA DCD-3 transactions. The “Push“ procedures between SFR server and SFR enabled Feed Reader re-use the OMA DCD-2 transactions (see section 5.6) and extend them to cover MBMS delivery via direct binding. The “Pull“ Interface to the SFR Server corresponds to “DCD-1“. Th
49、e “Pull“ procedures between SFR server and SFR enabled Feed Reader re-use a subset of OMA DCD-1 transactions (See section 5.6). The SFR enabled Feed Reader implements a profile of the DCD client and supports some of the DCD Enabled Client Application (DECA) functionalities. The “Poll“ interface to the syndicated feed provider (dashed line) corresponds to the stateless pull of legacy syndicated feed readers using HTTP. The “Poll“ interface is not in scope of this specification. The profiling of DCD 5 is defined in section 5.7. 4.2 Operations
