Method and apparatus for determining reference bandwidth in wireless communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting higher data transmission rates. A method by which a wireless communication system processes a control signal of the present disclosure comprises the steps of: receiving a first control signal transmitted from a base station; processing the received first control signal; and transmitting, to the base station, a second control signal generated on the basis of the processing.

Description

Method and device for determining reference bandwidth in a wireless communication system

[0001] The present disclosure relates to the operation of a terminal and a base station in a wireless communication system or mobile communication system. Specifically, the present disclosure relates to a method and device for a terminal to receive system information upon initial cell access to determine a reference bandwidth in a wireless communication system.

[0002] 5G mobile communication technology defines a wide frequency band to enable fast transmission speeds and new services, and can be implemented not only in the sub-6GHz frequency band such as 3.5 gigahertz (3.5GHz), but also in the ultra-high frequency band called millimeter wave (mmWave) such as 28GHz and 39GHz ('Above 6GHz'). In addition, for 6G mobile communication technology, which is called the system after 5G communication (Beyond 5G), implementation in the terahertz band (for example, the 3 terahertz (3THz) band at 95GHz) is being considered to achieve a transmission speed that is 50 times faster than 5G mobile communication technology and an ultra-low latency time that is reduced to one-tenth.

[0003] In the early stages of 5G mobile communication technology, the goal is to support services and satisfy performance requirements for enhanced Mobile Broadband (eMBB), Ultra-Reliable Low-Latency Communications (URLLC), and massive Machine-Type Communications (mMTC). These include beamforming and massive MIMO to mitigate path loss of radio waves in ultra-high frequency bands and increase the transmission distance of radio waves, support for various numerologies (such as operation of multiple subcarrier intervals) and dynamic operation of slot formats for efficient use of ultra-high frequency resources, initial access technology to support multi-beam transmission and wideband, definition and operation of BWP (Bidth Part), new channel coding methods such as LDPC (Low Density Parity Check) codes for large-capacity data transmission and Polar Code for reliable transmission of control information, and L2 pre-processing (L2). Standardization has been made for network slicing, which provides dedicated networks specialized for specific services, and pre-processing.

[0004] Currently, discussions are underway to improve and enhance the initial 5G mobile communication technology in consideration of the services that 5G mobile communication technology was intended to support, and physical layer standardization is in progress for technologies such as V2X (Vehicle-to-Everything) to help autonomous vehicles make driving decisions and increase user convenience based on their own location and status information transmitted by vehicles, NR-U (New Radio Unlicensed) for the purpose of system operation that complies with various regulatory requirements in unlicensed bands, NR terminal low power consumption technology (UE Power Saving), Non-Terrestrial Network (NTN), which is direct terminal-satellite communication to secure coverage in areas where communication with terrestrial networks is impossible, and Positioning.

[0005] In addition, standardization of radio interface architecture / protocols is in progress for technologies such as intelligent factories (Industrial Internet of Things, IoT) to support new services through linkage and convergence with other industries, Integrated Access and Backhaul (IAB) that provides nodes for expanding network service areas by integrating wireless backhaul links and access links, Mobility Enhancement technology including Conditional Handover (CHO) and Dual Active Protocol Stack (DAPS) handover, and 2-step random access (2-step RACH for NR) that simplifies random access procedures. Standardization is also in progress for system architecture / services such as 5G baseline architecture (e.g., Service-based Architecture, Service-based Interface) for grafting Network Functions Virtualization (NFV) and Software-Defined Networking (SDN) technologies, and Mobile Edge Computing (MEC) that provides services based on the location of the terminal.

[0006] Once these 5G mobile communication systems are commercialized, an explosive increase in connected devices will be connected to the communication network, necessitating enhanced functionality and performance of 5G mobile communication systems and integrated operation of these connected devices. To this end, new research will be conducted on improving 5G performance and reducing complexity, supporting AI services, supporting metaverse services, and drone communications by utilizing eXtended Reality (XR), Artificial Intelligence (AI), and Machine Learning (ML) to efficiently support Augmented Reality (AR), Virtual Reality (VR), and Mixed Reality (MR).

[0007] In addition, the development of these 5G mobile communication systems includes new waveforms to ensure coverage in the terahertz band of 6G mobile communication technology, multi-antenna transmission technologies such as Full Dimensional MIMO (FD-MIMO), Array Antenna, and Large Scale Antenna, metamaterial-based lenses and antennas to improve the coverage of terahertz band signals, high-dimensional spatial multiplexing technology using Orbital Angular Momentum (OAM), Reconfigurable Intelligent Surface (RIS) technology, as well as full duplex technology to improve the frequency efficiency and system network of 6G mobile communication technology, satellite, AI (Artificial Intelligence) from the design stage and AI-based communication technology that realizes system optimization by internalizing end-to-end AI support functions, and ultra-high-performance communication and computing resources to provide services with complexity that exceeds the limits of terminal computing capabilities. It can serve as a basis for the development of next-generation distributed computing technologies that can be realized by utilizing them.

[0008] The present disclosure seeks to provide a device and method capable of effectively providing a service in a wireless communication system or a mobile communication system.

[0009] According to one embodiment of the present invention, a method for solving the above-described problem may include a method for processing a control signal in a wireless communication system, the method including: receiving a first control signal transmitted from a base station; processing the received first control signal; generating a second signal based on the processing; and transmitting the generated second control signal to the base station.

[0010] The disclosed embodiment can provide a device and method capable of effectively providing a service in a wireless communication system or a mobile communication system.

[0011] FIG. 1 is a diagram illustrating a basic structure of a time-frequency domain in a wireless communication system according to one embodiment of the present disclosure.

[0012] FIG. 2 is a diagram illustrating a frame, subframe, and slot structure in a wireless communication system according to one embodiment of the present disclosure.

[0013] FIG. 3 is a diagram illustrating an example of bandwidth portion settings in a wireless communication system according to one embodiment of the present disclosure.

[0014] FIG. 4 is a diagram illustrating an example of setting a control region of a downlink control channel in a wireless communication system according to one embodiment of the present disclosure.

[0015] FIG. 5 is a diagram illustrating the structure of a downlink control channel in a wireless communication system according to one embodiment of the present disclosure.

[0016] FIG. 6 is a diagram for explaining a method for a base station and a terminal to transmit and receive data by considering a downlink data channel and rate matching resources according to one embodiment of the present disclosure.

[0017] FIG. 7 is a diagram illustrating an example of frequency axis resource allocation of a physical downlink shared channel (PDSCH) in a wireless communication system according to one embodiment of the present disclosure.

[0018] FIG. 8 is a diagram illustrating an example of time axis resource allocation of PDSCH in a wireless communication system according to one embodiment of the present disclosure.

[0019] FIG. 9 is a diagram illustrating an example of time axis resource allocation according to subcarrier spacing of a data channel and a control channel in a wireless communication system according to one embodiment of the present disclosure.

[0020] FIG. 10 is a diagram illustrating a wireless protocol structure of a base station and a terminal in a single cell, carrier aggregation, or dual connectivity situation according to one embodiment of the present disclosure.

[0021] FIG. 11 is a diagram illustrating an SS / PBCH block, CORESET, and PDSCH according to one embodiment of the present disclosure.

[0022] FIG. 12 is a diagram illustrating a situation in which an initial downlink bandwidth portion is set to be larger than the bandwidth of CORESET according to one embodiment of the present disclosure.

[0023] FIG. 13a is a diagram illustrating candidates for a portion of a reference bandwidth determined according to frequency information of CORESET according to one embodiment of the present disclosure.

[0024] FIG. 13b is a diagram illustrating candidates for a portion of a reference bandwidth determined according to frequency information of CORESET according to one embodiment of the present disclosure.

[0025] FIG. 14 is a diagram in which a reference subband is determined according to frequency information of SS / PBCH and CORESET according to one embodiment of the present disclosure.

[0026] FIG. 15 is a diagram illustrating a PDSCH for a narrowband terminal and a PDSCH for a wideband terminal according to one embodiment of the present disclosure.

[0027] FIG. 16 is a diagram illustrating frequency axis PDSCH repetition according to one embodiment of the present disclosure.

[0028] FIG. 17 is a diagram illustrating frequency axis PDSCH repetition according to one embodiment of the present disclosure.

[0029] FIG. 18 is a diagram for receiving a PDSCH in multiple reception opportunities according to one embodiment of the present disclosure.

[0030] FIG. 19 is a flowchart showing the operation of a terminal according to an embodiment of the present disclosure.

[0031] FIG. 20 is a flowchart showing the operation of a terminal according to an embodiment of the present disclosure.

[0032] FIG. 21 is a diagram illustrating the structure of a terminal in a wireless communication system according to one embodiment of the present disclosure.

[0033] FIG. 22 is a diagram illustrating the structure of a base station in a wireless communication system according to one embodiment of the present disclosure.

[0034] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the attached drawings.

[0035] In describing the embodiments, descriptions of technical details that are well known in the technical field to which the present disclosure pertains and are not directly related to the present disclosure will be omitted. This is to avoid obscuring the gist of the present disclosure by omitting unnecessary explanations and to convey the gist more clearly.

[0036] For the same reason, some components in the attached drawings are exaggerated, omitted, or schematically depicted. Furthermore, the dimensions of each component do not entirely reflect its actual size. In each drawing, identical or corresponding components are assigned the same or different reference numbers.

[0037] The advantages and features of the present disclosure, and methods for achieving them, will become clearer with reference to the embodiments described below in detail together with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below and may be implemented in various different forms. These embodiments are provided only to ensure that the disclosure of the present disclosure is complete and to fully inform those skilled in the art of the scope of the disclosure, and the present disclosure is defined only by the scope of the claims. Like reference numerals designate like elements throughout the specification. In addition, when describing the present disclosure, if a specific description of a related function or configuration is determined to unnecessarily obscure the gist of the present disclosure, the detailed description thereof will be omitted. In addition, the terms described below are terms defined in consideration of the functions of the present disclosure, and may vary depending on the intention or custom of the user or operator. Therefore, the definitions should be made based on the contents throughout the specification.

[0038] In the present disclosure, it will be appreciated that each block of the processing flowchart drawings and combinations of the flowchart drawings can be performed based on computer program instructions. These computer program instructions can be selectively installed in at least one processor of a general-purpose computer, a special-purpose computer, or other programmable data processing equipment, so that the instructions executed by any one or any combination of at least one processor of the computer or other programmable data processing equipment create means for performing the functions described in the flowchart block(s). These computer program instructions can also be stored in a computer-available or computer-readable memory that can direct a computer or other programmable data processing equipment to implement the functions in a specific manner, so that the instructions stored in the computer-available or computer-readable memory can also produce an article of manufacture that includes instruction means for performing the functions described in the flowchart block(s). Since the computer program instructions may be installed on a computer or other programmable data processing device, a series of operational steps may be performed on the computer or other programmable data processing device to create a computer-executable process, and the instructions that cause the computer or other programmable data processing device to perform the steps for performing the functions described in the flowchart block(s) may also provide steps for performing the functions described in the flowchart block(s).

[0039] Additionally, each block may represent a module, segment, or portion of code that contains one or more executable instructions for performing a specific logical function(s). It should also be noted that in some alternative implementation examples, the functions mentioned in the blocks may occur out of order. For example, two blocks (or functions) depicted in succession may actually be executed substantially concurrently, or the blocks may sometimes be executed in reverse order, depending on the corresponding function.

[0040] The term '~ unit' used in the embodiments of the present disclosure means a software or hardware component such as a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC), and the '~ unit' performs certain roles. However, terms including '~ unit' are not limited to software or hardware. The '~ unit' may be configured to be on an addressable storage medium and may be configured to play one or more processors. Thus, as an example, the '~ unit' includes components such as software components, object-oriented software components, class components, and task components, processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functionality provided within the components and '~ units' may be combined into a smaller number of components and '~ units' or further separated into additional components and '~ units'. In addition, the components and '~parts' may be implemented to play one or more central processing units (CPUs) within the device or secure multimedia card. Also, in an embodiment, the '~parts' may include one or more processors.

[0041] As described above, it should be noted that the blocks and combinations of flowcharts described in the present disclosure may be implemented by one or more computer programs containing instructions. One or more computer programs may be stored entirely in a single memory device, or one or more computer programs may be divided and stored in different portions across multiple memory devices.

[0042] Additionally, any / any function or operation described in the present disclosure may be processed by a single processor or a combination of processors. The single processor or the combination of processors may include circuitry that performs processing, such as an application processor (AP, e.g., a central processing unit (CPU)), a communication processor (CP, e.g., a modem), a graphics processing unit (GPU), a neural processing unit (NPU) (e.g., an artificial intelligence (AI) chip), a Wi-Fi chip, a Bluetooth® chip, a global positioning system (GPS) chip, a near-field communication (NFC) chip, a connectivity chip, a sensor controller, a touch controller, a fingerprint sensor controller, a display driver integrated circuit (IC), an audio codec (CODEC) chip, a universal serial bus (USB) controller, a camera controller, an image processing IC, a microprocessor unit (MPU), a system on a chip (SoC), an IC, or similar circuitry.

[0043] It should also be noted that the various embodiments in the claims and description of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software.

[0044] Such software may be stored on a non-transitory computer-readable storage medium. The non-transitory computer-readable storage medium stores one or more computer programs (software modules), wherein the one or more computer programs include computer-executable instructions that, when executed alone or collectively by one or more processors of an electronic device, cause the electronic device to perform a method according to the present disclosure.

[0045] The software may be stored in a temporary or non-transitory storage device, for example, in the form of a read-only memory (ROM) (whether erasable or rewritable), a random access memory (RAM), a memory chip, a device, or an integrated circuit (IC). Furthermore, the software may be stored in the form of an optically or magnetically readable medium, for example, a compact disc (CD), a digital versatile disc (DVD), a magnetic disk, or a magnetic tape. It should be understood that the storage device and the storage medium are examples of non-transitory machine-readable storage media suitable for storing a program for implementing various embodiments of the present disclosure. Accordingly, various embodiments of the present disclosure may provide a program comprising code for implementing a device or method according to any one of the claims of the present specification, and a non-transitory machine-readable storage medium storing such a program.

[0046] In the present disclosure, determining the priority between A and B may be referred to in various ways, such as selecting a higher priority according to a predetermined priority rule and performing an action corresponding to it, or omitting or dropping an action for a lower priority.

[0047] Hereinafter, 'A or B' described in the present disclosure may be understood as 'A and / or B', which may be understood to include 'A', or 'B', or 'A and B'.

[0048] Additionally, 'at least one of A, B, and C' described in the present disclosure may be understood to include 'A', or 'B', or 'C', or 'any combination of A, B, and C'.

[0049] Additionally, 'at least one of A, B, or C' described in the present disclosure may be understood to include 'A', or 'B', or 'C', or 'any combination of A, B, and C'.

[0050] Additionally, 'A / B' described in the present disclosure may be understood as 'A and / or B', which may be understood to include 'A', or 'B', or 'A and B'.

[0051] Additionally, 'A, B' described in the present disclosure may be understood as 'A and / or B', which may be understood to include 'A', or 'B', or 'A and B'.

[0052] Additionally, 'A and B' described in the present disclosure may be understood as 'A and / or B', which may be understood to include 'A', or 'B', or 'A and B'.

[0053] In addition, it can be understood that the 'case where conditions A and B are satisfied' described in the present disclosure is not necessarily limited to the case where both conditions A and B are satisfied, but may include the case where each of conditions A or B is satisfied, the case where both conditions A and B are satisfied, or the case where one or more additional conditions are satisfied together.

[0054] Additionally, throughout this specification, ordinal terms such as "first," "second," "third," and the like (and modifiers thereof) are used solely to distinguish between various instances, occurrences, configurations, messages, stages, or aspects of elements, operations, or information, as described below. Unless the context clearly requires otherwise, the use of such ordinal terms does not require that the elements, operations, or information distinguished by them be structurally, numerically, or inherently different. For example, "a first signal" and "a second signal" may represent instances of the same signal transmitted at different times, may represent signals containing the same core information albeit with some modifications, or may represent signals having different content or characteristics depending on the specific context. Similarly, "a first value" and "a second value" may represent measurements or applications of the same magnitude in different circumstances, or may represent different magnitudes. Such interpretation should be determined by the specific technical context, functions and relationships described in the relevant portions of the specification and claims.

[0055] Furthermore, although terms such as "first" and "second" described in this disclosure are used to refer to various elements such as information, objects, actions, and sequences, they are not intended to limit such elements to a specific order. These terms may be understood to be used merely to distinguish one element from another. For example, a first element may be referred to as a second element, and similarly, a second element may be referred to as a first element.

[0056] Additionally, it may be understood that the terms "first~" and "second~" described in this disclosure may refer to the same or different elements. For example, if the elements are information, the first information and the second information may both be information, and in some cases, they may be the same information or different information.

[0057] In addition, the expressions "if" and "in case that" described in the present disclosure or claims may be interpreted to mean "when or upon," "in response to," or "based on," or "according to," depending on the context, and these expressions may be used interchangeably. In addition, in addition to these expressions, other expressions having substantially the same meaning may be used interchangeably, within the scope that does not impair the technical features of the present disclosure.

[0058] Additionally, the term "not perform" as used in this disclosure or claims may be understood to mean omitting or skipping a step, depending on the context. Such terms may be replaced with other terms having the same or substantially similar meaning.

[0059] Additionally, "transmitting a message including A and B" as described herein may be interpreted to include both (i) cases where A and B are transmitted in a single message, as well as (ii) cases where A and B are transmitted individually via multiple messages (e.g., transmitting a first message including A and a second message including B). This interpretation may also apply when a message including two or more items, such as A, B, and C, is transmitted together or individually.

[0060] Additionally, 'sending a message containing A and sending a message containing B' can also be interpreted as sending a single message containing A and B.

[0061] In the specific embodiments of the present disclosure described below, terms or components included in the disclosure will be expressed in the singular or plural, depending on the specific embodiment presented. However, the singular or plural expressions are selected to suit the presented situation for convenience of explanation, and the present disclosure is not limited to singular or plural components. Components expressed in the plural may be composed of singular elements, or components expressed in the singular may be composed of plural elements.

[0062] The drawings or flowcharts described below illustrate exemplary methods that may be implemented according to the principles of the present disclosure, and various modifications may be made to the methods depicted in the flowcharts of the present disclosure. For example, although depicted as a series of steps, various steps in each drawing or flowchart may overlap, occur in parallel, occur in different orders, or occur multiple times. In other instances, any step may be omitted or replaced with another step.

[0063] The methods and devices proposed in the embodiments of the present disclosure are not limited to each embodiment, and may be utilized as a combination of one or more embodiments, all or part of the embodiments proposed in the disclosure. Accordingly, the embodiments of the present disclosure may be applied with some modifications within a scope that does not significantly deviate from the scope of the present disclosure, as determined by a person skilled in the art.

[0064] In this case, even if any wording is mentioned in different embodiments, if the concepts correspond, they may be used interchangeably, combined, or substituted. For example, for identical or corresponding concepts, even if one embodiment uses the expression "A" and another uses the expression "B," these may be understood interchangeably, substituted, or combined.

[0065] In the following description, terms used to identify connection nodes, terms referring to network entities, terms referring to messages, terms referring to interfaces between network entities, terms referring to various identification information, etc. are examples for convenience of explanation. Therefore, the present disclosure is not limited to the terms described below, and other terms referring to objects having equivalent technical meanings may be used. In addition, the terms may be replaced with terms defined in the 3rd generation partnership project (3GPP) Technical Specifications (TS), if appropriate.

[0066] Hereinafter, the base station is an entity that performs resource allocation of a terminal, and may be at least one of a gNode B, an eNode B, a Node B, a BS (base station), a radio access unit, a base station controller, or a node on a network. In addition, the base station of the present disclosure may include a structure that is split into a central unit (CU) and a distributed unit (DU). In this structure, the CU is responsible for the upper layers of the control and user planes, and the DU is responsible for radio resource processing of the lower layers. The embodiments of the present disclosure can be equally applied to a 5G base station structure in which functions are separated into the CU and DU.

[0067] The terminal may include a UE (user equipment), MS (mobile station), cellular phone, smartphone, computer, or multimedia system capable of performing communication functions.

[0068] In the present disclosure, downlink (DL) refers to a wireless transmission path of a signal transmitted from a base station to a terminal, and uplink (UL) refers to a wireless transmission path of a signal transmitted from a terminal to a base station.

[0069] In addition, although the fifth generation mobile communication system (5G, new radio, NR) and the sixth generation mobile communication system (6G) may be described below as examples, the embodiments of the present disclosure may also be applied to other communication systems having similar technical backgrounds or channel types. For example, this may include new evolved mobile communication systems developed after 5G and 6G. In addition, the present disclosure may be applied to other communication systems (e.g., Wi-Fi systems) with some modifications within a range that does not significantly deviate from the scope of the present disclosure, as determined by a person having skilled technical knowledge.

[0070] In the following description, the terms "physical channel" and "signal" may be used interchangeably with data or control signals. For example, while PDSCH (physical downlink shared channel) refers to a physical channel through which data is transmitted, PDSCH may also be used to refer to data. That is, in the present disclosure, the expression "transmitting a physical channel" may be interpreted equivalently to the expression "transmitting data or a signal through a physical channel."

[0071] In the following description of the present disclosure, upper layer signaling may be signaling corresponding to at least one or a combination of one or more of MIB (master information block), SIB (system information block), SIB M (M=1, 2, ...), RRC (radio resource control), MAC (medium access control) CE (control element), NAS (non-access stratum) signaling, or application layer messages. The RRC signaling may also be referred to as L3 signaling (layer 3 signaling).

[0072] In addition, L1 signaling may be signaling corresponding to at least one or a combination of one or more signaling methods using a physical layer channel or signaling of PDCCH (physical downlink control channel), DCI (downlink control information), UE-specific DCI, group common DCI, common DCI, scheduling DCI (e.g., DCI used for the purpose of scheduling downlink or uplink data), non-scheduling DCI (e.g., DCI not for the purpose of scheduling downlink or uplink data), physical uplink control channel (PUCCH), or uplink control information (UCI). The L1 signaling may also be referred to as physical layer signaling.

[0073] Hereinafter, the expression that information can be configured from a base station in the present disclosure or claims may mean that a terminal receives the information from the base station through physical layer signaling or upper layer signaling, depending on the context, and such expression may be replaced with other terms having the same or substantially similar meaning.

[0074] The operating principle of the present disclosure is described in detail with reference to the attached drawings below.

[0075] Wireless communication systems are evolving from providing voice-oriented services in the early days to broadband wireless communication systems that provide high-speed, high-quality packet data services, such as communication standards such as 3GPP's HSPA (High Speed ​​Packet Access), LTE (Long Term Evolution or E-UTRA (Evolved Universal Terrestrial Radio Access)), LTE-Advanced (LTE-A), LTE-Pro, 3GPP2's HRPD (High Rate Packet Data), UMB (Ultra Mobile Broadband), and IEEE's 802.16e.

[0076] As a representative example of the above broadband wireless communication system, the LTE system adopts the Orthogonal Frequency Division Multiplexing (OFDM) method in the downlink (DL) and the Single Carrier Frequency Division Multiple Access (SC-FDMA) method in the uplink (UL). The uplink refers to a wireless link in which a terminal (User Equipment (UE) or Mobile Station (MS)) transmits data or control signals to a base station (eNode B, gNode B, or base station (BS)), and the downlink refers to a wireless link in which a base station transmits data or control signals to a terminal. The above multiple access method can distinguish the data or control information of each user by allocating and operating the time-frequency resources for transmitting data or control information to each user so that they do not overlap, that is, so as to achieve orthogonality.

[0077] As the future communications system beyond LTE, 5G communication systems must be able to freely reflect the diverse needs of users and service providers. Therefore, they must support services that simultaneously satisfy these diverse requirements. Services being considered for 5G communication systems include enhanced Mobile Broadband (eMBB), massive Machine Type Communication (mMTC), and Ultra Reliability Low Latency Communication (URLLC).

[0078] eMBB aims to provide data transmission rates that are significantly higher than those supported by existing LTE, LTE-A, or LTE-Pro. For example, in a 5G communication system, eMBB must be able to support a peak data rate of 20 Gbps in the downlink and a peak data rate of 10 Gbps in the uplink from a single base station. Furthermore, 5G communication systems must simultaneously provide the peak data rate and an increased user-perceived data rate for terminals. To meet these requirements, improvements in various transmission and reception technologies, including improved multi-input, multi-output (MIMO) transmission technology, are required. Furthermore, while LTE transmits signals using a maximum 20 MHz transmission bandwidth in the 2 GHz band, 5G communication systems can meet the data transmission rates required by 5G communication systems by utilizing a wider frequency bandwidth than 20 MHz in the 3-6 GHz or higher 6 GHz bands.

[0079] At the same time, mMTC is being considered to support application services such as the Internet of Things (IoT) in 5G communication systems. To efficiently provide the IoT, mMTC requires supporting large-scale terminal connections within a cell, improved terminal coverage, enhanced battery life, and reduced terminal costs. The IoT requires the ability to support a large number of terminals (e.g., 1,000,000 terminals / km^2) within a cell, as it provides communication capabilities through the attachment of various sensors and devices. Furthermore, due to the nature of the service, terminals supporting mMTC are likely to be located in shadow areas not covered by cells, such as basements, and thus may require wider coverage than other services provided by 5G communication systems. Terminals supporting mMTC must be inexpensive, and since frequent battery replacement is unlikely, they may require extremely long battery lifespans, such as 10 to 15 years.

[0080] Finally, URLLC refers to cellular-based wireless communication services used for specific mission-critical purposes. Examples include remote control of robots or machinery, industrial automation, unmanned aerial vehicles (UAVs), remote health care, and emergency alerts. Therefore, URLLC communications must offer extremely low latency and high reliability. For example, URLLC-enabled services must meet air interface latency requirements of less than 0.5 milliseconds and a packet error rate (PER) of less than 10^-5. Therefore, for services supporting URLLC, 5G systems must provide shorter transmission time intervals (TTIs) than other services, and design considerations may require the allocation of extensive resources in the frequency band to ensure communication link reliability.

[0081] The three 5G services—eMBB, URLLC, and mMTC—can be multiplexed and transmitted within a single system. To meet the differing requirements of each service, different transmission and reception techniques and parameters can be used. Of course, 5G is not limited to the three services described above.

[0082] [NR time-frequency resources]

[0083] Below, the frame structure of the 5G system is described in more detail with reference to drawings.

[0084] FIG. 1 is a diagram illustrating the basic structure of the time-frequency domain in a wireless communication system according to one embodiment of the present disclosure. Specifically, FIG. 1 is a diagram illustrating the basic structure of the time-frequency domain, which is a wireless resource domain in which data or control channels are transmitted in a 5G system.

[0085] The horizontal axis of Figure 1 represents the time domain, and the vertical axis represents the frequency domain. The basic unit of resources in the time and frequency domains is a resource element (RE, 101), which can be defined as 1 OFDM (Orthogonal Frequency Division Multiplexing) symbol (102) on the time axis and 1 subcarrier (103) on the frequency axis. In the frequency domain (For example, 12) consecutive REs can form one resource block (RB, 104).

[0086] FIG. 2 is a diagram illustrating a frame, subframe, and slot structure in a wireless communication system according to one embodiment of the present disclosure.

[0087] Figure 2 illustrates an example of a structure of a frame (Frame, 200), a subframe (Subframe, 201), and a slot (Slot, 202). One frame (200) can be defined as 10 ms. One subframe (201) can be defined as 1 ms, and therefore one frame (200) can be composed of a total of 10 subframes (201). One slot (202, 203) can be defined as 14 OFDM symbols (i.e., the number of symbols per slot ( )=14). 1 subframe (201) may be composed of one or more slots (202, 203), and the number of slots (202, 203) per 1 subframe (201) may vary depending on the setting value μ (204, 205) for the subcarrier spacing. In an example of FIG. 2, the cases where μ = 0 (204) and μ = 1 (205) as the subcarrier spacing setting value are illustrated. When μ = 0 (204), 1 subframe (201) may be composed of 1 slot (202), and when μ = 1 (205), 1 subframe (201) may be composed of 2 slots (203). That is, the number of slots per 1 subframe ( ) may vary, and accordingly the number of slots per frame ( ) may vary. Depending on the subcarrier spacing setting μ and can be defined as shown in Table 1 below.

[0088]

[0089] [Bandwidth Part (BWP)]

[0090] Next, the bandwidth part (BWP) setting in the 5G communication system will be explained in detail with reference to the drawing.

[0091] FIG. 3 is a diagram illustrating an example of bandwidth portion settings in a wireless communication system according to one embodiment of the present disclosure.

[0092] Figure 3 shows an example in which the UE bandwidth (300) is set to two bandwidth portions, namely, bandwidth portion #1 (BWP#1) (301) and bandwidth portion #2 (BWP#2) (302). The base station can set one or more bandwidth portions to the UE, and can set information such as Table 2 below for each bandwidth portion.

[0093]

[0094] The configuration information is, of course, not limited to the above examples, and in addition to the configuration information, various parameters related to the bandwidth portion may be configured for the terminal. The above information may be transmitted from the base station to the terminal via upper layer signaling, for example, RRC (Radio Resource Control) signaling. At least one of the configured bandwidth portions may be activated. Whether or not the configured bandwidth portion is activated may be semi-statically transmitted from the base station to the terminal via RRC signaling or dynamically transmitted via DCI (Downlink Control Information).

[0095] According to some embodiments, a terminal before RRC (Radio Resource Control) connection can receive configuration information for an initial bandwidth portion (Initial BWP) for initial access from a base station through a Master Information Block (MIB). More specifically, the terminal can receive configuration information for a control region (Control Resource Set, CORESET) and a search space, through the MIB, in the initial access phase, where a PDCCH for receiving system information required for initial access (which may correspond to Remaining System Information (RMSI) or System Information Block 1 (SIB1)) can be transmitted. The control region and search space configured by the MIB may each be regarded as identifier (ID) 0. The base station can notify the terminal of configuration information such as frequency allocation information, time allocation information, and numerology for control region #0 through the MIB. In addition, the base station can notify the terminal of configuration information for a monitoring cycle and occasion for control region #0, i.e., configuration information for search space #0, through the MIB. The terminal may consider the frequency range set as control area #0 obtained from the MIB as the initial bandwidth portion for initial connection. At this time, the identifier (ID) of the initial bandwidth portion may be considered as 0.

[0096] The bandwidth settings supported by 5G systems can be used for various purposes.

[0097] In one embodiment, when the bandwidth supported by a terminal is smaller than the system bandwidth, this can be supported through bandwidth portion configuration. For example, the base station can configure the bandwidth portion frequency location (configuration information 2) for the terminal, thereby allowing the terminal to transmit and receive data at a specific frequency location within the system bandwidth.

[0098] Additionally, in some embodiments, a base station may configure multiple bandwidth segments for a terminal to support different numerologies. For example, to support data transmission and reception using both 15 kHz and 30 kHz subcarrier spacing for a given terminal, the base station may configure two bandwidth segments with subcarrier spacings of 15 kHz and 30 kHz, respectively. The different bandwidth segments may be frequency-division multiplexed, and when data is to be transmitted and received using a specific subcarrier spacing, the bandwidth segment configured for that subcarrier spacing may be activated.

[0099] Furthermore, according to one embodiment, for the purpose of reducing power consumption of the terminal, the base station can set bandwidth portions with different bandwidth sizes for the terminal. For example, if the terminal supports a very large bandwidth, such as 100 MHz, and constantly transmits and receives data using that bandwidth, very large power consumption may occur. In particular, monitoring unnecessary downlink control channels using a large bandwidth of 100 MHz in a traffic-free situation can be very inefficient in terms of power consumption. To reduce power consumption of the terminal, the base station can set a bandwidth portion with a relatively small bandwidth, such as 20 MHz, for the terminal. In a traffic-free situation, the terminal can perform monitoring operations in the 20 MHz bandwidth portion, and when data is generated, it can transmit and receive data using the 100 MHz bandwidth portion according to the instructions of the base station.

[0100] In the method for setting the bandwidth part described above, terminals before RRC connection can receive configuration information for the initial bandwidth part through the MIB (Master Information Block) during the initial access stage. More specifically, the terminal can receive a control region (Control Resource Set, CORESET) for a downlink control channel on which DCI (Downlink Control Information) that schedules a SIB (System Information Block) can be transmitted from the MIB of the PBCH (Physical Broadcast Channel). The bandwidth of the control region set by the MIB can be regarded as the initial bandwidth part, and the terminal can receive the PDSCH (Physical Downlink Shared Channel) on which the SIB is transmitted through the set initial bandwidth part. In addition to receiving the SIB, the initial bandwidth part can also be utilized for other system information (Other System Information, OSI), paging, and random access.

[0101] [Bandwidth Part (BWP) Change]

[0102] When one or more bandwidth parts are set for a terminal, the base station can instruct the terminal to change (or switch, transition) the bandwidth part using the bandwidth part indicator field in the DCI. For example, in FIG. 3, when the currently activated bandwidth part of the terminal is bandwidth part #1 (301), the base station can instruct the terminal to bandwidth part #2 (302) using the bandwidth part indicator in the DCI, and the terminal can perform a bandwidth part change to bandwidth part #2 (302) indicated by the bandwidth part indicator in the received DCI.

[0103] As mentioned above, since DCI-based bandwidth part changes can be indicated by the DCI scheduling the PDSCH or PUSCH, when a UE receives a bandwidth part change request, it must be able to seamlessly receive or transmit the PDSCH or PUSCH scheduled by the corresponding DCI in the changed bandwidth part. To this end, the standard stipulates requirements for the delay time (TBWP) required when changing the bandwidth part, which can be defined, for example, as shown in Table 3.

[0104]

[0105] The bandwidth-partial change delay time requirement supports Type 1 or Type 2 depending on the terminal's capability. The terminal can report the supported bandwidth-partial delay time type to the base station.

[0106] According to the requirement for bandwidth part change delay time mentioned above, when the terminal receives DCI including bandwidth part change indicator in slot n, the terminal changes to the new bandwidth part indicated by the bandwidth part change indicator in slot n+T. BWP It can be completed at a later time, and transmission and reception for the data channel scheduled by the DCI can be performed in the new bandwidth portion that has been changed. If the base station wants to schedule a data channel in the new bandwidth portion, the terminal's bandwidth portion change delay time (T BWP ), time domain resource allocation for the data channel can be determined. That is, when the base station schedules a data channel with a new bandwidth portion, the data channel can be scheduled after the bandwidth portion change delay time in the method of determining time domain resource allocation for the data channel. Accordingly, the terminal can determine whether the DCI instructing a bandwidth portion change is equal to the bandwidth portion change delay time (T BWP) may not be expected to indicate a slot offset (K0 or K2) value smaller than that.

[0107] If the terminal receives DCI (e.g., DCI format 1_1 or 0_1) indicating a bandwidth change, the terminal may not perform any transmission or reception during the time period from the third symbol of the slot in which the PDCCH including the DCI is received to the start of the slot indicated by the slot offset (K0 or K2) value indicated by the time domain resource allocation indicator field in the DCI. For example, if the terminal receives DCI indicating a bandwidth change in slot n and the slot offset value indicated by the DCI is K, the terminal may not perform any transmission or reception from the third symbol of slot n to the symbol before slot n+K (i.e., the last symbol of slot n+K-1).

[0108] [SS / PBCH block]

[0109] Next, we will explain the SS (Synchronization Signal) / PBCH block in the 5G system.

[0110] An SS / PBCH block may refer to a physical layer channel block consisting of a PSS (Primary SS), SSS (Secondary SS), and PBCH. Specifically, it is as follows.

[0111] - PSS: A signal that serves as a reference for downlink time / frequency synchronization and provides some information about the cell ID.

[0112] - SSS: It serves as a reference for downlink time / frequency synchronization and provides the remaining cell ID information not provided by PSS. Additionally, it can serve as a reference signal for PBCH demodulation.

[0113] - PBCH: Provides essential system information required for the terminal's data channel and control channel transmission and reception. Essential system information may include search space-related control information indicating radio resource mapping information for the control channel, and scheduling control information for a separate data channel that transmits system information.

[0114] - SS / PBCH Block: An SS / PBCH block is composed of a combination of PSS, SSS, and PBCH. One or more SS / PBCH blocks can be transmitted within a 5ms period, and each transmitted SS / PBCH block can be distinguished by an index.

[0115] The terminal can detect PSS and SSS in the initial access stage, and decode PBCH. The terminal can obtain MIB from PBCH, and can set control region (Control Resource Set; CORESET) #0 (which may correspond to a control region with a control region index of 0) therefrom. The terminal can monitor control region #0, assuming that the selected SS / PBCH block and the DMRS (Demodulation Reference Signal) transmitted in control region #0 are QCL (Quasi Co Location). The terminal can receive system information through downlink control information transmitted in control region #0. The terminal can obtain RACH (Random Access Channel) related configuration information required for initial access from the received system information. The terminal can transmit PRACH (Physical RACH) to the base station considering the selected SS / PBCH index, and the base station receiving the PRACH can obtain information on the SS / PBCH block index selected by the terminal. The base station can know that the terminal has selected a block among each SS / PBCH block and monitors the control region #0 associated with it.

[0116] [PDCCH: DCI related]

[0117] Next, we will specifically explain downlink control information (DCI) in the 5G system.

[0118] In a 5G system, scheduling information for uplink data (or physical uplink shared channel (PUSCH)) or downlink data (or physical downlink shared channel (PDSCH)) is transmitted from a base station to a terminal via DCI. The terminal can monitor a DCI format for fallback and a DCI format for non-fallback for the PUSCH or PDSCH. The fallback DCI format can be composed of fixed fields predefined between the base station and the terminal, and the non-fallback DCI format can include configurable fields.

[0119] DCI can be transmitted through the Physical Downlink Control Channel (PDCCH) after going through the channel coding and modulation process. A Cyclic Redundancy Check (CRC) is attached to the DCI message payload, and the CRC can be scrambled with a Radio Network Temporary Identifier (RNTI) corresponding to the identity of the UE. Different RNTIs can be used depending on the purpose of the DCI message, such as UE-specific data transmission, power control command, or random access response. That is, the RNTI is not transmitted explicitly, but is included in the CRC calculation process. When the UE receives a DCI message transmitted on the PDCCH, it verifies the CRC using the assigned RNTI. If the CRC verification result is correct, the UE can determine that the message was transmitted to the UE.

[0120] For example, a DCI scheduling a PDSCH for System Information (SI) may be scrambled with SI-RNTI. A DCI scheduling a PDSCH for a Random Access Response (RAR) message may be scrambled with RA-RNTI. A DCI scheduling a PDSCH for a Paging message may be scrambled with P-RNTI. A DCI notifying a Slot Format Indicator (SFI) may be scrambled with SFI-RNTI. A DCI notifying a Transmit Power Control (TPC) may be scrambled with TPC-RNTI. A DCI scheduling a UE-specific PDSCH or PUSCH may be scrambled with C-RNTI (Cell RNTI).

[0121] DCI format 0_0 can be used as a fallback DCI for scheduling PUSCH, in which case the CRC can be scrambled with C-RNTI. DCI format 0_0 with the CRC scrambled with C-RNTI can include, for example, the information in Table 4.

[0122]

[0123] DCI format 0_1 ​​can be used as a fallback DCI for scheduling PUSCH, in which case the CRC can be scrambled with C-RNTI. DCI format 0_1 ​​with the CRC scrambled with C-RNTI can include, for example, the information in Table 5.

[0124]

[0125]

[0126] DCI format 1_0 can be used as a fallback DCI for scheduling PDSCH, in which case the CRC can be scrambled with C-RNTI. DCI format 1_0 with the CRC scrambled with C-RNTI can include, for example, the information in Table 6.

[0127]

[0128] DCI format 1_1 can be used as a fallback DCI for scheduling PDSCH, in which case the CRC can be scrambled with C-RNTI. DCI format 1_1 with the CRC scrambled with C-RNTI can include, for example, the information in Table 7.

[0129]

[0130] [PDCCH: CORESET, REG, CCE, Search Space]

[0131] Below, the downlink control channel in a 5G communication system will be described in more detail with reference to drawings.

[0132] FIG. 4 is a diagram illustrating an example of setting a control region of a downlink control channel in a wireless communication system according to an embodiment of the present disclosure. FIG. 4 illustrates an example of a control region (Control Resource Set, CORESET) in which a downlink control channel is transmitted in a 5G wireless communication system. FIG. 4 illustrates an example in which two control regions (Control Region #1 (401), Control Region #2 (402)) are set within a UE bandwidth part (410) in the frequency axis and one slot (420) in the time axis. The control regions (401, 402) may be set to specific frequency resources (403) within the entire UE bandwidth part (410) in the frequency axis. The control regions (401, 402) may be set to one or more OFDM symbols in the time axis, and this may be defined as a control region length (Control Resource Set Duration, 404). Referring to the illustrated example of FIG. 4, control area #1 (401) is set to a control area length of 2 symbols, and control area #2 (402) is set to a control area length of 1 symbol.

[0133] In the aforementioned 5G system, the control region can be established by the base station to the terminal through higher-layer signaling (e.g., system information, Master Information Block (MIB), Radio Resource Control (RRC) signaling). The base station establishing a control region for the terminal means that the base station provides the terminal with information such as the control region identifier (Identity), the frequency location of the control region, and the symbol length of the control region. For example, this information may include the information in Table 8.

[0134]

[0135] In Table 8, the tci-StatesPDCCH (simply named TCI (Transmission Configuration Indication) state) configuration information may include information on one or more SS (Synchronization Signal) / PBCH (Physical Broadcast Channel) block indices or CSI-RS (Channel State Information Reference Signal) indices that are in a QCL (Quasi Co Located) relationship with the DMRS transmitted in the corresponding control region.

[0136] FIG. 5 is a diagram illustrating the structure of a downlink control channel in a wireless communication system according to one embodiment of the present disclosure.

[0137] Fig. 5 shows an example of a basic unit of time and frequency resources that constitute a downlink control channel that can be used in a 5G system. According to Fig. 5, the basic unit of time and frequency resources that constitute a control channel can be referred to as a REG (Resource Element Group, 503), and a REG (503) can be defined as 1 OFDM symbol (501) on the time axis and 1 PRB (Physical Resource Block, 502) on the frequency axis, i.e., 12 subcarriers. A base station can concatenate REGs (503) to constitute a downlink control channel allocation unit.

[0138] As illustrated in FIG. 5, if the basic unit to which a downlink control channel is allocated in a 5G system is called a CCE (Control Channel Element, 504), 1 CCE (504) can be composed of multiple REGs (503). Taking the REG (503) illustrated in FIG. 5 as an example, the REG (503) can be composed of 12 REs, and if 1 CCE (504) is composed of 6 REGs (503), 1 CCE (504) can be composed of 72 REs. When a downlink control region is set, the region can be composed of multiple CCEs (504), and a specific downlink control channel can be mapped to one or multiple CCEs (504) and transmitted according to the aggregation level (AL) within the control region. CCEs (504) within the control area are distinguished by numbers, and the numbers of the CCEs (504) can be assigned according to a logical mapping method.

[0139] The basic unit of the downlink control channel illustrated in FIG. 5, that is, the REG (503), may include both the REs to which the DCI is mapped and the areas to which the DMRS (505), which is a reference signal for decoding the REs, is mapped. As shown in FIG. 5, three DMRSs (505) may be transmitted within one REG (503). The number of CCEs required to transmit the PDCCH may be 1, 2, 4, 8, or 16 depending on the aggregation level (AL), and different numbers of CCEs may be used to implement link adaptation of the downlink control channel. For example, when AL = L, one downlink control channel may be transmitted through L CCEs. The terminal must detect a signal without knowing information about the downlink control channel, and a search space representing a set of CCEs is defined for blind decoding. A search space is a set of downlink control channel candidates (CCEs) that a terminal must attempt to decode at a given aggregation level. Since there are multiple aggregation levels, each of which can be a set of 1, 2, 4, 8, or 16 CCEs, a terminal can have multiple search spaces. A search space set can be defined as the set of search spaces at all configured aggregation levels.

[0140] Search spaces can be categorized into common search spaces and UE-specific search spaces. A certain group of UEs, or all UEs, can search the common search space of the PDCCH to receive cell-common control information, such as dynamic scheduling of system information or paging messages. For example, PDSCH scheduling allocation information for transmitting SIBs, including cell operator information, can be received by searching the common search space of the PDCCH. In the case of the common search space, since a certain group of UEs, or all UEs, must receive the PDCCH, it can be defined as a set of pre-arranged CCEs. Scheduling allocation information for UE-specific PDSCH or PUSCH can be received by searching the UE-specific search space of the PDCCH. The UE-specific search space can be defined UE-specifically as a function of the UE's identity and various system parameters.

[0141] In a 5G system, parameters for a search space for PDCCH can be configured from a base station to a terminal via higher layer signaling (e.g., SIB, MIB, RRC signaling). For example, the base station can configure the number of PDCCH candidates at each aggregation level L, the monitoring period for the search space, the monitoring occasion for each symbol within the slot for the search space, the search space type (common search space or terminal-specific search space), the combination of DCI format and RNTI to be monitored in the corresponding search space, the control region index to be monitored for the search space, etc. to the terminal. For example, the parameters for a search space for PDCCH can include the information in Table 9.

[0142]

[0143]

[0144] Depending on the configuration information, the base station may configure one or more search space sets for the terminal. In some embodiments, the base station may configure search space set 1 and search space set 2 for the terminal, and may configure the terminal to monitor DCI format A scrambled with X-RNTI in search space set 1 in a common search space, and may configure the terminal to monitor DCI format B scrambled with Y-RNTI in search space set 2 in a terminal-specific search space.

[0145] According to the configuration information, one or more search space sets may exist in a common search space or a terminal-specific search space. For example, search space set #1 and search space set #2 may be configured as a common search space, and search space set #3 and search space set #4 may be configured as terminal-specific search spaces.

[0146] In the common search space, the following combinations of DCI formats and RNTIs can be monitored. Of course, the examples below are not limited to these.

[0147] - DCI format 0_0 / 1_0 with CRC scrambled by C-RNTI, CS-RNTI, SP-CSI-RNTI, RA-RNTI, TC-RNTI, P-RNTI, SI-RNTI

[0148] - DCI format 2_0 with CRC scrambled by SFI-RNTI

[0149] - DCI format 2_1 with CRC scrambled by INT-RNTI

[0150] - DCI format 2_2 with CRC scrambled by TPC-PUSCH-RNTI, TPC-PUCCH-RNTI

[0151] - DCI format 2_3 with CRC scrambled by TPC-SRS-RNTI

[0152] In a terminal-specific search space, the following combinations of DCI formats and RNTIs can be monitored. Of course, the examples below are not limited to these examples.

[0153] - DCI format 0_0 / 1_0 with CRC scrambled by C-RNTI, CS-RNTI, TC-RNTI

[0154] - DCI format 1_0 / 1_1 with CRC scrambled by C-RNTI, CS-RNTI, TC-RNTI

[0155] The RNTIs specified may follow the definitions and uses below.

[0156] C-RNTI (Cell RNTI): For terminal-specific PDSCH scheduling purposes

[0157] TC-RNTI (Temporary Cell RNTI): For terminal-specific PDSCH scheduling purposes

[0158] CS-RNTI (Configured Scheduling RNTI): Used for terminal-specific PDSCH scheduling that is set semi-statically.

[0159] RA-RNTI (Random Access RNTI): Used for PDSCH scheduling in the random access phase.

[0160] P-RNTI (Paging RNTI): Used for scheduling PDSCH where paging is transmitted.

[0161] SI-RNTI (System Information RNTI): Used for scheduling PDSCH where system information is transmitted.

[0162] INT-RNTI (Interruption RNTI): Used to indicate whether PDSCH is punctured.

[0163] TPC-PUSCH-RNTI (Transmit Power Control for PUSCH RNTI): Used to indicate power control commands for PUSCH.

[0164] TPC-PUCCH-RNTI (Transmit Power Control for PUCCH RNTI): Used to indicate power control commands for PUCCH.

[0165] TPC-SRS-RNTI (Transmit Power Control for SRS RNTI): Used to indicate power control commands for SRS.

[0166] The aforementioned specified DCI formats may follow definitions such as the examples in Table 10.

[0167]

[0168] In a 5G system, the search space of aggregation level L in a control region p and a search space set s can be expressed as in the following mathematical expression 1.

[0169] [Mathematical Formula 1]

[0170]

[0171] - Integration level

[0172] - Carrier Index

[0173] - Total number of CCEs existing within the control region p

[0174] - Slot Index

[0175] - Number of PDCCH candidates for aggregation level L

[0176] - PDCCH candidate index for aggregation level L

[0177] -

[0178] -

[0179] - : Terminal identifier

[0180] The value can be 0 for a common search space.

[0181] In the case of a terminal-specific search space, the value may correspond to a value that changes depending on the terminal's identity (C-RNTI or ID set to the terminal by the base station) and the time index.

[0182] In a 5G system, since multiple search space sets can be set with different parameters (e.g., parameters in Table 9), the set of search space sets monitored by a terminal at each point in time can be different. For example, if search space set #1 is set with an X-slot period and search space set #2 is set with a Y-slot period and X and Y are different, the terminal can monitor both search space set #1 and search space set #2 in a specific slot, or can monitor either search space set #1 or search space set #2 in a specific slot.

[0183] [PDCCH: BD / CCE limit]

[0184] When multiple search space sets are set for a terminal, the following conditions may be considered in determining the search space set that the terminal should monitor.

[0185] If the value of monitoringCapabilityConfig-r16, which is an upper layer signaling, is set to r15monitoringcapability, the terminal defines the maximum values ​​for the number of PDCCH candidates that can be monitored and the number of CCEs that constitute the entire search space (wherein the entire search space means the entire set of CCEs corresponding to the union area of ​​multiple search space sets) per slot, and if the value of monitoringCapabilityConfig-r16 is set to r16monitoringcapability, the terminal defines the maximum values ​​for the number of PDCCH candidates that can be monitored and the number of CCEs that constitute the entire search space (wherein the entire search space means the entire set of CCEs corresponding to the union area of ​​multiple search space sets) per Span.

[0186] [Condition 1: Limit the maximum number of PDCCH candidates]

[0187] As described above, depending on the setting value of the upper layer signaling, the maximum number of PDCCH candidates that the terminal can monitor is M. μ is a subcarrier spacing of 15·2 μ When defined by slot in a cell set to kHz, Table 11 below can be followed, and when defined by span, Table 12 below can be followed.

[0188]

[0189]

[0190] [Condition 2: Maximum CCE limit]

[0191] As above, according to the setting value of the upper layer signaling, the maximum number of CCEs that constitute the entire search space (here, the entire search space means the entire set of CCEs corresponding to the union area of ​​multiple search space sets) is C μ is a subcarrier spacing of 15·2 μWhen defined by slot in a cell set to kHz, Table 13 below may be followed, and when defined by span, Table 14 below may be followed.

[0192]

[0193]

[0194] For convenience of explanation, let us define a situation where both conditions 1 and 2 are satisfied at a certain point in time as “condition A.” Therefore, not satisfying condition A may mean not satisfying at least one of conditions 1 and 2.

[0195] [PDCCH: Overbooking]

[0196] Depending on the configuration of the search space sets of the base station, there may be cases where condition A is not satisfied at a certain point in time. If condition A is not satisfied at a certain point in time, the terminal can select and monitor only some of the search space sets configured to satisfy condition A at that point in time, and the base station can transmit a PDCCH to the selected search space set.

[0197] The following method can be followed to select a partial search space from the entire set of search spaces.

[0198] If condition A for PDCCH is not satisfied at a specific point in time (slot), the terminal (or base station) may preferentially select a search space set whose search space type is set to a common search space from among the search space sets existing at that point in time over a search space set whose search space type is set to a terminal-specific search space.

[0199] If all search space sets set as common search spaces are selected (i.e., if condition A is satisfied even after selecting all search spaces set as common search spaces), the terminal (or base station) can select search space sets set as terminal-specific search spaces. At this time, if there are multiple search space sets set as terminal-specific search spaces, a search space set with a lower search space set index may have a higher priority. The terminal (or base station) can select terminal-specific search space sets within the range where condition A is satisfied, taking the priority into consideration.

[0200] [Rate matching / Puncturing related]

[0201] Below, the rate matching operation and puncturing operation are described in detail.

[0202] When a time and frequency resource A, through which an arbitrary symbol sequence A is to be transmitted, overlaps with an arbitrary time and frequency resource B, a rate matching or puncturing operation may be considered for transmission and reception operations of channel A considering resource C, an area in which resources A and B overlap. The specific operations may follow the contents below.

[0203] Rate Matching Operation

[0204] - The base station can map and transmit channel A only for the remaining resource areas excluding resource C corresponding to the overlapping area with resource B among the entire resources A that are trying to transmit symbol sequence A to the terminal. For example, if symbol sequence A is composed of {symbol #1, symbol #2, symbol #3, symbol #4}, resource A is {resource #1, resource #2, resource #3, resource #4}, and resource B is {resource #3, resource #5}, the base station can sequentially map and transmit symbol sequence A to {resource #1, resource #2, resource #4}, which are the remaining resources among resource A excluding {resource #3} corresponding to resource C. As a result, the base station can map and transmit symbol sequences {symbol #1, symbol #2, symbol #3} to {resource #1, resource #2, resource #4}, respectively.

[0205] The terminal can determine resources A and B from scheduling information for symbol sequence A from the base station, and can thereby determine resource C, which is an area where resources A and B overlap. The terminal can receive symbol sequence A, assuming that symbol sequence A was mapped and transmitted in the remaining area of ​​the entire resource A except for resource C. For example, if symbol sequence A is composed of {symbol #1, symbol #2, symbol #3, symbol #4}, and resource A is {resource #1, resource #2, resource #3, resource #4}, and resource B is {resource #3, resource #5}, the terminal can receive symbol sequence A, assuming that it was sequentially mapped to {resource #1, resource #2, resource #4}, which are the remaining resources of resource A except {resource #3}, which corresponds to resource C. As a result, the terminal can perform a series of subsequent reception operations, assuming that symbol sequences {symbol #1, symbol #2, symbol #3} were mapped and transmitted to {resource #1, resource #2, resource #4}, respectively.

[0206] Puncture action

[0207] When a base station wants to transmit symbol sequence A to a terminal, if there is a resource C corresponding to an area overlapping with resource B among all resources A, the base station maps symbol sequence A to the entire resource A, but does not perform transmission in the resource area corresponding to resource C, and can perform transmission only for the remaining resource areas of resource A excluding resource C. For example, if symbol sequence A is composed of {symbol #1, symbol #2, symbol #3, symbol #4}, resource A is {resource #1, resource #2, resource #3, resource #4}, and resource B is {resource #3, resource #5}, the base station can map symbol sequence A {symbol #1, symbol #2, symbol #3, symbol #4} to resource A {resource #1, resource #2, resource #3, resource #4}, and transmit only the symbol sequence {symbol #1, symbol #2, symbol #4} corresponding to the remaining resources {resource #1, resource #2, resource #4} excluding {resource #3} corresponding to resource C among resources A, and may not transmit {symbol #3} mapped to {resource #3} corresponding to resource C. As a result, the base station can transmit symbol sequences {symbol #1, symbol #2, symbol #4} by mapping them to {resource #1, resource #2, resource #4}, respectively.

[0208] The terminal can determine resources A and B from scheduling information for symbol sequence A from the base station, and can thereby determine resource C, which is an area where resources A and B overlap. The terminal can receive symbol sequence A assuming that symbol sequence A is mapped to the entire resource A, but is transmitted only in the remaining area of ​​resource area A excluding resource C. For example, if symbol sequence A is composed of {symbol #1, symbol #2, symbol #3, symbol #4}, resource A is {resource #1, resource #2, resource #3, resource #4}, and resource B is {resource #3, resource #5}, the terminal can assume that symbol sequence A {symbol #1, symbol #2, symbol #3, symbol #4} is mapped to resource A {resource #1, resource #2, resource #3, resource #4} respectively, but {symbol #3} mapped to {resource #3} corresponding to resource C is not transmitted, and can receive it assuming that symbol sequence {symbol #1, symbol #2, symbol #4} corresponding to {resource #1, resource #2, resource #4}, which are the remaining resources among resource A except {resource #3} corresponding to resource C, are mapped and transmitted. As a result, the terminal can assume that the symbol sequence {symbol #1, symbol #2, symbol #4} is transmitted by being mapped to {resource #1, resource #2, resource #4}, respectively, and perform a series of subsequent receiving operations.

[0209] Below, we describe a method for configuring rate-matching resources for the purpose of rate-matching in 5G communication systems. Rate-matching refers to adjusting the size of a signal based on the amount of resources available for transmission. For example, rate-matching a data channel may mean adjusting the size of data accordingly, without mapping the data channel to a specific time and frequency resource region.

[0210] FIG. 6 is a diagram for explaining a method for a base station and a terminal to transmit and receive data by considering a downlink data channel and rate matching resources according to one embodiment of the present disclosure.

[0211] FIG. 6 illustrates a downlink data channel (PDSCH, 601) and a rate matching resource (602). A base station can configure one or more rate matching resources (602) to a terminal through upper layer signaling (e.g., RRC signaling). Rate matching resource (602) configuration information may include time-domain resource allocation information (603), frequency-domain resource allocation information (604), and period information (605). In the following, the bitmap corresponding to the frequency-domain resource allocation information (604) is named “first bitmap,” the bitmap corresponding to the time-domain resource allocation information (603) is named “second bitmap,” and the bitmap corresponding to the period information (605) is named “third bitmap.” If all or part of the time and frequency resources of the scheduled data channel (601) overlap with the set rate matching resources (602), the base station can rate-match and transmit the data channel (601) in the rate matching resource (602) portion, and the terminal can perform reception and decoding after assuming that the data channel (601) is rate-matched in the rate matching resource (602) portion.

[0212] The base station can dynamically notify the terminal via DCI whether to rate-match the data channel in the set rate-matching resource portion through additional configuration (corresponding to the “rate-matching indicator” in the aforementioned DCI format). Specifically, the base station can select some of the set rate-matching resources and group them into rate-matching resource groups, and can use a bitmap to indicate to the terminal via DCI whether the data channel for each rate-matching resource group is rate-matched. For example, if four rate-matching resources, RMR#1, RMR#2, RMR#3, and RMR#4, are set, the base station can set RMG#1={RMR#1, RMR#2}, RMG#2={RMR#3, RMR#4} as the rate-matching groups, and can use two bits in the DCI field to indicate to the terminal whether to rate-match in RMG#1 and RMG#2, respectively, using a bitmap. For example, if rate matching is required, it can be indicated as “1”, and if rate matching is not required, it can be indicated as “0”.

[0213] In 5G systems, granularity at the "RB symbol level" and "RE level" is supported by setting the aforementioned rate matching resources on terminals. More specifically, the following configuration method can be followed.

[0214] RB symbol level

[0215] A terminal can receive up to four RateMatchPatterns for each bandwidth section through upper layer signaling, and one RateMatchPattern can include the following contents.

[0216] - As a reserved resource within the bandwidth section, a resource in which the time and frequency resource domains of the reserved resource are set by combining a bitmap at the RB level and a bitmap at the symbol level along the frequency axis may be included. The reserved resource may span one or two slots. A time domain pattern (periodicityAndPattern) in which the time and frequency domains composed of each RB level and symbol level bitmap pair are repeated may additionally be set.

[0217] - It may include a time and frequency domain resource area set as a control resource set within the bandwidth section and a resource area corresponding to a time domain pattern set as a search space setting in which the resource area is repeated.

[0218] RE level

[0219] The terminal can be configured with the following contents through upper layer signaling.

[0220] - The configuration information (lte-CRS-ToMatchAround) for RE corresponding to the LTE CRS (Cell-specific Reference Signal or Common Reference Signal) pattern may include the number of LTE CRS ports (nrofCRS-Ports) and the LTE-CRS-vshift(s) value (v-shift), the location information (carrierFreqDL) of the center subcarrier of the LTE carrier from the reference frequency point (e.g., reference point A), the bandwidth size (carrierBandwidthDL) information of the LTE carrier, and the subframe configuration information (mbsfn-SubframConfigList) corresponding to the MBSFN (Multicast-broadcast single-frequency network). Based on the above-described information, the terminal can determine the location of the CRS within the NR slot corresponding to the LTE subframe.

[0221] - It may include configuration information for a set of resources corresponding to one or more ZP (Zero Power) CSI-RSs within the bandwidth section.

[0222] [Regarding LTE CRS rate match]

[0223] Next, the rate match process for the LTE CRS described above will be described in detail. In order to coexist between LTE (Long Term Evolution) and NR (New RAT) (LTE-NR Coexistence), NR provides a function to set a pattern of LTE's CRS (Cell Specific Reference Signal) to NR terminals. More specifically, the CRS pattern can be provided by RRC signaling including at least one parameter in the ServingCellConfig IE (Information Element) or ServingCellConfigCommon IE. Examples of the parameters can include lte-CRS-ToMatchAround, lte-CRS-PatternList1-r16, lte-CRS-PatternList2-r16, crs-RateMatch-PerCORESETPoolIndex-r16, etc.

[0224] In Rel-15 NR, the lte-CRS-ToMatchAround parameter provides a function that allows one CRS pattern to be set per serving cell. In Rel-16 NR, the function has been extended to allow multiple CRS patterns to be set per serving cell. More specifically, a single-TRP (transmission and reception point) configured terminal can have one CRS pattern set per LTE carrier, and a multi-TRP configured terminal can have two CRS patterns set per LTE carrier. For example, a single-TRP configured terminal can have up to three CRS patterns set per serving cell through the lte-CRS-PatternList1-r16 parameter. As another example, a multi-TRP configured terminal can have CRS set per TRP. That is, the CRS pattern for TRP1 can be set via the lte-CRS-PatternList1-r16 parameter, and the CRS pattern for TRP2 can be set via the lte-CRS-PatternList2-r16 parameter. Meanwhile, when two TRPs are set as above, whether both the CRS patterns of TRP1 and TRP2 or only the CRS pattern for one TRP is applied to a specific PDSCH (Physical Downlink Shared Channel) is determined via the crs-RateMatch-PerCORESETPoolIndex-r16 parameter. If the crs-RateMatch-PerCORESETPoolIndex-r16 parameter is set to enabled, only the CRS pattern of one TRP is applied, and in other cases, the CRS patterns of both TRPs are applied.

[0225] Table 15 shows a ServingCellConfig IE that includes the above CRS pattern, and Table 16 shows a RateMatchPatternLTE-CRS IE that includes at least one parameter for the CRS pattern.

[0226]

[0227]

[0228]

[0229]

[0230]

[0231] [PDSCH: Frequency Resource Allocation Related]

[0232] FIG. 7 is a diagram illustrating an example of frequency-axis resource allocation of PDSCH in a wireless communication system according to an embodiment of the present disclosure.

[0233] FIG. 7 is a diagram illustrating three frequency axis resource allocation methods, type 0 (700), type 1 (705), and dynamic switch (710), which can be set through an upper layer in an NR wireless communication system.

[0234] Referring to Fig. 7, if a terminal is set to use only resource type 0 through upper layer signaling (700), some downlink control information (DCI) that allocates PDSCH to the terminal includes a bitmap composed of NRBG bits. The conditions for this will be explained later. At this time, NRBG means the number of RBGs (resource block groups) determined according to the BWP size allocated by the BWP indicator and the upper layer parameter rbg-Size as shown in [Table 17] below, and data is transmitted to the RBG indicated as 1 by the bitmap.

[0235]

[0236] If the terminal is configured to use only resource type 1 through upper layer signaling (705), some DCIs that allocate PDSCH to the terminal It includes frequency axis resource allocation information consisting of bits. The conditions for this will be explained later. Through this, the base station can set the starting VRB (720) and the length (725) of frequency axis resources allocated continuously therefrom.

[0237] If a terminal is configured to use both resource type 0 and resource type 1 through upper layer signaling (710), some DCIs that allocate PDSCH to the terminal include frequency-axis resource allocation information composed of bits of a larger value (735) among the payload (715) for configuring resource type 0 and the payload (720, 725) for configuring resource type 1. Conditions for this will be explained later. At this time, one bit may be added to the first part (MSB) of the frequency-axis resource allocation information in the DCI, and if the bit has a value of '0', it may indicate that resource type 0 is used, and if the bit has a value of '1', it may indicate that resource type 1 is used.

[0238] [PDSCH / PUSCH: Time Resource Allocation Related]

[0239] Below, a time domain resource allocation method for data channels in next-generation mobile communication systems (5G or NR systems) is described.

[0240] A base station can set up a table for time domain resource allocation information for a downlink data channel (Physical Downlink Shared Channel, PDSCH) and an uplink data channel (Physical Uplink Shared Channel, PUSCH) to a terminal through higher layer signaling (e.g., RRC signaling). A table with up to maxNrofDL-Allocations=16 entries can be set up for PDSCH, and a table with up to maxNrofUL-Allocations=16 entries can be set up for PUSCH. In one embodiment, the time domain resource allocation information may include PDCCH-to-PDSCH slot timing (corresponding to the time interval in slot units between the time point at which a PDCCH is received and the time point at which a PDSCH scheduled by the received PDCCH is transmitted, denoted as K0), PDCCH-to-PUSCH slot timing (corresponding to the time interval in slot units between the time point at which a PDCCH is received and the time point at which a PUSCH scheduled by the received PDCCH is transmitted, denoted as K2), information on the position and length of the start symbol for which a PDSCH or PUSCH is scheduled within a slot, the mapping type of the PDSCH or PUSCH, etc. For example, information such as [Table 18] or [Table 19] below may be transmitted from the base station to the terminal.

[0241]

[0242]

[0243] The base station can notify the terminal of one of the entries in the table for the time domain resource allocation information described above via L1 signaling (e.g., DCI). For example, this may be indicated by the "Time Domain Resource Allocation" field in the DCI. The terminal can obtain time domain resource allocation information for the PDSCH or PUSCH based on the DCI received from the base station.

[0244] FIG. 8 is a diagram illustrating an example of time axis resource allocation of PDSCH in a wireless communication system according to one embodiment of the present disclosure.

[0245] Referring to FIG. 8, the base station uses the upper layer to set the subcarrier spacing (SCS) (μ) of the data channel and the control channel. PDSCH , μ PDCCH ), scheduling offset (K0) value, and the time axis position of the PDSCH resource can be indicated according to the OFDM symbol start position (800) and length (805) within a slot (810) dynamically indicated through DCI.

[0246] FIG. 9 is a diagram illustrating an example of time-domain resource allocation according to subcarrier spacing of a data channel and a control channel in a wireless communication system according to one embodiment of the present disclosure.

[0247] Referring to Fig. 9, when the subcarrier spacing of the data channel and the control channel is the same (900, μ PDSCH = μ PDCCH), since the slot numbers for data and control are the same, the base station and the terminal can generate a scheduling offset according to the predetermined slot offset K0. On the other hand, when the subcarrier spacing of the data channel and the control channel are different (905) (μ PDSCH ≠ μ PDCCH ), since the slot numbers for data and control are different, the base station and the terminal can generate a scheduling offset according to a predetermined slot offset K0 based on the subcarrier interval of the PDCCH.

[0248] [PUSCH: Transmission Method Related]

[0249] Next, we describe the scheduling method for PUSCH transmission. PUSCH transmission can be dynamically scheduled by the UL grant within the DCI or can operate by configured grant Type 1 or Type 2. Dynamic scheduling instructions for PUSCH transmission are possible in DCI format 0_0 or 0_1.

[0250] Configured grant Type 1 PUSCH transmission can be semi-statically configured by receiving configuredGrantConfig including rrc-ConfiguredUplinkGrant of [Table 20] through higher-order signaling, without receiving UL grant in DCI. Configured grant Type 2 PUSCH transmission can be semi-persistently scheduled by UL grant in DCI after receiving configuredGrantConfig not including rrc-ConfiguredUplinkGrant of [Table 20] through higher-order signaling. When PUSCH transmission operates by configured grant, parameters applied to PUSCH transmission are applied through configuredGrantConfig of higher-order signaling of [Table 20], except for dataScramblingIdentityPUSCH, txConfig, codebookSubset, maxRank, and scaling of UCI-OnPUSCH provided by pusch-Config of [Table 21]. If the terminal has been provided with transformPrecoder in configuredGrantConfig, which is the upper signaling of [Table 20], the terminal applies tp-pi2BPSK in pusch-Config of [Table 21] to PUSCH transmission operated by the configured grant.

[0251]

[0252]

[0253] Next, the PUSCH transmission method is described. The DMRS antenna port for PUSCH transmission is the same as the antenna port for SRS transmission. PUSCH transmission can follow a codebook-based or non-codebook-based transmission method, respectively, depending on whether the value of txConfig in the upper signaling, pusch-Config in [Table 21], is 'codebook' or 'nonCodebook'.

[0254] As described above, PUSCH transmission can be dynamically scheduled via DCI format 0_0 or 0_1, and can be semi-statically configured by configured grant. If the UE is instructed to schedule PUSCH transmission via DCI format 0_0, the UE performs beam configuration for PUSCH transmission using pucch-spatialRelationInfoID corresponding to the UE-specific PUCCH resource corresponding to the minimum ID within the activated uplink BWP within the serving cell, and at this time, the PUSCH transmission is based on a single antenna port. The UE does not expect scheduling for PUSCH transmission via DCI format 0_0 within a BWP where a PUCCH resource including pucch-spatialRelationInfo is not configured. If the UE does not configure txConfig in pusch-Config of [Table 21], the UE does not expect to be scheduled with DCI format 0_1.

[0255]

[0256]

[0257] Next, we describe codebook-based PUSCH transmission. Codebook-based PUSCH transmission can be dynamically scheduled via DCI format 0_0 or 0_1, and can operate semi-statically based on a configured grant. When codebook-based PUSCH is dynamically scheduled via DCI format 0_1 ​​or semi-statically configured via a configured grant, the UE can determine a precoder for PUSCH transmission based on the SRS Resource Indicator (SRI), the Transmission Precoding Matrix Indicator (TPMI), and the transmission rank (the number of PUSCH transmission layers).

[0258] At this time, the SRI can be given through the SRS resource indicator field in the DCI or configured through the srs-ResourceIndicator higher-level signaling. The UE is configured with at least one SRS resource when transmitting a codebook-based PUSCH, and can be configured with up to two. When the UE receives an SRI through the DCI, the SRS resource indicated by the SRI refers to the SRS resource corresponding to the SRI among the SRS resources transmitted before the PDCCH containing the SRI. In addition, the TPMI and transmission rank can be given through the precoding information and number of layers fields in the DCI or configured through the precodingAndNumberOfLayers higher-level signaling. The TPMI is used to indicate the precoder applied to the PUSCH transmission. If the UE is configured with one SRS resource, the TPMI is used to indicate the precoder to be applied to the configured one SRS resource. When a terminal is configured with multiple SRS resources, TPMI is used to indicate the precoder to be applied in the SRS resource indicated through SRI.

[0259] The precoder to be used for PUSCH transmission is selected from an uplink codebook having the same number of antenna ports as the nrofSRS-Ports value in the upper layer signaling, SRS-Config. In codebook-based PUSCH transmission, the UE determines the codebook subset based on the TPMI and codebookSubset in the upper layer signaling, pusch-Config. The codebookSubset in the upper layer signaling, pusch-Config, can be set to one of 'fullyAndPartialAndNonCoherent', 'partialAndNonCoherent', or 'nonCoherent' based on the UE capability reported by the UE to the base station. If the UE reported 'partialAndNonCoherent' as the UE capability, the UE does not expect the value of codebookSubset in the upper layer signaling to be set to 'fullyAndPartialAndNonCoherent'. Additionally, if the UE reports 'nonCoherent' as the UE capability, the UE does not expect the value of the upper signaling codebookSubset to be set to 'fullyAndPartialAndNonCoherent' or 'partialAndNonCoherent'. If nrofSRS-Ports in the upper signaling SRS-ResourceSet points to two SRS antenna ports, the UE does not expect the value of the upper signaling codebookSubset to be set to 'partialAndNonCoherent'.

[0260] The terminal can be configured with one SRS resource set in which the usage value in the upper signaling SRS-ResourceSet is set to 'codebook', and one SRS resource in the SRS resource set can be indicated via SRI. If multiple SRS resources are configured in the SRS resource set in which the usage value in the upper signaling SRS-ResourceSet is set to 'codebook', the terminal expects that the value of nrofSRS-Ports in the upper signaling SRS-Resource is set to the same value for all SRS resources.

[0261] The terminal transmits to the base station one or more SRS resources included in the SRS resource set in which the usage value is set to 'codebook' according to upper signaling, and the base station selects one of the SRS resources transmitted by the terminal and instructs the terminal to perform PUSCH transmission using transmission beam information of the corresponding SRS resource. At this time, in codebook-based PUSCH transmission, the SRI is used as information for selecting an index of one SRS resource and is included in the DCI. Additionally, the base station includes in the DCI information indicating a TPMI and rank to be used by the terminal for PUSCH transmission. The terminal performs PUSCH transmission by applying the indicated rank and the precoder indicated by the TPMI based on the transmission beam of the corresponding SRS resource using the SRS resource indicated by the SRI.

[0262] Next, we describe non-codebook-based PUSCH transmission. Non-codebook-based PUSCH transmission can be dynamically scheduled via DCI format 0_0 or 0_1, and can operate semi-statically based on a configured grant. If at least one SRS resource is configured within an SRS resource set in which the usage value in the upper signaling, SRS-ResourceSet, is set to 'nonCodebook', the UE can be scheduled for non-codebook-based PUSCH transmission via DCI format 0_1.

[0263] For an SRS resource set in which the usage value in the upper signaling SRS-ResourceSet is set to 'nonCodebook', the UE can be configured with one connected NZP CSI-RS resource (non-zero power CSI-RS). The UE can perform calculations for a precoder for SRS transmission by measuring the NZP CSI-RS resource connected to the SRS resource set. If the difference between the last received symbol of the aperiodic NZP CSI-RS resource connected to the SRS resource set and the first symbol of the aperiodic SRS transmission at the UE is less than 42 symbols, the UE does not expect information about the precoder for SRS transmission to be updated.

[0264] If the value of resourceType in the upper signaling SRS-ResourceSet is set to 'aperiodic', the connected NZP CSI-RS is indicated by the SRS request field in DCI format 0_1 ​​or 1_1. At this time, if the connected NZP CSI-RS resource is an aperiodic NZP CSI-RS resource, the presence of the connected NZP CSI-RS is indicated when the value of the SRS request field in DCI format 0_1 ​​or 1_1 is not '00'. At this time, the DCI must not indicate cross-carrier or cross BWP scheduling. In addition, if the value of the SRS request indicates the presence of an NZP CSI-RS, the NZP CSI-RS is located in the slot in which the PDCCH including the SRS request field is transmitted. At this time, the TCI states set for the scheduled subcarriers are not set to QCL-TypeD.

[0265] If a periodic or semi-persistent SRS resource set is configured, the associated NZP CSI-RS can be indicated through the associatedCSI-RS in the upper-level signaling SRS-ResourceSet. For non-codebook-based transmission, the UE does not expect the upper-level signaling spatialRelationInfo for the SRS resource and the associatedCSI-RS in the upper-level signaling SRS-ResourceSet to be configured together.

[0266] When multiple SRS resources are configured, the UE can determine the precoder and transmission rank to be applied to PUSCH transmission based on the SRI indicated by the base station. At this time, the SRI can be indicated through the SRS resource indicator field in the DCI or can be set through the srs-ResourceIndicator, which is a higher-level signaling. Similar to the codebook-based PUSCH transmission described above, when the UE receives an SRI through the DCI, the SRS resource indicated by the SRI refers to the SRS resource corresponding to the SRI among the SRS resources transmitted before the PDCCH containing the SRI. The UE can use one or more SRS resources for SRS transmission, and the maximum number of SRS resources that can be simultaneously transmitted in the same symbol within one SRS resource set and the maximum number of SRS resources are determined by the UE capability reported by the UE to the base station. At this time, the SRS resources that the UE simultaneously transmits occupy the same RB. The UE configures one SRS port for each SRS resource. Only one SRS resource set with the usage value set to 'nonCodebook' in the upper signaling SRS-ResourceSet can be set, and up to four SRS resources for non-codebook based PUSCH transmission can be set.

[0267] The base station transmits one NZP-CSI-RS associated with an SRS resource set to the terminal, and the terminal calculates a precoder to be used when transmitting one or more SRS resources within the SRS resource set based on the result measured upon reception of the NZP-CSI-RS. When the terminal transmits one or more SRS resources within the SRS resource set with usage set to 'nonCodebook' to the base station, the terminal applies the calculated precoder, and the base station selects one or more SRS resources from the received one or more SRS resources. At this time, in non-codebook based PUSCH transmission, the SRI represents an index that can express a combination of one or more SRS resources, and the SRI is included in the DCI. At this time, the number of SRS resources indicated by the SRI transmitted by the base station can be the number of transmission layers of the PUSCH, and the terminal transmits the PUSCH by applying the precoder applied to SRS resource transmission to each layer.

[0268] [PUSCH: Preparation time]

[0269] Next, the PUSCH preparation procedure time is described. When the base station schedules a UE to transmit a PUSCH using DCI format 0_0, 0_1, or 0_2, the UE may require a PUSCH preparation procedure time to transmit the PUSCH by applying the transmission method indicated through the DCI (transmission precoding method of SRS resources, number of transmission layers, spatial domain transmission filter). NR takes this into account and defines the PUSCH preparation procedure time. The PUSCH preparation procedure time of the UE can follow the following [Mathematical Formula 2].

[0270] [Equation 2]

[0271]

[0272] T as described in mathematical formula 2 proc,2 In , each variable can have the following meanings:

[0273] - N2: The number of symbols determined by the UE processing capability (UE processing capability) 1 or 2 and the numerology μ according to the UE capability. If UE processing capability 1 is reported according to the UE capability report, it has the value of [Table 22]. If UE processing capability 2 is reported and the availability of UE processing capability 2 is set through upper layer signaling, it can have the value of [Table 23].

[0274]

[0275]

[0276] - d 2,1 : The number of symbols set to 0 if all resource elements of the first OFDM symbol of PUSCH transmission are configured to consist of only DM-RS, and 1 otherwise.

[0277] - : 64

[0278] - μ: μ DL or μ UL Medium, T proc,2 This follows the larger value μ DL refers to the numerology of the downlink in which the PDCCH containing the DCI scheduling the PUSCH is transmitted, and μ UL It refers to the numerology of the uplink in which PUSCH is transmitted.

[0279] - T c : 1 / (Δf max *N f ), Δf max = 480*10 3 Hz, N f =has 4096.

[0280] - d 2,2 : If the DCI scheduling the PUSCH indicates BWP switching, it follows the BWP switching time, otherwise it has 0.

[0281] - d2: When the OFDM symbols of a PUCCH with a high priority index and a PUCCH with a low priority index overlap in time, the d2 value of the PUSCH with the high priority index is used. Otherwise, d2 is 0.

[0282] - T ext : If the terminal uses a shared spectrum channel access method, the terminal is T ext can be calculated and applied to the PUSCH preparation process time. Otherwise, T ext is assumed to be 0.

[0283] - T switch : T when the uplink switching interval is triggered switch is assumed to be the switching interval time. Otherwise, it is assumed to be 0.

[0284] When the base station and the terminal consider the time domain resource mapping information of the PUSCH scheduled through DCI and the influence of the timing advance between uplink and downlink, the base station and the terminal determine T from the last symbol of the PDCCH including the DCI that scheduled the PUSCH. proc,2 If the first symbol of the PUSCH begins before the first uplink symbol of the CP, the PUSCH preparation time is determined to be insufficient. Otherwise, the base station and the UE determine that the PUSCH preparation time is sufficient. The UE transmits the PUSCH only when the PUSCH preparation time is sufficient, and may ignore the DCI scheduling the PUSCH if the PUSCH preparation time is insufficient.

[0285] [CA / DC related]

[0286] FIG. 10 is a diagram illustrating a wireless protocol structure of a base station and a terminal in a single cell, carrier aggregation, or dual connectivity situation according to one embodiment of the present disclosure.

[0287] Referring to FIG. 10, the wireless protocol of the next-generation mobile communication system is composed of NR SDAP (Service Data Adaptation Protocol 1025, 1070), NR PDCP (Packet Data Convergence Protocol 1030, 1065), NR RLC (Radio Link Control 1035, 1060), and NR MAC (Medium Access Control 1040, 1055) in the terminal and NR base station, respectively.

[0288] The main functions of NR SDAP (1025, 1070) may include some of the following functions:

[0289] - Transfer of user plane data

[0290] - Mapping function between QoS flow and data bearer for both DL and UL

[0291] - Marking function of QoS flow ID for both uplink and downlink (marking QoS flow ID in both DL and UL packets)

[0292] - Ability to map reflective QoS flow to data bearer for uplink SDAP PDUs (reflective QoS flow to DRB mapping for the UL SDAP PDUs).

[0293] For the above SDAP layer device, the terminal can be configured by RRC message for each PDCP layer device, each bearer, or each logical channel, whether to use the header of the SDAP layer device or whether to use the function of the SDAP layer device, and when the SDAP header is configured, the terminal can instruct the NAS QoS reflection configuration 1-bit indicator (NAS reflective QoS) and the AS QoS reflection configuration 1-bit indicator (AS reflective QoS) of the SDAP header to update or reset the mapping information for the QoS flow and data bearer of the uplink and downlink. The SDAP header can include QoS flow ID information indicating QoS. The QoS information can be used as data processing priority, scheduling information, etc. to support smooth service.

[0294] The main functions of NR PDCP (1030, 1065) may include some of the following functions:

[0295] - Header compression and decompression (ROHC only)

[0296] - User data transfer function

[0297] - In-sequence delivery of upper layer PDUs

[0298] - Out-of-sequence delivery of upper layer PDUs

[0299] - PDCP PDU reordering for reception

[0300] - Duplicate detection of lower layer SDUs

[0301] - Retransmission function (Retransmission of PDCP SDUs)

[0302] - Encryption and decryption functions (Ciphering and deciphering)

[0303] - Timer-based SDU discard in uplink.

[0304] The reordering function of the NR PDCP device above refers to a function of reordering PDCP PDUs received from a lower layer in order based on the PDCP SN (sequence number), and may include a function of transmitting data to an upper layer in the reordered order. Alternatively, the reordering function of the NR PDCP device may include a function of transmitting data directly without considering the order, a function of recording lost PDCP PDUs by reordering the order, a function of reporting a status of lost PDCP PDUs to the transmitting side, and a function of requesting retransmission of lost PDCP PDUs.

[0305] The main functions of NR RLC (1035, 1060) may include some of the following functions:

[0306] - Data transfer function (Transfer of upper layer PDUs)

[0307] - In-sequence delivery of upper layer PDUs

[0308] - Out-of-sequence delivery of upper layer PDUs

[0309] - ARQ function (Error Correction through ARQ)

[0310] - Concatenation, segmentation and reassembly of RLC SDUs

[0311] - Re-segmentation of RLC data PDUs

[0312] - Reordering of RLC data PDUs

[0313] - Duplicate detection function

[0314] - Protocol error detection

[0315] - RLC SDU discard function

[0316] - RLC re-establishment function

[0317] In the above, the in-sequence delivery function of the NR RLC device refers to the function of sequentially delivering RLC SDUs received from a lower layer to an upper layer. The in-sequence delivery function of the NR RLC device may include a function of reassembling and delivering a single RLC SDU when it is received divided into multiple RLC SDUs, a function of rearranging received RLC PDUs based on the RLC SN (sequence number) or PDCP SN (sequence number), a function of recording lost RLC PDUs by rearranging the order, a function of reporting the status of lost RLC PDUs to the transmitting side, and a function of requesting retransmission of lost RLC PDUs. The in-sequence delivery function of an NR RLC device may include a function to sequentially deliver to the upper layer only the RLC SDUs up to the lost RLC SDU when there is a lost RLC SDU, or may include a function to sequentially deliver to the upper layer all RLC SDUs received before the timer starts if a predetermined timer has expired even if there is a lost RLC SDU. Alternatively, the in-sequence delivery function of an NR RLC device may include a function to sequentially deliver to the upper layer all RLC SDUs received up to the present if a predetermined timer has expired even if there is a lost RLC SDU.In addition, the RLC PDUs may be processed in the order in which they are received (in the order of arrival, regardless of the order of the sequence number) and delivered to the PDCP device out of order (out-of-sequence delivery). In the case of segments, the segments stored in the buffer or to be received later may be received, reconstructed into a complete RLC PDU, processed, and delivered to the PDCP device. The NR RLC layer may not include a concatenation function, and the function may be performed in the NR MAC layer or replaced with a multiplexing function of the NR MAC layer.

[0318] The out-of-sequence delivery function of the NR RLC device above refers to the function of directly delivering RLC SDUs received from a lower layer to an upper layer regardless of the order, and may include a function of reassembling and delivering RLC SDUs when an original RLC SDU is received divided into multiple RLC SDUs, and may include a function of storing the RLC SN or PDCP SN of received RLC PDUs and arranging the order to record lost RLC PDUs.

[0319] NR MAC (1040, 1055) can be connected to multiple NR RLC layer devices configured in one terminal, and the main functions of NR MAC can include some of the following functions.

[0320] - Mapping function (Mapping between logical channels and transport channels)

[0321] - Multiplexing / demultiplexing of MAC SDUs

[0322] - Scheduling information reporting function

[0323] - HARQ function (Error correction through HARQ)

[0324] - Priority handling between logical channels of one UE

[0325] - Priority handling between UEs by means of dynamic scheduling

[0326] - MBMS service identification function

[0327] - Transport format selection function

[0328] - Padding function

[0329] The NR PHY layer (1045, 1050) can perform operations of channel coding and modulating upper layer data, converting it into OFDM symbols and transmitting it through a wireless channel, or demodulating and channel decoding OFDM symbols received through a wireless channel and transmitting them to a higher layer.

[0330] The above wireless protocol structure can have various detailed structures depending on the carrier (or cell) operation method. For example, when a base station transmits data to a terminal based on a single carrier (or cell), the base station and the terminal use a protocol structure that has a single structure for each layer, such as 1000. On the other hand, when a base station transmits data to a terminal based on CA (carrier aggregation) that uses multiple carriers in a single TRP, the base station and the terminal use a protocol structure that has a single structure up to RLC, such as 1010, but multiplexes the PHY layer through the MAC layer. As another example, when a base station transmits data to a terminal based on DC (dual connectivity) that uses multiple carriers in multiple TRPs, the base station and the terminal use a protocol structure that has a single structure up to RLC, such as 1020, but multiplexes the PHY layer through the MAC layer.

[0331] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the attached drawings. The contents of the present disclosure can be applied to FDD and TDD systems. In the present disclosure below, upper signaling (or upper layer signaling) refers to a signal transmission method in which a base station transmits a signal to a terminal using a downlink data channel of a physical layer, or a terminal transmits a signal to a base station using an uplink data channel of a physical layer, and may also be referred to as RRC signaling, PDCP signaling, or MAC (medium access control) control element (MAC control element; MAC CE).

[0332] In the present disclosure, determining the priority between A and B may be referred to in various ways, such as selecting a higher priority according to a predetermined priority rule and performing an action corresponding to it, or omitting or dropping an action for a lower priority.

[0333] In the following disclosure, the above examples are described through a number of embodiments, but they are not independent, and one or more embodiments may be applied simultaneously or in combination.

[0334] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the attached drawings. Hereinafter, a base station is an entity that performs resource allocation of a terminal, and may be at least one of a gNode B, a gNB, an eNode B, a Node B, a BS (Base Station), a wireless access unit, a base station controller, or a node on a network. The terminal may include a UE (User Equipment), an MS (Mobile Station), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing a communication function. Although the embodiments of the present disclosure are described below using a 5G system as an example, the embodiments of the present disclosure may be applied to other communication systems having a similar technical background or channel type. For example, this may include LTE or LTE-A mobile communication and mobile communication technologies developed after 5G. Therefore, the embodiments of the present disclosure may be applied to other communication systems with some modifications without significantly departing from the scope of the present disclosure as determined by a person skilled in the art. The contents of the present disclosure can be applied to FDD and TDD systems.

[0335] Additionally, when describing the present disclosure, detailed descriptions of related functions or configurations will be omitted if they are deemed to unnecessarily obscure the gist of the present disclosure. Furthermore, the terms described below are defined based on the functions of the present disclosure and may vary depending on the intent or custom of the user or operator. Therefore, their definitions should be based on the contents of this specification.

[0336] In the following description of the present disclosure, upper layer signaling may be signaling corresponding to at least one or a combination of one or more of the following signaling.

[0337] - MIB (Master Information Block)

[0338] - SIB (System Information Block) or SIB

[0339] - RRC (Radio Resource Control)

[0340] - MAC (Medium Access Control) CE (Control Element)

[0341] In addition, L1 signaling may be signaling corresponding to at least one or a combination of one or more signaling methods using the physical layer channel or signaling below.

[0342] - PDCCH (Physical Downlink Control Channel)

[0343] - DCI (Downlink Control Information)

[0344] - UE-specific DCI

[0345] - Group common DCI

[0346] - Common DCI

[0347] - Scheduling DCI (e.g. DCI used for scheduling downlink or uplink data)

[0348] - Non-scheduled DCI (e.g. DCI not intended for scheduling downlink or uplink data)

[0349] - PUCCH (Physical Uplink Control Channel)

[0350] - UCI (Uplink Control Information)

[0351] In the present disclosure, determining the priority between A and B may be referred to in various ways, such as selecting a higher priority according to a predetermined priority rule and performing an action corresponding to it, or omitting or dropping an action for a lower priority.

[0352] In the following disclosure, the above examples are described through a number of embodiments, but they are not independent, and one or more embodiments may be applied simultaneously or in combination.

[0353] [Reference BWP Setting and Instruction Method]

[0354] According to the NR system, a terminal can receive a master information block (MIB) from a physical broadcast channel (PBCH) included in an SS / PBCH block. The terminal can obtain the location of a frequency domain of a CORESET in which a PDCCH is transmitted from the MIB. The terminal can determine the bandwidth of the CORESET (i.e., the frequency bandwidth from the lowest PRB on the frequency axis to the highest PRB on the frequency axis) as an initial downlink bandwidth part. The terminal can expect that the DCI format received from the CORESET will receive a PDSCH within the initial downlink bandwidth part. That is, when the terminal receives the DCI format and interprets the frequency domain allocation information of the PDSCH scheduled by the DCI format, the interpretation can be based on the initial downlink bandwidth part. Alternatively, the interpretation can be based on the number of RBs included in the initial downlink bandwidth part.

[0355] The MIB may include 4 bits indicating the frequency domain location of the CORESET. The interpretation of the 4 bits may vary depending on the subcarrier spacing of the SS / PBCH, the subcarrier spacing of the CORESET, and the minimum channel bandwidth. For example, [Table 24] is a table for interpreting the 4 bits when the subcarrier spacing of the SS / PBCH is 30 kHz, the subcarrier spacing of the CORESET is 30 kHz, and the minimum channel bandwidth is 5 MHz or 10 MHz. Here, the 4 bits may indicate one of the values ​​0, 1, ..., 15.

[0356]

[0357] Referring to [Table 24], the number of CORESETs indicated by the terminal in the MIB ( ) can be 24 or 48. This can be a bandwidth of 8.64 MHz to 17.28 MHz. Accordingly, the terminal can receive the PDCCH from the CORESET within the bandwidth of 8.64 MHz to 17.28 MHz. The PDCCH can include DCI for scheduling the PDSCH including system information.

[0358] FIG. 11 is a diagram illustrating an SS / PBCH block, a CORESET, and a PDSCH according to one embodiment of the present disclosure. Specifically, FIG. 11 illustrates an SS / PBCH block, a CORESET, and a PDSCH when 4 bits indicating the frequency domain location of the CORESET in the MIB indicate index 13.

[0359] Referring to FIG. 11, a terminal may receive an SS / PBCH block (1100). The SS / PBCH block may include a primary synchronization signal (PSS) and a secondary synchronization signal (SSS) for providing downlink synchronization and a cell index, and a physical channel, PBCH, for providing MIB, which is cell main information. The MIB may include information as shown in [Table 25]. Here, pdcch-ConfigSIB1 may include 4 bits indicating the location of the frequency domain of CORESET. More specifically, pdcch-COnfigSIB1 may include controlResourceSetZero, and the controlResourceSetZero may be 4 bits indicating one of the values ​​0, 1, ..., 15.

[0360]

[0361] The terminal can determine the frequency position or time position of the CORESET (1110) based on the MIB received from the base station. The CORESET can be called CORESET0 (i.e., the index of the CORESET is 0). The CORESET is 48 (Table 24) on the frequency axis. (1140)) RBs. The RBs may be consecutive RBs. The index of the starting RB of the CORESET may be determined based on the frequency position of the SS / PBCH block and Offset=12 of the MIB (Offset (1130) of Table 24). The number of OFDM symbols included in the time axis of the CORESET is 2 (Offset (1130) of Table 24). ) may be.

[0362] The terminal can receive a PDCCH that schedules a PDSCH including a system information block (SIB) from the CORESET. The PDCCH can include a DCI format that schedules the system information block. The DCI format can have a CRC scrambled with a specific RNTI. Here, the specific RNTI can be called SI-RNTI (System Information-RNTI), and the value of the SI-RNTI can be a value preset by the base station and the terminal. For example, the value of the SI-RNTI can be '000...0' with a length of 16 bits.

[0363] The DCI format for scheduling the system information block can be composed of the DCI fields in [Table 26]. Here, may be equal to the number of RBs included in the CORESET (1110). Additionally, the DCI format scheduling the system information block may have unused reserved bits (15 bits).

[0364]

[0365] Referring to [Table 26], the DCI format for scheduling a system information block may include a Frequency domain resource assignment (FDRA) field that indicates scheduling information on the frequency axis. The length of the FDRA field is the number of RBs included in the CORESET ( ) may vary. Here, the length of the FDRA field is It could be.

[0366] The FDRA field is a single RB unit, the index of the starting RB (RB start =0,1,..., ) and the number of consecutive RBs (L RBs =1,2,..., ) can be directed. More specifically, the index of the starting RB (RB start ) and the number of consecutive RBs (L RBs ) can be interpreted by joint coding as shown in [Table 27]. In [Table 27] It could be.

[0367] Through the FDRA field, the terminal indicates the index of the starting RB of the PDSCH containing the system information block (RB start ) and the number of consecutive RBs (L RBs ) can be obtained. Here, the index of the starting RB (RB start ) may be equal to the lowest RB on the frequency axis of the CORESET. Here, the CORESET may be the CORESET in which the PDCCH that scheduled the PDSCH is received, or the CORESET indicated in the MIB.

[0368] The terminal can be configured with a separate active downlink bandwidth part. In this case, the terminal can also set the index of the starting RB of the PDSCH including the system information block (RB start) may be equal to the lowest RB on the frequency axis of the CORESET. This may be applicable when the active downlink bandwidth includes the CORESET or the subcarrier spacing of the CORESET is equal to a portion of the active downlink bandwidth. If this condition is not satisfied, the terminal may set the index (RB) of the start RB of the PDSCH including the system information block. start ) may be equal to the lowest RB on the frequency axis in the active downlink bandwidth portion.

[0369]

[0370] According to the operation of the terminal described above, when the terminal is scheduled for a PDSCH including a system information block, the maximum number of RBs that the PDSCH can occupy is the number of RBs of the CORESET ( , which may be the same as . That is, the bandwidth occupied by the PDSCH including the system information block is 8.64 MHz ( ) to 17.28MHz ( ) may be limited. The above bandwidth may be referred to as the initial downlink bandwidth part (1150).

[0371] The initial downlink bandwidth portion may be smaller than the carrier bandwidth (1160) occupied by the downlink carrier or cell. For example, the initial downlink bandwidth portion may be 17.28 MHz (48 RBs, 30 kHz subcarrier spacing), but the carrier bandwidth may be 98.28 MHz (273 RBs, 30 kHz subcarrier spacing). Therefore, the bandwidth over which the PDSCH, including the system information block, is scheduled may be significantly smaller than the carrier bandwidth.

[0372] The PDSCH, including the system information block, uses a sufficiently low code rate to ensure sufficient coverage. Therefore, high coverage can be secured by increasing the number of resources transmitting the PDSCH. Here, the number of resources can be proportional to the number of RBs or OFDM symbols scheduled for the PDSCH. Since the UE must transmit the PDSCH within a single slot, it can be scheduled for up to 14 OFDM symbols. However, the UE can only be scheduled for up to 48 RBs, which is significantly less than the carrier bandwidth. Therefore, the UE's PDSCH coverage may be insufficient.

[0373] To reduce base station power consumption, it is desirable for the base station to transmit for as short a time as possible. Therefore, the base station can reduce the number of OFDM symbols containing the PDSCH to transmit the PDSCH containing the system information block for as short a time as possible. In this case, the resource shortage can be resolved by increasing the number of RBs in the frequency domain. However, since the base station uses significantly fewer RBs for PDSCH transmission containing the system information block than the number of RBs contained in the carrier used for downlink transmission, the base station may not be able to reduce power consumption.

[0374] A method for solving the above problem is disclosed.

[0375] FIG. 12 is a diagram illustrating a situation in which an initial downlink bandwidth portion is set to be larger than the bandwidth of CORESET according to one embodiment of the present disclosure.

[0376] When the terminal receives a PDSCH (1220) including system information from the base station, the terminal can set / instruct or determine a new initial downlink bandwidth portion (1250 in FIG. 12) instead of the initial downlink bandwidth portion corresponding to the bandwidth of the existing CORESET (e.g., 1150 in FIG. 11).

[0377] Here, the new initial downlink bandwidth portion (1250) may include a CORESET (1210). Here, the new initial downlink bandwidth portion (1250) may include an SS / PBCH block (1200). Here, the new initial downlink bandwidth portion (1250) may include both a CORESET (1210) and an SS / PBCH block (1200).

[0378] Hereinafter, a method for determining a new initial downlink bandwidth portion is described in this disclosure. For convenience, the new initial downlink bandwidth portion may be referred to as a reference bandwidth portion in the following description. That is, the reference bandwidth portion described below may represent a bandwidth for receiving a PDSCH containing system information.

[0379] <First embodiment. Reference bandwidth part indication in MIB or auxiliary MIB>

[0380] In one embodiment of the present disclosure, a terminal may be instructed on a reference bandwidth portion through a MIB or auxiliary MIB. Referring to Table 25, some bits within the MIB may be used as indicators indicating the reference bandwidth portion, or a field defined in the MIB may be used as an indicator indicating the reference bandwidth portion.

[0381] Here, the auxiliary MIB contains system information, and the auxiliary MIB can be described as SIB0 (System information block 0) or auxiliary PBCH (Physical Broadcast Channel).

[0382] An indicator (e.g., spare bit (1 bit)) in the MIB can indicate a reference bandwidth portion. For example, if the indicator (e.g., spare bit (1 bit)) is the first value, the reference bandwidth portion can be identical to the RBs included in the CORESET. That is, the frequency allocation of the CORESET can be determined through 4 bits in the MIB, and the RBs included in the CORESET can be included in the reference bandwidth portion. If the indicator (e.g., spare bit (1 bit)) is the second value, a new bandwidth can be indicated as the reference bandwidth portion. The new bandwidth can be a bandwidth determined based on at least one of the CORESET or SS / PBCH blocks. A method for determining the new bandwidth will be described later.

[0383] The MIB can indicate the presence of an auxiliary MIB. That is, the terminal can obtain the presence of an auxiliary MIB from the MIB (e.g., Cell ID, etc.). This can be indicated through an indicator (e.g., a spare bit (1 bit)) in the MIB. For example, if the indicator (e.g., a spare bit (1 bit)) is a first value, it can indicate that the base station does not transmit the auxiliary MIB, and if the indicator (e.g., a spare bit (1 bit)) is a second value, it can indicate that the base station transmits the auxiliary MIB.

[0384] The auxiliary MIB may contain additional cell information and may be received in adjacent RBs of the SS / PBCH block or in adjacent OFDM symbols of the SS / PBCH block or in time-frequency resources determined according to the index of the SS / PBCH block.

[0385] For example, the auxiliary MIB can be arranged in a frequency division multiplexed manner with the SS / PBCH block. If the SS / PBCH block occupies 20 RBs and 4 OFDM symbols, X RBs adjacent to the 20 RBs (X RBs in the lower frequency of the SS / PBCH block to X RBs in the upper frequency of the SS / PBCH block) can be used for auxiliary MIB transmission. Here, the auxiliary MIMO can be transmitted in 4 OFDM symbols, or the auxiliary MIB can be transmitted in some of the 4 OFDM symbols. Here, X can be 4 or 8.

[0386] For example, the auxiliary MIB can be arranged in a time-division multiplexed manner with the SS / PBCH block. If the SS / PBCH block occupies 20 RBs and 4 OFDM symbols, then X OFDM symbols after the 4 OFDM symbols can be used for auxiliary MIB transmission. Here, X OFDM symbols can occupy 20 RBs. Here, X can be 1 or 2.

[0387] The auxiliary MIB can be received from the CORESET. Here, the CORESET can be the CORESET indicated in the MIB. The terminal can receive a PDCCH whose CRC is scrambled with a specific RNTI from the CORESET. The PDCCH can be a DCI format including the MIB. Here, the specific RNTI can be a MIB-RNTI (MasterSystemInformation-RNTI), and the MIB-RNTI can be a different value from the SI-RNTI. The terminal can assume that the length of the DCI format whose CRC is scrambled with the MIB-RNTI is the same as the DCI format whose CRC is scrambled with the SI-RNTI. That is, if the length of the DCI format whose CRC is scrambled with the MIB-RNTI is shorter than the DCI format whose CRC is scrambled with the SI-RNTI, zero (or '0') can be padded so that it is the same as the DCI format whose CRC is scrambled with the SI-RNTI.

[0388] The terminal can blind-decode the DCI format whose CRC is scrambled with MIB-RNTI in the search space where the DCI format whose CRC is scrambled with SI-RNTI is blind-decoded. For example, if the search space of the DCI format whose CRC is scrambled with SI-RNTI includes four PDCCH candidates with aggregation level 4, two PDCCH candidates with aggregation level 8, and one PDCCH candidate with aggregation level 1, the DCI format whose CRC is scrambled with MIB-RNTI must be blind-decoded in the search space (including the PDCCH candidates).

[0389] The auxiliary MIB can be received from the CORESET. Here, the CORESET can be the CORESET indicated in the MIB. The terminal can receive a DCI format in which the CRC is scrambled with the SI-RNTI. The DCI format can include an indicator indicating whether the DCI format is a DCI format for scheduling a system information block or a DCI format including an auxiliary MIB. The indicator can be 1 bit, and if the 1 bit is a first value ('0'), it is a DCI format for scheduling a system information block, and if the 1 bit is a second value ('1'), it can be a DCI format including an auxiliary MIB. This is shown in Table 28.

[0390] If the DCI format includes an auxiliary MIB, the DCI format may not schedule a PDSCH.

[0391] The auxiliary MIB may include indicators indicating the reference bandwidth portion described above. Additionally, the auxiliary MIB may include various system information. For example, the auxiliary MIB may indicate the type of terminal that can connect to the cell. The terminal type may be categorized by the bandwidth supported by the terminal, the number of MIMO layers, the duplex mode, the peak data rate, etc.

[0392] For example, whether a terminal supporting a low bandwidth can access a cell can be indicated in the auxiliary MIB. A terminal supporting a low bandwidth can obtain access status from the auxiliary MIB. If access is not possible, the terminal supporting a low bandwidth may not access the cell. If access is possible, the terminal supporting a low bandwidth may access the cell.

[0393] For example, whether a terminal supporting full-duplex communication (or subband full-duplex) can access a cell can be indicated in the auxiliary MIB. A terminal supporting full-duplex communication (or subband full-duplex) can obtain access status from the auxiliary MIB. If access is not possible, a terminal supporting full-duplex communication (or subband full-duplex) may not access the cell. If access is possible, a terminal supporting full-duplex communication (or subband full-duplex) can access the cell.

[0394] The auxiliary MIB may include indicators indicating the reference bandwidth portion described above. Additionally, the auxiliary MIB may include various system information. For example, the auxiliary MIB may include a support list for the cell. The support list for the cell may be divided into the bandwidth of the downlink channel / signal, the number of MIMO layers, the duplex mode, the peak data rate, and so on.

[0395] For example, the bandwidth of the PDSCH transmitting system information may be indicated in the auxiliary MIB. Terminals supporting a bandwidth lower than the PDSCH bandwidth may not be able to receive the PDSCH in the cell. Accordingly, terminals supporting a bandwidth lower than the PDSCH bandwidth may not access the cell.

[0396] For example, the cell's duplex mode may be indicated in the auxiliary MIB. Terminals that do not support the duplex mode may not access the cell. Terminals that support the duplex mode may access the cell. The cell's duplex mode may be at least one of half-duplex mode and full-duplex mode.

[0397]

[0398] The auxiliary MIB can be scheduled based on the PDCCH received from the CORESET. Here, the CORESET can be the CORESET indicated in the MIB. The terminal can receive the PDCCH with the CRC scrambled with a specific RNTI from the CORESET. The PDCCH can be a DCI format for scheduling the MIB. Here, the specific RNTI can be the MIB-RNTI (MasterSystemInformation-RNTI), and the MIB-RNTI can be a different value from the SI-RNTI. The terminal can assume that the length of the DCI format with the CRC scrambled with the MIB-RNTI is the same as the DCI format with the CRC scrambled with the SI-RNTI. That is, if the length of the DCI format whose CRC is scrambled with MIB-RNTI is shorter than the DCI format whose CRC is scrambled with SI-RNTI, zero (or '0') may be padded to make it the same as the DCI format whose CRC is scrambled with SI-RNTI.

[0399] The terminal can blind-decode the DCI format whose CRC is scrambled with MIB-RNTI in the search space where the DCI format whose CRC is scrambled with SI-RNTI is blind-decoded. For example, if the search space of the DCI format whose CRC is scrambled with SI-RNTI includes four PDCCH candidates with aggregation level 4, two PDCCH candidates with aggregation level 8, and one PDCCH candidate with aggregation level 1, the DCI format whose CRC is scrambled with MIB-RNTI must be blind-decoded in the search space (including the PDCCH candidates).

[0400] The auxiliary MIB can be received from the CORESET. Here, the CORESET can be the CORESET indicated in the MIB. The terminal can receive a DCI format in which the CRC is scrambled with the SI-RNTI. The DCI format can include an indicator indicating whether the DCI format is a DCI format for scheduling a system information block or a DCI format for scheduling an auxiliary MIB. The indicator can be 1 bit, and if 1 bit is a first value ('0'), it is a DCI format for scheduling a system information block, and if 1 bit is a second value ('1'), it can be a DCI format including an auxiliary MIB. Alternatively, the indicator may be 2 bits, and if the 2 bits are a first value ('00'), it is a DCI format for scheduling system information block 1 (SIB1), if the 2 bits are a second value ('01'), it is a DCI format for scheduling system information blocks other than SIB1, and if the 2 bits are a third value ('10'), it is a DCI format for scheduling auxiliary MIB.

[0401] If the terminal is instructed that the auxiliary MIB is not being transmitted, the reference bandwidth can be assumed to be the same as the RBs included in the CORESET. If the terminal is instructed that the auxiliary MIB is being transmitted, the reference bandwidth can be instructed to be transmitted in the auxiliary MIB.

[0402] The terminal can be instructed to refer to the bandwidth portion through the MIB or auxiliary MIB, and at this time, the number of RBs included in the reference bandwidth portion It can be said that. The terminal can monitor the DCI format (DCI format with CRC scrambled with SI-RNTI) that schedules the PDSCH including system information in the CORESET indicated in the MIB. Here, the length of the FDRA field included in the DCI format is It could be.

[0403] For reference, a terminal can receive multiple SS / PBCH blocks. In this case, each of the multiple SS / PBCH blocks can include a MIB or auxiliary MIB. In this case, the MIBs or auxiliary MIBs corresponding to different SS / PBCH blocks can indicate the same reference bandwidth portion. In other words, regardless of which SS / PBCH block the terminal receives, the reference bandwidth portion can be determined identically.

[0404] <Example 2. Reference bandwidth part indication in DCI format>

[0405] In one embodiment of the present disclosure, a terminal may be instructed on a reference bandwidth portion in a DCI format that schedules system information. In one example, referring to [Table 26], the terminal may be instructed on some bits of the Reserved bits or some bits of the FDRA field.

[0406] Method 1. Using an indicator in the DCI field (using some bits from the reserved bits)

[0407] The terminal can be instructed about the reference bandwidth size using an indicator (N bits among the reserved bits) included in the DCI field. More specifically, a DCI format in which a CRC is scrambled with SI-RNTI can be received, and the DCI format can include an indicator of N bits indicating a reference bandwidth portion. The indicator of N bits can indicate an index of the reference bandwidth portion, and the index can have a corresponding reference bandwidth portion.

[0408] When a terminal is instructed to receive a portion of a reference bandwidth from a DCI format, the terminal can receive the FDRA field in at least one of the following FDRA field design methods.

[0409] FDRA field design method 1: Determine and interpret the FDRA field length based on the bandwidth of CORESET (RB start , L RBs ) obtained. Based on the indicated reference bandwidth size (RB start , L RBs ) can be scaled.

[0410] - Length of FDRA field: And,

[0411] - In [Table 27] Interpreted as RB start , L RBs decision

[0412] - Index of the starting RB of PDSCH (RB') start ) is RB' start =S*RB start , and the number of consecutive RBs (L') RBs ) is L' RBs =S*L RBs , where S is a natural number, and S is the number of RBs included in the reference bandwidth portion ( ) and the number of RBs included in CORESET ( ) is a value determined based on the ratio. For example, the S value is Or a value determined by at least one of rounding down, up, or down.

[0413] - RB' start =0 RB is equal to the lowest RB on the frequency axis of the indicated reference bandwidth portion.

[0414] FDRA Field Design Method 2: Determining FDRA field length based on the largest designable reference bandwidth. Interpretation can be based on the designation reference bandwidth.

[0415] - Length of FDRA field: And, Here The number of RBs included in the reference bandwidth portion whose index is i among the reference bandwidth portions that can be indicated in the DCI format.

[0416] - If the index of the indicated reference bandwidth part is i, among the FDRA fields Only the Least Significant Bits (LSBs) are used to interpret the FDRA field.

[0417] - In [Table 27] Interpreted as RB start , L RBs decision.

[0418] - Index of the starting RB of PDSCH (RB') start ) is RB' start =RB start , and the number of consecutive RBs (L') RBs ) is L' RBs =L RBs Decided on.

[0419] - RB' start =0 RB is equal to the lowest RB on the frequency axis of the indicated reference bandwidth portion.

[0420] FDRA Field Design Method 3: Determining and interpreting field lengths based on the largest designable reference bandwidth. It is possible to expect scheduling to occur only within the designated reference bandwidth, or to assume that only RBs within the designated reference bandwidth are included.

[0421] - Length of FDRA field: And, Here The number of RBs included in the reference bandwidth portion whose index is i among the reference bandwidth portions that can be indicated in the DCI format.

[0422] - All bits in the FDRA field are used to interpret the FDRA field.

[0423] - In [Table 27] Interpreted as RB start , L RBs decision

[0424] - Index of the starting RB of PDSCH (RB') start ) is RB' start =RB start , and the number of consecutive RBs (L') RBs ) is L' RBs =L RBs Decided on.

[0425] - RB' start =0 RB is equal to the lowest RB on the frequency axis of the indicated reference bandwidth portion. L RBs > In this case, L RBs= can be decided by

[0426] Method 2. Instruction using some bits of the FDRA field

[0427] The terminal can be instructed on the reference bandwidth size using N bits among the bits of the FDRA field. Here, N bits is the MSB of the FDRA field, and the remaining bits of the FDRA field can be used to indicate the frequency domain allocation information of the PDSCH.

[0428] More specifically, a DCI format in which a CRC is scrambled with SI-RNTI can be received, and the MSB N bits of the FDRA field of the DCI format can indicate a reference bandwidth portion. The N bits can indicate an index of the reference bandwidth portion, and the index can have a corresponding reference bandwidth portion.

[0429] When a terminal is instructed to receive a portion of a reference bandwidth from a DCI format, the terminal may receive the FDRA field using one of the following FDRA field design methods.

[0430] - Length of FDRA field: And,

[0431] - Based on the remaining bits excluding the MSB N bits of the above FDRA field, in [Table 27] Interpreted as RB start , L RBs decision

[0432] - Index of the starting RB of PDSCH (RB') start ) is RB' start =S*RB start , and the number of consecutive RBs (L') RBs ) is L' RBs =S*L RBs Determined by. Here, the S value is a natural number, and S is a value determined by the MSB N bits of the FDRA field. For example, if N = 1, if the MSB 1 bit is '0', it can be the first S value (S=1), and if it is '1', it can be the second S value (S=2). Here, the S value corresponding to the N value can be a value set based on the MIB or auxiliary MIB, or a value defined in the standard.

[0433] - RB' start =0 RB is equal to the lowest RB on the frequency axis of the indicated reference bandwidth portion.

[0434] Although the above-described method utilizes some bits of the FDRA field of the DCI format, all or some bits of other fields may be utilized. For example, some bits of the MCS (Modulation and coding scheme) field, some bits of the RV (Redundancy) field, some bits of the HPN (HARQ process number) field, or some bits of the DAI (downlink assignment index) field may be utilized.

[0435] <Example 3. Reference Bandwidth Partial Candidate>

[0436] Based on the first and second embodiments, the terminal can acquire N bits and be indicated with a reference bandwidth portion by the N bits. In the following disclosure, the N bits may be referred to as a reference bandwidth portion indicator. In one embodiment of the present disclosure, candidates for the reference bandwidth portion that may be indicated by the N bits may include the following. The N bits may indicate an index of one of the candidates for the reference bandwidth portion below.

[0437] As a first candidate, a candidate for the reference bandwidth portion can be determined based on the frequency information of the CORESET. Here, the CORESET may be a CORESET indicated in the MIB. More specifically, the terminal can determine a candidate for the reference bandwidth portion based on the starting RB of the COSESET and the number of RBs included in the CORESET.

[0438] For example, a candidate for the reference bandwidth part may have the same starting RB as the CORESET. That is, the lowest RB in the frequency axis of the candidate for the reference bandwidth part may be the same as the lowest RB in the frequency axis of the CORESET. And, the number of RBs included in the candidate for the reference bandwidth part may be an integer multiple of the number of RBs included in the CORESET. For example, the number of RBs included in the candidate for the reference bandwidth part may be K times the number of RBs included in the CORESET (K* ) can be. Therefore, the candidates for the reference bandwidth part are K* in ascending order of the frequency axis from the start RB of CORESET. It can be composed of RBs.

[0439] For example, a candidate for the reference bandwidth part may have the same last RB as the CORESET. That is, the highest RB in the frequency axis of the candidate for the reference bandwidth part may be the same as the highest RB in the frequency axis of the CORESET. And, the number of RBs included in the candidate for the reference bandwidth part may be an integer multiple of the number of RBs included in the CORESET. For example, the number of RBs included in the candidate for the reference bandwidth part may be K times the number of RBs included in the CORESET (K* ) can be. The candidates for the reference bandwidth part are K* in descending order of the frequency axis from the last RB of CORESET. It can be composed of RBs.

[0440] For example, the center frequency of the candidate of the reference bandwidth part and the CORESET can be aligned. For this purpose, the starting RB of the reference bandwidth part can be offset by X RB from the starting RB of the CORESET. More specifically, the number of RBs included in the candidate of the reference bandwidth part is K times the number of RBs included in the CORESET (K* ), the offset is (K-1)* / 2 can be. That is, the index of the starting RB of CORESET If so, the index of the starting RB of the candidate in the reference bandwidth part is It could be.

[0441] FIG. 13a is a diagram illustrating candidates for a portion of a reference bandwidth determined according to frequency information of CORESET according to one embodiment of the present disclosure.

[0442] Referring to Fig. 13a, K may be 2. CORESET is It can contain RBs of . Since K=2, the reference bandwidth part is It can contain RBs of dogs.

[0443] FIG. 13b is a diagram illustrating candidates for a portion of a reference bandwidth determined according to frequency information of CORESET according to one embodiment of the present disclosure.

[0444] Referring to Fig. 13b, K may be 2. CORESET is It can contain RBs. Since K=3, the reference bandwidth part is 3 It may include RBs. In FIGS. 13a and 13b, the position of the start RB of the reference bandwidth portion may be the same as the position of the start RB of CORESET (13a-01, 13b-01), the position of the last RB of the reference bandwidth portion may be the same as the position of the last RB of COREST (13a-02, 13b-02), or the positions of the center frequencies of the reference bandwidth portion and COREST may be the same (13a-03, 13b-03).

[0445] As a second candidate, a candidate for the reference bandwidth portion may be determined based on frequency information of the SS / PBCH, according to one embodiment of the present disclosure. More specifically, the terminal may determine a candidate for the reference bandwidth portion based on the starting RB of the SS / PBCH to the number of RBs included in the SS / PBCH.

[0446] For example, a candidate for the reference bandwidth part may have the same starting RB as the SS / PBCH. That is, the lowest RB in the frequency axis of the candidate for the reference bandwidth part may be the same as the lowest RB in the frequency axis of the SS / PBCH. And, the number of RBs included in the candidate for the reference bandwidth part may be an integer multiple of the number of RBs included in the SS / PBCH. For example, the number of RBs included in the candidate for the reference bandwidth part may be K times the number of RBs included in the SS / PBCH (K* ) can be. Therefore, the candidates for the reference bandwidth portion are K* in ascending order of the frequency axis from the start RB of SS / PBCH. It can be composed of RBs.

[0447] For example, a candidate for the reference bandwidth part may have the same last RB as the SS / PBCH. That is, the highest RB in the frequency axis of the candidate for the reference bandwidth part may be the same as the highest RB in the frequency axis of the SS / PBCH. And, the number of RBs included in the candidate for the reference bandwidth part may be an integer multiple of the number of RBs included in the SS / PBCH. For example, the number of RBs included in the candidate for the reference bandwidth part may be K times the number of RBs included in the SS / PBCH (K* ) can be. The candidates for the reference bandwidth part are K* in descending order of frequency axis from the last RB of SS / PBCH. It can be composed of RBs.

[0448] For example, the candidate of the reference bandwidth part and the center frequency of SS / PBCH can be aligned. For this purpose, the starting RB of the reference bandwidth part can be offset by X RB from the starting RB of SS / PBCH. More specifically, the number of RBs included in the candidate of the reference bandwidth part is K times the number of RBs included in SS / PBCH (K* ), the offset is (K-1)* / 2 can be. That is, the index of the starting RB of SS / PBCH If so, the index of the starting RB of the candidate in the reference bandwidth part is It could be.

[0449] As a third candidate, the candidate for the reference bandwidth portion can be determined based on the frequency information of the CORESET and the frequency information of the SS / PBCH. Here, the CORESET may be a CORESET indicated in the MIB. More specifically, the terminal can determine the candidate for the reference bandwidth portion based on the number of RBs included in the starting RB of the CORESET or the CORESET and the number of RBs included in the starting RB of the SS / PBCH or the SS / PBCH.

[0450] For example, the candidates for the reference bandwidth portion may be configured based on the lowest to highest RBs on the frequency axis among SS / PBCH and CORESET. That is, the reference bandwidth portion may include all RBs included in SS / PBCH, all RBs included in CORESET, and all RBs between the above RBs. In the following description, the above RBs may be referred to as SS / PBCH-CORESET.

[0451] The reference bandwidth part and SS / PBCH-CORESET can have the same starting RB. That is, the lowest RB in the frequency axis of the reference bandwidth part candidate can be the same as the lowest RB in the frequency axis of the SS / PBCH-CORESET. And, the number of RBs included in the candidate of the reference bandwidth part can be an integer multiple of the number of RBs included in the SS / PBCH-CORESET. For example, the number of RBs included in the candidate of the reference bandwidth part is K times the number of RBs included in the SS / PBCH-CORESET (K* ) can be. Therefore, the candidates for the reference bandwidth part are K* in ascending order of the frequency axis from the start RB of SS / PBCH-CORESET. It can be composed of RBs.

[0452] For example, a candidate for the reference bandwidth part may have the same last RB as the SS / PBCH-CORESET. That is, the highest RB in the frequency axis of the candidate for the reference bandwidth part may be the same as the highest RB in the frequency axis of the SS / PBCH-CORESET. And, according to one embodiment of the present disclosure, the number of R included in the candidate for the reference bandwidth part may be an integer multiple of the number of RBs included in the SS / PBCH-CORESET. For example, according to one embodiment of the present disclosure, the number of B included in the candidate for the reference bandwidth part may be K times the number of RBs included in the SS / PBCH-CORESET (K* ) can be. The candidates for the reference bandwidth part are K* in descending order of frequency axis from the last RB of SS / PBCH-CORESET. It can be composed of RBs.

[0453] For example, the center frequency of the candidate of the reference bandwidth part and the SS / PBCH-CORESET can be aligned. For this purpose, the starting RB of the reference bandwidth part can be offset by X RB from the starting RB of the SS / PBCH-CORESET. More specifically, the number of RBs included in the candidate of the reference bandwidth part is K times the number of RBs included in the SS / PBCH-CORESET (K* ), the offset is (K-1)* / 2 can be. That is, the index of the starting RB of SS / PBCH-CORESET If so, the index of the starting RB of the candidate in the reference bandwidth part is It could be.

[0454] As an example, [Table 29] is a table showing candidates for the reference bandwidth portion.

[0455]

[0456] According to the example described above, the reference bandwidth part indicator, N bits, indicates the index of the start RB of the reference subband and the number of RBs included in the reference subband. As another example, among the N bits, the first bit, N1 bits, may indicate the index of the start RB of the reference subband, and the second bit, N2 bits, may include the number of RBs included in the reference subband. Here, N1 + N2 may be N. This is shown in [Table 30] and [Table 31]. Here, N1 bits are 2 bits and may indicate one index among 0, 1, 2, and 3 of [Table 30], and N2 bits are 1 bit and may indicate one index among 0 and 1 of [Table 31].

[0457] In one example, the first bit (the index of the starting RB of the reference subband) or the second bit (the number of RBs included in the reference subband) may be omitted. In this case, a default value corresponding to the first bit or the second bit may be used.

[0458] In one example, the first bits and the second bits may be obtained from different physical channels. For example, the second bits may be obtained from the MIB or auxiliary MIB, and the first bits may be obtained from a DCI format in which the CRC is scrambled with the SI-RNTI.

[0459]

[0460]

[0461] FIG. 14 is a diagram in which a reference subband is determined according to frequency information of SS / PBCH and CORESET according to one embodiment of the present disclosure.

[0462] Referring to Fig. 14, the terminal can receive SS / PBCH (1400). The MIB included in the SS / PBCH can indicate frequency information of CORESET (1410). Here, the starting RB of CORESET is indicated by the RB unit Offset (1430) from SS / PBCH, and the number of RBs included in CORESET ( 1440) may be indicated. The terminal may determine the bandwidth of the SS / PBCH-CORESET, including the last RBs of the CORESET from the start RB of the SS / PBCH, as the reference subband portion (initial DL BWP, 1450 of FIG. 14). Accordingly, the PDSCH including the system information scheduled in the CORESET may be located within the reference subband portion (initial DL BWP, 1450 of FIG. 14).

[0463] <Example 4. Method for Determining Reference Subband Portions of Wideband and Narrowband Terminals>

[0464] According to the first and second embodiments of the present disclosure, a terminal may be instructed to a reference subband portion different from the initial downlink bandwidth portion determined by CORESET. Based on the instructed reference subband portion, the terminal may interpret the FDRA field to schedule a PDSCH including system information.

[0465] According to the third embodiment, the number of RBs included in the reference subband portion may be greater than the number of RBs included in the CORESET. Therefore, a UE capable of receiving a PDSCH including system information in the reference subband portion must be able to receive at least the reference subband portion. Such a UE will be referred to as a wideband UE. However, other UEs can only receive the RBs included in the CORESET. Furthermore, the number of RBs included in the reference subband portion may be the number of RBs that the UE cannot receive. Such a UE will be referred to as a narrowband UE.

[0466] According to the present disclosure, wideband and narrowband terminals must be scheduled with PDSCHs containing system information via CORESET. Wideband terminals can receive PDSCHs scheduled based on a reference subband portion. However, narrowband terminals cannot receive PDSCHs scheduled based on a reference subband portion.

[0467] For example, a narrowband terminal may receive a PDCCH for narrowband terminals in the CORESET. The PDCCH for the narrowband terminal may include a DCI format for scheduling a PDSCH within RBs included in the CORESET. A wideband terminal may receive a PDCCH for wideband terminals in the CORESET. The PDCCH for the wideband terminal may include a DCI format for scheduling a PDSCH within RBs included in the reference subband portion.

[0468] The DCI format for narrowband terminals may have the CRC scrambled with the first RNTI. The DCI format for wideband terminals may have the CRC scrambled with the second RNTI. Here, the first RNTI and the second RNTI may be different. Here, the first RNTI may be the SI-RNTI, and the second RNTI may be an RNTI different from the SI-RNTI.

[0469] FIG. 15 is a diagram illustrating a PDSCH for a narrowband terminal and a PDSCH for a wideband terminal according to an embodiment of the present disclosure. Specifically, FIG. 15 illustrates a PDSCH (1520) for a narrowband terminal and a PDSCH (1521) for a wideband terminal according to an embodiment of the present disclosure.

[0470] A narrowband terminal can receive a PDCCH for narrowband terminals from CORESET (1510). The PDCCH can schedule a PDSCH (1520) within a first initial DL BWP (1550). Here, the first initial DL BWP can be the same as the bandwidth of the CORESET. A wideband terminal can receive a PDCCH for wideband terminals from CORESET (1510). The PDCCH can schedule a PDSCH (1521) within a second initial DL BWP (1551). Here, the second initial DL BWP can be the same as the reference bandwidth portion.

[0471] <Example 5. Frequency Repetition for Wideband and Narrowband Terminals>

[0472] In one embodiment of the present disclosure, a wideband terminal and a narrowband terminal can receive a PDSCH including system information through PDSCH repetition along the frequency axis. Here, the frequency bandwidth of at least one PDSCH repetition may be less than or equal to the frequency bandwidth supported by the narrowband terminal.

[0473] FIG. 16 is a diagram illustrating frequency axis PDSCH repetition according to one embodiment of the present disclosure.

[0474] Referring to FIG. 16, the PDSCH (1620) transmitting system information may be repeated along the frequency axis, and each repetition (1621, 1622, 1623, 1624) may include the same system information. In addition, the number of RBs included in each repetition may be the same. That is, if the first repetition (1621) includes X RBs, other repetitions (1622, 1623, 1624) may also include X RBs. The first repetition (1621) may be the lowest repetition in the frequency axis.

[0475] The terminal can schedule a PDSCH that repeatedly transmits system information along the frequency axis from the PDCCH received from CORESET (1610). More specifically, the terminal can schedule the first repetition (1621) from the received PDCCH and be instructed on the number of repetitions.

[0476] If the terminal is a narrowband terminal, the terminal may receive one of the repetitions (1621, 1622, 1623, 1624), wherein one repetition may be less than or equal to the bandwidth of the narrowband terminal.

[0477] The terminal can be configured to determine whether or not to repeat the frequency-axis PDSCH and the number of repetitions through the MIB or auxiliary MIB. For example, a spare bit (1 bit) in the MIB can indicate whether or not to repeat the PDSCH. If the spare bit (1 bit) is the first value ('0'), the PDSCH may not be transmitted repeatedly along the frequency axis. If the spare bit (1 bit) is the second value ('1'), the PDSCH may be transmitted repeatedly along the frequency axis. In this case, the terminal can obtain the number of repetitions using at least one of the following methods.

[0478] In the first method, the frequency-axis PDSCH repetition count can be assumed to be a fixed value. That is, the frequency-axis PDSCH repetition count can always be assumed to be a fixed value, such as 2.

[0479] In a second method, the number of frequency-axis PDSCH repetitions can be determined based on PDSCH scheduling information and a reference bandwidth portion. For example, the RBs on which the PDSCH is scheduled can be determined from the PDSCH scheduling information. The RBs can be considered as RBs included in the first repetition, which is the lowest repetition in the frequency axis. The terminal can determine a repetition other than the first repetition. The second repetition can be located at a higher adjacent frequency than the first repetition and have the same number of RBs as the first repetition. If the second repetition is included in the reference bandwidth portion, the terminal can receive the second repetition. Similarly, the terminal can determine whether the third repetition, the fourth repetition, etc. are included in the reference bandwidth portion. If the third repetition is included but the fourth repetition is not included, the terminal can receive up to the third repetition.

[0480] As a third method, the number of PDSCH repetitions can be indicated through the MIB or auxiliary MIB. Here, the method for indicating the number of PDSCH repetitions in the MIB or auxiliary MIB can be the same as the method for indicating the reference subband portion described above.

[0481] If the terminal is a broadband terminal, the terminal can receive one or more of the repetitions (1621, 1622, 1623, 1624). Therefore, if the terminal is a broadband terminal, it can have higher coverage by receiving multiple repetitions.

[0482] FIG. 17 is a diagram illustrating frequency axis PDSCH repetition according to one embodiment of the present disclosure.

[0483] Referring to FIG. 17, the starting RB of the CORESET (1710) is indicated by an RB-unit offset (1730) from the SS / PBCH (1700), and the PDSCH (1720) transmitting system information may be transmitted in two repetitions along the frequency axis. The two repetitions (1721, 1722) may include the same system information. The first repetition (1721) may be composed of RBs scheduled within the first initial DL BWP (bandwidth of the CORESET) among the scheduled PDSCHs, and the second repetition (1722) may be composed of RBs scheduled only within the second initial DL BWP (indicated reference bandwidth portion) among the scheduled PDSCHs.

[0484] The terminal can schedule a PDSCH that repeatedly transmits system information along the frequency axis from the PDCCH received from CORESET (1710). The terminal can determine the RBs included in the first repetition and the RBs included in the second repetition among the RBs allocated to the scheduled PDSCH.

[0485] If the terminal is a narrowband terminal, the terminal can receive the first repetition (1721). Here, the first repetition is RBs within the bandwidth of the CORESET, which may be less than or equal to the bandwidth of the narrowband terminal.

[0486] If the terminal is a broadband terminal, the terminal can receive one or more of the first repetition (1721) and the second repetition (1722). Therefore, if the terminal is a broadband terminal, it can obtain higher coverage by receiving multiple repetitions.

[0487] The terminal can configure whether to repeat the frequency-axis PDSCH and the number of repetitions through the MIB or auxiliary MIB. For example, the spare bit (1 bit) of the MIB can indicate whether to repeat the PDSCH. If the spare bit (1 bit) is the first value ('0'), the PDSCH may not be transmitted repeatedly along the frequency axis. If the spare bit (1 bit) is the second value ('1'), the PDSCH may be transmitted repeatedly along the frequency axis.

[0488] FIG. 18 is a diagram for receiving a PDSCH in multiple reception opportunities according to one embodiment of the present disclosure.

[0489] Referring to Figures 16 and 17, narrowband terminals may have lower coverage compared to wideband terminals. To provide higher coverage to narrowband terminals, the PDSCH containing system information may be received in multiple reception opportunities. Here, the reception opportunities may include different OFDM symbols.

[0490] Referring to FIG. 18, the starting RB of CORESET (1810) is indicated by an RB-unit offset (1830) from SS / PBCH, and the terminal can receive a PDCCH from CORESET (1810). The PDCCH can schedule multiple PDSCHs including system information. The multiple PDSCHs can be composed of M PDSCHs (1820, 1821, 1822). The multiple PDSCHs can include a system information block in one of the following ways.

[0491] In the first method, the system information block is divided into multiple sub-system information blocks, each with an individual CRC attached, and can be individually encoded and transmitted on multiple PDSCHs. The system information block can be SIB1, and when SIB1 consists of B bits, multiple sub-SIB1s can be B1, B2, B3, ..., BM bits. That is, the i-th sub-SIB1 is B i bits. More specifically, each sub-SIB (e.g., B i ) can be transmitted with a CRC attached and encoded. The terminal can receive the first sub-SIB1 on the first PDSCH (1820). The terminal can receive the second sub-SIB1 on the second PDSCH (1821). The terminal can receive the M-th sub-SIB1 on the M-th PDSCH (1822). The terminal can receive the sub-SIB1 on each PDSCH and determine whether reception of each sub-SIB1 is successful.

[0492] In a second method, a system information block is encoded with a common CRC attached, and the encoded coded bits can be transmitted on multiple PDSCHs. The system information block can be SIB1, and when SIB1 consists of B bits, a CRC for the B bits can be attached. The terminal can be B+N. CRC (N CRC The number of attached CRC bits) can be encoded into a channel code. The coded bits can be transmitted on M PDSCHs. That is, the terminal can receive the first part of the coded bits on the first PDSCH (1820), the second part on the second PDSCH (1821), and the M-th part on the M-th PDSCH (1822). The terminal can receive the M PDSCHs and perform channel code decoding. And, using the attached CRC, it can be determined whether SIB1 was correctly received.

[0493] In the first method and the second method, the method for determining the length of SIB1 (i.e., the B value) may be at least one of the following.

[0494] In a first method, the terminal can determine the length of SIB1 based on the scheduling information of the first PDSCH (1820). That is, the terminal can determine the length of SIB1 based on the number of REs included in the first PDSCH (1820), regardless of the number of PDSCH repetitions scheduled. Coverage can be increased through PDSCH repetition.

[0495] In a second method, the terminal can determine the length of SIB1 based on the scheduling information of all PDSCHs (1820, 1821, 1822). That is, the length of SIB1 can be determined based on the number of REs included in all PDSCHs (1820, 1821, 1822). Through PDSCH repetition, SIB1 of a longer length can be transmitted.

[0496] FIG. 19 is a flowchart showing the operation of a terminal according to an embodiment of the present disclosure.

[0497] Referring to FIG. 19, the method by which a terminal receives a PDSCH including system information is as follows.

[0498] In step 1 (1900), the terminal can obtain information about a CORESET for receiving system information from the MIB. The MIB can be received in the SS / PBCH block. The information about the CORESET can include information about the frequency location of the CORESET. Here, the frequency location of the CORESET can include the location of the starting RB of the CORESET and the number of RBs included in the CORESET.

[0499] In step 2 (1910), the terminal can monitor the PDCCH in the CORESET. The terminal can receive a DCI format in which the CRC is scrambled with SI-RNTI. The DCI format can schedule a PDSCH including system information.

[0500] In step 3 (1920), the terminal can obtain frequency information for FDRA field interpretation from the received DCI format. Here, the frequency information may be information regarding a reference bandwidth portion. The reference bandwidth portion may be determined based on frequency information of the SS / PBCH block or frequency information of the CORESET.

[0501] In step 4 (1930), the terminal can interpret the FDRA field based on the reference bandwidth portion information to determine the RBs on which the PDSCH is scheduled. The determined RBs can be included in the reference bandwidth portion.

[0502] In step 5 (1940), the terminal can receive PDSCH in scheduled RBs and obtain system information from the PDSCH.

[0503] FIG. 20 is a flowchart showing the operation of a terminal according to an embodiment of the present disclosure.

[0504] Referring to FIG. 20, the method by which a terminal receives a PDSCH including system information is as follows.

[0505] In the first step (2000), the terminal can obtain first frequency information and second frequency information from the MIB or auxiliary MIB. Here, the frequency information can include at least a starting RB index and the number of consecutive RBs.

[0506] In the second step (2010), the terminal may receive a PDCCH scheduling a PDSCH based on first frequency information. The first frequency information may be associated with the bandwidth of the CORESET in which the PDCCH is received.

[0507] In the third step (2020), the terminal can determine the RBs on which the PDSCH is scheduled based on the second frequency information. The FDRA field of the DCI format included in the received PDCCH can be interpreted based on the second frequency information.

[0508] In step 4 (2040), the terminal can receive PDSCH in scheduled RBs and obtain system information from the PDSCH.

[0509] FIG. 21 is a diagram illustrating the structure of a terminal in a wireless communication system according to one embodiment of the present disclosure.

[0510] Referring to FIG. 21, the terminal may include a transceiver, which refers to a terminal receiving unit (2100) and a terminal transmitting unit (2110), a memory (not shown), and a terminal processing unit (2105, or a terminal control unit or processor). Depending on the communication method of the terminal described above, the transceiver units (2100, 2110), the memory, and the terminal processing unit (2105) of the terminal may operate. However, the components of the terminal are not limited to the examples described above. For example, the terminal may include more or fewer components than the components described above. In addition, the transceiver, the memory, and the processor may be implemented in the form of a single chip.

[0511] A transceiver unit can transmit and receive signals with a base station or other terminals. The signals may include control information and data. To this end, the transceiver unit may include an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies and down-converts the frequency of a received signal. However, this is only one embodiment of the transceiver unit, and the components of the transceiver unit are not limited to the RF transmitter and RF receiver.

[0512] Additionally, the transceiver can receive a signal through a wireless channel and output it to the processor, and transmit a signal output from the processor through the wireless channel.

[0513] Memory can store programs and data necessary for the terminal's operation. Furthermore, memory can store control information or data included in signals transmitted and received by the terminal. Memory can be comprised of a storage medium, such as ROM, RAM, a hard disk, CD-ROM, or DVD, or a combination of such storage media. Furthermore, there can be multiple memories.

[0514] Additionally, the processor can control a series of processes to enable the terminal to operate according to the aforementioned embodiments. For example, the processor can receive DCI consisting of two layers and control components of the terminal to simultaneously receive multiple PDSCHs. There may be multiple processors, and the processors can perform terminal component control operations by executing programs stored in memory.

[0515] FIG. 22 is a diagram illustrating the structure of a base station in a wireless communication system according to one embodiment of the present disclosure.

[0516] Referring to FIG. 22, the base station may include a transceiver, which refers to a base station receiver (2200) and a base station transmitter (2210), a memory (not shown), and a base station processor (2205, or a base station control unit or processor). Depending on the communication method of the base station described above, the transceiver (2200, 2210), the memory, and the base station processor (2205) of the base station may operate. However, the components of the base station are not limited to the examples described above. For example, the base station may include more or fewer components than the components described above. In addition, the transceiver, the memory, and the processor may be implemented in the form of a single chip.

[0517] The transceiver can transmit and receive signals with a terminal or another base station. The signals may include control information and data. To this end, the transceiver may include an RF transmitter that up-converts and amplifies the frequency of a transmitted signal, and an RF receiver that low-noise amplifies and down-converts the frequency of a received signal. However, this is merely one embodiment of the transceiver, and the components of the transceiver are not limited to the RF transmitter and RF receiver.

[0518] Additionally, the transceiver can receive a signal through a wireless channel and output it to the processor, and transmit the signal output from the processor through the wireless channel.

[0519] The memory can store programs and data necessary for the operation of the base station. Furthermore, the memory can store control information or data included in signals transmitted and received by the base station. The memory can be comprised of a storage medium, such as ROM, RAM, a hard disk, CD-ROM, or DVD, or a combination of such storage media. Furthermore, there can be multiple memories.

[0520] The processor can control a series of processes to enable the base station to operate according to the embodiments of the present disclosure described above. For example, the processor can configure two layers of DCIs containing allocation information for multiple PDSCHs and control each component of the base station to transmit them. There may be multiple processors, and the processors can perform component control operations of the base station by executing programs stored in memory.

[0521] The methods according to the embodiments described in the claims or specification of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software.

[0522] When implemented in software, a computer-readable storage medium storing one or more programs (software modules) may be provided. The one or more programs stored in the computer-readable storage medium are configured for execution by one or more processors within an electronic device. The one or more programs include instructions that cause the electronic device to execute methods according to the embodiments described in the claims or specification of the present disclosure.

[0523] These programs (software modules, software) may be stored in random access memory, non-volatile memory including flash memory, read only memory (ROM), electrically erasable programmable read only memory (EEPROM), magnetic disc storage device, compact disc ROM (CD-ROM), digital versatile discs (DVDs) or other forms of optical storage device, magnetic cassette. Or, they may be stored in a memory configured as a combination of some or all of these. In addition, each configuration memory may be included in multiple numbers.

[0524] Additionally, the program may be stored on an attachable storage device that is accessible via a communication network, such as the Internet, an intranet, a local area network (LAN), a wide local area network (WLAN), a storage area network (SAN), or a combination thereof. Such a storage device may be connected to a device performing an embodiment of the present disclosure via an external port. Additionally, a separate storage device on the communication network may be connected to a device performing an embodiment of the present disclosure.

[0525] In the specific embodiments of the present disclosure described above, components included in the invention are expressed in the singular or plural form, depending on the specific embodiment presented. However, the singular or plural expressions are selected to suit the presented situation for convenience of explanation, and the present disclosure is not limited to singular or plural components. Components expressed in the plural form may be composed of singular elements, or components expressed in the singular form may be composed of plural elements.

[0526] Meanwhile, the embodiments of the present disclosure disclosed in this specification and drawings are only specific examples to easily explain the technical contents of the present disclosure and help understand the present disclosure, and are not intended to limit the scope of the present disclosure. In other words, it will be apparent to those skilled in the art that other modifications based on the technical idea of ​​the present disclosure are possible. In addition, the above-mentioned embodiments can be combined and operated with each other as needed. For example, parts of one embodiment of the present disclosure and parts of another embodiment can be combined with each other to operate a base station and a terminal. For example, parts of the first embodiment and the second embodiment of the present disclosure can be combined with each other to operate a base station and a terminal. In addition, although the above-mentioned embodiments have been presented based on an FDD LTE system, other modifications based on the technical idea of ​​the above-mentioned embodiments can be implemented with other systems such as a TDD LTE system, 5G, or NR system.

[0527] Meanwhile, the order of description in the drawings explaining the method of the present invention does not necessarily correspond to the order of execution, and the order of precedence may be changed or executed in parallel.

[0528] Alternatively, the drawings illustrating the method of the present invention may omit some components and include only some components within a scope that does not harm the essence of the present invention.

[0529] In addition, the method of the present invention may be implemented by combining some or all of the contents included in each embodiment within a scope that does not harm the essence of the invention.

[0530] In the specific embodiments of the present invention described above, components included in the invention are expressed in the singular or plural form depending on the specific embodiment presented. However, the singular or plural expressions are selected to suit the presented situation for convenience of explanation, and the present invention is not limited to singular or plural components. Even components expressed in the plural form may be composed of singular elements, or even components expressed in the singular form may be composed of plural elements.

[0531] Meanwhile, while the detailed description of the present invention has described specific embodiments, it goes without saying that various modifications are possible without departing from the scope of the present invention. Therefore, the scope of the present invention should not be limited to the described embodiments, but should be determined not only by the scope of the following claims but also by equivalents of the scope of the claims. In other words, it will be apparent to those skilled in the art that other modifications based on the technical idea of ​​the present disclosure are possible. In addition, each of the above embodiments can be combined and operated with each other as needed. For example, parts of the methods proposed in the present disclosure can be combined with each other to operate a base station and a terminal. In addition, although the above embodiments have been presented based on a 5G, NR system, other modifications based on the technical idea of ​​the above embodiments can be implemented with other systems such as LTE, LTE-A, and LTE-A-Pro systems.

Claims

1. In a method performed by a UE (user equipment) in a wireless communication system, A step of receiving a master information block (MIB) containing information about a control resource set (CORESET) from a base station; A step of receiving DCI (downlink control information) including reference bandwidth information and FDRA (frequency domain resource assignment) field by monitoring PDCCH (physical downlink control channel) within the CORESET from the base station; A step of determining a bandwidth for a PDSCH (physical downlink shared channel) based on the reference bandwidth information and the FDRA field; and A method comprising the step of receiving, from the base station, the PDSCH including a system information block within the bandwidth.

2. In claim 1, The above reference bandwidth is greater than the bandwidth of the above CORESET, The above reference bandwidth information includes information indicating an index of the above reference bandwidth, A method in which the FDRA field for the PDSCH is interpreted based on information indicating an index of the reference bandwidth.

3. In claim 2, The length of the above FDRA field is interpreted based on the maximum size of the above reference bandwidth, A method in which the number of resource blocks (RBs) of a reference bandwidth corresponding to information indicating an index of the reference bandwidth is interpreted in relation to the number of bandwidth RBs for the PDSCH.

4. In claim 1, The above PDSCH is repeated at least once in the frequency domain, If the maximum bandwidth supported by the UE is greater than or equal to a threshold, the system information is received in one of the repeated PDSCHs, If the maximum bandwidth supported by the UE is less than a threshold, the system information is received in one or more of the repeated PDSCHs, A method wherein the above one PDSCH is less than or equal to the maximum bandwidth supported by the terminal.

5. For UE (user equipment): At least one transceiver; At least one processor communicatively coupled to said at least one transceiver; and At least one memory communicatively coupled to said at least one processor and storing instructions, The above instructions are executed individually or in any combination by the at least one processor so that the UE: Receive a MIB (master information block) containing information about CORESET (control resource set) from a base station, From the base station, by monitoring the PDCCH (physical downlink control channel) within the CORESET, DCI (downlink control information) including reference bandwidth information and FDRA (frequency domain resource assignment) field is received, Determine the bandwidth for PDSCH (physical downlink shared channel) based on the above reference bandwidth information and the above FDRA field, A UE configured to receive the PDSCH including a system information block within the bandwidth from the base station.

6. In claim 5, The above reference bandwidth is greater than the bandwidth of the above CORESET, The above reference bandwidth information includes information indicating an index of the above reference bandwidth, A UE in which the FDRA field for the PDSCH is interpreted based on information indicating an index of the reference bandwidth.

7. In claim 6, The length of the above FDRA field is interpreted based on the maximum size of the above reference bandwidth, The number of resource blocks (RBs) of the reference bandwidth corresponding to the information indicating the index of the reference bandwidth is interpreted in relation to the number of bandwidth RBs for the PDSCH, A UE in which a field corresponding to one bit is interpreted based on information indicating an index of the reference bandwidth among the above FDRA fields and the corresponding reference bandwidth.

8. In claim 5, The above PDSCH is repeated at least once in the frequency domain, If the maximum bandwidth supported by the UE is greater than or equal to a threshold, the system information is received in one of the repeated PDSCHs, If the maximum bandwidth supported by the UE is less than a threshold, the system information is received in one or more of the repeated PDSCHs, The above one PDSCH is less than or equal to the maximum bandwidth supported by the UE.

9. In a method performed by a base station in a wireless communication system, A step of transmitting a MIB (master information block) containing information about a CORESET (control resource set) to a UE (user equipment); A step of transmitting DCI (downlink control information) including reference bandwidth information and a frequency domain resource assignment (FDRA) field to the UE; A step of transmitting a PDSCH (physical downlink shared channel) including a system information block to the UE, A method wherein the above PDSCH is transmitted within a bandwidth associated with the above reference bandwidth information and the FDRA field.

10. In claim 9, The above reference bandwidth is greater than the bandwidth of the above CORESET, The above reference bandwidth information includes information indicating an index of the above reference bandwidth, A method in which information indicating an index of the above reference bandwidth is associated with the interpretation of the FDRA field for the above PDSCH.

11. In claim 10, The length of the above FDRA field is interpreted in relation to the maximum size of the above reference bandwidth, A method in which the number of resource blocks (RBs) of a reference bandwidth corresponding to information indicating an index of the reference bandwidth is interpreted in relation to the number of bandwidth RBs for the PDSCH.

12. In claim 9, The above PDSCH is repeated at least once in the frequency domain, If the maximum bandwidth supported by the UE is greater than or equal to a threshold, the system information is transmitted on one of the repeated PDSCHs, If the maximum bandwidth supported by the UE is less than a threshold, the system information is transmitted on one or more of the repeated PDSCHs, A method wherein the above one PDSCH is less than or equal to the maximum bandwidth supported by the terminal.

13. At the base station: At least one transceiver; At least one processor communicatively coupled to said at least one transceiver; and At least one memory communicatively coupled to said at least one processor and storing instructions, The above instructions are executed individually or in any combination by the at least one processor so that the base station: Transmitting DCI (downlink control information) including reference bandwidth information and FDRA (frequency domain resource assignment) field to the UE, To the UE, transmit a PDSCH (physical downlink shared channel) including a system information block, A base station, wherein the above PDSCH is transmitted within a bandwidth associated with the reference bandwidth information and the FDRA field.

14. In claim 13, The above reference bandwidth is greater than the bandwidth of the above CORESET, The above reference bandwidth information includes information indicating an index of the above reference bandwidth, Information indicating the index of the above reference bandwidth is associated with the interpretation of the FDRA field for the above PDSCH, the base station.

15. In claim 14, The length of the above FDRA field is interpreted in relation to the maximum size of the above reference bandwidth, A base station in which the number of resource blocks (RBs) of the reference bandwidth corresponding to information indicating the index of the reference bandwidth is interpreted in relation to the number of bandwidth RBs for the PDSCH.

Images