5.4 Optimized reception initiation of a syndicated feed

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

5.4.1 Introduction

The sections below specify the methods for initiating the optimised reception of feeds, whether the initiation is triggered by an external component,by the SFR enabled Feed Reader, or by the SFR server.

5.4.2 Optimized reception initiation triggered by the UE

The reception initiation for optimized reception procedure may be triggered when a UE subscribes to a syndicated feed. A UE subscribes to a syndicated feed, when it is interested in the content updates provided in this syndicated feed.

The SFR enabled Feed Reader registers with the SFR server to enable optimized reception of syndicated feed updates and its enclosures and attachments (e.g. images). The "activation for syndicated feed reception" procedure (section 5.3) shall be executed at least once before the reception initiation procedure.

The SFR server may need to establish a relation with the Syndicated Feed Provider to become aware about new content. If the Syndicated Feed Provider is a DCD Content Provider, then the SFR server should use procedures as defined in section 7.2.1 of [5] for the OMA CPR interface. In a scenario whereby the syndicated feed provider is not a "DCD Content Provider" and does not support the OMA-CPR interface, the SFR server retrieves the content from the syndicated feed provider via an HTTP GET request and inserts the relevant metadata in the feed both for optimised handling of enclosures and for optimised delivery.

Figure 6: Reception Initiation triggered by the UE

The Reception Initiation procedure (see figure 6) uses a subset of the OMA DCD Channel Subscription Procedure (see section 7.1.3.7 of [5]).

Information Elements of the ChannelSubscriptionRequest message:

– Session-ID: Mandatory in OMA DCD and SFR.

– Message-ID: Mandatory in OMA DCD and SFR.

– Delivery-personalization-Metadata: Conditional in OMA DCD and SFR. Delivery-personalization-metadata contains at least the Channel-ID. In SFR the Channel-ID shall take the value of the feed address. The relevant subset of delivery personalization metadata for SFR is defined in section 5.7.

– Channel-ID: Conditional in OMA DCD and SFR.

– Subscription-ID Conditional in OMA DCD and SFR (issued upon subscription personalization).

Information Elements of the ChannelSubscriptionResponse message:

– Session-ID: Mandatory in OMA DCD and SFR.

– Message-ID: Mandatory in OMA DCD and SFR.

– Channel-Metadata (delivery-preference-metadata): Optional in OMA DCD and SFR. If delivery-preference-metadata is return, the feed address is provided as the value of the channel-id. Relevant subset of the delivery-preference metadata for SFR is defined in section 5.7.

Note: The Channel-Metadata is used to describe the type of "Push" bearer used for syndicated feed delivery. The dcd-interface attribute has the value "DCD-2/Point-to-Point" when OMA Push is used for reception. Other values to indicate the usage of MBMS Download are described in section 5.7.

The delivery over MBMS might be done via the DCD OMA-BCAST adaptation specification or as an MBMS direct adaptation specification as described in section 5.6.

5.4.3 External triggered optimized reception initiation

The user discovers a feed via other means (e.g. from an operator’s web portal) and subscribes the UE externally (e.g. using a PC) for optimized syndicated feed reception. The user provides the relevant information (e.g. MSISDN) to receive the syndicated feed on its UE.

Figure 7: Reception Initiation triggered by an external device

If an external device triggers the Reception Initiation through the SFR server, a subset of the OMA DCD Channel Subscription Notification Procedure (see section 7.1.3.9 of [5]) is used (see figure 7).

Information Elements of the ChannelSubscriptionNotification message:

– Session-ID: Mandatory in OMA DCD and SFR.

– Message-ID: Mandatory in OMA DCD and SFR.

– Application -ID: Mandatory in OMA DCD and SFR.

– Subscription-ID Conditional in OMA DCD and SFR (if issued upon subscription personalization).

– Channel-Metadata: General-channel-metadata are mandatory, delivery-preference-metadata are conditional. Relevant subset of the channel metadata defined in section 5.7.

Information Elements of the ChannelSubscriptionNotificationResponse message:

– Session-ID: Mandatory in OMA DCD and SFR.

– Message-ID: Mandatory in OMA DCD and SFR.

– Channel-Metadata (delivery-personalization-metadata): Mandatory in OMA DCD and SFR. The relevant subset of the delivery-personalization-metadata is defined in section 5.7.

Note: To perform the subscription, the client must be activated as specified in section 5.4.