hash
stringlengths 32
32
| doc_id
stringlengths 7
13
| section
stringlengths 3
121
| content
stringlengths 0
3.82M
|
|---|---|---|---|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.7.2 Procedures for N-PVR Session
|
The UE follows procedures outlined in clause 5.1.4 for COD to stream a previously captured N-PVR content. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 48 The user part of the "Request-URI" parameter shall contain the NPVRContentId retrieved from the SSF as defined in clause 6.1.1.5 and shall correspond to the content that was captured via impulsive or offline request. The UE shall build the SDP offer as defined in clause 5.1.4.2 for CoD session initiation and shall include media control line for RTSP control channel. The SDP offer for the media delivery lines shall specify the transport and codec parameters for the corresponding BC ServiceId.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.7.3 Procedures for C-PVR Recording Session
|
The UE shall then extract the parameters from the received MESSAGE message body and verify the "NotificationReason" is "CPVRRecord". The UE extracts further sub-elements message body of the "CPVRRecordInfo" element, as follows: • The "CPVRContentID" element in the message body indicates the identifier of the C-PVR content, may be used as an index for user. • The "BCServiceId" element in the message body indicates the BC service that required to be recorded, UE shall initiate a C-PVR recording session which is similar to the procedures described in clause 5.1.3.1 to join the BCServiceId immediately and record the media content. The UE shall correlate the "BCServiceId" with the one from the service selection. • The "RecordEndDate" element in the message body indicates the BC service that required to be recorded, UE shall initiate the end date (and time) of the recording, the UE shall set a timer to terminate the C-PVR recording session.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.8 Procedure for UGC Service
| |
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.8.1 Procedure for UGC declaration
|
In the case of procedure for declaring user generated content, the UE shall send a SIP MESSAGE request to SCF for retrieving UGC contentID. The contents of the SIP MESSAGE request shall be as follows: • The Request-URI in the MESSAGE request shall be the well known PSI (Public Service Identifier) of the UGC Service. • From and To headers shall be set to the public identity of the user issuing the MESSAGE request. • Call-ID shall be generated by UE. • CSeq shall be generated by UE. • The Content-type header shall include the MIME type of XML documents representing IPTV service action data: "application/vnd.etsi.iptvsad-ugc+xml". • The message body of MESSAGE request carries the transaction-id, which should match "UGC items" specified in annex K. The transaction-id is used to identify a UGC declaration transaction, it is a string that is generated and only recognized by the UE, and it is carried in the declaration request from the UE and the declaration response from the SCF, and the "transaction-id" is not used in the following request response, and the "UGCContentId"can be used to correlate the request and response. The transaction-id is unique on the UE and there should be some mechanism for UE to populate the unique transaction-id. Time-stamp based transaction-id generation may be seen as an option, which is out of scope of the present document. Upon reception of the MESSAGE request from SCF including UGC contentID, the UE shall extract UGC contentID and the transaction-id from the message body. A SIP 200 OK response without message body shall be sent back to the SCF immediately after the MESSAGE request is successfully received by the UE. The UE then uses the transaction-id to correlate the UGC declaration request and enforce the subsequent actions, e.g. save the UGC contentID in local disk. Transaction Id is only valid until the response is received. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 49
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.8.2 Procedure for publishing UGC description information by UE
|
The procedure is similar to the procedure outlined in clause 5.1.8.1 for declaring user generated content, with the following difference: • The message body of MESSAGE request carries both the UGC contentID and UGC description information, which should match "UGC items" specified in annex K. This procedure may be combined with the UGC declaration procedures in clause 5.1.8.1. 5.1.8.3 Procedure for UGC creation
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.8.3.1 Session initiation
|
The UE shall support the procedures specified in ES 283 003 [20] for originating sessions. Upon request for a UGC creation session initiation, the UE shall generate an initial INVITE request as specified in ES 283 003 [20] for an originating UE. • The "Request-URI" shall be the well known PSI (Public Service Identifier) of the UGC Service. • The From header shall indicate the public user identity of the user. • The To header shall contain the UGC contentID generated in UGC declaration. • Call-ID shall be generated by UE. • CSeq shall be generated by UE. NOTE 1: The UGC contentID is retrieved from the MESSAGE request sent from SCF in response to the UGC declaration request. An SDP Offer shall be included in the request. The SDP Offer shall be done in accordance with the media capabilities and required bandwidth available for the UGC creating session. The SDP Offer at media level shall include the following elements: • The "m=" line indicates the type of the media, the transport protocol and the port of the related content delivery channel. • The "c=" line shall include the network type with the value set to IN, the address type set to IP4 or IP6 and unicast address of the flow of the related content delivery channel, (ex. c=IN IP4 <IP_ADDRESS>). • The "b=" line shall contain the appropriate bandwidth value that the generating UE supports. Since the UGC media stream is unidirectional the bandwidth shall be set to 0, except for the case that the transport is RTSP, RTP and RTCP is allowed. • For HTTP upload the transfer type may be indicated in the "fmtp:iptv_http_transfer" type attribute. The values that are applicable are "progressive" and "streaming". - The "progressive" upload is content in the UE that is fully available for upload and has no restrictions to the rate of upload. - The "streaming" or HTTP streaming is content in the UE that has a restricted rate of upload, for example content that is being recorded. - Other values may be used with a "x-" extension to indicate other proprietary type of downloads. EXAMPLE: a=fmtp:iptv_http transfer-type＝<transfer-type>). An "a=" line with a "sendonly" attribute (ex. a=sendonly). ETSI ETSI TS 183 063 V3.6.1 (2014-08) 50 NOTE 2: Procedures for publishing UGC description in clause 5.1.8.1 and UGC declaration procedures in clause 5.1.8.2 may also be embedded in the above UGC creation procedures. The UE may use the bandwidth and if present the transfer-type attributes in the SDP answer from the session initiation response to shape the rate of the content upload. The transmission of HTTP content upload is a best effort type of transmission. The speed at which content is transmitted with HTTP is limited by the available bandwidth. No prioritization is performed on the transmission of upload. If differentiation is required for HTTP content upload the attribute "transfer-type" SHALL be supported. The inclusion of the attribute "transfer-type" indicates to IMS and local transport policies in RACS that a session with special requirements shall be setup. For example HTTP streaming shall be set up with the bandwidth included in the SDP is the maximum guaranteed bandwidth for transmission.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.8.4 Procedure for UGC watching session
| |
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.8.4.1 UGC selection
|
The UE can select UGC content based on several methods: • Selection through the SSF, see clause 6.1.1 • Content recommendation • Notification, see clause 5.1.9 • Pre-selection, see below When a UE wants to pre-select UGC content that had already been declared and published but not yet created, it shall send a SIP MESSAGE request to the SCF. The contents of the SIP MESSAGE request shall be as follows: • The Request-URI shall be the well known PSI (Public Service Identifier) of the UGC Service. • From and To headers shall be set to the public identity of the user issuing the MESSAGE request. • Call-ID shall be generated by UE. • CSeq shall be generated by UE. • The Content-type header shall include the MIME type of XML documents representing IPTV service action data: "application/vnd.etsi.iptvsad-ugc+xml". NOTE: The XML schema corresponding to the MIME type "application/vnd.etsi.iptvsad-ugc+xml" is available in annex K of the present document. • The message body contains the contentID of the UGC content the UE wants to pre-select Upon receiving the SIP 200 OK answer from the SCF the UE stores the contentID of the pre-selected UGC.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.8.4.2 Session initiation
|
UE-initiated: When the UE selects UGC through the SSF, content recommendation, or notification it shall perform UE- initiated session initiation as described in clause 5.1.4.2 for CoD. SCF-initiated: Upon receiving an incoming INVITE the UE shall inspect the From header. If the From header includes contentID which corresponds to the stored contented of pre-selected content, the UE shall accept the SCF-initiated session initiation as described in clause 5.1.4.2A for CoD. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 51
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.9 Notification service
| |
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.9.1 Procedure for Notification service using signalling path
|
Upon reception of a SIP MESSAGE request, the UE shall check the Content-type header indicating "application/vnd.etsi.iptvnotification+xml" to verify the notification message. The UE shall parse the XML document defined in annex S. After all elements have been processed, the UE may present the received notification to the user and take the appropriate further actions.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.10 Procedure for Remote Service Initiation
| |
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.10.1 Procedure for service initiation by remote UE
|
When the Remote UE wants to initiate an IPTV service on the Target UE, the Remote UE shall send a SIP REFER request to Target UE, and the REFER message is routed to SCF by IFC. The contents of the SIP REFER request shall be as follows: • The Request-URI in the REFER request shall be set to the public GRUU or to the registered IMPU of the Target UE with the Accept-Contact header set to the SIP instance feature tag defined in clause 5.6.3 of the Target UE. • From header should be set to the public identity of the user issuing the REFER request. • To header should be set to the public GRUU or the IMPU of the Target UE. • Call-ID shall be generated by the Remote UE. • CSeq shall be generated by Remote UE. • Refer-To shall include the following parameters: - the SIP URI should be set to the PSI of the service to be activated on the Target UE; - the "method" shall be set to appropriate values according to different service, such as "INVITE" for BC, Cod; "MESSAGE" for UGC. When the Remote UE receive the NOTIFY message, the remote UE should send a SIP 200 OK to the originating UE.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.10.2 Procedure for service initiation on the Target UE
|
When receiving a SIP REFER request, the Target UE shall check whether or not it is capable of initiating the indicated IPTV session, e.g. Refer-To header to extract the Request-URI should start service request as the "Refer-To" message header of the REFER. If the Target UE is capable of initiating the service, the Target UE shall send a SIP 200 OK Message immediately. And the SIP 200 OK Message should be the same to the REFER request received before except the "contact" head field: • Contact shall be set to the GRUU of the Target UE. Then the Target UE should send an immediate NOTIFY message to remote UE for informing the agent sending the REFER of the status of the reference which shall be set as follows: • From header shall be set to the public GRUU of the Target UE. • To header shall be set to public identity of the user issuing the REFER request. • Call-ID shall be same to the REFER message received before. • CSeq shall be same to the REFER message received before. • Content-Type shall be set to "message/sipfrag". ETSI ETSI TS 183 063 V3.6.1 (2014-08) 52 • Event shall be set to "refer". • Subscription-State shall be set to "active". When the Target UE have sent the NOTIFY message, it should initiate the service according to the "Refer-To" message header of the REFER. After completion of the service initiation, it should send another NOTIFY message to remote UE, and the "Subscription-State" of such NOTIFY message should be set to "terminated" which is different from previous NOTIFY message.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.11 Procedure for Personalized Service Composition
| |
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.11.1 General
|
The Personalized Service Composition (PSC) service composes multiple BC and or CoD sessions into a PSC session. The PSCid is used to correlate the different BC/CoD sessions of the PSC, associating these BC/CoD sessions with each other within the PSC session, which is identified by the PSCid.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.11.2 Generation of the PSCid by the UE
|
The UE retrieves available services from SSF and composes a Personalized Service Composition (PSC). The PSC is to be composed of multiple BC and/or CoD services. The UE generates a PSCid and makes a record of it. The PSCid should be globally unique.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.11.3 UE-initiated session initiation
|
For all UE-initiated sessions in the PSC, the UE shall include the PSCid in the SDP offer in the initial INVITE request to the SCF. • An "a=PSCid:<PSCid>" line indicates the PSCid. The UE shall correlate the session with the PSCid. UE-initiated BC session initiation is specified in clause 5.1.3.1. UE-initiated CoD session initiation is specified in clause 5.1.4.2. Other types of IPTV sessions may also be used in a PSC, including an "empty" session that is used only to convey the PSCid.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.11.4 SCF-initiated session initiation
|
A UE is able to receive an initial invite request from the SCF following the SCF-initiated session initiation procedures specified in clauses 5.1.3.1A and 5.1.4.2A. When a UE receives an initial INVITE request from the SCF containing a PSCid, it shall check whether it already has a record of the indicated PSCid. • If it does, then the UE shall correlate the session with the PSCid. • If it does not, then the UE shall make a record of the PSCid and correlate the session with the PSCid.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.11.5 Session modification
|
Sessions within a PSC can be modified using normal session modification procedures, see e.g. clause 5.1.3.2. For UE- initiated modification of a session within a PSC, the UE shall include the PSCid in the SIP re-INVITE request or UPDATE request, depending on the dialogue state. • An "a=PSCid:<PSCid>" line indicates the PSCid The value of the PSCid may be different than in the original INVITE request, which indicates that the session is transferred to another PSC. The value of the PSCid may also be empty, which indicates that the session is removed from the PSC. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 53 For an SCF-initiated session modification, the UE shall check the PSCid in the received re-INVITE request or UPDATE request. If the PSCid is different from the original PSCid for this session, this indicates that the session is transferred to another PSC. If the value of the PSCid is empty, this indicates that the session is removed from the PSC.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.11.6 Session termination
|
Sessions within a PSC are terminated using normal session termination procedures, see e.g. clauses 5.3.1.4 and 5.3.2.4. When a session within a PSC is terminated, then the UE shall remove the correlation between that session and the PSCid. When the last session within a PSC is terminated, then the UE shall delete the record of the PSCid.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.12 Procedure for Personalized Channel (PCh) Service
| |
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.12.1 Procedure for PCh Declaration
|
For declaring a Personalized Channel (PCh), the UE shall send a SIP MESSAGE request to SCF for retrieving PChId. The contents of the SIP MESSAGE request shall be as follows: • The Request-URI in the MESSAGE request shall be the well known PSI (Public Service Identifier) of the PCh Service. • From and To headers shall be set to the public identity of the user issuing the MESSAGE request. • Call-ID shall be generated by UE. • CSeq shall be generated by UE. • The Content-type header shall include the MIME type of XML documents representing IPTV service action data: "application/vnd.etsi.iptvsad-pch+xml" (see annex K). • The message body carries one "IPTVPChActionData" element which only includes a unique "transaction-id" attribute that is generated by the UE. • If the UE wants to avoid forking in case the user is registered with the same IMPU from several devices, the UE should include the contact header and should include there in a public GRUU, a temporary GRUU or the sip instance feature tag. The transaction-id is used to identify a declaration transaction. It is a string that is generated and only recognized by the UE, and it is carried in the declaration request from the UE and the declaration response from the SCF, and the "transaction-id" is not used in the following request response, and the PChID can be used to correlate the request and response. The transaction-id is unique on the UE and there should be some mechanisms for UE to populate the unique transaction-id. Time-stamp based transaction-id generation may be seen as an option, which is out of scope of the present document. A SIP 200 OK response without message body shall be sent back to the SCF immediately after the MESSAGE request is successfully received by the UE. Upon reception of the MESSAGE request from SCF including PChId, the UE shall extract PChId from the message body. Transaction Id is only valid until the response is received.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.12.2 Procedure for PCh Operation
| |
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.12.2.1 PCh Session Initiation
|
For the PCh MF option, the PCh session initiation is similar with the CoD session initiation as described in clause 5.1.4.2, with the following differences: • The "Request-URI" in the INVITE request shall be set to the PChId generated in PCh declaration procedure. • The To header in the INVITE request shall contain the same PChId as in the "Request-URI" parameter. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 54
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.12.2.2 Session modification due to a PCh Content Item Switch
|
Upon receipt of a re-INVITE request or an UPDATE request, the UE shall modify the session as specified in procedure for CoD service of clause 5.1.4.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.12.2.3 PCh Overlap Handling through User interaction
|
On reception of SIP INFO request, that includes the PCh-Overlap-Handling Info Package in accordance with the SIP INFO framework, the UE shall examine the Call-ID header and the Content-type header which is "application/vnd.etsi.iptvsad-pch-overlap+xml" to identify the PCh conflict option request. The UE extracts the options from the message body, and selects one option according to the user choice and the UE capabilities (e.g. capability for C-PVR) . Following successful processing of the SIP INFO request, the UE shall send back a SIP 200 OK response to the sender. Then the UE shall send another SIP INFO request back to the SCF including the PCh-Overlap-Handling representing the choice result, as follows: • The Request-URI, To header, Call-ID shall be set identical to those present in the PCh session initiation procedure. • The CSeq shall be generated by the UE. • The Content-type shall be set to "application/vnd.etsi.iptvsad-pch-overlap+xml" which representing the PCh conflict choice data (see annex U). • The message body shall include the selected option that handles the PCh overlap. Note that it is assumed that both the UE and the SCF indicated their willingness to receive the PCh-Overlap-Handling Info Package.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.13 Procedure for Content Insertion at UE Side
|
Content insertion at the UE side is a generic capability that allows for inserting content. Content insertion is triggered by user input at the UE side or event detection by the UE or SCF. Annex A.6 provides example signalling flows for the case where the SCF detects an event and for the case where a user pauses a CoD stream. For the purpose of content insertion, the UE shall recieve a SIP INFO request including the Event-Notification Info Package (defined in clause ZA.4) according to the SIP INFO framework with Content-type set to "application/vnd.etsi.iptvnotification+xml". The UE shall then extract the parameters from the body in the received SIP INFO request and verify the "NotificationReason" is "ContentInsertion". Following successful processing of the SIP INFO request, the UE shall send back a SIP 200 OK response to the sender. The UE checks the local device for the support of content insertion and extracts further sub-elements message body of the "ContentInsertionInfo" element, as follows: • The "ContentInsertionReason" element in the message body describes the reason for ContentInsertion. The currently specified types are "Advertising", "PausedContent", "Generic". NOTE 1: The UE can handle the content insertion appropriately based on the reason for the insertion. The decision logic, as well as any configuration by the network, is operator-dependent and out of scope of the present document. Additionally, the UE may reject the insertion based on criteria such as local resource availability, bandwidth availability etc. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 55 • The "ContentInsertionTime" element contains two sub-elements: - The "ContentInsertionStartTime" element in the message body indicates the content start time. If it is earlier than the present clock, the UE shall ignore the SIP INFO request as if it is sent in error. If it is later than the present clock, the UE shall set up a timer to wait for the triggering of content insertion handling. If the body does not carry a "ContentInsertionStartTime" element, or the timer for the content insertion triggering is up, the UE shall perform the content insertion immediately: - The "ContentInsertionDuration" element in the message body indicates the duration of content insertion. • If the message body carries a PSCid according to clause 5.1.11, the PSCid is associated with the ongoing BC/CoD session and it is used to associate this session with the new session for content insertion. • If the message body carries a "MulticastContent" element, the UE shall initiate an INVITE request as described in clause 5.1.3.1, where the first BCServiceID that the UE tends to join shall be set to the one extracted from the "MulticastContent" element: - The SDP offer includes the PSCid according to clause 5.1.11.3 if available. This results in a PSC session composed of the ongoing BC/CoD session and the new multicast session for content insertion. • If the message body carries a "UnicastContent" element, the UE shall initiate an INVITE request as described in clause 5.1.4.2, where the Request-URI in the request shall include the one extracted from the "UnicastContent" element: - The SDP offer includes the PSCid according to clause 5.1.11.3 if available. This results in a PSC session composed of the ongoing BC/CoD session and the new unicast session for content insertion. NOTE 2: Since the PSCid is known by both the UE and the SCF, it allows for specific UE and/or network behaviour in case of associated sessions within a Personalized Service Composition. For example in case of advertisement the inserted content has reduced trick-play capabilities, or for example the SCF may pre- reserve and allocate sufficent additional bandwidth for the new content insertion session. • The SIP INVITE request initiated by the UE shall be constructed according to the procedures for BC service in clause 5.1.3 for multicast content insertion and the procedures for CoD service in clause 5.1.4 for unicast content insertion. After the new session has been established, the UE may use SIP INFO to update the content insertion SAD information. For example, in the cases when the content insertion is rejected, or has begun, ended, failed etc, the UE shall send SIP INFO to the SCF reporting the insertion status, with the InsertionStatus element set to "Rejected", "Started", "Finished" and "Failed" respectively. The Service Action Data information (see annex K) shall be populated as follows: • IPTVActionDataCommand shall be set to "Notify". • Notify shall be set to "IPTVContentInsertionActionData". • "IPTVContentIdentifer" shall be set to the content identifier of on-going session, e.g. the BC service id, the CoD content identifier etc. • "InsertedContentIdentifer" shall be set to the content identifier of the content that is inserted to the on-going session. • The "InsertionStatus" element shall be present and set to "Accepted". The Content-Type Header of the SIP INFO message shall be set to "application/vnd.etsi.iptvcommand+xml". Note that the UE shall have indicated its willingness to receive the Event-Notification Info Package.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.14 Procedures for IPTV Content Marker Service
| |
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.14.1 Procedure for IPTV Content Marker handling
|
The IPTV Content Marker handling procedure applies to storing, updating and removing IPTV Content Markers. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 56 For storing and/or updating the IPTV Content Marker, the UE shall, within an existing SIP dialog with the SCF, send a SIP INFO request that includes the IPTV-Content-Marker Info Package (defined in clause ZA.3) according to the SIP INFO framework, or send a SIP MESSAGE request to the SCF if there is no ongoing SIP dialog with the SCF. The contents of the SIP INFO/SIP MESSAGE request shall be as follows: • The value of the Request-URI shall be set to the one used in the related session, where applicable. • From and To headers shall be set to the one defined during the session initiation procedure. • Call-ID shall be set to the same value as that of the CoD session. • CSeq shall be generated by the UE following rules defined in ES 283 003[20] for request within a dialog. The Content-type header shall include the registered MIME type of XML documents representing IPTV Content Marker data: "application/vnd.etsi.iptvcontentmarker+xml". The message body carries data of IPTV Content Marker. The content of SIP INFO/SIP MESSAGE request shall be follows: - IPTVInformationDataCommand shall be set to "Update". - IPTVContentMarkerID is not set when the user wants to register IPTV Content Marker. If the user wants to update IPTV Content Marker data, IPTVContentMarkerID shall be set the value of targeted IPTV Content Marker. - OwnerUserID shall be set to IMPU. - IPTV service type identifier shall be set to the value of IPTV service type this IPTV Content Marker refers When the user updates IPTV Content Marker data, this value should not be changed. - IPTV content identifier shall be set to the value of IPTV content identifier. When the user updates IPTV Content Marker data, this value should not be changed. - ForbiddenViewUser is optionally set to IMPUs of specific users with whom the owner of this IPTV Content Marker does not want to share this particular IPTV Content Marker. - StartTimeOfIPTVContentMarker is optionally set to the timestamp value the UE indicates. - EndTimeOfIPTVContentMarker is optionally set to the timestamp value the UE indicates. - UserComment is optionally set to string value of comment the user notes. - GenerationTime is optinally set to the timestamp value of creating IPTV Content Marker. This value is generated by the SCF. - ExpiryTime is optionally set to the timestamp value IPTV Content Marker expires. To delete an existing IPTV Content Marker, the UE shall set this value to -1. - Tag: Represents any categorization chosen by the user. - Rank: Represents the user favorite rating for the content marker. - Retrieval count: SHALL be set to 0 and incremented by the service provider when the content marker is retrieved. This value is set by the SCF. - Retrieval Time SHALL be updated with a new entry every time the content bookmark is retrieved (note that retrieval does not imply the content bookmark is used). This value is set by the SCF. Updating and removing of content markers may also occur outside an existing session and if so than XCAP should be used for that purpose if the information is stored in the user profile. NOTE: Ranking and tagging procedures are considered out of scope (as UE intern procedures). ETSI ETSI TS 183 063 V3.6.1 (2014-08) 57
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.15 Procedure for Targeted Ad Insertion (TAI)
| |
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.15.1 TAI at UE side
|
In the case when service state detection happens at the SCF as described in clause 5.3.14.1, the UE shall use procedure for content insertion at UE side described in clauses 5.1.13 for TAI at UE side. The following attributes in the content insertion data are used as following: • The "ContentInsertionStartTime" indicates the ad insertion start time, the handling of the processing of "ContentInsertionStartTime" is same with the handling of the content insertion. • The "ContentInsertionEndTime" element indicates the ad insertion end time. • The "MulticastContent " element, it indicates multicast ad insertion, and the "UnicastAd" element indicates unicast AD insertion, the UE shall initiate an INVITE request according to the handling of content. The response of the request and the following session initiation of the inserted ad is the same with the procedures described in the content insertion procedures.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.15.2 TAI at MF side
|
NOTE: There are no additional procedures needed for the TAI at MF side. 5.1.16 Procedures for Content Switch within a CoD Contentlist(User- Owned) CoD content lists are lists.that are typically owned by a user and are under user control when it comes to content switching. The assumption in this case, is that all of the contents within one CoD contentlist shall share the same content delivery description information (e.g. the same QoS requirement), so that session modification procedures are not needed when users switch content within the contentlist. Note that the user is able to perform trickmodes on any content in the list.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.16.1 UE-initiated session Session initiation
|
The session initiation is similar with the CoD session initiation as described in clause 5.1.4.2, with the following differences: • The "Request-URI" in the INVITE request shall be set to the Content identifier fetched from the service discovery procedures. • An "a=fmtp:3gpp_rtsp h-Supported" attribute shall be present and set as "3gpp-switch", under the "m" line for RTSP stream which is defined in annex A of [51]. When the UE receives the SIP 200 OK response from MF, the UE shall examine that an "a=fmtp:3gpp_rtsp h- Supported" attribute is present and set as "3gpp-switch" under the "m" line for RTSP stream. The UE then extracts the contentlist information from the XML message body and stores it. The UE may present the received contentlist information, e.g. "ContentItemName" to the user and take the appropriate further actions. NOTE: The MF represents a combination of the MCF & MDF. In this context the MCF functionality is expected to be used.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.17 Procedures with other IMS Services
| |
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.17.1 Instant Messaging Procedures
|
When the UE supports OMA Instant Messaging according to [21] the UE shall follow the following procedures. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 58 When UE supports messaging using these procedures the SIP REGISTER Contact header shall include the OMA Instant Messaging feature tag '+g.oma.sip-im' according to [50] and an IPTV IMS Application Reference Identifier (IARI) URN media feature tag "urn:urn-xxx:3gpp-application.ims.iari.iptv-application" according to [21]. Example of the feature tag: g.3gpp.iari-ref="urn%3Aurn-xxx%3A3gpp-application.ims.iari.iptv-application" Upon reception of a SIP MESSAGE with an Accept-Contact header with Instant Messaging feature tag '+g.oma.sip-im' and IARI media feature tag 'urn:urn-xxx:3gpp-application.ims.iari.iptv-application' the UE shall handle the body as an IPTV related IPTV message. This allows the UE to screen regular SIP MESSAGE not coming from the SCF, e.g. in order to exhibit IPTV-specific behaviour. The body may include information relating to IPTV (for example TV program reminder/subscription set by the user). NOTE: If information related to IPTV is included in the message, this mechanism serves as an alternative to the procedure in clause 5.3.6; it is intended to be used if different types of IMS devices are targeted, among which non-IPTV devices. Upon successful reception of the request the UE responds with a SIP 200 OK response.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.18 Procedures for Unicast Content Download
| |
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.18.1 UE-initiated Content download session initiation for unicast download
|
The UE shall support the procedures specified in ES 283 003 [20] for originating sessions. Upon a request for a content download session initiation, the UE shall generate an initial INVITE request as specified in ES 283 003 [20] for an originating UE, and specifically: • the Request-URI shall contain the download content URI as CDS XML unicast locator described in TS 102 034 [3] clause 10.3.2.2; • the TO header shall contain the download content URI; • the content identifier shall be retrieved from service selection information (see annex L concerning the mapping between service selection information and SIP/SDP parameters); • the FROM header shall indicate the public user identity of the user; • an SDP Offer shall be included in the request. The SDP Offer shall be done in accordance with the media capabilities and required bandwidth available for the content download session; • the SDP Offer at media level shall include the following elements: - an "m" line for an HTTP download of format: m=<media> <port> <transport> <fmt>: the media field shall have a value of "application"; the port field shall be set to a value of 9, which is the discard port; the transport field shall be set to TCP; the fmt parameter shall be included and shall be set to iptv_http (ex. m=application 9 tcp iptv_http). - an "a=setup" attribute shall be present and set to "active" as defined in ES 283 003 [20] (ex. a=setup:active); - an "a= connection" attribute shall be present and set as "new" as defined in ES 283 003 [20] (ex. a=connection:new); - a "c" line shall include the network type with the value set to IN, the address type set to IP4 or IP6 and IP address of the flow of the related HTTP channel (ex. c=IN IP4 <IP_ADDRESS>); ETSI ETSI TS 183 063 V3.6.1 (2014-08) 59 - optionally, the "b=" line may contain the proposed bandwidth. If the user has fetched the bandwidth required for this particular content delivery channel during service selection procedure, the bandwidth attribute at media level shall be set to this value (ex. b=AS:15000); - the type of content download may be indicated in the "fmtp:iptv_http transfer-type" attribute. The values that are applicable are "progressive" and "streaming": The "progressive" download is content that is viewed as download is stored or buffered in the UE. The "streaming" or HTTP streaming is content that is viewed without storing or very limited buffering in the UE similar to RTSP streaming. Other values may be used with a "x-" extension to indicated other proprietary type of downloads. (ex. a=fmtp:iptv_http transfer-type＝<transfer-type>). The transmission of HTTP content download is a best effort type of transmission. The speed at which content is transmitted with HTTP is limited by the available bandwidth. No prioritization is performed on the transmission of download. If differentiation is required for HTTP download the attribute "transfer-type" SHALL be supported. The inclusion of the attribute "transfer-type" indicates to IMS and local transport policies in RACS that a session with special requirements shall be setup. For example HTTP streaming shall be set up with the bandwidth included in the SDP is the maximum guaranteed bandwidth for transmission.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.18.2 UE-initiated Content download session initiation for multicast download
|
NOTE: The details about acquiring and initiating multicast download have to be contributed and are not specified in this release The procedures need to conform to CDS in TS 102 034 [3] and will be similar to the procedures for unicast download (clause 5.1.18.1) and will be contributed for this clause.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.19 Procedure for Preview Service
| |
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.19.1 Procedures for BC preview session
| |
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.19.1.1 Session initiation
|
The BC content preview procedures may take place in the following cases: 1) Single-screen BC preview: Preview a specific BC program before the users decide to pay for it. 2) Multi-screen BC preview: Preview the BC services where the preview content is provided through a multi- screen mode (e.g. PiP, Mosaic). The BC preview session initiation shall use the BC session initiation procedures described in clause 5.1.3.1. The use of single-screen and/or multi-screen BC preview is independent of number of sessions and m-lines that are required. The UE can either establish a single BC session with the SDP carrying multiple m-line(s) including all the BC service identifiers of the BC channels that the UE intends to preview, or the UE can initiate independent sessions for each BC channel that the UE intends to preview. NOTE: For the BC preview service, regular BC content and preview BC content can use different BC service identifiers.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.19.2 Procedures for CoD preview session
| |
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.19.2.1 Session initiation
|
For preview content having its own content identifier, the preview procedures refer to procedures specified in clause 5.1.4.2. When the UE intends to terminate the CoD session, the procedure in clause 5.1.4.4 can be used. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 60
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.20 Procedure for Session Transfer
| |
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.20.1 Generic Procedure
|
These procedures are generic to all session transfer modes. For all modes the transferee UE initiates the new session that replaces the transferred session.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.20.1.1 Transferee UE session initiation
|
The transferee UE shall generate an initial INVITE using the same procedure in clause 5.1.4.2 with the following qualifications: • A new SIP header Replace header is included and is set to the information retrieved from the incoming REFER as per clause 5.1.20.2.3 Transferee UE Handling for Incoming Session Transfer Request. • For the push mode of session transfer, the domain part in the "Request-URI" is set to the field extracted from the To header embedded in the Refer-To header in the incoming REFER received by the transferee UE. • Finally, the SDP composition is based on the information extracted from the body header in the Refer-To header in the incoming SIP REFER.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.20.2 Session Transfer - Push Mode
| |
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.20.2.1 Transferor UE Locating a Transferee
|
To identify a transferee UE for a session, the transferor shall subscribe to the Registration-event package for the public user identity of the user as specified in ES 283 003 [20]. The transferor UE shall then locate an appropriate UE from the returned information and initiate a session transfer request to it according to clause 5.1.20.2.2.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.20.2.2 Transferor UE Initiation of Session Transfer Request
|
The transferor UE shall generate a REFER request to the transferee UE identified in clause 5.1.20.2.1. The transferor UE shall follow the procedures in TS 124 237 [58], clause 15 entitled "15 Roles for inter-UE transfer without establishment of collaborative session". In particular, the Request URI in the REFER request shall be set to the target device contact information derived from information returned in clause 5.1.20.2.1. The tranferor shall include in the contact header field a public GRUU or a temporary GRUU. The Refer-To header in the REFER request shall be set to the remote target URI included in the contact header field returned in the SIP 200 OK associated with initial session CoD setup by the transferor. Additionally, the Refer-To shall be extended with the following URI headers fields: • Replaces header field SHALL include the SIP dialog identifier for the original CoD session as per RFC 3891 [70]. • Require header field populated with the option tag value "replaces". • To header field includes the original content identifier copied from the Request URI of the original SIP INVITE request initiated from the transferor. • Optionally an Accept-Contact header field with the g.3gpp.icsi-ref media feature tag set to the IPTV Communication service identifier "urn%3Aurn-7%3A3gpp-service.ims.icsi.iptv". • P-preferred-Service set to IPTV Communication service Identifier urn:urn-7:3gpp-service.ims.icsi.iptv. • Body header. This contains the SDP body to be included in the CoD request initiated from the transferee UE. The SDP body shall contain the same number of media lines as the SDP used in the original CoD session from the transferor UE. Each media line shall indicate the same media type as its corresponding media component in the SDP used in the original session by the transferor UE. The body of the REFER request shall include the IPTV Content Marker for the original CoD session. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 61 Upon receipt of a SIP 200 OK, the transferor UE shall wait for the outcome of the transfer request. Upon receipt of a SIP UPDATE or SIP re-INVITE on the old session, instructing the UE that the media is on hold (port set to 0), the transferor shall abstain for performing any RTSP transactions on the old session. Upon receipt of a SIP NOTIFY request, indicating the success of the session transfer request, the transferor UE returns a SIP 200 OK final response. The transferor UE shall receive a SIP BYE request to terminate the CoD session to which the transferor UE returns a SIP 200 OK. This completes the successful transfer of the session.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.1.20.2.3 Transferee UE Handling for Incoming Session Transfer Request
|
Upon receipt by a UE for a SIP REFER request that indicates a session transfer, and if the transferee UE accepts the incoming SIP REFER, after validating the SIP REFER request, a SIP 200 OK request is returned as a response. The transferee UE extracts the following information from the incoming SIP REFER request: • The Content URI extracted from the To header included in the Refer-To header. • The body header to use as the SDP for initiating a session. • The Dialog ID to be replaced, extracted from the Replace header, in the Refer-To header. • The IPTV Content Marker from the SIP REFER body. Subsequently, the transferee UE initiates a new CoD session as per clause 5.1.20.2.1. Once the session is successfully established, the transferee initiates a SIP NOTIFY towards the transferor UE. Upon receipt of SIP 200 OK response, the transferee UE stores the relevant information and is now ready to start trick- play mode for viewing the content.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.2 Service Discovery Function (SDF)
| |
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.2.1 Procedure for IMS registration
|
If delivery of service discovery information using push mode is supported, the SDF acts as a third-party registrar and receive REGISTER requests from the Core-IMS during the IMS registration phase. The SDF shall store the public user identity of the user as received in the To header and use it to initiate delivery of service discovery information in push mode towards this user. The SDF shall answer to the REGISTER request with a SIP 200 OK response as specified in ES 283 003 [20]. If delivery of service discovery information in push mode is not used, the SDF shall send a 501 error response to the Core-IMS.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.2.2 Procedure for service attachment
| |
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.2.2.1 Push mode
|
In the push mode, after the regular third-party registration, the SDF shall generate a SIP MESSAGE to the UE, and the service attachment information is taken in the message body of the SIP MESSAGE. The SDF uses the SIP MESSAGE to transport the service attachment information, and the SDF shall generate a SIP MESSAGE request in accordance with ES 283 003 [20] and TS 124 229 [24] as used in ES 283 003 [20]. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 62 The contents of the SIP method request shall be as follows: • The Request-URI of the SIP MESSAGE request shall be set to the public user identity of the intended recipient. • The From head shall be set to the SIP URI of the SDF. • The To head shall be set to the public user identity of the intended recipient. • The content type shall be set to "application/vnd.etsi.iptvdiscovery+xml". • The message body shall conform to the XML schema described in annex M and shall be according to clause 5.2.2.3. The SDF shall send the SIP MESSAGE request towards the Core IMS according to the procedures of the Core IMS. When the SDF generates and sends the service attachment information to the UE, it can check IPTV profile of the user, and provides the custom/personalize service attachment information to the UE. IPTV profile including: • Location information, e.g. the SDF can retrieve the location of the UE and send the address of the SSF based on the location of the UE. • User subscription information. • UE capabilities, including the model, vender, version, coding format etc., and the SDF can send the service attachment information to the UE based the UE capabilities. When the service attachment information is changed, the SDF may generate a SIP method request including new service attachment information.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.2.2.2 Pull mode
|
The SDF addresses may be determined by the UE using any of the alternatives as defined in annex I. When the SDF receives a SUBSCRIBE request, if personalized information is required it shall perform user's identity verification as defined in ES 283 003 [20], clause 5.7.1.4. After successful user identification if an IPTV User Profile is available it is possible to perform personalization of the body (Service Attachment Information) of the NOTIFY. Filtering may also be performed if device capabilities are available to the SDF. If the SDF receives a SIP SUBSCRIBE message body from the UE carrying UE capabilities, the SDF shall process the SIP request as follows - if the content-type in the request does not match "application/vnd.etsi.iptvueprofile+xml:, then the SDF shall respond with a 415 Unsupported Media Type error. The SDF shall examine the parameters specified in the SIP SUBSCRIBE body and shall then record UE capabilities information as part of the IPTV user profile data. NOTE 1: The UE capabilities that are recorded as part of the IPTV user profile may be used by the SSF for personalization purposes. For a successful subscription, the SDF shall generate a SIP 200 OK in response to the SUBSCRIBE request. The SDF shall then send a NOTIFY request immediately. NOTE 2: The SDF can select personalized SSF information based on IPTV user profile. For example, the SDF will send only addresses of SSF(s) that contain information (e.g. EPG) related to the BC service package(s) subscribed by the user. The contents of the NOTIFY request shall be as follows: - The Event header shall be set to the "ua-profile" event package. - The "effective-by" parameter for the event header shall be set to 0. - The content type shall be set to "application/vnd.etsi.iptvdiscovery+xml". - The message body shall conform to the XML schema described in annex M and shall be according to clause 5.2.2.3. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 63 SUBSCRIBE request received by the SDF User’s identity verification Personalized information required Anonymous Retrieve IPTV user’s profile OK No yes Send 200 OK and NOTIFY with default document Not available Default document exists ? Send error response code 4xx and no NOTIFY Yes No available Send 200 Ok and NOTIFY with personnalized document SUBSCRIBE message body present? Examine UE information and store in IPTV user profile. Yes No Figure 5.2.2.2: SDF logic for processing SUBSCRIBE requests When any parameter of service configuration information has changed, the SDF may generate a NOTIFY request including new service configuration information. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 64
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.2.2.3 Service Attachment Information
|
The body of the SIP message from SDF shall include an XML document as defined in annex M listing SSF addresses and the means of connecting to the SSFs for retrieving service selection information. For each SSF, the following sub-elements are populated as follows: Table 5.2.2.3: SSF information sending by SDF during service attachment procedure Element Name Description Mandatory(M)/ Optional (O) Many = several instances are possible SSF Root element M Many @ID Identifier for SSF defined uniquely for a given SDF M @Technology Indicates the technology used for delivering service selection information. Currently defined technologies are "dvb.org_iptv""openmobilealliance.org_bcast", "tispan.org_sad", "tispan.org_tva2", and "tispan.org_iptvcontentmarker". Refer to annex L for the mapping of Technologies defined in the present document Refer to annex O for the definition procedure of new technologies M @Version This is incremented when one or more fields in SSF element have changed Description Description of the SSF for potential display in one or more languages. One description is allowed per language O Many ServiceProvider Provides information about IPTV service provider O @DomainName The IPTV service provider domain name M @LogoURI Link for the IPTV Service Provider Logo O Name Name of the IPTV Service Provider for potential display in one or more languages. One name is allowed per language M Many Description Description of the IPTV Service Provider for potential display in one or more languages. One description is allowed per language O Many Pull Provide information to access SSF via Pull Mode O Many @Location URI of the SSF M DataType Specifies the type of service selection information available at the SSF (e.g. COD, BC) M Many @Type The type of service selection information. The exact format is determined by the Technology M Segment Used to logically separate service selection information The mandatory/optional nature of this parameter depends on the SSF Technology and is detailed in annex L @ID Identifier for segment. The exact format is determined by the Technology M @Version This is incremented when the information in segment changes O Push Provide information to access SSF via Push Mode O Many @IPVersion Specifies the IP Version (4 or 6). If omitted, then version 4 is assumed O ETSI ETSI TS 183 063 V3.6.1 (2014-08) 65 Element Name Description Mandatory(M)/ Optional (O) Many = several instances are possible @MulticastAddress The address to join to in order to retrieve service selection data M @MulticastAddress The address to join to in order to retrieve service selection data M @SourceAddress The address of the sender of the service selection data O DataType Specifies the type of service selection information available at the SSF (e.g. COD, BC) M Many @Type The type of service selection information. The exact format is determined by the Technology M Segment Used to logically separate service selection information The mandatory/optional nature of this parameter depends on the SSF Technology and is detailed in annex L @ID Identifier for segment. The exact format is determined by the Technology M @Version This is incremented when the information in segment changes O NOTE 1: The mechanism used by the SDF to gather SSF information belonging to multiple service providers is outside the scope of Release 3. The following constraints apply to XML documents as described by table 5.2.2.3: • There shall be at least one Pull or Push element specified for an SSF. • When an optional element is included in the XML document, then all mandatory attributes and sub-elements related to this element shall be included as well. • Extensions to the elements are possible (refer to the XML schema defined in annex M). NOTE 2: Alternatively, annex J describes the optional case, when using a non-SIP AS based SDF (e.g. for legacy purpose) as described in annex A of TS 182 027 [2].
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.3 Service Control Function (SCF)
| |
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.3.1 Procedure for BC service
| |
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.3.1.1 UE-initiated session initiation
|
The SCF shall support the procedures specified in ES 283 003 [20] applicable to an AS acting as a terminating UA. Upon receipt of SIP INVITE request, the SCF shall examine the Request-URI to determine that it is a BC session initiation request. According to the user subscription information, the SCF shall check the service rights of requested broadcast service packages and multicast addresses. If the SCF supports the SIP INFO framework, it shall look for the Recv-Info header. If the header is present then the SCF shall be able to control the reporting the selected channel. If the header is absent, then the SCF shall not be able to control reporting of the selected channel. Following that, the SCF shall examine the SDP parameters. In particular: • It shall examine the a=bc_service parameter. This parameter contains the channel the UE intends to join. If the bc_service parameter does not point to a channel that the UE is allowed to join the SCF shall not accept the offer and shall answer with a 403 error code. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 66 • If present it shall examine the a=bc_service_package attributes and verify that the referred service packages are allowed in the user profile. The SCF shall limit the service packages and the BC services according to the user subscription (see below). If none of the service packages are subscribed, the SCF shall answer with a 403 error code. • It shall examine the c-line(s) to determine that it is a multicast session. It may also check that it corresponds to the bc_service parameter. If not, the SCF shall answer with a 403 error code. • It shall examine the b parameter if present to verify that it is the largest bandwidth of the BC services the UE intends to join. If not, the SCF shall answer with a 403 error code. If the SDP parameters are examined successfully, the SCF shall answer with a SIP 200 OK, indicating the SDP answer as follows: • The c-lines and m-lines shall be identical to ones indicated in the SDP offer. • It shall include an a=recvonly attribute. • It shall include a b-line parameter with the same value as in the offer, if present. If the b-lines were not present in the offer, the SCF shall include one with a value set to the largest bandwidth of all the BC services contained in the indicated service packages attribute. • If the SDP offer includes one or more a=bc_service_package attribute the SDP answer shall include the same number of attributes or less. The SCF shall remove service packages not subscribed by the user. If no bc_service_package attributes are included in the SDP offer the SCF shall include in the SDP answer one or more a=bc_service_package attribute, except if the SCF knows that the RACS is pre-provisioned with the list of subscribed channels and if all the subscribed channels are allowed for the session. In that case, the inclusion of a=bc_service_package is optional. NOTE: How the resources are pre-provisioned is a deployment issue; these attributes may be included for updating dynamically the RACS with new service packages or multicast address, when the UE knows its profile. The service packages shall be populated according to the user profile to indicate the service packages and BC services that can be used for the session according to annex N. If a=bc_service_package attribute is included the SCF shall include one or more mult_list parameter(s) if the user has not subscribed to the entire service package. It may also include the bc_service_id_list containing the list of subscribed BC service ids. If the user has subscribed to the entire service package, the inclusion of mult_list parameter is optional (e.g. depending on SCF local policies). Finally, if the UE supports the SIP INFO framework, and if the SCF, as well, supports the SIP INFO frameowork, then the SCF shall include the Recv-Info header in the SIP 200 OK and set it to the desired option, i.e. allow or disallow reporting the selected channel
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.3.1.1A SCF-initiated session initiation
|
The SCF shall support the procedures specified in ES 283 003 [20] applicable to an AS acting as an originating UA. Upon a cause for a BC session initiation, the SCF shall generate an initial INVITE request as specified in ES 283 003 [20] for an AS acting as an originating UA. The Request-URI in the INVITE request shall be the public user identity of the UE that is to be invited. The TO header shall have the same URI as the Request-URI. The SCF shall add a P-Asserted-Identity header containing the PSI (Public Service Identifier) of the BC Service. The FROM header shall have the same URI as the P-Asserted-Identity header. If the SCF supports the SIP INFO framework, then the SCF shall include the Recv-Info header in the INVITE and set it to the desired option, i.e allow or disallow reporting the selected channel An SDP offer shall be included in the request. The SDP offer shall be done in accordance with the allowed parameters and with media capabilities and required bandwidth for the BC session. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 67 The SDP offer at media level shall include the following elements: • The m-line(s) shall be set according to the mapping defined in clause L.2 for the BC service the SCF wants the UE to join. • The c-line(s) shall be set according to the mapping defined in clause L.2 for the BC service the SCF wants the UE to join. • An a=bc_service:BCServiceId line to indicate the BCServiceId (channel) that the SCF wants the UE to join. • Optionally one or more a=bc_service_package attributes as defined in annex N. The SCF determines the allowed service packages based on the user profile. • If the SCF has knowledge of the largest bandwidth of all the BC services included in the session, the b-line shall be included and set to this value. • An a=recvonly line. If the SCF receives a 488 error code with warning 370 Insufficient Bandwidth the SCF may perform a new SIP INVITE with a lower maximum bandwidth for BC service the SCF wants the UE to join. This procedure may be repeated. If no agreement can be reached the SCF may act accordingly.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.3.1.2 Session modification
|
Upon receipt of a re-INVITE request or an UPDATE request, the SCF shall follow the procedures defined in ES 283 003 [20] concerning the AS acting as a terminating UA or a B2BUA. When receiving an SDP offer, the SCF may modify the SDP answer in accordance to the user subscription. If the SCF finds a media line not compatible with the user's subscription, it shall set the port of this media line to 0. If none of the media lines are acceptable, it shall reply with a 403 error response. Upon request of a BC session modification, the SCF shall send a re-INVITE or an UPDATE request, depending on the dialogue state, and follow the procedures defined in ES 283 003 [20] concerning the AS acting as an originating UA.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.3.1.3 BC service with trick-play mode
|
When supporting BC service with trick play, the BC session can observe two special cases: • The Broadcast session is modified to change from Multicast to unicast flow. This is the case in which the UE activates the trick play mode. • The Broadcast session with trick play mode is modified to return to normal Broadcast TV. This is the case in which the UE deactivates the trick play mode by, e.g. switching channels from a paused channel to another live Broadcast TV channels.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.3.1.3.1 Trick-play mode activation
|
Within the existing Broadcast TV session, if the session modification request contains Service Action Data with IPTVActionDataCommand set to "SwitchToTM", the SCF shall determine the modify request is for transition from Broadcast TV to Broadcast TV with trick mode and shall act as a B2BUA, terminating the re-INVITE request and sending a INVITE request to initiate a session setup to the MCF in charge of recording the BC service that the user has selected. When sending the initial INVITE message to MCF, SCF shall follow the procedures defined in ES 283 003 [20] concerning the AS acting as originating UA or B2BUA. Prior to that procedure, the SCF shall check that the SDP in the re-INVITE contains the unicast streams description for content control and content delivery channels to be sent to the MCF to have the necessary parameter to initiate a session towards the MCF. If not, the SCF shall answer to the UE with a 403 error code. The value of Request-URI contained in the new session initiation request shall be set to the routable identifier of the MCF, i.e. the SIP URI of the MCF. The TO header shall contain the identifier of the channel to be trick-played i.e. the BC ServiceId included in the Service Action Data XML document or retrieved during session information procedure as defined in clause 5.1.3.5. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 68 If the content or channel that the user has selected is not enabled for trick play, a SIP error code 403 Forbidden, shall be generated as a response. The SDP offer sent with the INVITE to the MCF will follow the same pattern as in the CoD session initiation. The SDP answer shall contain the same number of media descriptors as in the offer, following the SDP offer/answer model as indicated in the CoD session initiation clause. The only difference with that is the inclusion of: • h-offset attribute different than 0, as calculated by the MCF indicating the offset in a given program. The SIP 200 OK message will be progressed from the SCF to the UE as the response to the session modification. The SDP answer in the SIP 200 OK shall contain the same number of media descriptors as the SDP offer in the re-INVITE.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.3.1.3.2 Trick-play mode deactivation
|
Within the existing Broadcast TV session, if the session modification request Service Action Data with IPTVActionDataCommand set to "SwitchToBC", the SCF shall determine the modify request is for transition from Broadcast TV with trick mode to Broadcast TV and shall act as a B2BUA, terminating the re-INVITE request and sending a BYE to terminate the session to the MCF. When the trick play mode is deactivated by the UE, the SCF will need to unlink the MF from the session in order to return to the normal broadcast session. Before answering to the UE, the SCF shall check that the m-lines containing the multicast streams have been added by the UE and those one containing the unicast media streams have been removed. If not, the SCF shall answer to the UE with a 403 error code. NOTE: How to add or remove a media stream in SDP conforms to ES 283 003 [20]. The SCF will then answer back to the re-INVITE request with a SIP 200 OK for the session to be returned to broadcast TV as defined in clause 5.3.1.2.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.3.1.4 Session termination
|
Upon receipt of a BC session termination request, the SCF shall follow the procedures defined in ES 283 003 [20] concerning the AS acting as a terminating UA. Upon receipt of an internal indication that a BC session shall be terminated, the SCF shall send a BYE request and follow the procedures defined in ES 283 003 [20] concerning the AS acting as a terminating UA.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.3.1.5 Procedure for PPV service
| |
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.3.1.5.1 PPV Session initiation
|
The PPV may use session initiation of BC as described in clause 5.3.1.1, with the following differences: The SCF shall examine the SDP parameters. In particular: 1) It shall examine the a=bc_service parameter. This parameter contains the channel the UE intends to join. If the bc_service parameter does not point to a channel that the UE is allowed to join, the SCF enforce the step 2). 2) If present it shall examine the a=bc_program parameter. This parameter contains the BC program ID the UE intends to enjoy. If the bc_program parameter does not point to a program that the UE subscribed the SCF shall not accept the offer and shall answer with a 403 error code. If the BC program is not ready to start, i.e. the current time is greater than/equal to program start time, the SCF shall not accept the offer and shall answer with a 403 error code. If no a=bc_program parameter is carried, the SCF shall not accept the offer and shall answer with a 403 error code. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 69
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.3.1.5.2 PPV Session termination
|
Upon receipt of a BC session termination request, the SCF shall follow the procedures defined in ES 283 003 [20] concerning the AS acting as a terminating UA, which is similar with BC session termination as described in clause 5.3.1.4. When the PPV program ends, SCF shall generate a BYE request and follow the procedures defined in ES 283 003 [20] for an originating UE, which is similar with BC session termination as described in clause 5.3.1.4.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.3.2 Procedure for CoD service
|
The SCF shall support the procedures specified in ES 283 003 [20] applicable to an AS acting as a proxy or B2B UA.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.3.2.1 Procedure for handling missing parameters before session initiation
|
When receiving the SIP OPTIONS message, the SCF shall select the appropriate media function (see TS 182 027 [2]) and forward the SIP request to the appropriate MCF by changing the "Request-URI" accordingly. The SCF shall not change the user-part of the TO header in order to keep the content-id in the OPTIONS request. In certain cases, the SCF may also forward the SIP OPTIONS over to a default media function. When receiving a 301 or 302 response from the MCF, the SCF shall not forward this message to the UE. The SCF may check if the MCF indicated in the contact header is allowed destinations. If allowed, the SCF shall use one of the MCF URI indicated in the contact header of this response and use it as a destination for the redirected OPTIONS.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.3.2.2 UE-initiated session initiation
|
When receiving any SIP request, the SCF may examine the request to see if it is compatible with the user's subscription (e.g. parental control level). If the user is not allowed to initiate a session for the requested content, the SCF shall reply with appropriate, SIP error code 403 Forbidden, response. The SCF shall select the appropriate media function (see TS 182 027 [2]) and forward the SIP request to the appropriate MCF by changing the "Request-URI" accordingly. The SCF shall not change the user-part of the TO header in order to keep the content-id in the INVITE request. In certain cases, the SCF may also forward the SIP INVITE over to a default media function. When receiving a 301 or 302 response from the MCF, the SCF shall not forward this message to the UE. The SCF may check if the MCF indicated in the contact header is allowed destinations. If allowed, The SCF shall use one of the MCF URI indicated in the contact header of this response and use it as a destination for the redirected INVITE.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.3.2.2A SCF-initiated session initiation
|
Upon a cause for a CoD session initiation, the SCF shall generate an initial INVITE request as specified in ES 283 003 [20] for an AS performing 3rd party call control as an initiating B2BUA, involving coordinated signalling with the UE and the MCF. An example protocol flow is provided in clause A.3.1A. For the INVITE request to the UE the Request-URI is the public user identity of the UE that is to be invited. The TO header shall contain the same URI as in the Request-URI parameter. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 70 The SCF shall add a P-Asserted-Identity header containing the CoD session that is to be activated. The FROM header shall have the same URI as the P-Asserted-Identity header. The URI of the CoD session that is to be activated shall be composed of a user and domain part as defined as follows: • The user part contains the content identifier in a free string format, as defined in TS 182 027 [2]. • The domain part is the Service Provider domain name. The INVITE request to the UE may contain an empty session description. The UE offers an SDP to the SCF. Upon receiving the SDP from the UE the SCF selects the MCF and uses the SDP offer in the INVITE to the MCF. For the INVITE request to the MCF the SCF shall add a P-Asserted-Identity header containing the public user identity of the invited UE. The FROM header shall have the same URI as the P-Asserted-Identity header. For the INVITE request to the MCF the Request-URI is set to the MCF address. The TO header shall include the content id of the CoD session that is to be activated in the user part of the URI. When the SCF receives the SIP 200 OK with the SDP answer from the MCF the SCF forwards it in the SIP ACK to the UE.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.3.2.3 Session modification
|
Void.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.3.2.4 Session termination
| |
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.3.2.4.1 Session termination using RTSP method 1
|
For SCF-initiated CoD session termination, the SCF shall send a BYE Request towards the UE and a BYE request towards the MF as specified in ES 283 003 [20].
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.3.2.4.2 Session termination using RTSP method 2
|
The SCF shall support the procedures specified in ES 283 003 [20] applicable to an AS acting as a proxy or B2B UA for call release. For SCF-initiated CoD session termination, the SCF shall send a BYE Request towards the UE and a BYE request towards the MF as specified in ES 283 003 [20].
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.3.2.5 Procedures for handling COD Service action data
|
Upon receiving an INFO request with Content-type set to "application/vnd.etsi.iptvsad-cod+xml", the SCF retrieves the service action data from the INFO message body and either creates or updates the matching object instance. A SIP 200 OK message with no body shall be sent to the originator if the INFO request is successfully received for an existing call; the service action data objects shall be created (or updated) according to the data retrieved from the INFO message body. A "405 Method Not Allowed" shall be sent back to the originator if the SCF has no capability to process INFO message. A "415 Unsupported Media Type" shall be sent back to the originator if the INFO request contains a body that the SCF does not understand. A "481 Call Leg/Transaction Does Not Exist" shall be sent back to the originator if the INFO request does not match any existing session. NOTE: The XML schema mapping to the MIME type: "application/vnd.etsi.iptvsad-cod+xml" is available in annex K of the present document. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 71
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.3.3 Procedure for Service Configuration
|
The UE uses the XCAP to manage the IPTV user profile (see clause 6.1.2). In order to keep the IPTV services data synchronized with the network elements and other terminals that the user might be using, the UE should subscribe from the SCF to changes in the XCAP IPTV documents. NOTE: Changes may result from XCAP manipulation and/or operator's actions. When the SCF receives a SUBSCRIBE request having the Event header field value set to "xcap-diff", the SCF shall authorize the request based on the contents of the P-Asserted-Id. If the authorization is successful the SCF shall generate a SIP 200 OK response to the SUBSCRIBE request and generate notifications in accordance with reference [15] and reference [26].
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.3.4 Procedure for PVR Service
| |
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.3.4.1 Procedures for PVR Service Capture Request
|
Upon receiving a SIP MESSAGE request, the SCF identifies the Content-type associated with the MESSAGE request and takes appropriate actions as specified below. The SCF then checks whether the Service Package id is indeed authorized for the user issuing the request. The actual BC service to be recorded/bookmarked is extracted from the XML body carried in the SIP MESSAGE. The SCF checks the rights granted to the user for this particular BC service. A "415 Unsupported Media Type" shall be sent back to the originator if the MESSAGE request contains a body that the SCF does not understand.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.3.4.1.1 Procedures for Impulsive Request
|
Case 1: content_type set to "application/vnd.etsi.iptvsad-bc+xml". Upon receiving a SIP MESSAGE request with Content-type set to "application/vnd.etsi.iptvsad-bc+xml", the SCF retrieves the service action data from the SIP MESSAGE message body and either creates or updates the matching object instance: - If the Bookmark attribute is set to "NOW", the SCF should set it to the current timestamp. NOTE: The XML schema mapping to the MIME type: "application/vnd.etsi.iptvsad-bc+xml" is available in annex K of the present document." Case 2: content_type set to "application/vnd.etsi.iptvsad-npvr+xml". Upon receiving a SIP MESSAGE request with Content-type set to "application/vnd.etsi.iptvsad-npvr+xml", the SCF retrieves the service action data from the SIP MESSAGE message body and either creates or updates the matching object instance: - If NPVRContentId is not present, it should be generated by the SCF itself. - If the request is acknowledged by the proper entities (e.g. N-PVR servers) RecordStatus is set to "Scheduled" by the SCF. - If the RecordStartDate attribute is set to "NOW", the SCF should set it to the current timestamp. The SCF may check the tNPVRStorageLimitInTime and tNPVRStorageLimitInVolume parameters associated with the user profile to decide whether to allow the user to capture the selected live content. Case 3: content_type set to "application/vnd.etsi.iptvsad-cpvr+xml". Upon receiving a SIP MESSAGE request with Content-type set to "application/vnd.etsi.iptvsad-cpvr+xml", the SCF retrieves the service action data from the SIP MESSAGE message body and either creates or updates the matching object instance: - If CPVRContentId is not present, it should be generated by the SCF itself. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 72 - If the request is acknowledged by the proper entities (e.g. C-PVR servers) RecordStatus is set to "Scheduled" by the SCF. - If the RecordStartDate attribute is set to "NOW", the SCF should set it to the current timestamp. The SCF may extract the target user identity from the TargetUEId attribute, and find out the corresponding target user profile by this user identity. The SCF check the tAuthorizedControlUser parameters associated with the target user profile to decide whether to allow the user who sent the C-PVR capture request to capture the selected live content on behalf of the target user. On all the cases above, a SIP 200 OK message with no body shall be sent to the originator if the MESSAGE request is successfully received for an existing call and the service action data objects shall be created (or updated) according to the data retrieved from the MESSAGE message body. For N-PVR,The the SCF follows relevant procedures to initiate the recording of the content by the N-PVR-MF. Details of the procedures are outside scope of the present document. ForC-PVR, the SCF follows procedures specified in clause 5.3.4.3 to initiate the recording of the content by the Target UE.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.3.4.1.2 Procedures for Offline Request
|
Upon receiving a SIP MESSAGE request, the SCF checks to see if the Content-type set to "application/vnd.etsi.iptvsad-npvr+xml". If so, it follows the procedures outlined in corresponding case 2 in clause 5.3.4.1.1.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.3.4.2 Procedures for N-PVR Session
|
The SCF follows procedures outlined in clause 5.3.2 for handling a COD session. NOTE: The XML schema mapping to the MIME type: "application/vnd.etsi.iptvsad-npvr+xml" is available in annex K of the present document.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.3.4.3 Procedures for C-PVR Service Recording Session
|
The SCF shall check the C-PVR service action data of the user to validate whether the record start-time is reached, the SCF may also get the C-PVR session related information, e.g. the BC serviceId and the TargetUEId which is populated by SIP instance identifier in clause 5.6.3. Then the SCF sends a SIP MESSAGE to the UE that indicated by the TargerUEId in the service action data using the notification procedures described in clause 5.3.6, and includes the following sub-elements of "CPVRRecordInfo" element. • The "NotificationReason" in the message body shall be set to "CPVRRecord", the "CPVRRecordInfo" element shall include the following sub-elements: - The "CPVRContentID", if present, shall be set to the same value that stored in the C-PVR service action data. - The "BCServiceId" in the message body shall be set to same value that stored in the C-PVR service action data. - The "RecordEndDate " in the message body shall be set to t same value that stored in the C-PVR service action data.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.3.5 Procedure for UGC Service
| |
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.3.5.1 Procedure for handling UGC declaration request
|
Upon receiving a SIP MESSAGE request, the SCF identifies the Content-type associated with the MESSAGE request and takes appropriate actions as specified below. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 73 The SCF shall immediately send a SIP 200 OK response without message body to the originator after the MESSAGE request is successfully received; The SCF then checks whether the user is authorized for declaring UGC. When the MESSAGE request contains message body including transaction-id, the SCF shall initiate another MESSAGE request to the originating UE, including the following contents: • The Request-URI and the To header in the MESSAGE request shall be the public identity of the originator. • From header shall be set to the PSI of UGC service. • Call-ID shall be generated by SCF. • CSeq shall be generated by SCF. • The Content-type header shall include the MIME type of XML documents representing IPTV service action data: "application/vnd.etsi.iptvsad-ugc+xml". • The message body carries a "UGC items" element described in TS 182 027 [2], clause 7.4.1, including a UGC contentID generated by the SCF, and the same transaction-id extracted from the received MESSAGE. When the MESSAGE request does contain a message body, the SCF shall treat it as a publication request for UGC description information and take the actions described in clause 5.3.5.2. The SCF does not need to store the transaction ID as part of the SAD since it is used only during the declaration phase.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.3.5.2 Procedure for handling publication request of UGC description information
|
Upon receiving a SIP MESSAGE request, the SCF sends back an immediate 200 OK to the originator, as the same procedure described in 5.3.5.1. The SCF then checks whether the user is authorized to publish UGC description information. When the MESSAGE request contains no message body, the SCF shall follow the same procedure as described in clause 5.3.5.1. When the MESSAGE request does contain a message body, the SCF shall retrieve the UGC contentID and UGC description information from the message body, then SCF shall establish the relationship between the UGC contentID and the UGC description information and publishes to the interested entities, e.g. SSF. NOTE 1: How the UGC description information is published from SCF to other entities is out scope of the present document. NOTE 2: It is up to the Service Provider policy when the UGC content has been successfully uploaded but the UGC description information is not published, which is out scope of the present document.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.3.5.3 Procedure for handling UGC creation request
|
When receiving a SIP INVITE request from the UE, the SCF may examine the request and exchanged session description to see if it is compatible with the user's subscription (e.g. UGC profile). If the user is not allowed to initiate a session for the requested content, the SCF shall reply with appropriate response, with SIP error code 403 Forbidden. The SCF shall select the appropriate media function (see TS 182 027 [2]) and forward the SIP request to the appropriate MCF by changing the "Request-URI" accordingly. The SCF shall not change the To header of the SIP request. In certain cases, the SCF may also send the SIP INVITE to a default media function. When receiving a 301 or 302 response from the MCF, the SCF shall not forward this message to the UE. The SCF may check if the MCF indicated in the Contact header is valid destination. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 74 If allowed, The SCF shall use one of the MCF URI indicated in the Contact header of this response and use it as a destination for the redirected INVITE. NOTE 1: UGC content creation using upload method, as well as the protocol used for upload are out scope of the present document. NOTE 2: Procedures for publishing UGC description in clause 5.3.5.1 and UGC declaration procedures in clause 5.3.5.2 may also be embedded in the above UGC creation procedures. If the SCF has a stored pre-selection for the created UGC, it shall initiate a session initiation to the UE that pre-selected the UGC, as described in clause 5.3.2.2A for CoD, and includes the contentID of the pre-selected content in the From header.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.3.5.4 Procedure for handling UGC watching request
| |
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.3.5.4.1 UGC pre-selection
|
Upon receiving a SIP MESSAGE request for pre-selection of UGC the SCF shall extract the contentID from the message body. If the contentID is invalid or unknown the SCF shall respond with a 406 Not Acceptable. If the UE is not allowed to pre-select the UGC the SCF shall respond with a 403 Forbidden. If the SCF accepts the request it shall store the pre-selected contentID and the requesting UE, and send a SIP 200 OK response.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.3.6 Notification service
|
SCF decides to inform the user of various events, e.g. based on the user subscription and/or the specific service logic. Then SCF generates and sends a message request for the transport of notification.. Signalling path applies if a single user is to be notified e.g. CoD content recommendation, SCF sends the Message via IMS core to the user. Multicast media path applies if large group of users are to be notified, e.g. upcoming BC program notification to users watching the same BC service, SCF sends the message to the MF which delivers the Message to the users via a multicast channel.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.3.6.1 Procedure for Notification service using signalling path
|
The SCF on detection of a trigger event to notify the user, e.g. new CoD availability, incoming call, content recommendation, etc., and the SCF decides to notify the UE through signalling path according to local policy, the SCF shall generate a SIP MESSAGE request in accordance with ES 283 003 [20] and TS 124 229 [24] as used in ES 283 003 [20]. The contents of the above SIP method request shall be as follows: • The Request-URI of the SIP MESSAGE request shall be set to the public user identity of the intended recipient. • The From header shall be set to the SIP URI of the SCF. • The To header shall be set to the public user identity of the intended recipient. • Call-ID shall be generated by the SCF. • CSeq shall be generated by the SCF. • The Content-type header shall include the registered MIME type of XML documents representing IPTV Notification service data: "application/vnd.etsi.iptvnotification+xml". • The message body shall carry the notification data and conform to the XML schema described in annex S: - NotificationReason shall be present and set to the reason caused the notification: ContentInsertion, in the case of content insertion service. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 75 CPVRRecord, in the case of C-PVR service. InstantMessage, in the case of instant message service. IncomingCall, in the case of incoming call management. ContentRecommendation, in the case of content recommendation service (CRS). - ContentIdentifier shall be set to the content identifier related to the notification, if present. - NotificationSender shall be set to the identifier of the originator who provides the notification, if present. - NotificationReceiver shall be set to the identifier of target user, if present. - IncomingCallInfo shall be set to the information of the caller, in the case of incoming call management. - ContentInsertionInfo shall be set according to the ad insertion information, in the case of content insertion. - CPVRRecordInfo shall be set to the information for C-PVR recording, in the case of C-PVR. - ContentRecommendationInfo shall be set to the information for content recommendation, in the case of CRS. - MediaPathNotificationInfo shall not be included. - MulticastAddress shall not be carried in the body. The SCF shall send the SIP MESSAGE request towards the Core IMS according to the procedures of the Core IMS in accordance with ES 283 003 [20].
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.3.6.2 Procedure for Notification service using multicast media path
|
When triggered by a notification event associated with a BC service, e.g. user commenting to the BC program, recommendations for BC watchers, etc., the SCF shall generate a SIP MESSAGE request outside the dialog or SIP INFO message inside the dialog, and then send it to appropriate MCF. The contents of the request shall be as follows: • The Request-URI in the MESSAGE request shall be MCF URI. • The From header shall be set to the SIP URI of the SCF. • The TO header shall contain the same URI as in the "Request-URI" parameter. • Call-ID shall be generated by the SCF. • CSeq shall be generated by the SCF. • The Content-type header shall include the registered MIME type of XML documents representing IPTV Notification service data: "application/vnd.etsi.iptvnotification+xml". • The message body shall carry the notification data conforming to the XML schema described in annex S: - NotificationReason shall be present and set to the reason caused the notification; - ContentIdentifier shall be set to the BC service ID with which the notification is associated, if present; - NotificationSender shall be set to the identifier of originator who provides the notification, if present; - NotificationReceiver shall be set to the identifier of target user, if present; - MediaPathNotificatonInfo shall be set to the information related to the notification using media path, in case of multicast messaging or multicast notification: a) MulticastAddress shall be set to the multicast address used for notification delivery, if present. b) InstantMessageInfo shall include the notification content text that the NotificationSender wants to send out. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 76
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.3.7 Procedure for restricted trick play
|
When receiving SIP INVITE request for BC with trick mode or CoD services specified in clauses 5.3.1.3 and 5.3.2.2, SCF shall further acquire the restricted trick play policy per the content identity and/or user's subscription information. Following the successful establishment of the session, and if the SCF has restricted trick play policy applicable to the selected content, the SCF shall immediately send a SIP INFO message, including the Restricted- Trickplay Info Package (defined in clause ZA.2) according to the SIP INFO framework, to the MCF selected for the session. The SCF should setup a session towards the UE only until after a confirmation on SIP INFO in order to avoid race conditions. The SIP INFO message SHALL include a XML body to describing the restricted trick play policy. The parameters shall be included as follows: • ContentID: the identifier for a content that SHALL be controlled by the restricted trick play policy. • StartTime: the start time that the restricted trick play SHALL be enforced. • EndTime: the end time that the restricted trick play SHALL be enforced. • RTSPOperation: the RTSP operations that are not permitted. The Content-Type header shall be set to "application/vnd.etsi.iptvrestrictedtrickplay+xml". NOTE: The XML schema mapping to the MIME type: "application/vnd.etsi.iptvrestrictedtrickplay+xml" is available in annex T of the present document. Note that the MCF shall have indicated its willingness to receive the Restricted-Trickplay Info Package.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.3.8 Procedure for Service Initiation for Remote UE
| |
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.3.8.1 Procedure for handling the request of remote UE initial procedures
|
Upon receiving a SIP REFER request, the SCF shall check whether the user is authorized to perform service initiation and the authorized information list may be set by the Target UE. If the request is authorized, the SCF then forwards the request to the Target UE.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.3.9 Procedures for Playlist handling
|
Playlists that are owned and created by the network can be conveyed using SIP re-INVITE, SIP UPDATE or SIP INFO based on the SIP INFO framework. These playlists are typically not visible to the user, and the user cannot control them for trick mode purposes. At session startup, playlists are conveyed within a SIP INVITE. Following the session establishment, conveying the play list using a SIP re-INVITE or a SIP UPDATE implies an immediate cessation of any content currently being streamed, if applicable, and a content switch to the content in the conveyed playlist. The conveyed playlist replaces any existing list. Following the session establishment, conveying the play list using SIP INFO based on the SIP INFO framework results in the conveyed list replacing any existing list.If content is being streamed (from an existing list) when the playlist is conveyed, streaming continues until its completion before content from the new play list starts streaming. 5.3.9.1 Network-Owned Playlist procedures for during CoD session initiation This procedure is similar to the procedure outlined in clause 5.3.2.2 for CoD session initiation, with the following difference: the SCF generates playlist information and passes it in the SIP INVITE request to the appropriate MCF. Whether the SCF generates the playlist information and sends it to the MCF depends on the content identifier in the Request-URI of the SIP INVITE request. The playlist information may be generated in two ways: • Statically - according to pre-configured playlist information. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 77 • Dynamically - generated on demand, potentially taking user profile information into account. In the latter case, the SCF may use external components (e.g. an advertising system). Before the SCF forwards the SIP INVITE request to the MCF, it adds the playlist information as MIME multi-part to the SIP INVITE request. The SCF shall set "Content-Type: multipart/mixed; boundary=unique-boundary" in the SIP INVITE request. The SCF should ensure that the SDP part of the SIP INVITE request is contained in the first part of MIME multipart message and the playlist information is added as a subsequent part of this MIME multipart message. The contents of the playlist information shall follow W3C SMIL 2.1 [1]: • The playing sequence information of IPTV contents shall be written in element content whose tag name is "seq". • A "video src=<IPTV content identifier>" shall be present and be set to IPTV Content identifier (e.g. CoDId, PVRContentID, etc). The position of this element between "seq" elements indicates the playing sequence. This element may include a timing control attribute: "begin", "end" and "dur": - "begin" attribute is optionally set to the value of the starting point of IPTV Content; - "end" attribute is optionally set to the starting point of IPTV Content; - "dur" attribute is optionally set to the duration of IPTV Content; - "href" attribute is optionally set to the multicast content source information (e.g. multicast address) from which the content is fetched. Additionally, this element may also include the attribute "skip-content" to identify whether trick play control for IPTV content is allowed or not: - "skip-content" is optionally set to the Boolean value. There may be one or more playlist entries in a single playlist. For each playlist entry with the "skip-content" attribute is present and set to false, the SCF shall generate a trick play restriction XML for inclusion in the SDP body as specified in clause 5.3.7 and sends it to the MCF as a part of a MIME multipart message. If "skip-content" not present, it shall be interpreted as equivalent to be present and set to true. 5.3.9.2 Playlist procedures during an existing CoD session If the SCF desires to just update the current playlist, the SCF shall send to the MCF a SIP INFO request that includes the Playlist Info-Package (defined in clause ZA.5) in this case, and where the body of the SIP INFO request carries the playlist information as described in clause 5.3.9.1. The content of the playlist information shall follow W3C SMIL 2.1 [39] as well as in clause 5.3.9.1. Note the Content-Type header in the SIP INFO request shall include the registered MIME type of XML documents representing IPTV playlist data: "application/vnd.etsi.playlist+xml". The playlist sent by the SCF regarding an ongoing CoD Session overrides any earlier playlist of that session. When composing the playlist, the SCF shall populate it in line with the existing CoD session parameters. If the SCF desires to stop the streaming the current content immediately and switch to a new content, and a new playlist, it shall use a SIP re-INVITE or SIP UPDATE for that purpose. The body of whichever message used shall include the new playlist and populated as described above in clause 5.3.9.1.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.3.10 Procedure for Personalized Service Composition
| |
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
5.3.10.1 UE-initiated session initiation
|
When an SCF receives an initial INVITE request from the UE containing a PSCid, it shall check whether it already has a record of the indicated PSCid: • If it does, then the SCF shall correlate the session with the PSCid. • If it does not, then the SCF shall make a record of the PSCid and correlate the session with the PSCid. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 78 In both cases, the SCF may perform service logic associated with the PSC, e.g. SCF-initiated session initiation, see clause 5.3.10.2.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.