hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.34 Status Report (CM-STATUS) | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.34.0 CM-STATUS Message Format | A CM shall generate the CM-STATUS message compliant with figure 6.55, including the Transaction ID and Event Type. The inclusion of these parameters in the beginning of the message body allows the CMTS to quickly filter events without parsing through the TLV structure. ETSI ETSI TS 103 311-3 V1.1.1 (2017-02) 178 Figure... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.34.1 CM-STATUS TLV Encodings | Table 6.61: CM-STATUS TLV Encodings Type Length Value 1 N Status Event This TLV is repeated for each error event that is being reported by the CM. 1.2 1 - 80 Event Description This is an optional vendor-specific text string containing details on the failure. The CM MAY include this TLV. 1.4 1 Downstream Channel ID This... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.35 CM Control Request (CM-CTRL-REQ) | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.35.0 CM-CTRL-REQ Message Format | The CM-CTRL-REQ command is used to enforce specific CM actions. It is a replacement to the DOCSIS 2.0 UP-DIS management message. The CMTS shall support the CM-CTRL-REQ message. The CM shall support the CM-CTRL- REQ message. Figure 6.56: CM-CTRL-REQ ETSI ETSI TS 103 311-3 V1.1.1 (2017-02) 180 A CMTS shall generate the C... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.35.1 CM-CTRL-REQ TLV Encodings | The CMTS shall use the TLV encodings described in table 6.62. The CM shall support each action defined by the TLV encodings described in table 6.62. The CM shall not act upon unknown TLVs in a CM-CTRL-REQ message. Table 6.62: CM-CTRL-REQ TLV Encodings Type Length Value 1 1 Upstream Channel RF Mute This field contains t... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.36 CM Control Response (CM-CTRL-RSP) | The CM-CTRL-RSP message is used to confirm receipt of a CM-CTRL-REQ message. The CM shall send a CM- CTRL-RSP message every time it receives a CM-CTRL-REQ message prior to performing the action described in the CM-CTRL-REQ message. The CMTS SHOULD consider a previously transmitted CM-CTRL-REQ message to be lost if the ... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.37 Energy Management Request (EM-REQ) | The Energy Management Request message is transmitted by the CM to request transition into or out of a low power mode of operation. Figure 6.58: Energy Management Request Message The parameters of the EM-REQ message include: • Transaction ID: Unique identifier for this transaction assigned by the CM. • Requested Power M... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.38 Energy Management Response (EM-RSP) | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.38.0 EM-RSP Message Format | The Energy Management Response message is sent by the CMTS in response to an Energy Management Request message from the CM. This message dictates if the CM is allowed to enter the selected power mode and, in some cases, defines the time duration before a follow-up EM-REQ message is allowed. The CMTS shall send an EM-RS... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.38.1 EM-RSP TLV-Encodings | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.38.1.1 Hold-Off Timer | This TLV specifies the amount of time to delay in seconds before transmitting an EM-REQ message again. Type Length Value 1 2 Minimum time (in seconds) before transmitting another EM-REQ message This parameter is only applicable if the EM-RSP message includes a Response Code of (1) "Reject Temporary". This value corresp... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.39 Status Report Acknowledge (CM-STATUS-ACK) | The Status Report Acknowledge (CM-STATUS-ACK) message is sent by the CMTS in response to a Status Report (CM-STATUS) message from the CM. The CM-STATUS-ACK message indicates that the CMTS has received the CM-STATUS message. Upon receiving a CM-STATUS-ACK message, the CM will cease retransmitting CM- STATUS messages wit... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.40 OFDM Channel Descriptor (OCD) | An OFDM Channel Descriptor allows the CMTS to communicate the parameters of the Downstream OFDM channel to cable modems. OCD describes the downstream direction only. OCD is used for parameters that are common for all profiles and are static assignments. Figure 6.61: OFDM Channel Descriptor ETSI ETSI TS 103 311-3 V1.1.1... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.41 Downstream Profile Descriptor (DPD) | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.41.0 DPD Message Format and TLV Encoding | A Downstream Profile Descriptor allows the CMTS to communicate the parameters of Downstream Profiles to cable modems. There is one DPD message per profile. The DPD can be changed dynamically. Figure 6.62: Downstream Profile Descriptor A CMTS shall generate the DPD message in the format shown in figure 6.62, including t... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.41.1 Subcarrier Assignment | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.41.1.0 Overview | The OFDM spectrum is illustrated in figure 6.63 and is described by two messages OCD and DPD. On the left is subcarrier(0) which is the first numbered subcarrier and is typically an excluded carrier. The outer 6.4 MHz past each end of the 192 MHz maximum spectrum is always excluded. There are fixed pilot tones describe... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.41.1.1 Default and Specific Values | The subcarrier assignment range/list TLV has a default mode. Subcarriers can be assigned a default value that can then subsequently be over-written with a specific value. For example, the subcarrier TLV could be issued once with all active data subcarriers set to a default modulation. The TLV could be issued again with... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.41.1.2 Subcarrier Assignment Vector | Subcarriers may also be assigned directly with a vector. A vector contains a starting subcarrier number and then a series of 4-bit modulation assignments. Note that the length field of the Subcarrier Assignment Vector is two bytes instead of one byte. When evaluating rules, assignments by the vector TLV are considered ... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.41.1.3 Example Subcarrier Assignment | The following is an example of how the OCD and DPD messages would be used to define an OFDM spectrum. OCD operation: 1) The location of the set of PLC subcarriers is designated. This is typically done with one range. 2) Excluded subcarriers are identified. This is typically done with one or more ranges. 3) Discrete con... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.42 OFDM Downstream Spectrum Request Message (ODS-REQ) | The ODS-REQ message is composed of a MAC Management Message header and an 8-bit downstream channel ID payload, as shown in figure 6.64. The CMTS shall use the ODS-REQ message format defined in figure 6.64. The ODS- REQ is a version 5 MAC Management Message. ETSI ETSI TS 103 311-3 V1.1.1 (2017-02) 190 Figure 6.64: OFDM ... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.43 OFDM Downstream Spectrum Response (ODS-RSP) | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.43.0 ODS-RSP Message Format | The ODS-RSP message is composed of a MAC Management Message header, a Downstream Channel ID, and TLV encoded information, as shown in figure 6.65. The CM shall use the ODS-RSP-MP message format defined in figure 6.65. The ODS-RSP is a version 5 MAC Management Message and uses the multi-part facility of the version 5 MM... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.43.1 ODS-RSP TLV Encodings | The CM shall use the ODS-RSP TLV encodings described in table 6.66. The CMTS shall support each of the TLV encodings described in table 6.66. Table 6.66: ODS-RSP-MP TLV Encodings Name Type (1 byte) Length (2 bytes) Value ODS Response Vector 1 N + 8 First Subcarrier-ID 1.1 2 ID of the subcarrier corresponding to the fir... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.44 OFDM Downstream Profile Test Request (OPT-REQ) | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.44.0 OPT-REQ Message Format | The OPT-REQ is used by the CMTS to cause a CM to test its ability to receive the specified downstream OFDM profile and then report the results. The OPT-REQ message is formatted as shown in figure 6.66. Figure 6.66: The OFDM Downstream Profile Test Request (OPT-REQ) Message Table 6.67: OPT-REQ Message Length/Value Lengt... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.44.1 OPT-REQ TLV Encodings | The CM shall support the OPT-REQ TLV encodings described in table 6.68. The CMTS shall support the OPT-REQ TLV encodings described in table 6.68. Table 6.68: OPT-REQ TLV encodings Name Type (1 byte) Length (1 byte) Value Requested Statistics 1 1 BITS encoding that commands the CM to include RxMER Margin Statistics in i... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.45 OFDM Downstream Profile Test Response (OPT-RSP) | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.45.0 OPT-RSP Message Format | The OPT-RSP is used by the CM first to acknowledge an OPT-REQ request and, if the request was to start a test, then another OPT-RSP will be sent to report the results. The normal transaction message flow is shown in figure 10.38. However, there might be reasons (operator intervention, fault management, etc.) why the CM... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.45.1 OPT-RSP TLV Encodings | The acknowledgement OPT-RSP message from the CM to the CMTS shall contain the same TLVs that the CM received in the OPT-REQ from the CMTS. See clause 6.4.44.1 for explanation of these TLVs. An OPT-RSP from the CM to the CMTS after the completion of a test cycle contains the following TLVs. Table 6.70: OPT-RSP TLV Encod... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.46 OFDM Downstream Profile Test Acknowledge (OPT-ACK) | The OPT-ACK message is sent from the CMTS to the CM to acknowledge the successful receipt of an OPT-RSP message with a Status of Complete or Incomplete that carries profile test metrics that were collected by the CM. Figure 6.68: The OFDM Profile Test Acknowledge (OPT-ACK) Message Table 6.71: OPT-ACK Message Length/Val... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.47 DOCSIS Time Protocol - Request (DTP-REQ) | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.47.0 DTP-REQ Message Format | The DTP Request message is used to initiate a DTP calibration sequence. The DTP-REQ message has the format shown in figure 6.69. The list of TLV values is provided in Annex C. Figure 6.69: DTP Request Message Transaction ID: A 16-bit unique identifier for this transaction assigned by the sending entity. ETSI ETSI TS 10... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.47.1 CMTS is DTP Master | If the CMTS is DTP Master and DTP is enabled, then the CMTS shall initiate a DTP-REQ at an interval specified by the DTP Calibration Interval in Annex B. If the CMTS issues a DTP-REQ to perform timing calculations, the CMTS shall include the following parameters as informational items: Clock ID, CMTS Timing Parameters,... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.47.2 CM is DTP Master | If the CM is DTP Master and DTP is enabled, then the CM shall initiate a DTP-REQ at an interval specified by the DTP Calibration Interval in Annex B. If the CM issues DTP-REQ, the CM shall include the following parameters as informational items: CM Timing Parameters and the True Ranging Offset. |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.48 DOCSIS Time Protocol - Response (DTP-RSP) | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.48.0 DTP-RSP Message Format | The DTP-RSP message responds to a DTP-REQ message with information for a timing calibration sequence. The DTP- RSP message has the format shown in figure 6.70. The list of TLV values is provided in Annex C. Figure 6.70: DTP Response Message Transaction ID: A 16-bit unique identifier for this transaction as contained in... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.48.1 CMTS is DTP Master | If the CM is a DTP Slave, DTP is enabled, and the CM receives a DTP-REQ message, then the CM shall respond with a DTP-RSP that contains the following parameters: CM Timing Parameters and the True Ranging Offset. If the CM receives a DTP-REQ message and cannot meet the requirements of DTP, the CM shall send a DTP RSP me... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.48.2 CM is DTP Master | If the CMTS is a slave, DTP is enabled, and the CMTS receives a DTP-REQ message, then the CMTS shall respond with a DTP-RSP that contains the following parameters: Clock ID, the CMTS Timing Parameters, the HFC Timing Parameters and the CMTS Override Timing Parameters. ETSI ETSI TS 103 311-3 V1.1.1 (2017-02) 198 |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.49 DOCSIS Time Protocol - Info (DTP-INFO) | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.49.0 DTP-INFO Message Format | The DTP-INFO message is sent in response to the DTP-RSP message with information from a timing calibration sequence. The DTP-INFO message has the format shown in figure 6.71. The list of TLV values is provided in Annex C. Figure 6.71: DTP-INFO Message Transaction ID: A 16-bit unique identifier for this transaction as c... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.49.1 CMTS is DTP Master | If the CMTS is a DTP Master, DTP is enabled, and the CMTS receives a DTP-RSP message, the CMTS shall respond with a DTP-INFO that contains the Timing Adjust parameter. |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.49.2 CM is DTP Master | If the CM is a DTP Master, DTP is enabled, and the CM receives a DTP-RSP message, the CM shall respond with a DTP-INFO that contains the following parameters as informational items: Timing Adjust and HFC Timing Parameters. |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.50 DOCSIS Time Protocol - Acknowledge (DTP-ACK) | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.50.0 DTP-ACK Message Format | The DTP-ACK message has the format shown in figure 6.72. The list of TLV values is provided in Annex C. Figure 6.72: DTP Acknowledge Message Transaction ID: A 16-bit unique identifier for this transaction as contained in the corresponding DTP-INFO message. |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.50.1 CMTS is DTP Master | If the CM is a DTP Slave, DTP is enabled, and the CM receives a DTP-INFO message, the CM shall respond with a DTP-ACK message. ETSI ETSI TS 103 311-3 V1.1.1 (2017-02) 199 |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.4.50.2 CM is DTP Master | If the CMTS is a DTP Slave, DTP is enabled, and the CMTS receives a DTP-INFO message, the CMTS shall respond with a DTP-ACK message. |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.5 PHY Link Channel | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.5.0 Overview | The PHY Link Channel (PLC) relative to the OFDM channel is shown in figure 6.73. Figure 6.73: OFDM Channel with PLC Prior to Interleaving The PHY Link Channel (PLC) is located in the downstream convergence layer. It is used for several tasks: • Timestamp • Energy management • Message channel for bringing new CMs on lin... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.5.1 PLC Structure | The structure of the PLC frame is shown in figure 6.74. Data Channel PHY Link Channel (PLC) 24 to 192 MHz Next CW Pointer Channel (NCP) ETSI ETSI TS 103 311-3 V1.1.1 (2017-02) 200 Figure 6.74: PLC Frame There is a preamble of 8 symbols at the beginning of a PLC Frame that consists of a field of fixed pilots. There is n... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.5.2 Timestamp Message Block | The timestamp MB contains the eight-byte DOCSIS timestamp. The TS MB shall be the first MB sent by the CMTS on the PLC after the preamble. The TS MB shall appear in every PLC frame sent by the CMTS. The timestamp references the end of the last symbol of the preamble at the start of the PLC frame that contains the times... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.5.3 Energy Management Message Block | The energy management message block (EM MB) contains messages that manage the DOCSIS Light Sleep (DLS) Mode. The EM MB contains one or more EM Messages (EMMs). Each EMM is associated with an EM group. An EMM consists of an EM-ID and a Sleep Time. The EM-ID identifies a CM or a group of CMs. The Sleep Time is assigned a... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.5.4 Message Channel Message Block | The message channel connects the CMTS MAC to the CM MAC. The contents of the message block contain properly formatted DOCSIS MAC Management Messages. ETSI ETSI TS 103 311-3 V1.1.1 (2017-02) 203 The CMTS shall transmit the Message Channel MB as the last MB in the PLC Frame unless other Message Blocks occupy the entire p... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.5.5 Trigger Message Block | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.5.5.0 Requirements for Trigger Message Block | The Trigger MB provides a mechanism for synchronizing an event at the CMTS and CM. The CMTS inserts a TR MB into the PLC and performs an action at a specific time aligned with the PLC frame. When the CM detects the TR MB, it performs an action at the same relative specified time aligned with the PLC frame received at t... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.5.5.1 Application of Trigger Message Block | This clause is informational. It describes how the TR MB message is used. In order for a CM to respond to the TR MB, the CM is first awakened if it is in sleep mode. The CM is configured to enable triggering. The CM is configured to belong to a Trigger Group. The CMTS inserts a single trigger message per measurement in... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 6.5.6 Future Use Message Blocks | The present document defines formats of four message block types for the PLC. Other types of Message Blocks may be defined in the future. In order to make the PLC protocol extensible, Cable Modems compliant with this version of specification need to be able to skip and ignore Message Blocks they do not support. For thi... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7 Media Access Control Protocol Operation | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.1 Timing and Synchronization | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.1.0 Overview | One of the major challenges in designing a MAC protocol for a cable network is compensating for the delays involved. These delays can be an order of magnitude larger than the transmission burst time in the upstream. To compensate for these delays, the cable modem needs to be able to time its transmissions precisely to ... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.1.1 Global Timing Reference | DOCSIS 3.0 and DOCSIS 3.1 CMTSs provide a timing reference on certain downstream channels. Downstream channels providing this timing reference are called "primary capable" and noted as such in the MAC Domain Descriptor MAC Management Message carried on that downstream channel. The physical layer provides the clock freq... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.1.2 CM Synchronization | The cable modem achieves MAC synchronization once it has received at least two timing synchronization messages, received one UCD message, has locked to the downstream symbol clock, and has verified that its clock tolerances are within specified limits (as defined in [12]). The cable modem shall lock to the downstream s... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.1.3 Ranging | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.1.3.0 Purpose of Ranging | Ranging is the process of acquiring the correct timing offset such that the cable modem's transmissions are aligned to the correct minislot boundary. The timing delays through the PHY layer of the CM and CMTS shall be relatively constant with the exception of the timing offsets specified in [12], related to modulation ... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.1.3.1 Broadcast Initial Ranging | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.1.3.1.0 General | First, a cable modem shall synchronize to the downstream as described in clause 7.1.2, and learn the upstream channel characteristics through the Upstream Channel Descriptor MAC management message. At this point, the cable modem shall scan the Bandwidth Allocation MAP message to find a Broadcast Initial Maintenance Reg... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.1.3.1.1 Broadcast Initial Ranging on SC-QAM Upstreams | For TDMA and S-CDMA upstream channels, the cable modem shall transmit either a Bonded Initial Ranging Request message (B-INIT-RNG-REQ), or a Ranging Request message (RNG-REQ) in a Broadcast Initial Maintenance region. The CM shall transmit a B-INIT-RNG-REQ if the CM is ranging for the first time after power-up or reini... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.1.3.1.2 Broadcast Initial Ranging on OFDMA Upstreams | For OFDMA upstream channels, the Broadcast Initial Maintenance region occupies a much larger percentage of the available spectrum. In order to reduce the size of this region, the burst sent in Broadcast Initial Maintenance regions on OFDMA upstream channels is a specialized shortened message called the OFDMA Initial Ra... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.1.3.2 Unicast Initial Ranging | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.1.3.2.1 Unicast Initial Ranging on SC-QAM Upstreams | After receiving a Ranging Response message after transmitting in a Broadcast Initial Maintenance region on an SC- QAM upstream, the cable modem shall now wait for an individual Station Maintenance or Unicast Initial Maintenance region assigned to its temporary SID (or previous primary SID if ranging as a result of a UC... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.1.3.2.2 Unicast Initial Ranging on OFDMA Upstreams | After receiving a Ranging Response message after transmitting in a Broadcast Initial Maintenance region on an OFDMA upstream, the cable modem shall now wait for an individual Station Maintenance region assigned to its temporary SID (or previous primary SID if ranging as a result of a UCC, DCC, or UCD change, or Ranging... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.1.4 Timing Units and Relationships | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.1.4.0 Timing Units | The SYNC message conveys a time reference with a resolution of 6,25/64 microseconds (10,24 MHz) to allow the CM to track the CMTS clock with a small phase offset. Since this timing reference is decoupled from particular upstream channel characteristics, a single SYNC time reference may be used for all upstream channels... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.1.4.1 TDMA Timing Units and Relationships | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.1.4.1.1 Minislot Capacity | On TDMA channels, the size of the minislot, expressed as a multiple of the SYNC time reference, is carried in the Upstream Channel Descriptor. The example in table 7.1 relates minislots to the SYNC time ticks (assuming QPSK modulation). ETSI ETSI TS 103 311-3 V1.1.1 (2017-02) 210 Table 7.1: Example Relating Minislots t... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.1.4.1.2 Minislot Numbering | The MAP counts minislots in a 32-bit counter that normally counts to (2(26-M) - 1) and then wraps back to zero. The CMTS shall match the least-significant bits (i.e. bit 0 to bit 25-M) of the minislot counter to the most-significant bits (i.e. bit 6+M to bit 31) of the SYNC timestamp counter. That is, minislot N begins... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.1.4.2 S-CDMA Timing Units and Relationships | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.1.4.2.1 Minislot Capacity | On S-CDMA channels, the size of the minislot is dependent on the modulation rate, the codes per minislot, and the spreading intervals per frame, which are all carried in the Upstream Channel Descriptor. The timing units and relationships for S-CDMA are covered in detail in [12]. An example of the timing relationships (... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.1.4.2.2 Minislot Numbering | Minislot numbering in S-CDMA mode is described in detail in [12]. ETSI ETSI TS 103 311-3 V1.1.1 (2017-02) 211 |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.1.4.3 OFDMA Timing Units and Relationships | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.1.4.3.1 Minislot Capacity | On OFDMA channels, the size of the minislot in total symbols is fixed for the channel. The size is specified by the number of symbols in a frame combined with the number of subcarriers per minislot. The bit loading and pilot pattern are variable per minislot based on the minislot location in the frame and the burst pro... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.1.4.3.2 Minislot Numbering | Minislot numbering in OFDMA mode is described in detail in [12]. |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.1.5 Extended Timestamp | DOCSIS 3.1 introduces an eight-byte extended timestamp. The value of the timestamp is referenced to the end of the PLC preamble. The DOCSIS extended timestamp has two additional features when compared to the original DOCSIS timestamp. • The extended timestamp is now an absolute timestamp rather than a relative timestam... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.2 Upstream Data Transmission | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.2.1 Upstream Bandwidth Allocation | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.2.1.0 Overview | The CMTS allocates bandwidth for one or more upstream channels. Bandwidth allocated to one CM may be allocated across multiple channels upon which the CM can transmit. An upstream channel is modelled as a stream of minislots. The CMTS shall generate the time reference for identifying these slots. The CMTS shall also co... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.2.1.1 The Allocation MAP MAC Management Message | The allocation MAP is a varying-length MAC Management Message that is transmitted by the CMTS to define transmission opportunities on the upstream channel. It includes a fixed-length header followed by a variable number of Information Elements (IEs) or Probe Information Elements (P-IEs) in the format shown in clause 6.... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.2.1.2 Information Elements | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.2.1.2.0 Types of Information Elements | Each IE consists of a 14-bit Service ID (SID), a 4-bit type code (IUC), and a 14-bit starting offset as defined in clause 6.4.4. Since all CMs shall scan all IEs, it is critical that IEs be short and relatively fixed format. IEs within the MAP are strictly ordered by starting offset. For most purposes, the duration des... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.2.1.2.1 The Request IE | The Request IE provides an upstream interval in which requests may be made for bandwidth for upstream data transmission. The character of this IE changes depending on the class of Service ID. If broadcast, this is an invitation for CMs to contend for requests. clause 7.2.2 describes which contention transmit opportunit... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.2.1.2.2 The Request_2 IE | The Request_2 IE provides a second type of upstream interval in which requests for bandwidth may be transmitted. The Request_2 IE replaces the Request/Data IE used in previous generations of DOCSIS. This region is primarily used in support of the Maximum Scheduled Codes feature on Type 3S and Type 4S upstreams as descr... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.2.1.2.3 The Initial Maintenance IE | The Initial Maintenance IE, when used with the Broadcast SID, provides an interval in which new stations may join the network. A long interval, equivalent to the maximum round-trip propagation delay plus the transmission time of a Ranging Request (RNG-REQ) message (see clause 7.1.3), shall be provided by the CMTS to al... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.2.1.2.4 The Station Maintenance IE | For non-OFDMA upstream channels, the Station Maintenance IE provides an interval in which stations are expected to perform some aspect of routine network maintenance such as ranging. The CMTS sends a unicast station maintenance IE to CMs periodically in order to ensure CM upstream transmit signal fidelity. Parameters s... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.2.1.2.5 Short and Long Data Grant IEs (also known as Data Profiles IUC5 and IUC6) | The Short and Long Data Grant IEs provide an opportunity for a CM to transmit one or more upstream PDUs. These IEs are issued either in response to a request from a station, or because of an administrative policy providing some amount of bandwidth to a particular station (see class-of-service discussion below). These I... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.2.1.2.6 Data Acknowledge IE | The Data Acknowledge IE is deprecated in this version of the DOCSIS specification. |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.2.1.2.7 Expansion IE | The Expansion IE provides for extensibility, if more than 16 IUCs or 32 bits are needed for future IEs. ETSI ETSI TS 103 311-3 V1.1.1 (2017-02) 216 |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.2.1.2.8 Null IE | A Null IE terminates all actual allocations in the IE list. It is used to infer a length for the last interval. All Data Grant Pending IEs (Data Grants with an inferred length of 0) follow the Null IE. 7.2.1.2.9 Advanced PHY Short and Long Data Grant IEs (also known as Data Profiles IUC9 and IUC10) These IEs are the Ad... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.2.1.2.10 Advanced PHY Unsolicited Grant IE (also known as Data Profile IUC11) | This IE can be used by the CMTS to make unsolicited grants of bandwidth to DOCSIS 2.0 CMs. If a significant portion of the traffic for an upstream is going to consist of unsolicited grants of a particular size, this IE provides a way for the CMTS to provide a set of physical layer parameters (such as code word length a... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.2.1.2.11 Data Profiles IUC12 and IUC13 IEs | These IEs are only applicable to Type 5 Upstream Channels. The CMTS uses Data Profiles IUC12 and IUC13 IEs to grant bandwidth to CMs assigned to IUC12 or IUC13 respectively. Operation on a Type 5 upstream channel uses Multiple Transmit Channel Mode. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.