hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
e89e5c9e50d911bf0957c3e2309fd124 | 132 106-8 | 3.1.1 IRPAgent | ........................................................................................................................................................... 7 |
e89e5c9e50d911bf0957c3e2309fd124 | 132 106-8 | 3.1.2 IRPManager | ....................................................................................................................................................... 7 |
e89e5c9e50d911bf0957c3e2309fd124 | 132 106-8 | 3.1.3 Managed Object and Network Resource | ........................................................................................................... 7 |
e89e5c9e50d911bf0957c3e2309fd124 | 132 106-8 | 3.1.4 Name | .................................................................................................................................................................. 7 |
e89e5c9e50d911bf0957c3e2309fd124 | 132 106-8 | 3.1.5 Name space | ........................................................................................................................................................ 7 |
e89e5c9e50d911bf0957c3e2309fd124 | 132 106-8 | 3.1.6 Global Root and Local Root | .............................................................................................................................. 7 |
e89e5c9e50d911bf0957c3e2309fd124 | 132 106-8 | 3.1.7 Distinguished Name and Relative Distinguished Name | .................................................................................... 8 |
e89e5c9e50d911bf0957c3e2309fd124 | 132 106-8 | 3.2 Abbreviations | .......................................................................................................................................................... 8 |
e89e5c9e50d911bf0957c3e2309fd124 | 132 106-8 | 4 System overview | ......................................................................................................................................9 |
e89e5c9e50d911bf0957c3e2309fd124 | 132 106-8 | 4.1 System context | ........................................................................................................................................................ 9 |
e89e5c9e50d911bf0957c3e2309fd124 | 132 106-8 | 5 Name Convention for Managed Objects | ..................................................................................................9 |
e89e5c9e50d911bf0957c3e2309fd124 | 132 106-8 | 6 Representations of DN | .............................................................................................................................9 |
e89e5c9e50d911bf0957c3e2309fd124 | 132 106-8 | 7 String Representation of DN | ..................................................................................................................10 |
e89e5c9e50d911bf0957c3e2309fd124 | 132 106-8 | 7.1 Converting DN from ASN.1 to a String | ................................................................................................................ 10 |
e89e5c9e50d911bf0957c3e2309fd124 | 132 106-8 | 7.1.1 Converting RDNSequence | ............................................................................................................................ 10 |
e89e5c9e50d911bf0957c3e2309fd124 | 132 106-8 | 7.1.2 Converting RelativeDistinguishedName | ........................................................................................... 10 |
e89e5c9e50d911bf0957c3e2309fd124 | 132 106-8 | 7.1.3 Converting AttributeTypeAndValue | .................................................................................................... 10 |
e89e5c9e50d911bf0957c3e2309fd124 | 132 106-8 | 7.2 Character syntax | .................................................................................................................................................... 10 |
e89e5c9e50d911bf0957c3e2309fd124 | 132 106-8 | 7.3 BNF of DN String Representation | ......................................................................................................................... 11 |
e89e5c9e50d911bf0957c3e2309fd124 | 132 106-8 | 7.4 Maximum size of DN string | .................................................................................................................................. 11 |
e89e5c9e50d911bf0957c3e2309fd124 | 132 106-8 | 8 Examples of DN in string representation | ...............................................................................................11 |
e89e5c9e50d911bf0957c3e2309fd124 | 132 106-8 | 9 Usage Scenario | ......................................................................................................................................12 |
e89e5c9e50d911bf0957c3e2309fd124 | 132 106-8 | 9.1 DN prefix usage | ..................................................................................................................................................... 12 Annex A (normative): Mapping of RDN AttributeType to Strings..........................................13 Annex B (normative): Rule for MO Designers regarding Attribute... |
ae0a5fe2a126eb7de0c6ec5c06eaed37 | 181 006 | 1 Scope | The present document defines the requirements for a Direct Communication which may be supported by a TISPAN NGN. These requirements form the basis for the definition of network capabilities. These requirements are an endorsement of the OMA requirements specifications. The present document only provides requirements for... |
ae0a5fe2a126eb7de0c6ec5c06eaed37 | 181 006 | 2 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document. • 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. • ... |
ae0a5fe2a126eb7de0c6ec5c06eaed37 | 181 006 | 3 Definitions and abbreviations | |
ae0a5fe2a126eb7de0c6ec5c06eaed37 | 181 006 | 3.1 Definitions | For the purposes of the present document, the terms and definitions given in OMA-RD-PoC-V1 [1] apply. |
ae0a5fe2a126eb7de0c6ec5c06eaed37 | 181 006 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviation applies: DC Direct Communication ETSI ETSI TS 181 006 V2.1.1 (2006-11) 6 4 Endorsement of OMA (Open Mobile Alliance) OMA-ERELD-PoC-V1; Enabler Release Definition for Push-to-Talk over Cellular The elements of OMA-ERELD-PoC-V1 [2] apply, with the follo... |
ae0a5fe2a126eb7de0c6ec5c06eaed37 | 181 006 | 4.1 Modifications to OMA-ERELD-PoC-V1 | General: Throughout the present document: • "Push-to-Talk over Cellular" is replaced by "Direct Communication"; • "PoC" is replaced by "DC"; • "3GPP IMS" is replaced by "3GPP/TISPAN IMS". Clause 3.2 Modify the definition of Service Instance by: Service Instance: a Service Instance is the instantiation of a logical conn... |
ae0a5fe2a126eb7de0c6ec5c06eaed37 | 181 006 | 5.1 Modifications to OMA-RD-PoC-V1 | General: Throughout the present document: • "Push-to-Talk over Cellular" is replaced by "Direct Communication"; • "PoC" is replaced by "DC"; • "radio resources" is replaced by "radio and/or fixed access resources"; • "mobile network" is replaced by "mobile/fixed network"; • "mobile phone" is replaced by "mobile/fixed p... |
d4763978937007086749bc87bda933cc | 182 019 | 1 Scope | The present document describes the Content Delivery Network (CDN) functional architecture, the interconnection with IMS-based and NGN Integrated IPTV solutions and user-related procedures in relationship with the unicast stored (e.g. content download) and streaming (e.g. CoD) services as defined in TS 181 016 [1]. |
d4763978937007086749bc87bda933cc | 182 019 | 2 References | References are either specific (identified by date of publication and/or edition number or version number) or non-specific. For specific references, only the cited version applies. For non-specific references, the latest version of the reference document (including any amendments) applies. Referenced documents which ar... |
d4763978937007086749bc87bda933cc | 182 019 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ETSI TS 181 016: "Telecommunications and Internet converged Services and Protocols for Advanced Networking (TISPAN); Service Layer Requirements to integrate NGN services and IPTV". [2] ETSI TS 182 027: "Telecommunications ... |
d4763978937007086749bc87bda933cc | 182 019 | 2.2 Informative references | The following referenced documents are not necessary for the application of the present document but they assist the user with regard to a particular subject area. [i.1] ETSI TS 102 990: "Media Content Distribution (MCD); CDN Interconnection, use cases and requirements". |
d4763978937007086749bc87bda933cc | 182 019 | 3 Definitions and abbreviations | |
d4763978937007086749bc87bda933cc | 182 019 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: consumer: entity where the content is consumed content acquisition: act of acquiring content from a content source content delivery: act of delivering deployed content to a user ETSI ETSI TS 182 019 V3.1.2 (2011-09) 8 Content Delivery ... |
d4763978937007086749bc87bda933cc | 182 019 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: ALF Asset Location Function CCF Cluster Controller Function C-COF Control plane COF CDF Content Delivery Function CDN Content Delivery Network CDNCF Content Delivery Network Control Function CoD Content on Demand COF Content Origin Function D-... |
d4763978937007086749bc87bda933cc | 182 019 | 4 General description of CDN | A Content Delivery Network (CDN) is a collaborative collection of components, where content is replicated over several mirrored servers in order to perform transparent and effective delivery of content to end users. ETSI ETSI TS 182 019 V3.1.2 (2011-09) 9 The major stages of CDN are: • Content acquisition: Acquiring co... |
d4763978937007086749bc87bda933cc | 182 019 | 4.1 Functional roles and CDN relationships | The present document describes the TISPAN CDN architecture, the interconnection of CDNs in the user-facing service delivery network, including the interfacing with IPTV subsystems defined in TS 182 027 [2] and TS 182 028 [3], and CDN content ingestion. For the purpose of the present document, concepts of domains, and r... |
d4763978937007086749bc87bda933cc | 182 019 | 4.2 High level functional overview | The following picture shows the main components of a CDN. Figure 4.2.1: Architectural components of a CDN The content deployment component is in charge of generating copies of content inside the CDN and controls the procedure of content deployment. When content is ingested from a content source (i.e. content provider, ... |
d4763978937007086749bc87bda933cc | 182 019 | 4.3 Requirements | |
d4763978937007086749bc87bda933cc | 182 019 | 4.3.1 CDN Functional Requirements | 4.3.1.1 The CDN solution shall support both IMS-based and NGN Integrated IPTV subsystems. 4.3.1.2 The CDN solution shall support content delivery for one or more multimedia systems. 4.3.1.3 The CDN solution should support content delivery for more than one kind of multimedia service systems. 4.3.1.4 The CDN solution sh... |
d4763978937007086749bc87bda933cc | 182 019 | 4.3.3 CDN non-functional requirements | 4.3.3.1 The CDN solution should provide geographical scalability maintaining performances and effectiveness from a limited local area deployment to a more geographically distributed pattern. 4.3.3.2 The CDN solution shall provide support for high availability (i.e. server mirroring, dynamic traffic forwarding, etc.). 4... |
d4763978937007086749bc87bda933cc | 182 019 | 5.1 General description | The Content Delivery Network (CDN) allows the optimization of the network use through a distribution of the content delivery servers in the physical network, and the optimization of the storage resources through mechanisms such as popularity-based distribution of the content on the content servers. Figure 5.1.1 shows t... |
d4763978937007086749bc87bda933cc | 182 019 | 5.2 Functional entities | The Content Delivery Network contains one or more Content Delivery Functions (CDF) grouped geographically or administratively in clusters. The CDFs in one cluster are controlled by a specific Cluster Controller Function (CCF). One or more CCFs are controlled by the Content Delivery Network Controller Function (CDNCF). ... |
d4763978937007086749bc87bda933cc | 182 019 | 5.2.1 Content Delivery Network Controller Function (CDNCF) | The Content Delivery Network Controller Function (CDNCF) is the function which manages one or more clusters. One or more CDN Controller Functions may coexist in the same CDN and may interact for the purpose of selecting the most appropriate cluster. There are two approaches with different outcomes for processing within... |
d4763978937007086749bc87bda933cc | 182 019 | 5.2.2 Cluster Controller Function (CCF) | The Cluster Controller Function (CCF) manages a set of content delivery functions (i.e. a cluster of CDFs). It is in charge of selecting the appropriate CDF within the cluster and controlling access from UE to the selected CDF. Tasks of CCF are: • Selecting the best suited CDF based on criteria which may include, but a... |
d4763978937007086749bc87bda933cc | 182 019 | 5.2.3 Content Delivery Function (CDF) | Tasks of Content Delivery Function (CDF) are: • Handling content delivery (for delivering multimedia content to user). • Reporting status to CCF (e.g. reporting on load status). • Reporting content availability to CCF (e.g. content has been acquired or deleted). • Handling trick mode commands from the UE. • Reporting o... |
d4763978937007086749bc87bda933cc | 182 019 | 5.2.4 Asset Location Function (ALF) | The Asset Location Function is a functional entity having the knowledge of the available content, the content location and others content parameters (e.g. category, popularity, size, media type, generator source, etc.). Having these parameters allows the ALF to provide a cluster list to the CDNCF, which will select an ... |
d4763978937007086749bc87bda933cc | 182 019 | 5.2.5 Content Origin Function (COF) | The Content Origin Function is a functional entity in charge of content ingestion. COF C-COF D-COF Figure 5.2.5.1: COF elementary functions The COF functional entity is composed of two elementary functions: • C-COF (Control plane COF) whose task is handling content ingestion signalling, such as: - Processing content in... |
d4763978937007086749bc87bda933cc | 182 019 | 5.3 Overall architecture and reference points | Figure 5.3.1 is an overall view of the TISPAN CDN architecture, showing the functional elements and reference points. Figure 5.3.1: Overall view of CDN architecture Reference points shown in figure 5.3.1 are specified in clause 6 of the present document. NOTE: Implementation of the CDN architecture may utilize multiple... |
d4763978937007086749bc87bda933cc | 182 019 | 5.4 Relationship between IPTV subsystem and CDN | The relationship between CDN and IMS-based IPTV, NGN integrated IPTV subsystem may be realized as shown in figure 5.4.1. The IPTV subsystem may be an IMS-based or NGN integrated subsystem. Content Delivery Network IPTV Subsystem UE Xc' Xd' Ys Yp Xc'' Ct Cu/Qc Cluster Yp CDNCF CCF CDF CDF ALF Qq Yy Ys Yp CCF CDF CDNCF Q... |
d4763978937007086749bc87bda933cc | 182 019 | 6 Reference points | |
d4763978937007086749bc87bda933cc | 182 019 | 6.1 CDNCF - CCF (Ys) | This reference point between CDNCF and CCF allows the CDNCF to hand over a content request to a specific CCF selected by the CDNCF using the local policy and the list of addresses where the content is available provided by the ALF. It also allows each CCF to report the status of the cluster regarding content availabili... |
d4763978937007086749bc87bda933cc | 182 019 | 6.2 CCF - CDF (Yp) | This reference point between CCF and CDF is used for CCF to control content delivery flow. It also allows CDF status reporting to the CCF and the CCF to request a CDF to acquire content. |
d4763978937007086749bc87bda933cc | 182 019 | 6.3 CCF - UE (Xc') | This reference point between CCF and UE is used to exchange content control messages for controlling the IPTV content flow, (i.e. trick mode commands in case of streaming). Content Delivery Network 1 Ys Yp Cluster CCF ALF Yy Qq CDNCF CDF CDF Cf Yp Content Delivery Network 2 Ys Yp Cluster CCF CDNCF CDF CDF Cf Yp Yy Qq Y... |
d4763978937007086749bc87bda933cc | 182 019 | 6.4 CDF - UE (Xc'') | This optional reference point between CDF and UE is used to exchange content control messages for controlling the IPTV content flow, i.e. trick mode commands. NOTE 1: The Xc'' reference point performs the same tasks with the reference point Xc (TS 182 027 [2] and TS 182 028 [3]), the difference is Xc connected to MCF (... |
d4763978937007086749bc87bda933cc | 182 019 | 6.5 CDF - UE (Xd') | This reference point between CDF and UE is used to deliver the content to UE. NOTE: The Xd' reference point performs the same tasks with the reference point Xd (TS 182 027 [2] and TS 182 028 [3]), the difference is Xd connected to MDF (TS 182 027 [2] and TS 182 028 [3]), but the Xd' connected to CDF. |
d4763978937007086749bc87bda933cc | 182 019 | 6.6 CDNCF - CDNCF (Yq) | The Yq reference point is used to allow a CDNCF to proxy a request to another CDNCF for handling. This reference point may exist between two CDNCFs belonging to different TISPAN CDNs. |
d4763978937007086749bc87bda933cc | 182 019 | 6.7 CDF-CDF (Cf) | The Cf reference point between CDF and CDF allows delivering content between the two CDFs for content distribution. The CDF is always instructed where to go to acquire content. This reference point may exist between two CDFs belonging to different TISPAN CDNs. |
d4763978937007086749bc87bda933cc | 182 019 | 6.8 CDNCF - IPTV subsystem (Cu) | The Cu reference point between CDNCF and IPTV subsystem carries IPTV service control signalling originating from the IPTV subsystem to CDNCF. |
d4763978937007086749bc87bda933cc | 182 019 | 6.8.1 CDNCF - IMS-based IPTV subsystem | In the case of an IMS-based IPTV subsystem, the Cu reference point performs the same tasks as the reference point y2 (TS 182 027 [2]). The difference is that y2 connected to the MCF (TS 182 027 [2]), but Cu is connected to a CDNCF. |
d4763978937007086749bc87bda933cc | 182 019 | 6.8.2 CDNCF - NGN integrated IPTV subsystem | In the case of an NGN Integrated IPTV subsystem, the Cu reference point performs the same tasks as the reference point Sa (TS 182 028 [3]). The difference is that Sa connected to the MCF (TS 182 028 [3]), but Cu is connected to a CDNCF. |
d4763978937007086749bc87bda933cc | 182 019 | 6.9 CDNCF - IPTV subsystem (Qc) | The Qc reference point between CDNCF and IPTV subsystem allows the IPTV subsystem to query the CDNCF for the CCF to be contacted for content. ETSI ETSI TS 182 019 V3.1.2 (2011-09) 23 |
d4763978937007086749bc87bda933cc | 182 019 | 6.10 CCF - IPTV subsystem (Ct) | The Ct reference point between CCF and IPTV subsystem carries IPTV service control signalling originating from the IPTV subsystem to CCF. The selected CCF must fulfil the request or return an error. Redirection or relay outside the CDN is not supported. |
d4763978937007086749bc87bda933cc | 182 019 | 6.10.1 CCF - IMS-based IPTV subsystem | In the case of an IMS-based IPTV subsystem, the Ct reference point performs the same tasks as the reference point y2 (TS 182 027 [2]). The difference is that y2 connected to MCF (TS 182 027 [2]), but Ct is connected to CCF. |
d4763978937007086749bc87bda933cc | 182 019 | 6.10.2 CCF - NGN Integrated IPTV subsystem | In the case of an NGN Integrated IPTV subsystem, the Ct reference point performs the same tasks as the reference point Sa (TS 182 028 [3]). The difference is that Sa connected to MCF (TS 182 028 [3]), but Ct is connected to CCF. |
d4763978937007086749bc87bda933cc | 182 019 | 6.11 CDNCF - ALF (Qq) | The Qq reference point between CDNCF and ALF allows the CDNCF to query the ALF about the addresses having the requested content. The Qq reference point allows the ALF to ask the CDNCF to instruct the CCF to acquire content after receiving a request from the COF. This reference point also allows the CDNCF to query the c... |
d4763978937007086749bc87bda933cc | 182 019 | 6.12 ALF - ALF (Qq') | The Qq' reference point between ALFs allows one ALF to query another about the addresses having the requested content. It can be considered a subset of the Qq reference point between CDNCF and ALF. This reference point may exist between two ALFs belonging to different CDNs. |
d4763978937007086749bc87bda933cc | 182 019 | 6.13 ALF - CCF (Yy) | The Yy reference point between ALF and CCF allows the CCF to send information on the content availability of the clusters, and may also be used by the CCF to query the content's parameters (e.g. category, popularity, generator source, etc.) from the ALF. The CCF may also utilize the Yy reference point to verify content... |
d4763978937007086749bc87bda933cc | 182 019 | 6.14 ALF - COF (Yv) | The Yv reference point between ALF and COF allows the COF to notify the ALF that content is available. This reference point also allows the ALF to request the COF to ingest content. |
d4763978937007086749bc87bda933cc | 182 019 | 6.15 COF - CDF (Cf') | The Cf' reference point between COF and CDF is used to deliver content between CDF and the content origin function. The CF' reference point may also be used by the CDF to deliver content (e.g. UGC) to the COF for ingestion in the CDN, or to the COF of another CDN. |
d4763978937007086749bc87bda933cc | 182 019 | 6.16 COF - COF (Cf'') | The Cf'' reference point between two separate COFs is used to deliver content between two content origin functions. ETSI ETSI TS 182 019 V3.1.2 (2011-09) 24 |
d4763978937007086749bc87bda933cc | 182 019 | 7 Procedures | NOTE: In the following clauses, when the core IMS is used, i.e. for an IMS-based IPTV subsystem, signalling between any 2 nodes involving the IPTV subsystem, CDNCF, and CCF goes through the IMS core. |
d4763978937007086749bc87bda933cc | 182 019 | 7.1 Request routing within CDN | This procedure describes all possible outcomes within CDN for routing a session. The routing procedure can be invoked from any CDN session establishment procedure that requires CDN request routing support to deliver the requested content to a UE. This applies to both IMS-based and NGN Integrated IPTV subsystems. Reques... |
d4763978937007086749bc87bda933cc | 182 019 | 7.1.1 CDN request routing resolves to a CDF - content available | The procedure below shows the case where the configured CDNCF selects a CDF to serve the requested content. 1. Request for Content CDNCF-1 ALF CCF-2 CDF-2 CDNCF-2 3. Request for Content CCF-1 CDF-1 6. Response COF 2. Locate CCF IPTV Subsystem 7. Response 5. Establish Delivery Session as per steps 5 to 7 in section 7.6.... |
d4763978937007086749bc87bda933cc | 182 019 | 7.1.2 CDN request routing resolves to a CDF - dynamic acquisition | In some scenarios, the content may not yet be available on the selected CDF. In these scenarios, dynamic acquisition of the content is triggered into the CDN. There are three cases that are considered here for such dynamic acquisition. In the first case, depicted in clause 7.1.2.1, the CCF triggers early dynamic acquis... |
d4763978937007086749bc87bda933cc | 182 019 | 7.1.2.1 CDN request routing resolves to the CDF - early dynamic acquisition | The procedure below shows the case of early dynamic acquisition, and where the requested content is located in the COF. In this case, the CDNCF instructs a CCF to download the content from the COF before the delivery session is established. The content will be retrieved from the COF and (after delivery initiation is re... |
d4763978937007086749bc87bda933cc | 182 019 | 7.1.3 CDN request routing resolves to a redirect to a new CDNCF | The procedure below shows the case where a CDF able to fulfil the request could not be located by the configured CDNCF, and where instead, a redirect to another CDNCF is returned to the IPTV subsystem. This case is only applicable when the incoming request from the IPTV subsystem to the CDNCF does not require the simul... |
d4763978937007086749bc87bda933cc | 182 019 | 7.1.5 CDN request routing for unicast content download | The initial request from the IPTV subsystem shall include an indication to distinguish a content download session from a content streaming session. For content download sessions, each node in the CDN, based on its internal policies, may decide to return its address to the IPTV subsystem, or locate another node that can... |
d4763978937007086749bc87bda933cc | 182 019 | 7.2.1 Service approach: common procedures | |
d4763978937007086749bc87bda933cc | 182 019 | 7.2.1.1 Unicast streaming session Initiation - service approach | The following sequence depicts the procedure for unicast streaming delivery. Figure 7.2.1.1.1: Unicast streaming session initiation procedure - service approach 1) The UE initiates a CoD related request to the IPTV subsystem. 2) The IPTV subsystem sends an initiation request to CDNCF. 3) In this case, the CDNCF follows... |
d4763978937007086749bc87bda933cc | 182 019 | 7.2.1.2 Service approach: CDNCF query to ALF | Figure 7.2.1.2.1: Content delivery for IPTV request (service approach) 1) The UE initiates a content request which contains the content identifier and the UE's location information (e.g. the IP address) to the IPTV subsystem. 2) The IPTV subsystem initiates a request to the CDNCF for the location of the optimal CDF for... |
d4763978937007086749bc87bda933cc | 182 019 | 7.2.2.1 Unicast streaming session initiation (no session delivery established) | This clause describes the common CDN implications for processing the UE initiated unicast streaming service described in clause 8.4.1.1.1, and the SCF initiated unicast streaming service described in clause 8.4.1.1.2 of TS 182 027 [2]. Figure 7.2.1.1.1 outlines the different steps and messages exchanged between the CDN... |
d4763978937007086749bc87bda933cc | 182 019 | 7.2.2.2 UE initiated unicast streaming session modification for IMS based IPTV | This clause describes the CDN implications for processing a UE initiated unicast streaming session Modification described in clause 8.4.2.0A of TS 182 027 [2]. Session modification is used to assign or renegotiate one or more content control and/or delivery channels in a session. Figure 7.2.2.3.1 outlines the different... |
d4763978937007086749bc87bda933cc | 182 019 | 7.2.2.3 CDN initiated unicast streaming session modification for IMS based IPTV | This clause describes the CDN implications for processing a CDN initiated unicast streaming session Modification described in clause 8.4.2.0B of TS 182 027 [2]. Session modification is used to assign or renegotiate one or more content control and/or delivery channels in a session. Figure 7.2.2.3.1 outlines the differen... |
d4763978937007086749bc87bda933cc | 182 019 | 7.2.2.4 SCF initiated unicast streaming session modification for IMS based IPTV | This clause describes the CDN implications for processing an SCF initiated unicast streaming session Modification request. Session modification is used to assign or renegotiate one or more content control and/or delivery channels in a session. The SCF initiates a session modification request routed by the Core IMS enti... |
d4763978937007086749bc87bda933cc | 182 019 | 7.2.2.5 Restricted (forced-playout policies) | The procedure for forced playout policies (restricted trickplay) of a content item has the same procedures as depicted in clause 7.2.1.1, with the following differences. Step (2) The IPTV subsystem sends a session initiation request to CDNCF, and also indicates the content shall have restricted playback. The restrictio... |
d4763978937007086749bc87bda933cc | 182 019 | 7.2.3.1 UE initiated unicast streaming session initiation - coupled mode | Figure 7.2.3.1.1 provides an overview of the information flows for content delivery flow for NGN integrated IPTV. Figure 7.2.3.1.1: Content delivery flow for NGN integrated IPTV 1) The UE initiates a dialogue to the CoD service as described in steps 1 to 7 in clause 11.2 of TS 182 028 [3]. 2) UE initiates a request to ... |
d4763978937007086749bc87bda933cc | 182 019 | 7.3.1 Query approach: common procedures | |
d4763978937007086749bc87bda933cc | 182 019 | 7.3.1.1 Query approach: CDNCF (ALF) query | The call flows depict the setup for a content delivery channel using the query approach. Figure 7.3.1.1.1: Content delivery for IPTV request via query approach 1) The UE initiates a content request which contains the content identifier and the UE's location information (e.g. the IP address) to the IPTV subsystem. 2) Th... |
d4763978937007086749bc87bda933cc | 182 019 | 7.3.1.2 Unicast streaming initiation - query approach | The following sequence depicts the procedure for unicast streaming delivery using the query approach. Figure 7.3.1.2.1: Unicast streaming initiation procedure - query approach 1) The UE initiates a content request to the IPTV subsystem. 2) The IPTV subsystem requests from the CDNCF the location of the optimal CCF for d... |
d4763978937007086749bc87bda933cc | 182 019 | 7.3.1.3 Restricted (forced-playout) policies | The procedure for forced playout policies (restricted trickplay) of a content item has the same procedures as depicted in clause 7.3.1.2 unicast streaming, with the following differences. ETSI ETSI TS 182 019 V3.1.2 (2011-09) 42 Step (5) The IPTV subsystem sends a content request to the CCF, and also indicates that the... |
d4763978937007086749bc87bda933cc | 182 019 | 7.4 Media control procedures | |
d4763978937007086749bc87bda933cc | 182 019 | 7.4.1 Unicast streaming delivery - trick play commands - proxy via CCF | This clause describes the procedures for delivering the content for the unicast streaming initiation described in clause 7.3.1.2, where Trick play commands are conveyed through the CCF. The following steps are depicted in figure 7.4.1.1. ETSI ETSI TS 182 019 V3.1.2 (2011-09) 43 Figure 7.4.1.1: Unicast streaming deliver... |
d4763978937007086749bc87bda933cc | 182 019 | 7.4.2 Unicast streaming delivery - trick play commands - direct to CDF | This clause describes the procedures for delivering the content as a result for unicast streaming Initiation described in clause 7.3.1.2 where Trick play commands are sent directly to the CDF. The following steps are depicted in figure 7.4.2.1. Figure 7.4.2.1: Unicast streaming delivery procedure with direct UE-CDF tri... |
d4763978937007086749bc87bda933cc | 182 019 | 7.5 Upload/upstream generic procedures | The CDN may be utilized for network content storage. After the UGC is uploaded to the CDN, the UGC owner may access and download the UGC from the CDN. Figure 7.5.1 provides an overview of the information flows for UGC based content delivery procedure. Figure 7.5.1: Content upload/upstream procedure 1) The sequence is t... |
d4763978937007086749bc87bda933cc | 182 019 | 7.6 Generic download procedures | This clause depicts the download procedures for either the IMS-based IPTV subsystem or NGN Integrated IPTV subsystem (see clauses 7.6.2 and 7.6.3). The interfaces associated with the CDN entities are universal to either IPTV subsystem. For information on the IPTV subsystems, refer to TS 182 027 [2] and TS 182 028 [3]. |
d4763978937007086749bc87bda933cc | 182 019 | 7.6.1 Unicast download/downstream common procedures | |
d4763978937007086749bc87bda933cc | 182 019 | 7.6.1.1 Unicast download delivery - redirect to CDF mode | The Redirect to CDF delivery mode procedure is shown in figure 7.6.1.1.1. Figure 7.6.1.1.1: Unicast download delivery procedure - redirect to CDF mode The Unicast download delivery procedure, in redirect to CDF mode, consists of the following steps: 1) The UE initiates delivery initiation request to the CDF. 2) The CDF... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.