A.4 Feed Discovery using the PC browser
26.1503GPPProtocols and codecsRelease 17Syndicated Feed Reception (SFR) within 3GPP environmentsTS
This informative example assumes syndicated feed discovery through the PC browser (example external application). The example requires, that the SFR enabled Feed Reader has configured a "default" SFR server.
The user discovers a feed via other means (e.g. from a web portal) and provides the relevant information (i.e. a delivery context) to receive the feed on its SFR terminal. The feed is routed via the SFR server to which the terminal is connected. (For instance, if a phone number is identified as belonging to a particular mobile network operator the feed provider knows the SFR server of that carrier)
The figure bellow illustrates the flow for external subscription to an external feed and corresponds to DCD figure 9, flow 3 as described in [5].
Figure A.5: Feed Discovery using an external device
Upon reception of the some subscription notification from the web portal, the SFR server sends a ChannelSubscriptionNotification message to the SFR enabled Feed Reader via the DCD-3 interface as specified in section 7.1.3.9 of [5].
The SFR enabled Feed Reader processes this message and returns a ChannelSubscriptionNotificationResponse to the SFR server as specified in section 7.1.3.9 of [5].
1) The user uses a browser to find and subscribe to syndicated feeds on the service provider’s portal. Note: syndicated feed discovery using the PC browser is one realization of syndicated feed discovery and not in scope of this specification. The assumption is that the UE is configured with the SFR server associated with the service provider’s portal. The user provides as part of the subscription process some information allowing to identify the UE (e.g. MSISDN). Upon completion of the subscription process, the SFR server is provided with the feed address and the UE information.
2) The SFR server sends a ChannelSubscriptionNotification message to the UE as specified in section 7.1.3.9 of [5]. (e.g. this may be done via an SMS message) The user confirms the channel subscription and a ChannelSubscriptionNotificationResponse is sent from the UE to the SFR server as specified in section 7.1.3.9.1 of [5]
3) content updates are received.
Annex B (informative):
Change history
|
Change history |
|||||||
|
Date |
TSG # |
TSG Doc. |
CR |
Rev |
Subject/Comment |
Old |
New |
|
2009-12 |
46 |
SP-090713 |
Presented to TSG SA#46 for approval |
1.0.0 |
|||
|
2009-12 |
46 |
Approved at TSG SA#46 Plenary |
1.0.0 |
9.0.0 |
|||
|
2010-03 |
47 |
SP-100026 |
0001 |
1 |
Editorial Corrections to SFR Specification |
9.0.0 |
9.1.0 |
|
2011-03 |
51 |
Version for release 10 |
9.1.0 |
10.0.0 |
|||
|
2012-09 |
57 |
Version for release 11 |
10.0.0 |
11.0.0 |
|||
|
2014-09 |
65 |
Version for release 12 |
11.0.0 |
12.0.0 |
|||
|
2015-12 |
70 |
Version for release 13 |
12.0.0 |
13.0.0 |
|||
|
Change history |
|||||||
|
Date |
Meeting |
TDoc |
CR |
Rev |
Cat |
Subject/Comment |
New version |
|
2017-03 |
75 |
Version for Release 14 |
14.0.0 |
||||
|
2018-06 |
80 |
Version for Release 15 |
15.0.0 |
||||
|
2020-07 |
– |
– |
– |
– |
– |
Update to Rel-16 version (MCC) |
16.0.0 |
|
2022-04 |
– |
– |
– |
– |
– |
Update to Rel-17 version (MCC) |
17.0.0 |