hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
d889670bb13fe140b45857bdfc45bcfd | 101 618 | 4.2.2 Numbering area | Where numbering areas exist recognized by the user, location portability outside a specific numbering area may confuse the user, what to dial. If a user recognizes a specific part of a number, mostly called area code, to be specific for a certain area, he may be confused to have to dial a foreign area code to call a pe... |
d889670bb13fe140b45857bdfc45bcfd | 101 618 | 4.2.3 Charge area | For the definition of what a charge area is in this respect, see the paragraph definitions. Location portability within one charge area has no impact on the charging. There is no difference in the charging between calls to ported lines and calls to non-ported lines. When location portability leaves the charge area, the... |
d889670bb13fe140b45857bdfc45bcfd | 101 618 | 4.2.4 Anywhere | Location portability anywhere means, that no restriction applies. To get an overview of all technical and non-technical impacts on location portability without restrictions, this has to be examined issue by issue. The known issues to be examined are the exchange area, the numbering area and the charging area. One of th... |
d889670bb13fe140b45857bdfc45bcfd | 101 618 | 4.3 Problems and solutions when leaving certain areas | |
d889670bb13fe140b45857bdfc45bcfd | 101 618 | 4.3.1 Leaving exchange area | Portability leaving the serving area of a specific exchange is widely discussed under the issue of service provider portability. Service provider portability is mostly understood as network operator portability. This kind of portability is in a poorly technical description the portability between different exchanges of... |
d889670bb13fe140b45857bdfc45bcfd | 101 618 | 4.3.2 Leaving numbering area | Where location portability leaves certain numbering areas, the only technical impact is how many digits of the called party number have to be taken into account to address the call to a new destination. This is more an issue of establishing an appropriate numbering plan for ported numbers than an issue of a specific te... |
d889670bb13fe140b45857bdfc45bcfd | 101 618 | 4.3.3 Leaving charge area | This seems to be the most difficult to examine, and probably also to realize, issue on location portability. For the definition of a what a charge area is in this respect, see the paragraph definitions. Location portability, that leaves the charge area means, that the costs of phoning a ported line differs from phoning... |
d889670bb13fe140b45857bdfc45bcfd | 101 618 | 4.3.3.1 Charge difference | It would be the technical simplest solution, if nobody would take care of the charge difference and the differential costs of a call would be left to the network operator. This however is neither the most economical nor the most customer orientated solution. When a call to the ported number has a longer distance than b... |
d889670bb13fe140b45857bdfc45bcfd | 101 618 | 4.3.3.2 Informing the charged party | Most users want to know, what the tariff of a certain telephone call is. Except of service-numbers, the tariff depends on the geographic distance to the called party. In tables the user can find out the valid tariff for a certain area code. The area code is often the only information, the user has about the location of... |
d889670bb13fe140b45857bdfc45bcfd | 101 618 | 4.4 Service provider portability and location portability | While service provider portability is forced by the regulation in many countries, it is up to the service provider, to provide the service of location portability. Also it is up to the service provider in which domains he provides location portability, but in many countries it is regulated, where location portability i... |
d889670bb13fe140b45857bdfc45bcfd | 101 618 | 4.4.1 Congruent domains | When location portability domains and service provider portability domains are congruent (the same), there are no restrictions on porting the same number several times by either type of porting. Any location porting is possible, because all service providers of the specific service provider portability domain also prov... |
d889670bb13fe140b45857bdfc45bcfd | 101 618 | 4.4.2 Different domains | Addressing schemes or the serving areas of the exchanges in the networks of different network operators may differ. Therefore the location portability domains also may differ. This means, that after a location porting a service provider porting may not be possible, because the new service provider (so called recipient)... |
d889670bb13fe140b45857bdfc45bcfd | 101 618 | 5 Conclusions | Location portability can be examined in three areas, exchange area, numbering area and charge area. There are different implications for each area, but there is no link between the implications. If location portability is provided by leaving more than one of that areas, the implications apply just in sum. Portability l... |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 1 Scope | The present document is intended to provide an introduction to the Converged Cable Access Platform (CCAP) architecture. The CCAP architecture has been specified in an integrated and a modular implementation. The present document describes both the integrated and modular architectures and discusses the various specifica... |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 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... |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 2.1 Normative references | The following referenced documents are necessary for the application of the present document. Not applicable. |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 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 EN 302 878-3: "Access, Terminals, Transmission and Multiplexing (ATTM); Third Generation Transmission Systems for Interactive Cable Television Se... |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 3 Definitions and abbreviations | |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply: Access Shelf (AS): one of the two chassis that make up a Modular CCAP implementation. The Access Shelf is primarily responsible for MPEG processing and access functions (PHY, PON, etc.) normally associated with the CMTS and the Edge QA... |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply: AES Advanced Encryption Standard ANCP Access Node Control Protocol AS Access Shelf ASM Any-Source Multicast AWGN Additive White Gaussian Noise BGP Border Gateway Protocol CA Conditional Access CATV Cable Television CBR Constant Bit Rate CCAP C... |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 4 VOID | |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 5 CCAP Architecture Goals, Benefits and Overview | |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 5.1 Fundamental Goals of the CCAP | The Converged Cable Access Platform (CCAP) is intended to provide a new equipment architecture option for manufacturers to achieve the Edge QAM and CMTS densities that cable operators require in order to address the costs and environmental challenges resulting from the success of narrowcast services. The CCAP leverages... |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 5.2 CCAP Benefits | Whether implemented in an integrated chassis or in a modular manner, the CCAP provides the following operational benefits. |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 5.2.1 Service Multiplexing Flexibilities | The CCAP provides efficient implementation of Edge QAM (EQAM) blocks by implementing separate sets of QAM channels for narrowcast and broadcast applications. QAM channels for narrowcast services are individually implemented for each RF port, while QAM channels used for broadcast services are shared among all the RF por... |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 5.2.2 Bandwidth Capacity and Density Gains | The CCAP is designed to greatly increase the capacity of a single edge device, delivering all narrowcast and broadcast services via the downstream RF ports deployed (15-20 downstream ports on a small chassis; 40-60 on a larger chassis). The CCAP is expected to support multiple 10, 40, and/or 100 GigE interfaces with th... |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 5.2.3 High Reliability and Redundancy Capabilities | Given the scope of each RF port providing all services for a given service group, it is important that the operation be highly reliable. Therefore, a CCAP is expected to support redundancy for critical components; however, even in a non- redundant configuration, the CCAP should provide sufficient up time. This, coupled... |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 5.2.4 Configuration and Management Simplifications | The CCAP will allow configuration of both CMTS and EQAM functions from the same configuration interface. CCAP configuration will move away from SNMP-based configuration and focus instead on the processing of XML configuration files that hold the configuration details for all services on the CCAP. The CCAP utilizes a co... |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 5.2.5 Rack-Space and Power Reduction | One of the key benefits of the CCAP is to achieve significant environmental efficiencies. To that end, figures 5-1 and 5-2 demonstrate an example of the space and power savings achieved by deployment of the CCAP in a typical system. Figure 5-1 depicts a typical installation in a headend consisting of the various digita... |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 5.2.6 RF Combining Simplifications | Deployment of the CCAP simplifies the RF combiner network by providing all QAM channels for all digital services from a single RF port, only leaving certain legacy functions for RF combining. Rather than having to rewire the physical plant to make service group changes, the QAM content of a downstream RF port can be ch... |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 5.2.7 IP Router Integration | A CCAP system will support IP routing and forwarding, including IP multicast proxies and forwarding, and IP service proxies from a CMTS, a DPoE System, and the hub router and switches that currently provide IP multicast functionality for video broadcast and SDV. As modular implementations are permitted, this functional... |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 5.3 Supported Services in CCAP | This clause discusses the various services supported by the CCAP on an HFC system. Some of these services can also be supported by a CCAP for an EPON deployment. |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 5.3.1 Video EQAM Services | Video services supported by the CCAP include digital video services that are supported today by existing broadcast and narrowcast Edge QAMs (EQAMs). These services include digital video delivered as: 1) broadcast digital video; 2) switched digital video; and 3) video on demand. The CCAP is not intended to support modul... |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 5.3.1.1 Broadcast Digital Video | Broadcast digital video services refer to the programming delivered in a channel lineup to subscribers in common, as opposed to just a particular subscriber or to a particular node. Sometimes, broadcast video services are referred to as linear broadcast services because of the time-linear nature of the broadcast, where... |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 5.3.1.2 Switched Digital Video | Switched digital video (SDV) is classified as a narrowcast video service, as opposed to a broadcast service. Although the SDV content is delivered in common to multiple subscribers, the target subscribers are only those of a particular SDV service group that corresponds to the SDV QAM channels delivered to one or more ... |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 5.3.1.3 Video on Demand | A video on demand (VOD) service is defined as a video service delivered to a specific subscriber, generally in response to a real-time request for pre-packaged MPEG content. Thus, VOD is a narrowcast video service. VOD requires interaction between the subscriber STB and the program control system across a bi-directiona... |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 5.3.2 DOCSIS Services | Services enabled by the CCAP and other equipment supporting the interfaces specified in the various DOCSIS specifications include: • High-speed Internet (HSI) • IPCablecom voice over IP (VoIP) • Transparent LAN Service (TLS) over DOCSIS L2VPN • Next generation video services delivered via DOCSIS These services are disc... |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 5.3.2.1 High-Speed Internet | Interfaces for cable modems (CMs) and cable modem termination systems (CMTSs) have been defined in the DOCSIS specifications. Multiple generations of DOCSIS specifications exist in support of high-speed Internet services. The DOCSIS 1.0 specifications provide basic broadband Internet connectivity for one or more device... |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 5.3.2.2 IPCablecom VoIP | The VoIP service discussed in this clause refers to VoIP as provided by equipment supporting the interfaces specified in various IPCablecom specifications. In this context, IPCablecom VoIP provides a voice service that has voice quality, call features, and reliability that is expected from a primary line telephony serv... |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 5.3.2.3 Transparent LAN Service | The Transparent LAN Service (TLS) discussed in this clause refers to the functionality defined in the DOCSIS L2VPN specification [i.8]. TLS is also sometimes referred to as a "Metro Ethernet" or "Carrier Ethernet" service, such as that specified by the Metro Ethernet Forum (MEF). TLS allows businesses to extend their L... |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 5.3.2.4 Next Generation Video Services | The CCAP is expected to support the managed delivery of IP video for next generation video services. Managed IP video delivery has certain characteristics that can make the handling of that traffic by the CCAP less resource intensive. For example, the traffic flows have the following fundamental characteristics: • Larg... |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 5.3.3 DOCSIS Provisioning of EPON | The CCAP is expected to support EPON interfaces for high speed Internet. To facilitate the interoperability of EPON with the CCAP, the CCAP will support the entire DOCSIS Provisioning of EPON (DPoE) suite of specifications. The DPoE system includes DOCSIS Provisioning functions and IP routing (forwarding and service) f... |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 5.4 CCAP Architectures | |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 5.4.1 Integrated CCAP Architecture | Two reference architectures are provided in this clause: one showing the digital video delivery infrastructure, and the other showing the high-speed Internet infrastructure. The CCAP was designed to fully support both types of services simultaneously. A discussion of using the CCAP in an M-CMTS architecture is also dis... |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 5.4.1.1 CCAP MPEG Video Headend Reference Architecture | Cable headends acquire video from various sources to be provided to the subscriber via the access network. In figure 5-3, the dotted lines represent the video data while the remainder of the diagram represents control elements or flows within the MPEG video system. ETSI ETSI TR 101 546 V1.1.1 (2011-10) 20 Figure 5-3: C... |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 5.4.1.2 CCAP Data Reference Architecture | The CCAP performs all DOCSIS functions in the way that a traditional CMTS platform does. In addition, PON can be deployed on the CCAP to manage commercial HSI traffic. The following diagram, figure 5-4, illustrates how HSI streams flow through the CCAP and the network to DOCSIS and PON devices and back. Figure 5-4: CCA... |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 5.4.1.3 Modular Headend Architecture Functionality | To assist with the transition from traditional EQAM and CMTS devices to the converged implementation of the CCAP, a CCAP can also function as a universal edge QAM. This allows the CCAP to conform to the architecture defined in [i.40], allowing existing CMTS infrastructure to be leveraged while transitioning in CCAP dev... |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 5.4.2 Modular CCAP Architecture | This clause presents two architectural views of the Modular CCAP (M-CCAP). The first is a functional architecture that describes the physical separation of the M-CCAP components and the responsibilities of each. The second presents an architectural view of the M-CCAP in the headend, showing the flow of data and video, ... |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 5.4.2.1 Modular CCAP Functional Architecture | An M-CCAP is the result of the decomposition of an Integrated CCAP (I-CCAP), whereby packet processing is segregated logically and physically from the real-time critical, access-specific processing. The M-CCAP is implemented as two separate "shelves": • A Packet Shelf • An Access Shelf The Packet Shelf is responsible f... |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 5.4.2.2 Packet Shelf Functionality | The Packet Shelf has common functions that are self-contained without regard to the type of Access Shelf connected to it. These common functions include, but are not limited to: • Terminate the DOCSIS OSSI • Provide an SNMP manager for querying the Packet Shelf and any subtended Access Shelves • Provide a configuration... |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 5.4.2.3 Access Shelf Functionality | Since each Access Shelf type is access-specific, there is very little that is common across Access Shelves. Access Shelves can be access-technology-specific, only supporting one access medium such as HFC; or they can be hybrid, supporting more than a single access method, such as HFC and EPON. The following is a list o... |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 5.4.2.4 Modular CCAP Data/Video Architecture | The flow of data traffic and video traffic in the M-CCAP is very similar to the flow for the I-CCAP, the difference being the physical separation of the Packet Shelf and its subtended Access Shelves. Multicast and unicast streams enter the Packet Shelf via an NSI interface using the same protocols as are used in the in... |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 5.4.2.5 Downstream-Only Access Shelf | The AS can also be configured as a downstream-only edge QAM, in the architecture defined in [i.40]. This approach will be essential during the transition from current CMTS/EQAM deployments to the deployment of the CCAP. |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 6 Summary of DOCSIS Specifications and Applicability | |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 6.1 DOCSIS 3.0 Specifications | The following clauses describe which DOCSIS 3.0 specifications are required for the CCAP, and the extent to which they apply. |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 6.1.1 MAC and Upper Layer Protocols Interface Specification v3.0 | The MAC and Upper Layer Protocols specification [i.9] defines the MAC layer protocols of DOCSIS 3.0 as well as the requirements for upper layer protocols (e.g. IP, DHCP, etc.). The CCAP is required to meet all CMTS requirements specified therein. |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 6.1.2 Physical Layer Specification v3.0 | The Physical Layer specification [i.11] defines the upstream physical layer requirements for hybrid fibre-coax systems that the CCAP needs to support. The CCAP is required to meet all of the requirements specified therein. In addition, the CCAP is also designed to be compatible with the European market. For a European ... |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 6.1.3 DOCSIS Security Specification v3.0 | The Security Services specification [i.29] defines security services for DOCSIS communications, providing the operator with the ability to secure the provisioning process of cable modems (CM) and protect cable modem users by encrypting traffic flows between the CM and the cable modem termination system; in this case, t... |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 6.2 CCAP Specifications | |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 6.2.1 CCAP Operations Support System Interface | The CCAP OSSI [i.32] specification defines new configuration interfaces based on a standardized, converged object model, supporting both EQAM and CMTS functions. This specification introduces and standardizes YANG-based configuration and NETCONF as a protocol to support the configuration and management of the CCAP. Thi... |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 6.2.1.1 SNMP Requirements and Reporting Requirements | The SNMP requirements of the CCAP are based upon the requirements specified in OSSI3.0 [i.10], but the CCAP does not implement all SNMP requirements specified therein. The CCAP is required to support SNMP v1 and v2, as well as at least 10 SNMP community strings with controlled access via access lists. The CCAP primaril... |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 6.2.1.2 CCAP Object Model | The [i.32] specification implements object models for configuration, fault management, and performance management. These object models build upon models established in [i.10]. The specification supports the use of YANG, allowing access to these object models via NETCONF [i.31]. The CCAP implements a configuration objec... |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 6.2.2 Packet Shelf to Access Shelf Interface Specification | A Modular CCAP (M-CCAP) supports the decomposition of an Integrated CCAP (I-CCAP), whereby packet processing is segregated logically and physically from the real-time critical, access-specific processing. The intention of this functional segregation is to independently leverage advances in routing and access technologi... |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 6.3 Modular Headend Architecture Specifications | |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 6.3.1 Edge Resource Management Interface Specification | The Edge Resource Management Interface [i.5] specification defines interfaces that are used by EQAMs, ERMs, and M-CMTS Cores. While the CCAP does not require that all of [i.5] be supported, because the CCAP will interface with ERMs to dynamically control video and possibly DOCSIS QAMs, the following interfaces specifie... |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 6.3.2 DOCSIS Timing Interface Specification | The DOCSIS Timing Interface [i.3] specification defines the timing interfaces required for the DOCSIS M-CMTS architecture. While the CCAP needs to support stratum 3 clock accuracies, it is not required to implement the timing interface as specified in the [i.3] specification, although [i.3] is an acceptable implementat... |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 6.3.3 Video Stream Interface Specification | The Video Stream Interface [i.4] specification defines the data plane requirements for receiving, processing, and transmitting MPEG transport streams in EQAMs. The CCAP implements all requirements in the [i.4] specification, with the following exceptions: • Clause 9 - Encryption and Encryption Interface: The CCAP may b... |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 6.4 Downstream RF Interface Specification | The Downstream RF Interface specification [i.1] defines the downstream radio frequency interface for EQAMs and CMTS; as such, the requirements specified in [i.1] are required for the CCAP. While all DRFI [i.1] requirements need to be met by the CCAP, the CCAP does diverge from DRFI [i.1] in the following areas: • Frequ... |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 6.5 DOCSIS Set-Top Gateway Specification | The DOCSIS Set-Top Gateway specification [i.2] defines an interface and associated protocol that introduces additional requirements on a DOCSIS CMTS and DOCSIS CMs to support the configuration and transport of a class of service known as "Out-Of-Band (OOB) messaging" between a set-top controller (or application servers... |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 6.6 Business Services over DOCSIS Specifications | |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 6.6.1 Layer 2 VPN Specification | The Layer 2 VPN specification [i.8] describes requirements for both CMTSs and CMs in order to implement a DOCSIS Layer-2 Virtual Private Network. The L2VPN feature allows cable operators to offer a Layer 2 Transparent LAN Service (TLS) to commercial enterprises. The CCAP is required to meet all CMTS L2VPN requirements ... |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 6.6.2 TDM Emulation Interface Specification | The TEI [i.30] specification defines a method for cable operators to deliver T1, E1 and NxDS0 emulation services that meet or exceed the quality requirement of applications that use such services. Implementation of TDM emulation is preferred for the CCAP, but no [i.30] specification requirements are mandatory. |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 6.7 DOCSIS Provisioning of EPON Specifications | A CCAP supporting EPON applications will be expected to implement the entire suite of DPoE specifications defined in the following clauses. |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 6.7.1 DOCSIS Provisioning of EPON Architecture Specification | The [i.33] specification describes the architecture required for DPoE Networks. |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 6.7.2 DOCSIS Provisioning of EPON MEF Specification | The [i.34] specification describes the provisioning and operations required to support Metro Ethernet Forum (MEF) Ethernet Services in DPoE Networks, which use EPON as defined in 802.3ah [i.46] and 802.3av [i.48]. 6.7.3 DOCSIS Provisioning of EPON MAC and Upper Layer Protocols Specification The [i.35] specification def... |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 6.7.6 DOCSIS Provisioning of EPON Physical Layer Specification | The [i.38] specification identifies requirements for the EPON PHY for the adaptation or additions to DOCSIS specifications that are required to support DOCSIS Provisioning of EPON. |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 6.7.7 DOCSIS Provisioning of EPON Security Specification | The [i.39] specification identifies recommendations for the adaptation or additions to DOCSIS specifications that are required to support DOCSIS Provisioning of EPON (DPoE). |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 6.8 Summary of DOCSIS Specification Applicability | Table 6-1 summarizes the level of adherence the CCAP is required to have to DOCSIS specifications. Table 6-1: DOCSIS Specification Adherence Specification Device MULPI PHY SEC CCAP OSSI PASI ERMI DTI VSI DRFI DSG L2VPN TEI DPoE I-CCAP M M M M NA P O P M M M O M* M-CCAP PS M NA P M M P O NA NA M M NA NA M-CCAP AS M M P ... |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 7 CCAP Features and Capabilities | |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 7.1 Service Multiplexing Capabilities | |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 7.1.1 CCAP Service Groups | For the purposes of the CCAP, a service group is defined as a set of channels in a given service delivered via some number of fibre nodes to the corresponding subscribers of that service, provided by one or more CCAP ports. One of the concepts tied in with service groups is the reachability of certain signals from the ... |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 7.1.1.1 Broadcast Service Groups | A broadcast service group consists of linear digital broadcast video channels corresponding to an advertising zone or a channel lineup with local or regional PEG channels. A broadcast service group typically spans more than one port on a DLC, possibly spans all ports on a DLC, and may even cross multiple DLCs. ETSI ETS... |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 7.1.1.2 Switched Digital Video Narrowcast Service Groups | An SDV service group consists of a number of downstream QAM carriers that are configured for video services for switched digital video applications. The SDV service group is a configured element of the CCAP and may span more than one RF port on a DLC. |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 7.1.1.3 VOD Narrowcast Service Groups | A VOD service group consists of a number of downstream QAM carriers that are configured for video services for video on demand. A VOD service group may be configured to be smaller than a DOCSIS service group, due to frequency re-use configurations and the number of QAMs needed for a specific serving area. The VOD servi... |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 7.1.1.4 DOCSIS Narrowcast Service Groups | A DOCSIS downstream service group today is typically configured to be comprised of one to four optical nodes, depending on node size, service penetration, and data traffic load. There is some expectation (not necessarily a rule) that a DOCSIS service group would correspond to one port on a DLC. |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 7.2 Optional Content Protection | The CCAP provides an option to accept incoming transport streams that have had network encryption applied to keep them protected as they traverse the network of the cable operator, remove that network encryption, and then, based on the encryption mode specified for the content, apply the appropriate conditional access ... |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 7.2.1 Network Decryption | The optional CCAP Decryptor component works in association with one external ECM decoder (ECMD) to remove the encryption layer used to secure the content distribution within the operator inner network. The control words and copy control information are retrieved from the incoming ECM to allow decrypting the associated ... |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 7.2.2 Access Encryption | The CCAP Scrambler is a simple scrambling engine; the conditional access intelligence resides in the ECM Generator (ECMG). The CCAP Scrambler is under the control of one or more external ECMGs and applies the encryption layer required to secure the content distribution to the subscriber CPE devices, based on the ECMG-p... |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 7.3 QAM Replication | In order to simplify integration of the CCAP into existing systems, the CCAP is expected to implement a QAM replication feature. The purpose of this feature is to allow an operator to create logical service groups on a decoupled, service-by-service basis. This will provide the ability to replicate narrowcast video (SDV... |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 7.4 Spectrum Surveillance | Due to the nature of the CCAP system and its targeted services, the CCAP is placed at a critical location within the cable operator's network. As the primary bridge between the back-office network and the HFC plant, the CCAP is responsible for transmitting and receiving all of the signals on the HFC plant for MPEG-TS S... |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 7.5 CCAP Configuration Management | The CCAP combines the functionality of an Edge QAM with a CMTS into a single platform designed to reduce operational costs and provide network flexibility. In order to provide operators the simplest path to deployment of CCAP with existing OSS systems, the goal for configuration and management of the CCAP is to treat t... |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 7.5.1 YANG Data Modelling Language and XML Background | The configuration of a CCAP chassis can be accomplished using a variety of methods such as via a command-line interface, through file-based processing, or methods such as NETCONF or Web services. Underlying these configuration methods is a common configuration object model which defines the parameters that are to be co... |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 7.5.2 Configuration Object Model | A CCAP Configuration Object Model has been developed in UML to define the elements (objects) and their parameters (attributes) that will need to be represented in the YANG configuration data model and eventually, the configuration XML schema. The object model also defines the associations between objects. One example o... |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 7.5.3 Configuration Data Model | The CCAP YANG configuration data model is created from a direct translation of the CCAP configuration UML object model into a set of YANG modules. The YANG data model is constructed in a tree format using modules and sub- modules. The CCAP YANG modules can be used by a YANG translation tool to generate the XML schema u... |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 7.5.4 CCAP Configuration File Processing | The CCAP is configured via the execution of an XML configuration file that is transferred to the file system on the I-CCAP (or on the Packet Shelf in the M-CCAP). The CCAP parses the entire XML configuration file and processes the configuration objects represented in the file as a sequence of individual element operati... |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 7.5.5 CCAP NETCONF-Based Configuration | The CCAP may also be configured via NETCONF as specified in [i.43]. The CCAP uses standard NETCONF edit- config commands to execute XML-based configuration parameters. The XML configuration data can contain explicit "merge", "replace", or "delete" operation values at various nodes within the configuration tree provided... |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 7.6 PON Configuration: DOCSIS Provisioning of EPON | Cable operators have recognized the value of including alternative access technologies into their network topology. This has included exploration and deployment of various wireless and passive optical solutions. The common characteristic for all of these alternative access technologies is that they have uncommon OSS mo... |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 7.6.1 The DOCSIS and DPoE Networks | The following diagram summarizes the primary systems and elements involved in a typical HFC-based DOCSIS network. For brevity, only a sample of the back-office systems used to provision, manage, authorize, and control the network are included. Figure 7-3: DOCSIS 3.0 HFC Network Using CCAP The DPoE specifications define... |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 7.6.2 DPoE Provisioning and Management | Interfaces and systems for managing DPoE devices may be provided through a DOCSIS Emulation module either running on the CCAP itself or running on an external server. Requirements for these interfaces are specified by the [i.37] specification to provide Provisioning and Management support for the network. As shown in f... |
96e320caefa6811bdaf7c3bb12b492f9 | 101 546 | 7.6.3 Provisioning and Management of OLT Devices | As CCAP is providing the functionality of the DPoE System, the OLT and associated PON interfaces are managed in a similar fashion to DOCSIS RF interfaces. Logical DOCSIS constructs, such as MAC domains, are implemented on top of the physical EPON interfaces. Relevant CMTS MIBs and DOCSIS CLI operations are mapped to th... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.