Method and apparatus for subband full duplex in mobile wireless communication system

Abstract

A method and apparatus for supporting sub-band full duplex (SBFD) are provided. The method comprises the steps of: a terminal receiving an RRC message containing various parameters for SBFD; triggering a PHR; determining the format of the PHR; determining a PH and PCMAX for non-SBFD uplink transmission and a PH and PCMAX for SBFD uplink transmission; and transmitting a PHR MAC CE.

Description

Technology Field

[0001] The present disclosure relates to a method and apparatus for subband full duplex in a wireless mobile communication system. Background Technology

[0002] TDD is widely used in commercial NR deployments. In TDD, time domain resources are divided between downlink and uplink. If a limited time period is allocated for the uplink in TDD, this can result in reduced coverage, increased latency, and reduced capacity. As a possible improvement, the simultaneous existence of downlink and uplink, i.e., full duplex, or more specifically, subband non-overlapping full duplex (SBFD) on the gNB side within the existing TDD band can be considered. The problem to be solved

[0003] The present disclosure aims to provide a method and apparatus for subband full duplex in a wireless mobile communication system. means of solving the problem

[0004] A method and apparatus for supporting sub-band full duplex (SBFD) are provided. The method comprises the steps of: a terminal receiving an RRC message containing various parameters for SBFD; triggering a PHR; determining the format of the PHR; determining a PH and PCMAX for non-SBFD uplink transmission and a PH and PCMAX for SBFD uplink transmission; and transmitting a PHR MAC CE. Effects of the invention

[0005] The present disclosure provides a method and apparatus for a subband full duplex in a wireless mobile communication system. Brief explanation of the drawing

[0006] Figure 1 is a diagram illustrating the architecture of a 5G system and NG-RAN. Figure 2 is a diagram illustrating the wireless protocol architecture of a 5G system. Figure 3 illustrates a random access procedure. Figure 4 is a diagram illustrating the ASN.1 structure of SIB1 in relation to frequency domain resources. Figure 5 illustrates an example of a frequency domain resource structure. Figure 6 is a diagram illustrating the ASN.1 structure of SIB1 in relation to time domain resources. Figure 7 illustrates an example of a time domain structure. Figure 8 illustrates another example of a frequency domain structure. Figure 9 illustrates another example of a time domain structure. Figure 10 illustrates an example of a resource pool. Figure 11 is a diagram illustrating the ASN.1 structure of SIB1 in relation to the SBFD configuration. Figure 12 illustrates the overall operation of the UE and GNB. Figure 13 is a diagram illustrating the ASN.1 structure of SIB1 in relation to the RACH configuration. Figure 14 illustrates an example of a RACH opportunity. Figure 15 illustrates SBFD-based RACH operation. Figure 16 illustrates another example of a RACH opportunity and function combination. Figure 17 illustrates another example of a frequency domain structure. Figure 18 illustrates the MAC PDU format. Figure 19 illustrates the format of a random access response. Figure 20 illustrates an example of PUSCH resource selection. Figure 21 illustrates an example of a cell's BWP. Figure 22 is a diagram illustrating the ASN.1 structure of SIB1 and RRC reconstruction. Figure 23 is a diagram illustrating the ASN.1 structure of BWP configuration information. Figure 24 is a diagram illustrating the ASN.1 structure of the TDD uplink-downlink configuration. Figure 25 illustrates examples of S-BWP and L-BWP of a cell. Figure 26 illustrates examples of virtual symbols and real symbols. Figure 27 illustrates the operation of the UE and GNB. Figure 28 is a flowchart explaining the operation of the terminal. FIG. 29 is a block diagram illustrating the internal structure of a UE to which the present disclosure applies. FIG. 30 is a block diagram illustrating the configuration of a base station according to the present disclosure. Figure 31 is a diagram illustrating the SFI configuration. Figure 32 is a diagram illustrating periodic uplink signal transmission and periodic downlink reception. Figure 33 is a flowchart explaining the operation of the terminal. Figure 34 illustrates the operation of the UE and GNB for power headroom reporting. Figure 35 illustrates various equations related to uplink transmission power. Figure 36 illustrates various forms of PHR MAC CE. Figure 37 illustrates various forms of PHR MAC CE. Figure 38 illustrates various forms of PHR MAC CE. Figure 39 illustrates mapping information for various fields of PHR MAC CE. Figure 40 is a flowchart illustrating the operation of the UE. Specific details for implementing the invention

[0007] Embodiments of the present disclosure are described in detail below with reference to the attached drawings. Furthermore, if it is determined that a detailed description of related known functions or configurations in the description of the present disclosure would unnecessarily obscure the essence of the present disclosure, such detailed description may be omitted. Additionally, terms described below are defined in consideration of the functions of the present disclosure and may vary depending on the intentions or conventions of users and operators. Therefore, definitions should be based on the content of the entire specification.

[0009] In the following description, the terms used to denote access nodes, network objects, messages, interfaces between network objects, and various identification information are provided for the convenience of explanation. Accordingly, the terms used in the following description are not limited to specific meanings and may be replaced by other terms equivalent in a technical sense.

[0011] For convenience, terms and definitions provided in 3GPP standards are used in the following description. However, this disclosure is not limited to the use of these terms and definitions, and any other terms and definitions may be used instead.

[0013] In this disclosure, the following terms are used interchangeably:

[0014] - Terminal, UE, and wireless device;

[0015] - Information elements (IE) and parameter sets;

[0016] - Parameters, fields, and IE;

[0017] - Base station and gNB.

[0019] Figure 1 is a diagram illustrating the architecture of a 5G system and NG-RAN to which the present disclosure can be applied.

[0020] The 5G system consists of NG-RAN 1A01 and 5GC 1A02. The NG-RAN node is one of the following:

[0021] >1: gNB providing NR user plane and control plane protocol termination for the UE; or

[0022] >1: ng-eNB providing E-UTRA user plane and control plane protocol termination for the UE.

[0023] gNB 1A05 or 1A06 and ng-eNB 1A03 or 1A04 are connected to each other via the Xn interface. The gNB and ng-eNB are connected to the 5GC, more specifically the Access and Mobility Management Function (AMF) and User Plane Function (UPF), via the NG interface. AMF 1A07 and UPF 1A08 may be implemented as physical nodes or as separate physical nodes.

[0025] gNB 1A05 or 1A06 or ng-eNB 1A03 or 1A04 hosts the various functions listed below.

[0026] >1: Functions for radio resource management, e.g., radio bearer control, radio acceptance control, connection mobility control, dynamic allocation (scheduling) of resources for UEs on uplink, downlink, and sidelink; and

[0027] >1: IP and Ethernet header compression, uplink data decompression, and encryption of user data streams; and

[0028] >1: Select AMF when attaching UE when routing to MME cannot be determined from the information provided by UE; and

[0029] >1: Routing user plane data to UPF; and

[0030] >1: Scheduling and transmission of page messages; and

[0031] >1: Scheduling and transmission of broadcast information (derived from AMF or O&M); and

[0032] >1: Configuration of measurement and measurement reporting for mobility and scheduling; and

[0033] >1: Session management; and

[0034] >1: QoS flow management and mapping for data radio bearers; and

[0035] >1: Support for UEs in RRC_INACTIVE state; and

[0037] AMF 1A07 hosts functions such as NAS signaling, NAS signal security, AS security control, SMF selection, authentication, mobility management, and location management.

[0038] UPF 1A08 hosts functions such as packet routing and forwarding, transport-level packet marking on the uplink, QoS processing and downlink, and mobility anchoring for mobility.

[0039] Figure 2 is a diagram illustrating the wireless protocol architecture of a 5G system to which the present disclosure can be applied.

[0040] The user plane protocol stack consists of SDAP 2B01 or 2B02, PDCP 2B03 or 2B04, RLC 2B05 or 2B06, MAC 2B07 or 2B08, and PHY 2B09 or 2B10. The control plane protocol stack consists of NAS 2B11 or 2B12, RRC 2B13 or 2B14, PDCP, RLC, MAC, and PHY.

[0042] Each protocol sublayer performs functions related to the tasks listed below.

[0043] - **NAS**: Authentication, mobility management, security control, etc.

[0045] *- **RRC**: System information, page sending, establishment, maintenance, and release of RRC connections, security features, establishment, configuration, maintenance, and release of Signaled Radio Bearers (SRB) and Data Radio Bearers (DRB), mobility, QoS management, wireless link failure detection and recovery, NAS message transmission, etc.

[0046] - **SDAP**: Mapping between QoS flows and data radio bearers, representing QoS flow IDs (QFI) in downlink (DL) and uplink (UL) packets

[0047] - **PDCP**: Data transmission, header compression and decompression, encryption and decryption, integrity protection and verification, redundancy handling, reordering and sequential delivery, non-sequential delivery, etc.

[0048] - **RLC**: Upper layer PDU transmission, error correction via ARQ, splitting and re-splitting of RLC SDUs, SDU reassembly, RLC reset, etc.

[0049] - **MAC**: Mapping between logical channels and transport channels, multiplexing / demultiplexing MAC SDUs belonging to one or more logical channels into transport blocks (TBs) delivered to the physical layer of the transport channel, reporting scheduling information, handling priority between UEs, handling priority between logical channels of a single UE, etc.

[0050] - **PHY**: Channel coding, physical layer hybrid ARQ processing, ratio matching, scrambling, modulation, layer mapping, downlink control information, uplink control information, etc.

[0052] State transitions between RRC_CONNECTED and RRC_INACTIVE occur through the exchange of Resume messages and Release messages, including Suspend IE.

[0053] State transitions between RRC_CONNECTED and RRC_IDLE occur through the establishment and disconnection of the RRC connection.

[0055] The UE supports three RRC states.

[0056] - **RRC_IDLE**: The UE has no RRC connection with the RAN. The UE monitors the Page Channel and idle mode mobility (UE-based mobility). As the name suggests, data transmission and reception are impossible in the RRC_IDLE state, and power consumption is minimized. To perform data transmission, the UE must transition to the RRC_CONNECTED state.

[0057] - **RRC_CONNECTED**: The UE has a valid RRC connection with the RAN. The UE establishes a radio bearer configured for data transmission / reception. UE mobility is handled by network-controlled handover. The RRC_CONNECTED state is the most power-consuming state. C-DRX and other technologies can be applied to minimize power consumption in this state.

[0058] In the RRC_INACTIVE state, the UE has disconnected its RRC connection with the RAN. Before performing a full data transmission, the UE and the base station resume the disconnected RRC connection. The UE's mobility is treated as idle mode mobility within a region defined by the RAN. If the UE is configured by the base station and is capable, a limited-scale data transmission can be performed in the RRC_INACTIVE state, which is referred to as the small data transmission procedure.

[0060] The RRC_IDLE state has the following characteristics:

[0061] >1: PLMN selection; broadcasting of system information;

[0062] >1: Cell reselection mobility;

[0063] >1: Page sending for mobile exit data is initiated by 5GC;

[0064] >1: DRX for CN pages configured by NAS.

[0066] The RRC_INACTIVE state has the following characteristics:

[0067] >1: PLMN selection; broadcasting of system information;

[0068] >1: Cell reselection mobility;

[0069] >1: Page dispatch is initiated by NG-RAN (RAN page);

[0070] >1: RAN-based notification regions (RNA) are managed by NG-RAN;

[0071] >1: DRX for RAN pages configured by NG-RAN;

[0072] >1: 5GC - NG-RAN connectivity for the UE (both user plane and control plane) is established;

[0073] >1: The UE AS context is stored in NG-RAN and UE;

[0074] 1: NG-RAN knows the RNA to which UE belongs.

[0076] The RRC_CONNECTED state has the following characteristics:

[0077] >1: 5GC - NG-RAN connectivity for the UE (both user plane and control plane) is established;

[0078] >1: The UE AS context is stored in NG-RAN and UE;

[0079] 1: NG-RAN knows the cell to which the UE belongs;

[0080] >1: Unicast data transmission with UE;

[0081] >1: Network control mobility including measurement.

[0082] Figure 3 illustrates a random access procedure.

[0083] The random access procedure enables the UE to align uplink transmission timing, indicate the optimal downlink beam, and transmit a MAC PDU that may include a CCCH SDU (e.g., RRCSetupRequest).

[0084] The random access procedure consists of transmitting a preamble 3A21, receiving a random access response 3A31, transmitting Msg 3 3A41, and resolving contention 3A51.

[0085] Parameters for the random access procedure are provided in SIB1 (for initial access) or RRC reorganization (for RRC handover) 3A11.

[0086] The random access procedure can be triggered by several events, such as the initial access in RRC_IDLE (e.g., the RRC connection establishment procedure), the arrival of DL or UL data, an RRC request due to synchronous reconfiguration (e.g., a handover), and the RRC connection resumption procedure in RRC_INACTIVE.

[0088] When the random access procedure starts, the UE can perform operations in the following order:

[0089] >1: Flush the buffer for Msg 3;

[0090] >1: Initialize counters for preamble transmission and power ramping;

[0091] >1: Select an uplink carrier to perform the random access procedure based on the rsrp threshold (e.g., rsrp-ThresholdSSB-SUL);

[0092] >1: Select a set of random access resources applicable to the current random access procedure;

[0093] >1: Select the SSB based on the rsrp threshold (e.g., rsrp-ThresholdSSB); the SSB corresponds to the downlink beam;

[0094] >1: Selects a random access preamble group based on the path loss of the selected SSB, the potential Msg 3 size, and various parameters (e.g., ra-Msg3SizeGroupA, preambleReceivedTargetPower, msg3-DeltaPreamble, messagePowerOffsetGroupB, etc.); the preamble group selection enables the UE to request a larger uplink allocation for Msg 3 transmission if channel conditions are sufficiently good and the potential Msg 3 size exceeds a specific threshold;

[0095] >1: Randomly select a random access preamble with equal probability from among the random access preambles associated with the selected SSB and the selected random access preamble group;

[0096] >1: Determine the next available PRACH opportunity among the PRACH opportunities corresponding to the selected SSB;

[0097] >1: Determines the transmission power of the preamble;

[0098] >>2: Preamble Transmission Power = Path Loss + preambleReceivedTargetPower + DELTA_PREAMBLE + (PREAMBLE_POWER_RAMPING_COUNTER ? 1) × PREAMBLE_POWER_RAMPING_STEP + POWER_OFFSET_2STEP_RA

[0099] >1: Transmits the preamble with the determined transmission power at the determined PRACH opportunity;

[0100] >1: Start ra-ResponseWindow;

[0101] >1: Monitors the SpCell's PDCCH for random access responses identified by RA-RNTI while ra-ResponseWindow is running;

[0102] >1: Receive a random access response containing a MAC subPDU containing a random access preamble identifier corresponding to the transmitted preamble;

[0103] >1: Processes received timing advance commands and received UL assignments;

[0104] >1: Send Msg 3 based on the received UL assignment;

[0105] >>2: Msg 3 may include a CCCH SDU such as RRCSetupRequest or RRCResumeRequest, for example;

[0106] >1: Start ra-ContentionResolutionTimer;

[0107] >1: Monitors PDCCH while ra-ContentionResolutionTimer is running;

[0108] >1: When a MAC PDU containing a UE contention resolution identifier is received, contention resolution is considered successful;

[0109] >1: The random access procedure is considered to have been successfully completed.

[0110] Subband Full Duplex (SBFD) operation is supported for TDD carriers, enabling simultaneous downlink transmission and uplink reception in each subband at the gNB. From the UE perspective, full duplex is not supported. Cell-specific SBFD time and frequency resource configuration is provided via SIB1 or a dedicated signal.

[0112] If the gNB supports the SBFD function, the gNB provides configuration information for I-BWP and UL-DL-TDD configurations (time pattern information) in the legacy signal field, and provides configuration information for SBFD in a new signal field that can only be understood by a UE that supports SBFD (hereinafter SBFD-UE).

[0113] FIG 4 shows the signal structure of SIB1 for the cell's frequency resource structure.

[0114] servingCellConfigCommon (A100) contains the IE ServingCellConfigCommonSIB, which is used to configure cell-specific parameters of the UE's serving cell in SIB1.

[0115] downlinkConfigCommon (A110) includes IE DownlinkConfigCommonSIB, which provides common downlink parameters for cells.

[0116] UplinkConfigCommon (A120) includes IE UplinkConfigCommonSIB, which provides common uplink parameters for the cell.

[0117] tdd-UL-DL-ConfigurationCommon (A130) includes IE TDD-UL-DL-ConfigCommon, which determines cell-specific uplink / downlink TDD configurations.

[0118] IE FrequencyInfoDL-SIB provides basic parameters for downlink carriers and transmissions.

[0119] FrequencyInfoDL-SIB ::= SEQUENCE {

[0120] frequencyBandListMultiFrequencyBandListNR-SIB,

[0122] * offsetToPointA INTEGER (0..2199),

[0123] scs-SpecificCarrierList SEQUENCE (SIZE (1..maxSCSs)) OF SCS-SpecificCarrier

[0124] }

[0125] The offsetToPointA field represents the offset for Point A. The offset for Point A provides a reference point for a specific carrier list within the SCS (Subcarrier Spacing). Point A acts as a common reference point for the resource block grid.

[0127] The scs-SpecificCarrierList field represents a set of carriers for different subcarrier intervals (numerology). If a cell consists of two or more SCSs, an SCS-SpecificCarrier IE is provided for each SCS.

[0129] IE SCS-SpecificCarrier provides parameters that determine the actual carrier position and width or carrier bandwidth in a given direction. This is defined for specific numerical values ​​(Subcarrier Spacing (SCS)) and in relation to the frequency offset with respect to Point A.

[0130] SCS-SpecificCarrier ::= SEQUENCE {

[0131] offsetToCarrier INTEGER (0..2199);

[0132] subcarrierSpacing SubcarrierSpacing,

[0133] carrierBandwidth INTEGER (1..maxNrofPhysicalResourceBlocks);

[0134] ...,

[0135] [[

[0136] txDirectCurrentLocation INTEGER (0..4095) OPTIONAL -- Need S

[0137] ]]

[0138] }

[0139] The carrierBandwidth field represents the width of this carrier as the number of PRBs (resource blocks) (using the subcarrier spacing defined for this carrier).

[0140] The offsetToCarrier field represents the frequency domain offset in PRB units between Point A (the lowest subcarrier of common RB 0) and the lowest available subcarrier of this carrier (using the subcarrier interval defined for this carrier).

[0141] The subcarrierSpacing field represents the subcarrier spacing of this carrier. This is used to convert offsetToCarrier to the actual frequency.

[0143] The IE SCS-SpecificCarrier for the downlink carrier (e.g., the SCS-SpecificCarrier of FrequencyInfoDL-SIB) additionally includes a new signal field for the SBFD time / frequency resources.

[0144] The IE SCS-SpecificCarrier for the uplink carrier (e.g., the SCS-SpecificCarrier of FrequencyInfoUL-SIB) also additionally includes a new signal field for the SBFD time / frequency resources (A140).

[0146] The initialDownlinkBWP field contains the BWP IE specific to the initial downlink BWP.

[0147] IE BWP is used to configure general parameters of the bandwidth portion.

[0148] BWP ::= SEQUENCE {

[0149] locationAndBandwidth INTEGER (0..37949);

[0150] subcarrierSpacing SubcarrierSpacing,

[0151] cyclicPrefix ENUMERATED { extended} OPTIONAL -- Need R

[0152] }

[0153] The cyclicPrefix field indicates whether to use an extended cyclic prefix for this bandwidth portion. If not set, the UE uses a standard cyclic prefix.

[0154] The locationAndBandwidth field indicates the frequency domain location and bandwidth of this bandwidth portion. The value of this field should be interpreted as a Resource Indicator Value (RIV). The RIV represents a series of consecutive PRBs. The first PRB is the PRB determined by the subcarrier spacing of this BWP and the offsetToCarrier associated with this subcarrier spacing. In the case of TDD, BWP pairs (UL BWP and DL BWP have the same bwp-Id) must have the same center frequency.

[0155] The subcarrierSpacing field indicates the subcarrier spacing to be used for all channels and reference signals in this BWP, and is used unless explicitly configured elsewhere.

[0157] FIG 5 shows an example of a frequency domain structure.

[0158] A 15KHz SCS (SCS-SpecificCarrier for 15KHz, E100) represents the full frequency domain structure of the associated link based on a 15KHz SCS (e.g., 1 PRB = 12 * 15KHz), and a 30KHz SCS (SCS-SpecificCarrier for 30KHz, E110) represents the full frequency domain structure of the associated link based on a 30KHz SCS (e.g., 1 PRB = 12 * 30KHz).

[0159] The UE determines the PRB to use for transmission / reception based on the SCS of the active BWP.

[0160] The UE determines the location and bandwidth (e.g., frequency domain structure) of the initial bandwidth portion based on the SCS-SpecificCarrier IE, where the BWP IE and SCS of the initial bandwidth portion are identical.

[0162] FIG 6 shows the signal structure of SIB1 for the cell's time resource structure.

[0163] The tdd-UL-DL-ConfigCommon field (A130) contains IE TDD-UL-DL-ConfigCommon, which determines the cell-specific uplink / downlink TDD configuration.

[0164] The ReferenceSubcarrierSpacing field (A150) represents the reference SCS used to determine the time domain boundaries of the UL-DL pattern, which must be common across all subcarrier-specific carriers. That is, it is independent of the actual subcarrier spacing used for data transmission. Since the slot length is SCS-specific (e.g., 1ms for a 15KHz SCS, 0.5ms for a 30KHz SCS, 0.25ms for a 60KHz SCS), a cell can have multiple SCSs.

[0165] The pattern1 field (A160) and the pattern2 field (A170) contain TDD-UL-DL-Pattern IE.

[0166] TDD-UL-DL-Pattern ::= SEQUENCE {

[0167] dl-UL-TransmissionPeriodicity ENUMERATED {ms0p5, ms0p625, ms1, ms1p25, ms2, ms2p5, ms5, ms10},

[0168] nrofDownlinkSlots INTEGER (0..maxNrofSlots);

[0169] nrofDownlinkSymbols INTEGER (0..maxNrofSymbols-1);

[0170] nrofUplinkSlots INTEGER (0..maxNrofSlots);

[0171] nrofUplinkSymbols INTEGER (0..maxNrofSymbols-1);

[0172] ...,

[0173] [[

[0174] dl-UL-TransmissionPeriodicity-v1530 ENUMERATED {ms3, ms4} OPTIONAL -- Need R

[0175] ]]

[0176] }

[0177] The dl-UL-TransmissionPeriodicity field indicates the periodicity of the DL-UL pattern (hereinafter, the periodicity of the DL-UL pattern, the periodicity of the pattern, and the slot configuration period are used interchangeably).

[0178] The nrofDownlinkSlots field indicates the number of consecutive total DL slots at the beginning of each DL-UL pattern.

[0179] The nrofDownlinkSymbols field indicates the number of consecutive DL symbols at the beginning of the slot following the last full DL slot (derived from nrofDownlinkSlots). A value of 0 means there are no partial downlink slots.

[0180] The nrofUplinkSlots field indicates the number of consecutive total UL slots at the end of each DL-UL pattern.

[0182] The *nrofUplinkSymbols field indicates the number of consecutive UL symbols at the end of the slot preceding the first full UL slot (derived from nrofUplinkSlots).

[0184] The UE determines the DL symbol, UL symbol, and flexible symbol based on pattern 1 and pattern 2.

[0185] The slot format includes downlink symbols, uplink symbols, and flexible symbols.

[0186] If the UE is provided with tdd-UL-DL-ConfigurationCommon, the UE sets the slot type on a slot-by-slot basis for the multiple slots indicated by tdd-UL-DL-ConfigurationCommon.

[0187] tdd-UL-DL-ConfigurationCommon provides the following:

[0188] > : Reference SCS by referenceSubcarrierSpacing;

[0189] > : pattern1.

[0191] pattern1 provides the following:

[0192] > : Slot configuration period of P milliseconds by dl-UL-TransmissionPeriodicity;

[0193] > : Number of slots containing only downlink symbols by nrofDownlinkSlots d_slot;

[0194] > : Number of downlink symbols by nrofDownlinkSymbols d_sym;

[0195] > : Number of slots containing only uplink symbols by nrofUplinkSlots u_slots;

[0196] > : Number of uplink symbols by nrofUplinkSymbols u_sym.

[0199] A slot configuration period of *P milliseconds contains S = P * slot_scs slots. If the reference SCS is 15 KHz, slot_scs = 1. If the reference SCS is 30 KHz, slot_scs = 2. If the reference SCS is 60 KHz, slot_scs = 4. If the reference SCS is 120 KHz, slot_scs = 8. Among the slots, the first d_slots slot contains only downlink symbols, and the last u_slots slot contains only uplink symbols. The d_sym symbols after the first d_slots slot are downlink symbols. The u_sym symbols before the last u_slots slot are uplink symbols. The remaining symbols are flexible symbols.

[0200] The first symbol of every 20 / P cycle is the first symbol of the even frame.

[0201] If tdd-UL-DL-ConfigurationCommon provides both pattern1 and pattern2, the UE sets the slot-specific format for the first number of slots indicated by pattern1 and the slot-specific format for the second number of slots indicated by pattern2.

[0202] E200 shows an example where Pattern 1 and Pattern 2 appear alternately.

[0204] Simply put, regarding frequency domain cell structures:

[0205] The offsetToCarrier and carrierBandwidth of the SCS-SpecificCarrier IE in FrequencyInfoDL-SIB define the frequency domain PRB structure of the cell's downlink carrier.

[0206] The offsetToCarrier and carrierBandwidth of the SCS-SpecificCarrier IE in FrequencyInfoUL-SIB define the frequency domain PRB structure of the cell's uplink carrier.

[0208] Regarding the time domain cell structure:

[0209] > : dl-UL-TransmissionPeriodicity, nrofDownlinkSlots, nrofDownlinkSymbols, nrofUplinkSlots, and nrofUplinkSymbols define the cell's downlink symbol, flexible symbol, and uplink symbol.

[0211] New parameters are introduced to define the SBFD time / frequency structure along with the existing cell time / frequency structure.

[0213] To enable non-SBFD terminals to operate in a cell, SBFD frequency resources (E300) must not overlap with the initial downlink BWP (E310). The base station may allocate SBFD frequency resources in consecutive RBs to minimize cross-link interference. This can be achieved by placing the SBFD frequency resources / locations as far away as possible from the cell's SSB (i.e., CD-SSB or NCD-SSB). Additionally, this can be achieved by placing the SBFD frequency resources / locations far away from critical reference signals such as PRS or CSI-RS. Signal flexibility must be ensured to guarantee such placement. Furthermore, since the SBFD structure is included in the system information, its size is also important (smaller is better).

[0215] Cells can be arranged at multiple subcarrier intervals (SCS x is top, SCS y is bottom). In this case, the system information includes multiple SCS-SpecificCarrier IEs. SBFD frequency resource information must be indicated on at least one of the one or more SCS-SpecificCarriers. This information may indicate offset and bandwidth. Since SBFD frequency resources are used for uplink transmission, a guard band needs to be inserted between SBFD resources and non-SBFD resources. However, this information does not need to be broadcast in the system information due to downlink reception being limited to the initial downlink BWP for idle / active UEs. Guard band information can be conveyed to connected mode UEs via RRC signals.

[0217] For each SCS-SpecificCarrier IE for downlinks, the following fields are added to the extension section:

[0218] The BandwidthSbfd field represents the width of the SBFD subband (e.g., the opposite subband) as a PRB number using the subcarrier spacing defined for this carrier. 1 PRB occupies 180 KHz at 15 KHz SCS, 360 KHz at 30 KHz, 720 KHz at 60 KHz, and 1440 KHz at 120 KHz.

[0219] The offsetToSbfd field represents the frequency domain offset between the lowest available subcarrier in this carrier and the lowest available subcarrier in the SBFD subband as a PRB number (using the subcarrier interval defined for this carrier).

[0220] The sbfdSCSInd field indicates that the SCS corresponding to this SCS-SpecificCarrier IE is the SCS of the SBFD subband.

[0221] Alternatively, offsetToSub and BandwidthSub are signaled / configured only for a specific SCS, where the specific SCS refers to the SCS used in the SBFD subband. For example, if a 30 KHz SCS is applied to the SBFD subband and a 15 KHz SCS is applied to the initial downlink BWP, the SCS-SpecificCarrier IE for 30 KHz contains the SBFD-specific field, but the SCS-SpecificCarrier IE for 15 KHz does not.

[0223] Since the purpose of SBFD is to provide more uplink opportunities, UL symbols are not affected by SBFD operation. The number of SBFD symbols occurs during the SBFD duration. The SBFD duration occurs for every SBFD cycle.

[0225] A downlink symbol is a symbol in which a downlink signal (no uplink or sidelink signal) is transmitted from the entire PRB of the cell.

[0226] The uplink symbol is the following symbol:

[0227] > : The uplink signal is transmitted from the cell's first PRB;

[0228] The sidelink signal is transmitted from the cell's second PRB, where the union / sum of the first and second PRBs becomes the cell's entire PRB.

[0230] Flexible symbols are the following symbols depending on scheduling / configuration:

[0231] > : Downlink signals are transmitted from the entire PRB of the cell or;

[0232] The uplink signal is transmitted from the first PRB and the sidelink signal is transmitted from the second PRB.

[0234] SBFD symbols are the following symbols depending on scheduling / configuration by the base station:

[0235] The downlink signal is transmitted from the cell's third PRB;

[0237] *> : The uplink signal is transmitted from the cell's fourth PRB, where the union / sum of the third and fourth PRBs becomes the cell's entire PRB.

[0239] E400 shows an example of an SBFD symbol configuration.

[0240] The following points may be noted.

[0241] >: Case where only pattern1 is configured:

[0242] >>: A single SBFD duration occurs every P1 (pattern 1 of tdd-UL-DL-ConfigurationCommon); SBFD period = P1;

[0243] >>: The SBFD duration consists of the following:

[0244] >>>: consecutive downlink symbol; or

[0245] >>>: Consecutive downlink symbols and flexible symbols starting at a specific downlink symbol and ending at a specific flexible symbol; or

[0246] >>>: Continuous flexible symbol.

[0248] When both pattern1 and pattern2 are configured:

[0249] A single SBFD duration occurs every P1 + P2 (pattern 2 of tdd-UL-DL-ConfigurationCommon); SBFD period = P1 + P2;

[0250] >>: The SBFD duration starts and ends in either pattern1 or pattern2 (the first and last SBFD symbols are within the same pattern).

[0251] >>: The SBFD duration consists of the following:

[0252] >>>: consecutive downlink symbols of pattern1; or

[0253] >>>: consecutive downlink symbols of pattern2; or

[0254] >>>: consecutive downlink symbols of pattern1 and consecutive flexible symbols of pattern1; or

[0255] >>>: consecutive downlink symbols of pattern2 and consecutive flexible symbols of pattern2; or

[0256] >>>: Continuous flexible symbol of pattern1;

[0257] >>>: Continuous flexible symbol of pattern2.

[0259] If SBFD is configured, TDD-UL-DL-ConfigCommon IE may include the following fields in addition to existing fields.

[0260] >: **offsetToFirstSBSymbol**: This field indicates the offset to the first SBFD symbol during the SBFD cycle.

[0261] >>: Contains integers; INTEGER (0..maxNrofSymbolsPerSbfdPeriodicity)

[0262] >>: This integer represents the number of symbols between the first symbol of the related pattern (or the first symbol of the slot configuration cycle) and the first symbol of the SBFD duration (or the first SBFD symbol);

[0263] >>: maxNrofSymbolsPerSbfdPeriodicity is determined based on the SBFD period and the SCS indicated by the referenceSubcarrierSpacing field.

[0264] >>>: maxNrofSymbolsPerSbfdPeriodicity = SBFD Period * SCS_symbol; SCS_symbol = 14 * SCS_coefficient; SCS_coefficient = 1 (SCS 15 KHz) or 2 (SCS 30 KHz) or 4 (SCS 60 KHz) or 8 (SCS 120 KHz)

[0265] >>>: SBFD Period = P1 (if only Pattern 1 is configured) or P1 + P2 (if both Pattern 1 and Pattern 2 are configured).

[0267] >: **nrOfSBSymbols**: This field indicates the number of consecutive SBFD symbols during an SBFD cycle (or SBFD duration).

[0268] >>: Contains integers; INTEGER (0..maxNrofSbfdSymbols)

[0269] >>: This integer represents the number of symbols within the SBFD duration;

[0270] >>: maxNrofSbfdSymbols is determined based on the slot configuration period (P1 or P2) and the SCS indicated by the referenceSubcarrierSpacing field.

[0271] >>>: maxNrofSbfdSymbols = Slot configuration period * SCS_symbol;

[0272] >>>: Slot configuration period = P1 (if it is the SBFD duration associated with Pattern 1) or P2 (if it is the SBFD duration associated with Pattern 2).

[0274] >: **associatedPattern**: This field indicates which pattern, Pattern 1 or Pattern 2, the SBFD duration is associated with. If this field is missing, the SBFD duration is associated with Pattern 1.

[0276] Based on the SBFD frequency domain structure and time domain structure, the overall structure is determined as follows (e.g., combination of frequency domain positions and time domain positions).

[0277] From the perspective of IDLE / INACTIVE UE:

[0278] Downlink resources are:

[0279] >>: PRB of the initial BWP during the downlink symbol; and

[0280] >>: PRB of the initial BWP during the SBFD downlink symbol.

[0282] Uplink resources are:

[0284] *>>: PRB of the initial BWP during the uplink symbol; and

[0285] >>: PRB of the SBFD subband during SBFD duration / SBFD symbol (downlink SBFD symbol and flexible SBFD symbol).

[0287] Flexible resources are:

[0288] >>: PRB of the initial BWP during the flexible symbol; and

[0289] >>: PRB of the initial BWP during the SBFD flexible symbol.

[0291] The SBFD downlink symbol is a downlink symbol according to the parameters of TDD-UL-DL-Pattern and an SBFD symbol according to the parameters of SBFD-Pattern.

[0292] The SBFD flexible symbol is a flexible symbol according to the parameters of TDD-UL-DL-Pattern and an SBFD symbol according to the parameters of SBFD-Pattern.

[0294] E500 shows examples of SBFD frequency domain structure and time domain structure.

[0295] Alternatively, fields related to SBFD resources may be included in a single / new IE (A200) to minimize the impact on legacy UEs.

[0297] Figure 12 illustrates the operation of the UE and GNB.

[0298] In S110, the UE (D100) receives system information from the GNB (D200).

[0299] System information includes the following:

[0300] >: Information about the initial downlink BWP;

[0301] >: Information about the initial uplink BWP;

[0302] Uplink carrier information for the first SCS;

[0303] Uplink carrier information for the second SCS;

[0304] >: Downlink carrier information for the first SCS;

[0305] >: Downlink carrier information for the second SCS;

[0306] >: Information on uplink-downlink slot configuration;

[0307] In O120, the UE determines the downlink symbol, uplink symbol, flexible symbol, and SBFD symbol based on relevant information.

[0308] Information regarding the uplink-downlink slot configuration includes a first set of parameters for the slot configuration and a second set of parameters for the slot configuration. The UE determines the downlink symbol, flexible symbol, and uplink symbol based on the first set of parameters for the slot configuration. The UE determines the SBFD symbol from the downlink symbol and flexible symbol based on the second set of parameters for the slot configuration.

[0310] The **downlink symbol** is the following symbol:

[0311] >>: Downlink symbol according to the first set of parameters for slot configuration; and

[0312] >>: Non-SBFD symbols according to the second parameter set for slot configuration;

[0314] The **flexible symbol** is the following symbol:

[0315] >>: Flexible symbol based on the first set of parameters for slot configuration (neither a downlink symbol nor an uplink symbol); and

[0316] >>: Non-SBFD symbols according to the second parameter set for slot configuration;

[0318] The **SBFD symbol** is the following symbol:

[0319] >>: Downlink symbol according to the first set of parameters for the slot configuration; and SBFD symbol according to the second set of parameters for the slot configuration; or

[0320] >>: Flexible symbol according to the first set of parameters for slot configuration; and SBFD symbol according to the second set of parameters for slot configuration;

[0322] The **uplink symbol** is the following symbol:

[0323] >>: Uplink symbol based on the first set of parameters for slot configuration.

[0325] In O130, the UE determines the PRB of the initial uplink BWP, the PRB of the initial downlink BWP, and the SBFD PRB based on relevant information.

[0326] Downlink carrier information for the first SCS includes a set of parameters for SBFD frequency positions specific to the first SCS. Downlink carrier information for the second SCS includes a set of parameters for SBFD frequency positions specific to the second SCS.

[0328] The UE determines the PRB structure of the uplink carrier specific to the first SCS based on the uplink carrier information for the first SCS. The UE determines the PRB structure of the uplink carrier specific to the second SCS based on the uplink carrier information for the second SCS.

[0329] The UE determines the PRB structure of the downlink carrier specific to the first SCS based on the downlink carrier information for the first SCS. The UE determines the PRB structure of the downlink carrier specific to the second SCS based on the downlink carrier information for the second SCS.

[0331] The UE determines the SBFD PRB specific to the first SCS based on a set of parameters for the SBFD frequency position specific to the first SCS. The UE determines the SBFD PRB specific to the second SCS based on a set of parameters for the SBFD frequency position specific to the second SCS.

[0332] The UE determines the SCS of the initial uplink BWP based on the subcarrierSpacing field of the BWP IE for the initial downlink BWP.

[0333] The UE determines the SCS of the SBFD PRB based on the sbfdSCSInd field, the sbfdSubCarrierSpacing field, or a specific SCS-SpecificCarrier. The SCS of the SBFD PRB is applied to uplink transmissions from the SBFD resource.

[0334] The UE determines the PRB for the initial uplink BWP based on the initial uplink BWP information and the uplink carrier information for the specific SCS. The specific SCS is the SCS indicated by the initial downlink BWP information.

[0336] The UE determines the PRB for the initial downlink BWP based on the initial downlink BWP information and the downlink carrier information for the specific SCS. The specific SCS is the SCS indicated by the initial downlink BWP information.

[0338] The UE determines the PRB for the SBFD resource based on downlink carrier information regarding the second specific SCS. The second specific SCS is the SCS of the SBFD PRB determined according to the sbfdSCSInd field, the sbfdSubCarrierSpacing field, or the specific SCS-SpecificCarrier IE. The PRB for the SBFD resource is used for uplink transmission.

[0340] In O140, the UE determines the initial uplink resource pool, initial downlink resource pool, and SBFD resource pool based on the determined symbols and PRB.

[0341] In O150, the UE performs a random access procedure based on the initial uplink resource pool and the initial downlink resource pool or the SBFD resource pool and the initial downlink resource pool.

[0343] The initial downlink resource pool is a set of downlink resources that the IDLE / INACTIVE UE performs initial access to (e.g., receiving RAR and monitoring PDCCH for Msg 3 retransmission and receiving Msg 4). The initial downlink resources are pairs of the PRB of the initial downlink BWP and downlink-specific symbols.

[0345] The initial uplink resource pool is a set of uplink resources that the IDLE / INACTIVE UE performs initial access to (e.g., sending a PRACH preamble, sending a PUSCH for Msg 3, and sending a HARQ ACK for Msg 4). The initial uplink resources are pairs of the PRB of the initial uplink BWP and uplink-specific symbols.

[0347] The SBFD resource pool is a set of SBFD resources that the IDLE / INACTIVE UE performs initial access to (e.g., sending a PRACH preamble, sending a PUSCH for Msg 3, and sending a HARQ ACK for Msg 4). An SBFD resource is a pair of SBFD PRBs and SBFD symbols.

[0349] The specific downlink symbol is one of the following:

[0350] >: Downlink symbol; or

[0351] >: The following flexible symbol:

[0352] >>: CORESET associated with searchSpaceSIB1 or SearchSpaceOtherSystem or ra-SearchSpace or pagingSearchSpace.

[0354] The specific uplink symbol is one of the following:

[0355] >: Uplink symbol; or

[0356] >: Flexible symbol corresponding to the RACH opportunity based on the PRACH-configIndex of RACH-ConfigCommon for the initial uplink BWP.

[0357] The UE performs random access procedures with the GNB based on the decisions made in O160.

[0358] The UE performs a preamble transmission from an initial uplink resource or an SBFD resource.

[0359] The UE performs RAR reception from the initial downlink resource.

[0360] The UE performs Msg 3 transmission on the initial uplink time / frequency resource or the SBFD time / frequency resource.

[0361] The UE receives Msg 4 from the initial downlink resource.

[0363] *

[0364] UEs perform random access procedures for various purposes. The delay or latency required to complete random access procedures affects the user experience. For example, when random access is triggered for initial access, a longer random access delay results in a longer delay in service startup. When random access is triggered for handover, a longer random access delay causes longer service interruptions.

[0366] A RACH Occasion (RO) is a specified area in the time and frequency domain (or time-frequency resource) available for receiving / transmitting a RACH preamble.

[0367] Multiple ROs are configured within a cell. The number of ROs per unit of time is called RO density. RO density significantly impacts random access latency because the UE must wait until the first available RO occurs. In TDD systems, it is impossible to dense ROs because ROs cannot be configured on downlink symbols. This limitation can be mitigated to some extent by applying SBFD to the random access procedure.

[0369] The basic idea is to configure ROs even on SBFD resources. Since SBFD resources and initial uplink resources are discrete in the frequency domain (and also in the time domain), it is advisable to limit preamble transmission to either the legacy RO or the SBFD RO. Since legacy UEs cannot transmit preambles on SBFD ROs, the GNB must ensure that signals related to SBFD Random Access (SBFD RA) are placed at appropriate locations so that only SBFD UEs can decode them. The GNB must also ensure that parameters common to both SBFD RA and SBHD (Subband Half-Duplex; random access performed based on the RO of the initial uplink / flexible resource) RA are signaled only once.

[0371] FIG 13 shows the random access signal structure of an INACTIVE UE.

[0372] A traditional INACTIVE UE performs Random Access (RA) in the initial uplink BWP (first frequency domain) and the initial downlink BWP (second frequency domain). Parameters for RA are contained in a container called RACH-Config (IE for RACH-Config). BWP-UplinkCommon (Uplink BWP Common Configuration; IE for the first frequency domain) for the initial uplink BWP may contain one or more RACH-ConfigCommons to support various function combinations. This is to allow the GNB to know as quickly as possible which function (or function combination) triggers Random Access (e.g., when a preamble is received). Each RACH-ConfigCommon may contain RA parameters for a function combination.

[0373] One might consider defining more RACH-ConfigCommons specific to SBFD-RA. However, this approach complicates the signal structure and increases signal overhead. This is because 1) many parameters apply commonly to both SBHD RA and SBFD RA, and 2) RACH-ConfigCommons specific to SBFD-RA need to be configured for each function combination. In this disclosure, SBFD-specific RA parameters are added to the extensions that are not decoded by legacy UEs to minimize signal overhead.

[0375] RACH-ConfigCommon includes RACH-ConfigGeneric (IE for RA general configuration), featureCombinationPreamblesList, and other RA parameters. Additionally, Sbfd-RACH-Config IE (IE for RA in the second frequency domain) is added to the extension part of RACH-ConfigCommon.

[0377] RACH-ConfigCommon provides parameters for RO and preamble sets. The RO set associated with RACH-ConfigCommon is defined by the parameters of RACH-ConfigGeneric. An additional RO set is provided by Sbfd-RACH-Config IE. The RO set defined by RACH-ConfigGeneric is the default RO set (default-RO-set). The additional RO set defined by Sbfd-RACH-Config IE is the SBFD RO set (sbfd-RO-set). The RO of the default RO set is the default RO (default-RO). The RO of the SBFD RO set is the SBFD RO (sbfd-RO).

[0379] RAs triggered for specific feature combinations use a specific subset of ROs and a specific subset of preambles determined from the set of ROs. These specific subsets of ROs and specific subsets of preambles are determined based on the corresponding FeatureCombinationPreambles IE and other IEs.

[0380] A specific subset of ROs may include only the default RO (default-RO), only the SBFD RO (sbfd-RO), or both.

[0382] About FeatureCombinationPreambles in featureCombinationPreambleList:

[0383] If sbfdEnabled(A500) is included in the corresponding FeatureCombinationPreambles, both default RO (default-RO) and SBFD RO (sbfd-RO) can be used for RA.

[0384] If sbfdEnabled is not included in the corresponding FeatureCombinationPreambles, only the default RO is available for RA.

[0386] For FeatureCombinationPreambles of featureCombinationPreambleList2(A900), only SBFD RO can be used for RA.

[0387] The parameters of RACH-ConfigCommon are explained below.

[0388] Other RA parameters (A600) are as follows.

[0389] totalNumberOfRA-Preambles: The total number of preambles used for contention-based and contention-free Phase 4 or Phase 2 random access to RACH resources defined in RACH-ConfigCommon, excluding other uses (e.g., preambles used for SI requests). If this field is omitted, all 64 preambles are available for RA. The setting must match the setting of ssb-perRACH-OccasionAndCB-PreamblesPerSSB, i.e., be a multiple of the number of SSBs per RACH opportunity.

[0390] ssb-perRACH-OccasionAndCB-PreamblesPerSSB: This field has two meanings: CHOICE conveys information about the number of SSBs per RACH opportunity. The value oneEighth corresponds to 1 SSB associated with 8 RACH opportunities, and the value oneFourth corresponds to 1 SSB associated with 4 RACH opportunities. The ENUMERATED part indicates the number of contested preambles per SSB. The value n4 corresponds to 4 contested preambles per SSB, and the value n8 corresponds to 8 contested preambles per SSB. The total number of CB preambles in a RACH opportunity is given by CB-preambles-per-SSB * max(1, SSB-per-rach-occasion).

[0391] ra-ContentionResolutionTimer: Initial value of the contention resolution timer

[0392] msg1-SubcarrierSpacing: PRACH's subcarrier spacing for the default RO

[0393] FeatureCombinationPreambles: IE FeatureCombinationPreambles links a set of preambles associated with feature combinations.

[0394] msg3-transformPrecoder: Enables the transform precoder for Msg3 transmission. If this field is missing, the UE disables the transform precoder.

[0395] groupBconfigured: Parameter set for group B-based random access.

[0396] prach-RootSequenceIndex: PRACH root sequence index. Represents the index for L=839 or L=139.

[0397] prach-RootSequenceIndex-r16: PRACH root sequence index. Represents the index for L=571 or L=1151.

[0398] The following describes RACH-ConfigGeneric (A700).

[0399] prach-ConfigurationIndex: PRACH configuration index.

[0400] msg1-FDM: Number of PRACH transmission opportunities FDMed in a single time instance.

[0401] msg1-FrequencyStart: Offset of the lowest PRACH transmission opportunity for PRB 0 in the frequency domain. The value is configured so that the corresponding RACH resource is completely contained within the bandwidth of the UL BWP.

[0402] preambleReceivedTargetPower: Target power level of the network receiver.

[0403] preambleTransMax: Maximum number of RA preamble transmissions performed before declaring failure.

[0404] powerRampingStep: PRACH's power ramping step.

[0405] ra-ResponseWindow: Msg2 (RAR) Window length (number of slots).

[0406] The following explains FeatureCombinationPreambles.

[0407] DeltaPreamble: Power offset between the Msg3 or msgA-PUSCH transfer and the RACH preamble transfer. If this parameter is configured, this parameter overrides msg3-DeltaPreamble or msgA-DeltaPreamble.

[0408] featureCombination: Indicates which feature combination the preamble displayed by this IE is associated with. The UE ignores the RACH resources defined by this FeatureCombinationPreambles if any feature within the feature combination is not supported by the UE or if the slack field within the feature combination is set to true.

[0409] numberOfPreamblesPerSSB-ForThisPartition: Determines how many consecutive preambles are associated per SSB, starting from the starting preamble, based on the feature combination.

[0410] ssb-SharedRO-MaskIndex: Represents a subset of ROs to which a preamble is assigned for this feature combination.

[0411] startPreambleForThisPartition: Defines the first preamble associated with the feature combination.

[0412] sbfdEnabled: Indicates whether SBFD resources are available to the RA associated with this feature combination. If this field is missing, SBFD resources are not allowed to the RA associated with the feature combination.

[0413] ssb-SharedRO-MaskIndex: Represents a subset of ROs to which a preamble is assigned for this feature combination.

[0414] groupBconfigured: Parameter set for group B-based random access.

[0415] The following describes Sbfd-Config (A800).

[0416] prach-ConfigurationIndex-sbfd: PRACH configuration index for SBFD RA. If this field is missing, the relevant parameters of RACH-ConfigGeneric are applied.

[0417] msg1-FDM-sbfd: The number of FDMed PRACH transmission opportunities in a single time instance for SBFD RA. If this field is missing, the relevant parameters of RACH-ConfigGeneric apply.

[0418] msg1-FrequencyStart-sbfd: Offset of the lowest PRACH transmission opportunity in the frequency domain for PRB 0 of the SBFD. The value is configured so that the corresponding RACH resource is completely contained within the bandwidth of the SBFD subband.

[0419] preambleReceivedTargetPower-sbfd: Target power level of the network receiving side; if this field is missing, the value of RACH-ConfigGeneric is applied.

[0420] preambleTransMax-sbfd: The maximum number of RA preamble transfers performed before declaring failure for SBFD RA. If this field is missing, the value of RACH-ConfigGeneric applies.

[0421] powerRampingStep-sbfd: Power ramping step for PRACH. If this field is missing, the value of RACH-ConfigGeneric is applied.

[0422] ra-ResponseWindow-sbfd: Msg2 (RAR) Window length (number of slots) (determined by the SCS of the initial DL BWP). If this field is missing, the value of RACH-ConfigGeneric is applied.

[0423] ssb-perRACH-OccasionAndCB-PreamblesPerSSB-sbfd SBFD: Indicates the number of SSBs per RACH opportunity and the number of contention-based preambles per SSB. If this field is missing, ssb-perRACH-OccasionAndCB-PreamblesPerSSB applies.

[0424] msg1-SubcarrierSpacing-sbfd: Subcarrier spacing of PRACH for SBFD RA. If this field is missing, msg1-SubcarrierSpacing applies.

[0425] groupBconfigured-sbfd: A set of parameters for group B-based random access to SBFD RA. If this field is missing, groupBconfigured-sbfd applies.

[0426] prach-RootSequenceIndex-sbfd: PRACH root sequence index. Represents the index for L=839 or L=139 or L=571 or L=1151. If this field is missing and RACH-ConfigCommon has prach-RootSequenceIndex-r16, prach-RootSequenceIndex-r16 is applied. If this field is missing, prach-RootSequenceIndex-r16 is missing, and prach-RootSequenceIndex is present, prach-RootSequenceIndex is applied.

[0427] Figure 14 shows examples of default RO and SBFD RO.

[0428] The E600 shows examples of basic RO and SBFD RO in the following configurations:

[0429] >: **prach-ConfigurationIndex** indicates that the default RO occurs in subframes 5 and 9 of every radio frame;

[0430] >: **msg1-FDM** indicates that two primary ROs are configured in the same time instance;

[0431] >: **msg1-FrequencyStart** indicates that the first default RO is configured in PRB1 of the initial BWP;

[0432] >: **prach-ConfigurationIndex-sbfd** indicates that SBFD RO occurs in subframes 2 and 4 of every radio frame;

[0433] >: **msg1-FDM-sbfd** indicates that two SBFD ROs are configured in the same time instance;

[0434] >: **msg1-FrequencyStart-sbfd** indicates that the first SBFD RO is configured in PRB1 of the SBFD resource.

[0436] If SBFD RO overlaps with an SSB symbol, it is considered invalid.

[0437] Based on existing signals and new signals, the INACTIVE UE equipped with SBFD performs a random access procedure.

[0439] Figure 15 illustrates a random access procedure.

[0440] In O150-05, the UE triggers RA. RA can be triggered for function combinations, by a PDCCH command, for handover, or by mobility management.

[0441] In O150-10, the UE determines the uplink between the SUL (secondary uplink) and the NUL (primary uplink). This step may be skipped if the serving cell is not configured as a secondary uplink. If the RSRP of the downlink path loss reference is less than the rsrp-ThresholdSSB-SUL indicated in RACH-ConfigCommon, the UE selects the SUL carrier to perform the random access procedure. If the RSRP of the downlink path loss reference is greater than or equal to the rsrp-ThresholdSSB-SUL, the UE selects the NUL carrier to perform the random access procedure.

[0443] In O150-15, the UE selects the RA resource set and frequency domain. The UE performs the following:

[0444] The UE determines whether Msg3 iteration is applicable based on rsrp-ThresholdMsg3 and other related parameters;

[0445] The UE determines whether Msg1 iteration is applicable and the number of iterations (if applicable) based on rsrp-ThresholdMsg1-RepetitionNum8, rsrp-ThresholdMsg1-RepetitionNum4, rsrp-ThresholdMsg1-RepetitionNum2, and other related parameters;

[0446] The UE selects a set of random access resources based on the availability of the function;

[0447] The UE selects a frequency domain according to the set of random access resources selected for this random access procedure.

[0448] To determine whether the Msg3 iteration is applicable to the UE, the following conditions are examined:

[0449] >: If the BWP selected for the random access procedure (where the RACH configuration IE of the initial uplink BWP is present) consists of both a random access resource set where msg3-Repetitions is set to true and a random access resource set where msg3-Repetitions is not set to true, and the RSRP of the downlink path loss reference is lower than rsrp-ThresholdMsg3; or

[0450] >: If the BWP selected for the random access procedure consists only of a set of random access resources where msg3-Repetitions is set to true:

[0451] >>: It is assumed that Msg3 iterations are applicable to the current random access procedure.

[0452] Otherwise:

[0453] >>: It is assumed that Msg3 iterations do not apply to the current random access procedure.

[0455] To determine whether the UE can iterate through Msg1 and, if so, to determine the number of iterations, the following conditions are examined:

[0456] If contention-free random access resources were provided for this random access procedure and the number of Msg1 iterations is indicated in rach-ConfigDedicated:

[0457] >>: It is assumed that Msg1 iterations are applicable, and the number of Msg1 iterations applicable to the current random access procedure is the number of Msg1 iterations indicated in rach-ConfigDedicated.

[0458] Otherwise, if contention-free random access resources are not provided for this random access procedure, and the BWP for the random access procedure (if the RACH configuration IE of the initial uplink BWP is present) consists of a set of random access resources with msg1-Repetitions set to true and a set of random access resources with msg1-Repetitions not set to true:

[0459] >>: If the BWP selected for the random access procedure (where the RACH configuration IE of the initial uplink BWP is present) consists of a random access resource set corresponding to Msg1 iteration number 8, and the RSRP of the downlink path loss reference is lower than rsrp-ThresholdMsg1-RepetitionNum8:

[0460] >>>: It is assumed that Msg1 iterations are applicable, and the number of Msg1 iterations applicable to the current random access procedure is 8.

[0461] >>: If the BWP selected for the random access procedure (where the RACH configuration IE of the initial uplink BWP is present) consists of a set of random access resources corresponding to Msg1 iteration number 4, and the RSRP of the downlink path loss reference is lower than rsrp-ThresholdMsg1-RepetitionNum4:

[0462] >>>: It is assumed that Msg1 iterations are applicable, and the number of Msg1 iterations applicable to the current random access procedure is 4.

[0463] >>: If the BWP selected for the random access procedure (where the RACH configuration IE of the initial uplink BWP is present) consists of a set of random access resources corresponding to Msg1 iteration number 2, and the RSRP of the downlink path loss reference is lower than rsrp-ThresholdMsg1-RepetitionNum2:

[0464] >>>: It is assumed that Msg1 iterations are applicable, and the number of Msg1 iterations applicable to the current random access procedure is 2.

[0465] >>: Otherwise, if the RSRP of the downlink path loss reference is not less than any configured rsrp-ThresholdMsg1-RepetitionNumX:

[0466] >>>: It is assumed that the Msg1 iteration does not apply to the current random access procedure.

[0467] Otherwise, if the BWP selected for the random access procedure (where the RACH configuration IE of the initial uplink BWP is present) consists only of random access resources with msg1-Repetitions set to true:

[0468] >>: It is assumed that the Msg1 iteration is applicable to the current random access procedure;

[0469] >>: If one or more of rsrp-ThresholdMsg1-RepetitionNumX are configured:

[0470] >>>: If rsrp-ThresholdMsg1-RepetitionNum8 is configured and the RSRP of the downlink path loss reference is lower than rsrp-ThresholdMsg1-RepetitionNum8:

[0471] >>>>: The number of Msg1 iterations applicable to the current random access procedure is considered to be 8.

[0472] >>>: If rsrp-ThresholdMsg1-RepetitionNum4 is configured and the RSRP of the downlink path loss reference is lower than rsrp-ThresholdMsg1-RepetitionNum4:

[0473] >>>>: The number of Msg1 iterations applicable to the current random access procedure is considered to be 4.

[0474] >>>: If rsrp-ThresholdMsg1-RepetitionNum2 is configured and the RSRP of the downlink path loss reference is lower than rsrp-ThresholdMsg1-RepetitionNum2:

[0475] >>>>: The number of Msg1 iterations applicable to the current random access procedure is considered to be 2.

[0476] >>>: Otherwise, if the RSRP of the downlink path loss reference is greater than or equal to any configured rsrp-ThresholdMsg1-RepetitionNumX:

[0477] >>>>: The number of Msg1 iterations applicable to the current random access procedure is considered to be the lowest number of Msg1 iterations configured for this BWP.

[0478] >>: Otherwise (if neither rsrp-ThresholdMsg1-RepetitionNumX is configured):

[0479] >>>: The number of Msg1 iterations applicable to the current random access procedure is considered to be the number of Msg1 iterations configured for this BWP.

[0481] For the UE to select a set of random access resources based on feature availability:

[0482] If contention-free random access resources or random access resources for SI requests are not provided for this random access procedure, and (e) one or more functions including RedCap and / or Slicing and / or SDT and / or MSG3 iterations and / or MSG1 iterations are applied to this random access procedure:

[0483] >>: If there is no set of available random access resources for all functions applicable to the current random access procedure:

[0484] >>>: Select a set of random access resources that are not related to the feature indication for this random access procedure.

[0485] Otherwise, if there is a single set of random access resources that can be used to represent all functions currently triggering random access procedures:

[0486] >>>: Select this set of random access resources for this random access procedure.

[0487] >>: Otherwise, if there are multiple sets of random access resources that can be used to represent all functions currently triggering the random access procedure, and if the Msg1 iteration applies to this random access procedure:

[0488] >>>: Select the random access resource set associated with the highest number of iterations from the random access resource sets.

[0490] *>>: Otherwise (i.e., if there is one or more sets of random access resources configured with indications for a subset of all functions that trigger this random access procedure):

[0491] >>>: For this random access procedure, a set of random access resources is selected from the set of available random access resources according to the priority order specified by the upper layer (as specified in Klaus 5.1.1d).

[0493] Otherwise, if a contention-free random access resource with Msg1 iterations is provided for this random access procedure, the number of Msg1 iterations is indicated in rach-ConfigDedicated, and RedCap is applied to the current random access procedure:

[0494] >>: Selects a set of random access resources composed only of RedCap marks and Msg1 iteration marks, and associated with the number of Msg1 iterations marked for this random access procedure.

[0496] Otherwise, if a contention-free random access resource with Msg1 iterations is provided for this random access procedure, the number of Msg1 iterations is indicated in rach-ConfigDedicated, and eRedCap is applied to the current random access procedure:

[0497] >>: Selects a set of random access resources composed only of eRedCap indications and Msg1 iteration indications, and associated with the number of Msg1 iterations indicated for this random access procedure.

[0499] Otherwise, if a contention-free random access resource has been provided for this random access procedure and there is a set of random access resources consisting only of RedCap marks where RedCap is applied to the current random access procedure; or

[0500] >: If contention-free random access resources have been provided for this random access procedure and eRedCap is applied to the current random access procedure and there is a set of random access resources consisting only of eRedCap indications; or

[0501] If contention-free random access resources have been provided for this random access procedure, eRedCap is applied to the current random access procedure, there is no set of random access resources consisting only of eRedCap markings, and there is one set of random access resources consisting only of RedCap markings:

[0502] >>: Select this set of random access resources for this random access procedure.

[0504] Otherwise:

[0505] >>: If the random access procedure is started by the PDCCH command with the DCI PRACH association indicator field set to 1 and SSB-MTC-AdditionalPCI is configured by the upper layer:

[0506] >>>: Select the set of random access resources corresponding to the active additionalPCI.

[0507] Otherwise, if the random access procedure is initiated by a PDCCH command for an LTM candidate cell:

[0508] >>>: Selects the set of random access resources corresponding to the Cell indicator field of the PDCCH command.

[0509] >>: Otherwise, if a contention-free random access resource with Msg1 iterations is provided for this random access procedure and the number of Msg1 iterations is indicated in rach-ConfigDedicated:

[0510] >>>: Selects a set of random access resources that consists only of Msg1 iteration indicators and is associated with the number of Msg1 iterations indicated for this random access procedure.

[0511] >>: Otherwise, if a random access procedure was initiated for an SI request and random access resources related to the Msg1 iteration and the number of Msg1 iterations for the SI request were provided for this random access procedure:

[0512] >>>: Selects a set of random access resources that consists only of Msg1 iteration indicators and is associated with the number of Msg1 iterations indicated for this random access procedure.

[0513] >>: Otherwise:

[0515] *>>>: Selects a set of random access resources that are not related to the function display for the current random access procedure.

[0517] To determine whether a set of random access resources is available to the UE:

[0518] If eRedCap is set to true for a random access resource set:

[0519] For random access procedures to which eRedCap does not apply, the corresponding set of random access resources is considered unavailable.

[0520] If the random access resource set is configured for a 4-level RA type but not for a 2-level RA type, and redCap is set to true:

[0521] For random access procedures to which RedCap does not apply, the corresponding set of random access resources is considered unavailable.

[0522] If redCap is set to true, regardless of whether the random access resource set is configured for a 2-level RA type and also for a 4-level RA type:

[0523] >>: (e) For random access procedures to which RedCap does not apply, the corresponding set of random access resources is considered unavailable;

[0524] >>: In the following procedures (Cloud 5.1.1c and 5.1.1d), eRedCap is considered as both eRedCap and RedCap.

[0525] If smallData is set to true for a random access resource set:

[0526] For random access procedures that are not triggered for RA-SDT by MO-SDT, the corresponding set of random access resources is considered unavailable.

[0527] If an NSAG-List is configured for a random access resource set:

[0528] >>: The set of random access resources is considered unavailable for the corresponding random access procedure unless triggered by any NSAG-ID in the NSAG-List.

[0529] If msg3-Repetitions is set to true for a random access resource set:

[0530] >>: Msg3 If the iteration does not apply to the current random access procedure, the corresponding set of random access resources is considered unavailable.

[0531] If msg1-Repetitions is set to true for a random access resource set:

[0532] >>: If Msg1 iteration is not applied to the current random access procedure; or

[0533] >>: If it is a set of random access resources unrelated to the number of Msg1 iterations applicable to the current random access procedure:

[0534] >>>: The set of random access resources is considered unavailable for the corresponding random access procedure.

[0535] If the random access resource set is not composed of a Feature Combination:

[0536] >>: The set of random access resources is considered to be unrelated to any function.

[0538] As a result of selecting a set of random access resources, the UE determines specific RACH-ConfigCommon and specific featureCombinationPreambles for the random access procedure. Based on the selected RACH-ConfigCommon and selected featureCombinationPreambles, the UE determines the RO for preamble transmission.

[0539] Figure 16 shows an example.

[0540] Each square represents a Random Access Opportunity (RO). If RACH-ConfigCommon contains three featureCombinationPreambles, the RO associated with the feature combination occurs as E700.

[0542] Depending on the case:

[0543] >>: A specific RACH-ConfigCommon is associated with additional ROs (e.g., includes sbfd-RACH-Config); and

[0544] >>: If a specific featureCombinationPreamble allows the use of both the primary RO and additional ROs (e.g., includes sbfdEnabled),

[0545] Both the additional RO and the basic RO are available in the random access resource set (available for the selected random access procedure). FC1 in the figure corresponds to this case.

[0547] Depending on the case:

[0548] >>: A specific RACH-ConfigCommon is associated with additional ROs (e.g., includes sbfd-RACH-Config); and

[0549] >>: If a specific featureCombinationPreamble is allowed to disable additional ROs (e.g., sbfdEnabled is not included),

[0550] Only the basic RO is available in the random access resource set (available for the selected random access procedure). FC2 in the figure corresponds to this case.

[0552] Depending on the case:

[0553] >>: A specific RACH-ConfigCommon is associated with additional ROs (e.g., includes sbfd-RACH-Config); and

[0554] >>: If a specific featureCombinationPreamble is not allowed to use the default RO (i.e., only allowed to use additional RO) (e.g., new list of featureCombinationPreambles),

[0555] Only additional ROs are available from the random access resource set (available for the selected random access procedure). FC3 in the figure corresponds to this case.

[0557] If both the primary RO and the additional RO are available for the random access procedure, the UE decides one of two for the preamble transfer.

[0558] Depending on the case:

[0559] >>: The associated feature combination includes Msg1 iteration (if associated with a selected set of random access resources); and

[0560] >>: If Msg1 iterations are allowed across the RA region (e.g., the corresponding featureCombinationPreambles contain specific new indications),

[0561] The UE performs preamble transmission in both the primary RA area and the additional RA area.

[0563] Depending on the case:

[0564] >>: The associated function combination does not include Msg1 repetition;

[0565] >>: If Msg1 repetition is not allowed across the RA region,

[0566] The UE selects one of the primary RA region and the additional RA region, and performs a preamble transfer in the selected RA region. The UE selects the RA region where the RO corresponding to the selected SSB comes first.

[0568] In S150-20, the UE transmits Msg1 / preamble at a specific RO in the determined RA area.

[0569] To determine a specific RO, the UE can perform the following:

[0571] **For SSB selection:**

[0572] If one or more of the SSBs where SS-RSRP exceeds rsrp-ThresholdSSB are available:

[0573] >>: Select the SSB where SS-RSRP exceeds rsrp-ThresholdSSB.

[0574] Otherwise:

[0575] >>: Select any SSB.

[0577] **For Preamble Group Selection:**

[0578] If Random Access Preamble Group B is configured:

[0579] >>: If the potential Msg3 size (sum of transmittable UL data, MAC subheader, and MAC CE if necessary) is greater than ra-Msg3SizeGroupA and the path loss is lower than PCMAX (of the serving cell performing the random access procedure) ? preambleReceivedTargetPower ? msg3-DeltaPreamble ? messagePowerOffsetGroupB:

[0580] >>>: Select Random Access Preamble Group B.

[0581] >>: Otherwise:

[0582] >>>: Select Random Access Preamble Group A.

[0583] Otherwise:

[0584] >>: Select Random Access Preamble Group A.

[0586] **Cases for determining RO:**

[0587] If the set of random access resources associated with the Msg1 iteration was selected for this random access procedure:

[0588] >>: Determines the next available set of applicable PRACH opportunities for the number of Msg1 iterations corresponding to the selected SSB (as specified in TS 38.213 [6]). This is permitted by the given restrictions if ra-ssb-OccasionMaskIndex is configured, or if ssb-SharedRO-MaskIndex is configured. The set of PRACH opportunities may include only the primary RO (if the primary RA area is selected), only the additional RO (if the additional RA area is selected), or both the primary RO and the additional RO (or if iterations across the RA area are permitted).

[0589] Otherwise:

[0590] >>: Determines the next available PRACH opportunity corresponding to the selected SSB. It is allowed according to the given restrictions if ra-ssb-OccasionMaskIndex is configured, or ssb-SharedRO-MaskIndex is configured, or indicated by PDCCH, or indicated by the LTM cell switching command MAC CE. If the initial transfer was performed on the primary RO, the PRACH opportunity for retransmission is the primary RO. If the initial transfer was performed on the additional RO, the PRACH opportunity for retransmission is the additional RO.

[0591] In O150-25, the UE starts the RA (Random Access) window and monitors the PDCCH to receive the RAR (Random Access Response).

[0592] After the PRACH (preamble) transmission, the UE attempts to detect the CRC-scrambed DCI format 1_0 with the corresponding RA-RNTI during the RAR window.

[0593] The UE monitors the PDCCH to detect DCI, and monitors the PDCCH based on specific resources in the initial downlink resource pool while the RAR window is running. These specific resources are determined by a specific SearchSpace.

[0595] For the random access procedure of a serving cell in an FDD system, the UE performs the following:

[0596] >: Perform a preamble transmission to a resource in the first frequency domain (NUL of the basic uplink BWP) or perform a preamble transmission to a resource in the fourth frequency domain (SUL of the basic uplink BWP); and

[0597] >: Perform RAR reception from the resources of the third frequency domain (initial downlink BWP).

[0599] In the FDD system:

[0600] The first frequency range is determined based on the following:

[0601] >>: First reference resource block (PointA for the normal uplink of the serving cell; determined based on the absoluteFrequencyPointA field within FrequencyInfoUL-SIB IE within the uplinkConfigCommon field);

[0602] >>: Offset from the first reference resource block to the normal uplink carrier (determined based on the offsetToCarrier field within a specific SCS-SpecificCarrier);

[0603] >>: Location and bandwidth of the first frequency domain (determined based on the locationAndBandwidth field within the initial uplink BWP field).

[0605] The fourth frequency domain is determined based on the following:

[0606] >>: Second reference resource block (PointA for the supplementary uplink of the serving cell; determined based on the absoluteFrequencyPointA field of FrequencyInfoUL-SIB IE within the supplementaryUplink field);

[0607] >>: Offset from the second reference resource block to the secondary uplink carrier (determined based on the offsetToCarrier field within a specific SCS-SpecificCarrier);

[0608] >>: Location and bandwidth of the fourth frequency domain (determined based on the locationAndBandwidth field of the initialUplinkBWP field within the auxiliary uplink field).

[0609] The third frequency range is determined based on the following:

[0610] >>: Third reference resource block (PointA for the downlink of the serving cell; determined based on the offsetToPointA field of FrequencyInfoDL-SIB IE within the downlinkConfigCommon field);

[0611] >>: Offset from the third reference resource block to the downlink carrier (determined based on the offsetToCarrier field within a specific SCS-SpecificCarrier);

[0612] >>: Location and bandwidth of the third frequency domain (determined based on the locationAndBandwidth field within the initial downlink BWP field).

[0614] In a TDD system, for the random access procedure of a serving cell, the UE performs the following:

[0615] Resource performing preamble transfer:

[0616] >>: First frequency range (NUL of the basic uplink BWP);

[0617] >>: Fourth frequency range (SUL of the basic uplink BWP); or

[0618] >>: Second frequency range (SBFD's NUL);

[0619] >: Perform RAR reception from the resources of the third frequency domain (initial downlink BWP).

[0621] In a TDD system, the first frequency domain is determined based on the following:

[0622] >>: First reference resource block (PointA for the normal uplink of the serving cell; determined based on the absoluteFrequencyPointA field of FrequencyInfoDL-SIB IE within the downlinkConfigCommon field);

[0623] >>: Offset from the first reference resource block to the normal uplink carrier (determined based on the offsetToCarrier field within a specific SCS-SpecificCarrier);

[0624] >>: Location and bandwidth of the first frequency domain (determined based on the locationAndBandwidth field within the initial uplink BWP field).

[0626] The fourth frequency domain is determined based on the following:

[0627] >>: Second reference resource block (PointA for the supplementary uplink of the serving cell; determined based on the absoluteFrequencyPointA field of FrequencyInfoUL-SIB IE within the supplementaryUplink field);

[0628] >>: Offset from the second reference resource block to the secondary uplink carrier (determined based on the offsetToCarrier field within a specific SCS-SpecificCarrier);

[0629] >>: Location and bandwidth of the fourth frequency domain (determined based on the locationAndBandwidth field within the initial uplink BWP field).

[0631] The third frequency range is determined based on the following:

[0632] >>: First reference resource block (Point A for the downlink of the serving cell; determined based on the offsetToPointA field of FrequencyInfoDL-SIB IE within the downlinkConfigCommon field);

[0633] >>: Offset from the third reference resource block to the downlink carrier (determined based on the offsetToCarrier field within a specific SCS-SpecificCarrier);

[0634] >>: Location and bandwidth of the third frequency domain (determined based on the locationAndBandwidth field within the initial downlink BWP field).

[0635] The second frequency range is determined based on the following:

[0636] >>: Offset from the first reference resource block to the normal uplink carrier (determined based on the offsetToCarrier field within a specific SCS-SpecificCarrier); and

[0637] >>: Offset between the lowest subcarrier of the normal uplink carrier and the lowest subcarrier of the second frequency region; and

[0638] >>: Bandwidth of the second frequency range.

[0640] For example, the first PRB and the number of PRBs in each frequency range are determined at the corresponding locationAndBandwidth. The location of the first PRB in each frequency range is determined at the corresponding offsetToCarrier and the corresponding absoluteFrequencyPointA.

[0642] The UE receives Msg2 / RAR (S150-30).

[0643] The UE performs a PUSCH transmission for Msg 3 (S150-35).

[0644] The UE receives Msg4 for contention resolution (S150-40).

[0645] The UE sends a HARQ ACK for Msg4 (S150-45).

[0647] The UE indirectly determines the SCS of the first frequency region based on the subcarrier spacing field within the IE for the third frequency region.

[0648] The UE directly determines the SCS of the second frequency domain based on a specific field (subcarrier spacing field or other field) within the downlink carrier-specific IE associated with the second frequency domain.

[0650] Figure 17 shows an example in the frequency domain.

[0651] The first frequency range (E1000), the second frequency range (E1100), the third frequency range (E1200), and the fourth frequency range (E1300) are configured based on the corresponding parameters.

[0653] The UE performs the following to send a preamble and receive a response:

[0654] The UE receives the SSB from the cell;

[0655] The UE receives system information from the cell;

[0656] The UE triggers random access in the cell;

[0657] The UE transmits a preamble from the cell for random access; and

[0658] The UE receives a response to the preamble from the cell.

[0660] The preamble is transmitted from the first frequency resource (the resource of the NUL of the basic uplink BWP), the second frequency resource (SBFD), or the fourth frequency resource (the resource of the SUL of the basic uplink BWP).

[0661] The response to the preamble is received from a third frequency source.

[0662] Here:

[0663] The first frequency resource belongs to the first frequency range [NUL of the basic uplink BWP];

[0664] The second frequency resource belongs to the second frequency domain [SBFD];

[0665] The third frequency resource belongs to the third frequency domain [initial downlink BWP];

[0666] The fourth frequency resource belongs to the fourth frequency range [SUL of the basic uplink BWP].

[0668] Here:

[0669] The first, second, and fourth frequency domains are for uplink transmission;

[0670] The third frequency range is for downlink reception.

[0672] The UE transmits a preamble at the fourth frequency resource when the RSRP of the downlink path loss reference is less than a specific threshold [rsrp - ThresholdSSB - SUL].

[0673] The UE transmits a preamble from the first frequency resource when the RSRP of the downlink path loss reference (downlink reference signal, e.g., SSB) is greater than or equal to a specific threshold, and also transmits it even if the parameters for the second frequency domain are not included in the set of parameters for the downlink configuration.

[0675] The UE performs the following procedures to transmit the preamble and receive the response:

[0676] The UE receives system information, and this system information includes various information elements (IE);

[0677] The UE triggers a random access (RA) procedure;

[0678] The UE determines the set of RA resources based on the availability of one or more functions; and

[0679] The UE performs the RA procedure based on the selected set of RA resources.

[0681] Here, the RA resource set is when the system information includes the following:

[0682] >: Offset parameter [OffsetToSbfd] for the second frequency domain within IE for downlink configuration; and

[0683] IE[sbfd-RACH-Config] for RA for the second frequency domain within IE for uplink configuration,

[0684] The first set of ROs is determined based on the following:

[0685] >: First frequency range;

[0686] >: First time domain;

[0687] >: Parameter for start frequency [msg1-frequencyStart] within RA General Configuration [RACH-ConfigGeneric]; and

[0688] Frequency Division Multiplexing (FDD) parameters [FDMed] within the general RA configuration;

[0690] The second RO set is determined based on the following:

[0691] >: Second frequency range;

[0692] >: Second time domain;

[0693] >: Parameter for the starting frequency within RA for the second frequency domain; and

[0694] >: Parameters for FDD within RA for the second frequency domain.

[0695] The first frequency range is determined based on the following:

[0696] >: IE for the first frequency domain within the IE for the uplink configuration; and

[0697] >: Offset parameter for uplink carrier within IE for uplink configuration; and

[0698] >: Offset parameter for the reference resource block within IE for downlink configuration.

[0700] The second frequency range is determined based on the following:

[0701] >: Offset parameter for the second frequency domain within IE for downlink configuration;

[0702] >: Parameter for the bandwidth of the second frequency domain within IE for downlink configuration;

[0703] >: Offset parameter for downlink carrier within IE for downlink configuration; and

[0704] >: Offset parameter for the reference resource block within IE for downlink configuration.

[0706] The first time domain is determined based on the following:

[0707] >: Parameters for the PRACH configuration index within IE for RA general configuration; and

[0708] >: one or more first symbols;

[0710] The second time domain is determined based on the following:

[0711] >: Parameters for the PRACH configuration index within RA for the second frequency domain; and

[0712] >: One or more second symbols.

[0714] One or more first symbols include the following:

[0715] One or more downlink symbols determined based on IE for the TDD uplink-downlink configuration; and

[0716] One or more flexible symbols determined based on IE for the TDD uplink-downlink configuration.

[0718] The second symbol is the following symbol:

[0719] >: Determined based on the parameter [offsetToFirstSBSymbol] for the subband time domain within IE for the TDD uplink-downlink configuration; and

[0720] >: Not the first symbol (to ensure that the first time domain takes precedence in the event of a conflict between the first and second time domains).

[0722] System information includes the following:

[0723] >: Set of parameters for downlink configuration;

[0724] >: Set of parameters for uplink configuration;

[0725] >: Set of parameters for auxiliary uplink configuration; and

[0726] >: Set of parameters for TDD uplink-downlink configuration.

[0728] The parameter set and IE are used interchangeably.

[0730] **DownlinkConfigCommonSIB**

[0731] The parameter set [DownlinkConfigCommonSIB] for downlink configuration includes the following:

[0732] >: Parameter set for the third frequency domain [initial downlink bandwidth portion];

[0733] >: Offset parameter [offsetToPointA] for the reference resource block; and

[0734] >: One or more downlink carrier-specific parameter sets.

[0736] **UplinkConfigCommonSIB**

[0737] The parameter set [UplinkConfigCommonSIB] for uplink configuration includes the following:

[0738] >: Parameter set for the first frequency domain [initial uplink bandwidth portion];

[0739] >: One or more uplink carrier-specific parameter sets.

[0741] The **set of parameters for the auxiliary uplink configuration** includes the following:

[0742] >: Parameter set for the fourth frequency domain;

[0743] >: Parameters for the reference resource block [absoluteFrequencyPointA]; and

[0744] >: One or more uplink carrier-specific parameter sets.

[0746] **Carrier Specific Parameters**

[0747] One or more sets of downlink carrier-specific parameters include the following:

[0748] >: Offset parameter for downlink carrier;

[0749] >: Parameter for the subcarrier spacing of the downlink carrier;

[0750] >: Parameter for downlink carrier bandwidth.

[0752] One or more uplink carrier-specific parameter sets include the following:

[0753] >: Offset parameter for uplink carrier;

[0754] >: Parameter for the subcarrier spacing of the uplink carrier;

[0755] >: Parameter for uplink carrier bandwidth.

[0756] ### Frequency Domain

[0758] The parameter set for the third frequency domain [initial downlink BWP] includes the following:

[0759] >: Parameter indicating the position and bandwidth of the third frequency range;

[0760] >: Parameter representing the subcarrier spacing in the third frequency domain.

[0762] ### Initial DL BWP

[0764] The third frequency domain [initial downlink bandwidth portion] is determined based on the following:

[0765] >: Set of parameters for the third frequency domain;

[0766] >: Offset parameter for the reference resource block; and

[0767] >: Specific downlink carrier specific parameter set.

[0769] The following are identical:

[0770] >: Subcarrier interval indicated by a specific downlink carrier specific parameter set; and

[0771] >: Subcarrier spacing indicated by the parameter set for the third frequency domain.

[0773] ### Initial UL BWP in NUL

[0775] The first frequency range [NUL of the basic uplink BWP] is determined based on the following:

[0776] >: Set of parameters for the first frequency domain;

[0777] >: Offset parameter for the reference resource block; and

[0778] A specific uplink carrier-specific parameter set within the parameter set for the uplink configuration.

[0780] The following are identical:

[0781] >: Subcarrier interval indicated by a specific uplink carrier-specific parameter set within a parameter set for uplink configuration; and

[0782] >: Subcarrier spacing indicated by the parameter set for the first frequency domain.

[0784] ### Initial UL BWP in SUL

[0786] The fourth frequency domain [SUL of the basic uplink BWP] is determined based on the following:

[0787] >: Parameter set for the fourth frequency domain [BWP];

[0788] >: Parameters for the reference resource block; and

[0789] A specific uplink carrier-specific parameter set within the parameter set for the auxiliary uplink configuration.

[0791] The following are identical:

[0792] >: Subcarrier interval indicated by a specific uplink carrier-specific parameter within the parameter set for the auxiliary uplink configuration; and

[0793] >: Subcarrier spacing indicated by the parameter set for the fourth frequency domain.

[0795] ### SBFD

[0797] The second frequency domain [SBFD frequency domain] is determined based on the following:

[0798] >: Offset parameter for reference resource block;

[0799] >: Offset parameter for downlink carrier;

[0800] >: Offset parameter for the second frequency domain; and

[0801] >: Parameter for the bandwidth of the second frequency range.

[0803] The second frequency domain includes n consecutive PRBs starting from a specific PRB;

[0804] A specific PRB is determined based on the following:

[0805] >: Offset parameter for the second frequency domain; and

[0806] >: Offset parameter for the reference resource block.

[0808] n is determined based on the parameter for the bandwidth of the second frequency domain.

[0810] The items included in a specific downlink carrier specific parameter set are as follows:

[0811] >: Offset parameter for the second frequency range;

[0812] >: Parameters for the bandwidth of the second frequency domain; and

[0813] >: Offset parameter for downlink carrier.

[0815] The subcarrier interval indicated by a specific downlink carrier specific parameter set is applied to the uplink transmission (Msg3 transmission).

[0816] ### Common Parameters

[0818] The offset parameter for the reference resource block is commonly used to determine the third frequency range, the first frequency range, and the second frequency range.

[0819] Offset parameters for a downlink carrier within a specific set of downlink carrier parameters are commonly used to determine the downlink carrier and the second frequency region.

[0820] Parameters for the subcarrier spacing within a specific set of downlink carrier parameters are generally used to determine the subcarrier spacing of the downlink carrier and the subcarrier spacing of the second frequency domain.

[0822] ### SIB1 Version 2

[0824] System information includes the following:

[0825] IE for downlink configuration;

[0826] >: IE for uplink configuration; and

[0827] IE for TDD uplink-downlink configuration.

[0829] **DownlinkConfigCommonSIB**

[0830] IE for downlink configuration includes the following:

[0831] >: IE[Initial Downlink BWP] for the third frequency range;

[0832] >: Offset parameter for reference resource block [offsetToPointA];

[0833] >: Offset parameter for downlink carrier [offsetToCarrier]; and

[0834] >: Offset parameter for the second frequency range.

[0836] **UplinkConfigCommon / RACH-ConfigCommon**

[0837] IE for uplink configuration includes the following:

[0838] >: IE[Initial Uplink BWP] for the first frequency range; and

[0839] >: Offset parameter for uplink carrier.

[0841] The IE for the first frequency domain includes the following:

[0842] >: Parameters for SCS; and

[0843] One or more IEs for Random Access Channel (RACH) configuration;

[0845] Each RACH configuration IE[RACH-ConfigCommon] includes the following:

[0846] IE for RA general configuration;

[0847] >: IE for RA for the second frequency domain; and

[0848] One or more IE for function combination preambles.

[0850] IE for the general RA configuration includes the following:

[0851] >: Parameters for the start frequency; and

[0852] >: Parameters for the PRACH configuration index.

[0854] The IE for RA in the second frequency domain includes the following:

[0855] >: Parameters for the start frequency; and

[0856] >: Parameters for the PRACH configuration index.

[0858] The parameter for the starting frequency in IE for the general RA configuration represents the number of PRBs indicated by SCS in IE for the first frequency range.

[0859] The parameter for the starting frequency in IE for RA for the second frequency range represents the number of PRBs in the fourth frequency range.

[0861] ### Other Matters

[0863] The first RO of the second RO set is located at a specific frequency point [the first FDMed LO].

[0864] A specific frequency point is located above the lowest PRB [first reference point] of the SBFD by an amount indicated by the parameter for the starting frequency within the RA for the second frequency range.

[0865] The first reference point is located upward from the lowest PRB [second reference point] of the downlink carrier, and this is located by an amount indicated by the offset parameter for the second frequency domain within the IE for the downlink configuration.

[0866] The second reference point is located upward from the reference resource block [PointA], and is located by the amount indicated by the offset parameter [offsetToCarrier] for the downlink carrier within IE for the downlink configuration.

[0867] The third reference point is located downward from the lowest subcarrier [fourth reference point] of the SSB, and is located by the amount indicated by the offset parameter [offsetToPointA] for the reference resource block within IE for the downlink configuration.

[0868] The fourth reference point is the lowest subcarrier of the SSB.

[0870] If the RA resource set is configured in both the first and second frequency domains, the base station requires a means to distribute the RA load across the frequency domains. Legacy UEs that do not understand SBFD / the second frequency domain perform RA procedures in the default frequency domain. SBFD UEs can perform RA procedures in the second frequency domain by default. For finer control, a new parameter can be considered. This new parameter indicates whether the SBFD UE can perform RA procedures (even when RA procedures are possible in the second RA domain) and represents the probability of selecting the first frequency domain.

[0871] The UE performs the following to select an RA resource set:

[0872] The UE receives system information, and this system information includes various information elements (IE);

[0873] The UE triggers a random access (RA) procedure;

[0874] The UE determines the first set of functions applicable to the RA procedure;

[0875] The UE determines the RA resource set based on the availability of the third set of functions; and

[0876] The UE performs the RA procedure based on the selected set of RA resources.

[0878] If a set of RA resources unrelated to any function is available for a function applicable to the RA procedure (second set of functions), the set of RA resources unrelated to the function is selected.

[0880] The UE determines that a specific set of RA resources unrelated to the function is selected based on a specific parameter [SbfdSelection]. In this case:

[0881] >: When the RA resource set is unavailable for any function applicable to the RA procedure; and

[0882] >: If a set of RA resources unrelated to the function is available in the first frequency domain; and

[0883] >: When a set of RA resources unrelated to the function is available in the second frequency domain.

[0885] The first set of functions for RA includes msg3-Repetition and / or msg1-Repetition determined to be applicable based on the RSRP of the downlink path loss reference.

[0886] The second set of functions includes one or more NSAG-IDs applicable to RA by the upper layer.

[0887] The third function set is the union of the first function set and the second function set.

[0889] The UE determines whether the msg3-Repetition function is applicable as follows:

[0890] >: Applicable to RA procedures:

[0891] >>: One or more sets of RA resources are available with msg3-Repetition set to true for the first or second frequency domain;

[0892] >>: If the RSRP of the downlink path loss reference is lower than rsrp-ThresholdMsg3;

[0893] Cases not applicable to RA procedures:

[0894] >>: One or more sets of RA resources are available with msg3-Repetition set to true for the first or second frequency domain;

[0895] >>: If the RSRP of the downlink path loss reference is higher than rsrp-ThresholdMsg3;

[0896] Cases not applicable to RA procedures:

[0897] >>: If there is no set of RA resources with msg3-Repetition set to true for the first or second frequency range.

[0899] The UE determines whether the msg1-Repetition function is applicable as follows:

[0900] >: Applicable to RA procedures:

[0901] >>: All RA resource sets in the first frequency domain have msg1-Repetitions set to true and;

[0902] >>: If all RA resource sets in the second frequency domain have msg1-Repetitions set to true;

[0903] Cases not applicable to RA procedures:

[0904] >>: No RA resource set in the first frequency domain has msg1-Repetitions set to true;

[0905] >>: If any RA resource set in the second frequency domain does not have msg1-Repetitions set to true;

[0906] >: Applicable to RA procedures:

[0907] >>: One or more sets of RA resources in the first frequency domain have msg1-Repetitions set to true, or one or more sets of RA resources in the second frequency domain have msg1-Repetitions set to true, and;

[0908] >>: If the RSRP of the downlink path loss reference is lower than at least one of rsrp-ThresholdMsg1-RepetitionNumX;

[0909] Cases not applicable to RA procedures:

[0910] >>: One or more sets of RA resources in the first frequency domain have msg1-Repetitions set to true, or one or more sets of RA resources in the second frequency domain have msg1-Repetitions set to true, and;

[0911] >>: When the RSRP of the downlink path loss reference is higher than rsrp-ThresholdMsg1-RepetitionNumX.

[0912] ### SbfdSelection

[0913] >: **SbfdSelection**:

[0914] >>: Represents the probability of selecting a set of RA resources for a specific set of features. In this case, if a set of RA resources representing the same set of features is available in both the first and second frequency domains;

[0915] >>: Includes the initial uplink BWP field (or within IE); and

[0916] >>: Represents an integer between the lowest value (1) and the highest value (100).

[0918] UE selects a random number between the lowest and highest values;

[0919] The UE selects the RA resource set:

[0920] >>: If the random number is less than or equal to an integer, in the first frequency domain; and

[0921] >>: In the second frequency domain if the random number is greater than an integer or if SbfdSelection is not included in the initial uplink BWP field.

[0923] >: **SbfdSelection**:

[0924] >>: Includes the initial uplink BWP field (or within IE); and

[0925] >>: Enumerated as a single value indicating activation;

[0927] The UE selects the RA resource set:

[0928] >>: If SbfdSelection exists in the initial uplink BWP field (or within that IE), with equal probability in both the second and first frequency domains;

[0929] >>: If SbfdSelection does not exist in the initial uplink BWP field (or within IE), in the second frequency domain.

[0931] The default RO, non-SBFD RO, and first RO are used interchangeably.

[0932] Additional RO, SBFD RO, and second RO are used interchangeably.

[0934] ### RAR format

[0935] RAR is described below. RAR is included within the MAC PDU (F100).

[0936] A MAC PDU for RAR contains one or more MAC subPDUs and optionally padding. Each MAC subPDU consists of one of the following:

[0937] MAC subheader containing only the Backoff Indicator;

[0938] >: MAC subheader containing only RAPID (i.e., confirmation for SI request);

[0939] MAC subheader containing RAPID and MAC RAR.

[0941] A MAC subPDU (F110) containing only a Backoff Indicator is placed at the beginning of the MAC PDU (if included).

[0942] 'MAC subPDU containing only RAPID' and 'MAC subPDU containing RAPID and MAC RAR' can be placed anywhere between the MAC subPDU containing only the Backoff Indicator (if any) and the padding (if any).

[0944] The MAC subheader (F120) containing RAPID consists of three header fields: E / T / RAPID.

[0945] MAC RAR(F130) has a fixed size and includes the following fields:

[0946] >: R: Reserved bit, set to 0;

[0947] Timing Advance Command: The Timing Advance Command field represents an index value TA used to control the amount of timing adjustments that the MAC entity must apply in TS 38.213 [6]. The size of the Timing Advance Command field is 12 bits;

[0948] >: UL Grant: The Uplink Grant field indicates the resources to be used for the uplink in TS 38.213 [6]. The size of the UL Grant field is 27 bits;

[0949] >: Temporary C-RNTI: The Temporary C-RNTI field represents a temporary ID used by the MAC entity during random access. The size of the Temporary C-RNTI field is 16 bits.

[0951] ### UL Grant

[0952] The UL Grant (F140) includes the following fields:

[0953] >: Frequency hopping flag (FH);

[0954] PUSCH Frequency Resource Allocation (FRA);

[0955] PUSCH time resource allocation (TRA);

[0956] >: MCS;

[0957] >: TPC command for PUSCH; and

[0958] >: CSI request.

[0960] The value m of the TAR field of RAR UL Grant provides / indicates row index m + 1 for the resource allocation table. The resource allocation table becomes the Default A table if pusch-TimeDomainAllocationList is provided within pusch-ConfigCommon or if it is not provided within the pusch-ConfigCommon of the selected uplink carrier.

[0961] **pusch-TimeDomainAllocationList** consists of one or more **pusch-TimeDomainAllocation** IEs. Each **pusch-TimeDomainAllocation** includes the following fields:

[0963] *>: **k2** field: Indicates the time domain offset between the UL Grant and the PUSCH transmission. If this field is missing, the UE applies a value of 1 if the PUSCH SCS is 15 / 30 kHz, a value of 2 if the PUSCH SCS is 60 kHz, and a value of 3 if the PUSCH SCS is 120 kHz;

[0964] >: **mappingType** field: indicates one of typeA or typeB;

[0965] >: **startSymbolAndLength**: An index (combined encoded) providing a valid combination of start symbol and length, used as a start and length indicator (SLIV).

[0967] The first **pusch-TimeDomainAllocation** corresponds to row index 1, the second to row index 2, and so on.

[0968] The indexed row defines the slot offset K2, start symbol S, allocation length L, and PUSCH mapping type, and defines the number of slots used for TBS determination (if numberOfSlotsTBoMS exists in the resource allocation table).

[0969] Table 1 below shows the Default A table. j is a variable determined by the PUSCH SCS.

[0970] Row index PUSCH mapping type K 2 S L 1 Type A j 0 14 2 Type A j 0 12 3 Type A j 0 10 4 Type B j 2 10 5 Type B j 4 10 6 Type B j 4 8 7 Type B j 4 6 8 Type A j +1 14 9 Type A j +1 12 10 Type A j +1 10 11 Type A j +2 14 12 Type A j +2 12 13 Type A j +2 10 14 Type B j 8 6 15 Type A j +3 14 16 Type A j +3 10

[0971] PUSCH SCS j 15 KHz 1 30 KHz 1 60 KHz 2 120 KHz 3 240 KHz 11 480 KHz 21

[0972] The **FRA field** represents a set of non-interfering virtual resource blocks allocated contiguously within the first or second frequency domain. The FRA field consists of a starting virtual resource block (RB_start) and a Resource Indication Value (RIV) corresponding to the length L_RBs of the contiguously allocated resource blocks. The RIV is defined as follows: If (L_RBs ? 1) is less than or equal to floor(N_frequencyRegion_size / 2), the RIV is equal to N_frequencyRegion_size * (L_RBs ? 1) + RB_start;

[0973] If (L_RBs ? 1) is greater than floor(N_frequencyRegion_size / 2), then the RIV is equal to N_frequencyRegion_size * (N_frequencyRegion_size - L_RBs + 1) + (N_frequencyRegion_size ? 1 - RB_start).

[0975] N_frequencyRegion_size is the number of RBs in a specific frequency range.

[0976] After the random access preamble is transmitted, the UE starts ra-ResponseWindow regardless of whether the measurement interval occurs.

[0977] The UE monitors the SpCell's PDCCH to receive a random access response (RAR) identified as RA-RNTI while ra-ResponseWindow is running.

[0978] The UE monitors different RA-RNTIs depending on the frequency domain in which the preamble is transmitted. If the preamble is transmitted in the first frequency domain in relation to RAR, the UE monitors the first RA-RNTI for RAR reception. If the preamble is transmitted in the second frequency domain in relation to RAR, the UE monitors the second RA-RNTI for RAR reception. The first RA-RNTI and the second RA-RNTI are different, the first RA-RNTI belongs to the first set of RA-RNTIs, and the second RA-RNTI belongs to the second set of RA-RNTIs.

[0979] Each RA-RNTI in the first set of RA-RNTIs is associated with the base RO. Each RA-RNTI in the second set of RA-RNTIs is associated with the SBFD RO.

[0981] Depending on the case:

[0982] >>: A valid downlink assignment for RA-RNTI was received from PDCCH and the received TB was successfully decoded; and

[0983] >>: If the random access response includes a MAC subPDU containing a random access preamble identifier corresponding to the transmitted preamble,

[0984] >: UE performs the following:

[0985] >>: Processes received timing advance commands;

[0986] >>: Determines the uplink transmission power based on preambleReceivedTargetPower and the power ramping amount applied to the latest random access preamble transmission ((PREAMBLE_POWER_RAMPING_COUNTER ? 1) × PREAMBLE_POWER_RAMPING_STEP); and

[0987] >>: RAR determines time domain resources and frequency domain resources for PUSCH transmission based on UL Grant.

[0989] In S150-35, the UE performs the following for a PUSCH transmission. The UE determines the time domain resource and the frequency domain resource based on the contents of the UL Grant and the frequency domain in which the preamble was transmitted. The UE performs the PUSCH transmission in the first frequency domain or the second frequency domain based on the determination.

[0991] For frequency domain determination, the UE performs the following.

[0992] If the TRA field of the UL Grant indicates the following:

[0993] >>: If the first symbol of the PUSCH transmission occurs during the SBFD duration (i.e., the SBFD symbol);

[0994] >>: If the entire PUSCH transmission period occurs during the SBFD duration (i.e., SBFD symbol); or

[0995] >>: If part of the PUSCH transmission period occurs during the SBFD duration (i.e., SBFD symbol),

[0996] The UE determines that PUSCH transmission will be performed in the second frequency domain (E700).

[0998] If the TRA field of the UL Grant indicates the following:

[0999] >>: If the first symbol of the PUSCH transmission occurs during a non-SBFD persistence (i.e., a flexible symbol or an uplink symbol); or

[1000] >>: When the entire PUSCH transmission period occurs during a non-SBFD duration (i.e., flexible symbol or uplink symbol);

[1001] >>: If part of the PUSCH transmission period occurs during a non-SBFD duration (i.e., flexible symbol or uplink symbol),

[1002] The UE determines that the PUSCH transmission will be performed in the first frequency domain (E800).

[1003] ### Non-SBFD duration

[1004] A non-SBFD duration is a time period that is not an SBFD duration;

[1005] >: Consists of the following:

[1006] >>: Uplink symbol according to the first part of TDD-UL-DL-ConfigurationCommon;

[1007] >>: A set of symbols considered as flexible symbols according to the first part of TDD-UL-DL-ConfigurationCommon and not SBFD symbols according to the second part of TDD-UL-DL-ConfigurationCommon; and

[1008] >>: A set of symbols considered as uplink symbols according to the first part of TDD-UL-DL-ConfigurationCommon, and not SBFD symbols according to the second part of TDD-UL-DL-ConfigurationCommon;

[1009] Non-SBFD duration is present in both Pattern 1 and Pattern 2.

[1011] ### SBFD duration

[1012] The SBFD duration consists of the following:

[1013] >>: A set of symbols that are considered flexible symbols according to the first part of TDD-UL-DL-ConfigurationCommon and are SBFD symbols according to the second part of TDD-UL-DL-ConfigurationCommon; and

[1014] >>: A set of symbols considered as downlink symbols according to the first part of TDD-UL-DL-ConfigurationCommon and SBFD symbols according to the second part of TDD-UL-DL-ConfigurationCommon;

[1015] The SBFD duration exists in either Pattern 1 or Pattern 2.

[1017] ### PUSCH transmission

[1018] A PUSCH transmission is performed in a sequence of symbols. The PUSCH transmission period is the set of symbols in which the PUSCH transmission occurs.

[1019] The UE determines the start slot of the PUSCH transmission period (e.g., the UE determines the frequency domain) based on the following:

[1020] When the PUSCH SCS determines whether the PUSCH period is included in the time-domain resources of the initial uplink BWP using K2 (or j) determined for the first frequency domain (e.g., whether the TRA represents an uplink symbol or a flexible symbol); and

[1021] When determining whether the PUSCH period is included in the SBFD duration using K2 (or j) determined for the second frequency domain in the PUSCH SCS (e.g., whether the TRA represents the SBFD symbol).

[1023] Alternatively, the UE performs frequency resource determination by doing the following.

[1024] The UE performs PUSCH transmission in the second frequency domain in the following cases:

[1025] >: When preamble transmission is performed in the second frequency domain; and

[1026] If puschSbfdAllowed (indicated by 1 bit) is included in uplinkConfigCommon of system information.

[1028] The UE performs PUSCH transmission in the first frequency domain in the following cases:

[1029] >: If preamble transmission is performed in the first frequency domain; or

[1030] If puschSbfdAllowed (indicated by 1 bit) is not included in uplinkConfigCommon of system information.

[1032] The UE determines the PRB for PUSCH transmission based on the FRA and the determined frequency range.

[1033] If the first frequency domain is selected for PUSCH transmission, the UE determines the set of contiguously allocated resource blocks of the first frequency domain based on the following:

[1034] >: N_frequencyRegion_size of the first frequency region; and

[1035] UL Grant's FRA.

[1037] If the second frequency domain is selected for PUSCH transmission, the UE determines the set of contiguously allocated resource blocks in the second frequency domain based on the following:

[1038] >: N_frequencyRegion_size of the second frequency region; and

[1039] UL Grant's FRA.

[1041] The UE performs a PUSCH transmission based on the above decision.

[1042] When the UE receives Msg4 for contention resolution in S150-40, the UE performs the following:

[1043] After Msg3 is sent, the UE performs the following:

[1044] Start or restart ra-ContentionResolutionTimer at the first symbol after Msg3 transmission is finished;

[1045] >: Monitors PDCCH while ra-ContentionResolutionTimer is running, regardless of whether the measurement interval occurs.

[1047] Depending on the case:

[1048] >>: SpCell's PDCCH transmission reception notification is received from the lower layer;

[1049] >>: MAC PDU is successfully decoded;

[1050] >>: The MAC PDU contains the UE contention resolution identifier MAC CE; and

[1051] >>: The UE contention resolution identifier in MAC CE matches the CCCH SDU sent in Msg3,

[1052] The UE stops ra-ContentionResolutionTimer and considers this random access procedure to have been successfully completed.

[1054] To send a HARQ ACK for Msg4 in S150-45, the UE performs the following.

[1055] In response to a PUSCH transmission scheduled by a RAR UL Grant while the UE has not been provided with a C-RNTI, the UE attempts to detect DCI format 1_0 scheduling a PDSCH containing a UE contention resolution identifier. In response to the reception of the PDSCH containing the UE contention resolution identifier, the UE transmits HARQ-ACK information in the PUCCH. The PUCCH transmission is performed within the first frequency resource (if the PUSCH and / or preamble was transmitted in the first frequency domain), or within the second frequency resource (if the PUSCH and / or preamble was transmitted in the second frequency domain and a second set of parameters for the PUCCH resource for the second frequency domain is provided in the system information).

[1057] The UE performs HARQ-ACK transmission in the first frequency domain based on the following:

[1058] >: First parameter set for PUCCH resource;

[1059] >: Second parameter set for PUCCH resources for the first frequency domain;

[1060] >: Uplink carrier-specific parameter set; and

[1061] >: Set of parameters for the first frequency domain.

[1063] The UE performs HARQ-ACK transmission in the second frequency domain based on the following:

[1064] >: First parameter set for PUCCH resource;

[1065] >: Second parameter set for PUCCH resources for the second frequency domain;

[1066] >: Downlink carrier specific parameter set; and

[1067] >: Set of parameters for the second frequency domain.

[1069] The first set of parameters for the PUCCH resource and the second set of parameters for the PUCCH resource for the first frequency domain are included in a single IE.

[1070] The second set of parameters for the PUCCH resource for the second frequency domain is included in a single IE or another IE (e.g., IE for the SBFD RA configuration).

[1072] The first set of parameters for the PUCCH resource is applied to HARQ ACK transmission in the first frequency domain and the second frequency domain.

[1073] The second set of parameters for the first frequency domain for the PUCCH resource is applied to the HARQ ACK transmission in the first frequency domain.

[1074] The second set of parameters for the PUCCH resource for the second frequency domain is applied to the HARQ ACK transmission in the second frequency domain.

[1076] The parameter set for the PUCCH resource for the second frequency domain includes the following:

[1077] >: pucch-ResourceCommon field; and

[1078] >: nrofPRBs field.

[1079] ### First parameter set for the PUCCH resource

[1081] The first set of parameters for the PUCCH resource includes the following:

[1082] >: **p0-nominal** field; and

[1083] >: **pucch-GroupHopping** field.

[1085] The **pucch-GroupHopping** field indicates the configuration of group and sequence hopping for all PUCCH types 0, 1, 3, and 4. The value 'neither' means that neither group hopping nor sequence hopping is enabled. The value 'enable' enables group hopping and disables sequence hopping. The value 'disable' disables group hopping and enables sequence hopping.

[1086] The **p0-nominal** field provides the power control parameter P0 for PUCCH transmission.

[1087] The **nrofPRBs** field indicates the number of PRBs used per PUCCH resource for PUCCH format 0 (TS 38.213, Klaus 9.2.1).

[1088] The **pucch-ResourceCommon** field represents an entry for a 16-row table where each row constitutes a cell-specific PUCCH resource / parameter (TS 38.213, Klaus 9.2). Each entry is associated with the PUCCH format, time resource, and the start PRB of the frequency resource.

[1090] ### RAR reception

[1092] RAR is received in the second frequency range.

[1093] Receiving RAR is essential for completing the random access procedure. Since the PRACH preamble can be transmitted in either the first or second frequency domain, a means is required to determine whether the RAR is intended for transmitting the PRACH preamble in the first frequency domain or the second frequency domain.

[1095] The UE performs the following to receive RAR:

[1096] The UE receives system information, and this system information includes various information elements (IE);

[1097] The UE triggers a random access (RA) procedure;

[1098] The UE transmits a PRACH preamble to the first frequency domain in the first RO or to the second frequency domain in the second RO;

[1099] The UE monitors the PDCCH of a specific RA-RNTI in the third frequency range for a specific period;

[1100] The UE receives a RAR containing a MAC subPDU containing a random access preamble identifier corresponding to the transmitted preamble; and

[1101] The UE performs a PUSCH transmission based on the RAR's UL Grant.

[1103] A specific RA-RNTI is selected as follows:

[1104] >: In the first set of RA-RNTI where the PRACH preamble is transmitted in the first frequency domain; and

[1105] In the second RA-RNTI set, when the PRACH preamble is transmitted in the second frequency domain.

[1107] If the PRACH preamble is transmitted in the first frequency domain, a specific RA-RNTI is determined based on the following:

[1108] >: Parameter for the start frequency within IE for the general RA configuration;

[1109] >: SCS-SpecificCarrier of Uplink Configuration;

[1110] >: Parameters for the PRACH configuration index within IE for RA general configuration;

[1111] >: The first TDD-UL-DL-Pattern IE within tdd-UL-DL-ConfigCommon; and

[1112] >: The second TDD-UL-DL-Pattern IE within tdd-UL-DL-ConfigCommon.

[1114] If the PRACH preamble is transmitted in the second frequency domain, a specific RA-RNTI is determined based on the following:

[1115] >: Parameter for the starting frequency within RA for the second frequency domain;

[1116] >: SCS-SpecificCarrier of Downlink Configuration;

[1117] >: Parameter for the PRACH configuration index within RA for the second frequency domain;

[1118] >: The first TDD-UL-DL-Pattern IE or the second TDD-UL-DL-Pattern IE within tdd-UL-DL-ConfigCommon; and

[1119] >: associatedPattern field within tdd-UL-DL-ConfigCommon;

[1120] >: offsetToFirstSBSymbol field within tdd-UL-DL-ConfigCommon; and

[1121] >: nrOfSBSymbols field within tdd-UL-DL-ConfigCommon.

[1122] The RA-RNTI in the PRACH opportunity where a random access preamble is transmitted, or the RA-RNTI associated with the last valid PRACH opportunity in the set of PRACH opportunities for Msg1 iteration, is calculated as follows:

[1124] \[

[1125] \text{RA-RNTI} = 1 + s_{id} + 14 \times t_{id} + 14 \times 80 \times f_{id} + 14 \times 80 \times 8 \times ul\_carrier\_id + SBFD\_RA\_RNTI\_OFFSET

[1126] \]

[1128] Here:

[1129] >: **s_id** is the index of the first OFDM symbol of the PRACH opportunity (0 ≤ s_id < 14);

[1130] >: **t_id** is the index of the first slot of the PRACH opportunity within the system frame (0 ≤ t_id < 80), and the subcarrier interval determining t_id is based on the value of μ (SCS index) and corresponds to the case where μ = {0, 1, 2, 3}. In the case where μ = {5, 6}, t_id is the index of the 120 kHz slot within the system frame containing the PRACH opportunity (0 ≤ t_id < 80).

[1131] >: **f_id** is the index of the PRACH opportunity in the frequency domain (0 ≤ f_id < 8), and **ul_carrier_id** represents the uplink carrier used for random access preamble transmission (0 is NUL carrier, 1 is SUL carrier).

[1133] If the RA-RNTI associated with the last valid PRACH opportunity in the set of PRACH opportunities for the PRACH opportunity (RO) or Msg1 iteration where the random access preamble is transmitted is a non-SBFD RO (non-SBFD symbol):

[1134] >: **s_id** and **t_id** are determined based on the following:

[1135] >>: SCS-SpecificCarrier of Uplink Configuration;

[1136] >>: Parameters for the PRACH configuration index for non-SBFD RO within IE for RA general configuration;

[1137] >>: The first TDD-UL-DL-Pattern IE within tdd-UL-DL-ConfigCommon; and

[1138] >>: The second TDD-UL-DL-Pattern IE within tdd-UL-DL-ConfigCommon.

[1139] >: **f_id** is determined based on the following:

[1140] >>: FDM-related parameters of RA general configuration(msg1-FDM, msg1-FrequencyStart);

[1141] >: **SBFD_RA_RNTI_OFFSET** is 0.

[1143] If the RA-RNTI associated with the last valid PRACH opportunity in the set of PRACH opportunities for the PRACH opportunity (RO) or Msg1 iteration where the random access preamble is transmitted is SBFD RO (SBFD symbol):

[1144] >: **s_id** and **t_id** are determined based on the following:

[1145] >>: SCS-SpecificCarrier of Downlink Configuration;

[1146] >>: Parameters for the PRACH configuration index for SBFD RO within sbfd-Config IE;

[1147] >>: The first TDD-UL-DL-Pattern IE within tdd-UL-DL-ConfigCommon;

[1148] >>: The second TDD-UL-DL-Pattern IE within tdd-UL-DL-ConfigCommon;

[1149] >>: offsetToFirstSBSymbol field within tdd-UL-DL-ConfigCommon; and

[1150] >>: nrOfSBSymbols field within tdd-UL-DL-ConfigCommon.

[1151] >: **f_id** is determined based on the following:

[1152] >>: sbfd-config FDM-related parameters in IE(msg1-FDM-sbfd, msg1-FrequencyStart-sbfd);

[1153] **SBFD_RA_RNTI_OFFSET** is set to a specific value. This specific value may be pre-configured or displayed in the system information.

[1156] If the SBFD / second frequency domain is configured in the serving cell, it is advantageous for the GNB to have control over the frequency domain in which Msg 3 is transmitted. The GNB uses the TRA field of the RAR to indicate the frequency domain for Msg 3 transmission.

[1158] The UE performs the following to send Msg 3:

[1159] The UE receives system information, and this system information includes various information elements (IE);

[1160] The UE triggers a random access (RA) procedure;

[1161] The UE transmits a PRACH preamble at the first RO in the first frequency domain or the second RO in the second frequency domain;

[1162] The UE monitors the PDCCH of a specific RA-RNTI in the third frequency range for a specific period;

[1163] The UE receives a RAR containing a MAC subPDU containing a random access preamble identifier corresponding to the transmitted preamble; and

[1164] The UE performs a PUSCH transmission based on the TAR and FAR fields of the RAR.

[1166] A RAR-based PUSCH transmission is performed as follows:

[1167] If the TAR field indicates that the PUSCH transmission is performed during the first time period, it is performed in the first frequency domain; and

[1168] If the TAR field indicates that the PUSCH transmission is performed during the second time period, it is performed in the second frequency domain.

[1170] The PRB for PUSCH transmission is determined based on the FRA field of the RAR, and:

[1171] If PUSCH transmission is performed during the first time period, it is determined by the number of PRBs in the first frequency domain; and

[1172] If PUSCH transmission is performed during the second time period, it is determined by the number of PRBs in the second frequency domain.

[1174] The UE performs the following for contention resolution and HARQ ACK transmission:

[1175] The UE receives system information, and this system information includes various information elements (IE);

[1176] The UE triggers a random access (RA) procedure;

[1177] The UE transmits a PRACH preamble at the first RO in the first frequency domain or the second RO in the second frequency domain;

[1178] The UE monitors the PDCCH of a specific RA-RNTI in the third frequency range for a specific period;

[1179] The UE receives a RAR containing a MAC subPDU containing a random access preamble identifier corresponding to the transmitted preamble;

[1180] The UE performs a PUSCH transmission based on the TAR and FAR fields of the RAR;

[1181] The UE performs PDSCH reception for contention resolution; and

[1182] The UE performs a HARQ ACK transmission.

[1184] Here, HARQ ACK transmission is performed in either the first frequency domain or the second frequency domain.

[1186] ### Bandwidth Section (BWP)

[1187] Bandwidth Parts (BWPs) are an essential function of 5G NR systems, enabling the efficient allocation of available bandwidth. BWPs provide the flexibility to allocate bandwidth according to specific user requirements. In the RRC_IDLE / INACTIVE state, the UE performs transmission and reception in the initial BWP. Since data transmission activity is limited in the RRC_IDLE / INACTIVE state, no additional BWPs are required. Unlike the RRC_IDLE / INACTIVE state, a UE in the RRC_CONNECTED state can be composed of multiple BWPs. The UE can switch between BWPs to maximize data transmission efficiency and minimize battery consumption.

[1189] The initial BWP is common to all UEs within the cell. The configuration of the initial BWP is provided in the system information. BWPs configured for a UE (e.g., dedicated BWPs) are UE-specific. The configuration of dedicated BWPs is provided via RRC messages.

[1190] When a UE operates in an SBFD cell, some of the UE's BWPs may overlap with the SBFD resource pool, as shown in the E800. If a BWP (e.g., BWP #2) partially overlaps with the SBFD frequency domain, scheduling for that BWP can become inefficient and complex. During the overlap period, the UE may need to determine priorities between downlink tasks (DL / FL resources) and uplink tasks (SBFD resources). Additionally, the fundamental principle of the center frequency (where the BWPs for the downlink center frequency and uplink center frequency are the same) is not maintained, which can affect the hardware design of the terminal.

[1192] In this disclosure, the base station configures a dedicated BWP so that the entire SBFD resource pool exactly matches the BWP (e.g., all PRBs in the BWP are SBFD PRBs, and all PRBs in other BWPs are not SBFD PRBs).

[1193] A BWP containing the entire SBFD resource pool is called an SBFD-BWP (S-BWP). An S-BWP (E900) consists only of non-SBFD resource pools during a specific period and only of SBFD resources during another period. All PRBs of an S-BWP are SBFD PRBs. The S-BWP configuration information includes a 1-bit mark indicating that all PRBs of a BWP are SBFD PRBs.

[1195] A BWP that does not include an SBFD resource pool is called a legacy-BWP (L-BWP). An L-BWP (E1000) always consists only of a non-SBFD resource pool. All PRBs in an L-BWP are non-SBFD PRBs.

[1196] If the active BWP is an L-BWP, this is equivalent to the UE being scheduled within the PRB set for the L-BWP.

[1197] If the active BWP is an S-BWP, this is equivalent to the UE being scheduled within the PRB set for the S-BWP.

[1199] ### BWP Configuration and Signal Structure

[1201] Figure 22 shows the signal structure for symbol type determination and BWP configuration.

[1202] The following BWPs are configured for UEs in the RRC_CONNECTED state:

[1203] >: Initial downlink BWP;

[1204] >: Initial Uplink BWP;

[1205] >: One or more dedicated downlink BWPs; and

[1206] >: One or more dedicated uplink BWPs.

[1208] The initial downlink BWP is composed of the BWP-DownlinkCommon IE in the initial downlink BWP field of SIB1 (A900) and the BWP-DownlinkDedicated IE in the initial downlink BWP field of the RRC reconstruction (A1000).

[1209] The initial uplink BWP is composed of the BWP-UplinkCommon IE in the initial uplink BWP field of SIB1 (A900) and the BWP-UplinkDedicated IE in the initial uplink BWP field of the RRC reconfiguration (A1000).

[1210] One or more dedicated downlink BWPs are configured by one or more BWP-Downlink IEs within the RRC reconfiguration (A1000).

[1211] One or more dedicated uplink BWPs are configured by one or more BWP-Uplink IEs within the RRC reconfiguration (A1000).

[1213] The SBFD resource pool is configured in one or more dedicated uplink BWPs.

[1214] The bwp-sbfd field within the BWP-Uplink IE (A1100) represents an uplink BWP configured with an SBFD resource pool (SBFD PRB). The UE determines the S-BWP based on the bwp-sbfd field. The UE determines the location and bandwidth of the S-BWP based on the locationAndBandwidth field within the corresponding BWP-UplinkCommon IE (A1200). The UE determines the SBFD PRB based on the locationAndBandwidth field because the entire bandwidth of the S-BWP is an SBFD PRB.

[1216] Alternatively, the UE can determine that it is an S-BWP as follows:

[1217] The SBFD resource pool is determined based on the received system information; and

[1218] A BWP with an SBFD resource pool is an S-BWP.

[1219] ### SBFD-PRB and Non-SBFD-PRB

[1221] **SBFD-PRB** can be used for the following:

[1222] >: Receive downlink during the first symbol (this symbol is marked as downlink by TDD-UL-DL-ConfigurationCommon and not an SBFD symbol by SBFD-time-resource-configuration);

[1223] >: Uplink transmission during the second symbol (this symbol is indicated as a downlink by TDD-UL-DL-ConfigurationCommon and as an SBFD symbol by SBFD-time-resource-configuration); and

[1224] >: Uplink transmission during the third symbol (this symbol is designated as uplink by TDD-UL-DL-ConfigurationCommon or TDD-UL-DL-ConfigurationDedicated).

[1226] **Non-SBFD-PRB** can be used for the following:

[1227] >: Receive downlink during the first symbol (this symbol is marked as downlink by TDD-UL-DL-ConfigurationCommon and not an SBFD symbol by SBFD-time-resource-configuration);

[1228] >: Receive downlink during the second symbol (this symbol is indicated as downlink by TDD-UL-DL-ConfigurationCommon and as an SBFD symbol by SBFD-time-resource-configuration); and

[1229] >: Uplink transmission during the third symbol (this symbol is designated as uplink by TDD-UL-DL-ConfigurationCommon or TDD-UL-DL-ConfigurationDedicated).

[1231] The PRB of the initial BWP is not composed of SBFD-PRB.

[1232] The PRB of a non-initial BWP consists of SBFD-PRB.

[1234] ### Operation in Unpaired Spectrum

[1236] In non-paired spectrum (i.e., TDD), the direction / type of a specific spectrum (e.g., PRB2 of the E1000) changes over time (or per symbol). A symbol is one of a downlink symbol, an uplink symbol, or a flexible symbol. In TDD, one UL BWP and one DL BWP are active at a time. A UL BWP and a DL BWP with the same bwp-Id are active together. If a UL BWP and a DL BWP have the same bwp-Id, they are a paired BWP. The GNB is configured so that paired BWPs have the same center frequency and the same bandwidth.

[1238] ### Behavior based on BWP type

[1240] If the active BWP is L-BWP:

[1241] DL BWP occurs on downlink symbols;

[1242] UL BWP occurs on the uplink symbol.

[1244] If the active BWP is an S-BWP:

[1245] DL BWP occurs on downlink symbols;

[1246] UL BWP occurs in uplink symbols and SBFD symbols.

[1248] If the active BWP is an L-BWP, UEs in the RRC_CONNECTED state determine the symbol type based on the following:

[1249] >: Parameters of TDD-UL-DL-ConfigCommon; and

[1250] >: Parameters of TDD-UL-DL-ConfigDedicated.

[1252] If the active BWP is an S-BWP, UEs in the RRC_CONNECTED state determine the symbol type based on the following:

[1253] >: Parameters of TDD-UL-DL-ConfigCommon;

[1254] >: Parameters of SBFD-time-resource-config; and

[1255] >: Parameters of TDD-UL-DL-ConfigDedicated.

[1257] ### Configuration Information

[1259] TDD-UL-DL-ConfigCommon (A1300) includes the referenceSubcarrierSpacing field, the pattern1 field, and the pattern2 field.

[1260] TDD-UL-DL-ConfigDedicated (A1400) includes one or more TDD-UL-DL-SlotConfig IEs.

[1261] SBFD-time-resource-config IE (A1500) includes TimeDomainResourceParameters IE.

[1262] ### L-BWPs

[1263] The UE determines downlink symbols, uplink symbols, and flexible symbols during the pattern period based on TDD-UL-DL-ConfigCommon;

[1264] The UE determines downlink and uplink symbols represented by flexible symbols in TDD-UL-DL-ConfigCommon based on TDD-UL-DL-ConfigDedicated.

[1266] ### S-BWPs

[1267] The UE determines downlink symbols, uplink symbols, and flexible symbols during the pattern period based on TDD-UL-DL-ConfigCommon;

[1268] The UE determines SBFD symbols and non-SBFD symbols during the pattern period based on SBFD-time-resource-config; and

[1269] The UE determines downlink and uplink symbols based on TDD-UL-DL-ConfigCommon, which are represented as flexible symbols in TDD-UL-DL-ConfigCommon and as non-SBFD symbols in SBFD-time-resource-config.

[1271] **symbol_rx** represents a receiveable symbol, and **symbol_tx** represents a transmittable symbol.

[1273] ### Symbol Availability for L-BWP

[1274] The UE considers the symbols in the slots marked as downlink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated to be receiveable, and the symbols in the slots marked as uplink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated to be transmittable.

[1276] ### Symbol Availability for S-BWP

[1277] >: When the UE considers the symbol to be receiveable:

[1278] >>: The symbol is marked as a downlink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated; and

[1279] >>: If not marked as an SBFD symbol by SBFD-time-resource-config.

[1281] When the UE considers the symbol to be transmittable:

[1282] >: If the symbol is marked as an uplink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated.

[1284] When the UE considers the symbol to be transmittable:

[1285] The symbol is marked as a downlink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated; and

[1286] When indicated by the SBFD symbol by SBFD-time-resource-config.

[1288] When the UE considers the symbol to be transmittable:

[1289] The symbol is represented as a flexible symbol by tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated; and

[1290] When indicated by the SBFD symbol by SBFD-time-resource-config.

[1292] Alternatively, the UE determines whether the symbol is receiveable or transmittable as follows.

[1293] In common*, indicated as In SBFD*, indicated as In dedicate*, indicated as Active BWP is L-BWP Active BWP is S-BWP Downlink SBFD symbol Downlink Available for reception Transmission available Downlink Non-SBFD symbol Downlink Available for reception Available for reception Flexible symbol SBFD symbol Downlink Available for reception Transmission available Flexible symbol SBFD symbol Flexible symbol Available for reception or transmission Transmission available Flexible symbol SBFD symbol Uplink Transmission available Transmission available Flexible symbol Non-SBFD symbol Downlink Available for reception Available for reception Flexible symbol Non-SBFD symbol Flexible symbol Available for reception or transmission Available for reception or transmission Flexible symbol Non-SBFD symbol Uplink Transmission available Transmission available Uplink Non-SBFD symbol Uplink Transmission available Transmission available

[1294] common*: tdd-UL-DL-ConfigurationCommon

[1295] SBFD*: SBFD-time-resource-config

[1296] dedicated*: tdd-UL-DL-ConfigurationDedicated

[1297] ### Symbol Availability

[1299] Symbols available in all directions can be used for transmission or reception depending on uplink or downlink signal configuration or dynamic scheduling.

[1301] ### Symbol configuration for L-BWP

[1302] The symbol is composed as follows:

[1303] >>: Downlink (e.g., Receiving) or Uplink (e.g., Transmitting), which is indicated by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated;

[1304] >>: Uplink, if the symbol is flexible (i.e., bidirectional) and the UE is configured to transmit SRS, PUCCH, PUSCH, or PRACH from the symbol;

[1305] >>: On the downlink (e.g., receivable), if the symbol is flexible and the UE is configured to receive PDCCH, PDSCH, or CSI-RS from the symbol

[1307] ### Symbol Configuration for S-BWP

[1308] The symbol is composed as follows:

[1309] >>: Downlink (e.g., receiveable) or uplink (e.g., transmitable), which is determined by a combination of tdd-UL-DL-ConfigurationCommon, tdd-UL-DL-ConfigurationDedicated, and SBFD-time-resource-config;

[1310] >>: On the uplink (transmittable), if the symbol is flexible (i.e., transmissible in both directions) and the UE is configured to transmit SRS, PUCCH, PUSCH, or PRACH in the symbol;

[1311] >>: Downlink (e.g., receivable), if the symbol is flexible (i.e., both directions possible) and the UE is configured to receive PDCCH, PDSCH, or CSI-RS from the symbol.

[1313] ### SRS Transmission

[1314] That the UE is configured to transmit SRS from symbols in the BWP is equivalent to the following:

[1315] SRS-Config for BWP is configured;

[1316] >: SRS opportunities occur in the symbol.

[1318] The UE transmits the SRS from the BWP symbol in the following cases:

[1319] The UE is configured to transmit SRS in the symbol;

[1320] The symbol can be used for transmission.

[1322] ### PUCCH transmission

[1323] That the UE is configured to transmit PUCCH from the symbol in the BWP is equivalent to the following:

[1324] PUCCH-Config for BWP is configured;

[1325] A PUCCH opportunity occurs in the symbol.

[1327] The UE transmits PUCCH from the BWP symbol in the following cases:

[1328] The UE is configured to transmit PUCCH in the symbol;

[1329] The symbol can be used for transmission.

[1331] ### PUSCH transmission

[1332] That the UE is configured to transmit PUSCH in the BWP symbol is equivalent to the following:

[1333] ConfiguredGrantConfig for BWP is configured;

[1334] >: An active configured assignment occurs in the symbol.

[1336] The UE transmits PUSCH from the BWP symbol in the following cases:

[1337] The UE is configured to transmit PUSCH in the symbol;

[1338] The symbol can be used for transmission.

[1340] That the UE is configured to transmit PRACH from the symbol in the BWP is equivalent to the following:

[1341] RACH-ConfigCommon is configured for BWP;

[1342] PRACH opportunity occurs in the symbol.

[1344] *

[1345] The UE transmits PRACH from the BWP symbol in the following cases:

[1346] The UE is configured to transmit PRACH in the symbol;

[1347] The symbol can be used for transmission.

[1349] That the UE is configured to receive PDCCH from the BWP symbol is equivalent to the following:

[1350] >: A SearchSpace is configured for the BWP (e.g., a related CORESET is configured within the BWP);

[1351] SearchSpace occurs in the symbol.

[1353] The UE receives PDCCH from the BWP symbol in the following cases:

[1354] The UE is configured to receive PDCCH from the symbol;

[1355] The symbol is available for reception.

[1357] That the UE is configured to receive PDSCH from symbols in the BWP is equivalent to the following:

[1358] SPS-Config is configured for BWP;

[1359] >: An active configured assignment occurs in the symbol.

[1361] The UE receives PDSCH from the BWP symbol in the following cases:

[1362] The UE is configured to receive PDSCH from the symbol;

[1363] The symbol is available for reception.

[1365] That the UE is configured to receive CSI-RS from symbols in the BWP is equivalent to the following:

[1366] CSI-ResourceConfig is associated with BWP;

[1367] CSI-Resource is activated and occurs in the symbol.

[1369] The UE receives CSI-RS from the BWP symbol in the following cases:

[1370] The UE is configured to receive CSI-RS from the symbol;

[1371] The symbol is available for reception.

[1373] ### Symbol Type and Direction

[1375] The symbol exists in either L-BWP or S-BWP.

[1376] For non-SBFD symbols (e.g., symbol n), the type / orientation of the symbol is the same among BWPs (E2100).

[1377] For SBFD symbols (e.g., symbol m), the type / direction of the symbol may differ between L-BWP and S-BWP (E2200). For example, symbol m is represented as a downlink symbol (received) in BWP#1 and BWP#0, but as an SBFD symbol (transmitted) in BWP#2.

[1379] In the case of an SBFD symbol:

[1380] The symbol can be received in the L-BWP and transmitted in the S-BWP. This applies to the following cases:

[1381] >>: Marked as a downlink by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated;

[1382] >>: Indicated by the SBFD symbol by SBFD-time-resource-config.

[1384] The symbol can be received in the L-BWP and transmitted in the S-BWP. This applies to the following cases:

[1385] >>: Indicated by flexible symbols by tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated;

[1386] >>: Indicated by the SBFD symbol by SBFD-time-resource-config; and

[1387] >>: The UE is configured to receive PDCCH, PDSCH, or CSI-RS from the symbol.

[1390] ### Symbol Definition and Type Determination

[1392] Let's define the symbol as follows:

[1393] >>: The nth symbol within a slot configuration period of P + P₂ milliseconds; and

[1394] >>: The k-th symbol of the m-th slot within a slot configuration period P + P₂ milliseconds.

[1396] >: When a symbol is marked as a downlink by TDD-UL-DL-ConfigurationCommon:

[1397] >>: d_slot * number_of_symbols_per_slot + d_sym >= n; or

[1398] >>: P * number_of_symbols_per_subframe < n <= P * number_of_symbols_per_subframe + d_slot2 * number_of_symbols_per_slot + d_sym2;

[1400] >: When a symbol is marked as an uplink by TDD-UL-DL-ConfigurationCommon:

[1401] >>: P * number_of_symbols_per_subframe ? (u_slot * number_of_symbols_per_slot + u_slot) < n <= P * number_of_symbols_per_subframe; or

[1402] >>: (P + P₂) * number_of_symbols_per_subframe - (u_slot2 * number_of_symbols_per_slot + u_slot2) < n <= (P + P₂) * number_of_symbols_per_subframe;

[1404] >: When a symbol is marked as a flexible symbol by TDD-UL-DL-ConfigurationCommon:

[1405] >>: d_slot * number_of_symbols_per_slot + d_sym < n <= P * number_of_symbols_per_subframe ? (u_slot * number_of_symbols_per_slot + u_slot); or

[1406] >>: P * number_of_symbols_per_subframe + d_slot2 * number_of_symbols_per_slot + d_sym2 < n <= (P + P₂) * number_of_symbols_per_subframe - (u_slot2 * number_of_symbols_per_slot + u_slot2);

[1408] >: When a symbol is marked as a downlink by TDD-UL-DL-ConfigurationDedicated:

[1409] >>: Must be represented by flexible symbols by TDD-UL-DL-ConfigurationCommon; and

[1410] >>: nrofDownlinkSymbols of m-th slot >= k;

[1412] >: When a symbol is marked as an uplink by TDD-UL-DL-ConfigurationDedicated:

[1413] >>: Must be represented by flexible symbols by TDD-UL-DL-ConfigurationCommon; and

[1414] >>: number_of_symbol_per_slot - nrofUplinkSymbols of m-th slot < k;

[1416] >: When indicated by the SBFD symbol:

[1417] >>: Associated with SBFD resource pool pattern 1 and if offsetToFirstSBSymobol <= n < offsetToFirstSBSymobol + nrOfSBSymbols; or

[1418] >>: Related to SBFD resource pool pattern 2, where P1 * number_of_symbols_per_slot + offsetToFirstSBSymobol <= n < P1 * number_of_symbols_per_slot + offsetToFirstSBSymobol + nrOfSBSymbols.

[1420] ### Determine Symbol Type

[1422] The UE performs the following to determine the type of symbol:

[1423] - **Determining the type of virtual symbol**: The UE determines the type of virtual symbol based on the subcarrier spacing indicated by the referenceSubcarrierSpacing field of TDD-UL-DL-ConfigCommon.

[1424] - **Determination of Actual Symbol Type**: The UE determines the actual symbol type based on the subcarrier spacing field within the BWP IE of the BWP-UplinkConfigCommon in the S-BWP.

[1426] The UE applies a symbol type to the set of actual symbols associated with a virtual symbol. For example, if a virtual symbol is represented as an SBFD symbol, the set of actual symbols mapped to that virtual symbol is also represented as an SBFD symbol.

[1427] SCS1 SCS2 No* SCS1 SCS2 No* 15 15 1 30 60 2 15 30 2 60 15 0.25 15 60 4 60 30 0.5 30 15 0.5 60 60 1 30 30 1

[1428] ### SCS and Symbol Definitions

[1429] **SCS1**: referenceSubcarrierSpacing

[1430] **SCS2**: subcarrierSpacing of the S-BWP

[1431] **No***: number of actual symbols per virtual symbol

[1433] ### Working with UE and GNB

[1435] Figure 27 illustrates the operation of the UE and GNB.

[1436] At S110, the UE (D100) receives system information from the GNB (D200).

[1438] Based on system information, the UE determines whether it can access the cell. At some point, when an RRC connection setup is required for reasons such as user services, the UE performs the RRC connection setup procedure with the GNB. The RRC connection setup procedure is performed at the initial BWP. After the RRC connection is established, the UE reports its radio capabilities to the GNB. Based on the reported capabilities, the GNB determines the radio resource control configuration for the UE.

[1440] At S220, the GNB sends an RRC reconfiguration message to the UE. The RRC reconfiguration message contains various configuration information for the UE.

[1441] The GNB schedules UEs based on configuration information provided by RRC reconfiguration.

[1443] At some point, the GNB decides to switch the UE's BWP. At S230, the BWP switch is indicated by the bwp-id field in the DCI sent by the GNB to the UE.

[1444] At O210, the UE disables the currently active BWP and enables the paired BWP indicated by bwp-id.

[1445] At O220, the UE determines the receiveable and transmitable symbols. In determining the receiveable and transmit symbols, the UE considers whether the active BWP is an S-BWP or an L-BWP.

[1446] At S240, the UE performs PDCCH / PDSCH / CSI-RS reception on the receiveable symbols.

[1447] At S250, the UE performs PRACH / PUCCH / PUSCH / SRS transmissions on transmittable symbols.

[1449] ### UE operations in RRC_CONNECTED state

[1451] The UE performs the following tasks.

[1452] The UE receives system information, and this system information includes various information elements / fields:

[1453] >>: referenceSubcarrierSpacing;

[1454] >>: TDD-UL-DL-Pattern for pattern 1;

[1455] >>: TDD-UL-DL-Pattern for pattern 2; and

[1456] >>:SBFD-time-resource-config;

[1458] The UE receives an RRC reconstruction message, which includes various information elements / fields:

[1459] >>: BWP configuration for one or more dedicated BWPs IE; and

[1460] >>:TDD-UL-DL-ConfigDedicated;

[1462] The UE enables paired BWPs based on the DCI's bwp-Id;

[1463] The UE determines the first set of symbols (receiveable symbols) and the second set of symbols (transmittable symbols); and

[1464] The UE performs transmission and reception based on the decision.

[1466] If bwp-Id represents the first BWP (L-BWP), the first and second symbol sets are determined based on the following:

[1467] >>: TDD-UL-DL-Pattern received from system information; and

[1468] >>: TDD-UL-DL-ConfigDedicated received in RRC message.

[1470] *

[1471] If bwp-Id represents the second BWP (S-BWP), the first and second symbol sets are determined based on the following:

[1472] >>: TDD-UL-DL-Pattern received from system information;

[1473] >>: SBFD-time-resource-config received from system information (or if received from an RRC message);

[1474] >>: TDD-UL-DL-ConfigDedicated received in RRC message.

[1476] The configuration information of the first BWP does not include specific fields related to SBFD (e.g., SBFD display or PRB list related to SBFD operations).

[1477] The configuration information of the second BWP includes specific fields related to SBFD.

[1478] ### UE operations in RRC connection status

[1480] The UE performs the following tasks:

[1481] The UE receives system information, and this system information includes various information elements / fields;

[1482] The UE receives an RRC reconstruction message, which includes various information elements / fields;

[1483] The UE determines whether the symbol is receiveable or transmittable; and

[1484] The UE performs transmission and reception according to the decision;

[1486] If the symbol is receivable in the first set of PRBs (PRBs configured for the default uplink BWP) and transmittable in the second set of PRBs (PRBs configured for the subband half-duplex BWP):

[1487] The symbol is indicated by the first type (downlink) by TDD-UL-DL-ConfigurationCommon or TDD-UL-DL-ConfigurationDedicated; and

[1488] The symbol is marked as the second type (SBFD) by SBFD-time-resource-config.

[1490] If the symbol is receivable in the first set of PRBs (PRBs configured for the default uplink BWP) and transmittable in the second set of PRBs (PRBs configured for the subband half-duplex BWP):

[1491] The symbol is marked as a second type (SBFD) by TDD-UL-DL-ConfigurationCommon and TDD-UL-DL-ConfigurationDedicated;

[1492] The symbol is marked as the second type (SBFD) by SBFD-time-resource-config; and

[1493] The UE is configured to receive PDSCH at the symbols of the first set of PRBs.

[1495] ### UE Workflow

[1497] Figure 28 shows the operation of the UE.

[1498] At U100, the UE receives system information from the base station.

[1499] At U200, the UE receives an RRC reconfiguration message from the base station.

[1500] At U300, the UE receives a DCI from the base station that triggers a BWP switch.

[1501] At U400, the UE determines the receivable and transmittable symbols. If the SBFD UL subband overlaps with the BWP, the SBFD symbol is transmittable. If the SBFD DL subband overlaps with the BWP, the SBFD symbol is receivable.

[1502] At U500, the UE performs reception on receiveable symbols and transmission on transmitable symbols. It receives RAR based on PDCCH.

[1504] ### Internal Structure of the UE

[1506] FIG. 29 is a block diagram showing the internal structure of a UE to which the present disclosure applies.

[1507] Referring to the diagram, the UE includes a controller W100, a storage device W200, a transceiver W300, a main processor W400, and an I / O device W500.

[1508] Controller W100 controls the overall operation of the UE in terms of mobile communication. For example, Controller W100 receives / transmits signals through transceiver W300. Additionally, Controller W100 writes and reads data from storage device W200. To this end, Controller W100 includes at least one processor. For example, Controller W100 may include a communication processor (CP) that performs control for communication and an application processor (AP) that controls upper layers such as application programs. The controller controls the storage device and transceiver so that the UE's operation is performed in accordance with this disclosure.

[1509] ### Components of the UE

[1511] Storage device W200 stores data for the operation of the UE and includes basic programs, application programs, and configuration information. Storage device W200 provides the stored data upon request from controller W100.

[1513] The W300 transceiver consists of an RF processor, a baseband processor, and one or more antennas. The RF processor performs signal transmission and reception functions over the wireless channel, such as signal band conversion and amplification. Specifically, the RF processor upconverts the baseband signal provided by the baseband processor into an RF band signal, transmits it through the antenna, and downconverts the RF band signal received through the antenna back into a baseband signal. The RF processor may include a transmit filter, a receive filter, an amplifier, a mixer, an oscillator, a digital-to-analog converter (DAC), an analog-to-digital converter (ADC), etc. The RF processor can perform MIMO and can receive multiple layers when performing MIMO operations. The baseband processor performs conversion functions between the baseband signal and the bit string according to the physical layer specifications of the system. For example, during data transmission, the baseband processor encodes and modulates the transmitted bit string to generate complex symbols. In addition, during data reception, the baseband processor demodulates and decodes the baseband signal provided by the RF processor to restore the received bit string.

[1515] The main processor W400 controls all operations other than mobile tasks. The main processor W400 processes user input received from the I / O device W500, stores data in the storage device W200, controls the controller W100 for necessary mobile communication tasks, and transmits user data to the I / O device W500.

[1517] The I / O device W500 is equipment for inputting and outputting user data and includes a microphone and a screen. The I / O device W500 inputs and outputs user data according to the instructions of the main processor.

[1519] ### Base Station Configuration

[1521] FIG. 30 is a block diagram showing the configuration of a base station according to the present disclosure.

[1522] As shown in the diagram, the base station includes a controller N100, a storage device N200, a transceiver N300, and a backhaul interface device N400.

[1524] Controller N100 controls the overall operation of the main base station. For example, Controller N100 receives / transmits signals through transceiver N300 or backhaul interface device N400. Additionally, Controller N100 writes and reads data from storage device N200. To this end, Controller N100 may include at least one processor. The controller controls the transceiver, storage device, and backhaul interface so that the operation of the base station is performed in accordance with this disclosure.

[1526] Storage device N200 stores data for the operation of the main base station and includes basic programs, application programs, and configuration information. In particular, storage device N200 can store information regarding bearers assigned to accessed UEs, measurement results reported by accessed UEs, etc. Additionally, storage device N200 can store information used as a criterion for determining whether to provide multiple connections to the UE. Storage device N200 provides the stored data upon request from controller N100.

[1527] ### Transmitter & Receiver Configuration

[1529] The transceiver N300 consists of an RF processor, a baseband processor, and one or more antennas. The RF processor performs signal transmission and reception functions over a wireless channel, such as signal band conversion and amplification. Specifically, the RF processor upconverts a baseband signal provided by the baseband processor into an RF band signal, transmits it through the antenna, and downconverts the RF band signal received through the antenna into a baseband signal. The RF processor may include a transmit filter, a receive filter, an amplifier, a mixer, an oscillator, a DAC (digital-to-analog converter), an ADC (analog-to-digital converter), etc. The RF processor can perform downlink MIMO operations by transmitting at least one layer.

[1531] The baseband processor performs conversion functions between baseband signals and bit strings according to the physical layer specifications of the first wireless access technology. For example, during data transmission, the baseband processor encodes and modulates the transmitted bit string to generate complex symbols. Additionally, during data reception, the baseband processor demodulates and decodes the baseband signal provided by the RF processor to restore the received bit string.

[1533] ### Backhaul Interface Device

[1535] The backhaul interface device N400 provides an interface for communicating with other nodes within the network. The backhaul interface device N400 converts bit strings transmitted from a base station to another node (e.g., another base station or core network) into physical signals, and converts physical signals received from other nodes into bit strings.

[1537] ### SCS-SpecificCarrier Information Elements

[1539] IE SCS-SpecificCarrier provides parameters that determine the actual carrier position and width or carrier bandwidth. This is defined in relation to specific numerical values ​​(Subcarrier Spacing (SCS)) and the frequency offset for Point A.

[1541] -- ASN1START

[1542] -- TAG-SCS-SPECIFICCARRIER-START

[1544] SCS-SpecificCarrier ::= SEQUENCE {

[1545] offsetToCarrier INTEGER (0..2199);

[1546] subcarrierSpacing SubcarrierSpacing,

[1547] carrierBandwidth INTEGER (1..maxNrofPhysicalResourceBlocks);

[1548] ...,

[1549] [[

[1550] txDirectCurrentLocation INTEGER (0..4095) OPTIONAL -- Need S

[1551] ]]

[1552] [[

[1553] ul-subbandlocationAndBandwidth INTEGER (0..37949) OPTIONAL, -- Need R

[1554] firstDLsubbandlocationAndBandwidth INTEGER (0..37949) OPTIONAL, -- Need R

[1555] secondDLsubbandlocationAndBandwidth INTEGER (0..37949) OPTIONAL -- Need R

[1556] ]]

[1557] }

[1559] -- TAG-SCS-SPECIFICCARRIER-STOP

[1560] -- ASN1STOP

[1562] ### SCS-SpecificCarrier Field Description

[1564] **TxDirectCurrentLocation**: Indicates the downlink Tx DC location of the carrier. Value ranges 0..3299 represent the subcarrier index within the carrier. Value ranges 3301..4095 are reserved and ignored by the UE. If this field is missing for the downlinks of ServingCellConfigCommon and ServingCellConfigCommonSIB, the UE assumes the default value of 3300.

[1566] **SubcarrierSpacing**: Represents the subcarrier spacing of this carrier. This is used to convert offsetToCarrier to the actual frequency.

[1568] **ul-subbandlocationAndBandwidth**: Configures the frequency domain location and bandwidth of the uplink subband. The value of this field should be interpreted as a Resource Indicator Value (RIV) when N_frequencyRegion_size is 275. The network does not configure this field for downlink carriers.

[1570] **FirstDLsubbandlocationAndBandwidth**: Configures the frequency domain location and bandwidth of the first downlink subband. The value of this field should be interpreted as a Resource Indicator Value (RIV) when N_frequencyRegion_size is 275. The network does not configure this field for uplink carriers.

[1572] **SecondDLsubbandlocationAndBandwidth**: Configures the frequency domain location and bandwidth of the second downlink subband. The network does not configure this field for the uplink carrier.

[1575] The IE TDD-UL-DL-ConfigCommon determines the cell specific Uplink / Downlink TDD configuration.

[1576] TDD-UL-DL-ConfigCommon information element

[1577] -- ASN1START

[1578] -- TAG-TDD-UL-DL-CONFIGCOMMON-START

[1580] TDD-UL-DL-ConfigCommon ::= SEQUENCE {

[1581] referenceSubcarrierSpacing SubcarrierSpacing,

[1582] pattern1 TDD-UL-DL-Pattern,

[1583] pattern2 TDD-UL-DL-Pattern OPTIONAL, -- Need R

[1584] ...

[1585] }

[1587] TDD-UL-DL-Pattern ::= SEQUENCE {

[1588] dl-UL-TransmissionPeriodicity ENUMERATED {ms0p5, ms0p625, ms1, ms1p25, ms2, ms2p5, ms5, ms10},

[1589] nrofDownlinkSlots INTEGER (0..maxNrofSlots);

[1590] nrofDownlinkSymbols INTEGER (0..maxNrofSymbols-1),

[1591] nrofUplinkSlots INTEGER (0..maxNrofSlots),

[1592] nrofUplinkSymbols INTEGER (0..maxNrofSymbols-1),

[1593] ...,

[1594] [[

[1595] dl-UL-TransmissionPeriodicity-v1530 ENUMERATED {ms3, ms4} OPTIONAL -- Need R

[1596] ]],

[1597] [[

[1598] sbfd-StartingSlotIndex-r19 INTEGER (0..maxNrofSlots-1) OPTIONAL, -- Need R

[1599] sbfd-StartingSymbolIndex-r19 INTEGER (0..maxNrofSymbols-1) OPTIONAL, -- Need R

[1600] sbfd-EndingSlotIndex-r19 INTEGER (0..maxNrofSlots-1) OPTIONAL, -- Need R

[1601] sbfd-EndingSymbolIndex-r19 INTEGER (0..maxNrofSymbols-1) OPTIONAL -- Need R

[1602] ]]

[1603] }

[1605] -- TAG-TDD-UL-DL-CONFIGCOMMON-STOP

[1606] -- ASN1STOP

[1608] ### SBFD Related Parameters

[1610] **sbfd-StartingSlotIndex, sbfd-EndingSlotIndex**: Configures the start slot index and end slot index of the SBFD subband within the TDD-UL-DL period.

[1611] **sbfd-StartingSymbolIndex, sbfd-EndingSymbolIndex**: Constructs the start symbol index and end symbol index within the start slot of the SBFD subband during the TDD-UL-DL period.

[1612] The SBFD resource pool is the uplink resource of the UL subband in the SBFD symbol.

[1614] A consecutive set of SBFD symbols is composed of pattern 1 or pattern 2.

[1615] A successive set of SBFD symbols can be determined based on a set of parameters for the SBFD symbols.

[1616] The parameter set for the SBFD symbol can be sbfd-StartingSlotIndex, sbfd-EndingSlotIndex, sbfd-StartingSymbolIndex, and sbfd-EndingSymbolIndex.

[1617] The set of parameters for SBFD symbols can be determined based on offsetToFirstSBSymobol and nrOfSBSymbols.

[1619] The UE determines that a consecutive set of SBFD symbols is constructed in Pattern 1:

[1620] >: If the parameter set for the SBFD symbol is included in the TDD-UL-DL-Config for Pattern 1; or

[1621] >: If associatedPattern represents pattern 1.

[1623] The UE determines that a consecutive set of SBFD symbols is constructed in Pattern 2:

[1624] >: If the parameter set for the SBFD symbol is included in the TDD-UL-DL-Config for Pattern 2; or

[1625] >: If associatedPattern represents pattern 2.

[1627] ### BWP-DownlinkDedicated IE

[1629] IE BWP-DownlinkDedicated is used to configure dedicated (UE-specific) parameters for downlink BWPs.

[1631] -- ASN1START

[1632] -- TAG-BWP-DOWNLINKDEDICATED-START

[1634] BWP-DownlinkDedicated ::= SEQUENCE {

[1635] pdcch-Config SetupRelease { PDCCH-Config} OPTIONAL, -- Need M

[1636] pdsch-Config SetupRelease { PDSCH-Config} OPTIONAL, -- Need M

[1637] sps-Config SetupRelease { SPS-Config} OPTIONAL, -- Need M

[1638] radioLinkMonitoringConfig SetupRelease { RadioLinkMonitoringConfig} OPTIONAL, -- Need M

[1639] ...,

[1640] preConfGapStatus-r17 BIT STRING (SIZE (maxNrofGapId-r17)) OPTIONAL, -- Cond PreConfigMG

[1641] beamFailureRecoverySpCellConfig-r17 SetupRelease { BeamFailureRecoveryRSConfig-r16} OPTIONAL, -- Cond SpCellOnly

[1642] harq-FeedbackEnablingforSPSactive-r17 BOOLEAN OPTIONAL, -- Need R

[1643] cfr-ConfigMulticast-r17 SetupRelease { CFR-ConfigMulticast-r17} OPTIONAL, -- Need M

[1644] dl-PPW-PreConfigToAddModList-r17 DL-PPW-PreConfigToAddModList-r17 OPTIONAL, -- Need N

[1645] dl-PPW-PreConfigToReleaseList-r17 DL-PPW-PreConfigToReleaseList-r17 OPTIONAL, -- Need N

[1646] nonCellDefiningSSB-r17 NonCellDefiningSSB-r17 OPTIONAL, -- Need R

[1647] servingCellMO-r17 MeasObjectId OPTIONAL -- Cond MeasObject-NCD-SSB

[1648] ]],

[1649] [[

[1650] tci-InDCI-r18 SetupRelease {TCI-InDCI-r18} OPTIONAL -- Need M

[1651] ]],

[1652] [[

[1653] sbfd-Config2-Reception-r19 ENUMERATED {enabled} OPTIONAL -- Need S

[1654] ]]

[1655] }

[1657] -- TAG-BWP-DOWNLINKDEDICATED-STOP

[1658] -- ASN1STOP

[1659] ### PDCCH and PDSCH Configuration

[1661] **pdcch-Config**: UE-specific PDCCH configuration for a single BWP.

[1662] **pdsch-Config**: UE-specific PDSCH configuration for a single BWP.

[1663] **sbfd-Config2-Reception**: Indicates that PDSCH reception is possible in different slots for SBFD symbols and non-SBFD symbols for a dedicated DL BWP. This is as specified in TS 38.214

[19] , Klaus X. If not enabled, Configuration 1 applies for PDSCH reception in a given DL BWP.

[1665] **sps-Config**: UE-specific SPS (semi-permanent scheduling) configuration for a single BWP. Except for synchronized reconfiguration, the NW does not reconfigure sps-Config when there are active configured downlink assignments (see TS 38.321 [3]). However, the NW can release sps-Config at any time. The network can configure SPS in only one BWP using this field or sps-ConfigToAddModList. The network does not configure SPS in one BWP using this field and sps-ConfigMulticastToAddModList-r17 simultaneously.

[1667] ### BWP-UplinkCommon IE

[1669] IE BWP-UplinkCommon is used to configure the common parameters of the uplink BWP. These are "cell-specific," and the network ensures the necessary alignment with the corresponding parameters of other UEs. Common parameters for the initial bandwidth portion of the PCell, excluding additional RACH-perPCI-ToAddModList and additional RACH-perPCI-ToReleaseList, are also provided via system information. For all other serving cells, the network provides common parameters via dedicated signals.

[1670] -- ASN1START

[1671] -- TAG-BWP-UPLINKCOMMON-START

[1673] BWP-UplinkCommon ::= SEQUENCE {

[1674] genericParameters BWP,

[1675] rach-ConfigCommon SetupRelease { RACH-ConfigCommon} OPTIONAL, -- Need M

[1676] pusch-ConfigCommon SetupRelease { PUSCH-ConfigCommon} OPTIONAL, -- Need M

[1677] pucch-ConfigCommon SetupRelease { PUCCH-ConfigCommon} OPTIONAL, -- Need M

[1678] …

[1679] additionalRACH-ConfigList-r17 SetupRelease { AdditionalRACH-ConfigList-r17} OPTIONAL, -- Cond SpCellOnly2

[1680] rsrp-ThresholdMsg3-r17 RSRP-Range OPTIONAL, -- Need R

[1681] numberOfMsg3-RepetitionsList-r17 SEQUENCE (SIZE (4)) OF NumberOfMsg3-Repetitions-r17 OPTIONAL, -- Cond Msg3Rep

[1682] mcs-Msg3-Repetitions-r17 SEQUENCE (SIZE (8)) OF INTEGER (0..31) OPTIONAL -- Cond Msg3Rep

[1683] …

[1684] rsrp-ThresholdMsg1-RepetitionNum2-r18 RSRP-Range OPTIONAL, -- Need R

[1685] rsrp-ThresholdMsg1-RepetitionNum4-r18 RSRP-Range OPTIONAL, -- Need R

[1686] rsrp-ThresholdMsg1-RepetitionNum8-r18 RSRP-Range OPTIONAL, -- Need R

[1687] preambleTransMax-Msg1-Repetition-r18 ENUMERATED {n1, n2, n4, n6, n8, n10, n20, n50, n100, n200} OPTIONAL -- Cond Msg1Rep1

[1688] ]],

[1689] [[

[1690] sbfd-RSRP-ThresholdRO-Type-r19 RSRP-Range OPTIONAL, -- Need R

[1691] sbfd-RSRP-ThresholdRO-TypeUsage-r19 ENUMERATED {above,below} OPTIONAL, -- Need R

[1692] sbfd-RSRP-ThresholdMsg1-RepetitionNum2-r19 RSRP-Range OPTIONAL, -- Need R

[1693] sbfd-RSRP-ThresholdMsg1-RepetitionNum4-r19 RSRP-Range OPTIONAL, -- Need R

[1694] sbfd-RSRP-ThresholdMsg1-RepetitionNum8-r19 RSRP-Range OPTIONAL, -- Need R

[1695] rach-ConfigCommonSBFD-r19 SetupRelease { RACH-ConfigCommonSBFD-r19} OPTIONAL -- Need M

[1696] ]]

[1697] }

[1698] AdditionalRACH-ConfigList-r17 ::= SEQUENCE (SIZE(1..maxAdditionalRACH-r17)) OF AdditionalRACH-Config-r17

[1699] AdditionalRACH-Config-r17 ::= SEQUENCE {

[1700] rach-ConfigCommon-r17 RACH-ConfigCommon OPTIONAL, -- Need R

[1701] msgA-ConfigCommon-r17 MsgA-ConfigCommon-r16 OPTIONAL, -- Need R

[1702] ...

[1703] [[

[1704] rach-ConfigCommonSBFD-r19 SetupRelease { RACH-ConfigCommonSBFD-r19} OPTIONAL -- Need M

[1705] ]]

[1706] }

[1707] NumberOfMsg3-Repetitions-r17::= ENUMERATED {n1, n2, n3, n4, n7, n8, n12, n16}

[1708] RACH-ConfigCommonSBFD-r19 = SEQUENCE {

[1709] sbfd-RACH-SingleConfig-r19 ENUMERATED {enabled} OPTIONAL, -- Need R

[1710] sbfd-RACH-DualConfig-r19 SBFD-RACH-DualConfig-r19 OPTIONAL -- Need R

[1711] }

[1712] SBFD-RACH-DualConfig-r19 ::= SEQUENCE {

[1713] sbfd-AdditionalRACH-Config-r19 RACH-ConfigCommon OPTIONAL, -- Need R

[1714] sbfd-RACH-DualConfig-ValidROacrossSymbolTypes-r19 ENUMERATED {enabled} OPTIONAL -- Need R

[1715] }

[1716] -- TAG-BWP-UPLINKCOMMON-STOP

[1717] -- ASN1STOP

[1719] ### Additional RACH Configuration List

[1721] **additionalRACH-ConfigList**: A list of RACH configurations specific to a function or combination of functions, representing RACH configurations configured in addition to those configured by rach-ConfigCommon and msgA-ConfigCommon. The network associates all possible preambles of additional RACH configurations with one or more functions or combinations of functions. The network does not configure more than 16 entries in this list. If both rach-ConfigCommon and msgA-ConfigCommon are configured for a specific combination of functions, the network always provides it from the same additional RACH configuration.

[1723] ### MCS and Iteration Configuration

[1725] **mcs-Msg3-Repetitions**: A configuration of eight candidate MCS indices for PUSCH transfers scheduled by the RAR UL grant, with the CRC scrambled by TC-RNTI. Only the first four configured or default MCS indices are used for PUSCH transfers scheduled by the RAR UL grant. This field applies only when the UE selects a random access resource in this BWP that indicates Msg3 repetitions. If this field is missing, and a set of random access resources with Msg3 repetition indications is configured in BWP-UplinkCommon, the UE must apply the value {0, 1, 2, 3, 4, 5, 6, 7} (cf. TS 38.214

[19] , Klaus 6.1.4).

[1727] **preambleTransMax-Msg1-Repetition**: The maximum number of repetitions for Msg1 (2, 4, 8), which is the number of repetitions performed before switching to a higher number of repetitions (see TS 38.321 [3], Klaus 5.1.1). This field applies only when more than one number of repetitions is configured in a shared RO. Without this field, switching from a lower number of repetitions to a higher number of repetitions is not allowed.

[1729] ### PUCCH and PUSCH Configuration

[1731] **pucch-ConfigCommon**: Cell-specific parameters for PUCCH of this BWP.

[1732] **pusch-ConfigCommon**: Cell-specific parameters for this BWP's PUSCH.

[1734] ### RACH Configuration

[1736] **rach-ConfigCommon**: Configuration of cell-specific random access parameters used by the UE for contention-based and contention-free random access, as well as contention-based beam failure recovery in this BWP. The network configures SSB-based RA (and thus RACH-ConfigCommon) only if the linked DL BWP (with the same bwp-Id as the UL-BWP) is an initial DL BWP, a DL BWP containing an SSB connected to the initial DL BWP, a DL BWP connected to a non-cell-defined SSB, or (e) a RedCap-specific initial downlink BWP for a RedCap UE. The network configures rach-ConfigCommon (without suffix) and / or rach-ConfigCommon-r17 whenever contention-free 4-stage random access is configured, in which case the UE applies the configuration according to the set of RACH resources selected during RACH initialization (see TS 38.321 [3]). For a specific initial uplink BWP in RedCap, rach-ConfigCommon is always configured when msgA-ConfigCommon is configured in this BWP.

[1738] ### RSRP Threshold

[1740] **rsrp-ThresholdMsg1-RepetitionNum2, rsrp-ThresholdMsg1-RepetitionNum4, rsrp-ThresholdMsg1-RepetitionNum8**: These are the thresholds used by the UE to determine whether to select resources in this BWP that represent Msg1 repetition counts of 2, 4, or 8 (see TS 38.321 [3]). These values ​​apply to all BWPs and all RACH configurations. For a given Msg1 repetition count, this corresponding field is required if a set of random access resources with Msg1 repetition marks associated with this Msg1 repetition count and a set of random access resources without Msg1 repetition marks are configured in the BWP, or if a set of random access resources with Msg1 repetition marks associated with this Msg1 repetition count and a set of random access resources with Msg1 repetition marks associated with a lower repetition count are configured in the BWP. Otherwise, this field does not exist.

[1741] ### RSRP Threshold and SBFD Configuration

[1743] **rsrp-ThresholdMsg3**: A threshold used by the UE to determine whether to select resources in this BWP that indicate Msg3 repetition. This is specified in TS 38.321 [3]. This field is required if a set of random access resources with Msg3 repetition markings and a set of random access resources without Msg3 repetition markings are configured in the BWP. Otherwise, this field does not exist.

[1745] **sbfd-RACH-SingleConfig**: Indicates whether RACH configuration option 1 for SBFD random access operations is enabled. For details, see Klaus x in TS 38.211

[16] and Klaus y in TS 38.213

[13] .

[1747] **sbfd-RACH-DualConfig**: This field is used to configure dual RACH configurations and to configure random access parameters in SBFD symbols. By setting additional RACH configurations, refer to RACH configuration option 2 for SBFD random access operations. For details, refer to Klaus x in TS 38.211

[16] and Klaus y in TS 38.213

[13] .

[1749] **sbfd-RACH-DualConfig-ValidROacrossSymbolTypes**: Indicates whether the configured ROs starting from SBFD symbols and ending from non-SBFD symbols are valid for RACH configuration option 2 within the same slot or across different slots.

[1751] **sbfd-RSRP-ThresholdMsg1-RepetitionNum2, sbfd-RSRP-ThresholdMsg1-RepetitionNum4, sbfd-RSRP-ThresholdMsg1-RepetitionNum8**: These are the thresholds used by the UE to determine whether to select a resource representing Msg1 repetition counts of 2, 4, or 8 within the SBFD RO.

[1753] **sbfd-RSRP-ThresholdRO-Type**: This is the threshold used by a UE with SBFD capabilities to select the RACH opportunity type.

[1755] **sbfd-RSRP-ThresholdRO-TypeUsage**: Indicates how a UE with SBFD capability selects a RACH opportunity type using sbfd-RSRP-ThresholdRO-Type. If the value above is present, the UE with SBFD capability selects an SBFD RACH opportunity if the measured downlink path loss reference RSRP exceeds sbfd-RSRP-ThresholdRO-Type, and selects a non-SBFD RACH opportunity if the measured downlink path loss reference RSRP does not exceed sbfd-RSRP-ThresholdRO-Type. If the value below is present, the UE with SBFD capability selects an SBFD RACH opportunity if the measured downlink path loss reference RSRP is lower than sbfd-RSRP-ThresholdRO-Type, and selects a non-SBFD RACH opportunity if the measured downlink path loss reference RSRP is not lower than sbfd-RSRP-ThresholdRO-Type.

[1757] ### BWP-UplinkDedicated

[1759] IE BWP-UplinkDedicated is used to configure dedicated (UE-specific) parameters for uplink BWPs.

[1760] **BWP-UplinkDedicated Information Element**

[1761] -- ASN1START

[1762] -- TAG-BWP-UPLINKDEDICATED-START

[1764] BWP-UplinkDedicated ::= SEQUENCE {

[1765] pucch-Config SetupRelease { PUCCH-Config} OPTIONAL, -- Need M

[1766] pusch-Config SetupRelease { PUSCH-Config} OPTIONAL, -- Need M

[1767] configuredGrantConfig SetupRelease { ConfiguredGrantConfig} OPTIONAL, -- Need M

[1768] srs-Config SetupRelease { SRS-Config} OPTIONAL, -- Need M

[1769] beamFailureRecoveryConfig SetupRelease { BeamFailureRecoveryConfig} OPTIONAL, -- Cond SpCellOnly

[1770] ...,

[1771] ul-powerControl-r17 Uplink-powerControlId-r17 OPTIONAL, -- Cond NoTCI-PC

[1772] sbfd-Config2-Transmission-r19 ENUMERATED {enabled} OPTIONAL, -- Need S

[1773] sbfd-Config2-PUSCH-RBOffset-r19 INTEGER(0..maxNrofPhysicalResourceBlocks) OPTIONAL -- Need R

[1775] -- TAG-BWP-UPLINKDEDICATED-STOP

[1776] -- ASN1STOP

[1777] ### 구성된 Grant 및 PUCCH / PUSCH 구성

[1779] **configuredGrantConfig**: A configured Grant of Type 1 or Type 2. It can be configured for either a UL or a SUL, but for Type 1, both cannot be configured simultaneously. Except for synchronized reconfiguration, the NW does not reconfigure configuredGrantConfig when there is an active configured uplink Grant Type 2 (see TS 38.321 [3]). However, the NW can unconfigure configuredGrantConfig at any time. The network can configure a Grant configured in only one BWP using this field or configuredGrantConfigToAddModList.

[1781] **pucch-Config**: PUCCH configuration for a single BWP for the normal UL or SUL of a serving cell. If the UE is configured as a SUL, the network configures PUCCH on only one uplink (BWP) (normal UL or SUL). The network configures PUCCH-Config on at least the SpCell's non-initial BWP and on all BWPs of the PUCCH SCell. If supported by the UE, the network may configure one additional SCell in the cell group with PUCCH-Config (i.e., PUCCH SCell). If PUCCH cell switching is supported by the UE, the network may configure PUCCH-Config for two TDD serving cells within each PUCCH group. To support PUCCH cell switching with a SpCell within a PUCCH group, the TDD SpCell and one TDD SCell must have PUCCH-Config on the normal UL. To support PUCCH cell switching using only SCells within a PUCCH group, two TDD SCells must have PUCCH-Config in a normal UL.

[1783] The network can configure PUCCH for the BWP when setting up the BWP. The network can also add or remove PUCCH-Config during RRC reconfiguration, which allows moving PUCCH between uplink and SUL carriers along with reconfigurationWithSync (for SpCell or PUCCH SCell) or SCell removal and addition (for PUCCH SCell). In other cases, only modification of the previously configured PUCCH-Config is permitted.

[1785] If a (S)UL BWP of one serving cell is configured as PUCCH, all other (S)UL BWPs must also be configured as PUCCH.

[1787] ### PUSCH Configuration

[1789] **pusch-Config**: PUSCH configuration for a single BWP for the normal UL or SUL of the serving cell. If the UE is configured for SUL and there is a PUSCH-Config for both UL and SUL, the UL / SUL indication field within the DCI indicates which of the two to use. (Reference: TS 38.212

[17] , Klaus 7.3.1).

[1791] ### SBFD Configuration

[1793] **sbfd-Config2-Transmission**: Indicates that PUCCH and PUSCH transmissions are possible in different slots for SBFD symbols and non-SBFD symbols. This is configured for a given UL BWP (see TS 38.213

[13] , Klaus x and TS 38.214

[19] , Klaus y). If not enabled, Configuration 1 applies to PUCCH and PUSCH transmissions in a given UL BWP.

[1795] **sbfd-Config2-PUSCH-RBOffset**: Represents the RB offset for determining the start PRB of Type 2 configured Grant and dynamic Grant PUSCH transmissions for SBFD symbols in Configuration 2 (cf. TS 38.214

[19] , Klaus y).

[1797] ### SRS Configuration

[1799] **srs-Config**: Uplink sounding reference signal configuration.

[1801] ### Uplink Power Control

[1803] **ul-powerControl**: Configures power control parameters for PUCCH, PUSCH, and SRS when the UE is configured with unified TCI-StateType for this serving cell. For each serving cell, ul-powerControl is configured in all BWP-UplinkDedicated or not in any BWP-UplinkDedicated. If a unified TCI-StateRef within a BWP-UplinkDedicated refers to another serving cell, ul-powerControl is configured in all BWP-UplinkDedicated of these two serving cells or not in any BWP-UplinkDedicated of these two serving cells.

[1805] ### Configured Grant

[1807] **IE ConfiguredGrantConfig** is used to configure uplink transport without dynamic grants. The actual uplink grant can be configured via RRC (type 1) or provided via PDCCH (address is CS-RNTI) (type 2). Multiple configured grant configurations are possible within a single serving cell's BWP.

[1809] -- ASN1START

[1810] -- TAG-CONFIGUREDGRANTCONFIG-START

[1811] ConfiguredGrantConfig ::= SEQUENCE {

[1812] frequencyHopping ENUMERATED {intraSlot, interSlot} OPTIONAL, -- Need S

[1813] cg-DMRS-Configuration DMRS-UplinkConfig,

[1814] mcs-Table ENUMERATED {qam256, qam64LowSE} OPTIONAL, -- Need S

[1815] mcs-TableTransformPrecoder ENUMERATED {qam256, qam64LowSE} OPTIONAL, -- Need S

[1816] uci-OnPUSCH SetupRelease { CG-UCI-OnPUSCH} OPTIONAL, -- Need M

[1817] resourceAllocation ENUMERATED { resourceAllocationType0, resourceAllocationType1, dynamicSwitch},

[1818] rbg-Size ENUMERATED {config2} OPTIONAL, -- Need S

[1819] powerControlLoopToUse ENUMERATED {n0, n1},

[1820] p0-PUSCH-Alpha P0-PUSCH-AlphaSetId,

[1821] transformPrecoder ENUMERATED {enabled, disabled} OPTIONAL, -- Need S

[1822] nrofHARQ-Processes INTEGER(1..16),

[1823] repK ENUMERATED {n1, n2, n4, n8},

[1824] repK-RV ENUMERATED {s1-0231, s2-0303, s3-0000} OPTIONAL, -- Need R

[1825] periodicity ENUMERATED {

[1826] sym2, sym7, sym1x14, sym2x14, sym4x14, sym5x14, sym8x14, sym10x14, sym16x14, sym20x14,

[1827] sym32x14, sym40x14, sym64x14, sym80x14, sym128x14, sym160x14, sym256x14, sym320x14, sym512x14,

[1828] sym640x14, sym1024x14, sym1280x14, sym2560x14, sym5120x14,

[1829] sym6, sym1x12, sym2x12, sym4x12, sym5x12, sym8x12, sym10x12, sym16x12, sym20x12, sym32x12,

[1830] sym40x12, sym64x12, sym80x12, sym128x12, sym160x12, sym256x12, sym320x12, sym512x12, sym640x12,

[1831] sym1280x12, sym2560x12

[1832] },

[1833] configuredGrantTimer INTEGER (1..64) OPTIONAL, -- Need R

[1834] rrc-ConfiguredUplinkGrant SEQUENCE {

[1835] timeDomainOffset INTEGER (0..5119),

[1836] timeDomainAllocation INTEGER (0..15),

[1837] frequencyDomainAllocation BIT STRING (SIZE(18)),

[1838] antennaPort INTEGER (0..31),

[1839] dmrs-SeqInitialization INTEGER (0..1) OPTIONAL, -- Need R

[1840] precodingAndNumberOfLayers INTEGER (0..63),

[1841] srs-ResourceIndicator INTEGER (0..15) OPTIONAL, -- Need R

[1842] mcsAndTBS INTEGER (0..31),

[1843] frequencyHoppingOffset INTEGER (1.. maxNrofPhysicalResourceBlocks-1) OPTIONAL, -- Need R

[1844] pathlossReferenceIndex INTEGER (0..maxNrofPUSCH-PathlossReferenceRSs-1),

[1845] ...,

[1846] [[

[1847] pusch-RepTypeIndicator-r16 ENUMERATED {pusch-RepTypeA,pusch-RepTypeB} OPTIONAL, -- Need M

[1848] frequencyHoppingPUSCH-RepTypeB-r16 ENUMERATED {interRepetition, interSlot} OPTIONAL, -- Cond RepTypeB

[1849] timeReferenceSFN-r16 ENUMERATED {sfn512} OPTIONAL -- Need S

[1850] ]],

[1851] [[

[1852] pathlossReferenceIndex2-r17 INTEGER (0..maxNrofPUSCH-PathlossReferenceRSs-1) OPTIONAL, -- Need R

[1853] srs-ResourceIndicator2-r17 INTEGER (0..15) OPTIONAL, -- Need R

[1854] precodingAndNumberOfLayers2-r17 INTEGER (0..63) OPTIONAL, -- Need R

[1855] timeDomainAllocation-v1710 INTEGER (16..63) OPTIONAL, -- Need M

[1856] timeDomainOffset-r17 INTEGER (0..40959) OPTIONAL, -- Need R

[1857] cg-SDT-Configuration-r17 CG-SDT-Configuration-r17 OPTIONAL -- Need M

[1858] ]],

[1859] [[

[1860] srs-ResourceSetId-r18 SRS-ResourceSetId OPTIONAL, -- Need R

[1861] cg-LTM-Configuration-r18 CG-RRC-Configuration-r18 OPTIONAL, -- Cond LTM

[1862] cg-SDT-PeriodicityExt-r18 ENUMERATED {

[1863] sym1x14x1280, sym2x14x1280, sym4x14x1280 , sym8x14x1280, sym16x14x1280,

[1864] sym32x14x1280, sym48x14x1280, sym64x14x1280, sym96x14x1280, sym128x14x1280,

[1865] sym192x14x1280, sym240x14x1280, sym256x14x1280, sym384x14x1280, sym472x14x1280,

[1866] sym480x14x1280, sym512x14x1280, sym768x14x1280, sym944x14x1280, sym960x14x1280,

[1867] sym1408x14x1280, sym1536x14x1280, sym1888x14x1280, sym1920x14x1280,

[1868] sym2816x14x1280, sym3072x14x1280, sym3776x14x1280, sym5632x14x1280,

[1869] sym6144x14x1280, sym7552x14x1280, sym7680x14x1280, sym11264x14x1280,

[1870] sym15104x14x1280, sym15360x14x1280, sym22528x14x1280, sym30208x14x1280,

[1871] sym45056x14x1280, sym60416x14x1280, sym90112x14x1280, sym180224x14x1280,

[1872] sym4x12x1280, sym8x12x1280, sym16x12x1280, sym32x12x1280, sym192x12x1280,

[1873] sym384x12x1280, sym960x12x1280, sym1888x12x1280, sym3776x12x1280,

[1874] sym5632x12x1280, sym11264x12x1280, spare13, spare12, spare11, spare10, spare9,

[1875] spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1

[1876] } OPTIONAL, -- Cond CG-SDT1

[1877] timeReferenceHyperSFN-r18 INTEGER (0..1023) OPTIONAL, -- Cond CG-SDT2

[1878] cg-RRC-Configuration-r18 CG-RRC-Configuration-r18 OPTIONAL, -- Cond RACH-LessHO

[1879] applyIndicatedTCI-State-r18 ENUMERATED {first, second, both, spare1} OPTIONAL -- Need R

[1880] ]],

[1881] [[

[1882] sbfd-Config2-PUSCH-RBoffset-r19 INTEGER (0..maxNrofPhysicalResourceBlocks) OPTIONAL, -- Need R

[1883] symbolType-r19 ENUMERATED {sbfd, non-sbfd} OPTIONAL, -- Need R

[1884] frequencyHoppingOffset-SBFD-r19 INTEGER (1.. maxNrofPhysicalResourceBlocks-1) OPTIONAL, -- Need R

[1885] pusch-MutingResources-r19 PUSCH-MutingResources-r19 OPTIONAL -- Need R

[1886] ]]

[1888] } OPTIONAL, -- Need R

[1889] ...,

[1891] }

[1892] -- TAG-CONFIGUREDGRANTCONFIG-STOP

[1893] -- ASN1STOP

[1894] ### Common Parameters

[1896] **cg-StartingOffsets**: This field does not apply to UEs that can act as starters in semi-static channel access mode. In other words, it does not apply to UEs configured with UE FFP parameters (e.g., period, offset), and the UE can share the GNB's COT regardless of whether it can start its own COT.

[1898] **dmrs-SeqInitialization**: The network configures this field if transformPrecoder is disabled or the value of sdt-NrofDMRS-Sequences is set to 1. Otherwise, this field does not exist.

[1900] **frequencyDomainAllocation**: Indicates frequency domain resource allocation. (References: TS 38.214

[19] , Klaus 6.1.2 and TS 38.212

[17] , Klaus 7.3.1).

[1902] **frequencyHopping**: A value of intraSlot enables 'intra-slot frequency hopping', and a value of interSlot enables 'inter-slot frequency hopping'. If this field is missing, frequency hopping is not configured. The frequencyHopping field applies to the configured Grant for 'pusch-RepTypeA' (cf. TS 38.214

[19] , Klaus 6.3.1).

[1904] **frequencyHoppingOffset**: Frequency hopping offset used when frequency hopping is enabled (see TS 38.214

[19] , Klaus 6.1.2 and Klaus 6.3).

[1907] ***frequencyHoppingOffset-SBFD**: Configures the frequency hopping offset for a Type 1 configured Grant PUSCH in the SBFD symbol (see TS 38.214

[19] ).

[1909] **mcs-Table**: Indicates the MCS table that the UE will use for PUSCH without conversion precoding. If this field is missing, the UE applies the value qam64.

[1911] **p0-PUSCH-Alpha**: This is the index of the P0-PUSCH-AlphaSet to be used in this configuration.

[1913] **pusch-MutingResources**: Used to configure the time and frequency positions of UL muting resources for a Type 1 configured Grant PUSCH transmission. (References: Klaus x in TS 38.211

[16] and Klaus y in TS 38.214

[19] ).

[1915] **rbg-Size**: Selection between Configuration 1 and Configuration 2 for RGB size for PUSCH. If resourceAllocation is set to resourceAllocationType1, the UE does not apply this field. Otherwise, the UE applies the value config1 when this field is absent. Note: rbg-Size is used when the transformPrecoder parameter is disabled.

[1917] **repK-RV**: The duplicate version (RV) sequence to use. (Reference: TS 38.214

[19] , Klaus 6.1.2). The network configures this field when iteration is used, that is, when repK is set to n2, n4, or n8. If cg-RetransmissionTimer is configured, this field is not configured. Otherwise, this field does not exist.

[1919] **repK**: Number of iterations K. (Reference: TS 38.214

[19] ). If repK-v1710 exists, the UE must ignore repK(no suffix).

[1921] **resourceAllocation**: Configuration of resource allocation type 0 and resource allocation type 1. Without grant in type 1 uplink data transfer, resourceAllocation must be resourceAllocationType0 or resourceAllocationType1.

[1923] **rrc-ConfiguredUplinkGrant**: Configuration for sending a fully RRC-configured UL grant (Type 1). If this field is missing, the UE uses a UL grant addressed to the CS-RNTI in the DCI (Type 2).

[1925] **sbfd-Config2-PUSCH-RBOffset**: Indicates the RB offset for determining the start PRB of Type 1 configured Grant and dynamic Grant PUSCH transfers in the SBFD symbol of Configuration 2 (cf. TS 38.214

[19] , Klaus y).

[1927] **sequenceOffsetForRV**: Configures the RV offset for the start RV for the first iteration (for PUSCH iteration type B in the first actual iteration). This is configured by using 'codebook' or 'noncodebook' in srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2.

[1929] **srs-ResourceSetId**: Represents the set of associated SRS resources for PUSCH + PUSCH simultaneous uplink transmission of CG type 1 PUSCH. The network does not configure this field if cg-RRC-Configuration is configured.

[1930] ### SRS Resources and Related Configuration

[1932] **srs-ResourceIndicator, srs-ResourceIndicator-v1850**: Indicates the SRS resources to be used (see TS 38.212

[17] , Klaus 7.3.1.1.2 and TS 38.214

[19] , Klaus 6.1.2.3). The network does not configure this field for CG-SDT or if cg-RRC-Configuration is configured. The field srs-ResourceIndicator-v1850 is configured only when 8 antenna ports are configured (see TS 38.214

[19] , Klaus 6.1.1.2). The network does not configure srs-ResourceIndicator and srs-ResourceIndicator-v1850 simultaneously.

[1934] **srs-ResourceIndicator2**: Indicates the SRS resource to be used for the second set of SRS resources. If this field exists, srs-ResourceIndicator is used for the first set of SRS resources. The network does not configure this field if cg-RRC-Configuration is configured.

[1936] **startingFromRV0**: This field is used to determine the initial transmission opportunity of a transmission block for a given RV sequence. (Reference: TS 38.214

[19] , Klaus 6.1.2.3.1). The network does not configure this field if cg-RetransmissionTimer-r16 is configured for CG operations.

[1938] *

[1939] **symbolType**: Configures valid symbol types for Type 1 CG PUSCH for SBFD Configuration 1. The network does not configure this field if SBFD Configuration 2 is enabled for UL BWP. (Reference: TS 38.214

[19] , Klaus 6.1.3)

[1941] **timeDomainAllocation, timeDomainAllocation-v1710**: Indicates a combination of start symbol, length, and PUSCH mapping type. (References: TS 38.214

[19] , Klaus 6.1.2 and TS 38.212

[17] , Klaus 7.3.1).

[1942] If the timeDomainAllocation-v1710 field exists, the UE must ignore the timeDomainAllocation field (without a suffix).

[1944] **timeDomainOffset**: The offset relative to the reference SFN indicated by timeReferenceSFN. (Reference: TS 38.321 [3], Klaus 5.8.2). timeDomainOffset-r17 applies only to 480 kHz and 960 kHz. If timeDomainOffset-r17 is present, the UE must ignore timeDomainOffset(no suffix).

[1946] **timeReferenceHyperSFN**: Represents the H-SFN used to determine the offset of a resource in the time domain. The UE uses the H-SFN closest to the indicated number before the configured Grant configuration is received. (Reference: TS 38.321 [3], Klaus 5.8.2). If the timeReferenceHyperSFN field does not exist, the reference hyper-SFN is 0.

[1948] **timeReferenceSFN**: Indicates the SFN used to determine the offset of a resource in the time domain. The UE uses the SFN closest to the indicated number before the configured Grant configuration is received. (Reference: TS 38.321 [3], Klaus 5.8.2). If the timeReferenceSFN field does not exist, the reference SFN is 0.

[1950] **transformPrecoder**: Enables or disables transform precoding for Type 1 and Type 2. If this field is missing, the UE enables or disables transform precoding based on the msg3-transformPrecoder field of RACH-ConfigCommon included directly within the BWP configuration. (Reference: TS 38.214

[19] , Klaus 6.1.3).

[1952] **uci-OnPUSCH**: Selection and configuration between dynamic and semi-static beta offsets. For Type 1 uplink data transmission without Grant, uci-OnPUSCH must be set to semi-static. The network does not configure this field for the CG-SDT.

[1954] **IE PUCCH-Config** is used to configure UE-specific PUCCH parameters (for each BWP).

[1955] PUCCH-Config information element

[1956] -- ASN1START

[1957] -- TAG-PUCCH-CONFIG-START

[1958] PUCCH-Config ::= SEQUENCE {

[1959] resourceSetToAddModList SEQUENCE (SIZE (1..maxNrofPUCCH-ResourceSets)) OF PUCCH-ResourceSet OPTIONAL, -- Need N

[1960] resourceSetToReleaseList SEQUENCE (SIZE (1..maxNrofPUCCH-ResourceSets)) OF PUCCH-ResourceSetId OPTIONAL, -- Need N

[1961] resourceToAddModList SEQUENCE (SIZE (1..maxNrofPUCCH-Resources)) OF PUCCH-Resource OPTIONAL, -- Need N

[1962] resourceToReleaseList SEQUENCE (SIZE (1..maxNrofPUCCH-Resources)) OF PUCCH-ResourceId OPTIONAL, -- Need N

[1963] format1 SetupRelease { PUCCH-FormatConfig} OPTIONAL, -- Need M

[1964] format2 SetupRelease { PUCCH-FormatConfig} OPTIONAL, -- Need M

[1965] format3 SetupRelease { PUCCH-FormatConfig} OPTIONAL, -- Need M

[1966] format4 SetupRelease { PUCCH-FormatConfig} OPTIONAL, -- Need M

[1967] schedulingRequestResourceToAddModList SEQUENCE (SIZE (1..maxNrofSR-Resources)) OF SchedulingRequestResourceConfig

[1968] OPTIONAL, -- Need N

[1969] schedulingRequestResourceToReleaseList SEQUENCE (SIZE (1..maxNrofSR-Resources)) OF SchedulingRequestResourceId

[1970] OPTIONAL, -- Need N

[1971] multi-CSI-PUCCH-ResourceList SEQUENCE (SIZE (1..2)) OF PUCCH-ResourceId OPTIONAL, -- Need M

[1972] dl-DataToUL-ACK SEQUENCE (SIZE (1..8)) OF INTEGER (0..15) OPTIONAL, -- Need M

[1973] spatialRelationInfoToAddModList SEQUENCE (SIZE (1..maxNrofSpatialRelationInfos)) OF PUCCH-SpatialRelationInfo

[1974] OPTIONAL, -- Need N

[1975] spatialRelationInfoToReleaseList SEQUENCE (SIZE (1..maxNrofSpatialRelationInfos)) OF PUCCH-SpatialRelationInfoId

[1976] OPTIONAL, -- Need N

[1977] pucch-PowerControl PUCCH-PowerControl OPTIONAL, -- Need M

[1978] ...,

[1979] [[

[1980] resourceToAddModListExt-v1610 SEQUENCE (SIZE (1..maxNrofPUCCH-Resources)) OF PUCCH-ResourceExt-v1610 OPTIONAL, -- Need N

[1981] dl-DataToUL-ACK-r16 SetupRelease { DL-DataToUL-ACK-r16} OPTIONAL, -- Need M

[1982] ul-AccessConfigListDCI-1-1-r16 SetupRelease { UL-AccessConfigListDCI-1-1-r16} OPTIONAL, -- Need M

[1983] subslotLengthForPUCCH-r16 CHOICE {

[1984] normalCP-r16 ENUMERATED {n2,n7},

[1985] extendedCP-r16 ENUMERATED {n2,n6}

[1986] } OPTIONAL, -- Need R

[1987] dl-DataToUL-ACK-DCI-1-2-r16 SetupRelease { DL-DataToUL-ACK-DCI-1-2-r16} OPTIONAL, -- Need M

[1988] numberOfBitsForPUCCH-ResourceIndicatorDCI-1-2-r16 INTEGER (0..3) OPTIONAL, -- Need R

[1989] dmrs-UplinkTransformPrecodingPUCCH-r16 ENUMERATED {enabled} OPTIONAL, -- Cond PI2-BPSK

[1990] spatialRelationInfoToAddModListSizeExt-v1610 SEQUENCE (SIZE (1..maxNrofSpatialRelationInfosDiff-r16)) OF PUCCH-SpatialRelationInfo

[1991] OPTIONAL, -- Need N

[1992] spatialRelationInfoToReleaseListSizeExt-v1610 SEQUENCE (SIZE (1..maxNrofSpatialRelationInfosDiff-r16)) OF PUCCH-SpatialRelationInfoId

[1993] OPTIONAL, -- Need N

[1994] spatialRelationInfoToAddModListExt-v1610 SEQUENCE (SIZE (1..maxNrofSpatialRelationInfos-r16)) OF PUCCH-SpatialRelationInfoExt-r16

[1995] OPTIONAL, -- Need N

[1996] spatialRelationInfoToReleaseListExt-v1610 SEQUENCE (SIZE (1..maxNrofSpatialRelationInfos-r16)) OF

[1997] PUCCH-SpatialRelationInfoId-r16 OPTIONAL, -- Need N

[1998] resourceGroupToAddModList-r16 SEQUENCE (SIZE (1..maxNrofPUCCH-ResourceGroups-r16)) OF PUCCH-ResourceGroup-r16

[1999] OPTIONAL, -- Need N

[2000] resourceGroupToReleaseList-r16 SEQUENCE (SIZE (1..maxNrofPUCCH-ResourceGroups-r16)) OF PUCCH-ResourceGroupId-r16

[2001] OPTIONAL, -- Need N

[2002] sps-PUCCH-AN-List-r16 SetupRelease { SPS-PUCCH-AN-List-r16} OPTIONAL, -- Need M

[2003] schedulingRequestResourceToAddModListExt-v1610 SEQUENCE (SIZE (1..maxNrofSR-Resources)) OF SchedulingRequestResourceConfigExt-v1610

[2004] OPTIONAL -- Need N

[2005] ]],

[2006] ]],

[2007] [[

[2008] schedulingRequestResourceToAddModListExt-v19xy SEQUENCE (SIZE (1..maxNrofSR-Resources)) OF SchedulingRequestResourceConfigExt-v19xy

[2009] OPTIONAL, -- Need N

[2010] resourceToAddModListExt-v19xy SEQUENCE (SIZE (1..maxNrofPUCCH-Resources)) OF PUCCH-ResourceExt-v19xy

[2011] OPTIONAL -- Need N

[2012] ]]

[2013] PUCCH-FormatConfig ::= SEQUENCE {

[2014] interslotFrequencyHopping ENUMERATED {enabled} OPTIONAL, -- Need R

[2015] additionalDMRS ENUMERATED {true} OPTIONAL, -- Need R

[2016] maxCodeRate PUCCH-MaxCodeRate OPTIONAL, -- Need R

[2017] nrofSlots ENUMERATED {n2,n4,n8} OPTIONAL, -- Need S

[2018] pi2BPSK ENUMERATED {enabled} OPTIONAL, -- Need R

[2019] simultaneousHARQ-ACK-CSI ENUMERATED {true} OPTIONAL -- Need R

[2020] }

[2021] -- A set with one or more PUCCH resources

[2022] PUCCH-ResourceSet ::= SEQUENCE {

[2023] pucch-ResourceSetId PUCCH-ResourceSetId,

[2024] resourceList SEQUENCE (SIZE (1..maxNrofPUCCH-ResourcesPerSet)) OF PUCCH-ResourceId,

[2025] maxPayloadSize INTEGER (4..256) OPTIONAL -- Need R

[2026] }

[2027] PUCCH-ResourceSetId ::= INTEGER (0..maxNrofPUCCH-ResourceSets-1)

[2028] PUCCH-Resource ::= SEQUENCE {

[2029] pucch-ResourceId PUCCH-ResourceId,

[2030] startingPRB PRB-Id,

[2031] intraSlotFrequencyHopping ENUMERATED { enabled} OPTIONAL, -- Need R

[2032] secondHopPRB PRB-Id OPTIONAL, -- Need R

[2033] format CHOICE {

[2034] format0 PUCCH-format0,

[2035] format1 PUCCH-format1,

[2036] format2 PUCCH-format2,

[2037] format3 PUCCH-format3,

[2038] format4 PUCCH-format4

[2039] }

[2040] }

[2041] PUCCH-ResourceExt-v19xy ::= SEQUENCE {

[2042] startingPRB-SBFD-r19 PRB-Id OPTIONAL, -- Need R

[2043] secondHopPRB-SBFD-r19 PRB-Id OPTIONAL -- Need R

[2044] }

[2045] PUCCH-ResourceId ::= INTEGER (0..maxNrofPUCCH-Resources-1)

[2046] PUCCH-format0 ::= SEQUENCE {

[2047] initialCyclicShift INTEGER(0..11),

[2048] nrofSymbols INTEGER (1..2),

[2049] startingSymbolIndex INTEGER(0..13)

[2050] }

[2051] PUCCH-format1 ::= SEQUENCE {

[2052] initialCyclicShift INTEGER(0..11),

[2053] nrofSymbols INTEGER (4..14),

[2054] startingSymbolIndex INTEGER(0..10),

[2055] timeDomainOCC INTEGER(0..6)

[2056] }

[2057] PUCCH-format2 ::= SEQUENCE {

[2058] nrofPRBs INTEGER (1..16),

[2060] * nrofSymbols INTEGER (1..2),

[2061] startingSymbolIndex INTEGER(0..13)

[2062] }

[2063] PUCCH-format3 ::= SEQUENCE {

[2064] nrofPRBs INTEGER (1..16),

[2066] * nrofSymbols INTEGER (4..14),

[2067] startingSymbolIndex INTEGER(0..10)

[2068] }

[2069] PUCCH-format4 ::= SEQUENCE {

[2070] nrofSymbols INTEGER (4..14),

[2072] * occ-Length ENUMERATED {n2,n4},

[2073] occ-Index ENUMERATED {n0,n1,n2,n3},

[2074] startingSymbolIndex INTEGER(0..10)

[2075] }

[2076] DL-DataToUL-ACK-r16 ::= SEQUENCE (SIZE (1..8)) OF INTEGER (-1..15)

[2077] -- TAG-PUCCH-CONFIG-STOP

[2078] -- ASN1STOP

[2079] dl-DataToUL-ACK and dl-DataToUL-ACK-DCI-1-2 are timing lists for DL ​​ACKs for PDSCH. dl-DataToUL-ACK applies to DCI format 1_1, and dl-DataToUL-ACK-DCI-1-2 applies to DCI format 1_2. dl-DataToUL-ACK-v1700 applies to non-terrestrial networks (NTN), and dl-DataToUL-ACK-r17 applies to FR2-2. dl-DataToUL-ACK-r18 is used in the air (ATG).

[2081] If dl-DataToUL-ACK-r16, dl-DataToUL-ACK-r17, dl-DataToUL-ACK-v1700, or dl-DataToUL-ACK-r18 is transmitted as a signal, the user device (UE) must ignore dl-DataToUL-ACK without a suffix. A value of -1 indicates that A / N feedback timing is not explicitly included in the PDSCH reservation.

[2083] dl-DataToUL-ACK-r17 and dl-DataToUL-ACK-DCI-1-2-r17 apply only to subcarrier intervals (SCS) of 480 kHz or 960 kHz. dl-DataToUL-ACK-r18 applies to DCI format 1_1, and dl-DataToUL-ACK-DCI-1-2-r18 applies to DCI format 1_2.

[2085] **format0**: Parameter common to all PUCCH resources of format 0.

[2087] **format1**: Parameters common to all PUCCH resources of format 1.

[2089] **format2**: Parameters common to all PUCCH resources of format 2.

[2091] **format3**: Parameters common to all PUCCH resources of format 3.

[2093] **format4**: Parameters common to all PUCCH resources of format 4.

[2095] **mappingPattern**: Indicates whether the UE must follow a periodic mapping pattern or a sequential mapping pattern.

[2097] **pucch-PowerControl**: Sets power control parameters for PUCCH transmission.

[2099] **resourceToAddModList, resourceToAddModListExt, resourceToReleaseList**: A list for adding and releasing PUCCH resources applied to UL BWPs and serving cells where PUCCH-Config is defined.

[2101] **sps-PUCCH-AN-List**: Represents a list of PUCCH resources for DL ​​SPS HARQ ACK.

[2103] **nrofSlots**: The number of slots with the same PUCCH.

[2105] **nrofPRBs**: Indicates the number of PRBs used for each PUCCH resource for the PUCCH format.

[2107] **pucch-ResourceId**: Identifier of the PUCCH resource.

[2109] **secondHopPRB-SBFD**: Represents the second-hop PRB of the PUCCH resource in the SBFD symbol.

[2111] **startingPRB-SBFD**: Represents the starting PRB of the PUCCH resource in the SBFD symbol.

[2113] **RACH-ConfigDedicated**: Used to specify dedicated random access parameters.

[2114] RACH-ConfigDedicated information element

[2115] -- ASN1START

[2116] -- TAG-RACH-CONFIGDEDICATED-START

[2117] RACH-ConfigDedicated ::= SEQUENCE {

[2118] cfra CFRA OPTIONAL, -- Need S

[2119] ra-Prioritization RA-Prioritization OPTIONAL, -- Need N

[2121] * ...,

[2122] [[

[2123] ra-PrioritizationTwoStep-r16 RA-Prioritization OPTIONAL, -- Need N

[2124] cfra-TwoStep-r16 CFRA-TwoStep-r16 OPTIONAL -- Need S

[2126] * ]],

[2127] [[

[2128] ra-OccasionType-r19 ENUMERATED {SBFD} OPTIONAL -- Need S

[2129] ]]

[2130] }

[2131] CFRA ::= SEQUENCE {

[2132] occasions SEQUENCE {

[2133] rach-ConfigGeneric RACH-ConfigGeneric,

[2134] ssb-perRACH-Occasion ENUMERATED {oneEighth, oneFourth, oneHalf, one, two, four, eight, sixteen}

[2135] OPTIONAL -- Cond Mandatory

[2136] } OPTIONAL, -- Need S

[2137] resources CHOICE {

[2138] ssb SEQUENCE {

[2139] ssb-ResourceList SEQUENCE (SIZE(1..maxRA-SSB-Resources)) OF CFRA-SSB-Resource,

[2140] ra-ssb-OccasionMaskIndex INTEGER (0..15)

[2141] },

[2142] csirs SEQUENCE {

[2143] csirs-ResourceList SEQUENCE (SIZE(1..maxRA-CSIRS-Resources)) OF CFRA-CSIRS-Resource,

[2144] rsrp-ThresholdCSI-RS RSRP-Range

[2145] }

[2146] },

[2147] ...,

[2148] [[

[2149] totalNumberOfRA-Preambles INTEGER (1..63) OPTIONAL -- Cond Occasions

[2150] ]],

[2151] [[

[2152] msg1-RepetitionNum-r18 ENUMERATED {n2, n4, n8, spare1} OPTIONAL -- Cond 4StepCFRArep

[2153] ]]

[2154] }

[2155] CFRA-SSB-Resource ::= SEQUENCE {

[2156] ssb SSB-Index,

[2157] ra-PreambleIndex INTEGER (0..63),

[2158] ...,

[2159] [[

[2160] msgA-PUSCH-Resource-Index-r16 INTEGER (0..3071) OPTIONAL -- Cond 2StepCFRA

[2161] ]]

[2162] }

[2163] CFRA-CSIRS-Resource ::= SEQUENCE {

[2164] csi-RS CSI-RS-Index,

[2165] ra-OccasionList SEQUENCE (SIZE(1..maxRA-OccasionsPerCSIRS)) OF INTEGER (0..maxRA-Occasions-1),

[2166] ra-PreambleIndex INTEGER (0..63),

[2167] ...

[2168] }

[2169] -- TAG-RACH-CONFIGDEDICATED-STOP

[2170] -- ASN1STOP

[2171] **csi-RS**: ID of the CSI-RS resource defined in the measurement object associated with this document cell.

[2173] **ra-OccasionList**: RA opportunities to use when performing CF-RA when the UE selects a candidate beam identified by this CSI-RS. The network ensures that the provided RA opportunity index is configured by prach-ConfigurationIndex and msg1-FDM. Each RACH opportunity is numbered sequentially, first in increasing order of the frequency resource index of frequency multiplexing PRACH opportunities; second in increasing order of the time resource index of time multiplexing PRACH opportunities within the PRACH slot; and third in increasing order of the index for the PRACH slot.

[2175] **ra-PreambleIndex**: The RA preamble index to use in the RA opportunity associated with this CSI-RS.

[2177] **msg1-RepetitionNum**: Indicates the MSG1 repetition number used for the contention-free 4-step random access type of TS 38.321 [3]. If this field is missing, the UE performs contention-free 4-step random access without MSG1 repetition.

[2179] **Occasions**: RA opportunities for non-contention random access. If this field is missing, the UE uses the RA opportunities configured in RACH-ConfigCommon from the first active UL BWP.

[2181] **ra-ssb-OccasionMaskIndex**: An explicitly signaled PRACH mask index for RA resource selection in TS 38.321 [3]. This mask is valid for all SSB resources signaled in ssb-ResourceList. If the msg1-RepetitionNum field included in CFRA is configured, the UE must ignore this field.

[2183] **rach-ConfigGeneric**: Configuration of contention-free random access opportunities for CFRA. The UE must ignore preambleReceivedTargetPower, preambleTransMax, powerRampingStep, and ra-ResponseWindow signaled within this field and use the corresponding values ​​provided by RACH-ConfigCommon.

[2184] **ssb-perRACH-Occasion**: Number of SSBs per RACH opportunity.

[2186] *

[2187] **totalNumberOfRA-Preambles**: The total number of preambles used for contention-free random access to RACH resources defined in CFRA. Preambles used for other purposes (e.g., for SI requests) are excluded. If this field is missing but the occasions field is present, the UE can assume that all 64 preambles are for RA. The setting must be consistent with the ssb-perRACH-Occasion setting and, if present, must be a multiple of the number of SSBs per RACH opportunity.

[2189] **ra-PreambleIndex**: The preamble index to use when performing CF-RA when the UE selects the candidate beam identified by this SSB.

[2191] **Ssb**: ID of the SSB transmitted by this serving cell.

[2193] **Cfra**: Parameter for non-contention random access to a specific target cell. If this field and cfra-TwoStep are absent, the UE performs contention-based random access.

[2195] **ra-OccasionType**: Indicates the SBFD RACH opportunity type of CFRA to be used by UEs with SBFD capabilities. If this field is missing, a non-SBFD RACH opportunity type is used.

[2197] **ra-prioritization**: A parameter applied to the priority random access procedure for a specific target cell (for details, see TS 38.321 [3], Clause 5.1.1).

[2199] **RACH-ConfigGeneric**: An information element used to specify random access parameters for general random access and beam failure recovery.

[2200] -- ASN1START

[2201] -- TAG-RACH-CONFIGGENERIC-START

[2202] RACH-ConfigGeneric ::= SEQUENCE {

[2203] prach-ConfigurationIndex INTEGER (0..255);

[2204] msg1-FDM ENUMERATED {one, two, four, eight},

[2205] msg1-FrequencyStart INTEGER (0..maxNrofPhysicalResourceBlocks-1);

[2206] zeroCorrelationZoneConfig INTEGER(0..15);

[2207] preambleReceivedTargetPower INTEGER (-202..-60);

[2208] preambleTransMax ENUMERATED {n3, n4, n5, n6, n7, n8, n10, n20, n50, n100, n200},

[2209] powerRampingStep ENUMERATED {dB0, dB2, dB4, dB6},

[2210] ra-ResponseWindow ENUMERATED {sl1, sl2, sl4, sl8, sl10, sl20, sl40, sl80},

[2211] ...,

[2212] [[

[2213] prach-ConfigurationPeriodScaling-IAB-r16 ENUMERATED {scf1,scf2,scf4,scf8,scf16,scf32,scf64} OPTIONAL, -- Need R

[2214] prach-ConfigurationFrameOffset-IAB-r16 INTEGER (0..63) OPTIONAL, -- Need R

[2215] prach-ConfigurationSOffset-IAB-r16 INTEGER (0..39) OPTIONAL, -- Need R

[2216] ra-ResponseWindow-v1610 ENUMERATED { sl60, sl160} OPTIONAL, -- Need R

[2217] prach-ConfigurationIndex-v1610 INTEGER (256..262) OPTIONAL -- Need R

[2218] ]],

[2219] [[

[2220] ra-ResponseWindow-v1700 ENUMERATED {sl240, sl320, sl640, sl960, sl1280, sl1920, sl2560} OPTIONAL -- Need R

[2221] ]],

[2222] [[

[2223] sbfd-RACH-SingleConfig-preambleReceivedTargetPower-r19 INTEGER (-202..-60) OPTIONAL -- Need R

[2224] ]]

[2226] }

[2228] -- TAG-RACH-CONFIGGENERIC-STOP

[2229] -- ASN1STOP

[2230] **msg1-FDM**: Number of PRACH transmission opportunities FDMed at a time (for details see TS 38.211

[16] , Clause 6.3.3.2).

[2232] **msg1-FrequencyStart**: Offset of the lowest PRACH transmission opportunity in the frequency domain for PRB 0. This value is configured so that the corresponding RACH resource is fully contained within the bandwidth of the UL BWP (for details, see TS 38.211

[16] , Clause 6.3.3.2).

[2234] **powerRampingStep**: Power ramping step for PRACH (see TS 38.321 [3], Clause 5.1.3 for details). This field is set to the same value for different iteration numbers associated with a specific FeatureCombination.

[2236] **prach-ConfigurationIndex**: PRACH configuration index. The prach-ConfigurationIndex configured under beamFailureRecoveryConfig may only be in short preamble format (see TS 38.211

[16] , clause 6.3.3.2 for details). If the prach-ConfigurationIndex-v1610 field exists, the UE must ignore the value provided for prach-ConfigurationIndex (no suffix).

[2238] **preambleReceivedTargetPower**: Target power level on the network receiver side (see TS 38.213

[13] , Clause 7.4, TS 38.321 [3], Clauses 5.1.2, 5.1.3 for details). Only multiples of 2 dBm can be selected (e.g., -202, -200, -198, etc.). This field is set to the same value for different repetition numbers associated with a specific FeatureCombination.

[2240] **preambleTransMax**: The maximum number of RA preamble transmissions performed before declaring failure (see TS 38.321 [3], provisions 5.1.4, 5.1.5 for details). If rach-ConfigGeneric is included within EarlyUL-SyncConfig IE, the UE must ignore this field.

[2242] **ra-ResponseWindow**: Msg2 (RAR) window length expressed in slot numbers. The network configures a value of 10 ms or less when Msg2 is transmitted in licensed spectrum and 40 ms or less when Msg2 is transmitted via shared spectrum channel access (see TS 38.321 [3], Clause 5.1.4 for details). The UE must ignore this field if it is included in SCellConfig. If ra-ResponseWindow-v1610 or ra-ResponseWindow-v1700 is transmitted as a signal, the UE must ignore ra-ResponseWindow (no suffix). The ra-ResponseWindow-v1700 field applies to SCS 480 kHz and SCS 960 kHz. If rach-ConfigGeneric is included within EarlyUL-SyncConfig IE, the UE must ignore this field.

[2243] **sbfd-RACH-SingleConfig-preambleReceivedTargetPower**: Configures the preambleReceivedTargetPower of the SBFD RACH configuration option 1. (For details, see provision x of TS 38.211

[16] and provision y of TS 38.213

[13] ).

[2245] **SchedulingRequestResourceConfig**: Determines the physical layer resources of PUCCH to which a UE can send dedicated scheduling requests (D-SR) (for details, see TS 38.213

[13] , Clause 9.2.4).

[2246] -- ASN1START

[2247] -- TAG-SCHEDULINGREQUESTRESOURCECONFIG-START

[2248] SchedulingRequestResourceConfig ::= SEQUENCE {

[2249] schedulingRequestResourceId SchedulingRequestResourceId,

[2250] schedulingRequestID SchedulingRequestId,

[2251] periodicityAndOffset CHOICE {

[2252] sym2 NULL,

[2253] sym6or7 NULL,

[2254] sl1 NULL, -- Recurs in every slot

[2255] sl2 INTEGER (0..1),

[2256] sl4 INTEGER (0..3),

[2257] sl5 INTEGER (0..4),

[2258] sl8 INTEGER (0..7),

[2259] sl10 INTEGER (0..9),

[2260] sl16 INTEGER (0..15),

[2261] sl20 INTEGER (0..19),

[2262] sl40 INTEGER (0..39),

[2263] sl80 INTEGER (0..79),

[2264] sl160 INTEGER (0..159),

[2265] sl320 INTEGER (0..319),

[2266] sl640 INTEGER (0..639)

[2267] } OPTIONAL, -- Need M

[2268] resource PUCCH-ResourceId OPTIONAL -- Need M

[2269] }

[2271] SchedulingRequestResourceConfigExt-v19xy ::= SEQUENCE {

[2272] symbolType-r19 ENUMERATED {sbfd, non-sbfd} OPTIONAL -- Need R

[2273] }

[2275] -- TAG-SCHEDULINGREQUESTRESOURCECONFIG-STOP

[2276] -- ASN1STOP

[2278] **periodicityAndOffset**: SR periodicity and offset are represented by 심보 or slot number.

[2280] **resource**: The ID of the PUCCH resource to which the UE will send scheduling requests. The actual PUCCH resource is configured in the PUCCH-Config of the same UL BWP and serving cell as this SchedulingRequestResourceConfig. The network configures PUCCH resources of PUCCH-format0 or PUCCH-format1, and other formats are not supported (for details, see TS 38.213

[13] , Clause 9.2.4).

[2282] **schedulingRequestID**: The ID of the SchedulingRequestConfig using this scheduling request resource.

[2284] **symbolType**: Configures the valid symbol type of the PUCCH configured for the SR for SBFD configuration 1. If SBFD configuration 2 is enabled for the UL BWP, the network does not configure this field (see TS 38.214

[19] , Clause X for details).

[2286] **SRS-Config**: Used to configure sounding reference signal transmission. This configuration defines the SRS-Resources list, SRS-PosResources list, SRS-PosResourceSets list, and SRS-ResourceSets list. Each resource set defines a set of SRS-Resources or SRS-PosResources. The network triggers the transmission of the SRS-Resources or SRS-PosResources set using the configured aperiodicSRS-ResourceTrigger (L1 DCI). If unifiedTCI-StateType is configured for the serving cell, the network does not configure the SRS-specific power control parameters alpha (no suffix) or pathlossReferenceRS.

[2287] -- ASN1START

[2288] -- TAG-SRS-CONFIG-START

[2289] SRS-Config ::= SEQUENCE {

[2290] srs-ResourceSetToReleaseList SEQUENCE (SIZE(1..maxNrofSRS-ResourceSets)) OF SRS-ResourceSetId OPTIONAL, -- Need N

[2291] srs-ResourceSetToAddModList SEQUENCE (SIZE(1..maxNrofSRS-ResourceSets)) OF SRS-ResourceSet OPTIONAL, -- Need N

[2292] srs-ResourceToReleaseList SEQUENCE (SIZE(1..maxNrofSRS-Resources)) OF SRS-ResourceId OPTIONAL, -- Need N

[2293] srs-ResourceToAddModList SEQUENCE (SIZE(1..maxNrofSRS-Resources)) OF SRS-Resource OPTIONAL, -- Need N

[2294] tpc-Accumulation ENUMERATED {disabled} OPTIONAL, -- Need S

[2295] ...,

[2296] [[

[2297] srs-RequestDCI-1-2-r16 INTEGER (1..2) OPTIONAL, -- Need S

[2298] srs-RequestDCI-0-2-r16 INTEGER (1..2) OPTIONAL, -- Need S

[2299] srs-ResourceSetToAddModListDCI-0-2-r16 SEQUENCE (SIZE(1..maxNrofSRS-ResourceSets)) OF SRS-ResourceSet OPTIONAL, -- Need N

[2300] srs-ResourceSetToReleaseListDCI-0-2-r16 SEQUENCE (SIZE(1..maxNrofSRS-ResourceSets)) OF SRS-ResourceSetId OPTIONAL, -- Need N

[2301] srs-PosResourceSetToReleaseList-r16 SEQUENCE (SIZE(1..maxNrofSRS-PosResourceSets-r16)) OF SRS-PosResourceSetId-r16

[2302] OPTIONAL, -- Need N

[2303] srs-PosResourceSetToAddModList-r16 SEQUENCE (SIZE(1..maxNrofSRS-PosResourceSets-r16)) OF SRS-PosResourceSet-r16 OPTIONAL,-- Need N

[2304] srs-PosResourceToReleaseList-r16 SEQUENCE (SIZE(1..maxNrofSRS-PosResources-r16)) OF SRS-PosResourceId-r16 OPTIONAL,-- Need N

[2305] srs-PosResourceToAddModList-r16 SEQUENCE (SIZE(1..maxNrofSRS-PosResources-r16)) OF SRS-PosResource-r16 OPTIONAL -- Need N

[2306] ]],

[2307] [[

[2308] dci-TriggeringPosResourceSetLink-r18 ENUMERATED { enabled} OPTIONAL -- Need R

[2309] ]]

[2310] }

[2312] SRS-ResourceSet ::= SEQUENCE {

[2313] srs-ResourceSetId SRS-ResourceSetId,

[2314] srs-ResourceIdList SEQUENCE (SIZE(1..maxNrofSRS-ResourcesPerSet)) OF SRS-ResourceId OPTIONAL, -- Cond Setup

[2315] resourceType CHOICE {

[2316] aperiodic SEQUENCE {

[2317] aperiodicSRS-ResourceTrigger INTEGER (1..maxNrofSRS-TriggerStates-1),

[2318] csi-RS NZP-CSI-RS-ResourceId OPTIONAL, -- Cond NonCodebook

[2319] slotOffset INTEGER (1..32) OPTIONAL, -- Need S

[2320] ...,

[2321] [[

[2322] aperiodicSRS-ResourceTriggerList SEQUENCE (SIZE(1..maxNrofSRS-TriggerStates-2))

[2323] OF INTEGER (1..maxNrofSRS-TriggerStates-1) OPTIONAL -- Need M

[2324] ]]

[2325] },

[2326] semi-persistent SEQUENCE {

[2327] associatedCSI-RS NZP-CSI-RS-ResourceId OPTIONAL, -- Cond NonCodebook

[2328] ...

[2329] },

[2330] periodic SEQUENCE {

[2331] associatedCSI-RS NZP-CSI-RS-ResourceId OPTIONAL, -- Cond NonCodebook

[2332] ...

[2333] }

[2334] },

[2335] usage ENUMERATED {beamManagement, codebook, nonCodebook, antennaSwitching},

[2336] alpha Alpha OPTIONAL, -- Need S

[2337] p0 INTEGER (-202..24) OPTIONAL, -- Cond Setup

[2338] pathlossReferenceRS PathlossReferenceRS-Config OPTIONAL, -- Need M

[2339] srs-PowerControlAdjustmentStates ENUMERATED { sameAsFci2, separateClosedLoop} OPTIONAL, -- Need S

[2340] ...,

[2341] [[

[2342] pathlossReferenceRSList-r16 SetupRelease { PathlossReferenceRSList-r16} OPTIONAL -- Need M

[2343] ]],

[2344] [[

[2345] usagePDC-r17 ENUMERATED {true} OPTIONAL, -- Need R

[2346] availableSlotOffsetList-r17 SEQUENCE (SIZE(1..4)) OF AvailableSlotOffset-r17 OPTIONAL, -- Need R

[2347] followUnifiedTCI-StateSRS-r17 ENUMERATED {enabled} OPTIONAL -- Need R

[2348] ]],

[2349] [[

[2350] applyIndicatedTCI-State-r18 ENUMERATED {first, second} OPTIONAL -- Cond FollowUTCI

[2351] ]],

[2352] [[

[2353] symbolType-r19 ENUMERATED {sbfd, non-sbfd} OPTIONAL -- Need R

[2354] ]]

[2355] }

[2357] AvailableSlotOffset-r17 ::= INTEGER (0..7)

[2359] PathlossReferenceRS-Config ::= CHOICE {

[2360] ssb-Index SSB-Index,

[2361] csi-RS-Index NZP-CSI-RS-ResourceId

[2362] }

[2364] PathlossReferenceRSList-r16 ::= SEQUENCE (SIZE (1..maxNrofSRS-PathlossReferenceRS-r16)) OF PathlossReferenceRS-r16

[2366] PathlossReferenceRS-r16 ::= SEQUENCE {

[2367] srs-PathlossReferenceRS-Id-r16 SRS-PathlossReferenceRS-Id-r16,

[2368] pathlossReferenceRS-r16 PathlossReferenceRS-Config

[2369] }

[2371] SRS-PathlossReferenceRS-Id-r16 ::= INTEGER (0..maxNrofSRS-PathlossReferenceRS-1-r16)

[2373] SRS-PosResourceSet-r16 ::= SEQUENCE {

[2374] srs-PosResourceSetId-r16 SRS-PosResourceSetId-r16,

[2375] srs-PosResourceIdList-r16 SEQUENCE (SIZE(1..maxNrofSRS-ResourcesPerSet)) OF SRS-PosResourceId-r16

[2376] OPTIONAL, -- Cond Setup

[2377] resourceType-r16 CHOICE {

[2378] aperiodic-r16 SEQUENCE {

[2379] aperiodicSRS-ResourceTriggerList-r16 SEQUENCE (SIZE(1..maxNrofSRS-TriggerStates-1))

[2380] OF INTEGER (1..maxNrofSRS-TriggerStates-1) OPTIONAL, -- Need M

[2381] ...

[2382] },

[2383] semi-persistent-r16 SEQUENCE {

[2384] ...

[2385] },

[2386] periodic-r16 SEQUENCE {

[2387] ...

[2388] }

[2389] },

[2390] alpha-r16 Alpha OPTIONAL, -- Need S

[2391] p0-r16 INTEGER (-202..24) OPTIONAL, -- Cond Setup

[2392] pathlossReferenceRS-Pos-r16 CHOICE {

[2393] ssb-IndexServing-r16 SSB-Index,

[2394] ssb-Ncell-r16 SSB-InfoNcell-r16,

[2395] dl-PRS-r16 DL-PRS-Info-r16

[2396] } OPTIONAL, -- Need M

[2397] ...

[2399] }

[2401] SRS-ResourceSetId ::= INTEGER (0..maxNrofSRS-ResourceSets-1)

[2403] SRS-PosResourceSetId-r16 ::= INTEGER (0..maxNrofSRS-PosResourceSets-1-r16)

[2405] SRS-Resource ::= SEQUENCE {

[2406] srs-ResourceId SRS-ResourceId,

[2407] nrofSRS-Ports ENUMERATED {port1, ports2, ports4},

[2408] ptrs-PortIndex ENUMERATED {n0, n1} OPTIONAL, -- Need R

[2409] transmissionComb CHOICE {

[2410] n2 SEQUENCE {

[2411] combOffset-n2 INTEGER (0..1),

[2412] cyclicShift-n2 INTEGER (0..7)

[2413] },

[2414] n4 SEQUENCE {

[2415] combOffset-n4 INTEGER (0..3),

[2416] cyclicShift-n4 INTEGER (0..11)

[2417] }

[2418] },

[2419] resourceMapping SEQUENCE {

[2420] startPosition INTEGER (0..5),

[2421] nrofSymbols ENUMERATED {n1, n2, n4},

[2422] repetitionFactor ENUMERATED {n1, n2, n4}

[2423] },

[2424] freqDomainPosition INTEGER (0..67),

[2425] freqDomainShift INTEGER (0..268),

[2426] freqHopping SEQUENCE {

[2427] c-SRS INTEGER (0..63),

[2428] b-SRS INTEGER (0..3),

[2429] b-hop INTEGER (0..3)

[2430] },

[2431] groupOrSequenceHopping ENUMERATED { neither, groupHopping, sequenceHopping},

[2432] resourceType CHOICE {

[2433] aperiodic SEQUENCE {

[2434] ...

[2435] },

[2436] semi-persistent SEQUENCE {

[2437] periodicityAndOffset-sp SRS-PeriodicityAndOffset,

[2438] ...

[2439] },

[2440] periodic SEQUENCE {

[2441] periodicityAndOffset-p SRS-PeriodicityAndOffset,

[2442] ...

[2443] }

[2444] },

[2445] sequenceId INTEGER (0..1023),

[2446] spatialRelationInfo SRS-SpatialRelationInfo OPTIONAL, -- Need R

[2447] ...,

[2448] [[

[2449] resourceMapping-r16 SEQUENCE {

[2450] startPosition-r16 INTEGER (0..13),

[2451] nrofSymbols-r16 ENUMERATED {n1, n2, n4},

[2452] repetitionFactor-r16 ENUMERATED {n1, n2, n4}

[2453] } OPTIONAL -- Need R

[2454] ]],

[2455] [[

[2456] spatialRelationInfo-PDC-r17 SetupRelease { SpatialRelationInfo-PDC-r17} OPTIONAL, -- Need M

[2457] resourceMapping-r17 SEQUENCE {

[2458] startPosition-r17 INTEGER (0..13),

[2459] nrofSymbols-r17 ENUMERATED {n1, n2, n4, n8, n10, n12, n14},

[2460] repetitionFactor-r17 ENUMERATED {n1, n2, n4, n5, n6, n7, n8, n10, n12, n14}

[2461] } OPTIONAL, -- Need R

[2462] partialFreqSounding-r17 SEQUENCE {

[2463] startRBIndexFScaling-r17 CHOICE{

[2464] startRBIndexAndFreqScalingFactor2-r17 INTEGER (0..1),

[2465] startRBIndexAndFreqScalingFactor4-r17 INTEGER (0..3)

[2466] },

[2467] enableStartRBHopping-r17 ENUMERATED {enable} OPTIONAL -- Need R

[2468] } OPTIONAL, -- Need R

[2469] transmissionComb-n8-r17 SEQUENCE {

[2470] combOffset-n8-r17 INTEGER (0..7),

[2471] cyclicShift-n8-r17 INTEGER (0..5)

[2472] } OPTIONAL, -- Need R

[2473] srs-TCI-State-r17 CHOICE {

[2474] srs-UL-TCI-State TCI-UL-StateId-r17,

[2475] srs-DLorJointTCI-State TCI-StateId

[2476] } OPTIONAL -- Need R

[2477] ]],

[2478] [[

[2479] repetitionFactor-v1730 ENUMERATED {n3} OPTIONAL, -- Need R

[2480] srs-DLorJointTCI-State-v1730 SEQUENCE {

[2481] cellAndBWP-r17 ServingCellAndBWP-Id-r17

[2482] } OPTIONAL -- Cond DLorJointTCI-SRS

[2483] ]],

[2484] [[

[2485] nrofSRS-Ports-n8-r18 ENUMERATED {ports8, ports8tdm} OPTIONAL, -- Need R

[2486] combOffsetHopping-r18 SEQUENCE {

[2487] hoppingId-r18 INTEGER (0..1023) OPTIONAL, -- Need R

[2488] hoppingSubset-r18 CHOICE {

[2489] transmissionComb-n4 BIT STRING (SIZE (4)),

[2490] transmissionComb-n8 BIT STRING (SIZE (8))

[2491] } OPTIONAL, -- Need R

[2492] hoppingWithRepetition-r18 ENUMERATED {symbol, repetition} OPTIONAL -- Need R

[2493] } OPTIONAL, -- Need R

[2494] cyclicShiftHopping-r18 SEQUENCE {

[2495] hoppingId-r18 INTEGER (0..1023) OPTIONAL, -- Need R

[2496] hoppingSubset-r18 CHOICE {

[2497] transmissionComb-n2 BIT STRING (SIZE (8)),

[2498] transmissionComb-n4 BIT STRING (SIZE (12)),

[2499] transmissionComb-n8 BIT STRING (SIZE (6))

[2500] } OPTIONAL, -- Need R

[2501] hoppingFinerGranularity-r18 ENUMERATED {enable} OPTIONAL -- Need R

[2502] } OPTIONAL -- Need R

[2503] ]]

[2504] }

[2506] SRS-SpatialRelationInfo ::= SEQUENCE {

[2507] servingCellId ServCellIndex OPTIONAL, -- Need S

[2508] referenceSignal CHOICE {

[2509] ssb-Index SSB-Index,

[2510] csi-RS-Index NZP-CSI-RS-ResourceId,

[2511] srs SEQUENCE {

[2512] resourceId SRS-ResourceId,

[2513] uplinkBWP BWP-Id

[2514] }

[2515] }

[2516] }

[2517] SSB-Configuration-r16 ::= SEQUENCE {

[2518] ssb-Freq-r16 ARFCN-ValueNR,

[2519] halfFrameIndex-r16 ENUMERATED {zero, one},

[2520] ssbSubcarrierSpacing-r16 SubcarrierSpacing,

[2521] ssb-Periodicity-r16 ENUMERATED { ms5, ms10, ms20, ms40, ms80, ms160, spare2,spare1} OPTIONAL, -- Need S

[2522] sfn0-Offset-r16 SEQUENCE {

[2523] sfn-Offset-r16 INTEGER (0..1023),

[2524] integerSubframeOffset-r16 INTEGER (0..9) OPTIONAL -- Need R

[2525] } OPTIONAL, -- Need R

[2526] sfn-SSB-Offset-r16 INTEGER (0..15),

[2527] ss-PBCH-BlockPower-r16 INTEGER (-60..50) OPTIONAL -- Cond Pathloss

[2528] }

[2530] SSB-InfoNcell-r16 ::= SEQUENCE {

[2531] physicalCellId-r16 PhysCellId,

[2532] ssb-IndexNcell-r16 SSB-Index OPTIONAL, -- Need S

[2533] ssb-Configuration-r16 SSB-Configuration-r16 OPTIONAL -- Need S

[2534] }

[2537] SRS-ResourceId ::= INTEGER (0..maxNrofSRS-Resources-1)

[2538] SRS-PosResourceId-r16 ::= INTEGER (0..maxNrofSRS-PosResources-1-r16)

[2540] SRS-PeriodicityAndOffset ::= CHOICE {

[2541] sl1 NULL,

[2542] sl2 INTEGER(0..1),

[2543] sl4 INTEGER(0..3),

[2544] sl5 INTEGER(0..4),

[2545] sl8 INTEGER(0..7),

[2546] sl10 INTEGER(0..9),

[2547] sl16 INTEGER(0..15),

[2548] sl20 INTEGER(0..19),

[2549] sl32 INTEGER(0..31),

[2550] sl40 INTEGER(0..39),

[2551] sl64 INTEGER(0..63),

[2552] sl80 INTEGER(0..79),

[2553] sl160 INTEGER(0..159),

[2554] sl320 INTEGER(0..319),

[2555] sl640 INTEGER(0..639),

[2556] sl1280 INTEGER(0..1279),

[2557] sl2560 INTEGER(0..2559)

[2558] }

[2559] }

[2561] -- TAG-SRS-CONFIG-STOP

[2562] -- ASN1STOP

[2563] **dci-TriggeringPosResourceSetLink**: Indicates whether a single DCI triggering SRS location resource set between linked carriers is enabled for a bandwidth set.

[2565] **tpc-Accumulation**: If this field is missing, the UE applies TPC commands through accumulation. If disabled, the UE applies TPC commands without accumulation (this applies if a separate closed loop is configured for the SRS) (see TS 38.213

[13] , Clause 7.3 for details).

[2567] **periodicityAndOffset-p, periodicityAndOffset-p-Ext**: Periodicity and slot offset of this SRS resource. All values ​​are expressed as "number of slots". Value sl1 corresponds to a period of 1 slot, and value sl2 corresponds to a period of 2 slots. For each period, the corresponding offset is provided as the number of slots. If the period is sl1, the offset is 0 slots (see TS 38.214

[19] , Clause 6.2.1 for details). For CLI SRS-RSRP measurements, sl1280 and sl2560 cannot be configured. For SRS-PosResource, sl20480, sl40960, and sl81920 cannot be configured at SCS=15kHz, sl40960 and sl81920 cannot be configured at SCS=30kHz, and sl81920 cannot be configured at SCS=60kHz except when a period of 20480ms is configured. If periodicityAndOffset-p-Ext exists, the UE must ignore periodicityAndOffset-p.

[2569] **resourceMapping**: OFDM symbol positions of SRS resources within a slot, including nrofSymbols (number of OFDM symbols), startPosition (value 0 indicates the last symbol, value 1 indicates the previous symbol), and repetitionFactor (for details, see TS 38.214

[19] , Clause 6.2.1 and TS 38.211

[16] , Clause 6.4.1.4). The configured SRS resources do not extend beyond the slot boundaries. If resourceMapping-r16 is transmitted as a signal, the UE must ignore resourceMapping(no suffix). If resourceMapping-r17 is transmitted as a signal, resourceMapping-r16 is not transmitted as a signal, the UE must ignore resourceMapping(no suffix), and the value of nrofSymbols can only be an integer multiple of the configured repetitionFactor. The network may signal repetitionFactor-v1730 only when resourceMapping-r17 is signaled. If repetitionFactor-v1730 is signaled, the UE must ignore repetitionFactor-r17. For CLI SRS-RSRP measurements, the network always configures nrofSymbols and repetitionFactor to 'n1'. If srs-PosRRC-InactiveValidityAreaPreConfigList or srs-PosRRC-InactiveValidityAreaNonPreConfig is configured, the value of this field applies to all cells within the valid area. If TxHoppingConfig is configured, nrofSymbols is the same for all hops.

[2571] **resourceType**: Periodicity and offset of semi-permanent and periodic SRS resources, or slot offset of non-periodic SRS resources for positioning (see TS 38.214

[19] , Clause 6.2.1 for details). For CLI SRS-RSRP measurements, only 'periodic' applies to resourceType. If srs-PosRRC-InactiveValidityAreaPreConfigList or srs-PosRRC-InactiveValidityAreaNonPreConfig is configured, the value of this field applies to all cells within the valid area.

[2573] **sequenceId**: The sequence ID used to initialize pseudo-random number groups and sequence hops (see TS 38.214

[19] , Clause 6.2.1 for details). If srs-PosRRC-InactiveValidityAreaPreConfigList or srs-PosRRC-InactiveValidityAreaNonPreConfig is configured, the value of this field applies to all cells within the valid area.

[2574] **slotOffset**: Offset for the number of slots between the trigger DCI and the actual transfer of this SRS-PosResource. If this field is missing, the UE does not apply an offset (value 0).

[2577] ***spatialRelationInfo**: Configures the spatial relationship between the reference RS and the target SRS. The reference RS can be an SSB / CSI-RS / SRS (see TS 38.214

[19] , Clause 6.2.1 for details). This parameter does not apply to CLI SRS-RSRP measurements. If unifiedTCI-StateType is configured for the serving cell, this field is not configured.

[2579] **Alpha**: Alpha value for SRS power control (see TS 38.213

[13] , Clause 7.3 for details). If this field is not present, the UE applies a value of 1. If srs-PosRRC-InactiveValidityAreaPreConfigList or srs-PosRRC-InactiveValidityAreaNonPreConfig is configured, the value of this field applies to all cells within the valid area.

[2581] **aperiodicSRS-ResourceTriggerList**: A list of additional DCI "code points" to which the UE must send SRS according to this SRS resource set configuration (see TS 38.214

[19] , Clause 6 for details). While this field is non-periodic (not included during the reconfiguration of an SRS-ResourceSet where resourceType is set to aperiodic), the UE retains this value based on Need M, meaning this list is not considered an extension of aperiodicSRS-ResourceTrigger for the purpose of applying the general rule of Clause 6.1.3.

[2583] **aperiodicSRS-ResourceTrigger**: DCI "code point" to which the UE must send an SRS according to this SRS resource set configuration (see TS 38.214

[19] , Clause 6 for details).

[2585] **applyIndicatedTCI-State**: This field indicates whether the UE applies the first or second “designated” UL-only TCI or joint TCI specified in TS 38.214

[19] , Clause 6.2.1 to the SRS-ResourceSet.

[2587] **associatedCSI-RS**: ID of the CSI-RS resource associated with this set of SRS resources in non-codebook-based operations (see TS 38.214

[19] , Clause 6.1.1.2 for details).

[2589] **availableSlotOffsetList**: Represents a list of up to four different available slot offset values ​​from slot n with the trigger DCI to the slot where the aperiodic SRS resource set is transferred, where slot n is the slot with the trigger DCI and k is slotOffset (no suffix) as described in TS 38.214

[19] , Clause 6.2.1.

[2591] **csi-RS**: ID of the CSI-RS resource associated with this SRS resource set (for details, see TS 38.214

[19] , Clause 6.1.1.2).

[2592] **slotOffset**: Offset for the number of slots between the trigger DCI and the actual transfer of this SRS-PosResource. If this field is missing, the UE does not apply an offset (value 0).

[2594] **spatialRelationInfo**: Configures the spatial relationship between the reference RS and the target SRS. The reference RS can be an SSB, CSI-RS, or SRS. This parameter does not apply to CLI SRS-RSRP measurements. If unifiedTCI-StateType is configured for the serving cell, this field is not configured.

[2596] **Alpha**: Alpha value for SRS power control. If this field is missing, the UE applies a value of 1. If srs-PosRRC-InactiveValidityAreaPreConfigList or srs-PosRRC-InactiveValidityAreaNonPreConfig is configured, the value of this field applies to all cells within the valid area.

[2598] **aperiodicSRS-ResourceTriggerList**: A list of additional DCI "code points" to which the UE must send SRS according to this SRS resource set configuration. While this field is non-periodic (not included during the reconfiguration of an SRS-ResourceSet where resourceType is set to aperiodic), the UE retains this value based on Need M, meaning this list is not considered an extension of aperiodicSRS-ResourceTrigger for the purpose of applying the general rule of Clause 6.1.3.

[2600] **aperiodicSRS-ResourceTrigger**: DCI "code point" to which the UE must send SRS according to this SRS resource set configuration.

[2602] *

[2603] **applyIndicatedTCI-State**: This field indicates whether the UE applies a specified UL-only TCI or a co-TCI for the SRS-ResourceSet.

[2605] **associatedCSI-RS**: The ID of the CSI-RS resource associated with this set of SRS resources in non-codebook-based operations.

[2607] **availableSlotOffsetList**: Represents a list of up to four different available slot offset values ​​from slot n, where the trigger DCI is located, to the slot where the aperiodic SRS resource set is transferred. Here, slot n is the slot with the trigger DCI, and k is the slotOffset (no suffix).

[2609] **csi-RS**: ID of the CSI-RS resource associated with this SRS resource set.

[2610] **srs-PowerControlAdjustmentStates**: hsrs,c(i) = fc(i,1) or hsrs,c(i) = fc(i,2) (if two PUSCH-PC-AdjustmentStates are configured) or indicates whether a separate closed loop is configured for the SRS. This parameter applies only to the UL to which the UE transmits PUSCH. If this field is missing or disabled, the UE applies the sameAs-Fci1 value (see TS 38.213

[13] , Clause 7.3 for details).

[2612] **srs-ResourceIdList, srs-PosResourceIdList**: IDs of SRS-Resources / SRS-PosResources used in this SRS-ResourceSet / SRS-PosResourceSet. If this SRS-ResourceSet is configured for codebook use, srs-ResourceIdList contains up to 2 items. If configured for non-codebook use, srs-ResourceIdList contains up to 4 items. If srs-PosRRC-InactiveValidityAreaPreConfigList or srs-PosRRC-InactiveValidityAreaNonPreConfig is configured, srs-PosResourceIdList is typically configured between cells within the validity area.

[2614] **srs-ResourceSetId, srs-PosResourceSetId**: The ID of this resource set. It is unique within the context of the BWP where the parent SRS-Config is defined. If srs-PosRRC-InactiveValidityAreaPreConfigList or srs-PosRRC-InactiveValidityAreaNonPreConfig is configured, srs-PosResourceSetId is typically configured among cells within the validity area.

[2616] **ssb-IndexServing**: Represents the SSB index belonging to the serving cell configured with SRS.

[2618] **ssb-Ncell**: This field indicates the SSB configuration of the neighboring cell.

[2620] **symbolType**: Configures the valid symbol type for the SRS resources in the SRS resource set. Do not configure this field if the network is configured as 'antennaSwitching' (see TS 38.214, Clause X for details).

[2622] **usage**: Indicates whether the SRS resource set is used for beam management, codebook-based or non-codebook-based transmission, or antenna switching. Reconfiguration between codebook-based and non-codebook-based transmission is not supported (see TS 38.214

[19] , Clause 6.2.1 for details).

[2624] **physicalCellId**: This field specifies the physical cell ID for the NCD-SSB of a neighboring cell or serving cell.

[2626] **ssb-IndexNcell**: This field specifies the SSB index for the neighboring cell's SSB or the NCD-SSB of the serving cell. (See TS 38.213

[13] for details). If this field is missing, the UE determines the ssb-IndexNcell of physicalCellId based on the SSB measurement in the cell.

[2628] **ssb-Configuration**: This field specifies the overall configuration of the SSB. If this field is missing, the UE obtains the SSB configuration from nr-SSB-Config received as part of the LPP's DL-PRS support data, and uses the physicalCellId field to look up the corresponding SSB configuration (see TS 37.355

[49] for details).

[2630] **halfFrameIndex**: Indicates whether the SSB is in the first half or the second half of the frame. A value of 0 indicates the first half, and a value of 1 indicates the second half.

[2631] **integerSubframeOffset**: Represents the subframe boundary offset of the cell where the SSB is transmitted.

[2633] **sfn0-Offset**: Represents the time offset of the cell relative to SFN0 slot 0 of the serving cell.

[2635] **sfn-Offset**: Specifies the SFN offset between the cell transmitting the SSB and the serving cell. This offset corresponds to the total number of radio frames from the start of radio frame #0 of the serving cell to the start of the nearest next radio frame #0 of the cell transmitting the SSB.

[2637] **sfn-SSB-Offset**: Indicates the SFN offset of the transmitted SSB relative to the start of the SSB period. A value of 0 indicates that the SSB is transmitted in the first system frame, and a value of 1 indicates that the SSB is transmitted in the second system frame. The network configures this field according to the ssb-Periodicity field to ensure that the indicated system frame does not exceed the configured SSB period.

[2639] **ssb-Freq**: Represents the frequency of the SSB.

[2641] **ss-PBCH-BlockPower**: Indicates the average EPRE of the resource element containing the auxiliary synchronization signal used for SSB transmission in dBm (for details, see TS 38.213

[13] , Clause 7).

[2643] **ssb-Periodicity**: Indicates the period of the SSB. If this field is missing, the UE applies the value ms5 (for details, see TS 38.213

[13] , Clause 4.1).

[2645] **ssbSubcarrierSpacing**: SSB의 서브캐리어 간격.

[2646] ? Uplink-PowerControl

[2647] The IE Uplink-PowerControl is used to configure UE specific power control parameter for PUSCH, PUCCH and SRS.

[2648] Uplink-PowerControl information element

[2649] -- ASN1START

[2650] -- TAG-UPLINK-POWERCONTROL-START

[2652] Uplink-powerControl-r17 ::= SEQUENCE {

[2653] ul-powercontrolId-r17 Uplink-powerControlId-r17,

[2654] p0AlphaSetforPUSCH-r17 P0AlphaSet-r17 OPTIONAL, -- Need R

[2655] p0AlphaSetforPUCCH-r17 P0AlphaSet-r17 OPTIONAL, -- Need R

[2656] p0AlphaSetforSRS-r17 P0AlphaSet-r17 OPTIONAL -- Need R

[2657] }

[2659] P0AlphaSet-r17 ::= SEQUENCE {

[2660] p0-r17 INTEGER (-16..15) OPTIONAL, -- Need R

[2661] alpha-r17 Alpha OPTIONAL, -- Need S

[2662] closedLoopIndex-r17 ENUMERATED { i0, i1}

[2663] }

[2665] Uplink-powerControlId-r17 ::= INTEGER(1.. maxUL-TCI-r17)

[2667] Uplink-powerControl-v19xy ::= SEQUENCE {

[2668] p0AlphaSetforPUSCH-SBFD-r19 P0AlphaSet-r17 OPTIONAL, -- Need R

[2669] p0AlphaSetforPUCCH-SBFD-r19 P0AlphaSet-r17 OPTIONAL, -- Need R

[2670] p0AlphaSetforSRS-SBFD-r19 P0AlphaSet-r17 OPTIONAL -- Need R

[2671] }

[2673] -- TAG-UPLINK-POWERCONTROL-STOP

[2674] -- ASN1STOP

[2675] **p0AlphaSetforPUSCH, p0AlphaSetforPUCCH, p0AlphaSetforSRS**: Configures the power control parameters for PUSCH, PUCCH, and SRS (see TS 38.213

[13] , Clause 7.2 for details). If the alpha field is missing in p0AlphaSetforPUSCH, the UE applies a value of 1 for PUSCH power control. If the alpha field is missing in p0AlphaSetforSRS, the UE applies a value of 1 for SRS power control. In p0AlphaSetForPUCCH, the alpha field is missing (not used).

[2677] **p0AlphaSetforPUSCH-SBFD, p0AlphaSetforPUCCH-SBFD, p0AlphaSetforSRS-SBFD**: Configures separate UL power control parameters for PUSCH, PUCCH, and SRS transmissions in the SBFD symbol (see TS 38.213

[13] , clause x for details).

[2679] If the UE is provided with tdd-UL-DL-ConfigurationCommon for a cell, the PRACH opportunity for the cell in the PRACH slot is valid when the following conditions are satisfied:

[2681] >: Exists only within the UL symbol, or

[2682] >: Exists only within an SBFD symbol, where at least one SBFD symbol is indicated as a downlink by tdd-UL-DL-ConfigurationCommon, and exists in the RB of the active UL BWP and UL subband if the UE is provided with sbfd-RACHSingleConfig or sbfd-RACHDualConfig, or starts in an SBFD symbol and ends in a non-SBFD symbol, and exists in the RB of the active UL BWP and UL subband if the UE is provided with sbfd-RACHDualConfig and sbfd-RACHDualConfig-ValidROAcrossSymbolTypes, or

[2683] >: It must not precede the SS / PBCH block within the PRACH slot and must start at least N_gap symbols after the last downlink symbol and at least Ngap symbols after the last SS / PBCH block symbol. Here, Ngap is provided in Table 8.1-2. If the channel access mode is provided as "semiStatic", it must not overlap with a consecutive set of symbols for which no transmissions must occur before the start of the next channel occupancy time (see [15, TS 37.213] for details).

[2684] >>: The candidate SS / PBCH block index must match the SS / PBCH block index provided by ssb-PositionsInBurst in SSB-MTC-AdditionalPCI for SIB1, ServingCellConfigCommon, or the corresponding cell (see Clause 4.1 for details).

[2685] The downlink or flexible symbol provided by tdd-UL-DL-ConfigurationCommon may include the UL subband provided by ulSubbandlocationAndBandwidth, the first DL subband provided by firstdlSubbandlocationAndBandwidth, and additionally the second DL subband provided by seconddlSubbandlocationAndBandwidth. These correspond to the SCS configuration μ for the configured UL BWP or DL ​​BWP provided by scs-SpecificCarrierList, respectively. In this case, the downlink or flexible symbol is referred to as an SBFD symbol, and otherwise as a non-SBFD symbol. The uplink symbol is a non-SBFD symbol. The SBFD symbol or non-SBFD symbol provided by tdd-UL-DL-ConfigurationCommon cannot be changed to a non-SBFD symbol or an SBFD symbol by other information. The UE is not provided with a coresetPoolIndex and is not configured to receive PDSCH according to two or more TCI states mapped to a single TCI code point for a serving cell where SBFD symbols are provided [6, TS 38.214].

[2687] SBFD symbols are provided sequentially, starting at the first slot provided by SBFD-StartingSlotIndex and the first symbol provided by SBFD-StartingSymbolIndex, and ending at the second slot provided by SBFD-EndingSlotIndex and the second symbol provided by SBFD-EndingSymbolIndex. SBFD symbols can be provided as either pattern1 or pattern2 (if provided). The duration of the SBFD symbol construction is P milliseconds if only pattern1 is provided, and P + P2 if pattern2 is additionally provided.

[2689] Except for PRACH transmissions in PRACH opportunities determined by the second RACH configuration provided by sbfd-RACHDualConfig, the UE transmits or receives physical channels or signals only within SBFD symbols or only within non-SBFD symbols.

[2690] If the UE is provided with sbfd-Configuration2-Transmission, the UE

[2691] In a non-SBFD symbol, you can transmit the first PUCCH or PUSCH, transmit the first repetition of PUCCH or PUSCH, receive the first PDSCH, or receive the first repetition of PDSCH, and

[2692] In the SBFD symbol, a second PUCCH or PUSCH may be transmitted, or a second repetition of PUCCH or PUSCH may be transmitted, or a second PDSCH may be received, or a second repetition of PDSCH may be received.

[2694] If the UE is not provided with sbfd-Configuration2-Transmission

[2695] In a PUCCH or PUSCH transmission, if there are repetitions, if the first repetition is in an SBFD symbol or a non-SBFD symbol, the remaining repetitions must also be in an SBFD symbol or a non-SBFD symbol, respectively.

[2696] For Type 2 CG PUSCH transmissions, PUSCH transmissions with SP-CSI reporting, or SPS PDSCH receptions, if the first transmission or reception after the latest activation is in an SBFD symbol or a non-SBFD symbol, the remaining transmissions or receptions associated with the latest activation must also be in an SBFD symbol or a non-SBFD symbol, respectively.

[2697] For Type 1 CG PUSCH, PUCCH transmission with SP-CSI reporting, SR, [LRR, UEIRI], P-CSI, or PUCCH with SRS, all such transmissions must be made only within SBFD symbols or only within non-SBFD symbols, depending on the respective configuration [12, TS 38.331].

[2699] Within SBFD symbols, and excluding cross-link interference measurements [6, TS 38.214], the UE transmits or receives only from RBs in both the active UL BWP and UL subband, or transmits or receives from both the active DL BWP and DL subband(s). The UE does not transmit in SBFD symbols specified to indicate the presence of an SS / PBCH block within an active DL BWP by ssb-PositionsInBurst in SIB1 or ServingCellConfigCommon [or by a non-cell defined SS / PBCH].

[2701] DCI format 1_0 is used for scheduling PDSCH in a single DL cell.

[2702] The following information is transmitted via DCI format 1_0 with the CRC scrambled by C-RNTI, CS-RNTI, or MCS-C-RNTI:

[2703] >: DCI format identifier - 1 bit

[2704] >>: The value of this bit field is always set to 1 and represents the DL DCI format.

[2705] >: Frequency domain resource allocation - n bits

[2706] If the CRC of DCI format 1_0 is scrambled by C-RNTI and the "Frequency Domain Resource Allocation" field is all 1, DCI format 1_0 is for a random access procedure initiated by the PDCCH command, and the remaining fields are set as follows:

[2707] >: Random access preamble index - 6 bits.

[2708] >: UL / SUL indicator - 1 bit.

[2709] >>: If the cell indicator field is missing or the cell indicator field represents a serving cell, and the values ​​of the "Random Access Preamble Index" are not all zero and the UE is configured as supplementaryUplink in the cell's ServingCellConfig, this field indicates the UL carrier within the cell to transmit PRACH;

[2710] >>: If the cell indicator field indicates a candidate cell, and the values ​​of the "Random Access Preamble Index" are all non-zero and the UE is configured with LTM-Candidate's ltm-EarlyUL-SyncConfigSUL for the candidate cell, this field indicates the UL carrier within the candidate cell to transmit PRACH;

[2711] Otherwise, this field is reserved.

[2712] >: SS / PBCH index - 6 bits. If the values ​​of the "Random Access Preamble Index" are not all zero, this field indicates the SS / PBCH to be used to determine the RACH opportunity for PRACH transmission; otherwise, this field is reserved.

[2713] >: PRACH mask index - 4 bits. If the values ​​of the "random access preamble index" are not all zero, this field indicates the RACH opportunity associated with the SS / PBCH indicated by the "SS / PBCH index" for PRACH transmission (see provision 5.1.1 of [8, TS38.321] for details); otherwise, this field is reserved.

[2714] >: Cell Indicator - m bits representing the cell for the corresponding PRACH transmission if the UE is configured with the upper layer parameter EarlyUL-SyncConfig; C is the number of candidate cells configured with the upper layer parameter EarlyUL-SyncConfig; otherwise, 0 bits. Bit field index 0 of the cell indicator field is mapped to the serving cell, other bit field indices are mapped to candidate cells configured with the upper layer parameter EarlyUL-SyncConfig according to the ascending order of candidate IDs configured by ltm-CandidateId, and bit field index 1 is mapped to the candidate cell with the smallest candidate ID.

[2715] >: PRACH associated indicator - 0 or 1 bit

[2716] >>: 1 bit if the UE is provided with tag2-Id and the UE is not provided with coresetPoolIndex, or if coresetPoolIndex is provided with a value of 0 for the first CORESET and coresetPoolIndex is provided with a value of 1 for the second CORESET. This field is reserved if the cell indicated by the cell indicator field is a candidate cell.

[2717] >>>: This field indicates the PCI associated with the PRACH transfer when the UE is provided with SSB-MTC-AdditionalPCI. Bit field index 0 of this field maps to the PCI of the serving cell, and bit field index 1 of this field maps to the additional PCI associated with the active TCI status.

[2718] >>>: If the UE is not provided with SSB-MTC-AdditionalPCI, this field indicates the PL-RS for the PRACH transmission. Bit field index 0 of this field maps to the DL RS which is quasi-equivalent to the DM-RS of the PDCCH command, and bit field index 1 of this field maps to the SS / PBCH indicated by the SS / PBCH index field of this DCI format.

[2719] >>: Otherwise, 0 bits.

[2721] >: PRACH retransmission indicator - 0 or 1 bit

[2722] >>: 1 bit if the UE is configured with the upper layer parameter EarlyUL-SyncConfig. This field indicates the initial transmission or retransmission of PRACH if the cell indicated by the cell indicator field is a candidate cell, and this field is reserved if the value of the cell indicator field is 0.

[2723] >>: Otherwise, 0 bits.

[2725] >: RACH chance indicator - 0 or 1 bit

[2726] >>: 1 bit if UE is configured with the upper layer parameter sbfd-RACHSingleConfig or sbfd-RACHDualConfig. If the values ​​of the "Random Access Preamble Index" are all non-zero, this field indicates a RACH opportunity for PRACH transmission; otherwise, this field is reserved.

[2727] >>: Otherwise, 0 bits.

[2728] >>: 0: The RACH opportunity for PRACH transmission occurs at the first PRACH opportunity.

[2729] >>: 1: The RACH opportunity for PRACH transmission occurs at the second PRACH opportunity.

[2731] If the UE is configured with SBFD symbols, the UE does not receive PDSCH mapped to both SBFD and non-SBFD symbols within the slot. If the UE is scheduled to receive PDSCH across SBFD and non-SBFD symbols in different slots,

[2732] If the UE is not configured with sbfd-Config2-Reception, the UE receives only PDSCH of valid symbol types, where

[2733] >>: For PDSCH receptions scheduled across different slots enabled with DCI format 1_0, 1_1, or 1_2 without the corresponding PDCCH transmission using sps-Config, the valid symbol type is the symbol type of the first PDSCH reception opportunity associated with the enabled DCI.

[2734] >>: For PDSCH receptions spanning different slots scheduled using pdsch-TimeDomainAllocationListForMultiPDSCH of a DCI using pdsch-AggregationFactor or repetitionNumber, where one or more rows contain multiple SLIVs, the valid symbol type is the symbol type of the first PDSCH reception opportunity indicated by the scheduling DCI. The UE does not expect the first PDSCH reception opportunity indicated by the scheduling DCI to map to both SBFD symbols and non-SBFD symbols.

[2735] Otherwise, the UE receives PDSCH of SBFD symbols and non-SBFD symbols, in which case it applies collision handling in accordance with provision 11.1 of [6, TS 38.213] (if applicable).

[2737] When the UE is configured with sbfd-Config2-Reception, it performs PDSCH reception using only the assigned PRBs in both the active DL BWP and DL subband(s), which is scheduled on SBFD symbols enabled in DCI format 1_0, 1_1, or 1_2 without the corresponding PDCCH transmission using sps-Config, or PDSCH reception across different slots on SBFD symbols scheduled in DCI using pdsch-TimeDomainAllocationListForMultiPDSCH.

[2739] If the UE is configured with SBFD symbols, only the assigned PRBs in both the active DL BWP and DL subband(s) are used for a single PDSCH reception in an SBFD symbol within a slot, or for PDSCH reception across different slots where the valid symbol type is an SBFD symbol (Clause 5.1.2.1a). The UE does not expect to receive an RBG assignment for a PDSCH that is not fully contained in both the active DL BWP and DL subband(s).

[2741] In the case of PDSCH reception at SBFD symbols, DM-RS sequence mapping applies only to the assigned PRB in both the active DL BWP and DL subband(s). The UE does not expect srs-ResourceSetId and srs-ResourceIndicator2 to be configured in rrc-ConfiguredUplinkGrant. If txConfig is set to 'codebook', the UE does not expect precodingAndNumberOfLayers2 to be configured in rrc-ConfiguredUplinkGrant. If txConfig is set to 'nonCodebook', each SRS resource set is associated with the corresponding CSI-RS.

[2743] In the case of a Type 1 PUSCH transmission with a configured contract,

[2744] If the UE is not configured with sbfd-Config2-Transmission, srs-ResourceIndicator is associated with the most recent transmission of an SRS resource identified by SRI in SRS-ResourceSet, where symbolType corresponds to the same symbol type as the valid symbol type of the PUSCH transmission. If txConfig is set to 'codebook', precodingAndNumberOfLayers corresponds to an SRS resource identified by SRI in SRS-ResourceSet that corresponds to the same symbol type as the valid symbol type of the PUSCH transmission.

[2745] If the UE is configured with sbfd-Config2-Transmission, srs-ResourceIndicator applies to both the SRS resource set with symbolType set to 'non-sbfd' and the SRS resource set with symbolType set to 'sbfd'. For PUSCH transmissions in SBFD symbols, srs-ResourceIndicator is associated with the most recent transmission of the SRS resource identified by SRI in the SBFD symbol. For PUSCH transmissions in non-SBFD symbols, srs-ResourceIndicator is associated with the most recent transmission of the SRS resource identified by SRI in the non-SBFD symbol. If txConfig is set to 'codebook', for PUSCH transmissions in SBFD symbols, precodingAndNumberOfLayers corresponds to the SRS resource identified by SRI in the SRS-ResourceSet with symbolType set to 'sbfd'. For PUSCH transmissions with non-SBFD symbols, precodingAndNumberOfLayers corresponds to SRS resources identified by SRI in the SRS-ResourceSet where symbolType is set to 'non-sbfd'.

[2747] In the case of a Type 2 PUSCH transmission with a configured contract, or for a PUSCH transmission opportunity spanning SBFD symbols and non-SBFD symbols scheduled by DCI format 0_1, 0_2, or 0_3,

[2748] If the UE is not configured with sbfd-Config2-Transmission, the indicated SRI in slot n is associated with the most recent transmission of the SRS resource identified by the SRI in the SRS-ResourceSet, where symbolType corresponds to the same symbol type as the valid symbol type of the PUSCH transmission, and the SRS resource must be located before the PDCCH containing the SRI. If txConfig is set to 'codebook', the precoding information and layer number (TPMI) fields of the DCI correspond to the SRS resource identified by the SRI in the SRS-ResourceSet that corresponds to the same symbol type as the valid symbol type of the PUSCH transmission.

[2749] If the UE is configured with sbfd-Config2-Transmission, the SRS resource indicator applies to both the set of SRS resources with symbolType set to 'non-sbfd' and the set of SRS resources with symbolType set to 'sbfd'. For PUSCH transmissions in SBFD symbols, the SRI indicated in the slot is associated with the most recent transmission of the SRS resource identified by the SRI in the SBFD symbol, provided that the SRS resource is located prior to the PDCCH containing the SRI. For PUSCH transmissions in non-SBFD symbols, the SRI indicated in the slot is associated with the most recent transmission of the SRS resource identified by the SRI in the non-SBFD symbol, provided that the SRS resource is located prior to the PDCCH containing the SRI. When txConfig is set to 'codebook', for PUSCH transmission in SBFD symbols, the precoding information and layer number (TPMI) fields of the DCI correspond to the SRS resources identified by SRI in the SRS-ResourceSet, where symbolType must be the same as the symbol type of the PUSCH transmission. For PUSCH transmission in non-SBFD symbols, the precoding information and layer number (TPMI) fields of the DCI correspond to the SRS resources identified by SRI in the SRS-ResourceSet, where symbolType must be the same as the symbol type of the PUSCH transmission.

[2751] If only a single SRS resource is configured in both the SRS resource set with symbolType set to 'non-sbfd' and the SRS resource set with symbolType set to 'sbfd', the SRI field does not exist in the DCI.

[2753] For a PUSCH transmission scheduled by DCI format 0_1, 0_2, or 0_3 without repetition, the SRI indicated in the slot is associated with the most recent transmission of the SRS resource identified by the SRI in the SRS-ResourceSet, wherein the symbolType must be the same as the valid symbol type of the PUSCH transmission. The SRS resource must be located prior to the PDCCH containing the SRI. If txConfig is set to 'codebook', the precoding information and layer number (TPMI) fields of the DCI correspond to the SRS resource identified by the SRI in the SRS-ResourceSet corresponding to the symbol type identical to the valid symbol type of the PUSCH transmission.

[2754] For a UE scheduled for PUSCH transmission opportunities in different slots across SBFD symbols and non-SBFD symbols,

[2755] If the UE is not configured with sbfd-Config2-Transmission,

[2756] >>: The UE transmits only PUSCH of valid symbol types.

[2757] >>>: For Type 1 PUSCH transmissions with a configured contract, the valid symbol type is provided by symbolType in rrc-ConfiguredUplinkGrant of ConfiguredGrantConfig.

[2758] >>>: For a Type 2 PUSCH transmission with a configured contract or a PUSCH transmission scheduled by a DCI scrambled with SP-CSI-RNTI, the valid symbol type is the symbol type of the first PUSCH transmission opportunity associated with the activating DCI. For a Type 2 PUSCH transmission with a configured contract of PUSCH repeat type B, the valid symbol type is the symbol type of the first actual repeat associated with the activating DCI.

[2759] For PUSCH transmissions using a CRC scrambled with TC-RNTI in DCI formats 0_1, 0_2, 0_3, 0_0, the valid symbol type is the symbol type of the first PUSCH transmission opportunity indicated by the scheduling DCI, RAR UL grant, or fallbackRAR UL grant. If PUSCH repeat type B is scheduled in DCI format 0_1 ​​or 0_2, the valid symbol type is the symbol type of the first actual repeat opportunity indicated by the scheduling DCI. The UE does not expect the first PUSCH transmission opportunity indicated by the scheduling DCI, RAR UL grant, or fallbackRAR UL grant to map to both SBFD symbols and non-SBFD symbols, except for PUSCH repeat type B.

[2760] >>: If PUSCH iteration type A is scheduled as DCI format 0_1, 0_2, or 0_3 when AvailableSlotCounting is enabled and K>1, or as DCI format 0_0 using a CRC scrambled with TC-RNTI,

[2761] Slots containing transmission opportunities that do not correspond to valid symbol types are not included in the N?K slot count.

[2762] >>>: If the valid symbol type is an SBFD symbol, and all symbols for transfer opportunities within the slot are allocated as SBFD symbols and do not contain symbols from the SS / PBCH block, the slot is included in the N?K slot count (index provided by ssb-PositionsInBurst).

[2763] >>>: If the valid symbol type is a non-SBFD symbol, and PUSCH repeat type A is scheduled in DCI format 0_0 using a CRC scrambled with TC-RNTI, and all symbols for in-slot transfer opportunities are assigned as non-SBFD symbols and do not contain DL symbols indicated by tdd-UL-DL-ConfigurationCommon, the slot is included in the N?K slot count (if provided) or does not contain symbols of the SS / PBCH block index provided by ssb-PositionsInBurst. Otherwise, the slot is included in the N?K slot count (if provided) or symbols of the SS / PBCH block index provided by ssb-PositionsInBurst if all symbols for in-slot transfer opportunities are assigned as non-SBFD symbols and do not contain DL symbols indicated by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated.

[2764] Otherwise, the UE transmits the PUSCH transmission opportunity after applying collision handling to SBFD symbols and non-SBFD symbols (if applicable, see provision 11.1 of [6, TS 38.213]). If PUSCH iteration type A has AvailableSlotCounting enabled and K > 1, or if TB processing is performed across multiple slots, and all symbols for the transmission opportunity within the slot are assigned as SBFD symbols and the symbols in the SS / PBCH block are not included in the index provided by ssb-PositionsInBurst, or all symbols for the transmission opportunity within the slot are assigned as non-SBFD symbols and the DL symbols indicated by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated are not included (if provided), or the symbols in the SS / PBCH block are not included in the index provided by ssb-PositionsInBurst, the slot is included in the N?K slot count.

[2766] If a UE configured with SBFD symbols is scheduled for a PUSCH transmission opportunity mapped to SBFD symbols and non-SBFD symbols,

[2767] When a PUSCH transfer opportunity is scheduled as PUSCH repeat type A and AvailableSlotCounting is enabled and K > 1, or when TB processing is performed across multiple slots, the slot is not included in the number of N?K slots.

[2768] If the PUSCH transmission opportunity is a nominal repetition of PUSCH repetition type B, the nominal repetition is divided into actual repetitions along the boundary between SBFD symbols and non-SBFD symbols.

[2769] Otherwise, the UE does not send a PUSCH transmission opportunity.

[2771] If the UE is configured with SBFD symbols,

[2772] For PUSCH transmissions in SBFD symbols, only resource blocks located in both the active UL BWP and UL subband are used. For a single PUSCH transmission in an SBFD symbol within a slot, or for a PUSCH transmission across different slots where the valid symbol type is an SBFD symbol (see Clause 5.1.2.1), the UE does not expect to receive an RBG allocation for PUSCH in an SBFD symbol that is not included in both the active UL BWP and UL subband.

[2773] >: [If the UE is configured with sbfd-Config2-Transmission, and the UE is scheduled for PUSCH transmission opportunities in different slots across SBFD symbols and non-SBFD symbols, or if the UE is scheduled for PUSCH transmission opportunities within a slot across SBFD symbols and non-SBFD symbols for PUSCH repeat type B, the resource allocation of type 0 for PUSCH transmission opportunities in non-SBFD symbols is provided by the bitmap, and for each RBG allocated to a PUSCH transmission opportunity in SBFD symbols,

[2774] >>: The RGB size is the same as the RGB size for the PUSCH transmission opportunity in non-SBFD symbols.

[2775] >>: The starting resource block of an RBG is defined by the following:

[2776] >>>: Starting PRB index of the PRB present in both the active UL BWP and the UL subband, based on the start of the active UL BWP,

[2777] >>>: RBG's starting PRB index.

[2778] >>>: Number of PRBs present in both the active UL BWP and UL subband,

[2779] The UE does not expect the PRB for PUSCH transmission in the SBFD symbol to overlap with a PRB outside of the PRB that is in both the active UL BWP and the UL subband.

[2781] If the symbolType is set to 'sbfd' for an SRS resource in the SRS resource set provided by srs-ResourceSetToAddModList and srs-ResourceSetToAddModListDCI-0-2,

[2782] For periodic or semi-permanent SRS resources, the UE is expected to transmit the SRS only in SBFD symbols.

[2783] For non-periodic SRS resources, if availableSlotOffsetList is not provided, the UE does not expect to be instructed to transmit SRS on non-SBFD symbols.

[2784] For non-periodic SRS resources, if availableSlotOffsetList is provided, the available slots are slots composed of SBFD symbols for time domain positions for all SRS resources in the resource set, and must satisfy the minimum timing requirements between the trigger PDCCH and all SRS resources in the resource set.

[2786] If the symbolType is set to 'non-sbfd' for an SRS resource in the SRS resource set provided by srs-ResourceSetToAddModList and srs-ResourceSetToAddModListDCI-0-2,

[2787] For periodic or semi-permanent SRS resources, the UE is expected to transmit SRS only in non-SBFD symbols.

[2788] For non-periodic SRS resources, if availableSlotOffsetList is not provided, the UE does not expect to be instructed to transmit SRS in SBFD symbols.

[2789] For non-periodic SRS resources, if availableSlotOffsetList is provided, the available slots must be slots with UL or flexible symbols that are not configured with SBFD symbols for time domain positions for all SRS resources in the resource set, and must satisfy the minimum timing requirements between the trigger PDCCH and all SRS resources in the resource set.

[2791] For SRS resource sets provided in srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2-SBFD for the same purposes as 'scodebook', 'noncodebook', or 'beamManagement', the number of SRS resources in an SRS resource set with symbolType set to 'sbfd' is the same as the number of SRS resources in an SRS resource set with symbolType set to 'non-sbfd'.

[2793] If symbolType is configured for the SRS resource set configured in srs-ResourceSetToAddModList and srs-ResourceSetToAddModListDCI-0-2,

[2794] If the parent tier parameter usage in SRS-ResourceSet is set to 'noncodebook', the UE expects a single SRS port for each configured SRS resource.

[2795] When the parent tier parameter usage in SRS-ResourceSet is set to 'codebook', the number of SRS ports is the same for all SRS resources with symbolType set to 'non-sbfd' in SRS-ResourceSet(s), except when the parent tier parameter ul-FullPowerTransmission is set to 'fullpowerMode2'. When the parent tier parameter ul-FullPowerTransmission is set to 'fullpowerMode2', the number of SRS ports is the same for SRS resources with the same SRI value when symbolType is set to 'non-sbfd' and when symbolType is set to 'sbfd' in SRS-ResourceSet(s).

[2796] To further extend the slot format adjustment function, a specific DCI (e.g., DCI format 2_0) can be configured. DCI format 2_0 has the following characteristics.

[2797] DCI format 2_0 is a group common physical downlink control channel (PDCCH) that can be detected by the group's UE (user equipment).

[2798] DCI format 2_0 includes one or more SFIs (E3100 to E3400).

[2799] Each SFI indicates the slot type of the upcoming slot of a specific cell.

[2800] If the UE is configured with a slot format indicator (SFI) (A2000) via an upper layer signal, it can detect DCI format 2_0. The UE determines the slot format of a specific serving cell based on the specific slot format indicator.

[2801] The slot format indicator (SFI-index) (E3300) represents the slot format combination ID (A2100) associated with the combination / integer series, where the lowest value is 0 and the highest value is 255 (A2200). Each integer is a format index. Each format index is shown in Figure AB, where 'D' represents the downlink symbol, 'U' represents the uplink symbol, and 'F' represents the flexible symbol.

[2802] The SFI-index field value of DCI format 2_0 indicates to the UE the slot format for the number of slots of each DL BWP or UL BWP, starting from the slot where the UE detects DCI format 2_0.

[2804] For serving cells, symbols are classified as downlink, uplink, flexible symbols, or SBFD according to tdd-UL-DL-ConfigurationCommon, tdd-UL-DL-ConfigurationDedicated, SBFD-time-resource-config, and DCI format 2_0.

[2806] For L-BWP, the UE determines the symbol type based on the cell-specific static slot configuration (TDD-UL-DL-ConfigCommon), then based on the UE-specific static slot configuration (TDD-UL-DL-ConfigDedicated), and finally based on the cell-specific dynamic slot configuration (DCI format 2_0). More specifically, if a symbol is marked as an uplink or downlink with a high priority, the symbol is considered an uplink or downlink regardless of the low priority. If a symbol is marked as flexible with a high priority, the next highest priority is considered.

[2808] In the case of S-BWP, the UE determines the symbol type based on the cell-specific sbfd configuration (SBFD-time-resource-config), then based on the cell-specific static slot configuration (TDD-UL-DL-ConfigCommon), then based on the UE-specific static slot configuration (TDD-UL-DL-ConfigDedicated), and then based on the cell-specific dynamic slot configuration (DCI format 2_0). More specifically, it is first determined whether a symbol is an SBFD symbol or a non-SBFD symbol according to the cell-specific sbfd configuration. Then, if the symbol is a non-SBFD symbol, the symbol type is further determined based on the remaining indications.

[2809] For example, in Case 15, if the symbol is displayed as follows:

[2810] >: Downlinked by tdd-UL-DL-ConfigCommon;

[2811] >: Flexible via tdd-UL-DL-ConfigDedicated;

[2812] >: As an uplink by DCI format 2_0; and

[2814] *>: As a non-SBFD symbol by SBFD-time-resource-config,

[2815] The UE considers the corresponding symbol as a downlink symbol for both L-BWP and S-BWP.

[2817] As another example, in Case 54, where the symbol is displayed as follows:

[2818] >: Flexible via tdd-UL-DL-ConfigCommon;

[2819] >: Flexible via tdd-UL-DL-ConfigDedicated;

[2820] >: As an uplink by DCI format 2_0; and

[2821] As an SBFD symbol by SBFD-time-resource-config,

[2822] L-BWP is identical to PRB of the non-SBFD symbol.

[2823] L-BWP is identical to the second specific PRB of the SBFD symbol.

[2824] S-BWP is identical to a specific PRB of the SBFD symbol.

[2825] A specific PRB is the PRB of the UL subband. The UL subband is configured by scs-SpecificCarrierList. The UL subband is a subband for FD (full-duplex). The UL subband is configured by the FrequencyDomainResourceParameters of SbfdConfigCommon. The UL subband is configured by ul-subbandlocationAndBandwidth.

[2826] The second specific PRB is the PRB of the DL subband. The DL subband is configured by dl-subbandlocationAndBandwidth.

[2827] L-BWP is the same as BWP that does not contain a specific PRB.

[2828] S-BWP is the same as a BWP containing at least one PRB of a specific PRB.

[2830] The UE considers the corresponding symbol as an uplink symbol for L-BWP and as an SBFD symbol for S-BWP.

[2831] The table below lists examples.

[2832] CASE Comm Ded DCI SBFD L-BWP S-BWP 1 D D D N D D 2 D D F N D D 3 D D U N D D 4 D D D Y D sbfd 5 D D F Y D sbfd 6 D D U Y D sbfd 7 D U D N D D 8 D U F N D D 9 D U U N D D 10 D U D Y D sbfd 11 D U F Y D sbfd 12 D U U Y D sbfd 13 D F D N D D 14 D F F N D D 15 D F U N D D 16 D F D Y D sbfd 17 D F F Y D sbfd 18 D F U Y D sbfd 19 U D D N U U 20 U D F N U U 21 U D U N U U 22 U D D Y U sbfd 23 U D F Y U sbfd 24 U D U Y U sbfd 25 U U D N U U 26 U U F N U U 27 U U U N U U 28 U U D Y U sbfd 29 U U F Y U sbfd 30 U U U Y U sbfd 31 U F D N U U 32 U F F N U U 33 U F U N U U 34 U F D Y U sbfd 35 U F F Y U sbfd 36 U F U Y U sbfd 37 F D D N D D 38 F D F N D D 39 F D U N D D 40 F D D Y D sbfd 41 F D F Y D sbfd 42 F D U Y D sbfd 43 F U D N U U 44 F U F N U U 45 F U U N U U 46 F U D Y U sbfd 47 F U F Y U sbfd 48 F U U Y U sbfd 49 F F D N D D 50 F F F N F F 51 F F U N U U 52 F F D Y D sbfd 53 F F F Y F sbfd 54 F F U Y U sbfd D: Downlink; U: Uplink; F: Flexible; Y: SBFD symbol; N: non-SBFD symbol; sbfd: SBFD symbolComm: TDD-UL-DL-ConfigCommon; Ded: TDD-UL-DL-ConofigDedicatedSBFD: SBFD-time-resource-config; DCI: DCI format 2_0

[2833] If the UE is not configured with a SlotFormatIndicator by the upper layer, the UE performs the following actions.

[2835] In the case of L-BWP:

[2836] For the symbol set of the slot marked as an uplink to the UE by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated:

[2837] >>: UE does not receive PDCCH, PDSCH, or CSI-RS if PDCCH, PDSCH, or CSI-RS overlaps even partially with the slot's symbol set.

[2838] >>: The UE receives PDCCH, PDSCH, or CSI-RS if PDCCH, PDSCH, or CSI-RS does not overlap with the slot's symbol set at all.

[2839] For the symbol set of the slot marked as an uplink to the UE by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated:

[2840] >>: If the UE is not provided with a measurement gap, it does not receive DL PRS from the symbol set of the slot.

[2841] >>: When the UE is provided with a measurement gap, it receives DL PRS from the symbol set of the slot.

[2842] For the symbol set of a slot marked as a downlink to the UE by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated:

[2843] >>: UE does not transmit PUSCH, PUCCH, PRACH, or SRS if PUSCH, PUCCH, PRACH, or SRS overlaps even partially with the slot's symbol set.

[2844] >>: UE transmits PUSCH, PUCCH, PRACH, or SRS if PUSCH, PUCCH, PRACH, or SRS does not overlap with the slot's symbol set at all.

[2845] For the symbol set of the slot indicated to the UE for receiving SS / PBCH blocks by SIB1's ssb-PositionsInBurst or ServingCellConfigCommon's ssb-PositionsInBurst:

[2846] >>: If a transmission occurs when a symbol in the slot's symbol set overlaps with any symbol, the UE does not transmit PUSCH, PUCCH, or PRACH in the slot.

[2847] >>: If it does not overlap with any symbol in the slot's symbol set, the UE transmits PUSCH, PUCCH, or PRACH in the slot.

[2848] >>: The UE does not transmit SRS in the slot's symbol set.

[2849] >>: The UE transmits the SRS from the slot's symbol set.

[2850] >>: The UE does not expect the slot's symbol set to be uplinked by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated (when provided to the UE).

[2851] In the case of S-BWP:

[2852] (Regarding receiving download links)

[2853] For the symbol set of the slot marked as an uplink to the UE by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated; or

[2854] For the symbol set of a slot marked as a downlink to the UE by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated and marked as an SBFD symbol by SBFD-time-resource-config;

[2855] >>: UE does not receive PDCCH, PDSCH, or CSI-RS if PDCCH, PDSCH, or CSI-RS overlaps even partially with the slot's symbol set.

[2856] >>: The UE receives PDCCH, PDSCH, or CSI-RS if PDCCH, PDSCH, or CSI-RS does not overlap with the slot's symbol set at all.

[2858] (Regarding Downlink PRS)

[2859] For the symbol set of the slot marked as an uplink to the UE by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated; or

[2860] For the symbol set of a slot marked as a downlink to the UE by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated and marked as an SBFD symbol by SBFD-time-resource-config;

[2861] >>: The UE does not receive DL PRS from the symbol set of the slot if no measurement gap is provided.

[2862] >>: The UE receives DL PRS from the symbol set of the slot when a measurement gap is provided.

[2864] (Regarding uplink transmission)

[2865] For the symbol set of a slot that is marked as a downlink to the UE by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated and is not marked as an SBFD symbol by SBFD-time-resource-config:

[2866] >>: UE does not transmit PUSCH, PUCCH, PRACH, or SRS if PUSCH, PUCCH, PRACH, or SRS overlaps even partially with the slot's symbol set.

[2867] >>: UE transmits PUSCH, PUCCH, PRACH, or SRS if PUSCH, PUCCH, PRACH, or SRS does not overlap with the slot's symbol set at all.

[2868] For the symbol set of a slot marked as a downlink to the UE by tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated and marked as an SBFD symbol by SBFD-time-resource-config:

[2869] >>: The UE transmits PUSCH, PUCCH, PRACH, or SRS from the slot's symbol set. (Content regarding SSB)

[2870] If the symbol set of the slot marked for receiving an SS / PBCH block to the UE by SIB1's ssb-PositionsInBurst is not an SBFD symbol,

[2871] >>: UE does not transmit PUSCH, PUCCH, or PRACH from the slot.

[2872] >>: The UE does not transmit SRS in the slot's symbol set.

[2874] If the symbol set of the slot marked for receiving SS / PBCH blocks to the UE by SIB1's ssb-PositionsInBurst is marked with SBFD symbols,

[2875] >>: The UE transmits PUSCH, PUCCH, and PRACH from the slot.

[2876] >>: The UE transmits the SRS from the slot's symbol set.

[2878] If the UE is configured as a SlotFormatIndicator by the upper layer, the UE is provided with the SFI-RNTI by sfi-RNTI and the payload size by DCI format 2_0. The UE performs the following operations.

[2880] In the case of L-BWP,

[2881] For the symbol set of slots flexibly represented to the UE by tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated, and if the UE detects DCI format 2_0 providing a format for the slot and the slot format value is not 255:

[2882] >>: If one or more symbols in the symbol set are symbols of the CORESET configured for PDCCH monitoring in the UE, the UE receives PDCCH from the CORESET only if the SFI-index field value of DCI format 2_0 indicates that one or more symbols are downlink symbols.

[2883] >>: If the SFI-index field value of DCI format 2_0 flexibly represents the symbol set of the slot and the UE detects the DCI format to receive PDSCH or CSI-RS from the symbol set of the slot, the UE receives PDSCH or CSI-RS from the symbol set of the slot.

[2884] >>: If the SFI-index field value of DCI format 2_0 flexibly represents the symbol set of the slot and the UE detects DCI format, RAR UL grant, fallbackRAR UL grant, or successRAR that the UE should transmit PUSCH, PUCCH, PRACH, or SRS from the symbol set of the slot, the UE transmits PUSCH, PUCCH, PRACH, or SRS from the symbol set of the slot.

[2885] >>: If the SFI-index field value of DCI format 2_0 flexibly indicates the symbol set of the slot and the UE does not detect DCI format, RAR UL grant, fallbackRAR UL grant, or successRAR instructing the UE to receive PDSCH or CSI-RS, or if the UE does not detect DCI format, RAR UL grant, fallbackRAR UL grant, or successRAR instructing the UE to transmit PUSCH, PUCCH, PRACH, or SRS from the symbol set of the slot, the UE does not transmit or receive from the symbol set of the slot.

[2886] >>: If the UE is configured by the upper layer to receive PDSCH or CSI-RS from the slot's symbol set, the UE receives PDSCH or CSI-RS from the slot's symbol set only if the SFI-index field value of DCI format 2_0 indicates the slot's symbol set as downlink, and if applicable, the slot's symbol set is within the remaining channel occupancy period.

[2887] If the UE is configured by the upper layer to receive DL PRS from the slot's symbol set, the UE receives DL PRS from the slot's symbol set only when the SFI-index field value of DCI format 2_0 indicates the slot's symbol set as downlink or flexible.

[2888] If the UE is configured by the upper layer to transmit PUCCH, PUSCH, or PRACH from the slot's symbol set, the UE transmits PUCCH, PUSCH, or PRACH from the slot only when the SFI-index field value of DCI format 2_0 indicates the slot's symbol set as an uplink.

[2889] If the UE is configured by the upper layer to transmit SRS from the symbol set of a slot, the UE transmits SRS only from the symbol set of the slot indicated as the uplink symbol by the SFI-index field value of DCI format 2_0.

[2890] The UE does not expect to detect one or more symbols in the slot's symbol set that transmit SRS, PUSCH, PUCCH, or PRACH in DCI format, RAR UL grant, fallbackRAR UL grant, or successRAR at the same time as the SFI-index field value of DCI format 2_0 indicates the slot's symbol set as downlink.

[2891] >>: The UE does not expect the SFI-index field value of DCI format 2_0 to indicate a downlink or flexible symbol set of a slot, especially if the symbol set of a slot contains symbols associated with the repetition of a PUSCH transmission (if enabled by UL Type 2 grant PDCCH, see Clause 10.2).

[2892] The UE does not expect to detect a DCI format that receives PDSCH or CSI-RS from one or more symbols in the slot's symbol set when the SFI-index field value of DCI format 2_0 indicates the slot's symbol set as an uplink.

[2894] In the case of S-BWP,

[2895] In the symbol set of slots flexibly marked to the UE by tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated, if they are marked as non-SBFD symbols by SBFD-time-resource-config, and the UE detects DCI format 2_0 providing a format for the slot and the slot format value is not 255:

[2896] >>: If one or more symbols in the symbol set are symbols of the CORESET configured for PDCCH monitoring in the UE, the UE receives PDCCH from the CORESET only if the SFI-index field value of DCI format 2_0 indicates that one or more symbols are downlink symbols.

[2897] >>: If the SFI-index field value of DCI format 2_0 flexibly represents the symbol set of the slot and the UE detects the DCI format to receive PDSCH or CSI-RS from the symbol set of the slot, the UE receives PDSCH or CSI-RS from the symbol set of the slot.

[2898] >>: If the SFI-index field value of DCI format 2_0 flexibly represents the symbol set of the slot and the UE detects DCI format, RAR UL grant, fallbackRAR UL grant, or successRAR that the UE should transmit PUSCH, PUCCH, PRACH, or SRS from the symbol set of the slot, the UE transmits PUSCH, PUCCH, PRACH, or SRS from the symbol set of the slot.

[2899] >>: If the SFI-index field value of DCI format 2_0 flexibly indicates the symbol set of the slot and the UE does not detect DCI format, RAR UL grant, fallbackRAR UL grant, or successRAR instructing the UE to receive PDSCH or CSI-RS, or if the UE does not detect DCI format, RAR UL grant, fallbackRAR UL grant, or successRAR instructing the UE to transmit PUSCH, PUCCH, PRACH, or SRS from the symbol set of the slot, the UE does not transmit or receive from the symbol set of the slot.

[2900] If the UE is configured by the upper layer to receive PDSCH or CSI-RS from the slot's symbol set, the UE receives PDSCH or CSI-RS from the slot's symbol set only if the SFI-index field value of DCI format 2_0 indicates the slot's symbol set as downlink, and if applicable, the slot's symbol set is within the remaining channel occupancy period.

[2901] >>: If the UE is configured by the upper layer to receive DL PRS from the slot's symbol set, the UE receives DL PRS from the slot's symbol set only when the SFI-index field value of DCI format 2_0 indicates the slot's symbol set as downlink or flexible.

[2902] If the UE is configured by the upper layer to transmit PUCCH, PUSCH, or PRACH from the slot's symbol set, the UE transmits PUCCH, PUSCH, or PRACH from the slot only when the SFI-index field value of DCI format 2_0 indicates the slot's symbol set as an uplink.

[2903] If the UE is configured by the upper layer to transmit SRS from the symbol set of a slot, the UE transmits SRS only from the symbol set of the slot indicated as the uplink symbol by the SFI-index field value of DCI format 2_0.

[2904] The UE does not expect to detect one or more symbols in the slot's symbol set that transmit SRS, PUSCH, PUCCH, or PRACH in DCI format, RAR UL grant, fallbackRAR UL grant, or successRAR at the same time as the SFI-index field value of DCI format 2_0 indicates the slot's symbol set as downlink.

[2905] >>: If the slot's symbol set contains symbols associated with the repetition of a PUSCH transmission, the UE does not expect the SFI-index field value of DCI format 2_0 to indicate the slot's symbol set as downlink or flexible (if enabled by UL Type 2 grant PDCCH, see Clause 10.2).

[2906] The UE does not expect to detect a DCI format that receives PDSCH or CSI-RS from one or more symbols in the slot's symbol set when the SFI-index field value of DCI format 2_0 indicates the slot's symbol set as an uplink.

[2908] In the case of S-BWP,

[2909] If the symbol set of slots flexibly represented to the UE by tdd-UL-DL-ConfigurationCommon and tdd-UL-DL-ConfigurationDedicated is represented as SBFD symbols by SBFD-time-resource-config, and the UE detects DCI format 2_0 providing a format for the slot and the slot format value is not 255:

[2910] If one or more symbols in the symbol set are symbols of a CORESET configured for PDCCH monitoring in the UE, the UE does not receive PDCCH from the CORESET regardless of whether the SFI-index field value of DCI format 2_0 indicates the symbol set of the slot as uplink, downlink, or flexible.

[2911] >>: When the UE detects a DCI format that calls for receiving PDSCH or CSI-RS from the slot's symbol set, the UE does not receive PDSCH or CSI-RS from the slot's symbol set, regardless of whether the SFI-index field value of DCI format 2_0 indicates the slot's symbol set as uplink, downlink, or flexible.

[2912] >>: When the UE detects DCI format, RAR UL grant, fallbackRAR UL grant, or successRAR and is instructed to transmit PUSCH, PUCCH, PRACH, or SRS from the slot's symbol set, the UE transmits PUSCH, PUCCH, PRACH, or SRS from the slot's symbol set regardless of whether the SFI-index field value of DCI format 2_0 indicates the slot's symbol set as uplink, downlink, or flexible.

[2913] >>: If the UE does not detect a DCI format RAR UL grant, fallbackRAR UL grant, or successRAR to transmit PUSCH, PUCCH, PRACH, or SRS from the slot's symbol set, the UE does not transmit or receive from the slot's symbol set, regardless of whether the SFI-index field value of DCI format 2_0 indicates the slot's symbol set as uplink, downlink, or flexible.

[2914] If the UE is configured by the upper layer to receive PDSCH or CSI-RS from the slot's symbol set, the UE does not receive PDSCH or CSI-RS from the slot's symbol set regardless of whether the SFI-index field value of DCI format 2_0 indicates the slot's symbol set as uplink, downlink, or flexible.

[2915] If the UE is configured by the upper layer to receive DL PRS from the slot's symbol set, the UE does not receive DL PRS from the slot's symbol set regardless of whether the SFI-index field value of DCI format 2_0 indicates the slot's symbol set as uplink, downlink, or flexible.

[2916] If the UE is configured by the upper layer to transmit PUCCH, PUSCH, or PRACH from the slot's symbol set, the UE transmits PUCCH, PUSCH, or PRACH from the slot regardless of whether the SFI-index field value of DCI format 2_0 indicates the slot's symbol set as uplink, downlink, or flexible.

[2917] If the UE is configured by the upper layer to transmit an SRS from the slot's symbol set, the UE transmits the SRS regardless of whether the SFI-index field value of DCI format 2_0 indicates the slot's symbol set as uplink, downlink, or flexible.

[2918] >>: If the UE detects a DCI format 2_0 SFI-index field value indicating that the slot's symbol set is downlink and a DCI format RAR UL grant, fallbackRAR UL grant, or successRAR in one or more symbols of the slot's symbol set to transmit SRS, PUSCH, PUCCH, or PRACH, the UE transmits SRS, PUSCH, PUCCH, or PRACH in one or more symbols of the slot's symbol set.

[2919] The UE does not expect to detect a DCI format in which the SFI-index field value of DCI format 2_0 indicates that the slot's symbol set is an uplink and that PDSCH or CSI-RS is to be received from one or more symbols of the slot's symbol set.

[2921] The GNB can configure periodic transmission and / or reception to the UE for various purposes. For example:

[2922] Periodic CSI-RS is configured in the BWP to allow the UE to measure CSI-RS;

[2923] Periodic DL PRS is configured for the UE to perform position measurements;

[2924] An allocation configured based on semi-permanent scheduling is configured in the BWP so that the UE receives PDSCH without dynamic scheduling;

[2925] PUCCH (HARQ Feedback / CSI-RS Report / SR) is configured in the BWP so that the UE performs PUCCH (HARQ Feedback / CSI-RS Report / SR) transmission;

[2926] The configured contract is configured in the BWP so that the UE transmits PUSCH without dynamic scheduling;

[2927] SRS is configured in the BWP so that the UE transmits SRS.

[2929] This time pattern information for periodic transmission / reception represents a set of symbols that occur periodically. If the set of symbols for periodic transmission / reception is not aligned with the direction of periodic transmission / reception, the UE and GNB determine whether to perform periodic transmission / reception based on the classification of the symbols.

[2931] For example, in Case 4, if the symbol is displayed as follows:

[2932] >: Downlinked by tdd-UL-DL-ConfigCommon;

[2933] >: Downlink by tdd-UL-DL-ConfigDedicated;

[2934] >: Downlinked by DCI format 2_0; and

[2935] As an SBFD symbol by SBFD-time-resource-config,

[2936] If this symbol is configured as CSI-RS in L-BWP, the UE receives CSI-RS from that symbol;

[2937] If this symbol is configured as CSI-RS in S-BWP, the UE does not receive CSI-RS from that symbol;

[2938] If this symbol is configured as a PUCCH resource for SR in L-BWP, the UE does not send an SR to the PUCCH from that symbol;

[2939] If this symbol is configured as a PUCCH resource for SR in S-BWP, the UE sends an SR from that symbol to the PUCCH.

[2940] Indication classification PDSCH / CSI-RS / DL-PRS PUCCH / PUSCH / PRACH / SRS CASE Comm Ded DCI SBFD L-BWP S-BWP L-BWP S-BWP L-BWP S-BWP 1 D D D N D D rx rx no tx no tx 2 D D F N D D rx rx no tx no tx 3 D D U N D D rx rx no tx no tx 4 D D D Y D sbfd rx no rx no tx tx 5 D D F Y D sbfd rx no rx no tx tx 6 D D U Y D sbfd rx no rx no tx tx 7 D U D N D D rx rx no tx no tx 8 D U F N D D rx rx no tx no tx 9 D U U N D D rx rx no tx no tx 10 D U D Y D sbfd rx no rx no tx tx 11 D U F Y D sbfd rx no rx no tx tx 12 D U U Y D sbfd rx no rx no tx tx 13 D F D N D D rx rx no tx no tx 14 D F F N D D rx rx no tx no tx 15 D F U N D D rx rx no tx no tx 16 D F D Y D sbfd rx no rx no tx tx 17 D F F Y D sbfd rx no rx no tx tx 18 D F U Y D sbfd rx no rx no tx tx 19 U D D N U U no rx no rx tx tx 20 U D F N U U no rx no rx tx tx 21 U D U N U U no rx no rx tx tx 22 U D D Y U sbfd no rx no rx tx tx 23 U D F Y U sbfd no rx no rx tx tx 24 U D U Y U sbfd no rx no rx tx tx 25 U U D N U U no rx no rx tx tx 26 U U F N U U no rx no rx tx tx 27 U U U N U U no rx no rx tx tx 28 U U D Y U sbfd no rx no rx tx tx 29 U U F Y U sbfd no rx no rx tx tx 30 U U U Y U sbfd no rx no rx tx tx 31 U F D N U U no rx no rx tx tx 32 U F F N U U no rx no rx tx tx 33 U F U N U U no rx no rx tx tx 34 U F D Y U sbfd no rx no rx tx tx 35 U F F Y U sbfd no rx no rx tx tx 36 U F U Y U sbfd no rx no rx tx tx 37 F D D N D D rx rx no tx no tx 38 F D F N D D rx rx no tx no tx 39 F D U N D D rx rx no tx no tx 40 F D D Y D sbfd rx no rx no tx tx 41 F D F Y D sbfd rx no rx no tx tx 42 F D U Y D sbfd rx no rx no tx tx 43 F U D N U U no rx no rx tx tx 44 F U F N U U no rx no rx tx tx 45 F U U N U U no rx no rx tx tx 46 F U D Y U sbfd no rx no rx tx tx 47 F U F Y U sbfd no rx no rx tx tx 48 F U U Y U sbfd no rx no rx tx tx 49 F F D N D D rx rx no tx no tx 50 F F F N F F no rx no rx no tx no tx 51 F F U N U U no rx no rx tx tx 52 F F D Y D sbfd rx no rx no tx tx 53 F F F Y F sbfd no rx no rx no tx tx 54 F F U Y U sbfd no rx no rx tx tx

[2941] Time pattern information is summarized in the table below.

[2942] periodic signal time pattern parameters CSI-RS ServingCellConfig / CSI-MeasConfig / CSI-ResourceConfig / NZP-CSI-RS-Resource / CSI-ResourcePeriodicityAndOffset AND CSI-RS-ResourceMapping DL-PRS NR-DL-PRS-Info-r16 / dl-PRS-Periodicity-and-ResourceSetSlotOffset AND dl-PRS-NumSymbols SPS ServingCellConfig / BWP-DownlinkDedicated / SPS-Config / periodicity ; ANDDCI 1_1 in TimeDomain Resource Allocation PUCCH for CSI-RS ServingCellConfig / CSI-MeasConfig / CSI-ReportConfig / CSI-ReportPeriodicityAndOffset ServingCellConfig / BWP-UplinkDedicated / PUCCH-Config / PUCCH-Resource / startingPRB ServingCellConfig / BWP-UplinkDedicated / PUCCH-Config / PUCCH-format_n / nrofSymbols PUCCH for A / N ServingCellConfig / BWP-UplinkDedicated / PUCCH-Config / dl-DataToUL-ACK-DCI; AND DCI 1_x / PDSCH-to-HARQ_feedback timing indicator in DCI 1_x; x = 0, 1, 2 or 3 PUCCH for SR ServingCellConfig / BWP-UplinkDedicated / PUCCH-Config / SchedulingReq...

Claims

Claim 1 A method of a terminal in a wireless communication system, wherein the terminal receives a predetermined system information block from a base station, the predetermined system information block comprises: parameters for the frequency domain portion of the uplink bandwidth for a Sub-band Full Duplex (SBFD); a set of parameters for the time domain portion of the SBFD; and a set of parameters for a cell-specific Time Division Multiple Access (TDD) configuration; wherein the terminal receives a radio resource control (RRC) message from a base station, the RRC message comprises: parameters for the position of a slot format indicator (SFI) index field within specific downlink control information (DCI); and parameters for monitoring periodicity for specific DCI; wherein the terminal receives specific downlink control information (DCI) from a base station; and wherein the terminal performs a downlink reception for a first symbol, the first symbol is determined as a flexible symbol by a set of parameters for a cell-specific TDD configuration; is not within the time domain portion of the SBFD; and is determined as a downlink symbol by an SFI index. A method comprising the step of determining based on; and a terminal performing uplink transmission for a second symbol, wherein the second symbol is determined based on: a flexible symbol determined by a set of parameters of a cell-specific TDD configuration; being within a time domain portion of an SBFD; and being determined as a downlink symbol by an SFI index; and wherein the uplink transmission in the second symbol is performed within a frequency domain portion of the uplink bandwidth for an SBFD. Claim 2 A method according to claim 1, wherein the time domain portion for the SBFD is composed of continuous symbols, and the start and end symbols of the time domain portion for the SBFD are determined according to the set of parameters of the time domain portion for the SBFD. Claim 3 A method according to claim 1, wherein the first symbol is determined to be a flexible symbol when the first symbol is neither a downlink symbol nor an uplink symbol according to a set of parameters of a cell-specific TDD configuration. Claim 4 A method according to claim 2, characterized in that the first symbol is not in the time domain for SBFD if it is not one of the consecutive symbols, and the second symbol is in the time domain for SBFD if it is one of the consecutive symbols. Claim 5 A method according to claim 1, wherein the SFI index collectively represents a plurality of slot types for a plurality of slots, each of the plurality of slot types represents a symbol type of the corresponding slot, and the symbol type is one of a downlink symbol, a flexible symbol, or an uplink symbol. Claim 6 A method according to claim 1, further comprising the step of performing an uplink transmission in a third symbol for a first sounding reference signal (SRS), wherein: the third symbol is represented as a downlink symbol by a set of parameters of a cell-specific TDD configuration; and the configuration parameters for the first SRS include instructions related to SBFD; and further comprising the step of performing an uplink transmission in a fourth symbol for a second SRS, wherein: the fourth symbol is represented as an uplink symbol by a set of parameters of a cell-specific TDD configuration; and the configuration parameters for the second SRS do not include the instructions related to SBFD. Claim 7 A terminal of a wireless communication system comprises: a transceiver configured to transmit and receive signals; and a control unit, wherein the control unit receives a predetermined system information block from a base station, the predetermined system information block includes: parameters for the frequency domain portion of the uplink bandwidth for a Sub-band Full Duplex (SBFD); a set of parameters for the time domain portion of the SBFD; and a set of parameters for a cell-specific Time Division Multiple Access (TDD) configuration; receives a radio resource control (RRC) message from a base station, the RRC message includes: parameters for the position of a slot format indicator (SFI) index field within specific downlink control information (DCI); and parameters for monitoring periodicity for the specific DCI; receives specific downlink control information (DCI) from a base station, performs downlink reception for a first symbol, the first symbol is determined as a flexible symbol by a set of parameters for the cell-specific TDD configuration; and is not within the time domain portion of the SBFD. A terminal characterized by being determined based on a downlink symbol determined by an SFI index, and configured to perform uplink transmission for a second symbol, wherein the second symbol is determined based on: a flexible symbol determined by a set of parameters of a cell-specific TDD configuration; being within the time domain portion of an SBFD; and being determined as a downlink symbol by an SFI index; and wherein uplink transmission in the second symbol is performed within the frequency domain portion of the uplink bandwidth for an SBFD. Claim 8 A method performed by a base station of a wireless communication system comprises the step of the base station transmitting a predetermined system information block to a terminal, wherein the predetermined system information block includes: parameters for the frequency domain portion of the uplink bandwidth for a Sub-band Full Duplex (SBFD); a set of parameters for the time domain portion of the SBFD; and a set of parameters for a cell-specific Time Division Multiple Access (TDD) configuration; the step of the base station transmitting a Radio Resource Control (RRC) message to a terminal, wherein the RRC message includes: parameters for the position of a Slot Format Indicator (SFI) index field within specific Downlink Control Information (DCI); and parameters for monitoring periodicity for specific DCI; the step of the base station transmitting specific Downlink Control Information (DCI) to a terminal; and the step of the base station performing a downlink transmission for a first symbol, wherein the first symbol is determined as a flexible symbol by a set of parameters for a cell-specific TDD configuration; is not within the time domain portion of the SBFD; and is determined as a downlink symbol by an SFI index; A method comprising the step of determining based on; and a base station performing uplink reception for a second symbol, wherein the second symbol is determined as a flexible symbol by a set of parameters of a cell-specific TDD configuration; is within a time domain portion of the SBFD; and is determined as a downlink symbol by an SFI index; and wherein uplink reception in the second symbol is performed within a frequency domain portion of the uplink bandwidth for the SBFD.

Images