hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.2.1.2.12 Probe IE | This IE is used by the CMTS to assign probe opportunities in probe frames on OFDMA channels. This IE is always unicast and can only appear in a P-MAP. The CM transmits a probe signal (see [12]) in the allocated region. |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.2.1.3 Requesting with Multiple Transmit Channel Mode Disabled | This clause applies to bandwidth requests when Multiple Transmit Channel Mode is disabled, such as when a 3.0 CM is operating on a Pre-3.0 DOCSIS CMTS, or a Pre-3.0 DOCSIS CM that does not support Multiple Transmit Channel Mode is operating on a DOCSIS 3.0 or 3.1 CMTS. Requests refer to the mechanism that a CM uses to ... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.2.1.4 Requesting with Multiple Transmit Channel Mode Enabled | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.2.1.4.0 Types of Request Mechanisms with MTC Enabled | This clause applies to bandwidth requests when Multiple Transmit Channel Mode is enabled. As required in clause 6.2.4.3, when the CM is operating in Multiple Transmit Channel Mode, it does not use the Request Frame (bandwidth request in minislots), but rather it uses the Queue-Depth Based Request Frame (bandwidth reque... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.2.1.4.1 Request Mechanisms for Segment Header OFF Service Flows | As described in clause 8.3.2.2, Segment Header Off operation is only defined for service flows that have a scheduling type of UGS or UGS-AD, and as indicated in clause 7.2.3, UGS and UGS-AD service flows are required to have an R/T Policy which prohibits the use of contention request opportunities, request_2 opportunit... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.2.1.4.2 Request Mechanisms for Segment Header ON Service Flows | 7.2.1.4.2.0 Types of Request Mechanisms for Segment Header ON Service Flows For a service flow configured for Segment Header ON operation, the CM can send a Request as a stand-alone Queue- depth Based Request Frame transmission (refer to clause 6.2.4.5) or (unless disabled by the R/T Policy) as a piggyback request in a... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.2.1.5 Information Element Feature Usage Summary | Table 7.4 summarizes what types of frames the CM can transmit using each of the MAP IE types that represent transmit opportunities in non-probe frames. The CM shall support the requirements as indicated in table 7.4 and table 7.5, following the definitions below: • A "shall" entry in the table means that, if appropriat... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.2.1.6 Map Transmission and Timing | The allocation MAP shall be transmitted by the CMTS in time to propagate across the physical cable and be received and handled by the receiving CMs. As such, it MAY be transmitted by the CMTS considerably earlier than its effective time. The components of the delay are: • Worst-case round-trip propagation delay - can b... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.2.1.7 Protocol Example | This clause illustrates the interchange between the CM and the CMTS when the CM has data to transmit (see figure 7.3). Although the diagram and description are focused on a single upstream channel, DOCSIS 3.1 operation allows a request to be made on any of multiple upstream channels and the subsequent grants from the C... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.2.1.8 MAP Generation Examples - Two Logical Upstreams | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.2.1.8.1 S-CDMA and TDMA Logical Channel Combination | This clause illustrates the timing requirements for scheduling an S-CDMA and a TDMA logical channel on the same physical channel. For simplicity it is assumed that: • The duration of the S-CDMA frames is an integral multiple of the duration of the TDMA minislots; • Both TDMA and S-CDMA maps begin and end on frame bound... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.2.1.8.2 OFDMA and TDMA Logical Channel Combination | This clause illustrates the timing requirements for scheduling an OFDMA and a TDMA logical channel sharing the same physical spectrum. For simplicity it is assumed that: • The duration of the OFDMA frames is an integral multiple of the duration of the TDMA minislots; • Both TDMA and OFDMA maps begin and end on frame bo... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.2.1.9 MAP Generation for Initial Ranging Regions on OFDMA Upstream Channels | The Initial Maintenance Region on an OFDMA upstream can be several minislots in height and will be some number of OFDMA frames in length. The actual burst transmitted in the region will be much shorter than the allocated region and will follow the parameters of the Initial Ranging on OFDMA channels outlined in the PHY ... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.2.2 Upstream Transmission and Contention Resolution | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.2.2.1 Contention Resolution Overview Mechanisms | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.2.2.1.0 Overview | The CMTS controls assignments on the upstream channel through the MAP and determines which minislots are subject to collisions. The CMTS MAY provide broadcast/multicast request opportunities, which might be subject to collision. This clause provides an overview of upstream transmission and contention resolution. For si... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.2.2.1.1 Contention Resolution with Multiple Transmit Channel Mode Disabled | Every time a CM wants to transmit in a contention region, it shall enter the contention resolution process by setting its internal backoff window equal to the Data Backoff Start defined in the MAP currently in effect. ETSI ETSI TS 103 311-3 V1.1.1 (2017-02) 229 NOTE 1: The MAP currently in effect is the MAP whose alloc... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.2.2.1.2 Contention Resolution with Multiple Transmit Channel Mode Enabled | Contention bandwidth requesting in Multiple Transmit Channel Mode is similar to that described above. However, for Multiple Transmit Channel Mode, whenever a service flow is associated with more than one upstream channel, the CM counts the request opportunities in time-order across channels associated with the service ... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.2.2.2 Transmit Opportunities | A Transmit Opportunity is defined as any minislot in which a CM may be allowed to start a transmission. Transmit Opportunities typically apply to contention opportunities and are used to calculate the proper amount to defer in the contention resolution process. The number of Transmit Opportunities associated with a par... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.2.2.3 CM Bandwidth Utilization | The following rules govern the response a CM makes when processing MAPs: NOTE: These standard behaviours can be overridden by the CM's Request/Transmission Policy (see clause C.2.2.8.3). 1) When a CM has data to send, it shall first use any available Data Grants assigned to the Service Flow or Class of Service if it is... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.2.3 Upstream Service Flow Scheduling Services | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.2.3.0 Overview | Clauses 7.2.3.1 through 7.2.3.8 define the basic upstream Service Flow scheduling services and list the QoS parameters associated with each service. A detailed description of each QoS parameter is provided in Annex C. This portion of the present document also discusses how these basic services and QoS parameters can be... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.2.3.1 Unsolicited Grant Service | The Unsolicited Grant Service (UGS) is designed to support real-time service flows that generate fixed size data packets on a periodic basis, such as Voice over IP. UGS offers fixed size grants (in bytes) on a real-time periodic basis, which eliminate the overhead and latency of CM requests and assure that grants will ... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.2.3.2 Real-Time Polling Service | The Real-Time Polling Service (rtPS) is designed to support real-time service flows that generate variable size data packets on a periodic basis, such as MPEG video. The service offers real-time, periodic, unicast request opportunities, which meet the flow's real-time needs and allow the CM to specify the size of the d... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.2.3.3 Unsolicited Grant Service with Activity Detection | The Unsolicited Grant Service with Activity Detection (UGS-AD) is designed to support UGS flows that may become inactive for substantial portions of time (i.e. tens of milliseconds or more), such as Voice over IP with silence suppression. The service provides Unsolicited Grants when the flow is active and unicast polls... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.2.3.4 Non-Real-Time Polling Service | The Non-Real-Time Polling Service (nrtPS) is designed to support non real-time service flows that require variable size data grants on a regular basis, such as high bandwidth FTP. The service offers unicast polls on a regular basis which assures that the flow receives request opportunities even during network congestio... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.2.3.5 Best Effort Service | The intent of the Best Effort service is to provide efficient service to best effort traffic. In order for this service to work correctly, the Request/Transmission Policy setting should be such that the CM is allowed to use contention request opportunities. The CMTS shall reject a Best Effort Service Flow for which the... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.2.3.6 Other Services | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.2.3.6.1 Committed Information Rate (CIR) | A Committed Information Rate (CIR) service can be defined a number of different ways. For example, it could be configured by using a Best Effort service with a Minimum Reserved Traffic Rate or an nrtPS with a Minimum Reserved Traffic Rate. |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.2.3.7 Parameter Applicability for Upstream Service Scheduling | Table 7.7 summarizes the relationship between the scheduling services and key QoS parameters. A detailed description of each QoS parameter is provided in clause C.2. Table 7.7: Parameter Applicability for Upstream Service Scheduling Service Flow Parameter Best Effort Non-Real- Time Polling Real-Time Polling Unsolicited... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.2.3.8 CM Transmit Behaviour | In order for these services to function correctly, all that is required of the CM in regards to its transmit behaviour for a service flow, is for it to follow the rules specified in clause 7.2.2, and the Request/Transmission Policy specified for the service flow. |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.2.4 Continuous Concatenation and Fragmentation | CMs in Multiple Transmit Channel Mode generally use Continuous Concatenation and Fragmentation (CCF) to fill data grants. CCF treats each service flow at the CM as a continuous stream of data regardless of the channel on which that data is transmitted. Each service flow is a different stream. When in Multiple Transmit ... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.2.5 Pre-3.0 DOCSIS Concatenation and Fragmentation | As required of CMTSs for backward compatibility described in Annex G, Pre-3.0 DOCSIS Concatenation and Fragmentation requirements are specified in [8], clause 7.2.5, "Pre-3.0 DOCSIS Concatenation and Fragmentation." Pre-3.0 DOCSIS Concatenation and Fragmentation support is not required of the CM. 7.3 Upstream - Downstr... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.3.1.0 Primary Downstream Channel | During initialization, the CM shall select a single downstream channel with which to attempt initial ranging. This downstream channel is known as the CM's candidate Primary Downstream Channel. Over the course of normal operation, the CM's Primary Downstream Channel may be changed several times by the CMTS. For pre-3.1 ... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.3.1.1 Backup Primary Downstream Channels | When registering a DOCSIS 3.1 CM, the CMTS will assign one primary capable downstream channel as the CM's primary downstream and might assign one or more other primary-capable downstream channels as backup primary channel(s) in the Receive Channel Configuration (RCC). When this happens, the CM would attempt to utilize ... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.3.2 MAP and UCD Messages | UCD and MAP messages for a given upstream channel may be sent on any downstream channel in the MAC Domain, regardless of whether or not the channel is a Primary-Capable Downstream Channel. UCD and MAP messages for a given upstream channel may be sent on more than one downstream channel. A CMTS shall transmit MAP and UC... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.3.3 Multiple MAC Domains | The CMTS might operate in a configuration in which downstream channels are shared across multiple MAC domains. If a downstream channel is shared between multiple MAC domains, the CMTS shall ensure that the downstream channel is primary-capable in only one of the MAC domains. On a given downstream channel, the CMTS shal... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.4 DSID Definition | A DSID is a 20-bit value contained in a Downstream Service Extended Header (DS EHDR) on a frame that identifies a stream of packets to a set of CMs (see clause 6.2.6.6). The CM uses the DSID for purposes of downstream resequencing, filtering, and forwarding. A DSID value communicated to the CM by the CMTS is said to be... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.5 Quality of Service | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.5.1 Concepts | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.5.1.1 Service Flows | A Service Flow is a MAC-layer transport service that provides unidirectional transport of packets either to upstream packets transmitted by the CM or to downstream packets transmitted by the CMTS. NOTE 1: A Service Flow, as defined here, has no direct relationship to the concept of a "flow" as defined by the IETF's Int... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.5.1.2 Classifiers | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.5.1.2.0 General | A Classifier is a set of matching criteria applied to each packet entering the cable network which consists of some packet matching criteria (destination IP address, for example) and a classifier priority. A QoS Classifier additionally consists of a reference to a service flow. If a packet matches the specified packet ... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.5.1.2.1 Upstream and Downstream QoS Classifiers | Several QoS Classifiers may all refer to the same Service Flow. The classifier priority is used for ordering the application of Classifiers to packets. Explicit ordering is necessary because the patterns used by Classifiers may overlap. The priority need not be unique, but care needs to be taken within a classifier pri... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.5.1.2.2 Upstream Drop Classifiers | DOCSIS 3.0 expands the concept of classifiers to encompass the filtering of upstream traffic. An Upstream Drop Classifier is a Classifier created by the CM to filter upstream traffic. If a packet matches the specified packet matching criteria of an Upstream Drop Classifier, it is then dropped. Unlike QoS Classifiers, U... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.5.2 Object Model | The major objects of the architecture are represented by named rectangles in figure 7.12. Each object has a number of attributes; the attribute names which uniquely identify the object are underlined. Optional attributes are denoted with brackets. The relationship between the number of objects is marked at each end of ... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.5.3 Service Classes | The QoS attributes of a Service Flow may be specified in two ways: either by explicitly defining all attributes, or implicitly by specifying a Service Class Name. A Service Class Name is a string which the CMTS associates with a QoS Parameter Set. It is described further below. The Service Class serves the following pu... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.5.4 Authorization | Every change to the Service Flow QoS Parameters shall be approved by an authorization module at the CMTS. This includes every REG-REQ REG-REQ-MP, or DSA-REQ message to create a new Service Flow, and every DSC-REQ message to change a QoS Parameter Set of an existing Service Flow. Such changes include requesting an admis... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.5.5 States of Service Flows | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.5.5.0 General | It is useful to think about four states of Service Flows. This clause describes these four states of Service Flows in more detail. However, it is important to note that there are more than just these basic states. |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.5.5.1 Deferred Service Flows | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.5.5.1.0 States of Deferred Service Flows | A service flow may be authorized in an inactive state for subsequent admittance and activation. There are two states of deferred flows - Provisioned and Authorized. As a result of external action beyond the scope of the present document (e.g. ETSI TS 101 909-9 [i.16]), the CM MAY choose to authorize and/or activate a d... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.5.5.1.1 Provisioned Service Flows | A Service Flow may be created in the Provisioned state but not immediately activated. That is, the description of any such service flow in the TFTP configuration file contains an attribute which provisions but defers activation and admission. During Registration, the CMTS assigns a Service Flow ID for such a service fl... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.5.5.1.2 Authorized Service Flows | A Service Flow may be created in the Authorized state but not immediately activated. That is, the description of any such service flow is passed to the CMTS which authorizes but defers activation and admission (refer to clause C.2.2.5.5). The CMTS internally shall assign a Service Flow ID for such a service flow but do... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.5.5.2 Admitted Service Flows | This protocol supports a two-phase activation model which is often utilized in telephony applications. In the two-phase activation model, the resources for a "call" are first "admitted," and then once the end-to-end negotiation is completed (e.g. called party's gateway generates an "off-hook" event) the resources are "... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.5.5.3 Active Service Flows | A Service Flow that has a non-NULL set of ActiveQoSParameters is said to be in the Active state. It is requesting and being granted bandwidth for transport of data packets. A Service Flow in the Admitted state may be made active by providing an ActiveQoSParameterSet, signalling the resources actually desired at the cur... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.5.6 Service Flows and Classifiers | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.5.6.0 Basic Model of Classification | The basic model is that the Classifiers associate packets into exactly one Service Flow. The Service Flow Encodings provide the QoS Parameters for treatment of those packets on the RF interface. These encodings are described in clause C.2. In the upstream direction, the CM shall classify upstream packets to Active Serv... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.5.6.1 Policy-Based Classification and Service Classes | As noted in is a variety of ways in which packets may be enqueued for transmission at the MAC Service Interface. At one extreme are embedded applications that are tightly bound to a particular Payload Header Suppression Rule and which forego more general classification by the MAC. At the other extreme are general trans... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.5.7 General Operation | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.5.7.0 Service Flow Rejection | The CMTS shall reject a Service Flow if the CMTS does not have the capability to support the Quality of Service parameters for the flow. For example, if the CMTS only supports certain Grant Intervals for Unsolicited Grant Service, it is required to reject a Service Flow request for a Grant Interval other than a support... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.5.7.1 Static Operation | Static configuration of QoS Classifiers, Upstream Drop Classifiers, and Service Flows uses the Registration process. A provisioning server provides the CM with configuration information. The CM passes this information to the CMTS in a Registration Request. The CMTS adds information and replies with a Registration Respo... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.5.7.2 Dynamic Service Flow Creation - CM Initiated | Service Flows may be created by the Dynamic Service Addition process, as well as through the Registration process outlined above. The Dynamic Service Addition may be initiated by either the CM or the CMTS, and may create one upstream and/or one downstream dynamic Service Flow(s). A three-way handshake is used to create... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.5.7.3 Dynamic Service Flow Creation - CMTS Initiated | A DSA-Request from a CMTS contains Service Flow Identifier(s) for one upstream and/or one downstream Service Flow, possibly one or more SID Cluster Encodings, set(s) of active or admitted QoS Parameters, and any required Classifier(s). A CMTS-initiated DSA-Request does not contain Upstream Drop Classifiers. The protoco... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.5.7.4 Dynamic Service Flow Modification and Deletion | In addition to the methods presented above for creating service flows, protocols are defined for modifying and deleting service flows (refer to clauses 11.2.3 and 11.2.4). Both provisioned and dynamically created Service flows are modified with the DSC message, which can change the Admitted and Active QoS Parameter set... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.5.8 QoS Support for Joined IP Multicast Traffic | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.5.8.0 Overview | 7.5. |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 8.0 Overview | This clause describes a standard configuration and implementation of QoS for downstream IP multicast traffic that is joined dynamically by a multicast host or statically joined via CMTS configuration. The mechanism for providing QoS to a group of CMs is similar to the mechanism for providing it to an individual CM: the... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.5.8.1 IP Multicast QoS Operation | An object model diagram that describes multicast QoS operation is depicted in figure 7.16. ETSI ETSI TS 103 311-3 V1.1.1 (2017-02) 255 Figure 7.16: IP Multicast QoS Object Model Diagram The operational model of the CMTS as described in Annex N is that a CMTS Forwarder submits a MAC_DATA_GROUP.request primitive to a MAC... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.5.8.2 Group Configuration and Group QoS Configuration Tables | For IP Multicast QoS, a cable operator controls the creation of GCRs and GSFs by configuring entries in Group Configuration (GC) and Group QoS Configuration (GQC) tables. These tables only configure the QoS for IP Multicast sessions; they do not control how CMTS replicates IP Multicast Sessions on DCSs. Replication of ... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.5.8.3 Instantiating Group Classifier Rules and Group Service Flows | The CMTS shall take the following steps to instantiate GCRs and GSFs for controlling the QoS of dynamically or statically joined IP Multicast sessions: 1) When a client within a MAC Domain joins a multicast session, the CMTS determines to which Downstream Channel Set (DCS) it will replicate the packets of that session ... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.5.8.4 Default Group Service Flows | A CMTS shall identify one of its Service Classes as the Default Group Service Class. When the CMTS replicates a multicast packet to a Downstream Channel Set on which the packet matches no Group Classifier Rule, the CMTS shall transmit the packet on a Group Service Flow instantiated using the Default Group Service Class... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.5.8.5 Service Class QoS Parameter Changes | The CMTS MAY dynamically change the QoS parameters of all Group Service Flows derived from a Service Class when the QoS parameters of the Service Class are changed. ETSI ETSI TS 103 311-3 V1.1.1 (2017-02) 265 |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.5.8.6 Group QoS Configuration Changes | Because the GC and GQC tables are the only mechanism for controlling the instantiation of GCRs and GSFs, when a GC or GQC entry is added, modified or deleted, the CMTS shall dynamically implement changes to the GCR(s) and GSF(s) instantiated from that GC or GQC entry, as follows: • For each replication of an IP multica... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.5.9 Other Multicast and Broadcast Traffic | The Group QoS Configuration Table specifies how QoS is provided to downstream multicast traffic only for joined IP Multicast sessions. The QoS provided to all other downstream broadcast and multicast traffic is not configured with the GQC Table. Examples of traffic which are not configured with a GQC Table include: • L... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.5.10 Hierarchical QoS | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.5.10.0 General | DOCSIS 3.1 defines the framework for hierarchical QoS (HQoS) which enables operators to define QoS policies on an aggregation of Service Flows. Hierarchical QoS is defined as a strict tree structure where the bonding group's or channel's capacity is typically the root (or "parent") node. The word "strict" means that fo... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.5.10.1 CMTS and CM Roles | HQoS is defined as a feature which requires implementation only on the CMTS. The CMTS manages HQoS including Service Flow to ASF mapping as well as Service Flow to IATC mapping. All aggregate QoS policy enforcement functions, including the real time traffic scheduling and queuing are performed only by the CMTS. CMTS pr... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.5.10.2 Aggregate Service Flow | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.5.10.2.0 Concept of Aggregate Service Flow | An Aggregate Service Flow (ASF) is a grouping of one or more Service Flows mapped to a single CM. The DOCSIS Network supports a hierarchical, two-layered subscriber QoS model through the concept of an ASF, which is defined as a MAC-layer transport service that provides unidirectional transport of frames, transmitted in... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.5.10.2.1 Relationship between Service Flow and ASF | A Service Flow may be associated with zero or one ASF instance. Any SF not associated with ASF needs to be directly mapped to a channel or a bonding group. An ASF may group SFs with different QoS parameters, for example maximum sustained rate or traffic priority. Dynamically provisioned service flows, for example those... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.5.10.2.2 ASF QoS Profile | ASFs serve as an implementation tool for service layer agreements with two levels of QoS parameters. ASFs provide the outer QoS envelope, while Service Flows define QoS parameters for more granular, individual services or applications. Each ASF instance is associated to ASF QoS Profile (AQP). The operators provision AQ... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.5.10.3 Interface Aggregate Traffic Class | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.5.10.3.0 Concept of Interface Aggregate Traffic Class | An Interface Aggregate Traffic Class (IATC) represents a grouping of one or more Service Flows mapped to a single channel or a bonding group. The IATCs enable the operators to virtually divide the bandwidth of service groups, bonding groups or channels between distinct services or users. Unlike ASFs IATCs group service... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.5.10.3.1 IATC Profiles | IATCs are provisioned solely in the CMTS configuration through IATC Profiles. An IATC Profile configuration includes parameters as listed in table 7.10. Table 7.10: IATC Profile parameters Attributes Description IATC Profile Name A string that uniquely identifies the IATC profile. Aggregate QoS Set A set of parameters ... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.5.10.3.2 Mapping of Service Flows to IATCs | In the absence of H-QoS settings the CMTS maps Service Flows to bonding groups or individual channels. With HQoS, the SF mapping process needs to include one additional step: a decision whether to assign a SF to an IATC and which IATC to select. Operators will be able to control SF to IATC association via several match... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.6 Packet Queuing | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.6.1 Downstream Traffic Priority | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.6.1.0 General | The downstream Traffic Priority parameter is an explicit tag that will allow the CM to support multiple prioritized egress queues at its CMCI port. DOCSIS 3.0 defines a Downstream Service Extended Header (DS EHDR) element (refer to clause 6.2.6.6) in which the first three bits of the EH_VALUE indicate the Traffic Prior... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.6.1.1 Traffic Priority Ordering and Mapping to CM Output Queues | Table 7.11 indicates the CM output queue to which a packet shall be assigned based on the number of CM output queues supported by the CM implementation and the Traffic Priority indicated in the DS EHDR of the packet. The CM output queues are numbered in order of increasing priority with 0 as the lowest priority and 7 a... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.6.2 Active Queue Management | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.6.2.0 Overview | Active Queue Management (AQM) schemes attempt to maintain low queue occupancy while supporting the ability to absorb a momentary traffic burst by communicating early to transport layers (typically by means of packet drops or Explicit Congestion Notification) when they start to force higher queue occupancy. See RFC 2309... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.6.2.1 CM AQM Requirements | AQM operation on the CM is independent of the DOCSIS version of the CMTS and AQM algorithm operation of the CMTS. The CM shall always enable the AQM algorithm defined below on each Best Effort and Non-Real-Time Polling Service Upstream Service Flow queue, unless provisioned otherwise by TLV as defined in clause C.2.2.7... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.6.2.2 CMTS AQM Requirements | The CMTS shall support a default AQM scheme defined by the vendor. The CMTS SHOULD support a published AQM algorithm as the default AQM. An AQM algorithm description that is publicly accessible allows for wider evaluation by the industry and networking community. The CMTS default AQM scheme shall bound the median downs... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.7 Data Link Encryption Support | |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.7.0 General | The procedures to support data link encryption are defined in ETSI EN 302 878-5 [14]. The interaction between the MAC layer and the security system is limited to the items defined below. |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.7.1 MAC Messages | MAC Management Messages shall not be encrypted, except for certain cases where such a frame is included in a Pre- 3.0 DOCSIS fragmented concatenated burst on the upstream (refer to clause 7.7.3). For Multiple Transmit Channel Mode operation, MAC Management Messages shall not be encrypted. |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.7.2 Framing | When encryption is applied to a data PDU, the CM shall include the Privacy EH element ETSI EN 302 878-5 [14] as the first EH element of the Extended Header field (EHDR). When encryption is applied to a data PDU, the CMTS shall include the Privacy EH element [14] as the first EH element of the Extended Header field (EHD... |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.7.3 Multiple Transmit Channel Mode Operation and Packet Encryption | For Multiple Transmit Channel Mode Operation, when enabled for a service flow, encryption shall be performed on data PDUs prior to Continuous Concatenation and Fragmentation at the CM. At the CMTS, packets shall be reassembled prior to any decryption. |
977e8a176c53922fd5283270c744fd61 | 103 311-3 | 7.8 Downstream Profiles |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.