1、 ETSI TS 1Digital cellular telecoUniversal Mobile TelSyndicated Feed RecepPro(3GPP TS 26.1TECHNICAL SPECIFICATION126 150 V13.0.0 (2016communications system (Phaelecommunications System (LTE; eption (SFR) within 3GPP envirotocols and codecs .150 version 13.0.0 Release 1316-01) hase 2+); (UMTS); v ron
2、ments; 13) ETSI ETSI TS 126 150 V13.0.0 (2016-01)13GPP TS 26.150 version 13.0.0 Release 13Reference RTS/TSGS-0426150vd00 Keywords GSM,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 Asso
3、ciation but non lucratif enregistre la Sous-Prfecture 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 pri
4、nt versions of the present document shall not be 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 o
5、n a specific network drive within ETSI Secretariat. 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 http:/portal.etsi.org/tb/status/status.asp If you fin
6、d errors in the present document, please 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 microfil
7、m except as authorized by written permission 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 2016. All rights rese
8、rved. DECTTM, PLUGTESTSTM, UMTSTMand 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
9、 the GSM Association. ETSI ETSI TS 126 150 V13.0.0 (2016-01)23GPP TS 26.150 version 13.0.0 Release 13Intellectual 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 av
10、ailable for ETSI members and non-members, 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 se
11、rver (https:/ipr.etsi.org/). Pursuant 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 bec
12、ome, essential to the present document. Foreword This Technical Specification (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 b
13、e interpreted as being references to the corresponding 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 “shall“, “shall not“, “should“, “should not“, “may“, “
14、need not“, “will“, “will not“, “can“ and “cannot“ are to be interpreted 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 V13.0.0
15、(2016-01)33GPP TS 26.150 version 13.0.0 Release 13Contents Intellectual 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 Fu
16、nctional overview . 7g34.2 Operations overview. 8g35 Protocols and procedures 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
17、 Syndicated Feed Reception . 10g35.3.1 Introduction. 10g35.3.2 Activation 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 trig
18、gered by the network . 13g35.4 Optimized reception initiation of a syndicated 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 SF
19、R profile of DCD . 18g35.7.1 Procedure 18g35.7.2 Metadata . 18g35.7.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
20、.2.7 Other DCD Metadata 21g36 Optimized handling of enclosure . 21g36.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 2
21、3g3ETSI ETSI TS 126 150 V13.0.0 (2016-01)43GPP TS 26.150 version 13.0.0 Release 13Annex 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 Fee
22、d Discovery using the PC browser 28g3Annex B (informative): Change history . 30g3History 31g3ETSI ETSI TS 126 150 V13.0.0 (2016-01)53GPP TS 26.150 version 13.0.0 Release 13Foreword This Technical Specification has been produced by the 3rdGeneration Partnership Project (3GPP). The contents of the pre
23、sent 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 number as follows: Version x.y
24、.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, updates, etc. z the third dig
25、it is incremented when editorial only changes have been incorporated 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
26、non-compatible proprietary extensions and a number of different RSS 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 a
27、ny bearers. As a consequence there are no specific optimizations for 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 of
28、fer different content delivery alternatives to receivers. The Syndicated 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 T
29、S 126 150 V13.0.0 (2016-01)63GPP TS 26.150 version 13.0.0 Release 131 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 oper
30、ators, service providers and manufacturers. 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-
31、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 implicitly refers to the latest version of that document in the same
32、 Release as the present document. 1 3GPP TR 21.905: “Vocabulary for 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“, Jun
33、e 2009. 6 3GPP TS 26.234: “Transparent end-to-end Packet-switched Streaming 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 an
34、d codecs“. 9 Open Mobile Alliance: “OMA Push V2.2“, June 2009. 10 IETF 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 Definition
35、s For the purposes of the present document, the terms and definitions 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
36、 or other syndicated feed formats, which is frequently updated with new content updates. Syndicated Feed Reader: The client, which receives and processes one or more syndicated feed formats. ETSI ETSI TS 126 150 V13.0.0 (2016-01)73GPP TS 26.150 version 13.0.0 Release 13Syndicated feed URI: A Uniform
37、 Resource Identifier, pointing to the document, which is formatted according to RSS, ATOM or other syndicated feed formats. Syndicated 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 opt
38、imized receptions and/or optimized enclosure handling as defined in 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
39、 and the following apply. An abbreviation defined in the present document 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
40、Switch Streaming RSS Really Simple Syndication SFR Syndicated Feed Reception 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
41、for syndicated feed reception (SFR). The system is subdivided into an 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 i
42、nteract with any legacy syndicated feed server (e.g. RSS or Atom) using 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 f
43、eed formats such as RSS or Atom. From an implementation/deployment perspective, 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 a
44、nd/or enclosures support interactions with SFR servers. SFR servers 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 SF
45、R server with Syndicated feed servers are out of scope of this specification. 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 V13.0.0 (2016
46、-01)83GPP TS 26.150 version 13.0.0 Release 13Figure 1: Overall SFR System 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 usin
47、g OMA Push or MBMS download delivery using the “Push“ reference point. 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
48、 5. The “Admin“ transactions between SFR enabled Feed Reader and SFR 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 bindin
49、g. The “Pull“ Interface to the SFR Server corresponds to “DCD-1“. The “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
