hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 5.2 Service Discovery Function (SDF) | |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 5.2.1 Procedure for IMS registration | If delivery of service discovery information using push mode is supported, the SDF acts as a third-party registrar and receive REGISTER requests from the Core-IMS during the IMS registration phase. The SDF shall store the public user identity of the user as received in the To header and use it to initiate delivery of s... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 5.2.2 Procedure for service attachment | |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 5.2.2.1 Push mode | In the push mode, after the regular third-party registration, the SDF shall generate a SIP MESSAGE to the UE, and the service attachment information is taken in the message body of the SIP MESSAGE. The SDF uses the SIP MESSAGE to transport the service attachment information, and the SDF shall generate a SIP MESSAGE req... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 5.2.2.2 Pull mode | The SDF addresses may be determined by the UE using any of the alternatives as defined in annex I. When the SDF receives a SUBSCRIBE request, if personalized information is required it shall perform user's identity verification as defined in ES 283 003 [20], clause 5.7.1.4. After successful user identification if an IP... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 5.2.2.3 Service Attachment Information | The body of the SIP message from SDF shall include an XML document listing SSF addresses and the means of connecting to the SSFs for retrieving service selection information. ETSI ETSI TS 183 063 V2.1.0 (2008-06) 34 For each SSF, the following sub-elements are populated as follows. Table 5.2.2.3: SSF information sendin... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 5.3 Service Control Function (SCF) | |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 5.3.1 Procedure for BC service | |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 5.3.1.1 Session initiation | The SCF shall support the procedures specified in ES 283 003 [20] applicable to an AS acting as a terminating UA. Upon receipt of SIP INVITE request, the SCF shall examine the Request-URI to determine that it is a BC session initiation request. According to the user subscription information, the SCF shall check the ser... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 5.3.1.2 Session modification | Upon receipt of a re-INVITE request or an UPDATE request, the SCF shall follow the procedures defined in ES 283 003 [20] concerning the AS acting as a terminating UA or a B2BUA. When receiving an SDP offer, the SCF may modify the SDP answer in accordance to the user subscription. If the SCF finds a media line not compa... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 5.3.1.3 BC service with trick-play mode | In case of supporting BC service with trick play, the BC session can observe two special cases: • The Broadcast session is modified to change from Multicast to unicast flow. This is the case in which the UE activates the trick play mode. • The Broadcast session with trick play mode is modified to return to normal Broad... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 5.3.1.3.1 Trick-play mode activation | Within the existing Broadcast TV session, if the session modification request contains Service Action Data with IPTVActionDataCommand set to "SwitchtoTM", the SCF shall determine the modify request is for transition from Broadcast TV to Broadcast TV with trick mode and shall act as a B2BUA, terminating the re-INVITE re... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 5.3.1.3.2 Trick-play mode deactivation | Within the existing Broadcast TV session, if the session modification request Service Action Data with IPTVActionDataCommand set to "SwitchtoBC", the SCF shall determine the modify request is for transition from Broadcast TV with trick mode to Broadcast TV and shall act as a B2BUA, terminating the re-INVITE request and... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 5.3.1.4 Session termination | Upon receipt of a BC session termination request, the SCF shall follow the procedures defined in ES 283 003 [20] concerning the AS acting as a terminating UA. Upon receipt of an internal indication that a BC session shall be terminated, the SCF shall send a BYE request and follow the procedures defined in ES 283 003 [2... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 5.3.2 Procedure for CoD service | The SCF shall support the procedures specified in ES 283 003 [20] applicable to an AS acting as a proxy or B2B UA. |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 5.3.2.1 Procedure for handling missing parameters before session initiation | When receiving the SIP OPTIONS message, the SCF shall select the appropriate media function (see TS 182 027 [2]) and forward the SIP request to the appropriate MCF by changing the "Request-URI" accordingly. The SCF shall not change the user-part of the TO header in order to keep the content-id in the OPTIONS request. I... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 5.3.2.2 Session initiation | When receiving any SIP request, the SCF may examine the request to see if it is compatible with the user's subscription (e.g. parental control level). If the user is not allowed to initiate a session for the requested content, the SCF shall reply with appropriate, SIP error code 403 Forbidden, response. The SCF shall s... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 5.3.2.3 Session modification | Void. |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 5.3.2.4 Session termination | |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 5.3.2.4.1 Session termination using RTSP method 1 | In case of SCF-initiated CoD session termination, the SCF shall send a BYE Request towards the UE and a BYE request towards the MF as specified in ES 283 003 [20]. |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 5.3.2.4.2 Session termination using RTSP method 2 | The SCF shall support the procedures specified in ES 283 003 [20] applicable to an AS acting as a proxy or B2B UA for call release. In case of SCF-initiated CoD session termination, the SCF shall send a BYE Request towards the UE and a BYE request towards the MF as specified in ES 283 003 [20]. |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 5.3.2.5 Procedures for handling COD Service action data | Upon receiving an INFO request with Content-type set to "application/vnd.etsi.iptvsad-cod+xml", the SCF retrieves the service action data from the INFO message body and either creates or updates the matching object instance. A 200 OK message with no body shall be sent to the originator if the INFO request is successful... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 5.3.3 Procedure for Service Configuration | The UE uses the XCAP to manage the IPTV user profile (see clause 6.1.2). In order to keep the IPTV services data synchronized with the network elements and other terminals that the user might be using, the UE should subscribe from the SCF to changes in the XCAP IPTV documents. NOTE: Changes may result from XCAP manipul... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 5.3.4 Procedure for NPVR Service | |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 5.3.4.1 Procedures for NPVR Service Capture Request | Upon receiving a SIP MESSAGE request, the SCF identifies the Content-type associated with the MESSAGE request and takes appropriate actions as specified below. The SCF then checks whether the Service Package id is indeed authorized for the user issuing the request. The actual BC service to be recorded/bookmarked is ext... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 5.3.4.1.1 Procedures for Impulsive Request | Case 1: In case of content_type set to "application/vnd.etsi.iptvsad-bc+xml": Upon receiving a SIP MESSAGE request with Content-type set to "application/vnd.etsi.iptvsad-bc+xml", the SCF retrieves the service action data from the SIP MESSAGE message body and either creates or updates the matching object instance. - If ... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 5.3.4.1.2 Procedures for Offline Request | Upon receiving a SIP MESSAGE request, the SCF checks to see if the Content-type set to "application/vnd.etsi.iptvsad- npvr+xml". If so, it follows the procedures outlined in corresponding case 2 in clause 5.3.4.1.1. |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 5.3.4.2 Procedures for NPVR Session | The SCF follows procedures outlined in clause 5.3.2 for handling a COD session. NOTE: The XML schema mapping to the MIME type: "application/vnd.etsi.iptvsad-npvr+xml" is available in annex K of the present document. |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 5.4 Media Control Function (MCF) | |
5d7ec12f766781dab55c1d864dce26b5 | 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. |
5d7ec12f766781dab55c1d864dce26b5 | 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 thi... |
5d7ec12f766781dab55c1d864dce26b5 | 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, ... |
5d7ec12f766781dab55c1d864dce26b5 | 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. In case the MCF supports CoD RTSP playback control Method 1 as defined in clause 7.2.1, the MCF shall generate an RTSP sessio... |
5d7ec12f766781dab55c1d864dce26b5 | 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, indica... |
5d7ec12f766781dab55c1d864dce26b5 | 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 para... |
5d7ec12f766781dab55c1d864dce26b5 | 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... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 5.4.1.4 Session termination | |
5d7ec12f766781dab55c1d864dce26b5 | 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 persist... |
5d7ec12f766781dab55c1d864dce26b5 | 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 persist... |
5d7ec12f766781dab55c1d864dce26b5 | 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 below) 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 rela... |
5d7ec12f766781dab55c1d864dce26b5 | 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... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 5.4.3 Procedure for NPVR Session | The MF follows procedures outlined in clause 5.4.1 for CoD session initiation, modification and termination procedures. |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 5.5 Core IMS | |
5d7ec12f766781dab55c1d864dce26b5 | 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]. |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 5.5.2 Procedure for Service Attachment | |
5d7ec12f766781dab55c1d864dce26b5 | 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 incl... |
5d7ec12f766781dab55c1d864dce26b5 | 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 r... |
5d7ec12f766781dab55c1d864dce26b5 | 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... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 5.5.4 Procedure for Service Selection | Core IMS entities are not involved during service selection procedures |
5d7ec12f766781dab55c1d864dce26b5 | 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 provid... |
5d7ec12f766781dab55c1d864dce26b5 | 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 ha... |
5d7ec12f766781dab55c1d864dce26b5 | 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 Ident... |
5d7ec12f766781dab55c1d864dce26b5 | 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 communicatio... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 5.6.2 Session Control Procedures | The ICSI may be supported 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. The "IMS IPTV Service" may support different types of media, including media t... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 6 Procedures using HTTP for IMS-based IPTV | |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 6.1 User Equipment (UE) | |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 6.1.1 Procedures for Service Selection | |
5d7ec12f766781dab55c1d864dce26b5 | 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 ... |
5d7ec12f766781dab55c1d864dce26b5 | 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. |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 6.1.1.3 Request of DVB BCG | |
5d7ec12f766781dab55c1d864dce26b5 | 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. |
5d7ec12f766781dab55c1d864dce26b5 | 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. |
5d7ec12f766781dab55c1d864dce26b5 | 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. |
5d7ec12f766781dab55c1d864dce26b5 | 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 avai... |
5d7ec12f766781dab55c1d864dce26b5 | 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 broa... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 6.1.2 Procedure for Service Configuration | |
5d7ec12f766781dab55c1d864dce26b5 | 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 2246 [32].... |
5d7ec12f766781dab55c1d864dce26b5 | 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 draft-ietf-simple-xcap-diff-09.txt [15] and draft-ietf-sip-xcapevent-00.txt ... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 6.2 Service Control Function (SCF) | |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 6.2.1 Procedure for Service Configuration | |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 6.2.1.1 General | An Application Server implements the role of an XCAP server as described in RFC 4825 [9]. |
5d7ec12f766781dab55c1d864dce26b5 | 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]. ETSI ETSI TS 183 063 V2... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 6.2.1.3 Authentication and authorization | An Authentication Proxy (AP) may exist between the UE and the SCP, 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... |
5d7ec12f766781dab55c1d864dce26b5 | 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 dr... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 6.3 Service Selection Function (SSF) | |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 6.3.1 Procedure for Service Selection | 6.3.1.1 Authentication and authorization in case of 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 a... |
5d7ec12f766781dab55c1d864dce26b5 | 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 ... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 6.3.1.3 Delivery of DVB SD&S | When the SD&S SSF receives a 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 appropria... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 6.3.1.4 Delivery of DVB BCG | |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 6.3.1.4.1 Container-based delivery | When the BCG SSF receives a 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 appropriat... |
5d7ec12f766781dab55c1d864dce26b5 | 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. |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 6.3.1.5 Delivery of OMA BCAST ESG | 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 transp... |
5d7ec12f766781dab55c1d864dce26b5 | 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: • IPTVActionDataComma... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 6.4 Stand-Alone XMDS | |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 6.4.1 Procedure for Service Configuration | |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 6.4.1.1 General | The stand-alone XDMS implements the role of an XCAP server as described in RFC 4825 [9]. |
5d7ec12f766781dab55c1d864dce26b5 | 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. |
5d7ec12f766781dab55c1d864dce26b5 | 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. |
5d7ec12f766781dab55c1d864dce26b5 | 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. ETSI ETSI TS 183 063 V2.1.0 (2008-06) 54 |
5d7ec12f766781dab55c1d864dce26b5 | 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 Sess... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 7.1 User Equipment (UE) | |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 7.1.1 Procedures for RTSP playback control (Method 1) | |
5d7ec12f766781dab55c1d864dce26b5 | 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... |
5d7ec12f766781dab55c1d864dce26b5 | 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... |
5d7ec12f766781dab55c1d864dce26b5 | 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 f... |
5d7ec12f766781dab55c1d864dce26b5 | 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 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. Any other parameter that is used in GET_PARAMETER reque... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 7.1.1.5 Handling of Media Events | Upon the reception of the RTSP ANNOUNCE with indication of end-of-stream the UE may take relevant actions to handle the end of stream event (e.g. Terminating session, rewinding the media stream, etc.). The UE shall respond with a 200 OK. In case of BC sessions with trick-play, if the UE receives an RTSP ANNOUNCE reques... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 7.1.2 Procedure for content control (Method 2) | |
5d7ec12f766781dab55c1d864dce26b5 | 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 (U... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 7.1.2.2 Media Description Procedure | In case the 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 SCF/MCF during the SIP ses... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.