5.7 SFR profile of DCD

26.1503GPPProtocols and codecsRelease 17Syndicated Feed Reception (SFR) within 3GPP environmentsTS

Tools: ARFCN - Frequency Conversion for 5G NR/LTE/UMTS/GSM

5.7.1 Procedure

The SFR profile defines the set of DCD procedures that an SFR enabled Feed Reader and an SFR server supports:

SFR enabled Feed Reader and an SFR server shall support the following DCD procedures:

– Channel Discovery (section 7.1.3.10.3 of [5])

– Activation (section 7.1.3.1 of [5]) and deactivation (section 7.1.3.2 of [5])

– Application Registration (section 7.1.3.3 of [5]) and deregistration (section 7.1.3.4 of [5])

– Channel Subscription (section 7.1.3.7 of [5]) and un-subscription (section 7.1.3.8 of [5])

– Channel Suspend and Channel Resume (section 7.1.3.11 of [5])

– Syndicated Feed Delivery over DCD-2 using OMA Push and MBMS if these delivery methods are supported on the device

– Syndicated Feed Delivery over DCD-1

– Embedding DCD metadata into RSS and Atom feeds as per sections 9.2 and 9.3 of [5]

Other DCD procedures may be supported but are not required for this specification:

– Content Submission

– Usage tracking report

– Channel Subscription Update

– Content Repair

– Contextual Information Update

– Channel Metadata update

– All procedures between DCD client and DCD enabled Client Application

– All procedures between DCD servers and DCD content providers

5.7.2 Metadata

5.7.2.1 Application Profile Metadata

The SFR enabled Feed Reader and the SFR server shall support the following subset of DCD application profile metadata as specified in section 8.1.2 of [5]:

– "application-profile" element with the following attributes:

– "application-id"

– "dcd-channel-selection-metadata" element

5.7.2.2 Channel Selection Metadata

The SFR enabled Feed Reader and the SFR server shall support all Channel Selection metadata as specified in section 8.2.2.1.1 of [5].

5.7.2.3 Delivery Personalisation Metadata

Channel Delivery personalisation metadata listed below, as specified in section 8.2.2.1.2 of [5], with specific values for particular parameters. The Channel delivery personalization metadata is always sent from client to server:

– "channel-id" attribute: either RSS URL or value of "atom:id"

– "content-availability-notification" attribute: The SFR enabled Feed Reader should set this to"true"

– "delivery-when-roaming" attribute: default False

"dcd-2-broadcast-profile" element with the following additional sub-parameters (Mbms-access-info and usd-description) to support the direct binding to MBMS:

dcd-2-broadcast-profile

0..1

A set of parameters that define how the DCD Client receives content via the DCD-2 interface for specific transports (note: WAP Push requires no special configuration).

Contains the following attributes:

cell-broadcast-message-id

Contains the following sub-elements:

bcast-access-info

mbms-acess-info

Structure

Mbms-access-info

0..1

MBMS specific connection details for file delivery session over which the SFR Enabled feed Reader should expect DCD-2 interface data to be delivered via MBMS

Contains the following sub-elements:

Sdp-description

Structure

DS, DC

usd-description

URI to the MBMS User Service Description Fragment

String

DS, DC

5.7.2.4 General Channel Metadata

The SFR enabled Feed Reader and the SFR server shall support the following DCD general channel metadata as specified in section 8.2.2.2.1 of [5] with the following values. The general channel metadata is provided from the SFR server to the SFR enabled Feed Reader:

– DCD Channel-ID: SFR server or SFR Feed provider shall use the DCD Channel ID for identification of the RSS feed. The value of Channel ID shall be identical to the RSS feed URL. In the case of Atom feed, the DCD Channel ID shall take the value of the "atom:id" element.

– DCD Content-type : This metadata parameter is provided by SFR server and used by SFR enabled Feed Reader to filter available syndicated feeds in the channel guide. It is used at channel/feed discovery stage to enable the SFR server to match application preferences and available feeds and to create a subset of channels/feeds that correspond to the preferences of installed SFR enabled applications. This subset is returned to device during channel discovery and the SFR client enables subscription to the particular feeds. The DCD content-type corresponds to the rss category or atom:category fields.

– DCD Mime-type: This metadata parameter is provided to indicate needed mime type support to correctly receive the syndicated feed. This parameter is used at channel/feed discovery stage e.g. filtering relevant channels and content for the UE:

– By SFR enabled Feed Reader to announce capabilities (i.e. supported mime-types).

– By SFR server to announce types of syndicated feeds and of media content included in the enclosures of the syndicated feeds in the channel. RFC 4281 shall be used to indicate the mime-type.

The SFR enabled Feed Reader and the SFR server may support the following DCD general channel metadata, as specified in section 8.2.2.2.1 of [5], that corresponds to some ATOM or RSS feed metadata. If these DCD metadata are supported, the value of equivalent parameters in ATOM or RSS shall be used as values for the corresponding DCD metadata:

– DCD Channel-name: This DCD channel metadata corresponds to the RSS Channel Title and/or to the ATOM Feed.title parameter.

– DCD Updated: This DCD channel metadata corresponds to the RSS channel lastbuildDate and/or to the ATOM feed.updated parameter.

– DCD channel-description: This DCD channel metadata corresponds to the RSS channel description and/or to the ATOM feed.subtitle parameter.

– DCD genre: This DCD channel metadata corresponds to the RSS channel category and/or to the ATOM feed.category.

– DCD channel-icon: This DCD channel metadata corresponds to the RSS channel image and/or to the ATOM feed.icon/ feed.logo. The DCD Channel-icon provides a mime-type attribute that is not available in ATOM and RSS.

Other general channel metadata as described in [5] and not listed above may be supported but are not required for SFR.

5.7.2.5 Delivery preference metadata

The delivery preference metadata listed below, as specified in section 8.2.2.2.3 of [5], with specific values for particular parameters, shall be supported. Delivery preference metadata are provided either by feed provider or SFR server:

– "channel-id" attribute: either RSS URL or value of "atom:id"

– "dcd-interface":

– "DCD-2/point-to-point": OMA-Push with point-to-point bearers

– "DCD-2/Broadcast": Content delivery with MBMS Download delivery method in case of direct MBMS binding

– "DCD-1/HTTP(S)": Content reception using unicast UMTS bearer services

– "dcd-2-broadcast-profile" with the additional element "Mbms-access-info" define in section 5.7.2.3.

5.7.2.6 Content Metadata

Content Metadata are provided by the feed provider. In SFR, content metadata are RSS and ATOM metadata and may consist of DCD Content metadata. The SFR server can update or add some DCD metadata to the content metadata received from the feed provider.

If the syndicated feed provider uses the DCD content metadata, or if the SFR server extends the feed metadata with DCD metadata, then the following shall apply:

The SFR enabled Feed Reader and the SFR server shall support the DCD content metadata as specified in section 8.3.2 of [5] and with the particular limitations described below:

– DCD mime-type: This parameter shall be used by SFR to indicate the expected mime-type of the content item and of the enclosure in the item. RFC 4281 shall be used to indicate the mime-type.

– DCD replace-content-id: this parameter shall be used by SFR to indicate which content item shall be replaced by the content item for which a content-id (RSS item guid and/or ATOM feed.entry.id) is provided in the same message.

The SFR enabled Feed Reader and the SFR server may support the following DCD content metadata as specified in section 8.3.2 of [5] that corresponds to some ATOM or RSS entry metadata. If these DCD metadata are supported, the value of equivalent parameters in ATOM or RSS shall be used as values for the corresponding DCD metadata:

– DCD content-id: This DCD content metadata corresponds to the RSS item guid and/or to the ATOM feed.entry.id parameter.

– DCD content-name: This DCD content metadata corresponds to the RSS item title and/or to the ATOM feed.entry.title parameter.

– DCD content-update: This DCD content metadata corresponds to the ATOM feed.entry.updated parameter. There is no equivalent parameter in RSS.

5.7.2.7 Other DCD Metadata

Other DCD metadata may be supported but are not required for SFR v1.0:

– Charging metadata as specified in section 8.2.2.2.1 of [5]