hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
ca21a3998d34549327b3d05d69fb17e5 | 183 067 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: termination point: element acting as the neighbouring multicast router receiving and handling IGMP/MLD request from the UE |
ca21a3998d34549327b3d05d69fb17e5 | 183 067 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: AF Application Function A-RACF Access-Resource and Admission Control Function BTF Basic Transport Functions CAC Connection Admission Control CCA Credit-Control-Answer CCR Credit-Control-Request CPN Customer Premises Network IGMP Internet Group... |
ca21a3998d34549327b3d05d69fb17e5 | 183 067 | 4 Overview | 4.1 Overview of multicast transport control protocol to Re mapping PULL mode for multicast applies in two cases: • PULL mode case 1: when it applies below the termination point in the access segment, the PULL mode is used to request resources for a channel in the access network and/or to indicate that the resources ass... |
ca21a3998d34549327b3d05d69fb17e5 | 183 067 | 4.2.1 Push Mode | Figure 4.2 illustrates the RSVP to Re mapping in Push Mode with on-path QoS reservation in the case of a successful reservation establishment. ETSI ETSI TS 183 067 V3.1.1 (2009-11) 8 Figure 4.2: RSVP to Re mapping in Push Mode with on-path QoS reservation 1) As a result of a request from the AF for admission and resour... |
ca21a3998d34549327b3d05d69fb17e5 | 183 067 | 4.2.2 Pull Mode | Figure 4.3 illustrates the RSVP to Re mapping in Pull Mode in the case of a successful reservation establishment. Figure 4.3: RSVP to Re mapping in Pull Mode ETSI ETSI TS 183 067 V3.1.1 (2009-11) 9 1) The BTF receives an RSVP Path message corresponding to a path-coupled QoS reservation initiation request from a Transpo... |
ca21a3998d34549327b3d05d69fb17e5 | 183 067 | 5 Behaviours of the transport functions for multicast | |
ca21a3998d34549327b3d05d69fb17e5 | 183 067 | 5.1 PULL mode: case 1 | On reception of an IGMPv3/MLDv2 request, the BTF communicates the request to the RCEF. If the type is set to 0x22 "v3 Membership Report" in case of IGMPv3 or to 143 "Version 2 Multicast Listener Report" in case of MLDv2, the RCEF shall take the following actions for each Group/multicast Records present in the request: ... |
ca21a3998d34549327b3d05d69fb17e5 | 183 067 | 5.2 PULL mode: case 2 | On reception of an IGMPv3/MLDv2 request, the BTF communicates the request to the RCEF. If the type is set to 0x22 "v3 Membership Report" in case of IGMPv3 or to 143 "Version 2 Multicast Listener Report" in case of MLDv2, the RCEF shall take the following actions for each Group/multicast Records present in the request: ... |
ca21a3998d34549327b3d05d69fb17e5 | 183 067 | 6 Multicast to Re parameters mapping | |
ca21a3998d34549327b3d05d69fb17e5 | 183 067 | 6.1 PULL mode: case 1 | When the RCEF sends a CCR for PULL mode case 1, it shall use the mapping defined in table 6.1 for IGMPv3/MLDv2 request. Table 6.1: Rules for derivation of CCR AVPs from IGMPv3/MLDv2 requests for PULL mode case 1 CCR AVPs Derivation from IGMPv3/MLDv2 Parameters CC-Request-Type It shall be set to UPDATE_REQUEST. Event-Tr... |
ca21a3998d34549327b3d05d69fb17e5 | 183 067 | 6.2 PULL mode: case 2 | When the RCEF sends a CCR for PULL mode case 2, it shall use the mapping defined in table 6.3 for IGMPv3/MLDv2 request. Table 6.3: Rules for derivation of CCR AVPs from IGMPv3/MLDv2 requests for PULL mode case 2 CCR AVPs Derivation from IGMPv3/MLDv2 Parameters CC-Request-Type It shall be set to UPDATE_REQUEST. Framed-I... |
ca21a3998d34549327b3d05d69fb17e5 | 183 067 | 7 Behaviours of the transport functions for unicast | |
ca21a3998d34549327b3d05d69fb17e5 | 183 067 | 7.1 Push mode (RACS initiated Procedures) | This clause specifies the behavior of the RSVP transport functions for unicast in the case of Push mode with on-path QoS reservation. |
ca21a3998d34549327b3d05d69fb17e5 | 183 067 | 7.1.1 Handling Policy-Install-Request from RACS | On receipt of a Policy-Install-Request from RACS, the RCEF shall process the message as specified in TS 183 060 [2]. In addition, when operating in the Push mode with on-path QoS reservation, the RCEF shall extend this behavior as defined in clause 7.1.1.1 (respectively clauses 7.1.1.2 and 7.1.1.3) in case of policy ac... |
ca21a3998d34549327b3d05d69fb17e5 | 183 067 | 7.1.1.1 Activation of a Policy Rule | On receipt of a Policy-Install-Request with PI-Request-Type AVP containing the value INITIAL_REQUEST that activates a new Policy Rule with Flow-Status ENABLED-DOWNLINK, the RCEF shall consider that a new on-path QoS reservation is to be initiated for each IP Flow defined in a Flow-Description AVP. The RCEF shall commun... |
ca21a3998d34549327b3d05d69fb17e5 | 183 067 | 7.1.1.2 Policy Modification | On receipt of a Policy-Install-Request with the PI-Request-Type AVP set to UPDATE_REQUEST, and a Policy-Rule-Install AVP specified (with Flow-Status ENABLED-DOWNLINK), the RCEF shall consider that the existing on-path QoS reservation for each IP Flow is to be modified. The RCEF shall communicate with the BTF to ensure ... |
ca21a3998d34549327b3d05d69fb17e5 | 183 067 | 7.1.1.3 Deactivation of a Policy Rule | On receipt of a Policy-Install-Request with PI-Request-Type AVP set to TERMINATION_REQUEST, if the terminated Policy Rule(s) had a Flow-Status ENABLED-DOWNLINK the RCEF shall consider that the corresponding on-path QoS reservation for each IP Flow is to be torn down. The RCEF shall communicate with the BTF to ensure th... |
ca21a3998d34549327b3d05d69fb17e5 | 183 067 | 7.1.2 Handling unicast transport control protocol events | |
ca21a3998d34549327b3d05d69fb17e5 | 183 067 | 7.1.2.1 RSVP Reservation establishment | On receipt of an RSVP Resv message for a new, or a modified on-path QoS reservation, the BTF shall process the RSVP message as per procedures specified in [1]. On successful establishment of the Resv state, the BTF shall notify the RCEF. Then, assuming all the other processing of the corresponding Policy-Install-Reques... |
ca21a3998d34549327b3d05d69fb17e5 | 183 067 | 7.1.2.2 RSVP Reservation Reject/Establishment Failure/Modification Failure | On receipt of an RSVP message indicating that a new on-path QoS reservation establishment has been rejected (e.g. receipt of a PathErr message containing an ERROR_SPEC object with an error code of "Code 1 - Admission Control Failure" or "Code 2 - Policy Control Failure" as specified in [5]) or has failed possibly after... |
ca21a3998d34549327b3d05d69fb17e5 | 183 067 | 7.1.2.3 RSVP Reservation Loss/Tear-Down | The BTF shall detect the loss or teardown on an existing on-path QoS reservation that the RCEF established. The detection is based on existing RSVP procedures as specified in [2] and [5]. For example, this includes time-out of received Resv refreshes or receipt of an RSVP PathErr containing an ERROR_SPEC object with an... |
ca21a3998d34549327b3d05d69fb17e5 | 183 067 | 7.2 Pull mode (RCEF initiated Procedures) | |
ca21a3998d34549327b3d05d69fb17e5 | 183 067 | 7.2.1 Reservation pre-authorization | NOTE: The current release does not specify reservation pre-authorization for unicast pull-mode. |
ca21a3998d34549327b3d05d69fb17e5 | 183 067 | 7.2.2 Reservation establishment in pull mode | On receipt of an RSVP Resv message for a new on-path QoS reservation, the BTF shall process the RSVP message as per procedures specified in [1]. In case of RSVP message processing failure, the BTF shall behave in accordance with [1] (e.g. generate a ResvErr). In case of successful message processing, the BTF shall noti... |
ca21a3998d34549327b3d05d69fb17e5 | 183 067 | 7.2.3 Reservation Loss/Tear-Down | The BTF shall detect the loss or tear-down on an existing on-path QoS reservation. The detection is based on existing RSVP procedures as specified in [2] and [5]. For example, this includes: • time-out of received Resv refreshes; • receipt of a ResvTear; • receipt of an RSVP PathErr containing an ERROR_SPEC object with... |
ca21a3998d34549327b3d05d69fb17e5 | 183 067 | 7.2.4 Reservation Modification | The BTF shall detect the modification of an existing on-path QoS reservation (i.e. the change of one or more reservation parameters specified in the received Resv message). The BTF shall first process the RSVP message as per procedures specified in [1]. In case of RSVP message processing failure, the BTF shall behave i... |
ca21a3998d34549327b3d05d69fb17e5 | 183 067 | 8 RSVP to Re parameters mapping | |
ca21a3998d34549327b3d05d69fb17e5 | 183 067 | 8.1 Push Mode | |
ca21a3998d34549327b3d05d69fb17e5 | 183 067 | 8.1.1 Re PIR to RSVP Path Parameter Mapping | When, in accordance with clause 7.1.1.1, the RCEF/BTF sends an RSVP Path message to initiate an on-path QoS reservation as a result of a received Policy-Install-Request from RACS, the mapping defined in the following table shall be used: Table 8.1: Re PIR to RSVP Path Parameter mapping RSVP Objects Derivation from PIR ... |
ca21a3998d34549327b3d05d69fb17e5 | 183 067 | 8.2 Pull Mode | |
ca21a3998d34549327b3d05d69fb17e5 | 183 067 | 8.2.1 RSVP Resv to Re CCR Parameter Mapping | When, in accordance with clause 7.2.2, the RCEF/BTF sends a CCR request to RACS to request resource reservation as a result of a received RSVP Resv message, the mapping defined in the following table shall be used: Table 8.2: RSVP Resv to Re CCR Parameter mapping CCR AVP Derivation from RSVP Resv Flow-Description AVP I... |
ecb85a7739eb1fdb3cacaea64cc5c9a3 | 185 011 | 1 Scope | The present document describes the protocols used on the reference points defined for the Customer Network Device (CND) enabling the IMS-based IPTV service usage. This description is based on the architecture and stage 2 information flows contained in TS 185 009 [4], the architectural specifications of the Customer Net... |
ecb85a7739eb1fdb3cacaea64cc5c9a3 | 185 011 | 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... |
ecb85a7739eb1fdb3cacaea64cc5c9a3 | 185 011 | 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 TS 182 027 (V2.y.z): "Telecommunications and Int... |
ecb85a7739eb1fdb3cacaea64cc5c9a3 | 185 011 | 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 TR 185 004: "Telecommunications and Interne... |
ecb85a7739eb1fdb3cacaea64cc5c9a3 | 185 011 | 3 Definitions and abbreviations | |
ecb85a7739eb1fdb3cacaea64cc5c9a3 | 185 011 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: Customer Premises Network (CPN): in-house network composed by customer network gateway, customer network devices, network segments, network adapters and nodes NOTE 1: See TR 185 004 [i.1]. NOTE 2: Network segments are physical wired or... |
ecb85a7739eb1fdb3cacaea64cc5c9a3 | 185 011 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: ALG Application Layer Gateway B2BUA Back-to-Back User Agent BC BroadCast CDS Content Directory Service CND PPF CND Plug and Play Function CND Customer Network Device CND-AtF CND Attachment Function CNG Customer Network Gateway CNG-ACF CNG-Admi... |
ecb85a7739eb1fdb3cacaea64cc5c9a3 | 185 011 | 4 Overview | The clause briefly describes applicability of the protocols discussed further in the present document to the Reference Points and Functional Entities defined in TS 185 003 [3] and TS 185 009 [4]. NOTE: The IPTV CND functions are described within the specification document reference TS 185 009 [4]. 4.1 Overview of IPTV ... |
ecb85a7739eb1fdb3cacaea64cc5c9a3 | 185 011 | 4.1.1 Bridged mode | Reference points Gm, Xc, Xd, Ut, Xa all conforms to TS 183 063 [2]. Reference point e1 conforms to TS 183 019 [12]. Reference point e3 conforms to TS 183 065 [11]. |
ecb85a7739eb1fdb3cacaea64cc5c9a3 | 185 011 | 4.1.2 Routed mode | Reference points Xc, Xd, Ut, Xa conforms to TS 183 063 [2]. The e1 reference point is described in clause 5. The e3 reference point is described in clause 6. |
ecb85a7739eb1fdb3cacaea64cc5c9a3 | 185 011 | 4.1.2.1 Routed NGN mode | The C reference point is described in clause 14.1. The Gm reference point is described in clause 7.2. |
ecb85a7739eb1fdb3cacaea64cc5c9a3 | 185 011 | 4.1.2.2 Routed CPN mode | The C reference point is described in clause 14.2. The Gm' reference point is described in clause 15.1. |
ecb85a7739eb1fdb3cacaea64cc5c9a3 | 185 011 | 4.2 Data model information | Table 1 summarizes parameters to be provisioned in the CND, thanks to the CNGCF (reference point e3), through DHCP options (reference point e1') or by pre-configuration. Some kinds of data are grouped together, according to the SIP message types in which they are used: The table describes the data to be provisioned and... |
ecb85a7739eb1fdb3cacaea64cc5c9a3 | 185 011 | 5 Procedures at the e1 reference point | |
ecb85a7739eb1fdb3cacaea64cc5c9a3 | 185 011 | 5.1 IPTV-CND Operating in Bridged Mode | |
ecb85a7739eb1fdb3cacaea64cc5c9a3 | 185 011 | 5.1.1 Procedures for Network Attachment | The IPTV-CND follows network attachment procedures over the e1 reference point as defined in TS 183 019 [12]. |
ecb85a7739eb1fdb3cacaea64cc5c9a3 | 185 011 | 5.1.2 Procedures for SDF Discovery | The IPTV-CND should use vendor class ("ETSI_TISPAN_IPTV_SDS") DHCP options 43/60 or DHCP options 124/125 to fetch addresses of SDF and associated service provider information during network attachment as per procedures defined in TS 183 063 [2]. |
ecb85a7739eb1fdb3cacaea64cc5c9a3 | 185 011 | 5.1.3 Data model information | Table 2 summarizes the parameters which may be provisioned by the NGN network DHCP server or DNS SRV procedure to the IPTV-CND, through the e1 reference point. Table 2 Data Description (ref) P-CSCF Address Host name or IP address of the SIP Proxy IMS_IPTV_SP service provider name IMS-IPTV-SPDOMAIN service provider doma... |
ecb85a7739eb1fdb3cacaea64cc5c9a3 | 185 011 | 6 Procedures at the e3 reference point | 6.1 IPTV-CND Operating in Bridged Mode and Routed NGN mode |
ecb85a7739eb1fdb3cacaea64cc5c9a3 | 185 011 | 6.1.1 Procedures for remote management | The IPTV-CND is remotely managed over the e3 reference point using the CPE WAN Management Protocol (CWMP) as described in TS 183 065 [11]. The IPTV-CND should support the device data model for remote management as defined by the Broadband Forum, the TR-135 [i.4] model for STB published in December 2007. Additionally, a... |
ecb85a7739eb1fdb3cacaea64cc5c9a3 | 185 011 | 6.1.2 Procedures for SDF Discovery | The IPTV-CND may be optionally provisioned with the addresses of the SDF server and associated service provider information by the CNGCF using the CWMP protocol over the e3 reference point. The procedures are as described in TS 183 063 [2]. NOTE: The exact format of the IPTV objects will be as specified by appropriate ... |
ecb85a7739eb1fdb3cacaea64cc5c9a3 | 185 011 | 6.1.3 Procedures for NAT traversal (applicable only in routed mode) | The NAT-traversal procedures described in the TR-069 specification Annex G [i.5] should be used to manage a CND through the CNG NAT. |
ecb85a7739eb1fdb3cacaea64cc5c9a3 | 185 011 | 6.1.4 Data model information | Table 3 summarizes the parameters provisioned by the CNGCF to the IPTV-CND through the e3 reference point. Table 3 Data Description (ref) IMPI Authentication Username for IMS authentication IMPU SIP URI P-CSCF Address Host name or IP address of the SIP Proxy Registrar Server Host name or IP address of the SIP registrar... |
ecb85a7739eb1fdb3cacaea64cc5c9a3 | 185 011 | 7 Procedures at the Gm reference point | |
ecb85a7739eb1fdb3cacaea64cc5c9a3 | 185 011 | 7.1 IPTV-CND Operating in Bridged Mode | The procedures for IMS registration, Service Attachment, BC Service, CoD Service, IPTV Presence, BC with trick plays, NPVR Service and Service Configuration follow TS 183 063 [2]. |
ecb85a7739eb1fdb3cacaea64cc5c9a3 | 185 011 | 7.2 IPTV-CND Operating in Routed NGN Mode | |
ecb85a7739eb1fdb3cacaea64cc5c9a3 | 185 011 | 7.2.1 Procedures for IMS Registration | Conforms to TS 183 063 [2]. |
ecb85a7739eb1fdb3cacaea64cc5c9a3 | 185 011 | 7.2.2 Procedures for Service attachment | Conforms to TS 183 063 [2]. |
ecb85a7739eb1fdb3cacaea64cc5c9a3 | 185 011 | 7.2.3 Procedures for BC service | Conforms to TS 183 063 [2]. ETSI ETSI TS 185 011 V2.1.1 (2009-07) 14 |
ecb85a7739eb1fdb3cacaea64cc5c9a3 | 185 011 | 7.2.4 Procedures for CoD service | Conforms to TS 183 063 [2]. |
ecb85a7739eb1fdb3cacaea64cc5c9a3 | 185 011 | 7.2.5 Procedures for Services Configuration | Conforms to TS 183 063 [2]. |
ecb85a7739eb1fdb3cacaea64cc5c9a3 | 185 011 | 7.2.6 Procedures for IPTV Presence | Conforms to TS 183 063 [2]. |
ecb85a7739eb1fdb3cacaea64cc5c9a3 | 185 011 | 7.2.7 Procedures for NPVR service | Conforms to TS 183 063 [2]. |
ecb85a7739eb1fdb3cacaea64cc5c9a3 | 185 011 | 7.2.8 Procedures for NAT traversal | The CNG NAT-traversal may be performed using the P-CSCF functionalities described in TS 123 228 [13], annex G and RACS specified in ES 282 003 [14]. NOTE: The SIP ALG in the CNG-SIP Proxy B2BUA may be an alternative to the network-based NAT-traversal mechanism, in this case the CND should use the Gm' reference point. |
ecb85a7739eb1fdb3cacaea64cc5c9a3 | 185 011 | 7.3 Data model information | To retrieve parameters provisioned through Gm reference point, see TS 183 063 [2], clause 5.2.2.3. |
ecb85a7739eb1fdb3cacaea64cc5c9a3 | 185 011 | 8 Procedures at the Ut reference point | |
ecb85a7739eb1fdb3cacaea64cc5c9a3 | 185 011 | 8.1 IPTV-CND Operating in Bridged Mode | The procedures for managing service action data follow TS 183 063 [2]. |
ecb85a7739eb1fdb3cacaea64cc5c9a3 | 185 011 | 8.2 IPTV-CND Operating in Routed NGN Mode | The procedures for managing service action data follow TS 183 063 [2]. |
ecb85a7739eb1fdb3cacaea64cc5c9a3 | 185 011 | 8.3 Data model information | To retrieve parameters provisioned through Ut reference point, see TS 183 063 [2], annex C. |
ecb85a7739eb1fdb3cacaea64cc5c9a3 | 185 011 | 9 Procedures at the Xa reference point | |
ecb85a7739eb1fdb3cacaea64cc5c9a3 | 185 011 | 9.1 IPTV-CND Operating in Bridged Mode | The procedures for service selection follow TS 183 063 [2]. ETSI ETSI TS 185 011 V2.1.1 (2009-07) 15 |
ecb85a7739eb1fdb3cacaea64cc5c9a3 | 185 011 | 9.2 IPTV-CND Operating in Routed (NGN/CPN) Mode | The procedures for service selection follow TS 183 063 [2]. |
ecb85a7739eb1fdb3cacaea64cc5c9a3 | 185 011 | 9.3 Data model information | To retrieve parameters provisioned through Xa reference point, see TS 183 063 [2], annex J. |
ecb85a7739eb1fdb3cacaea64cc5c9a3 | 185 011 | 10 Procedures at the Xc reference point | |
ecb85a7739eb1fdb3cacaea64cc5c9a3 | 185 011 | 10.1 IPTV-CND Operating in Bridged Mode | The procedures for media control for CoD service and BC with trick plays follow TS 183 063 [2]. |
ecb85a7739eb1fdb3cacaea64cc5c9a3 | 185 011 | 10.2 IPTV-CND Operating in Routed NGN Mode | The procedures for media control for CoD service and BC with trick plays follow TS 183 063 [2]. |
ecb85a7739eb1fdb3cacaea64cc5c9a3 | 185 011 | 10.2.1 Procedures for NAT traversal | NOTE: NAT traversal support on Xc is out of the scope of the present document. |
ecb85a7739eb1fdb3cacaea64cc5c9a3 | 185 011 | 10.3 IPTV-CND Operating in Routed CPN Mode | The procedures for media control for CoD service and BC with trick plays follow TS 183 063 [2]. |
ecb85a7739eb1fdb3cacaea64cc5c9a3 | 185 011 | 11 Procedures at the Xd reference point | |
ecb85a7739eb1fdb3cacaea64cc5c9a3 | 185 011 | 11.1 IPTV-CND Operating in Bridged Mode | All procedures at this reference point follow TS 183 063 [2]. |
ecb85a7739eb1fdb3cacaea64cc5c9a3 | 185 011 | 11.2 IPTV-CND Operating in Routed NGN Mode | The procedures for media delivery for CoD service, BC service, NPVR service and BC with trick play follow TS 183 063 [2]. |
ecb85a7739eb1fdb3cacaea64cc5c9a3 | 185 011 | 11.2.1 Procedures for NAT traversal | To keep NAT bindings and firewall pinholes open with unidirectional RTP traffic early media (empty RTP packets) shall be sent by the IPTV CND so as to open CNG NAT pinholes before receiving media flows from the NGN. This is described in ES 283 003 [9], annex F.4a. |
ecb85a7739eb1fdb3cacaea64cc5c9a3 | 185 011 | 11.3 IPTV-CND Operating in Routed CPN Mode | The procedures for media delivery for CoD service, BC service, NPVR service and BC with trick play follow TS 183 063 [2]. ETSI ETSI TS 185 011 V2.1.1 (2009-07) 16 |
ecb85a7739eb1fdb3cacaea64cc5c9a3 | 185 011 | 11.3.1 Procedures for NAT traversal | NAT traversal for media delivery in CNG may be performed by the CNG - SIP Proxy B2BUA TS 185 010 [5] based on Gm' signalling. This mechanism performs a NAT binding between the IPTV CND receiver IP address (and port) and the NGN side CNG receiving port, for incoming media delivery. NOTE: The solution above works for CoD... |
ecb85a7739eb1fdb3cacaea64cc5c9a3 | 185 011 | 12 Procedures at the e1' reference point | |
ecb85a7739eb1fdb3cacaea64cc5c9a3 | 185 011 | 12.1 IPTV-CND Operating in Routed (NGN/CPN) Mode | |
ecb85a7739eb1fdb3cacaea64cc5c9a3 | 185 011 | 12.2 Procedures for network attachment | The e1' reference point serves the CND-AtF with appropriate configuration data to connect to a local IP network and attach to some selected services such as the P-CSCF. The protocol of choice is DHCP (RFC 2131 [15]). The DHCP options needed to implement this procedure are described in TS 185 010 [5]. In addition to the... |
ecb85a7739eb1fdb3cacaea64cc5c9a3 | 185 011 | 12.3 Data model information | In the case the IPTV-CND does not go through the CNG-SIP B2BUA (Routed NGN Mode), the IPTV-CND shall be provisioned with the following parameter. Table 4 Data Description (ref) Entity responsible for the provisioning P-CSCF Address Host name or IP address of the SIP Proxy CNG DHCP server (option 120) |
ecb85a7739eb1fdb3cacaea64cc5c9a3 | 185 011 | 12.4 CNG | |
ecb85a7739eb1fdb3cacaea64cc5c9a3 | 185 011 | 12.4.1 Procedures for network attachment | When the IPTV CND is sending the DHCP request to the CNG including options to get SDF discovery information, the CNG should provide the requested information to the IPTV CND as described TS 183 063 [2], annex I. NOTE: Other methods to configure P-CSCF and SDF addresses exist, see clause 4.2. |
ecb85a7739eb1fdb3cacaea64cc5c9a3 | 185 011 | 12.4.2 Data model information | In the case the IPTV-CND goes through the CNG-SIP B2BUA (Routed CPN Mode), the CNG has to be provisioned with the following parameters, so as to connect non-IMS CND to the IMS Network (e.g. replacing the CNG-SIP proxy Address by the P-CSCF Address). ETSI ETSI TS 185 011 V2.1.1 (2009-07) 17 Table 5 Data Description (ref... |
ecb85a7739eb1fdb3cacaea64cc5c9a3 | 185 011 | 13 Procedures at the e3' reference point | NOTE: This clause is not elaborated in Release 2. |
ecb85a7739eb1fdb3cacaea64cc5c9a3 | 185 011 | 14 Procedures at the C reference point | Utilization of reference point C in Release 2 for IPTV services is limited to three service offers: Broadcast, CoD and NPVR offers. In such a limited scope of offers, reference point C is only partially described within the present document. Routed NGN and Routed CPN modes can be used in parallel. |
ecb85a7739eb1fdb3cacaea64cc5c9a3 | 185 011 | 14.1 IPTV-CND Operating in Routed NGN Mode | |
ecb85a7739eb1fdb3cacaea64cc5c9a3 | 185 011 | 14.1.1 Procedures for Content description Functions | |
ecb85a7739eb1fdb3cacaea64cc5c9a3 | 185 011 | 14.1.1.1 Procedures for Synchronization of Device List | The IPTV-CND PPF can collect available UPnP™ devices either at a regular interval (polling mode) or by listening to proper events (notification mode) in accordance with UPnP™ Device Architecture 1.0 (UPnP™ AV 1.0 Specifications, UPnP Forum [6]). This is done using M-SEARCH and NOTIFY messages. |
ecb85a7739eb1fdb3cacaea64cc5c9a3 | 185 011 | 14.1.1.2 Procedures for Collecting Media List | The IPTV-CND PPF can collect available UPnP™ media items either at a regular interval (polling mode) or by listening to proper events (notification mode) in accordance with UPnP™ AV 1.0. This is done using UPnP AV messages. The IPTV-CND PPF should use UPnP™ AV CDS::Browse and CDS::Search actions to retrieve the list of... |
ecb85a7739eb1fdb3cacaea64cc5c9a3 | 185 011 | 14.1.1.3 Procedure for Exposing Media List | The IPTV-CND PPF can expose available UPnP media items. Three cases are possible: • Those media items can be locally stored within the device where the IPTV-CND PPF resides. The UPnP™ AV architecture is used. The Content Directory Service exposes the list of media items. ETSI ETSI TS 185 011 V2.1.1 (2009-07) 18 • Those... |
ecb85a7739eb1fdb3cacaea64cc5c9a3 | 185 011 | 15 Procedures at the Gm' reference point |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.