KR102472518B1 - Method and Apparatus for selecting a random access configuration from a plurality of random access configurations based on target feature combination in wireless communication system - Google Patents

Abstract

According to an embodiment of the present disclosure, a method of user equipment for selecting one random access configuration among a plurality of random access configurations based on a target feature combination in a wireless mobile communication system comprises the steps of: receiving, by the user equipment, an SIB1 from a base station; determining, by the terminal, a first target feature combination; determining, by the user equipment, an uplink for a random access procedure based on rsrpThresholdSSB-SUL included in a first RACH-ConfigCommon included in a first BWP-UplinkCommon; determining, by the UE, that an SDT is applicable when RSRP of a downlink path loss criterion is higher than rsrp-ThresholdSSB-SDT included in the first RACH-ConfigCommon of the selected uplink and the SDT is triggered by a higher layer; determining, by the UE, a target feature combination by including the SDT in the first target feature combination when it is determined that the SDT is applicable; selecting, by the UE, one second RACH-ConfigCommon from the plurality of second RACH-ConfigCommons of the selected uplink, based on the comparison between the target feature combination and the plurality of feature combinations associated with a plurality of second RACH-ConfigCommons of the selected uplink; and performing, by the UE, a random access procedure based on the selected second RACH-ConfigCommon.

Description

Method and Apparatus for selecting a random access configuration from a plurality of random access configurations based on target feature combination in a wireless mobile communication system in wireless communication system}

The present disclosure relates to a method and apparatus for a terminal to select one random access configuration from a plurality of random access configurations based on a target feature combination in a wireless mobile communication system.

In order to meet the growing demand for wireless data traffic after the commercialization of 4G communication systems, 5G communication systems have been developed. In order to achieve a high data rate, the 5G communication system has introduced a very high frequency (mmWave) band (eg, such as the 60 GHz band). In order to mitigate the path loss of radio waves and increase the propagation distance of radio waves in the ultra-high frequency band, beamforming, massive MIMO, and Full Dimensional MIMO (FD-MIMO) are used in 5G communication systems. ), array antenna, analog beam-forming and large scale antenna technologies are used. In the 5G communication system, scalability is increased by dividing the base station into a central unit and a distribution unit. In addition, the 5G communication system aims to support very high data rates and very low transmission delays in order to support various services.

Various attempts are being made to apply the 5G communication system to the IoT network. For example, 5G communication such as sensor network, machine to machine (M2M), and machine type communication (MTC) is implemented by techniques such as beamforming, MIMO, and array antenna.

In the 5G communication system, various feature combinations may be provided in one cell. The network may divide and provide RACH resources for each feature combination in order to achieve load balancing or the like. A means for efficiently providing RACH resource partitioning information for each combination of various features is required.

The disclosed embodiment is intended to provide a method and apparatus for a terminal to select one random access configuration from a plurality of random access configurations based on a target feature combination in a wireless mobile communication system.

According to an embodiment of the present disclosure, in a method of a terminal, according to an embodiment of the present disclosure, in the method of a terminal, the step of receiving the SIB1 from the base station by the terminal, and selecting a first target feature combination by the terminal Determining step, determining uplink for random access procedure based on rsrpThresholdSSB-SUL included in 1st RACH-ConfigCommon included in 1st BWP-UplinkCommon by UE, selecting RSRP based on downlink path loss Determining that the SDT is applicable by the terminal when the SDT is higher than the rsrp-ThresholdSSB-SDT included in the first RACH-ConfigCommon of the uplink and the SDT is triggered by a higher layer; if the SDT is determined to be applicable, a first target feature Determining a target feature combination by the terminal by including the SDT in the combination; Based on a comparison between the target feature combination and a plurality of feature combinations associated with a plurality of second RACH-ConfigCommons of the selected uplink, the plurality of features of the selected uplink. Selecting one second RACH-ConfigCommon from the second RACH-ConfigCommon by the terminal and performing a random access procedure by the terminal based on the selected second RACH-ConfigCommon.

The disclosed embodiment provides a method and apparatus for a terminal to request and configure a gap setting related to a bandwidth part in a wireless mobile communication system.

1A is a diagram illustrating the structure of a 5G system and an NG-RAN according to an embodiment of the present disclosure.
1B is a diagram illustrating a radio protocol structure in a NR system according to an embodiment of the present disclosure.
Figure 1c is a diagram illustrating bandwidth portion adjustment and bandwidth portion.
1D is a diagram illustrating a search period and a control resource set.
1E is a diagram showing the structure of serving cell configuration information included in system information.
1F is a diagram illustrating feature combinations supported in one cell.
1G is a diagram showing an alternative structure of uplink bandwidth portion setting information included in system information or a downlink control message.
2A is a diagram illustrating operations of a terminal and a base station according to an embodiment of the present disclosure.
2B is a diagram illustrating operations of a terminal in a connected state and a base station according to an embodiment of the present disclosure.
3A is a flowchart for explaining an operation of a terminal according to an embodiment of the present disclosure.
4A is a block diagram showing the internal structure of a terminal to which the present invention is applied.
4B is a block diagram showing the internal structure of a base station to which the present invention is applied.

Hereinafter, embodiments of the present invention will be described in detail with accompanying drawings. In addition, in describing the present invention, if it is determined that a detailed description of a related known function or configuration may unnecessarily obscure the subject matter of the present invention, the detailed description will be omitted. In addition, terms to be described later are terms defined in consideration of functions in the present invention, which may vary according to the intention or custom of a user or operator. Therefore, the definition should be made based on the contents throughout this specification.

A term used in the following description to identify a connection node, a term referring to network entities, a term referring to messages, a term referring to an interface between network entities, and a term referring to various types of identification information. Etc. are illustrated for convenience of description. Therefore, the present invention is not limited to the terms described below, and other terms indicating objects having equivalent technical meanings may be used.

For convenience of description below, the present invention uses terms and names defined in the 3rd Generation Partnership Project (3GPP) standard, which is the most up-to-date among existing communication standards. However, the present invention is not limited by the above terms and names, and may be equally applied to systems conforming to other standards.

Table 1 lists the abbreviations used in the present invention.

Acronym full name Acronym full name 5GC 5G Core Network RACH Random Access Channel ACK Acknowledgment RAN Radio Access Network AM Acknowledged Mode RAR Random Access Response AMF Access and Mobility Management Function RA-RNTI Random Access RNTI ARQ Automatic Repeat Request RAT Radio Access Technology AS Access Stratum RB Radio Bearer ASN.1 Abstract Syntax Notation One RLC Radio Link Control BSR Buffer Status Report RNA RAN-based Notification Area BWP Bandwidth Part RNAU RAN-based Notification Area Update CA Carrier Aggregation RNTI Radio Network Temporary Identifier CAG Closed Access Group RRC Radio Resource Control CG Cell Group RRM Radio Resource Management C-RNTI Cell RNTI RSRP Reference Signal Received Power CSI Channel State Information RSRQ Reference Signal Received Quality DCI Downlink Control Information RSSI Received Signal Strength Indicator DRB (user) Data Radio Bearer SCell Secondary Cell DRX Discontinuous Reception SCS Subcarrier Spacing HARQ Hybrid Automatic Repeat Request SDAP Service Data Adaptation Protocol IE Information element SDU Service Data Unit LCG Logical Channel Group SFN System Frame Number MAC Medium Access Control S-GW Serving Gateway MIB Master Information Block SI System Information NAS Non-Access Stratum SIB System Information Block NG-RAN NG Radio Access Network SpCell Special Cell NR NR Radio Access SRB Signaling Radio Bearer PBR Prioritized Bit Rate SRS Sounding Reference Signal PCell Primary Cell SS Search space PCI Physical Cell Identifier SSB SS/PBCH block PDCCH Physical Downlink Control Channel SSS Secondary Synchronization Signal PDCP Packet Data Convergence Protocol SUL Supplementary Uplinks PDSCH Physical Downlink Shared Channel TM Transparent Mode PDUs Protocol Data Unit UCI Uplink Control Information PHR Power Headroom Report UE User Equipment PLMN Public Land Mobile Network UM Unacknowledged Mode PRACH Physical Random Access Channel CRP Cell Reselection Priority PRB Physical Resource Block MUSIM Multi-Universal Subscriber Identity Module PSS Primary Synchronization Signal CCCH Common Control Channel PUCCH Physical Uplink Control Channel CSI-RS Channel State Information - Reference Signal PUSCH Physical Uplink Shared Channel

Table 2 defines terms frequently used in the present invention.

Terminology Definition Carrier frequency center frequency of the cell. Cell combination of downlink and optionally uplink resources. The linking between the carrier frequency of the downlink resources and the carrier frequency of the uplink resources is indicated in the system information transmitted on the downlink resources. Cell Group in dual connectivity, a group of serving cells associated with either the MeNB or the SeNB. Cell reselection A process to find a better suitable cell than the current serving cell based on the system information received in the current serving cell Cell selection A process to find a suitable cell either blindly or based on the stored information Cell Reselection Priority Priority of a carrier frequency regarding cell reselection. System Information Block 2 and System Information Block 3 provide the CRP of the serving frequency and CRPs of inter-frequencies respectively. UE consider higher priority frequency for cell reselection if channel condition of the frequency is better than a specific threshold even if channel condition of a lower priority frequency is better than that of the higher priority frequency. Dedicated signaling Signaling sent on DCCH logical channel between the network and a single UE. Field The individual contents of an information element are referred to as fields. Frequency layer set of cells with the same carrier frequency. Global cell identity An identity to uniquely identify an NR cell. It is consisted of cellIdentity and plmn-Identity of the first PLMN-Identity in plmn-IdentityList in SIB1. gNB node providing NR user plane and control plane protocol terminations towards the UE, and connected via the NG interface to the 5GC. Handover procedure that changes the serving cell of a UE in RRC_CONNECTED. Information element A structural element containing single or multiple fields is referred as information element. L The Length field in MAC subheader indicates the length of the corresponding MAC SDU or of the corresponding MAC CE LCID 6 bit logical channel identity in MAC subheader to denote which logical channel traffic or which MAC CE is included in the MAC subPDU Logical channel a logical path between a RLC entity and a MAC entity. There are multiple logical channel types depending on what type of information is transferred e.g. CCCH (Common Control Channel), DCCH (Dedicate Control Channel), DTCH (Dedicate Traffic Channel), PCCH (Paging Control Channel) NR NR radio access PCell SpCell of a master cell group. registered PLMN PLMN which UE has registered to selected PLMN PLMN which UE has selected to perform registration procedure equivalent PLMN PLMN which is equivalent to registered PLMN. UE is informed of list of EPLMNs by AMF during registration procedure PLMN ID Check the process that checks whether a PLMN ID is the RPLMN identity or an EPLMN identity of the UE. Primary Cell The MCG cell, operating on the primary frequency, in which the UE either performs the initial connection establishment procedure or initiates the connection re-establishment procedure. Radio Bearer Logical path between a PDCP entity and upper layer (i.e. SDAP entity or RRC) RLC bearer RLC and MAC logical channel configuration of a radio bearer in one cell group. RLC bearer configuration The lower layer part of the radio bearer configuration comprising the RLC and logical channel configurations. Serving Cell For a UE in RRC_CONNECTED not configured with CA/DC there is only one serving cell comprising of the primary cell. For a UE in RRC_CONNECTED configured with CA/ DC the term 'serving cells' is used to denote the set of cells comprising of the Special Cell(s) and all secondary cells. SpCell primary cell of a master or secondary cell group. Special Cell For Dual Connectivity operation the term Special Cell refers to the PCell of the MCG or the PSCell of the SCG, otherwise the term Special Cell refers to the PCell. SRB Signaling Radio Bearers" (SRBs) are defined as Radio Bearers (RBs) that are used only for the transmission of RRC and NAS messages. SRB0 SRB0 is for RRC messages using the CCCH logical channel SRB1 SRB1 is for RRC messages (which may include a piggybacked NAS message) as well as for NAS messages prior to the establishment of SRB2, all using DCCH logical channel; SRB2 SRB2 is for NAS messages and for RRC messages which include logged measurement information, all using DCCH logical channel. SRB2 has a lower priority than SRB1 and may be configured by the network after AS security activation; SRB3 SRB3 is for specific RRC messages when UE is in (NG)EN-DC or NR-DC, all using DCCH logical channel SRB4 SRB4 is for RRC messages which include application layer measurement reporting information, all using DCCH logical channel. CCCH CCCH is a logical channel to transfer initial RRC messages such as RRCSetupRequest, RRCResumeRequest and RRCSetup DCCH DCCH is a logical channel to transfer RRC messages after RRC connection establishment Suitable cell A cell on which a UE may camp. Following criteria apply
- The cell is part of either the selected PLMN or the registered PLMN or PLMN of the Equivalent PLMN list
- The cell is not barred
- The cell is part of at least one TA that is not part of the list of "Forbidden Tracking Areas for Roaming" (TS 22.011 [18]), which belongs to a PLMN that fulfills the first bullet above.
- The cell selection criterion S is fulfilled (ie RSRP and RSRQ are better than specific values

In the present invention, "trigger" or "triggered" and "initiate" or "start" may be used in the same meaning.

In the present invention, a terminal with reduced performance and a RedCap UE may be used in the same meaning.

1A is a diagram illustrating structures of a 5G system and an NG-RAN according to an embodiment of the present disclosure. The 5G system consists of NG-RAN (1a-01) and 5GC (1a-02). An NG-RAN node is one of the two below.

1: gNB providing NR user plane and control plane towards UE; or

2: ng-eNB providing E-UTRA user plane and control plane to UE side.

gNBs (1a-05 to 1a-06) and ng-eNBs (1a-03 to 1a-04) are interconnected through an Xn interface. The gNB and ng-eNB are connected to an Access and Mobility Management Function (AMF) (1a-07) and a User Plane Function (UPF) (1a-08) through an NG interface. AMF (1a-07) and UPF (1a-08) can be composed of one physical node or separate physical nodes.

gNBs (1a-05 to 1a-06) and ng-eNBs (1a-03 to 1a-04) host the functions listed below.

Radio bearer control, radio admission control, connection mobility control, dynamic allocation of resources to UEs in uplink, downlink and sidelink (constant), IP and Ethernet header compression, uplink data decompression and encryption of user data streams, AMF selection, routing of user plane data to UPF, scheduling and transmission of paging messages, scheduling and transmission of broadcast information (originating from AMF or O&M), when AMF selection is not possible with the information provided;

Measurement and measurement report configuration for mobility and scheduling, session management, QoS flow management and mapping to data radio bearers, RRC_INACTIVE support, radio access network sharing;

Close interaction between NR and E-UTRA, support for network slicing.

AMF (1a-07) hosts functions such as NAS signaling, NAS signaling security, AS security control, S-GW selection, authentication, mobility management and location management.

UPF 1a-08 hosts functions such as packet routing and forwarding, uplink and downlink transport level packet marking, QoS management, and mobility anchoring for mobility.

1B is a diagram illustrating a radio protocol structure of a 5G system.

The user plane protocol stack is SDAP (1b-01 to 1b-02), PDCP (1b-03 to 1b-04), RLC (1b-05 to 1b-06), MAC (1b-07 to 1b-08), PHY (1b-09 to 1b-10). The control plane protocol stack consists of NAS (1b-11 to 1b-12), RRC (1b-13 to 1b-14), PDCP, RLC, MAC, and PHY.

Each protocol sublayer performs functions related to the operations listed in the table below.

Sublayer Functions NAS Authentication, mobility management, security control, etc. RRC System information, paging, RRC connection management, security functions, signaling radio bearer and data radio bearer management, mobility management, QoS management, recovery from radio link failure detection and recovery, NAS message transmission, etc. SDAP Mapping between QoS flows and data radio bearers, QoS flow ID (QFI) marking of DL and UL packets. PDCP Data transmission, header compression and decompression, encryption and decryption, integrity protection and integrity verification, redundant transmission, ordering and out-of-order delivery, etc. RLC Higher layer PDU transmission, error correction through ARQ, RLC SDU division and re-division, SDU reassembly, RLC re-establishment, etc. MAC Mapping between logical channels and transport channels, multiplexing/demultiplexing MAC SDUs belonging to one or another logical channel in a transport block (TB) carried in the physical layer, information reporting schedule, priority processing between UEs, priority between single UE logical channels ranking processing, etc. PHY Channel coding, physical layer hybrid-ARQ processing, rate matching, scrambling, modulation, layer mapping, downlink control information, uplink control information, etc.

1C is a diagram illustrating an example of a bandwidth part.

Bandwidth adaptation (BA) allows the UE's receive and transmit bandwidth to be adjusted so that it need not be as large as the cell's bandwidth. It can also be commanded to change width (e.g. collapse during periods of low activity to conserve power) or move position in the frequency domain (e.g. increase scheduling flexibility). Also, the sub-carrier interval may be changed (eg to allow other services). A subset of the cell's total cell bandwidth is called BWP(s). BA is achieved by configuring several BWPs to the UE and telling the UE which of the configured BWPs is active. In FIG. 2A, a scenario in which three different BWPs are configured below is shown.

1: BWP1 (1c-11 to 1c-19) with a width of 40 MHz and a subcarrier spacing of 15 kHz

2: BWP2 (1c-13 to 1c-17) with a width of 10 MHz and a subcarrier spacing of 15 kHz

3: BWP3 (1c-15) with a width of 20 MHz and a subcarrier spacing of 60 kHz

1D is a diagram illustrating an example of a search period and a control resource set.

A plurality of SSs may be set in one BWP. The UE monitors PDCCH candidates according to the SS configuration of the currently activated BWP. One SS consists of an SS identifier, a CORESET identifier indicating a related CORESET, a period and offset of a slot to be monitored, a duration in units of slots, a symbol to be monitored within a slot, and an SS type. The information may be explicitly and individually set, or may be set to a predetermined index related to predetermined values.

One CORESET consists of a CORESET identifier, frequency domain resource information, symbol-unit duration, and TCI state information.

Basically, it can be understood that CORESET provides frequency domain information to be monitored by the terminal, and SS provides time domain information to be monitored by the terminal.

CORESET#0 and SS#0 can be set in IBWP. In IBWP, one CORESET and a plurality of SSs can be additionally set. When the terminal receives the MIB (1d-01), it recognizes CORESET#0 (1d-02) and SS#0 (1d-03) for receiving SIB1 using predetermined information included in the MIB. The terminal receives SIB1 (1d-05) through the CORESET#0 (1d-02) and SS#0 (1d-03). SIB1 includes information for setting CORESET#0 (1d-06) and SS#0 (1d-07) and information for setting another CORESET, for example, CORESET#n (1d-11) and SS#m (1d-13). may be included. The terminal receives necessary information from the base station before entering the RRC connected state, such as SIB2 reception, paging reception, and random access response message reception, using the CORESETs and SSs configured in SIB1. CORESET#0 (1d-02) set in MIB and CORESET#0 (1d-06) set in SIB1 may be different from each other, and the former is called 1st CORESET#0 and the latter is called 1st CORESET#0. SS#0 (1d-03) set in MIB and SS#0 (1d-07) set in SIB1 may be different from each other, and the former is referred to as first SS#0 and the latter as second SS#0. SS#0 and CORESET#0 configured for the RedCap terminal are referred to as 3rd SS#0 and 3rd CORESET#0. The first SS#0, the second SS#0, and the third SS#0 may be identical to or different from each other. The first CORESET#0, the second CORESET#0, and the third CORESET#0 may be identical to or different from each other. SS#0 and CORESET#0 are instructed to set with a 4-bit index, respectively. The 4-bit index indicates a setting predetermined in the standard. Except for SS#0 and CORESET#0, the detailed configuration of SS and CORSESET is indicated by individual information elements.

When the RRC connection is established, additional BWPs may be configured for the UE.

A serving cell may consist of one or several BWPs.

A UE may be configured with a plurality of DL BWPs and a plurality of UL BWPs for one serving cell. When the serving cell operates in a paired spectrum (ie, FDD band), the number of DL BWPs and the number of UL BWPs may be different. When the serving cell operates in an unpaired spectrum (ie, TDD band), the number of DL BWPs and the number of UL BWPs are the same.

SIB1 includes DownlinkConfigCommonSIB, UplinkConfigCommonSIB, and tdd-UL-DL-ConfigurationCommon.

tdd-UL-DL-ConfigurationCommon is a cell specific TDD UL/DL configuration. It consists of subfields such as referenceSubcarrierSpacing, pattern1, and pattern2.

referenceSubcarrierSpacing is a reference SCS used to determine the time domain boundary in the UL-DL pattern.

pattern1 and pattern2 are TDD uplink and downlink patterns. It consists of subfields such as dl-UL-TransmissionPeriodicity, nrofDownlinkSlots, nrofDownlinkSymbols, nrofUplinkSlots, and nrofUplinkSymbols.

dl-UL-TransmissionPeriodicity indicates a period of a DL-UL pattern.

nrofDownlinkSlots indicates the number of consecutive full DL slots in each DL-UL pattern.

nrofDownlinkSymbols indicates the number of consecutive DL symbols from the start of the slot following the last full DL slot.

nrofUplinkSlots indicates the number of consecutive full UL slots in each DL-UL pattern.

nrofUplinkSymbols indicates the number of consecutive UL symbols at the end of the slot before the first full UL slot.

Slots between the last full DL slot and the first full UL slot are flexible slots. A full UL slot is also referred to as a static UL slot. In this disclosure, the UL slot is a static UL slot.

DownlinkConfigCommonSIB includes BWP-DownlinkCommon for initial DL BWP. UplinkConfigCommonSIB includes BWP-UplinkCommon for initial UL BWP. BWP-id of initialDownlinkBWP is 0.

The RRCReconfiguration message includes multiple BWP-Downlinks, multiple BWP-Uplinks, firstActiveDownlinkBWP-Id, bwp-InactivityTimer, defaultDownlinkBWP-Id, and BWP-DownlinkDedicated for the initial DL BWP.

BWP-Downlink includes bWP-Id, BWP-DownlinkCommon and BWP-DownlinkDedicated.

BWP-Uplink includes bwp-Id, BWP-UplinkCommon and BWP-UplinkDedicated.

bwp-Id is an integer between 0 and 4. bwp-Id 0 is used only for the BWP indicated in SIB1. bwp-Id1 to 4 can be used for the BWP indicated in the RRCReconfiguration message.

BWP-DownlinkCommon contains the following information: frequency domain location and bandwidth of this bandwidth portion, subcarrier spacing to be used by this BWP, cell specific parameters for PDCCH of this BWP, cell specific parameters for PDSCH of this BWP.

BWP-UplinkCommon contains the following information: frequency domain location and bandwidth of this bandwidth portion, subcarrier spacing to be used by this BWP, cell specific parameters for PUCCH of this BWP, cell specific parameters for PUSCH of this BWP, cell Specific random access parameters.

BWP-DownlinkDedicated is used to configure dedicated (UE specific) parameters of the downlink BWP. This includes cell specific parameters for PDCCH of this BWP, cell specific parameters for PDSCH of this BWP.

BWP-UplinkDedicated is used to configure dedicated (UE specific) parameters of uplink BWP.

firstActiveDownlinkBWP-Id includes the ID of the DL BWP to be activated when RRC (re)configuration is performed.

defaultDownlinkBWP-Id is the ID of the downlink bandwidth portion to be used when the BWP inactivity timer expires.

bwp-InactivityTimer is the duration in ms after the UE falls back to the default bandwidth portion.

1e is a diagram showing the structure of ServingCellConfigCommonSIB included in SIB1.

SIB1 (1e-03) includes ServingCellConfigCommonSIB (1e-05). ServingCellConfigCommonSIB includes one DownlinkConfigCommonSIB (1e-07) and two UplinkConfigCommonSIBs. One UplinkConfigCommonSIB (1e-09) is for normal uplink (NUL) and another UplinkConfigCommonSIB (1e-11) is for supplementary uplink (SUL). UplinkConfigCommonSIB (1e-09) for NUL is located before UplinkConfigCommonSIB (1e-11) for SUL.

DownlinkConfigCommonSIB includes FrequencyInfoDL-SIB and BWP-DownlinkCommon (1e-13). BWP-DownlinkCommon is for initial DL BWP and includes PDCCH-ConfigCommon (1e-15) and PDSCH-ConfigCommon (1e-17).

UplinkConfigCommonSIB includes FrequencyInfoUL-SIB, TimeAlignmentTimer (1e-21) and BWP-UplinkCommon (1e-23). BWP-UplinkCommon is for initial UL BWP. BWP-UplinkCommon includes RACH-ConfigCommon (1e-25), PUSCH-ConfigCommon (1e-27), PUCCH-ConfigCommon (1e-29), and a plurality of RACH-ConfigCommon_fc (1e-31).

DownlinkConfigCommonSIB is a common downlink configuration of the serving cell. It consists of sub-fields such as FrequencyInfoDL-SIB and BWP-DownlinkCommon.

FrequencyInfoDL-SIB is a basic parameter of a downlink carrier. It consists of sub-fields such as frequency band list and carrier bandwidth for each SCS.

BWP-DownlinkCommon is a configuration of the second downlink initial BWP. It consists of sub-fields such as BWP, PDCCH-ConfigCommon, and PDSCH-ConfigCommon. The first initial BWP has a frequency domain corresponding to the first CORESET#0 of the MIB and has a subcarrier spacing indicated in the MIB. The first initial BWP is an initial BWP indicated by MIB and receiving SIB1, and the second initial BWP is an initial BWP indicated by SIB1 and receiving SIB2, paging, random access response message, etc.

BWP is an IE that configures the general parameters of BWP. It consists of sub-fields such as locationAndBandwidth, which indicates the bandwidth and location of BWP, and subcarrierSpacing, which indicates SCS of BWP.

PDCCH-ConfigCommon is a cell specific PDCCH parameter for this BWP. It consists of subfields such as controlResourceSetZero, commonControlResourceSet, searchSpaceZero, commonSearchSpaceList, searchSpaceOtherSystemInformation, pagingSearchSpace, and ra-SearchSpace.

controlResourceSetZero is defined as an integer between 0 and 15. Indicates one of the predefined CORESET#0 configurations. ControlResourceSetZero included in MIB corresponds to first CORESET#0, and controlResourceSetZero included in PDCCH-ConfigCommon of servingCellConfigCommon of SIB1 corresponds to second CORESET#0.

searchSpaceZero is defined as an integer between 0 and 15. Indicates one of the predefined SS#0 configurations. searchSpaceZero included in MIB corresponds to 1st SS#0, and controlResourceSetZero included in PDCCH-ConfigCommon of servingCellConfigCommon of SIB1 corresponds to 2nd SS#0.

commonControlResourceSet is a common CORESET defined as ControlResourceSet IE. Defines additional CORESETs that can be used for paging reception, random access response reception, system information reception, etc.

commonSearchSpaceList is a list of common SSs. The common SS may be used for paging reception, random access response reception, system information reception, and the like.

searchSpaceOtherSystemInformation is defined as SS identifier IE. If it is 0, it indicates the second SS#0, and if it is a value other than 0, it indicates one of the SSs defined in commonSearchSpaceList.

pagingSearchSpace is defined with the SS identifier IE. If it is 0, it indicates the second SS#0, and if it is a value other than 0, it indicates one of the SSs defined in commonSearchSpaceList.

ra-SearchSpace is defined as the SS identifier IE. If it is 0, the second SS#0 is displayed, and if it is a value other than 0, one of the SSs defined in commonSearchSpaceList is displayed.

PDSCH-ConfigCommon consists of pdsch-TimeDomainAllocationList as the cell specific PDSCH parameter of this BWP. The pdsch-TimeDomainAllocationList is a list composed of a plurality of pdsch-TimeDomainAllocations.

pdsch-TimeDomainAllocation configures the time domain relationship between PDCCH and PDSCH. It consists of sub-fields such as K0 and startSymbolAndLength. K0 is the slot offset between DCI and scheduled PDSCH. startSymbolAndLength is an index indicating a valid start symbol and length combination.

pcch-Config is a configuration related to paging. It consists of sub-fields such as base station paging cycle, PF-related parameters, and PO-related parameters.

bcch-config is a configuration related to system information. It consists of sub-fields such as modificationPeriodCoeff indicating the length of the modification period.

UplinkConfigCommonSIB is a common uplink configuration of the serving cell. It consists of subfields such as frequencyInfoUL, initialUplinkBWP, and timeAlignmentTimerCommon.

FrequencyInfoUL-SIB is a basic parameter of an uplink carrier. It consists of sub-fields such as frequency band list and carrier bandwidth for each SCS.

BWP-UplinkCommon is a configuration of the second uplink initial BWP. Consists of subfields such as BWP, rach-ConfigCommon, pusch-ConfigCommon, and pucch-ConfigCommon.

rach-ConfigCommon is a cell specific random access parameter for this BWP. It consists of subfields such as prach-ConfigurationIndex, msg1-FrequencyStart, preambleReceivedTargetPower, ra-ResponseWindow, preambleTransMax, msg1-SubcarrierSpacing, rsrp-ThresholdSSB, rsrp-ThresholdSSB-SUL, and ra-ContentionResolutionTimer.

prach-ConfigurationIndex is the PRACH configuration index. One PRACH configuration corresponds to pattern information on PRACH transmission opportunities in the time domain (information indicating that PRACH transmission is possible in which symbol in which slot of which radio frame) and the transmission format of the preamble.

msg1-FrequencyStart is an offset from PRB0 of the lowest PRACH transmission opportunity. This is information indicating PRACH transmission resources in the frequency domain. PRB0 is the lowest frequency PRB among PRBs of the corresponding carrier.

preambleReceivedTargetPower is the target power level of the network receiving end. This is a parameter related to transmission power control during the random access procedure.

ra-ResponseWindow is the length of the random access response window represented by the number of slots.

preambleTransMax is the maximum number of random access preamble transmissions

msg1-SubcarrierSpacing. is the SCS of PRACH. Commonly applied to general terminals and RedCap UEs.

rsrp-ThresholdSSB is an SSB selection criterion. The UE performs random access by selecting a preamble corresponding to the selected SSB.

rsrp-ThresholdSSB-SUL is the SUL selection criterion. The UE selects an SUL carrier for random access based at least in part on this threshold.

ra-ContentionResolutionTimer is an initial value of the contention resolution timer. Displays the number of subframes.

push-ConfigCommon is a cell-specific PUSCH parameter of this BWP and consists of sub-fields such as push-TimeDomainAllocationList. The push-TimeDomainAllocationList is a list composed of a plurality of push-TimeDomainAllocations.

pushch-TimeDomainAllocation constitutes a time domain relationship between PDCCH and PUSCH. It consists of sub-fields such as K2 and startSymbolAndLength. K2 is the slot offset between DCI and scheduled PUSCH. startSymbolAndLength is an index representing a valid combination of start symbol and length.

pucch-ConfigCommon is a cell specific PUCCH parameter for this BWP. It consists of sub-fields such as pucch-ResourceCommon and p0-norminal.

pucch-ResourceCommon is an index corresponding to a cell-specific PUCCH resource parameter. One index corresponds to a PUCCH format, a PUCCH time period, a PUCCH frequency period, a PUCCH code, and the like.

p0-normal is a power offset applied during PUCCH transmission. It is defined as an integer between -202 and 24 in increments of 2. Unit is dBm.

timeAlignmentTimerCommon is a timer applied when the UE performs random access for RRC connection establishment procedure and RRC connection re-establishment procedure. When the UE receives the RAR, it starts driving the timer, and stops driving the timer when contention fails.

tdd-UL-DL-ConfigurationCommon is a cell specific TDD UL/DL configuration. It consists of subfields such as referenceSubcarrierSpacing, pattern1, and pattern2.

referenceSubcarrierSpacing is a reference SCS used to determine the time domain boundary in the UL-DL pattern.

pattern1 and pattern2 are TDD uplink and downlink patterns. It consists of subfields such as dl-UL-TransmissionPeriodicity, nrofDownlinkSlots, nrofDownlinkSymbols, nrofUplinkSlots, and nrofUplinkSymbols.

dl-UL-TransmissionPeriodicity indicates a period of a DL-UL pattern.

nrofDownlinkSlots indicates the number of consecutive full DL slots in each DL-UL pattern.

nrofDownlinkSymbols indicates the number of consecutive DL symbols from the start of the slot following the last full DL slot.

nrofUplinkSlots indicates the number of consecutive full UL slots in each DL-UL pattern.

nrofUplinkSymbols indicates the number of consecutive UL symbols at the end of the slot before the first full UL slot.

1F shows an example of a feature combination (also referred to as a feature combination) supported by a cell.

A single cell can support multiple functions (also called features) such as RedCap, SDT, Coverage Enhancement and various slices.

Some of them may be used together by one UE. The network can partition RACH resources and related parameters by feature combination to achieve load balancing and better performance. For example, if the RACH resource is partitioned into RedCap, the reduced capability can be indicated to the network in MSG1 so that the network can adapt to subsequent transmissions. If the RACH resource is divided into SDT, a larger MSG3 size can be requested.

One problem is that the network may not be able to provide all possible combinations due to lack of RACH resources. Another problem is that there can be quite a number of feature combinations supported in one cell.

In order to solve this problem, the present disclosure provides a method and apparatus for providing related information about RACH partitioning to a UE in an efficient manner. Signaling load and UE processing load are reduced by defining RACH-related parameters to be jointly applied to a plurality of feature combinations and RACH-related parameters to be applied singly to one feature combination.

A network slice consists of a RAN part and a CN part. The support of network slicing relies on the principle that traffic for different slices is handled in different PDU sessions. The network can provide scheduling and other L1/L2 configurations to realize different network slices.

Each network slice is uniquely identified by S-NSSAI. Network Slice Selection Assistance Information (NSSAI) includes one or a list of Single NSSAI (S-NSSAI). S-NSSAI is a combination of:

- Mandatory SST (Slice/Service Type) field, which identifies the slice type and consists of 8 bits (range 0-255).

- An optional Slice Differentiator (SD) field distinguishes slices having the same SST field and consists of 24 bits.

The list includes up to 8 S-NSSAIs.

The UE provides NSSAI (Network Slice Selection Assistance Information) for network slice selection in RRCSetupComplete when provided by the NAS. The network can support a large number of slices (hundreds), but the UE need not support more than 8 slices at the same time.

Network slice is a concept that enables differentiated treatment according to each customer's requirements.

Feature combinations and RACH partitions are described as examples. The network is a combination of features from RedCap and CovEnh (or MSG3 iteration or CE) and slice 1 (1f-03) and a combination of features from CovEnh and CovEnh and slice 2 (1f-05) plus SDT and slice 2 (1f-07)). Provide feature combinations and slice 3 (1f-09) feature combinations. The network provides three RACH partitions. The network maps the first feature combination and the second feature combination with RACH partition 1 (1f-11). The network maps the third feature combination with RACH partition 2 (1f-13). The network maps the fourth feature combination with RACH partition 3 (1f-15). One of the RACH partitions may be configured as a primary RACH partition.

A RACH triggered for either the first feature combination or the second feature combination uses RACH partition 1. The RACH triggered for the third feature combination uses RACH partition 2. The RACH triggered for the fourth feature combination uses RACH partition 3. RACHs triggered for other feature combinations (or RACHs for SI requests) use the default RACH partition.

Figure 1g is a diagram showing an alternative structure of BWP-UplinkCommon included in SIB1 or downlink RRC message.

BWP-UplinkCommon (1g-03) includes rach-ConfigCommon, push-ConfigCommon, pucch-ConfigCommon and 0 or 1 or 2 or more additional Rach-ConfigCommon IEs. addionalRach-ConfigCommon is included in the extended part of BWP-UplinkCommon. Other IEs are included in the non-extended part of BWP-UplinkCommon. The extended portion is placed after the non-expanded portion.

AdditionalRACH-ConfigCommon (1g-05) consists of AdditionalRACH-ConfigIndex (or RACH-Id) and rach-ConfigCommon.

The rach-ConfigCommon in the non-expanded part of BWP-UplinkCommon is the first rach-ConfigCommon. The rach-ConfigCommon (rach-ConfigCommon of AdditionalRACH-ConfigCommon) in the extension part of BWP-UplinkCommon is the second rach-ConfigCommon.

Legacy UE understands the IE of the non-extension part and does not understand the IE of the extension part.

rach-ConfigCommon (1g-07) includes the following IEs in the non-extended part: totalNumberOfRA-Preambles, ra-Msg3SizeGroupA, messagePowerOffsetGroupB, numberOfRA-PreamblesGroupA, rsrp-ThresholdSSB, ra-ResponseWindow, ra-ContentionResolutionTimer, preambleReceivedTargetPower, etc.

rach-ConfigCommon (1g-07) additionally includes 0, 1, or 2 or more featureCombinationParameters (1g-09) in the extension part.

featureCombinationParameter is selectively present in the first rach-ConfigCommon and necessarily present in the second rach-ConfigCommon.

totalNumberOfRA-Preambles is the total number of preambles used for contention-based and contention-free step 4 or step 2 random access in RACH resources defined in RACH-ConfigCommon, excluding preambles used for other purposes (e.g., SI request). This IE is selectively present in the first rach-ConfigCommon and absent in the second rach-ConfigCommon.

totalNumberOfRA-Preambles is an integer between 1 and 63. If totalNumberOfRA-Preambles is not present in the first rach-ConfigCommon, all 64 preambles can be used for random access.

When totalNumberOfRA-Preambles is not present in the second rach-ConfigCommon, the number of preambles usable for random access is displayed in featureCombinationParameter.

The next IE of the non-extension part of RACH-ConfigCommon (hereafter the first IE) is applied to multiple feature combinations (or RACH partitions) of the extension part of RACH-ConfigCommon. msg1-SubcarrierSpacing, ra-ContentionResolutionTimer, prach-ConfigurationIndex, msg1-FDM, msg1-FrequencyStart, tdd-UL-DL-ConfigurationCommon.

The following IEs of the non-extension part of RACH-ConfigCommon (hereinafter the second IE) do not apply to multiple feature combinations (or RACH partitions) of the extension part of RACH-ConfigCommon: ra-Msg3SizeGroupA, messagePowerOffsetGroupB, numberOfRA-PreamblesGroupA.

For each feature combination (or RACH partition), the second IE of the corresponding featureCombinationParameter is applied.

The following IEs of the non-extension part of RACH-ConfigCommon (hereafter the third IE) are conditionally applied to multiple feature combinations (or RACH partitions) of the extension part of RACH-ConfigCommon: rsrp-ThresholdSSB, preambleReceivedTargetPower, preambleTransMax, ra-ResponseWindow , ra-ContentionResolutionTimer.

If a feature combination includes a third IE, the third IE of the feature combination is applied to the feature combination. If the third IE is not included in the feature combination, the third IE in the non-expanded part applies to that feature combination.

featureCombinationParameter (1g-09) contains the following IEs: featureCombination, startPreambleForThisPartition, nrofPreamblesForThisPartition, numberOfRA-PreamblesGroupA, rsrp-threshold1, rsrp-threshold2, ra-Msg3SizeGroupA, messagePowerOffsetGroupB, rsrp-ThresholdSSB, preambleReceivedTargetPower, preambleTransMax, etc.

startPreambleForThisPartition defines the first preamble associated with the feature combination. startPreambleForThisPartition is an integer between 1 and 64.

nrofPreamblesForThisPartition determines the number of consecutive preambles associated with the feature combination starting from the starting preamble. nrofPreamblesForThisPartition is an integer between 1 and 64. Both nrofPreamblesForThisPartition and totalNumberOfRA-Preambles indicate the number of preambles. The maximum number (i.e. 64) is implicitly indicated in totalNumberOfRA-Preambles and explicitly indicated in nrofPreamblesForThisPartition.

numberOfRA-PreamblesGroupA determines how many consecutive preambles are associated with group A starting with the start preamble(s). The remaining preambles associated with feature combinations are associated with group B.

Regarding rsrp-threshold1, the UE can use the preamble defined by this feature combination and the RACH opportunity defined by the corresponding RACH-ConfigCommon only when the RSRP of the downlink path loss reference is lower than this threshold. If not present, the value is infinity.

Regarding rsrp-threshold2, the UE can use the preamble defined by this feature combination and the RACH opportunity defined by the corresponding RACH-ConfigCommon only when the RSRP of the downlink path loss reference is higher than this threshold. If not present, the value is minus infinity.

If both rsrp-threhold1 and rsrp-threshold2 are satisfied, the UE uses the preamble defined by this feature combination and the RACH opportunity defined by the corresponding RACH-ConfigCommon.

Only one of rsrp-threshold1 and rsrp-threshold2 can exist in featureCombinationParameter.

If rsrp-threshold1 and rsrp-threshold2 do not exist, the UE can use the RACH opportunity defined by the corresponding RACH-ConfigCommon and the preamble defined by this feature combination regardless of the RSRP of the downlink path loss reference.

If rsrp-threshold1 is present and rsrp-threshold2 is not present, the UE uses the RACH opportunity defined by the corresponding RACH-ConfigCommon and the preamble defined by this feature combination if the RSRP of the downlink path loss reference is higher than rsrp-threshold1. can be used

If rsrp-threshold1 does not exist and rsrp-threshold2 does exist, the UE, if the RSRP of downlink path loss reference is lower than rsrp-threshold2, the RACH opportunity defined by the corresponding RACH-ConfigCommon and the preamble defined by this feature combination can be used.

Figure 2a illustrates the operation of the UE and GNB for a random access procedure.

Random access preamble and preamble are used interchangeably.

After switching on, the UE performs cell selection and camps on an appropriate cell.

At 2a-13, UE 2a-01 receives SIB1 on the appropriate cell. GNB (2a-05) includes various information in SIB1. SIB1 includes information related to the UE's ability to access the cell and defines scheduling of other system information. It also includes radio resource configuration information common to all UEs. It also includes radio resource configuration information common to feature combinations.

Configuration information related to random access includes ra-SearchSpace, pdsch-TimeDomainAllocationList, rach-ConfigCommon, pucch-ResourceCommon, p0-norminal, tdd-UL-DL-ConfigurationCommon, and push-TimeDomainAllocation.

ra-SearchSpace is included in PDCCH-ConfigCommon (1e-15). pdsch-TimeDomainAllocationList is included in PDSCH-ConfigCommon (1e-17). pucch-ResourceCommon and p0-norminal are included in PUCCH-ConfigCommon (1e-29). push-TimeDomainAllocation is included in PUSCH-ConfigCommon (1e-27).

Configuration information related to random access may be provided for each RACH partition (or feature combination) in one of two ways. In the first method, one IE, for example, RACH-ConfigCommon_fc, is defined for each RACH partition (or feature combination), and all configuration information related to random access of the corresponding RACH partition (or feature combination) is stored in the RACH-ConfigCommon_fc. include

In the second method, one IE, for example, RACH-ConfigCommon_fc, is defined for each RACH partition (or feature combination), but some of the configuration information related to random access of the corresponding RACH partition (or feature combination) is included in the RACH-ConfigCommon_fc , and the rest are included in PDCCH-ConfigCommon (1e-15), PDSCH-ConfigCommon (1e-17), PUCCH-ConfigCommon (1e-29), and PUSCH-ConfigCommon (1e-27).

RACH-ConfigCommon_fc contains the following IEs: rach_ConfigCommon, rach-ConfigID, featureCombinationList, prioritizedFeature

rach-ConfigID is the identifier/index of this RACH partition configuration (or this additional RACH configuration). Also called RACH id.

featureCombinationList consists of one or more featureCombinations.

featureCombination represents a feature combination to which this RACH configuration is applied. The featureCombination IE includes a redCap field, a smallData field, a covEnh field, and a slicing field. The redCap field/ smallData field/ covEnh field are 1 bit enumerated as a single value of "true". If the corresponding field is present, it indicates that redCap terminal/small data transmission/coverage enhancement is one of the functions of this feature combination.

The slicing field is a bitmap. The first bit of the bitmap corresponds to the first slice indicated in a specific field of a specific system information block. The second bit of the bitmap corresponds to the second slice indicated in the specific field of the specific system information block. The specific field is a list of slice identifiers supported in this cell. A slice identifier may be S-NSSAI or ST. The specific system information may be system information block 1, system information block 2, or system information block 3.

The redCap field, smallData field, covEnh field, and slicing field are optional fields.

Each slice of the plurality of slices indicated in featureCombination actually creates an additional feature combination. For example, if the featureCombination field contains slicing fields representing slice x and slice y (a bitmap with one bit for slice x and one bit for slice y set to 1 and the other bit set to 0), there are effectively two A feature combination is created. A feature combination for slice x with the same single-value field set to the same value as the original feature combination, and a feature combination for slice y with the same single-value field set to the same value as the original feature combination.

The prioritizedFeature is a feature that is prioritized when the target feature combination does not match any feature combination of a specific BWP of the selected uplink.

A plurality of RACH-ConfigCommons may be included in the BWP-UplinkCommon (1e-23). The first RACH-ConfigCommon (1e-25) is placed in the first part of BWP-UplinkCommon. The first RACH-ConfigCommon is not explicitly associated with rach-ConfigID but is implicitly associated with rach-ConfigID 0. The second RACH-ConfigCommon included in RACH-ConfigCommon_fc (1e-31) is associated with an explicit rach-ConfigID. A second RACH-ConfigCommon associated with an explicit rach-ConfigID is placed in the second part of BWP-UplinkCommon. The second part is the extension part of BWP-UplinkCommon. The second part is placed after the first part.

Upon receiving the information, the UE applies the timeAlignmentTimerCommon received from SIB1 to timeAlignmentTimer prior to starting transmission of a predetermined uplink RRC message.

The predetermined uplink RRC message may be RRCSetupRequest, RRCReestablishmentRequest, or RRCResumeRequest. RRC_IDLE UE transmits RRCSetupRequest message to establish RRC connection. RRC_INACTIVE The UE transmits the RRCResumeRequest message to resume the RRC connection. RRC_CONNECTED The terminal transmits an RRCReestablishmentRequest message to re-establish the RRC connection.

When transmission of the uplink RRC message is initiated, a random access procedure is initiated.

In 2a-15, the UE selects an uplink on which a random access procedure is to be performed based at least in part on the rsrp-ThresholdSSB-SUL indicated in the first RACH-ConfigCommon of NUL (Normal Uplink).

If the RSRP of the downlink path loss reference is less than rsrp-ThresholdSSB-SUL, the UE selects a NUL 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 a SUL (Supplementary Uplink) carrier to perform the random access procedure.

The downlink path loss reference may be an SSB having the best RSRP among SSBs of the cell. Alternatively, any SSB of the cell may be a downlink path loss reference.

When selecting the UL, the UE may use rsrp-ThresholdSSB-SUL included in the first RACH-ConfigCommon of the SUL. GNB may set the same value for rsrp-ThresholdSSB-SUL included in RACH-ConfigCommon of SUL and rsrp-ThresholdSSB-SUL included in RACH-ConfigCommon of NUL. GNB does not include rsrp-ThresholdSSB-SUL in the second RACH-ConfigCommon of NUL and the second RACH-ConfigCommon of SUL.

Alternatively, GNB sets the same value for all rsrp-ThresholdSSB-SULs included in UplinkConfigCommonSIB (1e-09) for NUL and all rsrp-ThresholdSSB-SULs included in UplinkConfigCommonSIB (1e-11) for SUL, The terminal may use any of these.

In 2a-16, the UE determines whether to use Msg 3 repetition mode (CovEnh) and SDT. When rsrp-ThresholdSSB-CE exists in the first RACH-ConfigCommon of the selected uplink and RSRP of downlink path loss reference is lower than rsrp-ThresholdSSB-CE, the UE determines to use Msg 3 repetition mode. If rsrp-ThresholdSSB-CE does not exist in the first RACH-ConfigCommon of the selected uplink or if the RSRP of the downlink path loss reference is higher than rsrp-ThresholdSSB-CE, the UE determines not to use the Msg 3 repetition mode.

If rsrp-ThresholdSSB-SDT exists in the first RACH-ConfigCommon of the selected uplink, RSRP of downlink path loss reference is higher than rsrp-ThresholdSSB-SDT, and SDT is triggered by a higher layer, the UE uses SDT to decide If rsrp-ThresholdSSB-SDT does not exist in the first RACH-ConfigCommon of the selected uplink or if RSRP of downlink path loss reference is lower than rsrp-ThresholdSSB-SDT, the UE determines not to use SDT.

GNB sets rsrp-ThresholdSSB-SDT to be higher than rsrp-ThresholdSSB-CE.

If it is determined to use the Msg 3 repetition mode, the UE includes CovEnh in the target feature combination for the corresponding RACH. For example, if the RedCap terminal triggers the RACH and decides to use the Msg 3 repetition mode, the target feature combination is [RedCap AND CovEnh].

If it is determined to use the SDT, the UE includes the SDT in the target feature combination for the corresponding RACH. For example, if the UE triggers RACH for slice x traffic and decides to use SDT, the target feature combination is [SDT AND slice x].

In 2a-17, the UE selects the RACH partition (or RACH-ConfigCommon) in consideration of the target feature combination and the feature combination of RACH partitions.

The target feature combination means a feature combination that triggers RACH. For example, if random access for SDT is triggered in a RedCap terminal, the target feature combination is [RedCap AND SDT]. The UE performs RACH partition (or RACH-ConfigCommon) selection for feature combinations indicated in the UplinkConfigCommonSIB of a specific BWP of the selected carrier.

For example, there are 3 RACH-ConfigCommon-fc, and each featureCombination is as follows: RACH-ConfigCommon-fc-1 = [RedCap AND CovEnh AND Slice1 OR Slice2] = [RedCap AND CovEnh AND Slice1] OR [ RedCap AND CovEnh AND Slice2], RACH-ConfigCommon-fc-2 = [SDT AND Slice2], RACH-ConfigCommon-fc-3 = [Slice3].

<How to select RACH partition (or RACH-ConfigCommon)>

1: Select a candidate feature combination that is a superset of the target feature combination. If all features of feature set 1 are included in feature set 2, then feature set 2 is a superset of feature set 1.

2: Among candidate feature combinations, a feature combination closest to the target feature combination and a related RACH partition are selected.

3: If a superset feature combination does not exist, a feature combination in which at least one of the features of the target feature combination is a prioritized feature is selected.

4: Select default RACH-ConfigCommon if there is no feature combination that matches the prioritized feature.

If the target feature combination is [RedCap AND Slice1], since [RedCap AND CovEnh AND Slice1], a feature combination of RACH-ConfigCommon-fc-1, is a superset feature combination of the target feature combination, the terminal selects RACH-ConfigCommon-fc-1. do.

If the target feature combination is [RedCap AND SDT], there is no superset feature combination. For example, if the prioritizedFeature of RACH-ConfigCommon-fc-2 is SDT, the UE can select RACH-ConfigCommon-fc-2.

The first RACH-ConfigCommon is the default RACH-ConfigCommon.

Selecting a certain RACH-ConfigCommon-fc means selecting a feature combination associated with that RACH-Configcommon-fc.

In 2a-19, the UE selects an SSB based at least in part on the rsrp-ThresholdSSB.

The UE uses the rsrp-ThresholdSSB of the selected RACH partition (or feature combination). For example, if the UE selects the default RACH-ConfigCommon, the UE applies the rsrp-ThresholdSSB of the first RACH-ConfigCommon. If the UE selects the n-th RACH-ConfigCommon-fc, the UE applies the rsrp-ThresholdSSB of the second RACH-ConfigCommon included in the n-th RACH-ConfigCommon-fc.

In 2a-21, the UE selects a preamble group based at least in part on the selected RACH partition (or feature combination).

A total of 64 preambles are defined. They can be divided into two groups. A UE with large data and good channel conditions may select Preamble Group B so that the GNB can allocate a larger UL grant. A UE with small data or poor channel conditions may select Preamble Group A so that the GNB can allocate a general UL grant.

If the potential Msg3 size (transportable UL data, MAC subheader(s) and MAC CE if necessary) is greater than ra-Msg3SizeGroupA and the path loss is PCMAX (of the serving cell performing random access procedure) preambleReceivedTargetPower, msg3-DeltaPreamble and If it is less than the value obtained by subtracting messagePowerOffsetGroupB, the UE selects random access preamble group B.

If the random access procedure is initiated for the CCCH logical channel and the CCCH SDU size and MAC subheader are greater than ra-Msg3SizeGroupA, the UE selects random access preamble group B.

If the random access procedure is not initiated for the CCCH logical channel and the potential Msg3 size (UL data available for transmission and MAC subheader(s) and MAC CE if necessary) is not greater than ra-Msg3SizeGroupA, the UE sends a random access preamble Choose group A.

If the random access procedure is initiated for the CCCH logical channel and the potential Msg3 size (UL data available for transmission + MAC subheader(s) and MAC CE if necessary) is not greater than ra-Msg3SizeGroupA, the UE selects random access preamble group A Choose

No random access procedure has been initiated for the CCCH logical channel, the potential Msg3 size (UL data available for transmission plus MAC subheader(s) and MAC CE if necessary) is greater than ra-Msg3SizeGroupA, and the path loss is PCMAX (random access If not smaller than the subtraction of preambleReceivedTargetPower, msg3-DeltaPreamble and messagePowerOffsetGroupB from (of the serving cell performing the procedure), the UE selects random access preamble group A.

One msg3-DeltaPreamble may be included in the first part of PUSCH-ConfigCommon, and multiple msg3-DeltaPreambles may be included in the second part. msg3-DeltaPreamble of the second part is a parameter for featureCombination/RACH partition/second RACH-ConfigCommon. The second part is an extension part and is located behind the first part.

Alternatively, RACH-ConfigCommon-fc may include msg3-DeltaPreamble to be applied to the corresponding featureCombination. If the UE selects the default RACH-ConfigCommon, the UE selects a random access preamble group using msg3-DeltaPreamble of PUSCH-ConfigCommon and Msg3SizeGroupA, preambleReceivedTargetPower, and messagePowerOffsetGroupB of the first RACH-ConfigCommon. If msg3-DeltaPreamble is not included in PUSCH-ConfigCommon, the UE uses 0.

If the UE selects the nth RACH-ConfigCommon-fc, the UE selects msg3-DeltaPreamble included in the RACH-ConfigCommon-fc and Msg3SizeGroupA, preambleReceivedTargetPower, and messagePowerOffsetGroupB included in the second RACH-ConfigCommon included in the RACH-ConfigCommon-fc. Select a random access preamble group using If msg3-DeltaPreamble is not included in the RACH-ConfigCommon-fc, the UE uses 0.

If the UE selects the nth RACH-ConfigCommon-fc, the UE selects the nth msg3-DeltaPreamble of the second part of PUSCH-ConfigCommon and Msg3SizeGroupA, preambleReceivedTargetPower, and messagePowerOffsetGroupB of the second RACH-ConfigCommon included in the RACH-ConfigCommon-fc. to select a random access preamble group.

The UE randomly selects a preamble with equal probability from among the preambles associated with the selected SSB and the selected preamble group. The UE sets PREAMBLE_INDEX to ra-PreambleIndex corresponding to the selected preamble.

The UE determines the next available PRACH opportunity from the PRACH opportunity corresponding to the selected SSB. The UE shall randomly select a PRACH opportunity with equal probability among consecutive PRACH opportunities indicated by the PRACH configuration index of the selected RACH-ConfigCommon of the specific BWP of the selected uplink. The specific BWP is an initial uplink BWP.

In 2a-23, the UE transmits the selected preamble on the selected PRACH opportunity in the selected uplink.

The UE sets PREAMBLE_RECEIVED_TARGET_POWER as preambleReceivedTargetPower + DELTA_PREAMBLE + (PREAMBLE_POWER_RAMPING_COUNTER - 1) × powerRampingStep + POWER_OFFSET_2STEP_RA.

The UE sets the transmit power of the preamble as the sum of PREAMBLE_RECEIVED_TARGET_POWER and path loss.

If the UE selects the default RACH-ConfigCommon, the UE uses preambleReceivedTargetPower and powerRampingStep of the first RACH-ConfigCommon. The UE sets POWER_OFFSET_2STEP_RA to 0. The UE sets DELTA_PREAMBLE according to the preamble format determined from the prach-ConfigurationIndex indicated in the first RACH-ConfigCommon. DELTA_PREAMBLE is predefined for each preamble format. PREAMBLE_POWER_RAMPING_COUNTER is initialized to 1 and incremented by 1 for each preamble transmission.

If the UE selects the nth RACH-ConfigCommon-fc, the UE uses the preambleReceivedTargetPower and powerRampingStep of the second RACH-ConfigCommon of the RACH-ConfigCommon-fc. The UE sets POWER_OFFSET_2STEP_RA to 0. The UE sets DELTA_PREAMBLE according to the preamble format determined from the prach-ConfigurationIndex indicated in the second RACH-ConfigCommon. DELTA_PREAMBLE is predefined for each preamble format. PREAMBLE_POWER_RAMPING_COUNTER is initialized to 1 and incremented by 1 for each preamble transmission.

In 2a-25, the UE receives an uplink grant in RAR.

To receive the RAR, the UE starts the ra-ResponseWindow configured in the RACH-ConfigCommon at the first PDCCH opportunity after the random access preamble transmission ends. The UE monitors SpCell's PDCCH for random access response(s) identified by RA-RNTI while ra-ResponseWindow is running.

In PDCCH monitoring, the UE applies the searchSpace indicated by ra-SearchSpace.

A set of PDCCH candidates to be monitored by the UE is defined as a PDCCH search space set. The search space set may be a Common Search Space (CSS) set or a UE Search Space (USS) set. The UE monitors PDCCH candidates in a search space set by ra-SearchSpace of PDCCH-ConfigCommon or ra-SearchSpace of second rach-ConfigCommon.

One ra-SearchSpace may be included in the first part of PDCCH-ConfigCommon, and multiple ra-SearchSpaces may be included in the second part. ra-SearchSpace of the second part is a parameter for featureCombination/RACH partition/second RACH-ConfigCommon. The second part is an extension part and is located behind the first part.

Alternatively, RACH-ConfigCommon-fc may include ra-SearchSpace to be applied to the corresponding featureCombination.

If the UE selects the default RACH-ConfigCommon, the UE monitors the RA-RNTI by applying the ra-SearchSpace of the first part of the PDCCH-ConfigCommon.

If the UE selects the n-th RACH-ConfigCommon-fc, the UE monitors the RA-RNTI by applying the ra-SearchSpace included in the n-th RACH-ConfigCommon-fc.

If the UE selects the n-th RACH-ConfigCommon-fc, the UE monitors the RA-RNTI by applying the n-th ra-SearchSpace of the second part of the PDCCH-ConfigCommon.

The UE considers that the random access response has been received successfully when the random access response includes a MAC subPDU having a random access preamble identifier corresponding to the transmitted PREAMBLE_INDEX.

MAC subPDU includes MAC RAR. MAC RAR includes fields such as Timing Advance Command, Uplink Grant and Temporary C-RNTI. The Timing Advance Command field indicates an index value used to control the amount of timing adjustment that the UE should apply. The size of the Timing Advance Command field is 12 bits. The UE adjusts uplink transmission timing based on the Timing Advance Command field and starts timeAlignmentTimer. The timeAlignmentTimer is set to timeAlignmentTimerCommon, and the same timeAlignmentTimerCommon is applied to all feature combinations of one uplink. The Uplink Grant field indicates resources to be used in uplink. The size of the UL Grant field is 27 bits. Temporary C-RNTI field indicates a temporary ID used by the UE during random access. The size of the temporary C-RNTI field is 16 bits.

The uplink grant field further includes a PUSCH time resource allocation field. The PUSCH time resource allocation field is 4 bits.

One first push-TimeDomainAllocationList may be included in the first part of PUSCH-ConfigCommon, and a plurality of second push-TimeDomainAllocationLists may be included in the second part. The second push-TimeDomainAllocationList of the second part is a parameter for featureCombination/RACH partition/second RACH-ConfigCommon. The second part is an extension part and is located behind the first part.

Alternatively, RACH-ConfigCommon-fc may include one second push-TimeDomainAllocationList to be applied to the corresponding featureCombination.

If the UE selects the default RACH-ConfigCommon, the UE determines the time domain relationship between the PDCCH and the PUSCH by using the first push-TimeDomainAllocationList of the PUSCH-ConfigCommon.

If the UE selects the nth RACH-ConfigCommon-fc, the UE determines the time domain relationship between the PDCCH and the PUSCH by using the second push-TimeDomainAllocationList included in the nth RACH-ConfigCommon-fc. If TimeDomainAllocationList is not included in the nth RACH-ConfigCommon-fc, the UE uses the first push-TimeDomainAllocationList of the first part of PUSCH-ConfigCommon or uses the default PUSCH time domain resource allocation table.

If the UE selects the nth RACH-ConfigCommon-fc, the UE determines the time domain relationship between the PDCCH and the PUSCH by using the nth second push-TimeDomainAllocationList of the second part of the PUSCH-ConfigCommon. If the nth second push-TimeDomainAllocationList does not exist in the second part, the UE uses the first push-TimeDomainAllocationList of the first part of PUSCH-ConfigCommon or uses the default PUSCH time domain resource allocation table.

The PUSCH time resource allocation field indicates push-TimeDomainResourceAllocation of push-TimeDomainResourceAllocationList included in PUSCH-ConfigCommon.

If PUSCH-ConfigCommon does not include push-TimeDomainResourceAllocationList, the PUSCH time resource allocation field indicates an indexed column of the default PUSCH time domain resource allocation table illustrated in the table below.

Row index K ₂ S L One j 0 14 2 j 0 12 3 j 0 10 4 j 2 10 5 j 4 10 6 j 4 8 7 j 4 6 8 j+1 0 14 9 j+1 0 12 10 j+1 0 10 11 j+2 0 14 12 j+2 0 12 13 j+2 0 10 14 j 8 6 15 j+3 0 14 16 j+3 0 10

j is a value specific to the PUSCH subcarrier spacing and is defined in the table below.

PUSCH subcarrier spacing j 15 kHz One 30 kHz One 60 kHz 2 120 kHz 3

When a UE transmits a PUSCH scheduled by RAR, a specific delta is applied to the PUSCH subcarrier interval in addition to k2. Delta is defined in the table below.

PUSCH subcarrier spacing delta 15 kHz 2 30 kHz 3 60 kHz 4 120 kHz 6

The UE determines K2 based at least in part on the value h indicated in the PUSCH Time Resource Allocation field.

When the terminal selects the default RACH-ConfigCommon and the PUSCH-ConfigCommon includes the first push-TimeDomainResourceAllocationList, h indicates the (h+1)th entry of the first push-TimeDomainResourceAllocationList.

When the UE selects the nth RACH-ConfigCommon-fc and the PUSCH-ConfigCommon includes the nth second push-TimeDomainResourceAllocationList, h indicates the (h+1)th entry of the nth second push-TimeDomainResourceAllocationList.

Alternatively, when the UE selects the n-th RACH-ConfigCommon-fc and the n-th RACH-ConfigCommon-fc includes the second push-TimeDomainResourceAllocationList, h indicates the (h+1)-th entry of the second push-TimeDomainResourceAllocationList .

Each item of push-TimeDomainResourceAllocationList (or each TimeDomainResourceAllocation of TimeDomainResourceAllocationList) is associated with k2. The UE determines k2 for PUSCH transmission by a k2 value related to push-TimeDomainResourceAllocation denoted by h.

When the UE selects the default RACH-ConfigCommon and the PUSCH-ConfigCommon does not include the first push-TimeDomainResourceAllocationList, h represents the row index (h+1) of the default PUSCH time domain resource allocation table.

When the UE selects the n-th RACH-ConfigCommon-fc and the PUSCH-ConfigCommon does not include the n-th second push-TimeDomainResourceAllocationList, h represents the row index (h+1) of the default PUSCH time domain resource allocation table.

Alternatively, when the UE selects the nth RACH-ConfigCommon-fc and the nth RACH-ConfigCommon-fc does not include the second push-TimeDomainResourceAllocationList, h is a row index (h+1) of the default PUSCH time domain resource allocation table indicates

Each row of the default PUSCH time domain resource allocation table is associated with k2, which is a function of j. and i. The UE determines j according to the PUSCH subcarrier spacing. The UE determines i based at least in part on h. The UE determines k2 by adding the determined j and the determined i. In other words, the UE determines k2 based at least in part on the row index determined based at least in part on j and h determined based at least in part on the PUSCH subcarrier spacing.

The PUSCH subcarrier spacing is determined by the subcarrier spacing IE included in the BWP-UplinkCommon IE. If the UE is in RRC_IDLE or RRC_INACTIVE, BWP-UplinkCommon is indicated in SIB1 and is for initial uplink BWP. If the UE is in RRC_CONNECTED, BWP-UplinkCommon is for the currently active uplink BWP.

The UE determines the time slot for PUSCH transmission scheduled by RAR. When the UE receives the PDSCH with the RAR message ending in slot n for the PRACH transmission from that UE, the UE transmits the PUSCH in slot (n + k2 + delta). k2 and delta are subcarrier spacing specific and are determined as follows.

If push-TimeDomainResourceAllocationList is not included in PUSCH-ConfigCommon of ServingCellConfigCommonSIB, k2 is determined based on h, j, and i. j is determined based at least in part on the subcarrier spacing IE included in the BWP-UplinkCommon IE of the ServingCellConfigCommonSIB. If the subcarrier spacing IE indicates 15 kHz or 30 kHz, j is 1. If the subcarrier spacing IE represents 60 kHz, j is 2. If the subcarrier spacing IE represents 120 kHz, j is 3.

Delta is determined based at least in part on the subcarrier spacing IE included in the BWP-UplinkCommon IE of the ServingCellConfigCommonSIB. If the subcarrier spacing IE indicates 15 kHz, the delta is 2. If the subcarrier spacing IE indicates 30 kHz, the delta is 3. If the subcarrier spacing IE indicates 60 kHz, the delta is 4. If the subcarrier spacing IE indicates 120 kHz, the delta is 6.

In step 2a-27, the UE performs Msg 3 transmission in the determined slot according to the UL grant in the received RAR.

The UE determines the PUSCH transmit power by summing the offset, path loss, and other parameters related to the number of PRBs and power control commands.

The offset is the sum of preambleReceivedTargetPower and msg3-DeltaPreamble.

One msg3-DeltaPreamble may be included in the first part of PUSCH-ConfigCommon, and multiple msg3-DeltaPreambles may be included in the second part. msg3-DeltaPreamble of the second part is a parameter for featureCombination/RACH partition/second RACH-ConfigCommon. The second part is an extension part and is located behind the first part.

Alternatively, RACH-ConfigCommon-fc may include msg3-DeltaPreamble to be applied to the corresponding featureCombination.

If the UE selects the default RACH-ConfigCommon, the UE uses msg3-DeltaPreamble of the PUSCH-ConfigCommon and preambleReceivedTargetPower of the first RACH-ConfigCommon.

If the terminal selects the nth RACH-ConfigCommon-fc, the terminal uses msg3-DeltaPreamble and preambleReceivedTargetPower included in the RACH-ConfigCommon-fc.

If the UE selects the nth RACH-ConfigCommon-fc, the UE uses the nth msg3-DeltaPreamble of the second part of the PUSCH-ConfigCommon and the preambleReceivedTargetPower included in the nth RACH-ConfigCommon-fc.

The UE generates Msg3. When SDT is applied, Msg3 (or MAC PDU scheduled by RAR) includes an RRC message and DRB data. RRC messages are not encrypted and DRB data is encrypted with a security key stored in the UE AS context. The RRC message is included in the first MAC SDU and the DRB data is included in the second MAC SDU. The first MAC SDU and the second MAC SDU consist of a MAC subheader and a MAC payload. The MAC payload of the second MAC SDU includes DRB data. The MAC subheader is not encrypted. The second MAC SDU is located after the first MAC SDU.

The UE transmits Msg3. The UE starts the contention-ResolutionTimer. The timer is set to the value indicated in the selected RACH-ConfigCommon of the selected uplink carrier.

GNB receives Msg 3 and processes the content. If there is an RRC message requesting connection establishment, GNB performs call admission control and takes action according to the result.

In step 2a-29, the UE receives Msg 4 from the base station. Msg 4 includes a downlink RRC control message such as RRCSetup.

The UE receives the DCI on the PDCCH addressed to the temporary C-RNTI. The DCI includes a time domain resource allocation field. Temporary C-RNTI is assigned in RAR.

To receive DCI on the PDCCH addressed to the temporary C-RNTI, the UE applies the searchSpace indicated by ra-SearchSpace. The UE monitors the PDCCH while the contention-ResolutionTimer is running.

If the UE selects the default RACH-ConfigCommon, the UE monitors the RA-RNTI by applying the ra-SearchSpace of the first part of the PDCCH-ConfigCommon.

If the UE selects the n-th RACH-ConfigCommon-fc, the UE monitors the RA-RNTI by applying the ra-SearchSpace included in the n-th RACH-ConfigCommon-fc.

If the UE selects the n-th RACH-ConfigCommon-fc, the UE monitors the RA-RNTI by applying the n-th ra-SearchSpace of the second part of the PDCCH-ConfigCommon.

One first pdsch-TimeDomainAllocationList may be included in the first part of PDSCH-ConfigCommon, and a plurality of second pdsch-TimeDomainAllocationLists may be included in the second part. The second pdsch-TimeDomainAllocationList of the second part is a parameter for featureCombination/RACH partition/second RACH-ConfigCommon. The second part is an extension part and is located behind the first part.

Alternatively, RACH-ConfigCommon-fc may include one second pdsch-TimeDomainAllocationList to be applied to the corresponding featureCombination.

If the UE selects the default RACH-ConfigCommon, the UE determines the time domain relationship between the PDCCH and the PDSCH by using the first pdsch-TimeDomainAllocationList of the PDSCH-ConfigCommon.

If the UE selects the n-th RACH-ConfigCommon-fc, the UE determines the time-domain relationship between the PDCCH and the PDSCH by using the second pdsch-TimeDomainAllocationList included in the n-th RACH-ConfigCommon-fc. If TimeDomainAllocationList is not included in the nth RACH-ConfigCommon-fc, the UE uses the first pdsch-TimeDomainAllocationList of the first part of PDSCH-ConfigCommon or uses the default PDSCH time domain resource allocation table.

If the UE selects the n-th RACH-ConfigCommon-fc, the UE determines the time-domain relationship between the PDCCH and the PDSCH by using the n-th pdsch-TimeDomainAllocationList of the second part of the PDSCH-ConfigCommon. If the nth second pdsch-TimeDomainAllocationList does not exist in the second part, the UE uses the first pdsch-TimeDomainAllocationList of the first part of PDSCH-ConfigCommon or uses the default PDSCH time domain resource allocation table.

The time resource allocation field indicates pdsch-TimeDomainResourceAllocation of pdsch-TimeDomainResourceAllocationList included in PDSCH-ConfigCommon.

If PDSCH-ConfigCommon does not include pdsch-TimeDomainResourceAllocationList, the PDSCH time resource allocation field indicates an indexed column of the default PDSCH time domain resource allocation table illustrated in the table below.

Row index dmrs-TypeA-Position PDSCH mapping type K ₀ S L One 2 Type A 0 2 12 3 Type A 0 3 11 2 2 Type A 0 2 10 3 Type A 0 3 9 3 2 Type A 0 2 9 3 Type A 0 3 8 4 2 Type A 0 2 7 3 Type A 0 3 6 5 2 Type A 0 2 5 3 Type A 0 3 4 6 2 Type B 0 9 4 3 Type B 0 10 4 7 2 Type B 0 4 4 3 Type B 0 6 4 8 2,3 Type B 0 5 7 9 2,3 Type B 0 5 2 10 2,3 Type B 0 9 2 11 2,3 Type B 0 12 2 12 2,3 Type A 0 One 13 13 2,3 Type A 0 One 6 14 2,3 Type A 0 2 4 15 2,3 Type B 0 4 7 16 2,3 Type B 0 8 4

The UE determines k0, S, and L based at least in part on the value h indicated in the time resource allocation field.

When the terminal selects the default RACH-ConfigCommon and the PDSCH-ConfigCommon includes the first pdsch-TimeDomainResourceAllocationList, h indicates the (h+1)th entry of the first pdsch-TimeDomainResourceAllocationList.

When the UE selects the nth RACH-ConfigCommon-fc and the PDSCH-ConfigCommon includes the nth second pdsch-TimeDomainResourceAllocationList, h indicates the (h+1)th entry of the nth second pdsch-TimeDomainResourceAllocationList.

Alternatively, when the UE selects the n-th RACH-ConfigCommon-fc and the n-th RACH-ConfigCommon-fc includes the second pdsch-TimeDomainResourceAllocationList, h indicates the (h+1)-th entry of the second pdsch-TimeDomainResourceAllocationList. .

Each item of pdsch-TimeDomainResourceAllocationList (or each pdsch-TimeDomainResourceAllocation of pdsch-TimeDomainResourceAllocationList) is associated with k0 and S and L. The UE determines k0 and S and L for PDSCH reception by k0 and S and L values related to pdsch-TimeDomainResourceAllocation indicated by h.

When the UE selects the default RACH-ConfigCommon and the PDSCH-ConfigCommon does not include the first pdsch-TimeDomainResourceAllocationList, h indicates a row index (h+1) of the default PDSCH time domain resource allocation table.

When the UE selects the nth RACH-ConfigCommon-fc and the PDSCH-ConfigCommon does not include the nth second pdsch-TimeDomainResourceAllocationList, h represents the row index (h+1) of the default PDSCH time domain resource allocation table.

Alternatively, when the UE selects the n-th RACH-ConfigCommon-fc and the n-th RACH-ConfigCommon-fc does not include the second pdsch-TimeDomainResourceAllocationList, h is a row index (h+1) of the default PDSCH time domain resource allocation table. indicates

The UE determines a transmission resource to transmit the HARQ ACK for Msg 4 based on one of a plurality of PUCCH-ResourceCommon.

One first pucch-ResourceCommon may be included in the first part of PUCCH-ConfigCommon, and a plurality of second pucch-ResourceCommons may be included in the second part. The second pucch-ResourceCommon of the second part is a parameter for featureCombination/RACH partition/second RACH-ConfigCommon. The second part is an extension part and is located behind the first part.

Alternatively, RACH-ConfigCommon-fc may include a second pucch-ResourceCommon to be applied to the corresponding featureCombination.

If the UE selects the default RACH-ConfigCommon, the UE selects the first pucch-ResourceCommon of the PUCCH-ConfigCommon.

If the UE selects the n-th RACH-ConfigCommon-fc, the UE selects the second pucch-ResourceCommon included in the n-th RACH-ConfigCommon-fc. If there is no pucch-ResourceCommon in the nth RACH-ConfigCommon-fc, the UE selects the first pucch-ResourceCommon of the PUCCH-ConfigCommon.

Alternatively, if the UE selects the n-th RACH-ConfigCommon-fc, the UE selects the n-th second pucch-ResourceCommon of the second part of the PUCCH-ConfigCommon. If the n-th second pucch-ResourceCommon does not exist, the terminal selects the first pucch-ConfigCommon.

The UE includes a first nominal power offset (p0-norminal) included in the first part of pucch-ConfigCommon and a plurality of second nominal power offsets included in the second part of pucch-ConfigCommon or included in RACH-ConfigCommon-fc A nominal power offset to be applied to HARQ ACK transmission for Msg 4 is determined by selecting one of nominal power offsets fixed to a predetermined value.

After transmitting and receiving the RRCRequest message and the RRCSetup message, the UE and the base station configure an RRC connection.

Figure 2b illustrates the operation of the UE and GNB in the RRC_CONNECTED state for a random access procedure.

At 2b-09, GNB 2b-03 transmits SIB1 and terminal 2b-01 receives SIB1 in the appropriate cell. SIB1 includes BWP-DownlinkCommon for initial downlink BWP, BWP-UplinkCommon for initial UL BWP of general uplink, and BWP-UplinkCommon for initial UL BWP of additional uplink.

The UE performs a random access procedure as shown in FIG. 2A.

In 2b-11, the UE transmits the RRCSetup message included in Msg3 and GNB receives it. If the UE is a RedCap UE, the LCID of the MAC SDU including RRCSetup is set to the first value. If the UE is not a RedCap UE, the LCID of the MAC SDU including RRCSetup is set to the second value. The first value represents a 48-bit CCCH sent by the RedCap UE. The second value represents a 48-bit CCCH not transmitted by the RedCap UE.

The GNB determines whether the UE is a RedCap UE based at least in part on the LCID of the CCCH included in Msg 3. The GNB determines the dedicated BWP configuration for the initial downlink BWP and the initial uplink BWP.

In 2b-13, the GNB transmits the RRCSetup message and the UE receives it. The UE configures the dedicated part of the initial BWP based at least in part on the configuration information contained in the RRCSetup message.

In 2b-15, the UE transmits the RRCSetupComplete message and the GNB receives the RRCSetupComplete message. The message includes the S-NSSAI list configured for the UE.

In 2b-17, the UE transmits the UECapabilityInformation message and the GNB receives it. The message includes a plurality of frequency band specific capability information. Each band-specific capability information includes a band indicator and an indicator indicating whether the UE supports Msg 3 repetition mode (range enhancement or CovEnh).

In Msg 3 repetition mode, the UE repeatedly transmits Msg 3 within a bundle. The number of repetitions is indicated in the uplink grant of RAR.

Based at least in part on the Msg 3 repetition capability information in the UECapabilityInformation message, the Slice information in the RRCSetupComplete message, and the LCID for CCCH in Msg 3, the GNB determines the number and type of non-initial BWPs to configure for the UE.

A UE may be configured with one initial DL BWP, one initial UL BWP, a plurality of non-initial DL BWPs, and a plurality of non-initial UL BWPs.

DL BWP is composed of BWP-DownlinkCommon and BWP-DownlinkDedicate. UL BWP is composed of BWP-UplinkCommon and BWP-UplinkDedicate.

BWP-DownlinkCommon for initial DL BWP is provided in SIB1. BWP-DownlinkDedicate for initial DL BWP is provided in DL RRC messages such as RRCSetup, RRCReconfiguration, and RRCResume.

BWP-UplinkCommon for initial UL BWP is provided in SIB1. BWP-UplinkDedicate for initial UL BWP is provided in DL RRC messages such as RRCSetup, RRCReconfiguration, and RRCResume.

BWP-DownlinkCommon and BWP-DownlinkDedicate for non-initial DL BWP are provided in DL RRC messages such as RRCSetup and RRCReconfiguration and RRCResume.

BWP-UplinkCommon and BWP-UplinkDedicate for non-initial UL BWP are provided in DL RRC messages such as RRCSetup and RRCReconfiguration and RRCResume.

One BWP is associated with one bwp-id. The bwp-id for the initial DL BWP is fixed to a specific value. The specific value is 0. The bwp-id for non-initial DL BWP is explicitly configured in DL RRC messages such as RRCSetup, RRCReconfiguration, and RRCResume.

GNB may configure multiple non-initial BWPs for the UE. A non-initial UL BWP may include a plurality of RACH-ConfigCommons for the UE.

Each feature of the feature combination may be a feature related to a radio channel state, a feature related to a UE type, a feature related to a service type, or a composite feature.

CovEnh is a radio channel state related feature. RedCap is a UE type specific feature. A slice is a feature related to a service type. SDT is a composite feature related to service type and radio channel condition.

The feature combination indicated in the initial UL BWP may include a feature related to a radio channel condition, a feature related to a UE type, a feature related to a service type, or a composite feature. Therefore, the UE considers radio conditions, UE type and service type when selecting a feature combination in the initial UL BWP.

The feature combination indicated in the non-initial UL BWP may include only radio channel state related features. Therefore, the UE only considers radio conditions when selecting a feature combination in a non-initial (configured RRC) UL BWP.

In 2b-19, the GNB transmits an RRCReconfiguration message and the UE receives it. The RRCReconfiguration message includes configuration information for a plurality of non-initial BWPs. GNB and UE configure non-initial BWP according to the configuration information.

At any point in time, a random access procedure is triggered.

The random access procedure may be triggered by the UE itself or by a PDCCH command transmitted from the GNB.

When the PDCCH command is received, the UE performs uplink and preamble based on the Random Access Preamble index field, UL/SUL indicator field, and SS/PBCH index field indicated in the PDCCH order (DCI format 1_0 in which the frequency domain resource allocation field is all 1). and SSB.

The UE performs a random access procedure in the currently activated UL BWP without selecting a BWP. The UE selects the RACH partition based at least in part on the value of the RACH-Id field indicated in the PDCCH order. The UE selects the RACH-ConfigCommon indicated by the RACH-Id field among the RACH-ConfigCommons of the currently active UL BWP.

The PDCCH order is addressed by C-RNTI and contains the following fields: DCI format identifier field, frequency domain resource allocation field, random access preamble index field, UL/SUL indicator field, SS/PBCH index field, PRACH mask index field and RACH-Id field.

If the random access procedure is triggered by the UE itself, the UE performs steps 2b-21 to 2b-31 to select uplink and preamble, SSB and BWP, and RACH partitions.

In 2b-21, the UE selects an uplink on which a random access procedure is performed based at least in part on the rsrp-ThresholdSSB-SUL indicated in the first RACH-ConfigCommon of NUL (Normal Uplink). The first RACH-ConfigCommon is included in the BWP-UplinkCommon of the initial UL BWP even if the currently active UL BWP is not the initial UL BWP.

If the RSRP of the downlink path loss reference is less than rsrp-ThresholdSSB-SUL, the UE selects a NUL 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 a SUL (Supplementary Uplink) carrier to perform the random access procedure.

The downlink path loss reference may be an SSB having the best RSRP among the SSBs of the currently active DL BWP. Alternatively, among the SSBs of the initial DL BWP, RSRP may be the best SSB. Alternatively, any SSB of the cell may be a downlink path loss reference.

In 2b-23, the UE selects BWP for the random access procedure.

When the random access procedure starts in the serving cell, after carrier selection for performing the random access procedure, if no PRACH opportunity is configured for the active UL BWP, the UE switches the active UL BWP to the BWP indicated by initialUplinkBWP. If the serving cell is SpCell, the UE switches the active DL BWP to the BWP indicated by initialDownlinkBWP.

Alternatively, if the PRACH opportunity for the target feature combination is not configured for the active UL BWP, the UE switches the active UL BWP to the BWP indicated by initialUplinkBWP. If the serving cell is SpCell, the UE switches the active DL BWP to the BWP indicated by initialDownlinkBWP.

Alternatively, if CovEnh is required and the PRACH opportunity for CovEnh is not configured for the active UL BWP, the UE switches the active UL BWP to the BWP indicated by initialUplinkBWP. If the serving cell is SpCell, the UE switches the active DL BWP to the BWP indicated by initialDownlinkBWP.

In 2b-25, the UE determines whether to use the Msg 3 repetition mode (CovEnh). If rsrp-ThresholdSSB-CE is present in the first rach-ConfigCommon and RSRP of downlink path loss reference is lower than rsrp-ThresholdSSB-CE, the UE determines to use Msg 3 repetition mode. If there is no rsrp-ThresholdSSB-CE in the first rach-ConfigCommon or if the RSRP of the downlink path loss reference is higher than rsrp-ThresholdSSB-CE, the UE determines not to use the Msg 3 repetition mode. The downlink path loss reference may be the SSB or CSI-RS of the currently active DL BWP. The first rach-ConfigCommon is included in the BWP-UplinkCommon of the currently activated UL BWP.

In 2b-27, the UE selects a RACH partition (or RACH-ConfigCommon) in consideration of a target feature combination and a feature combination of RACH partitions.

When the currently activated UL BWP is the initial UL BWP, the target feature combination may include a UE type related feature, a service type related feature, and a radio channel condition related feature.

If the currently activated UL BWP is not the initial UL BWP, only radio channel condition related features are included in the target feature combination.

In 2b-29, the UE selects an SSB based at least in part on the rsrp-ThresholdSSB.

The UE uses the rsrp-ThresholdSSB of the selected RACH partition (or feature combination). For example, if the UE selects the default RACH-ConfigCommon, the UE applies the rsrp-ThresholdSSB of the first RACH-ConfigCommon. If the UE selects the n-th RACH-ConfigCommon-fc, the UE applies the rsrp-ThresholdSSB of the second RACH-ConfigCommon included in the n-th RACH-ConfigCommon-fc.

The first RACH-ConfigCommon and the second RACH-ConfigCommon are those included in the BWP-UplinkCommon of the currently activated UL BWP.

In 2b-31, the UE selects a preamble group based at least in part on the selected RACH partition (or feature combination).

If the potential Msg3 size (transportable UL data, MAC subheader(s) and MAC CE if necessary) is greater than ra-Msg3SizeGroupA and the path loss is PCMAX (of the serving cell performing random access procedure) preambleReceivedTargetPower, msg3-DeltaPreamble and If it is less than the value obtained by subtracting messagePowerOffsetGroupB, the UE selects random access preamble group B.

If the random access procedure is initiated for the CCCH logical channel and the CCCH SDU size and MAC subheader are greater than ra-Msg3SizeGroupA, the UE selects random access preamble group B.

If the random access procedure is not initiated for the CCCH logical channel and the potential Msg3 size (UL data available for transmission and MAC subheader(s) and MAC CE if necessary) is not greater than ra-Msg3SizeGroupA, the UE sends a random access preamble Choose group A.

If the random access procedure is initiated for the CCCH logical channel and the potential Msg3 size (UL data available for transmission + MAC subheader(s) and MAC CE if necessary) is not greater than ra-Msg3SizeGroupA, the UE selects random access preamble group A Choose

No random access procedure has been initiated for the CCCH logical channel, the potential Msg3 size (UL data available for transmission plus MAC subheader(s) and MAC CE if necessary) is greater than ra-Msg3SizeGroupA, and the path loss is PCMAX (random access If not smaller than the subtraction of preambleReceivedTargetPower, msg3-DeltaPreamble and messagePowerOffsetGroupB from (of the serving cell performing the procedure), the UE selects random access preamble group A.

One msg3-DeltaPreamble may be included in the first part of PUSCH-ConfigCommon, and multiple msg3-DeltaPreambles may be included in the second part. msg3-DeltaPreamble of the second part is a parameter for featureCombination/RACH partition/second RACH-ConfigCommon. The second part is an extension part and is located behind the first part.

Alternatively, RACH-ConfigCommon-fc may include msg3-DeltaPreamble to be applied to the corresponding featureCombination.

If the UE selects the default RACH-ConfigCommon, the UE selects a random access preamble group using msg3-DeltaPreamble of PUSCH-ConfigCommon and Msg3SizeGroupA, preambleReceivedTargetPower, and messagePowerOffsetGroupB of the first RACH-ConfigCommon. If msg3-DeltaPreamble is not included in PUSCH-ConfigCommon, the UE uses 0.

If the UE selects the nth RACH-ConfigCommon-fc, the UE selects msg3-DeltaPreamble included in the RACH-ConfigCommon-fc and Msg3SizeGroupA, preambleReceivedTargetPower, and messagePowerOffsetGroupB included in the second RACH-ConfigCommon included in the RACH-ConfigCommon-fc. Select a random access preamble group using If msg3-DeltaPreamble is not included in the RACH-ConfigCommon-fc, the UE uses 0.

If the UE selects the nth RACH-ConfigCommon-fc, the UE selects the nth msg3-DeltaPreamble of the second part of PUSCH-ConfigCommon and Msg3SizeGroupA, preambleReceivedTargetPower, and messagePowerOffsetGroupB of the second RACH-ConfigCommon included in the RACH-ConfigCommon-fc. selects a random access preamble group using

The PUSCH-ConfigCommon, the first RACH-ConfigCommon, and the n-th RACH-ConfigCommon-fc are included in the BWP-UplinkCommon of the currently activated UL BWP.

The UE randomly selects a preamble with equal probability from among the preambles associated with the selected SSB and the selected preamble group. The UE sets PREAMBLE_INDEX to ra-PreambleIndex corresponding to the selected preamble.

The UE determines the next available PRACH opportunity from the PRACH opportunity corresponding to the selected SSB. The UE shall randomly select a PRACH opportunity with equal probability among consecutive PRACH opportunities indicated by the PRACH configuration index of the selected RACH-ConfigCommon of the specific BWP of the selected uplink. The specific BWP is a currently active uplink BWP.

In 2b-33, the UE transmits the selected preamble on the selected PRACH opportunity in the selected uplink.

The UE sets PREAMBLE_RECEIVED_TARGET_POWER as preambleReceivedTargetPower + DELTA_PREAMBLE + (PREAMBLE_POWER_RAMPING_COUNTER - 1) × powerRampingStep + POWER_OFFSET_2STEP_RA.

The UE sets the transmit power of the preamble as the sum of PREAMBLE_RECEIVED_TARGET_POWER and path loss.

If the UE selects the default RACH-ConfigCommon, the UE uses preambleReceivedTargetPower and powerRampingStep of the first RACH-ConfigCommon. The UE sets POWER_OFFSET_2STEP_RA to 0. The UE sets DELTA_PREAMBLE according to the preamble format determined from the prach-ConfigurationIndex indicated in the first RACH-ConfigCommon. DELTA_PREAMBLE is predefined for each preamble format. PREAMBLE_POWER_RAMPING_COUNTER is initialized to 1 and incremented by 1 for each preamble transmission.

If the UE selects the nth RACH-ConfigCommon-fc, the UE uses the preambleReceivedTargetPower and powerRampingStep of the second RACH-ConfigCommon of the RACH-ConfigCommon-fc. The UE sets POWER_OFFSET_2STEP_RA to 0. The UE sets DELTA_PREAMBLE according to the preamble format determined from the prach-ConfigurationIndex indicated in the second RACH-ConfigCommon. DELTA_PREAMBLE is predefined for each preamble format. PREAMBLE_POWER_RAMPING_COUNTER is initialized to 1 and incremented by 1 for each preamble transmission.

The first RACH-ConfigCommon and the n-th RACH-ConfigCommon-fc are included in the BWP-UplinkCommon of the currently activated UL BWP.

In 2b-35, the UE receives an uplink grant in RAR.

To receive the RAR, the UE starts the ra-ResponseWindow configured by RACH-ConfigCommon at the first PDCCH opportunity after the random access preamble transmission ends. The UE monitors SpCell's PDCCH for random access response(s) identified by RA-RNTI while ra-ResponseWindow is running.

In PDCCH monitoring, the UE applies the searchSpace indicated by ra-SearchSpace.

If the UE selects the default RACH-ConfigCommon, the UE monitors the RA-RNTI by applying the ra-SearchSpace of the first part of the PDCCH-ConfigCommon.

If the UE selects the n-th RACH-ConfigCommon-fc, the UE monitors the RA-RNTI by applying the ra-SearchSpace included in the n-th RACH-ConfigCommon-fc.

If the UE selects the n-th RACH-ConfigCommon-fc, the UE monitors the RA-RNTI by applying the n-th ra-SearchSpace of the second part of the PDCCH-ConfigCommon.

The first RACH-ConfigCommon and the n-th RACH-ConfigCommon-fc are included in the BWP-UplinkCommon of the currently activated UL BWP.

The PDCCH-ConfigCommon is included in the BWP-DownlinkCommon of the currently active DL BWP (or the DL BWP having the same bwp-id as the currently active UL BWP).

The UE considers that the random access response has been received successfully when the random access response includes a MAC subPDU having a random access preamble identifier corresponding to the transmitted PREAMBLE_INDEX.

MAC subPDU includes MAC RAR. MAC RAR includes fields such as Timing Advance Command, Uplink Grant and Temporary C-RNTI. The Timing Advance Command field indicates an index value used to control the amount of timing adjustment that the UE should apply. The size of the Timing Advance Command field is 12 bits. The Uplink Grant field indicates resources to be used in uplink. The size of the UL Grant field is 27 bits. Temporary C-RNTI field indicates a temporary ID used by the UE during random access. The size of the temporary C-RNTI field is 16 bits.

The uplink grant field further includes a PUSCH time resource allocation field. The PUSCH time resource allocation field is 4 bits.

One first push-TimeDomainAllocationList may be included in the first part of PUSCH-ConfigCommon, and a plurality of second push-TimeDomainAllocationLists may be included in the second part. The second push-TimeDomainAllocationList of the second part is a parameter for featureCombination/RACH partition/second RACH-ConfigCommon. The second part is an extension part and is located behind the first part.

Alternatively, RACH-ConfigCommon-fc may include one second push-TimeDomainAllocationList to be applied to the corresponding featureCombination.

If the UE selects the default RACH-ConfigCommon, the UE determines the time domain relationship between the PDCCH and the PUSCH by using the first push-TimeDomainAllocationList of the PUSCH-ConfigCommon.

If the UE selects the nth RACH-ConfigCommon-fc, the UE determines the time domain relationship between the PDCCH and the PUSCH by using the second push-TimeDomainAllocationList included in the nth RACH-ConfigCommon-fc. If TimeDomainAllocationList is not included in the nth RACH-ConfigCommon-fc, the UE uses the first push-TimeDomainAllocationList of the first part of PUSCH-ConfigCommon or uses the default PUSCH time domain resource allocation table.

If the UE selects the nth RACH-ConfigCommon-fc, the UE determines the time domain relationship between the PDCCH and the PUSCH by using the nth second push-TimeDomainAllocationList of the second part of the PUSCH-ConfigCommon. If the nth second push-TimeDomainAllocationList does not exist in the second part, the UE uses the first push-TimeDomainAllocationList of the first part of PUSCH-ConfigCommon or uses the default PUSCH time domain resource allocation table.

When the terminal selects the default RACH-ConfigCommon and the PUSCH-ConfigCommon includes the first push-TimeDomainResourceAllocationList, h indicates the (h+1)th entry of the first push-TimeDomainResourceAllocationList.

When the UE selects the nth RACH-ConfigCommon-fc and the PUSCH-ConfigCommon includes the nth second push-TimeDomainResourceAllocationList, h indicates the (h+1)th entry of the nth second push-TimeDomainResourceAllocationList.

Alternatively, when the UE selects the n-th RACH-ConfigCommon-fc and the n-th RACH-ConfigCommon-fc includes the second push-TimeDomainResourceAllocationList, h indicates the (h+1)-th entry of the second push-TimeDomainResourceAllocationList .

When the UE selects the default RACH-ConfigCommon and the PUSCH-ConfigCommon does not include the first push-TimeDomainResourceAllocationList, h represents the row index (h+1) of the default PUSCH time domain resource allocation table.

When the UE selects the n-th RACH-ConfigCommon-fc and the PUSCH-ConfigCommon does not include the n-th second push-TimeDomainResourceAllocationList, h represents the row index (h+1) of the default PUSCH time domain resource allocation table.

Alternatively, when the UE selects the nth RACH-ConfigCommon-fc and the nth RACH-ConfigCommon-fc does not include the second push-TimeDomainResourceAllocationList, h is a row index (h+1) of the default PUSCH time domain resource allocation table indicates

The PUSCH-ConfigCommon, the first RACH-ConfigCommon, and the n-th RACH-ConfigCommon-fc are included in the BWP-UplinkCommon of the currently activated UL BWP.

Each row of the default PUSCH time domain resource allocation table is associated with k2, a function of j and i. The UE determines j according to the PUSCH subcarrier spacing. The UE determines i based at least in part on h. The UE determines k2 by adding the determined j and the determined i. In other words, the UE determines k2 based at least in part on the row index determined based at least in part on j and h determined based at least in part on the PUSCH subcarrier spacing.

The UE determines the time slot for PUSCH transmission scheduled by RAR. When the UE receives the PDSCH with the RAR message ending in slot n for the PRACH transmission, the UE transmits the PUSCH in slot (n + k2 + delta). k2 and delta are subcarrier spacing specific and are determined as follows.

If push-TimeDomainResourceAllocationList is not included in PUSCH-ConfigCommon for non-initial UL BWP of ServingCellConfigCommon, k2 is determined based on h, j, and i. j is determined based at least in part on the subcarrier spacing IE included in the BWP-UplinkCommon IE for the non-initial UL BWP of the ServingCellConfigCommon of the downlink RRC message. If the subcarrier spacing IE indicates 15 kHz or 30 kHz, j is 1. If the subcarrier spacing IE represents 60 kHz, j is 2. If the subcarrier spacing IE represents 120 kHz, j is 3.

Delta is determined based at least in part on the subcarrier spacing IE included in the BWP-UplinkCommon IE for the non-initial UL BWP of the ServingCellConfigCommon of the downlink RRC message. If the subcarrier spacing IE indicates 15 kHz, the delta is 2. If the subcarrier spacing IE indicates 30 kHz, the delta is 3. If the subcarrier spacing IE indicates 60 kHz, the delta is 4. If the subcarrier spacing IE indicates 120 kHz, the delta is 6.

In 2b-37, the UE performs Msg 3 transmission in the determined slot according to the UL grant in the received RAR.

The UE determines the PUSCH transmit power by summing the offset, path loss, and other parameters related to the number of PRBs and power control commands.

The offset is the sum of preambleReceivedTargetPower and msg3-DeltaPreamble.

One msg3-DeltaPreamble may be included in the first part of PUSCH-ConfigCommon, and multiple msg3-DeltaPreambles may be included in the second part. msg3-DeltaPreamble of the second part is a parameter for featureCombination/RACH partition/second RACH-ConfigCommon. The second part is an extension part and is located behind the first part.

Alternatively, RACH-ConfigCommon-fc may include msg3-DeltaPreamble to be applied to the corresponding featureCombination.

If the UE selects the default RACH-ConfigCommon, the UE uses msg3-DeltaPreamble of the PUSCH-ConfigCommon and preambleReceivedTargetPower of the first RACH-ConfigCommon.

If the terminal selects the nth RACH-ConfigCommon-fc, the terminal uses msg3-DeltaPreamble and preambleReceivedTargetPower included in the RACH-ConfigCommon-fc.

If the UE selects the nth RACH-ConfigCommon-fc, the UE uses the nth msg3-DeltaPreamble of the second part of the PUSCH-ConfigCommon and the preambleReceivedTargetPower included in the nth RACH-ConfigCommon-fc.

The PUSCH-ConfigCommon, the first RACH-ConfigCommon, and the n-th RACH-ConfigCommon-fc are included in the BWP-UplinkCommon of the currently activated UL BWP.

The UE generates Msg3. Msg3 may include a buffer status report MAC CE and a C-RNTI MAC CE.

The UE transmits Msg3. UE starts contention-ResolutionTimer. The timer is set to the value indicated in the selected RACH-ConfigCommon of the selected uplink carrier. The RACH-ConfigCommon is selected from among multiple RACH-ConfigCommons in the BWP-UplinkCommon of the currently activated UL BWP.

GNB receives Msg3 and processes the Buffer Status Report included in Msg 3. The GNB may send UL grants to the UE.

The Random Access procedure is complete when the UE receives a UL grant addressed by the UE's C-RNTI.

The following illustrates the operation of the UE and GNB when the alternative signaling structure of Figure 1g is used.

The GNB includes one first RACH-ConfigCommon and zero, one, or two or more second RACH-ConfigCommons in BWP-UplinkCommon for one uplink.

The GNB includes 0, 1, or 2 or more featureCombinations in the first rach-ConfigCommon and includes one or more featureCombinations in each of the 2nd rach-ConfigCommon.

The UE selects a featureCombination from a plurality of featureCombinations included in a plurality of RACH-ConfigCommon of BWP-UplinkCommon of the selected uplink based at least in part on the target feature combination that triggered the random access procedure.

The UE selects a RACH-ConfigCommon based at least in part on the selected featureCombination (the RACH-ConfigCommon containing the selected featureCombination is selected).

If the featureCombination does not match the target feature combination, the first rach-ConfigCommon is selected.

GNB includes rsrp-ThresholdSSB in the non-extended part of the first RAH-ConfigCommon. GNB includes 0, 1, or 2 or more rsrp-ThresholdSSBs in the extension part of the first rach-ConfigCommon. GNB includes 0 or 1 rsrp-ThresholdSSB in each featureCombinationParameter of the first rach-ConfigCommon.

GNB includes 0 or 1 rsrp-ThresholdSSB in the non-extended part of each of the second RAH-ConfigCommon. GNB includes 0, 1, or 2 or more rsrp-ThresholdSSBs in each extension part of the second rach-ConfigCommon. GNB includes 0 or 1 rsrp-ThresholdSSB in each featureCombinationParameter of the second rach-ConfigCommon.

The UE selects the SSB based at least in part on the rsrp-ThresholdSSB.

If the selected featureCombinationParameter (or the selected feature combination) is included in the first rach-ConfigCommon and the selected featureCombinationParameter does not include the rsrp-ThresholdSSB, the UE is included in the non-extended part of the first rach-ConfigCommon. Apply the ThresholdSSB.

If the selected featureCombinationParameter (or the selected feature combination) is included in the first rach-ConfigCommon and the selected featureCombinationParameter includes rsrp-ThresholdSSB, the UE applies the rsrp-ThresholdSSB included in the selected featureCombinationParameter.

When the first rach-ConfigCommon is selected because there is no featureCombination matching the target feature combination, the UE applies the rsrp-ThresholdSSB included in the non-extended part of the first rach-ConfigCommon.

If the selected featureCombinationParameter (or the selected feature combination) is included in the second rach-ConfigCommon and the selected featureCombinationParameter does not include the rsrp-ThresholdSSB, the UE is included in the non-extended part of the second rach-ConfigCommon. Apply the ThresholdSSB.

If the selected featureCombinationParameter (or the selected feature combination) is included in the second rach-ConfigCommon and the selected featureCombinationParameter includes the rsrp-ThresholdSSB, the UE applies the rsrp-ThresholdSSB included in the selected featureCombinationParameter of the selected second rach-ConfigCommon.

GNB includes ra-Msg3SizeGroupA in the non-extended part of the first RAH-ConfigCommon. GNB includes 0, 1, or 2 or more ra-Msg3SizeGroupA in the extension part of the first rach-ConfigCommon. GNB includes 0 or 1 ra-Msg3SizeGroupA in each featureCombinationParameter of the first rach-ConfigCommon.

GNB includes 0 or 1 ra-Msg3SizeGroupA in the non-extended part of each of the second RAH-ConfigCommon. GNB includes 0, 1, or 2 or more ra-Msg3SizeGroupA in each extension part of the second rach-ConfigCommon. GNB includes 0 or 1 ra-Msg3SizeGroupA in each featureCombinationParameter of the second rach-ConfigCommon.

GNB includes messagePowerOffsetGroupB in the non-extended part of the first RAH-ConfigCommon. GNB includes 0, 1, or 2 or more messagePowerOffsetGroupBs in the extension part of the first rach-ConfigCommon. GNB includes 0 or 1 messagePowerOffsetGroupB in each featureCombinationParameter of the first rach-ConfigCommon.

GNB includes 0 or 1 messagePowerOffsetGroupB in the non-extended part of each of the second RAH-ConfigCommon. The GNB includes 0, 1, or 2 or more messagePowerOffsetGroupBs in each extension of the second rach-ConfigCommon. GNB includes 0 or 1 messagePowerOffsetGroupB in each featureCombinationParameter of the second rach-ConfigCommon.

GNB includes preambleReceivedTargetPower in the non-extended part of the first RAH-ConfigCommon. GNB includes 0, 1, or 2 or more preambleReceivedTargetPower in the extension part of the first rach-ConfigCommon. GNB includes 0 or 1 preambleReceivedTargetPower in each featureCombinationParameter of the first rach-ConfigCommon.

GNB includes 0 or 1 preambleReceivedTargetPower in the non-extended part of each of the second RAH-ConfigCommon. GNB includes 0, 1, or 2 or more preambleReceivedTargetPower in each extension part of the second rach-ConfigCommon. GNB includes 0 or 1 preambleReceivedTargetPower in each featureCombinationParameter of the second rach-ConfigCommon.

GNB includes 0 or 1 msg3-DeltaPreamble in the non-extended part of PUSCH-ConfigCommon and 0 or 1 or 2 or more msg3-DeltaPreambles in the extended part of rach-ConfigCommon 1. GNB includes 0 or 1 msg3-DeltaPreamble in each featureCombinationParameter of the first rach-ConfigCommon.

The GNB includes 0, 1, or 2 or more msg3-DeltaPreambles in each extension part of the second RACH-ConfigCommon. GNB includes 0 or 1 msg3-DeltaPreamble in each featureCombinationParameter of the second rach-ConfigCommon.

The UE selects a random access preamble group based at least in part on ra-Msg3SizeGroupA and messagePowerOffsetGroupB and preambleReceivedTargetPower and msg3-DeltaPreamble.

The UE determines the PUSCH transmit power for Msg 3 based at least in part on the preambleReceivedTargetPower and the path loss in msg3-DeltaPreamble and downlink path loss reference.

If the selected featureCombinationParameter (or the selected feature combination) is included in the first rach-ConfigCommon and the selected featureCombinationParameter does not include ra-Msg3SizeGroupA and messagePowerOffsetGroupB, the UE ra-Msg3SizeGroupA and messagePowerOffsetGroupB included in the non-extended part of the first rach-ConfigCommon apply

If the selected featureCombinationParameter (or the selected feature combination) is included in the first rach-ConfigCommon and the selected featureCombinationParameter includes ra-Msg3SizeGroupA and messagePowerOffsetGroupB, the UE applies ra-Msg3SizeGroupA and messagePowerOffsetGroupB included in the selected featureCombinationParameter.

When the first rach-ConfigCommon is selected because there is no featureCombination matching the target feature combination, the UE applies ra-Msg3SizeGroupA and messagePowerOffsetGroupB included in the non-extended part of the first rach-ConfigCommon.

If the selected featureCombinationParameter (or the selected feature combination) is included in the second rach-ConfigCommon and the selected featureCombinationParameter does not include ra-Msg3SizeGroupA and messagePowerOffsetGroupB, the UE includes ra-Msg3SizeGroupA and ra-Msg3SizeGroupA included in the non-extended part of the second rach-ConfigCommon Apply messagePowerOffsetGroupB.

If the selected featureCombinationParameter (or the selected feature combination) is included in the second rach-ConfigCommon and the selected featureCombinationParameter includes ra-Msg3SizeGroupA and messagePowerOffsetGroupB, the UE includes ra-Msg3SizeGroupA and messagePowerOffsetGroupB included in the selected featureCombinationParameter of the selected second rach-ConfigCommon apply

If the selected featureCombinationParameter (or the selected feature combination) is included in the first rach-ConfigCommon and the selected featureCombinationParameter does not include the preambleReceivedTargetPower, the UE includes the preambleReceivedTargetPower included in the non-extended part of the first rach-ConfigCommon. Apply.

If the selected featureCombinationParameter (or the selected feature combination) is included in the first rach-ConfigCommon and the selected featureCombinationParameter includes preambleReceivedTargetPower, the UE applies the preambleReceivedTargetPower included in the selected featureCombinationParameter.

If the first rach-ConfigCommon is selected because there is no featureCombination matching the target feature combination, the UE applies the preambleReceivedTargetPower included in the non-extended part of the first rach-ConfigCommon.

If the selected featureCombinationParameter (or the selected feature combination) is included in the second rach-ConfigCommon and the selected featureCombinationParameter does not include the preambleReceivedTargetPower, the UE includes the preambleReceivedTargetPower included in the non-extended part of the second rach-ConfigCommon. Apply.

When the selected featureCombinationParameter (or the selected feature combination) is included in the second rach-ConfigCommon and the selected featureCombinationParameter includes the preambleReceivedTargetPower, the UE is included in the selected featureCombinationParameter of the selected second rach-ConfigCommon. Apply preambleReceivedTargetPower.

If the selected featureCombinationParameter (or the selected feature combination) is included in the first rach-ConfigCommon and the selected featureCombinationParameter does not include msg3-DeltaPreamble, the UE is included in the non-extended part of PUSCH-ConfigCommon. Apply msg3-DeltaPreamble. If msg3-DeltaPreamble is not included in the non-extended part of PUSCH-ConfigCommon, the UE applies 0.

If the selected featureCombinationParameter (or the selected feature combination) is included in the first rach-ConfigCommon and the selected featureCombinationParameter includes msg3-DeltaPreamble, the UE applies the msg3-DeltaPreamble included in the selected featureCombinationParameter.

When the first rach-ConfigCommon is selected because there is no featureCombination matching the target feature combination, the UE applies msg3-DeltaPreamble included in the non-extended part of the PUSCH-ConfigCommon. If msg3-DeltaPreamble is not included in the non-extended part of PUSCH-ConfigCommon, the UE applies 0.

If the selected featureCombinationParameter (or the selected feature combination) is included in the second rach-ConfigCommon and the selected featureCombinationParameter does not include msg3-DeltaPreamble, the UE applies msg3-DeltaPreamble included in the extension of PUSCH-ConfigCommon. PUSCH- If msg3-DeltaPreamble is not included in the extension part of ConfigCommon, the UE applies 0.

If the selected featureCombinationParameter (or the selected feature combination) is included in the second rach-ConfigCommon and the selected featureCombinationParameter includes msg3-DeltaPreamble, the UE is included in the selected featureCombinationParameter of the selected second rach-ConfigCommon. Apply msg3-DeltaPreamble.

GNB includes powerRampingStep in the non-extended part of the first RAH-ConfigCommon. GNB includes 0, 1, or 2 or more powerRampingSteps in the extension part of the first rach-ConfigCommon. GNB includes 0 or 1 powerRampingStep in each featureCombinationParameter of the first rach-ConfigCommon.

GNB includes 0 or 1 powerRampingStep in the non-expansion part of each of the second RAH-ConfigCommon. GNB includes 0, 1, or 2 or more powerRampingSteps in each extension part of the second rach-ConfigCommon. GNB includes 0 or 1 powerRampingStep in each featureCombinationParameter of the second rach-ConfigCommon.

GNB includes prach-ConfigurationIndex in the non-extended part of the first RAH-ConfigCommon. GNB does not include prach-ConfigurationIndex in the extension part of the first rach-ConfigCommon.

GNB includes prach-ConfigurationIndex in the non-extended part of the second RAH-ConfigCommon. GNB does not include prach-ConfigurationIndex in the extension part of the second rach-ConfigCommon.

The UE determines the transmit power of the preamble based at least in part on the preambleReceivedTargetPower and powerRampingStep and prach-ConfigurationIndex.

If the selected featureCombinationParameter (or the selected feature combination) is included in the first rach-ConfigCommon and the selected featureCombinationParameter does not include the powerRampingStep, the UE applies the powerRampingStep included in the non-extended part of the first rach-ConfigCommon.

If the selected featureCombinationParameter (or the selected feature combination) is included in the first rach-ConfigCommon and the selected featureCombinationParameter includes the powerRampingStep, the UE applies the powerRampingStep included in the selected featureCombinationParameter.

If the first rach-ConfigCommon is selected because there is no featureCombination matching the target feature combination, the UE applies the powerRampingStep included in the non-extended part of the first rach-ConfigCommon.

If the selected featureCombinationParameter (or the selected feature combination) is included in the second rach-ConfigCommon and the selected featureCombinationParameter does not include the powerRampingStep, the UE applies the powerRampingStep included in the non-extended part of the second rach-ConfigCommon.

If the selected featureCombinationParameter (or the selected feature combination) is included in the second rach-ConfigCommon and the selected featureCombinationParameter includes the powerRampingStep, the UE applies the included powerRampingStep included in the selected featureCombinationParameter of the selected second rach-ConfigCommon.

If the selected featureCombinationParameter (or the selected feature combination) is included in the first rach-ConfigCommon and the selected featureCombinationParameter does not include the preambleReceivedTargetPower, the UE includes the preambleReceivedTargetPower included in the non-extended part of the first rach-ConfigCommon. Apply.

If the selected featureCombinationParameter (or the selected feature combination) is included in the first rach-ConfigCommon and the selected featureCombinationParameter includes preambleReceivedTargetPower, the UE applies the preambleReceivedTargetPower included in the selected featureCombinationParameter.

If the first rach-ConfigCommon is selected because there is no featureCombination matching the target feature combination, the UE applies the preambleReceivedTargetPower included in the non-extended part of the first rach-ConfigCommon.

If the selected featureCombinationParameter (or the selected feature combination) is included in the second rach-ConfigCommon and the selected featureCombinationParameter does not include the preambleReceivedTargetPower, the UE includes the preambleReceivedTargetPower included in the non-extended part of the second rach-ConfigCommon. Apply.

When the selected featureCombinationParameter (or the selected feature combination) is included in the second rach-ConfigCommon and the selected featureCombinationParameter includes the preambleReceivedTargetPower, the UE is included in the selected featureCombinationParameter of the selected second rach-ConfigCommon. Apply preambleReceivedTargetPower.

If the first rach-ConfigCommon is selected, the UE applies the prach-ConfigurationIndex included in the non-extended part of the first rach-ConfigCommon.

If the second rach-ConfigCommon is selected, the UE applies the prach-ConfigurationIndex included in the non-extended part of the second rach-ConfigCommon.

GNB includes ra-ResponseWindow in the non-extended part of the first RAH-ConfigCommon. GNB includes 0, 1, or 2 or more ra-ResponseWindows in the extension part of the first rach-ConfigCommon. GNB includes 0 or 1 ra-ResponseWindow in each featureCombinationParameter of the first rach-ConfigCommon.

GNB includes 0 or 1 ra-ResponseWindow in the non-expanded part of each of the second RAH-ConfigCommon. GNB includes 0, 1, or 2 or more ra-ResponseWindows in each extension part of the second rach-ConfigCommon. GNB includes 0 or 1 ra-ResponseWindow in each featureCombinationParameter of the second rach-ConfigCommon.

GNB includes ra-SearchSpace in the non-extended part of PDCCH-ConfigCommon of DL BWP connected (associated) with UL BWP. The GNB includes 0, 1, or 2 or more ra-SearchSpaces in the extension part of the PDCCH-ConfigCommon of the DL BWP connected (associated) with the UL BWP.

GNB includes 0 or 1 ra-SearchSpace in each featureCombinationParameter of the first rach-ConfigCommon. GNB includes 0 or 1 ra-SearchSpace in each featureCombinationParameter of the second rach-ConfigCommon.

The UE determines the RAR based at least in part on the ra-ResponseWindow. The UE monitors the PDCCH for RAR reception based at least in part on the ra-SearchSpace. The UE performs RAR reception based at least in part on ra-ResponseWindow and ra-SearchSpace. The UE monitors the PDCCH for contention resolution based at least in part on the ra-SearchSpace.

If the selected featureCombinationParameter (or the selected feature combination) is included in the first rach-ConfigCommon and the selected featureCombinationParameter does not include the ra-ResponseWindow, the UE is included in the non-extended part of the first rach-ConfigCommon. Apply ResponseWindow.

If the selected featureCombinationParameter (or the selected feature combination) is included in the first rach-ConfigCommon and the selected featureCombinationParameter includes the ra-ResponseWindow, the UE applies the ra-ResponseWindow included in the selected featureCombinationParameter.

If the first rach-ConfigCommon is selected because there is no featureCombination matching the target feature combination, the UE applies the ra-ResponseWindow included in the non-extended part of the first rach-ConfigCommon.

If the selected featureCombinationParameter (or the selected feature combination) is included in the second rach-ConfigCommon and the selected featureCombinationParameter does not include the ra-ResponseWindow, the UE applies the ra-ResponseWindow included in the non-extended part of the second rach-ConfigCommon. .

If the selected featureCombinationParameter (or the selected feature combination) is included in the second rach-ConfigCommon and the selected featureCombinationParameter includes the ra-ResponseWindow, the UE applies the ra-ResponseWindow included in the selected featureCombinationParameter of the selected second rach-ConfigCommon.

If the selected featureCombinationParameter (or the selected feature combination) is included in the first rach-ConfigCommon and the selected featureCombinationParameter does not include ra-SearchSpace, the UE ra-SearchSpace included in the non-extended part of the PDCCH-ConfigCommon of the DL BWP associated with the UL BWP apply The UL BWP is an initial UL BWP (when the UE is RRC_IDLE or RRC_INACTIVE) or a currently active UL BWP (when the UE is RRC_CONNECTED).

If the selected featureCombinationParameter (or the selected feature combination) is included in the first rach-ConfigCommon and the selected featureCombinationParameter includes ra-SearchSpace, the UE applies the ra-SearchSpace included in the selected featureCombinationParameter of the first rach-ConfigCommon of the UL BWP do.

If the first rach-ConfigCommon is selected because there is no featurecombination matching the target feature combination, the UE applies the ra-SearchSpace included in the non-extended part of the PDCCH-ConfigCommon of the DL BWP associated with the UL BWP.

If the selected featureCombinationParameter (or the selected feature combination) is included in the second rach-ConfigCommon and the selected featureCombinationParameter does not include ra-SearchSpace, the UE includes the ra- Apply SearchSpace.

If the selected featureCombinationParameter (or the selected feature combination) is included in the second rach-ConfigCommon and the selected featureCombinationParameter includes ra-SearchSpace, the UE applies the ra-SearchSpace included in the selected featureCombinationParameter of the second rach-ConfigCommon of the UL BWP do.

GNB includes 0 or 1 push-TimeDomainAllocationList in the non-extended part of PUSCH-ConfigCommon.

GNB includes 0, 1, or 2 or more push-TimeDomainAllocationLists in the extension part of PUSCH-ConfigCommon.

GNB includes 0 or 1 push-TimeDomainAllocationList in each featureCombinationParameter of the first rach-ConfigCommon.

GNB includes 0 or 1 push-TimeDomainAllocationList in each featureCombinationParameter of the second rach-ConfigCommon.

The UE determines a time slot for a PUSCH transmission scheduled by the RAR based at least in part on the push-TimeDomainAllocationList.

If the selected featureCombinationParameter (or the selected feature combination) is included in the first rach-ConfigCommon, the selected featureCombinationParameter does not include the push-TimeDomainAllocationList, and the push-TimeDomainAllocationList is included in the non-extended part of the PUSCH-ConfigCommon of the UL BWP, UE applies push-TimeDomainAllocationList included in the non-extended part of PUSCH-ConfigCommon of UL BWP. The UL BWP is an initial UL BWP (when the UE is RRC_IDLE or RRC_INACTIVE) or a currently active UL BWP (when the UE is RRC_CONNECTED).

If the selected featureCombinationParameter (or the selected feature combination) is included in the first rach-ConfigCommon, the selected featureCombinationParameter does not include the push-TimeDomainAllocationList, and the push-TimeDomainAllocationList is not included in the non-extended part of the PUSCH-ConfigCommon of the UL BWP, the UE defaults A time domain resource allocation table is applied to the PUSCH.

If the selected featureCombinationParameter (or the selected feature combination) is included in the first rach-ConfigCommon and the selected featureCombinationParameter includes push-TimeDomainAllocationList, the UE push-TimeDomainAllocationList included in the selected featureCombinationParameter. Apply.

If the first rach-ConfigCommon is selected because there is no featureCombination that matches the target feature combination, and the push-TimeDomainAllocationList is included in the non-extended part of the PUSCH-ConfigCommon of the UL BWP, the UE is included in the non-extended part of the PUSCH-ConfigCommon of the UL BWP The pushed push-TimeDomainAllocationList is applied to the UL BWP.

If the first rach-ConfigCommon is selected because there is no featureCombination matching the target feature combination and the push-TimeDomainAllocationList is included in the non-extended part of the PUSCH-ConfigCommon of the UL BWP, the UE pushes to the non-extended part of the PUSCH-ConfigCommon of the UL BWP -If TimeDomainAllocationList is not included, the UE applies the default PUSCH time domain resource allocation table.

If the selected featureCombinationParameter (or the selected feature combination) is included in the second rach-ConfigCommon and the selected featureCombinationParameter does not include the push-TimeDomainAllocationList and the corresponding push-TimeDomainAllocationList is included in the extension part of the PUSCH-ConfigCommon of the UL BWP, the UE is UL BWP Apply the corresponding push-TimeDomainAllocationList included in the extension part of PUSCH-ConfigCommon of

If the selected featureCombinationParameter (or the selected feature combination) is included in the second rach-ConfigCommon and the selected featureCombinationParameter does not include the push-TimeDomainAllocationList and the corresponding push-TimeDomainAllocationList is not included in the extension part of the PUSCH-ConfigCommon of the UL BWP, the UE defaults Apply the PUSCH time domain resource allocation table.

When the selected featureCombinationParameter (or the selected feature combination) is included in the second rach-ConfigCommon and the selected featureCombinationParameter includes push-TimeDomainAllocationList, the UE push-TimeDomainAllocationList included in the selected featureCombinationParameter. Apply.

GNB includes one pdsch-TimeDomainAllocationList in the non-extended part of PDSCH-ConfigCommon.

GNB includes 0, 1, or 2 or more pdsch-TimeDomainAllocationLists in the extension part of PDSCH-ConfigCommon.

GNB includes 0 or 1 pdsch-TimeDomainAllocationList in each featureCombinationParameter of the first rach-ConfigCommon.

GNB includes 0 or 1 pdsch-TimeDomainAllocationList in each featureCombinationParameter of the second rach-ConfigCommon.

The UE determines the number of symbols and starting symbol for PDSCH reception based at least in part on the pdsch-TimeDomainAllocationList.

If the selected featureCombinationParameter (or the selected feature combination) is included in the first rach-ConfigCommon and the selected featureCombinationParameter does not include the pdsch-TimeDomainAllocationList, the UE is included in the non-extended part of the PDSCH-ConfigCommon of the DL BWP associated with the UL BWP. Apply TimeDomainAllocationList. The UL BWPs are the initial UL BWP (if the UE is RRC_IDLE or RRC_INACTIVE) and the current active UL BWP (if the UE is RRC_CONNECTED).

When the selected featureCombinationParameter (or the selected feature combination) is included in the first rach-ConfigCommon and the selected featureCombinationParameter includes the pdsch-TimeDomainAllocationList, the UE includes the selected featureCombinationParameter. Apply the pdsch-TimeDomainAllocationList.

If the first rach-ConfigCommon is selected because there is no featureCombination matching the target feature combination, the UE applies the pdsch-TimeDomainAllocationList included in the non-extended part of the PDSCH-ConfigCommon of the DL BWP associated with the UL BWP.

If the selected featureCombinationParameter (or the selected feature combination) is included in the second rach-ConfigCommon and the selected featureCombinationParameter does not include pdsch-TimeDomainAllocationList, the UE corresponds to the pdsch-TimeDomainAllocationList in the extension part of the PDSCH-ConfigCommon of the DL BWP associated with the UL BWP apply

When the selected featureCombinationParameter (or the selected feature combination) is included in the second rach-ConfigCommon and the selected featureCombinationParameter includes the pdsch-TimeDomainAllocationList, the UE includes the selected featureCombinationParameter. Applies the pdsch-TimeDomainAllocationList.

If any UL BWP and any DL BWP have the same BWP-Id, the UL BWP and DL BWP are related/connected to each other.

3A is a diagram illustrating an operation of a terminal.

4A is a block diagram showing the internal structure of a terminal to which the present invention is applied.

Referring to the drawing, the terminal includes a control unit 4a-01, a storage unit 4a-02, a transceiver 4a-03, a main processor 4a-04, and an input/output unit 4a-05.

The controller 4a-01 controls overall operations of the UE related to mobile communication. For example, the controller 4a-01 transmits and receives signals through the transceiver 4a-03. Also, the controller 4a-01 writes and reads data in the storage unit 4a-02. To this end, the controller 4a-01 may include at least one processor. For example, the controller 4a-01 may include a communication processor (CP) that controls communication and an application processor (AP) that controls upper layers such as application programs. The controller 4a-01 controls the storage unit and the transceiver so that the terminal operations of FIGS. 2A and 3A are performed. The transceiver is also referred to as a transceiver.

The storage unit 4a-02 stores data such as a basic program for operation of the terminal, an application program, and setting information. The storage unit 4a-02 provides stored data according to the request of the control unit 4a-01.

The transver 4a-03 includes an RF processing unit, a baseband processing unit, and an antenna. The RF processing unit performs functions for transmitting and receiving signals through a wireless channel, such as band conversion and amplification of signals. That is, the RF processing unit up-converts the baseband signal provided from the baseband processing unit into an RF band signal, transmits the signal through an antenna, and down-converts the RF band signal received through the antenna into a baseband signal. The RF processing unit 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 processing unit may perform MIMO, and may receive multiple layers when performing MIMO operation. The baseband processing unit performs a conversion function between a baseband signal and a bit string according to the physical layer standard of the system. For example, during data transmission, the baseband processing unit generates complex symbols by encoding and modulating a transmission bit stream. In addition, when data is received, the baseband processing unit demodulates and decodes the baseband signal provided from the RF processing unit to restore a received bit stream. The transceiver is also referred to as a transceiver.

The main processor 4a-04 controls overall operations except for operations related to mobile communication. The main processor 4a-04 processes the user's input transmitted from the input/output unit 4a-05, stores necessary data in the storage unit 4a-02, and controls the control unit 4a-01 for mobile communication It performs related operations and delivers output information to the input/output unit 4a-05.

The input/output unit 4a-05 is composed of a device that accepts user input, such as a microphone and a screen, and a device that provides information to the user, and performs input and output of user data under the control of the main processor.

4B is a block diagram showing the configuration of a base station according to the present invention.

As shown in the figure, the base station includes a control unit 4b-01, a storage unit 4b-02, a transceiver 4b-03, and a backhaul interface unit 4b-04.

The controller 4b-01 controls overall operations of the base station. For example, the control unit 4b-01 transmits and receives signals through the transceiver 4b-03 or the backhaul interface unit 4b-04. Also, the controller 4b-01 writes and reads data in the storage unit 4b-02. To this end, the controller 4b-01 may include at least one processor. The controller 4b-01 is a transceiver so that the operation of the base station shown in FIG. 2A is performed. storage. Controls the backhaul interface.

The storage unit 4b-02 stores data such as a basic program for the operation of the main base station, an application program, and setting information. In particular, the storage unit 4b-02 may store information on bearers assigned to the connected terminal, measurement results reported from the connected terminal, and the like. In addition, the storage unit 4b-02 may store information that is a criterion for determining whether to provide or stop multiple connections to the terminal. And, the storage unit 4b-02 provides the stored data according to the request of the control unit 4b-01.

The transceiver 4b-03 includes an RF processing unit, a baseband processing unit, and an antenna. The RF processing unit performs functions for transmitting and receiving signals through a wireless channel, such as band conversion and amplification of signals. That is, the RF processor upconverts the baseband signal provided from the baseband processor into an RF band signal, transmits the signal through an antenna, and downconverts the RF band signal received through the antenna into a baseband signal. The RF processing unit may include a transmit filter, a receive filter, an amplifier, a mixer, an oscillator, a DAC, an ADC, and the like. The RF processing unit may perform a downlink MIMO operation by transmitting one or more layers. The baseband processing unit performs a conversion function between a baseband signal and a bit string according to the physical layer standard. For example, during data transmission, the baseband processing unit generates complex symbols by encoding and modulating a transmission bit stream. In addition, when receiving data, the baseband processing unit demodulates and decodes the baseband signal provided from the RF processing unit to restore a received bit stream. The transceiver is also referred to as a transceiver.

The backhaul interface unit 4b-04 provides an interface for communicating with other nodes in the network. That is, the backhaul communication unit 4b-04 converts a bit string transmitted from the main base station to another node, for example, a secondary base station, a core network, etc., into a physical signal, and converts the physical signal received from the other node into a bit string. convert to heat

delete

Claims (5)

In a wireless communication system, in a terminal method,
Receiving a System Information Block (SIB) 1 by a terminal, wherein the SIB1 includes one or more RACH-ConfigCommons, and each of the one or more RACH-ConfigCommons includes 0 or one or more feature-combination-related-information; Each of the one or more feature-combination-related-information includes one feature-combination-information, and the feature-combination-information includes one redcap related field, one smallData related field, and one Message3 repetition related field. and one slice-related field, wherein each of the redcap-related field, the smallData-related field, and the message 3 repetition-related field includes one bit representing one single value, and the slice-related field It includes information corresponding to one or more S-NSSAI (Single-Network Slice Selection Assistance Information), and the information corresponding to the one or more S-NSSAIs is composed of a plurality of bits,
Selecting, by a terminal, feature-combination-related-information based on the feature-combination-information;
A method comprising performing, by a terminal, random access based on the selected feature-combination-related-information.
According to claim 1,
The terminal performs random access further based on feature-combination-common-information associated with the feature-combination-related-information selected by the terminal, and the feature-combination-common-information associated with the feature-combination-related-information is and ra-ContentionResolutionTimer and prach-ConfigurationIndex located in a non-extended part of RACH-ConfigCommon including the feature-combination-related-information.
According to claim 1,
If a field related to Redcap exists in the feature-combination-information, it indicates that RedCap is part of the feature combination, and if a field related to smallData exists in the feature-combination-information, it indicates that small data transmission is part of this feature combination, and the feature-combination-information indicates that small data transmission is part of this feature combination. If the message 3 repetition related field exists in the combination-information, it indicates that the message 3 repetition is part of this feature combination, and if the slice related field exists in the feature-combination-information, the S-indicated by the slice related field information. A method characterized in that the NSSAI indicates that it is part of a feature combination. In a terminal in a wireless communication system,
a transceiver configured to transmit and receive signals; and
It includes a control unit,
The control unit,
SIB1 is received, the SIB1 includes one or more RACH-ConfigCommon, the one or more RACH-ConfigCommon includes zero or one or more feature-combination-related-information, and each of the one or more feature-combination-related-information Each feature-combination-information may include a redcap-related field, a smallData-related field, a message 3 repetition-related field, and a slice-related field, a redcap-related field and a smallData-related field. and message 3 repetition-related fields each include one bit representing a single value, the slice-related field includes information corresponding to one or more S-NSSAIs, and information corresponding to one or more S-NSSAIs. is composed of a plurality of bits,
select feature-combination-related-information based on feature-combination-information;
A terminal configured to perform random access based on selected feature-combination-related-information.
In a wireless communication system, in a base station method,
Transmitting, by a base station, a System Information Block (SIB) 1, wherein the SIB1 includes one or more RACH-ConfigCommons, the one or more RACH-ConfigCommons include 0 or one or more feature-combination-related-information, and the one or more RACH-ConfigCommons include Each of the above feature-combination-related-information may include one feature-combination-information, and the feature-combination-information may include a redcap related field, a smallData related field, a message 3 repetition related field, and a slice related field. Each of the redcap-related field, the smallData-related field, and the message 3 repetition-related field contains one bit representing one single value, and the slice-related field includes one or more S-NSSAI (Single - Network Slice Selection Assistance Information) Includes information corresponding to, and the information corresponding to the one or more S-NSSAIs is composed of a plurality of bits,
The base station performs random access with the terminal based on one feature-combination-related-information among the plurality of feature-combination-related-information and feature-combination-common-information associated with the one feature-combination-related-information. How to include steps to perform.

Images