A.2 Feed Discovery using the Syndicated Feed Reader

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

The SFR enabled Feed Reader may provide a build-in function to select and subscribe to syndicated feeds. The SFR enabled Feed Reader fetches the list of available feeds from the SFR server.

Figure A.2: Feed Discovery using the SFR enabled Feed Reader

1) The SFR enabled Feed Reader must have previously executed once the OMA DCD activation and registration procedures. The SFR enabled Feed Reader gets a list of available syndicated feeds in the ApplicationActivationResponse message.

2) The SFR enabled Feed Reader may send a request to update the list of syndicated feeds, when a user starts browsing the available syndicated feeds.

3) When the user finds a syndicated feed of interest, the SFR enabled Feed Reader sends the ChannelSubscriptionRequest message to the SFR server to initiate the optimized reception of the feed. The Content Address contains the URI of the syndicated feed.

The ChannelSubscription Response contains a Channel Metadata. If content update notification is delivered using OMA push, then the "dcd-interface" element in the channel metadata contains the value "DCD-2/Point-To-Point". Other channel metadata are defined for OMA DCD.

If content update notification is delivered using MBMS, then the "dcd-interface" element in the channel metadata contains the value "DCD-2/Broadcast". The "network-preferences" element shall contain the string "MBMS" in that case.

The SFR server has established a "Content update" relation with the desired syndicated feed server. In a scenario whereby the syndicated feed provider is not a "DCD Content Provider" and does not support the CPR interface and messages exchanged over the 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.