A.3 SFR Server Discovery triggered by Feed Discovery

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

The syndicated feed is served through a new SFR server. The terminal needs to discover the new SFR server or needs to be discovered as an SFR capable terminal by this new SFR server. It may also happen that the UE has no "default" SFR server configured.

The SFR enabled Feed Reader can activate and register to a new SFR server when the SFR feed URI contains the SFR server connection information as specified in section 5.3.2.2.

Figure A.3: SFR Server Discovery triggered by Feed Discovery

1) The user browses and discovers a feed URI. The browser pass the URI to the SFR enabled Feed Reader. The SFR enabled Feed Reader retrieves from the URI the SFR server parameters.

2) The SFR enabled Feed Reader uses the SFR server connection parameters to activate and further register to the SFR server and provide the feed URI to the SFR server. The SFR server establishes a content update relation with the feed server if not already in place.

3) Content updates are received.

Alternatively, the SFR enabled Feed Reader can be activated by a new SFR server as the SFR enabled Feed Reader provides its SFR UAProf capabilities when fetching the feed URI as specified in section 5.3.3.

Figure A.4: activation triggered by SFR Server

1) The terminal fetches a feed URI and provides its SFR UAprof parameters as part of the request. The web server forward these information to the SFR server. Alternatively, as per figure 5 in section 5.3.3, upon reception of the feed URI, the SFR enabled Feed Reader requests the feed to the SFR server and provides itq SFR capabilities as part of the UAprof information element.

2) The SFR server sends a request for activation notification to the SFR enabled Feed Reader (e.g. via SMS message).

3) Upon completion of the activation/registration process, content updates are received.