hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
ecb85a7739eb1fdb3cacaea64cc5c9a3 | 185 011 | 15.1 IPTV CND Operating in Routed CPN Mode | In routed CPN mode the IPTV CND utilizes Gm' for SIP signalling with CNG-SIP Proxy B2BUA TS 185 010 [5]. The CNG-SIP Proxy B2BUA may perform NAT/FW-traversal and QoS management based on this signalling. Signalling conforms to TS 183 063 [2] with two limitations: • SIP messages shall be sent to the CNG-SIP Proxy B2BUA (... |
ecb85a7739eb1fdb3cacaea64cc5c9a3 | 185 011 | 16 Procedures at the au reference point | Procedures at the au reference point are as specified by TS 185 010 [5]. ETSI ETSI TS 185 011 V2.1.1 (2009-07) 19 17 Data to be provisioned in the IPTV-CND by pre-configuration This clause is dedicated to the pre-configured data, which are presented in table 6. Table 6 Data Description (ref) Vendor Class Id Device iden... |
d20cee83487b776a4bad5c032873a036 | 185 006 | 1 Scope | The present document defines the stage 2 Customer Network Devices (CND) specifications, including architectural building blocks to be included in the Customer Network Devices to support the interworking with control plane NGN architecture, both for the transport layers (NASS, RACS) and for the service layer. The presen... |
d20cee83487b776a4bad5c032873a036 | 185 006 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. • For a specific reference, subsequent revisions do not apply. • Non-specific reference may be made only to a complete document or a part thereof and only in the following cases: - if it is accept... |
d20cee83487b776a4bad5c032873a036 | 185 006 | 2.1 Normative references | The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. [1] ETSI ES 282 002: "Telecommunications and Internet con... |
d20cee83487b776a4bad5c032873a036 | 185 006 | 2.2 Informative references | The following referenced documents are not essential to the use of the present document but they assist the user with regard to a particular subject area. For non-specific references, the latest version of the referenced document (including any amendments) applies. [i.1] ETSI TS 185 009: "Telecommunications and Interne... |
d20cee83487b776a4bad5c032873a036 | 185 006 | 3 Definitions and abbreviations | |
d20cee83487b776a4bad5c032873a036 | 185 006 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: CPN Device: device that is physically installed in the CPN allowing user access to network services; this can be a Customer Network Gateway with gateway functionalities towards the NGN, or a Customer Network Device being the end user t... |
d20cee83487b776a4bad5c032873a036 | 185 006 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: AKA Authentication and Key Agreement B2BUA Back to Back User Agent C-BGF Core Border Gateway Function CND Customer Network Device CND-A CND-client Application CND-AtF CND-Attachment Function CND-CMF CND-Configuration and Management Function CN... |
d20cee83487b776a4bad5c032873a036 | 185 006 | 4 Customer Network Device (CND) classification | The Customer Network Devices connected to the Customer Premises Network can be of different types. The services supported from each CND depend of the CND's type. In this clause a macro-classification is given. More in general, in a customer premises network End Devices used by end user, Network Devices to support the C... |
d20cee83487b776a4bad5c032873a036 | 185 006 | 4.1 Non IMS capable CNDs | |
d20cee83487b776a4bad5c032873a036 | 185 006 | 4.1.2 Non-IP CNDs | The non-IP devices include the POTS phone and ISDN devices; these type of devices can be connected to the NGN through the CNG or directly. In any case, the architecture of these devices is out of scope of the present document. The voice services on POTS/ISDN devices can be done in emulation [1], [2] and [3] or simulati... |
d20cee83487b776a4bad5c032873a036 | 185 006 | 4.1.2.1 Non-IP CNDs connected to the NGN without a CNG | In this case the POTS and ISDN device is connected to the MG (Media Gateway) [3] via the Z interface for voice services, as shown in figure 4.1. In case of data services, for ISDN device, the S/T interface is needed. The case of voice services for POTS/ISDN in PES scenario is shown in figure 4.1. ETSI ETSI TS 185 006 V... |
d20cee83487b776a4bad5c032873a036 | 185 006 | 4.1.2.2 Non-IP CNDs connected to the NGN through a CNG | In this case, the CNG includes all the CPN functionalities necessary to fulfil a service between the analogue or ISDN phone and the NGN network. The voice services can be based on PES or Core IMS scenario. The details of CNG architecture are specified in TS 185 003 [6]. IMS Core Customer Premises Network POTS Z Gm CNG ... |
d20cee83487b776a4bad5c032873a036 | 185 006 | 4.1.3 IP CNDs | These devices are able to get IP connectivity within the CPN, but they are not implementing the RFC 3261 [10] functionalities to manage signalling. This can be a communication device non compliant with RFC 3261 [10], but also devices not specifically devoted to communication services (for example: webcam with HTTP serv... |
d20cee83487b776a4bad5c032873a036 | 185 006 | 4.1.4 SIP IETF capable CNDs | |
d20cee83487b776a4bad5c032873a036 | 185 006 | 4.1.4.1 Non-IMS SIP CND connected to the NGN through a CNG | A non-IMS SIP IETF device shall utilize the Gm' reference point (instead of the Gm reference point that is utilized by IMS capable devices) in order to get a service from NGN-IMS. See figure 4.5. ETSI ETSI TS 185 006 V2.3.1 (2009-05) 14 CNG LAN side : the User Equipment WAN side : the NGN and IMS entities P-CCSF CNGCF ... |
d20cee83487b776a4bad5c032873a036 | 185 006 | 4.1.5 Consumer Electronics | These types of CNDs are out of scope. The case of CND correlated to IPTV is detailed in TS 185 009 [i.1]. |
d20cee83487b776a4bad5c032873a036 | 185 006 | 4.2 IMS capable CNDs | 4.2.1 IMS Customer Network Device connected to the NGN through a CNG In this case, the Customer Network Device includes all the service-related functionalities necessary to fulfil a service between itself and the NGN-IMS network, as shown in figure 4.6. The CNG offers the capabilities to support attachment and transpor... |
d20cee83487b776a4bad5c032873a036 | 185 006 | 4.2.2 Consumer Electronics | The definition of consumer electronics architecture is out of scope for the present document. The architecture of CND involved in IPTV services are covered in TS 185 009 [i.1] |
d20cee83487b776a4bad5c032873a036 | 185 006 | 4.3 IMS customer network device architecture | In the following clause a detailed description of the entities on figure 4.6 is given. 4.3.1 The Customer Network Devices- Network Attachment Subsystem entities (CND-NASS) CND-CMF: Customer Network Device - Configuration and Management Function. The CND-CMF entity shall enable the configuration of CND based on data obt... |
d20cee83487b776a4bad5c032873a036 | 185 006 | 4.3.2 The transfer level functions | CND-NTF: NAPT Traversal Function The function shall allow the CNG-NFF (in CNG) traversal (as detailed in TR 187 008 [i.3]) and particularly maintain the binding between the SIP UA and the P-CSCF/C-BGF. The CND-NTF should also supply the SIP UA with the mapping made by the CNG on the NGN side so as to fill the SDP field... |
d20cee83487b776a4bad5c032873a036 | 185 006 | 4.3.3 The transport level functions | CND-CSMF: Customer Network Device-Communication Services Media Function The CND-CSMF shall terminate the media flows. In some cases the media flows may be encrypted. 4.3.4 The Customer Network Devices - Service-related Functional entities (CND-SF) CND-SIP UA: Customer Network Device SIP UA This block shall implement th... |
d20cee83487b776a4bad5c032873a036 | 185 006 | 5 Reference Points | |
d20cee83487b776a4bad5c032873a036 | 185 006 | 5.1 Network attachment reference points | e1': The e1' reference point is defined between the CND and the CNG-AtF. The CNG-AtF provides IP addresses (IPv4 or IPv6 format) to the CND through the CND-AtF, it may also send some configuration information for the CND (typically through DHCP options). The CND and CNG shall mutually exchange their hardware identities... |
d20cee83487b776a4bad5c032873a036 | 185 006 | 5.2 Transport level reference points | Dj: The Dj reference point is responsible for the exchange of media flows between the User Equipment (CNG or CND) and the C-BGF. This reference point is mandatory. It is based on ES 282 001 [14]. |
d20cee83487b776a4bad5c032873a036 | 185 006 | 5.3 Service layer reference points | Gm: The Gm reference point supports the communication between UE and the IMS, e.g. related to registration and session control. Gm between the P-CSCF and the SIP proxy B2BUA is used to support several actions: - send SIP messages to/from the NGN; - call forking at the CNG level. The protocol used for the Gm reference p... |
d20cee83487b776a4bad5c032873a036 | 185 006 | 6 Authentication issues | This clause is related to the authentication method used by customer network devices for registration and authentication on IMS core. The target authentication method is IMS AKA authentication based on ISIM/UICC, but in coherence with TS 187 001 [i.2] there are other two methods to be considered: HTTP Digest and NBA. F... |
d20cee83487b776a4bad5c032873a036 | 185 006 | 6.1 CNG based | In case of CNG in the CPN, the CNG can be add the private identity in the Authorization Header ES 283 003 [4], if needed, both for HTTP Digest and NBA authentication method. ETSI ETSI TS 185 006 V2.3.1 (2009-05) 20 CNG CND IMS capable (early deploy) Auth Http Digest NGN REGISTER((IMPU, IMPI, Authorization head. mandato... |
d20cee83487b776a4bad5c032873a036 | 185 006 | 6.2 Non CNG based | In case of no CNG is in CPN, for non CND R2 and non IMS capable CND it is impossible to add the Authorization Header to the message that requires authorization before the challenge, so these CNDs cannot be supported in shared IMPU use case [5]. Figure 6.2: Early Implementation without CNG in CPN ETSI ETSI TS 185 006 V2... |
d20cee83487b776a4bad5c032873a036 | 185 006 | 7 The CND Data Model | The CND should support the device data model proposed by DSL Forum, the TR-106 [9] (data model for a generic device). The CND is needed to support the set of parameters defined by DSL Forum in TR-104 [8] (data model for VoIP functionalities). |
d20cee83487b776a4bad5c032873a036 | 185 006 | 8 Information Flows | NOTE: Information flows clause is non normative text reported in form of examples, to better understand the relationships between the CPN entities and functionalities. |
d20cee83487b776a4bad5c032873a036 | 185 006 | 8.1 Attachment Flows | |
d20cee83487b776a4bad5c032873a036 | 185 006 | 8.1.1 Example of Information Flows on e1' | The candidate on e1' is DHCP specified in RFC 2131 [16]. In figure 8.1 the basic information flow is given. ETSI ETSI TS 185 006 V2.3.1 (2009-05) 23 CND CND - AtF CNG CNG - AtF DHCP Discover DHCP Offer DHCP Request DHCP Ack CND CND - AtF CNG CNG - AtF DHCP Discover DHCP Offer DHCP Request DHCP Ack Figure 8.1: Informati... |
d20cee83487b776a4bad5c032873a036 | 185 006 | 8.2 Configuration and management flows | |
d20cee83487b776a4bad5c032873a036 | 185 006 | 8.2.1 Example of management reference point selection | In this clause an example of a general way to select between e3 and e3' is given. CNG routed mode Figure 8.2 shows the routed mode scenario; the main data exchanges in this flow are the following: (1) The CNG sends on e1 the request for IP address acquiring to the NASS, on the same e1 the NASS replies with the IP addre... |
d20cee83487b776a4bad5c032873a036 | 185 006 | 8.2.2 Example of Information Flows on e3' | The following information flow is an example of service provisioning functions supported by CNG (see figure 8.4). CND CND - CMF CNG CNG - CMF HTTP GET (Ask Identity) 200 OK (GET Response) HTTP GET (Set Identity) 200 OK (GET Response) CND CND - CMF CNG CNG - CMF HTTP GET (Ask Identity) 200 OK (GET Response) HTTP GET (Se... |
d20cee83487b776a4bad5c032873a036 | 185 006 | 8.3 Signalling flows | The candidate on Gm' is SIP specified in RFC 3261 [10], the one on Gm is SIP specified in TS 124 229 [17] and ES 283 003 [4]. |
d20cee83487b776a4bad5c032873a036 | 185 006 | 8.3.1 CND attachment and NGN registration | The non-IMS devices considered in this case are devices associated to the VoIP phone number of the CNG. Different kinds of devices (see table 4.1): • Fixed or Wireless SIP phone. • SIP Multi-mode (e.g. dual WI-Fi/3G phone). • SIP soft phone on PC. • Other: play station, STB, etc. These SIP devices have a local SIP iden... |
d20cee83487b776a4bad5c032873a036 | 185 006 | 8.3.2 Outgoing call | The non-IMS device is provided with a public SIP URI or a local identity, as it is the case in figure 8.7. INVITE (local SIP URI) 200 OK 407 (challenge) INVITE (IMPU, IMPI, challengeresponse) CND with a local Id (eg device_kitchen) CNG-SIP Proxy B2BUA IMS core network 1xx ACK INVITE (IMPU) RTP/RTCP 1xx 200 OK ACK INVIT... |
d20cee83487b776a4bad5c032873a036 | 185 006 | 8.3.3 Internal Call | The CNG SIP- proxy can route local call between 2 devices of the CPN. No NGN resource is used to establish internal call. SIP signalling is not forwarded to core network and media streams are kept on the CPN directly between endpoints. The CNG SIP proxy identifies internal call after the analysis of the called party nu... |
d20cee83487b776a4bad5c032873a036 | 185 006 | 8.3.4 Admission Control (CNG-ACF) | The CNG-Admission Control Function (CNG-ACF) module calculates the available resources on the access line during the establishment of a new session, possibly limiting the number of sessions in advance, before the direct intervention of the RACS on the NGN side. As it has no means of reading signalling protocols other t... |
d20cee83487b776a4bad5c032873a036 | 185 006 | 8.4 Remote Access information flows | |
d20cee83487b776a4bad5c032873a036 | 185 006 | 8.4.1 Connection Setup | This clause describes one procedure where information of which CNDs are registered in the CNG and therefore accessible via Remote Access, is retrieved by the remote UE. The UE provides an application linking the procedures for Remote Access services. ETSI ETSI TS 185 006 V2.3.1 (2009-05) 32 SIP ACK SIP ACK Remote UE IM... |
d20cee83487b776a4bad5c032873a036 | 185 006 | 8.4.2 Download of content | This clause describes the procedure where content is downloaded from a particular CND to the remote UE. The information about which CNDs are available has been retrieved during the connection setup procedure. The UE provides an application linking the procedures for Remote Access services. Prerequisite is the RA Connec... |
d20cee83487b776a4bad5c032873a036 | 185 006 | 8.4.3 Upload of content | This clause describes the procedure where content is uploaded to a particular CND from the remote UE. The information about which CNDs are available has been retrieved during the connection setup procedure. The UE provides an application linking the procedures for Remote Access services. Prerequisite is the RA Connecti... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 1 Scope | The present document describes the Procedures on the Functional Entities and Call Flows for the protocols and their possible enhancements to support IPTV services based on the architecture and stage 2 information flows described in TS 182 027 [2]. The possible enhancements of protocols will define the scope of new or e... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. • For a specific reference, subsequent revisions do not apply. • Non-specific reference may be made only to a complete document or a part thereof and only in the following cases: - if it is accept... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 2.1 Normative references | The following referenced documents are indispensable for the application of the present document. For dated references, only the edition cited applies. For non-specific references, the latest edition of the referenced document (including any amendments) applies. [1] ETSI ES 282 007: "Telecommunications and Internet con... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 2.2 Informative references | The following referenced documents are not essential to the use of the present document but they assist the user with regard to a particular subject area. For non-specific references, the latest version of the referenced document (including any amendments) applies. [i.1] ETSI TS 183 060: "Telecommunications and Interne... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 3 Abbreviations | For the purposes of the present document, the following abbreviations apply: AUID Application Unique ID BC BroadCast BCG Broadband Content Guide CoD Content On Demand DVB Digital Video Broadcasting DVBSTP DVB SD&S Transport Protocol ECF/EFF Elementary Control Function/ Elementary Forwarding Function ERE Extended Regula... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 4 Applicability | |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 4.1 Overview | The overall functional architecture for the IMS-based IPTV service conforms to TS 182 027 [2]. This clause provides the list of protocols and related reference points. Figure 4.1: Protocols used in functional architecture for the IMS-based IPTV service ETSI ETSI TS 183 063 V2.1.0 (2008-06) 15 Table 4.1: IMS based IPTV ... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 4.2 Functional Entities | |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 4.2.1 User Equipment (UE) | The UE is a functional entity that provides the user with access to IPTV services. |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 4.2.2 Service Control Function (SCF) | The SCF is a functional entity that provides IPTV service logic and the functions required to support execution of such logic. |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 4.2.3 Service Discovery Function (SDF) | An SDF is a functional entity that provides service attachment information to the UE. |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 4.2.4 Service Selection Function (SSF) | An SSF is a functional entity that provides service selection information to the UE. |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 4.2.5 Media Control Function (MCF) | The MCF is a functional entity that provides the UE with functions required to control media flows and manages the MDFs under its control. |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 4.2.6 Media Delivery Function (MDF) | The MDF is a functional entity that delivers content data to the UE. |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 4.2.7 Core-IMS | The Core IMS includes a number of functional entities identified in ES 282 007 [1]. For the purpose of supporting IPTV services, the following functional entities of the Core IMS are involved: - the P-CSCF; - the S-CSCF; - the I-CSCF; - the IBCF in case the P-CSCF and the I/S-CSCF or the CSCF and the MCF are in differe... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 5 Procedures using SIP/SDP for IMS-based IPTV | Use the SIP/SDP protocol across the following interfaces is described in this clause: • interface Gm; • interface ISC; • interface y2. SIP/SDP capable functional entities are following: • UE. • SCF. • SDF. • MCF. • Core IMS. NOTE: Summary of compliancy requirements and referred specification are listed in clause H.1. |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 5.1 User Equipment (UE) | |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 5.1.1 Procedure for IMS registration | As specified in TS 182 027 [2], clause 8.2 the UE shall perform IMS registration before launching a service attachment procedure. The behaviour of the UE with regards to IMS registration shall comply with ES 283 003 [20]. |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 5.1.2 Procedure for service attachment | If the SDF is known as per annex I the Pull mode as in clause 5.1.2.2 shall be used, else the UE shall be preconfigured to use the public user identity of the user to send a SIP SUBSCRIBE request according to the Pull mode or to expect a SIP MESSAGE request according to Push mode as in clause 5.1.2.1. |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 5.1.2.1 Push mode | Upon receipt of a SIP MESSAGE request from the SDF, the UE shall parse the XML document as described in clause 5.1.2.2.2. |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 5.1.2.2 Pull mode | Service Attachment, the UE shall generate a SUBSCRIBE request. The behaviour of the UE when processing a SUBSCRIBE request shall conform to ES 283 003 [20], clause 5.1.2A.1. ETSI ETSI TS 183 063 V2.1.0 (2008-06) 18 |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 5.1.2.2.1 Subscription | When the UE intends to retrieve service attachment information from the SDF, it shall generate a SUBSCRIBE request for the "ua-profile" event package defined in draft-channabasappa-sipping-app-profile-type-02 [22]. The contents of the SUBSCRIBE request shall be as follows: • The value of the Request-URI shall be set to... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 5.1.2.2.2 Receiving notifications | Upon receipt of a NOTIFY request on the dialog which was generated during subscription, the UE shall look for a message body with a content-type header indicating "application/vnd.etsi.iptvdiscovery+xml ". The IPTV application within the UE shall parse the XML document contained in the message body. The list of paramet... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 5.1.3 Procedure for BC service | |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 5.1.3.1 Session initiation | The UE shall support the procedures specified in ES 283 003 [20] for originating sessions. Upon a request for a BC session initiation, the UE shall generate an initial INVITE request as specified in ES 283 003 [20] for an originating UE. The Request-URI in the INVITE request shall be the well known PSI (Public Service ... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 5.1.3.1.1 Additional SDP lines for FEC streams | When the UE decides to connect to FEC stream(s) associated to the original BC stream(s), it shall include additional SDP lines in the SDP offer as follows: • One or more m line(s) for each FEC stream exposed through the SSF: - it shall be set according to the mapping defined in clause L.2; - it shall contain a c-line a... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 5.1.3.2 Session modification | When there is a need for BC session modification, the UE shall generate a re-INVITE request or an UPDATE request, depending on the dialogue state, as specified in ES 283 003 [20] for an originating UE. The UE shall include SDP offer in session modification request. When the modified session is also a broadcast session ... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 5.1.3.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.1.3.3.1 Trick-play mode activation | Upon activation of trick-play mode, the UE shall perform session modification as described in clause 5.1.3.2. The UE shall include an SDP offer with previously negotiated media descriptions with the port set to zero and two or more additional media descriptions: one for RTSP control and one or more for the unicast stre... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 5.1.3.3.2 Trick-play mode deactivation | Upon deactivation of trick-play mode, the UE shall perform session modification as described in clause 5.1.3.2. The UE shall include an SDP offer with previously negotiated RTSP and unicast media descriptions with the port set to zero. The SDP corresponding to the broadcast session shall be reactivated (i.e. port not s... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 5.1.3.4 Session termination | Upon a request for a BC session termination, the UE shall generate a BYE request as specified in ES 283 003 [20] for an originating UE. Upon receipt of a BYE request the UE shall follow the procedure specified in ES 283 003 [20] for an originating UE. |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 5.1.3.5 Session Information | During the procedures for join multicast group (clause 8.1.1) the UE may inform SCF of the selected channel. If the UE informs the SCF of the selected channel it shall reset a delay timer after successfully viewing a new channel using the procedure for joining multicast group (clause 8.1.1). The delay timer is a precon... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 5.1.4 Procedure for CoD service | |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 5.1.4.1 Procedure for retrieving missing parameters before session initiation | In case of procedure for establishing the content control and content delivery at the same time see clause 5.1.4.2.1, if the UE does not have all transport parameters (RTP or UDP transport for MPEG2TS encapsulation or direct RTP, FEC layers addresses and ports) the UE shall send a SIP OPTIONS message, NOTE: it is an op... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 5.1.4.2 Session initiation | The UE shall support the procedures specified in ES 283 003 [20] for originating sessions. Upon a request for a COD session initiation, the UE shall generate an initial INVITE request as specified in ES 283 003 [20] for an originating UE. The "Request-URI" is related to the CoD session that the user wants to activate. ... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 5.1.4.2.1 Procedure for establishing the RTSP content control and content delivery channel | 5.1.4.2.1.1 UE as SDP offerer An SDP Offer shall be included in the initial INVITE request. the SDP offer shall be done in accordance with media capabilities and policies available for the CoD session and with the parameters received from the SSF during UE service selection procedure (cf. annex L concerning the mapping... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 5.1.4.2.2 Procedure for establishing the RTSP channel separately | 5.1.4.2.2.1 UE as SDP offerer The INVITE request shall contain an SDP offer of media description only for the RTSP channel. The SDP session level parameters shall be used as specified in ES 283 003 [20]. The SDP parameters for the RTSP channel shall be set as follows: • A "m" line for an RTSP stream of format: m=<media... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 5.1.4.2.3 Additional SDP lines for FEC streams | When the UE decides to connect to FEC stream(s) associated to the COD original stream, it shall include additional SDP lines in the SDP offer as follows: • One or more m-line(s) for each FEC stream exposed through the SSF: - it shall be set according to the mapping defined in clause L.3; - it shall contain a c-line acc... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 5.1.4.3 Session modification | In order to modify the session from the UE side, the UE shall send a re-INVITE or an UPDATE request as specified in ES 283 003 [20] for an originating UE. The UE shall not modify RTSP channel m-line description in the SDP if the media delivery streams controlled by RTSP are not removed (port not set to zero in m-lines)... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 5.1.4.3.1 Procedure for establishing the content delivery channel | 5.1.4.3.1.1 UE as SDP offerer The UE shall send a re-INVITE or an UPDATE request containing SDP offer after acquiring the network parameters via RTSP DESCRIBE as specified in clause 7.1.2.2 in order to establish the content delivery channels. The media descriptions of content delivery channels shall be populated as fol... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 5.1.4.3.2 Additional SDP lines for FEC streams | When the UE decides to connect to FEC stream(s) associated to the COD original stream, it shall include additional SDP lines in the SDP offer as follows: • One or more m-line(s) for each FEC stream exposed through the SSF: - it shall be set according to the mapping defined in clause L.3; - it shall contain a c-line acc... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 5.1.4.4 Session termination | The session termination will differ when using RTSP "Method 1" or RTSP "Method 2" as described in the following clauses. The different RTSP methods are described in clause 7 and annex Q. |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 5.1.4.4.1 Session termination using RTSP Method 1 | In order to terminate the session, the UE shall first close the RTSP session that was established during session initiation by closing the underlying TCP connection and then send a BYE request as specified in ES 283 003 [20]. Upon receipt of a BYE request, the UE shall then terminate the session as specified in ES 283 ... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 5.1.4.4.2 Session termination using RTSP Method 2 | In order to terminate the session, the UE shall send a BYE request as specified in ES 283 003 [20]. The media teardown procedures using RTSP TEARDOWN as described in clause 7.1.2.6 shall be executed before the BYE is sent out. This would ensure that the BYE request does not close the RTSP content control channel ports ... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 5.1.4.5 Procedures for handling COD Service action data | When a user requests to stop viewing a CoD with the intention of resuming it later, the UE may send a SIP INFO request to the SCF. The content of that INFO request shall be as follows: • The value of the Request-URI shall be set to the one used in the related session. • From and To headers shall be set to the one defin... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 5.1.5 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 User Profile 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 man... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 5.1.5.1 Subscription to notification of changes | If subscription to notification of changes is used, the UE shall generate a SUBSCRIBE request in accordance with IETF draft-ietf-sip-xcapevent-03 [26] and draft-ietf-simple-xcap-diff-09.txt [15]. The contents of the SUBSCRIBE request shall be as follows: • The value of the Request-URI shall be set to the IMS public use... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 5.1.5.2 Processing of notifications | Upon receipt of a NOTIFY request on the dialog which was generated during subscription, the UE shall look for a message body with a content-type header indicating "application/xcap-diff+xml" stores its contents for further processing. and return a 200 OK response to the NOTIFY request. |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 5.1.6 Procedure for IPTV presence service | If presence service is used, the UE shall implement the role of a PUA as specified in ES 283 030 [21]. Publication of IPTV specific information in presence document depends on user-configurable data stored in the user equipment. Depending on the user configuration, the UE may send a SIP PUBLISH request in the following... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 5.1.7 Procedure for NPVR Service | |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 5.1.7.1 Procedures for NPVR Service Capture Request | The SIP MESSAGE method is used here to achieve what is described in the architectural document (TS 182 027 [2]) as "N-PVR content capture request". This request may be done in an impulsive way or offline. |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 5.1.7.1.1 Procedures for Impulsive Request | This use case is itself divided in two sub-cases: Case 1: The user do not specify any end date and time for the recording. This can be seen as a case of "Park and pickup TV' as described in TS 182 027 [2]: In this case the UE shall send a SIP MESSAGE request to SCF requiring Bookmark setting. The contents of the SIP ME... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 5.1.7.1.2 Procedures for Offline Request | A user may request to record a live programme that has not started yet. In this case the UE shall send a SIP MESSAGE request to the SCF. The content of the SIP MESSAGE request shall be as follows: • The user-part of the Request-URI shall be set to the BC Service Package ID that the BC service belongs to. • From and To ... |
5d7ec12f766781dab55c1d864dce26b5 | 183 063 | 5.1.7.2 Procedures for NPVR Session | The UE follows procedures outlined in clause 5.1.4 for COD to stream a previously captured NPVR content. The user part of the "Request-URI" parameter shall contain the NPVRContentId retrieved from the SSF as defined in clause 6.1.1.5 and shall correspond to the content that was captured via impulsive or offline request... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.