hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
dde9e2552d661348f67d747426d8c5c3 | 183 002 | 7.4 Specific procedures for V5 interfaces | V5 support is out of scope of an RGW, but may be an optional interface at an AGW. |
dde9e2552d661348f67d747426d8c5c3 | 183 002 | 7.4.1 General | Support of V5 interfaces (V5.1, V5.2) requires (see note) the use of a backhaul mechanism in conjunction with H.248. In particular H.248 shall be used for handling the adaptation of the 64-kbit/s bearer channels to RTP media streams, for applying tones and announcements, and for inband DTMF digit collection. NOTE: It i... |
dde9e2552d661348f67d747426d8c5c3 | 183 002 | 7.4.2 V5 signalling | An AGW shall support a signalling gateway according RFC 3807 [53] as a backhaul mechanism for transporting LAPV5 information to the MGC. |
dde9e2552d661348f67d747426d8c5c3 | 183 002 | 7.4.3 Handling of p- and f-type frames | Handling of p- and f-type frames is according clauses 7.3.2.2 and 7.3.2.3. 8 MG and MGC management and call-independent procedures Generic TISPAN Call-independent procedures are defined in a separate document (TR 183 025 [i.1]), which is an overall description for all ETSI defined H.248 profile specifications, i.e. TR ... |
dde9e2552d661348f67d747426d8c5c3 | 183 002 | 8.1 Overload control | MG overload control procedures are supported using the Overload Control package (ITU-T Recommendation H.248.11 [19]). In the case of MGC overload there are two mechanisms, the "notification behaviour" and "adaptive rate based" that are available to the MGC in order to regulate the traffic presented to it. ETSI ETSI TS ... |
dde9e2552d661348f67d747426d8c5c3 | 183 002 | 8.1.1 Notification Behaviour | MGC will give preference to emergency calls and priority lines. Priority lines do not need any special H.248 handling since the MGC has the information and can use regular call setup procedures for those subscribers. Detection of emergency calls requires special handling whilst minimizing the MGC load. The special hand... |
dde9e2552d661348f67d747426d8c5c3 | 183 002 | 8.1.2 Adaptive Rate Based | The adaptive rate based mechanism is defined in ES 283 039-4 [57] and allows the MGC to offset the load onto the AGWs during periods of MGC load. This is achieved using the "etsi_nr" package that enables the MGC to specify the "off-hook" rate that it can handle. When the MGC is no longer in overload, then the "Off-Hook... |
dde9e2552d661348f67d747426d8c5c3 | 183 002 | 8.2 IP QoS control and monitoring | The Quality of Service (QoS) of network connections can be monitored using the quality alert event of the network package. It is up to the MGC to set the threshold value that will trigger the notification of this event. The threshold value is expressed as a percentage of measured quality loss. The Media GateWay (MGW) d... |
dde9e2552d661348f67d747426d8c5c3 | 183 002 | 8.3 Testing of analog and digital lines | It shall be possible to trigger "metallic" line testing on physical terminations via the MG OAM interface. This profile does not support H.248-controlled line tests (e.g. line tests defined in ITU-T Recommendation H.248.17 [49]). A service change procedure shall be initiated by the MG, when a termination is placed in t... |
dde9e2552d661348f67d747426d8c5c3 | 183 002 | 8.4 Real-Time Statistics Reporting | |
dde9e2552d661348f67d747426d8c5c3 | 183 002 | 8.4.1 Overview of conditional reporting | Normally a MGC obtains bearer related statistics through periodic auditing of the H.248 statistic descriptor or at the time of deletion of a stream or subtraction of a termination. However, in both cases, there is a time delay from when a reporting condition occurs on a MG (e.g. a statistic threshold being passed) and ... |
dde9e2552d661348f67d747426d8c5c3 | 183 002 | 8.4.2 Basic conditional reporting | Basic conditional reporting uses the protocol elements of the Statistic Conditional Reporting package version 1. This allows the definition of many, but limited reporting conditions. |
dde9e2552d661348f67d747426d8c5c3 | 183 002 | 8.4.3 Extended conditional reporting | Extended conditional reporting uses the protocol elements of the Statistic Conditional Reporting package version 2. This package allows in addition • to control whether a timestamp is reported with the detection of the (conditional reporting) events; and • extends the reporting conditions with value-based metric condit... |
dde9e2552d661348f67d747426d8c5c3 | 183 002 | 8.5.1 Usage metering | Usage metering is supported by the statistics defined in the Network (nt), RTP (rtp) and RTP Application Data (rtpad) packages. Such statistics are notified to MGC when a termination is subtracted from a context (e.g. at the end of a session) or due to conditional reporting (see clause 8.4). They provide information ab... |
dde9e2552d661348f67d747426d8c5c3 | 183 002 | 8.5.1.1 Traffic Volume related Statistics | Figure 5 provides an overview of different traffic volume related statistics. Traffic volume related statistics are only accessible by the nt and rtp packages in profile versions 1 and 2. Profile version 3 provides additional metrics. Application Level Framing Protocol RTP, UDPTL, … L3: IP L2 L4: UDP, TCP, … L1 e.g. au... |
dde9e2552d661348f67d747426d8c5c3 | 183 002 | 8.5.1.1.1 RTP Case (general) | Ephemeral terminations in this profile using RTP as application level framing protocol. Traffic volume based statistics may be accessed via the rtp package: • packet granularity: RTP packets sent and/or received; NOTE: Packet level statistics could already provide useful volume measurements in case of RTP packets with ... |
dde9e2552d661348f67d747426d8c5c3 | 183 002 | 8.5.1.1.2 RTP Case: application data | The RTP Application Data package provides support for explicit octet count statistics concerning media traffic, i.e. the RTP payload based traffic volume. |
dde9e2552d661348f67d747426d8c5c3 | 183 002 | 8.5.1.1.3 IP Case: network layer data | The IP layer octets count statistics package provides traffic volume statistics on IP layer for IP version 4 or 6. The H.248 ipocs package (see indication in figure 3) is not supported by this profile and previous versions. ETSI ETSI TS 183 002 V3.3.1 (2009-08) 86 |
dde9e2552d661348f67d747426d8c5c3 | 183 002 | 8.5.2 Statistics for reported metering pulses at analog lines | There is a PSTN supplementary service ("Advice of Charge" (AOC)) for reporting metering pulses towards PSTN terminals from network side. The PSTN AOC service is only applicable for H.248 analog line (ALN) terminations and provided by the amet package. The MG records reported metering pulses by: 1) a cumulative statisti... |
a816caab598d1d98df7e0e65e42626c6 | 182 032 | 1 Scope | The present document specifies the architecture and functions of a CDN Interconnection system, implementing the requirements defined in TS 102 990 [1]. |
a816caab598d1d98df7e0e65e42626c6 | 182 032 | 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... |
a816caab598d1d98df7e0e65e42626c6 | 182 032 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. [1] ETSI TS 102 990: "Media Content Distribution (MCD); CDN Interconnection, use cases and requirements". |
a816caab598d1d98df7e0e65e42626c6 | 182 032 | 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 TR 102 688-9: "Media Content Distribution (MCD); MCD framework; Part 9: Content Delivery Infrastructures (CDI)". [i.2] IETF RFC 6707: "Content Di... |
a816caab598d1d98df7e0e65e42626c6 | 182 032 | 3 Definitions and abbreviations | |
a816caab598d1d98df7e0e65e42626c6 | 182 032 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: NOTE: Some of the following definitions are from TS 182 019 [i.6] and TR 102 688-9 [i.1]. CDN Interconnection: interconnection between two CDNs, enabling the controlled distribution of content between those CDNs content delivery: act o... |
a816caab598d1d98df7e0e65e42626c6 | 182 032 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: AAC Advanced Audio Coding ALF Asset Location Function AMT Automatic Multicast Tunnelling AS Autonomous System ATIS Alliance for Telecommunications Industry Solutions BGP Border Gateway Protocol CCF Cluster Controller Function CDF Content Deliv... |
a816caab598d1d98df7e0e65e42626c6 | 182 032 | 4 High-level overview | |
a816caab598d1d98df7e0e65e42626c6 | 182 032 | 4.1 CDN interconnection services and capabilities | CDNs are in general autonomous networks offering different services to their users. A CDN's primary function is to optimize content distribution and delivery. In addition to this primary function many CDNs chose to implement various other capabilities like content manipulation, digital rights management (DRM), intellig... |
a816caab598d1d98df7e0e65e42626c6 | 182 032 | 4.2 CDN interconnection capabilities | Table 4.2.1 provides a table of all the capabilities available for CDN interconnection, grouped into the basic and extended capability set. It also mentions whether those capabilities are mandatory or optional. Table 4.2.1: Capability Overview Table Basic capability set Extended capability set Description Interconnecti... |
a816caab598d1d98df7e0e65e42626c6 | 182 032 | 4.3 CDN-I basic capability set | Every CDN that wants to take part in CDN interconnection shall have a basic set of interconnection related capabilities. These capabilities give the CDN the ability to properly respond to requests coming from other CDNs. The capabilities included in the basic service set are listed in figure 4.3.1. ETSI ETSI TS 182 032... |
a816caab598d1d98df7e0e65e42626c6 | 182 032 | 4.4 CDN-I extended capability set | Whereas the basic capability set is sufficient for basic CDN interconnection many CDNs have additional capabilities that may not be available in all CDNs participating in the CDN federation. The presence of optional capabilities in the CDN federation requires those CDNs that wish to make use of those capabilities to ha... |
a816caab598d1d98df7e0e65e42626c6 | 182 032 | 4.5 Compliance | A CDN interconnection solution is compliant to the present document if the following points are fulfilled: • All mandatory services and features are implemented as specified in the present document. • If an optional service or feature is implemented, then it is implemented as specified in the present document. • If an ... |
a816caab598d1d98df7e0e65e42626c6 | 182 032 | 5 Overview of functional entities | |
a816caab598d1d98df7e0e65e42626c6 | 182 032 | 5.1 Functional architecture for CDN interconnection services | The overall functional architecture for CDN interconnection service is shown in figure 5.1.1. The functional architecture is based on a multi-layer architecture that enable separate functionalities used for interconnection of CDNs that may involve up to 3 different level of functionalities and related reference points ... |
a816caab598d1d98df7e0e65e42626c6 | 182 032 | 5.2 Functional entities | The Content Delivery Network contains one or more Distribution of Content Function (DCF) that can be grouped geographically or administratively in clusters and contains several delivery nodes (that distribute content to other CDN or to end user) hidden to other CDN. CDN shall contain one or more Request and Content Fun... |
a816caab598d1d98df7e0e65e42626c6 | 182 032 | 5.2.1 CDN Interconnection Control Function (ICF) | A CDN Interconnection Control Function (ICF) shall manage, create, terminate and exchange CDN networks properties, status report required for CDN interconnection between two or more CDNs (CDN peers). An ICF contains following functionalities: • Footprint Exchange - enable CDNs exchange footprint information. • Capabili... |
a816caab598d1d98df7e0e65e42626c6 | 182 032 | 5.2.2 Request and Content Control Function (RCF) | The Request and Content Control Function (RCF) is responsible for content control and request routing as well as exchanging metadata related to content control. The RCF contains following functionalities: • Metadata exchange function - Metadata are sent from upstream CDN to downstream CDN. Downstream CDN can then make ... |
a816caab598d1d98df7e0e65e42626c6 | 182 032 | 5.2.3 Distribution of Content Function (DCF) | Distribution of Content Function (DCF) is responsible for distribution of content between CDNs in form of files, streams, metadata. The DCF contains following functionalities: • Transfer of file-based content. • Publication and streaming of stream-based content. • Content metadata distribution (if metadata distributed ... |
a816caab598d1d98df7e0e65e42626c6 | 182 032 | 5.3 Reference points | |
a816caab598d1d98df7e0e65e42626c6 | 182 032 | 5.3.1 ICF - ICF (CDN-Ic) | This reference point is between two ICFs and it is used for controlling interconnection peer and transferred over this point information related to CDN capabilities and status, including footprint exchange, capability exchange, interconnection status reporting and network usage/performance logging. ETSI ETSI TS 182 032... |
a816caab598d1d98df7e0e65e42626c6 | 182 032 | 5.3.2 RCF - RCF (CDN-Ir) | This reference point is between two CCFs and it is used for requesting content and to transfer content related information, including content metadata exchange, content requests and content status reporting. |
a816caab598d1d98df7e0e65e42626c6 | 182 032 | 5.3.3 DCF - DCF (CDN-Id) | This reference point is between two DCFs. Content files, content streams and content related data (if distributed as part of content) are transferred over this point. |
a816caab598d1d98df7e0e65e42626c6 | 182 032 | 6 Procedures | This clause specifies CDN-I procedures. Clause 6.1 specifies the 3 main phases of interconnection. The following clauses describe specific procedures related to different capabilities that were agreed during the interconnection phase. |
a816caab598d1d98df7e0e65e42626c6 | 182 032 | 6.1 CDN interconnection phases | The basic process of CDN interconnection may consist of three basic phases: • Interconnection establishment, during which the CDNs negotiate the interconnection. • Interconnection phase, during which the CDNs are fully interconnected and able to share their resources. • Interconnection release, during which the interco... |
a816caab598d1d98df7e0e65e42626c6 | 182 032 | 6.1.1 Interconnection establishment | The interconnection establishment is a procedure in which an uCDN and a dCDN begin with no relationship between each other and proceed by exchanging all the information needed to verify each other's identity and thus establish a secure communication channel between each other. This communication is between the ICFs of ... |
a816caab598d1d98df7e0e65e42626c6 | 182 032 | 6.1.2 Interconnection phase | The second phase is simply called interconnection phase. In interconnection phase shall be both CDNs already fully interconnected and through their interconnection interfaces ICFs and RCFs. Interconnection interfaces are fully useable by both CDNs and agreed capabilities accessible over CDN interconnection. ETSI ETSI T... |
a816caab598d1d98df7e0e65e42626c6 | 182 032 | 6.1.3 Interconnection release | The interconnection release is a phase that begins when an uCDN or a dCDN decides to release a CDN peering relationship with each other (for a specific ICF-ICF relation, and associated RCF-RCF relations). This means that the procedure has two variants, depending on whether it was initiated by the uCDN or the dCDN. In b... |
a816caab598d1d98df7e0e65e42626c6 | 182 032 | 6.2 Content distribution | |
a816caab598d1d98df7e0e65e42626c6 | 182 032 | 6.2.1 General | This clause provides procedures for content distribution: • Content distribution control, the initiation of content exchange. • Content exchange, the actually transfer or streaming of content between the interconnecting CDNs. |
a816caab598d1d98df7e0e65e42626c6 | 182 032 | 6.2.2 Content distribution control | |
a816caab598d1d98df7e0e65e42626c6 | 182 032 | 6.2.2.1 General | This clause provides procedures for content distribution control: • Content distribution. • Content deletion. |
a816caab598d1d98df7e0e65e42626c6 | 182 032 | 6.2.2.2 Upstream-initiated content distribution | Figure 6.2.2.2.1 shows the procedure for upstream-initiated content distribution from the uCDN to the dCDN. The two CDNs should be interconnected. NOTE 1: Upstream-initiated content distribution is typically used for the prepositioning of files or streams. Figure 6.2.2.2.1: Upstream-initiated content distribution The p... |
a816caab598d1d98df7e0e65e42626c6 | 182 032 | 6.2.2.3 Downstream-initiated content distribution | Figure 6.2.2.3.1 shows the procedure for downstream-initiated content distribution from the uCDN to the dCDN. The procedure is used when the dCDN needs to know from where to retrieve an identified content item from the uCDN. NOTE 1: Downstream-initiated content distribution is typically used for cases where the distrib... |
a816caab598d1d98df7e0e65e42626c6 | 182 032 | 6.2.2.4 Upstream-initiated content deletion | Figure 6.2.2.4.1 shows the procedure for upstream-initiated content deletion in the dCDN. NOTE 1: Upstream-initiated content deletion is typically performed at the request of a Content Provider to make sure that content is no longer available after a point in time. 2. dDCF uRCF dRCF uDCF 1. Trigger 6. Content Exchange,... |
a816caab598d1d98df7e0e65e42626c6 | 182 032 | 6.2.2.5 Downstream notification of content deletion | Figure 6.2.2.5.1 shows the procedure for downstream notification of content deletion. Figure 6.2.2.5.1: Downstream notification of content deletion The procedure has the following steps: 1) The dRCF is triggered to send a notification of content deletion. The dRCF may be triggered when all instances of a particular con... |
a816caab598d1d98df7e0e65e42626c6 | 182 032 | 6.2.3 Content exchange | |
a816caab598d1d98df7e0e65e42626c6 | 182 032 | 6.2.3.1 General | This clause provides procedures for content exchange. The following types of content may be exchanged: • Files. • Streams. • Segmented content. |
a816caab598d1d98df7e0e65e42626c6 | 182 032 | 6.2.3.2 File transfer | Figure 6.2.3.2.1 shows the content-exchange procedure for file transfer. Figure 6.2.3.2.1: File transfer The procedure has the following steps: 1) The dDCF is triggered retrieve a file. The trigger includes information that enables the dDCF to identify and locate a selected uDCF. 2) The dDCF sends a retrieval request t... |
a816caab598d1d98df7e0e65e42626c6 | 182 032 | 6.2.3.3 Stream set-up | Figure 6.2.3.3.1 shows the content-exchange procedure for stream set-up. 3. 2. dDCF uRCF dRCF uDCF 1. Trigger ETSI ETSI TS 182 032 V1.1.1 (2013-04) 23 Figure 6.2.3.3.1: Stream set-up The procedure has the following steps: 1) The dDCF is triggered to set up a stream. The trigger includes information that enables the dDC... |
a816caab598d1d98df7e0e65e42626c6 | 182 032 | 6.2.3.4 Stream release | Figure 6.2.3.4.1 shows the content-exchange procedure for stream release. Figure 6.2.3.4.1: Stream release The procedure has the following steps: 1) The dDCF is triggered to release a stream. 2) The dDCF sends a request to the uDCF to release the stream. 3) The uRCF stops sending the stream to the dDCF. 4) The uRCF con... |
a816caab598d1d98df7e0e65e42626c6 | 182 032 | 6.2.3.5 Segmented content | Segmented content is content composed of multiple files, or content composed of multiple streams, or content composed of one or more files and one or more streams. The composition of segmented content is described in an associated manifest file (MF). NOTE 1: The term "manifest file" has several synonyms, depending on t... |
a816caab598d1d98df7e0e65e42626c6 | 182 032 | 6.3 Request routing | |
a816caab598d1d98df7e0e65e42626c6 | 182 032 | 6.3.1 General | This clause provides procedures for request routing between two interconnected CDNs. |
a816caab598d1d98df7e0e65e42626c6 | 182 032 | 6.3.2 Single-delivery request routing | Figure 6.3.2.1 shows the procedure for request routing for a single content-item delivery. Figure 6.3.2.1: Single-delivery request routing The procedure has the following steps: 1) The uRCF is triggered to initiate request routing, e.g. by an incoming content delivery request from a User Equipment (UE). 2) The uRCF sen... |
a816caab598d1d98df7e0e65e42626c6 | 182 032 | 6.3.3 Multiple-delivery request routing | Figure 6.3.3.1 shows the procedure for request routing for multiple content items simultaneously. This procedure increases efficiency when there is a high intensity of request routing between the uCDN and dCDN. A specific case is segmented content, where the uCDN wants to fill-in a manifest file (MF) for directing indi... |
a816caab598d1d98df7e0e65e42626c6 | 182 032 | 6.4 Reporting | |
a816caab598d1d98df7e0e65e42626c6 | 182 032 | 6.4.1 General | The reporting between CDNs is realized by two different procedures. The differences between them are explained below: • Upstream-initiated reporting is used by the upstream CDN to retrieve any information from the downstream CDN. This information may include up-to date delivery statistics and status , comprehensive his... |
a816caab598d1d98df7e0e65e42626c6 | 182 032 | 6.4.2 Upstream-initiated reporting | The main role of the upstream-initiated reporting procedure is to make it possible for the uCDN to get access to the content-related information gathered by the dCDN while delivering the content to clients. This procedure shall be initiated by the uRCF to inform the dRCF about the fact that the uRCF requests specific i... |
a816caab598d1d98df7e0e65e42626c6 | 182 032 | 6.4.3 Downstream-initiated reporting | The role of the downstream-initiated reporting procedure is to inform the uCDN about a content-related event that happened within the dCDN. This procedure is visualized in figure 6.4.3.1. Figure 6.4.3.1: Downstream-initiated reporting procedure The procedure consists of following steps: 1) The dRCF sends a report messa... |
a816caab598d1d98df7e0e65e42626c6 | 182 032 | 6.5 Interconnection Control Function Procedures | |
a816caab598d1d98df7e0e65e42626c6 | 182 032 | 6.5.1 General | These procedures allow to inform the uCDN about changes of specified capabilities/footprint/status of a dCDN. The information contained in these updates shall match the data models defined in clause 7. Examples of specific messages can be found in annex B. 1. Report request uRCF dRCF 2. Report response 3. Report ack uR... |
a816caab598d1d98df7e0e65e42626c6 | 182 032 | 6.5.2 Capabilities exchange | The capability exchange is a procedure whose main goal is to inform the uCDN about the capabilities of a dCDN. The capability list is a data structure describing the list of capabilities (or features, services and their parameters) that the dCDN is willing to provide to uCDN. The capability exchange procedure is primar... |
a816caab598d1d98df7e0e65e42626c6 | 182 032 | 6.5.3 Footprint exchange | The footprint exchange is a procedure whose main goal is to inform the uCDN about the footprint of a dCDN. The footprint is a data structure containing a list of network segments for which the dCDN can deliver content items for the uCDN. There are multiple methods that can be used to describe a network segment. The mos... |
a816caab598d1d98df7e0e65e42626c6 | 182 032 | 6.5.4 Services status exchange | The status exchange is a procedure whose main goal is to inform the uCDN about the status of a dCDN. This procedure is specific in the fact that it can be triggered not only in reaction to a change of status in the dCDN but is also used as a keep alive mechanism. This means that even when the dCDN's status did not chan... |
a816caab598d1d98df7e0e65e42626c6 | 182 032 | 6.6 DRM Procedures | |
a816caab598d1d98df7e0e65e42626c6 | 182 032 | 6.6.1 General | These procedures are used when the CDN interconnection is involved in the DRM for content delivery. |
a816caab598d1d98df7e0e65e42626c6 | 182 032 | 6.6.2 Flagging CDN content for DRM | An uCDN can flag to a dCDN that DRM procedures should be applied for a specific content item. This is flagged during content distribution. In case of upstream-initiated content distribution, step 3 of clause 6.2.2.2 includes that DRM flag. In case of downstream-initiated content distribution, step 4 of clause 6.2.2.3 i... |
a816caab598d1d98df7e0e65e42626c6 | 182 032 | 6.6.3 Key exchange for DRM | These procedures are relevant if the dCDN would need to encrypt a content item for delivery to a specific UE. Different encryption for different UE provides an additional layer of protection against signal theft. The content item could be stored in plain format. There exist also DRM systems that enable the content to b... |
a816caab598d1d98df7e0e65e42626c6 | 182 032 | 6.6.3.1 uCDN-initiated key exchange for DRM | Figure 6.6.3.1.1 shows the procedure for uCDN-initiated key exchange for DRM. It may be combined with the single- delivery request-routing procedure of clause 6.3.2. ETSI ETSI TS 182 032 V1.1.1 (2013-04) 31 Figure 6.6.3.1.1: uCDN-initiated key exchange for DRM The procedure has the following steps: 1) The uRCF is trigg... |
a816caab598d1d98df7e0e65e42626c6 | 182 032 | 6.6.3.2 dCDN-initiated key exchange for DRM | Figure 6.6.3.2.1 shows the procedure for dCDN-initiated key exchange for DRM. If the content distribution to the dCDN has not yet taken place, then this procedure may be combined with the procedure for downstream-initiated content distribution in clause 6.2.2.3. Figure 6.6.3.2.1: dCDN-initiated key exchange for DRM 2. ... |
a816caab598d1d98df7e0e65e42626c6 | 182 032 | 7 Data models | There are two categories of data models. 1) CDN related data models This category of data represents the information about a specific CDN network from the interconnection perspective. - CDN information contains basic data that is relevant to specific CDN. - CDN footprint defines a single footprint segment that is relat... |
a816caab598d1d98df7e0e65e42626c6 | 182 032 | 8 Security | This clause specifies all the security aspects used for CDN interconnection. Their main purpose is to make it provide a complete tool-set that can be used to make CDN interconnection into a secure environment while maintaining scalability and flexibility. Scalability is guaranteed by adhering to the architectural princ... |
a816caab598d1d98df7e0e65e42626c6 | 182 032 | 8.1 Security feature interoperability | Because all of the security features in CDN-I environments are optional it is important to define the means of interoperability between CDNs with different CDN-I security feature sets. This kind of interoperability is achieved by the means of capabilities, see clause 6.5.2. This means that every security feature is rep... |
a816caab598d1d98df7e0e65e42626c6 | 182 032 | 8.2 CDN interconnection service protection | The security of communication between CDN-I entities, as specified in clause 6, is achieved by using the SSL/TLS protocol to encrypt and authenticate all communication channels. In most scenarios this consists of using the HTTPS protocol instead of plain HTTP for CDN-I procedure messages. In some cases it may also mean... |
a816caab598d1d98df7e0e65e42626c6 | 182 032 | 8.2.1 Secure CDN-I connection establishment | The establishment of a secure CDN-I connection should begin by trying to connect to the Interconnection Control Interface of a peer CDN via the HTTPS protocol, using procedures described in clause 6.1.1. If the connection can be established and the certificates are valid and considered trustworthy, then the connection ... |
a816caab598d1d98df7e0e65e42626c6 | 182 032 | 8.3 CDN interconnection content and metadata authenticity | The authenticity of content and its metadata shall be achieved by protecting integrity by means of the security certificates. Content and or its metadata can be signed with a private key belonging to the content provider. The certificate and checksum generated for authenticity, generated with the use of the content pro... |
a816caab598d1d98df7e0e65e42626c6 | 182 032 | 8.4 Security policy definition by content provider | It shall be possible for the content provider to define rules related to the security requirements of the content they want to provide. These rules should be indicated within the metadata file accompanying the content. The content provider should guarantee the authenticity and integrity of this metadata file by signing... |
1648b3e8e46828428b32588407b8d464 | 183 025 | 1 Scope | The purpose of the present document is to define guidelines with regard to the interaction of non-call related H.248 procedures and generic network management use cases and vice versa. More specifically, the interaction between the following is considered: • Control procedures at the H.248 interface. These are the proc... |
1648b3e8e46828428b32588407b8d464 | 183 025 | 1.1 Applicability | The present document is applicable to any network element that exhibits a H.248 interface and a management interface (e.g. SNMP). The intent of the present document is to provide guidelines so as to facilitate a consistent set of behaviour for non-call related procedures in the related H.248 profile specifications. Due... |
1648b3e8e46828428b32588407b8d464 | 183 025 | 1.2 Relation to H.248 Standards | The present document is considered to be complementary to H.248 standards where there are discrepancies between the present document and the correspondent ITU-T Recommendation H.248-series Recommendations, the procedures of these ITU-T Recommendations (in particular ITU-T Recommendation H.248.1 [i.5] and its annex F on... |
1648b3e8e46828428b32588407b8d464 | 183 025 | 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... |
1648b3e8e46828428b32588407b8d464 | 183 025 | 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. Not applicable. |
1648b3e8e46828428b32588407b8d464 | 183 025 | 2.2 Informative references | The following referenced documents are not essential to the use of the ETSI deliverable 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 ES 283 002 (V1.1.1): "Telecommunications an... |
1648b3e8e46828428b32588407b8d464 | 183 025 | 3 Definitions and abbreviations | |
1648b3e8e46828428b32588407b8d464 | 183 025 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: control association: The H.248 Control Association is defined in clause F.2/H.248.1 version 3 [i.5]. primary Media Gateway: No explicit definition in H.248. NOTE: The primary MG is rather implicitly defined. See mainly ITU-T Recommenda... |
1648b3e8e46828428b32588407b8d464 | 183 025 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: AGW Access GateWay DSP Digital Signal Processor FE Functional Entity IP Internet Protocol IS In Service MG Media Gateway MGC Media Gateway Controller NGN Next-Generation Network OOS Out-of-Service PE Physical Entity RTP Real-time Transport Pro... |
1648b3e8e46828428b32588407b8d464 | 183 025 | 4 Reference Architecture | Figure 1 illustrates the reference architecture assumed in the present document. MGC MG Management System H.248.1 Protocol Procedures Management Commands Management Commands Figure 1: Reference architecture The present document discusses the message primitives that may be passed over the Management Command interface an... |
1648b3e8e46828428b32588407b8d464 | 183 025 | 5 H.248 Concepts And Logical Entities | |
1648b3e8e46828428b32588407b8d464 | 183 025 | 5.1 H.248 Entities | H.248 commands and procedures are acting on H.248 logical entities. These are the different types: • Context - this is the entity that associates terminations together in a call or session. See also clause 6.1 of [i.5]. • NULL Context - this is a special Context which contains all Physical Terminations that are not ass... |
1648b3e8e46828428b32588407b8d464 | 183 025 | 5.2 H.248 Non-Call Related Commands | The H.248.1 commands relevant to the present document are: • AuditValue - this command enables a MGC to request the supported packages and current state of properties, events, signals and statistics of terminations. For further details, see also clause 7.2.5 of [i.5]. • AuditCapability - this command enables a MGC to r... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.