Apparatus and method for allocating frequency domain resources in wireless communication system

Abstract

The disclosure is to allocate frequency domain resources in a wireless communication system. A method of operating a terminal may comprise the steps of: receiving configuration information related to resource allocation; receiving control information related to resource allocation; identifying the allocated resource based on at least one of the configuration information and the control information; and transmitting or receiving a signal through the resource.

Description

Technical Field

[0001] The following description relates to a wireless communication system, and to an apparatus and method for allocating frequency domain resources in the wireless communication system. Background Art

[0002] Wireless communication systems have been widely deployed to provide various types of communication services, such as voice or data. Generally speaking, wireless communication systems are multiple access systems that support communication for multiple users by sharing available system resources (bandwidth, transmission power, etc.). Examples of multiple access systems include code division multiple access (CDMA) systems, frequency division multiple access (FDMA) systems, time division multiple access (TDMA) systems, orthogonal frequency division multiple access (OFDMA) systems, and single carrier frequency division multiple access (SC-FDMA) systems.

[0003] In particular, since a large number of communication devices require a large communication capacity, an enhanced mobile broadband (eMBB) communication technology is being proposed compared to a conventional radio access technology (RAT). In addition, not only a large-scale machine type communication (massive MTC) that provides various services anytime and anywhere by connecting multiple devices and objects is being proposed, but also a communication system that takes into account services / user terminal devices (UEs) that are sensitive to reliability and latency is being proposed. Various technical configurations are proposed for this purpose. Summary of the invention

[0004] Technical issues

[0005] The present disclosure may provide an apparatus and method for more efficiently allocating resources in a wireless communication system.

[0006] The present disclosure may provide an apparatus and method for efficiently representing allocation information of resources in the frequency domain in a wireless communication system.

[0007] The present disclosure may provide an apparatus and method for expressing resources allocated to a channel using a bandwidth of a limited size using a field designed for a wider bandwidth in a wireless communication system.

[0008] The present disclosure may provide an apparatus and method for optimizing a frequency domain resource allocation (FDRA) field for a channel having a narrow bandwidth in a wireless communication system.

[0009] The present disclosure may provide an apparatus and method for determining an RBG (Resource Block Group) size associated with an FDRA field in a wireless communication system.

[0010] The present disclosure may provide an apparatus and method for signaling information related to an RBG size applied to resource allocation in a wireless communication system.

[0011] The present disclosure may provide an apparatus and method for adaptively adjusting an RBG size corresponding to bits included in an FDRA field in a wireless communication system.

[0012] The present disclosure may provide an apparatus and method for imposing constraints on an FDRA field for resource allocation within a narrow bandwidth in a wireless communication system.

[0013] The present disclosure may provide an apparatus and method for performing transmission in a license-exempt band within a narrow bandwidth in a wireless communication system.

[0014] The present disclosure may provide an apparatus and method for performing frequency hopping considering a narrow bandwidth in a wireless communication system.

[0015] The technical objectives to be achieved in the present disclosure are not limited to the above contents, and a person skilled in the art in the field to which the technical configuration of the present disclosure is applied may consider other technical objectives not mentioned from the embodiments of the present disclosure to be described below.

[0016] Technical Solution

[0017] As an example of the present disclosure, a method for operating a terminal in a wireless communication system may include: receiving configuration information related to resource allocation, receiving control information related to resource allocation, identifying the allocated resources based on at least one of the configuration information or the control information, and sending or receiving a signal through the resources. The resources may be identified based on at least one table, the at least one table defining a plurality of resource block group (RBG) sizes by bandwidth part (BWP) size, and each of the plurality of BWP sizes may correspond to at least one RBG size value for allocation of a relatively wide bandwidth and at least one RBG size value for allocation of a relatively narrow bandwidth.

[0018] As an example of the present disclosure, a terminal in a wireless communication system may include a transceiver and a processor connected to the transceiver. The processor may receive configuration information related to resource allocation, receive control information related to resource allocation, identify the allocated resources based on at least one of the configuration information or the control information, and send or receive signals through the resources. The resources may be identified based on at least one table, the at least one table defining a plurality of resource block group (RBG) sizes by bandwidth part (BWP) size, and each of the plurality of BWP sizes may correspond to at least one RBG size value for allocation of a relatively wide bandwidth and at least one RBG size value for allocation of a relatively narrow bandwidth.

[0019] As an example of the present disclosure, a communication device may include at least one processor and at least one computer memory, the at least one computer memory being connected to the at least one processor and configured to store instructions that, when executed by the at least one processor, direct operations. These operations may include receiving control information related to resource allocation, identifying allocated resources based on at least one of configuration information or control information, and sending or receiving signals through resources. Resources may be identified based on at least one table that defines a plurality of resource block group (RBG) sizes by bandwidth part (BWP) size, and each of the plurality of BWP sizes may correspond to at least one RBG size value for allocation of a relatively wide bandwidth and at least one RBG size value for allocation of a relatively narrow bandwidth.

[0020] As an example of the present disclosure, a non-transitory computer-readable medium storing at least one instruction may include at least one instruction that can be executed by a processor. The at least one instruction may control a device to receive control information related to resource allocation, identify allocated resources based on at least one of configuration information or control information, and send or receive signals through resources. Resources may be identified based on at least one table, the at least one table defining multiple resource block group (RBG) sizes by bandwidth part (BWP) size, and each of the multiple BWP sizes may correspond to at least one RBG size value for allocation of a relatively wide bandwidth and at least one RBG size value for allocation of a relatively narrow bandwidth.

[0021] The above-mentioned aspects of the present disclosure are only a part of exemplary embodiments of the present disclosure, and those skilled in the art can derive and understand various embodiments reflecting the technical features of the present disclosure based on the following detailed description of the present disclosure.

[0022] Beneficial Effects

[0023] As is apparent from the above description, the embodiments of the present disclosure have the following effects.

[0024] According to the present disclosure, hardware cost can be reduced by saving buffers.

[0025] Those skilled in the art will appreciate that the effects that can be achieved by the embodiments of the present disclosure are not limited to the above effects, and other beneficial effects of the present disclosure will be more clearly understood from the following detailed description. That is, those skilled in the art can derive unexpected effects according to the embodiments of the present disclosure from the embodiments of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] The accompanying drawings are provided to help understand the present disclosure, and may provide embodiments of the present disclosure together with the detailed description. However, the technical features of the present disclosure are not limited to specific drawings, and the features disclosed in each drawing may be combined with each other to form new embodiments. The reference numerals in each drawing may refer to structural elements.

[0027] Figure 1 An example of a structure of a wireless communication system to which the present disclosure can be applied is illustrated.

[0028] Figure 2 An example of a wireless device applicable to the present disclosure is illustrated.

[0029] Figure 3 A frame structure in a wireless communication system to which the present disclosure can be applied is illustrated.

[0030] Figure 4 An example of a resource grid in a wireless communication system to which the present disclosure may be applied is illustrated.

[0031] Figure 5 An example of a physical resource block in a wireless communication system to which the present disclosure can be applied is illustrated.

[0032] Figure 6 An example of a time slot structure in a wireless communication system to which the present disclosure can be applied is illustrated.

[0033] Figure 7 An example of a physical channel used in a wireless communication system to which the present disclosure can be applied and an example of a general signal transmission and reception method using the physical channel are illustrated.

[0034] Figure 8 An example of PRB (Physical Resource Block) allocation per RBG (Resource Block Group) according to RA (Resource Allocation) type 0 applicable to the present disclosure is illustrated.

[0035] Fig. 9 An example of PRB allocation according to RA type 1 applicable to the present disclosure is illustrated.

[0036] Fig.10 An example of frequency hopping applicable to the present disclosure is illustrated.

[0037] Fig.11 An example of a process of transmitting or receiving data in a wireless communication system according to an embodiment of the present disclosure is illustrated.

[0038] Fig.12 An example of a process of performing communication based on an adjusted RBG size in a wireless communication system according to an embodiment of the present disclosure is illustrated.

[0039] Fig.13An example of a process of processing a data signal based on a limited bandwidth in a wireless communication system according to an embodiment of the present disclosure is illustrated.

[0040] Fig.14 An example of a process of applying multiple RBG sizes to a frequency domain resource allocation (FDRA) field in a wireless communication system according to an embodiment of the present disclosure is illustrated.

[0041] Fig.15a and Fig.15b An example of interleaved transmission applicable to the present disclosure is illustrated. DETAILED DESCRIPTION

[0042] The embodiments of the present disclosure described below are combinations of elements and features of the present disclosure in a particular form. Unless otherwise mentioned, elements or features may be considered to be selective. Each element or feature may be put into practice without being combined with other elements or features. In addition, embodiments of the present disclosure may be constructed by combining some elements and / or features. The order of operations described in the embodiments of the present disclosure may be rearranged. Some structures or elements of any one embodiment may be included in another embodiment and may be replaced with the corresponding structures or features of another embodiment.

[0043] In the description of the drawings, processes or steps that render the scope of the present disclosure unnecessarily ambiguous will be omitted, and processes or steps that can be understood by those skilled in the art will be omitted.

[0044] Throughout the specification, when a part "includes" or "comprises" a component, this indicates that other components are not excluded and may further be included, unless otherwise specified. The terms "unit", "-or / er" and "module" described in this specification indicate a unit for processing at least one function or operation, which can be implemented by hardware, software or a combination thereof. In addition, "a" or "an", "one", "the", etc. in the context of the present disclosure (more specifically, in the context of the appended claims) may include singular and plural expressions, unless otherwise specified in the specification or unless the context clearly indicates otherwise.

[0045] In the embodiments of the present disclosure, the data transmission and reception relationship between the base station (BS) and the mobile station is mainly described. The BS refers to the terminal node of the network, which directly communicates with the mobile station. The specific operation described as being performed by the BS can be performed by the upper node of the BS.

[0046] That is, it is apparent that in a network composed of a plurality of network nodes including a BS, various operations performed for communication with a mobile station may be performed by the BS or network nodes other than the BS. The term "BS" may be replaced with a fixed station, a Node B, an evolved Node B (eNode B or eNB), an advanced base station (ABS), an access point, etc.

[0047] In an embodiment of the present disclosure, the term terminal may be replaced with UE, mobile station (MS), subscriber station (SS), mobile subscriber station (MSS), mobile terminal, advanced mobile station (AMS), etc.

[0048] The transmitter is a fixed and / or mobile node that provides data services or voice services, and the receiver is a fixed and / or mobile node that receives data services or voice services. Therefore, on the uplink (UL), the mobile station can act as a transmitter and the BS can act as a receiver. Similarly, on the downlink (DL), the mobile station can act as a receiver and the BS can act as a transmitter.

[0049] The embodiments of the present disclosure may be supported by at least one of the standard specifications disclosed for wireless access systems including the Institute of Electrical and Electronics Engineers (IEEE) 802.xx system, the 3rd Generation Partnership Project (3GPP) system, the 3GPP Long Term Evolution (LTE) system, the 3GPP Fifth Generation (5G) New Radio (NR) system, and the 3GPP2 system. Specifically, the embodiments of the present disclosure may be supported by the standard specifications 3GPP TS 36.211, 3GPP TS 36.212, 3GPP TS 36.213, 3GPP TS36.321, and 3GPP TS 36.331.

[0050] In addition, the embodiments of the present disclosure are applicable to other radio access systems and are not limited to the above-mentioned systems. For example, the embodiments of the present invention are applicable to systems applied after the 3GPP 5G NR system and are not limited to a specific system.

[0051] That is, steps or parts that are not described to clarify the technical features of the present disclosure may be supported by those documents. In addition, all terms as proposed herein may be interpreted by standard documents.

[0052] Embodiments of the present disclosure will now be described in detail with reference to the accompanying drawings. The detailed description given below with reference to the accompanying drawings is intended to explain exemplary embodiments of the present disclosure, rather than to show the only embodiments that can be implemented according to the present disclosure.

[0053] The following detailed description includes specific terms in order to provide a thorough understanding of the present disclosure. However, it is obvious to those skilled in the art that other terms may be used to replace specific terms without departing from the technical spirit and scope of the present disclosure.

[0054] The embodiments of the present disclosure can be applied to various radio access systems such as code division multiple access (CDMA), frequency division multiple access (FDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), single carrier frequency division multiple access (SC-FDMA), etc.

[0055] Hereinafter, in order to clarify the following description, the description is based on the 3GPP communication system (e.g., LTE, NR, etc.), but the technical spirit of the present disclosure is not limited thereto. LTE may refer to the technology after 3GPP TS 36.xxx version 8. Specifically, the LTE technology after 3GPP TS 36.xxx version 10 may be referred to as LTE-A, and the LTE technology after 3GPP TS 36.xxx version 13 may be referred to as pre-LTE-A. 3GPP NR may refer to the technology after TS 38.xxx version 15. 3GPP 6G may refer to the technology after TS version 17 and / or version 18. "xxx" may refer to the detailed number of the standard document. LTE / NR / 6G may be collectively referred to as the 3GPP system.

[0056] 3GPP 6G may refer to post-3GPP NR technology based on the 3GPP system. 3GPP 6G may not be limited to a version or a specific TS document, and its name may have a different form from 3GPP 6G. That is, 3GPP 6G may refer to a technology introduced after 3GPP NR, and is not limited to a specific form.

[0057] The following description will mainly focus on the 3GPP NR system, but is not limited thereto, and can be applied to 3GPP 6G. In addition, the content described below may be partially modified to be used in consideration of the 3GPP 6G system, and is not limited to a specific form. However, in the following, for ease of explanation, the 3GPP NR system will be mainly described. For the background technology, terms, abbreviations, etc. used in this disclosure, please refer to the matters described in the standard documents published before this disclosure. For example, standard documents 36.xxx and 38.xxx may be referenced.

[0058] Overall system

[0059] As more and more communication devices require greater communication capacity, the demand for mobile broadband communications that are more enhanced than existing radio access technologies (RATs) is rising. In addition, large-scale machine type communications (MTC) that provide various services anytime and anywhere by connecting multiple devices and things is also one of the main issues worth considering in next-generation communications. In addition, the design of communication systems that consider services / terminals that are sensitive to reliability and latency is also under discussion. Therefore, the introduction of next-generation RATs that consider enhanced mobile broadband communications (eMBB), massive MTC (mMTC), ultra-reliable low-latency communications (URLLC), etc. is under discussion, and for convenience, the corresponding technology is referred to as NR in this disclosure. NR is a representation of an example representing a 5G RAT.

[0060] The new RAT system including NR uses an OFDM transmission method or a similar transmission method. The new RAT system may follow OFDM parameters different from those of LTE. Alternatively, the new RAT system may follow the parameter set of the existing LTE / LTE-A as is, but support a wider system bandwidth (e.g., 100MHz). Alternatively, a cell may support multiple parameter sets. In other words, terminals operating according to different parameter sets may coexist in one cell.

[0061] A parameter set corresponds to one subcarrier spacing in the frequency domain. Because the reference subcarrier spacing is scaled by an integer N, different parameter sets can be defined.

[0062] In addition, new RAT systems including 6G may be considered as next generation RATs. New RAT systems including 6G may consider i) very high data speeds per device, ii) a large number of connected devices, iii) global connectivity, iv) very low latency, v) reduced energy consumption of battery-free IoT devices, vi) ultra-high reliability connectivity, and vii) connectivity intelligence with machine learning capabilities, but are not limited thereto. In view of the above, new RAT systems including 6G may consider using the terahertz (THz) band, i.e., a frequency higher than the NR system, for wider bandwidth and higher transmission speeds. RAT systems including 6G may overcome existing limitations by applying artificial intelligence / machine learning (AI / ML), but may not be limited thereto.

[0063] Figure 1 The structure of a wireless communication system to which the present disclosure can be applied is illustrated. Figure 1, NG-RAN consists of gNBs that provide control plane (RRC) protocol terminations for the NG-Radio Access (NG-RA) user plane (i.e., new access stratum (AS) sublayer / packet data convergence protocol (PDCP) / radio link control (RLC) / MAC / PHY) and UE. The gNBs are interconnected through the Xn interface. In addition, the gNBs are connected to the new generation core (NGC) through the N2 interface. More specifically, the gNB is connected to the access and mobility management function (AMF) through the N2 interface and to the user plane function (UPF) through the N3 interface. Figure 1 It can be based on the structure of the NR system. Figure 1 The structure can be used in the 6G system as it is or by being partially modified, and is not limited to a specific form.

[0064] Figure 2 An example of a wireless device applicable to the present disclosure is illustrated.

[0065] Reference Figure 2 The wireless device 200 may send / receive radio signals via various wireless access technologies (e.g., LTE, LTE-A, pre-LTE-A, NR, 5G, 5G-A, 6G). The wireless device 200 may include at least one processor 202 and at least one memory 204, and may further include at least one transceiver 206 and / or at least one antenna 208.

[0066] The processor 202 may be configured to control the memory 204 and / or the transceiver 206 and implement the description, function, process, proposal, method and / or operation flow chart disclosed in this document. For example, the processor 202 may generate a first information / signal by processing the information in the memory 204, and then send a radio signal including the first information / signal through the transceiver 206. In addition, the processor 202 may receive a radio signal including a second information / signal through the transceiver 206, and then store information obtained from the signal processing of the second information / signal in the memory 204. The memory 204 may be connected to the processor 202 and store various information associated with the operation of the processor 202. For example, the memory 204 may store software code including instructions for implementing part or all of the processes controlled by the processor 202 or for implementing the description, function, process, proposal, method and / or operation flow chart disclosed in this document. Here, the processor 202 and the memory 204 may be part of a communication modem / circuit / chip designed to implement wireless communication technology. The transceiver 206 may be connected to the processor 202 and transmit and / or receive radio signals through at least one antenna 208. The transceiver 206 may be a transmitter and / or a receiver. The transceiver 206 may be used interchangeably with a radio frequency (RF) unit. In the present disclosure, a wireless device may refer to a communication modem / circuit / chip.

[0067] Hereinafter, the hardware elements of the wireless device 200 will be described in further detail. Although not limited thereto, at least one processor 202 may implement at least one protocol layer (e.g., functional layers such as physical (PHY), medium access control (MAC), radio link control (RLC), packet data convergence protocol (PDCP), radio resource control (RRC), and service data adaptation protocol (SDAP)). At least one processor 202 may generate at least one protocol data unit (PDU) and / or at least one service data unit (SDU) according to the description, function, process, proposal, method, and / or operation flow chart disclosed in this document. At least one processor 202 may generate a message, control information, data, or information according to the description, function, process, proposal, method, and / or operation flow chart disclosed in this document. At least one processor 202 may generate a signal (e.g., a baseband signal) including a PDU, SDU, message, control information, data, or information according to the function, process, proposal, and / or method disclosed in this document, and provide the signal to at least one transceiver 206. At least one processor 202 can receive a signal (e.g., a baseband signal) from at least one transceiver 206 and obtain PDUs, SDUs, messages, control information, data, or information according to the descriptions, functions, processes, proposals, methods, and / or operational flow charts disclosed in this document.

[0068] At least one processor 202 may be referred to as a controller, a microcontroller, a microprocessor, or a microcomputer. At least one processor 202 may be implemented by hardware, firmware, software, or a combination thereof. As an example, at least one application specific integrated circuit (ASIC), at least one digital signal processor (DSP), at least one digital signal processing device (DSPD), at least one programmable logic device (PLD), or at least one field programmable gate array (FPGA) may be included in at least one processor 202. The description, functions, processes, proposals, methods, and / or operational flowcharts disclosed in this document may be implemented using firmware or software, and the firmware or software may be implemented to include modules, processes, or functions. Firmware or software configured to execute the description, functions, processes, proposals, methods, and / or operational flowcharts disclosed in this document may be included in at least one processor 202, or may be stored in at least one memory 204 and executed by at least one processor 202. The description, functions, processes, proposals, methods, and / or operational flowcharts disclosed in this document may be implemented using firmware or software in the form of code, instructions, and / or instruction sets.

[0069] At least one memory 204 may be connected to at least one processor 202 and store various forms of data, signals, messages, information, programs, codes, instructions, and / or instructions. At least one memory 204 may be configured as a read-only memory (ROM), a random access memory (RAM), an erasable programmable read-only memory (EPROM), a flash memory, a hard disk, a register, a cache memory, a computer-readable storage medium, and / or a combination thereof. At least one memory 204 may be located inside and / or outside of at least one processor 202. In addition, at least one memory 204 may be connected to at least one processor 202 via various technologies such as a wired or wireless connection.

[0070] At least one transceiver 206 can send user data, control information, and wireless signals / channels mentioned in the method and / or operation flow chart of this document to at least one other device. At least one transceiver 206 can receive user data, control information, and wireless signals / channels mentioned in the description, function, process, proposal, method, and / or operation flow chart disclosed in this document from at least one other device. For example, at least one transceiver 206 can be connected to at least one processor 202 and send and receive radio signals. For example, at least one processor 202 can control at least one transceiver 206 to send user data, control information, or radio signals to at least one other device. In addition, at least one processor 202 can control at least one transceiver 206 to receive user data, control information, or radio signals from at least one other device. In addition, at least one transceiver 206 can be connected to at least one antenna 208, and at least one transceiver 206 can be configured to send and receive user data, control information, and radio signals / channels mentioned in the description, function, process, proposal, method, and / or operation flow chart disclosed in this document through at least one antenna 208. In this document, at least one antenna may be a plurality of physical antennas or a plurality of logical antennas (e.g., antenna ports). At least one transceiver 206 may convert received radio signals / channels from RF band signals to baseband signals in order to facilitate processing of received user data, control information, and radio signals / channels using at least one processor 202. At least one transceiver 206 may convert user data, control information, and radio signals / channels processed using at least one processor 202 from baseband signals to RF band signals. To this end, at least one transceiver 206 may include an (analog) oscillator and / or a filter.

[0071] Reference Figure 2 The components of the described wireless device may be referred to by other terms from the functional aspect. For example, the processor 202 may be referred to as a control unit, the transceiver 206 may be referred to as a communication unit, and the memory 204 may be referred to as a storage unit. In some cases, the communication unit may be used to mean at least a part of the processor 202 and the transceiver 206.

[0072] Reference Figure 2 The structure of the wireless device described may be understood as the structure of at least a portion of various devices. As an example, the structure may be at least a portion of various devices (e.g., a robot, a vehicle, an XR device, a handheld device, a home appliance, an IoT device, an AI device / server, etc.). In addition, according to various embodiments, in addition to Figure 2 In addition to the components illustrated in the figure, the device may further include other components.

[0073] For example, the device may be a handheld device such as a smart phone, a smart tablet, a wearable device (e.g., a smart watch, smart glasses), and a handheld computer (e.g., a laptop computer, etc.). In this case, the device may further include at least one of: a power supply unit that supplies power and includes a wired / wireless charging circuit, a battery, etc.; an interface unit that includes at least one port for connecting to another device (e.g., an audio input / output port, a video input / output port); and an input / output unit for inputting and outputting video information / signals, audio information / signals, data, and / or information input from a user.

[0074] For example, the device may be a mobile device such as a mobile robot, a vehicle, a train, a manned / unmanned aerial vehicle (AV), and a ship. In this case, the device may further include at least one of the following: a drive unit including at least one of an engine, a motor, a power train, wheels, brakes, and a steering device of the device; a power supply unit that supplies power and includes a wired / wireless charging circuit, a battery, etc.; a sensor unit that senses state information, environmental information, and user information of the device or the surroundings of the device; an automatic driving unit that performs functions such as route maintenance, speed control, and destination setting; and a position measurement unit that obtains mobile object position information through a global positioning system (GPS) and various sensors.

[0075] For example, the device may be an XR device such as an HMD, a head-up display (HUD) provided in a vehicle, a TV, a smartphone, a wearable device, a home appliance device, a digital signage, a vehicle, and a robot. In this case, the device may further include at least one of: a power supply unit that supplies power and includes a wired / wireless charging circuit, a battery, etc.; an input / output unit that obtains control information and data from the outside and outputs a generated XR object; and a sensor unit that senses state information, environmental information, and user information of the device or the surroundings of the device.

[0076] For example, the device may be a robot, which may be classified according to the purpose or field of use as industrial use, medical use, home use, military use, etc. In this case, the device may further include at least one of: a sensor unit that senses state information, environmental information, and user information of the device or the surroundings of the device; and a drive unit that moves robot joints and performs various other physical operations.

[0077] For example, the device may be an AI device such as a TV, a projector, a smartphone, a PC, a laptop, a digital broadcast terminal, a tablet, a wearable device, a set-top box (STB), a radio, a washing machine, a refrigerator, a digital signage, a robot, and a vehicle. In this case, the device may further include at least one of: an input unit that obtains various types of data from the outside; an output unit that generates an output associated with vision, hearing, or touch; a sensor unit that senses state information, environmental information, and user information of the device or the surroundings of the device; and a training unit that uses learning data to learn a model composed of an artificial neural network. Figure 2 The structure of the wireless device illustrated in the example can be understood as a part of a RAN node (eg, a base station, a DU, a RU, a RRH, etc.). That is, Figure 2 The device illustrated in the example may be a RAN node. In this case, the device may further include a wired transceiver for fronthaul and / or backhaul communication. However, in the case where the fronthaul and / or backhaul communication is based on wireless communication, Figure 2 The at least one transceiver 206 illustrated in FIG. 2 may be used for fronthaul and / or backhaul communications and may not include a wired transceiver.

[0078] Figure 3 A frame structure in a wireless communication system to which the present disclosure can be applied is illustrated.

[0079] The NR system may support multiple parameter sets. Here, the parameter set may be defined by a subcarrier spacing and a cyclic prefix (CP) overhead. Here, multiple subcarrier spacings may be derived by scaling the default (reference) subcarrier spacing by an integer N (or μ). In addition, although it is assumed that very low subcarrier spacing is not used in very high carrier frequencies, the parameter set used herein may be selected independently of the frequency band. In addition, various frame structures according to multiple parameter sets may be supported in the NR system.

[0080] In the following, OFDM parameter sets and frame structures that can be considered in the NR system will be described. The various OFDM parameter sets supported in the NR system can be defined as shown in Table 1 below.

[0081] [Table 1]

[0082] μ <![CDATA[Δf=2 μ ·15[kHz]]]> CP 0 15 normal 1 30 normal 2 60 Normal, Extended 3 120 normal 4 240 normal

[0083] NR supports multiple parameter sets (or subcarrier spacing (SCS)) to support various 5G services. For example, when the SCS is 15kHz, a wide area of ​​the traditional cellular band is supported, and when the SCS is 30kHz / 60kHz, dense urban areas, lower latency and wider carrier bandwidth are supported, and when the SCS is 60kHz or higher, bandwidth greater than 24.25GHz is supported to overcome phase noise.

[0084] The NR frequency band is defined as two types of frequency ranges (FR1, FR2). FR1 and FR2 can be configured as shown in Table 2 below. In addition, FR2 may mean millimeter wave (mmW).

[0085] [Table 2]

[0086] Frequency range specification Corresponding frequency range Subcarrier spacing FR1 410MHz-7125MHz 15, 30, 60kHz FR2 24250MHz-52600MHz 60, 120, 240kHz

[0087] Regarding the frame structure in the NR system, the sizes of various fields in the time domain are expressed in T c =1 / (Δf max ·N f ) is expressed in multiples of the time unit. Here, Δf max 480·10 3 Hz, and N f is 4096. Downlink and uplink transmissions are configured (organized) with T f =1 / (Δf max ·N f / 100)T c =10ms duration radio frame. Here, the radio frames are respectively configured with T sf =(Δf max ·N f / 1000)T c =10 subframes of duration of 1ms. In this case, there is one set of frames for uplink and one set of subframes for downlink. In addition, the transmission in uplink frame number i from the terminal should start T earlier than the corresponding downlink frame in the corresponding terminal. TA =(N TA +N TA，offset )T c For the subcarrier spacing configuration μ, the time slots in the subframe are The time slots in a radio frame are numbered in ascending order of A time slot is configured with A continuous OFDM symbol configuration is determined based on the CP Time slot in subframe The start time is the same as the OFDM symbol in the same subframe It is impossible for all terminals to perform transmission and reception at the same time, which means that not all OFDM symbols of a downlink time slot or an uplink time slot are available.

[0088] [Table 3] shows the number of OFDM symbols per time slot in a normal CP Number of time slots per radio frame and the number of time slots per subframe And Table 4 represents the number of OFDM symbols per slot, the number of slots per radio frame, and the number of slots per subframe in the extended CP.

[0089] [Table 3]

[0090]

[0091] [Table 4]

[0092]

[0093] Figure 3 This is an example about μ=2 (SCS is 60 kHz), and referring to Table 3, 1 subframe may include 4 slots. Figure 3 1 subframe = {1, 2, 4} slots shown in is an example, and the number of slots that may be included in 1 subframe is as defined in Table 3 or Table 4. In addition, a mini-slot may include 2, 4, or 7 symbols or more or less.

[0094] Regarding the physical resources in the NR system, antenna ports, resource grids, resource elements, resource blocks, carrier parts, etc. can be considered. Hereinafter, the physical resources that can be considered in the NR system will be described in detail.

[0095] First, with respect to antenna ports, the antenna ports are defined so that the channel carrying the symbol in the antenna port can be inferred from the channel carrying another symbol in the same antenna port. When the large-scale characteristics of the channel carrying the symbol in one antenna port can be inferred from the channel carrying the symbol in another antenna port, the two antenna ports can be said to be in a quasi-co-location or quasi-co-location (QC / QCL) relationship. In this case, the large-scale characteristics include one or more of delay spread, Doppler spread, frequency offset, average received power, and receive timing.

[0096] In the 6G system, communication can be performed at the above-mentioned THz frequency band higher than the millimeter wave (mmW) frequency, and the same Figure 3 The same frame structure as shown, or a separate frame structure for the 6G system may be used, but is not limited to a specific form.

[0097] Figure 4 A resource grid in a wireless communication system to which the present disclosure may be applied is illustrated.

[0098] Reference Figure 4 , as an illustrative description, the resource grid is configured in the frequency domain with subcarriers, and one subframe is configured with 14·2 μ OFDM symbols, but the resource grid and subframe are not limited to this. In the NR system, the transmitted signal consists of OFDM symbols and One or more resource grids for each subcarrier. Here, represents the maximum transmission bandwidth, which may differ between uplink and downlink and between parameter sets. In this case, one resource grid can be configured for each μ and antenna port p. Each element of the resource grid for μ and antenna port p is called a resource element and is uniquely identified by an index pair (k, l'). Here, is an index in the frequency domain, and refers to the position of a symbol in a subframe. When referring to a resource element in a slot, an index pair (k, l) is used. Here, The resource element (k, l') for μ and antenna port p corresponds to the complex value When there is no risk of confusion or no specific antenna port or parameter set is specified, the indices p and μ can be discarded and the complex value can be or a k，l′ In addition, a resource block (RB) is defined as consecutive subcarriers.

[0099] Point A plays the role of a common reference point for the resource block grid and is obtained as follows.

[0100] -OffsetToPointA for the primary cell (PCell) downlink represents the frequency offset between point A and the lowest subcarrier of the lowest resource block overlapping the SS / PBCH block used by the terminal for initial cell selection. It is expressed in resource blocks, assuming a subcarrier spacing of 15kHz for FR1 and 60kHz for FR2.

[0101] -absoluteFrequencyPointA represents the frequency position of point A, as expressed in absolute radio frequency channel number (ARFCN).

[0102] For subcarrier spacing configuration μ, the common resource blocks are numbered from 0 upwards in the frequency domain. The center of subcarrier 0 of common resource block 0 for subcarrier spacing configuration μ is the same as "point A". Number of common resource blocks for subcarrier spacing configuration μ in the frequency domain The relationship between and resource element (k, l) is given in Equation 1 below.

[0103] [Equation 1]

[0104]

[0105] In Equation 1, k is defined relative to point A, so that k=0 corresponds to a subcarrier centered at point A. Physical resource blocks are spaced from 0 to 1 in a bandwidth part (BWP). where i is the number of the BWP. Physical resource block n in BWP i PRB and public resource block n CRB The relationship between is given by the following equation 2.

[0106] [Equation 2]

[0107]

[0108] is the common resource block where the BWP starts relative to common resource block 0.

[0109] Figure 5 The physical resource blocks in the wireless communication system to which the present disclosure can be applied are illustrated. Figure 6 The following illustrates a time slot structure in a wireless communication system to which the present disclosure can be applied.

[0110] Reference Figure 5 and Figure 6 , a slot includes a plurality of symbols in the time domain. For example, for a normal CP, a slot includes 7 symbols, but for an extended CP, a slot includes 6 symbols.

[0111] A carrier includes multiple subcarriers in the frequency domain. A resource block (RB) is defined as multiple (e.g., 12) consecutive subcarriers in the frequency domain. A bandwidth part (BWP) is defined as multiple consecutive (physical) resource blocks in the frequency domain and may correspond to a parameter set (e.g., SCS, CP length, etc.). A carrier may include up to N (e.g., 5) BWPs. Data communication may be performed through an activated BWP, and only one BWP may be activated for one terminal. In a resource grid, each element is called a resource element (RE) and may map a complex symbol.

[0112] In the NR system, each component carrier (CC) can support up to 400MHz. If the terminal working in such a wideband CC always operates with the radio frequency (FR) chip for the entire CC turned on, the terminal battery consumption may increase. Alternatively, when considering several application scenarios operating in a wideband CC (e.g., eMBB, URLLC, Mmtc, V2X, etc.), different parameter sets (e.g., subcarrier spacing, etc.) can be supported in each frequency band in the corresponding CC. Alternatively, each terminal may have a different maximum bandwidth capability. In this regard, the base station may instruct the terminal to operate only in part of the bandwidth instead of the total bandwidth of the wideband CC, and for convenience, the corresponding part of the bandwidth is defined as a bandwidth part (BWP). BWP can be configured with continuous RBs on the frequency axis and may correspond to a parameter set (e.g., subcarrier spacing, CP length, slot / microslot duration).

[0113] At the same time, even in one CC configured for the terminal, the base station can configure multiple BWPs. For example, a BWP occupying a relatively small frequency domain can be configured in the PDCCH monitoring time slot, and the PDSCH indicated by the PDCCH can be scheduled in a larger BWP. Alternatively, when the UE is congested in a specific BWP, some terminals can be configured with another BWP for load balancing. Alternatively, considering the frequency domain inter-cell interference elimination between adjacent cells, etc., some middle spectrums of the entire bandwidth can be excluded, and the BWPs on two edges can be configured in the same time slot. In other words, the base station can configure at least one DL / UL BWP for a terminal associated with a broadband CC. The base station can activate at least one DL / UL BWP in the configured DL / UL BWP at a specific time (through L1 signaling or MAC control unit (CE) or RRC signaling, etc.). In addition, the base station can indicate switching to another configured DL / UL BWP (through L1 signaling or MAC CE or RRC signaling, etc.). Alternatively, based on a timer, when the timer value expires, it can switch to the determined DL / UL BWP. Here, the activated DL / UL BWP is defined as the active DL / UL BWP. However, when the terminal performs the initial access process or has not yet established an RRC connection, the configuration of the DL / UL BWP may not be received, so the DL / UL BWP assumed by the terminal in this case is defined as the initial active DL / UL BWP.

[0114] Figure 7 A physical channel used in a wireless communication system to which the present disclosure may be applied and a general signal transmission and reception method using the physical channel are illustrated.

[0115] In a wireless communication system, a terminal receives information from a base station via a downlink, and a terminal sends information to a base station via an uplink. The information sent and received by the base station and the terminal includes data and various control information, and there are various physical channels according to the type / purpose of the information they send and receive.

[0116] When the terminal is turned on or newly enters a cell, the terminal performs an initial cell search, which includes synchronization with a base station (S701). To this end, the terminal can synchronize with the base station by receiving a primary synchronization signal (PSS) and a secondary synchronization signal (SSS) from the base station, and obtain information such as a cell identifier (ID). Next, the terminal can obtain broadcast information in the cell by receiving a physical broadcast channel (PBCH) from the base station. At the same time, the terminal can check the downlink channel state by receiving a downlink reference signal (DL RS) in the initial cell search step.

[0117] The terminal that has completed the initial cell search can obtain more detailed system information by receiving a physical downlink control channel (PDCCH) and a physical downlink shared channel (PDSCH) according to information carried in the PDCCH (S702).

[0118] Meanwhile, if the terminal accesses the base station for the first time or does not have radio resources for signal transmission, the terminal may perform a random access procedure (RACH) on the base station (S703 to S706). To this end, the terminal may send a specific sequence as a preamble through a physical random access channel (PRACH) (S703 and S705), and receive a response message to the preamble through a PDCCH and a corresponding PDSCH (S704 and S706). In the case of a contention-based RACH, a contention resolution process may be additionally performed.

[0119] The terminal that has performed the above process may then perform PDCCH / PDSCH reception (S707) and physical uplink shared channel (PUSCH) / physical uplink control channel (PUCCH) transmission (S708) as a general uplink / downlink signal transmission process. Specifically, the terminal receives downlink control information (DCI) through PDCCH. Here, DCI includes control information such as resource allocation information for the terminal, and has different formats depending on its purpose of use.

[0120] At the same time, the control information sent by the terminal to the base station through the uplink or received by the terminal from the base station includes downlink / uplink confirmation / non-confirmation (ACK / NACK) signal, channel quality indicator (CQI), precoding matrix indicator (PMI), rank indicator (RI), etc. For the 3GPP LTE system, the terminal can send the above-mentioned CQI / PMI / RI and other control information through PUSCH and / or PUCCH.

[0121] Specific embodiments of the present disclosure

[0122] The present disclosure relates to the allocation of frequency domain resources in a wireless communication system, and more particularly, to a technology for allocating resources to a channel using a limited bandwidth and indicating the allocated resources. Specifically, the present disclosure proposes various embodiments for indicating the allocated resources of a channel with a narrow bandwidth using a frequency domain resource allocation (FDRA) field designed based on a relatively wider bandwidth.

[0123] 5G NR is a technology that provides services mainly through three major technologies: eMBB (enhanced mobile broadband), URLLC, and mIoT (massive Internet of Things). In terms of mIoT, it can be regarded as a terminal device form that optimizes power consumption based on small size and low power, rather than a technical direction such as CA (carrier aggregation) that requires high-performance maximum throughput (max T-put) speed transmission. Then, in 5G NR, there are not only three major technologies of URLLC, eMBB, and mIoT, but also a hybrid form of these three technologies. In 3GPP Release-17, in order to meet smart factory applications or wearable devices to a certain extent, a new type of device that requires low power consumption while requiring URLLC or a certain level of speed may be required. This type of device is called a reduced capability terminal, that is, Redcap (reduced capability) UE or Redcap terminal.

[0124] For frequency resources, Redcap UE uses a narrow spectrum or bandwidth (BW) that is different from the existing one. Specifically, Redcap UE uses a maximum of 20MHz or 5MHz BW instead of the existing 100MHz BW, in which case power consumption and cost savings may be achieved. The present disclosure proposes a technology for setting and operating only a PxSCH channel with a 5MHz BW in a Redcap terminal using a 20MHz BW in 3GPP Release 17. The UE according to the proposed technology can be understood as a new type of Redcap based on simple changes rather than many changes (compared to the existing Redcap using a 20MHz BW). In this case, the PxSCH channel needs to be optimized, and various implementations will be described at this time so that the allocation of the PxSCH channel can operate with only a 5MHz BW and the corresponding T-put.

[0125] The present disclosure relates to a terminal using a narrow bandwidth, and proposes a technique for using only a maximum of 5MHz BWP for a PxSCH channel in a terminal using a maximum of 20MHz BWP, instead of using a maximum of 100MHz BWP as the overall channel BW used by a general device. In this case, from the perspective of the existing L1, the control channels (e.g., PDCCH, PUCCH, SRS, PRACH) may not change, and in order to reduce the T-put or buffer of the PDSCH of the downlink and the PUSCH of the uplink, the BW or BWP will be maintained at a maximum of 5MHz.

[0126] For this purpose, although the base station can allocate 5MHz resources using FDRA, a method of presetting a range of consecutive RBs in a form similar to BWP and allocating PxSCH (e.g., PDSCH, PUSCH) within the range can be considered. In this case, rules are required for how the FDRA indicating PxSCH will be indicated within a new set of consecutive RBs, and specifically, a method for frequency hopping, the starting number of RBs, and the RB BW indicating the size is required. In addition, an alternative solution is also needed to solve the problem that when allocating PxSCH within 5MHz, by indicating the RB start and RB BW while following the existing allocation method of FDRA without presetting the RB range.

[0127] If all channels of a Redcap terminal are operated within a 20MHz BWP, then a method of allocating up to 100MHz within the BWP can be applied, not much different from the existing method of FDRA allocation. However, if only specific channels are restricted to 5MHz in a device using up to 20MHz BWP, a different method from the existing resource allocation may be required. Since only specific channels are restricted to 5MHz, additional changes in frequency hopping, etc. may be required.

[0128] FDRA is defined as two types: RA (Resource Allocation) Type 0 and RA Type 1. Type 0 is a method of grouping RBs and indicating whether each RBG is used in the frequency domain. Type 1 is a method of specifying the starting RB index and BW length through a special equation using RIV (Resource Indication Value).

[0129] RA type 0 is also called a bitmap method, and is a method of indicating whether an RBG is used by using each bit of a bitmap. Referring to TS 38.213, the size of an RBG is determined according to the BW of a BWP, and a bit value of "1" indicates that an RBG is allocated, and "0" indicates that an RBG is not allocated. The following [Table 5] shows the definition of the RBG size according to the size of the BWP.

[0130] [Table 5]

[0131] BWP size Configuration 1 Configuration 1 1-36 2 4 37-72 4 8 73-144 8 16 145-275 16 16

[0132] Referring to [Table 5], if the size of BWP is 50RB, the size of RBG is 4RB. An example of RGB definition according to this can be as follows Figure 8 shown. Figure 8 An example of PRB allocation per RBG according to RA type 0 applicable to the present disclosure is illustrated. Figure 8 An example of RGB allocation according to a bitmap of RA type 0 is illustrated. Figure 8 As shown, four RBs are grouped into one RGB, and DCI uses the FDRA field to indicate whether RBG is used. For example, if the value of FDRA is "0100...", this means that the second RGB is allocated and the remaining RBG is not allocated.

[0133] That is, according to RA type 0, the size of the RBG is determined according to the size of the BWP, and one bit in the bitmap uses the values ​​'1' and '0' to indicate whether the RBG is allocated. Depending on the size of the BWP and the size of the RBG, the bit size of the FDRA field of the DCI may vary. For example, in the case of a 15KHz SCS (subcarrier spacing) of 100MHz in FR1, the FDRA field may include up to 18 bits.

[0134] Unlike RA type 0, RA type 1 uses RIV to indicate the starting index of the RB and the size of how many RBs are used continuously. The value of RIV represents a value determined using a predefined equation in binary format. Generally, the bit size of the FDRA field used in DCI may be smaller than the bit size of the above-mentioned bitmap format. In the case of RA type 1, continuous RBs can be allocated, or for frequency diversity effect, RBs can be distributed as two sets to different frequency domains.

[0135] Fig. 9 An example of PRB allocation according to RA type 1 applicable to the present disclosure is illustrated. Fig. 9 An example of the result of distributing RBs to different frequency domains in RA type 1 is shown. Fig. 9, when the non-interleaved VRB to PRB mapping in the RIV method is the same, the leftmost RB indices are grouped into RB bundles and indexes are assigned to the RB bundles. RBs or RB bundles are arranged using the starting RB and size determined based on the RIV calculation. The size of the RB bundle can be set to one of 1, 2, and 4 through RRC layer signaling. In this case, the RBs of the PDSCH actually to be allocated can be arranged continuously. However, for the frequency diversity effect, one bundle can be divided into two parts and dispersed from each other. This is possible when interleaved VRB to PRB mapping is performed. [Table 6] describes the division of the bundle.

[0136] [Table 6]

[0137]

[0138] Frequency hopping can be applied to PUSCH as follows. The above-mentioned RA type 0 and RA type 1 are mainly applied to PDSCH of the downlink. In the case of RA type 0, it does not allow full flexibility in allocating RBGs per RBG unit within the BWP range, and under the concept of "almost continuous RB allocation", when allocating RBGs, there is a limit on the size of the unallocated gap part in the middle. This is to solve the problem that PAPR becomes a power consumption issue in the uplink. In the case of RIV, interleaved VRB to PRB mapping is not applied to the uplink. This is because if an RB or RB bundle is divided into two parts, PAPR is detrimental to performance and may become a problem of terminal power consumption. Therefore, in the case of PUSCH, inter-slot frequency hopping or intra-slot frequency hopping can be applied to provide a frequency diversity effect while reducing PAPR.

[0139] Fig.10 An example of frequency hopping applicable to the present disclosure is illustrated. Fig.10 Inter-slot frequency hopping or intra-slot frequency hopping of the PUSCH is illustrated. Fig.10 Intra-slot frequency hopping and inter-slot frequency hopping are illustrated. Hopping is not applied to the downlink, but hopping is applied to the uplink, thereby obtaining performance improvement in terms of frequency diversity. That is, the application of RA type in the downlink is limited by PAPR.

[0140] The present disclosure describes various embodiments of how to efficiently apply and / or operate the above-mentioned RA type 0, RA type 1, frequency hopping of uplink, etc. when the frequency band of a shared channel such as PxSCH is limited to 5 MHz. That is, the present disclosure describes various embodiments of guiding resource allocation of a shared channel when a shared channel limited to a specific size is used.

[0141] Fig.11An example of a process of transmitting or receiving data in a wireless communication system according to an embodiment of the present disclosure is illustrated. Fig.11 The operation method of the terminal is illustrated.

[0142] Reference Fig.11 In step S1101, the terminal receives configuration information related to resource allocation. The configuration information related to resource allocation may include information related to interpretation of the resource allocation information. According to various embodiments, the configuration information may include information related to interpretation of the FDRA field included in the DCI. For example, the configuration information may include configuration information for interpreting the RBG size corresponding to each bit in the bitmap included in the FDRA field.

[0143] In step S1103, the terminal receives control information for resource allocation. The control information includes DCI, and the DCI may include scheduling information for PDSCH or PUSCH. Here, the scheduling information includes information about the allocated frequency resources. At this time, the frequency resources may be allocated with a bandwidth of 5 MHz or less. For example, the frequency resources may be indicated by the FDRA field included in the DCI.

[0144] In step S1105, the terminal identifies the allocated resources based on at least one of the configuration information and / or the control information. The terminal identifies the location of the resources allocated for the channel (e.g., PDSCH or PUSCH) by interpreting the DCI. At this time, the terminal can interpret the DCI based on the information indicated by the configuration information and the predefined information (e.g., RBG size table).

[0145] In step S1107, the terminal sends or receives data through the allocated resources. The terminal can identify the frequency resources and / or time resources indicated by the control information, and send or receive signals through the identified resources. That is, during transmission, the terminal can generate a signal by performing processing such as encoding or modulation on the data, and send the signal after mapping it to the allocated resources. During reception, the terminal can reconstruct the data by demapping the signal from the allocated resources and then performing processing such as demodulation or decoding on the demapped signal.

[0146] Implementation #1 : Defines a size different from the existing RBG size in RA type 0 of FDRA.

[0147] In the case of a bitmap method such as RA type 0, the RBG size can be defined according to the number of RBs in the BWP defined in [Table 5]. In this case, if all channels (e.g., PDSCH, PUSCH, PUCCH, PDCCH, SRS, etc.) are included in the BWP, a bitmap can be generated based on 20MHz. However, if PxSCH (e.g., PDSCH, PUSCH) is operated only with a bandwidth or band size of 5MHz according to various embodiments of the present disclosure, the granularity of RBG allocation may be set too coarsely (i.e., too large), which may reduce the efficiency of frequency use. That is, from the perspective of frequency diversity or frequency efficiency, it is not desirable to use a large granularity. For example, a 20MHz BWP uses 8RB as the RBG size. However, a 5MHz BWP uses 2RB as the RBG size, in which case, when PxSCH is applied for 5MHz, the use of 2RB has high flexibility in the resource allocation process. Therefore, for a device using a PxSCH with an RB size of 5 MHz, when using FDRA according to RA type 0, according to one embodiment of the present disclosure, the base station and the terminal apply a new RBG size instead of the existing RBG size of RA type 0.

[0148] -Implementation #1-1: New tables may be applied to RBG sizes for PxSCH that are different from the tables defined in the existing TS 38.213 or that modify the existing TS 38.213 tables. For example, the new table may include RBG sizes that are smaller than the RBG sizes defined in the existing table (e.g., 1 / n of the existing RBG sizes). Specifically, the table is identified based on a table that defines multiple RBG sizes by BWP size, and each of the multiple BWP sizes corresponds to at least one RBG size value for allocation of a relatively wide bandwidth and at least one RBG size value for allocation of a relatively narrow bandwidth. In addition, at least one BWP size may be defined that corresponds to three or more RBG sizes that have a multiple relationship with each other. Here, the table may be understood as a set of multiple tables including an existing table and a table for a narrow bandwidth (e.g., 5 MHz).

[0149] - Embodiment #1-2: A rule (eg, equation) for creating a new RBG size value based on the RBG size value of PxSCH defined in the existing TS 38.213 table may be applied. Examples of specific rules are as follows.

[0150] (1-2-1) A value obtained by dividing a value defined in the table by 4 may be applied. For example, if the RBG size in the table is 8 RB, 2 RB may be applied as the RBG size of the PxSCH having a maximum RB size of 5 MHz.

[0151] (1-2-2) A value obtained by dividing the value defined in the table by 2 may be applied. For example, if the RBG size in the table is 8 RB, 4 RB may be applied as the RBG size of the PxSCH having a maximum RB size of 5 MHz.

[0152] (1-2-3) In the above example, the divisible value (e.g., 4, 2) may not be predefined and may be signaled by a higher layer. For example, the value may be 1, in which case it may not be signaled separately by a higher layer. That is, if the divisible value is not signaled, the value defined in the table may be applied without modification.

[0153] The (1-2-4) divisible value (eg, 4, 2) may be set differently for each RNTI or may be predefined.

[0154] (1-2-5) The starting RB starting position and frequency band size of PxSCH can be statically set in the higher layer or dynamically indicated in the DCI.

[0155] As described in implementation #1-2, by setting or dividing the RBG size value defined in the existing table by a predefined value, the RBG size value per BWP size for narrow bandwidth can be determined. The RBG size value per BWP size for narrow bandwidth is not predefined in the table. However, through the above implementation #1-2, a new table including RBG size values ​​calculated according to the RBG size values ​​defined in the table is determined, which can be understood as creating a new table used inside the terminal.

[0156] Fig.12 An example of a process of performing communication based on an adjusted RBG size in a wireless communication system according to an embodiment of the present disclosure is illustrated. Fig.12 A method of operating a terminal is illustrated. In the following description, a first type channel means a channel using a general bandwidth, and a second type channel means a channel using a relatively narrow bandwidth (eg, 5 MHz).

[0157] Reference Fig.12 In step S1201, the terminal identifies the RBG size for resource allocation of the first type of channel. For example, the terminal identifies the RBG size for the FDRA field designed based on 20 MHz or 100 MHz. Here, the RBG size can be identified based on the BWP size. For example, the RBG size according to the BWP size is identified based on predefined mapping relationship information (e.g., a table), and the mapping relationship information can define multiple options (e.g., configurations) for each of the multiple BWP size segments. Here, which of the multiple options is used can be pre-signaled by configuration information or determined according to a predefined rule.

[0158] In step S1203, the terminal identifies the weight of the RBG size for resource allocation of the second type channel. The RBG size identified in step S1201 is related to the allocation of the first type channel, and the RBG size for the second type channel allocation may be smaller than the RBG size for the first type channel allocation. That is, the RBG size for the second type channel allocation may be expressed as the product of the RBG size for the first type channel allocation and the weight. Therefore, the terminal may identify the weight to be multiplied by the RBG size identified in step S1201. According to various embodiments, the weight may be predefined or may be signaled from the base station. Here, the signaling may be explicit or implicit. As implicit signaling, the weight may be associated with another parameter. For example, the weight may be less than 1.

[0159] In step S1205, the terminal receives resource allocation information for the second type of channel. The terminal may receive control information including scheduling information for the second type of channel, such as DCI. The DCI includes information indicating frequency and / or time resources allocated to the channel. For example, the frequency resources may be indicated by the FDRA field.

[0160] In step S1207, the terminal sends or receives a signal through the second type channel based on the weight and the RBG size. The terminal can identify the frequency and / or time resources allocated to the second type channel based on the resource allocation information, and send or receive a signal through the identified resources. At this time, according to one embodiment, the terminal can interpret the resource allocation information based on the weight identified in step S2103 and the RBG size identified in step S2301. Specifically, the terminal can determine the RBG size applied when using the second type channel based on the RBG size and the weight, and identify the allocated frequency resources (e.g., at least one RBG) by interpreting the FDRA included in the DCI based on the determined RBG size.

[0161] - Implementation #1-3: Applying a size different from the existing RBG size in RA type 0

[0162] In the case of RA type 0 called the bitmap method, the RBG size is defined according to the BWP size as shown in [Table 5]. At this time, if the number of RBs concerned in the present disclosure is expressed as the maximum scheduled transmission N, only the number of RBs less than or equal to N can be allocated continuously or discontinuously.

[0163] However, since the RBG size is generally allocated based on the size of the BWP, if the SCS is 15KHz and the RBG size is 16, even if the number of PRBs corresponding to the maximum scheduling allocation BW of 5MHz is 25, 16 or 32 RBs may be allocated. Considering the limitation that a maximum of 25 RBs can be used, the existing bitmap method of FDRA may have problems in terms of maximum throughput performance. Therefore, in this case, a value smaller than the value defined in [Table 5] may be applied as the RBG size. As the RBG size decreases, a larger number of bits may be required to represent the FDRA, and an implementation method for solving this problem will be proposed below.

[0164] (1-3-1) The RGB size p may be determined by the size of the BWP. If the maximum RB is applied to the PxSCH, a new RGB size P' may be set through higher layer signaling.

[0165] (1-3-1-1) The P' value may be set by RRC (ie, higher layer signaling). If this value is not signaled, the value in [Table 5] may be used.

[0166] (1-3-1-2) The P' value may be indicated by DCI. Alternatively, these values ​​may have been set in RRC, and the DCI may indicate the corresponding code point.

[0167] (1-3-1-3)P' value may be different between BWP IDs.

[0168] (1-3-1-4) In this case, the RBG size parameter signaled by the existing configuration 1 or configuration 2 can be ignored.

[0169] According to the above embodiment, when the RBG size is set to 4, the number of RBGs may increase more than when the previous RBG size is 16RB, for example, from 4 to 8. At this time, if 6 RBGs are allocated, 24 RBs are allocated, so a number of PRBs close to 25 PRBs corresponding to the maximum scheduled transmission bandwidth (for example, a number of PRBs corresponding to 5 MHz) can be allocated. In the above example, more efficient RBG allocation can be achieved compared to the case where the RBG size is set to 16RB.

[0170] (1-3-2) The ratio value of the RGB size may be signaled. For example, the ratio value may be set to any one of 1, 1 / 2, 1 / 4, and 1 / 8. The range of the ratio value may vary depending on the situation. Therefore, when the REG size is selected as 16RB according to [Table 5], if the ratio value such as 1 / 2, 1 / 4, etc. is multiplied, the RBG size may be determined to be 4 or 8.

[0171] (1-3-2-1) The scaling value may be set in the RRC. If the parameter for setting the scaling value is not signaled, it may be interpreted as multiplying by 1 or not multiplying by the scaling value.

[0172] (1-3-2-2) The ratio value is set in RRC, and DCI can indicate the corresponding code point.

[0173] (1-3-2-3) The scale value may be different between BWPs and may be signaled separately for each BWP. When signaling the scale value in RRC, 1 or 2 bits of information are used, and one parameter per cell may be used to indicate the scale value, which reduces signaling overhead by using a bit order according to the BWP ID.

[0174] The (1-3-2-4) index of the scale value may not include 1.

[0175] (1-3-2-5) When the P value is 2, the scale value is not multiplied, and the scale value can be applied only to P values ​​other than 2.

[0176] As described in the above embodiment, if the RBG size is set to be smaller than the BWP size defined in [Table 5], the number of bits used to represent FDRA may increase, that is, the overhead of DCI may increase. For example, in the case of 20MHz, a maximum of 106RBs can be used, and according to [Table 5], since the RBG size is 8RBs or 16RBs, 106RBs require 14 bits or 7 bits. In this case, assuming that the RBG size is 4 in the BWP size of 106RB, a maximum of 27 bits are required, which significantly increases the overhead.

[0177] (1-3-3) When changing the RBG size to a smaller size, the number of bits of FDRA may be predefined, and only RBGs up to the corresponding number of bits may be allocated. The change in RBG size may be signaled for each BWP ID. If no signaling is performed for a specific BWP ID, the RBG size defined in [Table 5] is used.

[0178] (1-3-4) Implementation #1-3 may be defined to be applied only when the RBG size is greater than or equal to a specific P or a specific K1 / K2. For example, when the RBG size is 16 in 15KHz SCS or the RBG size is 3 in 30KHz SCS, implementation #1-3 may be applied.

[0179] -Implementation #1-4: When the RBG size is determined according to implementations #1-1 and #1-2, if the number of valid RBs exceeds the maximum applicable number of 5MHz PxSCH, the RBs can be actually allocated within the range included in the 5MHz bandwidth during the channel coding process. For example, when the RBG size is 4RBs, 7 bits are required as a bitmap representing the RBG in the 15KHz SCS. This is because, as shown in [Table 7] below, in the case of the 15KHz SCS, 25 PRBs are defined within the 5MHz BW. However, when 4 RBs configure one RBG and the value of the bit corresponding to the last RBG (e.g., the 7th bit) is positive (e.g., 1), another 3 RBs are indicated. In other words, 3 more RBs can be allocated than the actually available RBs. At this time, a rule or instruction on how to handle the indicated additional 3 RBs is required, which can be handled by high-level signaling according to one implementation. For example, starting from the MSB of FDRA within the BWP, the PRB index of RGB starting with 1, to the range of RB numbers representing up to 5MHz can be determined as the valid range for PxSCH transmission. The following [Table 7] shows the maximum number of available RBs according to BW and SCS defined in TS 38.101-1.

[0180] [Table 7]

[0181]

[0182] (1-4-1) Since three RBs exceed the 5 MHz channel bandwidth, the base station can adjust the TB size and apply rate matching to not pre-allocate resources.

[0183] (1-4-2) Since three RBs exceed the 5 MHz channel bandwidth, the base station can allocate up to three RBs and puncture them so that these three RBs are not sent during actual transmission. In this case, since there may be performance degradation, frequency hopping can be applied in the downlink.

[0184] (1-4-3) The bandwidth of PxSCH is at most 5 MHz, and a smaller bandwidth size can be applied. In this case, the rate matching and puncturing of the above embodiment can also be applied.

[0185] (1-4-4) For rate matching and puncturing, related operations or parameters can be pre-configured in the higher layer or can be dynamically indicated in the DCI.

[0186] (1-4-5) The number of RBs to which rate matching and puncturing can be applied can be selected from the range of RBG size minus 1 to 1. For example, if the RGB size is 4, rate matching and / or puncturing can be performed for 3, 2, or 1 RBs.

[0187] (1-4-6) The terminal may anticipate puncturing for broadcast PDSCH (e.g., SIB1, OSI, RAR, MSG4, messages or channels distinguished by RNTI for DCI reception, such as full or partial paging) and rate matching for unicast PDSCH. That is, the terminal may process the signal while considering puncturing for broadcast channels and rate matching for unicast channels.

[0188] (1-4-7) When the terminal assumes that puncturing is performed to perform partial reception, it may be pre-defined in the standard whether reception needs to be performed in units of RB or RBG within 5 MHz.

[0189] Fig.13 An example of a process of processing a data signal based on a limited bandwidth in a wireless communication system according to an embodiment of the present disclosure is illustrated. Fig.13 A method of operating a terminal is illustrated.

[0190] Reference Fig.13 In step S1301, the terminal receives resource allocation information of a channel. The terminal may receive control information including scheduling information of the channel, such as DCI. The DCI includes information indicating frequency and / or time resources allocated to the channel. For example, the frequency resource may be indicated by the FDRA field.

[0191] In step S1303, the terminal identifies that some of the allocated RBs are outside the available RB range within the bandwidth. The channel scheduled by the DCI received in step S1301 is a channel with limited bandwidth, and the number of available RBs may also be limited according to the bandwidth limitation. However, the control information received in step S1301 may indicate RBs or RBGs that are more widely distributed than the available RB range. In this case, the terminal may identify that some of the indicated RBs are outside the available RB range.

[0192] In step S1305, the terminal performs puncturing or rate matching by considering the RBs outside the available RB range. That is, when sending or receiving data, the terminal may exclude a portion of a data signal generated by considering at least one RB outside the available RB range, or adjust the length (e.g., number of symbols) of the data signal. At this time, configuration information or parameters for performing puncturing or rate matching may be signaled in advance.

[0193] - Implementation #1-5: PxSCH of 5 MHz band size or smaller may be indicated in ascending order of PRB index starting from the bit mapped to the first RBG of the existing FDRA field, or in descending order of PRB index starting from the bit mapped to the last RBG. For example, when FDRA is "00 101001000", if 5MHz PxSCH is used, the underlined bits indicate the maximum 5MHz bandwidth allocated for PxSCH when applicable. In this case, the granularity of the underlined bits can be smaller than the granularity of the non-underlined bits.

[0194] (1-5-1)FDRA can specify a bitmap in the 20MHz range.

[0195] (1-5-2) The RBG size of the underlined portion and the RBG size indicated by each bit of the remaining non-underlined portion may be different from each other.

[0196] (1-5-3) When determining the RB index range, if it is in ascending order, the non-underlined bits are indicated starting from the MSB, and the non-underlined bits starting from the LSB may not be indicated. The RBG size indicated by the non-underlined bits and the RBG size indicated by the underlined bits may be different, and the RB may be indicated within the BW(P) range of the actual valid PxSCH.

[0197] (1-5-3-1) The RBG size corresponding to the non-underlined part can be applied as the number of RBs defined in the existing TS 38.213.

[0198] (1-5-3-2) The RBG size corresponding to the non-underlined part can be preset through upper layer signaling.

[0199] (1-5-3-3) The RBG size corresponding to the underlined portion can be determined according to one of the above-mentioned implementations.

[0200] (1-5-3-4) Among the bits included in the FDRA, several bits starting from the MSB are used to indicate an offset of a specific granularity, and subsequent bits may indicate an allocation of up to 5 MHz according to RA type 0 of the FDRA. The granularity may be the number of RBs of an RBG according to the BWP size or a specific number of RBs configured. Alternatively, the granularity may be a multiple of the RBG size.

[0201] (1-5-3-5) If the frequency domain of a specific PxSCH is determined, the non-underlined bits whose values ​​are 0 described above can be omitted from FDRA.

[0202] (1-5-3-6) Whether implementation mode #1-5 can be applied can be reported through UE capability information.

[0203] (1-5-3-7) If the setting with a value of 1 in the bitmap exceeds the valid RBG range of up to 5 MHz or the valid band size of PxSCH, the terminal performs partial reception by allocating data from the front end of the bitmap to the valid RGB and puncturing the rest.

[0204] (1-5-3-8) In the case of (1-5-3-7) above, rate matching is also possible, which does not allocate data to the corresponding RBG but punctures it and allocates it only to the valid RBG.

[0205] (1-5-3-9) For the above (1-5-3-7) and (1-5-3-8), relevant high-level signaling can be executed.

[0206] (1-5-4) When determining the RB index range, if it is in descending order, only the non-underlined bits starting from the LSB can be indicated, and the non-underlined bits starting from the MBS can not be indicated. The size of the RBG mapped to the non-underlined bits with a value of 0 and the RBG mapped to the underlined bits can be different, and the RB can be indicated within the BW(P) range of the actual valid PxSCH.

[0207] (1-5-4-1) For the above (1-5-4), the above (1-5-3-1) to (1-5-3-9) can be applied.

[0208] As described above, two or more RBG sizes may be applied to the bits in the bitmap. That is, the terminal may determine, for a first bit set and a second bit set of the bits included in the bitmap, to apply a first RBG size to at least one RBG corresponding to the bits belonging to the first bit set, and to apply a second RBG size to at least one RBG corresponding to the bits belonging to the second bit set.

[0209] Fig.14 An example of a process of applying multiple RBG sizes to the FDRA field in a wireless communication system according to an embodiment of the present disclosure is illustrated. Fig.14 A method of operating a terminal is illustrated.

[0210] Reference Fig.14 In step S1401, the terminal receives bitmap information for allocating frequency resources of a channel. The bitmap information is included in the DCI and may include FDRA. Each bit of the bitmap information corresponds to an RBG, and a bit set to 0 (e.g., "0 bit" hereinafter) means that the RBG corresponding to the bit is not allocated, and a bit set to 1 means that the RBG corresponding to the bit is allocated.

[0211] In step S1403, the terminal applies the first RBG size to the consecutive 0 bits in the front end or the back end. Each bit of the bitmap is set to 1 or 0, and one 0 bit or consecutive 0 bits may be included in the front end or the back end. At least one consecutive 0 bit in the front end or the back end means that at least one corresponding RBG is not allocated. At this time, the terminal interprets that the RB of the first RBG size is not allocated for each 0 bit.

[0212] In step S1405, the terminal applies the second RBG size to the remaining bits. The second RBG size is applied to the remaining bits except for at least one 0 bit to which the first RBG size is applied in step S1403. That is, two different RBG sizes may be applied to the bits included in one bitmap. For example, the second RBG size may be defined or set to be smaller than the first RBG size.

[0213] - Implementation #1-6: In RA type 0, the RBG size for 1 and the RBG size for 0 in the bit of FDRA may be set differently.

[0214] For the uplink, 1 may be arranged continuously. For the downlink, 1 may be arranged discontinuously. In this case, 0 represents the distance from the PRB, and 1 represents the actual valid RGB index. According to the above embodiment, the RBG size of the RBG index represented as 1 is set to be smaller than the value defined in [Table 5]. In this case, since the number of 1s in PxSCH scheduling is not always constant, the number of bits of FDRA may vary depending on the situation. This may cause problems when decoding the corresponding PDCCH of DCI. Therefore, if the number of bits of FDRA may be variable, the number of bits of FDRA may be fixed to a certain M value.

[0215] (1-6-1) For the RBG corresponding to the bit with a value of 0 in FDRA, the RBG size may be directly indicated by the base station, or may indicate a proportional value multiplied by the existing RBG size. For example, the proportional value may be predefined as a fixed value of 2.

[0216] (1-6-2) For the RBG corresponding to the bit with a value of 1 in FDRA, the RBG size may be directly indicated by the base station, or a ratio value multiplied by the existing RBG size may be indicated. For example, if the result of multiplying by the ratio value is 1, the RBG size is set to 2. For example, the ratio value may be predefined as 1 / 2.

[0217] (1-6-3) In the above (1-6-1) and (1-6-2), MAC CE, DCI, RRC high-layer signaling, etc. can be used to indicate the RBG size.

[0218] (1-6-4) The maximum number of available bits in the DCI field of FDRA is set to M, and M bits in the DCI can always be used as the FDRA field.

[0219] (1-6-4-1) M may be signaled in higher layers. Alternatively, M may be predefined to be twice the number of bits before the RBG size reduction.

[0220] (1-6-4-2) When allocating resources using FDRA, if there are remaining bits, the remaining bits can be filled with 0.

[0221] (1-6-4-3) When allocating resources using FDRA, if the number of bits is insufficient, they can be allocated bit by bit according to the RBG index ranking, and the rest can be treated as unallocated.

[0222] (1-6-4-4) The number of RBs included in the first RBG and the corresponding RBG may be smaller than the changed size. In this case, the number of RBs of the corresponding RBG may vary depending on whether the bit value of the RBG index is 0 or 1.

[0223] (1-6-4-5) The M value can be determined based on the number of RBGs before the RBG is changed without signaling from a higher layer. For example, if the original RBG size is 4 RBs, the number of RBGs and the number of bits can be determined based on 4. At this time, if the number of bits is 10, M can be determined to be 10.

[0224] (1-6-5) Implementation #1-6 may be defined as applicable only when the RBG size is greater than or equal to a specific P or a specific K1 / K2. For example, when the RBG size is 16 in a 15KHz SCS or the RBG size is 3 in a 30KHz SCS, implementation #1-6 may be applied.

[0225] - Implementation #1-7: For FDRA, concepts such as PxSCH-BWP or RB subsets may be introduced to allow configuration of new bitmaps for PxSCH in addition to the existing BWP units. The starting RB starting position and band size of PxSCH may be statically set in the higher layer or may be dynamically pre-indicated in the DCI.

[0226] Implementation #2: For the RIV method of RA type 1, restrictions different from existing restrictions may be set, or at least some of the implementations described above in connection with RA type 1 may be applied.

[0227] As described above, the RIV method indicates a specific value determined by using the starting index of the RB and the number of RBs. At this time, it is necessary to set the value not to exceed the maximum 5MHz band size or bandwidth of the PxSCH. In this case, when the FDRA is generated based on the maximum 20MHzBWP, the starting RB within the 5MHz range of the PxSCH is the starting RB of the RIV, not the starting RB of the BWP, and the maximum 5MHz band size and bandwidth from the starting RB can be indicated.

[0228] - Implementation #2-1: For PDSCH, similar to PUSCH, interleaved VRB to PRB mapping may not be applied.

[0229] (2-1-1) When interleaved VRB to PRB mapping is applied, RBs are divided into multiple groups by an interleaving operation, and these groups are distributed in the frequency domain. Fig. 9 , there may be a situation where RB or RB bundle #12, #13 and #14 exceed the maximum 5MHz range. By excluding interleaved VRB to PRB mapping, the effect of preventing this phenomenon can be obtained.

[0230] (2-1-2) Under certain conditions, interleaved VRB to PRB mapping may be excluded. For example, if interleaved VRB to PRB mapping is applied, when the allocated PRB exceeds 5 MHz bandwidth, the terminal may not apply the interleaved VRB to PRB mapping even if the base station sets the interleaved VRB to PRB mapping.

[0231] - Implementation #2-2: When interleaved VRB to PRB mapping is applied, if the RBs or RB bundles #12, #13, #14 described above exceed the maximum 5 MHz range, various methods may be considered to handle resource mapping of these RBs or RB bundles.

[0232] (2-2-1) The base station or the terminal can determine the TB size by pre-considering the number of RBs or RB bundles exceeding the corresponding range, and perform rate matching so as not to allocate physical resources for the corresponding RBs.

[0233] (2-2-2) The base station or terminal may allocate physical resources for RBs beyond the corresponding range and puncture the corresponding part during transmission. At this time, since there may be performance degradation, frequency hopping may be applied in the downlink.

[0234] (2-2-3) Whether to perform rate matching or puncturing can be statically preset in the higher layer, or can be dynamically indicated through DCI.

[0235] (2-2-4) The valid range of RIV is from the starting PRB to the number of RBs set in the higher layer, i.e. 5 MHz or less, and the maximum number of RBs can be signaled by the base station or based on a predefined value. The maximum number of RBs can be a multiple of the PRB bundling size.

[0236] (2-2-5) When the RB exceeds the 5MHz bandwidth due to interleaved VRB to PRB mapping, whether to apply interleaved VRB to PRB mapping, whether to perform puncturing or rate matching can be set or predefined in the higher layer. Alternatively, the relevant settings can be indicated in real time according to the situation through a specific bit of the DCI.

[0237] (2-2-6) The bandwidth size of PxSCH transmission can be defined as a multiple of the PRB bundle size.

[0238] - Implementation #2-3: For FDRA, concepts such as PxSCH-BWP or RB subsets may be introduced to allow configuration of new bitmaps or RIVs for PxSCH in addition to the existing BWP units. The starting RB starting position and band size of PxSCH may be statically set in the higher layer or may be dynamically pre-indicated in the DCI.

[0239] - Implementation #2-4: The offset described in the above implementation #1-4 proposal may be included in the FDRA and notified.

[0240] - Implementation #2-5: For eRedcap terminals, the RIV method of RA type 1 may be applied only to both downlink and uplink, or to one of the downlink and uplink. The application target of the RIV method may be set in a high layer, which may increase flexibility.

[0241] Implementation #3: When frequency hopping is applied, RB start is reapplied.

[0242] Generally, frequency hopping is applied when interleaving is not performed in RIV of RA type 1 of uplink. The standard definition of frequency hopping is shown in the following [Table 8].

[0243] [Table 8]

[0244]

[0245]

[0246] - Embodiment #3-1: When interleaved VRB to PRB mapping is not applied in transmitting PDSCH in the downlink within 5 MHz, frequency hopping may be applied. The application of frequency hopping may be configured using higher layers (such as RRC or DCI).

[0247] - Embodiment #3-2: In the case where a range such as a special BWP is pre-applied in the maximum 5 MHz band size or bandwidth of a PUSCH, unlike the existing definition, the RB start for determining the RIV within the UL BWP may be determined as follows.

[0248] (3-2-1) The first RB of the maximum frequency band size of the PUSCH is determined as the RB start. That is, hopping may be considered for the entire PUSCH-BWP or an RB subset.

[0249] (3-2-2) Frequency hopping is applied as before only within the range of the corresponding PxSCH-BWP or RB subset. At this time, the value of FDRA can be set based on the range of the corresponding PxSCH-BWP or RB subset (instead of the existing UL BWP).

[0250] Implementation #4: FDRA Optimization Allocation Method in RIV Method

[0251] Unlike the bitmap method used in RA type 0, the RIV method of RA type 1 is divided into two methods. One method is the DCI X_1 or X_0 method, which calculates RIV in units of one RB. The content related to RIV extracted from TS 38.214 is as follows [Table 9].

[0252] [Table 9]

[0253]

[0254] In this method, a variable LRB representing the RB size may be used. Therefore, in this method, scheduling may be performed so as not to exceed the number of PRBs that transmits the maximum scheduling BW (e.g., 5MHz PRB). However, in another method, when K1 / K2 of DCIX_2 is used to determine RBGs and determine RIVs with 2, 4, 8, or 16 RBs, some problems may occur for larger RBGs. To this end, the present disclosure proposes the following implementations.

[0255] #Implementation 4-1: When K1 / K2 is 16, the base station or terminal may interpret K1 / K2 as 8 and process RIV.

[0256] #Implementation 4-2: A new RRC parameter K1' / K2' may be defined with a new 1 in K1 / K2. If RIV is allowed to be determined in units of 1 RB in DCI 2_X, even the maximum scheduled transmission bandwidth (eg, 5 MHz PRB) in an odd number case can be accurately processed without causing waste.

[0257] #Implementation 4-3: In the case of the bitmap method, due to the problem of accurately using the number of RBs of the maximum scheduled transmission bandwidth (e.g., 5MHz PRB), it is possible to limit the use of only DCI X_1 or DCI X_0 of RA type 1. In this case, even if the DCI field includes an FDRA additional bit for dynamically indicating the RA type, the additional bit may not be used. Specifically, the bit indicating the dynamic RA type may be removed, fixed to a specific value, or the terminal may not refer to the bit.

[0258] Implementation #5 : The interleaved uplink transmission method in the unlicensed band can be applied based on 5MHz instead of 20MHz.

[0259] Interleaved uplink transmission method such as Fig.15a and Fig.15b shown. Fig.15a and Fig.15bAs shown in FIG15 , according to the interleaved uplink transmission scheme, based on 20 MHz LBT (Listen Before Talk) channel sensing in the unlicensed band, RBs are distributed in the frequency domain at 10 RBs or other specific intervals.

[0260] Interleaved transmission can be performed to meet the PSD (power spectral density) specification in the OFDMA scheme. That is, by allocating as many RBs as a multiple of a specific RB unit, unlike the aforementioned bitmap method or RIV method, RBs are distributed over the 20MHz frequency domain at fixed intervals of each 1RB. In this case, if PUSCH is transmitted within a limited bandwidth of 5MHz, additional restrictions may be required. According to various embodiments of the present disclosure, a variety of methods can be applied. When interleaved transmission based on 20MHz is applied to the case where PxSCH is transmitted only based on 5MHz, the key is how to perform interleaved transmission within the maximum 5MHz frequency band.

[0261] - Implementation #5-1: To specify 5 MHz in the 20 MHz unlicensed band, the 20 MHz band may be divided into four equal parts, thereby being divided into four 5 MHz bands, and one of the four 5 MHz bands may be indicated using 2 bits of information. This may be set via DCI, MAC CE, or higher layer signaling. By doing so, the base station may indicate the 5 MHz band in the entire 20 MHz band to the terminal, and the terminal may perform LBT in the specified 5 MHz band.

[0262] - Implementation #5-2: Refer to Fig.15b , there are five interlaces such as 1 to 5. Unit bundles of five RBs are defined by these five interlaces, with one RB per interlace. When M bundles are defined, these bundles can be indexed as 0, 1, 2, 3, .... If the starting interlace 0 is determined as the starting PRB and at least one RB is arranged at 5MHz intervals, the PRBs included in the corresponding range can be used as a continuous set of valid PRBs sent by PxSCH. Thereafter, regarding how to process actual data for the valid RBs, it can be distinguished in terms of channel coding based on rate matching or puncturing.

[0263] - Embodiment #5-3: Although the RBs of the PUSCH are arranged on 20 MHz, rate matching can be performed based on the TB size corresponding to the number of RBs within the actual 5 MHz transmission range. And, only the RBs within the actual range can be used for transmission.

[0264] - Implementation #5-4: Which 5 MHz band to use within the 20 MHz band acquired through LBT is pre-set in DCI or a higher layer, after which RBs can be interleaved and allocated at specific intervals in the 5 MHz band. The methods of the above implementations #5-1 and #5-2 can be applied to uplink channels such as PRACH and SRS, but not to PxSCH channels.

[0265] Implementation #6 : Various other proposals

[0266] - Embodiment #6-1: When only the bandwidth size of PDSCH and PUSCH is limited to a maximum of 5 MHz, the above transmission method may be adaptively applied using RNTI (eg, depending on the PDDCH type of a specific SSS).

[0267] (6-1-1) The limitation of maximum 5MHz PxSCH can be applied only to C-RNTI.

[0268] (6-1-2) The above transmission method can be applied to all RNTIs set as PxSCH.

[0269] (6-1-3) FDRA for a specific RNTI (e.g., SI-RNTI) should be allocated only in a predefined frequency domain or a specific frequency range, not through DCI.

[0270] - Embodiment #6-2: When MSG3 of the random access procedure is transmitted, (6-1-2) may be applied to the FDRA field which is the uplink RAR of MSG2.

[0271] - Implementation #6-3: For shared channels (eg, PxSCH), application of a maximum 5 MHz band size and bandwidth may be dynamically indicated by DCI.

[0272] - Implementation #6-4: The maximum transmission bandwidth size of the shared channel can be preset in the higher layer according to the RNTI.

[0273] - Implementation #6-5: In the case of a method based on setting the offset of the starting point of PxSCH to a maximum of 5 MHz, if the BWP of the downlink or uplink exceeds 5 MHz, the maximum continuous RB range of PxSCH can be limited to 5 MHz. In other words, the transmission bandwidth of PxSCH can be fixed to a maximum of 5 MHz.

[0274] - Implementation #6-6: When the BWP size is 5 MHz or less, the maximum transmission BWP of PxSCH can be determined according to the corresponding BWP. For example, the transmission range of PxSCH can always be set to be equal to the BWP size.

[0275] - Implementation #6-7: When the PxSCH-BWP is determined and the PxSCH is operated within the existing BWP, the size of the PxSCH-BWP is less than or equal to the existing BWP but cannot exceed 5 MHz.

[0276] - Implementation #6-8: As shown in [Table 7], the number of RBs per channel bandwidth is defined in TS 38.101-1 of RAN4 according to the SCS. However, the maximum number of transmit RBs for a PxSCH of up to 5 MHz may be defined as a new value higher than the value defined in [Table 7], or may be preset in a higher layer. In this case, the actually transmittable range may be understood as the concept of the "Max RB" number set set in a higher layer.

[0277] - Embodiment #6-9: The present disclosure describes the concept of RB start or RBG first application. This mainly involves how to arrange the RB start in the frequency domain. Precoding is performed in units of bundles or groups, and when the concept of sub-BWP or PxSCH-BWP is introduced for PxSCH, a new PRG can be configured by applying the sub-BWP or PxSCH-BWP instead of the existing BWP when configuring the PRG.

[0278] If precoding is performed for PxSCH of a specific frequency band size less than 5 MHz, a new array index may also be added specifically for the narrowband in the size of the PRG, such as {1,2,wideband} instead of {2,4,wideband}.

[0279] - Implementation #6-10: When the above RB resources exceed the valid RB number of a specific PxSCH (for example, the number corresponding to the maximum 5 MHz frequency band size), whether to perform puncturing or rate matching can be predefined by RNTI or can be set by RNTI in RRC.

[0280] - Embodiment #6-11: In the case where the allocation of PxSCH is limited to have a bandwidth of 5 MHz or less, regarding the explanation of FDRA, the starting position of RB can be set differently in the time slot including the CORESET of PDCCH and the time slot not including the CORESET. In particular, for PDSCH of USS, for buffer saving of post-FFT, the bandwidth of PxSCH is set continuously or discontinuously within the number of PRBs corresponding to 5 MHz.

[0281] (6-11-1) If the corresponding time slot includes a CORESET and the CORESET includes a PDCCH associated with USS-based unicast, the starting PRB of the FDRA of the PxSCH associated with unicast of the corresponding time slot can be interpreted as follows:

[0282] (6-11-1-1)The starting PRB of CORESET can be interpreted as the starting PRB.

[0283] (6-11-1-2) Whether to interpret the starting PRB of the corresponding CORESET as the starting PRB can be preset or predefined in the RRC. If the corresponding RRC parameter is omitted, whether the CORESET PRB is the starting PRB or whether the active BWP is the starting PRB can be defined as a default setting.

[0284] (6-11-2) If the corresponding time slot includes a CORESET and the CORESET does not include a PDCCH associated with USS-based unicast, the starting PRB of the FDRA of the PxSCH associated with unicast of the corresponding time slot may be interpreted as follows:

[0285] (6-11-2-1) The starting PRB corresponding to CORESET can be interpreted as the starting PRB.

[0286] (6-11-2-2) Whether to interpret the starting PRB of the corresponding CORESET as the starting PRB can be preset or predefined in the RRC. If the corresponding RRC parameter is omitted, whether the CORESET PRB is the starting PRB or whether the active BWP is the starting PRB can be defined as a default setting.

[0287] (6-11-3) If the corresponding time slot does not include CORESET and only includes PxSCH, the RRC parameter can be used to signal whether to determine the starting PRB of the BWP as the starting PRB, or a specific offset is set in the RRC and the starting PRB is determined based on the set offset. In this case, if the corresponding parameter is omitted, the offset can be interpreted as 0.

[0288] (6-11-4) Even if the time slot does not include CORESET, for unicast PxSCH, the starting PRB of the CORESET position including the USS can be interpreted as the starting PRB of the corresponding FDRA.

[0289] (6-11-5) For PxSCH scheduled by DCI, it can indicate whether the starting PRB position of FDRA is determined as the start of the active BWP or the start PRB of the CORESET. If the corresponding field is not set in the higher layer, the default setting of whether it is the start of the active BWP or the start of the CORESET can be defined.

[0290] Compared to general-purpose devices that must support up to 100MHz in 5G, the maximum bandwidth of the Redcap device of Release 17 is 20MHz. The Redcap device is introduced as a technology that is simple in components and operation and can save a lot of costs. The present disclosure proposes a technology that can additionally reduce costs in terms of buffer size or memory without significantly changing the Redcap technology. Generally, memory or buffer size, etc. rely more on user-specific information of shared channels rather than control channels. Therefore, in the present disclosure, by limiting the bandwidth of PxSCH to a maximum of 5MHz instead of a maximum of 20MHz of the system or channel bandwidth, the HW platform structure applied in Release 17 is reused, and the cost reduction of part of the memory can be considered. Of course, limiting all channels to 5MHz and reducing the entire HW platform structure to 5MHz will reduce the initial manufacturing cost compared to 20MHz RFIC or BB (baseband) components, but since the 20MHz BB platform and RIFC are currently very active, reuse is more desirable. In other words, considering the costs required for IOT (interoperability testing), IoDT (interoperability development testing), etc., reducing the memory size while considering a certain degree of reuse will provide better improvements. Therefore, the present disclosure can minimize the changes compared to the prior art, shorten the development cycle, and save some costs by simply imposing a bandwidth limit of about 5 MHz on the shared channel through the above-mentioned various embodiments. Therefore, the proposed technology is expected to be used in efficient wearable devices or private factory devices.

[0291] The example of the above-mentioned proposed method may be included as one of the implementation methods of the present disclosure, and thus may be regarded as a type of the proposed method. In addition, the above-mentioned proposed method may be implemented independently, or some of the proposed methods may be combined (or merged). The rule may be defined so that the base station notifies the UE of information on whether to apply the proposed method (or information about the rule of the proposed method) through a predefined signal (e.g., a physical layer signal or a higher layer signal).

[0292] Those skilled in the art will appreciate that the present disclosure can be implemented in other specific ways than those described herein without departing from the spirit and essential characteristics of the present disclosure. Therefore, the above exemplary embodiments should be 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 it is intended that all changes that come within the meaning and equivalent range of the appended claims are covered therein. In addition, it will be apparent that some claims that refer to specific claims can be combined with another claim that refers to other claims other than the specific claims to constitute an embodiment, or new claims can be added by amendment after the application is submitted.

[0293] Industrial Applicability

[0294] Embodiments of the present disclosure are applicable to various radio access systems. Examples of various radio access systems include the 3rd Generation Partnership Project (3GPP) or 3GPP2 system.

[0295] The embodiments of the present disclosure are applicable not only to various radio access systems but also to all technical fields to which various radio access systems are applied. In addition, the proposed method is applicable to millimeter wave and terahertz wave communication systems using ultra-high frequency bands.

[0296] Additionally, embodiments of the present disclosure are applicable to a variety of applications, such as autonomous vehicles, drones, and the like.

Claims

1. A method for operating a terminal in a wireless communication system, the method comprising the following steps: receiving configuration information related to resource allocation; receiving control information related to the resource allocation; identifying allocated resources based on at least one of the configuration information or the control information; as well as Sending or receiving a signal via said resource, wherein the resource is identified based on at least one table, the at least one table defining a plurality of resource block group (RBG) sizes by bandwidth part (BWP) size, and Each of the plurality of BWP sizes corresponds to at least one RBG size value for allocation of a relatively wide bandwidth and at least one RBG size value for allocation of a relatively narrow bandwidth.

2. The method according to claim 1, wherein: The at least one RBG size value for allocation of the relatively narrow bandwidth is predefined.

3. The method according to claim 1, wherein: At least one BWP size among the plurality of BWP sizes corresponds to three or more RBG sizes having a multiple relationship with each other.

4. The method according to claim 1, wherein: The at least one RBG size value for the allocation of the relatively narrow bandwidth is determined by multiplying the RBG size value for the allocation of a wide bandwidth by a weight.

5. The method according to claim 4, further comprising the steps of: Information related to the weights is received from a base station.

6. The method according to claim 4, wherein: The weight is a predefined value and includes 2 or 4.

7. The method according to claim 1, wherein: The step of transmitting or receiving the signal through the resource includes the step of performing puncturing or rate matching on the at least one RB based on allocating the at least one RB out of a range of available RBs in a narrow bandwidth.

8. The method according to claim 7, further comprising the steps of: Configuration information or parameters related to the puncturing or the rate matching are received.

9. The method according to claim 7, wherein: The step of performing the puncturing or the rate matching comprises the following steps: processing a signal by taking into account said puncturing for a broadcast channel; and The signal is processed by considering the rate matching for the unicast channel.

10. The method according to claim 1, in, The step of identifying the allocated resources comprises the following steps: determining a first bit set and a second bit set for bits included in a bitmap indicating per-RBG allocation included in the control information; applying a first RBG size to at least one RBG corresponding to bits belonging to the first bit set; applying a second RBG size to at least one RBG corresponding to a bit belonging to the second bit set, and The second RBG size is smaller than the first RBG size.

11. The method according to claim 10, wherein: The first bit set includes at least one consecutive 0 bits in the front or back of the bitmap.

12. A terminal in a wireless communication system, the terminal comprising: Transceiver; as well as a processor connected to the transceiver, Wherein, the processor is configured to: receiving configuration information related to resource allocation; receiving control information related to the resource allocation; identifying allocated resources based on at least one of the configuration information or the control information; and Sending or receiving a signal via said resource, wherein the resource is identified based on at least one table, the at least one table defining a plurality of resource block group (RBG) sizes by bandwidth part (BWP) size, and Each of the plurality of BWP sizes corresponds to at least one RBG size value for allocation of a relatively wide bandwidth and at least one RBG size value for allocation of a relatively narrow bandwidth.

13. A communication device, comprising: at least one processor; as well as at least one computer memory coupled to the at least one processor and configured to store instructions that direct operations when executed by the at least one processor, The operations include: receiving configuration information related to resource allocation; receiving control information related to the resource allocation; identifying allocated resources based on at least one of the configuration information or the control information; and Sending or receiving a signal via said resource, wherein the resource is identified based on at least one table, the at least one table defining a plurality of resource block group (RBG) sizes by bandwidth part (BWP) size, and Each of the plurality of BWP sizes corresponds to at least one RBG size value for allocation of a relatively wide bandwidth and at least one RBG size value for allocation of a relatively narrow bandwidth.

14. A non-transitory computer-readable medium storing at least one instruction, the non-transitory computer-readable medium including the at least one instruction executable by a processor, in, The at least one instruction controls the device to: receiving configuration information related to resource allocation; receiving control information related to the resource allocation; identifying allocated resources based on at least one of the configuration information or the control information; as well as Sending or receiving a signal via said resource, wherein the resource is identified based on at least one table, the at least one table defining a plurality of resource block group (RBG) sizes by bandwidth part (BWP) size, and Each of the plurality of BWP sizes corresponds to at least one RBG size value for allocation of a relatively wide bandwidth and at least one RBG size value for allocation of a relatively narrow bandwidth.

Images