hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 9.2.7.3.2 Static IP Multicast Session Rule Subtype | A CMTS MAY accept Static IP Multicast Session Rule subtypes in an IP Multicast Join Authorization Encoding as defining session rules associated with the CM. If a CMTS does not accept Static IP Multicast Session Rule subtypes, the CMTS shall silently ignore the encoding. If supported, the CMTS shall support at least 16 ... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 9.2.7.4 Matching Session Rules | The CMTS shall associate with a CM all session rules in the IP Multicast Profile Name encodings referenced in the CM's registration request. In addition, if the CMTS accepts Static IP Multicast Join Authorization Session Rule subtypes, the CMTS shall also associate with the CM the static session rules signalled in the ... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 9.2.7.5 IP Multicast Profile Changes | A CMTS shall support changes to the set of session rules associated with an IP Multicast Profile while a CM remains registered that references that IP Multicast Profile Name. A CMTS shall apply an updated IP Multicast Profile to subsequent join requests from clients reached through a CM that references the profile. For... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10 Cable Modem - CMTS Interaction | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.1 CMTS Initialization | The mechanism utilized for CMTS initialization is described in [10]. The CMTS meets the following criteria for system interoperability. • The CMTS shall be able to reboot and operate in a stand-alone mode using configuration data retained in non- volatile storage. • If valid parameters are not available from non-volati... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.2 Cable Modem Initialization and Reinitialization | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.2.0 Initialization Overview | A cable modem shall initialize or reinitialize as shown in figure 10.1. This figure shows the overall flow between the stages of initialization in a CM. The more detailed finite state machine representations of the individual stages (including error paths) are shown in the subsequent figures. Timeout values are defined... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.2.1 Scan for Downstream Channel | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.2.1.0 Overall Process | Figure 10.2: Scan for Downstream Channel On initial power-on the CM shall set its CM initialization reason to POWER_ON. On initialization or a "Reinitialize MAC" operation, the cable modem shall acquire a Primary-Capable downstream channel. The CM shall have non- volatile storage in which the last operational parameter... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.2.1.1 Gather Downstream Channel Parameters from PLC | Figure 10.3: Gather Downstream Channel Parameters from PLC ETSI ETSI TS 103 311-3 V1.1.1 (2017-02) 327 The CM will read the Timestamp Message Block of the PLC for a DOCSIS timestamp. If the DOCSIS timestamp is found, the CM will then read the Message Channel Message Block of multiple PLC frames for a valid OCD message ... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.2.1.2 Remove All Frequencies Covered by this Channel from the PLC List | There is one PLC per OFDM channel and the 6 MHz encompassed spectrum containing the PLC at its centre can be located on any one MHz boundary. However, the edges and exclusion bands of the OFDM channels are not known in advance and can be placed anywhere with a 25 kHz resolution. In order to scan for a PLC, the CM start... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.2.2 Continue Downstream Scanning | When the CM determines that the current candidate primary channel is unsuitable, the CM shall resume scanning downstream spectrum for a suitable candidate downstream channel. The CM SHOULD continue to scan the previously unscanned spectrum. |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.2.3 Service Group Discovery and Initial Ranging | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.2.3.0 Overall Process | The CMTS needs to determine the service group of a DOCSIS 3.0 or later CM for channel bonding and load balancing purposes. As described in figure 10.4, the CM shall attempt to determine its MAC Domain Downstream Service Group ID (MD-DS-SG-ID) if an MDD is present on the downstream. During initialization DOCSIS 3.1 CM l... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.2.3.1 Read MAC Domain Descriptor (MDD) | A CMTS periodically transmits a MAC Domain Descriptor (MDD) MAC management message on all DOCSIS 3.0 or later Downstream Channels of a MAC Domain. On non-Primary-Capable Channels, the CMTS transmits a MDD message that contains at least the MDD Header with the Downstream Channel ID on which the MDD is sent. On Primary-C... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.2.3.2 Determination of MD-DS-SG | Figure 10.6: Determine MD-DS-SG The CM shall attempt to determine its MD-DS-SG according to figure 10.6. This process is described as follows: NOTE: The CM keeps track of the "list of currently visible DCIDs" by accumulating a list of all DCID values within the MAC Domain of the primary Downstream Channel that it encou... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.2.3.3 Determination of MD-US-SG | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.2.3.3.0 Overall Process | Clauses 10.2.3.3.1 through 10.2.3.3.3 explain the steps that a CM shall perform in order to resolve MD-US-SG resolution. ETSI ETSI TS 103 311-3 V1.1.1 (2017-02) 334 Figure 10.7: Determine MD-US-SG The CM shall store the UCID and the transmit power level of all the US channels in its latest operational Transmit Channel ... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.2.3.3.1 Ranging Holdoff | Figure 10.8: Ranging Holdoff The CM shall check for ranging holdoff direction per figure 10.8 prior to sending an initial ranging request message when it performs initial maintenance for any of the following reasons: • Power on initialization. • Reinitialize MAC event, except when triggered by a DCC-REQ with an initial... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.2.3.3.2 Bonded Initial Ranging | If the upstream channel is an SC-QAM channel then the CM proceeds to follow figure 10.10 for bonded initial ranging on an SC-QAM channel. If the upstream channel is an OFDMA upstream channel, the CM starts timer T2 and waits for an OFDMA initial ranging opportunity. If the T2 timer expires then Bonded Initial Ranging h... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.2.3.3.3 Continue US Ambiguity Initial Ranging | Figure 10.11: Continue US Ambiguity Initial Ranging T3 timeout Adjust Power No End RNG-RSP RNG-REQ Yes US Channel Adjustment TLVs Present in RNG-RSP? Use new Upstream Channel ID , Ranging SID , Initialization Technique and wait for ranging opportunity US Ambiguity Range Done No Retune to previous US frequency Exceeded ... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.2.3.4 Ranging and Automatic Adjustments | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.2.3.4.0 Message Sequence and State Machine | The CM performs the ranging and adjustment process defined by the message sequence charts and the finite state machine in this clause. The CMTS performs the ranging and adjustment process defined by the message sequence charts and the finite state machine in this clause. NOTE: MAPs are transmitted as described in claus... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.2.3.4.1 Adjust Transmit Parameters | Upon receipt of a RNG-RSP message, the CM shall reduce or increase the power by the specified amount in RNG-RSP messages. Adjustment of local parameters (e.g. transmit power) in a CM as a result of the non-receipt of a RNG-RSP is considered to be implementation-dependent with the following restrictions (refer to clause... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.2.3.5 CMTS Determination of Cable Modem Service Group and Initial Ranging | The CMTS shall attempt to determine the CM-SG of a CM according to figure 10.15. After determining the service group of a CM, the CMTS shall perform Initial Ranging according to figure 10.16. ETSI ETSI TS 103 311-3 V1.1.1 (2017-02) 345 NOTE: The poll list is a list of CMs that are currently performing unicast initial r... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.2.4 Authentication | Once a CM has completed ranging, if Early Authentication and Encryption (EAE) is enabled in the MDD the CM will initiate EAE before continuing with the initialization process. EAE helps prevent unauthorized CMs from accessing IP provisioning servers and provides confidentiality/privacy for IP provisioning messages betw... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.2.5 Establish IP Connectivity | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.2.5.0 Modes for Establishing IP Connectivity | The CM performs IP provisioning in one of four modes: IPv4 Only, IPv6 Only, Alternate Provisioning Mode (APM), and Dual-stack Provisioning Mode (DPM). The CM determines the IP provisioning mode via the CmMdCfg management object defined in [10], CM Provisioning Objects section, Object Model diagram. If the management ob... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.2.5.1 Establish IPv4 Network Connectivity | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.2.5.1.0 Message Flow | This clause describes how the CM is provisioned with an IPv4 address and associated parameters. The requirements in this clause apply to CMs using IPv4 provisioning. A CM uses IPv4 provisioning when the MDD indicates IPv4 Only provisioning or DPM, or when the MDD indicates APM and IPv6 provisioning fails, or when a CM ... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.2.5.1.1 DHCPv4 Fields Used by the CM | The following fields shall be present in the DHCPDISCOVER and DHCPREQUEST messages from the CM: • The hardware type (htype) shall be set to 1. • The hardware length (hlen) shall be set to 6. • The client hardware address (chaddr) shall be set to the 48 bit MAC address associated with the RF interface of the CM. • The c... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.2.5.1.2 Use of T1 and T2 Timers | 10.2.5.1.2.0 Overview The CM shall initiate the lease renewal process when timer DHCP-T1 expires. The CM shall initiate the lease rebinding process when timer DHCP-T2 expires. Timers DHCP-T1 and DHCP-T2 are called T1 and T2, respectively, in the DHCP specifications. If the DHCP server sends a value for DHCP-T1 to the C... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.2.5.1.3 CMTS Requirements | In order to assist the DHCP server in differentiating between a DHCPDISCOVER sent from a CM and a DHCPDISCOVER sent from a CPE: • The CMTS DHCPv4 relay agent shall support the DHCP Relay Agent Information Option (RAIO) [40]. Specifically, the CMTS DHCPv4 relay agent shall add an RAIO to the DHCPDISCOVER message before ... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.2.5.2 Establish IPv6 Network Connectivity | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.2.5.2.0 Message Flow | This clause describes how the CM is provisioned with an IPv6 address and associated configuration parameters. The requirements in this clause apply only to CMs instructed to use IPv6 provisioning. A CM uses IPv6 provisioning when the MDD indicates IPv6 Only provisioning, DPM, APM, or supports IP Provisioning Mode Overr... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.2.5.2.1 Obtain Link-Local Address | The CM shall construct a link-local address for its management interface according to the procedure in [51]. The CM shall use the EUI-64 (64-bit Extended Unique Identifier) as a link-local address for its management interface as described in [44]. The CM management interface shall join the all-nodes multicast address a... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.2.5.2.2 Obtain Default Routers | The CM shall perform router discovery as specified in [50]. The CM identifies neighbouring routers and default routers from the received RAs. If the CM does not receive a properly formatted response to the Router Solicitation message within the retransmission requirements defined in [50], the CM shall proceed as if IPv... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.2.5.2.3 Obtain IPv6 Management Address and Other Configuration Parameters | A CM shall examine the contents of RAs that it receives. The CM obeys the following rules: • If the M bit in the RA is set to 1, the CM shall use DHCPv6 to obtain its management address and other configuration information (and ignore the O bit); • If there are no prefix information options in the RA, the CM shall not p... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.2.5.2.4 IP Provisioning Mode Override | 10.2.5.2.4.0 Override Requirements This clause describes optional IP Provisioning Mode Override capabilities. The IpProvMode and associated attributes are described in more detail in [10] CM Provisioning Objects section. The IpProvMode attribute describes the IP provisioning mode in which the CM will operate, regardles... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.2.5.2.5 Use of T1 and T2 Timers | 10.2.5.2.5.0 Overview The CM shall initiate the lease renewal process when timer DHCP-T1 expires. The CM shall initiate the lease rebinding process when timer T2 expires. Timers DHCP-T1 and DHCP-T2 are called T1 and T2, respectively, in the DHCP specifications. If the DHCP server sends a value for DHCP-T1 to the CM in ... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.2.5.2.6 CMTS Requirements | The CMTS DHCPv6 relay agent shall send the following DHCPv6 options to the DHCPv6 server, in any Relay- Forward messages used to forward messages from the CM to the northbound router for a bridging CMTS and to the DHCPv6 server for a routing CMTS: • Interface-ID option [42]; • CMTS Capabilities option, containing the v... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.2.5.2.7 Prefix Stability at the CMTS | Many customers are interested in maintaining a stable IPv6 prefix to minimize renumbering in their LAN. This functionality is desired regardless of topology changes such as node splits or load-balancing events in the operators' network. When a node split or load-balancing event occurs, subscriber CM and CPE devices cou... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.2.5.3 Alternate Provisioning Mode (APM) Operation | When provisioning in Alternate Provisioning Mode, the CM tries to provision using IPv6 first. If IPv6 provisioning is unsuccessful, either because IPv6 Address acquisition or the TFTP configuration file download fails, the CM abandons IPv6 provisioning and attempts provisioning using IPv4. Figure 10.20 shows the proces... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.2.5.4 Dual-stack Provisioning Mode (DPM) | In Dual-stack Provisioning Mode (DPM), the CM attempts to acquire both IPv6 and IPv4 addresses and parameters through DHCPv6 and DHCPv4 almost simultaneously. For the acquisition of time-of-day and the download of a configuration file the CM prioritizes the use of the IPv6 address over the IPv4 address. If the CM canno... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.2.5.5 Establish Time of Day | The CM acquires time of day for the purpose of timestamping warning and error logs and messages, and may also acquire it for the correct operation of some eSAFE devices. The CM acquisition of time is not required for successful CM provisioning. The CM shall attempt to obtain the current date and time by using the Time ... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.2.5.6 Transfer Operational Parameters | After the CM has attempted to obtain the time of day, the CM shall download a configuration file using Trivial File Transfer Protocol (TFTP) [31], as shown in figure 10.22. When using DHCPv4, if there are one or more addresses in the DHCPv4 TFTP Servers option in the DHCPACK, the CM shall utilize the addresses listed i... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.2.5.7 Configuration File Processing | After downloading the configuration file and prior to completing IP Provisioning, the CM performs several processing steps with the configuration file. If a modem downloads a configuration file containing an Upstream Channel ID Configuration Setting (see Annex C) different from what the modem is currently using, the mo... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.2.5.8 Post-registration Failures to Renew IP Addresses | If the CM is configured to provision in IPv4 Only or IPv6 Only mode, and it fails to renew its IP address it shall reinitialize the MAC as defined in clause 10.2. If a CM is configured to use APM and the CM fails to renew its IP address, the CM shall note the event in the Local Event Log. Failure to renew the IP addres... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.2.6 Registration with the CMTS | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.2.6.1 Cable Modem Requirements | Once the CM establishes IP Connectivity, and unless directed to a different Primary Downstream Channel via the configuration file (see clauses C.1.1 and C.1.1.22), the CM shall register with the CMTS per figure 10.26 through figure 10.32. In this clause, the term Registration Request refers to the REG-REQ-MP MAC Manage... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.2.6.2 CMTS Requirements | In this clause, the term Registration Request refers to either the REG-REQ MAC Management Message or the REG- REQ-MP MAC Management Message. The term Registration Response refers to either the REG-RSP MAC Management Message or the REG-RSP-MP MAC Management Message. If the CM sent a REG-REQ message, the CMTS responds wi... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.2.6.3 CMTS Requirements for Pre-DOCSIS 3.0 CMs | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.2.6.3.0 Registration Process | The DOCSIS 2.0 CM with IPv6 support is required to register with both DOCSIS 3.1 and pre-DOCSIS 3.1 CMTS platforms. When the DOCSIS 2.0 CM with IPv6 support registers with a DOCSIS 2.0 CMTS, registration follows [13]. When a DOCSIS 2.0 CM with IPv6 support registers with a DOCSIS 3.1 CMTS, registration may follow eithe... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.2.6.3.1 Channel Assignment During Registration | The Registration Request message can have a number of TLVs which will influence the selection of downstream and upstream channels that the CMTS assigns to CMs operating in Multiple Receive Channel (MRC) mode in the Registration Response. Additionally, some of these TLVs will cause the CMTS to re-direct CMs not operatin... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.2.7 Baseline Privacy Initialization | Following registration, if the CM is provisioned to run Baseline Privacy and EAE was not enabled, the CM shall initialize Baseline Privacy operations, as described in [14]. |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.2.8 Service IDs During CM Initialization | After completion of the Registration process (see clause 10.2.6), the CM will have been assigned Service IDs (SIDs) to match its provisioning. However, the CM needs to complete a number of protocol transactions prior to that time (e.g. Ranging, DHCP, etc.), and requires a temporary Service ID in order to complete those... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.3 Periodic Maintenance | Remote RF signal level adjustment at the CM is performed through a periodic maintenance function using the unicast RNG-REQ MAC Management messages, probes, and RNG-RSP MAC messages. This is shown in figure 10.36 and figure 10.37. Note that each figure represents the operation for a single upstream channel on a CM. The ... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.4 OFDM Profile Usability Testing Process | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.4.0 Objective | Prior to Registration, a CM only has one downstream profile (Profile A) and one upstream profile (IUC 13) available to it. To maximize capacity and for other reasons the CMTS needs a way to test the physical layer performance of a given CM on a downstream or upstream profile so that it can determine what profiles can s... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.4.1 Downstream Profile Usability Testing Process | The design goal of the downstream profile testing process is to enable rapid determination of the usability by a given CM of profiles already being made available in the downstream via DPD messages. The optimization of the profiles themselves to best serve a given population of CMs is outside the scope of the present d... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.4.2 Upstream OFDMA Data Profile Assignment and Testing | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.4.2.1 Assignment of OFDMA Upstream Data Profile (OUDP) IUCs | It is intended that the Burst Descriptor associated with Data Profile IUC 13 be configured as a robust OFDMA profile usable by any DOCSIS 3.1 CM served by that upstream channel. The CMTS shall use Data Profile IUC 13 for all OFDMA data grants to modems which have not completed registration. The CM shall be capable of t... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.4.2.2 Upstream Profile Testing | Because it is expected that not all upstream data profiles will be usable by all modems, a CMTS might wish to evaluate a modem's performance using a particular profile before assigning that profile to be used for "live" traffic. A CMTS performs such an evaluation in vendor-specific ways. The present document provides v... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.4.2.3 Upstream Probes and RxMER Measurements | A CMTS uses upstream probes for ranging-related functions such as determining transmit pre-equalizer coefficients [12]. A CMTS also has the option of using an upstream probe to take an RxMER measurement. To do this, the CMTS grants P-IEs in a P-MAP message (clause 6.4.4] with the "MER" bit set. When the CMTS receives t... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.4.2.4 Upstream Data Profile Testing Bursts | Some types of upstream profile performance measurements cannot be performed using probe bursts. For example, a CMTS might wish to gather information on FEC performance or count CRC errors for a particular profile. Probe bursts cannot be used for these purposes since they carry no information. To enable a CMTS to make t... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.5 Fault Detection and Recovery | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.5.0 Fault Detection and Recovery Mechanisms | Fault detection and recovery occurs at multiple levels: • At the physical level, FEC is used to correct errors where possible - refer to [12] for details. • At the Transmission Convergence layer, the CM can use the continuity counter and Payload Unit Start Indicator (PUSI) to detect and recover from lost MPEG packets f... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.5.1 CM Downstream Channel Lost Lock Handling | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.5.1.0 Lost Lock Handling Mechanism | A Downstream Channel signal is considered to be valid when the modem has achieved the following steps: • On a SC-QAM channel: - Synchronization of the QAM symbol timing. - Synchronization of the FEC framing. - Synchronization of the MPEG packetization. - For a Primary Downstream Channel, recognition of SYNC downstream ... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.5.1.1 Primary Downstream Channel Interruption | An interruption of the Primary Downstream Channel occurs when all of the following conditions are met: • The interruption occurs on a downstream that is valid before and after the loss. • The interruption is defined as an instantaneous loss of signal and after a predetermined delay, an instantaneous return to the origi... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.5.1.2 Primary Downstream Channel Redundancy | If the CM loses its Primary Downstream channel and then it successfully acquires master clock reference timing from a backup primary downstream channel, the CM shall not transmit on any channel until it has adjusted for any timing skew between the originally designated Primary Downstream and Backup Primary downstream c... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.5.2 MAC Layer Error-Handling | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.5.2.0 Types of MAC Layer Errors | This clause describes the procedures that are required when an error occurs at the MAC framing level. The most obvious type of error occurs when the HCS on the MAC Header fails. This can be a result of noise on the HFC network or possibly by collisions in the upstream channel. Framing recovery on the downstream channel... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.5.2.1 Error Recovery During Pre-3.0 DOCSIS Fragmentation | There are some special error handling considerations for fragmentation. Each fragment has its own fragmentation header complete with a Fragment Header Checksum (FHCS) and its own FCRC. There may be other MAC headers and CRCs within the fragmented payload. However, only the FHCS and the FCRC are used for error detection... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.5.2.2 Error Recovery During Segmentation with Segment Headers On | There are some special error handling considerations for segmentation with Segment Headers On. Each segment has its own segment header complete with an HCS. If the HCS for a segment fails, the CMTS shall discard that segment. If the HCS passes for a segment, the CMTS may process any bandwidth request in the segment hea... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.5.3 Partial Channel Mode of OFDM Downstream Channel | Partial channel mode of operation occurs whenever one or more profiles on an OFDM downstream channel are unusable. A profile is deemed to be unusable when an operational CM is unable to receive data correctly from one or more provisioned profiles or from the PLC. The CM signals to the CMTS that the CM is in a partial c... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.5.4 CM Status Report | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.5.4.0 Overview | CM-STATUS messages are needed in cases where the CM detects a failure that the CMTS cannot detect directly (for example, a failure in the CIN where an M-CMTS is used), or where the CM can send valuable information to the CMTS when an error or a recovery event occurs (for example, the CM can report a T3 timeout to the C... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.5.4.1 CM Requirements | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.5.4.1.0 General | A CM shall transmit a CM-STATUS message on any available channel when it detects an event condition listed in table 10.4 for any object and reporting of the event type for that object is enabled on the CM. Table 10.4 describes the trigger conditions that set each event "on", and the reset conditions at which the event ... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.5.4.1.1 CM-STATUS State Diagram | Figure 10.42: CM-STATUS Event Type State Machine Operation of the CM-STATUS Event Type State Machine is described below. ETSI ETSI TS 103 311-3 V1.1.1 (2017-02) 403 The CM is considered to be in one of two stable states for each CM-STATUS event type: IDLE or SENDING. The state machine starts in the IDLE state with the ... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.5.4.1.2 Event Codes | As described above, reporting for each of these events is controlled by CM-STATUS Event Enable Bitmask and CM-STATUS Event Control TLV in the MDD message and CM-CTRL-REQ message. The CM power events (Codes 9 and 10) are only applicable to CMs with battery backup capability. These events are used to signal the CMTS when... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.5.4.2 CMTS Requirements | If the CMTS does not confirm the CM-STATUS-ACK modem capability in a CM's Registration Response, the CMTS shall not send a CM-STATUS-ACK message to the CM. If the CMTS receives a CM-STATUS with an event code and transaction ID for which it has already transmitted a CM- STATUS-ACK message, the CMTS shall retransmit the ... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.6 DOCSIS Path Verification | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.6.1 DPV Overview | The DOCSIS Path Verify (DPV) protocol offers two modes of operation: • Per Path: An operational mode which will permit the measurement of latency between two particular DPV reference points. This mode uses a dedicated MAC Management Message to perform the measurement. • Per Packet: A diagnostics mode where the source (... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.6.2 DPV Reference Points | The reference points recognized by DPV are shown in figure 10.43. The expression "DS MAC" refers to the downstream MAC processing element and the term "US MAC" refers to the upstream MAC processing element. Figure 10.43: DPV Reference Diagram Each direction, downstream and upstream, has a separate set of reference poin... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.6.3 DPV Math | The difference between the Timestamp End and the Timestamp Start in the DPV-RSP (see clause 6.4.34) does not include downstream propagation delay in the HFC, and thus should be considered a relative latency rather than an absolute latency. The reason for this has to do with how timestamps are used and distributed in a ... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.6.4 DPV Per Path Operation | The DPV Per Path feature is appropriate for sampling the latency of a particular data path and for generating long term averages. DPV Per Path measurements can be made independent of the data packet flow. Latency measurements may be useful in the downstream direction for several applications, including the determinatio... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.6.5 DPV Per Packet Operation | The DPV Per Packet operation is appropriate for determining the maximum and minimum latency seen by the packets of a particular service flow. DPV Per Packet operation can only be performed when data packets are present in the service flow. The DPV Per Packet operation is performed by having the source device generate a... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.7 DOCSIS Time Protocol | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.7.1 DTP Overview | The DOCSIS Time Protocol (DTP) is a set of techniques coupled with extensions to the DOCSIS signalling messages. The CMTS MAY support DTP. The CM MAY support DTP. DTP allows the timing and frequency system of DOCSIS to be interfaced to external timing protocols with high accuracy. Once the CMTS has a legitimate frequen... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.7.2 DOCSIS and PTP Clock Types | Timing protocols, [15] in particular, define different types of network clocks. In DTP, the CMTS and the CM appear as one DOCSIS system that then interfaces to the outside world. When doing so, the DOCSIS system can assume different types of clocks. The DOCSIS system can act as a Grandmaster Clock (GC) for a [15] syste... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.7.3 True Ranging Offset | In all timing protocol solutions, the delay through the system has to be measured and added to the timestamp so that the timestamp value is the same at all reference points. The general approach is to measure the round trip delay of a link, account for asymmetry, and then divide by two to derive the one-way delay. Timi... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.7.4 DTP Math | A mathematical representation of the DTP math is shown in figure 10.46. ETSI ETSI TS 103 311-3 V1.1.1 (2017-02) 416 Figure 10.46: DTP Math and Delays The subscripts used in describing the delays are: • cmts, hfc, and cm indicate the three basic elements of the system. • ds (downstream) and us (upstream) indicate the di... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.7.5 DTP Example | An example that shows the relationship between DTP math and the DTP True Ranging Offset is shown in figure 10.47. Figure 10.47: True Ranging Offset Example In this example, all the final values are shown. The numbers used are arbitrary and are for the sake of illustration. Each element (CMTS, HFC, CM) in each direction... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.7.6 DTP Signalling | The goal of DTP is to generate a time adjustment (t-adj) that can be added to the native timestamp of the CM to create a timestamp that matches the CMTS timestamp in real time. Either the CMTS or the CM can perform the DTP calculations. The entity performing the calculation is known as the DTP Master. The other entity ... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.7.7 DTP Configuration | CM and CMTS support for DTP varies. The CMTS and CM might support DTP Master Mode, DTP Slave Mode, or no DTP operation. DOCSIS Time Protocol is enabled and configured via the DOCSIS Time Protocol Mode modem capability. The CM reports which DOCSIS Time Protocol Modes it supports using the DOCSIS Time Protocol Mode modem... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 10.7.8 DTP System Level Performance | The goal of a DTP system is to enable the efficient and accurate transfer of an external timing protocol across a DOCSIS system. Figure 10.50: DTP System Performance Figure 10.50 shows a DTP system that couples a timing protocol from the NSI or DTI port of the CMTS to the CMCI port of two CMs. The external timing proto... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 11 Dynamic Operations | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 11.1 Upstream Channel Descriptor Changes | Whenever the CMTS is to change any of the upstream burst characteristics specified in the Upstream Channel Descriptor (UCD) message (see clause 6.4.3), it needs to provide for an orderly transition from the old values to the new values by all CMs. Whenever the CMTS is to change any of the upstream characteristics, it s... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.