CN116806415A - Method and device for reporting channel state information through repeated uplink data transmission in network cooperative communication - Google Patents
Method and device for reporting channel state information through repeated uplink data transmission in network cooperative communication Download PDFInfo
- Publication number
- CN116806415A CN116806415A CN202280013082.6A CN202280013082A CN116806415A CN 116806415 A CN116806415 A CN 116806415A CN 202280013082 A CN202280013082 A CN 202280013082A CN 116806415 A CN116806415 A CN 116806415A
- Authority
- CN
- China
- Prior art keywords
- terminal
- pusch
- repetition
- dci
- srs
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 317
- 238000004891 communication Methods 0.000 title claims abstract description 127
- 230000005540 biological transmission Effects 0.000 title abstract description 838
- 230000003213 activating effect Effects 0.000 claims description 19
- 230000004044 response Effects 0.000 claims description 14
- 238000005516 engineering process Methods 0.000 abstract description 17
- 230000006872 improvement Effects 0.000 abstract description 3
- 230000006855 networking Effects 0.000 abstract 1
- 230000011664 signaling Effects 0.000 description 163
- 230000008859 change Effects 0.000 description 91
- 230000006870 function Effects 0.000 description 57
- 238000013468 resource allocation Methods 0.000 description 57
- 238000013507 mapping Methods 0.000 description 50
- 238000012545 processing Methods 0.000 description 41
- 238000012544 monitoring process Methods 0.000 description 33
- 230000001052 transient effect Effects 0.000 description 27
- 230000015654 memory Effects 0.000 description 26
- LKKMLIBUAXYLOY-UHFFFAOYSA-N 3-Amino-1-methyl-5H-pyrido[4,3-b]indole Chemical compound N1C2=CC=CC=C2C2=C1C=C(N)N=C2C LKKMLIBUAXYLOY-UHFFFAOYSA-N 0.000 description 24
- 230000000737 periodic effect Effects 0.000 description 21
- 230000008569 process Effects 0.000 description 19
- 230000004913 activation Effects 0.000 description 16
- 230000008054 signal transmission Effects 0.000 description 16
- 238000002360 preparation method Methods 0.000 description 15
- 238000005259 measurement Methods 0.000 description 14
- 102100031413 L-dopachrome tautomerase Human genes 0.000 description 13
- 101710093778 L-dopachrome tautomerase Proteins 0.000 description 13
- 238000003860 storage Methods 0.000 description 13
- 230000002776 aggregation Effects 0.000 description 12
- 238000004220 aggregation Methods 0.000 description 12
- 230000001960 triggered effect Effects 0.000 description 11
- 125000004122 cyclic group Chemical group 0.000 description 10
- 238000007726 management method Methods 0.000 description 10
- 238000012384 transportation and delivery Methods 0.000 description 10
- 101150006914 TRP1 gene Proteins 0.000 description 9
- LVTKHGUGBGNBPL-UHFFFAOYSA-N Trp-P-1 Chemical compound N1C2=CC=CC=C2C2=C1C(C)=C(N)N=C2C LVTKHGUGBGNBPL-UHFFFAOYSA-N 0.000 description 9
- 230000001427 coherent effect Effects 0.000 description 8
- 238000010295 mobile communication Methods 0.000 description 7
- 238000012986 modification Methods 0.000 description 7
- 230000004048 modification Effects 0.000 description 7
- 238000004590 computer program Methods 0.000 description 6
- 230000009977 dual effect Effects 0.000 description 5
- 101710163881 5,6-dihydroxyindole-2-carboxylic acid oxidase Proteins 0.000 description 4
- 241000760358 Enodes Species 0.000 description 4
- 235000008694 Humulus lupulus Nutrition 0.000 description 4
- 101710141933 Single-stranded DNA-binding protein 1 Proteins 0.000 description 4
- 102000003627 TRPC1 Human genes 0.000 description 4
- 230000008901 benefit Effects 0.000 description 3
- 230000001413 cellular effect Effects 0.000 description 3
- 239000013256 coordination polymer Substances 0.000 description 3
- 238000001514 detection method Methods 0.000 description 3
- 230000000694 effects Effects 0.000 description 3
- 230000003287 optical effect Effects 0.000 description 3
- 238000001228 spectrum Methods 0.000 description 3
- 230000006978 adaptation Effects 0.000 description 2
- 239000000969 carrier Substances 0.000 description 2
- 238000012937 correction Methods 0.000 description 2
- 238000013461 design Methods 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- 230000018109 developmental process Effects 0.000 description 2
- 230000004927 fusion Effects 0.000 description 2
- 230000007774 longterm Effects 0.000 description 2
- 239000011159 matrix material Substances 0.000 description 2
- 230000011218 segmentation Effects 0.000 description 2
- 241000282412 Homo Species 0.000 description 1
- 230000002411 adverse Effects 0.000 description 1
- 230000004931 aggregating effect Effects 0.000 description 1
- 230000004075 alteration Effects 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 230000000903 blocking effect Effects 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 230000015556 catabolic process Effects 0.000 description 1
- 230000006835 compression Effects 0.000 description 1
- 238000007906 compression Methods 0.000 description 1
- 230000008878 coupling Effects 0.000 description 1
- 238000010168 coupling process Methods 0.000 description 1
- 238000005859 coupling reaction Methods 0.000 description 1
- 230000006837 decompression Effects 0.000 description 1
- 238000006731 degradation reaction Methods 0.000 description 1
- 238000003780 insertion Methods 0.000 description 1
- 230000037431 insertion Effects 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 239000013307 optical fiber Substances 0.000 description 1
- 230000002441 reversible effect Effects 0.000 description 1
- 230000007704 transition Effects 0.000 description 1
Landscapes
- Mobile Radio Communication Systems (AREA)
Abstract
The present disclosure relates to a communication technology and system thereof for converged internet of things (IoT) technology and 5G communication systems to support higher data transmission rates than 4G systems. The present disclosure may be applied to smart services (e.g., smart home, smart building, smart city, smart car or networking car, healthcare, digital education, retail business, security and security related services, etc.) based on 5G communication technology and IoT related technology. The present disclosure provides a coverage improvement method for a PDCCH in a wireless communication system.
Description
Technical Field
The present disclosure relates to operation of terminals and base stations in a wireless communication system. In particular, the present disclosure relates to a method for reporting channel state information by repeating uplink data transmission in network cooperative communication, and an apparatus capable of performing the method in a wireless communication system.
Background
In order to meet the increasing demand for wireless data services and the increasing multimedia services since the deployment of 4G communication systems, efforts have been made to develop an improved 5G or front 5G communication system. Thus, the 5G or former 5G communication system is also referred to as a "super 4G network" communication system or a "LTE-after" system. Consider implementing a 5G communication system in the ultra-high frequency (millimeter wave) band (e.g., 60GHz band) in order to increase data rates. In order to reduce propagation loss of radio waves and increase transmission distance in ultra-high frequency bands, beamforming, massive multiple input multiple output (massive MIMO), full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, massive antenna techniques are discussed in 5G communication systems. In addition, in the 5G communication system, development of system network improvement is being conducted based on advanced small cells, cloud radio access networks (cloud RANs), ultra dense networks, device-to-device (D2D) communication, wireless backhaul, mobile networks, cooperative communication, coordinated multipoint (CoMP), reception-side interference cancellation, and the like. Hybrid FSK and QAM modulation (FQAM) and Sliding Window Superposition Coding (SWSC) as Advanced Code Modulation (ACM) and Filter Bank Multicarrier (FBMC), non-orthogonal multiple access (NOMA) and Sparse Code Multiple Access (SCMA) as advanced access techniques have also been developed in 5G systems.
The internet, which is an artificially centric connected network in which humans generate and consume information, is now evolving into the internet of things (IoT) in which distributed entities such as things exchange and process information without human intervention. Internet of everything (IoE) has emerged as a combination of IoT technology and big data processing technology through connections with cloud servers. As IoT implementations require technical elements such as "sensing technology," "wired/wireless communication and network infrastructure," "service interface technology," and "security technology," sensor networks, machine-to-machine (M2M) communications, machine Type Communications (MTC), etc. have recently been investigated. Such IoT environments may provide intelligent internet technology services that create new value for human life by collecting and analyzing data generated among connections. IoT may be applied in a variety of fields including smart homes, smart buildings, smart cities, smart cars or networked cars, smart grids, healthcare, smart appliances, and advanced healthcare through fusion and combination between existing Information Technology (IT) and various industrial applications.
In keeping with this, various attempts have been made to apply 5G communication systems to IoT networks. For example, techniques such as sensor networks, machine Type Communications (MTC), and machine-to-machine (M2M) communications may be implemented by beamforming, MIMO, and array antennas. The application of cloud radio access networks (cloud RANs) as the big data processing technology described above may also be considered as an example of a fusion of 5G technology with IoT technology.
With the development of the wireless communication system as described above, various services can be provided, and thus a scheme of smoothly providing these services is required.
The above information is presented merely as background information to aid in the understanding of the present disclosure. No determination has been made, nor has an assertion made, as to whether any of the above can be applied as prior art to the present disclosure.
Disclosure of Invention
Technical problem
Embodiments disclosed herein provide an apparatus and method for efficiently providing a service in a mobile communication system.
Problem solution
According to one aspect of the present disclosure, a method performed by a terminal in a communication system is provided. The method includes receiving a configuration of a Physical Uplink Shared Channel (PUSCH) repetition type B from a base station; receiving Downlink Control Information (DCI) from a base station, the DCI scheduling an aperiodic Channel State Information (CSI) report or activating a semi-persistent CSI report on a PUSCH, the DCI including a first Sounding Reference Signal (SRS) resource indicator field associated with a first SRS resource set and a second SRS resource indicator field associated with a second SRS resource set; identifying nominal repetition and actual repetition of the PUSCH according to the PUSCH repetition type B; and transmitting a CSI report on the PUSCH to the base station according to PUSCH repetition type B, wherein in a case where the PUSCH is transmitted together with the transport block, the CSI report is transmitted on the first actual repetition associated with the SRS resource set and the first actual repetition associated with the second SRS resource set in response to the first actual repetition associated with the first SRS resource set and the first actual repetition associated with the second SRS resource set having the same number of symbols.
According to another aspect of the present disclosure, a method performed by a base station in a communication system is provided. The method includes transmitting a configuration of a Physical Uplink Shared Channel (PUSCH) repetition type B to a terminal; transmitting Downlink Control Information (DCI) to the terminal, the DCI scheduling an aperiodic Channel State Information (CSI) report or activating a semi-persistent CSI report on a PUSCH, the DCI including a first Sounding Reference Signal (SRS) resource indicator field associated with a first SRS resource set and a second SRS resource indicator field associated with a second SRS resource set; and receiving a CSI report on a PUSCH from the terminal according to a PUSCH repetition type B, wherein the CSI report is received on the first actual repetition associated with the SRS resource set and the first actual repetition associated with the second SRS resource set in response to the first actual repetition associated with the first SRS resource set and the first actual repetition associated with the second SRS resource set having the same number of symbols in a case where the PUSCH is received together with the transport block.
According to another aspect of the present disclosure, a terminal in a communication system is provided. The terminal includes a transceiver, and a controller configured to: receiving a configuration of a Physical Uplink Shared Channel (PUSCH) repetition type B from a base station; receiving Downlink Control Information (DCI) from a base station, the DCI scheduling an aperiodic Channel State Information (CSI) report or activating a semi-persistent CSI report on a PUSCH, the DCI including a first Sounding Reference Signal (SRS) resource indicator field associated with a first SRS resource set and a second SRS resource indicator field associated with a second SRS resource set; identifying nominal repetition and actual repetition of the PUSCH according to the PUSCH repetition type B; and transmitting a CSI report on a PUSCH to the base station according to PUSCH repetition type B, wherein the CSI report is transmitted on the first actual repetition associated with the SRS resource set and the first actual repetition associated with the second SRS resource set in response to the first actual repetition associated with the first SRS resource set and the first actual repetition associated with the second SRS resource set having the same number of symbols in a case where the PUSCH is transmitted together with the transport block.
According to another aspect of the present disclosure, a base station in a communication system is provided. The base station includes a transceiver; and a controller configured to: transmitting a configuration of a Physical Uplink Shared Channel (PUSCH) repetition type B to a terminal; transmitting Downlink Control Information (DCI) to the terminal, the DCI scheduling an aperiodic Channel State Information (CSI) report or activating a semi-persistent CSI report on a PUSCH, the DCI including a first Sounding Reference Signal (SRS) resource indicator field associated with a first SRS resource set and a second SRS resource indicator field associated with a second SRS resource set; and receiving a CSI report on a PUSCH from the terminal according to a PUSCH repetition type B, wherein the CSI report is received on the first actual repetition associated with the SRS resource set and the first actual repetition associated with the second SRS resource set in response to the first actual repetition associated with the first SRS resource set and the first actual repetition associated with the second SRS resource set having the same number of symbols in a case where the PUSCH is received together with the transport block.
Other aspects, advantages, and salient features of the disclosure will become apparent to those skilled in the art from the following detailed description, which, taken in conjunction with the annexed drawings, discloses various embodiments of the disclosure.
Drawings
The foregoing and other aspects, features, and advantages of certain embodiments of the disclosure will become more apparent from the following description, taken in conjunction with the accompanying drawings, in which:
fig. 1 illustrates a basic structure of a time-frequency domain in a wireless communication system according to an embodiment of the present disclosure;
fig. 2 illustrates a structure including frames, subframes, and slots in a wireless communication system according to an embodiment of the present disclosure;
fig. 3 shows an example of a configuration of a bandwidth part in a wireless communication system according to an embodiment of the present disclosure;
fig. 4 illustrates an example of a configuration of a control region of a downlink control channel in a wireless communication system according to an embodiment of the present disclosure;
fig. 5A illustrates a structure of a downlink control channel in a wireless communication system according to an embodiment of the present disclosure;
fig. 5B illustrates, by span, a case in which a terminal may have a plurality of PDCCH monitoring occasions in a slot in a wireless communication system according to an embodiment of the present disclosure;
fig. 6 illustrates an example of DRX operation in a wireless communication system according to an embodiment of the present disclosure;
fig. 7 illustrates an example of base station beam allocation configured according to TCI status in a wireless communication system according to an embodiment of the present disclosure;
Fig. 8 illustrates an example of a TCI state allocation method for a PDCCH in a wireless communication system according to an embodiment of the present disclosure;
fig. 9 illustrates a TCI indication MAC CE signaling structure for PDCCH DMRS in a wireless communication system according to an embodiment of the present disclosure;
fig. 10 illustrates an example of a configuration of a control resource set and a search space beam in a wireless communication system according to an embodiment of the present disclosure;
fig. 11 illustrates a method for transmitting or receiving data by a base station and a terminal considering a downlink data channel and rate matching resources in a wireless communication system according to an embodiment of the present disclosure;
fig. 12 illustrates a method for selecting an acceptable set of control resources in consideration of priority when a terminal receives a downlink control channel in a wireless communication system according to an embodiment of the present disclosure;
fig. 13 illustrates an example of an aperiodic CSI reporting method according to an embodiment of the present disclosure;
fig. 14 illustrates an example of frequency domain resource allocation of PDSCH in a wireless communication system according to an embodiment of the disclosure;
fig. 15 illustrates an example of allocating time domain resources of a PDSCH in a wireless communication system according to an embodiment of the disclosure;
fig. 16A illustrates an example of allocating time domain resources according to subcarrier spacing of a data channel and a control channel in a wireless communication system according to an embodiment of the present disclosure;
Fig. 16B illustrates an example of a repeated PUSCH transmission type B in a wireless communication system according to an embodiment of the disclosure;
fig. 17 illustrates a radio protocol structure of a base station and a terminal in a single cell, carrier aggregation, and dual connectivity case in a wireless communication system according to an embodiment of the present disclosure;
fig. 18 illustrates an example of antenna port configuration and resource allocation for cooperative communication in a wireless communication system in accordance with an embodiment of the present disclosure;
fig. 19 illustrates an example of a Downlink Control Information (DCI) configuration for cooperative communication in wireless communication according to an embodiment of the present disclosure;
fig. 20 illustrates base station and terminal operations for repeating PUSCH transmission, taking into account multiple TRPs based on transmission of a single DCI in which multiple SRI or TPMI fields are present, according to an embodiment of the present disclosure;
fig. 21 illustrates an operation of a terminal considering a third embodiment of the present disclosure;
fig. 22 illustrates an operation of a base station considering a third embodiment of the present disclosure;
fig. 23 illustrates an operation of a terminal considering a fourth embodiment of the present disclosure;
fig. 24 illustrates an operation of a base station considering a fourth embodiment of the present disclosure;
fig. 25 shows an example of a structure of a terminal in a wireless communication system according to an embodiment of the present disclosure; and
Fig. 26 shows an example of a structure of a base station in a wireless communication system according to an embodiment of the present disclosure.
Detailed Description
Before proceeding with the following detailed description, it may be advantageous to set forth definitions of certain words and phrases throughout this patent document: the terms "include" and "comprise," as well as derivatives thereof, mean inclusion without limitation; the term "or" is inclusive, meaning and/or; the phrases "associated with" and derivatives thereof may mean inclusion, inclusion therein, interconnection therewith, inclusion therein, connection therewith, coupling therewith, communicable therewith, cooperating therewith, interleaving therewith, juxtaposing therewith, approaching therewith, binding thereto or binding therewith, having properties thereof, or the like; the term "controller" means any device, system, or portion thereof that controls at least one operation, such device may be implemented in hardware, firmware, or software, or some combination of at least two of the same. It should be noted that the functionality associated with any particular controller may be centralized or distributed, whether locally or remotely.
Furthermore, the various functions described below may be implemented or supported by one or more computer programs, each of which is formed from computer readable program code and embodied in a computer readable medium. The terms "application" and "program" refer to one or more computer programs, software components, sets of instructions, procedures, functions, objects, classes, instances, related data, or a portion thereof adapted for implementation in a suitable computer readable program code. The phrase "computer readable program code" includes any type of computer code, including source code, object code, and executable code. The phrase "computer readable medium" includes any type of medium capable of being accessed by a computer, such as Read Only Memory (ROM), random Access Memory (RAM), a hard disk drive, a Compact Disc (CD), a Digital Video Disc (DVD), or any other type of memory. "non-transitory" computer-readable media do not include wired, wireless, optical, or other communication links that transmit transitory electrical or other signals. A non-transitory computer readable medium includes a medium that can permanently store data and a medium that can store and later overwrite data, such as a rewritable optical disc or an erasable memory device.
Definitions for certain words and phrases are provided throughout this patent document, those of ordinary skill in the art should understand that in many, if not most instances, such definitions apply to prior, as well as future uses of such defined words and phrases.
Figures 1 through 26, discussed below, and the various embodiments used to describe the principles of the present disclosure in this patent document are by way of illustration only and should not be construed in any way to limit the scope of the disclosure. Those skilled in the art will appreciate that the principles of the present disclosure may be implemented in any suitably arranged system or device.
Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings.
In describing embodiments of the present disclosure, descriptions related to technical contents well known in the art and not directly associated with the present disclosure will be omitted. Such unnecessary description is omitted to prevent obscuring the main idea of the present disclosure and to more clearly convey the main idea.
For the same reason, in the drawings, some elements may be exaggerated, omitted, or schematically shown. Furthermore, the size of each element does not fully reflect the actual size. In the drawings, identical or corresponding elements are provided with identical reference numerals.
For the same reason, in the drawings, some elements may be exaggerated, omitted, or schematically shown. Furthermore, the size of each element does not fully reflect the actual size. In the drawings, identical or corresponding elements are provided with identical reference numerals. Further, in describing the present disclosure, when it is determined that a detailed description of known functions or configurations incorporated herein may unnecessarily obscure the subject matter of the present disclosure, the description will be omitted. The terms to be described below are terms defined in consideration of functions in the present disclosure, and may be different according to users, intention of users, or custom. Accordingly, the definition of the terms should be made based on the contents of the entire specification.
In the following description, a base station is an entity that allocates resources to a terminal, and may be at least one of a eNode B, an eNode B, a node B, a Base Station (BS), a radio access unit, a base station controller, and a node on a network. A terminal may include a User Equipment (UE), a Mobile Station (MS), a cellular phone, a smart phone, a computer, or a multimedia system capable of performing a communication function. In the present disclosure, "Downlink (DL)" refers to a radio link via which a base station transmits signals to a terminal, and "Uplink (UL)" refers to a radio link via which a terminal transmits signals to a base station. Furthermore, in the following description, an LTE or LTE-a system may be described by way of example, but embodiments of the present disclosure may also be applied to other communication systems having similar technical backgrounds or channel types. Examples of such communication systems may include fifth generation mobile communication technologies (5G, new radio and NR) developed outside LTE-a, and in the following description, "5G" may be a concept covering existing LTE, LTE-a or other similar services. In addition, based on the determination by those skilled in the art, embodiments of the present disclosure may also be applied to other communication systems with some modifications without significantly departing from the scope of the present disclosure.
Herein, it will be understood that each block of the flowchart illustrations, and combinations of blocks in the flowchart illustrations, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart block or blocks. These computer program instructions may also be stored in a computer-usable or computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-usable or computer-readable memory produce an article of manufacture including instruction means that implement the function specified in the flowchart block or blocks. The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart block or blocks.
Furthermore, each block of the flowchart illustrations may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order. For example, two blocks shown in succession may in fact be executed substantially concurrently or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved.
As used herein, a "unit" refers to a software element or a hardware element, such as a Field Programmable Gate Array (FPGA) or an Application Specific Integrated Circuit (ASIC), that performs a predetermined function. However, the "unit" does not always have a meaning limited to software or hardware. The "unit" may be structured to be stored in an addressable storage medium or to execute one or more processors. Thus, a "unit" includes, for example, software elements, object-oriented software elements, class elements or task elements, processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuitry, data, databases, data structures, tables, arrays, and parameters. The elements and functions provided by a "unit" may be combined into a smaller number of elements or "units" or divided into a larger number of elements or "units". Furthermore, the elements and "units" may be implemented to render one or more CPUs within a device or secure multimedia card. Further, a "unit" in an embodiment may include one or more processors.
Wireless communication systems have expanded beyond the original role of providing voice-oriented services and have evolved into broadband wireless communication systems that provide high-speed high-quality packet data services in accordance with, for example, communication standards such as high-speed packet access (HSPA), long term evolution (LTE or evolved universal terrestrial radio access (E-UTRA)), LTE-advanced (LTE-a), LTE-Pro of 3GPP, high Rate Packet Data (HRPD) and Ultra Mobile Broadband (UMB) of 3GPP2, and 802.16E of IEEE.
As a representative example of the broadband wireless communication system, in the LTE system, an Orthogonal Frequency Division Multiplexing (OFDM) scheme has been adopted for Downlink (DL) and a single carrier frequency division multiple access (SC-FDMA) scheme has been adopted for Uplink (UL). The uplink indicates a radio link transmitting data or control signals from a terminal (user equipment (UE) or a Mobile Station (MS)) to a base station (eNode B or Base Station (BS)), and the downlink indicates a radio link transmitting data or control signals from the base station to the terminal. In the above multiple access scheme, data or control information is distinguished according to users by allocating or managing time-frequency resources for carrying the data or control information for each user, in general, wherein the time-frequency resources do not overlap, i.e., orthogonality is established.
Future communication systems after LTE, i.e., 5G communication systems, must be able to freely reflect various demands from users, service providers, etc., and thus need to support services that satisfy all of the various demands. Services considered for 5G communication systems include enhanced mobile broadband (emmbb), large-scale machine type communication (mctc), ultra-reliable low-delay communication (URLLC), and the like.
The eMBB is intended to provide a data rate that is better than the data rate supported by existing LTE, LTE-A or LTE-Pro. For example, in a 5G communication system, from the perspective of one base station, an eMBB may provide a peak data rate of 20Gbps in the downlink and 10Gbps in the uplink. In addition, 5G communication systems may be capable of providing not only peak data rates, but also increased user perceived terminal data rates. To meet such requirements, improvements in various transmission and reception techniques may be needed, including further improved Multiple Input Multiple Output (MIMO) transmission techniques. In addition, a transmission bandwidth of up to 20MHz is used in a 2GHz band used by the current LTE to transmit signals, but the 5G communication system uses a bandwidth wider than 20MHz in a frequency band of 3 to 6GHz or higher, thereby satisfying a data rate required in the 5G communication system.
In addition, mctc is being considered to support application services such as internet of things (IoT) in 5G communication systems. mctc needs to support access for a large number of terminals in a cell, enhance coverage of terminals, improve battery time, and reduce cost of terminals in order to efficiently provide IoT. The IoT needs to be able to support a large number of terminals (e.g., 1,000,000 terminals/km 2) in a cell because the IoT attaches to various sensors and devices to provide communication functionality. Furthermore, a terminal supporting mctc is more likely to be located in a shadow area that is not covered by a cell due to the nature of the service, such as a basement of a building, and thus, the terminal may need a wider coverage than other services provided in a 5G communication system. Terminals supporting mctc need to be configured as inexpensive terminals and may require a very long battery life of 10 to 15 years because it is difficult to frequently replace the battery of the terminal.
Finally, URLLC is a cellular-based wireless communication service for mission critical purposes. For example, services for remote control of robots or machines, industrial automation, unmanned aerial vehicles, remote healthcare, emergency alerts, etc. may be considered. Thus, the communication provided by URLLC needs to provide very low latency and very high reliability. For example, services supporting URLLC need to meet an air interface delay of less than 0.5 ms, and may also have 10 -5 % or lower packet error rate. Thus, for services supporting URLLC, 5G systems need to provide smaller Transmission Time Intervals (TTIs) than other services, and design problems may also arise that allocate wider resources in the frequency band to ensure the reliability of the communication link.
The three services of 5G above, namely emmbb, URLLC, and mctc, can be multiplexed and transmitted in a single system. Here, in order to meet different requirements of each service, different transmission or reception techniques and different transmission and reception parameters may be used for the service. The 5G is not limited to the above three services.
[ NR time-frequency resource ]
Hereinafter, a frame structure of the 5G system is described in detail with reference to the accompanying drawings.
Fig. 1 shows a basic structure of a time-frequency domain as a radio resource region for transmitting data or control channels in a 5G system.
In fig. 1, the horizontal axis indicates the time domain, and the vertical axis indicates the frequency domain. The basic unit of resource in the time-frequency domain is a Resource Element (RE) 101, and may be defined as one Orthogonal Frequency Division Multiplexing (OFDM) symbol 102 on the time axis and one subcarrier 103 on the frequency axis. In the frequency domain of the power supply,(e.g., 12) consecutive REs may constitute one Resource Block (RB) 104.
Fig. 2 illustrates a structure including frames, subframes, and slots in a wireless communication system according to an embodiment of the present disclosure.
In fig. 2, an example of a structure including a frame 200, a subframe 201, and a slot 202 is shown. One frame 200 may be defined as 10ms. One subframe 201 may be defined as 1ms, and thus one frame 200 may include a total of 10 subframes 201. One slot 202 or 203 may be defined as 14 OFDM symbols (i.e., the number of symbols per slotOne subframe 201 may include one or more slots 202 and 203, and the number of slots 202 and 203 of each subframe 201 may vary according to a configuration value 204 or 205 of a subcarrier spacing. The example of fig. 2 shows a case where the subcarrier spacing configuration value corresponds to μ=0 (204) and a case where the subcarrier spacing configuration value corresponds to μ=1 (205). In the case of μ=0 (204), one subframe 201 may include one slot 202, and in the case of μ=1 (205), one subframe 201 may include twoTime slot 203. I.e. the number of slots per subframe +.>Can be varied according to the configuration value mu of the subcarrier spacing and accordingly the number of slots per frame +.>And may also vary. Mu is configured according to each subcarrier spacing And
andcan be as follows [ Table 1]]Are shown to be defined.
TABLE 1
Bandwidth portion (BWP)
Next, a configuration of a bandwidth part (BWP) in the 5G communication system is described in detail with reference to the accompanying drawings.
Fig. 3 illustrates an example of a configuration of a bandwidth part in a wireless communication system according to an embodiment of the present disclosure.
Fig. 3 shows an example in which a terminal bandwidth (UE bandwidth) 300 is configured to be divided into two bandwidth parts, namely, a bandwidth part #1 (BWP # 1) 301 and a bandwidth part #2 (BWP # 2) 302. The base station may configure one or more bandwidth parts for the terminal and may configure the following pieces of information for each bandwidth part.
TABLE 2
The present disclosure is not limited to the above examples, and various parameters related to the bandwidth part may be configured for the terminal in addition to the pieces of configuration information described above. These pieces of information may be transmitted by the base station to the terminal through higher layer signaling, such as radio point resource control (RRC) signaling. At least one of the configured bandwidth portion or portions may be activated. Whether the configured bandwidth part is activated or not may be semi-statically transmitted through RRC signaling or dynamically transmitted from the base station to the terminal through Downlink Control Information (DCI).
According to some embodiments, a terminal prior to a Radio Resource Control (RRC) connection may receive a configuration of an initial bandwidth part (initial BWP) for initial access from a base station through a Master Information Block (MIB). More specifically, the terminal may receive configuration information related to a control resource set (CORESET) and a search space through the MIB in an initial access phase, and may transmit a PDCCH for receiving system information (corresponding to remaining system information (RMSI) or system information block 1 (SIB 1)) required for initial access through the configuration information. Each of the control region and the search space configured by the MIB may be regarded as an Identity (ID) 0. The base station may notify the terminal of configuration information such as frequency allocation information, time allocation information, and parameter set (numerology) of the control region #0 through the MIB. In addition, the base station may notify the terminal of configuration information of the monitoring period and timing of the control region #0, i.e., configuration information of the search space #0, through the MIB. The terminal may consider the frequency domain configured as the control region #0 obtained from the MIB as an initial bandwidth portion for initial access. At this time, the Identification (ID) of the initial bandwidth portion may be considered as 0.
The bandwidth part configuration supported by 5G may be used for various purposes.
According to some embodiments, when the bandwidth supported by the terminal is smaller than the system bandwidth, the bandwidth supported by the terminal may be supported by the bandwidth part configuration. For example, the base station may configure the frequency location of the bandwidth part (configuration information 2) for the terminal so that the terminal transmits or receives data at a specific frequency location in the system bandwidth.
According to another embodiment, the base station may configure multiple bandwidth parts for the terminal in order to support different parameter sets. For example, in order to support data transmission or reception using a subcarrier spacing of 15KHz and data transmission/reception using a subcarrier spacing of 30KHz to a terminal, a base station may configure the terminal with two bandwidth portions having a subcarrier spacing of 15KHz and a subcarrier spacing of 30KHz, respectively. The different bandwidth portions may undergo frequency division multiplexing, and when data is to be transmitted or received at a specific subcarrier interval, the bandwidth portions configured at the corresponding subcarrier interval may be activated.
According to another embodiment, the base station may configure the terminal with bandwidth portions having different bandwidths in order to reduce the power consumption of the terminal. For example, when a terminal supports a very wide bandwidth (e.g., a bandwidth of 100 MHz) and always transmits or receives data through the corresponding bandwidth, the terminal may consume a very large amount of power. In particular, unnecessary monitoring of downlink control channels in a large bandwidth of 100MHz without traffic may be very inefficient in view of power consumption. In order to reduce the power consumption of the terminal, the base station may configure the terminal with a bandwidth portion having a relatively small bandwidth, for example, a bandwidth portion having 20 MHz. The terminal may monitor the 20MHz bandwidth portion when there is no traffic, and when data is generated, the terminal may transmit or receive data through the 100MHz bandwidth portion according to an instruction of the base station.
Regarding the above method of configuring a bandwidth part, a terminal before RRC connection may receive configuration information of an initial bandwidth part through a Master Information Block (MIB) in an initial access phase. More specifically, a terminal may be configured with a control resource set (CORESET) for a downlink control channel through a MIB of a Physical Broadcast Channel (PBCH) through which Downlink Control Information (DCI) of a scheduling System Information Block (SIB) may be transmitted. The bandwidth of the control resource set configured by the MIB may be regarded as an initial bandwidth portion, and the terminal may receive a Physical Downlink Shared Channel (PDSCH) transmitting the SIB through the configured initial bandwidth portion. In addition to the purpose of receiving SIBs, the initial bandwidth portion may be used for Other System Information (OSI), paging, and random access.
[ Bandwidth portion (BWP) Change ]
When configuring one or more bandwidth parts for a terminal, a base station may indicate a bandwidth part change (or handover) to the terminal by using a bandwidth part indicator field in DCI. For example, in fig. 3, when the currently active bandwidth part of the terminal is bandwidth part #1, the base station may indicate bandwidth part #2 302 to the terminal by using the bandwidth part indicator in the DCI, and the terminal may perform a bandwidth part handover to bandwidth part #2 302 indicated by the bandwidth part indicator in the received DCI.
As described above, the DCI-based bandwidth switching may be indicated by DCI scheduling PDSCH or PUSCH, and thus, when a terminal receives a request to switch a bandwidth part, the terminal may be able to receive or transmit PDSCH or PUSCH scheduled by DCI in the switched bandwidth part without difficulty. For this purpose, the delay time (T) required for switching the bandwidth part is specified in the standard BWP ) And may be defined, for example, below.
TABLE 3
The requirement of bandwidth part switching delay time supports either type 1 or type 2 depending on the capabilities of the terminal. The terminal may report supportable bandwidth-part delay time types to the base station.
When the terminal receives DCI including the bandwidth part switching indicator in the time slot n according to the requirement of the bandwidth part switching delay time, the terminal can be no later than the time slot n+T BWP To the new bandwidth part indicated by the bandwidth part switch indicator, and transmission or reception of the data channel scheduled by the corresponding DCI may be performed in the new bandwidth part switched to. When the base station intends to schedule the data channel to a new bandwidth part, the base station can switch the delay time (T BWP ) To determine a time domain resource assignment for the data channel. That is, in a method for determining a time domain resource assignment of a data channel when a base station schedules the data channel to a new bandwidth part, the base station may schedule the corresponding data channel after a bandwidth part switching delay time. Thus (2)The DCI indication indicating the bandwidth part switch may not be desired by the terminal to have a value less than the bandwidth part switch delay time (T BWP ) Time slot offset (K0 or K2) of the value of (c).
When the terminal receives DCI (e.g., DCI format 1_1 or 0_1) indicating a bandwidth part switch, the terminal may not perform transmission or reception during a time interval from a third symbol of a slot in which a PDCCH including the DCI is received to a start symbol of a slot indicated by a slot offset (K0 or K2) indicated by a time domain resource assignment field in the DCI. For example, when the terminal has received DCI indicating a bandwidth part switch in the 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 the slot n to the symbol before the slot n+k (i.e., the last symbol of the slot n+k-1).
[ SS/PBCH Block ]
Next, a Synchronization Signal (SS)/PBCH block in 5G will be described.
The SS/PBCH block may represent a physical layer channel block including a primary SS (PSS), a Secondary SS (SSs), and a PBCH. More specifically, the SS/PBCH block may be defined as follows:
-PSS: the PSS is a reference signal for downlink time/frequency synchronization, which provides a part of information of a cell ID;
SSS: SSS is a reference signal for downlink time/frequency synchronization that provides the rest of the cell ID information that PSS does not provide. Additionally, SSS may also be used as a Reference Signal (RS) for demodulation of PBCH;
-PBCH: the PBCH provides the terminal with basic system information required for transmission or reception of the data channel and the control channel. The basic system information may include search space related control information indicating radio resource mapping information of a control channel, scheduling control information of an additional data channel for transmitting system information, and the like; and
-SS/PBCH block: the SS/PBCH block is a combination of PSS, SSs and PBCH. One or more SS/PBCH blocks may be transmitted within 5ms, and each SS/PBCH block may be distinguished by an index.
The terminal may detect PSS and SSS in the initial access phase and decode the PBCH. The terminal may acquire the MIB from the PBCH and may configure a control resource set (CORESET) #0 (which may correspond to a control resource set with a control resource set index of 0) from the PBCH. The terminal may monitor the control resource set #0 assuming that a demodulation reference signal (DMRS) transmitted in the control resource set #0 is quasi co-located with the selected SS/PBCH block (QCL). The terminal may acquire system information as downlink control information transmitted in the control resource set # 0. The terminal may acquire Random Access Channel (RACH) related configuration information required for initial access from the received system information. The terminal may transmit a Physical RACH (PRACH) to the base station in consideration of the selected SS/PBCH index, and the base station having received the PRACH may acquire the SS/PBCH block index selected by the terminal. The base station may identify a block selected by the terminal from among the respective SS/PBCH blocks and may identify that the control resource set #0 associated with the selected block is monitored.
[DRX]
Fig. 6 illustrates Discontinuous Reception (DRX).
Discontinuous Reception (DRX) is an operation in which a terminal using a service discontinuously receives data in an RRC connected state in which a radio link is configured between a base station and the terminal. In case of applying the DRX, the terminal may turn on the receiver at a specific point of time to monitor the control channel, and when no data is received for a predetermined period of time, the terminal may turn off the receiver to reduce power consumption of the terminal. DRX operation may be controlled by the MAC layer device based on various parameters and timers.
Referring to fig. 6, the activation time 605 is a time interval during which the terminal wakes up and monitors the PDCCH during the DRX period. The activation time 605 may be defined as follows:
-drx-ondurationTimer or drx-InactivityTimer or drx-retransmission Timer DL or drx-retransmission Timer UL or ra-Contention Resolution Timer is running;
-a scheduling request is sent on PUCCH and is pending; or alternatively
-indicating that a PDCCH of a new transmission addressed to a C-RNTI of the MAC entity has not been received after successful reception of a random access response for a random access preamble not selected by the MAC entity among the contention-based random access preambles.
The drx-onDurationTimer, drx-InactivityTimer, drx-RetransmissionTimerDL, drx-retransmission timer ul and ra-contentioresolute are timers, the values of which are configured by the base station, and have a function of configuring the terminal so that the terminal monitors the PDCCH if a predetermined condition is satisfied.
The DRX-onduration timer 615 is a parameter used to configure the minimum time interval for a terminal to wake up in a DRX cycle. The drx-incaactyitytimer 620 is a parameter for configuring an additional time interval for terminal wakeup in case 630 of receiving a PDCCH indicating a new uplink transmission or downlink transmission. drx-retransmission timer dl is a parameter for configuring the maximum time interval for which a terminal is awake to receive downlink retransmission in a downlink HARQ process. The drx-retransmission timer ul is a parameter for configuring a maximum time interval for which a terminal is awake to receive grant of uplink retransmission in an uplink HARQ process. The drx-onDurationTimer, drx-InactivityTimer, drx-retransmission timer dl and drx-retransmission timer ul may be configured by time, the number of subframes, or the number of slots. ra-contentioresolutiontimer is a parameter for monitoring PDCCH during random access.
The inactivity time 610 is a time interval configured to not monitor or receive a PDCCH in the DRX operation, and a time interval remaining after subtracting the activation time 605 from an entire time interval in which the DRX operation is performed may be the inactivity time 610. If the terminal does not monitor the PDCCH during the activation time 605, the terminal can enter a sleep or inactive state to reduce power consumption.
The DRX cycle represents a period during which the terminal wakes up and monitors the PDCCH. That is, the DRX cycle represents a time interval or duration occurrence period between the monitoring of the PDCCH by the terminal and the monitoring of the next PDCCH. Two types of DRX cycles, a short DRX cycle and a long DRX cycle, may be applied, wherein the short DRX cycle may be optionally applied.
The long DRX cycle 625 is a long cycle of two types of DRX cycles configured for the terminal. When the terminal operates according to the long DRX cycle, the terminal restarts the DRX-onduration timer 615 from a starting point (e.g., a start symbol) of the DRX-onduration timer 615 at a point of time after the long DRX cycle 625 elapses. If the terminal operates according to the long DRX cycle 625, the terminal may start the DRX-onduration timer 615 in a slot after DRX-SlotOffset in a subframe satisfying the following equation 1. Here, drx-SlotOffset represents the delay before drx-onduration timer 615 starts. The drx-SlotOffset may be configured by, for example, time, number of slots, etc.
[ equation 1]
[ (SFN X10) +number of subframes ] mod (drx-LongCycle) =drx-StartOffset.
In this case, the DRX-longcyclestatoffset may include the long DRX cycle 625 and DRX-StartOffset, and may be used to define a subframe in which the long DRX cycle 625 is to be started. The drx-longcycletartoffset may be configured by, for example, time, the number of subframes, the number of slots, and the like.
[ PDCCH: regarding DCI ]
Next, downlink Control Information (DCI) in the 5G system will be described in detail.
In the 5G system, scheduling information of 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 through DCI. The terminal may monitor the fallback DCI format and the non-fallback DCI format of the PUSCH or PDSCH. The fallback DCI format may be configured with a fixed field predefined between the base station and the terminal, and the non-fallback DCI format may include a configurable field.
The DCI may be subjected to a channel coding and modulation procedure and then transmitted through a Physical Downlink Control Channel (PDCCH). A Cyclic Redundancy Check (CRC) may be appended to the DCI message payload, and the CRC may be scrambled by a Radio Network Temporary Identifier (RNTI) corresponding to an identity of the terminal. Different types of RNTIs may be used depending on the purpose of the DCI message, such as terminal-specific (UE-specific) data transmissions, power control commands, random access responses, etc. That is, the RNTI may not be explicitly transmitted, and may be transmitted after being included in the CRC calculation process. If the terminal has received the DCI message transmitted on the PDCCH, the terminal may identify the CRC by using the assigned RNTI, and if the CRC identification result is correct, the terminal may identify that the message has been transmitted to the terminal.
For example, DCI scheduling PDSCH for System Information (SI) may be scrambled by SI-RNTI. The DCI scheduling PDSCH for a Random Access Response (RAR) message may be scrambled by the RA-RNTI. The DCI scheduling PDSCH for a paging message may be scrambled by a P-RNTI. The DCI informing of the Slot Format Indicator (SFI) may be scrambled by the SFI-RNTI. The DCI informing of Transmit Power Control (TPC) may be scrambled by a TPC-RNTI. The DCI scheduling the terminal-specific PDSCH or PUSCH may be scrambled by a cell RNTI (C-RNTI).
DCI format 0_0 may be used to schedule a fallback DCI for PUSCH, and in this case, the CRC may be scrambled by the C-RNTI. DCI format 0_0 with CRC scrambled by C-RNTI may include information as shown in table 4 below.
TABLE 4
DCI format 0_1 may be used for non-fallback DCI for scheduling PUSCH, and in this case, CRC may be scrambled by C-RNTI. DCI format 0_1 with CRC scrambled by C-RNTI may include information as shown in table 5 below.
TABLE 5
/>
DCI format 1_0 may be used to schedule a fallback DCI for PDSCH, and in this case, the CRC may be scrambled by the C-RNTI. The DCI format 1_0 with CRC scrambled by the C-RNTI may include several pieces of information as follows.
TABLE 6
DCI format 1_1 may be used for non-fallback DCI for scheduling PDSCH, and in this case, CRC may be scrambled by C-RNTI. DCI format 1_1 with CRC scrambled by C-RNTI may include several pieces of information as follows.
TABLE 7
[ PDCCH: CORESET, REG, CCE search space ]
Hereinafter, a downlink control channel in a 5G communication system will be described in detail with reference to the accompanying drawings. Fig. 4 illustrates an example of a control resource set (CORESET) on which a downlink control channel is transmitted in a 5G wireless communication system. Fig. 4 shows an example in which a bandwidth part 410 of a terminal is configured along a frequency axis and two control resource sets (control resource set #1 401 and control resource set #2 402) are configured in one slot 420 along a time axis. The control resource sets 401 and 402 may be configured along the frequency axis on specific frequency resources 403 in the entire terminal bandwidth part 410. The control resource sets 401 and 402 may be configured by one or more OFDM symbols, the configured one or more OFDM symbols may be configured along a time axis, and the configured one or more OFDM symbols may be defined as a control resource set duration 404. In the example depicted in fig. 4, control resource set #1 401 is configured with a control resource set duration of two symbols, and control resource set #2 is configured with a control resource set duration of one symbol.
The control resource set in 5G described above may be configured for the terminal by the base station through higher layer signaling, e.g., system information, master Information Block (MIB), and Radio Resource Control (RRC) signaling. Configuring the control resource set for the terminal means that the base station provides the terminal with information such as control resource set identification, frequency location of the control resource set or symbol length of the control resource set. For example, the information provided to the terminal by the base station may include the following pieces of information.
TABLE 8
In table 8, TCI-statepdcch (simply referred to as Transmission Configuration Indication (TCI) state) configuration information may include information about one or more indexes of one or more SS/PBCH blocks having a quasi co-sited (QCL) relationship with DMRS transmitted on a corresponding CORESET, or information about indexes of channel state information reference signals (CSI-RS).
Fig. 5A shows an example of a basic unit of time and frequency resources of the downlink control channel available in 5G. Referring to fig. 5A, a basic unit of time and frequency resources constituting a control channel may be referred to as a Resource Element Group (REG), wherein REG503 may be defined as one OFDM symbol 501 along a time axis and one Physical Resource Block (PRB) 502 along a frequency axis, i.e., 12 subcarriers. The base station may configure the downlink control channel allocation unit by connecting REG 503.
As shown in fig. 5A, if the basic unit of allocation of a downlink control channel in 5G is a Control Channel Element (CCE) 504, one CCE504 may include a plurality of REGs 503. For example, REGs 503 in fig. 5A may include 12 REs, and if one CCE504 includes six REGs 503, one CCE504 may include 72 REs. If a set of downlink control resources is configured, the corresponding set of resources may include a plurality of CCEs 504, and a particular downlink control channel may be mapped to one or more CCEs 504 according to an Aggregation Level (AL) within the set of control resources and may then be transmitted. CCEs 504 in the control resource set may be distinguished by the number, and the number of CCEs 504 may be allocated according to a logical mapping scheme.
The basic unit of the downlink control channel shown in fig. 5A, i.e., REG 503, may include all REs to which DCI is mapped and an area to which DMRS505 corresponding to a reference signal for decoding the REs is mapped. As shown in fig. 5A, three DMRSs 505 may be transmitted within one REG 503. The number of CCEs required to transmit the PDCCH may be 1, 2, 4, 8, or 16 according to an Aggregation Level (AL), and link adaptation of a downlink control channel may be achieved using a different number of CCEs. For example, if al=l, one downlink control channel may be transmitted through L CCEs. The terminal is required to detect the signal without knowing about the downlink control channel and define information indicating the search space of the CCE set for blind decoding. The search space is a set of downlink control channel candidates including CCEs, which a terminal may attempt to decode at a given aggregation level, and there are several aggregation levels where the CCE sets are configured by 1, 2, 4, 8, and 16 CCEs, and thus, the terminal may have multiple search spaces. A set of search spaces may be defined as a set of search spaces at the aggregate level of all configurations.
The search space may be classified into a common search space and a terminal (UE) -specific search space. Terminals or all terminals in a predetermined group may investigate the common search space of the PDCCH in order to receive cell common control information (such as system information or dynamic scheduling of paging messages). For example, PDSCH scheduling allocation information for transmission of SIBs including information on service providers of cells may be received by investigating a common search space of the PDCCH. In the case of a common search space, terminals or all terminals in a predetermined group may receive the PDCCH, and thus the common search space may be defined as a set of CCEs agreed in advance. The scheduling allocation information of the terminal-specific PDSCH or PUSCH may be received by investigating a UE-specific search space of the PDCCH. The UE-specific search space may be defined in a UE-specific manner as a function of the terminal identity and various system parameters.
In 5G, parameters of the PDCCH search space may be configured for the terminal by the base station through higher layer signaling (e.g., SIB, MIB or RRC signaling). For example, the base station may configure the terminal with the number of PDCCH candidates at each aggregation level L, a monitoring period of the search space, monitoring occasions in symbols within a slot of the search space, a search space type (common search space or UE-specific search space), a combination of DCI formats and RNTIs to be monitored in the corresponding search space, a control resource set index for monitoring the search space, and the like. For example, the following information may be included.
TABLE 9
According to the configuration information, the base station may configure one or more search space sets for the terminal. According to some embodiments, a base station may configure search space set 1 and search space set 2 for a terminal, may be configured such that DCI format a scrambled by an X-RNTI in search space set 1 is monitored in a common search space, and may be configured such that DCI format B scrambled by a Y-RNTI in search space set 2 is monitored in a UE-specific search space.
According to the configuration information described above, there may be one or more sets of search spaces in a common search space or a UE-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 UE-specific search spaces.
In the common search space, the following combination of DCI format and RNTI may be monitored. These combinations are not limited to the following examples:
-DCI format 0_0/1_0, the CRC of which is scrambled by C-RNTI, CS-RNTI, SP-CSI-RNTI, RA-RNTI, TC-RNTI, P-RNTI, SI-RNTI;
-DCI format 2_0, the CRC of which is scrambled by SFI-RNTI;
-DCI format 2_1 with CRC scrambled by INT-RNTI;
-DCI format 2_2 with CRC scrambled by TPC-PUSCH-RNTI, TPC-PUCCH-RNTI; and
DCI format 2_3, the CRC of which is scrambled by TPC-SRS-RNTI.
In the UE-specific search space, the following combination of DCI format and RNTI may be monitored. These combinations are not limited to the following examples:
-DCI format 0_0/1_0, the CRC of which is scrambled by C-RNTI, CS-RNTI, TC-RNTI;
-DCI format 1_0/1_1, the CRC of which is scrambled by C-RNTI, CS-RNTI, TC-RNTI;
the RNTI listed above may follow the following definitions and usage:
-C-RNTI (cell RNTI): UE-specific PDSCH scheduling use;
-TC-RNTI (temporary cell RNTI): UE-specific PDSCH scheduling use;
CS-RNTI (configured scheduling RNTI): semi-statically configured UE-specific PDSCH scheduling usage;
RA-RNTI (random access RNTI): PDSCH scheduling in the random access phase;
-P-RNTI (paging RNTI): PDSCH scheduling in paging transmissions;
SI-RNTI (system information RNTI): PDSCH scheduling in system information transmission;
-INT-RNTI (interrupt RNTI): indicating whether there is a puncturing usage for PDSCH;
TPC-PUSCH-RNTI (transmission power control of PUSCH RNTI): indicating the use of power adjustment commands for PUSCH;
TPC-PUCCH-RNTI (transmission power control of PUCCH RNTI): indicating the use of a power adjustment command for PUCCH; and
TPC-SRS-RNTI (transmission power control of SRS RNTI): indicating the use of power adjustment commands for SRS.
The DCI formats listed above may follow the following definitions:
TABLE 10
In 5G, the search space of aggregation level L in control resource set p and search space set s may be represented in equation 2 below:
[ equation 2]
Wherein:
-L: aggregation level;
-n CI : a carrier index;
-N CCE,p : controlling the total number of CCEs present in the resource set p;
a slot index;
aggregation level L PDCCH candidate number;
aggregating PDCCH candidate indexes of level L;
-i＝0，...，L-1；
Y p,-1 ＝n RNTI not equal to 0, for p mod 3=0a p =39827 for p mod 3=1a p =39829 for p mod 3=2a p =39839, d=65537; and
-n RNTI terminal identifier.
The value may correspond to zero in the common search space.
In the case of a UE-specific search space, theThe value may correspond to a value that varies according to a time index and a terminal identity (C-RNTI or an ID configured by the base station for the terminal).
In 5G, since multiple search space sets may be configured with different parameters (e.g., parameters in table 10), a set of search space sets monitored by a terminal may change at each point in time. For example, when the search space set #1 is configured with an X slot period, the search space set #2 is configured with a Y slot period, and X and Y are different from each other, the terminal may monitor both the search space set #1 and the search space set #2 in a specific slot, or may monitor one of the search space set #1 and the search space set #2 in a specific slot.
[ PDCCH: span ]
For the case where there are multiple PDCCH monitoring occasions within a slot, the terminal may perform terminal capability reporting for each subcarrier spacing, and in this case, the concept of "span" may be used. The span may represent consecutive symbols in which a terminal may monitor the PDCCH in a slot, and each PDDCH monitoring occasion is within one span. The span may be denoted as (X, Y), where X indicates the minimum number of symbols that need to be separated between the first symbols of two consecutive spans, and Y indicates the number of consecutive symbols in which the PDCCH may be monitored in one span. Here, the terminal may monitor the PDCCH from an interval within Y symbols from the first symbol of the span within the span.
Fig. 5B illustrates, by span, a case in which a terminal can have a plurality of PDCCH monitoring occasions in a slot in a wireless communication system. The span may correspond to (X, Y) = (7, 4), (4, 3), (2, 2), where in fig. 5B the three cases are denoted 5-1-00,5-1-05 and 5-1-10, respectively. For example, 5-1-00 shows a case where two spans, which may be represented as (7, 4), exist in one slot. The interval between the first symbols of two spans is denoted as x=7, the pdcch monitoring occasion may exist within a total of y=3 symbols from the first symbol of each span, and search spaces 1 and 2 exist in y=3 symbols. In another example, 5-1-05 shows a case where there are a total of three spans in one time slot, which can be represented as (4, 3), where the interval between the second and third spans is indicated as X' =5 greater than x=4.
[ PDCCH: UE capability report ]
The slot positions where the above common search space and the UE-specific search space are located are indicated by the monitoringsymbol wiswiswiring slot parameter in table 11-1, and the symbol positions within the slot are indicated by the bitmap by the monitoringsymbol wiswiring slot parameter in table 9. Symbol opportunities within a slot in which a terminal may perform search space monitoring may be reported to a base station by the following terminal capabilities (UE capabilities):
UE capability 1 (hereinafter referred to as "FG 3-1"). The UE capability indicates the capability of monitoring a corresponding MO when there is one Monitoring Occasion (MO) in a slot for a type 1 and type 3 common search space or a UE specific search space, as shown in table 11-1 below, and the corresponding MO is located within the first three symbols in the slot. The UE capability corresponds to a mandatory capability that may be supported by all NR-capable terminals and whether the capability is supported is not explicitly reported to the base station.
TABLE 11-1
UE capability 2 (hereinafter referred to as "FG 3-2"). The UE capability means capability of monitoring a corresponding MO regardless of a position of a start symbol of the corresponding MO when one Monitoring Occasion (MO) for a common search space or a UE-specific search space exists in a slot as shown in table 11-2 below. The UE capability is optionally supported by the terminal (optional) and whether the capability is supported is explicitly reported to the base station.
TABLE 11-2
UE capability 3 (hereinafter referred to as "FG 3-5, 3-5a, and 3-5 b"). The UE capability indicates a MO pattern that may be monitored by a terminal when there are multiple Monitoring Opportunities (MOs) for a common search space or a UE-specific search space in a slot, as shown in table 11-3 below. The pattern includes X indicating an interval between start symbols between different MOs and Y indicating a maximum symbol length of one MO. In { (2, 2), (4, 3), (7, 3) }, there may be one or more combinations of (X, Y) supported by the terminal. The UE capability is optionally supported by the terminal and whether the capability is supported and the above (X, Y) combination is explicitly reported to the base station.
[ Table 11-3]
/>
The terminal may report to the base station whether the above-described UE capability 2 and/or UE capability 3 and parameters related thereto are supported. The base station may perform time domain resource allocation of the common search space and the UE-specific search space based on the reported UE capabilities. During resource allocation, the base station may allow the MO not to be located in a position where the terminal cannot perform monitoring.
[ PDCCH: BD/CCE restriction ]
When configuring a plurality of search space sets for a terminal, the following conditions may be considered in a method for determining a search space set to be monitored by the terminal.
If the value of monitoringcapability config-r16 corresponding to higher layer signaling is configured as r15monitoringcapability of the terminal, the terminal defines a maximum of the number of monitorable PDCCH candidates and the number of CCEs constituting an entire search space (here, the entire search space represents all CCE sets corresponding to a joint region of a plurality of search space sets) for each slot, and if the value of monitoringcapability config-r16 is configured as r16monitoringcapability of the terminal, the terminal defines a maximum of the number of monitorable PDCCH candidates and the number of CCEs constituting the entire search space (here, the entire search space represents all CCE sets corresponding to a joint region of a plurality of search space sets) for each span.
[ condition 1: restriction on maximum number of PDCCH candidates
According to the above high-layer signaling configuration value, 15.2 is configured μ In a cell with KHz subcarrier spacing, M is defined on a slot basis μ At this time, M corresponds to the number of PDCCH candidates that the terminal can monitor μ Table 12-1 below may be followed when M is defined based on span μ When this is the case, the following Table 12-2 can be followed.
TABLE 12-1
| μ | Maximum number of PDCCH candidates per slot and per serving cell |
| 0 | 44 |
| 1 | 36 |
| 2 | 22 |
| 3 | 20 |
TABLE 12-2
[ condition 2: restriction on maximum number of CCEs
According to the above higher layer signaling configuration value, 15.2 is configured μ In a cell with KHz subcarrier spacing, C is defined when on a slot basis μ When C, which corresponds to the maximum number of CCEs constituting the entire search space (where the entire search space represents the entire set of CCEs corresponding to the joint region of the plurality of search space sets) μ Table 12-3 below may be followed when C is defined based on span μ When this is the case, the following Table 12-4 can be followed.
[ Table 12-3]
| μ | Maximum number of non-overlapping CCEs per slot and per serving cell (C μ ) |
| 0 | 56 |
| 1 | 56 |
| 2 | 48 |
| 3 | 32 |
[ tables 12-4]
For convenience of description, a case where both the condition 1 and the condition 2 are satisfied at a specific point in time is defined as "condition a". Thus, failure to meet condition a may indicate failure to meet at least one of condition 1 or condition 2.
[ PDCCH: oversubscription
Depending on the configuration of the search space set of base stations, there may be cases where condition a cannot be satisfied at a specific point in time. When the condition a is not satisfied at a specific point of time, the terminal may select and monitor only a portion of the search space set configured to satisfy the condition a at the corresponding point of time, and the base station may transmit the PDCCH by using the selected search space set.
As a method of selecting some search spaces from the entire set of configured search spaces, the following method may be followed.
When the condition a for the PDCCH is not satisfied at a specific point of time (slot), the terminal (or base station) may preferentially select a search space set in which a search space type is configured as a common search space among search spaces existing at a corresponding point of time, instead of a search space set configured as a UE-specific search space.
When all the search space sets configured as the common search space are selected (i.e., when the condition a is satisfied even after all the search spaces configured as the common search space are selected), the terminal (or base station) may select the search space set configured as the UE-specific search space. In this case, when there are a plurality of search space sets configured as UE-specific search spaces, a search space set having a lower search space set index may have a higher priority. By taking into account the priority, the set of UE-specific search spaces may be selected within the scope of meeting condition a.
[ QCL, TCI State ]
In a wireless communication system, one or more different antenna ports (or alternatively, one or more channels, signals, or a combination thereof, but for convenience in the following description of the present disclosure, referred to as "different antenna ports" for consistency) may be associated with each other by a quasi co-location (QCL) configuration as shown in table 13 below. The TCI state is used to inform QCL relationships between PDCCH (or PDCCH DMRS) and different RSs or channels, and when one reference antenna port a (reference rs#a) is quasi co-located with another target antenna port B (target rs#b), this means that the terminal is allowed to apply some or all of the large-scale channel parameters estimated in antenna port a to perform channel measurements from antenna port B. QCL can be related to each other according to different parameters, such as 1) time tracking affected by average delay and delay spread, 2) frequency tracking affected by doppler shift and doppler spread, 3) Radio Resource Management (RRM) affected by average gain, and 4) Beam Management (BM) affected by spatial parameters, which require different parameters. Thus, NR supports four types of QCL relationships as shown in Table 13 below.
TABLE 13
| QCL type | Large scale characteristics |
| A | Doppler shift, doppler spread, average delay, delay spread |
| B | Doppler shift and Doppler spread |
| C | Doppler shift, average delay |
| D | Spatial Rx parameters |
The spatial Rx parameters may collectively refer to all or some of various parameters such as angle of arrival (AoA), power Angle Spectrum (PAS) of AoA, angle of departure (AoD), PAS of AoD, transmit/receive channel correlation, transmit/receive beamforming, and spatial channel correlation.
The QCL relationship may be configured for the terminal through the RRC parameters TCI-State and QCL-Info as shown in table 14 below. Referring to table 14, the base station may configure at least one TCI state for the terminal to inform the terminal of up to two QCL relationships (e.g., QCL Type1 (QCL-Type 1) and QCL Type2 (QCL-Type 2)) with respect to RSs (i.e., target RSs) referencing IDs of the TCI states. In this case, each QCL information (QCL-Info) included in each TCI state includes a serving cell index and a BWP index of a reference RS indicated by the corresponding QCL information, a type and ID of the reference RS, and a QCL type as shown in table 13 above.
TABLE 14
Fig. 7 shows an example of base station beam allocation configured according to TCI state. Referring to fig. 7, a base station may transmit information of N different beams to a terminal through N different TCI states. For example, as shown in fig. 7, if n=3, the base station may allow QCL type2 parameters included in each of the three TCI states 700, 705 and 710 to be associated with CSI-RS or SSB corresponding to different beams and configured as QCL type D in order to inform that antenna ports for the different TCI states 700, 705 and 710 are associated with different spatial Rx parameters (i.e., different beams).
Tables 15-1 to 15-5 below show the effective TCI state configuration according to the target antenna port type.
Table 15-1 shows the effective TCI state configuration in the case where the target antenna port is CSI-RS (TRS) for tracking. TRS means NZP CSI-RS for which no repetition parameter is configured, and TRS-Info is configured to have a value of "true" in the CSI-RS. In table 15-1, the target antenna port may be used for aperiodic TRS when configuration 3 is configured.
TABLE 15-1 effective TCI State configuration when the target antenna port is the CSI-RS (TRS) for tracking
Table 15-2 shows an effective TCI state configuration in the case where the target antenna port is a CSI-RS for CSI. CSI-RS means NZP CSI-RS for which neither a parameter indicating repetition (repetition parameter) nor trs-Info is configured to have a value of "true" in CSI-RS.
TABLE 15-2 effective TCI State configuration when the target antenna port is the CSI-RS for CSI
Table 15-3 shows the effective TCI state configuration in the case where the target antenna port is a CSI-RS for Beam Management (BM) having the same meaning as the CSI-RS for L1RSRP reporting. CSI-RS of BM means NZP CSI-RS for which the repetition parameter is configured and has a value of "on" or "off", and trs-info is not configured to have a value of "true" in CSI-RS.
TABLE 15-3 effective TCI State configuration when the target antenna port is CSI-RS for BM (for L1RSRP reporting)
Table 15-4 shows the effective TCI state configuration when the target antenna port is PDCCH DMRS.
TABLE 15-4 effective TCI State configuration when the target antenna port is PDCCH DMRS
Table 15-5 shows the effective TCI state configuration when the target antenna port is PDSCCH DMRS.
TABLE 15-5 effective TCI State configuration when the target antenna port is PDSCH DMRS
In the representative QCL configuration methods according to tables 15-1 to 15-5, the target antenna port and the reference antenna port of each stage are configured and managed, such as "SSB" - > "TRS" - > "CSI-RS for CSI, CSI-RS for BM, PDCCH DMRS, or PDSCH DMRS". Accordingly, statistical characteristics measurable from SSB and TRS are associated with the antenna ports, and thus, the reception operation of the terminal can be assisted.
[ PDCCH: regarding TCI State ]
Specifically, combinations of TCI states applicable to PDCCH DMRS antenna ports are shown in tables 15-6 below. In table 15-6, the combinations in the fourth row are assumed by the terminal before RRC configuration and cannot be configured after RRC configuration.
[ tables 15-6]
NR supports a hierarchical signaling method as shown in fig. 8 for dynamic allocation of PDCCH beams. Referring to fig. 8, a base station may configure a terminal with N TCI states 805, 810,..and 820 through RRC signaling 800, and may configure some TCI states as TCI states of CORESET 825. After configuration, the base station may indicate one of the TCI states 830, 835 and 840 of CORESET to the terminal through MAC CE signaling 845. Thereafter, the terminal receives the PDCCH based on beam information included in the TCI state indicated by the MAC CE signaling.
Fig. 9 shows a TCI indication MAC CE signaling structure for a PDCCH DMR. Referring to fig. 9, TCI indication MAC CE signaling for PDCCH DMR is configured by 2 bytes (16 bits) 900 and 905 and includes a serving cell ID 915 of 5 bits, a CORESET ID 920 of 4 bits, and a TCI status ID 925 of 7 bits.
Fig. 10 shows an example of a configuration of CORESET and search space beams according to the description above. Referring to fig. 10, the base station may indicate one TCI state in a TCI state list included in the configuration of CORESET 1000 through MAC CE signaling 1005. Thereafter, until another TCI state in CORESET is indicated through another MAC CE signaling, the terminal may assume that the same QCL information (beam #1 1005) is applied to one or more search spaces 1010, 1015, and 1020 connected to CORESET. In the above PDCCH beam allocation method, it is difficult to indicate beam change before MAC CE signaling delay, and there are advantages in that the same beam is commonly applied to each CORESET regardless of the characteristics of the search space, and thus, flexible PDCCH beam management is difficult. Hereinafter, embodiments of the present disclosure provide more flexible PDCCH beam configuration and management methods. In describing embodiments of the present disclosure, some distinguishable examples are provided for convenience of description, but these examples are not mutually exclusive and may be appropriately combined with each other according to the circumstances of application.
The base station may configure one or more TCI states for the terminal with respect to a specific control resource set, and may activate one of the configured TCI states through a MAC CE activation command. For example, { TCI state #0, TCI state #1, TCI state #2} is configured as the TCI state for the control resource set #1, and the base station can transmit an activation command assuming the TCI state of the control resource set #1 as the TCI state #0 to the terminal through the MAC CE. Based on the activation command for the TCI state received through the MAC CE, the terminal can correctly receive the DMRS in the control resource set based on the QCL information in the activated TCI state.
For the control resource set (control resource set # 0) configured to have index 0, if the terminal fails to receive the MAC CE activation command for the TCI state of the control resource set #0, the terminal may assume that the DMRS transmitted in the control resource set #0 is quasi co-located with the SS/PBCH block identified in the initial access procedure or the non-contention based random access procedure that is not triggered by the PDCCH command.
For a control resource set (control resource set #x) configured to have a non-zero value index, if the TCI state of the control resource set #x cannot be configured for the terminal, or if one or more TCI states are configured for the terminal, but the terminal fails to receive a MAC CE activation command activating one of the TCI states, the terminal may assume that the DMRS transmitted in the control resource set #x is quasi co-located with the SS/PBCH block identified in the initial access procedure.
[ PDCCH: regarding QCL priority rules
Hereinafter, an operation of determining the QCL priority of the PDCCH is described in detail.
When the terminal performs a carrier aggregation operation in a single cell or a frequency band and a plurality of control resource sets existing in an active bandwidth part in the single cell or a plurality of cells overlap in time while having the same QCL type characteristics or different QCL type characteristics in a specific PDCCH monitoring occasion, the terminal may select a specific control resource set according to the QCL priority determining operation and monitor a control resource set having the same QCL type characteristics as a corresponding control resource set. That is, only one QCL type characteristic can be received when a plurality of control resource sets overlap in time. In this case, the condition for determining QCL priority may be as follows:
-condition 1: in a cell including a common search interval, a control resource set connected to the common search interval corresponding to the lowest index of the lowest indexed cells; and
-condition 2: in a cell including a UE-specific search interval, a control resource set corresponding to a lowest-indexed UE-specific search interval in a lowest-indexed cell is connected.
As described above, when each condition is not satisfied, the next condition is applied. For example, in the case where control resource sets overlap in time in a specific PDCCH monitoring occasion, when all control resource sets are not connected to a common search interval but to a UE-specific search interval (i.e., when condition 1 is not satisfied), the terminal may omit the application of condition 1 and may apply condition 2.
When the terminal selects the control resource set according to the above conditions, the following two additional matters can be considered for QCL information configured for the control resource set. First, if the control resource set 1 has CSI-RS 1 as a reference signal having a QCL type D relationship, the reference signal with which the CSI-RS 1 has a QCL type D relationship corresponds to SSB 1, and the reference signal with which the other control resource set 2 has a QCL type D relationship corresponds to SSB 1, the terminal may consider that the two control resource sets 1 and 2 have different QCL type D characteristics. Second, if the control resource set 1 has CSI-RS 1 configured in the cell 1 as a reference signal having a QCL type D relationship, the CSI-RS 1 and the reference signal having a QCL type D relationship thereof correspond to SSB 1, the control resource set 2 has CSI-RS2 configured in the cell 2 as a reference signal having a QCL type D relationship, and the CSI-RS2 and the reference signal having a QCL type D relationship thereof correspond to SSB 1, the terminal may consider that the two control resource sets have the same QCL type characteristics.
Fig. 12 illustrates a method for selecting an acceptable control resource set in consideration of priority when a terminal receives a downlink control channel in a wireless communication system according to an embodiment of the present disclosure. For example, the terminal may be configured with reception of multiple control resource sets overlapping in time in a specific PDCCH monitoring occasion 1210, and the multiple control resource sets may be connected to a common search space or UE-specific search space for multiple cells. In the corresponding PDCCH monitoring occasion, the control resource set #1 1215 connected to the common search space #1 may exist in the bandwidth part #1 1200 of the cell #1, and the control resource set #1 1220 connected to the common search space #1 and the control resource set #2 1225 connected to the UE-specific search space #2 may exist in the bandwidth part #1 1205 of the cell # 2. The control resource sets 1215 and 1220 may have a QCL type D relationship with the CSI-RS resource #1 configured in the bandwidth part #1 of the cell #1, and the control resource set 1225 may have a QCL type D relationship with the CSI-RS resource #1 configured in the bandwidth part #1 of the cell # 2.
Accordingly, when condition 1 is applied to the corresponding PDCCH monitoring occasion 1210, all other control resource sets having reference signals in QCL type D, such as control resource set #11215, may be received. Accordingly, the terminal may receive the control resource sets 1215 and 1220 in the corresponding PDCCH monitoring occasion 1210. In another example, the terminal may be configured with reception of multiple control resource sets overlapping in time in a specific PDCCH monitoring occasion 1240, and the multiple control resource sets may be connected to a common search space or UE-specific search space for multiple cells. In the corresponding PDCCH monitoring occasion, the control resource set #1 1245 connected to the UE-specific search space #1 and the control resource set #2 1250 connected to the UE-specific search space #2 may exist in the bandwidth portion #1 1230 of the cell #1, and the control resource set #1 1255 connected to the UE-specific search space #1 and the control resource set #2 1260 connected to the UE-specific search space #3 may exist in the bandwidth portion #1 1235 of the cell # 2.
Control resource sets 1245 and 1250 may have a QCL type D relationship with CSI-RS resource #1 configured in bandwidth part #1 of cell #1, control resource set 1255 may have a QCL type D relationship with CSI-RS resource #1 configured in bandwidth part #1 of cell #2, and control resource set 1260 may have a QCL type D relationship with CSI-RS resource #2 configured in bandwidth part #1 of cell # 2. However, when condition 1 is applied to the corresponding PDCCH monitoring occasion 1240, there is no common search space, and thus, condition 2 corresponding to the next condition may be applied. When condition 2 is applied to the corresponding PDCCH monitoring occasion 1240, all other control resource sets, such as control resource set 1245, having the reference signal of QCL type D may be received. Accordingly, the terminal may receive control resource sets 1245 and 1250 in corresponding PDCCH monitoring occasions 1240.
[ regarding Rate matching/puncturing ]
Hereinafter, the rate matching operation and the puncturing operation are described in detail.
When the time and frequency resource a for transmitting the predetermined symbol sequence a overlaps with the predetermined time and frequency resource B, the rate matching or puncturing operation may be regarded as an operation of transmitting or receiving the channel a in consideration of the resource C in the region where the resource a and the resource B overlap. The detailed operation may follow the following description.
Rate matching operation
The base station may perform mapping to the channel a only for a resource region remaining after excluding a resource C corresponding to a region overlapping with the resource B from the entire resource a for transmitting the symbol sequence a to the terminal, and perform transmission. For example, when the symbol sequence a includes { symbol #1, symbol #2, symbol #3, symbol #4}, the resource a includes { resource #1, resource #2, resource #3, resource #4}, and the resource B includes { resource #3, resource #5}, the base station may sequentially map the symbol sequence a to the resources { resource #1, resource #2, resource #4}, which correspond to the resources remaining after excluding the { resource #3} corresponding to the resource C from the resource a, and perform transmission. Accordingly, the base station can map { symbol #1, symbol #2, symbol #3} corresponding to the symbol sequence to { resource #1, resource #2, resource #4} respectively and perform transmission.
The terminal may determine resource a and resource B from scheduling information related to symbol sequence a from the base station and determine resource C corresponding to an area where resource a overlaps with resource B. The terminal may receive the symbol sequence a by assuming that the symbol sequence a is mapped to an area remaining after excluding the resource C from the entire resource a and transmitted. For example, when the symbol sequence a includes { symbol #1, symbol #2, symbol #3, symbol #4}, the resource a includes { resource #1, resource #2, resource #3, resource #4}, and the resource B includes { resource #3, resource #5}, the terminal may receive the symbol sequence a by assuming that the symbol sequence a is sequentially mapped to { resource #1, resource #2, resource #4} corresponding to the resource remaining after excluding { resource #3} corresponding to resource C from the resource a and transmitted. Accordingly, the terminal can then perform a series of reception operations by assuming that { symbol #1, symbol #2, symbol #3} corresponding to the symbol sequence is mapped to { resource #1, resource #2, and resource #4} respectively and transmitted.
Perforating operation
When there is a resource C corresponding to an area overlapping with a resource B in the entire resource a for transmitting the symbol sequence a to the terminal, the base station may map the symbol sequence to the entire resource a, but may perform transmission only on a resource area remaining after the resource C is excluded from the resource a, instead of performing transmission in the resource area corresponding to the resource C. For example, when the symbol sequence a includes { symbol #1, symbol #2, symbol #3, symbol #4}, the resource a includes { resource #1, resource #2, resource #3, resource #4}, and the resource B includes { resource #3, resource #5}, the base station may map the symbol sequence a { symbol #1, symbol #2, symbol #3, symbol #4} to the resource a { resource #1, resource #2, resource #3, resource #4}, respectively, and may transmit only the symbol sequence of { symbol #1, symbol #2, symbol #4} corresponding to { symbol #1, symbol #2, symbol #4} remaining after excluding { resource #3} corresponding to resource C from the resource a, instead of transmitting { symbol #3} mapped to { resource #3} corresponding to resource C. Accordingly, the base station can map { symbol #1, symbol #2, symbol #4} corresponding to the symbol sequence to { resource #1, resource #2, resource #4} respectively and perform transmission.
The terminal may determine the resource a and the resource B from scheduling information related to the symbol sequence a from the base station, and accordingly, may determine the resource C corresponding to the region where the resource a and the resource B overlap. The terminal may receive the symbol sequence a by assuming that the symbol sequence a is mapped to the entire resource a, but performing transmission in an area remaining after excluding the resource C from the resource area a. For example, when the symbol sequence a includes { symbol #1, symbol #2, symbol #3, symbol #4}, the resource a includes { resource #1, resource #2, resource #3, resource #4}, and the resource B includes { resource #3, resource #5}, the terminal may receive the symbol sequence a by assuming that { symbol #1, symbol #2, symbol #3, symbol #4} corresponding to the symbol sequence a is mapped to { resource #1, resource #2, resource #3, resource #4} corresponding to the resource a, but not transmitting { symbol #3} mapped to { resource #3} corresponding to the resource C, and assuming that { symbol #1, symbol #2, symbol #4} of the symbol sequence corresponding to { resource #1, resource #2, resource #4} remaining after excluding { resource #3} corresponding to the resource C from the resource a is mapped and transmitted. Accordingly, the terminal can then perform a series of reception operations by assuming that { symbol #1, symbol #2, symbol #4} of the symbol sequence are mapped to { resource #1, resource #2, and resource #4} respectively.
Hereinafter, a method for configuring rate matching resources for rate matching purposes in a 5G communication system is described. Rate matching means controlling the size of a signal by considering the amount of resources capable of transmitting the signal. For example, rate matching of data channels means adjusting the amount of data without mapping and transmitting the data channels with respect to a given time and frequency resource region.
Fig. 11 illustrates a method of transmitting or receiving data by a base station and a terminal in consideration of a downlink data channel and rate matching resources.
Fig. 11 shows a downlink data channel (PDSCH) 1101 and rate matching resources 1102. The base station may configure one or more rate matching resources 1102 for the terminal via higher layer signaling (e.g., RRC signaling). Configuration information for rate matching resource 1102 may include time domain resource allocation information 1103, frequency domain resource allocation information 1104, and period information 1105. Hereinafter, a bitmap corresponding to the frequency domain resource allocation information 1104 is referred to as a "first bitmap", a bitmap corresponding to the time domain resource allocation information 1103 is referred to as a "second bitmap", and a bitmap corresponding to the period information 1105 is referred to as a "third bitmap". If all or some of the time and frequency resources of the scheduled data channel 1101 overlap with the configured rate matching resources 1102, the base station may perform rate matching on the data channel 1101 in the rate matching resources 1102 portion and transmit the data channel 1101. The terminal may perform reception and decoding under the assumption that rate matching of the data channel 1101 has been performed in the portion of the rate matching resource 1102.
With the additional configuration, the base station may dynamically inform the terminal whether to perform rate matching on the data channels in the configured rate matching resource part through DCI (corresponding to the "rate matching indicator" in the DCI format described above). Specifically, the base station may select some configured rate matching resources and group the selected rate matching resources into rate matching resource groups, and may indicate to the terminal whether the data channel has been rate-matched with respect to each rate matching resource group through DCI by using a bitmap scheme. For example, if four rate matching resources rmr#1, rmr#2, rmr#3, and rmr#4 have been configured, the base station may configure rmg#1= { rmr#1, rmr#2} and rmg#2= { rmr#3, rmr#4} as a rate matching group and may indicate to the terminal whether rate matching has been performed in each of rmg#1 and rmg#2 in the form of a bitmap by using 2 bits in the DCI field. For example, if rate matching can be performed, it may be indicated with "1", and if rate matching may not be performed, it may be indicated with "0".
In 5G, granularity of "RB symbol level" and "RE level" is supported as a method for configuring the above-described rate matching resource for the terminal. More specifically, the following configuration method may be used.
RB symbol level
Up to four RateMatchPatterns per bandwidth portion may be configured for the terminal via higher layer signaling, and each RateMatchPattern may include the following information:
as reserved resources in the bandwidth part, resources whose corresponding time and frequency resource regions of reserved resources are configured as a combination of symbol-level bitmaps and RB-level bitmaps along the frequency axis may be included. The reserved resources may span one or two time slots. In a time domain pattern (periodic pattern), time and frequency regions each including a pair of RB-level bitmap and symbol-level bitmap repetition may be additionally configured.
A resource region corresponding to a time domain and frequency domain resource region configured as a control resource set in the bandwidth part, and a resource region corresponding to a time domain pattern configured as a search space configuration in which the corresponding resource region is repeated may be included.
RE level
The terminal may be configured with the following information via higher layer signaling:
as configuration information (LTE-CRS-to-matching around) of REs corresponding to LTE CRS (cell-specific reference signal or common reference signal) patterns, the number of LTE CRS Ports (nrofCRS-Ports) and LTE-CRS-vshift value (v-shift), center subcarrier position information (carrier freqdl) of an LTE carrier from a baseband point (e.g., from reference point a), bandwidth part size (carrier bandwidth dl) of an LTE carrier, subframe configuration information (MBSFN-subframe configuration list) corresponding to a multicast broadcast single frequency network (MBSFN-subframe), and the like may be included. The terminal may determine the location of the CRS in the NR slot corresponding to the LTE subframe based on the above information.
Configuration information for a set of resources corresponding to one or more Zero Power (ZP) CSI-RS in a bandwidth portion may be included.
[ regarding LTE CRS Rate matching ]
Next, the LTE cell-specific reference signal (CRS) rate matching procedure will be described in detail. For coexistence between Long Term Evolution (LTE) and New RAT (NR) (LTE-NR coexistence), NR terminals in NR are provided with functionality for configuring LTE CRS patterns. More specifically, the CRS pattern may be provided via RRC signaling including at least one parameter of a ServingCellConfig Information Element (IE) or ServingCellConfigCommon IE. Examples of parameters may include lte-CRS-ToMatchAround, lte-CRS-Pattern List1-r16, lte-CRS-Pattern List2-r16, CRS-RateMatch-PercoresETPoolIndex-r16, and so forth.
A function of configuring one CRS pattern for each serving cell through the lte-CRS-to-matcharound parameter is provided in Rel-15 NR. In Rel-16NR, this functionality has been extended to enable configuration of multiple CRS patterns for each serving cell. More specifically, one CRS pattern per LTE carrier may be configured for a single (transmission and reception point) TRP configuration terminal, and two CRS patterns per LTE carrier may be configured for a multi-TRP configuration terminal. For example, up to three CRS patterns may be configured for a single TRP configured terminal via the lte-CRS-PatternList1-r16 parameters. In another example, CRS for each TRP may be configured for a multi-TRP configuration terminal. That is, CRS pattern of TRP1 may be configured by the lte-CRS-Pattern List1-r16 parameter, and CRS pattern of TRP2 may be configured by the lte-CRS-Pattern List2-r16 parameter. When configuring two TRPs, whether to apply CRS patterns of TRP1 and TRP2 to a specific Physical Downlink Shared Channel (PDSCH) or CRS patterns of only one TRP is determined by the CRS-RateMatch-percoresetpolindex-r 16 parameter. If the CRS-RateMatch-PercoresETPoollindex-r 16 parameter is configured to be enabled, only one TRP's CRS pattern is applied. Otherwise, CRS patterns of two TRPs will be applied.
Table 16 below shows ServingCellConfig IE including a CRS pattern and table 17 below shows a ratematchpattern lte-CRS IE including at least one parameter of the CRS pattern.
TABLE 16
/>
TABLE 17
[ PDSCH: regarding frequency resource allocation ]
Fig. 14 illustrates an example of frequency domain resource allocation of a Physical Downlink Shared Channel (PDSCH) in a wireless communication system according to an embodiment of the disclosure.
Fig. 14 shows three frequency domain resource allocation methods of type 0 (14-00), type 1 (14-05) and dynamic handover 14-10, which can be configured by higher layers in an NR wireless communication system.
Referring to fig. 14, in case that a terminal is configured to use only resource type 0, some Downlink Control Information (DCI) for allocating PDSCH to the terminal includes a bitmap of NRBG bits through higher layer signaling 14-00. The conditions for this will be described later. In this case, NRBG indicates the number of Resource Block Groups (RBGs) determined according to the Size of BWP allocated by the BWP indicator and higher layer parameter "RBG-Size", as shown in [ table 18] below, and data is transmitted to RBGs represented as "1" by a bitmap.
TABLE 18
| Bandwidth portion size | Configuration 1 | Configuration 2 |
| 1-36 | 2 | 4 |
| 37-72 | 4 | 8 |
| 73-144 | 8 | 16 |
| 145-275 | 16 | 16 |
In case the terminal is configured to use only resource type 1, some DCI for allocating PDSCH to the terminal already includes frequency domain resource allocation information including by higher layer signaling 14-05And a number of bits. The conditions for this will be described again later. The base station may configure the starting VRB 14-20 and the length 14-25 of the frequency domain resources allocated consecutively after the starting VRB.
If a terminal is configured to use resource type 0 and resource type 1 through higher layer signaling 14-10, some DCI for allocating PDSCH to the corresponding terminal includes frequency domain resource allocation information including bits for configuring a large value 14-35 of payloads 14-15 of resource type 0 and payloads 14-20 and 14-25 of resource type 1. The conditions for this will be described again later. In this case, one bit 14-30 may be added to the foremost part (MSB) of the frequency domain resource allocation information in the DCI, may indicate the use of resource type 0 when the corresponding bit has a value of "0", and may indicate the use of resource type 1 when the corresponding bit has a value of "1".
PDSCH/PUSCH: regarding time resource Allocation
Hereinafter, a time domain resource allocation method for a data channel in a next generation mobile communication system (5G or NR system) will be described.
The base station may configure the terminal with a table of time domain resource allocation information on a downlink data channel (physical downlink shared channel (PDSCH)) and an uplink data channel (physical uplink shared channel (PUSCH)) through higher layer signaling (e.g., RRC signaling). A table including up to maxNrofDL-allocations=16 entries may be configured for PDSCH, and a table including up to maxNrofUL-allocations=16 entries may be configured for PUSCH. In an embodiment, the time domain resource allocation information may include PDCCH to PDSCH slot timing (corresponding to a time interval in units of slots between a time point at which the PDCCH is received and a time point at which the PDSCH scheduled by the received PDCCH is transmitted and denoted as K0), PDCCH to PUSCH slot timing (corresponding to a time interval in units of slots between a time point at which the PDCCH is received and a time point at which the PUSCH scheduled by the received PDCCH is transmitted and denoted as K2), information on a position and length of a start symbol in a slot at which the PDSCH or PUSCH is scheduled, a mapping type of the PDSCH or PUSCH, and the like. For example, the information shown in the following [ table 19] or [ table 20] may be notified from the base station to the terminal.
TABLE 19
TABLE 20
/>
The base station may inform the terminal of one of the entries in the table of the above-described time domain resource allocation information (e.g., it may be indicated by the field "time domain resource allocation" in the DCI) through L1 signaling (e.g., DCI). The terminal may acquire time domain resource allocation information of PDSCH or PUSCH based on DCI received from the base station.
Fig. 15 illustrates an example of allocating time domain resources of a PDSCH in a wireless communication system according to an embodiment of the disclosure.
Referring to fig. 15, the base station may perform a base station according to subcarrier spacing (SCS) (μ) of data channels and control channels configured using higher layers PDSCH Sum mu PDCCH ) The scheduling offset value (K0), the starting position 1500 of the OFDM symbol within one slot 1510 dynamically indicated by the DCI, and its length 1505, indicates the time domain position of the PDSCH resources.
Fig. 16A illustrates an example of allocating time domain resources according to subcarrier spacing of a data channel and a control channel in a wireless communication system according to an embodiment of the present disclosure.
Referring to fig. 16A, if the subcarrier spacing of the data channel is the same as the subcarrier spacing of the control channel (μ) PDSCH ＝μ PDCCH ) 1600, the data and control slot numbers are the same and thus, the base station and the terminal may generate a scheduling offset according to a predetermined slot offset (K0). On the other hand, if the subcarrier spacing of the data channel is different from the subcarrier spacing of the control channel (μ) PDSCH ≠μ PDCCH ) 1605, the data and the controlled slot numbers are different from each other, and thus, the base station and the terminal may generate a scheduling offset according to a predetermined slot offset (K0) based on the subcarrier spacing of the PDCCH.
[ PDSCH: treatment time ]
Next, PDSCH processing time (PDSCH processing procedure time) will be described. When the base station performs scheduling of PDSCH transmission to the terminal by using DCI format 1_0, 1_1 or 1_2, the terminal may require PDSCH processing time for receiving PDSCH by applying a transmission method (modulation/demodulation and coding indication index (modulation and coding scheme (MCS), modulation reference signal related information, time and frequency resource allocation information, etc.) via DCI.
[ equation 3]
T proc,1 ＝(N 1 +d 1,1 +d 2 )(2048+144)κ2 -μ T c +T ext.
T in the above equation 3 proc,1 May have the following meaning:
N 1 : the parameter indicates the number of symbols determined from the parameter set μ and the UE processing capability 1 or capability 2 determined from the UE capability. In case of reporting UE processing capability 1 according to UE capability report, N 1 May have [ Table 21 ]]And N in case of reporting UE processing capability 2 and configuring availability of UE processing capability 2 via higher layer signaling 1 May have [ Table 22]]Is a value of (b). Parameter set μmay correspond to μ PDCCH 、μ PDSCH Sum mu UL To make T proc,1 Maximizing the value of (a) and μ PDCCH 、μ PDSCH Sum mu UL The parameter set of the PDCCH having the scheduled PDSCH, the parameter set of the scheduled PDSCH, and the parameter set of the uplink channel through HARQ-ACK to be transmitted may be represented, respectively.
TABLE 21 PDSCH processing time in case of PDSCH processing capability 1
TABLE 22 PDSCH processing time with PDSCH processing capability 2
-κ：64
Text: if the terminal uses the shared spectrum channel access scheme, the terminal may calculate a value of Text and apply it to PDSCH processing time. Otherwise, the value of Text is assumed to be 0.
If l1, which indicates a PDSCH DMRS position value, is 12, then the value of N1,0 in [ Table 21] is 14. Otherwise, N1,0 has a value of 13.
For PDSCH mapping type a, d1,1 is 7-i if the last symbol of the PDSCH corresponds to the i-th symbol in the slot in which the PDSCH is transmitted and i > 7. Otherwise, d1,1 is 0.
-d2: if the PUCCH with the higher priority index overlaps with the PUCCH or PUSCH with the lower priority index in the time domain, d2 of the PUCCH with the higher priority index may be configured as a value reported from the terminal. Otherwise, d2 is 0.
If PDSCH mapping type B is used for UE processing capability 1, the value d1,1 may be determined according to the number of scheduled PDSCH symbols (L) and the number of symbols (d) overlapping between PDCCH for scheduling PDSCH and scheduled PDSCH, as follows:
-if L is ≡ 7, d1, 1=0;
-if L is ≡4 and L is ≡6, d1, 1=7-L;
-if l=3, d1, 1=min (d, 1); and
-if l=2, d1, 1= 3+d.
If PDSCH mapping type B is used for UE processing capability 2, the value d1,1 may be determined according to the number of scheduled PDSCH symbols (L) and the number of symbols (d) overlapping between PDCCH for scheduling PDSCH and scheduled PDSCH, as follows:
-if L is ≡ 7, d1, 1=0;
-if L is ≡4 and L is ≡6, d1, 1=7-L; and
if l=2.
If the PDCCH performing scheduling exists in CORESET including three symbols and the corresponding CORESET and the scheduled PDSCH have the same starting symbol, d1, 1=3,
otherwise, d1, 1=d.
Given terminal support capability 2 in the serving cell, PDSCH processing time according to UE processing capability 2 may be applied when the terminal is configured to have higher layer signaling processing type2Enabled for the corresponding cell as "Enabled".
If HARQ-ACK message is includedThe position of the first uplink transmission symbol of the PUCCH of the information (the corresponding position may be considered to be defined as K1 of the HARQ-ACK transmission time point, PUCCH resources for HARQ-ACK transmission and timing advance effect) is not T later than the last symbol from PDSCH proc,1 The first uplink transmission symbol of which time arrives starts earlier, the terminal may send a valid HARQ-ACK message. That is, the terminal may transmit the PUCCH including the HARQ-ACK only if the PDSCH processing time is sufficient. If not, the terminal cannot provide the base station with valid HARQ-ACK information corresponding to the scheduled PDSCH. When T- proc,1 Can be used in standard CP and extended CP. In the case that PDSCH includes two PDSCH transmission positions in one slot, d1,1 is calculated with reference to the first PDSCH transmission position in the corresponding slot.
[ PDSCH: reception preparation time for Cross-Carrier scheduling
Next, in the case of cross-carrier scheduling, μ corresponding to a parameter set in which a PDCCH for performing scheduling is transmitted PDCCH μ corresponding to a parameter set different from that of transmitting PDSCH scheduled by the corresponding PDCCH PDSCH N- pdsch 。
At mu PDCCH ＜μ PDSCH In the case where the scheduled PDSCH cannot be transmitted earlier than the first symbol of the slot, N comes after the last symbol of the PDCCH for which the corresponding PDSCH has been scheduled pdsch And a symbol. The transmission symbol of the corresponding PDSCH may include DM-RS.
At mu PDCCH ＞μ PDSCH In the case of (2), the scheduled PDSCH may be N after the last symbol from the PDCCH on which the corresponding PDSCH has been scheduled pdsch The symbols are then transmitted. The transmission symbol of the corresponding PDSCH may include DM-RS.
TABLE 23]N according to the PDCCH subcarrier spacing being scheduled pdsch
| μ PDCCH | N pdsch [ symbol ]] |
| 0 | 4 |
| 1 | 5 |
| 2 | 10 |
| 3 | 14 |
[ concerning SRS ]
Next, an uplink channel estimation method using Sounding Reference Signal (SRS) transmission of the terminal will be described. To transmit configuration information for SRS transmission, the base station may configure at least one SRS configuration for each uplink BWP and at least one SRS resource set for each SRS configuration for the terminal. For example, the base station and terminal may send or receive the following higher layer signaling information to convey information related to the SRS resource set:
srs-ResourceSetId: SRS resource set index;
srs-ResourceIdList: an SRS resource index set referenced by the SRS resource set;
-resourceType: this corresponds to a timeline transmission configuration of SRS resources referenced by the SRS resource set, and may be configured as one of "periodic," semi-persistent, "and" aperiodic. When it is configured to be "periodic" or "semi-persistent", the associated CSI-Rs information may be provided according to the use of SRS resource sets. When it is configured as "aperiodic", an aperiodic SRS resource trigger list and slot offset information may be provided, and associated CSI-RSs may be provided according to the use of SRS resource sets;
-usage: this corresponds to a configuration of the purpose of the SRS resource referred to by the SRS resource set, and may be configured as one of "beam management", "codebook", "non-codebook", and "antenna switching"; and
alpha, p0, pathlossReferenceRS, srs-PowerControlAdjust states: this provides a parameter configuration for transmission power adjustment of SRS resources referenced by the SRS resource set.
The terminal may understand that the SRS resources included in the SRS resource index set referenced by the SRS resource set follow information configured for the SRS resource set.
In addition, the base station and the terminal may transmit and receive higher layer signaling information to transmit separate configuration information of SRS resources. For example, the separate configuration information of the SRS resource may include time-frequency axis mapping information in a slot of the SRS resource, and this may include information related to intra-slot or inter-slot frequency hopping of the SRS resource. In addition, the separate configuration information of the SRS resource may include a timeline transmission configuration of the SRS resource, and may be configured as one of "periodic", "semi-persistent", and "aperiodic". This may be limited to having the same timeline transmission configuration as the SRS resource set that includes SRS resources. If the timeline transmission configuration of SRS resources is configured to be "periodic" or "semi-persistent," SRS resource transmission periods and slot offsets (e.g., periodic and offset) may be additionally included in the timeline transmission configuration.
The base station may activate, deactivate, or trigger SRS transmission of the terminal via higher layer signaling (e.g., DCI) including RRC signaling or MAC CE signaling or L1 signaling. For example, the base station may activate or deactivate periodic SRS transmission of the terminal via higher layer signaling. The base station may instruct activation of the SRS resource set with the resourceType configured to periodicity via higher layer signaling, and the terminal may transmit SRS resources referenced by the activated SRS resource set. The time-frequency domain resource map in the slot of the transmitted SRS resource may follow the resource map information configured for the SRS resource, and the slot map including the transmission period and the slot offset may follow the periodic and offset configured for the SRS resource. In addition, the spatial domain transmission filter applied to the transmitted SRS resources may refer to spatial relationship information configured for the SRS resources or to associated CSI-RS information configured for the SRS resource set in which the SRS resources are included. The terminal may transmit SRS resources in uplink BWP activated for the periodic SRS resources activated via higher layer signaling.
For example, the base station may activate or deactivate the semi-persistent SRS transmission of the terminal via higher layer signaling. The base station may indicate activation of the SRS resource set via MAC CE signaling and the terminal may transmit SRS resources referenced by the activated SRS resource set. The SRS resource set activated via MAC CE signaling may be limited to SRS resource sets with a resource type configured to be semi-persistent. The time-frequency domain resource map in the slot of the transmitted SRS resource may follow the resource map information configured for the SRS resource, and the slot map including the transmission period and the slot offset may follow the periodic and offset configured for the SRS resource.
In addition, the spatial domain transmission filter applied to the transmitted SRS resources may refer to spatial relationship information configured for the SRS resources or to associated CSI-RS information configured for the SRS resource set in which the SRS resources are included. If the spatial relationship information is configured for the SRS resource, the spatial relationship information may not be followed, and the spatial domain transmission filter may be determined with reference to the configuration information of the spatial relationship information transmitted through the MAC CE signaling for activating the semi-persistent SRS transmission. The terminal may transmit SRS resources in an uplink BWP activated for the semi-persistent SRS resources activated via higher layer signaling.
For example, the base station may trigger aperiodic SRS transmission of the terminal via DCI. The base station may indicate one of aperiodic SRS resource triggers (aperiodic SRS-resource trigger) via an SRS request field of the DCI. The terminal may understand that in the SRS resource set configuration information, an SRS resource set triggered by the aperiodic SRS resource indicated via DCI from the aperiodic SRS resource trigger list is included. The terminal may transmit SRS resources referenced by the triggered SRS resource set. The time-frequency domain resource mapping in the slot of the transmitted SRS resource may follow the resource mapping information configured for the SRS resource. In addition, a slot map of the transmitted SRS resources may be determined by a slot offset between the SRS resources and the PDCCH including the DCI, and this may refer to one or more values included in a slot offset set configured for the SRS resource set.
Specifically, for a slot offset between an SRS resource and a PDCCH including DCI, a value indicated by a time domain resource allocation field of the DCI may be applied in an offset value included in a slot offset set configured for the SRS resource set. In addition, the spatial domain transmission filter applied to the transmitted SRS resource may refer to spatial relationship information configured for the SRS resource or may refer to associated CSI-RS information configured for the spatial relationship information configured for the SRS resource. The terminal may transmit SRS resources in uplink BWP activated for aperiodic SRS resources triggered via DCI.
When the base station triggers aperiodic SRS resources for the terminal via DCI, a minimum time interval between the transmitted SRS and a PDCCH including DCI for triggering aperiodic SRS transmission may be required in order for the terminal to apply configuration information of the SRS resources and transmit the SRS. The time interval of SRS transmission of the terminal may be defined as the number of symbols between the last symbol of the PDCCH including the DCI for triggering the aperiodic SRS transmission and the first symbol to which the first transmitted SRS resource is mapped in the transmitted one or more SRS resources. The minimum time interval may be determined with reference to a PUSCH preparation procedure time required for the terminal to prepare for PUSCH transmission. In addition, the minimum time interval may have a different value than the use of the SRS resource set including the transmitted SRS resource.
For example, the minimum time interval may be determined with N2 symbols defined in consideration of UE processing capability according to UE capability with reference to PUSCH preparation procedure time of the terminal. In addition, when the use of the SRS resource set including the transmitted SRS resource is configured as "codebook" or "antiswitching" in consideration of the use of the SRS resource set, the minimum time interval may be determined as N2 symbols, and when the use of the SRS resource set is configured as "non codebook" or "beam management", the minimum time interval may be determined as N2+14 symbols. The terminal may transmit the aperiodic SRS when the time interval of the aperiodic SRS transmission has a value equal to or greater than the minimum time interval, and omit DCI for triggering the aperiodic SRS when the time interval of the aperiodic SRS transmission has a value less than the minimum time interval.
TABLE 24
The sputialrationinfo configuration information in table 24 allows reference to one reference signal and applies beam information of the corresponding reference signal to a beam for the corresponding SRS transmission. For example, the configuration of the sputialrationinfo may include information in the following [ table 25 ].
TABLE 25
With reference to the spuatialrelationship info configuration, an SS/PBCH block index, CSI-RS index, or SRS index may be configured as an index of a specific reference signal referred to using beam information of the reference signal. The higher layer signaling reference signal corresponds to configuration information indicating beam information of a reference signal to be referred to for corresponding SRS information, ssb-Index indicates SS/PBCH block Index, CSI-RS-Index indicates CSI-RS Index, and SRS indicates SRS Index. When the value of the higher layer signal reference signal is configured as "ssb-Index", the terminal may apply a reception beam that has been used when receiving the SS/PBCH block corresponding to the ssb-Index as a transmission beam for the corresponding SRS transmission. When the value of the higher layer signaling reference signal is configured as "CSI-RS-Index", the terminal may apply a reception beam that has been used when receiving CSI-RS corresponding to the CSI-RS-Index as a transmission beam for the corresponding SRS transmission. When the value of the higher layer signaling reference signal is configured as "SRS", the terminal can apply a transmission beam that has been used when the SRS corresponding to SRS is transmitted as a transmission beam for the corresponding SRS transmission.
[ PUSCH: regarding transmission scheme ]
Next, a PUSCH transmission scheduling method is described. PUSCH transmissions may be dynamically scheduled by UL grants in the DCI, or may be operated by configured grant type 1 or type 2. The indication of dynamic scheduling of PUSCH transmissions may be made by DCI format 0_0 or 0_1. The configured grant type 1PUSCH transmission may be semi-statically configured by receiving a configurable grant configuration including the rrc-configurable uplink grant in table 26 via higher layer signaling without receiving a UL grant in the DCI. After receiving the configurable grant of the rrc-configurable uplink grant not included in table 26 via higher layer signaling, the configured grant type 2PUSCH transmission may be semi-persistently scheduled by UL grant in the DCI. When the PUSCH transmission is operated by the configured grant, the parameters to be applied to the PUSCH transmission are applied via higher layer signaling configurable grantconfig in table 33, except for the scaling of dataScramblingIdentityPUSCH, txConfig, codebookSubset, maxRank and UCI-on PUSCH provided via higher layer signaling PUSCH-Config in table 27. When the terminal is provided with the transformpredecoder in higher layer signaling configuredGrantConfig in table 26, the terminal applies tp-pi2BP2K in PUSCH-Config in table 27 to PUSCH transmission operated by the configured grant.
TABLE 26
Next, a PUSCH transmission method will be described. The DMRS antenna port for PUSCH transmission is the same as the antenna port for SRS transmission. The PUSCH transmission may follow a codebook-based transmission method or a non-codebook-based transmission method according to whether the value of txConfig in the higher layer signaling PUSCH-Config in [ table 27] is "codebook" or "non-codebook". As described above, PUSCH transmissions may be dynamically scheduled by DCI format 0_0 or 0_1 and may be semi-statically configured by configured grants. If scheduling of PUSCH transmission is indicated to the terminal through DCI format 0_0, the terminal may perform beam configuration of PUSCH transmission by using PUCCH-specialrelationinfoid corresponding to a UE-specific PUCCH resource corresponding to the minimum ID in activated uplink BWP in the serving cell, wherein PUSCH transmission is based on a single antenna port. The terminal does not expect to schedule PUSCH transmission through DCI format 0_0 in BWP without configuring PUCCH resource including PUCCH-sputterrelation info. If txConfig in the pusch-Config in table 27 is not configured for the terminal, the terminal does not desire scheduling by DCI format 0_1.
TABLE 27
Next, a codebook-based PUSCH transmission is described. Codebook-based PUSCH transmissions may be dynamically scheduled by DCI formats 0_0 or 0_1 and may operate semi-statically through configured grants. When codebook-based PUSCH is dynamically scheduled through DCI format 0_1 or semi-statically configured through configured grant, a terminal may determine a precoder for PUSCH transmission based on SRS Resource Indicator (SRI), transmission Precoding Matrix Indicator (TPMI), and transmission rank (number of PUSCH transmission layers).
In this case, the SRI may be given via an SRS resource indicator field in the DCI, or may be configured by higher layer signaling SRS-resource indicator. When performing codebook-based PUSCH transmission, at least one SRS resource is configured for the terminal, and at most two SRS resources may be configured. When the SRIs provided to the terminal via DCI, the SRS resources indicated by the corresponding SRIs represent SRS resources corresponding to the SRIs among SRS resources transmitted before the PDCCH including the corresponding SRIs. In addition, TPMI and transmission rank may be given via precoding information and layer number fields in DCI, or may be configured via higher layer precoding and dnumberoflayers. TPMI is used to indicate the precoder applied to PUSCH transmission. When one SRS resource is configured for a terminal, TPMI is used to indicate a precoder to be applied to one configured SRS resource. When configuring a plurality of SRS resources for a terminal, TPMI is used to indicate a precoder to be applied to the SRS resources indicated via SRI.
The precoder for PUSCH transmission is selected from an uplink codebook with the same number of antenna Ports as the nrorSRS-Ports value in higher layer signaling SRS-Config. In codebook-based PUSCH transmission, the terminal determines a codebook subset based on TPMI and codebook subset in higher layer signaling PUSCH-Config. The codebook subset in the higher layer signaling pusch-Config may be configured as one of "full and partial and incoherent", a "partialanddnoncoherent", and a "non-coherent", based on the UE capability reported by the terminal to the base station. If the terminal has reported "partialAndNON Coherent" as UE capability, the terminal does not expect the value of higher layer signaling codebook subset to be configured as "fullyParafialAndNON Coherent". In addition, when the terminal has reported "non-coherent" as UE capability, the terminal does not expect the value of higher layer signaling codebook subset to be configured as "fullyand partialanddnoncoherent" or "partialanddnoncoherent". When nrofSRS-Ports in higher layer signaling SRS-resource set indicate two SRS antenna Ports, the terminal does not expect the value of higher layer signaling codebook subset to be configured as "partialanddnonpeer".
A terminal may be configured with one SRS resource set having a use value in higher layer signaling SRS-resource set, the use value configured as "codebook", and one SRS resource in the corresponding SRS resource set may be indicated via SRI. When an SRS Resource set having a use value in a higher layer signaling SRS-Resource is configured with several SRS resources, the use value is configured as "codebook", and the terminal expects that the value of nrofSRS-Ports in the higher layer signaling SRS-Resource will be configured with the same value for all SRS resources.
The terminal transmits one or more SRS resources including an SRS resource set whose use value is configured as "codebook" according to higher layer signaling, and the base station selects one of the SRS resources transmitted by the terminal and instructs the terminal to perform PUSCH transmission by using transmission beam information of the corresponding SRS resource. In this case, in the codebook-based PUSCH transmission, SRI is used as information for selecting an index of SRS resources, and is included in DCI. Additionally, the base station includes information indicating a rank and TPMI to be used when the terminal performs PUSCH transmission in DCI. By using SRS resources indicated by the SRI, the terminal performs PUSCH transmission by applying a precoder indicated by a rank and TPMI indicated based on a transmission beam of the corresponding SRS resources.
Next, PUSCH transmission based on non-codebook is described. Non-codebook based PUSCH transmissions may be dynamically scheduled via DCI formats 0_0 or 0_1 and may operate semi-statically through configured grants. When at least one SRS resource is configured in the SRS resource set having a use value in the higher layer signaling SRS-resource set, the use value is configured as "non codebook", and non codebook based PUSCH transmission can be scheduled to the terminal via DCI format 0_1.
For SRS resource sets with usage values in higher layer signaling SRS-resource, the usage values are configured as "non-codebook", one connected non-zero power CSI-RS (NZP CSI-RS) resource may be configured for the terminal. The terminal may calculate a precoder for SRS transmission by measurement of NZP CSI-RS resources connected to the SRS resource set. When the interval between the last received symbol of the aperiodic NZP CSI-RS resource connected to the SRS resource set and the first symbol of the aperiodic SRS transmission has a value greater than 42, the terminal does not desire to update information about the precoder for the SRS transmission.
When the value of the resourceType in the higher layer signaling SRS-resourceNet is configured as "apidic", the connected NZP CSI-RS is indicated by the SRS request corresponding to the field of DCI format 0_1 or 1_1. In this case, when the connected NZP CSI-RS resource corresponds to the aperiodic NZP CSI-RS resource, the presence of the connected NZP CSI-RS is indicated when the value of the SRS request field in the DCI format 0_1 or 1_1 does not correspond to "00". In this case, the corresponding DCI may not indicate cross-carrier or cross-BWP scheduling. Further, when the value of the SRS request indicates the presence of the NZP CSI-RS, the corresponding NZP CSI-RS is located in a slot in which the PDCCH including the SRS request field is transmitted. In this case, the TCI state configured for the scheduled subcarriers is not configured as QCL type.
When the periodic or semi-persistent SRS resource set is configured, the connected NZP CSI-RS may be indicated by associpedsi-RS in the higher layer signaling SRS-resource set. For non-codebook based transmissions, the terminal does not expect higher layer signaling spuatialrelationship info for SRS resources to be configured with associtysi-RS in the higher layer signaling SRS-resource.
When configuring a plurality of SRS resources for a terminal, the terminal may determine a transmission rank and precoder for PUSCH transmission based on the SRI indicated by the base station. In this case, the SRI may be indicated by an SRS resource indicator field in the DCI, or may be configured via higher layer signaling SRS-resource indicator. Similar to the codebook-based PUSCH transmission described above, when an SRI is provided to a terminal via DCI, SRS resources indicated by the corresponding SRI may represent SRS resources corresponding to the SRI among SRS resources transmitted before a PDCCH including the corresponding SRI. The terminal may use one or more SRS resources for SRS transmission and determine the maximum number of SRS resources and the maximum number of SRS resources that may be simultaneously transmitted in the same symbol in one SRS resource set through UE capabilities reported by the terminal to the base station. In this case, SRS resources simultaneously transmitted by the terminals may occupy the same RB. The terminal configures one SRS port for each SRS resource. Only one SRS resource set with a use value in higher layer signaling SRS-resource set, which is configured as "non codebook", may be configured, and up to four SRS resources may be configured for non codebook based PUSCH transmission.
The base station transmits one NZP-CSI-RS connected to the SRS resource set to the terminal, and the terminal calculates a precoder to be used during transmission of one or more SRS resources in the corresponding SRS resource set based on a measurement result during reception of the corresponding NZP-CSI-RS. When transmitting one or more SRS resources in the SRS resource set having the purpose configured as "non codebook" to the base station, the terminal applies the calculated precoder and the base station selects one or more SRS resources from the received one or more SRS resources. In this case, the SRI indication in the non-codebook based PUSCH transmission may represent an index of one or a combination of a plurality of SRS resources, and the SRI is included in the DCI. In this case, the number of SRS resources indicated by the SRI transmitted by the base station may correspond to the number of transmission layers of the PUSCH, and the terminal applies a precoder applied to SRS resource transmission to each layer to transmit the PUSCH.
[ PUSCH: preparation procedure time ]
Next, PUSCH preparation procedure time is described. When the base station performs scheduling such that the terminal transmits PUSCH by using DCI format 0_0, 0_1 or 0_2, the terminal may need PUSCH preparation procedure time to apply a transmission method (transmission precoding method of SRS resource, the number of transmission layers and spatial domain transmission filter) indicated via DCI and transmit PUSCH. In NR, PUSCH preparation procedure time is defined in consideration of the above description. The PUSCH preparation procedure time of the terminal may follow the following [ equation 4]:
[ equation 4]
T proc,2 ＝max((N 2 +d 2,1 +d 2 )(2048+144)κ2 -μ T c +T ext +T switch ,d 2,2 ).
T in the above equation 4 proc，2 May have the following meaning:
N 2 : the parameter indicates the number of symbols determined from the parameter set μ and the UE processing capability 1 or capability 2 determined from the UE capability. In case of reporting UE processing capability 1 according to UE capability report, N 2 May have [ Table 28]]And N in case of reporting UE processing capability 2 and configuring availability of UE processing capability 2 via higher layer signaling 2 May have [ Table 29]]Is a value of (b).
TABLE 28
| μ | PUSCH preparation time N 2 [ symbol ]] |
| 0 | 10 |
| 1 | 12 |
| 2 | 23 |
| 3 | 36 |
TABLE 29
| μ | PUSCH preparation time N 2 [ symbol ]] |
| 0 | 5 |
| 1 | 5.5 |
| 2 | 11 for frequency range 1 |
-d2,1: this corresponds to the number of symbols, and is determined to be 0 if the resource element of the first OFDM symbol of PUSCH transmission is configured with only DM-RS. Otherwise, d2,1 is determined to be 1;
-K：64；
- μ: this follows a value that causes Tproc,2 to be μ DL Sum mu UL And larger. Mu (mu) DL A parameter set indicating a downlink through which a PDCCH including DCI for scheduling PUSCH is transmitted, and μ UL A parameter set indicating an uplink through which a PUSCH is transmitted;
-Tc: tc is 1/(Δf) max ·N f )、ΔΔf max ＝480·10 3 Hz and N f ＝4096；
-d2,2: if the DCI for scheduling PUSCH indicates BWP switching, d2,2 follows the BWP switching time. Otherwise, d2,2 has a value of 0;
-d2: if the OFDM symbols of the PUCCH, PUSCH having a higher priority index, and PUCCH having a lower priority index overlap in the time domain, the d2 value of PUSCH having a higher priority index is used. Otherwise, d2 is 0;
text: if the terminal uses the shared spectrum channel access scheme, the terminal may calculate a value of Text and apply it to PDSCH preparation process time. Otherwise, the value of Text is assumed to be 0; and
tswitch: if an uplink switch interval is triggered, then Tswitch is assumed to be the switch interval time. Otherwise, T switch Is assumed to be 0.
Considering time axis resource mapping information of PUSCH scheduled via DCI and uplink-downlink timing advance effect, if a first symbol of PUSCH starts earlier than a first uplink symbol in which CP is at T later than a last symbol of PDCCH including DCI of PUSCH having been scheduled proc,2 Starting after the time, the base station and the terminal determine that the PUSCH preparation procedure time is insufficient. Otherwise, the base station and the terminal determine that the PUSCH preparation procedure time is sufficient. The terminal may transmit PUSCH only when PUSCH preparation procedure time is sufficient, and may omit DCI for scheduling PUSCH when PUSCH preparation procedure time is insufficient.
[ PUSCH: regarding repeated transmissions
Hereinafter, repeated uplink data channel transmission in the 5G system will be described in detail. In a 5G system, two types of duplicate uplink data channel transmission schemes are supported: a repeated PUSCH transmission type a and a repeated PUSCH transmission type B. One of the repeated PUSCH transmission type a and the repeated PUSCH transmission type B may be configured for the terminal via higher layer signaling.
Repeated PUSCH transmission type a
As described above, in one slot, the symbol length of the uplink data channel and the position of the start symbol are determined according to the time domain resource allocation method, and the base station may inform the terminal of the number of repeated transmissions via higher layer signaling (e.g., RRC signaling) or L1 signaling (e.g., DCI).
The terminal repeatedly transmits an uplink data channel having the same length and starting symbol as those of the configured uplink data channel in consecutive slots based on the number of repeated transmissions received from the base station. In this case, when at least one of a slot configured for the terminal via a downlink or an uplink data channel symbol configured for the terminal is configured via a downlink, the terminal may omit uplink data channel transmission but count the number of repeated uplink data channel transmissions.
Repeated PUSCH transmission type B
As described above, in one slot, the length of the uplink data channel and the start symbol are determined according to the time domain resource allocation method, and the base station may inform the terminal of the number of repeated transmissions (numberofrepetitions) via higher layer signaling (e.g., RRC signaling) or L1 signaling (e.g., DCI).
First, a nominal repetition of the uplink data channel is determined based on the length of the configured uplink data channel and the start symbol as described below. The time slot started by the nth nominal repetition is formed byGiven, and the symbols starting from the slot are represented by/>Given. The time slot ending with the nth nominal repetition is defined byThe time slot given and ending in symbols is defined by +.>Given. Here, n=0,..number of repetitions-1, s indicates a start symbol of the configured uplink data, and L indicates a symbol length of the configured uplink data channel. K (K) s Time slot indicating the start of PUSCH transmission, and +.>Indicating the number of symbols per slot.
The terminal determines an invalid symbol of the repeated PUSCH transmission type B. The symbol configured by tdd-UL-DL-configuration common or tdd-UL-DL-configuration dedicatedly via downlink is determined as an invalid symbol for repeating PUSCH transmission type B. Additionally, invalid symbols may be configured in higher layer parameters (e.g., invalidSymbolPattern). Higher layer parameters (e.g., invalidSymbolPattern) can provide symbol level bitmaps over one or both slots and invalid symbols can be configured therein. In the bitmap, 1 indicates an invalid symbol. Additionally, the periodicity and style of the bitmap may be configured by higher layer parameters (e.g., periodicityAndPattern). If higher layer parameters (e.g., invalidSymbolPattern) are configured and either InvalidSymbolPattern indicator-ForDCIFformat0_1 or InvalidSymbolPattern indicator-ForDCIFformat0_2 parameter indicates 1, the terminal may apply an invalid symbol pattern. If the parameter indicates 0, the terminal does not apply an invalid symbol pattern. The terminal may apply the invalid symbol pattern if higher layer parameters (e.g., invalidSymbolPattern) are configured and no InvalidSymbolPattern indicator-ForDCIFormat0_1 or InvalidSymbolPattern indicator-ForDCIFormat0_2 parameters are configured.
After determining the invalid symbols, the terminal may treat the symbols other than the invalid symbols as valid symbols for each nominal repetition. When one or more active symbols are included in each nominal repetition, then the nominal repetition may include one or more actual repetitions. Here, each actual repetition includes a set of consecutive active symbols in one slot, which may be used to repeat PUSCH transmission type B.
Fig. 16B illustrates an example of a repeated PUSCH transmission type B in a wireless communication system according to an embodiment of the present disclosure. The terminal may receive a configuration in which a start symbol S of the uplink data channel is 0, a length L of the uplink data channel is 14, and the number of repeated transmissions is 16. In this case, the nominal repetition 1601 indicates 16 consecutive time slots. Thereafter, the terminal may determine the symbol configured as the downlink symbol in each nominal repetition 1601 as an invalid symbol. In addition, the terminal determines a symbol configured as 1 in the invalid symbol pattern 1602 as an invalid symbol. When a valid symbol is configured as one or more consecutive symbols in a slot instead of an invalid symbol, in each nominal repetition the valid symbol is configured as an actual repetition 1603 and transmitted.
In addition, regarding repeated PUSCH transmissions, in NR version 16, the following additional methods may be defined for UL grant-based PUSCH transmissions and grant-based PUSCH transmissions configured across slot boundaries.
Method 1 (mini-slot level repetition): two or more repeated PUSCH transmissions are scheduled across slot boundaries in one slot or in consecutive available slots with one UL grant. In addition, regarding method 1, the time domain resource allocation information in the dci indicates resources of the first retransmission. In addition, the time domain resource information of the first retransmission and the time domain resource information of the remaining retransmission may be determined according to an uplink or downlink direction determined for each symbol of each slot. Each repeated transmission occupies a consecutive symbol.
Method 2 (multi-segment transmission): two or more repeated PUSCH transmissions are scheduled in consecutive slots with one UL grant. In this case, one transmission is designated for each slot, and the transmissions may have different starting points or different repetition lengths, respectively. In addition, in method 2, time domain resource allocation information in DCI indicates a start point and a repetition length of all repeated transmissions. In addition, when the repeated transmission is performed in a single slot by the method 2 and there are several consecutive uplink symbol groups in the corresponding slot, each repeated transmission is performed for each uplink symbol group. If there is only one group of consecutive uplink symbols in the corresponding slot, one repeated PUSCH transmission is performed according to the method in NR version 15.
Method 3: two or more repeated PUSCH transmissions are scheduled in consecutive slots with two or more UL grants. In this case, one transmission is designated for each slot, and the nth UL grant may perform reception before PUSCH transmission scheduled by the (n-1) th UL grant ends.
Method 4: one or several repeated PUSCH transmissions may be supported in a single slot, or two or more repeated PUSCH transmissions may be supported across the boundary of consecutive slots, with one UL grant or one configured grant. The number of repetitions indicated by the base station to the terminal is merely a nominal value, and the number of repeated PUSCH transmissions actually performed by the terminal may be greater than the nominal number of repetitions. The time domain resource allocation information or the configured grant in the DCI represents the resources of the first retransmission indicated by the base station. The time domain resource information of the remaining repeated transmissions may be determined with reference to the uplink or downlink direction of the symbol and the resource information of the at least first repeated transmission. If the time domain resource information of the repeated transmission indicated by the base station is on a slot boundary or includes an uplink/downlink transition point, the corresponding repeated transmission may be divided into a plurality of repeated transmissions. In this case, one slot may include one repeated transmission for each uplink period.
[ PUSCH: frequency hopping procedure ]
Hereinafter, frequency hopping of an uplink data channel (physical uplink shared channel (PUSCH)) in the 5G system will be described in detail.
In 5G, as an uplink data channel hopping method, two modes are supported for each repeated PUSCH transmission type. First, in the repeated PUSCH retransmission type a, intra-slot hopping and inter-slot hopping are supported, and in the repeated PUSCH transmission type B, inter-slot hopping and inter-slot hopping are supported.
The intra-slot frequency hopping method supported in the repeated PUSCH transmission type a corresponds to a method in which a terminal changes frequency domain allocation resources by a frequency offset configured in two hops in one slot and performs transmission. In intra-slot frequency hopping, the start RB of each hop can be indicated by the following equation 5.
[ equation 5]
In equation 5, i=0 and i=1 indicate the first hop and the second hop, respectively, and RB start Indicates a start RB in UL BWP and is calculated from a frequency resource allocation method. RB (radio bearer) offset The frequency offset between two hops is indicated by higher layer parameters. The number of symbols of the first hop may be determined byIndicating that the number of symbols of the second hop may be determined byAn indication. />Indicated by the length of PUSCH transmission and the number of OFDM symbols in one slot.
Next, the inter-slot frequency hopping method supported in the repeated PUSCH transmission types a and B corresponds to a method in which the terminal changes the frequency domain allocation resource of each slot by the configured frequency offset and performs transmission. In inter-slot frequency hopping, this can be indicated by the following equation 6The beginning RB of the slot.
[ equation 6]
In the equation (6) for the case of the optical fiber,indicating the current slot number in a multi-slot PUSCH transmission, and RB start Indicates a start RB in UL BWP and is calculated from a frequency resource allocation method. RB (radio bearer) offset The frequency offset between two hops is indicated by higher layer parameters.
Next, the inter-repetition frequency hopping method supported in the repetition PUSCH transmission type B corresponds to a method for allocating a frequency domain allocation resource of one or more actual repetitions in each nominal repetition to a frequency offset of a mobile configuration and performing transmission. The RBstart (n) of the index of the starting RB on the frequency domain corresponding to one or more actual repetitions in the nth nominal repetition may follow the following equation 7.
[ equation 7]
In equation 7, n indicates the index of the nominal repetition, and RB offset The RB offset between two hops is indicated by a higher layer parameter.
[ PUSCH: multiplexing rules for AP/SP CSI reporting
Hereinafter, a method for measuring and reporting a channel state in the 5G communication system will be described in detail. The Channel State Information (CSI) may include a Channel Quality Indicator (CQI), a Precoding Matrix Indicator (PMI), a CSI-RS resource indicator (CRI), an SS/PBCH block resource indicator (SSBRI), a Layer Indicator (LI), a Rank Indicator (RI), an L1 Reference Signal Received Power (RSRP), and the like. The base station may control the time and frequency resources for the above CSI measurement and reporting of the terminal.
For the above-described CSI measurement and reporting, the terminal may receive the configuration of N (Σ 1) pieces of CSI report setting information (CSI-ReportConfig), M (Σ 1) pieces of RS transmission resource setting information (CSI-ResourceConfig), and one or two pieces of trigger state list information (CSI-apeeriodicdigerstatelist and CSI-semipersistenonppusch-TriggerStateList) via higher layer signaling. The configuration information of the above CSI measurement and reporting may be described in more detail as shown in the following [ table 30] to [ table 36 ].
TABLE 30 CSI-ReportConfig
The IE CSI-ReportConfig is used to configure periodic or semi-persistent reports sent on PUCCH on a cell including CSI-ReportConfig, or semi-persistent or non-periodic reports sent on PUSCH triggered by received DCI on a cell including CSI-ReportConfig (in which case the cell sending the report is determined by the received DCI). See TS 38.214[19], clause 5.2.1.
CSI-ReportConfig information element
/>
/>
/>
/>
TABLE 31 CSI-ResourceConfig
The IE CSI-ResourceConfig defines a group of one or more NZP-CSI-RS-ResourceSet, CSI-IM-ResourceSet and/or CSI-SSB-ResourceSet.
CSI-ResourceConfig information element
/>
Table 32 NZP-CSI-RS-resource set
IE NZP-CSI-RS-resource set is a non-zero power (NZP) CSI-RS resource (their ID) set and set specific parameters.
NZP-CSI-RS-resource set information element
TABLE 33 CSI-SSB-ResourceSet
IE CSI-SSB-resource set is used to configure a set of SS/PBCH block resources that references SS/PBCH as indicated in ServerCellConfigCommon.
CSI-SSB-Resourceset information element
TABLE 35 CSI-AperiodicTriggerStateList
CSI-AperiodicTriggerStateList IE is used to configure the UE with an aperiodic trigger state list. Each code point of the DCI field "CSI request" is associated with one trigger state. Upon receiving the value associated with the trigger state, the UE may perform measurement of CSI-RS (reference signal) and aperiodic reporting of L1 according to all entries in the associtreportconfigmnfolist for the trigger state.
CSI-AperiodicTriggerStateList information element
/>
TABLE 36 CSI-semiPersistentOnPUSCH-TriggerStateList
CSI-semipersistent on pusch-TriggerStateList IE is used to configure the UE with a trigger status list for semi-persistent reporting of channel state information on L1. See also TS 38.214[19], clause 5.2.
CSI-semipersistent OnPUSCH-triggerStateList information element
Regarding the above-described CSI reporting settings, each CSI reporting setting (CSI-ReportConfig) may be associated with a Downlink (DL) bandwidth portion identified by a higher layer parameter bandwidth portion identification (bwp-id) provided via a CSI resource setting (CSI-ResourceConfig) associated with the corresponding CSI reporting setting. For the time domain reporting operation in which CSI-ReportConfig is set with respect to each report, the "aperiodic", "semi-persistent", and "periodic" types are supported, and may be configured to a terminal by a base station via a reportConfigType parameter configured from a higher layer. The semi-persistent CSI reporting method supports the "PUCCH-based semi-persistent (semi-persistent on PUCCH)" and "PUSCH-based semi-persistent (semi-persistent on PUSCH)" reporting methods. In the periodic or semi-persistent CSI reporting method, a terminal may be configured with PUCCH or PUSCH resources for transmitting CSI from a base station via higher layer signaling. The periodicity and slot offset of the PUCCH or PUSCH resources for transmitting CSI may be provided via a set of parameters configured to transmit the UL bandwidth portion of the CSI report. In the aperiodic CSI reporting method, PUSCH resources for transmitting CSI may be scheduled to a terminal by a base station via L1 signaling (DCI format 0_1 described above).
Regarding the CSI resource settings (CSI-ResourceConfig), each CSI resource setting (CSI-ResourceConfig) may include S (. Gtoreq.1) CSI resource sets (provided as higher layer parameters CSI-RS-ResourceLetList). The CSI resource set list may include a non-zero power (NZP) CSI-RS resource set and an SS/PBCH block set, or may include a CSI interference measurement (CSI-IM) resource set. Each CSI resource setting may be located in a Downlink (DL) bandwidth portion identified by a higher layer parameter bwp-id, and the CSI resource setting may be connected to a CSI report setting at the same downlink bandwidth portion. Time domain operation of CSI-RS resources in CSI resource settings may be configured as one of "aperiodic", "periodic", or "semi-persistent" by a higher layer parameter resourceType. Regarding periodic or semi-persistent CSI resource settings, the number of CSI-RS resource sets may be limited to s=1, and the configured period and slot offset may be provided by a parameter set of the downlink bandwidth portion identified by bwp-id. The terminal may be configured with one or more CSI resource settings for channel or interference measurements via higher layer signaling by the base station and may include, for example, the following CSI resources:
-CSI-IM resources for Interference Measurement (IM);
-NZP CSI-RS resources for IM; and
NZP CSI-RS resources for channel measurement.
Regarding a set of CSI-RS resources associated with a resource setting in which a higher layer parameter resourceType is configured to be "aperiodic", "periodic", or "semi-persistent", a trigger state of a CSI report setting in which reportType is configured to be "aperiodic" and a resource setting for channel or interference measurement of one or more Component Cells (CCs) may be configured as higher layer parameters CSI-aperictriggerstatelist.
The aperiodic CSI report of the terminal may use PUSCH, the periodic CSI report may use PUCCH, and the semi-persistent CSI report may use PUSCH when triggered or activated by DCI, and may use PUCCH after activated by a MAC Control Element (CE). As described above, CSI-ResourceConfig may be configured to be aperiodic, periodic, or semi-permanent. Based on table 37 below, a combination of CSI reporting settings and CSI resource settings may be supported.
Table 37 triggers/activates CSI reporting for possible CSI-RS configurations.
Aperiodic CSI reporting may be triggered by a "CSI request" field corresponding to DCI format 0_1 for scheduling DCI for PUSCH. The terminal may monitor the PDCCH, obtain DCI format 0_1, and obtain scheduling information and CSI request indicator of PUSCH. The CSI request indicator may be configured with NTS (=0, 1, 2, 3, 4, 5, or 6) bits and may be determined by higher layer signaling reportTriggerSize. One of one or more aperiodic CSI report trigger states (CSI-aperiodic triggerstatelist) configurable via higher layer signaling may be triggered by a CSI request indicator:
When all bits of the CSI request field are 0, CSI report may not have been requested yet;
-when the number M of CSI trigger states within the configured CSI-aperictriggerstatelist is greater than 2NTs-1, the M CSI trigger states may be mapped to 2NTs-1 according to a predefined mapping relationship, and one of the 2NTs-1 trigger states may be indicated via a CSI request field; and
-when the number M of CSI trigger states in the configured CSI-aperictriggerstatelist is equal to or less than 2NTs-1, one of the M CSI trigger states may be indicated via the CSI request field.
Table 38 below illustrates an example of a relationship between CSI request indicators and CSI trigger states that may be indicated by the CSI request indicators.
TABLE 38
The terminal may perform measurements on CSI resources in a CSI triggered state triggered by the CSI request field and thereby generate CSI (including at least one of CQI, PMI, CRI, SSBRI, LI, RI or L1-RSRP described above). The terminal may transmit the obtained CSI by using the PUSCH scheduled by the corresponding DCI format 0_1. When 1 bit corresponding to an UL data indicator (UL-SCH indicator) in DCI format 0_1 indicates "1", uplink data (UL-SCH) and the obtained CSI may be multiplexed and transmitted using PUSCH resources scheduled by DCI format 0_1. When 1 bit corresponding to an uplink data indicator (UL-SCH indicator) in DCI format 0_1 indicates "0", only CSI may be mapped and transmitted using PUSCH resources scheduled by DCI format 0_1 without uplink data (UL-SCH).
Fig. 13 shows an example of an aperiodic CSI reporting method.
In example 1300 of fig. 13, a terminal may obtain DCI format 0_1 by monitoring PDCCH 1301 and obtain scheduling information and CSI request information of PUSCH 1305 therefrom. The terminal may obtain resource information of the CSI-RS 1302 to be measured from the received CSI request indicator. The terminal may determine a time point at which to transmit the measured resources of the CSI-RS 1302 based on a time point when the DCI format 0_1 is received and a parameter (apersinictriggeroffset described above) for an offset in a CSI resource set configuration (e.g., NZP-CSI-RS-resource set). In particular, the terminal may be configured with an offset value X of a parameter (aperictriggeringoffset) in the NZP-CSI-RS resource set configuration via higher layer signaling by the base station, and the configured offset value X may represent an offset between a slot in which CSI-RS resources are transmitted and a slot in which DCI triggering aperiodic CSI reports is received. For example, the parameter value of apiodicTriggeringOffset and the offset value X may have the following mapping relation [ Table 39 ].
TABLE 39
| Offset X | |
| 0 | 0 time slots |
| 1 | 1 time slot |
| 2 | 2 time slots |
| 3 | 3 time slots |
| 4 | 4 time slots |
| 5 | 16 time slots |
| 6 | 24 time slots |
In the example 1300 of fig. 13, the offset value 1303 is configured to x=0. In this case, the terminal may receive the CSI-RS 1302 from the slot of the received DCI format 0_1 (slot 0 1306 of fig. 13) triggering aperiodic CSI reporting and report CSI information measured by the received CSI-RS to the base station via the PUSCH 1305. The terminal may obtain scheduling information (information corresponding to each field of the above-described DCI format 0_1) of PUSCH 1305 for CSI report from DCI format 0_1. For example, the terminal may obtain information about a slot for transmitting the PUSCH 1305 from the time domain resource allocation information of the PUSCH 1305 in the DCI format 0_1. In example 1300 of fig. 13, the terminal has obtained 3 as a K2 value corresponding to a slot offset value of PDCCH-to-PUSCH, and thus, PUSCH 1305 may be transmitted from slot 3 1309 three slots away from slot 0 1306, i.e., when PDCCH 1301 is received.
In example 1310 of fig. 13, a terminal may obtain DCI format 0_1 by monitoring PDCCH 1311 and obtain scheduling information and CSI request information of PUSCH 1315 therefrom. The terminal may obtain resource information of the CSI-RS 1312 to be measured from the received CSI request indicator. Example 1310 of fig. 13 illustrates an example in which offset value 1313 of CSI-RS is configured to x=1. In this case, the terminal may receive the CSI-RS 1312 from the slot of the received DCI format 0_1 (slot 0 1316 of fig. 13) triggering the aperiodic CSI report and report CSI information measured by the received CSI-RS to the base station via the PUSCH 1315. The terminal may obtain scheduling information of PUSCH 1315 for CSI report (information corresponding to each field of the above-described DCI format 0_1) from DCI format 0_1. For example, the terminal may obtain information about a slot for transmitting PUSCH 1315 from time domain resource allocation information of PUSCH 1315 in DCI format 0_1. In example 1310 of fig. 13, the terminal has obtained 3 as K2 value 1314 corresponding to the slot offset value of PDCCH-to-PUSCH, and thus, PUSCH 1315 may be transmitted from slot 3 1319 three slots away from slot 0 1316, i.e., when PDCCH 1311 is received.
The aperiodic CSI report may include at least one or both of CSI part 1 and CSI part 2, and the aperiodic CSI report may be multiplexed to a transport block when the aperiodic CSI report is transmitted through PUSCH. Once the CRC is inserted into the input bits for multiplexed aperiodic CSI, the CSI is mapped to resource elements in PUSCH in a specific pattern after being encoded and rate-matched, and transmitted. CRC insertion may be omitted depending on the encoding method or the length of the input bits. The number of modulation symbols calculated for rate matching of the multiplexed CSI part 1 and CSI part 2 included in the aperiodic CSI report may be calculated as shown in the following table 40.
TABLE 40
/>
Specifically, in the case of repeated PUSCH transmission types a and B, the terminal may multiplex only the aperiodic CSI report to the first repeated transmission among repeated PUSCH transmissions and transmit the aperiodic CSI. This is because the multiplexed aperiodic CSI report information is encoded in a polar code scheme, and in this case, in order to perform multiplexing to several PUSCH repetitions, each PUSCH repetition needs to have the same frequency and time resource allocation. In particular, in case of PUSCH repetition type B, each actual repetition may have a different OFDM symbol length, and thus, the aperiodic CSI report may be multiplexed to only the first PUSCH repetition and transmitted.
In addition, for the repeated PUSCH transmission type B, when the terminal schedules an aperiodic CSI report without scheduling for a transport block or receives DCI for activating a semi-persistent CSI report, the value of the nominal repetition may be assumed to be 1 even when the number of repeated PUSCH transmissions configured via higher layer signaling is greater than 1. In addition, when scheduling or activating aperiodic or semi-persistent CSI reports based on the repeated PUSCH transmission type B without scheduling for a transport block, the terminal may expect the first nominal repetition to be the same as the first actual repetition. For repetition PUSCH transmission type B, the semi-persistent CSI report is not scheduled for the DCI after it has been activated via the DCI, and the transmitted PUSCH including the semi-persistent CSI may be omitted if the first nominal repetition is different from the first actual repetition.
[ reporting on UE capability ]
In LTE and NR, when a terminal connects to a serving base station, the terminal may perform a procedure of reporting, by the terminal, the capability of supporting the base station. In the following description, this procedure is referred to as UE capability reporting.
The base station may transmit a UE capability query message for requesting a capability report from the terminal in a connected state. The message may include a UE capability request for each Radio Access Technology (RAT) type of the base station. The request for each RAT type may include supported band combination information, etc. In addition, in the case of the UE capability query message, a plurality of RAT type-specific UE capabilities may be required through one RRC message container transmitted by the base station, or the UE capability query message including each RAT type-specific UE capability request may be included multiple times to be transmitted to the terminal. That is, the UE capability query may be repeated a plurality of times in one message, and the terminal may configure the UE capability information message corresponding thereto to report the message a plurality of times. In the next generation mobile communication system, a UE capability request for multi-RAT dual connectivity including NR, LTE, E-UTRA-NR dual connectivity (EN-DC) may be requested. In addition, it is conventional to transmit the UE capability query message at an initial stage after the terminal is connected to the base station, but in any case the UE capability query message may be requested according to the needs of the base station.
In the above-described phase, the terminal having received the UE capability report request from the base station configures the UE capability according to the RAT type and band information required by the base station. A method for configuring UE capabilities by a terminal in an NR system is described below.
1. If a list of LTE and/or NR bands is provided to the terminal according to a UE capability request from the base station, the terminal configures a Band Combination (BC) for EN-DC and NR independent (SA). That is, the BC candidate list for EN-DC and NR SA is configured based on the frequency band requested from the base station with FreqBandList. In addition, the frequency band has a priority according to the priorities listed in FreqBandList.
2. If the base station sets the "eutra-NR-only" flag or the "eutra" flag and requests the UE capability report, the terminal completely removes the NR SA BC candidate from the BC candidate list configured above. This may only occur when an LTE base station (eNB) requests an "eutra" capability.
3. Thereafter, the terminal removes the back-off BC from the BC candidate list configured in the above stage. Here, the fallback BC means BC that can be obtained by removing a frequency band corresponding to at least one SCell from a predetermined BC, and may be omitted because BC before removing the frequency band corresponding to at least one SCell has covered the fallback BC. This phase also applies to MR-DC, i.e. to the LTE band. The BC remaining after this stage is referred to as the final "candidate BC list".
4. The terminal selects a BC matching the requested RAT type from the final "candidate BC list" to select the BC to report. At this stage, the terminal configures the supplementadband communication list according to a predetermined sequence. That is, the terminal configures BC and UE capabilities to be reported according to a predetermined rate-Type sequence (nr- > eutra-nr- > eutra). In addition, the terminal configures featureset combination for the configured suppliedband combination list, and configures a "candidate feature set combination" list from the candidate BC list from which the back BC (including the same or lower step capabilities) list has been removed. The "candidate feature set combinations" include all feature set combinations of NR and EUTRA-NR BC, and may be obtained from feature set combinations of containers of UE-NR-Capabilities and UE-MRDC-Capabilities.
5. In addition, when the requested rate type is eutra-NR and there is an effect resulting therefrom, the featurecombinations may be included in the containers of UE-NR-Capabilities and UE-MRDC-Capabilities. However, NR feature sets are included in UE-NR-Capabilities.
After the UE capability configuration is completed, the terminal forwards a UE capability information message including the UE capability to the base station. Thereafter, based on the UE capability received from the terminal, the base station performs scheduling and transmission or reception management appropriate for the corresponding terminal.
[ concerning CA/DC ]
Fig. 17 illustrates a radio protocol structure of a base station and a terminal in a single cell, carrier aggregation, and dual connectivity case according to an embodiment of the present disclosure.
Referring to fig. 17, the radio protocol of the next generation mobile communication system includes an NR Service Data Adaptation Protocol (SDAP) S25 or S70, an NR Packet Data Convergence Protocol (PDCP) S30 or S65, an NR Radio Link Control (RLC) S35 or S60, and an NR Medium Access Control (MAC) S40 or S55 in each of the terminal and the NR base station.
The main functions of NR SDAP S25 or S70 may include some of the following functions:
-transmitting user plane data;
-mapping between QoS flows and DRBs for both DL and UL;
-marking QoS flow IDs in both DL and UL packets; and
-mapping the reflected QoS flow to DRBs of UL SDAP PDU.
Regarding the SDAP layer entity, the terminal may receive a configuration indicating whether to use a header of the SDAP layer entity or whether to use a function of the SDAP layer entity for each PDCP layer entity, for each bearer, or for each logical channel through an RRC message. In the case of an SDAP header configured, the 1-bit NAS reflective QoS configuration indicator and the 1-bit AS reflective QoS configuration indicator of the SDAP header may indicate that the terminal updates or reconfigures mapping information between QoS flows and data bearers of the uplink and downlink. The SDAP header can include QoS flow ID information indicating QoS. QoS information may be used as data processing priority, scheduling information, etc. in order to support efficient services.
The main functions of NR PDCP S30 or S765 may include some of the following functions:
header compression and decompression: ROHC only;
-transmitting user data;
-sequential delivery of upper layer PDUs;
-out-of-order delivery of upper layer PDUs;
-reordering for received PDCP PDUs;
-duplicate detection of lower layer SDUs;
retransmission of PDCP SDUs;
-encryption and decryption; and
-timer based SDU discard in uplink.
The reordering function of the NR PDCP layer entity means a function of reordering PDCP PDUs received from a lower layer in order based on a PDCP Sequence Number (SN), and may include a function of transferring data to a higher layer in the reordered order. Alternatively, the reordering function of the NR PDCP layer entity may include a function of directly transmitting data regardless of an order, a function of performing reordering and recording of lost PDCP PDUs, a function of transmitting a status report of the lost PDCP PDUs to a transmitting end, and a function of requesting retransmission of the lost PDCP PDUs.
The main functions of NR RLC S35 or S60 may include some of the following:
-transmission of upper layer PDUs;
-in-order delivery of upper layer PDUs;
-out-of-order delivery of upper layer PDUs;
-error correction by ARQ;
concatenation, segmentation and reassembly of RLC SDUs;
-re-segmentation of RLC data PDUs;
-reordering of RLC data PDUs;
-repeated detection;
-protocol error detection;
-RLC SDU discard; and
RLC re-establishment.
The sequence delivery function of the NR RLC layer entity means a function of sequentially delivering RLC SDUs received from a lower layer to a higher layer. The sequence delivery function of the NR RLC layer entity may include a function of reassembling and transmitting one original RLC SDU if the RLC SDU is divided into a plurality of RLC SDUs and received; may include a function of reordering received RLC PDUs based on RLC Sequence Numbers (SNs) or PDCP Sequence Numbers (SNs); may include the function of performing reordering and recording missing RLC PDUs; may include a function of transmitting a status report of the missing RLC PDU to the transmitting side; and may include a function of requesting retransmission of the lost RLC PDU. The sequence delivery function of the NR RLC layer entity may include a function of sequentially transmitting only RLC SDUs preceding the missing RLC SDU to a higher layer if there is the missing RLC SDU, or may include sequentially transmitting all RLC SDUs received before the timer starts to a higher layer if a predetermined timer expires even if there is the missing RLC SDU.
Alternatively, the sequence delivery function of the NR RLC layer entity may include sequentially transmitting all RLC SDUs received up to now to a higher layer if a predetermined timer expires even though there are missing RLC SDUs. In addition, RLC PDUs may be processed in the order of reception (in the order of arrival without regard to their sequence numbers or sequence numbers) and may be transmitted to the PDCP layer entity in an out-of-order delivery manner. In case of segmentation, the segments stored in the buffer or to be received later may be received and reconfigured into one complete RLC PDU, and the RLC PDU may be processed and transmitted to the PDCP layer entity. The NR RLC layer may not include a concatenation function, and the function may be performed in the NR MAC layer or may be replaced with a multiplexing function of the NR MAC layer.
Out-of-order delivery of NR RLC layer entities means a function of directly transmitting RLC SDUs received from a lower layer to a higher layer regardless of order, may include a function of reassembling and transmitting RLC SDUs if one original RLC SDU is divided into a plurality of RLC SDUs and received, and may include a function of storing and ordering RLC SNs or PDCP SNs of received RLC PDUs, thereby recording lost RLC PDUs.
The NR MAC S40 or S55 may be connected to a plurality of NR RLC layer entities configured in a single UE, and main functions of the NR MAC may include some of the following functions:
-mapping between logical channels and transport channels;
-multiplexing/demultiplexing of MAC SDUs;
-scheduling information reporting;
HARQ functions (error correction by HARQ);
-priority handling between logical channels of one UE;
-priority handling between UEs employing dynamic scheduling;
-MBMS service identity;
-transport format selection; and
-filling.
The NR PHY layer S45 or S50 may perform an operation of channel-coding and modulating higher layer data into OFDM symbols and transmitting them through a radio channel, or an operation of demodulating and channel-decoding OFDM symbols received through a radio channel and transmitting them to a higher layer.
The detailed structure of the radio protocol may be varied in various ways according to the carrier (or cell) operating scheme. For example, in the case where the base station transmits data to the terminal, the base station and the terminal use a single protocol structure for each layer based on a single carrier (or cell), as shown in S00. On the other hand, in the case where the base station transmits data to the terminal, the base station and the terminal use a protocol structure that provides a single structure before the RLC layer and in which the PHY layer is multiplexed by the MAC layer, based on Carrier Aggregation (CA) using a plurality of carriers in a single TRP, as shown in S10. In another example, in case that the base station transmits data to the terminal, the base station and the terminal use a protocol structure that provides a single structure before the RLC layer and in which the PHY layer is multiplexed through the MAC layer, based on a Dual Connection (DC) using a plurality of carriers among a plurality of TRPs, as shown in S20.
With reference to the above description on PDCCH and beam configuration, in current Rel-15 and Rel-16NR, repeated PDCCH transmission is not supported, and thus, it is difficult to achieve reliability required in a scene requiring high reliability such as URLLC. In the present disclosure, a method of repeating PDCCH transmission through a plurality of transmission points (TRPs) is provided to improve PDCCH reception reliability of a terminal. The detailed process is described in detail in the examples below.
Hereinafter, embodiments of the present disclosure are described in detail with reference to the accompanying drawings. The present disclosure is applicable to Frequency Division Duplex (FDD) and Time Division Duplex (TDD) systems. Hereinafter, in the present disclosure, high-level signaling (higher layer signaling) is a signaling method in which a signal is transmitted from a base station to a terminal using a downlink data channel of a physical layer or from a terminal to a base station using an uplink data channel of a physical layer, and may be referred to as RRC signaling, PDCP signaling, or a Medium Access Control (MAC) control element (MAC CE).
Hereinafter, in the present disclosure, in determining whether to apply cooperative communication, a terminal may use various methods: the PDCCH in which the PDSCH to which the cooperative communication is applied is allocated has a specific format; the PDCCH allocating the PDSCH to which the cooperative communication is applied includes a specific indicator indicating whether the cooperative communication is applied; scrambling a PDCCH to which a PDSCH to which cooperative communication is applied is allocated with a specific RNTI; the application of cooperative communication assumes in a specific section indicated by a higher layer, and so on. Hereinafter, for convenience of description, a case where the terminal receives the PDSCH to which cooperative communication is applied based on similar conditions as described above will be referred to as NC-JT case.
Hereinafter, in the present disclosure, determining the priority between a and B may be mentioned in various ways, such as selecting one having a higher priority than another according to a predetermined priority rule to perform an operation corresponding thereto, or omitting or discarding an operation having a lower priority.
Hereinafter, in the present disclosure, the above examples will be described by a plurality of embodiments, but the embodiments are not independent and one or more embodiments may be applied simultaneously or in combination.
[ concerning NC-JT ]
In accordance with embodiments of the present disclosure, in order for a terminal to receive PDSCH from multiple TRPs, non-coherent joint transmission (NC-JT) may be used.
The 5G wireless communication system can support not only a service requiring a high transmission speed but also a service having a very short transmission delay and a service requiring a high connection density. In a wireless communication network including a plurality of cells, transmission and Reception Points (TRPs), or beams, coordinated transmission between each cell, TRP, and/or beam may satisfy various service requirements by increasing the strength of signals received by a terminal or efficiently performing interference control between cells, TRPs, or/and beams.
Joint Transmission (JT) is a representative transmission technique for the above cooperative communication in which signals are transmitted to terminals through different cells, TRPs, and/or beams to increase the strength or throughput of the signals received by the terminals. In this case, channels between the terminal and each cell, TRP, or/and beam may have significantly different characteristics, and in particular, in case of incoherent joint transmission (NC-JT) supporting incoherent precoding between the respective cells, TRP, and/or beams, separate precoding, MCS, resource allocation, TCI indication, etc. may be required according to the channel characteristics of the links between the terminal and each cell, TRP, and/or beam.
The NC-JT transmission described above may be applied to at least one of a downlink data channel (physical downlink shared channel (PDSCH)), a downlink control channel (physical downlink control channel (PDCCH)), an uplink data channel (physical uplink shared channel (PUSCH)), and an uplink control channel (physical uplink control channel (PUCCH)). During PDSCH transmission, transmission information such as precoding, MCS, resource allocation, and TCI will be indicated via DL DCI, and for NC-JT transmission, transmission information needs to be indicated independently for each cell, TRP, and/or beam. This becomes a major factor to increase the payload required for DL DCI transmission, which may adversely affect the reception performance of the PDCCH transmitting the DCI. Therefore, it is necessary to carefully design a compromise between the amount of DCI information and control information reception performance for JT support of PDSCH.
Fig. 18 illustrates an example of antenna port configuration and resource allocation for PDSCH transmission using cooperative communication in a wireless communication system according to an embodiment of the present disclosure.
Referring to fig. 18, an example of PDSCH transmission is described for each Joint Transmission (JT) technique, and an example of radio resource allocation is shown for each TRP.
Referring to fig. 18, an example N000 of coherent joint transmission (C-JT) supporting coherent precoding between individual cells, TRPs, or/and beams is shown.
In the case of C-JT, a single data (PDSCH) is transmitted from TRP a N005 and TRP B N010 to terminal N015, and joint precoding may be performed among a plurality of TRPs. This may mean that TRP a N005 and TRP B N010 transmit DMRS through the same DMRS port to transmit the same PDSCH. For example, TRP a N005 and TRP B N010 may transmit DMRS to the terminal through DMRS port a and DMRS port B, respectively. In this case, the terminal may receive one piece of DCI information for receiving one PDSCH demodulated based on DMRS transmitted through DMRS ports a and B.
Fig. 18 shows an example N020 of non-coherent joint transmission (NC-JT) supporting non-phase interference coding between individual cells, TRPs, or/and beams for PDSCH transmission.
In the case of NC-JT, PDSCH is transmitted to terminal N035 for each cell, TRP, or/and beam, and separate precoding may be applied to each PDSCH. Each cell, TRP or/and beam transmits a different PDSCH or different PDSCH layer to the terminal compared to single cell, TRP or/and beam transmissions to improve throughput. In addition, each cell, TRP or/and beam may repeatedly transmit the same PDSCH to the terminal to improve reliability as compared to single cell, TRP or/and beam transmission. For ease of description, cells, TRPs, and/or beams are collectively referred to as TRPs.
In this case, various radio resource allocations may be considered, such as a case where all frequency and time resources of the plurality of TRPs used to transmit the PDSCH are the same (N040), a case where frequency and time resources of the plurality of TRPs used do not overlap at all (N045), or a case where some frequency and time resources of the plurality of TRPs used overlap (N050).
For NC-JT support, DCI of various forms, structures, and relationships may be considered to simultaneously allocate multiple PDSCH to one UE.
Fig. 19 illustrates an example of a Downlink Control Information (DCI) configuration for NC-JT in which respective TRPs transmit different PDSCH or different PDSCH layers to terminals in a wireless communication system according to an embodiment of the present disclosure.
Referring to fig. 19, case #1 (N100) is an example in which, in the case where different (N-1) PDSCHs are transmitted from (N-1) additional TRPs (TRP #1 to trp# (N-1)) in addition to a service TRP (TRP # 0) used when transmitting a single PDSCH, control information of a PDSCH transmitted from (N-1) additional TRPs is transmitted independently of control information of a PDSCH transmitted from the service TRP. That is, the terminal may obtain control information of PDSCH transmitted from different TRPs (dci#0 to dci# (N-1)) through independent DCIs (dci#0 to dci# (N-1)). The independent DCI may have the same format or different formats, and may have the same payload or different payloads. In case #1 described above, the degree of freedom of control or allocation of each PDSCH may be fully ensured, but when the respective DCIs are transmitted in different TRPs, coverage difference of each DCI may occur and reception performance may be deteriorated.
Case #2 (N105) is an example in which, in the case where different (N-1) PDSCHs are transmitted among (N-1) additional TRPs (TRP #1 to trp# (N-1)) in addition to a service TRP (TRP # 0) used when a single PDSCH is transmitted, several pieces of control information (DCI) of the PDSCH transmitted from (N-1) additional TRPs are transmitted, respectively, and each DCI depends on control information of the PDSCH transmitted from the service TRP.
For example, in the case where dci#0 corresponds to control information of PDSCH transmitted from service TRP (trp#0), all information elements of DCI format 1_0, DCI format 1_1, and DCI format 1_2 are included, but in the case where shortened DCIs (sdi#0 to sdi# (N-2)) corresponds to control information of PDSCH transmitted from cooperative TRP (trp#1 to trp# (N-1)), only some information elements of DCI format 1_0, DCI format 1_1, and DCI format 1_2 may be included. Accordingly, in the case of scdci transmitting control information of PDSCH transmitted in cooperative TRPs, a payload is small compared to conventional DCI (ncdci) transmitting PDSCH-related control information transmitted from a serving TRP, and thus, a reserved bit may be included compared to ncdci.
In case #2 described above, the degree of freedom of control or allocation of each PDSCH may be limited according to the content of the information element included in the sdi, but since the reception performance of the sdi is superior to that of the nci, the occurrence probability of coverage difference of each DCI may be reduced.
Case #3 (N110) is an example in which, in the case where (N-1) PDSCH is transmitted from (N-1) additional TRPs (TRP #1 to TRP # (N-1)) instead of the service TRP (TRP # 0) used when transmitting a single PDSCH, one piece of control information of PDSCH of (N-1) additional TRPs is transmitted, and the DCI depends on the control information of PDSCH transmitted from the service TRP.
For example, in the case where dci#0 corresponds to control information of PDSCH transmitted from service TRP (trp#0), all information elements of DCI format 1_0, DCI format 1_1, DCI format 1_2 are included, and in the case of control information of PDSCH transmitted from cooperative TRP (trp#1 to trp# (N-1)), only some information elements of DCI format 1_0, DCI format 1_1, DCI format 1_2 may be collected and transmitted in one piece of "secondary" DCI (sdi). For example, the sdi may include at least one of HARQ related information, such as frequency domain resource allocation, time domain resource allocation, and MCS of cooperative TRP. In addition, for information not included in the scdci, such as a bandwidth part (BWP) indicator or a carrier indicator, the information may follow the DCI (dci#0, regular DCI, and ncdci) serving the TRP.
In case #3, the degree of freedom of control or allocation of each PDSCH may be limited according to the content of the information element included in the sdi, but compared to case #1 (N100) or case #2 (N105), the reception performance of the sdi may be adjusted and the complexity of DCI blind decoding of the terminal may be reduced.
Case #4 (N115) is an example in which in the case where (N-1) PDSCHs are transmitted from (N-1) additional TRPs (TRP #1 to TRP # (N-1)) instead of the service TRP (TRP # 0) used when transmitting a single PDSCH, control information of the PDSCH transmitted from (N-1) additional TRPs and control information of the PDSCH transmitted from the service TRP are transmitted in the same DCI (long DCI). That is, the terminal may acquire control information of PDSCH transmitted from different TRPs (TRP #0 to trp# (N-1)) through a single DCI. In case #4 (N115), the complexity of DCI blind decoding of the terminal may not increase, but the degree of freedom of control or allocation per PDSCH may be low, such as a limited number of cooperative TRPs due to long DCI payload restrictions.
In the following description and embodiments, scdci may refer to various auxiliary DCIs, such as shortened DCI, auxiliary DCI, or conventional DCI (DCI formats 1_0 to 1_1 described above), including PDSCH control information transmitted from cooperative TRPs. The description is equally applicable to various auxiliary DCIs, if no special restrictions are specified.
In the following description and embodiments, the above case #1 (N100), case #2 (N105), and case #3 (N110), in which one or more DCIs (PDCCHs) are used for NC-JT support, are classified as NC-JT based on a plurality of PDCCHs, and the above case #4 (N115), in which a single DCI (PDCCH) is used for NC-JT support, is classified as NC-JT based on a single PDCCH. In PDSCH transmission based on multiple PDCCHs, CORESET in which DCI of service TRP (TRP # 0) is scheduled may be distinguished from CORESET in which DCI of cooperative TRP (TRP #1 to trp# (N-1)) is scheduled. As a method for dividing CORESETs, there may be a method for dividing each CORESET by a higher layer indicator, a method for dividing each CORESET by a beam configuration, or the like. In addition, in NC-JT based on a single PDCCH, instead of scheduling a plurality of PDSCHs through a single DCI, a single PDSCH having a plurality of layers may be scheduled and a plurality of layers may be transmitted from a plurality of TRPs. In this case, the connection relationship between a layer and the TRP for transmitting the corresponding layer may be indicated by a Transmission Configuration Indicator (TCI) indicator of the layer.
In embodiments of the present disclosure, when actually applied, the "cooperative TRP" may be replaced with various terms such as "cooperative panel" or "cooperative beam".
In the embodiments of the present disclosure, the term "case of applying NC-JT" may be interpreted in various ways according to circumstances, such as "a case where a terminal receives one or more PDSCH simultaneously in one BWP", "a case where a terminal indicates reception of PDSCH simultaneously in one BWP based on two or more Transmission Configuration Indicators (TCIs)" and "a case where a PDSCH received by a terminal is associated with one or more DMRS port groups", etc., but for convenience of description, one expression is used for these cases.
In the present disclosure, the radio protocol structure for NC-JT may be used in various ways according to TRP deployment scenarios. For example, if there is no backhaul delay or backhaul delay is small between cooperative TRPs, a method using a structure based on MAC layer multiplexing (CA-like method) similar to fig. 17 (S10) may be used. On the other hand, when the backhaul delay between cooperative TRPs is too large to be ignored (for example, when CSI exchange or scheduling information exchange between cooperative TRPs requires 2ms or more), a method (DC-like method) of securing delay robust characteristics by using an independent structure of each TRP from the RLC layer may be used similarly to S20 of fig. 17.
A terminal supporting C-JT/NC-JT may receive C-JT/NC-JT related parameters, setting values, etc. from a higher layer configuration, and may set RRC parameters of the terminal based thereon. For higher layer configurations, the terminal may utilize UE capability parameters, such as tci-StatePDSCH. Here, the UE capability parameter (e.g., TCI-StatePDSCH) may define TCI states for PDSCH transmission purposes, where the number of TCI states may be configured as 4, 8, 16, 32, 64, and 128 in FR1, and as 64 and 128 in FR2, and in the configured number, a maximum of eight states may be configured that may be indicated by a 3-bit TCI field of DCI through a MAC CE message. The maximum value 128 may refer to a value indicated by maxnumberconfiguredtstatestateper cc included in tci-StatePDSCH parameters in UE capability signaling. The serial configuration operation from the higher layer configuration to the MAC CE configuration may be applied to a beamforming indication or a beamforming handover command of at least one PDSCH in one TRP.
[ multiple DC-based multiple TRP ]
According to embodiments of the present disclosure, a downlink control channel for NC-JT transmission may be configured based on multiple PDCCHs.
In NC-JT based on multiple PDCCHs, there may be CORESET or search space classified for each TRP when DCI is transmitted to schedule PDSCH of each TRP. The CORESET or search space for each TRP may be configured for at least one of the following.
In one example case, the higher layer index configuration of each CORESET: the CORESET configuration information configured via higher layers may include index values, and TRP of a PDCCH transmitted from a corresponding CORESET may be classified by the index value configured for each CORESET. That is, in a group of CORESETs having the same higher layer index value, it can be considered that the same TRP transmits a PDCCH or a PDCCH scheduling a PDSCH of the same TRP is transmitted. The above index of each CORESET may be named coresetpoolndex, and for CORESETs configured with the same coresetpoolndex value, the PDCCH may be considered to be transmitted from the same TRP. In the case of CORESET where the coresetpoinlindex value is not configured, the default value of coresetpoinlindex may be considered to be configured, and may be 0.
In one example case, configuration of multiple PDCCH-Configs: multiple PDCCH configurations may be configured in one BWP, and each PDCCH configuration may include a PDCCH configuration of each TRP. That is, the CORESET list of each TRP and/or the search space list of each TRP may be configured in one PDCCH-Config, and one or more CORESETs and one or more search spaces included in one PDCCH-Config may be considered to correspond to a specific TRP.
In one example case, CORESET beam/beam group configuration: the TRP corresponding to each CORESET may be classified by the beam or beam group set for that CORESET. For example, when the same TCI state is configured for a plurality of CORESETs, it may be considered that the corresponding CORESETs are transmitted through the same TRP, or PDCCHs scheduling PDSCH of the same TRP are transmitted in the corresponding CORESETs.
In one example case, search space beam/beam group configuration: a beam or beam group may be configured for each search space, and the TRP of each search space may be classified by beam or beam group. For example, when the same beam/beam group or TCI state is configured in a plurality of search spaces, the same TRP may be considered to transmit a PDCCH in the search space or a PDCCH scheduling a PDSCH of the same TRP may be transmitted in the search space.
By classifying CORESET or search space of each TRP as described above, PDSCH and HARQ-ACK information of each TRP can be classified, and by this, an independent HARQ-ACK codebook can be generated for each TRP and an independent PUCCH resource can be used.
The above configuration may be independent for each cell or each BWP. For example, two different coresetpoolndex values are configured in the PCell, but coresetpoolndex values may not be configured in a particular SCell. In this case, NC-JT transmission is configured in the PCell, but NC-JT transmission is not configured in scells where coreetpolindex values are not configured.
[ multiple TRP based on Single DCI ]
In another embodiment of the present disclosure, the downlink beam for NC-JT transmission may be configured based on a single PDCCH.
In NC-JT based on a single PDCCH, PDSCH transmitted by multiple TRPs via one DCI may be scheduled. In this case, as a method of indicating the number of TRPs for transmitting the corresponding PDSCH, the number of TCI states may be used. That is, NC-JT transmission based on a single PDCCH may be considered when the number of TCI states indicated in DCI scheduling PDSCH is two, and single TRP transmission may be considered when the number of TCI states is one. The TCI state indicated by the DCI may correspond to one or both of the TCI states activated via the MAC-CE. When the TCI state of the DCI corresponds to two TCI states activated via MAC-CE, a correspondence between the TCI state activated via MAC-CE and a TCI code point indicated by the DCI, and there may be two TCI states activated via MAC-CE, corresponding to the TCI code point.
The configuration may be independent for each cell or each BWP. For example, there may be at most two active TCI states corresponding to one TCI code point in one PCell, but there may be at most one active TCI state corresponding to one TCI code point in one particular SCell. In this case, NC-JT transmission may be considered to be configured for the PCell, but NC-JT transmission is not configured in the SCell.
According to the description of PUSCH and aperiodic/semi-persistent CSI report, in the current Rel-15/16NR, aperiodic CSI report may be multiplexed to only the first PUSCH or the first actual repetition according to the repeated PUSCH transmission type a or B. That is, the aperiodic CSI report may be transmitted to a single TRP by using only a single transmission beam. In Rel-17FeMIMO, in order to obtain better reliability during repetition of PUSCH transmission, a method is being discussed in which spatial diversity can be ensured by applying a plurality of transmission beams to PUSCH repetition by supporting PUSCH repetition based on a plurality of TRP extensions. In the corresponding discussion, it is mainly discussed that repeated PUSCH transmission for a plurality of TRPs is supported by repeatedly applying different beams to each PUSCH based on the existing repeated PUSCH transmission type a or B. In this case, in the case of the repeated PUSCH transmission type a or B based on a plurality of TRPs, when aperiodic CSI reports are multiplexed and transmitted and multiplexing is repeatedly performed only on the first PUSCH in the existing Rel-15/16 scheme, transmission to the corresponding TRP may fail due to channel degradation factors such as blocking, and thus, a method for performing transmission multiplexed to each TRP may be required.
In this case, as described above, due to the polar code characteristic, it is possible to combine after receiving from the base station only when the time and frequency resource allocation values (i.e., the number of Resource Elements (REs) allocated to the terminal) of the respective repeated PUSCH transmissions are identical to each other. Therefore, when aperiodic CSI reports are multiplexed while transmitting a transport block by using the repetition PUSCH transmission type a or B, a method for determining PUSCH repetition to which the aperiodic CSI reports are to be multiplexed among all PUSCH repetitions may be required. In addition, in the case of multiplexing aperiodic or semi-persistent CSI reports when no transport block is transmitted in the repetition PUSCH transmission type B, at least one transmission is ensured for each TRP even if the PUSCH repetition number is configured to be greater than 1. In the present disclosure, when aperiodic/semi-persistent CSI reports are transmitted or multiplexed, a method of multiplexing or transmitting CSI reports for repeated PUSCH transmission in consideration of a plurality of TRPs is provided, so that CSI reception reliability in a base station can be enhanced. The detailed process is described in the examples below.
In the following description of the present disclosure, for convenience of description, cells, transmission points, panels, beams, and/or transmission directions, which may be classified by higher layer/L1 parameters such as an indicator (such as a cell ID, TRP ID, or panel ID) or such as TCI status or station relation information, are collectively referred to as Transmission Reception Points (TRP). Accordingly, when actually applied, TRP may be appropriately replaced with one of the above terms.
Hereinafter, in the present disclosure, in determining whether a terminal applies cooperative communication, various methods may be used, including a method in which a PDCCH for allocating a PDSCH to which cooperative communication is applied has a specific format, a method in which a PDCCH for allocating a PDSCH to which cooperative communication is applied includes a specific indicator indicating whether cooperative communication is applied, a method in which a PDSCH to which cooperative communication is applied is scrambled with a specific RNTI, or a method in which cooperative communication is assumed to be applied within a specific period indicated via a higher layer. Hereinafter, for convenience of description, reception of PDSCH to which cooperative communication is applied by a terminal based on conditions similar to the above description is referred to as NC-JT case.
Hereinafter, embodiments of the present disclosure are described with reference to the drawings. Hereinafter, the base station is an entity performing resource allocation of the terminal, and may be at least one of a gNode B, a gNB, an eNode B, a node B, a Base Station (BS), a radio access unit, a base station controller, or a node on a network. A terminal may include a User Equipment (UE), a Mobile Station (MS), a cellular phone, a smart phone, a computer, or a multimedia system capable of performing a communication function. Hereinafter, embodiments of the present disclosure will be described using a 5G system as an example, but embodiments of the present disclosure may be applied to other communication systems having similar technical backgrounds or channel types. For example, other communication systems may include mobile communication technologies developed after LTE or LTE-a mobile communication and 5G. Thus, embodiments of the present disclosure may also be applied to different communication systems with some modifications, as determined by one skilled in the art, without the extent of the modifications significantly departing from the scope of the disclosure. The present disclosure applies to FDD and TDD systems.
In addition, in describing the present disclosure, if a detailed description of related well-known functions or configurations is considered to unnecessarily obscure the gist of the present disclosure, a detailed description thereof will be omitted. Furthermore, the terms described below have been defined by considering functions in the present disclosure, and may be changed according to the intention or practice of a user, operator. Accordingly, each term should be defined based on the contents of the entire specification.
Hereinafter, in describing the present disclosure, higher layer signaling may be signaling corresponding to at least one of the following signaling methods or a combination of one or more methods:
-a Master Information Block (MIB);
-a System Information Block (SIB) or SIB X (x=1, 2.);
-Radio Resource Control (RRC); and
-a Medium Access Control (MAC) Control Element (CE).
In addition, the L1 signaling may be signaling corresponding to at least one of signaling methods using a physical layer channel, or the following signaling, or a combination of one or more methods:
-a Physical Downlink Control Channel (PDCCH);
-Downlink Control Information (DCI);
-UE specific DCI;
-group common DCI;
-common DCI;
scheduling DCI (e.g., DCI for scheduling downlink or uplink data);
Non-scheduling DCI (e.g., DCI not used to schedule downlink or uplink data);
-a Physical Uplink Control Channel (PUCCH); and
uplink Control Information (UCI).
Hereinafter, in the present disclosure, determining the priority between a and B may be mentioned in various ways, such as selecting one having a higher priority than another according to a predetermined priority rule to perform an operation corresponding thereto, or omitting or discarding an operation having a lower priority.
Hereinafter, in the present disclosure, the above examples will be described by a plurality of embodiments, but the embodiments are not independent and one or more embodiments may be applied simultaneously or in combination.
< first embodiment: method of repeated PUSCH transmission considering multiple TRPs >
In a first embodiment of the present disclosure, a method of indicating L1 signaling and configuring higher layer signaling for repeated PUSCH transmission in consideration of multiple TRPs is described. The repeated PUSCH transmission considering the multiple TRP may be operated by an indication based on a single DCI or multiple DCIs, and the repeated PUSCH transmission based on a single DCI and multiple DCIs are described in (1-1) th and (1-2) th embodiments, respectively. In addition, in the (1-3) th embodiment of the present disclosure, a method for authorizing PUSCH transmission in consideration of repeated configuration of multiple TRPs is described. In addition, in the (1-4) th embodiment of the present disclosure, a method for configuring SRS resource sets for repeating PUSCH transmission in consideration of multiple TRPs is described.
< example (1-1): method of considering repeated PUSCH transmission of multiple TRP based on single DCI >
In the (1-1) th embodiment, as an embodiment of the present disclosure, a repeated PUSCH transmission method considering multiple TRPs based on a single DCI is described. It is possible that the terminal may report to the base station a repeated PUSCH transmission considering multiple TRPs based on a single DCI through the UE capability report. The base station may configure a type of repeated PUSCH transmission to be used for a terminal that has reported corresponding UE capabilities (e.g., UE capabilities that repeat PUSCH transmissions considering multi-TRP support based on a single DCI) through higher layer signaling. In this case, higher layer signaling may be configured by selecting one of the repeated PUSCH transmission type a and the repeated PUSCH transmission type B.
In the case of the method of repeated PUSCH transmission considering a single TRP in Rel-15/16, both codebook-based and non-codebook-based transmission schemes are performed based on a single DCI. When performing codebook-based PUSCH transmission, the terminal may apply the same value to each repeated PUSCH transmission by using SRI or TPMI indicated by a single DCI. In addition, when performing non-codebook based PUSCH transmission, the terminal may apply the same value to each repeated PUSCH transmission by using the SRI indicated by the single DCI. For example, when codebook-based PUSCH transmission and repeated PUSCH transmission type a are configured via higher layer signaling and a time resource allocation index, SRI index 0, and TPMI index 0 having the number of repeated PUSCH transmissions configured to four are indicated via DCI, the terminal applies SRI index 0 and TPMI index 0 to all four repeated PUSCH transmissions.
Here, the SRI may be associated with a transmission beam, and the TPMI may be associated with a transmission precoder. Unlike the method of considering repeated PUSCH transmission of a single TRP, the method of considering repeated PUSCH transmission of multiple TRP may require that different transmission beams and transmission precoders are applied to the transmissions to the respective TRPs. Accordingly, the terminal may receive an indication of a plurality of SRIs or TPMI via DCI, apply the indication to each repeated PUSCH transmission, and perform repeated PUSCH transmission considering multiple TRPs.
When a method of considering repeated PUSCH transmission of multiple TRPs based on a single DCI is indicated to a terminal, the following method may be regarded as a method for indicating a plurality of SRIs or TPMI for a codebook-based or non-codebook-based PUSCH transmission method to the terminal.
Method 1 transmission of a single DCI in which a plurality of SRI or TPMI fields exist
To support repeated PUSCH transmission considering multiple TRPs based on a single DCI, a base station may transmit DCI in which multiple SRI or TPMI fields exist to a terminal. Such DCI has a new format (e.g., DCI format 0_3) or an existing format (e.g., DCI format 0_1, 0_2), but if additional higher layer signaling (e.g., signaling for being able to determine whether multiple SRIs or TPMI fields can be supported) is configured and there is a corresponding configuration, DCI in which only one SRI field and one TPMI field already exist may have multiple SRIs or TPMI fields. For example, when a codebook-based PUSCH transmission is configured via higher layer signaling and a terminal receives a configuration capable of determining whether a plurality of SRI or TPMI fields can be supported, the terminal may receive DCI having two SRI fields and two TPMI fields and having a new format or an existing format, via higher layer signaling, in order to perform codebook-based repeated PUSCH transmission considering multiple TRPs.
In another example, when a non-codebook based PUSCH transmission is configured via higher layer signaling and a terminal receives higher layer signaling enabling a determination of whether multiple SRI or TPMI fields can be supported, the terminal may receive DCI having two SRI fields and having a new format or an existing format in order to perform non-codebook based repeated PUSCH transmission in consideration of multiple TRPs. When multiple SRI fields are used for both codebook-based and non-codebook-based PUSCH transmissions, two or more SRS resource sets corresponding to higher layer signaling and having uses configured as a codebook or a non-codebook may be configured, wherein the SRI fields may respectively indicate SRS resources and the SRS resources may be respectively included in two different SRS resource sets. A plurality of SRS resource sets will be described in detail in embodiment (1-4).
Method 2 transmission of DCI using enhanced SRI and TPMI fields
In order to support a method of considering repeated PUSCH transmission of multiple TRPs based on a single DCI, a terminal may receive a MAC-CE for supporting an enhanced SRI or TPMI field from a base station. The MAC-CE may include information indicating an interpretation of changing a code point in a DCI field such that a plurality of transmission beams are indicated for a specific codebook in an SRI field in the DCI or a plurality of transmission precoders are indicated for a specific codebook in a TPMI field. Two methods for indicating multiple transmission beams can be considered:
-receiving a MAC-CE for performing an activation such that a specific code point in the SRI field indicates one SRS resource connected to a plurality of pieces of SRS spatial relation information; and
-receiving a MAC-CE for performing an activation such that a specific code point in the SRI field indicates a plurality of SRS resources connected to one piece of SRS spatial relation information.
When a plurality of SRS resources are indicated by using the enhanced SRI field, transmission power adjustment parameters of the SRS resources are configured for each SRS resource set, and thus, in order to configure different transmission power adjustment parameters for TRPs, respectively, the individual SRS resources may exist in different SRS resource sets. Thus, there may be two or more SRS resource sets corresponding to higher layer signaling and having utility to be configured as a codebook or non-codebook.
< example (1-2): method for repeated PUSCH transmission considering multiple TRPs based on multiple DCIs >
In the (1-2) th embodiment, as an embodiment of the present disclosure, a method of considering repeated PUSCH transmission of multiple TRPs based on multiple DCI is described. As described above, all the repeated PUSCH transmission methods in Rel-15/16 consider a single TRP, and thus, the transmission beam, the transmission precoder, the resource allocation, and the power adjustment parameters may use the same values for each repeated transmission. However, during repeated PUSCH transmission considering multiple TRPs, it may be necessary to apply different PUSCH transmission related parameters configured via higher layer signaling or indicated by DCI, respectively, to the TRPs for each repeated PUSCH transmission to multiple TRPs. For example, when a plurality of TRPs exist in different directions from a terminal, a transmission beam or a transmission precoder may be different, and thus, it is necessary to configure or indicate the transmission beam or the transmission precoder for each TRP.
In another example, when the plurality of TRPs are spaced apart from the terminal by different distances, an independent power adjustment scheme between the plurality of TRPs and the terminal may be required, and thus, different time/frequency resource allocation may be performed. For example, a relatively small number of RBs and a relatively large number of symbols may be allocated to TRPs at a relatively long distance in order to increase the power of each RE, as compared to a specific TRP. Thus, transmitting different pieces of information applied to each TRP to a terminal through a single DCI may result in the length of bits of the corresponding DCI being too long, and thus, indicating repeated PUSCH transmissions to the terminal via multiple DCIs may be more efficient.
It is possible that the terminal may report to the base station as a UE capability report considering repeated PUSCH transmissions based on multiple TRPs of multiple DCI. The base station may send a notification to the terminal such that the terminal performs a repeated PUSCH transmission taking into account multiple TRPs over multiple DCI, relative to a corresponding UE capability that has been reported (e.g., a UE capability taking into account multiple TRPs based on multiple DCI supporting repeated PUSCH transmissions) by using the configuration via higher layer signaling, the indication via L1 signaling, and the configuration and indication via a combination of higher layer signaling and L1 signaling. The base station may configure or indicate a method of repeating PUSCH transmission using multi-TRP considering multi-DCI based as described below.
When PUSCH transmission is performed considering multi-TRP based on multi-DCI, a terminal may expect several pieces of time/frequency resource allocation information indicated via each DCI to be different from each other considering TRPs spaced different distances from the terminal. The terminal may report to the base station through UE capabilities whether different time/frequency resource allocations can be supported. The base station may configure whether different time/frequency resource allocation can be supported for the terminal via higher layer signaling, and the terminal having received the configuration may expect several pieces of time/frequency resource allocation information indicated via each piece of DCI to be different from each other.
In this case, the terminal may receive a configuration or an indication from the base station considering repeated PUSCH transmission of multiple TRPs based on multiple DCIs in consideration of a higher layer signal configuration and conditions between multiple DCI fields. When the transmission beam and the transmission precoder information are indicated by the multi-DCI, the SRI and TPMI in the first received DCI may be applied at a first time when the transmission beam mapping scheme in the second embodiment below is applied, and the SRI and TPMI in the second received DCI may be applied at a second time when the transmission beam mapping scheme in the second embodiment below is applied.
The base station may configure a coretpoolindex corresponding to higher layer signaling to the terminal for each CORESET, and upon receipt of the CORESET, the terminal may identify from the coretpoolindex the TRP that sent the corresponding CORESET. For example, when coresetpoinlindex is configured to 0 in CORESET #1 and coresetpoinlindex is configured to 1 in CORESET #2, the terminal may identify that CORESET #1 is transmitted from TRP #0 and CORESET #2 is transmitted from TRP # 1. In addition, the fact that DCI transmitted in CORESET with coresetpoolndex values configured to 0 and 1, respectively, indicates repeated PUSCH may be implicitly indicated by a condition between specific fields in the plurality of DCIs.
For example, when the HARQ process number field value and NDI field value in a plurality of DCIs transmitted from a base station to a terminal are the same, the terminal may implicitly consider the plurality of DCIs to perform scheduling of repeated PUSCH considering multiple TRPs. When the HARQ process sequence number field value is the same and the NDI field value is the same, there may be a limitation on reception of multiple pieces of DCI. For example, a maximum interval between multiple DCI receptions may be defined to be within one or more specific slot sequence numbers or one or more specific symbol sequence numbers. In this case, the terminal may perform PUSCH transmission based on a minimum transport block size calculated (or identified) based on different time/frequency resource allocation information blocks indicated by the plurality of DCIs.
< example (1-3): method of authorizing PUSCH transmission considering repeated configuration of multiple TRP >
In the (1-3) th embodiment of the present disclosure, as an embodiment of the present disclosure, a method for authorizing PUSCH transmission in consideration of repeated configuration of multiple TRPs is described. The terminal may report to the base station whether or not authorized PUSCH transmission considering repeated configuration of the multi-TRP is performed as UE capability. The base station may configure the terminal with the authorized PUSCH transmission considering the repeated configuration of the multi-TRP via higher layer signaling, indicate the same transmission via L1 signaling, or configure and indicate the same transmission via a combination of higher layer signaling and L1 signaling by using the following various methods.
Method 1 activation of a single configured grant configuration based on a single DCI
Method 1 corresponds to a method for indicating a plurality of SRIs or TPMI to a terminal based on a single DCI, and activating an authorized configuration of a single configuration in addition to the indication. The method of indicating a plurality of SRIs or TPMI based on a single DCI may follow the method in embodiment (1-1), and when there is only one configured grant configuration in the terminal, all bits in the HARQ process number field and redundancy version field in the corresponding DCI may be indicated with zeros. When there are multiple configurations of grant configurations in the terminal and one of the configurations is activated as a corresponding DCI, the HARQ process sequence number field in the corresponding DCI may indicate the grant configuration index of the configuration and all bits in the redundancy version field may be indicated by zeros. The terminal may perform mapping of each repeated transmission of the activated configuration grant PUSCH to the transmission beam and the transmission precoder by using a plurality of SRIs or TPMI indicated by a single DCI according to the transmission beam mapping method in the following second embodiment.
Method 2 activation of a single configuration grant configuration based on multiple DCIs
Method 2 corresponds to a method for indicating a plurality of SRIs or TPMI to a terminal based on a multi-DCI, and activating an authorized configuration of a single configuration in addition to the indication. The method of indicating a plurality of SRIs or TPMI based on the multi-DCI may follow the method in embodiment (1-2), and when there is only one configured grant configuration in the terminal, all bits in the HARQ process number field and redundancy version field in the corresponding multi-DCI may be indicated with zeros. When there are multiple configurations of grant configurations in the terminal and one of the configurations is activated as a corresponding multi-DCI, all HARQ process number fields in the corresponding multi-DCI may indicate the same configuration of grant configuration index and all bits in all redundancy version fields in the corresponding multi-DCI may be indicated by zero.
The NDI field may be the same value except for the HARQ process sequence number field according to the condition of the DCI field during multi-DCI based repeated PUSCH transmission. The terminal may perform mapping of each repeated transmission of the activated configuration grant PUSCH to the transmission beam and the transmission precoder by using a plurality of SRIs or TPMI indicated by the multi-DCI according to the following transmission beam mapping method. For example, when the transmission beam and the transmission precoder-related information indicated by the first received DCI correspond to sri#1 and tpmi#1, the transmission beam and the transmission precoder-related information indicated by the second received DCI correspond to sri#2 and tpmi#2, and the transmission beam mapping scheme configured via higher layer signaling is cyclic, the terminal may apply sri#1 and tpmi#1 to odd (1, 3,5,) transmission of the activated configuration grant PUSCH and may apply sri#2 and tpmi#2 to even (2, 4,6,) transmission of the repeated transmission in order to perform PUSCH transmission.
Method 3 activation of multiple configuration grant configurations based on multiple DCIs
Method 3 corresponds to a method for indicating a plurality of SRIs or TPMI to a terminal based on a multi-DCI and activating an authorized configuration of a plurality of configurations in addition to the indication. The method for indicating a plurality of SRIs or TPMI based on multi-DCI may follow the method in embodiment (1-2). When there are multiple configured grant configurations in the terminal, the grant configuration index of each configuration may be indicated by the HARQ process sequence number field in each DCI. In addition, all bits in all redundancy version fields in the corresponding multi-DCI may be indicated by zeros.
The NDI field may be the same value except for the HARQ process sequence number field according to the condition of the DCI field during multi-DCI based repeated PUSCH transmission. The terminal may receive MAC-CE signaling indicating (commanding) a connection between the grant configuration activated as multiple configurations of the multi-DCI. Once HARQ-ACK transmission for MAC-CE signaling is performed, the terminal may receive multi-DCI from the base station after 3ms, and when a grant configuration index of a configuration indicated by each DCI is identical to a grant configuration index of a configuration of an indication (command) of a connection that has been received via MAC-CE signaling, repeated PUSCH transmission considering multi-TRP may be performed based on the grant configuration of the corresponding indicated configuration.
In this case, the authorized configuration of the plurality of configurations connected to each other may share the same value for some configurations. For example, repK corresponding to higher layer signaling represents the number of retransmissions, repK-RV corresponding to higher layer signaling represents the sequence of redundancy versions during the retransmissions, and periodicity of higher layer signaling corresponding to periodicity representing the retransmissions may be configured to have the same value in the configuration grant configuration of the connection.
< examples (1-4): configuration method of SRS resource set for repeated PUSCH transmission considering multiple TRPs >
In the (1-4) th embodiment, as an embodiment of the present disclosure, a method for configuring SRS resource sets for repeating PUSCH transmission in consideration of multiple TRPs is described. SRS power adjustment parameters (e.g., alpha, p0, pathlossReferenceRS, SRS-powercontrol adjustment states, etc., which may be configured via higher layer signaling) may vary for each SRS resource set, and thus, to make different SRS power adjustments to the TRPs during repeated PUSCH transmissions considering multiple TRPs, the number of SRS resource sets may be increased to a value equal to or greater than two, and different SRS resource sets may be used to support different TRPs. The SRS resource set allocation method considered in the present embodiment is applicable to the (1-1) to (1-3) th embodiments.
When performing repeated PUSCH transmission considering multiple TRPs based on a single DCI, multiple SRIs indicated by the single DCI may be selected from SRS resources present in different SRS resource sets. For example, when two SRIs are indicated by a single DCI, a first SRI may be selected from SRS resource set #1 and a second SRI may be selected from SRS resource set # 2.
When performing repeated PUSCH transmissions that take into account multiple TRPs based on multiple DCIs, the respective SRIs indicated by the two DCIs may be selected from SRS resources present in different SRS resource sets, and the SRS resource sets may be explicitly or implicitly connected to (or may explicitly or implicitly correspond to) higher layer signaling (e.g., coresetpooolindex) that represents each TRP. As an explicit connection method, a coresetpoolndex value may be configured in an SRS resource set configuration configured via higher layer signaling, and a terminal may be notified of a semi-static connection state between CORESET and SRS resource set.
In another example, as a more explicit connection method, MAC-CE that activates a connection between SRS resource set and a specific CORESET (including both the case where coreetpolindex value is configured to 0 or 1 and the case where coresetpolindex value is not configured) may be used. After 3ms from the point in time when the terminal transmits the HARQ-ACK for the MAC-CE signaling for activating the connection between the SRS resource set and the specific CORESET (including both the case where the coresetpolindex value is configured to 0 or 1 and the case where the coresetpolindex value is not configured), the terminal may consider the connection between the SRS resource set and the corresponding CORESET to be activated.
As an implicit method, an implicit connection state is assumed by using a specific condition between the index of the SRS resource set and coresetpoolndex. For example, assuming that the terminal has received both configurations of SRS resource sets #0 and #1, the terminal may assume that no corespiolindex is configured or CORESET with corespiolindex configured to 0 is connected to SRS resource set #0 and may assume that CORESET with corespiolindex configured to 1 is connected to SRS resource set #1.
For methods based on a single DCI or multiple DCIs, a terminal that explicitly or implicitly configures or indicates a connection between different SRS resource sets and corresponding TRPs may expect a SRS-powercontrol Adjust states value configured via higher layer signaling in each SRS resource set to be configured as sameAsFci2 or may not expect a SRS-powercontrol Adjust states value to be configured as secparteclosedloop. In addition, for each SRS resource set, the terminal may expect the same purpose configured via higher layer signaling to be configured with a codebook or a non-codebook.
< examples (1-5): codebook-based determination of dynamic switching method for PUSCH transmission considering single TRP or PUSCH transmission considering multiple TRP >
In the (1-5) th embodiment, as an embodiment of the present disclosure, a dynamic switching method is described that considers PUSCH transmission of a single TRP or PUSCH transmission of multiple TRP based on codebook determination.
According to (1-1) to (1-4) embodiments, a base station may receive a UE capability report from a terminal that may perform codebook-based repeated PUSCH transmission considering multiple TRPs based on a single DCI, and may configure the terminal with higher layer signaling for performing repeated PUSCH transmission through the multiple TRPs. In this case, as described in (1-4) th embodiment, during repeated PUSCH transmission considering multiple TRPs based on a single DCI, the base station may transmit a single DCI including a plurality of SRI fields to the terminal to indicate SRS resources existing in different SRS resource sets.
Multiple SRI fields can be interpreted in the same way as each NR version 15/16. More specifically, the first SRI field may select SRS resources from a first set of SRS resources, and the second SRI field may select SRS resources from a second set of SRS resources. Similar to the plurality of SRI fields, to perform repeated PUSCH transmission considering multiple TRPs, the base station may transmit a single DCI including a plurality of TPMI fields to the terminal in order to select a TPMI corresponding to the SRS resource indicated by each SRI field. In this case, the plurality of TPMI fields may be indicated via the same DCI as the DCI including the plurality of SRI fields. The plurality of TPMI used during PUSCH transmission to each TRP may be selected by:
Method 1 each TPMI field can be interpreted in the same way as NR version 15/16. For example, the first TPMI field may indicate TPMI index and layer information of the SRS resource indicated by the first SRI field, and the second TPMI field may indicate TPMI index and layer information of the SRS resource indicated by the second SRI field.
Method 2 in the same method as NR version 15/16, the first TPMI field may indicate a TPMI index and layer information of the SRS resource indicated by the first SRI field. Unlike the first TPMI field, the second TPMI field selects a TPMI index for the same layer as that indicated by the first TPMI field, and may not indicate layer information and indicates TPMI index information of SRS resources indicated by the second SRI field.
In case that a plurality of TPMI is selected through the method 2, the bit length of the second TPMI field may be shorter than the bit length of the first TPMI field. This is because the second TPMI field indicates one value (index) in the same TPMI index candidates as the layer indicated by the first TPMI field, and thus, layer information may not be indicated.
The terminal may receive a single DCI including a plurality of SRI fields and a plurality of TPMI fields and support a dynamic switching method for determining a repeated PUSCH transmission considering a plurality of TRPs or determining a repeated PUSCH transmission considering a single TRP based on the received single DCI. The terminal may support dynamic handover by using a reserved value having no meaning among values that may be possessed by a plurality of TRMI fields or SRI fields included in the received DCI. For example, when the bit length of the SRI field is 2 bits, a total of four cases may be represented, and in this case, each of the representable cases may be defined as a code point. In addition, if three of the total four code points have the meaning of SRI to be indicated and the remaining one code point has no meaning, the remaining code points may correspond to code points indicating reserved values (hereinafter, the code points indicating reserved values may be expressed as code points configured as "reserved"). As will be described in more detail below.
To describe a dynamic handover method that can be supported by reserved values in multiple TPMI fields, a case of four PUSCH antenna ports is assumed with one detailed example. In addition, it is assumed that the first TPMI field is configured with 6 bits, the higher layer parameter codebook subset is configured with fullyand partialanddnoncoupler, and indicates that the method is the same as NR version 15/16. In this case, in the first TPMI field, indexes 0 to 61 may be configured to indicate valid TPMI indexes and layer information, and indexes 62 and 63 may be configured to be reserved. If the second TPMI field includes TPMI index information remaining after excluding layer information as described in method 2 above, the second TPMI field may indicate only the TPMI index in case that a layer for PUSCH transmission according to the first TPMI field is limited to one value (e.g., one of 1 to 4).
In this case, the number of bits of the second TPMI field may be configured with reference to the number of bits that may represent a layer having the largest number of candidates among TPMI index candidates that may be configured for each layer. For example, layer 1 has the largest number of candidates according to an example in which layer 1 has 0 to 27 candidates, layer 2 has 0 to 21 candidates, layer 3 has 0 to 6 candidates, and layer 4 has 0 to 4 candidates. Accordingly, the number of bits of the second TPMI field may be configured to be 5 according to the number of TPMI index candidates of layer 1. According to the detailed description of the configuration of the second TPMI field, for example, when the layer 1 and the TPMI index according to the layer 1 are indicated by the second TPMI field, the terminal may interpret the second TPMI field as a code point indicating one value of the TPMI indexes 0 to 27 and a code point indicating a reserved value.
In another example, when layer 2 and the TPMI index according to layer 2 are indicated by the first TPMI field, the terminal may interpret the second TPMI field as a code point indicating one value of TPMI indexes 0 to 21 and a code point indicating a reserved value. In addition, for example, when layer 3 or layer 4 and a TPMI index according to layer 3 or layer 4 are indicated by the first TPMI field, the terminal may also interpret the second TPMI field in a similar manner to the above description. In this case, when there are two or more code points indicating a reserved value in the second TPMI field, the two code points indicating a reserved value may be used to indicate dynamic handover in addition to the code point indicating the TPMI index.
That is, among the code points of the second TPMI field configured with 5 bits, the penultimate code point (i.e., the 31 st code point in the example) corresponding to the code point indicating the reserved value may be used to indicate the repeated PUSCH transmission to the first TRP considering the single TRP, and the last code point (i.e., the 32 nd code point in the example) may be used to indicate the repeated PUSCH transmission to the second TRP considering the single TRP. In this case, layer information and TPMI index information for repeated PUSCH transmission considering a single TRP may be indicated to the terminal through the first TPMI field. The assumptions in the above description are for convenience of description, and the present disclosure is not limited thereto.
For convenience of description, according to an example in which the above detailed examples of two TRPs are summarized, a terminal may receive a single DCI including two SRI fields and two TPMI fields and perform dynamic handover according to a code point indicated by a second TPMI field. The terminal may perform repeated PUSCH transmission considering multiple TRPs if the code point of the second TPMI field indicates the TPMI index of the layer indicated by the first TPMI field. If the second TPMI field indicates that the penultimate code point corresponds to the code point indicating the reserved value, the terminal may perform repeated PUSCH transmission considering a single TRP of TRP 1, and may identify layer information and TPMI index for the codebook-based PUSCH transmission from the first TPMI field. If the second TPMI field indicates that the last code point corresponds to a code point indicating a reserved value, the terminal may perform repeated PUSCH transmission considering a single TRP of TRP 2, and may identify layer information and TPMI index information for codebook-based PUSCH transmission from the first TPMI field.
In the above example, the last two reserved code points of the second TPMI field are used to indicate dynamic handoff, but the embodiment is not limited thereto. In other words, dynamic switching may be indicated by using a code point indicating two different reserved values of the second TPMI field, and repeated PUSCH transmission of a single TRP in consideration of TRP 1 or repeated PUSCH transmission of a single TRP in consideration of TRP 2 may be mapped to the code point indicating each reserved value and indicated.
In addition, in the above example, it is described that the second TPMI field is determined according to method 2, but even in the case where the second TPMI field is determined in the same manner as NR version 15/16, as described in method 1, dynamic handover can be supported by using reserved code points of TPMI in the same manner as in the above example.
For example, if the number of code points indicating the reserved value of the second TPMI field is less than 2, the number of bits of the second TPMI field may be increased by 1, and the last-last code point and the last code point referring to the increased number of bits may be used to support dynamic handover.
When determining two TPMI fields according to method 1, a method for supporting dynamic handover according to whether each TPMI field is indicated as a code point indicating a reserved value may be additionally considered. That is, when the first TPMI field is indicated as a code point indicating a reserved value, the terminal may perform repeated PUSCH transmission of a single TRP in consideration of TRP2, and when the second TPMI field is indicated as a code point indicating a reserved value, the terminal may perform repeated PUSCH transmission of a single TRP in consideration of TRP 1. If both TPMI fields indicate a code point of TPMI, not a code point of a reserved value, the terminal may perform repeated PUSCH transmission considering multiple TRPs. If there is no code point with a reserved value, the number of bits of the TPMI field may be increased by 1, and the last code point referring to the increased number of bits may be used to support dynamic handover.
As another dynamic handover support method, two SRI fields may indicate dynamic handover, and two TPMI fields may indicate layer information and TPMI index information for repeated PUSCH transmission considering multi-TRP or single TRP. If each SRI field has one or more code points indicating a reserved value, dynamic switching may be supported depending on whether the corresponding SRI field indicates a code point indicating a reserved value. If the first SRI field indicates a code point indicating a reserved value and the second SRI field indicates SRS resources of the second SRS resource set, the terminal may perform a repeated PUSCH transmission considering a single TRP of TRP 2. In this case, the terminal may identify layer information and TPMI index information from the first TPMI field to perform repeated PUSCH transmission considering a single TRP of TRP 2. If the second SRI field indicates a code point indicating a reserved value and the first SRI field indicates SRS resources of the first SRS resource set, the terminal may perform a repeated PUSCH transmission considering a single TRP of TRP 1.
In this case, the terminal may identify layer information and TPMI index information from the first TPMI field to perform repeated PUSCH transmission considering a single TRP of TRP 1. If the two SRI fields have code points indicating SRS resources of each SRS resource set, instead of code points indicating reserved values, the terminal may perform repeated PUSCH transmission considering multiple TRPs. In this case, in order to perform repeated PUSCH transmission for TRP1, the terminal may identify layer information and TPMI index information from the first TPMI field and identify TPMI index information from the second TPMI field to perform repeated PUSCH transmission for TRP 2. In this case, the same layer may be configured during PUSCH transmission of TRP1 and TRP 2. If there is no code point indicating a reserved value in the two SRI fields, the number of bits per SRI field may be increased by 1, and the last code point among the code points indicating a reserved value with reference to the increased number of bits may be used to support dynamic switching.
< examples (1-6): dynamic switching method for PUSCH transmission considering single TRP or PUSCH transmission considering multiple TRP based on non codebook determination >
In the (1-6) th embodiment, as an embodiment of the present disclosure, a dynamic switching method that considers PUSCH transmission of a single TRP or PUSCH transmission of multiple TRP based on non-codebook determination is described.
According to (1-1) to (1-4) embodiments, a base station may receive a UE capability report from a terminal that may perform non-codebook based repeated PUSCH transmission considering multiple TRPs based on a single DCI, and may configure the terminal with higher layer signaling for performing the repeated PUSCH transmission through the multiple TRPs. In this case, as described in (1-4) th embodiment, during repeated PUSCH transmission considering multiple TRPs based on a single DCI, the base station may transmit a single DCI including a plurality of SRI fields to the terminal to indicate SRS resources existing in different SRS resource sets. For example, the plurality of SRI fields may be selected by:
method 1 each SRI field can be interpreted in the same way as NR version 15/16. For example, the first SRI field may indicate PUSCH transmission SRS resources in the first SRS resource set, and the second SRI field may indicate PUSCH transmission SRS resources in the second SRS resource set.
Method 2 in the same method as NR version 15-/16, the first SRI field may indicate PUSCH transmission SRS resources in the first SRS resource set. The second SRI field may indicate one or more PUSCH transmission SRS resources in a second SRS resource set for the same layer as indicated by the first SRI field.
In the case that a plurality of SRIs are selected through the method 2, the bit length of the second SRI field may be shorter than the bit length of the first SRI field. This is because the second SRI is determined from the SRI candidates for the same layer as the layer determined as the first SRI field from among the SRI candidates of all support layers.
The terminal may receive a single DCI including a plurality of SRI fields and support a dynamic switching method for determining a repeated PUSCH transmission considering a plurality of TRPs or determining a repeated PUSCH transmission considering a single TRP based on the received single DCI. The terminal may support dynamic handover by using a code point indicating a reserved value of a plurality of SRI fields included in the received DCI.
To describe a dynamic handover method that can be supported by a code point indicating a reserved value in a plurality of SRI fields, assume, with one detailed example, a case where there are at most four PUSCH antenna ports and four SRS resources in each SRS resource set. In addition, it is assumed that the first SRI field is configured to 4 bits and is indicated in the same way as NR version 15/16. In this case, in the first TPMI field, indexes 0 to 14 may be configured to indicate PUSCH transmission SRS resources and layers according to the selected SRS resources, and index 15 may be configured to indicate code points of reserved values. If the second SRI field selects as many SRS resources as the number of layers indicated by the first SRI, as in method 2, the second SRI field may indicate an SRS resource selection candidate in a case where the layer for PUSCH transmission is limited to one value (e.g., one of 1 to 4) according to the first SRI field.
In this case, the number of bits of the second SRI field may be configured with reference to a layer having the largest candidate number among the number of SRS resource selection candidates per layer. For example, the SRI field value indicating the SRS resource selection candidate of layer 1 may correspond to 0 to 3, and there are four candidates in total. The SRI field value indicating the SRS resource selection candidate of layer 2 may correspond to 4 to 9, and there are six candidates in total. The SRI field value indicating the SRS resource selection candidate of layer 3 may correspond to 10 to 13, and there are four candidates in total. The SRI field value indicating the SRS resource selection candidate of layer 4 may correspond to 14 and there is one candidate. In this case, layer 2 has the largest candidate value (six), and thus, the number of bits of the second SRI field may be configured to be 3. According to the detailed description of the second SRI field configuration, for example, when the first SRI field indicates an SRI value in case that a layer for PUSCH transmission is 1, the terminal may interpret the second SRI field as a code point indicating one value of SRI candidates 0 to 3 for layer 1 or a code point having other reserved values.
In another example, when the first SRI field indicates an SRI value in case of layer 2 for PUSCH transmission, the terminal may interpret the second SRI field as a code point indicating one value of SRI candidates 0 to 5 for layer 2 or a code point having other reserved values. In addition, for example, when the first SRI field indicates an SRI value in the case where a layer for PUSCH transmission is 3 or 4, the terminal may also interpret the second SRI field in a similar manner to the above description. In this case, when there are two or more code points indicating a reserved value in the second SRI field, the two code points indicating a reserved value may be used to indicate dynamic switching in addition to the code points indicating the SRI index according to the layer.
That is, among the code points of the second SRI field configured with 3 bits, the penultimate code point (i.e., the 7 th code point in the example) corresponding to the code point indicating the reserved value may be used to indicate the repeated PUSCH transmission to the first TRP considering the single TRP, and the last code point (i.e., the 28 th code point in the example) may be used to indicate the repeated PUSCH transmission to the second TRP considering the single TRP. In this case, the SRI for considering the repeated PUSCH transmission of a single TRP may be indicated to the terminal through the first SRI field. The assumptions in the above description are for convenience of description, and the present disclosure is not limited thereto.
For convenience of description, according to an example in which the above detailed examples of two TRPs are summarized, a terminal may receive a single DCI including two SRI fields and perform dynamic handover according to a code point indicated by a second SRI field. The terminal may perform repeated PUSCH transmission considering multiple TRPs if the code point of the second SRI field indicates the SRI value of the layer indicated by the first SRI field. If the second SRI field indicates that the penultimate code point corresponds to a code point indicating a reserved value, the terminal may perform a repeated PUSCH transmission with a single TRP of TRP 1 taken into account, and may identify an SRI from the first SRI field for a non-codebook based PUSCH transmission. If the second SRI field indicates that the last code point corresponds to a code point indicating a reserved value, the terminal may perform repeated PUSCH transmission considering a single TRP of TRP 2, and may identify an SRI for non-codebook based PUSCH transmission from the first SRI field.
In the above example, the last two code points of the second SRI field indicating the reserved value are used to indicate dynamic switching, but the embodiment is not limited thereto. In other words, dynamic switching may be indicated by using a code point indicating two different reserved values of the second SRI field, and repeated PUSCH transmissions of a single TRP considered for TRP 1 or repeated PUSCH transmissions of a single TRP considered for TRP 2 may be mapped to the code point indicating each reserved value and indicated.
In addition, in the above example, it is described that the second SRI field is determined according to method 2, but even in the case where the second SRI field is determined in the same manner as NR version 15/16, as described in method 1, dynamic handover can be supported by using the code point of the SRI field indicating the reserved value in the same manner as in the above example.
For example, if the number of code points indicating the reserved value of the second SRI field is less than 2, the number of bits of the second SRI field may be increased by 1, and the last-to-last code point and the last code point referring to the increased number of bits may be used to support dynamic switching.
When determining two SRI fields according to method 1, a method for supporting dynamic handover according to whether each SRI field is indicated as a code point indicating a reserved value may be additionally considered. That is, when the first SRI field is indicated as a code point indicating a reserved value, the terminal may perform repeated PUSCH transmission of a single TRP in consideration of TRP 2, and when the second SRI field is indicated as a code point indicating a reserved value, the terminal may perform repeated PUSCH transmission of a single TRP in consideration of TRP 1. If both SRI fields indicate a code point for indicating SRI, instead of a code point for indicating a reserved value, the terminal may perform repeated PUSCH transmission considering multiple TRPs. If no code point indicating a reserved value is available, the number of bits of the SRI field may be increased by 1, and the last code point referencing the increased number of bits may be used to support dynamic switching.
Fig. 20 illustrates a base station and terminal operation for repeating PUSCH transmission in consideration of multiple TRP based transmission of a single DCI in which multiple SRI or TPMI fields exist, according to an embodiment of the present disclosure. The terminal performs UE capability reporting for information related to whether repeated PUSCH transmission considering multiple TRPs based on a single DCI is supported, whether multiple SRI or TPMI fields are supported, whether dynamic switching between single/multiple TRPs by using corresponding fields is supported, and transient offset when transmission beam switching, which will be described in the second embodiment below, is performed (operation 2051), and the base station having received the corresponding UE capability reporting (operation 2001) transmits a repeated PUSCH transmission configuration considering multiple TRPs based on a single DCI to the terminal (operation 2002).
In this case, the transmitted configuration information may include information about a repeated transmission method, the number of repeated transmissions, a transmission beam mapping unit or scheme, whether a plurality of SRI or TPMI fields are supported, a plurality of codebooks or non-codebook SRS resource sets, a transient offset when performing transmission beam switching, which will be described in the second embodiment below, and the like. The terminal having received the corresponding configuration (operation 2052) may identify the number of repeated PUSCH transmissions based on a time resource allocation field in DCI or a configuration through higher layer signaling.
In this case, when the number of repeated transmissions is not greater than 1 (operation 2003 or 2053), that is, when repeated transmissions are not performed, the terminal may perform a first PUSCH transmission operation (operation 2004 or 2054). The first PUSCH transmission operation may correspond to an operation of performing a single transmission of PUSCH to a single TRP by using one SRI field and one TPMI field in the case of codebook-based PUSCH transmission, and using one SRI field (i.e., using one transmission beam) in the case of non-codebook-based PUSCH transmission. When the number of repeated transmissions is greater than 1 (operation 2003 or 2053) and the terminal does not receive a configuration capable of supporting a plurality of SRI or TPMI fields from the base station (operation 2005 or 2055), the terminal may perform a second PUSCH transmission operation (operation 2006 or 2056). The second PUSCH transmission operation corresponds to an operation of performing repeated PUSCH transmission to a single TRP by using one SRI field and one TPMI field in the case of codebook-based PUSCH transmission, and using one SRI field (i.e., using one transmission beam) in the case of non-codebook-based PUSCH transmission.
When the terminal has received a configuration capable of supporting a plurality of SRIs or TPMI fields from the base station (operation 2005 or 2055), and the plurality of SRIs or TPMI fields in the DCI received by the terminal indicate a code point based on repeated transmission of a single TRP as described in the above (1-5) and (1-6) embodiments, instead of a code point based on repeated transmission of multiple TRPs (operation 2007 or 2057), the terminal may perform a third PUSCH transmission operation (2008 or 2058). The third PUSCH transmission operation corresponds to such operations: wherein the terminal performs PUSCH repetition transmission to a specific single TRP by indicating code points of single TRP transmission between code points in each field by using two SRI fields and two TRMI fields in case of codebook-based PUSCH transmission and two SRI fields (i.e., using one transmission beam) in case of non-codebook-based PUSCH transmission.
Thus, repeated transmissions to trp#1 or trp#2 may be indicated depending on the code points indicated by the plurality of SRI or TPMI fields. When the terminal has received a configuration capable of supporting a plurality of SRI or TPMI fields from the base station (operation 2005 or 2055), and the plurality of SRI or TPMI fields in the DCI received by the terminal indicate a code point representing a multi-TRP based repeated transmission (operation 2007 or 2057), the terminal may perform a fourth PUSCH transmission operation (operation 2009 or 2059). The fourth PUSCH transmission operation corresponds to the operation: wherein the terminal performs repeated PUSCH transmission to a plurality of TRPs by indicating code points of multi-TRP transmission between code points in each field by using two SRI fields and two TRMI fields in the case of codebook-based PUSCH transmission and using two SRI fields (i.e., using a number of transmission beams) in the case of non-codebook-based PUSCH transmission.
< second embodiment: method for defining a time interval and transmitting an uplink signal considering UE capability reporting >
According to embodiments of the present disclosure, a terminal may define a time interval (e.g., referred to as a transient period, a transient offset, a transient gap, etc.) between a plurality of uplink transmissions required to perform UE capability reporting or to receive configuration from a base station, and by considering this, the terminal may apply a corresponding time interval between respective uplink transmissions when performing uplink signal transmission. In order to transmit an uplink signal, the terminal may change at least one of an uplink beam, transmission power, and frequency before transmitting the uplink signal.
In addition, in order to transmit an uplink signal, the terminal may change the panel before transmitting the uplink signal. Thus, in order to transmit an uplink signal, the terminal may change at least one of an uplink beam, transmission power, frequency, and panel before transmitting the uplink signal. For example, when the plurality of beams are classified into a plurality of beam groups, the panel may be configured to correspond to each beam group, such as panel #1 in beam group #1, panel #2 in beam group #2,. In another example, when there are a plurality of antenna modules for forming a beam in a terminal and the plurality of antenna modules are installed at different positions, a panel may be configured to correspond to each antenna module. In addition, the plurality of panels may be configured in various schemes for classifying a plurality of beams having different beam widths, different beam directions, and the like. This change for uplink signal transmission may be performed in the following cases:
in one example case 1, an uplink signal (e.g., PUCCH, PUSCH, SRS, etc.) is repeatedly transmitted to a plurality of TRPs and a terminal changes an uplink beam, transmission power, or frequency to change and transmit the TRPs between repeated transmissions, or a terminal changes a panel to change and transmit the TRPs between repeated transmissions.
In one exemplary case 2, the base station indicates uplink signal transmission via L1 signaling or MAC CE signaling including DCI, and the terminal changes an uplink beam, transmission power, or frequency to transmit the uplink signal, or the terminal changes a panel to transmit the uplink signal.
In one exemplary case 3, SRS transmission is indicated or configured, a plurality of SRS resources included in the SRS resource set are used, and an uplink beam, transmission power, or frequency is changed to use the plurality of SRS resources, or a terminal changes a panel to perform SRS transmission.
In case 1, the case of changing transmission information for TRP change between repeated transmissions may be determined according to a mapping pattern between repeated transmissions and TRPs. Here, the repeated transmission means, for example, a case where the same uplink signal is transmitted. In the 3GPP release 16 standard, when the base station performs repeated PUSCH transmission, two mapping patterns (e.g., "sequential" and "cyclic") are supported. The mapping pattern for repeatedly transmitting PDSCH to the plurality of TRPs may be applied to a case where the terminal repeatedly transmits uplink signals to the plurality of TRPs. The "sequential" mapping corresponds to a scheme of changing and transmitting TRP into two repeated transmission units such as { TRP1, TRP2} for example, and the "cyclic" mapping corresponds to a scheme of changing TRP into { TRP1, TRP2, TRP1, TRP2} and transmitting it, for example, at each repeated transmission.
When at least one of an uplink beam, a transmission power, and a transmission frequency (or a frequency hopping) for transmitting an uplink signal to a plurality of TRPs, the terminal may transmit the uplink signal by applying uplink transmission change information determined according to the mapping scheme. Alternatively, when a panel for transmitting an uplink signal to a plurality of TRPs is determined, the terminal may transmit the uplink signal by applying uplink transmission change information determined according to the mapping scheme. In this case, the uplink transmission change information may represent at least one of an uplink beam, a transmission power, and a transmission frequency for transmitting the uplink signal.
Alternatively, the uplink transmission change information may represent a panel for transmitting an uplink signal. The case of repeatedly transmitting the PUSCH to the plurality of TRPs may include both the case of repeatedly transmitting the PUSCH according to the repeated PUSCH transmission type a and the case of repeatedly transmitting the PUSCH according to the repeated PUSCH transmission type B. For a repeated transmission unit, the repeated PUSCH transmission type B may consider both the case of nominal repetition and the case of actual repetition.
In case 2, the base station may configure higher layer parameters of uplink signal transmission for the terminal and instruct the terminal to transmit uplink signals (e.g., PUCCH, PUSCH, SRS, etc.) through L1 signaling (e.g., DCI). In this case, the time interval between signaling indicating uplink signal transmission by the base station to the terminal and uplink signal transmitted by the terminal may be defined as "time offset", and this may be replaced with "scheduling interval", "scheduling offset", "time interval", "transient period", "transient offset", "transient time", or the like.
When the base station indicates uplink signal transmission to the terminal via L1 signaling including DCI, the time offset may be calculated as the interval between "after the last symbol of the PDCCH including DCI is transmitted therein and before the first symbol of the uplink signal (e.g., PUCCH including HARQ-ACK for aperiodic/semi-persistent SRS, PUSCH, or PDSCH) is transmitted therein". When the DCI decoding time of the terminal is additionally considered, the time offset may be calculated as the interval between "after the last symbol of the PDCCH including the DCI is transmitted therein and before the first symbol of the uplink signal is transmitted therein". When the base station indicates uplink signal transmission via MAC CE signaling, the time offset may be calculated according to the following method:
in one example of method 1, after the last symbol of PDSCH in which MAC CE signaling is transmitted ends and before the first symbol of uplink signals (e.g., aperiodic/semi-persistent SRS) is transmitted begins.
In one example of method 2, after the last symbol of PUCCH/PUSCH in which HARQ-ACK for PDSCH including MAC CE signaling is transmitted ends and before the first symbol in which uplink is transmitted starts.
In one example of method 3, after the MAC CE applies a delay time (e.g., a first starting slot after 3 ms), it passes from a point in time at which a last symbol of PUCCH/PUSCH including HARQ-ACK for PDSCH including MAC CE signaling is transmitted ends to before a first symbol at which an uplink signal is transmitted begins.
Such a time offset may be converted in absolute time (e.g., ms) units or in symbol units. When the terminal receives an uplink signal transmission indication from the base station, the terminal may change at least one of an uplink beam, a transmission power, and a frequency for uplink transmission during the time offset. Alternatively, the terminal may change the panel for uplink transmission during the time offset.
In case 3, when the terminal transmits the SRS scheduled by the base station, the terminal may change an uplink beam, transmission power, and frequency according to a higher layer configuration of SRS resources included in the SRS resource set to be transmitted, and transmit the SRS. Alternatively, the terminal may change the panel and transmit the SRS according to a higher layer configuration of the SRS resource.
The terminal may require a transient time to change at least one of uplink beam, transmission power, and frequency according to UE capability. Alternatively, the terminal may need a transient time to change the panel for uplink transmission according to the UE capability. Such a transient time may be considered, for example, when the repeated transmission is performed in units of long sub-slots or in units of short sub-slots. The transient time according to the UE capability may be applied to some or all of the uplink beam, transmission power, or frequency determined in the transmission of the uplink signal according to whether the transient time satisfies a time offset or interval between repeated transmissions of the uplink signal.
As described above, a predetermined time may be required to change the uplink beam, transmission power, or frequency, and in order to satisfy the predetermined time, the base station may instruct the uplink signal transmission to the terminal such that an offset interval is added between repeated transmissions, or a time offset is greater than the predetermined time for the change. Alternatively, when an additional panel change for uplink transmission is performed, a predetermined time may be required, and in order to meet the predetermined time, the base station may indicate uplink signal transmission to the terminal such that an offset interval or a time offset is added between repeated transmissions that is greater than the predetermined time for the change.
In the following, in the present disclosure, an offset in the time domain for a terminal uplink transmission may be understood to include the meaning of a time offset or time interval between repeated transmissions of an uplink signal.
In the present disclosure, detailed embodiments related to a method of a base station determining an offset in a time domain to ensure a time required to change an uplink beam, transmission power or frequency according to UE capability, and a method of a terminal transmitting an uplink signal indicated by a base station will be implemented by the following (2-1) th and (2-2) th embodiments. The division between the (2-1) th and (2-2) th embodiments is for convenience of description, and each embodiment of the present disclosure may be combined with at least one embodiment to be implemented.
< example (2-1): method for base station to determine offset and configure offset for terminal according to UE capability
As an example of a method for determining an offset in a time domain for uplink signal transmission, a terminal may report UE capability information to a base station, the UE capability information including at least one of UE capability for performing uplink beam change, UE capability for performing transmission power change, UE capability for performing frequency change in consideration of frequency hopping, and the like. Alternatively, the three UE capabilities described above may be reported to the base station separately. In addition, the terminal may select one of three UE capabilities and report the capabilities. In addition, the terminal may report a representative value of UE capability for changing a transmission configuration of the uplink signal.
Additionally, when a terminal can transmit an uplink signal by using a plurality of panels, UE capabilities for panel change may be considered together in a stage of determining UE capabilities to report. That is, the terminal may report UE capability information to the base station, the UE capability information including at least one of UE capability for performing uplink beam change, UE capability for performing transmission power change, UE capability for performing frequency change in consideration of frequency hopping or the like, and UE capability for performing panel change. Alternatively, the four UE capabilities described above may be reported to the base station separately. In addition, the terminal may select one of four UE capabilities and report the capabilities. In addition, the terminal may report a representative value of UE capability for changing a transmission configuration of the uplink signal.
Hereinafter, the terms "UE capability", "UE capability information" and "terminal capability" used interchangeably in this disclosure may be understood to have the same meaning.
As described above, the reason why the terminal reports the UE capability to the base station is to provide information required for the base station to determine the offset in the case where the terminal changes some or all of the uplink beam, transmission power, or frequency when transmitting the uplink signal. Additionally, when the terminal supports a plurality of panels and the panels are changed, the terminal may provide the base station with information required for the base station to determine the offset. The terminal may perform reporting of UE capability for each uplink beam change or power adjustment or frequency change by using one of the following methods. In addition, UE capabilities for panel changes may also be reported by using one of the following methods.
In one embodiment, the terminal may report the UE capability of the uplink transmission configuration change of NR version 15/16. For example, to report UE capabilities for beam change, the terminal may configure "beamSwitchTiming" to one of {14, 28, 48} described in NR version 15/16, for example, to report UE capabilities to the base station. To report the panel changed UE capability, the terminal may configure "beamSwitchTiming" to one of {224,336} to report the UE capability to the base station. Here, the number indicating "beamSwitchTiming" may correspond to a symbol unit, and for example, when "beamSwitchTiming" is configured as "224" in the UE capability report for a panel change, this means that beam switching processing time in the UE capability for the panel change means takes as much as 224 symbols. In addition, "beamSwitchTiming" may be configured for each subcarrier interval.
In one embodiment, the time required for the change may be reported in symbols or absolute time periods (e.g., ms).
In one embodiment, the base station and the terminal may predefine a processing time allowed to indicate processing capabilities. The processing time of the N processing capabilities may be predefined and may vary according to the subcarrier spacing. The following [ table 41] and [ table 42] indicate examples of predefined processing time intervals between the base station and the terminal for processing the uplink beam, the processing power n of the change of the transmission power or the frequency and n+1. Here, the values of the required time regions may be configured such that, for example, { a1< a2< a3< a4} and { b1< a1, b2< a2, b3< a3} relationships are formed. The unit of time required may be configured as a symbol or a millisecond.
TABLE 41
TABLE 42
When reporting a processing time for changing at least one of an uplink beam, a transmission power, and a frequency as UE capability, the terminal may determine a value to report in consideration of each uplink signal. For example, when the terminal reports a processing time for uplink beam change as UE capability, the terminal may classify the UE capability into UE capability for beam change of PUCCH, UE capability for beam change of PUSCH, and UE capability for beam change of SRS in order to report the UE capability. UE capabilities for transmission power change and UE capabilities for frequency change may be classified according to PUCCH, PUSCH, or SRS and reported in the same manner as described above.
When the terminal reports the changed UE capability for each uplink beam of the PUCCH, at least one of transmission power and frequency, the terminal may determine the UE capability by considering the number of PUCCH resources, the number of configured spatial relationship information, the number of activated spatial relationship information, the frequency hopping configuration, etc. When the terminal reports UE capability of a change in at least one of each uplink beam, transmission power, and frequency of PUSCH, the terminal may determine the UE capability by considering a precoding method of PUSCH (e.g., "codebook" or "non-codebook"), the number of SRS resource sets associated with PUSCH transmission, the number of SRS resources configured in the associated SRS resource set, a relationship between PUSCH and SRS antenna ports, a hopping configuration, and the like.
When the terminal reports UE capability for a change in at least one of each uplink beam, transmission power, and frequency of the SRS, the terminal may determine the UE capability by considering an SRS transmission indication method (e.g., based on DCI or based on MAC-CE), SRS timeline information (e.g., periodic SRS, semi-persistent SRS, or aperiodic SRS), use of the SRS (e.g., "beam management", "codebook", "non-codebook", or "anticonswitching"), the number of SRS resource sets, the number of SRS resources, and the like. Additionally, a terminal supporting multiple panels reports the processing time of the panel change as UE capability, and the terminal may determine a value to report in consideration of an uplink signal. Alternatively, the terminal may determine and report the changed UE capability for at least one of the uplink beam, the transmission power, and the frequency without distinguishing the UE capability of each uplink signal. In addition, the terminal may determine and report the panel changed UE capabilities without distinguishing the UE capabilities of each uplink signal.
Additionally, the terminal may report UE capabilities indicating whether uplink beams, transmission power, and frequency may be changed simultaneously or sequentially. Here, a terminal supporting a plurality of panels may report UE capabilities for indicating whether the panels may also be changed at the same time. That is, the terminal may report whether uplink beams, transmission power, frequency, panel, etc. may be changed at the same time as UE capability. As an example of UE capability, the terminal may select one of "simultaneous" and "sequential" and report it to the base station. When the terminal reports UE capability as "simultaneous", this means that the terminal can change uplink beam, transmission power and frequency simultaneously. This also means that a terminal supporting multiple panels can also change panels at the same time. When the terminal reports UE capabilities as "sequential", this means that the terminal can sequentially change uplink beams, transmission power, and frequency. This also means that a terminal supporting a plurality of panels may also change the panels sequentially.
In addition to the UE capability report for supporting the change of uplink beam, transmission power, frequency and panel, the terminal may report to the base station a UE capability "beamcorespontensingthoutul-beamswiping" for informing whether the beam correspondence requirement is satisfied. Beam correspondence represents the ability of a terminal to select a beam for uplink transmission based on downlink measurements without relying on uplink beam scanning. If the terminal reports "beam response withoutul-beam scanning" corresponding to the UE capability to which the beam corresponds, the terminal may select an uplink beam for uplink transmission without uplink beam scanning and transmit an uplink signal by using the selected uplink beam.
The base station may determine an offset for ensuring a time required to apply the uplink transmission change information based on the UE capability reported by the terminal. The base station may consider one or a combination of the following options to determine the offset.
In one example of option 1, the offset may be determined with reference to a maximum value of at least one of an uplink beam changed UE capability, a transmission power changed UE capability, and a frequency changed UE capability reported from the terminal.
In one example of option 2, the offset may be determined with reference to the maximum value of the changed UE capabilities required for actual uplink transmission from among the UE capabilities reported from the terminal. For example, when the base station indicates an uplink signal to the terminal so as to perform only uplink beam change and transmission power change, the offset may be determined with reference to the maximum value of the UE capability of the uplink beam change and the UE capability of the transmission power change. In addition to the above example, an offset for an uplink transmission change combination may also be determined in the same manner as the above example.
In one example of option 3, the offset may be determined with reference to the uplink beam changed UE capability, the transmission power changed UE capability, and the number of frequency changed UE capabilities reported from the terminal.
In one example of option 4, the offset may be determined with reference to a sum of UE capabilities to perform a change required for actual uplink transmission from among UE capabilities reported from the terminal. For example, when the base station indicates an uplink signal to the terminal so as to perform only uplink beam change and transmission power change, the offset may be determined with reference to the sum of the UE capability of the uplink beam change and the UE capability of the transmission power change. In addition to the above example, an offset for an uplink transmission change combination may also be determined in the same manner as the above example.
In one example of option 5, when the offset is determined through one of options 1 to 4 described above, the offset may be determined in consideration of the configuration of each uplink transmission signal. For example, when the base station determines an offset for repeatedly transmitting PUCCH to a plurality of TRPs, the base station may determine the offset with reference to UE capability reported by the terminal in consideration of PUCCH configuration according to option 1 above. Alternatively, when the terminal does not report the UE capability without distinguishing the UE capability of each uplink signal, the base station may predict an additional time required due to PUCCH configuration in addition to the UE capability in order to determine the offset. This option may be applied when the base station determines an offset for transmitting another uplink signal (e.g., PUSCH or SRS).
In one example of option 6, when the offset is determined by one of options 1 to 4 described above, the offset may be determined without distinguishing the configuration of each uplink transmission signal.
In one example of option 7, the base station may determine the offset by using a predetermined value. In this case, higher layer parameter configuration of the uplink signal, uplink resource configuration, and the like may be considered.
In one example of option 8, when the terminal supports multiple panels and determines an offset through options 1 to 6 above, the terminal may determine the offset by additionally considering the panel-changed UE capability.
Each option corresponds to an example in the case where all UE capabilities of the above three pieces of uplink transmission change information are reported, and when the terminal reports only some UE capabilities, the base station can determine an offset by applying only the reported UE capabilities to each option.
For example, when the terminal has reported that the uplink beam, transmission power, and frequency can be changed simultaneously, the base station can select option 1 or option 2 to determine the offset. Alternatively, when the terminal has reported that the uplink beam, transmission power and frequency may be sequentially changed, the base station may select option 3 or option 4 to determine the offset. When the terminal supports a plurality of panels and has reported that uplink beams, transmission power, frequency, and panels (or two or more of uplink beams, transmission power, frequency, and panels) may be changed simultaneously, the base station may determine the offset by additionally considering UE capability for panel change according to option 8 in addition to option 1, or may determine the offset by additionally considering UE capability for panel change according to option 8 in addition to option 2. This corresponds to an example of the above embodiment, and the base station may determine the offset according to the UE capability reported by the terminal, taking into account one or a combination of the above options 1 to 8.
The base station may adjust the offset value determined according to the above options according to whether or not the beam correspondence of the terminal through the UE capability report is supported. For example, when the terminal supports beam correspondence, the base station may determine the offset value determined through the above option as a final offset value, or may adjust the offset value to a smaller value. When the terminal does not support beam correspondence, the base station may add an additional required time to the offset value determined by the option.
The base station may adjust the offset value determined according to the above option according to whether or not there is an uplink beam report for uplink transmission to the plurality of TRPs by the terminal. When an uplink beam has been reported to the base station, this may indicate that the corresponding uplink beam is a "known" beam of the terminal. When an uplink beam is not reported, this may indicate that the corresponding uplink beam is an "unknown" beam for the terminal. If an uplink beam to be used for the terminal to perform uplink transmission has been reported to the base station, the base station may determine the offset value determined through the above option as a final offset value, or may adjust the offset value to a smaller value. When an uplink beam for a terminal to perform uplink transmission is not reported to the base station, the base station may add an additional required time to the offset value determined by the option.
The base station may inform the terminal of the determined offset. In this case, the base station may explicitly or implicitly inform the terminal about the offset.
In one embodiment, the base station explicitly configures the determined offset for the terminal: the base station may configure the offset as a new higher layer parameter and notify the terminal of it as displayed. For example, a new higher layer parameter "timeduration forulswitch" may be added to PUSCH transmission configuration information such as PUCCH-FormatConfig or PUCCH-conconfig. For PUSCH or SRS, the new parameters of the offset may also be added to the higher layer parameters for PUSCH transmission and the higher layer parameters for SRS transmission in a similar manner. The above example corresponds to a method for configuring a new higher layer parameter for indicating an offset determined by a base station to a terminal, and may be defined as a higher layer parameter having the same function under another name.
In one embodiment, the base station implicitly configures the case of the determined offset: instead of configuring the offset directly with higher layer parameters as described above, the base station may implicitly indicate the offset by the configuration used to transmit another uplink signal. For example, the offset may be implicitly indicated by "startingsymbol" configured with PUCCH-format [ a ] (here, a refers to, for example, 0, 1, 2, 3, or 4) in higher layer parameters PUCCH-Resource. More specifically, as one of enhanced examples for indicating repetition transmission of PUCCH in a slot, startingsymbol in PUCCH-format [ a ] of PUCCH-Resource may be configured to be as many as the number of repetition of PUCCH in a slot. As a detailed example, when the number of repetitions in a slot is, for example, 2, startingsymbol index may indicate a transmission start symbol of a first repetition PUCCH transmission occasion in the slot, and newly added "startingsymbol index2" may indicate a transmission start symbol of a second repetition PUCCH transmission occasion in the slot.
In this case, the symbol position indicated by startingsymbol index may be at an earlier symbol position than the symbol position indicated by startingsymbol index, and the interval between the two symbols may be determined by the base station such that the interval is greater than nrofSymbols, the number of symbols for one PUCCH transmission, and the offset determined by the base station. The above example is just one example, and the base station may implicitly inform the terminal of the offset through PUCCH resource configuration of PUCCH transmission, or the like. Alternatively, when the base station performs scheduling of PUCCH including HARQ-ACK information of PDSCH for the terminal, the base station may indicate PDSCH-to-harq_feedback timing indicator to the terminal such that the time offset is greater than the determined offset. Also, for uplink signals (e.g., PUSCH or SRS) other than PUCCH, the base station may implicitly inform the terminal of the offset through transmission timing indicated by DCI or higher layer parameter configuration of the uplink signal.
Example (2-2): method for transmitting uplink signal indicated by base station according to UE capability >
When the terminal has received the repeated transmission of the uplink signal from the base station, the terminal may determine an operation for repeating the uplink transmission according to whether an offset determined by the base station has been explicitly configured or implicitly indicated. When the base station has explicitly configured an offset for the terminal, the terminal may configure an interval between repeated transmissions according to the offset in the time domain to transmit an uplink signal. When the offset has been implicitly indicated to the terminal, the terminal transmits the uplink signal according to a higher layer parameter configuration of the uplink signal configured by the base station. When the base station explicitly configures an offset for the terminal or implicitly indicates the offset and applies the offset to repeated transmission of the uplink signal, at least one of uplink beam, transmission power, and frequency is changed and transmitted during the offset according to the capability of the terminal.
If the offset determined by the base station is configured to have a value equal to or greater than the UE capability for changing the uplink beam, transmission power, or frequency, the terminal may change the uplink beam or transmission beam to change TRP and transmit between repeated transmissions, or may change the frequency to perform frequency hopping, or the like. If the offset determined by the base station is configured to have a value smaller than the UE capability for changing the uplink beam, transmission beam or frequency, the terminal may perform a predefined default uplink transmission method between the base station and the terminal in consideration of one or a combination of the following operations in order to perform repeated transmission of the uplink signal.
In one example, for transmitting uplink signals at the same uplink beam, transmission power, and frequency as in the previous repeated transmission, the terminal cannot meet the time required to change the beam, transmission power, or frequency between repeated transmissions because the offset determined by the base station has a value less than the UE capability. Accordingly, the terminal can perform the next repetition transmission by using the same beam, transmission power, and frequency applied to the previous repetition transmission. Here, the previous retransmission indicates a retransmission occasion immediately before the retransmission occasion to be transmitted. In addition, at least one of the same uplink beam, transmission power and frequency as the previous (repeated) transmission may be used, and the remaining part of the at least one of the uplink beam, transmission power and frequency may be changed. For example, the same uplink beam and frequency as the previous (repeated) transmission may also be used, and the transmission power is changed in the next repeated transmission.
In one example, for transmitting uplink signals using a default configuration of uplink beams, transmission power, and frequency, the terminal cannot meet the time required to change the beams, transmission power, or frequency between repeated transmissions because the offset determined by the base station has a value less than the UE capability. Thus, the terminal may perform the next repeated transmission with a predefined default uplink beam, default transmission power, and default frequency. Here, the base station and the terminal may define default transmission information for each uplink signal (PUCCH, PUSCH, or SRS). Alternatively, the base station and the terminal may define default transmission information of the uplink signal with each other. In addition, at least one of the uplink beam, the transmission power, and the frequency may be used as a default configuration, and the remaining portion of the at least one of the uplink beam, the transmission power, and the frequency is changed. For example, the uplink beam and frequency may also be used as default configurations and the transmission power changed in the next repeated transmission.
In one example, to change an uplink beam, transmission power, or frequency and transmit an uplink signal under conditions, when the mapping between uplink repeated transmission and TRP is configured as "sequential", the uplink beam, transmission power, or frequency may be changed and transmitted in a repeated transmission occasion that satisfies the UE capability. At a retransmission occasion where the UE capability cannot be satisfied, the terminal may transmit an uplink signal with the same configuration as the previous retransmission occasion. For example, when the mapping is configured as { TRP1, TRP2}, the first two repetition transmission opportunities are transmitted by using the uplink beam, transmission power, and frequency of TRP 1. The third retransmission occasion needs to change the uplink beam, transmission power, and frequency of TRP2 in order to be transmitted, but the offset has a value smaller than the UE capability, and thus, the uplink signal is transmitted by using the TRP1 configuration without changing uplink transmission information. The terminal may transmit a fourth recurring transmission opportunity by performing a change to the uplink beam, transmission power, and frequency of TRP 2.
In one example, to send duplicate uplink transmissions by applying a variable configuration in the uplink beam, transmission power, and frequency, when the terminal compares the size of the offset of the base station configuration with the size of the UE capability, the terminal may apply some variable configuration to the next duplicate transmission occasion, with the value of the offset being less than that of the UE capability. For example, when the offset has a value greater than the UE capability for uplink beam change and has a value less than the UE capability for transmission power change or frequency change, the terminal may change only the uplink beam and apply the same transmission power and frequency as in the previous repeated transmission to transmit the next repeated transmission occasion. As the terminal sequentially changes the uplink beam, the transmission beam, and the frequency, the terminal compares the offset determined by the base station with the sum of the combinations of UE energies for the changes in the uplink beam, the transmission power, and the frequency. In this case, when the value of the combination of the plurality of UE capabilities is smaller than the offset, the determination is made according to the priority of the change of the predetermined uplink beam, transmission power, or frequency between the base station and the terminal. For example, when the offset determined by the base station has a value smaller than the sum of all UE capabilities, smaller than the sum of UE capabilities for uplink beam and transmission power change, smaller than the sum of UE capabilities for uplink beam and frequency change, and smaller than the sum of UE capabilities for transmission power and frequency change, and the priority is predetermined between the base station and the terminal as { uplink beam > transmission power > frequency } for example, the terminal can transmit an uplink signal by changing the uplink beam and transmission power.
In one example, for transmitting an uplink signal by discarding some symbols or repeating transmission occasions, in order to apply uplink transmission change information and perform repeated transmission of the uplink signal, a terminal may discard some symbols in front of the repeating transmission occasion in which at least one of a beam, a transmission power, and a frequency is changed, and may perform repeated transmission by using the remaining resources. For example, when the mapping between the repetition PUCCH transmission and the TRP is configured as { TRP1, TRP2}, in the third repetition transmission, the PUCCH is not transmitted during some symbols of the front part until the time when the uplink beam, transmission power and frequency of the TRP2 need to be changed. The terminal may perform a third repeated PUCCH transmission on the remaining symbols after satisfying a time required to change an uplink beam, transmission power, and frequency.
In another example, for repeated transmission of a changed TRP, when the time required to change the uplink beam, transmission power, or frequency is not satisfied, the terminal may discard the corresponding repeated uplink transmission occasion. For example, the mapping between the repetition PUCCH transmission and the TRP is configured as { TRP1, TRP2}, the terminal may discard the third repetition PUCCH transmission occasion. Thereafter, a fourth repetition PUCCH transmission occasion may be transmitted after the uplink beam, the transmission beam and the frequency change for TRP 2. In another example, when the mapping between the repetition PUCCH transmission and the TRP is configured to { TRP1, TRP2, TRP1, TRP2}, the terminal may discard the second and fourth repetition PUCCH transmission opportunities and transmit a repetition PUCCH transmission based on a single TRP.
When the repetition PUCCH transmission is performed in consideration of the channel state of each TRP by the method provided in the embodiments of the present disclosure, coverage extension of the uplink control signal may be expected. In addition, since transmission power is configured for each transmission or reception point, efficient battery management of the terminal can be expected.
This may be applied in the same way to the relation between the size of the time offset and the UE capability for uplink signal transmission. The terminal may transmit an uplink signal if the time offset has a value greater than the UE capability for changing the uplink beam, transmission power, or frequency. When the time offset has a value less than the UE capability for changing the uplink beam, transmission power or frequency, the terminal may consider one or a combination of the following operations to transmit an uplink signal in a similar manner as in the case where the offset between repeated transmissions fails to satisfy the UE capability:
-transmitting uplink signals with the same uplink beam, transmission power and frequency as in the previous uplink signal transmission;
-transmitting uplink signals with a default configured uplink beam, transmission power and frequency;
-applying a variable configuration in uplink beams, transmission power and frequency and transmitting repeated uplink signal transmissions; and
-discarding some symbols of the first retransmission occasion or the first retransmission occasion and transmitting the uplink signal.
Operation according to this condition describes a method in which a terminal supporting a single panel changes uplink beam, transmission power or frequency. If the terminal can support multiple panels, the terminal identifies whether the offset determined by the base station is configured to have a value less than the changed UE capability for the uplink beam, transmission power, frequency, or panel. The terminal may transmit an uplink signal when the offset determined by the base station has a value greater than the changed UE capability for the uplink beam, transmission power, frequency, or panel. When the offset is configured to have a value smaller than the changed UE capability for the uplink beam, transmission power, frequency, or panel, the terminal may transmit an uplink signal according to one or a combination of the following operations in a similar manner to the case where the offset between repeated transmissions fails to satisfy the UE capability by additionally considering the changed UE capability for the panel:
-transmitting uplink signals with the same uplink beam, transmission power, frequency and panel as in the previous uplink signal transmission;
-transmitting uplink signals with a default configured uplink beam, transmission power, frequency and panel;
-applying a variable configuration in the uplink beam, transmission power, frequency and panel and transmitting repeated uplink signal transmissions; and
-discarding some symbols of the first retransmission occasion or the first retransmission occasion and transmitting the uplink signal.
Here, the previous uplink signal represents the same recently transmitted physical channel as the uplink signal (PUCCH, PUSCH, or SRS) to be transmitted. The base station and the terminal may define default transmission information for each uplink signal (PUCCH, PUSCH, or SRS). Alternatively, the base station and the terminal may define default transmission information of the uplink signal with each other.
< third embodiment: aperiodic CSI report multiplexing method during repeated PUSCH transmission considering multiple TRPs >
According to embodiments of the present disclosure, when a terminal receives a configuration of a multi-TRP based repetition PUSCH transmission type a or B and receives scheduling of a transport block transmission, various methods for multiplexing an aperiodic CSI report to one or more specific PUSCH repetitions may be considered. PUSCH repetition to be considered below may correspond to nominal repetition or actual repetition. In addition, in the case where the terminal determines PUSCH repetition to which the aperiodic CSI report is to be multiplexed, when the corresponding PUSCH repetition has a length of one OFDM symbol, the PUSCH repetition may be excluded. As UE capabilities, the terminal may report whether or not a function of multiplexing aperiodic CSI reports to a plurality of PUSCH repetitions is supported.
Method 1-1 according to the disclosure, a terminal may perform multiplexing of aperiodic CSI repeatedly reported only to a first PUSCH among all PUSCH repetitions.
Method 1-2 according to the disclosure, a terminal may perform multiplexing of aperiodic CSI reports on two PUSCH repetitions among all PUSCH repetitions. In this case, the terminal may determine the first PUSCH repetition to which the first transmission beam is applied as the first PUSCH repetition of the two PUSCH repetitions to which the aperiodic CSI report is multiplexed. In addition, the terminal may determine a second PUSCH repetition among two PUSCH repetitions to which the aperiodic CSI report is multiplexed according to the following detailed method. According to the disclosure, aperiodic CSI reports with the same information may be multiplexed to each PUSCH repetition. In other words, CSI part 1 or CSI part 2 having the same information may be multiplexed.
Method 1-2-1 continuing with method 1-2 described above, the terminal may determine the first PUSCH repetition to which the second transmission beam is applied as the second PUSCH repetition. In this case, the terminal may perform multiplexing of aperiodic CSI on two PUSCH repetition reports regardless of whether the two determined PUSCH repetitions have the same OFDM symbol length or different OFDM symbol lengths. In this case, when the two PUSCH repetitions have different OFDM symbol lengths, soft combining is impossible in the base station, and only selection diversity can be obtained by decoding each of the two PUSCH repetitions.
Method 1-2-2 continuing with the above method 1-2, the terminal may limit the OFDM symbol length of the first PUSCH repetition to which the second transmission beam is applied to be the same as the OFDM symbol length of the first PUSCH repetition determined in the above method 1-2, thereby multiplexing the aperiodic CSI report thereto. For example, the terminal may adjust the transient period such that two PUSCH repetitions determined for multiplexing of aperiodic CSI reports have the same length during beam switching between two transmit beams. That is, the terminal may increase the length of a transient period existing between nominal repetitions of performing transmission beam switching such that OFDM symbol lengths between first actual repetitions of respective transmission beams are identical to each other.
For example, when there is no OFDM symbol position configured as an invalid symbol, the transmission beam mapping method of PUSCH repetition based on multiple TRPs is sequential, the OFDM symbol length of the nominal repetition of the repetition PUSCH transmission type a is 6, and the number of repeated transmissions is 4, the first nominal repetition may be mapped to the first transmission beam and transmitted in OFDM symbols 1 through 6 of slot 1, and the second nominal repetition may be mapped to the first transmission beam and transmitted in OFDM symbols 7 through 12 of slot 1. The third nominal repetition corresponds to the first nominal repetition after switching from the first transmission beam to the second transmission beam, and thus, there may be a transient period between the second and third nominal repetition. When the length of the transient period requires one OFDM symbol length, a third nominal repetition may be transmitted in OFDM symbol 14 of slot 1 through OFDM symbol 5 of slot 2 and may be split into two actual repetitions at the slot boundary. The first actual repetition of the third nominal repetition may be transmitted in OFDM symbol 14 of slot 1 and the second actual repetition may be transmitted in OFDM symbols 1 through 5 of slot 2.
In this case, the OFDM symbol length of the first actual repetition to which the first transmission beam is applied may be different from the OFDM symbol length of the second actual repetition to which the second transmission beam is applied. In order to make the OFDM symbol lengths the same, a transmission period corresponding to one OFDM symbol may be added between the second and third nominal repetitions. In this case, the third nominal repetition may be mapped to the second transmission beam and transmitted in OFDM symbols 1 through 6 of slot 2, and the aperiodic CSI report may be multiplexed to the first actual repetition of each transmission beam and transmitted.
According to the disclosure, when the OFDM symbol length of the first PUSCH repetition to which the second transmission beam is applied is different from the OFDM symbol length of the first PUSCH repetition, the aperiodic CSI report may be multiplexed to only one of the two PUSCH repetitions. In this case, one PUSCH to which the aperiodic CSI report is multiplexed may be predefined. That is, the aperiodic CSI report may be multiplexed to the first PUSCH repetition or the second PUSCH repetition. Alternatively, the aperiodic CSI report may be multiplexed to a shorter or longer PUSCH repetition of the two PUSCH repetitions. Alternatively, the aperiodic CSI report may be multiplexed to PUSCH repetition having a large or small number of resources among two PUSCH repetition.
Method 1-2-3 continuing with method 1-2, when the OFDM symbol length of the first PUSCH repetition to which the aperiodic CSI report determined in the above method 1-2 is applied is not identical to the OFDM symbol length of the first PUSCH repetition to which the aperiodic CSI report is to be multiplexed, the terminal may compare the amount of resources between the two PUSCH repetitions to determine a rate matching scheme according to the PUSCH repetition to which a smaller amount of resources is allocated, and perform multiplexing of the aperiodic CSI report to the two PUSCH repetitions.
According to one embodiment, reference is made to Table 40 above]The Q 'of the first and second PUSCH repetition can be calculated separately' CSI-part1 And Q' CSI-part2 And by using Q 'having a small value' CSI-part1 And Q' CSI-part2 Aperiodic CSI reports may be multiplexed to two PUSCH repetitions.
According to another embodiment, above [ Table 40]Used in the equation in And->At least one of the values of (c) may be applied to the repeated multiplexing operation of two PUSCHs in the same manner. In other words, in each of the two PUSCH repetitionsAnd->Has a small value inAnd->Can be used to calculate Q 'for rate matching of two PUSCH repetitions' CSI-part1 And Q' CSI-part2 。
In the above embodiment, it is possible to calculate only Q' CSI-part1 And Q' CSI-part2 Is used to multiplex aperiodic CSI reports.
Method 1-2-4 continuing with method 1-2, in PUSCH repetition to which the second transmission beam is applied, the terminal may determine an xth PUSCH repetition of the same length as the first PUSCH repetition to which the aperiodic CSI report determined in the above method 1-2 is multiplexed, as the PUSCH repetition to which the aperiodic CSI report is to be multiplexed. In this case, when there are several PUSCH repetitions having the same length, the terminal may determine the xth PUSCH repetition in the earliest order (i.e., with the smallest number) as the PUSCH repetition to which the aperiodic CSI report is to be multiplexed. When there is no such case (i.e., when there is no PUSCH repetition having the same length as the first PUSCH repetition among PUSCH repetitions to which the second transmission beam is applied), the terminal may determine the second PUSCH repetition to which the aperiodic CSI report is to be multiplexed in consideration of one of the above-described methods 1-1, 1-2-2, and 1-2-3.
Method 1-3 according to the disclosure, when determining PUSCH repetition to which aperiodic CSI reports are to be multiplexed, a terminal may determine an xth PUSCH repetition having the same OFDM symbol length for each transmission beam as a PUSCH repetition. For example, when there are four PUSCH repetitions for each of two transmission beams, and the second PUSCH repetition to which the first and second transmission beams are applied has the same OFDM symbol length, the terminal may multiplex the aperiodic CSI report to the corresponding PUSCH repetition. Here, when there are several pairs of PUSCH repetitions having the same length, the terminal may determine the X-th pair of PUSCH repetitions in the earliest order (i.e., with the smallest number) as the PUSCH repetition to which the aperiodic CSI report is to be multiplexed. When there is no such case, that is, when PUSCH repetitions of the same order in two transmission beams have different OFDM symbol lengths, the terminal may determine two PUSCH repetitions to which aperiodic CSI reports are to be multiplexed in consideration of one of the above-described methods 1-1, 1-2-2, and 1-2-3.
In the above-described methods 1-1 to 1-3, only two transmission beams are considered for convenience of description, but these methods may be generalized and considered for considering repeated transmission of N (> 2) or more transmission beams, i.e., N (> 2) or more TRPs. In addition, in the above-described methods 1-1 to 1-3, when PUSCH repetition to which aperiodic CSI reports are to be multiplexed is determined by a terminal, for convenience of description, description is made considering only whether PUSCH repetition has the same number or different number of OFDM symbols, but description is made by assuming that there is the same frequency resource allocation among PUSCH repetition, and thus, the methods 1-1 to 1-3 may be generalized and considered for considering not only whether PUSCH repetition has the same number of OFDM symbols but also whether PUSCH repetition has the same resource allocation value. That is, generalization to whether PUSCH repetition has the same number of REs determined in consideration of both time and frequency resource allocation is possible.
Fig. 21 illustrates an operation of a terminal in consideration of the third embodiment of the present disclosure. In fig. 21, the terminal may report UE capability information to the base station (operation 2101). In this case, when transmission beam switching in the second embodiment is performed, the transmittable information may include aperiodic CSI report related information, PUSCH repetition type a or B related information, whether or not multi-TRP-based PUSCH repetition is supported, and transient offset related information.
Thereafter, the terminal may receive higher layer signaling configuration information from the base station (operation 2102). In this case, the receivable information may include aperiodic CSI report related information, repeated PUSCH transmission type a or B related information, multi-TRP-based PUSCH repetition related information (repeated transmission method, number of repeated transmissions, transmission beam mapping unit or scheme, whether multiple SRI or TPMI fields can be supported, multiple codebook/non-codebook SRS resource sets, etc.).
Thereafter, the terminal may receive a DCI for scheduling an aperiodic CSI report and a repeated transmission of PUSCH including a transport block (operation 2103), and perform repeated PUSCH transmission considering one of methods 1-1 to 1-3 when determining repeated PUSCH transmission to which the aperiodic CSI report is to be multiplexed (operation 2104). When the terminal considers methods 1-2-4 and 1-3 and a backoff operation is required as described above (for example, when the method 1-2-4 is considered and there is no PUSCH repetition having the same length as the first PUSCH repetition in PUSCH repetition to which the second transmission beam is applied), the terminal may perform repeated PUSCH transmission considering one of methods 1-1 and 1-2-1 to 1-2-3 (operation 2105).
Fig. 22 illustrates an operation of a base station considering the third embodiment of the present disclosure. In fig. 22, the base station may receive a UE capability report from the terminal (operation 2201). In this case, when transmission beam switching in the second embodiment is performed, the receivable information may include aperiodic CSI report related information, PUSCH repetition type a or B related information, multi-TRP-based PUSCH repetition related information, and transient offset related information. Thereafter, the base station may transmit higher layer signaling configuration information to the terminal (operation 2202).
In this case, the transmittable information may include aperiodic CSI report related information, repeated PUSCH transmission type a or B related information, multi-TRP-based PUSCH repetition related information (repeated transmission method, number of repeated transmissions, transmission beam mapping unit or scheme, whether multiple SRI or TPMI fields can be supported, multiple codebook/non-codebook SRS resource sets, etc.). Thereafter, the base station may transmit DCI for scheduling an aperiodic CSI report and repeated transmission of PUSCH including a transport block (operation 2203), and receive the repeated PUSCH transmission by considering one of methods 1-1 to 1-3 on the assumption that the terminal determines the repeated PUSCH transmission to which the aperiodic CSI report is to be multiplexed (operation 2204). When the terminal considers methods 1-2-4 and 1-3 and a backoff operation is required as described above (e.g., when method 1-2-4 is considered and there is no PUSCH repetition having the same length as the first PUSCH repetition in PUSCH repetition to which the second transmission beam is applied), the base station may receive the repeated PUSCH transmission by assuming that the terminal considers one of methods 1-1 and 1-2-1 to 1-2-3 (operation 2205).
< example (3-1): method of multiplexing aperiodic CSI reports according to higher layer signaling during PUSCH transmission considering multiple TRPs >
According to embodiments of the present disclosure, when a terminal receives a configuration of a multi-TRP based repetition PUSCH transmission type a or B and receives scheduling of a transport block transmission, various methods for multiplexing an aperiodic CSI report to one or more specific PUSCH repetitions may be considered. PUSCH repetition to be considered below may correspond to nominal repetition or actual repetition. In addition, in the case where the terminal determines PUSCH repetition to which the aperiodic CSI report is to be multiplexed, when the corresponding PUSCH repetition has a length of one OFDM symbol, the PUSCH repetition may be excluded. As UE capabilities, the terminal may report whether or not a function of multiplexing aperiodic CSI reports to a plurality of PUSCH repetitions is supported.
Methods 1-4 according to the disclosure, a terminal may multiplex aperiodic CSI reports to two PUSCH repetitions among all PUSCH repetitions. In this case, the terminal may determine a first PUSCH repetition of the two PUSCH repetitions to which the aperiodic CSI report is to be multiplexed as the first PUSCH repetition to which the first transmission beam is applied. In addition, when the terminal determines an xth PUSCH repetition to which the second transmission beam is applicable, the base station may configure Y corresponding to the candidate number of X via higher layer signaling. In the case of PUSCH repetition type a, when the number of repetitions indicated to the terminal via DCI is N, Y may be a natural number equal to or greater than 1 and equal to or less than N.
In the case of PUSCH repetition type B, when the number of nominal repetitions indicated to the terminal via DCI is N and the number of actual repetitions is M, Y may be a natural number equal to or greater than 1 and equal to or less than M. In addition, for a second PUSCH repetition of two PUSCH repetitions to which aperiodic CSI reports are to be multiplexed, the terminal can determine the following detailed method by using a Y value configured via higher layer signaling. According to the disclosure, aperiodic CSI reports with the same information may be multiplexed to each PUSCH repetition. In other words, CSI part 1 and CSI part 2 having the same information may be multiplexed.
Method 1-4-1 continuing with method 1-4 described above, the terminal may determine the second PUSCH repetition as the first PUSCH repetition to which the second transmission beam is applied. In this case, the terminal may multiplex the aperiodic CSI report to two PUSCH repetitions, regardless of the fact that the two PUSCH repetitions determined have the same OFDM symbol length and different OFDM symbol lengths. In this case, when the two PUSCH repetitions have different OFDM symbol lengths, soft combining is impossible in the base station, and only selection diversity can be obtained by decoding each of the two PUSCH repetitions.
Method 1-4-2 continuing with the above method 1-4, the terminal may limit the OFDM symbol length of the first PUSCH repetition to which the second transmission beam is applied to be the same as the OFDM symbol length of the first PUSCH repetition determined in the above method 1-4, thereby multiplexing the aperiodic CSI report thereto. For example, the terminal may adjust the transient period such that two PUSCH repetitions determined for multiplexing of aperiodic CSI reports have the same length during beam switching between two transmit beams. That is, the terminal may increase the length of a transient period existing between nominal repetitions of performing transmission beam switching such that OFDM symbol lengths between first actual repetitions of respective transmission beams are identical to each other.
For example, when there is no OFDM symbol position configured as an invalid symbol, the transmission beam mapping method of the PUSCH repetition based on the multiple TRP is sequential, the OFDM symbol length of the nominal repetition of the repetition PUSCH transmission type B is 6, and the number of repeated transmissions is 4, the first nominal repetition may be mapped to the first transmission beam and transmitted in OFDM symbols 1 to 6 of slot 1, and the second nominal repetition may be mapped to the first transmission beam and transmitted in OFDM symbols 7 to 12 of slot 1. The third nominal repetition corresponds to the first nominal repetition after the beam is switched from the first transmission beam to the second transmission beam, and thus, there may be a transient period between the second and third nominal repetitions.
When the length of the transient period requires one OFDM symbol length, a third nominal repetition may be transmitted in OFDM symbol 14 of slot 1 through OFDM symbol 5 of slot 2 and may be split into two actual repetitions at the slot boundary. The first actual repetition of the third nominal repetition may be transmitted in OFDM symbol 14 of slot 1 and the second actual repetition may be transmitted in OFDM symbols 1 through 5 of slot 2. In this case, the OFDM symbol length of the first actual repetition to which the first transmission beam is applied may be different from the OFDM symbol length of the second actual repetition to which the second transmission beam is applied. In order to make the OFDM symbol lengths the same, a transmission period corresponding to one OFDM symbol may be added between the second and third nominal repetitions. In this case, the third nominal repetition may be mapped to the second transmission beam and transmitted in OFDM symbols 1 through 6 of slot 2, and the aperiodic CSI report may be multiplexed to the first actual repetition of each transmission beam and transmitted.
According to the disclosure, when the OFDM symbol length of the first PUSCH repetition to which the second transmission beam is applied is different from the OFDM symbol length of the first PUSCH repetition, the aperiodic CSI report may be multiplexed to only one of the two PUSCH repetitions. In this case, one PUSCH to which the aperiodic CSI report is multiplexed may be predefined. That is, the aperiodic CSI report may be multiplexed to the first PUSCH repetition or the second PUSCH repetition. Alternatively, aperiodic CSI reports may be multiplexed to shorter or longer PUSCH repetitions of the two PUSCH repetitions. Alternatively, the aperiodic CSI report may be multiplexed to PUSCH repetition having a large or small number of resources among two PUSCH repetition.
Method 1-4-3 continuing with method 1-4-3, when the OFDM symbol length of the first PUSCH repetition to which the aperiodic CSI report determined in the above method 1-4 is applied is not identical to the OFDM symbol length of the first PUSCH repetition to which the aperiodic CSI report is to be multiplexed, the terminal may compare the amount of resources between the two PUSCH repetitions to determine a rate matching scheme according to the PUSCH repetition to which a smaller amount of resources is allocated, and perform multiplexing of the aperiodic CSI report to the two PUSCH repetitions.
According to one embodiment, reference is made to Table 40 above]The Q 'of the first and second PUSCH repetition can be calculated separately' CSI-part1 And Q' CSI-part2 And by using Q 'having a small value' CSI-part1 And Q' CSI-part2 Aperiodic CSI reports may be multiplexed to two PUSCH repetitions.
According to another embodiment, above [ Table 40]Values used in the equation in Can be applied in the same way to the multiplexing operation of two PUSCH repetitions. In other words, in each of the two PUSCH repetitionsAnd->Has a small value inAnd->Can be used to calculate Q 'for rate matching of two PUSCH repetitions' CSI-part1 And Q' CSI-part2 。
In the above embodiment, it is possible to calculate only Q' CSI-part1 And Q' CSI-part2 Is used to multiplex aperiodic CSI reports.
Method 1-4-4 continuing with method 1-4, in PUSCH repetition to which the second transmission beam is applied, the terminal may determine the xth PUSCH repetition of the same length as the first PUSCH repetition to which the aperiodic CSI report determined in the above method 1-4 is multiplexed as the PUSCH repetition to which the aperiodic CSI report is to be multiplexed. Here, when determining the X-th PUSCH repetition, the number of PUSCH repetitions applied for comparing whether the second transmission beam having the same OFDM symbol length as the first PUSCH repetition may be limited to a Y value configured via higher layer signaling.
In this case, when there are several PUSCH repetitions having the same length, the terminal may determine the xth PUSCH repetition in the earliest order (i.e., with the smallest number) as the PUSCH repetition to which the aperiodic CSI report is to be multiplexed. When there is no such case (i.e., when there is no PUSCH repetition having the same length as the first PUSCH repetition among PUSCH repetitions to which the second transmission beam is applied), the terminal may determine the second PUSCH repetition to which the aperiodic CSI report is to be multiplexed in consideration of one of the above-described methods 1-4, 1-4-1, 1-4-2, and 1-4-3.
Method 1-5 according to the disclosure, when determining PUSCH repetition to which aperiodic CSI reports are to be multiplexed, a terminal may determine an xth PUSCH repetition having the same OFDM symbol length for each transmission beam as a PUSCH repetition. Here, when determining the X-th PUSCH repetition, the number of PUSCH repetition pairs for comparing whether each transmission beam has the same OFDM symbol length may be limited to a Y value configured via higher layer signaling.
For example, when there are four PUSCH repetitions for each of two transmission beams, Y is configured to be 2, and the second PUSCH repetition to which the first and second transmission beams are applied has the same OFDM symbol length, the terminal may multiplex the aperiodic CSI report to the corresponding PUSCH repetition. Here, when there are several pairs of PUSCH repetitions having the same length, the terminal may determine the X-th pair of PUSCH repetitions in the earliest order (i.e., with the smallest number) as the PUSCH repetition to which the aperiodic CSI report is to be multiplexed. When there is no such case, that is, when PUSCH repetitions of the same order in two transmission beams have different OFDM symbol lengths, the terminal may determine two PUSCH repetitions to which aperiodic CSI reports are to be multiplexed in consideration of one of the above-described methods 1-4, 1-4-1, 1-4-2, and 1-4-3.
In the above-described methods 1-4, 1-4-1, 1-4-2, 1-4-3, and 1-5, only two transmission beams are considered for convenience of description, but these methods may be generalized to and considered for considering repeated transmission of N (> 2) or more transmission beams, i.e., N (> 2) or more TRPs. In addition, in the above-described methods 1-4, 1-4-1, 1-4-2, 1-4-3, and 1-5, when PUSCH repetition to which aperiodic CSI report is to be multiplexed is determined by a terminal, for convenience of description, description is made considering only whether PUSCH repetition has the same number or different number of OFDM symbols, but description is made by assuming that there is the same frequency resource allocation between PUSCH repetition, and thus, methods 1-4, 1-4-1, 1-4-2, 1-4-3, and 1-5 may be generalized to and considered for considering not only whether PUSCH repetition has the same number of OFDM symbols but also whether PUSCH repetition has the same resource allocation value. That is, generalization to whether PUSCH repetition has the same number of REs determined in consideration of both time and frequency resource allocation is possible.
< fourth embodiment: method for aperiodic/semi-persistent CSI report transmission during repeated PUSCH transmission considering multiple TRPs >
In embodiments of the present disclosure, a terminal receives a configuration of a repeated PUSCH transmission type B based on multiple TRPs and receives DCI for receiving a scheduling of an aperiodic CSI report or activating a semi-persistent SCI report, and the corresponding DCI may consider various PUSCH repeated transmission schemes for a case where a transport block transmission is not scheduled. In addition, when it is determined that the PUSCH repetition to which the aperiodic or semi-persistent CSI report is to be multiplexed and the corresponding PUSCH repetition have a length of one OFDM symbol, the PUSCH repetition may be excluded.
Method 2-1 according to the disclosure, a terminal can assume that a nominal repetition number corresponds to one regardless of the configured number of repeated transmissions of the repeated PUSCH transmission type B. In this case, the terminal may apply a first transmission beam of two different transmission beams received through a repeated PUSCH transmission configuration based on the multi-TRP and transmit the first transmission beam. In this case, it is assumed that the OFDM symbol length of the first nominal repetition is the same as the OFDM symbol length of the first actual repetition. The first nominal repeated transmission may be omitted if the first nominal repeated OFDM symbol length is not the same as the first actual repeated OFDM symbol length.
Method 2-1-1 continuing with method 2-1, the terminal may consider only one nominally repeated transmission, regardless of the configured number of repeated PUSCH transmissions, the terminal may transmit one PUSCH, such as the nominal and actual repetitions among a plurality of nominally and actual repetitions generated by the configured number of repeated transmissions of the repeated PUSCH transmission type B, and omit different repeated PUSCH transmissions. In this case, when there are a plurality of PUSCH transmissions such as a nominal repetition and an actual repetition, PUSCH repetition of the earliest order may be performed, and the remaining repeated PUSCH transmissions may be omitted. When all the nominal repeated and actual repeated OFDM symbol lengths are different, the corresponding repeated PUSCH transmission may be omitted.
Method 2-2 according to the disclosure, the terminal can assume that the nominal repetition number corresponds to one and the actual repetition number corresponds to two, regardless of the configured number of repeated transmissions of the repeated PUSCH transmission type B. In this case, each of the actual repetition and the nominal repetition may have half the number of OFDM symbols. When the configured nominal repeated OFDM symbol length corresponds to an odd number, and when the terminal determines the actually repeated OFDM symbol length, the terminal may use a value obtained by dividing the OFDM symbol length by 2 and truncating the result number.
In this case, the terminal may map the first transmission beam to the first actual repetition and the second transmission beam to the second actual repetition, regardless of the configuration of the transmission beam mapping scheme during the PUSCH repetition based on the multiple TRP corresponding to the sequential or cyclic scheme. That is, the terminal may apply a cyclic scheme as the transmission beam mapping scheme regardless of a configuration in which the transmission beam mapping scheme corresponds to a sequential or cyclic scheme. If the OFDM symbol length of the first actual repetition is not the same as the OFDM symbol length of the second actual repetition, both actual repetitions may be omitted, or one of the (first and second) actual repetition transmissions may be omitted.
Method 2-3 according to the disclosure, the terminal can assume that the nominal repetition number corresponds to two regardless of the configured number of repeated transmissions of PUSCH repetition type B. In this case, the terminal may map the first transmission beam to the first PUSCH repetition and the second transmission beam to the second PUSCH repetition, regardless of a configuration in which the transmission beam mapping scheme during the multi-TRP-based PUSCH repetition corresponds to a sequential or cyclic scheme. That is, the terminal may apply a cyclic scheme as the transmission mapping scheme regardless of a configuration in which the transmission beam mapping scheme corresponds to a sequential or cyclic scheme.
The first nominal repeated transmission may be omitted if the first nominal repeated OFDM symbol length is not the same as the first actual repeated OFDM symbol length. Thus, when the first transmission is omitted, the transmission beam for the second transmission may still be mapped to the second transmission beam. In addition, if the OFDM symbol length of the second nominal repetition is not the same as the OFDM symbol length of the second actual repetition, the second nominal repetition transmission may be omitted. In another example, if the first nominally repeated OFDM symbol length is not the same as the first actually repeated OFDM symbol length, both the first and second nominally repeated transmissions may be omitted.
Method 2-3-1 continuing with method 2-3 above, the terminal may consider only two nominally repeated transmissions, regardless of the configured number of repeated PUSCH transmissions, the terminal may transmit one PUSCH transmission per transmission beam, such as the nominal repetition and the actual repetition of a plurality of nominally and actual repetitions generated by the configured number of repeated PUSCH transmissions, and omit different repeated PUSCH transmissions.
That is, a total of two nominal repetition transmissions may be considered in which transmission is performed on PUSCH in the earliest order in PUSCH having the same OFDM symbol length in nominal repetition and actual repetition by comparison between all nominal repetition and actual repetition of the first transmission beam, and transmission is performed on PUSCH in the earliest order in PUSCH having the same OFDM symbol length in nominal repetition and actual repetition by comparison between all nominal repetition and actual repetition of the second transmission beam. In this case, for each transmission beam, there is no case where the nominal repetition and the actual repetition have the same OFDM symbol length, and the corresponding transmission may be omitted.
In the methods 2-1 to 2-3-1, only two transmission beams are considered for convenience of description, but these methods may be generalized and considered for considering repeated transmission of N (> 2) or more transmission beams, i.e., N (> 2) or more TRPs.
Fig. 23 illustrates an operation of a terminal in consideration of the fourth embodiment of the present disclosure. In fig. 23, the terminal may report UE capability information to the base station (operation 2301). In this case, when transmission beam switching in the second embodiment is performed, the transmittable information may include aperiodic CSI report related information, repetition PUSCH transmission type a or B related information, multi-TRP-based PUSCH repetition related information, and transient offset related information. Thereafter, the terminal may receive higher layer signaling configuration information from the base station (operation 2302).
In this case, when transmission beam switching in the second embodiment is performed, the receivable information may include aperiodic/semi-persistent CSI report related information, repeated PUSCH transmission type a or B related information, repeated PUSCH transmission related information based on multiple TRPs (repeated transmission method, number of repeated transmissions, transmission beam mapping unit or scheme, whether multiple SRI or TPMI fields can be supported, multiple codebook/non-codebook SRS resource sets, etc.), and transient offset related information. Thereafter, the terminal may receive DCI for scheduling an aperiodic CSI report, activating a semi-persistent CSI report, and scheduling a repeated PUSCH transmission excluding transport block scheduling (operation 2303), and perform repeated PUSCH transmission considering one of methods 2-1 to 2-3 when determining the repeated PUSCH transmission to which the aperiodic or semi-persistent CSI report is to be multiplexed (operation 2304).
Fig. 24 shows an operation of a base station in consideration of the fourth embodiment of the present disclosure. In fig. 24, the base station may receive a UE capability report from the terminal (operation 2401). In this case, when transmission beam switching in the second embodiment is performed, the receivable information may include aperiodic CSI report related information, repeated PUSCH transmission type a or B related information, repeated PUSCH transmission related information based on multi-TRP, and transient offset related information. Thereafter, the base station may transmit higher layer signaling configuration information to the terminal (operation 2402).
In this case, when transmission beam switching in the second embodiment is performed, the transmittable information may include aperiodic CSI report related information, repetition PUSCH transmission type a or B related information, multi-TRP-based PUSCH repetition related information (repetition transmission method, number of repetition transmissions, transmission beam mapping unit or scheme, whether multiple SRI or TPMI fields can be supported, multiple codebook/non-codebook SRS resource sets, etc.), and transient offset related information. Thereafter, the base station may transmit DCI for scheduling an aperiodic CSI report, activating a semi-persistent CSI report, and scheduling a repeated PUSCH transmission excluding transport block scheduling (operation 2403), and receive the repeated PUSCH transmission by considering one of methods 2-1 to 2-3 when the terminal determines the repeated PUSCH transmission to which the aperiodic or semi-persistent CSI report is to be multiplexed (operation 2404).
Fig. 25 illustrates a terminal structure in a wireless communication system according to an embodiment of the present disclosure.
Referring to fig. 25, a terminal may include a transceiver, a memory (not shown), and a terminal processor 2505 (or a terminal controller or processor) that instruct a terminal receiver 2500 and a terminal transmitter 2510. The transceivers 2500 and 2510, memory and terminal processor 2505 of the terminal may operate according to the terminal communication methods described above. However, the elements of the terminal are not limited to the above examples. For example, the terminal may include more or fewer components than those described above. In addition, the transceiver, memory, and processor may be implemented in a single chip.
The transceiver may transmit signals to and receive signals from a base station. Here, the signal may include control information and data. To this end, the transceiver may include an RF transmitter that up-converts the frequency of a transmission signal and amplifies the transmission signal, an RF receiver that amplifies a reception signal with low noise and down-converts the frequency, and so on. However, this is merely an embodiment of a transceiver, and the elements of the transceiver are not limited to RF transmitters and RF receivers.
In addition, the transceiver may receive a signal through a wireless channel, output the signal to the processor, and transmit the signal output from the processor through the wireless channel.
The memory may store programs and data required for operation of the terminal. In addition, the memory may store control information or data included in signals transmitted and received by the terminal. The memory may include storage media such as ROM, RAM, hard disk, CD-ROM, and DVD, or a combination of storage media. In addition, there may be multiple memories.
In addition, the processor may control a series of processes so that the terminal operates according to the above-described embodiments. For example, the processor may control an element of the terminal to simultaneously receive a plurality of PDSCH by receiving DCI including two layers. There may be a plurality of processors, and the processors may perform operations of controlling elements of the terminal by executing programs stored in the memory.
Fig. 26 illustrates a structure of a base station in a wireless communication system according to an embodiment of the present disclosure.
Referring to fig. 26, a base station may include a transceiver, a memory (not shown), and a base station processor 2605 (or a base station controller or processor) that instruct the base station receiver 2600 and a base station transmitter 2610. The base station transceivers 2600 and 2610, memory, and base station processor 2605 may operate according to the base station communication methods described above. However, the elements of the base station are not limited to the above examples. For example, a base station may include more or fewer elements than those described above. In addition, the transceiver, memory, and processor may be implemented in a single chip.
The transceiver may transmit signals to and receive signals from the terminal. Here, the signal may include control information and data. To this end, the transceiver may include an RF transmitter that up-converts the frequency of a transmission signal and amplifies the transmission signal, an RF receiver that amplifies a reception signal with low noise and down-converts the frequency, and so on. However, this is merely an embodiment of a transceiver, and the elements of the transceiver are not limited to RF transmitters and RF receivers.
In addition, the transceiver may receive a signal through a wireless channel, output the signal to the processor, and transmit the signal output from the processor through the wireless channel.
The memory may store programs and data required for operation of the base station. In addition, the memory may store control information or data included in signals transmitted and received by the base station. The memory may include storage media such as ROM, RAM, hard disk, CD-ROM, and DVD, or a combination of storage media. In addition, there may be multiple memories.
The processor may control a series of processes so that the base station may operate according to the above-described embodiments of the present disclosure. For example, the processor may configure two layers of DCI including allocation information for a plurality of PDSCH, and control each element of the base station to transmit the DCI. There may be a plurality of processors, and the processors may perform operations of controlling elements of the base station by executing programs stored in the memory.
The method according to the embodiments described in the claims or specification of the present disclosure may be implemented by hardware, software, or a combination of hardware and software.
When the method is implemented by software, a computer-readable storage medium storing one or more programs (software modules) may be provided. One or more programs stored in the computer-readable storage medium may be configured to be executed by one or more processors within the electronic device. The at least one program may include instructions that cause an electronic device to perform a method according to various embodiments of the present disclosure defined by the appended claims and/or disclosed herein.
Programs (software modules or software) may be stored in non-volatile memory, including random access memory and flash memory, read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), magnetic disk storage, compact disc-ROM (CD-ROM), digital Versatile Disks (DVD), or other types of optical storage devices or cartridges. Alternatively, any combination of some or all of them may form a memory storing a program. In addition, a plurality of such memories may be included in the electronic device.
In addition, the program may be stored in an attachable storage device that may access the electronic device through a communication network such as the internet, an intranet, a Local Area Network (LAN), a wide area network (WLAN), and a Storage Area Network (SAN), or a combination thereof. Such a storage device may access the electronic device via an external port. Further, a separate storage device on the communication network may access the portable electronic device.
In the above detailed embodiments of the present disclosure, elements included in the present disclosure are expressed in singular or plural according to the presented detailed embodiments. However, for convenience of description, the singular or plural forms are appropriately selected to the presented case, and the present disclosure is not limited by the elements expressed in the singular or plural. Accordingly, an element expressed in a plurality may also include a single element, or an element expressed in the singular may also include a plurality of elements.
The embodiments of the present disclosure described and illustrated in the specification and drawings are merely specific examples, which have been presented to easily explain the technical content of the present disclosure and to aid understanding of the present disclosure, and are not intended to limit the scope of the present disclosure. That is, it is apparent to those skilled in the art that other modifications based on the technical ideas of the present disclosure may be implemented. Further, the above respective embodiments may be used in combination as required. For example, a portion of one embodiment of the present disclosure may be combined with a portion of another embodiment to operate a base station and a terminal. As an example, a portion of embodiment 1 of the present disclosure may be combined with a portion of embodiment 2 to operate a base station and a terminal. Further, although the above embodiments have been described based on the FDD LTE system, other variations of the technical ideas based on the embodiments may be implemented in other systems such as the TDD LTE, 5G, or NR systems.
In the drawings describing the methods of the present disclosure, the order of description does not always correspond to the order in which the steps of each method are performed, and the order relationship between the steps may be changed or the steps may be performed in parallel.
Alternatively, in the drawings describing the method of the present disclosure, some elements may be omitted, and only some elements may be included therein, without departing from the true spirit and scope of the present disclosure.
Further, in the methods of the present disclosure, some or all of the contents of each embodiment may be combined without departing from the true spirit and scope of the present disclosure.
Various embodiments of the present disclosure have been described, but the foregoing description of the present disclosure is for illustrative purposes only and the embodiments of the present disclosure are not limited to the embodiments set forth herein. Those skilled in the art will understand that the present disclosure may be changed into other specific forms without changing the technical idea or essential features of the present disclosure. The scope of the present disclosure should be determined not by the above detailed description but by the appended claims, and all changes and modifications that come within the meaning and range of the claims and the concept equivalent thereto should be construed to be within the scope of the present disclosure.
While the present disclosure has been described with various embodiments, various changes and modifications may be suggested to one skilled in the art. The present disclosure is intended to embrace such alterations and modifications that fall within the scope of the appended claims.
Claims (14)
1. A terminal in a communication system, the terminal comprising:
a transceiver; and
a controller operatively connected to the transceiver, the controller configured to:
a configuration of a Physical Uplink Shared Channel (PUSCH) repetition type B is received from a base station,
receiving Downlink Control Information (DCI) from the base station, the DCI scheduling aperiodic Channel State Information (CSI) report or activating a semi-persistent CSI report on a PUSCH, the DCI including a first SRS resource indicator field associated with a first Sounding Reference Signal (SRS) resource set and a second SRS resource indicator field associated with a second SRS resource set,
identifying nominal repetition and actual repetition of the PUSCH based on the PUSCH repetition type B, and
transmitting a CSI report on the PUSCH to the base station according to the PUSCH repetition type B,
wherein in the case where the PUSCH is transmitted with a transport block, the CSI report is transmitted on both actual repetitions in response to a first actual repetition associated with the first SRS resource set and the first actual repetition associated with the second SRS resource set comprising the same number of symbols.
2. The terminal of claim 1, wherein the two actual repetitions comprise a first actual repetition associated with the SRS resource set and a first actual repetition associated with the second SRS resource set.
3. The terminal of claim 1, wherein the CSI report is transmitted on a first one of the actual repetitions of the PUSCH in response to the first actual repetition associated with the first SRS resource set and the first actual repetition associated with the second SRS resource set comprising different numbers of symbols, if the PUSCH is transmitted with the transport block.
4. The terminal of claim 1, wherein a nominal repetition number of the PUSCH is determined to be two in case the PUSCH is not transmitted with a transport block, regardless of the nominal repetition number configured from the base station.
5. The terminal of claim 4, wherein a first nominal repetition and a second nominal repetition of a number of nominal repetitions determined to be two comprise the same number of symbols corresponding to the first actual repetition and the second actual repetition, respectively, and
wherein the CSI report is transmitted on the first actual repetition and the second actual repetition.
6. The terminal of claim 4, wherein one of the first or second nominal repetition comprises the same number of symbols as the corresponding first or second actual repetition, and
wherein a nominal repetition that does not include the same number of symbols as the corresponding actual repetition is ignored and the CSI report is transmitted on the actual repetition that is not ignored.
7. A base station in a communication system, the base station comprising:
a transceiver; and
a controller operatively connected to the transceiver, the controller configured to:
a configuration of a Physical Uplink Shared Channel (PUSCH) repetition type B is transmitted to the terminal,
transmitting Downlink Control Information (DCI) to the terminal, the DCI scheduling an aperiodic Channel State Information (CSI) report or activating a semi-persistent CSI report on a PUSCH, the DCI including a first SRS resource indicator field associated with a first Sounding Reference Signal (SRS) resource set and a second SRS resource indicator field associated with a second SRS resource set, and
receiving a CSI report on the PUSCH from the terminal according to the PUSCH repetition type B,
wherein in case the PUSCH is received with a transport block, the CSI report is received on both actual repetitions in response to a first actual repetition associated with the first SRS resource set and the first actual repetition associated with the second SRS resource set comprising the same number of symbols.
8. The base station of claim 7, wherein the two actual repetitions comprise a first actual repetition associated with the SRS resource set and a first actual repetition associated with the second SRS resource set.
9. The base station of claim 7, wherein the CSI report is received on a first one of the actual repetitions in response to the first actual repetition associated with the first set of SRS resources and the first actual repetition associated with the second set of SRS resources comprising a different number of symbols if the PUSCH is received with the transport block.
10. The base station of claim 7, wherein a nominal repetition number of the PUSCH is determined to be two in case the PUSCH is not received with a transport block, regardless of the nominal repetition number configured to the terminal.
11. The base station of claim 10, wherein a first nominal repetition and a second nominal repetition of a number of nominal repetitions determined to be two comprise the same number of symbols corresponding to the first actual repetition and the second actual repetition, respectively, and
wherein the CSI report is received on the first actual repetition and the second actual repetition.
12. The base station of claim 10, wherein one of the first or second nominal repetition comprises the same number of symbols as the corresponding first or second actual repetition, and
wherein a nominal repetition that does not include the same number of symbols as the corresponding actual repetition is ignored and the CSI report is received on the actual repetition that is not ignored.
13. A method of a terminal in a communication system, the method comprising:
a configuration of a Physical Uplink Shared Channel (PUSCH) repetition type B is received from a base station,
receiving Downlink Control Information (DCI) from the base station, the DCI scheduling aperiodic Channel State Information (CSI) report or activating a semi-persistent CSI report on a PUSCH, the DCI including a first SRS resource indicator field associated with a first Sounding Reference Signal (SRS) resource set and a second SRS resource indicator field associated with a second SRS resource set,
identifying nominal repetition and actual repetition of the PUSCH based on the PUSCH repetition type B, and
transmitting a CSI report on the PUSCH to the base station according to the PUSCH repetition type B,
wherein in the case where the PUSCH is transmitted with a transport block, the CSI report is transmitted on both actual repetitions in response to a first actual repetition associated with the first SRS resource set and the first actual repetition associated with the second SRS resource set comprising the same number of symbols.
14. A method of a base station in a communication system, the method comprising:
a configuration of a Physical Uplink Shared Channel (PUSCH) repetition type B is transmitted to the terminal,
transmitting Downlink Control Information (DCI) to the terminal, the DCI scheduling an aperiodic Channel State Information (CSI) report or activating a semi-persistent CSI report on a PUSCH, the DCI including a first SRS resource indicator field associated with a first Sounding Reference Signal (SRS) resource set and a second SRS resource indicator field associated with a second SRS resource set, and
receiving a CSI report on the PUSCH from the terminal according to the PUSCH repetition type B,
wherein in case the PUSCH is received with a transport block, the CSI report is received on both actual repetitions in response to a first actual repetition associated with the first SRS resource set and the first actual repetition associated with the second SRS resource set comprising the same number of symbols.
Applications Claiming Priority (5)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| KR10-2021-0015625 | 2021-02-03 | ||
| KR10-2021-0030851 | 2021-03-09 | ||
| KR10-2021-0049435 | 2021-04-15 | ||
| KR1020210049435A KR20220112154A (en) | 2021-02-03 | 2021-04-15 | Method and apparatus of channel state information reporting via uplink data repetition in network cooperative communications |
| PCT/KR2022/001712 WO2022169272A1 (en) | 2021-02-03 | 2022-02-03 | Method and apparatus for reporting channel state information through repeated uplink data transmission in network cooperative communication |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116806415A true CN116806415A (en) | 2023-09-26 |
Family
ID=88080850
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202280013082.6A Pending CN116806415A (en) | 2021-02-03 | 2022-02-03 | Method and device for reporting channel state information through repeated uplink data transmission in network cooperative communication |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116806415A (en) |
-
2022
- 2022-02-03 CN CN202280013082.6A patent/CN116806415A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| KR102514603B1 (en) | Method and apparatus for transmitting and receiving PDCCH in wireless communication system | |
| CN113785527A (en) | Method for transmitting PUSCH, user equipment, device and storage medium, and method and base station for receiving PUSCH | |
| CN115516978A (en) | Method and apparatus for uplink data repetition transmission and reception for network cooperative communication | |
| US20220209904A1 (en) | Method and apparatus for determining processing time of ue in wireless communication system | |
| US20220239410A1 (en) | Method and apparatus for transmitting and receiving uplink phase tracking reference signal for network cooperative communication system | |
| CN113424631A (en) | Method of performing uplink transmission, user equipment, device and storage medium, and method of performing uplink reception and base station | |
| CN116018865A (en) | Method and apparatus for allocating frequency resources in a wireless communication system | |
| US20220295457A1 (en) | Method and apparatus for determining priority regarding downlink control information reception in wireless communication system | |
| CN117063542A (en) | Method and apparatus for reporting uplink power headroom in wireless communication system | |
| KR20240001286A (en) | Method and device for transmission/reception based on time unit group in wireless communication system | |
| KR20220136788A (en) | Method and apparatus for repetitive transmission of downlink control information in network cooperative communications | |
| CN115516801A (en) | Detection method and device in wireless communication system | |
| US20230209527A1 (en) | Method and apparatus for transmission and reception based on predicted transmission configuration information in wireless communication systems | |
| US20220255700A1 (en) | Method and apparatus for reporting channel state information through repeated uplink data transmission in network cooperative communication | |
| CN117441399A (en) | Method and device for data transmission and reception in network cooperative communication | |
| CN116349173A (en) | Method and apparatus for repeatedly transmitting/receiving downlink control information in wireless communication system | |
| CN117136516A (en) | Method and apparatus for uplink transmission in a wireless communication system | |
| CN116806415A (en) | Method and device for reporting channel state information through repeated uplink data transmission in network cooperative communication | |
| US20220408468A1 (en) | Method and apparatus for transmitting data in network cooperative communications | |
| EP4270844A1 (en) | Method and apparatus for uplink transmission in wireless communication system | |
| CN117016035A (en) | Method and apparatus for determining downlink control information reception priority in wireless communication system | |
| KR20220112154A (en) | Method and apparatus of channel state information reporting via uplink data repetition in network cooperative communications | |
| KR20220167157A (en) | Method and apparatus for transmitting and receiving downlink control information and data in a wirelss communication system | |
| CN116803174A (en) | Method and apparatus for configuring repeated transmission and reception of downlink control information in wireless communication system | |
| KR20220144706A (en) | Method and apparatus for repetitive transmission of downlink control information in network cooperative communications |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |