Method and device for transmitting and receiving sounding reference signal in communication system
The method for determining SRS resources in multi-cell scheduling within wireless communication systems addresses the complexity of resource configuration by using higher layer signaling and SRS request field mapping, enhancing system performance and supporting advanced services.
Patent Information
- Application Number
- PCT/KR2023/019715
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-11-03
- Filing Date
- 2023-12-01
- Publication Date
- 2024-11-21
AI Technical Summary
In wireless communication systems, particularly in 5G and beyond, determining SRS resources for multi-cell or multi-carrier scheduling is challenging due to complex resource configuration and mapping relationships, which affects the efficiency of transmission and reception.
A method and apparatus that involve receiving SRS resource configuration through higher layer signaling, identifying SRS resources based on downlink control information, and transmitting SRS resources for multiple cells using a specific mapping relationship indicated by a code point in the SRS request field, allowing for effective resource allocation and management.
This approach enhances the ability to manage and allocate SRS resources efficiently across multiple cells, improving communication system performance and supporting advanced services like V2X and metaverse applications by optimizing resource utilization and reducing latency.
Smart Images

Figure KR2023019715_21112024_PF_FP_ABST
Abstract
Description
Method and device for transmitting and receiving sounding reference signals in a communication system
[0001] The present disclosure relates to the operation of a terminal and a base station in a wireless communication system. Specifically, the present disclosure relates to a method for determining a transmission configuration indicator for multi-cell scheduling in a wireless communication system and a device capable of performing the same. Furthermore, the present disclosure relates to a method and device for transmitting and receiving a sounding reference signal (SRS) 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 wireless interface architecture / protocols is in progress for technologies such as intelligent factories (Industrial Internet of Things, IIoT) 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 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] One embodiment of the present disclosure is to provide a device and method capable of effectively providing a service in a mobile communication system.
[0009] One embodiment of the present disclosure provides a method and device for determining SRS resources when multi-cell or multi-carrier scheduling is applied in a communication system.
[0010] The technical problems to be achieved in various embodiments of the present disclosure are not limited to those mentioned above, and other technical problems not mentioned can be considered by a person having ordinary skill in the art from various embodiments of the present disclosure described below.
[0011] According to one embodiment, a method performed by a terminal in a communication system may be provided.
[0012] According to one embodiment, the method may include receiving information about sounding reference signal (SRS) resource configuration via upper layer signaling.
[0013] According to one embodiment, the method may include receiving downlink control information (DCI) scheduling a plurality of cells.
[0014] According to one embodiment, the DCI may include an SRS request field.
[0015] According to one embodiment, the method may include identifying a plurality of SRS resources for the plurality of cells based on information about the SRS resource configuration and a code point of the SRS request field.
[0016] According to one embodiment, the code point of the SRS request field may indicate a mapping relationship between one or more SRS resource sets included in the SRS resource configuration and the plurality of cells.
[0017] According to one embodiment, the SRS resources for each cell may be included in a set of SRS resources corresponding to each cell.
[0018] According to one embodiment, the method may include transmitting an SRS for the plurality of cells based on the plurality of SRS resources.
[0019] According to one embodiment, the size of the SRS request field may be 4 bits.
[0020] According to one embodiment, the 2 most significant bits (MSBs) of the SRS request field may be associated with one or more of the plurality of cells.
[0021] According to one embodiment, the 2 least significant bits (LSBs) of the SRS request field may be associated with one or more cells other than the one or more cells among the plurality of cells.
[0022] According to one embodiment, each index of said one or more cells associated with said 2 MSBs may be smaller than each index of said one or more cells associated with said 2 LSBs.
[0023] According to one embodiment, the maximum number of said plurality of cells may be 4.
[0024] According to one embodiment, the DCI may further include a 4-bit field indicating the plurality of cells.
[0025] According to one embodiment, the format of the DCI may be DCI format 0_3 or DCI format 1_3.
[0026] According to one embodiment, an information element (IE) for the size of the SRS request field can be received via the upper layer signaling.
[0027] In one embodiment, the IE may be set separately according to the format of the DCI.
[0028] According to one embodiment, if a medium access control control element (MAC CE) that updates the mapping relationship is received prior to receiving the DCI, the mapping relationship can be identified as having been updated by the MAC CE.
[0029] According to one embodiment, the MAC CE may include information corresponding to the plurality of cells and information indicating one or more SRS resource sets mapped to specific values among code points of the SRS request field.
[0030] According to one embodiment, a terminal of a communication system may be provided.
[0031] According to one embodiment, the terminal may include a transceiver; and one or more processors connected to the transceiver.
[0032] According to one embodiment, the processor may be configured to receive information about sounding reference signal (SRS) resource configuration via upper layer signaling.
[0033] According to one embodiment, the processor may be configured to receive downlink control information (DCI) scheduling a plurality of cells.
[0034] According to one embodiment, the DCI may include an SRS request field.
[0035] According to one embodiment, the processor may be configured to identify a plurality of SRS resources for the plurality of cells based on information about the SRS resource configuration and a code point of the SRS request field.
[0036] According to one embodiment, the code point of the SRS request field may indicate a mapping relationship between one or more SRS resource sets included in the SRS resource configuration and the plurality of cells.
[0037] According to one embodiment, the SRS resources for each cell may be included in a set of SRS resources corresponding to each cell.
[0038] According to one embodiment, the processor may be configured to transmit an SRS for the plurality of cells based on the plurality of SRS resources.
[0039] According to one embodiment, a method performed by a base station in a communication system may be provided.
[0040] According to one embodiment, the method may include the step of transmitting information on sounding reference signal (SRS) resource configuration via upper layer signaling.
[0041] According to one embodiment, the method may include transmitting downlink control information (DCI) scheduling a plurality of cells.
[0042] According to one embodiment, the DCI may include an SRS request field.
[0043] According to one embodiment, the method may include transmitting an SRS for the plurality of cells based on a plurality of SRS resources.
[0044] According to one embodiment, the plurality of SRS resources may be based on information about the SRS resource configuration and a code point of the SRS request field.
[0045] According to one embodiment, the code point of the SRS request field may indicate a mapping relationship between one or more SRS resource sets included in the SRS resource configuration and the plurality of cells.
[0046] According to one embodiment, the SRS resources for each cell may be included in a set of SRS resources corresponding to each cell.
[0047] According to one embodiment, a base station of a communication system may be provided.
[0048] According to one embodiment, the base station may include a transceiver; and one or more processors connected to the transceiver.
[0049] According to one embodiment, the processor may be configured to: transmit information about sounding reference signal (SRS) resource configuration via upper layer signaling;
[0050] According to one embodiment, the processor may be configured to transmit downlink control information (DCI) scheduling a plurality of cells.
[0051] According to one embodiment, the DCI may include an SRS request field.
[0052] According to one embodiment, the processor may be configured to transmit an SRS for the plurality of cells based on a plurality of SRS resources.
[0053] According to one embodiment, the plurality of SRS resources may be based on information about the SRS resource configuration and a code point of the SRS request field.
[0054] According to one embodiment, the code point of the SRS request field may indicate a mapping relationship between one or more SRS resource sets included in the SRS resource configuration and the plurality of cells.
[0055] According to one embodiment, the SRS resources for each cell may be included in a set of SRS resources corresponding to each cell.
[0056] The various embodiments of the present disclosure described above are only some of the preferred embodiments of the present disclosure, and various embodiments reflecting the technical features of the various embodiments of the present disclosure can be derived and understood by a person having ordinary skill in the art based on the detailed description to be described below.
[0057] One embodiment of the present disclosure provides a device and method capable of effectively providing a service in a mobile communication system.
[0058] One embodiment of the present disclosure provides a method and device for determining SRS resources when multi-cell or multi-carrier scheduling is applied in a communication system.
[0059] The effects that can be obtained from various embodiments of the present disclosure are not limited to the effects mentioned above, and other effects that are not mentioned can be clearly derived and understood by a person having ordinary skill in the art based on the detailed description below.
[0060] 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.
[0061] 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.
[0062] 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.
[0063] FIG. 4 is a diagram illustrating a wireless protocol structure of a base station and a terminal in a single cell, carrier aggregation, and dual connectivity situation in a wireless communication system according to one embodiment of the present disclosure.
[0064] FIG. 5 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.
[0065] FIG. 6 is a diagram illustrating the structure of a downlink control channel in a wireless communication system according to one embodiment of the present disclosure.
[0066] FIG. 7 is a diagram illustrating an example of a control resource set and a beam setting of a search space in a wireless communication system according to one embodiment of the present disclosure.
[0067] FIG. 8 is a diagram illustrating an example of frequency axis resource allocation of PDSCH or PUSCH in a wireless communication system according to one embodiment of the present disclosure.
[0068] FIG. 9 is a diagram illustrating a VRB-PRB interleaving method of PDSCH in FDRA type-1 resource allocation according to one embodiment of the present disclosure.
[0069] FIG. 10 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.
[0070] FIG. 11 is a diagram illustrating an example in which MC-DCI according to one embodiment of the present disclosure includes multiple FDRA fields.
[0071] FIG. 12 is a diagram illustrating an example in which MC-DCI according to one embodiment of the present disclosure includes at least one of a cell set indicator field, a scheduling cell indicator field, and a plurality of FDRA fields.
[0072] FIG. 13 is a diagram illustrating an example of a field indicating frequency domain resource allocation information according to a subcarrier spacing of a cell according to one embodiment of the present disclosure.
[0073] FIG. 14 is a diagram illustrating an example of a field indicating multiple cells and SRS requests in MC-DCI according to one embodiment of the present disclosure.
[0074] FIG. 15 is a diagram illustrating an example of a field indicating multiple cells and SRS requests in MC-DCI according to one embodiment of the present disclosure.
[0075] FIG. 16 is a diagram illustrating an example of a MAC-CE message for indicating multiple cells and SRS requests in MC-DCI according to one embodiment of the present disclosure.
[0076] FIG. 17 is a diagram illustrating the operation of a terminal according to one embodiment of the present disclosure.
[0077] FIG. 18 is a diagram illustrating the operation of a base station according to one embodiment of the present disclosure.
[0078] FIG. 19 is a diagram illustrating the operation of a terminal according to one embodiment of the present disclosure.
[0079] FIG. 20 is a diagram illustrating the operation of a base station according to one embodiment of the present disclosure.
[0080] FIG. 21 is a diagram illustrating the structure of a terminal in a wireless communication system according to one embodiment of the present disclosure.
[0081] 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.
[0082] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the attached drawings.
[0083] 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 ensure that the gist of the present disclosure is conveyed more clearly without obscuring it by omitting unnecessary explanations.
[0084] 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. Identical or corresponding components in each drawing are assigned the same reference numbers.
[0085] 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.
[0086] Hereinafter, the base station is an entity that performs resource allocation of the terminal, and may be at least one of a gNode B, 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. 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. In addition, although the LTE or LTE-A system may be described below as an example, the embodiments of the present disclosure may also be applied to other communication systems having a similar technical background or channel type. For example, the 5th generation mobile communication technology (5G, new radio, NR) developed after LTE-A may be included here, and the 5G below may also be a concept that includes existing LTE, LTE-A, and other similar services. In addition, the present disclosure may be applied to other communication systems through some modifications within a scope that does not significantly deviate from the scope of the present disclosure, as judged by a person having skilled technical knowledge.
[0087] At this time, it will be understood that each block of the processing flowchart drawings and combinations of the flowchart drawings can be performed by computer program instructions. These computer program instructions can be installed in a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing equipment, so that the instructions executed by the processor of the computer or other programmable data processing equipment create a 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 a manufactured item that includes an 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).
[0088] 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 described in the blocks may occur out of order. For example, two blocks depicted in succession may actually be executed substantially concurrently, or the blocks may sometimes be executed in reverse order, depending on their respective functions.
[0089] Here, the term '~ part' used in this embodiment means software or hardware components such as FPGA (Field Programmable Gate Array) or ASIC (Application Specific Integrated Circuit), and the '~ part' performs certain roles. However, the '~ part' is not limited to software or hardware. The '~ part' may be configured to be on an addressable storage medium or may be configured to play one or more processors. Therefore, as an example, the '~ part' includes components such as software components, object-oriented software components, class components, and task components, processes, functions, properties, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functions provided within the components and '~ parts' may be combined into a smaller number of components and '~ parts' or further separated into additional components and '~ parts'. Additionally, the components and '~parts' may be implemented to activate one or more CPUs within a device or secure multimedia card. In addition, in an embodiment, the '~parts' may include one or more processors.
[0090] 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.
[0091] 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 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.
[0092] As a 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).
[0093] 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.
[0094] 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 / km2) 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, such as basements, beyond cell coverage. This may require broader coverage compared to 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.
[0095] Finally, URLLC refers to a cellular-based wireless communication service used for a specific purpose (mission-critical). For example, services such as remote control of robots or machinery, industrial automation, unmanned aerial vehicles, remote health care, and emergency alerts can be considered. Therefore, the communication provided by URLLC must provide very low latency and very high reliability. For example, a service supporting URLLC must satisfy an air interface latency of less than 0.5 milliseconds and, at the same time, must have a 10 -5The following packet error rate (PER) requirements apply. Therefore, for services supporting URLLC, 5G systems must provide a smaller Transmit Time Interval (TTI) than other services. Simultaneously, design considerations may require the allocation of extensive resources in the frequency band to ensure communication link reliability.
[0096] 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.
[0097] Hereinafter, a / b can be understood as at least one of a or b.
[0098] [NR time-frequency resources]
[0099] Below, the frame structure of the 5G system is described in more detail with reference to drawings.
[0100] Figure 1 is a diagram illustrating the basic structure of the time-frequency domain, which is a radio resource domain in which data or control channels are transmitted in a 5G system.
[0101] 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 symbol (102) on the time axis and 1 subcarrier (103) on the frequency axis. In the frequency domain (For example, 12) consecutive REs can constitute one resource block (RB, 104). One subframe (110) on the time axis can include multiple OFDM symbols (102). For example, the length of one subframe can be 1 ms.
[0102] 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.
[0103] 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 10ms. One subframe (201) can be defined as 1ms, 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, cases where the subcarrier spacing setting value μ = 0 (204) and μ = 1 (205) are illustrated. When μ = 0 (204), 1 subframe (201) may be composed of one slot (202), and when μ = 1 (205), 1 subframe (201) may be composed of two 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 [Table 1] below.
[0104] [Table 1]
[0105]
[0106] [Bandwidth Part (BWP)]
[0107] Next, the bandwidth part (BWP) setting in the 5G communication system will be explained in detail with reference to the drawing.
[0108] 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.
[0109] FIG. 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 the information in [Table 2] below for each bandwidth portion.
[0110] [Table 2]
[0111]
[0112] Of course, the above example is not limited, and in addition to the above configuration information, various parameters related to the bandwidth portion can be configured for the terminal. The above information can be transmitted from the base station to the terminal via upper layer signaling, for example, RRC (Radio Resource Control) signaling. At least one bandwidth portion among the configured one or more bandwidth portions can be activated. Whether or not the configured bandwidth portion is activated can be semi-statically transmitted from the base station to the terminal via RRC signaling or dynamically transmitted via DCI.
[0113] According to some embodiments, a terminal before RRC connection can be configured with 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 about a control resource set (CORESET) and a search space in which a PDCCH for receiving system information required for initial access (which may correspond to Remaining System Information (RMSI) or System Information Block 1 (SIB1)) and search space can be transmitted through the MIB during the initial access phase. The control space and search space configured by the MIB can 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 space #0 through the MIB. Additionally, the base station can notify the terminal of the monitoring cycle and monitoring occasion settings for control area #0, i.e., search space #0, via the MIB. The terminal can consider the frequency range set as control area #0 obtained from the MIB as the initial bandwidth portion for initial access. At this time, the identifier (ID) of the initial bandwidth portion can be considered as 0.
[0114] The settings for the bandwidth supported by the above 5G can be used for various purposes.
[0115] In some embodiments, 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.
[0116] 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, two bandwidth segments may be configured with subcarrier spacings of 15 kHz and 30 kHz, respectively. The different bandwidth segments may be frequency-division multiplexed (FDM), 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.
[0117] Furthermore, in some embodiments, the base station may configure bandwidth portions with different bandwidth sizes for the terminal for the purpose of reducing power consumption of the terminal. For example, if the terminal supports a very large bandwidth, for example, 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 situation where there is no traffic may be very inefficient in terms of power consumption. To reduce power consumption of the terminal, the base station may configure a bandwidth portion with a relatively small bandwidth, for example, 20 MHz, for the terminal. In a situation where there is no traffic, 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.
[0118] In the method for setting the bandwidth portion, terminals prior to RRC connection (Connected) can receive configuration information for the initial bandwidth portion (Initial BWP) through the MIB during the initial access phase. More specifically, the terminal can receive a control region (i.e., CORESET) for a downlink control channel on which a DCI scheduling a System Information Block (SIB) can be transmitted from the MIB of the Physical Broadcast Channel (PBCH). The bandwidth of the control region set by the MIB can be regarded as the initial bandwidth portion, and the terminal can receive the Physical Downlink Shared Channel (PDSCH) on which the SIB is transmitted through the set initial bandwidth portion. In addition to receiving the SIB, the initial bandwidth portion can also be utilized for other system information (Other System Information (OSI), paging, and random access).
[0119] [Bandwidth Part (BWP) Change]
[0120] When one or more bandwidth part values are set for a terminal, the base station can instruct the terminal to change (or switch, transition) the bandwidth part value 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.
[0121] As described above, since DCI-based bandwidth part change can be indicated by DCI scheduling PDSCH or PUSCH, when a terminal receives a bandwidth part change request, it must be able to receive or transmit PDSCH or PUSCH scheduled by the corresponding DCI without difficulty in the changed bandwidth part. To this end, the standard stipulates the delay time (T) required when changing the bandwidth part. BWP ) and can be defined as in [Table 3] below, for example.
[0122] [Table 3]
[0123]
[0124] 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.
[0125] 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 The completion can be done 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. When 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 the 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 the time domain resource allocation for the data channel. Accordingly, the terminal can determine whether the DCI instructing the bandwidth portion change is after the bandwidth portion change delay time (TBWP ) may not be expected to indicate a slot offset (K0 or K2) value smaller than that.
[0126] 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 point 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).
[0127] [SS / PBCH block]
[0128] Next, we will explain the SS (Synchronization Signal) / PBCH block in 5G.
[0129] 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.
[0130] - PSS: A signal that serves as a reference for downlink time / frequency synchronization and provides some information about the cell ID.
[0131] - 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.
[0132] - PBCH: Provides essential system information required for transmission and reception of data and control channels of a terminal. 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.
[0133] - 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.
[0134] 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.
[0135] [CA / DC related]
[0136] FIG. 4 is a diagram illustrating a wireless protocol structure of a base station and a terminal in a single cell, carrier aggregation, and dual connectivity situation according to one embodiment of the present disclosure.
[0137] Referring to FIG. 4, the wireless protocol of the next-generation mobile communication system is composed of NR SDAP (Service Data Adaptation Protocol S25, S70), NR PDCP (Packet Data Convergence Protocol S30, S65), NR RLC (Radio Link Control S35, S60), and NR MAC (Medium Access Control S40, S55) in the terminal and NR base station, respectively.
[0138] Key features of NR SDAP (S25, S70) may include some of the following:
[0139] - Transfer of user plane data
[0140] - Mapping function between QoS flow and data bearer for both DL and UL
[0141] - Marking function of QoS flow ID for both uplink and downlink (marking QoS flow ID in both DL and UL packets)
[0142] - Ability to map reflective QoS flow to data bearer for uplink SDAP PDUs (reflective QoS flow to DRB mapping for the UL SDAP PDUs).
[0143] For the above SDAP layer device, the terminal can be configured by an 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 a smooth service.
[0144] The main functions of NR PDCP (S30, S65) may include some of the following functions:
[0145] - Header compression and decompression (ROHC only)
[0146] - User data transfer function
[0147] - In-sequence delivery of upper layer PDUs
[0148] - Out-of-sequence delivery of upper layer PDUs
[0149] - PDCP PDU reordering for reception
[0150] - Duplicate detection of lower layer SDUs
[0151] - Retransmission function (Retransmission of PDCP SDUs)
[0152] - Encryption and decryption functions (Ciphering and deciphering)
[0153] - Timer-based SDU discard in uplink.
[0154] 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.
[0155] The main functions of NR RLC (S35, S60) may include some of the following functions:
[0156] - Data transfer function (Transfer of upper layer PDUs)
[0157] - In-sequence delivery of upper layer PDUs
[0158] - Out-of-sequence delivery of upper layer PDUs
[0159] - ARQ function (Error Correction through ARQ)
[0160] - Concatenation, segmentation and reassembly of RLC SDUs
[0161] - Re-segmentation of RLC data PDUs
[0162] - Reordering of RLC data PDUs
[0163] - Duplicate detection function
[0164] - Protocol error detection
[0165] - RLC SDU discard function
[0166] - RLC re-establishment function
[0167] 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.
[0168] 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 one RLC SDU is received divided into multiple RLC SDUs, and may include a function of storing and arranging the RLC SN or PDCP SN of received RLC PDUs to record lost RLC PDUs.
[0169] NR MAC (S40, S55) 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.
[0170] - Mapping function (Mapping between logical channels and transport channels)
[0171] - Multiplexing / demultiplexing of MAC SDUs
[0172] - Scheduling information reporting function
[0173] - HARQ function (Error correction through HARQ)
[0174] - Priority handling between logical channels of one UE
[0175] - Priority handling between UEs by means of dynamic scheduling
[0176] - MBMS service identification function
[0177] - Transport format selection function
[0178] - Padding function
[0179] The NR PHY layer (S45, S50) can perform operations such as channel coding and modulating upper layer data, converting it into OFDM symbols and transmitting it over a wireless channel, or demodulating and channel decoding OFDM symbols received over a wireless channel and transmitting them to a higher layer.
[0180] 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 S00. On the other hand, when a base station transmits data to a terminal based on CA (carrier aggregation) using multiple carriers in a single TRP, the base station and the terminal use a protocol structure that has a single structure up to RLC, but multiplexes the PHY layer through the MAC layer, such as S10. As another example, when a base station transmits data to a terminal based on DC (dual connectivity) using multiple carriers in multiple TRPs, the base station and the terminal use a protocol structure that has a single structure up to RLC, but multiplexes the PHY layer through the MAC layer, such as S20.
[0181] [PDCCH: DCI related]
[0182] Next, we will specifically explain downlink control information (DCI) in 5G systems.
[0183] 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 defined between the base station and the terminal, and the non-fallback DCI format can include configurable fields.
[0184] 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.
[0185] 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).
[0186] 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] below.
[0187] [Table 4]
[0188]
[0189] 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] below.
[0190] [Table 5]
[0191]
[0192]
[0193]
[0194] 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] below.
[0195] [Table 6]
[0196]
[0197] 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] below.
[0198] [Table 7]
[0199]
[0200] [PDCCH: CORESET, REG, CCE, Search Space]
[0201] Below, the downlink control channel in a 5G communication system will be described in more detail with reference to drawings.
[0202] FIG. 5 is a diagram illustrating 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. 5 illustrates an example in which two control regions (Control Region #1 (501), Control Region #2 (502)) are set within a UE bandwidth part (510) in the frequency axis and one slot (520) in the time axis. The control regions (501, 502) may be set to specific frequency resources (503) within the entire UE bandwidth part (510) in the frequency axis. The time axis may be set to one or more OFDM symbols, which may be defined as the control region length (Control Resource Set Duration, 504). Referring to the example illustrated in FIG. 5, Control Region #1 (501) is set to a control region length of two symbols, and Control Region #2 (502) is set to a control region length of one symbol.
[0203] In the aforementioned 5G, the control region can be established by the base station to the terminal via higher-layer signaling (e.g., system information, Master Information Block (MIB), Radio Resource Control (RRC) signaling). Establishing a control region for the terminal means providing information such as the control region identifier, 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] below.
[0204] [Table 8]
[0205]
[0206] 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. FIG. 6 is a diagram showing an example of a basic unit of time and frequency resources constituting a downlink control channel that can be used in 5G. According to FIG. 6, the basic unit of time and frequency resources constituting the control channel can be referred to as a REG (Resource Element Group, 603), and the REG (603) can be defined as 1 OFDM symbol (601) in the time axis and 1 PRB (Physical Resource Block, 602) in the frequency axis, i.e., 12 subcarriers. The base station can configure a downlink control channel allocation unit by concatenating REGs (6903).
[0207] As illustrated in FIG. 6, if the basic unit to which a downlink control channel is allocated in 5G is called a CCE (Control Channel Element, 604), 1 CCE (604) can be composed of multiple REGs (603). Taking the REG (603) illustrated in FIG. 6 as an example, the REG (603) can be composed of 12 REs, and if 1 CCE (604) is composed of 6 REGs (603), 1 CCE (604) can be composed of 72 REs. When a downlink control region is established, the region can be composed of multiple CCEs (604), and a specific downlink control channel can be mapped to one or multiple CCEs (604) and transmitted according to the aggregation level (AL) within the control region. CCEs (604) within the control area are distinguished by numbers, and the numbers of the CCEs (604) can be assigned according to a logical mapping method.
[0208] The basic unit of the downlink control channel illustrated in FIG. 6, that is, the REG (603), may include both the REs to which the DCI is mapped and the areas to which the DMRS (605), which is a reference signal for decoding the REs, is mapped. As shown in FIG. 6, three DMRSs (605) may be transmitted within one REG (603). 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.
[0209] 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.
[0210] In 5G, parameters for the search space for PDCCH can be configured from the base station to the 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 information in [Table 9] below can be included.
[0211] [Table 9]
[0212]
[0213]
[0214] 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.
[0215] 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.
[0216] 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.
[0217] - 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
[0218] - DCI format 2_0 with CRC scrambled by SFI-RNTI
[0219] - DCI format 2_1 with CRC scrambled by INT-RNTI
[0220] - DCI format 2_2 with CRC scrambled by TPC-PUSCH-RNTI, TPC-PUCCH-RNTI
[0221] - DCI format 2_3 with CRC scrambled by TPC-SRS-RNTI
[0222] 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.
[0223] - DCI format 0_0 / 1_0 with CRC scrambled by C-RNTI, CS-RNTI, TC-RNTI
[0224] - DCI format 1_0 / 1_1 with CRC scrambled by C-RNTI, CS-RNTI, TC-RNTI
[0225] The RNTIs specified may follow the definitions and uses below.
[0226] - C-RNTI (Cell RNTI): For terminal-specific PDSCH scheduling purposes.
[0227] - TC-RNTI (Temporary Cell RNTI): For terminal-specific PDSCH scheduling purposes.
[0228] - CS-RNTI (Configured Scheduling RNTI): Used for terminal-specific PDSCH scheduling that is set semi-statically.
[0229] - RA-RNTI (Random Access RNTI): Used for PDSCH scheduling in the random access phase.
[0230] - P-RNTI (Paging RNTI): Used for scheduling PDSCH where paging is transmitted.
[0231] - SI-RNTI (System Information RNTI): Used for scheduling PDSCH where system information is transmitted.
[0232] - INT-RNTI (Interruption RNTI): Used to indicate whether pucturing is in progress for PDSCH.
[0233] - TPC-PUSCH-RNTI (Transmit Power Control for PUSCH RNTI): Used to indicate power control commands for PUSCH.
[0234] - TPC-PUCCH-RNTI (Transmit Power Control for PUCCH RNTI): Used to indicate power control commands for PUCCH.
[0235] - TPC-SRS-RNTI (Transmit Power Control for SRS RNTI): Used to indicate power control commands for SRS.
[0236] The aforementioned specified DCI formats may follow the definitions in [Table 10] below.
[0237] [Table 10]
[0238]
[0239] In 5G, the search space of aggregation level L in the control region p and search space set s can be expressed as in the following mathematical expression 1.
[0240] [Mathematical Formula 1]
[0241]
[0242] - : Integration level
[0243] - : Carrier Index
[0244] - : Total number of CCEs existing within the control region p
[0245] - : slot index
[0246] - : Number of PDCCH candidates for aggregation level L
[0247] - : PDCCH candidate index of aggregation level L
[0248] -
[0249] - , , , , ,
[0250] - : Terminal identifier
[0251] The value can be 0 for a common search space.
[0252] 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.
[0253] In 5G, since multiple search space sets can be configured 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 configured with an X-slot period and search space set #2 is configured 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.
[0254] FIG. 7 is a diagram illustrating an example of a control resource set and a beam setting of a search space in a wireless communication system according to one embodiment of the present disclosure.
[0255] Referring to FIG. 7, the base station can indicate one of the TCI state lists included in the CORESET (700) configuration through MAC CE signaling (705). Thereafter, until another TCI state is indicated to the corresponding CORESET through another MAC CE signaling, the terminal considers that the same QCL information (beam #1, 705) is applied to all one or more search spaces (710, 715, 720) connected to the CORESET. The above-described PDCCH beam allocation method has the disadvantage that it is difficult to indicate a beam change faster than the MAC CE signaling delay, and also has the disadvantage of applying the same beam to each CORESET regardless of the search space characteristics, which makes flexible PDCCH beam operation difficult. The embodiments of the present invention below provide a more flexible PDCCH beam setting and operation method. In the following description of the embodiments of the present invention, several distinct examples are provided for the convenience of explanation, but these are not mutually exclusive and can be applied in combination with each other as appropriate depending on the situation.
[0256] A base station can set one or more TCI states for a specific control region to a terminal, and can activate one of the set TCI states through a MAC CE activation command. For example, if {TCI state#0, TCI state#1, TCI state#2} are set as TCI states in control region #1, the base station can transmit a command to the terminal to activate TCI state#0 for control region #1 through MAC CE. Based on the activation command for the TCI state received through MAC CE, the terminal can correctly receive DMRS of the corresponding control region based on QCL information in the activated TCI state.
[0257] For a control region (control region #0) with an index set to 0, if the terminal has not received a MAC CE activation command for the TCI state of control region #0, the terminal can assume that it has QCL with the SS / PBCH block identified during the initial access process or the non-contention-based random access process that is not triggered by a PDCCH command for the DMRS transmitted in control region #0.
[0258] For a control region (control region #X) whose index is set to a value other than 0, if the terminal has not set a TCI state for the control region #X, or has set one or more TCI states but has not received a MAC CE activation command to activate one of them, the terminal may assume that the DMRS transmitted in the control region #X is QCL with the SS / PBCH block identified during the initial access process.
[0259] [PDSCH / PUSCH: Frequency Resource Allocation Related]
[0260] Next, we describe the frequency domain resource assignment (FDRA) for the Physical Downlink Shared Channel (PDSCH) and Physical Uplink Shared Channel (PUSCH) in NR.
[0261] FIG. 8 is a diagram illustrating an example of frequency axis resource allocation of PDSCH or PUSCH in a wireless communication system according to one embodiment of the present disclosure.
[0262] FIG. 8 is a diagram illustrating three frequency axis resource allocation methods, FDRA type 0 (800), FDRA type 1 (805), and dynamic switch (810), which can be set via an upper layer in an NR wireless communication system.
[0263] Referring to FIG. 8, if the terminal is configured to use only FDRA type 0 through upper layer signaling (1300), some downlink control information (DCI) for scheduling PDSCH or PUSCH to the terminal is N RBG It contains a bitmap consisting of N bits. The conditions for this will be explained later. At this time, N RBG refers to the number of RBGs (resource block groups) determined according to the size of the bandwidth portion allocated by the bandwidth portion indicator and the upper layer parameter rbg-Size as shown in [Table 11] below, and data is transmitted to the RBG indicated as 1 by the bitmap.
[0264] [Table 11]
[0265]
[0266] The size of the frequency resource in the bandwidth part can be defined as the number of RBs included in the bandwidth part. More specifically, if the terminal is instructed to allocate FDRA type-0 resources, the length of the FDRA field of the DCI received by the terminal is the number of RBGs (N) in the bandwidth part. RBG ) and Here, the first RBG within the bandwidth section is It contains RBs of the dog, and the last RBG within the bandwidth part is On the other hand, Contains the RBs of the dog, otherwise, It contains RBs of the dog. The remaining RBGs contain P RBs, where P is the number of nominal RBGs determined according to [Table 11] above.
[0267] If the terminal is configured to use only FDRA type 1 through upper layer signaling (805), the DCI that allocates PDSCH or PUSCH to the terminal is It contains frequency domain resource allocation information (FDRA) consisting of bits. Here, is the number of RBs included in the bandwidth portion. Through this, the base station can set the starting VRB (820) and the length of frequency axis resources (825) allocated continuously therefrom.
[0268] If the terminal does not receive the upper layer signaling, vrb-ToPRB-Interleaver, the terminal can connect the resources allocated to the VRB to the PRB without interleaving. If the terminal receives the upper layer signaling, vrb-ToPRB-Interleaver, the upper layer signaling has a value of 2 or 4, and this value can be the unit of multiple RBs that perform interleaving. In other words, RB bundles of 2 or 4 units can be used for interleaving.
[0269] If the terminal Starting from the position and length The i-th BWP consisting of RBs is set, and the vrb-ToPRB-Interleaver is If set to , the terminal will set the i-th BWP It can be divided into RB bundles, and each RB bundle is It can be made up of RBs.
[0270] - In the i-th BWP, the first RB bundle is It can be made up of RBs.
[0271] - In the i-th BWP, the last RB bundle is if If the value is greater than 0 It can be made up of RBs of dogs, and if not It can be made up of RBs.
[0272] - In the i-th BWP, the remaining RB bundles are It can be made up of RBs.
[0273] At this time, VRB can be connected to PRB according to the following method.
[0274] - The last VRB bundle can be connected to the last PRB bundle.
[0275] - jth VRB bundle is can be connected to the th PRB bundle, can be expressed as in [Mathematical Formula 2] below.
[0276] [Equation 2]
[0277]
[0278] FIG. 9 is a diagram illustrating a VRB-PRB interleaving method of PDSCH in FDRA type-1 resource allocation according to an embodiment of the present disclosure. In FIG. 9, the first and last VRB bundles (900) in a BWP consisting of 10 RBs are represented as (910) consisting of 1 VRB. Therefore, the number of VRB bundles can be 6, and by the above [Mathematical Formula 2] can be calculated as follows. Therefore, since the jth VRB bundle can be connected to the f(j)th PRB bundle by the above [Mathematical Formula 2], the connection from the VRB bundle to the PRB bundle can be performed as in (920) through the result (930) calculated by the above [Mathematical Formula 2]. For example, VRB bundle 1 (940) can be connected to PRB bundle 3 (950).
[0279] Referring back to FIG. 8, if a terminal is configured to use both FDRA type-0 resource allocation and FDRA type-1 resource allocation through upper layer signaling (810), some DCIs that allocate PDSCH / PUSCH to the terminal include frequency-axis resource allocation information composed of bits of a larger value (835) among the payload (815) for configuring FDRA type-0 resource allocation and the payload (820, 825) for configuring FDRA type-1 resource allocation. The 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 FDRA type-0 resource allocation is used, and if the bit has a value of '1', it may indicate that FDRA type-1 resource allocation is used.
[0280] If the terminal has been set to the FDRA type-2 resource allocation method through upper layer signaling, the terminal can be instructed by the base station about the FDRA type-2 resource allocation method according to the following method.
[0281] The terminal can receive RB allocation information from the base station, which is a set of M interlace indices.
[0282] Interlace Index Silver common RB It can be composed of fields, and M can be defined as in [Table 12].
[0283] [Table 12]
[0284]
[0285] RB in interlace m and bandwidth part i and common RB The relationship with can be defined as follows:
[0286]
[0287] When the subcarrier spacing is 15 kHz (u=0), RB allocation information for an interlace set with m0 + l indices can be notified from the base station to the terminal. In addition, the resource allocation field can be configured with a resource indicator value (RIV). The resource indicator value When the starting interlace m0 and the number of consecutive interlaces It can be composed of , and its values are as follows:
[0288]
[0289] The resource indicator value is When this happens, the resource indicator value is composed of the start interlace index m0 and l values and can be configured as shown in [Table 13].
[0290] [Table 13]
[0291]
[0292] When the subcarrier spacing is 30 kHz (u=1), RB allocation information can be notified from the base station to the terminal in the form of a bitmap indicating the interlaces allocated to the terminal. The size of the bitmap is M, and each bit in the bitmap corresponds to an interlace. The order of the interlace bitmap can be mapped from the MSB to the LSB, from interlace index 0 to M-1.
[0293] Also, the least significant bit (LSB) of the FDRA field for 15 kHz and 30 kHz may mean a set of consecutive RBs of PUSCH scheduled with DCI format 0_1. The Y bit may be configured as a resource indication value (RIVRBset). In , the RIVRBset value is the starting RB set ( ) and the number of consecutive RB sets ( ) can be determined. The RIVRBset value can be defined as follows.
[0294]
[0295] It refers to the number of RB sets included in the bandwidth portion, and can be determined by the number of guard gaps (or bands) within the carrier set by upper signaling (or preset).
[0296] [PDSCH / PUSCH: Time Resource Allocation Related]
[0297] Below, a time domain resource allocation method for data channels in next-generation mobile communication systems (5G or NR systems) is described.
[0298] A base station can set up a table for time domain resource allocation information for a downlink data channel (PDSCH) and an uplink data channel (PUSCH) to a terminal via higher layer signaling (e.g., RRC signaling). A table with up to maxNrofDL-Allocations=16 entries can be set up for the PDSCH, and a table with up to maxNrofUL-Allocations=16 entries can be set up for the 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 about the position and length of the start symbol at which a PDSCH or PUSCH is scheduled within a slot, a mapping type of the PDSCH or PUSCH, etc. For example, information such as [Table 14] or [Table 15] below may be transmitted from the base station to the terminal.
[0299] [Table 14]
[0300]
[0301] [Table 15]
[0302]
[0303] 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) (e.g., indicated by the 'Time Domain Resource Allocation' field in the DCI). The terminal can obtain the time domain resource allocation information for the PDSCH or PUSCH based on the DCI received from the base station.
[0304] FIG. 10 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.
[0305] Referring to FIG. 10, 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 start position (1000) and length (1005) of an OFDM symbol within a slot that are dynamically indicated through DCI.
[0306] [SRS related]
[0307] Next, we describe an uplink channel estimation method using the Sounding Reference Signal (SRS) transmission of a terminal. The base station can configure at least one SRS configuration for each uplink BWP to convey configuration information for SRS transmission to the terminal, and can also configure at least one SRS resource set for each SRS configuration. For example, the base station and the terminal can exchange the following upper-level signaling information to convey information regarding the SRS resource set.
[0308] - srs-ResourceSetId: SRS resource set index
[0309] - srs-ResourceIdList: A set of SRS resource indices referenced in the SRS resource set.
[0310] - resourceType: This is the time axis transmission setting of the SRS resource referenced in the SRS resource set, and can be set to one of 'periodic', 'semi-persistent', and 'aperiodic'. If set to 'periodic' or 'semi-persistent', associated CSI-RS information can be provided depending on the usage of the SRS resource set. If set to 'aperiodic', an aperiodic SRS resource trigger list and slot offset information can be provided, and associated CSI-RS information can be provided depending on the usage of the SRS resource set.
[0311] - usage: This is a setting for the usage of the SRS resource referenced in the SRS resource set, and can be set to one of 'beamManagement', 'codebook', 'nonCodebook', and 'antennaSwitching'.
[0312] - alpha, p0, pathlossReferenceRS, srs-PowerControlAdjustmentStates: Provides parameter settings for adjusting the transmission power of the SRS resource referenced in the SRS resource set.
[0313] The terminal can understand that the SRS resource included in the set of SRS resource indices referenced in the SRS resource set follows the information set in the SRS resource set.
[0314] In addition, the base station and the terminal can transmit and receive upper layer signaling information to convey individual configuration information for the SRS resource. For example, the individual configuration information for the SRS resource can include time-frequency axis mapping information within the slot of the SRS resource, which can include information about frequency hopping within the slot or between slots of the SRS resource. In addition, the individual configuration information for the SRS resource can include the time axis transmission configuration of the SRS resource, which can be set to one of 'periodic', 'semi-persistent', and 'aperiodic'. This can be restricted to have the same time axis transmission configuration as the SRS resource set including the SRS resource. If the time axis transmission configuration of the SRS resource is set to 'periodic' or 'semi-persistent', the SRS resource transmission period and slot offset (e.g., periodicityAndOffset) can additionally be included in the time axis transmission configuration.
[0315] The base station can activate, deactivate, or trigger SRS transmission to the UE through higher layer signaling, including RRC signaling or MAC CE signaling, or L1 signaling (e.g., DCI). For example, the base station can activate or deactivate periodic SRS transmission to the UE through higher layer signaling. The base station can instruct the UE to activate an SRS resource set with resourceType set to periodic through higher layer signaling, and the UE can transmit the SRS resource referenced in the activated SRS resource set. The time-frequency domain resource mapping within the slot of the transmitted SRS resource follows the resource mapping information set in the SRS resource, and the slot mapping, including the transmission period and slot offset, follows the periodicityAndOffset set in the SRS resource. In addition, the spatial domain transmission filter applied to the transmitted SRS resource can refer to the spatial relation information set in the SRS resource, or the associated CSI-RS information set in the SRS resource set that includes the SRS resource. A terminal can transmit SRS resources within an activated uplink BWP for periodic SRS resources activated through upper layer signaling.
[0316] For example, a base station can activate or deactivate semi-persistent SRS transmission to a terminal through upper layer signaling. The base station can instruct the terminal to activate an SRS resource set through MAC CE signaling, and the terminal can transmit an SRS resource referenced in the activated SRS resource set. The SRS resource set activated through MAC CE signaling can be limited to an SRS resource set with resourceType set to semi-persistent. The time-frequency domain resource mapping within the slot of the transmitted SRS resource follows the resource mapping information configured in the SRS resource, and the slot mapping including the transmission period and slot offset follows the periodicityAndOffset configured in the SRS resource. In addition, the spatial domain transmission filter applied to the transmitted SRS resource can refer to the spatial relation information configured in the SRS resource, or the associated CSI-RS information configured in the SRS resource set that includes the SRS resource. If spatial relation info is configured in an SRS resource, the spatial domain transmission filter can be determined by referring to the configuration information for spatial relation info transmitted through MAC CE signaling that activates semi-persistent SRS transmission without following it. The terminal can transmit SRS resources within the activated uplink BWP for the semi-persistent SRS resource activated through upper layer signaling.
[0317] For example, a base station can trigger aperiodic SRS transmission to a terminal via DCI. The base station can indicate one of the aperiodic SRS resource triggers (aperiodicSRS-ResourceTrigger) via the SRS request field of the DCI. The terminal can understand that an SRS resource set including the aperiodic SRS resource trigger indicated via DCI in the aperiodic SRS resource trigger list among the configuration information of the SRS resource set has been triggered. The terminal can transmit an SRS resource referenced in the triggered SRS resource set. The time-frequency domain resource mapping within the slot of the transmitted SRS resource follows the resource mapping information configured in the SRS resource. In addition, the slot mapping of the transmitted SRS resource can be determined through a slot offset between a PDCCH including the DCI and the SRS resource, which can refer to value(s) included in a slot offset set configured in the SRS resource set. Specifically, the slot offset between the PDCCH including DCI and the SRS resource can be applied by applying the value indicated in the time domain resource assignment field of the DCI among the offset value(s) included in the slot offset set configured in the SRS resource set. In addition, the spatial domain transmission filter applied to the transmitted SRS resource can refer to the spatial relation information configured in the SRS resource, or can refer to the associated CSI-RS information configured in the SRS resource set including the SRS resource. The UE can transmit the SRS resource within the activated uplink BWP for the aperiodic SRS resource triggered through the DCI.
[0318] When a base station triggers aperiodic SRS transmission to a terminal through DCI, a minimum time interval may be required between a PDCCH including the DCI that triggers aperiodic SRS transmission and the SRS to be transmitted, so that the terminal can transmit the SRS by applying configuration information for the SRS resource. The time interval for SRS transmission of the terminal can be defined as the number of symbols between the last symbol of the PDCCH including the DCI that triggers aperiodic SRS transmission and the first symbol to which the first SRS resource to be transmitted among the SRS resource(s) is mapped. The minimum time interval can be determined with reference to the PUSCH preparation procedure time required for the terminal to prepare for PUSCH transmission. In addition, the minimum time interval can have different values depending on the usage of the SRS resource set including the SRS resource to be transmitted. For example, the minimum time interval can be determined as N2 symbols, which are defined by considering the terminal processing ability according to the capability of the terminal with reference to the PUSCH preparation procedure time of the terminal. In addition, considering the usage of the SRS resource set including the SRS resource being transmitted, if the usage of the SRS resource set is set to 'codebook' or 'antennaSwitching', the minimum time interval can be set to N2 symbols, and if the usage of the SRS resource set is set to 'nonCodebook' or 'beamManagement', the minimum time interval can be set to N2+14 symbols.The terminal may transmit an aperiodic SRS if the time interval for aperiodic SRS transmission is greater than or equal to the minimum time interval, and may ignore the DCI that triggers the aperiodic SRS if the time interval for aperiodic SRS transmission is less than the minimum time interval.
[0319] [Table 16]
[0320]
[0321]
[0322] The spatialRelationInfo setting information in Table 16 above refers to a single reference signal and applies the beam information of the reference signal to the beam used for the corresponding SRS transmission. For example, the spatialRelationInfo setting may include information as shown in Table 17 below.
[0323] [Table 17]
[0324]
[0325] Referring to the above spatialRelationInfo setting, the index of the reference signal to be referenced in order to use the beam information of a specific reference signal, i.e., the SS / PBCH block index, CSI-RS index, or SRS index can be set. The upper signaling referenceSignal is setting information indicating which beam information of which reference signal is to be referenced for the corresponding SRS transmission, ssb-Index means the index of the SS / PBCH block, csi-RS-Index means the index of the CSI-RS, and srs means the index of the SRS, respectively. If the value of the upper signaling referenceSignal is set to 'ssb-Index', the terminal can apply the reception beam used when receiving the SS / PBCH block corresponding to ssb-Index as the transmission beam of the corresponding SRS transmission. If the value of the upper signaling referenceSignal is set to 'csi-RS-Index', the terminal can apply the reception beam used when receiving the CSI-RS corresponding to csi-RS-Index as the transmission beam of the corresponding SRS transmission. If the value of the upper signaling referenceSignal is set to 'srs', the terminal can apply the transmission beam used when transmitting the SRS corresponding to srs as the transmission beam for the corresponding SRS transmission.
[0326] The SRS request field (e.g., 2 bits) indicated in DCI formats 0_1, 0_2, 1_1, 1_2, and 2_3 may indicate some of the resources set in the Triggered aperiodic SRS resource(s). For example, if the indication value of the SRS request in the DCI information transmitted by the base station is 00, the terminal may determine that the aperiodic SRS resource set is not triggered. In addition, if the indication value of the SRS request in the DCI information transmitted by the base station is 01, the terminal may determine that the SRS resource set(s) associated with the aperiodic SRS resource set trigger is set to 1, or the aperiodicSRS-ResourceTriggeredList Set is set to 1. In addition, when the indication value of the SRS request in the DCI information transmitted by the base station is 10, the terminal can determine that the SRS resource set(s) associated with the aperiodic SRS resource set trigger is set to 2 or the aperiodicSRS-ResourceTriggeredList Set is set to 2. In addition, when the indication value of the SRS request in the DCI information transmitted by the base station is 11, the terminal can determine that the SRS resource set(s) associated with the aperiodic SRS resource set trigger is set to 3 or the aperiodicSRS-ResourceTriggeredList Set is set to 3.
[0327] [SRS antenna switching related]
[0328] Below, SRS for antenna switching is described.
[0329] SRS can be used to acquire DL (downlink) CSI (Channel State Information) information (e.g., DL CSI acquisition). As a specific example, in a single-cell or multi-cell (e.g., carrier aggregation (CA)) situation based on TDD (Time Division Duplex), after a BS (Base Station) schedules SRS transmission to a UE (User Equipment), the BS can measure the SRS transmitted from the UE. In this case, assuming DL / UL reciprocity, the BS can schedule DL signals / channels to the UE based on the measurement by SRS. In this case, with respect to DL CSI acquisition based on SRS, the usage of the SRS resource referenced in the SRS resource set can be set to antenna switching.
[0330] For example, according to the standard (e.g., 3gpp TS38.214), the usage of SRS can be set to the base station and / or terminal using a higher layer parameter (e.g., usage of RRC parameter SRS-ResourceSet). Here, the usage of SRS can be set to beam management usage, codebook transmission usage, non-codebook transmission usage, antenna switching usage, etc.
[0331] Below, we will specifically examine the case where SRS transmission (i.e., transmission of SRS resources or a set of SRS resources) is set for antenna switching purposes among the above purposes.
[0332] For example, for a terminal with partial reciprocity, SRS transmission based on antenna switching (i.e., transmit antenna switching) may be supported to acquire DLCSI through SRS transmission in situations such as TDD. When antenna switching is applied, an interval between SRS resources (and / or resources between SRS resources and PUSCH / PUCCH) of approximately 15 μs may be required for antenna switching of the terminal. Taking this into account, a (minimum) guard period as shown in Table 18 below may be defined. Table 20 shows the minimum guard period according to numerology.
[0333] [Table 18]
[0334]
[0335] In Table 18, μ represents numerology, represents the subcarrier spacing, and Y represents the number of symbols in the guard interval, i.e., the length of the guard interval. Referring to Table 20, the guard interval can be set based on the parameter μ that determines the numerology. In the guard interval, the terminal is set not to transmit any other signal, and the guard interval can be set to be used entirely for antenna switching. For example, the guard interval can be set considering SRS resources transmitted in the same slot. In particular, when the terminal is set and / or instructed to transmit an aperiodic SRS configured with intra-slot antenna switching, the terminal transmits the SRS using a different transmission antenna for each designated SRS resource, and the above-described guard interval can be set between each resource.
[0336] In addition, as described above, when the terminal is configured with SRS resources and / or SRS resource sets for antenna switching purposes through upper layer signaling, the terminal may be configured to perform SRS transmission based on UE capability related to antenna switching. The terminal may report capability information indicating whether it supports SRS antenna switching to the base station. The capability information may include a parameter indicating an SRS transmission port switching pattern supported by the terminal. Here, the capability of the terminal related to antenna switching reported by the parameter may be '1T2R', '2T4R', '1T4R', '1T4R / 2T4R', '1T1R', '2T2R', '4T4R', etc. Here, 'xTyR' may mean a terminal capability indicating that SRS transmission is possible on x antenna ports over y receiving antennas.
[0337] For example, for a terminal supporting 1T2R, up to two SRS resource sets can be configured with different values for the resourceType of the upper layer parameter SRS-ResourceSet. Here, each SRS resource set can have two SRS resources transmitted in different symbols, and each SRS resource in a given SRS resource set can configure a single SRS port. In addition, the SRS port for the second SRS resource in an SRS resource set can be configured to be associated with a different terminal antenna port than the SRS port for the first SRS resource in the same SRS resource set.
[0338] For another example, for a terminal supporting 2T4R, up to two SRS resource sets may be configured with different values for the resourceType of the upper layer parameter SRS-ResourceSet. Here, each SRS resource set may have two SRS resources transmitted in different symbols, and each SRS resource in a given SRS resource set may configure two SRS ports. In addition, the SRS port pair for the second SRS resource in an SRS resource set may be configured to be associated with a different terminal antenna port than the SRS port pair for the first SRS resource in the same SRS resource set.
[0339] For another example, for a terminal supporting 1T4R, SRS resource sets may be configured in different ways depending on whether SRS transmission is configured to be periodic, semi-persistent, and / or aperiodic. First, if SRS transmission is configured to be periodic or semi-persistent, 0 or 1 SRS resource set configured based on the resourceType of the upper layer parameter SRS-ResourceSet may be configured with 4 SRS resources transmitted in different symbols. Here, each SRS resource in the given SRS resource set may configure a single SRS port. In addition, the SRS port for each SRS resource may be configured to be associated with different terminal antenna ports. In contrast, when SRS transmission is configured aperiodic, zero or two SRS resource sets configured based on the resourceType of the upper layer parameter SRS-ResourceSet can be configured with a total of four SRS resources transmitted in different symbols of two different slots. Here, the SRS port for each SRS resource in the given two SRS resource sets can be configured to be associated with different terminal antenna ports. Each SRS resource set can be configured with two SRS resources, or one SRS resource set can be configured with one SRS resource and the other SRS resource sets can be configured with three SRS resources.
[0340] For another example, for a terminal supporting 1T1R, 2T2R, or 4T4R, up to two SRS resource sets, each consisting of one SRS resource, may be configured for SRS transmission. The number of SRS ports of each SRS resource may be set to 1, 2, or 4.
[0341] If the indicated terminal capability is 1T4R / 2T4R, the terminal may expect the same number of SRS ports (e.g., 1 or 2) to be configured for all SRS resources in the SRS resource set(s). In addition, if the indicated terminal capability is 1T2R, 2T4R, 1T4R, or 1T4R / 2T4R, the terminal may not expect one or more SRS resource sets configured for antenna switching purposes in the same slot to be configured or triggered. In addition, even if the indicated terminal capability is 1T1R, 2T2R, or 4T4R, the terminal may not expect one or more SRS resource sets configured for antenna switching purposes in the same slot to be configured or triggered.
[0342] The various embodiments described above have been described without explicitly configuring panels for uplink and downlink transmission for the terminal. That is, the terminal antenna port for SRS antenna switching can be configured without explicit consideration of the terminal panel, and the base station and the terminal can operate accordingly. If at least two or more panels are explicitly configured, SRS resource set(s) for antenna switching purposes can be configured for each panel. In this case, UE capability may exist depending on whether the terminal can simultaneously transmit the corresponding SRS resource set(s) configured for each panel, whether they can be configured in the same slot, or whether they can be transmitted in the same slot.
[0343] [Regarding terminal capability reporting]
[0344] In LTE and NR, a terminal, while connected to a serving base station, can perform a procedure to report its supported capabilities to the base station. In the description below, this is referred to as a UE capability report.
[0345] A base station can transmit a UE capability inquiry message requesting a capability report to a connected terminal. The message can include a UE capability request for each RAT (radio access technology) type of the base station. The RAT type-specific request can include information on a combination of supported frequency bands, etc. In addition, in the case of the UE capability inquiry message, UE capabilities for multiple RAT types can be requested through a single RRC message container transmitted by the base station, or the base station can include multiple UE capability inquiry messages including UE capability requests for each RAT type and transmit them to the terminal. That is, the UE capability inquiry can be repeated multiple times in one message, and the terminal can compose a corresponding UE capability information message and report it multiple times. In the next-generation mobile communication system, a UE capability request can be made for MR-DC (Multi-RAT dual connectivity), including NR, LTE, and EN-DC (E-UTRA - NR dual connectivity). Additionally, the terminal capability inquiry message is typically transmitted initially after the terminal is connected to the base station, but the base station may request it under any conditions when necessary.
[0346] In the above step, the terminal that receives the UE capability report request from the base station configures the terminal capability based on the RAT type and band information requested from the base station. Below is a summary of how the terminal configures the UE capability in the NR system.
[0347] 1. If the UE receives a list of LTE and / or NR bands through a UE capability request from the base station, the UE configures a band combination (BC) for EN-DC and NR stand-alone (SA). That is, it configures a candidate list of BCs for EN-DC and NR SA based on the bands requested to the base station via FreqBandList. Furthermore, the bands are prioritized in the order listed in FreqBandList.
[0348] 2. If the base station requests UE capability reporting by setting the "eutra-nr-only" flag or the "eutra" flag, the UE completely removes NR SA BCs from the list of configured BC candidates. This operation can only occur when the LTE base station (eNB) requests the "eutra" capability.
[0349] 3. The terminal then removes fallback BCs from the BC candidate list constructed in the above step. Here, a fallback BC is a BC obtained by removing at least one band corresponding to an SCell from a random BC. This step can be omitted because the BC before removing the band corresponding to at least one SCell can already cover the fallback BC. This step also applies to MR-DC, i.e., to LTE bands. The BCs remaining after this step are the final "candidate BC list."
[0350] 4. The terminal selects BCs to report by selecting BCs that match the requested RAT type from the final "candidate BC list" above. In this step, the terminal constructs the supportedBandCombinationList in a set order. That is, the terminal constructs BCs and UE capabilities to report in the order of the preset rat-Type (nr -> eutra-nr -> eutra). In addition, it constructs a featureSetCombination for the constructed supportedBandCombinationList, and constructs a list of "candidate feature set combinations" from the candidate BC list after removing the list for the fallback BC (which contains capabilities of the same or lower level). The "candidate feature set combinations" above include feature set combinations for both NR and EUTRA-NR BCs, and can be obtained from the feature set combinations in the UE-NR-Capabilities and UE-MRDC-Capabilities containers.
[0351] 5. Also, if the requested rat Type is eutra-nr and has an effect, featureSetCombinations are included in both containers: UE-MRDC-Capabilities and UE-NR-Capabilities. However, the NR feature set is included only in UE-NR-Capabilities.
[0352] After terminal capabilities are configured, the terminal transmits a terminal capability information message containing the terminal capabilities to the base station. Based on the terminal capabilities received from the terminal, the base station then performs appropriate scheduling and transmission / reception management for the terminal.
[0353] 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 and / or XDD (and / or SBFD, full duplex) 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).
[0354] In the present disclosure, when determining whether cooperative communication is applied, the terminal may use various methods, such as having the PDCCH(s) that allocate the PDSCH to which cooperative communication is applied have a specific format, or including a specific indicator that indicates whether cooperative communication is applied, or scrambled with a specific RNTI by the PDCCH(s) that allocate the PDSCH to which cooperative communication is applied, or assuming cooperative communication is applied in a specific section indicated by a higher layer. For the convenience of the following description, the case where the terminal receives the PDSCH to which cooperative communication is applied based on conditions similar to the above will be referred to as the NC-JT case.
[0355] 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.
[0356] 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.
[0357] For convenience in the following description of the present disclosure, cells, transmission points, panels, beams, and / or transmission directions, which can be distinguished through upper layer / L1 parameters such as TCI state or spatial relation information, or indicators such as cell ID, TRP ID, and panel ID, may be uniformly described as TRP (transmission reception point), beam, or TCI state. Therefore, in actual application, TRP, beam, or TCI state can be appropriately replaced with one of the above terms.
[0358] In the present disclosure, when determining whether cooperative communication is applied, the terminal may use various methods, such as having the PDCCH(s) that allocate the PDSCH to which cooperative communication is applied have a specific format, or including a specific indicator that indicates whether cooperative communication is applied, or scrambled with a specific RNTI by the PDCCH(s) that allocate the PDSCH to which cooperative communication is applied, or assuming cooperative communication is applied in a specific section indicated by a higher layer. For the convenience of the following description, the case where the terminal receives the PDSCH to which cooperative communication is applied based on conditions similar to the above will be referred to as the NC-JT case.
[0359] 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 embodiments of the present disclosure are described below using a 5G system as an example, 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 LTE or LTE-A mobile communication and mobile communication technologies developed after 5G. Therefore, 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 are applicable to FDD and TDD systems.
[0360] 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.
[0361] 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.
[0362] - MIB (Master Information Block)
[0363] - SIB (System Information Block) or SIB
[0364] - RRC (Radio Resource Control)
[0365] - MAC (Medium Access Control) CE (Control Element)
[0366] 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.
[0367] - PDCCH (Physical Downlink Control Channel)
[0368] - DCI (Downlink Control Information)
[0369] - UE-specific DCI
[0370] - Group common DCI
[0371] - Common DCI
[0372] - Scheduling DCI (e.g. DCI used for scheduling downlink or uplink data)
[0373] - Non-scheduled DCI (e.g. DCI not intended for scheduling downlink or uplink data)
[0374] - PUCCH (Physical Uplink Control Channel)
[0375] - UCI (Uplink Control Information)
[0376] 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.
[0377] The term “slot” used in the present disclosure below is a general term that may refer to a specific time unit corresponding to a TTI (Transmit Time Interval), and may specifically mean a slot used in a 5G NR system, or a slot or subframe used in a 4G LTE system.
[0378] 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.
[0379] <Embodiment 1: MC-DCI Scheduling Method>
[0380] As one embodiment of the present disclosure, a scheduling method using MC-DCI (Multi-cell scheduling DCI) is described. This embodiment can be operated in combination with other embodiments.
[0381] In the present disclosure, one DCI may be a single-DCI or may be in one DCI format, and multiple DCIs may be multi-DCI or may be in multiple DCI formats. In the present disclosure, one DCI may be one PDCCH and / or may be transmitted and received through one PDCCH, and multiple DCIs may be multiple PDCCHs and / or may be transmitted and received through multiple PDCCHs.
[0382] Typically, a terminal receives one DCI, which may include scheduling information for one cell. For example, DCI format 0_0 / 0_1 / 0_2 may schedule one PUSCH for one uplink cell. Additionally, DCI format 1_0 / 1_1 / 1_2 may schedule one PDSCH for one downlink cell. Here, the scheduled cell may be indicated by the CIF (carrier indication field) of the DCI format.
[0383] However, according to this method, when PDSCH or PUSCH is scheduled in each of multiple cells, multiple DCIs must be transmitted and received. Therefore, a lot of DCI overhead may occur. To reduce the DCI overhead, one DCI may schedule PDSCH or PUSCH in each of multiple cells. This may be conveniently referred to as MC-DCI. In the present disclosure, MC-DCI may be one DCI that schedules PDSCH and / or PUSCH in each of multiple cells. In this case, the DCI format of the MC-DCI may be DCI format 1_X or 1_3 for PDSCH scheduling, and may be DCI format 0_X or 0_3 for PUSCH scheduling.
[0384] Within a specific cell, a terminal can report the number of candidates for a cell set that can be scheduled via MC-DCI to the base station through the terminal capability (UECapability). At this time, a cell set means a set that includes multiple cells. For example, cell set 1 may include cell 1, cell 2, cell 3, and cell 4, and cell set 2 may include cell 5, cell 6, cell 7, and cell 8. The maximum number of cells that can be included in a cell set is 4, and the cells included in each cell set may not overlap each other. At this time, the number of candidates for a cell set that a terminal can report as the terminal capability may be 1 or 2 or more.
[0385] If the terminal reports the number of candidates for a set of cells that can be scheduled as 1 through MC-DCI received within a specific cell, the terminal can expect that there is no cell set indicator field within the MC-DCI, and the terminal can expect scheduling for cells within one cell set when receiving MC-DCI from the base station.
[0386] If a terminal reports the number of candidates for a cell set that can be scheduled as two or more through MC-DCI received within a specific cell, the terminal can expect that a cell set indicator field exists in the MC-DCI, and the terminal can receive an index of one cell set from the base station through the field. The terminal can receive scheduling information for one or more cells within one cell set among multiple cell sets through the MC-DCI. The following description assumes that the number of candidates for the cell set reported by the terminal is one, and the same can be applied to a case where the number of candidates for the cell set is two or more.
[0387] The cells that can be scheduled in MC-DCI can be configured by a higher layer. For example, it is assumed that MC-DCI can schedule cell 0, cell 1, cell 2, and cell 3 (simultaneously). When the terminal receives the MC-DCI, the terminal can check the scheduling information for cell 0, cell 1, cell 2, and cell 3. That is, the terminal can obtain the scheduling information for cell 0, cell 1, cell 2, and cell 3 from the MC-DCI. For example, it can be configured from a higher layer that MC-DCI can schedule cell 0, cell 1, cell 2, and cell 3. Here, the scheduling information can include time domain resource allocation (TDRA) information and / or frequency domain resource allocation (FDRA) information for transmitting and receiving data channels (PDSCH for downlink, PUSCH for uplink) in each cell. Accordingly, the terminal can obtain scheduling information of each cell through the MC-DCI and transmit and receive data channels to and from each cell.
[0388] A base station may not be able to schedule all cells configured for a terminal in certain circumstances. Scheduling may not be possible for at least some of the multiple cells configured by the base station for a terminal. For example, a base station may configure four cells (e.g., Cell 0, Cell 1, Cell 2, and Cell 3) within a list of cells configured via upper layer signaling that can be scheduled via MC-DCI to a terminal, but some of these cells may not be schedulable, for example, because they are scheduled for other terminals, have poor channel conditions, or for other various reasons. In this case, the base station must be able to indicate to the terminal which of the cells configured to be schedulable via MC-DCI are actually scheduled via MC-DCI. In other words, the base station must be able to indicate to the terminal which of the multiple cells configured to be schedulable via MC-DCI are actually scheduled via MC-DCI.
[0389] It may be directed based on one of the following two methods, or a combination of at least one of the following two methods.
[0390] In a first method, the terminal can obtain information indicating co-scheduled cells among the preset cells (e.g., cell 0, cell 1, cell 2, cell 3) from the MC-DCI. That is, among a plurality of cells set to be scheduled in the MC-DCI, one or more cells that are (actually) co-scheduled through the MC-DCI can be identified based on the MC-DCI. More specifically, the base station can set a table including cells that are co-scheduled for the terminal. For example, rows of this table can have unique indexes. The index of each row (and / or each row) can include the indexes of cells that are co-scheduled. For example, {cell 0, cell 1} can be set for row 0, {cell 2, cell 3} for row 1, and {cell 0, cell 1, cell 2, cell 3} for row 2. An example of a table set for a terminal can be found in [Table 19].
[0391] [Table 19]
[0392]
[0393] The terminal can obtain a value indicating the index of the row through MC-DCI. Accordingly, the terminal can determine the cell to be scheduled based on the value. For example, the MC-DCI can include information about the index of the row, and the terminal can identify the cell to be scheduled based on the index of the row obtained from the MC-DCI and the table. For example, if row 0 is indicated from the MC-DCI, the terminal can identify that cell 0 and cell 1 are scheduled cells. For example, if row 1 is indicated from the MC-DCI, the terminal can identify that cell 2 and cell 3 are scheduled cells. For example, if row 2 is indicated from the MC-DCI, the terminal can identify that cell 0, cell 1, cell 2, and cell 3 are scheduled cells. Meanwhile, in the present disclosure, the base station explains information including cells to be scheduled simultaneously to the terminal in the form of a table, but the embodiments of the present disclosure are not limited thereto. That is, various methods can be used to indicate cells that are scheduled simultaneously. For example, information about cells scheduled simultaneously can be organized into a list, with each piece of information assigned an identifier to identify the cells scheduled simultaneously. Accordingly, the term "table" described below can be replaced with terms such as "information about cells scheduled simultaneously."
[0394] In the present disclosure, a table is set for a mapping relationship between a scheduled cell (or an index of a scheduled cell) and an index indicated from DCI, and a scheduled cell can be identified based on the table and the index indicated from DCI.
[0395] Although the present disclosure has described an embodiment in which cells to be scheduled simultaneously are identified based on the index of a row of a table, the present disclosure is not limited thereto, and for example, cells to be scheduled may also be identified based on the index of a column of a table, in which case the rows in the above-described embodiment may be replaced with columns.
[0396] In the present disclosure, if the number of candidates for a cell set that can be scheduled through MC-DCI received by a terminal within a specific cell is two or more, the terminal can set a table as described above for each cell set, and the terminal can determine which table for which cell set to use through a cell set indicator field in the MC-DCI.
[0397] In a second method, the terminal can determine whether there is scheduling information for one or more cells based on the FDRA field of MC-DCI.
[0398] If the terminal reports the number of candidates for a set of cells that can be scheduled within a specific cell as 1 via MC-DCI, the terminal can expect that there will be as many FDRA fields in the MC-DCI as the number of cells included in the set of cells. In this case, if the terminal has not received a higher layer signaling configuration such as the table mentioned in the first method above, the terminal can determine whether scheduling information for each cell exists based on one or more FDRA fields in the MC-DCI.
[0399] If the terminal reports the number of candidate cell sets that can be scheduled via MC-DCI within a specific cell as two or more through the terminal capability report, the terminal can expect the presence of as many FDRA fields as the maximum number of cells included in each of the two or more cell sets. For example, if the terminal reports the number of candidate cell sets as two, and the first cell set includes three cells and the second cell set includes four cells, the terminal can expect the presence of four FDRA fields in the MC-DCI, which is the maximum number of cells included in each of the first and second cell sets.
[0400] - If the terminal has not received the upper layer signaling configuration such as the table mentioned in the first method for all cell sets, the terminal can determine whether scheduling information for each cell exists based on the FDRA fields in the MC-DCI, and if the number of cells in the cell set indicated to the terminal through the cell set indicator field is less than the number of FDRA fields, the terminal can consider the FDRA field corresponding to the number of cells in the indicated cell set as an ascending index of the FDRA field, and can ignore the FDRA fields corresponding to indices greater than the number of cells.
[0401] - If the terminal has received the upper layer signaling configuration, such as the table mentioned in the first method, for a specific cell set, but has not received it for the remaining cell sets, the terminal can expect that a scheduling cell indicator field, which can indicate the index of a specific row in the table configured with the upper layer signaling, such as the first method, is included in the MC-DCI, and the terminal can use a method of interpreting the scheduling cell indicator field or the FDRA field when determining whether there is scheduling information for one or more cells regarding which cell set is indicated through the cell set indicator field in the MC-DCI. In this case, the scheduling cell indicator field that can be included in the MC-DCI may be a separate field distinct from the CIF (carrier indication field), or the CIF may replace the scheduling cell indicator field in the MC-DCI.
[0402] If the terminal is indicated to have received a set of cells that have received upper layer signaling such as the table above through the cell set indicator field in the MC-DCI, the terminal can be indicated to have scheduling information for one or more cells through the scheduling cell indicator field. If the terminal is indicated to have received a set of cells that have not received upper layer signaling such as the table above through the cell set indicator field in the MC-DCI, the terminal can be indicated to have scheduling information for one or more cells through the FDRA field.
[0403] FIG. 11 is a diagram illustrating an example in which MC-DCI according to one embodiment of the present disclosure includes multiple FDRA fields.
[0404] Referring to FIG. 11, MC-DCI (1100) may include multiple FDRA fields. And each FDRA field may have a corresponding cell. That is, when cells that can be scheduled simultaneously in MC-DCI (1100) are set as cell 0 (1120), cell 1 (1121), cell 2 (1122), and cell 3 (1123), the MC-DCI (1100) may include an FDRA field (1110) for cell 0, an FDRA field (1111) for cell 1, an FDRA field (1112) for cell 2, and an FDRA field (1113) for cell 3. Accordingly, the terminal may determine whether each cell is scheduled based on the value of the FDRA field. Cells scheduled based on the value of the above FDRA field can be called actually co-scheduled cells.
[0405] FIG. 12 is a diagram illustrating an example in which MC-DCI according to one embodiment of the present disclosure includes at least one of a cell set indicator field, a scheduling cell indicator field, and a plurality of FDRA fields.
[0406] Referring to FIG. 12, MC-DCI (1200) may include at least one of a cell set indicator field (1201), a scheduling cell indicator field (1202), and a plurality of FDRA fields (1205, 1206, 1207, 1208). As described above, if a terminal reports to a base station the number of candidates for a cell set that can be scheduled within a specific cell through MC-DCI as two or more, the terminal may expect the presence of the cell set indicator field (1201) in the MC-DCI. On the other hand, if a candidate for a cell set that can be scheduled is reported to the base station as one through MC-DCI, the cell set indicator field (1201) may not be present in the MC-DCI. FIG. 12 illustrates a case where a terminal reports the number of candidates for a cell set as two. In this embodiment, for example, cell set 0 (1210) may include three cells, namely cell 0 (1211), cell 1 (1212), and cell 2 (1213), and cell set 1 (1220) may include cell 3 (1221), cell 4 (1222), cell 5 (1223), and cell 6 (1224). Accordingly, the terminal may expect that the MC-DCI contains as many FDRA fields as the maximum number of cells included in each of cell set 0 (1210) and cell set 1 (1220), namely, four.
[0407] In addition, in Fig. 12, it is assumed that the terminal has not set up upper layer signaling, such as the table above, for cell set 0 (1210). Therefore, as in the second method, the presence or absence of scheduling information for cells in cell set 0 (1210) can be indicated by the FDRA fields (1205, 1206, 1207, 1208) in MC-DCI. At this time, since there are three cells in cell set 0 (1210), the terminal can be indicated with scheduling information for cell 0 (1211), cell 1 (1212), and cell 2 (1213) through the first, second, and third FDRA fields (1208, 1207, 1206).
[0408] In addition, in Fig. 12, it can be assumed that the terminal has received the upper layer signaling as in the table above for cell set 1 (1220). Therefore, as in the first method, the presence or absence of scheduling information for cells in cell set 1 (1220) can be indicated by the scheduling cell indicator field (1202) in MC-DCI. For example, the terminal can be indicated to a specific row among all rows in the table set by the upper layer signaling through the scheduling cell indicator field (1202) in MC-DCI, and the row can indicate scheduling information for, for example, cell 3 (1221) and cell 5 (1223) in cell set 1 (1220).
[0409] The FDRA field can be divided into valid and invalid values. A valid value may be one in which a frequency domain assignment corresponding to the value in the FDRA field exists. Conversely, an invalid value may be one in which a frequency domain assignment corresponding to the value in the FDRA field does not exist.
[0410] For example, we describe valid and invalid values based on FDRA type-0. FDRA type-0 is a method of indicating RBs (or RBGs) to be scheduled based on a bitmap. Here, each bit may have corresponding RBs (or RBGs). If the bit is '1', the corresponding RBs (or RBGs) may be scheduled, and if the bit is '0', the corresponding RBs (or RBGs) may not be scheduled. Therefore, if at least one bit is '1', it may be determined as a valid value, and if all bits are '0', it may be determined as an invalid value.
[0411] For example, valid and invalid values are explained based on FDRA type-1. FDRA type-1 is a method of indicating RBs to be scheduled based on RIV (resource indication value). Here, FDRA type-1 can schedule consecutive RBs in the frequency domain. FDRA type-1 can indicate the index of the starting RB and the number of consecutive RBs. The RIV value can be one of 0, 1,…, N*(N+1) / 2 -1. Here, N is the number of RBs included in the frequency domain. Therefore, if the RIV value is one of 0, 1,…, N*(N+1) / 2 -1, it can be determined as a valid value, and a value greater than or equal to N*(N+1) / 2 can be determined as an invalid value.
[0412] Some of the cells scheduled by MC-DCI may be in licensed bands, while others may be in unlicensed bands (or shared spectrum). For example, for cells in unlicensed bands, FDRA type-2 may need to be used for uplink scheduling. Specific information on FDRA type-2 or an example in which FDRA type-2 is used will be described later.
[0413] The present disclosure discloses a method for determining a cell to be scheduled from a single DCI when a terminal supports multiple cell scheduling with a single DCI.
[0414] A terminal can receive multiple frequency domain resource allocation (FDRA) fields in a single DCI and determine a cell corresponding to each FDRA field. The terminal can determine whether the cell is scheduled based on the FDRA type of the cell and the value of the FDRA field. The terminal can identify whether a cell is scheduled and / or whether a scheduled cell and / or an unscheduled cell based on one or more of the FDRA type or the FDRA field. For example, the interpretation method of the FDRA field may vary depending on the subcarrier spacing of the corresponding cell.
[0415] When a terminal is set to FDRA type-2 in a cell, whether the cell is scheduled or not can be determined based on at least one or a combination of the following.
[0416] If the above cell has a 15kHz subcarrier spacing (if the subcarrier spacing set for a cell is 15kHz), the terminal can determine that the cell is not scheduled if the value of the FDRA field is as follows.
[0417] In the first case, all bits in the FDRA field are “1”.
[0418] The second case is when all of the first 6 bits of the FDRA field are “1”. That is, when all 6 MSBs (most significant bits) of the bits of the FDRA field are “1”.
[0419] The third case is when all of the Y bits in the FDRA field are “1”. That is, when all of the Y LSBs (least significant bits) of the bits in the FDRA field are “1”.
[0420] If the above cell has a 30kHz subcarrier spacing (if the subcarrier spacing set for a cell is 30kHz), the terminal can determine that the cell is not scheduled if the value of the FDRA field is as follows.
[0421] In the first case, the first 5 bits of the FDRA field are all “0” and the following Y bits are all “1”. That is, the 5 MSBs of the FDRA field are all “0” and the Y LSBs are all “1”.
[0422] In the second case, all bits in the FDRA field are “0”.
[0423] The third case is when the first 5 bits of the FDRA field are all “0”. That is, when all 5 MSBs of the FDRA field are “0”.
[0424] The fourth case is when all of the Y bits in the FDRA field are “1”. That is, when all of the Y LSB bits in the FDRA field are “1”.
[0425] Each situation is described in more detail below.
[0426] Situation 1. When one cell has a 15 kHz subcarrier spacing.
[0427] The terminal can check the subcarrier spacing and FDRA type information of each cell included in the set of candidate cells scheduled by MC-DCI. If one of the cells included in the set of candidate cells scheduled by MC-DCI is set to FDRA type-2, the terminal can check whether the subcarrier spacing of the cell is 15 kHz (μ=0) or 30 kHz (μ=1). This embodiment may be the case where the terminal has confirmed that the subcarrier spacing of the cell is 15 kHz (μ=0).
[0428] FIG. 13 is a diagram illustrating an example of a field indicating frequency domain resource allocation information according to a subcarrier spacing of a cell according to one embodiment of the present disclosure.
[0429] Figure 13 (a) illustrates an example of a field indicating frequency domain resource allocation information when the subcarrier spacing of a cell is 15 kHz. The size of the frequency resource in the bandwidth portion can be defined as the number of RBs included in the bandwidth portion. More specifically, if the terminal is instructed to allocate FDRA type-0 resources, the length of the FDRA field of the DCI received by the terminal is the number of RBGs (N) in the bandwidth portion. RBG ) and Here, the first RBG within the bandwidth section is It contains RBs of the dog, and the last RBG within the bandwidth part is On the other hand, Contains the RBs of the dog, otherwise, It contains P RBs. The remaining RBGs within the bandwidth portion contain P RBs. Here, P can be set by upper layer signaling and can have a value of 2 or 4, and other values may not be excluded.
[0430] Referring to (a) of Fig. 13, when the subcarrier spacing of a cell is 15 kHz, the length of the field indicating frequency domain allocation information of the cell within MC-DCI may be 6+Y bits. Here, 6 bits may indicate the start index (m0) and length (L) of M=10 interlaces included in one RB-set, and Y bits indicate the scheduled RB-set. Here, Y bits can indicate the index and length of the starting RB set among the RB sets included in the UL BWP. In the present disclosure, may be the number of RB-sets set for indicated active UL BWP. In the present disclosure, for convenience, 6 bits and Y bits may be referred to as RIV mode (or RIV-like).
[0431] More specifically, 6 bits are as follows:
[0432] When μ=0, X=6 MSBs (Most Significant Bits) of resource block allocation information (or frequency domain resource allocation information) can indicate a set of interlace indices m0+l allocated to the UE. Here, the indication for the set of interlace indices is composed of a Resource Indication Value (RIV). and when l=0,1,...,L-1, the resource indication value corresponds to the starting interlace index m0 and the number of consecutive interlace indices. The resource indication value is defined as follows.
[0433] [RIV formula]
[0434]
[0435] For , the RIV value corresponds to the start interlace index m0 and l value in [Table 20] below.
[0436] [Table 20]
[0437]
[0438] Referring to the RIV formula or [Table 20] above, among the RIV values The starting interlace index and the number of consecutive interlace indices can be indicated according to the RIV formula, and then According to [Table 20], the start interlace index (m0) and l value can be indicated. The 6 bits of the RIV value can represent one of the values 0, 1,…, 63, and 0, 1,…, 62 are the values used to schedule the interlace. However, RIV=63 (6 bits in binary are ‘111111’) may be an unused value. In other words, there may not be a scheduled interlace corresponding to the value (RIV=63). Therefore, an unscheduled cell can be indicated using the value (RIV=63 (6 bits in binary are ‘111111’)).
[0439] More specifically, Y bits are as follows:
[0440] When μ=0 to μ=1, the resource block allocation information (or frequency domain resource allocation information) The least significant bit (LSB) indicates a contiguous RB set to the terminal. For example, Y bits may be present in DCI format 0_1. The resource allocation field contains a resource indication value ( ) is composed of. For , the resource indication value is the starting RB set index ( ) and the number of consecutive RB sets ( ) is indicated. The resource indication value is defined as follows.
[0441]
[0442] Referring to the above formula, the following can be observed.
[0443] - When 1 RB-set is included in UL BWP ( ), Y=0 bits (Y=0). Therefore, when Y=0 bits, cells that are not scheduled with the Y bits may not be indicated.
[0444] - When two RB-sets are included in the UL BWP ( ), Y=2 bits (Y=2). Here, can be used to indicate the starting RB set index and the number of consecutive RB sets. Y bits can have values of 0, 1,…, 3. Therefore, there may not be a scheduled RB-set corresponding to Y bits equal to 3 (both 2 bits are '11', 2 bits are '11' in binary). Therefore, an unscheduled cell can be indicated using the above value (3 (2 bits are '11' in binary).
[0445] - When 3 RB-sets are included in UL BWP ( ), Y=3 bits (Y=3). Here, can be used to indicate the starting RB set index and the number of consecutive RB sets. Y bits can have values of 0, 1,…, 7. Therefore, there may not be a scheduled RB-set corresponding to 7 of Y bits (all 3 bits are '111', 3 bits are '111' in binary). Therefore, an unscheduled cell can be indicated using the above value (7 (3 bits are '111' in binary)).
[0446] - When 4 RB-sets are included in UL BWP ( ), Y=4 bits (Y=4). Here, is used to indicate the starting RB set index and the number of consecutive RB sets. Y bits can have values of 0, 1,…, 15. Therefore, there may not be a scheduled RB-set corresponding to Y bits equal to 15 (all 4 bits are '1111'. In binary, 4 bits are '1111'). Therefore, an unscheduled cell can be indicated using the above value (15 (4 bits are '1111' in binary)).
[0447] - When 5 RB-sets are included in UL BWP ( ), Y=4 bits (Y=4). Here, is used to indicate the starting RB set index and the number of consecutive RB sets. Y bits can have values of 0, 1,…, 15. Therefore, there may not be a scheduled RB-set corresponding to Y bits equal to 15 (all 4 bits are '1111'. In binary, 4 bits are '1111'). Therefore, an unscheduled cell can be indicated using the above value (15 (4 bits are '1111' in binary)).
[0448] In summary, in all cases except for the case where Y=0 among the sizes of Y bits, if all Y bits are '1', an unscheduled cell may be indicated. That is, if all bits included in the Y LSB of FDRA are '1', an unscheduled cell may be indicated.
[0449] In the present disclosure, the method for indicating that a cell with a 15 kHz subcarrier spacing is not scheduled may be one or a combination of at least one of the following. In the description of the present method, the FDRA field is a field corresponding to a cell with the 15 kHz subcarrier spacing. And the FDRA type may be FDRA type-2.
[0450] - In the first method, the terminal can determine whether a cell is scheduled based on all bits (6+Y bits) of the FDRA field. For example, if all bits of the FDRA field are '1', the terminal can determine that the cell is an unscheduled cell. Here, the FDRA field can include 6 bits MSB and Y bits LSB. Therefore, the terminal can determine that the cell of the 15kHz subcarrier spacing corresponding to the FDRA field is not scheduled if all 6+Y bits are '1' (if the bit values of the bits included in 6+Y bits are all 1). For example, if all 6 bits MSB are '1' and the remaining Y bits LSB are not all '1' (if all bit values of the bits included in the 6 MSBs are 1 and at least some bit values of the bits included in the Y LSB are 0 or if all bit values of the bits included in the 6 MSBs are 1 and the bit values of the bits included in the Y LSB are all 0), the terminal can determine that the DCI format including the above information is an error case. Alternatively, if all Y bits LSB are '1' and the remaining 6 bits MSB are not all '1' (if all bit values of the bits included in the Y LSB are 1 and at least some bit values of the bits included in the 6 MSBs are 0 or if all bit values of the bits included in the Y LSB are 1 and the bit values included in the 6 MSBs are 0), the terminal can determine that the DCI format including the above information is an error case. If it is determined to be an error case, the terminal may discard (or ignore) the information indicated by the DCI format above.Alternatively, if it is determined to be an error case, the terminal may discard the information about the cell (the cell corresponding to the FDRA field determined to be an error case) among the information indicated by the DCI format and apply the information about the remaining cells (the remaining cells excluding the cell corresponding to the FDRA field determined to be an error case).
[0451] - In the second method, the terminal can determine whether a cell is scheduled based on only the 6 bits MSB of the FDRA field. The terminal can identify whether a cell is scheduled through the 6 MSBs of the FDRA field. For example, if all bits of the 6 bits MSB of the FDRA field are '1' (if the bit values of all bits included in the 6 MSBs are 1), the terminal can determine that the cell (the cell corresponding to the FDRA field) is an unscheduled cell. Accordingly, the terminal can determine that the cell of the 15 kHz subcarrier spacing corresponding to the FDRA field is unscheduled if all of the 6 bits MSB are '1'. For example, in this case, the bits of the Y bits LSB may not provide information. That is, regardless of the value of the Y bits LSB, whether a cell is scheduled can be determined based on the 6 bits MSB. For example, Y bits LSB may be discarded, ignored, or not included in the FDRA field (e.g., Y=0).
[0452] - In a third method, the terminal can determine whether a cell is scheduled based only on the Y bits LSB of the FDRA field. The terminal can identify whether a cell is scheduled through the Y LSB of the FDRA field. For example, if all bits of the Y bits LSB of the FDRA field are '1' (if the bit values of all bits included in the Y LSB are 1), the terminal can determine that the cell (the cell corresponding to the FDRA field) is an unscheduled cell. Accordingly, the terminal can determine that the cell of the 15kHz subcarrier spacing corresponding to the FDRA field is unscheduled if all of the total Y bits LSB are '1'. For example, in this case, the bits of the 6 bits MSB may not provide information. That is, whether a cell is scheduled can be determined based on the Y bits LSB regardless of the value of the 6 bits MSB. For example, the 6 bits MSB may be discarded, ignored, or not included in the FDRA field.
[0453] In one embodiment, the third method may be used when Y>0. If Y=0, the second method may be used. That is, based on the value of Y, the second or third method may be selectively used. That is, the method to be used by the terminal may be determined based on the value of Y (the bit size of the Y LSB of the FDRA field).
[0454] Situation 2: When one cell has a 30 kHz subcarrier spacing
[0455] The terminal can check the subcarrier spacing and FDRA type information of each cell included in the set of candidate cells scheduled by MC-DCI. If one of the cells included in the set of candidate cells scheduled by MC-DCI is set to FDRA type-2, the terminal can check whether the subcarrier spacing of the cell is 15 kHz (μ=0) or 30 kHz (μ=1). This embodiment may be the case where the terminal has confirmed that the subcarrier spacing of the cell is 30 kHz (μ=1).
[0456] Figure 13 (b) shows an example of a field indicating frequency domain resource allocation information when the subcarrier spacing of a cell is 30 kHz.
[0457] Referring to (b) of Fig. 13, when the subcarrier spacing of a cell is 30 kHz, the length of the field indicating frequency domain allocation information of the cell within MC-DCI may be 5+Y bits. Here, 5 bits may indicate, as a bitmap, whether M=5 interlaces included in one RB-set are scheduled. That is, each bit included in the 5 bits may be used to indicate whether one interlace is scheduled. Here, an interlace corresponding to a bit with a value of '1' among the 5 bits may be determined to be scheduled. An interlace corresponding to a bit with a value of '0' among the 5 bits may be determined not to be scheduled. Y bits indicate a scheduled RB-set, Here, Y bits can indicate the index and length of the starting RB set among the RB sets included in the UL BWP. In the present disclosure, may be the number of RB-sets set for indicated active UL BWP. In the present disclosure, for convenience, 5 bits are called bitmap mode and Y bits are called RIV mode (or RIV-like).
[0458] The above 5 bits can indicate an interlace scheduled based on a bitmap. If each bit of the above 5 bits is '1', the terminal can determine that the interlace corresponding to '1' is scheduled. In other words, the interlace corresponding to a bit with a value of '1' among the 5 bits can be determined to be scheduled. If all of the above 5 bits are '0', no interlace may be scheduled. Therefore, if the above 5 bits are all '0', the terminal can determine that the cell is not scheduled.
[0459] Since the Y bits in situation 2 are the same as in Example 1, their explanation is omitted. For this, refer to the explanation of the Y bits in situation 1.
[0460] The FDRA field of a cell with a 30kHz subcarrier spacing contains 5+Y bits, where the 5-bit MSB indicates the interlace scheduled within the RB set in bitmap format, and the Y-bit LSB indicates the RB sets scheduled in RIV format. Therefore, whether a cell is scheduled can be determined based on the values of the 5-bit MSB and the Y-bit LSB.
[0461] In the present disclosure, a method for indicating that a cell with a 30 kHz subcarrier spacing is not scheduled may be one or a combination of at least one of the following. In the description of the present method, the FDRA field is a field corresponding to a cell with the 30 kHz subcarrier spacing. And the FDRA type may be FDRA type-2.
[0462] - In the first method, the terminal can determine whether a cell is scheduled based on all bits (5+Y bits) of the FDRA field. For example, if all bits of the FDRA field are '0', the terminal can determine that the cell with the 30kHz subcarrier spacing is an unscheduled cell. Here, the FDRA field can include 5 bits MSB and Y bits LSB. Therefore, the terminal can determine that the cell with the 30kHz subcarrier spacing corresponding to the FDRA field is not scheduled if all 5+Y bits are '0' (if all bit values of the bits included in 5+Y bits are 0). For example, if all Y bits LSB are '0', Depending on the formula, a corresponding value may exist. However, since all 5 bits MSB are '0', the RB set indicated by Y bits LSB may not be used as information on whether or not to schedule. In other words, since it is determined that there is no scheduled interlace since all 5 bits MSB are '0', the RB set corresponding to Y bits LSB can be ignored.
[0463] - In the second method, the terminal can determine whether a cell is scheduled based on only the 5 bits MSB of the FDRA field. The terminal can identify whether a cell is scheduled through the 5 MSBs of the FDRA field. For example, if all bits of the 5 bits MSB of the FDRA field are '0' (if the bit values of all bits included in the 5 MSBs are 1), the terminal can determine that the cell (the cell corresponding to the FDRA field) is an unscheduled cell. Accordingly, the terminal can determine that the cell of the 30 kHz subcarrier spacing corresponding to the FDRA field is not scheduled if all 5 bits MSB are '0'. For example, in this case, the bits of the Y bits LSB may not provide information. That is, regardless of the value of the Y bits LSB, whether a cell is scheduled can be determined based on the 5 bits MSB. For example, Y bits LSB may be discarded, ignored, or not included in the FDRA field (e.g., Y may be 0).
[0464] - In a third method, the terminal can determine whether a cell is scheduled based only on the Y bits LSB of the FDRA field. The terminal can identify whether a cell is scheduled through the Y LSB of the FDRA field. For example, if all bits of the Y bits LSB of the FDRA field are '1' (if the bit value of all bits included in the Y LSB is 1), the terminal can determine that the cell (the cell corresponding to the FDRA field) is an unscheduled cell. Therefore, the terminal can determine that the cell of the 30kHz subcarrier spacing corresponding to the FDRA field is unscheduled if all of the total Y bits LSB are '1'. For example, in this case, the bit of the 5 bits MSB may not provide information. That is, whether a cell is scheduled may be determined based on the Y bits LSB regardless of the value of the 5 bits MSB. For example, the 5 bits MSB may be discarded, ignored, or not included in the FDRA field.
[0465] In one embodiment, the third method may be used when Y>0. If Y=0, the second method may be used. That is, based on the value of Y, the second or third method may be selectively used. That is, the method to be used by the terminal may be determined based on the value of Y (the bit size of the Y LSB of the FDRA field).
[0466] <Example 2: SRS Setting and Instruction Method for MC-DCI>
[0467] In addition to the basic self-carrier or cross-carrier SRS configuration operations described above, the following describes co-scheduled cell configuration operations associated with SRS for multi-carriers according to one embodiment of the present disclosure. This embodiment may operate independently or in combination with other embodiments. One or more of the following methods and / or a combination of one or more of the following methods may be used.
[0468] First, at least one carrier (band) among the multi-carriers on which SRS transmission is performed can commonly utilize the configuration and instruction of co-scheduled cells determined for transmission of at least one channel or reference signal among PDSCH, PUSCH, and CSI-RS. That is, at least one carrier (band) among the multi-carriers on which SRS transmission is performed can follow the configuration and instruction of co-scheduled cells determined for transmission of at least one channel or reference signal among PDSCH, PUSCH, and CSI-RS.
[0469] Second, at least one carrier (band) among the multi-carriers on which SRS transmission is performed can be independently configured, distinct from the configuration of co-scheduled cells determined for transmission of channels or reference signals such as PDSCH, PUSCH, CSI-RS, etc. The base station and the terminal can configure separate co-scheduled cells for SRS only by linking at least one cell ID when configuring an SRS resource set or SRS resource.
[0470] Thirdly, the maximum number of carriers of a multi-carrier on which SRS transmission is performed in DCI format 0_3 / 1_3 may be determined or set to at least one of {3, 4, 8}. As described above, if a base station sets the maximum number of carriers to one of the above values for a specific terminal, the terminal may determine that the number of SRS transmissions indicated in DCI format 0_3 is determined to be less than or equal to the determined / set value.
[0471] Fourth, the bit-width of the field indicating co-scheduled cells that the base station indicates for SRS transmission of the terminal in DCI format 0_3 / 1_3 can be set to at least 4 bits or less. For the co-scheduled cells indicator, as described above, a table can be set by {2^max_num_bits_DCI_field, number of cells}. In particular, in order to indicate the set table, DCI format 0_3 / 1_3 can indicate all combinations of cells in all entries of the set table. Table 21 shows an example of a table according to one embodiment of the present disclosure.
[0472] [Table 21]
[0473]
[0474] For example, in Table 21, the 4 bits of type A can exclude single-cell indications as explained above. That is, the 0000-1111 indices can be mapped to the combination of cells below so that at least two or more cells can be indicated. That is, in the case of type A, at least two or more cells can be indicated. In this case, the mapping of the combination of cells and the indices can be sequentially linked, and can be mapped to cell ids in ascending or descending order.
[0475] 2 cell instructions: {cell 0, cell 1}, {cell 0, cell 2}, {cell 0, cell 3}, {cell 1, cell 2}, {cell 1, cell3}, {cell 2, cell3},
[0476] 3 cell instructions: {cell 0, cell1, cell2}, {cell 0, cell1, cell3}, {cell 0, cell2, cell3}, {cell 1, cell2, cell3},
[0477] 4 cell instructions: {cell 0, cell1, cell2, cell 3}
[0478] As another example, the 4 bits of type B in Table 21 may include indicating a single cell. That is, the 0000-1111 index may be mapped to a combination of cells below so that at least one cell may be indicated. That is, for type B, more than one cell may be indicated. In this case, the mapping of the combination of cells and the index may be sequentially linked and may be mapped to a cell id in ascending or descending order.
[0479] The type A or type B described above can be determined as one type depending on the settings of the base station and the terminal. For example, the base station can configure either type A or type B to the terminal. Alternatively, the determination of type A and type B can be determined differently depending on the index of the DCI format. That is, type A and type B can be determined depending on the DCI format. For example, type A can be applied in DCI format 0_3 and / or 1_3, and type B can be applied in a different DCI format. For example, type B can be applied in a DCI format other than DCI format 0_3 and / or 1_3.
[0480] If the size of the field for indicating co-scheduled cells between the base station and the terminal is 4 bits, co-scheduled cells can be sequentially indicated by combining the 11 cells, and the remaining 5 indicators can be assumed to be unused in a reserved form or used for a separate purpose.
[0481] In addition to the basic self-carrier or cross-carrier SRS configuration operations described above, the following describes an SRS configuration operation for multi-carriers according to one embodiment of the present disclosure. This embodiment may be operated independently or in combination with other embodiments. One or more of the following methods and / or a combination of one or more of the following methods may be used.
[0482] First, the base station can configure an SRS resource set or SRS resource in a higher layer for self-carrier, cross-carrier SRS transmission, and can commonly configure an SRS resource set or SRS resource configuration in a higher layer for SRS transmission for multi-carrier. That is, the terminal can apply a configuration for SRS resources based on the common configuration of the base station. The base station can configure an SRS resource set and / or SRS resource through higher layer signaling, and the terminal can commonly apply the configured SRS resource set and / or SRS resource to self-carrier, cross-carrier SRS transmission, and SRS (or multi-carrier SRS) transmission for multi-carrier.
[0483] Second, the base station can configure an SRS resource set or SRS resource in a higher layer for self-carrier, cross-carrier SRS transmission, and separately configure an SRS resource set or SRS resource in a higher layer for SRS transmission for multi-carrier. The base station can configure an SRS resource set and / or SRS resource for self-carrier, cross-carrier SRS, and also configure an SRS resource set and / or SRS resource for multi-carrier SRS through higher layer signaling. The terminal can apply the configured SRS resource set and / or SRS resource for self-carrier, cross-carrier SRS to self-carrier, cross-carrier SRS transmission. The terminal can apply the configured SRS resource set and / or SRS resource for multi-carrier SRS to multi-carrier SRS transmission.
[0484] Third, if the base station configures two SRS resource sets for codebook or non-codebook based SRS transmission to the terminal, the terminal can determine that the PUSCH scheduled in DCI format 0_3 is always associated with the first SRS resource set based on codebook or non-codebook.
[0485] Fourth, the bit-width of the field indicating the SRS request or SRS offset indicator that the base station indicates for SRS transmission of the terminal in DCI format 0_3 may be set to at least 4 bits or less. For example, the SRS request fields may indicate SRS request information corresponding to at least two or more co-scheduled cells.
[0486] Below, information in the SRS request field corresponding to the co-scheduled cell indicated in DCI format 0_3 is specifically described. This embodiment may be operated in combination with other embodiments or may be operated independently. One or more of the following embodiments and / or a combination of one or more of the following embodiments may be used.
[0487] In one embodiment, a single field for an SRS request may indicate a common SRS request to co-scheduled cells scheduled in the same slot or the same PDCCH. Specifically, when a base station indicates a co-scheduled cells information indicator 0000 in a 4-bit type A format to a terminal and indicates 0000 in an SRS request field, the terminal may determine to transmit an SRS transmission based on the SRS resource information indicated by 0000 in the SRS request field to {cell 0, cell 1} corresponding to the co-scheduled cells information indicator 0000. Here, it can be assumed that the commonly applicable SRS information has the same specific configuration information such as an SRS resource set, a location of an SRS resource set in an SRS resource, a period of the resource, a comb type, an offset, etc., or is set similarly to correspond to the band information of the corresponding cell.
[0488] In another embodiment, a single field for an SRS request may be applied to only one cell among co-scheduled cells scheduled in the same slot or on the same PDCCH. For example, a specific carrier may be temporarily released or excluded during a carrier update among multiple carriers.
[0489] In another embodiment, a single field for an SRS request may indicate an SRS request corresponding to each co-scheduled cell scheduled in the same slot or the same PDCCH using a joint indication method. Here, the information in the SRS request field means that the information corresponds to the value set in the SRS resource set, Triggered AP-SRS-resource(s), set by the base station to the terminal during the RRC configuration process. In addition, the base station may set up to four Triggered AP-SRS-resource(s) per BWP, taking into account the co-scheduled cells in the RRC configuration.
[0490] Table 22 illustrates an example of RRC settings according to one embodiment of the present disclosure. The names of each information element (IE) are examples and the present disclosure is not limited thereto.
[0491] [Table 22]
[0492]
[0493] In Table 22, srs-RequestDCI-1-3 may be an IE that sets the number of bits of the SRS request field included in DCI format 1_3, and srs-RequestDCI-0-3 may be an IE that sets the number of bits of the SRS request field included in DCI format 0_3. The number of bits of the SRS request field may be set to 1 bit to 4 bits, but this is an example and the present disclosure is not limited thereto.
[0494] Alternatively, considering that the maximum number of co-scheduled cells that can be scheduled in DCI format 0_3 / 1_3 is 4, the number of bits in the SRS request field may be 4 bits. For example, it may be set to 4 bits by the above srs-RequestDCI-0-3 / srs-RequestDCI-1-3 or may be predefined to 4 bits.
[0495] After the RRC setting, the base station can basically link and instruct co-scheduled cells and Triggered AP-SRS-resource(s) using SRS request information in DCI included in PDCCH. After the RRC setting, the base station can additionally transmit a MAC-CE message to remap or update the linkage of the configured Triggered AP-SRS-resource(s) and co-scheduled cells. After transmitting the MAC CE, the base station can finally link and instruct co-scheduled cells and Triggered AP-SRS-resource(s) by transmitting a PDCCH including SRS request information in DCI to the terminal. Detailed information related thereto is described in detail in the description of an embodiment of the present disclosure described with reference to FIGS. 14 to 16.
[0496] Below, we specifically assume that the base station indicates to the terminal co-scheduled cell information in the form of 4 bits-type A / B, and describe the method of indicating SRS request information of up to 4 bits. For an example of co-scheduled cell information in the form of 4 bits-type A / B, refer back to Table 21.
[0497] In one embodiment, the range of values of the table indicated in the SRS request field in DCI format 0_3 / 1_3 for multi-carrier may be indicated to match the range of values of the SRS request field in DCI format 0_1 / 1_1. In this case, the range of values in the table itself may correspond to {00, 01, 10, 11}. In this case, since the range is determined by only 2 bits out of the entire 4-bit field, values of up to 2 tables may be indicated.
[0498] FIG. 14 is a diagram illustrating an example of a field indicating a plurality of cells and an SRS request in MC-DCI according to an embodiment of the present disclosure. FIG. 14A is an example (1400) in which the number of co-scheduled cells scheduled by MC-DCI is 2, and FIG. 14B is an example (1450) in which the number of co-scheduled cells scheduled by MC-DCI is 3.
[0499] Referring to FIG. 14A, an embodiment (1400) of the correspondence between the information structure of MC-DCI transmitted by a base station and the SRS request information associated therewith is described. MC-DCI may include information on co-scheduled cells, FDRA information for co-scheduled cells, and an SRS request field. For more specific details on FDRA information for co-scheduled cells, refer to the description of the first embodiment.
[0500] For example, a base station can indicate to a terminal information of two co-scheduled cells in DCI format 0_3 and / or DCI format 1_3 for MC-DCI. DCI format 0_3 / 1_3 can include information of co-scheduled cells. DCI format 0_3 / 1_3 including information of co-scheduled cells can be understood as an example of MC-DCI. For example, if a terminal receives a value of 0010 as in Table 21, it can determine that the indicated cell 0 and cell 3 are indicated as co-scheduled cells. That is, if the terminal confirms 0010 as information of co-scheduled cells from DCI, it can determine that cell 0 and cell 3 are indicated as co-scheduled cells. In this case, when two cells are indicated, the base station can allocate the first two bits to cell 0 corresponding to the first of the two cells, and the remaining two bits to cell 3 corresponding to the second. The two most significant bits of the four bits of the SRS request field can correspond to / map to the first cell (cell 0) among the co-scheduled cells. The two least significant bits of the four bits of the SRS request field can correspond to / map to the second cell (cell 3) among the co-scheduled cells.
[0501] For example, if the SRS request information received by the terminal is 0010, it can be determined that the SRS is transmitted using the SRS resources set in the Triggered AP-SRS-resource(s) set 0 associated with the first cell (e.g., cell 0) and the SRS resources set in the Triggered AP-SRS-resource(s) set 2 associated with the second cell (e.g., cell 3). Here, the terminal may not expect a case where the associated Triggered AP-SRS-resource(s) set index is not set.
[0502] For example, if the value of 2 MSBs of the 4 bits of the SRS request field is 00, it may indicate Triggered AP-SRS-resource(s) set 0 for the first cell among the co-scheduled cells. That is, the terminal can transmit SRS to the first cell using the SRS resources set in Triggered AP-SRS-resource(s) set 0.
[0503] For example, if the value of 2 MSBs of the 4 bits of the SRS request field is 01, it may indicate Triggered AP-SRS-resource(s) set 1 for the first cell among the co-scheduled cells. That is, the terminal can transmit SRS to the first cell using the SRS resources set in Triggered AP-SRS-resource(s) set 1.
[0504] For example, if the value of the 2 MSBs of the 4 bits of the SRS request field is 10, it may indicate Triggered AP-SRS-resource(s) set 2 for the first cell among the co-scheduled cells. That is, the terminal can transmit SRS to the first cell using the SRS resources set in Triggered AP-SRS-resource(s) set 2.
[0505] For example, if the value of 2 MSBs of the 4 bits of the SRS request field is 11, it may indicate Triggered AP-SRS-resource(s) set 3 for the first cell among the co-scheduled cells. That is, the terminal can transmit SRS to the first cell using the SRS resources set in Triggered AP-SRS-resource(s) set 3.
[0506] For example, if the value of 2 LSBs of the 4 bits of the SRS request field is 00, it may indicate Triggered AP-SRS-resource(s) set 0 for the second cell among the co-scheduled cells. That is, the terminal can transmit SRS to the second cell using the SRS resources set in Triggered AP-SRS-resource(s) set 0.
[0507] For example, if the value of the 2nd LSB of the 4 bits of the SRS request field is 01, it may indicate Triggered AP-SRS-resource(s) set 1 for the second cell among the co-scheduled cells. That is, the terminal can transmit SRS to the second cell using the SRS resources set in Triggered AP-SRS-resource(s) set 1.
[0508] For example, if the value of the 2 LSBs of the 4 bits of the SRS request field is 10, this may indicate Triggered AP-SRS-resource(s) set 2 for the second cell among the co-scheduled cells. That is, the terminal can transmit SRS to the second cell using the SRS resources set in Triggered AP-SRS-resource(s) set 2.
[0509] For example, if the value of the 2nd LSB of the 4 bits of the SRS request field is 11, this may indicate Triggered AP-SRS-resource(s) set 3 for the second cell among the co-scheduled cells. That is, the terminal can transmit SRS to the second cell using the SRS resources set in Triggered AP-SRS-resource(s) set 3.
[0510] An example of the SRS request field can be found in Table 23. The SRS-Request-IndicatorList can be a configuration IE that allows RRC to request multiple SRS resources to indicate at the DCI / MAC CE level that is multi-carrier / multi-scheduled.
[0511] [Table 23]
[0512]
[0513] For example, if the format of the received DCI is 0_3, the SRS request field can be interpreted as above based on SRS-Request-IndicatorList-DCI-0-3, and if the format of the received DCI is 1_3, the SRS request field can be interpreted as above based on SRS-Request-IndicatorList-DCI-1-3.
[0514] Referring to FIG. 14B, an embodiment (1450) of the correspondence between the information structure of MC-DCI transmitted by a base station and the SRS request information associated therewith is described. MC-DCI may include information on co-scheduled cells, FDRA information for co-scheduled cells, and an SRS request field. For more specific details on FDRA information for co-scheduled cells, refer to the description of the first embodiment.
[0515] Extending the embodiment (1400) of FIG. 14A, for example, the base station may indicate to the terminal information of three co-scheduled cells in DCI format 0_3 and / or DCI format 1_3 for MC-DCI. DCI format 0_3 / 1_3 may include information of co-scheduled cells. DCI format 0_3 / 1_3 including information of co-scheduled cells may be understood as an example of MC-DCI. For example, if the terminal receives a value of 0111 as in Table 21, it may determine that the indicated cell 0, cell 1, and cell 3 are indicated as co-scheduled cells. That is, if the terminal confirms 0111 as information of co-scheduled cells from the DCI, it may determine that cell 0, cell 1, and cell 3 are indicated as co-scheduled cells. In this case, when three cells are indicated, the base station can allocate the first two bits to cell 0 and / or cell 1 among the three cells, and allocate the remaining two bits to cell 3 corresponding to the second. The two most significant bits of the four bits of the SRS request field can correspond to / map to the first cell (cell 0) and the second cell (cell 1) among the co-scheduled cells. The two least significant bits of the four bits of the SRS request field can correspond to / map to the third cell (cell 3) among the co-scheduled cells.For example, if the SRS request information received by the terminal is 1110, it can be determined that the SRS is transmitted using the SRS resources set in the Triggered AP-SRS-resource(s) set 3 associated with the cell (e.g., cell 0 and / or cell 1) for the first 2 bits, and using the SRS resources set in the Triggered AP-SRS-resource(s) set 2 associated with the cell (e.g., cell 3) for the second 2 bits.
[0516] For example, if the value of 2 MSBs of the 4 bits of the SRS request field is 00, it may indicate Triggered AP-SRS-resource(s) set 0 for the first cell and the second cell among the co-scheduled cells. That is, the terminal can transmit SRS for the first cell and the second cell using the SRS resources set in Triggered AP-SRS-resource(s) set 0.
[0517] For example, if the value of 2 MSBs of the 4 bits of the SRS request field is 01, it may indicate Triggered AP-SRS-resource(s) set 1 for the first cell and the second cell among the co-scheduled cells. That is, the terminal can transmit SRS for the first cell and the second cell using the SRS resources set in Triggered AP-SRS-resource(s) set 1.
[0518] For example, if the value of 2 MSBs of the 4 bits of the SRS request field is 10, it may indicate Triggered AP-SRS-resource(s) set 2 for the first cell and the second cell among the co-scheduled cells. That is, the terminal can transmit SRS for the first cell and the second cell using the SRS resources set in Triggered AP-SRS-resource(s) set 2.
[0519] For example, if the value of 2 MSBs of the 4 bits of the SRS request field is 11, this may indicate Triggered AP-SRS-resource(s) set 3 for the first cell and the second cell among the co-scheduled cells. That is, the terminal can transmit SRS for the first cell and the second cell using the SRS resources set in Triggered AP-SRS-resource(s) set 3.
[0520] For example, if the value of 2 LSBs of the 4 bits of the SRS request field is 00, it may indicate Triggered AP-SRS-resource(s) set 0 for the third cell among the co-scheduled cells. That is, the terminal can transmit SRS to the third cell using the SRS resources set in Triggered AP-SRS-resource(s) set 0.
[0521] For example, if the value of 2 LSBs of the 4 bits of the SRS request field is 01, this may indicate Triggered AP-SRS-resource(s) set 1 for the third cell among the co-scheduled cells. That is, the terminal can transmit SRS to the third cell using the SRS resources set in Triggered AP-SRS-resource(s) set 1.
[0522] For example, if the value of the 2 LSBs of the 4 bits of the SRS request field is 10, this may indicate Triggered AP-SRS-resource(s) set 2 for the third cell among the co-scheduled cells. That is, the terminal can transmit SRS to the third cell using the SRS resources set in Triggered AP-SRS-resource(s) set 2.
[0523] For example, if the value of the 2 LSBs of the 4 bits of the SRS request field is 11, this may indicate Triggered AP-SRS-resource(s) set 3 for the third cell among the co-scheduled cells. That is, the terminal can transmit SRS to the third cell using the SRS resources set in Triggered AP-SRS-resource(s) set 3.
[0524] Alternatively, the base station may allocate the first two bits to cell 0, which corresponds to the first of the three cells, and the remaining two bits to cell 1 and / or cell 3, which correspond to the second. Of the four bits of the SRS request field, the two most significant bits may correspond to / map to the first cell (cell 0) among the co-scheduled cells, and the two least significant bits may correspond to / map to the second cell (cell 1) and the third cell (cell 3) among the co-scheduled cells. For example, if the SRS request information received by the terminal is 1110, it can be determined that the SRS is transmitted using the SRS resources set in the Triggered AP-SRS-resource(s) set 3 associated with the first cell (e.g., cell 0) and the SRS resources set in the Triggered AP-SRS-resource(s) set 2 associated with the second cell (e.g., cell 1 and / or cell 3).
[0525] For example, if the value of 2 MSBs of the 4 bits of the SRS request field is 00, it may indicate Triggered AP-SRS-resource(s) set 0 for the first cell among the co-scheduled cells. That is, the terminal can transmit SRS to the first cell using the SRS resources set in Triggered AP-SRS-resource(s) set 0.
[0526] For example, if the value of 2 MSBs of the 4 bits of the SRS request field is 01, it may indicate Triggered AP-SRS-resource(s) set 1 for the first cell among the co-scheduled cells. That is, the terminal can transmit SRS to the first cell using the SRS resources set in Triggered AP-SRS-resource(s) set 1.
[0527] For example, if the value of the 2 MSBs of the 4 bits of the SRS request field is 10, it may indicate Triggered AP-SRS-resource(s) set 2 for the first cell among the co-scheduled cells. That is, the terminal can transmit SRS to the first cell using the SRS resources set in Triggered AP-SRS-resource(s) set 2.
[0528] For example, if the value of 2 MSBs of the 4 bits of the SRS request field is 11, it may indicate Triggered AP-SRS-resource(s) set 3 for the first cell among the co-scheduled cells. That is, the terminal can transmit SRS to the first cell using the SRS resources set in Triggered AP-SRS-resource(s) set 3.
[0529] For example, if the value of 2 LSBs of the 4 bits of the SRS request field is 00, it may indicate Triggered AP-SRS-resource(s) set 0 for the second cell and the third cell among the co-scheduled cells. That is, the terminal can transmit SRS for the second cell and the third cell using the SRS resources set in Triggered AP-SRS-resource(s) set 0.
[0530] For example, if the value of 2 LSBs of the 4 bits of the SRS request field is 01, this may indicate Triggered AP-SRS-resource(s) set 1 for the second cell and the third cell among the co-scheduled cells. That is, the terminal can transmit SRS for the second cell and the third cell using the SRS resources set in Triggered AP-SRS-resource(s) set 1.
[0531] For example, if the value of the 2 LSBs of the 4 bits of the SRS request field is 10, this may indicate Triggered AP-SRS-resource(s) set 2 for the second and third cells among the co-scheduled cells. That is, the terminal can transmit SRS for the second and third cells using the SRS resources set in Triggered AP-SRS-resource(s) set 2.
[0532] For example, if the value of 2 LSBs of the 4 bits of the SRS request field is 11, this may indicate Triggered AP-SRS-resource(s) set 3 for the second and third cells among the co-scheduled cells. That is, the terminal can transmit SRS for the second and third cells using the SRS resources set in Triggered AP-SRS-resource(s) set 3.
[0533] In the embodiment described above, the terminal may not expect a case where the associated Triggered AP-SRS-resource(s) set index is not set. In addition, whether the first two cells among the three co-scheduled cells are linked to the first 2 bits or the remaining 2 bits may be determined in advance between the base station and the terminal, or may be configured according to parameters (e.g., follow_first, follow_second) during the RRC configuration process. Alternatively, whether the first two cells among the three co-scheduled cells are linked to the first 2 bits and the remaining one cell is linked to the remaining 2 bits, or whether the first cell among the three co-scheduled cells is linked to the first 2 bits and the remaining two cells are linked to the remaining 2 bits, may be determined in advance between the base station and the terminal, or may be configured according to parameters during the RRC configuration process.
[0534] FIG. 15 illustrates other embodiments of the correspondence between the information structure of MC-DCI transmitted by a base station and the SRS request information associated therewith. FIG. 15 is an example (1500, 1550) in which the number of co-scheduled cells scheduled by MC-DCI is 4. MC-DCI may include information on co-scheduled cells, FDRA information for co-scheduled cells, and an SRS request field. For more specific details on FDRA information for co-scheduled cells, refer to the description of the first embodiment.
[0535] Referring to FIG. 15A, for example, a base station may indicate to a terminal information of four co-scheduled cells in DCI format 0_3 and / or DCI format 1_3 for MC-DCI. DCI format 0_3 / 1_3 may include information of co-scheduled cells. DCI format 0_3 / 1_3 including information of co-scheduled cells can be understood as an example of MC-DCI. Here, when the terminal receives the value 1010 as in Table 21, it can determine that the indicated cell 0, cell 1, cell 2, and cell 3 are indicated as co-scheduled cells. That is, when the terminal confirms 1010 as information of co-scheduled cells from DCI, it can determine that cell 0, cell 1, cell 2, and cell 3 are indicated as co-scheduled cells. In this case, when four cells are indicated, the base station can allocate the first two bits to cell 0 and / or cell 1 among the four cells, and allocate the remaining two bits to cell 2 and / or cell 3 corresponding to the second cells. The two most significant bits (MSBs) of the four bits of the SRS request field can correspond to / map to the first cell (cell 0) and the second cell (cell 1) among the co-scheduled cells. The two least significant bits (LSBs) of the four bits of the SRS request field can correspond to / map to the third cell (cell 3) and the fourth cell (cell 4) among the co-scheduled cells.
[0536] For example, if the SRS request information received by the terminal is 0010, it can be determined that the SRS is transmitted using the SRS resources set in the Triggered AP-SRS-resource(s) set 0 associated with the cell (e.g., cell 0 and / or cell 1) for the first 2 bits, and using the SRS resources set in the Triggered AP-SRS-resource(s) set 2 associated with the cell (e.g., cell 2 and / or cell 3) for the second 2 bits.
[0537] For example, if the value of 2 MSBs of the 4 bits of the SRS request field is 00, it may indicate Triggered AP-SRS-resource(s) set 0 for the first cell and the second cell among the co-scheduled cells. That is, the terminal can transmit SRS for the first cell and the second cell using the SRS resources set in Triggered AP-SRS-resource(s) set 0.
[0538] For example, if the value of 2 MSBs of the 4 bits of the SRS request field is 01, it may indicate Triggered AP-SRS-resource(s) set 1 for the first cell and the second cell among the co-scheduled cells. That is, the terminal can transmit SRS for the first cell and the second cell using the SRS resources set in Triggered AP-SRS-resource(s) set 1.
[0539] For example, if the value of 2 MSBs of the 4 bits of the SRS request field is 10, it may indicate Triggered AP-SRS-resource(s) set 2 for the first cell and the second cell among the co-scheduled cells. That is, the terminal can transmit SRS for the first cell and the second cell using the SRS resources set in Triggered AP-SRS-resource(s) set 2.
[0540] For example, if the value of 2 MSBs of the 4 bits of the SRS request field is 11, this may indicate Triggered AP-SRS-resource(s) set 3 for the first cell and the second cell among the co-scheduled cells. That is, the terminal can transmit SRS for the first cell and the second cell using the SRS resources set in Triggered AP-SRS-resource(s) set 3.
[0541] For example, if the value of 2 LSBs of the 4 bits of the SRS request field is 00, it may indicate Triggered AP-SRS-resource(s) set 0 for the third and fourth cells among the co-scheduled cells. That is, the terminal can transmit SRS for the third and fourth cells using the SRS resources set in Triggered AP-SRS-resource(s) set 0.
[0542] For example, if the value of 2 LSBs of the 4 bits of the SRS request field is 01, this may indicate Triggered AP-SRS-resource(s) set 1 for the third and fourth cells among the co-scheduled cells. That is, the terminal can transmit SRS for the third and fourth cells using the SRS resources set in Triggered AP-SRS-resource(s) set 1.
[0543] For example, if the value of the 2 LSBs of the 4 bits of the SRS request field is 10, this may indicate Triggered AP-SRS-resource(s) set 2 for the third and fourth cells among the co-scheduled cells. That is, the terminal can transmit SRS for the third and fourth cells using the SRS resources set in Triggered AP-SRS-resource(s) set 2.
[0544] For example, if the value of 2 LSBs of the 4 bits of the SRS request field is 11, this may indicate Triggered AP-SRS-resource(s) set 3 for the third and fourth cells among the co-scheduled cells. That is, the terminal can transmit SRS for the third and fourth cells using the SRS resources set in Triggered AP-SRS-resource(s) set 3.
[0545] According to the various embodiments described above, up to two SRS resource set ids among the SRS resource set ids set in RRC can be indicated to correspond to SRS request information in MC-DCI. Accordingly, up to two pairs of co-scheduled cells, which are up to four cells, can be designated as SRS resource set ids.
[0546] Below, a method is described to support flexible instructions according to additional RRC settings and / or determined rules of the base station and the terminal so that flexibility in the aspect of the base station instructing the terminal to transmit SRS can be supplemented.
[0547] In one embodiment, the range of values of the table indicated in the SRS request field in the DCI format 0_3 / 1_3 for multi-carrier may be indicated to match the range of values of the SRS request field in the DCI format 0_1 / 1_1. The values of {00, 01, 10, 11} in the field may correspond to the SRS resource set LIST ID or the SRS resource set LIST pattern / rule ID. Here, the SRS resource set LIST ID may be set to correspond to 0 to 3. In addition, the SRS resource set LIST pattern / rule ID may be set to a preconfigured pattern (e.g., 2 / 3 / 0 / 1), an incremental pattern (e.g., 0 / 1 / 2 / 3), a pattern according to a rule (e.g., 0 / 0 / 1 / 1, 2 / 2 / 3 / 3), etc.), and each pattern may correspond to the set values 00 to 11.
[0548] Specifically, referring to FIG. 15B, the base station can indicate to the terminal information of four co-scheduled cells in DCI format 0_3 and / or DCI format 1_3 for MC-DCI. DCI format 0_3 / 1_3 can include information of co-scheduled cells. DCI format 0_3 / 1_3 including information of co-scheduled cells can be understood as an example of MC-DCI. Here, when the terminal receives the value 1010 as in Table 21, it can determine that the indicated cell 0, cell 1, cell 2, and cell 3 are indicated as co-scheduled cells. That is, when the terminal confirms 1010 as information of co-scheduled cells from the DCI, it can determine that cell 0, cell 1, cell 2, and cell 3 are indicated as co-scheduled cells. In this way, when four cells are indicated and determined or set in an increasing pattern (0 / 1 / 2 / 3), the base station can allocate the first two bits as a reference for cell 0 and / or cell 1 corresponding to the first of the four cells to the terminal, and the remaining two bits as a reference for cell 2 and / or cell 3 corresponding to the second.
[0549] That is, if the SRS request information received by the terminal is 0010, the SRS resource set in Triggered AP-SRS-resource(s) set 0 is used in the first cell (cell 0) linked to the cell (e.g., cell 0 and / or cell 1) for the first 2 bits, the SRS resource set in Triggered AP-SRS-resource(s) set 1 is used in the second cell (cell 1) linked to the cell (e.g., cell 0 and / or cell 1) for the first 2 bits, the SRS resource set in Triggered AP-SRS-resource(s) set 2 is used in the first cell (cell 2) linked to the cell (e.g., cell 2 and / or cell 3) for the second 2 bits, and the SRS resource set in Triggered AP-SRS-resource(s) set 2 is used in the second cell (cell 3) linked to the cell (e.g., cell 2 and / or cell 3) for the second 2 bits. It can be determined that SRS is transmitted using the SRS resources set in set 3.
[0550] For the 4 bits of SRS request information, if we distinguish between the MSB 2 bits and the LSB 2 bits, each 2 bits can indicate as follows.
[0551] If MSB is 00, AP-SRS resource Set 0 for the 1st cell and AP-SRS resource Set 1 for the 2nd cell
[0552] If MSB is 01, AP-SRS resource Set 1 for the 1st cell and AP-SRS resource Set 2 for the 2nd cell
[0553] If MSB is 10, AP-SRS resource Set 2 for the 1st cell and AP-SRS resource Set 3 for the 2nd cell
[0554] If MSB is 11, AP-SRS resource Set 3 for the 1st cell and AP-SRS resource Set 0 for the 2nd cell
[0555] If LSB is 00, AP-SRS resource Set 0 for the 3rd cell and AP-SRS resource Set 1 for the 4th cell
[0556] If LSB is 01, AP-SRS resource Set 1 for the 3rd cell and AP-SRS resource Set 2 for the 4th cell
[0557] If LSB is 10, AP-SRS resource Set 2 for the 3rd cell and AP-SRS resource Set 3 for the 4th cell
[0558] If LSB is 11, AP-SRS resource Set 3 for the 3rd cell and AP-SRS resource Set 0 for the 4th cell
[0559] As another example, if 4 bits of SRS request information are interpreted at once, for example, if it is 0000, it can be interpreted as AP-SRS resource Set 0 for the 1st cell, AP-SRS resource Set 1 for the 2nd cell, AP-SRS resource Set 2 for the 3rd cell, and AP-SRS resource Set 3 for the 4th cell, and if it is 0001, it can be interpreted as AP-SRS resource Set 1 for the 1st cell, AP-SRS resource Set 2 for the 2nd cell, AP-SRS resource Set 3 for the 3rd cell, and AP-SRS resource Set 0 for the 4th cell. Specifically, the base station can indicate information of three co-scheduled cells to the terminal in DCI format 0_3 and / or DCI format 1_3 for MC-DCI. Here, if the terminal receives the value 0111 as in Table 21, it can determine that the indicated cell 0, cell 1, and cell 3 are indicated as co-scheduled cells. That is, if the terminal confirms 0111 as information of co-scheduled cells from the DCI, it can determine that cell 0, cell 1, and cell 3 are indicated as co-scheduled cells. In this way, when three cells are indicated and are determined or set in an increasing pattern (0 / 1 / 2 / 3), the base station can allocate the first two bits of the three cells, cell 0 and / or cell 1, as references, and the remaining two bits thereafter can be allocated as references for cell 2 and / or cell 3, which correspond to the second. For example, the first two bits can be allocated for cell 0, and the remaining two bits thereafter can be allocated for cell 1 and cell 2.Alternatively, the first two bits may be allocated for cell 0 and cell 1, and the remaining two bits may be allocated for cell 2.
[0560] That is, if the SRS request information received by the terminal is 0010, it can be determined that the SRS is transmitted using the SRS resource set in Triggered AP-SRS-resource(s) set 0 in the first cell (cell 0) linked to the cell (e.g., cell 0 and / or cell 1) for the first 2 bits, the SRS resource set in Triggered AP-SRS-resource(s) set 1 is used in the second cell (cell 1) linked to the cell (e.g., cell 0 and / or cell 1) for the first 2 bits, and the SRS resource set in Triggered AP-SRS-resource(s) set 2 is used in the cell (e.g., cell 3) for the second 2 bits.
[0561] For the 4 bits of SRS request information, if we distinguish between the MSB 2 bits and the LSB 2 bits, each 2 bits can indicate as follows. For example, let's assume that it is set in ascending order.
[0562] If MSB is 00, AP-SRS resource Set 0 for the 1st cell and AP-SRS resource Set 1 for the 2nd cell
[0563] If MSB is 01, AP-SRS resource Set 1 for the 1st cell and AP-SRS resource Set 2 for the 2nd cell
[0564] If MSB is 10, AP-SRS resource Set 2 for the 1st cell and AP-SRS resource Set 3 for the 2nd cell
[0565] If MSB is 11, AP-SRS resource Set 3 for the 1st cell and AP-SRS resource Set 0 for the 2nd cell
[0566] If LSB is 00, AP-SRS resource set 0 for 3rd cell
[0567] If LSB is 01, AP-SRS resource set 1 for 3rd cell
[0568] If LSB is 10, AP-SRS resource set 2 for 3rd cell
[0569] If LSB is 11, AP-SRS resource Set 3 for 3rd cell
[0570] The above-described embodiment describes an embodiment based on one increasing pattern or rule, and can be extended and applied to various other patterns or rules.
[0571] In another embodiment, the range of values of the table indicated in the SRS request field in DCI format 0_3 / 1_3 for multi-carrier may be instructed not to match the range of values of the SRS request field in DCI format 0_1 / 1_1. For example, among the 4-bit fields, each bit may be instructed to correspond to an SRS resource set LIST ID. For example, if there are 4 co-scheduled cells and 4 bits are 0000, each bit of the 4 bits may correspond / map to the co-scheduled cells in ascending order. For example, if the value of each field is 0, it may be determined that it is mapped to an even ID, such as SRS resource set LIST ID 0 or SRS resource set LIST IDs 0 and 2. Conversely, if the value of each field is 1, it can be determined that it is mapped to an odd ID, such as SRS resource set LIST ID 1 or SRS resource set LIST ID 1 and 3. Whether only one ID or both IDs are indicated above can be distinguished depending on whether the number of co-scheduled cells is 2 or less or 3 or more.
[0572] According to the various embodiments described above, up to two SRS resource set IDs among the SRS resource set IDs set in RRC can be indicated to correspond to SRS request information in MC-DCI. Accordingly, up to two pairs of co-scheduled cells, which are up to four cells, can be designated as SRS resource set IDs.
[0573] Hereinafter, a method of additionally utilizing the MAC-CE message to supplement the flexibility in terms of the base station instructing the terminal to transmit SRS will be described. That is, the MAC CE message can be utilized to supplement the scalability between the base station and the terminal. According to one embodiment of the present disclosure, SRS resources can be indicated based on RRC and DCI (RRC and DCI based joint indication) and / or SRS resources can be indicated based on RRC, MAC CE and DCI (RRC, MAC CE and DCI based joint indication). The description of one embodiment of the present disclosure described above is an embodiment in which SRS resources are indicated based on DCI, and the following describes an embodiment in which SRS resources are indicated based on RRC, MAC CE and DCI. The following embodiment can be applied in combination with the above-described embodiment of the present disclosure.
[0574] FIG. 16 is a diagram illustrating an example of a MAC-CE message for indicating multiple cells and SRS requests in MC-DCI according to one embodiment of the present disclosure.
[0575] Referring to FIG. 16, examples (1600, 1620, 1640) of the structure / form of a MAC CE according to an embodiment of the present disclosure are described. According to an embodiment of the present disclosure, a form (1600, 1620, 1640) of a MAC CE message capable of updating an SRS resource set while properly corresponding to the number of co-scheduled cells for an SRS resource set resource set in RRC can be provided.
[0576] To indicate an SRS request for MC-DCI, the MAC CE message transmitted by the base station may include at least one of the following information.
[0577] First, the MAC CE message can include a BWP ID for the uplink to configure the SRS resource set. Here, the BWP ID is basically composed of four, and 2 bits can be allocated for this. A 2-bit field indicating one of the four BWP IDs can be included / allocated in the MAC CE. The BWP ID can be the UL BWP for SRS transmission.
[0578] Second, the MAC CE message may include an ID corresponding to the configuration of co-scheduled cells established by the RRC configuration. An example of an ID corresponding to the configuration of co-scheduled cells can be referred to Table 21, and the ID included in the MAC CE message can be interpreted according to the table.
[0579] Third, the MAC-CE message can include the number of co-scheduled cells. Information about the number of co-scheduled cells can be used to identify the configuration or setting of information within the MAC CE. For example, the location of a field for resource mapping (e.g., the start and end of the field) within the MAC CE can be identified based on the number of co-scheduled cells. For example, a 2-bit field for indicating the number of cells to be updated can be included / allocated in the MAC CE. For example, if 2 cells are updated in the MAC-CE, if 3 cells are updated in the MAC-CE, and if 4 cells are updated in the MAC-CE, each can be mapped to 00, 01, 10, and 11, and the remaining cases can be left blank in the reserved form or omitted if unnecessary.
[0580] Fourth, the MAC-CE message may contain at least some resource ids among the Triggered AP-SRS-resource(s) set in the RRC configuration. And / or may contain at least some set ids among the Triggered AP-SRS-resource.
[0581] For example, referring to FIGS. 16A to D, when a terminal receives a MAC-CE message while checking the number of specific BWP IDs, co-scheduled cell IDs, and the number of co-scheduled cells in the RRC settings, the terminal can check the set of co-scheduled cells according to the co-scheduled cell ID and set an SRS resource set ID corresponding to each cell.
[0582] For example, referring to FIGS. 16A and 16D, when the co-scheduled cell ID is 0010, the MAC CE message may include up to 16 SRS resource set IDs (SRS request fields: 0000 to 1111) that commonly correspond to cell 0 and cell 3. After receiving the MAC-CE, the terminal may check the information of the MC-DCI including the SRS request field described above, and transmit the SRS based on the resource corresponding to the common SRS resource set ID indicated by the SRS request information. For example, referring back to the description of FIG. 14A, in the case of RRC and DCI-based indication, for example, when the SRS request field in the DCI is 0000, it can be understood that Triggered AP-SRS-resource set 0 is indicated for the first cell, and Triggered AP-SRS-resource set 0 is indicated for the second cell. On the other hand, in case of RRC, MAC CE and DCI based indication, i.e., when a MAC CE is received that updates an SRS resource set, the SRS request field in the DCI may be interpreted as the information updated by the MAC CE, rather than as interpreted in FIG. 14A. For example, if an SRS resource set ID for an SRS request field value of 0000 for cell 0 and cell 3 is indicated in the MAC CE, and then an SRS request field indicating cell 0 and cell 3 as co-scheduled cells and indicating 0000 is received in the DCI, the SRS request field may be interpreted as the SRS resource set ID indicated in the MAC CE.
[0583] As another example, referring to FIGS. 16B and 16D, when the co-scheduled cell id is 0010 (e.g., number of scheduled cells = 2), the MAC CE message may include up to 16 SRS resource set IDs corresponding to cell 0 and up to 16 SRS resource set IDs corresponding to cell 3 (SRS request field: 0000 to 1111). After receiving the MAC-CE, the terminal may check the information of the MC-DCI including the SRS request field described above, and transmit the SRS based on the MAC-CE message configuration information with the first SRS resource set ID and the second SRS resource set ID corresponding to the value indicated by the SRS request information. For example, referring back to the description of FIG. 14B, in case of RRC and DCI based indications, for example, when the SRS request field in the DCI is 0000, it can be understood that Triggered AP-SRS-resource set 0 is indicated for the first cell and the second cell, and Triggered AP-SRS-resource set 0 is indicated for the third cell. On the other hand, in case of RRC, MAC CE and DCI based indications, i.e., when a MAC CE that updates the SRS resource set is received, the SRS request field in the DCI may be interpreted as information updated by the MAC CE, not as in FIG. 14B.For example, if an SRS resource set ID for SRS request field value 0000 for cell 0 and cell 1 and an SRS resource set ID for SRS request field value 0000 for cell 3 are indicated in the MAC CE, and then an SRS request field indicating cell 0, cell 1, and cell 3 as co-scheduled cells and indicating 0000 is received in the DCI, the SRS request field can be interpreted as the SRS resource set ID indicated in the MAC CE.
[0584] As another example, referring to FIGS. 16C and 16D, the MAC CE message may include a total of 64 SRS resource set IDs, up to 16 each corresponding to cell 0, cell 1, cell 2, and cell 3, when the co-scheduled cell ID is 1010 (e.g., number of scheduled cells = 4). After receiving the MAC-CE, the terminal may check the information of the MC-DCI including the SRS request field described above, and transmit the SRS based on the MAC-CE message configuration information with the first to fourth SRS resource set IDs corresponding to the values indicated by the SRS request information. For example, referring back to the description of FIG. 15A, in case of RRC and DCI based indications, for example, when the SRS request field in the DCI is 0000, it can be understood that Triggered AP-SRS-resource set 0 is indicated for the first cell and the second cell, and Triggered AP-SRS-resource set 0 is indicated for the third cell and the fourth cell. On the other hand, in case of RRC, MAC CE and DCI based indications, i.e., when a MAC CE that updates the SRS resource set is received, the SRS request field in the DCI may be interpreted as information updated by the MAC CE, not as in FIG. 15A.For example, if an SRS resource set ID for SRS request field value 0000 for cell 0 and cell 1 and an SRS resource set ID for SRS request field value 0000 for cell 2 and cell 3 are indicated in the MAC CE, and then an SRS request field indicating cell 0, cell 1, cell 2, and cell 3 as co-scheduled cells and indicating 0000 is received in the DCI, the SRS request field can be interpreted as the SRS resource set ID indicated in the MAC CE.
[0585] FIG. 17 is a diagram illustrating the operation of a terminal according to one embodiment of the present disclosure. Various modifications may be made to the method illustrated in the flowchart of FIG. 17. For example, although illustrated as a series of steps, the various steps in each diagram may overlap, occur in parallel, occur in different orders, or occur multiple times. In other examples, steps may be omitted or replaced with other steps.
[0586] In step 1700, the terminal may report terminal capabilities (or terminal capabilities) to the base station. At this time, the terminal capabilities that the terminal may report to the base station may include at least one of the following information: whether to support at least one of the number of cell sets that can be scheduled via MC-DCI, the maximum number of cells per cell set, the maximum number of SRS resources (sets), and whether to support at least one MAC-CE in FIG. 16. In addition, if the terminal has previously reported terminal capabilities to the base station or terminal capability reporting is not required, step 1700 may be omitted.
[0587] In step 1705, the terminal may receive upper layer signaling from the base station. Information transmitted via the upper layer signaling may include at least one of information from a table including one or more cell indexes included in a cell set, cell scheduling information and / or SRS resource (set) information within each cell set that can be scheduled via MC-DCI, and information on whether at least one MAC-CE among FIG. 16 is supported.
[0588] In step 1710, the terminal may receive a MAC-CE from the base station. At this time, the MAC-CE that the terminal may receive from the base station may be a MAC-CE that links and activates information of the SRS request field included in DCI formats 0_3 and 1_3 within each BWP within each cell in which the terminal may be scheduled via MC-DCI, and may be, for example, at least one piece of information that constitutes the MAC-CE in FIG. 16. If the embodiments of FIG. 14 and FIG. 15 do not require a MAC-CE, this step may be omitted.
[0589] In step 1715, the terminal may configure each code point of the co-scheduled cells and / or SRS request field in the MC-DCI based on the information received from the base station. In addition, the terminal may assume that the base station will also configure each code point of the co-scheduled cells and / or SRS request field in the MC-DCI in the same manner.
[0590] At step 1720, the terminal may receive MC-DCI from the base station. At this time, the MC-DCI may include scheduling information for one or more cells and an SRS request field.
[0591] At step 1725, the terminal may transmit SRS signals for multiple cells based on scheduling information in the MC-DCI received from the base station.
[0592] FIG. 18 is a diagram illustrating the operation of a base station according to one embodiment of the present disclosure. Various modifications may be made to the method illustrated in the flowchart of FIG. 18. For example, although illustrated as a series of steps, the various steps in each diagram may overlap, occur in parallel, occur in different orders, or occur multiple times. In other examples, steps may be omitted or replaced with other steps.
[0593] In step 1800, the base station may receive terminal capability (or terminal capability) from the terminal. At this time, the terminal capability that the terminal may report to the base station may include at least one of the following information: the number of cell sets that can be scheduled via MC-DCI, the maximum number of cells per cell set, the maximum number of SRS resources (sets), and whether at least one MAC-CE in FIG. 16 is supported. In addition, if the base station has previously received terminal capability or if terminal capability reporting is not required, step 1800 may be omitted.
[0594] In step 1805, the base station may transmit upper layer signaling to the terminal. The information transmitted via the upper layer signaling may include at least one of information from a table including one or more cell indexes included in a cell set, cell scheduling information and / or SRS resource (set) information within each cell set that can be scheduled via MC-DCI, and information on whether at least one MAC-CE of FIG. 16 is supported.
[0595] In step 1810, the base station may transmit a MAC-CE to the terminal. At this time, the MAC-CE that the terminal may receive from the base station may be a MAC-CE that links and activates information of the SRS request field included in DCI formats 0_3 and 1_3 within each BWP within each cell in which the terminal may be scheduled via MC-DCI, and may be, for example, at least one piece of information that constitutes the MAC-CE in FIG. 16. If the embodiments of FIG. 14 and FIG. 15 do not require a MAC-CE, this step may be omitted.
[0596] In step 1815, the base station may configure each code point of the co-scheduled cells and / or SRS request field in the MC-DCI based on the information transmitted to the terminal. In addition, the base station may assume that the terminal will also configure each code point of the co-scheduled cells and / or SRS request field in the same manner.
[0597] At step 1820, the base station may transmit MC-DCI to the terminal. At this time, the MC-DCI may include scheduling information for one or more cells and an SRS request field.
[0598] At step 1825, the base station can receive SRS signals for multiple cells based on scheduling information in the MC-DCI transmitted to the terminal.
[0599] FIG. 19 is a diagram illustrating the operation of a terminal according to one embodiment of the present disclosure. Various modifications may be made to the method illustrated in the flowchart of FIG. 19. For example, although illustrated as a series of steps, the various steps in each drawing may overlap, occur in parallel, occur in different orders, or occur multiple times. In other examples, steps may be omitted or replaced with other steps.
[0600] At step 1910, the terminal may receive information about SRS (sounding reference signal) resource configuration through an RRC message or higher layer signaling.
[0601] At step 1920, the terminal can receive a MAC CE. The operation of receiving the MAC CE may be omitted.
[0602] At step 1930, the terminal may receive downlink control information (DCI) scheduling multiple cells. The DCI may include an SRS request field.
[0603] In step 1940, the terminal can transmit an SRS. According to one embodiment, the terminal can identify a plurality of SRS resources for a plurality of cells based on information about SRS resource configuration and a code point of an SRS request field, and can transmit an SRS for the plurality of cells based on the identified plurality of SRS resources. According to one embodiment, the code point of the SRS request field can indicate a mapping relationship between one or more SRS resource sets included in the SRS resource configuration and the plurality of cells, and the SRS resource for each cell can be included in an SRS resource set corresponding to each cell.
[0604] If a MAC CE updating a mapping relationship is received in step 1920, the mapping relationship may be identified as being updated by the MAC CE. The MAC CE may include information corresponding to multiple cells and information indicating one or more sets of SRS resources mapped to specific values among code points of the SRS request field.
[0605] For more specific details on the operation of the terminal according to one embodiment of the present disclosure described above, reference may be made to the description of one embodiment of the present disclosure described above.
[0606] FIG. 20 is a diagram illustrating the operation of a base station according to one embodiment of the present disclosure. Various modifications may be made to the method illustrated in the flowchart of FIG. 20. For example, although illustrated as a series of steps, the various steps in each diagram may overlap, occur in parallel, occur in different orders, or occur multiple times. In other examples, steps may be omitted or replaced with other steps.
[0607] At step 2010, the base station may transmit information about sounding reference signal (SRS) resource configuration via an RRC message or higher layer signaling.
[0608] In step 2020, the base station can receive a MAC CE. The operation of transmitting the MAC CE can be omitted.
[0609] At step 2030, the base station may transmit downlink control information (DCI) scheduling multiple cells. The DCI may include an SRS request field.
[0610] In step 2040, the base station can receive an SRS. According to one embodiment, the base station can receive an SRS for a plurality of cells based on a plurality of SRS resources. According to one embodiment, the code point of the SRS request field can indicate a mapping relationship between one or more SRS resource sets included in the SRS resource configuration and the plurality of cells, and the SRS resource for each cell can be included in the SRS resource set corresponding to each cell.
[0611] If a MAC CE that updates the mapping relationship is transmitted in step 2020, the mapping relationship may be updated by the MAC CE. The MAC CE may include information corresponding to multiple cells and information indicating one or more sets of SRS resources mapped to specific values among code points of the SRS request field.
[0612] For more specific details on the operation of the base station according to one embodiment of the present disclosure described above, reference may be made to the description of one embodiment of the present disclosure described above.
[0613] FIG. 21 is a diagram illustrating the structure of a terminal in a wireless communication system according to one embodiment of the present disclosure.
[0614] 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.
[0615] A transceiver unit can transmit and receive signals to and from a base station. 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 merely one embodiment of the transceiver unit, and the components of the transceiver unit are not limited to the RF transmitter and RF receiver.
[0616] 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.
[0617] 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.
[0618] 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 component control operations of the terminal by executing programs stored in memory.
[0619] 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.
[0620] 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.
[0621] The transceiver can transmit and receive signals with the terminal. Here, the signals may include control information and data. To this end, the transceiver may be configured with 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, and the components of the transceiver are not limited to the RF transmitter and RF receiver.
[0622] 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.
[0623] 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.
[0624] The processor can control a series of processes to enable the base station to operate according to the aforementioned embodiments of the present disclosure. 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.
[0625] 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.
[0626] 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 embodiments described in the claims or specification of the present disclosure.
[0627] 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.
[0628] 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 implementing 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 implementing an embodiment of the present disclosure.
[0629] In the specific embodiments of the present disclosure described above, components included in one embodiment are expressed singularly or plurally, 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 plural may be composed of singular elements, or components expressed in singular may be composed of plural elements.
[0630] Meanwhile, the embodiments of the present disclosure disclosed in this specification and drawings are merely specific examples to easily explain the technical contents of the present disclosure and to help the understanding of 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.
[0631] Meanwhile, the order of description in the drawings explaining the method of the present disclosure does not necessarily correspond to the order of execution, and the order of precedence may be changed or executed in parallel.
[0632] Alternatively, the drawings illustrating the method of the present disclosure may omit some components and include only some components without detracting from the essence of the present disclosure.
[0633] In addition, the method of the present disclosure 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 present disclosure.
[0634] Various embodiments of the present disclosure have been described above. The foregoing description of the present disclosure is for illustrative purposes only, and the embodiments of the present disclosure are not limited to the disclosed embodiments. Those skilled in the art will appreciate that the present disclosure can be readily modified into other specific forms without altering the technical spirit or essential characteristics of the present disclosure. The scope of the present disclosure is indicated by the claims described below rather than the detailed description above, and all changes or modifications derived from the meaning and scope of the claims and their equivalents should be construed as being included within the scope of the present disclosure.
Claims
1. In a method performed by a terminal in a communication system, A step of receiving information on setting up SRS (sounding reference signal) resources through upper layer signaling; A step of receiving downlink control information (DCI) scheduling a plurality of cells, the DCI including an SRS request field; A step of identifying a plurality of SRS resources for the plurality of cells based on information about the SRS resource configuration and a code point of the SRS request field, wherein the code point of the SRS request field indicates a mapping relationship between one or more SRS resource sets included in the SRS resource configuration and the plurality of cells, and the SRS resources for each cell are included in the SRS resource set corresponding to each cell; and A method comprising the step of transmitting an SRS to the plurality of cells based on the plurality of SRS resources.
2. In paragraph 1, The size of the above SRS request field is 4 bits, The 2 MSBs (most significant bits) of the above SRS request field are related to one or more cells among the plurality of cells, The 2 least significant bits (LSBs) of the above SRS request field are related to one or more cells remaining excluding one or more cells among the above multiple cells, A method, wherein each index of said one or more cells associated with said 2 MSBs is less than each index of said one or more cells associated with said 2 LSBs.
3. In paragraph 1, A method wherein the maximum number of the plurality of cells is 4, and the DCI further includes a 4-bit field indicating the plurality of cells.
4. In paragraph 1, The format of the above DCI is DCI format 0_3 or DCI format 1_3, A method wherein an information element (IE) for the size of the SRS request field is received through the upper layer signaling, and the IE is set separately according to the format of the DCI.
5. In paragraph 1, If a MAC CE (medium access control control element) that updates the above mapping relationship is received prior to receiving the DCI, the mapping relationship is identified as having been updated by the MAC CE, A method wherein the MAC CE includes information corresponding to the plurality of cells and information indicating one or more SRS resource sets mapped to specific values among code points of the SRS request field.
6. At the terminal of the communication system, Transmitter and receiver; and comprising one or more processors coupled to the transceiver, the processors comprising: Receive information about SRS (sounding reference signal) resource settings through upper layer signaling; Receive downlink control information (DCI) that schedules multiple cells; The above DCI includes an SRS request field; Identifying a plurality of SRS resources for the plurality of cells based on information about the above SRS resource configuration and a code point of the SRS request field; The code point of the above SRS request field indicates a mapping relationship between one or more SRS resource sets included in the above SRS resource configuration and the plurality of cells, and the SRS resources for each cell are included in the SRS resource set corresponding to each cell; and A terminal configured to transmit SRS for the plurality of cells based on the plurality of SRS resources.
7. In paragraph 6, The size of the above SRS request field is 4 bits, The 2 MSBs (most significant bits) of the above SRS request field are related to one or more cells among the plurality of cells, The 2 least significant bits (LSBs) of the above SRS request field are related to one or more cells remaining excluding one or more cells among the above multiple cells, A terminal, wherein each index of said one or more cells associated with said 2 MSBs is smaller than each index of said one or more cells associated with said 2 LSBs.
8. In a method performed by a base station in a communication system, A step of transmitting information about SRS (sounding reference signal) resource settings through upper layer signaling; A step of transmitting downlink control information (DCI) scheduling a plurality of cells, the DCI including an SRS request field; and A step of transmitting SRS to the plurality of cells based on the plurality of SRS resources, The above multiple SRS resources are based on information about the SRS resource settings and the code points of the SRS request field, The code point of the above SRS request field indicates a mapping relationship between one or more SRS resource sets included in the above SRS resource configuration and the above multiple cells, A method wherein SRS resources for each cell are included in a set of SRS resources corresponding to each cell.
9. In paragraph 8, The size of the above SRS request field is 4 bits, The 2 MSBs (most significant bits) of the above SRS request field are related to one or more cells among the plurality of cells, The 2 least significant bits (LSBs) of the above SRS request field are related to one or more cells remaining excluding one or more cells among the above multiple cells, A method, wherein each index of said one or more cells associated with said 2 MSBs is less than each index of said one or more cells associated with said 2 LSBs.
10. In paragraph 8, A method wherein the maximum number of the plurality of cells is 4, and the DCI further includes a 4-bit field indicating the plurality of cells.
11. In paragraph 8, The format of the above DCI is DCI format 0_3 or DCI format 1_3, A method wherein an information element (IE) for the size of the SRS request field is transmitted through the upper layer signaling, and the IE is set separately according to the format of the DCI.
12. In paragraph 8, If a MAC CE (medium access control control element) that updates the above mapping relationship is transmitted prior to the DCI transmission, the mapping relationship is updated by the MAC CE, A method wherein the MAC CE includes information corresponding to the plurality of cells and information indicating one or more SRS resource sets mapped to specific values among code points of the SRS request field.
13. In the base station of the communication system, Transmitter and receiver; and comprising one or more processors coupled to the transceiver, the processors comprising: Transmitting information about SRS (sounding reference signal) resource settings through upper layer signaling; Transmits downlink control information (DCI) that schedules multiple cells; The above DCI includes an SRS request field; and is configured to transmit SRS to the plurality of cells based on the plurality of SRS resources; The above multiple SRS resources are based on information about the SRS resource settings and the code points of the SRS request field, The code point of the above SRS request field indicates a mapping relationship between one or more SRS resource sets included in the above SRS resource configuration and the above multiple cells, The SRS resources for each cell are included in the set of SRS resources corresponding to each cell, the base station.
14. In paragraph 13, The size of the above SRS request field is 4 bits, The 2 MSBs (most significant bits) of the above SRS request field are related to one or more cells among the plurality of cells, The 2 least significant bits (LSBs) of the above SRS request field are related to one or more cells remaining excluding one or more cells among the above multiple cells, A base station, wherein each index of said one or more cells associated with said 2 MSBs is less than each index of said one or more cells associated with said 2 LSBs.
15. In paragraph 13, A base station, wherein the maximum number of the plurality of cells is 4, and the DCI further includes a 4-bit field indicating the plurality of cells.
Citation Information
Patent Citations
CLI measurement reference signal configuration method and device, CLI measurement reference signal transceiving method and device, medium and equipment
CN111417199A
Apparatus and method for transmitting sounding reference signal, and transmission indicating apparatus and method using the same
KR1020130018074A
Beverage maker and control method of the same
KR1020210149528A
Control signaling for uplink multiple input multiple output, channel state information reference signal configuration and sounding reference signal configuration
US20190174466A1
KR20220141831A
