Signal transmission / reception method for wireless communication and apparatus therefor

Abstract

A terminal according to an embodiment may: receive downlink control information (DCI) through a physical downlink control channel (PDCCH); determining a downlink resource allocated to the terminal based on a frequency domain resource allocation (FDRA) field included in the DCI; and receiving a physical downlink shared channel (PDSCH) on the downlink resource, in which the terminal may determine the downlink resource allocated through the FDRA field based on a second bandwidth rather than the first bandwidth, based on the first bandwidth supported by the terminal for the PDCCH being different from the second bandwidth supported by the terminal for the PDSCH.

Description

Technical Field

[0001] The present disclosure relates to wireless communication, and more particularly, to a method for transmitting or receiving an uplink / downlink signal in a wireless communication system and an apparatus thereof. Background Art

[0002] In general, wireless communication systems are developing to cover a wide range in various ways to provide communication services such as audio communication services, data communication services, etc. Wireless communication is a multiple access system that can support communication with multiple users by sharing available system resources (e.g., bandwidth, transmission power, etc.). For example, the multiple access system can be any of a code division multiple access (CDMA) system, a frequency division multiple access (FDMA) system, a time division multiple access (TDMA) system, an orthogonal frequency division multiple access (OFDMA) system, and a single carrier frequency division multiple access (SC-FDMA) system. Summary of the invention

[0003] Technical issues

[0004] An object of the present disclosure is to provide a method of transmitting and receiving signals more accurately and efficiently.

[0005] The objects of the present disclosure are not limited to what has been specifically described above, and other objects that can be achieved by the present disclosure will be more clearly understood from the following detailed description.

[0006] Technical Solution

[0007] According to one aspect, a method for receiving a signal by a user equipment (UE) in a wireless communication system includes: receiving downlink control information (DCI) through a physical downlink control channel (PDCCH); determining downlink resources allocated to the UE based on a frequency domain resource allocation (FDRA) field included in the DCI; and receiving a physical downlink shared channel (PDSCH) in the downlink resources, wherein, based on a first bandwidth supported by the UE for the PDCCH being different from a second bandwidth supported by the UE for the PDSCH, the UE determines the downlink resources allocated through the FDRA field based on the second bandwidth instead of the first bandwidth.

[0008] The second bandwidth may be smaller than the first bandwidth.

[0009] The first bandwidth may be equal to or greater than 5 MHz, and the second bandwidth may be equal to or less than 5 MHz.

[0010] The frequency region associated with the second bandwidth may belong to a first bandwidth part (BWP), and the first BWP may be shared with other UEs supporting PDSCH reception of a bandwidth larger than the second bandwidth.

[0011] The frequency domain associated with the second bandwidth may be one of a plurality of sub-BWPs included in the first BWP.

[0012] The DCI may include information for configuring one of a plurality of sub-BWPs included in the first BWP as a frequency domain associated with the second bandwidth.

[0013] The UE determines downlink resources allocated in the frequency domain associated with the second bandwidth through the FDRA field.

[0014] A total number of resource block groups (RBGs) associated with the PDSCH and physical resource blocks (PRBs) may be determined based on the second bandwidth.

[0015] According to another aspect, there may be provided a processor-readable recording medium having recorded thereon a program for executing the above-mentioned signal receiving method.

[0016] According to another aspect, a user equipment (UE) for performing the above-mentioned signal receiving method may be provided.

[0017] According to another aspect, an apparatus for controlling a user equipment (UE) to perform the above signal receiving method may be provided.

[0018] According to another aspect, a method for sending a signal by a base station (BS) in a wireless communication system includes: sending downlink control information (DCI) to a user equipment (UE) through a physical downlink control channel (PDCCH); and sending a physical downlink shared channel (PDSCH) in the downlink resources allocated to the UE based on a frequency domain resource allocation (FDRA) field included in the DCI, wherein, based on the fact that a first bandwidth of the PDCCH supported by the UE is different from a second bandwidth of the PDSCH supported by the UE, the downlink resources allocated through the FDRA field are determined based on the second bandwidth rather than the first bandwidth.

[0019] According to another aspect, a base station (BS) for performing the above-mentioned signal transmission method may be provided.

[0020] Beneficial Effects

[0021] According to the embodiments of the present disclosure, signal transmission and reception can be performed more accurately and efficiently in a wireless communication system.

[0022] The effects of the present disclosure are not limited to the contents specifically described above, and other effects that can be achieved by the present disclosure will be more clearly understood from the following detailed description. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] Figure 1Illustrated are physical channels used in a 3rd Generation Partnership Project (3GPP) system as an exemplary wireless communication system, and a general signal transmission method using the physical channels.

[0024] Figure 2 The radio frame structure is shown.

[0025] Figure 3 A resource grid of time slots is illustrated.

[0026] Figure 4 The figure shows the random access process.

[0027] Figure 5 An example of physical channel mapping is shown.

[0028] Figure 6 The flow of a method of transmitting and receiving a signal according to an embodiment is shown.

[0029] Figure 7 An example of a method of allocating N PDSCH resources according to an embodiment is shown.

[0030] Figure 8 An example of allocation of PDSCH resources within 20 MHz according to an embodiment is shown.

[0031] Fig. 9 An example of allocation of PDSCH resources outside 20 MHz according to an embodiment is shown.

[0032] Fig.10 An example of a method of allocating PDSCH resources according to an embodiment is shown.

[0033] Fig.11 is a diagram for explaining the configuration of the size of RBG depending on the BWP size.

[0034] Fig.12 is a diagram for explaining transmission and reception of a PDSCH according to an embodiment.

[0035] Fig.13 and Fig.14 A communication system 1 and a wireless device applied to the present disclosure are illustrated.

[0036] Fig.15 A discontinuous reception (DRX) operation suitable for use with the present disclosure is illustrated. DETAILED DESCRIPTION

[0037] Embodiments of the present disclosure are applicable to various wireless access technologies such as code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), and single carrier frequency division multiple access (SC-FDMA). CDMA can be implemented as a radio technology such as Universal Terrestrial Radio Access (UTRA) or CDMA2000. TDMA can be implemented as a radio technology such as Global System for Mobile Communications (GSM) / General Packet Radio Service (GPRS) / Enhanced Data Rates for GSM Evolution (EDGE). OFDMA can be implemented as a radio technology such as Institute of Electrical and Electronics Engineers (IEEE) 802.11 (Wireless Fidelity (Wi-Fi)), IEEE 802.16 (Worldwide Interoperability for Microwave Access (WiMAX)), IEEE 802.20, and Evolved UTRA (E-UTRA). UTRA is part of Universal Mobile Telecommunications System (UMTS). 3rd Generation Partnership Project (3GPP) Long Term Evolution (LTE) is a part of Evolved UMTS (E-UMTS) using E-UTRA, and LTE-Advanced (A) 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.

[0038] As more and more communication devices require greater communication capacity, enhanced mobile broadband communications relative to traditional radio access technologies (RATs) are needed. In addition, large-scale machine-type communications (MTC), which can provide various services anytime and anywhere by connecting multiple devices and objects, is another important issue to be considered for next-generation communications. Discussions are also underway to design communication systems that take into account services / UEs that are sensitive to reliability and latency. Therefore, discussions are underway to introduce new radio access technologies that take into account enhanced mobile broadband communications (eMBB), massive MTC, and ultra-reliable low-latency communications (URLLC). In this disclosure, for simplicity, this technology will be referred to as NR (new radio or new RAT).

[0039] For the sake of clarity, 3GPP NR is mainly described, but the technical ideas of the present disclosure are not limited to this. LTE refers to the technology after 3GPP TS 36.xxx version 8. Specifically, LTE technology after 3GPP TS 36.xxx version 10 is called LTE-A, and LTE technology after 3GPP TS 36.xxx version 13 is called LTE-A pro. 3GPP NR refers to technology after TS 38.xxx version 15. LTE / NR can be referred to as a 3GPP system. In this document, "xxx" represents the detailed number of the specification. LTE / NR can be collectively referred to as a 3GPP system.

[0040] Details of the background, terms, abbreviations, etc. used herein can be found in documents published prior to this disclosure. For example, this disclosure may be supported by the following documents:

[0041] 3GPP NR

[0042] -3GPP TS38.211: Physical channels and modulation

[0043] -3GPP TS38.212: Multiplexing and channel coding

[0044] -3GPP TS38.213: Physical layer procedures for control

[0045] -3GPP TS38.214: Physical layer procedures for data

[0046] -3GPP TS38.215: Physical layer measurements

[0047] -3GPP TS38.300: NR and NG-RAN general description

[0048] -3GPP TS38.304: User Equipment (UE) procedures in idle mode and RRC inactive state

[0049] -3GPP TS38.321: Medium Access Control (MAC) protocol

[0050] -3GPP TS38.322: Radio Link Control (RLC) protocol

[0051] -3GPP TS38.323: Packet Data Convergence Protocol (PDCP)

[0052] -3GPP TS38.331: Radio Resource Control (RRC) protocol

[0053] -3GPP TS37.324: Service Data Adaptation Protocol (SDAP)

[0054] -3GPP TS37.340: Multi-connectivity; general description

[0055] -3GPP TS23.287: Application layer supporting V2X services; functional architecture and information flow

[0056] -3GPP TS23.501: System architecture of 5G system

[0057] -3GPP TS23.502: 5G system procedures

[0058] -3GPP TS23.503: Policy and charging control framework for 5G systems; Stage 2

[0059] -3GPP TS24.501: Non-Access Stratum (NAS) Protocol for 5G System (5GS); Stage 3

[0060] -3GPP TS24.502: Access to the 3GPP 5G Core Network (5GCN) via non-3GPP access networks

[0061] -3GPP TS24.526: User Equipment (UE) Strategy for 5G System (5GS); Stage 3

[0062] Technical terms used in this document

[0063] -UE: User Equipment

[0064] -SSB: Synchronization Signal Block

[0065] -MIB: Master Information Block

[0066] -RMSI: Remaining Minimum System Information

[0067] - FR1: Frequency Range 1. Concerning the frequency range below 6 GHz (e.g., 450 MHz to 6000 MHz)

[0068] -FR2: Frequency Range 2. This involves the millimeter wave (mmWave) region above 24 GHz (e.g., 24250 MHz to 52600 MHz)

[0069] -BW: Bandwidth

[0070] -BWP: Bandwidth Part

[0071] -RNTI: Radio Network Temporary Identifier

[0072] -CRC: Cyclic Redundancy Check

[0073] -SIB: System Information Block

[0074] -SIB1: SIB1 of NR device = RMSI (Remaining Minimum System Information). Broadcasts information necessary for NR UE to access the cell

[0075] - CORESET (Control Resource Set): Time / frequency resources where the NR UE attempts to decode PDCCH candidates

[0076] -CORESET#0: CORESET of Type0-PDCCH CSS set for NR devices (based on MIB configuration)

[0077] -Type0-PDCCH CSS set: Search space set where the NR UE monitors a set of PDCCH candidates for DCI format with CRC scrambled by SI-RNTI

[0078] -MO: PDCCH monitoring opportunity for Type0-PDCCH CSS set

[0079] -SIB1-R: (Additional) SIB1 for NR devices with reduced capabilities. SIB1-R can be generated as a TB separate from SIB1 and sent over a separate PDSCH

[0080] -CORESET#0-R: CORESET#0 for NR devices with reduced capabilities

[0081] -Type0-PDCCH-R CSS set: Search space set where a redcap UE monitors a set of PDCCH candidates for DCI format with CRC scrambled by SI-RNTI

[0082] -MO-R: PDCCH monitoring opportunity for Type0-PDCCH CSS set

[0083] -Cell Definition SSB (CD-SSB): SSB including RMSI scheduling information between NR SSBs

[0084] - Non-cell defining SSB (non-CD-SSB): refers to SSBs placed in the NR synchronization grid but does not include the RMSI scheduling information of the cell being measured. However, non-CD-SSBs may contain information pointing to the location of the cell defining SSB

[0085] -SCS: Subcarrier Spacing

[0086] -SI-RNTI: System Information Radio Network Temporary Identifier

[0087] - Camped On: "Camped On" is a UE state where the UE stays on a cell and is ready to initiate potential dedicated services or receive ongoing broadcast services

[0088] -TB: Transport Block

[0089] -RSA (Redcap Standalone): Units that only support Redcap devices or services

[0090] -SIB1(-R)-PDSCH: SIB1(-R) for sending PDSCH

[0091] -SIB1(-R)-DCI: SIB1(-R)-PDSCH scheduling DCI. DCI format with CRC scrambled by SI-RNTI

[0092] -SIB1(-R)-PDCCH: SIB1(-R)-DCI for sending PDCCH

[0093] -FDRA: Frequency Domain Resource Allocation

[0094] -TDRA: Time Domain Resource Allocation

[0095] -RA: Random Access

[0096] -MSGA: Preamble and payload transmission for 2-step RA type random access procedure

[0097] -MSGB: Response to MSGA in the 2-step random access procedure. MSGB may include a response for contention resolution, a backoff indication, and a backoff indication.

[0098] -RO-N: RO (RACH timing) for 4-step RACH and 2-step RACH (if configured) for normal UEs

[0099] -RO-N1, RO-N2: If a separate RO is configured for 2-step RACH of normal UE, the RO is classified as RO-N1 (4 steps), RO-N2 (2 steps)

[0100] -RO-R: RO (RACH timing) for 4-step RACH and 2-step RACH (if configured) for redcap UEs, set separately from RO-N

[0101] -RO-R1, RO-R2: If a separate RO is configured for 2-step RACH of redcap UE, the RO is classified into RO-R1 (4 steps) and RO-R2 (2 steps)

[0102] -PG-R: MsgA preamble group for redcap UE

[0103] -RAR: Random Access Response

[0104] -RAR window: time window for monitoring RA response

[0105] -FH: Frequency Hopping

[0106] -iBWP: Initial BWP

[0107] -iBWP-DL(-UL): Initial DL(UL) BWP

[0108] -iBWP-DL(-UL)-R: (Individual) Initial DL(UL) BWP for RedCap

[0109] -CS: Circular shift

[0110] -NB: Narrow Band

[0111] In the present disclosure, the term "set / setting" may be replaced with "configure / configuration", and the two may be used interchangeably. In addition, conditional expressions (e.g., "if", "in this case", or "when...") may be replaced with "based on" or "under the situation / state of...". In addition, the operation or software / hardware (SW / HW) configuration of the user equipment (UE) / base station (BS) may be derived / understood based on the satisfaction of the corresponding condition. When the process on the receiving (or transmitting) side can be derived / understood from the process on the transmitting (or receiving) side in the signal transmission / reception between the wireless communication device (e.g., BS and UE), its description may be omitted. For example, the signal determination / generation / encoding / transmission on the transmitting side may be understood as the signal monitoring reception / decoding / determination on the receiving side. In addition, when it is said that the UE performs (or does not perform) a specific operation, this may also be interpreted as the BS expecting / assuming (or not expecting / assuming) that the UE performs a specific operation. When it is said that the BS performs (or does not perform) a specific operation, this may also be interpreted as the UE expecting / assuming (or not expecting / assuming) that the BS performs a specific operation. In the following description, for the convenience of description, chapters, embodiments, examples, options, methods, schemes, proposals, etc. are distinguished from each other and marked with indexes, which does not mean that each of them must constitute an independent disclosure or each of them can only be implemented separately. Unless explicitly contradicted, it can be concluded / understood that at least some of the chapters, embodiments, examples, options, methods, schemes, proposals, etc. can be implemented in combination or can be omitted.

[0112] In a wireless communication system, a user equipment (UE) receives information from a base station (BS) through a downlink (DL) and transmits information to the BS through an uplink (UL). The information transmitted and received by the BS and the UE includes data and various control information, and includes various physical channels according to the type / purpose of the information transmitted and received by the UE and the BS.

[0113] Figure 1 Illustration of physical channels used in a 3GPP NR system and a general signal transmission method using the same.

[0114] When the UE is powered on again from a power-off state or enters a new cell, in step S101, the UE performs an initial cell search process (e.g., establishes synchronization with the BS). To this end, the UE receives a synchronization signal block (SSB) from the BS. The SSB includes a primary synchronization signal (PSS), a secondary synchronization signal (SSS), and a physical broadcast channel (PBCH). The UE establishes synchronization with the BS based on the PSS / SSS and obtains information such as a cell identity (ID). The UE can obtain broadcast information in the cell based on the PBCH. The UE can receive a DL reference signal (RS) during the initial cell search process to monitor the DL channel status.

[0115] The SSB consists of four consecutive OFDM symbols, each of which carries PSS, PBCH, SSS / PBCH or PBCH. Each of the PSS and SSS includes one OFDM symbol multiplied by 127 subcarriers, and the PBCH includes three OFDM symbols multiplied by 576 subcarriers. The PBCH is encoded / decoded based on the polarization code and modulated / demodulated according to quadrature phase shift keying (QPSK). The PBCH in the OFDM symbol consists of data resource elements (REs) to which the complex modulation values ​​of the PBCH are mapped and demodulation reference signal (DMRS) REs to which the DMRS for the PBCH is mapped. Three DMRS REs are configured for each RB in the OFDM symbol, and three data REs are configured between the DMRS REs.

[0116] PSS can be used in detecting a cell ID within a cell ID group, and SSS can be used in detecting a cell ID group. PBCH can be used in detecting an SSB (time) index and a half frame. There are 336 cell ID groups, and each cell ID group includes three cell IDs. Therefore, there are a total of 1008 cell IDs.

[0117] The SSB is sent periodically with an SSB periodicity. The default SSB periodicity assumed by the UE in the initial cell search is defined as 20ms. After cell access, the SSB periodicity can be set by the network (e.g., BS) to one of {5ms, 10ms, 20ms, 40ms, 80ms, and 160ms}. An SSB burst set can be configured at the beginning of the SSB periodicity. The SSB burst set can be set to a time window of 5ms (i.e., half a frame), and the SSB can be repeatedly sent up to L times within the SS burst set. The maximum number of SSB transmissions L can be given as follows depending on the carrier band. One time slot includes up to two SSBs.

[0118] - For frequency range up to 3 GHz, L = 4

[0119] - For the frequency range from 3 GHz to 6 GHz, L = 8

[0120] - For the frequency range from 6 GHz to 52.6 GHz, L = 64

[0121] The time domain positions of the candidate SSBs in the SS burst set may be defined depending on the subcarrier spacing. The time domain positions of the candidate SSBs are indexed in time order from (SSB index) 0 to L-1 within the SSB burst set (ie, half-frame).

[0122] Multiple SSBs may be transmitted within the frequency span of a carrier. Each SSB may not need to have a unique physical layer cell identifier, but different SSBs may have different physical layer cell identifiers.

[0123] The UE can acquire DL synchronization by detecting the SSB. The UE can identify the structure of the SSB burst set based on the detected SSB (time) index, and thus the UE can detect the symbol / time slot / half-frame boundary. The frame / half-frame number to which the detected SSB belongs can be identified based on the system frame number (SFN) information and the half-frame indication information.

[0124] Specifically, the UE can obtain the 10-bit SFN of the frame to which the PBCH belongs from the PBCH. Then, the UE can obtain 1-bit half-frame indication information. For example, when the UE detects a PBCH in which the half-frame indication bit is set to 0, the UE can determine that the SSB to which the PBCH belongs is included in the first half frame of the frame. When the UE detects a PBCH in which the half-frame indication bit is set to 1, the UE can determine that the SSB to which the PBCH belongs is included in the second half frame of the frame. Finally, the UE can obtain the SSB index of the SSB to which the PBCH belongs based on the PBCH payload and DMRS sequence carried by the PBCH.

[0125] After the initial cell search, the UE may acquire more specific system information by receiving a physical downlink control channel (PDCCH) and receiving a physical downlink shared channel (PDSCH) based on information of the PDCCH in step S102.

[0126] System information (SI) is divided into a master information block (MIB) and a plurality of system information blocks (SIBs). SI other than the MIB may be referred to as remaining minimum system information (RMSI). Details thereof will be described below.

[0127] -MIB includes information / parameters (SystemInformationBlock1) for monitoring the PDCCH that schedules the PDSCH carrying SIB1, and the MIB is sent by the BS on the PBCH of the SSB. For example, the UE can check whether there is a CORESET for the Type0-PDCCH common search space based on the MIB. The Type0-PDCCH common search space is a PDCCH search space that is used to send a PDCCH that schedules an SI message. If a Type0-PDCCH common search space exists, the UE can determine (1) multiple consecutive RBs and one or more consecutive symbols included in the CORESET, and (ii) the PDCCH timing (e.g., the time domain position for PDCCH reception) based on the information in the MIB (e.g., pdcch-ConfigSIB1). If the Type0-PDCCH common search space does not exist, pdcch-ConfigSIB1 provides information about the frequency position where the SSB / SIB1 exists and information about the frequency range where the SSB / SIB1 does not exist.

[0128] -SIB1 includes information about the availability and scheduling (e.g., transmission periodicity, SI window size, etc.) of the remaining SIBs (hereinafter referred to as SIBx, where x is an integer greater than or equal to 2). For example, SIB1 may indicate whether SIBx is broadcast periodically or provided on demand at the request of the UE. When SIBx is provided on demand, SIB1 may include information necessary for the UE to send an SI request. SIB1 is transmitted on the PDSCH, and the PDCCH that schedules SIB1 is transmitted in the Type0-PDCCH common search space. That is, SIB1 is transmitted on the PDSCH indicated by the PDCCH.

[0129] - SIBx is included in the SI message and transmitted on the PDSCH. Each SI message is transmitted within a time window (ie, SI window) that occurs periodically.

[0130] In steps S103 to S106, the UE may perform a random access procedure (e.g., a 4-step RA procedure) to access the BS. For random access, the UE may send a preamble to the BS on a physical random access channel (PRACH) (S103), and receive a response message to the preamble on a PDCCH and a PDSCH corresponding to the PDCCH (S104). In the case of contention-based random access, the UE may perform a contention resolution procedure by further sending a PRACH (S105) and receiving a PDCCH and a PDSCH corresponding to the PDCCH (S106).

[0131] Hereinafter, the 2-step random access procedure will be briefly described. In the 2-step random access procedure, S103 / S105 (wherein the UE performs transmission) (message A) can be performed in one step, and S104 / S106 (wherein the BS performs transmission) (message B) can be performed in one step. Message A (MsgA) may include a preamble and a payload (PUSCH payload), and the preamble and the payload may be multiplexed based on time division multiplexing (TDM). In response to MsgA, message B (MsgB) may be sent for contention resolution, (one or more) backoff indications, and / or backoff indications. The 2-step random access procedure may be subdivided into a contention-based random access (CBRA) procedure and a contention-free random access (CFRA) procedure. In the CFRA procedure, the BS may provide the UE with information about the preamble that the UE needs to send in MsgA and information about PUSCH allocation before the UE sends MsgA.

[0132] After the foregoing process, the UE may receive PDCCH / PDSCH (S107) and send a physical uplink shared channel (PUSCH) / physical uplink control channel (PUCCH) (S108) as a general downlink / uplink signal transmission process. The control information sent from the UE to the BS is called uplink control information (UCI). UCI includes hybrid automatic repeat and request confirmation / negative determination (HARQ-ACK / NACK), scheduling request (SR), channel state information (CSI), etc. CSI includes channel quality indicator (CQI), precoding matrix indicator (PMI), rank indicator (RI), etc. Although UCI is usually sent on PUCCH, UCI may be sent on PUSCH when control information and business data need to be sent simultaneously. In addition, UCI may be sent aperiodically via PUSCH according to a request / command of the network.

[0133] The MR system can support signal transmission / reception in unlicensed bands. According to regional regulations for unlicensed bands, communication nodes in unlicensed bands need to determine whether the channel is used by (one or more) other communication nodes before sending a signal. Specifically, the communication node can perform carrier sensing (CS) before transmitting a signal to check whether (one or more) other communication nodes perform signal transmission. When it is determined that (one or more) other communication nodes do not perform signal transmission, it can be said that the idle channel assessment (CCA) is confirmed. When the CCA threshold is predefined or configured by higher layer signaling (e.g., RRC signaling), if the detected channel energy is higher than the CCA threshold, the communication node can determine that the channel is busy. Otherwise, the communication node can determine that the channel is idle. When it is determined that the channel is idle, the communication node can start signal transmission in UCell. The above series of processes can be referred to as listen before talk (LBT) or channel access process (CAP). LBT and CAP can be used interchangeably in this document.

[0134] Figure 2 Figure 1. Radio frame structure. In NR, uplink transmission and downlink transmission are configured in frames. Each radio frame has a length of 10 ms and is divided into two 5 ms half frames (HF). Each half frame is divided into five 1 ms subframes (SF). A subframe is divided into one or more time slots, and the number of time slots in a subframe depends on the subcarrier spacing (SCS). Depending on the cyclic prefix (CP), each time slot includes 12 or 14 orthogonal frequency division multiplexing (OFDM) symbols. When a normal CP is used, each time slot includes 14 OFDM symbols. When an extended CP is used, each time slot includes 12 OFDM symbols.

[0135] Table 1 exemplarily shows that the number of symbols per slot, the number of slots per frame, and the number of slots per subframe vary according to the SCS when a normal CP is used.

[0136] [Table 1]

[0137] SCS(15*2^u) <![CDATA[N slot symb ]]> <![CDATA[N frame,u slot ]]> <![CDATA[N subframe,u slot ]]> 15KHz(u=0) 14 10 1 30KHz(u=1) 14 20 2 60KHz(u=2) 14 40 4 120KHz(u=3) 14 80 8 240KHz(u=4) 14 160 16

[0138] *N slot symb : The number of symbols in a time slot

[0139] *N frame,u slot : Number of time slots in a frame

[0140] *N subframe,u slot : Number of time slots in a subframe

[0141] Table 2 shows that the number of symbols per slot, the number of slots per frame, and the number of slots per subframe vary according to the SCS when the extended CP is used.

[0142] [Table 2]

[0143] SCS(15*2^u) <![CDATA[N slot symb ]]> <![CDATA[N frame,u slot ]]> <![CDATA[N subframe,u slot ]]> 60KHz(u=2) 12 40 4

[0144] The structure of the frame is only an example. The number of subframes, the number of time slots, and the number of symbols in a frame may vary.

[0145] In the NR system, OFDM parameter sets (e.g., SCS) may be configured differently for multiple cells aggregated for one UE. Therefore, the (absolute time) duration of a time resource (e.g., SF, time slot, or TTI) (referred to as a time unit (TU) for simplicity) consisting of the same number of symbols may be configured differently between aggregated cells. Here, the symbol may include an OFDM symbol (or CP-OFDM symbol) and an SC-FDMA symbol (or a discrete Fourier transform-spread-OFDM (DFT-s-OFDM) symbol).

[0146] Figure 3 A resource grid showing a time slot. A time slot includes multiple symbols in the time domain. For example, when a normal CP is used, a time slot includes 14 symbols. However, when an extended CP is used, a time slot includes 12 symbols. A carrier includes multiple subcarriers in the frequency domain. A resource block (RB) is defined as a plurality of consecutive subcarriers (e.g., 12 consecutive subcarriers) in the frequency domain. A bandwidth part (BWP) may be defined as a plurality of consecutive physical RBs (PRBs) in the frequency domain and corresponds to a single parameter set (e.g., SCS, CP length, etc.). A carrier may include up to N (e.g., five) BWPs. Data communication may be performed via enabled BWPs, and only one BWP may be enabled for a UE. In a resource grid, each element is referred to as a resource element (RE), and a complex symbol may be mapped to each RE.

[0147] Bandwidth Part (BWP)

[0148] The NR system can support up to 400MHz frequency for each carrier. The network can instruct the UE to operate only in part of the bandwidth of such a wideband carrier instead of the entire bandwidth. The partial bandwidth is called BWP. BWP refers to a subset of continuous common RBs defined by a parameter set in the BWP of a carrier in the frequency domain, and a parameter set (e.g., SCS, CP length, slot / mini-slot duration, etc.) can be configured.

[0149] The activation / deactivation of DL / UL BWP or BWP switching can be performed according to network signaling and / or timers (e.g., L1 signaling corresponding to a physical layer control signal, a MAC control element corresponding to a MAC layer control signal, RRC signaling, etc.). When performing initial access or before setting up an RRC connection, the UE may not receive any DL / UL BWP configuration. The DL / UL BWP assumed by the UE in this situation is referred to as the initial active DL / UL BWP.

[0150] Figure 4 An exemplary normal random access process is shown. Specifically, Figure 4 A contention-based random access procedure of a UE is shown, which is performed in four steps.

[0151] First, the UE may send a message 1 (Mg1) including a random access preamble on the PRACH (see Figure 4 (a) 1701).

[0152] Random access preamble sequences with different lengths can be supported. The long sequence length of 839 can be applied to SCSs of 1.25 and 5 kHz, and the short sequence length of 139 can be applied to SCSs of 15, 30, 60, and 120 kHz.

[0153] Multiple preamble formats may be defined by one or more RACH OFDM symbols and different CPs (and / or guard times). The RACH configuration for a cell may be included in the SI about the cell and provided to the UE. The RACH configuration may include information about the SCS of the PRACH, available preambles, preamble formats, etc. The RACH configuration may include information about the association between the SSB and the RACH (time-frequency) resources. The UE sends a random access preamble on the RACH time-frequency resources associated with the detected or selected SSB.

[0154] The threshold of the SSB for RACH resource association may be configured by the network, and the RACH preamble may be sent or retransmitted based on the SSB, where the reference signal received power (RSRP) measured based on the SSB meets the threshold. For example, the UE may select an SSB from among the SSBs that meet the threshold, and send or retransmit the RACH preamble based on the RACH resource associated with the selected SSB.

[0155] Upon receiving the random access preamble from the UE, the BS may transmit a message 2 (Msg2) corresponding to a random access response (RAR) message to the UE (see Figure 41703 of (a)). The PDCCH that schedules the PDSCH carrying the RAR may be CRC-masked with a random access (RA) radio network temporary identifier (RNTI) (RA-RNTI) and then transmitted. When the UE detects the PDCCH masked by the RA-RNTI, the RAR may be obtained from the PDSCH scheduled by the DCI carried by the PDCCH. The UE may check whether the RAR includes RAR information in response to the preamble sent by the UE, i.e., Msg1. The presence or absence of RAR information in response to Msg1 sent by the UE may be determined depending on whether there is a random access preamble ID for the preamble sent by the UE. If there is no response to Msg1, the UE may retransmit the RACH preamble within a predetermined number of times while performing power ramping. The UE may calculate the PRACH transmit power for retransmitting the preamble based on the most recent path loss and the power ramp counter.

[0156] The RAR information sent on the PDSCH may include timing advance (TA) information for UL synchronization, initial UL grant, and temporary cell-RNTI (C-RNTI). The TA information may be used to control the UL signal transmission timing. The UE may send a UL signal on the UL shared channel as message 3 (Msg3) of the random access procedure based on the RAR information (see Figure 4 1705 of (a)). Msg3 may include an RRC connection request and a UE identifier. In response to Msg3, the network may send message 4 (Msg4), which may be regarded as a contention resolution message on the DL (see Figure 4 Upon receiving Msg4, the UE may enter the RRC_CONNECTED state.

[0157] On the other hand, when the UE is switched to another cell or BS or when it is requested by the BS, a non-contention random access procedure may be performed. In the non-contention random access procedure, the preamble to be used by the UE (hereinafter referred to as a dedicated random access preamble) is allocated by the BS. Information about the dedicated random access preamble may be included in an RRC message (e.g., a handover command) or provided to the UE via a PDCCH command. When initiating a random access procedure, the UE may send a dedicated random access preamble to the BS. When the UE receives an RAR from the BS, the random access procedure is completed.

[0158] As described above, the UL grant in the RAR can schedule PUSCH transmission to the UE. The PUSCH carrying the initial UL transmission based on the UL grant in the RAR is called Msg3 PUSCH. The content of the RAR UL grant can start at the MSB and end at the LSB, and the content can be given as shown in Table 3.

[0159] [Table 3]

[0160] RAR UL Permit Field Number of bits Frequency Hopping Flag 1 Msg3 PUCCH frequency resource allocation 12 Msg3 PUSCH time resource allocation 4 Modulation and Coding Scheme (MCS) 4 Transmit Power Control (TPC) for Msg3 PUSCH 3 CSI Request 1

[0161] In the contention-free random access (CFRA) procedure, the CSI request field in the RAR UL grant indicates whether the terminal includes aperiodic CSI reports in the corresponding PUSCH transmission. The subcarrier spacing for Msg3 PUSCH transmission can be provided by RRC parameters. The terminal can send PRACH and Msg3PUSCH on the same uplink carrier in the same serving cell. The ULBWP for Msg3 PUSCH transmission is indicated by system information block 1 (SIB1).

[0162] Figure 5 An exemplary mapping of physical channels in a time slot is illustrated. PDCCH may be sent in the DL control region, and PDSCH may be sent in the DL data region. PUCCH may be sent in the UL control region, and PUSCH may be sent in the UL data region. A guard period (GP) provides a time gap for a transmission mode to reception mode switch or a reception mode to transmission mode switch at a BS and a UE. Some symbols in a subframe at the time of a DL to UL switch may be configured as a GP.

[0163] Each physical channel is described in more detail below.

[0164] PDCCH delivers DCI. For example, PDCCH (i.e., DCI) can carry information about the transport format and resource allocation of the DL shared channel (DL-SCH), resource allocation information of the uplink shared channel (UL-SCH), paging information about the paging channel (PCH), system information about DL-SCH, information about resource allocation of higher-layer control messages (such as RAR sent on PDSCH), transmit power control commands, information about activation / release of configured scheduling, etc. DCI includes a cyclic redundancy check (CRC). Depending on the owner or purpose of the PDCCH, the CRC is masked with various identifiers (IDs) (e.g., radio network temporary identifiers (RNTI)). For example, if the PDCCH is used for a specific UE, the CRC is masked by the UEID (e.g., cell RNTI (C-RNTI)). If the PDCCH is used for a paging message, the CRC is masked by the paging RNTI (P-RNTI). If the PDCCH is used for system information (e.g., system information block (SIB)), the CRC is masked by the system information RNTI (SI-RNTI). When the PDCCH is used for RAR, the CRC is masked by a random access RNTI (RA-RNTI).

[0165] The PDCCH includes 1, 2, 4, 8 or 16 control channel elements (CCEs) depending on its aggregation level (AL). CCE is a logical allocation unit for providing a specific code rate for the PDCCH according to the radio channel state. CCE includes 6 resource element groups (REGs), each REG is defined by one OFDM symbol multiplied by one (P)RB. The PDCCH is transmitted in a control resource set (CORESET). A CORESET is defined as a set of REGs with a given parameter set (e.g., SCS, CP length, etc.). Multiple CORESETs for one UE can overlap with each other in the time / frequency domain. The CORESET can be configured by system information (e.g., master information block (MIB)) or UE-specific higher layer signaling (e.g., radio resource control (RRC) signaling). Specifically, the number of RBs and the number of symbols (up to 3) in the CORESET can be configured by higher layer signaling.

[0166] For PDCCH reception / detection, the UE monitors PDCCH candidates. PDCCH candidates are CCEs that the UE should monitor to detect PDCCH. Depending on the AL, each PDCCH candidate is defined as 1, 2, 4, 8 or 16 CCEs. Monitoring includes (blind) decoding of PDCCH candidates. The set of PDCCH candidates decoded by the UE is defined as the PDCCH search space (SS). The SS can be a common search space (CSS) or a UE-specific search space (USS). The UE can obtain DCI by monitoring PDCCH candidates in one or more SSs configured by MIB or higher layer signaling. Each CORESET is associated with one or more SSs, and each SS is associated with one CORESET. The SS can be defined based on the following parameters.

[0167] -controlResourceSetId: CORESET associated with SS.

[0168] - monitoringSlotPeriodicityAndOffset: PDCCH monitoring periodicity (in time slot units) and PDCCH monitoring offset (in time slot units).

[0169] - monitoringSymbolsWithinSlot: PDCCH monitoring symbols in a slot (eg, the first symbol of a CORESET).

[0170] -nrofCandidates: The number of PDCCH candidates for each AL={1,2,4,8,16} (one of 0, 1, 2, 3, 4, 5, 6 and 8).

[0171] * The timing (eg, time / frequency resource) at which the UE is to monitor a PDCCH candidate is defined as a PDCCH (monitoring) timing. One or more PDCCH (monitoring) timings may be configured in a time slot.

[0172] Table 4 shows the characteristics of each SS.

[0173] [Table 4]

[0174]

[0175] Table 5 shows the DCI format transmitted on the PDCCH.

[0176] [Table 5]

[0177]

[0178] DCI format 0_0 can be used to schedule TB-based (or TB-level) PUSCH, and DCI format 0_1 ​​can be used to schedule TB-based (or TB-level) PUSCH or code block group (CBG) (or CBG level) PUSCH. DCI format 1_0 can be used to schedule TB-based (or TB-level) PDSCH, and DCI format 1_1 can be used to schedule TB-based (or TB-level) PDSCH or CBG (or CBG level) based PDSCH (DL grant DCI). DCI format 0_0 / 0_1 can be referred to as UL grant DCI or UL scheduling information, and DCI format 1_0 / 1_1 can be referred to as DL grant DCI or DL ​​scheduling information. DCI format 2_0 is used to deliver dynamic slot format information (e.g., dynamic slot format indicator (SFI)) to the UE, and DCI format 2_1 is used to deliver DL preemption information to the UE. DCI format 2_0 and / or DCI format 2_1 may be delivered to a corresponding group of UEs on a group-common PDCCH, which is a PDCCH for a group of UEs.

[0179] DCI format 0_0 and DCI format 1_0 may be referred to as fallback DCI formats, while DCI format 0_1 ​​and DCI format 1_1 may be referred to as non-fallback DCI formats. In the fallback DCI format, the DCI size / field configuration remains the same regardless of the UE configuration. In contrast, the DCI size / field configuration varies in the non-fallback DCI format depending on the UE configuration.

[0180] PDSCH transmits DL data (e.g., DL shared channel transport block (DL-SCH TB)) and uses a modulation scheme such as quadrature phase shift keying (QPSK), hexadecimal quadrature amplitude modulation (16QAM), 64QAM or 256QAM. TB is encoded into codewords. PDSCH can deliver up to two codewords. Scrambling and modulation mapping can be performed on the basis of codewords, and the modulation symbols generated from each codeword can be mapped to one or more layers. Each layer is mapped to a resource together with a demodulation reference signal (DMRS), and an OFDM symbol signal is generated from a mapped layer with DMRS and sent through a corresponding antenna port.

[0181] PUCCH delivers uplink control information (UCI). UCI includes the following information.

[0182] -SR (Scheduling Request): Information used to request UL-SCH resources.

[0183] -HARQ (Hybrid Automatic Repeat Request) -ACK (Acknowledgement): A response to a DL data packet (e.g., a codeword) on the PDSCH. HARQ-ACK indicates whether the DL data packet has been successfully received. In response to a single codeword, a 1-bit HARQ-ACK can be sent. In response to two codewords, a 2-bit HARQ-ACK can be sent. The HARQ-ACK response includes a positive ACK (abbreviated as ACK), a negative ACK (NACK), a discontinuous transmission (DTX), or NACK / DTX. The term HARQ-ACK is used interchangeably with HARQ ACK / NACK and ACK / NACK.

[0184] -CSI (Channel State Information): Feedback information for DL ​​channels. Feedback information related to Multiple Input Multiple Output (MIMO) includes RI and PMI.

[0185] The PUSCH delivers UL data (e.g., UL shared channel transport block (UL-SCH TB)) and / or UCI based on a CP-OFDM waveform or a DFT-s-OFDM waveform. When the PUSCH is transmitted with a DFT-s-OFDM waveform, the UE transmits the PUSCH by transform precoding. For example, when transform precoding is not possible (e.g., disabled), the UE can transmit the PUSCH with a CP-OFDM waveform, and when transform precoding is possible (e.g., enabled), the UE can transmit the PUSCH with a CP-OFDM waveform or a DFT-s-OFDM waveform. PUSCH transmission can be dynamically scheduled by a UL grant in the DCI, or semi-statically scheduled (configured scheduling or configured grant) by higher layer (e.g., RRC) signaling (and / or layer 1 (L1) signaling such as PDCCH). PUSCH transmission can be performed in a codebook-based or non-codebook-based manner.

[0186] Narrower DL BWP for system information and paging

[0187] Recently, in addition to the main 5G use cases (mMTC, eMBB and URLLC), the importance / interest in use case areas across mMTC and eMBB or across mMTC and URLLC has increased. These use cases may include connected industries, smart cities, wearable devices, etc. In order to more efficiently support the above use cases in terms of terminal cost / complexity, power consumption, etc. in wireless communication systems, a new type of terminal that is different from traditional NR terminals has been introduced. This new type of terminal may be referred to as a NR terminal with reduced capability (hereinafter referred to as RedCap UE / terminal or RedCap), and in order to distinguish the new type of terminal from conventional NR terminals, conventional NR terminals may be referred to as non-RedCap UE / terminal or non-RedCap. RedCap terminals are cheaper than non-RedCap terminals and have low power consumption, and in detail, may have all or some of the following functions.

[0188] A. Features related to complexity reduction:

[0189] - Reduced maximum UE bandwidth

[0190] - Reduced number of UE RX / TX branches / antennas

[0191] -Half-duplex FDD

[0192] -Relaxed UE processing time

[0193] -Relaxed UE processing capabilities

[0194] B. Functions related to power saving:

[0195] - Extended DRX for RRC Inactive and / or Idle

[0196] - RRM relaxation for fixed installations

[0197] Target use cases for a Redcap terminal with the above capabilities may include the following:

[0198] 1) Connected Industry

[0199] -Sensors and actuators connected to the 5G network and core

[0200] - Large-scale Industrial Wireless Sensor Networks (IWSN)

[0201] - In addition to URLLC services with very high requirements, relatively low-cost services in a small device form factor with a battery life of several years are required

[0202] - The requirements for these services are higher than Low Power Wide Area (LPWA, i.e. LTE-M / NB-IOT) but lower than URLCC and eMBB

[0203] -Pressure sensor, humidity sensor, thermometer, motion sensor, accelerometer, actuator, etc.

[0204] 2) Smart City

[0205] Data collection and processing to more efficiently monitor and control city resources and provide services

[0206] -Basic surveillance cameras for factories and industries as well as smart cities

[0207] 3) Wearable devices

[0208] -Smart watches, rings, electronic health-related devices, medical monitoring devices, etc.

[0209] -Small devices, etc.

[0210] RedCap terminals may have lower transmit and receive performance compared to non-RedCap terminals. The main reason is the reduction in frequency diversity performance due to the reduction in terminal bandwidth. The performance degradation increases as the supported terminal bandwidth decreases.

[0211] Considering the main use cases of RedCap, such as wearable devices and large-scale wireless sensors, traffic congestion is expected due to the need to support large-scale connections over narrow bandwidth.

[0212] A method for solving the above problem is proposed, that is, supporting terminal frequency hopping (hereinafter referred to as FH) and supporting service offloading (hereinafter referred to as TO).

[0213] In the present specification, "()" may be interpreted as excluding the contents in () and including the contents in the brackets.

[0214] In the present specification, “ / ” may mean including all contents separated by / (and) or including only some contents among the contents separated by / (or).

[0215] Multiple RedCap UE types and BWP methods

[0216] In this specification, multiple different RedCap UE types are supported as follows. In particular, it supports at least two types.

[0217] (1) Version 17 Red Cap Terminal: Version 17R Terminal supports 20 MHz BWP

[0218] (2) Release 18 Red Cap Terminal: Release 18 R Terminal supports 5 MHz BWP (or 5 MHz sub-BWP or 5 MHz BW position)

[0219] 1) Option BW1: For UL / DL, both RF and baseband (BB) bandwidths of the terminal support 5 MHz.

[0220] 2) Option BW2: For all UL / DL signals / channels, the terminal supports a BB bandwidth of 5 MHz and an RF bandwidth of 20 MHz.

[0221] 3) Option BW3: For PDSCH (unicast / broadcast PDSCH) and PUSCH, only 5MHz BB bandwidth is supported, and for UL / DL, 20MHz RF bandwidth is supported. However, for different physical channels and signals, up to 20MHz RF+BB bandwidth of the UE is supported.

[0222] In this specification, Release 18 PDSCH or DCI may refer to PDSCH or DCI for Release 18R terminals. Release 17 PDSCH, legacy PDSCH, or PDSCH before Release 18 may refer to PDSCH for non-RedCap terminals, regardless of Release 17R terminals or versions, and Release 17 DCI, legacy DCI, or DCI before Release 18 may refer to DCI for non-RedCap terminals, regardless of Release 17R terminals or versions.

[0223] In the specification, the BWP for Release 18R terminals may be replaced with a sub-BWP or BW position and may have a size of 5 MHz or less.

[0224] Method for dividing and allocating an initial BWP for a general terminal or a Release 17 initial BWP for a Release 17 RedCap terminal into N 5MHz PDSCHs for a Release 18 terminal

[0225] For Release 18R terminals, the BS may divide the initial BWP for general terminals or the initial BWP for Release 17 RedCap terminals into N 5MHz to allocate PDSCH. For example, when the Release 18R terminal can only receive PDSCH transmission up to 5MHz, the initial BWP of 20MHz is divided into N 5MHz, and in order to send system information or send paging, the Release 18 PDSCH can be sent in one or more specific parts of 5MHz in the initial BWP of 20MHz.

[0226] Figure 6 FIG. 2 shows a flow chart of a method for transmitting and receiving a signal according to an embodiment of the present invention. Figure 6 , the terminal may receive system information (605) and configure an initial BWP (610). The terminal may receive a paging signal from the BS (615) and may perform a RACH procedure (620).

[0227] Method 1: One DCI schedules multiple PDSCH transmissions using FDM within a 20MHz DL BWP

[0228] Figure 7 An example of a method of allocating N PDSCH resources according to an embodiment is shown.

[0229] For example, when there is a separate search space / CORESET for Release 18 terminals or a separate initial BWP of 5 MHz, the BS may divide the 20 MHz BWP into more / less than four 5 MHz sub-BWPs or 5 MHz BW positions. At this time, a set of all sub-BWPs or BW positions may be configured outside the 20 MHz initial BWP. For example, when four 5 MHz BW positions are allocated in a 15 kHz SCS, this may be possible when more than 20 MHz is allocated. This method may be applied to PDSCH transmissions for paging or system information. For example, in Figure 7 In the case of paging, the PDCCH may transmit the paging DCI, and the PDSCH may correspond to different PDSCHs for different paging subgroups.

[0230] like Figure 7As shown, in the case where a Release 18 UE monitors a paging PDCCH on the same MO of a paging group, multiple PDSCH transmissions in FDM can be divided into individual paging subgroups of the paging group. In this case, the same time domain resource allocation (TDRA) can be applied to all FDMed PDSCHs scheduled by the same DCI. For UEs with option BW3, the PDCCH carrying the paging DCI can be sent within 20MHz. For UEs with option BW1 or BW2, the PDCCH carrying the paging DCI can be sent within 5MHz.

[0231] When frequency hopping is configured for paging, the PDCCH in 5MHz can schedule the PDSCH in 5MHz for the UE of BW1, and here, the PDCCH of 5MHz and the PDSCH of 5MHz can be allocated differently in the frequency domain, and may or may not overlap in the frequency domain. The UE may not be able to decode both the PDCCH of 5MHz and the PDSCH of 5MHz in the same time slot, and therefore the PDCCH of 5MHz can schedule the PDSCH of 5MHz in the next (sub) time slot (i.e., by cross-slot scheduling). For example, the PDCCH of 5MHz can be sent in the first time slot, and the PDSCH of 5MHz scheduled by the PDCCH of 5MHz can be sent in the second time slot after the first time slot. There can be zero or one or more time slots between the first time slot and the second time slot.

[0232] exist Figure 7 In the embodiment of the present invention, the FDM PDSCH is scheduled in the same time slot. Alternatively, the FDM PDSCH can be scheduled in different time slots. For example, the 5MHz PDSCH for subgroup 1 can be scheduled in the first time slot by the PDCCH in the first time slot, the 5MHz PDSCH for subgroup 2 can be scheduled in the second time slot by the PDCCH in the first time slot, the 5MHz PDSCH for subgroup 3 can be scheduled in the third time slot by the PDCCH in the first time slot, and the 5MHz PDSCH for subgroup 4 can be scheduled in the third time slot or the fourth time slot by the PDCCH in the first time slot. The same or different multiple transmissions of the 5MHz PDSCH in 5MHz can be scheduled by the same DCI or different DCIs within 20MHz.

[0233] The 5 MHz PDSCH may be fully or partially scheduled outside the 20 MHz of the PDCCH or within the 20 MHz of the PDCCH.The same TDRA may be applied to multiple transmissions of the 5 MHz PDSCH in the same or different time slots.

[0234] In the TDRA method, the value K0 corresponding to the difference between DCI transmission and PDSCH transmission may be configured as an RRC message or a fixed value K0. Alternatively, the DCI may indicate the value K0. The K0 value may be configured or indicated separately for each BW option. For example, the RRC message or DCI sets / indicates the value K0 for each option, and at this time, the terminal of the BW2 option may set / indicate a smaller value K0 than the terminal of the BW1 option. The K0 value may configure the time gap between the DCI and the PDSCH as a slot level difference or a symbol level difference.

[0235] In the case of Release 18 UEs, the sub-BWP or BW position in the (initial) BWP for frequency domain resource allocation (FDRA) may be determined as follows:

[0236] (1) Option A: Configure the UE for each UE group or RRC message according to Release 18 rules (e.g., based on UE ID) 5MHz position of PDSCH.

[0237] A Release 18 UE may be configured at a predefined BW position to receive PDSCH within 5 MHz. Figure 7 In the present invention, a specific UE may be configured to schedule the PDSCH of paging subgroup 3 within a third 5MHz position according to a predefined rule. The predefined rule may be configured based on the UE ID of the UE (e.g., s-TMSI, recovery ID, or C-RNTI) or according to system information and / or UE-specific signaling. The predefined BW position may have a width of 5MHz, 5MHz or greater, or 5MHz or less, and may be configured as a DL (sub) BWP for Release 18 UEs. The UE may monitor the PDCCH within a predefined position of 5MHz, and the PDCCH may schedule the PDSCH with the predefined BW position. The predefined BW position of the PDCCH may be the same as or different from the predefined BW position of the PDSCH of the PDCCH.

[0238] The predefined BW position may be configured to a sub-BWP of a UE or an (initial) BWP of a UE. The predefined BW position may be configured or reconfigured via system information or UE-specific signaling.

[0239] (2) Option B: Dynamic allocation of 5 MHz locations for PDSCH

[0240] For the entire frequency domain of the (initial) BWP (e.g., 20 MHz), when the terminal receives DCI and the DCI includes an index / indicator of a specific sub-BWP or a predefined BW position, the PDSCH scheduled by the DCI can be received in the indicated specific sub-BWP or predefined BW position.

[0241] - One of Option A or Option B of the UE may be used, or both Option A and Option B may be used. For example, even if the position of 5 MHz is predefined, DCI indicating cross-slot scheduling may change the position of 5 MHz of the scheduled PDSCH.

[0242] 1) Option B1: For the entire frequency domain of the (initial) BWP (e.g., 20 MHz), a method of indicating an index / indicator of a specific sub-BWP or predefined BW position through a specific bit in the FDRA field of the DCI or a new field

[0243] For example, when receiving Figure 7 When a DCI of a PDCCH is received, if 20 MHz is divided into 4 sub-BWPs, the 2 MSBs or 2 LSBs of FDRA indicate a specific sub-BWP or a predetermined BW position. A terminal receiving the DCI receives the PDSCH scheduled by the DCI in the indicated sub-BWP or predetermined BW position.

[0244] 2) Option B2: The DCI includes a field in the form of a bitmap, each bit of the bitmap indicates a specific sub-BWP or a predefined BW position, and the DCI indicates the same RIV for one or more sub-BWPs indicated by the bitmap.

[0245] For example, when passing Figure 7 When DCI is received on a PDCCH with a bitmap of 0011, the same RIV is applied to PDSCH transmissions in the third or fourth sub-BWP or predefined BW position.

[0246] In the above method, the 2 MSBs or 2 LSBs in the FDRA bits of the DCI may also indicate the position of the sub-BWP of 5 MHz or the predefined BW position.

[0247] For example, for paging or system information, DCI can schedule various Release 18 PDSCHs in the time domain using different K0 values ​​as follows:

[0248] -K0=1: Release 18 PDSCH1

[0249] -K0=2: Version 18 PDSCH2

[0250] -K0=3: Release 18 PDSCH3

[0251] -K0=4: Release 18 PDSCH4

[0252] exist Figure 7 In FDM, four PDSCHs can be allocated in the time domain using different K0 values.

[0253] Method 2: One DCI schedule for Release 18 RedCap UEs within or outside the pre-Release 18 DL BWP More than one Release 18 PDSCH transmission

[0254] For example, Release-18 PDSCH transmissions as well as Release-17 PDSCH transmissions may be scheduled using Release-17 search space / CORESET or Release-17 initial BWP. In this case, the Release-17 PDSCH may transmit Release-17 paging or system information and the Release-18 PDSCH may transmit Release-18 paging or system information. The BS may transmit Release-18 PDSCH within or outside the Release-17 initial BWP and configure a separate Release-18 sub-BWP or BW position for Release-18 for Release-18 PDSCH transmissions within or outside the Release-17 initial BWP.

[0255] In this method, the legacy DCI for release 18 or earlier can schedule the PDSCH transmission before the release and the release 18 PDSCH transmission together. Therefore, the terminal before release 18 and the terminal of release 18 can monitor the monitoring opportunity (MO) or paging opportunity according to the configuration. In this case, the reserved bits of the legacy DCI for release 18 PDSCH transmission can include the following FDRA or TDRA information.

[0256] 1) Option 2-1: The reserved bits of the legacy DCI indicate the FDRA used for transmission of Release-18 PDSCH (eg, the resource indicator value (RIV) of allocation type 1).

[0257] TDRA applied to the legacy PDSCH in DCI is also applied to Release-18 PDSCH.

[0258] (i) Option 2-1A: The K0 value and SLIV applied to the existing PDSCH also apply to Release-18 PDSCH

[0259] (ii) Option 2-1B: SLIV applied to legacy PDSCH is also applied to Rel-18 PDSCH transmission. However, separate K0 values ​​are applied to legacy PDSCH and Rel-18 PDSCH, and reserved bits in legacy DCI indicate separate K0 values.

[0260] 2) Option 2-2: The reserved bits of the legacy DCI indicate TDRA for Release 18 transmission.

[0261] In the DCI, the FDRA applied to the legacy PDSCH is also applied to the Rel-18 PDSCH. In the DCI, the FDRA applied to the legacy PDSCH is reflected in the sub-BWP or BW position of 5 MHz for the Rel-18 PDSCH.

[0262] (i) Option 2-2A: SLIV applied to legacy PDSCH is also applied to Rel-18 PDSCH transmission. However, separate K0 values ​​are applied to legacy PDSCH and Rel-18 PDSCH, and reserved bits in legacy DCI indicate separate K0 values.

[0263] (ii) Option 2-2B: Apply separate K0 and SLIV values ​​to the existing PDSCH and Release-18 PDSCH, and indicate the separate K0 and SLIV values ​​as reserved bits of the existing DCI.

[0264] For example, DCI may schedule one Release 17 paging PDSCH and two Release 18 paging PDSCHs in the time domain using different K0 values ​​as follows.

[0265] - K0 = 1: Release 17 Paging PDSCH

[0266] -K0=2: Release 18 paging PDSCH1

[0267] - K0 = 3: Release 18 paging PDSCH2

[0268] 3) Option 2-3: The reserved bits of the legacy DCI indicate FDRA and TDRA for Release-18 PDSCH transmission.

[0269] (i) Option 2-3A: In case of TDRA, the SLIV applied to the legacy PDSCH is also applied to the Rel-18 PDSCH transmission. However, a separate K0 value is applied to the legacy PDSCH and the Rel-18 PDSCH, and the separate K0 value is indicated as a reserved bit in the legacy DCI.

[0270] (ii) Option 2-3B: In case of TDRA, separate K0 values ​​and SLIV values ​​are applied to legacy PDSCH and Rel-18 PDSCH, and the separate K0 values ​​and SLIV are indicated as reserved bits in the legacy DCI.

[0271] (iii) Option 2-3C: In case of FDRA allocation type 1, separate RIV values ​​are applied to legacy PDSCH and Rel-18 PDSCH, and the separate RIV values ​​are indicated by the reserved bits of the legacy DCI and applied to Rel-18 (sub)BWP or BW positions. For example, a bandwidth of 5 MHz.

[0272] (iv) Option 2-3D: In case of FDRA allocation type 0, a separate RBG bitmap is applied to legacy PDSCH and Rel-18 PDSCH, and the separate RBG bitmap is indicated as a reserved bit in the legacy DCI and applied to Rel-18 (sub)BWP or BW positions. For example, a bandwidth of 5 MHz.

[0273] Figure 8 and Fig. 9 An example of Rel-18 PDSCH resource allocation using option 2-1 is shown. Figure 8 and Fig. 9 B shows a method of applying the same TDRA to legacy PDSCH and Release-18 PDSCH but applying different FDRAs. Figure 8 A case is shown where multiple Rel-18 PDSCHs scheduled by DCI are included in the legacy initial BWP (Rel-18 PDSCH resource allocation within 20 MHz). Fig. 9 A case is shown where there is one Rel-18 PDSCH scheduled by DCI and is not included in the legacy initial BWP (Rel-18 PDSCH resource allocation outside 20 MHz). Fig.10 An example of Release 18 PDSCH resource allocation using Option 2-2 or Option 2-3 is shown. Fig.10 As shown, according to option 2-2, the FDRA bit of the legacy PDSCH can be applied to the 5 MHz version 18 PDSCH of the next time slot. Fig.10 As shown, according to options 2-3, FDRA and TDRA, which are different from the legacy PDSCH, can be applied to the Release 18 PDSCH of 5 MHz.

[0274] exist Fig.10 Among the PRBs determined as the FDRA of the legacy PDSCH, the FDRA of the Release-18 PDSCH may be determined only based on the frequency resources belonging to the (sub)BWP or BW position (e.g., 5 MHz) of Release-18.

[0275] Fig. 9 Probably not an appropriate configuration for the BW3 option.

[0276] Method 3: Rel-18 FDRA allocation Type 0 and Type 1 for 5 MHz PDSCH transmission for Rel-18R terminals Law

[0277] For PDSCH frequency resource allocation in a (sub)BWP or BW position of Method 1 or Method 2, Method 3 may be applied as follows.

[0278] In the case of Release 18 UEs, for a sub-BWP or BW position within an (initial) BWP, the frequency domain resource allocation (FDRA) may be determined as follows:

[0279] (1) FDRA allocation type 0

[0280] like Fig.11 As shown, the existing FDRA allocation type 0 may be based on the determined RBG size and the number of RBGs.

[0281] 1) Option A1-1: (In the box), when PDSCH resources are allocated according to FDRA allocation type 0, if the total number of RBGs and PRBs is calculated, the BWP size is calculated in units of a sub-BWP size or a predefined BW position size (e.g., 5 MHz). For example, UE1 and UE2 belonging to different paging subgroups receiving the same paging DCI apply the same FDRA to the lower 5 MHz and the upper 5 MHz, respectively, and apply the RBG bitmap of the DCI received for 5 MHz to determine the PDSCH resource position for 5 MHz.

[0282] 2) Option A1-2: When PDSCH resources are allocated according to FDRA allocation type 0, the DCI indicates the RBGs of the entire BWP (e.g., 20 MHz) as a bitmap as in the normal case, and a specific terminal only uses the RBGs of the sub-BWP or predefined BW position configured for the specific terminal to determine the position of the PDSCH to be received.

[0283] In this case, the bitmap of DCI can be configured as follows.

[0284] i) Option A1-2a: The DCI includes a bitmap field for each sub-BWP or each predefined BW position. That is, the DCI includes one or more fields for one or more sub-BWPs or predefined BW positions.

[0285] ii) Option A1-2b: DCI includes one bitmap field, and one bitmap indicates FDRA of multiple sub-BWPs or predefined BW positions. The terminal finds the start / end position of the bit mapped to the terminal's own sub-BWP or predefined BW position in the bitmap, and applies FDRA to the PDSCH of the terminal's own sub-BWP or predefined BW position.

[0286] Therefore, the terminal calculates the start / end positions of all sub-BWPs or predefined BW positions of the corresponding BWP within the bitmap, and thus, the terminal finds the bit for the terminal's own sub-BWP or predefined BW position within the bitmap and applies FDRA.

[0287] iii) Option A1-2c: As in the conventional case, the DCI receives only the PDSCH with RBGs belonging to its own sub-BWP in the bitmap of all RBGs of the BWP.

[0288] At this time, when the boundary of the sub-BWP or the predefined BW position divides the RBG near the boundary, one of the following two methods may be determined.

[0289] i) RBGs near the boundary are configured with only the RBG portion included in the sub-BWP or predefined BW position. Therefore, the RGB size near the boundary is determined to be smaller than other RBG sizes; or

[0290] ii) The RBG portion included in the sub-BWP or predefined BW position is included as a portion of the adjacent RBG. Therefore, the size of the adjacent RBG is increased by a portion of the included RBG.

[0291] (2) FDRA allocation type 1

[0292] When PDSCH resources are allocated according to FDRA allocation type 1, a different RB start may be configured for each sub-BWP as follows.

[0293] 1) Option A2-1: The BS may pre-specify the RB start value for each terminal or terminal group. According to the configuration of the BS, the terminal determines the RB start value associated with the UE ID or the paging subgroup.

[0294] - For example, in Figure 7 In the DCI received by the PDCCH of the Paging DCI, the RIV of the DCI indicates the lowest RB start value, the reference RB start value, or RB start = 0. The terminal receiving the DCI configures the RB start for each sub-BWP or each predefined BW position. For example, when the RIV of the paging DCI is indicated as RB start = 0, UE1 with sub-BWP1 and UE2 with sub-BWP2 apply RB start 1 and RB start 2 to calculate their FDRA, respectively. As a result, the DCI indicating RB start = 0 only indicates the RB length shared by the sub-BWP, and the RB start can be semi-statically specified as an RRC message for each terminal or terminal group.

[0295] 2) Option A2-2: The terminal determines whether to receive the PDSCH by determining whether resource allocation exists in its own sub-BWP or predefined BW position according to the RIV value of the DCI.

[0296] - For example, the terminal is configured within the initial BWP to its configured sub-BWP or predefined BW position (the terminal group to which the configured terminal belongs). Then, when Figure 7 When a PDCCH receives DCI, it calculates the consecutive PRBs of all PDSCHs in the initial BWP according to the RIV value of the DCI, and only uses the PRBs located in the sub-BWP or predefined BW position configured for it to calculate the PDSCH transmission resources to receive the corresponding PDSCH.

[0297] 3) Option A2-3: The terminal calculates N PRB sets by dividing all consecutive PRBs according to the RIV value of the DCI by 1 / N, and selects a PRB set to receive the PDSCH. At this time, when the selected PRB set overlaps or does not overlap with its own sub-BWP or its predefined BW position frequency domain, the terminal can re-tune according to the PRB set.

[0298] - For example, when passing Figure 7 When the PDCCH receives DCI, the continuous PRBs of all PDSCHs in the initial BWP are calculated according to the RIV value of the DCI, and all continuous PRBs allocated according to the received RIV are divided by 1 / N to calculate N PRB sets and select the PRB set.

[0299] i) At this time, the terminal selects a PRB set from N PRB sets based on the index of the sub-BWP to which the terminal belongs, the predefined BW position index, the paging subgroup index, or the UE ID of the terminal, and receives the PDSCH according to the selected PRB set; or

[0300] ii) At this time, the terminal selects a PRB set in the frequency domain belonging to the terminal's own sub-BWP or predefined BW position. When there are multiple selected PRB sets, all PRB sets are selected, or one PRB set with the largest number of PRBs is selected.

[0301] 4) Option A2-4: DCI indicates the RIV value of each sub-BWP, each predefined BW position or each sub-group respectively. At this time, the DCI field can be configured as follows.

[0302] i) Option A2-4a: The RIV value for each sub-BWP or each predefined BW position is indicated as a different field in the DCI for each sub-BWP or each predefined BW position.

[0303] ii) Option A2-4b: The RIV value for each sub-BWP or each predefined BW position is indicated as a field in the DCI.

[0304] In this case, the terminal identifies the start / end position of the RIV bit of the sub-BWP or predefined BW position of the terminal in consideration of all sub-BWPs or predefined BW positions within the BWP.

[0305] iii) Option A2-4c: RB start value of a sub-BWP or predefined BW position different from the RIV value calculated based on RB start = 0 or lowest / highest / reference sub-BWP is included in one or a separate field.

[0306] For example, the RIV value of the DCI is indicated based on RB Start=0, and the corresponding DCI additionally includes RB Start 1 for UE1 and RB Start 2 for UE2.

[0307] The FDRA bit size in the DCI may be determined using a sub-BWP size or a predefined BW size (eg, 5 MHz) instead of the CORESET0 size.

[0308] This method can also be applied to terminals of other BW1 / BW2 options and BW3 options. For example, after receiving the 5MHz DCI, the terminal of the BW1 / 2 option can receive the 5MHz PDSCH by skipping the sub-BWP or predefined BW position. In this case, the 5MHz frequency domain of the 5MHz DCI and the 5MHz PDSCH can be allocated differently.

[0309] The terminal can determine whether to receive a specific PDSCH of 5 MHz based on the allocation of FDRA. For example, as a result of the calculation of the FDRA of the PDSCH, when there is no PDSCH transmission resource within the sub-BWP or predefined BW position of the terminal, the PDSCH of the DCI is not received. Alternatively, if there is no PDSCH transmission resource within the sub-BWP or predefined BW position of the terminal, the PDSCH of 5 MHz can be received via retuning.

[0310] Sub-BWP (or predefined BW position) operation method for Release 18R terminals

[0311] A Release-18R terminal that receives sub-BWP configuration information through system information may select a sub-BWP as follows.

[0312] (1) Option C1: Select one sub-BWP among N sub-BWPs based on a terminal-specific UE ID (eg, s-TMSI or C-RNTI or I-RNTI).

[0313] For example, a sub-BWP index that is the same as the value of the UE ID modulo N is selected, and a sub-BWP corresponding thereto is selected.

[0314] (2) Option C2: Select one sub-BWP from the N sub-BWPs according to the UE type of the terminal.

[0315] For example, 1 RX terminal selects sub-BWPIndex=0, 2 RX terminals select sub-BWPIndex=1, a half-duplex terminal selects sub-BWPIndex=2, a full-duplex terminal selects sub-BWPIndex=3, a 20MHz terminal selects sub-BWPIndex=4, and a 5MHz terminal selects a sub-BWP corresponding to sub-BWPIndex=5.

[0316] (3) Option C3: Select a sub-BWP based on the paging sub-group to which the terminal belongs.

[0317] For example, a sub-BWPIndex mapped according to the index of the sub-group is selected, and a sub-WP corresponding to the index is selected.

[0318] (4) Option C4: Random selection.

[0319] For example, the terminal randomly selects a random value between [0 and 1], and the BS compares the random value with the value [0, N1, N2, N3, ..., 1] transmitted using system information to select a sub-BWP. For example, when the random value is between [0 and N1], sub-BWPIndex = 0 is selected, when the random value is between [N1 and N2], sub-BWPIndex = 1 is selected, and when the random value is between [N2 and N3], sub-BWPIndex = 3 is selected, and in this case, the sub-BWP corresponding to the index is selected.

[0320] (5) Option C5: Select a sub-BWP based on the cell quality measured by the terminal.

[0321] For example, when the RSRP measurement value of the serving cell is equal to or greater than the Q0 value, sub-BWP=0 is selected, when the RSRP measurement value is equal to or greater than the Q1 value, sub-BWP=1 is selected, and when the RSRP measurement value is equal to or greater than the Q2 value, sub-BWP=2 is selected, and so on, and in this case, the sub-BWP corresponding to the index is selected.

[0322] (6) Option C6: Select the sub-BWP based on the beam quality measured by the terminal.

[0323] For example, when the SSB index of the best SSB of the serving cell is 0, 4, sub-BWP=0 is selected, when the SSB index of the best SSB is 1 and 5, sub-BWP=1 is selected, and when the SSB index of the best SSB is 2 and 6, sub-BWP=2 is selected, and so on, and in this case, the sub-BWP corresponding to the index is selected.

[0324] (7) Option C7: Select the sub-BWP according to the purpose specified by the BS.

[0325] 1) C7-0: The BS may specify the sub-BWP where the SIB1 of the Release 18 R terminal is located as sub-BWPIndex=0 (hereinafter referred to as sub-BWP0) through MIB, DCI scheduling regular SIB1, or regular SIB1 message. Alternatively, sub-BWPIndex=0 may be configured to always be used to send R-SIB1.

[0326] Therefore, the Release-18R terminal moves to the sub-BWP0 and receives SIB1 of the Release-18R terminal after receiving the MIB, receiving the DCI scheduling the regular SIB1, or receiving the regular SIB1 message.

[0327] The cell-defined SSB or non-cell-defined SSB for the Release-18R terminal may be configured in the sub-BWP0. The Release-18R terminal obtains the Release-18 SSB configuration information from the normal SIB1 or R-SIB1.

[0328] The Release 18R terminal can utilize the BS configuration to measure the Release 18 SSB and apply it to idle mobility measurement for cell selection / reselection, or can apply the Release 18 SSB measurement results to paging monitoring in sub-BWP, PRACH preamble / resource selection in sub-BWP, etc.

[0329] 2) C7-1: The BS may designate the sub-BWP where other system information (i.e., SIBx, x>1) is transmitted as sub-BWPIndex=1 (hereinafter referred to as sub-BWP1) through MIB, DCI scheduling regular SIB1, regular SIB1 message, or R-SIB1 of Release 18 R terminal. Alternatively, sub-BWPIndex=1 may be configured to always send other system information.

[0330] 3) C7-2: The BS may designate the sub-BWP where paging transmission is located as sub-BWPIndex=2 (hereinafter referred to as sub-BWP2) through MIB, DCI scheduling regular SIB1, regular SIB1 message, or R-SIB1 of Release 18 R terminals. Alternatively, sub-BWPIndex=2 may be configured to always send paging.

[0331] An alternative method may be used to send paging in k sub-BWPs among N sub-BWPs, and in this case, the following method is possible. (k=N or k <N)

[0332] i) Alternative 2A: Select one sub-BWP among k sub-BWPs and monitor paging using one method among options C1, C2, C3, C4, C5 and C6.

[0333] - In this case, paging search space is configured for all k sub-BWPs.

[0334] ii) Alternative 2B: The BS or a core network (CN) node (eg, AMF or MMF) selects one sub-BWP among k sub-BWPs to indicate to the terminal, and monitors paging.

[0335] - For example, select a sub-BWP configured by a paging search space, and monitor paging.

[0336] -At this time, when the terminal is inactive, the BS can instruct the terminal, and when the terminal is idle, the CN node can instruct the terminal.

[0337] iii) Alternative 2C: A sub-BWP indicated by the RRC release message may be selected and paging may be monitored.

[0338] - For example, when the terminal switches from connected mode to idle or inactive mode, the BS may indicate the sub-BWPIndex through an RRC release message. According to the indicated sub-BWPIndex, a sub-BWP is selected and paging is monitored.

[0339] 4) C7-3: The BS may specify the sub-BWP for performing RACH as sub-BWPIndex=3 (hereinafter referred to as sub-BWP3) through MIB, DCI scheduling regular SIB1, regular SIB1 message, or R-SIB1 of Release 18 R terminals. Alternatively, RACH may be configured to always be performed when sub-BWPIndex=3.

[0340] The Release 18R terminal defines the selected sub-BWP as follows.

[0341] (1) Option D1: The selected sub-BWP is defined as the initial BWP of the Release 18R terminal.

[0342] The Release 18R terminal applies the selected sub-BWP to perform normal initial BWP operations.

[0343] (2) Option D2: The selected sub-BWP is defined as a special-purpose BWP for Release 18R terminals.

[0344] For example, according to the Option C method, the selected sub-BWP may be defined as a DL BWP for paging monitoring, as a UL / DL BWP for RACH, or as a UL / DL BWP for SDT.

[0345] R-SIB1 reception in Release 18R terminals

[0346] The Release-18R terminal receives the Release-18 PDSCH transmitting system information according to methods 1, 2, and 3. In this case, the DCI of methods 1, 2, and 3 is a DCI having a CRC scrambled with an SI-RNTI.

[0347] When Release-18 PDSCH sends R-SIB1 for Release-18R terminals, DCI may schedule Release-18 PDSCH for R-SIB1 as follows.

[0348] (1) Option 1: One DCI on a CORESET shared by pre-Release 18 UEs and Rel-18 UEs schedules pre-Release 18 SIB1 and Rel-18 R-SIB1 within the initial DL BWP of 20 MHz using FDM (e.g., Figure 8 ).

[0349] (2) Option 2: One DCI on a CORESET shared by pre-Release 18 UEs and Release 18 UEs schedules pre-Release 18 SIB1 within the initial DL BWP of 20 MHz and Release 18 R-SIB1 outside the initial DL BWP of 20 MHz using FDM (e.g., Fig. 9 ).

[0350] (3) Option 3: One DCI on a CORESET shared by pre-Release 18 UEs and Release 18 UEs schedules pre-Release 18 SIB1 and Release 18 R-SIB1 within the initial DL BWP of 20 MHz using TDM (e.g., Fig.10 (b)).

[0351] In option 3, the Rel-18 PDSCH conveying Rel-18 R-SIB1 is scheduled within a (sub)BWP or BW position of 5 MHz, but the legacy PDSCH conveying pre-Rel-18 SIB1 is scheduled within an initial BWP of 5 MHz or an initial BWP of 20 MHz.

[0352] Like in option, the BS may indicate whether the DCI is scheduled by DCI or MIB for both Release 18 R-SIB1 and SIB1 before Release 18.

[0353] When the Release 18R terminal receives DCI for scheduling regular SIB1 or regular SIB1, the Release 18R terminal receives a separate cellBarred parameter for the Release 18R terminal from the regular SIB1 or the DCI for scheduling regular SIB1. According to the received cellBarred parameter, it is determined whether the Release 18R terminal can access the corresponding cell or whether the cell needs to be barred.

[0354] When the Release 18R terminal receives a new R-SIB1 or a DCI scheduling R-SIB1 but does not receive a regular SIB1, the Release 18R terminal selects a sub-BWP for R-SIB1 and selects the DCI of the selected sub-BWP or a separate cellBarred parameter for the Release 18R terminal from R-SIB1. According to the received cellBarred parameter, it is determined whether the Release 18R terminal can access the corresponding cell or whether the cell needs to be barred.

[0355] When SI on demand is configured, the BS may configure dedicated RACH resources for SI on demand requests. Alternatively, dedicated RACH resources may be configured for terminal identification during initial access. Therefore, for SI on demand requests or for terminal identification during initial access, the BS distinguishes and assigns RACH resources for Release 17R terminals, RACH resources for Release 18R terminals, and RACH resources for ordinary terminals. In this case, the BS may classify and allocate RACH resources for Option BW1 terminals, RACH resources for Option BW2 terminals, and RACH resources for Option BW3 terminals. These different RACH resources may be allocated separately through existing SIB1 and R-SIB1. In this case, the Release 18R terminal selects a PRACH resource suitable for its terminal type and sends MSG1 or MSGA. In addition, the Release 18R terminal may be indicated by the (sub) header of the MAC PDU of MSG3 PUSCH or MSGA PUSCH, or Option BW1, BW2, or BW3 may be indicated according to the terminal type.

[0356] Reception of paging by Release 18R terminals

[0357] The Release-18R terminal receives the Release-18 PDSCH transmitting the paging message according to methods 1, 2, and 3. In this case, the DCI of methods 1, 2, and 3 is a DCI having a CRC scrambled with a P-RNTI.

[0358] The DCI for PEI instead of the DCI in methods 1, 2 and 3 may indicate the (sub)BWP for the R terminal or the BW position for receiving the Release 18 paging PDSCH. Alternatively, the DCI for PEI instead of the DCI in methods 1, 2 and 3 may provide FDRA and / or TDRA information for receiving Release 18 paging.

[0359] When TRS for paging is configured for a Release 18R terminal, the Release 18 TRS may be configured as follows.

[0360] (1) Option 1: TRS for paging of Release 18R terminals is configured only within the initial BWP, sub-BWP or BW position of 5 MHz for Release 18R terminals.

[0361] When a TRS for a Release 18R terminal performs frequency hopping, the corresponding TRS performs frequency hopping only within an initial BWP, sub-BWP, or BW position of 5 MHz for the Release 18R terminal.

[0362] (2) Option 2: TRS for paging of Release 18R terminals can be configured outside the initial BWP, sub-BWP or BW position of 5 MHz. In this case, TRS is configured within the initial BWP of Release 17R terminals of 20 MHz.

[0363] Release 18R terminals (particularly Option BW1 or BW2 terminals) receive TRS by RF retuning.

[0364] Fig.12 The flow of a downlink signal transmitting and receiving method according to an embodiment is shown.

[0365] Reference Fig.12 , the UE can receive downlink control information (DCI) through the physical downlink control channel (PDCCH) (A05).

[0366] The UE may determine DL resources allocated to the UE based on a frequency domain resource allocation (FDRA) field included in the DCI (A10).

[0367] The UE may receive a Physical Downlink Shared Channel (PDSCH) on the DL resources (A15).

[0368] Based on that a first bandwidth supported by the UE for the PDCCH is different from a second bandwidth supported by the UE for the PDSCH, the UE may determine DL resources allocated through the FDRA field based on the second bandwidth instead of the first bandwidth.

[0369] The second bandwidth may be smaller than the first bandwidth.

[0370] The first bandwidth may be equal to or greater than 5 MHz, and the second bandwidth may be equal to or less than 5 MHz.

[0371] The frequency domain associated with the second bandwidth may belong to a first bandwidth part (BWP), and the first BWP may be shared with other UEs supporting reception of a PDSCH having a bandwidth greater than the second bandwidth.

[0372] The frequency domain associated with the second bandwidth may be one of a plurality of sub-BWPs included in the first BWP.

[0373] The DCI may include information for configuring one of a plurality of sub-BWPs included in the first BWP as a frequency domain associated with the second bandwidth.

[0374] The UE may determine DL resources allocated in the frequency domain associated with the second bandwidth through the FDRA field.

[0375] The total number of physical resource blocks (PRBs) and resource block groups (RBGs) associated with the PDSCH may be determined based on the second bandwidth.

[0376] Fig.13 A communication system 1 applied to the present disclosure is shown.

[0377] Reference Fig.13, the communication system 1 applied to the present disclosure includes a wireless device, a base station (BS), and a network. Herein, the wireless device refers to a device that performs communication using a radio access technology (RAT) (e.g., 5G new RAT (NR) or long term evolution (LTE)), and may be referred to as a communication / radio / 5G device. The wireless device may include (but is not limited to) a robot 100a, vehicles 100b-1 and 100b-2, an extended reality (XR) device 100c, a handheld device 100d, a home appliance 100e, an Internet of Things (IoT) device 100f, and an artificial intelligence (AI) device / server 400. For example, a vehicle may include a vehicle with a wireless communication function, an autonomous driving vehicle, and a vehicle capable of performing communication between vehicles. Herein, a vehicle may include an unmanned aerial vehicle (UAV) (e.g., a drone). XR devices may include augmented reality (AR) / virtual reality (VR) / mixed reality (MR) devices, and may be implemented in the form of a head mounted device (HMD), a head up display (HUD) installed in a vehicle, a television, a smart phone, a computer, a wearable device, a home appliance device, a digital sign, a vehicle, a robot, etc. Handheld devices may include smart phones, smart boards, wearable devices (e.g., smart watches or smart glasses), and computers (e.g., notebooks). Home appliances may include TVs, refrigerators, and washing machines. IoT devices may include sensors and smart meters. For example, a BS and a network may be implemented as wireless devices, and a specific wireless device 200a may operate as a BS / network node relative to other wireless devices.

[0378] The wireless devices 100a to 100f may be connected to the network 300 via the BS 200. The AI ​​technology may be applied to the wireless devices 100a to 100f, and the wireless devices 100a to 100f may be connected to the AI ​​server 400 via the network 300. The network 300 may be configured using a 3G network, a 4G (e.g., LTE) network, or a 5G (e.g., NR) network. Although the wireless devices 100a to 100f may communicate with each other via the BS 200 / network 300, the wireless devices 100a to 100f may perform direct communication (e.g., side link communication) with each other without passing through the BS / network. For example, the vehicles 100b-1 and 100b-2 may perform direct communication (e.g., vehicle-to-vehicle (V2V) / vehicle-to-everything (V2X) communication). An IoT device (e.g., a sensor) may perform direct communication with other IoT devices (e.g., a sensor) or other wireless devices 100a to 100f.

[0379] Wireless communication / connection 150a, 150b or 150c may be established between wireless devices 100a to 100f / BS200 or BS200 / BS200. Herein, wireless communication / connection may be established through various RATs (e.g., 5G NR) such as uplink / downlink communication 150a, sidelink communication 150b (or D2D communication) or inter-BS communication (e.g., relay, integrated access backhaul (IAB)). The wireless device and the BS / wireless device may send / receive radio signals to / from each other through wireless communication / connection 150a and 150b. For example, wireless communication / connection 150a and 150b may send / receive signals through various physical channels. To this end, at least a portion of various configuration information for configuring a process for sending / receiving a radio signal, various signal processing processes (e.g., channel coding / decoding, modulation / demodulation, and resource mapping / demapping), and a resource allocation process may be performed based on various proposals of the present disclosure.

[0380] Fig.14 A wireless device suitable for use with the present disclosure is shown.

[0381] Reference Fig.14 , the first wireless device 100 and the second wireless device 200 may transmit radio signals through various RATs (e.g., LTE and NR). Herein, {the first wireless device 100 and the second wireless device 200} may correspond to Fig.13 {wireless device 100x and BS 200} and / or {wireless device 100x and wireless device 100x}.

[0382] The first wireless device 100 may include one or more processors 102 and one or more memories 104, and further include one or more transceivers 106 and / or one or more antennas 108. The processor 102 may control the memory 104 and / or the transceiver 106, and may be configured to implement the description, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document. For example, the processor 102 may process the information in the memory 104 to generate first information / signals, and then transmit a radio signal including the first information / signals through the transceiver 106. The processor 102 may receive a radio signal including second information / signals through the transceiver 106, and then store information obtained by processing the second information / signals in the memory 104. The memory 104 may be connected 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 codes including commands for executing part or all of the processes controlled by the processor 102 or for executing the description, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document. Herein, the processor 102 and the memory 104 may be part of a communication modem / circuit / chip designed to implement a RAT (e.g., LTE or NR). The transceiver 106 may be connected to the processor 102 and transmit and / or receive radio signals through one or more antennas 108. Each transceiver 106 may include a transmitter and / or a receiver. The transceiver 106 may be used interchangeably with a radio frequency (RF) unit. In the present disclosure, a wireless device may represent a communication modem / circuit / chip.

[0383] The second wireless device 200 may include one or more processors 202 and one or more memories 204, and further include one or more transceivers 206 and / or one or more antennas 208. The processor 202 may control the memory 204 and / or the transceiver 206, and may be configured to implement the description, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document. For example, the processor 202 may process the information in the memory 204 to generate third information / signals, and then transmit a radio signal including the third information / signals through the transceiver 206. The processor 202 may receive a radio signal including fourth information / signals through the transceiver 206, and then store information obtained by processing the fourth information / signals in the memory 204. The memory 204 may be connected 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 codes including commands for executing part or all of the processes controlled by the processor 202 or for executing the description, functions, processes, proposals, methods, and / or operation flowcharts disclosed in this document. Herein, the processor 202 and the memory 204 may be part of a communication modem / circuit / chip designed to implement a RAT (e.g., LTE or NR). The transceiver 206 may be connected to the processor 202 and transmit and / or receive radio signals through one or more antennas 208. Each transceiver 206 may include a transmitter and / or a receiver. The transceiver 206 may be used interchangeably with an RF unit. In the present disclosure, a wireless device may represent a communication modem / circuit / chip.

[0384] In the following, the hardware elements of the wireless devices 100 and 200 will be described in more detail. One or more protocol layers may be implemented by (but not limited to) one or more processors 102 and 202. For example, one or more processors 102 and 202 may implement one or more layers (e.g., functional layers such as PHY, MAC, RLC, PDCP, RRC, and SDAP). One or more processors 102 and 202 may generate one or more protocol data units (PDUs) and / or one or more service data units (SDUs) according to the descriptions, functions, processes, proposals, methods, and / or operational flowcharts disclosed in this document. One or more processors 102 and 202 may generate messages, control information, data, or information according to the descriptions, functions, processes, proposals, methods, and / or operational flowcharts disclosed in this document. One or more processors 102 and 202 may generate a signal (e.g., a baseband signal) including a PDU, SDU, message, control information, data, or information according to the description, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this document, and provide the generated signal to one or more transceivers 106 and 206. One or more processors 102 and 202 may receive a signal (e.g., a baseband signal) from one or more transceivers 106 and 206 and obtain the PDU, SDU, message, control information, data, or information according to the description, functions, procedures, proposals, methods, and / or operational flowcharts disclosed in this document.

[0385] One or more processors 102 and 202 may be referred to as controllers, microcontrollers, microprocessors, or microcomputers. One or more processors 102 and 202 may be implemented by hardware, firmware, software, or a combination thereof. As an example, 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) may be included in one or more processors 102 and 202. The descriptions, functions, processes, proposals, methods, and / or operational flow charts disclosed in this document may be implemented using firmware or software, and the firmware or software may be configured to include modules, processes, or functions. Firmware or software configured to execute the descriptions, functions, processes, proposals, methods, and / or operational flow charts disclosed in this document may be included in one or more processors 102 and 202 or stored in one or more memories 104 and 204 to be driven by one or more processors 102 and 202. The descriptions, functions, processes, proposals, methods and / or operational flow charts disclosed in this document may be implemented in the form of codes, commands and / or command sets using firmware or software.

[0386] One or more memories 104 and 204 may be connected to one or more processors 102 and 202 and store various types of data, signals, messages, information, programs, codes, instructions and / or commands. One or more memories 104 and 204 may be configured by read-only memory (ROM), random access memory (RAM), electrically erasable programmable read-only memory (EPROM), flash memory, hard disk drive, register, cache memory, computer-readable storage medium and / or a combination thereof. One or more memories 104 and 204 may be located inside and / or outside of one or more processors 102 and 202. One or more memories 104 and 204 may be connected to one or more processors 102 and 202 by various technologies such as wired or wireless connections.

[0387] One or more transceivers 106 and 206 may send user data, control information and / or radio signals / channels mentioned in the method and / or operation flow chart of this document to one or more other devices. One or more transceivers 106 and 206 may receive user data, control information and / or radio signals / channels mentioned in the description, function, process, proposal, method and / or operation flow chart disclosed in this document from one or more other devices. For example, one or more transceivers 106 and 206 may be connected to one or more processors 102 and 202 and send and receive radio signals. For example, one or more processors 102 and 202 may perform control so that one or more transceivers 106 and 206 may send user data, control information or radio signals to one or more other devices. One or more processors 102 and 202 may perform control so that one or more transceivers 106 and 206 may receive user data, control information or radio signals from one or more other devices. One or more transceivers 106 and 206 may be connected to one or more antennas 108 and 208, and one or more transceivers 106 and 206 may be configured to send and receive user data, control information and / or radio signals / channels mentioned in the description, functions, processes, proposals, methods and / or operation flow charts disclosed in this document through one or more antennas 108 and 208. In this document, one or more antennas may be multiple physical antennas or multiple logical antennas (e.g., antenna ports). One or more transceivers 106 and 206 may convert received radio signals / channels, etc. from RF band signals to baseband signals so as to process received user data, control information, radio signals / channels, etc. using one or more processors 102 and 202. One or more transceivers 106 and 206 may convert user data, control information, radio signals / channels, etc. processed using one or more processors 102 and 202 from baseband signals to RF band signals. To this end, one or more of the transceivers 106 and 206 may include (analog) oscillators and / or filters.

[0388] Fig.15 is a diagram illustrating a DRX operation of a UE according to an embodiment of the present disclosure.

[0389] The UE may perform DRX operation in the process and / or method described / proposed above. A UE configured with DRX may reduce power consumption by discontinuously receiving DL signals. DRX may be performed in the RRC_IDLE state, the RRC_INACTIVE state, and the RRC_CONNECTED state. The UE performs DRX in the RRC_IDLE state and the RRC_INACTIVE state to discontinuously receive paging signals. DRX in the RRC_CONNECTED state (RRC_CONNECTED DRX) will be described below.

[0390] The DRX cycle includes an on-duration and a DRX opportunity. The DRX cycle defines the time interval between periodic repetitions of the on-duration. The on-duration is the time period during which the UE monitors the PDCCH. When the UE is configured with DRX, the UE performs PDCCH monitoring during the on-duration. When the UE successfully detects the PDCCH during the PDCCH monitoring period, the UE starts an inactivity timer and remains awake. On the contrary, when the UE fails to detect any PDCCH during the PDCCH monitoring period, the UE transitions to a sleep state after the on-duration. Therefore, when DRX is configured, PDCCH monitoring / reception may be performed discontinuously in the time domain in the process and / or method described / proposed above. For example, when DRX is configured, the PDCCH reception timing (e.g., a time slot with a PDCCH SS) may be configured discontinuously according to the DRX configuration in the present disclosure. On the contrary, when DRX is not configured, PDCCH monitoring / reception may be performed continuously in the time domain. For example, when DRX is not configured, the PDCCH reception timing (e.g., a time slot with a PDCCH SS) may be configured continuously in the present disclosure. Regardless of whether DRX is configured, PDCCH monitoring may be restricted during time periods configured as measurement gaps.

[0391] The above-mentioned embodiments are combinations of elements and features of the present disclosure in a specific form. Unless otherwise mentioned, these elements or features may be considered to be selective. Each element or feature may be implemented without being combined with other elements or features. In addition, the embodiments of the present disclosure may be configured by combining some elements and / or some features. The order of operations described in the embodiments of the present disclosure may be rearranged. Some structures or features of any one embodiment may be included in another embodiment, or may be replaced by the corresponding structures or features of another embodiment. It is obvious that claims that are not explicitly cited in the attached claims may be proposed as a combination of embodiments of the present disclosure, or may be included as new claims by subsequent amendments after submitting an application.

[0392] Those skilled in the art will appreciate that the present disclosure can be performed in other specific ways different from the ways set forth herein without departing from the spirit and essential characteristics of the present disclosure. Therefore, the above embodiments are interpreted in all respects as illustrative and not restrictive. The scope of the present disclosure should be determined by the appended claims and their legal equivalents, rather than by the above description, and all changes falling within the meaning and equivalent range of the appended claims should be included therein.

[0393] Industrial Applicability

[0394] The present disclosure is applicable to UE, BS or other devices in a wireless mobile communication system.

Claims

1. A method for receiving a signal by a user equipment UE in a wireless communication system, the method comprising: Receiving downlink control information DCI via a physical downlink control channel PDCCH; Determine the downlink resources allocated to the UE based on the frequency domain resource allocation FDRA field included in the DCI; as well as receiving a physical downlink shared channel (PDSCH) in the downlink resource, Wherein, based on the fact that a first bandwidth of the PDCCH supported by the UE is different from a second bandwidth of the PDSCH supported by the UE, the UE determines the downlink resource allocated through the FDRA field based on the second bandwidth instead of the first bandwidth.

2. The method according to claim 1, wherein: The second bandwidth is smaller than the first bandwidth.

3. The method according to claim 1, wherein: The first bandwidth is equal to or greater than 5 MHz, and the second bandwidth is equal to or less than 5 MHz.

4. The method according to claim 1, wherein: The frequency domain associated with the second bandwidth belongs to the first bandwidth part BWP; and The first BWP is shared with other UEs that support PDSCH reception with a bandwidth larger than the second bandwidth.

5. The method according to claim 4, wherein: The frequency domain associated with the second bandwidth is one of a plurality of sub-BWPs included in the first BWP.

6. The method according to claim 5, wherein: The DCI includes information for configuring one of the plurality of sub-BWPs included in the first BWP to be the frequency domain associated with the second bandwidth.

7. The method according to claim 1, wherein: The UE determines the downlink resources allocated through the FDRA field in a frequency domain associated with the second bandwidth.

8. The method according to claim 1, wherein: The total number of physical resource blocks (PRBs) and resource block groups (RBGs) related to the PDSCH is determined based on the second bandwidth. 9 . A processor-readable recording medium having recorded thereon a program for executing the method according to claim 1 .

10. An apparatus for wireless communication, the apparatus comprising: a memory configured to store instructions; as well as a processor configured to perform operations by executing the instructions, The operation of the processor includes: Receiving downlink control information DCI via a physical downlink control channel PDCCH; determining downlink resources allocated to the apparatus based on a frequency domain resource allocation FDRA field included in the DCI; and receiving a physical downlink shared channel (PDSCH) in the downlink resource, and Wherein, based on the fact that a first bandwidth supported by the device for the PDCCH is different from a second bandwidth supported by the device for the PDSCH, the processor determines the downlink resource allocated through the FDRA field based on the second bandwidth instead of the first bandwidth.

11. The device according to claim 10, further comprising: a transceiver configured to send and receive wireless signals under the control of the processor, The device is a user equipment UE used for wireless communication based on 3GPP.

12. The device according to claim 10, wherein: The device is an application specific integrated circuit ASIC or a digital signal processing device.

13. A method for sending a signal by a base station BS in a wireless communication system, the method comprising: Sending downlink control information DCI to user equipment UE via a physical downlink control channel PDCCH; as well as sending a physical downlink shared channel PDSCH in a downlink resource allocated to the UE based on a frequency domain resource allocation FDRA field included in the DCI, Wherein, based on the fact that a first bandwidth of the PDCCH supported by the UE is different from a second bandwidth of the PDSCH supported by the UE, the downlink resource allocated through the FDRA field is determined based on the second bandwidth instead of the first bandwidth.

14. A base station BS in a wireless communication system, the BS comprising: a memory configured to store instructions; as well as a processor configured to perform operations by executing the instructions, The operation of the processor includes: Sending downlink control information DCI to the user equipment UE via a physical downlink control channel PDCCH; and sending a physical downlink shared channel PDSCH in a downlink resource allocated to the UE based on a frequency domain resource allocation FDRA field included in the DCI, Wherein, based on the fact that a first bandwidth of the PDCCH supported by the UE is different from a second bandwidth of the PDSCH supported by the UE, the downlink resource allocated through the FDRA field is determined based on the second bandwidth instead of the first bandwidth.

Images