13 Networked bookmark service

26.2343GPPProtocols and codecsRelease 17Transparent end-to-end Packet-switched Streaming Service (PSS)TS

13.1 Introduction

Bookmarking allows a PSS client receiving a stream from a PSS server to mark a point in time in the streamed content. The bookmark is either stored at a bookmarking server that is accessible via HTTP or at the PSS server that is accessible via RTSP. At a later time this bookmark is retrieved from the server and can be used for PSS session establishment.

Bookmarking at a bookmarking server accessible via HTTP is described in sub-clause 13.2. Bookmarking at the PSS server accessible via RTSP is described in sub-clause 13.3.

A registration to the bookmarking service may be necessary. Procedures for registration and providing the address of the bookmarking server are out of scope of this specification. The bookmarking service UserID is allocated uniquely during this registration process.

The bookmark is an XML-document that is formatted according to the XML schema provided in Annex T. The MIME type of the bookmark shall be "application/vnd.3gpp.bookmarking+xml".

13.2 Bookmarking using HTTP

13.2.1 Bookmark storage

After the user requests a bookmark, the PSS client sends a HTTP POST message together with the XML bookmark to the bookmarking server. The element "BookmarkList" is used for bookmark storage. At least the attributes UserID, the ContentURI and time are set. A bookmark is by default private but may optionally be made public, in which case it is accessible by all PSS clients.

After parsing the XML document and storing the bookmark, the bookmarking server sends back an HTTP 200 OK to the PSS client using the element "BookmarkListResponse". The bookmarking server optionally sets the attribute BookmarkID identifying individual bookmarks.

13.2.2 Bookmark retrieval

For bookmark retricval the PSS client sends an HTTP POST message together with the XML bookmark request to the bookmarking server. The element "BookmarkRequest" is used for bookmark retrieval.

After parsing the XML document, the bookmarking server sends back an HTTP 200 OK to the PSS client using the element "BookmarkResponse". If the attributes ContentURI and BookmarkID are set, the bookmarking server sends back the individual bookmark identified by the BookmarkID. If only the attributes UserID and ContentURI are set, all private bookmarks belonging to the ContentURI are returned. If only the attribute UserID is set, all private bookmarks belonging to the UserID are returned. In order to retrieve public bookmarks the Privacy attribute should be set to Public. If only ContentURI is set, then all public bookmarks for the corresponding content are retrieved.

13.2.3 Bookmark deletion

For bookmark deletion the the PSS client sends a HTTP POST message together with the XML bookmark to the bookmarking server. The element "BookmarkDeleteRequest" is used for bookmark deletion.

After parsing the XML document, deletion procedures are executed. If the attributes UserID, ContentURI and BookmarkID are set, the individual bookmark identified by the BookmarkID is deleted. If only the attributes UserID and ContentURI are set, all private bookmarks belonging to the ContentURI are deleted. If only the attribute UserID is set, all bookmarks belonging to the UserID are deleted.

After deletion, the bookmarking server sends back an HTTP 200 OK to the PSS client using the element "BookmarkDeleteResponse". The attribute BookmarkDeleted is set to true.

13.3 Bookmarking using RTSP

In case of bookmarking at the PSS server the RTSP method SET_PARAMETER is used. The body of the SET_PARAMETER requests and responses is formatted according to the XML Scheme defined in Annex T. The content type is set to "application/vnd.3gpp.bookmarking+xml".

A PSS server that does not support bookmarking, would reply with a 451 Parameter Not Understood. The PSS client that desires to use bookmarking with the PSS Server may check for support for the bookmarking feature in advance by including the "3gpp-bookmarking" feature tag as part of a "Supported" header field (as defined in sub-clause 5.5.2.2.2) in any of the preceding RTSP requests.

For bookmark storage, retrieval and deletion the XML bookmarking document is formatted in the same way as described in sub-clause 13.2.

Annex A (informative):
Protocols