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

Abstract

A random access method for a user device (UE) in a wireless communication system is provided. The method comprises the steps of initiating a random access procedure, determining a random access opportunity type (RO-type), determining a random access resource set, and transmitting a preamble. The random access resource set is selected based on whether Msg1 repetition is applicable. For a 2nd-RO associated with subband full-duplex operation, the applicability of Msg1 repetition is determined using sbfd-RSRP-ThresholdMsg1-RepetitionNumX by comparing the reference signal received power of a downlink path loss reference. The preamble transmission power is determined based on preambleReceivedTargetPower of sbfd-RACH-SingleConfig-preambleReceivedTargetPower or sbfd-RACH-DualConfig for the 2nd-RO, or based on preambleReceivedTargetPower of RACH-ConfigCommon for the 1st-RO, along with power ramping parameters.

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. In TDD, time-domain resources are divided into downlink and uplink. In TDD, allocating a limited time period to the uplink reduces coverage, increases latency, and reduces capacity. As a possible improvement, the simultaneous existence of downlink and uplink, also known as full duplex, or more specifically, subband non-overlapping full duplex (SBFD), on the gNB side within the conventional TDD band can be considered. The problem to be solved

[0003] The objective of the present invention is to provide a method for performing efficient random access by determining whether to repeatedly apply Msg1 according to the random access opportunity type and setting an appropriate transmission power in a subband full-duplex (SBFD) operating environment. means of solving the problem

[0004] The present invention relates to a random access method of a user device (UE) in a wireless communication system that supports subband full-duplex (SBFD) operation with a Msg1 repeat function.

[0005] According to one aspect of the present invention, a random access method comprises: initiating a random access procedure; determining a random access opportunity type (RO-type); determining a set of random access resources based on whether Msg1 repetition is applicable; determining random access resources; and transmitting a preamble. If the RO-type is 2nd-RO, the applicability of Msg1 repetition is determined based on a second set of parameters including sbfd-RSRP-ThresholdMsg1-RepetitionNumX. If the RO-type is 1st-RO, a first set of parameters including RSRP-ThresholdMsg1-RepetitionNumX is used, where X is 2, 4, or 8.

[0006] According to another aspect of the present invention, the method comprises the steps of selecting an SSB based on SS-RSRP, determining a set of available PRACH opportunities consisting of n valid PRACH opportunities having time-continuous and identical frequency resources and SSB indices, and determining a preamble received target power. The power is set based on the preambleReceivedTargetPower of sbfd-RACH-SingleConfig-preambleReceivedTargetPower or sbfd-RACH-DualConfig for the 2nd-RO, or based on the preambleReceivedTargetPower of RACH-ConfigCommon for the 1st-RO. Effects of the invention

[0007] According to the present disclosure, by applying differentiated RSRP thresholds and power control parameters for each random access opportunity type in a subband full-duplex (SBFD) operating environment, it is possible to improve the random access success rate under various channel conditions and achieve efficient resource utilization. Brief explanation of the drawing

[0009] Figure 1 is a diagram showing the architecture of a 5G system and NG-RAN. Figure 2 is a diagram showing the wireless protocol architecture in a 5G system. Figure 3 illustrates a random access procedure. Figure 4 is a diagram showing 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 shows an example of a resource pool. Figure 11 is a diagram showing 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 showing the ASN.1 structure of SIB1 in relation to the RACH configuration. Figure 14 shows an example of the RACH case. Figure 15 illustrates a RACH operation based on SBFD. Figure 16 illustrates examples of RACH cases and feature combinations. Figure 17 illustrates another example of a frequency domain structure. Figure 18 illustrates the MAC PDU format. Figure 19 shows the format of a random access response. Figure 20 shows an example of PUSCH resource selection. Figure 21 shows an example of a cell's BWP. Figure 22 is a diagram showing the ASN.1 structure of SIB1 and RRCReconfiguration. Figure 23 is a diagram showing the ASN.1 structure of BWP configuration information. Figure 24 is a diagram showing the ASN.1 structure of the TDD uplink downlink configuration. Figure 25 shows examples of S-BWP and L-BWP of the cell. Figure 26 shows examples of virtual symbols and real symbols. Figure 27 illustrates the operation of the UE and GNB. Figure 28 is a flowchart showing the operation of a terminal. FIG. 29 is a block diagram showing a UE to which the disclosure is applied. FIG. 30 is a block diagram showing a base station according to the present disclosure. Figure 31 is a diagram illustrating RACH setting 1. Figure 32 is a diagram illustrating RACH setting 2. FIG. 33 is a diagram illustrating the operation of a terminal and a base station related to a successful random access procedure. FIG. 34 is a diagram illustrating the operation of a terminal and a base station related to an unsuccessful random access procedure. FIG. 35 is a block diagram showing terminal operation. Figure 36 is a block diagram showing base station operation. Specific details for implementing the invention

[0010] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. Furthermore, in the description of the present disclosure, if it is determined that a detailed description of related known functions or configurations may unnecessarily obscure the essence of the present disclosure, such detailed description will be omitted. Additionally, the terms described below are defined in consideration of their functions in the present disclosure, and these may vary depending on the intentions or customs of the user and operator. Therefore, definitions must be based on the entire content of this specification.

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

[0012] In the following description, terms and definitions provided in the 3GPP standard are used for convenience of explanation. However, the present disclosure is not limited by the use of these terms and definitions, and any other terms and definitions may be used instead.

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

[0014] Terminal and UE and wireless device;

[0015] IE (Information Element) and parameter set;

[0016] Parameters and 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 disclosed content 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 toward the UE; or

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

[0023] gNB 1A05 or 1A06 and ng-eNB 1A03 or 1A04 are interconnected via the Xn interface. The gNB and ng-eNB are also 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 can be implemented as physical nodes or as separate physical nodes.

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

[0025] >1: Functions for radio resource management such as Radio Bearer Control, Radio Admission Control, Connection Mobility Control, and dynamic allocation (scheduling) of resources for UEs in uplink, downlink, and sidelink; and

[0026] >1: IP and Ethernet header compression, uplink data decompression and user data stream encryption; and

[0027] >1: Selection of the AMF in the UE attachment when routing to the MME cannot be determined from the information provided by the UE; and

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

[0029] >1: Scheduling and transmission of paging messages; and

[0030] >1: Scheduling and transmission of broadcast information (starting from AMF or O&M) and

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

[0032] >1: Session management; and

[0033] >1: QoS flow management and mapping of data to wireless bearer; and

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

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

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

[0037] FIG. 2 is a diagram illustrating the wireless protocol architecture in a 5G system to which the disclosure can be applied.

[0038] 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.

[0039] Each protocol sublayer performs functions related to the operations listed below.

[0040] NAS: Authentication, mobility management, security control, etc.

[0041] RRC: System information, paging, setup, maintenance, and release of RRC connections, security features, setup, configuration, maintenance, and release of Signaling Radio Bearer (SRB) and Data Radio Bearer (DRB), mobility, QoS management, wireless link failure detection and recovery, NAS message transmission, etc.

[0042] SDAP: Mapping between QoS flows and data wireless bearers, indication of QoS Flow ID (QFI) in both DL and UL packets.

[0043] PDCP: Data transmission, header compression and decompression, encryption and decryption, integrity protection and integrity verification, replication, reordering and sequential delivery, non-sequential delivery, etc.

[0044] RLC: Transmission of upper-layer PDUs, error correction via ARQ, segmentation and re-segmentation of RLC SDUs, SDU reassembly, RLC reset, etc.

[0045] MAC: Mapping between logical channels and transport channels, multiplexing / demultiplexing of MACs belonging to one or another logical channel transmitted to / from the physical layer of the transport channel into / at the TB (Transport Block) of an SDU, reporting scheduling information, handling priority processing between UEs, handling priority processing between logical channels of a single UE, etc.

[0046] PHY: Channel coding, physical layer hybrid ARQ processing, rate matching, scrambling, modulation, layer mapping, downlink control information, uplink control information, etc.

[0047] Between RRC_CONNECTED and RRC_INACTIVE, a state transition occurs through the exchange of Resume messages and Release messages containing Suspend IE.

[0048] State transitions occur between RRC_CONNECTED and RRC_IDLE through RRC connection establishment and RRC disconnection.

[0049] The UE supports three RRC states.

[0050] In RRC_IDLE, the UE has no RRC connection with the RAN. The UE monitors the paging 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.

[0051] In RRC_CONNECTED, the UE has a valid RRC connection with the RAN. The UE establishes a radio bearer configured for data transmission and reception. UE mobility is handled by network control 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.

[0052] In RRC_INACTIVE, the UE has terminated the RRC connection with the RAN. Before performing full data transmission, the terminal and the base station resume the terminated RRC connection. UE mobility is handled by idle mode mobility within the RAN defined area. If the UE can be configured by the base station, data transmission of a limited scale can be performed in the RRC_INACTIVE state, which is called the small data transmission procedure.

[0053] The RRC_IDLE state can be characterized as follows.

[0054] >1: PLMN Selection; System Information Broadcast;

[0055] >1: Cell reselection motility;

[0056] >1: Paging for mobile exit data is initiated by 5GC.

[0057] >1: DRX for CN paging configured on NAS.

[0058] The RRC_INACTIVE state can be characterized as follows.

[0059] >1: PLMN Selection; System Information Broadcast;

[0060] >1: Cell reselection motility;

[0061] >1: Paging is initiated by NG-RAN (RAN paging).

[0062] >1: The RAN-based notification region (RNA) is managed by NG-RAN.

[0063] >1: DRX for RAN paging configured by NG-RAN;

[0064] >1: 5GC - NG-RAN connectivity (both C / U planes) is established for the UE.

[0065] >1: The UE AS context is stored in NG-RAN, and the UE is

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

[0067] The RRC_CONNECTED state can be characterized as follows.

[0068] >1: 5GC - NG-RAN connectivity (both C / U planes) is established for the UE.

[0069] >1: The UE AS context is stored in NG-RAN, and the UE is

[0070] 1: NG-RAN knows the cell to which the UE belongs.

[0071] >1: Step of transmitting unicast data to / from the UE;

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

[0073] Figure 3 illustrates a random access procedure.

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

[0075] The random access procedure includes sending a preamble 3A21, receiving a random access response 3A31, sending message 3 3A41, and resolving contention 3A51.

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

[0077] The random access procedure can be triggered by several events, such as initial access from RRC_IDLE (e.g., RRC connection establishment procedure), arrival of DL or UL data, requests by RRC upon synchronous reconfiguration (e.g., handover), and the RRC connection resumption procedure from RRC_INACTIVE.

[0078] When a random access procedure is initiated, the UE can perform the following actions in sequence.

[0079] >1: Flush the buffer for message 3.

[0080] >1: Initializes the counter for preamble transmission and power ramping.

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

[0082] >1: Select a set of Random Access resources that can be applied to the current Random Access procedure.

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

[0084] >1: Select a random access preamble group based on the path loss of the selected SSB, the potential Msg3 size, and various parameters (e.g., ra-Msg3SizeGroupA, preambleReceivedTargetPower, msg3-DeltaPreamble, messagePowerOffsetGroupB, etc.). The preamble group selection allows the UE to request a larger uplink grant for Msg3 transmission when channel conditions are sufficiently good and the potential Msg3 size exceeds a specific threshold.

[0085] >1: A step of randomly selecting a random access preamble with equal probability from a random access preamble associated with a selected SSB and a selected random access preamble group;

[0086] >1: A step of determining the next available PRACH situation from the PRACH opportunity corresponding to the selected SSB;

[0087] >1: Determines the transmission power of the preamble.

[0088] >>2: Preamble transmit power = pathloss + preambleReceivedTargetPower + DELTA_PREAMBLE + (PREAMBLE_POWER_RAMPING_COUNTER - 1) × PREAMBLE_POWER_RAMPING_STEP + POWER_OFFSET_2STEP_RA

[0089] >1: A step of transmitting a preamble in a determined PRACH situation with a determined transmission power;

[0090] >1; Start ra-ResponseWindow.

[0091] >1: Monitor SpCell's PDCCH for random access responses identified by RA-RNTI while ra-ResponseWindow is running.

[0092] >1: Receiving a random access response comprising a MAC subPDU having a random access preamble identifier corresponding to the received preamble;

[0093] >1: Processes the received Timing Advanced Command and the received UL assignment.

[0094] >1: Send Msg 3 based on the received UL grant;

[0095] >>2: Message 3 may contain a CCCH SDU such as RRCSetupRequest or RRCResumeRequest, for example.

[0096] >1: Start ra-ContentionResolutionTimer.

[0097] >1: Monitor PDCCH while ra-ContentionResolutionTimer is running.

[0098] >1: When a MAC PDU containing the UE contention resolution ID MAC CE is received, the contention resolution is considered successful.

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

[0100] Sub-Band Full Duplex (SBFD) operation is supported for TDD carriers, enabling simultaneous downlink transmission and uplink reception at the gNB on each sub-band. From the UE perspective, full duplex is not supported. Configuration of per-cell SBFD time and frequency resources is provided via SIB1 or dedicated signaling.

[0101] If the GNB can use SBBF, the GNB provides I-BWP and UL-DL-TDD configurations (time pattern information) in legacy signaling fields and provides configuration information for SBFD in new signaling fields that only SBFD-capable UEs (hereinafter SBFD-UEs) can understand.

[0102] Figure 4 shows the signal structure of SIB1 for the frequency resource structure of the cell.

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

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

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

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

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

[0108] FrequencyInfoDL-SIB ::= SEQUENCE {

[0109] frequencyBandListMultiFrequencyBandListNR-SIB,

[0110] offsetToPointA INTEGER (0..2199);

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

[0112] }

[0113] The offsetToPointA field indicates the offset to point A, and the offset to point A provides a reference point for an SCS-specific carrier list. Point A serves as a common reference point for the resource block grid.

[0114] The scs-SpecificCarrierList field represents a set of carriers for different subcarrier spacings (numerologies). If a cell is configured with one or more SCSs, an SCS-SpecificCarrier IE is provided for each SCS.

[0115] IE SCS-SpecificCarrier provides parameters that determine the actual carrier position and width or the carrier bandwidth in a given direction. It is specifically defined for numerology (SCS (Subcarrier Spacing)) and the relationship with Point A (frequency offset).

[0116] SCS-SpecificCarrier ::= SEQUENCE {

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

[0118] subcarrierSpacing SubcarrierSpacing,

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

[0120] ...,

[0121] [[

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

[0123] ]]

[0124] }

[0125] The carrierBandwidth field indicates the width of this carrier in the number of PRBs (using the subcarrierSpacing defined for this carrier).

[0126] The offsetToCarrier field represents the offset in the frequency domain between point A (the lowest subcarrier of common RB 0) and the lowest available subcarrier of this carrier as the PRB number (using subcarrierSpacing defined for this carrier).

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

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

[0129] The IE SCS-SpecificCarrier for the uplink carrier (e.g., the SCS-SpecificCarrier of FrequencyInfoUL-SIB) further includes new signaling fields for the SBFD time / frequency resource (A140).

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

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

[0132] BWP ::= SEQUENCE {

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

[0134] subcarrierSpacing SubcarrierSpacing,

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

[0136] }

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

[0138] The locationAndBandwidth field indicates the frequency domain, location, and bandwidth of this bandwidth portion. The value of the field should be interpreted as a Resource Indicator Value (RIV). The RIV represents a consecutive set of 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, a pair of BWPs (a UL BWP and a DL BWP with the same bwp-Id) must have the same center frequency.

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

[0140] Figure 5 shows an example of a frequency domain structure.

[0141] It can be understood that the SCS-SpecificCarrier (E100) for 15KHz represents the entire frequency domain structure of the corresponding link based on the 15KHz SCS (e.g., 1 PRB = 12 N·K 15KHz), and the SCS-SpecificCarrier (E110) for 30KHz represents the entire frequency domain structure of the corresponding link based on the 30KHz SCS (e.g., 1 PRB = 12 N·K 30KHz).

[0142] The UE determines the PRB to use for transmission / reception based on the active BWP's SCS.

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

[0144] Figure 6 shows the signaling structure of SIB1 for the time resource structure of the cell.

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

[0146] The ReferenceSubcarrierSpacing field (A150) represents the subcarrier spacing, which is a reference SCS used to determine time domain boundaries in the UL-DL pattern, and must be independent of the actual subcarrier spacing used for data transmission across all subcarrier-specific carriers. This is necessary because the slot length is SCS-specific (1 ms for a 15 kHz SCS, 0.5 ms for a 30 kHz SCS, 0.25 ms for a 60 kHz SCS, etc.) and a cell can have multiple SCSs.

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

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

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

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

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

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

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

[0154] ...,

[0155] [[

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

[0157] ]]

[0158] }

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

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

[0161] 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 indicates no partial downlink slots.

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

[0163] 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).

[0164] Based on pattern 1 and pattern 2, the UE determines DL symbols, UL symbols and flexible symbols.

[0165] Slot formats include downlink symbols, uplink symbols, and flexible symbols.

[0166] If the UE is provided as tdd-UL-DL-ConfigurationCommon, the UE sets the slot-per-slot format across multiple slots as indicated by tdd-UL-DL-ConfigurationCommon.

[0167] tdd-UL-DL-ConfigurationCommon provides the following.

[0168] >: Reference SCS by referenceSubcarrierSpacing

[0169] >: pattern1.

[0170] pattern1 provides the following.

[0171] Slot setting period of P msec by dl-UL-TransmissionPeriodicity

[0172] >: Downlink symbols only by nrofDownlinkSlots d_slot multiple slots

[0173] d_sym multiple downlink symbols by nrofDownlinkSymbols

[0174] u_slots multiple slots containing only uplink symbols by nrofUplinkSlots

[0175] u_sym multiple uplink symbols by nrofUplinkSymbols

[0176] A slot configuration period of P msec includes slots S=PN·Kslot_scs. Since the reference SCS is 15 kHz, slot_scs = 1. Since the reference SCS is 30 kHz, slot_scs = 2. Since the reference SCS is 60 kHz, slot_scs = 4. Since the reference SCS is 120 kHz, slot_scs = 8. In 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 following 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.

[0177] In every 20 / P cycle, the first symbol is the first symbol of the even frame.

[0178] If tdd-UL-DL-ConfigurationCommon provides both pattern1 and pattern2, the UE sets the slot format per slot across the first number of slots as indicated by pattern1, and the UE sets the slot format per slot across the second number of slots as indicated by pattern2.

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

[0180] In short, for the frequency domain cell structure:

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

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

[0183] For time domain cell structures:

[0184] dl-UL-TransmissionPeriodicity, nrofDownlinkSlots, nrofDownlinkSymbols, nrofUplinkSlots, and nrofUplinkSymbols define the downlink symbol, flexible symbol, and uplink symbol of the cell.

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

[0187] 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 to consecutive RBs to minimize cross-link interference. This can be achieved by placing the SBFD frequency resources / locations as far away from the cell's SSB as possible (CD-SSB or NCD-SSB). This can also be achieved by isolating the SBFD frequency resources / locations from critical reference signals such as PRS or CSI-RS. Signal flexibility must be ensured to guarantee such placement. Additionally, the size of the SBFD structure is important (smaller is better) because it is conveyed to system information.

[0188] Cells may be arranged with one or more subcarrier intervals (e.g., upper is SCS x, lower is SCS y). In this case, one or more SCS-SpecificCarrier IEs are included in the system information. SBFD frequency resource information must be indicated on at least one of the one or more SCS-SpecificCarriers. The information may indicate offset and bandwidth. Since SBFD frequency resources are utilized for uplink transmission, a guard band may need to be inserted between SBFD resources and non-SBFD resources. However, because downlink reception is limited to the initial downlink BWP for idle / active UEs, this information does not need to be broadcast in the system information. Guard band information may be known to connected mode UEs via RRC signaling.

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

[0190] The BandwidthSbfd field represents the width of the SBFD subband (e.g., subband for the opposite direction) as the number of PRBs (using the subcarrierSpacing defined for this carrier). 1 PBR occupies 180KHz at 15KHz SCS, 360 at 30, 720 at 60, and 1440 at 120.

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

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

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

[0194] Since the purpose of SBFD is to allow more uplink opportunities, UL symbols are not subject to SBFD operation. The number of SBFD symbols occurs during the SBFD period. The SBFD period occurs for every SBFD cycle.

[0195] The downlink symbol is a symbol in which a downlink signal (no uplink signal, no sidelink signal) is transmitted from the entire PRB of the cell.

[0196] The uplink symbol is the following symbol.

[0197] >: Step of transmitting an uplink signal from the cell's first PRB; and

[0198] The sidelink signal is transmitted to the cell's second PRB, where the sum of the first PRB and the second PRB is the cell's total PRB.

[0199] Flexible symbols are symbols based on scheduling / configuration,:

[0200] >: Downlink signals are transmitted from the cell's entire PRB; or

[0201] The uplink signal of the 1st PRB and the sidelink signal of the 2nd PRB are transmitted.

[0202] The SBFD symbol depends on the base station's scheduling / configuration, where:

[0203] >: Downlink signals are transmitted from the cell's 3rd PRB; and

[0204] The uplink signal is transmitted from the cell's 4th PRB, where the sum of the 3rd PRB and the 4th PRB is the cell's total PRB.

[0205] E400 shows an example where the sbfd symbol is configured.

[0207] The following points may be noted.

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

[0209] >>: A single SBFD period occurs for every P1 (tdd-UL-DL-ConfigurationCommon of pattern1). SBFD periodicity = P1;

[0210] >>: The SBFD period is configured as follows.

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

[0212] >>>: As a series of downlink symbols and flexible symbols, starting from a specific downlink symbol and ending at a specific flexible symbol; or

[0213] >>>: It is a continuous, flexible symbol.

[0214] When both pattern1 and pattern2 are configured:

[0215] >>: A single SBFD period occurs every P1 + P2 (common to tdd-UL-DL-Configurationpattern2). SBFD periodicity = P1 + P2;

[0216] >>: The SBFD period starts and ends during pattern 1 or pattern 2 (the first and last SBFD symbols are within the same pattern).

[0217] >>: The SBFD period is configured as follows.

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

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

[0220] >>>: consecutive downward link symbols of pattern1 and consecutive flexible symbols of pattern1; or

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

[0222] >>>: Continuous flexible symbol of pattern1.

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

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

[0225] >: offsetToFirstSBSymobol: This field indicates the offset to the first SBFD symbol during the SBFD cycle.

[0226] >>: Includes integers. Integer (0..maxNrofSymbolsPerSbfdPeriodicity)

[0227] >>: The integer represents the number of symbols between the first symbol of the related pattern (or the first symbol of the slot configuration period) and the first symbol of the SBFD period (or the first SBFD symbol).

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

[0229] >>>: maxNrofSymbolsPerSbfdPeriodicity = SBFD Periodicity N·K SCS_symbol; SCS_symbol = 14 N·K SCS_coefficient; SCS_coefficient = 1(SCS 15KHz) or 2(SCS 30KHz) or 4(SCS 60KHz) or 8(SCS 120KHz)

[0230] >>>: SBFD Periodicity = P1 when only pattern1 is configured, P1+P2 when both pattern1 and pattern2 are configured.

[0231] >: nrOfSBSymbols: This field indicates the number of consecutive SBFD symbols during the SBFD period (or SBFD period).

[0232] >>: Includes integers. Integer (0..maxNrofSbfdSymbols)

[0233] >>: The integer represents the number of symbols within the SBFD period.

[0234] maxNrofSbfdSymbols is determined based on the slot configuration period (P1 or P2) and SCS indicated by the reference SubcarrierSpacing field.

[0235] >>>: maxNrofSbfdSymbols = slot configuration period N·K SCS_symbol;

[0236] >>>: Slot configuration period = P1 if the SBFD period is connected to pattern1, P2 if the SBFD period is connected to pattern2.

[0237] >: associatedPattern: This field indicates the pattern (connection) between pattern1 and pattern2 for the SBFD period. If this field is missing, the SBFD period is connected to pattern1.

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

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

[0240] The downlink resources are as follows.

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

[0242] >>: This is the PRB of the initial BWP of the SBFD_downlink symbol.

[0243] The uplink resources are as follows.

[0244] >>: PRB of the initial BWP of the uplink symbol; and

[0245] >>: PRB of SBFD subband of SBFD period / SBFD symbol (both SBFD_downlink symbol and SBFD_flexible symbol);

[0246] Flexible resources are as follows.

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

[0248] >>: PRB of the initial BWP of the SBFD_flexible symbol

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

[0250] The SBFD_flexible symbol is a flexible symbol based on the parameters of TDD-UL-DL-Pattern and is an SBFD symbol based on the parameters of SBFD-Pattern.

[0251] E500 represents an example of an SBFD frequency domain structure and a time domain structure.

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

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

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

[0255] System information includes the following:

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

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

[0258] >: Information on the uplink carrier for the 1st SCS;

[0259] >: Information on uplink carriers for the 2nd SCS;

[0260] >: Information on downlink carriers for the 1st SCS;

[0261] >: Information on downlink carriers for the 2nd SCS;

[0262] Information on uplink-downlink slot configuration;

[0263] In O120, the UE determines the DL symbol, UL symbol, flexible symbol, and SBFD symbol based on relevant information.

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

[0265] The downlink symbol is the following symbol.

[0266] >>: Downlink symbol according to the first parameter set for slot configuration; and

[0267] >>: Not an SBFD symbol according to the second parameter set for slot configuration;

[0268] A flexible symbol is the following symbol.

[0269] >>: Flexible symbol according to the first parameter set for slot configuration (neither downlink symbol nor uplink symbol); and

[0270] >>: Not an SBFD symbol according to the second parameter set for slot configuration;

[0271] The SBFD symbol is the following symbol.

[0272] >>: Downlink symbol according to the first parameter set for slot configuration; and SBFD symbol according to the second parameter set for slot configuration. or

[0273] >>: Flexible symbol according to a first parameter set for slot configuration; and SBFD symbol according to a second parameter set for slot configuration..

[0274] The uplink symbol is the following symbol.

[0275] >>: Uplink symbol according to the first parameter set for slot configuration.

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

[0277] Information regarding the downlink carrier for the first SCS includes a set of parameters for an SBFD frequency position specific to the first SCS. Information regarding the downlink carrier for the second SCS includes a set of parameters for an SBFD frequency position specific to the second SCS.

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

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

[0280] The UE determines SBFD PRBs specific to the first SCS based on a set of parameters for SBFD frequency positions specific to the first SCS. The UE determines SBFD PRBs specific to the second SCS based on a set of parameters for SBFD frequency positions specific to the second SCS.

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

[0282] 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.

[0283] The UE determines the PRB for the initial uplink BWP based on information regarding the initial uplink BWP and information regarding the uplink carrier for a specific SCS. The specific SCS is the SCS indicated in the information regarding the initial downlink BWP.

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

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

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

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

[0288] The initial downlink resource pool is configured as a downlink resource for the IDLE / INACTIVE UE to perform initial access (e.g., receiving RAR and monitoring PDCCH for retransmitting Msg 3 and receiving Msg 4), receiving paging, and receiving system information. The initial downlink resource is a pair of the initial downlink BWP and the PRB of the downlink-specific symbol.

[0289] The initial uplink resource pool is a configuration of uplink resources for which the IDLE / INACTIVE UE performs initial access (e.g., sending a PRACH preamble and PUSCH for message 3 and sending a HARQ ACK for message 4). The initial uplink resources are the PRB pair of the initial uplink BWP and the uplink-related symbol.

[0290] 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 and PUSCH for message 3, sending a HARQ ACK for message 4). An SBFD resource is a pair of SBFD PRBs and SBFD symbols.

[0291] The downlink-related symbol is one of the following.

[0292] >: Downlink symbol; or

[0293] >: Flexible symbols belonging to the following:

[0294] >>: This is a CORESET associated with searchSpaceSIB1 or SearchSpaceOtherSystem or ra-SearchSpace or pagingSearchSpace.

[0295] The uplink-related symbol is one of the following.

[0296] >: Uplink symbol; or

[0297] >: Flexible symbol belonging to the RACH opportunity (depending on the PRACH-configIndex of the RACH-ConfigComon for the initial uplink BWP)

[0298] The UE performs a random access procedure to the GNB based on the O160 decision.

[0299] The UE performs a preamble transfer from an initial uplink resource or an SBFD resource.

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

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

[0302] The UE receives Msg 4 for the initial downlink resource.

[0303] The UE performs random access procedures for various purposes. The waiting time or delay required to complete random access procedures affects the user experience. For example, if random access is triggered for initial access, the longer the random access delay, the longer the waiting time for the service to start. If random access is triggered for a handover, a longer random access delay results in a longer service interruption.

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

[0305] Multiple ROs are configured in a cell. It can be understood that the number of ROs per unit of time is the RO density. RO density has a significant impact on random access latency because the UE waits until the first available RO occurs. In TDD systems, ROs cannot be densified because ROs cannot be configured in downlink symbols. This limitation can be mitigated to some extent by applying SBFD to the random access procedure.

[0306] 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 time domain), it is advisable to limit preamble transmission to legacy ROs or SBFD ROs. Because legacy UEs cannot transmit preambles on SBFD ROs, the GNB must ensure that signaling related to SBFD RAs (Random Access) is placed in appropriate locations so that only SBFD UEs can decode them. Additionally, the GNB must ensure that parameters common to both SBFD RAs and SBHD (sub-band half-duplex, random access performed based on ROs on initial uplink / flexible resources) RAs are signaled only once.

[0307] Figure 13 shows a signaling structure for random access of an inactive UE.

[0308] A conventional INACTIVE UE performs random access (RA) in the initial uplink BWP (first frequency domain) and initial downlink BWP (second frequency domain). Parameters for the RA are contained in a container called RACH-ConfigCommon (IE of the RACH configuration). BWP-UplinkCommon (uplink BWP common configuration; IE) may include one or more RACH-ConfigCommons for the initial uplink BWP to support PRACH partitioning for various function combinations. This allows the GNB to know the function (or function combination) that triggers random access as soon as possible (e.g., when a preamble is received). Each RACH-ConfigCommon can be configured with RA parameters for a function combination.

[0309] One might consider defining more RACH-ConfigCommons specific to SBFD-RA. This approach complicates the signaling structure and increases signaling overhead because 1) many parameters apply commonly to SBHD RA and SBFD RA, and 2) SBFD-RA specific RACH-ConfigCommons may need to be configured for each function combination. In this disclosure, SBFD-specific RA parameters are added to extensions (not decoded by legacy UEs) in a manner that minimizes signaling overhead.

[0310] RACH-ConfigCommon consists of RACH-ConfigGeneric (for RA general configuration), featureCombinationPreamblesList, and other RA parameters. In addition, Sbfd-RACH-Config IE (IE for RA in the second frequency domain) has been added to the extended part of RACH-ConfigCommon.

[0311] RACH-ConfigCommon provides parameters for RO and preamble sets. The set of ROs associated with RACH-ConfigCommon is defined as a parameter of RACH-ConfigGeneric. Additional sets of ROs are provided by Sbfd-RACH-Config IE. The set of ROs defined by RACH-ConfigGeneric is default-RO-set. The additional set of ROs defined by Sbfd-RACH-Config IE is sbfd-RO-set. The RO of default-RO-set is default-RO. The RO of sbfd-RO-set is sbfd-RO.

[0312] RAs triggered for specific feature combinations use a specific subset of ROs determined from a specific subset of ROs and preambles. The specific subset of ROs and the specific subset of preambles are determined based on the corresponding FeatureCombinationPreambles, IEs, and other IEs.

[0313] A specific subset of ROs may include only default-RO, only sbfd-RO, or consist of default-RO(s) and sbfd-RO(s).

[0314] For FeatureCombinationPreambles in featureCombinationPreambleList:

[0315] If sbdfEnabled (A500) is configured in the corresponding FeatureCombinationPreambles, both default-RO(s) and sbfd-RO(s) can be used for RA.

[0316] If sbdfEnabled is not configured in the corresponding FeatureCombinationPreambles, only default-RO(s) can be used for RA.

[0317] For FeatureCombinationPreambles of featureCombinationPreambleList2(A900), only sbfd-RO can be used for RA.

[0318] The following describes the parameters of RACH-ConfigCommon.

[0319] >: Other RA parameters (A600)

[0320] >>: totalNumberOfRA-Preambles: The total number of preambles used for contention-based and contention-free Phase 4 or Phase 2 random access on RACH resources defined in RACH-ConfigCommon (excluding preambles used for other purposes (e.g., SI requests). If the field is empty, all 64 preambles can be used for RA. The setting must match the setting of ssb-perRACH-OccasionAndCB-PreamblesPerSSB (i.e., must be a multiple of the number of SSBs per RACH case).

[0321] >>: ssb-perRACH-OccasionAndCB-PreamblesPerSSB: This field has two meanings: CHOICE conveys information about the number of SSBs per RACH case. The value oneEighth corresponds to one SSB associated with 8 RACH cases, and the value oneFourth corresponds to one SSB associated with 4 RACH cases. The ENUMERATED part indicates the number of contention-based preambles per SSB. The value n4 corresponds to 4 contention-based preambles per SSB, and the value n8 corresponds to 8 contention-based preambles per SSB. The total number of CB preambles in a RACH situation is provided by CB-preambles-per-SSB N·K max(1, SSB-per-rach-occasion).

[0322] >>: ra-ContentionResolutionTimer: This is the initial value of the contention resolution timer.

[0323] >>: msg1-SubcarrierSpacing: PRACH's subcarrier spacing for the underlying RO

[0324] >>: FeatureCombinationPreambles: IE FeatureCombinationPreambles links a set of preambles with feature combinations.

[0325] >>: msg3-transformPrecoder: Enables the transform precoder for Msg3 transmission. If no field is present, the UE disables the transformer precoder.

[0326] >>: groupBconfigured: This is the parameter set for group B-based random access.

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

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

[0329] RACH-ConfigGeneric (A700)

[0330] >>: prach-ConfigurationIndex: PRACH configuration index.

[0331] >>: msg1-FDM: This is the number of PRACH transmissions FDMed in a single case.

[0332] >>: msg1-FrequencyStart: Offset of the lowest PRACH transmission situation in the frequency domain corresponding to PRB 0. This value is configured so that the corresponding RACH resource is entirely within the bandwidth of the UL BWP.

[0333] >>: preambleReceivedTargetPower: This is the target power level on the network receiver side.

[0334] >>: preambleTransMax: Maximum number of RA preamble transmissions performed before declaring failure

[0335] >>: powerRampingStep: PRACH's power ramping step

[0336] >>: ra-ResponseWindow: Msg2(RAR) is the window length (number of slots).

[0338] >: FeatureCombinationPreambles

[0339] >>: DeltaPreamble: Power offset between msg3 or msgA-PUSCH and RACH preamble transmissions. If configured, this parameter overrides msg3-DeltaPreamble or msgA-DeltaPreamble.

[0340] featureCombination represents a combination of features linked by preambles indicated by this IE. The UE ignores the RACH resources defined by this FeatureCombinationPreambles if any feature within the featureCombination is not supported by the UE, or if any of the reserve fields within the featureCombination are set to true.

[0341] >>: numberOfPreamblesPerSSB-ForThisPartition: Determines the number of consecutive preambles connected to the Feature Combination, starting from the starting preamble per SSB.

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

[0343] >>: startPreambleForThisPartition: Defines the first preamble associated with the function combination.

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

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

[0346] >>: groupBconfigured: This is the parameter set for group B-based random access.

[0347] >: Sbfd-Config (A800)

[0348] >>: prach-ConfigurationIndex-sbfd: PRACH configuration index for SBFD RA. If not present, the relevant parameters of RACH-ConfigGeneric are applied.

[0349] >>: msg1-FDM-sbfd: The number of FDMed PRACH transmissions at once for SBFD RA. If none, the relevant parameter of RACH-ConfigGeneric is applied.

[0350] >>: msg1-FrequencyStart-sbfd: Offset of the lowest PRACH transmission situation in the frequency domain corresponding to PRB 0 of the SBFD. The value is configured so that the corresponding RACH resource is entirely within the bandwidth of the SBFD subband.

[0351] >>: preambleReceivedTargetPower-sbfd: Target power level on the network receiver side; if none, the value of RACH-ConfigGenric is applied.

[0352] >>: preambleTransMax-sbfd: The maximum number of RA preamble transfers performed before declaring failure for SBFD RA. If none, the value of RACH-ConfigGenric is applied.

[0353] >>: powerRampingStep-sbfd: Power ramping step of PRACH. If not present, the value of RACH-ConfigGenric is applied.

[0354] >>: ra-ResponseWindow-sbfd: Msg2(RAR) Number of slots (window length) (determined by the SCS of the initial DL BWP). If none, the value of RACH-ConfigGenric is applied.

[0355] >>: ssb-perRACH-OccasionAndCB-PreamblesPerSSB-sbfd: SBFD Indicates the number of SSBs per RACH instance and the number of contention-based preambles per SSB. If none, ssb-perRACH-OccasionAndCB-PreamblesPerSSB applies.

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

[0357] >>: groupBconfigured-sbfd: Parameter set for group B-based random access for SBFD RA. If this field is missing, groupBconfigured-sbfd applies.

[0358] >>: 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 prach-RootSequenceIndex-r16 is present in RACH-ConfigCommon, prach-RootSequenceIndex-r16 applies. If this field is missing and prach-RootSequenceIndex-r16 is missing and prach-RootSequenceIndex is present, prach-RootSequenceIndex applies.

[0360] Figure 14 shows examples of default-RO and sbfd-RO.

[0361] E600 shows examples of default-RO and sbfd-RO in the following configurations.

[0362] prach-ConfigurationIndex indicates that default-RO occurs in subframes 5 and 9 of all radio frames.

[0363] >: msg1-FDM indicates that two basic ROs were configured simultaneously.

[0364] msg1-FrequecyStart indicates that the first basic RO is configured in PRB1 of the initial BWP.

[0365] >: prach-ConfigurationIndex-sbfd indicates that sbfd-RO occurs in subframe 2 and subframe 4 of all radio frames.

[0366] >: msg1-FDM-sbfd indicates that two sbfd-RO instances are configured simultaneously.

[0367] >: msg1-FrequecyStart-sbfd indicates that the first sbfd-RO is configured on PRB1 of the SBFD resource.

[0368] sbfd-RO that overlaps with SSB symbols is considered invalid.

[0369] An INACTIVE UE capable of SBFD based on existing signaling and new signaling performs a random access procedure.

[0370] Figure 15 illustrates a random access procedure.

[0371] In O150-05, the UE triggers an RA. An RA can be triggered for function combinations or PDCCH orders, handovers, or mobility management.

[0372] In O150-10, the UE determines the uplink between SUL and NUL. This step may be skipped if the serving cell is not configured as an auxiliary uplink. If the RSRP of the downlink path loss reference is less than 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 rsrp-ThresholdSSB-SUL, the UE selects the NUL carrier to perform the random access procedure.

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

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

[0375] The UE determines whether Msg1 repetition is applicable and the number of repetitions (if applicable) based on rsrp-ThresholdMsg1-RepetitionNum8, rsrp-ThresholdMsg1-RepetitionNum4, rsrp-ThresholdMsg1-RepetitionNum2, and other related parameters.

[0376] The UE selects a set of Random Access resources based on the availability of the feature.

[0377] The UE selects a frequency domain based on the set of random access resources selected for this random access procedure.

[0378] To determine whether the UE can apply the Msg3 iteration, the UE is as follows.

[0379] >: If the BWP selected for the random access procedure (in the case of IE for RACH configuration of the initial uplink BWP) consists of a random access resource set with msg3-Repeats set to true and a random access resource set with msg3-Repeats set to true, and the RSRP of the downlink path loss reference is less than rsrp-ThresholdMsg3; or

[0380] >: If the BWP selected for the random access procedure (in the case of IE for the RACH configuration of the initial uplink BWP) consists only of a set of random access resources with msg3-Repeats set to true:

[0381] >>: Msg3 Iteration is considered applicable to the current random access procedure.

[0382] Others:

[0383] >>: Msg3 Iteration is considered not to apply to the current random access procedure.

[0384] To determine whether the UE is eligible for Msg1 iteration and, if so, the number of iterations, the UE is as follows.

[0385] If contention-free Random Access Resources are provided for this Random Access procedure and the Msg1 iteration number is displayed in rach-ConfigDedicated:

[0386] >>: The number of Msg1 iterations applicable to the current random access procedure is the number of Msg1 iterations displayed in rach-ConfigDedicated.

[0387] Otherwise, if no contention-free random access resource was provided for this random access procedure, and the BWP selected for the random access procedure (and IE for RACH configuration of the initial uplink BWP) is configured with a set of random access resources where msg1-Repeats is set to true and a set of random access resources where msg1-Repeats is not set to true:

[0388] >>: For the random access procedure (in the case of IE for the RACH configuration of the initial uplink BWP), if the selected BWP is configured with a random access resource set associated with Msg1 repetition number 8 and the RSRP of the downlink path loss reference is less than rsrp-ThresholdMsg1-RepetitionNum8:

[0389] Assume that Msg1 iterations are applied and that the number of Msg1 iterations applicable to the current random access procedure includes 8.

[0390] >>: If the BWP selected for the random access procedure (in the case of IE for RACH configuration of the initial uplink BWP) is configured with a random access resource set associated with Msg1 repetition number 4 and the RSRP of the downlink path loss reference is less than rsrp-ThresholdMsg1-RepetitionNum4:

[0391] >>>: Assume that Msg1 iterations are applied and that the number of Msg1 iterations applicable to the current random access procedure includes 4.

[0392] >>: For the random access procedure (in the case of IE for the RACH configuration of the initial uplink BWP), if the selected BWP is configured with a random access resource set associated with Msg1 repetition number 2 and the RSRP of the downlink path loss reference is less than rsrp-ThresholdMsg1-RepetitionNum2:

[0393] Assume that Msg1 iterations are applied and that the number of Msg1 iterations applicable to the current random access procedure includes 2.

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

[0395] >>>: Msg1 Iteration is considered not to apply to the current random access procedure.

[0396] Otherwise, if the BWP selected for the random access procedure consists only of random access resources with msg1-Repetitions set to true (otherwise in the case of IE for the RACH configuration of the initial uplink BWP):

[0397] >>: Assume that Msg1 iteration is applied to the current random access procedure.

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

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

[0400] >>>>: The number of Msg1 iterations applicable to the current random access procedure includes 8.

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

[0402] >>>>: Assume that the number of Msg1 iterations applicable to the current random access procedure includes 4.

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

[0404] >>>>: It is assumed that the number of Msg1 iterations applicable to the current random access procedure includes 2.

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

[0406] >>>>: 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.

[0407] >>: else(rsrp-ThresholdMsg1-RepetitionNumX is not configured):

[0408] >>>: The Msg1 iteration number applicable to the current random access procedure is the Msg1 iteration number configured for this BWP.

[0409] To select a set of random access resources based on the availability of the feature, the UE:

[0410] >: For this random access procedure, no contention-free random access resources and random access resources for SI requests were provided, and (e) if one or more functions, including RedCap and / or slicing and / or SDT and / or MSG3 iterations and / or MSG1 iterations, apply to this random access procedure:

[0411] >>: If there is no set of Random Access resources available for the features applicable to the current Random Access procedure:

[0412] >>>: Select a set of Random Access resources not associated with the feature display for this Random Access procedure.

[0413] >>: Otherwise, if there is a set of Random Access resources that can be used to represent all functions triggering this Random Access procedure:

[0414] >>>: Select this set of Random Access resources for this Random Access procedure.

[0415] >>: Otherwise, if there are two or more available sets of Random Access resources that can be used to display all functions triggering this Random Access procedure, and Msg1 iteration applies to this Random Access procedure:

[0416] >>>: Select the Random Access resource set associated with the highest number of iterations from the Random Access resource sets.

[0417] >>: else (i.e., there is one or more sets of Random Access resources configured as indications for a subset of all functions that trigger this Random Access procedure):

[0418] >>>: Select a set of Random Access resources from the set of available Random Access resources according to the priority represented by the upper layer, as specified in Section 5.1.1d of this Random Access Procedure.

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

[0420] >>: Selects the set of random access resources composed only of RedCap marks and Msg1 repeat marks, and associated with the Msg1 repeat number displayed for this random access procedure.

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

[0422] >>: Selects the set of random access resources composed only of eRedCap marks and Msg1 repeat marks, and associated with the Msg1 repeat number displayed for this random access procedure.

[0423] Otherwise, if a contention-free random access resource has been provided for this random access procedure and RedCap is applicable to the current random access procedure, and a single set of random access resources consisting solely of RedCap marks is available; or

[0424] >: If a contention-free random access resource is provided for this random access procedure and eRedCap is applied to the current random access procedure, and a single set of random access resources consisting only of eRedCap indications is available; or

[0425] If a contention-free Random Access resource has been provided for this Random Access procedure, eRedCap is applicable to the current Random Access procedure, there is no set of available Random Access resources consisting only of eRedCap markings, and there is a single set of Random Access resources consisting only of RedCap markings:

[0426] >>: Select this set of Random Access resources for this Random Access procedure.

[0427] Besides:

[0428] >>: If the random access procedure is initiated by a PDCCH sequence in which the DCI PRACH connection indicator field is set to 1 and SSB-MTC-AdditionalPCI is configured by the upper layer:

[0429] >>>: Select the set of Random Access resources corresponding to the active additionalPCI.

[0430] >>: Otherwise, if the random access procedure is initiated by the PDCCH sequence for LTM candidate cells:

[0431] >>>: Select the set of Random Access resources corresponding to the Cell indicator field in PDCCH order.

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

[0433] >>>: Selects the set of Random Access resources associated with the Msg1 iteration number displayed for this Random Access procedure, consisting only of Msg1 iteration marks.

[0434] >>: Otherwise, if a random access procedure is initiated for an SI request and a random access resource associated with the Msg1 iteration and the number of Msg1 iterations for the SI request is provided for this random access procedure:

[0435] >>>: Selects the set of Random Access resources associated with the Msg1 iteration number displayed for this Random Access procedure, consisting only of Msg1 iteration marks.

[0436] >>: else:

[0437] >>>: Select a set of Random Access resources not associated with the feature display for the current Random Access procedure.

[0438] UE to determine whether the UE can use a set of random access resources:

[0439] >: When eRedCap is set to true for a random access resource set:

[0440] Sets of random access resources that cannot be used in random access procedures to which eRedCap does not apply are considered unavailable.

[0441] If redCap is set to true for a random access resource set configured for a 4-stage RA type, but is set for a 2-stage RA type:

[0442] >>: Sets of random access resources that cannot be used by random access procedures to which RedCap does not apply are considered unavailable.

[0443] If set to true for a random access resource set configured for a 2-stage RA type, regardless of whether redCap is configured for a 4-stage RA type:

[0444] >>: (e) A set of Random Access resources that cannot be used in Random Access procedures to which RedCap does not apply is considered unavailable.

[0445] >>: In the following procedures of Sections 5.1.1c and 5.1.1d, eRedCap is considered as eRedCap and RedCap.

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

[0447] >>: Consider a set of random access resources that cannot be used for random access procedures that are not triggered for RA-SDT by MO-SDT.

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

[0449] >>: A set of Random Access resources is considered unavailable for Random Access procedures unless triggered by one of the NSAG-IDs in the NSAG-List.

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

[0451] >>: Msg3 If iteration is not applied, consider the Random Access resource set as unavailable for use in the Random Access procedure.

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

[0453] >>: Msg1 If the iteration does not apply to the current random access procedure; or

[0454] >>: If the Random Access resource set is not associated with the number of Msg1 iterations applicable to the current Random Access procedure:

[0455] >>>: Considers the Random Access resource set as unavailable for use in Random Access procedures.

[0456] >: If the random access resource set is not configured as a FeatureCombination:

[0457] >>: The random access resource set is considered not to be associated with any function.

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

[0459] Figure 16 illustrates an example.

[0460] Each square represents an RO. When RACH-ConfigCommon configures three featureCombiantionPreambles, an RO related to feature combination occurs, as in the E700.

[0461] >: In the following cases:

[0462] A specific RACH-ConfigCommon is associated with additional ROs (e.g., sbfd-RACH-Config is configured). And

[0463] A specific featureCombinationPreamble can use both the default RO and additional RO (e.g., sbfdEnabled is configured).

[0464] Both the additional RO and the basic RO can be used for the random access resource set (available for the random access procedure in which the random access resource set is selected). FC1 in the drawing corresponds to this case.

[0465] >: In the following cases:

[0466] A specific RACH-ConfigCommon is associated with additional ROs (e.g., sbfd-RACH-Config is configured). And

[0467] Certain featureCombinationPreambles cannot use additional ROs (e.g., sbfdEnabled is not configured).

[0468] Only default-RO can be used for random access resource sets (available for random access procedures where the random access resource set is selected). FC2 in the drawing corresponds to this case.

[0469] >: In the following cases:

[0470] A specific RACH-ConfigCommon is associated with additional ROs (e.g., sbfd-RACH-Config is configured). And

[0471] Specific featureCombinationPreambles cannot use the default RO (or can only use additional ROs) (e.g., featureCombinationPreambles in the new list).

[0472] Only additional ROs can be used for a random access resource set (available for use in random access procedures where the random access resource set is selected). FC3 in the drawing corresponds to this case.

[0473] If both default-ROs and additional-ROs are available in a random access procedure, the UE determines one of them for preamble transmission.

[0474] >: In the following cases:

[0475] >>: The associated feature combination (if selected, if a set of random access resources is associated) repeat Msg1; and

[0476] >>: Msg1 repetition is allowed in the RA region (e.g., specific new markers are configured in the corresponding featureCombinationPreambles).

[0477] The UE performs preamble transmission in both the default-RA-region and the additional-RA-region.

[0478] >: In the following cases:

[0479] >>: Related function combinations do not include Msg1 repetition. Or

[0480] >>: Repetition of Msg1 is not allowed in the RA region.

[0481] The UE selects either the default-RA-region or 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.

[0483] In S150-20, the UE transmits Msg1 / Preamble at a specific RO of the determined RA-region.

[0484] To determine a specific RO, the UE can do the following.

[0485] For SSB selection:

[0486] If one or more of the SSBs with an SS-RSRP greater than or equal to rsrp-ThresholdSSB are available:

[0487] >>: Select the SSB with SS-RSRP on top of rsrp-ThresholdSSB.

[0488] Others:

[0489] >>: Select SSB.

[0490] For preamble group selection:

[0491] If Random Access Preambles Group B is configured:

[0492] >>: If the potential Msg3 size (UL data and MAC subheader available for transmission and MAC CE if necessary) is greater than ra-Msg3SizeGroupA and the path loss is less than PCMAX (of the serving cell performing the random access procedure) - preambleReceivedTargetPower - msg3-DeltaPreamble - messagePowerOffsetGroupB; or

[0493] >>: If a random access procedure is initiated for the CCCH logical channel and the CCCH SDU size and MAC subheader are greater than ra-Msg3SizeGroupA:

[0494] >>>: Select Random Access Preambles group B.

[0495] >>: Others:

[0496] >>>: Select Random Access Preambles group A.

[0497] Others:

[0498] >>: Select Random Access Preambles group A.

[0499] In the case of RO decisions:

[0500] >: If a random access resource set associated with the Msg1 iteration is selected for this random access procedure:

[0501] >>: Determine the next available set of PRACH opportunities (as specified in TS 38.213[6]) for the Msg1 iteration number applicable to this random access procedure corresponding to the selected SSB, and is allowed by the restrictions provided by ra-ssb-OccasionMaskIndex (if configured) or ssb-SharedRO-MaskIndex (if configured). The set of PRACH situations may consist only of a default RO (if default-RA-region is selected) or an additional RO (if additional-RA-region is selected) or a default RO and an additional RO (or iterations between RA regions are allowed).

[0502] else:

[0503] >>: Determines the next available PRACH opportunity from the PRACH case corresponding to the selected SSB, which is allowed by the restrictions given by ra-ssb-OccasionMaskIndex or ssb-SharedRO-MaskIndex, indicated by PDCCH, or directed by the LTM cell switch command MAC CE. If the initial transfer is performed on the primary RO, the PRACH case for retransmission is the primary RO. If the initial transfer is performed on the additional RO, the retransmission time for PRACH is the additional RO.

[0504] In O150-25, the UE starts the RA window and monitors the PDCCH to receive RAR.

[0505] After the PRACH / preamble transmission, the UE attempts to detect DCI format 1_0 with the CRC scrambled by the corresponding RA-RNTI during the RAR window.

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

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

[0508] >: Preamble transmission for a resource in the first frequency domain (initial uplink BWP of NUL) or a resource in the fourth frequency domain (initial uplink BWP of SUL); and

[0509] >: Receive RAR from a third frequency domain resource (initial downlink BWP).

[0510] In the FDD system,

[0511] The first frequency range is determined based on the following.

[0512] >>: 1st reference resource block (PointA for the normal uplink of the serving cell; determined based on the absoluteFrequencyPointA field within FrequencyInfoUL-SIB IE within the uplink configuration common field);

[0513] >>: Offset from the first reference resource block to the general uplink carrier (determined based on the offsetToCarrier field within a specific SCS-SpecificCarrier within the FrequencyInfoUL-SIB IE within the uplink conficommon field); and

[0514] >>: Location and bandwidth of the first frequency domain (determined by the locationAndBandwidth field within the initialUplinkBWP field within the uplinkConfigCommon field).

[0515] The fourth frequency range is determined based on the following.

[0516] >>: 2nd reference resource block (PointA for the supplementary uplink of the serving cell; determined based on the absoluteFrequencyPointA field in the FrequencyInfoUL-SIB within the auxiliary uplink);

[0517] >>: Offset from the second reference resource block to the auxiliary uplink carrier (determined based on the offsetToCarrier field within a specific SCS-SpecificCarrier within the FrequencyInfoUL-SIB IE within the auxiliary uplink field); and

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

[0519] The third frequency domain is determined based on the following.

[0520] >>: 3rd reference block (PointA for the downlink of the serving cell; determined based on the offsetToPointA field; within the downlinkConfigCommon field in FrequencyInfoDL-SIB IE);

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

[0522] >>: Location and bandwidth of the third frequency domain (determined based on the locationAndBandwidth field within the initialDownlinkBWP field within the downlinkConfigCommon field).

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

[0524] >: Send preamble for the next resource:

[0525] >>: 1st frequency domain (initial uplink BWP of NUL);

[0526] >>: 4th frequency domain (SUL's initial uplink BWP); or

[0527] >>: Second frequency domain (SBFD of NUL);

[0528] >: Receive RAR from a third frequency domain resource (initial downlink BWP).

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

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

[0531] >>: Offset from the first reference resource block to the general uplink carrier (determined based on the offsetToCarrier field within a specific SCS-SpecificCarrier within the FrequencyInfoUL-SIB IE within the uplink conficommon field); and

[0532] >>: Location and bandwidth of the first frequency domain (determined by the locationAndBandwidth field within the initialUplinkBWP field within the uplinkConfigCommon field).

[0533] The fourth frequency range is determined based on the following.

[0534] >>: 2nd reference resource block (PointA for the supplementary uplink of the serving cell; determined based on the absoluteFrequencyPointA field in the FrequencyInfoUL-SIB within the auxiliary uplink);

[0535] >>: Offset from the second reference resource block to the auxiliary uplink carrier (determined based on the offsetToCarrier field within a specific SCS-SpecificCarrier within the FrequencyInfoUL-SIB IE within the auxiliary uplink field); and

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

[0537] The third frequency domain is determined based on the following.

[0538] >>: 1st reference block (Point A for the downlink of the serving cell; determined based on the offsetToPointA field in FrequencyInfoDL-SIB IE within the downlink conficonfidation common field);

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

[0540] >>: Location and bandwidth of the third frequency domain (determined based on the locationAndBandwidth field within the initialDownlinkBWP field within the downlinkConfigCommon field).

[0541] The second frequency range is determined based on the following.

[0542] >>: Offset from the first reference resource block to the general uplink carrier (determined based on the offsetToCarrier field within a specific SCS-SpecificCarrier within the FrequencyInfoUL-SIB IE within the uplink configuration common field); and

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

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

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

[0546] The UE receives Msg2 / RAR S150-30.

[0547] The UE performs a PUSCH transmission for Msg 3 S150-35.

[0548] The UE receives Msg4 for contention resolution S150-40.

[0549] The UE sends a HARQ ACK for Msg4 S150-45.

[0550] 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.

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

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

[0553] 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.

[0554] The UE performs the following for sending a preamble and receiving a response.

[0555] The UE receives the SSB from the cell.

[0556] The UE receives system information from the cell.

[0557] The UE triggers random access in the cell.

[0558] The UE sends a preamble to the cell for random access. And

[0559] The UE receives a response to the preamble within the cell, and

[0560] The preamble is transmitted from the first frequency resource [a resource in the initial uplink BWP of NUL] or the second frequency resource [SBFD] or the fourth frequency resource [a resource in the initial UL BWP of SUL].

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

[0562] In what respects:

[0563] The first frequency resource belongs to the first frequency range [initial UL BWP of NUL].

[0564] The second frequency resource belongs to the second frequency range [SBFD];

[0565] The third frequency resource belongs to the third frequency range [initial DL BWP];

[0566] The fourth frequency resource belongs to the fourth frequency range [SUL's initial UL BWP], and

[0567] In what respects:

[0568] The first frequency range, the second frequency range, and the fourth frequency range are for uplink transmission;

[0569] The above third frequency range is for downlink reception, and

[0570] If the RSRP of the downlink path loss reference is smaller than a specific threshold [rsrp-ThresholdSSB-SUL], the UE transmits a preamble on the fourth frequency resource, and

[0571] The UE transmits a preamble from the first frequency resource in the following cases.

[0572] The RSRP of the downlink path loss criterion (downlink reference signal such as SSB) is greater than or equal to a specific threshold; and

[0573] The set of parameters for the second frequency domain above is not composed of a set of parameters for downlink configuration, and

[0574] The above UE transmits a preamble from the above second frequency resource in the following cases:

[0575] The RSRP of the downlink path loss reference is greater than or equal to a specific threshold. And

[0576] The parameter set for the second frequency domain is not configured as a parameter set for downlink configuration.

[0578] The UE performs the following tasks to transmit a preamble and receive a response.

[0579] The UE receives system information, wherein the system information consists of various information elements (IE);

[0580] The UE triggers the RA (Random Access) procedure.

[0581] The UE determines the set of RA resources based on the availability of one or more functions. And

[0582] The UE performs RA procedures based on a set of RA resources, and

[0583] If the above set of RA resources includes system information, it includes a first set of ROs and a second set of ROs, and

[0584] >: Parameter for the offset for the second frequency domain [OffsetToSbfd] within IE for downlink configuration; and

[0585] IE for RA in the second frequency range [sbfd-RACH-Config] within the IE for uplink configuration,

[0586] The first RO set is determined based on the following.

[0587] >: First frequency range;

[0588] >: First region;

[0589] >: Parameters for the start frequency [msg1-frequencyStart] within IE for the RA general configuration [RACH-ConfigGeneric]; and

[0590] >: Parameters for FDD (Frequency Division Multiplexing) [FDMed] within IE for RA general configuration; and

[0591] The second RO set is determined based on the following.

[0592] >: Second frequency range;

[0593] >: Second time domain;

[0594] >: Parameter for the starting frequency within IE for RA in the second frequency domain; and

[0595] >: Parameters for FDD in IE for RA in the second frequency domain;

[0596] The first frequency range is determined based on the following.

[0597] >: IE for the first frequency range within the IE for uplink configuration; and

[0598] >: Parameter for the offset for the uplink carrier within IE for uplink configuration; and

[0599] >: Parameter for the offset to reference the resource block within IE for downlink configuration; and.

[0600] The second frequency range is determined based on the following.

[0601] >: Parameter for offset to the second frequency domain within IE for downlink configuration;

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

[0603] >: Parameter for the offset for the downlink carrier within IE for downlink configuration; and

[0604] >: Parameter for the offset to reference the resource block within IE for downlink configuration; and

[0605] The first region is determined based on the following criteria.

[0606] >: This is a parameter for the prach configuration index within IE for general RA configuration. And

[0607] >: one or more first symbols; and

[0608] The second time domain is determined based on the following.

[0609] >: Parameter for the prach configuration index within IE for the RA in the second frequency domain; and

[0610] >: One or more second symbols,

[0611] One or more first symbols include the following.

[0612] >: tdd One or more downlink symbols determined based on IE for uplink downlink configuration; and

[0613] >: tdd One or more flexible symbols determined based on IE for uplink and downlink configuration,

[0614] The second symbol is the following symbol.

[0615] >: Determined based on the parameter for the sub-band time domain [offsetToFirstSBSymobol] within IE for tdd uplink downlink configuration;

[0616] >: The first symbol is A. (To ensure that the first time domain takes precedence in the event of a conflict between the first and second time domains).

[0617] System information is configured as follows.

[0618] >: Parameter set for downlink configuration;

[0619] This is a set of parameters for uplink configuration.

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

[0621] As a parameter set for configuring TDD uplinks and downlinks,

[0622] Parameter set and IE are used interchangeably.

[0623] The parameter set for the downlink configuration [DownlinkConfigCommonSIB] is configured as follows.

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

[0625] >: Parameter for the offset to reference resource block [offsetToPointA];

[0626] >: One or more downlink carrier-specific parameter sets;

[0627] The parameter set for the uplink configuration [UpinkConfigCommonSIB] is configured as follows.

[0628] >: Parameter set for the first frequency region [initial uplink bandwidth parts];

[0629] >: One or more uplink carrier-specific parameter sets,

[0630] The set of parameters for auxiliary uplink configuration is configured as follows.

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

[0632] >: Parameter [absoluteFrequencyPointA] for the referenced resource block; and

[0633] >: One or more uplink carrier-specific parameter sets;

[0634] Each of one or more sets of downlink carrier specific parameters includes the following: The one or more sets of downlink carrier specific parameters are,

[0635] >: Parameter for offset for downlink carrier;

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

[0637] >: Parameters for downlink carrier bandwidth

[0638] Each of one or more uplink carrier-specific parameter sets includes the following.

[0639] >: Parameter for offset for uplink carrier;

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

[0641] >: This is a parameter for the uplink carrier bandwidth.

[0643] The parameter set for the third frequency domain [initial DL BWP] includes the following.

[0644] >: Parameters indicating the position and bandwidth of the third frequency domain; and

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

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

[0647] >: Parameter set for the third frequency domain;

[0648] >: This is a parameter for the offset to the referenced resource block. And

[0649] A specific set of downlink carrier specific parameters, and

[0650] The following are identical.

[0651] >: Subcarrier interval determined by a specific set of downlink carrier specific parameters; and

[0652] >: Subcarrier interval indicated by a parameter set for the third frequency domain.

[0653] The first frequency range [the initial uplink bandwidth portion of the NUL] is determined based on the following.

[0654] >: Parameter set for the first frequency domain;

[0655] >: This is a parameter for the offset to the referenced resource block. And

[0656] A specific set of uplink carrier-specific parameters within the parameter set for uplink configuration, and

[0657] The following are identical.

[0658] >: Subcarrier interval indicated by a specific set of uplink carrier specific parameters within a parameter set for uplink configuration; and

[0659] >: Subcarrier interval indicated by the parameter set for the first frequency domain.

[0660] The fourth frequency region [the initial uplink bandwidth portion of SUL] is determined based on the following.

[0661] >: Parameter set for the 4th frequency domain [BWP];

[0662] >: This is a parameter for the referenced resource block. And

[0663] A specific uplink carrier-specific parameter set within the parameter set for supplemental uplink configuration, and

[0664] The following are identical.

[0665] >: Subcarrier intervals dictated by a specific set of uplink carrier-specific parameters within a parameter set for supplementary uplink settings; and

[0666] >: Subcarrier intervals indicated by a parameter set for the fourth frequency domain

[0667] The second frequency domain [SBFD frequency domain] is determined based on the following.

[0668] >: This is a parameter for the offset to the referenced resource block.

[0669] >: Parameter for offset for downlink carrier;

[0670] >: Parameter for offset for the second frequency domain; and

[0671] >: Parameters for the bandwidth of the second frequency domain, and

[0672] The above second frequency range includes n consecutive PRBs starting from a specific PRB;

[0673] A specific PRB is determined based on the following criteria.

[0674] >: Parameter for offset to the second frequency domain; And

[0675] >: offset to reference is a parameter for the resource block.

[0676] n is determined based on parameters for the bandwidth of the second frequency domain.

[0677] The following consists of a specific set of parameters per downlink carrier.

[0678] >: Parameter for offset for the second frequency domain;

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

[0680] >: Parameter for offset for downlink carrier,

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

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

[0683] Within a specific set of downlink carrier specific parameters, parameters for the offset for the downlink carrier are generally used to determine the downlink carrier and the second frequency region.

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

[0686] System information is configured as follows.

[0687] IE for downlink configuration;

[0688] >: IE for uplink configuration; and

[0689] >: This is IE for configuring tdd uplinks and downlinks.

[0690] IE for downlink configuration is configured as follows.

[0691] >: IE for the third frequency range [initial DL BWP];

[0692] >: This is a parameter for the offset to reference the resource block [offsetToPointA].

[0693] >: Parameter for offset to downlink carrier [offsetToCarrier]; A parameter to offset to downlink carrier [offsetToCarrier], and And

[0694] >: Parameters for offset for the second frequency domain

[0695] IE for uplink configuration is configured as follows.

[0696] >: IE for the first frequency range [initial UL BWP]; and

[0697] >: Parameter for offset for uplink carrier,

[0698] The IE for the first frequency range includes the following.

[0699] >: Parameters for SCS. And

[0700] One or more IE for RACH (Random Access Channel) configuration;

[0701] Each IE for the RACH configuration [RACH-ConfigCommon] is configured as follows.

[0702] >: IE for RA general configuration;

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

[0704] One or more IE for the feature combination preface,

[0705] IE for the general RA configuration is configured as follows.

[0706] >: Parameters for frequency start; and

[0707] Parameters for the prach configuration index,

[0708] The IE for RA in the second frequency domain includes the following.

[0709] >: Parameters for frequency start; and

[0710] Parameters for the prach configuration index,

[0711] The parameter for frequency start in IE for RA general configuration represents the number of PRBs of SCS indicated as the parameter for SCS in IE for the first frequency range.

[0712] The parameter for the frequency start in IE for RA in the second frequency domain represents the number of PRBs in the SCS of the fourth frequency domain.

[0713] The first RO of the second RO set is located at a specific frequency point [FDM-enhanced first LO].

[0714] A specific frequency point is located upward from the first reference point [the lowest PRB of SBFD] by an amount indicated by the parameter for the starting frequency in IE for RA in the second frequency domain.

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

[0716] The second reference point is located upward from the third reference point [PointA] by an amount indicated by the parameter for the offset for the downlink carrier [offsetToCarrier] within the IE for downlink configuration.

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

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

[0719] When sets of RA resources are configured in both the first frequency domain and the second frequency domain, the base station requires an average 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 first frequency domain. SBFD UEs can perform RA procedures in the second frequency domain by default. For finer control, new parameters may be considered. The new parameters indicate whether the SBFD UE can perform RA procedures (even if RA procedures are possible in the second RA domain) and the probability of selecting the first frequency domain.

[0720] The UE performs the following to select an RA resource set.

[0721] The UE receives system information, wherein the system information consists of various information elements (IE);

[0722] The UE triggers the RA (Random Access) procedure.

[0723] The UE determines a first set of functions applicable to the RA procedure.

[0724] The UE determines the set of RA resources based on the availability of a third set of functions; and

[0725] The UE performs RA procedures based on a set of RA resources, and

[0726] If an RA resource set is not available for all functions applicable to the RA procedure (second function set), an RA resource set not associated with any function is selected.

[0727] Based on a specific parameter [SbfdSelectiona], the UE determines that a specific set of RA resources not associated with any feature is selected based on the parameter for the following cases.

[0728] There is no set of available RA resources for the functions applicable to the RA procedure. And

[0729] A set of RA resources not associated with any function is available in the first frequency domain; and

[0730] A set of RA resources not connected to any function can be used in the second frequency domain.

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

[0732] The second set of functions consists of one or more NSAG-IDs determined by the upper layer to be applicable to RA.

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

[0734] The UE determines that the msg3-Repetition function is as follows.

[0735] The RA procedure applies in the following cases.

[0736] One or more sets of RA resources with msg3-Repeat set to true are available for the first frequency domain or the second frequency domain. And

[0737] >>: The RSRP of the downlink path loss reference is less than rsrp-ThresholdMsg3.

[0738] The RA procedure does not apply in the following cases.

[0739] One or more sets of RA resources with msg3-Repeat set to true are available for the first frequency domain or the second frequency domain. And

[0740] >>: The RSRP of the downlink path loss reference is greater than rsrp-ThresholdMsg3. And

[0741] The RA procedure does not apply in the following cases.

[0742] >>: A set of RA resources with msg3-Repetition set to true cannot be used for both the first frequency domain and the second frequency domain.

[0743] The UE determines that the msg1-Repetition function is as follows.

[0744] The RA procedure applies in the following cases.

[0745] All sets of RA resources for the first frequency domain are configured so that msg1-Repetitions is set to true;

[0746] All RA resource sets for the second frequency domain are configured so that msg1-Repeats is set to true.

[0747] The RA procedure does not apply in the following cases.

[0748] >>: None of the sets of RA resources for the first frequency region are configured to set msg1-Repetitions to true; and any sets of RA resources for the first frequency region for the first frequency region for the first frequency resources sets of the first frequency region for the message 1-Repetitions set to true; and And

[0749] None of the RA resource sets for the second frequency domain are configured with msg1-Repetitions set to true.

[0750] The RA procedure applies in the following cases.

[0751] >>: One or more RA resource sets for the first frequency domain are configured so that msg1-Repetitions is set to true, or one or more RA resource sets for the second frequency domain are configured so that msg1-Repetitions is set to true;

[0752] >>: The RSRP of the downlink path loss reference is less than at least one of rsrp-ThresholdMsg1-RepetitionNumX;

[0753] The RA procedure does not apply in the following cases.

[0754] >>: One or more RA resource sets for the first frequency domain are configured so that msg1-Repetitions is set to true, or one or more RA resource sets for the second frequency domain are configured so that msg1-Repetitions is set to true;

[0755] >>: The RSRP of the downlink path loss reference is greater than all rsrp-ThresholdMsg1-RepetitionNumX.

[0756] >: SbfdSelection:

[0757] >>: Indicates the probability that the UE selects a set of RA resources for a specific set of features when a set of RA resources indicating the same set of features is available in both the first frequency domain and the second frequency domain;

[0758] >>: Consists of the initialUpliknBWP field (or the corresponding IE of the field). And

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

[0760] UE draws a random number between the lowest and highest values.

[0761] The UE selects a set of RA resources.

[0762] >>: In the first frequency domain, if the random number is equal to or less than an integer; and

[0763] >>: If random in the second frequency domain is higher than an integer or SbfdSelection is not configured in the initialUplinkBWP field;

[0764] >: SbfdSelection:

[0765] >>: Consists of the initialUpliknBWP field (or the corresponding IE of the field). And

[0766] >>: Enumerated as a single value indicating activation.

[0767] The UE selects a set of RA resources.

[0768] >>: If SbfdSelection exists in the initialUpliknBWP field (or the corresponding IE within the field), in the second frequency domain or the first frequency domain with equal probability; and

[0769] >>: If SbfdSelection is not in the initialUpliknBWP field (or the corresponding IE of the field), in the second frequency domain.

[0770] default-RO, non-sbfd-RO, and the first RO are interchangeable.

[0771] The additional RO, sbfd-RO, and second RO are interchangeable.

[0772] The format of the RAR is as follows. The RAR is loaded within the MAC PDU (F100).

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

[0774] >: Applies only to MAC subheaders with a Backoff Indicator.

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

[0776] This is the MAC subheader containing RAPID and MAC RAR.

[0777] The MAC subheader with backoff indicator (F110) consists of five header fields: E / T / R / R / BI.

[0778] A MAC subPDU with a backoff indicator is placed only at the beginning of the MAC PDU (if included).

[0779] 'MAC subPDU with RAPID only' and 'MAC subPDU with RAPID and MAC RAR' can be placed anywhere between the MAC subPDU with only a backoff indicator (if any) and the padding (if any).

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

[0781] MAC RAR (F130) has a fixed size and consists of the following fields.

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

[0783] >: 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.

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

[0785] >: 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.

[0786] The UL Grant (F140) has the following fields.

[0787] >: Frequency Hopping Flag (FH);

[0788] PUSCH Frequency Resource Allocation (FRA);

[0789] PUSCH time resource allocation (TRA);

[0790] Multi-chemical sensitivity;

[0791] >: TPC command for PUSCH; and

[0792] This is a CSI request.

[0793] In a RAR UL grant, the value m of the TAR field provides / represents row index m + 1 to the resource allocation table. The resource allocation table is either the pusch-TimeDomainAllocationList provided by pusch-ConfigCommon or (if the TimeDomainAllocationList provided by pusch-ConfigCommon is not provided by the pusch-ConfigCommon of the selected uplink carrier).

[0794] pusch-TimeDomainAllocationList consists of one or more pusch-TimeDomainAllocation IEs. Each pusch-TimeDomainAllocation consists of the following fields.

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

[0796] mappingType field representing typeA or typeB,

[0797] >: startSymbolAndLength - Represents an index that provides a valid combination of start symbol and length (co-encoded) as a SLIV (start and length indicator).

[0798] The first pusch-TimeDomainAllocation corresponds to row index 1, and the second corresponds to row index 2.

[0799] Indexed rows define the slot offset K2, start symbol S, allocation length L, PUSCH mapping type, and the number of slots used for TBS determination (if numberOfSlotsTBoMS exists in the resource allocation table).

[0800] Table 1 below shows the basic A table. j is a variable whose value is determined based on PUSCH SCS.

[0801] 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

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

[0803] The FRA field represents a set of non-interleaved virtual resource blocks allocated consecutively within the first frequency domain or the second frequency domain. The FRA field consists of a Resource Indication Value (RIV) corresponding to the starting virtual resource block (RB_start) and the length of the consecutively allocated resource blocks (L_RBs). The RIV is defined as follows.

[0804] If (L_RBs - 1) is less than or equal to the bottom (N_frequencyRegion_size / 2), the RIV is equal to N_frequencyRegion_size N·K (L_RBs - 1) + RB_start.

[0805] If (L_RBs - 1) is greater than the bottom (N_frequencyRegion_size / 2), the RIV is equal to N_frequencyRegion_size N·K (N_frequencyRegion_size - L_RBs + 1) + (N_frequencyRegion_size - 1 - RB_start).

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

[0807] A Random Access Preamble is transmitted, and the UE starts the ra-ResponseWindow regardless of the possibility of a measurement gap occurring.

[0808] The UE monitors the SpCell's PDCCH for the Random Access Response identified by RA-RNTI while ra-ResponseWindow is running.

[0809] The UE monitors different RA-RNTIs depending on the frequency domain in which the preamble is transmitted. If the preamble associated with RAR is transmitted in the first frequency domain, the UE monitors the first RA-RNTI for RAR reception. If the preamble associated with RAR is transmitted in the second frequency domain, 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. The second RA-RNTI belongs to the second set of RA-RNTIs. Each RA-RNTI in the first set of RA-RNTIs is associated with default-RO. Each RA-RNTI in the second set of RA-RNTIs is associated with sbfd-RO.

[0810] >: In the following cases:

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

[0812] >>: The above Random Access Response includes a MAC subPDU having a Random Access Preamble identifier corresponding to the transmitted preamble, and

[0813] >: UE performs the following.

[0814] >>: Processing received Timing Advance Command;

[0815] >>: A step of determining the uplink transmission power based on preambleReceivedTargetPower and the power ramping amount applied to the latest random access preamble transmission (i.e., (PREAMBLE_POWER_RAMPING_COUNTER - 1) × PREAMBLE_POWER_RAMPING_STEP); and

[0816] >>: Step of determining time domain resources and frequency domain resources for PUSCH transmission based on UL grant in RAR.

[0818] For PUSCH transmission in S150-35, the UE performs the following operations. 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 is transmitted. Based on the determination, the UE performs PUSCH transmission in the first frequency domain or the second frequency domain.

[0819] To determine the frequency domain, the UE performs the following.

[0820] If the TRA field of the UL grant indicates the following:

[0821] >>: The first symbol of the PUSCH transmission occurs during the SBFD period (in the SBFD symbol).

[0822] >>: The total PUSCH transmission duration occurs during the SBFD duration (SBFD symbols). Or

[0823] >>: At least a portion of the PUSCH transmission duration occurs during the SBFD duration (in the SBFD symbol), and

[0824] The UE determines the PUSCH transmission to be performed in the second frequency domain (E700).

[0825] If the TRA field of the UL grant indicates the following:

[0826] >>: The first symbol of the PUSCH transmission duration occurs during a non-SBFD duration (in a flexible symbol or uplink symbol); or

[0827] >>: The entire PUSCH transmission duration occurs during non-SBFD durations (flexible symbols or uplink symbols).

[0828] >>: At least a portion of the PUSCH transmission duration occurs during non-SBFD duration (flexible symbol or uplink symbol), and

[0829] The UE determines the PUSCH transmission to be performed in the first frequency range (E800).

[0830] Non-SBFD Period:

[0831] It is a period that is not an SBFD period.

[0832] >: Consists of the following.

[0833] >>: Uplink symbol according to part 1 of tdd-UL-DL-ConfigurationCommon (reference SubcarrierSpacing; pattern 1; pattern 2);

[0834] >>: A set of symbols that are flexible symbols according to Part 1 of tdd-UL-DL-ConfigurationCommon and not sbfd symbols according to Part 2 of tdd-UL-DL-ConfigurationCommon (offsetToFirstSBSymobol; nrOfSBSymbols); and

[0835] >>: Set of symbols that are 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 (offsetToFirstSBSymobol; nrOfSBSymbols);

[0836] >: exists in both pattern1 and pattern2.

[0837] SBFD Period:

[0838] >: Consists of the following.

[0839] >>: A symbol set (offsetToFirstSBSymobol; nrOfSBSymbols) that is a flexible symbol according to the first part of tdd-UL-DL-ConfigurationCommon and an sbfd symbol according to the second part of tdd-UL-DL-ConfigurationCommon; and

[0840] >>: A symbol set (offsetToFirstSBSymobol; nrOfSBSymbols) that is a downlink symbol according to the first part of tdd-UL-DL-ConfigurationCommon and an sbfd symbol according to the second part of tdd-UL-DL-ConfigurationCommon;

[0841] It is in pattern1 or pattern2.

[0843] A PUSCH transmission is performed for a sequence of symbols. The PUSCH transmission duration is the series of symbols over which the PUSCH transmission occurs.

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

[0845] K2 (or j) determined by forming a PUSCH SCS in the first frequency domain when determining whether the PUSCH duration belongs to the time domain resources of the initial uplink BWP (e.g., whether the TRA indicates an uplink symbol or a flexible symbol); and

[0846] >: Includes K2 (or j) determined by forming a PUSCH SCS in the second frequency domain when determining whether the PUSCH duration belongs to the SBFD duration (e.g., whether the TRA indicates an SBFD symbol).

[0847] Alternatively, the UE performs the following to determine frequency resources.

[0848] The UE performs PUSCH transmission in the second frequency domain in the following cases.

[0849] Preamble transmission was performed in the second frequency domain; and

[0850] puschSbfdAllowed (indicated by 1 bit) is configured as uplinkConfigCommon of system information.

[0851] The UE performs PUSCH transmission in the first frequency domain in the following cases.

[0852] >: Preamble transmission was performed in the first frequency domain; or

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

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

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

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

[0857] FRA of UL grant.

[0858] When a second frequency domain is selected for PUSCH transmission, the UE determines a set of contiguously allocated resource blocks of the second frequency domain based on the following.

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

[0860] FRA of UL grant.

[0861] The UE performs a PUSCH transmission based on the above judgment.

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

[0863] When Msg3 is transmitted, the UE performs the following.

[0864] >: Step of starting or restarting ra-ContentionResolutionTimer at the first symbol after Msg3 transmission ends;

[0865] >: Monitors PDCCH while ra-ContentionResolutionTimer is running, regardless of the possibility of measurement gaps.

[0866] >: In the following cases:

[0867] >>: A step of receiving a notification of receipt of PDCCH transmission of SpCell from the lower layer;

[0868] >>: MAC PDU was successfully decoded.

[0869] The MAC PDU includes the UE contention resolution identity MAC CE;

[0870] >>: The UE Contention Resolution Identity of MAC CE matches the CCCH SDU transmitted in Msg3, and

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

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

[0873] When the UE is not provided with a C-RNTI, in response to a PUSCH transmission scheduled by a RAR UL grant, the UE attempts to detect DCI format 1_0 with a CRC scrambled by the corresponding TC-RNTI that schedules a PDSCH containing the UE contention resolution identity. In response to receiving a PDSCH with the UE contention resolution identity, the UE transmits HARQ-ACK information to the PUCCH. The PUCCH transmission may exist within a first frequency resource (where the PUSCH and / or preamble is transmitted in the first frequency domain) or a second frequency domain (where the PUSCH and / or preamble is transmitted in the second frequency domain, and where a second set of parameters for the PUCCH resource for the second frequency domain is provided in the system information).

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

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

[0876] >: A second set of parameters for PUCCH resources for the first frequency domain;

[0877] >: Uplink Carrier-specific parameter set; and

[0878] >: This is the set of parameters for the first frequency domain.

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

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

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

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

[0883] This is the set of parameters for the second frequency domain.

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

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

[0886] A first set of parameters for PUCCH resources is applied to HARQ ACK transmission in the first frequency domain and to HARQ ACK transmission in the second frequency domain.

[0887] A second set of parameters for PUCCH resources for the first frequency domain is applied to HARQ ACK transmission in the first frequency domain.

[0888] The second parameter set for the PUCCH resource for the second frequency domain is applied to the HARQ ACK transmission in the second frequency domain.

[0889] The second set of parameters for the PUCCH resource is configured as follows.

[0890] >: pucch-ResourceCommon field; and

[0891] >: nrofPRBs field.

[0892] The first set of parameters for the PUCCH resource is configured as follows.

[0893] >: p0-alpha field;

[0894] >: pucch-GroupHopping field.

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

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

[0897] The nrofPRBs field i represents the number of PRBs used per PUCCH resource for PUCCH type 0 (TS 38.213, Section 9.2.1)

[0898] The pucch-ResourceCommon field represents an entry for a 16-row table in which each row constitutes a set of PUCCH resources / parameters per cell (TS 38.213, Clause 9.2). Each entry is associated with the start PRB of the PUCCH format, time resource, and frequency resource.

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

[0901] Receiving RA is essential for completing the RA procedure. Since the PRACH preamble can be transmitted in the first frequency domain or the second frequency domain, there is a means to determine whether the RAR is for transmitting the PRACH preamble in the first frequency domain or the second frequency domain.

[0902] The UE performs the following to receive RAR.

[0903] The UE receives system information, wherein the system information consists of various information elements (IE);

[0904] The UE triggers the RA (Random Access) procedure.

[0905] The UE transmits a PRACH preamble on a first RO in a first frequency domain or on a second RO in a second frequency domain;

[0906] The UE monitors the PDCCH of a specific RA-RNTI for a specific duration in the third frequency domain;

[0907] The UE receives a RAR containing a MAC subPDU having a random access preamble identifier corresponding to a PRACH preamble; and

[0908] The UE performs a PUSCH transmission based on the UL grant in the RAR, and

[0909] A specific RA-RNTI is selected from the following.

[0910] >: A first set of RA-RNTI when the PRACH preamble is transmitted in the first frequency domain; and

[0911] A second set of RA-RNTI when the PRACH preamble is transmitted in the second frequency domain.

[0912] When the PRACH preamble is transmitted in the first frequency domain, a specific RA-RNTI is determined / calculated based on the following.

[0913] >: For the general RA configuration, this is a parameter for the frequency starting from IE.

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

[0915] >: Parameters for IE's prach configuration index for RA general configuration;

[0916] >: tdd-UL-DL-ConfigCommon's 1st TDD-UL-DL-Pattern IE; and

[0917] >: tdd-UL-DL-ConfigCommon's 2nd TDD-UL-DL-Pattern IE.

[0918] When the PRACH preamble is transmitted in the second frequency domain, a specific RA-RNTI is determined / calculated based on the following.

[0919] >: Frequency start parameter of IE for RA in the second frequency domain;

[0920] >: SCS-SpecificCarrier of downlink configuration;

[0921] >: Parameter for the IE prach configuration index for the RA second frequency domain;

[0922] >: 1st TDD-UL-DL-Pattern IE of tdd-UL-DL-ConfigCommon or 2nd TDD-UL-DL-Pattern IE of tdd-UL-DL-ConfigCommon; and

[0923] >: associatedPattern field of tdd-UL-DL-ConfigCommon;

[0924] >: offsetToFirstSBSymbol field of tdd-UL-DL-ConfigCommon; and

[0925] >: nrOfSBSymbols field of tdd-UL-DL-ConfigCommon.

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

[0927] RA-RNTI = 1 + s_id + 14 × t_id + 14 × 80 × f_id + 14 × 80 × 8 × ul_carrier_id + SBFD_RA_RNTI_OFFSET

[0928] where:

[0929] >: s_id is the index of the first OFDM symbol of the PRACH event (0 ≤ s_id < 14).

[0930] t_id is the index of the first slot of the PRACH event in the system frame (0 ≤ t_id < 80).

[0931] >>: The subcarrier interval for determining t_id is based on the μ(SCS index) value for μ = {0, 1, 2, 3}, and

[0932] For >> μ = {5, 6}, t_id is the index of the 120kHz slot in the system frame containing the PRACH case (0 ≤ t_id < 80).

[0933] >: f_id is the index for the PRACH case in the frequency domain (0 ≤ f_id < 8), and ul_carrier_id is the UL carrier used for random access preamble transmission (0 for NUL carrier, 1 for SUL carrier).

[0934] If the RA-RNTI associated with the last valid PRACH case in the PRACH chance set for the Msg1 iteration is a non-SBFD RO (non-SBFD symbol) when a random access preamble is transmitted in the PRACH case (RO) or when the RA-RNTI is a non-SBFD RO (non-SBFD symbol):

[0935] s_id and t_id are determined according to the following.

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

[0937] >>: Parameters for the prach configuration index for non-SBFD RO in IE for RA general configuration;

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

[0939] >>: tdd-UL-DL-ConfigCommon's second TDD-UL-DL-Pattern IE.

[0940] f_id is determined based on the following.

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

[0942] >: SBFD_RA_RNTI_OFFSET is equal to 0.

[0943] If the RA-RNTI associated with the last valid PRACH case in the PRACH chance set for the Msg1 iteration is an SBFD RO (non-SBFD symbol) when a random access preamble is transmitted in the PRACH case (RO) or when the RA-RNTI is an SBFD RO (non-SBFD symbol):

[0944] s_id and t_id are determined according to the following.

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

[0946] >>: Parameters of the prach configuration index for SBFD RO in sbfd-Config IE;

[0947] >>: The first TDD-UL-DL-Pattern IE of tdd-UL-DL-ConfigCommon;

[0948] >>: tdd-UL-DL-ConfigCommon's second TDD-UL-DL-Pattern IE;

[0949] >>: offsetToFirstSBSymbol field of tdd-UL-DL-ConfigCommon; and

[0950] >>: nrOfSBSymbols field of tdd-UL-DL-ConfigCommon;

[0951] f_id is determined based on the following.

[0952] >>: sbfd-config IE FDM-related parameters (msg1-FDM-sbfd-sbfd, msg1-FrequencyStart-sbfd)

[0953] SBFD_RA_RNTI_OFFSET is equal to a specific value. The specific value may be pre-configured or displayed in system information.

[0955] When the SBFD / second frequency region is configured in the serving cell, it is advantageous for the GNB to control the frequency region in which Msg 3 is transmitted. The GNB uses the TRA field of the RAR to indicate the frequency region for Msg 3 transmission.

[0956] The UE performs the following to send Msg 3.

[0957] The UE receives system information, wherein the system information consists of various information elements (IE);

[0958] The UE triggers the RA (Random Access) procedure.

[0959] The UE transmits a PRACH preamble on a first RO in a first frequency domain or on a second RO in a second frequency domain;

[0960] The UE monitors the PDCCH of a specific RA-RNTI for a specific duration in the third frequency domain;

[0961] The UE receives a RAR containing a MAC subPDU having a random access preamble identifier corresponding to a PRACH preamble; and

[0962] The UE performs a PUSCH transmission based on the TAR and FAR fields in the RAR, and

[0963] A PUSCH transmission based on RAR is performed.

[0964] >: In the first frequency domain, if the TAR field indicates that a PUSCH transmission was performed during the first time period; and

[0965] In the above second frequency domain, if the TAR field indicates that PUSCH transmission is performed during the second time interval,

[0966] The PRB for PUSCH transmission is determined based on the FRA field of the RAR and is as follows.

[0967] >: Number of PRBs in the first frequency domain when PUSCH transmission is performed during the first time interval; and

[0968] >: Number of PRBs in the second frequency domain when PUSCH transmission is performed during the second time period:

[0970] The UE performs the following for contention resolution and HARQ ACK transmission.

[0971] The UE receives system information, wherein the system information consists of various information elements (IE);

[0972] The UE triggers the RA (Random Access) procedure.

[0973] The UE transmits a PRACH preamble on a first RO in a first frequency domain or on a second RO in a second frequency domain;

[0974] The UE monitors the PDCCH of a specific RA-RNTI for a specific duration in the third frequency domain;

[0975] The UE receives a RAR containing a MAC subPDU having a random access preamble identifier corresponding to a PRACH preamble;

[0976] The UE performs a PUSCH transmission based on the TAR and FAR fields in the RAR;

[0977] The UE performs PDSCH reception to resolve contention. And

[0978] The UE performs a HARQ ACK transmission.

[0979] The above HARQ ACK transmission is performed in a first frequency range or a second frequency range.

[0981] Figure 28 illustrates the operation of the UE.

[0982] In U100, the UE receives system information from the base station.

[0983] In U200, the UE receives RRCReconfiguration from the base station.

[0984] In U300, the UE receives the DCI that triggers BWP switching from the base station.

[0985] In U400, the UE determines the symbols available for reception and the symbols available for transmission. If the SBFD UL subband overlaps with the BWP, the SBFD symbol can be transmitted. If the SBFD DL subband overlaps with the BWP, the SBFD symbol can be received.

[0986] In the U500, the UE performs reception for symbols for reception and transmission for symbols for transmission. It receives RAR based on PDCCH.

[0988] FIG. 29 is a block diagram showing the internal structure of a UE to which the disclosure is applied.

[0989] Referring to the diagram, the UE includes a controller (W100), a storage unit (W200), a transmission and reception unit (W300), a main processor (W400), and an I / O unit (W500).

[0990] The control unit (W100) controls the overall operation of the UE in terms of mobile communication. For example, the control unit (W100) receives / transmits signals through the transceiver unit (W300). Additionally, the control unit (W100) writes and reads data to and from the storage unit (W200). To this end, the control unit (W100) includes at least one processor. For example, the control unit (W100) may include a Communication Processor (CP) that performs control for communication and an Application Processor (AP) that controls upper layers, such as an application program. The controller controls the storage unit and the transceiver so that UE operation is performed in the present disclosure.

[0991] The storage unit (W200) stores data for the operation of the UE, such as basic programs, application programs, and configuration information. The storage unit (W200) provides the stored data upon a request from the control unit (W100).

[0992] The transceiver W300 consists of an RF processor, a baseband processor, and one or more antennas. The RF processor performs functions for transmitting and receiving signals over a wireless channel, such as signal band conversion and amplification. Specifically, the RF processor converts a baseband signal provided by an up-baseband processor into an RF band signal, transmits the same signal through the antenna, and converts the RF band signal received through the down-antenna 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), and the like. The RF processor can perform MIMO and can receive multiple layers when performing MIMO operations. The baseband processor performs conversion functions between baseband signals and bit strings 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.

[0993] The main processor W400 controls overall operations other than mobile operations. The main processor (W400) processes user input received from the I / O unit (W500), stores data in the storage unit (W200), controls the controller (W100) for necessary mobile communication operations, and transmits user data to the I / O unit (W500).

[0994] The I / O unit (W500) consists of equipment that inputs user data and outputs user data such as microphones and screens. The I / O unit W500 performs the input and output of user data according to the commands of the main processor.

[0995] FIG. 30 is a block diagram showing the configuration of a base station according to the present disclosure.

[0996] As can be seen in the diagram, the base station includes a controller N100, a storage unit N200, a transceiver N300, and a backhaul interface unit N400.

[0997] The controller N100 controls the overall operation of the main base station. For example, the controller (N100) receives / transmits signals through the transceiver (N300) or the backhaul interface (N400). Additionally, the controller N100 writes and reads data to and from the storage unit N200. To this end, the controller (N100) may include at least one processor. The controller controls the transceiver, the storage unit, and the backhaul interface to enable the base station to operate in the present disclosure.

[0998] Storage unit N200 stores data for the operation of the main base station, such as basic programs, application programs, and configuration information. In particular, storage unit (N200) can store information regarding bearers assigned to connected UEs, measurement results reported by connected UEs, etc. Additionally, storage unit (N200) can store information that serves as a criterion for determining whether to provide multiple connections to the UE or to discontinue them. Furthermore, storage unit (N200) provides the stored data upon request from control unit N100.

[0999] The transceiver N300 consists of an RF processor, a baseband processor, and one or more antennas. The RF processor performs functions for transmitting and receiving signals over a wireless channel, such as signal band conversion and amplification. Specifically, the RF processor converts a baseband signal provided by an up-baseband processor into an RF band signal, transmits the same signal through the antenna, and converts the RF band signal received through the down-antenna into a baseband signal. The RF processor may include a transmit filter, a receive filter, an amplifier, a mixer, an oscillator, a DAC, an ADC, etc. The RF processor may perform downlink MIMO operations by transmitting at least one layer. The baseband processor performs a conversion function between a baseband signal and a bit string 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.

[1000] The backhaul interface unit N400 provides an interface for communicating with other nodes within the network. The backhaul interface unit (N400) converts a bit sequence transmitted from a base station to another node, for example, another base station or core network, into a physical signal, and converts a physical signal received from another node into a bit string.

[1002] IE SCS-SpecificCarrier provides parameters that determine the location and width of the actual carrier or carrier bandwidth. It is specifically defined for numerology (SCS (Subcarrier Spacing)) and the relationship with Point A (frequency offset).

[1004] -- ASN1START

[1005] -- TAG-SCS-SPECIFICCARRIER-START

[1007] SCS-SpecificCarrier ::= SEQUENCE {

[1008] offsetToCarrier INTEGER (0..2199),

[1009] subcarrierSpacing SubcarrierSpacing,

[1010] carrierBandwidth INTEGER (1..maxNrofPhysicalResourceBlocks),

[1011] ...,

[1012] [[

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

[1014] ]]

[1015] [[

[1016] ul-subbandlocationAndBandwidth INTEGER (0..37949) OPTIONAL, -- Need R

[1017] firstDLsubbandlocationAndBandwidth INTEGER (0..37949) OPTIONAL, -- Need R

[1018] secondDLsubbandlocationAndBandwidth INTEGER (0..37949) OPTIONAL -- Need R

[1019] ]]

[1020] }

[1022] -- TAG-SCS-SPECIFICCARRIER-STOP

[1023] -- ASN1STOP

[1025] TxDirectCurrentLocation: Indicates the carrier's downlink Tx DC location. Values ​​in the range 0..3299 represent the subcarrier index within the carrier. Values ​​in the range 3301..4095 are reserved and ignored by the UE. If this field is missing for downlinks within ServingCellConfigCommon and ServingCellConfigCommonSIB, the UE assumes the default value of 3300.

[1026] SubcarrierSpacing: This is the subcarrier spacing of this carrier. It is used to convert offsetToCarrier to the actual frequency.

[1027] ul-subbandlocationAndBandwidth: Configures the frequency domain location and bandwidth of the UL subband. The field value should be interpreted as a Resource Indicator Value (RIV) with N_frequencyRegion_size of 275. The network does not configure this field for DL ​​carriers.

[1028] FirstDLsubbandlocationAndBandwidth: Configures the frequency domain location and bandwidth of the first DL subband. The field value should be interpreted as a Resource Indicator Value (RIV) with N_frequencyRegion_size of 275. The network does not configure this field for UL carriers.

[1029] SecondDLsubbandlocationAndBandwidth: Configures the frequency domain location and bandwidth of the second DL subband. The network does not configure this field for UL carriers.

[1032] The IE TDD-UL-DL-ConfigCommon determines the cell specific Uplink / Downlink TDD configuration.

[1033] TDD-UL-DL-ConfigCommon information element

[1034] -- ASN1START

[1035] -- TAG-TDD-UL-DL-CONFIGCOMMON-START

[1037] TDD-UL-DL-ConfigCommon ::= SEQUENCE {

[1038] referenceSubcarrierSpacing SubcarrierSpacing,

[1039] pattern1 TDD-UL-DL-Pattern,

[1040] pattern2 TDD-UL-DL-Pattern OPTIONAL, -- Need R

[1041] ...

[1042] }

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

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

[1046] nrofDownlinkSlots INTEGER (0..maxNrofSlots),

[1047] nrofDownlinkSymbols INTEGER (0..maxNrofSymbols-1),

[1048] nrofUplinkSlots INTEGER (0..maxNrofSlots),

[1049] nrofUplinkSymbols INTEGER (0..maxNrofSymbols-1),

[1050] ...,

[1051] [[

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

[1053] ]],

[1054] [[

[1055] sbfd-StartingSlotIndex-r19 INTEGER (0..maxNrofSlots-1) OPTIONAL, -- Need R

[1056] sbfd-StartingSymbolIndex-r19 INTEGER (0..maxNrofSymbols-1) OPTIONAL, -- Need R

[1057] sbfd-EndingSlotIndex-r19 INTEGER (0..maxNrofSlots-1) OPTIONAL, -- Need R

[1058] sbfd-EndingSymbolIndex-r19 INTEGER (0..maxNrofSymbols-1) OPTIONAL -- Need R

[1059] ]]

[1060] }

[1062] -- TAG-TDD-UL-DL-CONFIGCOMMON-STOP

[1063] -- ASN1STOP

[1065] sbfd-StartingSlotIndex, sbfd-EndingSlotIndex: Configures the start slot index and end slot index of the SBFD lower band within the TDD-UL-DL period.

[1066] sbfd-StartingSymbolIndex, sbfd-EndingSymbolIndex: Configures the start symbol index and end symbol index within the start slot of the SBFD lower band within the TDD-UL-DL period.

[1067] The SBFD resource pool is an uplink resource in the UL subband of SBFD symbols.

[1069] A consecutive set of SBFD symbols is configured in pattern1 or pattern2.

[1070] A set of consecutive SBFD symbols can be determined based on a set of parameters for the SBFD symbols.

[1071] The parameter set for the SBFD symbol can be sbfd-StartingSlotIndex, sbfd-EndingSlotIndex, StartingSymbolIndex, and sbfd-EndingSymbolIndex.

[1072] The parameter set for SBFD symbols can be determined based on offsetToFirstSBSymobol and nrOfSBSymbols.

[1073] The UE determines that a consecutive set of SBFD symbols is configured in pattern1 in the following cases.

[1074] The parameter set for the SBFD symbol is included in the TDD-UL-DL-Config for pattern1. Or

[1075] >: associatedPattern represents pattern1.

[1076] The UE determines that a consecutive set of SBFD symbols is composed of pattern2 in the following cases.

[1077] The parameter set for the SBFD symbol is included in the TDD-UL-DL-Config for pattern2. Or

[1078] >: associatedPattern represents pattern2.

[1080] The downlink or flexible symbol provided by tdd-UL-DL-ConfigurationCommon may include a UL subband provided by ulSubbandlocationAndBandwidth, a first DL subband provided by firstdlSubbandlocationAndBandwidth, and additionally, for the SCS configuration of any configured UL BWP or DL ​​BWP provided by, may include a second DL subband provided by seconddlSubbandlocationAndBandwidth. Refer to μscs-SpecificCarrierList [4, TS 38.211]. Then, the downlink or flexible symbol is called an SBFD symbol. Otherwise, it is called a non-SBFD symbol. The uplink symbol is a non-SBFD symbol. An SBFD symbol or non-SBFD symbol provided by tdd-UL-DL-ConfigurationCommon cannot be changed to a non-SBFD symbol or an SBFD symbol, respectively, by other information. The UE is not provided with a coresetPoolIndex and is not configured to receive PDSCH according to one or more TCI states mapped to a single TCI code point [6, TS 38.214] for a serving cell that is provided with SBFD symbols.

[1081] The SBFD symbol starts at the first slot provided by SBFD-StartingSlotIndex, starts at the first symbol of the first slot provided by SBFD-StartingSymbolIndex, ends at the second slot provided by SBFD-EndingSlotIndex, and ends at the second symbol of the second slot provided by SBFD-EndingSymbolIndex. The SBFD symbol can be provided as either pattern1 or pattern2 (if provided). The construction period for the SBFD symbol is P msec if only pattern1 is provided, or P + P2 if pattern2 is additionally provided.

[1082] IE BWP-DownlinkDedicated is used to configure dedicated (UE-specific) parameters for the downlink BWP.

[1084] -- ASN1START

[1085] -- TAG-BWP-DOWNLINKDEDICATED-START

[1087] BWP-DownlinkDedicated::= SEQUENCE {

[1088] pdcch-Config SetupRelease { PDCCH-Config} OPTIONAL, -- Need M

[1089] pdsch-Config SetupRelease { PDSCH-Config} OPTIONAL, -- Need M

[1090] sps-Config SetupRelease { SPS-Config} OPTIONAL, -- Need M

[1091] radioLinkMonitoringConfig SetupRelease { RadioLinkMonitoringConfig} OPTIONAL, -- Need M

[1092] ...,

[1093] preConfGapStatus-r17 BIT STRING (SIZE (maxNrofGapId-r17)) OPTIONAL, -- Cond PreConfigMG

[1094] beamFailureRecoverySpCellConfig-r17 SetupRelease { BeamFailureRecoveryRSConfig-r16} OPTIONAL, -- Cond SpCellOnly

[1095] harq-FeedbackEnablingforSPSactive-r17 BOOLEAN OPTIONAL, -- Need R

[1096] cfr-ConfigMulticast-r17 SetupRelease { CFR-ConfigMulticast-r17} OPTIONAL, -- Need M

[1097] dl-PPW-PreConfigToAddModList-r17 DL-PPW-PreConfigToAddModList-r17 OPTIONAL, -- Need N

[1098] dl-PPW-PreConfigToReleaseList-r17 DL-PPW-PreConfigToReleaseList-r17 OPTIONAL, -- Need N

[1099] nonCellDefiningSSB-r17 NonCellDefiningSSB-r17 OPTIONAL, -- Need R

[1100] servingCellMO-r17 MeasObjectId OPTIONAL -- Cond MeasObject-NCD-SSB

[1101] ]],

[1102] [[

[1103] tci-InDCI-r18 SetupRelease {TCI-InDCI-r18} OPTIONAL -- Need M

[1104] ]],

[1105] [[

[1106] sbfd-Config2-Reception-r19 ENUMERATED {enabled} OPTIONAL -- Need S

[1107] ]]

[1108] }

[1110] -- TAG-BWP-DOWNLINKDEDICATED-STOP

[1111] -- ASN1STOP

[1112] pdcch-Config: UE-specific PDCCH configuration for a single BWP.

[1113] pdsch-Config: UE-specific PDSCH configuration for a single BWP.

[1114] sbfd-Config2-Reception: TS 38.214

[19] , as specified in clause X, indicates that PDSCH reception may be on SBFD symbols and non-SBFD symbols in other slots for a dedicated DL BWP. If not enabled, Configuration 1 applies to PDSCH reception for the specified DL BWP.

[1115] sps-Config: A UE-specific Semi-Persistent Scheduling (SPS) configuration for a single BWP. Except for reconfiguration using synchronization, the NW does not reconfigure sps-Config when there is an active configured downlink assignment (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.

[1116] IE BWP-UplinkCommon is used to configure common parameters for 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.

[1117] -- ASN1START

[1118] -- TAG-BWP-UPLINKCOMMON-START

[1120] BWP-UplinkCommon::= SEQUENCE {

[1121] genericParameters BWP,

[1122] rach-ConfigCommon SetupRelease { RACH-ConfigCommon} OPTIONAL, -- Need M

[1123] pusch-ConfigCommon SetupRelease { PUSCH-ConfigCommon} OPTIONAL, -- Need M

[1124] pucch-ConfigCommon SetupRelease { PUCCH-ConfigCommon} OPTIONAL, -- Need M

[1125] …

[1126] additionalRACH-ConfigList-r17 SetupRelease { AdditionalRACH-ConfigList-r17} OPTIONAL, -- Cond SpCellOnly2

[1127] rsrp-ThresholdMsg3-r17 RSRP-Range OPTIONAL, -- Need R

[1128] numberOfMsg3-RepetitionsList-r17 SEQUENCE (SIZE (4)) OF NumberOfMsg3-Repetitions-r17 OPTIONAL, -- Cond Msg3Rep

[1129] mcs-Msg3-Repetitions-r17 SEQUENCE (SIZE (8)) OF INTEGER (0..31) OPTIONAL -- Cond Msg3Rep

[1130] …

[1131] rsrp-ThresholdMsg1-RepetitionNum2-r18 RSRP-Range OPTIONAL, -- Need R

[1132] rsrp-ThresholdMsg1-RepetitionNum4-r18 RSRP-Range OPTIONAL, -- Need R

[1133] rsrp-ThresholdMsg1-RepetitionNum8-r18 RSRP-Range OPTIONAL, -- Need R

[1134] preambleTransMax-Msg1-Repetition-r18 ENUMERATED {n1, n2, n4, n6, n8, n10, n20, n50, n100, n200} OPTIONAL -- Cond Msg1Rep1

[1135] ]],

[1136] [[

[1137] sbfd-RSRP-ThresholdRO-Type-r19 RSRP-Range OPTIONAL, -- Need R

[1138] sbfd-RSRP-ThresholdRO-TypeUsage-r19 ENUMERATED {above,below} OPTIONAL, -- Need R

[1139] sbfd-RSRP-ThresholdMsg1-RepetitionNum2-r19 RSRP-Range OPTIONAL, -- Need R

[1140] sbfd-RSRP-ThresholdMsg1-RepetitionNum4-r19 RSRP-Range OPTIONAL, -- Need R

[1141] sbfd-RSRP-ThresholdMsg1-RepetitionNum8-r19 RSRP-Range OPTIONAL, -- Need R

[1142] rach-ConfigCommonSBFD-r19 SetupRelease { RACH-ConfigCommonSBFD-r19} OPTIONAL -- Need M

[1143] ]]

[1144] }

[1145] AdditionalRACH-ConfigList-r17::= SEQUENCE (SIZE(1..maxAdditionalRACH-r17)) OF AdditionalRACH-Config-r17

[1146] AdditionalRACH-Config-r17::= SEQUENCE {

[1147] rach-ConfigCommon-r17 RACH-ConfigCommon OPTIONAL, -- Need R

[1148] msgA-ConfigCommon-r17 MsgA-ConfigCommon-r16 OPTIONAL, -- Need R

[1149] ...

[1150] [[

[1151] rach-ConfigCommonSBFD-r19 SetupRelease { RACH-ConfigCommonSBFD-r19} OPTIONAL -- Need M

[1152] ]]

[1153] }

[1154] NumberOfMsg3-Repetitions-r17::= ENUMERATED {n1, n2, n3, n4, n7, n8, n12, n16}

[1155] RACH-ConfigCommonSBFD-r19 = SEQUENCE {

[1156] sbfd-RACH-SingleConfig-r19 ENUMERATED {enabled} OPTIONAL, -- Need R

[1157] sbfd-RACH-DualConfig-r19 SBFD-RACH-DualConfig-r19 OPTIONAL -- Need R

[1158] }

[1159] SBFD-RACH-DualConfig-r19::= SEQUENCE {

[1160] sbfd-AdditionalRACH-Config-r19 RACH-ConfigCommon OPTIONAL, -- Need R

[1161] sbfd-RACH-DualConfig-ValidROacrossSymbolTypes-r19 ENUMERATED {enabled} OPTIONAL -- Need R

[1162] }

[1163] -- TAG-BWP-UPLINKCOMMON-STOP

[1164] -- ASN1STOP

[1166] additionalRACH-ConfigList: A list of RACH configurations by feature or feature combination; that is, RACH configurations configured in addition to those configured by rach-ConfigCommon and msgA-ConfigCommon. The network links all possible preambles of additional RACH configurations to one or more features or feature combinations. The network does not configure this list to have more than 16 items. If both rach-ConfigCommon and msgA-ConfigCommon are configured for a specific FeatureCombination, the network always provides the same additional RACH-Config.

[1167] mcs-Msg3-Repetitions: Configuration of eight candidate MCS indices for PUSCH transfers scheduled by DCI format 0_0 using a CRC scrambled by TC-RNTI and scheduled by RAR UL grant. Only the first four configured MCS indices or the default MCS index are used for PUSCH transfers scheduled by RAR UL grant. This field is applicable only if the UE selects a random access resource representing Msg3 repetitions in this BWP. If this field is missing when 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} (see TS 38.214

[19] , Clause 6.1.4).

[1168] preambleTransMax-Msg1-Repetition: The maximum number of MSG1 iterations (2, 4, and 8) performed before switching to a higher number of iterations (see TS 38.321[3], Section 5.1.1). This field applies only if more than one iteration number is configured in the shared RO. Without this field, it is not possible to switch from a lower number of iterations to a higher number of iterations.

[1169] pucch-ConfigCommon: This is a cell-specific parameter for the PUCCH of this BWP.

[1170] pusch-ConfigCommon: This is a cell-specific parameter for PUSCH of this BWP.

[1171] rach-ConfigCommon: Configuration of the cell-specific random access parameters used by the UE for contention-based and contention-free random access and contention-based beam failure recovery in this BWP. NW configures the SSB-based RA (and the corresponding RACH-ConfigCommon) only for the UL BWP if the linked DL BWP (with the same bwp-Id as the UL-BWP) is an initial DL BWP or an initial DL BWP including a DL BWP associated with nonCellDefiningSSB, or (e) for a RedCap UE, if it is a RedCap-specific initial downlink BWP. Whenever the network configures contention-free 4-phase random access (e.g., reconfiguration via synchronous or beam failover or PDCCH sequence), rach-ConfigCommon (no suffix) and / or rach-ConfigCommon-r17 are configured, and the UE applies these configurations according to the set of RACH resources selected during RACH initialization, as specified in TS 38.321[3]. For RedCap-related initial uplink BWPs, if msgA-ConfigCommon is configured for this BWP, rach-ConfigCommon is always configured.

[1172] rsrp-ThresholdMsg1-RepetitionNum2, rsrp-ThresholdMsg1-RepetitionNum4, rsrp-ThresholdMsg1-RepetitionNum8: Thresholds used by the UE to determine whether to select resources representing Msg1 repeat numbers 2, 4, or 8 in this BWP, as specified in TS 38.321[3]. This value applies to all BWPs and all RACH configurations. For a given MSG1 repeat count, this field is required if both the set of random access resources with the MSG1 repeat mark associated with this MSG1 repeat count and the set of random access resources without the MSG1 repeat mark are configured in the BWP, or if both the set of random access resources with the MSG1 repeat mark associated with this MSG1 repeat count and the set of random access resources with the MSG1 repeat mark are configured in the BWP. A lower repeat count is configured in the BWP; otherwise, it is absent.

[1173] rsrp-ThresholdMsg3: This is the threshold used by the UE to determine whether to select resources with Msg3 repeats in this BWP, as specified in TS 38.321[3]. This field is required if both a set of random access resources with MSG3 repeats and a set of random access resources without MSG3 repeats are configured in the BWP. Otherwise, it is absent.

[1174] sbfd-RACH-SingleConfig: Indicates whether RACH configuration option 1 for SBFD random access operations is enabled.

[1175] sbfd-RACH-DualConfig: Used to configure random access parameters in SBFD symbols by setting one additional RACH configuration; see RACH configuration option 2 for SBFD random access operations in section x of TS 38.211

[16] and section y of TS 38.213

[13] .

[1176] sbfd-RACH-DualConfig-ValidROacrossSymbolTypes: Indicates whether a configured RO starting with an SBFD symbol and ending with a non-SBFD symbol in the same slot or a different slot is valid for RACH configuration option 2.

[1177] 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 number 2, 4, or 8 within the SBFD RO.

[1178] sbfd-RSRP-ThresholdRO-Type: This is the threshold used by the SBFD capable UE to select the RACH occasion type.

[1179] sbfd-RSRP-ThresholdRO-TypeUsage: Indicates how an SBFD capable UE selects a RACH occasion type using sbfd-RSRP-ThresholdRO-Type. With the above value, the SBFD capable UE selects an SBFD RACH occasion if the measured downlink path loss threshold RSRP is greater than or equal to sbfd-RSRP-ThresholdRO-Type, and selects a non-SBFD RACH occasion if the measured downlink path loss threshold RSRP is not greater than or equal to sbfd-RSRP-ThresholdRO-Type. With the following value, the SBFD capable UE selects an SBFD RACH occasion if the measured downlink path loss threshold RSRP is less than sbfd-RSRP-ThresholdRO-Type, and selects a non-SBFD RACH occasion if the measured downlink path loss threshold RSRP is not less than sbfd-RSRP-ThresholdRO-Type.

[1181] - BWP-UplinkDedicated

[1182] IE BWP-UplinkDedicated is used to configure dedicated (UE-specific) parameters for the uplink BWP.

[1183] BWP-UplinkDedicated information element

[1184] -- ASN1START

[1185] -- TAG-BWP-UPLINKDEDICATED-START

[1187] BWP-UplinkDedicated::= SEQUENCE {

[1188] pucch-Config SetupRelease { PUCCH-Config} OPTIONAL, -- Need M

[1189] pusch-Config SetupRelease { PUSCH-Config} OPTIONAL, -- Need M

[1190] configuredGrantConfig SetupRelease { ConfiguredGrantConfig} OPTIONAL, -- Need M

[1191] srs-Config SetupRelease { SRS-Config} OPTIONAL, -- Need M

[1192] beamFailureRecoveryConfig SetupRelease { BeamFailureRecoveryConfig} OPTIONAL, -- Cond SpCellOnly

[1193] ...,

[1194] ul-powerControl-r17 Uplink-powerControlId-r17 OPTIONAL, -- Cond NoTCI-PC

[1195] sbfd-Config2-Transmission-r19 ENUMERATED {enabled} OPTIONAL, -- Need S

[1196] sbfd-Config2-PUSCH-RBOffset-r19 INTEGER(0..maxNrofPhysicalResourceBlocks) OPTIONAL -- Need R

[1198] -- TAG-BWP-UPLINKDEDICATED-STOP

[1199] -- ASN1STOP

[1200] configuredGrantConfig: A configured grant of type 1 or type 2. It can be configured for UL or SUL, but for type 1, it cannot be configured for both at once. Except for reconfiguration using synchronization, the NW does not reconfigure configuredGrantConfig when there is an active configured uplink grant of type 2 (see TS 38.321 [3]). However, the NW can deconfigure configuredGrantConfig at any time. The network can configure a grant configured in only one BWP using this field or configuredGrantConfigToAddModList.

[1201] PUCCH-Config: This is the PUCCH configuration for one BWP of the serving cell's generic UL or SUL. If the UE is configured as a SUL, the network configures PUCCH in only one BWP of the uplink (general UL or SUL). The network configures PUCCH-Config in at least the non-initial BWP for SpCells and in all BWPs for PUCCH SCells. If supported by the UE, the network may configure up to one additional SCell in a cell group (i.e., PUCCH SCell) that has PUCCH-Config. If PUCCH cell switching is supported by the UE, the network may configure two TDD serving cells with PUCCH-Config within each PUCCH group. To support PUCCH cell switching in a PUCCH group with SpCells, the TDD SpCell and one TDD SCell must have PUCCH-Config in the generic UL. To support PUCCH cell switching in a PUCCH group that has only SCells, two TDD SCells must have PUCCH-Config in a general UL.

[1202] The NW can configure the PUCCH for the BWP when setting up the BWP. The network can also move the PUCCH between the UL and SUL carriers of a single serving cell by adding / removing and adding (for PUCCH SCells) pucch-Config in RRCReconfiguration using reconfigurationWithSync (for SpCells or PUCCH SCells) or SCell release. In other cases, only modifications to previously configured pucch-Configs are allowed.

[1203] If the (S)UL BWP of the serving cell is configured as PUCCH, all other (S)UL BWPs must also be configured as PUCCH.

[1204] pusch-Config: PUSCH configuration for one BWP of the general UL or SUL of the serving cell. If the UE is configured as SUL and has PUSCH-Config for both UL and SUL, the UL / SUL indicator field in the DCI indicates which one to use. See TS 38.212

[17] , clause 7.3.1.

[1205] sbfd-Config2-Transmission: Indicates that PUCCH and PUSCH transmissions may be in SBFD symbols and non-SBFD symbols in different slots of a given UL BWP (see TS 38.213

[13] , section x and TS 38.214

[19] , section y). If not enabled, configuration 1 applies to PUCCH and PUSCH transmissions in a given UL BWP.

[1206] sbfd-Config2-PUSCH-RBOffset: Indicates the RB offset for determining the start PRB for Type 2 configuration grant and dynamic grant PUSCH transmissions in the SBFD symbol for configuration 2 (see TS 38.214

[19] , section y).

[1208] srs-Config: Uplink sounding reference signal configuration.

[1209] ul-powerControl: Configures power control parameters for PUCCH, PUSCH, and SRS when the UE is configured with unifiedTCI-StateType for this serving cell. For each serving cell, ul-powerControl is configured for all BWP-UplinkDedicated or not configured for BWP-UplinkDedicated. If unifiedTCI-StateRef in BWP-UplinkDedicated or PDSCH-Config is set to unifiedTCI-StateType as joint, it refers to another serving cell, and ul-powerControl is configured for all BWP-UplinkDedicated of these two serving cells or not configured for all BWP-UplinkDedicated of these two serving cells.

[1211] IE ConfiguredGrantConfig is used to configure uplink transport without dynamic grants according to two possible schemes. The actual uplink grant can be configured via RRC (type 1) or provided via PDCCH (addressed as CS-RNTI) (type 2). Multiple configured grant configurations can be configured in a single BWP of a serving cell.

[1213] -- ASN1START

[1214] -- TAG-CONFIGUREDGRANTCONFIG-START

[1215] ConfiguredGrantConfig::= SEQUENCE {

[1216] frequencyHopping ENUMERATED {intraSlot, interSlot} OPTIONAL, -- Need S

[1217] cg-DMRS-Configuration DMRS-UplinkConfig,

[1218] mcs-Table ENUMERATED {qam256, qam64LowSE} OPTIONAL, -- Need S

[1219] mcs-TableTransformPrecoder ENUMERATED {qam256, qam64LowSE} OPTIONAL, -- Need S

[1220] uci-OnPUSCH SetupRelease { CG-UCI-OnPUSCH} OPTIONAL, -- Need M

[1221] resourceAllocation ENUMERATED { resourceAllocationType0, resourceAllocationType1, dynamicSwitch},

[1222] rbg-Size ENUMERATED {config2} OPTIONAL, -- Need S

[1223] powerControlLoopToUse ENUMERATED {n0, n1},

[1224] p0-PUSCH-Alpha P0-PUSCH-AlphaSetId,

[1225] transformPrecoder ENUMERATED {enabled, disabled} OPTIONAL, -- Need S

[1226] nrofHARQ-Processes INTEGER(1..16),

[1227] repK ENUMERATED {n1, n2, n4, n8},

[1228] repK-RV ENUMERATED {s1-0231, s2-0303, s3-0000} OPTIONAL, -- Need R

[1229] periodicity ENUMERATED {

[1230] sym2, sym7, sym1x14, sym2x14, sym4x14, sym5x14, sym8x14, sym10x14, sym16x14, sym20x14,

[1231] sym32x14, sym40x14, sym64x14, sym80x14, sym128x14, sym160x14, sym256x14, sym320x14, sym512x14,

[1232] sym640x14, sym1024x14, sym1280x14, sym2560x14, sym5120x14,

[1233] sym6, sym1x12, sym2x12, sym4x12, sym5x12, sym8x12, sym10x12, sym16x12, sym20x12, sym32x12,

[1234] sym40x12, sym64x12, sym80x12, sym128x12, sym160x12, sym256x12, sym320x12, sym512x12, sym640x12,

[1235] sym1280x12, sym2560x12

[1236] },

[1237] configuredGrantTimer INTEGER (1..64) OPTIONAL, -- Need R

[1238] rrc-ConfiguredUplinkGrant SEQUENCE {

[1239] timeDomainOffset INTEGER (0..5119),

[1240] timeDomainAllocation INTEGER (0..15),

[1241] frequencyDomainAllocation BIT STRING (SIZE(18)),

[1242] antennaPort INTEGER (0..31),

[1243] dmrs-SeqInitialization INTEGER (0..1) OPTIONAL, -- Need R

[1244] precodingAndNumberOfLayers INTEGER (0..63),

[1245] srs-ResourceIndicator INTEGER (0..15) OPTIONAL, -- Need R

[1246] mcsAndTBS INTEGER (0..31),

[1247] frequencyHoppingOffset INTEGER (1.. maxNrofPhysicalResourceBlocks-1) OPTIONAL, -- Need R

[1248] pathlossReferenceIndex INTEGER (0..maxNrofPUSCH-PathlossReferenceRSs-1),

[1249] ...,

[1250] [[

[1251] pusch-RepTypeIndicator-r16 ENUMERATED {pusch-RepTypeA,pusch-RepTypeB} OPTIONAL, -- Need M

[1252] frequencyHoppingPUSCH-RepTypeB-r16 ENUMERATED {interRepetition, interSlot} OPTIONAL, -- Cond RepTypeB

[1253] timeReferenceSFN-r16 ENUMERATED {sfn512} OPTIONAL -- Need S

[1254] ]],

[1255] [[

[1256] pathlossReferenceIndex2-r17 INTEGER (0..maxNrofPUSCH-PathlossReferenceRSs-1) OPTIONAL, -- Need R

[1257] srs-ResourceIndicator2-r17 INTEGER (0..15) OPTIONAL, -- Need R

[1258] precodingAndNumberOfLayers2-r17 INTEGER (0..63) OPTIONAL, -- Need R

[1259] timeDomainAllocation-v1710 INTEGER (16..63) OPTIONAL, -- Need M

[1260] timeDomainOffset-r17 INTEGER (0..40959) OPTIONAL, -- Need R

[1261] cg-SDT-Configuration-r17 CG-SDT-Configuration-r17 OPTIONAL -- Need M

[1262] ]],

[1263] [[

[1264] srs-ResourceSetId-r18 SRS-ResourceSetId OPTIONAL, -- Need R

[1265] cg-LTM-Configuration-r18 CG-RRC-Configuration-r18 OPTIONAL, -- Cond LTM

[1266] cg-SDT-PeriodicityExt-r18 ENUMERATED {

[1267] sym1x14x1280, sym2x14x1280, sym4x14x1280 , sym8x14x1280, sym16x14x1280,

[1268] sym32x14x1280, sym48x14x1280, sym64x14x1280, sym96x14x1280, sym128x14x1280,

[1269] sym192x14x1280, sym240x14x1280, sym256x14x1280, sym384x14x1280, sym472x14x1280,

[1270] sym480x14x1280, sym512x14x1280, sym768x14x1280, sym944x14x1280, sym960x14x1280,

[1271] sym1408x14x1280, sym1536x14x1280, sym1888x14x1280, sym1920x14x1280,

[1272] sym2816x14x1280, sym3072x14x1280, sym3776x14x1280, sym5632x14x1280,

[1273] sym6144x14x1280, sym7552x14x1280, sym7680x14x1280, sym11264x14x1280,

[1274] sym15104x14x1280, sym15360x14x1280, sym22528x14x1280, sym30208x14x1280,

[1275] sym45056x14x1280, sym60416x14x1280, sym90112x14x1280, sym180224x14x1280,

[1276] sym4x12x1280, sym8x12x1280, sym16x12x1280, sym32x12x1280, sym192x12x1280,

[1277] sym384x12x1280, sym960x12x1280, sym1888x12x1280, sym3776x12x1280,

[1278] sym5632x12x1280, sym11264x12x1280, spare13, spare12, spare11, spare10, spare9,

[1279] spare8, spare7, spare6, spare5, spare4, spare3, spare2, spare1

[1280] } OPTIONAL, -- Cond CG-SDT1

[1281] timeReferenceHyperSFN-r18 INTEGER (0..1023) OPTIONAL, -- Cond CG-SDT2

[1282] cg-RRC-Configuration-r18 CG-RRC-Configuration-r18 OPTIONAL, -- Cond RACH-LessHO

[1283] applyIndicatedTCI-State-r18 ENUMERATED {first, second, both, spare1} OPTIONAL -- Need R

[1284] ]],

[1285] [[

[1286] sbfd-Config2-PUSCH-RBoffset-r19 INTEGER (0..maxNrofPhysicalResourceBlocks) OPTIONAL, -- Need R

[1287] symbolType-r19 ENUMERATED {sbfd, non-sbfd} OPTIONAL, -- Need R

[1288] frequencyHoppingOffset-SBFD-r19 INTEGER (1.. maxNrofPhysicalResourceBlocks-1) OPTIONAL, -- Need R

[1289] pusch-MutingResources-r19 PUSCH-MutingResources-r19 OPTIONAL -- Need R

[1290] ]]

[1292] } OPTIONAL, -- Need R

[1293] ...,

[1295] }

[1296] -- TAG-CONFIGUREDGRANTCONFIG-STOP

[1297] -- ASN1STOP

[1298] cg-StartingOffsets: This field does not apply to UEs that can act as start devices in semi-static channel access mode; that is, it does not apply to UEs configured with UE FFP parameters (e.g., period, offset), regardless of whether the UE starts its own COT or shares the gNB's COT.

[1299] dmrs-SeqInitialization: The network configures this field if transformPrecoder is disabled or the value of sdt-NrofDMRS-Sequences is set to 1. Otherwise, the field does not exist.

[1300] frequencyDomainAllocation: Indicates frequency domain resource allocation (see TS 38.214

[19] , Clause 6.1.2 and TS 38.212

[17] , Clause 7.3.1).

[1301] frequencyHopping: The intraSlot value enables 'Intra-slot frequency hopping' and the interSlot value enables 'Inter-slot frequency hopping'. If the field is absent, frequency hopping is not configured. The frequencyHopping field applies to grants configured for 'pusch-RepTypeA' (see TS 38.214

[19] , Section 6.3.1).

[1302] frequencyHoppingOffset: Frequency hopping offset used when frequency hopping is enabled (see TS 38.214

[19] , Sections 6.1.2 and 6.3).

[1303] frequencyHoppingOffset-SBFD: Configures the frequency hopping offset for PUSCH, assigning a type 1 configuration from the SBFD symbol (see TS 38.214

[19] ).

[1304] mcs-Table: Represents the MCS table that the UE will use for PUSCH without transform precoding. If the field is missing, the UE applies the qam64 value.

[1305] p0-PUSCH-Alpha: This is the index of the P0-PUSCH-AlphaSet to be used for this configuration.

[1306] pusch-MutingResources: Type 1 configuration assigned. Used to configure the time and frequency positions of UL muting resources for PUSCH transmission, see Section x of TS 38.211

[16] and Section y of TS 38.214

[19] .

[1307] rbg-Size: Select between Configuration 1 and Configuration 2 for the RGB size of PUSCH. If resourceAllocation is set to resourceAllocationType1, the UE does not apply this field. Otherwise, the UE applies the config1 value when the field is missing. Note: rbg-Size is used when the transformPrecoder parameter is disabled.

[1308] repK-RV: The RV (redundancy version) sequence to use. Refer to TS 38.214

[19] , clause 6.1.2. The network configures this field when repetition is used, i.e., when repK is set to n2, n4, or n8. This field is not configured when cg-RetransmissionTimer is configured. Otherwise, the field is absent.

[1309] repK: number of iterations K, see TS 38.214

[19] . If field repK-v1710 exists, UE ignores repK(no suffix).

[1310] resourceAllocation: A configuration of resource allocation type 0 and resource allocation type 1. For type 1 UL data transfer without grants, resourceAllocation must be resourceAllocationType0 or resourceAllocationType1.

[1311] rrc-ConfiguredUplinkGrant: Configuration for "configured grant" transmission using a fully RRC configured UL grant (Type 1). If this field is missing, the UE uses the UL grant configured by the DCI addressed as CS-RNTI (Type 2).

[1312] sbfd-Config2-PUSCH-RBoffset: Indicates the RB offset for determining the start PRB for a Type 1 configuration-granted PUSCH transmission in the SBFD symbol for configuration 2 (see TS 38.214

[19] , section y).

[1313] sequenceOffsetForRV: Configures the RV offset for the start RV for the first iteration (the first actual iteration of PUSCH iteration type B) to the second 'SRS resource set' of PUSCH configured in srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2 for 'codebook' or 'noncodebook'.

[1314] srs-ResourceSetId: Represents the set of associated SRS resources for PUSCH+PUSCH simultaneous uplink transmission for CG-type 1 PUSCH. If cg-RRC-Configuration is configured, the network does not configure this field.

[1315] srs-ResourceIndicator, srs-ResourceIndicator-v1850: Indicates the SRS resources to be used (see TS 38.212

[17] , Section 7.3.1.1.2 and TS 38.214

[19] , Section 6.1.2.3). The network does not configure this if CG-SDT or cg-RRC-Configuration is configured. The srs-ResourceIndicator-v1850 field is configured only if 8 antenna ports are configured (see TS 38.214

[19] , Section 6.1.1.2). The network does not configure both srs-ResourceIndicator and srs-ResourceIndicator-v1850.

[1316] srs-ResourceIndicator2: Indicates the SRS resource to be used for the second set of SRS resources. If this field is present, srs-ResourceIndicator is used for the first set of SRS resources. If cg-RRC-Configuration is configured, the network does not configure this field.

[1317] startingFromRV0: This field is used to determine the initial transmission status of a transmission block for a specified RV sequence (see TS 38.214

[19] , clause 6.1.2.3.1). If cg-RetransmissionTimer-r16 is configured for CG operations, the network does not configure this field.

[1318] symbolType: Configures a valid symbol type for Type 1 CG PUSCH for SBFD Configuration 1. If SBFD Configuration 2 is enabled for UL BWP, the network does not configure this field. (See TS 38.214

[19] , Clause 6.1.3)

[1319] timeDomainAllocation, timeDomainAllocation-v1710: Indicates a combination of start symbol, length, and PUSCH mapping type (see TS 38.214

[19] , Section 6.1.2 and TS 38.212

[17] , Section 7.3.1).

[1320] If the timeDomainAllocation-v1710 field exists, the UE must ignore the timeDomainAllocation field (without a suffix).

[1321] timeDomainOffset: Offset associated with the reference SFN indicated by timeReferenceSFN, see TS 38.321 [3], clause 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).

[1322] timeReferenceHyperSFN: Represents the H-SFN used to determine the offset of a resource in the time domain. The UE uses the nearest H-SFN with the indicated number prior to receiving the configured grant configuration (see TS 38.321[3], Section 5.8.2). If the timeReferenceHyperSFN field is missing, the reference hyper-SFN is 0.

[1323] 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 prior to receiving the configured grant configuration (see TS 38.321[3], Section 5.8.2). If the timeReferenceSFN field is missing, the reference SFN is 0.

[1324] transformPrecoder: Enables or disables transform precoding for type1 and type2. If the field is missing, the UE enables or disables transform precoding based on the msg3-transformPrecoder field of the RACH-ConfigCommon included directly within the BWP configuration (i.e., not included in additionalRACH-ConfigList), see TS 38.214

[19] , clause 6.1.3).

[1325] uci-OnPUSCH: Selection and configuration between dynamic and semi-static beta offsets. For unauthorized Type 1 UL data transmission, uci-OnPUSCH must be set to semiStatic. The network does not configure this for CG-SDT.

[1326] IE PUCCH-Config is used to configure UE-specific PUCCH parameters (per BWP).

[1327] IE PUCCH-Config is used to configure UE-specific PUCCH parameters (per BWP).

[1328] PUCCH-Config information element

[1329] -- ASN1START

[1330] -- TAG-PUCCH-CONFIG-START

[1331] PUCCH-Config::= SEQUENCE {

[1332] resourceSetToAddModList SEQUENCE (SIZE (1..maxNrofPUCCH-ResourceSets)) OF PUCCH-ResourceSet OPTIONAL, -- Need N

[1333] resourceSetToReleaseList SEQUENCE (SIZE (1..maxNrofPUCCH-ResourceSets)) OF PUCCH-ResourceSetId OPTIONAL, -- Need N

[1334] resourceToAddModList SEQUENCE (SIZE (1..maxNrofPUCCH-Resources)) OF PUCCH-Resource OPTIONAL, -- Need N

[1335] resourceToReleaseList SEQUENCE (SIZE (1..maxNrofPUCCH-Resources)) OF PUCCH-ResourceId OPTIONAL, -- Need N

[1336] format1 SetupRelease { PUCCH-FormatConfig} OPTIONAL, -- Need M

[1337] format2 SetupRelease { PUCCH-FormatConfig} OPTIONAL, -- Need M

[1338] format3 SetupRelease { PUCCH-FormatConfig} OPTIONAL, -- Need M

[1339] format4 SetupRelease { PUCCH-FormatConfig} OPTIONAL, -- Need M

[1340] schedulingRequestResourceToAddModList SEQUENCE (SIZE (1..maxNrofSR-Resources)) OF SchedulingRequestResourceConfig

[1341] OPTIONAL, -- Need N

[1342] schedulingRequestResourceToReleaseList SEQUENCE (SIZE (1..maxNrofSR-Resources)) OF SchedulingRequestResourceId

[1343] OPTIONAL, -- Need N

[1344] multi-CSI-PUCCH-ResourceList SEQUENCE (SIZE (1..2)) OF PUCCH-ResourceId OPTIONAL, -- Need M

[1345] dl-DataToUL-ACK SEQUENCE (SIZE (1..8)) OF INTEGER (0..15) OPTIONAL, -- Need M

[1346] spatialRelationInfoToAddModList SEQUENCE (SIZE (1..maxNrofSpatialRelationInfos)) OF PUCCH-SpatialRelationInfo

[1347] OPTIONAL, -- Need N

[1348] spatialRelationInfoToReleaseList SEQUENCE (SIZE (1..maxNrofSpatialRelationInfos)) OF PUCCH-SpatialRelationInfoId

[1349] OPTIONAL, -- Need N

[1350] pucch-PowerControl PUCCH-PowerControl OPTIONAL, -- Need M

[1351] ...,

[1352] [[

[1353] resourceToAddModListExt-v1610 SEQUENCE (SIZE (1..maxNrofPUCCH-Resources)) OF PUCCH-ResourceExt-v1610 OPTIONAL, -- Need N

[1354] dl-DataToUL-ACK-r16 SetupRelease { DL-DataToUL-ACK-r16} OPTIONAL, -- Need M

[1355] ul-AccessConfigListDCI-1-1-r16 SetupRelease { UL-AccessConfigListDCI-1-1-r16} OPTIONAL, -- Need M

[1356] subslotLengthForPUCCH-r16 CHOICE {

[1357] normalCP-r16 ENUMERATED {n2,n7},

[1358] extendedCP-r16 ENUMERATED {n2,n6}

[1359] } OPTIONAL, -- Need R

[1360] dl-DataToUL-ACK-DCI-1-2-r16 SetupRelease { DL-DataToUL-ACK-DCI-1-2-r16} OPTIONAL, -- Need M

[1361] numberOfBitsForPUCCH-ResourceIndicatorDCI-1-2-r16 INTEGER (0..3) OPTIONAL, -- Need R

[1362] dmrs-UplinkTransformPrecodingPUCCH-r16 ENUMERATED {enabled} OPTIONAL, -- Cond PI2-BPSK

[1363] spatialRelationInfoToAddModListSizeExt-v1610 SEQUENCE (SIZE (1..maxNrofSpatialRelationInfosDiff-r16)) OF PUCCH-SpatialRelationInfo

[1364] OPTIONAL, -- Need N

[1365] spatialRelationInfoToReleaseListSizeExt-v1610 SEQUENCE (SIZE (1..maxNrofSpatialRelationInfosDiff-r16)) OF PUCCH-SpatialRelationInfoId

[1366] OPTIONAL, -- Need N

[1367] spatialRelationInfoToAddModListExt-v1610 SEQUENCE (SIZE (1..maxNrofSpatialRelationInfos-r16)) OF PUCCH-SpatialRelationInfoExt-r16

[1368] OPTIONAL, -- Need N

[1369] spatialRelationInfoToReleaseListExt-v1610 SEQUENCE (SIZE (1..maxNrofSpatialRelationInfos-r16)) OF

[1370] PUCCH-SpatialRelationInfoId-r16 OPTIONAL, -- Need N

[1371] resourceGroupToAddModList-r16 SEQUENCE (SIZE (1..maxNrofPUCCH-ResourceGroups-r16)) OF PUCCH-ResourceGroup-r16

[1372] OPTIONAL, -- Need N

[1373] resourceGroupToReleaseList-r16 SEQUENCE (SIZE (1..maxNrofPUCCH-ResourceGroups-r16)) OF PUCCH-ResourceGroupId-r16

[1374] OPTIONAL, -- Need N

[1375] sps-PUCCH-AN-List-r16 SetupRelease { SPS-PUCCH-AN-List-r16} OPTIONAL, -- Need M

[1376] schedulingRequestResourceToAddModListExt-v1610 SEQUENCE (SIZE (1..maxNrofSR-Resources)) OF SchedulingRequestResourceConfigExt-v1610

[1377] OPTIONAL -- Need N

[1378] ]],

[1379] ]],

[1380] [[

[1381] schedulingRequestResourceToAddModListExt-v19xy SEQUENCE (SIZE (1..maxNrofSR-Resources)) OF SchedulingRequestResourceConfigExt-v19xy

[1382] OPTIONAL, -- Need N

[1383] resourceToAddModListExt-v19xy SEQUENCE (SIZE (1..maxNrofPUCCH-Resources)) OF PUCCH-ResourceExt-v19xy

[1384] OPTIONAL -- Need N

[1385] ]]

[1386] PUCCH-FormatConfig::= SEQUENCE {

[1387] interslotFrequencyHopping ENUMERATED {enabled} OPTIONAL, -- Need R

[1388] additionalDMRS ENUMERATED {true} OPTIONAL, -- Need R

[1389] maxCodeRate PUCCH-MaxCodeRate OPTIONAL, -- Need R

[1390] nrofSlots ENUMERATED {n2,n4,n8} OPTIONAL, -- Need S

[1391] pi2BPSK ENUMERATED {enabled} OPTIONAL, -- Need R

[1392] simultaneousHARQ-ACK-CSI ENUMERATED {true} OPTIONAL -- Need R

[1393] }

[1394] -- A set with one or more PUCCH resources

[1395] PUCCH-ResourceSet::= SEQUENCE {

[1396] pucch-ResourceSetId PUCCH-ResourceSetId,

[1397] resourceList SEQUENCE (SIZE (1..maxNrofPUCCH-ResourcesPerSet)) OF PUCCH-ResourceId,

[1398] maxPayloadSize INTEGER (4..256) OPTIONAL -- Need R

[1399] }

[1400] PUCCH-ResourceSetId::= INTEGER (0..maxNrofPUCCH-ResourceSets-1)

[1401] PUCCH-Resource::= SEQUENCE {

[1402] pucch-ResourceId PUCCH-ResourceId,

[1403] startingPRB PRB-Id,

[1404] intraSlotFrequencyHopping ENUMERATED { enabled} OPTIONAL, -- Need R

[1405] secondHopPRB PRB-Id OPTIONAL, -- Need R

[1406] format CHOICE {

[1407] format0 PUCCH-format0,

[1408] format1 PUCCH-format1,

[1409] format2 PUCCH-format2,

[1410] format3 PUCCH-format3,

[1411] format4 PUCCH-format4

[1412] }

[1413] }

[1414] PUCCH-ResourceExt-v19xy::= SEQUENCE {

[1415] startingPRB-SBFD-r19 PRB-Id OPTIONAL, -- Need R

[1416] secondHopPRB-SBFD-r19 PRB-Id OPTIONAL -- Need R

[1417] }

[1418] PUCCH-ResourceId::= INTEGER (0..maxNrofPUCCH-Resources-1)

[1419] PUCCH-format0::= SEQUENCE {

[1420] initialCyclicShift INTEGER(0..11),

[1421] nrofSymbols INTEGER (1..2),

[1422] startingSymbolIndex INTEGER(0..13)

[1423] }

[1424] PUCCH-format1::= SEQUENCE {

[1425] initialCyclicShift INTEGER(0..11),

[1426] nrofSymbols INTEGER (4..14),

[1427] startingSymbolIndex INTEGER(0..10),

[1428] timeDomainOCC INTEGER(0..6)

[1429] }

[1430] PUCCH-format2::= SEQUENCE {

[1431] nrofPRBs INTEGER (1..16),

[1432] nrofSymbols INTEGER (1..2),

[1433] startingSymbolIndex INTEGER(0..13)

[1434] }

[1435] PUCCH-format3::= SEQUENCE {

[1436] nrofPRBs INTEGER (1..16),

[1437] nrofSymbols INTEGER (4..14),

[1438] startingSymbolIndex INTEGER(0..10)

[1439] }

[1440] PUCCH-format4::= SEQUENCE {

[1441] nrofSymbols INTEGER (4..14),

[1442] occ-Length ENUMERATED {n2,n4},

[1443] occ-Index ENUMERATED {n0,n1,n2,n3},

[1444] startingSymbolIndex INTEGER(0..10)

[1445] }

[1446] DL-DataToUL-ACK-r16::= SEQUENCE (SIZE (1..8)) OF INTEGER (-1..15)

[1447] -- TAG-PUCCH-CONFIG-STOP

[1448] -- ASN1STOP

[1449] dl-DataToUL-ACK, dl-DataToUL-ACK-DCI-1-2: Timing list of specified PDSCHs for DL ​​ACK (see TS 38.213

[13] , Section 9.1.2). The dl-DataToUL-ACK field applies to DCI format 1_1 and the dl-DataToUL-ACK-DCI-1-2 field applies to DCI format 1_2 (see TS 38.212

[17] , Section 7.3.1 and TS 38.213

[13] , Section 9.2.3). dl-DataToUL-ACK-v1700 applies to NTN and dl-DataToUL-ACK-r17 applies to FR2-2. dl-DataToUL-ACK-r18 may apply to ATG. If dl-DataToUL-ACK-r16, dl-DataToUL-ACK-r17, dl-DataToUL-ACK-v1700, or dl-DataToUL-ACK-r18 is signaled, the UE must ignore dl-DataToUL-ACK (no suffix). A value of -1 corresponds to an "inapplicable value" for cases where A / N feedback timing is not explicitly included during PDSCH scheduling. The dl-DataToUL-ACK-r17 and dl-DataToUL-ACK-DCI-1-2-r17 fields are applicable only to 480 kHz or 960 kHz SCS. The dl-DataToUL-ACK-r18 field applies to DCI format 1_1, and the dl-DataToUL-ACK-DCI-1-2-r18 field applies to DCI format 1_2 (see TS 38.212

[17] , Section 7.3.1 and TS 38.213

[13] , Section 9.2.3).

[1450] format0: This is a parameter common to all PUCCH resources of format 0.

[1451] format1: A parameter common to all PUCCH resources of format 1.

[1452] format2: This is a parameter common to all PUCCH resources of format 2.

[1453] format3: This is a parameter common to all PUCCH resources of format 3.

[1454] format4: This is a parameter common to all PUCCH resources of format 4.

[1455] mappingPattern: Indicates whether the UE must follow a cyclic mapping pattern or a sequential mapping pattern when the PUCCH resource used for the repetition of PUCCH transmission includes first and second spatial settings for FR2, or first and second sets of power control parameters for FR1 (see TS 38.213

[13] , Section 9.2.6).

[1456] pucch-PowerControl: Configures PUCCH transmission of power control parameters.

[1457] resourceToAddModList, resourceToAddModListExt, resourceToReleaseList: A list for adding and releasing PUCCH resources that can be applied to serving cells where UL BWP and PUCCH-Config are defined. The resources defined herein are referenced from other parts of the configuration to determine which resources the UE will use for which reporting. If resourceToAddModListExt is included in the network, it contains the same number of items as resourceToAddModList and is listed in the same order.

[1458] sps-PUCCH-AN-List: Represents a list of PUCCH resources for DL ​​SPS HARQ ACK. The first and last SPS-PUCCH-AN in the list do not have a maxPayloadSize field. If configured, override n1PUCCH-AN in SPS-config.

[1459] nrofSlots: PUCCH is the same number of slots. When the field is empty, UE applies the value n1. See TS 38.213

[13] , clause 9.2.6.

[1460] nrofPRBs: Indicates the number of PRBs used per PUCCH resource for a PUCCH format (see TS 38.213

[13] , Section 9.2.1). This field is applicable to PUCCH format0, format1, and format4 in FR2-2. Supported values ​​for format4 are 1, 2, 3, 4, 5, 6, 8, 9, 10, 12, 15, and 16.

[1461] pucch-ResourceId: This is the identifier of the PUCCH resource.

[1462] secondHopPRB-SBFD: Represents the second hop PRB of the PUCCH resource at the SBFD symbol.

[1463] startingPRB-SBFD: Represents the starting PRB of the PUCCH resource in the SBFD symbol.

[1465] IE RACH-ConfigDedicated is used to specify dedicated random access parameters.

[1466] RACH-ConfigDedicated information element

[1467] -- ASN1START

[1468] -- TAG-RACH-CONFIGDEDICATED-START

[1469] RACH-ConfigDedicated::= SEQUENCE {

[1470] cfra CFRA OPTIONAL, -- Need S

[1471] ra-Prioritization RA-Prioritization OPTIONAL, -- Need N

[1472] ...,

[1473] [[

[1474] ra-PrioritizationTwoStep-r16 RA-Prioritization OPTIONAL, -- Need N

[1475] cfra-TwoStep-r16 CFRA-TwoStep-r16 OPTIONAL -- Need S

[1476] ]],

[1477] [[

[1478] ra-OccasionType-r19 ENUMERATED {SBFD} OPTIONAL -- Need S

[1479] ]]

[1480] }

[1481] CFRA::= SEQUENCE {

[1482] occasions SEQUENCE {

[1483] rach-ConfigGeneric RACH-ConfigGeneric,

[1484] ssb-perRACH-Occasion ENUMERATED {oneEighth, oneFourth, oneHalf, one, two, four, eight, sixteen}

[1485] OPTIONAL -- Cond Mandatory

[1486] } OPTIONAL, -- Need S

[1487] resources CHOICE {

[1488] ssb SEQUENCE {

[1489] ssb-ResourceList SEQUENCE (SIZE(1..maxRA-SSB-Resources)) OF CFRA-SSB-Resource,

[1490] ra-ssb-OccasionMaskIndex INTEGER (0..15)

[1491] },

[1492] csirs SEQUENCE {

[1493] csirs-ResourceList SEQUENCE (SIZE(1..maxRA-CSIRS-Resources)) OF CFRA-CSIRS-Resource,

[1494] rsrp-ThresholdCSI-RS RSRP-Range

[1495] }

[1496] },

[1497] ...,

[1498] [[

[1499] totalNumberOfRA-Preambles INTEGER (1..63) OPTIONAL -- Cond Occasions

[1500] ]],

[1501] [[

[1502] msg1-RepetitionNum-r18 ENUMERATED {n2, n4, n8, spare1} OPTIONAL -- Cond 4StepCFRArep

[1503] ]]

[1504] }

[1505] CFRA-SSB-Resource::= SEQUENCE {

[1506] ssb SSB-Index,

[1507] ra-PreambleIndex INTEGER (0..63),

[1508] ...,

[1509] [[

[1510] msgA-PUSCH-Resource-Index-r16 INTEGER (0..3071) OPTIONAL -- Cond 2StepCFRA

[1511] ]]

[1512] }

[1513] CFRA-CSIRS-Resource ::= SEQUENCE {

[1514] csi-RS CSI-RS-Index,

[1515] ra-OccasionList SEQUENCE (SIZE(1..maxRA-OccasionsPerCSIRS)) OF INTEGER (0..maxRA-Occasions-1),

[1516] ra-PreambleIndex INTEGER (0..63),

[1517] ...

[1518] }

[1519] -- TAG-RACH-CONFIGDEDICATED-STOP

[1520] -- ASN1STOP

[1521] csi-RS: ID of the CSI-RS resource defined in the measurement object associated with this document cell.

[1522] ra-OccasionList: The RA occasions used by the UE when performing CF-RA to select candidate beams identified by this CSI-RS. The network ensures that the RA occasion indexes provided here are also configured by prach-ConfigurationIndex and msg1-FDM. Each RACH occasion is numbered sequentially, first in ascending order of the frequency resource index for frequency multiplexed PRACH situations; second, in increasing order of the time resource index for time-multiplexed PRACH events within the PRACH slot; and third, in increasing order of the index for the PRACH slot.

[1523] ra-PreambleIndex: RA preamble index to use in RA situations associated with this CSI-RS.

[1524] msg1-RepetitionNum: Indicates the number of MSG1 repetitions used for contention-free 4-step random access types in TS 38.321[3]. If this field is missing, the UE performs contention-free 4-step random access without MSG1-Repetitions.

[1525] Case: RA case for contention-free random access. If the field is missing, the UE uses the RA occasions configured in RACH-ConfigCommon in the first active UL BWP.

[1526] ra-ssb-OccasionMaskIndex: PRACH mask index explicitly signaled for RA resource selection in TS 38.321[3]. The mask is valid for all SSB resources receiving signals in ssb-ResourceList. The UE must ignore this field if the msg1-RepetitionNum field included in CFRA is set.

[1527] rach-ConfigGeneric: Configures contention-free random access situations for CFRA. The UE must ignore preambleReceivedTargetPower, preambleTransMax, powerRampingStep, and ra-ResponseWindow signaled within this field and use the corresponding values ​​provided in RACH-ConfigCommon.

[1528] ssb-perRACH-Occasion: This is the number of SSBs per RACH case.

[1529] totalNumberOfRA-Preambles: The total number of preambles used for contention-free random access to RACH resources defined in CFRA, excluding preambles used for other purposes (e.g., SI requests). If the field is missing but the field occasions exists, the UE can assume that all 64 preambles are for RA. The setting must match the setting of ssb-perRACH-Occasion (if present), i.e., it must be a multiple of the number of SSBs per RACH occasion.

[1530] ra-PreambleIndex: This is the preamble index that the UE must use when performing CF-RA to select candidate beams identified by this SSB.

[1531] Ssb: This is the ID of the SSB transmitted from this serving cell.

[1532] Cfra: A parameter for contention-free random access to a given target cell. If this field and cfra-TwoStep are absent, the UE performs contention-based random access.

[1533] ra-OccasionType: Indicates the SBFD RACH occasion type to use CFRA in SBFD-supported UEs. If none is present, it indicates the non-SBFD RACH occasion type to use.

[1534] ra-prioritization: A parameter applied to a priority random access procedure for a specified target cell (see TS 38.321 [3], clause 5.1.1).

[1536] IE RACH-ConfigGeneric is used to specify random access parameters for general random access and beam failure recovery.

[1537] RACH-ConfigGeneric information element

[1538] -- ASN1START

[1539] -- TAG-RACH-CONFIGGENERIC-START

[1540] RACH-ConfigGeneric::= SEQUENCE {

[1541] prach-ConfigurationIndex INTEGER (0..255);

[1542] msg1-FDM ENUMERATED {one, two, four, eight},

[1543] msg1-FrequencyStart INTEGER (0..maxNrofPhysicalResourceBlocks-1);

[1544] zeroCorrelationZoneConfig INTEGER(0..15);

[1545] preambleReceivedTargetPower INTEGER (-202..-60);

[1546] preambleTransMax ENUMERATED {n3, n4, n5, n6, n7, n8, n10, n20, n50, n100, n200},

[1547] powerRampingStep ENUMERATED {dB0, dB2, dB4, dB6},

[1548] ra-ResponseWindow ENUMERATED {sl1, sl2, sl4, sl8, sl10, sl20, sl40, sl80},

[1549] ...,

[1550] [[

[1551] prach-ConfigurationPeriodScaling-IAB-r16 ENUMERATED {scf1,scf2,scf4,scf8,scf16,scf32,scf64} OPTIONAL, -- Need R

[1552] prach-ConfigurationFrameOffset-IAB-r16 INTEGER (0..63) OPTIONAL, -- Need R

[1553] prach-ConfigurationSOffset-IAB-r16 INTEGER (0..39) OPTIONAL, -- Need R

[1554] ra-ResponseWindow-v1610 ENUMERATED { sl60, sl160} OPTIONAL, -- Need R

[1555] prach-ConfigurationIndex-v1610 INTEGER (256..262) OPTIONAL -- Need R

[1556] ]],

[1557] [[

[1558] ra-ResponseWindow-v1700 ENUMERATED {sl240, sl320, sl640, sl960, sl1280, sl1920, sl2560} OPTIONAL -- Need R

[1559] ]],

[1560] [[

[1561] sbfd-RACH-SingleConfig-preambleReceivedTargetPower-r19 INTEGER (-202..-60) OPTIONAL -- Need R

[1562] ]]

[1564] }

[1566] -- TAG-RACH-CONFIGGENERIC-STOP

[1567] -- ASN1STOP

[1568] msg1-FDM: The number of PRACH transmissions FDMed in a single instance. (See TS 38.211

[16] , Clause 6.3.3.2).

[1569] msg1-FrequencyStart: The offset of the lowest PRACH transmission situation in the frequency domain corresponding to PRB 0. This value is configured so that the corresponding RACH resource is entirely within the bandwidth of the UL BWP. (See TS 38.211

[16] , Clause 6.3.3.2).

[1570] powerRampingStep: The power ramping step of PRACH (see TS 38.321 [3], 5.1.3). This field is set to the same value for different iteration counts associated with a specific FeatureCombination.

[1571] prach-ConfigurationIndex: This is the PRACH configuration index. For prach-ConfigurationIndex configured under beamFailureRecoveryConfig, prach-ConfigurationIndex may only be in short preamble format (see TS 38.211

[16] , Section 6.3.3.2). If the prach-ConfigurationIndex-v1610 field exists, the UE must ignore the value provided for prach-ConfigurationIndex (no suffix).

[1572] preambleReceivedTargetPower: This is the 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). Only multiples of 2 dBm can be selected (e.g., -202, -200, -198, etc.). This field is set to the same value for different iterations associated with a specific FeatureCombination.

[1573] preambleTransMax: The maximum number of RA preamble transmissions performed before declaring failure (see TS 38.321[3], Sections 5.1.4 and 5.1.5). The UE must ignore this field if rach-ConfigGeneric is included within EarlyUL-SyncConfig IE.

[1574] ra-ResponseWindow: This is the Msg2(RAR) window length (number of slots). The network configures a value of 10ms or less when Msg2 is transmitted over the permitted spectrum and 40ms or less when Msg2 is transmitted over shared spectrum channel access (see TS 38.321 [3], Section 5.1.4). The UE ignores this field if it is included in SCellConfig. If ra-ResponseWindow-v1610 or ra-ResponseWindow-v1700 is received, the UE ignores ra-ResponseWindow(no suffix). The ra-ResponseWindow-v1700 field is applicable to SCS 480kHz and SCS 960kHz. The UE must ignore this field if rach-ConfigGeneric is included within EarlyUL-SyncConfig IE.

[1575] sbfd-RACH-SingleConfig-preambleReceivedTargetPower: Configures preambleReceivedTargetPower for SBFD RO for SBFD RACH configuration option 1 (see section x of TS 38.211

[16] and section y of TS 38.213

[13] ).

[1577] -SchedulingRequestResourceConfig

[1578] IE SchedulingRequestResourceConfig determines the physical layer resources in the PUCCH to which the UE can send dedicated scheduling requests (D-SR) (see TS 38.213

[13] , Section 9.2.4).

[1580] -- ASN1START

[1581] -- TAG-SCHEDULINGREQUESTRESOURCECONFIG-START

[1582] SchedulingRequestResourceConfig::= SEQUENCE {

[1583] schedulingRequestResourceId SchedulingRequestResourceId,

[1584] schedulingRequestID SchedulingRequestId,

[1585] periodicityAndOffset CHOICE {

[1586] sym2 NULL,

[1587] sym6or7 NULL,

[1588] sl1 NULL, -- Recurs in every slot

[1589] sl2 INTEGER (0..1),

[1590] sl4 INTEGER (0..3),

[1591] sl5 INTEGER (0..4),

[1592] sl8 INTEGER (0..7),

[1593] sl10 INTEGER (0..9),

[1594] sl16 INTEGER (0..15),

[1595] sl20 INTEGER (0..19),

[1596] sl40 INTEGER (0..39),

[1597] sl80 INTEGER (0..79),

[1598] sl160 INTEGER (0..159),

[1599] sl320 INTEGER (0..319),

[1600] sl640 INTEGER (0..639)

[1601] } OPTIONAL, -- Need M

[1602] resource PUCCH-ResourceId OPTIONAL -- Need M

[1603] }

[1605] SchedulingRequestResourceConfigExt-v19xy::= SEQUENCE {

[1606] symbolType-r19 ENUMERATED {sbfd, non-sbfd} OPTIONAL -- Need R

[1607] }

[1609] -- TAG-SCHEDULINGREQUESTRESOURCECONFIG-STOP

[1610] -- ASN1STOP

[1612] periodicityAndOffset: SR periodicity and offset(symbol or slot number)

[1613] resource: The ID of the PUCCH resource to which the UE must send a scheduling request. The actual PUCCH-Resource is configured in the PUCCH-Config of the same UL BWP and serving cell as this SchedulingRequestResourceConfig. The network configures a PUCCH-Resource of PUCCH-format0 or PUCCH-format1 (other formats are not supported) (see TS 38.213

[13] , Section 9.2.4).

[1614] schedulingRequestID: This is the ID of the SchedulingRequestConfig using this scheduling request resource.

[1615] symbolType: Configures the valid symbol type for the PUCCH configured for the SR in 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)

[1617] IE SRS-Config is used to configure sounding reference signal transmission. The 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 a set of SRS-Resources or SRS-PosResources using the configured aperiodicSRS-ResourceTrigger (L1 DCI). The network does not configure the SRS-specific power control parameter Alpha (no suffix) or path loss ReferenceRS (if the integrated TCI-StateType is configured for the serving cell).

[1618] -- ASN1START

[1619] -- TAG-SRS-CONFIG-START

[1620] SRS-Config::= SEQUENCE {

[1621] srs-ResourceSetToReleaseList SEQUENCE (SIZE(1..maxNrofSRS-ResourceSets)) OF SRS-ResourceSetId OPTIONAL, -- Need N

[1622] srs-ResourceSetToAddModList SEQUENCE (SIZE(1..maxNrofSRS-ResourceSets)) OF SRS-ResourceSet OPTIONAL, -- Need N

[1623] srs-ResourceToReleaseList SEQUENCE (SIZE(1..maxNrofSRS-Resources)) OF SRS-ResourceId OPTIONAL, -- Need N

[1624] srs-ResourceToAddModList SEQUENCE (SIZE(1..maxNrofSRS-Resources)) OF SRS-Resource OPTIONAL, -- Need N

[1625] tpc-Accumulation ENUMERATED {disabled} OPTIONAL, -- Need S

[1626] ...,

[1627] [[

[1628] srs-RequestDCI-1-2-r16 INTEGER (1..2) OPTIONAL, -- Need S

[1629] srs-RequestDCI-0-2-r16 INTEGER (1..2) OPTIONAL, -- Need S

[1630] srs-ResourceSetToAddModListDCI-0-2-r16 SEQUENCE (SIZE(1..maxNrofSRS-ResourceSets)) OF SRS-ResourceSet OPTIONAL, -- Need N

[1631] srs-ResourceSetToReleaseListDCI-0-2-r16 SEQUENCE (SIZE(1..maxNrofSRS-ResourceSets)) OF SRS-ResourceSetId OPTIONAL, -- Need N

[1632] srs-PosResourceSetToReleaseList-r16 SEQUENCE (SIZE(1..maxNrofSRS-PosResourceSets-r16)) OF SRS-PosResourceSetId-r16

[1633] OPTIONAL, -- Need N

[1634] srs-PosResourceSetToAddModList-r16 SEQUENCE (SIZE(1..maxNrofSRS-PosResourceSets-r16)) OF SRS-PosResourceSet-r16 OPTIONAL,-- Need N

[1635] srs-PosResourceToReleaseList-r16 SEQUENCE (SIZE(1..maxNrofSRS-PosResources-r16)) OF SRS-PosResourceId-r16 OPTIONAL,-- Need N

[1636] srs-PosResourceToAddModList-r16 SEQUENCE (SIZE(1..maxNrofSRS-PosResources-r16)) OF SRS-PosResource-r16 OPTIONAL -- Need N

[1637] ]],

[1638] [[

[1639] dci-TriggeringPosResourceSetLink-r18 ENUMERATED { enabled} OPTIONAL -- Need R

[1640] ]]

[1641] }

[1643] SRS-ResourceSet::= SEQUENCE {

[1644] srs-ResourceSetId SRS-ResourceSetId,

[1645] srs-ResourceIdList SEQUENCE (SIZE(1..maxNrofSRS-ResourcesPerSet)) OF SRS-ResourceId OPTIONAL, -- Cond Setup

[1646] resourceType CHOICE {

[1647] aperiodic SEQUENCE {

[1648] aperiodicSRS-ResourceTrigger INTEGER (1..maxNrofSRS-TriggerStates-1),

[1649] csi-RS NZP-CSI-RS-ResourceId OPTIONAL, -- Cond NonCodebook

[1650] slotOffset INTEGER (1..32) OPTIONAL, -- Need S

[1651] ...,

[1652] [[

[1653] aperiodicSRS-ResourceTriggerList SEQUENCE (SIZE(1..maxNrofSRS-TriggerStates-2))

[1654] OF INTEGER (1..maxNrofSRS-TriggerStates-1) OPTIONAL -- Need M

[1655] ]]

[1656] },

[1657] semi-persistent SEQUENCE {

[1658] associatedCSI-RS NZP-CSI-RS-ResourceId OPTIONAL, -- Cond NonCodebook

[1659] ...

[1660] },

[1661] periodic SEQUENCE {

[1662] associatedCSI-RS NZP-CSI-RS-ResourceId OPTIONAL, -- Cond NonCodebook

[1663] ...

[1664] }

[1665] },

[1666] usage ENUMERATED {beamManagement, codebook, nonCodebook, antennaSwitching},

[1667] alpha Alpha OPTIONAL, -- Need S

[1668] p0 INTEGER (-202..24) OPTIONAL, -- Cond Setup

[1669] pathlossReferenceRS PathlossReferenceRS-Config OPTIONAL, -- Need M

[1670] srs-PowerControlAdjustmentStates ENUMERATED { sameAsFci2, separateClosedLoop} OPTIONAL, -- Need S

[1671] ...,

[1672] [[

[1673] pathlossReferenceRSList-r16 SetupRelease { PathlossReferenceRSList-r16} OPTIONAL -- Need M

[1674] ]],

[1675] [[

[1676] usagePDC-r17 ENUMERATED {true} OPTIONAL, -- Need R

[1677] availableSlotOffsetList-r17 SEQUENCE (SIZE(1..4)) OF AvailableSlotOffset-r17 OPTIONAL, -- Need R

[1678] followUnifiedTCI-StateSRS-r17 ENUMERATED {enabled} OPTIONAL -- Need R

[1679] ]],

[1680] [[

[1681] applyIndicatedTCI-State-r18 ENUMERATED {first, second} OPTIONAL -- Cond FollowUTCI

[1682] ]],

[1683] [[

[1684] symbolType-r19 ENUMERATED {sbfd, non-sbfd} OPTIONAL -- Need R

[1685] ]]

[1686] }

[1688] AvailableSlotOffset-r17::= INTEGER (0..7)

[1690] PathlossReferenceRS-Config::= CHOICE {

[1691] ssb-Index SSB-Index,

[1692] csi-RS-Index NZP-CSI-RS-ResourceId

[1693] }

[1695] PathlossReferenceRSList-r16::= SEQUENCE (SIZE (1..maxNrofSRS-PathlossReferenceRS-r16)) OF PathlossReferenceRS-r16

[1697] PathlossReferenceRS-r16::= SEQUENCE {

[1698] srs-PathlossReferenceRS-Id-r16 SRS-PathlossReferenceRS-Id-r16,

[1699] pathlossReferenceRS-r16 PathlossReferenceRS-Config

[1700] }

[1702] SRS-PathlossReferenceRS-Id-r16::= INTEGER (0..maxNrofSRS-PathlossReferenceRS-1-r16)

[1704] SRS-PosResourceSet-r16::= SEQUENCE {

[1705] srs-PosResourceSetId-r16 SRS-PosResourceSetId-r16,

[1706] srs-PosResourceIdList-r16 SEQUENCE (SIZE(1..maxNrofSRS-ResourcesPerSet)) OF SRS-PosResourceId-r16

[1707] OPTIONAL, -- Cond Setup

[1708] resourceType-r16 CHOICE {

[1709] aperiodic-r16 SEQUENCE {

[1710] aperiodicSRS-ResourceTriggerList-r16 SEQUENCE (SIZE(1..maxNrofSRS-TriggerStates-1))

[1711] OF INTEGER (1..maxNrofSRS-TriggerStates-1) OPTIONAL, -- Need M

[1712] ...

[1713] },

[1714] semi-persistent-r16 SEQUENCE {

[1715] ...

[1716] },

[1717] periodic-r16 SEQUENCE {

[1718] ...

[1719] }

[1720] },

[1721] alpha-r16 Alpha OPTIONAL, -- Need S

[1722] p0-r16 INTEGER (-202..24) OPTIONAL, -- Cond Setup

[1723] pathlossReferenceRS-Pos-r16 CHOICE {

[1724] ssb-IndexServing-r16 SSB-Index,

[1725] ssb-Ncell-r16 SSB-InfoNcell-r16,

[1726] dl-PRS-r16 DL-PRS-Info-r16

[1727] } OPTIONAL, -- Need M

[1728] ...

[1730] }

[1732] SRS-ResourceSetId::= INTEGER (0..maxNrofSRS-ResourceSets-1)

[1734] SRS-PosResourceSetId-r16::= INTEGER (0..maxNrofSRS-PosResourceSets-1-r16)

[1736] SRS-Resource::= SEQUENCE {

[1737] srs-ResourceId SRS-ResourceId,

[1738] nrofSRS-Ports ENUMERATED {port1, ports2, ports4},

[1739] ptrs-PortIndex ENUMERATED {n0, n1} OPTIONAL, -- Need R

[1740] transmissionComb CHOICE {

[1741] n2 SEQUENCE {

[1742] combOffset-n2 INTEGER (0..1),

[1743] cyclicShift-n2 INTEGER (0..7)

[1744] },

[1745] n4 SEQUENCE {

[1746] combOffset-n4 INTEGER (0..3),

[1747] cyclicShift-n4 INTEGER (0..11)

[1748] }

[1749] },

[1750] resourceMapping SEQUENCE {

[1751] startPosition INTEGER (0..5),

[1752] nrofSymbols ENUMERATED {n1, n2, n4},

[1753] repetitionFactor ENUMERATED {n1, n2, n4}

[1754] },

[1755] freqDomainPosition INTEGER (0..67),

[1756] freqDomainShift INTEGER (0..268),

[1757] freqHopping SEQUENCE {

[1758] c-SRS INTEGER (0..63),

[1759] b-SRS INTEGER (0..3),

[1760] b-hop INTEGER (0..3)

[1761] },

[1762] groupOrSequenceHopping ENUMERATED { neither, groupHopping, sequenceHopping},

[1763] resourceType CHOICE {

[1764] aperiodic SEQUENCE {

[1765] ...

[1766] },

[1767] semi-persistent SEQUENCE {

[1768] periodicityAndOffset-sp SRS-PeriodicityAndOffset,

[1769] ...

[1770] },

[1771] periodic SEQUENCE {

[1772] periodicityAndOffset-p SRS-PeriodicityAndOffset,

[1773] ...

[1774] }

[1775] },

[1776] sequenceId INTEGER (0..1023),

[1777] spatialRelationInfo SRS-SpatialRelationInfo OPTIONAL, -- Need R

[1778] ...,

[1779] [[

[1780] resourceMapping-r16 SEQUENCE {

[1781] startPosition-r16 INTEGER (0..13),

[1782] nrofSymbols-r16 ENUMERATED {n1, n2, n4},

[1783] repetitionFactor-r16 ENUMERATED {n1, n2, n4}

[1784] } OPTIONAL -- Need R

[1785] ]],

[1786] [[

[1787] spatialRelationInfo-PDC-r17 SetupRelease { SpatialRelationInfo-PDC-r17} OPTIONAL, -- Need M

[1788] resourceMapping-r17 SEQUENCE {

[1789] startPosition-r17 INTEGER (0..13),

[1790] nrofSymbols-r17 ENUMERATED {n1, n2, n4, n8, n10, n12, n14},

[1791] repetitionFactor-r17 ENUMERATED {n1, n2, n4, n5, n6, n7, n8, n10, n12, n14}

[1792] } OPTIONAL, -- Need R

[1793] partialFreqSounding-r17 SEQUENCE {

[1794] startRBIndexFScaling-r17 CHOICE{

[1795] startRBIndexAndFreqScalingFactor2-r17 INTEGER (0..1),

[1796] startRBIndexAndFreqScalingFactor4-r17 INTEGER (0..3)

[1797] },

[1798] enableStartRBHopping-r17 ENUMERATED {enable} OPTIONAL -- Need R

[1799] } OPTIONAL, -- Need R

[1800] transmissionComb-n8-r17 SEQUENCE {

[1801] combOffset-n8-r17 INTEGER (0..7),

[1802] cyclicShift-n8-r17 INTEGER (0..5)

[1803] } OPTIONAL, -- Need R

[1804] srs-TCI-State-r17 CHOICE {

[1805] srs-UL-TCI-State TCI-UL-StateId-r17,

[1806] srs-DLorJointTCI-State TCI-StateId

[1807] } OPTIONAL -- Need R

[1808] ]],

[1809] [[

[1810] repetitionFactor-v1730 ENUMERATED {n3} OPTIONAL, -- Need R

[1811] srs-DLorJointTCI-State-v1730 SEQUENCE {

[1812] cellAndBWP-r17 ServingCellAndBWP-Id-r17

[1813] } OPTIONAL -- Cond DLorJointTCI-SRS

[1814] ]],

[1815] [[

[1816] nrofSRS-Ports-n8-r18 ENUMERATED {ports8, ports8tdm} OPTIONAL, -- Need R

[1817] combOffsetHopping-r18 SEQUENCE {

[1818] hoppingId-r18 INTEGER (0..1023) OPTIONAL, -- Need R

[1819] hoppingSubset-r18 CHOICE {

[1820] transmissionComb-n4 BIT STRING (SIZE (4)),

[1821] transmissionComb-n8 BIT STRING (SIZE (8))

[1822] } OPTIONAL, -- Need R

[1823] hoppingWithRepetition-r18 ENUMERATED {symbol, repetition} OPTIONAL -- Need R

[1824] } OPTIONAL, -- Need R

[1825] cyclicShiftHopping-r18 SEQUENCE {

[1826] hoppingId-r18 INTEGER (0..1023) OPTIONAL, -- Need R

[1827] hoppingSubset-r18 CHOICE {

[1828] transmissionComb-n2 BIT STRING (SIZE (8)),

[1829] transmissionComb-n4 BIT STRING (SIZE (12)),

[1830] transmissionComb-n8 BIT STRING (SIZE (6))

[1831] } OPTIONAL, -- Need R

[1832] hoppingFinerGranularity-r18 ENUMERATED {enable} OPTIONAL -- Need R

[1833] } OPTIONAL -- Need R

[1834] ]]

[1835] }

[1837] SRS-SpatialRelationInfo::= SEQUENCE {

[1838] servingCellId ServCellIndex OPTIONAL, -- Need S

[1839] referenceSignal CHOICE {

[1840] ssb-Index SSB-Index,

[1841] csi-RS-Index NZP-CSI-RS-ResourceId,

[1842] srs SEQUENCE {

[1843] resourceId SRS-ResourceId,

[1844] uplinkBWP BWP-Id

[1845] }

[1846] }

[1847] }

[1848] SSB-Configuration-r16 ::= SEQUENCE {

[1849] ssb-Freq-r16 ARFCN-ValueNR,

[1850] halfFrameIndex-r16 ENUMERATED {zero, one},

[1851] ssbSubcarrierSpacing-r16 SubcarrierSpacing,

[1852] ssb-Periodicity-r16 ENUMERATED { ms5, ms10, ms20, ms40, ms80, ms160, spare2,spare1} OPTIONAL, -- Need S

[1853] sfn0-Offset-r16 SEQUENCE {

[1854] sfn-Offset-r16 INTEGER (0..1023),

[1855] integerSubframeOffset-r16 INTEGER (0..9) OPTIONAL -- Need R

[1856] } OPTIONAL, -- Need R

[1857] sfn-SSB-Offset-r16 INTEGER (0..15),

[1858] ss-PBCH-BlockPower-r16 INTEGER (-60..50) OPTIONAL -- Cond Pathloss

[1859] }

[1861] SSB-InfoNcell-r16 ::= SEQUENCE {

[1862] physicalCellId-r16 PhysCellId,

[1863] ssb-IndexNcell-r16 SSB-Index OPTIONAL, -- Need S

[1864] ssb-Configuration-r16 SSB-Configuration-r16 OPTIONAL -- Need S

[1865] }

[1868] SRS-ResourceId::= INTEGER (0..maxNrofSRS-Resources-1)

[1869] SRS-PosResourceId-r16::= INTEGER (0..maxNrofSRS-PosResources-1-r16)

[1871] SRS-PeriodicityAndOffset::= CHOICE {

[1872] sl1 NULL,

[1873] sl2 INTEGER(0..1),

[1874] sl4 INTEGER(0..3),

[1875] sl5 INTEGER(0..4),

[1876] sl8 INTEGER(0..7),

[1877] sl10 INTEGER(0..9),

[1878] sl16 INTEGER(0..15),

[1879] sl20 INTEGER(0..19),

[1880] sl32 INTEGER(0..31),

[1881] sl40 INTEGER(0..39),

[1882] sl64 INTEGER(0..63),

[1883] sl80 INTEGER(0..79),

[1884] sl160 INTEGER(0..159),

[1885] sl320 INTEGER(0..319),

[1886] sl640 INTEGER(0..639),

[1887] sl1280 INTEGER(0..1279),

[1888] sl2560 INTEGER(0..2559)

[1889] }

[1890] }

[1892] -- TAG-SRS-CONFIG-STOP

[1893] -- ASN1STOP

[1894] dci-TriggeringPosResourceSetLink: Indicates whether a single DCI triggering SRS positioning resource set is enabled for bandwidth aggregation across all connected carriers.

[1895] tpc-Accumulation: If the field is not present, the UE applies TPC commands through accumulation. If disabled, the UE applies TPC commands without accumulation (applied to the SRS if a separate closed loop is configured for the SRS) (see TS 38.213

[13] , clause 7.3).

[1896] periodicityAndOffset-p, periodicityAndOffset-p-Ext: These are the periodicity and slot offset of this SRS resource. All values ​​are within "number of slots". Value sl1 corresponds to 1 slot of periodicity, and value sl2 corresponds to 2 slots of periodicity. For each periodicity, the corresponding offset is provided as the number of slots. For periodicity sl1, the offset is 0 slots (see TS 38.214

[19] , clause 6.2.1). sl1280 and sl2560 cannot be configured for CLI SRS-RSRP measurements. For SRS-PosResource, the sl20480, sl40960, and sl81920 values ​​cannot be configured with SCS=15kHz, the sl40960 and sl81920 values ​​cannot be configured with SCS=30kHz, and the sl81920 value cannot be configured with SCS=60kHz except when the periodicity is set to 20480ms.

[1897] If periodicityAndOffset-p-Ext exists, periodicityAndOffset-p must be ignored by the UE.

[1898] resourceMapping: OFDM symbol positions of an SRS resource within a slot, including nrofSymbols (number of OFDM symbols), startPosition (value 0 for the last symbol, value 1 for the second-last symbol), and repetitionFactor (see TS 38.214

[19] , Section 6.2.1 and TS 38.211

[16] , Section 6.4.1.4). The configured SRS resource does not extend beyond the slot boundaries. When resourceMapping-r16 is signaled, the UE must ignore resourceMapping(no suffix). When resourceMapping-r17 is signaled, resourceMapping-r16 is not signaled, and the UE ignores resourceMapping(no suffix) and can only configure the value of nrofSymbols as an integer multiple of the configured repetition factor. The network may signal repetitionFactor-v1730 only when resourceMapping-r17 is signaled. When 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 in the validity area. nrofSymbols is the same for all hops when TxHoppingConfig is configured.

[1899] resourceType: Periodicity for semi-permanent and periodic SRS resources and slot offset for non-periodic SRS resources for offset or positioning (see TS 38.214

[19] , Clause 6.2.1). 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 in the valid area.

[1900] sequenceId: This is the sequence ID used to initialize pseudo-random group and sequence hopping (see TS 38.214

[19] , Section 6.2.1). If srs-PosRRC-InactiveValidityAreaPreConfigList or srs-PosRRC-InactiveValidityAreaNonPreConfig is configured, the value of this field applies to all cells in the validity area.

[1901] slotOffset: The slot number offset between the triggering DCI and the actual transfer of this SRS-PosResource. If the field is missing, the UE does not apply the offset (value 0).

[1902] 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] , Section 6.2.1). This parameter does not apply to CLI SRS-RSRP measurements. This field is not configured if unifiedTCI-StateType is configured for the serving cell.

[1903] Alpha: Alpha value for SRS power control (see TS 38.213

[13] , Clause 7.3). If the 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 in the valid area.

[1904] aperiodicSRS-ResourceTriggerList: An additional list of DCI "code points" to which the UE must send SRS according to this SRS resource set configuration (see TS 38.214

[19] , Clause 6). If the field is not included while reconfiguring the SRS-ResourceSet of a resourceType set to aperiodic, the UE retains this value according to Need M. That is, this list is not considered an extension of aperiodicSRS-ResourceTrigger for the purpose of applying the general rules for extension lists in Section 6.1.3.

[1905] aperiodicSRS-ResourceTrigger: This is the DCI "code point" to which the UE must send an SRS based on the configuration of this SRS resource set (see TS 38.214

[19] , clause 6).

[1906] applyIndicatedTCI-State: This field indicates whether the UE applies a first or second "indicated" UL-only TCI or joint TCI to the SRS-ResourceSet as specified in TS 38.214

[19] , Section 6.2.1.

[1907] 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] , Section 6.1.1.2).

[1908] availableSlotOffsetList: Represents a list of up to four different available slot offset values ​​from slot n+k to the slot where a non-periodic SRS resource set is transmitted, where slot n is the slot with the triggering DCI and k is slotOffset (no suffix) as described in Section 6.2.1 of TS 38.214

[19] .

[1909] csi-RS: ID of the CSI-RS resource associated with this SRS resource set (see TS 38.214

[19] , Section 6.1.1.2).

[1910] When set to followUnifiedTCI-StateSRS: enable, for the set of SRS resources, the UE applies the “indicated” UL-only TCI or joint TCI as specified in TS 38.214

[19] , Clause 5.1.5. This parameter can be configured for non-periodic SRS for BM or for SRS of all time-domain operations for codebook, non-codebook, and antenna switching.

[1911] p0: This is the P0 value for SRS power control. The value is in dBm units. Only even values ​​(step size 2) are allowed (see TS 38.213

[13] , Section 7.3). If srs-PosRRC-InactiveValidityAreaPreConfigList or srs-PosRRC-InactiveValidityAreaNonPreConfig is configured, the value of this field applies to all cells in the valid area.

[1912] pathlossReferenceRS: A reference signal used for SRS path loss estimation (e.g., CSI-RS configuration or SS block) (see TS 38.213

[13] , Section 7.3).

[1913] pathlossReferenceRS-Pos: A reference signal used for SRS path loss estimation (e.g., SS block or DL-PRS configuration) (see TS 38.213

[13] , Section 7.3).

[1914] pathlossReferenceRSList: Multiple candidate pathloss reference RS(s) for SRS power control, where one candidate RS can be mapped to an SRS resource set via MAC CE (Section 6.1.3.27 of TS 38.321[3]). The network can configure this field only if pathlossReferenceRS is not configured in the same SRS-ResourceSet.

[1915] resourceType: Time domain behavior of SRS resource configuration, see TS 38.214

[19] , Clause 6.2.1. The network configures SRS resources in the same set of resources with the same time domain behavior in periodic, non-periodic, and semi-permanent SRSs. Non-periodic SRSs do not apply to UEs of RRC_INACTIVE. If srs-PosRRC-InactiveValidityAreaPreConfigList or srs-PosRRC-InactiveValidityAreaNonPreConfig is configured, the value of this field applies to all cells in the validity area.

[1916] slotOffset: The slot number offset between the triggering DCI and the actual transfer of this SRS-ResourceSet. If the field is missing, the UE does not apply the offset (value 0).

[1917] srs-PowerControlAdjustmentStates: Indicates whether hsrs,c(i) = fc(i,1) or hsrs,c(i) = fc(i,2) (if twoPUSCH-PC-AdjustmentStates is set) or a separate close loop is configured for the SRS. This parameter is applicable only to the Uls to which the UE sends PUSCH. If absent or released, the UE applies the sameAs-Fci1 value (see TS 38.213

[13] , Section 7.3).

[1918] srs-ResourceIdList, srs-PosResourceIdList: These are the IDs of the SRS-Resources / SRS-PosResources used in this SRS-ResourceSet / SRS-PosResourceSet. If this SRS-ResourceSet is configured with usage set to codebook, srs-ResourceIdList contains up to 2 entries. If this SRS-ResourceSet is configured with usage set to nonCodebook, srs-ResourceIdList contains up to 4 entries. If srs-PosRRC-InactiveValidityAreaPreConfigList or srs-PosRRC-InactiveValidityAreaNonPreConfig is configured, srs-PosResourceIdList is typically configured across cells within the validity area.

[1919] srs-ResourceSetId, srs-PosResourceSetId: These are the IDs of this resource set. They are 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 across cells within the validity area.

[1920] ssb-IndexServing: Represents the SSB index belonging to the serving cell configured with SRS.

[1921] ssb-Ncell: This field indicates the SSB setting of an adjacent cell.

[1922] symbolType: Configures a valid symbol type for an SRS resource in the SRS resource set. If usage is set to 'antennaSwitching', the network does not configure this field (see TS 38.214, Clause X).

[1923] usage: Indicates whether the SRS resource set is used for beam management, codebook-based or non-codebook-based transmission, or antenna switching. See TS 38.214

[19] , Clause 6.2.1. Reconfiguration between codebook-based transmission and non-codebook-based transmission is not supported.

[1924] physicalCellId: This field specifies the physical cell ID of the NCD-SSB of the serving cell where the SSB configuration is provided, or of an adjacent cell.

[1925] ssb-IndexNcell: This field specifies the index of the SSB for an adjacent cell of the serving cell or NCD-SSB. See TS 38.213

[13] . If this field is missing, the UE determines the ssb-IndexNcell of physicalCellId based on the SSB measurement from the cell.

[1926] ssb-Configuration: This field specifies the overall configuration of the SSB. If this field is missing, the UE obtains the configuration for the SSB from nr-SSB-Config received from the LPP as part of the DL-PRS auxiliary data by using the physicalCellId field to retrieve the corresponding SSB configuration (see TS 37.355

[49] ).

[1927] halfFrameIndex: Indicates whether the SSB is in the first or second half of the frame. A value of 0 indicates the first half, and a value of 1 indicates the second half.

[1928] integerSubframeOffset: Represents the subframe boundary offset of the cell where the SSB is transmitted.

[1929] sfn0-Offset: Represents the time offset of SFN0 slot 0 for the cell for SFN0 slot 0 of the serving cell.

[1930] sfn-Offset: Specifies the SFN offset between the cell where the SSB is transmitted and the serving cell. The offset corresponds to the total number of radio frames calculated from the start of radio frame #0 of the serving cell to the start of the nearest subsequent radio frame #0 of the cell where the SSB is transmitted.

[1931] 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 so that the indicated system frame does not exceed the configured SSB periodicity.

[1932] ssb-Freq: Represents the frequency of the SSB.

[1933] ss-PBCH-BlockPower: Average EPRE of resource elements in dBm that transmit auxiliary synchronization signals used by NW for SSB transmission, TS 38.213

[13] , see Clause 7.

[1934] ssb-Periodicity: Indicates the periodicity of the SSB. If the field is missing, the UE applies the ms5 value. (See TS 38.213

[13] , Clause 4.1)

[1935] ssbSubcarrierSpacing: Subcarrier spacing of the SSB.

[1937] IE Uplink-PowerControl is used to configure UE-specific power control parameters for PUSCH, PUCCH, and SRS.

[1938] Uplink-PowerControl information element

[1939] -- ASN1START

[1940] -- TAG-UPLINK-POWERCONTROL-START

[1942] Uplink-powerControl-r17 ::= SEQUENCE {

[1943] ul-powercontrolId-r17 Uplink-powerControlId-r17,

[1944] p0AlphaSetforPUSCH-r17 P0AlphaSet-r17 OPTIONAL, -- Need R

[1945] p0AlphaSetforPUCCH-r17 P0AlphaSet-r17 OPTIONAL, -- Need R

[1946] p0AlphaSetforSRS-r17 P0AlphaSet-r17 OPTIONAL -- Need R

[1947] }

[1949] P0AlphaSet-r17::= SEQUENCE {

[1950] p0-r17 INTEGER (-16..15) OPTIONAL, -- Need R

[1951] alpha-r17 Alpha OPTIONAL, -- Need S

[1952] closedLoopIndex-r17 ENUMERATED { i0, i1}

[1953] }

[1955] Uplink-powerControlId-r17::= INTEGER(1.. maxUL-TCI-r17)

[1957] Uplink-powerControl-v19xy ::= SEQUENCE {

[1958] p0AlphaSetforPUSCH-SBFD-r19 P0AlphaSet-r17 OPTIONAL, -- Need R

[1959] p0AlphaSetforPUCCH-SBFD-r19 P0AlphaSet-r17 OPTIONAL, -- Need R

[1960] p0AlphaSetforSRS-SBFD-r19 P0AlphaSet-r17 OPTIONAL -- Need R

[1961] }

[1963] -- TAG-UPLINK-POWERCONTROL-STOP

[1964] -- ASN1STOP

[1965] p0AlphaSetforPUSCH, p0AlphaSetforPUCCH, p0AlphaSetforSRS: Configures power control parameters for PUSCH, PUCCH, and SRS (see TS 38.213

[13] , Section 7.2). If p0AlphaSetforPUSCH has no field alpha, the UE applies a value of 1 for PUSCH power control. If p0AlphaSetforSRS has no field alpha, the UE applies a value of 1 for SRS power control. p0AlphaSetForPUCCH has no field alpha (not used).

[1966] p0AlphaSetforPUSCH-SBFD, p0AlphaSetforPUCCH-SBFD, p0AlphaSetforSRS-SBFD: Configure separate UL power control parameters for PUSCH, PUCCH, and SRS transmissions in the SBFD symbol (see TS 38.213

[13] , Section x).

[1968] If the UE is provided with tdd-UL-DL-ConfigurationCommon for the cell, the PRACH occasion for the cell in the PRACH slot is valid in the following cases.

[1969] Only within the UL symbol or

[1970] It exists only within an SBFD symbol containing one or more SBFD symbols marked as downlinked by tdd-UL-DL-ConfigurationCommon, and only within an RB in both the active UL BWP and UL subband if the UE provides sbfd-RACHSingleConfig or sbfd-RACHDualConfig, or starts at an SBFD symbol and ends at a non-SBFD symbol, and is in an RB in both the active UL BWP and UL subband if the UE provides sbfd-RACHDualConfig and sbfd-RACHDualConfig-ValidROAcrossSymbolTypes.

[1971] >: It does not precede the SS / PBCH block in the PRACH slot, and starts the minimum number of symbols after the last downlink symbol and the minimum number of N_gap symbols after the last N_gapSS / PBCH block symbol, where Ngap is given in Table 8.1-2 and channelAccessMode = "semiStatic", and does not overlap with a consecutive set of symbols before the next channel occupancy time, which should not have any transmissions, begins, as described in [15, TS 37.213].

[1972] >>: The candidate SS / PBCH block index for the SS / PBCH block corresponds to the SS / PBCH block index provided by SIB1 or ServingCellConfigCommon or ssb-PositionsInBurst of SSB-MTC-AdditionalPCI, which corresponds to the cell as described in Section 4.1.

[1973] The downlink or flexible symbol provided by tdd-UL-DL-ConfigurationCommon may include a UL subband provided by ulSubbandlocationAndBandwidth, a first DL subband provided by firstdlSubbandlocationAndBandwidth, and additionally, for the SCS configuration of any configured UL BWP or DL ​​BWP provided by μscs-SpecificCarrierList, it may include a second DL subband provided by seconddlSubbandlocationAndBandwidth. Then, the downlink or flexible symbol is called an SBFD symbol. Otherwise, it is called a non-SBFD symbol. The uplink symbol is a non-SBFD symbol. An SBFD symbol or a non-SBFD symbol provided by tdd-UL-DL-ConfigurationCommon cannot be changed to a non-SBFD symbol or an SBFD symbol, respectively, by other information. The UE is not provided with a coresetPoolIndex and is not configured to receive PDSCH according to one or more TCI states mapped to a single TCI code point [6, TS 38.214] for a serving cell that is provided with SBFD symbols.

[1974] The SBFD symbol starts at the first slot provided by SBFD-StartingSlotIndex, starts at the first symbol of the first slot provided by SBFD-StartingSymbolIndex, ends at the second slot provided by SBFD-EndingSlotIndex, and ends at the second symbol of the second slot provided by SBFD-EndingSymbolIndex. The SBFD symbol may be provided as either pattern1 or pattern2 (if provided). The construction period for the SBFD symbol is P msec if only pattern1 is provided, or P + P2 if pattern2 is additionally provided.

[1976] Except for PRACH transmission on a PRACH occasion determined based on the second RACH configuration provided by sbfd-RACHDualConfig as described in Section 8, the UE transmits or receives physical channels or signals only at SBFD symbols or only at non-SBFD symbols.

[1977] When a UE is provided with sbfd-Configuration2-Transmission, the UE can perform the following:

[1978] >: Transmit the first PUCCH or PUSCH or the first repetition of PUSCH as a non-SBFD symbol, or receive the first PDSCH or the first repetition of PDSCH, and

[1979] Transmit a second PUCCH or PUSCH or a second repetition of PUSCH with an SBFD symbol, or receive a second PDSCH or a second repetition of PDSCH.

[1980] If UE is not provided, sbfd-Configuration2-Transmission

[1981] In the case of a PUCCH or PUSCH transmission with repetition or a PDSCH reception with repetition, if the first repetition is in an SBFD symbol or a non-SBFD symbol, the remaining repetitions are also in an SBFD symbol or a non-SBFD symbol, respectively.

[1982] In the case of a Type 2 CG PUSCH transmission, or a PUSCH transmission via an SP-CSI report, or an SPS PDSCH reception, if the first transmission or reception after the latest activation is an SBFD symbol or a non-SBFD symbol, the remaining transmissions or receptions associated with the latest activation also exist in SBFD symbols or non-SBFD symbols, respectively, and each

[1983] For a Type 1 CG PUSCH, or a PUCCH transmission with an SP-CSI report, or a PUCCH with an SR, [LRR, UEIRI], or a P-CSI or SRS, each respective transmission is either in SBFD symbols only or in non-SBFD symbols only, as indicated by the respective configuration [12, TS 38.331].

[1984] Except for SBFD symbols and 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 from RBs in both the active DL BWP and DL subband(s), respectively. The UE does not transmit with SBFD symbols indicating the presence of an SS / PBCH block within the active DL BWP by ssb-PositionsInBurst or ServingCellConfigCommon [or NonCellDefiningSSB] of SIB1.

[1986] DCI format 1_0 is used for scheduling PDSCH in a single DL cell.

[1987] The following information is transmitted via DCI format 1_0 with a CRC scrambled by C-RNTI, CS-RNTI, or MCS-C-RNTI.

[1988] >: DCI format identifier - 1 bit

[1989] >>: The value of this bit field is always set to 1, which indicates the DL DCI format.

[1990] >: Frequency Domain Resource Allocation - n bits

[1991] If the CRC of DCI format 1_0 is scrambled by C-RNTI and the "Frequency domain resource assignment" field is all 1, DCI format 1_0 is for random access procedures initiated by the PDCCH sequence, and all remaining fields are set as follows.

[1992] >: Random Access Preamble Index - 6 bits

[1993] >: UL / SUL Indicator - 1 bit.

[1994] >>: If the cell indicator field is missing or the cell indicator field indicates a serving cell, if the values ​​of the "random access preamble index" are not all zero and the UE is configured as a secondary uplink in the ServingCellConfig within the cell, this field indicates the UL carrier within the cell to transmit PRACH.

[1995] >>: If the cell indicator field indicates a candidate cell, and the values ​​of the "random access preamble index" are not all zero, and the UE is configured with ltm-EarlyUL-SyncConfigSUL in LTM-Candidate for the candidate cell, this field indicates the UL carrier to transmit PRACH from the candidate cell.

[1996] Otherwise, this field is reserved.

[1997] >: SS / PBCH Index - 6 bits. If the values ​​of the "Random Access Preamble Index" are all non-zero, this field indicates the SS / PBCH used to determine the RACH status for a PRACH transfer. Otherwise, this field is reserved.

[1998] >: PRACH Mask Index - 4 bits. If the values ​​of the "Random Access Preamble Index" are all non-zero, this field indicates the RACH situation associated with the SS / PBCH indicated by the "SS / PBCH Index" for the PRACH transfer in accordance with provision 5.1.1 of [8, TS38.321]. Otherwise, this field is reserved.

[1999] >: Cell Indicator - m bits representing the cell for the corresponding PRACH transmission if the UE is configured with the upper layer parameter EarlyUL-SyncConfig, where 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 identities configured by ltm-CandidateId, and bit field index 1 is mapped to the candidate cell with the smallest candidate identity.

[2000] >: PRACH associated indicator - 0 or 1 bit

[2001] >>: 1 bit if tag2-Id is provided to the UE and coresetPoolIndex is not provided to the UE, or if a coresetPoolIndex with a value of 0 is provided for the first CORESET and a coresetPoolIndex with a value of 1 is provided for the second CORESET. This field is reserved if the cell indicated in the Cell indicator field is a candidate cell.

[2002] >>>: 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.

[2003] >>>: This field indicates the PL-RS for PRACH transmission when the terminal does not provide SSB-MTC-AdditionalPCI. Bit field index 0 of this field maps to the DL RS where the DM-RS of the PDCCH order is quasi-collocated, and bit field index 1 of this field maps to the SS / PBCH indicated by the SS / PBCH index field in this DCI format.

[2004] Otherwise, it is 0 bits.

[2005] >: PRACH Retransmission Indicator - 0 or 1 bit

[2006] >>: 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.

[2007] Otherwise, it is 0 bits.

[2008] >: RACH occasion indicator - 0 or 1 bit

[2009] >>: 1 bit if the 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 the RACH situation for a PRACH transmission. Otherwise, this field is reserved.

[2010] Otherwise, it is 0 bits.

[2011] >>: 0: The RACH opportunity for PRACH transmission starts in the first PRACH case.

[2012] >>: 1: The RACH opportunity for PRACH transmission starts in the second PRACH case.

[2014] 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,

[2015] If the UE is not configured with sbfd-Config2-Reception, the UE receives only PDSCH of valid symbol types, where,

[2016] >>: For PDSCH receptions across different slots scheduled without the corresponding PDCCH transmission using sps-Config and enabled by DCI format 1_0, 1_1, or 1_2, the valid symbol type is the symbol type at the time of the first PDSCH reception associated with the enabling DCI, and

[2017] >>: In the case of PDSCH receptions spanning different slots scheduled by a DCI using pdsch-TimeDomainAllocationListForMultiPDSCH, 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 time indicated by the scheduling DCI. The UE does not expect the first PDSCH reception time indicated by the scheduling DCI to map to both SBFD symbols and non-SBFD symbols.

[2018] Otherwise, the UE receives PDSCH in SBFD symbols and non-SBFD symbols after applying collision handling in Section 11.1 of [6, TS 38.213].

[2019] If the UE is configured with sbfd-Config2-Reception, only the allocated PRBs in both the active DL BWP and DL subband are scheduled without their corresponding PDCCH transmissions using sps-Config and are used for PDSCH reception of SBFD symbols across other slots enabled by or scheduled by DCI formats 1_0, 1_1, or 1_2. pdsch-TimeDomainAllocationListForMultiPDSCH: One or more rows contain multiple SLIVs, use pdsch-AggregationFactor, use repetitionNumber, or contain these.

[2020] If the UE is configured with SBFD symbols, only the assigned PRBs located in both the active DL BWP and the DL sub-band are used for receiving a single PDSCH from the SBFD symbol(s) within the slot, or for receiving a PDSCH through another slot where the valid symbol type is an SBFD symbol (Clause 5.1.2.1a) and the UE is not expected to be assigned as an RBG for a PDSCH completely outside the PRBs located in both the active DL BWP and the DL sub-band.

[2021] For PDSCH reception in SBFD symbols, DM-RS sequence mapping applies only to assigned PRBs in both the active DL BWP and DL subband(s).

[2024] 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 an associated CSI-RS.

[2025] For a Type 1 PUSCH transfer with a configured grant,

[2026] 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, where symbolType corresponds to the same symbol type as the valid symbol type of the PUSCH transmission.

[2027] If the UE is configured with sbfd-Config2-Transmission, srs-ResourceIndicator can be applied 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 in non-SBFD symbols, precodingAndNumberOfLayers corresponds to SRS resources identified by SRI in an SRS-ResourceSet where symbolType is set to 'non-sbfd'.

[2028] In the case of a Type 2 PUSCH transfer with a configured grant, or a PUSCH transfer traversing SBFD symbols and non-SBFD symbols scheduled in DCI format 0_1, 0_2, or 0_3,

[2029] If the UE is not configured with sbfd-Config2-Transmission, the SRI specified 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, where the SRS resource precedes the PDCCH carrying the SRI. If txConfig is set to 'codebook', the precoding information and layer number (TPMI) field of the DCI corresponds to 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.

[2030] If the UE is configured with sbfd-Config2-Transmission, the SRS resource descriptor can be applied 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 symbols, where the SRS resource precedes the PDCCH carrying 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 symbols, where the SRS resource precedes the PDCCH carrying the SRI. When txConfig is set to 'codebook', for PUSCH transmission in SBFD symbols, the Precoding Information and Layer Count (TPMI) field in the DCI corresponds to the SRS resource identified by SRI in the SRS-ResourceSet where symbolType is set to 'sbfd'. For PUSCH transmission in non-SBFD symbols, the Precoding Information and Layer Count (TPMI) field in the DCI corresponds to the SRS resource identified by SRI in the SRS-ResourceSet where symbolType is set to 'non-sbfd'. If only a single SRS resource is configured in both the SRS resource set where symbolType is set to 'non-sbfd' and the SRS resource set where symbolType is set to 'sbfd', the SRI field is not present in the DCI.

[2031] For a non-repeating PUSCH transmission scheduled by DCI format 0_1, 0_2, or 0_3, 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, where symbolType corresponds to the same symbol type as the PUSCH transmission, and the SRS resource precedes the PDCCH carrying the SRI. If txConfig is set to 'codebook', the DCI precoding information and layer number (TPMI) field corresponds to the SRS resource identified by the SRI in the SRS-ResourceSet, where symbolType corresponds to the same symbol type as the PUSCH transmission.

[2033] For a UE scheduled for a PUSCH transmission time across SBFD symbols and non-SBFD symbols in different slots,

[2034] If the UE is not configured with sbfd-Config2-Transmission

[2035] >>: The UE transmits only PUSCH of valid symbol types.

[2036] >>>: For a Type 1 PUSCH transfer with a configured grant, the valid symbol type is provided by the symbolType in rrc-ConfiguredUplinkGrant of ConfiguredGrantConfig.

[2037] >>>: For a Type 2 PUSCH transmission with a configured grant 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 time associated with the activating DCI. For a Type 2 PUSCH transmission with a configured grant of PUSCH iteration type B, the valid symbol type is the symbol type of the first actual iteration associated with the activating DCI.

[2038] For PUSCH transmissions scheduled in DCI formats 0_1, 0_2, 0_3, 0_0 using a CRC scrambled by TC-RNTI, a RAR UL grant, or a fallback RAR UL grant, the valid symbol type is the symbol type of the first PUSCH transmission time indicated by the scheduling DCI, the RAR UL grant, or the fallback RAR UL grant. For PUSCH repeat type B scheduled by DCI formats 0_1 or 0_2, the valid symbol type is the symbol type of the first actual repeat case indicated by the scheduling DCI. The UE does not expect the first PUSCH transmission time indicated by the scheduling DCI, the RAR UL grant, or the fallback RAR UL grant to map to both SBFD symbols and non-SBFD symbols, except for PUSCH repeat type B.

[2039] >>: For PUSCH iteration type A scheduled by DCI format 0_1, 0_2, or 0_3 when AvailableSlotCounting is enabled and K>1 or TB processing across multiple slots, or for PUSCH iteration type A scheduled by DCI format 0_0 using a CRC scrambled by TC-RNTI, RAR UL grant, or alternative RAR UL grant,

[2040] Slots containing transmission situations not of valid symbol types are not included in the number of N·K slots.

[2041] >>>: If the valid symbol type is an SBFD symbol, the slot is included in the slot count if all symbols assigned at the time of transfer in the N·K slot are SBFD symbols and do not contain symbols from an SS / PBCH block with an index provided by ssb-PositionsInBurst.

[2042] >>>: If the valid symbol type is a non-SBFD symbol, and PUSCH repeat type A is scheduled by DCI format 0_0 with a CRC scrambled by TC-RNTI, RAR UL grant, or alternative RAR UL grant, and the symbols assigned to the transfer situation of the N·K slot are all non-SBFD symbols and do not include DL symbols marked as tdd-UL-DL-ConfigurationCommon or symbols of an SS / PBCH block with an index provided by ssb-PositionsInBurst, the slot is included in the slot count. Otherwise, if the symbols assigned at the time of transfer of the N·K slot are all non-SBFD symbols and do not include DL symbols marked as tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated (if provided) or symbols of an SS / PBCH block with an index provided by ssb-PositionsInBurst, the slot is counted in the slot count.

[2043] Otherwise, the UE applies collision handling in Section 11.1 of [6, TS 38.213] and then transmits PUSCH occurrences with SBFD symbols and non-SBFD symbols. When AvailableSlotCounting is enabled and there are K>1 or TB processing in multiple slots, for PUSCH iteration type A scheduled by DCI format 0_1, 0_2, or 0_3, if the symbols assigned to the slot's transfer opportunity (situation) are all SBFD symbols and do not contain symbols of an SS / PBCH block with an index provided by ssb-PositionsInBurst, N·K slots are counted in the slot count, or if the symbols assigned at the time of transfer of the slot are all non-SBFD symbols and do not contain DL symbols marked as tdd-UL-DL-ConfigurationCommon or tdd-UL-DL-ConfigurationDedicated (if provided) or symbols of an SS / PBCH block with an index provided by ssb-PositionsInBurst.

[2045] For a UE scheduled for a PUSCH transmission time consisting of SBFD symbols and mapped to SBFD symbols and non-SBFD symbols within a slot,

[2046] If the PUSCH transfer time is scheduled as a PUSCH iteration type A where AvailableSlotCounting is enabled and K>1 or TB processing is possible across multiple slots, the slots are not included in the number of N·K slots.

[2047] If the PUSCH transmission situation is a nominal repetition for PUSCH repetition type B, the nominal repetition is divided into actual repetitions around the boundary between SBFD symbols and non-SBFD symbols.

[2048] Otherwise, the UE does not transmit the PUSCH transmission time.

[2050] If the UE is set to SBFD symbols,

[2051] Only resource blocks in both the active UL BWP and UL subband are used for PUSCH transmission of SBFD symbols. For a single PUSCH transmission of SBFD symbol(s) within a slot, or for a PUSCH transmission through another slot where the valid symbol type is SBFD symbol (Clause 5.1.2.1), the UE does not expect to be allocated an RBG for PUSCH in SBFD symbol(s) that are entirely outside the PRBs in both the active UL BWP and UL subband.

[2052] >: [If the UE is configured with sbfd-Config2-Transmission, and the UE is scheduled for a PUSCH transmission time traversing SBFD and non-SBFD symbols in different slots, or if the UE is scheduled for a PUSCH transmission time traversing SBFD and non-SBFD symbols within a slot for PUSCH repeat type B, the resource allocation of type 0 for the PUSCH transmission time in non-SBFD symbols is provided by the bitmap, and meanwhile, for each RBG allocated for the PUSCH transmission situation in SBFD symbols,

[2053] >>: The RBG size is the same as the RBG size for the PUSCH transmission situation in non-SBFD symbols.

[2054] >>: The starting resource block of the RBG is defined as follows.

[2055] >>>: Starting PRB index of the PRB in both the active UL BWP and the UL subband based on the start of the active UL BWP,

[2056] >>>: RBG's starting PRB index.

[2057] >>>: Number of PRBs in both active UL BWP and UL subband,

[2058] - The UE does not expect the PRBs for PUSCH transmission within the SBFD symbol to overlap with PRBs outside the PRBs within the active UL BWP and UL subband.

[2060] For SRS resources of the SRS resource set provided in srs-ResourceSetToAddModList and srs-ResourceSetToAddModListDCI-0-2 (symbolType set to 'sbfd')

[2061] For periodic or semi-permanent SRS resources, the UE is expected to transmit the SRS only as SBFD symbols, and

[2062] For non-periodic SRS resources and when availableSlotOffsetList is not provided, the UE is not expected to be instructed to transmit SRS on non-SBFD symbols, and

[2063] For non-periodic SRS resources, when availableSlotOffsetList is provided, the available slots are slots consisting of SBFD symbols for time domain positions for all SRS resources in the resource set, which trigger PDCCH and satisfy the minimum timing requirements between all SRS resources in the resource set.

[2064] For SRS resources of the SRS resource set provided in srs-ResourceSetToAddModList and srs-ResourceSetToAddModListDCI-0-2 (where symbolType is set to 'non-sbfd')

[2065] For periodic or semi-permanent SRS resources, the UE is expected to transmit only the SRSs in non-SBFD symbols, and

[2066] For non-periodic SRS resources and when availableSlotOffsetList is not provided, the UE does not expect to be instructed to transmit SRS in SBFD symbols, and

[2067] For non-periodic SRS resources, the available slot is a slot that satisfies the minimum timing requirements between all SRS resources in the resource set and triggering a UL or flexible symbol and PDCCH that is not composed of SBFD symbols for time domain positions for all SRS resources in the resource set.

[2068] If 'codebook', 'noncodebook', or 'beamManagement' is used identically, this is the number of SRS resources in the SRS resource set where symbolType is set to 'sbfd' for the SRS resource set provided in srs-ResourceSetToAddModList or srs-ResourceSetToAddModListDCI-0-2-SBFD. This is the same as the number of SRS resources in the SRS resource set where symbolType is set to 'non-sbfd'.

[2069] For SRS resource sets configured in srs-ResourceSetToAddModList and srs-ResourceSetToAddModListDCI-0-2 with symbolType configured,

[2070] If the usage of the upper layer parameter of SRS-ResourceSet is set to 'noncodebook', the UE expects a single SRS port for each configured SRS resource.

[2071] When the parent layer parameter of an SRS-ResourceSet is set to 'codebook', the number of SRS ports is the same for all SRS resources in an SRS-ResourceSet with symbolType set to 'non-sbfd', except when the parent layer parameter ul-FullPowerTransmission is set to 'fullpowerMode2' and symbolType is set to 'sbfd' in SRS-ResourceSet(s). When the parent layer parameter ul-FullPowerTransmission is set to 'fullpowerMode2', the number of SRS ports for SRS resources is the same for SRS resources with the same corresponding SRI value in an SRS-ResourceSet with symbolType set to 'non-sbfd' and an SRS-ResourceSet with symbolType set to 'sbfd'.

[2072] RO type

[2073] The following two types of RO are used.

[2074] There are the first PRACH opportunity (occasion), RO-1, legacy-RO, RO-1, and the second PRACH opportunity, SBFD-RO, additional-RO, RO-2.

[2075] First PRACH opportunity, RO-1, legacy-RO, and RO-1 are used interchangeably.

[2076] The second PRACH opportunity, SBFD-RO, additional-RO, and RO-2 are used interchangeably.

[2077] RO-1 is set in Situation-1 or Situation-2.

[2078] RO-1 is set by RACH-ConfigCommon-1.

[2079] RO-1 contains only Symbol-1.

[2080] RO-1 is set in PRB-1.

[2081] RO-2 is set in situation-2.

[2082] RO-2 is set by RACH-ConfigCommon-1 (in RACH configuration option 1) or RACH-ConfigCommon-2 (in RACH configuration option 2).

[2083] RO-2 includes only Symbol-2.

[2084] RO-2 is configured in PRB-2.

[2085] Situation Classification

[2086] Situation 1: Scenario where SBFD-RACH is not configured

[2087] This refers to the case where neither sbfd-RACHDualConfig nor sbfd-RACHSingleConfig is set in BWP-UplinkCommon of the active uplink bandwidth portion (active UL BWP). This indicates the default RACH operation mode where the Sub-Band Full Duplex (SBFD) function is not enabled.

[2088] Situation 2: SBFD-RACH Configuration Scenario

[2089] This occurs when at least one of the following conditions is met in the BWP-UplinkCommon of the active UL BWP.

[2090] This is the case where at least one sbfd-RACHSingleConfig is set or at least one sbfd-RACHDualConfig is set.

[2091] This indicates an advanced RACH operation mode that supports subband full-duplex functionality.

[2092] RACH Common Configuration Types

[2093] RACH-ConfigCommon-1 (E3000)

[2094] This setting includes the following.

[2095] The RACH-ConfigCommon of the rach-ConfigCommon field (SetupRelease structure) and / or the RACH-ConfigCommon of the rach-ConfigCommon-r17 field are included.

[2096] This represents the standard RACH setting parameters used in the existing operation mode.

[2097] RACH-ConfigCommon-2 (E4000)

[2098] This setting means the following.

[2099] It refers to RACH-ConfigCommon within SBFD-RACH-DualConfig-r19.

[2100] This is specifically designed for dual setup scenarios in subband full-duplex operation and includes RACH parameters optimized for SBFD environments.

[2101] Symbol Classification

[2102] Symbol-1: Non-SBFD symbol

[2103] Non-SBFD symbols are defined as symbols that satisfy the following conditions.

[2104] It is a symbol that is indicated as uplink or flexible by tdd-UL-DL-ConfigurationCommon and is not indicated as SBFD by tdd-UL-DL-ConfigurationCommon.

[2105] These symbols are used for traditional uplink transmission and follow standard TDD configuration rules without SBFD operation.

[2106] Symbol-2: SBFD Symbol

[2107] An SBFD symbol is defined as a symbol that satisfies the following conditions.

[2108] It is a symbol that is indicated as downlink or flexible by tdd-UL-DL-ConfigurationCommon and simultaneously indicated as SBFD by tdd-UL-DL-ConfigurationCommon.

[2109] These symbols enable subband full-duplex operation, allowing uplink and downlink transmission to occur simultaneously in different frequency subbands.

[2110] Definition of Physical Resource Blocks (PRB) and Rach Opportunities (RO)

[2111] PRB-1 and RO-1 settings

[2112] PRB-1 includes physical resource blocks that satisfy the following criteria.

[2113] These are resource blocks located within an active UL BWP and associated with a symbol set that consists entirely of non-SBFD symbols.

[2114] RACH opportunity type 1 (RO-1) is configured in this symbol set. RO-1 represents a traditional RACH opportunity that can transmit a random access preamble using existing uplink resources without SBFD operation.

[2115] PRB-2 and RO-2 settings

[2116] PRB-2 includes physical resource blocks that satisfy the following conditions.

[2117] It is located within both the active UL BWP and the UL subband and is associated with a symbol set that satisfies at least one of the following criteria.

[2118] All symbols are SBFD symbols and the set contains at least one SBFD symbol directed downlinked by tdd-UL-DL-ConfigurationCommon, or the symbol set starts with an SBFD symbol and ends with a non-SBFD symbol.

[2119] RACH opportunity type 2 (RO-2) is configured in this symbol set. RO-2 represents a RACH opportunity with SBFD enabled, where the random access procedure can utilize subband full-duplex capabilities, allowing for more flexible and efficient use of radio resources in scenarios where simultaneous uplink and downlink operations are advantageous.

[2120] RO-1 is configured only by RACH-ConfigCommon-1.

[2121] RO-2 is set by RACH-ConfigCommon-1 if sbfd-RACHSingleConfig is set for the corresponding rach-ConfigCommon-r17 field.

[2122] RO-2 is set by RACH-ConfigCommon-2 when RACH-ConfigCommon is set by the sbfd-RACHDualConfig field for the corresponding rach-ConfigCommon-r17 field.

[2123] If a symbol is not specified as an SBFD symbol, that symbol is a non-SBFD symbol.

[2124] Before starting a physical random access procedure, Layer 1 may receive instructions from an upper layer to perform the random access procedure using the following.

[2125] Each first PRACH opportunity is used that includes only the symbols designated as uplink or variable by tdd-UL-DL-ConfigurationCommon and considered as uplink for random access procedures, or a second PRACH opportunity is used that starts at SBFD symbols and ends at non-SBFD symbols, if sbfd-RACHSingleConfig or sbfd-RACHDualConfig is provided to the UE within RBs in both active UL BWP and UL subband and sbfd-RACHDualConfig is provided, if associated only with SBFD symbols including at least one SBFD symbol designated as downlink by tdd-UL-DL-ConfigurationCommon, or if sbfd-RACHDualConfig and sbfd-RACHDualConfig-ValidROAcrossSymbolTypes are provided to the UE.

[2126] 'additional-ROs' are defined as follows.

[2127] For RACH configuration option 1, additional-ROs include ROs of SBFD symbols set as downlinks by tdd-UL-DL-ConfigurationCommon and ROs spanning SBFD symbols set as downlinks by tdd-UL-DL-ConfigurationCommon and variably set SBFD symbols.

[2128] For RACH configuration option 2, additional-ROs are ROs set by additional RACH configuration.

[2129] For RACH configuration option 2, additional-RO is valid in the following cases.

[2130] This is a case where it is configured to be valid if it is within SBFD symbols or if the network starts at an SBFD symbol and ends at a non-SBFD symbol within the same slot or across different slots.

[2131] It must start after at least the Ngap symbol following the last downlink non-SBFD symbol.

[2132] It must start after at least one Ngap symbol after the latest SSB.

[2133] It must not overlap with the SSB in the time domain.

[2134] RO is set by various parameters of RACH-ConfigCommon (e.g., prach configuration index and msg1-frequency-start, msg1-FDM, etc.). RO is associated with a random access resource set if FeatureCombinationPreambles associated with the random access resource set are included in the RACH-ConfigCommon that sets the RO.

[2135] A random access resource set (featureCombinationPreambles) is associated with RO-2 if the FeatureCombinationPreambles associated with that random access resource set are included in the RACH-ConfigCommon that sets RO-2. The RACH-ConfigCommon that sets RO-2 is a specific RACH-ConfigCommon-1 (where RACH Configuration 1 applies) or a specific RACH-ConfigCommon-2 (where RACH Configuration 2 applies).

[2136] RO-2 is set by RACH-ConfigCommon-1 if sbfd-RACHSingleConfig is set for the corresponding rach-ConfigCommon-r17.

[2137] RO-2 is set by RACH-ConfigCommon-2 if sbfd-RACHDualConfig is set for the corresponding rach-ConfigCommon-r17.

[2138] Figure 33 shows a sequence for a successful random access operation.

[2139] In S100, the UE receives system information.

[2140] In S200, the UE triggers a random access procedure.

[2141] In S300, the UE selects the uplink.

[2142] In the S400, the UE selects the RO type.

[2143] In S500, the UE performs SOP1b for selecting a random access resource set.

[2144] In S600, the UE performs SOP2 for selecting a random access resource for preamble transmission.

[2145] In S700, the UE performs SOP3 for preamble transmission.

[2146] In S800, the UE performs SOP4 for receiving random access responses.

[2147] In S900, the UE performs Msg 3 transmission based on the RAR's UL grant.

[2148] In S1000, the UE performs SOP5 for competition resolution.

[2149] When a specific MAC PDU or downlink allocation is received, if the contention is considered successful, the UE sends a HARQ ACK to PUCCH.

[2150] If the contention resolution is the result of the PRACH transmission in RO-1, the PUCCH transmission is associated with the PRACH transmission in RO-1.

[2151] If the contention resolution is the result of the PRACH transmission in RO-2, the PUCCH transmission is associated with the PRACH transmission in RO-2.

[2152] If the PUCCH transmission is associated with the PRACH transmission in RO-1, the PUCCH transmission is performed in PRB-1 of Symbol-1.

[2153] If the PUCCH transmission is associated with the PRACH transmission in RO-2, the PUCCH transmission is performed in PRB-2 of Symbol-2.

[2154] Figure 34 shows a sequence for a successful random access operation.

[2155] In S100, the UE receives system information.

[2156] In S200, the UE triggers a random access procedure.

[2157] In S300, the UE selects the uplink.

[2158] In the S400, the UE selects the RO type.

[2159] In S500, the UE performs SOP1b for selecting a random access resource set.

[2160] In S600, the UE performs SOP2 for selecting a random access resource for preamble transmission.

[2161] In S700, the UE performs SOP3 for preamble transmission.

[2162] If RAR is not received, the UE increments PREAMBLE_TRANSMISSION_COUNTER by 1.

[2163] In S1100, the UE compares PREAMBLE_TRANSMISSION_COUNTER with preambleTransMaxRO-Type. If PREAMBLE_TRANSMISSION_COUNTER is less than preambleTransMaxRO-Type + 1, the UE retains the current RO_TYPE and performs the appropriate action for preamble retransmission.

[2164] In S1200, the UE performs SOP2 for selecting a random access resource for preamble transmission.

[2165] In S1300, the UE performs SOP3 for preamble transmission.

[2166] If RAR is not received, the UE increments PREAMBLE_TRANSMISSION_COUNTER by 1.

[2167] In S1400, the UE compares PREAMBLE_TRANSMISSION_COUNTER with preambleTransMaxRO-Type. If PREAMBLE_TRANSMISSION_COUNTER is equal to preambleTransMaxRO-Type + 1, the UE decides to change RO_TYPE and performs the appropriate action for preamble retransmission.

[2168] In S1500, the UE switches the RO type.

[2169] In S1600, the UE performs SOP1b for selecting a random access resource set.

[2170] In S1700, the UE performs SOP2 for selecting a random access resource for preamble transmission.

[2171] In S1800, the UE performs SOP3 for preamble transmission.

[2172] The UE can perform preamble retransmission until a RAR is received or PREAMBLE_TRANSMISSION_COUNT becomes equal to preambleTransMax.

[2173] Random access procedure

[2174] Random access procedures are initiated by the PDCCH command MAC object itself or by an RRC for an event according to TS 38.300. At any given time, only one random access procedure is in progress on a MAC object. MAC objects and UEs are used interchangeably.

[2175] When the random access procedure starts, the UE selects a random access resource set as specified in SOP1b and initializes the following parameters for the random access procedure according to the values ​​set by RRC for the selected random access resource set.

[2176] prach-ConfigurationIndex is a set of available PRACH opportunities for the transmission of a random access preamble to Msg1. This also applies to MSGA PRACH when PRACH opportunities are shared between 2-stage and 4-stage RA types.

[2177] preambleReceivedTargetPower is the initial random access preamble power for a 4-stage RA type.

[2178] rsrp-ThresholdSSB is the RSRP threshold for SSB selection for the 4-stage RA type. When a random access procedure is initiated for beam failure recovery, rsrp-ThresholdSSB used for SSB selection within candidateBeamRSList refers to rsrp-ThresholdSSB in BeamFailureRecoveryConfig IE.

[2179] rsrp-ThresholdSSB-SUL is the RSRP threshold for selection between NUL carriers and SUL carriers.

[2180] rsrp-ThresholdMsg1-RepetitionNum2 is the RSRP threshold for Msg1 repetitions with a repetition count of 2 (see SOP1b).

[2181] rsrp-ThresholdMsg1-RepetitionNum4 is the RSRP threshold for Msg1 repetitions with a repetition count of 4 (see SOP1b).

[2182] rsrp-ThresholdMsg1-RepetitionNum8 is the RSRP threshold for Msg1 repetitions with a repetition count of 8 (see SOP1b).

[2183] rsrp-ThresholdMsg3 is the RSRP threshold for Msg3 iterations (see SOP1b).

[2184] sbfd-RSRP-ThresholdRO-Type is an RSRP threshold for initial RO type selection between SBFD RO and non-SBFD RO in a competition-based random access procedure.

[2185] FeatureCombination is a feature or combination of features associated with a set of random access resources.

[2186] featurePriorities are priorities for features such as (e) RedCap, Slicing, etc. (see Section SOP1d).

[2187] powerRampingStep is the power ramping factor.

[2188] scalingFactorBI is a scaling factor for a prioritized random access procedure.

[2189] ra-PreambleIndex is a random access preamble.

[2190] ra-ssb-OccasionMaskIndex defines the PRACH opportunities associated with the SSB through which a MAC entity can transmit a random access preamble (see Section 7.4).

[2191] ssb-SharedRO-MaskIndex defines PRACH opportunities with preambles assigned to the function or function combination associated with the SSB to which a MAC object can transmit a random access preamble (see Section 7.4).

[2192] ra-OccasionList defines PRACH opportunities associated with CSI-RS where a MAC object can transmit a random access preamble.

[2193] ra-PreambleStartIndex is the starting index of random access preambles for on-demand SI requests.

[2194] startPreambleForThisPartition is the first preamble associated with the set of random access resources applicable to the random access procedure.

[2195] preambleTransMax is the maximum number of random access preamble transmissions.

[2196] preambleTransMax-Msg1-Repetition is the maximum number of random access preamble transfers performed with a given number of Msg1 iterations before switching to the next available higher number of Msg1 iterations.

[2197] preambleTransMaxRO-Type is the maximum number of random access preamble transfers before switching RO types between SBFD RO and non-SBFD RO.

[2198] If groupBconfigured is set, random access preamble group B is set for 4-stage RA type.

[2199] Among the contention-based random access preambles associated with the SSB (as defined in TS 38.213), the first numberOfRA-PreamblesGroupA random access preambles included in groupBconfigured belong to random access preamble group A. The remaining random access preambles associated with the SSB belong to random access preamble group B (if configured).

[2200] If Random Access Preamble Group B is set for a 4-stage RA type, the following applies.

[2201] ra-Msg3SizeGroupA is a threshold that determines the random access preamble group for the 4-step RA type.

[2202] msg3-DeltaPreamble is TS 38.213's am.

[2203] messagePowerOffsetGroupB is the power offset for preamble selection included in groupBconfigured.

[2204] numberOfRA-PreamblesGroupA defines the number of random access preambles in group A for each SSB included in groupBconfigured.

[2205] If there is a set of random access preambles and / or prach opportunities for SI requests, it includes this.

[2206] Includes a set of random access preambles and / or prach opportunities for beam failure recovery requests, if any.

[2207] Includes, if there is a set of random access preambles and / or prach opportunities for resetting via synchronization.

[2208] ra-ResponseWindow is a time window for monitoring RA responses (SpCell only).

[2209] ra-ContentionResolutionTimer is a race resolution timer (SpCell only).

[2210] msgB-ResponseWindow is a time window for monitoring RA responses for 2-stage RA types (SpCell only).

[2211] The following UE variables are used in the random access procedure.

[2212] PREAMBLE_INDEX

[2213] PREAMBLE_TRANSMISSION_COUNTER

[2214] PREAMBLE_POWER_RAMPING_COUNTER

[2215] PREAMBLE_POWER_RAMPING_STEP

[2216] PREAMBLE_RECEIVED_TARGET_POWER

[2217] PREAMBLE_BACKOFF

[2218] PCMAX

[2219] SCALING_FACTOR_BI

[2220] TEMPORARY_C-RNTI

[2221] RA_TYPE

[2222] POWER_OFFSET_2STEP_RA

[2223] MSGA_PREAMBLE_POWER_RAMPING_STEP

[2224] RO_TYPE

[2225] When a random access procedure is initiated for a serving cell or an LTM candidate cell, the MAC object performs the following:

[2226] Flush the Msg3 buffer.

[2227] Flush the MSGA buffer.

[2228] Set PREAMBLE_TRANSMISSION_COUNTER to 1.

[2229] If the random access procedure starts in the serving cell, perform the following.

[2230] Set PREAMBLE_BACKOFF to 0 ms.

[2231] Set POWER_OFFSET_2STEP_RA to 0 dB.

[2232] If the carrier to be used in the random access procedure is explicitly signaled, perform the following.

[2233] Select a signaled carrier to perform a random access procedure.

[2234] Set PCMAX to PCMAX,f,c of the signaled carrier.

[2235] Otherwise, if the carrier to be used for the random access procedure is not explicitly signaled, and the serving cell for the random access procedure is set to a supplementary uplink as specified in TS 38.331, and the RSRP of the downlink path loss criterion is less than rsrp-ThresholdSSB-SUL, then do the following.

[2236] Select a SUL carrier to perform a random access procedure.

[2237] Set PCMAX to PCMAX,f,c of the SUL carrier.

[2238] If not, perform the following.

[2239] Select a NUL carrier to perform a random access procedure.

[2240] Set PCMAX to PCMAX,f,c of the NUL carrier.

[2241] BWP operation is performed except when the random access procedure is initiated by a PDCCH command for an LTM candidate cell.

[2242] If SBFD ROs available for random access preamble transmission for random access procedures are provided by the RRC, perform the following.

[2243] If the RO type for the random access procedure is signaled as RO-2, set RO_TYPE to RO-2.

[2244] Otherwise, if the RO type for the random access procedure is signaled as RO-1, set RO_TYPE to RO-1.

[2245] Otherwise, if the RO type for the random access procedure is not signaled, perform the following.

[2246] If sbfd-RSRP-ThresholdRO-Type is set for the random access procedure, do the following.

[2247] If the RSRP of the downlink path loss criterion is lower than sbfd-RSRP-ThresholdRO-Type and sbfd-RSRP-ThresholdRO-TypeUsage is set to below (as specified in TS 38.331), or if the RSRP of the downlink path loss criterion is higher than sbfd-RSRP-ThresholdRO-Type and sbfd-RSRP-ThresholdRO-TypeUsage is set to above (as specified in TS 38.331), set RO_TYPE to RO-2.

[2248] Otherwise, set RO_TYPE to RO-1.

[2249] Otherwise, set RO_TYPE to RO-1.

[2250] Select a set of random access resources applicable to the current random access procedure in accordance with SOP1b.

[2251] If a random access procedure is initiated by the PDCCH command and the ra-PreambleIndex explicitly provided by PDCCH is not 0b000000, or if a random access procedure is initiated for an SI request (as specified in TS 38.331) and random access resources for the SI request are explicitly provided by RRC, or if a random access procedure is initiated for SpCell beam failure recovery (as specified in Section 5.17) and contention-free random access resources for a beam failure recovery request for a 4-stage RA type for the BWP selected for the random access procedure are explicitly provided by RRC, or if a random access procedure is initiated for a reset via synchronization that is not initiated for recovery using an LTM candidate configuration as specified in TS 38.331 Section 5.3.7.3, and contention-free random access resources for a 4-stage RA type for the BWP selected for the random access procedure are explicitly provided in rach-ConfigDedicated, perform the following.

[2252] If RO_TYPE is set to RO-1 or if contention-free random access resources are explicitly provided in the LTM cell switching command MAC CE, set RA_TYPE to 4-stepRA.

[2253] Otherwise, if the BWP selected for the random access procedure is configured with both 2-step and 4-step RA type random access resources within the selected random access resource set (as specified in SOP1b) and the RSRP of the downlink path loss criterion is higher than the msgA-RSRP-Threshold, or if the BWP selected for the random access procedure is configured with only 2-step RA type random access resources within the selected random access resource set according to SOP1b, or if the random access procedure is initiated for reset via synchronization that was not initiated for recovery using LTM candidate configuration as specified in TS 38.331 Section 5.3.7.3 and for the BWP selected for the random access procedure, competition-free random access resources for the 2-step RA type are explicitly provided in rach-ConfigDedicated, set RA_TYPE to 2-stepRA.

[2254] Otherwise, set RA_TYPE to 4-stepRA.

[2255] Initialize variables specific to random access types as specified in SOP1a.

[2256] If RA_TYPE is set to 2-stepRA, the random access resource selection procedure for the 2-step RA type is performed (see Section SOP2a).

[2257] Otherwise, perform the random access resource selection procedure (see Section SOP2).

[2258] SOP1a Initialization of variables specific to random access types

[2259] The MAC object performs the following.

[2260] If RA_TYPE is set to 4-stepRA, do the following.

[2261] Set PREAMBLE_POWER_RAMPING_STEP to powerRampingStep.

[2262] Set SCALING_FACTOR_BI to 1.

[2263] Set preambleTransMax to the preambleTransMax included in RACH-ConfigGeneric.

[2264] If a random access procedure is initiated for SpCell beam failure recovery (as specified in Section 5.17) and beamFailureRecoveryConfig is set for the active UL BWP of the selected carrier, perform the following.

[2265] If beamFailureRecoveryTimer is set, start it.

[2266] Apply the parameters powerRampingStep, preambleReceivedTargetPower, and preambleTransMax set in beamFailureRecoveryConfig.

[2267] If a random access procedure has been initiated for beam failure recovery (as specified in Section 5.17), and beamFailureRecoveryConfig is set for the active UL BWP of the selected carrier and ra-Prioritization is set in beamFailureRecoveryConfig, then do the following.

[2268] Set PREAMBLE_POWER_RAMPING_STEP to powerRampingStepHighPriority included in ra-Prioritization of beamFailureRecoveryConfig.

[2269] If scalingFactorBI is set in ra-Prioritization of beamFailureRecoveryConfig, set SCALING_FACTOR_BI to scalingFactorBI.

[2270] Otherwise, if the random access procedure is initiated for reset via synchronization or SCG activation that was not initiated for recovery using LTM candidate configuration as specified in TS 38.331 Section 5.3.7.3, and rach-ConfigDedicated is set for the selected carrier and ra-Prioritization is set for rach-ConfigDedicated, do the following.

[2271] Set PREAMBLE_POWER_RAMPING_STEP to powerRampingStepHighPriority included in ra-Prioritization of rach-ConfigDedicated.

[2272] If scalingFactorBI is set in ra-Prioritization of rach-ConfigDedicated, set SCALING_FACTOR_BI to scalingFactorBI.

[2273] Otherwise, if both ra-PrioritizationForSlicing and ra-PrioritizationForAccessIdentity for the NSAG-ID are set for the selected carrier, and the MAC object has received both this NSAG-ID and Access Identity 1 or 2 from the upper layer, and the corresponding bit of ra-PrioritizationForAI is set to 1 for at least one of these Access Identityes, do the following.

[2274] If enableRA-PrioritizationForSlicing is set to true, do the following.

[2275] If powerRampingStepHighPriority is set for ra-PrioritizationForSlicing for this NSAG-ID, set PREAMBLE_POWER_RAMPING_STEP to powerRampingStepHighPriority.

[2276] If scalingFactorBI is set in ra-PrioritizationForSlicing for this NSAG-ID, set SCALING_FACTOR_BI to scalingFactorBI.

[2277] Otherwise, if enableRA-PrioritizationForSlicing is set to false, do the following.

[2278] If powerRampingStepHighPriority is set in ra-PrioritizationForAccessIdentity, set PREAMBLE_POWER_RAMPING_STEP to powerRampingStepHighPriority.

[2279] If scalingFactorBI is set in ra-PrioritizationForAccessIdentity, set SCALING_FACTOR_BI to scalingFactorBI.

[2280] Otherwise, if ra-PrioritizationForSlicing for the NSAG-ID is set for the selected carrier and the MAC object has received this NSAG-ID from the parent layer, do the following.

[2281] If powerRampingStepHighPriority is set for ra-PrioritizationForSlicing for this NSAG-ID, set PREAMBLE_POWER_RAMPING_STEP to powerRampingStepHighPriority.

[2282] If scalingFactorBI is set in ra-PrioritizationForSlicing for this NSAG-ID, set SCALING_FACTOR_BI to scalingFactorBI.

[2283] Otherwise, if ra-PrioritizationForAccessIdentity is set for the selected carrier and the MAC object has received access identity 1 or 2 from the upper layer and the corresponding bit of ra-PrioritizationForAI is set to 1 for at least one of these access identities, perform the following.

[2284] If powerRampingStepHighPriority is set in ra-PrioritizationForAccessIdentity, set PREAMBLE_POWER_RAMPING_STEP to powerRampingStepHighPriority.

[2285] If scalingFactorBI is set in ra-PrioritizationForAccessIdentity, set SCALING_FACTOR_BI to scalingFactorBI.

[2286] If RA_TYPE is switched from 2-stepRA to 4-stepRA during this random access procedure, set POWER_OFFSET_2STEP_RA to (PREAMBLE_POWER_RAMPING_COUNTER - 1) ×(MSGA_PREAMBLE_POWER_RAMPING_STEP - PREAMBLE_POWER_RAMPING_STEP).

[2287] SOP1b Selection of Random Access Resource Sets for Random Access Procedures

[2288] Determining the applicability of Msg3 repetition

[2289] If RO_TYPE is RO-1 or RO-2, or if RO_TYPE is not set, do the following.

[2290] It is assumed that Msg3 iteration is applicable to the current random access procedure if the BWP selected for the random access procedure is set to both random access resource sets where msg3-Repetitions is set to true and random access resource sets where msg3-Repetitions is not set to true, and the RSRP of the downlink path loss criterion is less than rsrp-ThresholdMsg3, or if the BWP selected for the random access procedure is set only to random access resource sets where msg3-Repetitions is set to true.

[2291] Otherwise, assume that the Msg3 iteration is not applicable to the current random access procedure.

[2292] Determining the applicability of Msg1 repetition to RO-1

[2293] For LTM cell switching commands / Rach-ConfigDedicated

[2294] If RO_TYPE is RO-1 or RO_TYPE is not set, do the following.

[2295] It is assumed that if competitive free random access resources for this random access procedure are provided to the LTM cell switching command MAC CE and a non-zero number of Msg1 iterations is indicated in the LTM cell switching command MAC CE, then the number of Msg1 iterations is applicable and the number of Msg1 iterations applicable to the current random access procedure is the number of Msg1 iterations indicated in the LTM cell switching command MAC CE.

[2296] Otherwise, if competing free random access resources have been provided for this random access procedure and the number of Msg1 iterations is indicated in rach-ConfigDedicated, it is assumed that the Msg1 iteration is applicable and the number of Msg1 iterations applicable to the current random access procedure is the number of Msg1 iterations indicated in rach-ConfigDedicated.

[2297] In the case of CBRA

[2298] Otherwise, if no competing free random access resources are provided for this random access procedure and the BWP selected for the random access procedure is configured with sets of random access resources where msg1-Repetitions is set to true and sets of random access resources where msg1-Repetitions is not set to true, perform the following.

[2299] It is assumed that if the BWP selected for the random access procedure is set to random access resource sets associated with Msg1 iteration count 8, and the RSRP of the downlink path loss criterion is less than rsrp-ThresholdMsg1-RepetitionNum8, Msg1 iteration is applicable and 8 is included in the number of Msg1 iterations applicable to the current random access procedure.

[2300] It is assumed that if the BWP selected for the random access procedure is set to random access resource sets associated with Msg1 iteration count 4, and the RSRP of the downlink path loss criterion is less than rsrp-ThresholdMsg1-RepetitionNum4, Msg1 iteration is applicable and 4 is included in the Msg1 iteration count applicable to the current random access procedure.

[2301] It is assumed that if the BWP selected for the random access procedure is set to random access resource sets associated with Msg1 iteration count 2, and the RSRP of the downlink path loss criterion is less than rsrp-ThresholdMsg1-RepetitionNum2, Msg1 iteration is applicable and 2 is included in the number of Msg1 iterations applicable to the current random access procedure.

[2302] Otherwise, if the RSRP of the downlink path loss criterion is not smaller than any of the set rsrp-ThresholdMsg1-RepetitionNumX, it is assumed that Msg1 repetition is not applicable to the current random access procedure.

[2303] If only the msg1-repetition resource exists

[2304] Otherwise, if the BWP selected for the random access procedure is configured only with sets of random access resources where msg1-Repetitions is set to true, perform the following.

[2305] It is assumed that the Msg1 iteration is applicable to the current random access procedure.

[2306] If at least one of rsrp-ThresholdMsg1-RepetitionNumX is set, perform the following.

[2307] If rsrp-ThresholdMsg1-RepetitionNum8 is set and the RSRP of the downlink path loss criterion is less than rsrp-ThresholdMsg1-RepetitionNum8, it is assumed that the number of Msg1 iterations applicable to the current random access procedure includes 8.

[2308] If rsrp-ThresholdMsg1-RepetitionNum4 is set and the RSRP of the downlink path loss criterion is less than rsrp-ThresholdMsg1-RepetitionNum4, it is assumed that the number of Msg1 iterations applicable to the current random access procedure includes 4.

[2309] If rsrp-ThresholdMsg1-RepetitionNum2 is set and the RSRP of the downlink path loss criterion is less than rsrp-ThresholdMsg1-RepetitionNum2, it is assumed that the number of Msg1 iterations applicable to the current random access procedure includes 2.

[2310] Otherwise, if the RSRP of the downlink path loss criterion is not smaller than any of the set rsrp-ThresholdMsg1-RepetitionNumX, it is assumed that the number of Msg1 iterations applicable to the current random access procedure is the lowest number of Msg1 iterations set for this BWP.

[2311] Otherwise (if none of rsrp, ThresholdMsg1, or RepetitionNumX are set), it is assumed that the number of Msg1 iterations applicable to the current random access procedure is the number of Msg1 iterations set for this BWP.

[2312] Repetition of Msg1 for RO-2

[2313] For LTM cell switching commands / Rach-ConfigDedicated

[2314] If RO_TYPE is RO-2, perform the following.

[2315] It is assumed that if competitive free random access resources for this random access procedure are provided to the LTM cell switching command MAC CE and a non-zero number of Msg1 iterations is indicated in the LTM cell switching command MAC CE, then the number of Msg1 iterations is applicable and the number of Msg1 iterations applicable to the current random access procedure is the number of Msg1 iterations indicated in the LTM cell switching command MAC CE.

[2316] Otherwise, if competing free random access resources have been provided for this random access procedure and rach-ConfigDedicated indicates the number of Msg1 iterations and RO_Type set to RO-2, 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.

[2317] In the case of CBRA

[2318] Otherwise, if no competing free random access resources are provided for this random access procedure and the BWP selected for the random access procedure is configured with sets of random access resources where msg1-Repetitions is set to true and sets of random access resources where msg1-Repetitions is not set to true, perform the following.

[2319] It is assumed that if the BWP selected for the random access procedure is set to random access resource sets associated with Msg1 iteration count 8, and the RSRP of the downlink path loss criterion is less than sbfd-rsrp-ThresholdMsg1-RepetitionNum8, Msg1 iteration is applicable and 8 is included in the number of Msg1 iterations applicable to the current random access procedure.

[2320] It is assumed that if the BWP selected for the random access procedure is set to random access resource sets associated with Msg1 iteration count 4, and the RSRP of the downlink path loss criterion is less than sbfd-rsrp-ThresholdMsg1-RepetitionNum4, Msg1 iteration is applicable and 4 is included in the Msg1 iteration count applicable to the current random access procedure.

[2321] It is assumed that if the BWP selected for the random access procedure is set to random access resource sets associated with Msg1 iteration count 2, and the RSRP of the downlink path loss criterion is less than sbfd-rsrp-ThresholdMsg1-RepetitionNum2, Msg1 iteration is applicable and 2 is included in the number of Msg1 iterations applicable to the current random access procedure.

[2322] Otherwise, if the RSRP of the downlink path loss criterion is not smaller than any of the set sbfd-rsrp-ThresholdMsg1-RepetitionNumX, it is assumed that Msg1 repetition is not applicable to the current random access procedure.

[2323] If only the msg1-repetition resource exists

[2324] Otherwise, if the BWP selected for the random access procedure is configured only with sets of random access resources where msg1-Repetitions is set to true, perform the following.

[2325] It is assumed that the Msg1 iteration is applicable to the current random access procedure.

[2326] If at least one of sbfd-rsrp-ThresholdMsg1-RepetitionNumX is set, perform the following.

[2327] If sbfd-rsrp-ThresholdMsg1-RepetitionNum8 is set and the RSRP of the downlink path loss criterion is less than sbfd-rsrp-ThresholdMsg1-RepetitionNum8, it is assumed that the number of Msg1 iterations applicable to the current random access procedure includes 8.

[2328] If sbfd-rsrp-ThresholdMsg1-RepetitionNum4 is set and the RSRP of the downlink path loss criterion is less than sbfd-rsrp-ThresholdMsg1-RepetitionNum4, it is assumed that the number of Msg1 iterations applicable to the current random access procedure includes 4.

[2329] If sbfd-rsrp-ThresholdMsg1-RepetitionNum2 is set and the RSRP of the downlink path loss criterion is less than sbfd-rsrp-ThresholdMsg1-RepetitionNum2, it is assumed that the number of Msg1 iterations applicable to the current random access procedure includes 2.

[2330] Otherwise, if the RSRP of the downlink path loss criterion is not smaller than any of the set sbfd-rsrp-ThresholdMsg1-RepetitionNumX, it is assumed that the number of Msg1 iterations applicable to the current random access procedure is the lowest number of Msg1 iterations set for this BWP.

[2331] Otherwise (if neither rsrp-ThresholdMsg1-RepetitionNumX is set and neither sbfd-rsrp-ThresholdMsg1-RepetitionNumX is set), it is assumed that the number of Msg1 iterations applicable to the current random access procedure is the number of Msg1 iterations set for this BWP.

[2332] Select Random Access Resource Set

[2333] If competitive free random access resources are provided for this random access procedure, perform the following.

[2334] Select a set of random access resources associated with the competitive free random access resources provided for this random access procedure.

[2335] Otherwise, if competitive free random access resources are not provided for this random access procedure, perform the following.

[2336] Among the random access resource sets configured in the BWP selected for the random access procedure, a random access resource set that satisfies all of the following conditions is selected.

[2337] If it is determined that Msg3 iterations are applicable to the current random access procedure, the random access resource set must have msg3-Repetitions set to true; otherwise, the random access resource set must not have msg3-Repetitions set to true.

[2338] If it is determined that a Msg1 iteration is applicable to the current random access procedure, the random access resource set must have msg1-Repetitions set to true and be associated with one of the applicable Msg1 iteration counts; otherwise, the random access resource set must not have msg1-Repetitions set to true.

[2339] If RO_TYPE is set to RO-2, the random access resource set must be associated with SBFD ROs, and otherwise, the random access resource set must not be associated with SBFD ROs.

[2340] If a random access procedure is initiated for an on-demand SI request, the random access resource set must be associated with the SI request.

[2341] If a random access procedure is initiated for beam failure recovery, the random access resource set must be associated with the beam failure recovery request.

[2342] If a random access procedure is initiated for a reset via synchronization, the random access resource set must be associated with the reset via synchronization.

[2343] If there are multiple sets of random access resources that satisfy the above conditions, select a random access resource set as specified in Section SOP1d.

[2344] SOP1d Selection of random access resource sets based on function priority

[2345] If there are multiple random access resource sets applicable to the current random access procedure among the random access resource sets identified in SOP1b, the MAC object performs the following:

[2346] For each set of random access resources, calculate the sum of the priority values ​​of all features associated with the corresponding FeatureCombination.

[2347] Select the set of random access resources with the smallest sum of priority values.

[2348] If there are multiple random access resource sets with the smallest sum of priority values, one of them is randomly selected.

[2349] If a priority value is not set for a function, the priority value of that function is considered to be the lowest priority (highest value).

[2350] SOP2 Random Access Resource Selection

[2351] The MAC object performs the following.

[2352] If PREAMBLE_TRANSMISSION_COUNTER is 1 or if data with a higher priority occurs after the previous transmission, do the following.

[2353] Set PREAMBLE_RECEIVED_TARGET_POWER to preambleReceivedTargetPower and set PREAMBLE_POWER_RAMPING_COUNTER to 1.

[2354] If not, perform the following.

[2355] Set PREAMBLE_RECEIVED_TARGET_POWER to PREAMBLE_RECEIVED_TARGET_POWER + PREAMBLE_POWER_RAMPING_STEP × (PREAMBLE_POWER_RAMPING_COUNTER - 1).

[2356] If the random access procedure is initiated by the PDCCH command and the ra-PreambleIndex explicitly provided by PDCCH is not 0b000000, do the following.

[2357] Set PREAMBLE_INDEX to ra-PreambleIndex explicitly signaled by PDCCH.

[2358] If not, perform the following.

[2359] If the random access procedure is initiated by the MAC object itself and one of the following conditions is met, perform the following.

[2360] UL data or multiplexed L1 / L2 control information can be transmitted or

[2361] If SR masking is not set or

[2362] If the random access procedure was initiated for a reason other than beam failure recovery, perform the following.

[2363] The UE determines the size of the UL data to be used for Msg3 transmission as specified in SOP2b.

[2364] If the total size of the UL data to be used for Msg3 transmission is greater than ra-Msg3SizeGroupA and Random Access Preamble Group B is set for the set of random access resources selected in SOP1b and the downlink path loss is less than PCMAX(for serving cell) - preambleReceivedTargetPower - msg3-DeltaPreamble - messagePowerOffsetGroupB, or if Random Access Preamble Group B is set and a MAC PDU containing a CCCH SDU is scheduled to be transmitted in Msg3 and the size of the CCCH SDU is greater than 72 bits, then do the following.

[2365] Select Random Access Preamble Group B for the current random access procedure.

[2366] If not, perform the following.

[2367] Select Random Access Preamble Group A for the current random access procedure.

[2368] If not, perform the following.

[2369] Select Random Access Preamble Group A for the current random access procedure.

[2370] One random access preamble is uniformly and randomly selected from among the random access preambles that are associated with the selected random access resource set and belong to the selected random access preamble group.

[2371] Sets PREAMBLE_INDEX to the selected random access preamble.

[2372] Perform random access preamble transmission as specified in SOP3.

[2373] SOP2b Msg3 Determine buffer size

[2374] The MAC object performs the following.

[2375] For the configured logical channels, determine the following.

[2376] Data amount available for UL-SCH transmission

[2377] Except when a C-RNTI MAC CE or Common CCCH SDU is included in the transmission, the amount of data available for each logical channel is determined as follows.

[2378] If there is data available for transmission on a logical channel that does not include the amount of UL data set by RRC for the logical channel, and RLC headers and subheaders for PDCP control PDUs and MAC control elements, or

[2379] If the corresponding logical channel is not configured to transmit through the configured grant, or if the corresponding logical channel is configured to transmit through the configured grant and there is data through the configured UL Grant Type 1 for the logical channel, or if the configured Grant Type 2 is enabled, or

[2380] If the RA type is 2-stepRA, if allowedServingCells is not set for the corresponding logical channel, or if allowedServingCells includes a serving cell where a random access procedure is in progress, and

[2381] If allowedSCS-List is not set for the corresponding logical channel, or if the subcarrier interval of the active UL BWP is included in allowedSCS-List, and

[2382] If ue-SpecificUL-Delay is not set for the corresponding logical channel, or if it is set and the slot timing value is appropriate

[2383] Buffer status report, MAC control elements and configured grant verification, amount of data available for MAC control elements including MAC control elements.

[2384] Amount of data available for transmission via UL-CCH if there is data available for transmission via CCCH

[2385] Amount of data available for C-RNTI MAC CE in the case of the MAC object itself that initiated the random access procedure

[2386] Amount of data available for multiplexed L1 / L2 control information including the corresponding padding BSR when there is a request to transmit multiplexed L1 / L2 control information

[2387] Recommended Bitrate Query MAC CE when triggered, amount of data available for the Recommended Bitrate Query MAC CE

[2388] The total amount of data ready to be transmitted on the uplink is determined as the sum of the above-determined data amounts.

[2389] SOP3 Random Access Preamble Transmission

[2390] The MAC object performs the following.

[2391] In the selected random access resource set of the BWP selected for the random access procedure, determine the PRACH opportunity associated with the corresponding RA-RNTI according to TS 38.213.

[2392] If RO_TYPE is set to RO-1, the PRACH opportunity is selected from among the PRACH opportunities associated only with non-SBFD symbols.

[2393] If RO_TYPE is set to RO-2, the PRACH opportunity is selected from among the PRACH opportunities associated with SBFD symbols.

[2394] If the PRACH mask index is set to 0 or if competitive free random access resources are provided for this random access procedure, perform the following.

[2395] Instruct the transmission of the selected PRACH to the lower layer with the following parameters as specified in TS 38.213.

[2396] Selected PREAMBLE_INDEX

[2397] Selected PRACH mask index (ra-ssb-OccasionMaskIndex, ra-OccasionList, or ssb-SharedRO-MaskIndex)

[2398] Selected downlink path loss criteria and corresponding RSRP

[2399] PREAMBLE_RECEIVED_TARGET_POWER + POWER_OFFSET_2STEP_RA determined as specified in TS 38.213

[2400] Otherwise (if the PRACH mask index is set to a non-zero value), do the following.

[2401] Uses the PRACH mask index to instruct the transmission of the selected PRACH to the lower layer.

[2402] Start ra-ResponseWindow if RA_TYPE is set to 4-stepRA.

[2403] Start msgB-ResponseWindow when RA_TYPE is set to 2-stepRA.

[2404] SOP4 Receiving Random Access Response

[2405] When the random access response reception procedure is completed, the MAC object performs the following.

[2406] If there is a successfully received random access response where RA_TYPE is set to 4-stepRA and contains a random access preamble identifier that matches the random access preamble, do the following.

[2407] It is assumed that there is a transmittable UL grant in the random access response.

[2408] Transmit the MAC PDU in accordance with Section 5.4.2 in the PUSCH of the earliest UL transmission.

[2409] Proceed with the competition resolution procedures specified in SOP5.

[2410] Otherwise, if ra-ResponseWindow or msgB-ResponseWindow expires and no random access response is received, or if it is notified that receiving a response from a lower layer was unsuccessful before ra-ResponseWindow or msgB-ResponseWindow expires, do the following.

[2411] Increase PREAMBLE_TRANSMISSION_COUNTER by 1.

[2412] Increases PREAMBLE_POWER_RAMPING_COUNTER by 1.

[2413] If Msg1 repetition is applicable to the current random access procedure and PREAMBLE_TRANSMISSION_COUNTER is equal to or less than preambleTransMax-Msg1-Repetition, do the following.

[2414] Continue random access resource selection starting from SOP2 using the same number of Msg1 iterations.

[2415] Otherwise, if Msg1 iterations are applicable for the current random access procedure and PREAMBLE_TRANSMISSION_COUNTER is greater than preambleTransMax-Msg1-Repetition and there is a next higher Msg1 iteration available among the applicable Msg1 iterations, do the following.

[2416] Reset PREAMBLE_TRANSMISSION_COUNTER to 1.

[2417] Select the next higher available Msg1 iteration from the applicable Msg1 iterations.

[2418] Using the selected number of Msg1 iterations, continue selecting a random access resource set starting from SOP1b.

[2419] Otherwise, if SBFD ROs are provided for use in random access preamble transmission and RO type switching is possible and PREAMBLE_TRANSMISSION_COUNTER is equal to preambleTransMaxRO-Type + 1, do the following.

[2420] If RO_TYPE is set to RO-1, switch RO_TYPE to RO-2; otherwise, switch RO_TYPE to RO-1.

[2421] Reset PREAMBLE_TRANSMISSION_COUNTER to 1.

[2422] Reset PREAMBLE_POWER_RAMPING_COUNTER to 1.

[2423] Continue selecting random access resource sets starting from SOP1b using the converted RO_TYPE.

[2424] Otherwise, if PREAMBLE_TRANSMISSION_COUNTER is equal to preambleTransMax + 1, do the following.

[2425] If a random access procedure is performed in SpCell, perform the following.

[2426] Displays random access problems in the upper layer.

[2427] If a random access procedure is performed in SCell, perform the following.

[2428] Displays random access problems in the upper layer.

[2429] Stop the random access procedure and flush the Msg3 buffer.

[2430] If not, perform the following.

[2431] Select PREAMBLE_BACKOFF.

[2432] If there is a BI received in the random access response message, set PREAMBLE_BACKOFF to SCALING_FACTOR_BI × BI.

[2433] Otherwise, set PREAMBLE_BACKOFF to 0.

[2434] Delays the PREAMBLE_BACKOFF period.

[2435] Return to SOP2 and continue with random access resource selection.

[2436] SOP5 Competition Resolution

[2437] The MAC object performs the following.

[2438] If the random access preamble is not explicitly signaled by the MAC object's C-RNTI, do the following.

[2439] Stores the TEMPORARY_C-RNTI set for the random access preamble of the successfully received random access response message.

[2440] Start ra-ContentionResolutionTimer.

[2441] If not, perform the following.

[2442] The competition resolution is considered to have been successfully completed.

[2443] If ra-ContentionResolutionTimer is running and a PDCCH transmission containing the C-RNTI of a MAC object is received, perform the following.

[2444] The competition resolution is considered to have been successfully completed.

[2445] Stop ra-ContentionResolutionTimer.

[2446] Discard TEMPORARY_C-RNTI.

[2447] If ra-ContentionResolutionTimer is running and a MAC PDU containing a CCCH SDU is sent to Msg3 and the UE contention resolution identity MAC CE is successfully received, perform the following.

[2448] Compare the received UE contention resolution identity MAC CE with the CCCH SDU transmitted in the Msg3 MAC PDU.

[2449] If it matches, do the following.

[2450] The competition resolution is considered to have been successfully completed.

[2451] Stop ra-ContentionResolutionTimer.

[2452] Set TEMPORARY_C-RNTI to C-RNTI.

[2453] If they do not match, do the following.

[2454] Discard TEMPORARY_C-RNTI.

[2455] Flush the Msg3 buffer.

[2456] If the competition resolution is deemed to have been successfully completed, perform the following.

[2457] Flush the Msg3 buffer.

[2458] The random access procedure is...

Claims

Claim 1 A Random Access (RA) method performed by a User Equipment (UE) in a wireless communication system, comprising the steps of: initiating a random access procedure; determining a Random Access Channel Opportunity Type (RO-type); determining a set of random access resources; and determining RA resources. A method comprising the step of transmitting a preamble; wherein the RA resource set is selected based on whether a Msg1 repetition is applicable to the random access procedure, and if the RO-type is 2nd-RO, whether a Msg1 repetition is applicable to the random access procedure is determined based on a second parameter set, and if the RO-type is 1st-RO, whether a Msg1 repetition is applicable to the random access procedure is determined based on a first parameter set, wherein the second parameter set includes one or more sbfd-RSRP-ThresholdMsg1-RepetitionNumX, and the first parameter set includes one or more RSRP-ThresholdMsg1-RepetitionNumX, and X is any one of 2, 4, and 8. Claim 2 A method according to claim 1, wherein the RO-type is a 2nd-RO and the Reference Signal Received Power (RSRP) of the downlink path loss reference is less than any configured sbfd-RSRP-ThresholdMsg1-RepetitionNumX, wherein the Msg1 repetition is applicable to the random access procedure. Claim 3 A method according to claim 1, wherein the RO-type is a 2nd-RO and the RSRP of the downlink path loss reference is greater than or equal to any configured sbfd-RSRP-ThresholdMsg1-RepetitionNumX, wherein the Msg1 repetition is not applicable to the random access procedure. Claim 4 A method according to claim 1, wherein the 2nd-RO is located on a resource block (RB) belonging to both an active uplink (UL) bandwidth part (BWP) and a UL sub-band; and is associated with a sub-band full duplex (SBFD) symbol comprising at least one SBFD symbol indicated as a downlink (DL) by tdd-UL-DL-ConfigurationCommon.

Images