hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.3.3 Subcarrier to Minislot Mapping for OFDMA Channels | The CM shall derive a subcarrier to minislot mapping from the total number of available subcarriers, number of subcarriers per minislot as indicated by the Subcarrier Spacing TLV value, exclusion bands, and unused subcarriers specified in the UCD message. The CMTS shall specify all exclusion bands and unused subcarrier... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.3.4 Required Burst Attributes on OFDMA Channels | The CMTS shall include the following burst attributes for various IUCs that can have burst descriptors in a Type 51 UCD: • IUC 1 and IUC 2: no burst attributes specific to IUC 1 and IUC 2 are included in the UCD. • IUC 3: Preamble Length, Preamble Value Offset, Nir. • IUC 4: Preamble Length, Preamble Value Offset, Nfr.... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.4 Upstream Bandwidth Allocation Map (MAP) | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.4.0 MAP Types, Message Format and Information Elements | There are two versions of MAP messages. MAP messages with a version number of 1 are understood by DOCSIS 1.0, 1.1, 2.0, 3.0 and 3.1 equipment and are used for bandwidth allocation on TDMA and S-CDMA upstream channels. MAP messages with a version number of 5 are understood only by DOCSIS 3.1 equipment and are used for b... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.4.1 Upstream Quiet Probe Measurement | For Proactive Network Maintenance (PNM) and upstream profile evaluation, the CMTS shall provide the capability to measure the upstream channel during "quiet" symbol times when no CM is actively transmitting, permitting accurate measurement of the underlying noise, intermods and ingress. In order to facilitate this cond... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.5 Ranging Request Messages | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.5.0 Types of Ranging Request Messages | Ranging Request messages are transmitted by a CM at initialization on an upstream and periodically (for upstream Types 1 - 4) on request from the CMTS to determine network delay and request power adjustment. There are four types of Ranging Request messages: RNG-REQ, INIT-RNG-REQ, B-INIT-RNG-REQ, and O-INIT-RNG-REQ. The... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.5.1 Ranging Request (RNG-REQ) | The RNG-REQ message transmitted by the CM shall use an FC_TYPE = MAC Specific Header and FC_PARM = Timing MAC Header, followed by a Packet PDU in the format shown in figure 6.25. Figure 6.25: RNG-REQ Format The parameters of RNG-REQ messages transmitted by the CM shall be as follows: SID: For RNG-REQ messages transmitt... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.5.2 Initial Ranging Request (INIT-RNG-REQ) | The INIT-RNG-REQ message transmitted by legacy CMs use an FC_TYPE = MAC Specific Header and FC_PARM = Timing MAC Header, followed by a Packet PDU in the format shown in figure 6.26. The INIT-RNG-REQ differs from the RNG-REQ in that it has an upstream channel ID in place of the Reserved field in a RNG-REQ. Figure 6.26: ... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.5.3 Bonded Initial Ranging Request (B-INIT-RNG-REQ) | The B-INIT-RNG-REQ message transmitted by a CM shall use an FC_TYPE = MAC Specific Header and FC_PARM = Timing MAC Header, followed by a Packet PDU in the format shown in figure 6.27. The B-INIT-RNG-REQ differs from the INIT-RNG-REQ in that it includes the MD-DS-SG-ID used for downstream topology resolution and a set o... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.5.4 OFDMA Initial Ranging Request (O-INIT-RNG-REQ) | The O-INIT-RNG-REQ message is transmitted only in Initial Maintenance Regions and only on OFDMA upstream channels. This message does not use the standard MAC Frame format but uses a condensed format to conserve bandwidth on the OFDMA channel. The O-INIT-RNG-REQ transmitted by a CM shall use the format shown in figure 6... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.6 Ranging Response (RNG-RSP) | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.6.0 RNG-RSP Message Format | A Ranging Response shall be transmitted by a CMTS in response to received RNG-REQ, INIT-RNG-REQ, B-INIT- RNG-REQ, O-INIT-RNG-REQ, or probe. The state machines describing the ranging procedure appear in clause 10.2.3.4. In that procedure it may be noted that, from the point of view of the CM, reception of a Ranging Resp... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.6.1 RNG-RSP Encodings | The type values used by the CMTS in the RNG-RSP shall comply with table 6.32 and figure 6.30. These are unique within the ranging response message but not across the entire MAC message set. The type and length fields used by the CMTS in the RNG-RSP shall each be 1 octet in length. Table 6.32: Ranging Response Message E... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.6.2 Example of TLV Data | An example of TLV data is given in figure 6.30. ETSI ETSI TS 103 311-3 V1.1.1 (2017-02) 134 Figure 6.30: Example of TLV Encoded Data |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.6.3 Transmit Equalization Encodings for S-CDMA and TDMA Channels | Figure 6.31: Equalization Coefficient Encodings for S-CDMA and TDMA Channels The number of taps per modulation interval T signalled by the CMTS shall be either 1, 2, or 4. The main tap location refers to the position of the zero delay tap, between 1 and N. For a T-spaced equalizer, the number of taps per modulation int... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.6.4 Transmit Equalization Encodings for OFDMA Channels | Figure 6.32: Equalization Coefficient Encodings for OFDMA Channels To reduce the number of coefficients sent, it is intended that the range encompassed by the lowest subcarrier number and highest subcarrier number not include exclusion bands that are below and above the active subcarriers in the OFDMA channel. For subc... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.6.5 RNG-RSP Channel Overrides | The RNG-RSP message allows the CMTS to instruct the modem to move to a new downstream and/or upstream channel and to repeat initial ranging. However, the CMTS may do this only in response to an initial ranging request from a modem that is attempting to join the network, or in response to any of the unicast ranging requ... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.6.6 Upstream Channel Adjustments | A CMTS sends this TLV for use in upstream ambiguity resolution and for post registration ranging adjustments to one or more upstream channels other than the upstream channel indicated by the Upstream Channel ID encoded in the body of the RNG-RSP message prior to the TLV encodings. ETSI ETSI TS 103 311-3 V1.1.1 (2017-02... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.6.7 T4 Timeout Multiplier | In Multiple Transmit Channel Mode the CMTS MAY increase the value of the T4 timeout by means of the T4 Timeout Multiplier in order to reduce CMTS overhead associated with scheduling RNG-REQ slots and processing RNG-RSP messages. The CM shall set its T4 timeout to the value of the multiplier times the default T4 timeout... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.6.8 Commanded Power | The CMTS uses the Commanded Power TLV after Registration to control the Dynamic Range Window and the transmit power level for all of the upstream channels in the CM's Transmit Channel Set. The Commanded Power TLV contains two sub-TLVs. ETSI ETSI TS 103 311-3 V1.1.1 (2017-02) 137 Table 6.34: Commanded Power Sub-TLVs Nam... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.7 Registration Request Messages | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.7.0 Types of Registration Request Messages | The CM transmits a Registration Request message after receipt of a CM configuration file as specified in clause 10.2. There are two types of Registration Request messages: the single frame Registration Request message (referred to as REG-REQ), and the Multipart Registration Request message (referred to as REG-REQ-MP). ... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.7.1 Registration Request (REG-REQ) | Figure 6.33: Registration Request (REG-REQ) A legacy CM generates Registration Requests in the form shown in figure 6.33, including the following parameters: SID: Temporary SID for this CM. All other parameters are coded as TLV tuples as defined in Annex C. |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.7.2 Multipart Registration Request (REG-REQ-MP) | Figure 6.34: Multipart Registration Request (REG-REQ-MP) ETSI ETSI TS 103 311-3 V1.1.1 (2017-02) 139 A CM shall generate Multipart Registration Requests in the form shown in figure 6.34, including the following parameters: SID: Temporary SID for this CM. Number of Fragments: Fragmentation allows the REG-REQ-MP TLV para... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.8 Registration Response Messages | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.8.0 Types and Formatting of Registration Response Messages | There are two types of Registration Response messages: the single frame Registration Response message (referred to as REG-RSP), and the Multipart Registration Response message (referred to as REG-RSP-MP). The present document will use the terms "REG-RSP" and "REG-RSP-MP" when it is important to make a distinction betwe... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.8.1 Registration Response (REG-RSP) | A Registration Response shall be transmitted by the CMTS in response to a received REG-REQ. To provide for flexibility, the message parameters following the Response field shall be encoded by the CMTS in a TLV format. ETSI ETSI TS 103 311-3 V1.1.1 (2017-02) 141 Figure 6.35: Registration Response Format A CMTS shall gen... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.8.2 Multipart Registration Response (REG-RSP-MP) | A Multipart Registration Response shall be transmitted by the CMTS in response to a received REG-REQ-MP. To provide for flexibility, the message parameters following the Response field shall be encoded by the CMTS in a TLV format. Figure 6.36: Multipart Registration Response Format ETSI ETSI TS 103 311-3 V1.1.1 (2017-0... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.8.3 Encodings | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.8.3.0 General | The type values used by the CMTS shall be those shown below. These are unique within the Registration Response message but not across the entire MAC message set. The type and length fields used by the CMTS shall each be 1 octet. |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.8.3.1 Modem Capabilities | This field defines the CMTS response to the modem capability field in the Registration Request. The CMTS shall respond to the modem capability to indicate whether they may be used. If the CMTS is setting a capability to "on" (indicating that it may be used), unless explicitly indicated otherwise in clause C.1.3.1, the ... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.8.3.2 DOCSIS 1.0 Service Class Data | If the CMTS supports DOCSIS 1.0 CMs, then the CMTS shall include a DOCSIS 1.0 Service Class Data parameter in the Registration Response for each DOCSIS 1.0 Class of Service parameter (see the clause DOCSIS 1.0 Class of Service Configuration Setting in Annex C) in the Registration Request. This encoding defines the para... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.9 Registration Acknowledge (REG-ACK) | A Registration Acknowledge shall be transmitted by the CM in response to a REG-RSP or REG-RSP-MP from the CMTS under the circumstances described in clause 10.2.6.1. It confirms acceptance by the CM of the Registration Response parameters as reported by the CMTS. The CM shall format a REG-ACK as shown in figure 6.37. ET... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.10 Upstream Channel Change Request (UCC-REQ) | The Upstream Channel Change (UCC) feature is not required for DOCSIS 3.1, thus there is no need to support a UCC-REQ message from a DOCSIS 3.1 CMTS. The CM shall ignore a UCC-REQ message received from a CMTS. |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.11 Upstream Channel Change Response (UCC-RSP) | The Upstream Channel Change (UCC) feature is not required for DOCSIS 3.1, thus there is no need to support a UCC-REQ message from a DOCSIS 3.1 CMTS. Refer to clause 6.4.10. |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.12 Dynamic Service Addition - Request (DSA-REQ) | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.12.0 DSA-REQ Message Format | A Dynamic Service Addition Request MAY be sent by a CM or CMTS to create a new Service Flow. Figure 6.38: Dynamic Service Addition - Request A CM or CMTS shall generate DSA-REQ messages in the form shown in figure 6.38 including the following parameter: Transaction ID: Unique identifier for this transaction assigned by... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.12.1 CM-Initiated Dynamic Service Addition | The CM shall use the Service Flow Reference to link Classifiers to Service Flows when generating a CM initiated DSA-REQ. Values of the Service Flow Reference are local to the DSA message; each Service Flow within the DSA-Request shall be assigned a unique Service Flow Reference by the CM. This value need not be unique ... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.12.2 CMTS-Initiated Dynamic Service Addition | CMTS-initiated DSA-Requests shall use the Service Flow ID to link Classifiers to Service Flows. Service Flow Identifiers are unique within the MAC domain. CMTS-initiated DSA-Requests for Upstream Service Flows shall also include a Service ID. CMTS-initiated DSA-Requests which include Classifiers, shall assign a unique ... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.13 Dynamic Service Addition - Response (DSA-RSP) | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.13.0 DSA-RSP Message Format | A Dynamic Service Addition Response shall be generated in response to a received DSA-Request by a CM or CMTS. The format of a DSA-RSP used by a CM or CMTS shall be as shown in figure 6.39. ETSI ETSI TS 103 311-3 V1.1.1 (2017-02) 147 Figure 6.39: Dynamic Service Addition - Response The parameters of DSA-RSP transmitted ... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.13.1 CM-Initiated Dynamic Service Addition | The CMTS's DSA-Response for Service Flows that are successfully added shall contain a Service Flow ID. The CMTSs DSA-Response for successfully Admitted or Active upstream QoS Parameter Sets shall also contain a Service ID. If the corresponding DSA-Request uses the Service Class Name (see clause C.2.2.5.4) to request se... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.13.2 CMTS-Initiated Dynamic Service Addition | If the transaction is unsuccessful, the CM shall use the Classifier Identifier(s) and Service Flow Identifier(s) to identify the failed parameters in the DSA-RSP. |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.14 Dynamic Service Addition - Acknowledge (DSA-ACK) | A Dynamic Service Addition Acknowledge shall be generated by a CM or CMTS in response to a received DSA-RSP. The format of a DSA-ACK transmitted by a CM or CMTS shall be as shown in figure 6.40. Figure 6.40: Dynamic Service Addition - Acknowledge The parameters of a DSA-ACK transmitted by a CM or CMTS shall be as follo... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.15 Dynamic Service Change - Request (DSC-REQ) | A Dynamic Service Change Request MAY be sent by a CM or CMTS to dynamically change the parameters of an existing Service Flow. If a CMTS sends a DSC-REQ message changing an Upstream Drop Classifier, then conceptually the Upstream Drop Classifier is associated with a NULL Service Flow that is not signalled in the DSC-RE... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.16 Dynamic Service Change - Response (DSC-RSP) | A Dynamic Service Change Response shall be generated by a CM or CMTS in response to a received DSC-REQ. ETSI ETSI TS 103 311-3 V1.1.1 (2017-02) 151 Figure 6.42: Dynamic Service Change - Response A CM or CMTS shall generate DSC-RSP messages in the form shown in figure 6.42 including the following parameters as described... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.17 Dynamic Service Change - Acknowledge (DSC-ACK) | A Dynamic Service Change Acknowledge shall be generated by a CM or CMTS in response to a received DSC-RSP. Figure 6.43: Dynamic Service Change - Acknowledge A CM or CMTS shall generate DSC-ACK messages in the form shown in figure 6.43 including the following parameters as described below: Transaction ID: Transaction ID... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.18 Dynamic Service Deletion - Request (DSD-REQ) | A DSD-Request MAY be sent by a CM or CMTS to delete a single existing Upstream Service Flow and/or a single existing Downstream Service Flow. ETSI ETSI TS 103 311-3 V1.1.1 (2017-02) 153 Figure 6.44: Dynamic Service Deletion - Request A CM or CMTS shall generate DSD-REQ messages in the form shown in figure 6.44 includin... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.19 Dynamic Service Deletion - Response (DSD-RSP) | A DSD-RSP shall be generated by a CM or CMTS in response to a received DSD-REQ. Figure 6.45: Dynamic Service Deletion - Response A CM or CMTS shall generate DSD-RSP messages in the form shown in figure 6.45 including the following parameters as described below: Transaction ID: Transaction ID from the corresponding DSD-... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.20 Dynamic Channel Change - Request (DCC-REQ) | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.20.0 DCC-REQ Message Format | A Dynamic Channel Change Request may be transmitted by a CMTS to cause a DOCSIS 3.1 CM to change MAC domains. A Dynamic Channel Change Request may be transmitted by a CMTS to cause a pre-DOCSIS 3.1 CM to change the upstream channel on which it is transmitting, the downstream channel on which it is receiving, or both. T... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.20.1 Encodings | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.20.1.0 General | The type values used by the CMTS in a DCC-REQ shall be those shown below. These are unique within the Dynamic Channel Change Request message, but not across the entire MAC message set. |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.20.1.1 Upstream Channel ID | When present, this TLV specifies the new upstream channel ID that the CM shall use when performing a Dynamic Channel Change. It is an override for the current upstream channel ID. The CMTS SHOULD ensure that the Upstream Channel ID for the new channel is different than the Upstream Channel ID for the old channel. This ... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.20.1.2 Downstream Parameters | 6.4.20.1.2.0 General When present, this TLV specifies the operating parameters of the new downstream channel. The value field of this TLV contains a series of sub-types. Type Length Value 2 n List of subtypes The CMTS shall include this TLV when specifying a downstream channel change. If this TLV is missing, the CM sha... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.20.1.3 Initialization Technique | This TLV allows the CMTS to direct the CM to reinitialize its MAC when moving a CM to a different MAC domain. While changing the MAC domain of a D-3.1 CM, CMTS shall use initialization technique 0 (re-initialize the MAC) and include this TLV. The CMTS shall use initialization technique 0 (re-initialize the MAC) when ch... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.20.1.4 UCD Substitution | When present, this TLV allows the CMTS to send an Upstream Channel Descriptor message to the CM. This UCD message is intended to be associated with the new upstream and/or downstream channel(s). The CM stores this UCD message in its cache, and uses it after synchronizing to the new channel(s). Type Length Value 4 n UCD... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.20.1.5 Security Association Identifier (SAID) Substitution | When present, this TLV allows the CMTS to replace the Security Association Identifier (SAID) in the current Service Flow with a new Security Association Identifier. The CMTS shall ensure that the baseline privacy keys associated with the SAID remain the same. Type Length Value 6 4 Current SAID (lower-order 14 bits of a... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.20.1.6 Service Flow Substitutions | 6.4.20.1.6.0 General When present, this TLV allows the CMTS to replace specific parameters within the current Service Flows on the current channel assignment with new parameters for the new channel assignment. One TLV is used for each Service Flow that requires changes in parameters. The CMTS may choose to do this to h... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.20.1.7 CMTS MAC Address | When present, this TLV allows the current CMTS to send the MAC address of the destination CMTS corresponding to the target downstream frequency. Type Length Value 8 6 MAC Address of Destination CMTS The CMTS shall include this TLV if the CM is changing downstream channels and UCD substitution is specified or if the CM ... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.21 Dynamic Channel Change - Response (DCC-RSP) | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.21.0 DCC-RSP Message Format | A Dynamic Channel Change Response shall be transmitted by a CM in response to a received Dynamic Channel Change Request message to indicate that it has received and is complying with the DCC-REQ. The format of a DCC- RSP message transmitted by a CM shall be as shown in figure 6.47. Before it begins to switch to a new u... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.21.1 Encodings | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.21.1.0 General | A pre-DOCSIS 3.1 CM might use the type values shown below. These are unique within the Dynamic Channel Change Response message, but not across the entire MAC message set. |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.21.1.1 CM Jump Time | 6.4.21.1.1.0 General When present, this TLV allows the CM to indicate to the CMTS when the CM plans to perform its jump and be disconnected from the network. With this information, the CMTS MAY take preventative measures to minimize or to eliminate packet drops in the downstream due to the channel change. Type Length V... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.22 Dynamic Channel Change - Acknowledge (DCC-ACK) | A Dynamic Channel Change Acknowledge shall be transmitted by a CMTS in response to a received Dynamic Channel Change Response message on the new channel with its Confirmation Code set to arrive(1). The format of a DCC-ACK message transmitted by a CMTS shall be as shown in figure 6.48. Figure 6.48: Dynamic Channel Chang... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.23 Device Class Identification Request (DCI-REQ) | The Device Class Identification Request (DCI-REQ) message is not required for DOCSIS 3.1. Hence when a DOCSIS 3.1 CM is registered with a DOCSIS 3.1 CMTS, it is not required to send DCI-REQ after ranging complete, so there is no need to support DCI-RSP messages from a DOCSIS 3.1 CMTS. |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.24 Device Class Identification Response (DCI-RSP) | The Device Class Identification Request (DCI-REQ) message is not required for DOCSIS 3.1. Hence when a DOCSIS 3.1 CM is registered with a DOCSIS 3.1 CMTS, it is not required to send DCI-REQ after ranging complete, so there is no need to support DCI-RSP messages from a DOCSIS 3.1 CMTS. |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.25 Upstream Transmitter Disable (UP-DIS) | The Upstream Transmitter Disable (UP-DIS) message is not required for DOCSIS 3.1, hence there is no need for a DOCSIS 3.1 CMTS to send this type of message to DOCSIS 3.1 CM. If received, the CM shall ignore UP-DIS message. ETSI ETSI TS 103 311-3 V1.1.1 (2017-02) 162 |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.26 Test Request (TST-REQ) | Test Request (TST-REQ) is not required for DOCSIS 3.1, hence there is no need for a DOCSIS 3.1 CMTS to send this type of message to DOCSIS 3.1 CM. If received, the CM shall ignore TST-REQ message. |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.27 Downstream Channel Descriptor (DCD) | The format and usage of the DCD message is defined in [4]. |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.28 MAC Domain Descriptor (MDD) | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.28.0 MDD Message Format | A CMTS shall transmit an MDD message periodically on every downstream channel in the MAC Domain. The CMTS shall observe the MDD Interval specified in Annex B. The CMTS shall transmit a separate MDD message for every downstream channel. The CMTS shall not transmit an MDD message with a total Management Message Payload s... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.28.1 MDD TLV Encodings | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.28.1.0 General | The CMTS shall use the type values defined in this clause. These are unique within the MDD message, but not across the entire MAC message set. Unless explicitly indicated otherwise, each of these TLVs shall be included by the CMTS exactly once in each MDD message on a primary-capable downstream channel. |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.28.1.1 Downstream Active Channel List TLV | Each instance of this TLV represents one downstream channel in the MAC Domain. The CMTS MAY include this TLV more than once in a given MDD message. When sending this message on a primary-capable downstream channel, the CMTS shall include a Downstream Active Channel List TLV for every downstream channel in every MD-DS-S... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.28.1.2 MAC Domain Downstream Service Group (MD-DS-SG) TLV | When Downstream Channel Bonding is enabled in a MAC Domain, the CMTS shall transmit one or more instances of this TLV on the primary-capable downstream channels of the MAC Domain. When Downstream Channel Bonding is not enabled in a MAC Domain, the CMTS MAY omit this TLV. When present, CMTS shall insert this TLV once fo... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.28.1.3 Downstream Ambiguity Resolution Frequency List TLV | This TLV lists downstream frequencies to be used for CM-SG ambiguity resolution per clause 10.2.3. The CMTS shall include this TLV when sending an MDD message on a primary-capable downstream channel if either Upstream Channel Bonding or Downstream Channel Bonding is enabled for the MAC Domain and this MDD message conta... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.28.1.4 Receive Channel Profile Reporting Control TLV | This TLV controls the reporting of Receive Channel Profiles by CMs in the REG-REQ-MP message. See clause 8.2.4 for details on Receive Channel Profiles. When sending an MDD message on a primary-capable downstream channel, the CMTS shall include this TLV. The CMTS shall comply with table 6.40 and table 6.41. When sending... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.28.1.5 IP Initialization Parameters TLV | This TLV is used to communicate to the CM certain parameters related to the initialization of the CM's IP-layer services. When sending an MDD message on a primary-capable downstream channel, the CMTS shall include this TLV. The CMTS shall comply with table 6.42 and table 6.43. When sending an MDD on a non-primary-capab... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.28.1.6 Early Authentication and Encryption (EAE) Enable/Disable TLV | This TLV is used to indicate whether the CM is required to perform early authentication and encryption for security purposes. When sending the MDD on a primary-capable downstream channel, the CMTS shall include this TLV. When sending the MDD on a non-primary-capable downstream channel, the CMTS shall not include this T... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.28.1.7 Upstream Active Channel List TLV | Each instance of this TLV represents one active upstream channel in the MAC Domain. The CMTS MAY include this TLV more than once in a given MDD message. When sending the MDD on a primary-capable downstream channel, the CMTS shall include an instance of this TLV for every active upstream channel in each MD-CM-SG that in... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.28.1.8 Upstream Ambiguity Resolution Channel List TLV | This TLV lists upstream channel IDs to be used for CM-SG ambiguity resolution per clause 10.2.3. When sending the MDD on a primary-capable downstream channel, the CMTS shall include this TLV. When sending the MDD on a non- primary-capable downstream channel, the CMTS shall not include this TLV. The CMTS shall comply wi... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.28.1.9 Upstream Frequency Range TLV | This TLV indicates the frequency range of the plant reserved for upstream transmission. When sending the MDD on a primary-capable downstream channel, the CMTS shall include this TLV. When sending the MDD on a non-primary- capable downstream channel, the CMTS shall not include this TLV. The CMTS shall format and use the... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.28.1.10 Symbol Clock Locking Indicator | ETSI EN 302 878-3 [3] requires the CMTS to lock its Symbol Clock to the Master Clock. This TLV indicates whether or not the symbol clock for the current downstream channel is locked to the CMTS Master Clock. When sending the MDD on a primary-capable downstream channel, the CMTS shall include this TLV. When sending the ... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.28.1.11 CM-STATUS Event Control | The CM-STATUS reporting mechanism includes a random holdoff prior to transmission of status report messages. This TLV indicates the value of that random holdoff timer to be used by the CM when determining when/whether to transmit a CM-STATUS message. This TLV associates a separate hold-off timer value with each CM-STAT... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.28.1.12 Upstream Transmit Power Reporting | This TLV indicates whether the CM should report its upstream transmit power in the SSAP field of the MAC Management Header of the RNG-REQ, INIT-RNG-REQ, and B-INIT-RNG-REQ messages. The reporting of upstream transmit power is described in clause 6.4.5. When sending the MDD on a primary-capable downstream channel, the C... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.28.1.13 DSG DA-to-DSID Association Entry | This TLV conveys the association between a DSID and a MAC Destination Address being used for DSG. It is necessary to communicate this information in a broadcast downstream message for DOCSIS 3.0 DSG modems operating in one-way mode. The CMTS is not required to include this TLV in the MDD if the CMTS has been configured... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.28.1.14 CM-STATUS Event Enable for Non-Channel-Specific Events | The CMTS MAY include one instance of this TLV in a MDD message on a primary-capable downstream channel. When sending an MDD on a non-primary-capable downstream channel, the CMTS shall not include this TLV. Table 6.54: CM-STATUS Event Enable for Non-Channel-Specific Events TLV Type Length Value 15 2 CM-STATUS Event Enab... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.28.1.15 Extended Upstream Transmit Power Support | This encoding within the MDD message signals whether or not modems may transmit at power levels greater than the default Pmax values defined in [12] prior to registration (post registration behaviour is controlled via the Extended Upstream Transmit Power capability as defined in the clause C.1.3.1.40). By default, the ... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.28.1.16 CMTS DOCSIS Version | This encoding within the MDD message signals the version of DOCSIS being supported by the CMTS. A CMTS compliant to the present document shall report a CMTS Major DOCSIS Version of 3 and a CMTS Minor DOCSIS Version of 1. If this TLV is absent in an MDD message on a primary-cable downstream channel, then the CM shall as... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.28.1.17 CM Periodic Maintenance Timeout Indicator | This encoding within the MDD message instructs the modem as to the Periodic Maintenance timeout behaviour for OFDMA channels. The CMTS sets this TLV based on its Periodic Maintenance implementation. The CMTS sets a value of "use Unicast Ranging opportunity" to indicate that the CM is required to utilize the T4 timer an... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.28.1.18 DLS Broadcast and Multicast Delivery Method TLV | This encoding within the MDD message communicates the method of broadcast and multicast delivery to CMs in DLS mode. The available methods are described in clause 11.7.4.5. The CMTS shall include one instance of DLS Broadcast and Multicast Delivery Method TLV in an MDD message on a primary-capable OFDM downstream chann... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.28.1.19 CM-STATUS Event Enable for DOCSIS 3.1 Specific Events | The CMTS MAY include one instance of this TLV in a MDD message on a primary-capable downstream channel. When sending an MDD on a non-primary-capable downstream channel, the CMTS shall not include this TLV. Table 6.60: CM-STATUS Event Enable for DOCSIS 3.1 Events TLV Type Length Value 19 4 CM-STATUS Event Enable Bitmask... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.29 Dynamic Bonding Change Request (DBC-REQ) | A Dynamic Bonding Change Request message is transmitted by the CMTS in order to change upstream and/or downstream bonding parameters, or downstream multicast parameters. Only one DBC transaction per CM can be in the process at any time. The CMTS shall wait for any ongoing transaction for a particular CM to be finished ... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.30 Dynamic Bonding Change Response (DBC-RSP) | The CM shall transmit a Dynamic Bonding Change Response in response to a received Dynamic Bonding Change Request (DBC-REQ) message. The DBC-RSP message transmitted by a CM shall be formatted as shown in figure 6.51. Figure 6.51: Dynamic Bonding Change Response Message The Parameters of the DBC-RSP transmitted by a CM s... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.31 Dynamic Bonding Change Acknowledge (DBC-ACK) | The Dynamic Bonding Change Acknowledge shall be transmitted by a CMTS in response to a received Dynamic Bonding Change Response (DBC-RSP) message from a CM. The DBC-ACK message is formatted as shown in figure 6.52. Figure 6.52: Dynamic Bonding Change Acknowledge Message The parameters of a DBC-ACK message transmitted b... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.32 DOCSIS Path Verify Request (DPV-REQ) | The DOCSIS Path Verify (DPV) MAC Management Messages are used for measuring latency within the DOCSIS system. This message may be sent to either the DOCSIS multicast MAC address (refer to Annex A) or directly to a unicast MAC address of a CM. Figure 6.53: DPV-REQ MAC Message When transmitting a DPV-REQ message, the CMT... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.33 DOCSIS Path Verify Response (DPV-RSP) | The DPV MAC Management Messages are used for estimating latency and skew within the DOCSIS system. The CM shall comply with figure 6.54 for DPV Response messages. This message is sent by the CM to the unicast MAC address of the CMTS. Figure 6.54: DPV-RSP MAC Message The CM shall copy the values of all fields from the D... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.