Initial access method and apparatus for reduced capability terminals in wireless communication systems

Abstract

An initial access method and apparatus for a reduced capability terminal in a wireless communication system are disclosed. According to an embodiment of the present disclosure, a method performed by a terminal in the wireless communication system may include: receiving, from a network, information about one or more feature combinations and information about one or more random access (RA) resource sets associated with the one or more feature combinations; and transmitting a first message of a random access procedure to the network based on one RA resource set of the one or more RA resource sets. Based on the first feature combination being associated with a first RA resource set and the second feature combination being associated with a second RA resource set, the first feature combination may include a first reduced capability feature, the second feature combination may include a second reduced capability feature, and the first reduced capability feature and the second reduced capability feature may not both be included in one feature combination.

Description

[Technical Field]

[0001] The present disclosure relates to wireless communication systems, and more particularly to a method and apparatus for initial access for reduced capability terminals in wireless communication systems. [Background technology]

[0002] Mobile communication systems were developed to provide voice services while ensuring user activity. However, the scope of mobile communication systems has expanded beyond voice to include data services, and the explosive growth in traffic is causing resource shortages. Users are also demanding faster services, so there is a demand for more advanced mobile communication systems.

[0003] The requirements for next-generation mobile communication systems are to accommodate large and explosive data traffic, dramatically increase the transmission rate per user, accommodate a significantly increased number of connected devices, support very low end-to-end latency, and high energy efficiency.To achieve this, various technologies are being researched, including dual connectivity, massive multiple input multiple output (MIMO), in-band full duplex, non-orthogonal multiple access (NOMA), super wideband support, and device networking. Summary of the Invention [Problem to be solved by the invention]

[0004] A technical problem of the present disclosure is to provide an initial access method and apparatus for various reduced capability terminals in a wireless communication system.

[0005] A further technical object of the present disclosure is to provide a method and apparatus for early indication of features based on random access-related resources of various reduced capability terminals in a wireless communication system.

[0006] A further technical problem of the present disclosure is to provide a method and apparatus for bandwidth portion configuration and initial access based thereon for various reduced capability terminals in a wireless communication system.

[0007] Another technical problem will be clearly understood by a person having ordinary skill in the art to which the present disclosure pertains from the following description. [Means for solving the problem]

[0008] A method performed by a terminal in a wireless communication system according to an embodiment of the present disclosure may include (may comprise; may configure; may establish; may configure; may be contiguous; may include; may contain; may have): receiving, from a network, information regarding one or more feature combinations and information regarding one or more random access (RA) resource sets associated with the one or more feature combinations; and transmitting a first message of a random access procedure to the network based on one RA resource set of the one or more RA resource sets. Based on a first feature combination being associated with a first RA resource set and a second feature combination being associated with a second RA resource set, the first feature combination includes a first reduced capability feature, the second feature combination includes a second reduced capability feature, and both the first reduced capability feature and the second reduced capability feature may not be included in one feature combination.

[0009] A method performed by a base station in a wireless communication system according to a further aspect of the present disclosure may include: transmitting, to one or more terminals, information regarding one or more feature combinations and information regarding one or more random access (RA) resource sets associated with the one or more feature combinations; and receiving, from the terminals, a first message of a random access procedure to be transmitted based on one RA resource set among the one or more RA resource sets. Based on the first feature combination being associated with a first RA resource set and the second feature combination being associated with a second RA resource set, the first feature combination may include a first reduced capability feature, the second feature combination may include a second reduced capability feature, and both the first reduced capability feature and the second reduced capability feature may not be included in one feature combination. [Effects of the Invention]

[0010] SUMMARY OF THE INVENTION The present disclosure provides a method and apparatus for initial access for various reduced capability terminals in a wireless communication system.

[0011] According to the present disclosure, a method and apparatus for early indication of features based on random access-related resources of various reduced capability terminals in a wireless communication system can be provided.

[0012] According to the present disclosure, it is possible to provide a method and apparatus for bandwidth portion configuration and initial access based thereon for various reduced capability terminals in a wireless communication system.

[0013] The effects obtained from the present disclosure are not limited to the effects mentioned above, and other effects not mentioned will be clearly understood by those having ordinary skill in the art to which the present disclosure pertains from the following description. [Brief explanation of the drawings]

[0014] The accompanying drawings, which are included as part of the detailed description to aid in understanding the present disclosure, provide examples of the present disclosure and, together with the detailed description, explain the technical features of the present disclosure. [Figure 1] 1 illustrates the structure of a wireless communication system to which the present disclosure can be applied. [Figure 2] 1 illustrates an example of a frame structure in a wireless communication system to which the present disclosure can be applied. [Figure 3] 1 illustrates an example of a resource grid in a wireless communication system to which the present disclosure can be applied. [Figure 4] 1 illustrates an example of a physical resource block in a wireless communication system to which the present disclosure can be applied. [Figure 5] 1 illustrates an example of a slot structure in a wireless communication system to which the present disclosure can be applied. [Figure 6] 1 illustrates examples of physical channels used in a wireless communication system to which the present disclosure can be applied, and a general signal transmission / reception method using the channels. [Figure 7] FIG. 10 is a diagram illustrating an example of the operation of a terminal according to the present disclosure. [Figure 8] FIG. 10 is a diagram for explaining an example of the operation of a base station according to the present disclosure. [Figure 9] FIG. 1 is a block diagram illustrating a wireless communication device according to an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE INVENTION

[0015] Preferred embodiments of the present disclosure will be described in detail below with reference to the accompanying drawings. The detailed description disclosed below together with the accompanying drawings is intended to describe exemplary embodiments of the present disclosure and is not intended to represent the only embodiments in which the present disclosure can be implemented. The detailed description below includes specific details to provide a complete understanding of the present disclosure. However, it will be understood by those skilled in the art that the present disclosure can be implemented without such specific details.

[0016] In some cases, in order to avoid obscuring the concepts of the present disclosure, known structures and devices may be omitted or shown in block diagram form, focusing on the core functions of each structure and device.

[0017] In this disclosure, when a component is "coupled," "coupled," or "connected" to another component, this may include a direct connection as well as an indirect connection where there are other components between them. Also, in this disclosure, the terms "comprise" or "have" specify the presence of stated features, steps, operations, elements, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, elements, components, and / or groups thereof.

[0018] In this disclosure, terms such as "first" and "second" are used only to distinguish one component from another, not to limit the components, and do not limit the order or importance of the components unless otherwise specified. Therefore, within the scope of this disclosure, a first component in one embodiment may be referred to as a second component in another embodiment, and similarly, a second component in one embodiment may be referred to as a first component in another embodiment.

[0019] The terms used in this disclosure are for the purpose of describing particular embodiments and are not intended to limit the scope of the claims. As used in the description of the embodiments and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms unless the context clearly dictates otherwise. The term "and / or" used in this disclosure means that one of the associated listed items may be used, or that any and all possible combinations of two or more of them may be used. Also, in this disclosure, " / " between words has the same meaning as "and / or" unless otherwise specified.

[0020] The present disclosure is described with respect to a wireless communication network or a wireless communication system, and operations performed in a wireless communication network may be performed in the process in which a device (e.g., a base station) that manages the wireless communication network controls the network and transmits or receives signals, or in the process in which a terminal coupled to the wireless network transmits or receives signals to or from the network or between terminals.

[0021] In this disclosure, transmitting or receiving a channel includes transmitting or receiving information or signals on that channel. For example, transmitting a control channel means transmitting control information or signals on the control channel. Similarly, transmitting a data channel means transmitting data information or signals on the data channel.

[0022] Hereinafter, downlink (DL) refers to communication from a base station to a terminal, and uplink (UL) refers to communication from a terminal to a base station. In the downlink, a transmitter may be part of the base station, and a receiver may be part of the terminal. In the uplink, a transmitter may be part of the terminal, and a receiver may be part of the base station. The base station may be expressed as a first communication device, and the terminal may be expressed as a second communication device. A base station (BS) may be replaced with terms such as a fixed station, Node B, evolved-Node B (eNB), Next Generation Node B (gNB), base transceiver system (BTS), access point (AP), network (5G network), artificial intelligence (AI) system / module, road side unit (RSU), robot, unmanned aerial vehicle (UAV), augmented reality (AR) device, virtual reality (VR) device, etc. Furthermore, a terminal may be fixed or mobile, and may be replaced with terms such as UE (User Equipment), MS (Mobile Station), UT (user terminal), MSS (Mobile Subscriber Station), SS (Subscriber Station), AMS (Advanced Mobile Station), WT (Wireless terminal), MTC (Machine-Type Communication) device, M2M (Machine-to-Machine) device, D2D (Device-to-Device) device, vehicle, RSU (road side unit), robot, AI (Artificial Intelligence) module, drone (UAV: Unmanned Aerial Vehicle), AR (Augmented Reality) device, VR (Virtual Reality) device, etc.

[0023] The following technologies may be used for various wireless access systems, such as CDMA, FDMA, TDMA, OFDMA, SC-FDMA, etc. CDMA may be implemented by radio technologies such as Universal Terrestrial Radio Access (UTRA) and CDMA2000. TDMA may be implemented by radio technologies such as Global System for Mobile communications (GSM), General Packet Radio Service (GPRS), and Enhanced Data Rates for GSM Evolution (EDGE). OFDMA may be implemented by radio technologies such as IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802-20, Evolved UTRA (E-UTRA), etc. UTRA is part of the Universal Mobile Telecommunications System (UMTS). 3GPP (3rd Generation Partnership Project: registered trademark; the same applies hereinafter) LTE (Long Term Evolution) is a part of E-UMTS (Evolved UMTS) that uses E-UTRA, and LTE-A (Advanced) / LTE-A pro is an evolved version of 3GPP LTE. 3GPP NR (New Radio or New Radio Access Technology) is an evolved version of 3GPP LTE / LTE-A / LTE-A pro.

[0024] For clarity, the following description will be based on a 3GPP communication system (e.g., LTE-A, NR), but the technical concept of the present disclosure is not limited thereto. LTE refers to technology from 3GPP Technical Specification (TS) 36.xxx Release 8 onward. Specifically, LTE technology from 3GPP TS 36.xxx Release 10 onward is called LTE-A, and LTE technology from 3GPP TS 36.xxx Release 13 onward is called LTE-A pro. 3GPP NR refers to technology from TS 38.xxx Release 15 onward. LTE / NR may be referred to as a 3GPP system. "xxx" refers to the standard document detail number. LTE / NR may be referred to as a 3GPP system. For background technology, terms, abbreviations, etc. used in the description of the present disclosure, please refer to the matters described in standard documents published before the present disclosure. For example, the following documents may be referenced:

[0025] In 3GPP LTE, reference can be made to TS 36.211 (Physical channels and modulation), TS 36.212 (Multiplexing and channel coding), TS 36.213 (Physical layer procedures), TS 36.300 (General description), and TS 36.331 (Radio resource control).

[0026] For 3GPP NR, reference can be made to TS 38.211 (Physical Channels and Modulation), TS 38.212 (Multiplexing and Channel Coding), TS 38.213 (Physical Layer Procedures for Control), TS 38.214 (Physical Layer Procedures for Data), TS 38.300 (General Description of NR and NG-RAN (New Generation-Radio Access Network)), and TS 38.331 (Radio Resource Control Protocol Standard).

[0027] The terminology abbreviations that may be used in this disclosure are defined as follows:

[0028] - BM: Beam management

[0029] - CQI: Channel Quality Indicator

[0030] - CRI: Channel state information-reference signal resource indicator

[0031] - CSI: Channel State Information

[0032] - CSI-IM: Channel state information-interference measurement

[0033] - CSI-RS: Channel state information-reference signal

[0034] - DMRS: Demodulation Reference Signal

[0035] - FDM: frequency division multiplexing

[0036] - FFT: Fast Fourier transform

[0037] - IFDMA: Interleaved frequency division multiple access

[0038] - IFFT: Inverse fast Fourier transform

[0039] - L1-RSRP: Layer 1 reference signal received power

[0040] - L1-RSRQ: Layer 1 reference signal received quality

[0041] - MAC: Medium Access Control

[0042] - NZP: Non-zero power

[0043] - OFDM: Orthogonal frequency division multiplexing

[0044] - PDCCH: Physical downlink control channel

[0045] - PDSCH: Physical downlink shared channel

[0046] - PMI: Precoding matrix indicator

[0047] - RE: resource element

[0048] - RI: Rank indicator

[0049] - RRC: Radio resource control

[0050] - RSSI: received signal strength indicator

[0051] - Rx: Reception

[0052] - QCL: quasi co-location

[0053] - SINR: Signal to interference and noise ratio

[0054] - SSB (or SS / PBCH block): Synchronization signal block (including primary synchronization signal (PSS), secondary synchronization signal (SSS), and physical broadcast channel (PBCH))

[0055] - TDM: time division multiplexing

[0056] - TRP: transmission and reception point

[0057] - TRS: Tracking reference signal

[0058] - Tx: transmission

[0059] - UE: User equipment

[0060] - ZP: Zero power

[0061] System in general

[0062] As more communication devices require greater communication capacity, there is a growing need for improved mobile broadband communication compared to existing radio access technologies (RATs). Massive machine-type communications (MTC), which connects multiple devices and objects to provide a variety of services anytime, anywhere, is also one of the key issues being considered for next-generation communications. In addition, communication system designs that take into account reliability- and latency-sensitive services / terminals are also being discussed. Thus, the introduction of next-generation RATs that take into account technologies such as enhanced mobile broadband communication (eMBB), massive MTC (mMTC), and ultra-reliable and low latency communication (URLLC) is being discussed. For convenience, these technologies will be referred to as NR in this disclosure. NR is an example of a 5G RAT.

[0063] New RAT systems, including NR, use an OFDM transmission scheme or a similar transmission scheme. A new RAT system may follow OFDM parameters different from those of LTE. Alternatively, a new RAT system may follow the existing LTE / LTE-A numerology but support a larger system bandwidth (e.g., 100 MHz). Alternatively, one cell may support multiple numerologies. That is, terminals operating with different numerologies may coexist within one cell.

[0064] A numerology corresponds to a subcarrier spacing in the frequency domain. Different numerologies can be defined by scaling the reference subcarrier spacing by an integer N.

[0065] FIG. 1 illustrates the structure of a wireless communication system to which the present disclosure can be applied.

[0066] Referring to FIG. 1, the NG-RAN is composed of gNBs that provide an NG-Radio Access (NG-RA) user plane (i.e., a new access stratum (AS) sublayer / packet data convergence protocol (PDCP) / radio link control (RLC) / MAC / PHY) and control plane (RRC) protocol termination for UEs. The gNBs are interconnected via an Xn interface. The gNBs are also connected to a New Generation Core (NGC) via an NG interface. More specifically, the gNBs are connected to an Access and Mobility Management Function (AMF) via an N2 interface and to a User Plane Function (UPF) via an N3 interface.

[0067] FIG. 2 illustrates a frame structure in a wireless communication system to which the present disclosure can be applied.

[0068] An NR system can support multiple numerologies. Here, a numerology may be defined by subcarrier spacing and cyclic prefix (CP) overhead. In this case, multiple subcarrier spacings may be derived by scaling the base (reference) subcarrier spacing by an integer N (or μ). Furthermore, even if it is assumed that very low subcarrier spacings are not used at very high carrier frequencies, the numerology used may be selected independently of the frequency band. Furthermore, an NR system may support various frame structures based on multiple numerologies.

[0069] The following describes OFDM numerologies and frame structures that can be considered in an NR system. A number of OFDM numerologies supported in an NR system may be defined as shown in Table 1 below.

[0070] [Table 1]

[0071] NR supports multiple numerologies (or subcarrier spacing (SCS)) to support various 5G services. For example, a 15 kHz SCS supports wide areas in traditional cellular bands, a 30 kHz / 60 kHz SCS supports dense urban areas, lower latency, and wider carrier bandwidths, and a 60 kHz or higher SCS supports bandwidths greater than 24.25 GHz to overcome phase noise.

[0072] The NR frequency band is defined as two types of frequency ranges (FR1 and FR2). FR1 and FR2 may be configured as shown in Table 2 below. FR2 can also refer to millimeter wave (mmW).

[0073] [Table 2]

[0074] In relation to the frame structure in an NR system, the size of the various fields in the time domain is T c =1 / (Δf max N f ) where Δf max =480 10 3Hz and N f = 4096. Downlink and uplink transmission is T f =1 / (Δf max N f / 100)·T c The radio frame is organized into radio frames each having a duration of T = 10 ms. sf =(Δf max N f / 1000)·T c In this case, there may be one set of frames for the uplink and one set of frames for the downlink. In addition, transmission from a terminal in uplink frame number i begins T TA =(N TA +N TA,offset )T c For a subcarrier spacing configuration μ, a slot is allocated within a subframe. s μ ∈{0,...,N slot subframe,μ -1}, and n s,f μ ∈{0,...,N slot frame,μ The slots are numbered in increasing order {N -1}. symb slot It consists of N consecutive OFDM symbols, symb slot is determined by the CP. s μ The start of OFDM symbol n s μ N symb slotNot all terminals can transmit and receive at the same time, which means that not all OFDM symbols in a downlink slot or an uplink slot can be used. Table 3 shows the number of OFDM symbols per slot (N symb slot ), the number of slots per radio frame (N slot frame,μ ), the number of slots per subframe (N slot subframe,μ ) and Table 4 shows the number of OFDM symbols per slot, the number of slots per radio frame, and the number of slots per subframe in the extended CP.

[0075] [Table 3]

[0076] [Table 4]

[0077] FIG. 2 shows an example where μ=2 (SCS is 60 kHz), and referring to Table 3, one subframe can include four slots. The {1, 2, 4} slots shown in FIG. 2 are an example, and the number of slots that can be included in one subframe is defined as shown in Table 3 or Table 4. A mini-slot can include 2, 4, or 7 symbols, or more or fewer symbols. Regarding physical resources in an NR system, antenna ports, resource grids, resource elements, resource blocks, carrier parts, and the like may be considered. Hereinafter, the physical resources that can be considered in an NR system will be described in detail.

[0078] First, with respect to antenna ports, the antenna port is defined so that the channel on which symbols on the antenna port are carried can be inferred from the channel on which other symbols on the same antenna port are carried. If the large-scale properties of the channel on which symbols on one antenna port are carried can be inferred from the channel on which symbols on the other antenna port are carried, the two antenna ports are said to have a QC / QCL (quasi co-located or quasi co-location) relationship. Here, the large-scale properties include one or more of delay spread, Doppler spread, frequency shift, average received power, and received timing.

[0079] FIG. 3 illustrates an example of a resource grid in a wireless communication system to which the present disclosure can be applied.

[0080] JPEG2026504834000006.jpg141168

[0081] Point A serves as a common reference point for the resource block grid and is obtained as follows:

[0082] - offsetToPointA for the primary cell (PCell) downlink indicates the frequency offset between point A and the lowest subcarrier of the lowest resource block that overlaps with the SS / PBCH block used by the terminal for initial cell selection. It is expressed in resource block units assuming 15 kHz subcarrier spacing for FR1 and 60 kHz subcarrier spacing for FR2.

[0083] - absoluteFrequencyPointA indicates the frequency-location of point A expressed as in ARFCN (absolute radio-frequency channel number).

[0084] Common resource blocks are numbered from 0 upwards in the frequency domain for a subcarrier spacing setting μ. The center of subcarrier 0 of common resource block 0 for a subcarrier spacing setting μ coincides with 'point A'. Common resource block number n in the frequency domain CRB μ The relationship between the resource elements (k, l) for the subcarrier spacing setting μ is given by the following equation 1.

[0085]

number

[0086] In Equation 1, k is defined relative to point A so that k=0 corresponds to the subcarrier centered at point A. The physical resource blocks are numbered from 0 to N within the bandwidth part (BWP). BWP,i size,μ The numbering is from -1 to i, where i is the number of the BWP. PRB and common resource block n CRB The relationship between is given by Equation 2 below.

[0087]

number

[0088] N BWP,i start,μ is the common resource block where the BWP starts relative to common resource block 0.

[0089] Fig. 4 illustrates a physical resource block in a wireless communication system to which the present disclosure can be applied, and Fig. 5 illustrates a slot structure in a wireless communication system to which the present disclosure can be applied.

[0090] 4 and 5, a slot includes multiple symbols in the time domain. For example, in the general CP, one slot includes seven symbols, while in the extended CP, one slot includes six symbols.

[0091] A carrier wave includes multiple subcarriers in the frequency domain. A resource block (RB) is defined as multiple (e.g., 12) consecutive subcarriers in the frequency domain. A bandwidth part (BWP) is defined as multiple consecutive (physical) resource blocks in the frequency domain, and may correspond to one numerology (e.g., SCS, CP length, etc.). A carrier wave can include up to N (e.g., 5) BWPs. Data communication is performed using activated BWPs, and only one BWP may be activated for one terminal. Each element in the resource grid is called a resource element (RE), and one complex symbol may be mapped to it.

[0092] The NR system may support up to 400 MHz per component carrier (CC). If a terminal operating on such a wideband CC keeps the radio frequency (RF) chip for the entire CC on at all times, battery consumption may increase. Considering various application cases (e.g., eMBB, URLLC, MMTc, V2X, etc.) operating within a single wideband CC, different numerologies (e.g., subcarrier spacing, etc.) may be supported for each frequency band within the CC. Alternatively, each terminal may have different capabilities for maximum bandwidth. In consideration of this, a base station may instruct a terminal to operate only with a portion of the bandwidth of a wideband CC, rather than the entire bandwidth. For convenience, this portion of bandwidth is defined as a bandwidth part (BWP). A BWP may consist of contiguous RBs on the frequency axis and may correspond to one numerology (e.g., subcarrier spacing, CP length, slot / minislot duration).

[0093] Meanwhile, a base station can configure multiple BWPs within one CC configured for a terminal. For example, a BWP occupying a relatively small frequency domain can be configured in a PDCCH monitoring slot, and the PDSCH indicated by the PDCCH can be scheduled on a larger BWP. Alternatively, if UEs are concentrated in a specific BWP, other BWPs can be configured for some terminals for load balancing. Alternatively, considering frequency domain inter-cell interference cancellation between neighboring cells, some spectrum from the entire bandwidth can be excluded and both BWPs can be configured within the same slot. That is, a base station can configure at least one DL / UL BWP for a terminal associated with a wideband CC. The base station can activate at least one DL / UL BWP configured at a specific time (through L1 signaling, MAC Control Element (CE), RRC signaling, etc.). In addition, the base station can instruct switching to another configured DL / UL BWP (by L1 signaling, MAC CE, RRC signaling, etc.). Alternatively, the base station may switch to a predetermined DL / UL BWP when a timer value expires on a timer basis. In this case, the activated DL / UL BWP is defined as an active DL / UL BWP. However, in situations where the UE is performing an initial access procedure or before an RRC connection is set up, the UE may not be able to receive the configuration for the DL / UL BWP. Therefore, the DL / UL BWP assumed by the UE in such a situation is defined as the initially active DL / UL BWP.

[0094] FIG. 6 illustrates examples of physical channels used in a wireless communication system to which the present disclosure can be applied, and a general signal transmission / reception method using the physical channels.

[0095] In a wireless communication system, a terminal receives information from a base station through a downlink and transmits information to the base station through an uplink. Information exchanged between the base station and the terminal includes data and various control information, and various physical channels exist depending on the type / use of the information exchanged.

[0096] When a terminal is powered on or newly enters a cell, it performs an initial cell search, such as synchronizing with a base station (S601). To do this, the terminal receives a primary synchronization signal (PSS) and a secondary synchronization signal (SSS) from the base station to synchronize with the base station and acquire information such as a cell identifier (ID). The terminal then receives a physical broadcast channel (PBCH) from the base station to acquire in-cell broadcast information. Meanwhile, the terminal can receive a downlink reference signal (DL RS) during the initial cell search phase to check the downlink channel status.

[0097] After completing the initial cell search, the terminal receives a physical downlink control channel (PDCCH) and a physical downlink shared channel (PDSCH) based on the information carried on the PDCCH, thereby obtaining more specific system information (S602).

[0098] Meanwhile, when the terminal first connects to the base station or when there are no radio resources for signal transmission, the terminal can perform a random access procedure (RACH) with the base station (steps S603 to S606). To this end, the terminal transmits a specific sequence as a preamble on a physical random access channel (PRACH) (steps S603 and S605) and can receive a response message to the preamble on a PDCCH and a corresponding PDSCH (steps S604 and S606). In the case of a contention-based RACH, a contention resolution procedure can also be performed.

[0099] After performing the above-described procedures, the UE can then perform PDCCH / PDSCH reception (S607) and physical uplink shared channel (PUSCH) / physical uplink control channel (PUCCH) transmission (S608) as a general uplink / downlink signal transmission procedure. In particular, the UE receives downlink control information (DCI) via the PDCCH. Here, DCI includes control information such as resource allocation information for the UE, and its format varies depending on its purpose.

[0100] Meanwhile, control information that a terminal transmits to a base station on the uplink or that the terminal receives from a base station includes downlink / uplink ACK / NACK (Acknowledgement / Non-Acknowledgement) signals, CQI (Channel Quality Indicator), PMI (Precoding Matrix Indicator), RI (Rank Indicator), etc. In a 3GPP LTE system, a terminal can transmit the above-mentioned control information such as CQI / PMI / RI on a PUSCH and / or a PUCCH.

[0101] Table 5 shows an example of a DCI format in an NR system.

[0102] [Table 5]

[0103] Referring to Table 5, DCI formats 0_0, 0_1, and 0_2 may include resource information related to PUSCH scheduling (e.g., UL / SUL (Supplementary UL), frequency resource allocation, time resource allocation, frequency hopping, etc.), transport block (TB)-related information (e.g., Modulation Coding and Scheme (MCS), New Data Indicator (NDI), Redundancy Version (RV), etc.), Hybrid-Automatic Repeat and Request (HARQ)-related information (e.g., process number, Downlink Assignment Index (DAI), PDSCH-HARQ feedback timing, etc.), multiple antenna-related information (e.g., DMRS sequence initialization information, antenna port, CSI request, etc.), and power control information (e.g., PUSCH power control, etc.), and the control information included in each DCI format may be predefined. DCI format 0_0 is used for PUSCH scheduling in one cell. The information included in DCI format 0_0 is CRC (cyclic redundancy check) scrambled using C-RNTI (Cell Radio Network Temporary Identifier, Cell RNTI), CS-RNTI (Configured Scheduling RNTI), or MCS-C-RNTI (Modulation Coding Scheme Cell RNTI) and then transmitted.

[0104] DCI format 0_1 ​​is used to indicate scheduling of one or more PUSCHs in one cell or downlink feedback information of configured grants (CGs) to a terminal. The information included in DCI format 0_1 ​​is CRC-scrambled by C-RNTI, CS-RNTI, SP-CSI-RNTI (Semi-Persistent CSI RNTI), or MCS-C-RNTI and then transmitted.

[0105] DCI format 0_2 is used for scheduling the PUSCH in one cell. Information included in DCI format 0_2 is CRC scrambled using the C-RNTI, CS-RNTI, SP-CSI-RNTI, or MCS-C-RNTI and then transmitted.

[0106] Next, DCI formats 1_0, 1_1, and 1_2 may include resource information related to PDSCH scheduling (e.g., frequency resource allocation, time resource allocation, VRB (virtual resource block)-PRB (physical resource block) mapping, etc.), transmission block (TB) related information (e.g., MCS, NDI, RV, etc.), HARQ related information (e.g., process number, DAI, PDSCH-HARQ feedback timing, etc.), multiple antenna related information (e.g., antenna port, TCI (transmission configuration indicator), SRS (sounding reference signal) request, etc.), and PUCCH related information (e.g., PUCCH power control, PUCCH resource indicator, etc.), and the control information included in each DCI format may be pre-defined.

[0107] DCI format 1_0 is used for scheduling PDSCH in one DL cell. Information included in DCI format 1_0 is CRC scrambled using C-RNTI, CS-RNTI, or MCS-C-RNTI and then transmitted.

[0108] DCI format 1_1 is used for scheduling PDSCH in one cell. Information included in DCI format 1_1 is CRC scrambled using C-RNTI, CS-RNTI, or MCS-C-RNTI and then transmitted.

[0109] DCI format 1_2 is used for scheduling PDSCH in one cell. Information included in DCI format 1_2 is CRC scrambled using C-RNTI, CS-RNTI, or MCS-C-RNTI and then transmitted.

[0110] Initial access for various reduced capability terminals

[0111] In existing wireless communication systems, reduced capability (RedCap) terminals have been defined to support devices that meet low power, low cost, and low latency requirements suitable for smart factories, wearable devices, etc. In addition, support for enhanced reduced capability (eRedCap) terminals is being discussed. For example, a RedCap terminal may support a peak data rate of 50 Mbps, while an eRedCap terminal may correspond to a lower performance terminal type that supports a peak data rate of 10 Mbps. In wireless communication systems that mix high performance (or non-RedCap) terminals such as existing smartphones, existing RedCap terminals, and the newly defined eRedCap terminals, a new method is required to efficiently enable initial access for terminals.

[0112] For example, after a terminal establishes a connection through initial access, appropriate random access procedures and scheduling methods need to be defined for various terminal types (or groups / combinations of supported capabilities / features) to transmit and receive unicast data between the terminal and the network (or base station). Also, an early indication method is required to inform the network of the terminal type (or supported capabilities / feature groups / combinations) before the terminal reports its specific capability information to the network.

[0113] Various types of terminals assumed in this disclosure may include RedCap, eRedCap, and general terminals. Furthermore, eRedCap terminals may be classified into eRedCap terminals that support a maximum bandwidth of 20 MHz (i.e., do not support reduced bandwidth) and eRedCap terminals that support a maximum bandwidth of less than 20 MHz (e.g., 5 MHz) (i.e., support reduced bandwidth) (and eRedCap terminals with other capabilities). For example, a reduced capability terminal (e.g., (e)RedCap) that can only operate in a narrow bandwidth may have limited decoding performance and available bandwidth size compared to a high-performance terminal such as a smartphone. Before a terminal provides information about its capabilities and / or functions to the network through a terminal capability report, the network can perform scheduling for the terminal, assuming minimum performance. A method for early indication of the terminal type (or supported capabilities / feature group / combination) through an initial access procedure, such as a terminal random access procedure, before reporting terminal capabilities and supporting the network's detection of this information also needs to be improved.

[0114] FIG. 7 is a diagram illustrating an example of the operation of the terminal according to the present disclosure.

[0115] In step S710, the terminal may receive information about one or more feature combinations and information about one or more random access (RA) resource sets associated with the one or more feature combinations from the network.

[0116] For example, one feature combination may correspond to a combination of one or more fields / features among various fields (i.e., features) such as RedCap, eRedCap, smallData (transmission of data and / or signaling in an RRC inactive state), nsag (network slice AS group), msg3-repetition (repeated transmission of the third message of the random access procedure), etc. That is, in the information for configuring the feature combination, a feature included in any of the feature combinations has the field set to true (or is present in the feature combination configuration information), and another feature not included in the feature combination does not have the field set to true (or may not be present in the feature combination configuration information). Different feature combinations may include different fields / features.

[0117] In some examples of the present disclosure, the eRedCap feature (or the first reduced capability feature) and the RedCap feature (or the second reduced capability feature) may not both be included in one feature combination. That is, if one feature combination includes an eRedCap feature, it may not include the RedCap feature. Or, if one feature combination includes a RedCap feature, it may not include the eRedCap feature. Or, one feature combination may include neither a RedCap feature nor an eRedCap feature.

[0118] In some examples of the present disclosure, one feature combination (or feature group or capability set) may be associated with one RA resource set. The RA resource set may correspond to a set of preambles used in the random access procedure. For example, the preambles for a feature combination may be defined by a starting preamble, a preamble number, etc.

[0119] For example, a first feature combination may include an eRedCap feature (or a first reduced capability feature). A first RA set may be associated with the first feature combination. A second feature combination may include a RedCap feature (or a second reduced capability feature). A second RA set may be associated with the second feature combination. Information about a feature combination and its associated RA resource set may include all of the first feature combination, the first RA set, the second feature combination, and the second RA set, or may include only one of them.

[0120] Information about one or more feature combinations and information about one or more RA resource sets associated with the one or more feature combinations may be included in a system information block (SIB) and received by the terminal. The system information may be provided commonly to multiple (or all) terminals in a cell.

[0121] In step S720, the terminal may transmit a first message of the random access procedure to the network based on one RA resource set of the one or more RA resource sets.

[0122] In some examples of the present disclosure, when a terminal supports an eRedCap feature (or a first reduced capability feature), one RA resource set used to transmit the first message may be a first RA set (i.e., a preamble set associated with a first feature combination that includes the eRedCap feature (or a first reduced capability feature)).

[0123] In some examples of the present disclosure, the eRedCap feature (or the first reduced capability feature) may be configured in an RA resource set (or preamble set) configured for a four-stage RA type. That is, an eRedCap terminal can transmit a first message (or Msg1) of a four-stage random access procedure including a preamble selected from an RA resource set associated with a feature combination including the eRedCap feature. The RedCap feature (or the second reduced capability feature) may be configured in an RA resource set (or preamble set) configured for a four-stage RA type, or may be configured in an RA resource set (or preamble set) configured for a two-stage RA type. That is, a RedCap terminal can transmit a first message (or Msg1) of a four-stage random access procedure or a first message (or MsgA) of a two-stage random access procedure including a preamble selected from an RA resource set associated with a feature combination including the RedCap feature.

[0124] In some examples of the present disclosure, a terminal may support the eRedCap feature (or a first reduced capability feature), but among one or more (or all configured) RA resource sets, there may be no RA resource set associated with a first feature combination including the eRedCap feature (or the first reduced capability feature). In this case, one RA resource set used to transmit the first message may be a second RA set (i.e., a preamble set associated with a second feature combination including the RedCap feature (or a second reduced capability feature)).

[0125] The terminal may receive a second message (Msg2, or a random access response (RAR)) from the network after transmitting a first message (Msg1, or a PRACH preamble) of the four-stage random access procedure. After this, the terminal may receive a fourth message (Msg4, a contention resolution message) from the network after transmitting a third message (Msg3, or PUSCH data). Alternatively, the terminal may receive a second message (MsgB) from the network after transmitting a first message (MsgA, or a PRACH preamble transmission and a PUSCH data transmission) of the two-stage random access procedure. The PUSCH data transmitted by the terminal using Msg3 of the four-stage random access procedure or MsgA of the two-stage random access procedure may correspond to a message transmitted on the UL-SCH, and the message may include a common control channel (CCCH) service data unit (SDU).

[0126] In some examples of the present disclosure, the LCID (logical channel identifier) ​​for the UL-SCH / CCCH may be defined as a value that distinguishes between a terminal that supports the eRedCap feature (or a first reduced capability feature) and a terminal that supports the RedCap feature (or a second reduced capability feature).

[0127] In some examples of the present disclosure, an initial uplink (UL) BWP may be configured commonly or independently for a terminal supporting the eRedCap feature (or a first reduced capability feature) and a terminal supporting the RedCap feature (or a second reduced capability feature). The first message (Msg1) and / or the third message (Msg3) of the four-stage random access procedure, or the first message (MsgA) of the two-stage random access procedure, may be transmitted on the initial UL BWP.

[0128] In some examples of the present disclosure, an initial downlink (DL) BWP may be configured jointly or independently for a terminal supporting the eRedCap feature (or a first reduced capability feature) and a terminal supporting the RedCap feature (or a second reduced capability feature). The second message (Msg2) and / or the fourth message (Msg4) of the four-stage random access procedure, or the second message (MsgB) of the two-stage random access procedure, may be received on the initial DL BWP.

[0129] In some examples of the present disclosure, the eRedCap feature (or the first reduced capability feature) may be a terminal that supports a reduced bandwidth (e.g., a bandwidth of less than 20 MHz (e.g., 5 MHz) for unicast, as described below), or a terminal that does not support the reduced bandwidth (e.g., a terminal that supports a 20 MHz bandwidth for unicast). That is, terminals having the eRedCap feature (or the first reduced capability feature) can use a common RA resource set and a common LCID regardless of whether they are terminals that support the reduced bandwidth or terminals that support the reduced bandwidth. Terminals that support the reduced bandwidth of such an eRedCap feature (or the first reduced capability feature) and terminals that do not support the reduced bandwidth can support a peak data rate of 10 Mbps.

[0130] The method described in the example of Fig. 7 may be performed by the first device 100 in Fig. 9 described below. For example, the one or more processors 102 of the first device 100 in Fig. 9 may be configured to receive, from a network via one or more transceivers, information regarding one or more feature combinations and information regarding one or more RA resource sets associated with the one or more feature combinations, and to transmit, to the network via the one or more transceivers, a first message of a random access procedure based on one of the one or more RA resource sets. Note that the one or more memories 104 of the first device 100 may store instructions for performing the method described in the example of Fig. 7 or the example described below, when executed by the one or more processors 102.

[0131] For example, one feature combination may correspond to a combination of one or more fields / features among various fields (i.e., features) such as RedCap, eRedCap, smallData (transmission of data and / or signaling in an RRC inactive state), nsag (network slice AS group), msg3-repetition (repeated transmission of the third message of the random access procedure), etc. That is, in the information for configuring the feature combination, a feature included in any of the feature combinations has the field set to true (or is present in the feature combination configuration information), and another feature not included in the feature combination does not have the field set to true (or may not be present in the feature combination configuration information). Different feature combinations may include different fields / features.

[0132] In some examples of the present disclosure, the eRedCap feature (or the first reduced capability feature) and the RedCap feature (or the second reduced capability feature) may not both be included in one feature combination. That is, if one feature combination includes an eRedCap feature, it may not include the RedCap feature. Or, if one feature combination includes a RedCap feature, it may not include the eRedCap feature. Or, one feature combination may include neither a RedCap feature nor an eRedCap feature.

[0133] In some examples of the present disclosure, one feature combination (or feature group or capability set) may be associated with one RA resource set. The RA resource set may correspond to a set of preambles used in a random access procedure. For example, the preambles for a feature combination may be defined by a starting preamble, a preamble number, etc.

[0134] For example, a first feature combination may include an eRedCap feature (or a first reduced capability feature). A first RA set may be associated with the first feature combination. A second feature combination may include a RedCap feature (or a second reduced capability feature). A second RA set may be associated with the second feature combination. Information about a feature combination and its associated RA resource set may include all of the first feature combination, the first RA set, the second feature combination, and the second RA set, or may include only one of them.

[0135] Information about one or more feature combinations and information about one or more RA resource sets associated with the one or more feature combinations may be included in a system information block (SIB) and received by the terminal. The system information may be provided commonly to multiple (or all) terminals in a cell.

[0136] In step S720, the terminal may transmit a first message of a random access procedure to the network based on one RA resource set of the one or more RA resource sets.

[0137] In some examples of the present disclosure, if a terminal supports an eRedCap feature (or a first reduced capability feature), one RA resource set used to transmit the first message may be a first RA set (i.e., a preamble set associated with a first feature combination that includes the eRedCap feature (or a first reduced capability feature)).

[0138] In some examples of the present disclosure, the eRedCap feature (or the first reduced capability feature) may be configured in an RA resource set (or preamble set) configured for a four-stage RA type. That is, an eRedCap terminal can transmit a first message (or Msg1) of a four-stage random access procedure including a preamble selected from an RA resource set associated with a feature combination including the eRedCap feature. The RedCap feature (or the second reduced capability feature) may be configured in an RA resource set (or preamble set) configured for a four-stage RA type, or may be configured in an RA resource set (or preamble set) configured for a two-stage RA type. That is, a RedCap terminal can transmit a first message (or Msg1) of a four-stage random access procedure or a first message (or MsgA) of a two-stage random access procedure including a preamble selected from an RA resource set associated with a feature combination including the RedCap feature.

[0139] In some examples of the present disclosure, a terminal may support the eRedCap feature (or a first reduced capability feature), but one or more (or all configured) RA resource sets may not include an RA resource set associated with a first feature combination including the eRedCap feature (or a first reduced capability feature). In this case, one RA resource set used to transmit the first message may be a second RA set (i.e., a preamble set associated with a second feature combination including the RedCap feature (or a second reduced capability feature)).

[0140] The terminal may receive a second message (Msg2 or a random access response (RAR)) from the network after transmitting a first message (Msg1 or a PRACH preamble) of the four-stage random access procedure. After transmitting a third message (Msg3 or PUSCH data), the terminal may receive a fourth message (Msg4, a contention resolution message) from the network. Alternatively, the terminal may receive a second message (MsgB) from the network after transmitting a first message (MsgA, or a PRACH preamble transmission and a PUSCH data transmission) of the two-stage random access procedure. The PUSCH data transmitted by the terminal using Msg3 of the four-stage random access procedure or MsgA of the two-stage random access procedure may correspond to a message transmitted on the UL-SCH, and the message may include a common control channel (CCCH) service data unit (SDU).

[0141] In some examples of the present disclosure, the LCID (logical channel identifier) ​​for the UL-SCH / CCCH may be defined as a value that distinguishes between a terminal that supports the eRedCap feature (or a first reduced capability feature) and a terminal that supports the RedCap feature (or a second reduced capability feature).

[0142] In some examples of the present disclosure, an initial uplink (UL) BWP may be configured commonly or independently for a terminal supporting the eRedCap feature (or a first reduced capability feature) and a terminal supporting the RedCap feature (or a second reduced capability feature). The first message (Msg1) and / or the third message (Msg3) of the four-stage random access procedure, or the first message (MsgA) of the two-stage random access procedure, may be transmitted on the initial UL BWP.

[0143] In some examples of the present disclosure, an initial downlink (DL) BWP may be configured jointly or independently for a terminal supporting the eRedCap feature (or a first reduced capability feature) and a terminal supporting the RedCap feature (or a second reduced capability feature). The second message (Msg2) and / or the fourth message (Msg4) of the four-stage random access procedure, or the second message (MsgB) of the two-stage random access procedure, may be received on the initial DL BWP.

[0144] In some examples of the present disclosure, the eRedCap feature (or the first reduced capability feature) may be a terminal that supports a reduced bandwidth (e.g., a bandwidth of less than 20 MHz (e.g., 5 MHz) for unicast, as described below), or a terminal that does not support the reduced bandwidth (e.g., a terminal that supports a 20 MHz bandwidth for unicast). In other words, terminals having the eRedCap feature (or the first reduced capability feature) can use a common RA resource set and a common LCID regardless of whether they support the reduced bandwidth or not. Terminals that support the reduced bandwidth of such an eRedCap feature (or the first reduced capability feature) and terminals that do not support the reduced bandwidth can support a peak data rate of 10 Mbps.

[0145] The method described in the example of Fig. 7 may be performed by the first device 100 in Fig. 9 described later. For example, the one or more processors 102 of the first device 100 in Fig. 9 may be configured to receive, from a network via one or more transceivers, information regarding one or more feature combinations and information regarding one or more RA resource sets associated with the one or more feature combinations, and to transmit, to the network via the one or more transceivers, a first message of a random access procedure based on one of the one or more RA resource sets. Note that the one or more memories 104 of the first device 100 may store instructions for performing the method described in the example of Fig. 7 or the example described later, when executed by the one or more processors 102.

[0146] FIG. 8 is a diagram illustrating an example of the operation of the base station according to the present disclosure.

[0147] In step S810, the base station receives information about one or more feature combinations and information about one or more RA resource sets associated with the one or more feature combinations as follows: The information may be transmitted to one or more terminals, for example, the information may be commonly transmitted to one or more terminals as system information.

[0148] In step S820, the base station may receive from a terminal a first message of the random access procedure, the first message being transmitted based on one RA resource set among one or more RA resource sets. There may be multiple terminals that simultaneously transmit the first message based on the same RA resource set during random access. Different terminals may select different RA resources (or preambles) from the same RA resource set to transmit the first message, and if multiple terminals select the same RA resource, contention may be resolved in a subsequent step of the random access procedure.

[0149] In the example of Figure 8, the specific features of one or more feature combinations associated with the first and second reduced capabilities, one or more RA resource sets, LCID for UL-SCH / CCCH, initial UL / DL-BWP, etc. are the same as those described with reference to Figure 7, and duplicated descriptions will be omitted.

[0150] The method described in the example of Fig. 8 may be performed by the second device 200 of Fig. 9 described later. For example, the one or more processors 202 of the second device 200 of Fig. 9 may be configured to transmit information regarding one or more feature combinations and information regarding one or more RA resource sets associated with the one or more feature combinations to one or more terminals via one or more transceivers, and receive, from the terminals via the one or more transceivers, a first message of a random access procedure that is transmitted based on one of the one or more RA resource sets. Note that the one or more memories 204 of the second device 200 may store instructions for performing the method described in the example of Fig. 8 or the example described later, when executed by the one or more processors 202.

[0151] [Embodiment] Below, various examples for initial access for various reduced capability terminals according to the present disclosure are described.

[0152] Example 1

[0153] This embodiment relates to the initial bandwidth portion (BWP) in the initial access of various reduced capability terminals.

[0154] In the following description, the term (separate) initial BWP includes (separate) initial UL BWP, (separate) initial DL BWP, or (separate) initial UL BWP and (separate) initial DL BWP.

[0155] For example, information regarding the initial BWP for each type / feature of the terminal may be provided by system information (e.g., SIB) commonly provided to terminals in a cell including various reduced capability terminals. Thus, the network / base station can determine that a terminal operating on a specific initial BWP has a specific type / feature before receiving a terminal capability report message (e.g., an RRC message). For example, the network / base station can optimize scheduling for the terminal to match the terminal-specific performance of various types / features with reduced capabilities. This also solves problems that occur in a situation where terminals with various types / features are mixed during the initial access process.

[0156] For example, a situation may be assumed in which a first reduced capability (e.g., eRedCap) terminal that does not support reduced bandwidth (e.g., supports a maximum bandwidth of 20 MHz), a terminal that supports reduced bandwidth (e.g., supports a maximum bandwidth less than 20 MHz), a second reduced capability terminal (e.g., RedCap terminal), and a general high-performance terminal (e.g., non-RedCap terminal) coexist. Specifically, various capabilities may be defined in which the bandwidth size that a terminal can process for transmitting and receiving unicast data (e.g., PDSCH / PUSCH data scheduled by a PDCCH CRC-scrambled by a C-RNTI or a temporary C-RNTI) is up to 100 MHz, 20 MHz, or less than 20 MHz. For example, a bandwidth less than 20 MHz may correspond to a bandwidth of 5 MHz or less, and will be referred to as a 5 MHz bandwidth in the following description as a non-limiting example. For example, a first reduced capability terminal (e.g., eRedCap) may be further classified as an eRedCap-1 terminal supporting a maximum bandwidth of 20 MHz, an eRedCap-2 terminal supporting a maximum bandwidth of 5 MHz, or an eRedCap-X (X=3, 4, ...) terminal supporting one or more other distinct features / capabilities. In this disclosure, as a representative example, it is assumed that a RedCap terminal supports unicast scheduling of a 20 MHz bandwidth and a peak data rate of 50 Mbps, an eRedCap-1 terminal supports unicast scheduling of a 20 MHz bandwidth and a peak data rate of 10 Mbps, and an eRedCap-2 terminal supports unicast scheduling of a 5 MHz bandwidth and a peak data rate of 10 Mbps. If an eRedCap-X terminal with more detailed types / features is defined, it can be assumed that the eRedCap-X terminal supports unicast scheduling of bandwidths other than 20 MHz and 5 MHz.

[0157] This disclosure describes various methods for allowing terminals having different features (or feature combinations) or different reduced capability performance / features to operate in one and the same initial BWP or in separate initial BWPs. By configuring multiple initial BWPs (i.e., an initial BWP and separate initial BWPs) in this manner and associating / assigning terminals with different capabilities to the separate initial BWPs in the frequency domain, it is possible to alleviate the shortage of PUCCH resources for various terminals or perform further unicast PDSCH / PUSCH scheduling according to the features of the terminals.

[0158] Configuration information for the initial uplink / downlink (UL / DL) BWP may be provided by a system information block (e.g., SIB1) that the terminal receives after acquiring a master information block (MIB) in the SS / PBCH block. Furthermore, configuration information for a separate initial UL / DL BWP for a reduced capability terminal (i.e., a RedCap terminal) may be provided to the terminal by an SIB (e.g., SIB1). The separate initial BWP may correspond to an additional initial BWP based on a maximum 20 MHz bandwidth different from the existing initial BWP (which may also be referred to as a basic (or default) initial BWP).

[0159] Information about the downlink basic initial BWP and the separated initial BWP may be included in a DownlinkConfigCommonSIB included in an SIB. For example, the DownlinkConfigCommonSIB may include parameters such as frequencyInfoDL, initialDownlinkBWP, bcch-Config, pcch-Config, pei-Config-r17, and initialDownlinkBWP-RedCap-r17, where initialDownlinkBWP corresponds to the basic initial DL BWP and initialDownlinkBWP-RedCap-r17 corresponds to the separated initial DL BWP.

[0160] Information about the uplink basic initial BWP and the separated initial BWP may be included in an UplinkConfigCommonSIB included in a SIB. For example, the UplinkConfigCommonSIB may include parameters such as frequencyInfoUL, initialUplinkBWP, timeAlignmentTImerCommon, and initialUplinkBWP-RedCap-r17, where initialUplinkBWP corresponds to the basic initial UL BWP and initialUplinkBWP-RedCap-r17 corresponds to the separated initial UL BWP.

[0161] If the SIB includes parameters for the separated initial UL / DL BWP (e.g., initialUplinkBWP-RedCap-r17, initialDownlinkBWP-RedCap-r17), the RedCap UE can apply / switch the active UL / DL BWP to the separated initial UL / DL BWP and use it (e.g., perform a random access procedure on the active UL / DL BWP). If the SIB does not include parameters for the separated initial UL / DL BWP, the RedCap UE can apply / switch the BWP corresponding to the parameters for the basic initial UL / DL BWP (e.g., initialUplinkBWP, initialDownlinkBWP) to the active UL / DL BWP.

[0162] Example 1-1

[0163] This embodiment relates to a method for setting one or more additional separate initial BWPs for an eRedCap terminal. The one or more additional separate initial BWPs are distinguished from the separate initial BWP for the RedCap terminal and may be set by an upper layer (e.g., SIB by an RRC message, etc.).

[0164] [Table 6]

[0165] Various separate initial BWPs corresponding to various terminal types / features may be set, and further separate initial BWPs corresponding to further types / features (e.g., bandwidth, maximum throughput (or peak data rate), etc.) not exemplified in Table 6 may be further defined / set, and different separate initial BWPs may be set independently of each other.

[0166] As an example, separate initial UL / DL BWPs corresponding to every detailed type / feature (eg, bandwidth) of the eRedCap terminal may be independently defined / configured.

[0167] Additionally or alternatively, the number of separate initial UL / DL BWPs may be limited. The upper limit on the number of separate initial UL / DL BWPs may be predefined (in this disclosure, "predefined" means that the terminal and the base station each have the relevant information without any additional signaling) or may be configured by a higher layer (in this disclosure, "pre-configured" means that the relevant information is provided between the terminal and the base station by signaling). This is to reduce the overhead incurred when defining / configuring separate initial BWPs for all combinations of various bandwidths and throughputs.

[0168] Additionally or alternatively, if a separate initial BWP for a particular reduced capability terminal is not configured by an RRC message (e.g., SIB), the terminal may be predefined to use another separate initial BWP or the basic initial BWP.

[0169] Additionally or alternatively, if a separate initial BWP for a particular reduced capability terminal is not configured by an RRC message (e.g., SIB), the terminal may be configured by an RRC message (e.g., SIB) to use another separate initial BWP or the basic initial BWP.

[0170] Additionally or alternatively, if a separate initial BWP for some reduced capability terminals is not configured by an RRC message (e.g., SIB), the terminal may be predefined to use another separate initial BWP or the basic initial BWP. If a separate initial BWP for some other reduced capability terminals is not configured by an RRC message (e.g., SIB), the terminal may be predefined to use another separate initial BWP or the basic initial BWP by an RRC message (e.g., SIB).

[0171] Example 1-2

[0172] This embodiment relates to a method for setting one additional separate initial BWP for an eRedCap terminal. The additional separate initial BWP is distinguished from the separate initial BWP for the RedCap terminal and may be set by an upper layer (for example, an SIB by an RRC message).

[0173] In order to reduce complexity and frequency resource overhead when various separate initial BWPs for various detailed types / features of eRedCap are defined / configured as in Example 1-1, one separate initial BWP commonly used by terminals of various detailed types / features of eRedCap may be defined / configured, thereby configuring a basic initial BWP, a first separate initial BWP (for RedCap), and a second separate initial BWP (for eRedCap) for the terminal.

[0174] As an example, an eRedCap-1 terminal (e.g., an eRedCap terminal supporting 20 MHz bandwidth for unicast) can use the basic initial BWP if the second separated initial BWP is not configured, or can use the first separated initial BWP for RedCap if configured if the second separated initial BWP is not configured.

[0175] Additionally or alternatively, the eRedCap-1 terminal may be predefined or preconfigured (via an RRC message / SIB) to use the second separated initial BWP, or the eRedCap-1 terminal may be predefined or preconfigured (via an RRC message / SIB) to use the first separated initial BWP.

[0176] Additionally or alternatively, an eRedCap-2 terminal (e.g., an eRedCap terminal supporting 5 MHz bandwidth for unicast) may be predefined or preconfigured (by RRC message / SIB) to use the second separated initial BWP, or the eRedCap-2 terminal may be predefined or preconfigured (by RRC message / SIB) to use the first separated initial BWP.

[0177] Additionally or alternatively, the eRedCap-1 terminal can be tied to or operate identically to the RedCap terminal, i.e., the eRedCap-1 terminal can use the first separated initial BWP if it is set, and can use the basic initial BWP if the first separated initial BWP is not set.

[0178] Additionally or alternatively, the eRedCap-1 terminal may operate in conjunction with or identical to the eRedCap-2 terminal, i.e., in the above examples, descriptions of the eRedCap-1 terminal or the eRedCap-2 terminal may be replaced with descriptions of the eRedCap terminal.

[0179] Examples 1-3

[0180] This embodiment relates to a method for setting up a separate initial BWP for a RedCap terminal and an eRedCap terminal. A separate initial BWP is distinguished from the basic initial BWP and may be set by a higher layer (e.g., SIB by an RRC message).

[0181] One separate initial BWP may correspond to an initial BWP that is commonly applied to all RedCap terminals, eRedCap terminals, and (if any) further reduced capability terminals that will be defined in the future. For example, instead of setting independent separate initial BWPs for reduced capability terminals of various types / features in the example of Table 6, one separate initial BWP may be set. This can further reduce the frequency resource overhead caused by setting separate initial BWPs.

[0182] Here, a feature including both RedCap and eRedCap can be referred to as (e)RedCap. For example, if initialDownlinkBWP-RedCap-r17 exists in DownlinkConfigCommonSIB, an (e)RedCap terminal can use the DL BWP (i.e., the separated initial BWP corresponding to initialDownlinkBWP-RedCap-r17) instead of the basic initial DL BWP (i.e., initialDownlinkBWP). For example, if initialDownlinkBWP-RedCap-r17 is absent in DownlinkConfigCommonSIB, an (e)RedCap terminal can use the basic initial DL BWP (i.e., initialDownlinkBWP). For example, if initialUplinkBWP-RedCap-r17 exists in UplinkConfigCommonSIB, an (e)RedCap terminal can use the UL BWP (i.e., the separated initial BWP corresponding to initialUplinkBWP-RedCap-r17) instead of the basic initial UL BWP (i.e., initialUplinkBWP). For example, if initialUplinkBWP-RedCap-r17 is absent from UplinkConfigCommonSIB, (e) the RedCap terminal can use the basic initial DL BWP (ie, initialUplinkBWP).

[0183] Alternatively, one separate initial BWP may be a first separate initial BWP that can be set for a RedCap terminal, a second separate initial BWP that can be set for an eRedCap terminal, or a third separate initial BWP that can be set for a further reduced capability terminal defined in the future, but only one of the first, second, and third separate initial BWPs may be set (i.e., multiple separate BWPs may not be set at the same time). For example, independent separate initial BWPs may be set for reduced capability terminals of various types / features in the example of Table 6, but only one of them may be set. This can further reduce the frequency resource overhead caused by separate initial BWP setting.

[0184] As an example, an eRedCap-1 terminal (e.g., an eRedCap terminal supporting 20 MHz bandwidth for unicast) can operate in conjunction with or identical to a RedCap terminal, i.e., the eRedCap-1 terminal can use one separate initial BWP if one is configured, and can use the basic initial BWP if one is not configured.

[0185] Additionally or alternatively, the eRedCap-1 terminal can operate in conjunction with or identical to the eRedCap-2 terminal, i.e., the eRedCap (e.g., eRedCap-1, eRedCap-2, eRedCap-X, ...) terminal can use one separate initial BWP if it is configured, use one separate initial BWP if it is configured, and use the basic initial BWP if one separate initial BWP is not configured.

[0186] Additionally or alternatively, the basic initial BWP may be predefined to be used if one separate initial BWP is not configured by an RRC message (eg, SIB).

[0187] Additionally or alternatively, when only one separated initial BWP is configurable, a second separated initial BWP for an eRedCap terminal, which is distinct from the first separated initial BWP for an existing RedCap terminal, may be defined as a configurable parameter. For example, initialDownlinkBWP-RedCap-r17 and initialDownlinkBWP-RedCap-r18 (or initialDownlinkBWP-eRedCap-r18) may be defined as configurable parameters in the DownlinkConfigCommonSIB configuration information, and initialUplinkBWP-RedCap-r17 and initialUplinkBWP-RedCap-r18 (or initialUplinkBWP-eRedCap-r18) may be defined as configurable parameters in the UplinkConfigCommonSIB configuration information.

[0188] More specifically, if only one separate initial BWP can be configured for RedCap terminals and eRedCaps (e.g., eRedCap-1, eRedCap-2, eRedCap-X, ...), an additional separate initial BWP for eRedCap terminals may not be necessary. If the first separate initial BWP parameter (e.g., initialUplinkBWP-RedCap-r17 and / or initialDownlinkBWP-RedCap-r17) is used only for RedCap terminals if it is present in the configuration information (e.g., UplinkConfigCommonSIB and / or DownlinkConfigCommonSIB), and if the first separate initial BWP parameter is not present in the configuration information, the basic initial BWP is used. If the first separate initial BWP parameter is defined to be used only for RedCap terminals, eRedCap terminals that are not RedCap terminals may not be able to use the first separate initial BWP parameter. In other words, if only one separate initial BWP is configured in the system, RedCap terminals may use the basic initial BWP, and eRedCap terminals may not be supported to use the first separate initial BWP. Therefore, it is necessary to define a second separated initial BWP for the eRedCap terminal that is distinct from (or does not conflict with) the first separated initial BWP for the RedCap terminal. In this case, the second separated initial BWP for the eRedCap terminal may be set only if the first separated initial BWP for the RedCap terminal is not set.

[0189] Additionally or alternatively, when the basic initial BWP and the first separated initial BWP for a RedCap terminal are configured, the initial BWP for an eRedCap (e.g., eRedCap-1, eRedCap-2, eRedCap-X, ...) may be applied as follows. For example, which of the basic initial BWP and the first separated initial BWP to use for each terminal of type / feature eRedCap-1, eRedCap-2, eRedCap-X, ... may be predefined or configured by an RRC message (e.g., SIB). Alternatively, which of the basic initial BWP and the first separated initial BWP to use for some terminals of type / feature eRedCap-1, eRedCap-2, eRedCap-X, ... may be predefined, and which of the basic initial BWP and the first separated initial BWP to use for terminals of the remaining types / features may be configured by an RRC message (e.g., SIB).

[0190] Additionally or alternatively, when the basic initial BWP and the second separated initial BWP for an eRedCap terminal are configured, the initial BWP for the eRedCap (e.g., eRedCap-1, eRedCap-2, eRedCap-X, ...) may be applied as follows. For example, which of the basic initial BWP and the second separated initial BWP to use for each terminal of type / feature eRedCap-1, eRedCap-2, eRedCap-X, ... may be predefined or configured by an RRC message (e.g., SIB). Alternatively, which of the basic initial BWP and the second separated initial BWP to use for some terminals of type / feature eRedCap-1, eRedCap-2, eRedCap-X, ... may be predefined, and which of the basic initial BWP and the second separated initial BWP to use for terminals of the remaining types / features may be configured by an RRC message (e.g., SIB).

[0191] Examples 1-4

[0192] The eRedCap-2 type / feature (i.e., 5 MHz bandwidth support for unicast) is different from the RedCap type / feature in terms of unicast bandwidth and throughput, and the eRedCap-2 type / feature (i.e., 20 MHz bandwidth support for unicast) is the same as the RedCap type / feature in terms of unicast bandwidth and is different only in terms of throughput. Considering this, an eRedCap-1 terminal may be defined to operate identically to a RedCap terminal.

[0193] In one example, the eRedCap-1 type / feature may be considered the same type / feature as the RedCap type / feature. That is, the eRedCap-1 terminal uses the same separated initial BWP as the RedCap terminal, and can use the basic initial BWP if there is no setting for the separated initial BWP. In this case, even if another separated initial BWP is set for the eRedCap terminal, the eRedCap-1 terminal does not need to use the other separated initial BWP.

[0194] Additionally or alternatively, the eRedCap-1 type / feature may be considered the same type / feature as the eRedCap-2 type / feature. That is, the same initial BWP can be used regardless of the detailed type / feature of the eRedCap. For example, if a second separate initial BWP is configured for the eRedCap device, the eRedCap device can use the second separate initial BWP, and if the second separate initial BWP is not configured, the eRedCap device can use the basic initial BWP. If a first separate initial BWP is configured for the eRedCap device, but a second separate initial BWP is not configured for the eRedCap device, the eRedCap device can use the first separate initial BWP.

[0195] In the above example, the separate initial BWP for the RedCap terminal and / or the separate initial BWP for the eRedCap terminal can be set for each of the UL and DL, whereas the separate initial BWP for the eRedCap terminal may be set / defined only for the UL. In order for the base station to distinguish the type / feature of the terminal early based on the uplink transmission of the terminal during the initial access process, a further separate initial BWP may be defined as being settable only for the UL.

[0196] In one example, a separate initial BWP for an eRedCap terminal may be configured / defined only for the UL, not for the DL. For example, initialUplinkBWP-RedCap-r18 (or initialUplinkBWP-eRedCap-r18) may be defined as a configurable parameter in the RRC configuration information for the uplink (e.g., UplinkConfigCommonSIB), but initialDownlinkBWP-RedCap-r18 (or initialDownlinkBWP-eRedCap-r18) may not be defined / included in the RRC configuration information for the downlink (e.g., DownlinkConfigCommonSIB).

[0197] Additionally or alternatively, when a separate initial BWP dedicated to eRedCap terminals is configured, the early indication method of the eRedCap feature (or a feature combination including the eRedCap feature) using the random access resource (or preamble) set of the first message (Msg1 or MsgA) in the random access procedure of the eRedCap terminal may be defined not to be configured / applied in the cell. This reduces the partitioning of random access resources for each feature / feature combination, thereby reducing complexity. This may be applied to both the eRedCap-1 type / feature (i.e., 20 MHz bandwidth support) and the eRedCap-2 type / feature (i.e., 5 MHz bandwidth support).

[0198] In the above example, when one or more basic initial BWPs and one or more separated initial BWPs are configured, which initial BWP is used for each of the RedCap terminal and eRedCap terminal may be configured by higher layer signaling.

[0199] For example, which of one or more basic initial BWPs and one or more separated initial BWPs will be used for an eRedCap-1 terminal (i.e., 20 MHz bandwidth support) may be predefined or set by an RRC message (e.g., SIB).

[0200] Additionally or alternatively, which of one or more basic initial BWPs and one or more separated initial BWPs is used for an eRedCap-2 terminal (i.e., 5 MHz bandwidth support) may be predefined or set by an RRC message (e.g., SIB).

[0201] Example 2

[0202] This embodiment relates to random access resources for early indication of feature combinations at initial access for various reduced capability terminals.

[0203] Given feature combinations of various terminals in a cell, the network / base station can provide (e.g., signal using SIB) information on one or more feature combinations and information on random access resource sets corresponding to one or more feature combinations to terminals in the cell. Based on this information, the terminal can select a random access resource (or preamble) for a first random access message (Msg1 or MsgA) in an initial access process from among the random access resource sets corresponding to the feature combinations including the features it supports (based on the priority of the features if there are multiple feature combinations), and transmit the selected random access resource to the network / base station. The network / base station that receives the first message of the random access procedure can detect / acquire the feature combination supported by the terminal from the random access resource set to which the preamble selected by the terminal belongs.

[0204] For example, configuration information called FeatureCombination among higher layer (e.g., RRC) information elements may include fields corresponding to features such as msg3-repetition, smallData, nsag, and RedCap, and a FeatureCombination may be configured as a combination of one or more of these. Information regarding a random access resource set (i.e., a set of preamble candidates for the first message of the random access procedure) associated with each FeatureCombination may be included in higher layer configuration information called FeatureCombinationPreambles, for example.

[0205] A plurality of feature combinations (e.g., FeatureCombination) as described above may be configured. For example, assuming one feature combination including a RedCap field and a msg3-Repetition field, a terminal supporting both the RedCap and msg3-Repetition features can perform an early indication for the feature combination by transmitting a first message for the random access procedure using a preamble selected from one random access resource set associated with the feature combination. Alternatively, assuming another feature combination including only the RedCap field, a terminal supporting only the RedCap feature can perform an early indication for the feature combination by transmitting a first message for the random access procedure using a preamble selected from another random access resource set associated with the feature combination.

[0206] Additionally or alternatively, for subsequent uplink messages (Msg3 / UL-SCH / PUSCH or UL-SCH / PUSCH of MsgA) of the random access procedure, the LCID value for the CCCH / UL-SCH of a terminal that supports a specific capability / feature may be defined to be different from the LCID value for the CCCH / UL-SCH of a terminal that does not support the specific capability / feature, thereby allowing the network / base station to be informed of the terminal's type / feature / capability early.

[0207] As mentioned above, when terminals with various features / capabilities, such as non-RedCap terminals, RedCap terminals, and eRedCap terminals, are mixed, if the network / base station cannot detect / acquire terminal features / capabilities early, only minimal / restricted functions commonly applicable to terminals of different types and capabilities are performed until a terminal capability report (which is reported from the terminal to the base station when general PUSCH transmission / reception between the terminal and the network is possible after the random access procedure) is received, or when a specific function is performed, terminals that cannot support the specific function may have difficulty communicating normally with the network. Therefore, a method is required to early instruct the base station on the type / feature / capability supported by a specific terminal before the terminal capability report.

[0208] In this embodiment, an example will be described in which early indication of UE features / capabilities, including RedCap, eRedCap, etc., is based on an uplink message of the random access procedure during the UE's initial access process (e.g., the first message (Msg1) / PRACH / preamble and / or subsequent uplink message (Msg3) / UL-SCH / PUSCH of a four-stage random access type, or the PRACH / preamble and / or UL-SCH / PUSCH of MsgA of a two-stage random access type). This allows the base station to appropriately set / adapt processing time, maximum usable bandwidth, etc. for UEs with various capabilities to suit the capabilities of the UE until the UE reports its capabilities.

[0209] Although an early indication method has been defined for existing RedCap devices, an early indication method has not been defined for eRedCap devices, and an early indication method has not been defined for detailed features of eRedCap devices (e.g., eRedCap-1, eRedCap-2, eRedCap-X, ...). Therefore, it is necessary to define a new method for early indication in the random access procedure for various features / feature combinations, including eRedCap.

[0210] For example, if the above-described early indication scheme (e.g., random access resource set configuration associated with a feature combination and / or LCID definition for UL-SCH / PUSCH of a random access procedure) is modified to separate RedCap and eRedCap (more specifically, eRedCap-1, eRedCap-2, eRedCap-X, ...), the overhead of preamble partitioning increases and LCID values ​​may become insufficient. Therefore, this disclosure describes examples for early indication and scheduling that efficiently support various reduced capability terminals.

[0211] Example 2-1

[0212] This embodiment relates to a method for early indication of terminal features that support 20 MHz bandwidth.

[0213] For example, for each of various reduced capability terminal types / features, a random access first message (PRACH / preamble of Msg1 or MsgA) based scheme for early indication (e.g., distinct random access resource (or preamble) set and / or PRACH resource (e.g., time-frequency resource or PRACH occasion) configuration) and / or a subsequent uplink message (UL-SCH / PUSCH of Msg3 or MsgA) based scheme for random access (e.g., distinct LCIDs are predefined) may be applied. For example, early indication schemes may be defined according to terminal types / features as shown in Table 7 below.

[0214] [Table 7]

[0215] In Table 7, TBD does not mean the same value, but represents any value to be determined in the future. For example, maximum bandwidths other than 20 MHz and 5 MHz may be supported for the eRedCap-X type / feature, and / or throughputs other than 10 Mbps may be supported.

[0216] The eRedCap1-r18, eRedCap2-r18, and eRedCapX-r18 associated with the first message in Table 7 may be defined as fields that may be included (or set to true) in feature combination setting information (e.g., FeatureCombination). FeatureCombination may include one or more of the existing redcap-r17, smallData, nsag, and msg3-Repetitions fields.

[0217] LCID-1, LCID-2, and LCID-X associated with the subsequent uplink message in Table 7 may correspond to new values ​​that are distinct from the existing LCIDs for RedCap terminals. For example, different LCID values ​​may be defined for CCCHs of different sizes for RedCap terminals, and different LCID values ​​may also be defined for CCCHs of different sizes for eRedCap (specifically, eRedCap-1, eRedCap-2, eRedCap-X, ...) terminals.

[0218] For example, for each of various reduced capability terminal types / features, an independent random access resource set / PRACH resource for the first message-based early indication may be configured, and / or an independent LCID for the subsequent uplink message-based early indication may be predefined. If the scheme for the first message-based early indication itself is defined but not configured for the terminal, the network / base station can detect / acquire the reduced capability type / feature of the terminal using the scheme for the subsequent uplink message-based early indication.

[0219] Example 2-2

[0220] This embodiment relates to a method in which an eRedCap terminal shares settings / definitions for early instructions with an existing RedCap terminal.

[0221] In order to reduce complexity when various settings / definitions for early indication for various detail types / features of eRedCap are applied independently as in Example 2-1, in the absence of settings for early indication for various detail types / features of eRedCap, the settings for early indication of the RedCap terminal may be applied to the eRedCap terminal.

[0222] As an example, terminals having various types / features belonging to eRedCap can share the configuration of the random access resource (or preamble) and / or PRACH resource (or time-frequency resource) for the first message (PRACH / preamble of Msg1 or MsgA) for the RedCap terminal. In this case, the network / base station can confirm that the terminal that transmitted the first message on the preamble / PRACH resource is a RedCap terminal or a terminal having various types / features of eRedCap, and the more specific type / feature of the terminal can be distinguished based on the LCID of the subsequent uplink message of the random access procedure. For example, if there is a configuration of the random access resource / PRACH resource for the first message-based early indication for the specific type / feature of eRedCap as in Example 2-1, the terminal having the specific type / feature of eRedCap can use it; otherwise, it can use the configuration of the random access resource / PRACH resource for the first message-based early indication for the RedCap terminal. Alternatively, if the random access resource / PRACH resource itself for the first message-based early indication for the detailed type / feature of eRedCap is not defined, a terminal having the detailed type / feature of eRedCap can use the setting of the random access resource / PRACH resource for the first message-based early indication for the RedCap terminal.

[0223] Additionally or alternatively, a terminal having a first type / feature of eRedCap may share the configuration of the random access resource (or preamble) and / or PRACH resource (or time-frequency resource) for the first message (PRACH / preamble of Msg1 or MsgA) with a terminal having a second type / feature of eRedCap. For example, if the random access resource / PRACH resource for the first message-based early indication for the first type / feature of eRedCap is configured, the terminal having the first type / feature of eRedCap may use it; otherwise, the terminal may use the configuration of the random access resource / PRACH resource for the first message-based early indication for the second type / feature of eRedCap. Alternatively, if the random access resource / PRACH resource for the first message-based early indication for the first type / feature of eRedCap itself is not defined, the terminal having the first type / feature of eRedCap may use the configuration of the random access resource / PRACH resource for the first message-based early indication for the second type / feature of eRedCap. For example, in Table 7, if resources for the first message-based early instruction of eRedCap-1 are set and resources for the first message-based early instruction of eRedCap-2 or eRedCap-X are not set, the eRedCap-2 terminal or eRedCap-X terminal can use resources for the first message-based early instruction for eRedCap-1.

[0224] When a resource for the first message-based early indication associated with a terminal type / feature is not configured / defined, which of the configured / defined resources for the first message-based early indication associated with other types / features to use may be configured or predefined for the terminal by higher layer signaling. For example, when resources for the first message-based early indication are configured / defined for RedCap and eRedCap-1, but resources for the first message-based early indication for eRedCap-2 are not configured / defined, which of the types / features, RedCap and eRedCap-1, to use for the eRedCap-2 terminal may be configured or predefined by the network / base station. Alternatively, when a first resource for a first message-based early indication associated with RedCap and a second resource for a first message-based early indication associated with eRedCap-2 are configured, and no resource for a first message-based early indication for eRedCap-1 is configured / defined, whether the eRedCap-1 terminal uses the first resource or the second resource may be configured or predefined by an RRC message (e.g., SIB).

[0225] Example 2-3

[0226] This embodiment relates to a method of defining the LCID for the subsequent uplink message (e.g., PUSCH / UL-SCH of the third message (Msg3) of the four-stage random access type or the first message (MsgA) of the two-stage random access type) based early indication of random access as a distinct or identical LCID value for the eRedCap terminal and the LCID value for the RedCap terminal (i.e., sharing).

[0227] Since the LCID used in the subsequent uplink message-based early indication of random access is pre-defined rather than set by the network / base station, it is necessary to efficiently define LCID values ​​corresponding to various reduced capability E types / features to prevent a shortage of LCID candidate values ​​limited by the LCID length.

[0228] As an example, one LCID that is commonly applied to eRedCap-1, eRedCap-2, eRedCap-X, etc. may be defined. For example, the LCID may be defined as a different value for each CCCH size, but may not be defined as a different value for each detailed type / feature of the eRedCap. The LCID common to eRedCap terminals of various detailed types / features may or may not be shared (i.e., identical) with the LCID for the RedCap terminal.

[0229] Additionally or alternatively, LCIDs may be predefined for some types / features among eRedCap-1, eRedCap-2, eRedCap-X, etc., and not predefined for the remaining types / features. In this case, a terminal of a specific type / feature of eRedCap for which an LCID is not predefined can use an LCID for the specific type / feature of eRedCap for which an LCID is predefined, or can use an LCID predefined for a RedCap terminal. For example, if the LCID value for a RedCap terminal is predefined to 1000 and the LCID value for an eRedCap-1 terminal is predefined to 2000, an eRedCap-2 terminal may use either 1000 or 2000 as the LCID value in a subsequent uplink random access message. Which of the predefined LCID values ​​to use for other types / features may be configured for the terminal by higher layer signaling or may be predefined.

[0230] Additionally or alternatively, if an eRedCap-2 (e.g., supporting 5 MHz bandwidth for unicast) terminal also supports the SDT (small data transmission) feature, the LCID of the CCCH can be predefined separately for the combination of eRedCap-2 and SDT features (e.g., as an LCID value that corresponds only to the eRedCap-2 feature and that is distinct from the LCID corresponding only to the SDT feature).

[0231] If the configuration / definition of random access resources / PRACH resources for the first message-based early indication of random access is not provided for a specific detailed type / feature of eRedCap, and if the resources for the first message-based early indication for RedCap or for other detailed types / features of eRedCap are not shared, the eRedCap terminal can use the random access resources / PRACH resources configured / defined for non-RedCap terminals. In this case, the early indication for the type / feature of the terminal may be performed only by the LCID of the subsequent uplink message of random access as follows:

[0232] As an example, an eRedCap terminal to which the first message-based early indication cannot be applied can transmit a subsequent uplink message of the random access procedure using a new LCID predefined for the eRedCap. For example, an eRedCap terminal in which a resource for the first message-based early indication is configured / defined can use an LCID for a non-RedCap or an LCID for a RedCap in the subsequent uplink message of the random access. Here, whether the LCID for a non-RedCap or the LCID for a RedCap is to be used may be configured or predefined by higher layer signaling.

[0233] Additionally or alternatively, an eRedCap terminal to which the first message-based early indication cannot be applied may use an LCID for a non-RedCap or an LCID for a RedCap in a subsequent uplink message of random access. Here, whether to use an LCID for a non-RedCap or an LCID for a RedCap may be set by higher layer signaling or may be predefined.

[0234] Examples 2-4

[0235] As shown in Table 7 above, for each of various detailed types / features of eRedCap, resources (e.g., random access resource (preamble) set / PRACH resource) for the first message-based early indication of the random access procedure may be configured and / or LCIDs for the subsequent uplink message-based early indication of the random access procedure may be predefined. For new reduced capability types / features that may be further defined in the future, resources / LCIDs for early indication for some or all of the RedCap / eRedCap types / features defined in Table 7 may be configured / defined to be used / shared. In other words, rather than configuring / defining new resources / LCIDs for independent early indication, early indication for new reduced capability types / features may be supported using any one or a combination of the first message-based early indication resources and subsequent uplink message-based early indication LCIDs according to the present disclosure.

[0236] Additionally or alternatively, a first message-based early indication resource and a subsequent uplink message-based early indication LCID are defined for the RedCap type / feature. Taking this into consideration, resources for the first message-based early indication of the random access procedure may be shared rather than independently defined for each of the RedCap, eRedCap-1, and eRedCap-2 types. Additionally or alternatively, LCIDs for the subsequent uplink message-based early indication of the random access procedure may be shared rather than independently defined for each of the RedCap, eRedCap-1, and eRedCap-2 types. In this case, the base station cannot detect the type / feature of a terminal with reduced capabilities until the terminal capability report is performed, and a solution to compensate for this is required.

[0237] As an example, the eRedCap-1 terminal (i.e., the eRedCap terminal supporting a 20 MHz bandwidth) can share the first message-based early indication resource configured for the RedCap terminal, and a first message-based early indication resource that is distinct from the first message-based early indication resource configured for the RedCap terminal can be configured / defined for the eRedCap-1 terminal (i.e., the eRedCap terminal supporting a 5 MHz bandwidth).

[0238] Additionally or alternatively, the eRedCap-1 terminal (i.e., the eRedCap terminal supporting the 20 MHz bandwidth) may share the subsequent uplink message-based early indication LCID value defined for the RedCap terminal. A subsequent uplink message-based early indication LCID value distinct from the subsequent uplink message-based early indication LCID value defined for the RedCap terminal may be defined for the eRedCap-1 terminal (i.e., the eRedCap terminal supporting the 5 MHz bandwidth). In this case, the eRedCap-2 terminal may use the first message-based early indication resource configured / defined for the RedCap terminal or the first message-based early indication resource configured / defined for the eRedCap-2 terminal for the first message-based early indication. Which of these first message-based early indication resources to use may be configured by a higher layer.

[0239] Additionally or alternatively, the eRedCap-1 terminal may share the subsequent uplink message-based early indication LCID value defined for the eRedCap terminal, i.e., the subsequent uplink message-based early LCID value may be predefined for the eRedCap terminals in common without distinguishing between the eRedCap-1 and eRedCap-2.

[0240] The eRedCap feature and the RedCap feature may be defined as includeable fields in the configuration information of a feature combination (e.g., a FeatureCombination information element) associated with the first message-based early indication resource of the random access procedure. In this case, taking into consideration a case where one terminal does not have all of the RedCap, eRedCap-1, and eRedCap-2 types / features overlapping, the terminal may be predefined so as not to expect the RedCap feature and the eRedCap feature to be simultaneously included in the configuration information of one feature combination (e.g., a FeatureCombination information element). That is, it may be predefined that the RedCap feature and the eRedCap feature are not both included in the configuration information of one feature combination (e.g., a FeatureCombination information element) generated by the base station (i.e., the RedCap and eRedCap fields shall not both be set true). Here, eRedCap may include all types / features such as eRedCap-1, eRedCap-2, eRedCap-X, etc. (i.e., eRedCap-1, eRedCap-2, eRedCap-X type / feature terminals use random access resource sets associated with feature combinations that include the eRedCap feature).

[0241] Additionally or alternatively, when a first message-based early indication resource associated with the RedCap feature and a first message-based early indication resource associated with the eRedCap feature are respectively configured, a terminal having the RedCap feature / capability and a terminal having the eRedCap feature / capability can independently use the first message-based early indication resource. For example, a terminal that supports all features included in a Feature Combination can generally use the first message-based early indication resource associated with the Feature Combination. However, a terminal that does not support both RedCap and eRedCap (i.e., a terminal that supports RedCap or eRedCap) can be defined to be able to use the early indication associated with the Feature Combination. For example, instead of multiple Feature Combinations that separately include RedCap and eRedCap, a single Feature Combination may include RedCap and eRedCap. In this case, the first message-based early indication resources associated with RedCap and eRedCap cannot be distinguished, but the RedCap and eRedCap features can be distinguished by the subsequent uplink message-based early indication LCID value. In other words, for multiple features that are set together in one FeatureCombination, the use of the associated first message-based early instruction resource may be allowed to be applied independently (i.e., the first message-based early instruction resource may be used even if only one of the multiple features is supported), and such allowed multiple features may be limited to RedCap and eRedCap related features.

[0242] Additionally or alternatively, if the eRedCap-1 (i.e., 20 MHz bandwidth support) feature and the eRedCap-2 (i.e., 5 MHz bandwidth support) feature are predefined as features that can be included in a feature combination, the eRedCap-1 and eRedCap-2 fields may be set simultaneously in one FeatureCombination. In this case, the eRedCap-1 terminal and the eRedCap-2 terminal cannot be distinguished using the first message-based early indication resource associated with the FeatureCombination, but the eRedCap-1 and eRedCap-2 features can be distinguished using the subsequent uplink message-based early indication LCID value.

[0243] Alternatively, when the eRedCap-1 (i.e., 20 MHz bandwidth support) feature and the eRedCap-2 (i.e., 5 MHz bandwidth support) feature are predefined as features that can be included in a feature combination, the eRedCap-1 and eRedCap-2 fields may be restricted so as not to be set simultaneously in one FeatureCombination, taking into consideration the low possibility of supporting both the eRedCap-1 and eRedCap-2 features.

[0244] In the above example, the description of the LCID of Msg3 in the four-phase random access procedure may be applied as an example of the LCID for MsgA in the two-phase random access procedure, which may be an example of the LCID for the subsequent uplink message-based early indication of the random access procedure.

[0245] Additionally or alternatively, the first message-based early indication resource for eRedCap may be set only in an initial UL BWP (or a separated initial UL BWP) in which the first message-based early indication resource for RedCap is not set. That is, in an initial UL BWP (or a separated initial UL BWP) in which the first message-based early indication resource for RedCap is not set, the first message-based early indication resource for eRedCap may not be set. Here, eRedCap may be replaced with eRedCap-1 or eRedCap-2, and eRedCap-1 and eRedCap-2 may be collectively referred to.

[0246] In the above example, a random access resource (or preamble) set and a PRACH resource (or PRACH opportunity) are described as examples of the first message-based early indication resource. In this regard, among a plurality of preamble sets and / or a plurality of PRACH opportunities configured in a terminal, which preamble set and / or which PRACH opportunity to use may be predefined or may be configured by RRC signaling (e.g., SIB) depending on the features of the terminal.

[0247] For example, for the eRedCap-1 (i.e., 20 MHz bandwidth support) feature, which preamble set / PRACH opportunity to use may be predefined or may be configured by RRC signaling (e.g., SIB). Additionally or alternatively, for the eRedCap-2 (i.e., 5 MHz bandwidth support) feature, which preamble set / PRACH opportunity to use may be predefined or may be configured by RRC signaling (e.g., SIB). Here, for each preamble set / PRACH opportunity, whether the first message-based early indication and / or the subsequent uplink message-based early indication is predefined for each feature may be configured by RRC signaling (e.g., SIB) or may be predefined.

[0248] According to the various examples of the present disclosure described above, for terminals of various types / features, such as existing RedCap terminals and further introduced eRedCap (or eRedCap-1 and eRedCap-2) terminals, various examples of operation in initial BWP and separated initial BWP can optimize base station load balancing and efficient scheduling, and various examples of early indication of terminal type / features using the first message base and / or subsequent uplink messages of the random access procedure before terminal capability reporting can enable efficient resource utilization and reduce complexity and overhead.

[0249] General devices to which the present disclosure can be applied

[0250] FIG. 9 is a block diagram illustrating a wireless communication device according to an embodiment of the present disclosure.

[0251] Referring to FIG. 9, the first device 100 and the second device 200 can transmit and receive wireless signals using various wireless connection technologies (e.g., LTE, NR).

[0252] The first device 100 includes one or more processors 102 and one or more memories 104, and may further include one or more transceivers 106 and / or one or more antennas 108. The processor 102 may be configured to control the memory 104 and / or the transceiver 106 to implement the descriptions, functions, procedures, suggestions, methods and / or operational flow diagrams disclosed in this disclosure.

[0253] For example, the processor 102 may process information in the memory 104 to generate first information / signal and then transmit a wireless signal including the first information / signal from the transceiver 106. Additionally, the processor 102 may receive a wireless signal including second information / signal from the transceiver 106 and then store information obtained from signal processing of the second information / signal in the memory 104.

[0254] The memory 104 may be coupled to the processor 102 and may store various information related to the operation of the processor 102. For example, the memory 104 may store software code including instructions for performing some or all of the processes controlled by the processor 102 or for implementing the descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed in this disclosure. Here, the processor 102 and the memory 104 may be part of a communications modem / circuit / chip designed to implement a wireless communication technology (e.g., LTE, NR). The transceiver 106 may be coupled to the processor 102 and may transmit and / or receive wireless signals via one or more antennas 108. The transceiver 106 may include a transmitter and / or a receiver. The transceiver 106 may also be referred to as an RF (Radio Frequency) unit. In the present invention, a device may refer to a communications modem / circuit / chip.

[0255] The second device 200 may include one or more processors 202, one or more memories 204, and may further include one or more transceivers 206 and / or one or more antennas 208. The processor 202 may be configured to control the memory 204 and / or the transceiver 206 to implement the descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed in this disclosure. For example, the processor 202 may process information in the memory 204 to generate third information / signal and then transmit a wireless signal including the third information / signal from the transceiver 206. The processor 202 may also receive a wireless signal including fourth information / signal from the transceiver 206 and store information obtained from signal processing of the fourth information / signal in the memory 204. The memory 204 may be coupled to the processor 202 and may store various information related to the operation of the processor 202. For example, the memory 204 may store software code including instructions for performing some or all of the processes controlled by the processor 202 or for implementing the descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed in this disclosure. Here, the processor 202 and the memory 204 may be part of a communications modem / circuit / chip designed to implement a wireless communication technology (e.g., LTE, NR). The transceiver 206 may be coupled to the processor 202 and may transmit and / or receive wireless signals via one or more antennas 208. The transceiver 206 may include a transmitter and / or a receiver. The transceiver 206 may also be referred to as an RF unit. In the present invention, a device may refer to a communications modem / circuit / chip.

[0256] The hardware elements of the devices 100, 200 are described in more detail below. Without limitation, one or more protocol layers may be implemented by one or more processors 102, 202. For example, one or more processors 102, 202 may implement one or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC, and SDAP). The one or more processors 102, 202 may generate one or more protocol data units (PDUs) and / or one or more service data units (SDUs) according to the descriptions, functions, procedures, suggestions, methods, and / or operational flow diagrams disclosed in this disclosure. The one or more processors 102, 202 may generate messages, control information, data, or information according to the descriptions, functions, procedures, suggestions, methods, and / or operational flow diagrams disclosed in this disclosure. The one or more processors 102, 202 can generate signals (e.g., baseband signals) including PDUs, SDUs, messages, control information, data, or information according to the functions, procedures, suggestions, and / or methods disclosed in this disclosure and provide them to the one or more transceivers 106, 206. The one or more processors 102, 202 can receive signals (e.g., baseband signals) from the one or more transceivers 106, 206 and obtain the PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed in this disclosure.

[0257] The one or more processors 102, 202 may be referred to as a controller, microcontroller, microprocessor, or microcomputer. The one or more processors 102, 202 may be implemented using hardware, firmware, software, or a combination thereof. As an example, the one or more processors 102, 202 may include one or more application-specific integrated circuits (ASICs), one or more digital signal processors (DSPs), one or more digital signal processing devices (DSPDs), one or more programmable logic devices (PLDs), or one or more field programmable gate arrays (FPGAs). The descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed in this disclosure may be implemented using firmware or software, and the firmware or software may be implemented to include modules, procedures, functions, etc. Firmware or software configured to execute the descriptions, functions, procedures, suggestions, methods, and / or operational flow diagrams disclosed in this disclosure may be included in one or more processors 102, 202 or stored in one or more memories 104, 204 and executed by one or more processors 102, 202. The descriptions, functions, procedures, suggestions, methods, and / or operational flow diagrams disclosed in this disclosure may be embodied by firmware or software in the form of code, instructions, and / or collections of instructions.

[0258] One or more memories 104, 204 may be coupled to one or more processors 102, 202 and may store various types of data, signals, messages, information, programs, code, instructions, and / or instructions. The one or more memories 104, 204 may be comprised of ROM, RAM, EPROM, flash memory, hard drives, registers, cache memory, computer-readable storage media, and / or combinations thereof. The one or more memories 104, 204 may be located internal and / or external to the one or more processors 102, 202. Additionally, the one or more memories 104, 204 may be coupled to the one or more processors 102, 202 via various techniques, such as wired or wireless connections.

[0259] One or more transceivers 106, 206 may transmit user data, control information, wireless signals / channels, etc., as referred to in the methods and / or operational flowcharts of the present disclosure, to one or more other devices. One or more transceivers 106, 206 may receive user data, control information, wireless signals / channels, etc., as referred to in the descriptions, functions, procedures, suggestions, methods and / or operational flowcharts of the present disclosure, from one or more other devices. For example, one or more transceivers 106, 206 may be coupled to one or more processors 102, 202 and may transmit and receive wireless signals. For example, one or more processors 102, 202 may control one or more transceivers 106, 206 to transmit user data, control information, or wireless signals to one or more other devices. Also, one or more processors 102, 202 may control one or more transceivers 106, 206 to receive user data, control information, or wireless signals from one or more other devices. Furthermore, one or more transceivers 106, 206 may be coupled to one or more antennas 108, 208, and the one or more transceivers 106, 206 may be configured to transmit and receive user data, control information, wireless signals / channels, etc., referred to in the descriptions, functions, procedures, suggestions, methods, and / or operational flowcharts disclosed in this disclosure, via the one or more antennas 108, 208. In this disclosure, the one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). The one or more transceivers 106, 206 may convert the received user data, control information, wireless signals / channels, etc., from RF band signals to baseband signals for processing using one or more processors 102, 202. The one or more transceivers 106, 206 may convert the user data, control information, wireless signals / channels, etc., processed using one or more processors 102, 202, from baseband signals to RF band signals. To that end, one or more of the transceivers 106, 206 may include (analog) oscillators and / or filters.

[0260] The embodiments described above are combinations of the components and features of the present disclosure in a predetermined form. Each component or feature should be considered optional unless otherwise explicitly stated. Each component or feature may be implemented without being combined with other components or features. It is also possible to combine some components and / or features to form embodiments of the present disclosure. The order of operations described in the embodiments of the present disclosure may be changed. Some components or features of one embodiment may be included in another embodiment, or may be replaced with corresponding components or features of another embodiment. It is clear that claims that do not have an explicit reference relationship in the claims may be combined to form embodiments, or may be included as new claims by amendment after filing.

[0261] It is obvious to those skilled in the art that the present disclosure can be embodied in other specific forms without departing from the essential features of the present disclosure. Therefore, the above detailed description should not be interpreted as limiting in any respect, but should be considered as illustrative. The scope of the present disclosure should be determined by reasonable interpretation of the appended claims, and any modifications within the equivalent scope of the present disclosure are included in the scope of the present disclosure.

[0262] The scope of the present disclosure includes software or machine-executable instructions (e.g., operating systems, applications, firmware, programs, etc.) that cause a device or computer to perform operations according to the methods of various embodiments, as well as non-transitory computer-readable media on which such software or instructions are stored and executable on a device or computer. Instructions usable for programming a processing system to perform features described in this disclosure may be stored on or in a storage medium or computer-readable storage medium, and computer program products including such storage media may be used to embody features described in this disclosure. Storage media may include high-speed random access memory such as DRAM, SRAM, DDR RAM, or other random access solid-state memory devices, but may also include non-volatile memory such as one or more magnetic disk storage devices, optical disk storage devices, flash memory devices, or other non-volatile solid-state storage devices. Memory optionally includes one or more storage devices located remotely from the processor. Memory, or alternatively, non-volatile memory devices within memory, comprise non-transitory computer-readable storage media. The features described in this disclosure may be embodied in software and / or firmware stored on any one of a number of machine-readable media and capable of controlling the hardware of a processing system and allowing the processing system to interact with other mechanisms that utilize the results of embodiments of the present disclosure. Such software or firmware may include, but is not limited to, application code, device drivers, operating systems, and execution environments / containers.

[0263] Here, the wireless communication technology implemented in the devices 100 and 200 of the present disclosure may include LTE, NR, 6G, and also Narrowband Internet of Things (NB-IoT) for low-power communication. Here, for example, the NB-IoT technology may be an example of a Low Power Wide Area Network (LPWAN) technology and may be implemented according to standards such as LTE Cat NB1 and / or LTE Cat NB2, and is not limited to the above-mentioned names. Additionally or alternatively, the wireless communication technology implemented in the devices 100 and 200 of the present disclosure may perform communication based on the LTE-M technology. Here, for example, the LTE-M technology may be an example of an LPWAN technology and may be referred to by various names such as enhanced Machine Type Communication (eMTC). For example, LTE-M technology may be implemented by at least one of various standards, such as 1) LTE Cat 0, 2) LTE Cat M1, 3) LTE Cat M2, 4) LTE non-BL (non-Bandwidth Limited), 5) LTE-MTC, 6) LTE Machine Type Communication, and / or 7) LTE M, and is not limited to the above names. Additionally or alternatively, wireless communication technologies implemented in devices 100 and 200 of the present disclosure may include at least one of ZigBee, Bluetooth, and Low Power Wide Area Network (LPWAN), which consider low-power communication, and are not limited to the above names. As an example, ZigBee technology may create personal area networks (PANs) related to small / low-power digital communication based on various standards, such as IEEE 802.15.4, and may be referred to by various names.

[0264] [Industrial Applicability] The method proposed in this disclosure has been described mainly as being applied to 3GPP LTE / LTE-A and 5G systems, but it can also be applied to various other wireless communication systems in addition to 3GPP LTE / LTE-A and 5G systems.

[0265] [Claims at the time of international application] [Claim 1] 1. A method performed by a terminal in a wireless communication system, comprising: receiving information from a network regarding one or more feature combinations and information regarding one or more random access (RA) resource sets associated with the one or more feature combinations; transmitting a first message of a random access procedure to the network based on an RA resource set of the one or more RA resource sets; Based on the first feature combination being associated with the first RA resource set and the second feature combination being associated with the second RA resource set, the first feature combination includes a first reduced capability feature; the second feature combination includes a second reduced capability feature; The method, wherein the first reduced capability feature and the second reduced capability feature are not both included in one feature combination. [Claim 2] The method of claim 1 , wherein the one RA resource set is the first RA set based on the terminal supporting the first reduced capability feature. [Claim 3] The method of claim 1 , wherein the first reduced capability feature is configured in the first RA resource set configured to a four-stage RA type. [Claim 4] based on the terminal supporting the first reduced capability feature; and based on there being no RA resource set associated with the first feature combination in the one or more RA resource sets; The method of claim 1 , wherein the one RA resource set is the second RA set. [Claim 5] 2. The method of claim 1, wherein one or more logical channel identifier (LCID) values ​​for one or more common control channels (CCCHs) associated with the first reduced capability are distinct from one or more LCID values ​​for one or more CCCHs associated with the second reduced capability. [Claim 6] The method of claim 5, wherein the third message of the random access procedure includes a CCCH service data unit (SDU) and is transmitted on an uplink shared channel (UL-SCH). [Claim 7] 2. The method of claim 1, wherein an initial uplink bandwidth part (BWP) is configured to be used by both the first reduced capability terminal and the second reduced capability terminal. [Claim 8] The method of claim 7, wherein one or more of the first message or third message of the random access procedure are transmitted from the terminal to the network on the initial uplink BWP. [Claim 9] The method of claim 1 , wherein an initial downlink BWP is configured for use by both the first reduced capability terminal and the second reduced capability terminal. [Claim 10] The method of claim 9 , wherein one or more of the second message or the fourth message of the random access procedure are transmitted from the network to the terminal on the initial downlink BWP. [Claim 11] The method of claim 1 , wherein information about the one or more feature combinations and information about the one or more RA resource sets associated with the one or more feature combinations is included in a system information block (SIB). [Claim 12] The method of claim 1 , wherein the RA resource set is a set of preambles used in the random access procedure. [Claim 13] The terminal having the first reduced capability: a terminal that supports reduced bandwidth, or The method of claim 1, wherein the terminal does not support reduced bandwidth. [Claim 14] The maximum bandwidth for a terminal that does not support the reduced bandwidth is 20 MHz; The method of claim 13 , wherein the reduced bandwidth is less than 20 MHz. [Claim 15] In the information about the one or more feature combinations, the first reduced capability feature corresponds to an eRedCap field; The method of claim 1 , wherein the second reduced capability feature corresponds to a RedCap field. [Claim 16] A terminal in a wireless communication system, one or more transceivers; one or more processors coupled to the one or more transceivers; The one or more processors: receiving information about one or more feature combinations and one or more random access (RA) resource sets associated with the one or more feature combinations from a network via the one or more transceivers; and configured to transmit a first message of a random access procedure to the network via the one or more transceivers based on an RA resource set of the one or more RA resource sets; Based on the first feature combination being associated with the first RA resource set and the second feature combination being associated with the second RA resource set, the first feature combination includes a first reduced capability feature; the second feature combination includes a second reduced capability feature; A terminal, wherein the first reduced capability feature and the second reduced capability feature are not both included in one feature combination. [Claim 17] 1. A method performed by a base station in a wireless communication system, comprising: transmitting information about one or more feature combinations and information about one or more random access (RA) resource sets associated with the one or more feature combinations to one or more terminals; receiving, from a terminal, a first message of a random access procedure transmitted based on one RA resource set among the one or more RA resource sets; Based on the first feature combination being associated with the first RA resource set and the second feature combination being associated with the second RA resource set, the first feature combination includes a first reduced capability feature; the second feature combination includes a second reduced capability feature; The method, wherein the first reduced capability feature and the second reduced capability feature are not both included in one feature combination. [Claim 18] A base station in a wireless communication system, comprising: one or more transceivers; one or more processors coupled to the one or more transceivers; The one or more processors: transmitting information about one or more feature combinations and information about one or more random access (RA) resource sets associated with the one or more feature combinations to one or more terminals via the one or more transceivers; and configured to receive, from a terminal via the one or more transceivers, a first message of a random access procedure transmitted based on one RA resource set of the one or more RA resource sets; Based on the first feature combination being associated with the first RA resource set and the second feature combination being associated with the second RA resource set, the first feature combination includes a first reduced capability feature; the second feature combination includes a second reduced capability feature; A base station, wherein the first reduced capability feature and the second reduced capability feature are not both included in one feature combination. [Claim 19] 1. A processing apparatus configured to control a device in a wireless communication system, comprising: one or more processors; and one or more computer memories operably coupled to the one or more processors and storing instructions for performing the method of any one of claims 1 to 15 when executed by the one or more processors. [Claim 20] one or more non-transitory computer-readable media storing one or more instructions, A computer-readable medium, wherein the one or more instructions are executed by one or more processors and control devices in a wireless communication system to perform the method of any one of claims 1 to 15.

Claims

1. 1. A method performed by a terminal in a wireless communication system, comprising: receiving information from a network regarding one or more feature combinations and information regarding one or more random access (RA) resource sets associated with the one or more feature combinations; transmitting a first message of a random access procedure to the network based on an RA resource set of the one or more RA resource sets; Based on the first feature combination being associated with the first RA resource set and the second feature combination being associated with the second RA resource set, the first feature combination includes a first reduced capability feature; the second feature combination includes a second reduced capability feature; The method, wherein the first reduced capability feature and the second reduced capability feature are not both included in one feature combination.

2. The method of claim 1 , wherein the one RA resource set is the first RA set based on the terminal supporting the first reduced capability feature.

3. The method of claim 1 , wherein the first reduced capability feature is configured in the first RA resource set configured to a four-stage RA type.

4. based on the terminal supporting the first reduced capability feature; and based on there being no RA resource set associated with the first feature combination in the one or more RA resource sets; The method of claim 1 , wherein the one RA resource set is the second RA set.

5. 2. The method of claim 1, wherein one or more logical channel identifier (LCID) values ​​for one or more common control channels (CCCHs) associated with the first reduced capability are distinct from one or more LCID values ​​for one or more CCCHs associated with the second reduced capability.

6. The method of claim 5, wherein the third message of the random access procedure includes a CCCH service data unit (SDU) and is transmitted on an uplink shared channel (UL-SCH).

7. 2. The method of claim 1, wherein an initial uplink bandwidth part (BWP) is configured to be used by both the first reduced capability terminal and the second reduced capability terminal.

8. The method of claim 7 , wherein one or more of the first message or third message of the random access procedure is transmitted from the terminal to the network on the initial uplink BWP.

9. The method of claim 1 , wherein an initial downlink BWP is configured to be used by both the first reduced capability terminal and the second reduced capability terminal.

10. The method of claim 9 , wherein one or more of the second message or the fourth message of the random access procedure are transmitted from the network to the terminal on the initial downlink BWP.

11. The method of claim 1 , wherein information about the one or more feature combinations and the one or more RA resource sets associated with the one or more feature combinations is included in a system information block (SIB).

12. The method of claim 1 , wherein the RA resource set is a set of preambles used in the random access procedure.

13. The terminal having the first reduced capability: a terminal that supports reduced bandwidth, or The method of claim 1, wherein the terminal does not support reduced bandwidth.

14. The maximum bandwidth for a terminal that does not support the reduced bandwidth is 20 MHz; The method of claim 13 , wherein the reduced bandwidth is less than 20 MHz.

15. In the information about the one or more feature combinations, the first reduced capability feature corresponds to an eRedCap field; The method of claim 1 , wherein the second reduced capability feature corresponds to a RedCap field.

16. A terminal in a wireless communication system, one or more transceivers; one or more processors coupled to the one or more transceivers; The one or more processors: receiving information about one or more feature combinations and one or more random access (RA) resource sets associated with the one or more feature combinations from a network via the one or more transceivers; and configured to transmit a first message of a random access procedure to the network via the one or more transceivers based on an RA resource set of the one or more RA resource sets; Based on the first feature combination being associated with the first RA resource set and the second feature combination being associated with the second RA resource set, the first feature combination includes a first reduced capability feature; the second feature combination includes a second reduced capability feature; A terminal, wherein the first reduced capability feature and the second reduced capability feature are not both included in one feature combination.

17. 1. A method performed by a base station in a wireless communication system, comprising: transmitting information about one or more feature combinations and information about one or more random access (RA) resource sets associated with the one or more feature combinations to one or more terminals; receiving, from a terminal, a first message of a random access procedure transmitted based on one RA resource set among the one or more RA resource sets; Based on the first feature combination being associated with the first RA resource set and the second feature combination being associated with the second RA resource set, the first feature combination includes a first reduced capability feature; the second feature combination includes a second reduced capability feature; The method, wherein the first reduced capability feature and the second reduced capability feature are not both included in one feature combination.

18. A base station in a wireless communication system, comprising: one or more transceivers; one or more processors coupled to the one or more transceivers; The one or more processors: transmitting information regarding one or more feature combinations and information regarding one or more random access (RA) resource sets associated with the one or more feature combinations to one or more terminals via the one or more transceivers; and configured to receive, from a terminal via the one or more transceivers, a first message of a random access procedure transmitted based on one RA resource set of the one or more RA resource sets; Based on the first feature combination being associated with the first RA resource set and the second feature combination being associated with the second RA resource set, the first feature combination includes a first reduced capability feature; the second feature combination includes a second reduced capability feature; A base station, wherein the first reduced capability feature and the second reduced capability feature are not both included in one feature combination.

19. 1. A processing apparatus configured to control a device in a wireless communication system, comprising: one or more processors; and one or more computer memories operably coupled to the one or more processors and storing instructions for performing the method of any one of claims 1 to 15 when executed by the one or more processors.

20. one or more non-transitory computer-readable media storing one or more instructions, A computer readable medium, wherein the one or more instructions are executed by one or more processors and control devices in a wireless communication system to perform the method of any one of claims 1 to 15.

Images