hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 5.3.17 Procedures for Unicast Content Download | |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 5.3.17.1 UE-initiated Content Download session initiation | The procedures are similar with the procedures outlined in clause 5.3.2.2 for UE-initiated CoD session initiation, with the following differences: the SCF checks the content identifier selects and forwards the SIP request to the MCF which is in charge of the download service by changing the "Request-URI" accordingly. |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 5.3.18 Procedure for Preview Service | |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 5.3.18.1 Procedures for BC preview session | |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 5.3.18.1.1 Session initiation | In the case of either single-screen or multi-screen BC preview, the procedures can refer to BC session initiation as described in clause 5.3.1.1. NOTE: The SCF may execute the preview policy after accept the session initiation, e.g. only allow 5 minutes view time for the user, then send teardown request towards UE. |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 5.3.18.2 Procedures for CoD preview session | 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.18.2.1 Session initiation | For preview content having its own content identifier, the preview procedures can use the procedures specified in clause 5.3.2.2. |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 5.3.19 Procedure for Session Transfer | |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 5.3.19.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. It is assumed that the SCF includes the session transfer functionality based on 3GPP procedures in that regard. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 85 |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 5.3.19.1.1 Transferee UE session initiation | Upon receipt by the SCF for an initial INVITE by a transferee related to session transfer, the SCF shall follow the procedure in clause 5.3.2.2 with the following qualifications: • If the request includes the SIP Replace header that refers to a SIP session for which the SCF has no state, the SCF shall return an appropriate SIP 403 (Forbidden) response. • If the request includes the SIP Replace header that refers to a SIP session for which the SCF has a state, then the SCF shall first authorize the user for the request. If the user is not authorized then the SCF shall return a SIP error. If the user is authorized for the request, then clause 5.3.2.2 is followed with the following qualifications: - If the same MCF of the transferred session can be used, then the SCF shall send a SIP UPDATE (or re- INVITE) to update the SIP session leg with the new SDP for the transferee. - If the same MCF of the transferred session cannot be used, and a new one is required, then the SCF shall terminate the SIP leg towards the old MCF, followed by a SIP UPDATE or SIP re-INVITE to the transferor to put the media on hold (transferor UE shall not perform any RTSP transactions), and then create a new SIP session leg for the requested content using existing procedures as defined in clause 5.3.2.2. After the SIP leg for the transferred session is successfully established, the SCF returns a SIP 200 OK to the transferee. |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 5.3.19.2 Session Transfer - Push Mode | |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 5.3.19.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.3.19.2.2 Transferor and Transferee Handling of Session Transfer Request | Upon receipt by the SCF of a SIP REFER request, the SCF SHALL follow the procedure in TS 124 237 [58], clause 15 entitled "Roles for inter-UE transfer without establishment of collaborative session". Following that, and if the request is successfully authorized, the REFER request is forwarded to the transferee UE. The SCF shall receive a SIP 200 OK or a rejection of the transfer request from the transferee, and which it will forward to the transferor. If the session transfer request is accepted by the transferee, the SCF shall expect a session initiation request to be initiated from the transferee. Following the successful session initiation by the transferee and the reporting of the successful session initiation to the transferor by the transferee through a SIP NOTIFY, the SCF shall terminate the old session by sending a SIP BYE to the transferor and shall wait for the arrival of the SIP 200 OK. |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 5.4 Media Control Function (MCF) | |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 5.4.1 Procedure for CoD service | The MCF shall support the procedures specified in ES 283 003 [20] applicable to a terminating UA. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 86 |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 5.4.1.1 Procedure for providing missing parameters before session initiation | When receiving SIP OPTIONS request, the MCF shall examine the CoD content identifier present in the user-part of the TO header. The MCF may decide to redirect the request to another MCF as described in TS 182 027 [2], clause 5.1.3.3. In this case, the MCF shall return a 301 response if the content is not managed by this MCF and the MCF indicates one or more MCF addresses in the contact header as indicated in ES 283 003 [20]. If the MCF responds to the request, the MCF shall answer with the SDP description of the content delivery channel conforming to clause 5.4.1.2.1.1, as requested by the request URI. |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 5.4.1.2 Session initiation | When receiving COD session initiation SIP request, the MCF shall examine the CoD content identifier present in the user-part of the TO header and the media parameters in the received SDP, if present. The MCF may decide to redirect the request to another MCF as described in TS 182 027 [2], clause 5.1.3.3. In this case, the MCF shall return a 301 response if the content is not managed by this MCF or 302 response for any other reasons (e.g. load-balancing). The MCF indicates one or more MCF addresses in the contact header as indicated in ES 283 003 [20]. |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 5.4.1.2.1 Procedure for establishing the RTSP content control and content delivery channel | 5.4.1.2.1.1 MCF as SDP answerer In the case when the MCF receives a session initiation request, the MCF shall examine the RTSP SDP parameters and shall allocate server ports for the CoD session. If the MCF supports CoD RTSP playback control Method 1 as defined in clause 7.2.1, the MCF shall generate an RTSP session ID for the content control channel. The MCF shall also examine the media lines of the media channel SDP offer. If none of the media lines in the SDP offer are acceptable, it shall reply with a SIP error code 488 Not Acceptable here, response. One reason may be that the SDP does not match the indicated content. Otherwise, the MCF shall answer with a SIP 200 OK, indicating the SDP answer. If the content that the user has selected cannot be found the MCF shall reply with appropriate, SIP error code 404 Not Found, response. The SDP parameters for the RTSP channel shall be set as follows: • An 'm' line for an RTSP stream of format: m=<media> <port> <transport> <fmt>: - The media field shall have a value of "application". - The port field is setup according to ES 283 003 [20]. The port number is set to the port allocated by the MCF. - The transport field shall be identical to the one received in the SDP offer. - The fmt field shall be identical to the one received in the SDP offer. (ex. m=application 554 tcp iptv_rtsp). • An "a=setup" attribute shall be present and set as "passive" as defined in ES 283 003 [20] indicating that connection shall be initiated by the other endpoint (UE) (ex:a=setup:passive). • An "a= connection" attribute shall be present and set as "new" as defined in ES 283 003 [20] (ex:a=connection:new). NOTE: RTSP over UDP is out of scope of the present document. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 87 • One or more a=fmtp lines representing RTSP specific attributes set as follows: - An "fmtp:iptv_rtsp h-uri" attribute shall be set to the RTSP URL to be used in the RTSP requests The h-uri can be in form of absolute or relative URI. If absolute URI is specified then it is used as-is in subsequent RTSP requests. If relative URI is specified in form of a media path, then the RTSP absolute URL could be constructed by the UE using the IPAddress (from c-line) and port (from m-line) as the base followed by h-uri value for the media path. - (a=fmtp:rtsp h-uri=<request-uri>). - If the MCF supports CoD RTSP playback control Method 1 as defined in clause 7.2.1, the MCF shall include a "fmtp:iptv_rtsp h-session" attribute representing the session-id of the RTSP session to be created (ex. a=fmtp:iptv_rtsp h-session＝<rtsp-session>). - For content related to BC service with trick-play mode the MCF shall include "fmtp:iptv_rtsp h-offset" attribute that indicates where the playback is to start from (ex. a=fmtp:iptv_rtsp h-offset＝<media-offset>). For each media stream controlled by the RTSP content control channel, SDP answer shall include a content delivery channel media description set as follows: • the "m=" line indicates the type of the media, the transport protocol and the port of the related content delivery channel. If an fmt parameter is in the SDP offer it shall be completed with the supported format by the MDF; • 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 related to the content delivery channel, (ex. c=IN IP4 <IP_ADDRESS>); • the "b=" line shall contain the proposed bandwidth. Since the COD media stream is unidirectional the bandwidth shall be set to 0, except for the case that the transport is RTP and RTCP is allowed. (ex. b=AS:0); • an "a=" line with a "sendonly" (ex. a=sendonly). |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 5.4.1.2.2 Procedure for establishing the RTSP channel separately | 5.4.1.2.2.1 MCF as SDP answerer When the MCF receives the SDP offer for establishing only the RTSP channel in the session initiation request, the MCF shall examine the SDP parameters. If the SDP offer is not acceptable, the MCF shall reply with an SIP error response. Else, the MCF shall answer with a SIP 200 OK, indicating the SDP answer. The SDP parameters for the RTSP channel shall be set as follows: • An "m" line for an RTSP stream of format: m=<media> <port> <transport> <fmt>. • The media field shall have a value of "application". • The port field is setup according to ES 283 003 [20]. Typically, the port number is a port number of 554 (rtsp server port) on its "m" line, and the "setup" attribute is set to "passive" indicating that connection shall be initiated by the other endpoint (UE). • The transport field shall be identical to the one received in the SDP offer. • The fmt field shall be identical to the one received in the SDP offer. • If "a=setup" attribute is present in the offer, it shall be present and set to "passive" as defined in ES 283 003 [20]. • If "a= connection" attribute is present in the offer, it shall be present and set to "new" as defined in ES 283 003 [20]. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 88 Optionally, an "a=fmtp:iptv_rtsp h-uri" attribute shall be set to the RTSP URL to be used in the RTSP requests The h- uri can be in form of absolute or relative URI. If absolute URI is specified then it is used as-is in subsequent RTSP requests. If relative URI is specified in form of a media path, then the RTSP absolute URL could be constructed by the UE using the IPAddress (from c-line) and port (from m-line) as the base followed by h-uri value for the media path. (a=fmtp:rtsp h-uri=<request-uri>). |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 5.4.1.3 Session modification | Upon receipt of a re-INVITE request or an UPDATE request, the MCF shall modify the session as specified in ES 283 003 [20] if the request is acceptable to the MCF in accordance with the user subscription. In order to modify the session from the MCF side, the MCF shall send a re-INVITE or an UPDATE request. The SDP parameters for the RTSP channel shall be set to the same parameters as specified in clause 5.4.1.2.2.1 except for the "a=connection" attribute. The attribute shall be set to "existing" as defined in ES 283 003 [20]. For each media stream controlled by the RTSP content control channel the SDP offer shall include a content delivery channel media description set as follows: • The "m=" line indicates the type of the media, the transport protocol 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. • The "b=" line shall contain the proposed bandwidth. • An "a=" line with a "sendonly". The MCF shall not modify RTSP channel m-line description in the SDP if the media delivery streams controlled by RTSP are not removed (port not set to zero in m-lines) in the SDP. |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 5.4.1.3.1 Procedure for establishing the content delivery channel | 5.4.1.3.1.1 MCF as SDP answerer When the MCF receives the SDP offer for establishing content delivery channel in the session modification request, the MCF shall examine the SDP parameters and answer with a SIP 200 OK, indicating the SDP answer. The SDP parameters for the RTSP channel shall be set to the same parameters as specified in clause 5.4.1.2.2.1 except for the "a=connection" attribute. The attribute shall be set to "existing" as defined in ES 283 003 [20]. The SDP parameters shall include one or more media description sets as follows: • The "m=" line indicates the type of the media, the transport protocol and the port. The type of the media, the transport protocol shall be identical to the one received in the SDP offer. The port shall be set to the value used for the 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. • The "b=" line shall contain the bandwidth. The bandwidth attribute shall be identical to the one received in the SDP offer. • The "a=" line with a "sendonly". ETSI ETSI TS 183 063 V3.6.1 (2014-08) 89 |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 5.4.1.4 Session termination | |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 5.4.1.4.1 Session termination using RTSP method 1 | Upon receipt of a BYE request, the MCF shall terminate the session as specified in ES 283 003 [20]. In order to terminate the session from the MCF side, the MCF shall first close the RTSP session that was established during session initiation by closing the underlying TCP connection if existing (e.g. in case of persistent TCP connection). The MCF shall then send a BYE request as specified in ES 283 003 [20]. |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 5.4.1.4.2 Session termination using RTSP method 2 | Upon receipt of a BYE request, the MCF shall terminate the session as specified in ES 283 003 [20]. In order to terminate the session from the MCF side, the MCF shall first close the RTSP session that was established during session initiation by closing the underlying TCP connection if existing (e.g. in case of persistent TCP connection). The MCF shall then send a BYE request as specified in ES 283 003 [20]. |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 5.4.1.5 Procedures for handling COD Service action data | Upon receiving normal playback RTSP PLAY (scale header set to 1) (see note 1) request from UE, the MCF may send a SIP INFO request to the SCF containing the user related IPTV service action data. The content of INFO request shall be as follows: - The value of the Request-URI shall be set to the one used in the related session. - 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 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 service action data: "application/vnd.etsi.iptvsad-cod+xml". - The message body carries the service action data: the matching "Available CoD" object shall be updated so that CoDDeliveryStatus is set to "Ongoing". NOTE 1: This will only be performed when the very first RTSP PLAY (scale header=1) request is received by the MCF for a given CoD session (to avoid over flooding the network with unnecessary updates when user presses Play subsequently to FFW or FRW). In the case of normal end of streaming, MCF may send a SIP INFO request to the SCF containing the related service action data. The content of INFO request shall be as follows: - The value of the Request-URI shall be set to the one used in the related session. - 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 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 service action data: "application/vnd.etsi.iptvsad-cod+xml". - The message body carries the service action data: the matching "Available CoD" object shall be updated so that CoDDeliveryStatus is set to "Completed". In the case of error occurring in streaming, MCF may send a SIP INFO request to the SCF containing the related service action data. The content of INFO request shall be as follows: - The value of the Request-URI shall be set to the one used in the related session. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 90 - From and To headers shall be set to the one defined during the session initiation procedureFrom and To headers shall be set to the public identity of the user issuing the INFO message. - Call-ID shall be set to the same value as that of the CoD session. - CSeq shall be generated by MCF. - The Content-type header shall include the registered MIME type of XML documents representing IPTV service action data: "application/vnd.etsi.iptvsad-cod+xml". - The message body carries the service action data: the matching "Available CoD" object shall be updated so that CoDDeliveryStatus is set to "Failed". NOTE 2: The XML schema mapping to the MIME type: "application/vnd.etsi.iptvsad-cod+xml" is available in annex K. If the INVITE request received in session initiation contains an Allow header that does not describe INFO, the MCF shall not send INFO request of CoD service action data. NOTE 3: INFO request may arrive at the UE if the SCF acts as a proxy. Handling of that case is not specified in the current release. If the SIP INFO request of service action data resulted in 405 or 415 response, the MCF does not send again the INFO request of service action data. |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 5.4.2 Procedure for support of BC service with trick play | As a general rule, the MCF is not involved in the BC service. Only in the case of a user initiating trick play mode of a Broadcast TV session, the MCF in charge of recording the requested channel will be linked to the session. At receipt of an INVITE message from the SCF, the MCF will derive the content ID in real time and from the channel identifier it received in the TO header then carry out the same steps as described for the CoD session (see clause 5.4.1.2) before replying back, in a positive case, with the SIP 200 OK message. In the SDP answer, the only difference with regards to the media descriptors compared to a normal CoD session is the inclusion of an h-offset attribute different than 0. At receipt of the ACK message acknowledging the SIP 200 OK, trick mode can be initiated. When the trick mode is deactivated by the UE, the MF will receive a BYE message as in the CoD session termination. The successful release of resources will imply responding with a SIP 200 OK to the SCF. 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.4.3 Procedure for N-PVR Session | The MF follows procedures outlined in clause 5.4.1 for CoD session initiation, modification and termination procedures. 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.4.4 Procedure for UGC Service | The MCF shall support the procedures specified in ES 283 003 [20] applicable to a terminating UA. |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 5.4.4.1 Procedure for handling UGC creating Session | When receiving UGC creating session initiation SIP request, the MCF shall retrieve the UGC content ID present in the To header and the media parameters in the received SDP. After that the selected MCF should establish the relationship between UGC contentID and server ports. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 91 |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 5.4.4.1.1 MCF as SDP answerer | In the case when the MCF receives a session initiation request, the MCF shall examine the SDP parameters and shall allocate server ports for the UGC session. The MCF shall also examine the media lines of the media channel SDP offer. If none of the media lines in the SDP offer are acceptable, it shall reply with a SIP error code 488 Not Acceptable here, One reason may be that the SDP does not match the indicated content. Else, the MCF shall examine the SDP media description in the SDP offer, when there is an "a=" line with a "sendonly" and there is a UGC contentID in the To header, the MCF shall answer with a SIP 200 OK, indicating the SDP answer. SDP answer shall include a content delivery channel media description set as follows: • The "m=" line indicates the type of the media, the transport protocol and the port of the related content delivery channel. If an fmt parameter is in the SDP offer it shall be completed with the supported format by the MDF. • 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 related to the content delivery channel, (ex. c=IN IP4 <IP_ADDRESS>). • The "b=" line shall contain the proposed bandwidth. • If the transfer type is included in the SDP offer it shall be copied into the SDP answer. The MCF may use the bandwidth and if present the transfer-type attributes in the SDP to police the rate the content is being uploaded. The bandwidth attribute indicates the bandwidth that the MF wants the UE to use for sending media. The MCF uses a pre-configured value to indicate the desired bandwidth. an "a=" line with a "recvonly" (ex. a=recvonly). NOTE: UGC content creation using upload method, as well as the protocol used for upload are out scope of the present document. 5.4.4.2 Procedure for handling UGC watching Session Upon receiving a SIP INVITE the MCF shall retrieve the contentID from the To header and shall check if it has an MDF with the stored content or incoming UGC multimedia stream with that contentID: • If the MCF has an MDF with the stored content, it creates a CoD session as described in clause 5.4.1.2. • If the MCF has an MDF with the incoming multimedia stream, it creates a mapping between the MDF server ports of the incoming UGC multimedia stream and the RTSP server settings for sending the associated UGC multimedia stream. The MCF acts as CoD-MCF, see clause 5.4.1.2. If the MCF does not have an MDF with the stored content or incoming UGC multimedia stream with the UGC contentID it shall respond with a 488 Not Acceptable Here. |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 5.4.5 Notification service | |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 5.4.5.1 Procedure for Notification service using multicast media path | Upon receiving a SIP MESSAGE request outside the dialog or SIP INFO request inside the dialog with Content-type set to "application/vnd.etsi.iptvnotification+xml", the MCF shall extract MulticastAddress, if present, from the message body, otherwise the MCF shall use the ContentIdentifier in the message body to obtain relevant multicast address for notification delivery. NOTE: The multicast address for notification delivery may be pre-configured on MCF or from management entities, which is out scope of this specification. A "415 Unsupported Media Type" shall be sent back to the originator if the request contains a body that the MCF does not understand. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 92 A SIP 200 OK message with no body shall be sent to the SCF if the request is successfully received and the notification data is disposed successfully. |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 5.4.6 Procedure for restricted trick play | When receiving a SIP INFO message, including the Restricted-Trickplay Info, withinPackage, within a CoD or BC with trick modes session, the MCF shall extract the restricted trick play policy from the SIP message body and store it for enforcement against the content in the concerned session. The procedures for establishing the RTSP content control and content delivery channel should follow the description in clause 5.4.1.2.1. The procedure for establishing the RTSP channel separately should follow the description in clause 5.4.1.2.2. Note that the MCF shall have indicated its willingness to receive the Restricted-Trickplay Info Package. |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 5.4.7 Procedures for Playlist handling | |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 5.4.7.1 Procedures for updating playlist information | Upon receipt by the MCF of a SIP INFO request from the SCF that includes the Playlist INFO package, the MCF shall discard any other playlist it may have acquired prior to that. Subsequently, the MCF checks the availablity of each content listed in the new playlist. The MCF shall return a SIP 301 response if some of the content indicated in the playlist is not controlled by this MCF or a SIP 302 response for any other reason (e.g. load-balancing). There is no difference between this procedures and regular CoD procedures in clause 5.4.1 from a viewpoint of the UE. When delivering content to the UE, the MCF shall switch IPTV Content according to the received playlist information. If the updated play list information is received through SIP INFO, the MF cotinues to stream the current content, if any, until its completion. Following that, the MF starts playing the content from the new playlist. If the updated play list is received through a SIP re-INVITE or a SIP UPDATE (which implictly stops the streaming of any content from the old playlist) the MF stops the streaming of the current content and starts playing content from the new playlist (see clause 5.4.7.2). |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 5.4.7.2 Procedures for Content Switching according to playlist information | When the MCF is instructed switch content, through a SIP re-INVITE or SIP UPDATE, the MCF stops the content that is currently being streamed and start streaming the next content based on the playlist. |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 5.4.8 Procedure for Personalized Channel (PCh) Service | |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 5.4.8.1 Procedure for PCh Operation | |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 5.4.8.1.1 PCh Session Initiation | When receiving the INVITE request, the MCF shall examine the PChId included in the user-part of To header, the media parameters in the SDP, and the PCh control data received, if present. The MCF may store the PCh control data after receiving the request. NOTE: The MCF may validate the content item(s) carried in the PCh control data before it sends back the response, e.g. verify the source address of the on-demand content, join the multicast group of the live content. How the MCF validates the content item is out scope of the the present document. Then the MCF shall follow the procedure in clause 5.4.1.2 to handle the request, acting as an SDP answerer for the unicast PCh session. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 93 |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 5.4.8.1.2 PCh Content Item Switch | Upon receiving the SIP UPDATE or SIP re-INVITE for a content switch, the MCF shall follow clause 5.4.7 Procedures for Playlist handling. The MF shall extract the content source address and the switch start/end time from the playlist, and prepare the delivery of upcoming PCh content item by acquiring content from the content source address before the switch start time. NOTE 1: The MF represents a combination of the MCF & MDF. In this context the MCF functionality is expected to be used. NOTE 2: How the MCF acquires content from the content source is out scope of the present document. |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 5.4.9 Procedure for Targeted Ad Insertion (TAI) | |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 5.4.9.1 Procedure for Internal TAI option | |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 5.4.9.1.1 TAI at UE side | NOTE: There are no additional procedures needed for the TAI at UE side. |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 5.4.9.1.2 TAI at MF side | If within a SIP dialog and upon receipt of a SIP INFO message from the SCF that includes the Play-List Info Package, in accordance with the SIP INFO framework and Content-Type of "application/vnd.etsi.playlist+xml", the MF shall follow the content insertion procedure as described in clause 5.4.12 for ad insertion, i.e. extract the ad Content Identifier from the encapsulated message body, and perform ad insertion. The MF shall repeat the same procedure as above if it receives outside a SIP dialog a SIP MESSAGE with a Content- Type of "application/vnd.etsi.playlist+xml". Note that the MCF shall have indicated its willingness to receive the Play-List Info Package. |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 5.4.10 Procedures for inter-destination media synchronization | |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 5.4.10.1 Synchronization session initiation | If a received INVITE contains a SyncGroupId, the MCF shall store the value of the rtcp-attribute included in the SDP. The MCF shall assign an SSRC value before responding to the INVITE. A SIP 200 OK response to the INVITE shall include this SSRC value as part of the SDP, using the attribute from RFC 5576 [46], and include both SyncGroupId and rtcp-attribute. The MCF shall also include its CNAME value as part of the attribute: • a=ssrc:<ssrc-id> <attribute>:<value> as specified in [46]. • a=rtcp-xr: grp-sync,sync-group=<SyncGroupId>, see clause W.2. • a=rtcp:port [nettype space addrtype space connection-address] as specified in [47]. SyncGroupId is a 32-bit unsigned integer in network byte order and represented in decimal. The value SyncGroupId=0 represents an empty SyncGroupId. The value 4294967295 (2^32-1) is reserved for future use. ssrc-id is a 32-bit unsigned integer in network byte order and represented in decimal. If the MCF conveys the SDP using RTSP DESCRIBE (i.e. using RTSP method 2), the SDP parameters can be equivalent. Alternatively, if the MCF has not assigned an SSRC value during SIP session setup, it assigns one before responding to an RTSP DESCRIBE. |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 5.4.10.2 Synchronization session modification | When an SSRC conflict occurs at the transport level, the MF may have to assign a new SSRC value to a media stream. If this concerns a media stream that is part of a synchronization group, the MCF shall use the session modification procedures to communicate this new SSRC to the SC. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 94 |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 5.4.10.3 Synchronization session termination | If the MCF receives session modification request for a media session that is part of a synchronization session, it shall check the request for presence of the SyncGroupId. If the SyncGroupId is not present, the MCF shall end the synchronization session for that SC. |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 5.4.11 Procedures for Content Switch within a CoD Contentlist | |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 5.4.11.1 UE-initiated Session Initiation | The handling of session initiation is similar with the CoD session initiation as described in clause 5.4.1.2, with the following differences: Upon receipt of the SIP INVITE request, the MCF checks that an "a=fmtp:3gpp_rtsp h-Supported" attribute is present and set as "3gpp-switch" under the "m" line for RTSP stream. The MCF then extracts the XML body from the SIP INVITE request, and replaces the content ID with the RTSP URL. The MCF then returns the SIP 200 OK response with the Content-Type header set to "Content-Type: multipart/mixed; boundary=unique-boundary", adds the XML body representing the updated contentlist information as MIME multi-part. The MCF also adds an "a= fmtp:3gpp_rtsp h-Supported" attribute and set as "3gpp-switch" under the "m" line for RTSP stream. |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 5.4.12 Procedure for Content Insertion at MF Side | When receiving the SIP MESSAGE request with Content-type set to "application/vnd.etsi.playlist+xml", in case there in no ongoing SIP dialog between the SCF and MCF, the MF shall immediately send back a SIP 200 OK response without any message body. When the MCF receives the SIP MESSAGE request carrying the selected content list from the SCF, the MCF checks the availablity of each content in the playlist. If "a href=<Content Source Link>" element is present the MCF shall contact the source link and fetch the content in case the required content is not on this MF. The MCF may also pre-fetch the content prior to the actual time for the content insertion, to achieve the seamless delivery of the streams. NOTE 1: How the MF fetches the content is not specified in the present document. After all information is extracted correctly, the content insertion shall be enforced on the MF, i.e. insert or replace the regular content in the on-going session with the content fetched from the content source. The MF may perform transcoding or session modification prior to the content insertion start time. The MF shall repeat the same procedure as above if it receives within a SIP dialog a SIP INFO message including the Play-List Info Package in accordance with the SIP INFO framework and Content-Type of "application/vnd.etsi.playlist+xml". NOTE 2: The MF represents a combination of the MCF & MDF. In this context the MCF functionality is expected to be used. NOTE 3: The MCF do have indicated its willingness to receive the Play-List Info Package. |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 5.4.13 Procedure for Unicast Content Download | The MCF shall support the procedures specified in ES 283 003 [20] applicable to a terminating UA. |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 5.4.13.1 Procedure for handling UE-initiated Content Download session | When receiving content download session initiation SIP request, the MCF shall examine the content identifier present in the user-part of the TO header and the media parameters in the received SDP, if present. The MCF may decide to redirect the request to another MCF as described in TS 182 027 [2], clause 5.1.3.3. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 95 In this case, the MCF shall return a 301 response if the content is not managed by this MCF or 302 response for any other reasons (e.g. load-balancing). The MCF indicates one or more MCF addresses in the contact header as indicated in ES 283 003 [20]. |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 5.4.13.1.1 MCF as SDP answerer | In the case when the MCF receives a session initiation request, the MCF shall examine the SDP parameters and shall allocate server ports for the content download session. The MCF shall also examine the media lines of the SDP offer. If none of the media lines in the SDP offer are acceptable, it shall reply with a SIP error code 488 Not Acceptable here, response. One reason may be that the SDP does not match the indicated content. The MCF may also read the bandwidth and if present the transfer-type attributes in the SDP and shape the rate of the content download. Else, the MCF shall answer with a SIP 200 OK, indicating the SDP answer. The MCF also add the XML body in the SIP 200 OK for the download session description which referenced by the session description URI indicated in Request-URI header in the SIP INVITE request. If the content that the user has selected cannot be found the MCF shall reply with appropriate, SIP error code 404 Not Found, response. Since the SIP message body contains two kinds of data type (SDP and XML), The MCF shall set the Content-Type Header to "multipart/mixed", in addition, a boundary parameter value should be included in the Content-Type header. Before the start of each content part, a Content-Type header shall be set. For SDP part, the Content-Type header SHALL be set to "application/sdp". For XML part, it shall be set to "application/vnd.etsi.iptvcontentdownload+xml". The XML schema can be refer to the TS 102 034 [3], clause C.2.3. The SDP parameters for the HTTP channel shall be set as follows: • an 'm' line for an HTTP connection of format: m=<media> <port> <transport> <fmt>: - The media field shall have a value of "application". - The port field is setup according to ES 283 003 [20]. The port number is set to the port allocated by the MCF. Typically, the port number is a port number of 80 (http server port) on its "m" line. - The transport field shall be identical to the one received in the SDP offer. - The fmt field shall be identical to the one received in the SDP offer. (ex. m=application 80 tcp iptv_http). • an "a=setup" attribute shall be present and set as "passive" as defined in ES 283 003 [20] indicating that connection shall be initiated by the other endpoint (UE) (ex:a=setup:passive). • 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>). - An "a= connection" attribute shall be present and set as "new" as defined in ES 283 003 [20] (ex. a=connection:new). - Optionally the "b=" line may contain the proposed bandwidth. Since the content download is unidirectional the bandwidth shall be set to 0. (ex. b=AS:0). |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 5.4.14 Procedure for Preview Service | |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 5.4.14.1 Procedures for CoD preview session | The MCF shall support the procedures specified in ES 283 003 [20] applicable to a terminating UA. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 96 |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 5.5 Core IMS | In general, the behaviour of Core IMS entities shall conform to the procedures specified in ES 283 003 [20]. This clause provides some further details for specific procedures and services. |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 5.5.1 Procedure for Registration | The behaviour of Core IMS entities when supporting IMS registration shall conform to ES 283 003 [20]. |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 5.5.2 Procedure for Service Attachment | |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 5.5.2.1 Push mode | The behaviour of Core IMS entities when processing the third-party REGISTER and MESSAGE method shall conform to ES 283 003 [20]. The S-CSCF sends a third-party REGISTER request to the SDF that matches the Filter Criteria of the service profile from the UPSF for the REGISTER event. The Initial Filter Criteria shall include the REGISTER method as the prime Service Trigger Point. Examples of service trigger points that may be used to build an appropriate IFC are available in annex R. |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 5.5.2.2 Pull mode | The behaviour of Core IMS entities when processing the SUBSCRIBE and NOTIFY methods shall conform to ES 283 003 [20]. SUBSCRIBE requests are routed to the SDF using one of the following methods: 1) The SDF identity received in the Request URI matches a Public Service Identity (PSI) hosted by the SDF. 2) The SUBSCRIBE request matches an Initial Filter Criteria (IFC) stored against the public user identity of the UE. The present document does not place any restrictions on the procedures to be used for routing a session to a PSI nor on the list of service trigger points to use in building Initial Filter Criteria. The Initial Filter Criteria shall include the SUBSCRIBE method as the prime Service Trigger Point. Examples of service trigger points that may be used to build an appropriate IFC are available in annex R. |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 5.5.3 Procedure for Service Configuration | Core IMS entities are not involved during service configuration procedures except if the UE subscribes to notifications to changes to its user profile, in which case the behaviour of Core IMS entities when processing the SUBSCRIBE and NOTIFY methods shall conform to ES 283 003 [20]. SUBSCRIBE requests are routed to the SDF using one of the following methods: 1) The identity received in the Request URI matches a Public Service Identity (PSI) hosted by the SCF acting as a front end to manage the user profile. 2) The SUBSCRIBE request matches an Initial Filter Criteria stored against the public user identity of the UE. The present document does not place any restrictions on the procedures to be used for routing a session to a PSI nor on the list of service trigger points to use in building Initial Filter Criteria. The Initial Filter Criteria shall include the SUBSCRIBE method as the prime Service Trigger Point. Examples of service trigger points that may be used to build an appropriate IFC are available in annex R. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 97 |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 5.5.4 Procedure for Service Selection | Core IMS entities are not involved during service selection procedures. |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 5.5.5 Procedure for CoD service | The behaviour of Core IMS entities shall conform to the procedure for handling an originating session as described in ES 283 003 [20]. INVITE requests are routed to the SCF using one of the following methods: 1) The SCF identity received in the Request URI matches a Public Service Identity (PSI) hosted by an SCF providing CoD service logic. 2) The INVITE request matches an Initial Filter Criteria stored against the public user identity of the UE. The present document does not place any restrictions on the procedures to be used for routing a session to a PSI nor on the list of service trigger points to use in building Initial Filter Criteria. The Initial Filter Criteria shall include the INVITE method as the prime Service Trigger Point. Examples of service trigger points that may be used to build an appropriate IFC are available in annex R. |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 5.5.6 Procedure for BC service | The behaviour of Core IMS entities conforms to the procedure for handling an originating session as described in ES 283 003 [20], with the additional capability that the P-CSCF transports the service package attributes as defined in annex N when present to the RACS as part of BC service resource reservation. It also handles appropriate error messages when bandwidth negotiation fails as defined in ES 283 003 [20]. INVITE requests are routed to the SCF using one of the following steps: 1) The well known Public Service Identity (PSI) received in the request URI is mapped to a set of SCFs providing BC service logic. 2) The SCF address is resolved by the INVITE request matching an Initial Filter Criteria stored against the public user identity of the UE. The present document does not place any restrictions on the procedures to be used for routing a session to a PSI nor on the list of service trigger points to use in building Initial Filter Criteria. The Initial Filter Criteria shall include the INVITE method as the prime Service Trigger Point. Examples of service trigger points that may be used to build an appropriate IFC are available in annex Q. |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 5.6 Common Procedures | NOTE: If the application contains a set of optional features and depending on the type of application (for example support of BC or CoD services have different application ids), there might be a need to have multiple IMS Application Reference Identifiers for that application that is one IMS Application Reference Identifier per sub-feature. |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 5.6.1 IMS Communication Service Identifier | The IMS Communication Service Identifier uniquely identifies the IMS service and associated SIP procedures. The IMS Communication Service Identifier defines restrictions to which SIP procedures are possible within a single SIP session or standalone transaction and how those SIP procedures are used. The IMS communication service contains an aggregation of zero, one, or several media components and the service logic managing the aggregation, represented in the protocols used, see ES 283 003 [20]. URN used to define the ICSI for the "IMS IPTV Service": urn:urn-7:3gpp-service.ims.icsi.iptv. The URN is registered at http://www.3gpp.org/tb/Other/URN/URN.htm. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 98 Summary of the URN: This URN indicates that the device supports the IMS IPTV Service. |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 5.6.2 Session Control Procedures | The ICSI SHALL be supported by he UE to differentiate the procedures for IPTV service in relation to other IMS services. For example, an IPTV unicast media stream may require differentiation from other unicast streams for other services like telephony. As specified in TS 124 229 [24], core IMS entities will accept a request which does not contain an ICSI. If Release 2 compliant UE's are supported and the IPTV related ICSI is not supported by the UE the differentiation of services relies on RACS procedures outside the scope of the present document. The "IMS IPTV Service" may support different types of media, including media types listed in the present document. The session control procedures for the different media types shall be in accordance with ES 283 003 [20] and the present document, with the following additions: If the ICSI is used the following applies: a) "IPTV" is an IMS communication service and the P-Preferred-Service and P-Asserted-Service headers shall be treated as described in ES 283 003 [20]. The coding of the ICSI value in the P-Preferred-Service and P-Asserted-Service headers shall be as described in clause 5.6.1. b) The UE shall include the g.3gpp.icsi-ref feature tag equal to the ICSI value defined in clause 5.6.1 in the P-Preferred-Service header field in initial requests and responses as described in ES 283 003 [20]. c) The UE shall include the g.3gpp. icsi-ref feature tag equal to the ICSI value defined in clause 5.6.1 in the Contact header field in initial requests and responses as described in ES 283 003 [20]. d) The UE shall include an Accept-Contact header field containing the g.3gpp. icsi-ref feature tag containing the ICSI value as defined in clause 5.6.1 of ES 283 003 [20] in initial requests. If the user requests capabilities other than IPTV, the Accept-Contact header field may contain other feature parameters and feature parameter values, and other Accept-Contact header fields may be added to accurately express user preferences as per ES 283 003 [20]. e) The AS may include the g.3gpp. icsi-ref feature tag equal to the ICSI value defined in clause 5.6.1 in the P-Preferred-Service header field in initial requests and responses as described in ES 283 003 [20]. f) The AS may include the g.3gpp. icsi-ref feature tag equal to the ICSI value defined in clause 5.6.1 in the Contact header field in initial requests and responses as described in ES 283 003 [20]. NOTE: How the user indicates other feature parameters and feature parameter values are outside of the scope of the present document. |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 5.6.3 UE SIP Instance Identifier | The UE shall support the sip instance feature tag at registration as per clauses 4.1 and 4.2 of RFC 5626 [64]. Its format SHALL be identical to the format specified RFC 4122 [65]. The globally unique identifier may be based on the MAC address of the equipment which the UE resides on, or any other appropriate scheme as defined in the RFC. If the UE only supports release 2 functionality the identifier is not required to be supported. The Contact header for UE originating SIP requests shall include the sip instance feature tag in all stand-alone (e.g. SIP REGISTER) and all initial requests (e.g. SIP INVITE) relating to the IPTV procedures. The initial requests not relating to the IPTV procedures (e.g. Instant Messaging) may include the sip instance feature tag. If the originating end, either another UE or SCF, is targeting a SIP request to a specific UE the originating end shall include the Accept-Contact header with the sip,instance feature tag that corresponds to the target UE. This allows targeting a specific user on a specific device. For some services such as session transfer it is not appropriate to use this method for targeting a user on a specific device. In this case GRUU shall be supported by the UE that wishes to use the session transfer service. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 99 |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 5.6.4 UE Support for GRUU | A UE that would like to use session transfer services shall support GRUU. To support GRUU, a UE shall conform to RFC 5627 [59]. The UE shall include the GRUU in its contact information when it establishes an IPTV service that requires session transfer. The usage of GRUU beyond IPTV is outside the scope of the present document. |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 5.7 Synchronization Client (SC) | |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 5.7.1 Procedures for inter-destination media synchronization | |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 5.7.1.1 Synchronization session initiation | Upon a request for an inter-destination media synchronization session, the SC shall initiate this session using modified BC or CoD session initiation or modification procedures, depending on the status of the IPTV service at the moment of the request. NOTE 1: There are various ways to convey which services require inter-destination synchronization. This can be signalled via SSF information (e.g. the EPG/ESG), through a shared service control session, with notifications, recommendations, and others. The SC shall use BC session initiation, described in clause 5.1.3.1, or CoD session initiation, described in clause 5.1.4.2, if no current BC or CoD session is active at the moment of the request for a synchronization session. If the SC is currently in a BC session at the moment of the request for a synchronization session, it shall use a BC session modification, described in clause 5.1.3.2. If the SC is currently in a CoD session at the moment of the request, it shall use a CoD session modification, described in clause 5.1.4.3. The SC shall include the SyncGroupId as part of the session initiation or modification request. If the SyncGroupId is known, it shall be set accordingly. If no SyncGroupId is known, e.g. because the SC is first to setup the inter-destination media synchronization, the SC shall include the parameter but leave it empty by setting the value SyncGroupId=0. This SyncGroupId shall be set as a media level attribute as rtcp-xr parameter Media Stream Correlation Identifier, see annex W. • a=rtcp-xr grp-sync,:sync-group=<SyncGroupId>, see clause W.2. NOTE 2: The ways that an SC can obtain a SyncGroupId are similar to obtaining a phone conference id. For example, one user can request a new SyncGroupId through an off-line process, and share it with other users through an offline process. If the group of users does already have a group identifier, e.g. a phone conference id, they may reuse this identifier. Also, the SSC room identifier can be reused for this purpose. When the SC receives any SIP requests or responses, the SC shall examine the media parameters in the received SDP. It shall be able to deal with the following attributes: • a=ssrc:<ssrc-id> <attribute>:<value> as specified in [46]. • a=rtcp:port [nettype space addrtype space connection-address] as specified in [47]. • a=rtcp-xr: grp-sync,sync-group=<SyncGroupId>, see clause W.2. SyncGroupId is a 32-bit unsigned integer in network byte order and represented in decimal. The value SyncGroupId=0 represents an empty SyncGroupId. The value 4294967295 (2^32-1) is reserved for future use. ssrc-id is a 32-bit unsigned integer in network byte order and represented in decimal. The SC shall keep these values for use in synchronization status information and settings instructions procedures, described in clause 11. Since the SSRC value may change if a SSRC conflict is discovered at the transport level, the SC shall be prepared for this. The SC can be involved in multiple synchronized sessions, as long as the sessions and associated services are disjunctive. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 100 |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 5.7.1.2 Synchronization session termination | When the SC leaves a synchronization session, e.g. because there are no other SCs involved, it shall generate a re-INVITE request or an UPDATE request, depending on the dialogue state, as specified in ES 283 003 [20] for an originating UE. This re-INVITE shall be an exact duplicate of the current session, but omitting the inter-destination media synchronization parameters SyncGroupId, rtcp port and address and SSRC. Ending an existing BC or CoD session shall also end any associated synchronization session. |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 5.8 Media Synchronization Application Server (MSAS) | |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 5.8.1 Procedures for inter-destination media synchronization | |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 5.8.1.1 Synchronization session initiation | Upon a request for session setup or modification, the (session-level) MSAS shall examine the SDP containing the media offer for the presence of a SyncGroupId as a media level attribute. If the MSAS can not retrieve a SyncGroupId parameter form the SDP, no further procedures apply. The MSAS shall assign a media-level MSAS using the SyncGroupId. If the SyncGroupId is present and empty, the MSAS shall assign a new SyncGroupId to the synchronization session and it shall assign a media-level MSAS address and port to be used for this SyncGroupId. If the SyncGroupId is present and is assigned a value, the MSAS shall check if this value is known. If this value is known, the media-level MSAS shall lookup the MSAS address and port to be used for this synchronization group. If this value is not known, the MSAS shall assign store the SyncGroupId and a media- level MSAS address and port to be used for this SyncGroupId. NOTE 1: The session-level MSAS can assign address and port values from different media-level MSASes if necessary. For a BC session setup or modification, the MSAS shall include in its answer to the SC: • The SyncGroupId, using the media level attribute a=rtcp-xr: grp-sync,sync-group=<SyncGroupId>, see clause W.2. • The media-level MSAS address and port to be used, using a=rtcp:port [nettype space addrtype space connection-address] as specified in [47]. SyncGroupId is a 32-bit unsigned integer in network byte order and represented in decimal. The value SyncGroupId=0 represents an empty SyncGroupId. The value 4294967295 (2^32-1) is reserved for future use. NOTE 2: In order to distinguish RTCP reports coming from the media-level MSAS from the multicast media source, they can have different addresses. For CoD session setup or modification, the MSAS shall include these same parameters when forwarding the INVITE or UPDATE to the MCF. The MSAS shall keep track of the members of a synchronization group and the MSAS address and port used for a synchronization group. |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 5.8.1.2 Synchronization session termination | If the MSAS receives a session modification request of a group member of a synchronization session, it shall check this request for the presence of the SyncGroupId. If the SyncGroupId is not present, the MSAS shall remove the SC from the synchronization group. If the MSAS receives a session termination request from a group member of a synchronization session, it shall remove this member from the group. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 101 The MSAS shall keep track of the members of a synchronization group. If the removal of a member leads to the situation that only one member remains in the group, the MSAS should end the synchronization group. The MSAS shall do this by sending a re-INVITE or UPDATE to the remaining SC according to existing network-initiated session modification procedures. In this modification the synchronization parameters SyncGroupId, rtcp-parameters and SSRC are removed. The MSAS will leave all other parameters unchanged. If the last member of a synchronization group leaves the synchronization session, the MSAS shall end the synchronization group. |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 6 Procedures using HTTP for IMS-based IPTV | |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 6.1 User Equipment (UE) | |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 6.1.1 Procedures for service selection | |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 6.1.1.1 Procedure for service personalization | For HTTP-based data retrieval, when sending the HTTP request to the SSFs, the UE may indicate personalization information to enable personalized answer. This shall be done by adding the following HTTP header to the request: • X-3GPP-Intended-Identity to transmit the public identity. • User-agent to transmit UE ID. The authentication shall follow TS 187 003 [10], and may be performed either using the mechanisms specified in TS 133 222 [14] or HTTP Digest access authentication, as described in ES 283 003 [20]. The UE shall implement Transport Layer Security (TLS), as described in RFC 5246 [32]. NOTE: Authentication mechanism is specified in the present document. |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 6.1.1.2 Request of DVB SD&S | In the pull model of unicast delivery of a DVB SD&S data, the HTTP protocol shall be used conforming to TS 102 034 [3], clause 5.4.2.2. The payload id and segments to be retrieved shall be those advertised in the SDF attachment response. |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 6.1.1.3 Request of DVB BCG | |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 6.1.1.3.1 Container-based request | In the pull model of unicast container-based delivery of DVB BCG, data the HTTP protocol shall be used conforming to TS 102 539 [13], clause 4.1.2.2.2. |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 6.1.1.3.2 Query mechanism | In the pull model of unicast query mechanism of DVB BCG data, the HTTP protocol is used to transport SOAP messages. This shall be conforming to TS 102 539 [13], clause 4.2. |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 6.1.1.4 Request of OMA BCAST ESG | In the pull model of unicast delivery of an OMA BCAST ESG, the HTTP protocol shall be used conforming to OMA-TS-BCAST_Service_Guide, [6], clause 5.4.3. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 102 |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 6.1.1.5 Request of service action data | When the UE requests Service Action Data, it shall send HTTP GET request as defined in RFC 2616 [30]. The HTTP URL shall be /tispan/serviceactiondata?id=DomainName&Payload=Type where DomainName and Type are retrieved from the SSF as defined in clause L.1.3. If Payload is set to 0, it means that the UE requests all available Service Action Data. When receiving HTTP 200 OK response, the UE shall evaluate the received XML document as defined in clause 6.1.1.6. |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 6.1.1.5A Request of TV-Anytime Phase 2 XML | In the pull model of unicast delivery of TV-Anytime Phase 2 XML data, the HTTP and SOAP protocols are used to query the SSF. When the UE contacts the SSF, it shall send HTTP POST requests as defined in RFC 2616 [30]. The HTTP URL shall be /tispan/tva2. The HTTP POST request shall be compliant to [48] and carry a SOAP message body to query the SSF as defined in [48]. Response code handling of HTTP and SOAP complies to [48]. If the SOAP message contained in the HTTP response received from the SSF indicates a successful operation, the UE shall examine the contained TV-Anytime Phase 2 Metadata. |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 6.1.1.6 Use of service selection information | The UE shall use parameters received from SSF as defined in clause L.2 for BC session initiation and L3 for CoD session initiation. NOTE: There is no restriction on the UE to use any parameter received from SSF also for other purposes than session initiation, e.g. to present SSF information to the user. Concerning broadcast service selection information, BC service package parameters are defined in Package Discovery record as described in TS 102 034 [3], clause 5.2.6.5 for DVB SD&S and in Purchase Item as described in OMA-TS-BCAST_ServiceGuide [6], clause 5.1.2.6 for OMA ESG.BC service parameters are defined in TS 102 034 [3], clause 5.2.6.2 for DVB SD&S and OMA-TS-BCAST_Service_Guide [6], clause 5.1.2. For each BC service package, when parsing the list of related parameters the UE shall take the following action: - information relates to BC Service Package whom the UE has already an entree. The UE shall update parameters related to the service package (e.g. the list of related BC services); - information relates to BC Service Package not known by the UE. The UE shall store parameters related to the service package. For each BC service, when parsing the list of related parameters the UE shall take the following action: - information relates to a BC service whom the UE has already an entree. If present, the UE shall update stored BC services parameters; - information relates to a BC service not known by the UE: the UE creates a new entree for this BC service. If present, it shall store at least multicast and source address(es), port, transport and codecs information related to the BC service. The UE may store a part of the EPG information covering certain period of time and refresh this information periodically This avoid the UE to contact the SSF every time the user needs to consult the EPG. If the UE is unable to contact any discovered SSF, it shall not delete stored information. Concerning Service Action Data record, the UE shall use n-PVR, CoD and BC data as follows: • if the data type indicates n-PVR service action data, the UE shall use the retrieved data as defined in clause 5.1.7; ETSI ETSI TS 183 063 V3.6.1 (2014-08) 103 • if the data type indicates CoD service action data, the UE may use "CoDoffset" parameter to initiate CoD session related to the indicated Content-Id as defined in clause 7.1.1.2; • if the data type indicates BC service action data, the UE may use "BCServiceId" parameter to indicate the channel the UE intend to join in BC session initiation (see clause 5.1.3.1). |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 6.1.1.7 Query for IPTV Content Marker | When the UE requests IPTV Content Marker, it shall send the HTTP POST request defined in RFC 2616 [30]. The HTTP URL shall contain the domain name of the SSF and end with /tispan/iptvcontentmarker. The HTTP POST request may contain the following parameters to filter the IPTV Content Marker data retrieval on the SSF side: • IPTVInformationDataCommand shall be set to "Retrieval". • IPTVContentMarkerIDs=<IPTVContentMarkerIDs> indicate the list of specific IPTVContentMakerID. Wildcards ('*','?') may be allowed, depending on the capabilities of the query processor implementation. Multiple IPTVContentMarkerIDs shall be separated by space character. • IPTVContentIDs=<IPTVContentIDs> indicate the list of specific IPTVContentID. Wildcards ('*','?') may be allowed, depending on the capabilities of the query processor implementation. Multiple IPTVContentIDs shall be separated by space character. • owneruserIDs=<owneruserIDs> indicate the list of specific owneruserID. Multiple owneruserIDs shall be separated by space character. • maxresults=<MaxResults> indicate the maximum number of the query results. There shall be at most one number of maximum results supplied. When receiving HTTP 200 OK response, the UE shall evaluate the payload in the HTTP response, which contains the IPTV Content Markers as defined in clause 6.3.1.7. The XML document of IPTV Content Markers to indicate a Content Marker Retrieval in HTTP Response is defined in annex V. An SSF technology for IPTV Content Marker handling is described in clauses 5.2.2.3 and L.4. |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 6.1.2 Procedure for service configuration | |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 6.1.2.1 General | The UE implements the role of an XCAP client, as described in RFC 4825 [9], in accordance with the IPTV application usage specified in annex B. The UE shall implement HTTP Digest access authentication, as described in ES 283 003 [20]. The UE shall implement Transport Layer Security (TLS), as described in RFC 5246 [32]. On sending an HTTP request, the UE may indicate the user's identity intended to be used with the SCF or stand-alone XDMS by adding an HTTP X-3GPP-Intended-Identity header (see TS 124 109 [11]) to the outgoing HTTP request. |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 6.1.2.2 Subscription for notification of state changes in XML document | 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 to changes in the XCAP IPTV documents by generating a SUBSCRIBE request in accordance with reference [15] and reference [26]. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 104 |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 6.1.3 Procedures for Unicast Content Download | |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 6.1.3.1 Request of Content Download | Once the UE has received the SIP 200 OK from the MCF, it extract the XML body of the download session description, and sends the HTTP GET request to the URL obtained in download session description, the detail can refer to the single server unicast download as defined in TS 102 034 [3] clause 10.6.3.2. The HTTP "Connection" header shall be set to "Keep-Alive" to require persistent TCP connection. |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 6.2 Service Control Function (SCF) | |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 6.2.1 Procedure for service configuration | |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 6.2.1.1 General | An Application Server implements the role of an XCAP server as described in RFC 4825 [9]. |
df2807db9e02a958d05489c27e83bfa9 | 183 063 | 6.2.1.2 Manipulation acceptance | When the XCAP server receives an HTTP PUT, HTTP GET or HTTP DELETE request for manipulating or fetching a resource list, the XCAP server shall first authenticate the request and then perform authorization. The SCF shall implement HTTP Digest access authentication as described in ES 283 003 [20]. The SCF shall implement Transport Layer Security (TLS) as described in see RFC 5246 [32]. Clause 6.2.1.3 provides more details on the authentication and authorization of HTTP requests. Afterwards the XCAP server shall perform the requested action and generate a response in accordance with RFC 4825 [9] and the IPTV application usage specified in annex B. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.