Apparatus and method for performing cross-slot scheduling in wireless communication system

Abstract

An object of the present disclosure is to perform cross-slot scheduling in a wireless communication system. A method for operating a terminal may comprise the steps of: receiving configuration information including information indicating an offset between a physical downlink control channel (PDCCH) and a physical downlink shared channel (PDSCH); if the configuration information indicates zero offset, setting a result obtained by adding a value indicated by the configuration information and a predefined value as offset; receiving control information through the PDCCH; confirming a time slot and a resource to which the PDSCH is mapped based on the control information and the offset; and receiving the PDSCH from the confirmed time slot and resource.

Description

Technical Field

[0001] The following description relates to a wireless communication system, and to an apparatus and method for performing cross slot scheduling 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 allocating resources to a terminal using a shared channel having a narrow bandwidth in a wireless communication system.

[0007] The present disclosure may provide an apparatus and method for scheduling channels with different bandwidths in different time slots in a wireless communication system.

[0008] The present disclosure may provide an apparatus and method for signaling information about a gap between a physical downlink control channel (PDCCH) and a physical downlink / uplink shared channel (PxSCH) in a wireless communication system.

[0009] The technical objects to be implemented in the present disclosure are not limited to the above contents, and those skilled in the art in the field to which the technical configuration of the present disclosure is applied may consider other technical objects not mentioned from the embodiments of the present disclosure described below.

[0010] Technical Solution

[0011] As an example of the present disclosure, a method for operating a terminal in a wireless communication system may include: receiving configuration information, the configuration information including information indicating an offset between a physical downlink control channel (PDCCH) and a physical downlink shared channel (PDSCH); based on the configuration information indicating an offset of 0, configuring a result of adding a value indicated by the configuration information to a predefined value as an offset; receiving control information through the PDCCH; identifying a time slot and a resource to which the PDSCH is mapped based on the control information and the offset; and receiving the PDSCH in the identified time slot and resource.

[0012] 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 including information indicating an offset between a physical downlink control channel (PDCCH) and a physical downlink shared channel (PDSCH); based on the configuration information indicating a zero offset, configure the result of adding a value indicated by the configuration information to a predefined value as an offset; receive control information through the PDCCH; identify a time slot and a resource to which the PDSCH is mapped based on the control information and the offset; and receive the PDSCH in the identified time slot and resource.

[0013] As an example of the present disclosure, a communication device may include at least one processor and at least one computer memory connected to the at least one processor, the at least one memory being configured to store instructions, the instructions guiding operations when executed by the at least one processor. These operations may include: receiving configuration information, the configuration information including information indicating an offset between a physical downlink control channel (PDCCH) and a physical downlink shared channel (PDSCH); based on the configuration information indicating a zero offset, configuring the result of adding the value indicated by the configuration information to a predefined value as an offset; receiving control information through the PDCCH; identifying the time slot and resource to which the PDSCH is mapped based on the control information and the offset; and receiving the PDSCH in the identified time slot and resource.

[0014] As an example of the present disclosure, a non-transitory computer-readable medium storing at least one instruction may include at least one instruction executable by a processor. The at least one instruction may control a device to: receive configuration information including information indicating an offset between a physical downlink control channel (PDCCH) and a physical downlink shared channel (PDSCH); based on the configuration information indicating a 0 offset, configure the result of adding a value indicated by the configuration information to a predefined value as an offset; receive control information through the PDCCH; identify the time slot and resource to which the PDSCH is mapped based on the control information and the offset; and receive the PDSCH in the identified time slot and resource.

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

[0016] Beneficial Effects

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

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

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

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

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

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

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

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

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

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

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

[0028] Figure 8The concept of cross-slot scheduling in a wireless communication system according to an embodiment of the present disclosure is illustrated.

[0029] Fig. 9 An example of a method of indicating slot offset information in a wireless communication system according to an embodiment of the present disclosure is illustrated.

[0030] Fig.10 An example of a process of receiving data in a wireless communication system according to an embodiment of the present disclosure is illustrated. DETAILED DESCRIPTION

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0047] Overall system

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

[0070] [Table 1]

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

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

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

[0074] [Table 2]

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

[0076] 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 =1 / (Δ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.

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

[0078] [Table 3]

[0079]

[0080] [Table 4]

[0081]

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

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

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

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

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

[0087] 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, k = 0, ..., is an index in the frequency domain, and l'=0,..., 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, l = 0, ..., 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.

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

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

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

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

[0092] [Equation 1]

[0093]

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

[0095] [Equation 2]

[0096]

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

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

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

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

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

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

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

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

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

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

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

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

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

[0110] Specific embodiments of the present disclosure

[0111] The present disclosure relates to the scheduling of data and describes a technique for performing cross-slot scheduling. Specifically, the present disclosure proposes various embodiments for reducing buffer and memory usage when using narrow bandwidth for data channels.

[0112] 5G NR is a technology that provides services mainly through three major technologies: eMBB (enhanced mobile broadband), URLLC and mIoT (massive Internet of Things). As far as mIoT is concerned, 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. In addition, there are not only three major technologies, URLLC, eMBB and mIoT, in 5G NR, but also a hybrid form of these three technologies. In 3GPP version 17, in order to meet smart factory applications or wearable devices to a certain extent, a new device type that requires low power while requiring URLLC or a certain degree of speed may be required. Such devices are called reduced capability terminals, i.e., Redcap (reduced capability) UEs or Redcap terminals. The present disclosure introduces a technology that simply saves costs by using less buffering and memory for devices with the Redcap device type introduced in version 17. The HW (hardware) platform of the device according to the proposed technology is not much different from the Redcap device type of version 17. If the HW platform is developed from a low-cost perspective rather than aiming to reduce the BOM (bill of materials) of simple components, it will be possible to improve utilization in the wearable device or smart factory fields (target markets served by 10 to 20MHz) by aiming to additionally reduce the maximum throughput (T-put) or buffer component materials with minor changes. That is, from a timeline perspective, the commercialization of this technology will be much shorter than that of Redcap for version 17, and it will be able to fully respond to other market needs even without significant improvements in cost reduction.

[0113] The present disclosure considers a situation of operating in a narrow bandwidth. In addition, in the initial access phase or connection mode where the terminal initially attempts to access the base station, from the perspective of BWP, it may be considered to maintain only 5MHz BW (bandwidth) and continuous band size in PxSCH, while maintaining a maximum of 20MHz BW in other existing channels (e.g., PDCCH, PUCCH, SRS, PRACH, etc.). In this case, from the perspective of the HW platform, it is expected that there will be no major changes in the baseband circuit or RFIC (radio frequency integrated circuit). Due to the reduction in maximum throughput, it is possible to consider reducing the memory size, etc. In addition, while the range of other channels is up to 20MHz, the range of PxSCH is only up to 5MHz. Therefore, if PxSCH and PDCCH are scheduled in the same time slot, buffers may not be saved. However, after decoding the DCI of PDCCH, if it is confirmed through the TDRA field that transmission will be performed in the next or subsequent time slot, buffering can be performed for the transmission of PDSCH within 5MHz. Therefore, if PDCCH and PxSCH are transmitted in different time slots, the terminal can operate the memory without wasting buffers. That is, if a gap of at least one time slot can be provided between the PDCCH and the corresponding PDSCH through cross-slot scheduling, and if the transmission of the PDSCH in another time slot can be known in advance through the TDRA field of the PDCCH, the buffer size of the shared channel can be pre-designed to be reduced in the eRedcap (enhanced Redcap) terminal of version 18, and therefore a cost reduction effect can be expected.

[0114] According to various embodiments of the present disclosure, since PxSCH is transmitted within a maximum of 5 MHz, but reception of other channels can be performed within a maximum of 20 MHz, it is not easy to reduce buffering when the channels of PxSCH and other channels are received and / or transmitted in one time slot. This is because the buffer memory size of PxSCH must be designed to a maximum of 20 MHz BW. In order to save the buffer, it is preferred to arrange the time slots including PDCCH and the time slots including PxSCH with a difference of 1 to 2 time slots. Buffering can be set on a slot-by-slot basis because when two channels are received in one time slot, information about PDSCH cannot be known before decoding PDCCH. Therefore, the present disclosure proposes a technique for preventing same-slot scheduling by spacing out the scheduling of PDCCH and PxSCH in Redcap of version 18 using cross-slot scheduling.

[0115] Release 16 defines a power saving technology. Regarding the power saving technology, the concept of cross-carrier scheduling is introduced for the first time. In Release 16, cross-carrier scheduling aims at power saving and buffer saving, and can be used in combination with the technology proposed in the present disclosure from the perspective of ensuring the scheduling gap between PDCCH and PDSCH. In addition, the present disclosure studies the problems that may arise when combining cross-carrier scheduling and introduces methods that can solve these problems.

[0116] The cross-slot scheduling technique related to power saving in Release 16 is as follows.

[0117] Figure 8 The concept of cross-slot scheduling in a wireless communication system according to an embodiment of the present disclosure is illustrated. Figure 8 , a constant gap between PDCCH and PDSCH scheduled by PDCCH can be guaranteed by cross-slot scheduling technology. Two slots from slots 0 to 16 can be configured in RRC, and one of the two configured slots can be designated as DCI. That is, in Figure 8 In the sleep period, the terminal may not perform any operation or decode the PDCCH slowly (e.g., across multiple time slots) during the sleep period. That is, even if the PDCCH is received over a bandwidth greater than 5MHz, the terminal may divide the FFT output data of the PDCCH into a 5MHz buffer and store and process it. In this case, the decoding of the PDCCH may be completed after multiple time slots have passed.

[0118] For this purpose, it is assumed that the K0 value is always greater than a certain minimum value, and this minimum value can be defined by an RRC parameter called minimumSchedulingOffset. If PDCCH and PxSCH can be scheduled in the same time slot, even if the transmission and reception of PxSCH does not exceed the 5MHz bandwidth, the terminal has to always assign a maximum of 20MHz as the buffer size in the corresponding time slot, which is not considered from the perspective of power saving. However, if Figure 8 As shown, cross-slot scheduling is performed, and the terminal can prepare a buffer with a bandwidth size of 5 MHz for the transmission or reception of PxSCH without considering the transmission of PxSCH of 5 MHz or larger.

[0119] Reference Figure 8 , PDCCH is sent in slot n, and PDSCH is sent in slot n + 3. Therefore, the UE can decode PDCCH in slot n, enter sleep state in slots n + 1 and n + 2, or decode PDCCH with low power in slots n to n + 2.

[0120] ● Minimum scheduling offset limit: When the minimum scheduling offset limit is applied, the UE should not expect to be scheduled by DCI to receive PDSCH or PUSCH in time slot n (when K0 or K2 is less than the minimum scheduling offset limit K 0min or K 2min in the case of ).

[0121] ● Power savings using minimum scheduling offset constraints

[0122] -When gNB is configured with K 0min When , the UE can reduce power consumption as follows:

[0123] -UE behavior #1) Fast PDCCH decoding and sleep during guaranteed gaps, or

[0124] -UE behavior #2) Relaxed PDCCH decoding (eg, lower voltage, lower clock rate).

[0125] minimumSchedulingOffset indicates the minimum slot gap that PDSCH and PUSCH based on PDCCH have for K0 and K2 respectively. Since the indicated gap is the minimum value, the actual slot of K0 or K2 of TDRA will be equal to or greater than this value. In addition, when specified by DCI, the following rules may be applied. As shown below, the power saving applied in Release 16 may only apply to the connected mode of USS. However, the technology proposed in the present disclosure can also be applied to RRC idle or initial access or RRC inactive mode in addition to the connected mode of USS.

[0126] Implementation #1 : In cross-slot scheduling of eRedCap in Release 18, if it is USS, the power saving related minimumSchedulingOffset parameter of Release 16 is reused to apply appropriately.

[0127] The minimum applicable scheduling offset indicator included in DCI format 0_1 / 0_1 is 0 bit when the high-level parameter minimumSchedulingOffset is not configured; and is 1 bit when the high-level parameter minimumSchedulingOffset is configured. At this time, according to the value of the minimum applicable scheduling offset indicator, the minimum applicable K0 and K2 are set as shown in the following [Table 5].

[0128] [Table 5]

[0129]

[0130] Referring to [Table 5], there may be a 0 offset. In some cases, such as when not configured in RRC, a 0 offset may be applied. Even if this part reuses the corresponding parameters, it may not be suitable for cross-slot scheduling of the current version of eRedcap. Therefore, the present disclosure proposes the following implementation.

[0131] - Implementation #1-1: If the offset is 0, cross-slot scheduling is applied by configuring it to 1.

[0132] - Implementation #1-2: If cross-carrier scheduling of eRedcap is applied with an offset determined according to [Table 5], add 1 additionally.

[0133] ■ Other values ​​(instead of 1) may be added, and the added value may be signaled in advance from a higher layer. Here, higher layer signaling refers to RRC signaling.

[0134] - Embodiment #1-3: As a predefined frequency domain, it can be assumed that a specified area of ​​up to 5 MHz is used. In this case, same time slot scheduling is also possible.

[0135] - Implementation #1-4: When DCI is used instead of RRC configuration, if the offset is 0 or 1, implementation #1-3 is applied.

[0136] Implementation #2 : A new offset parameter or field is newly defined and the value is indicated through RRC or DCI.

[0137] - Embodiment #2-1: In RRC, a fixed value or a part of a table is indicated by DCI by using an index.

[0138] - The offsets for uplink and downlink may be different.

[0139] Implementation #3 : If a terminal supporting cross-slot scheduling for power saving of Release 16 also needs to support cross-slot scheduling for eRedcap of Release 18, the slot offset related parameters for these two cases are signaled in DCI or from higher layers.

[0140] - Implementation #3-1: The larger of the two values ​​is applied. Alternatively, only the slot offset parameter related to cross-slot scheduling is applied.

[0141] - Implementation #3-2: The minimumSchedulingOffset of Release 16 power saving is applied first. However, if the value of minimumSchedulingOffset is 0, the offset value of eRedcap is applied.

[0142] - Implementation #3-3: Applying the sum of two parameters. In the case of K0 or K2, a guarantee for the sum value or greater should be supported in the TDRA allocation table list information in the RRC message.

[0143] Implementation #4 : If dynamic positioning is not performed, the pre-configured maximum 5MHz bandwidth size or BW zone of PxSCH is used.

[0144] During the PRACH process or initial access process, there may be a situation where the list index of a specific offset cannot be preconfigured with a specific RRC. In this case, you can consider configuring the value in the SIB or defining the position of the PxSCH in the initial BWP.

[0145] - Implementation #4-1: Prior to initial access, a specific PDCCH and offset on the PDSCH are signaled using SIB. At this time, restrictions may be imposed on the applied PDSCH, such as using only a specific RNTI (eg, C-RNTI or MCS-C-RNTI).

[0146] ■ The slot offset value can be configured differently for each RNTI, and for a specific RNTI, a predefined value can be used to improve operational ease.

[0147] Implementation #4-2: During PRACH or initial access, the location of the RB can be pre-specified. That is, before decoding the PDCCH, the possible location of the PDSCH can be pre-determined within a range of up to 5 MHz, so in this case, same-time slot scheduling is also possible to a certain extent.

[0148] ■In this case, the position and size can be indicated in advance through SIB, etc.

[0149] ■ 5 MHz (or less than the pre-specified size of the 5 MHz BW) may be configured from lower index PRBs, or 5 MHz (or less than the pre-specified size of the 5 MHz BW) may be configured from higher index PRBs.

[0150] Implementation #5 : Impose restrictions on the K0 value or K2 value of the RRC parameters in the TDRA table list.

[0151] The method of guaranteeing the minimum gap between PDCCH and PxSCH through minimumSchedulingOffset has the advantage of being able to dynamically configure the timeslot offset. However, if only the static buffer size reduction is considered, a method of imposing restrictions on K0 and K2 from the beginning in the RRC signaling can be used. If the default TDRA table defined in TS 38.213 is not used, up to 16 TDRA lists can be set from a high level and indicated in the DCI. At this time, if the following RRC parameter information is referenced in the TDRA table, K0 or K2 can be configured from a minimum value of 0, but restrictions may be imposed on the configuration value range of K0 or K2. This implementation may only be applicable to reducing the buffer memory size of eRedcap terminals.

[0152] - Implementation #5-1: The list range for K0 and K2 can be set or defined to have a specific value or greater. For example, for eRedcap, K0 and K2 may only have values ​​greater than 1 or 2.

[0153] - Implementation #5-2: By adding a new Redcap list parameter of version 18 for K0 and K2, it can be indicated to use the corresponding eRedcap list. In this case, the corresponding list can be defined so that the range of values ​​starts from 0.

[0154] - Implementation #5-3: As shown in [Table 6] below, an offset (e.g., K0_offset, K2_offset) is defined in IE (Information Element), and the result of adding the corresponding value to the existing K0 or K2 can be used as K0 or K2. If the corresponding value is not signaled, the corresponding value can be recognized as a default value (e.g., 0).

[0155] [Table 6]

[0156]

[0157] Implementation #6 : Various other proposals

[0158] - Implementation #6-1: Whether cross-slot scheduling is supported in eRedcap can be signaled through UE capability report.

[0159] ■Therefore, the base station can determine how to schedule the corresponding terminal.

[0160] - Embodiment #6-2: As an early indication, the terminal may pre-signal a request for cross-slot scheduling support using Message 1 (eg, RACH preamble) or Message 3 in the RACH procedure.

[0161] - Implementation #6-3: Using the PDSCH of Message 2, the base station may preconfigure the PDSCH position of the 5 MHz region in the frequency domain as the SIB of Release-18eRedcap.

[0162] - Implementation #6-4: When the terminal supports PEI (Paging Early Indication), the time slot offset information between PDCCH and PxSCH can be indicated in advance through PEI. Fig. 9 An example of a method of indicating slot offset information in a wireless communication system according to an embodiment of the present disclosure is illustrated.

[0163] - Implementation #6-5: In case of cross-slot scheduling, MAC CE may be used to indicate the slot offset of PDCCH and PDSCH.

[0164] - Implementation #6-6: When it is necessary to distinguish the paging of the eRedcap terminal of Release 18 from the paging of the legacy terminal, 1 bit in the DCI indicating the paging can be used to indicate whether it is a 5MHz Redcap terminal. By doing so, when the eRedcap PxSCH is within 5MHz, predefined frequency domain resources (e.g., resources less than 5MHz BW) can be allocated.

[0165] - Implementation #6-7: When the PDSCH default time domain allocation is applied, the K0 value in all tables is 0, but other values ​​may be used.

[0166] ■New tables other than K0 values ​​can be applied.

[0167] ■ A value that is the sum of a specific value and a K0 value defined in an existing table may be used. For example, the specific value may be 1 or 2, etc., and may be predefined.

[0168] - Implementation #6-8: When the default time domain allocation of PUSCH is applied to the eRedcap terminal, the following implementation may be applied:

[0169] ■New tables other than K2 values ​​can be applied.

[0170] ■ A value that is the sum of a specific value and a K2 value defined in an existing table may be used. For example, the specific value may be 1 or 2, etc., and may be predefined or configured in RRC.

[0171] - Implementation #6-9: Information about the UE's cross-slot scheduling-related preference may be added to the UE assistance information.

[0172] ■UEAssistanceInformation (Assistance Information) information is an IE used to report to the base station the preferences that the UE may support based on its capabilities in the current situation, but hopes to be scheduled for various situations. That is, in this respect, UE assistance information is different from UE capability information. Although minSchdulingOffsetPreference is defined in Release 16 as related to power saving, it can be reused for the purpose of indicating the preference for PxSCH cross-slot scheduling of Redcap. Therefore, the definition of the parameters in [Table 7] can be extended so that it can be used for the purpose of reducing the PxSCH buffer size.

[0173] [Table 7]

[0174]

[0175]

[0176]

[0177] ■ Alternatively, a new preference for cross-slot scheduling may be specified via a new parameter. In this case, in addition to simple information about the preference, the actual offset value of one or more preferences may also be reported.

[0178] - Implementation #6-10: When the PxSCH BW size of a specific RNTI exceeds 5 MHz, the same timeslot scheduling may be performed in the timeslot in which the CORESET#x scheduling PDCCH is transmitted.

[0179] ■ In this case, from the perspective of saving buffer, the 5MHz restriction is not required in this time slot.

[0180] • When the PxSCH BW size is less than or equal to 5 MHz, same slot scheduling or cross slot scheduling may be applied as described above. Application and signaling of slot offsets may be performed regardless of the BW size.

[0181] When the PxSCH BW size is less than or equal to 5 MHz, even if the slot offset parameter related to cross-slot scheduling is indicated in advance, the slot offset parameter may not be applied.

[0182] - Implementation #6-11: When BWP is less than or equal to 5 MHz, cross-slot scheduling has no benefit, so cross-slot scheduling is only used when BWP is greater than or equal to 5 MHz.

[0183] - Embodiment #6-12: When a slot offset for applying cross-slot scheduling is configured from an upper layer, a slot offset value may be specified for each BWP. If a sub-BWP or PxSCH-BWP of a BWP of a shared channel is defined, a slot offset value may be indicated for each sub-BWP or PxSCH-BWP.

[0184] - Implementation #6-13: Cross-slot scheduling in eRedcap refers to all cases where PDCCH and PxSCH are not included in the same slot. That is, in the case where K0 and K2 are 1 or more, it may be the same slot as a PDCCH that performs scheduling later instead of a PDCCH that schedules PxSCH. At this time, in order to save the buffer, a bandwidth size of 5 MHz or less may be excluded for PxSCH transmission.

[0185] ■At this time, in the time slot including CORESET#X mapped by the SSS (search space set) and SSSG (search space set group) of the PDCCH, the TDRA of the PxSCH may be configured in the DCI so that the PxSCH is not scheduled.

[0186] ■ If a slot occurs in which the PDCCH and PxSCH of CORESET#X are monitored or transmitted simultaneously, the terminal may not attempt to decode the PxSCH in the slot. Alternatively, the terminal may not attempt to decode the PDCCH.

[0187] ●Whether to try to decode PDCCH or PxSCH can be configured or predefined at a higher level.

[0188] ●Whether to attempt to decode PDCCH or PxSCH for each RNTI may be indicated or predefined at a higher level.

[0189] Implementation #7 :Static resource pre-configuration method for same time slot scheduling

[0190] In order to limit the FFT post-buffer size to 5MHz, the terminal needs to decode the FDRA of the PxSCH, but the decoding operation may require more than 1 time slot. Therefore, in the above-mentioned cross-slot scheduling case, after the PDCCH is sent in the CORESET, the PxSCH corresponding to the PDCCH will not be scheduled in the corresponding time slot, which may cause performance delays. Therefore, cross-slot scheduling can be used as a method to reduce the FFT post-buffer size in services that are not sensitive to delay. However, for services requiring extremely low latency, if the FFT post-buffer size needs to be changed in units of OFDM symbols in the same time slot, it is necessary to pre-configure which area of ​​the frequency domain of the PDSCH starts after a specific OFDM symbol. Therefore, the present disclosure describes the following several proposals that may achieve this goal.

[0191] - Implementation #7-1: The starting OFDM symbol from which PxSCH may start to be transmitted may be pre-configured after CORESET (designation of search space set). In this way, the terminal may know in advance and prepare from which OFDM symbol the PxSCH may start to be transmitted in the corresponding time slot.

[0192] ■If there is no CORESET for PDCCH scheduling in the timeslot, the configuration of the OFDM start symbol of PxSCH may not be applicable.

[0193] ■When configuring TDRA for PxSCH, the start symbol S should be set to the position after the symbol occupied by a specific CORESET. For example, if the CORESET occupies the 1st to 3rd OFDM symbols in the time slot, the higher layer should indicate that PDSCH is sent after the 3rd or 4th symbol.

[0194] ■ It is possible to control the PxSCH not to be located in the OFDM symbol position of the CORESET where the PDCCH is configured. The PxSCH may only be located in the OFDM symbols before and after the CORESET position in the time slot.

[0195] - Implementation #7-2: For unicast PxSCH, FDRA may be interpreted differently so that resources are allocated starting from the PRB of CORESET instead of the starting PRB of BWP. In addition, the OFDM symbols of PxSCH in a slot may be configured not to overlap with the OFDM symbols of CORESET and additionally not to overlap with the OFDM symbols of SSB.

[0196] ■ If there is no CORESET for scheduling PDCCH in the timeslot, the starting PRB of PxSCH may be the same as the starting PRB of BWP.

[0197] ◆The BW of PxSCH is limited to a maximum of 5MHz starting from the starting PRB. In this case, if the sum of consecutive RBs is within the maximum 5MHz range, or even if not consecutive, the sum of allocated RBs is within 5MHz, then such allocation is allowed.

[0198] - Embodiment #7-3: Instead of receiving the PDSCH for unicast, the RB index may be determined as follows:

[0199] ■ The RB index may be determined based on the CORESET including the PDCCH scheduling the unicast PDSCH.

[0200] ◆The RB index can be determined within a range of up to 5 MHz starting from the lowest RB index of the CORESET in the increasing direction of the RB index.

[0201] ◆The RB index can be determined in a range of up to 5MHz starting from the highest RB index of the CORESET in the decreasing direction of the RB index.

[0202] ◆The above index direction can be configured by a specific parameter in the high layer. If the parameter is omitted, it can be identified as a predefined direction (for example, an increasing direction).

[0203] ■ The 5MHz region to be buffered needs to be indicated via dedicated RRC signaling.

[0204] ◆ The 5MHz region can be indicated in FDRA format, or the offset can be preconfigured at a higher layer. The configured offset can be interpreted as the starting PRB of the FDRA.

[0205] ◆For interpretation standard PRBs of FDRA, detailed options can be indicated in the CORESET / Active DL BWP standard method. If the indicated parameter is omitted, the Active DL BWP can be considered.

[0206] ◆PxSCH can be aligned based on the center frequency of the active BWP.

[0207] Fig.10 An example of a process of receiving data in a wireless communication system according to an embodiment of the present disclosure is illustrated. Fig.10 A method of operating a terminal is illustrated.

[0208] 18, in step S1001, the terminal receives configuration information related to communication. For example, the configuration information may include information related to the offset between PDCCH and PDSCH. Alternatively, the configuration information may include information related to the offset between PDCCH and PUSCH.

[0209] In step S1003, the terminal receives control information through the PDCCH. 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 domain resources. At this time, the frequency domain resources may be allocated with a bandwidth of 5 MHz or less.

[0210] In step S1005, the terminal identifies the allocated resources based on the configuration information and the control information. The terminal identifies the location of the resources allocated for PDSCH or PUSCH by interpreting the DCI. At this time, the offset between PDSCH / PDSCH is determined based on the offset indicated by the terminal configuration information. Here, the determined offset can be determined based on the configuration information received in step S1001 and the information received through other additional signaling.

[0211] In step S1007, the terminal receives data through the allocated resources. The terminal may process the data by buffering signals received through the identified resources and performing necessary operations.

[0212] Since the existing version 17 Redcap utilizes narrow bandwidth to a maximum of 20MHz, cost savings and weight reduction have been achieved compared to existing terminals from the perspective of the HW platform. The technology proposed in the present disclosure can achieve cost savings and reduction of buffer size or memory without major changes from the perspective of the existing hardware platform, so that it can be applied to wearable devices or smart factory devices without much effort from the perspective of development or verification. For devices and services that require a certain degree of mobility, the proposed technology may be a slightly improved method over version 17, and it is expected that when the market requires it, its commercialization process will be faster than technologies that require complex improvements.

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

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

[0215] Industrial Applicability

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

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

[0218] 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: receiving configuration information, the configuration information comprising information indicating an offset between a physical downlink control channel (PDCCH) and a physical downlink shared channel (PDSCH); Based on the configuration information indicating a 0 offset, configuring a result of adding a value indicated by the configuration information to a predefined value as an offset; receiving control information through the PDCCH; Identify the time slot and resource to which the PDSCH is mapped based on the control information and the offset; as well as The PDSCH is received in the identified time slot and resources.

2. The method according to claim 1, wherein: The predefined value is configured through radio resource control (RRC) layer signaling.

3. The method according to claim 1, wherein: The PDSCH is allocated within a bandwidth of 5 MHz or less.

4. The method according to claim 1, wherein: The offset between the PDCCH and the PDSCH is configured to be different from the offset between the PDCCH and a physical uplink shared channel PUSCH.

5. The method according to claim 1, in, The configuration information includes a DSCH-TimeDomainResourceAllocationList IE, which is an information element, and The DSCH-TimeDomainResourceAllocationList IE includes K0, K0_offset, K2, and K2_offset.

6. The method according to claim 1, further comprising: A capability report message is sent, wherein the capability report message indicates support for cross-slot scheduling.

7. The method according to claim 1, further comprising: Send MSG1 or MSG3, wherein MSG1 or MSG3 requests cross-slot scheduling, wherein MSG1 is message 1 and MSG3 is message 3.

8. A terminal in a wireless communication system, the terminal comprising: Transceiver; as well as a processor coupled to the transceiver, Wherein, the processor is configured to: receiving configuration information, the configuration information comprising information indicating an offset between a physical downlink control channel (PDCCH) and a physical downlink shared channel (PDSCH); Based on the configuration information indicating a 0 offset, configuring a result of adding a value indicated by the configuration information to a predefined value as an offset; receiving control information through the PDCCH; identifying a time slot and a resource to which the PDSCH is mapped based on the control information and the offset; and The PDSCH is received in the identified time slot and resources.

9. 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, the configuration information comprising information indicating an offset between a physical downlink control channel (PDCCH) and a physical downlink shared channel (PDSCH); Based on the configuration information indicating a 0 offset, configuring a result of adding a value indicated by the configuration information to a predefined value as an offset; receiving control information through the PDCCH; identifying a time slot and a resource to which the PDSCH is mapped based on the control information and the offset; and The PDSCH is received in the identified time slot and resources.

10. 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, the configuration information comprising information indicating an offset between a physical downlink control channel (PDCCH) and a physical downlink shared channel (PDSCH); Based on the configuration information indicating a 0 offset, configuring a result of adding a value indicated by the configuration information to a predefined value as an offset; receiving control information through the PDCCH; Identify the time slot and resource to which the PDSCH is mapped based on the control information and the offset; as well as The PDSCH is received in the identified time slot and resources.

Images