hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.8.0 Concept of Downstream Profiles | DOCSIS 3.1 introduces the concept of downstream profiles for OFDM channels. A profile is a list of modulation orders that are defined for each of the subcarriers within an OFDM channel, as defined by the Downstream Profile Descriptor (DPD, see clause 6.4.42). The CMTS can define multiple profiles for use in an OFDM cha... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.8.1 CM and CMTS Profile Support | The latency incurred by the codeword builder of the MAC-PHY Convergence Layer (see ETSI TS 103 311-2 [12]) increases as the number of profiles supported by the CMTS increases on this channel, and as the OFDM channel bandwidth decreases. As such, the number of profiles supported by the CMTS can be defined according to t... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.8.2 Changes to the Profiles | Changes to operating conditions can occur due to changes in the PHY characteristics of the HFC network, CMs leaving or joining the network, or as a result of administrative controls, etc. The CMTS can react to these changes by changing the DS profiles. Clause 11.8 describes the process for the CMTS to change profile de... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.8.3 Service Flow to Profile Mapping | For a bonded downstream service flow, the CMTS can transmit the packets belonging to that service flow on more than one channel. For bonded downstream service flows, the CM performs the resequencing operations across the different channels and does not resequence over multiple profiles within the same OFDM channel. The... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.9 CM Downstream MER Reporting Protocol | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.9.0 Overview | DOCSIS 3.1 introduces the concept of multiple Modulation and Coding Schemes to the downstream OFDM channel PHY. The CMTS broadcasts the settings for each of the current downstream channel's profiles to all cable modems that are listening to the current downstream channel. Each CM uses this information to determine whic... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.9.1 Calculations | The following calculations determine value ranges and parameter sizes: • For 20 μs symbol time: 192 MHz OFDM block / 50 kHz subcarrier = 3 840 subcarriers • For 40 μs symbol time: 192 MHz OFDM Block / 25 kHz subcarrier = 7 680 subcarriers • log2(7 680) ~ 13 bits for a subcarrier ID (round up to 16 bits) Assuming a 192 ... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.9.2 Message Flow | Figure 7.20 depicts the downstream MER reporting process. At a (vendor-proprietary) time of its choosing, the CMTS individually polls each DOCSIS 3.1 CM for each OFDM channel's downstream spectrum MER characteristics. To do this, the CMTS issues an OFDM-Downstream-Spectrum-Request (ODS-REQ) message to the CM. The CM pr... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 8 Channel Bonding | 8.0 Overview Channel bonding refers to the scheduling of information in DOCSIS service flows over multiple channels concurrently. The bonded channels may be SC-QAM only, OFDM/OFDMA only or a mixture of SC-QAM and OFDM/OFDMA channels. In the downstream direction, the CMTS distributes individual packets over multiple cha... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 8.1 Upstream and Downstream Common Aspects | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 8.1.1 Service Flow Assignment | The CMTS shall assign Service Flows to either individual upstream or downstream channels, or to upstream or downstream bonding groups. This assignment can be dynamic in that, at any point in time, the CMTS can reassign a Service Flow to a different channel or bonding group following the guidelines in this clause. When ... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 8.1.2 CMTS Bonding and Topology Requirements | The CMTS shall permit Downstream Channels reaching the same CM-SG to be configured into separate MAC Domains. The CMTS shall permit Upstream Channels reaching the same CM-SG to be configured into separate MAC Domains. This permits an operator to segregate tiers of service (e.g. DSG CMs or business service CMs) to entir... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 8.2 Downstream Channel Bonding | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 8.2.1 Multiple Downstream Channel Overview | Prior to DOCSIS 3.0, downstream data service was provided to a Cable Modem on a single downstream channel. DOCSIS 3.0 expanded the downstream service offering by requiring DOCSIS 3.0 CMs to be capable of receiving multiple downstream channels simultaneously. DOCSIS 3.1 extends this further by requiring DOCSIS 3.1 CMs t... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 8.2.2 CMTS Downstream Bonding Operation | A Downstream Bonding Group is a set of Downstream Channels on which the CMTS distributes packets. Downstream Bonding Groups may either be statically configured or dynamically determined by the CMTS. The CMTS shall support the static configuration and modification of Downstream Bonding Groups. The CMTS MAY support the d... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 8.2.3 Sequenced Downstream Packets | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 8.2.3.0 General | When packets are transmitted with a Resequencing DSID, they are called "sequenced" downstream packets. A CMTS transmits sequenced downstream packets with a five-byte Downstream Service Extended Header (DS EHDR). Each DS EHDR of a sequenced downstream packet defines the following fields relevant to the resequencing oper... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 8.2.3.1 Downstream Sequencing | Once released from the CMTS, packets may experience varying delays before reaching the CM. This is particularly true in an M-CMTS system, where the packet traverses the CIN and EQAM. Packets are assumed to remain in order within a particular downstream channel, but packets on different channels may experience different... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 8.2.3.2 Skew Requirements | In downstream channel bonding, there are multiple physical paths between the CMTS and a given CM. These paths may have different delays. This delay variation results in "skew" across the CM's received channels. For purposes of this clause, each possible path from the CMTS bonding distribution point to the CM's RF input... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 8.2.3.3 Resequencing DSID Signalling | The Downstream Resequencing Encoding of a DSID Encoding (see clause C.1.5.4.3) defines the following attributes for a DSID: • Resequencing Enabled; • Downstream Resequencing Channel List; • DSID Resequencing Wait Time; • Resequencing Warning Threshold; • CM-STATUS holdoff timer for out-of-range events. ETSI ETSI TS 103... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 8.2.4 Cable Modem Physical Receive Channel Configuration | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 8.2.4.0 Cable Modem Receiver Capabilities | A Cable Modem reports its ability to receive multiple channels using the CM capabilities TLV (Type 5) subtypes 29, 49, 54, and 55. A DOCSIS 3.1 CM is capable of receiving channels anywhere on the RF spectrum it supports so the concept or a receive module is no longer required. The CMTS reads the DOCSIS 3.1 CM receive c... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 8.2.4.1 Receive Channels | The term "Receive Channel" refers to the component of a Cable Modem that receives a single SC-QAM Downstream Channel on a single centre frequency. A CM is considered to implement a fixed number of Receive Channels, each of which is identified within the CM by a Receive Channel Identifier. The CMTS assigns one or more o... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 8.2.4.2 Receive Modules | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 8.2.4.2.0 Receive Module Definition | The term "Receive Module" refers to a component in the DOCSIS 3.0 CM physical layer implementation shared by multiple SC-QAM Receive Channels. Examples of Receive Modules include analogue tuners, intermediate frequency down-converters, analogue-to-digital converters, digital sample buses, and digital signal processing ... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 8.2.4.2.1 Receive Module Interconnection | Some DOCSIS 3.0 CM architectures may support the concept of a programmable interconnection between a Receive Channel and a Receive Module. For example, a Receive Channel may be programmed to be connected to only one of several different A/D converters. Furthermore, a Receive Module itself (e.g. an A/D converter) may be... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 8.2.4.3 Receive Channel Profile | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 8.2.4.3.0 Receive Channel Profile Definition | A Receive Channel Profile is an encoding that represents the Receive Channels and Receive Modules (if any) of the CM. A CM registering on a DOCSIS 3.0 CMTS shall communicate to the CMTS one or more Receive Channel Profile (RCP) Encodings within its Registration Request, using the TLV structure as defined in clause C.1.... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 8.2.4.3.1 Standard Receive Channel Profiles | In order to avoid requiring CMTS software to support an increasing number of arbitrarily complex RCPs, DOCSIS defines the concept of a Standard RCPs. A Standard RCP represents a well-known virtual model of Receive Channels and Receive Modules that describes a useful minimum feature set for a class of multiple-channel D... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 8.2.4.4 RCP DOCSIS 3.0 Backwards Compatibility | The downstream spectrum lower band edge of the DOCSIS 3.1 CM [12] can be different than the DOCSIS 3.0 CM. The shift in downstream lower band edge affects the DOCSIS 3.1 CM registering with DOCSIS 3.0 CMTS. Hence, while registering with DOCSIS 3.0 CMTS, DOCSIS 3.1 CM shall send standard RCPs defined in Annex E, includi... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 8.2.4.5 Receive Channel Configuration | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 8.2.4.5.0 General Requirements | When registering a DOCSIS 3.0 CM, the CMTS shall select one of the RCPs in the Registration Request for configuring the CM. The CMTS returns, in a Registration Response to a CM, a "Receive Channel Configuration" (RCC) Encoding that contains TLVs to configure the Receive Channels and Receive Modules of the selected RCP.... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 8.2.4.5.1 Static Receive Module Assignments | The placement of Receive Modules in the downstream spectrum and the interconnection between Receive Channels and Receive Modules can require arbitrary complexity in the CMTS. To avoid this, the CMTS MAY support the static configuration of the parameters and interconnections of a Receive Module. CM-SP-OSSIv3.0-I22-14040... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 8.2.5 QoS for Downstream Channel Bonding | While the CMTS is required to maintain the DOCSIS Quality of Service for a Bonded Service Flow, the actual output data burst size for a Bonded Service Flow at the CMCI port may differ from the Maximum Traffic Burst QoS parameter for the flow. This is a result of CMTS packet distribution process, the CM resequencing ope... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 8.3 Upstream Channel Bonding | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 8.3.0 Relation to Multiple Transmit Channel Mode | An upstream bonding group consists of two or more upstream channels over which a service flow may be transmitted. A service flow may be assigned to a single upstream channel or an upstream bonding group. Multiple Transmit Channel Mode (MTC Mode) provides mechanisms and capabilities that enable Upstream Channel Bonding.... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 8.3.1 Granting Bandwidth | The CMTS scheduler allocates bandwidth on the individual channels based on the available bandwidth on all of the bonded upstream channels. Requests transmitted on any individual channel may be allocated bandwidth on any combination of upstream channels within the bonding group associated with the requesting service flo... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 8.3.2 Upstream Transmissions with Upstream Channel Bonding | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 8.3.2.0 General | For upstream channel bonding, the CM uses segmentation with Continuous Concatenation and Fragmentation (CCF) to fill the grants allocated to each service flow. The CM shall not combine different service flows within a segment. CCF uses a segment header to aid the CMTS in reconstructing the original data sent for each s... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 8.3.2.1 Segment Header ON Operation | Each service flow for Multiple Transmit Channel Mode operation is provisioned for either Segment Header ON operation or Segment Header OFF operation. With Segment Header On operation, the CM shall place the 8-byte segment header at the beginning of every segment for the service flow. For the first segment transmitted o... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 8.3.2.2 Segment Header OFF Operation | For service flows with Segment Header OFF, the CM shall not use the fragmentation portion of CCF. For service flows with Segment Header OFF, the CM shall not use the concatenation portion of CCF. Thus, all segments transmitted by the CM for these service flows shall contain only a single complete packet. If a segment i... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 8.3.3 Dynamic Range Window | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 8.3.3.0 Overview | The Dynamic Range Window defines a 12 dB range of Transmit Power Levels for the CM to use for each of the channels in its Transmit Channel Set. The DRW is controlled by the CMTS and communicated to the CM in the RNG- RSP or in the TCC encodings of the REG-RSP-MP or the DBC-REQ message. The top of the DRW is defined as ... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 8.3.3.1 Channels Added During Registration | The CMTS is required to send a value for the Dynamic Range Window in the Registration Response message if the CM is to be operating in Multiple Transmit Channel Mode. The CM shall use the Dynamic Range Window value sent in the Registration Response. When the CM receives the REG-RSP-MP it determines which upstream chann... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 8.3.3.2 Channels Added by a DBC-REQ | If a Dynamic Range Window value is provided in the DBC-REQ, the CM shall use that value. If no Dynamic Range Window value is provided in the DBC-REQ, the CM continues to use the value that it had been using. When the CM receives the DBC-REQ it determines which upstream channels it will be using based on the TCC encodin... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 8.3.3.3 Channels Deleted by a DBC-REQ | A DBC-REQ that deletes channels from the CM's Transmit Channel Set could result in an increase in Phi for the remaining channels. When sending a DBC-REQ to remove channels from the CM's TCS, the CMTS shall adjust the Dynamic Range Window and or any CM upstream transmit power levels so that there is no violation of the ... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 8.3.3.4 UCD Changes Burst Profiles Resulting in New Value for Phi | If the CM receives a new UCD with burst profile changes such that Phi for the channel is changed, the CM shall adjust its Reported Transmit Power (Pr) for the channel by an amount equal to the change in Phi such that Pload [12] is maintained. By definition, this adjustment in Pr will result in the CM maintaining the sa... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 8.4 Partial Service | Whenever one or more channels in the Transmit Channel Set (TCS) and/or the Receive Channel Set (RCS) are unusable, that CM is said to be operating in a "partial service" mode of operation in the upstream and/or downstream respectively. A channel is deemed to be unusable when the CM is unable to acquire one or more chan... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 9 Data Forwarding | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 9.1 General Forwarding Requirements | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 9.1.0 Overview | This clause defines the rules and requirements for CM and CMTS forwarding in the DOCSIS 3.0 Network. There are primarily 3 types of packets that a DOCSIS network is concerned with forwarding: broadcast (IPv4 packets destined for all hosts), multicast (IPv4 or IPv6 packets sent to a group of hosts) or unicast (IPv4 or I... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 9.1.1 CMTS Forwarding Rules | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 9.1.1.1 General CMTS Forwarding | Data forwarding through the CMTS shall be transparent bridging, network-layer forwarding (routing, IP switching), or a combination of the two. The CMTS shall provide IP (v4 and v6) connectivity between hosts attached to cable modems, and do so in a way that meets the expectations of Ethernet-attached customer equipment... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 9.1.1.2 DSID Labelling | In addition to its forwarding responsibilities, the CMTS labels packets it forwards to the CM with a DSID according to the following rules: • The CMTS SHOULD NOT label broadcast packets (addressed to a MAC destination of FF:FF:FF:FF:FF:FF) with a DSID. • The CMTS labels multicast packets according to the rules specifie... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 9.1.2 CM Address Acquisition, Filtering and Forwarding Rules | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 9.1.2.0 General CM Forwarding | The CM shall support forwarding of IP traffic (both IPv4 and IPv6). CMs and CMTSs operate as IP and LLC hosts as defined by [16] for communication over the cable network. The term "CPE MAC addresses" used in this clause includes MAC addresses of both connected CPE devices and eSAFEs. The term "CMCI port" describes phys... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 9.1.2.1 MAC Address Acquisition | The CM maintains a forwarding database (bridging table) including entries for the CM's own MAC address and CPE MAC addresses. The CM shall acquire CPE Ethernet MAC addresses, either from the provisioning process or from learning, until the CM acquires its maximum number of CPE MAC addresses (the lesser of the Max CPE f... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 9.1.2.2 CM Filtering Rules | The CM shall discard frames that are received with CRC or frame format errors. The CM shall discard packets based on the configurable filtering mechanisms defined in [9] and clause 7.5.1.2.2. Filtering downstream frames received on any of the downstream channels in the CM's Receive Channel Set conforms to the following... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 9.1.2.3 CM Forwarding Rules | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 9.1.2.3.0 General Behaviour | The CM shall not duplicate link-layer frames. |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 9.1.2.3.1 CM Pre-Operational Forwarding Behaviour | Prior to becoming operational as in figure 10.1, the CM operates per the following rules: • The CM shall forward to its IP stack all unicast frames that are received on the Primary Downstream Channel and addressed to the CM's MAC address. • The CM shall forward from its IP stack to the RF interface the multicast traffi... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 9.1.2.3.2 CM Operational Forwarding Behaviour | Once the CM is operational as in figure 10.1, CM forwarding in the upstream and downstream directions conforms to the following rules: • The CM MAY perform one or more frame/packet processing functions on frames received from the CPE port prior to classifying them to a Service Flow. Example frame/packet processing func... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 9.2 Multicast Forwarding | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 9.2.0 Multicast Forwarding Architecture | The Multicast DSID Forwarding (MDF) architecture and requirements as defined in DOCSIS 3.0 applies to DOCSIS 3.1 CMs and CMTSs as well. DOCSIS 3.1 provides support for wide band OFDM channels with each channel supporting multiple cable modem profiles. This requires additional rules for multicast forwarding as cable mod... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 9.2.1 Introduction Multicast Forwarding | Multicast can provide significant bandwidth savings in a network. Multicast is especially attractive in the cable network because of the broadcast nature of the cable downstream. In addition to providing end to end bandwidth savings, the cable RF network can be used effectively to distribute multicast streams to multip... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 9.2.2 Downstream Multicast Forwarding | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 9.2.2.0 Downstream Multicast Forwarding Requirements | This clause outlines the CMTS requirements when the Multicast DSID Forwarding is enabled on the CMTS. This clause also outlines the CM requirements when the CMTS sets the Multicast DSID Forwarding Capability of a CM to GMAC-Promiscuous(2). Annex G identifies exceptions or enhancements to the CM requirements described i... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 9.2.2.1 Examples of Downstream Multicast Forwarding using DSIDs | DOCSIS 3.0 introduced the capability of CMs to receive multiple Downstream Channels (DCs) and therefore to receive multicast session traffic distributed by a CMTS on a Downstream Bonding Group (DBG) of multiple channels. CMs incapable of receiving multiple Downstream Channels can receive multicast traffic on only a sin... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 9.2.2.2 Labelling Multicast Packets with DSIDs | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 9.2.2.2.0 General | The CMTS shall label all downstream multicast packets with a DSID. Packets with a known DSID are received by the CM and forwarded to the set of interfaces associated with the DSID. A routing CMTS shall label traffic for different "IP multicast SSM Channels" or "IP multicast ASM Groups" with different DSIDs, with the ex... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 9.2.2.2.1 Mixed CM Environment | DOCSIS 3.0 networks may contain a mix of DOCSIS 3.0 cable modems and Pre-3.0 DOCSIS cable modems. Pre-3.0 DOCSIS CMs do not support downstream channel bonding. However, the CMTS may need to transmit multicast packets to Multicast Clients behind the Pre-3.0 DOCSIS CMs. A CMTS shall replicate multicast traffic intended f... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 9.2.2.2.2 Pre-Registration DSID | The Pre-Registration DSID is the DSID for labelling multicast packets used by a CM prior to its completion of the registration process; these multicast packets used for DHCPv6, Neighbour Solicitation (DAD), and IPv6 Router Advertisements (RAs), are received only by a CM's IP stack. The CMTS shall label all link local m... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 9.2.2.2.3 Upstream Multicast Traffic from a Multicast Client | According to the requirements in clause 9.1.2.3, when a CM receives upstream multicast packets on its CMCI interface, it forwards packets on its RF Port, the CM IP stack and all of its CMCI ports, except the one from which it received the packets. Additionally, as specified in clause 9.1.2.2, when the CM receives DSID ... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 9.2.2.3 Communicating DSIDs and Group Forwarding Attributes to a CM | The CMTS is responsible for signalling to the CM a DSID that the multicast traffic is labelled with. The CMTS advertises the Pre-registration DSID value in the MDD message (clause 6.4.28.1.5). The CMTS also communicates DSID values to the CM during the registration process in a REG-RSP message and dynamically using the... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 9.2.2.4 DSID based Filtering and Forwarding by a Cable Modem | A CM shall not forward downstream multicast packets based on snooped IGMP v2/v3 messages. Since all multicast traffic that is meant to be forwarded by the CM is labelled with a DSID, the CM shall discard any multicast packets without a DSID label. The CM discards any packet with an unknown DSID. The CM performs filteri... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 9.2.2.5 Individually Directed Multicast | Individually directed multicast refers to the ability in the DOCSIS network to send a multicast packet on the downstream and ensure that it is forwarded by only one CM rather than the full set of CMs with Multicast Clients that have joined an IP Multicast Session. One potential usage scenario is for IGMPv2/MLDv1 Leave ... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 9.2.3 Downstream Multicast Traffic Encryption | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 9.2.3.1 Multicast Encryption Overview | When a CMTS encrypts downstream multicast traffic associated with an IP Multicast Session intended to be received and/or forwarded by a group of CMs, it does so with a Security Association (SA) previously signalled to those CMs. This type of Security Association ID (SAID) is defined as Per-Session SAID. A Security Asso... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 9.2.3.2 Dynamic Multicast Encryption | The message exchange between the CMTS and the CM for the signalling and initialization of multicast traffic encryption varies depending on the type of multicast session, the capabilities of the modem and the multicast forwarding mode selected by the CMTS. The signalling of Security Associations for encrypted dynamic mu... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 9.2.3.3 DSIDs and SAIDs | In general, the set of DSIDs and SAs known at a CM are considered to be independent. The CM is not expected to associate an SA with a DSID. Unless specified otherwise, the CMTS MAY transmit encrypted downstream multicast traffic intended for forwarding by a set of one or more CMs with any combination of an SA known by ... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 9.2.3.4 Pre-Registration Multicast Encryption | Before a CM registers, it receives layer 2 multicasts for DHCP /ARP for IPv4 or DHCPv6/Neighbour Discovery for IPv6. The CMTS labels multicast traffic intended for reception by CMs before registration with a Pre-Registration DSID advertised in the MAC Domain Descriptor (MDD) message. A CM that performs Early Authentica... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 9.2.4 Static Multicast Session Encodings | The cable operator can configure the cable modem to join IP multicast sessions during registration. Such multicast sessions are called Static Multicast Sessions. The cable operator configures such static multicast sessions using the CMTS Static Multicast Session Encodings (see clause C.1.1.27). The CMTS shall communica... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 9.2.5 IGMP and MLD Support | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 9.2.5.1 Motivation Behind Taking CM out of IGMP Control Plane | In DOCSIS 1.1 and 2.0, the cable modem is required to provide IGMP version 2 type snooping functionality in which the CM intercepts IGMP membership reports and establishes forwarding of multicast packets appropriately. Two modes, active and passive are defined. IGMP timers and requirements are specified in [13]. This m... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 9.2.5.2 IP Multicast Service Model Support | IGMP for IPv4 and MLD for IPv6 are the two IETF standards based protocols by which CPE devices signal membership for IP multicast Session. While originally intended to be used only by host-type CPEs, they can also be used by router-type CPE devices or CM co-located routers by using IGMP/MLD proxy-routing [i.34]. IGMP a... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 9.2.5.3 IGMP and MLD Membership Handling | Multicast Clients send triggered IGMP/MLD membership reports when they want to start or stop receiving an IP Multicast Session. When the CMTS processes these triggered membership reports, the CMTS sends DBC messages to control forwarding of multicast packets by a CM. When the CMTS receives a JoinMulticastSession messag... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 9.2.5.4 IGMPv2/MLDv1 Leave Processing | If there are multiple Multicast Clients on the same egress interface of the CM, periodic IGMPv2/MLDv1 membership reports are subject to suppression. Hence the CMTS needs to send an IGMPv2/MLDv1 group specific query as part of IGMPv2/MLDv1 leave processing ([i.23] and [39]) to determine if there are any remaining Multic... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 9.2.5.5 IGMP and MLD Version and Query Support | For each CM, the CMTS shall maintain a highest supported version of IGMP and MLD. The CMTS shall maintain the IGMP version as v3 for MDF-enabled CMs. The CMTS shall maintain the MLD version as v2 for MDF-enabled CMs. When the CMTS receives IGMP or MLD membership reports from a CM with a version higher than the maintain... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 9.2.5.6 Separation of Query Domains | In a mixed-mode cable environment where CMs in DOCSIS 3.0 mode co-exist with Pre-3.0 DOCSIS CMs, it is important to control which IGMP messages are being forwarded to the CPEs behind the CMs. It is necessary to prevent forwarding of IGMPv3 membership queries by DOCSIS 1.1/2.0 CMs. DOCSIS 1.1 /2.0 CMs are only capable o... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 9.2.6 Encrypted Multicast Downstream Forwarding Example | This example involves the forwarding of an encrypted multicast session to two multicast clients behind a CM. Refer to figure 9.5: 1) Multicast traffic labelled with DSID1 is not forwarded through the CM to any of the clients. 2) The Multicast Client 1 on Interface A sends out a "JoinMulticastSession" when it wants to j... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 9.2.7 IP Multicast Join Authorization | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 9.2.7.0 Overview | DOCSIS 3.0 introduces an IP Multicast Join Authorization feature that allows operators to control which IP multicast sessions may be joined by multicast clients reached through a CM. The set of IP multicast clients reached through a CM includes the CM IP host stack itself. This feature controls only the joining of down... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 9.2.7.1 Maximum Multicast Sessions | The IP Multicast Join Authorization feature permits an operator to configure the maximum number of multicast sessions joined by clients reached through a CM. Since the CMTS maintains a database of each client for each session on each cable modem, limiting the number of sessions for any one CM can prevent a denial of se... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 9.2.7.2 Session Rules | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 9.2.7.2.0 Concept of Session Rules | DOCSIS 3.0 introduced the concept of IP Multicast Join Authorization Session Rules, which are called simply "session rules" in this clause. A session rule applies to a range of IP multicast sessions, and identifies whether a multicast client reached through a CM is permitted or denied authorization to join a session wi... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 9.2.7.2.1 IP Multicast Profiles | At the CMTS, an operator configures a named "IP Multicast Profile" with a set of IP Multicast Join Authorization Session Rules. The IP Multicast Join Authorization Encoding in the CM configuration file in Annex C provides the name of one or more IP Multicast Profiles. The CMTS associates with the CM the union of all se... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 9.2.7.2.2 Static IP Multicast Join Authorization Rules | The IP Multicast Join Authorization Encoding also can contain explicit, static IP Multicast Join Authorization Rules. The CMTS associates with the CM all static session rules defined in the encoding. |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 9.2.7.3 CM Configuration File | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 9.2.7.3.0 Overview | An IP Multicast Join Authorization Encoding (see Annex C) in the CM configuration file and CM registration request determines the set of IP Multicast Join Authorization Session Rules associated with the CM. Because the IP Multicast Join Authorization encoding is a subtype of the TLV-43 DOCSIS Extension Information enco... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 9.2.7.3.1 IP Multicast Profile Name Subtype | A CMTS shall accept an IP Multicast Profile Name subtype in an IP Multicast Join Authorization Encoding as identifying a set of session rules configured at the CMTS to be associated with the CM. The CMTS shall accept at least 16 IP Multicast Profile Name encodings for a single CM. The total number of IP Multicast Profi... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.