[api] My Action Items 156 and 157 - Push and SSE

Hello,

I have completed my 2 action items 156 and 157. Here is the summary:


√ means: requirement (will be) covered

x means: requirement not covered but we think it should be

? means: we're not sure yet - more investigation/discussion needed
<blank> means Not Applicable


(1)    Requirement 1.3 Service Synchronization

-          Requirement: “There SHALL be a Service Synchronization mechanism between the device that interacts with a subscriber and the sources of local networked services, including the content in the services.”

-          It can be supported by both Push and SSE

-          Reason:

o   Push: whenever local networked service and its content are updated, they can send a Push notification to the device, and device can retrieve more details of the update from the source so as to synchronize.

o   SSE: device can set up an event source from the local networked service. Whenever the service and the content are updated, the source can send a message to the device to achieve the synchronization.

-          More investigation is needed to assess whether Push or SSE or another method is the best approach to achieve this requirement.


(2)    Requirement 1.9 Wake-up Mechanism

-          Requirement: “There SHALL be a Wake-up mechanism for the local network services to push a notification to the device and wake up a proper application to serve the subscriber.”

-          It MAY be supported by Push

o   It is self-explanatory that a push notification can be sent to the device. The device MAY wake up a proper application according to its pushRegistrationId.

§  Wake-up also depends on system support, i.e. the relation of the pushRegistrationId with the proper application

§  More investigation and discussion are needed for feasibility.

-          It can be supported by SSE

o   Device can set up an event source from the local networked service. The source can send a message as a push notification to the device in order to wake up a proper application.

-          More investigation is needed to assess whether Push or SSE is a better approach to achieve this requirement.


(3)    Requirement 1.10 Service Information on Push Notifications

-          Requirement: “The Push notification in the Wake-up mechanism SHALL carry all necessary information related to services and contents so that the appropriate application will be able to present the subscriber with content services WITHOUT extra handshaking steps.”

-          It CANNOT be supported by Push as of today, while we think it SHOULD.

o   Today’s Push only supports a new event without any data

o   Push should be enhanced to include data in the push notification

-          It can be supported by SSE

o   The message from event source to device can contain those necessary information.

-          More investigation is needed to assess whether Push or SSE is a better approach to achieve this requirement.


(4)    Requirement 1.12 Device-to-Device Content Transfer

-          Requirement: “There SHALL be a mechanism for content to be transferred among the devices, and between the device and original sources of local networked services.”

-          It can be supported by both Push and SSE

-          Reason:

o   Push: a device A can send a Push notification to another device B, and device B can retrieve the content from device A upon the notification.

o   SSE: device B can set up an event source from device A. Device A then can send a message to device B to transfer the content.

-          More investigation is needed to assess whether Push or SSE or another method is the best approach to achieve this requirement.

Others are all Not Applicable.

Let me know if there is any comment
Thanks

Bin Hu | Service Standards | AT&T