hash
stringlengths 32
32
| doc_id
stringlengths 7
13
| section
stringlengths 3
121
| content
stringlengths 0
3.82M
|
|---|---|---|---|
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.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
6.2.1.3 Authentication and authorization
|
An Authentication Proxy (AP) may exist between the UE and the SCF, in which case the behaviour of the AP is assumed to conform to TS 183 023 [12]. If an Authentication Proxy (AP) is provided in the path of the HTTP request, then the SCF receives an HTTP request from a trusted source (the AP) and contains an HTTP X-3GPP-Asserted-Identity header (TS 124 109 [11]) that includes an asserted identity of the user. In this case the SCF does not need to authenticate the user, but just provide authorization to access the requested resource. If an HTTP X-3GPP-Asserted-Identity header (TS 124 109 [11]) is not present in the HTTP request or if the request is received from a non-trusted source, then the SCF needs to authenticate the user prior to providing authorization to the XCAP resource by applying the following procedures. On receiving an HTTP request that does not contain an Authorization header the SCF shall: a) challenge the user by generating a 401 Unauthorized response that contains the proper Digest authentication parameters (e.g. realm), according to ES 283 003 [20]. Provisioning of credentials to authenticate the user is outside the scope of the present document; and b) forward the 401 Unauthorized response to the sender of the HTTP request. On receiving an HTTP request that contains an Authorization header, the SCF shall: a) apply the authentication procedures defined in ES 283 003 [20]; and b) authorize or deny authorization depending on the authenticated identity. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 105
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
6.2.1.4 Subscription acceptance and notification of state changes in XML document
|
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 response to the SUBSCRIBE request and generate notifications in accordance with references [15] and [26].
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
6.3 Service Selection Function (SSF)
| |
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
6.3.1 Procedure for service selection
|
6.3.1.1 Authentication and authorization for personalized service selection information In case of service selection personalization the SCF shall authenticate the user. 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 SSF shall implement Transport Layer Security (TLS) as described in RFC 5246 [32]. An Authentication Proxy (AP) may exist between the UE and the SSF in which case the behaviour of the AP is assumed to conform to TS 183 023 [12] and TS 187 003 [10]. If an Authentication Proxy (AP) is provided in the path of the HTTP request, then the SSF receives an HTTP request from a trusted source (the AP) and the request contains an HTTP X-3GPP-Asserted-Identity header (TS 124 109 [11]) that includes an asserted identity of the user. In this case the SSF does not need to authenticate the user, but just provide authorization to access the requested resource. If an HTTP X-3GPP-Asserted-Identity header (TS 124 109 [11]) is not present in the HTTP request or if the request is received from a non-trusted source, then the SSF needs to authenticate the user prior to providing personalize information by applying the following procedures: On receiving an HTTP request that does not contain an Authorization header the SSF shall: a) challenge the user by generating a 401 Unauthorized response that contains the proper Digest authentication parameters (e.g. realm), according to ES 283 003 [20]. Provisioning of credentials to authenticate the user is outside the scope of the present document; and b) forward the 401 Unauthorized response to the sender of the HTTP request. On receiving an HTTP request that contains an Authorization header, the SSF shall: a) apply the authentication procedures defined in ES 283 003 [20]; and b) authorize or deny authorization depending on the authenticated identity.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
6.3.1.2 Procedure for service personalization
|
If personalization headers are present in the query from the UE, the SSF shall extract the UE ID and/or the public user identity information that is present in the query to customize/personalize the service information that is returned in the query response. The SSF shall use the public user identity that is specified in the X-3GPP-Intended-Identity header or the X-3GPP-Asserted-Identity header (as defined in clause 6.3.1.1) if an authentication proxy is used to fetch the corresponding IPTV user profile associated with the user. For instance, the Parental Control level (if present) should be used to remove unsuitable elements from the COD listings that are returned to the UE. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 106 The SSF shall use the public user identity that is specified in the X-3GPP-Intended-Identity header or the X-3GPP-Asserted-Identity header (as defined in clause 6.3.1.1) if an authentication proxy is used and the UE-ID that is specified in the user-agent header to fetch the corresponding UE profile information from the IPTV user profile associated with the specified IPTV user. If present, the SSF should use the UE capabilities to return back service information matching the capabilities supported by the specific UE. For example, the UE Capabilities information such as supported video frame rates and supported encodings can be used to identify the decoding and display capabilities of the UE and can be used to return back only SD content listings to UE that has no HD support. The fetching of IPTV user profile shall be done towards a dedicated database or UPSF within a service provider domain as specified in TS 182 027 [2], clause 7.2.4. NOTE: The support of personalization for multiple service providers from a single UPSF as well as the interface between the SSF and the dedicated database is out of scope of the present document.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
6.3.1.3 Delivery of DVB SD&S
|
In case an SSF receives an HTTP request for unicast delivery of DVB SD&S data it shall act as a so-called SD&S SSF. When the SD&S SSF receives an HTTP GET request, if personalization headers are presents it shall use those headers in order to build a personalized response. The SD&S SSF shall send an HTTP response conforming to TS 102 034 [3], clause 5.4.2. The body of the HTTP response shall contain an XML document with the appropriate SD&S offering record, conforming to TS 102 034 [3], clause 5.2.6. Available Offering records are: • The Broadcast Discovery record (clause 5.2.6.2) is a list of IPTV services. • The Package Discovery record (clause 5.2.6.5) is a list of packages, a package being a list of pointers to services that are advertised in the broadcast discovery record. • The BCG Discovery record (clause 5.2.6.6) is a list of BCGs, and for each of them the location of the BCG SSF(s) to connect to the BCG server(s) (DVB multicast and unicast modes are available, plus a specific Query mechanism). - The type of TV-Anytime content carried in the Payload shall be advertised by the SSF, conforming to TS 102 539 [13], clause 4.1.2.1 table 2. - When present, the DVBSTP@Source or the HTTP@Location of the TransportMode parameter in BCG Discovery Record represent respectively the multicast address (when service selection data are multicasted) and the URI (when service selection is done through HTTP) used by the BCG SSF. - When using the DVB pull mode without SOAP, the SD&S SSF shall include the Segment information.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
6.3.1.4 Delivery of DVB BCG
|
In case an SSF receives an HTTP request for unicast container-based delivery of DVB BCG data it shall act as a so-called BCG SSF.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
6.3.1.4.1 Container-based delivery
|
When the BCG SSF receives an HTTP GET request, if personalization headers are presents it shall use those headers in order to build a personalized response. The BCG SSF shall send an HTTP response conforming to TS 102 539 [13], clause 4.1.2. The body of the HTTP response shall contain an XML document with the appropriate BCG data, conforming to TS 102 539 [13]. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 107
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
6.3.1.4.2 Query response
|
When the BCG SSF receives a BCG Query SOAP message, if personalization headers are present it shall use those headers in order to build a personalized response. The BCG SSF shall send a SOAP response conforming to TS 102 539 [13], clause 4.2.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
6.3.1.5 Delivery of OMA BCAST ESG
|
In case an SSF receives an HTTP request for unicast delivery of an OMA BCAST ESG it shall act as a so-called ESG SSF. The procedure for retrieving OMA BCAST service selection information is employed to retrieve one or more Service Guide Delivery Descriptors (SGDD) and/or Service Guide Delivery Units (SGDU). The SGDD describes service level information as well as access information to the Service Guide fragments. The SGDU is the transport-independent network structure for encapsulating Service Guide fragments. When the ESG SSF receives a HTTP POST request, if personalization headers are presents (in the form of key-value pairs) it shall use those headers in order to build a personalized response. For instance, the ESG SSF may use the provided user identity to retrieve the associated Parental Control Level in the IPTV user profile. This Parental Control Level would then be used to remove non suitable elements from the ESG data that are sent back. The provided user identity may also be used to retrieve a personalized ESG using the method in OMA-TS-BCAST_Service_Guide-V1_0 [6], clause 5.4.3.3. The ESG SSF shall send a HTTP response conforming to OMA-TS-BCAST_Service_Guide-V1_0 [6], clause 5.4.3.1. The body of the HTTP response shall contain an XML document with SGResponse data, conforming to OMA-TS-BCAST_Service_Guide-V1_0, clause 5.4.3.1.1 [6].
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
6.3.1.6 Delivery of Service Action Data
|
When receiving HTTP GET request for service action data, the SSF shall evaluate "Payload" parameter in the HTTP query and respond with the appropriate XML document as defined in annex D. If the "Payload" parameter indicates BC service action Data, the message body carries the following parameters: • IPTVActionDataCommand shall be set to "Notify". • Notify shall be set to "IPTVBcActionData". • BCServiceId is set to the value of the channel previously reported by the UE in BC session information procedure as defined in clause 5.1.3.5. • If available, the following parameters shall be present: ProgrammeID, Bookmark, BookmarkExpiryTime. It means that a record exists for such a bookmark and that the UE can use it as an N-PVR content. If the "Payload" parameter indicates CoD service action Data, the message body carries the following parameters: • IPTVActionDataCommand shall be set to "Notify". • Notify shall be set to "IPTVCodActionData". • For each content identified by a CoDId: - CoDDelivery status shall be present and set to the value stored for that content; - CoDOffset shall be present and set to the value stored for that content. If the "Payload" parameter indicates N-PVR service action Data, the message body carries the following parameters: • IPTVActionDataCommand shall be set to "Notify". • Notify shall be set to "IPTVNpvrActionData". • For each N-PVR content identified by a NPVRContentId, the following parameters shall be present if available: BCServiceId, RecordStartDate, RecordEnDate, RecordStatus, RecordOffset and RecordExpiryTime shall be present if available. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 108 If the "Payload" parameter is set to "ALL", the SSF shall send all available Service Action Data as defined above. If no information is available for the requested type, the SSF shall answer with an HTTP 404 error code.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
6.3.1.7 Delivery of IPTV Content Marker
|
For fine grained access control, The SSF shall check two parameters: • IPTVContentMarkerSourceUser is generated by other users' IPTVContentMarkerAuthorizedViewUser parameter and indicates that the requesting user can share which users' IPTV Content Marker. • ForbiddenViewUser can be set to the particular IPTV Content Marker by the owner when the owner does not want to share this IPTV Content Marker with specific users included in IPTVContentMarkerAuthorizedViewUser parameter. When receiving HTTP request for IPTV Content Markers with the IPTVInformationDataCommand parameter set to "Retrieval", the SSF shall extract the User ID and lookup the IPTV Content Marker data associated to that User ID. It shall also examine the IPTV User Profile associated to that User ID in order to look up the IPTVContentMarkerSourceUser parameters of the BC, CoD and PVR profiles. The SSF shall attempt to retrieve the IPTV Content Marker data associated with these other users' User ID only if the other users' IPTVContentMarkerAuthorizedViewUser parameters of the relevant IPTV service profile indicate the requesting User ID. Additionally, the SSF shall check for each retrieved IPTV Content Marker if the parameter ForbiddenViewUser is present. If this ForbiddenViewUser parameter is present, the SSF shall check whether the requesting User ID is included in this parameter. If that User ID exists in ForbiddenViewUser, the SSF shall remove that particular IPTV Content Marker data from the response data set. After all ForbiddenViewUser parameters of all IPTV Content Marker data have been checked, the SSF shall respond with the IPTV Content Markers remaining in the response data set. The XML document of IPTV Content Markers to indicate a Content Marker Retrieval in HTTP Response is defined in annex V. Upon receiving an HTTP based IPTVContentMaker retrieval request, the SSF shall send an HTTP response. The body of the HTTP response shall contain an XML document defined in clause 6.1.1.7 and contain only data that matches the filter parameters passed in the HTTP request.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
6.3.1.8 Delivery of TV-Anytime Phase 2 XML
|
When the TV-Anytime Phase 2 based SSF receives an HTTP POST request, if personalization headers are present it shall use those headers in order to build a personalized response. For instance, the provided IPTV user profile may be used to retrieve the personalized EPG data. Further, the SSF shall examine the SOAP message carried in the HTTP request and process it according to [48]. It shall process the query, and build a SOAP response compliant with [48]. The SSF shall send that SOAP response to the UE in a HTTP response compliant with [48].
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
6.4 Stand-Alone XMDS
| |
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
6.4.1 Procedure for service configuration
| |
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
6.4.1.1 General
|
The stand-alone XDMS implements the role of an XCAP server as described in RFC 4825 [9].
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
6.4.1.2 Manipulation acceptance
|
The behaviour of a stand-alone XDMS server with regards to XCAP is identical to the behaviour of an SCF as described in clause 6.2.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
6.4.1.3 Authentication and authorization
|
The behaviour of a stand-alone XDMS server with regards to XCAP is identical to the behaviour of an SCF as described in clause 6.2. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 109
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
6.4.1.4 Subscription acceptance and notification of state changes in XML document
|
A stand-alone XDMS does not support subscriptions to profile changes. Subscriptions to profile changes are directed to the SCF acting as a front-end to the XDMS.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
6.5 Media Function (MF)
| |
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
6.5.1 Procedures for Unicast Content Download
| |
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
6.5.1.1 Response of Content Download
|
Once the MF has received the HTTP GET request from the UE, it should return HTTP response with the content file corresponding to the URL obtained in the received HTTP GET. Also the HTTP "Connection" header shall be set to "Keep-Alive" to indicate it is a persistent TCP connection. The detail can also refer to the single server unicast download as defined in TS 102 034[3] clause 10.6.3.2. NOTE: The Xd interfaces are used for the UE to download the content. And the MCF and MDF are treated as a whole in release 3.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
7 Procedures using RTSP for IMS-based IPTV
|
This clause specifies how the playback control, e.g. in the CoD Service, through RTSP is achieved. Two approaches have been identified: • "Method 1": clauses 7.1.1 and 7.2.1 describe a protocol which uses a subset of the RTSP methods defined in RFC 2326 [8], interpreting SIP INVITE and SIP BYE as triggers for RTSP Session Initiation and termination. • "Method 2": clauses 7.1.2 and 7.2.2 describe a protocol which follows RFC 2326 [8].
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
7.1 User Equipment (UE)
| |
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
7.1.1 Procedures for RTSP playback control (Method 1)
| |
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
7.1.1.1 Introduction
|
The UE shall support the following RTSP methods for RTSP playback control: • PLAY (UE to MCF). • PAUSE (UE to MCF). • GET_PARAMETER (UE to MCF). • SET_PARAMETER (UE to MCF). • ANNOUNCE (MCF to UE). • OPTION (UE to MCF). NOTE: The UE is not required to use OPTION method since all the specified methods are mandatory. The OPTION method is included simply to allow for future compatibility and easier introduction of new optional methods. The methods shall use the same session id as specified in the SDP h-session attribute. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 110
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
7.1.1.2 Media playback initiation procedure
|
Upon a request to start playback the UE shall send an RTSP PLAY message to the MCF using the h-uri attribute received in the SDP. If a domain address is used in the RTSP URL the UE shall not perform DNS lookup. The IP header for the RTSP PLAY message shall be set to the IP address from the connection line ("c=") in the SDP answer and the port from the media line ("m="). NOTE: The UE does not perform DNS lookup in order to avoid misaligning the information conveyed in the SDP. The RTSP fields in the RTSP PLAY message shall be filled as follows: • The RTSP URL shall be set to the value retrieved from the SDP h-uri attribute in the case of an absolute URI. If the value of h-url is a relative URI that is in the form of a media path, then the RTSP absolute URL is constructed by the UE using the SDP IPAddress (from c-line) and port (from m-line) as the base followed by h-uri value for the media path. (e.g. rtsp://10.5.1.72:22554/TV3/823527). • If the h-offset attribute is present in the SDP, then the Range parameter in the first RTSP PLAY message shall be included and set to the value retrieved from this SDP h-offset attribute. Else: - the Range parameter may be included and set to the value retrieved in the CoD SAD from the SSF in case the user wants to resume a pending CoD at the time it was previously stopped. • If Range parameter is not sent by the UE, the stream will play from the beginning. (e.g. Range: npt=<OFFSET>-).
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
7.1.1.3 Media playback modification procedure
|
Upon a request to modify playback the UE shall send an RTSP PLAY message with a request to modify the position, speed and/or direction of playback. The UE changes the direction and/or speed of playback by including a Scale header or change the position of playback by including a Range header. • Scale header is set as follows: - 1 indicates normal play. - If not 1, the value corresponds to the rate with respect to normal viewing rate. - A negative value indicates reverse direction. If the request is to pause playback, the UE shall send an RTSP PAUSE message.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
7.1.1.4 Media playback information retrieval and setting procedure
|
Upon a request to retrieve playback information the UE shall send an RTSP GET_PARAMETER message. The UE shall create a message with a content type: text/parameters. The parameters the UE wants to retrieve shall be set in the body, one parameter per line.The UE may retrieve the following information: • position: - The position in the media in seconds. • scales: - The allowed scales that can be used in the PLAY request. • duration: - The total duration in seconds of the media to be played. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 111 If a GET_PARAMETER request contains other parameters than specified here, the MCF shall ignore these parameters. In case the request contains only unspecified parameters the request shall be considered as a request with an empty body. An empty body is allowed for RTSP keep alive. The UE may also set the position parameter (ex. to jump to a bookmark position within a video) by sending the RTSP SET_PARAMETER message. Any other parameter that is used in SET_PARAMETER request will be rejected by the MCF.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
7.1.1.5 Handling of media events
|
Upon the reception of the RTSP ANNOUNCE with the beginning-of-stream, the end-of-stream or the transition indication the UE may take relevant actions to handle the event (e.g. Terminating session, rewinding the media stream, etc.). The UE shall respond with a RTSP 200 OK. For BC sessions with trick-play, if the UE receives an RTSP ANNOUNCE request with an end-of-stream indication, the UE may initiate a session modification procedure in order to go back to a normal BC session in multicast mode or may alternatively take other actions (e.g. rewind, pause, terminate session, etc.). If the UE receives an RTSP ANNOUNCE request with a transition indication, the UE may send an RTSP GET_PARAMETER with parameter scales in order to have the latest valid scale values. If the UE does not understand any of the headers or the notice-code value in the ANNOUNCE request, it simply shall ignore the request.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
7.1.2 Procedure for content control (Method 2)
| |
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
7.1.2.1 Introduction
|
After CoD session setup, RTSP as defined in RFC 2326 [8] is used to control media delivery. It includes media setup, media control and media teardown. RTSP header fields shall conform to TS 102 034 [3], clause 6.3.2. The UE shall support the following RTSP methods: • DESCRIBE (UE to MCF). • SETUP (UE to MCF). • PLAY (UE to MCF). • PAUSE (UE to MCF). • TEARDOWN (UE to MCF). • ANNOUNCE (MCF to UE). For transport parameters, the ones conveyed over SIP shall always take precedence over the ones conveyed over RTSP.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
7.1.2.2 Media description procedure
|
If UE did not get content delivery description information (from the SSF or from the SCF/MCF during the SIP session initiation), it shall request description of the media via the DESCRIBE message. The RTSP URL to send the DESCRIBE message to is retrieved from the SSF data or from the MCF during the SIP session initiation. If a domain address is used in the RTSP URL the UE shall not perform DNS lookup. The IP header for the RTSP DESCRIBE message shall be set to the IP address from the connection line ("c=") in the SDP answer and the port from the media line ("m="). • The RTSP URL shall be set to the value retrieved from the SDP h-uri attribute in the case of an absolute URI. If the value of h-url is a relative URI that is in the form of a media path, then the RTSP absolute URL is constructed by the UE using the SDP IPAddress (from c-line) and port (from m-line) as the base followed by h-uri value for the media path. (e.g. rtsp://10.5.1.72:22554/TV3/823527). ETSI ETSI TS 183 063 V3.6.1 (2014-08) 112 NOTE: The UE does not perform DNS lookup in order to avoid misaligning the information conveyed in the SDP. The UE shall include an Accept header in the request with "application/sdp" and "text/xml".
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
7.1.2.3 Media setup procedure
|
On sending a SETUP request, the UE shall populate the header fields as follows: - RTSP URL header shall be set to the a=control parameter if present in the answer to the DESCRIBE sent by the MCF. If not present, RTSP URL shall be set to the corresponding media RTSP URL which has been obtained from the SSF data, or from the CoD session initiation. If a domain address is used in the RTSP URL the UE shall not perform DNS lookup. The IP header for the RTSP SETUP message shall be set to the IP address from the connection line ("c=") in the SDP answer and the port from the media line ("m="). - CSeq header shall be generated by the UE. On receiving a SIP 200 OK response to the SETUP request, the UE shall retrieve and store the Session header for issuing the PLAY request later.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
7.1.2.4 Media playback initiation procedure
|
After SETUP request has been acknowledged as successful, UE shall start the playback of the content by sending an RTSP PLAY request. The UE shall populate the header fields as follows: - RTSP URL header shall be set to the a=control parameter if present in the answer to the DESCRIBE sent by the MCF. If not present, RTSP URL shall be set to the corresponding media RTSP URL which has been obtained from the SSF data, or from the CoD session initiation. If a domain address is used in the RTSP URL the UE shall not perform DNS lookup. The IP header for the RTSP SETUP message shall be set to the IP address from the connection line ("c=") in the SDP answer and the port from the media line ("m="). - CSeq header shall be generated by the UE. - Session header shall be set to the same value as that in the SETUP request. - If Range header was present in the DESCRIBE response, then the UE shall use it. Otherwise, the UE may include a Range header. If Range header is not sent by the UE, the stream will play from the beginning.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
7.1.2.5 Media playback modification procedure
|
Upon a request to modify playback the UE shall send an RTSP PLAY message with a request to modify the position, speed and/or direction of playback. The UE changes the direction and/or speed of playback by including a Scale header or change the position of playback by including a Range header. The UE shall populate the header fields conforming to clause 7.1.2.4 with the following additions: • Range header is optional. • Scale header is optional: it is set as follows: - 1 indicates normal play. - If not 1, the value corresponds to the rate with respect to normal viewing rate. - A negative value indicates reverse direction. If the request is to pause playback, the UE shall send an RTSP PAUSE message. On sending a PAUSE request, the UE shall populate the header fields as follows: - RTSP URL header shall be set to the same value as that in the previous PLAY request. - CSeq header shall be set to the same value as that in the previous PLAY request. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 113 - Session header shall be set to the same value as that in the PLAY request.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
7.1.2.6 Media teardown procedure
|
On sending TEARDOWN request, the UE shall populate the header fields as follows: - RTSP URL header shall be set to the a=control parameter if present in the answer to the DESCRIBE sent by the MCF. If not present, RTSP URL shall be set to the corresponding media RTSP URL which has been obtained from the SSF data, or from the CoD session initiation. If a domain address is used in the RTSP URL the UE shall not perform DNS lookup. The IP header for the RTSP SETUP message shall be set to the IP address from the connection line ("c=") in the SDP answer and the port from the media line ("m="). - CSeq header shall be generated by the UE. - Session header shall be set to the same value as that in the SETUP request.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
7.1.2.7 Handling of media events
|
Upon the reception of the RTSP ANNOUNCE with the beginning-of-stream, the end-of-stream or the transition indication the UE may take relevant actions to handle the event (e.g. Terminating session, rewinding the media stream etc.). The UE shall respond with a RTSP 200 OK. For BC sessions with trick-play, if the UE receives an RTSP ANNOUNCE request with an end-of-stream indication, the UE may initiate a session modification procedure in order to go back to a normal BC session in multicast mode or may alternatively take other actions (e.g. rewind, pause, terminate session, etc.). If the UE receives an RTSP ANNOUNCE request with a transition indication, the UE may send a RTSP GET_PARAMETER with parameter scales in order to have the latest valid scale values. If the UE does not understand any of the headers or the notice-code value in the ANNOUNCE request, it simply shall ignore the request.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
7.1.3 Procedures for Content Switch within a CoD Contentlist
|
Upon a request for a content switch the UE shall send an RTSP PLAY message to the MCF using the contentlist information received in the SDP. If the UE confirms that the UE and the media server support the "3gpp-switch" feature in the session initiation procedure as described in clauses 5.1.16.1 and 5.4.11.1, the UE shall populate the header fields as follows: • RTSP URL header shall be set to the value received from MF during CoD session initiation. • Switch-Stream header shall be set by UE: - "old-stream" attribute shall be set to RTSP URL of the media stream that is current watchingly being watched. - "new-stream" attribute shall be set to RTSP URL of the new media stream that user wants to switch to. EXAMPLE: Switch-Stream:old= rtsp://10.5.1.72:22554/TV3/823527; new= rtsp://10.5.1.72:22554/TV3/823528). NOTE: The syntax of Switch-Stream header is specified in TS 26 234 [49], clause 5.5.4.2. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 114
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
7.2 Media Control Function (MCF)
| |
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
7.2.1 Procedures for RTSP playback control (Method 1)
| |
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
7.2.1.1 Introduction
|
The MCF shall support the following RTSP methods for RTSP playback control: • PLAY (UE to MCF). • PAUSE (UE to MCF). • GET_PARAMETER (UE to MCF). • SET_PARAMETER (UE to MCF). • ANNOUNCE (MCF to UE). • OPTION (UE to MCF). All other methods that the MCF does not support will result in "405 Method not allowed" reply from the MCF. The methods shall use the same session id as specified in the SDP h-session attribute.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
7.2.1.2 Media Playback Initiation Procedure
|
Upon successful RTSP PLAY request the MCF responds with a RTSP 200 OK message except for the cases as follows: • If the requested content is not ready for playing, the MCF shall reply with an RTSP error code 404 Not Found. The contents of the RTSP 200 OK response shall be as follows: • CSeq shall be set to the same value as that in the request. • Date header may be generated by the MCF. It represents the date and time at which the message was originated. • RTP-Info header may be generated by the MCF when the media packets are transported over the RTP layer. It indicates the RTP-specific parameters. The parameters url and rtptime shall be present. The parameter seq is recommended to be present. For non-MPEG2TS streams, the UE uses the parameter rtptime to calculate the mapping of RTP timestamp to NPT, and the UE may also use the parameter rtptime for inter-media synchronization.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
7.2.1.3 Media playback modification procedure
|
Upon successful RTSP PLAY or PAUSE request the MCF responds with a RTSP 200 OK message. The contents of the RTSP 200 OK response shall be as follows: - CSeq shall be set to the same value as that in the request. - Date header may be generated by the MCF. It represents the date and time at which the message was originated. - RTP-Info header may be generated by the MCF when the media packets are transported over the RTP layer. It indicates the RTP-specific parameters. The parameters url and rtptime shall be present. The parameter seq is recommended to be present. For non-MPEG2TS streams, the UE uses the parameter rtptime to calculate the mapping of RTP timestamp to NPT, and the UE may also use the parameter rtptime for inter-media synchronization. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 115
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
7.2.1.4 Media playback information retrieval and setting procedure
|
Upon successful RTSP GET_PARAMETER or SET_PARAMETER request the MCF responds with a RTSP 200 OK message with the requested values or with the successful setting of a parameter.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
7.2.1.5 Handling of media events
|
Upon receipt of the beginning-of-stream or the end-of-stream indication from MDF, MCF may send an RTSP ANNOUNCE to the UE with an indication that the beginning-of-stream or the end-of-stream has been reached. Upon reception of the indication from the MDF that there is a transition in the media characteristics, MCF shall send a RTSP ANNOUNCE to the UE with an indication that transition has occurred. The transition of the media characteristics relate to the change in the available playback scales or the current speed of playback. The transition occurs when MDF has a playlist which contains content with playback restrictions. The Range header shall be included to indicate the current position where the transition has taken place. The Scale header shall be included if the value has changed from a previously scale value. The "Notice" header shall be included with the notice code value set to "2104 Start-of-Stream Reached", "2101 End-of- Stream Reached" or "2103 Transition". NOTE: The header and code are based draft-stiemerling-rtsp-announce-01 [i.10]. The use of other event types is outside the scope of the present document.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
7.2.2 Procedure for content control (Method 2)
|
The MCF shall act as a media server as defined in RFC 2326 [8]. RTSP header fields shall conform to TS 102 034 [3], clause 6.3.2. The MCF shall not redirect the RTSP methods using either the REDIRECT method or Redirection status code (3xx). NOTE: It is recommended that the MCF does not perform redirection to avoid misaligning the information conveyed in the SDP. The problem occurs if the redirected URL differs from the ones conveyed in the SDP connection and media line is that SIP is used for opening proxies and firewalls for the content control and the content delivery paths. For transport parameters, the ones conveyed over SIP shall always take precedence over the ones conveyed over RTSP.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
7.2.2.1 Introduction
|
After CoD session setup, RTSP as defined in RFC 2326 [8] is used to control media delivery. It includes media setup, media control and media teardown. RTSP header fields shall conform to TS 102 034 [3], clause 6.3.2. The MCF shall support the following RTSP methods: • DESCRIBE (UE to MCF). • SETUP (UE to MCF). • PLAY (UE to MCF). • PAUSE (UE to MCF). • TEARDOWN (UE to MCF). • ANNOUNCE (MCF to UE). All other methods that the MCF does not support will result in "405 Method not allowed" reply from the MCF.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
7.2.2.2 Media description procedure
|
Upon successful RTSP DESCRIBE request the MCF responds with a RTSP 200 OK message. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 116 The DESCRIBE response sent by the MCF shall have: • Content-type header set to "application/sdp"; or • Content-type header set to "text/xml" and Content-encoding set to "utf8", conforming to TS 102 034 [3], clause 6.3.1.2.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
7.2.2.3 Media setup procedure
|
Upon successful RTSP SETUP request the MCF responds with a RTSP 200 OK message. The contents of 200 OK response shall be as follows: - CSeq shall be set to the same value as that in the SETUP request. - Date header may be generated by the MCF. It represents the date and time at which the message was originated. - Session header is generated by the MCF. - Transport header contains the transport parameters selected by the MCF.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
7.2.2.4 Media playback initiationcontrol procedure
|
Upon successful RTSP PLAY request the MCF responds with a RTSP 200 OK message. The contents of the RTSP 200 OK response shall be as follows: - CSeq shall be set to the same value as that in the request. - Date header may be generated by the MCF. It represents the date and time at which the message was originated. - RTP-Info header may be generated by the MCF when the media packets are transported over the RTP layer. It indicates the RTP-specific parameters. The parameters url and rtptime shall be present. The parameter seq is recommended to be present. For non-MPEG2TS streams, the UE uses the parameter rtptime to calculate the mapping of RTP timestamp to NPT, and the UE may also use the parameter rtptime for inter-media synchronization.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
7.2.2.5 Media playback modification procedure
|
Upon successful RTSP control (PLAY, PAUSE) request the MCF responds with a RTSP 200 OK message. The contents of the RTSP 200 OK response shall be as follows: - CSeq shall be set to the same value as that in the request. - Date header may be generated by the MCF. It represents the date and time at which the message was originated. - RTP-Info header may be generated by the MCF when the media packets are transported over the RTP layer. It indicates the RTP-specific parameters. The parameters url and rtptime shall be present. The parameter seq is recommended to be present. For non-MPEG2TS streams, the UE uses the parameter rtptime to calculate the mapping of RTP timestamp to NPT, and the UE may also use the parameter rtptime for inter-media synchronization.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
7.2.2.6 Media teardown procedure
|
Upon successful RTSP TEARDOWN request the MCF responds with a RTSP 200 OK message. The contents of 200 OK response shall be as follows: - CSeq shall be set to the same value as that in the TEARDOWN request. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 117
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
7.2.2.7 Handling of media events
|
Upon receipt of the beginning-of-stream or the end-of-stream indication from MDF, MCF shall send an RTSP ANNOUNCE to the UE with an indication that the beginning-of-stream or the end-of-stream has been reached. Upon reception of the indication from the MDF that there is a transition in the media characteristics, MCF shall may send a RTSP ANNOUNCE to the UE with an indication that transition has occurred. The transition of the media characteristics relate to the change in the available playback scales or the current speed of playback. The transition occurs when MDF has a playlist which contains content with playback restrictions. The Range header shall be included to indicate the current position where the transition has taken place. The Scale header shall be included if the value has changed from a previously scale value. The "Notice" header shall be included with the notice code value set to "2104 Start-of-Stream Reached","2101 End-of-Stream Reached" or "2103 Transition". NOTE: The header and code are based draft-stiemerling-rtsp-announce-01 [i.10]. The use of other event types is outside scope of release 3.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
7.2.3 Procedures for restricted trick play
|
On receiving a request from the user to control the playback (e.g. RTSP PLAY, PAUSE, etc.) which specified in clause 7.1, the MCF shall examine the request to see whether the playback operation is permitted based on the restricted trick play policy. If the requested playback operation is forbidden by the policy, for example, the user tries to fast forward when an advertisement is showing, the MCF shall disable the request and respond with a RTSP "405 Method Not Allowed" message.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
7.2.4 Procedures for inter-destination media synchronization
|
If RTSP method 2 is used, before the MCF sends a reply to the SC to a DESCRIBE method it shall use the assigned SSRC value to the media stream (see clause 5.4.10.1). NOTE: The text in clauses 7.1.2.1 and 7.1.2.2 regarding media description procedure applies here. The MCF shall include in the SDP it sends to the SC: • 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. If an SSRC conflict occurs at the transport level, and the MF has to assign a new SSRC value, the MCF shall send an RTSP announce to the SC containing the new SSRC value as part of the modified SDP.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
7.2.5 Procedures for Content Switch within a CoD Contentlist
|
Upon successful RTSP PLAY request with a Switch-Stream header the MCF responds with a RTSP 200 OK message and replace the old media stream with the new media stream except for the cases as follows: • If the requested content is not ready for playing, the MCF shall reply with an RTSP error code 404 Not Found. • If the requested new media stream is not in the playlist, the MCF shall reply with an RTSP error code 406 Not Acceptable The contents of the RTSP 200 OK response shall be as described in clause 7.2.1.2 for method 1 or clause 7.2.2.4 for method 2.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
7.2.6 Procedure for PlayBack following Session Transfer
|
Following a successful session transfer, the transferee UE can use the IPTV Content Marker received during the session transfer procedures to view the content using any of the methods in clauses 7.2. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 118
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
7.2.7 Playlist handling when end of stream is reached
|
For CoD and a UE-owned play list (CoD content list), when a content that is currently being streamed terminates, the MCF sends to the UE an RTSP ANNOUNCE message with an indication as per [i.9] to indicate End-of Stream reached, 2101.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
7.2.8 Procedures for trick play during playlist
|
Upon reception of an RTSP trick play while streaming a content belonging to a playlist, the MCF translates/maps incoming RTSP commands to the current IPTV content item played out.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
7.3 Synchronization Client (SC)
| |
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
7.3.1 Procedures for inter-destination media synchronization
|
If RTSP method 2 is used, i.e. because the SC did not receive the synchronization information from the MCF via the procedure in clause 5.4.10.1, the SC shall check the SDP for the SSRC identifier and rtcp-parameter containing the MSAS address. It shall use the RTCP address and port number given in the SDP using the rtcp-attribute and not an RTCP port number specified in the reply to the RTSP SETUP message. When an SSRC conflict occurs at the transport level, the SC shall be prepared to receive an RTSP ANNOUNCE containing a new SSRC value.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
8 Procedures using IGMP/MLD for IMS-based IPTV
| |
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
8.1 User Equipment (UE)
|
If IPv4 is used for the transport, the UE shall support IGMPv3 as described in RFC 3376 [28]. If IPv6 is used for the transport, the UE shall support MLDv2 as described in RFC 3810 [29]. Backward compatibility rules between the UE and the Transport Function have to be done conforming to RFC 3376 [28], clause 7 and RFC 3810 [29], clause 8.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
8.1.1 Procedure for service selection
| |
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
8.1.1.1 Procedure to start receiving service selection information
|
When the UE wishes to receive service selection information from the SSF in multicast mode, it shall send an IGMPv3 unsolicited Membership Report or a MLDv2 Multicast Listener Report Message to the Access Node as specified in RFC 3376 [28] and RFC 3810 [29]. The IGMPv3/MLDv2 request shall be populated as follows: • the type shall be set to 0x22 "v3 Membership Report" for IGMPv3 or to 143 "Version 2 Multicast Listener Report" for MLDv2; • for IGMPv3, the value of "Number of Group Records" is set to the number of group records present in the request. For MLDv2, the value of "Number of Multicast Address Records" is set to the number of multicast address records present in the request; • the Group/Multicast Address Records shall be set as follows: - "Multicast Address" shall be set to the "Push@MulticastAddress" as specified in the XML document sent by the SDF. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 119 - If one or more "Push@SourceAddress" elements are present in the XML document sent by the SDF, then: "Record Type" shall be set to ALLOW_NEW_SOURCES with INCLUDE filter mode: - the value of "Number of Sources" is set to the number of source addresses present in the group record, i.e. number of "Push@SourceAddress" elements; - the "Source Address" fields shall be set to the "Push@SourceAddress" elements. - When no "Push@SourceAddress" element is present in the XML document sent by the SDF (i.e. source address filtering is not used): "Record Type" shall be set to CHANGE_TO_EXCLUDE_MODE with no "Source Address" fields. The case when the UE has to use IGMP v2 for compatibility reason (i.e. the network does not support IGMPv3), the UE shall send v2 Membership report, set as follows: - the type shall be set to 0x16 "v2 Membership Report"; - the Max response time shall be set to 0; - the Group Address shall be set to the "Push@MulticastAddress" element as specified in the XML document sent by the SDF. To cover the possibility of the initial Membership Report or Multicast Listener Report being lost or damaged, the UE may resend the request once or twice after short delays. If the UE does not receive service selection data as a result of sending these requests, it shall assume that the data are not available and shall stop attempting to join the multicast group.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
8.1.1.2 Procedure to stop receiving service selection information
|
When the UE wants to stop receiving service selection information from an SSF in multicast mode, it shall send an IGMP v3 Membership Report Message or MLD v2 Multicast Listener Report Message for leaving a multicast group. The IGMPv3/MLDv2 request shall be populated as follows: • the type shall be set to 0x22 "v3 Membership Report" for IGMPv3 or to 143 "Version 2 Multicast Listener Report" for MLDv2; • for IGMPv3, the value of "Number of Group Records" is set to the number of group records present in the request. For MLDv2, the value of "Number of Multicast Address Records" is set to the number of multicast address records present in the request; • the Group/Multicast Address Records shall be set as follows: - "Multicast Address" shall be set to the "Push@MulticastAddress" as specified in the XML document sent by the SDF related to the service selection information that the user does not want to receive anymore. - When one or more "Source Address" fields were set in the Join Operation, the same source address list shall be excluded from the listening interface: The "Record Type" shall be set to "BLOCK_OLD_SOURCES" and the "Source Address" fields shall be set to the source list being filtered. - If no "Source Address" fields were set in the Join Operation, The "Record Type" shall be set to "CHANGE_TO_INCLUDE_MODE" with an empty source list. When the UE has to use IGMP v2 for compatibility reason (i.e. the network does not support IGMPv3), the UE shall send v2 Leave, set as follows: - the type shall be set to 0x17 "Leave Group"; - the Max response time shall be set to 0; - the Group Address shall be set to the "Push@MulticastAddress" element as specified in the XML document sent by the SDF. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 120
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
8.1.2 Procedure for BC service
| |
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
8.1.2.1 Procedure for joining a BC service
|
After the BC session initiation procedure, when the UE wishes to join a particular BC service, an IGMP unsolicited v3 Membership Report or a MLD v2 Multicast Listener Report Message to the Access Node as specified in RFC 3376 [28] and RFC 3810 [29]. The IGMPv3/MLDv2 request shall be populated as follows: • the type shall be set to 0x22 "v3 Membership Report" for IGMPv3 or to 143 "Version 2 Multicast Listener Report" for MLDv2; • for IGMPv3, the value of "Number of Group Records" is set to the number of group records present in the request. For MLDv2, the value of "Number of Multicast Address Records" is set to the number of multicast address records present in the request; • the Group/Multicast Address Records shall be set as follows: - "Multicast Address", as obtained from the SSF, shall be set to one of the allowed channels according to the session initiation. - When one or more source address elements are present in network parameters received during the BC session initiation procedure or received from the SSF, then: "Record Type" shall be set to ALLOW_NEW_SOURCES with INCLUDE filter mode: - the value of "Number of Sources" is set to the number of source addresses present in the group record; - the "Source Address" fields shall be set to the source address elements received during the BC session initiation procedure or received from the SSF. - If no source address elements are present in network parameters received during the BC session initiation procedure or received from the SSF, (i.e. source address filtering is not used): "Record Type" shall be set to CHANGE_TO_EXCLUDE_MODE with no "Source Address" fields. When the UE has to use IGMP v2 for compatibility reason (i.e. the network does not support IGMPv3), the UE shall send v2 Membership report, set as follows: - the type shall be set to 0x16 "v2 Membership Report"; - the Max response time shall be set to 0; - the Group Address shall be set to the multicast address, as obtained from the SSF. It shall be one of the allowed channels according to the session initiation. To cover the possibility of the initial Membership Report or Multicast Listener Report being lost or damaged, the UE may resend the request once or twice after short delays. If after these attempts no BC media received, and an IGMP v3 Membership Report was sent, the UE shall revert to an IGMP v2 Multicast Listener Report and repeat the above procedure. If the UE does not receive BC media data as a result of sending these requests, it shall assume that the data is not available and shall stop attempting to join the multicast group.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
8.1.2.2 Procedure for leaving BC service
|
When the UE wants to stops receiving content delivery data from the previously selected BC service, it shall send an IGMPv3 Membership Report Message or MLDv2 Multicast Listener Report Message for leaving a multicast group. The IGMPv3/MLDv2 request shall be populated as follows: • the type shall be set to 0x22 "v3 Membership Report" forIGMPv3 or to 143 "Version 2 Multicast Listener Report" for MLDv2; ETSI ETSI TS 183 063 V3.6.1 (2014-08) 121 • for IGMPv3, the value of "Number of Group Records" is set to the number of group records present in the request. For MLDv2, the value of "Number of Multicast Address Records" is set to the number of multicast address records present in the request; • the Group/Multicast Address Records shall be set as follows: - "Multicast Address" shall be set to the multicast address of the BC service that the user does not want to receive anymore. - When one or more "Source Address" fields were set in the Join Operation, the same source address list shall be excluded from the listening interface: The "Record Type" shall be set to "BLOCK_OLD_SOURCES" and the "Source Address" fields shall be set to the source list being filtered. - If no "Source Address" fields were set in the Join Operation, The "Record Type" shall be set to "CHANGE_TO_INCLUDE_MODE" with an empty source list. The case when the UE has to use IGMP v2 for compatibility reason (i.e. the network does not support IGMPv3), the UE shall send v2 Leave, set as follows: - the type shall be set to 0x17 "Leave Group"; - the Max response time shall be set to 0; - the Group Address shall be set to the multicast address of the BC service the UE wants to leave.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
8.1.3 Procedure for Notification service using multicast media path
|
When the notification service is consumed together with the related BC service, the notification service is described as a separate service from the related BC. In this case, an extension to the BC service mechanism, through the inclusion of a "Network Generated Notification" indicator, is used to identify such a notification service. The UE shall join a notification service like Procedure for joining a BC service in clause 8.1.2.1, the Group/Multicast Address Records and the Group Address shall be set to the notification multicast address. The UE shall leave a notification service like Procedure for leaving a BC service in clause 8.1.2.2, the Group/Multicast Address Records and the Group Address shall also be set to the notification multicast address.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
8.2 Transport Functions
|
For IPv4 multicast IPTV service distribution, the network transport functions shall support minimally IGMPv2 or higher. The use of IGMPv3 is recommended, in which case the backwards compatibility rules of RFC 3376 [28], clause 7 shall apply. For IPv6 multicast IPTV service distribution, the network transport functions shall support minimally MLDv1 or higher. The use of MLDv2 is recommended, in which case the backwards compatibility rules of RFC 3810 [29], clause 8 shall apply.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
8.2.1 Receiving IGMP/MLD request corresponding to a join operation
|
When receiving an IGMP/MLD request corresponding to a join, the ECF/EFF shall check, based on traffic policies, whether the sender of the request is allowed to join the targeted multicast group. If the multicast group is not allowed the ECF/EFF shall ignore the UE request. If the multicast group is allowed, the ECF/EFF may also check whether the resource level specified in the installed policy matches the resource level required by the requested multicast group. In case of a mismatch, the ECF/EFF node may request a new policy by querying the RACS. If fails no new policy is received or the new policy still does not match the request, the ECF/EFF shall ignore the UE request. Traffic policies may be pre-configured in the ECF/EFF, received from the RACS when the UE attaches to the network (i.e. RACS push model), received from the RACS as a result of an IMS session being established (i.e. RACS push model) or received from the RACS in response to a query from the ECF/EFF (i.e. RACS pull model). Information received from the RACS takes precedence over pre-configured policies. Traffic policies supporting the decisions to forward traffic and traffic policies supporting admission control may be received using the same or different means. ETSI ETSI TS 183 063 V3.6.1 (2014-08) 122 Whether the ECF/EFF queries the RACS depend on local policy rules and on the targeted multicast group. The ECF/EFF queries the RACS, by sending a DIAMETER CCR command as defined in TS 183 060 [38]. If the targeted multicast group is allowed and the resource reservation procedure is successful the ECF/EFF shall register the UE IP address as member of this multicast group and begin to forward content delivery data to the UE, when available. If the ECF/EFF does not receive content delivery data from this multicast group yet, it shall subscribe to it.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
8.2.2 Receiving IGMP/MLD request corresponding to a leave operation
|
When Receiving IGMP/MLD request corresponding to a leave operation, the ECF/EFF shall stop forwarding data to the UE corresponding to the multicast group indicated in the Leave operation and delete the subscription of the UE IP address to this group. If pull model is used, the ECF/EFF shall inform the RACS of the Leave operation to make the resources available to other services by sending a DIAMETER CCR command as defined in TS 183 060 [38].
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
9 Procedures using DVBSTP for IMS-based IPTV
|
This clause applies when using DVB-IPTV multicast delivery for service and content guide discovery.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
9.1 User Equipment (UE)
| |
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
9.1.1 Procedure for service selection
| |
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
9.1.1.1 Request of DVB service discovery and selection data
|
In the DVB push model of multicast delivery of DVB SD&S data, the UE shall subscribe to the multicast DVBSTP streams identified within the response from the SDF. Refer to clause 8 for multicast connection mechanism.
|
df2807db9e02a958d05489c27e83bfa9
|
183 063
|
9.1.1.2 Request of DVB broadband content guide
|
In the DVB push model of multicast delivery of a DVB BCG data, the UE shall subscribe to the multicast DVBSTP streams identified within the response from the SDF or within the Service Selection information returned by the SSF. Refer to clause 8 for multicast connection mechanism.
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.