name: BWP
full_form: Bandwidth part
context: The SDAP entities are located in the SDAP sublayer. Several SDAP entities may be defined for a UE. There is an SDAP entity configured for each individual PDU session or MBS session for NR Uu. For NR sidelink, SDAP entity is configured per Destination Layer-2 ID and cast type in the UE. An SDAP entity receives/delivers SDAP SDUs from/to upper layers and submits/receives SDAP data PDUs to/from its peer SDAP entity via lower layers. - At the transmitting side, when an SDAP entity receives an SDAP SDU from upper layers, it constructs the corresponding SDAP data PDU and submits it to lower layers; - At the receiving side, when an SDAP entity receives an SDAP data PDU from lower layers, it retrieves the corresponding SDAP SDU and delivers it to upper layers. Figure 4.2.2-1 illustrates the functional view of the SDAP entity for the SDAP sublayer; it should not restrict implementation. The figure is based on the radio interface protocol architecture defined in TS 38.300 [2]. Figure 4.2.2-1:
description: A Bandwidth Part (BWP) is a channel or a subset of bandwidth resources allocated for sidelink transmission and reception in a 5G network. It provides a convenient way to specify aspects relating to a UE's RF hardware chain implementation, allowing for efficient management of sidelink communications.
explanation: The context describes BWP as being defined for sidelink in a similar way as for UL/DL, indicating that it is related to the allocation and management of bandwidth resources. The mention of subcarrier spacing, resource pools, and S-SSB also suggests that BWP is closely tied to the transmission and reception of data over specific channels or frequencies.
section_title: 6.3.1.1	Sidelink bandwidth parts
biotag_Context: O,B-Protocol,O,O,O,O,O,B-Protocol,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,B-Connection,O,O,B-Service,O,O,B-Network,O,O,B-Network,O,B-Protocol,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,B-Protocol,O,O,B-Protocol,O,O,O,O,O,O,B-Protocol,O,O,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,B-Protocol,B-Parameter,O,O,O,O,O,O,O,B-Protocol,O,B-Connection,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,B-Protocol,O,B-Connection,O,O,O,O,O,O,O,B-Protocol,B-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Protocol,O,O,O,B-Protocol,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Specification,O,O,O,O
biotag_Description: O,B-Parameter,I-Parameter,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Technology,O,O,O,O,O,O,O,O,O,O,O,O,O,B-Parameter,O,O,O,O,O,O,O,O,O,O