name: CPS
full_form: Common Part Sublayer
context: Figure 7 shows the idea of Path type capability. The capability to select a succeeding AAL type 2 path or underlying VC according to the requested path type is deployed in AAL type 2 endpoints and AAL type 2 switching nodes. An AAL type 2 connection is established within a series of AAL type 2 paths align with the requested path type. Absence of the new parameter âPath typeâ in the ESTABLISH.request primitive at an originating AAL type 2 endpoint or in the Establish Request message at an AAL type 2 switching node indicates that the network default stringent AAL type 2 path expected in Q.2630.1[5] is requested. In case the new parameter âPath typeâ is present, it indicates the requested QoS for the AAL type 2 path. The path type parameter contains an ATM QoS code point The range of the codepoint is 0 â 255. The code points 1, 2, and 5 indicate stringent, tolerant, and stringent bi-level respectively. The code points 0, 3, 4, and 6 - 127 are reserved for assignment by ITU-T. The code
description: The Common Part Sublayer (CPS) is a protocol component responsible for multiplexing and de-multiplexing cells and sub-cells on an ATM link. It plays a crucial role in managing packet queuing delay in the transmitter buffer, which affects the Packet Transfer Delay (PTD) and Packet Delay Variation (PDV). The CPS operates based on various traffic assumptions and network configurations, including individual source bit-rate, negotiated QoS of the ATM connection, and the number of active multiplexed AAL2 connections.
explanation: The context describes the CPS as a component that manages packet queuing delay and affects PTD and PDV on an ATM link. These actions and their impact on network performance are characteristic of a protocol.
section_title: 5.3.2	Multiplexing and De-multiplexing Delay (TN1)
biotag_Context: O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,B-Technology,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,B-Protocol,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,B-Message,I-Message,I-Message,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Measurement,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,B-Specification,B-Measurement,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O
biotag_Description: O,B-Protocol,I-Protocol,I-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Specification,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Measurement,I-Measurement,I-Measurement,O,O,B-Measurement,I-Measurement,I-Measurement,O,O,B-Network Function,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Measurement,O,O,B-Specification,O,O,O,O,O,O,O,B-Protocol,O